Visara LINCS Features User Manual
Page 127
117
Chapter 10. Management Features
707021-001
• Data Object Source - This data object is defined and saved on the System disk using the
Keyboard Definition Utility.
• Data Object Destination - The destination of the KDU data object is a System disk at the
receiving node.
• Distributing the Data Object - Use the following steps to distribute the KDU data object
to other LINCS nodes:
1.
Use the “Display/Update Keyboard Definition utility to define a KDU data object,
and save it to the System disk. Identify the data object by assigning a unique data
object ID.
2.
Build a NetView DM transmission plan to distribute the KDU data object to the desired
Network nodes.
3.
If any Network nodes require a different KDU, redefine the KDU at the Central Site
and build a NetView DM transmission plan to distribute the modified KDU to the
desired Network nodes. If desired, you may save the original KDU to a floppy using
the “Copy Data Objects” utility prior to redefining it.
ASCII Definition Utility Customization
The ASCII Definition Utility (ADU) Customization data object is used to modify the default
keyboard and translate table layouts for ASCII devices and ASCII host sessions. The ADU 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 ADU data object canonical name is built based on the
Data Object Name assigned when saving the ADU data object. It has the following format:
MCUST.1174.NA.NA.NA.ADU.dobjname - It is recommended that a meaningful data
object name be defined, especially for networks in which multiple versions of the ADU
data object will be used.
• Data Object Source - This data object is defined and saved on system disk using the ASCII
Definition Utility.
• Data Object Destination - The destination of the ADU data object is a System disk at the
receiving node.
• Distributing the Data Object - Use the following steps to distribute the ADU data object to
other LINCS nodes.
1.
Use the “Display/Update ASCII Definition utility to define an ADU data object
and save it to the System disk. Identify the data object by assigning a unique data
object ID.
2.
Build a NetView DM transmission plan to distribute the ADU data object to the desired
Network nodes.
3.
If any Network nodes require a different ADU, redefine the ADU at the Central Site
and build a NetView DM transmission plan to distribute the modified ADU to the
desired Network nodes. If desired, you may save the original ADU to a floppy using
the “Copy Data Objects” utility prior to redefining it.
Translate Table Utility Customization
The Translate Table Utility (TTU) Customization data object is used to modify the translate
tables for 3270 host sessions. The Translate Table utility is available on the Customization