|
|
|
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:
A SHOW EPS command has been entered and the connection to the SSI P1 is not active.
System Action:
This message is produced instead of the SHOW EPS output.
User Action:
Determine why the required SSI, P1, is not active. If necessary restart the SSI region or change the /PARMS SSI setting to the correct SSID name.
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:
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:
This message is sent to the Packet Analyzer NMSSI region if an apparent stall in Packet Analyzer processing is detected.
The message will appear at intervals of approximately 1 minute when a problem is detected.
An individual request is allowed 30 seconds elapsed time before it is regarded as 'stalled'.
The fields in the message are:
aaa is the current number of requests that have been send to the Packet Analyzer subtask for processing.
bbb is the current number of requests that appear to have 'stalled' (because they have taken too long to process).
ccc is the total number of stalled requests that have been detected since this message was last issued.
System Action:
The Packet Analyzer continues execution.
User Action:
This is an internal error. Contact Technical Support.
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:
This message is logged during region startup, if the IBM health checker interface cannot be initialized. A descriptive reason is included in the message as shown in the following table:
|
code |
desc |
|
1 |
REGION IS NOT APF AUTHORISED |
System Action:
The IBM health checker interface is not activated.
User Action:
Contact your support representative.
Reason:
This message is issued as part of the response to a STATUS command and provides the status of the IBM health checker interface.
It indicates that the health checker interface was successfully installed and is available.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a STATUS command and provides the status of the IBM health checker interface.
It indicates that the health checker interface was not activated, and the reason is shown.
Note: See the online help for message NH0080 for the various reasons.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a STATUS command and indicates that the status of the IBM health checker interface is not known.
System Action:
None.
User Action:
Contact your support representative.
Reason:
This message is issued as part of the response to a STATUS command and shows the status and procedure name of the IBM health checker region, if this information is known.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and indicates that responses follow.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command.
The message indicates the status of this region’s interfaces to the IBM health checker for defining checks and querying checks.
It also shows the number of checks that this region has defined.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and shows the IBM health checker region status and procedure name, if known.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and is the heading message for the following NH0414 messages, which show the list of health checks defined by this region.
The column headings are:
TYP identifies the type of check.
CHECK NAME displays the name of the check.
HANDLER displays the name of the handling program or procedure.
F-CODE displays the function code passed to the handler.
NM-PARM displays the parameter value passed to the handler.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and is the detail line for the list of checks defined by this region.
Note: See the online help for message NH0413 for the column descriptions.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and shows that a query request has been scheduled.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and shows that a query request has been completed.
The return information from the request is shown. This information is the result and reason, the R15, R0, and abend code values.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and precedes the display for the HZSQUAA area (if requested).
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and follows the NH0428 message.
It shows the HZSQUAA area in hex and character.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and provides headings for the following NH0431 messages
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and shows the names and values of various fields in the HZSQUAA header.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and provides headings for the following NH0433 messages
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and shows the names and values of various fields in the HZSQUAAG area.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and indicates that a list of health checks follows.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and provides column headings for the following NH0445 messages.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and provides column headings for the following NH0446 messages.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and provides information about a registered health check.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and provides information about a registered health check.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and indicates that a list of lines from a health check follows.
System Action:
None.
User Action:
None.
Reason:
This message is issued as part of the response to a SH HC command and provides one line from a specific health check message buffer.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a successful HC DEFINE command. It indicates that the named health check was defined.
System Action:
The health check will be activated.
User Action:
None.
Reason:
This message is issued in response to a successful HC DELETE command. It indicates that the named health check will be deleted.
System Action:
The health check is deleted.
User Action:
None.
Reason:
This message is issued in response to an HC DELETE command. It indicates that the named health check cannot be deleted, as it was not previously defined.
System Action:
None.
User Action:
Check the name of the check.
Reason:
This message is issued in response to an HC DELETE command. It indicates that the named health check will be deleted shortly.
System Action:
The named health check will be deleted when possible.
User Action:
None.
Reason:
This message is issued in response to an HC command. It indicates that the name of the health check was not valid.
The name must be from 1 to 23 characters in length. It the first 3 char characters are 'NM_', the minimum length is 4. If the first 3 characters are not NM_ the minimum length is 1, and the maximum length is 20. (The system will automatically prefix the name with 'NM_' in this case.)
The name must consist of characters A-Z, 0-9, @, #, $, and _ only.
System Action:
The command is ignored.
User Action:
Correct the check name.
Reason:
This message is issued in response to an HC command. It indicates that the supplied check reason is not valid The supplied check reason must be quoted, and must not be null. It must not be longer than 126 characters.
System Action:
The command is ignored.
User Action:
Correct the check reason.
Reason:
This message is issued in response to an HC command. It indicates that the supplied check interval value is not valid.
An interval value can be in one of these formats:
(The numbers need not have leading zeros.)
If just minutes are entered, it must have a value from 1 to 1440.
If hours and minutes are entered, the hours value must be from 0 to 24, and the minutes value must be from 0 to 59. The resulting value calculated as (hours*60+minutes) must be in the range 1 to 1440.
System Action:
The command is ignored.
User Action:
Correct the interval value.
Reason:
This message is issued in response to an HC command, if a storage shortage prevents processing from continuing.
System Action:
The command is ignored.
User Action:
Notify your support representative.
Reason:
This message is issued in response to an HC DEFINE command. It indicates that the request to define a check was not processed, as the supplied check name already exists.
System Action:
The command is ignored.
User Action:
Correct the name of the check.
Reason:
This message is issued in response to an HC command, if a storage shortage prevents processing from continuing.
System Action:
The command is ignored.
User Action:
Contact your support representative.
Reason:
This message is logged whenever a specific health check is requested.
System Action:
The requested health check procedure is started.
User Action:
None.
Reason:
The NCL process identified by 'pppppp' in the message has completed. It was running a check for the health check named 'cccc' in the message.
The result is as indicated ('rrr'). The possible values are:
N/S indicates that no result was set (this is an error).
OK indicates that the check completed successfully and no problems were detected.
EXCEPT indicates that an exception condition was found.
ERROR indicates that the check encountered an error.
BADPARM indicates that the check found that parameters provided to it were in error.
ENVERROR indicates that the check found that the environment was not suitable.
System Action:
In some cases, the check may be disabled.
User Action:
None.
Reason:
This message is written if execution of a health check procedure had an error. It provides the NCLID of the check process and the name of the health check.
Additional error messages follow.
System Action:
None.
User Action:
None.
Reason:
This message follows an NH2210 message, and indicates that the problem with the check was that no 'result' was set by the check procedure.
System Action:
The health check is disabled.
User Action:
None.
Reason:
This message follows an NH2210 message, and indicates the reason for the error.
A set of required text messages was not provided by the check procedure. The result name, and the text type are indicated in the message.
System Action:
The health check is disabled.
User Action:
None.
Reason:
This message follows the NH2210 message, and indicates that the problem was that no message ID value was set for the messages in the indicated section.
System Action:
The health check is disabled.
User Action:
None.
Reason:
This message follows the NH2210 message, and indicates that the reason for the error is that the check procedure indicated an error, but failed to provide a non-zero diagnostic value.
System Action:
The health check is disabled.
User Action:
None.
Reason:
This message is issued when a health check procedure terminates abnormally. Any information that the procedure set up before terminating is ignored.
System Action:
The health check is disabled.
User Action:
None.
Reason:
This message is issued when a health check procedure fails to complete within a reasonable time.
System Action:
The health check is disabled.
User Action:
None.
Reason:
The HC_UTIL OML verb can only be issued in an HCPROC-type procedure.
System Action:
An error is raised.
User Action:
None.
Reason:
This message is issued if an HC_UTIL DONE OML statement is executed. It indicates that the health check procedure has not set a result.
System Action:
An error is raised.
User Action:
None.
Reason:
This message is issued if an HC_UTIL DONE OML statement is executed. It indicates that the health check procedure has not supplied required text.
System Action:
An error is raised.
User Action:
None.
Reason:
This message is issued if an HC_UTIL DONE OML statement is executed. It indicates that the health check procedure has not set a message ID.
System Action:
An error is raised.
User Action:
None.
Reason:
This message is issued if an HC_UTIL DONE OML statement is executed. It indicates that the health check procedure has not provided a diagnostic value when one is required.
System Action:
An error is raised.
User Action:
None.
Reason:
This message is issued when an HC_UTIL OML statement is executed, and the supplied stem variable name is too long.
System Action:
An error is raised.
User Action:
None.
Reason:
This message is issued if an HC_UTIL OML statement is executed.
It indicates that the variable name generated by concatenating the supplied stem. value and a suffix exceeds the allowed OML variable name length.
System Action:
An error is raised.
User Action:
None.
Reason:
This message is issued during region initialization and indicates that a module used to interface to the IBM Health checker could not be loaded.
System Action:
The IBM Health Checker interface is disabled.
User Action:
Report the error to your support representative.
Reason:
This message is issued during region initialization and indicates that the IBM Health Checker interface encountered a problem during initialization.
The return code and register 0 and 1 values are displayed.
System Action:
The IBM Health Checker interface is disabled.
User Action:
Report the error to your support representative.
Reason:
This message is issued when a new health check has been successfully defined. The assigned correlator is displayed.
The return code and register 0 and 1 values are displayed.
System Action:
The health check will be scheduled when necessary.
User Action:
None.
Reason:
This message is issued when a new health check was not able to be defined. The return code and register 0 and 1 values are displayed.
System Action:
None.
User Action:
Report the error to your local support representative.
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.
| Copyright © 2012 CA. All rights reserved. |
|