 |
» |
|
|
|
|  | |
The network management configuration file must be validated before it can be processed by SYSGEN. The validation procedure is invoked in NMMGR by requesting it on the VALIDATE CONFIGURATION FILE screen. Error messages will be displayed on the system console. Additionally, error messages can be directed to a printer.
The DTS validation procedure starts by displaying the following on the
system console: 197 - Validation of DTS/LINK started. - Errors are then listed to the console. When the validation procedure is complete, it will print the following on the system console: nnn Encountered Errors - 1
- MESSAGE
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.
- 2
- MESSAGE
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.
- 3
- MESSAGE
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, update the screen, and press Update Data.
- 4
- MESSAGE
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 to the link screen specified by the NMMGRpath or go to the link screen specified by the linkname, and modify the physical path.
- 5
- MESSAGE
Path: NMMGRpath The same station address is being used at LINK.linkname. (DTSERR=5)
- 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 modify the station address.
- 6
- MESSAGE
Path: NMMGRpath LINK.linkname is not defined. (DTSERR=6)
- CAUSE
The link name specified on the DTS DATACOMM & TERMINAL CONTROLLER CONFIGURATION screen is not defined; therefore, the link data record was not created.
- ACTION
Verify the link name on the DTS DATACOMM & TERMINAL CONTROLLER CONFIGURATION screen. Check that the link name exists on the LINK SELECTION screen and if it does, check that the link data record was created. If the link data record does not exist, update the LINK SELECTION screen and press Update Data.
- 7
- MESSAGE
Path: NMMGRpath DTS.PROFILE.linkname is not defined. (DTSERR=7)
- CAUSE
The linkname 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 DISTRIBUTED TERMINAL SUBSYSTEM PROFILE SELECTION screen and if it does, check that the data record for this profile was created. If the profile data record was not created, then update the linkname screen and press Update Data.
- 8
- MESSAGE
Path: NMMGRpath The same station address or node name is being used at DTS.DTC.
SELECT.linkname. (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 DTS.DTC.SELECT.linkname screen.
- ACTION
Go to the screen specified by the NMMGRpath or to the screen specified by the linkname and modify the station address or node name.
- 9
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTC.SELECT.linkname.CARD012. (DTSERR=9)
- CAUSE
The logical device (ldev) number is being used on the screen specified by the
NMMGRpath and on the DTS.DTC.SELECT.linkname.CARD012 screen.
- ACTION
Go to one of the two screens and change the ldev number. The ldev number must be unique for each port.
- 10
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTC.SELECT.linkname.CARD345. (DTSERR=10)
- CAUSE
The same logical device (ldev) number is being used on the screen specified by
the NMMGRpath and on the DTS.DTC.SELECT.linkname.CARD345 screen.
- ACTION
Go to one of the two screens and change the ldev number. The ldev number must be unique for each port.
- 12
- MESSAGE
Path: NMMGRpath LDEV #nnn is too big (must be ≤999). (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.
- 13
- MESSAGE
Path: NMMGRpath Too many LDEVs are being used (must be ≤600). (DTSERR=13)
- CAUSE
Too many logical device (ldev) numbers are being used.
- ACTION
Visit the screens that use ldevs and delete some ldev numbers. The validation procedure allows a total of 600 ldevs.
- 15
- MESSAGE
Path: NMMGRpath Defined LINK. linkname is not being used. (DTSWARN15)
- CAUSE
The defined linkname is not used by DTS or the network interface.
- ACTION
This is a warning only. No action is required.
- 16
- MESSAGE
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 LINK SELECTION screen and delete the link specified in the NMMGRpath. Delete all unused links so that eight or less links are being used.
- 17
- MESSAGE
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 LINK SELECTION screen and delete the link specified in the NMMGRpath. Delete all unused links so that eight or less links are being used.
- 18
- MESSAGE
Path: NMMGRpath Too many DTCs are being used (max. number allowed = 24). (DTSERR=18)
- CAUSE
The DTC specified in the NMMGRpath cannot be processed. Too many DTCs are already configured.
- ACTION
Go back to the DTC SELECTION screen and delete the DTC specified in the NMMGRpath.
- 19
- MESSAGE
Path: NMMGRpath Too many nodes are being used (max. number allowed = 33). (DTSERR=19)
- CAUSE
The DTC specified in the NMMGRpath cannot be processed. Too many nodes are being used.
- ACTION
Go to the DTC SELECTION screen and delete the DTC specified in the NMMGRpath.
- 20
- MESSAGE
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.
- 21
- MESSAGE
Path: NMMGRpath Too many profiles are being used (max. number allowed = 100). (DTSERR=21)
- CAUSE
The total number of defined profiles exceeds the maximum allowed.
- ACTION
Delete profiles so that no more than 100 are specified.
- 22
- MESSAGE
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.
- 23
- MESSAGE
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.
- 24
- MESSAGE
Path: NMMGRpath LINK.linkname is shared with network interface. (DTSWARN=24)
- CAUSE
The same link is shared between the DTS and the 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.
- 25
- MESSAGE
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. Press Update Data.
- 27
- MESSAGE
Path: NMMGRpath Must supply a physical path. (DTSERR=27)
- CAUSE
A physical path was not specified in the Physical Path IEEE 802.3 Device Adapter field.
- ACTION
Go the IEEE 802.3 LINK CONFIGURATION screen and enter the appropriate physical path. Press Update Data.
- 28
- MESSAGE
Path: NMMGRpath Duplicate profile class name linkname used. (DTSWARN=28)
- CAUSE
The same class name is used in a terminal profile or a printer profile.
- ACTION
Remove the duplicate class name from the printer profile or the terminal profile.
- 29
- MESSAGE
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 the terminal profile or the printer profile.
- 30
- MESSAGE
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 printer profile to be a terminal profile.
- 31
- MESSAGE
Path: NMMGRpath Profile linkname 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 printer profile to be a terminal profile.
- 32
- MESSAGE
Path: NMMGRpath PAD device name for LDev #nnn is being used at DTS.DTCPC.SELECT.linkname.CARD012.PAD0. (DTSERR=32)
- CAUSE
A PAD name is used more than once.
- ACTION
Remove all of the duplicate references to the PAD name.
- 33
- MESSAGE
Path: NMMGRpath PAD device name for LDev #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD012.PAD1. (DTSERR=33)
- CAUSE
A PAD name is used more than once.
- ACTION
Remove all of the duplicate references to the PAD name.
- 34
- MESSAGE
Path: NMMGRpath PAD device name for LDev #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD012.PAD2. (DTSERR=34)
- CAUSE
A PAD name is used more than once.
- ACTION
Remove all of the duplicate references to the PAD name.
- 35
- MESSAGE
Path: NMMGRpath PAD device name for LDev #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD345.PAD3. (DTSERR=35)
- CAUSE
A PAD name is used more than once.
- ACTION
Remove all of the duplicate references to the PAD name.
- 36
- MESSAGE
Path: NMMGRpath PAD device name for LDev #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD345.PAD4. (DTSERR=36)
- CAUSE
A PAD name is used more than once.
- ACTION
Remove all of the duplicate references to the PAD name.
- 37
- MESSAGE
Path: NMMGRpath PAD device name for LDev #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD345.PAD5. (DTSERR=37)
- CAUSE
A PAD name is used more than once.
- ACTION
Remove all of the duplicate references to the PAD name.
- 38
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTCPC.SELECT.linkname.CARD 012.PAD0. (DTSERR=38)
- CAUSE
The same logical device (ldev) number is used more than once.
- ACTION
Remove the duplicate ldev number.
- 39
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD012.PAD1. (DTSERR=39)
- CAUSE
The same logical device (ldev) number is used more than once.
- ACTION
Remove the duplicate ldev number.
- 40
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD012.PAD2. (DTSERR=40)
- CAUSE
The same logical device (ldev) number is used more than once.
- ACTION
Remove the duplicate ldev number.
- 41
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD345.PAD3. (DTSERR=41)
- CAUSE
The same logical device number (ldev) is used more than once.
- ACTION
Remove the duplicate ldev number.
- 42
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD345.PAD4. (DTSERR=42)
- CAUSE
The same logical device (ldev) number is used more than once.
- ACTION
Remove the duplicate ldev number.
- 43
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTCPC.SELECT.linkname .CARD345.PAD5. (DTSERR=43)
- CAUSE
The same logical device (ldev) number is used more than once.
- ACTION
Remove duplicate ldev number.
- 44
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTCPC.SELECT.linkname .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.
- 45
- MESSAGE
Path: NMMGRpath The same LDEV #nnn is being used at DTS.DTCPC.SELECT.linkname .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.
- 46
- MESSAGE
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.
- 47
- MESSAGE
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.
|
