Chapter 60 NNM (NonStop NET/MASTER) Messages

The messages in this chapter are sent by the NonStop NET/MASTER (NNM) subsystem. The subsystem ID displayed by these messages includes NNM as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

objfile - PROCESS MUST BE NAMED

objfile

is the file name of the object code of the process.

Cause The startup procedure was altered such that the control process was not named. All processes in the NonStop NET/MASTER Management Services (MS) subsystem must be named.

Effect The NonStop NET/MASTER MS subsystem does not start.

Recovery Check the Tandem Advanced Command Language (TACL) RUN command in your startup procedure. Specify the process name and try again.

TRACE DISABLED, UNABLE TO OPEN FILE filename (errno)

`filename`	is the name of the file as specified by the TRACEFILE system parameter.
`errno`	identifies a file-system error.

Cause The trace failed because there was an error with the file.

Effect Tracing is disabled.

Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

TRACE ENABLED TO FILE filename

filename

is the name of the file specified by the TRACEFILE system parameter.

Cause Tracing to the file was enabled.

Effect Tracing is enabled.

Recovery Informational message only; no corrective action is needed.

TRACE DISABLED, IO ERROR ON OUTPUT FILE filename (errno)

`filename`	is the name of the file as specified by the TRACEFILE system parameter.
`errno`	identifies a file-system error.

Cause The trace failed because there was an error with the file.

Effect Tracing is disabled.

Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

WARNING - $RECEIVE DEPTH OF queue_depth HAS BEEN REACHED

queue_depth

is the number of data messages in the queue.

Cause An internal queueing problem has occurred. The queue has become full and cannot accept any more messages.

Effect Processing of new data messages is suspended until replies to some of the queued messages are issued.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable
Applications that were running when the message was displayed

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

WARNING - $RECEIVE QUEUE HAS count MESSAGES

count

is the number of messages in the queue.

Cause A NonStop NET/MASTER Management Services (MS) process was receiving messages from a process external to the system. The internal receive queue was enabled, but no thread was processing it. This message is issued once for every ten messages added to the internal receive queue.

Effect The NonStop NET/MASTER MS subsystem continues to receive messages from the external process.

Recovery Informational message only; no corrective action is needed.

WARNING - $RECEIVE MESSAGE DISCARDED, NO EPC ENTRY

Cause The NonStop NET/MASTER Management Services (MS) process received an unexpected message.

Effect The message is discarded.

Recovery Contact the the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated; frequency of occurrence
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable
Applications that were running when the message was displayed

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

process_name (objfile) ABENDING AT P=%paddr, TRAP=trapid, THRDID=thrdss/thrdno, filename [line.line]

`process_name`	is the name of the failed process.
`objfile`	is the file name of the object code that caused the problem.
`paddr`	is the memory address of the code that failed.
`trapid`	is an ID to help the Global NonStop Solution Center (GNSC) identify the problem.
`thrdss/thrdno`	is the ID of the thread.
`filename`	is the file name of the source code that caused the problem.
`line.line`	is the line number within the source file where the problem occurred.

Cause An internal check in a process has failed.

Effect The process abends. If the process is a static process, it is restarted.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable
Abend dump file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

process_name (objfile) ABENDING, TRAP=trapid, THRDID=thrdss/thrdno, trapname

`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 the Global NonStop Solution Center (GNSC) identify the problem.
`thrdss/thrdno`	is the ID of the thread.
`trapname`	is the name of the trap that has occurred.

Cause A system trap has occurred in the process.

Effect The process abends. If the process is a static process, it is restarted.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable
Abend dump file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

TRACE DISABLED TO FILE filename

filename

is the name of the file specified by the TRACEFILE system parameter.

Cause A SYSPARMS TRACEFLAGS=0 command was issued, and tracing to the file was disabled.

Effect Tracing is disabled.

Recovery Informational message only; no corrective action is needed.

STACK TRACE framenumber #functionname + %instrcountI

`framenumber`	is the frame number.
`#functionname`	is the function number.
`%instrcount`	is the instruction number.

Cause When a process abends, a series of messages is issued. The messages form a single set, ordered by increasing frame number. functionname and instrcount can help the Global NonStop Solution Center (GNSC) identify the problem. This message is for HP personnel only.

Effect The process abends. If the process is a static process, it is restarted.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable
Abend dump file

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

551

THE PROGRAM OBJECT FILES ARE INCOMPLETE

Cause During system startup, some of the NonStop NET/MASTER Management Services (MS) program object files could not be found or were not of the correct version.

