|
|
|
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
-> 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.
| Path: NMMGRpath — A read error encountered while reading the data
record (bad file). (DTSERR=3) |
Level: (DTSERR 3)
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. |
| Path: NMMGRpath — A write error encountered while updating the data
record (bad file). (DTSERR=4) |
Level: (DTSERR 4)
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. |
| Path: NMMGRpath — The data record is empty (use Update Data function
key). (DTSERR=5) |
Level: (DTSERR 5)
Cause: The data record was not created for the NMMGRpath.
Action: Go back to the screen specified by the NMMGRpath
and update the screen. |
| Path: NMMGRpath — The same physical path is being used at
LINK.linkname. (DTSERR=6) |
Level: (DTSERR 6)
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. |
| Path: NMMGRpath — The same station address is being used at
LINK.linkname. (DTSERR=7) |
Level: (DTSERR 7)
Cause: The IEEE 802.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. |
| Path: NMMGRpath — LINK.linkname is not defined. (DTSERR=8) |
Level: (DTSERR 8)
Cause: The linkname specified on the DTS 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 DTS
Configuration screen. |
| Path: NMMGRpath — DTS.PROFPC.profilename is not defined.
(DTSERR=9) |
Level: (DTSERR 9)
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. |
| Path: NMMGRpath — The same station address or node name is being
used at DTS.DTC.SELECT.DTCname. (DTSERR=10) |
Level: (DTSERR 10)
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 screen.
Action: Go to the screen specified by the NMMGRpath or to
the screen specified by the DTC name and modify the station address
or node name. |
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012. (DTSERR=11) |
Level: (DTSERR 11)
Cause: The logical device (ldev) number is being used on the
screen specified by the NMMGRpath and on the
DTS.DTC.SELECT.DTCname.CARD012 screen.
Action: Go to one of the two screens and change the ldev number.
The ldev number must be unique for each port. |
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345. (DTSERR=12) |
Level: (DTSERR 12)
Cause: The same logical device (ldev) number is being used on the
screen specified by the NMMGRpath and on the
DTS.DTC.SELECT.DTCname.CARD345.
Action: Go to one of the two screens and change the ldev number.
The ldev number must be unique for each port. |
| Path: NMMGRpath — LDEV #nnn is too big (must be <=4679).
(DTSERR=14) |
Level: (DTSERR 14)
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. |
| Path: NMMGRpath — Too many LDEVs are being used (must be <=4649).
(DTSERR=15) |
Level: (DTSERR 15)
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. |
| Path: NMMGRpath — Defined LINK.linkname is not being used.
(DTSWARN=17) |
Level: (DTSWARN 17)
Cause: The defined linkname is not used by DTS or the
network interface.
Action: This is a warning only. No action is required. |
| Path: NMMGRpath — Too many links are being used (max. number allowed
= 8). (DTSERR=18) |
Level: (DTSERR 18)
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. |
| Path: NMMGRpath — Too many paths are being used (max. number allowed
= 8). (DTSERR=19) |
Level: (DTSERR 19)
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 links are being used. |
| Path: NMMGRpath — Too many DTCs are being used (max. number allowed
= 120). (DTSERR=20) |
Level: (DTSERR 20)
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. |
| Path: NMMGRpath — Too many nodes are being used (max. number allowed
= 129). (DTSERR=21) |
Level: (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) |
Level: (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) |
Level: (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) |
Level: (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) |
Level: (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) |
Level: (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) |
Level: (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.
Action: Remove the class name from the profile for the ldev and
delete and re- add the ldev. Cross-validate the NMCONFIG.PUB.SYS
file with SYSGEN. Correct any problems found then restart DTS. |
| Path: NMMGRpath — Must supply a Physical Path. (DTSERR=32) |
Level: (DTSERR 32)
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. |
| Path: NMMGRpath — Duplicate profile class name profilename used.
(DTSWARN=34) |
Level: (DTSWARN 34)
Cause: The same class name is used in several terminal profiles
or the same class name is used in several printer profiles.
Action: No action is required. Informational message only.
|
| Path: NMMGRpath — Class name duplicated between printer and terminal
profiles. (DTSERR=35) |
Level: (DTSERR 35)
Cause: The same class name is used for both a terminal profile
and a printer profile.
Action: Remove the duplicate class name from the terminal profile
or the printer profile. |
| Path: NMMGRpath — Profile profilename specified for non-nailed
terminals is of PRINTER type. (DTSERR=36) |
Level: (DTSERR 36)
Cause: A printer profile is specified where only a terminal
profile is allowed.
Action: Change the printer profile to be a terminal
profile. |
| Path: NMMGRpath — Profile profilename specified for non-nailed PAD
terminals is of PRINTER type. (DTSERR=37) |
Level: (DTSERR 37)
Cause: A printer profile is specified where only a terminal
profile is allowed.
Action: Change the printer profile to be a terminal profile.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012.PAD0. (DTSERR=38) |
Level: (DTSERR 38)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012.PAD1. (DTSERR=39) |
Level: (DTSERR 39)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012.PAD2. (DTSERR=40) |
Level: (DTSERR 40)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345.PAD3. (DTSERR=41) |
Level: (DTSERR 41)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345.PAD4. (DTSERR=42) |
Level: (DTSERR 42)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345.PAD5. (DTSERR=43) |
Level: (DTSERR 43)
Cause: A PAD name is used more than once.
Action: Remove all of the duplicate references to the PAD name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012.PAD0. (DTSERR=44) |
Level: (DTSERR 44)
Cause: The same logical device (ldev) number is used more than
once.
Action: Remove the duplicate ldev number. |
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012.PAD1. (DTSERR=45) |
Level: (DTSERR 45)
Cause: The same logical device (ldev) number is used more than
once.
Action: Remove the duplicate ldev number. |
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012.PAD2. (DTSERR=46) |
Level: (DTSERR 46)
Cause: The same logical device (ldev) number is used more than
once.
Action: Remove the duplicate ldev number. |
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345.PAD3. (DTSERR=47) |
Level: (DTSERR 47)
Cause: The same logical device (ldev) number is used more than
once.
Action: Remove the duplicate ldev number. |
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345.PAD4. (DTSERR=48) |
Level: (DTSERR 48)
Cause: The same logical device (ldev) number is used more than
once.
Action: Remove the duplicate ldev number. |
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345.PAD5. (DTSERR=49) |
Level: (DTSERR 49)
Cause: The same logical device (ldev) number is used more than
once.
Action: Remove the duplicate ldev number. |
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD012. (DTSERR=50) |
Level: (DTSERR 50)
Cause: The logical device (ldev) number is used more than once in
the CARD012 configuration.
Action: Remove any duplicate references to the ldev number.
|
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.DTCname.CARD345. (DTSERR=51) |
Level: (DTSERR 51)
Cause: The logical device (ldev) number is used more than once in
the CARD345 configuration.
Action: Remove any duplicate references to the ldev number.
|
| Path: NMMGRpath — The same node name is being used at linkname.
(DTSERR=52) |
Level: (DTSERR 52)
Cause: The same node name is used more than once.
Action: Remove the duplicate reference to the node name. |
| Path: NMMGRpath — Blank NODENAME. (DTSERR=53) |
Level: (DTSERR 53)
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. |
| Path: NMMGRpath — The profile for LDEV #nnn, profilename, is not
defined. (DTSERR=54) |
Level: (DTSERR 54)
Cause: An incorrect profile name was used for the logical device
(ldev).
Action: Verify the profile name for the logical device in the DTS
Profile Selection screen. |
| Path: NMMGRpath — Profile profilename specified for non-nailed PAD
terminals is of PRINTER or PADPRINT type. (DTSERR=57) |
Level: (DTSERR 57)
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.
|
| Path: NMMGRpath — The profile for LDEV #nnn, profilename, is of
PADTERM or PADPRINT type. (DTSERR=58) |
Level: (DTSERR 58)
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. |
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012.PAD0. (DTSERR=59) |
Level: (DTSERR 59)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012.PAD1. (DTSERR=60) |
Level: (DTSERR 60)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012.PAD2. (DTSERR=61) |
Level: (DTSERR 61)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345.PAD3. (DTSERR=62) |
Level: (DTSERR 62)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345.PAD4. (DTSERR=63) |
Level: (DTSERR 63)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
|
| Path: NMMGRpath — PAD device name for LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345.PAD5. (DTSERR=64) |
Level: (DTSERR 64)
Cause: The same PAD device name is used more than once in the
configuration.
Action: Remove any duplicate references to the PAD device name.
|
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012.PAD0. (DTSERR=65) |
Level: (DTSERR 65)
Cause: The logical device (ldev) number is used more than once in
the configuration.
Action: Remove any duplicate references to the ldev number.
|
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012.PAD1. (DTSERR=66) |
Level: (DTSERR 66)
Cause: The logical device (ldev) number is used more than once in
the configuration.
Action: Remove any duplicate references to the ldev number.
|
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD012.PAD2. (DTSERR=67) |
Level: (DTSERR 67)
Cause: The logical device (ldev) number is used more than once in
the configuration.
Action: Remove any duplicate references to the ldev number.
|
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345.PAD3. (DTSERR=68) |
Level: (DTSERR 68)
Cause: The logical device (ldev) number is used more than once in
the configuration.
Action: Remove any duplicate references to the ldev number.
|
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345.PAD4. (DTSERR=69) |
Level: (DTSERR 69)
Cause: The logical device (ldev) number is used more than once in
the configuration.
Action: Remove any duplicate references to the ldev number.
|
| Path: NMMGRpath — The same LDEV #nnn is being used at
DTS.DTC.SELECT.DTCname.CARD345.PAD5. (DTSERR=70) |
Level: (DTSERR 70)
Cause: The logical device (ldev) number is used more than once in
the configuration.
Action: Remove any duplicate references to the ldev number.
|
| Path: NMMGRpath — Modem behavior DCE high for LDEV #nnn, defined in
Profile profilename, is not supported on DTC16 and DTC48. (DTSERR=71)
|
Level: (DTSERR 71)
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. |
| Path: NMMGRpath — Hardware handshaking for LDEV #nnn, defined in
Profile profilename, is not supported on DTC16 and DTC48.
(DTSERR=72) |
Level: (DTSERR 72)
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.
|
| Path: NMMGRpath — Modem behavior is not supported.
(DTSERR=73) |
Level: (DTSERR 73)
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. |
| Path: NMMGRpath — Invalid AFCP timer selection. (DTSERR=74) |
Level: (DTSERR 74)
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. |
| Path: NMMGRpath — Invalid Management timer selection.
(DTSERR=75) |
Level: (DTSERR 75)
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. |
| Path: NMMGRpath — Baud rate 38400 for LDEV #nnn, defined in Profile
profilename, is not supported on DTC16 and DTC48. (DTSERR=76) |
Level: (DTSERR 76)
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. |
| Internal error. Failed to get memory. (DTSERR=77) |
Level: (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. |
| Path: NMMGRpath — Back-to-Back, currently configured on LDEV #nnn,
must use LDEV # -1. (DTSERR=78) |
Level: (DTSERR 78)
Cause: A profile of type HOST has been configured on a
DTC port and the ldev specified is not -l.
Action: Ports using HOST profiles are for back-to-back
and must have an ldev of -l. Go to the screen specified in NMMGRpath
and change the ldev to -l or use a different profile that is not of type
HOST. |
| Path: NMMGRpath — X.25 card is not allowed in slot s.
(DTSERR=79) |
Level: (DTSERR 79)
Cause: An X.25 card has been configured in a slot that is not
allowed for the DTC type.
Action: Go to the DTC specified in the NMMGRpath and
delete the X.25 card from the slot number s. |
| Path: NMMGRpath — Too many X.25 cards are configured. Maximum is 3.
(DTSERR=80) |
Level: (DTSERR 80)
Cause: To many X.25 cards have been configured in the DTC
specified in NMMGRpath.
Action: Go to the DTC specified in the NMMGRpath and
delete one or more X.25 cards. |
| Path: NMMGRpath — LAN cardtype is not allowed on DTC16 or DTC48.
(DTSERR=81) |
Level: (DTSERR 81)
Cause: The configuration for the DTC specified in NMMGRpath
has a cardtype of "L" configured. This is not allowed for DTC16 or DTC48.
Action: Go to the DTC Configuration screen specified in
NMMGRpath and enter the correct cardtypes. |
| Path: NMMGRpath — Too many LAN cards configured. Only one is allowed.
(DTSERR=82) |
Level: (DTSERR 82)
Cause: The configuration for the DTC specified in NMMGRpath
has more than one LAN card specified in the cardtypes.
Action: Go to the DTC Configuration screen specified in
NMMGRpath and change the extra "L" cardtypes to another valid type.
|
| Path: NMMGRpath — Unknown cardtype specified for card c.
(DTSERR=83) |
Level: (DTSERR 83)
Cause: The configuration for the DTC specified in NMMGRpath
has been corrupted.
Action: Delete the DTC specified in NMMGRpath and re-enter
the data for this DTC. |
| Path: NMMGRpath — Cardtype for card c does not match DTC card
configuration. (DTSERR=84) |
Level: (DTSERR 84)
Cause: The configuration for the DTC specified in NMMGRpath
has been corrupted.
Action: Delete the DTC specified in NMMGRpath and re-enter
the data for this DTC. |
| Path: NMMGRpath — Cardtype configured on card c not allowed on
dtctype. (DTSERR=85) |
Level: (DTSERR 85)
Cause: The configuration for the DTC specified in NMMGRpath
has been corrupted.
Action: Delete the DTC specified in NMMGRpath and re-enter
the data for this DTC. |
| Path: NMMGRpath — Ldev #nnn> is not valid (must be >= -l and
<=4679). (DTSERR=86) |
Level: (DTSERR 86)
Cause: The logical device (ldev) number is outside the allowed
range.
Action: Go to the screen specified in NMMGRpath and modify
the ldev number. |
| Path: NMMGRpath — Ldev of -l is not allowed with printer or terminal
profile. (DTSERR=87) |
Level: (DTSERR 87)
Cause: An ldev number of -l has been specified on a port that has
a profile configured that is of type terminal or printer.
Action: Go to the screen specified in NMMGRpath and change
the ldev or specify a profile that is a type HOST. |
| Path: NMMGRpath — Profile for ldev #nnn, <profname>, is of
HOST type. (DTSERR=88) |
Level: (DTSERR 88)
Cause: Profile <profname> is of type HOST and has
been configured on a DTC port where ldev specified is not -l.
Action: Ports using HOST profiles are for back-to-back
and must have an ldev of -l. Go to the screen specified in NMMGRpath
and change the ldev to -l or use a different profile that is not of type
HOST. |
| Path: NMMGRpath — Too few non-nailed ldevs available above TIO start
ldev. (DTSERR=89) |
Level: (DTSERR 89)
Cause: There are not enough ldevs available above the TIO start
ldev number to configure the number of ldev specified.
Action: Lower the number of TIO non-nailed ldevs or delete all
TIO non-nailed ldevs and specify a lower starting ldev number. Then add
the desired number of ldevs. |
| Path: NMMGRpath — Too few non-nailed ldevs available above PAD start
ldev. (DTSERR=90) |
Level: (DTSERR 90)
Cause: There are not enough ldevs available above the PAD start
ldev number to configure the number of ldev specified.
Action: Lower the number of PAD non-nailed ldevs or delete all
PAD non-nailed ldevs and specify a lower starting ldev number. Then add
the desired number of ldevs. |
|
