NMGR Error and Warning Messages

CAUSE: The user's terminal is not a block mode terminal supported by VPLUS/3000.

ACTION: Check the terminal type and strap settings.

CAUSE: The user is attempting to run NMMGR from a batch job. Batch operation is not supported.

ACTION: None.

CAUSE: A terminal I/O or internal VPLUS/3000 error occurred.

ACTION: Check the version of VPLUS/3000 and repeat VPLUS/3000 installation if necessary.

CAUSE: NMMGR was unable to open the forms file NMMGRF.PUB.SYS at program startup. The file NMMGRF.PUB.SYS is missing.

ACTION: See "Invalid Software Installation" at the beginning of this appendix.

CAUSE: A file equation exists for NMMGRF.PUB.SYS.

ACTION: Check for file equations using LISTEQ5.PUB.SYS and RESET if necessary.

CAUSE: File NMMGRF.PUB.SYS is not a valid VFAST or VFORM forms file, or it has become corrupted.

ACTION: Restore a back-up copy of NMMGRF.PUB.SYS.

CAUSE: An internal VPLUS/3000 error occurred.

ACTION: Check the version of VPLUS/3000 and repeat VPLUS/3000 installation if necessary.

CAUSE: The user entered a type name in the TYPE field of a typed-select screen that is not defined for this screen.

ACTION: Check the subsystem manual for correct type names and try again.

CAUSE: The user pressed an invalid function key (with a blank label), or pressed the [ENTER] in a screen without a command window (currently only the OPEN FILE screen).

ACTION: None.

CAUSE: The user typed an unrecognizable command in the command window and pressed [ENTER].

ACTION: Check the spelling of the command, and check the list of valid commands in your subsystem node management or configuration manual.

CAUSE: The user typed :EOF or :EOD in response to the prompt:

"Press Return when done viewing screen contents."

ACTION: This error is irrecoverable since the terminal is closed for further input. Run NMMGR again to continue configuration.

CAUSE: The user changed information on a data screen and pressed a key other than UPDATE. This warning prevents accidental exit from the screen without saving changes.

ACTION: The user may ignore the warning by pressing a key other than UPDATE, or may save changes by pressing UPDATE.

CAUSE: The user pressed the PREV PAGE or NEXT PAGE key in a selection screen when there are no items to be displayed on this select screen. Scrolling with these keys is only necessary when there are already items configured.

ACTION: None.

CAUSE: NMMGR has encountered an unexpected condition in the configuration file.

ACTION: Check the NMCONF error (if one is reported) for further information.

CAUSE: NMMGR has encountered an unexpected condition in the configuration file. Two or more users are updating the same configuration file concurrently, and one renames or deletes a path which another is configuring.

ACTION: Coordinate activity between users.

CAUSE: NMMGR has encountered an unexpected condition in the configuration file. An internal error occurred. Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

ACTION: Check the version of NMCONF.

