|
|
|
Reason:
The MAI feature failed to initialize because the module specified could not be loaded. This message indicates that the MAI feature has not been properly installed.
System Action:
No MAI functions will be available.
User Action:
Review the SOLVE installation process. The indicated load module should be made available in a load library accessible to SOLVE.
Reason:
The MAI feature failed to initialize because there was insufficient storage.
System Action:
No MAI functions will be available.
User Action:
SOLVE should be restarted in a larger region or partition.
Reason:
The MAI Extended Function (MAI/EF) feature failed to initialize because the nominated module could not be loaded. This message indicates that the MAI/EF feature has not been properly installed.
System Action:
No MAI/EF functions will be available.
User Action:
Review the SOLVE installation process. The indicated load module should be available in a load library accessible to SOLVE.
Reason:
The MAI/NTS interface failed to initialize because the nominated module could not be loaded. This message indicates that the MAI feature has not been properly installed.
System Action:
The MAI/NTS interface is unavailable. NTS will not be able to correlate logical terminal and physical terminal sessions.
User Action:
Review the SOLVE installation process. The indicated load module should be available in a load library accessible to SOLVE.
Reason:
The MAI/FS NCL interface failed to initialize because the nominated module could not be loaded.
System Action:
The MAI NCL verb set is unavailable. MAI/FS functions will not be usable.
User Action:
This message indicates that the MAI feature has not been properly installed. The indicated load module should be available in a load library accessible to SOLVE.
Reason:
Operand xxxxx entered as part of an MAILOGON command is not recognized as a valid operand.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
Operand xxxxx entered as part of an MAILOGON command is invalid.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An MAILOGON command was entered but no target application name was specified.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An MAILOGON command was entered but the target application name specified was not valid as the name of a VTAM APPL definition.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An MAILOGON command specified an ID to be used for the session that was already in use as the ID of another MAI-OC session from the same Operator Control Services window. If the ID= parameter was not specified on the MAILOGON command it defaults to the target application name.
System Action:
The command is rejected.
User Action:
Select another ID and retry. The SHOW MAI command will display existing MAI sessions and their IDs.
Reason:
A lack of storage prevented establishment of an MAI-OC session following entry of a valid MAILOGON command.
System Action:
The command is rejected.
User Action:
Retry. If the problem persists increase the SOLVE region size.
Reason:
Confirms that the system has accepted a valid MAILOGON command and will attempt to establish the session.
System Action:
Session establishment starts.
User Action:
None.
Reason:
An MAISEND command was entered without any operands. The MAISEND command must be followed by the ID of the session over which data is to be sent.
System Action:
The command is rejected.
User Action:
Re-enter the command specifying a session ID.
Reason:
An MAISEND command specified a session ID that is invalid or out of range. The session ID must be a 1 - 8 character string.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An MAISEND command was entered requesting that data be sent on an MAI-OC session, but no session was located that has the specified ID.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An MAISEND command was entered requesting that data be sent on an MAI-OC session, but the session is temporarily logically "locked" because the target application is due to send a response to an earlier message. This is functionally equivalent to the keyboard of a real terminal being locked.
System Action:
The command is rejected, the data is not sent to the application.
User Action:
Retry the command. The SHOW MAI command may be used to determine when the session becomes available for further input. In most situations the application will be ready to receive further data after it has responded to the previous send.
Reason:
An MAISEND request has specified data greater than the Request Unit size and chaining is not supported.
System Action:
The data is truncated at the RU size and this warning message is logged.
User Action:
Review the session characteristics. It may be possible to modify the LOGMODE to specify larger RU sizes or to support chaining. Also the use of newline characters may be suppressed by use of the MAIONL system parameter.
Reason:
An MAIDISC or MAIINT command was entered but operand xxxxx was not recognized as a valid operand.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An MAIDISC or MAIINT command was entered but operand xxxxx was invalid.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An MAIDISC or MAIINT command was entered but no session ID included to specify the session on which data is to be sent.
System Action:
The command is rejected.
User Action:
Enter a session ID.
Reason:
An MAIDISC or MAIINT command was entered that specified an invalid session ID. The session ID must be a 1 - 8 character string.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An MAIDISC or MAIINT command was entered from an OCS window but no MAI sessions have been established from that window.
System Action:
The command is rejected.
User Action:
Enter the command from the applicable window or restart the required MAI-OC session.
Reason:
An MAIDISC or MAIINT command was entered specifying a session ID not in use for any MAI-OC sessions that exist from this window.
System Action:
The command is rejected.
User Action:
Correct the session ID and retry.
Reason:
An MAIINT command was entered requesting that a CNCL be sent on the specified session to cancel the incoming data stream, but no data was being received on the specified session when the command was entered. The MAIINT TYPE=CNCL command is accepted only if a chain of data is being received at the time.
System Action:
The command is rejected.
User Action:
None.
Reason:
An MAIINT command was entered before an earlier MAISEND had been completed.
System Action:
The command is rejected.
User Action:
Retry. This should be a temporary condition.
Reason:
Confirms that a valid MAIDISC command has been entered.
System Action:
Session termination is started.
User Action:
None.
Reason:
An MAIINT TYPE=ATTN command was entered and an ATTN will be presented on the specified session.
System Action:
None.
User Action:
None.
Reason:
An MAIINT TYPE=CNCL command was entered while data was being received on the specified session.
System Action:
The SNA CANCEL command will be presented on that session to terminate the output stream.
User Action:
None.
Reason:
The heading line of a display presented in response to a SHOW MAI or SHOW MAI=ALL command.
System Action:
None.
User Action:
Refer to help for message N50802 for details.
Reason:
This is a detail message displayed for each MAI session in response to a SHOW MAI command. This detail line follows the heading line message N50801. The items in this detail line are:
sessid The session ID of the session being displayed on this line
con YES, NO, or LCK. Indicates whether the session is currently established, and if so, whether it is logically locked. The LCK status indicates the LU cannot send to the application. The LU may be in receive state or, for MAI/FS, the keyboard has not been unlocked by the application
appl The name of the target application
lu The name of the LU being used by MAI for this session
i The value of the (optional) newline character associated with this MAI-OC session, or an indicator (Y or N) as to whether an MAI-FS session is ACB sharing
wait Shows the value of the WAIT= option as specified when the session was created
stat When the session is active (CON=YES/LCK), this field shows the current status of the session in SNA terms. The following values are defined:
SEND - The LU is ready to send to the application.
RCV - The LU is ready to receive from the application.
STBY - The LU is in contention state.
DRWT - The LU is waiting for a response. - - A state transition is in progress or the session is not operating as an LU type 2. When the session is not active (CON=NO), the following values are defined:
ACBW - Waiting for ACB open to complete
BNDW - Waiting for BIND from the application
UNBW - Waiting for UNBIND from the application
TRMW - Waiting for termination (ACB close/MAIEX02)
brac Indicates the current session bracket state as STBY, INB, BB, or BBP, where the meaning of these terms is as used in the IBM 3767 Component Description Manual. The bracket states are for diagnostic purposes only. They should be recorded for documenting any problems encountered with the operation of MAI sessions.
out Shows, for an MAI-FS session, if data is waiting to be displayed on the session ( out =YES).
userid For SHOW MAI=ALL, the userid owning the MAI session. For an MAI-OC session created from EASINET, this may be blank. For SHOW MAI=OWN, this is the window that owns the session and may be:
THIS - For this window
OTH/WIND - For another window within the same region
OTH/SESS - For another region for the same userid
OCSID - The ID of the window as set by an OCSID command
text Additional descriptive text denoting some special condition. The following values are defined:
DISC - The user has disconnected.
LOCK - The user's terminal is currently locked.
END - The user's region has been terminated and the session is in the process of terminating. A session script may be running in END mode.
System Action:
None.
User Action:
None.
Reason:
A SHOW MAI command was entered but no MAI sessions of the specified type are established. The text `FOR USERID uuuuuuuu' is not included for a SHOW MAI=ALL or SHOW MAI=userid command.
System Action:
None.
User Action:
None.
Reason:
Issued in response to a STATUS command to indicate that this SOLVE system is configured with the MAI feature of the specified level.
System Action:
None.
User Action:
None.
Reason:
The content of this message is identical to message N50802, but it is displayed in high intensity to show that some output is waiting on the MAI-FS session.
System Action:
None.
User Action:
None.
Reason:
Issued in response to a SHOW MAI command.
ddddd is the number of MAI sessions displayed.
ttttt current total sessions
mmmmm maximum number of sessions ever
jjjjj total number of jumps that have been made to MAI-FS sessions.
System Action:
None.
User Action:
None.
Reason:
The heading line of a display presented in response to a SHOW MAISTAT command.
System Action:
None.
User Action:
None.
Reason:
A detail message issued in response to a SHOW MAISTAT command. Refer to the command help for SHOW MAISTAT for further explanation.
System Action:
None.
User Action:
None.
Reason:
Issued in response to a SHOW MAISTAT command. This line summarizes the number of active MAI-FS sessions and the maximum that have been active at the same time. cccccc'is the number of session jumps that have been processed.
System Action:
None.
User Action:
None.
Reason:
Issued in response to a SHOW MAISTAT command. This message details the number of MAI-OC sessions currently active and the maximum that have been active at the same time.
System Action:
None.
User Action:
None.
Reason:
The heading line from a SHOW MAISTAT=ACTIVITY command.
System Action:
None.
User Action:
For details, refer to the online help for message N50814.
Reason:
This is a detail line displayed in response to a SHOW MAISTAT=ACTIVITY command. It follows the headline N50813 message. The fields are:
task Identifies the MAI task. SERV is the Service subtask responsible for ACB open/close and communicating with the MAIEX02 exit. A number in the range 1 to 16 indicates a session subtask responsible for communication with the applications.
activity The current function being performed by the task. A value of IDLE indicates the task is waiting for work. Other values are associated with a particular session and the fields luname, userid, sessid and interval are set. These values are:
BUSY A session event is being processed. OPEN_ACB An Open has been issued for the virtual terminal LU. CLOSE_ACB A Close has been issued for the virtual terminal LU. EX02_START_CALL MAIEX02 has been driven for session start. EX02_OPEN_CALL MAIEX02 has been driven for ACB open. EX02_END_CALL MAIEX02 has been driven for session end. TERMINATING The subtask is processing a terminate request. SETLOGON The virtual terminal LU is being modified to allow sessions. REQUEST_SESSION A session with the application is being requested. OPEN_SECONDARY A session with the application is being established. RECEIVE A Receive is in progress for the session. RESETSR A Terminate Receive processing is in progress. TERMINATE_SESSION A Terminate Session request is in progress. SEND_RESPONSE A response is being sent to the application. SEND_SHUTC A Shutdown Complete is being sent to the application. SEND_DATA Data is being sent to the application. SEND_SIGNAL SEND_NULL A 0 length data RU is being sent to the application.
luname The LU representing the virtual terminal.
userid The user ID owning the session.
sessid The MAI session ID.
interval The time interval since the activity started.
System Action:
None.
User Action:
Use the activity display to determine the status of MAI tasks. A time period of any significance (for example, greater than 1 second) indicates that a task has been delayed by a call to an external function. This may be the communications subsystem (VTAM) or a user exit.
If it is a communications related function (for example, ACB open/close), then a display of the LU (that is, D luname,E) may reveal the cause. You may diagnose delays caused by system contentions by issuing the system command 'D GRS,C'.
Reason:
This is a heading line displayed in response to a SHOW MAI LIST=ALL command and follows the headline N50801 message.
System Action:
None.
User Action:
Refer to the N50816 message for details about the corresponding session.
Reason:
This is a detail line displayed in response to a SHOW MAI LIST=ALL command, that corresponds to the headline N50815 message. The fields are:
P1 - The name of the DEFLOGON used to start the session
P2 - The NCL process ID if a script is running for the session
P3 - The amount in bytes of storage currently used for datastream and image buffers
System Action:
None.
User Action:
You can issue a SHOW DEFLOGON= P1 to display the DEFLOGON details. Use SHOW NCL ID= P2 to display the script.
Reason:
This is a summary line displayed in response to a SHOW MAI command. P1 is the average storage used for datastream and image buffers for the sessions previously displayed.
System Action:
None.
User Action:
None.
Reason:
An MAI-OC session is terminated because of an abend in the subtask associated with the session.
System Action:
The MAI-OC session is terminated.
User Action:
Report the abend condition to your systems administrator or installation help desk facility.
Reason:
Confirms successful disconnection of the specified MAI-OC session.
System Action:
None.
User Action:
None.
Reason:
An MAI-OC session created in response to an MAILOGON command that specifies WAIT=PERM has terminated before session creation was completed, or the MAIEX02 negated the PERM option. The WAIT=PERM option is therefore cancelled to avoid the possibility of recursive session failures.
System Action:
None.
User Action:
Re-issue MAILOGON if another MAI-OC session attempt is required.
Reason:
Indicates that an MAI-OC session has terminated but has been queued for re-establishment when the target application re-opens it. This is the result of WAIT=PERM having been specified on the original MAILOGON command that was entered to start the session.
System Action:
None.
User Action:
The MAI-OC session cannot be used until the application re-establishes the session. When the session is restarted the standard salutation message from the target application will be displayed. Use the MAIDISC command to terminate the pending MAI-OC session if it is no longer required.
Reason:
Indicates that the specified MAI-OC session has been disconnected unexpectedly. The following message(s) indicate the nature of the error.
System Action:
The session is terminated, and queued for re-establishment if WAIT=PERM was specified on the original MAILOGON command and if the session had been successfully established. Subsequent messages detail the failure condition.
User Action:
None.
Reason:
A SYSPARMS MAIMDTAB=xxxxxxxx or SYSPARMS MAIEX03=xxxxxxxx command has failed because the load module could not be loaded.
System Action:
The command is ignored.
User Action:
Check that the load module is in a load library (core-image library) that is defined to SOLVE.
Reason:
A SYSPARMS MAIMDTAB=NO or SYSPARMS MAIEX03=NO command has failed because the load module deletion was rejected.
System Action:
The command is ignored.
User Action:
Contact your systems administrator.
Reason:
A SYSPARMS MAIMDTAB=xxxxxxxx command has failed because the load module is not recognisable as a mode table.
System Action:
The command is ignored.
User Action:
Check that the correct module name has been specified and that the module was correctly assembled and linked.
Reason:
A SYSPARMS operand ( P1 ) was specified when another SYSPARMS operand ( P2 ) was previously specified. These operands are mutually exclusive.
System Action:
The command is ignored.
User Action:
If you want this operand, you must use the SYSPARMS P2 command to clear the conflicting operand. For example, SYSPARMS MAIEX03=NO clears the MAIEX03 operand.
Reason:
Indicates that errors were encountered during operation of an MAI-FS session that caused the session to fail. Other messages will follow to indicate the nature of the error.
System Action:
The session ends.
User Action:
Determine the cause of the failure from the other error messages. All these messages appear on a 'session end' panel, from which a jump can be made to another session.
Reason:
An MAI-FS session subtask abended with the specified operating system abend code.
System Action:
All sessions managed by the abending subtask end.
User Action:
Record the error messages and report the failure to your installation help desk facility.
If necessary a systems administrator should save the system abend dumps, activity logs and formatted dump output, and report the problem to your product support representative.
Reason:
The MAI-FS session, ID P1 , with the application P2 has started using ACB P3 . If a script procedure has been named for the session then P4 is the name of the script.
System Action:
The session is started.
User Action:
None. This message is written to the activity log only.
Reason:
The MAI-FS session, ID P1 , with the application P2 has been started.
System Action:
The session begins operation.
User Action:
None.
Reason:
The MAI-FS session, ID P1, with the application P2 has ended, and was using ACB P3.
System Action:
The session ends.
User Action:
None.
Reason:
This message indicates the VTAM return code and feedback information associated with the failure of MAI-FS VTAM operations. This message will follow a message indicating the general error condition.
System Action:
None.
User Action:
Refer to the appropriate VTAM Programming Manual for explanation of the error codes.
Reason:
The MAI-FS session, ID P1 , was started with the WAIT=YES option, and the application P2 is not currently available.
System Action:
A session request is issued and the session is maintained pending a BIND from the application.
The session will be created when the application becomes active and requests a session with the MAI Node Name (LU), The panel on which this message is displayed will remain in the session circle.
User Action:
Wait until the application starts the session. Remove the Waiting Panel from the session circle by using the Hide function ('H' session command or menu selection).
The session environment can be destroyed by using the Cancel function ('C' session command or menu selection).
Reason:
An MAI-FS session has terminated either before session creation was completed, as a result of a session cancel or due to errors. The session will not be automatically restarted.
System Action:
None.
User Action:
Review the associated session termination messages. If necessary report the failure to your system administrator.
Reason:
The MAI-FS session has ended but has been queued for re-establishment when the target application re-opens it. This is as a result of the specification of the RESTART option when the session was created.
System Action:
The session environment is maintained.
User Action:
The `session wait' panel will remain in the session circle until the session is re- established. The waiting session may be terminated by using the cancel option if required.
Reason:
An MAI-FS session has been cancelled because insufficient storage was available to operate it.
System Action:
The session is cancelled.
User Action:
Notify your installation help desk of the problem. If necessary re-establish the session.
Your systems administrator may need to increase the SOLVE region or partition size.
Reason:
An MAI-FS session could not be started because there was insufficient storage to start a new subtask.
System Action:
The session request is refused.
User Action:
Notify your installation help desk of the problem. If necessary attempt to re-establish the session.
Your systems administrator may need to increase the SOLVE region or partition size.
Reason:
The MAI-FS session has been cancelled because a subtask managing another session that uses the same VTAM ACB has abended.
System Action:
The session is cancelled.
User Action:
Notify your installation help desk of the problem. If necessary re-establish the session.
Your systems administrator should investigate the cause of the session subtask abend.
Reason:
An MAI session has terminated due to errors. This message is displayed on the session end panel. Message N51501 and other messages also appear on the panel and are logged indicating the errors that occurred.
System Action:
The session end panel is displayed. The session resources will be freed once the end panel is acknowledged.
User Action:
Review the error messages that are associated and notify your installation help desk if appropriate. Press a session jump key, enter a skip command or press the ENTER key to acknowledge the end panel.
Reason:
An MAI session has ended. This message is displayed on the session end panel.
System Action:
The session end panel is displayed. If the session is not eligible for restart the session resources will be freed when the end panel is acknowledged.
User Action:
Acknowledge the session end panel by pressing a session jump key, entering a skip command or pressing the ENTER key.
Reason:
An MAI session has been initiated but the required application is not currently active. This message appears on the session waiting panel. The target application will initiate the session when it becomes available.
System Action:
The session waiting panel is displayed.
User Action:
Acknowledge the session waiting panel by pressing a session jump key, entering a skip command or pressing the ENTER key.
Reason:
An MAI session has ended. The session is defined as permanent and will therefore wait for re-establishment of the session.
System Action:
The session waiting panel is displayed. A new session is requested with the target application. If the application is unavailable the session will wait for the application to restart the session.
User Action:
Acknowledge the session waiting panel by pressing a session jump key, entering a skip command or pressing the ENTER key.
Reason:
The MAI-FS session has been cancelled because the subtask managing the session has abended. An N51502 monitor message is issued indicating the abend reason.
System Action:
The session is cancelled.
User Action:
Notify your installation help desk of the problem. If necessary re-establish the session.
Your systems administrator should investigate the cause of the session subtask abend.
Reason:
An MAISESS CANCEL command has terminated the session. The command was issued by the named user.
System Action:
The session is terminated.
User Action:
None.
Reason:
An MAI session subtask attach request failed. Refer to the SOLVE log for more details.
System Action:
The session fails to start.
User Action:
None.
Reason:
The field containing the cursor is required for the function being requested.
System Action:
The request is rejected.
User Action:
Supply the required field and retry.
Reason:
The field indicated by the cursor contains imbedded blanks invalidly.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
The field indicated by the cursor contains an invalid value.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
The program function or attention key specified in the field containing the cursor has already been specified in another jump key field. Jump key values must be unique.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
A data type mismatch has occurred for an MAI session list attribute.
System Action:
The request is rejected and the attribute is marked as in error.
User Action:
Specify a valid name for the attribute value.
Reason:
The field indicated by the cursor must contain Y to indicate YES or N to indicate NO.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
The nominated MAI/EF script procedure does not have a valid procedure name.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
The send of a datastream, received across the session sessid, to the nominated terminal failed.
System Action:
The MAI-FS session is cancelled.
User Action:
Determine the cause of the failure from the VTAM return code, feedback and sense information provided in the message, which can be found in the appropriate VTAM Programming manual and terminal Component Description manuals. It is possible that the application concerned provided an invalid datastream, or one not supported by the physical terminal.
Reason:
The script procedure could not be invoked because of a storage shortage.
System Action:
The MAI session continues.
User Action:
If necessary increase the SOLVE region or partition size.
Reason:
This message precedes the dump of a datastream sent to either the PLU or SLU on an MAI/FS session.
System Action:
None.
User Action:
The message indicates that a script procedure is being traced and that the datastream may need to be reviewed by the MAI/FS script author.
Reason:
The NCL function on the failing statement is valid only if issued by an MAI/EF script procedure.
System Action:
The NCL procedure is flushed.
User Action:
Correct and retry.
Reason:
The failing statement contains a syntax error.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The failing statement specified a logical screen location outside the valid ranges for the terminal being used.
System Action:
The NCL procedure is flushed.
User Action:
Correct and retry.
Reason:
The failing statement specified invalid hexadecimal data. The data either contains invalid characters or is an uneven number of characters.
System Action:
The NCL procedure is flushed.
User Action:
Correct and retry.
Reason:
The MAI/EF script procedure could not continue processing because of a storage shortage.
System Action:
The procedure terminates.
User Action:
If necessary increase the SOLVE region or partition size.
Reason:
An &MAIPUT statement has attempted to increase the send buffer beyond the limit of 65535 bytes.
System Action:
The script procedure is flushed.
User Action:
Check that the script procedure is not in an infinite loop building the datastream. Correct the procedure and rerun.
Reason:
The failing statement contains a syntax error.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The NCL function on the failing statement is valid only if issued by an MAI/EF script or session procedure.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An attempt to reference a session's screen image copy buffer has failed.
System Action:
The NCL procedure is flushed.
User Action:
Ensure that the failing statement is being used in the correct manner. If necessary modify the NCL procedure and retry.
Reason:
An attempt to start a script NCL procedure for a session has failed. A script process is already running for the specified session.
System Action:
The request is rejected.
User Action:
None.
Reason:
An attempt to start a script NCL procedure has failed due to lack of available storage.
System Action:
The request is rejected.
User Action:
Retry the request. If the problem persists notify your installation's help desk facility.
Reason:
An attempt has been made to start a script NCL procedure for an MAI session that has no script procedure name defined.
System Action:
The request is rejected.
User Action:
Modify the session parameters to specify the required script procedure name. If necessary contact you installation help desk to update your MAI session definitions.
Reason:
An attempt to start a script NCL procedure has been made when the session is not in a state able to run a script. The session may not be active or may be terminating.
System Action:
The request is rejected.
User Action:
Retry the request when the session is active.
Reason:
An attempt has been made to flush a script procedure for a specified session. The session does not currently have a script process associated with it.
System Action:
None.
User Action:
None.
Reason:
A request to format session data has failed. The requested session data is not available for processing.
System Action:
The request is failed and &SYSMSG is set to the text of this message.
User Action:
None.
Reason:
There was insufficient storage to enable the logon panel defaults to be permanently updated on disk.
System Action:
The defaults will apply for this SOLVE execution only.
User Action:
Retry later, or increase the SOLVE region or partition size.
Reason:
An error has occurred attempting to write the logon panel defaults to the VFS dataset. The code X`xx' is the VSAM RPL return code.
System Action:
The defaults will apply for this SOLVE execution only.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the VFS dataset from the most recent backup.
Reason:
Confirms the successful updating of the logon panel defaults.
System Action:
The defaults will apply for future executions of this SOLVE system.
User Action:
None.
Reason:
An attempt to start a session failed because the session limit for the application has reached the limit.
System Action:
The session start request fails.
User Action:
Wait a short while and retry. If the problem persists, contact your systems administrator.
The session limit for an application is specified using the MAXSESS parameter of the DEFLOGON (and REPLOGON) command. The SHOW DEFLOGON command can be used to display the current number of sessions for an application and the maximum number of concurrently active sessions.
Reason:
An attempt to start a session failed because you have reached the maximum number of sessions allowed in your user definition.
System Action:
The session start request fails.
User Action:
Close an existing session.
Your session limit is defined as part of your MAI-FS user privileges. Contact your security or systems administrator if you want to change the maximum session limit.
Reason:
An error has occurred sending a datastream from an application to the terminal. P1 is the feedback and sense code returned by the SEND request.
System Action:
The session is cancelled.
User Action:
Determine the cause of the error from the appropriate VTAM Programming Manual. The activity log may contain more information. If necessary use a tracing tool (Session Replay Facility) to record the session flow and assist in problem determination.
Reason:
An informational message to indicate that output has arrived on the MAI-FS session P2 . P1 is the time the data arrived.
System Action:
If the session is marked as Sleeping it is now Visible and will appear in the session circle when jumping.
User Action:
This output may be viewed by returning to MAI-FS and jumping to the session.
Reason:
The nominated structured field was returned by a security exit implementation but was incorrectly defined.
System Action:
The data is rejected and defaults may be taken.
User Action:
Notify the installation help desk of the problem. Your systems administrator should verify the security exit processing is correct.
Reason:
Not enough storage was available to perform the initialization call to the installation provided MAIEX02 exit.
System Action:
No MAI sessions will be allowed.
User Action:
Consider increasing the SOLVE region size.
Reason:
An attempt to perform an initialization call to the installation provided MAIEX02 exit failed because the exit abended.
System Action:
No MAI sessions will be allowed.
User Action:
Determine the cause for the abend, re-assemble and re-link the exit, and retry the SYSPARMS MAIEX02= command.
Reason:
An attempt to perform an initialization call to the installation provided MAIEX02 exit failed because the exit returned an invalid return code.
System Action:
No MAI sessions will be allowed.
User Action:
Correct the error, re-assemble and re-link the exit, and retry the SYSPARMS MAIEX02= command.
Reason:
An attempt to perform an initialization call to the installation-provided MAIEX02 exit failed because the attach failed.
System Action:
No MAI sessions are allowed.
User Action:
Examine the log for additional details about the failure and correct the error.
Reason:
An attempt to perform an initialization call to the installation-provided MAIEX02 exit failed. Either an ABEND occurred or a non-zero return code was returned.
System Action:
No MAI sessions are allowed.
User Action:
Determine the cause of the error, reassemble and relink the exit, and retry the SYSPARMS MAIEX02= command.
Reason:
The MAI-FS service subtask has abended.
System Action:
All MAI-FS sessions whose VTAM ACBs were opened by the service subtask are cancelled. The subtask will be re-attached.
User Action:
Report to your product support representative.
Reason:
The MAI service subtask has abended.
System Action:
All MAI-FS sessions whose VTAM ACBs were opened by the service subtask are cancelled. The subtask will be re-attached.
User Action:
Report the error to your product support representative.
Reason:
MAI session initialization was unable to modify a VTAM request buffer.
System Action:
Processing continues. The session may fail to start.
User Action:
Report the error code and any subsequent error information to Technical Support.
Reason:
A session start request has been terminated because the session start time limit (30 seconds) has expired. This most likely indicates a problem in ACB open/close processing. The output from a SHOW MAISTAT=ACTIVITY command will indicate the current activity for the Service subtask that processes ACB open/close.
System Action:
The MAI-FS session is terminated.
User Action:
Retry the session request. If necessary, notify your installation's help desk. Use the output from the SHOW MAISTAT=ACTIVITY command to determine the current activity for the Service subtask. You may diagnose delays caused by system contention by issuing the system command 'D GRS,C'. You may observe any delays in the communications subsystem (VTAM) processing by displaying the LU being processed.
Reason:
An error occurred during the attempt to obtain the model ACB for MAI-FS sessions.
System Action:
The session request fails.
User Action:
Report the error to your product support representative.
Reason:
An unrecognized input has been entered on the MAI Selection Menu.
System Action:
The input is ignored.
User Action:
Correct the error and retry.
Reason:
A jump request has been ignored, as there are no active MAI sessions.
System Action:
The request is ignored.
User Action:
None.
Reason:
A function key was pressed which has no defined action in the current window.
System Action:
None.
User Action:
None.
Reason:
The SHOW (or SHOWMSG) command has been issued but there are no line messages to display. Messages may be written by an MAI Script NCL procedure using the &WRITE verb or as a result of tracing the procedure using &CONTROL TRACE.
System Action:
None.
User Action:
None.
Reason:
An invalid command was entered on the command line.
System Action:
None.
User Action:
Correct the command and retry.
Reason:
The requested command failed with the specified return code.
System Action:
The command is rejected.
User Action:
Contact your systems administrator.
Reason:
An invalid command was issued for a session that is in use.
System Action:
The command is rejected.
User Action:
Re-enter the command when the target session is inactive.
Reason:
A session command was issued against a session that was not currently running.
System Action:
The command is rejected.
User Action:
The command is only valid for active MAI-FS sessions. Delete the command or specify it using an active session.
Reason:
A request was made to start an MAI session, but the session is already active in the other window.
System Action:
The request is rejected.
User Action:
Use the SPLIT or SWAP command to move to the other window and then select the required session from the MAI menu in that window.
Reason:
A request to start tracing was accepted.
System Action:
None.
User Action:
None.
Reason:
This user's stored definitions are modelled. The definitions may not be updated.
System Action:
The command is rejected.
User Action:
None.
Reason:
The user is not authorized to execute the requested MAI command.
System Action:
The request is rejected.
User Action:
Contact the System Administrator if the function is required.
Reason:
An invalid scroll amount was specified. Valid scroll amounts are PAGE, MAX, HALF or an amount between 1 and 99999.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter a valid value in the scroll field.
Reason:
The specified function key was pressed and it has no action assigned to it.
System Action:
None.
User Action:
None.
Reason:
A SCRIPT START command has completed successfully.
System Action:
The script procedure runs against the specified session.
User Action:
None.
Reason:
An MAISESS START command has been actioned. The session xxxxxxxx has been started.
System Action:
Session initiation is processed.
User Action:
None.
Reason:
An MAISESS START command has been actioned. The session xxxxxxxx has failed to start. Earlier messages indicate the reason for the start failing.
System Action:
None.
User Action:
Determine from the previous messages the reason for the session request failing.
Reason:
An MAISESS BUILD command has completed execution. aaaa is the number of sessions defined in the user's session list.
System Action:
None.
User Action:
None.
Reason:
The MAISESS or SCRIPT command has specified a session which is not defined. aaaaaaaa is either the MAI-FS session identifier or relative session number.
System Action:
The command is rejected.
User Action:
Retry the command correcting the session identifier or relative number specification.
Reason:
An MAISESS DELETE command has been actioned. xxxxxxxx is the MAI session identifier.
System Action:
The session definition is removed from the session list.
User Action:
None.
Reason:
An MAISESS MODIFY command has been actioned. xxxxxxxx is the MAI session identifier.
System Action:
The active session details are updated.
User Action:
None.
Reason:
A SCRIPT CANCEL command has been successfully processed for the named session.
System Action:
The script procedure is flushed.
User Action:
None.
Reason:
An MAISESS CANCEL command specified a region other than the issuing user region and the issuer's authority is less than the MAISESS command's operand authority.
System Action:
The command is rejected.
User Action:
Verify that the region specification is correct. If necessary contact your systems administrator to review your authority and the MAISESS's operand authority.
Reason:
An MAISESS command has specified a session that could not be located.
System Action:
None.
User Action:
Use SHOW MAI to determine the active sessions and reissue the command.
Reason:
An MAISESS CANCEL command has requested termination of an MAI session.
System Action:
The MAI session is terminated according to the options specified on the command.
User Action:
None.
Reason:
The MAISESS or SCRIPT command has specified a session which is currently not active. aaaaaaaa is either the MAI-FS session identifier or relative session number. The command is not valid for a session in this state.
System Action:
The command is rejected.
User Action:
Retry the command when the session state is valid for the command or correct the session specification (identifier or relative number).
Reason:
The MAISESS or SCRIPT command has specified a session which is currently ACTIVE. aaaaaaaa is either the MAI-FS session identifier or relative session number. The command is not valid for a session in this state.
System Action:
The command is rejected.
User Action:
Retry the command when the session state is valid for the command or correct the session specification (identifier or relative number).
Reason:
A MAITITLE command has completed successfully.
System Action:
The title is stored on the system VFS file and is accessible via the &MAITITLE system variable.
User Action:
None.
Reason:
The operand in error requires a valid MAI key name.
System Action:
The command is terminated. Message N29549 is issued indicating the operand in error.
User Action:
Correct the operand indicated by message N29549. Valid values are Fnn, PFnn (where 'nn' is in the range 1 to 24), PA1, PA2, PA3 or ATTN.
Reason:
An attempt to use MAI-FS services has failed because the MAI-FS environment is not available.
System Action:
The NCL procedure is terminated.
User Action:
Notify your installation help desk if necessary. The MAI-FS environment should be initialized prior to using MAI-FS services.
Reason:
The failing statement contains a syntactical error.
System Action:
The NCL procedure is flushed.
User Action:
Correct the coding error and retry.
Reason:
An MAI/FS session has been defined for which no DEFLOGON entry exists. The session cannot be used until a DEFLOGON is issued that specifies the application name.
System Action:
None.
User Action:
Contact your installation help desk to arrange the application's availability or verify the application name used for the session.
Reason:
An MAI verb has been specified without specific session selection and no session is currently active.
System Action:
The verb is not actioned. &RETCODE is set to 4. &SYSMSG is set to the text of this message.
User Action:
None.
Reason:
An MAI verb has been specified with a specific session parameter and the session does not exist.
System Action:
The verb is not actioned. &RETCODE is set to 4. &SYSMSG is set to the text of this message.
User Action:
The session may have been deleted. If you are using the MAI menu then use the REFRESH command (F6) to rebuild your menu and then retry the command. If the error persists contact your program support representative.
Reason:
The operand in error requires valid MAI session field names. At least one of the names supplied is incorrect.
System Action:
The function is terminated. Message N29549 is issued indicating the operand in error.
User Action:
Correct the operand indicated by message N29549.
Reason:
This message is issued in response to an MAIFMODE command and indicates that the request to define an MAI full screen mode terminal pool ( P1 ) was accepted.
System Action:
The pool is available for use in MAI sessions.
User Action:
None.
Reason:
This message is the heading line for a SHOW MAIFPREF command. For more information see message N53H02.
System Action:
None.
User Action:
None.
Reason:
This message provides the detail line for a SHOW MAIFPREF command.
P1 is the MAI full-screen terminal pool name (ACB name prefix).
P2 is the number of ACBs currently in use.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW MAIFPREF command when no MAI full screen prefixes (pool names) are defined that match the pool name criteria provided.
System Action:
None.
User Action:
If an application name pattern was provided, try using a different pattern.
Reason:
Confirms that a valid session cancel request has been accepted.
System Action:
An attempt will be made to cancel the session.
User Action:
The session id cannot be reused until you have viewed the `session end' panel for this session. If the session does not end, try a more powerful form of cancel, such as FORCE or UNCONDITIONAL.
Reason:
The maximum number of sessions has been reached.
System Action:
The session definition request is rejected.
User Action:
Delete unwanted session definitions and retry the request.
Reason:
A syntax error was encountered in attempting to perform variable substitution on the entered logon request.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
The session id entered on the logon panel is already in use by another session.
System Action:
The request is rejected.
User Action:
Choose another session id that is unique.
Reason:
An &MAISPUT verb has attempted to modify the session identifier of a session list item that is currently active. This action is not supported.
System Action:
The request is rejected.
User Action:
Terminate the active session before attempting to modify the session identifier.
Reason:
The session id chosen by default from the logon request conflicts with an existing session or is blank.
System Action:
The request is rejected.
User Action:
Enter a session identifier that is not already in use.
Reason:
An unrecognized session command has been entered.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
No current application image exists. The data has most likely been lost due to a session outage.
System Action:
None.
User Action:
Press the refresh key for the nominated session. This is most likely either PA2 or CLEAR. If the application is unable to refresh the image then restart the user interaction.
Reason:
No current application image exists. The data has most likely been lost due to a session outage. P2 is the application's refresh key.
System Action:
None.
User Action:
Press the refresh key for the session.
Reason:
An attempt to display application data has been rejected due to the display device being incompatible with the session. The terminal does not support extended color attributes used on the application session.
System Action:
The session incompatible panel is displayed in place of the application image.
User Action:
Press a jump key to view another session or the menu. If necessary disconnect from the current device and reconnect at a device that supports extended colors.
Reason:
An attempt to display application data has been rejected due to the display device being incompatible with the session. The terminal does not support extended highlighting attributes used on the application session.
System Action:
The session incompatible panel is displayed in place of the application image.
User Action:
Press a jump key to view another session or the menu. If necessary disconnect from the current device and reconnect at a device that supports extended highlighting.
Reason:
An attempt to display application data has been rejected due to the display device being incompatible with the session. The terminal does not support the screen sizes used on the application session.
System Action:
The session incompatible panel is displayed in place of the application image.
User Action:
Press a jump key to view another session or the menu. If necessary disconnect from the current device and reconnect at a device that supports the session's screen sizes.
Reason:
An attempt to display application data has been rejected due to the display device being incompatible with the session. The terminal does not support 560/20 datastreams used on the application session.
System Action:
The session incompatible panel is displayed in place of the application image.
User Action:
Press a jump key to view another session or the menu. If necessary disconnect from the current device and reconnect at a 560/20 device.
Reason:
MAI/FS is unable to display the application image due to the indicated reason.
System Action:
None.
User Action:
Press PF03 to return to the menu. If possible disconnect your region and reconnect on a terminal that supports the application session.
Reason:
A user that has stored definitions, or uses the definitions of a model userid, has entered the MAI selection menu. In attempting to read the MAI session definition record from the VFS dataset an error occurred. The code P1 is the VSAM RPL return code.
System Action:
The session list build process terminates. The session list may be incomplete.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the VFS dataset from the most recent backup.
Reason:
An attempt to open the MAI session definitions file has failed.
System Action:
The MAI session list is not built.
User Action:
Issue SHOW UDB=ACDB, and review the file availability. The file is defined using the Customizer (/PARMS) parameter group ACDB. Review the initialization log of parameter group and, if necessary, make changes and action the parameter group.
Reason:
Your userid requires a session model for building the MAI selection list information. This model could not be found.
System Action:
The selection menu will not be formatted containing stored session definitions.
User Action:
Stored definitions must be created for the model userid.
Reason:
You do not have any MAI session definitions.
System Action:
None.
User Action:
Press F1 for a tutorial on MAI session establishment, or to find out how to create stored session definitions. Alternatively enter a LOGON command to create a new session.
Reason:
The MAI session definition record contains an invalid session count.
System Action:
The MAI session selection list is not formatted.
User Action:
Notify your installation help desk.
Reason:
The MAI feature is not configured on the requesting system.
System Action:
The request for MAI/FS services is rejected.
User Action:
Notify your installation help desk of the problem circumstances. If MAI is a required feature then contact your product support representative to arrange licensing.
Reason:
NCL Substitution has detected an error condition in the MAI logon string.
System Action:
The MAI session start is terminated.
User Action:
Review the MAI session's logon string definition. Ensure all NCL variable references resolve to valid names.
Reason:
A request to process an MAI-FS session has been rejected because the session aaaaaaaa is still in use.
System Action:
The request is rejected.
User Action:
Retry the function when the session is inactive.
Reason:
An error has occurred processing a message for the MAI component.
System Action:
The message is suppressed.
User Action:
Report the error to your product support representative.
Reason:
An MAI-FS session has not processed input within the time specified by the MTLIMIT operand of the associated DEFLOGON.
System Action:
The timeout action cccccccc is commenced.
User Action:
None.
Reason:
This is the heading line of a SHOW SYSWAIT display.
System Action:
None.
User Action:
See message number N58002 for a description of the display.
Reason:
This line is an output line from a SHOW SYSWAIT display. Two of these lines are displayed for every SHOW SYSWAIT command. The first line is an interval display since the system started or the previous SHOW SYSWAIT command. The second line is a long term display since the product rtegion started or midnight.
hh.mm.ss In both cases this is the start interval time.
awaitnnn Is the number of operating system waits that have occured since the interval start time.
fwaitnnn Is the number of operating system waits issued when at least one NCL process was active but forced idle due to performance controls.
fff.ff Is the percent representation of fwaitnnn to awaitnnn.
aaa.aa The percentage of elapsed time since the interval start that the product region was in a voluntary operating system wait.
rrrrr Is the average number of internal events processed between each voluntary operating system wait.
System Action:
The short term interval statistics are reset.
User Action:
This display is designed as a guide to the effect external operating system processing resource controls and internal NCL performance controls are having on performance. Low processing resource consumption observed external to the product region combined with low AWAIT% indicates operating system controls may need to be adjusted in order to provide more processing resource. High processing resource consumption observed external to the region combined with low AWAIT% indicates NCL performance controls may need to be reviewed.
Reason:
This line is output from a SHOW SYSPGT command. Four lines are used to display each of the performance groups, BACKGROUND, OCS, FULLSCREEN, and SYSTEM as displayed by the description .
pg This is the performance group number.
pri This is the initial priority for that performance group.
active This is the number of NCL procedures currently active in the performance group.
hh.mm.ss This is the time that the performance group table was last updated by a SYSPGT command.
started This is the number of NCL processes that have started during the interval since hh.mm.ss .
delayed This is the number of forced waits that have occurred for all procedures that have run in this performance group.
chgpri This is the number of priority changes that have occurred for all procedures that have run in this performance group.
Description This is a descriptive name of the performance group.
System Action:
None.
User Action:
None.
Reason:
This line is the heading line for a SHOW SYSRCT display.
System Action:
None.
User Action:
See message number N58006 for a description of the display.
Reason:
This line is output from a SHOW SYSRCT command. Four lines are used to display each of the performance groups, BACKGROUND, OCS, FULLSCREEN, and SYSTEM.
pg This is the performance group number.
active This is the number of NCL procedures currently active in the performance group.
hh.mm.ss This is the time that the resource control table was last updated by a SYSRCT command.
started This is the number of NCL processes that have started during the interval since hh.mm.ss.
delayed This is the number of forced waits that have occurred for all procedures that have run in this performance group.
limit This is the number of times that a forced wait has been issued for the maximum or minimum duration.
chgpri This is the number of priority changes that have occurred for all procedures that have run in this performance group.
System Action:
None.
User Action:
None.
Reason:
This line is the first line output from a SHOW SYSRCT= pg command that displays the details of resource controls for the specified performance group pg .
pg This is the performance group number.
description This is the descriptive name of the performance group.
nnnn This is the number of NCL processes that have started during the interval since hh.mm.ss .
hh.mm.ss This is the time this performance group had its resource control table updated by a SYSRCT command.
System Action:
None.
User Action:
For more information about SHOW SYSRCT, see the Reference Guide.
Reason:
This line is the heading line of a SHOW SYSRCT detailed display.
System Action:
None.
User Action:
None.
Reason:
This line is a sub-heading for a priority grouping in a SHOW SYSRCT detail display.
pg is the performance group number.
initp is set to the value `<=I=' on the line for the initial priority of the performance group.
System Action:
None.
User Action:
None.
Reason:
This line is the first detail line for a priority grouping within a SHOW SYSRCT detail display. This line displays the short term resource controls and statistics. These controls apply to processing units consumed by an NCL process since a voluntary loss of control.
tdelay and tcpri are the processing unit trigger level values.
cinit , cadj , clim , and cnpri are the resource control measures to be actioned when the trigger levels are reached. sdelay , slim , and
scpri are statistics on the number of resource control actions taken.
active is the number of currently active processes in that priority grouping for this performance group.
System Action:
None.
User Action:
For further information refer to the SOLVE Management Services
Implementation and Administration Guide .
Reason:
This line is the second detail line for a priority grouping within a SHOW SYSRCT detail display. This line displays the long term resource controls and statistics. These controls apply to processing units consumed by an NCL process since it started. tdelay and tcpri are the processing unit trigger level values. cinit , cadj , clim , and cnpri are the resource control measures to be actioned when the trigger levels are reached. sdelay , slim , and scpri are statistics on the number of resource control actions taken.
System Action:
None.
User Action:
None.
Reason:
This line is the heading line of a SHOW SYSPGT display.
System Action:
None.
User Action:
See message number N58004 for a description of the display.
Reason:
No operands have been entered on SYSPGT/SYSRCT command.
System Action:
None.
User Action:
Re-enter the command with the desired operands.
Reason:
There is either no data after the keyword operand or the data has an invalid format.
System Action:
The command is not executed.
User Action:
Re-enter the command with the correct format.
Reason:
The supplied operand aaaaaaaa is not recognized as a valid keyword of the command.
System Action:
The command is not executed.
User Action:
Re-enter the command with the correct operands.
Reason:
The supplied value for operand is invalid.
System Action:
The command is not executed.
User Action:
Re-enter the command with the correct operand values.
Reason:
The command string contains unrecognisable characters.
System Action:
The command is not executed.
User Action:
Re-enter the command with the correct syntax.
Reason:
The operand specified contains too many subparameters to be valid.
System Action:
The command is not executed.
User Action:
Re-enter the command with the correct number of subparameters.
Reason:
An opername operand has been duplicated on either the SYSPGT or SYSRCT command.
System Action:
The command is not executed.
User Action:
Re-enter the command without the duplication.
Reason:
The data supplied either as a single data value or as subparameter nn of the operand is invalid. The attribute describes the nature of the error.
System Action:
The command is not executed.
User Action:
Re-enter the command with the correct values.
Reason:
The first form of the message indicates that a required operand , such as the performance group `PG=', has not been supplied. The second form of the message indicates that the operand was supplied without any data value.
System Action:
The command is not executed.
User Action:
Re-enter the command with all the required operands.
Reason:
No update values have been supplied on the update command.
System Action:
None.
User Action:
If you wish to update the resource control values supply update operands on the resource control command.
Reason:
The combined update and existing values are logically inconsistent. For example, an update has been attempted to make the delay limit less than the initial delay with the delay adjust value set to positive.
System Action:
The resource table update is not performed.
User Action:
Review the update values.
Reason:
The operand abbreviation aaa is too short to provide uniqueness.
System Action:
The command is not executed.
User Action:
Re-enter the command with a longer form of the keyword.
Reason:
The specified system performance control table has been updated with the new resource control values.
System Action:
The time of update is recorded. For Resource Control Table (SYSRCT) updates, the interval statistics are accumulated into the Performance Group Table and then reset.
User Action:
Monitor the effect of resource control measures using SHOW SYSRCT and SHOW SYSPGT.
Reason:
Insufficient storage was available to retrieve a panel from a panel library.
System Action:
The request fails.
User Action:
Retry. Contact your systems administrator if the condition persists.
Reason:
The VSAM panel library is not open. A panel library may be opened using the UDBCTL OPEN command.
System Action:
The requested function cannot be performed.
User Action:
Refer to your systems administrator.
Reason:
A panel was retrieved from a panel library but was found to be empty.
System Action:
The display of the panel fails.
User Action:
Determine why it was empty and correct the panel definition.
Reason:
An error occurred on a panel library.
xx is the VSAM RPL return code in hexadecimal.
libname is the name of the library in error.
System Action:
The request fails.
User Action:
Contact your systems administrator.
Reason:
A request was made to retrieve a panel that is not defined on the panel library path pathname.
System Action:
The request fails.
User Action:
The procedure invoking Panel Services is running with &CONTROL NOPANELRC, which is the default. If it is desired that the NCL procedure should ignore errors of this nature, and processing should continue having encountered such an error, attention should be given to the &CONTROL PANELRC statement, which in such a situation would return a value of 16 in the &RETCODE variable rather than terminate.
Reason:
SOLVE could not obtain storage when attempting to build a 3270 data stream from a panel definition, or SOLVE detected a corrupt panel definition that could not be processed.
System Action:
The request fails.
User Action:
Determine why SOLVE is short on storage, or update the panel definition using Edit Services and retry the panel display.
Reason:
A request was made to retrieve a panel, however the path pathname which is specified in the user profile is not defined to SOLVE.
System Action:
The request fails.
User Action:
Contact your systems administrator to ensure that the user profile and path definitions are correct.
Reason:
A 'View' request was issued for a panel in a library which is not on the users panel library path.
System Action:
The request is not performed.
User Action:
Correct the library name and retry.
Reason:
A 'View' request was issued for a panel in a particular library, however the panel is not present in the library.
System Action:
None.
User Action:
Correct the panel name, or use the 'Information' option to determine where the panel is defined.
Reason:
The #OPT ERRFLD= statement has been coded in the panel definition but no #ERR statement exists to specify the processing that is to be performed as a result of the error condition.
System Action:
The procedure terminates.
User Action:
Correct the panel definition and include an #ERR control statement.
Reason:
A panel definition contains no lines that can be displayed after all control statements have been processed.
System Action:
The attempt to display the panel fails.
User Action:
Correct the panel definition.
Reason:
Insufficient storage was available to process the request to display a panel.
System Action:
The request fails.
User Action:
Retry. Contact your systems administrator if the condition persists.
Reason:
During Preparse scanning of panel lines, an invalid variable name was encountered or the length of a line after variable substitution exceeded the system limits.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The maximum number of display lines allowed for a panel definition is 255 lines.
System Action:
The request is rejected.
User Action:
Correct the panel definition.
Reason:
The #TRAILER statement is being used in a panel, but there are more trailer lines than will fit on the physical screen.
System Action:
The request is rejected.
User Action:
Check that the #TRAILER END statement is present in the panel definition or reduce the number of lines in the trailer.
Reason:
The specified control statement is invalid. errortext is the text of the statement in error to a maximum of 80 characters.
System Action:
The procedure fails.
User Action:
This message will be accompanied by other messages detailing the reason for the error. Correct the statement and retry the procedure.
Reason:
The CURSOR operand allows specification of a field or exact screen co- ordinates into which the cursor is to be placed when the panel is displayed. The variable name or co- ordinates specified are invalid.
System Action:
The procedure is terminated.
User Action:
Correct the definition and retry the procedure.
Reason:
The #FLD allows a range of attributes to be associated with a single character. This character has been omitted from the #FLD statement.
System Action:
The procedure terminates.
User Action:
Correct the panel definition and retry the procedure.
Reason:
The #FLD statement allows a range of attributes to be associated with a character, but the character specified is not valid for use as a #FLD character. Valid characters are any non-alpha, non-numeric characters. Hexadecimal values may also be specified as X'xx'. The values X'0E' and X'0F' are not allowed.
System Action:
The procedure terminates.
User Action:
Correct the panel definition and retry the procedure.
Reason:
There is a limit of 90 #FLD characters allowed for any one panel definition.
System Action:
The procedure terminates.
User Action:
Correct the panel definition and retry.
Reason:
The INWAIT operand must be numeric and in the range 0 - 86400 (seconds).
System Action:
The procedure terminates.
User Action:
Correct the panel definition and retry the procedure.
Reason:
The #OPT DEFAULT operand allows specification of alternative field characters to replace the standard default characters (%,+,_), but invalid characters have been coded. Valid characters are any non-alpha, non-numeric characters. A hexadecimal string may be coded to represent the three bytes as well, if so the bytes must not represent alphabetic, or numeric characters in EBCDIC, or the values X'0E' or X'0F'.
System Action:
The procedure is terminated.
User Action:
Correct the panel definition and retry.
Reason:
The #OPT DEFAULT operand has specified alternative default field characters but the characters chosen conflict with other field characters already defined by #FLD statements.
System Action:
The procedure terminates.
User Action:
Correct the panel definition and retry. Place the #OPT statement before the #FLD statement if it is intended to define attributes for a default field character.
Reason:
The #OPT ERRFLD operand allows definition of a variable located in the panel to which will be applied the attributes in the #ERR control statement if the field is entered incorrectly. The variable name specified is invalid.
System Action:
The procedure terminates.
User Action:
Correct the panel definition and retry.
Reason:
After variable substitution the specified panel statement has exceeded the maximum length of 256 characters.
System Action:
The procedure terminates.
User Action:
Correct the panel definition and retry. If it is a control statement that is in error, split it into multiple statements.
Reason:
The #OPT PREPARSE operand must specify only one character which must not be A to Z or 0 to 9. Either more than one character was specified or the character specified was invalid.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The WIDTH operand on the #OPT statement was specified, but was not one of the valid values. The only valid values are 80 and 132.
System Action:
The NCL procedure is terminated, unless &CONTROL PANELRC was in effect.
User Action:
Correct and retry.
Reason:
The panel definition requested contains a #ALIAS statement with no operands. The #ALIAS name must be specified.
System Action:
The panel display request is rejected.
User Action:
Correct the panel definition such that any #ALIAS statement contains a valid name.
Reason:
The requested panel contains a #ALIAS statement which specifies an invalid name.
System Action:
The NCL procedure is terminated unless CONTROL PANELRC was in effect.
User Action:
The alias name must be a valid name. That is up to 8 characters made up of alphanumeric and national characters.
Reason:
The definition of the requested panel contains a list of variable names. The list contains null entries, this is not permitted.
System Action:
The NCL procedure is terminated unless &CONTROL PANELRC is in effect.
User Action:
Correct the panel definition and retry.
Reason:
The definition of the requested panel contains a list of variable names. There are too many entries in the list.
System Action:
The NCL procedure is terminated unless &CONTROL PANELRC is in effect.
User Action:
Split the #ALIAS statement into two statements and retry.
Reason:
The definition of the requested panel contains a list of variable names. The list must be a single variable name, or a list of variable names separated by commas and surrounded by parenthesis. For example: VARS=(VAR1,VAR2)
System Action:
The NCL procedure is terminated unless &CONTROL PANELRC is in effect.
User Action:
Correct the #ALIAS statement and retry.
Reason:
The definition of the panel requested contains an #ALIAS statement which has both the RANGE= and VARS= operands coded. Only one of these operands may be specified on a single #ALIAS statement.
System Action:
The NCL procedure is terminated unless &CONTROL PANELRC is in effect.
User Action:
Correct the panel definition and retry.
Reason:
A panel display was requested but there was insufficient storage to process the panel definition.
System Action:
The NCL procedure is terminated unless &CONTROL PANELRC was in effect.
User Action:
Retry the operation.
Reason:
The definition of the requested panel contained a #ALIAS statement. The list of variables contains an entry which is not a valid NCL variable name.
System Action:
The NCL procedure is terminated unless &CONTROL PANELRC is in effect.
User Action:
Correct the panel definition and retry.
Reason:
The definition of the requested panel contains a #ALIAS statement with the RANGE= operand specified. The value specified is not in the form RANGE=(min,max) where min and max are numbers and min is less than max.
System Action:
The NCL procedure is terminated unless &CONTROL PANELRC is in effect.
User Action:
Correct the panel definition and retry.
Reason:
The definition of the requested panel contains a #ALIAS statement with the VARS= operand specified. The list contains a value which is too long to be an NCL variable name.
System Action:
The NCL procedure is terminated unless &CONTROL PANELRC is in effect.
User Action:
Correct the panel definition and retry.
Reason:
Insufficient storage is available to display the panel.
System Action:
The display function fails.
User Action:
Retry the procedure. Contact your systems administrator if the condition persists.
Reason:
The panel line indicated contains a syntax error. nnnn is the line number (excluding control statements) in error. errtext is the error reason as follows:
PANEL EXCEEDS 62 LINES The panel definition (excluding control statements) exceeds the maximum number of 62 lines for a panel definition. OUTPUT VARIABLE INVALID The line in error contains a variable in an output field that does not conform to variable syntax requirements so substitution could not be performed.
MAX SUBSTITUTION LIMIT During the substitution process for a field on the line in error the substitution limit of 256 was exceeded.
INPUT VARIABLE MISSING An input field on the line in error does not specify the name of a variable that is to receive the input data entered into that field.
MULTIPLE INPUT VARIABLES An input field must only specify one input variable that is to receive data entered into the field. This error can result from failing to close an input field with another attribute character or due to the misuse of an attribute character.
INPUT VARIABLE TOO LONG The variable named in an input field exceeds the maximum length for an input variable (12 characters).
INPUT VARIABLE INVALID The input variable named in an input field on the line in error is not a valid variable name. The named variable need not be defined prior to its use in a panel definition, however, only valid variable names can be used.
INPUT VARIABLE RESERVED The input variable named in an input field on the line in error is a reserved system variable which cannot be used in an input field. System variables can only be used in output fields.
SPD FIELD INVALID FORMAT An SPD field on the line in error does not conform to the required format. The SPD field must start with one of the valid SPD characters, `?',` ' or a blank and must be followed by one or more spaces and the name of the variable that is to be set to SELECTED if the field is selected.
SPD FIELD INV. VARIABLE An SPD field on the line in error specifies the name of an invalid variable that is to be set to SELECTED if the field is selected. A valid variable name must be used.
INPUT FIELD FORMAT ERROR An input field must contain the name of the variable that is to receive the data entered into the field. This variable name must commence immediately following the field character that designates an input field with no intervening blanks. The field in error will be an input field on the specified line.
System Action:
A panel error condition is raised. If &CONTROL PANELRC is in effect then &RETCODE is set to 16 and &SYSMSG is set to the N59302 text. Otherwise the NCL process is terminated in error. In addition an N59305 message is logged containing the failing panel line.
User Action:
Correct the panel definition and retry.
Reason:
The panel definition specifies that the cursor is to be positioned in an input variable named varname but that variable does not exist in the panel definition.
System Action:
The procedure terminates.
User Action:
Define the nominated variable in an input field on the panel, then retry. The cursor location variable can be named on either the CURSOR or ERRFLD operand of the #OPT statement.
Reason:
The panel definition will produce a datastream too big for the current maximum datastream size.
System Action:
The &PANEL statement fails.
User Action:
Use SYSPARMS PANLBFSZ operand to increase the maximum buffer size available for panel definition datastreams. Then rerun the procedure.
Reason:
This message is logged following a failing &PANEL request. An N59302 message identifies the cause of the failure. This message contains the text of the panel definition in error.
System Action:
The &PANEL statement fails.
User Action:
Refer to the N59302 message to determine the cause of the error. If necessary correct the panel definition and/or the procedure.
Reason:
An error has occurred trying to generate the terminal datastream for the current panel.
System Action:
The &PANEL statement fails and diagnostic information is written to the activity log.
User Action:
This message indicates an internal error. Forward the diagnostic information to your product support representative.
Reason:
Insufficient storage was available to complete the display of a panel.
System Action:
The procedure terminates.
User Action:
Retry. Contact your systems administrator if the condition persists. If necessary increase the region size. REGION=32M is enough for most SOLVE systems. Large SOLVE:Central or SOLVE:Operations regions can be specified with REGION=0M.
Reason:
An internal error occurred when attempting to display a panel.
System Action:
The procedure terminates.
User Action:
Redefine the panel on the panel library. If the condition persists refer to your systems administrator, who should report the occurrence to your product support representative.
Reason:
The contents of the field shown as being in error have been omitted.
System Action:
None.
User Action:
Type the desired value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because the data contains imbedded blanks.
System Action:
None.
User Action:
Type the correct value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because the data contains trailing blanks. This field must be completely filled with valid characters.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because it does not contain solely numeric characters.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because it does not conform to naming conventions for a PDS member (the field must commence with alpha or national characters and be followed by alphanumeric and/or national characters).
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because the number entered is not within the range defined for that field.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because they do not match the date format defined for that field.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because it does not conform to naming conventions for valid OS/VS format dataset name. If required, a partitioned dataset (PDS) member name or Generation data Group (GDG) number can be specified as part of the name.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because an invalid member name was included in the dataset name. The member name must commence with alpha or national characters and be followed by alphanumeric and/or national characters.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because the data contained in it matches a reserved NCL keyword.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because it does not contain a (signed) numeric value.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because it does not conform to naming conventions for a generic PDS member name (the field must commence with alpha or national characters and be followed by alphanumeric and/or national characters but may be terminated with a single asterisk (*)).
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because it does not contain solely alphabetic characters.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because it contains characters other than A to Z, 0 to 9, @, # and $.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because it contains characters other than 0 to 9 and A to F.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because it does not conform to the syntax for integers, signed numbers or real numbers, including scientific notation.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
The contents of the field shown as being in error are invalid because they do not match the time format defined for that field.
System Action:
None.
User Action:
Type the corrected value into the indicated field and retry.
Reason:
Message returned from $MAINSII subsystem in variable. The subsystem version is different to the SOLVE version.
System Action:
Call to subsystem fails.
User Action:
Contact product support representative.
Reason:
No errors occurred on call to $MAINSII subsystem.
System Action:
None.
User Action:
None.
Reason:
No warnings occurred on call to $MAINSII subsystem.
System Action:
None.
User Action:
None.
Reason:
An error was detected in the NSI request vector on the call to the FNMNSI module from $MAINSII. This message is returned from the $MAINSII subsystem in a token.
System Action:
None.
User Action:
Look up FNMNSI return code and feedback code in NPM installation manual, and try to determine reason for error.
Reason:
The FNMNSI module returned an undocumented return code.
System Action:
MAI : NSI processing terminated.
User Action:
Verify that FNMNSI return code is not documented in NPM Installation manual, and contact product support representative.
Reason:
An internal error occurred in the FNMNSI module when it was called by the $MAINSII subsystem.
System Action:
MAI : NSI interface terminates.
User Action:
Contact product support representative.
Reason:
The FNMNSI module was called by the $MAINSII subsystem when the subsystem was not authorized.
System Action:
MAI : NSI interface is terminated.
User Action:
SOLVE system must be running authorized to use MAI : NSI interface.
Reason:
A call to the FNMNSI module was made by the $MAINSII subsystem, when the NSI address space was not running.
System Action:
MAI : NSI interface terminated.
User Action:
NPM must be started/restarted with the NSI component of NPM activated. NPM, and the NSI component of NPM must be active in order for the MAI : NSI interface to work.
Reason:
An attempt to call the FNMNSI module from the $MAINSII subsystem failed because the program id table in the NSI is full.
System Action:
MAI : NSI interface is terminated.
User Action:
Refer to NPM Installation manual, section on NSI.
Reason:
The FNMNSI module returned a return code that is undocumented in the NPM Installation manual, when called from the $MAINSII subsystem.
System Action:
MAI:NSI interface is terminated.
User Action:
Confirm that FNMNSI return code is not documented in the NPM Installation manual, and contact product support representative.
Reason:
An attempt was made to call the FNMNSI module from the $MAINSII subsystem before the subsystem connected to the NSI.
System Action:
MAI : NSI Interface is terminated.
User Action:
Re-start MAI : NSI interface. If problem continues to occur, contact product support representative.
Reason:
Connection to the FNMNSI module by the MAI interface to the NetView Synergy Interface (NSI) failed.
System Action:
MAI's interface to the NSI is not started.
User Action:
Check that Network Performance Monitor (NPM) and the NetView Synergy Interface (NSI) component of NPM are started. If there is no need to use the MAI NSI support then ignore the message.
Reason:
The program load for module NM055 has failed.
System Action:
MAI-OC initialization is not performed.
User Action:
Determine the cause of the load failure. If NM055 is not in the SOLVE load library then review the installation job messages.
Reason:
The NMIFR subtask is active. The NMIFR subtask is activated by one of the following reasons:
- After receipt of the first NMIFR verb call for this region
- After an abend and subtask reactivation, that is, after N5I302 and N5I303
- After an unrecoverable abend (message N5I304) and RESET call is issued
System Action:
The NMIFR subtask processes NMIFR verb calls as normal.
User Action:
None.
Reason:
The MIFR subtask has abended. This is preceeded by messages N15Z20 and N15Z21 detailing the abend details.
System Action:
If the subtask was processing a NMIFR verb work request, that request is terminated with &SYS.RETCODE=12 and &SYS.FDBK=5. This messages is followed by N5I303 or N5I304.
User Action:
Report the abend to Technical Support. See the following N5I303 or N5I304 messages.
Reason:
The NMIIFR subtask has abended, as noted by the preceeding message, N5I302. The NMIFR subtask has been reactivated.
System Action:
Subsequent work requests are processed as normal. To prevent a potential subtask abend loop, only two subtask reactivations are allowed. A third abend causes message N5I304 to be issued instead of N5I303.
User Action:
No action required.
Reason:
The NMIFR subtask has abended, as noted by the preceding message N5I302. The number of abends allowed for the NMIFR subtask has been exceeded. This number is set to two; the third abend during the region lifetime causes this message. The NMIFR interface is now disabled.
System Action:
Any subsequent NMIFR verb call requests are terminated with &SYS.RETCODE=12 and &SYS.FDBK=8. This also applies to any NMIFR requests already received but still queued for subtask processing.
User Action:
To re-establish the NMIFR subtask interface, recycle the region.
Reason:
An attempt to shutdown the NMIFR subtask was unsuccessful. The NMIFR subtask did not terminate gracefully in five seconds. The system has forcibly detached the subtask. This may occur if the subtask is busy processing a EZBNMIFR API call.
System Action:
After forcibly detaching the subtask, the NMIFR interface is disabled.
User Action:
A forced detach should occur at region shutdown only. This message is for informational use only.
Reason:
An OMLCTL CMDREPL command named an unknown or inexact command name.
System Action:
The command is ignored.
User Action:
Check the required command name.
Reason:
An OMLCTL CMDREPL command named a command that does not allow a CMDREPL procedure to replace it.
System Action:
The command is ignored.
User Action:
Check the required command name.
Reason:
An OMLCTL CMDREPL command named a command that is presently replaced by an NCL CMDREPL procedure,
System Action:
The command is ignored.
User Action:
Check the required command name.
Reason:
An OMLCTL RESETLT command has been successfully processed.
System Action:
The OML/NCL language recognition table has been cleared.
User Action:
None.
Reason:
An OMLCHECK command has been processed. This message shows the result. This message is produced if no errors or warnings were detected.
System Action:
None.
User Action:
None.
Reason:
An OMLCHECK command has been processed. This message shows the result. This message is produced if warnings were found (but no errors).
System Action:
None.
User Action:
None.
Reason:
An OMLCHECK command has been processed. This message shows the result. This message is produced if errors were found.
System Action:
None.
User Action:
None.
Reason:
An OMLCHECK command has been processed. This message is produced if STATS=YES was specified. The message shows the type of code loaded (SRC or OBJ), the number of lines in the member, and the amount of storage needed.
System Action:
None.
User Action:
None.
Reason:
An OMLCHECK command has been processed. This message is produced if STATS=YES was specified. The message shows the elapsed and CPU times taken to perform the load and compile.
System Action:
None.
User Action:
None.
Reason:
This is a header message from a SHOW OMLSTAT command. It contains column headings for the following N64015 message(s).
Columns are:
NAME The name of the procedure
LIBRARY The library that the procedure was loaded from
S/O Whether the procedure is source (SRC) or object (OBJ)
TYPE The type of procedure (PROC, FUNC, PKG), LDNG if loading
STATUS The present status of the procedure:
AUTOSHR - Presently shared in use
RETAIN - Retained for future use
PRELOAD - Preloaded
CMDREPL - A command replacement
P-UNLOAD - Pending unload
PVT-xxxx - Loaded privately
USERS The number of active users of the procedure
TOT-USE The total number of users of the procedure
LAST-PTF The last PTF applied to the source
UID/AUSE The private load user ID (PRIVATE), or aged use (RETAIN)
System Action:
None
User Action:
None
Reason:
This is a header message from a SHOW OMLSTAT command. It contains column headings for the following N64016 message(s).
This message is produced only if the DETAIL=YES operand is coded.
Columns are:
ASHR>RT1 The total number of moves from AUTOSHR to RETAIN status RT1>ASHR The total number of moves from RETAIN to AUTOSHR status RT1>RT2 Always zero RT2>ASHR Always zero
System Action:
None
User Action:
None
Reason:
This is a header message from a SHOW OMLSTAT command. It contains column headings for the following N64017 message(s).
This message is produced only if the DETAIL=YES operand is coded.
Columns are:
LD-TIME Total elapsed time to load the procedure
LD-CPU CPU time used loading the procedure (if available)
LD-FTIME Time spent issuing FIND operations
LD-#FIND Number of FIND operations performed
System Action:
None
User Action:
None
Reason:
This is a header message from a SHOW OMLSTAT command. It contains column headings for the following N64018 message(s).
This message is produced only if the DETAIL=YES operand is coded.
Columns are:
CODE-BLK Number of 4K blocks allocated to compiled code
RELO-BLK Number of 4K blocks allocated to relocation lists
STG-KBYT Total storage required in Kbytes
SRCLINES Number of source lines (for source), or the number of lines of object (if loaded from object)
System Action:
None
User Action:
None
Reason:
This is a detail message from a SHOW OMLSTAT command. See message N64010 for column headings.
System Action:
None
User Action:
None
Reason:
This is a detail message from a SHOW OMLSTAT command. Refer to message N64011 for column headings.
This message is only produced if the DETAIL=YES operand is coded.
System Action:
None.
User Action:
None.
Reason:
This is a detail message from a SHOW OMLSTAT command. Refer to message N64012 for column headings.
This message is only produced if the DETAIL=YES operand is coded.
System Action:
None.
User Action:
None.
Reason:
This is a detail message from a SHOW OMLSTAT command. Refer to message N64013 for column headings.
This message is only produced if the DETAIL=YES operand is coded.
System Action:
None.
User Action:
None.
Reason:
This is a header message from a SHOW OMLSTAT command. It provides column headings for following N64031 messages.
This message is only produced if the STATS=YES operand is coded.
System Action:
None.
User Action:
None.
Reason:
This is a detail message from a SHOW OMLSTAT command. It provides various statistics.
This message is produced only if the STATS=YES operand is coded.
The following items are displayed:
NUM PRELOAD - The current number of preloaded procedures
KB PRELOAD - The total preloaded procedure storage
NUM AUTOSHR - The current number of autoshared procedures
KB AUTOSHR - The total autoshared procedure storage
NUM RETAINED - The current number of retained procedures
KB RETAINED - The total retained procedure storage
NUM PRIVATE - The current number of private procedures
KB PRIVATE - The total private procedure storage
TOT EXECREQ - The total number of execution requests
FAST EXECREQ - The number of fast-path execution requests
SLOW EXECREQ - The number of slow-path execution requests
TOT EXECDROP - The total number of execution drop requests
FAST EXECDROP - The number of fast-path execution drop requests
SLOW EXECDROP - The number of slow-path execution drop requests
EXEC FROM PRELD - Number of exec requests satisfied from preload
EXEC FROM ASHR - Number of exec requests satisfied from autoshare
EXEC FROM RETN - Number of exec requests satisfied from retain
EXEC LOAD SHARE - Number of exec requests that caused a shared load
EXEC LOAD PVT - Number of exec requests that caused a private load
EXEC TOTAL LOAD - The total number of execution loads
MOVE AS -> RT - Total moves from autoshr to retain
MOVE RT -> AS - Total moves from retain to autoshare
DROP RT - Total drops from retain
ACTIVE STACKS - Current number of active stacks
FREE STACKS - Current number of available stacks
SYSGET STACKS - Number of stacks obtained from free storage
SYSPUT STACKS - Number of stacks released to free storage
ACTIVE VWAS - Current number of active verb work areas
FREE VWAS - Current number of available verb work areas
SYSGET VWAS - Number of verb work areas obtained from free storage SYSPUT VWAS - Number of verb work areas released to free storage
STACK GARB-COLL - Number of times a stack had a garbage collection
GARB-COLL-OK - Number of times a garbage collection freed storage
BUFF- RECLAIMED - Number of buffers reclaimed by stack garbage collect
System Action:
None
User Action:
None
Reason:
An attempt to call the named NCLEX01 exit has failed.
The following items are displayed:
NUM PRELOAD - the current number of preloaded procedures
KB PRELOAD - the total preloaded procedure storage
NUM AUTOSHR - the current number of autoshared procedures
KB AUTOSHR - the total autoshared procedure storage
NUM RETAINED - the current number of retained procedures
KB RETAINED - the total retained procedure storage
NUM PRIVATE - the current number of private procedures
KB PRIVATE - the total private procedure storage
TOT EXECREQ - the total number of execution requests
FAST EXECREQ - the number of fast-path execution requests
SLOW EXECREQ - the number of slow-path execution requests
TOT EXECDROP - the total number of execution drop requests
FAST EXECDROP - the number of fast-path execution drop requests
SLOW EXECDROP - the number of slow-path execution drop requests
EXEC FROM PRELD - Number of exec requests satisfied from preload
EXEC FROM ASHR - Number of exec requests satisfied from autoshr
EXEC FROM RETN - Number of exec requests satisfied from retain
EXEC LOAD SHARE - the number of exec request that caused a shared load EXEC LOAD PVT - the number of exec requests that caused a private load EXEC TOTAL LOAD - the total number of execution loads
MOVE AS -> RT - Total moves from autoshr to retain
MOVE RT -> AS - total moves from retain to autoshr
DROP RT - total drops from retain
ACTIVE STACKS - Current number of active stacks
FREE STACKS - current number of available stacks
SYSGET STACKS - number of stacks obtained from free storage
SYSPUT STACKS - number of stacks released to free storage
ACTIVE VWAS - Current number of active verb work areas
FREE VWAS - current number of available verb work areas
SYSGET VWAS - number of verb work areas obtained from free storage SYSPUT VWAS - number of verb work areas released to free storage
System Action:
The request fails.
User Action:
Determine why the call failed.
Reason:
A bad return code was returned from the named NCLEX01 exit.
The following items are displayed:
NUM PRELOAD - the current number of preloaded procedures
KB PRELOAD - the total preloaded procedure storage
NUM AUTOSHR - the current number of autoshared procedures
KB AUTOSHR - the total autoshared procedure storage
NUM RETAINED - the current number of retained procedures
KB RETAINED - the total retained procedure storage
NUM PRIVATE - the current number of private procedures
KB PRIVATE - the total private procedure storage
TOT EXECREQ - the total number of execution requests
FAST EXECREQ - the number of fast-path execution requests
SLOW EXECREQ - the number of slow-path execution requests
TOT EXECDROP - the total number of execution drop requests
FAST EXECDROP - the number of fast-path execution drop requests
SLOW EXECDROP - the number of slow-path execution drop requests
EXEC FROM PRELD - Number of exec requests satisfied from preload
EXEC FROM ASHR - Number of exec requests satisfied from autoshr
EXEC FROM RETN - Number of exec requests satisfied from retain
EXEC LOAD SHARE - the number of exec request that caused a shared load EXEC LOAD PVT - the number of exec requests that caused a private load EXEC TOTAL LOAD - the total number of execution loads
MOVE AS -> RT - Total moves from autoshr to retain
MOVE RT -> AS - total moves from retain to autoshr
DROP RT - total drops from retain
ACTIVE STACKS - Current number of active stacks
FREE STACKS - current number of available stacks
SYSGET STACKS - number of stacks obtained from free storage
SYSPUT STACKS - number of stacks released to free storage
ACTIVE VWAS - Current number of active verb work areas
FREE VWAS - current number of available verb work areas
SYSGET VWAS - number of verb work areas obtained from free storage SYSPUT VWAS - number of verb work areas released to free storage
System Action:
The request fails.
User Action:
Check the exit logic.
Reason:
The named NCLEX01 exit has abended with a system abend code.
The following items are displayed:
NUM PRELOAD - the current number of preloaded procedures
KB PRELOAD - the total preloaded procedure storage
NUM AUTOSHR - the current number of autoshared procedures
KB AUTOSHR - the total autoshared procedure storage
NUM RETAINED - the current number of retained procedures
KB RETAINED - the total retained procedure storage
NUM PRIVATE - the current number of private procedures
KB PRIVATE - the total private procedure storage
TOT EXECREQ - the total number of execution requests
FAST EXECREQ - the number of fast-path execution requests
SLOW EXECREQ - the number of slow-path execution requests
TOT EXECDROP - the total number of execution drop requests
FAST EXECDROP - the number of fast-path execution drop requests
SLOW EXECDROP - the number of slow-path execution drop requests
EXEC FROM PRELD - Number of exec requests satisfied from preload
EXEC FROM ASHR - Number of exec requests satisfied from autoshr
EXEC FROM RETN - Number of exec requests satisfied from retain
EXEC LOAD SHARE - the number of exec request that caused a shared load EXEC LOAD PVT - the number of exec requests that caused a private load EXEC TOTAL LOAD - the total number of execution loads
MOVE AS -> RT - Total moves from autoshr to retain
MOVE RT -> AS - total moves from retain to autoshr
DROP RT - total drops from retain
ACTIVE STACKS - Current number of active stacks
FREE STACKS - current number of available stacks
SYSGET STACKS - number of stacks obtained from free storage
SYSPUT STACKS - number of stacks released to free storage
ACTIVE VWAS - Current number of active verb work areas
FREE VWAS - current number of available verb work areas
SYSGET VWAS - number of verb work areas obtained from free storage SYSPUT VWAS - number of verb work areas released to free storage
System Action:
The request fails.
User Action:
Examine the abend code to resolve the problem.
Reason:
The TCPaccess exit, NMDSPAXS, which passes messages and events has been initialized.
System Action:
TCPaccess messages will be forwarded to regions that are configured to receive them (refer to message N6XA02). If the Data Space is active, it will be updated with TCPaccess events as they occur.
User Action:
None.
Reason:
This message follows N6XA01 when the TCPaccess exit, NMDSPAXS, is initialized. It identifies the (EPS) receiver ID used by NetMaster and/or NetSpy regions to receive copies of TCPaccess log messages.
System Action:
See message N6XA01.
User Action:
None, for information only. Regions are configured to receive copies of TCPaccess messages via TCP/IP Administration options.
Reason:
This message follows N6XA01 and N6X02 when the TCPaccess exit, NMDSPAXS, is initialized.
P1 is the Entry point adddress of the exit.
P2 is the date/time stamp of the Assembly in YYYYMMDDHHMM format.
The message helps to identify the exit code in storage and check its currency.
System Action:
None.
User Action:
None.
Reason:
A session being traced ended and NTS output processing started but not all trace data had arrived.
System Action:
This message is only present when SYSPARM NTSINTSV=YES.
User Action:
This condition may be common on certain sessions depending upon how the session is terminated. Refer also to the SYSPARM NTSCINTV value.
Reason:
NTS did not receive resource statistics for any resources involved in cross domain sessions under the control of the specified SSCP for the most recently expired collection interval. The reason for this is indicated in the supplied reason.
System Action:
None.
User Action:
For resource statistics to be received from another domain: 1. NTS must be executing in that domain. 2. An NTS ISR (Inter System Routing) conversation must be enabled between the systems. 3. NTS in the other domain must have resource statistics collection enabled.
Reason:
NTS has commenced logging of resource statistics to the NTS user exit. These statistics are collected at the expiry of each collection interval and are written to the user exit after waiting for cross domain data to arrive or for the correlation interval (NTSCINTV) to expire.
System Action:
None.
User Action:
None.
Reason:
NTS failed to connect to the NTS database when session awareness started and logging was requested.
System Action:
Processing continues without NTS logging.
User Action:
If NTS logging is required, allocate and open a file with the fileid shown and specify SAWARE LOG=YES.
Reason:
NTS has opened the NTS database in preparation for logging of session awareness data.
System Action:
None.
User Action:
None.
Reason:
An error occurred on the specified NTS database whilst logging session awareness data.
System Action:
NTS logging is disabled.
User Action:
Rectify the problem with reference to the VSAM feedback xx, and specify SAWARE LOG=YES to re-open database logging.
Reason:
A storage shortage has occurred whilst logging session awareness data.
System Action:
NTS logging is disabled.
User Action:
Re-start NTS logging by issuing SAWARE LOG=YES if the storage problem has been resolved.
Reason:
NTS logging has been suspended following a SAWARE LOG=NO command.
System Action:
NTS continues without logging.
User Action:
None.
Reason:
NTS has initialized the database as it was found to be empty.
System Action:
None.
User Action:
None.
Reason:
Provides the date on which the NTS database was last initialized.
System Action:
None.
User Action:
None.
Reason:
The indicated NTS database has been corrupted. The indicated session master record does not contain the required information.
System Action:
NTS logging is suspended.
User Action:
Determine if the NTS database indicated is valid. If it is not then use the correct NTS database. If it is valid, then determine the cause of the corruption. If necessary, re-initialize the NTS database and re-start NTS logging.
Reason:
The user supplied exit routine indicated has terminated prematurely. This indicates an abend or logic error in the exit routine.
System Action:
NTS detaches the NTS exit subtask and continues processing.
User Action:
Review the user supplied NTS exit code.
Reason:
A storage dump of SMF records that are to be passed to the NTS user exit has been requested. Message N22801 contains details of the display requested.
System Action:
None.
User Action:
Refer to message N22801.
Reason:
An inconsistency has been found in the RTM boundary definitions for RTM data that has been sourced remotely via NTS Single Image. The boundary definitions for the resource defined by the DEFCLASS RTM in the remote system are different to the RTM DEFCLASS that this resource matches in the local system.
System Action:
The remote RTM definition for the resource is used instead of the local RTM definition as defined in the the matching RTM DEFCLASS. Processing continues with the remote RTM DEFCLASS.
User Action:
Examine RTM DEFCLASS in both the local and remote NTS and correct the DEFCLASS RTM boundaries.
Reason:
This indicates completion of the transmission of session awareness data to the indicated domain for NTS Single Image. (See also message N72706.)
System Action:
None.
User Action:
None.
Reason:
An ISR command for NTS traffic on the specified link has been accepted (either specifically or by the ISR default) and is in the process of being established. Additional messages(s) will follow to indicate whether the establishment was successful or not.
System Action:
None.
User Action:
None.
Reason:
Contact with a remote NTS system in the indicated domain has been successfully established across an indicated ISR link. The version of the NTS in the remote system is included.
System Action:
None.
User Action:
None.
Reason:
Contact with a remote NTS system across the indicated ISR link has been lost. NTS data can not flow between the two systems. This is probably due to the INMC link becoming disabled, or to an ISR disable for NTS.
System Action:
NTS ISR traffic is suspended on this link. The ISR link will be automatically restarted following a link failure.
User Action:
Determine the cause of the link failure if appropriate.
Reason:
A request has been made to receive session awareness data for the indicated domain from a remote NTS in a different network. It cannot receive cross-network session data from this domain because there is an existing NTS Single Image conversation for inbound session data from this domain.
System Action:
The request is ignored.
User Action:
Review the NTS Single Image conversations for this domain to determine the correct flow of session data. For information about the flow of session data between different domains and networks, see the NTS Single Image data sharing rules in the Administration Guide.
Reason:
Refer to message N72704.
System Action:
None.
User Action:
None.
Reason:
A NTS Single Image conversation is enabled for outbound transmission of session awareness data with the indicated domain. The data transmission has commenced to this domain. Refer to subsequent messages to determine the result of this transmission.
System Action:
None.
User Action:
None.
Reason:
A NTS Single Image conversation is enabled for inbound transmission of session awareness data with the indicated domain. The data transmission has completed successfully.
System Action:
None.
User Action:
None.
Reason:
An NTS Single Image conversation was enabled for inbound sharing of session awareness data with the indicated domain. This conversation is no longer active and NTS has initiated the purging of all session awareness data that has been obtained from this system. This may occur due to session awareness becoming inactive in the remote NTS or the link from the remote NTS system becoming inactive. Subsequent message (N72709) will indicate when this is complete.
System Action:
All session awareness from the remote system is in the process of being purged. The session data will be re-transmitted when the link or data again becomes available.
User Action:
Determine the cause of the purging of data and, if necessary, re-establish the connection.
Reason:
The purging of NTS Single Image data from the indicated domain has completed. Refer to message N72708 for more information.
System Action:
None.
User Action:
None.
Reason:
All resource statistics collected by the indicated SSCP for resources controlled by the local SSCP have been received over an ISR link with NTS in that domain. This message is current to time and date indicated and may be issued to indicate data integrity following a link failure and restart.
System Action:
None.
User Action:
None.
Reason:
An NTSQUERY NCL Verb specified incorrect options.
System Action:
The NCL procedure terminates.
User Action:
Correct the problem and retry.
Reason:
An &NTSQUERY NCL Verb specified conflicting options.
System Action:
The NCL procedure terminates.
User Action:
Correct the problem and retry.
Reason:
NTS was unable to allocate sufficient storage to hold accounting statistics.
System Action:
Accounting statistics will not be kept for some resources.
User Action:
Review storage allocation and usage.
Reason:
NTS attempted to set the RTM boundaries for an LU but the NMVT RU was rejected by the PU with the sense shown in the message.
System Action:
NTS disables RTM collection for the LU.
User Action:
Determine from the sense code whether the control unit supports RTM or not. If not re-define NTS session classes such that controllers which do not support RTM have no RTMCLASS assigned.
Reason:
NTS attempted to set the RTM boundaries for an LU on the puname shown but the NMVT RU was rejected by the PU with the sense code indicating the PU did not support RTM. The number nn of sessions shown were then ignored for RTM class processing.
System Action:
NTS disables RTM collection for the PU.
User Action:
Review RTM/SESSION class definitions.
Reason:
A negative response has been received from the resource indicated to an RTM solicitation for interval based resource statistics. The sense code contained in the response is xxxxxxxx.
System Action:
RTM statistics are no longer solicited from resource aaaa.
User Action:
None.
Reason:
The RTM objective response time (OBJTIME) was changed for the session indicated as the reported boundary values did not correspond to the class values.
System Action:
RTM objectives may not agree with class values.
User Action:
Investigate any other means by which the RTM boundary values may have been altered, for example, NEWS.
Reason:
This message is the reference for the Event Distribution Services event for RTM objectives not being met for a particular session at session end. It describes the rtmclass for the session, the objective response time objt, the actual response time actt, the TOTAL TRANSACTION TIME nnnnnnnn and the TOTAL TRANSACTION COUNT mmmmmmmm.
System Action:
None.
User Action:
None.
Reason:
A specific NTS trace request is ignored as the resource name specified was unknown to NTS.
System Action:
The request is ignored.
User Action:
Determine the status of the resource, check the name entered, and retry the operation if necessary.
Reason:
An STRACE start request has been entered but the requested resource is already being traced.
System Action:
The request is ignored.
User Action:
None.
Reason:
A specific STRACE request to start or stop tracing was entered but the maximum number of resources which can be traced, or excluded from tracing, has been reached.
System Action:
The request is rejected.
User Action:
Determine whether the SYSPARMS NTSMAXTR is sufficient.
Reason:
A specific STRACE request has been entered but cannot be actioned as a previous request involving the same resource is awaiting a response from VTAM. Until the response arrives the resource trace status is unknown.
System Action:
The request is rejected.
User Action:
Retry the request.
Reason:
A request to start or stop tracing a particular resource has been accepted by NTS. However actual tracing of the resource continues as accounting data is being collected.
System Action:
None.
User Action:
None.
Reason:
This message is displayed as a result of a SHOW ISR=NTS OPTIONS command issued from OCS. It indicates the status of the ISR NTS conversation between SOLVE systems that are potentially sharing session awareness data with the local SOLVE sytem.
Fields in message indicate:
LOC SAW - The status of LOCAL session awareness
REM SAW - The status of REMOTE session awareness.
ACT SAW - The actual status of the sharing of session awareness data.
Where each status may be:
NO - Session awareness is not available and the link is started via an ISR ENABLE=NTS LINK=link OPTIONS SAW=NO command.
YES - Session awareness is started both inbound and outbound via an ISR ENABLE=NTS LINK=link OPTIONS SAW=YES command.
IN - Session awareness is started inbound via an ISR ENABLE=NTS LINK=link OPTIONS SAW=INBOUND command.
OUT - Session awareness is started outbound via an ISR ENABLE=NTS LINK=link OPTIONS SAW=OUTBOUND command.
N/A - Session awareness is not available or the link is not started.
System Action:
None.
User Action:
None.
Reason:
Following a LINK START between two SOLVE systems the ISR components in each system have established contact on the specified link.
System Action:
Other SOLVE components that use ISR services, for example NTS and/or AOM, may begin sending to, and requesting data from, the equivalent components in the other SOLVE system.
User Action:
None.
Reason:
ISR contact with the domain shown over linkname has been suspended due to the remote SOLVE system becoming unavailable (for example after LINK STOP request, or failure of the a remote SOLVE system).
System Action:
Processing continues without ISR-ISR transfers.
User Action:
Determine the reason for the suspension. If necessary, re-start the link to the remote SOLVE system.
Reason:
There was insufficient storage available to ISR to process an ISR request.
System Action:
The ISR-ISR communication is terminated.
User Action:
If possible, determine the cause of the storage shortage. If necessary, re-start the ISR-ISR communication after sufficient storage becomes available for the request.
Reason:
An internal error occurred during communications across the indicated ISR link to the indicated domain.
System Action:
The conversation is terminated.
User Action:
Contact your product support representative.
Reason:
An internal error occurred during compression or expansion of the ISR data across the indicated ISR link from the indicated domain.
System Action:
The conversation is terminated.
User Action:
Contact your product support representative.
Reason:
The ISR command issued has completed successfully. The indicated function is either ALTER, ENABLE, DISABLE or RESET.
System Action:
None.
User Action:
None.
Reason:
SOLVE has experienced a storage shortage while attempting to process an ISR command.
System Action:
The ISR command issued is terminated.
User Action:
Review storage allocation and requirements.
Reason:
Invalid ISR command parameter usage. More than one class operand (for example NTS, AOM) has been specified with the OPTIONS... operand. The OPTIONS... operand values vary depending on the class operand specified.
System Action:
The ISR command is terminated.
User Action:
Review ISR command usage. Refer to the Command Reference for details on ISR command usage.
Reason:
Invalid ISR command parameter usage. The specification of both the class indicated and the OPTIONS operand is invalid.
System Action:
The ISR command is terminated.
User Action:
Review ISR command usage. See the Command Reference for details on ISR command usage.
Reason:
Invalid ISR command parameter usage. The classlist (for example, NTS,AOM) specified contains invalid syntax.
System Action:
The ISR command is terminated.
User Action:
Review ISR command usage. See the Command Reference for details on ISR command usage.
Reason:
Invalid ISR command parameter usage. The class specified is invalid.
System Action:
The ISR command is terminated.
User Action:
Review ISR command usage. See the Command Reference for details on ISR command usage.
Reason:
Invalid ISR command parameter usage. The classlist specified contains a duplicated class value clasval.
System Action:
The ISR command is terminated.
User Action:
Review ISR command usage. See the Command Reference for details on ISR command usage.
Reason:
Heading message for SHOW ISR display. One or more N73615 messages follow. Each entry represents an ISR link from the local system to a remote system and displays information relating the link name, domain in which the remote system resides, link status, remote SSCP name, remote system network name, compaction options and the outbound queue limit.
System Action:
None.
User Action:
None.
Reason:
Heading message for the link analysis section of SHOW ISR display. One or more N73617 messages follow. Each entry represents the status of a class of conversation supported on the ISR link and displays information relating the class type (for example, PPO,NTS,NEWS,AOM) and status of the local and remote systems. Also displayed is the actual status which is an interpretation of the local and remote statuses. The interpretation of these statuses is defined by a N73612 message.
System Action:
None.
User Action:
None.
Reason:
Heading message for the status and protocol analysis section of SHOW ISR display. One or more N73617 messages follow. Information is provided relating the enabled/disabled status and whether solicited messages are supported inbound and outbound, for the local and remote systems.
System Action:
None.
User Action:
None.
Reason:
Refer to message N73610.
System Action:
None.
User Action:
None.
Reason:
The message forms the output of the SHOW ISR STATS command where the indicated direction is either IN for inbound or OUT for outbound and ccc..ccc are link compression statistics.
System Action:
None.
User Action:
None.
Reason:
Refer to message N73612.
System Action:
None.
User Action:
None.
Reason:
An invalid link name was specified as an operands to the SHOW ISR command.
System Action:
The SHOW ISR command is terminated.
User Action:
Issue a SHOW ISR command with no link name supplied to review existing link names.
Reason:
Invalid SHOW ISR command parameter usage. Unknown or mutually exclusive parameters have been specified.
System Action:
The SHOW ISR command is terminated.
User Action:
Review SHOW ISR command usage. See the Command Reference for details on SHOW ISR command usage.
Reason:
Invalid SHOW ISR command parameter usage. The classlist has invalid syntax or contains a class that is not one of PPO, NTS, NEWS or AOM.
System Action:
The SHOW ISR command is terminated.
User Action:
Review the SHOW ISR command usage. See the Command Reference for details on SHOW ISR command usage.
Reason:
Invalid SHOW ISR command parameter usage. The class list contains a duplicated entry.
System Action:
The SHOW ISR command is terminated.
User Action:
Review the SHOW ISR command usage. See the Command Reference for details on SHOW ISR command usage.
Reason:
The SHOW ISR command contains invalid operands. The class list contains invalid syntax.
System Action:
The SHOW ISR command is terminated.
User Action:
Review SHOW ISR command usage. See the Command Reference for details on the SHOW ISR command.
Reason:
The SHOW ISR command contains invalid operands. The class list contains the entry indicated, which is not one of PPO, NTS, NEWS and AOM.
System Action:
The SHOW ISR command is terminated.
User Action:
Review SHOW ISR command usage. See the Command Reference for details on the SHOW ISR command.
Reason:
Invalid SHOW ISR command operand usage. The classlist contains a duplicate class.
System Action:
The SHOW ISR command is terminated.
User Action:
Review SHOW ISR command usage. Refer to the SOLVE User Reference for details of the SHOW ISR command.
Reason:
Heading message for SHOW ISRSTATS display. One or more N73702 messages follow. Each entry represents an active ISR remote link domain and the associated class and displays information relating to the statistics for this domain and class. The statistics include the start date and time, the number of inbound messages and bytes, and the number of outbound messages and bytes.
System Action:
None.
User Action:
None.
Reason:
Refer to message N73701.
System Action:
None.
User Action:
None.
Reason:
The NTS database 'fileid' could not be opened.
System Action:
NTSDBMOD or SHOW SKEEP processing terminates.
User Action:
Allocate and open the appropriate fileid for the NTS database.
Reason:
An error occurred on the NTS database 'fileid'.
System Action:
NTSDBMOD or SHOW SKEEP processing terminates.
User Action:
Determine the cause of the error with reference to the VSAM feedback xx and retry.
Reason:
NTSDBMOD processing has successfully completed.
System Action:
None.
User Action:
None.
Reason:
NTSDBMOD processing terminated following an error.
System Action:
None.
User Action:
Refer to other messages issued to determine the cause of the error.
Reason:
Indicates the number nnnn and record type rectype (MASTER or SESSION) records actioned (UPDATED, DELETED or READ) following an NTSDBMOD command.
System Action:
None.
User Action:
None.
Reason:
Informational message identifying a particular session stored on the NTS database. This message provides the two network names and resource names identifying a unique session pair for which the details in message N73E07 apply.
System Action:
None.
User Action:
None.
Reason:
Specifies the session keep count limit nnn and current number mmm of session incidences found in the NTS database.
System Action:
None.
User Action:
None.
Reason:
SHOW SKEEP processing completed after selecting the number of records shown for processing.
System Action:
None.
User Action:
None.
Reason:
The SHOW SKEEP or NTSDBMOD process with ID=aaaa has been cancelled via the NTSDBMOD CANCEL=aaaa command.
System Action:
None.
User Action:
None.
Reason:
The VSAM dataset allocated for use as the NTS Database is incompatible with this release of NTS. This will occur if a database loaded by an NTS Version 2.1 system, or earlier, is allocated for use by an NTS Version 2.2 system.
System Action:
No further I/O is performed on the NTS Database.
User Action:
Refer to message N73F02.
Reason:
Refer to message N73F01.
System Action:
Refer to message N73F01.
User Action:
As specified in the message text.
Reason:
A VSAM error occurred during an I/O operation performed by NTS on the NTS Database. The VSAM feedback code is X`xx'.
System Action:
Discontinue I/O to the NTS Database.
User Action:
Review the integrity of the VSAM dataset allocated as the NTS Database.
Reason:
The NTS user modifiable RU, FMH, and Sense Code table failed to load during NTS initialization.
System Action:
Processing continues. An attempt is made to load the user modifiable table when session awareness is started using the SAWARE START command.
User Action:
Ensure the table is available and that it has been assembled and linked correctly. The table must be available before session awareness starts.
Reason:
The user modifiable RU, FMH, and Sense Code table failed verification during NTS initialization.
System Action:
Processing continues. An attempt is made to reload the user modifiable table when session awareness is started using the SAWARE START command.
User Action:
Ensure the correct user modifiable table is available and that it has been assembled and linked correctly. The table must be corrected before session awareness starts.
Reason:
An NTS command (SAWARE, STRACE, NTSMOD, NTSDBMOD or MAISESS) has required operands missing.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for appropriate command syntax requirements.
Reason:
An NTS command (SAWARE, STRACE, NTSMOD, NTSDBMOD or MAISESS) contains a keywrd operand which specifies a value which is not valid.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
An NTS command (SAWARE, STRACE, NTSMOD or NTSDBMOD) has an unrecognized operand keyword.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
An STRACE MONITOR request has been accepted.
System Action:
Trace monitoring commences for the resource nominated on the STRACE command.
User Action:
None.
Reason:
NTS trace monitoring has been terminated.
System Action:
Trace message delivery ceases for the user.
User Action:
None.
Reason:
A request to end NTS trace monitoring has been ignored as tracing is not active for the user.
System Action:
The request is ignored.
User Action:
None.
Reason:
An attempt was made to start session awareness processing but it was found to be already active.
System Action:
The request is ignored.
User Action:
None.
Reason:
An attempt was made to stop session awareness processing but it was found to be already inactive.
System Action:
None.
User Action:
None.
Reason:
Conflicting operands were entered on an NTS command, either SAWARE, STRACE, NTSMOD, NTSDBMOD or MAISESS.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
The SAWARE command LOG request has been accepted and will be completed when the next session is processed on the NTS output queue.
System Action:
None.
User Action:
None.
Reason:
NTS failed to open the NTS database in response to a SAWARE LOG=YES command.
System Action:
NTS will continue processing without attempting I/O to the Database.
User Action:
Review the procedure for enabling NTS to connect to the Database. Refer to message N74H04.
Reason:
A request to trace a resource via an STRACE command was entered, however, session awareness was started without the VTAM interface, that is, using the SAWARE START NOVTAM command.
System Action:
The request is ignored.
User Action:
If it is necessary to trace resources then session awareness must be re-started without the NOVTAM option.
Reason:
An NTS command, NTSMOD, NTSMOD, MAISESS or SHOW SKEEP, has required operands missing.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
The value specified for the operand shown in the message is invalid.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
The operand shown in the message was not recognized for the command NTSMOD, NTSDBMOD, MAISESS or SHOW SKEEP.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
Required NTSDBMOD, NTSMOD, MAISESS or SHOW SKEEP operands are missing, or are invalid.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
There was insufficient storage to process a SHOW SKEEP or NTSDBMOD SKEEP request.
System Action:
Command processing terminates.
User Action:
Investigate the storage problem.
Reason:
A SHOW SKEEP or NTSDBMOD SKEEP request has been accepted.
System Action:
Processing of the command commences.
User Action:
None.
Reason:
An NTSMOD command found no sessions of the type requested to select for modification.
System Action:
None.
User Action:
None, if necessary correct the session and retry the operation.
Reason:
Indicates the number, nnnn, of active sessions processed by an NTSMOD command.
System Action:
None.
User Action:
None.
Reason:
The NTSDBMOD process with ID=aaaa is not currently executing. Because of the asynchronous nature of the NTSDBMOD command, it is possible for several concurrent invocations of the command to exist. Attempts to issue NTSDBMOD CANCEL=aaaa commands for NTSDBMOD processes not currently executing will result in this message.
System Action:
None.
User Action:
Issue SHOW NTSDBMOD command to show processes currently executing.
Reason:
The operands specified on an NTSDBMOD or SHOW SKEEP command are mutually exclusive.
System Action:
None.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
An NTSMOD RECORD=RTM command was issued. An attempt was made to obtain the RTM data for the indicated resource in the indicated network, however the data was not available either in the remote or local system.
System Action:
None.
User Action:
Ensure the resource exists in the indicated network and the required RTM data is available in the domain where the resource resides. If the data is available, then ensure the classes for RTM data collection are the same in both the remote and local NTS and the data is being distributed correctly with the necessary ISR connections for NTS Single Image.
Reason:
An NTSMOD RECORD=ACC command was issued. An attempt was made to obtain the accounting data for the network qualified resource pair indicated, however the data was not available either in the remote or local system.
System Action:
None.
User Action:
Ensure the resources exist in the indicated networks and the required accounting data is available for the indicated session in the source (primary) domain. If the data is available, then ensure the classes for accounting data collection are correct and the same in both the remote and local NTS and the data is being distributed correctly with the necessary ISR connections for NTS Single Image.
Reason:
An NTSMOD RECORD=RTM command was issued. The RTM data is in the process of being obtained from either a remote or local NTS for all the LUs connected to the indicated PU.
System Action:
None.
User Action:
None.
Reason:
An NTSMOD RECORD=RTM command was issued. The RTM data is in the process of being obtained from either a remote or local NTS for the indicated LU.
System Action:
None.
User Action:
None.
Reason:
An NTSMOD RECORD=RTM command was issued, the request was for a resource other than a PU or an LU. This command is valid only for an PU or LU resource.
System Action:
The request is ignored.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
An NTSDBMOD REFNET= command was issued. The network indicated on the command is unknown to NTS.
System Action:
The command is ignored.
User Action:
Ensure the REFNET specified on the command is valid. If it is valid then ensure that this NTS is connected through ISR and established correctly for NTS Single Image processing. If necessary, correct and retry.
Reason:
A DEFCLASS, REPCLASS or DELCLASS command could not be processed due to a lack of storage.
System Action:
The command is rejected.
User Action:
Investigate the storage problem.
Reason:
Operands required on a DEFCLASS, REPCLASS or DELCLASS command were missing.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
A DEFCLASS, REPCLASS or DELCLASS command specified a value which was invalid on the indicated operand.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
A DEFCLASS, REPCLASS or DELCLASS command specified an operand which was invalid.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
A DEFCLASS command specified a name clsname which was an existing class name.
System Action:
The command is rejected.
User Action:
Use REPCLASS or change the class name on the DEFCLASS. Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
A DELCLASS command specified a class name which was not found.
System Action:
The command is ignored.
User Action:
Correct the classname and retry.
Reason:
An NTS class definition of the type (SESSION, SAW or RTM) and name shown, was actioned (DEFINED, REPLACED or DELETED).
System Action:
None.
User Action:
None.
Reason:
A DEFCLASS or REPCLASS command specified conflicting operands.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
An attempt was made to add a session class but the class attributes were identical to an existing session class.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
NTS could not send a CNM request due to insufficient storage.
System Action:
CNM request not sent.
User Action:
Investigate the storage problem.
Reason:
An SAWARE or STRACE command with the QUEUE operand specified has been issued when the CNM ACB is not open.
System Action:
NTS will queue the command to be executed after the CNM ACB has been opened.
User Action:
Open the CNM ACB via the $SN CNM parameter group or issue the CNM START command.
Reason:
An attempt was made to issue a command requiring session awareness to be active (eg. SAWARE STOP, STRACE ) while session awareness is inactive.
System Action:
None.
User Action:
Start session awareness.
Reason:
Response to the STATUS command, indicating that the NTS VTAM ACB is closed, and so no active data is available for display.
System Action:
None.
User Action:
None.
Reason:
Response to the STATUS command, giving the status of session awareness processing and database logging.
System Action:
None.
User Action:
None.
Reason:
Response to the STATUS command, giving the status of session trace processing.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to modify the NTS ACB name but the ACB was currently open.
System Action:
Command is rejected.
User Action:
Stop session awareness before changing the NTS ACB name.
Reason:
A SYSPARM NTSACBNM command entered to change the NTS ACB name failed on a MODCB macro with the return codes shown.
System Action:
None.
User Action:
Determine the reason for failure from the MODCB return codes and rectify the problem.
Reason:
An attempt was made to change the global NTS accounting or resource statistics option while session awareness was active, to a value other than 'NO'.
System Action:
Command is rejected.
User Action:
Stop session awareness to change the SYSPARM NTSACCT value to other than 'NO'.
Reason:
Response to the STATUS command, giving the status of session awareness processing and database logging. Session Awareness is active in NOVTAM mode.
System Action:
None.
User Action:
None.
Reason:
This is the heading line for a SHOW DEFCLASS display. Details follow in one or more N74803 messages which contain information on the defined DEFCLASS' including:
SESSION - defined session class name.
PRI-NAME - primary session partner name
SEC-NAME - secondary session partner name
COS - Class-of-Service name (COS)
ER - session Explicit Route number
VR - session Virtual Route number
TP - Transmission Priority
CL - session class (SD/XD/XN)
TY - session type (LL/SL/SP/SS)
SAWCLASS - the session awareness class associated with this class
RTMCLASS - the RTM class associated with this class
Also displayed is one or more N74802 messages which is a heading line for further information from the command. Details follow in one or more N74831 messages which contain:
SOURCE - the source of the session (LOCAL/REMOTE)
SSCPNAME - for a remote session, the source
SSCP APPNCOS - the APPN Class-of-Service
APPNTP - the APPN Transmission Priority
Note: An asterisk indicates all of the options for the display are acceptable.
System Action:
None.
User Action:
None.
Reason:
Refer to N74801.
System Action:
None.
User Action:
None.
Reason:
Refer to N74801.
System Action:
None.
User Action:
None.
Reason:
This is the heading message for a SHOW DEFCLASS SAW command. One or more N74805 messages follow which contain details for each SAW class processed, including:
CLASS - The defined SAW class name
KEEP - SAW data retention (YES/NO/LOCAL)
LOG - Logging of SAW data (YES/NO)
ACCT - Accounting data accumulation (YES/NO)
ITRC - Initial trace queue depth
FTRC - Final trace queue depth
EVENT - Trigger event generation (YES/NO)
System Action:
None.
User Action:
None.
Reason:
Refer to N74804.
System Action:
None.
User Action:
None.
Reason:
Heading message for a SHOW STRACE display. One or more messages N74807 follow with details on current NTS trace activity including:
NAME - Name of a specific resource, *GLOBAL* for global tracing.
TYPE - Type of resource being traced (LU/PU/CDRM).
STATUS - Actual tracing status, one of:
ACTIVE - Tracing active
INACT - Tracing inactive
ACT/PND - Activation pending; the requested resource may not be active. When the resource is available, VTAM will send trace data to NTS.
ACT/A - Accounting tracing only; trace data is discarded.
ACT/P - Tracing active; partial trace data retained.
ACT/C - Tracing active; complete trace data retained.
ACT/A/P - Tracing active; partial trace data and accounting data retained. ACT/A/C - Tracing active; complete trace data and accounting data retained. INACT/A - Accounting tracing; global tracing selected.
System Action:
None.
User Action:
None.
Reason:
Refer to N74806.
System Action:
None.
User Action:
None.
Reason:
Signifies the end of an NTS message display sequence.
System Action:
None.
User Action:
None.
Reason:
Additional operands found on a SHOW DEFCLASS command were found to be invalid.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
Additional operands found on a SHOW STRACE command were found to be invalid.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
Heading message for a SHOW NTSSTATS display. Following this message, two N74812 messages are displayed. The first shows statistics since the last time this command was issued, the second shows the totals since NTS was started. N74812 includes statistics on the number of session awareness and session trace buffers received from VTAM since session awareness was started, the number of entries processed from these buffers, and the statistics concerning the logging of session data to the NTS database on session end. Details include:
Type - Interval COUNTS or TOTALS.
SAWBUF - Number of session awareness buffers processed.
SAWENT - Number of session awareness entries that were processed from buffers received from VTAM.
TRCBUF - Number of session trace buffers processed.
TRCENT - Number of trace PIU entries that were processed from the buffers received from VTAM.
LOGGED - Number of session incidences that were logged to the NTS database.
READS - Number of records read from the NTS database.
ADDS - Number of records added to the NTS database.
UPDS - Number of records updated on the NTS database.
DELS - Number of records deleted from the NTS database.
System Action:
None.
User Action:
None.
Reason:
Refer to message N74811 for details on this message.
System Action:
None.
User Action:
None.
Reason:
Heading line message for a SHOW DEFCLASS RTM display. One or more N74814 messages will follow, each with details of an RTM class including:
CLASS - Name of the defined RTM class.
OBJTIME - Objective response time.
OBJ% - Objective percentage.
RTMDEF - Delimitation for response time measurement (FIRST/KEYBD/CDEB/LAST).
BNDY-n - 'n' Boundary time values for (up to) four boundaries.
System Action:
None.
User Action:
None.
Reason:
Refer N74813.
System Action:
None.
User Action:
None.
Reason:
This message ends the SHOW STRACE display. The number of specific trace requests currently active is displayed as aaaa. The maximum number of current traces allowed is displayed as bbbb and may be controlled via the SYSPARMS NTSMAXTR command. These may be explicit STRACE requests or implicit trace requests issued for the collection of accounting data.
System Action:
If aaaa equals bbbb then any subsequent trace requests, explicit or implicit, will be ignored.
User Action:
None.
Reason:
Heading message for SHOW DEFCLASS RESOURCE display. One or more N74817 messages follow, each representing a resource class definition. Information includes:
CLASS - The name of the defined resource class.
LU, PU and LINK - names matched by members of this class
STATS - whether or not resource statistics are to be kept.
LIMIT - number of collection intervals before the oldest interval is overwritten. RTMCLASS - the RTMCLASS used in collecting RTM statistics.
System Action:
None.
User Action:
None.
Reason:
Refer to message N74816.
System Action:
None.
User Action:
None.
Reason:
Heading message for SHOW NTSUSER display. One or more N74819 messages follow, each representing a different concurrent user of NTS. Each message contains:
USERID - The user id of the active user.
NTSVIEW - Details of the current NTS view for the user.
D/B - whether the user is connected to the NTS database.
NCLBASE, NCLPROC, NCLID - the current NTS NCL procedure executing.
System Action:
None.
User Action:
None.
Reason:
Refer to message N74818.
System Action:
None.
User Action:
None.
Reason:
Heading message for SHOW NTSDBMOD display. One or more N74821 messages follow, each representing a currently executing invocation of a NTSDBMOD or SHOW SKEEP command. Each entry provides:
USERID - details of the userid that issued the command.
COMMAND - the command type (NTSDBMOD/SHOW SKEEP)
ID - the process identifier.
READ-CNT - the number of records in the NTS database read by this process up to the time the SHOW NTSMOD command was issued.
System Action:
None.
User Action:
None.
Reason:
Refer to message N74820.
System Action:
None.
User Action:
None.
Reason:
Following any SHOW DEFCLASS command this message ends the display and provides the number nnnn of NTS class entries processed. Following a SHOW NTSDBMOD command nnnn provides the number of currently executing invocations of the NTSDBMOD and SHOW SKEEP commands.
System Action:
None.
User Action:
None.
Reason:
Refer to N74801.
System Action:
None.
User Action:
None.
Reason:
A SHOW NTS command referred to a resource or session which was not active, or requested a display for session data which was not available for the particular session.
System Action:
None.
User Action:
None.
Reason:
An operand specified on the SHOW NTS command was invalid.
System Action:
The command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
Operands on the SHOW NTS command were invalid or requested conflicting information.
System Action:
Command is rejected.
User Action:
Correct the command and retry the operation. Refer to the command help for the appropriate command syntax requirements.
Reason:
This message delimits a SHOW NTS display of multiple lines.
System Action:
None.
User Action:
None.
Reason:
Heading message for SHOW NTS resource type display, or a subheading for the SHOW NTS (no operands) display. Details in message N74907 provide the following:
SUBAREA - The subarea number of the resource.
TYPE - The resource type of the subarea (SSCP or NCP). This value may be unknown (UNKN) due to NTS being aware of this subarea (for example, via a ROUTE-TEST), but NTS does not know the resource type.
NAME - The VTAM name of the resource.
NETID - The network for the subarea.
ACT-RSC - The total number active resources known to NTS.
ACT-PU - The total number of PUs known to NTS.
ACT-LU - The total number of LUs known to NTS.
System Action:
None.
User Action:
None.
Reason:
Refer to message N74906.
System Action:
None.
User Action:
None.
Reason:
Heading message for N74009 detail message produced by the SHOW NTS command. Total numbers of SSCP-SSCP, SSCP-PU, SSCP-LU and LU-LU sessions currently active to NTS are displayed.
System Action:
None.
User Action:
None.
Reason:
Detail message following N74908 gives session counts as described for message N74908.
System Action:
None.
User Action:
None.
Reason:
The message displays the headings for SHOW NTS resource display. It follows message N74907 that identifies an subarea, and is followed by one or more N74912 messages with the following details of the resources selected by the command:
Displays the name of the resource.
Identifies the type of resource: AL (alias), LU, LS (ALS), PU, or SS (SSCP).
Displays the number of sessions where the resource is the primary session partner.
Displays the number of sessions where the resource is the secondary session partner.
System Action:
None.
User Action:
None.
Reason:
Refer to N74911.
System Action:
None.
User Action:
None.
Reason:
The message displays the headings for the SHOW NTS session display. One or more N74915 messages follow to provide details on the required session.
Identifies the primary session partner.
Identifies the secondary session partner.
Identify the network subarea (SUBA#) and element address (ELEM#) of both session partners.
Displays the start time and date for the session.
Display the current number of trace entries on the initial (ITR) and final (FTR) trace queues.
System Action:
None.
User Action:
None.
Reason:
Refer to message number N74914 for description.
System Action:
None.
User Action:
None.
Reason:
Heading message for a SHOW NTS session accounting display. Details follow in N74917 messages which contain the primary and secondary session partner names (PRI-NAME and SEC-NAME), the time accounting commenced for the session (AC-START), the inbound and outbound byte counts (I-BYTES and O-BYTES), PIU counts (I-CNT and O- CNT) and average PIU lengths (I-AVG and O-AVG).
System Action:
None.
User Action:
None.
Reason:
Information line for the SHOW NTS session accounting display. Refer to message number N74916 for a description of these fields.
System Action:
None.
User Action:
None.
Reason:
Heading line for a SHOW NTS session class display. Details follow in messages N74919 which contain:
PRI-NAME - The primary session partner name.
SEC-NAME - The secondary session partner name.
TYPE - Session type (SDOM=same domain, XDOM=cross domain, XNET=cross net, DISC=disconnected).
SAWCLASS - session awareness class name for the session.
COSNAME - Class of service entry name for the session.
ER - The explicit route.
RE - The reverse explicit route (RER).
VR - The virtual route.
TP - The transmission priority.
LG - Log option (N=no, A=All, S=Summary, E=Error, D=data)
AC - Accounting option (Y=Yes, N=No)
ITRC, FTRC - The requested depth of the initial (ITRC) and final (FTRC) trace queues.
System Action:
None.
User Action:
None.
Reason:
Information line for the SHOW NTS session class display. Refer to message number N74918 for a description of the fields.
System Action:
None.
User Action:
None.
Reason:
Heading for SHOW NTS VR/ER or VR/ER= display. One or more N74921 entries follow, each representing a specific explicit or virtual route stage. Each entry contains:
OSA-NAME, OSA-ADDR - The origin subarea name and network address.
DSA-NAME, DSA-ADDR - The destination subarea name and network address. ER - Explicit route number.
SESSIONS - The total number of sessions active on the displayed virtual or explicit route.
If the SHOW NTS VR command is issued the the following additional information is displayed:
VR - Virtual route number.
RER - Reverse explicit route number.
System Action:
None.
User Action:
None.
Reason:
Information line for the SHOW NTS session class display. Refer to message number N74920 for a description of the fields.
System Action:
None.
User Action:
None.
Reason:
The message displays the headings for the SHOW NTS display when no operands were specified. One or more N72922 messages follow, one for each network known to this NTS. If a remote network is inactive (for example, there is no active configured ISR link), the counter fields display "-".
Displays the network name.
Displays the total number of SSCPs in this network of which NTS is aware.
Displays the total number of PUs in the network of which NTS is aware.
Displays the total number of LUs in the network of which NTS is aware.
Displays the total number of cross network LUs in the network of which NTS is aware.
Displays the total number of cross network SSCP sessions in the network of which NTS is aware.
Displays the total number of sessions in the network of which NTS is aware.
System Action:
None.
User Action:
None.
Reason:
Information line for the SHOW NTS session class display. Refer to message number N74922 for a description of the fields.
System Action:
None.
User Action:
None.
Reason:
A SHOW NTS command requested data for a specific network using the NETID= operand. This network is not known to NTS.
System Action:
The command is ignored.
User Action:
Correct the NETID operand and retry. Issue a SHOW NTS command for information on the networks that are known to NTS at this time. If the required network is not available, then ensure the data is being shared correctly between NTS systems for NTS Single Image by examining the ISR links and/or the status of the NTS in the required network.
Reason:
An &NTSREAD statement was issued but no current &NTSVIEW was found.
System Action:
The procedure is terminated.
User Action:
Issue the appropriate &NTSVIEW before an &NTSREAD statement.
Reason:
The options specified on an &NTSREAD statement conflict with the type of
NTSVIEW established.
System Action:
Procedure is terminated.
User Action:
Check options on the &NTSREAD and/or the &NTSVIEW.
Reason:
Placed in &SYSMSG when an &NTSVIEW is attempted for active data but session awareness has not been started.
System Action:
Processing continues.
User Action:
None.
Reason:
Placed in &SYSMSG when an &NTSREAD for history is requested but no NTS database is available.
System Action:
Processing continues.
User Action:
None.
Reason:
Placed in &SYSMSG when &NTSREAD experiences an error on the NTS database.
System Action:
Processing continues.
User Action:
Determine the cause of the failure with reference to the VSAM feedback xx.
Reason:
This message is used to provide a hex/character dump display of an APPN Route Selection Control Vector. The RSCV is used to produce the APPN session route display in NTS. Refer to message TSAR10 for further details. The following fields are shown:
+oooo describes the offset (in hexadecimal) of this part of the display. xxxxxxxx contains a hexadecimal dump of this part of the display. cccccccccccccccc contains a character dump of this part of the display.
System Action:
None.
User Action:
None.
Reason:
This message is used to return APPN session route information to an NCL procedure following an &NTSREAD verb for an &NTSVIEW TYPE=APPNRSCV. The message describes the session route through the network. This message appears once for each APPN node on the session path. The following fields are shown:
tg# The TG# of the Transmission Group connecting the target node
cpnetid The Network Id of the target node
cpname The Node Name of the target node
tgtype The transmission group type of the transmission group (APPN, VRTG ir ICHG)
isl 'Y' if the link represents an intersubnetwork link, else 'N'
System Action:
None.
User Action:
None.
Reason:
Insufficient storage was available to process the NTSVIEW NCL statement.
System Action:
None.
User Action:
Review storage allocation and usage.
Reason:
An attempt was made to set a new &NTSVIEW using the index parameter, however the progression from the current view to the next one is invalid.
System Action:
&NTSVIEW fails with RETCODE 8.
User Action:
Contact your product support representative.
Reason:
No active session data is available because session awareness has not initialized successfully.
System Action:
None.
User Action:
The Customizer parameter group SAW controls the initial activation of session awareness using the SAWARE command and, in Update mode, can be used to control session awareness through the Currently Active field.
Review the Initialization Log for the SAW parameter group to determine the status. If necessary, set the Currently Active field to YES and press F6 (Action).
Note: The CNM interface is a prerequisite for activation of Session Awareness. Review the CNM parameter group to ensure CNM has started.
Reason:
NTS has not been connected to the NTS Database.
System Action:
None.
User Action:
The VSAM dataset acting as the NTS Database must be allocated and opened before NTS can access the database.
Reason:
Neither active or history session data is available, that is. session awareness has not been activated and NTS is not connected to the NTS database.
System Action:
None.
User Action:
The VSAM dataset acting as the NTS database must be allocated and opened before NTS can access the database. This gives NTS access to history data. To start session awareness, use the SAWARE START command. This gives NTS access to active data.
Reason:
The specified reference network is not known to NTS. Data for this network is not available.
System Action:
None.
User Action:
Ensure the correct NETID supplied is supplied. If it is, check that session data is being shared by NTS Single Image.
For information about sharing session data using NTS Single image, see the Administration Guide.
Reason:
An invalid date and/or time has been specified on an &NTSVIEW verb.
System Action:
The NCL procedure in terminated.
User Action:
Correct the NCL and retry the operation.
Reason:
The NTS ACB has been closed as NTS has been stopped.
System Action:
None.
User Action:
None.
Reason:
The NTS CNMRU request type CNMRU-type has been accepted for processing by VTAM.
System Action:
None.
User Action:
None.
Reason:
The CNMRU request indicated in the message and used to control NTS processing was rejected by VTAM with the sense code shown.
System Action:
Updates NTS status as appropriate for the request.
User Action:
Investigate the cause of the rejection.
Reason:
An NTS request was targeted to be sent across the CNM interface but the originating user was not authorized for that type of request.
System Action:
Request is rejected.
User Action:
None. If this function is required, refer the problem to your systems administrator to review your command authority.
Reason:
An attempt was made to start NTS session awareness processing but the system VTAM level was not at a level that supports the function.
System Action:
Request is rejected.
User Action:
Check that the VTAM level of the system is Version 2.2 or greater.
Reason:
A request was made to start NTS session awareness processing but it was already active.
System Action:
Request is ignored.
User Action:
None.
Reason:
A request to start NTS processing failed as the session between NTS and VTAM did not start. An accompanying message provides the reason for failure.
System Action:
NTS remains inactive.
User Action:
Determine reason for failure. Correct and retry.
Reason:
An NTS request requiring that session awareness be started could not be processed as session awareness was not active.
System Action:
Request is rejected.
User Action:
Start session awareness and retry the request.
Reason:
NTS has started session awareness processing but the VTAM session used to collect trace data failed to start.
System Action:
NTS processing continues with trace functions disabled.
User Action:
Determine the cause of error with reference to the SYSPARMS NTSACBNM= parameter.
Reason:
An attempt was made to deallocate the VTAM trace buffers while NTS tracing was active.
System Action:
Request is rejected.
User Action:
Stop all tracing, and if necessary turn global accounting off, before retrying the request.
Reason:
An NTS request was received to start a function which was already enabled, or in the process of starting.
System Action:
Request is ignored.
User Action:
None.
Reason:
A stop session awareness processing request has been detected by NTS and shutdown is in progress.
System Action:
NTS terminates when all log activity ceases.
User Action:
None.
Reason:
A request requiring that session awareness be inactive was invalidly received while session awareness was active.
System Action:
Request is rejected.
User Action:
Stop session awareness to issue the request.
Reason:
A request to stop global tracing has been accepted by NTS. However the NTS global accounting function is active and actual tracing continues to collect accounting data.
System Action:
Request is accepted.
User Action:
None.
Reason:
NTS has been started as a dormant NTS system via an SAWARE START NOVTAM command. NTS will not receive session awareness data from the local VTAM. Provided the correct ISR links are established, this NTS system will be able to receive session awareness data from a remote NTS system for NTS Single Image processing.
System Action:
NTS is started as a dormant NTS system.
User Action:
None.
Reason:
NTS session awareness processing has commenced.
System Action:
None.
User Action:
None.
Reason:
The NTS ACB name shown in the message failed to open with the error code shown.
System Action:
NTS session awareness start processing fails.
User Action:
Determine the reason for failure from the error code. Correct and retry.
Reason:
NTS session awareness processing has terminated.
System Action:
None.
User Action:
None.
Reason:
NTS could not start its session with VTAM due to the error reason codes shown.
System Action:
Session awareness processing is terminated.
User Action:
Determine the cause of the problem. Correct and restart NTS.
Reason:
An error occurred during a VTAM receive operation for NTS session awareness data.
System Action:
Session awareness processing terminates.
User Action:
Determine the cause of the problem and restart NTS. The error codes specified in the message text refer to the VTAM RPL completion and feedback codes following the RECEIVE macro completion, and are described in the VTAM Programming manual.
Reason:
NTS has closed its ACB.
System Action:
None.
User Action:
None.
Reason:
NTS could not continue due to a lack of storage.
System Action:
NTS session awareness processing terminates.
User Action:
Investigate the storage problem.
Reason:
During NTS closedown an error occurred ending the session with VTAM.
System Action:
Closedown continues.
User Action:
Investigate error with reference to the reason codes.
Reason:
During NTS intensive mode recording (SYSPARMS NTSINTSV=YES) the SAW buffer is written to the log.
System Action:
The SAW buffer is written to the log.
User Action:
None.
Reason:
An attempt to build an in-storage index for use by NTS failed due to a lack of storage.
System Action:
NTS processing continues but review functions are unavailable.
User Action:
Investigate the storage problem.
Reason:
NTS is terminating and has placed the number 'nnnn' of sessions shown on the output queue for processing.
System Action:
Final termination awaits completion of output processing.
User Action:
None.
Reason:
NTS has started collecting data as per specified parameters, where 'status' is one of SELECTIVE, GLOBAL, ACTIVE or NOT ACTIVE and 'type' is one of ACCOUNTING or RESOURCE STATISTICS.
System Action:
None.
User Action:
None.
Reason:
The NTS user-modifiable RU, FMH, and Sense Code table failed to load when session awareness was started.
System Action:
Session awareness start is aborted.
User Action:
Ensure the table is available and that it has been assembled and linked correctly.
Reason:
The user-modifiable RU, FMH, and Sense Code table failed verification when session awareness was started.
System Action:
Session awareness start is aborted.
User Action:
Ensure the correct user modifiable table is available and that it has been assembled and linked correctly. The table must be corrected before session awareness is started.
Reason:
As a result of starting NTS session awareness, VTAM has completed sending notification of all sessions that were active prior to the start of session awareness, that is, VTAM has completed WARM STARTING NTS. The number of active session sent by VTAM is indicated by 'nnnnnnnn'.
System Action:
None.
User Action:
None.
Reason:
NTS could not acquire sufficient storage to keep all session data requested. Some session data is lost.
System Action:
Processing continues.
User Action:
Investigate storage or SAW class keep options.
Reason:
A buffer received from VTAM carrying session awareness data was not the next in the sequence. The number of buffers lost is nnn which represents the difference between the expected and actual sequence numbers received from VTAM.
System Action:
Processing continues.
User Action:
Check SYSPARM NTSSAWBF values, as this failure could indicate that VTAM has insufficient buffers allocated.
Reason:
A session notification has been received via NTS Single Image, the local NTS system is already aware of the indicated session.
System Action:
NTS updates the session information with the new session data.
User Action:
None.
Reason:
Intensive message recording (SYSPARMS NTSINTSV={YES|name}) is active for NTS. The SAW buffer for a session start from VTAM is written to the log in dump format.
System Action:
The SAW buffer is written to the log.
User Action:
Collect the activity log output for Technical Support if required.
Reason:
Intensive message recording (SYSPARMS NTSINTSV={YES|name}) is active for NTS. The SAW buffer for a session end from VTAM is written to the log in dump format.
System Action:
The SAW buffer is written to the log.
User Action:
Collect the activity log output for Technical Support if required.
Reason:
Intensive message recording (SYSPARMS NTSINTSV={YES|name}) is active for NTS. The SAW buffer for a session end from VTAM is written to the log in dump format.
System Action:
The SAW buffer is written to the log.
User Action:
Collect the activity log output for Technical Support if required.
Reason:
Intensive message recording (SYSPARMS NTSINTSV={YES|name}) is active for NTS. The SAW buffer for a session start from ISR is written to the log in dump format.
System Action:
The SAW buffer is written to the log.
User Action:
Collect the activity log output for Technical Support if required.
Reason:
Intensive message recording (SYSPARMS NTSINTSV={YES|name}) is active for NTS. The SAW buffer for a session end from ISR is written to the log in dump format.
System Action:
The SAW buffer is written to the log.
User Action:
Collect the activity log output for Technical Support if required.
Reason:
Intensive message recording (SYSPARMS NTSINTSV={YES|name}) is active for NTS. The SAW buffer for a session end from ISR is written to the log in dump format.
System Action:
The SAW buffer is written to the log.
User Action:
Collect the activity log output for Technical Support if required.
Reason:
The session between NTS and VTAM used to collect session trace data has become active.
System Action:
NTS allows session trace requests.
User Action:
None.
Reason:
The session between NTS and VTAM used to collect session trace data has terminated.
System Action:
All tracing is disabled.
User Action:
None. If necessary, determine the cause of this session failure, correct the failure and retry session tracing.
Reason:
An error occurred whilst attempting to start the session between NTS and VTAM used to collect session trace data.
System Action:
Trace processing is disabled.
User Action:
Determine the cause of the error from the message. Correct and retry.
Reason:
An error occurred receiving session trace data from VTAM.
The error-reason-code contains the error codes as set in the RPL or if there is a short on storage condition, then the VTAM RECEIVE retry condition. The following reason codes will be issued in this circumstance:
- VTAM TEMPORARY SHORT-ON-STORAGE This condition is temporary if a short on main storage error code is received from the VTAM RECEIVE. The receive is retried every 5 seconds.
- VTAM PERMANENT SHORT-ON-STORAGE This condition is permanent if a short on main storage error code is received from the VTAM RECEIVE for 12 consecutive retries (1 minute).
System Action:
Under most error conditions, the trace processing is terminated
When a temporary short on storage condition is raised, the VTAM RECEIVE will be retried automatically.
The trace processing can be restarted with a STRACE START command.
User Action:
Determine the cause of the error from the message. Correct and retry.
Reason:
The NTS ACB has been closed.
System Action:
All session trace and session awareness processing has terminated.
User Action:
None.
Reason:
NTS trace processing experienced a storage shortage.
System Action:
Trace processing terminates.
User Action:
Investigate the storage shortage.
Reason:
An error occurred whilst NTS was closing its session trace session with VTAM.
System Action:
Termination continues.
User Action:
Investigate the problem with reference to the reason codes.
Reason:
During NTS intensive mode recording (SYSPARMS NTSINTSV=YES) the VTAM trace buffer is written to the log.
System Action:
The vtam trace is written to the log.
User Action:
None.
Reason:
There was insufficient storage to process all session trace entries passed to NTS from VTAM. 'nnnnnnnn' sessions were lost as a result of this condition.
System Action:
Processing continues - some data is lost.
User Action:
Investigate the storage problem.
Reason:
Dump of VTAM trace data when SYSPARM NTSINTSV=YES. This message is preceded by another which describes the type of trace entry being dumped.
System Action:
None.
User Action:
None.
Reason:
Intensive message recording (SYSPARMS NTSINTSV={YES|name}) is active for NTS. The session trace buffer is written to the log in dump format.
System Action:
The buffer is written to the log.
User Action:
Collect the activity log output for Technical Support if required.
Reason:
This message precedes a dump of any access method debug trace data which was received from VTAM while NTS was in intensive message recording mode. Refer to the VTAM Diagnosis manual for the meaning of such data.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of any normal PIU discarded trace data which was received from VTAM while NTS was in intensive message recording mode.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of any PIU trace data, discarded as no current session was active, and which was received from VTAM while NTS intensive recording mode was active.
System Action:
None.
User Action:
None.
Reason:
A buffer received from VTAM carrying session trace data was not the next in sequence. The number of buffers lost is nnn and represents the difference between the expected number and the actual sequence number received.
System Action:
Processing continues with a loss of trace data.
User Action:
Check the SYSPARM NTSTRCBF setting and if appropriate allocate more small buffers rather than fewer large ones.
Reason:
The number of trace entries shown in the message were discarded after they could not be matched to an active session and NTS had waited for a period defined in the NTS correlation interval to expire.
System Action:
Processing continues.
User Action:
Use SYSPARM NTSINTSV=YES to dump such data to determine the cause, and review the SYSPARM NTSCINTV value as necessary.
Reason:
This message precedes a dump of the invalid data found in the trace buffer received from VTAM while NTS was in intensive message recording mode.
System Action:
The data is not processed.
User Action:
Report this message to your product support representative.
Reason:
First line of a display of monitored session trace data. The pri-name and sec- name fields contain the primary and secondary session partner names. Between them the dir field can be either "-->" (primary to secondary) or "<--" (secondary to primary) indicating the direction in which the trace PIU was flowing. The time the PIU was traced is displayed, along with the PIU sequence number ( seq in decimal) and the PIU data count field value ( len in decimal).
System Action:
None.
User Action:
None.
Reason:
Display line for trace data being monitored contains Request Header information. The rqst can be "RQST", "+RSP" or "-RSP" to indicate the PIU contains a request unit, a positive response unit, or a negative response unit respectively. The type field indicates the RU type as FMD (Function Management Data), DFC (Data Flow Control), NC (Network Control) or SC (Session Control). The hex-data contains the 3-byte RH in hexadecimal format, and some RH settings such as brackets, chaining, change direction etc, are interpreted.
System Action:
None.
User Action:
None.
Reason:
Display line for trace data being monitored contains Request Unit information. For a formatted RU the RU-type can contain a short description of the RU, the hex- data displaying as much of the RU as is captured by NTS in hexadecimal format.
System Action:
None.
User Action:
None.
Reason:
Display line for trace data being monitored contains sense information. The sense- data is the 4 bytes of sense code from the RU in hexadecimal format, and the sense- description contains the meaning of this code.
System Action:
None.
User Action:
None.
Reason:
NTS could not acquire sufficient storage to format some trace data.
System Action:
The display of some selected trace data is aborted.
User Action:
Investigate the storage shortage problem.
Reason:
This message was returned from the NTS user exit.
System Action:
None.
User Action:
Refer to the NTS exit defined by your installation for further details.
Reason:
An attempt to activate the NTS user exit failed as no exit name was supplied.
System Action:
NTS processing continues without a user exit.
User Action:
Provide an exit name on the NTS System Support panel.
Reason:
The attempt to start the NTS user exit failed due to a lack of storage.
System Action:
NTS continues processing without a user exit.
User Action:
Investigate the storage shortage.
Reason:
The NTS user exit with name name has abended with the abend-code shown in the message.
System Action:
NTS processing continues without a user exit.
User Action:
Determine the cause of the error. Correct and restart the exit.
Reason:
This message is produced if NTS intensive mode recording is active and an MAI buffer is de-queued incorrectly.
System Action:
The buffer is written to the activity log.
User Action:
Conrtact your product support representative.
Reason:
The SOLVE session time-out manager has detected a session for the userid and luname shown which has been inactive for the time interval displayed. This is a warning message only and subsequent action depends upon the installation defined time-out options.
System Action:
None.
User Action:
None.
Reason:
An ATTACH command to initialize SOLVE from a VM/GCS Userid has been entered whilst SOLVE is initializing as the result of an earlier
ATTACH command.
System Action:
The command is ignored.
User Action:
Wait until SOLVE initialization is complete (and message N00503 issued) before entering commands.
Reason:
The length of the parameter data on the ATTACH command exceeds the maximum of 130 bytes (excluding NM ATTACH).
System Action:
Initialization fails to complete. The GCS task waits for a correct ATTACH command.
User Action:
Correct the ATTACH parameter list by removing embedded spaces or excessive parameters that may be allowed to default.
Reason:
The first command entered on the GCS task must be an ATTACH command.
System Action:
The command is ignored.
User Action:
Enter an ATTACH command and await message N00503 to indicate that initialization is complete before entering other commands.
Reason:
An attempt to initialize the SOLVE maintask from the GCS task has failed because the maintask member cannot be found.
System Action:
SOLVE initialization fails to complete. The GCS task waits for a correct
ATTACH command.
User Action:
Check that the initialization procedures specify the correct LOADLIB(s), that the appropriate minidisks have been accessed and that these commands were completed correctly.
Reason:
An attempt to ATTACH the maintask from the GCS task failed.
System Action:
Initialization fails to complete. The GCS task waits for a correct ATTACH command.
User Action:
Check the return code from the ATTACH macro by reference to the formatted dump. Contact Technical Support.
Reason:
You entered a command before initialization completed.
System Action:
The command is ignored.
User Action:
Wait until initialization is complete (and message N00503 issued) before entering commands.
Reason:
The length of the SOLVE command and parameters exceeds the maximum of 256 bytes (excluding NM).
System Action:
The command is ignored.
User Action:
Correct the command or parameter list by removing embedded spaces or excessive parameters.
Reason:
Internal error.
System Action:
Abnormal termination of SOLVE.
User Action:
Contact your product support representative.
Reason:
The Group Control System (GCS) group in which the SOLVE VM userid is running does not have that userid defined as an authorized machine.
System Action:
Abnormal termination of SOLVE.
User Action:
Use the (VM/SP) GROUP EXEC to add the SOLVE userid as an authorized machine. Refer to the SOLVE Installation Instructions for VM/GCS and the IBM manuals which describe GCS and group definitions.
Reason:
The system abnormally terminated and a formatted dump is being produced. However, one of the load modules used to complete the formatted dump cannot be found.
System Action:
Termination continues. The formatted dump is incomplete.
User Action:
Check that the initialization procedures specify the correct LOADLIBs, that the appropriate minidisks have been accessed, and that these commands were completed correctly.
Reason:
Indicates the end of the formatted dump dataset.
System Action:
None.
User Action:
None.
Reason:
The maintask has completed following an orderly SHUTDOWN or FSTOP, or an abnormal termination.
System Action:
The GCS task waits for an ATTACH command.
User Action:
Enter an ATTACH command to restart, and await message N00503 to indicate that initialization is complete.
Reason:
This is the title line of the SHOW LIB display.
NAME is the name of the panel library.
ID is the logical fileid used by the library. To use the library this fileid must have been opened using the UDBCTL OPEN command.
EDIT indicates if this library definition allow the library to be edited using the edit services component.
STATUS is the status of the file for this library. This column will contain OPEN if the file is available for use, or UNDEF if the UDBCTL OPEN has not yet been successfully issued for the file.
DESCRIPTION a description of the library entered when the library was defined to the system.
System Action:
None.
User Action:
None.
Reason:
This is the detail line of the SHOW LIB display as described by the N79E01 message.
System Action:
None.
User Action:
Refer to the description of N79E01 for a description of the contents of the fields in this message.
Reason:
This is the title line of the SHOW PATH display. This line is followed by N79E04 for each path definition displayed. Each N79E04 message is followed be an N79E05 message describing each library in the path.
PATH/LIB is the name of the panel concatenation path or library.
EDIT indicates if the path and library definition allow the library to be edited using the edit services component.
LIBDEF for N79E05 describes whether the library has been defined with the LIBRARY DEFINE command.
DESCRIPTION a description of the library or path entered when the library (or path) was defined to the system.
Refer to the individual message descriptions for more information.
System Action:
None.
User Action:
None.
Reason:
This is a detail line of the SHOW PATH display. This line describes a path as a whole and is followed by N79E05 messages describing each library in the path.
pathname is the name of the panel concatenation path.
edit indicates if the path allows edit of its component libraries. The possible values are:
ALL - the path definition allows all libraries to be edited.
NONE - the path definition does not allow any of its libraries to be edited.
LIST - the path definition allows some, but not all, of its libraries to be edited. libdef always '-'.
description a description of the path entered when the path was defined to the system.
Refer to the N97E03 and N79E05 message descriptions for more information.
System Action:
None.
User Action:
None.
Reason:
This is a detail line of the SHOW PATH display. This line describes a library in a path.
library is the name of the panel library.
edit indicates if the library may be edited on this path. The possible values are:
YES - the library may be edited.
NO-PATH - the path definition does not allow the library to be edited.
NO-LIB - the library definition does not allow the library to be edited.
libdef YES if the library has been defined.
NO if the library has not been defined. The LIBRARY DEFINE command is used to define libraries.
description a description of the library entered when the library was defined to the system.
System Action:
None.
User Action:
None.
Reason:
This is the response to a SHOW LIB command where no libraries matched the library name requested for display.
System Action:
None.
User Action:
None.
Reason:
This is the response to a SHOW PATH command where no library paths matched the path name requested for display.
System Action:
None.
User Action:
None.
Reason:
The description entered on a LIBRARY or LIBPATH command was too long. The maximum length allowed is 40 characters.
System Action:
The command is not performed.
User Action:
Reenter the command with a description of less than 40 characters.
Reason:
This is the response to a LIBRARY DEFINE, DELETE or REPLACE command for a library definition. The action xxxx has been performed. The action will be one of ADDED, REPLACED or DELETED depending on the option on the LIBRARY command.
System Action:
The action is performed.
User Action:
None.
Reason:
This is the response to a LIBPATH DEFINE, DELETE or REPLACE command for a library definition. The action xxxx has been performed. The action will be one of ADDED, REPLACED or DELETED depending on the option on the LIBPATH command.
System Action:
The action is performed.
User Action:
None.
Reason:
This is the response to a LIBRARY DEFINE or LIBPATH DEFINE command for the named item, however the library or path of that name was already defined.
System Action:
The command is rejected.
User Action:
None.
Reason:
A LIBRARY or LIBPATH command was issued but there is insufficient storage available to process the request.
System Action:
The command is not performed.
User Action:
Investigate the cause of the storage shortage condition.
Reason:
This is the response to a LIBRARY DELETE or LIBPATH DELETE command for the named item, however no library (or path) of that name was found.
System Action:
The command is rejected.
User Action:
Check the library or path you are trying to delete.
Reason:
This is the response to a LIBRARY REFRESH command. The refresh has completed successfully.
System Action:
All panels stored in the active panel queue which were related to the library have been dropped from storage. This includes panels loaded for any path which contains the named library. The library dataset is not effected in any way.
User Action:
None.
Reason:
This is the response to a LIBRARY DEFINE command which specified an invalid fileid. The fileid specified is reserved for use by the system and may not be used as a fileid for a panel library.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This is the response to a LIBPATH DEFINE or REPLACE command which incorrectly specified a list of editable libraries with the EDIT= keyword. The named library is not in the list of libraries specified by the LIB= keyword.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This is the response to a LIBPATH DEFINE or REPLACE command which omitted the LIB= parameter. The LIB= parameter is required.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This is the response to a LIBPATH DEFINE or REPLACE command which specified the LIB= or EDIT= parameter incorrectly. The parameter may not specify a list with null entries.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This is the response to a LIBPATH DEFINE or REPLACE command which specified the LIB= or EDIT= parameter incorrectly. The parameter may not specify a list which contains the same entry more than once.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This is the response to a LIBPATH DEFINE or REPLACE command which specified the LIB= or EDIT= parameter incorrectly. The maximum number of libraries in a path is 16.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This is the response to a LIBPATH DEFINE or REPLACE command which specified the LIB= or EDIT= parameter incorrectly. The list may contain a single entry or a list of entries separated by commas and enclosed in brackets.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This is the response to a LIBPATH DEFINE or REPLACE command which specified the LIB= or EDIT= parameter incorrectly. The list may contain a single entry or a list of entries separated by commas and enclosed in brackets.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This is the response to a LIBPATH DEFINE or REPLACE command which specified the LIB= or EDIT= parameter incorrectly. The list may contain only valid names, a valid name is up to 8 alphanumeric and national characters beginning with an alphabetic or national character.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This is the response to a LIBPATH or LIBRARY command which you were not authorized to issue. A higher command authority level is required.
System Action:
The command is rejected.
User Action:
Refer this problem to your systems administrator.
Reason:
During NVC initialization, it was determined that PPI module CNMNETV is not available.
System Action:
NV-Connect feature is not available.
User Action:
Determine the cause for the CNMNETV unavailability and rectify the problem.
Reason:
Issued when the connection from this NV-Connect (systemid) to the remote NetView (linkname) has been established.
System Action:
None.
User Action:
The Remote Operator Facility may now be used to route commands and enquiries to the remote system using the ROUTE command.
Reason:
The link from this NV-Connect system (systemid) to the NetView system known as linkname is inactive.
System Action:
If the link has become inactive as a result of an earlier LINK STOP= linkname command, the link will remain inactive until a subsequent LINK START= linkname command. The system will attempt to re-establish the link at regular intervals.
User Action:
Determine the cause of link deactivation if no LINK STOP= linkname was entered. Possible causes may be a failure in PPI communications or the remote NetView system may have been terminated.
Reason:
An NV-Connect PPI receiver detected a PPI communications error. rc indicates the last return code from PPI.
System Action:
The system will try to re-contact PPI at regular intervals.
User Action:
Consult PPI documentation for explanation of rc to determine the reason for communications failure.
Reason:
Notifies a user that the ROF connection to the NetView system linkname has been broken because the link to the system has been lost.
System Action:
The ROF connection is scheduled for re-establishment when the link becomes active again.
User Action:
None.
Reason:
NetView's portion of NVC is not compatible with SOLVE's release version.
System Action:
Link to NetView system is not started.
User Action:
Bring NetView's NVC code and SOLVE code to the same level and restart the systems.
Reason:
Confirms successful completion of a SIGNOFF command.
System Action:
None.
User Action:
None.
Reason:
This is a response to NVC STOP command.
System Action:
NVC's PPI receiver is terminated. All NVC-type links are terminated. NVC receiver will restart when LINK START command is entered for NVC-type link.
User Action:
None.
Reason:
This is a response to NVC STOP command, when no NVC-type links are active and NVC PPI receiver is also inactive.
System Action:
Command is ignored.
User Action:
None.
Reason:
An attempt to use a command through a system console has failed because the console userid, for example SYSOPER, does not have Command Facility access privilege.
System Action:
The command is rejected.
User Action:
None.
Reason:
A NetView operator tried to issue a command to NV-Connect nvcid via ROF, however there is no connection between NetView and NV-Connect.
System Action:
The command is ignored.
User Action:
Activate communications path between NetView and NVC, then re-issue the command.
Reason:
Informs NetView operators that there is no connection between NV-Connect nvcid and NetView.
System Action:
The system will try to establish connection at regular intervals.
User Action:
Determine the reason for connection unavailability.
Reason:
A NV-Connect operator tried to signon to NetView via ROF. However the operator autotask has not started within the allowed time frame.
System Action:
The system will reject ROF signon to NetView.
User Action:
Determine the reason for autotask start failure in NetView. Probable causes are: operator ID is not defined to NetView; operator logged on to NetView natively.
Reason:
A threshold limit of buffers on NVCV's public queue has been reached.
System Action:
NVCV subtask will deactivate itself until the message count drops to 75% of threshold limit, then it will reactivate itself. NetView exits attempting to queue messages to NVCV subtask, will not be able to do so while NVCV subtask is in INACTIVE state.
User Action:
Determine the reason for message rate flow and adjust OQLIM parameter for NVCV task if necessary.
Reason:
A NetView operator issued a command destined for NV-Connect. The command processor was unable to acquire a buffer for delivery of the message to the NVCV subtask.
System Action:
The command is not delivered to NVCV subtask and is not executed.
User Action:
Investigate the storage usage by NetView; if necessary increase the region size.
Reason:
A NetView operator issued a command destined for NV-Connect. The command processor tried to queue a command buffer to NVCV subtask but the DSIMQS macro returned a non-zero return code.
System Action:
The command is not delivered to NVCV subtask and is not executed.
User Action:
Ensure the NVCV subtask in NetView is active and reissue the command.
Reason:
This message indicates that a serious error has occurred on the NVC-type link to the system known as linkname . The link is now unusable. NV-Connect will close all sessions on the link and the link will remain in FAILED status until a LINK START command is entered to restart it.
System Action:
The link is inactivated and put into FAILED status.
User Action:
Other messages will precede this message, indicating the cause of the original error. Refer to these messages to see what corrective action is necessary. When the error condition has been corrected, issue a LINK START command to reactivate the link.
Reason:
This message indicates that an NV-Connect sender was unable to send messages due to failure in PPI. rc indicates the last return code from a call to PPI.
System Action:
The link is deactivated.
User Action:
Refer to PPI documentation for an explanation of the PPI return code, correct the problem and restart the link.
Reason:
This message indicates that data destined for linkname has been lost due to communications failure.
System Action:
The link is deactivated.
User Action:
Determine the reason for communications failure based on messages preceding or following this message.
Reason:
This message indicates an error during PPI send processing to NetView receiver receiverid . rc indicates the last return code from PPI.
System Action:
The link is deactivated.
User Action:
Consult PPI documentation to determine the reason for failure based on rc .
Reason:
Notifies a user that the ROF connection to remote NetView system linkname has been broken because the link to the remote system has been lost.
System Action:
The ROF connection is scheduled for re-establishment when the link becomes active again.
User Action:
None.
Reason:
This message indicates that the NetView PPI receiver's queue is full. rc indicates the last return code from PPI.
System Action:
Messages will not be sent to NetView.
User Action:
Determine the reason for message build-up on the PPI queue and rectify the problem.
Reason:
The link to NetView system known as linkname is inactive.
System Action:
If the link has become inactive as a result of an earlier LINK STOP= linkname command, the link will remain inactive until a subsequent LINK START= linkname command. Otherwise the system will attempt to re- establish the link at regular intervals.
User Action:
Determine the cause of link deactivation if no LINK STOP= linkname was entered. Check whether the remote NetView system was terminated.
Reason:
A NetView PPI receiver detected a PPI communication error. rc indicates the last return code from PPI.
System Action:
The system will retry connection to PPI at regular intervals.
User Action:
Consult PPI documentation for an explanation of rc to determine the reason for communications failure.
Reason:
A NetView PPI receiver is inactive due to registration failure with PPI.
System Action:
The system will retry PPI registration at regular intervals.
User Action:
Consult the PPI documentation for an explanation of the return codes issued in the preceding messages.
Reason:
Signon was attempted via ROF from NV-Connect but the NVCV subtask could not start operator autotask.
System Action:
ROF signon is rejected.
User Action:
The probable cause for error is that opid is not defined to NetView or opid is already active in NetView.
Reason:
Signon was attempted via ROF from NV-Connect, but the NVCV subtask could not allocate the required storage.
System Action:
ROF signon is rejected.
User Action:
Investigate the reason for storage problems in NetView.
Reason:
A ROF command arrived from NV-Connect, but the NVCV subtask could not queue it to the opid task. rc indicates the error code returned by the DSIMQS macro.
System Action:
Command is not executed.
User Action:
Investigate the reason for DSIMQS failure based on rc by consulting NetView documentation.
Reason:
The link from this NetView system to the NV-Connect system is inactive.
System Action:
The link has become inactive as a result of termination of the NVCV subtask in NetView. The link will remain inactive until the NVCV task is restarted. The system will attempt to re- establish the link at regular intervals.
User Action:
Determine the cause of link deactivation if NVCV task has not been terminated. Possible causes may be that the NV-Connect system was terminated or there was PPI communications error.
Reason:
ROF signon was attempted by opid from NV-connect, but the user has already signed on to NetView from another NV-Connect screen.
System Action:
Signon is rejected.
User Action:
Use the original session, or terminate it and start the new one.
Reason:
The SOLVE and NVCV versions are incompatible.
System Action:
The link from NetView to SOLVE is not established.
User Action:
Make sure that SOLVE & NVCV in NetView have been installed correctly and they are of the same release.
Reason:
This message indicates that an NVCv sender was unable to send messages due to a failure in PPI. rc indicates the last return code from a call to PPI.
System Action:
The NVCV subtask in NetView will retry to contact PPI.
User Action:
Refer to PPI documentation for explanation of return code from PPI.
Reason:
This message indicates an error during PPI send processing to NV-Connect from NVCV. The variables are:
P1 is the NetView PPI Receiver ID.
P2 indicates the current status of the specified receiver. This can be ACTIVE or INACTIVE .
P3 indicates the return code from PPI.
System Action:
There is no communication between NV-Connect and NVCV.
User Action:
Consult PPI documentation to determine the reason for failure based on
P3 .
Reason:
This message indicates that NV-Connect's PPI receiver queue is now full.
System Action:
The data destined for domid domain is discarded.
User Action:
Determine the reason for message build-up on the PPI queue and rectify the problem.
Reason:
This message indicates a call to NetView service service from the NVCV task has failed. rc contains the return call from the service call.
System Action:
NVCV will take the appropriate action, depending on the nature of service .
User Action:
Determine the reason for failure based on rc and service name.
Reason:
This message indicates that NVCV's parameters specified in the initialization member of DSIPARM library are incorrect.
System Action:
NVCV subtask will not start.
User Action:
Correct initialization parameters.
Reason:
This message indicates that NVCV subtask has failed to initialize.
System Action:
NVCV subtask will terminate.
User Action:
Determine the reason for failure based on the preceding messages.
Reason:
This message indicates that the call to DSILOD service in NetView has failed. modname is name of the module being loaded.
System Action:
NVCV subtask will terminate.
User Action:
Determine the reason for failure based on return code rc from DSILOD.
Reason:
This message indicates that the CNM/NMVT messages arriving from NV-Connect were not delivered to NetView. rc indicates the return code from the DSIMQS macro.
System Action:
The message is deleted.
User Action:
Determine the reason for failure based on the return code rc from DSIMQS.
Reason:
This message indicates that the user provided exit exitname has returned with invalid parameters. r15 is the contents of Register 15 and r0 is the contents of Register 0 that were returned by the user exit.
System Action:
The return code from user exits is returned.
User Action:
Consult documentation on coding user exits and correct the exit.
Reason:
This message indicates that a PPO message that arrived from NVC is not delivered to NetView's PPT task. rc indicates the return code from DSIMQS macro.
System Action:
The message is deleted.
User Action:
Determine the reason for failure based on return code rc from DSIMQS.
Reason:
An internal error has occurred in the module identified in the message. The reason code rc further clarifies the type of abend. A full list of internal abend codes (xxx-yy) can be displayed using the Common Application Services (CAS) message services.
System Action:
A formatted dump and a system dump are normally produced.
User Action:
Use the internal abend code to (xxx-yy) and examine the messages. If the problem cannot be easily diagnosed contact support. r
Reason:
Confirms successful processing of an earlier LINK RESET= linkname command issued to delete the definition of the remote NetView system linkname .
System Action:
None.
User Action:
A LINK START command will have to be entered to redefine the remote system linkname before connection can be re-established.
Reason:
A LINK RESET command was entered for link linkname but the link has not yet been de-activated by a LINK STOP command. Until this is done the link definition cannot be reset.
System Action:
The command is rejected.
User Action:
Issue a LINK STOP= linkname command if applicable, then re-issue the LINK RESET= linkname command.
Reason:
SOLVE and ASN1 subsystem are not compatible.
System Action:
ASN1 subsystem is not initialized.
User Action:
Make sure that the correct ASN1 compiler module is used by the SOLVE system.
Reason:
This message is returned by ASN1COMP subsystem in response to
&CALL SUBSYS=ASN1COMP READ ERROR request. It indicates that no errors were produced during compilation of ASN1 module.
System Action:
None.
User Action:
None.
Reason:
This message is returned by ASN1COMP subsystem in response to
&CALL SUBSYS=ASN1COMP READ WARNING request. It indicates that no warnings were produced during compilation of ASN1 module.
System Action:
None.
User Action:
None.
Reason:
A SOLVE:Manage security structured field value was invalid.
System Action:
The value is ignored.
User Action:
Correct the security exit value returned and restart the exit. Check the processing for SF x'0530'.
Reason:
The initialization process for the S:NM-TCP/IP feature has failed as the indicated procedure (P1) cannot be started due to insufficient storage.
System Action:
The feature initialization fails.
User Action:
Restart SOLVE in a larger region.
| Copyright © 2012 CA. All rights reserved. |
|