z/OS


MVS System Codes

SA22-7626-19
z/OS


MVS System Codes

SA22-7626-19
 Note
Before using this information and the product it supports, be sure to read the general information under “Notices” on page
443.

Twentieth Edition, April 2009

This is a major revision of SA22-7626-18.
This edition applies to Version 1 Release 10 of z/OS (5694-A01) and to all subsequent releases and modifications
until otherwise indicated in new editions.
IBM welcomes your comments. A form for readers’ comments may be provided at the back of this document, or you
may address your comments to the following address:
International Business Machines Corporation
MHVRCFS, Mail Station P181
2455 South Road
Poughkeepsie, NY 12601-5400
United States of America

FAX (United States & Canada): 1+845+432-9405

FAX (Other Countries):
Your International Access Code +1+845+432-9405

IBMLink (United States customers only): IBMUSM10(MHVRCFS)

Internet e-mail: mhvrcfs@[Link]
World Wide Web: [Link]
If you would like a reply, be sure to include your name, address, telephone number, or FAX number.
Make sure to include the following in your comment or note:
v Title and order number of this document
v Page number or topic related to your comment
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1988, 2009.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Who should use this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
How to use this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Code descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
How System Codes are Explained in this Book . . . . . . . . . . . . . . . . . . . . . vi
Location of user completion codes . . . . . . . . . . . . . . . . . . . . . . . . . vii
Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Information updates on the web . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Using LookAt to look up message explanations . . . . . . . . . . . . . . . . . . . . . vii

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Completion Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Abend of a Task or Address Space . . . . . . . . . . . . . . . . . . . . . . . . . 1
Abend of a System Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Abnormal End of Subtasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Wait State Codes in z/Architecture Mode . . . . . . . . . . . . . . . . . . . . . . . . 2
No Work Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Wait State Codes from a Stand-Alone Dump Program . . . . . . . . . . . . . . . . . . . 3
IPCS User Completion Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. System Completion Codes . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 3. Wait State Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

Chapter 4. System Completion Code to Module Table . . . . . . . . . . . . . . . . . 409

Chapter 5. Wait State Code to Module Table . . . . . . . . . . . . . . . . . . . . . 421

Chapter 6. Stand-Alone Dump Wait State Codes . . . . . . . . . . . . . . . . . . . 427

Chapter 7. IPCS User Completion Codes . . . . . . . . . . . . . . . . . . . . . . 435

Appendix. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Using assistive technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Keyboard navigation of the user interface . . . . . . . . . . . . . . . . . . . . . . . 441
z/OS information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Policy for unsupported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

© Copyright IBM Corp. 1988, 2009 iii

iv z/OS V1R10.0 MVS System Codes
About this document
This document describes the system completion codes and wait state codes issued by components,
products, and subsystems of z/OS (5694–A01). The document helps you interpret and respond to the
system completion codes and wait state codes.

System completion codes are also called abend codes.

Who should use this document

z/OS MVS System Codesis for all people who receive abend and wait state codes from the system.
Usually, these people are system operators, system programmers, and application programmers who do
any of the following tasks:
v Initialize the operating system and its subsystems
v Keep the system running correctly
v Diagnose and correct system problems
v Diagnose and correct errors in problem programs

How to use this document

z/OS MVS System Codescontains:
v An introduction to the format of system and user completion codes and of wait state codes
v Descriptions of system completion codes issued by system components, products, and subsystems
v Descriptions of wait state codes loaded during system operation
v Descriptions of wait state codes loaded during operation of a stand-alone dump program

Code descriptions
Each type of code is arranged in hexadecimal order in a chapter. The description of each code:
v Explains why the code was issued.
v Identifies the component, subsystem, or product issuing the code.
v Describes the actions taken by the system.
v Suggests actions that the operator, user, application programmer, or system programmer can take, if
appropriate, in response to the code.

The system programmer responses assume that the programmer has performed the customary diagnosis
described in the z/OS Problem Management.

© Copyright IBM Corp. 1988, 2009 v

How System Codes are Explained in this Book
The following describes the different parts of system code explanations in this book:
Explanation
The meaning of the abend, including why the system issued the abend.
System Action
v What the system did as a result of the system condition reported by the abend. A system
condition could include running out of storage, a hardware or software failure, or other situation.
v What the system did as a result of user input. User input can include a system command, a job
running on the system, a transaction, a query, or another user-system interaction.
Operator Response
Instructions for the system operator, including, as appropriate, decisions to make and actions to
take.
Only provided for abends that could appear at the system console.
User Response
Instructions for the end user.
Application Programmer Response
Instructions for an application programmer.
System Programmer Response
Instructions for the system programmer.
Only provided for abends that require additional action beyond the operator response, user
response, or application programmer response.
Storage Administrator Response
Instructions for the DFSMSdfp storage administrator.
Security Administrator Response
Instructions for the security administrator.
Only provided for security-related abends.
Problem Determination
Additional instructions for determining the cause of the problem, searching problem databases,
and, if necessary, reporting the problem to the IBM support center. These instructions are for a
customer support person who can troubleshoot problems, such as the system programmer or
system administrator, an experienced security administrator, or an experienced storage
administrator.
For additional information on performing problem determination procedures, see z/OS Problem
Management and the appropriate diagnosis guide for the product or element issuing the abend,
such as:
v DFSMS/MVS diagnosis guides and references
v z/OS JES2 Diagnosis
v z/OS JES3 Diagnosis
Source
Element, product, or component that issued the abend.
Detecting Module
Name of the module or modules that detected the condition that caused the abend to be issued.

