NMCN Error and Warning Messages
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| Index |
| nn | Subsystem |
|---|---|
| 0 | Node Management Services (30299-11017) |
| 1 | SNA Transport (32099-11015) |
| 2 | SNA/NRJE (Product #30245) |
| 3 | Network Transport (Product #30242) |
| 4 | Port Translator (30299-11017) |
| 5 | Sockets |
| 6 | Network Services (Product #32344) |
| 7 | Buffer Manager (30299-11016) |
| 8 | Link Manager (part of Node Management Services) |
| 9 | Reserved for future use |
| 10 | Reserved for future use |
| 11 | SNA/IMF |
| 12/15 | Reserved for future use |
NMNC Errors 1 - 80
| MESSAGE: NMMON: Unable to allocate area for port table. (NMCNERR 1) |
| Level: NMCNERR 1
CAUSE: NMMON is unable to expand the DL-DB area in its stack. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NMMON: Unable to obtain port data segment. (NMCNERR 2) |
| Level: NMCNERR 2
CAUSE: INITPORTDST returned a DST number of 0. The system is unable to allocate any extra data segments. ACTION: See "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NMMON: Unable to create port in data segment. (NMCNERR 3) |
| Level: NMCNERR 3
CAUSE: CREATEPORT returned a PORTID of 0. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NMMON: Unable to add port dictionary entry. (NMCNERR 4) |
| Level: NMCNERR 4
CAUSE: DICTADD returned a nonzero result. ACTION: See "Submitting a CRSubmitting a CR" at the beginning of this appendix. |
| MESSAGE: NMMON: CREATEPROCESS error n on NMFILE.PUB.SYS. (NMCNERR 5) |
| Level: NMCNERR 5
CAUSE: CREATEPROCESS failed for NMFILE. The NMFILE.PUB.SYS program file might not be present, or might not be Load-able. This could happen if the NMS software is not correctly installed, or if there is a mismatch between NMFILE and SL module versions. Also, there could be other MPE limitations such as insufficient table space. ACTION: Look up the CREATEPROCESS error number in the Intrinsics Reference Manual. Correct this error. See also "Invalid Software Installation" and "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NMMON: CREATEPROCESS error n on NMLOGMON.PUB.SYS. (NMCNERR 6) |
| Level: NMCNERR 6
CAUSE: CREATEPROCESS failed for NMLOGMON. The NMLOGMON.PUB.SYS program file might not be present, or might not be Load-able. This could happen if the NMS software is not correctly installed, or if there is a mismatch between NMLOGMON and SL module versions. Also, there could be other MPE limitations such as insufficient table space. ACTION: Look up the CREATEPROCESS error number in the Intrinsics Reference Manual. Correct this error. See also "Invalid Software Installation" and "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NMMON: NMS version mismatch. NMS-based datacomm unavailable. (NMCNERR 7) |
| Level: NMCNERR 7
CAUSE: Version mismatch detected in the Node Management Services subsystem software modules installed on the system. ACTION: See "Invalid Software Installation" at the beginning of this appendix. |
| MESSAGE: NMMON: Restart request rejected; not in proper state [!]. (NMCNERR 8) |
| Level: NMCNERR 8
CAUSE: User attempted to perform an unsupported function. ACTION: Use method supported by Hewlett Packard to achieve your goal. If uncertain, contact your HP representative. |
| MESSAGE: NMMON: Programmatic shutdown request rejected; not in proper state [!]. (NMCNERR 9) |
| Level: NMCNERR 9
CAUSE: User attempted to perform an unsupported function. ACTION: Use method supported by Hewlett Packard to achieve your goal. If uncertain, contact your HP representative. |
| MESSAGE: NMMON: CREATEPROCESS error n on NMINIT.PUB.SYS. (NMCNERR 11) |
| Level: NMCNERR 11
CAUSE: CREATEPROCESS failed for NMINIT. The NMINIT.PUB.SYS program file might not be present, or might not be Load-able. This could happen if the NMS software is not correctly installed, or if there is a mismatch between NMFILE and SL module versions. Also, there could be other MPE limitations such as insufficient table space. ACTION: Look up the CREATEPROCESS error number in the Intrinsics Reference Manual. Correct this error. See also "Invalid Software Installation" and "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NM Log Monitor: Another MainLogMonitor exists. This one terminating. (NMCNERR 16) |
| Level: NMCNERR 16
CAUSE: A Main Log Monitor process has found its entry already exists in the port dictionary. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Monitor: Unable to obtain port data segment. (NMCNERR 17) |
| Level: NMCNERR 17
CAUSE: INITPORTDST returned a DST number of 0. The system is unable to allocate any extra data segments. ACTION: See "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NM Log Monitor: Unable to create port in data segment. (NMCNERR 18) |
| Level: NMCNERR 18
CAUSE: CREATEPORT returned a PORTID of 0. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Monitor: Unable toadd port in dictionary entry. (NMCNERR 19) |
| Level: NMCNERR 19
CAUSE: DICTADD returned a nonzero result. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Monitor: Unable to add to NM Monitor port table. (NMCNERR 20) |
| Level: NMCNERR 20
CAUSE: NMMONADDID failed for MainLogMonitor. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Monitor: Unable to create user logging data segment. (NMCNERR 21) |
| Level: NMCNERR 21
CAUSE: Main Log Monitor is unable to acquire an extra data segment. ACTION: See "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NM Log Monitor: Unable to create trace dictionary data segment. (NMCNERR 22) |
| Level: NMCNERR 22
CAUSE: Main Log Monitor is unable to acquire an extra data segment. ACTION: See "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NM Log Monitor: Input/Output error in accessing the system disc cold load area. (NMCNERR 23) |
| Level: NMCNERR 23
CAUSE: An error occurred trying to access the area of disk where the next NMLGnnnn, and NMTCnnnn, file name numbers are stored. Check for other error indications that may affect the system disks, including I/O errors. ACTION: Correct any situation that may cause disk I/O errors. If the problem persists, see "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Monitor: Illegal parameter passed; create failed. (NMCNERR 24) |
| Level: NMCNERR 24
CAUSE: The user has attempted to enter a parameter which is not valid. ACTION: Check input parameters and try again. |
| MESSAGE: NM Log Monitor: CREATEPROCESS error n on NMLOGMON.PUB.SYS. (NMCNERR 25) |
| Level: NMCNERR 25
CAUSE: CREATEPROCESS failed for NMLOGMON. The NMLOGMON.PUB.SYS program file might not be present, or might not be Load-able. This could happen if the NMS software is not correctly installed, or if there is a mismatch between NMLOGMON and SL module versions. Also, there could be other MPE limitations such as insufficient table space. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Process: Internal error trying to set up NMS logging. (NMCNERR 26) |
| Level: NMCNERR 26
CAUSE: An unexpected error has occurred. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Process: Unable to obtain port data segment. (NMCNERR 30) |
| Level: NMCNERR 30
CAUSE: INITPORTDST returned a DST number of 0. The system is unable to allocate any extra data segments. ACTION: See "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NM Log Process: Unable to create port data segment. (NMCNERR 31) |
| Level: NMCNERR 31
CAUSE: CREATEPORT returned a PORTID of 0. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Process: Unable to add port dictionary entry. (NMCNERR 32) |
| Level: NMCNERR 32
CAUSE: DICTADD returned a nonzero result. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Process: Unable to add to NM Monitor port table. (NMCNERR 33) |
| Level: NMCNERR 33
CAUSE: NMMONADDID failed for MainLogMonitor. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NM Log Process: Unable to create logging buffer data segment. (NMCNERR 34) |
| Level: NMCNERR 34
CAUSE: NM Log Process is unable to acquire an extra data segment. ACTION: See "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NMLG FILE NUMBER nnnn ERROR #nnn. NM LOGGING STOPPED. (NMCNERR 36) |
| Level: NMCNERR 36
CAUSE: If the error number is greater than 1, this is the file system error that occurred when accessing file NMLGnnnn, where nnnn is the file number specified. If the error number is 1, then see the comments to NMCNERR 23. ACTION: Correct this problem, then type RESUMENMLOG. |
| MESSAGE: NMLG FILE NUMBER nnnn ERROR #nnn. NM LOGGING SUSPENDED. (NMCNERR 38) |
| Level: NMCNERR 38
CAUSE: If the error number is greater than 1, this is the file system error that occurred when accessing file NMLGnnnn, where nnnn is the file number specified. If the error number is 1, refer to message NMCNERR 23. ACTION: Correct this problem, then type RESUMENMLOG. |
| MESSAGE: UNABLE TO ACCESS NMLG FILE NUMBER nnnn. (NMCNERR 42) |
| Level: NMCNERR 42
CAUSE: The log buffer indicates the logging state is normal or suspended, but it contains a current file number of zero, or FFILEINFO returned a < > condition on the file. ACTION: Try typing RESUMENMLOG. If SHOWNMLOG after this gives this message again, try rebooting the system to force logging to open a new NMLGnnnn file. |
| MESSAGE: NM Log Process: Unable to create log dictionary data segment. (NMCNERR 44) |
| Level: NMCNERR 44
CAUSE: NM Log Process is unable to acquire an extra data segment. ACTION: See "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NM Log Process: Cannot format log msg. Cannot access formatter for subsystem !. Encountered LOADPROC error !. (NMCNERR 45) |
| Level: NMCNERR 45
CAUSE: A request to write a formatted log message specifies an NMS subsystem number where formatter Log Process was unable to LOADPROC. ACTION: The SUBSYSnLOGFORMA procedure, where n is the subsystem number specified in the message, either did not exist in SL.PUB.SYS or could not be loaded when NM Log Process started. Look up the LOADPROC error number in the MPE Intrinsics Reference Manual. Correct this error. Check that NMS subsystem n is completely, correctly installed. See "Invalid Software Installation" and "Insufficient MPE Resources" at the beginning of this appendix. |
| MESSAGE: NM Log Process: Cannot format log msg. Unknown subsystem nn. (NMCNERR 46) |
| Level: NMCNERR 46
CAUSE: A request to write a formatted log message specifies an unknown NMS subsystem number. ACTION: This is an internal error. See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: NMLG FILES mmmm THRU nnnn SKIPPED. (NMCNERR 47) |
| Level: NMCNERR 47
CAUSE: NM log files mmmm through nnnn were skipped over when NMS Logging tried to open a new disk log file. Files NMLGmmmm.PUB.SYS through NMLGnnnn.PUB.SYS already exist. This is an information message only; no error occurred. ACTION: None. |
| MESSAGE: NMLG FILES 0000 THRU 9999 ALL USED, NONE AVAILALBLE FOR NEXT LOGFILE. (NMCNERR 48) |
| Level: NMCNERR 48
CAUSE: NMS Logging finds that files NMLG0000 through NMLG9999 all already exist. It is more likely that a directory problem or an internal problem exists. ACTION: See "Submitting a CR" at the beginning of this appendix. |
| MESSAGE: MainLogMon: NMGLOBAL file found, purged (not needed for this version). (NMCNMSG 49) |
| Level: NMCNMSG 49
CAUSE: Privileged file NMGLOBAL.PUB.SYS was found. This file is not needed in this version of NMS software. The file information is transferred to the Cold Load area of disk, and the file is purged. ACTION: None. Informative message. |
| MESSAGE: NM Log Process: Cannot access NMCAT.PUB.SYS to format a log msg. (NMCNERR 50) |
| Level: NMCNERR 50
CAUSE: NM Log Process could not open the message catalog and so could not format a logging message. ACTION: See "Invalid Software Installation" at the beginning of this appendix. |
| MESSAGE: NM Log Process: Logging class ! not configured for subsystem ! in !. (NMCNERR 51) |
| Level: NMCNERR 51
CAUSE: A logging message was received from NMS subsystem m that specified log class n. However, log class n is not configured. The log message is discarded. ACTION: Use NMMGR to configure logging class n under subsystem m in the specified configuration file. The NMMGR subtree is LOGGING. SUBmmmm.CLASnnnn, where mmmm is the subsystem number m with leading zeros, and nnnn is the class number n with leading zeros. |
| MESSAGE: Link Manager unable to open NM logging. (NMCNWARN 70) |
| Level: NMCNWARN 70
CAUSE: A Link Manager process encountered an error from NMOPENLOG. ACTION: The specific NMERR will be reported in a console message immediately following this message. The Link Manager process will continue to execute, but will be unable to log any errors, including I/O errors. |
| MESSAGE: Trace Manager unable to open NM logging. (NMCNWARN 71) |
| Level: NMCNWARN 71
CAUSE: NMCONFIG does not have logging subsystem 18 configured. ACTION: None required. |
| MESSAGE: Linkname Table creation error, subsys=! info=!. (NMCNERR 80) |
| Level: NMCNERR 80
CAUSE: System call failure. ACTION: Reboot the system. |
|
Submitting a CR |
NMDUMP Error and Warning Messages |