Effect The startup of the NonStop NET/MASTER MS subsystem is abandoned.

Recovery Make sure that all NonStop NET/MASTER MS program object files are installed properly and are of the same version. Check the PROCESSOBJECT parameter in the configuration file (if used) to ensure that the correct object files are used.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable
Configuration file
List of the files (including the file security information) in the network control process (NCP) subvolume or specified by the PROCESSOBJECT parameter

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

552

NEWPROCESS ERROR process_name err1:err2 ON objfile

`process_name`	is the name of the process being started.
`err1`	identifies the NEWPROCESS error.
`err2`	identifies a NEWPROCESS error subcode or a file-system error.
`objfile`	is the name of the program to be executed.

Cause A NEWPROCESS error occurred while the control process was attempting to start a process.

Effect If the error code indicates that the process has started, then no action is taken and the process can be used. If the error code indicates that the process has not started, then the control process makes another attempt to start it.

Recovery See Appendix C, for information about the specified NEWPROCESS error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

See Appendix B, for a definition of the specified file-system error, if any. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

553

CONFIGURATION ERROR: errtext

errtext

contains the details of the error. There are four types of errors:

Duplicate Process: The NonStop NET/MASTER Management Services (MS) subsystem cannot add a process because of duplication. Remove the duplicate from the configuration file.
File Input/Output Error: Use the message and the displayed file-system error number to determine the cause and the appropriate action to take. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.
Too Many Processes Defined: There are too many processes of a certain type (for example, CMDSVR, CIP, or SECEXIT). Reduce the number of that type of process to within the allowed maximum. See the NonStop NET/MASTER Management Services (MS) System Management Guide.
Startup Parameter Error: Use the message to determine the error and correct, as appropriate.

Cause There is an error in the configuration file.

Effect The NonStop NET/MASTER MS subsystem is not started.

Recovery Correct the error in the configuration file and restart the NonStop NET/MASTER MS subsystem.

565

FAILED TO EXECUTE NCL INIT PROCEDURE

Cause The Network Control Language (NCL) procedure INIT could not be executed. Common causes include the following:

The INIT procedure is not present.
The INIT procedure is secured such that it cannot be accessed by the NonStop NET/MASTER Management Services (MS) subsystem.
The INIT procedure did not compile correctly.
The INIT procedure contained run-time errors.

Effect The startup of the NonStop NET/MASTER MS subsystem is abandoned.

Recovery Use the File Utility Program (FUP) to copy the activity log to your terminal, as follows:

TACL> FUP COPY log-file-name,,a,no head

Examine the output to determine the reason for the failure. Rectify the problem and restart the NonStop NET/MASTER MS subsystem.

566

FAILED TO EXECUTE NCL READY PROCEDURE

Cause The Network Control Language (NCL) procedure READY could not be executed. Common causes include the following:

The READY procedure is not present.
The READY procedure is secured such that it cannot be accessed by the NonStop NET/MASTER Management Services (MS) subsystem.
The READY procedure did not compile correctly.
The READY procedure contained run-time errors.

Effect The startup of the NonStop NET/MASTER MS subsystem is abandoned.

Recovery Use the File Utility Program (FUP) to copy the activity log to your terminal, as follows:

TACL> FUP COPY log-file-name,,a,no head

Examine the output to determine the reason for the failure. Rectify the problem and restart the NonStop NET/MASTER MS subsystem.

567

SYSTEM IS ALREADY STOPPING

Cause A SHUTDOWN or FSTOP command was received while the NonStop NET/MASTER Management Services (MS) subsystem was in the last stage of a shutdown.

Effect The NonStop NET/MASTER MS subsystem continues to complete the shutdown.

Recovery Informational message only; no corrective action is needed.

568

PROCESS process_name STOPPED

process_name

is the name of the stopped process.

Cause The control process stopped the process during shutdown.

Effect The process is stopped.

Recovery Informational message only; no corrective action is needed.

569

ALL PROCESSES HAVE STOPPED

Cause All NonStop NET/MASTER Management Services (MS) processes (including the control process) have been stopped, and shutdown is complete.

Effect All processes in the NonStop NET/MASTER MS subsystem are stopped.

Recovery Informational message only; no corrective action is needed.

570

UNABLE TO START ALL GMM PROCESSES

Cause One of the Global Memory Manager (GMM) processes could not be started during the initialization of the NonStop NET/MASTER Management Services (MS) subsystem, but the system requires all of them to be started. Common causes include the following:

The GMM object file is not present.
The GMM object file is secured such that it cannot be accessed by the NonStop NET/MASTER MS subsystem.
There are not enough system resources to run the process (such as disk swap space).

Effect Initialization of the NonStop NET/MASTER MS subsystem is stopped.

Recovery Examine the Event Management Service (EMS) log to determine the reason for the failure. After you have rectified the problem, restart the NonStop NET/MASTER MS subsystem.

571

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 Management Services (MS) subsystem, but the system requires all of them to be started. Common causes include the following:

The security exit object file is not present.
The security exit object file is secured such that it cannot be accessed by the NonStop NET/MASTER MS subsystem.
There are not enough system resources to run the process (such as disk swap space).

Effect The initialization of the NonStop NET/MASTER MS subsystem is stopped.

Recovery Examine the Event Management Service (EMS) log to determine the reason for the failure. After you have rectified the problem, restart the NonStop NET/MASTER MS subsystem.

572

UNABLE TO START ALL DSNM PROCESSES

Cause One of the Distributed Systems Network Management (DSNM) processes could not be started during the initialization of the NonStop NET/MASTER Management Services (MS) subsystem, but the system requires all of them to be started. Common causes include the following:

The DSNM object file is not present.
The DSNM object file is secured such that it cannot be accessed by the NonStop NET/MASTER MS subsystem.
There are not enough system resources (such as disk swap space) to run the process.

Effect The initialization of the NonStop NET/MASTER MS subsystem is stopped.

Recovery Examine the Event Management Service (EMS) log to determine the reason for the failure. After you have rectified the problem, restart the NonStop NET/MASTER MS subsystem.

573

PROCESS NOT NAMED

Cause During the startup of your NonStop NET/MASTER Management Services (MS) subsystem, a process that must be executed as a named process was started without a process name.

Effect The startup of the NonStop NET/MASTER MS subsystem is stopped.

Recovery If the process is the network control process (NCP), assign a name to the process using the NAME option in the RUN command and restart the NonStop NET/MASTER MS subsystem.

If the process is the Global Memory Manager (GMM), the process name is assigned by NCP and this error should not occur.

Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

574

INVALID BACKUP CPU

Cause During the startup of your NonStop NET/MASTER Management Services (MS) subsystem, a process was started with an invalid backup processor. The backup processor number cannot be higher than the highest processor number configured on your Tandem system.

Effect The startup of the NonStop NET/MASTER MS subsystem is stopped.

Recovery If the process is the network control process (NCP), assign a valid processor number for the backup NCP process in the RUN command.

If the process is the Global Memory Manager (GMM), assign a valid processor number for the backup GMM process using PARAM PROCESSCPU in the NonStop NET/MASTER MS configuration file.

After you have rectified the problem, restart the NonStop NET/MASTER MS subsystem.

575

PREMATURE TAKEOVER

Cause A primary NonStop NET/MASTER Management Services (MS) process failed before initialization completed. The backup process did not have enough information to enable the initialization to continue.

Effect The process abends and processing cannot be continued by NonStop NET/MASTER MS.

Recovery Examine the Event Management Service (EMS) log to determine the reason for the failure. After you have rectified the problem, restart the NonStop NET/MASTER MS subsystem.

If this problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

576

UNABLE TO READ STARTUP MESSAGE

Cause An input/output (I/O) error occurred when a NonStop NET/MASTER Management Services (MS) process was reading its startup message.

Effect The process abends and processing cannot be continued by NonStop NET/MASTER MS.

Recovery Examine the Event Management Service (EMS) log to determine the reason for the failure. After you have rectified the problem, restart the NonStop NET/MASTER MS subsystem.

If this problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

577

INCORRECT OS VERSION

Cause You attempted to start NonStop NET/MASTER Management Services (MS) on a Tandem system that was using a wrong version of the operating system. The NonStop NET/MASTER MS requires release D30.00 or later.

Effect The NonStop NET/MASTER MS subsystem is not started.

Recovery Install the correct operating system, then restart your NonStop NET/MASTER MS.

578

TOO MANY BACKUP TAKEOVERS

Cause A NonStop NET/MASTER Management Services (MS) process that ran as a process pair had to switch over to the backup process too many times, indicating an unstable processing environment.

Effect All NonStop NET/MASTER MS processes are stopped.

Recovery Examine the Event Management Service (EMS) log to determine the reason for the failure. After you have rectified the problem, restart the NonStop NET/MASTER MS subsystem.

If this problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

579