vi z/OS V1R10.0 MVS System Codes

Location of user completion codes
z/OS MVS System Codesdoes not contain the 4-digit decimal user completion codes that some
IBM-provided components, subsystems, or products issue. These codes appear in documents for the
component, subsystem, or product that issues the codes. Codes issued by installation-provided programs
do not appear in IBM® documents.

Where to find more information

Where necessary, this document references information in other documents, using the shortened version
of the document title. For complete titles and order numbers of the documents for all products that are part
of z/OS, see z/OS Information Roadmap.

The following table lists the titles and order numbers of documents for other IBM products.

Title Order Number

IBM Graphics Access Method/System Product: Messages and Codes SC33-0143
z/Architecture Principles of Operation SA22-7832
Print Services Access Facility for MVS User’s Guide and Reference S544-3100

Information updates on the web

For the latest information updates that have been provided in PTF cover letters and Documentation APARs
for z/OS®, see the online document at:
[Link]

This document is updated weekly and lists documentation changes before they are incorporated into z/OS
publications.

Using LookAt to look up message explanations

LookAt is an online facility that lets you look up explanations for most of the IBM messages you encounter,
as well as for some system abends and codes. Using LookAt to find information is faster than a
conventional search because in most cases LookAt goes directly to the message explanation.

You can use LookAt from these locations to find IBM message explanations for z/OS elements and
features, z/VM®, VSE/ESA™, and Clusters for AIX® and Linux®:
v The Internet. You can access IBM message explanations directly from the LookAt Web site at
[Link]/servers/eserver/zseries/zos/bkserv/lookat/.
v Your z/OS TSO/E host system. You can install code on your z/OS systems to access IBM message
explanations using LookAt from a TSO/E command line (for example: TSO/E prompt, ISPF, or z/OS
UNIX® System Services).
v Your Microsoft® Windows® workstation. You can install LookAt directly from the z/OS Collection
(SK3T-4269) or the z/OS and Software Products DVD Collection (SK3T-4271) and use it from the
resulting Windows graphical user interface (GUI). The command prompt (also known as the DOS >
command line) version can still be used from the directory in which you install the Windows version of
LookAt.
v Your wireless handheld device. You can use the LookAt Mobile Edition from [Link]/servers/
eserver/zseries/zos/bkserv/lookat/[Link] with a handheld device that has wireless access and an
Internet browser.

You can obtain code to install LookAt on your host system or Microsoft Windows workstation from:
v A CD in the z/OS Collection (SK3T-4269).

About this document vii

v The z/OS and Software Products DVD Collection (SK3T-4271).
v The LookAt Web site (click Download and then select the platform, release, collection, and location that
suit your needs). More information is available in the [Link] files available during the download
process.

viii z/OS V1R10.0 MVS System Codes

Summary of changes
Summary of changes
for SA22-7626-19
z/OS Version 1 Release 10
as updated April 2009

The document contains information previously presented in z/OS MVS System Codes, SA22-7626-18,
which supports z/OS Version 1 Release 10.

New information
v New system completion codes 150 and 7D0 have been added.
v System completion code 0F7 has a new reason code 13C.
v System completion code 1FB has a new reason code 6F.
v System completion code DC2 has new reason codes 0022, 0053, 0054 and 00AE.
v System completion code 18F has new reason codes 6D, CC, CD and D0.
v System completion code 0F7 has a new reason code 140.
v System completion code 306 has a new reason code 40.

Changed information

The following system completion codes have changed:

v 042
v 058
v 05C
v 071
v 07D
v 0C4
v 0D6
v 0D7
v 253
v DC2
v EC6

You may notice changes in the style and structure of some content in this document—for example,
headings that use uppercase for the first letter of initial words only, and procedures that have a different
look and format. The changes are ongoing improvements to the consistency and retrievability of
information in our documents.

This document contains terminology, maintenance, and editorial changes. Technical changes or additions
to the text and illustrations are indicated by a vertical line to the left of the change.

Summary of changes
for SA22-7626-18
z/OS Version 1 Release 10
as updated October 2008

The document contains information previously presented in z/OS MVS System Codes, SA22-7626-17,
which supports z/OS Version 1 Release 10.

© Copyright IBM Corp. 1988, 2009 ix

New information

The following system completion codes have been added:

v 7B0

This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.

Summary of changes
for SA22-7626-17
z/OS Version 1 Release 10

The document contains information previously presented in z/OS MVS System Codes, SA22-7626-16,
which supports z/OS Version 1 Release 9.

New information

The following system completion codes have been added:

v 2E0
v D24
v DC4

The following wait state codes have been added:

v A2C
v 0B5

Changed information

The following system completion codes have changed:

v 01D
v 02A
v 05C
v 077
v 09A
v 0F7
v 157
v 1FB
v 233
v 438
v 55F
v 5FC
v 653
v C0D
v DC2
v E23

The following wait state codes have changed:

v 007
v 05E
v 082

x z/OS V1R10.0 MVS System Codes

v 087
v 08A
v 0A2
v 0A3
v 0B1
v 202
v 204
v A22
v A70
v D0D

This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.

