System Software Library NonStop NET/MASTER Messages Manual Abstract Part Number Edition Published Product Version Release ID Supported Releases This manual describes the NonStop NET/MASTER messages and Network Control Language (NCL) error codes.. 106159 First December 1994 NonStop NET/MASTER D30 D30.00 This manual supports D30.00 and all subsequent releases until otherwise indicated in a new edition.
Document History Edition Part Number Product Version Earliest Supported Release Published Third 106159 D30 D30.00 December 1994 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT).
New and Changed Information This edition of the NonStop NET/MASTER Messages Manual contains the following new or changed information: The manual contains the following general updates: References to “Guardian 90” have been changed to reflect Tandem’s current and future operating system enhancements that further enable open systems and application portability.
New and Changed Information NNM1059 updated to include error number. NNM1078 and NNM1079 help updated to include new scopes for variables. NNM1092 through NNM1099, NNM2700, NNM2702 through NNM2707, and NNM2759 through NNM2761 added for NCL and panel objects. NNM1104 help updated. NNM1357 through NNM1359, and NNM2750, added for the #INCLUDE statement. NNM1394 through NNM1396 added for the #TRAILER statements. NNM1397 and NNM2375 deleted. NNM1503 help updated. NNM1545 added for activity log I/O errors.
Contents About This Manual Section 1 vii Introduction Looking for Additional Information 1-1 What to Prepare Before Contacting Your Tandem Support Representative Software Version Logs 1-2 1-2 Startup and Configuration Files 1-2 NCL Procedure or Panel Problem 1-2 DSNM Problem Terminal Problem 1-3 1-3 Messages Messages 2-1 NCL Error Codes NCL Error Codes Error Names Section 4 1-3 1-3 Additional Information Section 3 1-2 Process Abends, Hangs, or Loops Communications Problem Section 2
Contents Figures Figure 1. Documentation Road Map ix Tables Table 3-1.
About This Manual Purpose This manual describes the NonStop NET/MASTER messages and Network Control Language (NCL) error codes. The manual provides you with information on what recovery actions to take when an error occurs. Who Should Read This Any NonStop NET/MASTER user may need to use this manual. You should refer to Manual this manual for further information when you receive a NonStop NET/MASTER message.
About This Manual Your Comments Invited Also, you might find the following IBM manual helpful: Systems Network Architecture: Formats Your Comments Invited viii After you have had a chance to use this manual, please take a moment to fill out the Reader Comment Card and send it to us. The Reader Comment Card is located at the back of the printed manual and as a separate file in the CD Read Document List.
About This Manual Documentation Road Map Figure 1.
About This Manual Documentation Road Map (This page left intentionally blank) x 106159 Tandem Computers Incorporated
1 Introduction Looking for Additional This manual refers to topics that are discussed in more detail elsewhere.
Introduction What to Prepare Before Contacting Your Tandem Support Representative What to Prepare Some of the problems that you encounter might require you to contact your Tandem Before Contacting support representative. Before you contact your representative, ensure that you gather Your Tandem Support the relevant information identified in the following sections.
Introduction What to Prepare Before Contacting Your Tandem Support Representative Communications Problem If there is an Inter-NET/MASTER Connection (INMC) problem, gather the NonStop NET/MASTER MS version number, and the SOLVE management services version numbers, if applicable. Gather these version numbers as they pertain to any intermediate nodes as well. If the connection is to a SOLVE system, gather the IBM ACF/VTAM version information.
Introduction What to Prepare Before Contacting Your Tandem Support Representative A list of any warning or error messages which took place before and after the problem occurred. The location of the hometerm, the EMS log, and the activity log files. Any other information, as stated in the explanation of the pertinent error messages.
2 Messages Messages NonStop NET/MASTER messages provide operational information about your NonStop NET/MASTER MS system. Where a message signifies a problem, recovery guidelines are given here that can help you to solve it. NNM0001 objfile - PROCESS MUST BE NAMED Cause. The startup procedure was altered such that the control process was not named. All processes in the NonStop NET/MASTER MS system must be named. objfile is the file name of the object code of the process. Effect.
Messages NNM0004 NNM0004 TRACE DISABLED, IO ERROR ON OUTPUT FILE filename (errno) Cause. The trace failed because there was an error with the file. filename is the file name specified by the TRACEFILE system parameter. errno is the Guardian file-system error number. Effect. Tracing is disabled. Recovery. Use the error number to determine the appropriate action to take. NNM0005 WARNING - $RECEIVE DEPTH OF queue_depth HAS BEEN REACHED Cause. An internal queueing problem occurred.
Messages NNM0008 NNM0007 WARNING - $RECEIVE MESSAGE DISCARDED, NO EPC ENTRY Cause. The NonStop NET/MASTER MS process received an unexpected message. Effect. The message is discarded. Recovery. Refer the message to your system manager.
Messages NNM0009 NNM0009 process_name (objfile) ABENDING, TRAP=trapid, THRDID=thrdss/thrdno, trapname Cause. A system trap occurred in the process. process_name is the name of the failed process. objfile is the file name of the object code that caused the problem. trapid is an ID to help your Tandem support representative identify the problem. thrdss thrdno is the identification for the thread. trapname is the name of the trap that occurred. Effect. The process abends.
Messages NNM0013 NNM0012 process_name ENGINE MEMORY CRITICAL PERIOD OVER Cause. The memory shortage for the process is over. process_name is the name of the process whose memory critical period has passed. Effect. Normal operation resumes. Recovery. This message is informational only; no recovery action is necessary. NNM0013 NAME READY WAIT IO FILES MEMORY(KB) QUEUES Cause. A SHOW ENGINE command was issued and the message is part of the response. The line contains the headings of the display.
Messages NNM0014 NNM0014 process_name cur-ready/max-ready cur-wait/max-wait cur-io/maxio cur-files/max-files mem-used/mem-avail(crit) queues Cause. A SHOW ENGINE command was issued and the message is part of the response. The line contains information about the engine that may be useful to Tandem support representatives. process_name is the name of the process. cur-ready is the number of threads that are currently ready. max-ready is the maximum number of threads that were ready at one time.
Messages NNM0018 NNM0016 STACK TRACE framenumber #functionname + %instrcountI Cause. When a process abends, a series of messages is issued. The messages form a single set, ordered by increasing framenumber. functionname and instrcount help Tandem support representatives to identify the problem. Effect. The process abends. If the process is a static process, it is restarted. Recovery.
Messages NNM0019 NNM0019 COUNT=record_limit PAGES=page_limit WRAP=wrap_flag RECSIZE=record_size Cause. This message is a response to a SHOW TRACE command. The line contains information about the trace statistics being displayed. record_limit is the number that limits the number of records written to the trace file. page_limit is the number that limits the number of pages used by the trace collector to store trace data.
Messages NNM0023 NNM0022 PARAMETER IN ERROR: paramname Cause. A TRACE command was issued, but an invalid operand value was specified. is the invalid value. paramname Effect. The command is ignored. Recovery. Specify a valid value to correct the command, and retry. NNM0023 COMMAND AUTH OP-AUTH NOTE EQUATE TEXT Cause. A SHOW COMMANDS command was issued, and the message is part of the response. The line contains the headings for information about NonStop NET/MASTER MS commands.
Messages NNM0024 NNM0024 command-name cmdrepl-flag command-authority equate-name operand-authority Cause. A SHOW COMMANDS command was issued, and the message is part of the response. The line contains information about a NonStop NET/MASTER MS command. command-name is the name of a NonStop NET/MASTER command. command-authority is the authority level required to issue the command. operand-authority is the highest authority level found for the operands of the command.
Messages NNM0029 NNM0026 TRACE COMMAND UNRECOGNIZED Cause. The command entered was not recognized by command services. Effect. The command is ignored. Recovery. Correct the command and retry. NNM0027 TRACE COMMAND ACCEPTED Cause. The TRACE command was accepted. Effect. The command is successfully processed. Recovery. This message is informational only; no recovery action is necessary. NNM0028 TRACE COLLECTOR NOT STARTED. NO TRACE POINTS DECLARED Cause.
Messages NNM0030 NNM0030 ERROR OPENING TRACE COLLECTOR process_name ERROR errno Cause. A TRACE START command failed to open the trace collector. process_name is the name of the trace collector process. errno is the Guardian file-system error number. Effect. The trace collector is unavailable for use. Recovery. Use the error number to determine the appropriate action to take. After you have rectified the problem, use the TRACE START command to restart the interface.
Messages NNM0036 NNM0033 INVALID FILENAME SPECIFIED=filename Cause. A TRACE START=filename command was issued but the file name was incorrect. filename is the file name specified in the TRACE START command. Effect. The command is ignored. Recovery. The file name must be of the form [\system.]$volume.subvolume.name. Correct the file name specification and reissue the command. NNM0034 ERROR ALTERING TRACE COLLECTOR process_name ERROR errno Cause.
Messages NNM0037 NNM0037 TRACE COLLECTOR ERROR=errno, PROCESS=process_name Cause. An error occurred in the trace collector process. errno is the Guardian file-system error number. process_name is the name of the trace collector process. Effect. The trace collector is stopped. Recovery. Use the error number to determine the appropriate action to take. After you have corrected the problem, issue the TRACE command to set up your trace settings, then issue the TRACE START command to restart the trace.
Messages NNM0042 NNM0040 TRACE COLLECTOR process_name NOT STARTED. UNABLE TO OBTAIN LOCK FOR TRACEID Cause. A TRACE START command was issued but the trace collector could not be started because a unique trace ID could not be allocated due to an inability to obtain a global memory manager (GMM) lock. process_name is the name of the trace collector process. Effect. The command is ignored. Recovery. Retry the command at a later time. NNM0041 TRACE COLLECTOR process_name NOT STARTED.
Messages NNM0043 NNM0043 TRACING NOT INITIALIZED IN process_name PROCESS. MEMORY SHORTAGE Cause. A trace creation event was received by the NonStop NET/MASTER MS process, process_name, but the process could not initialize the trace collector because of a memory shortage. Effect. Trace events are not sent from this process to the trace collector. Recovery.
Messages NNM0048 NNM0046 TRACE RECORD NOT SENT FROM process_name PROCESS. MEMORY SHORTAGE Cause. A trace record was about to be sent from the NonStop NET/MASTER MS process, process_name, to the trace collector but memory could not be obtained to create the interprocess message. Effect. The message that was being traced is ignored. Recovery. Refer the message to your system manager. The manager should try to recover space on the swap disk volume.
Messages NNM0050 NNM0050 LINK NAME MODE MSGID COLOR HLITE BKGCOLOR Cause. A SHOW LINKS=linkname command was issued and the message is part of the response. The line contains the headings for information about the INMC link. Other messages provide the actual information. LINK NAME is the heading for the name of the INMC link. MODE is the heading for the mode of delivery of data to each unit in the link.
Messages NNM0052 NNM0052 LINK NAME NUM STATUS MODE MSGID PEER Cause. A SHOW LINKS command was issued and the message is part of the response. The line contains the headings of the SHOW LINKS display. Other messages provide the actual information. LINK NAME is the heading for the name of an INMC link. NUM is the heading for the link number. STATUS is the heading for the status of the link. The status is one of the following: ACTIVE indicates that the link is active.
Messages NNM0053 NNM0053 linkname linknum status ROTATE msgid HOST Cause. A SHOW LINKS command was issued and the message is part of the response. The line contains information about an INMC link. linkname is the name of the INMC link. linknum is the link number. status is the status of the link. The status is one of the following: msgid ACTIVE indicates that the link is active. PEND-ACT indicates that the link is pending active. STOPPED indicates that the link is stopped.
Messages NNM0057 NNM0056 SESSION NAME LINK NAME TYPE APPLID Cause. A SHOW LINKS=linkname command was issued and the message is part of the response. The line contains the headings for information about a session on the INMC link. Other messages provide the actual information. SESSION NAME is the heading for the name of a session. LINK NAME is the heading for the name of the INMC link. TYPE is the heading for the type of session. The type is one of the following: LU0 indicates an SNA session type.
Messages NNM0058 NNM0058 sessname sessnum status Cause. A SHOW LINKS command was issued and the message is part of the response. The line contains information about a session. sessname is the name of the session. sessnum is the session number. status is the status of the session. The status is one of the following: ACTIVE, PEND-ACT (pending active), or STOPPED. Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM0061 NNM0061 UNIT NAME DEVICE MODE SIZE DELAY Cause. A SHOW LINKS=linkname command was issued and the message is part of the response. The line contains the headings for information about a unit. Other messages provide the actual information. UNIT NAME is the heading for the name of a unit. DEVICE is the heading for the device name of the unit. MODE is the heading for the mode of operation.
Messages NNM0062 NNM0062 unitname devname mode size delay Cause. A SHOW LINKS=linkname command was issued and the message is part of the response. The line contains information about a unit. unitname is the name of the unit. devname is the device name of the unit. mode is the mode of operation. The mode is one of the following: ACTV indicates an active switched virtual circuit (SVC) in an X.25 session. PASS indicates a passive SVC in an X.25 session.
Messages NNM0067 NNM0064 dteaddr sessname Cause. A SHOW LINKS=linkname command was issued and the message is part of the response. The line contains information about a unit. dteaddr is the data-terminal equipment (DTE) address (analogous to a telephone number) of the called party. sessname is the name of the session using the unit. Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM0065 UNIT NAME Cause.
Messages NNM0068 NNM0068 INMC MEMORY SHORTAGE - RESETTING LINK=linkname Cause. The INMC software was unable to perform an operation because of a memory shortage in the process where it was running. This is usually caused by a shortage of disk space on the volume where the NonStop NET/MASTER MS process swap file resides. linkname is the name of the INMC link that is being reset. Effect. The link on which the operation was being performed is reset automatically and can no longer be used.
Messages NNM0071 NNM0070 LINK FROM NNMid TO linkname NOW INACTIVE Cause. An INMC link that was operational has just become inactive. NNMid is the ID of the NonStop NET/MASTER MS system. linkname is the name of the INMC link. Effect. Software components such as ROC and ISR that wish to make use of the now inactive link are no longer able to do so. Recovery. If the link became inactive as a result of LINK STOP or LINK RESET, then this message is informational only; no recovery action is necessary.
Messages NNM0072 NNM0072 RDID LINKNAME NMID NETWORK VTAM/NOD N/M OPSYS STATUS Cause. A SHOW DOMAINS command was issued and the message is part of the response. The line contains the headings of the SHOW DOMAINS display. Other messages provide the actual information. RDID is the heading for the domain ID of a remote system. LINKNAME is the heading for the name of the INMC link to the remote system. NMID is the heading for the NonStop NET/MASTER MS or SOLVE ID of the remote system.
Messages NNM0074 NNM0073 domain-id link-name system-id network-name nm-or-nnm version-number os-version information-status Cause. A SHOW DOMAINS command was issued, and the message is part of the response. The line contains information about a domain. domain-id is the domain ID of the remote system. link-name is the name of the INMC link to the remote system. system-id is the NonStop NET/MASTER MS or SOLVE ID of the remote system. network-name is the network name of the remote system.
Messages NNM0075 NNM0075 component-type name NOT DEFINED Cause. A LINK START, LINK DELETE, SESSION DELETE, or UNIT DELETE command was issued but the indicated link, session, or unit name was not found. This could be because the specified object has already been deleted or because the name was misspelled. component-type is LINK, SESSION, or UNIT. name is the name of the INMC link, session, or unit specified. Effect. The command is ignored and no further action is taken. Recovery.
Messages NNM0077 NNM0077 INMC OPEN ERROR errno, LINK= linkname DEVICE= devname Cause. A LINK START command was issued but the INMC software was unable to open the configured X.25 or SNA device because of the error. errno is the Guardian file-system error number. linkname is the name of the INMC link. devname is the name of the device that cannot be opened. Effect. The INMC subsystem will continue to try to acquire the device, each time displaying the message while the problem persists.
Messages NNM0078 NNM0078 DOMAIN ID REJECTED, LINK=linkname, LOCALDID=ldomainid, REMOTEDID=rdomainid Cause. It was not possible to start an INMC link with a remote system because the remote system had rejected the domain ID used for this NonStop NET/MASTER MS system. linkname is the name of the INMC link. ldomainid is the domain ID of this NonStop NET/MASTER MS system. rdomainid is the domain ID of the remote system. Effect. The link is considered faulty and cannot be used.
Messages NNM0081 NNM0081 INMC COMBINATION NOT SUPPORTED. ACCESS METHOD type WITH PRIMARY mode. UNIT unitname LINK linkname Cause. A LINK START command was issued, and the INMC software was validating the configuration of the INMC link that it was asked to start. It found that the configured session type (PTP, SNALU0, or X25) was inconsistent with the configured mode of operation for the unit. For example, an X.
Messages NNM0082 NNM0082 FATAL INMC UNIT ERROR LINK=linkname DEVICE=devname ERROR=errno Cause. A fatal input-output error occurred on an LU0 or X.25 device. linkname is the name of the INMC link. devname is the name of the device that caused the error. errno is the Guardian file-system error number. Effect. The unit whose device encountered the error becomes inoperative and will not be used for any further INMC traffic.
Messages NNM0088 NNM0086 component-type name ALREADY DEFINED Cause. A LINK DEFINE, SESSION DEFINE, or UNIT DEFINE command failed because the name used was already in use. component-type is LINK, SESSION, or UNIT. name is the name of the link, session, or unit specified. Effect. The command is ignored and no further action is taken. Recovery. Check the name of the INMC link, session, or unit being defined.
Messages NNM0089 NNM0089 INMC ACCESS METHOD type DOES NOT CORRESPOND TO DEFINITION OF LINK=linkname UNIT=unitname Cause. This message appears after a LINK START command was issued. The INMC software was validating the configuration of the link that it was asked to start. It found that the type of the device specified in the DEVICE setting of the unit definition was not consistent with the TYPE setting of the session definition under which the unit was configured. For example, the name of an X.
Messages NNM0101 NNM0100 INITIALIZATION FAILED ON LINK=linkname, DEVICE=devname Cause. The INMC SNALU0 software received a message that is not an INMC protocol message. This message commonly appears when an attempt is made to connect to a remote SOLVE system, but the remote system assumes that it is communicating with a 3270 terminal and sends a 3270 data stream. linkname is the name of the INMC link. devname is the name of the device. Effect.
Messages NNM0102 NNM0102 PACING INDICATORS IN BIND NOT SUPPORTED, LINK=linkname DEVICE=devname Cause. A LINK START command was issued and the INMC software is attempting to establish an LU-LU session with the remote system. The remote system has indicated in its BIND message that it wishes to use pacing, however the INMC software does not support pacing. linkname is the name of the INMC link being started. devname is the name of the device. Effect.
Messages NNM0203 NNM0104 INMC LU0 NEGATIVE RSP, SENSE=sense1 sense2, LINK=linkname DEVICE=devname Cause. A LINK START command was issued and the INMC software is attempting to establish an LU-LU session with the remote system. The remote system has issued a Negative Response message instead of a BIND message. sense1 is one of two sense codes received. sense2 is one of two sense codes received. linkname is the name of the INMC link being started. devname is the name of the device. Effect.
Messages NNM0204 NNM0204 MUTUALLY EXCLUSIVE ARGUMENTS SPECIFIED Cause. A command was issued but mutually exclusive operands were specified. Effect. The command is rejected. Recovery. Remove the conflict and retry the command. NNM0205 ARGUMENTS DUPLICATED Cause. A command was issued but a specified operand was duplicated. Effect. The command is rejected. Recovery. Remove the duplication and retry the command. NNM0206 INVALID OPSYS COMMAND 'text_string' Cause.
Messages NNM0211 NNM0208 INVALID OPERAND VALUE - MISSING QUOTE Cause. A command was issued but the value of a specified operand had mismatching quotation marks. Effect. The command is rejected. Recovery. Ensure that the quotation marks match and retry the command. NNM0209 COMMAND IS NOT VALID FROM TIMER COMMAND Cause. A timer command was issued but an invalid command was specified in the command string. Effect. The command is rejected. Recovery.
Messages NNM0212 NNM0212 THE COMMAND NEEDS A TERMINAL Cause. A command that required an interactive environment (a terminal) for execution was issued in a noninteractive environment. Effect. The command is rejected. Recovery. Do not use the command in ROC or background environments. NNM0213 NUMERIC VALUE TOO LARGE - 'operand-value' Cause. A command was issued and an operand that required a numeric value was specified. The value specified for the operand was numeric but too large.
Messages NNM0219 NNM0216 NO VALUE IS REQUIRED FOR OPERAND 'operand' Cause. A command was issued but an operand that does not require a value was given a value. operand identifies the operand that caused the problem. Effect. The command is rejected. Recovery. Specify the operand without a value and retry the command. NNM0217 THE VALUE 'opvalue' IS INVALID, A CHARACTER IS EXPECTED Cause. A command was issued and an operand that requires a single character as the value was specified.
Messages NNM0220 NNM0220 UNSIGNED NUMERIC VALUE IS REQUIRED - 'opvalue' Cause. A command was issued and an operand that required an unsigned numeric value was specified. The value specified for the operand either was not numeric or was a signed numeric value. opvalue is the value in error. Effect. The command is rejected. Recovery. Replace the value with an unsigned number, and retry the command. NNM0221 INVALID OPERAND RESERVED VALUE - 'opvalue' Cause.
Messages NNM0226 NNM0224 command COMMAND CANNOT RUN WHILE 'PROGRUN' IS ACTIVE Cause. A command was issued in a window but a PROGRUN command has control of the window. The window could not accept other commands. Effect. The command is rejected. Recovery. Retry the command after the PROGRUN command has completed. NNM0225 PROCEDURE NAME: procname IS NOT AN EXACT COMMAND NAME Cause. A SYSPARMS CMDREPL=procname command was issued but procname was not the full name of a command.
Messages NNM0227 NNM0227 COMMAND: procname OVERRIDDEN BY A GLOBAL EQUATE, NOT REPLACEABLE BY AN NCL PROCEDURE Cause. A SYSPARMS CMDREPL=procname command was issued for a globally equated command. You cannot replace a globally equated command by an NCL procedure of the same name. procname is the name of the procedure that was to replace the globally equated command of the same name. Effect. The globally equated command is not replaced. Recovery.
Messages NNM0234 NNM0231 EQUATE STRING CONTAINS INVALID CHARACTERS Cause. An EQUATE command was issued but a name string that contained invalid characters was specified. The string cannot contain the characters - and ?. Effect. The command is rejected. Recovery. Correct the string and retry the command. NNM0232 NO EQUATE TEXT SPECIFIED Cause. An EQUATE command was issued but no text value to be represented by the name string was specified. Effect. The name string is not created. Recovery.
Messages NNM0235 NNM0235 TEXT SET FOR EQUATE STRING eqstr Cause. An EQUATE command was issued and the name string (eqstr) was set successfully to represent the text. Effect. The name string now represents some text. Recovery. This message is informational only; no recovery action is necessary. NNM0236 GLOBAL EQUATE FOR eqstr NULLIFIED FOR LOCAL USE Cause. An EQUATE command was issued to replace the text represented by the global equate name string (eqstr).
Messages NNM0242 NNM0239 GLOBAL EQUATE eqstr HAS OVERRIDDEN MATCHING COMMAND Cause. An EQUATE command was issued in the NCL procedure INIT and the specified name string (eqstr) is the same as a command. When a user issues the command, the text is executed instead of the original command. Effect. The text replaces the command for all users. Recovery.
Messages NNM0245 NNM0245 -STRING- TYPE ------------ EQUATED COMMAND TEXT ----------Cause. A SHOW EQUATES command was issued and the message is part of the response. The line contains the headings of the SHOW EQUATES display. Other messages provide the actual information. STRING is the heading for the name of an equate. TYPE is the heading for the type of equate. The types are as follows: GLBL indicates a global equate where the name is not a NonStop NET/MASTER MS command. LOCL indicates a local equate.
Messages NNM0251 NNM0248 NO EQUATES DEFINED Cause. A SHOW EQUATES command was issued but the name strings that were defined through the EQUATE command were not found. Effect. No name strings are displayed. Recovery. This message is informational only; no recovery action is necessary. NNM0249 COMMAND IS NOT VALID FROM INIT PROCEDURE Cause. A command was issued through the NCL procedure INIT but it is illegal to do so. Effect. The command is rejected. Recovery. Remove the command from the procedure.
Messages NNM0252 NNM0252 ID DATE TIME USERID NCLID MFAV TEXT Cause. A SHOW NRD command was issued and the message is part of the response. The line contains the headings of the display. Other messages provide the actual information. ID is the heading for the delete operator message (DOM) ID of the message. DATE is the heading for the date the message was queued. TIME is the heading for the time the message was queued. USERID is the heading for the ID of the user that queued the message.
Messages NNM0255 NNM0253 dom-id date/time userid nclid mfav text Cause. A SHOW NRD command was issued and the message is part of the response. The line contains information about a queued NRD message. dom-id is the delete operator message (DOM) ID of the message. date is the date the message was generated. time is the time the message was generated. userid is the ID of the user that queued the message or dash (-) if not applicable.
Messages NNM0256 NNM0256 MAP-NAME MAP-KEY USE-CNT STATUS Cause. A SHOW MAPS command was issued and the message is part of the response. The line contains the headings of the display. Other messages provide the actual information. MAP-NAME is the heading for the name of a map. MAP-KEY is the heading for the key (in hexadecimal) of the map. USE-CNT is the heading for the number of active references to the map. STATUS is the heading for the status of the map.
Messages NNM0259 NNM0257 map-name key use-count status Cause. A SHOW MAPS command was issued and the message is part of the response. This line contains information about a map. map-name is the name of the map. key is the key (in hexadecimal) of the map. use-count is the number of active references to the map. status is the status of the map. The status is one of the following: ERROR indicates that an error occurred during the loading of the map into memory.
Messages NNM0260 NNM0260 MAP DELETE REQUEST ACCEPTED Cause. A SYSPARMS MAPDEL=map-name command was issued and accepted. Effect. The map is deleted from all processes when no longer in use. Recovery. This message is informational only; no recovery action is necessary. NNM0261 MAP DELETE REQUEST ACCEPTED. use-count ACTIVE Cause. A SYSPARMS MAPDEL=map-name command was issued but a map that was in use locally was specified. The map will be deleted when no users are using the map.
Messages NNM0268 NNM0264 NRD MESSAGES WITH NCLID nclid PURGED Cause. A PURGE NRD=nclid command was issued and the NRD messages that came from the specified NCL process were purged. nclid is the ID of the NCL process. Effect. The NRD messages are purged. Recovery. This message is informational only; no recovery action is necessary. NNM0266 SUPPLIED DESTINATION NAME IS INVALID Cause. A MSG command was issued but an invalid destination was specified.
Messages NNM0269 NNM0269 MESSAGE SENT TO ALL OCS OPERATORS Cause. A MSG ALL command was issued and was successful. Effect. The user message is sent to all OCS operators. Recovery. This message is informational only; no recovery action is necessary. NNM0270 MSG AT hh:mm FROM userid: text Cause. The OCS operator received a message that came from a MSG command. hh:mm is the time the message was sent. userid is the ID of the user that sent the message. text is the text of the message. Effect.
Messages NNM0273 NNM0273 MAPPING SERVICES MAPPING ERROR, errtext. KEY: key Cause. A Mapping Services mapping error occurred. key (in hexadecimal) identifies the map. errtext is one of the following: INVALID MAP DATA There are invalid lengths in the map data. MISSING DEFINITION VECTORS Necessary vectors are missing. DUPLICATE DEFINITION VECTORS There are duplicate vectors. NAME/KEY INVALID OR IN USE The name or the key duplicates that of another map.
Messages NNM0274 NNM0274 MAP map-name NOT FOUND Cause. A SYSPARMS MAPLOAD command was issued but the map to be loaded was not found. map-name is the name of the map to be loaded. Effect. The map is not loaded. Recovery. Use the SHOW MAPS command to list the maps known to the NonStop NET/MASTER MS system. Use a listed map and retry the SYSPARMS MAPLOAD command. NNM0275 LOAD FOR MAP map-name FAILED Cause. A SYSPARMS MAPLOAD command was issued but the map failed to load.
Messages NNM0279 NNM0278 WARNING - NRD RETENTION QUEUE AT OR BEYOND 75% FULL Cause. The NRD message queue is at least 75% full. Effect. The warning is displayed. Recovery. You can use one of the following commands to correct the problem: PURGE NRD= command to remove some of the messages from the queue SYSPARMS NRDLIM command to increase the queue limit NNM0279 EMS TOKENS FOR USER SUBSYSTEM ssowner.ssnumber WILL BE IGNORED Cause.
Messages NNM0300 NNM0300 command-type REQUEST COMPLETE filename Cause. A UDBCTL command was issued and was successful. If the command operated on two related files and the operation was successful on only one file, filename identifies that file. command-type is one of the following types of operation: ASSIGN assigns a UDB ID to a file or a pair of related files. CLOSE closes a file or a pair of files that were opened as a UDB. OPEN opens a file or a pair of related files as a UDB.
Messages NNM0304 NNM0302 UDB IS NOT CLOSED filename Cause. A UDBCTL OPEN or UDBCTL RESET command was issued, but the file or files specified in the command is associated with a UDB. filename is the name of the file that caused the error. Effect. The operation is not performed on the file. Recovery. The UDBCTL OPEN and UDBCTL RESET commands cannot operate on files associated with a UDB; that is, you must close the UDB first.
Messages NNM0305 NNM0305 FILEID fileid ALREADY ASSIGNED TO UDB filename Cause. A UDBCTL command was issued to assign an ID to a UDB file. However, the UDB file had an ID already. fileid is the ID of the UDB file specified. filename is the name of the UDB file specified. Effect. The assignment is rejected and the original UDB ID remains operative. Recovery. To assign a new ID to the UDB file, use the UDBCTL STOP command to delete the existing ID, then assign the new ID.
Messages NNM0309 NNM0308 FILEID fileid PREVIOUSLY ASSIGNED TO UDB filename Cause. A UDBCTL command was issued and an attempt to assign an ID to a UDB file was made. However, another UDB file has that ID already. UDB IDs must be unique. fileid is the UDB ID being assigned. filename is the name of the UDB file that has the specified ID. Effect. No ID is assigned to the specified UDB file. Recovery. Use the SHOW UDB command to list the IDs of the UDB files.
Messages NNM0310 NNM0310 FILENAME P-EXT S-EXT CUR MAX RCSZ CODE T Cause. A SHOW FILES command was issued and the message is part of the response. The line contains the headings of the SHOW FILES display. Other messages provide the actual information. FILENAME is the heading for the name of a UDB file. P-EXT is the heading for the primary extent size. S-EXT is the heading for the secondary extent size. CUR is the heading for the number of extents currently allocated.
Messages NNM0312 NNM0311 filename p-ext s-ext cur max-ext rcsz code type Cause. A SHOW FILES command was issued and the message is part of the response. The line contains information about the file attributes of a UDB file. filename is the name of the UDB file. p-ext is the primary extent size. s-ext is the secondary extent size. cur is the number of extents currently allocated. max-ext is the maximum number of extents allowed. rcsz is the maximum record size. code is the file code.
Messages NNM0313 NNM0313 FILENAME FILEID A/U RKP KYL STUS OPTNS Cause. A SHOW UDB command was issued and the message is part of the response. The line contains the headings of the SHOW UDB display. Other messages provide the actual information. FILENAME is the heading for the name of a UDB file. FILEID is the heading for the UDB ID of the file. A/U is the heading for the number of NCL processes accessing the file.
Messages NNM0314 NNM0314 filename fileid a/u rkp kyl stus optns Cause. A SHOW UDB command was issued and the message is part of the response. The line contains information about a UDB file. filename is the name of the UDB file. fileid is the UDB ID of the file. a/u is the number of NCL processes accessing the file. rkp is the relative position (offset) of the primary key from the beginning of a record in bytes. kyl is the length of the primary key in bytes. stus is the status of the file.
Messages NNM0315 NNM0315 filename >>> OPEN ERROR=errno stus Cause. A SHOW UDB command was issued and the message is part of the response. The line contains information about a UDB open error. filename is the name of the UDB file that has an error. errno is the Guardian file-system error number. stus is ERR. Effect. The information about the file in error is displayed. Recovery. Use the error number to determine the appropriate action to take.
Messages NNM0319 NNM0318 fileid userid procname nclid logitermname baseproc openid Cause. A SHOW UDBUSER command was issued and the message is part of the response. The line contains information about a UDB user. fileid is the UDB ID. userid is the ID of the user using the UDB file. procname is the NCL procedure that opened the UDB file. nclid is the ID of the NCL process using the UDB file. logitermname is the logical name of the terminal on which the NCL process is executing.
Messages NNM0319 FILE NOT AVAILABLE TO NCL The specified file Is not opened. Use UDBCTL OPEN to open the file. Has failed on an UDBCTL OPEN command. Use the SHOW UDB command to display the error condition on the file and take appropriate action. Is a system file, and the value of the SYSUDB system parameter is NO. If necessary, issue the SYSPARMS SYSUDB=YES command. FILE SYSTEM ERROR errno The error is indicated by a Guardian file-system error number.
Messages NNM0321 NNM0320 PSNDID USERID TIME-OPEN NCL-PROC NCLID TX AVG-RT AVG-MSG Cause. A SHOW PSNDUSER command was issued, and the message is part of the response. The line contains the headings of the SHOW PSNDUSER display. Other messages provide the actual information. PSNDID is the heading for the ID of a Pathway server class. USERID is the heading for the ID of the user using the server class. NCL-PROC is the heading for the name of the NCL procedure using the server class.
Messages NNM0322 NNM0322 PATHMON.SERVERCLASS STATUS PSNDID ACTIVE-USERS Cause. A SHOW PSND command was issued, and the message is part of the response. The line contains the headings of the SHOW PSND display. Other messages provide the actual information. PATHMON.SERVERCLASS is the heading for the name of the Pathway server class. PSNDID is the heading for the ID of the server class. ACTIVE-USERS is the heading for the number of users accessing the server class.
Messages NNM0327 NNM0324 command-type REQUEST COMPLETE Cause. A PSNDCTL command was issued and was successful. command-type is one of the following types of operation: CLOSE makes a Pathway server class unavailable. OPEN makes a Pathway server class available. STOP dissociates the ID from a Pathway server class. Effect. The operation is completed. Recovery. This message is informational only; no recovery action is necessary. NNM0326 PATHWAY SERVER CLASS IS NOT CLOSED Cause.
Messages NNM0328 NNM0328 PSNDID pathsend-id PREVIOUSLY ASSIGNED TO SERVER CLASS server-class-name Cause. A PSNDCTL command was issued and attempted to assign an ID to a Pathway server class. However, another server class has that ID already. Server class IDs must be unique. pathsend-id is the ID being assigned. server-class-name is the name of the Pathway server class that has the specified ID. Effect. No ID is assigned to the specified server class. Recovery.
Messages NNM0343 NNM0341 PSNDID pathsend-id IS INVALID Cause. A PSNDCTL OPEN command was issued, but an invalid ID was specified for the server class. A server class ID must satisfy the following criteria: The length must be from one through eight characters. Valid characters are letters, digits, @, #, $, and _. The ID must not begin with a digit. pathsend-id is the ID specified for the server class to be made available to NonStop NET/MASTER MS. Effect. The server class remains unavailable. Recovery.
Messages NNM0343 DATA LENGTH EXCEEDS MAXIMUM The data record produced is longer than the maximum message size specified in the PSNDCTL OPEN command for the server class. Specify less data on the PSEND verb, or use the PSNDCTL CLOSE command to close the server class and then the PSNDCTL OPEN command using a larger message size to reopen the server class. PSENDID NOT OPEN The specified server class ID has not been processed by the PSEND OPEN verb. Issue PSEND OPEN for this server class ID.
Messages NNM0347 NNM0344 PAIR OF UDBS ARE NOT RELATED Cause. A UDBCTL OPEN, ASSIGN, or CLOSE command was issued on a pair of files. One of the files in the pair was previously opened as part of another UDB pair. Effect. The operation is not performed. Recovery. Use the SHOW UDB command to check for the correct pair of files, and retry the command. NNM0345 ONE OR BOTH UDBS ARE NOT EXISTING DISK FILES Cause. A UDBCTL OPEN command was issued on a pair of files.
Messages NNM0348 NNM0348 RESET NOT ALLOWED ON SECOND FILE OF UDB PAIR Cause. A UDBCTL RESET command was issued on the second of a pair of UDB files. You cannot purge the contents of the second file with this command. Effect. The command is rejected. Recovery. If it is absolutely necessary to carry out this task, check with the systems administrator. NNM0350 NO SUCH COMMAND FOUND Cause. A !, ?, or FC command was issued but the specified command could not be found in the command history buffer. Effect.
Messages NNM0354 NNM0352 (indent) MULTILINE MESSAGES WILL BE INDENTED BY num COLUMNS. Cause. A PROFILE command was issued, and the message is part of the response. The line contains information about the INDENT operand. INDENT specifies the number of columns by which lines following the first line in a multiline message should be indented. indent is the value of the operand: 0 through m, where m is the width of the terminal screen minus ten.
Messages NNM0355 NNM0355 'ENTER' CMD REQUIRES A PFK IMM DEFINITION TO ACT AS A NEW ENTER Cause. An ENTER command was issued but none of the PF keys were previously redefined to act as a new ENTER key. Redefinition of the ENTER key is not allowed without defining a new ENTER key as a replacement. Effect. The command is ignored. Recovery. Define one of the PF keys as a new ENTER key (for example, FK PFnn IMM) and retry the command. NNM0356 'ENTER' COMMAND OPERAND REQUIRES A TEXT STRING Cause.
Messages NNM0360 NNM0359 (cmdkeep) text COMMAND WILL BE KEPT ON ENTRY LINE. Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the CMDKEEP operand. CMDKEEP specifies whether the NonStop NET/MASTER MS system keeps or erases the command after you enter it from the OCS command input line. cmdkeep is the value of the operand. text is part of the operand setting description. The message text is one of the following: (CMDKEEP=NO..
Messages NNM0361 NNM0361 (cmdstack) COMMAND STACK SIZE IS num. Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the CMDSTACK operand. CMDSTACK specifies the number of commands the NonStop NET/MASTER MS system retains in the history buffer. cmdstack is the value of the operand: 0 through 99. num is the number of commands retained in the history buffer. For example, (CMDSTACK=20.) COMMAND STACK SIZE IS 20. Effect.
Messages NNM0364 NNM0363 text Cause. An OCSID or TITLE command was issued and this message confirms that the OCS ID or title has changed. The message text is one of the following: OCS WINDOW ID SET OCS WINDOW ID RESET NEW TITLE SET Effect. The change in the OCS ID or title is confirmed. Recovery. This message is informational only; no recovery action is necessary. NNM0364 (hold) HELD MESSAGES THRESHOLD IS num. Cause. A PROFILE command was issued and the message is part of the response.
Messages NNM0365 NNM0365 (initcmd) text1 INITIAL CMD text2 string. Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the INITCMD operand. INITCMD specifies the command that automatically executes when you enter OCS. initcmd is the value of the operand. text1 text2 are parts of the operand description. string is the initial command string. The message text is one of the following: (INITCMD=....) INITIAL CMD HAS NOT BEEN SET. (INITCMD=...
Messages NNM0368 NNM0367 (msg) MSG COMMAND OUTPUT WILL text. Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the MSG operand. MSG specifies whether you can receive messages that other users send with the MSG command. msg is the value of the operand. text is part of the operand description. The message text is one of the following: (MSG=NO......) MSG COMMAND OUTPUT WILL NOT BE RECEIVED. (MSG=YES.....) MSG COMMAND OUTPUT WILL BE RECEIVED.
Messages NNM0369 NNM0369 (msgcode) CURRENT MESSAGE CODE SETTING IS num. Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the MSGCODE operand. MSGCODE contains the hexadecimal message code that is used to filter the receipt of messages from NCL procedures. msgcode is the value of the operand. num is the hexadecimal message code. For example, (MSGCODE=00..) CURRENT MESSAGE CODE SETTING IS 00. Effect.
Messages NNM0372 NNM0371 (ncltest) NCL PROCEDURES text. Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the NCLTEST operand. NCLTEST specifies the NCL test mode for the OCS window. ncltest is the value of the operand. text is part of the operand description. The message text is one of the following: (NCLTEST=NO..) NCL PROCEDURES MAY BE SHARED WITH OTHER USERS. (NCLTEST=YES.) NCL PROCEDURES WILL HAVE TO BE FRESH, PRIVATE COPIES. Effect.
Messages NNM0373 NNM0373 (prefsys) MESSAGES WILL text1 did text2 ORIGIN SYSTEM ID PREFIX. Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the PREFSYS operand. PREFSYS specifies whether each unsolicited message received is prefixed with the domain ID of the system from which the message originated. prefsys is the value of the operand. text1 is part of the operand description.
Messages NNM0376 NNM0375 (roll) SCREEN ROLL DELAY TIME IS num. Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the ROLL operand. ROLL specifies the length of time to hold a filled roll-delete message display prior to wrapping to the top to display the next message. roll is the value of the operand. num is the time in seconds. For example, (ROLL=1......) SCREEN ROLL DELAY TIME IS 1. Effect.
Messages NNM0377 NNM0377 (prftm) text1 text2 Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the PRFTM operand. PRFTM specifies whether each unsolicited message is prefixed with the time the message was generated. prftm is the value of the operand. text1 text2 are parts of the operand description. The message text is one of the following: (PRFTM=NO....) UNSOLICITED MESSAGES WILL NOT HAVE TIME PREFIX. (PRFTM=HM....
Messages NNM0381 NNM0379 MSGCODE VALUE EXCEEDS AUTHORIZED RANGE Cause. A PROFILE MSGCODE=nn command was issued where nn is a new message delivery code. You cannot use this command to select a delivery code that requires an authority level that is higher than the value set in your user ID definition record. Effect. The command fails. The message code remains unchanged. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM0382 NNM0382 NCL PROCEDURE LIBRARY ID: libname Cause. A PROFILE command was issued and the message is part of the response. The line identifies the NCL procedure library of the user. libname is the name of the library. For example, NCL PROCEDURE LIBRARY ID: $DATA2.HENRY Effect. The name of the NCL procedure library of the user is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM0383 USERID HAS status STATUS. Cause.
Messages NNM0385 NNM0384 AUTOHOLD text state auto Cause. An AUTOHOLD or PROFILE command was issued. The message contains information about the AUTOHOLD setting. AUTOHOLD specifies whether to roll or to hold roll-delete messages. text is part of the description and is one of the following: MODE SET TO indicates that an AUTOHOLD command was issued. SETTING IS indicates that a PROFILE command was issued. state is OFF or ON. auto is AUTO or NOAUTO.
Messages NNM0386 NNM0386 USER SERVICES PROCEDURE: userproc Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the user services NCL procedure. The procedure provides access to certain installation-specific applications. userproc is the name of the procedure. Effect. The name of the user services procedure is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM0387 (prefems) text Cause.
Messages NNM0392 NNM0389 USERID NOT AUTHORIZED TO RECEIVE EMS MESSAGES Cause. A PROFILE EMS= command was issued but the UMS record does not allow the user to receive EMS messages. Effect. The request is refused. Recovery. If necessary, update the UMS record to allow the user to receive EMS messages. NNM0390 .. RECEIVE text EMS MESSAGES. Cause. A PROFILE command was issued and the message is part of the response. The line contains information about the reception of EMS messages.
Messages NNM0393 NNM0393 MSGPROC PROCESSING ACTIVATED Cause. A PROFILE MSGPROC=procname command was issued and the request to start the NCL procedure (procname) as MSGPROC was successful. Effect. The procedure is started as MSGPROC. Recovery. This message is informational only; no recovery action is necessary. NNM0394 SESSION TERMINATED ON USER REQUEST Cause. The NCL verb QEXIT was issued and the session for the user that started the NCL procedure terminated. Effect. The current session is terminated.
Messages NNM0397 NNM0396 (trunc) text Cause. A PROFILE command was issued, and the message is part of the response. The line contains information about the TRUNC operand. TRUNC specifies whether messages longer than the width of an OCS window, should be truncated or wrapped to the next line. trunc is the value of the operand. text is part of the operand description. The message text is one of the following: (TRUNC=NO....) MESSAGES ARE NOT TRUNCATED. (TRUNC=YES...) MESSAGES ARE TRUNCATED. (TRUNC=WORD.
Messages NNM0398 NNM0398 -USERID- TERMINAL -------NAME------- -----LOCATION----- STATUS Cause. A SHOW OCS command was issued and the message is part of the response. The line contains the headings of the display. USERID is the heading for the ID of an OCS user. TERMINAL is the heading for the logical name of the user’s terminal. NAME is the heading for the name of the user. LOCATION is the heading for the location of the user. STATUS is the heading for the status of the user.
Messages NNM0400 NNM0400 OPEN PROCESS process_name ERROR=errno ON, LINK=linkname DEVICE=devname Cause. A LINK START command was issued for an INMC link that uses PTP sessions. During link establishment, the INMC software was unable to access the named process.
Messages NNM0401 NNM0401 action FILE=filename, ERROR=errno, LINK=linkname, UNIT=unitname Cause. A LINK START command was issued for an INMC link that uses PTP sessions. During link establishment, the INMC software was unable to access the file defined in the unit definition. Common causes of this error are an incorrect Safeguard setting or incorrect or missing REMOTEPASSWORD settings that prevent the INMC software from accessing the specified file. action is CREATE, OPEN, or PURGE.
Messages NNM0451 NNM0450 INMC X25 INCORRECT APPLID NAME. EXPECTED=ename ACTUAL=aname,LINK=linkname, DEVICE=devname, UNIT=unitname Cause. A LINK START command was issued and an X.25 virtual call was set up, but the APPLID value used by the remote system does not match the APPLID value configured in the session definition on this NonStop NET/MASTER MS system. This message is generated for each unit used by the session. ename is the APPLID value in the local session definition.
Messages NNM0501 NNM0501 LINKNAME DMN STATUS SSCP NETID L-C R-C A-C Cause. A SHOW ISR command was issued and the message is part of the response. The line contains the headings for information about the INMC links. Other messages provide the actual information. LINKNAME is the heading for the name of an INMC link. DMN is the heading for the domain ID of the connected remote system. STATUS is the heading for the status of the ISR connection: ACTIVE or INACTIVE.
Messages NNM0505 NNM0503 E/D SOL IN OUT E/D SOL IN OUT E/D SOL IN OUT Cause. A SHOW ISR command was issued. The message is part of the response and contains the second line of headings for information about the flow classes on the systems. Other messages provide the actual information. E/D is the heading for the availability of a flow class: DIS (disabled), ENA (enabled), or N/S (not supported). SOL is the heading for the solicited event message flow flag for the flow class: NO or YES.
Messages NNM0506 NNM0506 ISR COMMAND UNRECOGNIZED Cause. The command entered is not recognized by the ISR command services. The valid commands are ISR ALTER, ISR DISABLE, ISR ENABLE, or ISR RESET. Effect. The command is ignored. Recovery. Correct the command and retry. NNM0507 ISR paramname COMPLETED SUCCESSFULLY Cause. An ISR command was issued and was successful. paramname is the operand string to the command. Effect. The command is successfully processed. Recovery.
Messages NNM0551 NNM0511 PARAMETER IN ERROR: paramname Cause. An ISR command was issued but an invalid operand value was specified. paramname is the operand string that contains the invalid value. Effect. The command is ignored. Recovery. Specify a valid value to correct the command and retry. NNM0512 LINK linkname UNUSABLE AS ISR CONNECTION. DOMAIN domainid ALREADY CONNECTED Cause. A LINK START=linkname command was issued.
Messages NNM0552 NNM0552 NEWPROCESS ERROR process_name err1:err2 ON objfile Cause. A NEWPROCESS error occurred while the control process was attempting to start a process. process_name is the name of the process being started. err1 is the NEWPROCESS error number. err2 is the NEWPROCESS error subcode or a file-system error number. objfile is the name of the program to be executed. Effect. If the error code indicates that the process started, then no action is taken and the process can be used.
Messages NNM0554 NNM0554 PROCESS FAILED process_name logicalname objfile Cause. The process for the program failed. process_name is the name of the process. logicalname is the logical name of the process. objfile is the name of the program. Effect. If the failed process is a static process, it is restarted for a maximum of three times. If the failed process is a dynamic process, the application is informed of the failure and can take its own recovery actions. Recovery.
Messages NNM0555 NNM0555 PROCESS OCCURRENCE - logicalname process_name process_type process_class Cause. A SHOW PROCESS command was issued, and the message is part of the response. The line contains information about an occurrence of the process. logicalname is the logical name of the process. process_name is the name of the process. process_type is the type of process. The type is one of the following: process_class DSNM indicates a DSNM process. DYNAMIC indicates a dynamic process.
Messages NNM0556 NNM0556 OBJECT=objfile CPUS=cpu1:cpu2 WEIGHT=weight class Cause. A SHOW PROCESS command was issued, and the message is part of the response. The line contains information about the definition for the process. objfile is the name of the program (object file of the process). cpu1 cpu2 are the CPUs on which the process can run. The values are in the range 00 through 15. weight is the CPU loading for a dynamic process.
Messages NNM0557 NNM0557 LIBRARY=libfile PRIORITY=priority DEBUGTERM=devname SWAPVOL=swapvol Cause. A SHOW PROCESS command was issued and the message is part of the response. The line contains information about the definition for the process. libfile is the library file name for the process. The value is NONE if the library file does not exist. priority is the priority of the process. The value is in the range 1 through 199 with the larger value indicating a higher priority.
Messages NNM0563 NNM0560 SHUTDOWN IN PROGRESS Cause. A SHUTDOWN command was issued and was accepted; or a SHUTDOWN command was issued but the shutdown is already in progress. Effect. The NonStop NET/MASTER MS system stops all future logons and waits for all users to log off before starting the shutdown. Recovery. This message is informational only; no recovery action is necessary. NNM0561 SHUTDOWN NOT IN PROGRESS Cause.
Messages NNM0564 NNM0564 SYSTEM STOPPING Cause. A SHUTDOWN $ABEND$ command was issued and the command was accepted. Effect. An immediate shutdown of the NonStop NET/MASTER MS system has started. Recovery. This message is informational only; no recovery action is necessary. NNM0565 FAILED TO EXECUTE NCL INIT PROCEDURE Cause. The NCL procedure INIT could not be executed. Common causes include the following: INIT procedure is not present.
Messages NNM0570 NNM0567 SYSTEM IS ALREADY STOPPING Cause. A SHUTDOWN or FSTOP command was received while the NonStop NET/MASTER MS system was in the last stage of a shutdown. Effect. The NonStop NET/MASTER MS system continues to complete the shutdown. Recovery. This message is informational only; no recovery action is necessary. NNM0568 PROCESS process_name STOPPED Cause. The control process stopped a process during shutdown. process_name is the name of the stopped process. Effect.
Messages NNM0571 NNM0571 UNABLE TO START ALL SECEXIT PROCESSES Cause. One of the security exit processes could not be started during the initialization of the NonStop NET/MASTER MS system but the system requires all of them to be started. Common causes are: Security exit object file is not present Security exit object file is secured such that it cannot be accessed by the NonStop NET/MASTER MS system Not enough system resources to run the process (such as disk swap space) Effect.
Messages NNM0575 NNM0574 INVALID BACKUP CPU Cause. During the startup of your NonStop NET/MASTER MS system, a process was started with an invalid backup CPU. The backup CPU number cannot be higher than the highest CPU number configured on your Tandem system. Effect. The startup of the NonStop NET/MASTER MS system is stopped. Recovery. If the process is NCP, assign a valid CPU number for the backup NCP process in the RUN command.
Messages NNM0576 NNM0576 UNABLE TO READ STARTUP MESSAGE Cause. An I/O error occurred when a NonStop NET/MASTER MS process was reading its startup message. Effect. The process abends and processing cannot be continued by NonStop NET/MASTER MS. Recovery. Examine the EMS log to determine the reason for the failure. After you have corrected the problem, restart the NonStop NET/MASTER MS system. If this problem persists, contact your Tandem support representative. NNM0577 INCORRECT OS VERSION Cause.
Messages NNM0579 NNM0579 USER group-number,user-number AT HOMETERM home-term STARTED NCP objfile IN CPU cpu1:cpu2 config-file-info trace-info (backup-status) Cause. Your NonStop NET/MASTER MS system was being started, and the message was displayed to provide the following startup information: group-number,user-number is the Guardian user ID of the user that started NonStop NET/MASTER MS. home-term is the name of the home terminal for NonStop NET/MASTER MS. objfile is the name of the NCP object file.
Messages NNM0580 NNM0580 WARNING: FILE SECURITY OF filename IS 'file-security' Cause. During the startup of NonStop NET/MASTER MS, the licensed program object file (which executes privileged instructions) was not secured properly. The message was displayed to warn of the possible security exposure. The recommended file security of NonStop NET/MASTER MS licensed program object files is either --O- or--U-. filename is the name of the licensed program object file.
Messages NNM0584 NNM0582 WARNING: process-name FAILED TO RESTART PROCESS logical-name' restart-count TIMES IN time-interval SECONDS, NO FURTHER RESTARTS Cause. The number of restarts of a failed NonStop NET/MASTER MS static or external process (for example, a DSNM process) reached the maximum number allowed for the time interval, or the time limit for restarts expired. process-name is the name of the NonStop NET/MASTER MS control process. logical-name is the logical name of the failed process.
Messages NNM0585 ERROR error-number A Guardian file-system error occurred. Use error-number to determine the appropriate action to take. INVALID PROCESS NAME You specified an invalid process name. Correct the name and reissue the command. INVALID PROCESS TYPE You issued a PROCESS ALTER or PROCESS SWITCH command on a process that is not an NCP, GMM, or security exit process. NO BACKUP PROCESS You issued the PROCESS SWITCH command on a process that has no backup.
Messages NNM0587 NNM0586 BACKUP CPU OF process-name CHANGED FROM old-cpu TO new-cpu (backup-status) WITH command-effect EFFECT Cause. A PROCESS ALTER=process-name BACKUPCPU=new-cpu command changed the CPU in which the backup process of the NonStop NET/MASTER MS process pair executes or is to execute (backup CPU). process-name is the name of the process. old-cpu is the number that identifies the former backup CPU. new-cpu is the number that identifies the newly assigned backup CPU.
Messages NNM0601 NNM0601 SYSPARMS VALUE Cause. A SHOW SYSPARMS command was issued and the message is part of the response. The line contains the headings of the SHOW SYSPARMS display. Other messages provide the actual information. Effect. The headings are displayed. Recovery. This message is informational only; no recovery action is necessary. NNM0602 sysparmvalue Cause. A SHOW SYSPARMS command was issued and the message is part of the response. The line contains information about a system parameter.
Messages NNM0607 NNM0605 paramvalue Cause. A SHOW PARAM command was issued and the message is part of the response. The line contains information about a startup parameter for the NonStop NET/MASTER MS system. is the displayed information. paramvalue Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM0606 SYSPARMS keyword OPERAND NOT VALID AFTER INITIALIZATION COMPLETED Cause.
Messages NNM0608 NNM0608 statusinfo Cause. The message displays the status information about the NonStop NET/MASTER MS system in response to a STATUS command. statusinfo contains the following status information: SYSTEM STATUS AS AT current-time gives the time at which the status information is obtained. NONSTOP KERNEL VERSION: version-number gives the version number of the operating system. SYSTEM STATE: system-status gives the status of the NonStop NET/MASTER MS system.
Messages NNM0608 CONTROL PROCESS OBJECT FILE: object-name gives the name of the NCP object file. CONTROL PROCESS HOMETERM: device-name gives the device name of the terminal from which the NCP was started. log-status gives the status of the activity log: CURRENT ACTIVITY LOG FILE = file-name indicates that the activity log is available and gives the name of the current activity log file. LOG SUBSYSTEM INACTIVE - NO AVAILABLE LOG FILES indicates that the activity log is not available.
Messages NNM0609 DSNM dsnm-status: CMDSVR: cmdsvr-status, CIP: cip-status, OTHERS number-executing/number-configured gives the status of the DSNM processes. dsnm-status is one of the following: AVAILABLE indicates that all DSNM processes are available, and NonStop NET/MASTER MS can communicate with DSNM. NOT AVAILABLE indicates that the CMDSVR and CIP processes are not available, and NonStop NET/MASTER MS cannot communicate with DSNM.
Messages NNM0612 NNM0610 filename code size dd-mmm-yyyy hh:mm:ss group,user rwep Cause. A SHOW FILEINFO command was issued and the message is part of the response. The line contains information about a file. filename is the name of the file. code is the file code. size is the length of the file in bytes. dd-mmm-yyyy is the date the file was last modified. hh:mm:ss is the time the file was last modified. group,user is the Guardian user ID of the file owner.
Messages NNM0613 NNM0613 UNABLE TO OBTAIN INFORMATION OF filename (ERROR errno) Cause. The SHOW FILEINFO command failed to obtain detailed information for filename. The error returned by FILEINFO further explains the actual cause of the failure. Possible causes could be the remote system was inaccessible because the Expand link was down, or the file no longer existed when its information was retrieved. errno is the returned Guardian file-system error number. Effect. The command is terminated. Recovery.
Messages NNM0655 NNM0653 REMOTE USER userid LOGGED ON FROM linkname -- nnnnn Cause. A remote user logged on to this NonStop NET/MASTER MS system successfully. userid is the ID of the remote user that logged on to this NonStop NET/MASTER MS system. linkname is the name of the INMC link that the user is using. nnnnn is the name of the user. Effect. The remote user now has access to this NonStop NET/MASTER MS system. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM0656 NNM0656 USERID TERMINAL TYPE PHYSICAL NAME PROCESS Cause. A SHOW USERS command was issued, and the message is part of the response. The line contains the headings for the SHOW USERS display. Other messages provide the actual information. USERID is the heading for the ID of a user. A dash (-) indicates more than one user. TERMINAL is the heading for the logical name of the user terminal.
Messages NNM0658 NNM0658 userid logitermname type devname process-name Cause. A SHOW USERS command was issued, and the message is part of the response. The line contains information about a user. (NNM0659, which is in high intensity, contains information about the user that issued the SHOW USERS command.) userid is the ID of the user, or a dash (-) if there is more than one user. logitermname is the logical name of the user terminal.
Messages NNM0659 NNM0659 userid logitermname type devname process-name Cause. A SHOW USERS command was issued, and the message is part of the response. The line contains information about the user that issued the SHOW USERS command. userid is the ID of the user that issued the SHOW USERS command. If the value is a dash (-), the ID is in a previous NNM0658 message. logitermname is the logical name of the user terminal.
Messages NNM0663 NNM0661 NO matching USERS LOGGED ON Cause. A SHOW USERS command could not find any logged-on users that satisfyied the criteria specified (all users or specific users). matching is the word MATCHING if you issued the SHOW USERS=userid command; otherwise, matching is null. Effect. The command is ignored. Recovery. This message is informational only; no recovery action is necessary. NNM0662 CURRENT MAXUSERS LIMIT IS max, NUMBER OF USERS IS number_of_users Cause.
Messages NNM0664 NNM0664 LOCAL USER userid LOGGED OFF FROM logitermname BECAUSE OF MEMORY SHORTAGE Cause. The local user was logged off because there was a memory shortage in the process containing the user's execution environment. userid is the ID of the local user that was logged off. logitermname is the logical name of the terminal that the user was using. Effect. The local user is logged off. Recovery. Refer the message to your system manager.
Messages NNM0666 NNM0665 REMOTE USER userid LOGGED OFF FROM linkname BECAUSE OF MEMORY SHORTAGE Cause. The remote user was logged off because there was a memory shortage in the process containing the session's remote end. userid is the ID of the remote user that was logged off. linkname is the name of the INMC link that the user was using. Effect. The remote user is logged off. Recovery. Refer the message to your system manager. The manager should try to recover disk space from the swap volume.
Messages NNM0667 NNM0667 REMOTE USER userid LOGGED OFF FROM linkname BECAUSE OF LINK_FAILURE Cause. The remote user was logged off because the INMC link failed. userid is the ID of the remote user that was logged off. linkname is the name of the INMC link that failed. Effect. The remote user is logged off. Recovery. Refer the message to the person who looks after the INMC links. NNM0668 LOCAL USER userid LOGGED OFF FROM logitermname BECAUSE OF 'CANCEL' COMMAND Cause.
Messages NNM0671 NNM0670 LOCAL USER userid LOGGED OFF FROM logitermname BECAUSE OF PROCESS FAILURE Cause. A local user was logged off because the process containing that user's execution environment failed. userid is the ID of the local user that was logged off. logitermname is the logical name of the terminal that the user was using. Effect. A dump file is created. Recovery. Refer the message to your system manager.
Messages NNM0672 NNM0672 YOUR SESSION -userid- ENDED ON TERMINAL logitermname Cause. You logged off from the system successfully. userid is your user ID. logitermname is the logical name of the terminal that you were using. Effect. You are logged off. Recovery. This message is informational only; no recovery action is necessary. NNM0673 YOUR SESSION -userid- HAS BEEN CANCELED ON TERMINAL logitermname Cause. You or another user issued a CANCEL command that terminated your session.
Messages NNM0676 NNM0674 YOUR SESSION -userid- ON logitermname CANCELED BECAUSE OF MEMORY SHORTAGE Cause. You were logged off because of memory shortage. userid is your user ID. logitermname is the logical name of the terminal that you were using. Effect. You are logged off. Recovery. Try to log on again and refer the message to your system manager. The manager should try to recover disk space from the swap volume.
Messages NNM0677 NNM0677 SHUTDOWN CANCELED Cause. The SHUTDOWN CANCEL command canceled the shutdown process successfully. Effect. The shutdown that was in progress is canceled. Normal operation continues. Recovery. This message is informational only; no recovery action is necessary. NNM0678 NO SUCH ACTIVE USERID 'userid' Cause. The CANCEL U=userid command found no users with matching IDs. Effect. The command is ignored and no users are logged off. Recovery.
Messages NNM0683 NNM0681 YOUR SESSION -userid- TIMED OUT AND DISCONNECTED FROM TERMINAL logitermname Cause. Your session was canceled on timeout and the terminal closed (disconnected from the system) as specified by the TOACT1=DISC or the TOACT2=DISC system parameter. userid is your user ID. logitermname is the logical name of the terminal that you were using. Effect. You are logged off. Recovery. If required, log on again.
Messages NNM0684 NNM0684 YOUR SESSION -userid- ENDED BECAUSE OF 'CLOSTERM' ON logitermname Cause. A CLOSTERM command terminated your session. userid is your user ID. logitermname is the logical name of the terminal that was closed. Effect. You are logged off from the terminal. Recovery. Find out who else has modified the status of the terminal. NNM0685 LOCAL USER userid LOGGED OFF FROM logitermname BECAUSE 'CLOSTERM' Cause. A CLOSTERM command terminated the session.
Messages NNM0688 NNM0687 USER user-id LOGON REJECTED AFTER TRYING n TIMES ON device-name : USER WAS SUSPENDED Cause. NonStop NET/MASTER MS does not allow logons from suspended user IDs. The Suspend Date field in the definition of a suspended user ID has a date that has passed. A suspended user has tried to log on to the NonStop NET/MASTER MS system n times. user-id is the ID of the user trying to log on. n is the number of times the logon was tried.
Messages NNM0689 NNM0689 OPSC USER user-id LOGGED OFF FROM logon-device Cause. The OPSC user logged off from the NonStop NET/MASTER MS system. user-id is the ID of the OPSC user that logged off from the NonStop NET/MASTER MS system. logon-device is the origin of the attach request, and is: RSC TERMINAL terminal-name, where terminal-name is the name of an RSC terminal Effect. The OPSC user is no longer on the NonStop NET/MASTER MS system. Recovery.
Messages NNM0750 NNM0691 OPSC USER user-id LOGGED OFF FROM logon-device BECAUSE OF 'CANCEL' COMMAND Cause. A CANCEL command logged off the OPSC user. user-id is the ID of the OPSC user that was logged off. logon-device is the origin of the attach request, and is: RSC TERMINAL terminal-name, where terminal-name is the name of an RSC terminal Effect. The OPSC user is logged off. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM0750 NNM0750 NO SECURITY EXIT(S) ARE AVAILABLE Cause. The NonStop NET/MASTER MS system was being started but could not use any of the configured security exits; or UMS attempted to access an exit that was previously running and found that all exits had become unavailable. Effect. If the error occurs during system initialization, the NonStop NET/MASTER MS system terminates. If the error occurs while the system is running, all future security requests are denied.
Messages NNM0753 NNM0752 UNABLE TO READ/WRITE/OPEN SECURITY EXIT process_name, FS ERROR errno Cause. The application was not able to read from, write to, or open a security exit. process_name is the name of the security exit process. errno is the Guardian file-system error number. Effect. If the error occurs during system initialization, the NonStop NET/MASTER MS system continues as long as there are other exits available.
Messages NNM0754 NNM0754 SECURITY EXIT process_name RETURNED WRONG VALUE exit_code Cause. The installation provided a nonstandard security exit. When the NonStop NET/MASTER MS system attempted to use the exit, the exit set an invalid return code. This is a user programming error. process_name is the name of the security exit process. exit_code is the invalid return code from the security exit. Effect.
Messages NNM0759 NNM0757 INSUFFICIENT AUTHORITY TO USE SECCALL operand Cause. A user, unauthorized to use the full features of UMS, started an NCL procedure that used the SECCALL verb to modify the UMS database other than to update this user’s own password. operand is the keyword of the SECCALL verb. Effect. The UMS database is not modified. Recovery. If appropriate, the system manager can give you UMS management authority which allows you to use the verb. NNM0758 INVALID USER ID userid Cause.
Messages NNM0760 NNM0760 USERID INFORMATION UNAVAILABLE FOR userid Cause. A SECCALL verb was issued but there was no information for the specified user ID. If the UMS database is being used, then the user may not be defined in the database; if a full security exit is being used, then the user may not be defined by the exit. userid is the name of the user ID. Effect. No user information is returned to the SECCALL verb. Recovery. Check the spelling of the specified user ID.
Messages NNM0765 The password is not the same as, or a subset of, the concatenated user name. For example, if the user name is Russell Lucas, then passwords such as russell, rus, lucas, and lluca are invalid. The user name components do not form part of the password. For example, if the the user name is Russell Lucas, the components are Russell and Lucas, and passwords such as russello, trussell, and rlucas are invalid. Not the initials of the user's name.
Messages NNM0766 NNM0766 PASSWORD FOR userid NOT CHANGED - errtext Cause. An attempt to change the password of the user failed. userid is the ID of the user whose password was not changed. errtext is one of the following: FILE SYSTEM ERROR errno The error is a Guardian file-system error. errno is the error number. INCORRECT CURRENT PASSWORD An incorrect current password was specified. INVALID NEW PASSWORD An incorrect new password was specified.
Messages NNM0769 NNM0767 USER DEFINITION userid UPDATED Cause. A user record was updated successfully. userid is the ID of the user whose definition was updated. Effect. The user record is updated. Recovery. This message is informational only; no recovery action is necessary. NNM0768 FAILED TO UPDATE userid - errtext Cause. An attempt to update the information about the user failed. userid is the ID of the user whose information was not changed.
Messages NNM0770 NNM0770 FAILED TO ADD NEW USER userid - errtext Cause. An attempt was made to add a new user but the attempt failed for the reason displayed. userid is the ID of the new user that was not added. errtext is one of the following: FILE SYSTEM ERROR errno The error is a Guardian file-system error. errno is the error number. INVALID NEW PASSWORD The new password was invalid. The password must satisfy the following criteria: Length up to eight characters.
Messages NNM0773 NNM0771 USER DEFINITION userid DELETED Cause. A user record was deleted successfully. userid is the ID of the user whose record was deleted. Effect. The user record is deleted. Recovery. This message is informational only; no recovery action is necessary. NNM0772 FAILED TO DELETE USER userid - errtext Cause. The attempt to delete the user failed. userid is the ID of the user whose record was to be deleted.
Messages NNM0774 NNM0774 READ ONLY MDO FIELD mdofieldname FOR USER userid Cause. A SECCALL ADD or SECCALL UPDATE verb was issued to modify a readonly MDO field. mdofieldname is the name of the read-only MDO field. userid is the ID of the user being added or updated. Effect. The UMS database is not updated. Recovery. Remove the variable representing the field from the verb and restart NCL procedure. NNM0775 INVALID MDO FIELD mdofieldname FOR USER userid Cause.
Messages NNM0780 NNM0777 INSUFFICIENT MEMORY FOR SECCALL EXIT VERB Cause. An attempt was made to send data through the SECCALL EXIT verb but there was insufficient memory to service the request. Effect. The operation is not performed. Recovery. Reduce the amount of data passed through the verb. Refer the message to your system manager. The manager should try to recover disk space from the swap volume. NNM0778 USER groupid IS A GROUP USERID - LOGON REJECTED Cause.
Messages NNM0781 NNM0781 FORCE PASSWORD CHANGE FOR GROUP DEFINITION groupid INVALID Cause. An attempt was made to change the password of the group user ID. Group user IDs do not have passwords. groupid is the group user ID. Effect. The password change is not successful. Recovery. Ensure that you use the correct user ID. You can use the List option on the User ID Management Services Primary Menu to list the user IDs and their type. NNM0782 SELECT AN OPTION OR PRESS A FUNCTION KEY TO PROCEED Cause.
Messages NNM0790 NNM0785 NO ACCESS TO NEXT PAGE Cause. An attempt was made to access a UMS panel by a user with insufficient authority. Effect. The current panel continues to be displayed. Recovery. If necessary, your system manager can upgrade your authority . NNM0786 functionname CANCELED Cause. A CANCEL key was pressed and the function was canceled. functionname contains information about the function. Effect. The function is canceled. Recovery.
Messages NNM0791 NNM0791 AT LEAST ONE GUARDIAN ID MUST BE SUPPLIED Cause. An attempt was made to add/update a UMS record with no Guardian IDs specified. Effect. The UMS Add/Update panel is redisplayed with the first Guardian ID input field highlighted. Recovery. Enter at least one valid Guardian ID for the user record. NNM0792 VALUE NOT VALID FOR GUARDIAN ID - MUST BE FROM lower-limit TO upper-limit Cause. An attempt was made to add/update a UMS record containing an invalid Guardian ID.
Messages NNM0798 NNM0795 FIND STRING MUST BE SPECIFIED Cause. A FIND command was entered but the string to find was not specified. Effect. The search is not made. Recovery. Provide the string and retry the command. NNM0796 REACHED BOTTOM OF DATA Cause. An attempt was made to find (either through the FIND command or F5) or to locate (through the LOCATE command) a user ID. The search reached the end of the user definition list without finding the specified user ID. Effect. The user ID is not found.
Messages NNM0799 NNM0799 ENTER LOCATE PARAMETER Cause. A LOCATE command was entered but the user ID to locate was not specified. Effect. The operation is not performed. Recovery. Provide the user ID and retry the command. NNM0800 DISTRIBUTOR AVAILABLE FOR USE Cause. An EMSDIST START command was issued, and the distributor interface was successfully created and opened by the Event Management Service's distributor named in the EMSDISTPFN system parameter.
Messages NNM0808 NNM0804 DISTRIBUTOR ALREADY STARTED Cause. An EMSDIST START command was issued but the NonStop NET/MASTER MS distributor interface already exists and events are being received. Effect. The distributor interface continues to receive events. Recovery. This message is informational only; no recovery action is necessary. NNM0805 EMSDIST STOP COMMAND ACCEPTED Cause. An EMSDIST STOP command was accepted and will be processed. Effect.
Messages NNM0809 NNM0809 filtname security owner size Cause. A SHOW FILTERS command was issued, and the message is part of the response. The line contains information about a filter. filtname is the name of the filter. security gives the security attributes of the filter. owner is the Guardian user ID of the owner of the filter. size is the length of the filter file in bytes. Effect.
Messages NNM0814 NNM0813 ERROR OPENING DISTRIBUTOR dname ERROR errno Cause. The NonStop NET/MASTER MS distributor interface failed to open the event distributor. dname is the name of the event distributor. errno is the Guardian file-system error number. Effect. The distributor interface is stopped and flagged as unavailable for use. Recovery. Use the error number to determine the appropriate action to take. After you have rectified the problem, use the EMSDIST START command to restart the interface.
Messages NNM0815 NNM0815 EMS DISTRIBUTOR CONFIGURATION ERROR=ems_error, FILE ERROR=errno, LOGFILE logname Cause. An EMSDIST START command was issued, but the EMSDISTCOLL system parameter contains an event log file name; or a SYSPARMS EMSDISTCOLL command was issued with an event log file name while the NonStop NET/MASTER MS distributor interface was active, but the distributor could not access the file. ems_error is the EMS distributor error number. errno is the Guardian file-system error number.
Messages NNM0820 NNM0818 DISTRIBUTOR STARTED AS process_name Cause. An EMSDIST START command was issued, and the event distributor named in the EMSDISTPFN system parameter was started successfully. process_name is the name of the distributor process. Effect. The NonStop NET/MASTER MS distributor interface can now receive EMS events. Recovery. This message is informational only; no recovery action is necessary. NNM0819 DISTRIBUTOR COLLECTOR ALTERED TO collname Cause.
Messages NNM0821 NNM0821 NEWPROCESS ERROR ON process_name ERROR err1/err2 Cause. An EMSDIST START command was issued. The NonStop NET/MASTER MS distributor interface tried to start the process named in the EMSDISTPFN system parameter but encountered an error. process_name is the name of the process specified in EMSDISTPFN. err1 is the NEWPROCESS error number. err2 is the NEWPROCESS error subcode or a file-system error number. Effect.
Messages NNM0827 NNM0824 COLLECTOR ESTABLISHED LINK TO collname Cause. The NonStop NET/MASTER MS collector interface established a link to the collector named in the EMSCOLLPNM system parameter. collname is the name of the collector. Effect. The collector interface can now issue EMS events to collname. Recovery. This message is informational only; no recovery action is necessary. NNM0825 DISTRIBUTOR ALREADY STOPPED Cause.
Messages NNM0831 NNM0831 VARIABLE vblname IS NOT A $MSG MDO Cause. The NCL verbs EMSSEND and EMSALERT require an MDO variable mapped by MSG if the MDO= operand is specified. The error occurred because the specified variable does not exist, is not an MDO variable, or is of the wrong context. vblname is the name of the variable. Effect. No message is sent, and an error is raised in the NCL procedure. Recovery.
Messages NNM0835 NNM0834 EMS DISTRIBUTOR CONFIGURATION ERROR=ems_error, REASON CODE=reason, FILE filename, COLLECTOR=collname Cause. An EMSDIST START command was issued but the distributor was started with a collector specified in the EMSDISTCOLL system parameter. The collector found an invalid log file. ems_error is the EMS distributor error number. reason is the reason code for ems_error. filename is the name of the file in error.
Messages NNM0836 NNM0836 ERROR err1/err2 ACCESSING EVENTTD FILE filename Cause. An error occurred while retrieving help on an EMS event message. err1 is the first part of the EMSTEXT procedure error code. err2 is the second part of the EMSTEXT procedure error code. filename identifies the EMS events help file. Effect. No help is retrieved. Recovery. Use the error code returned by the EMSTEXT procedure to determine the appropriate action to take.
Messages NNM0855 NNM0853 SIGNON TO linkname LOST, RESTART PENDING LINK RECOVERY Cause. The INMC link to the remote system failed, breaking the ROC connection. linkname is the name of the link that failed. Effect. The ROC connection is scheduled for reestablishment when the link becomes active again. Recovery. Refer the message to your system manager. The manager should ensure that the physical link is operating correctly and then issue LINK START to restart the link.
Messages NNM0856 NNM0856 SIGNON RESTART FOR linkname NO LONGER IN EFFECT Cause. A LINK RESET command was issued, and the link reset occurred while the ROC connection was waiting for reestablishment due to a link failure. The connection was lost. linkname is the name of the INMC link that was reset. Effect. The ROC connection is lost. Recovery. To reestablish the connection, wait for the link to be restarted and then sign on to the remote system.
Messages NNM0864 NNM0860 UNABLE TO ROUTE COMMAND, linkname NOT CONNECTED Cause. A ROUTE command was issued but the specified INMC link is inactive. Effect. The specified command string is not routed to the remote system. Recovery. Wait for the link to become active. You can either use the SHOW LINK command to ensure that the link has become active or issue a SIGNON command and wait for its completion, then retry the ROUTE command. NNM0861 ROUTE COMMAND SPECIFIES INVALID LINK NAME linkname Cause.
Messages NNM0865 NNM0865 DESTINATION NAME linkname CONTAINS INVALID CHARACTERS Cause. A SIGNON or SIGNOFF command was issued but the specified INMC link name was invalid. Effect. The signon or signoff is not processed. Recovery. Use the SHOW LINK command to list the link names or use the SHOW USERS command to find out which link you are using for your remote session. Specify the correct link name and retry the command. NNM0866 SIGNON COMPLETE. REGION REFRESHED Cause.
Messages NNM0872 NNM0869 LINK TO linkname NOT ACTIVE, SIGNON COMMAND PENDING Cause. A SIGNON command was issued, and the signon request to the INMC link was queued because the link was inactive. Effect. The command is queued and will be processed when the link to the remote system becomes active. Recovery. If it is necessary to cancel a queued SIGNON, use the SIGNOFF command. NNM0870 SIGNOFF COMPLETE Cause. A SIGNOFF command was issued, and the user signed off successfully from an INMC link. Effect.
Messages NNM0873 NNM0873 DESTINATION LINKNAME linkname IS THE I.D. OF THIS HOST Cause. A SIGNON command was issued but the domain ID of the local NonStop NET/MASTER MS system was specified as the INMC link name. You can only specify the link names of remote systems in this command. linkname is the name specified for the link. Effect. The signon request is refused. Recovery. Use the SHOW LINK command to list the link names. Specify the correct link name and retry the command.
Messages NNM0879 NNM0876 REMOTE USER LOGON ATTEMPT FAILED SECURITY CHECK - SIGNON FAILED Cause. A SIGNON or a ROUTE command was issued to try to sign on to a remote system but the security check failed. Effect. The remote system refuses the signon request. Recovery. Ensure that the remote system knows your user ID. If your password at the remote system is different from your password at the local NonStop NET/MASTER MS system, ensure that you supply the correct password with your SIGNON command.
Messages NNM0880 NNM0880 REMOTE ENVIRONMENT FAILED BECAUSE OF PROCESS FAILURE. Cause. The remote command environment failed because of a process failure. Effect. The remote command is aborted. Recovery. Sign on to the remote system again and retry the command. NNM0881 ROC ATTEMPTING TO ESTABLISH CONVERSATION ON LINK=linkname Cause. A SIGNON or a ROUTE command was issued but a ROC session could not be established. Effect. The ROC subsystem attempts to establish the conversation with the remote system.
Messages NNM0977 NNM0976 NO HELP AVAILABLE Cause. You requested help on an event message, but the help information is available neither in the ZHLPCVP UDB (if configured) nor in the EMS event help file specified in the EMSEVENTTD system parameter. Effect. No help information is displayed. Recovery. Check the source of the EMS event help information, as follows: If you use two files to provide help on EMS event messages, issue the SHOW UDB command to check that the ZHLPCVP UDB is available.
Messages NNM0978 NNM0978 BEGINNING OF DATA Cause. NonStop NET/MASTER is using two sources for the event help message. You pressed the F10 function key to access the ZHLPCVP event help UDB for help on a previous EMS event message, but the ZHLPPCVP UDB contains no earlier data. Effect. The current help information remains displayed. Recovery. Type the ID of the event message on which you want help in the message ID field, and press the ENTER key.
Messages NNM0983 NNM0982 loginfo Cause. An attempt was made to resume a failed procedure but the value of the SYS.ERROR.RESUMEOK system variable was 0: that is, the procedure cannot be resumed. loginfo contains the ID of the NCL process and describes the failure of the procedure. Effect. The procedure is terminated. Recovery. Rewrite the procedure so that RESUME is only executed if the value of &SYS.ERROR.RESUMEOK is 1. NNM0983 loginfo Cause. An NCL procedure has failed.
Messages NNM0984 NNM0984 NCL ERROR loginfo Cause. An NCL procedure has failed. loginfo describes the failure of the procedure. The following is an example: NNM0984 NCL ERROR NMTHY HYNCLTST(1581) LOADFAIL_ERROR FLUSHED NMTHY is the ID of the user that owns the NCL procedure that was executing, HYNCLTST is the name of the NCL procedure that failed, 1581 is the NCL ID of the procedure that was executing, LOADFAIL_ERROR is the error name, and FLUSHED is the action that is performed on the procedure.
Messages NNM0989 NNM0987 VERB verb ONLY ALLOWED IN procedure_type Cause. An NCL verb was issued but the verb can only be used in the named type of NCL procedure. verb is the name of the issued verb: for example, EMSREAD. procedure_type is the type of procedure that can use the verb: for example, EMSPROC. Effect. The verb is not executed. Recovery. Correct the problem by one of the following: Define the procedure that raised the error to the named type (for example, through SYSPARMS commands).
Messages NNM0990 NNM0990 productname - productnumberversion (releasedate),copyrighttext Cause. The message contains the copyright information and appears during the startup of a NonStop NET/MASTER MS system. Effect. The copyright information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM0991 INVALID OPERAND VALUE 'opvalue' Cause. A command was issued using an invalid value for an operand.
Messages NNM0998 NNM0994 objectname NOT FOUND Cause. A command was issued but the object could not be found. objectname identifies the object. Effect. Processing of the command is abandoned. Recovery. Ensure that the object exists and retry the command. NNM0995 REQUEST COMPLETE Cause. A command was issued and was successful. Effect. The command is successful. Recovery. This message is informational only; no recovery action is necessary. NNM0996 INSUFFICIENT MEMORY Cause.
Messages NNM0999 NNM0999 *END* summarytext Cause. The message indicates the end of a list of messages. is any attached summary about the list. summarytext Effect. The listing has ended. Recovery. This message is informational only; no recovery action is necessary. NNM1000 NCLID nclid INSUFFICIENT MEMORY Cause. There was insufficient memory to continue executing an NCL procedure. nclid is the ID of the NCL process that was in progress. Effect. The procedure is terminated. Recovery.
Messages NNM1004 NNM1002 NCL PROCEDURE procname IN LIBRARY libname IS A FUNCTION Cause. A procedure was started, and the NCL file was found, but the top-level routine was defined as a function, not a procedure. procname is the name of the NCL file that caused the problem. libname is the name of the library containing the file. Effect. The function is not executed. Recovery. If the specified name is incorrect, specify the correct name.
Messages NNM1005 NNM1005 type procname PROCESSING COMPLETE. NCLID nclid Cause. The processing of an NCL procedure that was started through an EXEC or START command was completed. type is the command that started the procedure: EXEC or START. procname is the name of the procedure completed. nclid is the ID of the NCL process. Effect. The procedure is terminated normally. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1011 NNM1009 NCL PROCEDURE NAME procname IS INVALID Cause. An attempt to start an NCL procedure was made, but the specified procedure name is longer than 8 characters or contained invalid characters. procname is the specified name. Effect. No procedure is started. Recovery. Specify the correct name and restart the procedure. NNM1010 filename lineno text Cause. An NCL procedure was started, but an error occurred. The line of text describes the error.
Messages NNM1012 NNM1012 label LINE: lineno STMT NO: stmtno FILE: filename type: name NCLID: nclid Cause. An NCL procedure was started, and tracing was enabled through the CONTROL verb. A statement with a label was encountered and the message displayed. label is the name of the label. If the CONTROL statement specified the TRACEALL keyword, label contains the decompiled statement. lineno is the line number of the statement in the file. stmtno is the statement number.
Messages NNM1017 NNM1015 type procname PROCESSING COMPLETE. NCLID nclid INIT: userid PG: 1 PR: 1 P-UNITS: punits Cause. Processing of the NCL procedure that was started by the EXEC or START command was completed. type is EXEC or START. procname is the name of the procedure that was completed. nclid is the ID of the NCL process. userid is the ID of the user that started the procedure. punits is the number of processing units used by the NCL process. Effect. The procedure is completed. Recovery.
Messages NNM1018 NNM1018 text Cause. A LIST command was issued, and the message is part of the response. The message contains a line of text in the file being listed. Effect. A line in the file is displayed. Recovery. This message is informational only; no recovery action is necessary. NNM1019 LIST filename PROCESSING COMPLETE Cause. A LIST command was issued, and the message indicates the end of the LIST display. filename is the name of the file that was processed. Effect. The listing ends.
Messages NNM1025 NNM1022 FLUSH COMMAND ACCEPTED Cause. A FLUSH command was issued and accepted. Effect. The current NCL process is terminated. Recovery. This message is informational only; no recovery action is necessary. NNM1023 command COMMAND INVALID FOR MSGPROC Cause. A command was issued for a MSGPROC procedure but the operation was invalid. command identifies the command that caused the error. Effect. The MSGPROC procedure is not affected. Recovery.
Messages NNM1026 NNM1026 NCLID NOT PROCESSING IN YOUR ENVIRONMENT Cause. An END, FLUSH, GO, or INTQ command was issued but the target NCL process was not under the control of the user. To issue the commands for NCL processes that do not belong to you, you must have an appropriate authority level and the value of the NCLXUSER system parameter must be YES. Effect. The NCL process is not affected. Recovery. Use the SHOW NCL command to check if you have specified the correct ID for the NCL process.
Messages NNM1031 The object file name is the same as the name of the source file subvolume. For example, if the value of the NCLOBJLIB startup parameter is NCLOLIB, then a source file in $DATA2.NNMJN compiles into object file $DATA2.NCLOLIB.NNMJN. If the named library is the global library (named in the NCLOBJLIB startup parameter), the object file name is the name of the source file subvolume and resides on the source file volume.
Messages NNM1032 NNM1032 command OF PROC proc1 REJECTED, PROC proc2 STILL BEING PROCESSED Cause. An EXEC command was issued to execute an NCL procedure. However, another procedure was already executing in the same environment, and the value of the NCLPEND system parameter was not YES. The procedure could not be queued and was not executed. command is EXEC. proc1 is the name of the rejected procedure. proc2 is the name of the executing procedure. Effect. The procedure is not executed. Recovery.
Messages NNM1035 NNM1034 MSGPROC CANNOT BE STARTED IN DEBUGGING ENVIRONMENT Cause. An attempt to start a MSGPROC procedure failed. MSGPROC cannot be started in an environment that is both debugging and being debugged. Effect. The MSGPROC procedure is not started. Recovery. If you intend to debug MSGPROC, start MSGPROC in an environment that did not initiate a debug session for its own environment. For example, start a debug session for your other window and start MSGPROC in that window.
Messages NNM1036 NNM1036 NCLID BASEPROC CURRENT P-UNITS LEV W TYPE INIT OWNER G P Cause. A SHOW NCL or SHOW PAUSE command was issued, and the message is part of the response. The line contains the headings of the display. Other messages provide the actual information. NCLID is the heading for the ID of an NCL process. BASEPROC is the heading for the name of the procedure that initiates the NCL process.
Messages NNM1038 NNM1037 nclid procname name nesting_level window_number proctype userid1 userid2 1 1 punits Cause. A SHOW NCL or SHOW PAUSE command was issued, and the message is part of the response. The line contains information about an NCL process. nclid is the ID of the NCL process. procname is the name of the procedure that initiates the NCL process. name is the name of the current function or procedure that is being executed.
Messages NNM1039 NNM1039 ......RUNNING... Cause. A SHOW NCL or SHOW PAUSE command was issued, and the message is part of the response. The message follows NNM1037 if NNM1041 cannot be displayed for any reason: for example, the NCL procedure is still in the startup phase. Effect. If the NNM1041 message cannot be displayed, this message is displayed. Recovery. Try the command again. Message NNM1041 appears when the procedure has started up. NNM1040 USER REGION userid NOT FOUND Cause.
Messages NNM1045 NNM1042 MESSAGE(S) LOST, INTREAD QUEUE LIMIT EXCEEDED Cause. An NCL procedure issued a command using the INTCMD verb or an INTQ command was issued to pass data to the procedure from OCS, but the number of messages that can be queued to the dependent request or response queue of the procedure exceeded the limit as set by the NMIQLIM system parameter. The default limit is 1000. Effect. One or more messages are discarded and processing continues. Recovery.
Messages NNM1046 NNM1046 NAME LEN TEXT Cause. A SHOW NCLGLBL=global-variable-name command was issued, and the message is part of the response. The line contains the headings for a selective list of the NCL global variables. Other messages provide the actual information. NAME is the heading for the name of a global variable. LEN is the heading for the length (in bytes) of the data in the variable. TEXT is the heading for the value of the variable. Effect. The headings are displayed. Recovery.
Messages NNM1049 NNM1049 ERROR errno IN DEFAULT NCL LIB FOR USER userid : ncllib Cause. An NCL procedure was started but the default NCL library path as defined in the UMS database was invalid. For example, the path may have used a non-existing volume. errno is the Guardian file-system error number. userid is the ID of the user that started the procedure. ncllib is the NCL library path defined for the user. Effect. The system libraries are searched. Recovery.
Messages NNM1050 NNM1050 NAME STATUS USERS REFCNT STMTS NCLBUF LIBRARY AGEUSE Cause. A SHOW NCLSTAT or SHOW PRELOAD command was issued, and the message is part of the response. The line contains the headings of the display. Other messages provide the actual information. NAME is the heading for the name of an NCL procedure. STATUS is the heading for the status of the NCL procedure. The status is one of the following: AUTOSHR indicates a shared NCL procedure.
Messages NNM1051 NNM1051 procname loadstatus number_of_users reference_counter statements nclbuffer libname ageuse Cause. A SHOW NCLSTAT or SHOW PRELOAD command was issued, and the message is part of the response. The line contains information about a preloaded NCL procedure. procname is the name of an NCL procedure. loadstatus is the status of the NCL procedure: AUTOSHR indicates a shared NCL procedure. CMDREPL indicates a command replacement NCL procedure.
Messages NNM1052 NNM1052 NO NCL PROCEDURES PRELOADED OR AUTO-SHARED Cause. A SHOW NCLSTAT or SHOW PRELOAD command was issued but no preloaded or shared NCL procedures that matched the specified criteria could be found. Effect. No preloaded or shared procedures that match the specified criteria are found. Recovery. This message is informational only; no recovery action is necessary. NNM1053 NCL PROCEDURE procname DOES NOT EXIST IN LIBRARY libname Cause.
Messages NNM1056 NNM1055 GLOBAL TRACE UPD/DEL: global_variable_name UID:userid ID: nclid PROC: procname LINE: statement DATA:value Cause. Tracing of a set of NCL global variables was enabled, and an NCL procedure updated or deleted a specified NCL global variable. UPD/DEL indicates whether the variable was updated (UPD) or deleted (DEL). global_variable_name is the name of the variable. userid is the ID of the user that started the procedure. nclid is the ID of the NCL process.
Messages NNM1057 NNM1057 UNLOAD OF procname ACCEPTED [, number_of_users active] Cause. A SYSPARMS UNLOAD command was issued and accepted. procname is the name of the NCL procedure to be unloaded. If the procedure was in use, extra information appears as follows: number_of_users is the number of users using the procedure. is ACTIVE USERS. active Effect. The procedure is unloaded when the last active user terminates. Recovery.
Messages NNM1062 NNM1060 PROCEDURE procname NCLID nclid PAUSED Cause. A PAUSE verb was issued, and the execution of the NCL procedure was suspended. procname is the name of the procedure suspended. nclid is the ID of the NCL process. Effect. Processing for the procedure is suspended. Recovery. You can enter GO, FLUSH, or END as required to resume or cancel the processing of the procedure. NNM1061 procname NOW preloaded|cmdrepled Cause.
Messages NNM1063 NNM1063 GLOBAL VARIABLE NAME PREFIX IS TOO LONG Cause. A SHOW NCLGLBL= command was issued but a global variable reference that contained too many characters was specified. A variable name cannot be more than 250 characters long. Effect. No variable is displayed. Recovery. Use the SHOW NCLGLBL command to list the variable names. Use a correct variable reference and retry the SHOW NCLGLBL= command. NNM1064 locktext Cause.
Messages NNM1069 NNM1067 type NAME RESOURCE primary dot minor Cause. A SHOW LOCKS command was issued, and the message is part of the response. The line identifies the resource that has a lock on. type is the type of the resource: PRIMARY or MINOR. primary dot minor is the name of the resource (primary.minor). Effect. The name of the resource is displayed. Recovery. This message is informational only; no recovery action is necessary. NNM1068 LOCK-ID REQ LOCK-TEXT minorlock Cause.
Messages NNM1070 NNM1070 NO LOCKS FOUND Cause. A SHOW LOCKS command was issued but no locks that matched the selection criteria were found. Effect. No locks that match the specified criteria are found. Recovery. This message is informational only; no recovery action is necessary. NNM1071 WAITING LOCK REQUESTS Cause. A SHOW LOCKS command was issued, and the message is part of the response. The line identifies the lock requests that were waiting to be serviced. Effect.
Messages NNM1077 NNM1074 NCLID:nclid NOT FOUND IN ANY REGION Cause. A SHOW VARTABLES command was issued but the specified NCL process was not found. nclid is the ID of the NCL process specified. Effect. No vartables are displayed. Recovery. Use the SHOW NCL command to list the NCL processes. Use the correct ID and retry the SHOW VARTABLES command. NNM1075 USERID:userid NOT FOUND Cause. A SHOW VARTABLES command was issued but the specified user was not found in the NonStop NET/MASTER MS system.
Messages NNM1078 NNM1078 NAME SC/ID TERM USER KEYL LIMIT ENTRIES NF AGE UD Cause. A SHOW VARTABLES command was issued, and the message is part of the response. The line contains the headings of the SHOW VARTABLES display. Other messages provide the actual information. NAME is the heading for the name of a vartable. SC/ID is the heading for the scope of the vartable. The scope is one of the following: GLOBAL indicates that the vartable is globally applicable.
Messages NNM1079 Effect. The headings are displayed. Recovery. This message is informational only; no recovery action is necessary. NNM1079 name sc_id logitermname userid keyl limit entries nf age u d Cause. A SHOW VARTABLES command was issued, and the message is part of the response. The line contains information about a vartable. name is the name of the vartable being displayed. sc_id indicates the scope of the vartable: GLOBAL indicates that the vartable is globally applicable.
Messages NNM1080 u is the value of the user correlator flag: N (no) or Y (yes). d is the value of the oldest entry delete flag: N (no) or Y (yes). Effect. The information about the vartable is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM1080 type ALL COMMAND ACCEPTED Cause. A DEBUG HOLD ALL or DEBUG RESUME ALL command was issued and sent to all the NCL processes and environments under the debug session. type is either HOLD or RESUME.
Messages NNM1086 NNM1083 NO DEBUG SESSION CURRENTLY RUNNING Cause. A DEBUG command was issued but no debug sessions were found. Effect. The debug operation is not performed. Recovery. Use the DEBUG START command to start a debug session. NNM1084 NO NCLID HAS BEEN SPECIFIED AND NO DEFAULT HAS BEEN SET Cause. A DEBUG command was issued but an NCL process was not specified, and there was no default NCL process. Effect. The debug operation is not performed. Recovery.
Messages NNM1087 NNM1087 WINDOW window_number IS NOT OPEN Cause. A DEBUG START command was issued but the specified window was not open. window_number is either 1 or 2. Effect. The debug session is not started. Recovery. Specify a correct window or open the window and retry the command. NNM1088 number_of_procs NCL PROCESSES TARGETED IN WINDOW window_number Cause. A DEBUG START command was issued, and a debug session was started on the NCL processes in your environments that use the stated window.
Messages NNM1092 NNM1090 NCL nclid ALREADY TERMINATED Cause. A DEBUG command was issued but the specified NCL process was already terminated. You may have specified the wrong NCL ID. is the specified ID of the NCL process. nclid Effect. The debug operation is not performed. Recovery. Use the SHOW NCL command to obtain the ID of the NCL process that you want to debug and retry the command for that NCL ID. NNM1091 DEFAULT NCLID SET TO nclid Cause.
Messages NNM1093 NNM1093 file-name version-letterversion-number date-time Cause. A SHOW NCLOBJECT or SHOW PNLOBJECT command was issued, and the message is part of the response. file-name is the name of a compiled NCL procedure file or panel file. version-letter is the alphabetic part of the NonStop NET/MASTER MS version. version-number is the numeric part of the NonStop NET/MASTER MS version.
Messages NNM1097 NNM1095 FILE file-name IS NOT AN object-type OBJECT FILE Cause. A SHOW NCLOBJECT or a SHOW PNLOBJECT command was issued, but the specified object file either does not exist, or is not an NCL object file (file code 897) or a panel object file (file code 898). file-name is the name used for the object file. object-type is NCL or PANEL. Effect. No information about compiled NCL procedure files or panel files is displayed. Recovery.
Messages NNM1098 NNM1098 file-type file-name IS UP TO DATE, NO COMPILATION NEEDED Cause. An NCLCOMP command was issued, but the specified NCL procedure file or panel file is already compiled into the specified object file and is up to date. file-type is either PROCEDURE or PANEL, indicating the type of file being compiled. file-name is the name of the file that requires no further compilation. Effect. The NCL procedure file or panel file is not recompiled. Recovery.
Messages NNM1098 Use the error number and the sense code to determine the actions to take. INVALID TERMINAL DATA The NonStop NET/MASTER MS system received invalid data from the terminal. The condition may occur when a TACL program (or some other program) competes with the NonStop NET/MASTER MS system for access to the terminal.
Messages NNM1102 your system manager. The manager should contact the Tandem support representative, providing the following information: NCL procedure that caused the error Definition file of the panel that caused the error TIMEOUT An input-output operation timed out on the terminal. The NonStop NET/MASTER MS system uses a timeout period of 30 seconds for each terminal operation. A timeout situation may indicate other problems. For example: The terminal was turned off. Turn the terminal back on.
Messages NNM1200 NNM1103 OPENED TERMINAL logitermname devname Cause. The system retried the OPENTERM command and opened the terminal successfully. logitermname is the logical name of the terminal opened. devname is the device name of the terminal opened. Effect. The NonStop NET/MASTER logon panel is displayed on the opened terminal. Recovery. This message is informational only; no recovery action is necessary. NNM1104 INCORRECT SPLIT COORDINATES Cause.
Messages NNM1201 NNM1201 termname IS NOT KNOWN Cause. A CLOSTERM, OPENTERM, SHOW SESS, or SHOW TERM command was issued for a terminal that is not known to the system. termname is either the logical name or the device name of the terminal. Effect. The command is ignored. Recovery. Use the SHOW TERMDEF=ALL command to list the logical and device names of the terminals. Specify the correct terminal name and retry the command.
Messages NNM1204 NNM1204 logitermname devname color hlite model applstat Cause. A SHOW SESS or a SHOW TERM command was issued, and the message is part of the response. The line contains information about a terminal that is connected to the NonStop NET/MASTER MS system. logitermname is the logical name of the terminal. devname is the device name of the terminal. color is the color option specified for the terminal.
Messages NNM1205 applstat is the status of the terminal. The status is one of the following: IN SESSION indicates that a user is logged on. SUSPENDED indicates that a user is using the PROGRUN command. WAIT LOGON indicates that the terminal is waiting for a user to log on. Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM1205 NO TERMINALS CONNECTED Cause.
Messages NNM1209 NNM1207 CONNECTED TERMINAL logitermname devname Cause. An OPENTERM command was issued and the terminal was successfully connected to the NonStop NET/MASTER MS system. logitermname is the logical name of the terminal connected. devname is the device name of the terminal connected. Effect. The terminal can now be used for NonStop NET/MASTER MS sessions. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1209 INVALID TERMINAL DATA The NonStop NET/MASTER MS system received invalid data from the terminal. The condition may occur when a TACL program (or some other program) competes with the NonStop NET/MASTER MS system for access to the terminal.
Messages NNM1210 TERM BUF SIZE EXCEEDED The terminal buffer became full while a panel was being displayed. A NonStop NET/MASTER MS system uses an output buffer of about 4.1 KB (Tandem 6530 terminals) or 8 KB (IBM 3270 terminals) for panels. Reduce the number of fields in the panel or disable color display to economize on the transferred data. If the problem persists, the message indicates an internal error. Refer the message to your system manager.
Messages NNM1211 NNM1211 NO DISCONNECTED TERMINALS MEET GENERIC CRITERIA OF termmask Cause. An OPENTERM or a TERMINAL DELETE command was issued using a mask (a name ending in an *) to specify terminals. However, there were no disconnected terminals with a name that matched the mask. termmask is the specified mask. Effect. The command is ignored. Recovery. Use the SHOW TERMDEF=ALL command to list the logical and device names of the terminals. Specify a correct mask and retry the command.
Messages NNM1216 NNM1214 DISCONNECTED TERMINAL logitermname devname Cause. A CLOSTERM command was issued, and the terminal was disconnected from the NonStop NET/MASTER MS system successfully. logitermname is the logical name of the terminal disconnected. devname is the device name of the terminal disconnected. Effect. You cannot use the terminal to log on to the NonStop NET/MASTER MS system. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1217 NNM1217 LOGICALNM DEVICENM CLR HI MDL STATUS Cause. A SHOW SESS, SHOW TERM, or SHOW TERMDEF command was issued, and the message is part of the response. The line contains the headings of the display. Other messages provide the actual information. LOGICALNM is the heading for the logical name of a terminal. DEVICENM is the heading for the device name of a terminal. CLR is the heading for the color option specified for the terminal.
Messages NNM1219 STATUS is the heading for the status of the terminal. For the SHOW SESS and SHOW TERM commands, the status is one of the following: IN SESSION indicates that a user is logged on. SUSPENDED indicates that a user is using the PROGRUN command. WAIT LOGON indicates that the terminal is waiting for a user to log on. For the SHOW TERMDEF command, the status is one of the following: CONNECTED indicates that the terminal is connected to NonStop NET/MASTER MS.
Messages NNM1220 NNM1220 DUPLICATE LOGICAL TERMINAL NAME logitermname Cause. A TERMINAL ADD command was issued to assign a logical name to a terminal. However, another terminal had that name already. Logical terminal names must be unique. logitermname is the logical name for the terminal. Effect. The terminal is not added. Recovery. Use the SHOW TERMDEF=ALL command to list the logical names of the terminals. Specify a name that does not appear in the list and retry the TERMINAL ADD command.
Messages NNM1225 NNM1225 logitermname devname color hlite model applstat Cause. A SHOW TERMDEF command was issued, and the message is part of the response. The line contains information about a terminal that is defined to the NonStop NET/MASTER MS system. logitermname is the logical name of the terminal. devname is the device name of the terminal. color is the color option specified for the terminal.
Messages NNM1226 applstat is the status of the terminal. The status is one of the following: CONNECTED indicates that the terminal is connected to NonStop NET/MASTER MS. DISCON'D indicates that the terminal is not connected to NonStop NET/MASTER MS. PEND_CONN indicates that the connection of the terminal to NonStop NET/MASTER MS is in progress. Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1232 NNM1229 USERID MUST BE ENTERED Cause. A logon to the NonStop NET/MASTER MS system was attempted but a user ID was not provided. Effect. The logon request is refused. Recovery. Provide both the user ID and the password, and retry the logon. NNM1230 PASSWORD MUST BE ENTERED Cause. A logon to the NonStop NET/MASTER MS system was attempted but the password was not provided. Effect. The logon request is refused. Recovery. Provide both the user ID and the password, and retry the logon.
Messages NNM1233 NNM1233 MEMORY EXHAUSTED Cause. The NonStop NET/MASTER MS system ran out of memory during a logon request. Effect. The logon request is refused. Recovery. Refer the message to your system manager. The manager should try to recover disk space from the swap volume.
Messages NNM1238 NNM1236 YOUR LOGON HAS BEEN CANCELED Cause. Your request to log on to the NonStop NET/MASTER MS system was successful, but the logon was canceled before your environment was ready. The system may have shut down or another user may have issued a CANCEL command to log you off the system. Effect. The logon is canceled. Recovery. If the system is not shutting down, you can log on to the system again. NNM1237 FILESYSTEM ERROR WHEN CREATING TERMINAL DRIVER Cause.
Messages NNM1239 NNM1239 TOP-LEVEL NCL FILE NOT FOUND Cause. While servicing your logon request, the NonStop NET/MASTER MS system could not find the top-level NCL procedure specified in your UMS profile. Effect. The logon request fails. Recovery. Ensure that the correct name is specified for the main menu procedure in your UMS profile. You can use another account to check or modify your UMS profile.
Messages NNM1244 NNM1242 YOUR TOP-LEVEL NCL HAS BEEN TERMINATED Cause. Your request to log on to the NonStop NET/MASTER MS system was successful, but your top-level NCL procedure was terminated before your environment was ready. The system may have shut down or another user may have issued a FLUSH command that terminated your procedure. Effect. The logon fails. Recovery. If the system is not shutting down, log on to the system again. If the system is shutting down, log on when the system comes up again.
Messages NNM1245 NNM1245 MAXIMUM NUMBER OF USERS EXCEEDED Cause. You tried to log on to the NonStop NET/MASTER MS system but the system could not take on another user. Effect. The logon request is ignored. Recovery. Retry the logon. If the problem persists, refer the message to your system manager. The manager may try to log off inactive users, or may use the SYSPARMS MAXUSERS command to increase the allowed number of users. NNM1246 SHUTDOWN IN PROGRESS Cause.
Messages NNM1293 NNM1290 SYSPARMS CMDAUTH OPERAND - THE VALUE WAS INVALID Cause. A SYSPARMS CMDAUTH command was issued but an invalid value was specified. Effect. The command or command operand authority level remains unchanged. Recovery. Specify a correct value and retry the command. NNM1291 SYSPARMS CMDAUTH OPERAND - MISSING COMMAND NAME Cause. A SYSPARMS CMDAUTH was issued but a command to which to apply the authority level was not specified. Effect.
Messages NNM1294 NNM1294 SYSPARMS CMDAUTH OPERAND - command WAS NOT EXACT COMMAND NAME Cause. A SYSPARMS CMDAUTH command was issued but an invalid command was specified. command is the specified name of the command. Effect. No command or command operand authority level is changed. Recovery. Specify the correct command name and retry the SYSPARMS CMDAUTH command. NNM1295 SYSPARMS CMDAUTH OPERAND - MISSING OPERAND AUTHORITY LEVEL Cause.
Messages NNM1302 NNM1298 SYSPARMS CMDAUTH OPERAND - OPERAND AUTHORITY WAS OUT OF RANGE Cause. A SYSPARMS CMDAUTH command was issued, and an authority level for a command operand was specified but the level was out of range. The level must be from 0 through 255. Effect. The command operand authority level remains unchanged. Recovery. Specify the correct authority level and retry the SYSPARMS CMDAUTH command. NNM1301 background REGION NOT ACTIVE Cause.
Messages NNM1350 NNM1350 PANEL--- ---STATUS--- ---HITS--- ---LIBRARY Cause. A SHOW PANELS, SHOW PANELS=PRELOADED, or SHOW PANELS=LOADED command was issued, and the message is part of the response. The line contains the headings of the SHOW PANELS display. Other messages provide the actual information. PANEL is the heading for the name of the panel. STATUS is the heading for the status of the panel. The status is one of the following: LOADED indicates that the panel is in the active panel queue.
Messages NNM1352 NNM1351 panel status hits library Cause. A SHOW PANELS, SHOW PANELS=PRELOADED, or SHOW PANELS=LOADED command was issued, and the message is part of the response. The line contains information about a panel. panel is the name of the panel. status is the status of the panel. The status is one of the following: LOADED indicates that the panel is in the active panel queue. LOADING indicates that the panel is being loaded into the active panel queue.
Messages NNM1353 NNM1353 NO panel_state PANELS FOUND Cause. A SHOW PANELS, SHOW PANELS=LOADED, or SHOW PANELS=PRELOADED command was issued, but no panels were found. is ACTIVE, LOADED, or PRELOADED. panel_state Effect. The command is ignored. Recovery. This message is informational only; no recovery action is necessary. NNM1354 PANEL SKIP STARTED TO =skipstring Cause. A panel skip operation was started. skipstring is the target of the panel skip, for example, A.B.C. Effect.
Messages NNM1358 NNM1357 PANEL FILE panel-name NOT PRELOADED - INCLUDED PANEL included-panel HAD ERROR errno Cause. A SYSPARMS PPRELOAD command was issued, but a file-system error occurred on a panel description file included by the #INCLUDE statement. panel-name is the name of the file being preloaded. included-panel is the name of the included file on which the error occurred. errno is a Guardian file-system error number indicating the type of error. Effect.
Messages NNM1359 NNM1359 INCLUDE PANEL panel-name NOT DEFINED. ERROR=errno. Cause. A PANEL verb was issued to display a panel, but a #INCLUDE statement specified a panel description file that is not in the user panel library, customized panel library, or distribution panel library. panel-name identifies the panel description file that caused the error. errno is a Guardian file-system error number. Effect. The panel is not displayed. Recovery.
Messages NNM1363 NNM1361 PANEL panel NOT DEFINED. ERROR=errno. Cause. A PANEL verb was issued to retrieve a panel that was not in one of the following panel libraries: User panel library Customized panel library Distribution panel library panel is the name of the panel. errno is the Guardian file-system error number Effect. The request is ignored. Recovery. Use UMS to view the user panel library specified in your user ID definition.
Messages NNM1364 NNM1364 INSUFFICIENT STORAGE Cause. A PANEL verb was issued, and there was not enough CPU memory to process the request to display the panel. Effect. The request is ignored. Recovery. Retry the request. If the condition persists, refer the message to your system manager. NNM1365 PREPARSE VARIABLE SYNTAX ERROR OR EXCEEDED SUBSTITUTION LIMIT Cause.
Messages NNM1370 NNM1368 #OPT CURSOR OPERAND SPECIFIES INVALID VARIABLE NAME OR COORDINATES Cause. The #OPT statement specified the CURSOR operand with an invalid variable name or invalid coordinates. The coordinates must be in the range 1 through 62 for rows and 1 through 132 for columns. Effect. The panel is not displayed. Recovery. Ensure that the specified variable name resolves to a valid simple variable name, or that the coordinates are in the correct range.
Messages NNM1371 NNM1371 MORE THAN 90 #FLD ATTRIBUTE CHARACTERS SPECIFIED Cause. The panel description file contained more than 90 different field attribute characters. Only up to 90 different field attribute characters can be used in the same file. Effect. The panel is not displayed. Recovery. Reduce the number of different field attribute characters in the description file to 90, and restart the procedure. NNM1372 INVALID INWAIT OPERAND SPECIFIED Cause.
Messages NNM1377 NNM1375 #OPT ERRFLD OPERAND SPECIFIES INVALID VARIABLE Cause. The #OPT statement specified the ERRFLD operand with an invalid variable name. The name must resolve to a simple variable name after substitution. Effect. The panel is not displayed. Recovery. Specify a correct variable name for the ERRFLD operand in the panel description file, and ensure that the name resolves to a simple variable name. Restart the procedure. NNM1376 PANEL STATEMENT EXCEEDS MAXIMUM SIZE: size Cause.
Messages NNM1378 NNM1378 PANEL ERROR - SYNTAX LINE lineno - errtext Cause. The line in the display part of the panel contained an error. lineno is the display part line number at which the error occurred. errtext is one of the following: MULTIPLE INPUT VARIABLES You cannot have more than one variable name for each input field attribute. Ensure that you specify one variable for one input and that the specified variable name resolves to a simple variable name after substitution.
Messages NNM1383 NNM1380 PANEL DATASTREAM REQUIREMENTS EXCEED BUFFER SIZE Cause. The panel description file produced a data stream that was too big for Panel Services to handle. Effect. The panel is not displayed. Recovery. Redesign the panel to economize on the transferred data, then restart the NCL procedure. Try to use no more than 250 input fields. NNM1381 PANEL EXPANSION ERROR Cause. The attempt to display the panel failed. The resolved variable name has an invalid length.
Messages NNM1384 NNM1384 PANEL VERB DEFINITION ERROR Cause. The user did not use the PANEL verb correctly. Effect. The panel is not displayed. Recovery. Check the panel names, panel types, and variables used in the PANEL verb statement. The names of consecutive asynchronous panels must match if the PANEL verbs are not separated by the PANELEND verbs. Correct the discrepancy, then restart the NCL procedure. NNM1385 PANEL DISPLAY ERROR Cause. The attempt to display the panel failed.
Messages NNM1390 NNM1388 PANEL FILE filename DOES NOT EXIST IN LIBRARY libname Cause. A SYSPARMS PPRELOAD or PUNLOAD command was issued, but it could not find the panel description file in the subvolume. filename is the name of the file being accessed. libname is the name of the subvolume specified for the file or the first subvolume in the panel search path if no subvolume is specified. Effect. The command is rejected. Recovery.
Messages NNM1391 NNM1391 UNLOAD OF PANEL FILE filename ACCEPTED Cause. A SYSPARMS PUNLOAD command was issued and accepted. filename is the name of the panel description file to be unloaded. Effect. The panel description file is unloaded. Recovery. You can use the SHOW PANELS command to determine the status of the files. NNM1392 filename NOW PRELOADED Cause. A SYSPARMS PPRELOAD command was issued and was successful. The specified panel description file is now available for use system wide.
Messages NNM1398 NNM1395 PANEL ERROR - TRAILER LINES EXCEED MAXIMUM OF number-of-lines LINES Cause. A PANEL verb was issued, but the number of trailer lines in the panel description file exceeded the maximum allowed for the display terminal. number-of-lines is the maximum number of trailer lines allowed for the terminal. Effect. The panel is not displayed. Recovery. The maximum number of trailer lines allowed in a panel description file is equal to the number of rows on the display terminal.
Messages NNM1399 NNM1399 EVENT: event NOTIFY: PANEL OBJECT: panel Cause. An event occurred in an asynchronous panel. event panel is the type of event: CHANGE indicates that the size of the displayed panel changed. INPUT indicates that an input to the panel has occurred. TAKEOVER indicates that another panel has taken over the display area. is the name of the panel. Effect. The event is displayed. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1401 NNM1401 process_name ABENDING AT P=%paddr, TRAP=trapid,trapname Cause. A system trap occurred in a Global Memory Manager (GMM) process. The message includes useful information to help your Tandem support representative to identify the problem: process_name is the name of the failed GMM process. paddr is the memory address of the code that failed. trapid is an ID to help your Tandem support representative to identify the problem. trapname is the name of the trap that occurred.
Messages NNM1402 NNM1402 WARNING: backup-status Cause. The backup process of the Global Memory Manager (GMM) was not running. This is a warning message informing the user that the GMM process cannot be recovered if the primary process is stopped. backup-status provides information about the backup processes as follows: BACKUP PROCESS NOT RUNNING The backup of a GMM process cannot be started because the backup processor is not available.
Messages NNM1455 NNM1452 UNABLE TO COMMUNICATE WITH COMMAND SERVER process_name (Error errno) Cause. An OPSYS command was issued but the NonStop NET/MASTER MS system could not communicate with the command server of the DSNM subsystem. process_name is the name of the process that caused the error (this is one of the CIP or CMDSVR process names specified through the PARAM command or the default if none is specified). errno is the Guardian file-system error number. Effect. The command is ignored.
Messages NNM1456 NNM1456 responsetext Cause. The message contains the response text from a utility (for example, FUP) that was submitted for execution through an OPSYS command. The response may require several of these messages (that is, NNM1456) terminated by the message *END. responsetext contains the text of the response. Effect. The response is displayed. Recovery. This message is informational only; no recovery action is necessary. NNM1457 UNABLE TO ALLOCATE TERMINAL FOR PROGRAM Cause.
Messages NNM1461 NNM1459 PROCESS process_name CREATED FOR objfile Cause. A PROGRUN command was issued, and Guardian services created a process for the program. process_name is the name of the process. objfile is the name of the program specified for PROGRUN. Effect. The specified program is now executing. Recovery. This message is informational only; no recovery action is necessary. NNM1460 PROCESS process_name FOR objfile stop_reason Cause. The process for the program stopped or abended.
Messages NNM1462 NNM1462 NO DSNM COMMAND SERVER IS AVAILABLE TO PROCESS COMMAND Cause. The user issued an OPSYS command but there were no DSNM command servers (CMDSVR). Effect. The command is ignored. Recovery. Refer the message to your system manager. The manager should include the CMDSVR parameter in the configuration and restart the system. NNM1463 DSNM SUBSYSTEM INITIALIZATION FAILED (Error error) Cause.
Messages NNM1469 NNM1466 PROGRUN IN PROGRESS, UNABLE TO START objfile Cause. The system could not process this PROGRUN command because another PROGRUN was active. Only one PROGRUN can be active at a time. is the name of the program to execute. objfile Effect. The program does not execute. Recovery. Wait for the existing PROGRUN to finish, then retry the command. The message NNM1460 indicates the termination of the PROGRUN that was active. NNM1467 UNABLE TO START TEDIT Cause.
Messages NNM1470 NNM1470 errtext Cause. The message contains any error text sent by the Conversational Interface Process (CIP) in response to an OPSYS command. errtext contains the CIP error text. Effect. The error text is displayed. Recovery. Use the CIP error text to determine the appropriate action to take. NNM1471 INVALID FILE NAME SPECIFICATION filename Cause. An invalid file name was specified for Edit Services. filename is the name specification of the file. Effect.
Messages NNM1504 NNM1503 LOGSWAP REQUESTED BY userid STARTED Cause. The LOGSWAP command was accepted. userid is the ID of the user that issued the command. Effect. The current log file will be closed and the next available log file opened. The closed log file is available for automatic reuse if the LOGWRAP system parameter has the value YES. Recovery. This message is informational only; no recovery action is necessary. NNM1504 LOGSWAP REQUEST REJECTED, errtext Cause.
Messages NNM1505 NNM1505 NAME STATUS START DATE TIME STOP DATE TIME SWPD BY Cause. A SHOW LOGS command was issued, and the message is part of the response. The line contains the headings of the SHOW LOGS display. Other messages provide the actual information. NAME is the heading for the logical name of a log file. STATUS is the heading for the status of the file. The status is one of the following: AVAIL indicates that the file is available for use. IN USE indicates that the file is in use.
Messages NNM1506 NNM1506 logical-name status starttime stoptime userid Cause. A SHOW LOGS command was issued, and the message is part of the response. The line contains information about a log file. logical-name is the logical name of the log file: LOG1 through LOG9. status is the status of the file. The status is one of the following: AVAIL indicates that the file is available for use. IN USE indicates that the file is in use. SWAPPED indicates that the file has been swapped.
Messages NNM1507 NNM1507 NNM LOG SUBSYSTEM DOES NOT HAVE ANY AVAILABLE LOG FILES.error Cause. The LOG subsystem was unable to log event messages. Possible causes are: LOGWRAP system parameter has a value of NO and all declared log files were used once already Log files are secured from access by the LOG subsystem, in which case the reason for the error is returned error contains a Guardian file-system error number and the name of the file that is in error. Effect.
Messages NNM1516 NNM1510 LOG FILE logfilename REJECTED - WRONG FILE PARAMETERS Cause. A LOGSWAP command was issued, and the log subsystem attempted to use the log file but the file has the wrong parameters. This can only happen if the log subsystem was forced to use a file created in advance by the user. The user-provided log file must include: Enscribe key sequenced file Block record 4096 Record length 4060 Primary key length 44 Primary key offset 0 Effect.
Messages NNM1517 NNM1517 LOG BROWSE OF FILE filename Cause. You are browsing through the log file. filename is the name of the log file. Effect. The log file is being browsed. Recovery. This message is informational only; no recovery action is necessary. NNM1518 fileid FILE IO ERROR = errno Cause. An input-output error occurred while you were accessing a log file. fileid is the UDB ID of the log file. errno is the Guardian file-system error number. Effect. The operation fails. Recovery.
Messages NNM1523 NNM1520 READ ERROR ON fileid RC=return_code Cause. An error occurred during the execution of the NCL verb FILE GET in a Log Browse session. fileid is the UDB ID of the log file that is browsed. return_code is the FILE GET verb return code. Effect. The operation is ignored. Recovery. Use the return code to determine the appropriate action to take. NNM1521 INVALID COMMAND Cause. You entered an invalid command.
Messages NNM1524 NNM1524 INVALID DATE - MUST BE DD-MMM-YY OR [+|-]N Cause. A Log Browse DATE command was issued but you entered an invalid value. The value must be in the format dd-mmm-yy, +n (n days after the currently browsed date), or -n (n days before the currently browsed date). n must be from 0 through 99. For example, 20-nov-91, +1, or -1. Effect. The command is ignored. Recovery. Specify a valid value and retry the command. NNM1525 INVALID DATE VALUE Cause.
Messages NNM1529 NNM1528 SEARCH ERROR, NO SUCH TIME Cause. A Log Browse TIME command was issued but there were no log records for the specified time. Effect. The command is ignored. Recovery. This message is informational only; no recovery action is necessary. NNM1529 ENTER A FIND CODE AND STRING Cause. A Log Browse FIND command was issued with an invalid find code or missing parameters.
Messages NNM1530 NNM1530 INVALID FORMAT OF find_code_name NAME Cause. A Log Browse FIND command was issued but you entered an invalid string for the type of search. The format is incorrect. find_code_name is one of the following: NODE indicates a domain ID search (find code S). ID STRING indicates a text string search (find code C). TERM indicates a terminal name search (find code N or T). USER indicates a user ID search (find code U).
Messages NNM1534 NNM1532 num_of_lines LINES SEARCHED - find_code_name 'str_name' NOT FOUND Cause. The Log Browse FIND command could not find the string. num_of_lines is the number of lines searched. find_code_name is the name of the find code. str_name is the item to search for. Effect. The search stops, and the item is not found. Recovery. This message is informational only; no recovery action is necessary. NNM1533 REACHED FIND END LABEL Cause. A Log Browse FIND command was issued.
Messages NNM1535 NNM1535 find_code_name 'str_name' NOT FOUND BEFORE END OF LOG REACHED Cause. A Log Browse FIND command was issued. However, while searching forward for the item, the end of the log file was reached and the item was not found. find_code_name is the name of the find code. str_name is the item to search for. Effect. The search stops and the item is not found. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1542 NNM1539 UNKNOWN LABEL 'label' Cause. A Log Browse LOCATE command was issued but the label is not known to the Log Browse procedure. The label must be previously defined to Log Browse through the LABEL command. Effect. The command is ignored. Recovery. Either use a defined label or use the Log Browse LABEL command to define the label. Retry the Log Browse LOCATE command. NNM1540 LABEL NAME MUST BE A MAXIMUM OF 8 ALPHANUM CHARS Cause.
Messages NNM1543 NNM1543 INVALID VALUE WITH RECORD SCROLL ACTION Cause. An F7 or an F8 scroll key was pressed but an incorrect value was used. Valid values are as follows: D indicates scrolling to the last log record of the previous day or first log record of the next day. M indicates scrolling to the first or last log record of the current day. n indicates scrolling past the number of log records before or after the current record. blank indicates scrolling to the previous or next page of records.
Messages NNM1551 NNM1545 LOG IO ERROR errno ON filename Cause. An I/O error occurred when writing to the activity log. errno is the Guardian file-system error number. filename is the name of the log file that causes the error. Effect. The current log file is closed, and the next available log file is opened. If the error number is 45 (file full) and the LOGWRAP system parameter has the value YES, the log file is available for automatic reuse.
Messages NNM1552 NNM1552 process_name LOGON FAILED: ERROR=error Cause. The logon failed because of a failed request to the NonStop NET/MASTER MS control process. error is either a Guardian file-system error number or some error text. Error text is one of the following: CLOSTERM COMMAND There was a CLOSTERM command for the terminal, or the NonStop NET/MASTER MS system is shutting down. If necessary, check who else has modified the status of the specified terminal.
Messages NNM1552 NO FUNCTION KEY RETURNED The NonStop NET/MASTER MS system received an invalid function key value from the terminal. The condition may occur when a TACL program (or some other program) competes with the NonStop NET/MASTER MS system for access to the terminal.
Messages NNM1553 NET/MASTER MS system uses an output buffer of about 4.1 KB (Tandem 6530 terminals) or 8 KB (IBM 3270 terminals) for panels. Reduce the number of fields in the panel or disable color display to economize on the transferred data. If the problem persists, the message indicates an internal error. Refer the message to your system manager.
Messages NNM1553 The condition may occur when a TACL program (or some other program) competes with the NonStop NET/MASTER MS system for access to the terminal. Ensure that: Any TACL or COMINT program running on the terminal is paused, for example, through the PAUSE command No other programs are accessing the terminal There are no faults with the physical connection of the terminal INVALID TERMINAL TYPE The terminal is of an unsupported type. Supported types are IBM 3270 and Tandem 6530 class of devices.
Messages NNM1553 TOO MANY LOGONS FOR THIS USERID The user had too many logons to the NonStop NET/MASTER MS system. The system manager can give the user authority to log on to the system more than once. SECURITY CHECK FAILED The security subsystem of the NonStop NET/MASTER MS system did not authorize your request to log on. Your user ID, password, or both were invalid, or you have no authority to use this terminal. Refer the message to your security administrator.
Messages NNM1556 NNM1554 CANNOT RESTORE TERM devname: ERROR=errno Cause. A logoff was in progress but the attempt to return the terminal to its status before it was taken over by the NonStop NET/MASTER MS system failed. devname is the device name of the terminal where the logoff took place. errno is the Guardian file-system error number. Effect. The logoff continues. Recovery. Refer the message to your system manager.
Messages NNM1557 NNM1557 shutdown-command COMMAND FAILED Cause. You supplied a name that is not that of a NonStop NET/MASTER MS control process to the NNM shutdown utility. shutdown-command is either FSTOP or SHUTDOWN (for both SHUTDOWN and SHUTDOWN $ABEND$). Effect. The attempt to execute the NNM shutdown utility fails. Recovery. Correct the control process name, and retry. You can use the TACL STATUS command to retrieve the name of the control process. NNM1558 INSUFFICIENT COMMAND AUTHORITY Cause.
Messages NNM1562 NNM1560 process-name shutdown-command PROCEEDING Cause. You used the NNM shutdown utility to issue an FSTOP or SHUTDOWN command while the target NonStop NET/MASTER MS system was still initializing. The command cannot be processed because the NonStop NET/MASTER MS control process is not ready. The message indicates that shutdown is pending. process-name is the name of the control process for the NonStop NET/MASTER MS system to be shut down. shutdown-command is either FSTOP or SHUTDOWN.
Messages NNM1600 NNM1600 SPI_TKNDEF ERROR errno Cause. A RUN MDMAINT command was issued but the Map Data Maintenance program got an error from a SPI_TKNDEF procedure while reading the EMS template file. errno is a Guardian file-system error number. Effect. The program is terminated, and the map is not built. Recovery. Use the error number to determine the appropriate action to take. Correct the cause of the error and rerun the program. NNM1601 READING TEMPLATE FILE filename Cause.
Messages NNM1607 NNM1604 ILLEGAL FILENAME filename Cause. A RUN MDMAINT command was issued but an invalid map file name was specified. filename is not a valid Tandem file name. Effect. The program is terminated, and the map is not built. Recovery. Specify a valid disk file name for the map file and rerun the program. NNM1605 ERROR errno ON action filename Cause.
Messages NNM1608 NNM1608 filename DOES NOT HAVE RECLEN=1024, KEYLEN=36, KEYOFFSET=0 Cause. A RUN MDMAINT command was issued but the specified file did not satisfy the criteria for a map file. You may have specified a wrong file. filename is the name specified. Effect. The program is terminated, and the map is not built. Recovery. Specify the name of a valid map file and rerun the program. NNM1609 BUFFER OVERFLOW Cause.
Messages NNM1615 NNM1612 REDEFINING FIELD token.field IGNORED Cause. A RUN MDMAINT command was issued, and a field that is a redefinition was found. token is the name of the token that contains the redefining field. field is the name of the field that raised the message. Effect. The field is ignored and is not accessible in NCL. Recovery. If the field is in your own subsystem, you can modify the DDL definition so that the field is not a redefining field. NNM1613 UNKNOWN ARGUMENT paramname Cause.
Messages NNM1620 NNM1620 FILE filename CANNOT BE OPENED Cause. A RUN MDMAINT command was issued but the file that identifies subsystems that are foreign to the Tandem environment could not be opened. The file is not a readable EDIT format file. You may have specified the wrong file. filename is the specified name of the file. Effect. Tokens for the foreign subsystems are ignored and are not available in NCL. Recovery. Specify the correct file as the second parameter and rerun the program.
Messages NNM1625 NNM1623 DUPLICATE OWNER owner_name Cause. A RUN MDMAINT command was issued, and a file identifying owners that are foreign to the Tandem environment was specified. A line in the file must contain the name of a foreign owner and a unique positive number. The name of the owner was duplicated. owner_name is the name of the owner. Effect. The duplicate owner name is ignored. Recovery. Remove the duplication, and rerun the program. NNM1624 OWNER owner_name IGNORED Cause.
Messages NNM1626 NNM1626 ID owner_number FOR OWNER owner_name MUST BE GREATER THAN 0 Cause. A RUN MDMAINT command was issued, and a file identifying owners that are foreign to the Tandem environment was specified. A line in the file must contain the name of a foreign owner and a unique positive number. The number specified was not positive. owner_number is the number that was in error. owner_name is the name of the owner. Effect.
Messages NNM1632 NNM1629 USER MAP - DICTIONARY LOCATION REQUIRED Cause. A RUN MDMAINT command was issued to create a user map for a given DDL definition, but the location of the data dictionary was not supplied. Effect. The MDMAINT program is terminated, and the map is not built. Recovery. Supply the location of the dictionary in the format $volume.subvolume, and rerun the program. NNM1630 USER MAP - DDL REC OR DEF NAME REQUIRED Cause.
Messages NNM1633 NNM1633 INVALID OBJECT TYPE ddl_object_type MUST BE 'R' OR 'D' Cause. A RUN MDMAINT command was issued to create a user map for a given DDL definition, but the expected object type R indicating a DDL record or D indicating a DDL definition was not supplied. Effect. The MDMAINT program is terminated, and the map is not built. Recovery. Supply object type R for a DDL record or D for a DDL definition, and rerun the program. NNM1634 DUPLICATE MAPNAME map-name Cause.
Messages NNM1637 NNM1636 INVOKE ERROR : errtext Cause. A RUN MDMAINT command was issued to create a user map for a given DDL definition, but an error occurred while accessing the definition. errtext is one of the following : 1. DICTIONARY NOT LOCATED IN THIS SUBVOL $volume.subvolume 2. RECORD NAME record_name NOT FOUND IN DICTIONARY 3. DICTIONARY IS CORRUPT 4. INSUFFICIENT MEMORY 5. FILE ERROR ACCESSING DICTIONARY filename 6. UNSUPPORTED DICTIONARY VERSION ERRNO errno Effect.
Messages NNM1638 NNM1638 INVALID MAPNAME map-name Cause. A RUN MDMAINT command was issued with an invalid map name, or no map name was supplied and the name defaulted to the name of the DDL record or definition. The map name is invalid if it exceeds 32 characters, begins with a $ or a number, or contains other nonalphanumeric characters. map-name is the invalid name used for the map. Effect. The MDMAINT program is terminated. Recovery. Rerun the program using a valid map name.
Messages NNM1702 NNM1641 MAXIMUM MAPNAME LENGTH EXCEEDED map-name Cause. The map name supplied with the RUN MDMAINT command exceeded 32 characters. If no map name was supplied with the RUN MDMAINT command, the map name defaulted to the name of the DDL record or definition. map-name is the invalid name used for the map. Effect. The MDMAINT program is terminated. Recovery. Rerun the program using a valid map name. NNM1642 USER MAP - MAPNAME REQUIRED FOR DELETE Cause.
Messages NNM1704 NNM1704 COMMAND REJECTED. LIMIT OF maxtmrcmd TIMER BASED COMMANDS REACHED Cause. An AT or EVERY command was issued but the NonStop NET/MASTER MS system could not take on another timer command. maxtmrcmd is the maximum number of active timers allowed. Effect. The command is not queued for execution. Recovery. Retry the command later. The system may have purged some timer commands thus allowing new timer commands to run.
Messages NNM1711 NNM1708 TIMER TID=timerid VALUE ALREADY ASSIGNED Cause. An AT or EVERY command was issued with an ID (timerid) but the ID was assigned to another timer command already. Effect. The command is not queued for execution. Recovery. Use the SHOW TIMER command to list the user-assigned timer IDs. Specify an ID that does not appear in the list and retry the timer command. NNM1709 *+TIME ONLY VALID ON 'AT' COMMAND Cause. An EVERY command was issued, and a time offset expression was specified.
Messages NNM1712 NNM1712 MAXIMUM TIMER IDENTIFICATION IS maxtmrid CHARACTERS Cause. An AT or EVERY command was issued but the user-assigned timer ID exceeded 12 characters. Effect. The command is not queued for execution. Recovery. Specify a timer ID of not more 12 characters and retry the command. NNM1713 THE SYSTEM ASSIGNED TIMER NUMBER IS FULL Cause. An AT or EVERY command was issued but the NonStop NET/MASTER MS system could not take on another timer command.
Messages NNM1720 NNM1716 'EVERY' CANNOT BE SOURCED FROM AN 'EVERY' COMMAND Cause. An EVERY command was issued but another EVERY command was specified as the timed command. The operation is illegal. Effect. The command is not queued for execution. Recovery. Remove any EVERY command that may be issued through the command text string. Retry the command. NNM1717 UNABLE TO START TIMER Cause.
Messages NNM1721 NNM1721 ID BY INTERVAL -USERID-R LIM CNT K/P ENV P/M TID Cause. A SHOW TIMER command was issued, and the message is part of the response. The line contains the headings of the SHOW TIMER display. Other messages provide the actual information. ID is the heading for the system-assigned timer ID. BY is the heading for the type of the timer command. The type is one of the following: AT (AT command) or EV (EVERY command).
Messages NNM1722 NNM1722 timer_number command hr:min:sec env purgemsg timerid useridr limit count keep Cause. A SHOW TIMER command was issued, and the message is part of the response. The line contains information about a timer command in the NonStop NET/MASTER MS system. timer_number is the system-assigned timer ID. command is the type of the timer command. The type is one of the following: AT (AT command) or EV (EVERY command).
Messages NNM1723 Recovery. This message is informational only; no recovery action is necessary. NNM1723 NUMBER OF TIMER COMMANDS DISPLAYED WAS count Cause. A SHOW TIMER command was issued. The message is part of the response, and gives the number of timer commands in the NonStop NET/MASTER MS system. Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM1724 NO ACTIVE TIMER COMMANDS FOR USER ID userid Cause.
Messages NNM1733 NNM1731 TIMER COMMAND timer_number PURGED, userid NOT AVAILABLE AS OCS OPERATOR Cause. The user exited from OCS causing the purge of a previously issued timer command with no KEEP and ROUTE operands. timer_number is the system-assigned ID of the command. userid is the ID of the user controlling the command. Effect. The timer command is purged. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1734 NNM1734 HIGHER AUTHORITY LEVEL IS REQUIRED TO PURGE ANOTHER USER'S COMMAND - TIMER purge_timer_id Cause. A PURGE TIMER command was issued to purge a timer command created by another user. This function requires a higher authority level than you have. purge_timer_id is the specified timer ID which can be either the system-assigned or the user-assigned timer ID. Effect. The timer command is not purged. Recovery.
Messages NNM1752 NNM1738 NO TIMER COMMANDS ACTIVE, PURGE IGNORED Cause. A PURGE TIMER command was issued but no timers were active. Effect. No timer commands are purged. Recovery. This message is informational only; no recovery action is necessary. NNM1750 SSCP INTERFACE AVAILABLE FOR USE Cause. A CNM START command was issued. The NonStop NET/MASTER MS SSCP interface has become active and can process CNM messages. Effect. CNM messages can now be processed. Recovery.
Messages NNM1753 NNM1753 SSCP INTERFACE ALREADY STARTED Cause. A CNM START command was issued but the NonStop NET/MASTER MS SSCP interface already exists, and CNM messages are being processed. Effect. The command is ignored and the SSCP interface continues to process CNM messages. Recovery. This message is informational only; no recovery action is necessary. NNM1754 CNM STOP COMMAND ACCEPTED Cause. A CNM STOP command was issued, accepted, and will be processed. Effect.
Messages NNM1760 NNM1757 SSCP INTERFACE OPEN ERROR errno Cause. A CNM START command was issued but the attempt to open the NonStop NET/MASTER MS SSCP interface failed. The CNMAPPLNME system parameter contains the name of the interface. errno is a Guardian file-system error number. Effect. The SSCP interface is not started. Recovery. Use the error number to determine the appropriate action to take. After you have corrected the problem, use the CNM START command to restart the interface.
Messages NNM1762 NNM1762 data Cause. An REQMS command was issued, and the message contained the solicited data that was returned in response to the command. Effect. The data is displayed. Recovery. This message is informational only; no recovery action is necessary. NNM1763 CNM RECV - NEGATIVE RESPONSE, SEQ=prid SENSE=sense Cause. An REQMS command was issued, and a negative response from the target was received in reply to the command. prid is the sequence number of the REQMS request.
Messages NNM1850 NNM1766 CNM CONNECT REJECTED, ERROR INTERNAL errno EXTERNAL sense Cause. A CNM START command was issued but the process of connecting to the NonStop NET/MASTER MS SSCP interface failed. The CNMAPPLNME system parameter contains the name of the interface. errno is the Guardian file-system error number. sense is the SNA sense code. Effect. The SSCP interface is not started. Recovery. Use the error number and the sense code to determine the actions to take.
Messages NNM1851 NNM1851 INVALID ENVIRONMENT FOR FK COMMAND Cause. An FK command was issued from an invalid environment. The FK command can only be executed in an OCS environment or as part of the INIT procedure. Effect. The command is rejected. Recovery. Remove the FK command from NCL procedures that are executed in background, ROC, or dependent environments. NNM1852 KEY TYPE --ASSOCIATED TEXT-- Cause. A FK command was issued to list the function keys, and the message is part of the response.
Messages NNM1858 NNM1855 NAME OF FUNCTION KEY ILLEGAL FOR THIS DEVICE fnkey Cause. An FK command was issued using a function key that is not valid for this type of terminal. The key name must be valid for the type of terminal used. fnkey is the name of the function key. Effect. The command is rejected. Recovery. Specify a function key that is valid for the terminal and retry the command. NNM1856 NAME OF FUNCTION KEY ILLEGAL FOR THIS ENVIRONMENT fnkey Cause.
Messages NNM1859 NNM1859 COULD NOT START NCL PROC procname Cause. You pressed an action key (function key of type ACT) but the associated NCL procedure failed to start. procname is the name of the procedure. Effect. The procedure is not started. Recovery. Use the FK command to list the action key and check the name of the associated procedure: If the name is incorrect, use the FK command to redefine the key.
Messages NNM1900 NNM1863 command COMMAND REJECTED. errtext Cause. An ENTER, FK, or PF command was issued but failed. errtext is one of the following: NO PFK LIST FOUND There is a memory shortage. Retry the command. If the problem persists, refer the message to your system manager. The manager should try to recover disk space from the swap volume. CANNOT RESET GLOBAL ASSIGNMENT An ENTER IMM command was issued in the INIT procedure. Remove the command from the procedure.
Messages NNM1901 NNM1901 NCL nclid DEBUG SESSION INITIATED Cause. A DEBUG START command was issued, and a debug session for an NCL process was initiated. nclid is the ID of the NCL process to be debugged. Effect. The NCL process is now in a debug session. Recovery. This message is informational only; no recovery action is necessary. NNM1902 NCL nclid SUSPENDED location bp LINE lineno Cause. The NCL process was suspended because of a debug operation. nclid is the name of the NCL process suspended.
Messages NNM1907 NNM1904 NCL nclid HAS OTHER DEBUG SESSION Cause. An attempt was made to debug an NCL process but the NCL process was in another debug session. nclid is the ID of the NCL process to be debugged. Effect. The debug operation is not performed. Recovery. Specify the correct NCL ID. NNM1905 NCL nclid RESUMED Cause. A DEBUG RESUME command was issued, and the execution of the NCL process was resumed. nclid is the ID of the NCL process that was resumed. Effect.
Messages NNM1908 NNM1908 NCL nclid LOAD OF filename status Cause. A DEBUG LOAD command was issued, and the message indicates whether the command was successful. nclid is the ID of the NCL process that loads the file. filename is the name of the file to be loaded. status is SUCCESSFUL or UNSUCCESSFUL. Effect. The file is either loaded or not loaded. Recovery. If the status is UNSUCCESSFUL, other messages provide further information about the problem.
Messages NNM1913 NNM1911 NCL nclid ROUTINE name NOT FOUND Cause. A DEBUG BREAKPOINT command was issued but the function or procedure that contained the statement at which the breakpoint was set was not found. nclid is the ID of the NCL process being debugged. name is the name of the function or procedure. Effect. The breakpoint is not set. Recovery. Specify the correct function or procedure name and retry the command. NNM1912 NCL nclid STATEMENT stmtspec NOT FOUND Cause.
Messages NNM1914 NNM1914 NCL nclid INVALID NUMERIC SEGMENT IN stmtspec Cause. A DEBUG BREAKPOINT command was issued but the statement specification contained an invalid numeric segment. A numeric segment must be the last but not the only segment in the specification. nclid is the ID of the NCL process being debugged. stmtspec is the statement specification that is in error. Effect. The breakpoint is not set. Recovery. Specify the correct statement specification and retry the command.
Messages NNM1919 NNM1917 NCL nclid BREAKPOINT bpno DOES NOT EXIST Cause. A DEBUG CLEAR command was issued but the specified breakpoint did not exist. nclid is the ID of the NCL process being debugged. bpno is the breakpoint number specified. Effect. No breakpoint is cleared. Recovery. You can use the DEBUG LIST BREAKPOINTS command to list the breakpoints. NNM1918 NCL nclid NO BREAKPOINTS EXIST Cause. A DEBUG LIST BREAKPOINTS command was issued but no breakpoints were found.
Messages NNM1920 NNM1920 NCL nclid SCOPE nesting_level OUT OF RANGE Cause. A DEBUG command was issued but the specified nesting level was out of range. nclid is the ID of the NCL process being debugged. nesting_level is the nesting level specified. Effect. The operation is not performed. Recovery. Use the DEBUG TRACE command to get information about the nesting levels. NNM1921 NCL nclid VBL vblname vblattr VAL "value" Cause.
Messages NNM1923 NNM1922 NCL nclid ATTR vblattr VBL vblname Cause. A DEBUG DISPLAY command was issued, and the message is part of the binary format response. The line contains information about a variable. nclid is the ID of the NCL process. vblattr gives the attributes of the variable: ERRFLD indicates that the panel error setting is present. MDO indicates that the MDO was accessed directly or by a subfield. MODFLD indicates that the panel modification setting is present.
Messages NNM1924 NNM1924 NCL nclid ERROR errcode ACCESSING vblname Cause. A DEBUG DISPLAY command was issued but an error occurred when a variable was being accessed. nclid is the ID of the NCL process. errcode is the NCL error code. vblname is the name of the variable. Effect. The information about the variable is not displayed. Recovery. Use the error code to determine the appropriate action to take. NNM1925 NCL nclid WARNING: NOT SUSPENDED Cause.
Messages NNM1927 NNM1926 NCL nclid LINE# SMT EV ON STMT-TEXT FROM procedure-function Cause. A DEBUG SOURCE command was issued, and the message is part of the response. The line contains the headings of the display. Other messages provide the actual information. nclid is the ID of the NCL process being debugged. LINE# is the heading for the line number of the statement in the source file. SMT is the heading for the statement number.
Messages NNM1928 NNM1928 NCL nclid opcodetext Cause. A DEBUG SOURCE command specifying the DETAIL operand was issued and the message is part of the response. The line contains information about the low level code of the decompiled statement. nclid is the ID of the NCL process being debugged. opcodetext is the information about the low level code. Effect. The information about the low level code is displayed. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1931 NNM1930 NCL nclid type nesting_level stmtspec lineno errname errcode Cause. A DEBUG TRACE command was issued, and the message is a response. The line contains the trace information about an error handler. nclid is the ID of the NCL process being traced. type is E (error handler). nesting_level is the nesting level associated with the stack frame. The value 0 identifies the current nesting level. stmtspec is the specification of the statement being executed.
Messages NNM1932 NNM1932 NCL nclid VBL vblname UPDATED Cause. A DEBUG MODIFY command was issued, and the value of the variable was updated. nclid is the ID of the NCL process being debugged. vblname is the name of the variable updated. Effect. The value of the variable was updated. Recovery. This message is informational only; no recovery action is necessary. NNM1933 NCL nclid type procname PROCESSING COMPLETE Cause. An NCL process being debugged has terminated.
Messages NNM1937 NNM1935 NCL nclid END OF type name Cause. A DEBUG SOURCE command was issued, and the message is part of the response. The line indicates that all the decompiled statements are listed. nclid is the ID of the NCL process being debugged. type is FUNCTION or PROCEDURE. name is the name of the function or procedure. Effect. The decompiled statements are listed. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1938 NNM1938 NCL nclid BREAKPOINT ON type VARIABLE vblname ILLEGAL Cause. A DEBUG BREAKPOINT command was issued on a global, MDO or system variable You cannot set breakpoints on global, MDO, or system variables. nclid is the ID of the NCL process being debugged. type is GLOBAL, MDO, or SYSTEM. vblname is the name of the variable specified. Effect. The breakpoint is not set. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1942 NNM1940 NCL nclid T SC STMTSPEC LINE# Cause. A DEBUG TRACE command was issued, and the message is part of the response. The line contains the headings of the DEBUG TRACE display. Other messages provide the actual information. nclid is the ID of the NCL process. The headings are as follows: T is the heading for a type code indicating whether a line of stack trace information is for an error handler (E), a function (F), a procedure (P), or a subroutine (G).
Messages NNM1943 NNM1943 WINDOW window_number ALREADY DEBUGGED dsession Cause. A DEBUG START command was issued to start a debug session in a window that was already being debugged. window_number is the identification number for the window: 1 or 2. dsession is null if debugged by the current session or BY ANOTHER SESSION if debugged by another session. Effect. The debug session is not started. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM1948 NNM1946 NCL nclid NO VARIABLES STARTING WITH vblname EXIST Cause. A DEBUG DISPLAY command was issued, and a variable reference ending in an asterisk (*) was specified. No variables with names that matched the reference were found. nclid is the ID of the NCL process being debugged. vblname is the name of the variable reference specified. Effect. No variables are displayed. Recovery. Specify a correct variable reference. NNM1947 DEBUG SESSION HAS ENDED Cause.
Messages NNM1949 NNM1949 NEW NCL WILL BE SUSPENDED IN THE TARGET ENVIRONMENT number_of_procs Cause. A DEBUG START command was issued, and a debug session was started in the target environment. New NCL processes in the environment will be suspended for debug operations. The target environment can be one of the following: the current environment, the dependent environments, or all environments (that is, both the current and dependent environments).
Messages NNM1955 NNM1952 INCOMPLETE OPERATION - PROCEDURE 'procname' Cause. The NCL compiling process for the NCL procedure failed. The compilation was incomplete. procname is the name of the procedure. Effect. No executable code is produced. Recovery. Recompile the procedure. NNM1953 error_type filename lineno type VALUE REQUIRED Cause. A line in the file required a value of the specified type. error_type is ERROR:. filename is the name of the file containing the error.
Messages NNM1956 NNM1956 MDO KEYWORD MUST BE QUALIFIED BY A STEM VARIABLE Cause. The ASSIGN verb specified an invalid variable for the MDO keyword. In the context, the MDO keyword must take a stem variable. Effect. No executable code is produced. Recovery. Specify a stem name for the MDO keyword. NNM1957 INVALID MDO NAME Cause. The ASSIGN verb specified an invalid variable for the MDO keyword. The MDO keyword must take a stem or a compound variable. Effect. No executable code is produced. Recovery.
Messages NNM1963 NNM1960 INVALID SYNTAX IN BOOLEXPR EXPRESSION: lexical_element_1 lexical_element_2 Cause. The expression passed to the BOOLEXPR built-in function was not syntactically correct. The end of the expression that was expected at the position of lexical_element_2 was not found. lexical_element_1 and lexical_element_2 are part of the expression and identify the location of the error. Effect. The value INVALID is returned from BOOLEXPR. Recovery. Correct the Boolean expression.
Messages NNM1964 NNM1964 EXPECTED RELATIONAL OPERATOR, FOUND: lexical_element Cause. The expression passed to the BOOLEXPR built-in function was not syntactically correct. A relational operator (for example, = or >) that was expected at the position of lexical_element was not found. Effect. The value INVALID is returned from BOOLEXPR. Recovery. Correct the Boolean expression. NNM1965 RANGE OR GENERIC ONLY VALID FOR = AND \= OPERATORS Cause.
Messages NNM1971 NNM1968 STRING:NUMBER OR NUMBER:STRING IS NOT A VALID RANGE Cause. The expression passed to the BOOLEXPR built-in function was not syntactically correct. A range was specified either starting with a string literal and ending with a number or starting with a number and ending with a string literal. Both sides of a range must be of the same type: either both string literals or both numbers. Effect. The value INVALID is returned from BOOLEXPR. Recovery. Correct the Boolean expression.
Messages NNM1972 NNM1972 CONSTANTS ON BOTH SIDES OF AN OPERATOR Cause. The expression passed to the BOOLEXPR built-in function was not syntactically correct. Constants were given on both sides of an operator. One side of an operator must consist entirely of variables. Effect. The value INVALID is returned from BOOLEXPR. Recovery. Correct the Boolean expression. NNM1973 STRICT OPERATORS CANNOT HAVE NUMERIC OPERANDS Cause.
Messages NNM1978 NNM1976 INVALID NUMBER IN BOOLEXPR EXPRESSION: lexical_element Cause. The expression passed to the BOOLEXPR built-in function was not syntactically correct. It contained an invalid number, for example, no digits after a + or -, or no digits after an E (for exponent). lexical_element is the invalid number. Effect. The value INVALID is returned from BOOLEXPR. Recovery. Correct the Boolean expression. NNM1977 INVALID QUOTED STRING IN BOOLEXPR EXPRESSION: lexical_element Cause.
Messages NNM1979 NNM1979 VARIABLE: vblname HAS INVALID TYPE NAME: type_name Cause. The expression passed to the BOOLEXPR built-in function contained a variable that contained an invalid data type name. The variable was used as the right operand of the IS or IS NOT operator. vblname is the name of the variable in error. type_name is the invalid data type name. Effect. The value BAD is returned from BOOLEXPR. Recovery. Correct either the expression passed to BOOLEXPR or the contents of the variable.
Messages NNM2005 NNM2002 error_type DATA* AND VARIABLE PREFIX IN DIFFERENT LIST POSITIONS Cause. The VARTABLE verb specified FIELDS and VARS lists. However, the DATA* entry in the FIELDS list was not at the same position as the corresponding variable (a variable ending in *) in the VARS list. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery.
Messages NNM2006 NNM2006 error_type MISSING PARAMETER FOR %%OPTIONS Cause. The %%OPTIONS compiler directive did not specify the option. The option is either DEFER or NODEFER. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Correct the %%OPTIONS compiler directive. NNM2007 error_type BLANK REQUIRED BETWEEN DEFINE TOKEN AND DEFINITION Cause. The %%DEFINE compiler directive did not have a space between the symbol and the text.
Messages NNM2013 NNM2010 error_type INVALID %%OPTIONS PARAMETER Cause. The %%OPTIONS compiler directive specified an invalid option. The valid options are DEFER and NODEFER. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Specify the correct option. NNM2011 error_type SYMBOL definesym ALREADY DEFINED Cause. The %%DEFINE compiler directive specified a symbol that was already defined. error_type is FATAL ERROR:. definesym is the symbol. Effect.
Messages NNM2014 NNM2014 error_type SYMBOL definesym NOT DEFINED Cause. The %%UNDEFINE compiler directive specified a symbol that was not defined. error_type is WARNING:. definesym is the symbol specified. Effect. Compilation continues. Recovery. Specify the correct symbol or remove the directive. NNM2015 error_type MISSING INCLUDE FILE FOR %%INCLUDE Cause. The %%INCLUDE compiler directive did not specify a file name. error_type is FATAL ERROR:. Effect.
Messages NNM2021 NNM2018 error_type OPEN STRING AT EOF Cause. NCL reached the end of the file but a string was still open. The closing quotation mark was missing or did not match the opening quotation mark. error_type is FATAL ERROR:. Effect. Compilation stops, and no executable code is produced. Recovery. Ensure that the last opening quotation mark has a matching closing quotation mark. NNM2019 error_type OPEN COMMENT IN %% COMPILER DIRECTIVE Cause.
Messages NNM2022 NNM2022 error_type LINE CONTINUATION OVER EOF Cause. NCL reached the end of the file but the last line ended with the line continuation character, a comma. error_type is ERROR: or FATAL ERROR:.. Effect. If this is an error, compilation continues but no executable code is produced. If this is a fatal error, compilation stops and no executable code is produced. Recovery. Correct the last line. NNM2023 error_type STATEMENTS AFTER END OF OPEN CODE IGNORED Cause.
Messages NNM2029 NNM2026 error_type expect EXPECTED Cause. NCL expected to find an item but did not find it. error_type is ERROR: or FATAL ERROR:. expect denotes the item (for example, CLOSING PARENTHESIS, END, or SHARE OR NOSHARE). Effect. If this is an error, compilation continues but no executable code is produced. If this is a fatal error, compilation stops and no executable code is produced. Recovery. Correct the error. NNM2027 error_type INVALID MATCH CONDITION Cause.
Messages NNM2030 NNM2030 error_type SHARELIST FOR CALL PROC ONLY Cause. The CALL statement specified a share list but was not CALL PROC. Note CALL PGM and CALL SUBSYS are not supported forms of CALL in the NonStop NET/MASTER MS system. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Correct the NCL procedure and retry. NNM2031 error_type NON EMPTY EXPRESSION REQUIRED Cause. The statement required an expression but could find none.
Messages NNM2037 NNM2034 error_type INVALID LABEL Cause. The label was invalid. A label consists of a name followed by :. The name can be one of the following: String containing alphanumeric characters, @, #, $, and _ Quoted string error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Specify a correct label. NNM2035 error_type LOCAL SIMPLE VARIABLE EXPECTED AS CONTROL VARIABLE Cause. The DO statement specified an invalid control variable.
Messages NNM2038 NNM2038 error_type LABEL REQUIRED FOR type Cause. The FUNCTION or PROCEDURE statement did not have a label. error_type is ERROR:. type is FUNCTION or PROCEDURE. Effect. Compilation continues, but no executable code is produced. Recovery. Add a label to the statement. NNM2039 error_type type MUST BE AT OPEN CODE LEVEL Cause. The FUNCTION or PROCEDURE statement was illegal. For example, the statement may be in a DO loop. error_type is ERROR:. type is FUNCTION or PROCEDURE. Effect.
Messages NNM2045 NNM2042 error_type tok NOT CONSTANT Cause. NCL expected an item that is constant but the item found was not constant. error_type is ERROR:. tok is LIMIT LABEL (used in GOSUB and GOTO), SIGNAL LABEL (used in SIGNAL), or VARIABLE NAME. Effect. Compilation continues, but no executable code is produced. Recovery. Make the item a constant. NNM2043 error_type INVALID KEYWORD Cause. A keyword was illegal in the current statement, or illegal in the current position within a statement.
Messages NNM2046 NNM2046 error_type NO WHEN STATEMENTS Cause. No WHEN statements were present in a SELECT. There must be at least one. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Add a WHEN statement. NNM2047 error_type STATEMENT NOT WITHIN OTHERWISE OR WHEN Cause. A statement has been found in a SELECT that is not the target of a WHEN or OTHERWISE. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery.
Messages NNM2053 NNM2050 error_type UNEXPECTED CHARACTERS BEFORE END OF STATEMENT Cause. Extra characters were encountered where the end of the current statement was expected. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Remove the extra characters. NNM2051 error_type MISMATCHED END LABEL Cause. A label was supplied on an END statement for checking purposes, but it did not match a label on the statement construct being ended. error_type is ERROR:.
Messages NNM2054 NNM2054 error_type MISSING RHS VALUE Cause. The operator in an expression expected a term on the right but there was none. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Add the term in the expression. NNM2055 error_type LABEL label CONFLICTS WITH THE PREVIOUS SAME LEVEL PROC OR FUNC LABEL Cause. The label was the same as the label of the parent PROCEDURE or FUNCTION statement. error_type is ERROR:.
Messages NNM2061 NNM2058 error_type ILLEGAL CHARACTER Cause. An illegal character was found. error_type is ERROR:. Effect. The illegal character is replaced by a blank. Compilation continues, and no executable code is produced. Recovery. Remove the illegal character or replace it by a blank. NNM2059 error_type CANNOT OPEN FILE filename. ERROR errno Cause. NCL could not open the file. error_type is FATAL ERROR:. filename is the name of the file to be opened.
Messages NNM2062 NNM2062 error_type filename lineno NOT INSIDE AN ITERATIVE DO Cause. An ITERATE or LEAVE statement was not included in an iterative DO statement. error_type is ERROR:. filename is the name of the file containing the error. lineno is the line number where the error occurred. Effect. Compilation continues, but no executable code is produced. Recovery. Ensure that the ITERATE or LEAVE statement is included in an iterative DO statement. NNM2063 error_type UNKNOWN VERB verb Cause.
Messages NNM2069 NNM2066 error_type ILLEGAL TOKEN Cause. The value for an operand was invalid. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Specify a correct value for the operand. NNM2067 error_type LOW BOUND EXCEEDS HIGH BOUND Cause. The specification of a ranged variable reference had a high value which was less than the low value. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery.
Messages NNM2070 NNM2070 error_type NO TOKENS IN BRACKETED EXPRESSION Cause. NCL found a pair of parentheses with no expression in between: that is, (). error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. If a variable represents the expression, ensure that you initialize the variable to the correct value. NNM2071 error_type kwd1 EXCLUSION ERROR WITH kwd2 Cause. The verb specified mutually exclusive operands.
Messages NNM2076 NNM2074 error_type MISSING ASTERISK FOR GENERIC VARIABLE Cause. You specified the GENERIC keyword but specified an invalid value for the VARS= operand. With the GENERIC keyword, NCL expects a variable reference ending in *. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Append an asterisk to the variable reference. NNM2075 error_type filename lineno type VALUE REQUIRED FOR PARAMETER paramnum OF builtin Cause.
Messages NNM2077 NNM2077 error_type filename lineno LIMIT LABEL label NOT FOUND OR IN BAD SCOPE Cause. The GOSUB or GOTO statement specified a label for the LIMIT operand, but NCL could not find the label. error_type is FATAL ERROR:. filename is the name of the file containing the error. lineno is the line number where the error occurred. label is the label as specified for the LIMIT operand. Effect. Compilation stops, and no executable code is produced. Recovery.
Messages NNM2082 NNM2080 error_type filename lineno LABEL label NOT FOUND Cause. NCL could not find the label specified in the GOSUB, GOTO, or SIGNAL LABEL statement. error_type is ERROR:. filename is the name of the file containing the error. lineno is the line number where the error occurred. label is the name of the label. Effect. Compilation continues, but no executable code is produced. Recovery.
Messages NNM2083 NNM2083 error_type filename lineno ON HAS NO EFFECT Cause. The ON statement was ineffective at the current position. error_type is WARNING:. filename is the name of the file containing the error. lineno is the line number where the error occurred. Effect. Compilation continues. Recovery. Move the ON statement to a position where the statement is effective. NNM2084 error_type SYSTEM VARIABLE sysv READONLY Cause.
Messages NNM2088 NNM2086 error_type filename lineno VALUE ERROR FOR PARAMETER paramnum OF builtin Cause. The value of the parameter was invalid. error_type is ERROR:. filename is the name of the file containing the error. lineno is the line number where the error occurred. paramnum is the parameter position. builtin is the name of the built-in function. Effect. Compilation continues, but no executable code is produced. Recovery. Correct the line.
Messages NNM2089 NNM2089 error_type filename lineno VALUE OUT OF RANGE Cause. The line contained a value that was out of range. error_type is ERROR:. filename is the name of the file containing the error. lineno is the line number where the error occurred. Effect. Compilation continues, but no executable code is produced. Recovery. Specify a correct value. NNM2090 error_type PROCEDURE: filename LINE: lineno INVALID COMPLEX VARIABLE vblref Cause. The complex variable reference was invalid.
Messages NNM2095 NNM2092 error_type ENTRY MISMATCH IN SOURCE AND TARGET VARIABLE LISTS Cause. The ASSIGN verb specified the BYNAME, GENERIC, MERGE, or OVERLAY keyword, and the target VARS= operand contained a variable reference ending in *. However, the source VARS= operand did not contain a similar reference. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Specify a variable reference ending in * for the source VARS= operand.
Messages NNM2096 NNM2096 error_type SPECIFIED ASSIGN OPTION DOES NOT REQUIRE SOURCE DATA. Cause. The ASSIGN verb specified an option to update the attributes of variables that did not require source data, but source data was supplied. error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Remove the source data specification. NNM2097 error_type filename lineno PARAMETER paramnum OMITTED TO BUILTIN builtin Cause. The mandatory parameter did not have a value.
Messages NNM2102 NNM2099 error_type TOO MANY ARGUMENTS Cause. The function or procedure specified too many parameters (arguments). error_type is ERROR:. Effect. Compilation continues, but no executable code is produced. Recovery. Reduce the number of parameters. NNM2100 USERID SHOULD ONLY HAVE A MAX OF 8 CHARS Cause. A LOCATE command was entered but a user ID that was more than eight characters long was specified. Effect. The operation is not performed. Recovery.
Messages NNM2103 NNM2103 GROUP ID groupid DOES NOT EXIST Cause. A group user ID was assigned to a user but the group user ID did not exist. groupid is the ID specified as the group user ID. Effect. You are prompted to specify another value. Recovery. Specify an existing group user ID. NNM2104 INVALID VALUE FOR fieldname Cause. An invalid value was entered in the field. fieldname identifies the field that raised the error. Effect. You are prompted to specify another value. Recovery.
Messages NNM2109 NNM2107 NEW PASSWORD VERIFICATION COMPLETE Cause. You were changing your password and entered your new password a second time for verification. The verification was successful. Effect. Your password has been changed. Recovery. This message is for information only; no recovery is necessary. If you are not satisfied with your password, you can use the following keys: F3 to change your password, or F12 to cancel the change. NNM2108 MISSING MDO VALUE FOR SECCALL VERB Cause.
Messages NNM2110 NNM2110 GROUP DEF groupid RECURSIVE; USER PROFILE RESET Cause. The definition of the group to which the user belonged was recursive, or extended beyond ten levels of group definition. groupid is the group user ID for which the recursion was detected. Effect. The profile is reset to the level before this group ID. Recovery. Refer the message to the system manager, who must redefine the group ID references. If the problem is due to recursion, remove the recursive reference.
Messages NNM2154 NNM2151 UTILITY IS NOT DEFINED Cause. An attempt was made to browse, copy, update, delete, or run a utility definition that was not there. Effect. The request is not performed. Recovery. If the name or type was entered incorrectly, correct it and try again. If the name and type were entered correctly, and you were deleting, the utility definition is already deleted. NNM2152 UTILITY NAME AND TYPE ARE REQUIRED FOR THAT OPTION Cause.
Messages NNM2155 NNM2155 UNEXPECTED PANEL RETCODE: retcode Cause. The PANEL verb returned a status code that the program was not expecting. retcode is the return code contained in &SYS.RETCODE. Valid return codes have the values 0, 4, 8, 12, or 16. Effect. The panel display that was attempted is abandoned, and the program returns to the previous panel, on which this error message is displayed. Recovery. This message indicates a programming error; consult a programmer.
Messages NNM2162 NNM2159 FILE OPEN ERROR: rc/fileid Cause. The FILE OPEN verb was not successful. rc is the value of &SYS.FILE.RC. fileid is the UDB ID of the file. (In the case of a problem from PROGRUN starting NetStatus, the ID is a temporary one that exists only while the PROGRUN code is running.) Effect. The file is not opened. Recovery. Use the error code to determine the appropriate action to take. NNM2160 INVALID FILENAME Cause. The file name entered is not a valid Guardian file name.
Messages NNM2163 NNM2163 ONLY ALLOWED FOR PROGRUN UTILITY Cause. The utility type was given as O but some entries were made in the PROGRUN portion of the Utility Details panel. Effect. The definition is not added or updated. Recovery. Erase the entries in the PROGRUN portion of the panel, or correct the utility type if it is incorrect. NNM2164 PROMPT PATTERN NOT ALLOWED WITH OTHER PROMPT SPECIFICATION Cause.
Messages NNM2170 NNM2167 COMMAND SET IS NOT DEFINED Cause. An attempt was made to browse, copy, update, delete, or run a command set definition that was not there. Effect. The request is not performed. Recovery. If the name or type was entered incorrectly, correct it and try again. If the name and type were entered correctly, and you were deleting, the definition is already deleted. NNM2168 'SAME AS' COMMAND SET IS NOT DEFINED Cause.
Messages NNM2171 NNM2171 COMMAND ENTERED WITH NO AUTHORITY Cause. A command name was entered without a corresponding authority level. Effect. The definition is not added or updated. Recovery. Either erase the command name or add the authority level and try again. NNM2172 AUTHORITY ENTERED WITH NO COMMAND Cause. An authority level was entered without a corresponding command name. Effect. The definition is not added or updated. Recovery.
Messages NNM2178 NNM2175 SECURITY EXIT ERROR message-id PREVENTED COMMAND AUTHORITY CHECK Cause. The security exit returned message-id when the OPSYS or PROGRUN NCL procedure tried to check the user's authority to run the command. message-id is the ID of the message that provides further information about the error. Effect. The OPSYS or PROGRUN command is not executed. Recovery. Refer to the message identified by message-id to determine the action to take.
Messages NNM2179 NNM2179 UTILITY DEFINITION name type ADDED Cause. An Add or Copy operation was completed successfully. The utility name and type appear in the message. Effect. The utility definition is added. Recovery. This message is informational only; no recovery action is necessary. NNM2180 UTILITY DEFINITION name type UPDATED Cause. An Update operation was completed successfully. The utility name and type appear in the message. Effect. The utility definition is updated. Recovery.
Messages NNM2186 NNM2183 COMMAND SET name type ADDED Cause. An Add or Copy operation was completed successfully. The utility name and type appear in the message. name is the name of the utility for which the command set is added. type is the utility type: O (OPSYS) or P (PROGRUN). Effect. The command set is added. Recovery. This message is informational only; no recovery action is necessary. NNM2184 COMMAND SET name type UPDATED Cause. An Update operation was completed successfully.
Messages NNM2187 NNM2187 UNABLE TO CREATE NCL FOR THE UTILITY: errtext Cause. A utility definition or command set definition was added for an OPSYS type utility, and the database update was performed successfully, but a problem prevented creation of the NCL procedure to allow system-wide command replacement.
Messages NNM2189 NNM2188 BAD BACKUP CPU NUMBER IN STARTUP MSG: 'text' Cause. The first symbol in the parameter string portion of the startup message to the security exit was not acceptable as a backup CPU number. Either the symbol was not all digits, was a number less than 0 or greater than 15, or was the same number as the primary CPU number. text is the string of characters interpreted as the backup CPU number. This is defined in your NonStop NET/MASTER MS configuration file. Effect.
Messages NNM2190 NNM2190 OPEN ERROR errno ON FILE filename Cause. A file management error occurred when opening a file in the security exit server. errno is the Guardian file-system error number. filename is the name of the file on which the error occurred. Effect. The security exit abends, preventing the NonStop NET/MASTER MS system from starting up. Recovery. Use the error number to determine the appropriate action to take. NNM2191 proc ERROR errno ON FILE filename (name type) Cause.
Messages NNM2193 NNM2192 CHECKPOINT ERROR err1,err2 Cause. An error occurred on a CHECKPOINT procedure call in the security exit server. err1 is the value of bits 0 through 7 of the CHECKPOINT error code and has the value 3 indicating an illegal parameter. err2 is the value of bits 8 through 15 of the CHECKPOINT error code identifying the parameter in error. This message is only generated when err1 is 3. It represents a coding error in the security exit. Effect. The security exit abends.
Messages NNM2194 NNM2194 BACKUP TAKEOVER, reason Cause. The backup of the security exit server has taken over. reason is one of the following: PRIMARY ABENDED indicates that the security exit abended. PRIMARY CPU FAILED indicates that the CPU running the security exit failed. PRIMARY STOPPED indicates that the security exit stopped. Effect. Authorization functions are unaffected, but no backup is created if the CPU running the security exit fails.
Messages NNM2198 NNM2197 BAD DATABASE RECORD: errtext (name type filename) Cause. There is a problem with one of the records in the Utility Access database. errtext describes the error and is one of the following: INVALID COMMAND AUTHORITY: "text" INVALID STARTUP PARAMETER STRING LENGTH: "text" MDO FORMAT name is the name of the utility connected with the record in error. type is the utility type: O (OPSYS) or P (PROGRUN). filename is the name of the file containing the record in error.
Messages NNM2199 NNM2199 BAD SECURITY EXIT REQUEST errtext Cause. An invalid request was sent to the security exit server. errtext indicates the problem and is one of the following: BAD BAD BAD BAD BAD COMMAND AUTHORITY NUMBER: "text" FILENAME IN FILE OPEN REQUEST: "text" MDO REQUEST TYPE: "text" USERID: "text" This could be due to an error in the OPSYS or PROGRUN NCL procedure making it construct the request incorrectly or it could be an error elsewhere. Effect.
Messages NNM2204 NNM2201 MSGPROC NOT ACTIVE, FLUSH REQUEST REJECTED Cause. The cause is one of the following: 1. A PROFILE MSGPROC=FLUSH command was issued, but the attempt to flush MSGPROC failed because no MSGPROC was running. 2. A PROFILE MSGPROC=procname command was issued, but the specified NCL procedure did not exist. Effect. The request is rejected. Recovery. For cause 1, this message is informational only and no recovery action is necessary.
Messages NNM2205 NNM2205 command COMMAND CAN BE EXECUTED FROM OCS COMMAND LINE ONLY Cause. A command was issued but the attempt to execute the command failed. The command must be entered from the OCS command line. command is the name of the command that failed. Effect. The command is rejected. Recovery. Enter the command from an OCS command line. NNM2206 command COMMAND IS NOT VALID FOR ENTRY FROM THIS SOURCE Cause.
Messages NNM2301 NNM2209 OCS MESSAGES LOST Cause. Messages were inserted into the OCS message flow when the size of the internal OCS waiting queue was exhausted. This may happen if OCS scrolling is disabled for a long time, either because of HOLD or AUTOHOLD, or because a panel has taken over OCS. When the queue becomes full, the earliest messages are lost. The size of the OCS internal queue is set by the HELDMSG system parameter and the PROFILE HOLD command.
Messages NNM2302 NNM2302 THE TARGET ENVIRONMENT BELONGS TO ANOTHER USER Cause. A DEBUG START command was issued, and an environment belonging to another user was specified. However, the debug session was not started because you did not have sufficient authority or because the value of the NCLXUSER system parameter was NO. Effect. The debug session is not started. Recovery. Refer the message to your system manager.
Messages NNM2307 NNM2305 NO ENVIRONMENTAL DEBUGGING POSSIBLE FOR ROC LOGON Cause. A DEBUG START USER=... was issued and an attempt was made to start a debug session on a ROC session. A ROC session cannot be debugged on an environmental basis. Effect. The debug session is not started. Recovery. Use the SHOW NCL command to determine the IDs of the NCL processes that you want to debug, then use the DEBUG START ID=nclid command to start the debug session. NNM2306 NCL nclid DEBUG STOP NOT EXECUTED.
Messages NNM2308 NNM2308 NCL nclid VBL variable-name WAS NOT UPDATED. HEXADECIMAL VALUE REQUIRED. Cause. A DEBUG MODIFY command was issued with FORMAT=BINARY, but the value specified for the VAL operand was not hexadecimal. nclid is the ID of the NCL process being debugged. variable-name is the name of the variable to be modified. Effect. The value of the variable is not modified. Recovery. Correct the VAL operand to contain only 0 through 9 and A through F.
Messages NNM2357 NNM2353 MUST BE NUMERIC Cause. An entry in the field indicated must be a number. Effect. The information cannot be updated or added. Recovery. Supply a proper numeric value. NNM2354 VALUE TOO SMALL Cause. An entry in the field indicated must be larger than the entry supplied. Effect. The information cannot be updated or added. Recovery. Supply a value in the proper range for the field. NNM2355 VALUE TOO LARGE Cause.
Messages NNM2358 NNM2358 ONLY '*' ALLOWED FOR PROGRUN UTILITY Cause. For a PROGRUN utility, the command set definition may contain only an * entry for the Command field. Checks of the user's authority for individual commands cannot be done for PROGRUN utilities. The only check that may be done is to determine whether the user may run the utility at all. Effect. The definition cannot be updated or added. Recovery. If the utility is a PROGRUN utility, specify * in the Command field.
Messages NNM2364 NNM2361 TOO MANY COMMANDS IN THE COMMAND SET Cause. A command set definition had more than 140 commands. Effect. The definition cannot be updated or added. Recovery. Reduce the number of commands specified. NNM2362 UTILITY TYPE INCOMPATIBLE WITH VALUES ON THE OTHER PANEL Cause. You changed the utility type on one of the Utility Details panels, but there were already entries on the other panel that are not permitted for the new type.
Messages NNM2365 NNM2365 INVALID SUBVOLUME NAME Cause. The subvolume entered was not valid. It must be $volume.subvolume or \system.$volume.subvolume. Effect. The definition cannot be updated or added. Recovery. The name is most likely mistyped; correct the spelling and try again. If the name is as you intended, check your source to find the correct name. NNM2366 INVALID SWAP VOLUME NAME Cause. The volume name entered for the swap volume was not valid. Effect. The definition cannot be updated or added.
Messages NNM2371 NNM2369 CASE xxx NOT RECOGNIZED IN filename (id) Cause. The OTHERWISE case of a SELECT statement was taken when all the cases were supposedly listed. This is an internal error in the NCL code. xxx is the value that was not recognized. filename is the name of the NCL file in which the error was found. id is a number to distinguish between multiple instances of this error in the same NCL file. Effect. The function is not performed. Recovery.
Messages NNM2372 NNM2372 NETSTATUS MUST BE RUN FROM NETSTAT Cause. The NetStatus utility requires further communication after the PROGRUN command is issued. The extra communication requirements are met in the NETSTAT NCL routine, which should be used to invoke the NetStatus utility. Effect. The NetStatus utility is not invoked. Recovery. Use the command NETSTAT (or START NETSTAT) rather than PROGRUN NETSTATUS. NNM2373 'SAME AS' CANNOT REFER TO ITS OWN COMMAND SET Cause.
Messages NNM2454 NNM2451 UTILITY IS NOT DEFINED FOR PROGRUN Cause. You were maintaining a Console Extras configuration and specified a utility that was not defined for the PROGRUN command. Effect. The request is not performed. Recovery. Define the utility for the PROGRUN command using the UMS utility definition maintenance panels and its command set using the UMS command set definition maintenance panels. NNM2452 UTILITY NAME IS REQUIRED FOR THAT OPTION Cause.
Messages NNM2455 NNM2455 CONSOLE EXTRAS filename utility_name DELETED Cause. A Delete operation was completed successfully. filename is the name of the Console Extras configuration file from which the utility is deleted. utility_name is the name of the deleted utility. Effect. The utility in the Console Extras configuration file shown in the message is deleted, and the message is written to the activity log. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM2501 NNM2459 THE UTILITY CONFIGURATION HAS BEEN DELETED SINCE YOU READ IT Cause. Another user deleted the record that you were in the process of updating or deleting. Effect. The updating or deleting attempt fails. Recovery. If you were updating the record and need the record, use the Add option to recreate the record. If you were in the process of deleting the record, the record is already deleted. This message is informational only; no recovery action is necessary.
Messages NNM2550 NNM2550 procname SENT EVENT: event-time event-text Cause. The event was successfully sent back to the designated collector with the special token ZNNM_TKN_DUPLICATE_EVENT set. is the name of the DSM/PM Interface NCL procedure. procname event-time is the time of event generation in the format hh:mm:ss. event-text contains the event message that is the content of the &$xxx.TEXT message profile variable. Effect.
Messages NNM2554 NNM2552 procname INPUT MDO IS MISSING Cause. The DSM/PM Interface NCL procedure procname was invoked without passing in any parameters. This indicates a programming error. Effect. The event is not sent to the designated collector. The error message is returned in &SYSMSG. Recovery. Refer the message to your system programmer. The programmer should correct the NCL procedure that calls procname.
Messages NNM2555 NNM2555 procname ERROR IN PARAMETER: parameter-position Cause. The NCL procedure received a passed parameter that was invalid. procname is the name of the DSM/PM Interface NCL procedure. parameter-position identifies the invalid parameter as follows: 2 indicates the second parameter that must be either DOMAIN or LINK. 3 indicates the third parameter that must be a domain ID or a link name, and is mandatory if the second parameter is specified. This indicates a programming error.
Messages NNM2560 NNM2558 ISR LINK WAS NOT ENABLED FOR OUTBOUND EMS TRAFFIC Cause. You specified an INMC link that was not enabled for outbound EMS event messages when you pressed the DSM/PM Interface action function key to send an EMS event to DSM/PM. Effect. No DSM/PM record is added. Recovery. Use the SHOW ISR command to get the ISR configuration of your link.
Messages NNM2561 NNM2561 EMS COLLECTOR NOT STARTED, INSUFFICIENT TOKENS OR GUARDIAN SPI ERROR Cause. You pressed the DSM/PM Interface action function key to send an EMS event to DSM/PM, but one of the following reasons prevented the event from being sent: 1. The EMS collector was not started. 2. The message MDO passed did not contain the minimum number of required SPI tokens. This should only occur for user-generated events that were raised by the EMSALERT verb. 3.
Messages NNM2563 NNM2563 UNEXPECTED RETURN CODE return-code RETURNED FROM DSM/PM INTERFACE Cause. You pressed the DSM/PM Interface action function key to send an EMS event to DSM/PM, but the DSM/PM Interface returned an unexpected return code and the event was not sent. The DSM/PM Interface NCL procedure ZPMIEVUN on your system was customized. return-code is a value other than 0, 8, 12, 16, 20, 28, or 32. Effect. No DSM/PM record is added. Recovery. Refer the message to your system programmer.
Messages NNM2564 NNM2564 DSM/PM ERROR: error-text Cause. An error occurred when you pressed the DSM/PM Interface action function key to send an event to DSM/PM. error-text gives the reason of the error as follows: NO MDO WAS PASSED Your cursor was on a message that did not contain an MDO. The message is not an EMS event message. NO SPI TOKENS WERE FOUND IN THE MDO Your cursor was on a message that did not contain any SPI tokens. The message is not an EMS event message.
Messages NNM2602 NNM2601 parameter-1 parameter-2 Cause. A SHOW SESS or SHOW TERM command with the DETAIL=YES or DETAIL=OPEN operand was issued, and the message is part of the response. The line contains information about the host configuration parameters for the terminal in two columns. parameter-1 contains the name and value of a host configuration parameter. parameter-2 contains the name and value of a host configuration parameter or blank. Effect. The information is retrieved and displayed.
Messages NNM2603 NNM2603 fware-val1 fware-val2 Cause. A SHOW SESS or SHOW TERM command with the DETAIL=YES or DETAIL=OPEN operand was issued and the message is part of the response. The line contains the firmware information about the terminal in two columns. fware-val1 contains a piece of firmware information. fware-val2 contains a piece of firmware information or blank. Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary.
Messages NNM2608 NNM2606 TERMINAL CONFIGURATION PARAMETERS Cause. A SHOW SESS or SHOW TERM command with the DETAIL=YES or DETAIL=OPEN operand was issued, and the message is part of the response. The line contains the heading for the configuration parameters for the terminal. Effect. The heading is displayed. Recovery. This message is informational only; no recovery action is necessary. NNM2607 config-val1 config-val2 Cause.
Messages NNM2609 NNM2609 TERM RECLEN : record-length TYPE/SUBTYPE : device-type/device-subtype Cause. A SHOW SESS or SHOW TERM command with the DETAIL=YES or DETAIL=OPEN operand was issued, and the message is part of the response. The line contains the device information about the terminal. record-length is the configured record length of the terminal. device-type is the device type of the terminal. device-subtype is the device subtype of the terminal. Effect.
Messages NNM2650 NNM2611 DETAIL NOT AVAILABLE FOR TERMINAL termname, ERROR: errno Cause. A SHOW SESS or SHOW TERM command with the DETAIL=YES or DETAIL=OPEN operand was issued, but NonStop NET/MASTER MS failed to either open the terminal (if it is not currently defined to NonStop NET/MASTER MS and opened) or to gather the detailed terminal data. termname is the name of the terminal you specified in your SHOW command. errno is a Guardian file-system error number, indicating the reason for the failure.
Messages NNM2651 NNM2651 AUTOMATIC REFRESH, PLEASE WAIT Cause. A selection list is automatically refreshing its data. This occurred because you used the REFRESH ON or the REFRESH seconds command on the selection list panel. Effect. The data on the selection list panel is being refreshed, and no other operation on the list is allowed. Recovery. Wait for the message to disappear (which indicates the completion of the refreshing operation) before continuing. NNM2700 NO FILES MATCH file-mask Cause.
Messages NNM2704 NNM2703 record-type record-name NOT FOUND IN OBJECT FILE object-name Cause. An NCLCOMP command was issued, using the DELETE operand to delete an NCL procedure record from an NCL object file or to delete panel records from a panel object file. The specified NCL procedure or panel records were not in the object file. record-type is either PROCEDURE or PANEL, indicating the type of record to be deleted. record-name is the name of the record to be deleted.
Messages NNM2705 NNM2705 OBJECT OPERAND CANNOT BE A FILE SPECIFIED IN PARAM parameter-name Cause. An NCLCOMP command was issued, using one of the files specified in the NCLDISTCODE or PNLDISTCODE startup parameter as the object file. You cannot use the NCLCOMP command on files specified in those startup parameters. parameter-name is NCLDISTCODE or PNLDISTCODE. Effect. The command is not executed. Recovery.
Messages NNM2752 NNM2750 PANEL FILE panel-name NOT PRELOADED - RECURSIVE INCLUDE OF PANEL included-panel Cause. A SYSPARMS PPRELOAD command was issued, but a #INCLUDE statement caused the recursive inclusion of a panel description file. panel-name is the name of the file specified in the command. included-panel is the name of the file recursively included. Effect. The panel description file is not preloaded. Recovery.
Messages NNM2753 NNM2753 INVALID VARS LIST SPECIFIED IN #ALIAS STATEMENT Cause. A PANEL verb was issued, but a #ALIAS statement in the panel description file specified an invalid variable list. The list must be a single variable name, or a list of variable names separated by commas and surrounded by parentheses: for example, VARS=variable-name or VARS=(variable-name-1,variable-name-2). Effect. The panel is not displayed. Recovery. Correct the variable list, and retry the request.
Messages NNM2759 NNM2757 NULL ENTRIES SPECIFIED IN VARS LIST IN #ALIAS STATEMENT Cause. A PANEL verb was issued, but a #ALIAS statement in the panel description file specified an invalid variable list, containing null entries. (A null entry exists when a comma is immediately followed by another comma.) Effect. The panel is not displayed. Recovery. If you used variables to hold the entries in the list, ensure that none of the variables resolve to a null value.
Messages NNM2760 NNM2760 NCLCOMP COMMAND OF PANEL panel-name FROM LIBRARY library-name FAILED. ERROR error-number Cause. An NCLCOMP command on the panel file failed because of a file-system error. panel-name is the name of the panel file that caused the error. library-name is the name of the library that contains the panel file. error-number is the Guardian file-system error number. Effect. The operation on the panel file is not performed. Recovery.
Messages NNM2803 NNM2802 process-name eyecatcher count mem-used mem-pooled overhead Cause. A SHOW MEMORY command was issued, and the message is part of the response. The line contains information about memory use that may be useful to Tandem support representatives. process-name is the name of the process. eyecatcher is the identifier of the memory block. count is the number of allocated blocks for eyecatcher. mem-used is the amount of memory used by blocks for eyecatcher.
Messages NNM2804 NNM2804 process-name pool base-count base-size base-use% oflow-count oflow-size oflow-use% Cause. A SHOW MEMORY command was issued, and the message is part of the response. The line contains information about memory use that may be useful to Tandem support representatives. process-name is the name of the process. pool is the identifier of the pool. base-count is the number of base pools of this type. base-size is the total size of the base pools of this type.
Messages NNM2850 NNM2806 process-name q-number current-msgs/max-msgs 0xreader-thrd 0xcreator-thrd Cause. A SHOW QUEUES command was issued, and the message is part of the response. The line contains information about queue usage that may be useful to Tandem support representatives. process-name is the name of the process. q-number is the identifier of the queue. current-msgs is the number of messages currently queued. max-msgs is the maximum number of messages queued.
Messages NNM2851 NNM2851 COULD NOT OPEN FILE file-name, ERROR=file-system-error Cause. A command help maintenance operation failed to open the required file. file-name is the name of the file. file-system-error is a Guardian file-system error number. Effect. The operation is not performed. Recovery. Use the error number to determine the appropriate action to take. NNM2852 ERROR WHILE PROCESSING file-type file-name, ERROR=file-system-error Cause.
Messages NNM2855 NNM2853 HELP INFO ON command-name transfer-typeED FROM source TO destination Cause. A command help transfer operation was successful. command-name identifies the command. transfer-type is either EXPORT or IMPORT. source is where the information comes from. The value is either DATABASE or the name of an edit file. destination is where the information goes. The value is either DATABASE or the name of an edit file. Effect. The command help information is transferred. Recovery.
Messages NNM2856 NNM2856 UNABLE TO CREATE TEMPORARY FILE file-name ERROR=file-system-error Cause. To export command help, the operation writes the help information to a temporary file first and then converts the temporary file into an edit file. The command help export operation could not create a temporary file. file-name is the name of the temporary file. file-system-error is a Guardian file-system error number. Effect. The operation fails. Recovery.
Messages NNM2861 NNM2859 INCOMPATIBLE DATABASE file-name Cause. A command help maintenance operation failed because the customized command help file had the wrong attributes in terms of the file type, record length, key length, and key offset. Effect. The operation is not performed. Recovery. The attributes of the customized and the distributed command help files must be identical. You can create a customized command help file as follows: NNM2860 1.
Messages NNM2862 NNM2862 file-name IS NOT AN EDIT FILE Cause. A command help maintenance operation tried to export help to or import help from a file that was not an edit file. file-name is the name of the file. Effect. The operation is not performed. Recovery. Ensure that you use the correct name for the edit file. For an export operation, you can use the name of a nonexistent file. Reissue the command. NNM2863 NO SUCH RECORD IN DATABASE Cause.
Messages NNM2869 NNM2866 COMMAND MUST BE SPECIFIED Cause. You selected a command help maintenance operation that required a value in the Command field, but you did not specify that value. Effect. The operation is not performed. Recovery. Specify a value in the Command field, then retry the operation. NNM2867 FILE MUST BE SPECIFIED Cause. You selected the command help export or import operation without specifying a value in the File field. Effect. The operation is not performed. Recovery.
Messages NNM2870 NNM2870 FILE ALREADY EXISTS Cause. You tried to export command help information to an existing edit file from the Help Maintenance : Commands panel. Effect. The operation is not performed. Recovery. You cannot export help to an existing edit file from the Help Maintenance : Commands panel. Either purge or rename the existing file, or use the name of a nonexistent file, and retry the operation. If you want to export help to an existing edit file, use the HLPMAINT command.
Messages NNM2877 NNM2874 FILE ERROR error-text ON file-id Cause. You selected a command help browse, delete, or list operation. The operation failed because of an error encountered during a file operation on the command help database. is the ID of the command help database. file-id error-text identifies the encountered error. The value can be an error message or a Guardian file-system error number. Effect. The operation fails. Recovery.
Messages NNM2900 NNM2900 VALUE SPECIFIED FOR LINK OPERAND WAS TOO LONG - link-name Cause. An OPSC command was issued, but the value specified for the LINK operand was longer than 12 characters. The command was DEFLINK, REPLINK, DELLINK, DEFTRANS, or REPTRANS. is the value specified for the LINK operand. This operand specifies the OPSC link name. link-name Effect. The command is rejected. Recovery. Replace the value with a shorter OPSC link name, and retry the command.
Messages NNM2904 NNM2903 VALUE SPECIFIED FOR QUAL OPERAND WAS TOO LONG transaction-qualifier Cause. An OPSC command was issued, but the value specified for the QUAL operand was longer than four characters. The command was DEFLINK, REPLINK, DEFTRANS, REPTRANS, DELTRANS, or SHOW DEFTRANS. is the value specified for the QUAL operand. This operand specifies the qualifier for OPSC transactions. transaction-qualifier Effect. The command is rejected. Recovery.
Messages NNM2905 NNM2905 VALUE SPECIFIED FOR TERMNAME OPERAND WAS TOO LONG terminal-name Cause. An OPSC command was issued, but the value specified for the TERMNAME operand was longer than 24 characters. The command was DEFLINK or REPLINK. terminal-name is the value specified for the TERMNAME operand. This operand specifies the RSC terminal name. Effect. The command is rejected. Recovery. Replace the value with a shorter RSC terminal name, and retry the command.
Messages NNM2910 NNM2909 DYNAMIC LINK TABLE ENTRY ALREADY EXISTS Cause. A DEFLINK command was issued to define an OPSC link, but a Dynamic Link Table (DLT) entry already existed for the specified link name or terminal name mask. Effect. The OPSC link definition is not added to the DLT. Recovery. Use the SHOW DEFLINK command to list all the entries in the DLT.
Messages NNM2911 NNM2911 LINK TERMNAME PROT QUAL OPSET C BC H M ENV Cause. A SHOW DEFLINK command was issued, and the message is part of the response. The line contains the headings of the SHOW DEFLINK display for any Dynamic Link Table (DLT) entries that define OPSC links keyed by OPSC link names. Other messages provide the actual information. LINK is the heading for the name of an OPSC link. TERMNAME is the heading for the RSC terminal name. PROT is the heading for the OPSC link protocol.
Messages NNM2912 NNM2912 link-name terminal-name communications-protocol transaction-qualifier option-set color-attribute background-color highlight-attribute monitor-class-attribute userenv Cause. A SHOW DEFLINK command was issued, and the message is part of the response. The line contains information about the attributes of a Dynamic Link Table (DLT) entry, which defines an OPSC link and is keyed by the OPSC link name. link-name is the name of the OPSC link.
Messages NNM2913 NNM2913 TERMMASK PREF PROT QUAL OPSET C BC H M ENV Cause. A SHOW DEFLINK command was issued, and the message is part of the response. The line contains the headings of the SHOW DEFLINK display, for any Dynamic Link Table (DLT) entries that define OPSC links keyed by RSC terminal name masks. Other messages provide the actual information. TERMASK is the heading for an RSC terminal name mask. PREF is the heading for the prefix to be used to create an OPSC link name.
Messages NNM2916 NNM2914 terminal-name-mask link-prefix communications-protocol transaction-qualifier option-set color-attribute background-color highlight-attribute monitor-class-attribute userenv Cause. A SHOW DEFLINK command was issued, and the message is part of the response. The line contains information about the attributes of a Dynamic Link Table (DLT) entry, which defines an OPSC link keyed by the RSC terminal name mask. terminal-name-mask is the RSC terminal mask.
Messages NNM2917 NNM2917 VALUE SPECIFIED FOR TRANSID OPERAND WAS TOO LONG transaction-id Cause. An OPSC command was issued, but the value specified for the TRANSID operand was longer than 32 characters. The command was one of DEFTRANS, REPTRANS, DELTRANS, or SHOW DEFTRANS. transaction-id is the value specified for the TRANSID operand. This operand specifies the OPSC transaction identifier. Effect. The command is rejected. Recovery. Replace the value with a shorter transaction ID, and retry the command.
Messages NNM2922 NNM2920 TRANSACTION CONTROL TABLE ENTRY ALREADY EXISTS Cause. A DEFTRANS command was issued to define an OPSC transaction but a Transaction Control Table (TCT) entry with the specified transaction ID (and qualifier, if one was specified) already existed. Effect. The OPSC transaction definition is not added to the TCT. Recovery. Use the SHOW DEFTRANS command to list all the entries in the TCT.
Messages NNM2923 NNM2923 VALUE SPECIFIED FOR PROC OPERAND WAS TOO LONG - procedure-name Cause. A DEFTRANS or REPTRANS command was issued, but the value specified for the PROC operand was longer than eight characters. is the value specified for the PROC operand. This operand specifies the NCL procedure file name. procedure-name Effect. The command is rejected. Recovery. Correct the NCL procedure file name, and retry the command. NNM2924 TRANSID TPN QUAL ENV/LNK/DOMN PROC SYNC SECURITY Cause.
Messages NNM2926 NNM2925 transaction-id transaction-program-name transaction-qualifier transaction-environment procedure-name sync-level security-level Cause. A SHOW DEFTRANS command was issued, and the message is part of the response. The line contains information about the attributes of a Transaction Control Table (TCT) entry, which defines an OPSC transaction. transaction-id is the transaction identifier. transaction-program-name is the transaction program name.
Messages NNM2927 NNM2927 VALUE SPECIFIED FOR TRANSID OPERAND IS RESERVED transaction-id Cause. A DEFTRANS or REPTRANS command was issued, but the value specified for the TRANSID operand began with a $ character. Transaction IDs beginning with $ are reserved. transaction-id is the value specified for the TRANSID operand. This operand specifies the OPSC transaction ID. Effect. The command is rejected. Recovery.
Messages NNM2932 NNM2930 MODE CONTROL TABLE ENTRY command-action Cause. A DEFMODE, REPMODE or DELMODE command was issued and was successful. command-action is the actual operation on the Mode Control Table (MCT) entry, which occurred as a result of the command being issued, as follows: DEFINED indicates that a new MCT entry was added. REPLACED indicates that an existing MCT entry was replaced. DELETED indicates that an existing MCT entry was deleted. Effect. The operation is completed. Recovery.
Messages NNM2933 NNM2933 MODE SESSLIM MINWIN MINLOSE Cause. A SHOW DEFMODE command was issued, and the message is part of the response. The line contains the headings of the SHOW DEFMODE display. Other messages provide the actual information. MODE is the heading for the name of an OPSC mode definition. SESSLIM is the heading for the maximum number of sessions for a mode definition. MINWIN is the heading for the minimum number of contention winners for a mode definition.
Messages NNM2938 NNM2936 OPTION SET CONTROL TABLE ENTRY command-action Cause. A DEFOPSET, REPOPSET, or DELOPSET command was issued and was successful. command-action is the actual operation on the Option Set Control Table (OSCT) entry, which occurred as a result of the command being issued, as follows: DEFINED indicates that a new OSCT entry was added. REPLACED indicates that an existing OSCT entry was replaced. DELETED indicates that an existing OSCT entry was deleted. Effect.
Messages NNM2939 NNM2939 OPSET MODENAMES PARSESS SECURITY Cause. A SHOW DEFOPSET command was issued, and the message is part of the response. The line contains the headings of the SHOW DEFOPSET display. Other messages provide the actual information. OPSET is the heading for the name of an OPSC option set definition. MODENAMES is the heading for up to four mode names that are related to an option set definition. PARSESS is the heading for whether parallel sessions are supported on a single link.
Messages NNM2944 NNM2941 NO ENTRIES FOUND IN OPTION SET CONTROL TABLE Cause. A SHOW DEFOPSET command was issued, but no entries existed in the OPSC Option Set Control Table (OSCT). Effect. No OSCT entries are displayed. Recovery. This message is informational only; no recovery action is necessary. NNM2942 INVALID MODE LIST SPECIFIED FOR MODE OPERAND - operand-value Cause. A DEFOPSET or REPOPSET command was issued, but the MODE operand specified an invalid mode list.
Messages NNM2945 NNM2945 TCT ENTRY NOT command-action - TPN NOT UNIQUE Cause. A DEFTRANS or REPTRANS command was issued to define, or redefine, an OPSC transaction, but a Transaction Control Table (TCT) entry with the specified transaction program name (and qualifier, if one was specified) already existed. command-action is ADDED or REPLACED. Effect. The command is rejected. Recovery. Use the SHOW DEFTRANS command to list all the entries in the TCT.
Messages NNM2950 NNM2948 QUAL : transaction-qualifier Cause. A SHOW DEFTRANS command was issued, and the message is part of the response. The line contains information about the QUAL operand. transaction-qualifier is the qualifier for the OPSC transaction. Effect. The information about QUAL is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM2949 ENV : transaction-environment Cause.
Messages NNM2951 NNM2951 : domain-id DOMAIN Cause. A SHOW DEFTRANS command was issued, and the message is part of the response. The line contains information about the DOMAIN operand. is the domain ID of the NonStop NET/MASTER MS where the OPSC transaction occurs. domain-id Effect. The information about DOMAIN is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. NNM2952 : procedure-name PROC Cause.
Messages NNM2958 NNM2955 INVALID HEXADECIMAL STRING SPECIFIED FOR TPN OPERAND transaction-program-name Cause. A DEFTRANS or REPTRANS command was issued, specifying a hexadecimal value in an incorrect format. A hexadecimal value must start with a single quote ('), followed by one or more pairs of hexadecimal digits, and ending with a quote followed by the letter X: for example, TPN='6E4D3F'X. A maximum of 64 pairs of hexadecimal digits may be specified in this format.
Messages NNM2959 NNM2959 OPSC operand ERROR, ID=conversation-id - error-text Cause. An OPSC verb was issued and failed. operand is the second part of the OPSC verb (for example, SEND). conversation-id is the ID that identifies the OPSC conversation to the NCL process. error-text is CONVERSATION ID NOT KNOWN indicating that the specified conversation ID is not active for this NCL process. Effect. The requested OPSC conversation action is not taken. Recovery.
3 NCL Error Codes NCL Error Codes NCL error codes signify errors that occur during the execution of an NCL procedure. The codes might appear as part of a NonStop NET/MASTER message and can be accessed through the &SYS.ERROR.CODE system variable in an error handler. This section lists each error code number followed by a description of the code. 1. An invalid external procedure name was encountered and could not be loaded. The name was evaluated during run time and contained invalid or too many characters.
NCL Error Codes NCL Error Codes 19. A RETSUB core statement was encountered without a previous GOSUB core statement. 20. A SIGNAL core statement caused a recursive loop. 21. None of the conditions in a SELECT core statement were true but there was no OTHERWISE clause. 22. The procedure was terminated after an error handler was processed. 23. A RESUME core statement was not processed because the value of the &SYS.ERROR.
NCL Error Codes NCL Error Codes 38. A variable name was evaluated at run time but the resultant name contained invalid characters. 39. The evaluation of a variable name at run time required more buffers than were available. You may have used a complicated name that contains complex and nested components. NCL guarantees three levels of nesting. 40. A variable name was evaluated at run time but an “&(” was encountered without a matching “)”. 41.
NCL Error Codes NCL Error Codes 56. A VARTABLE verb was issued for a vartable that has a numeric key but the specified key was found to be nonnumeric. 57. A verb was issued but the syntax was found to be wrong. 58. The virtual memory allocated to NCL processes as specified in the NCLMAXK system parameter was used up and the NCL process cannot continue. 59. An attempt was made to resume normal processing from within a FLUSH_ERROR error handler. 60.
NCL Error Codes NCL Error Codes 78. A VARS list was specified using the GENERIC keyword but the variable specification is not of the form &[prefix]*. 79. An ASSIGN OPT={SETERR|RESETERR|SETMOD|RESETMOD} verb was issued to try to update global, MDO, or system variables. The option is not applicable to those variables. 80. A LOCK verb was issued to access a resource but the number of requests that were being serviced or were waiting to be serviced exceeded the value specified in the LOCKMAX system parameter.
NCL Error Codes NCL Error Codes 7180. A line in the display part of a panel definition file contains an error. Message NNM1378 provides further information on the error. 7182. An error occurred while reading a variable in the display part of a panel definition file. An associated message provides further information on the error. 7189. At the time when a panel was to be displayed, a shortage in CPU memory was encountered. 7190.
NCL Error Codes Error Names Error Names An error name identifies an error condition that can be in an error handler. Table 3-1 lists the error names and the NCL error codes that raise the error. Table 3-1.
NCL Error Codes Error Names (This page left intentionally blank) 3–8 106159 Tandem Computers Incorporated
4 Event-Message Tokens Event-Message Event-message tokens provide a means by which your application can retrieve Tokens information on Event Management Service (EMS) events. An event message contains two types of tokens: Header tokens appear in every event message and contain general information on the message. Data-portion tokens, on the other hand, contain specific information on the event that raised the message. The following event messages are listed in sequence of NonStop NET/MASTER message numbers.
Event-Message Tokens 0001: ZNNM-EVT-UNNAMED-PROC 0001: ZNNM-EVT-UNNAMED-PROC A TACL RUN command tried to start the NonStop NET/MASTER MS control process without specifying a process name. All processes in the NonStop NET/MASTER MS system must be named.
Event-Message Tokens 0002: ZNNM-EVT-TRACE-OPEN-ERR 0002: ZNNM-EVT-TRACE-OPEN-ERR The trace failed because there was an error with the file.
Event-Message Tokens 0003: ZNNM-EVT-TRACE-ENABLE ZSPI-TKN-PROC-ERR identifies the OPEN procedure. ZFIL-TKN-FILENAME contains the name of the trace file. It appears as filename in the message text. ZSPI-TKN-ENDLIST ends the list. 0003: ZNNM-EVT-TRACE-ENABLE Tracing to the file indicated was enabled.
Event-Message Tokens 0004: ZNNM-EVT-TRACE-IO-ERROR 0004: ZNNM-EVT-TRACE-IO-ERROR The trace failed because there was an error with the file.
Event-Message Tokens 0005: ZNNM-EVT-RCV-FULL ZSPI-TKN-PROC-ERR identifies the procedure call that had an error. ZFIL-TKN-FILENAME contains the name of the file that had the error. It appears as filename in the message text. ZSPI-TKN-ENDLIST ends the list. 0005: ZNNM-EVT-RCV-FULL An internal queueing problem has occurred. The queue has become full and cannot accept any more messages.
Event-Message Tokens 0006: ZNNM-EVT-RCV-FILLING 0006: ZNNM-EVT-RCV-FILLING A NonStop NET/MASTER MS process was receiving data messages from a process external to the NonStop NET/MASTER MS system. The internal receive queue was enabled but no thread was processing it. The message is issued once for every ten messages added to the internal receive queue.
Event-Message Tokens 0007: ZNNM-EVT-RCV-DISCARD 0007: ZNNM-EVT-RCV-DISCARD The NonStop NET/MASTER MS process received an unexpected message.
Event-Message Tokens 0008: ZNNM-EVT-THREAD-ABEND1 0008: ZNNM-EVT-THREAD-ABEND1 An internal check in a process failed.
Event-Message Tokens 0008: ZNNM-EVT-THREAD-ABEND1 ZNNM-TKN-OFILENAME contains the name of the object file. It appears as objfile in the message text. ZNNM-TKN-ADDR contains the P-address where the process failed. It appears as addr in the message text. ZNNM-TKN-TRAP-NUM contains the trap number that was reported. It appears as trapid in the message text. ZNNM-TKN-SUBSYS contains the thread subsystem number. It appears as thrdss in the message text. ZNNM-TKN-THREAD-ID contains the thread identifier.
Event-Message Tokens 0009: ZNNM-EVT-THREAD-ABEND2 0009: ZNNM-EVT-THREAD-ABEND2 A system trap occurred in the process.
Event-Message Tokens 0009: ZNNM-EVT-THREAD-ABEND2 ZNNM-TKN-TRAP-NUM contains the trap number that was reported. It appears as trapid in the message text. ZNNM-TKN-SUBSYS contains the thread subsystem number. It appears as thrdss in the message text. ZNNM-TKN-THREAD-ID contains the thread identifier. It appears as thrdno in the message text. ZNNM-TKN-TRAP-STRING contains the description of the trap. It appears as trapname in the message text.
Event-Message Tokens 0010: ZNNM-EVT-TRACE-DISABLE 0010: ZNNM-EVT-TRACE-DISABLE A SYSPARMS TRACEFLAGS=0 command was issued and tracing was disabled to the file name indicated.
Event-Message Tokens 0016: ZNNM-EVT-STACK-TRACE 0016: ZNNM-EVT-STACK-TRACE When a process abends, a series of messages ordered by increasing frame number is issued. The frame number, function count, and instruction count can be used to identify the problem.
Event-Message Tokens 0551: ZNNM-EVT-OBJ-FILE-INCOMPLETE 0551: ZNNM-EVT-OBJ-FILE-INCOMPLETE During system startup, some of the NonStop NET/MASTER MS program object files could not be found or are not of the correct version.
Event-Message Tokens 0552: ZNNM-EVT-NEWPROCESS-ERR 0552: ZNNM-EVT-NEWPROCESS-ERR A NEWPROCESS error occurred while the control process was attempting to start a process. Tokens Token Name Token Type Value Assigned ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZSPI-TKN-SSID ZSPI-TYP-INT ZSPI-TYP-BOOLEAN ZSPI-TYP-SSID 0552 TRUE 117 ZEMS-TKN-SUBJECT-MARK ZSPI-TYP-MARK ZNNM-TKN-PROC-NAME ZSPI-TYP-STRING ZSPI-TKN-ERRLIST ZSPI-TYP-LIST ZSPI-TKN-ERROR.ZNNM-DDL-ERROR.Z-SSID ZSPI-DDL-SSID ZSPI-TKN-ERROR.
Event-Message Tokens 0552: ZNNM-EVT-NEWPROCESS-ERR ZSPI-TKN-ERROR.ZNNM-DDL-ERROR.Z-SSID contains the ID of the subsystem that reported the error. ZSPI-TKN-ERROR.ZNNM-DDL-ERROR.ZBYTE1 contains the first byte of the error code returned by NEWPROCESS. The error appears in err1 in the message text. ZSPI-TKN-ERROR.ZNNM-DDL-ERROR.ZBYTE2 contains the second byte of the error code returned by NEWPROCESS. The error appears in err2 in the message text. ZSPI-TKN-PROC-ERR identifies the NEWPROCESS procedure.
Event-Message Tokens 0553: ZNNM-EVT-CONFIG-ERR 0553: ZNNM-EVT-CONFIG-ERR There is an error in the configuration file.
Event-Message Tokens 0565: ZNNM-EVT-NCL-INIT-FAIL 0565: ZNNM-EVT-NCL-INIT-FAIL The NCL procedure INIT could not be executed.
Event-Message Tokens 0566: ZNNM-EVT-NCL-READY-FAIL 0566: ZNNM-EVT-NCL-READY-FAIL The NCL procedure READY could not be executed.
Event-Message Tokens 0567: ZNNM-EVT-SYSTEM-STOP 0567: ZNNM-EVT-SYSTEM-STOP A SHUTDOWN or FSTOP command was received while the NonStop NET/MASTER MS system was in the last stage of a shutdown.
Event-Message Tokens 0568: ZNNM-EVT-PROCESS-STOP 0568: ZNNM-EVT-PROCESS-STOP The control process stopped the process during shutdown.
Event-Message Tokens 0569: ZNNM-EVT-ALL-PROCESSES-STOP 0569: ZNNM-EVT-ALL-PROCESSES-STOP All NonStop NET/MASTER MS processes (including the control process) are stopped and shutdown is complete.
Event-Message Tokens 0570: ZNNM-EVT-NO-START-GMM 0570: ZNNM-EVT-NO-START-GMM One of the GMM processes could not be started during the initialization of the NonStop NET/MASTER MS system. The system requires all GMM processes to be started.
Event-Message Tokens 0571: ZNNM-EVT-NO-START-SECEXIT 0571: ZNNM-EVT-NO-START-SECEXIT One of the security exit processes could not be started during the initialization of the NonStop NET/MASTER MS system. The system requires all security exit processes to be started.
Event-Message Tokens 0572: ZNNM-EVT-NO-START-DSNM 0572: ZNNM-EVT-NO-START-DSNM One of the DSNM processes could not be started during the initialization of the NonStop NET/MASTER MS system. The system requires all DSNM processes to be started.
Event-Message Tokens 0573: ZNNM-EVT-PROCESS-NOT-NAMED 0573: ZNNM-EVT-PROCESS-NOT-NAMED During the startup of your NonStop NET/MASTER MS system, a process that must be executed as a named process was started without a process name.
Event-Message Tokens 0574: ZNNM-EVT-INVALID-BACKUP-CPU 0574: ZNNM-EVT-INVALID-BACKUP-CPU During the startup of your NonStop NET/MASTER MS system, a process was started with an invalid backup CPU. The backup CPU number cannot be higher than the highest CPU number configured on your Tandem system.
Event-Message Tokens 0575: ZNNM-EVT-PREMATURE-TAKEOVER 0575: ZNNM-EVT-PREMATURE-TAKEOVER A primary NonStop NET/MASTER MS process failed before initialization completed. The backup process did not have enough information to enable the initialization to continue.
Event-Message Tokens 0576: ZNNM-EVT-NO-STARTUP-MSG 0576: ZNNM-EVT-NO-STARTUP-MSG An I/O error occurred when a NonStop NET/MASTER MS process was reading its startup message.
Event-Message Tokens 0577: ZNNM-EVT-WRONG-OS-VERSION 0577: ZNNM-EVT-WRONG-OS-VERSION An attempt was made to start NonStop NET/MASTER MS on a Tandem system that was using a wrong version of the operating system. NonStop NET/MASTER MS requires operating system release D30.00 or later.
Event-Message Tokens 0578: ZNNM-EVT-TOO-MANY-TAKEOVERS 0578: ZNNM-EVT-TOO-MANY-TAKEOVERS A NonStop NET/MASTER MS process that ran as a process pair had to switch over to the backup process too many times, indicating an unstable processing environment.
Event-Message Tokens 0579: ZNNM-EVT-SYS-STARTUP-PARAM 0579: ZNNM-EVT-SYS-STARTUP-PARAM Your NonStop NET/MASTER MS system was being started, and the message was displayed to provide the startup information.
Event-Message Tokens 0579: ZNNM-EVT-SYS-STARTUP-PARAM ZNNM-TKN-PROC-NAME contains the name of the process generating the event. The process is the subject of the event. ZNNM-TKN-USERID contains the Guardian user ID of the user who started NonStop NET/MASTER MS. It appears as group-number (upper byte) and user-number (lower byte) in the message text. ZNNM-TKN-XFILENAME(1) contains the device name of the terminal from which NonStop NET/MASTER MS was started. It appears as home-term in the message text.
Event-Message Tokens 0580: ZNNM-EVT-SECURITY-WARNING 0580: ZNNM-EVT-SECURITY-WARNING During the startup of NonStop NET/MASTER MS, the licensed program object file (which may execute privileged instructions) was not secured properly. The message was displayed to warn of the possible security exposure. The recommended file security of NonStop NET/MASTER MS licensed program object files is either --Oor --U-.
Event-Message Tokens 0582: ZEMS-EVT-PROC-RESTART-WARN 0582: ZEMS-EVT-PROC-RESTART-WARN The number of restarts of a failed NonStop NET/MASTER MS static or external process (for example, a DSNM process) reached the maximum number allowed for the time interval, or the time limit for restarts expired.
Event-Message Tokens 0585: ZNNM-EVT-PROCESS-SWITCH ZNNM-TKN-NUM-SECS contains the time interval (in seconds) within which NCP failed to restart the process. It appears as time-interval in the message text. 0585: ZNNM-EVT-PROCESS-SWITCH A PROCESS SWITCH command reversed the role of the primary and backup process of the NonStop NET/MASTER process pair.
Event-Message Tokens 0586: ZNNM-EVT-BACKUP-CPU-CHANGE 0586: ZNNM-EVT-BACKUP-CPU-CHANGE A PROCESS ALTER=process-name BACKUPCPU=new-cpu command changed the CPU in which the backup process of the NonStop NET/MASTER MS process pair executes or is to execute.
Event-Message Tokens 0750: ZNNM-EVT-SECURITY-NOT-RUN ZNNM-TKN-NONSTOP-STATE contains the changed status of the backup process when the command takes effect. It appears as backup-status in the message text. ZNNM-TKN-CMD-EFFECT contains the information that indicates whether the command takes effect immediately. It appears as command-effect in the message text. ZNNM-TKN-BACKUP-CPU(1) contains the old processor number for the backup process. This token is not present if a backup process does not exist.
Event-Message Tokens 0751: ZNNM-EVT-SECURITY-NOT-SAME 0751: ZNNM-EVT-SECURITY-NOT-SAME The configuration file contains more than one security exit. When the NonStop NET/MASTER MS system attempted to access the exits, they were found to be of different types. Security exits must be of the same type.
Event-Message Tokens 0752: ZNNM-EVT-SECURITY-IO-FAIL 0752: ZNNM-EVT-SECURITY-IO-FAIL The application was not able to read from, write to, or open a security exit. Tokens Token Name Token Type Value Assigned ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZSPI-TKN-SSID ZSPI-TYP-INT ZSPI-TYP-BOOLEAN ZSPI-TYP-SSID 0752 TRUE 117 ZEMS-TKN-SUBJECT-MARK ZNNM-TKN-PROC-NAME ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR.Z-SSID ZSPI-TKN-ERROR.
Event-Message Tokens 0752: ZNNM-EVT-SECURITY-IO-FAIL ZSPI-TKN-ERRLIST begins a standard Guardian error list owned by TANDEM.FILSYS. ZSPI-TKN-ERROR is the standard SPI error token, with the value of the fields Z-SSID and Z-ERROR. Z-SSID is the Guardian subsystem identifier ZGRD-VAL-SSID. Z-ERROR is the trap number. ZFIL-TKN-FILENAME contains the name of the file that had the error. It appears as filename in the message text. ZSPI-TKN-PROC-ERR identifies the procedure that cause the error.
Event-Message Tokens 0753: ZNNM-EVT-SECURITY-TYPE-INV 0753: ZNNM-EVT-SECURITY-TYPE-INV The installation provided a non-standard security exit. When the NonStop NET/MASTER MS system attempted to access the exit, the exit was found to be of an unsupported type.
Event-Message Tokens 0754: ZNNM-EVT-SECURITY-WRONG-VAL 0754: ZNNM-EVT-SECURITY-WRONG-VAL The installation provided a non-standard security exit. When the NonStop NET/MASTER MS system attempted to use the exit, the exit set an invalid return code. This is a user programming error.
Event-Message Tokens 0755: ZNNM-EVT-SECURITY-NO-PROF 0755: ZNNM-EVT-SECURITY-NO-PROF The installation provided a non-standard security exit. During a security check, the NonStop NET/MASTER MS system expected the exit to return a user profile. A full exit must always return a user profile; a password exit should return a profile if one was provided. This is a user programming error.
Event-Message Tokens 0980: ZNNM-EVT-NNM-SHUTTING 0980: ZNNM-EVT-NNM-SHUTTING An FSTOP, SHUTDOWN, or SHUTDOWN $ABEND$ command was issued to shut down a NonStop NET/MASTER MS system externally by using the NNM shutdown utility.
Event-Message Tokens 0985: ZNNM-EVT-REQUEST-OK 0985: ZNNM-EVT-REQUEST-OK An FSTOP or SHUTDOWN command was successful.
Event-Message Tokens 0990: ZNNM-EVT-CPYRITE 0990: ZNNM-EVT-CPYRITE The message contains the copyright information and appears during the startup of a NonStop NET/MASTER MS system.
Event-Message Tokens 0990: ZNNM-EVT-CPYRITE ZNNM-TKN-VERSION contains the release version. It appears as vers in the message text. ZNNM-TKN-REL-DATE contains the release date. It appears as releasedate in the message text. ZNNM-TKN-CPYRIGHT contains the copyright text. It appears as copyrighttext in the message text.
Event-Message Tokens 1400: ZNNM-EVT-MEMORY-FAIL 1400: ZNNM-EVT-MEMORY-FAIL An internal check in a Global Memory Manager (GMM) process failed causing the GMM process to abend.
Event-Message Tokens 1400: ZNNM-EVT-MEMORY-FAIL ZNNM-TKN-TRAP-NUM contains the trap number that was reported. It appears as trapnum in the message text. ZNNM-TKN-OFILENAME contains the object file name. It appears as file in the message text. ZNNM-TKN-LINE-NUM0 contains the current line number. It appears as line in the message text. ZNNM-TKN-LINE-NUM1 contains the fractional part of the current line number. It appears as fract in the message text.
Event-Message Tokens 1401: ZNNM-EVT-SYS-TRAP 1401: ZNNM-EVT-SYS-TRAP A system trap occurred in a Global Memory Manager (GMM) process.
Event-Message Tokens 1402: ZNNM-EVT-GMS-BACKUP-STATE 1402: ZNNM-EVT-GMS-BACKUP-STATE The backup process of the Global Memory Manager (GMM) was not running. This is a warning message informing the user that the GMM process cannot be recovered if the primary process is stopped.
Event-Message Tokens 1507: ZNNM-EVT-NO-LOG-FILE 1507: ZNNM-EVT-NO-LOG-FILE The LOG system was unable to log event messages. Possible causes are: LOGWRAP system parameter has a value of NO and all declared log files were used. Log files are secured from access by the LOG system, in which case the reason for the error is returned.
Event-Message Tokens 1544: ZNNM-EVT-LOG-ERROR 1544: ZNNM-EVT-LOG-ERROR The LOG system was unable to log event messages. The record length of the message exceeded the maximum length allowed for an activity log record.
Event-Message Tokens 2188: ZNNM-EVT-BAD-BACKUP-CPU 2188: ZNNM-EVT-BAD-BACKUP-CPU The first symbol in the parameter string portion of the startup message to the security exit was not acceptable as a backup CPU number.
Event-Message Tokens 2189: ZNNM-EVT-BAD-FILE-NAME 2189: ZNNM-EVT-BAD-FILE-NAME The second through fifth symbols in the parameter string portion of the startup message to the security exit are supposed to be the names of the Utility Access database files. This message indicates that one of those file names is invalid.
Event-Message Tokens 2190: ZNNM-EVT-OPEN-ERROR 2190: ZNNM-EVT-OPEN-ERROR A file management error occurred when opening a file in the security exit server.
Event-Message Tokens 2191: ZNNM-EVT-IO-ERROR 2191: ZNNM-EVT-IO-ERROR A file management error occurred when accessing a file in the security exit server.
Event-Message Tokens 2191: ZNNM-EVT-IO-ERROR ZSPI-TKN-ERRLIST begins a standard Guardian error list owned by TANDEM.FILSYS. ZSPI-TKN-ERROR is the standard SPI error token, with the value of the fields Z-SSID and Z-ERROR. Z-SSID is the Guardian subsystem identifier ZGRD-VAL-SSID. Z-ERROR is the trap number. ZSPI-TKN-PROC-ERR contains the code value for the procedure that returned the error. The code value can be ZFIL-VAL-KEYPOSITION, ZFIL-VAL-READUPDATE, or ZFIL-VAL-AWAITIO.
Event-Message Tokens 2192: ZNNM-EVT-CHECKPOINT-ERROR 2192: ZNNM-EVT-CHECKPOINT-ERROR An error occurred on a CHECKPOINT procedure call in the security exit server.
Event-Message Tokens 2193: ZNNM-EVT-CHECKOPEN-ERROR ZSPI-TKN-ERRLIST begins a standard Guardian error list owned by TANDEM.FILSYS. ZSPI-TKN-ERROR is the standard SPI error token, with the value of the fields Z-SSID and Z-ERROR. Z-SSID is the Guardian subsystem identifier ZGRD-VAL-SSID. Z-ERROR is the trap number. ZFIL-TKN-CHECKPOINTSTATUS contains the status returned by CHECKPOINT. It appears as err1 and err2 in the message text.
Event-Message Tokens 2193: ZNNM-EVT-CHECKOPEN-ERROR ZEMS-TKN-SUBJECT-MARK marks the next token in the event-message buffer as a subject token of the event message. ZSPI-TKN-ERRLIST begins a standard Guardian error list owned by TANDEM.FILSYS. ZSPI-TKN-ERROR is the standard SPI error token, with the value of the fields Z-SSID and Z-ERROR. Z-SSID is the Guardian subsystem identifier ZGRD-VAL-SSID. Z-ERROR is the trap number. ZFIL-TKN-FILENAME contains the name of the file that was opened.
Event-Message Tokens 2194: ZNNM-EVT-BACKUP-TAKEOVER 2194: ZNNM-EVT-BACKUP-TAKEOVER The backup of the security exit process has taken over.
Event-Message Tokens 2195: ZNNM-EVT-BACKUP-FAILURE 2195: ZNNM-EVT-BACKUP-FAILURE The backup of the security exit process failed.
Event-Message Tokens 2196: ZNNM-EVT-BACKUP-CREATE-ERROR 2196: ZNNM-EVT-BACKUP-CREATE-ERROR The security exit server encountered an error trying to start its backup.
Event-Message Tokens 2196: ZNNM-EVT-BACKUP-CREATE-ERROR ZGRD-TKN-CPU contains the CPU number passed to NEWPROCESS. ZGRD-TKN-PROCESSNAME contains the value (name) of the parameter to NEWPROCESS. ZSPI-TKN-ENDLIST ends the list.
Event-Message Tokens 2197: ZNNM-EVT-BAD-DB-REC 2197: ZNNM-EVT-BAD-DB-REC There ia a problem with one of the records in the Utility Access database.
Event-Message Tokens 2197: ZNNM-EVT-BAD-DB-REC ZNNM-TKN-BAD-DB-CODE tells what is wrong with the record and contains: the value one, indicating that the format of the MDO header is bad. It does not have the proper item code, or its length is wrong. the value two, indicating that one of the items that is supposed to be a command authority number is not a valid integer (in character form).
Event-Message Tokens 2198: ZNNM-EVT-TOO-MANY-SAME-AS 2198: ZNNM-EVT-TOO-MANY-SAME-AS More than five command sets were examined in one request due to the use of the “Same as” field in the definitions.
Event-Message Tokens 2199: ZNNM-EVT-BAD-SECEXIT-RQST 2199: ZNNM-EVT-BAD-SECEXIT-RQST An invalid request was sent to the security exit server.
Event-Message Tokens 2199: ZNNM-EVT-BAD-SECEXIT-RQST ZNNM-TKN-BAD-RQST-CODE tells what is wrong and contains: The value one, indicating that the format of the MDO header for the user data is bad. It does not have the proper item code, or its length is wrong. The value two, indicating that the file name in the open request is missing, or is not a valid file. The invalid file name appears as text in the message text.
Glossary This glossary defines NonStop NET/MASTER and Tandem system terms and abbreviations used in this manual. %INCLUDE rule. An RMS message action rule that allows a message handler to use rules from more than one ruleset. %START rule. An RMS message action rule that instructs a message handler to perform user-defined initialization actions on startup. => prompt. Any prompt that ends with =>: for example, Command ===>, M=>, and Select Option ===>. absolute time.
Glossary attribute byte. The data that defines the display attributes of a field on a screen. The attribute byte is displayed as a blank on the screen. It is represented by a field character in a panel description file. authority level. A number assigned to users, NonStop NET/MASTER MS commands, and NonStop NET/MASTER MS operands that signifies the authority to execute a command or operand. Authority levels range from 0 (lowest) through 255 (highest). autohold.
Glossary BIU. See basic information unit. BK process. See background services process. blank concatenation operation. An operation that replaces multiple blanks between two terms in an expression by a single blank. block. A logical group of statements. Blocks are bounded by core statements such as PROCEDURE and END, FUNCTION and END, DO and END, and SELECT and END. BLOG. See Background Logger. BMON. See Background Monitor. Boolean.
Glossary COBOL85. The Tandem compiler and run-time support for the American National Standard Programming Language COBOL, X.3.23-1985. The code for most Pathway server processes is written using COBOL85. Command Entry facility. The NonStop NET/MASTER MS facility used as an alternative to OCS for entering commands. See also Operator Control Services. Command prompt. Command ===>. You enter commands at a Command prompt. Command Server Process.
Glossary communications network management (CNM). An IBM architecture that describes the structure of messages traveling to and from SNA devices. compilation. The process of creating object code from a source file of NCL statements. compilation error. An error in an NCL procedure detected during compilation (before execution). There are three types of compilation errors: from least to most severe these are warnings, errors, and fatal errors. See also error, fatal error, run-time error, and warning.
Glossary correlation key. An RMS key that restricts the use of a rule feature to messages with the same key. One example of a key is a text string containing variables. CPU weight. The relative availability of a CPU for the creation of dynamic processes. cultural indicator. An indicator that identifies the culture of command help information. culture.
Glossary DDL data dictionary. A database consisting of prenamed and predefined files created by the DDL compiler or Pathmaker. deadly embrace. A situation in which a resource required by one NCL process is indefinitely locked by another NCL process. debug. To locate and correct errors in an NCL process. decompilation. The process of creating NCL statements from object code. Decompilation occurs during the debugging of an NCL process, when using the DEBUG commands. dedicated terminal.
Glossary delimited UDB. A user database in which each field in a record is separated from the next field by hexadecimal ‘FF’ (called a field separator). dependent processing environment. A processing environment controlled and owned by an NCL process. The output from this environment goes to the NCL process. dependent queue. A queue owned by the NCL process that is controlling the associated dependent processing environment: either a request queue or a response queue. dependent request queue.
Glossary distribution procedure library. A library that contains the source code of NCL procedures distributed as part of a NonStop NET/MASTER MS installation or upgrade. DO group. A group of NCL statements enclosed by matching DO and END core statements that is executed only once. DO loop. A group of NCL statements enclosed by matching DO and END core statements that can be executed more than once. DOM ID. See delete operator message (DOM) ID. domain. A logical division within a network. domain ID.
Glossary EMS. See Event Management Service. EMS event collector. A Guardian process, part of the Tandem EMS subsystem, that collects and stores messages. The default EMS event collector is $0. EMS event distributor. An EMS process that distributes event messages from event logs to requesting management applications, to a collector on another node, or to printers, devices, or files. EMS message. A message generated internally by EMSPROC and identified by the letter E when displayed on an OCS window.
Glossary equate. A symbol defined to correspond to some text by the EQUATE command. The text is normally one or more NonStop NET/MASTER MS commands. There are two types of equates: local and global. error. A condition that causes the execution of a NonStop NET/MASTER MS command, the compilation of an NCL procedure, or the execution of an NCL process to fail (a run-time error). In NCL, a condition caused during compilation that would cause run-time errors if the NCL procedure were executed.
Glossary Expand. The Tandem network software that links together geographically distributed Tandem NonStop systems to create a network having the same reliability, capacity to preserve data integrity, and potential for modular expansion as a single system. explicit declaration. The definition of a procedure or function beginning with the PROCEDURE or FUNCTION core statement, respectively. explicit execution.
Glossary FK. See function key. fold. To convert a lowercase alphabetic character to its corresponding uppercase character. freeze. The act of inactivating RMS rules for a subject. When you freeze a subject, messages containing that subject cannot trigger any rules. full NRD message. A NRD message, held in the NRD message central queue, that must be deleted using its DOM ID. full-screen mode. A presentation mode in which a window consists entirely of a panel. function.
Glossary group. Any contiguous section of data within the fixed length data section of an element. group ID. The first part of a GUID consisting of a number from 1 through 255. group user ID. A user ID definition record, used as the default template for groups of individual users. Guardian user ID (GUID). The two-part Tandem ID, consisting of a group ID and a user ID, that defines a user to the Guardian environment. GUID. See Guardian user ID. header. The first part of a map or an element.
Glossary inclusive OR (OR). The Boolean operator that results in a value of 1 (TRUE) if one or both adjacent terms in an expression are true: otherwise the operator results in a value of 0 (FALSE). See also exclusive OR (XOR). indentation value. The number of columns used to indent the overrun lines of messages that are longer than the current width of an OCS window. INIT. The NCL procedure that is executed by the NonStop NET/MASTER MS control process (NCP) during system initialization. initial value.
Glossary internal trace point number. A number identifying a NonStop NET/MASTER MS internal event or other significant trace data. internal validation rules. Options specified in the #FLD panel control statement that determine how input is validated by Panel Services before it is passed to an NCL process. interpreter. The NonStop NET/MASTER MS entity that interprets an object and executes its opcodes. IS process. See inter-system services process. ISR. See Inter-System Routing. iterative. Repetitive.
Glossary line continuation character. The character used to continue an NCL statement over more than one line: in NCL, a comma (,). link definition. An INMC record, retained in global memory, that defines the characteristics, and registers the hierarchical relationship of its three components: a link definition record, a session definition record, and a unit definition record. link definition record.
Glossary manager. A process to which command messages for associated subjects are routed. In event messages, the managers make subjects of the same name unique. The ZEMS-TKN-MANAGER token contains the manager. map. A set of definitions used by Mapping Services that together describe the entire structure of some item of data. map definition record. A record in the NonStop NET/MASTER MS map file that describes the structure of a map. map file.
Glossary message ID. An ID that uniquely identifies a message. It is typically the first word of a message. message number. A number that uniquely identifies a message. It has two parts: the characters NNM and a unique number that can be used to refer to the message. message profile variable. A mapped data object variable that Mapping Services can understand using the map $MSG. message queue. A queue that holds roll-delete messages destined for an OCS window. message recognition element.
Glossary monitor-class message. A message that has the monitor-class attribute. Monitor-class messages are sent to monitor-class users. A monitor-class message is identified by the letter E, L, or M when it is displayed in an OCS window. monitor-class user. A user who is entitled to receive monitor-class messages. MS process. See multi-user services process. MSGPROC. A system-level NCL procedure that intercepts and processes messages destined for an OCS window. multi-user services (MS) process.
Glossary nested variable. A variable that begins with an ampersand and an opening parenthesis, and terminates with a closing parenthesis (&, (, and ), respectively). NET/MASTER. See SOLVE management services. Network Control Language (NCL). A structured, high-level, compiled language supplied with NonStop NET/MASTER MS and integrated with other NonStop NET/MASTER MS services. It is used to develop NCL procedures. Network Management Vector Transport (NMVT).
Glossary NRD message with the OPER attribute. A NRD message that is not held in the NRD message central queue, and must be deleted using NRD cursor deletion. When deleted, the message immediately disappears from the NRD message display area. null. No value. In NCL, assigning a variable a null value does not delete the variable name from memory. number. In NCL, a number is a symbol that begins with a digit (0 through 9) or a period and is in a context that permits it to be a number (rather than a string).
Glossary operand authority level. A number assigned to the operand of a NonStop NET/MASTER MS command. Authority levels range from 0 (lowest) through 255 (highest). A user whose authority level is equal to or greater than the operand authority level can execute the command using the operand. operating mode. The mode in which NonStop NET/MASTER MS is running, defined by the mix and presence or absence of application processes. See also advanced mode, basic mode, and extended basic mode.
Glossary panel library search path. The search order through the user panel library, customized panel library, and distribution panel library. panel object file search path. The search order through the panel object file(s) defined as part of the search path for panel description files. panel queue. A central queue, maintained by NonStop NET/MASTER MS, that holds panels currently in use. The maximum size of the queue is set by the SYSPARMS MAXPANEL command. panel skipping.
Glossary Pathway command terminal. A terminal at which a Pathway system manager enters PATHCOM commands to configure and control a Pathway system. Pathway server class identifier. A unique identifier that NonStop NET/MASTER MS assigns to a Pathway server class so that an NCL PATHSEND requester can communicate with the server class. Pathway system. The TCPs, servers, terminals, programs, and any subsystems associated with Pathway that run together under the control of one PATHMON process. pend-unload list.
Glossary primary name. The name given to an entire resource, used to control access to the resource by cooperating NCL processes. primary processing environment. A processing environment that is controlled and owned by an OCS window or a virtual user. The output from this environment goes to the OCS window or virtual user, respectively. primary program operator (PPO). In IBM terminology, an operator who is authorized to receive unsolicited messages. primary trigger.
Glossary program attention (PA) key. A key on an IBM 3270 keyboard used to interrupt the execution of a program. Depending on the keyboard, there may be several PA keys. protected field. A field in a panel that cannot be updated by a user. PU. See physical unit. PUP. See Peripheral Utility Program. purge ID. An ID used to purge a timer command or NRD message. purge message. A message sent when a timer command is purged from the timer queue. qualification name list.
Glossary relative time. A time value expressed in hours, minutes, and seconds representing an interval from the current time. Remote Operator Control (ROC). The NonStop NET/MASTER MS service that allows users to log on from a local NonStop NET/MASTER MS system to a remote system; to execute NonStop NET/MASTER MS commands at the remote system; and to receive the results at the local system. remote command. A NonStop NET/MASTER MS command sent to a remote system. remote system.
Glossary restricted function selection. Selection of an option from the NonStop NET/MASTER MS primary menu by a user allowed to choose from a restricted set of options. retain list. A list, maintained by NonStop NET/MASTER MS if procedure sharing is allowed, that holds in memory copies of NCL procedures that have been previously executed but are currently not being executed. RETURN key. A key that returns to a NonStop NET/MASTER MS primary menu from any menu level when pressed.
Glossary ruleset. A collection of RMS rules that defines responses to events such as message arrival and time conditions. The message handler uses the information in a ruleset to set up its execution environment and respond to incoming messages. The timer driver uses the information in a ruleset to set up the execution environments for the timers that respond to time events. run-time error. An error detected by NCL during the execution of an NCL process that can be trapped using an error handler.
Glossary server process. A process that implements requests for an application and returns replies to the requester process. server program. A program in a Pathway system written using a language such as COBOL85, TAL, MUMPS, FORTRAN, BASIC, C, or Pascal. session definition record. A record, created by the SESSION DEFINE command, that names and establishes the characteristics of an INMC session type. share list. The list of elements after a SHARE, NOSHARE, SHRVARS, or NOSHRVARS keyword. shared loading.
Glossary special character. In NCL, a lexical element that is a single character and acts as a delimiter in a statement. Its meaning depends on the current context. SPI. See Subsystem Programmatic Interface. SPLIT grid. The grid composed of one vertical and one horizontal line that appears after the SPLIT key is pressed on a Tandem 6530 or compatible terminal. splitting. The opening of a new window or adjusting of the current window.
Glossary strict test of equality. A test of equality by a strict relational operator. stripping. The removing of characters (including blanks) from text. In a panel, usually to either left justify, right justify, or center the text on a screen. In an expression, usually to perform a test of equality on the text. structured file. An Enscribe file type consisting of records, each of which consists of defined fields and keys. Entry-sequenced UDBs and key-sequenced UDBs are structured files. subject.
Glossary System Services Control Point (SSCP). The subsystem responsible for managing and allocating all resources in a domain in an IBM Systems Network Architecture (SNA) network and for communicating with network operators. There is one SSCP for each domain in an SNA network. System Support Services. A group of NonStop NET/MASTER MS services that includes the Activity Log Browse facility, the Command Entry facility, and the Display/Update SYSPARMS Settings facility. system panel library.
Glossary term. The basic unit of an expression in NCL. There are five types of terms: symbols, quoted strings, variables, parenthesized expressions, and function references. terminal control process (TCP). The Guardian process that interprets SCREEN COBOL object code, handles input-output to operator terminals, and sends messages to server processes. terminal definition record. The record created when defining a terminal to NonStop NET/MASTER MS. test mode.
Glossary trace parameter. A value in the trace parameter list specifying the events to trace. trace parameter list (TPL). A list associated with an OCS window that holds the current trace parameter settings. trace point. A NonStop NET/MASTER MS code position that can be traced. trace record. An entry in a trace file: a message mapped by the map $MSG, text data, or binary data. Transaction Application Language (TAL).
Glossary unmapped UDB. A user database in which NCL treats the data in each record as a sequence of contiguous bytes. NCL does not interpret the data in an unmapped user database: an unmapped user database can contain any binary data. unprotected field. A panel field that can accept input. unquoted string. Within an NCL statement, a sequence of characters that do not begin and end with quotes, do not result in a number, and do not have a predefined meaning when used in a particular context.
Glossary user NCL procedure. An NCL procedure created by a user. user panel library. A panel library containing the panel description files belonging to a particular user or group of users. user procedure library. A procedure library containing the NCL procedures belonging to a particular user or group of users. user variable. A variable created by an NCL procedure. Parameters are user variables. user-defined error handler. An error handler defined by a user. user-defined map.
Glossary verb. Sometimes called a “verb statement,” an NCL statement that is not an intrinsic part of NCL. Its availability depends on the enabling of a NonStop NET/MASTER MS feature. Verbs do not affect the structure and flow of NCL process execution. virtual user. A NonStop NET/MASTER MS user that does not have a terminal associated with it. A virtual user acts the same way as a real user and has the same attributes as a real user operating in OCS. wake-up timer.
Glossary (This page left intentionally blank) Glossary–40 106159 Tandem Computers Incorporated
