Visara LINCS Features User Manual
Page 123
113
Chapter 10. Management Features
707021-001
• MAINTEC is used to identify a maintenance release of microcode. These releases are
done to correct specific customer problems. The microcode integration level (IL) is
incremented with each MAINTEC release.
• FEATURE is only valid for DSL microcode data objects. It is used to identify a feature
release of DSL microcode.
• Token 5 normally contains the microcode release level of a data object. It is a five character
field with the following format:
gffss where g indicates Generation level,
ff is a 2-digit functional release level, and
ss is a 2-digit suffix release level.
Example: C0300 indicates Generation C, Release 3.0.
• Token 6 identifies the type of microcode such as SYSTEM or DSL.
• Token 7 varies depending upon the type of data object as follows.
• For FUNCTEC levels of System Microcode, Token 7 is left blank.
• For MAINTEC levels of System Microcode, Token 7 is the integration level.
• For DSL microcode, Token 7 is the specific DSL device, such as 1192.
• Token 8 is only used for FEATURE DSL microcode. It contains the RPQ number of the
DSL feature.
The types of microcode data objects are listed and explained next.
System Microcode Data Objects
The System Microcode data object contains all the files necessary to load the LINCS node and
bring it on-line. You receive system microcode from MTX on diskette. Information about
naming and managing this object are detailed in the list below:
• Data Object Canonical Name - The System data object canonical name is based upon the
type of release and the integration level (il) of the System disk. The following canonical
name formats are supported.
• MCODE.9300.NA.FUNCTEC.rlvl.SYSTEM - This name refers to a new release of
system microcode.
• MCODE.9300.NA.MAINTEC.rlvl.SYSTEM.il - This canonical name refers to a
maintenance level of System microcode.
• Data Object Source - The System Microcode data object is provided on LINCS system
diskettes. The microcode can be copied to the hard disk using the Copy Data Object” utility
in Media Management or by using the software merge utility (accessible by pressing
• Data Object Destination - The destination of the System Microcode data object is a System
disk at the receiving LINCS node.
• Distributing the Data Object - Use the following steps to distribute a new level of System
Microcode to your LINCS nodes:
1.
Merge the new microcode onto the hard disk of the Central Site node, and IML with
the new microcode.