Summary of changes
for SA22-7626-16
z/OS Version 1 Release 9
as updated April 2008

The document contains information previously presented in z/OS MVS System Codes, SA22-7626-15,
which supports z/OS Version 1 Release 9.

New information

The following wait state code has been added:

v 0B5

Changed information

The following system completion codes have changed:

v 00C
v 05C
v 2E0
v 35F
v 400
v 422
v 800
v 922
v EC6

The following wait state codes have changed:

v 0A2
v 0A3
v 0E1

This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.

Summary of changes xi
Summary of changes
for SA22-7626-15
z/OS Version 1 Release 9

The document contains information previously presented in z/OS MVS System Codes, SA22-7626-14,
which supports z/OS Version 1 Release 8.

New information

The following system completion codes have been added:

v 050
v 1D0
v 1E0
v 2E0

Changed information

The following system completion codes have changed:

v 00C
v 02A
v 05C
v 077
v 09A
v 0E0
v 15F
v 18F
v 1C5
v 1FB
v 290
v 2C3
v 300
v 378
v 3C5
v 422
v 730
v 738
v C78
v D22
v D23
The following wait state codes have changed:
v 00A
v 05E
v 074
v 0A2
v 0A3
v 0B5

xii z/OS V1R10.0 MVS System Codes

This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.

Summary of changes
for SA22-7626-14
z/OS Version 1 Release 8
as updated April 2007

The document contains information previously presented in z/OS MVS System Codes, SA22-7626-13,
which supports z/OS Version 1 Release 8.

New information:
v System completion code 02A has the following new reason codes:
– 00000030
– 00000034
– 00000038
– 0000003C
– 00000040
v System completion code 05C has a new reason code 200.
v System completion code 422 contains new information about TCP/IP reason codes.
v Wait state code 007 has two new reason codes: 0000 and 0001.
v Wait state code 0A2 has two new reason codes: 158 and 15A.

Changed information:
v System completion code 02A contains changed information about the following reason codes:
– 00000004
– 00000008
– 0000000C
– 00000010
– 0000001C
– 00000020
– 00000024
– 00000028
– 0000002C
v System completion code 102 contains changed information about reason code 00.
v System completion codes 3C5 and 4C5 contains changed information about reference documentation.

Deleted information:
v The reason code 00000014 of system completion code 02A is removed.
v The reason code 08 of system completion code 402 is removed.

This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.

Summary of changes
for SA22-7626-13
z/OS Version 1 Release 8

The document contains information previously presented in z/OS MVS System Codes, SA22-7626-12,
which supports z/OS Version 1 Release 7.

Summary of changes xiii

New information

The following system completion codes have been added:

v 653

Changed information

The following system completion codes have changed:

v 077
v 0F7
v 1FB
v 2C3
v 2F3
v 3C4
v 653
v 800
v 9C6
v D23
v EC6
The following wait state codes have changed:
v 087
v 204

Deleted information

The following system completion codes have been deleted:

v C50C

This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.

xiv z/OS V1R10.0 MVS System Codes

Chapter 1. Introduction
This chapter topic introduces system and user completion codes and wait state codes.

Completion Codes
The system or an application program issues a completion code when abnormally ending processing by a
task, address space, or system module. The completion code indicates the reason for the abnormal end. A
completion code can be specified by the following:
v ABEND macro
v CALLRTM macro
v SETRP macro

Abend of a Task or Address Space

For a System-Detected Problem

The system abnormally ends a task or address space when the system determines that the task or
address space cannot continue processing and produce valid results.

For example, a task may incorrectly specify a request for a system service. Because the system cannot
perform the service with incorrect input, the system abnormally ends the task requesting the service. This
task is also referred to as a caller.

For a Hardware-Detected Problem

The system also abnormally ends a task with a completion code when the system receives control after a
hardware-generated interruption that indicates an error in the task.

For example, an instruction in an application running in storage key 7 branches to low central storage,
which is always in storage key 0. The difference in storage key causes a protection exception. The system
recovers from this hardware problem by ending the application’s task with an abend X'0C1'. If the
application has a recovery routine, the system gives control to the routine; the routine can clean up
resources being used by the application and can request a dump.

For an Application-Detected Problem

An application program abnormally ends itself when it determines that it cannot continue processing and
produce valid results.

For example, an application may be calculating a total by successive additions. After each addition, the
application checks the new total against a limit. If the total exceeds the limit, the application issues an
ABEND macro to end abnormally and, perhaps, to ask for an ABEND dump. The ABEND macro specifies
a user completion code.

Abend of a System Service

If a system service represented by a service request block (SRB) experiences a problem, the system gives
control to the recovery routine for the service; the routine can issue a SETRP macro to place a system
completion code in the system diagnostic work area (SDWA). The system service stops processing. If the
service was processing a request from a task, the system abnormally ends the task with the same system
completion code.

Note that another task can request the system service to do processing.

© Copyright IBM Corp. 1988, 2009 1

Format
The format of completion codes is:
v System completion code (or abend code): 3 hexadecimal digits
v User completion code: 4 decimal digits

Note: Only system completion codes appear in this book ; user completion codes do not. User completion
codes are in book for the IBM-provided component, subsystem, or product that issues the user
completion codes. IPCS user completion codes are documented in Chapter 7, “IPCS User
Completion Codes,” on page 435. Codes issued by installation-provided programs do not appear in
IBM book .

