Configuring and Managing Host-Based X.25 Links - Edition 5 (36939-90054)

Appendix A 163
Error Messages
Validation Error Messages
Path: NMMGRpath — Too many nodes are being used (max. number
allowed = 129). (DTSERR=21)
(DTSERR 21) Cause: The DTC specified in the NMMGRpath cannot be processed.
Too many nodes are being used.
Action: Go back to the DTC Configuration screen and delete the DTC
specified in the NMMGRpath.
Path: NMMGRpath Too many classes are being used (max. number
allowed = 1000). (DTSERR=22)
(DTSERR 22) Cause: The total number of classes exceeds the maximum allowed
number.
Action: Delete class names so that no more than 1000 different class
names are associated with asynchronous devices.
Path: NMMGRpath Too many profiles are being used (max. number
allowed = 1024). (DTSERR=23)
(DTSERR 23) Cause: The total number of defined profiles exceeds the maximum
allowed.
Action: Delete profiles so that no more than 1024 are specified.
No link is defined. (DTSWARN=24)
(DTSWARN 24) Cause: A link is not configured.
Action: Without a configured link, the network management
configuration file is useless. Return to the configuration screens and
add a link, making sure that all necessary data records are created.
No DTC is defined. (DTSWARN=25)
(DTSWARN 25) Cause: A DTC is not configured.
Action: An action is not required if neither terminals, printers, nor
both are needed. If terminals and printers are required, return to the
configuration screens and add a DTC, making sure that all necessary
data records are created.
Path: NMMGRpath LINK.linkname is shared with network interface.
(DTSWARN=26)
(DTSWARN 26) Cause: The same link is shared between the DTS and NS subsystem.
A separate link must exist for each of the two subsystems.
Action: Decide which of the two subsystems should use the existing
link and configure an additional link for the remaining subsystem.
Path: NMMGRpath — Modem type not supported. (DTSERR=30)
(DTSERR 30) Cause: The modem type specified on the DTS Terminal Profile screen
is not 0, 1, or 2. A problem occurred while adding the ldev to a device
class. This could be caused because the class is used by a different type
of device such as a HPIB printer.