USER group-number,user-number AT HOMETERM home-term STARTED NCP objfile IN CPU cpu1:cpu2 config-file-info trace-info (backup-status)

`group‑number`,`user‑number`	is the user ID of the user that started NonStop NET/MASTER Management Services (MS).
`home‑term`	is the name of the home terminal for NonStop NET/MASTER MS.
`objfile`	is the name of the network control process (NCP) object file.
`cpu1`	is the number that identifies the processor in which the primary process of the NCP is executing.
`cpu2`	is the number that identifies the processor in which the backup process of the NCP resides.
`config‑file‑info`	is the string WITH CONFIGURATION FILE `filename` if a configuration file is provided, or the string WITHOUT CONFIGURATION FILE if no configuration file is provided.
`trace-info`	is the string AND TRACE `trace-value` if trace flags are specified in the RUN command that starts NonStop NET/MASTER MS. (Trace flags are used only under the direction of the Global Mission Critical Solution Center (GMCSC).)
`backup-status`	provides information on the backup process as follows: BACKUP PROCESS NOT RUNNING—The backup of the NCP control process cannot be started because the specified processor is not available. The backup process is automatically restarted when the processor becomes available. BACKUP PROCESS RUNNING—The NCP control process is executing with a backup process. NO BACKUP PROCESS—The NCP control process is executing without a backup process. NCP was run using the same processor for the primary and backup processes.

Cause The NonStop NET/MASTER MS subsystem is being started, and the message is displayed to provide startup information.

Effect The startup of the NonStop NET/MASTER MS subsystem continues.

Recovery Informational message only; no corrective action is needed.

580

WARNING: FILE SECURITY OF filename IS 'file-security'

`filename`	is the name of the licensed program object file.
`file‑security`	gives the security settings of the named file at the time of startup.

Cause During the startup of NonStop NET/MASTER Management Services (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 -O- or -U-.

Effect The startup of the NonStop NET/MASTER MS subsystem continues.

Recovery Secure the named file to either -O- or -U-.

582

WARNING: process-name FAILED TO RESTART PROCESS logical-name’ restart-count TIMES IN time-interval SECONDS, NO FURTHER RESTARTS

`process-name`	is the name of the NonStop NET/MASTER MS control process.
`logical-name`	is the logical name of the failed process.
`restart-count`	is the number of times a process failed to restart.
`time-interval`	is the time interval (in seconds) within which NCP failed to restart the process.

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.

Effect The failed process is not restarted.

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.

585

PRIMARY AND BACKUP OF process-name SWITCHED

process-name

is the name of the process affected.

Cause A PROCESS SWITCH command reversed the role of the primary and backup process of the NonSrop NET/MASTER MS process pair.

Effect The role of the primary and backup process of the pair is reversed.

Recovery Informational message only; no corrective action is needed.

586

BACKUP CPU OF process-name CHANGED FROM old-cpu TO new-cpu (backup-status) WITH command-effect EFFECT

process-name

is the name of the process.

old-cpu

is the number that identifies the former backup of CPU.

new-cpu

is the number that identifies the newly assigned backup CPU.

backup-status

provides the changed status of the backup process as follows:

BACKUP PROCESS RUNNING	The process is executing with a backup CPU.
NO BACKUP PROCESS	The process is executing without a backup process or, if `command-effect` is PENDING, will execute without a backup process.

command-effect

provides information about the effect of the command according to the DEFER option:

IMMEDIATE	The backup process executes immediately in the new CPU.
PENDING	The backup process is created in the new CPU when the current backup process stops.

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).

Effect The CPU for the backup process is altered according to command-effect.

Recovery Informational message only; no corrective action is needed.

750

NO SECURITY EXIT(S) ARE AVAILABLE

Cause The NonStop NET/MASTER Management Services (MS) subsystem was being started but could not use any of the configured security exits; or the file security subsystem attempted to access a exit that was previously running and found that all exists had become unavailable.

Effect If the error occurs during system initialization, the NonStop NET/MASTER MS subsystem terminates. If the error occurs while the system is running, all future security requests are denied. Users who are currently logged on are allowed to continue. When an attempt to use a security exit fails, message 752 is displayed.

Recovery If the security exits are defined in the configuration file, ensure that they are running. If you want to use the security subsystem of the NonStop NET/MASTER MS subsystem, remove the security exits from the configuration file. Use the SHUTDOWN command to shut down the NonStop NET/MASTER MS subsystem. Once the shutdown is complete, the NonStop NET/MASTER MS subsystem must be restarted to reestablish the security environment.

751