Location
The codes can be obtained from the following:
v Messages accompanying the abend
v The header in any ABEND dump accompanying the abend
v Search arguments and, sometimes, the title in any SVC dump accompanying the abend
v Search arguments in any logrec data set error record written for the abend
v The system diagnostic work area (SDWA)
v Use of the EXTRACT macro with keyword CMC to determine the completion code for the ended task.

Abnormal End of Subtasks

When the highest-level task in a job step ends abnormally, the job step ends abnormally.

When a subtask ends abnormally, only the subtask itself and its subtasks end. To get the abend code for
an abnormal end of a subtask:
v Examine the event control block (ECB) specified by the task that attached the subtask
v Issue the EXTRACT macro with the CMC keyword

A low-level subtask that ends abnormally has two ways to cause the entire job step to end abnormally:
v Each task in the job step’s task chain, including the job step task, must end itself abnormally when it
detects an abend code from one of its subtasks. To end the job step with the abend code for the
original error, each task must use the abend code from its subtask as its own abend code.
v A subtask can abnormally end the entire job step if it specifies a STEP parameter on the ABEND
macro.

Wait State Codes in z/Architecture Mode

The wait state code appears in the program status word (PSW) when the operating system enters a wait
state. A valid PSW for a coded wait state in z/Architecture® mode has one of the following general formats:
v 00020000 x0000000 00000000 0rrrrwww
v 00020000 x0000000 00000000 0rr00www
v 00020000 x0000000 00000000 00rrrwww
v 00020000 x0000000 00000000 0rrr0www
2 Bits 12-15 (the CMWP bits, with the 'W' bit being on).
x Bits 32-35. Not part of the wait state information.
rrrr, rr00, 0rrr, rrr0
Bits 100-115, where r is the reason code for 8/12/16 bits and 0=zero.
A supplementary code accompanying the wait state code.
The wait state determines the size and position of the supplement code.

2 z/OS V1R10.0 MVS System Codes

 Usually the supplementary code is a reason code. Some wait state codes do not provide a
supplementary code in the PSW. See the description of the individual wait state code for more
information.
www
Bits 116-127.
The wait state code. The IBM-supplied wait state codes appear in this book . Installation-supplied
programs can use the wait state codes X'FF0' through X'FFE'; see installation-supplied information for
these codes.

No Work Wait
If the system hangs because it has no work waiting to be dispatched, either because the work is waiting
for a resource or because no work remained on the system queues, the PSW contains:
X'07060000 00000000 00000000 00000000'

A no work wait may not reflect an error. See z/OS Problem Management for diagnosis of a hang or wait.

Wait State Codes from a Stand-Alone Dump Program

See Chapter 6, “Stand-Alone Dump Wait State Codes,” on page 427 for information about reading
stand-alone dump wait state codes.

IPCS User Completion Codes

IPCS issues a 4 digit decimal user code when it encounters errors in either IBM-provided IPCS code or in
installation exit routines. See Chapter 7, “IPCS User Completion Codes,” on page 435 for more
information.

Chapter 1. Introduction 3
4 z/OS V1R10.0 MVS System Codes
Chapter 2. System Completion Codes
reflect the correct number of tracks, or correct the DCB
001
BLKSIZE.
Explanation: An I/O error condition was encountered
System programmer response: If the error recurs
during BDAM, BISAM, BPAM, BSAM, QISAM, or QSAM
and the program is not in error, look at the messages in
processing.
the job log for more information. Search problem
The completion code can be issued if CLOSE reporting data bases for a fix for the problem. If no fix
processing called end-of-volume (EOV), and EOV exists, contact the IBM Support Center. Provide the JCL
processing detected an out-of-space condition. Refer to and the program listing for the job.
the explanation of message IEC020I in z/OS MVS
Source: DFSMSdfp
System Messages, Vol 7 (IEB-IEE) for information about
the task that was ended.
003
Application Programmer Response: Respond as
indicated for message IEC020I. Explanation: The error occurred during end-of-block
processing using either BSAM or QSAM. The error
System programmer response: If the error recurs
occurred because the I/O macro instructions for a
and the program is not in error, look at the messages in
3525-associated data set were not run in the proper
the job log for more information. Search problem
sequence.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL The hexadecimal reason code in register 15 indicates
and the program listing for the job. the nature of the error:
Source: DFSMSdfp™ Code Explanation
01 A READ sequence error
002
02 A PUNCH sequence error
Explanation: For all return codes except 2C, the error
occurred while the control program was processing a 03 A PRINT sequence error
sequential data set with BSAM or QSAM, or creating a System action: The system ends the task.
direct organization data set. This system completion
code is accompanied by message IEC036I. Refer to the Application Programmer Response: Specify the I/O
explanation of message IEC036I for complete macro instructions in the proper sequence, and rerun
information about the task that was ended and for an the job.
explanation of the return code found in register 15. System programmer response: If the error recurs
For return code 2C, the error occurred while the control and the program is not in error, look at the messages in
program was opening an ISAM data set for QISAM load the job log for more information. Search problem
mode. Too many tracks were specified for cylinder reporting data bases for a fix for the problem. If no fix
overflow, or DCB BLKSIZE was not a multiple of DCB exists, contact the IBM Support Center. Provide the
LRECL, or DCB BLKSIZE was greater than the track program listing for the job.
size. Source: DFSMSdfp
System action: For all return codes except 2C,
pertinent control blocks are written to the GTF trace 004
data set, the user’s DCB ABEND exit is taken if one is
provided, and message IEC036I is issued. Explanation: The error occurred during OPEN
processing using either BSAM or QSAM because a
Operator response: Start a generalized trace facility conflicting or incorrect DCB parameter (FUNC or related
(GTF) trace, and re-create the problem. Reply to parameter) is specified. The hexadecimal reason code
message AHL100A with: in register 15 indicates the nature of the error:
TRACE=SYS,USR,SLIP
Code Explanation
On the DD statement for the data set in error, specify: 01 Incorrect DCB FUNC parameter specified.
DCB=DIAGNS=TRACE 02 Incorrect combination of DCB FUNC parameter
Application Programmer Response: See message and CNTRL macro specified.
IEC036I for the appropriate responses for each return 03 Conflicting access methods specified.
code except 2C. For return code 2C, change the
CYLOFL operand of the DCB macro instruction to 04 Incorrect DCB specified for 3505 or 3525.