CAUSE: NMMGR has encountered a link data record with a type code (word #1) that is not currently supported. The configuration file may have been corrupted by a file system or disk error.

ACTION: Restore an old version of the configuration file if possible, or delete and reconstruct the corrupt link data record.

CAUSE: The user attempted to add a new LINK without specifying a link type.

ACTION: The type for a new link must be specified.

CAUSE: NMMGR has encountered unrecognizable data in the configuration file. A file system or disc error may have corrupted the configuration file. Possible situations which may cause this error include: 1) A data record does not match the expected format. 2) A link data record has an unexpected type code (word #1). 3) A link exists without a data record to indicate its type.

ACTION: Restore an old version of the configuration file if possible, or delete and reconstruct the corrupt link data record.

CAUSE: The user attempted to add more items than the maximum allowed at this level.

ACTION: Check the NMMGR manual for these maximum values.

CAUSE: The file NMCAT.PUB.SYS is not a valid message file, does not exist, or is corrupt.

ACTION: See "Invalid Software Installation" at the beginning of this appendix.

CAUSE: A file equation exists for NMMGRCAT.PUB.SYS.

ACTION: Check for file equations using LISTEQ2.PUB.SYS and RESET if necessary.

CAUSE: The table of commands in the NM catalog file NMCAT.PUB.SYS is corrupt or missing. File NMCAT.PUB.SYS is not a valid catalog file, or it has become corrupted.

ACTION: Restore a back-up copy of NMMGRF.PUB.SYS.

CAUSE: The table of commands in the NM catalog file NMCAT.PUB.SYS is corrupt or missing. Set 7 of NMCAT.PUB.SYS (the command set) is missing, or some commands have been deleted from this set.

ACTION: Restore a back-up copy of NMMGRF.PUB.SYS.

CAUSE: NMMGR was unable to locate type code in data record.

ACTION: Restore an old version of the configuration file if possible, or delete and reconstruct the corrupt link data record.

CAUSE: The forms file NMMGRF.PUB.SYS may be missing or corrupt.

ACTION: Go to the Errors screen and check any other errors which are displayed. See "Invalid Software Installation" at the beginning of this appendix.

CAUSE: A terminal I/O error may have occurred. A user may have entered :EOF or :EOD in response to the prompt "Press RETURN when done viewing contents," thereby closing the terminal for further input.

ACTION: Check the state of the terminal. Run NMMGR again if the terminal is closed for input.

CAUSE: A data record may be corrupted, making it impossible for NMMGR to display it.

ACTION: Go to the Errors screen and check any other errors which are displayed. See "Invalid Software Installation" at the beginning of this appendix.

CAUSE: NMMGR was unable to display the form for the screen which the user selected. An internal VPLUS/3000 or NMCONF error may have occurred.

ACTION: Check the version of VPLUS/3000 and NMCONF and restore back-up copies if necessary.

CAUSE: The user has gone to the ERRORS screen to check the last error, but no errors have occurred.

ACTION: None.

CAUSE: The user executed an MPE command (by entering the command preceded by a colon and pressing ENTER), and the command terminated in an error state.

ACTION: Use the Error Information screen and check the Command Interpreter error for further information.

CAUSE: The user tried to DELETE, RENAME, or UPDATE an item in a select screen, but the item does not exist in the configuration file.

ACTION: Use the ADD key if you intend to add the new item; otherwise check the spelling of the item name.

CAUSE: The user tried to ADD an item in a select screen, but the item already exists.

ACTION: Check the spelling of the item name.

CAUSE: A file system error occurred.

ACTION: Go to the Errors screen and check for a file system error (FSERR). Correct the error and try again.

CAUSE: The NMFILE.PUB.SYS process of the Node Management Services is not running.

ACTION: Go to the Errors screen and check for FSERR 97. If this error occurred, the problem may be due to a version mismatch in the NMS subsystem. See "Invalid Software Installation" at the beginning of this appendix.

CAUSE: NMMGR was unable to reopen the configuration file after closing it for compression.

ACTION: Check the NMCONF or File System error (if one is reported) for further information. This error is fatal and cannot be recovered except by running NMMGR again. See message NMGRERR 22.

CAUSE: A file system error occurred.

ACTION: Go to the Errors screen and check for a file system error (FSERR). Correct the error and try again.

CAUSE: You are not the creator of the configuration file.

ACTION: Go to the Errors screen and check for FSERR 94. If this error occurred, you can copy the file and then compress it, or ask the creator to compress the file.

CAUSE: NMMGR was unable to compress the configuration file because at least one other user is currently accessing the file.

ACTION: COMPRESS requires exclusive access to the configuration file. Use LISTF,2 to check whether other users are accessing this file. Wait until the file is not being accessed and try again.

CAUSE: The absolute value of the number of records to add or remove is too large. The resulting file would not have been able to contain all the records in the file, or, if a positive number was specified, the resulting file would have exceeded the 64,000 record limit.

ACTION: Enter a different value.

CAUSE: The user does not have the Node Manager or Network Administrator capability required to run NMMGR.

ACTION: Check user capability with program LISTDIR5.PUB.SYS, and contact the account manager or system manager if an additional capability is needed.

CAUSE: The user tried to CREATE a file in the OPEN FILE screen when the file already exists.

ACTION: Delete the file to create a new, empty configuration file, or use the OPEN key to open an existing file.

CAUSE: The user tried to RENAME an item in a select screen without specifying the new name.

ACTION: Enter a name in the rename field and try again.

CAUSE: The user tried to OPEN a file in the OPEN FILE screen when the file does not exist.

ACTION: Use the CREATE key to create a new file.

CAUSE: The user typed an ambiguous command prefix in the command window and hit ENTER.

ACTION: Make the prefix unambiguous by using more letters of the command. Check the NMMGR manual for unambiguous command prefixes.

CAUSE: This error in an internal NMMGR error. NMMGR has created a path whose depth exceeds the maximum allowable depth for paths.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: NMMGR encountered a path name whose format is not recognized. A possible situation which may cause this error is that the user has entered an incorrect path name in the command window.

ACTION: Check your subsystem node management or configuration manual for correct format of a path name and check the subsystem manual for valid paths.

CAUSE: An internal NMMGR error has occurred.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: An error occurred during output of the tree structure or data records of a configuration file.

ACTION: Check the NMCONF or File System error to determine the specific error.

CAUSE: The configuration file may have corrupt data records or invalid paths.

ACTION: Delete and reconstruct the corrupt link data record, or restore a backup copy of the configuration file if possible and run NMMGRVER again. If the error still occurs, submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: If the file FORMLIST is equated to a disk file, the file may be too small to accommodate the output listing.

ACTION: Check the size of the file and change the file size specification if necessary.

CAUSE: The user attempted to OPEN or CREATE a configuration file with an invalid file name.

ACTION: Check the spelling and syntax of the file name.

CAUSE: The user pressed [ENTER] without putting a command in the command window. NMMGR uses [ENTER] ONLY for commands. Modifications to the configuration file are all made using function keys.

ACTION: Make modifications to the configuration file by using the function keys.

CAUSE: The user executed an MPE command (by entering the command preceded by a colon and pressing ENTER), and the command terminated in a warning state.

ACTION: Use the Error Information screen and check the Command Interpreter error for further information.

CAUSE: The termination trap handling procedure for program aborts cannot be set. This error indicates an internal MPE problem in the procedure XDSNTRAP, which places a termination procedure PLABEL in the process context for use by MPE during process termination.

ACTION: Check the MPE installation to see that XDSNTRAP is present and working.

CAUSE: The user is trying to view a configuration screen without first opening a configuration file.

ACTION: Open the configuration file and enter the command again.

CAUSE: The configuration file is corrupted.

ACTION: Restore a backup copy of the configuration file if possible and run NMMGRVER again. If the error still occurs, submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: The forms file is corrupted or is a bad version.

ACTION: See "Invalid Software Installation" at the beginning of this appendix.

CAUSE: This is an internal NMMGR error. NMMGR has encountered unexpected data from the screen.

ACTION: Check to see that the correct version of NMMGR is installed. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal NMMGR error. NMMGR cannot properly create a data record from the input from the screen.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: NMMGR cannot properly display a data field in the configuration file on the screen. The configuration file is corrupted.

ACTION: Restore a back-up copy of the configuration file if possible.

CAUSE: This is an internal NMMGR error. An unknown status code is returned from a procedure.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: The user has entered a path name in the command field that is not in the configuration file.

ACTION: Check the path name entered and try again.

CAUSE: This is an internal NMMGR error. NMMGR cannot match a path name and a type code to an internal table.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal NMMGR error. NMMGR cannot match a path name to an internal table.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an NMMGR internal error. NMMGR is scanning the configuration file off the boundary.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal NMMGR error. NMMGR cannot locate a node in an internal table describing the configuration file structure.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: There is no screen to display that is associated with this path name. A path exists in the configuration file but is not recognized by NMMGR.

ACTION: This path is for internal use only. Check the pathname and try again.

CAUSE: NMMGR creates version stamps for each subsystem in configuration file at file creation time, and in some cases at file open time. This is an internal NMMGR error. NMMGR cannot create version stamps in the configuration file due to an NMCONF error. Check the NMCONF error number for detail.

ACTION: Purge this new file and try to recreate it. If an error still occurs, see "Submitting an SR" at the beginning of this appendix.

CAUSE: NMMGR checks version stamps of each subsystem in the configuration file at file open time. Version checking results show that there is configuration data for at least one subsystem in the configuration file that is not supported by this version of NMMGR.

ACTION: Run the version control program NMMGRVER to update the file, or open another file, or create a new file.

CAUSE: NMMGR checks version stamps of each subsystem in the configuration file at file open time. An error has occurred in the version checking routine. The configuration file may have corrupt data records or invalid paths.

ACTION: Restore a back-up copy of the configuration file if possible.

CAUSE: An internal NMMGR error has occurred: unable to get vsflag status. The possible causes include: internal error in vsflag_check_driver, or the parameters file_num, file_type_column, or vsflag_path do not match those stored in vsflag array at open time.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: NMMGR checks version stamps of each subsystem in the configuration file at accessing time. The version checking result shows that the specified subsystem has a mismatched version stamp in the configuration file that is not supported by this version of NMMGR.

ACTION: Since this version stamp is greater than what NMMGR supports, use NMMGR to create a new file. In this case, the NMMGRVER conversion utility will not help.

CAUSE: NMMGR was unable to retrieve information on the screen field via VPLUS utilities.

ACTION: Go to the Errors screen and check the VPLUS error message to determine the specific error. Correct the error and try again.

CAUSE: NMMGR was unable to retrieve information on the screen field via VPLUS utilities. The forms file NMMGRF.PUB.SYS and NMMGR are different versions, or the forms file is corrupt.

ACTION: See "Invalid Software Installation" at the beginning of this appendix.

CAUSE: NMMGR was unable to retrieve information on the screen field via VPLUS utilities.

ACTION: Go to the Errors screen and check the VPLUS error messages to determine the specific error. Correct the error and try again.

CAUSE: NMMGR was unable to retrieve information on the screen field via VPLUS utilities. The forms file NMMGRF.PUB.SYS and NMMGR are different versions, or the forms file is corrupt.

ACTION: See "Invalid Software Installation" at the beginning of this appendix.

CAUSE: This is an NMMGR internal conversion table error.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an NMMGR internal conversion table error. NMMGR cannot locate data for a field to display on this screen.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an NMMGR internal conversion table error. NMMGR encountered an unknown conversion code.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal NMMGR error. A character string passed to one of the conversion routines is too long.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal NMMGR error.

ACTION: Go to the Errors screen and check for a VPLUS error message to determine the specific error. Correct any errors and try again.

CAUSE: This is an internal NMMGR error. The forms file NMMGRF.PUB.SYS and NMMGR are not the same version, or the forms file is corrupt.

ACTION: Restore a back-up copy of NMMGRF.PUB.SYS.

CAUSE: This is an internal NMMGR conversion table error.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an NMMGR internal table error. The screen name is not in an internal conversion table.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal NMMGR error. NMMGR cannot properly locate field data from this screen.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal NMGRR conversion table error.

ACTION: Submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: NMMGR was unable to successfully lock the configuration file.

ACTION: Go to the Errors screen and check for any NMERR or FSERR error messages to determine the specific error. Correct the error and try again. If necessary, submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: NMMGR was unable to successfully unlock the configuration file.

ACTION: Go to the Errors screen and check for any NMERR or FSERR error messages to determine the specific error. Correct the error and try again. If necessary, submit a Service Request. See "Submitting an SR" at the beginning of this appendix.

CAUSE: The Delete key needs to be pressed twice to accomplish the deletion.

ACTION: Press the Delete key a second time to confirm the deletion.

CAUSE: NMMGR was unable to open the NMMGR help catalog, NMMGRHLP.PUB.SYS.

ACTION: Restore the NMMGR help catalog.

CAUSE: Some configuration data could not be found or printed in the summary.

ACTION: Check the summary to ensure that all required fields are configured.

CAUSE: The data that could not be found or printed is replaced with asterisks in the summary printout.

ACTION: Check the summary to ensure that all required fields are configured.

CAUSE: The subsystem summary output routine cannot be load processed from the group, account, or system SL.

ACTION: Stream the install job I00INMAC.NMA.HPPL87 to add the routine to system SL.

CAUSE: The additional address in the Network Directory data screen must be in the format of AXXXXXXX.AXXXXXXX, where A is any alpha char and X is any alphanumeric character.

ACTION: Use correct format.

CAUSE: The MPE HELP subsystem could not use the help file NMMGRHLP.PUB.SYS.

ACTION: Make sure that the file NMMGRHLP.PUB.SYS is properly formatted (RUN MAKECAT.PUB.SYS,HELP).

CAUSE: The MPE HELP subsystem could not use the help file NMMGRHLP.PUB.SYS.

ACTION: RESTORE the file NMMGRHLP.PUB.SYS.

CAUSE: The user pressed a GO TO type function key on the DTS screen that was not compatible with the type of DTS subsystem specified on that screen.

ACTION: Press the correct key or, to force selection of the incompatible subsystem, press the incompatible key a second time.

CAUSE: The user entered an IP address that failed IP address edits (address was invalid).

ACTION: Enter a valid IP address; check the class letter (A, B, C, or E accepted). (Press the Help key for more information on entering a valid IP address.)

CAUSE: The user entered a LAN station address that failed station address edits (address was invalid).

ACTION: Enter a valid LAN station address; must be six pairs of hex digits. (Press the Help key for more information on entering a valid LAN station address.)

CAUSE: A reachable network IP address is the same as the gateway IP address. The network portion of these addresses must be different.

ACTION: Correct either the reachable network IP address or the gateway IP address and re-enter.

CAUSE: User attempted to update information without entering required data. At least one Reachable Net IP Address/Hop pair is required on page 1 of the Reachable Networks screen.

ACTION: Enter the required information and continue.

CAUSE: User attempted to go to next page at the maximum page count (256).

ACTION: Use CONDENSE PAGE.

CAUSE: User attempted to do "LAST PAGE" or "CONDENSE PAGE". The configuration file may have Reachable Network paths in excess of the maximum page count.

ACTION: Restore the configuration file with Reachable Network paths within the maximum page count.

CAUSE: The user pressed "Open Config" or "Create Config" but did not enter the configuration file name on the OPEN screen.

ACTION: Supply the configuration file name.

CAUSE: The user pressed "Open Directory" or "Create Directory", but did not fill in the Network Directory File Name field on the OPEN screen.

ACTION: Supply the network directory file name.

CAUSE: The user entered the NEXT command but there is no next screen.

ACTION: None.

CAUSE: No reachable networks exist in the file to be condensed.

ACTION: None.

CAUSE: Error occurs during "CONDENSE PAGE" while doing an "nmconfgetdata" or "nmconfrenamepath". It can be caused by a corrupted configuration file. Another possibility is that an internal error is occurring with NMCONF intrinsics.

ACTION: Restore a back up copy of the configuration file and try again. If the error still occurs, see "Submitting an SR" at the beginning of this appendix.

CAUSE: The file number was changed in NMMGR but not entered in the table.

ACTION: Exit NMMGR, then rerun it and try to observe what damage has been done. Repair if possible or restore the configuration file.

CAUSE: The file number was changed in NMMGR but not entered in the table.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: The file number was not located in a search through the table. It is likely that a file number was changed in NMMGR but not entered in the table.

ACTION: Exit NMMGR, and rerun NMMGR and try to observe what damage has been done. Repair if possible or restore the configuration file. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: An attempt to clear the file table of a closed file failed.

ACTION: Exit NMMGR. It is possible that no damage occurred. Rerun NMMGR. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: On trying to access the file table, an error was found in the table. This will happen at open time if an attempt is made to put a file into the file table and if the slot in the table is already occupied.

ACTION: Exit NMMGR. It is possible that no damage occurred. Rerun NMMGR. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: The network transport is being started using the file that NMMGR has open as the active configuration file. A guided dynamic update cannot be started until the transport has been started.

ACTION: Wait until the transport is started and then try again.

CAUSE: Either the transport is being started using the file NMMGR has open as the active configuration file, or NMMGR is processing a guided dynamic update which cannot continue until the transport has been started.

ACTION: Wait until the transport is started and then try again.

CAUSE: The transport is using the file NMMGR has open as the active configuration file. Guided configuration cannot be performed on an active configuration file (only guided dynamic updates can).

ACTION: None.

CAUSE: The transport is being started using the file NMMGR has open as the active configuration file. NMMGR is performing a guided configuration which cannot continue while the transport is up. The file cannot be modified except with guided dynamic updates until the transport is brought down.

ACTION: Type 'STOP' in the command window and press ENTER to stop guided configuration.

CAUSE: Transport is using the file NMMGR has open as the active configuration file. The file cannot be changed except with guided configuration.

ACTION: Enter guided configuration to perform this function.

CAUSE: The transport is being initiated using the file that NMMGR has open as the active configuration file, and NMMGR was in the middle of a subtree copy.

ACTION: When the transport is no longer running, purge the subtree you were copying into and restart the subtree copy.

CAUSE: NMMGR cannot determine whether or not the transport is using this file.

ACTION: If the transport is being started or shut down, wait until it is finished and then try again. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: Data in the NETXPORT subsystem was changed and NETXPORT was not successfully validated afterwords.

ACTION: Go to the validation screen and validate NETXPORT or type exit again, this leaves the file unvalidated.

CAUSE: Data in the DTS or LINK subsystems was changed and DTS/LINK was not successfully validated afterwords.

ACTION: Go to the validation screen and validate DTS/LINK or type exit again, this leaves the file unvalidated.

CAUSE: Data in the SNANODE, NRJE, or IMF subsystems was changed and HP-IBM was not successfully validated afterwards.

ACTION: The user can go to the validation screen and validate HP-IBM. The user can type exit again and leave the file unvalidated.

CAUSE: File does not exist.

ACTION: Check to see what happened to the file NMMGRVAL.PUB.SYS. If it has been inadvertently purged, try restoring it from a backup tape.

CAUSE: Internal error.

ACTION: Contact your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Contact your Hewlett-Packard representative.

CAUSE: Internal error.

ACTION: Contact your Hewlett-Packard representative.

CAUSE: The user entered two LU's with the same LU Numbers. The duplicate numbers may be on the same page of LU data, or one may be on page 1 of LU data and the other on page 2 of LU data.

ACTION: Make sure all LU's have unique numbers.

CAUSE: You have entered two LUs with the same LU name. These names may be on the same page (1 or 2) of LU data, or one name may be on page 1 and the other on page 2.

ACTION: Make sure all LUs have unique names.

CAUSE: The user entered an LU Number out of the acceptable range of 1-255.

ACTION: Enter an LU Number that is in the range 1-255.

CAUSE: You entered an IP address with the node portion of the IP address equal to zero.

ACTION: Modify the node portion of the IP address to a valid IP address.

CAUSE: The user entered a string that contained some non alpha-numeric characters.

ACTION: Re-enter the string with alpha-numeric characters only.

CAUSE: The IP mask was entered incorrectly. Each octet (XXX) can only contain digits. The octets can be separated by periods or blank spaces.

ACTION: Enter a mask in the correct format.

CAUSE: One or more of the octets entered in the IP mask contains a number less than 0 or greater than 255.

ACTION: Enter a mask with octets within the range 0 to 255.

CAUSE: More or less than four octets (XXX) were entered.

ACTION: Re-enter the mask with exactly four octets.

CAUSE: An IP Subnet Mask of 255.255.255 was entered. This is not a legal mask.

ACTION: Re-enter the mask with a different value.

CAUSE: If the PU Type is 2.1 and the PU Dependent Support is N, then there cannot be any LU Numbers associated with the LU names.

ACTION: Make all the LU Numbers blank and try again.

CAUSE: The user entered an invalid SNA LU name. The SNA LU Name must be in the format of AXXXXXXX.AXXXXXXX, where A is any alpha character and X in any alphanumeric character.

ACTION: Make all the LU Numbers blank and try again.

CAUSE: The user pressed the PREV PAGE function key on a paged data screen and there was no previous page of data.

ACTION: None.

CAUSE: The user entered an Ldev that is out of range.

ACTION: Re-enter an Ldev within the allowed range.

CAUSE: The user entered a name in a field that allows more characters than a valid name allows. This field is usually used for more than one type of entry. The program believes that the user is trying to store a name that is too long.

ACTION: Enter a new name 16 characters or shorter.

CAUSE: The user has tried to enter a name with invalid characters in it.

ACTION: Enter a name with valid characters.

CAUSE: The node portion of the IP address is all zeros.

ACTION: Check the IP address and make sure that the node portion is not all zeros. Enter a valid IP address. (Press the Help key for more information on entering a valid IP address.)

CAUSE: The network portion of the IP address is all zeros.

ACTION: Check the IP address and make sure that the network portion is not all zeros. Enter a valid IP address. (Press the Help key for more information on entering a valid IP address.)

CAUSE: The IP address entered has a network address of 127. This network address with any node address is reserved for loopback.

ACTION: Check the IP address and make sure that the network address is not 127. Enter a valid IP address. (Press the Help key for more information on entering a valid IP address.)

CAUSE: The IP address the user entered is a reserved address.

ACTION: Enter a different IP address. (Press the Help key for more information on entering a valid IP address.)

CAUSE: The user entered an invalid LAN address on a screen or in a maintenance mode command.

ACTION: Correct the LAN address and repeat the last command or action. (Press the Help key for more information on entering a valid LAN address.)

CAUSE: The user, while using the DTSDYNCONF command in maint mode, they entered in invalid char. The only valid response is either ON or OFF.

ACTION: Enter either ON or OFF.

CAUSE: Data in the SNA.DS subsystem was changed and SNA/DS was not successfully validated afterwords.

ACTION: Go to the validation screen and validate SNA/DS or type exit again to leave the file unvalidated.

CAUSE: One or more of the subsystems in NMMGR have not been validated.

ACTION: To see which subsystems have not been validated, type ERRORS in the command line and press the Enter key. Go to the validation screen to validate the unvalidated subsystems or type exit again to leave the file unvalidated.

CAUSE: This is an internal NMMGR error. The number of statements in an internal table does not match the number expected by NMMGR.

ACTION: Restore the file NMMGRCAT.PUB.SYS. Then run NMMAINT.PUB.SYS to make sure the version of NMMGR is correct.

CAUSE: This is an internal guided configuration error caused by a corrupt NMMGRCAT.PUB.SYS file.

ACTION: Restore NMMGRCAT and retry. If this fails see "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error caused when more than one NMCONF file is opened by the guided configuration open statement.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is caused when the source/destination file or the file NMAUX1.PUB.SYS is either missing, is the wrong version, is locked for exclusive access, or was corrupted during a subtree copy.

ACTION: If doing a subtree copy, check to see that the source and destination files really exist. If performing a guided configuration task, copy NMAUX1.PUB.SYS from backup tape, and run NMMAINT.PUB.SYS to make sure that you have the correct version.

CAUSE: This is an internal guided configuration error caused when data is copied from the auxiliary file to the user file and the auxiliary file was not opened.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is a guided configuration error caused when NMMGRCAT specifies a path in the auxiliary file that does not exist.

ACTION: Copy NMAUX1.PUB.SYS from back-up tape, and run NMAINT.PUB.SYS to make sure that the version of NMAUX1 is the same as the version of NMMGR.

CAUSE: This problem could be caused by a corrupt file or by an old configuration file that needs to be updated.

ACTION: Run NMMGRVER.PUB.SYS. If needed, restore a known good configuration file from a back-up tape, or create a new configuration file with NMMGR.

CAUSE: This is an internal guided configuration error.

ACTION: Restore NMMGRCAT.PUB.SYS from a back-up tape. If this fails see "Submitting an SR" at the beginning of this appendix.

CAUSE: An unexpected or internal guided configuration error occurred.

ACTION: Type the "ERROR" command after this message is displayed for clarification of the error(s). A PC value is specified at the end of this error message. If you are unable to include the value problem, submit an SR. See "Submitting an SR" at the beginning of this appendix. Be sure to include the value of the PC with the SR.

CAUSE: The STOP command is allowed only on screens which contain a "path." This is most likely to occur when the user types the command "STOP" on the errors screen during guided configuration.

ACTION: Move to a screen which contains a "path" at the top of the menu and retype the stop command.

CAUSE: This error occurs when the user attempts to use the NEXT command when no selection screen has been encountered.

ACTION: There is no need to use this function at this time.

CAUSE: The user has pressed a function key that is not allowed during guided configuration. If the user is on a data screen, it is possible to advance by pressing the Update function key.

ACTION: Press a labeled function key.

CAUSE: This is an internal guided configuration error that is caused by missing information in the forms file.

ACTION: Restore NMMGRF.PUB.SYS from back-up tape, and run NMMAINT.PUB.SYS. If this fails see "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal guided configuration error.

ACTION: Restore NMMGRCAT.PUB.SYS from back-up tape. If this fails see "Submitting an SR" at the beginning of this appendix.

CAUSE: Certain commands are only allowed on states which contain a path. This is likely to occur when the user types STOP on the errors screen or the version screen during guided configuration.

ACTION: Move to a state which contains a path and retype the stop command.

CAUSE: The type of the network interface does not match the topology key which you selected.

ACTION: Make sure you pressed the correct topology key and have the correct network interface name. Check the type of the network interface name by going to NEXPORT.NI (do a direct branch).

CAUSE: The Network Interface must be of type POINT-TO-POINT.

ACTION: Check the type of the network interface name by going to NETXPORT.NI (do a direct branch).

CAUSE: There is no Internet data to configure under the loopback network interface.

ACTION: Do not use this function with loopback.

CAUSE: You may have spelled the name incorrectly.

ACTION: Check the spelling and reenter.

CAUSE: The type may be unknown.

ACTION: Check the type of the network interface name by going to NETXPORT.NI (do a direct branch). File an SR if the type is labeled as UNKNOWN. (See "Submitting an SR" at the beginning of this appendix). Delete the unknown type and retry.

CAUSE: File does not exist or is the wrong version.

ACTION: If in guided configuration, then NMAUXI.PUB.SYS could not be opened. If performing a copy subtree, check the source file to make sure it exists and is the correct version.

CAUSE: File does not exist or is the wrong version.

ACTION: If in guided configuration, then NMCONFIG.PUB.SYS or the user file does not exist, or is corrupt. You may check the version by running NMMAINT.PUB.SYS. You may also run NMMGRVER to determine if your file is corrupt.

If performing a copy subtree, check the destination file to make sure it exists. Check the version and check to see if the file is corrupt (as above).

CAUSE: There is an internal G-code error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: There is an internal G-code error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: There is an internal G-code error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: The operation is illegal if the NI is not an X.25 link.

ACTION: Check to make sure that the NI is an X.25 link.

CAUSE: While running guided configuration, the user tried to press Next Screen without first pressing Update Data while at the path SNANODE.nodename.

ACTION: Enter the correct data and press Update Data.

CAUSE: At the Guided HP Configuration screen, the user attempted to fine tune the parameters for an NI configuration without specifying the NI name in the NI Name field.

ACTION: Enter a valid NI name in the NI Name field and press the FineTune Parms key again.

CAUSE: The user attempted to perform an operation on an non-existent NI. Either the NI is not configured or the specified NI name is incorrect.

ACTION: Specify the correct NI name of a configured NI and try again.

CAUSE: The user attempted to create an NI using an NI name that has already been configured for another NI of a different type.

ACTION: Specify an NI name that has not already been used and try again.

CAUSE: While configuring an NI, the user specified a link name that has already been configured for a different NI and cannot be shared.

ACTION: Specify a different link name and try again.

CAUSE: The user attempted to update the configuration file without specifying a link name, which is required for this screen.

ACTION: Enter a link name in the Link name field and try again.

CAUSE: The user attempted to change the name of a link that is used by more than one NI.

ACTION: Leave the link name as it is or reconfigure one or the other of the NIs to use a different link.

CAUSE: At the Guided HP Configuration screen, the user entered a new NI name and pressed the Config Network key without specifying a type in the NI type field. The type must be specified if the NI does not already exist.

ACTION: If you are configuring a new NI, enter the type of the new NI in the NI type field and press Config Network. If you are updating an existing NI and entered the wrong name in the NI name field, enter the correct NI name and press Config Network.

CAUSE: At the DTS Configuration screen or at one of the DTC card configuration screens, the user specified the name of a profile that is not configured and then pressed the save data key.

ACTION: Press the Go To Profiles key if one exists for the screen. If not, type GoToProfiles in the command line and press Enter. This will take you to the profile configuration screens. Configure the nonexisting profile(s) and save the information in the configuration file. When you are finished, press the Prior Screen key until NMMGR returns you to the screen you were at when you originally entered the nonexisting profile name. There is no need to re-enter the data on this screen, since it has already been saved. Continue with the next configuration task.

CAUSE: At the DTC Configuration screen, the user pressed the Read DTC function key without specifying a DTC name.

ACTION: Enter a valid DTC name and try again.

CAUSE: At the DTC Configuration screen, the user specified a nonexisting DTC name and pressed either the Config Card key or the Read DTC key.

ACTION: If an incorrect DTC name was entered, enter the correct DTC name and try again. If the DTC name is correct but the DTC has not yet been configured, enter the information for the DTC and press the Save Data key, then try again.

CAUSE: At the DTS Configuration screen, the user entered a nonexisting link name and pressed the Tune DTS Link key.

ACTION: If an incorrect link name was entered, enter the correct link name and try again. If the link name is correct but the link has not yet been configured, enter the information for the link and press the Save Data key, then try again.

CAUSE: At the DTC Configuration screen, the user entered an invalid character in the field specifying the card to be configured and pressed the Config Card key.

ACTION: Enter the number of the card to be configured and press Config Card again. The number must be between 0 and 5 and must correspond to the DTC slot number of the card being configured.

CAUSE: The user specified a nonexisting NI name as the home network interface and saved the data on the screen.

ACTION: If an incorrect NI name was specified, correct the NI name and press Save Data again. If the NI name is correct but the NI has not yet been configured, configure the NI. There is no need to re-enter the information on the current screen since it has already been saved.

CAUSE: The user specified a nonexisting SNA node and saved the data on the screen.

ACTION: If an incorrect SNA node was specified, correct the SNA node name and press Save Data again. If the SNA node name is correct but the SNA node has not yet been configured, configure the SNA node. There is no need to re-enter the information on the current screen since it has already been saved.

CAUSE: The user entered a nonexisting link name and pressed the Link Routing key.

ACTION: If an incorrect link name was specified, correct the link name and try again. If link name is correct but the link has not yet been configured, configure the link.

CAUSE: The user attempted to add an address to the network directory for a node whose path report is already full. No additional addresses can be added.

ACTION: Go to the Network Directory Data screen for the node and delete some of the addresses assigned to the node name.

CAUSE: The node name was not configured.

ACTION: Go to the Main screen and configure the node name.

CAUSE: The user neglected to enter the IP address in the appropriate field.

ACTION: Enter the IP address and try again.

CAUSE: The user pressed the Open Config or Create Config key with no file name specified in the backup configuration file name field.

ACTION: Enter a valid file name in the backup configuration file name field and press Open Config or Create Config again.

CAUSE: NMMGR was unable to open the file whose name was specified in the ADDVC or PURGEVC command, either because the file does not exist or because a more serious file system error occurred.

ACTION: 1. The file name specified may not exist. Try the command again with a file that exists.

ACTION: 2. A more serious file system error may have occurred. See the accompanying file system error message for resolution.

CAUSE: The user attempted to perform an ADDVC or PURGEVC command without first opening the configuration and/or directory files.

ACTION: Open a configuration file with the OPENCONF command and a directory file with the OPENDIR command.

CAUSE: The user specified an existing link name on one of the custom NI update screens. The selected link's type was not correct; that is, a LAPB type link was specified for an X.25 NI.

ACTION: Enter the name of a link with the correct type or delete the link configuration.

CAUSE: At the DTC Configuration screen, the user selected a card number and pressed the Config Card key. No type was entered in the Type field associated with the selected card.

ACTION: Fill in a card type in the Type field for the selected card and press the Save Data key. Type must be "D" for direct connect, "M" for modem, or "P" for PAD. Once the data has been saved, select the card and press the Config Card key again.

CAUSE: The user pressed the validate key and the configuration validated correctly, but NMMGR could not back up the configuration file because an error occurred while writing the backup file.

ACTION: Type ERR on the command line and view the errors that occurred. After correcting the errors, retry the validate operation.

CAUSE: The user failed to enter either a valid switched virtual circuit address or a valid permanent virtual circuit address. One or the other must be entered.

ACTION: Enter a valid address as appropriate for the VC, either switched or permanent.

CAUSE: The user entered the name of an existing NI and specified the type as X.25. The NI exists but its type is not X.25.

ACTION: If you are updating an existing NI, enter the correct NI name and the correct type and try again. If you are configuring a new NI, enter a name that has not already been used and try again.

CAUSE: The user specified an address key that was not unique for the NI specified at the VC Configuration screen or through the ADDVC command.

ACTION: Go to the SVC and PVC paths screens for the NI to see the names that are already configured. Choose an address key that is not used in either of these screens.

CAUSE: While using the ADDVC command in maintenance mode, the user forgot to enter the IP address with either an opening or a closing quote.

ACTION: Re-issue the command with the correct IP address enclosed in quotes.

CAUSE: The path to the subtree to copy was not found.

ACTION: Check to make sure you have the correct file and check the source path spelling.

CAUSE: The destination path, which is created by substituting any destination IDs into the source path, was not accessible. The path in the file was not an exact match, or the destination path was missing.

ACTION: Check the source and destination path spelling and make sure you have the correct file.

CAUSE: The destination path already exists in the file.

ACTION: Enter 'Y' in the overwrite option.

CAUSE: The source and destination paths must start at the same spot in the NMMGR schema. Most likely the user attempted to change the name of an item in the destination of a subtree copy.

ACTION: Check to see if the item that was changed was a select or type select identifier. If not, that will cause the subcopy to fail.

Check to make sure that any destination type select items, if changed, were changed to items of the same type (as in LAN to LAN, instead of LAN to router).

CAUSE: Internal error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: Incorrect ids in the destination path.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE:A path id in the destination pathname is not legal.

ACTION: Check the destination path id for typing mistakes.

CAUSE: The source and destination paths must be the same length. When entering data on the subtree copy screen, the source path may appear longer, but should this be the case, the destination path uses IDs from the source path. This error is generated in the other case when the destination path is longer than the source path.

ACTION: Check to make sure that you are not missing path ids in the source path.

CAUSE: This occurs when the user leaves path IDs empty in the middle of the source path field on the copy subtree screen.

ACTION: Check the source path, and fix the path, so that none of the source path IDs in the middle of the source path are blank.

CAUSE: The user is attempting to copy over the source data, which is not allowed.

ACTION: Select another file or path to copy into.

CAUSE: An NMCONF file to be opened for a copy could not be accessed.

ACTION: Check the spelling of the filename. Do a "listf <filename>" to see if file exists.

CAUSE: The source path is not permitted to be copied by the subtree command.

ACTION: None.

CAUSE: This is an internal error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an internal error.

ACTION: The directory file is probably corrupt and should be replaced by a copy from a back-up tape. Restore both data and key files. See "Submitting an SR" at the beginning of this appendix.

CAUSE: This is an informative message that is issued when the user hits NEXT PAGE and there are no subsequent names in the directory, or when the name supplied does not exist.

ACTION: None.

CAUSE: This is an informative message that is issued when the user hits PREV PAGE and there are none, or when the name supplied does not exist.

ACTION: None.

CAUSE: This is an informative message that is issued when the user tries to add a node name that already exists into the directory. The name is probably misspelled, or the wrong global/local setting was given.

ACTION: Correct the node name, the global/local setting, the type, and/or the enable flag.

CAUSE: This is an informative message that is issued when the user tries to delete or update a node name that does not exist. The name is probably misspelled, or the wrong global/local setting was given.

ACTION: Correct the node name, the global/local setting, the type, and/or the enable flag.

CAUSE: This is an informative message that is issued when the user tries to rename a node name (global/local setting), but both the new node name and new global/local setting were omitted.

ACTION: Specify the missing information.

CAUSE: The user attempted to delete or update a network address, or path data, but another user who is modifying the same directory file has just deleted the entry.

ACTION: Coordinate update activities with other user(s).

CAUSE: The user attempted to add a network address that already exists in the current path report.

ACTION: Either choose a different network address, or make sure you are updating the correct node name global/local setting.

CAUSE: This is an informative message that is issued when the user attempts to add or update a path in a very large path report list. This can happen only on very large gateway nodes, such as a node with more than 15 network addresses.

ACTION: See "Submitting an SR" at the beginning of this appendix. (Request an expansion on the limit on path reports.)

CAUSE: Severe error indicating an internal logic error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: Maintenance mode interface: An informative message that is issued when a user gives a command prior to completing a successful OPENDIR command.

ACTION: Open or create a directory file using OPENDIR, then reissue the command.

CAUSE: Maintenance mode interface: An informative message that is issued when no directory entry (either global, local, or neither — if no ;GLOBAL or ;LOCAL keyword given) could be found in the directory matching the specified node name.

ACTION: Correct the node name.

CAUSE: Maintenance mode interface: An informative message issued when an invalid file was specified in a MERGEDIR command. Possible causes are:

ACTION: Correct the filename.

CAUSE: Maintenance mode interface: Informative message issued when a user specified a node name in conjunction with a configuration file in a MERGEDIR command.

ACTION: Omit the node name from the command or use a directory file as the source and retain the node name.

CAUSE: Maintenance mode interface: An informative message issued when the user has given a DELETENODE command, specifying a node name that is not unique. For example, both a local and global entry could exist for the node name.

ACTION: Explicitly state the entry to be deleted using ;LOCAL or ;GLOBAL.

CAUSE: A node name was expected, however, the data present did not conform to the node name format.

ACTION: Correct the node name.

CAUSE: The node name is more than 50 characters long.

ACTION: Correct the node name.

CAUSE: An internal error in NMMGR has occurred.

ACTION: Run NMMAINT.PUB.SYS to make sure that you have the correct version of NMMGR. If necessary, restore the file NMMGRCAT.PUB.SYS from a back-up tape. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: The user specified too much data.

ACTION: Check syntax of command or type "help" for more information.

CAUSE: The user specified both a ;LOCAL and ;GLOBAL key operator.

ACTION: Retype the command with only a ;LOCAL or ;GLOBAL key operator.

CAUSE: The user specified more than one merge operator (KEEP, NOKEEP, TIMESTAMP).

ACTION: Retype the command with only one merge operator.

CAUSE: The user typed in an incorrect command.

ACTION: If the command is an MPE command, the command must start with a ':'. Check the spelling of the command name and reenter as needed.

CAUSE: A parameter's length in characters exceeds the maximum length permitted.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: A semicolon was encountered before other expected data was entered.

ACTION: Check syntax of the command or type "help" for more information.

CAUSE: A parameter is needed after certain commands. This error occurs if the user does not specify that parameter. OPENDIR: needs a filename. MERGEDIR: needs a filename. EXPANDDIR: needs an integer.

ACTION: Check syntax of the command or type "help" for more information.

CAUSE: This occurs in DELETENODE or MERGEDIR when the keyword local, global, keep, nokeep, or timestamp is spelled incorrectly or you have a duplicate type of keyword. DELETENODE only allows local or global keywords.

ACTION: Check spelling of keywords. Check for duplicate keyword types. Type "help" for correct syntax.

CAUSE: Configuration file name is invalid.

ACTION: Check the file name for validity. Also, make sure the name is not too long.

CAUSE: Directory name may be too long, or contains illegal characters.

ACTION: Recheck file name specified.

CAUSE: This command does not allow keywords.

ACTION: Check syntax of the command or type "help" for more information.

CAUSE: The node name length is wrong.

ACTION: Check the length of each segment in the node name. Each segment (name,domain,org) must be 1-16 characters in length.

CAUSE: The name portion of the node name is the incorrect length.

ACTION: Fix the length of the name in NAME.domain.org.

CAUSE: The domain portion of the node name is the incorrect length.

ACTION: Fix the length of the domain in name.DOMAIN.org.

CAUSE: The org portion of the node name is the incorrect length.

ACTION: Fix the length of the org in name.domain.org.

CAUSE: Each segment in node name (name,domain, and org) must begin with an alphabetic character.

ACTION: Check to see that the first char in each segment is in the set ['A' .. 'Z'].

CAUSE: Illegal character specified.

ACTION: Check each segment for an illegal character.

CAUSE: Incorrect format specified.

ACTION: Check to make sure that the three components—path, colon, and file—are present.

CAUSE: Incorrect format specified.

ACTION: File name parameters incorrectly specified.

CAUSE: Missing or invalid source file name specified.

ACTION: Check to make sure that an MPE file name was specified after the : delimiter to the copyconf command.

CAUSE: The syntax of the command requires a comma.

ACTION: Reissue the command using a comma.

CAUSE: Data was not updated for this node.

ACTION: Update the data for this node.

CAUSE: You did not access a paged data screen which has only one page.

ACTION: Check the path specified in the PATHCONF command.

CAUSE: User selected an empty selection from the entry selection window.

ACTION: Select an existing entry.

CAUSE: User entered a name which contained a label that terminated with an invalid character. Valid terminating characters are A..Z..,a..z, or 0..9.

ACTION: Enter the name correctly.

CAUSE: User entered a domain name which began with an invalid character. Domain name labels can only begin with an alphabetic character.

ACTION: Enter the name correctly.

CAUSE: User entered an invalid domain name. Valid characters consist of A..Z, a..z, 0..9 or -.

ACTION: Enter the name correctly.

CAUSE: Valid label length is 1 to 63 characters. User entered more than 63 characters.

ACTION: Enter the name correctly.

CAUSE: The user selected an operation which required a domain, yet neglected to enter a domain.

ACTION: Re-enter the information with the domain name specified.

CAUSE: User can access the domain screen only after using the add function key to add an NS nodename.

ACTION: Follow the instructions in "Cause."

CAUSE: User pressed a key which required that an entry selection be provided.

ACTION: User must either select an entry via the entry field, or enter the full node name in the nodename field.

CAUSE: User attempted to go to the domain screen after having just added a domain entry.

ACTION: None.

CAUSE: The entry field was empty or contained a value not in the range 1 to 8.

ACTION: Enter a value in the correct range.

CAUSE: User entered a name that exceeded 255 characters for DDN name, or user entered a name that exceeded 50 characters for NS name.

ACTION: Re-enter the name correctly.

CAUSE: User entered a file name that exceeded 36 characters.

ACTION: Enter a filename of correct length.

CAUSE: User entered a domain name that already existed in the directory.

ACTION: None.

CAUSE: The MERGEDIR command not permit the merging of a single domain entry. However, you can merge domain entries as a group, such as all the global domains or all the local domains.

ACTION: None.

CAUSE: User has selected a function that needs the above information.

ACTION: Enter the above information.

CAUSE: User has entered a name into the node name field and data into the entry number field. User can only specify one at a time for the operation selected (update, delete).

ACTION: Re-try with the correct information.

CAUSE: The user is using the merged command and is attempting to merge from a configuration file. In this case, the only valid options that can be specified are LOCAL and GLOBAL.

ACTION: Specify correct options.

CAUSE: User is on the directory data screen and wants to use NEXT branching. User cannot do so until the current data is updated.

ACTION: Press UPDATE; then NEXT can be used.

CAUSE: Maintenance mode interface: An operation on the existing directory file could not be performed. The possible operations are: FOPEN the file as a KSAM file exclusively, FGETINFO and FGETKEYINFO on the file, or FCLOSE the file with the delete option.

ACTION: Check the accompanying file system error for more information. If the error reflects an exclusive access violation, correct the multiple access and/or the user capabilities.

CAUSE: Maintenance mode interface: An operation on a COPY of the existing directory file could not be performed. The possible operations are:

ACTION: Check the accompanying file system error for more information. If the error reflects a security violation, then you are most likely (a) trying to access a file for read/write access for which you do not have adequate capabilities, or (b) trying to expand the file in a different account than your logon account.Since the expand operation involves a RENAME, you MUST be logged into the same account as the directory file that you are trying to expand. If the original directory file does not exist, but the temporary files ("ZTMPxxxx" and "ZTMPxxxK") do exist, then the directory can be recovered by building a new KSAM file manually (use KSAMUTIL) with attributes identical to that of the original file. Use FCOPY to copy the data and key files SEPARATELY into the newly built KSAM data and key files. Be sure to use the ";NOKSAM" option of FCOPY. If the temporary files do not exist, then the original directory must be restored from a back-up tape.

CAUSE: Maintenance mode interface: The location of internal KSAM data and key information has changed and thus cannot be updated with this version of the NMC software.

ACTION: For an intermediate solution, use KSAMUTIL to build a larger (expanded) file and use FCOPY to copy the directory to the new file. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: Maintenance mode interface: The user gave a negative number of records to expand the file.

ACTION: Supply a positive number of records.

CAUSE: The command file NMMGRCMD could not be opened.

ACTION: Check for any file equations set for "NMMGRCMD". See the accompanying file system error message for problem resolution.

CAUSE: Maintenance mode interface: An error message is issued when the configuration file argument for the OPENCONF command is missing.

ACTION: Reissue the command with the configuration file name.

CAUSE: Maintenance mode interface: An error message is issued when an invalid subsystem name is entered.

ACTION: Reissue the command with a correct subsystem name.

CAUSE: File system error.

ACTION: Check to see if user is allowed to access file. Check to see if user and account capabilities of NA or NM are set.

CAUSE: Incorrect use of PATHCONF command.

ACTION: Make sure that the screen you are trying to access is data or paged data. This can be checked by looking at the screen and seeing if there is a data flag in the upper right corner of the screen. If not, you are trying to access a screen which has no data fields.

CAUSE: You are trying to access a field N+k when there are only N fields on the form.

ACTION: Use NMMGR to go to the path which you specified in the PATHCONF command. Make sure that your field count matches the field number you are trying to access. Make sure you are not trying to use Vplus field numbers to access the field.

CAUSE: PATHCONF was not previously issued.

ACTION: Check to see if you set the path with the PATHCONF command. Check to see if the path that you specified exists in the configuration file

CAUSE: Version stamp must match NMMGR version.

ACTION: Change the version stamp in your batch file to match the version displayed on the NMMGR banner line.

CAUSE: Tried to perform OPENCONF before VERSIONCONF.

ACTION: Call VERSIONCONF with the version stamp which NMMGR displays on the banner line.

CAUSE: The copyconf command will not operate without a valid destination path.

ACTION: Check to make sure an NMCONF path name was specified for the copyconf command.

CAUSE: The copyconf command will not operate without a valid destination file name.

ACTION: Check to make sure that an MPE file name was specified after the colon (:) delimiter in the copyconf command.

CAUSE: An option other than KEEP was specified.

ACTION: Retry with valid option.

CAUSE: The nodelist file could not be opened for read/write access.

ACTION: See the accompanying file system error message for resolution.

CAUSE: The record size of the nodelist file is too small to be used.

ACTION: If creating the nodelist file using the LISTDIR command, then do not include a ;REC= parameter in the file equation. Copy the nodelist file into a file with a larger record width.

CAUSE: The nodelist file supplied did not have a 0 filecode—it was not a standard EDITOR-type file.

ACTION: If creating the nodelist file using the LISTDIR command, then do not include a ;CODE= parameter in the file equation. Copy the nodelist file into a file created with no file code.

CAUSE: Could not issue a directed read to the nodelist file. The file most likely has a variable-length record structure.

ACTION: See the accompanying file system error message for resolution.

CAUSE: Could not issue a directed write against the nodelist file.

ACTION: See the accompanying file system error message for resolution.

CAUSE: Could not close the nodelist file.

ACTION: See the accompanying file system error message for resolution.

CAUSE: Internal error.

CAUSE: Could not set the record pointer in the nodelist file.

ACTION: See the accompanying file system error message for resolution.

CAUSE: Internal error.

ACTION: See "Submitting an SR" at the beginning of this appendix.

CAUSE: Could not read sequentially from the nodelist file.

ACTION: See the accompanying file system error message for resolution.

CAUSE: A check to verify that the stream file does not already exist could not be completed.

ACTION: See the accompanying file system error message for resolution.

CAUSE: The stream file given already exists as a permanent file. The MAKESTREAM command requires that this file not exist.

ACTION: Choose another file name or rename the existing file to another name.

CAUSE: A check to verify that the command file does exist could not be completed.

ACTION: See the accompanying file system error message for resolution.

CAUSE: The command file given does not exist.

ACTION: Supply the name of an existing command file.

CAUSE: Message catalog NMMGRCAT.PUB.SYS is incorrect.

ACTION: RESTORE NMMGRCAT.PUB.SYS from a backup tape. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: Message catalog NMMGRCAT.PUB.SYS is incorrect.

ACTION: RESTORE NMMGRCAT.PUB.SYS from a backup tape. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: Internal error.

ACTION: RESTORE NMMGRCAT.PUB.SYS from a backup tape. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: Message catalog NMMGRCAT.PUB.SYS is incorrect.

ACTION: RESTORE NMMGRCAT.PUB.SYS from a backup tape. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: Message catalog NMMGRCAT.PUB.SYS is incorrect.

ACTION: RESTORE NMMGRCAT.PUB.SYS from a backup tape. If the problem still exists, see "Submitting an SR" at the beginning of this appendix.

CAUSE: The stream file could not be opened.

ACTION: See the accompanying file system error message for resolution.

CAUSE: Could not write to the stream file. Most likely, the end-of-file has been reached and the file is full.

ACTION: See the accompanying file system error message for resolution. If end-of-file has been reached, issue a file equation for the stream file: FILE yourfile;DISC=nnnn,32,1 where "yourfile" is the name of the stream file, and "nnnn" is the number of records needed in the file. Approximately 150 records should be allocated for each node in the nodelist file. Note that the stream file is created as a variable-length file, so fewer records should be required per node. The file is opened with a default of 5000 records. Retry the MAKESTREAM command with the new file equation.

CAUSE: The stream file could not be closed.

ACTION: See the accompanying file system error message for resolution.

CAUSE: An equal sign was missing in the command syntax.

ACTION: Re-enter the command with the proper syntax.

CAUSE: The syntax of the command requires a pathname parameter.

ACTION: Check pathname and reissue the command.

CAUSE: Either the field number parameter was not specified or the field number was not terminated with a comma.

ACTION: Check the field number on the screen.

CAUSE: WRITECONF command did not list data to be stored.

ACTION: The syntax of the command requires a data parameter. The data may be enclosed in quotes.

CAUSE: An invalid option was specified for the command.

ACTION: Use help to enter correct option.

CAUSE: Did not specify version correctly.

ACTION: The syntax of the command requires a valid version string parameter.

CAUSE: The syntax of the command requires a page number.

ACTION: The page number must be a positive integer.

CAUSE: The path must be for a select or type select screen.

ACTION: Check the path and reissue.

CAUSE: File system error.

ACTION: Check the file equation. See if the file is locked open or cannot be accessed. Check to see if there is disk space.

CAUSE: WRITECONF error.

ACTION: Check to see that you are accessing the correct field, or reduce the size of the data you are entering.

CAUSE: UPDATECONF error.

ACTION: Examine all WRITECONF statements before the screen associated with the UPDATECONF which caused the error. One or more of these fields does not match the edits which are associated with this field. Go to the NMMGR screen which corresponds to the path for further explanation of the Vplus error.

CAUSE: A READCONF or WRITECONF error occurred.

ACTION: Check to see if the field number entered is greater than zero.

CAUSE: A closing quote is needed.

ACTION: Retype the erroneous string with a closing quote.

CAUSE: The user tried to perform some maint mode command like SUMMARYCONF, COMPRESSCONF, PATHCONF, etc. that requires an open file.

ACTION: Open a config file with the OPENCONF command first.

CAUSE: You specified an invalid LDEV range while using the SUMMARYCONF command to obtain a DTS critical summary report on a range of logical devices.

ACTION: Reenter the SUMMARYCONF command with a correctly specified LDEV range. The LDEV range must be separated by a slash. (Example: SUMMARYCONF DTS,LDEV 35/83)

CAUSE: While using the SUMMARYCONF command to obtain a DTS critical summary report, you specified one or more of the parameters as a non-integer. The correct format for the LDEV specification is LDEV [xxx[/yyy]], where xxx and yyy are integers.

ACTION: Reenter the command with the parameters specified as integers.

CAUSE: While using the SUMMARYCONF command to obtain a DTS critical summary report on a range of logical devices, you entered more data than was expected in the command line.

ACTION: Reenter the command with the parameters specified in the correct format (LDEV [xxx[/yyy]], where xxx and yyy are integers).

CAUSE: While using the SUMMARYCONF command to obtain a DTS critical summary report on a range of logical devices, the first LDEV number you specified was higher than the second LDEV number you specified. This is an invalid range specification.

ACTION: Reenter the command with the LDEV range specified correctly, with the first number in the range lower than the second number in the range.

CAUSE: While using the SUMMARYCONF command to obtain a DTS critical summary report on a range of logical devices, you specified a valid range; however, there are no LDEVs within that range.

ACTION: Reenter the command with a correct range of logical devices specified (one that includes LDEVS).

CAUSE: You specified an incorrect DTC name while using the SUMMARYCONF command to obtain a DTS critical summary report on a specific DTC. Either the DTC does not exist or no data has been configured for that DTC.

ACTION: If the name was entered incorrectly, reenter the SUMMARYCONF command with the correct DTC name specified. If the DTC exists but is not correctly configured, use NMMGR to configure the data for the DTC, then reenter the SUMMARYCONF command.

CAUSE: You specified an incorrect card number while using the SUMMARYCONF command to obtain a DTS critical summary report on a specific DTC. Either the DTC does not exist or the card specified is not configured for that DTC.

ACTION: Reenter the command with the correct card number and DTC specified. If the card exists but is not properly configured, use NMMGR to correct the card configuration, then reenter the SUMMARYCONF command.

CAUSE: You specified an incorrect port number while using the SUMMARYCONF command to obtain a DTS critical summary report on a specific card in a specific DTC. Either the DTC does not exist, the card specified is not configured for that DTC, or the port is not configured for that card.

ACTION: Reenter the command with the correct port number, card number, and DTC specified. If the port exists but is not properly configured, use NMMGR to correct the configuration, then reenter the SUMMARYCONF command.

CAUSE: You entered a SUMMARYCONF DTS command on a system where no distributed terminal subsystem is configured (the HOST/PC flag has not been set).

ACTION: Configure the distributed terminal subsystem, then reenter the SUMMARYCONF DTS command.

CAUSE: While using the SUMMARYCONF command to obtain a DTS critical summary report, you entered an illegal delimiter.

ACTION: Type HELP at the prompt to access the HELP messages for the SUMMARYCONF command. Study these messages to determine the proper syntax to obtain the desired information. Reenter the command using the correct delimiters.

CAUSE: While using the SUMMARYCONF command to obtain a DTS critical summary report on a specific card in a DTC, you entered an invalid card number. Card numbers must be entered as integers, from 0 to 5.

ACTION: Reenter the command with a card number specified in the valid range, 0 through 5.

CAUSE: While using the SUMMARYCONF command to obtain a DTS critical summary report on a specific port, you entered an invalid port number. Port numbers must be entered as integers, from 0 to 7.

ACTION: Reenter the command with a port number specified in the valid range, 0 through 7.

CAUSE: You entered a SUMMARYCONF DTS command that ended in a delimiter when another parameter could have been entered. For example, you may have entered "LDEV 23/" instead of "LDEV 23".

ACTION: Reenter the command correctly. Type HELP to access the help messages if you do not know the correct syntax for the command you are trying to enter.

CAUSE: You entered a SUMMARYCONF DTS command that ended in a delimiter (",", "/", etc.)

ACTION: Reenter the command correctly. Type HELP to access the help messages if you do not know the correct syntax for the command you are trying to enter.