z/OS MVS System Codes
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


0AF

z/OS MVS System Codes
SA38-0665-00

0AF

Explanation

The Time Sharing Option Extensions (TSO/E) interactive data transmission facility detected a system error during the processing of a TRANSMIT or RECEIVE command. Register 15 contains a reason code:
Code
Explanation
0025
The RECEIVE command encountered an error while invoking the Job Entry Subsystem (JES) interface.

The RECEIVE command was issued to determine if any Interactive Data Transmission Facility files were available for you to receive. The JES subsystem request was not successful. Reason code 0025 is associated with message INMR037I.

002A
The TRANSMIT command attempted to allocate the SYSPRINT message file for IEBCOPY using SVC 99, and the allocation failed. The SYSPRINT message file is usually allocated to either the terminal or to a SYSOUT class. You can specify where you want it to be allocated in either in CSECT INMXPARM or on the TRANSEC keyword of parmlib member IKJTSO00. Reason code 002A is associated with messages INMX040I and INMX042I.
0043
The TRANSMIT command was issued with the DATASET or DSNAME keyword and the OBTAIN SVC was issued to get information about the data set. The OBTAIN SVC set a return code other than 0 (successful termination), 8 (data set not on volume), or 12 (VTOC I/O error). Reason code 0043 is associated with message INMX067I.
0053
The TRANSMIT command attempted to OPEN a data set previously written by the IEBCOPY utility or the AMS REPRO command. The OPEN failed. The data set is a temporary data set the TRANSMIT command allocates to contain intermediate data. Normally, the TRANSMIT command reads, transmits, and deletes the temporary data set. Reason code 0053 is associated with message INMX083I.
007F
The RECEIVE command attempted to allocate a spool file and the allocation failed. The RECEIVE command obtained the name of the spool file from JES. Reason code X'007F' is associated with message INMR127I.
0084
The RECEIVE command was issued with the INDATASET or INDSNAME keyword.

The data set specified with the keyword failed to OPEN. The data set was allocated successfully. Reason code 0084 is associated with message INMR132I.

0085
The RECEIVE command attempted to OPEN a file for incoming network files from the JES spool, but the OPEN failed. The process sysout subsystem interface successfully selected a name for the spool file and the dynamic allocation SVC successfully allocated the spool file. Reason code 0085 is associated with message INMR133I.
0086
The RECEIVE command attempted to deallocate a data set using SVC 99, and the unallocation failed. The data set was a JES input file or was specified by an INDATASET or INDSNAME keyword. Reason code 0086 is associated with message INMR134I.
0089
The RECEIVE command encountered an error while attempting to end the external writer interface with JES. After all files have been processed or after a unrecoverable error, the RECEIVE command invokes the process sysout subsystem interface, specifying that this is the final call to the subsystem interface. The subsystem returned a nonzero return code indicating an error. Reason code 0089 is associated with message INMR137I.
009C
The TRANSMIT or RECEIVE command processor received an unknown return code from the module IKJSMS1. The reason code 009C is associated with message INMC156I.
00CC
The TRANSMIT command processor encountered an error while opening the JES output file. Reason code 00CC is associated with message INMX204I.
00D2
The TRANSMIT command processor encountered an error while opening the output data set. Reason code 00D2 is associated with message INMX210I.

System action

The system issues one of the following messages: INMC156I, INMR037I, INMX067I, INMX083I, INMR127I, INMR132I, INMR133I, INMR134I, INMR137I, INMX040I, INMX042I, INMX204I, INMX210I.

The system issues an SVC dump.

System programmer response

If the problem recurs and if the program is not in error, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide the SVC dump and hardcopy of the TSO session if possible.

Source

Time Sharing Option Extensions (TSO/E)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014