THERE ARE DIFFERENT TYPES OF SECURITY EXITS

Cause The configuration file contains more than one security exit. When the NonStop NET/MASTER Management Services (MS) subsystem attempted to access the exits, they were found to be of different types. Security exits must be of the same type.

Effect This error occurs during system initialization. The NonStop NET/MASTER MS subsystem terminates.

Recovery Ensure that the security exits in the configuration file are of the same type.

752

UNABLE TO READ/WRITE/OPEN SECURITY EXIT process_name, FS ERROR errno

`process_name`	is the name of the security exit process.
`errno`	identifies a file-system error.

Cause The application was not able to read from, write to, or open a security exit.

Effect If the error occurs during system initialization, the NonStop NET/MASTER Management Services (MS) subsystem continues as long as there are other exits available. If no other exits are available, then the NonStop NET/MASTER MS subsystem terminates. If the error occurs while the system is running, the security request that caused the error is denied and all future requests are routed to other security exit processes. If all security exits had errors, all future requests will be denied. Users who are currently logged on are allowed to continue. NNM operator message 750 is displayed if all security exits have become unavailable.

Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

753

INVALID TYPE OF SECURITY EXIT PROVIDED process_name

process_name

is the name of the security exit process. A security exit must be of one of the following types:

File open
Full
Full with file open
Password validation
Password validation with file open

Cause The installation provided a nonstandard security exit. When the NonStop NET/MASTER Management Services (MS) subsystem attempted to access the exit, the exit was found to be of an unsupported type.

Effect This error occurs during system initialization. The NonStop NET/MASTER MS subsystem continues as long as there are other exits available. If no other exits are available, then the NonStop NET/MASTER MS subsystem terminates.

Recovery Ensure that all security exits in the configuration file are of the correct type.

754

SECURITY EXIT process_name RETURNED WRONG VALUE exit_code

`process_name`	is the name of the security exit process.
`exit_code`	is an invalid return code from the security exit.

Cause The installation provided a nonstandard security exit. When the NonStop NET/MASTER Management Services (MS) subsystem attempted to use the exit, the exit set an invalid return code. This is a user programming error.

Effect If the error occurs during system initialization, the NonStop NET/MASTER MS subsystem continues as long as there are other exits available. If no other exits are available, then the NonStop NET/MASTER MS subsystem terminates. If the error occurs while the system is running, the security request that caused the error is denied and all future requests are routed to other security exit processes. If all security exits had errors, all future requests will be denied. Users who are currently logged on are allowed to continue.

Recovery Correct the user-supplied security exit so that only the proper return codes are used.

755

SECURITY EXIT DID NOT RETURN USER'S PROFILE process_name

process_name

is the name of the security exit process.

Cause The installation provided a nonstandard security exit. During a security check, the NonStop NET/MASTER Management Services (MS) subsystem 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.

Recovery Correct the user-supplied security exit so that a user profile is returned when expected.

980

shutdown-command EXECUTED ON TERMINAL device-name

device-name

identifies the terminal from which the utility was executed.

Cause An FSTOP, SHUTDOWN, or SHUTDOWN $ABEND$ command (shutdown-command) was issued to shut down a NonStop NET/MASTER MS system externally by using the NNM shutdown utility.

Effect If the command SHUTDOWN $ABEND$, shutdown starts immediately, irrespective of whether the target NonStop NET/MASTER MS system is initializing or is running already.

If the command is FSTOP, shutdown starts immediately only if the target NonStop NET/MASTER MS system is running already. If the system is initializing, FSTOP waits until the system is running, and then executes the shutdown.

If the command is SHUTDOWN, the target NonStop NET/MASTER MS system prevents further logons and waits for all users to log off before starting the shutdown.

Recovery Informational message only; no corrective action is needed.

985

command EXECUTED BY userid

`command`	is the name of the command.
`userid`	is the name of the user ID.

Cause The command has executed successfully.

Effect The command is successful.

Recovery Informational message only; no corrective action is needed.

990

productname - productnumberversion - (releasedate),copyrighttext

Cause This message contains the copyright information and appears during the startup of a NonStop NET/MASTER Management Services (MS) subsystem.

Effect The copyright information is retrieved and displayed.

Recovery Informational message only; no corrective action is needed.

1400

process_name ABENDING AT P=%paddr, TRAP=trapid,filename [line.line]

`process_name`	is the name of the failed Global Memory Server (GMS) process.
`paddr`	is the memory address of the code that failed.
`trapid`	is an ID to help the Global NonStop Solution Center (GNSC) identify the problem.
`filename`	is the file name of the source code that caused the problem.
`line.line`	is the line number within the source file where the problem occurred.

