Reason:
A process has been unable to obtain storage.
System Action:
The process is terminated.
User Action:
Retry the request. If the problem persists notify your installations help desk facility.
Reason:
During formatted dump processing, an attempt was made to load the module identified in the message failed. The reason code refers to the BLDL and/or LOAD macro. This is normally due to insufficient storage.
System Action:
Formatted dump processing continues with the next report.
User Action:
Refer to the descriptions and return codes associated with the LOAD and BLDL macros in publications for the relevant operating system.
Reason:
Identifies the last line of a formatted dump.
System Action:
None, for information only.
User Action:
None, for information only.
Reason:
An abend occurred during formatted dump processing, the module and abend code are identified in the message. The particular formatted dump report is incomplete.
System Action:
Formatted dump processing continues with the next report.
User Action:
Ascertain the cause of the (original) formatted dump which may be related. Contact your product support representative.
Reason:
An internal error has occurred in the module identified in the message. The reason code further clarifies the type of abend. A full list of internal abend codes may be obtained using the CAS : Message Definition menu. All internal abend codes are prefixed by $ABEND ie. $ABENDxxx-yy.
System Action:
A formatted dump and a system dump are normally produced.
User Action:
Use the internal abend code to obtain the cause and description of the internal abend. If the problem cannot be easily diagnosed, refer the problem to your product support representative.
Reason:
The VSMLIST macro returned retcode nn. This return code was deemed to represent an error condition.
System Action:
Processing terminates.
User Action:
Refer to the discussion of VSMLIST in the SPL: System macros and Facilities Volume 2 manual for a description of the return code.
Reason:
The workarea for VSMLIST to place data into was not available.
System Action:
Processing terminates.
User Action:
The workarea address is found at symbol XCUSHONA within the GVT. If the word at this address is zero then this error condition is encountered.
Reason:
The VSMLIST macro did not return any subpool information to process.
System Action:
Processing terminates.
User Action:
None.
Reason:
This message is an underline for messages N93806 and N93809
System Action:
None.
User Action:
None.
Reason:
This message is an underline for messages N93807 and N93810
System Action:
None.
User Action:
None.
Reason:
This is the title line for a SH SUBPOOL detailed request where :
SP# : Subpool number
KEY : Storage key within subpool
TYPE : Storage type (CSA/SQA/LSQA/PVT)
TCB- ADDR : The TCB address of the owner (when TYPE=PVT)
BLK-ADDR : The starting address of the storage block
BLK-SIZE : The size of the block
FREE-ADDR : The starting address of free space within a block
FREE-SIZE : The size of the free space
System Action:
None.
User Action:
None.
Reason:
This is the title line for a SH SUBPOOL detailed request where :
SP# : Subpool number
KEY : Storage key within subpool
TYPE : Storage type (CSA/SQA/LSQA/PVT)
TCB- ADDR : The TCB address of the owner (when TYPE=PVT)
TOTAL : The total storage for key 'key' in subpool 'sp#'
FREE : The total free storage for key 'key' in subpool 'sp#'
% FREE : The percentage of free storage
System Action:
None.
User Action:
None.
Reason:
This is a total line for a detailed list where :
aaa : The subpool number the total is for
b : The storage key the total is for
cccc : The storage type (CSA/SQA/LSQA/PVT)
ddddddK : The total allocated storage
eeeeeeK : The total free storage
System Action:
None.
User Action:
None.
Reason:
This is a total line for a summary list where :
aaaa : The storage type (CSA/SQA/LSQA/PVT)
bbbbbbK : The total storage
ccccccK : The total free
nn% : The percentage of free storage within total
System Action:
None.
User Action:
None.
Reason:
This is the data line from a SH SUBPOOL=nnn request where :
aaa : Subpool number
b : Storage key within subpool
cccc : Storage type (CSA/SQA/LSQA/PVT)
dddddddd : The TCB address of the owner (when cccc=PVT)
eeeeeeee : The starting address of the storage block
ffffffff : The size of the block
gggggggg : The starting address of free space within a block
hhhhhhhh : The size of the free space
System Action:
None.
User Action:
None.
Reason:
Both the EASINET and Menu options were specified on the LOGON command. The Menu option has been ignored.
System Action:
Invokes EASINET processing.
User Action:
Varies depending on EASINET action for your installation.
Reason:
To connect to a product region the TSO interface module must open one of the NMTSOnnn ACBs. This open failed. The ACBERFLG value X'nn' is the VTAM error code associated with this failure.
System Action:
The request is ignored.
User Action:
Correct and retry.
Reason:
All of the TSO interface ACB's are in use.
System Action:
The request is ignored.
User Action:
A maximum of 999 ACB's (VTAM APPLS) of the form NMTSOnnn can be defined. If more concurrent TSO interface sessions are to be supported then extra VTAM APPL statements should be defined.
Reason:
The LU requested on the NMLOGON command is unknown or in use.
System Action:
The request is rejected.
User Action:
Retry specifying another LU.
Reason:
The VTAM SETLOGON macro failed.
System Action:
This message will be followed by message N95099 giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
The VTAM REQSESS macro failed.
System Action:
This message will be followed by message N95099 giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
The VTAM OPNSEC macro failed.
System Action:
This message will be followed by message N95099 giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
The user has attempted to invoke the TSO interface from a terminal other than a display terminal.
System Action:
The request is rejected.
User Action:
Use a 3270 type display terminal.
Reason:
The VTAM NSEXIT was driven during establishment of the session with SOLVE.
System Action:
Processing of the TSO interface is terminated.
User Action:
This condition may indicate that the product has not been correctly installed. A VTAM buffer trace may aid in problem determination.
Reason:
The requested SOLVE VTAM APPL (application) is not defined to VTAM.
System Action:
The request is rejected.
User Action:
Validate that the APPL you requested has been varied active to VTAM. The APPL name applname may be the default APPL name of NM or it may be one you have specified incorrectly in the APPL parameter of the NMLOGON command.
Reason:
The requested SOLVE system is not executing.
System Action:
The request is rejected.
User Action:
Validate that the APPL you requested is correct. If the APPL parameter was not specified in the TSO interface request the default VTAM APPL name of NM will be used.
Reason:
The VTAM GENCB macro failed.
System Action:
The TSO interface request has failed.
User Action:
See the VTAM Programming Manual for a description of these register return codes.
Reason:
A call to IKJPARS has returned a non zero return code nn in register 15.
System Action:
The TSO interface request has failed.
User Action:
This may indicate an incompatibility with your system. Refer this to your systems administrator.
Reason:
The TSO interface will only function with an SOLVE that is licensed for the External Interface Package (EIP) feature. This message will also appear if the user tries to logon to an application other than SOLVE.
System Action:
The request fails.
User Action:
If the logon attempt was to SOLVE, then your system is not licensed for this facility. Contact your product support representative.
Reason:
The session with SOLVE has failed.
System Action:
Processing of the TSO interface is terminated.
User Action:
Refer to preceding messages for determination of the problem.
Reason:
The requested SOLVE system is inactive or not accepting logons.
System Action:
The request is rejected.
User Action:
Determine the status of the required SOLVE system and retry when it available.
Reason:
This message is preceded by a message giving broad details of the error. This message supplies specific information to use in problem determination.
System Action:
The associated request has failed.
User Action:
Using the error codes above refer to the VTAM Programming Manual for the reasons for the failure. Correct the error and retry.
Reason:
The VTAM SEND macro failed.
System Action:
This message will be followed by message N95199 giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
The VTAM RECEIVE macro failed.
System Action:
This message will be followed by message N95199 giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
An error occurred on a TGET macro. The code shown is that returned in register 15.
System Action:
Processing of the TSO interface is terminated.
User Action:
Interpret the return code and correct the error.
Reason:
An error occurred on a TPUT macro. The code shown is that returned in register 15.
System Action:
Processing of the TSO interface is terminated.
User Action:
Interpret the return code and correct the error.
Reason:
The amount of data presented to the TSO interface from the TSO screen exceeded the internal buffer size.
System Action:
The request is rejected.
User Action:
Report this error to your product support representative.
Reason:
A chained message should not be received from SOLVE.
System Action:
Processing of the TSO interface is terminated.
User Action:
This is an internal error. Report it to your product support representative.
Reason:
The amount of data received by the TSO interface from SOLVE exceeds the internal buffer size.
System Action:
Processing of the TSO interface is terminated.
User Action:
This is an internal error. Report it to your product support representative.
Reason:
The VTAM MODCB macro has failed.
System Action:
This message will be followed by message N95199 giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
An error occurred on a TPUT macro. The code shown is that returned in register 15.
System Action:
Processing of the TSO interface is terminated.
User Action:
Interpret the return code and correct the error.
Reason:
This message is preceded by a message giving broad details of the error. This message supplies specific information to use in problem determination.
System Action:
The associated request has failed.
User Action:
Using the error codes above refer to the VTAM Programming Manual for the reasons for the failure. Correct the error and retry.
Reason:
A storage request failed with the specified value in Register 15.
System Action:
Processing of the TSO interface is terminated.
User Action:
Determine the cause of the error.
Reason:
A call to IKJPARS has returned a non zero return code nn in register 15.
System Action:
The TSO interface request has failed.
User Action:
This may indicate an incompatibility with your system. Refer this to your systems administrator.
Reason:
A call to IKJSCAN has returned a non zero return code xx in register 15.
System Action:
The TSO interface request has failed.
User Action:
This may indicate an incompatibility with your system. Refer this to your systems administrator.
Reason:
A PUTGET macro has returned a return code greater than 4 in register 15.
System Action:
Processing of the TSO interface is terminated.
User Action:
Refer to the TSO Guide to Writing a TMP or CP for explanation of the contents of R15.
Reason:
The command entered was not a valid command name.
System Action:
The command is rejected.
User Action:
Check that the command name was not longer than 8 characters, and did not contain invalid characters. Correct and retry.
Reason:
The procedure being processed via the NMCMD interface is in all probability looping, or has been flushed.
System Action:
Processing of the TSO interface is terminated.
User Action:
Determine the cause of the error and retry. The activity log may contain a reason for the failure.
Reason:
This is a help message issued to assist the user.
System Action:
None.
User Action:
Enter a valid NMCMD subcommand.
Reason:
An error has occurred whilst performing processing associated with the function code as described.
System Action:
Processing of the TSO interface is terminated.
User Action:
An associated message is issued to provide more precise details of the reason for failure.
Reason:
An attempted logon to SOLVE using NMCMD failed.
System Action:
Processing is terminated.
User Action:
Refer to the SOLVE log for details regarding this error.
Reason:
The panel that was received was not in the expected format.
System Action:
NMCMD processing terminates.
User Action:
Verify that the procedures and panels required for NMCMD processing have been installed correctly.
Refer to the activity log for further details of the error associated with this request.
Reason:
An internal error has occurred in the 3270 virtual interface.
System Action:
The command is rejected.
User Action:
Verify that the procedures and panels required for NMCMD processing have been installed correctly. Ensure sufficient input fields are available on the panel for the specified request. Refer to the SOLVE log for further details of the error associated with this requested. If the problem persists report it to your product support representative.
Reason:
The MAXRC command did not specify an operand that was in the range 0-99.
System Action:
The command is rejected, and MAXRC is reset to the default value of 8.
User Action:
Re-enter the command specifying a number in the range 0-99. NMCMD processing will be terminated if a SOLVE procedure invoked by an NMCMD subcommand sets a return code greater than or equal to the last value set by the MAXRC command.
Reason:
The SOLVE procedure invoked by an NMCMD subcommand has set a return code greater than or equal to the value specified by the MAXRC command.
System Action:
Processing of the TSO interface is terminated.
User Action:
None.
Reason:
An error was encountered when executing the TSO STACK macro. The return code rc was returned in R15. Refer to the TSO Guide to Writing a TMP or CP for details on the meaning of the return code.
System Action:
Processing of the TSO interface is terminated.
User Action:
Refer the problem to your systems administrator.
Reason:
During processing of the READ sub-command of NMCMD an attempt was made to open the input file (specified by the INDD parameter when NMCMD is invoked). The open failed.
System Action:
Processing of the TSO interface is terminated.
User Action:
Check whether the file is available or refer the problem to your systems administrator.
Reason:
An error occurred on execution of the TSO GETLINE macro. The return code was returned in R15. Refer to the TSO Guide to Writing a TMP or CP for details of the return code meaning.
System Action:
Processing of the TSO interface is terminated.
User Action:
Refer the problem to your systems administrator.
Reason:
Commands prefixed by FTS are passed to an FTS sub-command processor. The command entered is unknown to this processor.
System Action:
The command is rejected.
User Action:
Determine the correct FTS sub-command and retry.
Reason:
A call to IKJPARS has returned a non zero return code nn in register 15.
System Action:
NMCMD processing terminates.
User Action:
This may indicate an incompatibility with your system. Refer this to your systems administrator.
Reason:
A value of '*' was specified for an FTS sub-command keyword indicating that the data for this operand should be extracted from the stored FTS definition, but the copy keyword was not entered.
System Action:
The Command is rejected.
User Action:
Supply full details or specify the COPY keyword.
Reason:
If either FRVOL or FRUNT is specified then the other must also be specified. Neither should be specified if FRDSN refers to a cataloged dataset.
System Action:
The request is rejected.
User Action:
Determine the requirements of the request and retry.
Reason:
SYSOUT has been requested as the TODSN for an FTS transmission, it is invalid to specify other operands as explained in this message.
System Action:
The request is rejected.
User Action:
Determine the requirements of the request and retry.
Reason:
The operands TOVOL, TOUNT and TOSPC are invalid for a request that does not specify TODSP (NEW or REP).
System Action:
The request is ignored.
User Action:
Correct and retry.
Reason:
Specifying TIMCO(Y) requests an FTS imagecopy which dictates that the dataset attributes of the TODSN dataset will be copied from the FRDSN dataset and so dataset attributes must not be supplied.
System Action:
The request is rejected.
User Action:
Determine the requirements of the request and retry.
Reason:
If dataset attributes are to be specified, then specify all of them.
System Action:
The request is rejected.
User Action:
Determine the requirement of the request and retry.
Reason:
When a member name is specified in either the FRDSN or TODSN operand, the specification of a member list through the MEMBER operand is invalid.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
An error has occurred in the virtual 3270 interface whilst performing processing with the function code as described.
System Action:
NMCMD processing terminates.
User Action:
Determine the cause of the error and retry.
Reason:
An invalid datastream was received.
System Action:
NMCMD processing is terminated.
User Action:
Determine the cause of the error. Verify that all procedures and panels where installed correctly. The activity log may contain further details regarding this error.
Reason:
An internal error has occurred in the 3270 virtual interface.
System Action:
The request is rejected, and processing is terminated.
User Action:
Determine the cause of the error. Verify that all procedures and panels were installed correctly. The SOLVE log may contain further details regarding this error.
Reason:
If TODSP is NEW or REP then the amount of space required for the dataset must be specified with the TOSPC operand.
System Action:
The request is rejected.
User Action:
Determine the amount of space required for the TODSN and retry.
Reason:
If TODSP is NEW or REP then either TOVOL or TOUNT, or both, must be supplied to provide the unit/volume information for the dataset.
System Action:
The request is rejected.
User Action:
Provide the unit/volume information and retry the request.
Reason:
For a new dataset, the space allocation may specify directory blocks only if a PDS is indicated by inclusion of a member name in the dataset name, or the presence of a list of members in the MEMBERS operand. Otherwise directory block information cannot be specified.
System Action:
The request is rejected.
User Action:
Correct and retry the request.
Reason:
The virtual 3270 interface has been invoked with an invalid function code.
System Action:
The request is rejected.
User Action:
Determine the cause of the error and retry.
Reason:
Either a successful start session request has not been processed by the virtual 3270 interface, or the current session has failed. A send request is not permitted unless a session exists.
System Action:
The request is rejected.
User Action:
The session start call must be used to start or restart the session with SOLVE.
Reason:
Either a successful start session request has not been processed by the virtual 3270 interface, or the current session has failed. A receive request is not permitted unless a session exists.
System Action:
The request is rejected.
User Action:
The session start call must be used to start or restart the session with SOLVE.
Reason:
The VTAM SEND macro failed.
System Action:
This message will be followed by a message giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
The VTAM RECEIVE macro failed.
System Action:
This message will be followed by a message giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
A chained message should not be received from SOLVE.
System Action:
Processing of the virtual 3270 interface is terminated.
User Action:
This is an internal error. This error should be reported to your product support representative.
Reason:
The amount of data received by the Virtual Terminal Interface from SOLVE exceeds the internal buffer size.
System Action:
Processing of the interface is terminated.
User Action:
This is an internal error and should be reported to your Product Support Representative.
Reason:
The virtual 3270 interface was requested to start a session with SOLVE using a supplied user ID and password. The first panel received from SOLVE was not the logon panel so further processing was not possible.
System Action:
Processing terminates.
User Action:
Refer to the SOLVE log for details.
Reason:
This message is preceded by a message giving broad details of the error. This message supplies specific information to use in problem determination.
System Action:
The associated request has failed.
User Action:
Using the error codes above refer to the VTAM Programming Manual for the reasons for the failure. Correct the error and retry.
Reason:
A SOLVE user ID and password are required for batch processing, but have not been supplied.
System Action:
The request is rejected.
User Action:
Correct the problem and retry the operation.
Reason:
The virtual 3270 interface was unable to open an ACB.
System Action:
Processing of the interface is terminated.
User Action:
Refer to the VTAM Programming Guide for explanation of the ACBERFLG.
Reason:
No VTAM ACBs were available for use by the virtual 3270 interface.
System Action:
Processing of the interface is terminated.
User Action:
Retry later. If the problem persists refer to your systems administrator.
Reason:
The ACB requested in the LUNAME operand of the NMCMD command is currently in use.
System Action:
The request is rejected.
User Action:
Select a different luname for the requested, or retry when this ACB is no longer in use.
Reason:
A system macro - xxxxxxxx is GETVIS or FREEVIS - failed with a return code of nn.
System Action:
The program cancels.
User Action:
Refer to the IBM VSE Application Programming: Macro Reference manual using the macro name and the return code. A GETVIS error will probably mean running in a larger partition/region. A snap dump may also be produced which may be required by your product support representative if an immediate diagnosis cannot be ascertained.
Reason:
The virtual 3270 interface will only function with a SOLVE system that is licensed for the external interface feature. This message will also appear if a user of the TSO interface tries to logon to an application other than SOLVE.
System Action:
The request fails.
User Action:
If the logon attempt was to SOLVE, then your system is not licensed for this facility. Contact your product support representative.
Reason:
The VTAM SETLOGON macro failed.
System Action:
This message will be followed by message N95799 giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
The VTAM REQSESS macro failed.
System Action:
This message will be followed by message N95799 giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
The VTAM OPNSEC macro failed.
System Action:
This message will be followed by message N95799 giving specific return codes.
User Action:
Interpret the return codes and correct the error.
Reason:
The VTAM NSEXIT was driven during establishment of the session with SOLVE.
System Action:
Processing of the virtual 3270 interface is terminated.
User Action:
This condition may indicate that the product has not been correctly installed.
Reason:
The requested SOLVE VTAM APPL (application) is not defined to VTAM.
System Action:
The request is rejected.
User Action:
Validate that the APPL major node you requested has been varied active to VTAM. If it has not been, you can vary it active with the ACT command from an OCS screen. The APPL name 'applname' may be the default APPL name of NM or it may be one you have specified incorrectly in the APPL parameter of the NMCMD command.
Reason:
The requested SOLVE applname is not executing.
System Action:
The request is rejected.
User Action:
Validate that the APPL you requested is correct.
Reason:
The VTAM GENCB macro failed.
System Action:
The TSO interface request has failed.
User Action:
See the VTAM Programming Manual for a description of these register return codes.
Reason:
The session with SOLVE has failed.
System Action:
Processing of the virtual 3270 interface is terminated.
User Action:
Refer to preceding messages for determination of the problem.
Reason:
The SOLVE application requested is inactive, or not accepting logons.
System Action:
The request is rejected.
User Action:
Determine the status of the required SOLVE system and retry the operation when the application is available.
Reason:
This message is preceded by a message giving broad details of the error. This message supplies specific information to use in problem determination.
System Action:
The associated request has failed.
User Action:
Using the error codes above refer to the VTAM Programming Manual for the reasons for the failure. Correct the error and retry.
Reason:
An invalid 3270 command code was received in a datastream sent from SOLVE.
System Action:
Processing of the virtual 3270 interface is terminated.
User Action:
This should not occur. Report the occurrence to your product support representative.
Reason:
An invalid buffer order was detected in a datastream received from SOLVE.
System Action:
Processing of the virtual 3270 interface is terminated.
User Action:
This should not occur. Report the occurrence to your product support representative.
Reason:
A user-defined User Services screen has more than 86 fields. Each field is equivalent to an attribute byte, unprotected (i.e. input field) or protected (output). In the case of protected fields this extends to text literals etc., everywhere where a #FLD character is present.
Note: This message can be generated because the wrong panel is being presented as a result of incorrect logic in the User Services procedure. For example, if the MENU option of an NMLOGON or BCILOGON command is incorrect, an unexpected User Services panel may be presented if you the User Services procedure has been tailored.
System Action:
The program cancels.
User Action:
Check that the User Services panel does not have more than 86 fields defined. If so, correct and retry.
If the field count is correct ensure that the correct User Services panel is being presented as a result of the NMLOGON or BCILOGON MENU operand, or subsequent command(s). To check which panel is being presented, simulate the NMCMD or BCI data by using a real 3270 and entering the commands.
Reason:
The command just read from the system input device has been bypassed because there is no SOLVE session successfully established. This is possibly due to the failure of an earlier BCILOGON command.
System Action:
The command is ignored.
User Action:
Determine why there is no SOLVE session active. If a BCILOGON failed, correct it and re- run. If there was no BCILOGON command, rerun with the BCILOGON command added.
Reason:
A BCILOGON command has been read while a session (i.e. previous BCILOGON command) is still active. This may be due to the failure of an earlier BCIDISC command.
System Action:
The command is ignored.
User Action:
Determine why there is a SOLVE session active and correct the input accordingly.
Reason:
In executing a BCILOGON command, the Virtual 3270 Interface (NMV3270I), has to be loaded from the load/core-image library but it could not be found.
System Action:
The program cancels.
User Action:
Ensure that the library containing the member is in the search chain.
Reason:
The macro or load-member xxxxxxxx, which may be GETVIS, FREEVIS, CDLOAD or NMV3270I, has failed with a return code nn.
System Action:
The program cancels.
User Action:
If the message indicates NMV3270I, there may be an earlier message providing additional explanatory details. In the case of a macro, the appropriate IBM manual should be referenced using the return code given. GETVIS/CDLOAD errors will probably mean running in a larger partition/region. A snap dump is also produced which may be required by your product support representative if an immediate diagnosis cannot be ascertained.
Reason:
A session has to be implicitly disconnected for one of the following reasons:
System Action:
A BCIDISC command is assumed and actioned.
User Action:
If message N96009 was issued, the cause of that problem should be ascertained. If this message is issued for the latter reason, a BCIDISC command should be added to the input, unless a previous BCIDISC failed.
Reason:
A BCILOGON command has been successfully processed. The BCI applid is shown on the system output file.
System Action:
None.
User Action:
None.
Reason:
A BCILOGON command is incomplete for one of the following reasons:
System Action:
The command is ignored.
User Action:
Determine the actual cause of the error and correct the command.
Reason:
A BCILOGON command, shown in the message, cannot be actioned because the parameters and keywords cannot be recognized. Possible causes are:
System Action:
The command is ignored.
User Action:
Determine the cause of the error and correct the command.
Reason:
The User Services procedure has returned (in the third control field of the panel) a non- zero code (ie. &RETCODE = nn).
System Action:
BCI sends a F12 function (to clear any internal command replies), forces a disconnect (issuing N96005), and the job is cancelled setting the JCL return code to 1000 plus the &RETCODE value, for example, if &RETCODE was set to 30, the JCL return code is 1030.
User Action:
Use the return code to establish the reason for the error and correct either the command or the procedure.
Reason:
A BCIDISC has been successfully executed terminating the session with the applid shown in the message.
System Action:
None.
User Action:
None.
Reason:
The userid and/or password are not known to the SOLVE system identified by the applid in the BCILOGON command. Possible explanations are:
This message is also produced after N96016.
System Action:
The BCILOGON is rejected.
User Action:
Determine the cause of the error and correct the command.
Reason:
A BCIEXITC command with no operand was found, but there is no command user-exit currently active. This may be due to the failure of a previous BCIEXITC command.
System Action:
The command is ignored.
User Action:
Determine why there is no command user-exit active and correct the input accordingly.
Reason:
This can occur for VSE/SP only. The program name specified cannot be located in the core-image library. If this condition should occur in an OS environment an S806 abend or equivalent will occur.
System Action:
The job cancels.
User Action:
Ensure that the exitname is specified correctly and that the library containing the member is in the search chain.
Reason:
A BCIEXITC command specifying an exitname has been found while an exit is still active.
System Action:
The job cancels.
User Action:
De-activate the current exit by including a BCIEXITC command with no operands before the BCIEXITC command in error.
Reason:
For nn=4, the user-exit name specified on the BCIEXITC command is invalid. Possible reasons are:- - name longer than 8 characters - name is NMBCI or NMV3270I Other return codes are returned by the user coded exit.
System Action:
The job cancels.
User Action:
If the return code is 4, correct the user-exit name in the input data stream. If the code is not 4, refer to the command user exit in question.
Reason:
The password for this user has expired. This is due to either the password expiry period has elapsed, or this is the first logon after the setting of an initial or forced password.
System Action:
The user is logged off and message N96011 issued.
User Action:
Access SOLVE from a 3270 terminal to set a new password for this user.
Reason:
A BCILOGON request has established that reconnect environments existed, possibly due to previous BCI jobs that have failed. BCI does not support reconnection of these environments.
System Action:
The reconnect environments are cancelled and the BCILOGON continues.
User Action:
None.
Reason:
The Batch Command Interface (BCI) has tried to open the file whose DD name is P1 but the open failed due to a JCL error. The nature of the error is indicated by an operating system message, for example: IEC130I P1 DD STATEMENT MISSING.
System Action:
The message is written to the JES log as a Write-To-Operator (WTO) message. BCI terminates with return code 12.
User Action:
Check the job output for additional operating system messages. Correct the JCL and rerun.
Reason:
The SSI interface has connected to a SOLVE SSI for the indicated SSID and JOBNAME.
System Action:
SSI facilities are now available.
User Action:
None.
Reason:
The SSI interface has lost connection with the indicated SSI for the indicated reason.
System Action:
SSI facilities are unavailable.
User Action:
Check that the connection failure is expected. If not, investigate and restart the SSI.
Reason:
The SSI interface has lost connection with the indicated SSI and cleaned up the SSI command environment for this SOLVE system.
System Action:
SSI commands cannot be issued.
User Action:
None.
Reason:
The SSI interface could not connect with the indicated SSID.
The return code values and reasons (reason1) are:
12 - SSI Shut down
28 - Connection refused
32 - Abend occurred
36 - SSI communications error
The R0 value and reasons (reason2) are:
1 - (connection key expired) (timeout)
2 - (duplicate jobname)
3 - (duplicate domain id)
4 - (duplicate nmid)
5 - (duplicate acbname)
6 - (duplicate ascb)
7 - (no connection slots left)
8 - (jobname not in restriction list)
9 - (no connection tokens left)
10 - (no endpoint ids left)
11 - (unable to obtain $etm)
System Action:
The SSI interface remains inactive.
User Action:
Investigate the failure reason and correct it.
Reason:
The SSI interface could not connect with the indicated SSID. It will retry in the indicated interval.
System Action:
The SSI interface remains inactive.
User Action:
If the retry is not wanted, use the SYSPARMS SSID=NO command to stop retries.
Reason:
The SSI interface could not connect with the indicated SSID. Either the SSID is not in the system SSI names list, or it is not a recognisable SOLVE subsystem.
System Action:
The SSI interface remains inactive.
User Action:
Check that the correct SSID was specified.
Reason:
The SSI interface encountered an error when sending data buffers to the connected NMSSI.
System Action:
Depending on the reason for the error, either the NMSSI connection will be stopped or a retry will occur.
User Action:
Check that the SSI job is still processing.
Reason:
The SSI interface could not obtain the communications buffers used to send commands and messages to the SSI. This could indicate that the SSI job is hung or looping.
System Action:
The message will be reissued every 5 seconds until the SSI interface is stopped or buffers become available.
User Action:
Check that the SSI job is still processing.
Reason:
The SSI interface encountered an error when receiving data buffers from the connected NMSSI.
System Action:
Depending on the reason for the error, either the NMSSI connection will be stopped or a retry will occur.
User Action:
Check that the SSI job is still processing.
Reason:
The SSI command interface environment has been signed off for this user. This is as a result of the SSI SIGNOFF command.
System Action:
The environment is terminated in the SSI job.
User Action:
None.
Reason:
An invalid option opt for the SSI command cmd has been entered.
System Action:
The command is not processed.
User Action:
Correct the command.
Reason:
You are not authorized for this option of the indicated command.
System Action:
The command is not processed.
User Action:
Correct the command.
Reason:
The indicated command could not be processed, as there is no active connection to the SOLVE SSI.
System Action:
The command is not processed.
User Action:
Investigate why the SSI is not active.
Reason:
The indicated command could not be processed, as a storage shortage prevented obtaining required buffers.
System Action:
The command is not processed.
User Action:
Retry after determining the cause of the storage shortage.
Reason:
The SYSPARMS SSID command cannot be entered while the SSI interface is attempting a connection.
System Action:
The command is not processed.
User Action:
Retry after the SSI interface has finished the attempt at connection.
Reason:
The SYSPARMS SSID command was used to set a new SSID. The new SSID is not allowed, as a previous connection to the indicated SSID subsysid has occurred. This is the only acceptable SSID until SOLVE is stopped.
System Action:
The command is not processed.
User Action:
Correct the SSID.
Reason:
This message is a response message to the STATUS command; it provides the status of the SSI interface. Values for the status are:
System Action:
None.
User Action:
None.
Reason:
Input has been received from terminal aaaaaaaa but the input could not be processed due to a SOLVE temporary storage shortage.
System Action:
The connection with the terminal is closed.
User Action:
Investigate the cause of the SOLVE storage shortage.
Reason:
Terminal aaaaaaaa has attempted to logon to SOLVE but the logon has been unsuccessful due to a SOLVE temporary storage shortage.
System Action:
The logon attempt fails. The terminal will return to SSI control.
User Action:
Investigate the reason for the SOLVE temporary storage shortage.
Reason:
During initialization, the communication path between the product and NMSSI is initialized to allow communication for use of non-SNA terminals from NMSSI. This communication path initialization failed. EPS (EndPoint Services) returned a non-zero return code on registration.
System Action:
Support for Non-SNA terminals from NMSSI is disabled.
User Action:
Contact your product support office.
Reason:
A storage shortage has occurred during an attempt to send some data to terminal aaaaaaaa.
System Action:
The send to the terminal fails. The connection with the terminal will be closed.
User Action:
Investigate the reason for the SOLVE storage shortage.
Reason:
The SOLVE SSI was unable to obtain a system linkage index. The return code, abend code, and r15 value are shown.
System Action:
Cross-memory services are not set up.
User Action:
Contact your product support representative.
Reason:
This message is a response to the SHOW EPS command and indicates that a list of endpoints follows.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and indicates that a list of EPS Services follows.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and indicates that a list of active EPS conversations follows.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides column headings for following N99720 messages.
The columns are:
The endpoint name type (SOLV or SSI)
The endpoint name (SOLVE ACB name or NMSSI sysname and ssid)
The assigned endpoint id
A bitmap of supported EPS classes
The SOLVE or NMSSI version
various flags
This column is not used in this display (but is present to preserve alignment with the SHOW SSIEPS display)
The current hop count to this endpoint
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides column headings for following N99721 messages.
The columns are:
The SOLVE NMID
The jobname
The system name
The primary ACB
The Management Services level
The SOLVE domain ID
The NMSSI ssid
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides column headings for following N99722 messages.
The columns are:
The operating system
EPS attribute flags
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command and provides column headings for following N99723 messages.
The columns are:
The unacknowledged message window size
The retransmission timeout in seconds
The number of sends
The number of resends
The number of ignored inbound messages (outside window)
The number of ignored inbound acknowledgements (already acknowledged)
The number of send failures
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command and provides column headings for following N99724 messages.
The columns are:
The number of messages sent to this endpoint
The number of message bytes sent to this endpoint
The number of messages received from this endpoint
The number of message bytes received from this endpoint
These statistics relate to the actual number of messages or bytes that target this endpoint, as distinct to the total number of messages or bytes that were sent to or received from this endpoint including messages coming via or going via this endpoint.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides endpoint information. Refer to message N99710 for headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides endpoint information. Refer to message N99711 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides endpoint information. Refer to message N99712 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides endpoint information. Refer to message N99713 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides endpoint information. Refer to message N99714 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides column headings for following N99755 messages.
The columns are:
The internal ID assigned to this service name.
The service name
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides column headings for following N99756 messages.
The columns are:
The EndPoint ID of the owner of this service.
The service 'type'
The service scope, GLOBAL or LOCAL
A textual description of the service, if available.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides service information. Refer to message N99750 for headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides service information. Refer to message N99751 for headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides column headings for following N99765 messages.
The columns are:
The internal identifier assigned to this conversation
The conversation type (PRI or SEC)
A flag representing internal conversation state.
The Endpoint Identifier of the other end of the conversation
The CID for this conversation at the other end.
The EPS internal class of this conversation.
If this conversation is with a service, the service id.
If a description was provided on the connect request, the value provided.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides column headings for following N99766 messages.
The columns are:
The number of messages sent on this conversation
The number of message bytes sent on this conversation
The number of messages received on this conversation
The number of message bytes received on this conversation
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides service information. Refer to message N99760 for headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW EPS command and provides service information. Refer to message N99761 for headings.
System Action:
None.
User Action:
None.
Reason:
This message is issued during initialization if an error occurs during EPS access method initialization.
System Action:
The EPS access method is not initialized.
User Action:
Contact your support office.
Reason:
This message indicates that the EPS access method was unable to process input from the indicated EPS source node due to a storage shortage.
System Action:
The session is closed.
User Action:
ensure that the SOLVE region has sufficient storage available.
Reason:
An attempt to establish as session using EPS failed due to a lack of storage.
System Action:
The session establishment fails.
User Action:
Ensure that the SOLVE region has sufficient storage.
Reason:
EPS session connection failed for the indicated target system name. The specific type of processing is indicated (the ffffffff operand), and a reason is displayed.
For each processing type, the possible reasons are:
INTERNAL ERROR - UNKNOWN EPS CID
STORAGE SHORTAGE
INTERNAL ERROR - INVALID USERDATA LENGTH
EPS FACILITY NOT AVAILABLE
INTERNAL ERROR - UNKNOWN EPS CID
STORAGE SHORTAGE
INTERNAL ERROR - INVALID USERDATA LENGTH
EPS FACILITY NOT AVAILABLE
System Action:
The session establishment fails.
User Action:
Examine the reason and if possible, correct the problem.
Reason:
An attempt to establish as session using EPS failed due to a lack of storage.
System Action:
The session establishment fails.
User Action:
Ensure that the SOLVE region has sufficient storage.
Reason:
An attempt to send data across an EPS session failed due to a lack of storage.
System Action:
The send fails.
User Action:
Ensure that the SOLVE region has sufficient storage.
Reason:
An attempt to send data across an EPS session failed. The target SOLVE system name is shown. The reasons are:
INTERNAL ERROR - INVALID CID
STORAGE SHORTAGE
INTERNAL ERROR - INVALID USERDATA LENGTH
EPS FACILITY NOT AVAILABLE
REQUEST GAVE RC nnnnnnnn
System Action:
The send fails.
User Action:
Correct the problem if possible. It is possible that the target SOLVE system has terminated or EPS contact was lost. If the problem persists, contact your SOLVE product support office.
Reason:
An attempt to establish as session using EPS failed due to a lack of storage.
System Action:
The session establishment fails.
User Action:
Ensure that the SOLVE region has sufficient storage.
Reason:
A EPS connection to the named SOLVE system has been lost
System Action:
Any active EPS sessions are terminated.
User Action:
Determine why the EPS connection was lost and reestablish it if possible.
Reason:
This message indicates that the EPS access method was unable to process input from the indicated EPS source node due to a storage shortage.
System Action:
The session is closed.
User Action:
ensure that the SOLVE region has sufficient storage available.
Reason:
The NM/PASS feature could not be initialized because a required load module aaaaaaaa could not be loaded. The R15 and R1 values relate to the operating system LOAD macro and represent a return code and reason code respectively.
System Action:
NM/PASS will be disabled until the problem is corrected and SOLVE is restarted.
User Action:
Refer this problem to your systems administrator.
For OS systems the reason code (R1) equates to a system abend code. The most common reason code is 0806 which means that the load module does not exist in any library in the STEPLIB concatenation.
Reason:
NCL variable aaaaaaaa coded as an operand value on a &PASSCHK verb does not exist.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
During execution of a &PASSCHK verb, the internal algorithm used to check or verify a session pin failed.
System Action:
The NCL procedure terminates.
User Action:
Check the content of the variables coded on the &PASSCHK verb. This failure is generally due to invalid data being applied to the algorithm.
Reason:
NCL variable aaaaaaaa coded as an operand value on a &PASSCHK verb contains invalid data.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The NCL variable coded on the PK operand of a &PASSCHK verb did not contain a valid NM/PASS passkey.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry. The passkey required is a 44-character, expanded hexadecimal number, maintained for synchronisation purposes for a NM/PASS userid.
Reason:
This message is written to the activity log on every use of the &PASSCHK verb. It shows the name of the invoking NCL procedure, and the return code from the verb.
System Action:
None.
User Action:
This message provides the basis for an audit trail for NM/PASS usage.
Reason:
This message is logged when the SAS Object Services Procedure is initialised.
System Action:
None.
User Action:
None.
Reason:
This message is logged when the SAS Object Services Procedure completes processing. P1 indicates the number of observations written to the output dataset and P2 indicates the completion code of proc ASMOS.
System Action:
The procedure terminates.
User Action:
If the completion code is not 0 then review the SAS message log for other NBxxxx warning or error messages.
Reason:
The SAS Object Services Procedure has detected a syntax error in one of the supplied ATTR statements. This message is preceeded by message NB0202 which displays the statement in error. P1 describes the type of syntax error which was detected.
System Action:
The SAS procedure terminates.
User Action:
Correct the source statement and retry the operation.
Reason:
This message displays the SAS Object Services Procedure source ATTR statement which contains a syntax error. This message is followed by message NB0201 which describes the type of syntax error detected.
System Action:
The SAS procedure terminates.
User Action:
Correct the source statement and retry the operation.
Reason:
The SAS Object Services Procedure has received a response from Object Services to the object selection criteria specified in the source statements. P1 indicates the number of objects which will be extracted from the class nominated by P2.
System Action:
If P1 is greater than 0 processing continues otherwise the SAS Object Services Procedure terminates.
User Action:
None.
Reason:
The SAS Object Services Procedure was unable to locate the load module required to access Object Services.
System Action:
The SAS Object Services Procedure terminates.
User Action:
Ensure that the nominated load module is available either in the LPA or in the load search path for the SAS environment.
Reason:
The SAS Object Services Procedure was executed without any source ATTR statements being supplied.
System Action:
The SAS Object Services Procedure terminates without performing any data extraction.
User Action:
If object data extraction is desired then code at least one ATTR statement, otherwise no action is required.
Reason:
The SAS Object Services Procedure was unable to obtain sufficient storage for normal operation.
System Action:
The SAS Object Services Procedure terminates.
User Action:
Increase the region size available to the SAS environment and retry the operation.
Reason:
The SAS Object Services Procedure has been supplied more than the maximum allowed number of the nominated type of source statements. P1 indicates the type of source statement.
System Action:
The SAS Object Services Procedure continues processing. The source statement is ignored.
User Action:
Reduce the number of the nominated type of source statements supplied to the SAS Object Services Procedure.
Reason:
Object Services returned a greater number of attributes than the SAS Object Services Procedure was able to receive.
System Action:
Some attribute data will be discarded.
User Action:
Contact your product support representative.
Reason:
The SAS Object Services procedure received an error indication.
P1 indicates the communications function being performed. If an Object Services method was being accessed this is described by P2 while the error category is indicated by P3. This message is generally immediately followed by another message describing the error.
System Action:
The SAS Object Services Procedure terminates.
User Action:
Determine the cause of the error by reviewing associated NBxxxx and other messages in the SAS log. The SOLVE system activity log may also contain related information.
Reason:
The SAS Object Services Procedure was either unable to establish contact with the SOLVE system or else an existing communication path was unexpectedly terminated. P1 is the PPI address of the OS PPI Server NCL procedure. P2 is the return code associated with the Object Services Applications Programming Interface.
System Action:
The SAS Object Services Procedure terminates.
User Action:
Refer to the Object Services Applications Programming Interface documentation to determine the meaning of the return code.
Reason:
The SAS Object Services Procedure was unable to convert the value of attribute P1 according to the FORMAT and INFORMAT specifications of the source ATTR statement for that attribute. P2 indicates the nth processed object from which the attribute value was retrieved.
System Action:
The SAS Object Services Procedure continues.
User Action:
Refer to SAS FORMAT and INFORMAT specifications to determine the cause of the error.
Reason:
The SAS Object Services Procedure received an attribute which was not described by a source ATTR statement.
System Action:
The SAS Object Services Procedure discards the attribute data and continues processing.
User Action:
Contact your product support representative.
Reason:
The interface module for reporting problems to SOLVE:Problem from NetView was unable to load the Object Services Application Programming Interface (OS API) module.
System Action:
The request to create a SOLVE:Problem Problem object is terminated.
User Action:
Ensure the OS API load module is accessible from NetView.
Reason:
The interface module for reporting problems to SOLVE:Problem from NetView received an error response from the Object Services Application Programming Interface (OS API). The return code returned by the OS API was nnnn. If the return code is 8, then aaaaa will be the Object Services ErrorID (if applicable). If the Object Services error message is available, it will be returned with message NB4003.
System Action:
The request to create a SOLVE:Problem Problem object is terminated.
User Action:
If message NB4003 was also issued then refer to this message for further information.
Reason:
The interface module for reporting problems to SOLVE:Problem from NetView received an error response from the Object Services Application Programming Interface (OS API). The return code and ErrorID for the error was returned in message NB4002 and aaaaa contains the accompanying error message returned by Object Services.
System Action:
The request to create a SOLVE:Problem Problem object is terminated.
User Action:
Refer to the explanation of message aaaaa.
Reason:
The interface module for reporting problems to SOLVE:Problem from NetView issued a create service request to the Object Services Application Programming Interface (OS API). The create was successful however the naming attribute for the created object was not returned to the interface. The expected attribute ID was ZPRPROBID.
System Action:
The request to create a SOLVE:Problem Problem object was successful however the Problem ID will not be returned to NetView since it was not available.
User Action:
None.
Reason:
The interface module for reporting problems to SOLVE:Problem from NetView issued a create service request to the Object Services Application Programming Interface (OS API). The create was successful however the internal key attribute for the created object was not returned to the interface. The expected attribute ID was ZOSINTKEY.
The internal key was not available because the interface could not issue the create request for the related Reference Text object.
System Action:
The request to create a SOLVE:Problem Problem object was successful however the related Reference Text was not added.
User Action:
None.
Reason:
Endevor passed a pointer to the $PECBDS DSECT on the call to the package exit. This pointer was examined and found to be zero which is invalid.
System Action:
The package exit terminates.
User Action:
Contact the person responsible for Endevor at your installation.
Reason:
Endevor passes a pointer to the $PECBDS DSECT on a package exit call. The exit reads the PECBID field in this DSECT. This field is supposed always to be "PECB". However, another value was found in this field.
System Action:
The package exit terminates.
User Action:
Contact the person responsible for Endevor at your installation.
Reason:
Endevor passes a pointer to the $PHDRDS DSECT on a package exit call. The exit reads the PHDRID field in this DSECT. This field is supposed always to be "PHDR". However, another value was found in this field.
System Action:
The package exit terminates.
User Action:
Contact the person responsible for Endevor at your installation.
Reason:
Endevor passes a pointer to the $PACTREQ DSECT on a package exit call. The exit reads the PACTID field in this DSECT. This field is supposed always to be "PACT". However, another value was found in this field.
System Action:
The package exit terminates.
User Action:
Contact the person responsible for Endevor at your installation.
Reason:
The package exit GETMAINS a storage area and stores the pointer to this area in the field PECBUEXT in the $PECBDS control block. Register 12 is used to access this storage area. The exit periodically checks that the value in register 12 is still the same as that in PECBUEXT. A check showed that these values were different.
System Action:
The package exit terminates.
User Action:
Contact the person responsible for Endevor at your installation.
Reason:
The Endevor package exit was unable to load the SOLVE Object Services Application Programming Interface (OS API) module.
System Action:
The package exit terminates.
User Action:
Contact the person responsible for Endevor at your installation.
Reason:
A request by the Endevor package to obtain working storage failed. The request for storage was made via the assembler macro GETMAIN.
System Action:
The Endevor package exit terminates.
User Action:
Contact the person responsible for Endevor at your installation.
Reason:
The Endevor package obtains the working storage which it needs via a call to the GETMAIN macro. The pointer returned via the GETMAIN call is invalid.
System Action:
The Endevor package exit terminates.
User Action:
Contact the person responsible for Endevor at your installation.
Reason:
Endevor passes a pointer to the $PREQPDS DSECT on a package exit call. The exit reads the PREQID field in this DSECT. This field is supposed always to be "PREQ". However, another value was found in this field.
System Action:
The package exit terminates.
User Action:
Contact the person responsible for Endevor at your installation.
Reason:
The package exit did not invoke the ZCGENDLOG action to update text because no change number could be determined from the action CCID. P1 is the CCID.
System Action:
None.
User Action:
None.
Reason:
The Endevor exit attempted to extract a change number from the action CCID. The exit failed to extract a change number. P1 is the CCID.
System Action:
The Endevor exit rejects the package function.
User Action:
Correct the CCID.
Reason:
The Endevor exit called the Object Services Application Programming Interface (OS API). The Object Services API returned an error code. P1 is the error code. P2 contains an associated message if available.
System Action:
The package function is rejected if this is a before or mid exit call or the change is not updated if this is an after exit call.
User Action:
Review the explanation of associated messages.
Reason:
The Endevor exit called the Object Services Application Programming Interface (OS API). The Object Services API returned an error indicating a PPI error. P1 is the returned error code.
System Action:
The package function is rejected if this is a before or mid exit call or the change is not updated if this an after exit call.
User Action:
None.
Reason:
The Memo API Interface module was called with an invalid parameter list format.
System Action:
The Memo API Interface ignores the call.
User Action:
Contact the system administrator.
Reason:
The Memo API Interface module NMMEMO was invoked in other than a defined SUBSYS environment.
System Action:
The Memo API Interface terminates.
User Action:
Contact the system administrator.
Reason:
The Memo API Interface module NMMEMO was invoked by a procedure other than that which initially invoked it.
System Action:
The Memo API Interface ignores the call.
User Action:
Contact the system administrator.
Reason:
The Memo API Interface module NMMEMO was called to send data to the Memo email system but a valid initialization call has not yet been executed.
System Action:
The Memo API Interface ignores the call.
User Action:
Contact the system administrator.
Reason:
The Memo API Interface module NMMEMO was called without any parameters passed in the first NCL variable.
System Action:
The Memo API Interface ignores the call.
User Action:
Contact the system administrator.
Reason:
The Memo API Interface module NMMEMO was called with an invalid keyword parameter or parameter value. P1 is the keyword and P2 is the keyword value.
System Action:
The Memo API Interface ignores the call.
User Action:
Contact the system administrator.
Reason:
The Memo API Interface module NMMEMO was called without a mandatory keyword for the requested function. P1 is the function requested. P2 is the keyword which was not supplied.
System Action:
The Memo API Interface ignores the call.
User Action:
Contact the system administrator.
Reason:
The Memo API has returned an error indication to the Memo API Interface module NMMEMO. The Memo API function requested was P1. P2 is the API return code and P3 is the API feedback code.
System Action:
The request fails.
User Action:
Refer to the Memo/API User Reference Manual (supplied with the Memo email system) to determine the exact nature of the error.
Reason:
The Memo API Interface has successfully connected to the Memo email system.
System Action:
None.
User Action:
None.
Reason:
The Memo API Interface was called to connect to the Memo email system but was already connected.
System Action:
None.
User Action:
Contact the system administrator.
Reason:
The Memo API Interface has successfully delivered a mail item to the Memo email system known as P1. P2 is only present if one or more of the message receivers were not valid Memo users. P2 indicates a warning condition rather than an error.
System Action:
None.
User Action:
If P2 indicates an invalid receiver review the destination specification or the Memo distribution list for invalid Memo ID's.
Reason:
The Memo API Interface has successfully disconnected from the Memo email system.
System Action:
The Memo API Interface terminates.
User Action:
None.
Reason:
An attempt to change the name of SOLVE's UCE using SYSPARMS XNFUCENM has failed. The current UCE name is already cataloged, and cannot be changed.
System Action:
The SYSPARMS command is rejected.
User Action:
To change a cataloged UCE name, you must first release the UCE connection by using XNF STOP, then retry the command.
Reason:
The screen size specified on SYSPARMS XNFSCRSZ= is not supported. Enter the screen size in the format (mmm,nnn) where mmm (rows) is between 12 and 255 and nnn (columns) is between 40 and 255.
System Action:
The SYSPARMS command is rejected.
User Action:
Correct and re-enter the command.
Reason:
A CONNECT command has been entered to connect a network node to SOLVE, but the node name has been omitted.
System Action:
The command is rejected.
User Action:
Specify a node name on the command.
Reason:
A CONNECT command has been entered with a node name which is not a valid network node name.
System Action:
The command is rejected.
User Action:
Correct the node name and retry. The name must be 8 characters or less.
Reason:
A CONNECT command has been entered but contains an operand which is not recognised or has been entered in an invalid format.
System Action:
The command is rejected.
User Action:
Correct the format of the command and retry.
Reason:
A CONNECT command has been entered which specifies the SIZE=(rrr,ccc) operand but the screen size supplied is not valid. The row value rrr must be from 12 to 255, and the column value ccc must be from 40 to 255.
System Action:
The command is rejected.
User Action:
Correct the screen size and retry.
Reason:
Command XNFTRACE START=aaaaaaaa has been entered, but node aaaaaaaa is already being traced.
System Action:
The command is rejected.
User Action:
None. The SHOW XNFTRACE command can be used to list active XNF traces.
Reason:
Command XNFTRACE STOP=aaaaaaaa has been entered, but node aaaaaaaa is not being traced.
System Action:
The command is rejected
User Action:
Correct the node name and retry. The SHOW XNFTRACE command can be used to list active XNF traces.
Reason:
Command XNFTRACE START=aaaaaaa has been accepted.
System Action:
Since node aaaaaaa is not currently connected, the trace request is put in PENDING state. Tracing will go ACTIVE as soon as the node is connected.
User Action:
None. The SHOW XNFTRACE command can be used to list active XNF traces.
Reason:
Command XNFTRACE START=aaaaaaaa has been accepted.
System Action:
Tracing of node aaaaaaaa will start immediately. Trace messages will be written to the activity log.
User Action:
None. The SHOW XNFTRACE command can be used to list active XNF traces.
Reason:
Command XNFTRACE STOP=aaaaaaa has been accepted.
System Action:
The PENDING request for trace of aaaaaaa is cancelled.
User Action:
None.
Reason:
Command XNFTRACE STOP=aaaaaaaa has been accepted.
System Action:
The active trace of aaaaaaaa is stopped immediately.
User Action:
None.
Reason:
Command XNFTRACE STOP=ALL has been entered, but no XNFTRACE is active or pending in the system.
System Action:
None.
User Action:
None.
Reason:
Command XNF STOP has been accepted
System Action:
All connections between SOLVE and other nodes in the XNF network will be dropped. This includes connections to terminals, other SOLVE systems and NETM. When the disconnections are complete, SOLVE's UCE will be released. When all communication with XNF has ceased, a WTOR message will be written to the system console.
User Action:
To reestablish communication between SOLVE and XNF, reply to the outstanding WTOR.
Reason:
The XNF command was entered with an invalid operand. The only valid operand is 'STOP'.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An XNF STOP command has been entered, but no connection exists between SOLVE and XNF.
System Action:
The command is rejected.
User Action:
Check the system console for messages relating to the state of the SOLVE system's connection to XNF.
Reason:
This is the heading line displayed in response to a SHOW XNFTRACE command.
ULENAME - The name of the ULE node being traced
REQ-UID - The userid who requested the trace
REQ-DATE - The date the trace was requested
REQ-TIME - The time the trace was requested
STATUS - The current status of the trace, 'ACTIVE' or 'PENDING'.
System Action:
None
User Action:
None.
Reason:
This is a detail line of a SHOW XNFTRACE display. Refer to message NC6801 for a description of each field.
System Action:
None
User Action:
None
Reason:
A SHOW XNFTRACE command has been entered, but no traces are active or pending.
System Action:
None
User Action:
None
Reason:
A NETM command was entered, but no connection paths to NETM/OP have been defined.
System Action:
The command is rejected.
User Action:
To pass commands to NETM/OP, one or more connection paths must be defined. Use the NETMCNTL ADD= command to define the required paths.
Reason:
A NETM command was entered, but the system could not pass it to NETM for processing. A subsequent message has been written to the log explaining the specific error condition.
System Action:
The command is rejected.
User Action:
Refer to the log. Immediately following this message will be a message indicating failure codes. Refer to the explanation of that message for further information.
Reason:
Follows a NC6B01 or NC6G01 message, indicating an error has occurred in communications with NETM. xxxxx indicates the return code from the call to the NETM Application Programming Interface. yyyy indicates the type of call to the API that caused the error.
System Action:
For command processing, the command is rejected. For UNSOL processing, unsolicited message receipt is stopped.
User Action:
The error code (xxxxx) and call type (yyyy) are described in the NETM manual 'Operation Management UAP Interface Function Instruction Manual'. Refer to this manual for an explanation of the codes, or contact your product support representative. Common error code values (xxxxx) are:
79101 : Specified UAP name not defined to XNF/AM
79300 : Specified UAP name already in use
79021 : UAP name not alphanumeric
79023 : UAP name not defined to NETM/OP
Reason:
A storage shortage caused a failure in either NETM command handling or unsolicited message receipt.
System Action:
For command processing, the command is rejected. For UNSOL processing, unsolicited message receipt is stopped.
User Action:
Refer to your installation support representative to establish why there is insufficient storage.
Reason:
A subtask abend has occurred during communication with NETM. The abend code is indicated by xxx.
System Action:
For command processing, the command is rejected. For UNSOL processing, unsolicited message receipt is stopped.
User Action:
Refer to your support representative.
Reason:
A NETMCNTL ADD=xxxx command was entered, specifying a connection path name xxxx that is already defined.
System Action:
The command is rejected.
User Action:
Correct the name and re-enter.
Reason:
Confirms successful completion of a NETMCNTL ADD=xxxx command
System Action:
None
User Action:
None
Reason:
A NETMCNTL DEL=xxxx command was entered, specifying a connection path name that has not been defined.
System Action:
The command is rejected
User Action:
Correct the name and re-enter
Reason:
Confirms successful execution of a NETMCNTL DEL=xxxx command. Depending on the connection path's status at the time of the command, the path may not be deleted immediately, but will be deleted within two or three minutes at the maximum. Use the SHOW NETMCNTL command to display the status of the connection path if confirmation of actual deletion is required.
Note that the same name may not be re-defined using a NETMCNTL ADD command until the original definition has been successfully deleted.
System Action:
None.
User Action:
None.
Reason:
A NETM command was entered with no command text supplied. This is required, so that the command text can be sent to NETM.
System Action:
The command is rejected.
User Action:
Correct the command and re-enter.
Reason:
A NETM command was accepted, but no NETM communication paths (defined by the NETMCNTL ADD=name command) are immediately available to process the command. It has been been queued for processing.
System Action:
The command will be processed by the first available NETM communication path.
User Action:
This is a symptom of too many commands being issued simultaneously for the current number of defined NETM communication paths. If necessary, use the NETMCNTL ADD= command to define more NETM communication paths to allow more concurrent commands to be processed.
Reason:
A NETMCNTL DEL=xxxx command was entered specifying the name of a NETM communication path that is currently active for the receipt of unsolicited messages from NETM. This entry was defined using the NETMCNTL ADD=xxxx TYPE=UNSOL command, and activated by an earlier NETMCNTL START=UNSOL command.
System Action:
The command is rejected because the entry cannot be deleted until it is no longer active.
User Action:
If the entry is to be deleted, issue NETMCNTL STOP=UNSOL command, then re-issue the NETMCNTL DEL=xxxx command.
Reason:
A NETMCNTL ADD=xxxx TYPE=UNSOL command was entered, to define a connection path for receiving unsolicited messages from NETM/OP, but a TYPE=UNSOL definition already exists. You cannot define multiple TYPE=UNSOL paths.
System Action:
The command is rejected.
User Action:
None.
Reason:
xxxx may have the value of 'ALREADY' or 'NOT'. If its value is 'ALREADY', a NETMCNTL START=UNSOL command has been issued, but unsolicited message flow has been activated by an earlier NETMCNTL START= command. If xxxx has a value of 'NOT', a NETMCNTL STOP=UNSOL command was issued, but unsolicited message flow has not previously been activated by a NETMCNTL START=UNSOL command.
System Action:
The command is rejected.
User Action:
None.
Reason:
A NETMCNTL START=UNSOL command was entered, but there is no available TYPE=UNSOL connection path.
System Action:
The command is rejected.
User Action:
Use NETMCNTL ADD=xxxx TYPE=UNSOL to define a NETM communication path to receive unsolicited messages, then re-issue the NETMCNTL START=UNSOL command.
Reason:
A NETM command was entered, but NETM commands have been disabled by NETMCNTL STOP=CMD. No NETM commands will be accepted.
System Action:
The command is rejected.
User Action:
NETM commands can be enabled by a NETMCNTL START=CMD command. When NETM commands have been enabled, reenter your command.
Reason:
Confirms successful completion of a NETMCNTL START=CMD or STOP=CMD
System Action:
If NETMCNTL START=CMD has been issued, NETM commands will now be accepted. If NETMCNTL STOP=CMD has been issued, NETM commands will be disallowed
User Action:
None.
Reason:
This message acknowledges a NETMCNTL START=UNSOL or STOP=UNSOL command (aaaaa is START or STOP).
System Action:
The request to START or STOP the unsolicited message flow will be notified to NETM. Confirmation of successful start or stop will be subsequently logged to all MONITOR users and to the activity log.
User Action:
None.
Reason:
This is the heading line of a SHOW NETMCNTL command, which lists defined NETM connection paths.
System Action:
None
User Action:
None
Reason:
The text line of a SHOW NETMCNTL command. For each defined entry, (created by an earlier NETMCNTL ADD= command) one of these messages will be displayed.
wwww is the type of the connection path (COMMAND or UNSOL)
xxxx is the name of the connection path
yyyy is the NETM category used by the connection path.
zzzz is the status of the path, and will have one of the following values:
The path type has been stopped by a NETMCNTL STOP=CMD|UNSOL command, or has not yet had a NETMCNTL START= command issued.
Currently in use.
Not currently in use (TYPE=COMMAND only)
Active but awaiting work (TYPE=COMMAND only)
The tag qqqq will have the value -DEL- if the path has been scheduled for deletion. It will be deleted once it ceases its 'ACTIVE' status.
System Action:
None.
User Action:
None.
Reason:
A NETMCNTL START=UNSOL command has failed. A subsequent message has been written to the log explaining the specific error condition.
System Action:
Unsolicited message receipt is stopped.
User Action:
Refer to the log. Immediately following this message will be a message indicating failure codes. Refer to the explanation of that message for further information.
Reason:
A NETMCNTL START=UNSOL or STOP=UNSOL command has been entered. This message confirms successful completion of the command.
System Action:
None.
User Action:
None.
Reason:
During an attempt to send data to node aaaaaaaa, a temporary SOLVE storage shortage has occurred. The send of data could not be completed.
System Action:
The connection to aaaaaaaa will be terminated.
User Action:
Investigate the reason for the SOLVE storage shortage.
Reason:
An attempt to send data on a connection to node aaaaaaaa has failed. The detail code shows the return code from the XNF PUT service.
System Action:
The connection to node aaaaaaaa is terminated.
User Action:
Investigate the reason for the send failure using the detail code in this message.
Reason:
An invalid DT VAPDU has been received by SOLVE.
System Action:
The connection to node aaaaaaaa will be aborted. A dump of the invalid APDU will appear on the activity log following this message.
User Action:
Investigate the invalid APDU.
Reason:
This message contains a hexadecimal (xxxxxxxx) and character (cccccccc) format dump of an invalid APDU which has been received by SOLVE. This messages is preceded by message NC7201 which shows which node sent the invalid APDU.
System Action:
None.
User Action:
None.
Reason:
A temporary SOLVE storage shortage has prevented processing of some input received from node aaaaaaaa.
System Action:
The connection to node aaaaaaaa will be terminated.
User Action:
Investigate the reason for the SOLVE storage shortage.
Reason:
An ABORT APDU (UAB or PAB) has been received from node aaaaaaaa. An abort indicates that node aaaaaaaa has detected an error. bbbbbbbbbbbbb gives further information about the reason of the abort.
System Action:
The connection to node aaaaaaaa is terminated.
User Action:
Investigate the reason for the abort.
Reason:
A connection request has been received from node aaaaaaaa, but the request is not a valid format. 'bbbb' shows the offset of the field in the APDU which failed validation.
System Action:
The connection is force disconnected. The invalid APDU is dumped to the activity log following this message.
User Action:
Investigate the invalid APDU.
Reason:
This message contains a hexadecimal (xxxxxxxx) and character (cccccccc) format dump of an invalid APDU which has been received by SOLVE. This messages is preceded by message NC7501 which shows which node sent the invalid APDU and the offset of the field which failed validation.
System Action:
None.
User Action:
None.
Reason:
A connection request has been received from node aaaaaaaa, but could not be processed due to a temporary SOLVE storage shortage.
System Action:
The connection will be refused.
User Action:
Investigate the reason for the SOLVE storage shortage.
Reason:
A connection has been successfully completed with node aaaaaaaa, and Start Data Traffic (SDT) processing has begun. During processing, SOLVE received invalid input, or input which was unexpected (ie. not SDT related).
System Action:
The connection will be terminated. The invalid/unexpected APDU will be dumped to the activity log following this message.
User Action:
Investigate the received APDU and determine the cause of the error.
Reason:
This message contains a hexadecimal (xxxxxxxx) and character (cccccccc) format dump of an invalid APDU which has been received by SOLVE. This messages is preceded by message NC7801 which shows which node sent the invalid APDU.
System Action:
None.
User Action:
None.
Reason:
An attempt has been made to LOCK or UNLOCK input on an XNF connection, and the request has failed.
System Action:
The connection is terminated.
User Action:
Investigate the reason for the failure.
Reason:
A connection request for node aaaaaaaa has failed due to a temporary SOLVE storage shortage.
System Action:
The connection attempt fails.
User Action:
Investigate the reason for the SOLVE storage shortage.
Reason:
A connection request was received from another application but could not be successfully processed due to a temporary SOLVE storage shortage.
System Action:
The connection will be rejected.
User Action:
Investigate the reason for the SOLVE storage shortage.
Reason:
A connect request has been received from another application but the attempt to accept the connection has failed.
System Action:
The connection request is rejected.
User Action:
Investigate the reason for the connection failure using the detail code supplied in this message.
Reason:
An invalid DT-APDU has been received from aaaaaaaa.
System Action:
The invalid APDU is dumped to the activity log and the connection on which it was received is terminated.
User Action:
Investigate the APDU format error. 'bbbb' indicates the offset in the APDU of the field which failed validation.
Reason:
This message contains a hexadecimal (xxxxxxxx) and character (cccccccc) format dump of an invalid APDU which has been received by SOLVE. This messages is preceded by message NC7D01 which shows which node sent the invalid APDU and the offset of the field which failed validation.
System Action:
None.
User Action:
None.
Reason:
An incoming connection request from node aaaaaaa could not be refused normally due to a temporary SOLVE storage shortage.
System Action:
The connection will be force-disconnected.
User Action:
Investigate the reason for the SOLVE storage shortage.
Reason:
An invalid EST or ASR APDU has been received from node aaaaaaaa.
System Action:
The connection with node aaaaaaaa will be terminated. The invalid APDU will be dumped to the activity log.
User Action:
Investigate the APDU to see why it is invalid. 'bbbb' indicates the offset in the APDU of the field which failed validation.
Reason:
This message contains a hexadecimal (xxxxxxxx) and character (cccccccc) format dump of an invalid or unexpected APDU which has been received by SOLVE. This message is preceded by message NC7F01 or NC7F03 which shows the name of the node which sent the APDU.
System Action:
None.
User Action:
None.
Reason:
An ASR APDU or EST APDU was expected during connection establishment but a different APDU has been received.
System Action:
This is a protocol violation, so the connection will be terminated. The received APDU will appear on the activity log following this message.
User Action:
Investigate the dump of the received APDU to see what was received.
Reason:
The XNF 'ENTRY' service, used to catalog SOLVE's UCE to XNF, has failed. No connection to SOLVE is possible until the ENTRY succeeds. The message contains the reason code and detail code returned by ENTRY.
System Action:
This message is sent to the system console as a WTOR. SOLVE waits for a reply of 'RETRY' or 'END'.
User Action:
Reply as required. Refer to the VOS3 XNF Messages manual (Appendix B) for the meaning of the error codes.
Reason:
The XNF 'ENTRY' service, used to catalog SOLVE's UCE to XNF, has failed. No connection to SOLVE is possible until ENTRY succeeds. The message contains the reason code and detail code returned by ENTRY.
System Action:
Because SYSPARMS XNFRETRY is set to YES, SOLVE will automatically retry the ENTRY process every 30 seconds.
User Action:
Refer to the VOS3 XNF Messages manual (appendix B) for the meaning of the error codes.
Reason:
The ENTRY service to catalog SOLVE's UCE to XNF has completed successfully.
System Action:
SOLVE will now accept logon requests and other requests for connection.
User Action:
None
Reason:
An attempt to RELEASE SOLVE's UCE from XNF has failed. The message shows the error codes from the RELEASE service.
System Action:
None
User Action:
Refer to the VOS3 XNF Messages manual (Appendix B) for an explanation of the error codes.
Reason:
SOLVE's UCE aaaaaaaa has been released from XNF.
System Action:
None.
User Action:
None
Reason:
SOLVE's connection to XNF has been released, either due to an 'XNF STOP' command or because of a forced release from XNF. All XNF connections have been terminated.
System Action:
This message is sent to the system console as a WTOR message. SOLVE waits for a reply of 'RESTART' or 'END'.
User Action:
Reply as required.
Reason:
SOLVE's connection to XNF has been forcibly released by XNF.
System Action:
Because SYSPARMS XNFRETRY=YES, SOLVE will automatically attempt to reestablish the connection to XNF in 30 seconds.
User Action:
None.
Reason:
This message is logged to all terminals connected to SOLVE prior to their being disconnected due to a 'XNF STOP' command.
System Action:
This message is followed by disconnection of the terminal.
User Action:
Wait for XNF services to be reestablished, then reconnect to SOLVE.
Reason:
An XNF GET service has failed. The message shows the error codes returned from the GET service.
System Action:
Processing continues. The error is ignored.
User Action:
If the cause of this message cannot be determined, contact your product support representative.
Reason:
SOLVE's connection to network node aaaaaaaa has been unexpectedly released by XNF.
System Action:
SOLVE completes the disconnection from XNF.
User Action:
Investigate the cause of the connection failure.
Reason:
An ABORT SPDU has been received on the connection to node aaaaaaaa.
System Action:
The AB-SPDU is traced to the activity log and the connection to aaaaaaaa is terminated.
User Action:
Investigate the reason for the abort.
Reason:
An invalid DT-SPDU has been received from node aaaaaaaa.
System Action:
The invalid message is traced to the activity log and the connection to aaaaaaaa is aborted.
User Action:
Investigate the reason for the invalid message. If the problem persists, contact your product support representative.
Reason:
This is a header message preceding the trace of an incoming SPDU. The connection to aaaaaaaa is being traced because of an XNFTRACE command.
System Action:
A trace of the SPDU is written to the activity log.
User Action:
None
Reason:
The connection to aaaaaaa has been released because SOLVE could not obtain sufficient storage to process the connection.
System Action:
aaaaaaaaa is disconnected.
User Action:
Investigate why SOLVE is short of storage.
Reason:
The connection from SOLVE to node aaaaaaaa has been released by XNF.
System Action:
aaaaaaaa is disconnected
User Action:
Investigate the cause of the failure.
Reason:
The connection from SOLVE to node aaaaaaaa has been aborted by node aaaaaaaa.
System Action:
aaaaaaaa is disconnected.
User Action:
Investigate the reason for the abort.
Reason:
An invalid or unexpected SPDU has been received on a GET-BY-KEY service
System Action:
The invalid SPDU is traced to the activity log, and aaaaaaaa is disconnected.
User Action:
Investigate the cause of the invalid SPDU. If the error persists, contact your product support representative.
Reason:
This is the header message preceding the trace of an outgoing SDPU. The connection to aaaaaaaa is being traced because of an XNFTRACE command.
System Action:
A trace of the SPDU is written to the activity log.
User Action:
None
Reason:
This is the header message preceding the trace of an incoming SPDU. The connection to aaaaaaaa is being traced because of an XNFTRACE command.
System Action:
A trace of the SPDU is written to the activity log.
User Action:
None
Reason:
An XNF SDISCONNECT service, issued in response to an error, has failed. The error codes from the SDISCONNECT are displayed in the message. This message will normally follow another message describing the original error.
System Action:
None
User Action:
Refer to the VOS3 XNF Messages manual (Appendix B) for an explanation of the error codes.
Reason:
This message is part of a formatted trace of an incoming or outgoing SPDU. This message is the header preceding the trace of the XNF SPL used to send or receive the SDPU.
System Action:
None
User Action:
None
Reason:
This message is a hexadecimal (xxxxxxxx) and character (cccccccc) display of a trace of an SPL or SPDU used in XNF communications. This display follows another message which explains what the display is.
System Action:
None.
User Action:
None.
Reason:
This message is part of a formatted trace of an SPDU, logged because of an XNFTRACE command. This message displays the CEPID of the connection being traced.
System Action:
None
User Action:
None
Reason:
This message is part of a formatted trace being logged because of an XNFTRACE command. This message identifies the type of SPDU being traced, and its total length.
System Action:
None
User Action:
None
Reason:
Confirms successful completion of a DEFTERM command. DEFTERM is valid on VOS3 systems only.
System Action:
None
User Action:
None
Reason:
A DEFTERM command was entered, specifying a terminal name aaaaaaa that is already defined.
System Action:
The command is rejected.
User Action:
Correct the name and re-enter.
Reason:
Confirms successful completion of a DELTERM command. DELTERM is valid on VOS3 systems only.
System Action:
None
User Action:
None
Reason:
A DELTERM command was entered, specifying a terminal name aaaaaaaa that has not been defined by a previous DEFTERM command.
System Action:
The command is rejected
User Action:
Correct the name and re-enter
Reason:
This is the heading line of a SHOW DEFTERM display, which lists terminal definitions created by the DEFTERM command. DEFTERM is available on VOS3 systems only.
System Action:
None
User Action:
None
Reason:
The text line of a SHOW DEFTERM command. For each terminal definition (created by an earlier DEFTERM command) one of these messages will be displayed.
aaaa is the terminal name. This may be a name-mask, with asterisks as wildcards.
bbbb is the terminal type (3270 or 560/20)
ccc shows whether or not (Y or N) the terminal supports DBCS (Kanji)
ddd shows whether or not (Y or N) the terminal supports 7-color display.
eee shows whether or not (Y or N) the terminal supports extended highlighting (blink, reverse video and outlining).
System Action:
None.
User Action:
None.
Reason:
This message is issued during initialization of the SOLVE SSI region and as part of the SSI STATUS display. It provides information about the Configuration Data Interface (CDI) feature. It indicates that the feature is active and operational in the SOLVE SSI region.
P1 is the name of the SSI end point used for the CDI feature.
System Action:
None.
User Action:
None.
Reason:
An attempt to register an SSI end point to provide an interface to the Configuration Data Interface (CDI) feature failed.
P1 is the SSI EndPoint Services (EPS) return code.
P2 is the SSI end point name.
System Action:
The CDI feature is unavailable.
User Action:
This is an internal error. Contact Technical Support.
Reason:
This message is part of the SSI STATUS display and provides information about the Configuration Data Interface (CDI) feature. It shows the total number (P1) of active Endpoint Services (EPS) requests from all regions.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of a Configuration Data Interface (CDI) Endpoint Services (EPS) request buffer when tracing of CDI EPS requests and responses is enabled.
P1 identifies the EPS connection.
P2 identifies the NetMaster region.
P3 identifies the EPS function.
P4 identifies the EPS connection correlator.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of a Configuration Data Interface (CDI) Endpoint Services (EPS) response buffer when tracing of CDI EPS requests and responses is enabled.
P1 identifies the EPS connection.
P2 identifies the NetMaster region.
P3 identifies the EPS function.
System Action:
None.
User Action:
None.
Reason:
This message contains a hexadecimal and character dump of a Configuration Data Interface (CDI) Endpoint Services (EPS) request or response buffer. The message is written when tracing of CDI EPS requests and responses is enabled.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of a Configuration Data Interface (CDI) request buffer when tracing of the CDI requests and responses is enabled.
P1 identifies the EPS connection.
P2 identifies the type of CDI request buffer.
P3 is the address of the CDI request buffer.
P4 is the length of the CDI request buffer.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of a Configuration Data Interface (CDI) response buffer when tracing of the CDI requests and responses is enabled.
P1 identifies the EPS connection.
P2 identifies the type of CDI response buffer.
P3 is the address of the CDI response buffer.
P4 is the length of the CDI response buffer.
System Action:
None.
User Action:
None.
Reason:
This message contains a hexadecimal and character dump of a Configuration Data Interface (CDI) request or response buffer. The message is written when tracing of CDI requests and responses is enabled.
System Action:
None.
User Action:
None.
Reason:
This message shows UNIX System Services (USS) function results for a Configuration Data Interface (CDI) request. It is written when tracing of CDI requests and responses is enabled.
P1 identifies the EPS connection.
P2 identifies the USS function.
P3 is the USS return value.
P4 is the USS return code.
P5 is the USS reason code.
System Action:
None.
User Action:
None.
Reason:
Requests queued to the SOLVE SSI Configuration Data Interface (CDI) subtask are not being serviced in a timely manner. The subtask may have stalled.
P1 is the number of stalled requests.
System Action:
The SOLVE SSI region continues to monitor the CDI subtask.
This message is written approximately every 60 seconds until stalled requests are not detected.
User Action:
Ensure that the dispatching priority of the SOLVE SSI region enables subtasks in the region to be dispatched when ready.
If the problem persists, contact Technical Support.
Reason:
The Configuration Data Interface (CDI) feature is active in the SOLVE SSI region. The region attempted to attach a subtask under which CDI requests could be executed. The operation failed.
System Action:
The operation is retried every 60 seconds.
User Action:
See the SSI log for other messages that describe the cause of the error when attaching the subtask.
Reason:
The Configuration Data Interface (CDI) feature is active in the SOLVE SSI region. The region attached a subtask under which CDI requests could be executed. The subtask initialization failed.
P1 is the subtask return code.
P2 is the subtask error code:
00 indicates an expected termination (for example, the SOLVE SSI region is stopping) or the subtask abended.
04 indicates that the subtask engine cannot be initialized.
08 indicates that the SOLVE SSI region has insufficient virtual storage.
P3 is the subtask error subcode.
System Action:
The operation is retried every 60 seconds.
User Action:
See the SSI log for other messages that describe the cause of the subtask initialization error.
Reason:
The Configuration Data Interface (CDI) feature is active in the SOLVE SSI region. The region attached a subtask under which CDI requests could be executed. The subtask terminated.
P1 is the subtask return code.
P2 is the subtask error code:
00 indicates an expected termination (for example, the SOLVE SSI region is stopping) or the subtask abended.
04 indicates that the subtask engine cannot be initialized.
08 indicates that the SOLVE SSI region has insufficient virtual storage.
P3 is the subtask error subcode.
System Action:
If it is an expected termination, no action is taken; otherwise, the SOLVE SSI region waits 60 seconds and then reattaches the subtask.
User Action:
See the SSI log for other messages that describe the cause of an unexpected subtask termination.
Reason:
This is the title line of the SHOW CACHE CACHE=* display.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW CACHE CACHE= display. The list of caches can be filtered by specifying a specific or generic cache name (using * and ?). A message is issued for each matching cache defined to the region.
cache is the cache name.
hit% is the hit ratio. This is number of element references where the element is found in the cache divided by the total number of cache references. The high this figure, the better the cache is operating.
acc is the total number of open/query references to the cache.
act is the number of elements on the active queue.
ina is the number of elements on the inactive queue.
nld is the number of elements on the not loaded queue.
lft is the number of elements on the lifetime expiry queue.
size is the amount of storage in use in the cache.
lm-cnt is the limit count defined for this cache. When the number of inactive elements exceeds this value, elements are purged from the cache until the limit is under control.
lm-size is the limit size defined for this cache. When the size of inactive elements exceeds this value, elements are purged from the cache until the limit is under control.
load is the number of loads performed on this cache since the cache was defined.
drop is the number of drops performed on this cache since the cache was defined. Elements are dropped from the cache when the cache strategy in effect causes elements to be purged.
flsh is the number of elements purged from the cache using explicit flush commands.
System Action:
None.
User Action:
None.
Reason:
A SHOW CACHE command has been issued, but there are no caches currently defined to the region.
System Action:
None.
User Action:
None.
Reason:
A SHOW CACHE CACHE=xxx command has been issued, but no matching caches are defined to the region. CACHE=name can be specified to filter the list of caches shown. A specific or generic value (using * and ?) can be specified.
System Action:
None.
User Action:
None.
Reason:
This is the title line of the SHOW CACHE ELEMTYP=* display.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW CACHE ELEMTYP= display. A message is issued for each element type currently defined to the region.
elmt-typ is the element type name.
num is the number of elements in the cache for this element type, where the element is found in the cache divided by the total.
ldq is the number of element on the load queue, that is, waiting for a load thread to load the data into the cache.
thf is the number of free load threads, waiting for a load request.
thb is the number of busy load threads. A busy load thread is currently loading an element into the cache or not assigned.
thn is the number of non-assigned load threads. Non-assigned load threads are in between a CLOSE and a subsequent GETREQUEST or have started but not issued a GETREQUEST call to obtain new work.
slt-u is the number of hash slots in use. If num > sltu, this implies that different elements have hashed to the same hash slot.
slt-a is the number of hash slots allocated.
syn is the maximum length of the the hash synonym chain. Elements that hash to the same hash slot are chained together in a hash synonym chain.
cache is the cache name associated with this element type.
System Action:
None.
User Action:
None.
Reason:
A SHOW CACHE command has been issued, but there are no element types currently defined to the region.
System Action:
None.
User Action:
None.
Reason:
A SHOW CACHE ELEMTYP=xxx command has been issued, but no matching element types have been defined to the region. An element type filter can be specified.
System Action:
None.
User Action:
Check that a specified element type mask is specified correctly. You can issue a "SHOW CACHE ELEMTYP=*" to list of element types currently defined.
Reason:
This message forms part of the SHOW CACHE ELEMTYP= display. It is issued for any busy and non-assigned OML load thread. Typically, this should occur only for very short times.
System Action:
None.
User Action:
If repeated, SHOW CACHE ELEMTYP=xxx results in this message. This could indicate that the load thread is in trouble and is unable to issue a GETREQUEST call or terminate.
Reason:
This message forms part of the SHOW CACHE ELEMTYP= display. It is issued for any busy OML load procedure that is currently loading an element into the cache. The size in bytes, number of writes issued so far, and the element name being loaded are shown.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW CACHE ELEMTYP= display. It is issued for any busy and non-assigned assembler-based load thread. Typically, this should occur only for very short times.
System Action:
None.
User Action:
If repeated, SHOW CACHE ELEMTYP=xxx results in this message. This could indicate that the load thread is in trouble and is unable to issue a GETREQUEST call or terminate.
Reason:
The DD NMDRVCTL failed to open.
System Action:
System initialization is terminated.
User Action:
Provide a valid DD statement for DDName NMDRVCTL.
Reason:
An unrecognized operand was encountered in the input read from NMDRVCTL. A following message identifies the input.
System Action:
System initialization is terminated.
User Action:
For a description of the valid syntax for the input, see the Reference Guide.
Reason:
The program name specified on PGM= is longer than eight characters.
System Action:
System initialization is terminated.
User Action:
Specify a program name of one to eight characters in length.
Reason:
The LIST= operand was neither NO nor YES.
System Action:
System initialization is terminated.
User Action:
Specify a value of NO or YES for the LIST= operand.
Reason:
The ERROR= operand must start with either R or U followed by one to five digits (for example, U4095).
System Action:
System initialization is terminated.
User Action:
Specify a valid value for the ERROR= operand.
Reason:
The PARMSEP= operand must be one character in length.
System Action:
System initialization is terminated.
User Action:
Specify a valid value for the PARMSEP= operand.
Reason:
The PPREF= operand exceeds 1024 bytes in length.
System Action:
System initialization is terminated.
User Action:
Specify a value with a shorter length for the PPREF= operand.
Reason:
The WAIT= operand must be either ESM or VTAM.
System Action:
System initialization is terminated.
User Action:
Specify either ESM or VTAM for the WAIT= operand.
Reason:
The PSUFF= operand exceeds 1024 bytes in length.
System Action:
System initialization is terminated.
User Action:
Specify a value with a shorter length for the PSUFF= operand.
Reason:
A control line can have only one command.
System Action:
System initialization is terminated.
User Action:
Start commands on separate lines.
Reason:
The operand, p1, was not recognized.
System Action:
System initialization is terminated.
User Action:
For a list of valid operands, see the Reference Guide.
Reason:
The operand, p1, occurred more than once in the processed statement.
System Action:
System initialization is terminated.
User Action:
Specify p1 only once on the statement.
Reason:
The operand, p1, was invalid.
System Action:
System initialization is terminated.
User Action:
Correct the operand.
For valid syntax, see the Reference Guide.
Reason:
Variable substitution was requested, but the operating system does not support this.
System Action:
System initialization is terminated.
User Action:
Either change the specification to SUBS=NO or upgrade your operating system.
Reason:
The value for SUBS= must be either NO or YES.
System Action:
System initialization is terminated.
User Action:
Specify either NO or YES for SUBS=.
Reason:
The name of a variable must be 1 to 16 characters in length.
System Action:
System initialization is terminated.
User Action:
Specify a variable name of 1 to 16 characters.
Reason:
The name of a variable must consist of the characters A to Z, $, @, and #, with numerals allowable in all but the first character.
System Action:
System initialization is terminated.
User Action:
Specify a variable name with valid characters.
Reason:
The value supplied for a variable exceeds the length of the variable name plus 1.
System Action:
System initialization is terminated.
User Action:
Specify a value of the correct length.
Reason:
The number of variables defined exceeds the limit of 20.
System Action:
System initialization is terminated.
User Action:
Do not specify more than 20 variables.
Reason:
A buffer overflow condition occurred while calling the symbol substitution routine.
System Action:
System initialization is terminated.
User Action:
Increasing the region size, or decrease the number of variables for substitution.
Reason:
A syntax error was detected in column p1 of the input.
System Action:
System initialization is terminated.
User Action:
Correct the syntax.
For valid syntax, see the Reference Guide.
Reason:
A line ended with a continuation character, but EOF was encountered while attempting to read the continuation.
System Action:
System initialization is terminated.
User Action:
Either remove the continuation indicator, or provide the missing continuation line.
Reason:
This message follows an error message to echo the statement that was in error, p1.
System Action:
See the previous error message.
User Action:
See the previous error message.
Reason:
You specified WAIT=ESM, WAIT=VTAM or both, and the system is waiting for these events to occur.
System Action:
The system issues this message every 10 seconds until the events being waited on occur.
User Action:
None.
Reason:
You specified WAIT=ESM, causing a RACROUTE REQUEST=STAT call to be issued. This call failed.
p1 is the SAF return code.
p2 is the RACF return code.
p3 is the RACF reason code.
System Action:
The system continues to wait until the ESM is available, issuing this message every 10 seconds.
User Action:
For an explanation of the codes in this message, see IBM's Security Server RACROUTE Macro Reference.
Reason:
You specified WAIT=VTAM, causing VTAM OPEN to be issued. This failed with return code p1.
System Action:
The system continues to wait until VTAM is available, issuing this message every 10 seconds.
User Action:
Review the return code to determine the problem.
For an explanation of the return code in this message, see IBM's Communications Server: SNA Programming book.
Reason:
The specified combination of parameters for requesting dynamic allocation is not valid.
System Action:
System initialization is terminated.
User Action:
Correct the parameters in the request.
Note: For valid combinations of the parameters to allocate a data set dynamically, see the Reference Guide.
Reason:
DDName=* was specified without a previous allocation to concatenate to.
System Action:
System initialization is terminated.
User Action:
Ensure that a DD=name statement precedes the DDName.
Reason:
A concatenation to a SYSOUT allocation was attempted. This is not valid.
System Action:
System initialization is terminated.
User Action:
Recode the statement.
Reason:
More than four temporary data set names (that is, names starting with an ampersand (&)) were specified on an allocation.
System Action:
System initialization is terminated.
User Action:
Do not exceed four temporary data set names for an allocation.
Reason:
A temporary DSN has DISP=OLD without having been specified in another allocation with DISP=NEW.
System Action:
System initialization is terminated.
User Action:
Correct the temporary DSN specification.
Reason:
This message follows an error message to echo the statement that was in error, p1.
System Action:
See the previous error message.
User Action:
See the previous error message.
Reason:
This message is issued during NMSSI region startup if the Packet Analyzer is requested. Initialization of the Packet Analyzer failed for one of the following reasons:
The Packet Analyzer is supported on z/OS only.
The SSI startup parameter XMS (Cross-memory Services) is set to NO. The Packet Analyzer requires XMS=YES.
A required load module is missing from the load library.
System Action:
The NMSSI region terminates.
User Action:
Examine the reason, take corrective action, and retry.
Reason:
This message is issued in response to a PACTL command. It indicates that the level specified on that command is not a valid level.
Valid values for the LEVEL operand are:
2 or NOPACKETS
4 or NOSTATS
7 or STATSAMP
10 or FULL or ALL
System Action:
The PACTL command is ignored.
User Action:
Correct the command and retry.
Reason:
This message is issued in response to a PACTL command. It indicates that the level specified on that command is set as the new active Packet Analyser processing level.
System Action:
The Packet Analyzer now processes at the newly-requested level.
User Action:
None.
Reason:
This message is issued to the NMSSI log if the Packet Analyzer minute minder is activated. The message appears once every minute and provides statistics for the last minute.
The fields are as follows:
CPU: P1 is the CPU time used in seconds.
API: P2 is the number of database API requests received.
PKTS: P3 is the number of TCP/IP packets received.
EVT: P4 is the number of events received.
SMF: P5 is the number of SMF events received.
UUID: P6 is the number of update-userid requests received.
TRC: P7 is the number of TCP/IP packets truncated because of segmentation constraints.
System Action:
None.
User Action:
None.
Reason:
This message is issued to the NMSSI log if the Packet Analyzer minute minder is activated. The message is produced once every minute and provides statistics for the last minute.
The fields are as follows:
DDB-U: 1%-The percentage-used for the dynamic database
SDB-U: 2%-The percentage-used for the synchronous database
TDB-U: 3%-The percentage-used for the trace database
System Action:
None.
User Action:
None.
Reason:
This message is issued to the NMSSI log if the Packet Analyzer minute minder is activated. The message is produced once every minute and provides statistics for the last minute.
The statistics in this message relate to the decoupler, used to buffer TCP/IP packets and other events for processing.
The fields are as follows:
NQ: 1-The number of records enqueued to the decoupler
DQ: 2-The number of records dequeued from the decoupler
LS: 3-The number of records lost to buffer shortages
AW: 4-The number of actual waits for data
AT: 5-The number of timed waits for data
ST: 6-The number of decoupler segments touched
(%): 7-The percentage of decoupler segments touched, of the entire amount of decoupler segments
System Action:
None.
User Action:
None.
Reason:
This message is issued to the NMSSI log if the Packet Analyzer minute minder is activated. The message is produced once every minute and provides statistics for the last minute.
This specific message is produced only if the Packet Analyzer execution mode is ZIIP. The statistics in this message show the CPU time used by the Packet Analyzer, with a breakup between the time spent in Task mode and the time spent in SRB mode (which may be expended on a zIIP).
The fields are as follows:
CPU: 1-The total CPU time used by the Packet Analyzer
TASK: 2 (3%)-The CPU time and percentage of the total spent in Task mode
SRB: 4 (5%)-The CPU time and percentage of the total spent in SRB mode
M-SW: 6-The number of mode switches between Task and SRB mode
System Action:
None.
User Action:
None.
Reason:
This message is issued to the NMSSI log if the Packet Analyzer minute minder is activated. The message is produced once every minute and provides statistics for the last minute.
This specific message is produced only if the Packet Analyzer execution mode is zIIP. The statistics in this message show the CPU time used as derived from operating system-maintained fields. These values can be used to determine whether zIIP-eligible processing is actually being performed on a zIIP.
The fields are as follows:
PHTM: 1-The total pre-emptable-SRB CPU time expended in the last minute
ZONC: 2-CPU time that, while zIIP-eligible, was expended on a normal CP
ZNCT: 3-Enclave CPU time executed on a zIIP
%-ZIIP: 4-The percentage of zIIP-eligible CPU time actually executed on a zIIP
System Action:
None.
User Action:
If the percentage of time on a zIIP is 0, there may be no zIIPs online.
If the percentage of time on a zIIP is less than 100, available zIIPs may be in use or WLM priorities may be preventing the Packet Analyzer from using a zIIP.
Reason:
This message is part of the SSI STATUS display and provides information regarding TCP/IP stacks and stack management requests:
P1 is the number of current known stacks.
P2 is the number of previously known stacks, that is, occurrences of stacks that have terminated since SSI initialization.
P3 is the number of current stacks that have packet analysis enabled.
P4 is the number of packet analysis enable requests.
System Action:
None.
User Action:
None.
Reason:
This message is produced as part of an 'SSI STATUS' command. It indicates that the Packet Analyser facility, activated in this SOLVE SSI region, is not currently processing TCP/IP packets.
The reason can be:
The SOLVE SSI EXEC parm statement, or SSIIN data set, contains the statement 'PACKETS=NO'.
The PACTL command has been issued to the SOLVE SSI region, with the argument 'NOPACKETS'.
System Action:
None.
User Action:
If you want the SOLVESSI region packet analyser to process packets, you must restart the region and ensure that the JCL/SSIIN parameters do not include 'PACKETS=NO'.
Reason:
This message is part of the SSI STATUS display and provides information about Packet Analyzer.
It shows the Packet Analyzer version in the format aaa.bb.
aaa is the Packet Analyzer major version, for example, '116'.
bb is the Packet Analyzer minor version, for example, '00'.
Note: Leading zeroes are displayed.
System Action:
None.
User Action:
None.
Reason:
This message is produced as part of an SSI STATUS command. It shows the Packet Analyzer execution mode if the mode is not NORMAL.
The following mode values are available:
NORMAL - The Packet Analyzer is executing normally, that is, it is capturing packets and SMF events, and processing them.
RECORD - The Packet Analyzer is recording packets to a data set, which can be used for later playback.
PLAYBACK - The Packet Analyzer is in playback mode, that is, reading packets from a data set.
TEST - The Packet Analyzer is in test mode. No packet or SMF processing is performed.
System Action:
None.
User Action:
None.
Reason:
This message is produced as part of an SSI STATUS command. It shows the Packet Analyzer execution level if the execution level is not FULL.
The following level values are available:
FULL - The Packet Analyzer is executing normally. All packets are processed.
STATSAMP - The Packet Analyzer is processing 1 in n packets (for example, 1 in 10 packets) for statistics and scaling the statistics accordingly.
NOSTATS - The Packet Analyzer is processing packets but no statistics are gathered.
NOPACKETS - The Packet Analyzer is not processing packets. Only SMF events are processed.
System Action:
None.
User Action:
None.
Reason:
This message is produced as part of an SSI STATUS command. It provides information about the execution of the Packet Analyzer if the execution level is not FULL.
The status of packets, events, tracing, and statistics collection are shown.
The fields and their meanings are as follows:
EVENTS: aaa - Indicates whether SMF eventsare processed.
PACKETS: ppp - Indicates whether packets are processed.
TRACE: ttt - Indicates whether trace facilities are available.
STATS: sss sss - Indicates whether statistics are collected or sampled.
System Action:
None.
User Action:
None.
Reason:
This message is produced as part of an SSI STATUS command if the Packet Analyzer is executed in RECORD mode.
This message shows the stack for which packets are recorded, the number of packets recorded, and the number of records written to the record data set.
System Action:
None.
User Action:
None.
Reason:
This message is produced as part of an SSI STATUS command if the Packet Analyzer is executed in PLAYBACK mode.
This message shows the current playback status. The following values are available:
NOT STARTED - Playback has not started.
PENDING START - Playback start has been requested and will commence shortly.
RUNNING - Playback is in progress.
FINISHED -Playback is complete.
UNKNOWN - Unable to determine playback status.
System Action:
None.
User Action:
None.
Reason:
This message is produced as part of an SSI STATUS command and is also logged when the region starts.
This message shows the Packet Analyzer execution mode, as set by the PAEXMODE=mode SOLVE SSI parameter.
The current execution mode is shown. If this is not the same as the requested (or defaulted) mode, the requested mode is also shown. If this is the case, an NF1019 message follows this message and provides diagnostic information, except when the requested mode is BEST.
The modes are as follows:
TASK indicates that the Packet Analyzer is executing in task mode. (This is the default mode if no PAEXMODE parameter is specified)
ZIIP indicates that the Packet Analyzer is executing in SRB mode and can execute on a zIIP processor if eligible.
BEST indicates that the best available mode was requested. The actual mode will be TASK or ZIIP, depending on the availability of zIIP processors.
System Action:
None.
User Action:
If the requested mode is not the same as the actual mode and the requested mode was not BEST, use the diagnostic information in the following NF1019 message to determine the cause and then take appropriate action.
Reason:
This message may be produced as part of an SSI STATUS command and logged when the region starts.
This message is produced if the actual and requested Packet Analyzer execution modes are not the same (see message NF1018 for the modes and their meaning).
This message shows diagnostic information about why the requested mode cannot be used.
The diagnostic information shows two hexadecimal values, R0 and R1 values.
The R0 value is the primary diagnostic code. For some codes, supplementary information is in the R1 value.
The R0 values are as follows:
01xxyy00 - The requested execution mode is not available. xx is the requested execution mode (00-task, 04-sup, 0C-ZIIP). yy is the supported modes as a bitmap (80-task, 40-sup, 10-ziip)
02000000 - zIIP mode was requested. It is supported by the system and zIIP processors are available; however, the enabling APAR is not applied. See your support representative to obtain the enabling APAR.
0A000000 - Unable to obtain required storage.
14000000 - Unable to load a required system service module (IEAVAPE).
15000000 - Unable to load a required system service module (IEAVDPE).
16000000 - Unable to load a required system service module (IEAVPSE).
17000000 - Unable to load a required system service module (IEAVRLS).
18000000 - Unable to load a required system service module (IEAVXFR).
1E0000rr - Pause element allocation 1 failed. rr is the IEAVAPE return code.
1F0000rr - Pause element allocation 2 failed. rr is the IEAVAPE return code.
280000rr - WLM registration failed. rr is the IWM4CON macro return code. The R1 value is the reason code, that is, the R1 value returned from the macro.
290000rr - WLM enclave creation failed. rr is the IWM4ECRE macro return code. The R1 value is the reason code, that is, the R1 value returned from the macro.
2A0000rr - WLM enclave zIIP enablement failed. rr is the workload manager zIIP enablement macro return code. The R1 value is the reason code, that is, the R1 value returned from the macro.
System Action:
None.
User Action:
The diagnostic information in this message can be used to determine why the requested execution mode is not used.
Reason:
This message is issued during SSI initialization to indicate that the SSI has sucessfuly completed the TCP/IP stack discovery process.
System Action:
None.
User Action:
None.
Reason:
This message is issued during SSI initialiZation to indicate that the TCP/IP stack discovery process has failed and is being retried.
System Action:
The SSI retries every 5 seconds. This message is issued every minute. The retry process continues until a terminal failure occurs.
User Action:
If this message persists, contact Technical Support.
Reason:
This message is issued during SSI initialization to indicate that the TCP/IP stack discovery process has failed and may not be retried. The failure code (R15=P1) is displayed.
System Action:
Packet analysis for TCP/IP stacks is inoperative.
User Action:
This is an internal error. Contact Technical Support.
Reason:
This message is issued during SSI initialization to indicate that the TCP/IP stack discovery process has failed. The failure code (R15=P1) is displayed.
System Action:
Packet analysis for TCP/IP stacks is incomplete.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The SSI STACK REFRESH command for the identified stack name (P1) was accepted.
System Action:
The internal representation of the TCP/IP stack interfaces and home addresses are rebuilt.
User Action:
None.
Reason:
This is the header message for message NF1402 issued in response to the SSI SHOW STACKS command.
System Action:
None.
User Action:
None.
Reason:
This is the detail message issued in response to the SSI SHOW STACKS command. It provides the following details for a TCP/IP stack:
P1 is the stack name (the stack's STC/job name)
P2 is the stack type, IBM or TCPaccess.
P3 is the stack software version.
P4 is the SSID for the stack (TCPaccess only)
P5 indicates the packet analysis status for the stack:
System Action:
None.
User Action:
None.
Reason:
A request to refresh the configuration information about the indicated stack is complete.
System Action:
Processing continues.
User Action:
None.
Reason:
A change was detected in the configuration of the indicated stack.
System Action:
The Packet Analyzer database is updated with the changed configuration details.
User Action:
None.
Reason:
UNIX System Services are unavailable. Interface configuration and other stack information cannot be obtained for the IBM stack (P1) shown in the message.
System Action:
Processing continues.
User Action:
Review the system log and SSILOG for related messages.
Reason:
An attach for a module used to obtain configuration information from an IBM stack failed.
System Action:
The indicated stack is not hooked for packet processing.
User Action:
Review the system log and SSILOG for related messages.
Reason:
The task used to obtain configuration information from an IBM stack failed. The most likely reason is a storage shortage.
System Action:
The indicated stack is not hooked for packet processing.
User Action:
Review the system log and SSILOG for related messages.
Reason:
The module used to obtain configuration information from a CA TCPaccess stack failed. The most likely reason is a storage shortage.
System Action:
The indicated stack is not hooked for packet processing.
User Action:
Review the system log and SSILOG for related messages.
Reason:
An error occurred while attempting to obtain the configuration information for an IBM stack. A UNIX System Services (USS) error occurred. Diagnostic information is provided.
System Action:
The indicated stack is not hooked for packet processing.
User Action:
Review the system log and SSILOG for related messages.
Reason:
An error occurred while attempting to obtain the configuration information for a CA TCPaccess stack. Diagnostic information is provided.
System Action:
The stack is not hooked for packet processing.
User Action:
Review the system log and SSILOG for related messages.
Reason:
An error occurred while attempting to obtain the configuration information for a stack. A storage shortage occurred. Additional diagnostic information is provided.
System Action:
The stack is not hooked for packet processing.
User Action:
Increase the SSI region size and restart the SSI.
Reason:
An error occurred while attempting to obtain the configuration information for a stack. An internal error occurred. Additional diagnostic information is provided.
System Action:
The stack is not hooked for packet processing.
User Action:
Contact Technical Support and provide the following:
Reason:
An attempt to use the TCPaccess TLI interface failed. The message includes the following diagnostic data:
P1 is TCPaccess SSID.
P2 is the TLI macro name and/or function code, for example AOPEN.
P3 is the register 15 value in hex.
P4 is the register 0 value in hex.
System Action:
The socket request fails.
User Action:
R15/R0 values are documented in the TCPaccess Assembler API Programmers Reference manual. Use this information to resolve the error.
Reason:
An attempt to use the TCPaccess TLI interface failed because their was insufficient storage to obtain the work areas required for the calls.
System Action:
The socket request fails.
User Action:
Review the SSILOG for other related messages. Increase the SSI region size and restart.
Reason:
Packet analysis for a stack has been enabled or disabled as a result of a stack management request from a region. In the message:
P1 is stack name.
P2 is either ENABLED or DISABLED.
P3 and P4 are the user ID and region that issued the stack management request.
Note: The Packet Analyzer services all NetMaster regions in an LPAR. Packet analysis for a stack is required if any NetMaster region that is connected to the SOLVESSI has issued a management request.
A request to enable packet analysis for a stack from a NetMaster region will only take effect if packet analysis has not been enabled.
Similarly, a request to disable packet analysis for a stack from a NetMaster region will only take effect if no other region is requesting management of that stack.
This message indicates the first NetMaster region to enable packet analysis (for the stack) or the last to disable it.
System Action:
Packet analysis is enabled or disabled.
User Action:
None.
Reason:
The Packet Analyzer has detected that a TCP/IP stack (P1) has ended.
System Action:
None. When the stack is restarted, packet analysis for the stack will be automatically resumed if this was previously enabled.
User Action:
None.
Reason:
An attempt to enable or disable packet analysis has failed. In the message:
P1 is request type, either ENABLE or DISABLE
P2 is stack name
P3 is a return code
P4 is the failure reason, one of the following:
SEE PREVIOUS MESSAGE
STACK INACTIVE/UNHOOKABLE
INVALID TOKEN/NUMBER
API INACTIVE
UNKNOWN
System Action:
The request fails.
User Action:
If the reason is SEE PREVIOUS MESSAGE refer to the explanation of the previous message in the SSILOG. Other reasons represent an internal error that should be reported to Technical Support.
Reason:
Warm start connection pickup for a stack is complete. This message shows the results of the pickup.
P1 is the stack name.
P2 is the number of existing connections found.
P3 is the number of connection information records queued to the Packet Analyzer database processor.
P4 is the number of connection information records not queued due to a storage shortage.
P5 is the number of connection information records not queued due to some other error.
System Action:
None.
User Action:
None.
Reason:
Warm start connection pickup for a stack failed. This message shows the failure reason.
Possible failure reasons are as follows:
The attach request for the information gathering subtask failed. For more information, see other SSILOG messages. (The subtask name is NMSSI05A.)
The Packet Analyzer is unable to load the EZBNMIFR module, used to obtain the information.
The Packet Analyzer is unable to obtain storage for the results of the connection information request (for an initial buffer).
The Packet Analyzer is unable to obtain storage for the results of the connection information request (when a larger buffer is needed).
The call to the EZBNMIFR module failed with the displayed return value, return code, and reason code.
The information gathering subtask terminated unexpectedly. The abend or return code are displayed.
The information gathering subtask took too long.
System Action:
None.
User Action:
None.
Reason:
An error occurred while attempting to obtain IPv6 configuration information from an IBM stack.
The error means that the PTF for APAR PK11661 is not applied.
System Action:
IPv6 configuration information is not obtained.
User Action:
If you are using IPv6, apply the relevant PTF to your system.
Reason:
An attempt to record details for a TCP/IP stack (P1) has failed as there is insufficient storage to obtain the workareas required for record.
System Action:
The stack is not recorded. Packet analysis for the stack cannot be enabled.
User Action:
Review the SSILOG for other related messages. Increase the SSI region size and restart.
Reason:
The PASMFWRITE SSI parameter was either specified as 1 or defaulted to this value. This means that whether or not SMF records are written for a connection default to this value if not overridden by a matching Application Definition (ADF) record.
System Action:
Processing continues.
User Action:
None.
Reason:
An obsolete record was passed on a call from an SMF EXIT or a region. This indicates that an older version of SMF exits code is executing.
P1 is the number of obsolete calls since the previous message or since the SOLVE SSI started.
System Action:
The call is processed, but certain functions are ignored (such as updating byte counts).
User Action:
Contact Technical Support for advice about collecting diagnostics to identify which version of SMF exits are running.
Reason:
A call from an SMF exit with job name 1 and ASID 2 contains an unsupported function code 3 .
System Action:
The call is rejected.
User Action:
Determine what is running in the calling address space and report this to Technical Support.
Reason:
A $NMXEVNT call failed with return code 1 and feedback code 2.
System Action:
Processing continues.
User Action:
For R15=32 and R0=1, check that a SOLVE SSI providing the XEVENT service has been started on the LPAR where this message was issued. Otherwise, contact Technical Support.
Reason:
This message is part of the response to a SHOW SSISTATS command. It introduces the information about the identified Packet Analyzer database.
The database name can be DYNAM (the dynamic database), SYNCH (the synchronous databsae), or TRACE (the trace database).
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a SHOW SSISTATS command. It provides information about page usage in various Packet Analyser databases. (The database is identified in the preceding NF5010 message).
Each message displays several fields.
Identifies the information displayed in a field. It has one of the following values:
Displays the total number of pages (blocks) available in the database.
Displays the number of available (free) blocks in the database.
Displays the current number of used blocks in the database.
Displays the current percentage of the database used.
Displays the highest number of blocks used at any time.
Displays the highest percentage used at any time.
Displays the number of block GET requests.
Displays the number of block FREE requests.
Displays the number of GET requests that failed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a SHOW SSISTATS command. It introduces the information about the buffer pools for the Packet Analyzer trace database.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a SHOW SSISTATS command. It displays the following headings for subsequent NF5022 messages:
Indicates the buffer size.
Indicates the number of buffers per page.
Indicates the number of pages currently allocated to this pool.
Indicates the number of in-use buffers of this size.
Indicates the number of free buffers of this size.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a SHOW SSISTATS command. It displays information about a specific buffer pool for the Packet Analuzer trace database.
For information about what is displayed under each column, see the help for the NF5021 message.
System Action:
None.
User Action:
None.
Reason:
When reading the SSIDB, an error occurred. The return code (P1), Feedback (P2), and VSAM key (P3) are shown in hex.
System Action:
The file processing request fails.
User Action:
Contact Technical Support. The return code and feedback values are internal values and may not correspond to VSAM values.
Reason:
An attempt to convert an SSIDB record to an alternate format has failed. The message includes the following diagnostic data:
P1 is the feedback value from the conversion routine, shown in decimal and hex.
P2 is the internal ID of the field that caused the reformatting to fail. It is also shown in decimal and hex.
P3 is the VSAM record key in hex.
System Action:
The file processing request fails.
User Action:
This is an internal error. Contact Technical Support and provide them with the following information:
//PRINT EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SSIDB DD DISP=SHR,DSN=?prefix.SSIDB
//SYSIN DD *
PRINT INFILE(SSIDB) -
FROMKEY(X'hex key from message') -
COUNT(1) -
DUMP /*
Reason:
An attempt to add a record to the SSI database has failed. The message includes the following diagnostic data:
P1 is the feedback value shown in decimal and hex.
P2 is the internal ID of the field that caused the reformatting to fail. It is also shown in decimal and hex.
P3 is the VSAM record key in hex.
System Action:
The SSI database processing request fails.
User Action:
This is an internal error. Contact Technical Support and provide them with the following information:
//PRINT EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SSIDB DD DISP=SHR,DSN=?prefix.SSIDB
//SYSIN DD *
PRINT INFILE(SSIDB) -
FROMKEY(X'hex key from message') -
COUNT(1) -
DUMP /*
Reason:
During SSI initialization, records are retrieved from the SSIDB and are added to the SSI database. This message indicates that processing of the Packet Analyzer static database records from the SSIDB has completed without error.
System Action:
The population of the internal SSI database is complete.
User Action:
None.
Reason:
During SSI initialization, records are retrieved from the SSIDB and are added to the SSI database. There was insufficient storage to obtain the work areas required for this function.
System Action:
The population of the internal SSI database is incomplete.
User Action:
Review the SSILOG for other related messages. Increase the SSI region size and restart.
Reason:
During SSI initialization, the SSIDB file is read and Application Name Definition rules are loaded to the SSI database. During this process, the default rule, with order number 32767, was not processed. As a result, this message has been created. It usually occurs when the SSIDB is used for the first time (or has been deleted and redefined) because the default record cannot be deleted.
System Action:
SSI initialization continues.
User Action:
Application Name definition rules are maintained from a NetMaster region using the TCP/IP : Administration Menu, where all rules may be displayed and updated. All rules except the default rule may be deleted.
Display the default rule to ensure that the chosen values meet your requirements and update values as required.
Reason:
An attempt to convert an SSIDB record to an alternate format has failed. The message includes the following diagnostic data:
P1 is the feedback value from the conversion routine, shown in decimal and hex.
P2 is the internal ID of the field that caused the reformatting to fail. It is also shown in decimal and hex.
P3 is the VSAM record key in hex.
System Action:
The file processing request fails.
User Action:
This is an internal error. Contact Technical Support and provide them with the following information:
//PRINT EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SSIDB DD DISP=SHR,DSN=?prefix.SSIDB
//SYSIN DD *
PRINT INFILE(SSIDB) -
FROMKEY(X'hex key from message') -
COUNT(1) -
DUMP /*
Reason:
An attempt to add a record to the SSIDB database has failed. The message includes the following diagnostic data:
P1 is the RPL return code value shown in decimal and hex.
P2 is the RPL feedback value shown in decimal and hex.
P3 is the VSAM record key in hex.
System Action:
The SSI database processing request fails.
User Action:
Contact Technical Support. The return code and feedback values are internal values and may not correspond to VSAM values.
Reason:
The Packet Analyser database (1) dataspace (2) is now at least the indicated percentage (3) full.
System Action:
None.
User Action:
If this message continues to appear, with ever-increasing percentages, you may want to stop and start the Packet Analyser NMSSI region, increasing the values of the database size parameters.
Reason:
The Packet Analyser database (1) dataspace (2) storage has dropped below the threshold that produces NF5Z01 messages.
System Action:
None.
User Action:
None.
Reason:
The message indicates that PTF must be applied for APAR PK1161. The APAR relates to enhancements made to IPv6 support.
If the SOLVE SSI region (with Packet Analyzer enabled) is not used by CA NetMaster Network Management for TCP/IP, you can ignore this message.
System Action:
IPv6 packet processing is disabled for the indicated stack.
User Action:
Apply the relevant maintenance to the indicated stack's libraries, and restart the stack.
Reason:
This message is issued during SSI initialization, and as part of the SSI STATUS display. It provides information regarding the NetMaster Application Program Interface (API). The presence of this message indicates that the API is operational.
P1 is the name of the SSI endpoint used for the API.
System Action:
None.
User Action:
None.
Reason:
An attempt to register an SSI endpoint to provide the NetMaster Application Program Interface (API) has failed.
P1 is SSI EndPoint Services (EPS) return code.
P2 is the name of the SSI endpoint used for the API.
System Action:
The NetMaster API is unavailable.
User Action:
This is an internal error. Contact Technical Support.
Reason:
This message is part of the SSI STATUS display and provides information regarding the NetMaster Application Program Interface (API). The message shows the total number (P1) of active API requests from all NetMaster regions.
System Action:
None.
User Action:
None.
Reason:
This message is issued to the NMSSI log if an EPS connection from a region to the Packet Analyser component of NMSSI is dormant for more than five minutes. It indicates that the connection has been terminated by NMSSI.
The fields on the message can be used by Technical Support to diagnose problems.
Message NF7287 follows this message and provides more information.
System Action:
The EPS connection terminates.
User Action:
None.
Reason:
This message is issued to the NMSSI log following an NF7286 message and provides additional data.
System Action:
See Message NF7286
User Action:
None.
Reason:
A scan has started to locate the Event control blocks that can be purged.
This message is produced by the Packet Analyzer. The message is written to the SSILOG dataset for the NMSSI region that is executing the Packet Analyzer.
System Action:
None.
User Action:
None.
Reason:
A scan to locate Event control blocks that can be purged has ended, showing how many control blocks were purged (deleted).
This message is produced by the Packet Analyzer. The message is written to the SSILOG dataset for the NMSSI region that is executing the Packet Analyzer.
System Action:
None.
User Action:
None.
Reason:
This message is produced in response to the SSI STATUS command, if the Packet Analyser event facility is active, and shows that the EPS service for the Packet Analyzer event facility was registered. The service 'type' and 'name' are displayed.
System Action:
None.
User Action:
None.
Reason:
This message is produced in response to the SSI STATUS command, if the Packet Analyser event facility is active, and shows that registration of the EPS service for the Packet Analyzer event facility failed. The service type and name are displayed, as well as the return code from the failed registration request.
System Action:
None.
User Action:
Contact your support representative.
Reason:
This message is produced as part of the SSI STATUS command if the Packet Analyzer event facility is active. It follows the NFGZ01 message, and indicates the number of active requests for the service described in the preceding NFGZ01 message
System Action:
None.
User Action:
None.
Reason:
Packet analysis for a TCP/IP stack has been disabled because the SOLVE SSI region has terminated. The stack name (P1) and type (P2 - IBM or TCPaccess) is shown.
System Action:
IP packet analysis for the stack is disabled.
User Action:
None.
Reason:
Packet analysis for a TCP/IP stack has been disabled because the stack has terminated. The stack name (P1) and type (P2 - IBM or TCPaccess) is shown.
System Action:
IP packet analysis for the stack is disabled.
User Action:
None.
Reason:
A SOLVESSI region has been configured with the Packet Analyzer feature but initialization of the region has failed. The failure reason (P1) is shown:
This indicates that the Packet Analyzer feature is active in another SOLVESSI region on this LPAR. Only one SOLVESSI region per LPAR may be configured with this feature.
System Action:
The SSI terminates.
User Action:
Amend the appropriate SOLVESSI parameter member to remove the PKTANALYZER SSI parameter. This parameter enables the Packet Analyzer feature.
Reason:
Packet analysis for a TCP/IP stack has been enabled. The stack name (P1) and type (P2 - IBM or TCPaccess) is shown.
System Action:
IP packet analysis for the stack is enabled.
User Action:
None.
Reason:
This message is written to the system console as part of an SVC dump title when a packet intercept for an IBM stack ABENDs during processing. The message text includes the abend completion code (P1 - Sxxx/Unnnn), the IBM stack name (P2), the date (P3), and time of the ABEND (P4).
This message is followed by messages NFSM91 and NFSM92, both of which contain additional information describing the ABEND.
System Action:
Diagnostic data describing the ABEND is captured and the packet inter- cept is disabled.
User Action:
Contact Technical Support and provide the following:
Reason:
A packet intercept for an IBM stack abended during processing and an SVC dump was requested using the SDUMPX macro interface. The message text includes a description (P1) of the SDUMPX return code and the IBM stack name (P2).
The description (P1) of the SDUMPX return code will be one of the following:
The SVC dump was successfully captured.
The SVC dump was suppressed by CHNGDUMP.
The SVC dump was suppressed by SLIP NODUMP.
The SVC dump was suppressed by DAE.
The SVC dump request failed with the return code shown in the description.
System Action:
See message NFSM90.
User Action:
See message NFSM90.
Reason:
A packet intercept for an IBM stack abended during processing and this multiline message contains information describing the ABEND. The message text includes the following:
P1 is the ABEND completion code (Sxxx/Unnnn)
P2 is the ABEND reason code
P3 is the IBM stack name
P4 is the PSW at the time of the ABEND
P5 is the interrupt code
P6 is the instruction length code
P7 to P10 are a pair of access registers and general purpose registers at the time of the ABEND. These are repeated 8 times, once for each of the 8 pairs of registers 0 through 15.
System Action:
See message NFSM90.
User Action:
See message NFSM90.
Reason:
Packet analysis for a TCP/IP stack has been disabled. The stack name (P1), type (P2 - IBM or TCPaccess) and reason (P3) are shown. Possible reasons are:
An internal error has occurred.
An internal error has occurred.
The SOLVE SSI region that includes Packet Analyzer support has terminated.
A request to disable packet analysis for this stack has been actioned.
System Action:
IP packet analysis for the stack is disabled.
User Action:
Review the message reason. The following reasons represent normal situations:
SOLVESSI TERMINATION
DISABLE REQUEST
The following reasons are abnormal situations:
INTERCEPT ABENDED
INTERCEPT EXIT RETURNED NONZERO RC
If these occur, contact Technical Support and provide the following:
Reason:
This message is part of the SSI STATUS command when the SOLVESSI region is configured with the Packet Analyzer feature. It indicates that the feature is active.
System Action:
None.
User Action:
None.
Reason:
This message is part of the SSI STATUS command when the SOLVESSI region is configured with the Packet Analyzer feature. It includes information that may be required by your product supplier in the event of a product malfunction.
System Action:
None.
User Action:
None.
Reason:
A SOLVE SSI region is configured with the IPSec Network Management Interface (IPSEC NMI) feature; however, initialization of the feature failed.
The failure reason (P1) is shown:
Indicates that the IPSec Network Management Interface feature is not supported by the current operating system or release level. This feature requires z/OS V1R9 or a later release.
Indicates that the IPSec Network Management Interface feature is active in another SOLVE SSI region on this LPAR. You can configure only one SOLVE SSI region per LPAR with this feature.
System Action:
The SSI terminates.
User Action:
Amend the appropriate SOLVE SSI parameter member to remove the IPSECNMI SSI parameter. This parameter enables the IPSec Network Management Interface feature.
Reason:
This message is issued during initialization of the SOLVE SSI region and is part of the SSI STATUS display. It provides information about the IPSec Network Management Interface (IPSEC NMI) feature. This message indicates that the feature is active and operational in the SOLVE SSI region.
P1 is the name of the SSI endpoint used for the IPSECNMI feature.
System Action:
None.
User Action:
None.
Reason:
An attempt to register an SSI endpoint to provide an interface to the IPSec Network Management Interface (IPSEC NMI) feature failed.
P1 is SSI EndPoint Services (EPS) return code.
P2 is the name of the SSI endpoint used for the API.
System Action:
The IPSec Network Management Interface feature is unavailable.
User Action:
This is an internal error. Contact Technical Support.
Reason:
This message provides information about the IPSec Network Management Interface (IPSEC NMI) feature. The message shows the total number (P1) of active Endpoint Services (EPS) requests from all CA NetMaster regions and the status (P2) of the IPSEC NMI subtask.
The following list shows the possible IPSEC NMI subtask status values and their meanings:
Indicates that the subtask has successfully connected to the IPSec network management server.
Indicates that the subtask is in the process of connecting to the IPSec network management server.
Indicates that the subtask could not be attached.
Indicates that the subtask failed to initialize successfully.
Indicates that the subtask has been posted to terminate.
Indicates that the subtask has ended.
System Action:
None.
User Action:
Investigate and perform action based on the status:
No is action required. The subtask is connected successfully.
Wait for a short time, then check the status again. If the status does not change to STARTED after a short time, ensure that the IPSec network management server is functioning properly. The IPSec network management server is implemented by the IKE daemon.
For information about diagnosing IKE daemon problems, see the IBM z/OS Communications Server IP Diagnosis Guide.
The subtask could not be attached. This condition usually indicates an installation or implementation error (for example, the subtask load module is not in the load library), or region error (for example, there is insufficient virtual storage in the SOLVE SSI region).
Look for more error messages in the SOLVE SSI log, SOLVE SSI job log, and z/OS SYSLOG.
The subtask failed to initialize successfully. This condition usually indicates a configuration error (for example, the SOLVE SSI region is not authorized to create a socket, the IKE daemon is not started, or the SOLVE SSI region is not authorized to connect to the IPSec network management server).
Authorization problems can occur if the OMVS segment for the IKE daemon or the SOLVE SSI region is not set up correctly.
Look for more error messages in the SOLVE SSI log, SOLVE SSI job log, and z/OS SYSLOG.
For information about how to set up an OMVS segment, see the Installation Guide.
The subtask has been posted to terminate. Either the SOLVE SSI region is shutting down, or an SSI command to reconnect to the IPSec network management server was issued and the subtask is being stopped and restarted.
The subtask has ended. Either the SOLVE SSI region is shutting down or the subtask ended unexpectedly (for example, ABEND). In the latter case, the subtask is reattached after a short delay (60 seconds).
For an ABEND, look for more error messages in the SOLVE SSI log, SOLVE SSI job log, and z/OS SYSLOG.
Reason:
This message precedes a dump of an IPSec Network Management Interface (IPSEC NMI) Endpoint Services (EPS) request buffer. The message is written when tracing of IPSEC NMI EPS requests and responses is enabled.
P1 is the EPS connection identifier.
P2 is the CA NetMaster region identifier.
P3 is the EPS function name.
P4 is the EPS connection correlator.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of an IPSec Network Management Interface (IPSEC NMI) Endpoint Services (EPS) response buffer. The message is written when tracing of IPSEC NMI EPS requests and responses is enabled.
P1 is the EPS connection identifier.
P2 is the CA NetMaster region identifier.
P3 is the EPS function name.
System Action:
None.
User Action:
None.
Reason:
This message contains a hexadecimal and character dump of an IPSec Network Management Interface (IPSEC NMI) Endpoint Services (EPS) request or response buffer. The message is written when tracing of IPSEC NMI EPS requests and responses is enabled.
System Action:
None.
User Action:
None.
Reason:
Requests queued to the SOLVE SSI IPSec Network Management Interface (IPSEC NMI) subtask are not being serviced in a timely manner. The subtask can be stalled.
P1 is the number of stalled requests.
System Action:
The SOLVE SSI region continues to monitor the IPSEC NMI subtask.
This message is written approximately every 60 seconds until no stalled requests are detected.
User Action:
Ensure that the dispatching priority of the SOLVE SSI region allows subtasks in the region to be dispatched when ready.
Ensure that the IPSec network management server is functioning properly. The IPSec network management server is implemented by the IKE daemon. For information about diagnosing IKE daemon problems, see the IBM z/OS Communications Server IP Diagnosis Guide.
For assistance, contact Technical Support.
Reason:
The IPSec Network Management Interface (IPSEC NMI) feature is active in the SOLVE SSI region; the region is connected to the IPSec network management server.
System Action:
None.
User Action:
None.
Reason:
The IPSec Network Management Interface (IPSEC NMI) feature is active in the SOLVE SSI region. The region attempted to attach a subtask in order to establish a connection to the IPSec network management server. The subtask attach failed.
System Action:
The operation is retried every 60 seconds.
User Action:
See the SSI log for other messages that describe the cause of the subtask attach error.
Reason:
The IPSec Network Management Interface (IPSEC NMI) feature is active in the SOLVE SSI region. The region attached a subtask in order to establish a connection to the IPSec network management server. The subtask initialization failed.
P1 is the subtask return code.
P2 is the subtask error code and is one of the following values:
00 - The subtask ABENDed.
04 - The subtask engine cannot be initialized.
08 - The subtask invoked a UNIX System Services (USS) callable service and the service returned an error.
12 - The subtask made a request to the IPSec network management server and the server returned an error.
16 - Insufficient virtual storage is available in the SOLVE SSI region.
P3 is the subtask error subcode.
System Action:
For USS callable service errors and IPSec network management server errors, other messages are written to the SSI log that provide more information about the error.
The operation is retried every 60 seconds.
User Action:
See the SSI log for other messages that describe the cause of the subtask initialization error.
Reason:
The IPSec Network Management Interface (IPSEC NMI) feature is active in the SOLVE SSI region. The region attached a subtask in order to establish a connection to the IPSec network management server. The subtask terminated.
P1 is the subtask return code.
P2 is the subtask error code and is one of the following values:
00 - It is an expected termination (for example, the SOLVE SSI region is stopping) or the subtask ABENDed.
04 - The subtask engine cannot be initialized.
08 - The subtask invoked a UNIX System Services (USS) callable service and the service returned an error.
12 - The subtask made a request to the IPSec network management server and the server returned an error.
16 - Insufficient virtual storage is available in the SOLVE SSI region. P3 is the subtask error subcode.
System Action:
For USS callable service errors and IPSec network management server errors, other messages written to the SSI log provide more information about the error.
If it is an expected termination (for example, the SOLVE SSI region is stopping), no action is taken; otherwise, the SOLVE SSI region waits 60 seconds and then reattaches the subtask.
User Action:
See the SSI log for other messages that describe the cause of an unexpected subtask termination.
Reason:
The IPSec Network Management Interface (IPSEC NMI) feature is active in the SOLVE SSI region. The region attached a subtask in order to establish a connection to the IPSec network management server.
The subtask invoked a UNIX System Services (USS) callable service and the service returned an error.
P1 is the USS callable service name.
P2 is the USS callable service return value.
P3 is the USS callable service return code.
P4 is the USS callable service reason code.
System Action:
The SOLVE SSI region waits 60 seconds and then reattaches the subtask.
User Action:
For more information about the error, see the z/OS publication UNIX System Services Messages and Codes.
Reason:
The IPSec Network Management Interface (IPSEC NMI) feature is active in the SOLVE SSI region. The region attached a subtask in order to establish a connection to the IPSec network management server.
The subtask invoked the BPX1CON UNIX System Services (USS) callable service to connect to the IPSec network management server and the service returned an error that indicates that the IPSec network management server is not started.
P1 is the BPX1CON USS callable service return value.
P2 is the BPX1CON USS callable service return code.
P3 is the BPX1CON USS callable service reason code.
System Action:
The operation is retried every 60 seconds.
User Action:
Start the IKE daemon.
Reason:
The IPSec Network Management Interface (IPSEC NMI) feature is active in the SOLVE SSI region. The region attached a subtask in order to establish a connection to the IPSec network management server.
The connection to the IPSec network management server was terminated by the server.
P1 is the IPSec network management server termination return code (Errno value).
P2 is the IPSec network management server termination reason code (ErrnoJr value).
System Action:
The operation is retried every 60 seconds.
User Action:
For more information about the termination return and reason codes, see the z/OS publication Communications Server IP and SNA Codes.
Reason:
Initialization of the SOLVE SSI IPSec Network Management Interface (IPSEC NMI) subtask is not being completed in a timely manner. The subtask is in the process of connecting to the IPSec network management server.
System Action:
The SOLVE SSI region continues to monitor the IPSEC NMI subtask.
This message is written approximately every 60 seconds until the IPSEC NMI subtask connects to the IPSec network management server and subtask initialization completes.
User Action:
Ensure that the dispatching priority of the SOLVE SSI region allows subtasks in the region to be dispatched when ready.
Ensure that the IPSec network management server is functioning properly. The IPSec network management server is implemented by the IKE daemon. For information about diagnosing IKE daemon problems, see the IBM z/OS Communications Server IP Diagnosis Guide.
For assistance, contact Technical Support.
Reason:
This message precedes a dump of an IPSec network management server request buffer. The message is written when tracing of server requests and responses is enabled.
P1 is the address of the request buffer.
P2 is the length of the request buffer.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of an IPSec network management server response buffer. The message is written when tracing of server requests and responses is enabled.
P1 is the address of the response buffer.
P2 is the length of the response buffer.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of an IPSec network management server record buffer. The message is written when tracing of server requests and responses is enabled.
P1 is the address of the record buffer.
P2 is the length of the record buffer.
System Action:
None.
User Action:
None.
Reason:
This message contains a hexadecimal and character dump of an IPSec network management server request or response buffer. The message is written when tracing of server requests and responses is enabled.
System Action:
None.
User Action:
None.
Reason:
This is a VTAM message returned in response to a VTAM command or delivered by the PPO interface.
System Action:
The action depends on the VTAM message.
User Action:
See IBM's Communications Server SNA Messages manual for your level of VTAM.
To determine the VTAM level, issue the STATUS command and see message N11421.
This message definition, NIST000I, is used for all VTAM message help requests. You can modify it using CAS to provide more specific help.
Reason:
The named OML procedure was flushed before execution, as the region was terminated, for example, due to user logoff.
System Action:
None.
User Action:
None.
Reason:
The named OML procedure was not executed for the given reason.
System Action:
The procedure is not executed.
User Action:
Correct the problem and resubmit the procedure for execution if required.
Reason:
Data supplied for a verb operand was not of the indicated type.
System Action:
An error is raised.
User Action:
Correct the supplied data.
Reason:
An OML compiled procedure attempted to execute the named verb, The named verb is not known in this SOLVE system. This error can only occur for an OML procedure loaded from object code, not source code.
System Action:
An error is raised.
User Action:
Check to see if the INCLUDE/EXCLUDE JCL parms or licence have disabled a required feature.
Reason:
The indicated argument to the named built-in function is not a valid value.
System Action:
An error is raised.
User Action:
Correct the input value.
Reason:
An attempt to call the named external function failed. The external function could not be found in the procedure library.
System Action:
An error is raised.
User Action:
Check the spelling of the function name. If correct, ensure that the function code is in the procedure library.
Reason:
An attempt to load or compile the indicated function or package failed.
System Action:
An error is raised.
User Action:
Check the error messages for the compilation failure reason. Correct the problem and execute the procedure again.
Reason:
After loading the named file, it was not of the required type (function or package).
System Action:
An error is raised.
User Action:
Ensure that the name of the requested function or package is correct.
Reason:
An attempt was mode to perform a function call to an NCL procedure. NCL does not support user written functions.
System Action:
An error is raised.
User Action:
Check the requested function name.
Reason:
The named package does not contain a first-level function of the indicated name.
System Action:
An error is raised.
User Action:
Check the requested function name.
Reason:
The named package contains a first-level procedure of the indicated name, however a FUNCTION was requested. A non-function (such as PROCEDURE) cannot be executed by a function call.
System Action:
An error is raised.
User Action:
Check the requested function name.
Reason:
A compiled OML procedure attemped to execute the named builtin function. However, the named function is not known in this SOLVE system. This error can only occur for an OML procedure loaded from object code, not source code.
System Action:
An error is raised.
User Action:
Check to see if the INCLUDE/EXCLUDE JCL parms or licence have disabled a required feature.
Reason:
An attempt to call the named external procedure failed. The external procedure could not be found in the procedure library.
System Action:
An error is raised.
User Action:
Check the spelling of the procedure name. If correct, ensure that the procedure code is in the procedure library.
Reason:
An attempt to load or compile the named procedure or package failed.
System Action:
An error is raised.
User Action:
Check the error messages for the reason that the compilation failed. Correct the problem and execute the procedure again.
Reason:
The named file was loaded. It was not of the required type (procedure or package).
System Action:
An error is raised.
User Action:
Check the name of the requested procedure or package.
Reason:
The named package does not contain a first-level procedure with the indicated name.
System Action:
An error is raised.
User Action:
Check the name of the requested procedure.
Reason:
The named package contains a first-level function of the indicated name, however a PROCEDURE was requested. A non-procedure (such as FUNCTION) cannot be executed by a procedure call.
System Action:
An error is raised.
User Action:
Check that the name of the requested procedure is correct.
Reason:
This is a trace message for OML procedures. It traces labels.
System Action:
None.
User Action:
None.
Reason:
This is a trace message for OML procedures. It traces OML statements.
System Action:
None.
User Action:
None.
Reason:
This is a trace message for OML procedures. It traces the entry into new OML procedures or functions.
System Action:
None.
User Action:
None.
Reason:
This is a trace message for OML procedures. It traces OML expression processing.
The values for expression type are:
The expression source is displayed
A literal value has been pushed
A variable value has been pushed
The result of a binary operator has been pushed
The result of a prefix (unary) operator has been pushed
A function result has been pushed
This is the expression final result
If the 'value' is a null character string then is is represented by the string '<NULL>'
System Action:
None.
User Action:
None.
Reason:
This message provides a short description of an OML execution error.
System Action:
An error has been raised.
User Action:
Examine the message for the error reason and take appropriate corrective action.
Reason:
This message is used as the OML error description when no other message is available.
System Action:
An error has been raised.
User Action:
Use the error code and error location to determine the cause of the error.
Reason:
This message is produced when an OML process terminates.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML process is flushed.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML system procedure terminates in error.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML procedure terminates in error. The NCLID (aaaaaa), file (bbbbbbbb), line (cccccccc), error code (ddd), and error condition (eeee) are displayed.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML procedure terminates in error. Error information messages follow.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML procedure terminates in error. An execution stack traceback follows.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the procedure type and name, source file, line, column and decompiled statement in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It indicates that an ON-block was in the execution stack and the information that follows is derived from it.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It indicates that a GOSUB statement was in the execution stack. A dump of the GOSUB statement is displayed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It indicates that a call from another procedure (which could be a function call) was found. The following information is about the calling procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It show the error code that raised an ON-BLOCK or terminated the procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows any available error message from the error that raised an ON-BLOCK or terminated the procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the condition name from the error that raised an ON-BLOCK or terminated the procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the location of the error that raised an ON-BLOCK or terminated the procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the type and name of the procedure that had the error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the source of the statement in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the verb keyword that caused the error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the value that was in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the second value, if available, that was in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the source variable name, if available, that was in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the target variable name (after resolution, if available) that was in error.
System Action:
None.
User Action:
None.
Reason:
The OML procedure bbbbbbb set a return code aaa indicating that update of it's target object instance was to be ignored. Execution of the system method routine is bypassed and the object instance is not updated in the repository.
System Action:
The message is returned to the client in the reply SDU.
User Action:
None.
Reason:
The Object Services generated reply to the client failed.
System Action:
The message is logged.
User Action:
Check the activity log for possible causes.
Reason:
An Object Services request could not be processed due to insufficient virtual storage.
System Action:
The request is terminated.
User Action:
Look for possible causes of high storage utilisation. Increase virtual storage address space size.
Reason:
Object Services could not initialize the aaaaaa method for an object request. This usually indicates a problem with building the Mapped Data Objects (MDOs) or may indicate a resource shortage.
System Action:
The method is not executed.
User Action:
Check the object maps are valid. Check the activity log for additional messages.
Reason:
This message indicates that a variable name which was encountered during execution of an OML process is invalid. The text following the colon shows the reason why the variable name is invalid.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the invalid variable name.
Reason:
This message indicates that the name passed for an MDO variable does not constitute a valid name for an MDO. This can be because the name contains invalid characters, or contains a name segment which is longer than 32 bytes.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the MDO variable name.
Reason:
An attempt was made to assign data to an MDO variable, but the assignment was rejected by Mapping Services.
p1 is the return code,
p2 is the feedback code from the MDO assignment.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
For an explanation of the return and feedback codes, see the NCL Reference Guide. See system variables &ZMDORC and &ZMDOFDBK.
For programmers, to find out the reason for the rejection, change the statement to use the ASSIGN verb with CONTROL MDOCHK in effect. This change will cause more error information to be produced.
Reason:
OML supports returning the value of many NCL system variables during substitution, for a PANEL or certain built-in functions. This error indicates that the variable being accessed is recognised as an NCL system variable, but is not one which OML supports.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Change the variable name to use the correct OML system variable name.
Reason:
This message is produced during processing of a DEBUG DISPLAY command. It shows the name of a variable which is included in the display. This message is followed by further messages which show the data for the variable.
System Action:
None.
User Action:
None.
Reason:
This message is produced during processing of a DEBUG DISPLAY command. It shows the length of data contained in a variable (aaaaaaaa), the MODFLD number for the variable (bbbbbb), and attributes for the variable (ccc). The attribute value can contain the following values:
M - the variable is flagged as being modified (e.g. ASSIGN OPT=SETMOD)
E - the variable is flagged as being in error (e.g. ASSIGN OPT=SETERR)
O - the variable is flagged as being output (e.g. ASSIGN OPT=SETOUT)
System Action:
None.
User Action:
None.
Reason:
This message is produced during processing of a DEBUG DISPLAY command. It shows the data assigned to a variable. The data will be in the format designated by the FMT= operand on the DEBUG DISPLAY command. If FMT=CHAR is specified, the data is in character format and may be up to 256 bytes long. If FMT=HEX is specified, the data can be up to 256 bytes long (which is 128 bytes of the data in hex-expanded format). If FMT=DUMP is specified, a dump of the variable data follows, with message number NM4020.
System Action:
None.
User Action:
None.
Reason:
This message is produced during processing of a DEBUG DISPLAY command. It shows the data assigned to a variable in hex dump format. ooo is the offset (in hexadecimal) in the variable, xxxxxxxx is the variable data in hex format, and cccccccc is the variable data in character format.
System Action:
None.
User Action:
None.
Reason:
An ASSIGN verb has specified the RANGE= operand with an MDO assignment, but the MDO name supplied does not support the RANGE= operand. The MDO name must be a variable indexed name (e.g. MDO=A.B.C{*} )
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the MDO name or remove the RANGE= operand.
Reason:
An ASSIGN verb has specified an MDO to MDO assignment, and one of the MDO names is variable indexed but the other is not. This is invalid. If a variable indexed name is specified, both names must be variable indexed.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the MDO names and retry.
Reason:
An ASSIGN verb has specified the NOVALIDATE option on an assignment into an MDO variable, but the MDO name is variable indexed, which is invalid.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the MDO name or remove the NOVALIDATE option and retry.
Reason:
An OML procedure has attempted to execute a MSGREAD, MSGCONT or MSGDEL verb, but the procedure is not executing as a MSGPROC. These verbs are only valid from a MSGPROC procedure.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the procedure is terminated.
User Action:
Either remove the MSGREAD, MSGCONT or MSGDEL verb, or start the procedure as a MSGPROC using a PROFILE MSGPROC=procname command or defining the procedure as MSGPROC in the users UAMS definition.
Reason:
An OML procedure has attempted to execute a MSGREAD, or MSGCONT verb but the update of the $MSG MDO has failed. The message shows the return code (aa) and feedback (bb) values returned from Mapping Services which describe the error.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the procedure is terminated.
User Action:
Investigate the reason for the failure using the return code and feedback values.
Reason:
The &$INT. MDO name cannot be used as the target of an INTREAD MDO= operation.
System Action:
The verb signals an error.
User Action:
Change the INTREAD statement to use some other MDO name.
Reason:
An INTCONT statement was issued when no message was available from an INTREAD statement.
System Action:
The verb signals an error.
User Action:
Check the procedure logic.
Reason:
A PANEL statement was executed in an environment that does not support full-screen panels (for example, BSYS).
System Action:
The verb signals an error.
User Action:
Check the procedure logic.
Reason:
A VARTABLE statement FIELDS or VARS list keywords error was detected. The reason for the error follows the dash (-).
System Action:
The verb signals an error.
User Action:
Correct the VARTABLE verb operands.
Reason:
A VARTABLE statement attempted to access or update an entry that contains an MDO, using relative field access.
System Action:
The verb signals an error.
User Action:
Correct the VARTABLE verb operands.
Reason:
Source data for a VARTABLE statement exceeds the maximum length that can be stored in an entry.
System Action:
The verb signals an error.
User Action:
Correct the VARTABLE verb operands.
Reason:
The limit on the number of locks for a process has been reached.
System Action:
The lock request is not honored.
User Action:
Determine the number of currently active LOCKs using the SHOW LOCKS command and determine if the number of requests is excessive.
The default is 32767 locks per executing region.
Reason:
An OML procedure has executed a PPI SEND or PPI ALERT verb with the VARS= operand specified. The total amount of data from the specified variables exceeds the maximum supported size.
System Action:
An error is raised. If no relevant ON Block exists the procedure is terminated.
User Action:
Reduce the amount of data to be sent.
Reason:
An OML procedure has executed a PPI RECEIVE verb with the MDO= operand specified. During assignment of the data to the MDO, Mapping Services encountered an error.
System Action:
An error is raised. If no relevant ON Block exists the procedure is terminated.
User Action:
Correct the mapping of the MDO.
Reason:
An OML procedure has executed a PPI RECEIVE verb to receive data via a PPI connection. The procedure currently has no connection to PPI.
System Action:
An error is raised. If no relevant ON Block exists the procedure is terminated.
User Action:
Ensure that a PPI DEFINE has been issued. If so, check that the return code from the PPI define indicated that the operation was successful.
Reason:
A LOGREAD, LOGDEL, or LOGCONT statement was issued from an NCL process other than LOGPROC.
System Action:
The verb signals an error.
User Action:
These statements are not valid unless used in the LOGPROC procedure. Check that SYSPARMS LOGPROC=xxxx was used to start the procedure.
Reason:
An OML procedure has attempted to execute a LOGREAD, or LOGCONT verb but the update of the $MSG MDO has failed. The message shows the return code (aa) and feedback (bb) values returned from Mapping Services which describe the error.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the procedure is terminated.
User Action:
Investigate the reason for the failure using the return code and feedback values.
Reason:
The MDO supplied to an ENCODE or DECODE statement is invalid.
System Action:
None.
User Action:
Ensure that different source and target MDOs are used. Check the syntax of the MDO names and verify them against their respective MAP definitions.
Reason:
An internal MDS error has occurred.
System Action:
None.
User Action:
Contact your product support representative.
Reason:
The internal recursion stack limit was exceeded while processing an ENCODE or DECODE operation, possibly caused by too many segments in a compound name.
System Action:
None.
User Action:
Reduce number of name segments in mdo name. May require redefinition of the map.
Reason:
An ENCODE or DECODE statement has invalid syntax.
System Action:
None.
User Action:
Correct the statement and retry.
Reason:
The TRANSLATE= operand supplied to an ENCODE or DECODE statement is invalid.
System Action:
None.
User Action:
Check supported TRANSLATE operands, e.g. ISO, DEC, ASCII...
Reason:
The encoded string cannot be assigned to the target MDO of an ENCODE statement, possibly due to its defined type.
System Action:
None.
User Action:
Check the type definition of the target MDO and rectify as appropriate.
Reason:
The procedure has abended on an ENCODE or DECODE verb because an MDO was invalidly mapped because of one of the following:
. the map was not found on the mapping services database . it failed to load . it did not successfully attach to the MDO because it mismatched the data in the MDO.
System Action:
Procedure is flushed.
User Action:
Ensure map exists, loads and correctly maps the underlying MDO data.
Reason:
The specified target mdo contains invalid data.
System Action:
None.
User Action:
Delete the invalid component, or use a new MDO.
Reason:
An ENCODE or DECODE statement specified operands that indicate that ATF is to be used. However ATF is not available or is not licensed on this SOLVE system.
System Action:
An error is indicated.
User Action:
Check your SOLVE licence for ATF support.
Reason:
An ENCODE or DECODE statement has a SRC_CHARSET operand that names a character set that is not recognised by ATF.
System Action:
An error is indicated.
User Action:
Check the character set name.
Reason:
An ENCODE or DECODE statement has a TGT_CHARSET operand that names a character set that is not recognised by ATF.
System Action:
An error is indicated.
User Action:
Check the character set name.
Reason:
A SECCALL EXIT verb has been executed but the SOLVE system does not have a security exit to call.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
If the SOLVE system should have a security exit, investigate why it is not active.
Reason:
A SECCALL EXIT verb has been executed but one of the parameters to be passed is too long. The maximum length of any single parameter is 256 bytes.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Investigate why the parameter is too long.
Reason:
The input mask to the EDIT built-in function is not valid. The exact reason follows the colon.
System Action:
The function signals an error.
User Action:
Correct the EDIT function operands.
Reason:
The number supplied to the EDIT built-in function was too large for the number of integer positions in the edit mask.
System Action:
The function signals an error.
User Action:
Check and correct the edit mask or number.
Reason:
The indicated parameter number (n) to the STCKFIX function is not valid.
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
The indicated parameter number (n) (name also shown) requires a following value parameter.
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
The indicated parameter number (n) (name of preceding parameter also shown) must be data of one of the following types:
s is +, -, E (meaning +), or W (meaning -)
hh is an hours value from 00 to 15
mm is a minutes value from 00 to 59
(maximum allowed is 1500).
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
The input value to the STCKGEN function must be a date/time in one of the following formats:
yyyymmddhhmmss.ffffff
The value can be shortened, as long as it has at least the date (yyyymmdd).
unsigned packed decimal bytes, exactly 10 bytes long, in the format:
x'yyyymmddhhmmssffffff'
This is the same as the return format from the STCKFMT function when the P option is used.
The value must be in the following range:
19000101000000.000000 to 20420917235347.370495
This is the defined range for a STCK value from x'0000000000000000' to x'ffffffffffffffff'.
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
An OML SELSTR or REMSTR builtin function is being processed with CONTROL DBCS in effect and SYSPARMS DBCS=YES. The delimeter character supplied is not a single SBCS character and is not a single DBCS character enclosed by shift out and shift in.
System Action:
An error is raised.
User Action:
Check why the character was not a valid SBCS or DBCS character.
Reason:
The indicated parameter number ('p') to the named Date-related function is not valid.
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
An OML JCLXOPT built-in function was called, but the specified name of the JCL XOPT option is not in the name table of the function.
System Action:
An error is raised.
User Action:
Check the name of the specified option.
Reason:
The PLEXSUB OML builtin function can only be used if the operating system is OS/390 or later (such as z/OS).
System Action:
The function signals an error.
User Action:
Do not use the PLEXSUB function in this environment.
Reason:
The PLEXSUB OML builtin function could not load the MVS substitution service module, ASASYMBM.
System Action:
The function signals an error.
User Action:
Investigate why the ASASYMBM module is not accessible.
Reason:
The PLEXSUB OML builtin function requires user variable names to be 1 to 16 characters long (not including the &), and the first character must be alpha or national, the remainder being alpha, numeric, or national.
System Action:
The function signals an error.
User Action:
Correct the user variable name.
Reason:
The PLEXSUB OML builtin function requires user variable values to be no longer than the variable name including the leading &. (This is an MVS substitution service restriction).
System Action:
The function signals an error.
User Action:
Correct the user variable value. If a longer value is required, use a longer name.
Reason:
The PLEXSUB OML builtin function received a non-zero return code from the ASASYMBM MVS substution service module.
System Action:
The function signals an error.
User Action:
Contact your support representative. Non-zero return codes should not occur.
Reason:
The ASASYMBM MVS substitution service module ABENDed whilst processing a request for the PLEXSUB function.
System Action:
The function signals an error.
User Action:
Contact your support representative. An ABEND should not occur.
Reason:
The MIN and MAX operands of the RANDOM built-in function have a difference that is less than 1 or greater than 100000.
System Action:
The function signals an error.
User Action:
Correct the RANDOM function operands.
Reason:
An OML REMSTR builtin function has detected that the delimeter character supplied was not a single byte character.
System Action:
An error is raised.
User Action:
Check why the character was not a single byte character. The only situation in which the character can be longer is if CONTROL DBCS is in effect on a SOLVE system with SYSPARMS DBCS=YES, and the character is a single DBCS character enclosed by shift out and shift in.
Reason:
An OML SELSTR builtin function has detected that the delimiter character supplied was not a single byte character.
System Action:
An error is raised.
User Action:
Check why the character was not a single byte character. The only situation in which the character can be longer is if CONTROL DBCS is in effect on a SOLVE system with SYSPARMS DBCS=YES, and the character is a single DBCS character enclosed by shift out and shift in.
Reason:
An attempt has been made to share a variable or MDO from OML to NCL but the name is too long to be valid in NCL. The maximum name length for a variable is 12. The maximum name length for an MDO is 12 excluding the period.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML procedure is terminated.
User Action:
Change the name of the variable or avoid sharing it to NCL.
Reason:
An attempt has been made to share a variable or MDO from OML to NCL but the name is not valid in NCL.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML procedure is terminated.
User Action:
Change the name of the variable or avoid sharing it to NCL.
Reason:
An attempt has been made to share a variable from OML to NCL but the data contained in the variable is more than 256 bytes in length. This amount of data is not supported by NCL, so the request has been rejected.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML procedure is terminated.
User Action:
Consider why the variable is being shared to NCL and why the variable has more than 256 bytes of data. If required, add logic to the OML procedure to limit the amount of data in the variable to 256 bytes.
Reason:
This message is a trace message displaying aspects of a call to the Audit API. It is used to display the following information:
Each traced API call is given a unique ID so that associated messages can be grouped. This call ID is indicated by P1. The remainder of the message is contained in P2.
This message is written to the activity log if the Audit trace facility is enabled.
System Action:
None.
User Action:
To enable the Audit trace facility, specify TRACE=YES on the Audit API call or issue the command: $GLBL $NMAUTRC YES.
To disable the Audit trace facility, do not specify TRACE=YES on the Audit API call and ensure that the &GLBL$NMAUTRC global variable is not set to YES by issuing the command: $GLBL $NMAUTRC.
Reason:
The Audit API raised an Audit event of type P1, but the event was not received. This is because the Audit Event Listener is not profiled to receive this type of event.
System Action:
None.
User Action:
If you want this type of event audited, enable it through the AUDIT parameter group:
The parameter group opens for update.
The Audit Event Listener is profiled to listen to events of the required type.
The parameter group is updated.
Reason:
The Audit API was called with an invalid value, P2, for parameter P1. The reason why it is invalid is indicated by P3.
System Action:
The Audit API terminates before raising an audit event.
User Action:
See the Audit API appendix in this product's Reference Guide to determine the valid values for parameter P1.
Reason:
The Audit system went to raise utilization events for the registered event counters. However, it discovered that this had already been done for the given minute.
System Action:
Utilization events are not raised for the registered counters.
User Action:
None.
Reason:
The Audit API has successfully performed action P2 on the event counter identified by P1.
System Action:
None.
User Action:
None.
Reason:
The Audit API failed to perform action P2 on event counter P1. The reason for this failure is shown in P3.
System Action:
None.
User Action:
Review the activity log for any other error messages.
To trace calls to the Audit API, enable the Audit trace facility by specifying TRACE=YES on the Audit API call or by issuing the command: $GLBL $NMAUTRC YES.
To disable the Audit trace facility, do not specify TRACE=YES on the Audit API call and ensure that the &GLBL$NMAUTRC global variable is not set to YES by issuing the command: $GLBL $NMAUTRC.
Reason:
The Audit API has incremented an event counter identified by P1 to the value P2.
System Action:
None.
User Action:
None.
Reason:
The Audit API failed to increment an event counter identified by P1.
System Action:
None.
User Action:
Review the activity log for any other error messages.
To enable the Audit trace facility, specify TRACE=YES on the Audit API call or issue the command: $GLBL $NMAUTRC YES.
To disable the Audit trace facility, do not specify TRACE=YES on the Audit API call and ensure that the &GLBL$NMAUTRC global variable is not set to YES by issuing the command: $GLBL $NMAUTRC.
Reason:
The Audit API has raised events for P1 event counters.
System Action:
None.
User Action:
None.
Reason:
The Audit API attempted to execute service procedure P1 while processing a counter. However, the service procedure, or a subsequent procedure called by the service procedure, does not exist.
System Action:
The Audit API disregards the service procedure for the current counter.
User Action:
Check your COMMANDS library and make sure this service procedure, and any other procedures it calls, exist.
Reason:
The Audit API has detected that the Audit Event Listener is not running.
System Action:
No Audit events are recorded locally.
User Action:
If required, start the Audit Event Listener through the AUDIT parameter group:
The parameter group opens for update.
The Audit Event Listener starts.
The parameter group is updated.
Reason:
A call was made to the Audit API requesting an option that is not permitted while the Audit Event Listener is not auditing utilization events.
System Action:
The Audit API ends with return code 8.
User Action:
Do not call the Audit API with this option while utilization events are not being audited.
If you want utilization events to be audited, enable them through the AUDIT parameter group:
The parameter group opens for update.
The Audit Event Listener is profiled to audit utilization events.
The parameter group is updated.
Reason:
This informational message displays the completion code for an Audit API called from Command Entry.
System Action:
None.
User Action:
None.
Reason:
The $NM AUDIT parameter group has been actioned. It specifies that some event types should be written to SMF. However, the SMF parameter group has disabled the creation of subtyped records.
System Action:
The Audit Event Listener ($NMAU01Z) will initialize successfully; however, no events are written to SMF until the SMF parameter group enables the creation of subtyped records.
User Action:
In the SMF parameter group, specify a nonzero value in the SMF Record Identifier (Subtyped) field. This value must be in the range 128 to 255.
Alternatively, if SMF records are not required, change the event type fields to specify either NO (do not audit) or LOG (only write to the activity log).
Reason:
The Audit Event Listener has successfully completed initialization and is now waiting to receive audit events.
System Action:
Audit event listening starts.
User Action:
None.
Reason:
The Audit Event Listener started with an invalid parameter value.
System Action:
Audit Event Listener stops initializing.
User Action:
Provide a valid value for field P1 in the AUDIT parameter group, and then action the parameter group to restart Audit Event Listener.
Reason:
An Audit Event Listener ($NMAU01Z) was started; however, a Listener is already running.
System Action:
The second Audit Event Listener terminates.
User Action:
Do not start an Audit Event Listener while one is running.
Reason:
A command was issued to stop the Audit Event Listener; however, it is not active.
System Action:
None.
User Action:
None.
Reason:
A request was made to stop the Audit Event Listener.
System Action:
The Audit Event Listener terminates.
User Action:
None.
Reason:
The Audit Event Listener terminated normally.
System Action:
The Audit Event Listener terminates.
User Action:
None.
Reason:
The field in error requires a time value in the format hh.mm
System Action:
Validation fails.
User Action:
Enter a valid time value in the format hh.mm and continue.
Reason:
The Audit Event Listener has started and is documenting its runtime parameters.
System Action:
None.
User Action:
None.
Reason:
The region's AUDIT parameter group has the auditing of configuration events (such as changes to definitions) enabled to write to the activity log. This message indicates that the Audit Event Listener has received and logged a configuration event.
P1 is the object as "[objLocation:]objClass:objName[:objText]"
P2 is the action as "action[:actionText][:actionValue]"
P3 is the user as "userLocation:userId"
P4 is the UTC date of the event as yyyymmdd
P5 is the UTC time of the event as hh:mm:ss.th
System Action:
None.
User Action:
None.
Reason:
The region's AUDIT parameter group has the auditing of procedural events (such as actions performed at a monitor) enabled to write to the activity log. This message indicates that the Audit Event Listener has received and logged a procedural event.
P1 is the object as "[objLocation:]objClass:objName[:objText]"
P2 is the action as "action[:actionText][:actionValue]"
P3 is the user as "userLocation:userId"
P4 is the UTC date of the event as yyyymmdd
P5 is the UTC time of the event as hh:mm:ss.th
System Action:
None.
User Action:
None.
Reason:
The region's AUDIT parameter group has the auditing of serviceability events (such as changes in the status of monitored resources) enabled to write to the activity log. This message indicates that the Audit Event Listener has received and logged a serviceability event.
P1 is the object as "[objLocation:]objClass:objName[:objText]"
P2 is the action as "action[:actionText][:actionValue]"
P3 is the UTC date of the event as yyyymmdd
P4 is the UTC time of the event as hh:mm:ss.th
System Action:
None.
User Action:
None.
Reason:
The region's AUDIT parameter group has the auditing of utilization events (such as statistics on activities) enabled to write to the activity log. This message indicates that the Audit Event Listener has received and logged a utilization event.
P1 is the object as "[objLocation:]objClass[:objName][:objText]"
P2 is the action as "action[:actionText]"
P3 is the value of the action as actionValue
P4 is the period for the event in minutes
P5 is the UTC date of the event as yyyymmdd
P6 is the UTC time of the event as hh:mm:ss.th
System Action:
None.
User Action:
None.
Reason:
The region's AUDIT parameter group has the auditing of access events (such as security activities) enabled to write to the activity log. This message indicates that the Audit Event Listener has received and logged an access event.
P1 is the object as "[objLocation:]objClass:objName[:objText]"
P2 is the action as "action[:actionText][:actionValue]"
P3 is the user as "userLocation:userId"
P4 is the UTC date of the event as yyyymmdd
P5 is the UTC time of the event as hh:mm:ss.th
System Action:
None.
User Action:
None.
Reason:
The region's AUDIT parameter group has the auditing of application events (such as activities generated by your applications) enabled to write to the activity log. This message indicates that the Audit Event Listener has received and logged an application event.
P1 is the object as "[objLocation:]objClass:objName[:objText]"
P2 is the action as "action[:actionText][:actionValue]"
P3 is the user as "userLocation:userId"
P4 is the UTC date of the event as yyyymmdd
P5 is the UTC time of the event as hh:mm:ss.th
System Action:
None.
User Action:
None.
Reason:
The Audit General Event Listener has successfully completed initialization and is now waiting to receive events.
System Action:
None.
User Action:
None.
Reason:
An Audit General Event Listener ($NMAU02Z) was started; however, a Listener is already running.
System Action:
The second General Event Listener terminates.
User Action:
Do not start a General Event Listener while one is running.
Reason:
A command was issued to stop the Audit General Event Listener; however, it is not active.
System Action:
None.
User Action:
None.
Reason:
A request was made to stop the Audit General Event Listener.
System Action:
The Audit General Event Listener terminates.
User Action:
None.
Reason:
The Audit General Event Listener terminated normally.
System Action:
The General Event Listener terminates.
User Action:
None.
Reason:
The value in the Full value field must contain alphabetic characters only. It must not contain any spaces, numbers, or special characters.
System Action:
CAS Table Entry Definition ends in error.
User Action:
Provide an alphabet-only string for Full value.
Reason:
The value in the Hex Value field must contain four hexadecimal characters: 0 to 9 and A to F.
System Action:
CAS Table Entry Definition ends in error.
User Action:
Provide a valid 4-character hexadecimal string for Hex Value.
Reason:
The range 1000 to 1FFF is reserved for customers to define their own Audit actions. Do not use this range.
System Action:
CAS Table Entry Definition ends in error.
User Action:
Provide a valid 4-character hexadecimal string that is not in the range 1000 to 1FFF.
Reason:
User-defined Audit actions must be defined with a hexadecimal value in the range 1000 to 1FFF inclusive.
System Action:
CAS Table Entry Definition ends in error.
User Action:
Provide a valid 4-character hexadecimal string that is within the range 1000 to 1FFF.
Reason:
A Minute-Minder Listener ($NMCP01Z) was started; however, a Listener is already running.
System Action:
The second Minute-Minder Listener terminates.
User Action:
Do not start a second Minute-Minder Listener while one is already running.
Reason:
An invalid value for P1 was supplied to the Minute-Minder Listener.
System Action:
The Minute-Minder Listener terminates.
User Action:
Start the Listener with a valid value for P1.
Reason:
The Minute-Minder Listener was started with an incompatible LOCPU/HICPU combination. The LOCPU value must be less than the HICPU value.
System Action:
The Minute-Minder Listener terminates.
User Action:
Start the Listener with a valid LOCPU/HICPU combination.
Reason:
The Minute-Minder Listener was started with an invalid data set name for the PMON unload data set.
System Action:
The Minute-Minder Listener terminates.
User Action:
Start the Listener with a valid data set name. The data set must be a PDS.
Reason:
The Minute-Minder Listener started successfully.
System Action:
The Minute-Minder Listener waits for CPU monitoring events.
User Action:
None.
Reason:
This message is issued when the Minute-Minder Listener starts successfully. It documents the parameters the Listener is using for its monitoring.
System Action:
The Minute-Minder Listener waits for CPU monitoring events.
User Action:
None.
Reason:
A command was issued to stop the Minute-Minder Listener; however, it is not active.
System Action:
None.
User Action:
None.
Reason:
You requested the Minute-Minder Listener to stop.
System Action:
The Minute-Minder Listener terminates.
User Action:
None.
Reason:
The Minute-Minder Listener terminated normally.
System Action:
The Minute-Minder Listener terminates.
User Action:
None.
Reason:
The OML I/O manager has successfully initialized.
System Action:
None.
User Action:
None.
Reason:
The OML I/O manager has recovered from an I/O subtask abend. The abend code is shown in the message.
System Action:
The subtask is restarted.
User Action:
Examine the abend code and take corrective action if required.
Reason:
The OML I/O manager has detected an I/O error on a procedure library while attempting to load the named procedure. I/O error information is displayed.
System Action:
The load is retried.
User Action:
Examine the I/O error information and take corrective action if required.
Reason:
An OMLCTL CMDREPL command failed. The requested command procedure could not be found.
System Action:
The command replacement fails.
User Action:
Ensure that the command replacement procedure is in the COMMANDS library concatenation.
Reason:
An OML load request asked for a particular procedure type (eg FUNCTION). The loaded procedure type was not as expected.
System Action:
The load fails.
User Action:
Check that the procedure starts with the correct statement type, e.g., for a function, the FUNCTION statement.
Reason:
An OML procedure that had the 'CALLONLY' attribute was loaded for a non-callonly requestor, for example, to be executed as a command.
System Action:
The load fails.
User Action:
CALLONLY procedures cannot be executed from OCS, etc. Check the requirement to execute the procedure in this manner.
Reason:
On OMLCTL UNLOAD command requested that a procedure be purged from storage. This message confirms the request has been done.
System Action:
None.
User Action:
None.
Reason:
On OMLCTL UNLOAD command requested that a procedure be purged from storage. The procedure is currently in use and will be purged when its use count drops to 0. Any new requests for the procedure will trigger the loading of a new copy.
System Action:
None.
User Action:
None.
Reason:
An OMLCTL PRELOAD command has completed.
System Action:
None.
User Action:
None.
Reason:
An OMLCTL CMDREPL command has completed. The command has been replaced by an OML procedure.
System Action:
None.
User Action:
None.
Reason:
An OMLCTL CMDREPL command has failed. There is already a procedure of that command name loaded.
System Action:
None.
User Action:
Unload the old procedure if required and retry.
Reason:
An OMLCTL UNLOAD command has failed. You cannot unload a command replacement procedure with this command.
System Action:
None.
User Action:
Use the OMLCTL CMDREPL OPT=UNLOAD command if necessary.
Reason:
On OMLCTL PRELOAD command requested preloading of a procedure that is already preloaded.
System Action:
The command is ignored.
User Action:
Use OMLCTL UNLOAD to unload the preloaded procedure if a new copy is to be loaded.
Reason:
An OMLCTL CMDREPL command failed for one of the following reasons:
System Action:
The command is ignored.
User Action:
Use SHOW EQUATES, SHOW NCLSTAT, and SHOW OMLSTST to determine the cause of the problem.
Reason:
An OMLCTL UNLOAD command failed. The requested procedure is not presently loaded.
System Action:
The command is ignored.
User Action:
None.
Reason:
An OMLCTL CMDREPL UNLOAD command failed. The requested procedure is not presently loaded.
System Action:
The command is ignored.
User Action:
None.
Reason:
An OMLCTL CMDREPL UNLOAD command failed. The requested procedure is not a CMDREPL procedure.
System Action:
The command is ignored.
User Action:
None.
Reason:
An UNLOAD PROCEDURE= (or OMLCTL UNLOAD) command has been issued specifying a generic procedure or DD name. This message shows the total OML procedures unloaded as a result of the command.
System Action:
The procedures are reloaded, as required.
User Action:
None.
Reason:
An OML compile/load failed due to a shortage of storage.
System Action:
The OML compile or load fails.
User Action:
Investigate the storage shortage.
Reason:
An OML compile/load failed due to a problem opening the requested member. A reason is given.
System Action:
The OML compile or load fails.
User Action:
Investigate the reason for the failure.
Reason:
An OML compile/load failed due to the requested member being NCL.
System Action:
The OML compile or load fails.
User Action:
Convert the source to OML and re-compile.
Reason:
An OML compile/load failed due to an I/O error. A second attempt is made to compile after closing and reopening the library.
Note: This message is logged only.
System Action:
A second attempt is made to load the procedure.
User Action:
None.
Reason:
During compilation of an OML procedure an end-of-file condition was encountered before any statements were found. srcloc shows the source location of the end of file.
System Action:
Compilation of the procedure fails.
User Action:
Add some statements to the file.
Reason:
During compilation of an OML procedure an end-of-file condition was encountered during processing of a nested statement (eg IF/THEN/ELSE). srcloc shows the location of the statement in error
System Action:
Compilation of the procedure fails.
User Action:
Complete the nested statement.
Reason:
During compilation of an OML procedure an end-of-file condition was encountered either:
srcloc shows the source location of the statement in error
aaa shows the number of DO groups which have not been terminated
bbb shows the number of PROCEDUREs or FUNCTIONs which have not been terminated
System Action:
Compilation of the procedure fails.
User Action:
Add an END statement for each DO group, PROCEDURE or FUNCTION statement.
Reason:
The first statement in an OML procedure must be a PROCEDURE or FUNCTION statement. The procedure being compiled does not have one of these as the first statement. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Add a PROCEDURE or FUNCTION statement as the first executable statement in the procedure. Also make sure a corresponding END statement exists.
Reason:
During compilation of an OML procedure, statements were found after the END statement which terminated the source of the procedure or function. This is invalid. It indicates there may be incorrect pairing of DO/END statements. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Check the pairing of DO/END statements. If the code was not to be included in the procedure, remove it from the source file, or enclose the code in comment delimiters (/* comment */).
Reason:
During compilation of an OML procedure a label was found on a statement which is nested (e.g. IF cond THEN LAB: IF ....). This is invalid. srcloc shows the source location of the statement in error
System Action:
Compilation of the procedure fails.
User Action:
Remove the label from the statement.
Reason:
During compilation of an OML procedure more than 16,000,000 lines of source text were found. 16,000,000 is the maximum number allowed.
System Action:
Compilation of the procedure fails.
User Action:
Divide the source file into several source files, each with not more than 16,000,000 lines.
Reason:
The first executable statement in an OML procedure was not a PROCEDURE statement, so one has been inserted automatically. A corresponding END statement will also be inserted at the end of the source. This This message is a warning only and does not cause compilation failure. srcloc shows the source location of the PROCEDURE statement.
System Action:
Compilation of the procedure continues.
User Action:
None.
Reason:
During compilation of an OML procedure, a verb was encountered which had a compilation error.
srcloc shows the source location of the statement in error
verbname shows the name of the verb
reason shows the reason for the compilation failure
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the verb and retry.
Reason:
During compilation of an OML procedure, a statement was found which was not recognised as a valid OML statement type. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove or correct the statement.
Reason:
During compilation of an OML procedure, an assignment statement was found which attempted to update a system variable which cannot be updated.
srcloc shows the source location of the statement in error.
varname shows the name of the variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove or correct the statement.
Reason:
During compilation of an OML procedure, an assignment statement was found which attempted to update a system variable with a null value. Null is not a valid value for the system variable.
srcloc shows the source location of the statement in error.
varname shows the name of the system variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove or correct the statement.
Reason:
During compilation of an OML procedure, an assignment statement was found which attempted to update a variable with a null name.
srcloc shows the source location of the statement in error.
varname shows the name of the variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove or correct the statement.
Reason:
During compilation of an OML procedure, a SELECT statement was found without a following WHEN statement. The statement following a SELECT statement must always be a WHEN statement. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Insert a WHEN statement following the SELECT statement.
Reason:
During compilation of an OML procedure, a WHEN statement was processed which was not followed by an allowable statement type. The statement following a WHEN statement must always be:
srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Insert a WHEN, OTHERWISE or END statement following the WHEN statement. This error can also indicate incorrect DO/END pairing in the logic of the WHEN statement.
Reason:
During compilation of an OML procedure, a statement was encountered which was not recognisable as a valid verb or assignment statement. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the statement, or remove it, or enclose it in comment delimiters (/* */).
Reason:
During compilation of an OML procedure, a statement was encountered which was not a recognisable verb or assignment statement. The syntax of the statement indicates it may be a verb which is not supported by the system on which the compilation is taking place. srcloc shows the source location of the statement in error
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the statement, or remove it, or enclose it in comment delimiters (/* */). This error can be caused by an incorrectly spelt verb name. If the verb is valid but not supported by the system, use %%OPTIONS DEFER to avoid compilation errors. If the verb is encountered during execution an error will be raised.
Reason:
During compilation of an OML procedure, a statement was encountered which was not recognisable as a valid verb or assignment statement. The syntax of the statement indicates it may be a verb which is not supported by the system on which compilation is taking place.
%%OPTIONS DEFER is in effect, so compilation does not fail for this error, but if the verb is encountered during execution an error will be raised. This message is sent as a warning of the situation.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb.
System Action:
Compilation of the procedure continues.
User Action:
Make sure the verb name has been spelt correctly. If so, make sure the logic in the procedure will not execute the verb unless the verb is supported by the system (eg.if verb is an MAI verb, check that MAI is installed, using the ZFEATURE built-in function).
Reason:
During compilation of an OML procedure, a statement was encountered which was not recognisable as a valid verb or assignment statement. The syntax of the statement indicates it may be a verb which is not supported by the system on which the compilation is taking place.
%%OPTIONS DEFER is in effect, but is ignored because the compilation is producing executable object.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Make sure the verb name is spelt correctly. If so, make sure the system is licensed for the feature to which the verb belongs.
Reason:
During compilation of an OML procedure, an IF statement was encountered which had invalid syntax or was not followed by a THEN statement. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the statement, or insert a THEN statement after the conditional expression.
Reason:
During compilation of an OML procedure, an ELSE statement was encountered which was not preceded by an IF/THEN statement combination. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Examine the preceding statements to locate the IF/THEN combination. If not found, insert them. If found, this could indicate incorrect DO/END pairing in the THEN logic.
Reason:
During compilation of an OML procedure, a WHEN statement was encountered which was invalid.
srcloc shows the source location of the statement in error.
reason shows the reason for the WHEN statement being invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the WHEN statement and retry.
Reason:
During compilation of an OML procedure, an OTHERWISE statement was encountered which was not preceded by a WHEN statement.
srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
This could indicate incorrect DO/END pairing in the logic of the WHEN statement if the statements preceding the OTHERWISE statement contain a WHEN statement.
Reason:
During compilation of an OML procedure, nesting of DO or SELECT statements exceeded the limit of 250 levels. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Alter the logic of the procedure to avoid so many nested DO or SELECT statements.
Reason:
During compilation of an OML procedure, a DO statement was encountered which specified an unrecognised or duplicated keyword, or contained data after the DO expression. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the DO statement and retry.
Reason:
During compilation of an OML procedure, a DO statement was encountered which specified a control variable, but the variable is not acceptable. Complex, global and system variables cannot be used. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Choose a different control variable name.
Reason:
During compilation of an OML procedure, a GOTO or GOSUB statement was encountered which is invalid.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb (GOTO or GOSUB).
reason shows the reason the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement and retry.
Reason:
During compilation of an OML procedure, a RETSUB statement was encountered which is invalid.
srcloc shows the source location of the statement in error.
reason shows the reason the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement and retry.
Reason:
During compilation of an OML procedure, a RETURN statement was encountered which is invalid.
srcloc shows the source location of the statement in error.
reason shows the reason the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement and retry.
Reason:
During compilation of an OML procedure, an ON statement was encountered which specified a condition name which is not valid. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the condition name and retry.
Reason:
During compilation of an OML procedure, a SIGNAL statement was encountered which specified a condition name which is not valid, or null. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the condition name by removing invalid characters. If it was null, add the condition name to the statement.
Reason:
During compilation of an OML procedure, a REVERT statement was encountered which specified a condition name which is not valid. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the condition name and retry.
Reason:
During compilation of an OML procedure, an END statement was encountered which specified a label name which is invalid.
srcloc shows the source location of the statement in error.
labelname shows the invalid label name.
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name and retry.
Reason:
During compilation of an OML procedure, an END statement was encountered but no corresponding DO, PROCEDURE, or FUNCTION statement exists. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove the END statement or add the required DO, PROCEDURE, or FUNCTION statement.
Reason:
During compilation of an OML procedure, an END statement was encountered which specified a label name. The corresponding DO statement does not specify a label name or specifies a different label name. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name on either the DO statement or END statement. This error can also indicate incorrect DO/END pairing in the logic of the DO statement.
Reason:
During compilation of an OML procedure, an END statement was encountered which specified a label name, but the corresponding PROCEDURE or FUNCTION statement specifies a different label name. srcloc shows the source location of the statement in error
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name on either the PROCEDURE/FUNCTION statement or DO statement. This error can also indicate incorrect DO/END pairing in the procedure.
Reason:
During compilation of an OML procedure, a LEAVE or ITERATE statement was encountered which was not inside an iterative DO loop. LEAVE and ITERATE are only valid inside an iterative DO loop.
srcloc shows the source location of the statement in error.
verbname shows the verb name (LEAVE or ITERATE).
System Action:
Compilation of the procedure fails.
User Action:
Remove the LEAVE or ITERATE statement, or enclose it in an iterative DO loop.
Reason:
During compilation of an OML procedure, a LEAVE or ITERATE statement was encountered which specified a label name which is invalid.
srcloc shows the source location of the statement in error.
verbname shows the verb name (LEAVE or ITERATE).
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name by removing invalid characters.
Reason:
During compilation of an OML procedure, a LEAVE or ITERATE statement was encountered which specified a label name which does not match the label name on any preceding iterative DO statement which encloses the LEAVE or ITERATE statement.
srcloc shows the source location of the statement in error.
verbname shows the verb name (LEAVE or ITERATE).
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name on either the iterative DO statement or the LEAVE or ITERATE statement.
Reason:
During compilation of an OML procedure, a quoted label name was encountered which was null. This is invalid. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name and retry.
Reason:
During compilation of an OML procedure or function, a verb was encountered which is not supported in the specified procedure type.
srcloc shows the source location of the statement in error.
proctype shows the type of procedure (PROCEDURE or FUNCTION).
System Action:
Compilation of the procedure fails.
User Action:
Remove the verb from the procedure/function.
Reason:
During compilation of an OML procedure a verb was found to have an option specified that is not supported by that verb.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb.
option shows the option that was specified.
System Action:
Compilation of the procedure fails.
User Action:
Correct the option.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified that is not supported by that verb.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb.
operand shows the operand that was specified.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a null value, but null is not a valid value for the operand.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a value which is not constant. The operand must be specified as a constant in the source.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a value which is not in the list of valid keywords for this operand.
srcloc shows the source location of the statement in error.
keyword shows the invalid keyword which was specified.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the keyword.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has an unexpected value following the expected value for this operand. For example, end of statement was expected but more text was found.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Remove the extraneous data.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a variable list. The list has an opening parenthesis and no closing parenthesis.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Add a closing parenthesis to the variable list.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a null value, but a null value is invalid for this operand.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Add the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which has a numeric range specified. The first number in the range is greater than the second number in the range.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Change the range so that the second number is greater than the first number.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which has an invalid variable name.
srcloc shows the source location of the invalid variable name.
reason shows the reason that the variable name is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the invalid variable name.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which should have a variable name but one has not been supplied, or the one supplied is invalid. srcloc shows the source location of the operand.
System Action:
Compilation of the procedure fails.
User Action:
Add the variable or correct the name.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which allows a list of entries, but the number of entries in the list exceeds the number allowed for the operand.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb
System Action:
Compilation of the procedure fails.
User Action:
Reduce the number of entries in the list.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which supports a datatype which is not supported by the compiler.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Contact your product support representative.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified that has a value which is either too long or too short.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which has a numeric value which is either too low or too high.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which is required to be a specific data type other than character, but it is not. For example, required type is integer but its value is not an integer.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
datatype shows the required data type for the operand.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified that is required to be a specific character data type but it is not. For example, the name must be a PDS name but contains invalid characters.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
datatype shows the required data type for the operand.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which is required to be a specific data type but it is not that type.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which is required to be a specific type of variable name but it is a different type of variable name. For example, an MDO name is required but the name supplied is not a valid MDO name.
srcloc shows the source location of the invalid statement.
varname shows the variable name which was specified.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Change the variable name to one of the required type.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified more than once, when this is not allowed.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Remove all but one of the operand occurrences.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified, which is not allowed to be specified due to the presence of an earlier operand.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Determine which earlier operand is causing the problem and either remove it or remove the operand indicated in this message.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which allows a list of keywords. The named keyword occurs more than once in the list, which is not allowed.
srcloc shows the source location of the invalid statement.
keyword shows the keyword which has been duplicated.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Remove all but one of the occurrences of the keyword.
Reason:
During compilation of an OML procedure, a verb with invalid syntax was found.
srcloc shows the source location of the invalid statement.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the statement.
Reason:
During compilation of an OML procedure, a verb was found that did not have all of the required operands specified.
srcloc shows the source location of the invalid statement.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Add the required operands.
Reason:
During compilation of an OML procedure, a PROCEDURE or FUNCTION statement was encountered which specifies a name that has already been used within the current procedure or function.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
procname shows the name of the procedure or function.
System Action:
Compilation of the procedure fails.
User Action:
Change the name of the procedure or function to make it unique.
Reason:
During compilation of an OML procedure, a PROCEDURE or FUNCTION statement was encountered which specifies a name which has already been found within the current procedure or function.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
procname shows the name of the procedure or function.
System Action:
Compilation of the procedure fails.
User Action:
Change the name of the procedure or function to make it unique.
Reason:
During compilation of an OML procedure, a PROCEDURE or FUNCTION statement was encountered which specifies either a duplicate operand, or an operand which cannot be specified because of the presence of an earlier operand.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
operand shows the operand which is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Change the operand.
Reason:
During compilation of an OML procedure, a PROCEDURE or FUNCTION statement was encountered that specifies a shared variable list which contains conflicting variable names. For example, &A* and &AB* are specified. &AB* is unnecessary because of the presence of &A*.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
var shows the variable which conflicts with an earlier variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove one of the variable names from the list.
Reason:
During compilation of an OML procedure, a CLASS statement was found that specified a list of object classes from which this class can inherit. Either no class name has been specified, or a name specified is invalid or has been duplicated.
srcloc shows the source location of the invalid statement.
class shows the class name which is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Either add the required class name(s) or correct the one which is named in this message. The class name must be a valid PDS name up to 8 chars.
Reason:
During compilation of an OML procedure, a CALL statement was found that specified an unrecognised operand.
srcloc shows the source location of the invalid statement.
operand shows the operand which is unrecognised.
System Action:
Compilation of the procedure fails.
User Action:
Correct or remove the operand.
Reason:
During compilation of an OML procedure, a CALL statement was found that specified an operand which is duplicated or is invalid because of the existence of a previous operand.
srcloc shows the source location of the invalid statement.
operand shows the operand which is invalid or duplicated.
System Action:
Compilation of the procedure fails.
User Action:
Correct or remove the operand.
Reason:
During compilation of an OML procedure, a CALL statement was found that specifies a shared variable list which contains conflicting variable names. For example, &A* and &AB* are specified,&AB* is unnecessary because of the presence of &A*.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
var shows the variable which conflicts with an earlier variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove one of the variable names from the list.
Reason:
During compilation of an OML procedure, a CALL statement was found that specified SHARE or NOSHARE but has no shared variable list. When SHARE or NOSHARE is specified, either NO or a variable list must also be specified. srcloc shows the source location of the invalid statement.
System Action:
Compilation of the procedure fails.
User Action:
Following SHARE or NOSHARE, specify NO or a variable list.
Reason:
During compilation of an OML procedure, a CALL statement was found that specified SHARE or NOSHARE. The NO keyword was specified and also a variable list was specified. This is invalid. The NO keyword cannot be specified with a variable list. srcloc shows the source location of the invalid statement.
System Action:
Compilation of the procedure fails.
User Action:
Remove either the NO keyword or the variable list.
Reason:
During compilation of an OML procedure, a CALL statement was found that is invalid for the reason shown.
srcloc shows the source location of the invalid statement.
reason provides a description of the error:
The first symbol after 'CALL' is not PROC or PROCEDURE, and is not either a symbol, quoted string, or opening parenthesis (indicating an expression procedure name).
If the first symbol is 'PGM' or 'SUBSYS' this is also an error, as OML does not presently support calls to a user program or subsystem. (If you wish to call a procedure called 'PGM' or 'SUBSYS' then use 'CALL PROC(PGM)' or 'CALL PROC(SUBSYS)').
The syntax <CALL '' ...> or <CALL PROC('')> is not allowed, as a null string is not a valid procedure name.
The procedure name expression evaluated to a constant null value during compilation, and this is not a valid procedure name.
CALL supports a maximum of 32000 arguments.
Package notation (package:procedure) may not be specified when calling a program or subsystem.
System Action:
Compilation of the procedure fails.
User Action:
Correct the CALL statement.
Reason:
During compilation of an OML PARSE statement, an invalid source token was found. srcloc shows the source location of the error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE statement, an option that is not supported by OML was found.
word shows the option. The REXX PARSE statement options of EXTERNAL, NUMERIC, PULL, SOURCE, and VERSION are not supported by OML.
srcloc shows the source location of the error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE statement with the VALUE option, invalid syntax was detected after the expression. token shows the invalid syntax.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE or ARG statement with the VAR option, invalid syntax was detected where a variable name was expected. token shows the invalid syntax.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE or ARG statement, an error in the template was found.
srclc identifies the location in the source where the error was detected.
n is the error code:
1 - An unrecognizable template token was encountered.
2 - Following an equal sign (=), the next token was neither a left bracket '(' nor a valid symbol/number.
3 - Following a plus sign (+), the next token was neither a left parenthesis '(' nor a valid symbol/number.
4 - Following a plus sign (-), the next token was neither a left parenthesis '(' nor a valid symbol/number.
5 - Following an opening left parenthesis '(', the next token was not a variable name.
6 - Following a variable name, the next token was not a closing right parenthesis ')'.
7 - A number was expected at the indicated location. (The current token was a symbol but not a valid number.)
9 - A comma was encountered in a template, but the current statement is neither PARSE (UPPER) ARG nor ARG. A comma is valid only for PARSE ARG or ARG.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE or ARG statement, a template that had a system variable name was found.
srclc identifies the location in the source where the error was detected.
varname is the system variable name that was found.
PARSE (or ARG) cannot set an OML system variable, even if the system variable is normally assignable.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML procedure, an expression was found that contains a syntax error.
srcloc shows the source location of the invalid statement.
reason shows the reason why the expression syntax is incorrect.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the expression.
Reason:
During compilation of an OML procedure, an expression was found that contains a constant section which could be evaluated during compilation but during evaluation an error occurred.
srcloc shows the source location of the invalid statement.
reason shows the reason that the evaluation failed.
System Action:
Compilation of the procedure fails.
User Action:
The expression results in processing which cannot be performed by OML. The action to take will be dependant on the reason given.
Reason:
During compilation of an OML procedure, an expression was found that contained a logical operation (for example, comparison of two numbers) with both arguments being constant. This message is sent as a warning because this usually indicates a programming error as the result will already be known, which means the code is redundant. srcloc shows the source location of the expression.
System Action:
Compilation of the procedure continues.
User Action:
Check the expression. If you want the expression to remain in this format, no action is required. This warning is only sent during compilation due to the OMLCHECK command.
Reason:
During compilation of an OML procedure, an expression was found that contains only constant values. The expression is used for a function which would normally not have a constant value (e.g. IF 'A' = 'B'..). This warning message is sent because this usually indicates a programming error as the result will already be known, meaning the code is redundant. srcloc shows the source location of the expression.
System Action:
Compilation of the procedure continues.
User Action:
Check the expression. If you want the expression to remain in this format, no action is required. This warning is only sent during compilation due to the OMLCHECK command.
Reason:
During compilation of an OML procedure, an expression was found that contained an invalid component. The component is invalid for the reason shown.
srcloc shows the source location of the expression.
term shows the component which is invalid.
reason shows the reason why the component is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the expression.
Reason:
This message was sent during compilation of an OML procedure for OMLCHECK LIST=YES. It contains the listing of the procedure.
linenum shows the line number in the file.
text shows the source text for this line.
System Action:
None.
User Action:
None.
Reason:
This message is sent during compilation of an OML procedure when a new %%INCLUDE file is being processed, if requested via OMLCHECK LIST=YES.
filename shows the source file name of the included file.
level shows the depth of %%INCLUDE processing for this file.
System Action:
None.
User Action:
None.
Reason:
This message is sent during compilation of an OML procedure when the end of a %%INCLUDE file is encountered, if requested via OMLCHECK LIST=YES.
filename shows the source file name of the included file.
level shows the depth of %%INCLUDE processing for this file.
System Action:
None.
User Action:
None.
Reason:
During compilation of an OML procedure, the resolution of a symbol that was defined by %%DEFINE has caused more than 256 substitution passes to try to resolve the final string. This is considered to be an error because either a recursive definition has been entered or the string is so complex the author has no chance of understanding what the final string will be.
srcloc shows the source file location of the statement in error.
symbol shows the current %%DEFINEd symbol being resolved.
System Action:
Compilation of the procedure fails.
User Action:
Correct the %%DEFINE definitions to avoid the recursive definition, or make the definitions easier to understand.
Reason:
During compilation of an OML procedure, a string defined by %%DEFINE has been resolved, but the resulting string is more than 255 bytes long. The maximum length allowed is 255.
srcloc shows the source location of the statement in error.
symbol shows the name of the symbol being resolved when the error occurred.
System Action:
Compilation of the procedure fails.
User Action:
Redefine the %%DEFINEs to make sure the final string length cannot be more than 255 bytes.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have a comment which was not closed by */. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Add a closing */ to the comment.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have invalid syntax. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have unrecognised word.
srcloc shows the source location of the statement in error.
word shows the word which is not recognised.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have a quoted string which with no closing quote. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Add a closing quote to the string.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have unpaired DBCS shift characters. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Ensure that DBCS shift characters are correctly paired.
Reason:
During compilation of an OML procedure, end-of-file (EOF) was encountered whilst concatenating lines that end with '\'.
System Action:
Compilation of the procedure fails.
User Action:
Remove any redundant '\' character from the end of the last source line.
Reason:
During compilation of an OML procedure, end-of-file (EOF) in an included file (%%INCLUDE) was encountered whilst concatenating lines that end with '\'.
System Action:
Compilation of the procedure fails.
User Action:
Remove any redundant '\' character from the end of the include file source line.
Reason:
During compilation of an OML procedure, a set of concatenated lines has exceeded the maximum allowable buffer length. This length is 4000 characters.
System Action:
Compilation of the procedure fails.
User Action:
reduce the number of consecutive concatenated lines.
Reason:
During compilation of an OML procedure, a set of concatenated lines has exceeded the maximum allowable number of lines. This limit is 100 lines.
System Action:
Compilation of the procedure fails.
User Action:
Reduce the number of consecutive concatenated lines.
Reason:
During compilation of an OML procedure, a %%DEFINE or %%UNDEFINE statement was found which did not specify the symbol to be DEFINEd or UNDEFINEd. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Add the string to the statement.
Reason:
During compilation of an OML procedure, a %%DEFINE or %%UNDEFINE statement specified a symbol which was either too long, contained invalid characters or was numeric.
srcloc shows the source location of the statement in error.
symbol shows the invalid symbol.
System Action:
Compilation of the procedure fails.
User Action:
Correct the symbol.
Reason:
During compilation of an OML procedure, a %%DEFINE statement specified a symbol which had already been defined using %%DEFINE.
srcloc shows the source location of the statement in error.
symbol shows the symbol.
System Action:
Compilation of the procedure fails.
User Action:
Check that the symbol names are correct. If so, insert a %%UNDEFINE statement before the statement in error.
Reason:
During compilation of an OML procedure, a %%DEFINE statement specified a replacement value which was too long.
The limit for a %%define replacement value is approximately 4000 characters.
srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Reduce the length of the %%DEFINE replacement text.
Reason:
During compilation of an OML procedure, a %%UNDEFINE statement was found that had data after the symbol to be %%UNDEFINEd. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove the data following the symbol name or enclose it in comment delimiters (/* comment */).
Reason:
During compilation of an OML procedure, a %%UNDEFINE statement was found that specified the name of a symbol which had not been %%DEFINEd.
srcloc shows the source location of the statement in error.
symbol shows the name of the symbol.
System Action:
Compilation of the procedure continues.
User Action:
This is a warning message that only appears during compilation for an OMLCHECK command. Check that the symbol name is correct, and if a corresponding %%DEFINE has been omitted. Remove the %%UNDEFINE statement if it is not required.
Reason:
During compilation of an OML procedure, a %%INCLUDE statement was found that has no include file name, or an invalid include file name. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
If the name has been omitted, add it to the statement. If it is present make sure it is a valid PDS name which is up to 8 characters in length.
Reason:
During compilation of an OML procedure, a %%INCLUDE statement was found that has data after the include file name. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove the data after the include file name or enclose it in comment delimiters (/* comment */).
Reason:
During compilation of an OML procedure, the number of %%INCLUDE statements found was more than 256. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Restructure the procedure to use 256 %%INCLUDEs or less.
Reason:
During compilation of an OML procedure, the specified %%INCLUDE file could not be opened.
srcloc shows the source location of the statement in error.
filename shows the name of the file.
System Action:
Compilation of the procedure fails.
User Action:
Check that the name of the procedure is spelt correctly (this error could indicate a non- existent file was specified). Check the library concatenation used by your userID to ensure the required library is present.
Reason:
During compilation of an OML procedure, more than one %%PTF statement was found. This statement is used to record the maintenance level of a procedure. There can only be one maintenance level, therefore only one %%PTF statement is allowed per procedure. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove the unnecessary %%PTF statement(s).
Reason:
During compilation of an OML procedure, a %%PTF statement was found which specified an invalid PTF name. The name must be a PDS name up to 8 characters in length. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the PTF name.
Reason:
During compilation of an OML procedure, an invalid token was found, the reason is shown.
srcloc shows the source location of the token.
reason shows the reason why the token is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the token to make it valid.
Reason:
During compilation of an OML procedure, a quoted string was found which starts and ends on different lines. This warning message is sent to warn of the possibility that this is an accident. This message is only produced if the compilation is for an OMLCHECK command. srcloc shows the source location of the quoted string.
System Action:
Compilation of the procedure continues.
User Action:
Check if this is deliberate. If so, no further action is required.
Reason:
During compilation of an OML procedure, an abend occurred while the named file was being read.
System Action:
Compilation of the procedure is aborted immediately.
User Action:
Investigate the reason for the abend.
Reason:
During compilation of an OML procedure, an I/O error occurred while the named file was being read.
System Action:
Compilation of the procedure is aborted immediately.
User Action:
Investigate the reason for the I/O error.
Reason:
During compilation of an OML procedure a GOTO or GOSUB statement was found to be invalid for the reason shown.
srcloc shows the source location of the statement in error.
reason shows the reason that the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the GOTO or GOSUB statement.
Reason:
During compilation of an OML procedure, a CALL statement was found to be invalid for the reason shown.
srcloc shows the source location of the statement in error.
reason shows the reason why the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the CALL statement.
Reason:
During compilation of an OML procedure, a SIGNAL statement was found to be invalid. The reason is shown.
srcloc shows the source location of the statement in error.
reason shows the reason why the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the SIGNAL statement.
Reason:
During compilation of an OML procedure, a function call was found but the target name is actually the name of a PROCEDURE. The target of a function call must be a FUNCTION.
srcloc shows the source location of the statement in error.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Correct the function name or change the target procedure to that of a function.
Reason:
During compilation of an OML procedure, a function call was found. The target name was not found in the source file, and is not a valid PDS name and as such is invalid.
srcloc shows the source location of the statement in error.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Correct the function name.
Reason:
During compilation of an OML procedure, a built-in function call was found. The number of arguments specified is more than 32000.
srcloc shows the source location of the statement in error.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Reduce the number of arguments on the call.
Reason:
During compilation of an OML procedure, a built-in function call was found. The named argument is invalid.
srcloc shows the source location of the statement in error.
argnum shows the argument number of the invalid argument.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Correct the argument.
Reason:
During compilation of an OML procedure, a built-in function call was found. The specified argument is null. This is not allowed.
srcloc shows the source location of the statement in error.
argnum shows the argument number of the invalid argument.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Correct the argument.
Reason:
An OML object load failed. The reason code provides a precise indication of the error.
Some of the error codes are:
001 to 011 - Invalid object header record(s) (generally meaning that the object has been edited, or file-transferred with ASCII conversion, etc).
012 - Object version mismatch. This object was compiled on an incompatible version of Management Services.
013 to 029 - See 001 to 011 above.
040 or 042 - Invalid record sentinal. Could indicate that the object has been ASCII/EBCDIC translated.
501 - Storage shortage.
606 - See 012 above.
802 or 803 - Invalid checksum, indicating possible file transfer with ASCII translation, or tampering or editing of the object.
804 - Unexpected end-of-file condition.
805 - I/O abend.
806 - Unrecoverable I/O error.
807 - Not EOF when expected.
808 - Unrecoverable I/O error or abend.
810 - Invalid record sentinal. Could indicate that the object has been ASCII/EBCDIC translated.
All other error codes indicate internal failures or errors.
System Action:
The object load fails.
User Action:
Examine the error code and take corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a system variable.
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a built-in function.
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a verb.
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a verb argument (operand).
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a verb argument (operand) keyword.
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
This is a warning message. During object loading, an unrecognised system variable name was found. If the statement(s) referencing it are executed, an error will occur.
System Action:
The object load continues.
User Action:
Ensure that this will not cause a runtime problem.
Reason:
This is a warning message. During object loading, an unrecognised built-in function name was found. If the statement(s) referencing it are executed, an error will occur.
System Action:
The object load continues.
User Action:
Ensure that this will not cause a runtime problem.
Reason:
This is a warning message. During object loading, an unrecognised verb name was found. If the statement(s) referencing it are executed, an error will occur.
System Action:
The object load continues.
User Action:
Ensure that this will not cause a runtime problem.
Reason:
An OML object reload failed due to a storage shortage.
System Action:
The object load fails.
User Action:
Investigate the storage shortage.
Reason:
The OML compiler has encountered a fatal storage shortage.
System Action:
The compile fails.
User Action:
Investigate the storage shortage.
Reason:
The OML compiler has detected errors or warnings while compiling a procedure. This message precedes the actual error messages.
System Action:
The compile error and warning messages follow.
User Action:
Examine the messages and take appropriate action.
Reason:
The OML compiler has encountered a fatal storage shortage.
System Action:
The compile fails.
User Action:
Investigate the storage shortage.
Reason:
The system I/O manager, used to load NCL procedures, has initialized successfully.
System Action:
None.
User Action:
None.
Reason:
This message indicates an unexpected subtask abend by a system I/O subtask.
System Action:
An attempt is made to restart the subtask.
User Action:
Determine the reason for the abend from the operating system log. Contact your product support representative.
Reason:
An I/O error was encountered whilst loading the indicated NCL procedure. I/O error information, as obtained by the SYNADAF function is displayed.
System Action:
The system will retry the load, if possible.
User Action:
None, unless the problem persists. If it does, investigate the problem.
Reason:
The CA Common Services API has initialized successfully.
System Action:
None.
User Action:
None.
Reason:
The CA Common Services API has defined a JES output descriptor of SYSOUT CLASS=A for use by the API's C modules for STDOUT, SYSPRINT.
System Action:
None.
User Action:
If you want to override this definition, include an OUTPUT statement in your JCL.
Reason:
The CA Common Services API has attempted to define a JES output descriptor for use by the API's C modules for STDOUT, SYSPRINT. A definition for TNGPRINT already exists in the JCL.
System Action:
None.
User Action:
None.
Reason:
The CA Common Services API has attempted to define a JES output descriptor for use by the API's C modules for STDOUT, SYSPRINT. The dynamic allocation failed with the return code and reason indicated.
System Action:
None.
User Action:
Use the dynamic allocation reason code to determine the error. Use the /DAIR shortcut to view information about reason codes.
Reason:
NetView pipe emulation has terminated due to an internal error in the PIPEHELP facility.
System Action:
The PIPE command terminates.
User Action:
Contact Computer Associates Technical Support.
Reason:
NetView pipe emulation Extended Trace (TRACE) was specified.
P1 is the NCL ID.
P2 is the trace data.
System Action:
None.
User Action:
Contact Computer Associates Technical Support.
Reason:
NetView pipe emulation Extended Trace ( TRACE ) was specified.
P1 is the NCL ID.
P2 is the trace data.
System Action:
None.
User Action:
Contact Computer Associates Technical Support.
Reason:
NetView pipe emulation DEBUG 1 option was specified and/or the pipe stage (DEBUG) option was specified.
P1 is the stage number.
P2 is the stream number.
P3 are the first 16 characters read from the input stream.
System Action:
None.
User Action:
None.
Reason:
NetView pipe emulation DEBUG 1 option was specified and/or the pipe stage (DEBUG) option was specified.
P1 is the stage number.
P2 is the stream number.
P3 are the first 16 characters written to the output stream.
System Action:
None.
User Action:
None.
Reason:
The IBM MQ interface cannot be initialized because of the reason indicated by the code and extra data.
1 - DISABLED BY JCL PARM
Indicates that the MQI JCL parameter was set to (or defaulted to) N, meaning that the MQ interface was not wanted.
2 - LOAD FOR INTERFACE MODULE mmmmmmmm FAILED
Indicates that the MQ interface was unable to load a module that is required to access the IBM MQ facility. The module must be link edited and installed in the region's load library.
3 - INTERFACE MODULE mmmmmmmm RETURNED NON-ZERO COMPLETION CODE: cc Indicates that the module that provides the interface to the IBM MQ facility was unable to set up the interface.
System Action:
None.
User Action:
For reason code 1, no action is necessary.
For reason code 2, ensure that the relevant module is set up.
For reason code 3, contact Technical Support.
Reason:
This message is part of the response to a STATUS command.
It indicates that the interface to the IBM MQ facility is installed and available for use.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a STATUS command.
It indicates that the MQ interface was not initialized because of the displayed reason:
DISABLED BY JCL PARM
Indicates that the MQI JCL parameter specified or defaulted to N.
LOAD FOR API FAILED (SEE LOG)
Indicates that the requested IBM MQ API module could not be loaded.
API I/F MODULE RETURNED NZ RC (SEE LOG)
Indicates that the requested IBM MQ API module returned an error.
UNKNOWN
Indicates that the reason is not known.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a STATUS command.
It indicates that the status of the MQ interface is not known.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a SHOW MQ command.
It introduces the list of MQ API users.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a SHOW MQ command.
It provides column headings for the NQ0415 message:
NCLID identifies the process.
USERID identifies the user of the process.
QMGR identifies the MQ queue manager to which the process is connected.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a SHOW MQ DETAILS command.
It provides column headings for the NQ0416 message:
ID identifies the open object.
LST-FUNC identifies the last MQ function operated on this object.
CC displays the last MQ API completion code for this object.
RS displays the last MQ API reason code for this object.
T identifies the object type:
L for namelist
M for qmgr (queue manager)
P for process
Q for queue
? for unknown
NAME displays the object name.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a SHOW MQ command.
It provides information about an MQ API user.
For column descriptions, see the NQ0411 message.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a SHOW MQ DETAILS command.
It provides information about an open path for an MQ API user.
For column descriptions, see the NQ0412 message.
System Action:
None.
User Action:
None.
Reason:
This message is issued when the MQ verb encounters an error while processing an MDO that contains message descriptor information, or PUT or GET message options.
The fields describe the error.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
This message is issued when the MQ GET verb encounters an error while processing an MDO that is nominated as the return MDO.
The MDO assignment return code is shown.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
This message is issued when the MQ GET verb encounters an error while processing an MDO that is nominated as the return MDO.
The MDO map connection return code is shown.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
This message is issued when an MQ INQUIRE or MQ SET verb encounters an error while setting up an MDO.
The fields describe the error.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
An MQ SET verb nominated an MDO that is not mapped by the correct map.
The fields describe the error.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
An MQ SET or MQ INQUIRE verb specified the NATTR parameter with an invalid numeric attribute value, aaa .
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
An MQ SET or MQ INQUIRE verb specified the NATTR parameter with the following numeric attribute value duplicated: aaa .
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
An MQ SET verb specified the MDO parameter, but the indicated MDO key, aaa , is not a valid settable attribute.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
An MQ SET verb specified the MDO parameter, but the indicated MDO field (type (CHAR/NUMERIC) and key shown) is not valid data.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
An MQ INQUIRE or MQ SET verb specified the VARS parameter with not enough variables to set the values of the attributes specified in the ATTR or NATTR parameter.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
An MQ SET verb specified the VARS parameter, but the indicated data (type (CHAR/NUMERIC) and attribute code shown) is not valid data.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
An MQ INQUIRE verb specified the MDO parameter, but either the assignment of data or the map connection failed.
System Action:
The process is terminated.
User Action:
Correct the error.
Reason:
An MQ API subtask terminated unexpectedly.
It displays the NCL ID (if known) or the request name that was in progress.
System Action:
None.
User Action:
None.
Reason:
An MQ API subtask terminated unexpectedly.
It provides the subtask termination information, such as the ABEND code.
System Action:
None.
User Action:
None.
Reason:
An MQ API subtask terminated unexpectedly.
Preceding N15Znn messages provide information about the termination.
System Action:
None.
User Action:
Review theN15Znn messages to determine the action.
Reason:
The MQI JCL parameter is set to D or Y, but the region cannot load a required MQ interface module.
mmmmmmmm identifies the module.
rrr displays the internal load facility return code.
ccc displays the system return code.
System Action:
The MQ interface is not activated.
User Action:
Ensure that the relevant MQ load libraries are available to the region through STEPLIB, JOBLIB, LPA, or LINKLIST.
Reason:
This message is logged during NetMaster initialization if a required module related to the REXX interface could not be loaded.
The load failure codes are displayed.
System Action:
Initialization continues. The REXX facility will not be available.
User Action:
Check that the NetMaster load library has not been corrupted.
Reason:
This message is in response to a STATUS command, and indicates that this NetMaster system has the REXX interface available.
System Action:
None.
User Action:
None.
Reason:
This message is the first response message for a SHOW REXX command.
System Action:
Rexx process list messages follow.
User Action:
None.
Reason:
This message is the heading line for the response to a SHOW REXX command.
The column headings are:
The process identification number
The original procedure name
The currently executing (top) procedure name
The external call nesting level W The user window number
The process type:
The process is executing as a command
The process is executing as a function
The process is executing as a subroutine
The process is executing as a server
The owning user id
The 'Environment' that this REXX process is executing in
The associated 'REXXHELP' process identifier
The performance group that this process is executing in
The priority within the performance group.
System Action:
None.
User Action:
None.
Reason:
This message is the first detail line listing a REXX process in response to a SHOW REXX command.
Refer to the description of NR0411 for column headings and meanings.
System Action:
None.
User Action:
None.
Reason:
This message is the second detail line listing a REXX process in response to a SHOW REXX command.
This message indicates the status of the process:
The process is presently executing. The source line number and text currently executing is displayed
The process is presently being forced to wait due to performance controls. The source line number that is about to execute is displayed
The process is presently executing, but the exact statement is indeterminate
The process is presently loading a procedure.\
System Action:
None.
User Action:
None.
Reason:
This message is the first heading line for the response to a SHOW REXXSTAT command.
The column headings are:
The procedure name
The library (DDname) that the procedure was loaded from
SRC or OBJ indicating source or object.
The procedure status:
The procedure is loading
The procedure is pending unload
The procedure has been preloaded
The procedure is presently in use
The procedure was privately loaded:
PRV-NCLT Private load (NCLTEST mode)
PRV-REQ Private internal request
PRV-CHK Private load for RXCHECK command
PRV-OFLD Private load for RXCTL OFFLOAD command
The current number of active users of the procedure
The total number of uses of this procedure since it was loaded.
If loaded privately, the userid that requested the load
If STATUS is 'RETAIN', the 'aged' use count.
System Action:
None.
User Action:
None.
Reason:
This message is the second heading line for the response to a SHOW REXXSTAT command.
The column headings are:
The number of times the procedure moved from AUTOSHR status to RETAIN status
The number of times the procedure moved from RETAIN status to AUTOSHR status
The elapsed time the procedure took to load
The CPU time expended loading the procedure
System Action:
None.
User Action:
None.
Reason:
This message is the third heading line for the response to a SHOW REXXSTAT command.
The column headings are:
The number of source lines in the procedure
The number of blocks used to hold relevant (Non-comment) source lines
The size of the compiled code.
The total size of the compiled procedure in storage.
System Action:
None.
User Action:
None.
Reason:
This message is the first detail line for the response to a SHOW REXXSTAT command.
Refer to message NR0430 for column headings and descriptions.
System Action:
None.
User Action:
None.
Reason:
This message is the second detail line for the response to a SHOW REXXSTAT command.
Refer to message NR0431 for column headings and descriptions.
System Action:
None.
User Action:
None.
Reason:
This message is the third detail line for the response to a SHOW REXXSTAT command.
Refer to message NR0432 for column headings and descriptions.
System Action:
None.
User Action:
None.
Reason:
This message is the heading line for the second part of the response to a SHOW REXXSTAT command.
The column headings are:
A statistics item name (see below)
The value for the named item
The following items can occur:
The current number of preloaded procedures
The current storage occupied by preloaded procedures
The current number of autoshared procedures
The current storage occupied by autoshared procedures
The current number of retained procedures
The current storage occupied by retained procedures
The retain limit set by SYSPARMS RXRETAIN
The current number of privately loaded procedures
The current storage occupied by privately loaded procedures
The total number of 'execution' requests
The number of execution requests handled by an already-loaded, usable procedure
The number of execution requests that could not be handled by an already-loaded, usable procedure
The number of 'execution completed' requests
The number of execution requests satisfied by a preloaded procedure
The number of execution requests satisfied by an autoshared procedure
The number of execution requests satisfied by a retained procedure
the number of execution requests that used a shareable procedure
The number of execution requests that used a private procedure copy
The total number of loads done as a result of an execution request
The total number of procedures moved from the autoshare list to the retain list
The total number of procedures moved from the retain list to the autoshare list
The total number of procedures dropped from the retain list due to overflow
System Action:
None.
User Action:
None.
Reason:
This message is a detail for the second part of the response to a SHOW REXXSTAT command.
Refer to message NR0440 for column headings and descriptions.
System Action:
None.
User Action:
None.
Reason:
An UNLOAD PROCEDURE command requested that a REXX procedure be purged from storage. This message confirms that the request is complete.
System Action:
None.
User Action:
None.
Reason:
An UNLOAD PROCEDURE command requested that a REXX procedure be purged from storage. The procedure is in use and will be purged when its use count drops to 0. Any new requests for the procedure will load a new copy.
System Action:
None.
User Action:
None.
Reason:
A LOAD PROCEDURE command for a REXX procedure is complete.
System Action:
None.
User Action:
None.
Reason:
A LOAD PROCEDURE command requested preloading of a REXX procedure has failed because the procedure is already preloaded.
System Action:
The command is ignored.
User Action:
Use UNLOAD PROCEDURE to unload the preloaded procedure if you want to load a new copy.
Reason:
An UNLOAD PROCEDURE command failed. The requested REXX procedure is not loaded.
System Action:
The command is ignored.
User Action:
None.
Reason:
A UNLOAD PROCEDURE command with generic operands was entered. This message indicates the number of REXX procedures unloaded as a result.
System Action:
None.
User Action:
None.
Reason:
The REXX compiler has detected errors or warnings while compiling a procedure. This message precedes the actual error messages.
System Action:
The compile error and warning messages follow.
User Action:
Examine the messages and take appropriate action.
Reason:
The REXX compiler attempted to open a file to compile it. An error occurred. The message includes a description of the error.
System Action:
The REXX compile fails.
User Action:
Examine the messages and take appropriate action.
Reason:
The REXX compiler opened a file to compile it. The data in the file appears to be IBM- format REXX object code.
This format of object code is not supported by the NetMaster REXX facility. Obtain the source of the REXX program and make that available to NetMaster.
System Action:
The REXX compile fails.
User Action:
Locate the source code for the REXX program and make it available to NetMaster.
Reason:
The REXX compiler was unable to compile the requested program because there was not enough storage.
System Action:
The REXX compilation fails.
User Action:
Increase the storage available to the region.
Reason:
This is a REXX source line. It is written by the REXX compiler during compilation of a REXX program if a listing is requested.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the REXX loader/compiler has repaired a suspect source construct.
The specific correction is to add closing quotes, opening quotes, concatenation operators, and continuation commas to successive lines in the source where a quoted string that crossed lines was detected.
This repair is done only if the SYSPARMS RXQSFIX parameter is set to YES, or the overriding RXCTL OFFLOAD or RXCHECK command QSFIX=YES operand is specified.
REXX normally does not allow a quoted string to cross lines. However the IBM REXX interpreters do, as long as the resulting quoted string (including leading and possibly trailing blanks) does not exceed the REXX limit of 250 characters.
The GREXX compiler does not allow this. The NetMaster interface to GREXX tries to help run REXX source unchanged by repairing the source as follows:
From
SAY 'this is
a string
that crosses
lines...'
To
SAY 'this is'||, ' a string'||, ' that crosses'||, ' lines...'
This will create valid REXX source in all cases.
Note: There is one circumstance where the resulting REXX source, while syntactically correct, may not execute correctly. If the repaired string has a REXX operator of higher precedence than concatenate (||), the resulting expression is processed in the wrong order. Since the only operators of higher precedence are all arithmetic operators, and numbers are not normally in quoted strings(or that long), this case is not likely to occur.
System Action:
None.
User Action:
None.
Reason:
This message is written at the end of a REXX compile if the GREXX compiler returned a non-zero return code, but no other error messages were written.
This can occur if an internal error occurs in the GREXX compiler.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
This message is written if a REXX compile fails due to a severe storage shortage.
The values of ccc (the code) are:
Basic control block storage
Object code output area storage
Source pointer array storage
Source blocks area storage
System Action:
None.
User Action:
Increase the amount of storage available to the region.
Reason:
This message is written if a REXX compile fails due to an abend while reading the source.
System Action:
The compile is terminated.
User Action:
Investigate the abend and correct the problem.
Reason:
This message is written if a REXX compile fails due to an I/O error while reading the source.
System Action:
The compile is terminated.
User Action:
Investigate the error and correct the problem.
Reason:
This message is written when the REXX compiler detects an error in the REXX source.
If the source location is available, this message will contain line and column numbers that may help identify the exact location of the error.
It will be followed by an NR1285 message with more information.
System Action:
Depending on options, the compile may proceed to identify further errors.
User Action:
Correct the error in the REXX source.
Reason:
This message is written when the REXX compiler detects an error in the REXX source.
This message contains additional GREXX compiler error information.
For information about this message, see the IBM REXX manuals.
System Action:
Depending on options, the compile may proceed to identify further errors.
User Action:
Correct the error in the REXX source.
Reason:
A REXX object load failed. The reason code provides a precise indication of the error.
Some of the reason codes are:
001 to 011 - Invalid object header record(s) (generally meaning that the object has been edited or file-transferred with ASCII conversion, etc.).
012 - Object version mismatch. This object was compiled on an incompatible version of NetMaster services.
013 to 029 - See 001 to 011 above.
040 or 042 - Invalid record sentinal. Could indicate that the object has been ASCII/EBCDIC translated.
110 to 113 - Storage shortage.
802 or 803 - Invalid checksum, indicating possible file transfer with ASCII translation, or tampering or editing of the object.
804 - Unexpected end-of-file condition.
805 - I/O abend.
806 - Unrecoverable I/O error.
807 - Not EOF when expected.
808 - Unrecoverable I/O error or abend.
810 - Invalid record sentinal. Could indicate that the object has been ASCII/EBCDIC translated.
All other reason codes indicate internal failures or errors.
System Action:
The object load fails.
User Action:
Examine the error code and take corrective action if possible.
Reason:
A REXX object load failed. A fatal storage shortage occurred.
System Action:
The object load fails.
User Action:
Increase the region size.
Reason:
This message is returned to a requestor of a REXX process (and may be subsequently displayed) when a problem is detected during scheduling of a REXX process.
The fields in the message are return code (rc), information codes 1 and 2 (i1 and i2), and a short description.
The possible values are:
|
rc |
i1 |
i2 |
description |
|---|---|---|---|
|
08 |
10 |
00 |
INVALID REXX PROCEDURE NAME |
|
08 |
12 |
00 |
INVALID REXX ENVIRONMENT NAME |
|
08 |
30 |
00 |
INPUT PARAMETER TOO LONG |
|
08 |
31 |
00 |
INPUT STACK RECORD TOO LONG |
|
08 |
32 |
00 |
PARAMETER EXIT ABORTED EXECUTION |
|
12 |
20 |
00 |
NO STORAGE FOR REXX CONTROL BLOCKS |
|
12 |
21 |
00 |
NO STORAGE FOR INPUT PARAMETERS |
|
12 |
22 |
00 |
NO STORAGE FOR INPUT STACK |
|
12 |
23 |
00 |
COMMAND MUST HAVE MAX 1 PARAMETER |
|
16 |
01 |
00 |
REXX FACILITY NOT AVAILABLE |
|
16 |
02 |
00 |
REXX FACILITY NOT INITIALIZED |
|
16 |
03 |
00 |
SYSTEM IN SHUTDOWN |
System Action:
The requested REXX procedure is not executed.
User Action:
Examine the error information, correct the problem, and retry.
Reason:
This message is displayed when a REXX program executes an OPTIONS statement that contains an unsupported option.
Generally, the REXX language requires the implementation to ignore unrecognized or unsupported options.
However, this implementation will raise an error on the following options:
ETMODE
EXMODE
These options are not supported, as they imply that the execution environment is able to understand DBCS (Double-Byte character set) encodings.
Presently, NetMaster REXX does not support DBCS.
System Action:
A REXX error is signaled.
User Action:
Correct the OPTIONS statement.
Reason:
This message is displayed when a REXX program executes an OPTIONS statement that contains a recognized option, but the syntax of the option is not valid.
System Action:
A REXX error is signaled.
User Action:
Correct the OPTIONS statement.
Reason:
This message is issued when a REXX process requests a function that requires a subtask to be attached.
The subtask attach has failed. The NetMaster log will have additional information.
System Action:
The request fails.
User Action:
Examine the NetMaster log for further information.
Reason:
This message is issued when a REXX process requests a function that requires a subtask to be attached.
The subtask was attached, but failed to initialize. Additional information will be written to the NetMaster log
System Action:
The request fails.
User Action:
Examine the NetMaster log for further information.
Reason:
This message is issued when a REXX process requests a function that is processed by a subtask.
The subtask has abnormally terminated. Additional information will be written to the NetMaster log, including register contents, etc.
System Action:
The request fails.
User Action:
Examine the NetMaster log for further information.
Reason:
This message is issued when a REXX process has issued either a command that is handled by an external program, or a function or procedure call that is handled by an external program.
The external program, executing in a separate subtask, has attempted to call a support routine (defined by the TSO/E REXX assembler API), that NetMaster REXX does not support.
The message contains the following information:
Base (top)REXX procedure name
Current REXX procedure name
Line number in current REXX procedure
SUBCOMN environment or external function name
Load module that was caller
Logical name of the unsupported API entry point
System Action:
The API request fails with an appropriate error return code.
User Action:
Report this to your product support representative.
Note: The supported API routines and actual functions supported in those routines are documented in the NetMaster REXX Guide.
Reason:
This message is issued when a REXX process has issued either a command that is handled by an external program, or a function or procedure call that is handled by an external program.
The external program, executing in a separate subtask, has attempted to call a support routine (defined by the TSO/E REXX assembler API), that NetMaster REXX supported, but the specific function requested is not supported.
The message contains the following information:
Base (top)REXX procedure name
Current REXX procedure name
Line number in current REXX procedure
SUBCOMN environment or external function name
Load module that was caller
Logical name of the requested API entry point
The unsupported function name requested
System Action:
The API request fails with an appropriate error return code.
User Action:
Report this to your product support representative.
Note: The supported API routines and actual functions supported in those routines are documented in the NetMaster REXX Guide.
Reason:
This message is issued when a REXX process has issued either a command that is handled by an external program, or a function or procedure call that is handled by an external program.
The message traces the request. This allows you to see exactly what functions are used by the external program.
The message contains the following information:
Base (top)REXX procedure name
Current REXX procedure name
Line number in current REXX procedure
Load module that was called
API routine name
Function requeted
System Action:
None.
User Action:
None.
Reason:
This message is written when a REXX process completes. It indicates the assigned process ID and the return code.
System Action:
None.
User Action:
None.
Reason:
This message is written when a REXX process completes. It indicates that the requested procedure terminated because of an error.
Error messages will probably precede this message, and can be used to determine the cause of the problem.
System Action:
None.
User Action:
None.
Reason:
This message is written when a REXX process is flushed.
System Action:
None.
User Action:
None.
Reason:
This message is written when a REXX process could not be started.
Additional information is appended to the message in the form of another NetMaster message.
Refer to the help for that message for more information.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the requested RXCTL command (HI, HE, HT, RT, TS, TE) was processed.
The function return code is shown. If 0, the request has worked.
System Action:
The request function may have been performed.
User Action:
None.
Reason:
This message indicates that the requested REXX command (HI, HE, HT, RT, TS, TE) was processed.
The function return code is shown. If 0, the request has worked.
System Action:
The request function may have been performed.
User Action:
None.
Reason:
This message indicates that the requested RXCTL command (DEFINE) was processed.
System Action:
The request function has been performed.
User Action:
None.
Reason:
This message indicates that a RXCTL OFFLOAD command has been issued, and the requested member has been queued for processing by the OFFLOAD processor.
System Action:
A REXX offload compile will run shortly.
User Action:
None.
Reason:
This message indicates that a specific REXX OFFLOAD request that was queued is now being processed.
System Action:
None.
User Action:
None.
Reason:
This message indicates that a specific REXX OFFLOAD request that was queued has completed successfully. The object has been written to the indicated library.
System Action:
None.
User Action:
None.
Reason:
This message indicates that a specific REXX OFFLOAD request that was queued has failed.
The following are possible reasons:
STORAGE SHORTAGE
OUTPUT LIBRARY NOT ALLOCATED
OUTPUT LIBRARY NOT RECFM=F/FB
OUTPUT LIBRARY NOT LRECL=80
COMPILE FAILED
MEMBER LOADED FROM OBJECT
OUTPUT LIBRARY DID NOT OPEN
OUTPUT MEMBER DID NOT OPEN
WRITE ERROR ON OUTPUT LIBRARY
FINAL WRITE ERROR ON OUTPUT LIBRARY
OUTPUT MEMBER CLOSE ERROR
System Action:
No output object is written.
User Action:
Correct the error and retry.
Reason:
This message indicates that a request to define a new SUBCOM handler or external function has failed.
The following are possible reasons:
The requested subcommand environment is already defined, either as a standard one supported by Netmaster, or a previous RXCTL DEFINE command has defined it (the SHOW RXSUBCOM command will show a list of defined environments).
The nominated load module is not available to NetMaster.
There are no more entries in the subcommand table. Contact your support representative.
The nominated function has already been defined by a previous RXCTL DEFINE command.
The nominated function is provided by NetMaster. It cannot be externally defined (use the SHOW RXFUNC command to obtain a list of defined functions).
System Action:
The command is ignored.
User Action:
Correct the error and retry.
Reason:
This message indicates that the requested RXCTL command is not presently supported.
System Action:
The requested function is not performed.
User Action:
None.
Reason:
This message indicates that the requested REXX command is not presently supported.
System Action:
The requested function is not performed.
User Action:
None.
Reason:
This message indicates that a REXX environment has been processed as requested.
System Action:
The requested RXENV function has been performed.
User Action:
None.
Reason:
This message indicates that a REXX environment that was to be added already exists.
System Action:
The RXENV command is ignored.
User Action:
Use the RXENV REPLACE command instead.
Reason:
This message indicates that a REXX environment that was to be deleted was not defined.
System Action:
The RXENV command is ignored.
User Action:
If the name was misspelled, correct the spelling and retry.
Reason:
This message indicates that a REXX environment could not be set as the default environment, as it is not defined.
System Action:
The RXENV command is ignored.
User Action:
Check the environment list (use SH RXENV) and define the environment if required.
Reason:
This message indicates that a REXX environment name supplied on the RXENV command was not valid.
An environment name must be a valid MVS-style PDS member name, the first character A-Z, @, #, or $, and the rest A-Z, 0-9, @, #, or $, with a maximum length of eight characters and no embedded blanks.
The RXENV DEFAULT command also allows a name of .SYSTEM.
System Action:
The RXENV command is ignored.
User Action:
Correct the environment name.
Reason:
A RXCHECK command has been processed. This message shows the result. This message is produced if no errors or warnings were detected.
System Action:
None.
User Action:
None.
Reason:
A RXCHECK command has been processed. This message shows the result. This message is produced if warnings were found (but no errors).
System Action:
None.
User Action:
None.
Reason:
A RXCHECK command has been processed. This message shows the result. This message is produced if errors were found.
System Action:
None.
User Action:
None.
Reason:
A RXCHECK command has been processed. This message is produced if STATS was specified.
The message shows the type of code loaded (SRC or OBJ), the number of lines in the member, and the amount of storage needed.
System Action:
None.
User Action:
None.
Reason:
A RXCHECK command has been processed. This message is produced if STATS was specified.
The message shows the elapsed and CPU times taken to perform the load and compile.
System Action:
None.
User Action:
None.
Reason:
An RXSERV command has been processed. The option and server name are indicated. The requested action has been performed.
System Action:
None.
User Action:
None.
Reason:
An RXSERV command has been processed. The option and server name are indicated. The requested action failed.
Diagnostic information is presented.
System Action:
The requested action is not performed.
User Action:
Investigate the cause and retry.
Reason:
An error occurred during REXX interface initialization.
An attempt to identify an entry point for a REXX interface routine failed. The most likely cause is that another program in the region has loaded a standard REXX routine, thus preventing the NetMaster replacement routines from being identified.
This error should not cause problems, unless user-written external programs use the LOAD or LINK macro to obtain the address of REXX interface programs. Programs that use the REXX external vector table are not affected.
System Action:
REXX initialization continues.
User Action:
None.
Reason:
A request was made to start a REXX server. However, it failed to start. The reason will be a short message. The descriptions of these reasons can be found under the help for message NR2080.
System Action:
The requested server is not started (and is no longer defined).
User Action:
Investigate the cause and retry.
Reason:
A REXX Server has terminated. The termination was because the REXX procedure that is executing as the server has terminated.
This includes cases where the REXX procedure had a fatal error.
System Action:
The requested server terminates (and is no longer defined).
User Action:
Ensure that the REXX procedure terminated as expected. If the procedure terminated with an error, correct the cause of the error and restart the server.
Reason:
A REXX Server failed to initialize in a timely manner.
A REXX server procedure is allowed 10 seconds from when it is started until it issues the first ADDRESS NM REXXSERV GETREQ command.
If the procedure exceeds this limit, it will be terminated and the server deleted.
System Action:
The requested server terminates (and is no longer defined).
User Action:
Ensure that the REXX procedure initializes quickly. It should quickly enter the main processing loop and issue the REXXSERV GETREQ command as soon as possible.
Reason:
A REXXHELP verb received an error from the GRXEXCOM variable access utility. Error information is provided.
System Action:
An OML error is signaled.
User Action:
Contact Technical Support.
Reason:
The language processor could not read the format of the exec.
System Action:
Processing terminates.
User Action:
Check the format of the exec you are passing.
Reason:
The system halted the execution of a REXX program because of an error or by user request.
System Action:
Unless the attention interrupt is intercepted by a 'signal on halt' clause, the REXX exec terminates.
User Action:
If an error caused the termination, check other error messages issued and correct the problem.
Reason:
While attempting to execute a REXX program, the language processor was unable to obtain the storage it needed to continue execution.
System Action:
Processing terminates.
User Action:
Check how the program obtains and frees storage. Either increase the size of the external data queue, or increase the amount of storage available to the program.
Reason:
A comment or a literal string was started but never finished. This may be detected at the end of the program or INTERPRET instruction (for comments) or at the end of a line (for strings).
System Action:
Processing terminates.
User Action:
Examine the REXX program and correct the string.
Reason:
Within a SELECT construct, at least one WHEN construct (and possibly an OTHERWISE clause) is expected. If any other instruction is found (or no WHEN construct is found before OTHERWISE) then this message results. This is commonly caused by forgetting the DO and END around the list of instructions following a WHEN.
System Action:
Processing terminates.
User Action:
Examine the REXX program and correct the error.
Reason:
A THEN or an ELSE has been found that does not match a corresponding IF (or WHEN) clause. This error often occurs because of a missing END or DO...END in part of a complex IF...THEN...ELSE construct.
System Action:
Processing terminates.
User Action:
Examine the program and correct the error.
Reason:
A WHEN or OTHERWISE has been found outside a SELECT construct. It may have been enclosed unintentionally in a DO ... END construct by leaving off an END instruction, or an attempt may have been made to branch to it with a SIGNAL instruction, which cannot work as a SELECT is terminated by a SIGNAL.
System Action:
Processing terminates.
User Action:
Examine your program and fix the part in error.
Reason:
There are more ENDs in the program than DOs and SELECTs, or the ENDs are wrongly placed so they do not match the DOs and SELECTs. It may be useful to use TRACE SCAN to show the structure of the program and more easily locate the error. A common cause of this error is if you use the signal instruction to jump into the middle of this loop. This error is also generated if an END immediately follows a THEN or an ELSE.
System Action:
Processing terminates.
User Action:
Examine the incorrect line and correct the REXX program.
Reason:
An implementation limit of levels of nesting of control structures (DO...END,IF...THEN... ELSE, and so on) has been exceeded. This error might be caused by a looping INTERPRET instruction. It might also be caused by infinite recursive calls.
System Action:
Processing terminates.
User Action:
Examine the incorrect line and fix the program.
Reason:
There may be an implementation restriction that limits the length of the internal representation of a clause. This message is generated if this limit is exceeded.
System Action:
Processing terminates.
User Action:
Reduce the length of literal and hexadecimal strings that exceed the documented limits.
Reason:
The program includes a character outside the literal quoted string that is neither alphanumeric nor one of the acceptable special characters.
System Action:
Processing terminates.
User Action:
Examine the incorrect line and correct the invalid character.
Reason:
On reaching the end of the program (or the end of the string in an INTERPRET instruction), it has been detected that there is a DO or SELECT without a matching END or an IF that is not followed by a THEN clause to execute.
System Action:
Processing terminates.
User Action:
Find the unbalanced DO or SELECT and correct it.
Reason:
Hex constants may not have leading or trailing blanks and may only have embedded blanks at byte boundaries. Only the digits 0-9 and the letters A-F, a-f are allowed. Binary strings can only have blanks added at the boundaries of groups of four binary digits, and only the digits 0 and 1 are allowed.
The error may also be caused by following a literal string by the one character symbol "x" when the string is not intended to be taken as a hexadecimal specification, or by the symbol "b" when the string is not intended to be taken as a binary specification. Use the explicit concatenation operator, "| |", in this situation to concatenate the string to the value of the symbol.
System Action:
Processing terminates.
User Action:
Locate the error on the line and correct it.
Reason:
A SIGNAL instruction has been executed (or an event occurred for which a trap was set) and the specified label cannot be found in the program.
System Action:
Processing terminates.
User Action:
Correct the error and rerun the program.
Reason:
A PROCEDURE instruction was encountered which was not the first instruction executed after a CALL or function invocation. A possible cause of this is "dropping through" into an internal routine rather than invoking it properly.
System Action:
Processing terminates.
User Action:
Examine the incorrect line, correct the problem, and rerun.
Reason:
All IF and WHEN clauses in REXX must be followed by a THEN clause. Some other clause was found when a THEN was expected.
System Action:
Processing terminates.
User Action:
Examine the line and correct the error.
Reason:
Following either the keyword CALL or the sequence SIGNAL ON or SIGNAL OFF, a literal string or a symbol was expected but neither was found.
System Action:
Processing terminates.
User Action:
Add the literal string or symbol that is needed.
Reason:
In the clauses END, ITERATE, LEAVE, NUMERIC, PARSE, and PROCEDURE a symbol can be expected. Either it was not present when required, or some other token was found. Alternatively, the DROP and EXPOSE options of PROCEDURE expect a list of symbols. Some other token was found.
System Action:
Processing terminates.
User Action:
Correct the REXX program and rerun.
Reason:
A clause such as SELECT or NOP is followed by some token other than a comment.
System Action:
Processing terminates.
User Action:
Correct the line and rerun the REXX program.
Reason:
This error results if a literal string contains character codes that are not valid in a particular implementation. This might be because some characters are invalid or because the character set is extended in some way and certain character combinations are not allowed.
System Action:
Processing terminates.
User Action:
Examine the line and correct the error.
Reason:
The setting specified on a TRACE instruction (or as the argument to the TRACE built-in function) starts with a character that does not match one of the valid TRACE settings. This error is also raised if an attempt is made to request TRACE SCAN when inside any kind of control construct.
System Action:
Processing terminates.
User Action:
Correct the line and rerun the REXX program.
Reason:
An unexpected token has been found in the position in an expression where a particular sub-keyword was expected.
System Action:
Processing terminates.
User Action:
Correct the line and rerun the REXX program.
Reason:
The expression for DIGITS or FUZZ in the NUMERIC instruction, or a parsing positional parameter, or a repetition phrase of a DO clause, or the right-hand term of the power("*") operator, did not evaluate to a whole number (or is greater than the implementation limit, for these uses). This error is also raised if a negative repetition count is found in a DO clause.
System Action:
Processing terminates.
User Action:
Correct the line and rerun the REXX program.
Reason:
A syntax error has been found in the DO instruction. This may have occurred because you used the TO, BY, or FOR sub-keywords twice, or because you used these sub-keywords when no control variable was specified.
System Action:
Processing terminates.
User Action:
Correct the line and rerun the REXX program.
Reason:
A LEAVE or ITERATE instruction was encountered in an invalid position. Either no loop is active, or the name specified on the instruction does not match the control variable of any active loop. Note that because internal routine calls and the INTERPRET instruction protect DO loops, they become inactive. A common cause of this error is if you attempt to use the SIGNAL instruction to transfer control within or into the loop.
System Action:
Processing terminates.
User Action:
Fix the problem on the line and rerun the REXX program.
Reason:
The environment name specified by the ADDRESS instruction is longer than permitted for the system under which REXX is running.
System Action:
Processing terminates.
User Action:
Correct the problem and rerun the REXX program.
Reason:
This error results if there is an implementation limit on the length of a variable name or label name (or on the length of a literal string), and this limit is exceeded.
System Action:
Processing terminates.
User Action:
Fix the error and rerun the REXX program.
Reason:
A value has been assigned to a variable whose name starts with a numeric digit or a period. This is not allowed because it would enable numeric constants to be redefined.
System Action:
Processing terminates.
User Action:
Correct the error and rerun the REXX program.
Reason:
A stem has been used in an invalid way. For example, assigning a value to the environmental variable stem (MSG. = 'abc') in an AOF MSG rule is not allowed.
System Action:
Processing terminates.
User Action:
Correct the error and rerun the REXX program.
Reason:
The result of an expression in an instruction was found to be invalid in the particular context in which it was used. This may be because of an illegal FUZZ or DIGITS value in a NUMERIC instruction. (FUZZ may not become larger than DIGITS.)
System Action:
Processing terminates.
User Action:
Correct the error and rerun the REXX program.
Reason:
The expression in an IF, WHEN, DO WHILE, or DO UNTIL phrase must result in a 0 or a 1, as must any term operated on by a logical operator.
System Action:
Processing terminates.
User Action:
Correct the error and rerun the REXX program.
Reason:
This message results from a grammatical error in an expression, such as ending it with an operator or having two operators adjacent with nothing in between. It may also result from a missing expression when one is required. A common error is to include special characters in an intended character expression without enclosing them in quotes.
System Action:
Processing terminates.
User Action:
Correct the error and rerun the REXX program.
Reason:
This error results from not pairing parentheses correctly within an expression. There are more left parentheses than right parentheses.
System Action:
Processing terminates.
User Action:
Examine the line and fix the problem. Then rerun.
Reason:
Either a comma has been found outside a function invocation, or there are too many right parentheses in an expression.
System Action:
Processing terminates.
User Action:
Examine the line and fix the problem.
Reason:
Within a parsing template, a special character that is not allowed has been found, or the syntax of a variable pattern is incorrect. This error may also be raised if the WITH sub- keyword is omitted in a PARSE VALUE instruction.
System Action:
Processing terminates.
User Action:
Examine the program and fix the problem.
Reason:
The expression is too complex to be evaluated by the language processor. There are too many nested parentheses, functions, and so on.
System Action:
Processing terminates.
User Action:
Examine the program and simplify the expression.
Reason:
The specified built-in or external routine does exist but it has been used incorrectly. Either invalid arguments were passed to the routine or the program invoked was not compatible with the REXX language processor, or more than an implementation-limited number of arguments were passed to the routine.
System Action:
Processing terminates.
User Action:
Examine the statement calling the routine and correct it.
Reason:
One of the terms involved in an arithmetic operation is not a valid number, or its exponent exceeds the implementation limit.
System Action:
Processing terminates.
User Action:
Examine the program and correct the problem.
Reason:
The result of an arithmetic operation requires an exponent that is outside the range supported by the implementation. This can happen during evaluation of an expression (commonly an attempt to divide a number by 0), or possibly during the stepping of a DO loop control variable.
System Action:
Processing terminates.
User Action:
Examine the program and correct the error.
Reason:
A function has been invoked within an expression (or a subroutine was invoked by CALL) but it cannot be found. No label with the specified name exists in the program. It is not the name of a built-in function, and the language processor has been unable to locate it externally. The name has probably been mistyped, or it is possible that a symbol or literal string is adjacent to a "(" when it was meant to be separated by a blank or some other operator.
System Action:
Processing terminates.
User Action:
Examine the program and correct the error.
Reason:
An external function has been invoked within an expression, but even though it appeared to end without error, it did not return data for use within the expression.
System Action:
Processing terminates.
User Action:
Examine the program and correct the error.
Reason:
The program has been called as a function, but an attempt is being made (by RETURN) to return without passing back any data.
System Action:
Processing terminates.
User Action:
Examine the program and correct the error.
Reason:
An attempt to indirectly reference a variable is invalid. This would most likely occur on an EXPOSE or INTERPRET instruction; for example, "EXPOSE (Y)" where Y is a number. This error may also occur when you attempt to drop an AOF environmental variable. AOF environmental variables (for example, MSG.TEXT) cannot be dropped. It may also occur if you attempt to reference an AOF environmental variable that is not defined, for example MSG.GLORF.
System Action:
Processing terminates.
User Action:
Examine the program and correct the error.
Reason:
A system service used by the REXX language processor (such as stream input or output) has failed to work correctly and hence normal execution cannot continue.
System Action:
Processing terminates.
User Action:
Examine the program and correct the error.
Reason:
Implementations of the REXX language will normally carry out internal self-consistency checks during execution. This message indicates that some kind of severe error has been detected within the language processor or execution process.
System Action:
Processing terminates.
User Action:
Contact Technical Support for further assistance.
Reason:
The program has used a REXX language feature which is not supported by this version of the REXX interpreter. Code 64 is an extended error code used only by this REXX implementation.
System Action:
Processing terminates.
User Action:
Check documentation for support of the feature. Change REXX program to bypass use of the feature.
Reason:
The program has used the ampersand as a prefix to a symbol. The REXX interpreter does not allow this.
System Action:
Processing terminates.
User Action:
Correct the error and rerun the program.
Reason:
The program has defined the same label name twice.
System Action:
Processing terminates.
User Action:
Change the label on one of the two statements.
Reason:
The program has defined or referenced a function whose name exceeds the maximum function name length of 32 characters.
System Action:
Processing terminates.
User Action:
Change the function name to a shorter name.
Reason:
The program has called a function that requires more arguments than specified on the function call.
System Action:
Processing terminates.
User Action:
Add the necessary arguments to the function call. Check documentation for the specified function.
Reason:
The REXX program has called a function that requires fewer arguments than specified on the function call.
System Action:
Processing terminates.
User Action:
Remove the superfluous arguments to the function call. Check documentation for the specified function.
Reason:
The REXX program was compiled with a version of the REXX interpreter that is lower than the version used to execute the program.
System Action:
Processing terminates.
User Action:
This error should only occur when executing a precompiled, saved version of a program. If this is so, you should recompile and then re-execute the program. If not, contact Technical Support for further assistance.
Reason:
A REXX function written in assembler has returned incorrect data.
System Action:
Processing terminates.
User Action:
Contact Technical Support for further assistance.
Reason:
This is an internal, implementation-specific error.
System Action:
Processing terminates.
User Action:
Contact Technical Support for further assistance.
Reason:
This is an internal, implementation-specific error.
System Action:
Processing terminates.
User Action:
Contact Technical Support for further assistance.
Reason:
The REXX program attempted to assign a value to a variable. The string value exceeded the maximum allowed length.
System Action:
Processing terminates.
User Action:
Shorten the string value.
Reason:
The REXX program could not be compiled. The target code area is not large enough to hold the result of the compiled program.
System Action:
Processing terminates.
User Action:
Shorten the REXX program by dividing it into subroutines, and store these as separate members.
Reason:
A function returned with a non-zero value in R15. The RC variable will contain the value returned in R15.
System Action:
Processing terminates.
User Action:
If this error was caused by a user-written function, correct the error. If this error was caused by a CA-supplied function, contact Technical Support for further assistance.
Reason:
This is an internal implementation-specific error.
System Action:
Processing terminates.
User Action:
Please contact Technical Support to obtain additional assistance.
Reason:
The REXX program executed an INTERPRET instruction that contained a REXX structure not supported in INTERPRET.
System Action:
Processing terminates.
User Action:
Modify the interpreted code.
Reason:
The REXX program was attempting to store an element of an array. The element number was larger than the declared dimension of the array.
System Action:
Processing terminates.
User Action:
Contact Technical Support for further assistance.
Reason:
If this occurs during the compile phase, then the program is using a structure too complex for the compiler to handle. This could occur if a SELECT statement has too many WHEN clauses or there are too many nested control structures.
System Action:
Processing terminates.
User Action:
Reduce the complexity of the flagged structure and retry the compile.
Reason:
If this occurs during the compile phase, then the program is using too many symbols and the symbol table has overflowed.
System Action:
Processing terminates.
User Action:
Reduce the number of symbols used by the program and retry the compile.
Reason:
The REXX program has attempted to use a variable in a manner that is not supported. This could occur if a global variable is used as the control variable in a controlled repetitive loop; for example, DO GLOBAL.I = 1 TO 10.
System Action:
Processing terminates.
User Action:
Modify the REXX program so that it does not use a global variable as the loop control variable.
Reason:
A global symbol whose derived name exceeds the global variable symbol length limit of 50 characters has been used.
System Action:
Processing terminates.
User Action:
Check the incorrect statement and determine which symbol substitution caused the derived name of a global variable to exceed the specified limit. Modify the program to use a shorter derived name.
Reason:
This is an internal, implementation-specific error.
System Action:
Processing terminates.
User Action:
Contact Technical Support for further assistance.
Reason:
This is an internal, implementation-specific error.
System Action:
Processing terminates.
User Action:
Contact Technical Support for further assistance.
Reason:
Procedure function call nesting has exceeded 250 levels.
System Action:
Processing terminates.
User Action:
Examine the program and correct the problem.
Reason:
This message is issued by the NMSSI program if it cannot recognise or does not support the current operating system.
System Action:
NMSSI terminates.
User Action:
If the operating system is not MVS (any varient), MSP (any varient), or VOS3, then NMSSI cannot be used. If it is one of these, contact your support representative.
Reason:
THe NMSSI program must run APF authorised. As it is not, it terminates.
System Action:
NMSSI terminates.
User Action:
Ensure that all libraries in the STEPLIB for the NMSSI job are APF authorised.
Reason:
An error was detected in the NMSSI startup parameters.
System Action:
NMSSI terminates.
User Action:
Examine the preceding error messages that describe the PARM error and correct the erroneous parameter.
Reason:
NMSSI encountered an error whilst attempting to establish ESTAE protection.
System Action:
NMSSI terminates.
User Action:
Contact your product support representative.
Reason:
The NMSSI program was unable to load a required supplementary load module.
System Action:
NMSSI terminates.
User Action:
Examine the job log for preceding system messages that contain the name of the load module that failed to load. Contact your product support representative.
Reason:
The NMSSI program was unable to obtain required virtual storage.
System Action:
NMSSI terminates.
User Action:
Check the region size of the NMSSI job. Contact your product support representative.
Reason:
This message shows a line of input read from SSIIN.
System Action:
None.
User Action:
None, unless followed by a parm error message. In this case this line will aid determination of the error.
Reason:
This message displays the data obtained from the JCL PARM.
System Action:
None
User Action:
None, unless followed by a PARM error message. In this case the information in this message may aid in repair of the error.
Reason:
This message is produced when a parm error is detected during NMSSI initialization.
loc is the position in the previously displayed line from SSIIN (NS0201) or JCL parm (NS0202).
reason is a description of the error, which in most cases is self-explanatory. The list of reasons follows, divided into groups related to the stages of the syntax checking:
UNRECOGNISED PARAMETER
LIST NOT SUPPORTED FOR THIS PARM
QUOTED DATA NOT SUPPORTED FOR THIS PARM
QUOTED DATA REQUIRED FOR THIS PARM
VALUE NOT YES/NO
VALUE NOT YES/NO/*
INVALID/OMITTED PARAMETER NAME
INVALID/OMITTED PARAMETER VALUE
INVALID PARENTHESISED DATA
PARAMETER VALUE TOO LONG
NO DATA AFTER OPEN QUOTE
NO CLOSING QUOTE
INVALID QUOTED STRING
NULL QUOTED STRING
INVALID NAME
INVALID NUMBER
NUMBER NOT IN RANGE
HEX STRING TOO LONG
INVALID HEX STRING
INCORRECT NUMBER OF SUBPARMS
DESCRIPTION TOO LONG
XMS NOT SUPPORTED, YES NOT ALLOWED
XMS=YES was specified on the system which does not support XMS.
VALUE NOT LOG/OPER
CMDENV parameter can only specify LOG or OPER value.
ALREADY PROCESSED SOLVEJOB RESTRICTIONS
SOLVEJOB=* ALREADY PROCESSED
DUPLICATE SOLVEJOB NAME
TOO MANY SOLVEJOB NAMES
SOLVEJOB specification incorrect.
INVALID PFKEY NUMBER
TERMACCESS PFKEY specified is out of range (1–24).
UNUSABLE PFKEY NUMBER
TERMACCESS PFKEY specified is reserved.
DUPLICATE PFKEY NUMBER
TERMACCESS PFKEY specified is already used.
INVALID NMID VALUE
TERMACCESS NMID specified is invalid.
DUPLICATE NMID VALUE
TERMACCESS NMID specified is already used.
ENF CODE NOT NUMERIC
ENFADD/ENFDEL value is not numeric.
ENF CODE NOT IN RANGE
ENFADD/ENFDEL value specified is not in the range of 1–255.
IPSMF=119 NOT SUPPORTED
SMF record 119 processing was requested on the system which does not support it (pre zOS 1.2).
INVALID TCP/IP SERVER NAME
The TCP/IP server name specified by TCPIPSVR is either invalid or specifies unknown TCP/IP server.
System Action:
The NMSSI terminates.
User Action:
Correct the erroneous parameter.
Reason:
This message indicates that an obsolete parameter ( P1 ) was specified. The parameter has been ignored.
System Action:
None.
User Action:
Update your SSI run JCL to remove the obsolete parameter.
Reason:
If NMSSI detects any parameter errors during initialization, this message displays with the total number of errors found.
System Action:
NMSSI terminates.
User Action:
Examine the previous parameter error messages for details about the errors. Correct the errors and restart the NMSSI job.
Reason:
During NMSSI initialization, a call to the load module nnnnnnnn failed.
This may be a message describing the reason for the failure preceding this one (written to the system console or in the SSI log).
System Action:
NMSSI terminates.
User Action:
Examine the WTO messages and SSI log for a message describing the reason for the initialization failure, and follow the advice in the help for that message.
Reason:
During NMSSI initialization, an initialize call to the named load module failed.
System Action:
NMSSI terminates.
User Action:
Contact your product support representative.
Reason:
During NMSSI initialization, an initialize call to the named load module failed.
System Action:
NMSSI terminates
User Action:
Contact your product support representative.
Reason:
The SOLVE SSI has completed basic initialization.
System Action:
NMSSI enters SSI setup initialization.
User Action:
None.
Reason:
This message indicates that NMSSI has completed initialization, ssss is the SSID being used.
System Action:
NMSSI facilities (eg PPI) are now available.
User Action:
None.
Reason:
NMSSI initialization has failed due to an initialization module returning a non-zero return code.
System Action:
NMSSI terminates.
User Action:
Examine the NMSSI log for a previous error message and correct the problem if possible. If you cannot resolve the problem, contact Technical Support.
Reason:
An NMSSI initialization module returned a non-zero return code.
System Action:
NMSSI terminates.
User Action:
Examine the NMSSI log for an error message that may precede this message. If possible, correct the problem. If you cannot resolve the problem, contact Technical Support.
Reason:
An NMSSI initialization module has returned a non-zero return code.
System Action:
NMSSI terminates.
User Action:
Examine the NMSSI log for an error message preceding this message and correct the problem if possible. If unable to correct the problem, contact Technical Support.
Reason:
During NMSSI initialization, an attempt to connect the NMSSI control blocks to the nominated SSID failed.
System Action:
NMSSI terminates.
User Action:
Investigate for use of the same SSID by other third-party software that was initializing at the same time (the storage has been altered since NMSSI checked that it was zero during initialization).
If necessary, assign a different SSID to NMSSI.
Reason:
NMSSI initialization is unable to use the SSID nominated in the initialization parameters, The reasons that can occur are:
The SSID appears to be in use by another NMSSI or SOLVE job (running AOM).
The SSID has not been defined to the operating system (for example, for MVS in IEFSSNxx in SYS1.PARMLIB). (If on MVS/ESA 5.2 or later (including OS/390), this may indicate that the ADDSSID startup parameter is set to 'NO')
Attempts to validate the SSVT pointed to by the SSCVT failed. (see below)
Attempts to validate the control block pointed to by SSCTSUSE failed. (see below)
The SSVT appears to be last-used by an older version of NMSSI. (see below)
An attempt to automatically add the SSID when it was not found (using the MVS/ESA IEFSSI service) failed with the displayed return code.
The validation failures or version mismatch messages can occur when an SSID that was in use by one version of NMSSI or by SOLVE (for AOM) is nominated as the SSID to use in a later version of NMSSI.
New versions of NMSSI may be unable to reuse SSIDs used by previous versions of NMSSI, or by AOM, unless an IPL is performed.
In this case you should use a different SSID. One can be temporarily inserted using the NMAOMSSC program or, on MVS/ESA 5.2 the new SETSSI MVS command.
System Action:
NMSSI will either terminate or prompt the operator for action, depending on the setting of the PROMPT initialization parameter.
User Action:
Respond to message NS1102 (if PROMPT=YES) or correct the NMSSI startup parameter (SSID) and restart NMSSI.
Reason:
This message follows message NS1101 if PROMPT=YES is in effect. It is a WTOR message that can be replied to by the operator.
System Action:
NMSSI waits for a reply.
User Action:
Reply with either the word 'RETRY', meaning that NMSSI will have another attempt to use the current SSID, 'END' meaning that NMSSI will terminate, or any other valid 1-4 character SSID meaning that NMSSI will attempt to use that SSID.
Reason:
This message shows the reply to the previous NS1102 WTOR message.
System Action:
Processing of the reply commences.
User Action:
None.
Reason:
This message indicates that the reply to the previous NS1102 WTOR was not valid. It was not 'RETRY', 'END', or a valid 1-4 character SSID.
System Action:
Message NS1102 is reissued and can be replied to again.
User Action:
Reply to the next NS1102 message with a valid response. Refer to message NS1102 for the correct responses.
Reason:
This message indicates that the SSID nominated in the NMSSI startup parameter file was not found in the list of defined SSIDs in this system. The system is at least MVS/ESA 5.2, and the startup paramater ADDSSID was set to YES. The SSID has been successfully defined to MVS and SSI initialization continues.
The SSID remains defined until the next IPL. It should be defined to MVS in the IEFSSNxx SYS1.PARMLIB member.
System Action:
NMSSI initialization continues using the indicated SSID.
User Action:
The SSID should be added to the SYS1.PARMLIB IEFSSNxx member.
Reason:
NMSSI initialization found an old control block structure connected to the SSID that it is using. It has successfully cleaned this structure. (The previous NMSSI must have abnormally terminated).
System Action:
NMSSI initialization continues.
User Action:
None.
Reason:
SSI initialization found an old control block structure connected to the nominated SSID (P1). It was unable to clean up this structure for the nominated reason (P2). The initialization list entry (ILE) module that detected the error is shown (P3). This message usually indicates that the previous SSI abnormally terminated.
System Action:
The SSI will terminate.
User Action:
Use a different SSID when restarting the SSI or IPL the system to refresh the SSI structure.
Reason:
NMSSI initialization was unable to construct important SSI control blocks. The reasons are as follows:
NMSSI was unable to obtain SQA storage for a mandatory control block.
SSCTSUSE was not zero when attempting to set it.
Attempt to obtain a SYSTEM linkage index failed as indicated.
There are no free SVC numbers in the SVC Table for NMSSI to use for a service SVC.
An attempt to insert a special front-end to a system service failed.
A call to the MVS service routine IEAVG700 failed as indicated.
System Action:
NMSSI terminates.
User Action:
Contact Technical Support.
Reason:
NMSSI was unable to construct the SSI control block structure for the nominated reason:
an SQA GETMAIN for storage for the control block failed.
System Action:
NMSSI terminates.
User Action:
Contact your product support representative.
Reason:
NMSSI initialization was unable to obtain required storage as described in the message while setting up important SSI data structures.
System Action:
NMSSI terminates.
User Action:
Contact Technical Support.
Reason:
The NMSSI cross-memory environment has been successfully established.
System Action:
NMSSI will use cross-memory services for service functions.
User Action:
None.
Reason:
The NMSSI service SVC environment has been established. The SVC number that it found (a free one) is displayed.
System Action:
NMSSI will use SVCs to perform service functions, not cross-memory services.
User Action:
None.
Reason:
The NMSSI initialization has failed while attempting to construct control blocks for the cross-memory support environment.
System Action:
NMSSI terminates.
User Action:
Contact Technical Support.
Reason:
NMSSI initialization failed when trying to set up its service SVC.
System Action:
NMSSI terminates.
User Action:
Contact Technical Support.
Reason:
NMSSI has created Customer Vector Table, also called SAB (SSI Anchor Block).
System Action:
NMSSI initialization continues.
User Action:
None
Reason:
NMSSI has detected the presence of Customer Vector Table, also called SAB (SSI Anchor Block).
System Action:
NMSSI initialization continues.
User Action:
None
Reason:
NMSSI initialization encountered errors during Customer Vector Table (SAB) creation.
System Action:
NMSSI initialization terminates.
User Action:
Check for any errors in the NetMaster installation load libraries setup. Check for Contents Supervisor messages on the NMSSI job log. Contact Technical Support if the problem persists.
Reason:
NMSSI initialization encountered errors during Customer Vector Table (SAB) creation. P1 is the reason code returned by the creation routine.
System Action:
NMSSI initialization terminates.
User Action:
Contact Technical Support if the problem persists.
Reason:
The module performing ssi status detected that Customer Vector Table (SAB) was not created. This indicates that neither SSI nor any other NetMaster function requiring or creating SAB has executed yet.
System Action:
Processing continues.
User Action:
Make sure to start NMSSI if needed.
Reason:
The module performing ssi status received an error indication from the routine providing information about the Customer Vector Table (SAB).
System Action:
Processing continues.
User Action:
Contact Technical Support.
Reason:
Customer Vector Table (SAB) is located at memory address P1.
P2 is the name of the routine which created it.
P3 is the date of creation.
P4 is the time of creation.
System Action:
ssi status command processing continues.
User Action:
None
Reason:
The NMSSI Subsystem Interface has detected that the NMSSI job has terminated abnormally. It stops all SSI processing and writes this message to the console.
System Action:
NMSSI Subsystem Interface functions are disabled.
User Action:
Examine the NMSSI ABEND reasons and restart NMSSI if required.
Reason:
The NMSSI EOT/EOM module has had an internal ABEND during processing. This message contains indicative information.
System Action:
EOM/EOT processing terminates.
User Action:
Contact your product support representative. Note that this message is only produced if using a supplied debugging facility.
Reason:
This message follows message NS1E90 and contains further debugging information.
System Action:
EOM/EOT processing is terminated.
User Action:
see message NS1E90.
Reason:
This message is a diagnostic ABEND message issued by an NMSSI component.
System Action:
NMSSI continues.
User Action:
Contact your product support representative. This message only appears if debugging facilities have been enabled.
Reason:
Additional debugging information. See message NS1H90.
System Action:
See message NS1H90.
User Action:
See message NS1H90.
Reason:
NMSSI code executing in cross-memory or SRB mode has detected an ABEND. This message tells of the ABEND.
System Action:
The function in progress terminates. NMSSI continues.
User Action:
Contact your product support representative.
Reason:
This is additional abend information written to the NMSSI log following message NS1L01.
System Action:
See message NS1L01.
User Action:
See message NS1L01.
Reason:
This is additional information following message NS1L01.
System Action:
See message NS1L01.
User Action:
See message NS1L01.
Reason:
This is additional information following message NS1L01.
System Action:
See message NS1L01.
User Action:
See message NS1L01.
Reason:
This message follows message NS1L01 and contains additional debugging information.
System Action:
See message NS1L01.
User Action:
See message NS1L01.
Reason:
This message is written to the SSI log when the NMSSI attention processor finds that attention events were lost due to queue overflow. The number of attention events lost since the last attention was received is displayed.
System Action:
Processing continues. Terminals might be locked and might need to be reset and an interrupt key re-pressed.
User Action:
If this message occurs frequently, contact your local support office.
Reason:
This message contains NMSSI statistics information. nnnn is the number of 4K blocks of storage allocated for end-of-task or end-of-memory notification control blocks, (the storage is allocated in (E)CSA).
System Action:
None.
User Action:
None.
Reason:
This message contains NMSSI statistics information.
aaaa is the number of GETMAIN macros issued by the NMSSI maintask.
bbbb is the number of FREEMAIN macros issued by the NMSSI maintask.
cccc is the current total amount of GETMAIN storage owned by the NMSSI maintask in subpools 0 to 127.
System Action:
None.
User Action:
None.
Reason:
This message contains NMSSI statistics information. nnnn is the number of cross- memory calls made to processing routines in the NMSSI address space for authorised callers.
System Action:
None.
User Action:
None.
Reason:
This message contains NMSSI statistics. nnnn is the number of cross-memory calls made to service routines in the NMSSI address space for unauthorised callers.
System Action:
None.
User Action:
None.
Reason:
This message contains NMSSI statistics. nnnn is the number of calls made using SRB scheduling to service routines in the NMSSI address space.
System Action:
None.
User Action:
None.
Reason:
This message contains NMSSI statistics. nnnn is the total number of calls from messages NS1Z03, NS1Z04, and NS1Z05 that did not need to wait on the local lock for the NMSSI address space being available.
System Action:
None.
User Action:
None.
Reason:
This message contains NMSSI statistics. nnnn is the total number of calls from messages NS1Z03, NS1Z04, and NS1Z05 that needed to wait for the local lock, but due to a storage shortage were unable to obtain storage for accounting areas to enable the delay to be timed.
System Action:
None.
User Action:
If this number is consistently non-zero, contact your product support representative.
Reason:
This message contains NMSSI statistics. nnnn refers to the total number of calls from messages NS1Z03, NS1Z04, and NS1Z05 that waited for the local lock, and were able to obtain delay information.
System Action:
None.
User Action:
See message NS1Z09, following, for time statistics.
Reason:
The message contains NMSSI statistics.
aaaa is the total wait time for all timed local lock requests, from messages NS1Z03, NS0Z04, and NZ0Z05.
bbbb is the average wait time for the timed requests.
System Action:
None.
User Action:
None.
Reason:
An entered 'SSI' command contained no option.
System Action:
The command is ignored.
User Action:
Add a valid option to the command and try again.
Reason:
An invalid SSI command option was entered.
System Action:
The command is ignored.
User Action:
Correct the command and try again.
Reason:
The SSI STOP command cannot be used until NMSSI initialization is complete (after message NS1001 has been issued).
System Action:
The command is ignored.
User Action:
If NMSSI initialization is stalled, check for an outstanding WTOR (NS1102). You can reply END to that message.
Reason:
An SSI STOP command has been entered, but NMSSI is already shutting down due to a previous SSI STOP command.
System Action:
The command is ignored.
User Action:
None. NMSSI will stop shortly.
Reason:
An SSI STOP command has been entered. NMSSI has entered shutdown and will stop shortly.
System Action:
NMSSI commences shutdown processing.
User Action:
None.
Reason:
A user of NMSSI entered a SSI SIGNOFF command. The user has been signed off.
System Action:
The user is signed off from NMSSI.
User Action:
None.
Reason:
A user has attempted to sign off from a permanent SSI userid.
System Action:
None. The signoff request is ignored.
User Action:
None.
Reason:
A SSI STATUS command has been entered. This is the first response message.
System Action:
Status messages follow.
User Action:
None.
Reason:
The message displays information about NMSSI in response to an SSI STATUS command.
vvvv is the NMSSI version.
pppp is the NMSSI GEN level.
ssss is the NMSSI status as follows:
starting - NMSSI is initialising.
stopping - NMSSI is shutting down.
active - NMSSI is active.
unknown - NMSSI status is indeterminate.
System Action:
None.
User Action:
None.
Reason:
The message displays information about NMSSI in response to a SSI STATUS command.
ssss is the NMSSI SSID.
jjjj is the NMSSI jobname.
oooo is the operating system name.
vvvv is the operating system version.
nnnn is the system name.
System Action:
None.
User Action:
None.
Reason:
The message displays information about NMSSI in response to a SSI STATUS command. It indicates that there is no active connection to a SOLVE or NetMaster region.
System Action:
None.
User Action:
None.
Reason:
The message displays information about NMSSI in response to a SSI STATUS command. It indicates that a connection to a SOLVE or NetMaster region is active.
iiii is the NMID of the region.
jjjj is the job name of the region.
dddd is the domain ID of the region.
System Action:
None.
User Action:
None.
Reason:
The message displays information about NMSSI in response to a SSI STATUS command. It indicates that NMSSI is using cross memory services. The linkage index assigned to this NMSSI is also displayed.
System Action:
None.
User Action:
None.
Reason:
The message displays information about NMSSI in response to a SSI STATUS command, It indicates that a service SVC environment is in use and shows the SVC number.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SSI STATUS command, and indicates that DD SUBSYS is supported by this NMSSI.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SSI STATUS command, and indicates that an attention exit has been installed to process attention requests from terminals and CTCas. The index assigned is also shown.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SSI STATUS command, and provides the current local date and time for the SSI region, as well as the local time offset from GMT/UTC.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SSI STATUS command, and provides the unique value assigned to this SSI region on startup.
(Note that the value is the hardware clock value as at region startup).
System Action:
None.
User Action:
None.
Reason:
This message indicates that NMSSI shutdown has commenced following the issue of an SSI STOP command.
System Action:
NMSSI termination commences.
User Action:
None.
Reason:
This message indicates that NMSSI shutdown is complete.
System Action:
NMSSI terminates.
User Action:
None.
Reason:
This message is issued when an NMSSI EPS link initialises and EPS detects that this NMSSI region is both sides of the link.
System Action:
The EPS link is ignored.
User Action:
Investigate the link definition to see why both ends refer to the same NMSSI region.
Reason:
T=Type N=Name OTS=Old Time Stamp NTS=New Time Stamp
This message is issued when NMSSI EPS obtains a remote endpoint definition that is similar to one already defined, differing only in timestamp. This generally indicates two product regions using the same ACB name.
Values of the Type field:
0 SSI internal
1 SSI
2 XCF
3 CTC
4 UDP
5 VTAM
System Action:
EPS processing continues. This is a warning message.
User Action:
Investigate why the indicated endpoints have the same name and correct as appropriate.
Reason:
This message is a response to the SHOW SSIEPS command indicating that a list of endpoints follows.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command indicating that a list of primary (direct) links follows.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command indicating that a list of access method information follows.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command indicating that a full topology listing follows.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G20 messages.
The columns are:
The endpoint name type (SOLV or SSI)
The endpoint name (SOLVE ACB name or NMSSI sysname and ssid)
The assigned endpoint id
A bitmap of supported EPS classes
The SOLVE or NMSSI version
Various flags
The epid that messages are routed via, or the time the connectivity was lost
The current hop count to this endpoint
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G21 messages.
The columns are:
The SOLVE NMID
The jobname
The system name
The primary ACB
The Management Services level
The SOLVE domain id
The NMSSI ssid
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G22 messages.
The columns are:
The operating system
EPS attribute flags
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G23 messages.
The columns are:
The unacknowledged message window size
The retransmission timeout in seconds
The number of sends
The number of resends
The number of ignored inbound messages (outside window)
The number of ignored inbound acknowledgements (already acknowledged)
The number of send failures
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G24 messages.
The columns are:
The number of messages sent to this endpoint
The number of message bytes sent to this endpoint
The number of messages received from this endpoint
The number of message bytes received from this endpoint
These statistics relate to the actual number of messages or bytes that target this endpoint, as distinct from the total number of messages or bytes that were sent to or received from this endpoint including messages coming via or going via this endpoint.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G25 messages.
The columns are:
The total number of messages received from/via this endpoint
The total number of message bytes received from/via this endpoint
The total number of messages sent to/via this endpoint
The total number of message bytes sent to/via this endpoint
These statistics relate to the total number of messages or bytes that were sent to or via this endpoint, not just messages that targeted this endpoint as source or destination.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint information. Refer to message NS2G10 for headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint information. Refer to message NS2G11 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint information. Refer to message NS2G12 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint information. Refer to message NS2G13 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint information. Refer to message NS2G14 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint information. Refer to message NS2G15 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G35 messages.
The columns are:
The endpoint name type (SOLV or SSI)
The endpoint name (SOLVE ACB name or NMSSI sysname and ssid)
The assigned endpoint id
The number of message segments sent on this path
The number of message bytes sent on this path
The number of message segments received on this path
The number of message bytes received on this path
The number of send errors on this path
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G36 messages.
The columns are:
The access method name for this path
The internal pathid of this path
The maximum unsegmented message allowed on this path
Whether the access method wants EPS to coalesce messages or not
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G37 messages.
The columns are:
The number of message segments sent on this specific path
The number of message bytes sent on this specific path
The number of message segments received on this specific path
The number of message bytes received on this specific path
The number of send errors on this specific path
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G38 messages.
The columns are:
The number of message blocks sent on this specific path
The average number of message segments in a sent block
The number of message blocks received on this specific path
The average number of message segments in a received block
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint link information. Refer to message NS2G30 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint link information. Refer to message NS2G31 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint link information. Refer to message NS2G32 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing endpoint link information. Refer to message NS2G33 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G45 messages.
The columns are:
The A-side of a full topology link entry
The B-side of a full topology link entry
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing column headings for following NS2G46 messages.
The columns are:
The endpoint id that notified this link entry
The endpoint id that the A- side endpoint is known by at the notifying endpoint
The endpoint id that the B- side endpoint is known by at the notifying endpoint
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing link information for an EPS topology display.
Refer to message NS2G40 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command providing topology information. This is a notification entry for the link shown in a previous NS2G45 message.
Refer to message NS2G41 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SHOW SSIEPS command indicating that invalid operands were entered.
System Action:
The command is ignored.
User Action:
Correct the command and retry.
Reason:
This message is issued during NMSSI initialization if insufficient storage is available for SOLVE communications buffers.
System Action:
NMSSI terminates.
User Action:
Increase the NMSSI region size.
Reason:
This message is issued if NMSSI is unable to obtain a buffer to use to send data to a connected SOLVE system. The NMSSI SSID and the SOLVE NMID are displayed in the message.
System Action:
NMSSI retries the request after a short delay.
User Action:
If this message is issued frequently, check the dispatching priorities of the SOLVE region(s) and NMSSI region.
Reason:
NMSSI has connected to a SOLVE system.
jjjj is the jobname of the SOLVE system.
iiii is the NMID.
dddd is the domain id.
System Action:
NMSSI can now accept commands from the connected SOLVE system.
User Action:
None.
Reason:
The SSI connection to the connected SOLVE job has been lost. The SOLVE system might have been terminated or a SYSPARMS SSID=NO command was entered.
System Action:
NMSSI continues processing. SOLVE might reconnect.
User Action:
Determine why the connection was lost and reestablish it if necessary.
Reason:
NMSSI is terminating and has force disconnected the active connection to a SOLVE system. The SOLVE jobname is displayed.
System Action:
NMSSI is terminating. SSI commands cannot be issued from the previously connected SOLVE system.
User Action:
None. NMSSI has been deliberately stopped (by the SSI STOP command)
Reason:
NMSSI startup parameters contained the PPI=YES parameter. However. an attempt to activate PPI support failed as there is another NMSSI job in the system providing PPI services. Only one PPI server can be active in the system at once.
System Action:
NMSSI terminates.
User Action:
Change the PPI=YES parameter in one of the NMSSI jobs. Only one PPI service provider is necessary.
Reason:
This message indicates that the special *PPI SSCVT has been inserted to allow NMSSI to supply PPI services
System Action:
None.
User Action:
None.
Reason:
This message displays NMSSI/PPI statistics. nnnn is the number of PPI receivers that are defined. This count includes inactive receivers.
System Action:
None.
User Action:
None.
Reason:
This is an NMSSI/PPI statistics message. nnnn is the number of GETMAIN instructions issued for storage in the PPI data buffer pool.
System Action:
None.
User Action:
None.
Reason:
The is an NMSSI/PPI statistics message. nnnn is the number of FREEMAIN macro instructions issued during management of the PPI data buffer pool.
System Action:
None.
User Action:
None.
Reason:
This is an NMSSSI/PPI statistics message. nnnn is the number of PPI data buffers allocated out of the PPI storage pool.
System Action:
None.
User Action:
None.
Reason:
This is an NMSSI/PPI statistics message. nnnn is the number of PPI data buffers that had to be GETMAINed as they were too long for the PPI storage pool.
System Action:
None.
User Action:
None.
Reason:
This is an NMSSI/PPI statistics message. nnnn is the number of oversize PPI data buffers that have been FREEMAINed after delivery to the receiver.
System Action:
None.
User Action:
None.
Reason:
This is an NMSSI/PPI statistics message. nnnn is the length of the largest GETMAINed buffer found.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to an SSI STATUS command, and indicates that this NMSSI is providing PPI services.
System Action:
None.
User Action:
None.
Reason:
During NMSSI PPI initialization, an SSCT for *PPI was found, but the SSCTSSVT pointer was not 0.
System Action:
NMSSI terminates.
User Action:
Contact Technical Support.
Reason:
During NMSSI PPI initialization, NMSSI was unable to GETMAIN storage for an SSCVT for PPI.
System Action:
NMSSI terminates.
User Action:
Contact Technical Support.
Reason:
During NMSSI PPI initialization, a duplicate *PPI SSCVT was found.
System Action:
NMSSI terminates.
User Action:
Contact Technical Support.
Reason:
During NMSSI PPI initialization, an attempt to insert the *PPI SSCVT using the IEFSSI macro failed. The return and reason codes are displayed.
System Action:
NMSSI terminates.
User Action:
Contact Technical Support.
Reason:
During NMSSI PPI initialization, the IEFSSI macro was used to insert the *PPI sscvt; however after this the *PPI SSCVT could not be located.
System Action:
NMSSI terminates.
User Action:
Contact Technical Support.
Reason:
This message is written to the NMSSI log whenever the generated name scavenger facility has reclaimed inactive PPI receivers that have been named using the 'get unique name' facility. The message shows how many names were reclaimed in the last pass of the list of receivers.
Refer to the PPIINATO and PPIREUSE SSI startup parameters for more information regarding PPI receiver id reuse.
System Action:
None.
User Action:
None.
Reason:
This message is issued (via WTO) when the NMSSI initialization parameter PPIRC90T is set to YES, and a PPI API user is due to receive a return code 90. The information in this message mirrors the information returned to the caller in register 0. The message is followed by a dump of the RPB.
System Action:
THe PPI caller receives a return code of 90 in the RPB return code field and additional debugging information in R0.
User Action:
Determine the cause for the return code 90 and correct it.
Reason:
This message follows message NS3580 and provides additional debugging information about the PPI return code 90. This information is a hexadecimal dump of the PPI RPB.
System Action:
None.
User Action:
See message NS3581.
Reason:
This message signifies the end of the PPI RC90 debugging messages.
System Action:
None.
User Action:
None.
Reason:
This is a diagnostic message from NMSSI. It provides ABEND information.
Note that this message is issued in the context of a PPI user's address space. It is WTO'd.
System Action:
NMSSI continues.
User Action:
Provide the diagnostic information to your product support representative. Note that this message is only produced if NMSSI internal debugging facilities are enabled.
Reason:
This message follows the NS3590 message and contains additional debugging information.
System Action:
Refer to message NS3590.
User Action:
Refer to message NS3590.
Reason:
THis is a header message for the SHOW PPIUSERS command output. It maps the contents of the NS3903 message. Columns are:
NAME - The PPI receiver name.
STATUS - The PPI receiver status, ACTIVE or INACTIVE.
JOBNAME - The jobname of an active PPI receiver.
ASID - The ASID of an active PPI receiver.
AUTH - The APF authorisation requirement for sending to this PPI receiver.
Q-LIMIT - The queue limit of the PPI receiver
CUR-QUE - The number of messages currently queued to this PPI receiver.
TOT-QUE - The total number of messages queued to this PPI receiver.
System Action:
None.
User Action:
None.
Reason:
This is a second header message for output from the SHOW PPIUSERS command. It maps message NS3904.
The headings are:
CUR-KBS - The current storage (in Kbytes) occupied by currently queued messages.
TOT-KBS - The total amount of storage (in Kbytes) occupied by all queued messages.
System Action:
None.
User Action:
None.
Reason:
This message is part of the SHOW PPIUSERS command output.
Refer to message NS3901 for column headings and their meanings.
System Action:
None.
User Action:
None.
Reason:
This is part of the SHOW PPIUSERS command output.
Refer to message NS3902 for column headings and their meanings.
System Action:
None.
User Action:
None.
Reason:
A SHOW PPIUSERS command was entered when the NMSSI was initialising or terminating.
System Action:
The command is ignored.
User Action:
None.
Reason:
A SHOW PPIUSERS command was entered, but this NMSSI job is not providing PPI services.
System Action:
The command is ignored.
User Action:
None.
Reason:
A SHOW PPIUSERS=name command was entered. The name specified is not a valid PPI receiver name.
System Action:
The command is ignored.
User Action:
Correct the name operand and retry the operation.
Reason:
A SHOW PPIUSERS command was entered, The INACT parameter was specified more than once.
System Action:
The command is ignored.
User Action:
Correct the duplicate operand and retry the operation.
Reason:
A SHOW PPIUSERS command was entered, but an unrecognised operand was supplied.
System Action:
The command is ignored.
User Action:
Correct the unrecognised operand and retry the operation.
Reason:
A DD SUBSYS DD statement referring to an active NMSSI that is providing DD SUBSYS services does not have a second parameter with the function name. DD statements that use the NMSSI DD SUBSYS facility must have a SUBSYS=(ssid,function,other,parms) parameter.
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS statement.
Reason:
A DD SUBSYS JCL statement that refers to an NMSSI subsystem name does not have a valid function name parameter after the subsystem name. The function parameter must be a 1 to 8 character name.
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS JCL statement.
Reason:
A DD SUBSYS JCL statement referring to an active NMSSI subsystem has an unrecognised DD SUBSYS function name. Check the NMSSI DD SUBSYS documentation for a list of valid function names.
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS JCL statement.
Reason:
A DD SUBSYS JCL statement referring to an active NMSSI subsystem has an invalid number of parameters for the requested function.
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS JCL statement.
Reason:
A DD SUBSYS function has returned an invalid return code to the NMSSI DD SUBSYS manager.
System Action:
A JCL error is raised.
User Action:
Report the error to your SOLVE support representative.
Reason:
This message is only issued for the NMSSI DD SUBSYS function under exceptional circumstances, for example SSI shutdown, when no other specific message has been issued.
System Action:
A JCL error is raised.
User Action:
If the error occurs repeatedly, report it to your SOLVE support representative.
Reason:
This message is produced by the NMSSI DD SUBSYS support modules under exceptional circumstances.
System Action:
An allocation failure will occur for the job.
User Action:
If the error occurs repeatedly, contact you SOLVE support representative.
Reason:
An NMSSI DD SUBSYS function has been unable to obtain storage to process an allocation request.
System Action:
The subsystem dataset fails allocation, leading to a job step initialization failure.
User Action:
Investigate the reason for the storage shortage.
Reason:
An open failure occurred on an NMSSI DD SUBSYS dataset. The ddname and ssid are displayed in the message.
The error codes are:
1 - SSI inactive.
2 - internal error.
3 - internal error.
4 - invalid ACB MACRF1 (should not happen when opening a DCB).
5 - invalid ACB MACRF2 (should not happen when opening a DCB).
6 - invalid ACB MACRF3 (should not happen when opening a DCB).
7 - open for input not allowed.
8 - open for output not allowed.
9 - open for update not allowed.
10 - open sequential not allowed.
11 - open addressed not allowed.
12 - open direct not allowed.
13 - internal error.
14 - internal error.
15 - internal error.
16 - GETMAIN failure.
System Action:
None.
User Action:
None.
Reason:
A DD SUBSYS JCL statement referring to an NMSSI subsystem was being processed while the SSI was not active.
System Action:
A JCL or allocation error is raised.
User Action:
Restart the NMSSI subsystem.
Reason:
An ABEND occurred whilst processing a DD SUBSYS statement that referred to an NMSSI subsystem.
System Action:
A JCL, allocation, or open error is raised.
User Action:
Contact you SOLVE support representative.
Reason:
This message follows message NS4090 and provides additional debugging information.
System Action:
See message NS4090,
User Action:
See message NS4090.
Reason:
A DD SUBSYS DD statement has had an I/O operation attempted on it but a control block validation test has failed. Reasons for the failure can include:
This message is followed by a USER ABEND U0001.
System Action:
The program issuing the I/O request is abended with a U0001 user abend.
User Action:
Determine why the NMSSI program was stopped.
Reason:
A DD SUBSYS statement using the COPY facility to copy all records to another dataset had an invalid COPY operand.
The COPY operand must be a valid 1 to 8 character DDname.
System Action:
A JCL error is raised.
User Action:
Correct the COPY operand.
Reason:
A DD SUBSYS statement using the FILTER facility had an invalid FILTER operand.
The FILTER operand must be in the format FILTER=pgm, FILTER=(pgm), or FILTER=(pgm,parm) where both pgm and parm are 1 to 8 character values.
System Action:
A JCL error is raised.
User Action:
Correct the FILTER operand.
Reason:
A DD SUBSYS statement using the COPY facility had the same DDname for the COPY target as this DD statement.
This is not valid.
System Action:
A JCL error is raised.
User Action:
Correct the COPY operand to use a different target DDname.
Reason:
A DD SUBSYS statement using the COPY facility could not be opened as the nominated COPY DDname was not defined in the JCL.
System Action:
The open is failed with an ABEND 013-C0.
User Action:
Ensure that the nominated COPY DDNAME is defined.
Reason:
A DD SUBSYS statement using the COPY facility could not be opened as insufficient storage was available to obtain storage for the COPY DCB.
System Action:
THe open is failed with an ABEND 013-C0.
User Action:
Ensure that sufficient storage is available in the region.
Reason:
A DD SUBSYS statement using the COPY facility could not be opened. During OPEN processing of the COPY dataset, an internal error occurred:
04 - ESTAE setup failed.
08 - GETMAIN failure.
12 - ESTAE driven.
System Action:
The OPEN is failed with an ABEND 013-C0.
User Action:
Contact your SOLVE support office.
Reason:
A DD SUBSYS statement using the COPY facility could not be opened. The COPY dataset OPEN failed. The only return code is 04 which means that the OPEN of the COPY dataset failed.
System Action:
The OPEN fails with an ABEND 013-C0.
User Action:
Contact your SOLVE support office.
Reason:
A DD SUBSYS statement using the COPY facility could not be opened. A GETMAIN to obtain storage for an I/O area for the COPY dataset failed.
System Action:
The OPEN fails with an 013-C0 ABEND.
User Action:
Ensure that there is sufficient storage available to the job.
Reason:
A DD SUBSYS statement using the FILTER facility failed to open. The user-specified FILTER program could not be loaded.
System Action:
The OPEN fails with an ABEND 013-C0.
User Action:
Ensure that the FILTER program is available on either a step library, the linklist, or in LPA. If the job step is authorised, the filter program MUST be loaded from an APF authorised library.
Reason:
A DD SUBSYS statement using the FILTER facility could not be opened. Storage could not be obtained for the FILTER program parameter lists.
System Action:
The OPEN is failed with an ABEND 013-C0.
User Action:
Ensure that sufficient storage is available in the region.
Reason:
A DD SUBSYS statement using the FILTER facility could not be opened. An internal error occurred:
04 - ESTAE setup failed.
08 - GETMAIN failure.
12 - ESTAE driven (User FILTER program probably ABENDed).
System Action:
The OPEN is failed with an ABEND 013-C0.
User Action:
Contact your SOLVE support office.
Reason:
A DD SUBSYS statement using the FILTER option could not be opened. The FILTER program returned a non-zero return code on the Initialise call.
System Action:
The OPEN is failed with an ABEND 013-C0.
User Action:
Determine why the FILTER program returned a non-zero return code.
Reason:
This message is produced if an ABEND occurs during DD SUBSYS processing when the FILTER option is being used. It contains debugging information.
System Action:
The abend is retried and an error returned to the caller.
User Action:
Contact your SOLVE support office with the message details.
Reason:
This message follows message NS4290 and contains additional debugging information.
System Action:
See message NS4290.
User Action:
See message NS4290.
Reason:
This message indicates that a null parameter was supplied on a DD SUBSYS JCL statement using the PPISEND option.
System Action:
A JCL error is raised.
User Action:
Correct or remove the null parameter.
Reason:
This message is the result of a DD SUBSYS JCL statement that contains an unrecognised parameter for the PPISEND service.
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS JCL statement.
Reason:
A DD SUBSYS JCL statement using the PPISEND function has a duplicated parameter.
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS JCL statement.
Reason:
A DD SUBSYS JCL statement using the PPISEND option has an invalid TARGET name specified.
The TARGET name must be a valid PPI receiver name.
System Action:
A JCL error is raised.
User Action:
Correct the target name.
Reason:
A DD SUBSYS JCL statement using the PPISEND option has an invalid value specified for the SOURCE operand.
The value must be a valid PPI receiver/sender name or one of the special values: *JOB, *STEP, *PSTEP.
System Action:
A JCL error is raised.
User Action:
Correct the DD statement.
Reason:
A DD SUBSYS statement using the PPISEND option did not have a TARGET operand specified.
The TARGET operand is mandatory, to specify the target PPI receiver.
System Action:
A JCL error is raised.
User Action:
Correct the DD statement to add a TARGET operand.
Reason:
A DD SUBSYS statement using the PPISEND option has an invalid value for the QFULL operand.
Valid values for the QFULL operand are ERROR (default) and IGNORE.
System Action:
A JCL error is raised.
User Action:
Correct the QFULL operand.
Reason:
A DD SUBSYS statement using the PPISEND option has an invalid value for the BASE operand.
The BASE value must be a number from 1 to 32760.
System Action:
A JCL error is raised.
User Action:
Correct the BASE operand.
Reason:
A DD SUBSYS JCL statement using the PPISEND facility could not be opened as the CNMNETV PPI module could not be loaded.
System Action:
THe open fails with an ABEND 013-C0.
User Action:
Determine why CNMNETV could not be loaded. A step library may be necessary.
Reason:
A DD SUBSYS DD statement using the PPISEND facility failed. A GETMAIN macro instruction to obtain storage failed.
System Action:
The OPEN is failed with an ABEND 013-C0
User Action:
Determine the reason for the storage shortage.
Reason:
A DD SUBSYS JCL statement using the PPISEND facility failed to open. A PPI error occurred. The PPI function code and return code are shown. These codes can be looked up in the SOLVE user reference PPI chapters. Common return codes are decoded with a reason: PPI NOT ACTIVE (return code 24) RECEIVER UNDEFINED (return code 26)
System Action:
The OPEN fails with an ABEND 013-C0.
User Action:
Correct the problem and restart the affected job.
Reason:
A DD SUBSYS DD statement OPEN failed, for an internal reason:
04 - ESTAE failure.
08 - GETMAIN failure.
12 - ESTAE driven
System Action:
None.
User Action:
Contact your product support representative.
Reason:
This message is produced if an ABEND occurs during DD SUBSYS processing for the PPISEND function. IT contains debugging information.
System Action:
The abend is retried and an error returned to the caller.
User Action:
Contact your product support representative with the message details.
Reason:
This message follows message NS4A90 and contains additional debugging information.
System Action:
See message NS4A90.
User Action:
See message NS4A90.
Reason:
This message is produced if an invalid DD SUBSYS Parameter for the WTO function is found. A null parameter (for example 2 adjacent commas in the SUBSYS parameter) was found.
System Action:
A JCL error occurs.
User Action:
Correct the DD SUBSYS JCL statement.
Reason:
This message is produced if a DD SUBSYS JCL statement using the WTO option has an invalid or unrecognised parameter. The parameter in error is displayed.
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS JCL statement.
Reason:
A DD SUBSYS DD statement using the WTO option has a duplicated parameter.
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS JCL statement.
Reason:
A DD SUBSYS statement using the WTO option has an invalid ROUTCDE parameter. The ROUTCDE parameter must be a parenthesised list of numbers from 1 to 16 or 1 to 128 (MVS/XA 2.2 or higher).
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS JCL statement.
Reason:
A DD SUBSYS statement using the WTO option has an invalid DESC parameter. The DESC parameter must be a parenthesised list of 1 to 16 numbers, each from 1 to 16.
System Action:
A JCL error is raised.
User Action:
Correct the DD SUBSYS JCL statement,
Reason:
A DD SUBSYS statement using the WTO option has an invalid value for the PREFIX operand.
The prefix must be a character string from 1 to 12 characters in length, or NO to suppress the prefix.
System Action:
A JCL error is raised.
User Action:
Correct the PREFIX value.
Reason:
A DD SUBSYS statement using the WTO option has an invalid value for the BASE operand.
The BASE value must be a number from 1 to 32760.
System Action:
A JCL error is raised.
User Action:
Correct the BASE operand.
Reason:
A DD SUBSYS statement using the PPIRECV option has a null parameter.
System Action:
A JCL error is raised.
User Action:
Correct the DD statement.
Reason:
A DD SUBSYS statement with the PPIRECV option has an invalid or unrecognised parameter specified.
System Action:
A JCL error is raised.
User Action:
Correct the invalid parameter. It may be misspelt.
Reason:
A DD SUBSYS statement with the PPIRECV option has had a parameter duplicated.
System Action:
A JCL error is raised.
User Action:
Correct the DD statement.
Reason:
A DD SUBSYS DD statement for the PPIRECV parameter has an invalid value specified for the ID parameter.
The ID value must be a valid PPI receiver name.
System Action:
A JCL error is raised.
User Action:
Correct the receiver id.
Reason:
A DD SUBSYS statement with the PPIRECV option has an invalid value for the APF option specified.
The value must be NO or YES.
System Action:
A JCL error is raised.
User Action:
Correct the APF parameter.
Reason:
A DD SUBSYS statement for the PPIRECV option has an invalid value for the IQEMPTY operand.
The IQEMPTY option can have values of EOF, WAIT, or (WAIT,n)
System Action:
A JCL error is raised.
User Action:
Correct the IQEMPTY option.
Reason:
A DD SUBSYS statement using the PPIRECV option has an invalid value specified for the QEMPTY parameter.
Valid values for the QEMPTY parameter are EOF, WAIT, and (WAIT,n).
System Action:
A JCL error is raised.
User Action:
Correct the QEMPTY operand.
Reason:
A DD SUBSYS statement using the PPIRECV option has an invalid value for the MAXQUEUE operand.
A MAXQUEUE value is a number from 1 to 9999.
System Action:
A JCL error is raised.
User Action:
Correct the MAXQUEUE option.
Reason:
A DD SUBSYS statement using the PPIRECV option does not include an ID operand. This operand is mandatory; it sets the PPI receiver name.
System Action:
A JCL error is raised.
User Action:
Add the ID operand to the DD statement SUBSYS parameters.
Reason:
A DD SUBSYS statement for the PPIRECV option failed to open. The CNMNETV module could not be loaded.
System Action:
The OPEN fails with an ABEND 013-C0.
User Action:
Ensure that the CNMNETV module is available in the step library or the system linklist, or in LPALIB.
Reason:
A DD SUBSYS statement using the PPIRECV option failed to open, as a GETMAIN for storage failed.
System Action:
The open fails with an ABEND 013-C0.
User Action:
Ensure that sufficient storage is allocated to the region.
Reason:
A DD SUBSYS statement using the PPIRECV option failed to open. PPI returned an unexpected return code.
Some of the return codes have an additional reason appended.
System Action:
The OPEN fails with an ABEND 013-C0.
User Action:
Determine the reason for the PPI return code.
Reason:
A DD SUBSYS statement using the PPIRECV option OPEN failed. An internal error occurred. The errors are:
4 - ESTAE failed.
8 - GETMAIN failed.
12 - ESTAE driven.
System Action:
The OPEN fails with an ABEND 013-C0.
User Action:
Contact your SOLVE product support office.
Reason:
This message is produced if an ABEND occurs during DD SUBSYS processing for the PPIRECV function. It contains debugging information.
System Action:
The abend is retried and an error returned to the caller.
User Action:
Contact your SOLVE support office with the message details.
Reason:
This message follows message NS4E90 and contains additional debugging information.
System Action:
See message NS4E90.
User Action:
See message NS4E90.
Reason:
A DD SUBSYS statement using the USER option has a null parameter.
System Action:
A JCL error is raised.
User Action:
Correct the DD statement.
Reason:
A DD SUBSYS statement with the USER option has an invalid or unrecognised parameter specified.
System Action:
A JCL error is raised.
User Action:
Correct the invalid parameter. It may be misspelt.
Reason:
A DD SUBSYS statement with the USER option has had a parameter duplicated.
System Action:
A JCL error is raised.
User Action:
Correct the DD statement.
Reason:
A DD SUBSYS DD statement for the USER option has an invalid value specified for the PROGRAM parameter.
The PROGRAM operand must be a valid 1 to 8 character program name.
System Action:
A JCL error is raised.
User Action:
Correct the program name.
Reason:
A DD SUBSYS statement with the USER option has an invalid value for the PARM parameter specified.
The value must be a valid 1 to 8 character name.
System Action:
A JCL error is raised.
User Action:
Correct the PARM parameter.
Reason:
A DD SUBSYS statement using the USER option does not include a PROGRAM operand. This operand is mandatory; it sets the name of the user program to call.
System Action:
A JCL error is raised.
User Action:
Add the PROGRAM operand to the DD statement SUBSYS parameters.
Reason:
A DD SUBSYS statement for the USER option failed to open. The indicated user program module could not be loaded.
System Action:
The OPEN fails with an ABEND 013-C0.
User Action:
Ensure that the user program is available in the step library or the system linklist, or in LPALIB. If the program opening the dataset is APF authorised, the specified program MUST come from an APF library.
Reason:
A DD SUBSYS statement using the USER option failed to open, as a GETMAIN for storage failed.
System Action:
The open fails with an ABEND 013-C0.
User Action:
Ensure that sufficient storage is allocated to the region.
Reason:
A DD SUBSYS statement using the USER option OPEN failed. An internal error occurred. The errors are:
4 - ESTAE failed.
8 - GETMAIN failed.
12 - ESTAE driven.
System Action:
The OPEN fails with an ABEND 013-C0.
User Action:
Contact your SOLVE product support office.
Reason:
A DD SUBSYS statement using the USER option failed to open. The user program returned the indicated return code on the OPEN call.
System Action:
The OPEN fails with an ABEND 013-C0
User Action:
Determine why the user program returned a non-zero return code.
Reason:
This message is produced if an ABEND occurs during DD SUBSYS processing for the USER function. It contains debugging information.
System Action:
The abend is retried and an error returned to the caller.
User Action:
Contact your SOLVE support office with the message details.
Reason:
This message follows message NS4G90 and contains additional debugging information.
System Action:
See message NS4G90.
User Action:
See message NS4G90.
Reason:
This message is issued when an ARM-related ENF event is issued. It is WTO'd to the system log (no consoles). It is only issued for ARM registration events. The fields in the message are:
aaa - Y or N indicating whether the ARM element is restarting
bbb - the jobname
ccc - the ARM element name
ddd - the ARM element type
eee - the original system name that the element executed on
fff - the new (current) system name that the element is executing on
ggg - the ARM policy restart group that the element belongs to
System Action:
None.
User Action:
None.
Reason:
This message is issued when an ARM-related ENF event is issued. It is WTO'd to the system log (no consoles). It is only issued for ARM ready events. The fields in the message are:
aaa - Y or N indicating whether the ARM element is restarting
bbb - the jobname
ccc - the ARM element name
ddd - the ARM element type
eee - the original system name that the element executed on
fff - the new (current) system name that the element is executing on
ggg - the ARM policy restart group that the element belongs to
System Action:
None.
User Action:
None.
Reason:
This message is issued when an ARM-related ENF event is issued. It is WTO'd to the system log (no consoles). It is only issued for ARM deregistration events. The fields in the message are:
aaa - Y or N indicating whether the ARM element is restarting
bbb - the jobname
ccc - the ARM element name
ddd - the ARM element type
eee - the original system name that the element executed on
fff - the new (current) system name that the element is executing on
ggg - the ARM policy restart group that the element belongs to
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SSI STATUS command if the NMSSI ENF facility is active (that is, the NMSSI startup parameter ENF=YES was specified). It indicates that the facility is active.
System Action:
None
User Action:
None
Reason:
This message is issued in response to an SSI STATUS command if the NMSSI ENF facility is active (that is, the NMSSI startup parameter ENF=YES was specified). It shows a list of the ENF codes that are being monitored.
System Action:
None
User Action:
None
Reason:
This message is issued in response to a SHOW SSISTATS command, and indicates that NMSSI ENF facility statistics follow.
System Action:
Further ENF messages follow.
User Action:
None
Reason:
This message is issued in response to a SHOW SSISTATS command, and provides column headings for the following NS4X12 messages.
The column headings are:
The event code
The event name
The event type, either TASK or SRB
The token assigned by ENF when the NMSSI ENF exit was registered
The number of occurrences of this event
The number of times an error occurred during event processing
System Action:
NS4X12 messages follow.
User Action:
None
Reason:
This message is issued in response to a SHOW SSISTATS command, and provides statistical information about ENF events that NMSSI handles.
The column headings are documented under the message NS4X11.
System Action:
None
User Action:
None
Reason:
This message is issued in response to a SHOW SSISTATS command, and provides details about the last error that occurred when processing the event described by the previous NS4X12 message.
System Action:
None
User Action:
None
Reason:
This message is issued during NMSSI initialization if an error occurs during registration of an ENF event listener.
Information describing the event and error is displayed.
System Action:
NMSSI terminates.
User Action:
Contact your product support office and supply the information contained in this message.
Reason:
This message is issued during NMSSI initialization if an error occurs when requesting storage for a work pool for ENF message processing.
System Action:
NMSSI terminates.
User Action:
Check the region size for the NMSSI region.
Reason:
During NMSSI startup, the parameter ENF=YES was processed; however, the ENF facility is not supported on this operating system.
System Action:
NMSSI terminates.
User Action:
Remove the ENF=YES initialization parameter.
Reason:
During NMSSI startup, the parameter ENF=YES was processed. However, the XMS parameter was set to NO. Use of the ENF function requires XMS=YES.
System Action:
NMSSI terminates.
User Action:
Remove the ENF=YES initialization parameter, or add the XMS=YES initialization parameter.
Reason:
During NMSSI startup, an ENFADD or ENFDEL initialization parameter was processed. The ENF code on the parameter was valid, but is not supported by this release of NMSSI. The parameter is ignored.
System Action:
The ENFADD or ENFDEL parameter is ignored.
User Action:
Remove the ENFADD or ENFDEL parameter from the NMSSI initialization statements.
Reason:
This message is the title line for the SHOW SSIUSERS display. This display shows information about all logged on SSI users. Refer to message NS6022 for more information about this display.
System Action:
None.
User Action:
None.
Reason:
This message is the detail display of the SHOW SSIUSERS display. Each line of the display shows information about a user who is logged on to the SSI. The meanings of the fields are as follows:
aaaaaaaa - the userid of the user. The userid might be generated by the SSI if the user is a background region user, or is the SOLVE userid of the user.
bbbbbbbb - the node from which the user is logged on. This name might be generated by the SSI for background SSI users, or might be the NCLID of the NCL process within SOLVE which has issued an SSI command, or might be the LUNAME of the terminal on which the SOLVE user who issued an SSI command is logged on.
cccc - the type of user. This will be NUSR if the user is logged on to the SSI from SOLVE, or will be the background region type if the user is an SSI background region user.
dddd - the environment type if the user is logged on from SOLVE (for example, VTOP if OCS, PROC if dependent environment)
eeeeeeee - the LU (terminal) if the user is logged on from SOLVE
System Action:
None.
User Action:
None.
Reason:
This message is the first response message to the SHOW SSISTATS command. Other statistics messages follow.
System Action:
None.
User Action:
None.
Reason:
This message is issued if NMSSI is unable to produce statistics in response to the SHOW SSISTATS command. This message is issued if the SSI is initialising or terminating.
System Action:
The command is ignored.
User Action:
None.
Reason:
An ATTACH command has been entered to cause a terminal to be connected to the SSI, but no device address has been supplied.
System Action:
The command is rejected.
User Action:
Enter the ATTACH command with the address of the required device. The device address must be 3 hexadecimal characters that are the channel address of the device.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, but the device address supplied on the ATTACH command is not valid.
System Action:
The command is rejected.
User Action:
Enter the command again with a valid device address. The device address is 3 hexadecimal characters, which are the channel address of the device.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, but an operand specified on the ATTACH command is not recognised as being a valid operand.
System Action:
The command is rejected.
User Action:
Correct the operand which is incorrect, and re-enter the command.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, but an operand on the ATTACH command has been entered twice.
System Action:
The command is rejected.
User Action:
Remove one of the duplicated operand occurrences and retry the command.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, but two of the operands on the ATTACH command are mutually exclusive.
System Action:
The command is rejected.
User Action:
Correct the command by removing one of the operands, and retry.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, but the amount of user data supplied on the DATA= operand exceeds the maximum allowable amount.
System Action:
The command is rejected.
User Action:
Re-enter the command with less user data. The maximum length of user data is 32 bytes.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, but the AUTOLOG= operand specifies an invalid value.
System Action:
The command is rejected.
User Action:
Correct the command and retry. The valid values for AUTOLOG are YES and NO.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, but the NAME= operand specifies an invalid value.
System Action:
The command is rejected.
User Action:
Correct the command and retry. The NAME= operand value must conform to standard PDS member name conventions.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, but the device address specified represents a device which is already connected to the SSI.
System Action:
The command is rejected.
User Action:
Correct the device address and retry the command.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, but the name specified on the NAME= operand of the ATTACH command matches the name assigned to a device which is already connected to the SSI.
System Action:
The command is rejected.
User Action:
Re-enter the command, using a different device name.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI. The command has been successfully processed.
System Action:
The SSI will attempt to attach the device.
User Action:
None. Subsequent messages will indicate the success or otherwise of the attempt to attach the device.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI, and no name was specified on the command. However the terminal address is 4-digits (no leading 0), and the terminal prefix value has 5 characters. The resulting name has 9 characters and is too long.
System Action:
The command is rejected.
User Action:
Re-enter the command providing a specific terminal name.
Reason:
You entered an ATTACH command to attach a terminal to the SSI, but the SSI is not capable of attaching any terminals.
System Action:
The command is rejected.
User Action:
Investigate the reason for the inability of the SSI to attach terminals. The support of terminals requires the TERMINALS=YES SSI startup parameter, or terminal support may be disabled due to failure of the initialization of the terminal attention exit.
Reason:
A DETACH command has been entered to detach a terminal from the SSI, but no device address has been supplied to identify which terminal is to be detached.
System Action:
The command is rejected.
User Action:
Re-enter the command with the device address as the only operand.
Reason:
A DETACH command has been entered to detach a terminal from the SSI, but the device address supplied is not valid.
System Action:
The command is rejected.
User Action:
The device address must be from 001 to FFF inclusive. Correct the device address and retry the command.
Reason:
A DETACH command has been entered to detach a terminal from the SSI, but an unrecognised operand has been detected on the DETACH command.
System Action:
The command is rejected.
User Action:
The only operand valid on the DETACH command is the device address. Correct the command and retry.
Reason:
A DETACH command has been entered to detach a terminal from the SSI, but the device is already detaching.
System Action:
The terminal will soon be detached.
User Action:
None.
Reason:
A DETACH command has been entered to detach a terminal from the SSI, but a storage shortage has prevented NMSSI from processing the detach request.
System Action:
The device is not detached.
User Action:
Investigate the cause of the storage shortage.
Reason:
A DETACH command has been entered to detach a terminal from the SSI, but the device address specified does not represent a terminal which is currently attached to the SSI.
System Action:
The command is rejected.
User Action:
Correct the device address and retry the command.
Reason:
A DETACH command has been entered to detach a terminal from the SSI, and the command has been processed successfully.
System Action:
The specified terminal will be detached from the SSI.
User Action:
None. Message NS6F01 will appear when the detach processing has completed.
Reason:
A DETACH ALL command has been entered to detach all terminals from the SSI. The command has been processed successfully. aaaaaa shows the number of terminals which are to be detached.
System Action:
All terminals attached to the SSI will be detached.
User Action:
None. Message NS6F01 will appear for every terminal that is detached.
Reason:
You entered a DETACH command to detach a terminal from the SSI, but the SSI is not capable of supporting attached terminals.
System Action:
The command is rejected.
User Action:
Investigate the reason for the inability of the SSI to attach terminals. The support of terminals requires the TERMINALS=YES SSI startup parameter, or terminal support may be disabled due to the failure of the initialization of the terminal attention exit.
Reason:
During processing of an ATTACH command, a DYNALLOC macro is issued to perform dynamic allocation of the terminal using its channel address. The DYNALLOC macro has completed with r15 non-zero, indicating an error has occurred which prevented successful allocation of the device.
aaa - is the channel address of the device
bbbb - is the r15 value on return from the DYNALLOC macro
cccc - shows the Dynamic Allocation Interface Routine (DAIR) return code for the allocation request.
dddd - shows further qualifying information about the allocation request.
System Action:
The terminal will go through deallocation steps to ensure no trace of the failed allocation remains.
User Action:
Investigate the reason for the dynamic allocation failure using the DAIR return code.
Reason:
During ATTACH processing to attach a terminal to the SSI, a DEVTYPE macro is issued by the SSI to attempt to identify the specified device to ensure it is a supported device. The DEVTYPE macro has failed with R15 set as shown.
System Action:
The SSI will perform deallocation of the terminal to clear any remaining knowledge of the failed attach request.
User Action:
Investigate the failure of the DEVTYPE macro, using the R15 value to identify why the macro failed.
Reason:
During processing of an ATTACH request, the SSI issues a DEVTYPE macro to attempt to identify the device as being a supported device type. The information returned by the DEVTYPE macro indicates the device is not one which is supported by the SSI.
System Action:
The SSI will perform deallocation of the device to remove any remaining knowledge of the failed ATTACH request.
User Action:
The SSI only supports terminals attached to Local Non-SNA control units. If the device is a terminal attached to a Local Non-SNA control unit, contact SOLVE product support and supply them with the value of the returned devtype value 'bbbb'.
Reason:
During processing of an ATTACH request, an OPEN macro is issued to open communication between the SSI and the terminal. An ABEND has occurred during processing of the OPEN macro. The code bbbb shows the abend code.
System Action:
The SSI will perform deallocation of the device to remove all knowledge of the failed attach attempt.
User Action:
Investigate the reason for the abend, using the abend code supplied in this message.
Reason:
During processing of an ATTACH request, an OPEN macro is issued to open communications with the terminal. The OPEN request has failed.
System Action:
The SSI will perform deallocation processing to remove all knowledge of the failed request.
User Action:
Retry the ATTACH command. If the problem persists, contact your product support representative.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI. The attach processing has completed successfully and the terminal is now under SSI control.
System Action:
If AUTOLOG=NO was specified on the ATTACH command, the terminal will be sent the SSI LOGO. If AUTOLOG=YES was specified on the ATTACH command, the terminal will be passed to SOLVE.
User Action:
None.
Reason:
An ATTACH command has been entered to cause a terminal to be attached to the SSI. The Dynamic Allocation requested device address 'aaa' but the device with address 'bbb' was returned. This could indicate that a product such as Systems Managed Storage has returned a different device.
System Action:
The device is unallocated.
User Action:
Investigate the reason for the different device being returned. NMSSI does not allow the address to be different.
Reason:
A storage shortage has occurred during processing of input from SSI terminal aaaaaaaa.
System Action:
The input is discarded. The terminal remains connected to NMSSI.
User Action:
Investigate the reason for the storage shortage condition.
Reason:
When input is available from a terminal connected to NMSSI, an attention interrupt occurs which causes NMSSI to take action to retrieve the input from the terminal. This message is sent to the SSI log if NMSSI could not be notified of the attention interrupt.
System Action:
The input is not retrieved from the terminal.
User Action:
Report this problem to your SOLVE support representative.
Reason:
A request has been made to pass a terminal which is under NMSSI control to a SOLVE system, but the function key pressed is not assigned to a SOLVE system.
System Action:
The request to pass the terminal to SOLVE is rejected.
User Action:
Use function keys that have an active SOLVE assignment.
Reason:
A request has been made to pass a terminal from NMSSI control to SOLVE. However, the requested SOLVE system is not presently connected to the NMSSI that owns the terminal. This might be because the SOLVE system is not active.
System Action:
The request to connect to SOLVE is ignored.
User Action:
Investigate why the requested SOLVE system is not active or not connected to an NMSSI.
Reason:
A terminal which is connected to a SOLVE system via NMSSI has been returned to NMSSI control because the SOLVE system disconnected from NMSSI or refused the terminal session.
System Action:
The terminal is returned to NMSSI control.
User Action:
Investigate the reason for the termination of communication between NMSSI and SOLVE.
Reason:
A session with a SOLVE system was cancelled by pressing PF03/PF15 in the NMSSI menu, which cancelled the current SOLVE session.
System Action:
The terminal is returned to NMSSI control.
User Action:
None. A user action caused this message.
Reason:
A terminal which is connected to a SOLVE system via NMSSI has been returned to NMSSI control because the SOLVE system disconnected from NMSSI or dropped the terminal session.
System Action:
The terminal is returned to NMSSI control.
User Action:
Investigate the reason for the termination of communication between NMSSI and SOLVE.
Reason:
A session with a SOLVE system could not be established. The return code values are:
04 - unknown target SOLVE system
08 - storage shortage
12 - internal error
16 - internal error
20 - internal error
24 - internal error
System Action:
The terminal is returned to NMSSI control.
User Action:
If the return code indicates an internal error, contact your product support office.
Reason:
A session with a SOLVE system was refused by SOLVE.
System Action:
The terminal is returned to NMSSI control.
User Action:
Contact your product support office.
Reason:
An error occurred while attempting to read input from a terminal.
System Action:
The terminal stays under NMSSI control.
User Action:
Attempt the operation again. If the failure persists, contact your product support office.
Reason:
An error occurred while attempting to read input for the named terminal.
System Action:
The input is ignored.
User Action:
Report this problem to your SOLVE product support representative.
Reason:
An internal processing error occurred during processing of the named terminal.
System Action:
The terminal is discarded.
User Action:
Contact your product support office.
Reason:
An internal processing error occurred during processing of the named terminal.
System Action:
The terminal is discarded.
User Action:
Contact your product support office.
Reason:
A storage shortage has occurred during processing of input from terminal aaaaaaaa. This has caused NMSSI to discard the terminal.
System Action:
The terminal is discarded.
User Action:
Investigate the cause of the storage shortage condition.
Reason:
This message signifies the completion of detach processing for a terminal which has been attached to the SSI. This may indicate normal detach processing, initiated by the terminal user, or may indicate that cleanup after an unsuccessful attach request has been completed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the SSI STATUS display. It indicates that support for SSI attached terminals is active. This message does not appear if the support of attached terminals is not enabled.
System Action:
None.
User Action:
None.
Reason:
This message is the title line of the SHOW SSITERMS display. It shows column headings for the detail lines of the display. Refer to the description of message NS6J02 for more information about the display.
System Action:
None.
User Action:
None.
Reason:
This message is the detail line of the SHOW SSITERMS display. It shows information about each terminal which is under SSI control, or is connected to SOLVE via the SSI. The meanings of each field is as follows:
aaa - the channel address of the terminal
bbbbbbbb - the symbolic name assigned to the terminal either by the SSI or specified in the ATTACH command
cccccccc - the DDname assigned by the system during the dynamic allocation of the device by the SSI
dddddddd - the status of the terminal. This shows if the terminal is connected to the SSI, in the process of attaching or detaching, or is currently logged on to SOLVE.
eee - indicates if the terminal has encountered any I/O errors
fff - indicates if the terminal is currently under control of the SSI or a SOLVE system and which one
ggg - indicates if the terminal was attached to the SSI with the AUTOLOG option, which causes the terminal to be immediately passed to SOLVE
System Action:
None.
User Action:
None.
Reason:
This message is another title line of the SHOW SSITERMS display. It shows column headings for the detail lines of the display. Refer to the description of message NS6J04 for more information about the display.
System Action:
None.
User Action:
None.
Reason:
This message is another detail line of the SHOW SSITERMS display. It shows the status of a SOLVE connection for the terminal described in the previous NS6J02 message.
The first field is the ACB name of a SOLVE system, the second is the status of the connection, which can have the following values:
STARTING - the terminal is presently connection to the SOLVE system
IN-SESSION - the terminal has a session with the SOLVE system
*ENDED* - the terminal has disconnected from the SOLVE system, however this has not been acknowledged yet
System Action:
None.
User Action:
None.
Reason:
A SHOW SSITERMS command has been entered to display the status of all terminals connected to the SSI, but the SSI is not capable of attaching terminals.
System Action:
None.
User Action:
Investigate why the SSI does not support terminal attachment.
Reason:
This message is issued during NMSSI startup if errors are detected while compiling the panel definitions for the Non-VTAM terminal management feature.
It indicates that there are errors in the definitions and that details can be found on the SSI LOG.
System Action:
NMSSI terminates.
User Action:
Examine the error messages on the SSILOG dataset.
Reason:
This message is issued during NMSSI startup if errors are detected while compiling the panel definitions for the Non-VTAM terminal management feature.
This message is logged and describes the error.
System Action:
NMSSI terminates.
User Action:
Report the error(s) to your product support office.
Reason:
A 3270 datastream has been sent to terminal aaaaaaaa. The command code (the first byte in the datastream) is not supported by NMSSI.
System Action:
The datastream is not sent to the terminal.
User Action:
Check if the command code is valid for a local Non-SNA terminal. If so report the problem to your SOLVE product support representative.
Reason:
This message is the first message produced for an I/O trace where NMSSI is sending data to a terminal. This message shows the terminal name and a description of the I/O request.
System Action:
None.
User Action:
This message is followed by NS6X03, NS6X04, NS6X05, NS6X06 and NS6X07 messages. These messages contain more information about the I/O request. Terminal I/O tracing can be enabled using the TERMDEBUG NMSSI startup parameter.
Reason:
This message is preceded by NS6X02. This is a hexadecimal dump of the data sent to the terminal.
System Action:
None.
User Action:
None.
Reason:
This message is part of an outbound I/O terminal trace where NMSSI is sending data to a terminal. This message preceeds a hexadecimal dump of the CCW used for the I/O operation.
System Action:
None.
User Action:
This message is followed by NS6X05, which contains a hexadecimal dump of the CCW. If the command requires a chained command, two CCWs are used, and are chained together. In this case the hexadecimal dump shows both CCWs, which are consecutive in storage.
Reason:
This message is preceded by NS6X04. This is a hexadecimal dump of the CCW used in the I/O operation.
System Action:
None.
User Action:
None.
Reason:
This message is part of an outbound I/O terminal trace where NMSSI is sending data to a terminal. This message preceeds a hexadecimal dump of the IOB used for the I/O operation.
System Action:
None.
User Action:
This message is followed by NS6X05, which contains a hexadecimal dump of the IOB.
Reason:
This message is preceded by NS6X06. This is a hexadecimal dump of the IOB used in the I/O operation.
System Action:
None.
User Action:
None.
Reason:
This message is the produced on completion of I/O to a terminal which is being traced by NMSSI. It is the first in a series of messages which provide information about the results of the I/O operation.
System Action:
None.
User Action:
This message is followed by NS6X09, NS6X10, NS6X11, NS6X12 and NS6X13 messages. These messages contain more information about the results of the I/O request. Refer to these messages for more information.
Reason:
This message is preceded by NS6X08. This is a hexadecimal dump of the data sent from the terminal to NMSSI as a result of the I/O operation.
System Action:
None.
User Action:
None.
Reason:
This message is produced when I/O completes for a terminal which is being traced by NMSSI. This message is followed by a hexadecimal dump of the CCW used for the operation.
System Action:
None.
User Action:
This message is followed by NS6X11, which contains the hexadecimal dump of the CCW used for the operation. If the command required a chained command, two CCWs are used, and are chained together. In this case the hexadecimal dump shows both CCWs, which are consecutive in storage.
Reason:
This message is preceded by NS6X10. This is a hexadecimal dump of the CCW after the I/O operation has completed.
System Action:
None.
User Action:
None.
Reason:
This message is produced when I/O completes for a terminal which is being traced by NMSSI. This message is followed by a hexadecimal dump of the IOB used for the operation.
System Action:
None.
User Action:
This message is followed by NS6X13, which contains the hexadecimal dump of the IOB used for the operation.
Reason:
This message is preceded by NS6X10. This is a hexadecimal dump of the IOB after the I/O operation has completed.
System Action:
None.
User Action:
None.
Reason:
This message is produced when I/O completes for a terminal which is being traced by NMSSI. This message indicates that the I/O operation did not result in the terminal sending data to NMSSI.
System Action:
None.
User Action:
None.
Reason:
During SSI initialization with attached terminal support enabled, the SSI attempts to initialize several items to allow handling of attention interrupts which represent changes in terminal state, for example, power on, key pressed.
This process involves the use of temporary storage, crucial to the operation of the attention exit, but the GETMAIN for the required amount of storage has failed.
System Action:
The attention interrupt exit and attached terminal support are disabled.
User Action:
Investigate the reason for the storage shortage that caused the GETMAIN failure.
Reason:
During SSI initialization with terminal or ctca support enabled, the SSI attempts to insert an attention interrupt handler into the system's interrupt handler table.
The attempt to insert the SSI attention interrupt routine information into the system's interrupt table has failed, because the table is of a limited size and all available space has been used.
System Action:
NMSSI terminates.
User Action:
Investigate the usage of the interrupt table.
Reason:
This is a diagnostic message from NMSSI. It provides ABEND information.
Note that this message is issued in the context of a PPI user's address space. It is WTO'd.
System Action:
NMSSI continues.
User Action:
Provide the diagnostic information to your product support representative. Note that this message is only produced if NMSSI internal debugging facilities are enabled.
Reason:
This message follows the NS7090 message and contains additional debugging information.
System Action:
Refer to message NS7090.
User Action:
Refer to message NS7090.
Reason:
This is a diagnostic message from NMSSI. It provides ABEND information.
Note that this message is issued in the context of a PPI user's address space. It is WTO'd.
System Action:
NMSSI continues.
User Action:
Provide the diagnostic information to your product support representative. Note that this message is only produced if NMSSI internal debugging facilities are enabled.
Reason:
This message follows the NS7092 message and contains additional debugging information.
System Action:
Refer to message NS7092.
User Action:
Refer to message NS7092.
Reason:
A command input buffer (CIB) was received from a QEDIT operation. The CIBVERB field contained an invalid verb code.
System Action:
The CIB is ignored.
User Action:
Report the problem to your product support representative.
Reason:
NMSSI was started using the 'START' operating system command. Parameters were specified on this command. NMSSI does not allow parameters to be specified in this way.
System Action:
The parameters are ignored.
User Action:
If you need to specify overriding parameters when starting NMSSI, use the JCL EXEC statement PARM field.
Reason:
The operating system 'STOP' ('P') command is not supported by NMSSI.
System Action:
The command is ignored.
User Action:
Use the 'F jobname,SSI STOP' command to stop NMSSI.
Reason:
The SOLVE Subsystem Interface has terminated. This message informs the operator, and is the last message on the SSI log.
System Action:
The SSI terminates.
User Action:
None.
Reason:
This message is written to the SSI log when an SSI user environment is terminated.
uuuu is the userid.
nnnn is the terminal name.
System Action:
None.
User Action:
None.
Reason:
The entered command is not a valid NMSSI command.
System Action:
The command is ignored.
User Action:
Correct and re-enter the command.
Reason:
The entered command name does not uniquely identify an NMSSI command. For example, 'S' could be 'SSI' or 'SHOW'.
System Action:
The command is ignored.
User Action:
Correct and re-enter the command.
Reason:
The command entered to NMSSI was longer than 256 characters.
System Action:
The command is ignored.
User Action:
Correct and re-enter the command.
Reason:
The SHOW command entered to NMSSI did not contain a SHOW operand.
System Action:
The command is ignored.
User Action:
Correct and re-enter the command.
Reason:
The entered SHOW command for NMSSI contained an unrecognised operand.
System Action:
The command is ignored.
User Action:
Correct and re-enter the command.
Reason:
This message is written to the system console when an NMSSI region or job ABENDs. The message contains the abend code, SSID, jobname, date, and time of the abend.
System Action:
NMSSI takes a formatted dump and a system dump. This message is followed by the NS9502 and NS9503 messages with additional information.
User Action:
Contact your support office with the details of the ABEND.
Reason:
This message is written to the system console when an NMSSI region or job ABENDs. It follows the NS9501 message and contains information about the abend. The fields are:
SRC= P1 - The source of the abend information. P1 is either: AB - meaning that the information in this and the NS9503 message was derived from the PSW and registers at the time of the abend, or SE - meaning that the information was derived from the registers and PSW from the NMSSI primary RB
PRD= P2 - The product name (normally NMSSI)
REL= P3 - The product internal release level
SP= P4 - The product service pack level
ABC= P5 - The ABEND code:
S-xxx for a SYSTEM abend
U-nnn for a user abend
N-aaa-bb for an internal NMSSI abend
System Action:
See message NS9501.
User Action:
See message NS9501.
Reason:
This message is written to the system console when an NMSSI region or job ABENDs. It follows the NS9502 message and contains information about the abend. The fields are:
ALM=aaa - The ABEND load module
ALO=bbb - The offset within the ABEND load module
ACS=ccc - The ABEND CSECT, if it could be identified
ACO=ddd - The offset within the ABEND CSECT, if the CSECT could be identified
LLM=eee - The last apparent active load module
LCS=fff - The last apparent CSECT
System Action:
See message NS9501.
User Action:
See message NS9501.
Reason:
The UNIX interface provided by the SSI is now active and may be used by SOLVE regions. The EPS service name that SOLVE regions will use to connect to this is P1.
System Action:
Processing continues.
User Action:
None required.
Reason:
The UNIX interface attempted to obtain storage for a RACROUTE workarea and was unsuccessful.
System Action:
Processing continues. The PROGRAM and HOME definitions which may be present are not used, that is, the default program /bin/sh is executed with no home directory.
User Action:
Check the storage allocated to the SSI region.
Reason:
A RACROUTE EXTRACT call made by the UNIX interface failed with return code P1 and reason P2 .
System Action:
Processing continues. The PROGRAM and HOME definitions, which may be present, are not used. The default program /bin/sh is executed with no home directory.
User Action:
Check the return and reason codes in the Security Server (RACF) Messages and Codes manual.
Reason:
The UNIX interface is available only on OS/390 release 2.5 or higher.
System Action:
SSI initialization continues without UNIX support.
User Action:
Remove the UNIX=YES parameter from the SSI startup deck if UNIX support is not required, or run the SSI on OS/390 2.5 or higher.
Reason:
The UNIX interface must run in supervisor state, but another startup parameter has prevented this.
System Action:
The SSI terminates.
User Action:
Check the SSI startup deck for other parameters that may conflict with running the UNIX interface.
Reason:
The UNIX interface is already being provided by an SSI running in another region on the same OS/390 system.
System Action:
SSI initialization continues without UNIX support.
User Action:
Remove the UNIX=YES parameter from the SSI startup deck for this SSI, or terminate the other SSI region.
Reason:
This message precedes a dump of a connect request buffer when a trace of connect activity for the UNIX interface is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
This message precedes a dump of a connect response buffer when a trace of connect activity for the UNIX interface is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The UNIX interface EPS exit is about to start a conversation thread to manage an incoming connection request. This message is issued when a trace of connection activity is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
None.
Reason:
The UNIX interface EPS exit has received a DISCONNECT request from a client. This message is issued when a trace of connection activity is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
None.
Reason:
This message precedes a dump of a SEND request buffer when a trace of command activity for the UNIX interface is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
None.
Reason:
This message precedes a dump of a SEND response buffer when a trace of command responses for the UNIX interface is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
None.
Reason:
A UNIX interface conversation thread has been started to manage an EPS conversation from an incoming connection request. This message is issued when a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
None.
Reason:
The UNIX interface conversation manager has issued a RACROUTE call to extract an individual caller's OMVS definition. This message is issued when a trace of module flow is requested and UNIXSEPUSER=YES was specified.
P1 is a unique path identifier for this caller.
System Action:
If P2 is 0, the user's OMVS segment values for PROGRAM and HOME is used; otherwise PROGRAM value defaults to /bin/sh and no HOME value.
User Action:
If P2 is non-zero, see the Security Server (RACF) Messages and Codes manual.
Reason:
P2 was the return code returned to the UNIX interface conversation manager from an ATTACH of the UNIX owning task. This message is issued if a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
If P2 is 0, processing on behalf of the caller continues; otherwise the thread terminates and the caller receives a return code indicating that initialization failed.
User Action:
If P2 is non-zero, see the MVS Assembler Services Reference for an explanation of return codes from the ATTACH macro.
Reason:
The UNIX subtask ABENDed during initialization. This message is issued if a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
The thread terminates and the caller receives a return code indicating that subtask initialization failed.
User Action:
See the system log for messages relating to subtask termination.
Reason:
The UNIX subtask has successfully initialized. This message is issued if a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
None.
Reason:
The UNIX conversation manager is waiting for the client to disconnect or the subtask to terminate. This message is issued if a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
None.
Reason:
The UNIX client has disconnected (normally from a CLOSE). This message is issued if a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
The subtask is notified to perform an orderly termination, after which the conversation thread is terminated.
User Action:
None.
Reason:
The UNIX subtask has terminated. This message is issued if a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
The conversation thread is terminated.
User Action:
See the system log for further messages relating to subtask activity.
Reason:
The UNIX conversation thread has terminated. This message is issued if a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
The conversation thread is terminated.
User Action:
None.
Reason:
The STDIN task has been started for a UNIX client. This message is is issued when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
Separate user signon was requested and the call to UNIX to create a separate security environment failed. This message is issued only if a trace of module flow is requested.
System Action:
Processing for the UNIX client is terminated.
User Action:
Check the &SYS.UNIX.CALL, &SYS.UNIX.RETCODE, and &SYS.UNIX.REASCODE system variables returned to the calling program for more information.
Reason:
The call to start the UNIX SHELL failed. This message is issued only if a trace of module flow is requested.
System Action:
Processing for the UNIX client is terminated.
User Action:
Check the &SYS.UNIX.CALL, &SYS.UNIX.RETCODE, and &SYS.UNIX.REASCODE system variables returned to the calling program for more information.
Reason:
An attempt to attach the subtask to read results from the SHELL failed. This message is issued only if a trace of module flow is requested.
System Action:
Processing for the UNIX client is terminated.
User Action:
Check system log for any other messages relating to the failure.
Reason:
The subtask to read results from the SHELL has initialized. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The subtask to read results from the SHELL has terminated during initialization. This message is issued only if a trace of module flow is requested.
System Action:
Processing for the client is terminated.
User Action:
Check the system log for any other messages relating to the problem.
Reason:
The client has closed the connection prior to initialization completing. This message is issued only if a trace of module flow is requested.
System Action:
Processing for the client is terminated.
User Action:
Check client program in SOLVE to determine the reason for disconnection.
Reason:
The subtask to write commands to the SHELL has initialized. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
A command is about to be written to the UNIX SHELL for execution. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
An attempt to write a command to the UNIX SHELL failed. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
Check the &SYS.UNIX.RETCODE and &SYS.UNIX.RETVAL system variables returned to the calling program in SOLVE.
Reason:
A chaser command is about to be written to the UNIX SHELL to delineate the end of command response for the SHELL output task. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
An attempt to write a chaser to the UNIX SHELL failed. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
Check the &SYS.UNIX.RETCODE and &SYS.UNIX.RETVAL system variables returned to the calling program in SOLVE.
Reason:
A response from issuing a command to the UNIX SHELL has been queued to the distribution task. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
An exit command is about to be issued to the UNIX SHELL to have it terminate. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The SHELL has terminated normally. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The STDIN task is waiting for the output subtask to terminate. This message is issued only if a trace of module flow is requested.
System Action:
The STDIN task waits for the output subtask's termination ECB to be posted.
User Action:
None.
Reason:
The output subtask has been detached as part of the STDIN subtask termination. This message is issued only if a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The STDIN subtask has terminated. This message is issued only if a trace of module flow is requested.
System Action:
The STDIN subtask exits.
User Action:
None.
Reason:
The output task has been started for a UNIX client. This message is is issued when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task has initialized successfully. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task is about to issue a UNIX SELECT call. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task has buffers queued to it from the distribution thread to be freed. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task is about to read from the UNIX SHELL's STDERR. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task is about to read from the UNIX SHELL's STDOUT. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task is about to close the PIPE from the UNIX SHELL's STDOUT. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task is about to close the PIPE from the UNIX SHELL's STDERR. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task has detected end-of-data from a SHELL command response. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task is about to queue a SHELL command response to the distribution thread. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
The output task is about to terminate. This message is issued only when a trace of module flow is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
This message precedes a dump of a command response buffer when a trace command of responses for the UNIX interface is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
None.
Reason:
P2 was the return code returned to the UNIX interface message distribution manager from an EPS SEND of a command response. This message is issued if a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
If P2 is non-zero, there may be a problem with the EPS connection to the client.
Reason:
This message precedes a dump of a SHELL data buffer when a trace of data for the UNIX interface is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
None.
Reason:
P2 was the return code returned to the UNIX interface message distribution manager from an EPS SEND of SHELL data. This message is issued if a trace of module flow is requested.
P1 is a unique path identifier for this caller.
System Action:
Processing continues.
User Action:
If P2 is non-zero, there may be a problem with the EPS connection to the client.
Reason:
This message is issued as part of the SSI STATUS command. It shows the status of the SSIDB file. The status ( P1 ) is shown as a text string that includes one or more of the following values:
OPEN - The file is open.
CLOSED - The file is closed.
OPEN ERROR - An attempt to open the file failed.
INIT ERROR - The file was opened and found to be empty. An attempt to create an initial control record failed.
STRING SHORTAGES - One or more string shortages have been detected since the file was opened.
System Action:
None.
User Action:
The normal status will be OPEN. For all other status values, review the SSI log for earlier errors regarding DD=SSIDB. Use the SSI SHOW VFS command to display current file details, for example the current number of string shortages.
Reason:
This message is issued as part of the SSI STATUS command. It indicates that one or more requests to access an SSI data set have been suspended due to a record contention problem.
System Action:
None.
User Action:
None.
Reason:
The SSIDB data set is opened during SSI initialization, and a control record is read. The control record indicates that the SSIDB data set is in use on another system name (LPAR). The SSIDB may not be shared between LPARs. The message indicates the system name that last opened the data set ( P1 ).
Note: During normal SSI termination, the control record is updated to clear the system name to allow the data set to be used on another LPAR. This message may occur if the file was not closed when last used on the indicated system name.
System Action:
SSI initialization fails.
User Action:
Do the following to reset the system name in the SSIDB control record:
1. Start the SSI on the indicated system using this data set.
2. Terminate the SSI.
Reason:
During open or close processing of an SSI data set that requires control records to be read or rewritten, an error occured when processing the control record. In the message:
P1 is the record action: GET: the error occurred during file open processing when reading the control record. PUT: the error occurred during file close processing when writing the control record.
P2 is the VSAM return code, in hex.
P3 is the VSAM feedback code, in hex.
P4 is the DD name.
System Action:
If the error occurs at file open, SSI initialization fails.
User Action:
Refer to the VSAM Programming manual to determine the meaning of the feedback from the message and the appropriate course of corrective action.
Reason:
This message is issued as part of the SSI STATUS command. It indicates that the SSIDB dataset has not yet been opened.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the SSI STATUS command. It indicates that the SSIDB dataset is not in use in the NMSSI configuration.
System Action:
None.
User Action:
None.
Reason:
This is the heading line for the SSI SHOW VFS command. It is followed by detail lines (NSDC02), one for each data set. Refer to NSDC02 for a description of the fields displayed.
System Action:
None.
User Action:
None.
Reason:
This is the detail line for the SSI SHOW VFS command and shows the details for a single file. The fields, which match the column headings in message NSDC01, are:
P1 - the DD name
P2 - the key length
P3 - the maximum record size
P4 - the number of VSAM strings
P5 - the number of VSAM data buffers
P6 - the number of VSAM index buffers
P7 - the number of times that a VSAM string shortage has occurred
P8 - the VSAM open error code, in hex
P9 - file status flags, in hex (Internal use only)
P10 - the VSAM system time stamp (Internal use only)
System Action:
None.
User Action:
None.
Reason:
This message indicates that one or more VSAM string shortages has occurred for the indicated DD name ( P1 ).
System Action:
Processing is suspended for that request until sufficient resources are available.
User Action:
The SSI SHOW VFS command can be used to determine the total number of string shortages that have occurred. A large number indicates that system tuning is required to avoid significantly impacting performance. Contact your product supplier.
Reason:
During processing of the VSAM file, a VSAM macro return code indicated a physical error had occurred. The message provides the corresponding RPL feedback code ( P1 in hex), and DD name ( P2 ).
System Action:
The file processing request fails.
User Action:
Refer to the VSAM Programming manual to determine the meaning of the feedback from the message and the appropriate course of corrective action.
Reason:
This message is issued as a result of a physical I/O error on a VSAM data set on an MVS (or equivalent) system. It will be preceded by message NSDV04. The information contained in the message is as returned by VSAM ( P1 ) in the form: yyddd,hhmmssth,rbaaddr ,d-or-i,volser,jobname ,j
System Action:
The file I/O request fails.
User Action:
Refer to message NSDV04.
Reason:
When opening a VSAM file, the open was successful but one or more warning messages were issued by VSAM. The feedback code ( P1 in hex), and DD name ( P2 ) are shown.
System Action:
Processing continues.
User Action:
Refer to the VSAM Programming manual to determine the meaning of the feedback from the message and the appropriate course of corrective action.
Reason:
When opening a VSAM file, the open was unsuccessful. The feedback code ( P1 in hex), and DD name ( P2 ) are shown.
System Action:
The file processing request fails.
User Action:
Refer to the VSAM Programming manual to determine the meaning of the feedback from the message and the appropriate course of corrective action.
Reason:
If a system VSAM file is opened and found to be empty, an initial control record is created and written to the file. The attempt to write the record was unsuccessful. The feedback code ( P1 in hex), and DD name ( P2 ) are shown.
System Action:
The file processing request fails.
User Action:
Refer to the VSAM Programming manual to determine the meaning of the feedback from the message and the appropriate course of corrective action.
Reason:
At attempt to read ( P1 =GET) or write ( P1 =PUT) a control record to or from a system VSAM file was unsuccessful. The feedback code ( P2 in hex) and DD name ( P3 ) are shown.
System Action:
The file processing request fails.
User Action:
Refer to the VSAM Programming manual to determine the meaning of the feedback from the message and the appropriate course of corrective action.
Reason:
A system VSAM file was successfully opened but a file attribute is inconsistant with the file's requirements. The DD name ( P1 ) and reason ( P2 ) are shown. Possible reasons are:
INVALID KEYLENGTH - The VSAM cluster is defined with an incorrect key length.
INVALID RELATIVE KEY POSITION - The VSAM cluster is defined with a non-zero relative key position.
INVALID MAXIMUM RECORD LENGTH - The VSAM cluster is defined with a maximum record length that is too large.
System Action:
The file processing request fails.
User Action:
Refer to the VSAM Programming manual to determine the meaning of the feedback from the message and the appropriate course of corrective action.
Reason:
The OML SMFWRITE verb was called with OPT=TEST, or the SMFTRACE system parameter was set to YES. The message indicates that user security check will fail if the call is not made in TEST mode, and the record will not be written to SMF in normal operation.
Security check can fail for one of the following reasons:
Security exit is not installed
Security exit is installed but does not grant permission to the user
System Action:
The SMF record is dumped to the activity log.
User Action:
If you want to write SMF records from the same environment by the same user and the security exit (NCLEX01) is not installed, install it. Otherwise, change the user authorization or move the procedure to the background system.
Reason:
A SOLVE SSI region is configured with the SNA Network Management Interface (SNANMI) feature; however, initialization of the region failed.
The failure reason (P1) is shown:
Indicates that the SNA Network Management Interface feature is not supported by the current operating system or release level. This feature requires z/OS V1R5 or a later release.
Indicates that the SNA Network Management Interface feature is active in another SOLVE SSI region on this LPAR. You can configure only one SOLVE SSI region per LPAR with this feature.
System Action:
The SSI terminates.
User Action:
Amend the appropriate SOLVE SSI parameter member to remove the SNANMI SSI parameter. This parameter enables the SNA Network Management Interface feature.
Reason:
This message is issued during initialization of the SOLVE SSI region and as part of the SSI STATUS display. It provides information about the SNA Network Management Interface (SNANMI) feature. This message indicates that the feature is active and operational in the SOLVE SSI region.
P1 is the name of the SSI endpoint used for the SNANMI feature.
System Action:
None.
User Action:
None.
Reason:
An attempt to register an SSI endpoint to provide an interface to the SNA Network Management Interface (SNANMI) feature failed.
P1 is SSI EndPoint Services (EPS) return code.
P2 is the name of the SSI endpoint used for the API.
System Action:
The SNA Network Management Interface feature is unavailable.
User Action:
This is an internal error. Contact Technical Support.
Reason:
This message is part of the SSI STATUS display and provides information about the SNA Network Management Interface (SNANMI) feature. The message shows the total number ( P1 ) of active Endpoint Services (EPS) requests from all CA NetMaster regions and the status ( P2 ) of the SNANMI subtask.
Possible SNANMI subtask status values and their meanings:
STARTED The SSI SNANMI facility is enabled and has successfully connected to the VTAM SNAMGMT server.
STARTING The subtask is in the process of connecting to the VTAM SNAMGMT server.
ATTACH-ERROR The subtask could not be attached.
INIT-ERROR The subtask failed to successfully initialize.
STOPPING The subtask has been posted to terminate.
STOPPED The subtask has ended.
System Action:
None.
User Action:
Investigate the status, as follows.
STARTED No action required, subtask is successfully connected.
STARTING Wait for a short time, then check the status again.
ATTACH-ERROR The subtask could not be attached.
This usually indicates an install/implementation error (for example, the subtask load module is not in the load library) or region error (for example, there is insufficient virtual storage in the NetMaster SSI (NMSSI) NetMaster SSI (NMSSI) region).
Look for more error messages on the NMSSI log, NMSSI joblog, and z/OS syslog.
INIT-ERROR The subtask failed to successfully initialize.
This usually indicates a configuration error (for example, the NMSSI region is not authorized to create a socket; the VTAMSNAMGMT server is not started; the NMSSI region is not authorized to connect to the VTAM SNAMGMT server).
Use command D NET,VTAMOPTS,OPTION=SNAMGMT to display the SNAMGMT server status.
Authorization problems occur if the OMVS segment for the VTAM or NMSSI tasks is not correctly set up.
Look for more error messages on the NMSSI log, NMSSI joblog, and z/OS syslog. Errors related to OMVS authority for VTAM will appear on the joblog of the VTAM (NET) task.
See the Install Guide for the OMVS authorization steps.
STOPPING The subtask has been posted to terminate.
Either the NMSSI region is shutting down, or an SSI command to reconnect to the VTAM SNAMGMT server was issued and the subtask is being stopped and restarted.
STOPPED The subtask has ended.
Either the NMSSI region is shutting down or the subtask ended unexpectedly (for example ABEND). In the latter case the subtask is reattached after a short delay
(60 seconds).
For an abend, look for more error messages on the NMSSI log, NMSSI joblog, and z/OS syslog.
Reason:
This message precedes a dump of an SNA Network Management Interface (SNANMI) Endpoint Services (EPS) request buffer when tracing of SNANMI EPS requests and responses is enabled.
P1 is the EPS connection identifier.
P2 is the CA NetMaster region identifier.
P3 is the EPS function name.
P4 is the EPS connection correlator.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of a SNA Network Management Interface (SNANMI) Endpoint Services (EPS) response buffer when tracing of SNANMI EPS requests and responses is enabled.
P1 is the EPS connection identifier.
P2 is the CA NetMaster region identifier.
P3 is the EPS function name.
System Action:
None.
User Action:
None.
Reason:
This message contains a hexadecimal and character dump of an SNA Network Management Interface (SNANMI) Endpoint Services (EPS) request or response buffer. The message is written when tracing of server requests and responses is enabled.
System Action:
None.
User Action:
None.
Reason:
Requests queued to the SOLVE SSI SNA Network Management Interface (SNANMI) subtask are not being serviced in a timely manner. The subtask may be stalled.
P1 is the number of stalled requests detected.
System Action:
The SOLVE SSI region continues to monitor the SNANMI subtask.
This message is written approximately every 60 seconds until stalled requests are not detected.
User Action:
Ensure that the dispatching priority of the SOLVE SSI region allows subtasks in the region to be dispatched when ready.
Ensure that the VTAM SNAMGMT server is functioning properly.
If the problem persists, contact Technical Support.
Reason:
The SNA Network Management Interface (SNANMI) feature is active in the SOLVE SSI region; the region is connected to the VTAM SNAMGMT server.
P1 is the VTAM SNAMGMT server release level.
P2 is the VTAM SNAMGMT server functions supported flags.
System Action:
None.
User Action:
None.
Reason:
The SNA Network Management Interface (SNANMI) feature is active in the SOLVE SSI region. The region attempted to attach a subtask under which a connection to the VTAM SNAMGMT server cannot be made. The subtask attach failed.
System Action:
The operation is retried every 60 seconds.
User Action:
See the SSI log for other messages that describe the cause of the subtask attach error.
Reason:
The SNA Network Management Interface (SNANMI) feature is active in the SOLVE SSI region. The region attached a subtask under which a connection to the VTAM SNAMGMT server cannot be made. The subtask initialization failed.
P1 is the subtask return code.
P2 is the subtask error code and is one of the following values:
00-The subtask abended.
04-The subtask engine cannot be initialized.
08-The subtask invoked a UNIX System Services (USS) callable service and the service returned an error.
12-The subtask made a request to the VTAM SNAMGMT server and the server returned an error.
16-Insufficient virtual storage is available in the SOLVE SSI region.
P3 is the subtask error subcode.
System Action:
For USS callable service errors and VTAM SNAMGMT server errors, other messages are written to the SSI log that provides more information about the error.
The operation is retried every 60 seconds.
User Action:
See the SSI log for other messages that describe the cause of the subtask initialization error.
Reason:
The SNA Network Management Interface (SNANMI) feature is active in the SOLVE SSI region. The region attached a subtask under which a connection to the VTAM SNAMGMT server cannot be made. The subtask terminated.
P1 is the subtask return code.
P2 is the subtask error code and is one of the following values:
00-It is an expected termination (for example, the SOLVE SSI region is stopping) or the subtask abended.
04-The subtask engine cannot be initialized.
08-The subtask invoked a UNIX System Services (USS) callable service and the service returned an error.
12-The subtask made a request to the VTAM SNAMGMT server and the server returned an error.
16-Insufficient virtual storage is available in the SOLVE SSI region. P3 is the subtask error subcode.
System Action:
For USS callable service errors and VTAM SNAMGMT server errors, other messages are written to the SSI log that provides more information about the error.
If it is an expected termination (for example, the SOLVE SSI region is stopping), no action is taken; otherwise, the SOLVE SSI region waits 60 seconds and then reattaches the subtask.
User Action:
See the SSI log for other messages that describe the cause of an unexpected subtask termination.
Reason:
The SNA Network Management Interface (SNANMI) feature is active in the SOLVE SSI region. The region attached a subtask under which a connection to the VTAM SNAMGMT server cannot be made.
The subtask invoked a UNIX System Services (USS) callable service and the service returned an error.
P1 is the USS callable service name.
P2 is the USS callable service return value.
P3 is the USS callable service return code.
P4 is the USS callable service reason code.
System Action:
The SOLVE SSI region waits 60 seconds and then reattaches the subtask.
User Action:
For more information about the error, see the z/OS publication UNIX System Services Messages and Codes.
Reason:
The SNA Network Management Interface (SNANMI) feature is active in the SOLVE SSI region. The region attached a subtask under which a connection to the VTAM SNAMGMT server cannot be made.
The subtask invoked the BPX1CON UNIX System Services (USS) callable service to connect to the VTAM SNAMGMT server and the service returned an error that indicates that the VTAM SNAMGMT server is not started.
P1 is the BPX1CON USS callable service return value.
P2 is the BPX1CON USS callable service return code.
P3 is the BPX1CON USS callable service reason code.
System Action:
The operation is retried every 60 seconds.
User Action:
Use the MODIFY VTAMOPTS command to start the VTAM SNAMGMT server.
For more information about the SNAMGMT VTAM start option, see the z/OS publication Communications Server SNA Resource Definition Reference.
Reason:
The SNA Network Management Interface (SNANMI) feature is active in the SOLVE SSI region. The region attached a subtask under which a connection to the VTAM SNAMGMT server cannot be made.
VTAM terminated the SOLVE SSI region connection to the VTAM SNAMGMT server.
P1 is the VTAM SNAMGMT server termination return code (Errno value). P2 is the VTAM SNAMGMT server termination reason code (ErrnoJr value).
System Action:
The operation is retried every 60 seconds.
User Action:
For more information about the termination return and reason codes, see the z/OS publication Communications Server IP and SNA Codes.
Reason:
This message precedes a dump of an SNA Network Management Interface (SNANMI) VTAM SNAMGMT server request buffer when a trace of the SNANMI VTAM SNAMGMT server requests and responses is enabled.
P1 is the address of the VTAM SNAMGMT request buffer.
P2 is the length of the VTAM SNAMGMT request buffer.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of an SNA Network Management Interface (SNANMI) VTAM SNAMGMT server response buffer when a trace of the SNANMI VTAM SNAMGMT server requests and responses is enabled.
P1 is the address of the VTAM SNAMGMT response buffer.
P2 is the length of the VTAM SNAMGMT response buffer.
System Action:
None.
User Action:
None.
Reason:
This message precedes a dump of an SNA Network Management Interface (SNANMI) VTAM SNAMGMT server record buffer when a trace of the SNANMI VTAM SNAMGMT server requests and responses is enabled.
P1 is the address of the VTAM SNAMGMT record buffer.
P2 is the length of the VTAM SNAMGMT record buffer.
System Action:
None.
User Action:
None.
Reason:
This message contains a hexadecimal and character dump of an SNA Network Management Interface (SNANMI) VTAM SNAMGMT server request or response buffer. The message is written when tracing of server requests and responses is enabled.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the NMSAF security exit has failed NetMaster user logon. The indicated user ID is unknown to NetMaster and no modelling could be performed.
The user ID is known to the external security system.
System Action:
The NetMaster logon fails.
User Action:
Log on using a valid user ID.
Reason:
This message indicates that the NMSAF security exit has failed NetMaster user logon. A shortage of storage prevented the exit from obtaining required control blocks.
System Action:
The NetMaster logon fails.
User Action:
Allow the NetMaster region to obtain more storage.
Reason:
This message indicates that the NMSAF security exit has failed NetMaster user logon. The logon request was from TSO (using the NMLOGON TSO command).
The NMSAF exit parameter file has disabled auto-logon from TSO. A user ID and password must be provided.
System Action:
The NetMaster logon fails. The normal NetMaster logon panel is presented (this message is displayed there). Enter a user ID and password on this panel.
User Action:
Log on with a valid user ID and password.
Reason:
This message indicates that the NMSAF security exit has failed CA NetMaster user logon. The logon request was from ROF (the Remote Operator Facility) using the SIGNON command or an implied signon caused by use of the ROUTE command.
The target CA NetMaster is using the NMSAF security exit, and the initialization parameter file has set an option that requires ROF logons to supply a password.
System Action:
The ROF logon to CA NetMaster fails.
User Action:
Use the SIGNON command with the PASSWORD=password operand to sign on to the target CA NetMaster.
Note: The PASSWORD operand of the SIGNON command is not echoed to the panel or the CA NetMaster log.
Reason:
This message indicates that the NMSAF security exit has failed NetMaster user logon. The source of the logon request is not supported by the NMSAF exit.
Unsupported types include NetView CONNECT.
System Action:
The logon to NetMaster fails.
User Action:
This message is unlikely to appear unless you are using an unsupported NetMaster feature. Thus there is no specific user action.
If this message does occur, contact Technical Support.
Reason:
This message indicates that the NMSAF security exit has prevented use of the Password Change function.
The NMSAF initialization file contained a parameter that has disabled password change.
The NetMaster administrator has made this decision.
System Action:
The attempt to change a password fails.
User Action:
Contact your NetMaster administrator to determine why password change is not supported.
Possible reasons include:
- The external security system cannot handle password changes from NetMaster. - A password change on this MVS system may not propagate to other MVS systems.
Reason:
This message indicates that the NMSAF security exit has encountered an unexpected SAF (RACROUTE) error.
The RACROUTE macro SAF return code (aa), RACF return code (bb), and RACF reason code (cc) are displayed.
System Action:
The current NMSAF exit request fails. Requests include user logon, password change, and so on.
User Action:
Contact Technical Support with the following information:
- The request being attempted (logon, logoff, password change, and so on)
- The text of this message
- whether the problem is transient or permanent
It may also be helpful to restart NetMaster with NMSAF tracing enabled. This will help pinpoint the problem.
Reason:
This message indicates that the NMSAF security exit has been asked to verify a user but the user ID is not known to the external security system.
System Action:
The logon request fails.
User Action:
Retry the logon request with a valid user ID.
Reason:
This message indicates that the NMSAF security exit has been asked to verify a user, but the user ID has had all access revoked by the security administrator.
System Action:
The logon request fails.
User Action:
Contact your security administrator.
Reason:
This message indicates that the NMSAF security exit has been asked to verify a user, and the user ID's password has expired.
System Action:
The logon request is accepted, and a password change panel is presented.
If password change has been disabled by the NetMaster administrator, the logon request is rejected.
User Action:
If the password change panel is presented, change your password.
If password change has been inhibited, you will need to change your password using other facilities and attempt to log on to NetMaster again.
Reason:
This message indicates that the NMSAF security exit has been asked to verify a user, and the user ID's password is not correct.
This could be a logon request or a password change request, in which case the supplied current password is not correct.
System Action:
The logon or password change request fails.
User Action:
Retry the request with the correct password.
Reason:
This message indicates that the NMSAF security exit has been asked to change a password for a user.
The supplied new password is invalid
System Action:
The password change request fails.
User Action:
Retry the password change request with the correct password.
The new password may be invalid due to installation restrictions.
Reason:
This message indicates that an &SECCALL CALL request to the NMSAF security exit failed due to a missing or invalid first parameter.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure and retry.
Reason:
This message indicates that an &SECCALL CALL request to the NMSAF security exit failed due to an unrecognized first parameter.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure and retry.
Reason:
This message indicates that an &SECCALL CALL request to the NMSAF security exit failed.
The supplied parameter (request code) was recognized, but is not supported by this version of the NMSAF exit.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure and retry.
Reason:
This message indicates that the NMAF security exit was unable to initialize due to a shortage of storage.
System Action:
NetMaster will terminate.
User Action:
Provide a larger below-the-line region size for NetMaster.
Reason:
This message indicates that the NMSAF security exit was unable to initialize because the NetMaster version is prior to V5.0.
System Action:
NetMaster will terminate.
User Action:
Do not attempt to use the NMSAF security exit with earlier versions of NetMaster.
Reason:
This message indicates that the NMAF security exit was unable to initialize because of errors in the SXCTL input parameter file.
This message will be preceded by other messages detailing the errors.
System Action:
NetMaster will terminate.
User Action:
Correct the SXCTL file parameters.
Reason:
This message indicates that the NMSAF security exit was unable to initialize because the NetMaster region is not APF-authorized.
System Action:
NetMaster will terminate.
User Action:
Ensure the NetMaster load libraries are all APF authorized.
Also ensure any other load libraries in the STEPLIB concatenation are also APF authorized.
Reason:
This message indicates that the NMAF security exit was unable to initialize because the level of SAF (System Authorisation Facility) is not at least 1.9.
System Action:
NetMaster will terminate.
User Action:
Verify the level of SAF support in MVS.
MVS (RACF) SAF 1.9 or later has been in use since at least 1991.
Reason:
This message indicates that the NMAF security exit was unable to initialize because the a RACROUTE TOKENEXTR request failed.
System Action:
NetMaster will terminate.
User Action:
This message should not occur. However, non-IBM security systems may not correctly support the RACROUTE TOKENEXTR request.
Restart NetMaster. If the problem persists, add the following parameters to the SXCTL file:
TRACE=YES TRACESAF=YES
Also add an SXTRACE DD statement to the NetMaster JCL.
Send the diagnostic output from the trace to Technical Support. You should also provide details about the security product that you are using.
Reason:
This message indicates that the NMSAF security exit has detected an internal error.
This message displays the error code and is followed by additional diagnostic messages.
The exit then ABENDs, and NetMaster also ABENDs with a NetMaster internal abend code 268-01.
System Action:
After writing additional diagnostic messages, the security exit ABENDs, and NetMaster also ABENDs with an internal abend code 268-01.
User Action:
Contact Technical Support.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
Refer to message NSX290.
User Action:
Refer to message NSX290.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
Refer to message NSX290.
User Action:
Refer to message NSX290.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
Refer to message NSX290.
User Action:
Refer to message NSX290.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated value is not recognised as a valid parameter.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter requires a NO or YES as the value.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid. This parameter requires a valid name. A valid name is a 1-8 character value, the first character being alphabetic or national (@,#,$) and the remainder being alphanumeric or national.
A null value (meaning 'omitted') can be indicated by using a value of a single dash (-). This is the only otherwise invalid value permitted.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid. This parameter requires a valid user name. A valid user name is a 1-8 character value with all characters being alphanumeric or national (@,#,$).
A null value (meaning 'omitted') can be indicated by using a value of a single dash (-). This is the only otherwise invalid value permitted.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid. This parameter requires a valid resource. A resource name is a 1-20 character value. The exact syntax of this value is set by the security system.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid. This parameter requires a valid model. A model name has the same syntax as a name. Refer to message NSX383 for the rules.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The number of entries in the MODELGROUP list has been exceeded.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Reduce the number of MODELGROUP entries.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
An ABEND occured when opening the SXCTL file.
System Action:
NetMaster terminates.
User Action:
Examine other JOBLIG message for the ABEND messages and correct the problem.
Restart NetMaster.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
An I/O error occurred while reading the SXCTL file.
System Action:
NetMaster terminates.
User Action:
Ensure the SXCTL file is valid and accessible.
Reason:
The NMSAF security exit has failed user logon. The indicated user ID is unknown to the region, and no modeling could be performed.
The user ID is known to the external security system.
System Action:
The logon fails.
User Action:
Log on using a valid user ID.
Reason:
The NMSAF security exit has failed user logon. A shortage of storage prevented the exit from obtaining the required control blocks.
System Action:
The logon fails.
User Action:
Allow the NetMaster region to obtain more storage.
Reason:
The NMSAF security exit has failed user logon. The logon request was from TSO (using the NMLOGON TSO command).
The NMSAF exit parameter file has disabled auto-logon from TSO. A user ID and password must be provided.
System Action:
The logon fails. A logon panel is presented.
User Action:
Log on with a valid user ID and password.
Reason:
The NMSAF security exit has failed user logon. The logon request was from ROF (Remote Operator Facility) using the SIGNON command or an implied signon caused by use of the ROUTE command.
The target region is using the NMSAF security exit, and the initialization parameter file has set an option that requires ROF logons to supply a password.
System Action:
The ROF logon to the region fails.
User Action:
Use the SIGNON command with the PASSWORD=password operand to sign on to the target region.
Note: The PASSWORD operand of the SIGNON command is not echoed to the panel or the activity log.
Reason:
The NMSAF security exit has failed user logon. The source of the logon request is not supported by the NMSAF exit.
Unsupported types include NetView CONNECT.
Note: This message can appear if you are using an unsupported feature.
System Action:
The logon to the region fails.
User Action:
For assistance, contact Technical Support at HYPERLINK "http://ca.com/support" http://ca.com/support.
Reason:
The NMSAF security exit has prevented the use of the Password Change function.
The NMSAF initialization file contained a parameter that has disabled password change.
System Action:
The attempt to change a password fails.
User Action:
Contact your region administrator to determine why password change is disabled.
The following reasons are possible:
The external security system cannot handle password changes from the region.
A password change on this MVS system may not propagate to other MVS systems.
Reason:
The NMSAF security exit has encountered an unexpected SAF (RACROUTE) error.
The RACROUTE macro SAF return code (aa), RACF return code (bb), and RACF reason code (cc) are displayed.
System Action:
The NMSAF exit request fails. Requests include user logon, password change, and so on.
User Action:
For assistance, contact Technical Support with the following information:
The request being attempted (logon, logoff, password change, and so on)
The text of this message
Whether the problem is transient or permanent
Restarting the region with NMSAF tracing enabled can help to pinpoint the problem.
Reason:
The NMSAF security exit has been asked to verify a user whose ID is not known to the external security system.
System Action:
The logon request fails.
User Action:
Retry the logon request with a valid user ID.
Reason:
The NMSAF security exit has been asked to verify a user, but the security administrator has revoked all access for the user ID.
System Action:
The logon request fails.
User Action:
Contact your security administrator.
Reason:
The NMSAF security exit has been asked to verify a user, but the password specified with the user ID has expired.
System Action:
The logon request is accepted, and a password change panel is presented.
If password change has been disabled by the region administrator, the logon request is rejected.
User Action:
If the password change panel is presented, change your password.
If password change is disabled, you have to change your password using other facilities and attempt to log on to the region again.
Reason:
The NMSAF security exit has been asked to verify a user, but the password specified with the user ID is not correct.
This could be a logon request or a password change request, in which the specified current password is not correct.
System Action:
The logon or password change request fails.
User Action:
Retry the request with the correct password.
Reason:
The NMSAF security exit has been asked to change a password for a user.
The supplied new password is invalid.
System Action:
The password change request fails.
User Action:
The new password may be invalid due to site restrictions.
Retry the password change request with a correct password.
Reason:
An &SECCALL CALL request to the NMSAF security exit failed due to a missing or invalid first parameter.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure, and retry.
Reason:
An &SECCALL CALL request to the NMSAF security exit failed due to an unrecognized first parameter.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure, and retry.
Reason:
An &SECCALL CALL request to the NMSAF security exit failed.
The supplied parameter (request code) was recognized but is not supported by this version of the exit.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure, and retry.
Reason:
An &SECCALL CALL request to the NMSAF security exit failed.
The supplied parameter (request code) was recognized but is not supported by this version of the exit.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure, and retry.
Reason:
The NMAF security exit cannot initialize due to a shortage of storage.
System Action:
The region terminates.
User Action:
Provide a larger below-the-line region size for the region.
Reason:
The NMSAF security exit cannot initialize because the NetMaster version is prior to V5.0.
System Action:
The region terminates.
User Action:
Do not attempt to use the NMSAF security exit with earlier versions of NetMaster.
Reason:
The NMAF security exit cannot initialize because of errors in the SXCTL input parameter file.
This message is preceded by other messages detailing the errors.
System Action:
The region terminates.
User Action:
Correct the SXCTL parameters.
Reason:
The NMSAF security exit cannot initialize because the region is not APF-authorized.
System Action:
The region terminates.
User Action:
Ensure that the following load libraries are APF-authorized:
NetMaster load libraries
Other load libraries in the STEPLIB concatenation
Reason:
The NMSAF security exit cannot initialize because the level of SAF (system authorization facility) is earlier than 1.9.
System Action:
The region terminates.
User Action:
Verify the level of SAF support.
Reason:
The NMSAF security exit cannot initialize because a RACROUTE TOKENEXTR request failed.
This message should not occur. However, non-IBM security systems may not support the RACROUTE TOKENEXTR request correctly.
System Action:
The region terminates.
User Action:
Restart the region. If the problem persists, add the following parameters to the SXCTL file:
TRACE=YES
TRACESAF=YES
Also, add an SXTRACE DD statement to the region JCL job.
Contact Technical Support with the diagnostic output from the trace and details about the security product you are using.
Reason:
The NMSAF security exit has an internal error.
This message displays the error code and is followed by additional diagnostic messages.
System Action:
After writing additional diagnostic messages, the security exit abends. The region also abends with an internal ABEND code 268-01.
User Action:
For assistance, contact Technical Support at HYPERLINK "http://ca.com/support" http://ca.com/support.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
See the NSX290 message.
User Action:
See the NSX290 message.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
See the NSX290 message.
User Action:
See the NSX290 message.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
See the NSX290 message.
User Action:
See the NSX290 message.
Reason:
This message indicates that an inbound File Transfer request is waiting for exclusive use of a dataset.
The name of the dataset is indicated in a following NSXA02 message.
System Action:
The File Transmission Request will wait until the dataset is available.
User Action:
Determine the cause of the dataset contention.
Reason:
This message follows an NSXA01 or NSXA03 message, and indicates the name of the dataset referred to in those messages
System Action:
See Messages NSXA01 and NSXA03.
User Action:
See Messages NSXA01 and NSXA03.
Reason:
This message indicates that an inbound File Transfer request that was preveiously waiting for exclusive control of a dataset can now continue.
The name of the dataset is indicated in a following NSXA02 message.
System Action:
The File Transmission Request continues.
User Action:
None.
Reason:
The NMSECDSN exit detects an unsupported version of NetMaster.
This exit cannot be used with versions prior to NetMaster Version 7.0.
System Action:
The ALLOCATE request will fail unconditionally.
User Action:
Do not use the NMSECDSN exit with an incorrect version of NetMaster.
Reason:
This message is produced by the NMSECDSN exit during processing of an ALLOCATE command when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSN exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The ALLOCATE command fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSN exit during processing of an ALLOCATE command when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSN exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The ALLOCATE command fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSN exit during processing of an ALLOCATE command when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSN exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The ALLOCATE command fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSS exit during processing of a request when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSS exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
THe Dataset Services request fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSS exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The Dataset Services request fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSS exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The Dataset Services request fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSS exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The Dataset Services request fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request. The current user's SAF user ID and the pre-registered HFS user ID do not match.
This can only occur for NetMaster background user IDs when the security exit has nominated a different SAF user ID, and the SYSPARM HFSUSEC=YES is in effect. (SYSPARMS HFSUSEC=YES causes NetMaster to internally register the NetMaster user ID as the HFS user ID).
System Action:
The Dataset Services request fails unconditionally.
User Action:
Do not use SYSPARMS HFSUSEC=YES with the NMSECDSS and SEC=NMSAF exits.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request. An attempt to perform HFS security initialization failed. The BPX1SEC system call return and reason codes are displayed.
These codes can be found in the Unix System Services Messages and Codes manual.
System Action:
The Dataset Services request fails unconditionally.
User Action:
Examine the return and reason codes to determine the cause of the failure.