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.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|