Cause An internal check in a GMS process has failed, causing the GMS process to abend.

Effect The backup process of the failed GMS process takes over, and the NonStop NET/MASTER Management Services (MS) subsystem continues normal operation.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable
ABEND dump file
Activity log that contains the events leading up to the failure of the GMS process

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

1401

process_name ABENDING AT P=%paddr, TRAP=trapid,trapname

`process_name`	is the name of the failed Global Memory Server (GMS) process.
`paddr`	is the memory address of the code that failed.
`trapid`	is an ID to help the Global NonStop Solution Center (GNSC) identify the problem.
`trapname`	is the name of the trap that occurred.

Cause A system trap has occurred in the GMS process.

Effect The backup process of the failed GMS process takes over, and the NonStop NET/MASTER Management Services (MS) subsystem continues normal operation. If a backup does not exist, NonStop NET/MASTER Management Services (MS) stops.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable
ABEND dump file
Activity log that contains the events leading up to the failure of the GMS process

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

1402

WARNING: backup-status

backup-status

provides information on the backup processes as follows:

BACKUP PROCESS NOT RUNNING—The backup of a Global Memory Manager (GMM) process cannot be started because the backup processor is not available.

NO BACKUP PROCESS—The GMM process is executing without a backup process. The PROCESSCPU startup parameter in your NonStop NET/MASTER Management Services (MS) configuration file specified the same processor for the primary and backup processes.

Cause The backup process of GMM was not running. This is a warning message indicating that the GMM process cannot be recovered if the primary process is stopped.

Effect The NonStop NET/MASTER MS subsystem continues normal operation.

Recovery Because vital processing information is stored and handled by GMM processes, failure of a GMM process causes the NonStop NET/MASTER MS subsystem to stop if a backup process does not exist.




	CAUTION: Integrity of information cannot be guaranteed if the system is stopped inadvertently.

Running NonStop NET/MASTER MS without a backup GMM process is not recommended in a production environment.

If this message is displayed on a production system, specify different processors for the PROCESSCPU startup parameter in your NonStop NET/MASTER MS configuration file and restart the system.

1451

UNABLE TO OPEN DSNM COMMAND SERVER process_name (Error errno)

`process-name`	is the name of the process that caused the error (this is one of the CIP or CMDSRv process names specified through the PARAM command or the default if none is specified).
`errno`	is the Guardian file-system error number.

Cause An OPSYS command was issued but the NonStop NET/MASTER MS system could not open the command server of the DSNM subsystem.

Effect The command is ignored.

Recovery Refer the message to your system manager. The manager should:

Ensure that the command server of DSNM is operational
Use the error number to determine the appropriate action to take

1452

UNABLE TO COMMUNICATE WITH COMMAND SERVER process_name (Error errno)