© Copyright IBM Corp. 1988, 2009 5

005 • 00A

05 Incorrect format card or an incorrect device exists, contact the IBM Support Center. Provide the JCL
specified with Optical Mark Read (OMR). and the program listing for the job.
06 Data protection image not found in the Source: DFSMSdfp
[Link] data set, volume containing
[Link] not mounted, or
00A
[Link] data set not cataloged.
Explanation: A program attempted to schedule an
System action: In all cases, the system ends the task.
asynchronous or installation exit by branch-entering the
Application Programmer Response: In all cases, stage 2 exit effector. The stage 2 exit effector detected
correct the incorrect fields of the DCB macro instruction a problem.
and rerun the job.
A hexadecimal reason code in register 15 explains the
System programmer response: If the error recurs error:
and the program is not in error, look at the messages in
Code Explanation
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix 0004 IQETCB did not point to a valid TCB. A
exists, contact the IBM Support Center. Provide the program sets up the IQE by putting a TCB
program listing for the job. address into the IQETCB field. The program
then branch-enters the stage 2 exit effector to
Source: DFSMSdfp
schedule an asynchronous or installation exit,
passing the address of the IQE.
005
0008 RQETCB did not point to a valid TCB. A
Explanation: The error occurred because of an program sets up the RQE by putting a TCB
incorrect DECB during READ processing using BSAM. address into the RQETCB field. The program
This system completion code is accompanied by then branch-enters the stage 2 exit effector to
message IEC041I. Refer to the explanation of message schedule an asynchronous or installation exit,
IEC041I for complete information about the task that passing the address of the RQE.
was ended and for an explanation of the return code.
000C The program branch-entering the stage 2 exit
System action: The task is ended. effector did not hold the local lock for the home
address space.
Application Programmer Response: Make sure that
the RBL type of read is used and that the area address 0010 The program branch-entering the stage 2 exit
and header address parameters are specified so that effector did not have addressability to the
the DECB is valid. address space in which the asynchronous or
installation exit was to be dispatched.
System programmer response: If the error recurs
and the program is not in error, look at the messages in 0014 The program branch-entering the stage 2 exit
the job log for more information. Search problem effector was not in primary or secondary
reporting data bases for a fix for the problem. If no fix address space control (ASC) mode.
exists, contact the IBM Support Center. Provide the
System action: The system abends the program that
program listing for the job.
branch-entered the stage 2 exit effector. The system
Source: DFSMSdfp may also write a logrec data set error record and an
SVC dump.
008 Operator response: If the system programmer asks
for an SVC dump, set the following SLIP trap:
Explanation: The error occurred during processing of
a SYNAD routine. The routine was given control SLIP SET,COMP=00A,ACTION=SVCD,END
following processing of a BSAM CHECK macro System programmer response: Do the following:
instruction.
v If an SVC dump or a logrec data set error record is
The SYNAD routine returned control to the control not written with the abend, ask the operator to set a
program for the CHECK macro instruction. SLIP trap to obtain an SVC dump.
Application Programmer Response: Correct the v Use the address in register 14 at the time of error to
SYNAD routine so that the control program save area is identify program that branch-entered the stage 2 exit
not destroyed. Then run the job step again. effector.
– For an installation-provided module, continue
System programmer response: If the error recurs
diagnosis with the module.
and the program is not in error, look at the messages in
the job log for more information. Search problem – For an IBM module, search problem reporting data
reporting data bases for a fix for the problem. If no fix bases for a fix for the problem. If no fix exists,
contact the component group for the module at

6 z/OS V1R10.0 MVS System Codes

 00B • 00C

