HP 3000 Manuals HP 3000 Manuals
Validation Error Messages
The network management configuration file must be validated before
automatic cross-validation with SYSGEN takes place.
The DTS validation procedure starts by displaying the following:
-> Validation of DTS/LINK started. <-
Errors are then listed. When the validation procedure is complete, it
will print the following:
nnn Encountered Errors
NOTE: In order for any TIO changes to take effect, you must reboot the
system.
-> Validation of DTS/LINK finished. <-
where nnn is the total number of errors found during validation.
A numerical list of validation error messages and actions for each
follows.
DTSERR 1 Path: NMMGRpath -- A read error encountered while reading the
data record (bad file). (DTSERR=1)
Cause: Either a hardware problem occurred or the data record is too
long.
Action: Try to print the network management configuration file. Rebuild
the file from a copy of the sample file NMSAMP1.PUB.SYS. If the problem
persists, contact your Hewlett-Packard support representative.
DTSERR 2 Path: NMMGRpath -- A write error encountered while updating
the data record (bad file). (DTSERR=2)
Cause: Either a hardware problem occurred or the data record file is too
small.
Action: If the data record file has been compressed, it is impossible to
validate the file. Go to the UTILITY screen and use the compression
utility to make the file larger. Try to validate the file. If it still
fails, build the file from a copy of the sample file NMSAMP1.PUB.SYS. If
the problem persists when verifying the new file, contact your
Hewlett-Packard support representative.
DTSERR 3 Path: NMMGRpath -- The data record is empty (use Update Data
function key). (DTSERR=3)
Cause: The data record was not created for the NMMGRpath.
Action: Go back to the screen specified by the NMMGRpath and update the
screen (press the Save Data key).
DTSERR 4 Path: NMMGRpath -- The same physical path is being used at
LINK.linkname. (DTSERR=4)
Cause: The physical path specified for this link is being used.
Action: Go back to the screen specified by the NMMGRpath or go to the
link screen specified by the linkname and modify the physical path.
DTSERR 5 Path: NMMGRpath -- The same station address is being used at
LINK.linkname. (DTSERR=5)
Cause: The IEEE802.3 station address is already used. Each station
address must be unique.
Action: Go back to the screen specified by the NMMGRpath or go to the
screen specified by the linkname and correct the station address.
DTSERR 6 Path: NMMGRpath -- LINK.linkname is not defined. (DTSERR=6)
Cause: The linkname specified on the Host Configuration screen is not
defined; therefore, the link data record was not created.
Action: Verify the linkname on the Host Configuration screen. If the
link data record does not exist, update the Host Configuration screen.
DTSERR 7 Path: NMMGRpath -- DTS.PROFILE.profilename is not defined.
(DTSERR=7)
Cause: The profilename on the screen specified by the NMMGRpath is not
defined; therefore, the profile data record does not exist.
Action: Check that the profile name exists on the DTS Profile Selection
screen and, if it does, check that the data record for this profile was
created.
DTSERR 8 Path: NMMGRpath -- The same station address or node name is
being used at DTS.DTC.SELECT.DTCname. (DTSERR=8)
Cause: The station address or node name used on the screen specified by
the NMMGRpath is also used on the screen specified by the path
DTS.DTC.SELECT.DTCname.
Action: Go to the screen specified by the NMMGRpath or to the screen
specified by the path DTS.DTC.SELECT.DTCname and modify the station
address or node name.
DTSERR 9 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012. (DTSERR=9)
Cause: The logical device (ldev) number nnn is being used on both the
screen specified by NMMGRpath and on one of the screens specified by the
path DTS.DTC.SELECT.DTCname.CARD012.
Action: Go to one of the screens and change the ldev number. The ldev
number must be unique for each port.
DTSERR 10 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345. (DTSERR=10)
Cause: The logical device (ldev) number nnn is being used on both the
screen specified by NMMGRpath and on one of the screens specified by the
path DTS.DTC.SELECT.DTCname.CARD345.
Action: Go to one of the screens and change the ldev number. The ldev
number must be unique for each port.
DTSERR 12 Path: NMMGRpath -- LDEV #nnn is too big (must be <=2330).
(DTSERR=12)
Cause: The logical device (ldev) number is bigger than the allowed
maximum ldev number.
Action: Go to the screen specified by the NMMGRpath and modify the ldev
number.
DTSERR 13 Path: NMMGRpath -- Too many LDEVs are being used (must be
<=4649). (DTSERR=13)
Cause: Too many logical device (ldev) numbers are being used.
Action: Review the screens that use ldevs and delete some ldev numbers.
The validation procedure allows a total of 4649 ldevs.
DTSERR 15 Path: NMMGRpath -- Defined LINK.linkname is not being used.
(DTSWARN=15)
Cause: The defined linkname is not used by DTS or the network interface.
Action: This is a warning only. No action is required.
DTSERR 16 Path: NMMGRpath -- Too many links are being used (max.
number allowed = 8). (DTSERR=16)
Cause: The link specified in the NMMGRpath cannot be processed. Too
many links are already defined.
Action: Go back to the DTS Configuration screen and delete the link
specified in the NMMGRpath. Delete all unused links so that eight or
less links are being used.
DTSERR 17 Path: NMMGRpath -- Too many paths are being used (max.
number allowed = 8). (DTSERR=17)
Cause: The link specified in the NMMGRpath cannot be processed. Too
many physical paths are already defined.
Action: Go back to the DTS Configuration screen and delete the link
specified in the NMMGRpath. Delete all unused links so that eight or
less physical paths are being used.
DTSERR 18 Path: NMMGRpath -- Too many DTCs are being used (max.
number allowed = 120). (DTSERR=18)
Cause: The DTC specified in the NMMGRpath cannot be processed. Too many
DTCs are already configured.
Action: Go back to the DTC Configuration screen and delete the DTC
specified in the NMMGRpath.
DTSERR 19 Path: NMMGRpath -- Too many nodes are being used (max.
number allowed = 129). (DTSERR=19)
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.
DTSERR 20 Path: NMMGRpath -- Too many classes are being used (max.
number allowed = 450). (DTSERR=20)
Cause: The total number of classes exceeds the maximum allowed number.
Action: Delete class names so that no more than 450 different class
names are associated with asynchronous devices.
DTSERR 21 Path: NMMGRpath -- Too many profiles are being used (max.
number allowed = 256). (DTSERR=21)
Cause: The total number of defined profiles exceeds the maximum allowed.
Action: Delete profiles so that no more than 256 are specified.
DTSERR 22 No link is defined. (DTSWARN=22)
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.
DTSERR 23 No DTC is defined. (DTSWARN=23)
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.
DTSERR 24 Path: NMMGRpath -- LINK.linkname is shared with network
interface. (DTSWARN=24)
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.
DTSERR 25 Path: NMMGRpath -- Modem type not supported. (DTSERR=25)
Cause: The modem type specified on the DTS Terminal Profile screen is
not 0, 1, or 2.
Action: Modify the modem type specified on the DTS Terminal Profile
screen to specify the appropriate modem type.
DTSERR 27 Path: NMMGRpath -- Must supply a physical path. (DTSERR=27)
Cause: A physical path was not specified in the Physical Path of LANIC
field.
Action: Go to the DTS Configuration screen and enter the appropriate
physical path.
DTSERR 28 Path: NMMGRpath -- Duplicate profile class name profilename
used. (DTSWARN=28)
Cause: The same class name is used in more than one terminal profile or
the same class name is used in more than one printer profile.
Action: No action is required. Informational message only.
DTSERR 29 Path: NMMGRpath -- Class name duplicated between printer and
terminal profiles. (DTSERR=29)
Cause: The same class name is used for both a terminal profile and a
printer profile.
Action: Remove the duplicate class name from either the terminal profile
or the printer profile.
DTSERR 30 Path: NMMGRpath -- Profile specified for non-nailed
terminals is of PRINTER type. (DTSERR=30)
Cause: A printer profile is specified where only a terminal profile is
allowed.
Action: Change the specified profile to a terminal profile.
DTSERR 31 Path: NMMGRpath -- Profile profilename specified for
non-nailed PAD terminals is of PRINTER type. (DTSERR=31)
Cause: A printer profile is specified where only a terminal profile is
allowed.
Action: Change the specified profile to a terminal profile.
DTSERR 32 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTCPC.SELECT.DTCname.CARD012.PAD0. (DTSERR=32)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
DTSERR 33 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTCPC.SELECT.DTCname.CARD012.PAD1. (DTSERR=33)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
DTSERR 34 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTCPC.SELECT.DTCname.CARD012.PAD2. (DTSERR=34)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
DTSERR 35 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTCPC.SELECT.DTCname.CARD345.PAD3. (DTSERR=35)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
DTSERR 36 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTCPC.SELECT.DTCname.CARD345.PAD4. (DTSERR=36)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
DTSERR 37 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTCPC.SELECT.DTCname.CARD345.PAD5. (DTSERR=37)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
DTSERR 38 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012.PAD0 (DTSERR=38)
Cause: The same logical device (ldev) number is used more than once.
Action: Remove the duplicate ldev number.
DTSERR 39 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012.PAD1 (DTSERR=39)
Cause: The same logical device (ldev) number is used more than once.
Action: Remove the duplicate ldev number.
DTSERR 40 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012.PAD2 (DTSERR=40)
Cause: The same logical device (ldev) number is used more than once.
Action: Remove the duplicate ldev number.
DTSERR 41 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345.PAD3 (DTSERR=41)
Cause: The same logical device (ldev) number is used more than once.
Action: Remove the duplicate ldev number.
DTSERR 42 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345.PAD4 (DTSERR=42)
Cause: The same logical device (ldev) number is used more than once.
Action: Remove the duplicate ldev number.
DTSERR 43 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345.PAD5 (DTSERR=43)
Cause: The same logical device (ldev) number is used more than once.
Action: Remove the duplicate ldev number.
DTSERR 44 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012. (DTSERR=44)
Cause: The logical device (ldev) number is used more than once in the
CARD012 configuration.
Action: Remove any duplicate references to the ldev number.
DTSERR 45 Path: NMMGRpath -- The same LADE #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345. (DTSERR=45)
Cause: The logical device (ldev) number is used more than once in the
CARD345 configuration.
Action: Remove any duplicate references to the ldev number.
DTSERR 46 Path: NMMGRpath -- The same node name is being used at
linkname. (DTSERR=46)
Cause: The same node name is used more than once.
Action: Remove the duplicate reference to the node name.
DTSERR 47 Path: NMMGRpath -- Blank node name. (DTSERR=47)
Cause: A host node name is not specified on the screen specified in the
path.
Action: Enter a host node name on the screen specified in the path.
DTSERR 48 Path: NMMGRpath -- The profile for LDEV #nnn, profilename,
is not defined. (DTSERR=48)
Cause: The profile specified for use with this ldev number on the card
configuration screen is not defined in the configuration file. Either
the profile name you entered on the card configuration screen is
incorrect or the profile specified is not defined.
Action: If the profile name is specified incorrectly, enter the correct
profile name at the card configuration screen on which the ldev is
specified. If the profile name is specified correctly but the profile is
not defined, then configure the profile using the profile configuration
screens. See chapter 4 for information on how to configure a terminal or
printer profile.
DTSERR 49 Path: NMMGRpath -- Too many logical devices are configured
using device class name devicename (max allowed num = 255).
(DTSERR=49)
Cause: Too many logical devices are configured under the specified
device class name. The maximum allowed is 255.
Action: Reduce the number of logical devices configured under the
specified device class name.
DTSERR 50 Path: NMMGRpath -- Profile profilename specified for
non-nailed PAD terminals is of PRINTER or PADPRINT type.
(DTSERR=50)
Cause: A printer or PAD printer profile is specified where only a
terminal or pad terminal profile is allowed.
Action: Change the printer profile to be a terminal profile.
DTSERR 51 Path: NMMGRpath -- The profile for LDEV #nnn, profilename,
is of PADTERM or PADPRINT type. (DTSERR=51)
Cause: A PAD terminal or PAD printer profile is specified where only a
terminal or printer profile is allowed.
Action: Change the PAD terminal or PAD printer profile to be a terminal
or printer profile.
DTSERR 52 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTC.SELECT.DTCname.CARD012.PAD0. (DTSERR=52)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
DTSERR 53 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTC.SELECT.DTCname.CARD012.PAD1. (DTSERR=53)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
DTSERR 54 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTC.SELECT.DTCname.CARD012.PAD2. (DTSERR=54)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
DTSERR 55 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTC.SELECT.DTCname.CARD345.PAD3. (DTSERR=55)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
DTSERR 56 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTC.SELECT.DTCname.CARD345.PAD4. (DTSERR=56)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
DTSERR 57 Path: NMMGRpath -- PAD device name for LDEV #nnn is being
used at DTS.DTC.SELECT.DTCname.CARD345.PAD5. (DTSERR=57)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
DTSERR 58 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012.PAD0. (DTSERR=58)
Cause: The logical device (ldev) number is used more than once in the
configuration.
Action: Remove any duplicate references to the ldev number.
DTSERR 59 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012.PAD1. (DTSERR=59)
Cause: The logical device (ldev) number is used more than once in the
configuration.
Action: Remove any duplicate references to the ldev number.
DTSERR 60 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012.PAD2. (DTSERR=60)
Cause: The logical device (ldev) number is used more than once in the
configuration.
Action: Remove any duplicate references to the ldev number.
DTSERR 61 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345.PAD3. (DTSERR=61)
Cause: The logical device (ldev) number is used more than once in the
configuration.
Action: Remove any duplicate references to the ldev number.
DTSERR 62 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345.PAD4. (DTSERR=62)
Cause: The logical device (ldev) number is used more than once in the
configuration.
Action: Remove any duplicate references to the ldev number.
DTSERR 63 Path: NMMGRpath -- The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345.PAD5. (DTSERR=63)
Cause: The logical device (ldev) number is used more than once in the
configuration.
Action: Remove any duplicate references to the ldev number.
DTSERR 64 Path: NMMGRpath -- Modem behavior DCE high for LDEV #nnn,
defined in Profile profilename, is not supported on DTC16 and
DTC48. (DTSERR=64)
Cause: DCE high modem behavior is not supported for devices on a DTC 16
or DTC 48. DCE high is being specified for LDEV #nnn, which is on a DTC
16 or DTC 48.
Action: Modify the modem behavior to one that is supported for the DTC,
or make sure you have specified the right DTC type (not a DTC 16 or DTC
48) for the device with LDEV #nnn.
DTSERR 65 Path: NMMGRpath -- Hardware handshaking for LDEV #nnn,
defined in Profile profilename, is not supported on DTC16 and
DTC48. (DTSERR=65)
Cause: Hardware handshaking is not supported for devices on a DTC 16 or
DTC 48. Hardware handshaking is being specified for LDEV #nnn, which is
on a DTC 16 or DTC 48.
Action: Make sure you have specified the right DTC type (not a DTC 16 or
DTC 48), or if you are configuring ports on a DTC 16 or DTC 48, do not
use a profile that specifies hardware handshaking.
DTSERR 66 Path: NMMGRpath -- Modem behavior is not supported.
(DTSERR=66)
Cause: An invalid modem behavior has been specified. Valid modem
behavior values are: 0, 1, 2, or 3. The configuration file may be
corrupt.
Action: Modify the modem behavior specified on the Terminal Profile or
Printer Profile screens to a valid value.
DTSERR 67 Path: NMMGRpath -- Invalid AFCP timer selection.
(DTSERR=67)
Cause: You have specified an invalid AFCP timer selection.
Action: Go to the Tune DTC -- Timer Selection Screen and choose a value
from 1 to 6 for an AFCP timer selection.
DTSERR 68 Path: NMMGRpath -- Invalid Management timer selection.
(DTSERR=68)
Cause: You have specified an invalid management timer selection.
Action: Go to the Tune DTC -- Timer Selection Screen and choose a value
of 1 or 2 for a management timer selection.
DTSERR 69 Path: NMMGRpath -- Baud rate 38400 for LDEV #nnn, defined in
Profile profilename, is not supported on DTC16 and DTC48.
(DTSERR=69)
Cause: You have used a profile that specified a baud rate of 38400 for a
device that is connected to a DTC 16 or DTC 48.
Action: Make sure you specified the right DTC type (not a DTC 16 or DTC
48), or do not use this profile for the port with LDEV #nnn.
DTSERR 77 Internal error. Failed to get memory. (DTSERR=77)
Cause: The operating system was unable to allocate the memory needed to
store data used during validation.
Action: Build a new file from the sample file NMSAMP1.PUB.SYS. Try to
validate the file. If the same error message appears when verifying the
new file, contact your Hewlett- Packard support representative.
In order for any TIO changes to take effect, you must reboot the
system.
Cause: This is just a warning message.
Action: After you make changes to your DTS TIO configuration, you must
reboot your HP 3000 system in order for the changes to take effect.