|
|
|
Reason:
An MAILOGON command failed because all available MAI-OC APPL definitions are in use. xxxxx is the MAI-OC APPL prefix NMMAV or as set by the installation via the SYSPARMS MAIOPREF= operand.
System Action:
The command is rejected.
User Action:
Wait for an MAI-OC APPL to become available or increase the number of APPL statements defined to VTAM.
Reason:
An MAILOGON command requested that an MAI-OC session be established using a particular MAI LUNAME, but the LUNAME is already in use on another MAI-OC session or by another application.
System Action:
The command is rejected.
User Action:
Use another available LUNAME.
Reason:
An MAILOGON command requested that an MAI-OC session be established using a particular LUNAME, but the specified LUNAME is not known to VTAM as an APPL definition.
System Action:
The command is rejected.
User Action:
Use another available LUNAME.
Reason:
MAI-OC was unable to open the VTAM ACB associated with the LUNAME to be used on the MAI-OC session.
System Action:
The MAI-OC session is not established.
User Action:
Determine the cause of the error from the appropriate VTAM Programming Manual.
Reason:
A VTAM SETLOGON macro failed during MAI-OC session establishment. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-OC session is not established.
User Action:
Determine the cause of failure.
Reason:
An MAILOGON command could not complete because the target application with which a session is requested is either unknown to VTAM or cannot be contacted if in another domain.
System Action:
The command is rejected.
User Action:
Correct the application name. In the case of cross-domain logon the failure may be the result of appropriate cross domain resource definitions being unavailable.
Reason:
An MAILOGON command could not complete because the target application with which a session is requested is not active.
System Action:
The command is rejected.
User Action:
Retry when the target application is available.
Reason:
A VTAM REQSESS macro failed during MAI-OC session establishment. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-OC session is not established.
User Action:
Determine the cause of the failure.
Reason:
The VTAM NSEXIT was driven during establishment of an MAI-OC session, indicating a Network Services Procedure Error (NSPE).
System Action:
The MAI-OC session is terminated.
User Action:
Determine the cause of the failure. This error can occur when an application program rejects the MAI-OC session, for instance if the LUNAME being used has not been defined to the application.
Reason:
A VTAM OPNSEC macro failed during MAI-OC session establishment. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-OC session is not established.
User Action:
Determine the cause of failure.
Reason:
An MAILOGON request for a session with a target application could not be completed because the application returned BIND parameters which were unacceptable to MAI.
System Action:
The session attempt is terminated.
User Action:
Ensure that the BIND parameters associated with the MAI-OC LUNAME chosen for the failed session are correct and that the appropriate LOGMODE table is associated with the APPL definition. Also ensure that if the LUNAME is defined to the application with which the session was requested, the application has the LUNAME defined to it as an LU- TYPE 1.
Reason:
An MAILOGON command specified the name of a LOGMODE table entry name that is to be used on the requested session, but VTAM does not have the name defined to it.
System Action:
The session request is terminated.
User Action:
Correct the LOGMODE entry name and retry.
Reason:
An MAILOGON command could not complete because the target application with which a session is requested is not available.
System Action:
The command is rejected.
User Action:
Retry when the target application is available.
Reason:
This message indicates the VTAM return code and feedback information associated with the failure of MAI-OC VTAM operations. This message will follow a message indicating the general error condition, eg: N80010.
System Action:
None.
User Action:
Refer to the appropriate VTAM Programming Manual for explanation of the error codes.
Reason:
A VTAM RECEIVE macro failed during MAI-OC session operation. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-OC session is terminated.
User Action:
Determine the cause of the failure.
Reason:
A VTAM SEND macro failed during MAI-OC session operation. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-OC session is terminated.
User Action:
Determine the cause of the failure.
Reason:
A VTAM SEND macro failed during MAI-OC session operation when a response was being returned to the target application. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-OC session is terminated.
User Action:
Determine the cause of the failure.
Reason:
This message indicates the VTAM return code and feedback information associated with the failure of MAI-OC VTAM operations. This message will follow a message indicating the general error condition, eg: N80103.
System Action:
None.
User Action:
Refer to the appropriate VTAM Programming Manual for explanation of the error codes.
Reason:
A VTAM SEND macro failed during MAI-OC session operation. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-OC session is terminated.
User Action:
Determine the cause of the failure.
Reason:
A VTAM TERMSESS macro failed during MAI-OC session establishment. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-OC session is terminated.
User Action:
Determine the cause of the failure.
Reason:
This message indicates the VTAM return code and feedback information associated with the failure of MAI-OC VTAM operations. This message will follow a message indicating the general error condition, eg: N80202.
System Action:
None.
User Action:
Refer to the appropriate VTAM Programming Manual for explanation of the error codes.
Reason:
A VTAM SEND macro failed during MAI-OC session operation. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-OC session is terminated.
User Action:
Determine the cause of the failure.
Reason:
This message indicates the VTAM return code and feedback information associated with the failure of MAI-OC VTAM operations. This message will follow a message indicating the general error condition, eg: N80301.
System Action:
None.
User Action:
Refer to the appropriate VTAM Programming Manual for explanation of the error codes.
Reason:
The logon request failed because all available MAI-FS APPL definitions are in use. P1 is the MAI-FS APPL prefix in use. Where multiple pools are defined then P1 is the prefix of the last pool used.
System Action:
The request is rejected.
User Action:
Notify your system administrator. Retry the session when an MAI-FS application is available.
As system administrator: Increase the number of APPL statements defined to VTAM for this prefix. If necessary define APPL statements to VTAM for a new pool prefix and add the prefix definition to the $NM EXTAPPLPOOLS parameter group.
Reason:
A logon request specified that an MAI-FS session be established using a particular logical unit name (LU), but the name is already in use on another MAI-FS session or by another application.
System Action:
The request is rejected.
User Action:
Use another available NODENAME.
Reason:
A logon request specified that an MAI-FS session be established using a particular logical unit name (LU), but the name is not known to VTAM.
System Action:
The request is rejected.
User Action:
Use another Node Name.
Reason:
MAI-FS was unable to open the VTAM ACB associated with the NODENAME to be used on the MAI-FS session.
System Action:
The MAI-FS session is not established.
User Action:
Determine the cause of the error from the appropriate VTAM Programming Manual.
Reason:
A VTAM SETLOGON macro failed during MAI-FS session establishment. The accompanying N51506 message contains the error code information. The error codes are documented in the VTAM Programming Manual.
System Action:
The MAI-FS session is not established.
User Action:
Determine the cause of failure.
Reason:
A logon request could not complete because the target application with which a session is requested is either unknown to VTAM or cannot be contacted if in another domain.
System Action:
The request is rejected.
User Action:
Correct the application name. In the case of cross-domain logon the failure may be the result of appropriate cross domain resource definitions being unavailable.
Reason:
A logon request could not complete because the target application with which a session is requested is not active.
System Action:
The request is rejected.
User Action:
Retry when the target application is available.
Reason:
A VTAM REQSESS macro failed during MAI-FS session establishment. The accompanying N51506 message contains the error codes. These are documented in the VTAM Programming Manual.
System Action:
The MAI-FS session is not established.
User Action:
Determine the cause of the failure.
Reason:
The VTAM NSEXIT was driven during establishment of an MAI-FS session, indicating a Network Services Procedure Error (NSPE) or NOTIFY.
System Action:
The MAI-FS session is terminated.
User Action:
Determine the cause of the failure. This error can occur when an application program rejects the MAI-FS session, for instance if the LUNAME being used has not been defined to the application.
Reason:
A VTAM OPNSEC macro failed during MAI-FS session establishment. The accompanying N51506 contains the error codes. The codes are documented in the VTAM Programming Manual.
System Action:
The MAI-FS session is not established.
User Action:
Determine the cause of failure.
Reason:
A logon request for a session with a target application could not be completed because the application returned BIND parameters which were unacceptable to MAI-FS.
System Action:
The session is terminated.
User Action:
Ensure that the BIND parameters associated with the MAI-FS Node Name (LU) for the failed session are correct and that the appropriate LOGMODE table is associated with the APPL definition. Also ensure that if the LU is defined to the target application, the application has the LU defined to it as an LU-TYPE 0 or 2.
Reason:
The session request failed with a return code, feedback of X'144B'. The most likely cause is that the logon request specified the name of a LOGMODE table entry name that is not defined to VTAM. The error code is also used to indicate that cryptography is not supported.
System Action:
The session request is terminated.
User Action:
Correct the LOGMODE entry name and retry. If you did not enter a LOGMODE entry name, it is possible that MAI has not been installed correctly. If the logmode is valid then the node name used on the session request may be incorrectly defined. Contact your installation help desk.
Reason:
A logon request for a session with a target application could not be completed because the application returned BIND parameters which contained screen dimension information which did not match those of the physical screen from which the session was invoked.
System Action:
The session is terminated.
User Action:
If you entered a specific LOGMODE table entry name when invoking the session, it is possible that the table was not compatible with the terminal model being used.
If you allowed MAI to choose its own LOGMODE table entry name, the LU being used by MAI-FS may be defined incorrectly to the application. Refer this error to your systems administrator.
Reason:
A logon request could not complete because the target application with which a session is requested is not available.
System Action:
The request is rejected.
User Action:
Retry when the target application is available.
Reason:
A VTAM RECEIVE macro failed during MAI-FS session operation. The accompanying N51506 message contains the error codes. The codes are documented in the VTAM Programming Manual.
System Action:
The MAI-FS session is terminated.
User Action:
Determine the cause of the failure.
Reason:
A logon request specified that an MAI-FS session be established using a particular MAI NODENAME, but the name, P1 , is not defined to VTAM as an application.
System Action:
The request is rejected.
User Action:
Verify that either the specific nodename or MAI prefix being used is correct. If necessary contact your installation help desk. The node name in the message should be defined to VTAM according to the recommendation for MAI-FS APPLs.
Reason:
The session has been terminated by a VTAM command.
System Action:
None.
User Action:
None.
Reason:
The session has been terminated by an operator command.
System Action:
None.
User Action:
None.
Reason:
A session startup that requires a passticket has failed. The passticket generation routine could not be located in common storage.
System Action:
The session startup is terminated.
User Action:
Notify your systems programmer of the error.
The passticket generation routine is provided by the security product (CA ACF2, CA Top Secret, or RACF). Either the CVTRAC field in the MVS communications vector table (CVT) did not contain a security common area pointer or the RCVTPTGN field was zero.
Reason:
A session requiring a passticket has been activated, and the passticket generation routine returned a nonzero return code.
Is the name of the application.
Is the passticket generation return code.
System Action:
The session activation is terminated.
User Action:
Notify the systems programmer or security administrator.
Check that the application name used is correct and is defined to the security product for passticket use.
Reason:
A VTAM RECEIVE macro failed during MAI-FS session operation. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-FS session is terminated.
User Action:
Determine the cause of the failure.
Reason:
A VTAM SEND macro failed during MAI-FS session operation. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-FS session is terminated.
User Action:
Use the sense information to determine the cause of the failure and if necessary report the problem to your product support representative.
Reason:
A VTAM SEND macro failed during MAI-FS session operation when a response was being returned to the target application. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-FS session is terminated.
User Action:
Determine the cause of the failure.
Reason:
A VTAM SEND macro failed during MAI-FS session operation. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-FS session is terminated.
User Action:
Determine the cause of the failure.
Reason:
A VTAM TERMSESS macro failed during MAI-FS session establishment. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-FS session is terminated.
User Action:
Determine the cause of the failure.
Reason:
An MAI session output request has failed.
System Action:
The session is terminated in error.
User Action:
Report the problem to your product support representative.
Reason:
A VTAM SEND macro failed during MAI-FS session operation. The meaning of the error codes displayed on the next line are documented in the appropriate VTAM Programming Manual.
System Action:
The MAI-FS session is terminated.
User Action:
Determine the cause of the failure.
Reason:
A VTAM RESETSR request has failed.
System Action:
The MAI session is terminated.
User Action:
Notify your product support representative.
Reason:
The MAI exit has refused the creation of this session, without providing an alternative error message.
System Action:
The session request is refused.
User Action:
Contact your systems administrator if the reason for the error is unclear.
Reason:
This indicates rejection of an MAI logon request by the installation- supplied MAI exit. The text of the message is supplied by the exit, or a default text can be inserted by MAI if the exit does not supply a message.
System Action:
The request is rejected.
User Action:
Contact your systems administrator if the reason for the error is unclear.
Reason:
The MAI exit has refused the creation of this session.
System Action:
The session request is refused.
User Action:
Contact your systems administrator if the reason for the error is unclear.
Reason:
An attempt to start an MAI session has been refused, because MAIEX02 has not yet initialized.
System Action:
The session request is refused.
User Action:
Retry the request when the exit has completed initialization.
Reason:
The installation MAI exit did not initialize successfully.
System Action:
MAI sessions will not be started until the error is corrected.
User Action:
Refer the problem to your systems administrator.
Reason:
The MAIEX02 system parameter named a module that could not be loaded.
System Action:
MAI sessions will not be started until the error is corrected.
User Action:
Refer the problem to your systems administrator.
Reason:
The MAI exit has refused the creation of this session, without providing an alternative error message.
System Action:
The session request is refused.
User Action:
Contact your systems administrator if the reason for the error is unclear.
Reason:
An attempt to start an MAI session has been refused, because MAIEX02 has not yet initialized.
System Action:
None.
User Action:
Retry later.
Reason:
The installation MAI exit did not initialize successfully.
System Action:
MAI sessions will not be started until the error is corrected.
User Action:
Refer the problem to your systems administrator.
Reason:
The MAIEX02 entry address could not be found.
System Action:
MAI sessions will not be started until the error is corrected.
User Action:
Refer the problem to your systems administrator.
Reason:
Overflows in the AOM/MVS queues have led to messages being lost. This message is sent to inform AOMPROC and Monitor Users of this occurrence.
System Action:
This message replaces the lost messages.
User Action:
Determine whether the AOM queues are large enough, using the SHOW AOMSTAT=TUNING command. If this occurs regularly, increase the size of the relevent queue using the SYSPARMS AOMGQSZ (global) or AOMPQSZ (private) commands.
Reason:
This message records an MVS command, if SYSPARMS AOMLCMD is in effect. The source of the command, userid (if known), and screening action are shown, as well as the command text.
S=source The source of the command; values are:
INSTREAM - an instream JCL command
INTERNAL - an internal console
TSO - a TSO user (OPER command)
UNKNOWN - an unidentifiable source
CON## or CON### - a specific console (## is 01 to 99; ### is 100 to 255) xxxxxxxx - a named console (extended MCS) N/M - *this* SOLVE system
I=id The user ID of the command issuer, if known.
A=action The action taken by SOLVE command screening; values are:
NO-SCRN - No command screening done
ALLOW - Command was allowed
SUP-NMSG - Suppressed - no message
SUP-SMSG - Suppressed - standard message
SUP-UMSG - Suppressed - user message
REPLACE - Command replaced
REISSUE - Command reissued
T=command text The text of the command
System Action:
None
User Action:
As required.
Reason:
This message is issued after a successful AOM STOP or commencement of final system shutdown. It indicates that AOM has been terminated.
System Action:
AOM has terminated.
User Action:
None.
Reason:
A REPLY or ISSUE statement in the active AOM screening table has been disabled, after being executed more than AOMRILC times in AOMRILT seconds (These are the relevant SYSPARM names). The relative number of the reply or issue from the front of the table is shown, as is the table name and date and time of compilation. In MVS, this message is issued via WTO. In VM, it is sent to monitor receivers.
'mmmmmmmm' is the member name of the screening table. 'dd-mmm...' is the date and time the screening table was loaded.
System Action:
The indicated reply or issue statement is disabled until a new table is loaded.
User Action:
Determine why the statement was issued so frequently. If ok, adjust the AOMRILT and AOMRILC SYSPARM values.
Reason:
This message is produced by the AOM Subsystem Interface when AOM detected that the SOLVE system has terminated abnormally. It indicates that AOM will cease processing WTO/WTOR messages and commands.
System Action:
AOM Screening table action is stopped.
User Action:
Restart SOLVE.
Reason:
The AOM Subsystem Interface (SSI) has detected a SOLVE system abnormal termination. The current setting of the SYSPARMS AOMSTAY operand is YES. AOM will continue performing Screening Table actions.
System Action:
AOM Screening Table functions continue.
User Action:
Restart SOLVE.
Reason:
This message is sent (WTO or TPUT) by the AOM command issuer when an MVS command is suppressed by a screening table SUPPRESS statement and the statement had MSG=STD specified (or defaulted).
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
This message is produced by the AOM Subsystem Interface when an ABEND occurs during AOM processing of a WTO/WTOR, DOM, or system comand. The SSID that AOM is processing under is displayed. The CODE field will be in one of the following formats:
SYS-xxx where xxx is the 3-digit hexadecimal system ABEND code. USR-nnnn where nnnn is a 4-digit decimal user ABEND code.
System Action:
AOM may take a system dump (SDUMP).
AOM processing continues.
User Action:
If the ABEND code is a system code, refer to the appropriate system codes manual. A system code of 'x22' (x being any non-zero hex digit), possibly indicates that the region issuing the WTO etc was cancelled whilst in AOM code. This is harmless.
If the ABEND code is a user code, then AOM probably captured an ABEND issued in an asynchronous exit invoked while AOM was processing. In this case the ABEND code must be looked up in the appropriate manuals for the program etc executing in the region that the ABEND occurred in.
Reason:
AOM detected a change to the MPF tables (via SET MPF). An SRB has been dispatched to obtain the new MPF attributes.
System Action:
The SRB collects attribute information for the GLOB MPFATTR=YES screening statement.
User Action:
None.
Reason:
A request for AOM statistics, or AOM abend information, failed due to a storage shortage.
System Action:
The request is not processed.
User Action:
Re-issue the SHOW AOMxxx command. If the problem persists, investigate the reasons for the storage shortage.
Reason:
This is a header for a display of AOM statistics. This section will show general AOM information.
System Action:
Statistics follow.
User Action:
None.
Reason:
This message tells the date and time that AOM was last started.
System Action:
None.
User Action:
None.
Reason:
This is a header for a display of AOM statistics. This section provides summary statistics.
System Action:
None.
User Action:
None.
Reason:
This line provides summary information about the local AOM message. It displays information such as the total number of messages, DOMs seen, the total number accepted for processing, and (for z/OS) the total number lost in queue overflows.
System Action:
None.
User Action:
If the overflow amount is non-zero, determine the reason.
Reason:
This line provides more summary information about the local AOM message, etc. delivery. The total number of messages, DOMs, etc. received is indicated.
System Action:
None.
User Action:
None.
Reason:
This is a header message for the display of AOM statistics. Storage usage statistics follow.
System Action:
None.
User Action:
None.
Reason:
This message provides column headers for the following lines of N83922 messages, that provide storage statistics for AOM. The headings are self-explanatory.
System Action:
None.
User Action:
None.
Reason:
This message provides details about the storage necessary for an AOM pool or queue. The following pools and queues are described (depending on the environment, options, and so on):
In MVS, the CSA pool containing key AOM SSI control blocks and code.
In MVS, the (E)CSA-resident global queue. This queue is not allocated if using AOM cross memory services.
The storage allocated to the current and alternate screening tables. In MVS, this storage is in (E)CSA.
The storage allocated to the AOM SSI work pool. This pool is used to avoid GETMAIN processing in the SSI code.
The total MVS common storage used by AOM.
The AOM private queue in storage. This queue is used in AOM/VM only.
The total storage used in AOM/VM for critical AOM control blocks and queues.
System Action:
None.
User Action:
None.
Reason:
This message totals all common storage for the N83922 messages.
System Action:
None.
User Action:
None.
Reason:
This is a heading message that indicates AOM tuning information and statistics follow.
System Action:
None.
User Action:
None.
Reason:
This message shows the allocated size of the AOM work stack (work pool), and the number of times a GETMAIN was necessary because it was empty.
System Action:
None.
User Action:
None. If a large number of GETMAINs are shown, consider increasing the AOMWQSZ value.
Reason:
This message shows the size of the AOM global queue, the total number of entries queued through it, and the number of times an overflow occurred.
System Action:
None.
User Action:
None. If significant overflows occur, consider increasing the AOMGQSZ value.
Reason:
This message shows the maximum depth, number of times at the maximum, and average depth of the GLOBAL queue.
System Action:
None.
User Action:
None.
Reason:
This message displays the number of times a level 1 SRB was dispatched by AOM to perform work, the number of times it ran, and the number of global queue steals performed.
System Action:
None.
User Action:
None.
Reason:
This message displays the total number of messages dequeued, the average number of global queue steals, and average number of messages dequeued by a level 1 SRB.
System Action:
None.
User Action:
None.
Reason:
This message displays the number of level 2 srbs dispatched, run, and the number of transfer of control instructions issued to CA NetMaster.
System Action:
None.
User Action:
None.
Reason:
This message documents the number of level 2 srbs dispatched, run, and the number of transfer of control instructions issued to CA NetMaster when AOM is using Cross- Memory-Services (XMS).
System Action:
None.
User Action:
None.
Reason:
This message shows the size of the AOM private queue, the total number of inserts into it, and the total number lost through overflow.
System Action:
None.
User Action:
If messages are lost, consider increasing the private queue size.
Reason:
This message shows the maximum private queue depth, the number of times at the maximum, and the average private queue depth. The average depth is useful as it gives an indication of the relative amount of message traffic in the system.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of times CA NetMaster was posted to receive AOM traffic, the number of times the receive task ran, the total amount of messages, and so on dequeued from the private queue.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of times that the AOM receive task stole the current private queue, the average number of messages, etc dequeued per run, and the average number of private queue steals per receive run.
System Action:
None.
User Action:
None.
Reason:
This message shows the allocated size of the AOM/VM event queue, and the number of times a GETMAIN was required when it was empty.
System Action:
None.
User Action:
None. If a large number of GETMAINs occur, increase the size of the AOMVEQSZ parameter.
Reason:
This is a heading that indicates that AOM local interface message delivery statistics follow.
System Action:
None.
User Action:
None.
Reason:
This message is a column heading for the following messages. It indicates the individual message types that will be displayed.
System Action:
None.
User Action:
None.
Reason:
This message is a further column heading, if required, for more message types. It corresponds to the second line of any particular statistic display that follows.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each record type that were received for processing by the AOM operating system interface. This number is the total number of each record type. For example, for WTO, it includes all MPF suppressed and hardcopy only messages.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each type that were rejected by the AOM screening table. Note that messages can be rejected automatically by the screening table. For example, automatic rejection of MPF-suppressed, hardcopy only and solicited messages.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each type that were flagged for MVS deletion by the AOM screening table.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each type that were flagged as to be routed to SOLVE by the AOM screening table. Note that for messages marked ROUTE=LOG they are still delivered to SOLVE even if SYSPARMS AOMLOG=NO is in effect (they are simply not logged when they arrive).
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each type that were lost because of AOM GLOBAL queue overflow.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each type that were successfully enqueued on the AOM GLOBAL queue.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each type that were successfully dequeued from the AOM GLOBAL queue.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each record type that were lost because of AOM PRIVATE queue overflow.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each record type that were successfully enqueued to the AOM PRIVATE queue.
System Action:
None.
User Action:
None.
Reason:
This message shows the number of messages of each record type that were successfully dequeued from the AOM PRIVATE queue.
System Action:
None.
User Action:
None.
Reason:
This is a header for the display of ABEND information, if AOM has an ABEND in either the SSI code or an SRB.
System Action:
ABEND information follows.
User Action:
Send the hardcopy log of this information to your product support representative.
Reason:
This line provides debugging information about an AOM ABEND.
System Action:
None.
User Action:
None.
Reason:
This message provides ABEND debugging information. follows.
System Action:
None.
User Action:
None.
Reason:
This message provides ABEND debugging information.
System Action:
None.
User Action:
None.
Reason:
This message provides ABEND debugging information.
System Action:
None.
User Action:
None.
Reason:
This message provides ABEND debugging information.
System Action:
None.
User Action:
None.
Reason:
This message indicates that AOMPROC message delivery statistics follow.
System Action:
Statistics follow.
User Action:
None.
Reason:
This message shows the current AOMPQLIM value, the maximum depth of the AOMPROC delivery queue, and the number of times that maximum has been reached.
System Action:
None.
User Action:
None.
Reason:
This message shows the total number of messages enqueued to AOMPROC (includes DOMs, even if AOMPROC does not want them), the number of times the queue overflowed, and the total number of messages removed and sent to AOM receivers due to overflow. Multi-line WTO messages count as one message when queued to AOMPROC.
System Action:
None.
User Action:
None.
Reason:
This message shows the current number of messages in the primary AOMPROC queue, the number of messages delivered to OCS because AOMPROC was not active, and the number lost due to storage shortages.
System Action:
None.
User Action:
None.
Reason:
This message is produced when a SHOW AOMSTAT option that is not supported in the current environment is requested. It indicates that the option is unsupported.
System Action:
None.
User Action:
Re-enter the command with the correct options. Refer to the AOM guide.
Reason:
This line indicates the end of an AOM statistics display.
System Action:
None.
User Action:
None. This message can be used to indicate the end of an &INTREAD of an AOM statistics display.
Reason:
This message is issued at 30 second intervals when the AOM DOM queue exceeds the value of SYSPARMS AOMDQLIM and new entries are still being added.
System Action:
None.
User Action:
Investigate the reason for the DOM queue limit being exceeded (you can use the SHOW AOMDOMQ command to list entries on the queue) and increase the SYSPARMS AOMDQLIM value if feasible.
Reason:
AOM/MVS detected a previous execution of AOM that had not been terminated cleanly. Old CSA storage used will be freed.
System Action:
The storage is freed.
User Action:
None.
Reason:
A component of AOM/MVS has abended. Abend details are sent to all AOM and MON class receivers. The message indicates the AOM component (SSI or SRB), the abend type (SYS or USER), and abend code. The date and time is also shown. This message is Non-Roll-Delete and is deleted only when an AOM STOP command is issued. The activity log contains N83D10 to N83D12 messages with more information.
System Action:
The MVS AOM code is disabled.
User Action:
See the activity log for abend information. Contact Technical Support for more information.
Reason:
This log message provides information about an AOM abend. The message indicates the detected module name (xxxxxxxx), the type of ABEND (SYS or USER) and the ABEND code.
System Action:
AOM is disabled.
User Action:
Refer this message to your product support representative.
Reason:
This log message provides more AOM abend information.
System Action:
AOM is disabled.
User Action:
Refer this message to your product support representative.
Reason:
This log message provides more AOM abend information.
System Action:
AOM is disabled.
User Action:
Refer this message to your product support representative.
Reason:
This log message provides more AOM abend information. The message identifies modules (Nxxx) and their start/end addresses (ssssssss/ eeeeeeee) which can be useful at debugging.
System Action:
AOM is disabled.
User Action:
Refer this message to your product support representative.
Reason:
This message informs that AOM/VM has successfully established an IUCV connection to PROP, which is running in the indicated virtual machine.
System Action:
AOM/VM is active.
User Action:
Commands may be issued using SYSCMD DEST=PROP.
Reason:
AOM/VM received a retriable IUCV connect error. It will retry the connection as indicated.
System Action:
AOM/VM waits as indicated before retrying.
User Action:
Check the earlier connect fail reason and take corrective action if necessary. The AOM STOP, SYSPARMS AOMPROPI and SYSPARMS AOMPCRIN commands may be issued.
Reason:
AOM/VM encountered a non-zero IUCV connect error code when attempting to establish a connection to PROP. Some of these are retriable, and after a delay, AOM/VM will try again. Others are fatal, and only the AOM STOP command may be issued.
System Action:
AOM/VM will delay and try again, if a retriable error is detected. For fatal errors, AOM/VM will become dormant, awaiting an AOM STOP command.
User Action:
Correct the error if possible. For a fatal error, issue an AOM STOP and AOM START after correcting the problem. For retriable errors, just correct the problem if possible. AOM/VM will automatically retry.
Reason:
AOM/VM received an IUCV sever from PROP, either during AOM startup, or later on.
System Action:
AOM/VM will keep retrying an IUCV connect.
User Action:
Determine why PROP sent a SEVER. Possible causes include PROP being stopped, or the virtual machine being logged off.
Reason:
AOM/VM received an IUCV connect request from a machine other than the one identified by the SYSPARMS AOMPROPI= command.
System Action:
The connection is refused.
User Action:
If the machine is the correct one for PROP, issue a SYSPARMS AOMPROPI=userid command. Otherwise, determine why it issued the connect request.
Reason:
This message follows SYSCMD responses received from PROP.
System Action:
Another SYSCMD request can be sent to PROP.
User Action:
None. All responses to SYSCMD are complete.
Reason:
A SYSCMD DEST=PROP request has been rejected. The reason is indicated.
System Action:
None. The command will not be sent to PROP.
User Action:
Take corrective action based on the supplied reason. If too many commands are pending, PROP is possibly hung.
Reason:
The current command being executed by PROP has taken longer than the time specified by SYSPARMS AOMCTO1, plus any DELAY specified on the SYSCMD command.
System Action:
This message is sent to the command issuer and all monitor receivers. No further action can be taken, as PROP is in a separate virtual machine.
User Action:
Determine the reason for the delay.
Reason:
PROP has sent a positive response in reply to the AOM/VM LGLOPR RPL command.
System Action:
AOM/VM can now receive unsolicited console traffic.
User Action:
None.
Reason:
PROP did not accept the AOM/VM LGLOPR RPL command. AOM/VM will not be the logical operator. No unsolicited message traffic can be received.
System Action:
None.
User Action:
Determine why PROP rejected the LGLOPR RPL command. Possibly the PROP routing table does not authorize the AOM/VM userid (normally .AOMVUIL) for this command.
Reason:
Another VM virtual machine has issued a LGLOPR RPL command to PROP.
System Action:
AOM/VM will reissue the LGLOPR RPL in an attempt to reobtain the logical operator.
User Action:
Determine why another user issued the command. Take corrective action. PROP only allows one logical operator.
Reason:
AOM/VM has successfully established a connection to the *MSG system service for the GCS machine that the region is executing under.
System Action:
SYSCMD DEST=GCS commands are now accepted.
User Action:
None.
Reason:
AOM/VM received a non-zero IUCV connect return code when attempting to connect to the *MSG CP system service.
System Action:
AOM/VM will not connect to *MSG. SYSCMD DEST=GCS will be rejected.
User Action:
Determine why the connection failed and correct the problem.
Reason:
AOM/VM received an IUCV SEVER from the *MSG service.
System Action:
SYSCMD DEST=GCS will not be accepted.
User Action:
Determine why the connection was severed. Another program in the same GCS machine may be connected.
Reason:
AOM/VM received an unexpected IUCV connect request from another machine on it's *MSG connection path.
System Action:
AOM/VM refuses the connection.
User Action:
Determine why the connection was attempted.
Reason:
This is the last line received from a SYSCMD DEST=GCS command. It indicates that all responses have been received, and the return code. The return code can be RC WAS n, indicating the command was executed, with a return code of n, SYSTEM ABEND code or USER ABEND code, which indicates that the command abended with the indicated code.
System Action:
Another SYSCMD DEST=PROP command can be executed.
User Action:
The return code indicates the success or failure of the command.
Reason:
AOM/VM rejected the SYSCMD DEST=GCS command. The reason is shown.
System Action:
The command is not passed to GCS.
User Action:
The reason should be investigated. If it is TOO MANY COMMANDS PENDING, a long running GCS command may be executing.
Reason:
The current command being executed by GCS has taken longer than the time specified by SYSPARMS AOMCTO2, plus any DELAY specified on the SYSCMD command.
System Action:
This message is sent to the command issuer and all monitor receivers. No further action can be taken, as the GCS command task cannot be interrupted.
User Action:
Determine the reason for the delay.
Reason:
AOM/VM has lost some responses to a SYSCMD DEST=GCS, due to IUCV queue overflows.
System Action:
This warning message is issued.
User Action:
Check whether the SYSPARMS AOMVEQSZ parameter is too small (use SHOW AOMSTAT=TUNING).
Reason:
AOM was unable to queue a message to AOMPROC due to a storage shortage.
System Action:
This message is queued to AOMPROC to inform it of the problem.
User Action:
A larger region may be required, or AOMPROC processing is too slow.
Reason:
An AOMPROC queue has too many messages queued. The value of the AOMPQLIM sysparm was exceeded. The oldest message(s) are removed and delivered. This message is enqueued to AOMPROC informing it that messages have been lost.
System Action:
This message replaces the dropped messages.
User Action:
AOMPROC should recognize this message (AOMMSGID is set to N83K02) and take corrective action.
Reason:
A REPLY or ISSUE statement in the active AOM screening table has been disabled, after being executed more than AOMRILC times in AOMRILT seconds (These are the relevant SYSPARM names). The relative number of the reply or issue from the front of the table is shown, as is the table name and date and time of compilation. In MVS, this message is issued via WTO. In VM, it is sent to monitor receivers.
'mmmmmmmm' is the member name of the screening table. 'dd-mmm...' is the date and time the screening table was loaded.
System Action:
The indicated reply or issue statement is disabled until a new table is loaded.
User Action:
Determine why the statement was issued so frequently. If ok, adjust the AOMRILT and AOMRILC SYSPARM values.
Reason:
This message is one of a set of messages produced for each AOM message when AOM tracing is active. The fields of the message are:
seq The last 3 digits of an AOM-provided sequence number. All trace messages for a single AOM message will be grouped under this sequence number.
hhmmss The original message time.
type The message type, either WTO, WTOR, MSG, or EVNT
ss The message subtype flags. This is a hex value. For an EVENT, displays as a dash. The value is the sum of the following bits: 80 Always on for any WTO or MSG, off if a WTOR. 40 On for a WTOR, else off. 20 On if a WTO is a single-line WTO or MSG. 10 On if a WTO is the major line of a multi-line WTO (MLWTO) 08 On if a WTO is a minor line of a MLWTO. 04 On if the message is force-delivered as it is destined for a SOLVE assigned console. 02 On if the message is force-routed by AOM tracing being active (always on in trace messages). 01 On if this WTOR (see 40 above) was replied to by a screening-table WTOR statement.
odmn The originating SOLVE domain that the message came from.
ldmn The last handing SOLVE domain that the message came from.
os The message source operating system, OS (MVS, etc.) or VM.
JN,JI For OS-sourced messages, the message JOBNAME and JOBID.
UI,UN For VM-sourced messages, the message USERID and USERNODE.
System Action:
None.
User Action:
None.
Reason:
This message is one of a set of messages produced for each AOM message when AOM tracing is active. This message is not displayed for an EVENT message trace. The fields of the message are:
seq displays the last 3 digits of an AOM-provided sequence number, which matches the number of the previous N83T01 message.
sol displays one of the following the message solicit types:
NO indicates unsolicited messages. NM indicates messages solicited by an AOM user. OT indicates messages solicited by other users.
lev displays the message severity level.
desc displays the message descriptor codes in hexadecimal format.
routcde displays the message routing codes in either hexadecimal or list format, depending on the value of the AOMTRCRC system parameter setting.
System Action:
None.
User Action:
None.
Reason:
This message is one of a set of messages produced for each AOM message when AOM tracing is active. This message applies only to MVS sourced messages that are traced. The fields of the message are:
The last 3 digits of an AOM-provided sequence number. This matches the number of the previous N83T01 message.
The message MCS flags, in hexadecimal.
The message type flags, in hexadecimal.
The message line type. For a single line WTO or a WTO, 'NO'. For a line of a Multi- Line WTO, it will be 'C' (Control), 'L' (Label), 'D' (Data), 'E' (End), or 'xE' when one of the previous (C/L/D) lines is also the last line.
The MVS console ID, or 0.
The JES console number, if applicable, or 0.
The Extended MCS console name, if applicable.
System Action:
None.
User Action:
None.
Reason:
This message is one of a set of messages produced for each incoming WTO/R/EVENT message when AOM trace is active. It is only produced for MVS-sourced messages. The fields in the message are:
seq A 3-digit sequence number that allows matching up of all associated trace messages.
jobname The issuing jobname of the WTO/R/EVENT (That is, the jobname that the WTO/R was issued from)
sysname The system name, if known.
conid The Extended MCS fullword console id.
System Action:
None.
User Action:
None.
Reason:
This message is the third of a set of messages produced for each AOM message when AOM tracing is active. This message only applies to VM- sourced messages that are traced. The fields of the message are:
seq The last 3 digits of an AOM-provided sequence number. This will match the number of the previous N83T01 message.
mcls The IUCV message class, from 1 to 30.
src The message source, either PROP or GCS.
System Action:
None.
User Action:
None.
Reason:
This is one of a set of messages produced by the AOM message tracing facility for each AOM message processed. The fields are:
seq The same sequence number as in the N83T01 message.
xxxxxxxxxxxx The screening table assigned ID= value.
rr The screening table assigned ROUTE= options. The first letter is the local route, the second the remote route. Values are: F Message failed global screening. P ROUTE=PROC assigned. O ROUTE=PROCONLY assigned. B ROUTE=BOTH assigned. M ROUTE=MSG assigned. L ROUTE=LOG assigned. N ROUTE=NO assigned.
d The screening table assigned DELETE= option, Y or N.
s The screening table assigned SYSLOG= option, Y or N.
a The screening table assigned ALARM= option, Y or N.
m The screening table assigned MONITOR= option, Y or N.
n The screening table assigned NRD= option, Y or N.
i The screening table assigned INTENS= option, H or L.
h The screening table assigned HLIGHT=option. Values are: N None. D Default. R Reverse. U Uscore. B Blink.
c The screening table assigned COLOUR= option. Values are: N None. D Default. B Blue. G Green. P Pink. R Red. T Turquoise. W White. Y Yellow.
mm The screening table assigned MSGCODE= value (in hex).
uu The screening table assigned UFLAG1-8 values, in hex (UFLAG1 is the 80 bit, down to UFLAG8 being the 01 bit).
rr The screening table assigned RMTCLASS values, in hex (RMTCLASS=1 is the 80 bit, RMTCLASS=8 being the 01 bit).
System Action:
None. The message is logged.
User Action:
The message may be examined to determine any AOM screening table adjustments required.
Reason:
This is one of a set of messages produced by the AOM message tracing facility for each AOM message processed. The fields are:
seq The same sequence number as in the N83T01 message.
lll The length of the message text, or, for a MINOR line, the length of the major line of text.
text The message text, or, for a minor line, the major-line text (TEXT in the screening table).
System Action:
None.
User Action:
None.
Reason:
This is the seventh of several messages produced by the AOM message tracing facility for each AOM message processed. This message is only produced for a minor line of a multi-line WTO, to show the actual minor line text. The fields are:
seq The same sequence number as in the N83T01 message.
lll The length of the minor line message text.
minor-text The minor line message text (ATEXT in the screening table).
System Action:
None.
User Action:
None.
Reason:
This message is the second of a set of messages produced for each AOM EDSEVENT message when AOM tracing is active. The fields of the message are:
seq The last 3 digits of an AOM-provided sequence number. This will match the number of the previous N83T01 message.
domid The MVS DOMID.
s Identifies the scope of the EDSEVENT (System or Region).
tp Identifies the type of the EDSEVENT (APlication, SErviceability UTilisation, COnfiguration, ACcess and PRocedural).
routcd The routing code of the EDSEVENT request in hexadecimal or in bitlist format depending on the SYSPARMS AOMTRCRC definition.
System Action:
None.
User Action:
None.
Reason:
This message is the fourth of a set of messages produced for each AOM EDSEVENT message when AOM tracing is active.
seq The same sequence number as in the N83T01 message.
text Describes the defined keywords/value of the AOM EDSEVENT. Following mnemonics are used :
- NAM= ... for NAME= ...,
- OBJ= ... for OBJECT= ...,
- RES= ... for RESOURCE= ...,
- REF= ... for REFERENCE= ...,
- DAT= ... for DATA= ....
The text contains only the keywords specified on the EDSEVENT Screening Table statement.
System Action:
None.
User Action:
None.
Reason:
This message is one of a set of messages produced for each AOM message when AOM tracing is active. The fields of the message are:
seq The last 3 digits of an AOM-provided sequence number. This will match the number of the previous N83T01 message.
msgid The MSGID value.
domid The MVS DOMID.
class If this is an EVENT message, the event class.
System Action:
None.
User Action:
None.
Reason:
The number of local messages indicated by the SYSPARMS AOMTRLIM value has been reached. AOM trace is suspended.
System Action:
AOM tracing of locally sourced messages stops.
User Action:
Restart trace if necessary.
Reason:
The number of remote messages indicated by the SYSPARMS AOMTRLIM value has been reached. AOM trace is suspended.
System Action:
AOM tracing of remote sourced messages stops.
User Action:
Restart trace if necessary.
Reason:
While attempting to reserve a system linkage index, an ABEND occurred.
System Action:
AOM does not start.
User Action:
Determine the reason for the abend. The most common is a shortage of system linkage indexes (abends SYS-053 rc 111/112). AOM can be started in non-XMS mode in the meantime (use SYSPARMS AOMXMS=NO;AOM START). Contact your product support representative.
Reason:
The AOM screening table compiler has found that the current value of the AOM SYSPARMS AOMSTDDN (ddname), or AOMSTMEM (member name) were invalid or blank. Thus no compile was possible.
System Action:
The screening table compile is cancelled.
User Action:
Select new parameter values for the SYSPARMS AOMSTDDN or SYSPARMS AOMSTMEM commands. The AOMSTDDN value may only be altered by the NMINIT or NMREADY NCL procedures.
Reason:
The AOM screening table compiler has commenced compiling the nominated member, from the nominated library.
System Action:
The compile continues.
User Action:
None.
Reason:
The AOM screening table compiler has completed a compilation. The number of errors detected is shown. The size of the generated code (in hex) is shown by `C=aaaa'. The size of the generated literal pool (in hex) is shown by `L=bbbb'. The total (code + literal + other overheads) size (in hex) is shown by `T=cccc'. The maximum available size the compiler is configured for is shown (in hex) by `mmmm'. The usage and available size of the extended literal pool is shown (in hex) by `X=xxxx/yyyy'.
System Action:
The compile has ended.
User Action:
If the number of errors is not zero, review the accompanying error messages.
Reason:
The AOM screening table compiler successfully compiled the table, and has swapped in the compiled version, thus making it active.
System Action:
The new table is now being used by AOM.
User Action:
None.
Reason:
The AOM screening table compiler tried unsuccessfully to swap in the new table after a successful compile. The old table was `in use' each time it tried. The compiler tries 10 times before this message is produced.
System Action:
The compiled table is discarded.
User Action:
Rerun the compile. If heavy message traffic constantly causes this message to be generated, use AOM STOP/AOM START to load the new table.
Reason:
The AOM screening table compiler has found that the current value of the AOM SYSPARMS AOMSTFTY (filetype), or AOMSTMEM (file name) were invalid or blank. Thus no compile was possible.
System Action:
The screening table compile is cancelled.
User Action:
Select new parameter values for the SYSPARMS AOMSTFTY or SYSPARMS AOMSTMEM commands. The AOMSTFTY value may only be altered by the NMINIT or NMREADY NCL procedures.
Reason:
The AOM screening table compiler has commenced compiling the nominated CMS filename, filetype on the indicated disk.
System Action:
The compile continues.
User Action:
None.
Reason:
The AOM screening table compiler was unable to obtain the necessary working storage to run.
System Action:
The compile is aborted.
User Action:
Rerun the compile. If this message is constantly occurring, investigate the reason for the acute storage shortage in SOLVE. This storage is obtained above the 16M line in MVS/XA or MVS/ESA.
Reason:
The AOM screening table compiler has found an unrecognized statement. The displayed keyword is not a valid statement keyword (eg GLOBAL, WTOR, etc).
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. This message can occur if a member of a library that is not a screening table is accidentally nominated for a compile, or if a statement keyword is misspelled, or if a continuation character (+) is accidentally left off of a previous line.
Reason:
The indicated statement cannot be coded after an IF or ELSE statement. token is not a keyword.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. Refer to message N84201 for possible causes.
Reason:
The indicated statement may only be coded after an IF or ELSE statement, or within a DO group that commenced on an IF or ELSE statement. second global statement was encountered.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The indicated statement cannot be coded after an IF or ELSE statement, or within a DO group. For example, a GLOBAL statement. WTOR statements must follow the GLOBAL statement (if present), and precede all other screening statements.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler has encountered an unexpected keyword. statements. The second cannot therefore be reached by any messages, and this is regarded as an error.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found the end of a statement when more information was expected. This could be due to a missing continuation.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found a statement in a MESSAGE or COMMAND section that is not allowed there.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found a statement that cannot be reached at execution time, as all possible paths to this statement exit the screening table (for example, an ACCEPT statement in the COMMAND section).
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found a statement that is not supported on this operating system. For example, a WTOR statement in AOM/VM.
System Action:
The compile continues, for error checking purposes only. file).
User Action:
Use the error information in the message to find and correct the error. A '+' continuation may be missing. This can lead to another error on the next source line.
Reason:
The AOM screening table compiler reached the end of the screening table source, but there were unpaired DO statements.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler reached the end of the screening table source, but it found no processing statements, only comments and/or control statements.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler detected an out of sequence statement. For example, a WTOR statement that was not after the GLOBAL statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. Refer to the AOM screening table syntax descriptions in the AOM manuals.
Reason:
The AOM screening table compiler has found two logically adjacent MSGGROUP statements. The second cannot therefore be reached by any messages, and this is regarded as an error. This includes the condition where the only statements between two MSGGROUP statements do not reject any messages.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found a MSGGROUP statement that was followed by end of file. This last MSGGROUP is therefore always true. This is a warning message only.
System Action:
The compile continues.
User Action:
Ensure that this is the correct action. This error can occur if an error is made in the match- criteria coded on the WTOR statement.
Reason:
The AOM screening table compiler encountered a statement label error. The reason can be as follows:
- LABEL LONGER THAN 8 CHARACTERS: label
- END-STMT AFTER LABEL
- LABEL NOT ALLOWED ON A NESTED STATEMENT
- xxxxxxxx STATEMENT CANNOT HAVE A LABEL
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an unrecognized token in the nominated statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an iterative DO syntax error. The reason can be as follows:
- EXPECTED 'IX', FOUND xxxxxxxx
- EXPECTED '(', FOUND xxxxxxxx
- EXPECTED INDEX NUMBER, FOUND xxxxxxxx
- INDEX NUMBER nnnnnnnn CURRENTLY ACTIVE
- EXPECTED ')', FOUND xxxxxxxx
- EXPECTED '=', FOUND xxxxxxxx
- 'FROM' NUMBER NOT 1:256
- EXPECTED 'TO', FOUND xxxxxxxx
- 'TO' NUMBER NOT 1:256
- 'TO' NUMBER LESS THAN 'FROM' NUMBER
- 'DOWNTO' NUMBER GREATER THAN 'FROM' NUMBER
- INVALID SYNTAX AFTER 'TO' VALUE: xxxxxxxx
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a statement error. The reason can be as follows:
- INVALID LABEL: xxxxxxxx
- NOT END-STATEMENT AFTER LABEL
- NOT NESTED IN AN ITERATIVE 'DO'
- LABEL: xxxxxxxx NOT FOUND IN AN ENCLOSING 'DO'
- LABEL: xxxxxxxx IS NOT AN ITERATIVE 'DO' LABEL
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found a PROCESS statement with an invalid type. The value was not MESSAGES or COMMANDS.
System Action:
The compile is terminated.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found a PROCESS statement with a type that had been already encountered. This includes the case where a screening table started without a PROCESS statement, and thus a PROCESS MESSAGES statement was assumed.
System Action:
The compile is terminated.
User Action:
Use the error information in the message to find and correct the error. Refer to the AOM screening table reference documentation regarding the statement sequence required.
Reason:
The AOM screening table compiler encountered a PROCESS STATEMENT with a valid type that is not supported in the current environment. For example, a PROCESS COMMANDS statement in VM.
System Action:
The compile is terminated.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered more than 32 DEFCOND statements in the screening table.
System Action:
The compile continues, for error checking purposes only.
User Action:
Remove the excess number of DEFCOND statements.
Reason:
The AOM screening table compiler encountered a duplicated DEFCOND name.
System Action:
The compile continues, for error checking purposes only.
User Action:
Remove or rename the duplicated DEFCOND statement.
Reason:
The AOM screening table compiler encountered an invalid DEFCOND condition name. This must be a 1 to 12 character word.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. It is possible that an error in the match-criteria for this defcond generated this error message.
Reason:
The AOM screening table compiler encountered more than 32 DEFCOND statements in the current section of the screening table.
System Action:
The compile continues, for error checking purposes only.
User Action:
Remove the excess DEFCOND statements.
Reason:
The AOM screening table compiler encountered a duplicated DEFCOND condition name in the current section.
System Action:
The compile continues, for error checking purposes only.
User Action:
Remove or rename the duplicated DEFCOND statement.
Reason:
The AOM screening table compiler found unexpected data after processing the criteria on an IF statement, where a THEN keyword must be coded.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found an ELSE statement where one is not valid. ELSE statements must follow an IF statement, or the DOEND that pairs with a DO statement that was on an IF statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a DOEND statement, but there are no current DO groups (DO statements) active.
System Action:
The compile continues, for error checking purposes only.
User Action:
Remove or reposition the offending DOEND statement.
Reason:
The AOM screening table compiler encountered unexpected data at a point where a statement should have terminated.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered end-of-file after the last MSGGROUP statement in the input. Thus, all messages reaching this MSGGROUP statement will pass it.
System Action:
The compile continues. This is a warning message only.
User Action:
Check that this is the desired action.
Reason:
The AOM screening table compiler expected a valid word or string to be used as text for an ISSUE statement. The data encountered was invalid.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a WHEN statement with no SET or ISSUE clause. One of these is required for each WHEN, or each ELSE part of a WHEN statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found the TEXT='text' parameter as well as the MSGTEXT=YES or CMDTEXT=YES parameters on an EVENT statement. This combination is invalid.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a SET clause a second time in a WHEN or WTOR statement (for WHEN, more than once within each ELSE).
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a SET clause on a WTOR statement, but the keyword CONTINUE was not coded. This keyword is required to allow the SET processing to take effect.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a SET clause on a WHEN statement that also had REJECT coded. This is not permitted, as the SET options will be ignored if the message is rejected.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a GLOBAL statement that had MPFATTR=YES coded, as well as the COLOUR, HLITE, or INTENS attributes specified. Since MPFATTR=YES causes these attributes to be automatically assigned, these operands may not be specified in this case.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an invalid keyword on the WTOR statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found more than one REPLY clause on the indicated WTOR statement. SET clause. For example, ADDMVSRC AND NEWMVSRC are mutually exclusive.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler did not find a valid literal after the REPLY keyword on a WTOR statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler did not find a REPLY clause on a WTOR statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found a REJECT statement with no criteria (that is, an unconditional REJECT). This is only permitted if the REJECT statement is contained within the scope of an IF or ELSE statement, either on the IF or ELSE statement itself, or within a DO/DOEND group that is within an IF/ELSE.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found an unrecognized keyword on a WHEN statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. You should convert all WHEN statements to IF/ELSE/DO.
Reason:
The AOM screening table compiler encountered a token other than the ELSE keyword, or end-of-statement, while processing a WHEN statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. You should convert all WHEN statements to IF/ELSE/DO.
Reason:
The AOM screening table compiler did not find any actions for the current WHEN statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. You should change all WHEN statements to IF/ELSE/DO.
Reason:
The AOM screening table compiler expected a valid WHEN statement keyword after the ELSE keyword, but did not find one. The value found is shown.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered unexpected data at a point where a statement should have terminated.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found invalid data where it expected text for the REISSUE statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found invalid data where it expected text for the MESSAGE statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found invalid data where it expected text for the REPLACE statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an invalid subroutine definition name (DEFSUB). This must be a 1 to 12 character word.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered more than 127 subroutine definitions (DEFSUBs) in the current COMMAND or MESSAGE section.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an existing subroutine definition, ie: DEFSUB xxxxxxxx is previously defined in the current COMMAND or MESSAGE section.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an ENDSUB or RETSUB statement but a subroutine definition was not opened (DEFSUB xxxxxxxx) previously.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an undefined subroutine name on the GOSUB xxxxxxxx statement. Subroutines must be defined before referencing them.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a recursive subroutine call. Recursion is not supported by the screening table.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered more than 32 nested subroutine calls. The nesting of the subroutine calls is limited. It is also limited the size of the subroutine call table which contains the subroutines external subroutine references (GOSUB). The number of table entries is limited to 1500.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an unclosed subroutine definition at the end of the COMMAND or MESSAGE section. Subroutine definition (DEFSUB) must be closed by the ENDSUB statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an overlapped iterative DO statement index usage in the target subroutine. The index variables are 'global' variables and overlapping these DO index variables during subroutine calls is not allowed.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a numeric keyword/value error on the iterative DO statement. The reason can be as follows:
- EXPECTED NUMBER OR KEYWORD, FOUND xxxxxxxx
- NO INDEXING ALLOWED FOR xxxxxxxx
- INDEXING REQUIRED FOR xxxxxxxx
- EXPECTED A NUMBER OR 'IX', FOUND xxxxxxxx
- INDEX NUMBER xxxxxxxx NOT IN VALID RANGE
- EXPECTED '(' AFTER 'IX'
- EXPECTED AN INDEX NUMBER, FOUND xxxxxxxx
- xxxxxxxx IS NOT A VALID IX(n) NUMBER
- EXPECTED ')' AFTER IX(n..., FOUND xxxxxxxx
- EXPECTED ')' AFTER INDEX, FOUND xxxxxxxx
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a variable name/value error. The reason can be as follows:
- NO INDEXING ALLOWED FOR xxxxxxxx
- INDEXING REQUIRED FOR xxxxxxxx
- EXPECTED A NUMBER OR 'IX', FOUND xxxxxxxx
- INDEX NUMBER xxxxxxxx NOT IN VALID RANGE
- EXPECTED '(' AFTER 'IX' - EXPECTED AN INDEX NUMBER, FOUND xxxxxxxx
- xxxxxxxx IS NOT A VALID IX(n) NUMBER
- EXPECTED ')' AFTER IX(n..., FOUND xxxxxxxx
- EXPECTED ')' AFTER INDEX, FOUND xxxxxxxx
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an unrecognisable keyword for the current statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler did not find a valid subscript when it expected one. Subscripts must be in the format (n) and n must be from 1 to the relevent maximum allowed.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler found a keyword that duplicated an earlier keyword, or was mutually exclusive with an earlier keyword on this statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an invalid value for the indicated keyword.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an invalid value for the indicated keyword. The value must be a word, not exceeding the allowable length.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an invalid value for the indicated keyword. The value must be an even number of hexadecimal digits.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler did not find a valid text value for the indicated keyword. The value should be a string enclosed in quotes.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler did not find a required closing parenthesis.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler expected a valid keyword for the current statement, or end of statement, but neither was found. The value found is shown.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. A keyword is possibly misspelt.
Reason:
The AOM screening table compiler encountered a keyword kwrd that, while valid for the current statement, is not supported in this environment. For example, the DELETE option of the GLOBAL statement is not supported in AOM/VM.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a kwrd keyword that, while supported by the current statement, is not supported in the current screening table section. For example, MSGATTR on the EVENT statement is not supported in the COMMANDS section.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler was unable to obtain working storage while processing a statement. It is unable to continue processing.
System Action:
The compile terminates.
User Action:
Determine why the region is short on storage.
Reason:
The AOM screening table compiler encountered an empty value specification for the 'keyword'. A correct value must be assigned to the keyword used on the current statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an internal literal area length limitation. The total length of the literals used on the statement (eg.: EDSEVENT keyword=literal ...) exceeds this limitation.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an invalid index/subscript value specification or dynamic indexing not allowed for the keyword. Setting index variables is only permitted for IX(9) to IX(12). Index variables from 1 to 8 are reserved for iterative DO processing and cannot be set by another instruction.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered unexpected data at a point where a statement should have had '=', 'UP' or 'DOWN' specified.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The Screening Table compiler encountered an unlicensed statement type. The system must be licensed for AOM/Extension-2 to be able to use the requested function.
System Action:
The compilation continues, for error checking purposes only.
User Action:
Check with your product support representative.
Reason:
The AOM screening table compiler encountered an unexpected token while processing a match-criteria, when a closing parenthesis was expected.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered too many nested parentheses. The criteria are too complex.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. The maximum nesting of parentheses is 5. Use a DEFCOND statement to contain part of the criteria.
Reason:
The AOM screening table compiler encountered an unexpected end of statement or end of input file after an OR while processing criteria.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an unexpected end of statement or end of input file after an AND while processing criteria.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler was unable to obtain storage for a stack to process criteria.
System Action:
The compile is terminated.
User Action:
Determine why the region is short on storage.
Reason:
The AOM screening table compiler was asked to optimize the compiled table (this is the default). The optimizer will produce statistics on this. This heading indicates that the statistics follow.
System Action:
None.
User Action:
None.
Reason:
This message gives AOM screening table compiler optimizer statistics. `nnnnn' is the number, associated with `description'. Descriptions are:
PASSES - The number of passes the optimizer made over the code.
COND LINK L/ST REMOVED - The number of linkage instructions for CONDITION criteria that were removed.
BRANCHES NOP'D - The number of branch instructions that were removed, being redundant.
BRANCHES INVERTED - The number of branch instructions that had the condition inverted (usually in tandem with the previous optimization).
BRANCH CHAIN ADJUSTS MADE - The number of chained branches that were unchained.
(A)TEXT LEN BL UNCHAINS - the number of text length branch after test instructions that were unchained.
(A)TEXT LEN CLI/BL NOP'D - the number of redundant text length comparisons and branches that were removed.
ORIGINAL CODE SIZE - The size of the unoptimized code.
OPTIMISED CODE SIZE - The final optimized code size.
System Action:
None.
User Action:
None.
Reason:
The AOM screening table that has been compiled has generated too much code and literal storage for the configuration. The table is too complex.
System Action:
The compile is terminated.
User Action:
Simplify the table. If this is not possible, contact your product support representative.
Reason:
The AOM screening table compiler has had an overrun of the generated code into the generated literal pool. The table is too complex.
System Action:
The compile continues, for error checking purposes only.
User Action:
Simplify the table, if possible. If not, contact your product support representative.
Reason:
The AOM screening table compiler has had an overrun of the generated literal pool into the generated code. The table is too complex.
System Action:
The compile continues, for error checking purposes only.
User Action:
Simplify the table, if possible. If not, contact your product support representative.
Reason:
The AOM screening table compiler has had an overflow of the internal code label table. The table is too complex.
System Action:
The compile continues, for error checking purposes only.
User Action:
Simplify the table, if possible. If not, contact your product support representative.
Reason:
The AOM screening table compiler has had an overflow of the internal literal label table. The table is too complex.
System Action:
The compile continues, for error checking purposes only.
User Action:
Simplify the table, if possible. If not, contact your product support representative.
Reason:
The AOM screening table compiler has had an overflow of the extended literal pool during compilation.
System Action:
The compile continues, for error checking purposes only.
User Action:
Increase the size of the extended literal pool, using the SYSPARMS AOMSTSIZ=(a,b) command. (b is the extended literal pool size).
Reason:
The AOM screening table compiler has encountered a token in the input source which is too long. The value is truncated so the compile may continue.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler has encountered a quoted string that had no closing quote before the end of the statement or source file.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. Possibly, a statement continuation is missing.
Reason:
The AOM screening table compiler has encountered end of file when the last statement line had a continuation character (+) on it.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
This is an echo of the input to the AOM screening compiler, if a listing is requested. The input line will have the statement number from columns 73-80 moved to the front, if it is nonblank.
System Action:
None.
User Action:
None.
Reason:
The AOM screening table compiler has encountered an I/O error whilst reading the requested PDS member.
System Action:
The compile is aborted.
User Action:
Examine the activity log for further I/O error information.
Reason:
The AOM screening table compiler has encountered an error when opening the library indicated.
System Action:
The compile is aborted.
User Action:
Check that the PDS is allocated, and not security protected.
Reason:
The AOM screening table compiler found that the library nominated was not in the correct format. AOM screening table members must be fixed 80 byte records.
System Action:
The compile is aborted.
User Action:
Check that the correct library is specified.
Reason:
The AOM screening table compiler found that the library nominated did not contain the requested member.
System Action:
The compile is aborted.
User Action:
Check that the correct library and member names are specified.
Reason:
The AOM screening table compiler encountered an invalid or unknown variable when processing a REPLY or ISSUE string. Refer to the AOM manual for a list of the valid variable names.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error location information in the message to find and correct the error.
Reason:
The AOM screening table compiler has encountered an I/O error whilst reading the requested CMS file.
System Action:
The compile is aborted.
User Action:
Examine the activity log for further I/O error information.
Reason:
The AOM screening table compiler has encountered an error when opening the CMS file indicated.
System Action:
The compile is aborted.
User Action:
Check that the CMS minidisks are allocated to the region.
Reason:
The AOM screening table compiler could not find the CMS file indicated.
System Action:
The compile is aborted.
User Action:
Check that the correct filename, filetype, and filemode are specified.
Reason:
While attempting to initialize processing for an NCL virtual include file, the indicated global NCL variable was accessed. The value contained was not a number from 0 to 9999.
System Action:
The compile is aborted.
User Action:
Ensure that the correct NCL variable name was used on the % INCLUDE statement.
Reason:
While processing an NCL include file, the indicated variable contained a value longer than 72 characters.
System Action:
The compile is aborted.
User Action:
NCL include files must have individual lines no longer than 72 characters.
Reason:
The indicated % preprocessing line in the current screening table had a syntax error. The line could not be recognized as, for example, a % INCLUDE line.
System Action:
The compile is aborted.
User Action:
Correct the % line.
Reason:
The indicated % INCLUDE line does not contain a member or file name.
System Action:
The compile is aborted.
User Action:
Correct the % INCLUDE line.
Reason:
While processing a % INCLUDE line, an option surrounded by parentheses was found. The option is not recognized.
System Action:
The compile is aborted.
User Action:
Correct the % INCLUDE line.
Reason:
An option specified on a % INCLUDE line conflicts with or duplicates an earlier option.
System Action:
The compile is aborted.
User Action:
Correct the % INCLUDE line.
Reason:
The indicated name is not a valid PDS member name, or CMS file name, or NCL global variable prefix name.
System Action:
The compile is aborted.
User Action:
Correct the % INCLUDE line.
Reason:
An invalid parameter was found on a % INCLUDE line.
System Action:
The compile is aborted.
User Action:
Correct the % INCLUDE line.
Reason:
More than 5 nested % INCLUDE statements were found.
System Action:
The compile is aborted.
User Action:
Reorganize the % INCLUDE structure to have a maximum of 5 levels.
Reason:
The indicated % INCLUDE file was not found. The (OPTIONAL) parameter was specified, so the compile will continue as if the % INCLUDE line was not present. This is a warning message only.
System Action:
The compile continues.
User Action:
Check that this is the desired action.
Reason:
The indicated % INCLUDE file was not found. Since the (OPTIONAL) parameter was not specified, this is treated as an error.
System Action:
The compile is aborted.
User Action:
Ensure that the correct include file name was specified on the % INCLUDE statement.
Reason:
The indicated % INCLUDE NCL global variables were not found. The (OPTIONAL) parameter was specified, so the compile will continue as if the % INCLUDE line was not present. This is a warning message only.
System Action:
The compile continues.
User Action:
Check that this is the desired action.
Reason:
The indicated % INCLUDE NCL global variables were not found. Since the (OPTIONAL) parameter was not specified, this is treated as an error.
System Action:
The compile is aborted.
User Action:
Ensure that the correct include variable prefix was specified on the % INCLUDE statement.
Reason:
This message traces the start of an included file, to allow the file in which an error occurs during compilation to be detected.
System Action:
None.
User Action:
None.
Reason:
This message traces the end of an include file, to allow the file in which an error occurs during compilation to be detected.
System Action:
None.
User Action:
None.
Reason:
A numeric operand for an AOM screening table keyword was out of the valid range for that keyword. error-location indicates the source line and column where the error was detected. keyword is the screening table keyword.
System Action:
The screening table compile will continue, to detect other errors. The table will not be loaded.
User Action:
Use the error information in the message to identify and correct the error.
Reason:
value is not a valid value (keyword or number) for the AOM screening table keyword keyword.
System Action:
The screening table compile will continue, to detect other errors. The table will not be loaded.
User Action:
Use the error information in the message to identify and correct the error.
Reason:
Numeric ranges are not permitted as operands of this AOM screening table keyword keyword.
System Action:
The screening table compile will continue, to detect other errors. The table will not be loaded.
User Action:
Use the error information in the message to identify and correct the error.
Reason:
AOM screening table keywords that allow numeric ranges as operands (eg 5:10) require both sides of the range to be numeric. This message indicates a violation of that requirement.
System Action:
The screening table compile will continue, to detect other errors. The table will not be loaded.
User Action:
Use the error information in the message to identify and correct the error.
Reason:
AOM screening table keywords that allow keyword ranges as operands (eg MON:FRI) require both sides of the range to be a keyword. This message indicates a violation of that requirement.
System Action:
The screening table compile will continue, to detect other errors. The table will not be loaded.
User Action:
Use the error information in the message to identify and correct the error.
Reason:
The keyword pointed to by error-location is not permitted as a side of a keyword range (eg MON:FRI) for keyword.
System Action:
The screening table compile will continue, to detect other errors. The table will not be loaded.
User Action:
Use the error information in the message to identify and correct the error.
Reason:
The AOM screening keyword keyword does not allow circular (wrapped) numeric ranges eg 10:5.
System Action:
The screening table compile will continue, to detect other errors. The table will not be loaded.
User Action:
Use the error information in the message to identify and correct the error.
Reason:
The AOM screening keyword keyword does not allow keyword ranges eg MON:FRI.
System Action:
The screening table compile will continue, to detect other errors. The table will not be loaded.
User Action:
Use the error information in the message to identify and correct the error.
Reason:
The indicated token is not a word or quoted string. LOOKUP values must be one of these.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
The indicated token contains wildcard characters that are not escaped by a backslash. WILDCARDS are not permissable in the value lists for a LOOKUP criteria. Tokens containing an asterisk must be preceded by a backslash (\) to prevent its identification as a wildcard character.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
The indicated LOOKUP value is too long for the field being searched. This is also possible with substrings of the search field.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
A range of values (A:B) for a LOOKUP criteria has a `to' value less than the `from' value.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
The list of values for a LOOKUP criteria contains overlapping or duplicated values.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
While processing a LOOKUP criteria value list, the AOM compiler was unable to obtain working storage.
System Action:
The screening table compile continues for syntax checking only. No table will be loaded.
User Action:
Review the region size, and so on and then retry the compile.
Reason:
The maximum amount of core or table space needed to compile the LOOKUP statement has been exceeded. The list contains too many values or is too long.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Attempt to simplify the size of the LOOKUP list. Consider using a mirrored VARTABLE instead.
Reason:
The LOOKUP keyword required either a list of value surrounded by parenthesis (), or the keyword TABLE, indicating a mirrored VARTABLE lookup. Neither was found.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
A LOOKUP list contained a parenthesized option at the start of the list. The option, however, was not a valid LOOKUP option.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
A LOOKUP list option was not followed by a closing parenthesis. This is required.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
A LOOKUP TABLE criteria did not have a valid table name specified.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
At this point, the LOOKUP criteria syntax requires the word EQUAL or IGEN to be specified.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
At this point in the LOOKUP criteria syntax, a closing parenthesis was expected. Instead, the indicated token was found.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax and re-compile.
Reason:
The total length of all literals in the indicated LOOKUP criterion has exceeded the current design limit of 8 Kbytes.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Break the LOOKUP criterion into 2 criterions, and OR them together.
Reason:
The automatic determination of lookup strategy was overridden by the user. The override specified SERIAL, but this search type is inefficient for lists with more than a very small number of entries. This warning message is produced as a reminder.
System Action:
The screening table compile continues. This is a warning message only.
User Action:
Ensure that the override is really required.
Reason:
The automatic determination of lookup strategy was overridden by the user. The override specified ORDERED, but this search type is inefficient for lists with more than a small number of entries. This warning message is produced as a reminder.
System Action:
The screening table compile continues. This is a warning message only.
User Action:
Ensure that the override is really required.
Reason:
The automatic determination of lookup strategy was overridden by the user. The override specified INLINE, but this search type is space inefficient for lists with more than approximately 300 entries. This warning message is produced as a reminder.
System Action:
The screening table compile continues. This is a warning message only.
User Action:
Ensure that the override is really required.
Reason:
The automatic determination of lookup strategy was overridden by the user. The override specified SUBROUTINE, but this search type is inefficient for lists with less than approximately 20 entries. This warning message is produced as a reminder.
System Action:
The screening table compile continues. This is a warning message only.
User Action:
Ensure that the override is really required.
Reason:
The AOM screening table compiler encountered an unexpected end-of- statement or end- of-file while processing a selection criteria.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a null subparameter list after a match keyword, for example ROUTCDE(). This is not valid.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a keyword that was not a valid match criteria keyword, when one was expected.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. You may have misspelled a keyword, for example TAXT instead of TEXT.
Reason:
The AOM screening table compiler encountered a string match value that was too long or, when shifted by the specified starting position, extended past the possible field length.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a match string for a text comparison that also had a match range specified. The range was less than the length of the string, for example, TEXT(`ABCDEF',1:3). The end range must specify the position of the last character of the search string.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered the shown value when expecting either a word or quoted string.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a search string that, after processing any wildcard characters, became empty for example, TEXT(`*') is invalid, as it means `match any character'.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a match string that was too long for the specified keyword, eg: a 9-character JOBNAME match string.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a number range value that was not valid. It was either not numeric, not an `*', not less than 1, or greater than the maximum value allowed for this keyword.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a number range end value that was not valid. It was either not numeric, not an `*', not less than the start position specified, or greater than the maximum value allowed for this keyword.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a token that was neither a number, nor an asterisk. The syntax requires either a number or an asterisk at this point.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a token that was not a valid argument for the specified keyword, for example MPFSUPP(YES).
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a token that was not a valid time, either 2, 4, or 6 digits, in the range 000000 to 240000.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a token that was not a valid end time in a time range. The value was not numeric, 2, 4, or 6 digits, range 000000:240000, or was less than the specified start time.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a token that was not a valid end time.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a token that was not a valid condition name, for example COND( ).
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a valid condition name, but this name has not been defined by a previous DEFCOND statement.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered two match strings of unequal length when processing a text range match. For example, TEXT(ABC:DEFG). Both match strings must have the same length for a text range match. This includes leading and/or trailing wildcard *'s.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a `from' match string with wildcard characters in it, when processing a text range match. Neither string may have wildcards in this case.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a `to' match string with wildcard characters in it, when processing a text range match. Neither string may have wildcards in this case.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a match string range, that also had a position range, for example TEXT(ABC:DEF,1:10). This is not supported.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a text string range, where the `to' string value was not greater than the `from' string value.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler expected a valid subscript for a criteria, but no subscript was supplied, or had an invalid format.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an unexpected keyword for a particular criteria. The value shown is not recognized.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The supplied list of parameters has too many entries for the supplied criteria name.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error. Check the required syntax of the criteria.
Reason:
A right parenthesis was expected, but one was not encountered. The indicated token was found.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered an invalid substring notation for a field. The start or length parameters may be invalid, not numeric, or out of range. etc.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered substring notation. The indicated field does not allow substring notation.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered the exact equal (==), or exact not equal operators. The specified criteria does not allow exact equal, etc.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered the exact equal or not equal operators. These are permitted, but not if the match value(s) contain wildcards or position ranges. This is a warning only. The operator is treated as equal or not equal.
System Action:
The compile continues.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The indicated criteria is not supported under the current operating environment.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The indicated criteria is not supported in the indicated screening table section. For example, MCSFLAG is not applicable to MVS commands.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The Screening Table criteria statement contains an unlicensed criteria function call (COMPARE(...)) element. System must be licensed for AOM/Extension-2 to be allowed to use the COMPARE criteria function.
System Action:
The compilation continues, for error checking purposes only.
User Action:
Check with your product support representative.
Reason:
The indicated string contains an invalid AOM screening variable, or the variable is not correctly formatted, for example a bad substring specification.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
While processing a screening table variable, the encoding of it into internal form caused the string to exceed the limits imposed. These are 128 in MVS, and 240 in VM.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and simplify the string.
Reason:
The indicated variable is not supported in the current operating system environment. For example, JOBNAME is not valid in VM.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The indicated variable is not supported in the indicated screening table section. For example, JOBID is not applicable to MVS commands.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The variable type of the indicated variable and one or more subscripting attributes are mutually exlusive. For example the following statement is invalid : SET LVAR(1) '&RETCODE(1,16,SLBLANK,UCASE)'
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The field name specified in the FIELD clause of the LOOKUP statement is not a valid field that may be used.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid field name.
Reason:
The indicated LOOKUP statement keyword was found twice.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Remove the duplicate clause. Check that a comma separating 2 lookup requests was not accidently omitted.
Reason:
The syntax of a LOOKUP clause expected a closing parenthesis. Instead, the indicated token was found.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Insert the missing parenthesis.
Reason:
The table name specified in the LOOKUP statement TABLE clause did not meet the syntax rules of a VARTABLE name. It must be 1 to 12 characters with the first alpha or national, others alphanumeric or national.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid table name. The VARTABLE need not actually exist at compile time.
Reason:
The MATCH clause of the LOOKUP statement requires one of the keywords EQUAL or IGEN. Neither was found.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax to use EQUAL or IGEN.
Reason:
The RESULT clause of the LOOKUP statement requires a number from 1 to 8.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid result number.
Reason:
The field name specified in the DATA clause of the LOOKUP statement is not a valid field that may be used.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid field name.
Reason:
The indicated attribute name specified in the ASSIGN clause of the LOOKUP statement is not a valid attribute.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid attribute name.
Reason:
The indicated attribute name specified in the ASSIGN clause of the LOOKUP statement is duplicated or mutually exclusive with a previous attribute name.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Remove the attribute name that is in error.
Reason:
The subscript for a UFLAG(n) assign attribute is invalid. It must be a number from 1 to 8, in parenthesis eg (5).
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the subscript.
Reason:
The FIELD clause is required for a LOOKUP statement. Check for a possible missing statement continuation.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax of the LOOKUP statement.
Reason:
The TABLE clause is required for a LOOKUP statement. Check for a possible missing statement continuation.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid field name.
Reason:
The LOOKUP statement had no action clauses. Thus, it would not do anything. Check that a statement continuation was not omitted.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Add the necessary action clauses to the LOOKUP statement.
Reason:
If the DATA clause of a LOOKUP statement is specified, the ADD clause is also required.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Add the ADD clause.
Reason:
The MATCH=IGEN and ADD operands of the LOOKUP statement may not both be specified.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Remove one of the mutually exclusive clauses. Entries may only be dynamically added with MATCH=EQUAL.
Reason:
The FIELD or DATA clauses of the LOOKUP statement require a valid field name. The indicated value is not a valid field name.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid field name.
Reason:
The field name specified in the FIELD clause of the LOOKUP statement is one that requires a subscript. No opening parenthesis for the subscript was found.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Add the required subscript to the field.
Reason:
The subscript value specified is not valid for the indicated field. It must be numeric, from 1 to the number allowed by the specified field.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the subscript value.
Reason:
There was no closing parenthesis after the subscript value for a field.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the subscript syntax.
Reason:
The substring start position for the field was beyond the field length.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the substring syntax.
Reason:
The substring end position for this field is not valid.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the substring syntax.
Reason:
A field expression that started with an opening parenthesis did not have a closing parenthesis when expected.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Correct the syntax of the field expression.
Reason:
Substring notation is not permitted for the indicated field.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Remove the substring notation.
Reason:
The field named is not supported in the indicated operating system environment.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid, supported field name.
Reason:
The data field named is not supported in the indicated operating environment.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid, supported data field name.
Reason:
The indicated ASSIGN attribute is invalid in this operating environment.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid supported attribute name.
Reason:
The LOOKUP statement keyword indicated is invalid in this operating environment.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Remove the offending clause.
Reason:
The field name specified in the FIELD clause of the LOOKUP statement is not a valid field for the current screening table section (MESSAGE or COMMAND).
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid, supported field name.
Reason:
The DATA field name specified is not supported in the current screening tables section (MESSAGES or COMMANDS).
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid, supported DATA field name.
Reason:
The attribute listed cannot be assigned in this screening table section.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Use a valid, supported attribute name only.
Reason:
The indicated LOOKUP statement keyword cannot be used in the current screening table section.
System Action:
The screening table compile will continue for syntax checking only. No table will be loaded.
User Action:
Remove the clause in error.
Reason:
The AOM screening table compiler encountered an unexpected end-of- statement or end- of-file while processing a selection criteria.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
A left parenthesis was expected, but one was not encountered. The indicated token was found.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
A valid COMPARE operator was expected, but was not encountered. The indicated token was found.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The operands separation at the COMPARE criteria function call is incorrect. Valid separation character can be either blank or comma.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
A right parenthesis was expected, but one was not encountered. The indicated token was found.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
Mutually Exclusive operand types were specified on the COMPARE criteria. Comparison is only allowed between same type of operands, eg.: numeric and string type comparison is invalid.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler expected a valid keyword or string specification but found value .
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a keyword kwrd that, while valid for the current statement, is not supported in this environment.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler encountered a kwrd keyword that, while supported by the current statement, is not supported in the current screening table section.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The AOM screening table compiler expected a valid subscript in the COMPARE criteria function call, but no subscript was supplied, or had an invalid format.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
A comma separation character was expected, but was not encountered. The indicated token was found.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
One of the SUBSTR parameters (start or length) used in the COMPARE criteria is either invalid or not specified.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The START or LENGTH value of the SUBSTR specification used in the COMPARE criteria function call statement is greater than the length of the SUBSTR keyword value. The start/length specification is limited to the maximum length of the SUBSTR keyword value.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
SUBSTR specification is not allowed for the xxxxxxxx parameter. For example if SUBSTR is requested for a single literal.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
String starting with xxxxxxxx in the COMPARE criteria is invalid, ie.: not a valid keyword or literal specification.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
The value length of the operand xxxxxxxx in the COMPARE criteria function call statement is zero. For example null string cannot be used for comparison.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
A valid wildcard definition was expected, but one was not encountered. The indicated token was found.
System Action:
The compile continues, for error checking purposes only.
User Action:
Use the error information in the message to find and correct the error.
Reason:
During initialization, the AOM initialization code determined that the base system is back-level; therefore, this version of AOM will not run.
System Action:
AOM is not available. System initialization continues.
User Action:
Check with Technical Support.
Reason:
During initialization, the AOM initialization code determined that the operating system cannot support AOM; therefore, this version of AOM will not run.
System Action:
AOM is not available. System initialization continues.
User Action:
Check with Technical Support.
Reason:
During initialization, the AOM initialization code determined that the operating system only supports a subset of AOM facilities; therefore, only part of the AOM facility is available.
System Action:
Part of AOM is available. System initialization continues.
User Action:
Check that this is the expected result.
Reason:
An AOM SYSPARM command was entered but was not processed for the reason given.
System Action:
The command is not processed.
User Action:
Use the explanation to correct the SYSPARM operand in error.
Reason:
A SYSPARMS AOMPROC=FLUSH command was entered, but there was no current AOMPROC. The command is ignored.
System Action:
None. The command is ignored.
User Action:
None.
Reason:
A SYSPARMS AOMPROC=procname command was entered, but an AOMPROC was already executing. The command is ignored.
System Action:
None. The command is ignored.
User Action:
Use the SYSPARMS AOMPROC=FLUSH command to terminate the currently executing AOMPROC, if required.
Reason:
The AOMSSID parameter cannot be altered, as it has already been activated. AOM stores MVS cross memory information in control blocks associated with the SSID, and thus the SSID must stay associated with the particular product region.
System Action:
None. The command is ignored.
User Action:
Do not attempt to alter AOMSSID until the product region is restarted.
Reason:
A SYSPARMS CONSOLES=FREE or CONSOLES=0 command was entered, but there were no consoles acquired.
System Action:
None. The command is ignored.
User Action:
None.
Reason:
A SYSPARMS CONSOLES=FREE command was entered, but errors occurred whilst freeing the consoles. Consult the log for more information about the error(s).
System Action:
The AOM console table is marked as unusable.
User Action:
Retry the command. If errors persist, contact your product support representative.
Reason:
A SYSPARMS CONSOLES=FREE command was entered, but AOM is started. Consoles cannot be freed whilst AOM is active.
System Action:
None. The command is ignored.
User Action:
Determine whether consoles are to be freed, and, if so, issue the AOM STOP command before re-entering this command.
Reason:
A SYSPARMS CONSOLES=n command was entered, but AOM was only able to acquire the shown number of JES consoles from MVS.
System Action:
None. The console table will only contain the shown number of consoles.
User Action:
Check to see if another SOLVE has acquired too many consoles. The MVS command, 'D C,L' may be of assistance.
Reason:
A SYSPARMS CONSOLES=n command was entered, but no consoles could be acquired. The type of consoles requested (as per the SYSPARMS AOMCTYPE setting) and operating system is displayed.
System Action:
AOM will not start until a SYSPARMS CONSOLES=FREE command is entered, or a successful SYSPARMS CONSOLES=n command is processed.
User Action:
Check whether there should be any free consoles of the type requested. If none are available, you may need to alter parameters in SYS1.PARMLIB to make more consoles available.
Reason:
A SYSPARMS CONSOLES=n command was entered, but consoles had already been acquired.
System Action:
None. The command is ignored.
User Action:
None.
Reason:
A SYSPARMS CONSOLES=n command was entered, and n was less than 1 or greater than 99.
System Action:
None. The command is ignored.
User Action:
Correct and re-enter the command.
Reason:
A SYSPARMS CONSOLES=n command was entered. Either the SOLVE region is not APF authorized or the SCS module (IEAVG700) Is not available (MVS only).
System Action:
None. The command is ignored.
User Action:
Ensure that the SOLVE load library is APF authorized.
For MVS (XA, ESA), investigate whether module IEAVG700 is in the system libraries.
Reason:
A SYSPARMS CONSOLES=n command was entered, but AOM is currently active. Consoles must be acquired when AOM is stopped.
System Action:
None. The command is ignored.
User Action:
Probably none. If consoles are needed, stop AOM, re-issue the command, and then restart AOM.
Reason:
This message acknowledges the successful processing of a SYSPARMS CONSOLES=n command.
System Action:
None.
User Action:
None.
Reason:
This message acknowledges the successful processing of a SYSPARMS CONSOLES=FREE command.
System Action:
None.
User Action:
None.
Reason:
This message is produced if processing of a SYSPARMS CONSOLES command is terminated due to a storage shortage.
System Action:
SYSPARMS CONSOLES processing is terminated.
User Action:
Investigate the reason for the storage shortage and correct it.
Reason:
The SYSPARMS processor was unable to load a module.
System Action:
Processing of the SYSPARMS command is terminated.
User Action:
Dependent on the SYSPARMS command being issued.
Reason:
The CPF (command prefix facility) DEFINE request for prefix P1 failed; the reason is P2 and is one of the following errors:
ALREADY DEFINED
IS A SUBSET OF EXISTING PREFIX
IS A SUPERSET OF EXISTING PREFIX
COULD NOT BE DEFINED (RC=xx, REASON=xx)
The RC/REASON values are documented in the IBM manual, MVS Programming: Authorized Assembler Services Reference.
System Action:
Processing of the SYSPARMS command terminates. The parameter group $RM OPSYSIDS action also terminates.
User Action:
Check the AOM SSI Command String Prefix specification. Issue an MVS D OPDATA command to display the command prefixes currently defined.
Reason:
A SYSPARMS CONSOLES=FREE command was entered. Processing has commenced.
System Action:
Console release processing continues asynchronously.
User Action:
Wait for the processing to complete and check the results.
Reason:
A SYSPARMS CONSOLES=n command was entered. Processing has commenced.
System Action:
Console acquisition processing continues asynchronously.
User Action:
Wait for the processing to complete and then check the results.
Reason:
A SHOW AOMxxx command was entered, but an error has occurred. The description describes the error.
System Action:
None. The command is ignored.
User Action:
Correct the error.
Reason:
The SHOW AOMSTAT=ALL command is only accepted if the AOM SYSPARM AOMALLST, was set to YES before AOM was started. If it is not, AOM does not collect the statistics necessary for this display.
System Action:
None. The command is ignored.
User Action:
Use SH AOMSTAT, or stop AOM, alter AOMALLST to YES, and re-start AOM.
Reason:
This message is displayed if a SHOW AOMABEND command is entered, but AOM has not ABENDed in the SSI or SRB code. Thus there is no ABEND information to display.
System Action:
None. The command is ignored.
User Action:
None.
Reason:
This message is the first message displayed in response to a SHOW AOMDOMQ command. It shows the number of entries on the AOM DOM correlation queue.
System Action:
None.
User Action:
None.
Reason:
This message is a header message for the list of entries on the AOM DOM correlation queue. It gives the column headings for the N85513 messages that follow. The headings are:
DMN - The SOLVE domain that originated the message.
SYSDOMID - THe system- assigned DOMID.
ASID - The MVS ASID that originated the message.
JSTCB - THe MVS JSTCB that originated the message.
SOLVDOMID - The SOLVE assigned DOMID in this system.
TIME-ADD - The time the entry was added to the queue.
MSGID - The message id of the message.
System Action:
None.
User Action:
None.
Reason:
This message is a header message for the list of entries on the AOM DOM correlation queue. It gives the column headings for the N85514 messages that follow. The headings are:
X-REASON - extended reasons that this entry exists:
TO-LINK - msg is being tracked across an ISR link
NOTIFY - msg is being DOM-NOTIFY'd
SUB-AOMP - msg is being tracked for a secondary AOMPROC.
NCLID/LINK - The target NCLID or ISR link.
System Action:
None.
User Action:
None.
Reason:
This message is a data line for the SHOW AOMDOMQ command. Refer to message N85511 for the meanings of the columns.
System Action:
None.
User Action:
None.
Reason:
This message is an optional additional data message for the SHOW AOMDOMQ command. Refer to message N85512 for the column meanings.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the STATUS command to indicate the status of AOM. status can be:
ACTIVE (RUNNING) - AOM is active and running.
ACTIVE (PAUSED) - AOM is active, but in pause status.
INACTIVE - AOM has not been started.
If active or paused, the date and time that AOM was last started is also shown.
The message will say AOM HAS ABENDED if the AOM SSI code or SRB code has had an ABEND detected. THe SHOW AOMABEND command will provide more information.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the STATUS command to indicate the names of AOMPROC, CMDPROC, and the screening table. IN AOM/VM, no CMDPROC is present, and the TABLE is shown as: filename filetype filemode.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the STATUS command. It gives information about the AOMGDB (AOM Global Data Base) usage:
nnnnnnnnnn The number of entries (records) in the AOM Global Data Base.
size The storage usage in Kbytes of the AOM Global Data Base.
typ The storage type allocated to PVT (private) or CSA area.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command if an attempt to alter AOM profile attributes is made, and the user is not authorized for AOM message receipt.
System Action:
None. The option is ignored.
User Action:
Contact your system administrator.
Reason:
This message is displayed by the PROFILE command if an attempt to alter AOM message routing codes is made, and the supplied routing codes include ones that the user is not authorized for.
System Action:
None. The option is ignored.
User Action:
Contact your system administrator to check if you should have authority for the required routing codes.
Reason:
This message is displayed by the PROFILE command if an attempt to alter AOM message levels is made, and the supplied message levels include ones that the user is not authorized for.
System Action:
None. The option is ignored.
User Action:
Contact your system administrator to see if you should have authority for the required message levels.
Reason:
The AOM feature has been initialized to enable the use of the SYSCMD facility.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display, if the user has SYSCMD authority. The operating system and command authority levels are shown.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates whether AOM messages may be delivered to this user. The current setting of PROFILE AOMMSG= is reflected.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current message routing codes that will be displayed. The current setting of PROFILE ROUTCDE= is reflected. Note that, if NONE is displayed, no AOM messages will be displayed.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current message level codes that will be displayed. The current setting of PROFILE AOMMSGLV= is reflected. Values are:
ALL All the following message levels.
WTOR WTOR messages.
I Immediate action messages.
CE Critical eventual action messages.
E Eventual action messages.
IN Informational messages.
BC Broadcast messages.
NONE No messages. Note that if NONE is displayed, no AOM messages can be received.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current setting of the PROFILE AOMPRFTM= option, which governs the optional display of the message time for AOM messages.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current setting of the PROFILE AOMPRFJN= option, which governs the optional display of the originating JOBNAME for AOM messages.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current setting of the PROFILE AOMPRFJI= option, which governs the optional display of the originating or relevant JES JOBID for AOM messages.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current setting of the PROFILE AOMFMTRC= option, which governs the optional display of the message routing codes for AOM messages.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current setting of the PROFILE AOMPRFUI= option, which governs the optional display of the originating VM USERID for AOM messages.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current setting of the PROFILE AOMPRFUN= option, which governs the optional display of the originating or relevant VM node for AOM messages.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current setting of the PROFILE AOMPRFMN= option, which governs the optional prefixing of multi-line WTO minor lines.
System Action:
None.
User Action:
None.
Reason:
This message is displayed by the PROFILE command as part of a user profile display. It indicates the current setting of the PROFILE AOMPRFSN= option, which governs the optional display of the sourcing system name for AOM messages.
System Action:
None
User Action:
None
Reason:
This message indicates that the entered AOM command could not be processed, as a previous AOM command is still being processed. For example, entering a second AOM START when processing of another command is still in progress.
System Action:
None. The command is ignored.
User Action:
None.
Reason:
This message indicates that the entered AOM command could not be processed, as AOM was not in the status indicated in the message. For example, AOM PAUSE requires AOM to be ACTIVE.
System Action:
None. The command is ignored.
User Action:
Verify AOM status and use other AOM commands if necessary.
Reason:
This message indicates that the entered AOM command could not be processed, as you do not have sufficient authority for the entered options.
System Action:
None. The command is ignored.
User Action:
Contact your system administrator.
Reason:
This message indicates that the entered AOM command has been accepted, and processing has begun.
System Action:
The command is being processed.
User Action:
Await the outcome of command processing.
Reason:
The entered AOM command has been rejected because the region is in final shutdown processing.
System Action:
The command is ignored.
User Action:
None.
Reason:
This message indicates that AOM has successfully started, following entry of an AOM START command. If PAUSE was specified on the command, the literal (PAUSED) will indicate this.
System Action:
None.
User Action:
None.
Reason:
This message indicates that AOM could not be started. The reason and subreason codes indicate the problem. Message N85724 will follow, providing an explanation of the reason. Refer to that message for the explanations.
System Action:
None. AOM has not started.
User Action:
Correct the error, after referring the message N85724.
Reason:
This message follows message N85723, and provides an explanation of the reason and subreason why AOM cannot start.
The descriptions are as follows (note that some descriptions refer to a return code (RC); this return code is generally the subreason from the N85723 message):
001 REGION NOT RUNNING AUTHORIZED This region is not running from an authorized library, or is not link-edited as authorized.
003 SSI (SSAB) SETUP FAILED. RC: reason SSAB is the NetMaster SubSystem Anchor Block. There is one SSAB for each SSI acquired by NetMaster, pointed to by the operating system SSCT (SubSystem Communications vector Table) for the SSI. When AOM attempted to perform SSI setup, an error occurred. The following errors are possible:
NOT RUNNING AUTHORIZED. The product is not running authorized. (See reason 001 above).
ENQ ON AOMSSID FAILED. AOM is unable to use the SSID because an ENQ failed. It may be in use by another AOM.
NO SSCT FOUND (SSID BAD). The supplied AOMSSID cannot be found. Possibly, it is misspelt, or not in the subsystem definition member (for example, IEFSSNnn on MVS systems).
OTHER USER OF SSID. The SSID verification process determined that another user (not AOM) was using this SSID. Thus, it cannot be used.
SSAB LEVEL MISMATCH. An earlier level of AOM last used this SSID and it cannot be used.
SSVT EYECATCHER MISMATCH. Verification of the SSVT failed. There may be another user of the SSID.
SQA GETMAIN FAILURE. AOM is unable to obtain required SQA storage for control blocks.
CS OF SSAB PTR FAILED. AOM is unable to obtain use of a valid SSID. Another program obtained it in the meantime. (CS refers to the non-interruptible Compare and Swap instruction).
004 XMS REQUESTED BUT NO XMS SUPPORT. SYSPARMS AOMXMS=YES was specified, but AOM cannot use cross- memory services. Possibly, this operating system does not support
005 GETMAIN FOR AOM/VM CTL BLKS FAILED, RC: rc. A GETMAIN for AOM/VM control blocks failed with the indicated return code.
006 IUCVINI FOR PROP PATH FAILED, RC: rc. The IUCVINI macro instruction failed with the indicated return code.
007 IUCVINI FOR *MSG PATH FAILED, RC: rc. The IUCVINI macro instruction failed with the indicated return code.
010 CROSS-MEMORY SETUP FAILED: reason. SYSPARMS AOMXMS=YES was specified, but AOM was unable to establish the cross-memory environment. The following reasons are possible:
REGION RUNNING SWAPPABLE. SYSPARMS NONSWAP=NO was entered. Because MVS requires that cross-memory users are nonswappable, the XMS environment cannot be built.
NO XMS SUPPORT. This operating system does not support cross- memory services.
STORAGE SHORT (IHAETD). AOM cannot obtain storage to build control blocks.
XMS MODULE LOAD FAILED. AOM is unable to load cross-memory code.
SYSTEM LXRES FAILURE. AOM has a non-zero return code from an LXRES macro instruction. This includes the case where an 053- 111/112 abend occurs, which indicates that no system LXs are available.
SQA GETMAIN FAILED. AOM is unable to obtain storage for cross-memory control blocks.
011 GETMAIN FOR PVT Q FAILED, RC: rrr. AOM is unable to obtain storage for the private queue. The specified size (AOMPQSZ) may be too large or the region is too small.
012 GETMAIN FOR GLOB FIXED STG FAILED, RC: rrr. AOM is unable to obtain pagefixed storage in the CSA. This may be due to a small CSA allocation. An IPL may be required. In MVS/XA, this storage is below the line.
013 GETMAIN FOR GLOB PGBLE STG FAILED, RC: rrr. AOM is unable to obtain pageable CSA storage for the global be required. In MVS/XA, this storage is above the line.
014 GETMAIN FOR GLOB ST STG FAILED, RC: rrr. AOM is unable to obtain pageable CSA storage for the screening tables. This may be due to a small CSA allocation. An IPL may be required. In MVS/XA, this storage is above the line.
015 GETMAIN FOR GLOB WORK AREA FAILED, RC: rrr. AOM is unable to obtain pageable CSA storage for the subsystem code work areas. This may be due to a small CSA allocation. An IPL may be required. In MVS/XA, this storage is below the line.
016 SWAP IN OF SSVT FAILED. When AOM attempted to activate the subsystem interface, the SSCVT had been changed. Another product is using this SSID.
017 FRONT-ENDING OF JES FAILED. When AOM attempted to alter the JES SSVT to allow front-ending of JES SSI code, SSI serialization failed. This should not occur on MVS/SP or MVS/XA.
018 NZ RC FROM IEAVG700 BROADCAST FUNC: rrr When AOM linked to IEAVG700 to enable WTO broadcast, a non-zero return code was set. Contact your product support representative.
019 SCREENING TABLE COMPILE FAILED. AOM was started with a screening table requested. The compilation failed. Other messages will describe the error. Correct the table and retry.
020 AOM SYSPARM IN ERROR: name. The previously entered value for the named AOM SYSPARM is invalid. The relevant SYSPARM must be reset to a valid value.
Note: A display of the SYSPARM value shows the last good value, not the in-error value. See the activity log for any error information.
021 UNABLE TO MIRROR SCOPE=AOM VARTABLES. AOM cannot successfully obtain storage to mirror all the active SCOPE=AOM VARTABLEs.
030 CONS ALLOC FOR SCREENING TABLE FAILED. AOM cannot allocate a console to use for the screening table. Use the SHOW CONSOLES command to determine the current state of consoles allocated to AOM. There may be no consoles available.
031 IUCVINI FOR VMOPERATOR PATH FAILED, RC: rc The IUCVINI macro instruction that sets up the AOM/VM to VMOPERATOR VM system's GCS Macro Reference for a description of the return code.
032 IUCVINI FOR VMOPERATOR PATH FAILED, RC: rc The IUCVINI macro instruction that sets up the AOM/VM to VMOPERATOR communications to handle SYSCMD functions failed. See your VM system's GCS Macro Reference for a description of the return code.
033 IUCVINI FOR VMOPERATOR PATH FAILED, RC: rc The IUCVINI macro instruction that sets up the AOM/VM to VMOPERATOR communications to handle SECUSER functions failed. See your VM system's GCS Macro Reference for a description of the return code.
034 IUCVINI FOR VMOPERATOR PATH FAILED, RC: rc The IUCVINI macro instruction that sets up the AOM/VM to VMOPERATOR communications to handle SYSLOG functions failed. See your VM system's GCS Macro Reference for a description of the return code.
035 IUCVINI FOR VMOPERATOR PATH FAILED, RC: rc The IUCVINI macro instruction that sets up the AOM/VM to VMOPERATOR communications to handle USERID functions failed. See your VM
System Action:
User Action:
Reason:
An AOM PAUSE command has been entered, but AOM was already in PAUSE status.
System Action:
None. The command is ignored.
User Action:
None.
Reason:
An AOM PAUSE command was entered and processed successfully.
System Action:
None.
User Action:
None.
Reason:
An AOM GO command has been entered, but AOM was not PAUSED.
System Action:
None. The command is ignored.
User Action:
None.
Reason:
An AOM GO command was entered and processed successfully.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the AOM command was not accepted as subset AOM does not support it.
System Action:
The command is ignored.
User Action:
None.
Reason:
The system was shutting down, and an AOM STOP command was already being processed. This is a warning message.
System Action:
None. The second shutdown will continue.
User Action:
None.
Reason:
This NCL procedure has attempted to use an AOM NCL verb, for example,
AOMREAD. These verbs are only valid in an AOMPROC.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure. For secondary AOMPROCs, ensure that they have issued an AOMINIT statement.
Reason:
The NCL procedure has issued an &AOMDEL statement, when no message was currently active.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &AOMCONT statement, when no message was currently active.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &AOMREPL statement, when no message was currently active.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &AOMREPL statement, when the current message received by the last executed &AOMREAD was a DOM message. DOM messages cannot be replaced or deleted.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &AOMCONT or &AOMREPL statement, and the supplied value for the ROUTCDE= parameter is not a valid ROUTCDE list.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &AOMINIT verb. This is only valid if the NCL procedure is in the AOMP environment. It executes there if SUBMITted to AOMP, or EXEC'd, STARTed, or &INTCMD STARTed by AOMPROC.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an 7AOMCONT statement with the NCLID, LINKNAME, or DOMAIN parameters, when a minor line of a multi-line WTO was current. Only the major line (and thus the entire message) may be processed in this way.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &AOMDEL statement with the LINKNAME, or DOMAIN parameters, when a minor line of a multi-line WTO was current. Only the major line (and thus the entire message) may be processed in this way.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &AOMCONT statement, and the supplied value for the RMTCLASS= parameter is not a valid RMTCLASS list.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &AOMGFLAG statement to alter an AOM global flag. The value specified is not ON or OFF.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
No number was supplied on an AOM builtin function that requires one. For example, &AOMGVAR or &AOMMINLN.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has provided an invalid number to an AOM builtin function that requires one.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has provided invalid data after a number for an AOM builtin function. There should be no additional data after the number.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The command being passed to the migration ID exit is either missing or too long.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
Unable to supply a value for AOM built-in function &AOMMIGID because the system is being shutdown.
System Action:
The NCL procedure is terminated.
User Action:
None.
Reason:
Following a LINK START, or ISR ENABLE, AOM has commenced establishment across the indicated ISR link.
System Action:
The ISR conversation attempts to enable.
User Action:
None.
Reason:
AOM has completed the establishment of ISR contact across the indicated link. The remote system domain and AOM version are indicated.
System Action:
ISR message flow can commence.
User Action:
None.
Reason:
AOM has terminated the ISR conversation across the indicated link, possibly due to a LINK TSTOP, line error, or ISR DISABLE command.
System Action:
The ISR conversation is terminated.
User Action:
Determine whether the link needs to be restarted.
Reason:
This message is issued when a SHOW ISR OPTIONS command is issued, and AOM is included in the classes to be displayed. The following parameters are displayed:
type The type of displayed information. This can be LOC - the local settings, RMT - the remote settings (if the link is active), or ACT - the actual settings (if the link is active).
la The setting of the LINKATTR AOM ISR option.
lrt The setting of the LCLROUTE AOM ISR option.
rrt The setting of the RMTROUTE AOM ISR option.
nmc The setting of the NEWMSGCLASS AOM ISR option.
System Action:
None.
User Action:
None.
Reason:
This message is issued when a SHOW ISR OPTIONS command is issued, and AOM is included in the classes to be displayed. The following parameters are displayed:
type The type of displayed information. This can be LOC - the local settings, RMT - the remote settings (if the link is active), or ACT - the actual settings (if the link is active).
imc The setting of the INMSGCLASS AOM ISR option.
omc The setting of the OUTMSGCLASS AOM ISR option.
iml The setting of the INMSGLEVEL AOM ISR option.
omlc The setting of the OUTMSGLEVEL AOM ISR option.
System Action:
None.
User Action:
None.
Reason:
This message is issued when a SHOW ISR OPTIONS command is issued, and AOM is included in the classes to be displayed. The following parameters are displayed:
type The type of displayed information. This can be LOC - the local settings, RMT - the remote settings (if the link is active), or ACT - the actual settings (if the link is active).
irc The setting of the INROUTCDE AOM ISR option. This parameter can be quite long, as there are 128 individual routing codes.
System Action:
None.
User Action:
None.
Reason:
This message is issued when a SHOW ISR OPTIONS command is issued, and AOM is included in the classes to be displayed. The following parameters are displayed:
type The type of displayed information. This can be LOC - the local settings, RMT - the remote settings (if the link is active), or ACT - the actual settings (if the link is active).
orc The setting of the OUTROUTCDE AOM ISR option. This parameter can be quite long, as there are 128 individual routing codes.
System Action:
None.
User Action:
None.
Reason:
This message is issued when an ISR command is issued for AOM and the NEWMSGCLASS value supplied is invalid.
System Action:
The command is not processed.
User Action:
Correct the value and reissue the command.
Reason:
This message is issued when an ISR command is issued for AOM and the MSGCLASS, or INMSGCLASS, or OUTMSGCLASS value supplied is invalid.
System Action:
The command is not processed.
User Action:
Correct the value and reissue the command.
Reason:
This message is issued when an ISR command is issued for AOM and the MSGLEVEL, or INMSGLEVEL, or OUTMSGLEVEL value supplied is invalid.
System Action:
The command is not processed.
User Action:
Correct the value and reissue the command.
Reason:
This message is issued when an ISR command is issued for AOM and the ROUTCDE, or INROUTCDE, or OUTROUTCDE value supplied is invalid.
System Action:
The command is not processed.
User Action:
Correct the value and reissue the command.
Reason:
This message is issued when an &AOMALERT verb has an invalid time value supplied. The time must be in the format hmmss.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
This message is issued when an &AOMALERT verb has an invalid ROUTCDE value supplied.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
This message is issued when an &AOMALERT verb has an invalid DESC value supplied.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
This message is issued when an &AOMALERT verb has an invalid MSGLEVEL value supplied.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
This message is issued when an &AOMALERT verb has an invalid RMTCLASS value supplied.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
This message is issued when an &AOMALERT verb has an invalid MVS JOBID value supplied.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
This message is issued when an &AOMALERT verb has an invalid combination of operating system specific parameters. Two parameters conflict in their implied or forced operating system type.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The &AOMALERT NCL statement contains ROUTE=TABLE specification. This function is not licensed in the current system. ROUTE=TABLE allows NCL procedures to simulate single WTO messages on the AOM Screening Table without using system WTO (Write To Operator) services. The system must be licensed for AOM/Extension-2 to use this function.
System Action:
The NCL procedure is terminated.
User Action:
Check with your product support representative.
Reason:
The pool used for console management has been initialized as part of processing a SYSPARMS CONSOLES=n command.
System Action:
None.
User Action:
None.
Reason:
The pool used for console management has been deleted as part of processing a SYSPARMS CONSOLES=0 or SYSPARMS CONSOLES=FREE command.
System Action:
None.
User Action:
None.
Reason:
The pool used for console management could not be initialized as part of processing a SYSPARMS CONSOLES=n command due to a storage shortage.
System Action:
Processing of the SYSPARMS CONSOLES=n command is terminated.
User Action:
Check the storage size allocated to the SOLVE region.
Reason:
The pool used for console management could not be initialized as part of processing a SYSPARMS CONSOLES=n command. The reason is given in an earlier message in the LOG.
System Action:
Processing of the SYSPARMS CONSOLES=n command is terminated.
User Action:
Check the SOLVE LOG for a message giving further details of the problem.
Reason:
The pool used for console management could not be deleted as part of processing a SYSPARMS CONSOLES=0 or CONSOLES=FREE command. The reason is given in an earlier message in the LOG.
System Action:
Processing of the SYSPARMS CONSOLES=0 or CONSOLES=FREE command is terminated.
User Action:
Check the SOLVE LOG for a message giving further details of the problem.
Reason:
The value belonging to the field 'name' (used for user correlator services in the &AOMGDB PUT/UPDATE stmt) is invalid. The value is either longer than 8 characters or is not an expanded hexadecimal string.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The value belonging to the field 'name' definition (ADJUST or COUNTER on the &AOMGDB ... statement) is invalid. The value must be a non-zero number in the range - 2147483648 to 2147483647.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &AOMGDB statement has null entries eg: VARS=(A,,B). This is not permitted.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &AOMGDB statement has more entries than the system can handle.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &AOMGDB statement has invalid syntax.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &AOMGDB statement is empty.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &AOMGDB statement contains an invalid variable name.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &AOMGDB statement has null entries eg FIELDS=(A,,B). This is not permitted.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &AOMGDB statement has a duplicated entry. This is not permitted.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &AOMGDB statement has more entries than the system can handle.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &AOMGDB statement has invalid syntax.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &AOMGDB statement is empty.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &AOMGDB statement contains invalid or unrecognizable keywords. Only the keywords listed for the current option of &AOMGDB can be used.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &AOMGDB statement contains mutually exclusive keywords. For example COUNTER and ADJUST specifications are mutually exclusive.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An &AOMGDB statement has a missing VARS= or FIELDS= list specification. Both specifications must be present or omitted.
System Action:
The NCL procedure terminates.
User Action:
Correct the NCL procedure.
Reason:
An &AOMGDB statement was encountered where the number of elements in the fields list (FIELDS= keyword) was different to the number of elements in the variables list (VARS= keyword). There must be a 1-1 correspondence between the elements in the field list and the variables list.
System Action:
The NCL procedure terminates.
User Action:
Correct the NCL procedure.
Reason:
The &AOMGDB NCL verb is not licensed in the current system. The system must be licensed for AOM/Extension-2 to be able to use the AOM Global Data Base functions.
System Action:
The NCL procedure is terminated.
User Action:
Check with your product support representative.
Reason:
The SCS module, IEAVG700, returned a non-zero return code. This message is only written to the Log.
System Action:
None. Other messages may be issued (eg: by AOM).
User Action:
None.
Reason:
A SYSCMD command was entered with CON=value, but the entered value was not numeric, or not a valid MVS console id for this environment.
System Action:
The command is ignored.
User Action:
Provide a valid CON= value.
Reason:
A SYSCMD command was entered but no consoles were available to assign to this environment.
System Action:
The command is ignored.
User Action:
Use SHOW CONSOLES to check the status of the console table, and possibly acquire more if too few are provided.
Reason:
A SYSCMD OPT=REL command has been successfully processed.
System Action:
The console assigned to this environment has been released, if one was acquired.
User Action:
None.
Reason:
A SYSCMD OPT=LOCK command has been successfully processed.
System Action:
A console has been assigned to this environment, and locked to it until either the environment terminates, or SYSCMD OPT=REL is entered.
User Action:
None.
Reason:
A SYSCMD with command text has been processed, and the command passed to the operating system for processing.
System Action:
Depends on the command.
User Action:
Await the results of the command.
Reason:
A SYSCMD command was entered but no consoles were available to assign to this environment.
System Action:
The command is ignored.
User Action:
Use SHOW CONSOLES to check the status of the console table, and possibly acquire more if too few are provided.
Reason:
A SYSCMD command was entered with command text too long for the operating system or target environment. The limits are as follows:
System Action:
The command is ignored.
User Action:
Correct the input command.
Reason:
A SYSCMD CON=nn command was entered but the console number was less than 1, or greater than the maximum generated MVS console.
System Action:
The command is ignored.
User Action:
Correct the console number.
Reason:
A SYSCMD command was entered from a SYSOPER environment that is assigned to an MVS console acquired by this SOLVE system. For example, the command `SYSCMD ?SYSCMD command' entered from OCS is not allowed (assuming `?' is the current AOMCMDCH for the system) as a processing loop can result.
System Action:
The command is ignored.
User Action:
None.
Reason:
A SYSCMD command was entered but AOM is not started, or is started, but has been PAUSED.
System Action:
The command is ignored.
User Action:
Determine why AOM is not active.
Reason:
A SYSCMD command was entered but you have no console authority.
System Action:
The command is ignored.
User Action:
Check with your system administrator if you should have console authority.
Reason:
You are not authorized for the target of this SYSCMD command.
In MVS, this could be CON=MASTER.
In VM, this could be DEST=GCS, DEST=PROP, or DEST=VMOP.
System Action:
The command is ignored.
User Action:
Contact your system administrator to check if you should have the appropriate console authority.
Reason:
A SYSCMD CON=MASTER command was entered but another user has recently issued SYSCMD CON=MASTER. The timeout (AOMCTO3) has not yet expired.
System Action:
The command is ignored.
User Action:
Wait, and try again.
Reason:
A SYSCMD command was entered but SOLVE was unable to acquire storage to process the command.
System Action:
The command is ignored.
User Action:
Determine why SOLVE cannot obtain storage.
Reason:
A SYSCMD command was entered but the AOM SSI Interface has ABENDED. No responses can be returned.
System Action:
The command is ignored.
User Action:
AOM should be restarted.
The following steps should be followed:
When the AOM START has completed, the SYSCMD command can be reissued.
Reason:
A SYSCMD command was entered from the GCS console with DEST=GCS specified. As this can lead to a loop involving WTO, IUCV, and the GCS console, this is not permitted.
System Action:
The command is ignored.
User Action:
Do not issue this form of SYSCMD directly from the GCS console. Any commands that could be provided to GCS in this way can be entered directly to GCS.
Reason:
A SYSCMD CON=MASTER command was entered from the MVS master console. Since this can lead to a message delivery loop, it is not allowed. Just issue the MVS command directly.
System Action:
The command is ignored.
User Action:
Do not issue this form of SYSCMD directly from the MVS master console. Any commands that could be provided to MVS in this way can be entered directly to MVS.
Reason:
A SYSCMD DEST=VMOP command was entered, but VMOPERATOR is not active or has not connected to the region.
System Action:
The command is ignored.
User Action:
Wait, and try again.
Reason:
The CON=nn operand of SYSCMD is not allowed when using the indicated console type (AOMCTYPE SYSPARM). This is typically EXTMCS, indicating Extended MCS consoles.
System Action:
The command is ignored.
User Action:
Remove the CON=nn operand from the command and retry the operation.
Reason:
A SYSCMD command has been entered and has been rejected by the system. A previous SYSCMD command with the WAIT= operand specified is still waiting for a console to become available. It is invalid to issue any further commands until the first command completes, with the exception of the SYSCMD OPT=REL command which may be used to cancel the first command before a console becomes available.
System Action:
The command is rejected.
User Action:
The SYSCMD command which is waiting for a console to become available may be cancelled using the SYSCMD OPT=REL command. No further commands are allowed until the first command acquires a console or is cancelled.
Reason:
The entered SYSCMD command requested a migration ID (using the MIGID operand). However, the environment currently has a console assigned, and that console has no migration ID.
This can occur if MIGID=YES, MIGID=DEFAULT (and SYSPARMS AOMCMIGI=YES), or MIGID=EXIT (and the command is analyzed as requiring a migration ID).
System Action:
The command is rejected.
User Action:
Issue a SYSCMD OPT=REL to release the current console (without a migration ID). Then reissue the command.
Reason:
The entered SYSCMD command explicitly requested no migration ID (using the MIGID operand). However, the environment currently has a console assigned, and that console has a migration ID.
This can occur if MIGID=NO, MIGID=DEFAULT (and SYSPARMS AOMCMIGI=NO), or MIGID=EXIT (and the command is analyzed as not requiring a migration ID).
While this is not normally a problem, this situation probably indicates a programming logic error.
System Action:
The command is rejected.
User Action:
Issue a SYSCMD OPT=REL to release the current console (with a migration ID). Then reissue the command.
Alternatively, simply remove the MIGID operand from the command.
Reason:
The current console type (SYSPARMS AOMCTYPE) does not support the use of the SYSCMD CON=MASTER command.
System Action:
The command is ignored.
User Action:
Check the documentation for the correct approach to issuing master commands with this console type.
Reason:
A SYSCMD command was entered that contained parameters not supported by this operating system environment.
System Action:
The command is ignored.
User Action:
Correct the SYSCMD command and retry the operation.
Reason:
The SYSCMD command is not supported if SUBSET AOM is active.
System Action:
The command is ignored.
User Action:
Do not use SYSCMD unless full-function AOM is active.
Reason:
While processing an AOM structured field from an external security exit, an error was found in the nominated field.
System Action:
The default field value is taken.
User Action:
Correct the field value in the external security definition.
Reason:
This message appears as a response to a SHOW CONSOLES command; it indicates that console pool information follows.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it indicates that AOM SYSPARM settings relevant to the console pool follow.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it provides headings for the following N86E12 message. The headings name various AOM SYSPARMS.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it displays various AOM SYSPARM settings. The preceding N86E11 message provides column headings.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it provides headings for the following N86E14 message. The headings name various AOM SYSPARMS.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it displays various AOM SYSPARM settings. The preceding N86E13 message provides column headings.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it provides headings for the following N86E18 message. The only AOM SYSPARM named is CONIDS.
This message is issued only in a Fujitsu MSP environment.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it displays various AOM SYSPARM settings. The preceding N86E14 message provides the column heading. The display is the console id list.
This message is issued only in a Fujitsu MSP environment.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it indicates that statistics related to the console pool follow.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command, it provides headings for the following N86E22 message. The headings name various statistics related to console pool management.
The column headings are:
The number of logical console acquire requests (for example, SYSCMD OPT=LOCK)
The number of physical console acquire requests (that is, the number of times a console was requested from the operating system)
The percentage of physical to logical acquire requests. (A lower percentage indicates that more requests were satisfied from the console pool, without requiring a call to the operating system.)
The average time (in seconds) that a physical acquire request took.
Note: This is the actual time taken for the operating system calls. It does not include any queueing time if the request(s) are single-threaded.
The number of logical console release requests (for example, SYSCMD OPT=REL)
The number of physical console release requests (that is, the number of times a console was released back to the operating system)
The percentage of physical to logical release requests. (A lower percentage indicates that more requests were satisfied by simply returning the console to the pool, without requiring a call to the operating system.)
The average time (in seconds) that a physical release request took Note: This is the actual time taken for the operating system calls. It does not include any queueing time if the request(s) are single-threaded.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it provides various statistics. Refer to message N86E21 for column headings and descriptions.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it provides headings for the following N86E24 message. The headings name various statistics related to console pool management.
The column headings are:
The number of logical console acquire requests that requested a migration id.
The percentage of total logical console acquire requests that requested a migration id.
The number of physical console acquire requests that requested a migration id.
The percentage of total physical console acquire requests that requested a migration id.
The number of logical console acquire requests that failed due to no consoles being available.
The percentage of total logical console acquire requests that failed due to no consoles being available.
The number of physical console acquire requests that failed to obtain a console from the operating system.
The percentage of total physical console acquire requests that failed to obtain a console from the operating system.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it provides various statistics. Refer to message N86E23 for column headings and descriptions.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it provides headings for the following N86E31 message. The following N86E31 messages describe the currently allocated consoles.
The column headings are:
The SOLVE console number (from 1 to 255)
The MVS console (1-byte) id. If no id is assigned, for example when using Extended MCS consoles, this field has a dash (-).
The MVS console name. If no name is assigned, this field has a dash (-).
If the MASTER console is currently assigned to a user (SYSCMD CON=MASTER), the name shows *MASTER*, to indicate that this message displays the current owner of the master console.
The status of this console:
IN-ALLOC - A console is being requested from the operating system.
IN-FREE - A console is being freed to the operating system.
IN-USE - This console is assigned to a user.
TIMEOUT - This console is in a timeout, after being released by a user.
POOL - This console is in the free-console pool, available for reassignment to another user.
The LOCK status of this console:
- - Not locked
AOM - Locked by AOM (console 1)
SYSCMD - Locked by SYSCMD OPT=LOCK
WTOR - Locked because a WTOR was received as a command response
The authority level of this console:
MASTER - The console has master authority.
PS-MAST - the console has pseudo-master authority.
INFO - The console has informational authority.
S,I,C - (Any combination) The console has SYS (S), I/O (I), and/or CONS (C) authorities.
The currently assigned user ID, if there is one; otherwise,a dash.
The currently assigned user environment, if there is one; otherwise, a dash. An OCS window is indicated as PRIM An NCL &INTCMD environment is indicated by the NCLID.
The window (1 or 2) for the currently assigned user (a dash if none).
If the console is not locked, or is in the timeout state, the number of seconds remaining before timeout completes.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command; it provides information on a console. Refer to message N86E30 for column headings and descriptions.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW CONSOLES command, when no consoles have been acquired.
System Action:
None.
User Action:
Refer to the CONSOLES system parameter for information on acquiring consoles.
Reason:
The command being passed to the migration ID exit is either null or too long.
System Action:
The OML procedure is terminated.
User Action:
Correct the procedure.
Reason:
A migration ID exit trace was requested. This message is produced after the migration exit has been called. P1 is the result from the exit; P2 and P3 are the command byte and command passed to the exit.
System Action:
None.
User Action:
None.
Reason:
The AOM migration ID exit specified in the AOMCMIGX setting ABENDED. nnnnnnnn is the migration exit name and ccc is the ABEND code.
System Action:
The exit is disabled.
User Action:
See the SOLVE log for further messages that may indicate the cause of the problem, particularly messages N86M91 and N86M92.
Reason:
The AOM migration ID exit specified in the AOMCMIGX setting ABENDED.
pppppppp - pppppppp is the PSW
ll is the instruction length code extracted from the PSW
cc is the interrupt code extracted from the PSW
iiiiiiii is the failing instruction address extracted from the PSW
System Action:
The exit is disabled.
User Action:
See the SOLVE log for further messages that may indicate the cause of the problem, particularly messages N86M90 and N86M92.
Reason:
The AOM migration ID exit specified in the AOMCMIGX setting ABENDED. This message documents the register values of Rww-Rzz in the exit at the time of the ABEND.
System Action:
The exit is disabled.
User Action:
See the SOLVE log for further messages that may indicate the cause of the problem, particularly messages N86M90 and N86M91.
Reason:
JES console pool initialization was requested as part of a SYSPARMS CONSOLES=nn command and failed. rrrrrr is one of the following reasons:
NO STORAGE FOR JES CONSOLE MANAGEMENT CONTROL BLOCKS
ATTACH OF: nnnnnnnn FAILED
Is the name of the subtask being attached.
SUBTASK: nnnnnnnn FAILED
Is the name of the subtask being attached.
System Action:
Processing of the SYSPARMS CONSOLES=nn command is terminated.
User Action:
Dependent on the reason given.
Reason:
An SCS function ffffffff was issued for user uuuuuuuu and failed with return code rr.
System Action:
The console request is terminated.
User Action:
See the dump of the SCS parameter list that follows to determine the cause of the problem.
Reason:
The subtask that services JES console management requests has terminated. The ECB and STQE associated with the attach of the subtask are displayed.
ATTACH OF: nnnnnnnn FAILED
Is the name of the subtask being attached.
SUBTASK: nnnnnnnn FAILED
Is the name of the subtask being attached.
System Action:
SOLVE ABENDS with an ABEND code 99.
User Action:
See the system log for other messages relating to the problem.
Reason:
EXTMCS console pool initialization was requested as part of a SYSPARMS CONSOLES=nn command and failed. rrrrrr is one of the following reasons:
NO STORAGE FOR EXTMCS CONSOLE MANAGEMENT CONTROL BLOCKS
ATTACH OF: nnnnnnnn FAILED
Is the name of the subtask being attached.
SUBTASK: nnnnnnnn FAILED
Is the name of the subtask being attached.
System Action:
Processing of the SYSPARMS CONSOLES=nn command is terminated.
User Action:
Dependent on the reason given.
Reason:
An EXTMCS function ffffffff issued for console name nnnnnnnn failed with return code rr and reason code ss.
Note: if the return code is 4 and the reason is 00000000, this is a soft error, which is ignored (the console is already in use possibly by another region that is sharing the same prefix). Other console names (using different suffix values) are tried.
System Action:
The console request is terminated. (Except in the case of return code 4 and reason code 00000000, where other console names are tried).
User Action:
See the dump of the MCSOPER parameter list and associated areas that follow to determine the cause of the problem.
Reason:
The subtask that services EXTMCS console management requests has terminated. The ECB and STQE associated with the attach of the subtask are displayed.
ATTACH OF: nnnnnnnn FAILED
Is the name of the subtask being attached.
SUBTASK: nnnnnnnn FAILED
Is the name of the subtask being attached.
System Action:
SOLVE ABENDS with an ABEND code 99.
User Action:
See the system log for other messages relating to the problem.
Reason:
An NDB START UNLOCK command has been successfully processed. The database has been unlocked.
System Action:
The indicated database is restarted.
User Action:
None.
Reason:
An NDB START UNLOCK command was not successfully processed. Possible reasons are: REQUESTS PENDING - there are still requests queued to the locked database.
System Action:
The database remains locked.
User Action:
Re-enter the command when all queued requests have been processed. The SHOW NDB=dbname command will indicate how many requests are still pending.
Reason:
An NDB START command for the indicated database has been received, and reason indicates the result:
The database has been successfully started.
The database was already started.
The database was stopping, but there were still active users. The pending stop has been reset. The database is now regarded as started.
The database was already active, due to an &NDBOPEN. It is now flagged as started, so that it will stay active when there are no signed on users.
System Action:
As indicated by the message.
User Action:
None.
Reason:
An NDB START command was entered for the indicated database. The status of~option~has been altered as indicated.
System Action:
The relevent status has been altered.
User Action:
Ensure that the option has been set as requested.
Reason:
An NDB STOP command was entered for the indicated database.
System Action:
The database will stop when there are no users.
User Action:
If this is not what is wanted, issue an NDB START command for the database.
Reason:
An NDB STOP IMM command was entered for the indicated database. All active users are immediately disconnected and the database will stop.
System Action:
As described.
User Action:
None.
Reason:
An NDB STOP LOCK command was entered for the indicated database. When the database stops, it will be locked to prevent further access until an NDB START UNLOCK command is entered, or SOLVE is restarted.
System Action:
As described.
User Action:
None.
Reason:
An NDB RESET command was entered for the indicated database and successfully processed. All data has been deleted from the database, but field definitions are left intact.
System Action:
As described. The database will stop after this command.
User Action:
None.
Reason:
An &NDBOPEN statement was rejected by the indicated database as it is stopping.
System Action:
The NCL procedure is given a response code.
User Action:
Determine why the database is stopping, and rerun the NCL procedure.
Reason:
To start an NDB in DEFER status requires that the database dataset be opened by the UDBCTL command with the options LSR and DEFER. If this was not done, DEFER status cannot be set.
System Action:
The database runs in NODEFER status.
User Action:
If DEFER status is necessary, STOP the database, UDBCTL CLOSE it, UDBCTL OPEN it, with LSR and DEFER, and NDB START DEFER it.
Reason:
An &NDBOPEN statement was processed for the indicated database, but another user issued an &NDBOPEN EXCLUSIVE statement. Only the exclusive user can access the database.
System Action:
The NCL procedure is given a non-zero response code.
User Action:
Wait for the exclusive user to sign off.
Reason:
An &NDBOPEN EXCLUSIVE statement was processed by the indicated database, but there are currently other users. Thus, the EXCLUSIVE request cannot be honoured.
System Action:
The NCL procedure is given a non-zero response code.
User Action:
Wait for the other users to sign off.
Reason:
The indicated NDB has started, and is (now) in LOAD MODE. This message is a warning message to inform all MONITOR users of this.
System Action:
The NDB does not process keys.
User Action:
Check that LOAD MODE is wanted.
Reason:
The indicated NDB was started with a LOAD MODE request. It was already in LOAD MODE.
System Action:
THe NDB does not process keys.
User Action:
Be aware that LOAD MODE is in effect. It can only be reset by using NDB ALTER OPT=BLDX
Reason:
The indicated NDB was started with an INPUT mode request. Only non-update operations are allowed.
System Action:
No update operations are allowed.
User Action:
NO updating can be done.
Reason:
The indicated NDB was started with an INPUT mode request. It was already active in update mode. The input request is ignored.
System Action:
The NDB remains open in update mode.
User Action:
If input mode is wanted, stop and restart the NDB.
Reason:
The indicated NDB was active, in INPUT mode. The NDB START LOADMODE request cannot be honoured, as it requires the NDB be open for update.
System Action:
The NDB remains open in input mode.
User Action:
If LOADMODE is wanted, stop and restart the NDB.
Reason:
AN NDB START ndbname KEYSTATS=START command was processed. KEYSTATS were unable to start for the displayed reason.
The reason can be:
'ALREADY ACTIVE' - KEYSTATS are already active for this NDB.
System Action:
The request is ignored.
User Action:
Correct the command and re-issue it if required.
Reason:
An NDB START ndbname KEYSTATS=STOP command was processed. KEYSTATS could not be stopped for one of the following reasons:
'NOT ACTIVE' - KEYSTATS are not active for this NDB.
System Action:
The KEYSTATS=STOP request is ignored.
User Action:
Correct the command and-re-enter it if required.
Reason:
The indicated NDB was started with a RIDREUSE option. However, RID reuse status for this NDB cannot be altered. Possible reasons are as follows:
This NDB cannot have RID reuse enabled because the VSAM record length is too short. Control records cannot be upgraded to support RID Reuse. (You must unload the NDB and load it to a new data set with a longer record length.)
RID reuse is already enabled for this NDB.
RID reuse is already disabled for this NDB.
System Action:
RID Reuse status for this NDB is not altered.
User Action:
If required, perform the corrective action as described in the message reason descriptions.
Reason:
The indicated NDB was started with a RIDREUSE option. RID reuse status for this NDB was altered to the indicated status (ENABLED or DISABLED).
System Action:
RID Reuse status for this NDB was altered as requested.
User Action:
None.
Reason:
An NDB request failed as a required load module could not be loaded. The message gives the error reason.
System Action:
The request is not processed.
User Action:
Contact your systems administrator.
Reason:
When attempting to queue a request to a subthread for the indicated database, the Database Manager found that all the subthreads had terminated unexpectedly.
System Action:
The database terminates (stops).
User Action:
Examine the log for messages indicating the reasons the subthreads terminated. Correct the problems and restart the database.
Reason:
The indicated database has stopped, either in response to an NDB STOP command, or because the number of users dropped to 0 and the database was not started.
System Action:
As indicated.
User Action:
None.
Reason:
An NDB CREATE command for the indicated database has been successful. The number of records formatted for the NDB journal is indicated. The VSAM timestamp value is displayed. If LOAD MODE was requested, this is indicated.
System Action:
The database is now ready to be used.
User Action:
Start the database and insert field definitions. Data may then be added.
Reason:
An NDB CREATE command for the indicated database failed as the Database Manager was unable to obtain necessary storage.
System Action:
The database is not created.
User Action:
Determine the reason for the storage shortage. Then retry the create.
Reason:
An NDB CREATE for the indicated database failed because the Database Manager was unable to open the VSAM dataset.
System Action:
The database is not created.
User Action:
Determine why the open failed. Possibly, a UDBCTL OPEN has not been issued.
Reason:
An NDB CREATE for the indicated database failed because the dataset is not a VSAM KSDS.
System Action:
The database is not created.
User Action:
Check that the correct database name was used on the command.
Reason:
An NDB CREATE command for the indicated database failed, as the VSAM relative key position was not 0.
System Action:
The database is not created.
User Action:
Check that the correct database name was used, and, if so, check the VSAM define for the dataset.
Reason:
An NDB CREATE command for the indicated database failed, as the VSAM keylength was less than 16.
System Action:
The database is not created.
User Action:
Correct the VSAM definition for the database.
Reason:
An NDB CREATE command for the indicated database failed, as the VSAM maximum record size was less than 338 + 2 * keylength.
System Action:
The database is not created.
User Action:
Check the VSAM definition for the database.
Reason:
An NDB CREATE command for the indicated database failed, the dataset had data in it.
System Action:
The database is not created. Existing data is not removed.
User Action:
Check that you are not trying to create an already created database. If you really want to clear out existing data, consider the NDB RESET command as an alternative. Otherwise, either delete and redefine the dataset, or UDBCTL OPEN it with the RESET option. The RESET option may be used only for a dataset which has been defined with the REUSE option.
Reason:
An NDB CREATE command for the indicated database failed, as a VSAM error occurred. ff is the VSAM feedback code, in hex.
System Action:
The database is not created.
User Action:
Refer to the VSAM feedback code to determine the cause of the error.
Reason:
An NDB CREATE command for the indicated database failed due to an I/O error during processing.
System Action:
The database is not created. Some data may have been inserted.
User Action:
Determine the cause of the I/O error. The dataset may need to be redefined.
Reason:
An NDB CREATE command for the indicated database failed, as a `file full' condition was encountered during insertion of control information.
System Action:
The database is not created. Some data has been inserted but the database is unusable.
User Action:
Re-allocate the database with more space.
Reason:
While processing an &NDBDEF ADD, the indicated field name was found to be already defined in the database.
System Action:
The entire &NDBDEF statement is not processed.
User Action:
Correct the definition statement.
Reason:
While building internal indexes for the fields defined in a database, an error occurred. The database cannot start.
System Action:
The database fails to start.
User Action:
Contact your product support representative.
Reason:
While processing an &NDBDEF DELETE, the indicated field name was not found to be defined in the database.
System Action:
The entire &NDBDEF statement is not processed.
User Action:
Correct the definition statement.
Reason:
While processing an &NDBDEF DELETE, the name of the sequence key field was found. The sequence key field cannot be deleted.
System Action:
The entire &NDBDEF statement is not processed.
User Action:
Remove the sequence key field name from the delete list.
Reason:
While processing an &NDBDEF ADD, a field other than the first defined for the database was found with a description of KEY=SEQ. Only the first field ever defined to the database is accepted to be the key field for the database.
System Action:
The entire &NDBDEF statement is not processed.
User Action:
Correct the definition statement.
Reason:
An &NDBDEF statement was executed, attempting to add field names to the NDB. However, there were too many fields already in the NDB. The limit is 32,767.
System Action:
The request is cancelled.
User Action:
Split the database into more than one NDB.
Reason:
An &NDBDEF statement contained no fields to add or delete.
System Action:
The statement is not processed.
User Action:
Correct the statement.
Reason:
While processing an &NDBDEF statement, a field name was expected, but not found.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, an invalid keyword was found. This could be due to a missing closing parenthesis.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, an invalid keyword was found. This keyword is not valid for the requested action.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, an invalid field name was found. A field name must follow the rules for NCL variable names (less the ampersand).
System Action:
The &NDBDEF statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an NDBDEF statement, the indicated field name was duplicated in the field list.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, an invalid value was found for the indicated keyword, for example, CAPS=X.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a keyword was duplicated in a field definition.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a keyword requiring text was found, but the value after the `=' was not either a word or a quoted string.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, the text found for a keyword, eg: USER1, was longer than permissible.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, an invalid field name was found.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a sequence key field definition was found that contained NULLFIELD=YES. Since a sequence key field must be present in all records, this is invalid.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a sequence key field definition was found that contained UPDATE=YES. Since a sequence key field cannot change in value, this is invalid.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field definition was found that was not FORMAT=CHAR. The definition also had CAPS=NO. This is invalid. Only character format fields can have CAPS=NO.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field update request had a new name for the field that matches the name of a field in the NDB.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field update request had a new name for the field that matches the name of another field in the statement.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field update request had a new name for the field that matches the new name of another field in the statement.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field update request had a changed field format. The NDB is not empty, and field format changes are only allowed if the NDB is completely empty.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field update request had a KEY alteration to or from KEY=SEQ. This is not permitted.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement or an NDB FIELD command, a field update request had a KEY alteration that is not permitted unless the NDB is empty, or is in LOAD MODE. Only the following key alterations are permitted at any time:
System Action:
The statement or command is not processed.
User Action:
Correct the statement/command.
Reason:
While processing an &NDBDEF statement, a field update request had a NULLFIELD=YES specification for a field with KEY=SEQ. This is not permitted.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field update request had a UPDATE=YES specification for a field with KEY=SEQ. This is not permitted.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field update request had a CAPS= value other than YES, for a field format other than CHAR. This is not permitted.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field update request had a CAPS= value specified that requires an empty NDB or possibly LOADMODE.
System Action:
The statement is not processed.
User Action:
Correct the &NDBDEF statement.
Reason:
While processing an &NDBDEF statement, a field update request could not be honoured, as the old field definition on the NDB could not be read.
System Action:
The statement is not processed. The NDB will stop.
User Action:
Investigate the integrity of the NDB.
Reason:
A numeric fieldnames found in the Database while a numeric fields is not allowed.
System Action:
The NDB start fails.
User Action:
Correct the error fields in the given Database and try again.
Reason:
While processing an &NDBADD or &NDBUPD statement, the nominated field was either not provided (&NDBADD), or the null indicator passed (&NDBUPD), or the field definition has been added since the record was added or last updated (&NDBUPD). The field must be present in the record.
System Action:
The record is not added or updated.
User Action:
Correct the add/update field=value list.
Reason:
While processing an &NDBADD statement, the value provided for the sequence key field already exists. Duplicate values are not permitted for sequence keys.
System Action:
The record is not added.
User Action:
Correct and retry.
Reason:
While processing an &NDBDEL or &NDBUPD statement, no record with the supplied RID was found.
System Action:
The record is not deleted.
User Action:
Provide the correct RID.
Reason:
While processing an &NDBUPD statement, the new value for the indicated field was different to the existing value, and the field is defined as UPDATE=NO.
System Action:
The record is not updated.
User Action:
Correct the update field=value list to either remove the nominated field, or to provide the current value.
Reason:
An &NDBADD or &NDBUPD NCL statement with the FORMAT=fmtname operand was executed, but the format name is not presently defined.
System Action:
An NDB error condition is raised.
User Action:
Correct the NDB NCL statement.
Reason:
An &NDBADD or &NDBUPD NCL statement with the FORMAT=name operand was executed, but the named format is not an output format. Only output formats may be used on &NDBADD and &NDBUPD NCL statements.
System Action:
An NDB error condition is raised.
User Action:
Correct the NDB NCL statement.
Reason:
While processing an &NDBFMT statement, the supplied format name was invalid.
System Action:
The statement is not executed.
User Action:
Correct the format name.
Reason:
The format id supplied on an &NDBFMT statement already exists. It cannot be added.
System Action:
The statement is not processed.
User Action:
Provide a unique format name.
Reason:
The format id supplied on an &NDBGET statement is not currently defined for this user within the scope specified (defaulted).
System Action:
The statement is not processed.
User Action:
Provide a valid, defined format id. Ensure that the same scope is specified on &NDBFMT and &NDBGET statements.
Reason:
The field name supplied on an &NDBGET for get by key field is not defined on the database.
System Action:
The statement is not processed.
User Action:
Provide the name of a defined, key field on the database.
Reason:
The field name supplied on an &NDBGET for get by key field is not defined as a key field in the database.
System Action:
The statement is not processed.
User Action:
Provide the name of a defined, key field on the database.
Reason:
The sequence id supplied on an &NDBGET statement is not defined for this user.
System Action:
The statement is not processed.
User Action:
Provide a defined sequence id. If the sequence was not defined originally with KEEP=YES, and an EOF was returned for it in a previous &NDBGET, the sequence will have been automatically deleted.
Reason:
The key field that the indicated sequence was defined on has been deleted by an &NDBDEF DELETE statement. Thus, no further retrieval by that sequence is possible.
System Action:
The statement is not processed.
User Action:
Determine why the field was deleted.
Reason:
An &NDBGET statement requested get by the indicated sequence, and also specified SKIP=0 (re-read current record). The sequence is currently not positioned on a record.
System Action:
The statement is not processed.
User Action:
Establish position before requesting a re-read.
Reason:
An &NDBGET statement for the indicated sequence specified SKIP=0, but the sequence is currently at either front or back EOF.
System Action:
The statement is not processed.
User Action:
Re-establish position before requesting re-read of a record.
Reason:
An &NDBGET statement requested a generic retrieval. The indicated field's format does not support generic retrieval.
System Action:
The statement is not processed.
User Action:
Provide a valid field for generic retrieval.
Reason:
An &NDBGET statement requested a histogram retrieval. The indicated field is an NDB sequence key. Histogram is not supported for a sequence key.
System Action:
The statement is not processed.
User Action:
Provide a valid field for histogram processing.
Reason:
A format that is defined, but is not an input format, was requested for use on an &NDBGET NCL statement.
System Action:
An error condition is raised.
User Action:
Correct the format name.
Reason:
While parsing free-form text for an &NDBxxx statement, a token value longer than 256 characters was detected.
System Action:
The statement is not processed.
User Action:
Correct the free-form text. A quote may be misplaced or missing.
Reason:
While processing free-form text for an &NDBxxx statement, a quoted string had no closing quote.
System Action:
The statement is not processed.
User Action:
Correct the free-form text.
Reason:
A data item passed in free-format text to the NDB processor on an &NDBxxx NCL statement was too long and was truncated.
System Action:
An error condition is raised.
User Action:
Correct the free-format text.
Reason:
The NCL process has set &NDBCTL TRACE=YES. This message dumps the first 20 characters of each token encountered during parsing of free-form text.
System Action:
None.
User Action:
The messages may be used to detect the point of an error in free-form text.
Reason:
An error occurred when attempting to open the indicated database. The error codes and meanings are:
CODE DESCRIPTION
The Database manager was unable to open the database. Possibly, no UDBCTL OPEN=ddname has been issued for this dataset.
The indicated database dataset is not a VSAM KSDS. Check that the correct dbname was specified.
The indicated database dataset VSAM RKP was not 0. This cannot be a valid NDB database.
The indicated database dataset VSAM keylength was less than 16. This cannot be a valid NDB database.
The indicated database dataset VSAM maximum data length is less than 274 + 2 * keylength. This cannot be a valid NDB database.
The database manager was unable to read the NDB control record. This cannot be a valid, formatted NDB database. The dataset is empty, including the case when the RESET operand was specified on UDBCTL OPEN.
The database manager did not find a valid NDB control record. This cannot be a valid, formatted NDB database. This error can occur if an NDB CREATE failed to complete.
The database manager was unable to obtain required storage for holding the NDB control record.
The database manager was unable to read the NDB transaction control record. This could indicate a corruption of the NDB.
The database manager did not find a valid NDB transaction control record. This could indicate a corruption of the NDB.
The database manager was unable to obtain required storage for holding the NDB transaction control record.
The database manager was unable to obtain required storage for holding the NDB transaction data record.
The database manager detected a previous transaction had not been applied, and had an error when attempting to re-apply it. The database may be full, and need to be copied to a larger dataset.
The defer status flag in the NDB control record was set. This indicates that the database was running in DEFER status when a system or SOLVE failure occurred. As there can be no way of determining the validity or otherwise of the database, it cannot be used.
The UDB is currently open to other users (eg: NCL &FILE ID). An NDB cannot be open as a UDB as well as an NDB.
The UDB was opened with the 'INPUT' option but the NDB START did not have 'INPUT' specified. The NDB cannot be opened in update mode.
The SOLVE domain ID xxxx stored in the NDB control record was different to the domain ID of this SOLVE system.
This means that either (1) the NDB is currently open on another SOLVE system, or, (2) that it was last used with another SOLVE system that did not terminate normally.
This return code warns you that you may be trying to open the NDB for update simultaneously under 2 SOLVE systems. You can override this error if required by using the 'FORCE' and the 'UNLOCK' operands of the NDB START command. However, the 'FORCE' operand should be used only after ensuring that the return code was given because of reason (2) above.
The NDB you are STARTing was created under a version nnnn of SOLVE that is unsupported by this version.
This NDB appears to be already allocated to this SOLVE system (under fileid xxxxxxxx ). You are attempting to open it twice. (This is detected by the VSAM timestamps being the same).
System Action:
The database does not start.
User Action:
Use the error information to find and correct the problem.
Reason:
An error occurred while performing I/O on an NDB.
VFS REQUEST CODE describes the failing action:
4 = GET
8 = PUT
16 = REPL
36 = RESET
R15 is the return code from the action:
8 = Error, see FDBK code for details
12 = I/O Error
16 = Dataset is full
FDBK is the Error Reason Code from the Feedback Area in the VSAM RPL.
System Action:
The database is stopped and LOCKED.
User Action:
If necessary, see the IBM manual DFSMS Macro Instructions for Datasets to determine the meaning of the feedback and the appropriate course of corrective action.
Reason:
An error occured while writing to the Management Services JOURNAL dataset. R15 and FDBK are the VSAM error codes from the JUORNAL write operation.
System Action:
NDB aaaaaaaa is stopped and journaling is discontinued.
User Action:
Correct the problem with the journal dataset. If is is not possible to recover the journal dataset, all NDBs which rely on journaling should be stopped and backed up before proceeding.
Reason:
When opening an NDB, the internal saved SOLVE domain ID was not blank, and not the same as the current domain ID. The NDB START command had FORCE specified, and the domain ID has been reset.
System Action:
The database starts.
User Action:
Check that the NDB is not simultaneously open on another SOLVE system.
Reason:
When opening an NDB, the internal saved UDB FILEID was not the same as the NDB name. It has been reset.
System Action:
The database starts.
User Action:
This is a warning message. THe different file id could be because a copy of a production database is being opened under another name.
Reason:
The indicated token in the free-form text is not a valid field name.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the free-format text field name.
Reason:
The indicated field name is a valid field name, but is not defined on the NDB.
System Action:
The requested NDB operation is cancelled.
User Action:
Provide the correct, defined field name.
Reason:
The indicated field was specified more than once in a fieldname = fieldvalue list for an &NDBADD or &NDBUPD statement, but the values were different.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the duplicated entry, by either removing it, or by ensuring the values are identical.
Reason:
While processing a fieldname = fieldvalue list for an &NDBADD or &NDBUPD statement, something other than `=' or `EQ' was found following a field name.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the syntax of the list.
Reason:
The value found for the indicated fieldname was not in the correct format, or was unrecognisable.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value for the indicated field.
Reason:
The supplied value for the indicated field was too long. For example, a character-format field that is keyed had a value longer than the VSAM keylength - 8.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value for the indicated field.
Reason:
The supplied value for a numeric field had non-numeric characters, or the numeric value was greater than the valid range that will fit in a fullword (-2,147,483,648 to +2,147,483,647).
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value for the indicated field.
Reason:
The supplied value for a hex-format field contained characters other than 0-9, A-Z, a-z, or had an odd number of characters.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value for the indicated field.
Reason:
The supplied value for the indicated field is the null value (blank for character, 0 for numeric, blank for hex, 000000 for date), and the field has been defined with NULLVALUE = NO. Thus, the null value is not permitted.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value for the indicated field.
Reason:
The supplied value for the indicated field is not a valid DATE or CDATE. The expected format depends on the &NDBCTL DATEFMT setting. These formats are:
For the field format of DATE means that the date will only be accepted in the YYMMDD (DATE7) format. For the field format of CDATE means that a 6-digit number is processed as YYMMDD (DATE7) and an 8-digit number is processed as YYYYMMDD (DATE8).
The date data will be accepted in the format that the current user is profiled with, either UK or US format.
YY.DDD
DAY DD-MON-YEAR
DD-MON-YEAR
DD/MM/YY
MM/DD/YY
YY/MM/DD
YYMMDD
YYYYMMDD
n (the number of days from 1 January 0001)
YYYYMMDDHHMMSSxHHMM
Note that a 0 value is always valid and indicates a null date. See the NCL Reference (&DATEn system variables) for more explanation about the date formats.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value for the indicated field.
Reason:
The supplied value for the indicated field is not a valid floating point number.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value for the indicated field.
Reason:
&NDBCTL QUOTE=YES is in effect, and thus the value supplied for the named field must be in quotes.
System Action:
The value is rejected. Further action depends on the specific &NDBxxx NCL statement being processed.
User Action:
Correct the supplied value.
Reason:
The supplied value for the named field must be a valid hexadecimal number, from 1 to 8 hex digits.
System Action:
The value is rejected. Further processing depends on the specific &NDBxxx NCL statement being processed.
User Action:
Correct the value.
Reason:
The supplied value for the indicated field name is not a valid time, in the format 'HHMMSS.tttttt'.
System Action:
The value is rejected. Further processing depends on the specific &NDBxxx NCL statement being processed.
User Action:
Correct the supplied value.
Reason:
The supplied value for the named field is not a valid timestamp, in the format 'YYYYMMDDHHMMSS.tttttt'.
System Action:
The value is rejected. Further processing depends on the specific &NDBxxx NCL statement being processed.
User Action:
Correct the value.
Reason:
The supplied value was not a either a number, word, or quoted string.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value.
Reason:
While processing a value entry for a field, invalid data was found following it.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value. Quoting may be required.
Reason:
While processing an output format, the value retrieved from a variable was too long for the target NDB field.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value.
Reason:
While attempting to read an NDB data record with the indicated RID, an error occurred.
System Action:
The requested NDB operation is cancelled.
User Action:
Report the problem to your systems administrator.
Reason:
While processing an &NDBADD or &NDBUPD statement, the supplied value for the indicated field already exists in the NDB, and the field is defined as uniquely keyed (or a sequence key).
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the value for the indicated field.
Reason:
While processing key records for the indicated field, an error occurred when issuing an internal GET KGE for the key value.
System Action:
The requested NDB operation is cancelled.
User Action:
Report the problem to your systems administrator.
Reason:
While processing key records for the indicated field, an error occurred when issuing an internal GET for the high-value key record.
System Action:
The requested NDB operation is cancelled.
User Action:
Report the problem to your systems administrator.
Reason:
While processing key records for the indicated field, an error occurred when issuing an internal GET KGE for the key value.
System Action:
The requested NDB operation is cancelled.
User Action:
Report the problem to your systems administrator.
Reason:
While processing a format list on &NDBFMT or &NDBGET, the first word was not a valid format type: NO-FIELDS, KEY-FIELDS, ALL-FIELDS, FIELDS for INPUT formats or ALL- FIELDS, FIELDS for OUTPUT formats
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, an invalid, or an out of place keyword/variable name was encountered.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on &NDBFMT or &NDBGET, invalid data was found when either the end of the list, a field name, or an opening parenthesis was expected.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on &NDBFMT or &NDBGET, an invalid database field name (for an INPUT format) or NCL variable name (for an OUTPUT format) was found. The.RID keyword may be specified on the right hand side of a field entry for an INPUT format only.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on &NDBFMT or &NDBGET, unrecognized data was encountered when a closing parenthesis was expected.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, a field assignment statement was found where the target variable name was generic but the source database field name was not. Either both or neither of these values may be generic.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, a generic assignment was encountered where the target variable name prefix was longer than the source dbfield name prefix, however, a field field was encountered, which although not 12 characters long, would have generated an NCL variable name longer than 12 characters when the dbfield prefix was replaced with the field prefix.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, an opening parenthesis was encountered, however data was not a valid field/variable name or a generic name.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, a generic assignment statement was encountered which contained a numeric prefix for variableprefix but a non-numeric prefix for dbnameprefix. This would cause variable names to be generated which were non-numeric but which began with a numeric character, which is not allowed in NCL statements.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on &NDBFMT or &NDBGET, a field name that is not a defined field on the database was encountered.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing an input format list on an &NDBFMT or an &NDBGET, an assignment of a database field to an NCL variable name was encountered, however, the variable name was a special NCL reserved keyword, for example, IF. NCL keywords may not be used as targets for assignment of database fields.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
The nominated source field name is an NCL verb or builtin function name, for example, IF. Only NCL system variables are valid as output format source field names.
System Action:
The output format is not built.
User Action:
Correct the output format.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, a format field entry in parentheses was encountered, and either an unrecognized or misspelt keyword was encountered, or more than one field entry was entered. Each field entry must be in its own set of parenthesis.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
An output format has named the same NDB field twice.
System Action:
The output format is not built.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, a formatting option which required an argument preceded by an equals sign (for example, PAD = character) was found, however, there was no equals sign encountered.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, formatting option bbbbbb was encountered, however the argument data specified for it was not valid.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, the LENGTH option was encountered but the operand, length, was not in the range 0- 255.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, the PAD option was encountered but the operand, character, was more than one character long or was not properly enclosed in quotes..
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, the facility to link multiple records was used, but an attempt was made to link more than the maximum allowed. The maximum number allowed was n .
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition. To link more records, use separate NDB statements.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, the LINK option was encountered but was not followed by an opening parenthesis. The operands for the .LINK are required to be in parentheses.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, either an unknown or misspelt .LINK keyword was encountered, or there was no closing parenthesis after the .LINK keywords. The field lists following the link keywords and any subsequent .LINK keywords must not come before the closing parenthesis.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing the .LINK options within a format list on an &NDBFMT or an &NDBGET, an option was encountered which needed an operand preceded by an equals sign, for example, the FROM= operand, however no equals sign was encountered.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, keyword kwrd was encountered twice. Each keyword should only be present once.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, the fieldname name specified as the field from which to extract the search key value for a .LINK was not a valid field name or does not exist on the NDB.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, the fieldname name specified as the field to search on to perform the .LINK either was not a valid field name, did not exist on the NDB, or was not keyed. The field must be keyed to perform the search.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, the ID linkid specified as the reference for this .LINK operation was either invalid (contained invalid characters) or was used in a previous link operation on the same statement.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, the linkid representing the ID of the previous link operation from which to link in this operation was either invalid (that is contained invalid characters) or did not exist on a previous link operation on the same statement.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, the value of the nofind operand was invalid.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, a .LINK operation was attempted, however one or both of the FROM= and TO= operands was missing. Both of these operands are mandatory.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
While processing a format list on an &NDBFMT or an &NDBGET, a .LINK operation was attempted, however the fields specified on the FROM= and the TO= operands were a different format. They must be the same format, that is, both character, or both numeric etc.
System Action:
The requested NDB operation is cancelled.
User Action:
Correct the format definition.
Reason:
The sequence name seqname is not a valid sequence name.
System Action:
The sequence is not defined.
User Action:
Provide a valid sequence name.
Reason:
The sequence name supplied on an &NDBSEQ already exists for this process, and thus cannot be added.
System Action:
The sequence is not redefined.
User Action:
Provide a unique sequence name.
Reason:
When defining a sequence by RID, the supplied `from' RID value was not valid.
System Action:
The sequence is not defined.
User Action:
Correct the from RID value.
Reason:
When defining a sequence by RID, the supplied `to' RID value was not valid.
System Action:
The sequence is not defined.
User Action:
Correct the to RID value.
Reason:
When defining a sequence by RID, the supplied `from' RID value was greater than the supplied `to' RID value.
System Action:
The sequence is not defined.
User Action:
Correct the RID values.
Reason:
When defining a sequence by a key field, the named field was not defined on the database.
System Action:
The sequence is not defined.
User Action:
Provide a valid key field name.
Reason:
When defining a sequence by a key field, the named field was not defined as keyed.
System Action:
The sequence is not defined.
User Action:
Provide a valid, keyed field name.
Reason:
When defining a sequence by a key field, the provided FROM value was null.
System Action:
The sequence is not defined.
User Action:
Provide a non-null from value, or omit it altogether.
Reason:
When defining a sequence by a key field, the provided TO value was null.
System Action:
The sequence is not defined.
User Action:
Provide a non-null to value, or omit it altogether.
Reason:
When defining a sequence by a key field, the provided FROM value was greater than the provided TO value.
System Action:
The sequence is not defined.
User Action:
Ensure that the supplied FROM and TO values are correctly specified.
Reason:
When defining a sequence by a key field, the provided VALUE= value was null.
System Action:
The sequence is not defined.
User Action:
Provide a non-null VALUE value.
Reason:
When defining a sequence by a key field, the GENERIC= option was used, but this field format does not support generic operations.
System Action:
The sequence is not defined.
User Action:
Use the FROM/TO or VALUE options instead.
Reason:
When defining a sequence by a key field, the provided GENERIC= value was null.
System Action:
The sequence is not defined.
User Action:
Provide a non-null GENERIC= value.
Reason:
The indicated sequence name is currently defined by an in-progress NDBSCAN operation.
System Action:
The sequence is not defined.
User Action:
Provide a unique sequence name.
Reason:
The indicated field name is a sequence key for the NDB. A Histogram sequence is not permitted on the sequence key.
System Action:
The sequence is not defined.
User Action:
use a non-sequence-key field.
Reason:
The NDB is in LOAD MODE. Thus no keys are maintained. This prevents a sequence from being defined on a keyed field.
System Action:
The sequence is not defined.
User Action:
Use the NDB ALTER command to build the indices.
Reason:
The indicated sequence name is not known, so it cannot be reset.
System Action:
None.
User Action:
Provide the name of a defined sequence. Check that the desired sequence was defined with KEEP=YES, if you wish to reset it after an EOF has occurred.
Reason:
The supplied FROM RID value for a sequence definition was not numeric.
System Action:
The sequence is not defined.
User Action:
Correct the RID value.
Reason:
After processing the FROM RID value on an &NDBSEQ statement, unrecognized data was found following it.
System Action:
The sequence is not defined.
User Action:
Correct the &NDBSEQ statement.
Reason:
The supplied TO RID value for a sequence definition was not numeric.
System Action:
The sequence is not defined.
User Action:
Correct the RID value.
Reason:
After processing the TO RID value on an &NDBSEQ statement, unrecognized data was found following it.
System Action:
The sequence is not defined.
User Action:
Correct the &NDBSEQ statement.
Reason:
The supplied REPOS= RID value was not numeric, or was less than the defined FROM RID, or greater than the defined TO RID.
System Action:
The sequence is reset, but not repositioned.
User Action:
Correct the reposition RID value.
Reason:
The supplied REPOS= field value was null.
System Action:
The sequence is reset, but not repositioned.
User Action:
Correct the reposition value.
Reason:
An &NDBSEQ RESET REPOS= statement was attempted on a sequence built by &NDBSCAN. The scan did not specify a sort field. Only sorted scan sequences can be repositioned.
System Action:
The sequence is reset, but not repositioned.
User Action:
If repositioning is required for the list, specify a SORT field on the &NDBSCAN.
Reason:
A reposition by RID was attempted on a sequence not built by &NDBSCAN.
System Action:
The sequence is reset, but not repositioned.
User Action:
Only sequences built by &NDBSCAN can be repositioned to a specific RID. If you require this, build the sequence using &NDBSCAN.
Reason:
An &NDBSEQ RESET NCL statement attempted to use the RELPOS=n operand to reposition the nominated sequence. The sequence was not built by &NDBSCAN, thus the RELPOS repostion is not supported.
System Action:
An NDB error is returned.
User Action:
Correct the &NDBSEQ NCL statement.
Reason:
An &NDBSEQ RESET REPOS=value NCL statement has attempted to reposition a sequence that, whilst sorted, is not suitable for reposition. This is because the primary sort field was substringed.
System Action:
An NDB error is returned.
User Action:
Correct the &NDBSEQ NCL statement.
Reason:
The relative field number provided on an &NDBINFO NUMBER=n was less than 1, or greater than the number of fields currently defined in the database.
System Action:
No information is returned.
User Action:
Correct the relative field number.
Reason:
The supplied sequence name on an &NDBSCAN is currently defined as a sequence (not necessarily a SCAN sequence).
System Action:
The scan is not processed.
User Action:
Provide a unique sequence name.
Reason:
The supplied sequence name on an &NDBSCAN is currently being processed as another &NDBSCAN.
System Action:
The scan is not processed.
User Action:
Provide a unique sequence name.
Reason:
An error was found in the &NDBSCAN sort expression. The message text describes the error and location.
System Action:
The scan is not processed.
User Action:
Correct the sort expression.
Reason:
An unexpected token was found in the scan expression. An 'AND', 'OR', or a right parenthesis was expected.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The optional IGNORE clause is followed by 'token', the value allowed is TRUE or FALSE.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
An invalid field name found in the scan expression.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The field-name found in the scan expression is not defined on database.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The fieldname on the left of the RANGE expression is invalid.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The fieldname on the right of the RANGE expression is less than the fieldname on the the left of the RANGE expression.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
A range or generic field name specification was provided but no fields on the NDB match the name specification.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The operator aaaaaa found in the scan expression is invalid.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The operator aa found in the scan expression is invalid. It must be NULL.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The operator found after NOT is not a valid operator.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
ANY or ALL is invalid on the left hand side of the operator aaaaaa
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The field lists on the left hand side of the given operator is invalid.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
A mixed field formats is invalid when using the operator aaaaaa.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
CONTAINS or LIKE operator is invalid while using the given field format.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The given operator aaaaaa does not support fields on the left hand side.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
Syntax error found in the scan expression. A '(' was expected, but the displayed token was found.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The sequence name aaaaaa found in the scan expression is invalid.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The sequence name aaaaaa found in the scan expression was not found in the current list of sequences owned by the requesting user ID.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The sequence name in the scan expression names a sequence not built by an &NDBSCAN.
System Action:
The scan is not processed.
User Action:
Use &NDBSCAN SEQUENCE=name to specify the sequence name used in the scan expression.
Reason:
Syntax error found in the scan expression. The word 'AND' was expected but the displayed token was found.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The value of the second operand is lower than the first operand in the scan expression.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
Syntax error found in the scan expression. Either ',' or ' ', was expected but the displayed token was found.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
At least one of the fields provided to a scan operator is of a different type to the other fields.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
For the given field format in the scan expression PLUS or MINUS N is invalid.
System Action:
The scan is not processed.
User Action:
Use &NDBSCAN SEQUENCE=name to specify the sequence name used in the scan expression.
Reason:
The adjust amount given in the the scan expression is invalid.
System Action:
The scan is not processed.
User Action:
Correct the scan syntax.
Reason:
The generic or range value on the right hand side of the operator given is invalid.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The indicated scan subselect correlation id is not valid. It must be a 1 to 8 character name with the first character alpha or national, and the remaining characters alphanumeric or national, or a single asterisk (*).
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The correlation id xxxxxx found in the scan expression is not a parent id.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
Syntax error found in the scan expression expected ')' after correlation id but found 'token'.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
A correlated scan test was found with the PLUS or MINUS clause. PLUS/MINUS is not permitted when performing a correlated test.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
A generic comparison has been requested for a field with a format that does not support it, for example a numeric field.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The format of the fieldname is invalid when using this subselect.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
Syntax error found in the scan expression. Expected 'WHERE' but found xxxx.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
Syntax error found in the scan expression. Either ',' or 'FROM' was expected but found xxxxx.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
Syntax error found in the scan expression. An NDB name was expected but xxxxx was found.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The correlation id xxxxxx found in the scan expression is invalid.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The scan expression is incomplete, missing information after aaaaaa.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The scan expression is invalid, the keyword expected is 'SELECT'.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
Both of the fields used in comparison must be non NULL.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
In the scan expression SELECT or FROM or WHERE clause is invalid.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
The syntax aaaaaa in the scan expression is invalid.
System Action:
The scan is not processed.
User Action:
Correct the scan expression.
Reason:
This message indicates that a dump of a successfully parsed (analysed but not yet processed) scan request follows. This will occur if &NDBCTL SCANDEBUG=YES is in effect. If optimisation is in effect for this request, the 'type' field will show 'OPTIMISED', otherwise it will show 'PARSED'. THe NDB name and internal scan id are shown. THese will match up the processed trace messages, starting with N87K31.
System Action:
None. The debug information follows.
User Action:
None.
Reason:
This is the first line of scan debug output. It provides headings for message N87K03. The headings are:
The sequence name assigned to this scan, or '-' if none.
The SORT option, YES or NO.
The KEEP option, YES or NO.
The EXECUTE option, YES or NO.
THe RETDEL option, YES OR NO.
The RETPOS option, YES or NO.
The OPTIMISE option, YES or NO.
The value used as the I/O limit for this scan.
The value used as the TIME limit for this scan.
The value used as the STORAGE limit for this scan.
The value used as the RECORD limit for this scan.
System Action:
None.
User Action:
None.
Reason:
This line of the scan debug output displays various parameters in effect for the scan. The column headings and descriptions are in message N87K02. Refer to that message for details.
System Action:
None.
User Action:
None.
Reason:
This line of the scan debug output shows up to the first 50 characters of the scan expression.
System Action:
None.
User Action:
None.
Reason:
This line of the scan debug output contains addition scan expression text, as required.
System Action:
None.
User Action:
None.
Reason:
This scan debug message describes the sort options in effect for this scan. Each line displays the field name, and the optional start and end substring, and sort direction.
System Action:
None.
User Action:
None.
Reason:
This line of scan debug output is a header line for the following list of individual scan tables and sub-scan table (subselects). The headings are:
The internally assigned scan table id.
An optional correlation id.
The parent scan table.
The scan table result type:
PRIMARY - The primary scan table - result is the list of records.
UNIQUE - Keep unique field values for outer scan
LARGEST - Keep largest unique value for outer scan
SMALLEST - Keep smallest unique value for outer scan
EXISTS - Keep existence of at least one matching record.
The index of the first line in the action table dump.
Whether or not the scan is correlated. There are 3 possibilities:
NO - The scan is not correlated.
YES - The scan is correlated.
DEP - The scan is not correlated, but depends on a correlated sub-select.
The optimizer-assigned priority.
System Action:
None.
User Action:
None.
Reason:
This line contains the information about each scan table. Refer to message N87K10 for an explanation of each field.
System Action:
None.
User Action:
None.
Reason:
This is a heading line of the scan debug table. It provides column headings for the following dump of the parsed scan action table. The column headings are:
LINE - The table line number. Referred to in other columns, and indexed by the N87K11 individual table description lines.
NEXT - The next table line to execute after this one, including under a parent (for example AND) line.
TYP - The type of table line. The values can be:
AND - 'AND' operation.
OR - 'OR' operation.
NOT - 'NOT' operation.
REL - 'relation' test operation.
PRTY - The optimizer-assigned priority.
S/IG - Either a sub-line index or the IGNORE option.
RELATION INFORMATION - individual relation information.
System Action:
None.
User Action:
None.
Reason:
This scan debug message precedes the action table for each individual scan expression or sub-select expression. The internal id and first line number of the following expression are displayed. These line up under the LINE and NEXT heading columns of the N87K12 message.
System Action:
None.
User Action:
None.
Reason:
This scan debug message describes a single scan action table entry. The columns are:
line - the assigned line number of this line.
next - the next-to-execute line number under the line's parent.
type - the type of line, AND, OR, NOT, or REL.
prty - the optimizer-assigned priority.
s/ig - The first sub-line (AND/OR/NOT), or IGNORE option (REL).
specific-information - depends on the type of line:
System Action:
None.
User Action:
None.
Reason:
This scan debug line provides additional information about a specific scan test as described in the preceding N87K14 message. The specific information contains:
System Action:
None.
User Action:
None.
Reason:
This scan debug message follows message N87K15 and provides additional information for sub-select tests.
The list of fields that values will be extracted from is contained in this message, which will repeat if required.
System Action:
None.
User Action:
None.
Reason:
This scan debug message is the first message produced following the execution of an &NDBSCAN with the debug facility requested. The NDB name and internal id (iid) can be used to match the execution dump with the parsed dump (headed by message N87K01).
System Action:
None.
User Action:
None.
Reason:
This scan debug message provides headings for the following N87K33 message, which provides result information about the scan. The headings are:
RSP - The NDB response code.
RECORDS - The number of records that passed the scan.
I/O - The total number of logical I/Os issued.
TIME - The elapsed time in seconds.
MAXSTG - The peak amount of storage used while processing the scan.
System Action:
None.
User Action:
None.
Reason:
This scan debug message provides information about the results of the scan. Refer to message N87K32 for column headings and meanings.
System Action:
None.
User Action:
None.
Reason:
This scan debug message provides column headings for the following N87K35 messages, one per scan or sub-select. A correlated scan or subselect will produce 2 N87K35 lines, the second of which will contain grand totals (the first contains last-exec totals only).
The headings are:
IID - The internal id assigned to this scan or sub-select. When displaying grand totals for a correlated scan, the iid will be ' -CT' meaning this is the totals for the scan identified on the previous line.
'.PRI' identifies the primary (outer) scan.
'.SRT' identifies the final sort (if performed)
K-EXE - The number of times key-level processing was performed for this scan (0 or 1, unless correlated, where many executions are possible).
I/O-K - The number of key-level I/Os performed.
TIME-K - The time taken for key-level processing.
R-EXE - The number of time record-level processing was performed for this scan (0 or 1, unless correlated, where many executions are possible).
I/O-R - The number of record-level I/Os performed.
TIME-R - The time taken for record- level processing.
RSTG - The amount of storage used for the result list from this scan or sub-select.
UNQVALS - For a sub-select, the number of unique values that were found and stored in the result list.
System Action:
None.
User Action:
None.
Reason:
This scan debug message provides scan or sub-select level totals. Refer to message N87K34 for column headings and details.
System Action:
None.
User Action:
None.
Reason:
This scan debug message provides column headings for the following N87K40 Messages. It shows which columns are relevent to the key level processing, and which are relevent to the record level processing.
System Action:
None.
User Action:
None.
Reason:
This scan debug message provides column headings for the following N87K40 messages.
For key-level processing, the headings are:
RESULT - The result of the key level processing of this line. Possible values are:
SKIPPED - This line was not executed due to run-time decisions or optimisation.
ABANDONED - This line was abandoned due to excessive I/O counts.
NO-FILE - No records passed this line.
ALL-FILE - All records passed this line.
PART_FILE - Some records passed this line.
NOT-PART - all but some records passed this line.
SCAN - Whether or not the result list of records requires re-evaluation by scanning.
COUNT - The number of records passing (for PART-FILE) or not passing (for NOT-PART).
For record-level processing, the headings are:
IN - The number of records passed into this line for evaluation
PASS - The number of passed in records that passed the test.
FAIL - The number of passed in records that failed the test.
NULL-FLD - The number of passed in records that had a null-field failure on this test.
System Action:
None.
User Action:
None.
Reason:
This scan debug message provides column headings for the following N87K41 messages, that contain statistical information about key-level processing. The headings are:
TIME - The time taken to process this line.
I/O - The number of logical I/Os expended processing this line, excluding I/O expended in evaluating any required sub-selects.
BMENT - The number of spare bitmap blocks required to store the result list.
BMSTG - The amount of bitmap storage required to store the result list.
System Action:
None.
User Action:
None.
Reason:
This scan debug message heads up the action table dump for each scan expression or subselect. The internal id of the scan or subselect is shown. Also, if this subselect is correlated, a warning re the following statistics only representing the last execution is shown.
System Action:
None.
User Action:
None.
Reason:
This scan debug message shows execution information about a single scan action table line. Refer to message N87K37 for column meanings.
System Action:
None.
User Action:
None.
Reason:
This scan debug message provides additional key-level processing statistics for each line of a scan action table. Refer to message N87K38 for column headings.
System Action:
None.
User Action:
None.
Reason:
This line of the scan debug messages indicates the end of the scan debug output.
System Action:
None.
User Action:
None.
Reason:
This message is issued when an NDB UNLOAD is requested.
System Action:
The unload commences processing.
User Action:
None.
Reason:
This message is issued during an NDB UNLOAD request after the field definitions have been successfully unloaded. The message indicates that n field definitions were unloaded.
System Action:
The unload continues.
User Action:
None.
Reason:
This message is issued during an NDB UNLOAD request at the commencement of the unload of the data portion of the database.
System Action:
The unload continues.
User Action:
None.
Reason:
This message is issued at the completion of an NDB UNLOAD request. It indicates than n records were unloaded from the NDB, the unload finished at time, and m records per minute were unloaded.
System Action:
None.
User Action:
None.
Reason:
This message is issued at the completion of an NDB UNLOAD request. It indicates than n records were in error during the unload, however, out of those n records, m records were still unloaded.
System Action:
None.
User Action:
None.
Reason:
This message is issued at the completion of an NDB UNLOAD request. It indicates that n records were unloaded from the NDB, the unload finished at time time, the average rate of unloading the database was m records per minute and there were a total of q records written to the output UDB.
System Action:
None.
User Action:
None.
Reason:
An NDB UNLOAD was requested, however the fieldname name specified in the SEQUENCE option does not exist on the NDB dbname. The fieldname must exist on the NDB and it must be a keyed field.
System Action:
The unload request is not performed.
User Action:
Correct and retry.
Reason:
An NDB UNLOAD was requested, however the fieldname name specified in the SEQUENCE option specifies a field which is not keyed. The fieldname must exist on the NDB and it must be a keyed field.
System Action:
The unload request is not performed.
User Action:
Correct and retry.
Reason:
An NDB UNLOAD was requested, however an option was specified on the unload request which is not recognized. See the Command Reference for a a description of the correct NDB UNLOAD command syntax.
System Action:
The unload request is not performed.
User Action:
Correct and retry.
Reason:
An NDB UNLOAD was requested for file dbname specifying the file ddname as the output UDB. However, when the UNLOAD command attempted to open the file, it received an open error. The file ddname must be an existing ESDS, and must be ALLOCATED and opened via UDBCTL.
System Action:
The unload request is not performed.
User Action:
Correct and retry.
Reason:
An NDB UNLOAD was requested, however the output fileid ddname was not a VSAM ESDS.
System Action:
The unload request is not performed.
User Action:
Correct and retry.
Reason:
An NDB UNLOAD was requested, however the output file specified by ddname aaaaaaaa had a record size of less than 300 bytes. The output file must have a record size of at least 300 bytes for the unload.
System Action:
The unload request is not performed.
User Action:
Correct and retry.
Reason:
An NDB UNLOAD was requested, however the output file ddname was in use by another user. The output file for an unload must not be in use for the unload to perform.
System Action:
The unload request is not performed.
User Action:
Correct and retry.
Reason:
An NDB UNLOAD was requested. An error occurred while attempting to read the field definition record for the indicated field. Refer the problem to the system administrator.
System Action:
The unload request is not performed.
User Action:
Report the problem to your systems administrator.
Reason:
During an NDB UNLOAD, the record with id rid had invalid internal pointers stored in the NDB. This indicates that the NDB dbname may be corrupted.
System Action:
The record is unloaded and the unload continues, provided the option to stop in error is not specified.
User Action:
None.
Reason:
During an NDB UNLOAD, a response code of nn was encountered reading the record with the rid of mmmmmm.
System Action:
The record is unloaded and the unload continues, provided the option to stop in error is not specified.
User Action:
number is the record number of the output UDB of the record in question. Examine this record to check what actually got unloaded.
Reason:
During an NDB UNLOAD, a response code of nn was encountered reading the record with the rid of mmmmmm.
System Action:
The record is not unloaded but the unload continues, provided the option to stop in error is not specified.
User Action:
None.
Reason:
During an NDB UNLOAD request, SOLVE ran short of storage.
System Action:
The unload request terminates.
User Action:
Consider increasing the SOLVE region/virtual storage/partition size.
Reason:
While performing an NDB UNLOAD request, a VSAM I/O error was encountered writing to the output ESDS ddname.
System Action:
The unload request terminates.
User Action:
Refer to the VSAM messages and codes manual for a description of code and feedback.
Reason:
While performing an NDB UNLOAD request, a VSAM I/O error was encountered reading the NDB dbname.
System Action:
The unload request terminates.
User Action:
Refer to the VSAM messages and codes manual for a description of code and feedback.
Reason:
While performing and NDB UNLOAD request, an NDB STOP IMMEDIATE command for dbname was entered on this SOLVE system.
System Action:
The unload request terminates.
User Action:
None.
Reason:
An error occurred during an NDB UNLOAD request as described by a previous message, and the unload is terminating because the option to terminate the unload if an error occurs was in effect.
System Action:
The unload terminates.
User Action:
None.
Reason:
This message is produced whenever an NDB KEYSTATS run is commenced or restarted.
System Action:
NDB key statistics collection commences.
User Action:
None.
Reason:
This message is produced when an NDB key statistics collection run ends normally. The number of VSAM records read during collection, and the number of yields (times when statistics collection paused while other NDB activity occurred) is displayed.
System Action:
None.
User Action:
None.
Reason:
This message is produced during an NDB KEYSTATS run, at the end of statistics collection for each field. Various statistics are displayed. These statistics fields are:
The name of the NDB.
The name of the field.
The internal field identification (in hex).
The number of unique values of the key field.
The number of VSAM records containing key information.
THe number of NDB records that contain the field.
The minimum count of any unique value.
The maximum count of any unique value.
The average count of any unique value.
The modal occurrence of any unique value.
The count of modal occurrence.
The minimum count of unique value key records.
The maximum count of unique value key records.
The average count of unique value key records.
The modal occurrence of any unique value key records.
The count of modal occurrence of key records.
The minimum key length.
The maximum key length.
The average key length.
The modal key length.
The count of modal occurrence of key length.
The maximum all-equal key length.
System Action:
None.
User Action:
None.
Reason:
This message is produced during a KEYSTATS run when the RID Reuse scan phase is starting.
System Action:
NDB RID reuse scan processing commences.
Message N87V70 will be logged, with additional information.
User Action:
None.
Reason:
This message is produced during a KEYSTATS run when the RID Reuse scan phase has ended.
The number of RIDs recovered and the total number of available reuseable RIDs is displayed.
System Action:
NDB RID reuse scan processing terminates.
Message N87V71 will be logged, with additional information.
User Action:
None.
Reason:
This message is logged during a KEYSTATS run when the RID Reuse scan phase is starting.
It shows the RID range(s) that will be scanned looking for deleted, and therefore reuseable RIDs.
System Action:
NDB RID reuse scan processing commences.
User Action:
None.
Reason:
This message is logged during a KEYSTATS run when the RID Reuse scan phase has ended.
Various statistics are shown:
a - The total number of RIDs that were scavenged for reuse by this scan.
b - The number of consecutive RID ranges that were scavenged for reuse by this scan.
c - The total number of free RIDs that were found during this scan that were in consecutive ranges less then the reuse threshold (as set by the NDBRUMIN Sysparm).
d - The number of consecutive RID ranges that were found during this scan that were smaller than the reuse threshold range (as set by the NDBRUMIN Sysparm).
e - The total number of reuseable RIDs following completion of this run. This total includes previous reuseable RID ranges that were outside the range scanned by this run, as well as the 'current' reuse range.
f - The number of VSAM records written to hold the reuse lists.
g - The number of RIDs actually reused since the last completed KEYSTATS (and reuse scan) run.
h - The number of new R IDs allocated since the last completed KEYSTATS (and reuse scan) run.
i - The number of VSAM reads issued during this reuse scan.
j - The number of yields issued due to work arriving for this NDB during the reuse scan.
System Action:
NDB RID reuse scan processing terminates.
User Action:
None.
Reason:
This message explains why a KEYSTATS=START request has failed. The descriptive reason will be:
NDB IS IN LOAD MODE.
NDB IS OPEN FOR INPUT.
System Action:
The KEYSTATS run is not started.
User Action:
Correct the problem, if required and restart the NDB.
Reason:
This message is produced if an NDB STOP command is entered for an NDB whilst a KEYSTATS collection run is in progress.
The statistics collection is terminated. Unless overridden, the keystats will be restarted on the next NDB START.
System Action:
Key statistics collection is terminated.
User Action:
None.
Reason:
An NDB START ndbname KEYSTATS=STOP command has caused an in-progress key statistics collection run to be terminated.
System Action:
Key statistics collection is terminated.
User Action:
None.
Reason:
This message is produced at NDB start-up when an NDB START ndbname KEYSTATS=STOP command causes the pending keystats restart to be cancelled.
System Action:
The pending keystats restart is cancelled.
User Action:
None.
Reason:
A VSAM I/O error occurred during KEYSTATS processing. The R15 value and VSAM feedback codes are displayed.
System Action:
The keystats run is terminated.
User Action:
Report the error information to your product support representative.
Reason:
This message indicates the actions that will be performed by the entered NDB ALTER command.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the indicated field will be indexed by the entered NDB ALTER command. If it is to be marked as unique, the word (UNIQUE) will appear.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the indicated work file for NDB ALTER command processing has opened successfully.
System Action:
None.
User Action:
None.
Reason:
This message indicates the amount of sort work space that the NDB ALTER command will use.
System Action:
None.
User Action:
None.
Reason:
This message indicates the number of fields on the NDB that the NDB ALTER command is processing, and the number which are keyed in some way.
System Action:
None.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has commenced, and the NDB data is being read.
System Action:
None.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has read some records, and the number of keys extracted is noted. This is a checkpoint message, to inform of progress through the ALTER processing.
System Action:
None.
User Action:
None.
Reason:
This message indicates that a the NDB ALTER sort work area filled up, and the sorted string is being written to the work file.
System Action:
Processing continues.
User Action:
If excessive strings are written, consider increasing the SORT= size on the NDB ALTER command.
Reason:
This message indicates that a the NDB ALTER sort string has been written to the work file.
System Action:
Processing continues.
User Action:
If excessive strings are written, consider increasing the SORT= size on the NDB ALTER command. Also consider using a large CI and record size for the work file to speed up writing.
Reason:
This message indicates shows the totals for the sorted keys and strings for NDB ALTER processing.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has read all records, and the number of keys extracted is noted.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has updated the NDB to set LOAD MODE.
System Action:
Processing continues. If the ALTER is aborted, the NDB remains in LOAD MODE.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing is now deleting any old key records on the NDB.
System Action:
Processing continues. If the ALTER is aborted, the NDB remains in LOAD MODE.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has deleted the old key records. THe number of records deleted is indicated.
System Action:
Processing continues. If the ALTER is aborted, the NDB remains in LOAD MODE.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing is now reloading the key records from the sorted keys. This is a checkpoint message.
System Action:
Processing continues. If the ALTER is aborted, the NDB remains in LOAD MODE.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing is now reloading the key records for the indicated field. This is a checkpoint message.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that a unique key violation for the indicated field/value has occurred during NDB ALTER processing. The indicated field had more than one record with the indicated value.
System Action:
Processing continues. The field is loaded as if not unique. This allows easy correction using NCL procedures. The field is still defined as unique, and no additional records may be added with that value.
User Action:
When the alter completes, use the messages to provide the fields in error. Access and correct the records as appropriate with NCL procedures. Alternatively, update the field definition from KEY=UNIQUE to KEY=YES.
Reason:
This message indicates that NDB ALTER processing has completed loading the key records for the indicated field. This is a checkpoint message. Statistics on the number of unique values, keys, and VSAM records are provided.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has completed loading all key records. The number of keys and VSAM records loaded is indicated. If any unique key violations have occurred, this is noted. (see message N87W21).
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has updated the NDB to reset LOAD MODE.
System Action:
Processing continues. The keys have been rebuilt. LOADMODE is no longer required.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has encountered a field value that is too long to be keyed. The name of the field and the RID of the containing record are displayed.
System Action:
Processing continues until all data has been read. The NDB will not have the keys rebuilt. Only the first 10 violations for each field name are reported.
User Action:
When the ALTER stops (after reading all data), examine the records in error and correct the field values if required. Alternatively, increase the VSAM keylength of the NDB.
Reason:
This message indicates that NDB ALTER processing has updated the key option of the field from NO to YES or UNIQUE.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing is merging the sorted key strings. This is a checkpoint message.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing is performing a string merge. This is a checkpoint message.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing is performing an individual string merge. This is a checkpoint message.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has completed an individual string merge. The statistics show the number of keys in from each string, and out. The number of VSAM blocks is also displayed. This is a checkpoint message.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has completed a merge pass (which halves the number of strings). This is a checkpoint message.
System Action:
Processing continues.
User Action:
None.
Reason:
This message indicates that NDB ALTER processing has completed all string merge processing, resulting in a single complete sorted list of all keys.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is an error message resulting from an NDB ALTER OPT=CHKX command. The details are:
1 - value for field in indicated record is not in the key lists.
2 - value in key list is not in the associated record (field itself is not in record)
3 - value in key list is not in the associated record (field has a different value in record, this will pair with a type 1 error).
4 - data record not found.
other - 1000 + NDBRC rsp from internal record read
The field in error.
The internal field id in hex.
The RID of the data record.
The RID in hex.
This message will be followed by N87W71 and N87W72 messages containing further information.
System Action:
Processing continues.
User Action:
When the NDB ALTER completes, the errors should be investigated.
Reason:
This message is an error message resulting from an NDB ALTER OPT=CHKX command. It follows an N87W70 message and shows the key value keyval in hex.
System Action:
Processing continues.
User Action:
When the NDB ALTER completes, the errors should be investigated.
Reason:
This message is an error message resulting from an NDB ALTER OPT=CHKX command. It follows an N87W70 message and shows the data value in hex.
System Action:
Processing continues.
User Action:
When the NDB ALTER completes, the errors should be investigated.
Reason:
This message is the final message resulting from an NDB ALTER OPT=CHKX command. It shows the number of errors found. If any were found, the NDB is locked.
System Action:
NDB ALTER processing terminates.
User Action:
Check the results of the ALTER.
Reason:
This message is produced from an NDB ALTER command if the work file nominated cannot be used. The error message explains the problem. NDB is locked.
System Action:
NDB ALTER processing terminates.
User Action:
Correct the problem with the work file.
Reason:
This message is produced from an NDB ALTER command if the amount of sort storage requested could not be obtained.
System Action:
NDB ALTER processing terminates.
User Action:
Specify a lesser amount of sort work storage, or increase the region size for SOLVE.
Reason:
This message is produced from an NDB ALTER command if the specific field nominated is not defined on the NDB.
System Action:
NDB ALTER processing terminates.
User Action:
Correct the field name.
Reason:
This message is produced from an NDB ALTER command if the specific field nominated for indexing is already keyed.
System Action:
NDB ALTER processing terminates.
User Action:
Correct the field name. Use the NDB FIELD command to alter the key attributes if required.
Reason:
This message is produced from an NDB ALTER command if keying of a single field is requested, and the NDB is in load mode. It is also produced if OPT=CHKX is entered, and the NDB is in load mode.
System Action:
NDB ALTER processing terminates.
User Action:
The entire NDB must be indexed. Use the DB option on the NDB ALTER OPT=BLDX command.
Reason:
This message is produced from an NDB ALTER command if checking of the indexes for a keyed field is requested, but it is not keyed or is a sequence key.
System Action:
NDB ALTER processing terminates.
User Action:
Correct the NDB ALTER command. It makes no sense to check keys for a non-keyed field.
Reason:
This message is produced from an NDB ALTER command if an error occurs when writing to the work file or the NDB. The VSAM error codes may be checked against the relevent IBM manual. (FDBK=1C means out of space).
System Action:
NDB ALTER processing terminates.
User Action:
Determine the cause of the problem and re-enter the NDB ALTER command.
Reason:
This message is produced from an NDB ALTER command if an error occurs when setting up internal control blocks. No storage is available.
System Action:
NDB ALTER processing terminates.
User Action:
Correct the cause of the storage shortage and reissue the NDB ALTER command.
Reason:
This message is produced from an NDB ALTER command if an error occurs when reading NDB records. There will be a message on the SOLVE log preceding this message informing of the failure reason.
System Action:
NDB ALTER processing terminates.
User Action:
Correct the cause of the read failure and reissue the NDB ALTER command.
Reason:
This message is produced from an NDB ALTER command if field length errors occur (see message N87W25). It indicates that the processing has been aborted because of the errors.
System Action:
NDB ALTER processing terminates.
User Action:
Use an NCL procedure to read the records in error and correct the field values.
Reason:
This message is produced from an NDB ALTER command if an internal NDB I/O error occurs. There should be a message on the activity log describing the error.
System Action:
NDB ALTER processing terminates.
User Action:
Determine the cause of the I/O error.
Reason:
This message is produced from an NDB ALTER command if it is terminated by the entering of and NDB STOP dbname IMM command.
System Action:
NDB ALTER processing terminates.
User Action:
Confirm that the ALTER was to be stopped. If not, reissue the NDB ALTER command.
Reason:
AN NDB module has detected an internal ABEND condition related to NDB corruption. Diagnostic information follows.
The NDB name, and an abend code are displayed.
System Action:
The NDB may stop.
User Action:
Report the ABEND condition to you product support representative.
Reason:
This message follows message N87X90 and provides a descriptive reason for the NDB ABEND.
System Action:
See message N87X90.
User Action:
See message N87X90.
Reason:
This message follows message N87X90 and provides more information about the NDB request in progress at the time of the NDB ABEND.
System Action:
Refer to message N87X90.
User Action:
Refer to message N87X90.
Reason:
This message follows message N87X90 and provides additional debugging information.
System Action:
refer to message N87X90.
User Action:
Refer to message N87X90.
Reason:
This message provides additional information following an NDB ABEND. It is a heading for a hex/character dump produced in the following N87X95 messages.
System Action:
See message N87X90.
User Action:
See message N87X90.
Reason:
This message produces additional debugging information about and NDB ABEND. The area being dumped (in HEX and character) is titled by the preceding N87X94 message.
System Action:
See message N87X90.
User Action:
See message N87X90.
Reason:
This message produces additional NDB ABEND debug information. It is a title message for a dump of an NDB I/O area. Messages N87X97 and N87X98 will follow, containing hex and character dumps of the I/O area key and data areas.
System Action:
Refer to message N87X90.
User Action:
Refer to message N87X90.
Reason:
This message follows message N87X96 and is a hex and character dump of an NDB I/O area key area.
System Action:
Refer to message N87X90.
User Action:
Refer to message N87X90.
Reason:
This message follows message(s) N87X97 and is a hex and character dump of an NDB I/O area data area.
System Action:
Refer to message N87X90.
User Action:
Refer to message N87X90.
Reason:
This message is produced by an NDB request on dbname when the TRACE option is in effect in the NDB START command. The column meanings are:
The NDB the request is for.
The NDB request code.
The response code from the request (0=success).
The recordid this request was for.
The time taken to process this request in seconds.
The number of records accessed in processing this request.
The internal Database ID.
The nclid of the NCL procedure making the request.
The procedure name of the NCL procedure making the request.
The statement number within the procedure of the request.
System Action:
None.
User Action:
None.
Reason:
This message is issued when a database starts a subthread to handle asynchronous database commands, for example, &NDBSCAN.
System Action:
The subthread commences processing.
User Action:
None.
Reason:
This message is issued when a database subthread finds no more pending work, and the number of started subthreads for this database is above the NDBSUBMN value. The thread terminates.
System Action:
The subthread terminates.
User Action:
None.
Reason:
An internal error occurred while processing a panel.
System Action:
The panel fails.
User Action:
Report the error to your support representative.
Reason:
Refer to the description if N88801
System Action:
Refer to the description of N88801.
User Action:
Refer to the description of N88801.
Reason:
Refer to the description of N88801.
System Action:
Refer to the description of N88801.
User Action:
Refer to the description of N88801.
Reason:
Refer to the description of N88801.
System Action:
Refer to the description of N88801.
User Action:
Refer to the description of N88801.
Reason:
NCL/EF requires a SOLVE version more current than this SOLVE system. NCL/EF cannot initialize.
System Action:
NCL/EF is not available.
User Action:
Check that the correct load libraries are specified in the SOLVE JCL. Contact your product support representative.
Reason:
The SYSPARMS NDBPHONX command failed. The reason that the exit could not be loaded is displayed.
System Action:
NO NDBPHONX is available.
User Action:
Determine the reason for the load failure and retry the command.
Reason:
This message is produced in response to the SHOW NDB command if there are no NDB databases currently active, stopping, or locked.
System Action:
None.
User Action:
None.
Reason:
This message is produced in response to the SHOW NDB command if there are any NDB databases currently active, stopping, or locked. The number of databases in each status is shown.
System Action:
None.
User Action:
None.
Reason:
This message is in response to the SHOW NDB=<ALL | dbname> command and labels the columns displayed for each database. The column headings are:
The name of the database.
The status of the database:
The database is initializing.
The database is currently active.
The database is stopping.
The database is active, but an NDB STOP command has set a pending stop. It will stop when all users sign off it.
An NDB command with the LOCK option was entered. The database is locked from all access.
An error occurred on the database (eg: I/O error), and the database manager has stopped and locked it.
The number of pending DB commands and requests.
The following values may be displayed in this field:
The number of signed-on users.
A single user is signed-on with the EXCLUSIVE option.
The database is currently being unloaded by an NDB UNLOAD command.
The database index is currently being (re)building or validating by an NDB ALTER command.
The number of database commands processed since starting.
The current number of subthreads active.
The number of requests queued to subthreads.
Whether the database was started in DEFER status (highlighted YES) or not (NO).
The number of blocks in the transaction journal.
The highest used block number in the transaction journal.
The status of TRACE (T), SCANDEBUG (S), INPUT (I), LOADMODE (L), JOURNAL (J), and RIDREUSE (R).
The value of each is either N (No) or Y (Yes), with the exception of RIDREUSE (R), which has the following statuses:
RID reuse is not possible on the NDB (reclen too short).
RID reuse is possible but not enabled.
RID reuse is enabled and active.
RID reuse is enabled and active, and the collection of reuseable RIDs is in progress.
System Action:
None.
User Action:
None.
Reason:
This message follows the N89503 message for each database. Refer to N89503 for the column descriptions.
System Action:
None.
User Action:
None.
Reason:
This message terminates a multi-line display of NDB databases or VARTABLES.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the database on a SHOW NDB=dbname command was not found in the list of currently active, starting, stopping, or locked databases.
System Action:
None.
User Action:
Check that the database name was correctly spelled. If so, the database could be stopped (but not locked). Stopped databases do not display.
Reason:
This message is a header message for the following list of messages, the response to a SHOW NDBUSER command. The columns are:
The name of the database.
The user id of a signed on database user.
The LU (terminal) the user is logged on from.
The highest-level NCL procedure in the NCL process using the database.
The NCLID of the NCL process.
System Action:
None. The user list follows.
User Action:
None.
Reason:
This message is produced for each signed on user to each database, in response to the SHOW NDBUSER command. The columns are described in the N89507 description. If the user has opened as an EXCLUSIVE user, that is indicated by the text (EXCLUSIVE).
System Action:
None.
User Action:
None.
Reason:
Insufficient working storage was available to process the NDB command.
System Action:
The command is not processed.
User Action:
Determine the reason for the storage shortage.
Reason:
This message indicates that the entered NDB command had no syntax errors, and processing has commenced.
System Action:
The command is being processed.
User Action:
Wait for the N89703 message to indicate the results of the command.
Reason:
This message indicates the completion of processing for the entered NDB command. The response code (RC) is displayed.
System Action:
The command is complete.
User Action:
Your action depends on the displayed response code. For more information about NDB response codes, enter /NDBERR.
Reason:
The LANG operand of an NDB CREATE command has specified a language code that is unrecognized.
System Action:
The NDB CREATE is rejected.
User Action:
Correct the value specified on the LANG operand to supply a valid two character language code.
Reason:
An &NDBxxx statement refers to an NDB that has not been successfully opened.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An &NDBOPEN statement refers to an NDB that has already been successfully opened.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An &NDBxxx END statement refers to an NDB for which no START/DATA/END set is currently in progress.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An &NDBxxx START statement refers to an NDB for which a START/DATA/END set is already in progress.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An &NDBxxx DATA or END statement contains a keyword which is only valid on an NDBxxx START, or single-line DATA statement.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An &NDBCTL command has an invalid time zone value specified.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An &NDBxxx statement has received an error response from the database manager.
System Action:
The NCL procedure is terminated.
User Action:
If you wish to retain control after an error, use &NDBCTL ERROR=CONTINUE.
Reason:
An &NDBxxx START/DATA/END set had no data statements.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An MDS error occured for the MDO specified on an &NDBGET NCL statement.
System Action:
MDS retcode and fdbk are set and the &NDBGET fails.
User Action:
Ensure the MDO specified can be correctly mapped.
Reason:
An &NDBOPEN statement was executed for an NDB that was already open.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure, or, if you wish to retain control after this error, use &NDBCTL ERROR=CONTINUE.
Reason:
An &NDBCLOSE statement was executed for an NDB that is not open.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure, or, if you wish to retain control after this error, use &NDBCTL ERROR=CONTINUE.
Reason:
An assignment statement using the &NDBQUOTE builtin function had more than one parameter specified.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure. &NDBQUOTE may only have one parameter.
Reason:
The data supplied to the &NDBQUOTE builtin function was longer than 256 characters.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The data supplied to the &NDBQUOTE builtin function was longer than 254 characters, or an excessive number of embedded quotes would have made the resulting quoted data longer than 256 characters. Since only 256 characters can be stored in a variable, the addition of a leading and trailing quote and/or doubling up embedded quotes would have made it too long.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The &NDBPHON NCL builtin function requires the conversion type to be specified. In must be either SOUNDEX or USER.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The &NDBPHON NCL builtin function can only perform USER phonetic processing if a phonetic exit has been activated.
System Action:
The NCL procedure is terminated.
User Action:
Use the SYSPARMS NDBPHONX command to load the user phonetic exit.
Reason:
The &NDBPHON NCL builtin function requires the conversion type to be specified. In must be either SOUNDEX or USER.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The &NDBPHON NCL builtin function exit returned a non-zero return code in register 15. The value is displayed.
System Action:
The NCL procedure is terminated.
User Action:
Determine the reason for the non-zero return code.
Reason:
This message indicates that an OML NDB_ERROR has been raised.
System Action:
An OML NDB_ERROR condition is raised.
User Action:
Examine the NDB error code and correct the procedure if required.
Reason:
An NDB OPEN verb was requested for an NDB that this process has already opened.
System Action:
An error may be raised.
User Action:
Examine the NDB error code and correct the procedure if required.
Reason:
An NDB CLOSE verb was requested for an NDB that this process has not yet opened.
System Action:
An error may be raised.
User Action:
Examine the NDB error code and correct the procedure if required.
Reason:
An NDB verb that uses START/DATA/END had an END option when no START was issued.
System Action:
An error may be raised.
User Action:
Examine the procedure source for a logic error.
Reason:
An NDB verb that uses START/DATA/END had an END option but no data had been provided by DATA options.
System Action:
An error may be raised.
User Action:
Examine the procedure source for a logic error.
Reason:
An NDB verb that uses START/DATA/END had a START option when it was already STARTed.
System Action:
An error may be raised.
User Action:
Examine the procedure source for a logic error.
Reason:
An NDB verb that uses START/DATA/END had other options specified with a DATA or END option when a previous START was issued.
System Action:
An error may be raised.
User Action:
Examine the procedure source for a logic error.
Reason:
An NDB verb that requires data to be provided (using the DATA operand) had no data specified.
System Action:
An error may be raised.
User Action:
Examine the procedure source for a logic error.
Reason:
An NDB ADD or UPDATE verb had a FORMAT operand specified inside a START..END sequence.
System Action:
An error may be raised.
User Action:
Examine the procedure source for a logic error.
Reason:
An NDB verb had required operands omitted. For NDB UPDATE, no RID was provuded. For NDB FORMAT, either the OPT or FORMAT operands were omitted.
System Action:
An error may be raised.
User Action:
Examine the procedure source for a logic error.
Reason:
An MDS error occured while processing the MDO operand of an NDB GET statement.
System Action:
NDB GET statement processing is terminated.
User Action:
Ensure the MDO operand specifies an MDO which can be correctly mapped.
Reason:
No NDB phonetic exit has been set.
The NDBPHON function 'USER' option
System Action:
An error is raised.
User Action:
Use the NDBPHONX SYSPARM to set the exit name.
Reason:
An NDB phonetic exit returned a non-zero return code in R15.
System Action:
An error is raised.
User Action:
Examine the exit to determine the reason for the return code.
Reason:
An error occurred while trying to initialize the journal dataset. aaaaaaaa is the DD name of the dataset. The reason is shown in the message.
System Action:
NDB Journaling is terminated.
User Action:
Check the system journal dataset definitions. The NDB which caused journaling to start or swap will need to be unlocked.
Reason:
A JOURNAL SWAP command was issued, but no NDBs which require journaling have been started.
System Action:
The SWAP command is not processed.
User Action:
None.
Reason:
A JOURNAL SWAP operation occurred and the system attempted to start the journal procedure, however the procedure failed due to insufficient storage.
System Action:
none.
User Action:
Attempt to start the JOURNAL procedure manually to ensure that journal processing occurs.
Reason:
This message is issued in response to a JOURNAL SWAP command to verify that the command has been accepted.
System Action:
N/A
User Action:
N/A
Reason:
This message is issued when a JOURNAL SWAP command has been successfully completed.
System Action:
N/A
User Action:
N/A
Reason:
This message indicates that a JOURNAL SWAP command was unsuccessful.
System Action:
NDB journaling is unavailable.
User Action:
The reason will be displayed in message N89L01. Determine the reason for failure and correct the problem. The system will attempt to open the journal dataset again next time a journaled NDB is started.
Reason:
During EDBS initialization, it was determined that the EDBS load module was incompatible with the product version.
System Action:
EDBS feature is not available.
User Action:
Determine the cause for the incompatibility. This release of EDBS requires version 2.2 or higher of the SOLVE foundation. This message indicates that either the SOLVE foundation or the EDBS feature is not properly installed.
Reason:
This message is displayed in response to SH EDB command; i is the number of external databases defined for SOLVE and j is the number of external databases currently stopped.
System Action:
None.
User Action:
None.
Reason:
The heading displayed in response to SH EDB={ALL|dbname} command. This information is used to determine how the database was defined and the current status of the database connection.
System Action:
None.
User Action:
None.
Reason:
A detail line displayed in response to the SHOW EDB={ALL|dbname} command. The fields are as follows:
The external ID of the database.
The type of external database.
The internal ID of the database. Used in NCL procedures to reference the database.
he current status of the connection to the external database. The following values are possible:
ABEND - The external database connection is inactive. The CAF manager has abended.
ACTIVE - The external database connection is active. NCL procedures can communicate with the external database.
ATTACH - The external database connection is inactive. The CAF manager did not attach.
DOWN - The external database connection has been started but the database is unavailable. When the database becomes available,the connection will be activated automatically.
ERROR - The external database connection is inactive. An error condition was detected by the database.
FORCED - The external database connection is inactive. The system operator issued an EDB STOP command with FORCE operand.
NOLOAD - The external database connection is inactive. The interface load modules failed to load.
NOSTART - The external database connection is inactive. The NOSTART operand was specified on the EDB DEFINE command or some other DB2 system is currently ACTIVE
NOTDEF - The external database connection is inactive. It is not known to the operating system.
STOPPED - The external database connection is inactive. The system operator issued an EDB STOP command.
The maximum number of subtasks that can be attached by the CAF manager. That is, the maximum number of NCL procedures that can simultaneously communicate with the database.
The number of subtasks in a pool of tasks, waiting for an NCL procedure to request a database connection. These tasks will be allocated to NCL procedures as required.
The number of free subtasks in the pool.
The number of active subtasks.
System Action:
None.
User Action:
The appropriate action can be taken, depending on the status of the external database connections.
Reason:
This message is displayed in response to a SHOW EDB= dbname command if the database dbname is not defined to SOLVE.
System Action:
None.
User Action:
Define the database or re-enter the SHOW EDB= dbname command with the correct dbname.
Reason:
The heading displayed in response to SHOW EDBUSER command.
System Action:
None.
User Action:
None.
Reason:
A detail line displayed in response to the SHOW EDBUSER command. This message displays user information for each open external database connection from NCL. The fields are as follows:
The external ID of the database.
The type of the database.
The id by which NCL procedures know the external database i.e. the internal ID.
The ID of the user that started the NCL procedure that is communicating with the external database.
The user's LU name (logical unit name).
The name of the NCL procedure that is communicating with the external database.
The ID of NCL procedure that is communicating with the external database.
System Action:
None.
User Action:
None.
Reason:
The heading displayed in response to SHOW EDBSTAT command.
System Action:
None.
User Action:
None.
Reason:
A detail line displayed in response to the SHOW EDBSTATS command. This message displays statistical information for each external database connection. The fields are as follows:
The external ID of the database.
The type of the database.
The id by which NCL procedures knows the database i.e. the internal ID.
The number of &SQL and/or &EDB requests processed that resulted in communications with the external database.
The total elapsed time consumed by the external database.
The average response time of the database.
The total elapsed time taken to execute all requests (SOLVE's time plus database time).
The average response time to the user.
All time values are displayed in seconds.
System Action:
None.
User Action:
None.
Reason:
The heading displayed in response to SHOW EDBUSTAT command.
System Action:
None.
User Action:
None.
Reason:
A detail line displayed in response to the SHOW EDBUSTAT command. This message displays statistical information for each user attached to an open external database connection. Statistics are collected only if the external database was started with the STATS operand. The fields are as follows:
The ID by which NCL procedures know the database.
The ID of the executing the NCL procedure that is communicating with the external database.
The ID of the NCL procedure that is communicating with the external database.
The number of &SQL and &EDB requests executed.
The number of &SQL and &EDB requests executed that required communications with the external database.
The total elapsed time consumed by the external database to execute &SQL and &EDB requests.
The average response time of the database.
The total elapsed time taken to execute all requests (SOLVE's time plus database time).
The average response time to the user.
All time values are displayed in seconds.
System Action:
None.
User Action:
None.
Reason:
EDB cmdname command request has been accepted.
System Action:
Processing of the command commences.
User Action:
None.
Reason:
An attempt was made to redefine database dbname.
System Action:
Request is not performed.
User Action:
Delete database definition before issuing EDB DEFINE again.
Reason:
An attempt was made to define database dbname with either a database ID matching the external ID of an already defined database or the database ID is matching the internal ID of already defined database.
System Action:
Request is not performed.
User Action:
Change the name or the ID of the database.
Reason:
An attempt was made to issue an EDB command request but no definition for database dbname exists.
System Action:
Request is not performed.
User Action:
If the dbname was incorrectly specified, re-issue the command with the correct dbname. Alternately define the database dbname.
Reason:
An attempt was made to define a database, but the MAXTASK and/or MINTASK specified on the EDB DEFINE command are incorrect.
System Action:
Request is not performed.
User Action:
Re-issue the command with the correct MAXTASK and/or MINTASK.
Reason:
An attempt was made to define a database but TYPE operand specified a database type that is not supported by this release of EDBS.
System Action:
Request is not performed.
User Action:
Re-issue the command with the correct type.
Reason:
Informs the user that dbname database was successfully defined for SOLVE.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to cancel the connection between an NCL procedure and the database, but the NCL procedure was not communicating with the database.
System Action:
Request is not performed.
User Action:
Re-issue the command with correct NCLID.
Reason:
An attempt was made to delete an external database connection that has not been stopped.
System Action:
Request is not performed.
User Action:
Stop the database connection, then re-issue the EDB DELETE command.
Reason:
The EDB command failed due to system storage shortage.
System Action:
Request is not performed.
User Action:
Investigate SOLVE's use of storage.
Reason:
An attempt was made to issue EDB CANCEL command with FORCE option and a subtask associated with specified NCLID could not be found.
System Action:
Request is not performed.
User Action:
Check if connection between the NCL procedure and the database is still active.
Reason:
Informs the user that DB2's modules DSNALI, DSNHLI2 and DSNTIAR were successfully loaded.
System Action:
None.
User Action:
None.
Reason:
Informs the user that the module modname failed to load.
System Action:
The database connection is not started.
User Action:
Investigate the reasons for load failure.
Reason:
Informs the user that the connection to the external database dbname is ACTIVE.
System Action:
None.
User Action:
None.
Reason:
Informs the user that the EDBS has failed to attach the CAF management subtask for external database dbname.
System Action:
Database connection is not started.
User Action:
Refer to the SOLVE's job log for attach failure reasons.
Reason:
Informs the user that the SOLVE connection to the external database dbname failed. The type and code are the abend type and abend code returned by the system.
System Action:
The database connection is not active.
User Action:
Refer to the relevant system manual for an explanation of abend codes.
Reason:
Informs the user that the SOLVE connection to the external database dbname was stopped.
System Action:
None.
User Action:
None.
Reason:
Informs the user that the definition for the external database dbname was deleted.
System Action:
None.
User Action:
None.
Reason:
Informs the user that the SOLVE connection to the external database dbname is down.
System Action:
When the database becomes available, the connection is activated automatically.
User Action:
Investigate the reasons for the external database being inactive.
Reason:
Informs the user that the connection to the external database dbname is ACTIVE.
System Action:
Connection between SOLVE and the external database is established.
User Action:
None.
Reason:
An attempt was made to start an external database connection that was already started.
System Action:
None.
User Action:
If the dbname was incorrectly specified,re-issue the command with the correct dbname.
Reason:
An attempt was made to stop an external database connection that was already inactive.
System Action:
None.
User Action:
If the dbname was incorrectly specified,re-issue the command with the correct dbname.
Reason:
An attempt was made to delete an external database connection that is ACTIVE.
System Action:
None.
User Action:
Stop the database connection, then re-issue the command.
Reason:
Informs the user that the EDBS CAF manager for the external database dbname has abended. The type and code are the abend type and abend code returned by the system.
System Action:
Database connection is terminated.
User Action:
Refer to the relevant system manual for an explanation of abend codes.
Reason:
Informs the user that the connection to the external database dbname was stopped. The system operator issued an EDB STOP request with the FORCE operand. This means that all open NCL connections are force-detached; all transactions in progress will be backed out by the database.
System Action:
Database connection is terminated.
User Action:
None.
Reason:
Informs the user that the connection to the external database dbname is in a shutdown state. The system operator issued an EDB STOP request with QUIESCE operand. This means that the connection is stopped after all NCL processes finish database access.
System Action:
Stops the connection to the external database after all NCL procedures close their connections. New connections by NCL procedures are not allowed.
User Action:
None.
Reason:
Informs the user that the connection to the external database dbname has failed. The rc and reason are return and reason codes from the database.
System Action:
Database connection is not activated.
User Action:
Refer to the relevant database manual for an explanation of return and reason codes.
Reason:
An attempt was made to connect SOLVE to multiple DB2 databases. This is not allowed due to IBM restriction of an address space being able to connect only to one DB2 database via CAF at any one time.
System Action:
Request is not performed.
User Action:
Terminate other DB2 connection and re-issue the command.
Reason:
Informs the user that the request specified on &EDB or &SQL verb was invalid.
System Action:
The NCL procedure terminates.
User Action:
Correct the NCL procedure.
Reason:
Informs the user that the database ID specified on an &EDB or &SQL verb was invalid.
System Action:
NCL procedure terminates.
User Action:
Correct the NCL procedure.
Reason:
Informs the user that return code from an &EDB or &SQL verb was greater than 99.
System Action:
NCL procedure terminates.
User Action:
Report the problem to your product support representative.
Reason:
Informs the user that the syntax of an &EDB or &SQL verb was incorrect.
System Action:
NCL procedure terminates.
User Action:
Correct the NCL procedure.
Reason:
Informs the user that communication between NCL procedure and the external database failed.
System Action:
NCL procedure terminates.
User Action:
Report the problem to your product support representative.
Reason:
Informs the user that an &EDB or &SQL request failed due to system storage shortage.
System Action:
NCL procedure terminates.
User Action:
Investigate storage usage by SOLVE.
Reason:
This message is returned in the &ZSQLERRM0 variable after the execution of &EDB INFO request. The message contains an explanation of the error code available in &ZSQLCODE.
System Action:
None.
User Action:
See &ZSQLCODE in the chapter titled System Variable Descriptions.
Reason:
This message is returned in the &ZSQLERRM1 variable after the execution of an &EDB INFO request. The message contains the name of the module that detected the SQL error available in &ZSQLCODE variable.
System Action:
None.
User Action:
None.
Reason:
The NAME parameter on the &SQLFMT verb is missing or invalid.
System Action:
NCL procedure terminates.
User Action:
Correct the NCL procedure.
Reason:
The syntax of the &SQLFMT verb is invalid.
System Action:
NCL procedure terminates.
User Action:
Correct the NCL procedure.
Reason:
The NCL procedure tried to define a format, using the &SQLFMT verb, and the format already exists.
System Action:
NCL procedure terminates.
User Action:
Correct the NCL procedure.
Reason:
The NCL procedure tried to use a format, using the &SQLFMT verb, and the format has not been defined.
System Action:
NCL procedure terminates.
User Action:
Correct the NCL procedure. Use the &SQLFMT verb to define the format.
Reason:
The execution of the &SQLFMT verb failed due to system storage shortage.
System Action:
NCL procedure terminates.
User Action:
Investigate the reason for system storage shortage.
| Copyright © 2012 CA. All rights reserved. |
|