the IBM Support Center. Provide, if available, the 202 The system found an error in the parameter list
SVC dump and the logrec data set error record. passed by the routine that reads and writes
from data sets.
Source: Supervisor control
System action: The system writes an error record to
the logrec data set and writes an SVC dump.
00B
Operator response: If the abend recurs, notify the
Explanation: During restart of a checkpointed job, the
system programmer.
system detected an error. A reason code in the
SDWACRC field of the system diagnostic work area System programmer response: If the error recurs,
(SDWA) accompanies the abend and explains the error: search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support
Code Explanation
Center.
001 The system failed to obtain enough storage
Source: Scheduler restart
from the pre-allocated storage area.
002 A storage pointer pointed to an area outside
00C
the pre-allocated storage area.
Explanation: Cross-system coupling facility (XCF)
1F4 A parameter list contained an error.
encountered an error. See z/OS MVS Diagnosis:
1F5 An error was detected during initialization of Reference for more information on diagnosing sysplex
scheduler restart. problems.
1F6 An error occurred while processing a find The reason code in register 15 is:
request.
Code Explanation
1F7 An error occurred while processing a get
00000004 A group member abended another
request.
group member using the IXCTERM
1F8 An error occurred while building a DD names macro.
table (DDNT) record for a scheduler work area
0000004C Data Space IXCDSCBE cannot be
(SWA) DDNT.
created or accessed.
1F9 An error occurred while building a DD names
00000040 A group member abended another
table (DDNT) record for unallocated step input
group member using the IXCTERM
output tables (SIOTs).
macro.
1FA An error occurred while building a Type 1 data
00000044 Data space IXCDSMEM cannot be
set descriptor record (DSDR) for a step input
created or accessed.
output table / job file control block
(SIOT/JFCB). 00000048 Data space IXCDSCBD cannot be
created or accessed.
1FB An error occurred while building a Type 2 data
set descriptor record (DSDR) for a job file 0000005C Either the system encountered an
control block extension (JFCBX). error while loading an XCF module or
an XCF module is missing from the
1FC An error occurred while building a Type 2 data
nucleus.
set descriptor record (DSDR) for a job file
control block extension (JFCBE). 00000100 Data Space IXCDSLO1 cannot be
created or accessed.
1FD An error occurred while building a Type 3 data
set descriptor record (DSDR) for a generation 00000104 Data Space IXCDSLK1 cannot be
data group name table (GDGNT). created or accessed.
1FE An error occurred while writing an updated step 00000108 Data Space IXCAP1DS cannot be
input output table (SIOT) to the scheduler work created or accessed.
area (SWA).
00000160 A member of an XCF group appeared
1FF An error occurred when the system tried to end to be causing signalling sympathy
the scheduler JCL facility (SJF). sickness and was terminated.
Message IXC615I is issued to indicate
200 An error occurred when a program issued the
which member was selected for
DELETE macro.
termination.
201 An error occurred when a program issued the
02070000 A non-retryable error occurred and the
WTO macro.
function is considered complete.

Chapter 2. System Completion Codes 7

00C

