Visara LINCS Features - Manual (Page 124)

114
LINCS Features
707021-001
2. If the new microcode contains new functions which you want to configure for the
Network Sites, use the Central Site Customization utility to re-configure as desired
and save the modified configuration back to the library disk. Note that is it not necessary
to re-configure the library members unless you want to enable any new features. The
configurations which are already at the Network Sites will automatically be upgraded
to the new level during the IML process when LINCS detects that the configuration is
at a lower level than the System Microcode.
3. Build a NetView DM transmission plan to distribute the new System Microcode to the
desired Network Sites. If you reconfigured any of your library members, the transmission
plan should include statements to distribute the changed library members.
Downstream Load Microcode
Downstream Load Microcode is microcode required by downstream devices, in order for them
to work properly. An example is IBM’s 3290 display, which requires microcode from LINCS
when the display is powered on. Information about naming and managing this object are detailed
in the list below:
• Data Object Description - A Downstream Load (DSL) data object contains the microcode
necessary to load a single type of DSL device.
• Data Object Canonical Name - The DSL data object canonical name is built based upon
the type of device the DSL microcode supports. The following formats are supported.
• MCODE.9300.NA.FUNCTECT.rlvl.DSL.nnnn - This canonical name format is used to
distribute DSL microcode for a specific DSL device. The DSL device number (for
example, 1192) is specified in Token 7.
• MCODE.1174.NA.FEATURE.rlvl.DSL.nnnn.rpqnumbr - This canonical name indicates
a release of DSL microcode that contains RPQ microcode. The RPQ microcode contained
in the DSL microcode is identified by the RPQ number.
• Data Object Source - The DSL data object is provided on the DSL diskette that was received
when the DSL device was purchased. Prior to distributing the DSL Microcode, it must be
merged onto LINCS hard disk. The “Copy Disk” or “Copy Data Objects” utility in Media
Management may be used to copy the DSL microcode to the system hard disk.
• Data Object Destination - The destination of the DSL data object is a DSL disk at the
receiving LINCS node.
• Distributing the Data Object - Use the following steps to distribute the DSL microcode.
1. Merge the DSL microcode onto the hard disk of the Central Site node.
2. Build a NetView DM transmission plan to distribute the DSL data object.
Customization Data Objects
Customization data objects contain data which defines a particular feature. These data objects
are normally defined using customization utilities on the Customization Data Menu in Central
Control mode. The canonical names are built as follows:
• Token 1 must always be MCUST for Customization data objects.
• Token 2 is used to identify the project, such as 9300 or 1174.
• Token 3 is not used and must always be NA.