Visara LINCS Features - Manual (Page 125)

115
Chapter 10. Management Features
707021-001
• Token 4 is NA (not applicable) for all customization data objects except for Configuration
(CFG). For CFG data objects, token 4 is the Network ID defined during Configuration.
• Token 5 is NA (not applicable) for all customization data objects except for CFG. For CFG
data objects, token 5 is the CSCM LU Name defined during Configuration.
• Token 6 contains an acronym identifying the type of customization data.
• Token 7 varies depending upon the type of data object:
• For a CFG data object, token 7 is the name given to the library member when saving the
CFG using Central Site Customization. If the Configuration data object is modified using
the Configuration utility, token 7 contains LOCALCHG to indicate that a local change
has been performed.
• For other customization data objects, token 7 contains the ID given to the data object
when it was defined. The utilities for defining these data objects provide a field for
uniquely identifying the data.
• Token 8 is only used for the Configuration data object. It is the version number assigned to
the data object when it was saved using Central Site Customization. When Token 7 contains
LOCALCHG, Token 8 contains the 4-digit integration level of the System microcode used
to save the configuration.
Configuration Customization
The Configuration (CFG) data object contains the data that uniquely defines the operation of
a particular LINCS node. Information about naming and managing this object are detailed in
the list below:
• Data Object Canonical Name - The Configuration data object canonical name is built
using the NETID and LUNAME, which are defined during configuration. The library member
name and version number are defined by the Central Site Customization utility. The following
canonical name formats are supported for the Configuration Data object:
• MCUST.9300.NA.netid.luname.CFG.libmname.vernum - This canonical name identifies
a Configuration data object which has been defined using the Central Site Customization
utility.
• MCUST.1174.NA netid.luname.CFG.LOCALCHG.il - This canonical name identifies
a Configuration Data object, that has been changed locally using the Configuration Utility.
Token 7 is set to LOCALCHG to indicate that the data object no longer matches the
Configuration stored in the Resource Repository. Token 8 is the Integration Level of the
System Microcode used to save the configuration data.
• Data Object Source - The Configuration data object for Network Sites is usually created
using the Central Site Customization utility, although any LINCS node can reconfigure
using the Configuration utility.
The CFG data object is retrieved from a Library disk at the Central Site node by default. If
the CFG is not found on a library disk of the source node, LINCS will search the System
disk for the CFG.
• Data Object Destination - The destination of the CFG data object is a System disk installed
at the receiving node.
• Distributing the Data Object - The Configuration data object should be distributed when
the administrator of the Central Site node makes a Configuration Change for a Network