v If the message exit was not called, v Signals queued for processing by
the signal has been preserved and the user message exit routine have
will be presented later. not been processed in a timely
v If the message exit was called, the fashion
exit returned before the error v Signals queued for processing by
occurred, so the signal was the user message notify exit routine
delivered successfully. have not been processed in a
timely fashion
XCF percolates to the task to which v XCF work items queued for
the member is associated. The task processing in the member address
can retry in its recovery routine. The space have not been processed in
system issues a LOGREC data set a timely fashion
error record and an SVC dump. If the
ABEND occurred while XCF was in ″Timely″ is generally defined as 30
control, the system issues an SVC seconds. A member is considered
dump. stalled if any of the listed conditions is
02070001 A non-retryable error occurred and the true, even though it may be
signal data might not have been processing other XCF work in a timely
delivered to a member message exit. fashion.
v If the message exit routine was
The DISPLAY XCF,GROUP command
called, the failure occurred before
identifies stalled groups and members
the exit could successfully return to
with an asterisk (provided the stalled
XCF.
member is active on the system
v If the message exit was not called, where the command is executed).
XCF discarded the message, in Message IXC431I is issued to
which case a signal was lost. document a stall condition that
persists for more than 180 seconds.
XCF percolates to the task to which ABEND 00C reason 020F0006 is
the member is associated. The task issued if the stall condition persists for
can retry in its recovery routine. The more than 195 seconds. The ABEND
system issues a LOGREC data set does not impact the processing of the
error record. If the ABEND occurred stalled member as it is issued by the
while XCF was in control, the system monitor while running under a
issues an SVC dump. separate work unit in the XCF address
020F0006 A member of an XCF group appears space. Message IXC430E is issued if
to be stalled. XCF periodically the stall condition persists for more
monitors each active member of an than 300 seconds.
XCF group to determine whether the
member is processing its XCF work in The stall could be due to a user error,
a timely fashion. The monitor an internal XCF error, a system error
considers a member to be stalled if (such as storage overlay or lost SRB),
any of the following are true: or could be normal behavior from
which the system will recover. The
v A user group exit routine has not
system issues this ABEND to initiate
returned control to XCF in a timely
recovery actions to document the
fashion
problem, and to verify/repair internal
v A user message exit routine has XCF control blocks. For signalling
not returned control to XCF in a related stalls, the system may provide
timely fashion replacement member message
v A user message notify exit routine delivery cell(s) in hopes that signal
has not returned control to XCF in delivery can resume. If signal delivery
a timely fashion does not resume, signalling resources
v An SRB scheduled to the member (for example, MMDCs or SIOCBs)
address space to perform internal may be consumed/lost for the life of
XCF processing has not returned the member. This consumption of
control in a timely fashion signalling resources could surface
itself in many ways, such as: common
v Events queued for processing by storage growth, degradation of signal
the user group exit routine have not delivery (possible to the point where
been processed in a timely fashion

8 z/OS V1R10.0 MVS System Codes

 00C

no signals can be delivered), rejected Exit for this event. The exit will be
message-out requests, or repeated rescheduled and presented with the
path restarts. same event.
020F000C A member of an XCF group appears 060C0001 Group information may have been lost
to be causing signaling sympathy due to either a non-recoverable error
sickness. in XCF or the users Group Exit has
ABENDed two consecutive times. This
The DISPLAY XCF,GROUP command
code indicates the user may want to
identifies stalled group and member
issue a IXCQUERY macro to see
causing signaling sympathy sickness
what may have been lost.
with an exclamation point (in addition
to the asterisk, since any member 081C0001 XCF forcibly ended processing of a
causing signaling sympathy sickness SETXCF STOP command that was
has to be stalled as well). stopping a signalling path. This can
happen when an operator specifies
020F000D A member of an XCF group appears
UNCOND=YES on a SETXCF STOP
to be causing signaling sympathy
command.
sickness and is about to be
terminated. When the The XCF signalling service may have
MEMSTALLTIME interval expires, lost some messages as a result of this
XCF determines which member is ABEND. There may be unpredictable
most responsible for causing the results for the XCF groups whose
problem and initiates an SVC dump. messages got lost.
Message IXC615I indicates which
081CFF01 Unconditional stop processing is
member was selected for termination.
terminating the task that is currently
05070000 An error occurred while XCF was processing a signalling path START,
processing a Status Exit. XCF STOP, or RESTART request.
continues processing the Status Exit.
08960002 Internal error.
XCF tries to end the task that owns
0A1x0001 (x=4,5,6)
the Status Exit. The system writes a
A couple data set has been taken
LOGREC data set error record. If the
over by another sysplex. The data set
ABEND occurred while XCF was in
is removed from service in the sysplex
control, the system issues an SVC
of which the issuing system is a
dump.
member. The system does not take a
05070000 An error occurred while XCF was dump, but records the error in
processing a Status Exit. XCF LOGREC.
continues processing the Status Exit.
0A1x0070 (x=4,5,6)
XCF tries to end the task that owns I/O interrupt occurred with an invalid
the Status Exit. The system writes a CCW address.
LOGREC data set error record. If the
0A1x0074 (x=4,5,6)
ABEND occurred while XCF was in
XCF detected an I/O error while
control, the system issues an SVC
reading or writing to a couple data set.
dump.
This may be a hardware error.
06010001 Internal error.
If XCF cannot recover from the I/O
060B0001 An error occurred while XCF was error, it may end one or more groups
processing a Group Exit. Some group or members using the couple data set,
event information may have been lost. or else stop using the couple data set.
XCF writes a LOGREC data set error
XCF tries to end the task that owns
record.
the Group Exit. Some group event
information may have been lost. The 0A1x0078 (x=4,5,6)
system writes a LOGREC data set Failure of a previous write to the
error record. If the ABEND occurred couple data set was detected.
while XCF was in control, the system
11050040 Data space IXCDSMEX cannot be
issues an SVC dump.
created or accessed.
060C0000 A non-retryable error has occurred on
11050041 Data space IXCDSMEX cannot be
the first invocation of the users Group
created or accessed.

Chapter 2. System Completion Codes 9

00C

13C00851 System REXX™ exec IXCL2XPU is 02160001 02160002 02160003 02160005 02170001
missing from the System REXX 02170002 02170003 02170004 02170006 02170007
library. 02170008 021A0001 02220001 02220002 02220003
13C008xx The system encountered an error 02220004 02220005 02220006 022D0002 02330001
executing System REXX exec 02330002 02380002 02430001 05010084 05030088
IXCL2XPU. 05050090 08030001 08030002 08040001 08060002
08080001 08080002 080A0001 080C0001 08201002
16140003 Internal error. 08201003 0820100C 08221001 08221007 08240001
17090001 The system encountered an error 08300001 08300002 08321001 08340001 085A1006
executing System REXX exec 08600001 08600002 08690001 08691001 086B0001
IXCRXCDS, or System REXX exec 08750001 08750002 08750003 08780001 08780002
IXCRXCDS is missing from the 08781001 087A1001 087E1002 08801004 08891001
System REXX library. 088E0001 08960001 08960002 08FB0100 08FD0001
08FF0001 08FF0224 09030001 09031001 09080001
System action: XCF tries to end a member of a group 09080002 09080003 09080004 090A0001 090A0002
in the sysplex. The system may issue a LOGREC data 090E0001 09110001 091C0001 0F01008C 0F07006E
set error record or an SVC dump. Messages explaining 0F080060 0F08006C 0F0F008C 12B10001 12B10002
the error might precede this ABEND. Depending on the 16030001 16050010 16090010 16090030 16090050
reason code, the system also does the following:
16090070 160B0010 160B0030 160D0001 160F0001
Code Explanation 160F0002 160F0003 160F0004 160F0005 16100001
16120001 16140001 16140002 16160001 16160002
00000004 XCF ends the group member. 16160003 16160004 16160005 16160006 161E0002
08960002 The system initiates two MVS™ 161E0003 161E0004 161E0005 161E0006 161E0007
dumps. 161E0008 16200001 16200002 16240030 16280001
16280002 16280003 162A0001 162A0002 162A0003
Others XCF tries to end a member of a group 162A0004 162A0005 162A0006 162A0007 162A0008
in the sysplex. The system may issue
162A0009 162A000A 162A000B 162A000C 162A000D
a LOGREC data set error record or an
162A000E 162C0010 162C0030 16320001 16320002
SVC dump. Messages explaining the
163C0001 163C0002 163E0001 163E0002 16400010
error might precede this ABEND.
16400020 16400030 16420001 16440010 16440030
Operator response: Depending on the reason code, 16440050 16440070 16440090 164400B0 164E0001
do the following: 164E0002 164E0003 164E0004 164E0005 16500001
16500003 16500004 16500005 16500006 16560001
Code Explanation
16560002 16560003 16560004 165B0001 xxxx1008
08960002 Contact your system programmer. xxxx100C