`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.

Cause An OPSYS command was issued but the NonStop NET/MASTER MS system could not communicate with the command server of the DSNM subsystem.

Effect The command is ignored.

Recovery Refer the message to your system manager. The manager should:

Ensure that the command server of DSNM is operational
Use the error number to determine the appropriate action to take

1473

UNABLE TO OPEN process-name TO CANCEL UTILITY SESSION (ERROR errno)

`process-name`	is the name of the process that caused the error. This is one of the CIP server processes specified by using the PARAM command, or the default CIP server proess if none is specified.
`errno`	is the Guardian file-system error number.

Cause NonStop NET/MASTER MS system could not open the conversational interface process (CIP) to cancel utility sessions started by CIP.

Effect Utility sessions started by the CIP cannot be canceled.

Recovery Refer the message to your system manager, who should:

Ensure that the CIP server for DSNM is operational
If necessary, manuall stop the utilities started by the CIP
Use the error number to determine the appropriate action to take

1474

UNABLE TO SEND COMMAND TO process-name TO CANCEL UTILITY SESSION (ERROR errno)

`process-name`	is the name of the process that caused the error. This is one of the CIP server processes specified by using the PARAM command, or the default CIP server proess if none is specified.
`errno`	is the Guardian file-system error number.

Cause NonStop NET/MASTER MS could not communicate with the conversational interface process (CIP) to cancel utility sessions started by the CIP.

Effect Utility sessions started by the CIP cannot be cancelled.

Recovery Refer the message to your system manager, who should:

Ensure that the CIP server for DSNM is operational
If necessary, manuall stop the utilities started by the CIP
Use the error number to determine the appropriate action to take

1507

NNM LOG SUBSYSTEM DOES NOT HAVE ANY AVAILABLE LOG FILES.error

error

identifies a file-system error and the name of the file that is in error.

Cause The LOG subsystem was unable to log event messages. Possible causes include the following:

The LOGWRAP system parameter has a value of NO, and all declared log files were used once already.
The log files are secured from access by the LOG subsystem, in which case the reason of the error is returned.

Effect A warning message is sent to the Tandem system collector.

Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Use the SHOW SYSPARMS=LOG* command to determine the number of log files in the NonStop NET/MASTER Management Services (MS) subsystem. If there are fewer than nine, you can declare more files using the SYSPARMS LOGFILEn=filename command. If LOGWRAP is set to NO, you can use the SYSPARMS LOGWRAP=YES command to allow the log files to be reused.

1544

LOG RECORD LENGTH (n BYTES) EXCEEDED MAXIMUM m BYTES, NO RECORD LOGGED

`n`	is the log record length in bytes.
`m`	is the maximum log record length in bytes.

Cause NonStop NET/MASTER Management Services (MS) was unable to log an operator message. The record length of the message exceeded the maximum length allowed for an activity log record.

Effect A warning message is sent to the Event Management Service (EMS) collector ($0). The operator message is not logged in the activity log file.

Recovery Reduce the length of the operator message to less than m bytes. For example, split the message into two shorter messages.

2188

BAD BACKUP CPU NUMBER IN STARTUP MSG: 'text'

text

is the string of characters interpreted as the backup processor number. This is defined in your NonStop NET/MASTER Management Services (MS) configuration file.

Cause The first symbol in the parameter string portion of the startup message to the security exit was not acceptable as a backup processor number. The symbol either was not all digits, was a number less than 0 or greater than 15, or was the same number as the primary processor number.

Effect The security exit abends, preventing the NonStop NET/MASTER MS subsystem from starting up.

Recovery Contact your system manager. The system manager should ensure that in the configuration file, the PARAM PROCESSPARAM command for the security exit contains a valid backup processor number. Correct if necessary.

2189

BAD param FILENAME IN STARTUP MSG: 'text'

`param`	is the name of the startup parameter, associated with the Utility Access database files (UACUTIL, UADUTIL, UACAUTH, and UADAUTH), that tells you which file name was being processed. This is defined in your NonStop NET/MASTER Management Services (MS) configuration file.
`text`	is a string of characters being interpreted as a file name.

Cause The second through fifth symbols in the parameter string portion of the startup message to the security exit should represent the names of the Utility Access database files. This message indicates that one of these file names is invalid.

Effect The security exit abends, preventing the NonStop NET/MASTER MS subsystem from starting up.

Recovery Contact your system manager. The system manager should ensure that in the configuration file, the PARAM PROCESSPARAM command for the security exit contains valid file names. Correct if necessary.

2190

OPEN ERROR errno ON FILE filename

`errno`	identifies a file-system error.
`filename`	is the name of the file on which the error occurred.

Cause A file-management error occurred during an attempt to open a file in the security exit server.

Effect The security exit abends, preventing the NonStop NET/MASTER Management Services (MS) subsystem from starting up.

Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

2191

proc ERROR errno ON FILE filename (name type)

`proc`	is the name of the system procedure that encountered the error: AWAITIO, KEYPOSITION, or READUPDATE.
`errno`	identifies a file-system error.
`filename`	is the name of the file on which the error occurred.

If the error occurred on one of the database files:

`name`	is the name of the utility being inquired about.
`type`	is the utility type: O (OPSYS) or P (PROGRUN).

Cause A file-management error occurred during an attempt to access a file in the security exit server.

Effect The security exit denies authority for whatever request it was trying to evaluate when the error occurred.

Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

2192

CHECKPOINT ERROR err1,err2

`err1`	is the upper half of the CHECKPOINT error code.
`err2`	is the lower half of the CHECKPOINT error code.

Cause An error has occurred on a checkpoint in the security exit server.

This message is generated only when err1 indicates an internal error or is an unrecognized code. The message represents a coding error in the security exit.

Effect The security exit abends. If there is only one security exit, there is no longer any control over who can update the utility definitions, and all OPSYS SEND and PROGRUN utility-name commands are disabled.

Recovery Shut down and restart the NonStop NET/MASTER Management Services (MS) subsystem to restore normal performance.

Contact the Global NonStop Solution Center (GNSC) about the checkpoint error and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

2193

CHECKOPEN ERROR errno ON filename

`errno`	identifies a file-system error.
`filename`	is the name of the file that caused the error.

Cause An error occurred during an open of files in the backup process of the security exit server.

Effect The security exit stops its backup if the backup is not already stopped. Authorization functions are unaffected, but no backup is available to take over if the processor running the security exit fails. The security exit attempts to restart a backup.

Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

2194

BACKUP TAKEOVER, reason

reason

is one of the following:

PRIMARY ABENDED	The security exit has abended.
PRIMARY CPU FAILED	The processor running the security exit has failed.
PRIMARY STOPPED	The security exit has stopped.

Cause The backup process of the security exit server has taken over.

Effect Authorization functions are unaffected, but no backup is created if the processor running the security exit fails. The security exit attempts to restart a backup.

Recovery If a processor fails, try to get it reloaded.

2195

BACKUP FAILED, ERROR errno

errno

identifies a file-system error.

Cause The backup process of the security exit process has failed.

Effect Authorization functions are unaffected, but no backup is created if the processor running the security exit fails. The security exit attempts to restart a backup.

Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If a processor fails, try to get it reloaded.

2196

BACKUP CREATE ERROR err1,err2

`err1`	is the upper half of the NEWPROCESS error code.
`err2`	is the lower half of the NEWPROCESS error code.

Cause The security exit server got an error while trying to start its backup process.

Effect Authorization functions are unaffected, but no backup is available to take over if the processor running the security exit fails. The security exit attempts to restart a backup.

Recovery See Appendix C, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

2197

BAD DATABASE RECORD: errtext (name type filename)

errtext

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.

Cause Something is wrong with one of the records in the Utility Access database. This message is the result of an internal error in the database maintenance panels.

Effect The security exit denies authority for the request it was trying to evaluate when the error occurred. The security exit should continue to process requests normally.

Recovery Make a copy of the indicated file, then restore the file from a backup or delete the entries for the utility and enter them again. If you have modified the database maintenance panels, check your changes carefully.

2198

TOO MANY 'SAME AS' referrals for name type

`name`	is the name of the utility.
`type`	is the utility type in the initial request: O (OPSYS) or P (PROGRUN).

Cause More than five command sets were examined in one request due to the use of the “Same as” field in the definitions. This is a protection against a circular referral causing the security exit server to loop.

Effect The security exit denies authority for the request it was trying to evaluate when the error occurred. The security exit should continue to process requests normally.

Recovery Use the command set browse function to examine the “Same as” referrals starting with the command set named in the message. If you find a looped chain, correct it. If the chain is valid but is just too long, shorten it by making the referrals more direct.

2199

BAD SECURITY EXIT REQUEST errtext

errtext

identifies what is wrong and is one of the following:

BAD COMMAND AUTHORITY NUMBER: “text”

BAD FILENAME IN FILE OPEN REQUEST: “text”

BAD MDO

BAD REQUEST TYPE: “text”

BAD USERID: “text”

Cause An invalid request was sent to the security exit server. This could be due to an error in the OPSYS or PROGRUN Network Control Language (NCL) procedure that makes it construct the request incorrectly, or it could be an error elsewhere.

Effect The security exit denies authority for the request it was trying to evaluate when the error occurred. It should continue to process requests normally.

Recovery If you have customized the OPSYS or PROGRUN NCL procedure in any way, examine your changes carefully.

2807

ERROR 2 ATTEMPTING TO TAKE BREAK ON TERMINAL terminal-name

terminal-name

is the physical name of the terminal.

Cause NonStop NET/MASTER MS was trying to open a terminal and issued a SETPARAM 3 to take a break. The SETPARAM call returned Guardian file error 2 (not implemented).

Effect The terminal is opened but the behavior of the BREAK key is undefined.

Recovery Refer the message to your system manager. The system manager should contact the Global Mission Critical Solution Center (GMCSC), providing the device type of the terminal.

2808

INCORRECT OLDPARMS SIZE size FOR SETPARAM 3 ON TERMINAL terminal-name

`size`	is the size returned by SETPARAM.
`terminal-name`	is the physical name of the terminal.

Cause NonStop NET/MASTER MS was trying to open a terminal and issued a SETPARAM 3 to take break. The SETPARAM call returned an incorrect size for the old break parameters.

Effect The terminal is opened but the behavior of the BREAK key is undefined.

Recovery Refer the message to your system manager. The system manager should contact the the Global Mission Critical Solution Center (GMCSC), providing the device type of the terminal.