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


D23

z/OS MVS System Codes
SA38-0665-00

D23

Explanation

An error occurred in processing for a write to operator (WTO) or write to operator with reply (WTOR).

Register 15 contains a hexadecimal error code in the format xxxxyyyy. The fields in this error code are the following:
xxxx
This halfword is for IBM® internal use only.
yyyy
This halfword is the unique reason code identifier. Only yyyy is listed below.
The following are the yyyy values and their meanings:
Code
Explanation
0002
The caller issued a WTO or WTOR specifying an incorrect number of lines. Possible errors:
  • A WTOR was specified with SYNCH=NO and more than one line was specified
  • A multiple-line WTO with zero lines was specified
  • A WTO or WTOR was specified with SYNCH=YES, and more than 14 lines were specified
0003
The parameter list that the caller passed does not reside in storage that the caller can access.
0004
The caller requested a WTO or WTOR with a text length of zero, or a multiple-line WTO was specified with one of the lines having a text length of zero.
0005
A caller requested a WTO or WTOR with a text length too long for the type of line. The text was truncated to the maximum length for that type of line.
0006
Start of change A caller that was not in key 0-7 requested one or more of the authorized WTO keywords.End of change
0007
The caller requested mutually exclusive functions. Examples:
  • Both CONSID and CONSNAME were specified
  • A multiple-line message requested incompatible or invalid line types for a line
  • A WTOR prefix was specified with a WPX
0008
The caller supplied an incorrect parameter list structure. Here are possible reasons:
  • WPX length was not correct.
  • WQEBLK parameter was specified with an incorrect WPL.
  • Zero address was specified for the WPL.
0009
The caller requested a WTO or WTOR with a zero text address, or a multiple-line WTO was specified with one of its lines having a zero text address.
000B
The caller specified LINKAGE=BRANCH with unsupported keywords.
000C
The caller issued a WTOR with SYNCH=NO and LINKAGE=BRANCH.
000E
This processor does not hold the restart resource.
000F
The system could not access the action code storage.
0010
The system found an incorrect value in the write-to-operator queue element (WQE).
0011
The console name is reserved or incorrect.
yy12
The system was unable to create or expand an SQA cellpool. The return code from the failing STORCSR will be found in yy.
yy20
A GETCELL for an operator reply element (ORE) failed. The return code from the GETCELL macro will be found in yy.
yy21
The system could not build a cellpool for an operator reply element (ORE). The return code from the BLDCPOOL macro will be found in yy.
yy22
The system could not obtain storage for an operator reply element (ORE). The return code from the STORAGE macro will be found in yy.
0030
A write-to-operator queue element (WQE) for an operator reply could not be obtained.
yy40
A recovery environment could not be established. The return code from the ESTAE macro will be found in yy.
yy50
A LOADWAIT request failed. The return code from the BLWLDWT service will be found in yy.
yy51
The system could not obtain needed storage. The return code from the STORAGE macro will be found in yy. When yy equals 00, a WTO multi-line exceeded the maximum 65533 total lines allowed. The WTO multi-line connect was too large.
yy52
A failure occurred in the data block create routine. The return code from the data block routine will be found in yy.
0053
Storage could not be obtained for the dummy SSI control blocks (SSOB, SSWT, WQE, ORE). Processing continues for this message; however, the SSI is not called for this message.
0055
The caller requested a function that requires additional parameters.
0060
Delayed issued WTO subtask timed out.
yy61
Delayed issued WTO subtask could not establish recovery, where yy is the ESTAEX return code.
yy62
Delayed Issued WTO task could not attach a subtask where yy is the ATTACH return code.
0063
The first line of a multi-line message cannot be marked verbose.
Fyyy
An internal processing error occurred. The yyy field contains the abend code of the failure.

System programmer response

Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center.

If the reason code is X'0012', then increase the SQA/ESQA values in IEASYSxx in parmlib.

Programmer response

Correct the program issuing the WTO or WTOR macro. Recompile the program. Run the job step again. If the problem persists, notify the system programmer.

Source

Console services

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014