0A1x0074 (x=4,5,6)
Determine the cause of the I/O error.
Note:
If the error is caused by a hardware
problem, contact hardware support.
For reason code 08960002, the system initiates two
Others See the operator response for the MVS dumps. In this case, both dumps should be
preceding messages. Obtain the gathered before contacting the IBM Support Center.
LOGREC data set and SVC dump, if
Application Programmer Response: Depending on
one is issued. Notify the system
the reason code, do the following:
programmer.
Code Explanation
The following reason codes represent errors internal to
02070001 Make sure that the program that owns
the XCF component. Call the IBM Support Center for
the message exit has recovery
assistance with these errors. Provide the LOGREC data
established for missing messages.
set and SVC dump, if one is issued.
The recovery routine might do one of
Reason Codes: the following:
v Send a request to other active
00000050 00000054 00000058 00000060 00000064 group members requesting that
00000068 0000006C 00000070 00000080 0000008C they resend the message.
00000120 00000124 00000134 02030001 02030002 v Back up to a previous point in the
02030003 02070002 020F0001 020F0002 020F0003 program and continue processing
020F0005 020F0007 020F0008 020F0009 020F000A from there.
02130001 02140001 02140002 02140003 02140005 v End the task if the function cannot
tolerate any missing messages.

10 z/OS V1R10.0 MVS System Codes

 00D

060B0001 Determine which program owned the

00D
Group Exit. Make sure that the
program that owns the Group Exit has Explanation: An error occurred during processing of a
recovery established to handle CTRACE or CTRACEWR macro. Register 15 contains a
missing group event information. The reason code that further describes the error.
recovery routine should do one of the
Code Explanation
following:
v Issue the IXCQUERY macro to 00000101 For the CTRACE DEFINE macro, the
determine whether group event parameter list version number is
information was lost. incorrect.
v Back up to a previous point in the 00000102 For the CTRACE DEFINE macro, the
program and continue processing component name either does not
from there. begin with an alphabetic or national
v End the task if the function cannot character, or it contains one or more
tolerate missing information. characters that are not alphanumeric
or national characters.
08960002 Contact your system programmer.
00000301 The system found either nonzero
System programmer response: Depending on the values in the reserved fields or
reason code, do the following: unused fields for the requested
Code Explanation service in the CTRACE DEFINE
macro parameter list.
08960002 Call the IBM Support Center for
assistance with these errors. Provide 00000302 The system found either nonzero
both MVS dumps issued by the values in the reserved fields or
system. unused fields for the requested
service in the CTRACE DELETE
Other internal reason codes macro parameter list.
Call the IBM Support Center for
assistance with these errors. Provide 00000401 For the CTRACE macro, an incorrect
the LOGREC data set and SVC service request code was specified.
dump, if one is issued. Valid services are DEFINE and
DELETE.
Non-internal reason codes
00000501 For the CTRACE DEFINE macro, the
See the system programmer response length of the minimum options string
for the messages preceding this is greater than 256 bytes.
abend.
00010100 For the CTRACEWR macro, the
If the problem persists, do the parameter list version number is
following: incorrect.
v Format the SVC dump with the
00010200 The system found either nonzero
IPCS COUPLE subcommand.
values in the reserved fields or
Include all the reports and the
unused fields for the requested
summary, detail, and exception
service in the CTRACEWR macro
levels for each report.
parameter list.
v Format the SVC dump with the
IPCS CTRACE COMP(SYSXCF) 00010300 For the CTRACEWR macro, the buffer
subcommand to obtain XCF length was passed was zero or less.
component trace data. System action: The component trace service
v Search problem reporting data abnormally ends.
bases for a fix for the problem. If no
Application Programmer Response: Correct the
fix exists, contact the IBM Support
input on the CTRACE or CTRACEWR macro. See the
Center. Provide the formatted SVC
z/OS MVS Programming: Authorized Assembler
dump.
Services Reference ALE-DYN for the CTRACE and
Source: Cross-system coupling facility (XCF) CTRACEWR macros.
System programmer response: If the problem
recurs, search problem reporting data bases for a fix for
the problem. If no fix exists, contact the IBM Support
Center.

Chapter 2. System Completion Codes 11

00F • 016

Source: Component trace

014
Explanation: An error occurred during processing of a
00F
CLOSE macro instruction for a basic direct access
Explanation: The system detected a logic error in a method (BDAM) data set. This completion code is
hardware configuration definition (HCD) module. accompanied by message IEC208I. Refer to the
explanation of message IEC208I for complete
System action: The system issues message information about the task that was ended and for an
CBDA099I. The system abends the current task. explanation of the return code in register 15 (which is
Operator response: Notify the system programmer. provided in the IEC208I message text).

System programmer response: See z/OS HCD