Configuring and Managing Host-Based X.25 Links - Edition 6 (36939-90057)

Error Messages
Host Migration Tool Status Messages
Appendix B
216
MSG 152 Cannot copy DTC <DTCname> from PC-Based to Host based. Duplicate DTC name.
Cause:The Host Migration tool found a DTC in the Host-Based tree that has the same
DTC name as the DTC in the PC-Based tree, but with a different DTC Node Name. The
DTC node name of the DTC in the PC-based configuration was not found in the
Host-based configuration so the Host migration tool was attempting to create a
non-managed DTC in the Host-based configuration.
Action: Run NMMGR and rename the DTC in the Host-based tree to a different name and
re-run the Host Migration tool with the command: NMMGRVER;parm=77.
MSG 153 Host Based device type does not match PC-Based device type in
DTC <DTCname>, card x for port yy
Cause:The port type of the TIO devices in the Host-based configuration does not match
the port type of the TIO device in the PC based configuration, i.e., terminal/printer/host
type. The TIO device will be assigned ldev of (-1).
Action: Run NMMGR to examine and enter the correct ldev in the configuration for
specified port in the DTC with the listed DTC Name in the Host-based configuration.
MSG 154 No ldev was found for printer in <dtcname>, card x or Port yy
Cause: The Host Migration tool found a printer device in the Host-based configuration
but the corresponding port doesn't have an ldev assigned in the PC-Based configuration.
The printer port will be assigned ldev of (-1). This is an invalid ldev number for TIO
printers and will be detected by Validation.
Action: Run NMMGR and change the printer ldev to a valid ldev number in the
Host-based configuration.
MSG 155 No ldev was found for PAD device name <PAD name> in DTC <dtcname>, card x.
Cause: A PAD device with the displayed name is defined on a X.25 card in the PC-Based
DTC configuration that is not defined in the Host-Based DTC, the PAD device in the
Host-Based configuration will be assigned ldev of (1). This is an invalid ldev numbers for
PAD devices and an error will be detected by Validation.
Action: Run NMMGR and change the PAD device ldev to a valid ldev number in the Host
Based tree.
MSG 157 No PAD device name was found for ldev xxx on DTC <dtcname>, card x.
Cause: A PAD device was configured on the PC-Based DTC that was not configured on
the matching DTC in the Host-Based configuration. The ldev will be copied to the
Host-based DTC but the PAD device will not have a valid X.25 address assigned. The
invalid X.25 address will be detected by Validation
Action: Run NMMGR and assign a valid X.25 address to the device or delete the device.
MSG 158 Host Based Device type does not match PC-Based device type in
DTC <DTCName>, card x for PAD name <PADName>.
Cause:The type of the PAD devices with the displayed PAD Name in the Host-based
configuration does not match the type of the PAD device in the PC based configuration,
i.e., padterm/padprint type. The PAD devices will be assigned ldev of (1). This is an
invalid ldev numbers for PAD devices and an error will be detected by Validation.
Action: Run NMMGR to examine and enter the correct ldev in the configuration for
specified PAD device in the DTC with the listed DTC Name in the Host-based
configuration.