Visara LINCS Features User Manual

Page 126

116

LINCS Features

707021-001

node. The System Microcode at the Network Node must be at a level equal to or greater
than the changed Configuration data.

Use the following steps to upgrade the Configuration for a Network Site:

Modify the library member as desired, using the Central Site Customization utility.

Build a NetView DM transmission plan to distribute the updated library member to the
Network Site. If the System Microcode at the Network Site is at a lower level than the
System Microcode at the Central Site, the transmission plan should also include
statements to distribute the System Microcode.

APPN Class of Service Customization

The Class of Service (COS) Customization data object provides flexibility for session
characteristics and route selection in an APPN network. If not defined, LINCS will provide a
default COS data object to be used for APPN route selection. Information about naming and
managing this object are detailed in the list below:

• Data Object Canonical Name - The COS data object canonical name is built based on the

Data Object Name assigned when saving the COS data object. It has the following format:

MCUST.9300.NA.NA.NA.COS.dobjname - It is recommended that a meaningful data
object name be defined, especially for networks in which multiple versions of the COS
data object will be used.

• Data Object Source - This data object is defined and saved to the System disk using the

APPN COS utility, which is on the Customization Data Menu in Central Control Mode.

• Data Object Destination - The destination of the COS data object is a System disk at the

receiving node.

• Distributing the Data Object - Use the following steps to distribute the COS data object

to other LINCS nodes.

Use the Display/Update APPN COS utility to define a COS data object and save it to
the System disk. Identify the data object by assigning a unique data object ID.

Build a NetView DM transmission plan to distribute the COS data object to the desired
Network nodes.

If any Network nodes require a different COS, redefine the COS at the Central Site
and build a NetView DM transmission plan to distribute the modified COS to the
desired Network nodes. If desired, you may save the original COS to a floppy using
the “Copy Data Objects” utility prior to redefining it.

Keyboard Definition Utility Customization

The Keyboard Definition Utility (KDU) Customization data object redefines the default
keyboard table layouts for coax devices. If the keyboard tables are not redefined, the standard
keyboard table layouts are used. The Keyboard Definition Utility (KDU) is available from the
Customization Data Menu in Central Control Mode. Information about naming and managing
this object are detailed in the list below:

• Data Object Canonical Name - The KDU data object canonical name is built using the

Data Object Name assigned when saving the KDU data object. It has the following format:

MCUST.1174.NA.NA.NA.KDU.dobjname - We recommend you use a meaningful data
object name, especially for networks in which multiple versions of the KDU data object
will be used.