Completion Codes
Uploaded by
niharapatilCompletion Codes
Uploaded by
niharapatilz/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: [email protected]
World Wide Web: http://www.ibm.com/systems/z/os/zos/webqs.html
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:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/ZDOCAPAR.
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
www.ibm.com/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 www.ibm.com/servers/
eserver/zseries/zos/bkserv/lookat/lookatm.html 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 LOOKAT.ME 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
SYS1.IMAGELIB data set, volume containing
SYS1.IMAGELIB not mounted, or
00A
SYS1.IMAGELIB 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 Application Programmer Response: Respond as
User’s Guide for diagnosing abend X'00F'. indicated for message IEC208I.
Source: Hardware configuration definition (HCD) System programmer response: If the error recurs
and the program is not in error, look at the messages in
the job log for more information. Search problem
012 reporting data bases for a fix for the problem. If no fix
Explanation: A program incorrectly issued a exists, contact the IBM Support Center. Provide the JCL
TIMEUSED macro. A reason code in register 15 and the program listing for the job.
explains the error: Source: DFSMSdfp
Code Explanation
4 The program issued TIMEUSED with 015
LINKAGE=SYSTEM, but the program was not Explanation: The print services access facility (PSAF)
in task control block (TCB) mode. detected an error condition that is identified by the
8 The program issued TIMEUSED with unique reason code accompanying this abend.
LINKAGE=SYSTEM, but the program held one Operator response: For an explanation of the system
or more locks. action, the programmer response, and the reason
C The program issued TIMEUSED with codes, see Print Services Access Facility for MVS
LINKAGE=SYSTEM when enabled unlocked User’s Guide and Reference
task (EUT) recovery routine was running. Source: DFSMSdfp
System action: The system abnormally ends the
program that issued the TIMEUSED macro. 016
Application Programmer Response: Modify the code Explanation: An error occurred in the sequential
so that TIMEUSED will be issued in the correct access method (SAM) SIO/PAGE FIX or direct access
environment. Run the program again. storage device (DASD) end-of-block modules. A reason
Source: Timer supervision code (hexadecimal) further explains the error:
Code Explanation
013 04 The DASD end-of-block modules issued an
Explanation: The error occurred during processing of EXCPVR SVC request on behalf of a user
an OPEN macro instruction. This system completion request, but a previous EXCPVR SVC request
code is accompanied by message IEC141I. Refer to the has not yet completed. One of the following
explanation of message IEC141I for complete occurred:
information about the task that was ended and for an v A data event control block (DECB) was used
explanation of the return code in register 15 (which is twice.
provided in the IEC141I message text). v Multiple READs or WRITEs were issued, but
Application Programmer Response: Respond as CHECK macros were not issued for those
indicated for message IEC141I. requests in the same order.
System programmer response: If the error recurs The SAM SIO/PAGE FIX appendage issued
and the program is not in error, look at the messages in this abend.
the job log for more information. Search problem 08 An EXCPVR SVC request on behalf of a user
reporting data bases for a fix for the problem. If no fix request was going to be issued to read a data
exists, contact the IBM Support Center. Provide the JCL set that is RACF® EXECUTE access protected,
and the program listing for the job. but the user is not in supervisor state. The
Source: DFSMSdfp SAM SIO appendage issued this abend.
12 z/OS V1R10.0 MVS System Codes
017 • 019
System action: The system abnormally ends the task. 0304 The content of access register 1, passed for a
RESUME macro with PURGE=YES, is not
System programmer response: If the EXCPVR SVC
valid.
request was issued before the first request was
completed, ensure that the DECB that is created for the 0308 The ALET, used to address the SPTOKEN and
READ/WRITE operation is tested for successful passed for a RESUME macro with SPTOKEN
completion before it is reused. Also, ensure that the and PURGE=YES, is not valid.
CHECK macros are issued in the same order as the
030C The SPTOKEN, passed for a RESUME macro
associated READ or WRITE macros.
with SPTOKEN and PURGE=YES, is not valid.
Otherwise, unless the task is in supervisor state, do not
System action: For all reason codes, the system
attempt to read a data set that is protected with RACF
abends the issuer of the SUSPEND or RESUME macro.
EXECUTE access authority.
For reason code X'0114' only, the system writes a
Source: DFSMSdfp
logrec data set error record and an SVC dump.
Operator response: If the system programmer asks
017
for an SVC dump, set the following SLIP trap:
Explanation: A program issued the SUSPEND or SLIP SET,COMP=017,ACTION=SVCD,END
RESUME macro with an SPTOKEN macro incorrectly. A
hexadecimal reason code in register 15 explains the System programmer response: Do the following:
error: 1. If an SVC dump is not produced with the abend, ask
the operator to set a SLIP trap to obtain an SVC
Code Explanation
dump.
0100 The issuer of a SUSPEND macro with 2. For reason code X'0110', look at the registers at the
SPTOKEN held a lock other than a local or time of error for the following:
CML lock.
v Register 2 contains the return code from
0104 The content of access register 1, passed for a SUSPEND macro processing.
SUSPEND macro with SPTOKEN, was not v Registers 3 and 4 contain the SPTOKEN.
valid.
3. Identify the module that issued the SUSPEND or
0108 The access list entry token (ALET), used to RESUME macro by using the program status word
address the SPTOKEN and passed for a (PSW) of the current entry in the linkage stack.
SUSPEND macro with SPTOKEN, is not valid. v For an installation-provided module, continue
010C The issuer of a SUSPEND macro with diagnosis with the module.
SPTOKEN was not running under a service v For an IBM module, search problem reporting
request block (SRB). data bases for a fix for the problem. If no fix
exists, contact the component group associated
0110 The SUSPEND EXIT (specified by the EXIT
with this module at the IBM Support Center.
keyword on the SUSPEND macro) returned an
Provide, if available, the SVC dump and the
incorrect return code to the system.
logrec data set error record. For reason code
0114 Recursive errors occurred while processing a X'0110', provide the problem data collected in
SUSPEND macro with SPTOKEN. step 2.
0200 The caller of the RESUME SPTOKEN= service Source: Supervisor control
held a lock higher than or equal to the DISP
lock in the locking hierarchy.
019
0204 The content of access register 1, and passed
Explanation: With the exception of reason code
for a RESUME macro, is not valid.
00000000, a window services request was made either:
0208 The ALET used to address the SPTOKEN, and v With an input parameter value that is not valid
passed for a RESUME macro, is not valid. v Without a required input parameter value
020C The SPTOKEN passed for a RESUME macro
Reason code 00000000 is applicable to any callable
is not valid.
service.
0300 The issuer of a RESUME macro with
SPTOKEN and PURGE=YES requested that The following hexadecimal reason codes provide further
an SRB be purged. This issuer held a lock information about the error:
higher than or equal to the DISP lock. The
Code Explanation
macro issuer must not hold such a lock.
00000000 Request failed. Routine on down-level
system.
Chapter 2. System Completion Codes 13
01A
00000110 Identify and access request failed. 00000151 Refresh request failed. Specified
Operation type is not valid. offset is larger than the maximum size
of the object.
00000111 Identify and access request failed.
Object type is not valid. 00000160 EVW request failed. The operation
type must be “BEGIN” or “END”.
00000112 Identify and access request failed.
Scroll area value is not valid. 00000161 EVW request failed. The object ID
specified is not valid.
00000113 Identify and access request failed.
Object state is not valid. 00000162 EVW request failed. The usage type
must be “SEQ”.
00000114 Identify and access request failed.
Access mode is not valid. 00000163 EVW request failed. The disposition
input value must be “REPLACE” or
00000115 Identify and access request failed.
“RETAIN”.
Object size is not valid.
00000164 EVW request failed. Specified offset is
00000116 Identify and access request failed.
larger than the maximum size of the
Object identifier is not valid.
object.
00000120 View request failed. Operation type is
00000166 EVW request failed. Span extends
not valid.
beyond the maximum size of the
00000121 View request failed. Object identifier is object.
not valid.
System action: The system abnormally ends the task.
00000122 View request failed. Usage type is not
Application Programmer Response: Check your
valid.
parameters for valid values and rerun your job.
00000123 View request failed. Disposition is not
System programmer response: If the parameters are
valid.
correct and the problem persists, search problem
00000124 View request failed. Specified offset is reporting data bases for a fix for the problem. If no fix
larger than the maximum size of the exists, contact the IBM Support Center.
object.
Source: Callable Services (SCCSR)
00000126 View request failed. Span extends
beyond the maximum size of the
01A
object.
Explanation: The system found a problem during
00000130 Scroll out request failed. Object
TSO/E LOGON processing. The following hexadecimal
identifier is not valid.
reason codes provide further information about the
00000131 Scroll out request failed. Specified error:
offset is larger than the maximum size
Code Explanation
of the object.
04 The LOGON RACF interface routine received
00000132 Scroll out request failed. Cannot
an incorrect function type.
perform the SCROLLOUT service
because the data object does not 08 The RACROUTE macro received incorrect
have a scroll area. parameters for storing logon information in the
RACF data base.
00000140 Save request failed. Object identifier is
not valid. 10 The RACROUTE macro received incorrect
parameters for obtaining logon information from
00000141 Save request failed. Specified offset is
the RACF data base.
larger than the maximum size of the
object. 18 The RACROUTE macro returned an incorrect
segment length.
00000142 Save request failed. The SAVE
service is not allowed, because the 1C The LOGON panel load module IKJLPxxx (xxx
data object was identified and is the 3-character code for the language in
accessed in READ ONLY mode. which the panel is written) is in error. The
variable recording area (VRA) contains the
00000150 Refresh request failed. Object
LOGON panel address and the offset being
identifier is not valid.
accessed in the panel.
20 The LOGON command detected an error in
data supplied by either installation exit
14 z/OS V1R10.0 MVS System Codes
01B • 01D
IKJEFLN1 or installation exit IKJEFLN2. The 08 The RACONVRT I/O routine received an
VRA will contain the parameter number and the incorrect data management request.
parameter entry in error.
System action: The system abnormally ends the
24 The LOGON command detected an error in command.
validated data. One of the following is true:
Operator response: Notify the system programmer.
v Either installation exit IKJEFLN1 or
installation exit IKJEFLN2 validated a field System programmer response: Obtain the JCL for
by setting the key to X‘04’. The LOGON the job. Obtain the SYSOUT output for the job. Collect
processor has found that this value is not all printed output and output data sets related to the
valid. For example, one of the exits may problem. If the problem recurs and if the program is not
have validated the new password field. in error, search problem reporting data bases for a fix
However, on the RACROUTE for the problem. If no fix exists, contact the IBM Support
REQUEST=VERIFY that is done by Center.
LOGON, RACF may reject the password. Source: Time Sharing Option Extensions (TSO/E)
v Either installation exit IKJEFLN1 or
installation exit IKJEFLN2 changed the key
of a field that was already validated (the key 01C
was X‘04’). Explanation: The RACROUTE macro returned an
v Either installation exit IKJEFLN1 or unexpected return code.
installation exit IKJEFLN2 requested that the
System action: The system abnormally ends the
LOGON processor prompt the user for a
command.
field that has already been validated (the
key is X‘04’). Operator response: Notify the system programmer.
The VRA contains the LOGON panel field System programmer response: Obtain the JCL for
number and the parameter entry in error. the job. Obtain the SYSOUT output for the job. Collect
all printed output and output data sets related to the
28 The LOGON help text load module IKJLHxxx
problem. If the problem recurs and if the program is not
(xxx is the 3-character code for the language in
in error, search problem reporting data bases for a fix
which the help text is written) is in error. The
for the problem. If no fix exists, contact the IBM Support
VRA will contain the LOGON help panel
Center.
address and offset being accessed in the
panel. Source: Time Sharing Option Extensions (TSO/E)
2C Either installation exit IKJEFLN1 or installation
exit IKJEFLN2 validated the account number 01D
field on the LOGON panel for a user defined
Explanation: During processing of a DSPSERV or
only in the UADS data set, but the exit did not
HSPSERV macro, the system found a
supply a procedure name.
non-environmental error. The macro processing failed.
System action: The system ends the TSO/E LOGON Register 15 contains a hexadecimal reason code.
attempt. The system writes an ABEND dump.
| For the reason codes presented with format xxzzNNxx,
Operator response: Notify the system programmer. | zz must be one of:
System programmer response: If the problem recurs | v 07 for CREAD
and if the program is not in error, search problem | v 08 for CWRITE
reporting data bases for a fix for the problem. If no fix | v 09 for SREAD
exists, contact the IBM Support Center.
| v 0A for SWRITE
Source: Time Sharing Option Extensions (TSO/E) | v FE if the service that is requested cannot be
| determined
01B | When zz is not one of those values, such as 00, those
Explanation: An error occurred during RACONVRT | reason codes do not apply.
processing; the following hexadecimal reason codes Code Explanation
provide further information about the error:
xxzz07xx The CREAD or CWRITE request
Code Explanation failed because the caller was
04 The RACROUTE macro returned an unauthorized.
unexpected return code.
Chapter 2. System Completion Codes 15
01D
xxzz08xx The indicated address space does not xxzz18xx The SWRITE request failed because
exist or cannot be accessed by the the caller issued it against Hiperspace
caller. storage while a DIV SAVE macro was
active.
xxzz09xx The indicated Hiperspace™ does not
exist or cannot be accessed by the xxzz19xx The HSPSERV macro failed because
caller. This could be caused by the an unauthorized caller requested it
owner of the Hiperspace being against a shared standard Hiperspace
swapped out. without supplying an access list entry
token. (ALET).
xxzz0Axx The system does not recognize the
macro request. xxzz1Axx The supplied access list entry token
(ALET) does not belong to the
xxzz0Bxx A storage key violation occurred on
Hiperspace as indicated by the
the specified Hiperspace virtual
specified STOKEN.
storage.
xx0001xx A problem-state program with PSW
xxzz0Cxx The caller did not issue a GETMAIN
key 8-F attempted either to create a
macro for the indicated address space
SCOPE=ALL or SCOPE=COMMON
virtual storage.
data space, a disabled reference
xxzz0Dxx A storage key violation occurred on (DREF) data space, or a non-fetch
the specified address space virtual protected data space, or to assign
storage. ownership of a Hiperspace to another
task.
xxzz0Exx The specified address space virtual
storage did not start on a 4-kilobyte xx0002xx A supervisor-state caller attempted to
boundary or was not within the create a data space on behalf of an
bounds of the private area. owner that is not in the caller’s home
or primary address space.
xxzz0Fxx The specified Hiperspace virtual
storage did not start on a 4-kilobyte xx0003xx A service request block (SRB) mode
boundary or was not within the request did not specify the owner of
bounds of the Hiperspace. the data space or Hiperspace.
xxzz10xx The SREAD or SWRITE request failed xx0004xx The caller requested that a storage
because it was issued against key be assigned to the data space,
address space virtual storage that but the caller was not in supervisor
maps a data-in-virtual object, but the state.
storage is virtual I/O (VIO) storage,
xx0008xx The system did not create a data
fixed, or part of a disabled reference
space because the designated owner
(DREF) subpool.
does not exist.
xxzz11xx The caller specified a value for
xx000Axx The problem-state program with PSW
NUMRANGE that was not in the
key 8-F attempted to prefix the data
acceptable range.
space name with “SYS”, which is
xxzz12xx The SREAD or SWRITE request failed reserved for system use.
because the caller was in
xx000Bxx The caller specified an incorrect
cross-memory mode.
number of blocks for the data space
xxzz13xx The SREAD or SWRITE request failed size.
because it was issued against an
xx000Dxx The specified data space name is not
ESO Hiperspace.
correct. It must be left-justified or
xxzz14xx The request failed because the caller non-blank, can contain only
is not in 31-bit addressing mode. alphabetic, numeric and national
characters, cannot start with a
xxzz15xx The specified parameter list or range numeric character, and must be
list is not accessible. padded on the right with blanks.
xxzz16xx The caller specified an incorrect xx000Exx A supervisor-state caller attempted to
parameter list version. prefix the data space name with
xxzz17xx The parameter list contains “SYSDS”, which is reserved for
inconsistent data or data that is not system use.
valid. xx000Fxx An unauthorized caller requested
creation of an ESO Hiperspace.
16 z/OS V1R10.0 MVS System Codes
01D
xx0011xx The parameter list is inconsistent. ownership to a task other than the
caller’s task or the caller’s job step
xx0012xx An unauthorized caller requested
task.
creation of a shared standard
Hiperspace. xx010Dxx The caller attempted to delete a
Hiperspace while the Asynchronous
xx0013xx An problem-state program with PSW
Data Mover Facility (ADMF) was still
key 8-F tried to create a data space
processing a request to transfer data
and assign ownership of the data
to or from the Hiperspace.
space to a task that is neither the
caller’s own task nor the caller’s job xx010Exx The caller attempted to delete a data
step task. space which has one or more shared
segments.
xx0014xx The creation of a SCOPE=COMMON
data space failed because the caller xx0201xx The RELEASE request failed because
was swappable or because the the data space does not exist.
system detected that the owner of a
xx0202xx The RELEASE request failed because
SCOPE=COMMON data space has
the start address is not on a page
become swappable.
boundary.
xx0101xx The DELETE request failed because
xx0203xx The RELEASE request failed because
a problem program cannot specify
the input STOKEN is not valid.
TTOKEN.
xx0204xx The RELEASE request failed because
xx0102xx An authorized program specified a
the number of blocks is not valid.
TTOKEN that is not valid.
xx0205xx The RELEASE request failed because
xx0103xx An authorized program attempted to
the requested range of blocks is not in
delete a data space on behalf of an
the addressable range of the data
owner that is not its home or primary
space.
address space.
xx0206xx The RELEASE request failed because
xx0104xx A service request block (SRB) mode
the problem program caller attempted
request failed because it did not
to release a SCOPE=ALL or
specify a TTOKEN, which is required
SCOPE=COMMON data space.
to determine the owner.
xx0207xx The RELEASE request failed because
xx0105xx A specified STOKEN does not
the problem-state program tried to
represent a valid data space.
release storage in either a Hiperspace
xx0106xx The specified STOKEN’s owner (as it does not own or a SCOPE=SINGLE
specified by the TTOKEN) is not the data space it does not own or did not
owner of the data space. create, or to release a data space on
behalf of an owner that is not in its
xx0107xx The specified data space contains I/O
primary address space or is not the
defined pages.
current dispatching task.
xx0108xx The specified data space contains
xx0208xx The RELEASE request failed because
pages mapped by the DIV macro.
the supervisor state program
xx0109xx The specified data space contained attempted to release a private data
pages for which a DIV SAVE space on behalf of an owner that is
operation was in progress. not in the supervisor state’s home or
primary address space.
xx010Axx A problem program attempted to
delete a SCOPE=ALL or xx0209xx The RELEASE request failed because
SCOPE=COMMON data space. the caller is not in key 0, and the key
for the data space page did not match
xx010Bxx A problem program attempted to the caller’s key.
delete a SCOPE=SINGLE data space
that has a key different than the xx020Axx The RELEASE request failed because
caller’s key. the data space page is fixed, or fixed
in another view of a sharing group.
xx010Cxx A problem-state program with PSW
key 8-F tried to delete a xx020Bxx The RELEASE request failed because
SCOPE=SINGLE data space, created the caller was disabled and requested
by the caller’s task, that was assigned release of enabled reference storage.
Chapter 2. System Completion Codes 17
01D
xx020Cxx The RELEASE request failed because xx0403xx The DEFINE IOOFF request failed
the caller requested a page that is because the input STOKEN is not
READONLY. valid.
xx0213xx The RELEASE request failed because xx0404xx The DEFINE IOOFF request failed
the range list contains a non-zero because the number of blocks is less
value in one or more reserved fields. than one.
xx0301xx The DEFINE IOON request failed xx0405xx The DEFINE IOOFF request failed
because the data space does not because the requested addressable
exist. range of blocks is not in the data
space.
xx0302xx The DEFINE IOON request failed
because the start address is not on a xx0406xx The DEFINE IOOFF request failed
4-kilobyte boundary. because the caller was in problem
program state and not in system key.
xx0303xx The DEFINE IOON request failed
because the input STOKEN is not xx0407xx The DEFINE IOOFF request failed
valid. because the caller attempted to
DEFINE IOOFF for a
xx0304xx The DEFINE IOON request failed
SCOPE=SINGLE data space on
because the number of blocks is less
behalf of an owner that is not in the
than one.
caller’s home or primary address
xx0305xx The DEFINE IOON request failed space.
because the requested addressable
xx0408xx The DEFINE IOOFF request failed
range of blocks is not in the range of
because it was issued for a
the data space.
Hiperspace.
xx0306xx The DEFINE IOON request failed
xx040Cxx The DEFINE IOOFF request failed
because the caller was in problem
because the input range list contains
program state and not in system key.
a non-zero value in one or more
xx0307xx The DEFINE IOON request failed reserved fields.
because the caller attempted to
xx0501xx The specified STOKEN does not
DEFINE IOON for a SCOPE=SINGLE
represent a valid data space or
data space on behalf of an owner that
represents a data space for which the
is not in the caller’s home or primary
caller is not authorized.
address space.
xx0503xx The new current size exceeds the
xx0308xx The DEFINE IOON request failed
maximum size for the data space and
because the data space page has a
Hiperspace.
DIV SAVE operation in progress.
xx0601xx The DEFINE DREFON request failed
xx0309xx The DEFINE IOON request failed
because the data space does not
because it was issued for a
exist.
hiperspace.
xx0602xx The DEFINE DREFON request failed
xx030Bxx The DEFINE IOON request failed
because the start address is not on a
because the caller was disabled and
4-kilobyte boundary.
specified storage that was neither in a
disabled reference (DREF) state or an xx0603xx The DEFINE DREFON request failed
IOON state. because the input STOKEN is not
valid.
xx030Cxx The DEFINE IOON request failed
because the input range list contains xx0604xx The DEFINE DREFON request failed
a non-zero value in one or more because the number of blocks is less
reserved fields. than one.
xx0401xx The DEFINE IOOFF request failed xx0605xx The DEFINE DREFON request failed
because the data space does not because the requested addressable
exist. range of blocks extends beyond the
end of the data space.
xx0402xx The DEFINE IOOFF request failed
because the start address is not on a xx0606xx The DEFINE DREFON request failed
4-kilobyte boundary. because the caller was not in
supervisor state.
18 z/OS V1R10.0 MVS System Codes
01D
xx0607xx The DEFINE DREFON request failed scope single data space on behalf of
because the caller attempted to use an owner that is not in its home
DREFON against storage in a address space.
scope-single data space on behalf of
xx0B09xx An OUT failed because the data
an owner that is not in the home or
space is a Hiperspace.
primary address space.
xx0C01xx A LOAD failed because the data
xx0608xx The DEFINE DREFON request failed
space does not exist.
because the data space page has a
DIV SAVE operation in progress. xx0C02xx A LOAD failed because the start
address is not on a page boundary.
xx0609xx The DEFINE DREFON request failed
because the input STOKEN is for a xx0C03xx A LOAD failed because the input
Hiperspace. STOKEN is not valid.
xx060Axx The DEFINE DREFON request failed xx0C04xx A LOAD failed because the number of
because the specified area is part of a blocks is not valid.
data space that was created with a
disabled reference (DREF) attribute. xx0C05xx A LOAD failed because the requested
range of blocks is not in the range of
xx060Bxx The DEFINE DREFON request failed the data space.
because the caller was disabled and
specified storage that was neither in a xx0C06xx A LOAD failed because the problem
disabled reference (DREF) state nor program caller attempted to LOAD a
an IOON state. SCOPE ALL or SCOPE COMMON
data space.
xx060Cxx The DEFINE DREFON request failed
because the input range list contains xx0C07xx A LOAD failed because the problem
a non-zero value in one or more state program caller attempted to load
reserved fields. a data space on behalf of the data
space owner, but the data space is
xx060Dxx The requestor tried to DEFINE not in the owner’s primary address
DREFON for a data space with space.
shared segments.
xx0C08xx A LOAD failed because the supervisor
xx071Bxx CREAD processing detected a state program attempted to load a
PGSER fix in progress for the address scope single data space on behalf of
space virtual storage. the data space owner, but the data
space is not in the owner’s home
xx0B01xx An OUT failed because the data
address space.
space does not exist.
xx0C09xx A LOAD failed because the data
xx0B02xx An OUT failed because the start
space is a Hiperspace.
address is not on a page boundary.
xx0D01xx The DEFINE DREFOFF failed
xx0B03xx An OUT failed because the input
because the data space does not
STOKEN is not representing a caller’s
exist.
data space.
xx0D02xx The DEFINE DREFOFF failed
xx0B04xx An OUT failed because the number of
because the start address is not on a
blocks is not valid.
4-kilobyte boundary.
xx0B05xx An OUT failed because the requested
xx0D03xx The DEFINE DREFOFF failed
range of blocks is not in the range of
because the input STOKEN is not
the data space.
valid.
xx0B06xx An OUT failed because the problem
xx0D04xx The DEFINE DREFOFF failed
program caller attempted to OUT a
because the number of blocks is less
SCOPE ALL or SCOPE COMMON
than one.
data space.
xx0D05xx The DEFINE DREFOFF failed
xx0B07xx An OUT failed because the problem
because the requested addressable
program caller attempted to OUT a
range of blocks is not in the range of
data space on behalf of an owner that
the data space.
is not in its primary address space.
xx0D06xx The DEFINE DREFOFF failed
xx0B08xx An OUT failed because the supervisor
because the caller was not processing
state program attempted to OUT a
Chapter 2. System Completion Codes 19
01F
in supervisor state with a system specified an input range list for a
program status word (PSW) key. service that does not support a range
list.
xx0D07xx The DEFINE DREFOFF failed
because the caller attempted to xxFF0Bxx The request failed because the caller
DEFINE DREFOFF a SCOPE specified an incorrect value for
SINGLE or data space on behalf of an NUMRANGE. It must be greater than
owner that is not in its home or zero.
primary address space.
xxFF0Cxx The request failed because the caller
xx0D09xx The DEFINE DREFOFF failed specified a value for NUMRANGE that
because the input STOKEN is for a exceeded the maximum of 16 for an
Hiperspace. unauthorized caller.
xx0D0Axx The DEFINE DREFOFF failed xxFF0Dxx The request failed because the caller
because the specified area is part of a specified an input range list that is not
data space that was created with the accessible to the service using the
disabled reference attribute. caller’s PSW key.
xx0D0Dxx The requestor tried to DEFINE xxFF10xx The DEFINE request failed because
DREFOFF for a data space with IOON or IOOFF was incorrectly
shared segments. coded.
xx0D0Exx A DSPSERV DEFINE DREFOFF is System action: The system sends messages about
issued with FORCE option. The option the job to the job log, writes an ABEND dump for the
is no longer supported. failing job step, and writes the JCL and SYSOUT output
for the job.
xxFF01xx The DSPSERV macro request failed
because a secondary address space Application Programmer Response: If the caller was
identifier (ASID) is not valid. an application program, correct the program and run the
job again.
xxFF02xx The request failed because the caller
held locks but indicated System programmer response: If the caller was
DISABLED=NO. provided by the installation, correct it. Look at
accompanying messages in the job log, the JCL and the
xxFF03xx The DSPSERV macro request failed
SYSOUT output.
because the caller issued a macro
version that is not valid. If the caller was an IBM-supplied program, search
problem reporting data bases for a fix for the problem. If
xxFF04xx The DSPSERV macro request failed
no fix exists, contact the IBM Support Center. Provide
because reserved fields in the macro
the messages, the JCL, the SYSOUT output, and the
parameter list are not zeros.
ABEND dump.
xxFF05xx The DSPSERV macro request failed
Source: Real storage manager (RSM)
because the caller requested an
unknown service.
01F
xxFF06xx The DSPSERV macro request failed
because a protection exception Explanation: A unit of work attempted to end without
occurred while referencing the caller’s removing all its entries from the linkage stack. A
parameter list. hexadecimal reason code in register 15 explains the
abend:
xxFF07xx The DSPSERV macro request failed
because the caller must be in 31-bit Code Explanation
addressing mode to use any service
04 The unit of work issued an EXIT macro (SVC
of the DSPSERV macro.
3) without unstacking the linkage stack entries
xxFF08xx The request failed because the caller of the corresponding request block (RB).
was disabled but requested a service
08 An RB routine did not unstack the linkage
that requires the caller to be enabled.
stack entries it had added.
xxFF09xx The request failed because the caller
System action: The system abends the task and may
held one or more locks needed by the
write a dump.
system to process the request.
Operator response: If the system programmer asks
xxFF0Axx The request failed because the caller
for an SVC dump, set the following SLIP trap:
SLIP SET,COMP=01F,ACTION=SVCD,MATCHLIM=1,END
20 z/OS V1R10.0 MVS System Codes
020 • 022
System programmer response: Do the following:
021
1. If an SVC dump is not produced with the abend, ask
the operator to set a SLIP trap to obtain an SVC Explanation: A task management macro passed an
dump. address space control block (ASCB) address with an
error indicated in the following reason codes:
2. In the system trace, find an SVC D or SVCE D entry
for abend X'01F'. Use this entry to determine which Code Explanation
address space and task control block (TCB) was
00 High order bits are set on in the input ASCB for
active at the time of error. Note the address space
move or add processing.
identifier (ASID).
3. Look at the linkage stacks for the TCBs associated 04 ASCBNOQ bit is off in the ASCB for add
with the active address space. processing.
4. Determine which linkage stack entries were not 08 Attempt to add, move or delete the master
unstacked by examining the entries on the stack scheduler address space.
after the entry with the unstack suppression bit set
on. The high-order bit of the linkage stack entry 0C Acronym check for the input ASCB fails.
descriptor (LSED) is the unstack suppression bit. 10 Incorrect CHAP entry function code.
5. Identify the module that failed to remove its linkage
14 Incorrect EXTENDED MOVE function code.
stack entries by using the program status word
(PSW) address associated with the unstacked 18 Incorrect EXCNT count passed from the
linkage stack entry. system.
v If the module is not an IBM module, continue 1C Acronym check for the input enclave control
diagnosis with the module. block fails.
v If the module is an IBM module, search problem
System action: The system abnormally ends the
reporting data bases for a fix for the problem. If
program that issued the macro, writes a logrec data set
no fix exists, contact the component group
error record, and writes a dump.
associated with this module at the IBM Support
Center. Provide all data collected and, if available, Application Programmer Response: When calling
the logrec data set error record. the routine, ensure that the high-order byte of the ASCB
address is set to zero. Correct the error. Run the job
Source: Supervisor control
again.
System programmer response: Collect all printed
020
output and output data sets related to the problem.
Explanation: The error occurred during processing of Search problem reporting data bases for a fix for the
a BDAM OPEN macro instruction. problem. If no fix exists, contact the IBM Support
Center. Provide the logrec data set record and the
The control program found that the DCBMACRF field of
dump.
the data control block did not contain an A, K, or I, or an
attempt was made to open a BDAM data set that Source: Task management
contained zero extents.
System action: The system ends the task. 022
Application Programmer Response: In the first case, Explanation: The vector processing subsystem
make sure that A, K, or I is specified in the MACRF support (VPSS) encountered a missing device end
operand of the DCB macro instruction. Verify that the condition on control port 0. The VPSS cannot continue
DCBMACRF field was correctly modified by the problem processing or respond to operator commands.
program before the opening process. After making
System action: The VPSS missing interruption
corrections, reassemble the program and run the job
handler exit abnormally ends the VPSS monitor address
step again.
space with system completion code X'022'. The system
In the second case, create the data set before issues message IGF991I to identify the 3838 Array
attempting to open it as a BDAM file. Processor that caused the VPSS monitor address
space to end. The system writes a logrec data set error
System programmer response: If the error recurs
record.
and the program is not in error, look at the messages in
the job log for more information. Search problem Operator response: Contact hardware support.
reporting data bases for a fix for the problem. If no fix
Application Programmer Response: Determine why
exists, contact the IBM Support Center. Provide the JCL
the 3838 Array Processor is not responding with a
and the program listing for the job.
device end. You may let the system operator restart the
Source: DFSMSdfp
Chapter 2. System Completion Codes 21
023
VPSS so that the operator may enter VPSS commands 00000009 While LLA was building a new LLA
for other 3838 devices. directory, LLA reached the physical
end of the PDS directory before
Source: Vector processing
finding the last PDS directory block.
The last block must have a record key
023 of X'FFFFFFFFFFFFFFFF'.
Explanation: LNKLST or library lookaside (LLA) 0000000A While LLA was building a new LLA
encountered an error that prevented LLA from directory, the directory for an
completing some processing. LLA issues other contents LLA-managed data set contained too
supervision (CSV) messages with the abend code. many directory entries for LLA to fit
When more than one abend has occurred, LLA includes into its available virtual storage.
the original abend and reason code in the message or
0000000B LLA failed unexpectedly.
messages it issues for the sequence of abends.
00000014 An I/O error occurred during LLA
The hexadecimal reason code that describes the cause
processing.
of the abend is one of the following:
00000015 A media error occurred during LLA
Code Explanation
processing.
00000001 While LLA was copying directory
00000016 An error occurred during data set
entries from a LNKLST library to build
processing.
a new LLA directory, dynamic
allocation or unallocation failed. 00000017 An error occurred during SMS
processing.
00000002 While LLA was copying directory
entries from a LNKLST library to build 00000018 SMS failed to obtain required
a new LLA directory, OPEN failed. resources.
00000003 While LLA was building a new LLA 00000019 An error occurred during LLA
directory, LLA found a partitioned data processing.
set (PDS) directory block with a
00000100 During LLA address space
record key equal to
initialization processing, the ATTACH
X'0000000000000000'.
of LLA’s resource manager subtask
00000004 While LLA was building a new LLA failed.
directory, LLA found a PDS directory
00000101 LLA address space initialization
block with an incorrect record key; the
processing determined that the LLA
PDS directory block that contained the
fetch installation exit CSVLLIX1 was
final PDS directory entry did not have
not reentrant.
the correct record key of
X'FFFFFFFFFFFFFFFF'. 00000102 LLA detected that its resource
manager subtask abnormally ended.
00000005 While LLA was building a new LLA
directory, LLA found a PDS directory 00000103 LLA fetch installation exit CSVLLIX1
entry with the name was AMODE 24.
X'0000000000000000'.
00000201 While building a new LLA directory,
00000006 While LLA was building a new LLA LLA failed while making a table of
directory, LLA found a PDS directory PDS or PDSE directory entries from
block whose given length was too the directory of an LLA-managed data
small to contain an integral number of set.
PDS directory entries.
00000202 LLA failed while building an index for
00000007 While LLA was building a new LLA a new LLA directory.
directory, LLA found a PDS directory
block for which both of the following 00000203 While building a new LLA directory,
were true: LLA found no modules in the LNKLST.
v The block did not contain the final 00000204 LLA directory build processing of the
directory entry in the directory list of data sets to be managed by
v The block’s record key differed from LLA failed unexpectedly.
the name of the last PDS directory
entry in the block. 00000205 LLA directory build processing failed
because incorrect data was detected
00000008 While LLA was building a new LLA while parsing the LLA parmlib member
directory, LLA had an I/O error. CSVLLAxx.
22 z/OS V1R10.0 MVS System Codes
023
00000206 LLA directory build processing failed contains the control statements
because LLA failed unexpectedly needed to perform the LLA directory
while parsing the LLA parmlib member update.
CSVLLAxx.
00000A04 LLA directory refresh processing failed
00000207 LLA directory build processing failed unexpectedly while parsing the LLA
because LLA failed unexpectedly parmlib member CSVLLAxx, which
while processing a refresh request for contains the control statements
specific members of an LLA-managed needed to perform the LLA directory
data set. update.
00000208 During LLA MVS operator command 00000A05 LLA was unable to refresh a PDSE
processing, the user did not have library.
proper security authorization facility
00000A50 LLA’s cross memory directory access
(SAF) and security product (RACF)
routine was entered with incorrect
authorization to an LLA parmlib data
parameters.
set resource.
00000B00 LLA module staging processing did
00000401 Dynamic allocation (SVC 99) failed.
not convert a floating point number to
LLA may have been:
64-bit unsigned binary because the
v Allocating an LLA-managed data
number was less than one.
set to read its directory to build a
new LLA directory. 00000B01 LLA module staging processing was
v Allocating an LLA-managed data unable to convert a floating point
set to copy modules from it while number to 64-bit unsigned binary
staging modules. because the number was too big to be
v Allocating SYS1.parmlib or another represented by 64 bits.
parmlib data set to process an LLA
start or update request. 00000B02 LLA module staging processing was
v Unallocating a data set that LLA unable to convert a floating point
had previously allocated. number to 64-bit unsigned binary
because the number was not
00000500 Dynamic allocation or unallocation normalized.
failed while LLA was staging modules
for an LLA-managed library into the 00000B50 An incorrect LLPM parameter area
virtual lookaside facility (VLF) data has been passed to the LLA search
space. routine.
00000501 The LLA staging installation exit 00000B51 The LLA search routine was called
CSVLLIX2 was AMODE 24. from a program which was not running
under an supervisor request block
00000A00 While LLA was obtaining PDS (SVRB).
directory entries for an LLA-managed
data set during a selective module 00000B52 The LLA search routine was called
refresh, BLDL returned with a return with an incorrect DEB as input.
code greater than 4. 00000B53 The LLA search routine was called
00000A01 LLA directory refresh processing could with an incorrect value in LLPPCNCT.
not obtain sufficient storage to hold all 00000C00 The pointer to LLA’s component trace
the PDS directory entries accumulated buffer was outside of the projected
from selective LLA directory refreshes. storage range for the buffer.
00000A02 LLA directory update processing failed 00000D00 LLA directory build processing failed
while reading the LLA parmlib member unexpectedly while processing the
CSVLLAxx, which contains the control LLA parmlib member CSVLLAxx.
statements needed to perform the
LLA directory update. The parmlib 00000D01 LLA directory update processing failed
read routine detected that the input while reading the LLA parmlib member
parameter list contained incorrect CSVLLAxx, which contains the control
data. statements needed to perform the
LLA directory update. The parmlib
00000A03 LLA directory refresh processing failed read routine detected that the input
unexpectedly while reading the LLA parameter list contained incorrect
parmlib member CSVLLAxx, which data.
Chapter 2. System Completion Codes 23
023
00000D02 LLA directory refresh processing failed macro with an incorrect DCB
unexpectedly while reading the LLA parameter. The DCB does not point to
parmlib member CSVLLAxx, which a valid DEB.
contains the control statements
00001202 The caller invoked an LLACOPY
needed to perform the LLA directory
macro whose DCB references a data
update.
set for which the user does not have
00000D03 LLA directory refresh processing failed proper SAF security (RACF)
unexpectedly while parsing the LLA authorization.
parmlib member CSVLLAxx, which
00001203 The caller invoked an LLACOPY
contains the control statements
macro with a zero DCB parameter.
needed to perform the LLA directory
update. 00001204 The caller invoked an LLACOPY
macro with an incorrect level
00000D05 LLA directory refresh processing failed
parameter list or non-zero reserved
unexpectedly while allocating the LLA
fields.
parmlib member CSVLLAxx, which
contains the control statements 00001205 The user invoked an LLACOPY macro
needed to perform the LLA directory while in problem state.
update. The allocation was performed
using the IEFPRMLB service. A 00001206 CSVLLCPY was called with an invalid
previous message issued by the DCB - data set not PDS(E).
IEFPRMLB service accompanies this System action: If the LLA address space ends
ABEND. because of this error, the system usually attempts to
00000E01 While LLA was building a new LLA restart LLA in another address space. LLA issues one
directory, dynamic allocation or or more of the following messages: CSV222I,
unallocation failed. CSV226E, CSV227I, CSV247I.
00000E02 While LLA was building a new LLA If the failed LLA address space had not become active
directory, OPEN failed. and had been created to recover from a prior LLA
address space failure, the system issues message
00000E03 While LLA was building a new LLA CSV218E without restarting LLA.
directory, LLA found no data sets to
manage. Specific system actions for each reason code are as
follows:
00000E04 While LLA was building a new LLA
directory, LLA found that a data set to Code System Action
be managed by LLA was not a PDS. 00000001 This error was preceded by an abend
00000E05 While LLA was building a new LLA for which LLA took an SVC dump and
directory, LLA found that FREEZE or recorded the error in logrec data set.
NOFREEZE was specified for a If SVC 99 itself failed, LLA issues
non-LLA data set. abend X'023', reason code
X'00000401', and message CSV224I.
00000E06 During LLA MVS operator command If this error occurred during an initial
processing, the user did not have LLA directory build, LLA also issues
proper SAF and security product abend X'023', reason code
(RACF) authorization to an X'00000201', to end its address
LLA-managed data set resource. space.
00000E07 While LLA was building a new LLA 00000002 through 00000019
directory, LLA found that a data set to DFSMS™ may take an SVC dump.
be managed by LLA was a PDSE that LLA records this error in the logrec
was not known to be a load library. data set. The indicated library will not
Make sure that the data set was not be processed. LLA issues message
empty and had at least one program CSV221I or CSV247I, which contains
object in it. this reason code in its message text.
If this error occurred during an initial
00001200 The caller invoked an LLACOPY
LLA directory build, LLA also issues
macro with an incorrect data control
abend X'023', reason code
block (DCB) parameter.
X'00000201', to end its address
00001201 The caller invoked an LLACOPY space.
00000100 LLA takes an SVC dump and records
this error in the logrec data set. The
24 z/OS V1R10.0 MVS System Codes
023
next system action depends on what message CSV217I and keeps the old
release you are using; for MVS/SP™ directory active. Otherwise, the LLA
3.1, the LLA address space ends. For address space ends.
MVS/SP 3.1.0 or higher, LLA
00000208 If the error occurred during an LLA
continues processing without its
directory refresh, LLA issues CSV217I
resource management subtask until it
and keeps the old directory active. If
determines if the reattach threshold
the error occurred during an initial
has been reached. If the threshold
directory build, LLA issues abend
has not been reached, LLA attempts
X'023', reason code 204, to end its
to reattach the subtask. Otherwise,
address space.
LLA continues processing without its
resource management subtask. 00000401 LLA issues message CSV224I, which
includes dynamic allocation’s specific
00000101 LLA initialization issues message
error and information codes. LLA
CSV232I, and continues processing
takes an SVC dump and records the
as if CSVLLIX1 was not installed in
error in logrec data set. LLA’s
the LNKLST.
subsequent actions depend on the
00000102 LLA’s resource management subtask task LLA was performing when the
abnormally ends, and then the LLA dynamic allocation was requested:
address space also abnormally ends. v For MVS/SP 3.1, if LLA was
00000103 LLA initialization issues message allocating a data set to read its
CSV232I, and continues processing directory to build a new directory,
as if CSVLLIX1 was not installed in then LLA issues message
the LNKLST. CSV221I. If the error occurred
during an LLA directory refresh,
00000201 For dynamic allocation errors, LLA LLA also issues message CSV217I
issues message CSV224I; for PDS and keeps the old directory active.
related I/O errors, LLA issues If the error occurred during an initial
message CSV225I, for PDSE related directory build, LLA issues abend
errors, LLA issues message CSV247I. X'023', reason code X'00000201', to
In any case, LLA issues message end its address space.
CSV221I to show how far the LLA
v For MVS/SP 3.1.0e or higher, if
directory build had progressed prior to
LLA was allocating a data set to
the error, and includes a reason code
read its directory to build a new
that identifies the specific error. Then,
directory, then LLA issues message
if the error occurred during an LLA
CSV241I. If the error occurred
directory refresh, LLA issues CSV217I
during an LLA directory refresh,
and keeps the old directory active.
LLA also issues message CSV217I
Otherwise, the LLA address space
and keeps the old directory active.
ends.
If the error occurred during an initial
00000202, 00000204, 00000206, 00000207 directory build, LLA issues abend
For the original abend that LLA X'023', reason code X'00000204', to
detected, LLA takes an SVC dump end its address space.
and records the error in the logrec v If LLA was allocating a data set to
data set. LLA then issues this abend. copy modules from it while staging
If the error occurred during initial build modules, then LLA does not stage
processing, LLA ends its address modules from this library.
space. Otherwise, LLA keeps the old
v If LLA was allocating a parmlib data
directory active.
set to process a start LLA request,
00000203 LLA takes an SVC dump and records LLA issues message CSV235I,
the error in the logrec data set. Then, CSV236I, and does not start the
if the error occurred during an LLA LLA address space.
directory refresh, LLA issues CSV217I v If LLA was allocating a parmlib data
and keeps the old directory active. set to process a LLA refresh
Otherwise, the LLA address space request, LLA issues message
ends. CSV235I, CSV236I and keeps the
00000205 LLA issues message CSV235I, old directory active.
CSV236I. If the error occurred during
an LLA directory refresh, LLA issues
Chapter 2. System Completion Codes 25
023
v If LLA was unallocating a data set the error in the logrec data set. Then,
that it had previously allocated, LLA trace is deactivated, and LLA
then LLA takes no further action. continues without component trace
capabilities.
00000500 If SVC 99 itself failed, LLA issues
abend X'023', reason code 401, and 00000D00, 00000D01, 00000D02, 00000D03
message CSV224I. LLA’s subsequent LLA takes an SVC dump and records
actions depend on what release you the error in the logrec data set. If the
are using. error occurred during an LLA directory
refresh, LLA issues message
For MVS/SP 3.1, this error was
CSV217I and keeps the old directory
preceded by an abend for which LLA
active. Otherwise, the LLA address
took an SVC dump and recorded the
space ends.
error in the logrec data set. LLA’s
resource manager subtask ends, 00000E01 LLA issues message CSV224I, which
causing the LLA address space to includes dynamic allocation’s specific
end. error and information codes. If the
error occurred while allocating the
For MVS/SP 3.1.0e or higher, LLA’s
data set, LLA issues message
resource manager subtask ends and
CSV241I which includes the name of
LLA continues processing without its
the data set which could not be
resources management subtask until it
allocated. If the error occurred during
determines if the reattach threshold
an LLA directory refresh, LLA also
has been reached. If the threshold
issues message CSV217I and keeps
has not been reached, LLA attempts
the old directory active. If the error
to reattach the subtask. Otherwise,
occurred during an initial directory
LLA continues processing without its
build, LLA issues abend X'023',
resource management subtask.
reason code X'204' to end its address
00000501 LLA issues message CSV232I, and space.
continues processing as if CSVLLIX2
00000E02 LLA issues message CSV240I, which
was not installed in the LNKLST.
includes the name of the data set
00000A00 through 00000A05 which could not be opened. This error
LLA takes an SVC dump and records is preceded by an abend for which
the error in the logrec data set. Then, LLA takes an SVC dump and records
LLA issues message CSV217I, and this error in the logrec data set. If the
does not perform the requested LLA error occurred during an LLA directory
refresh. refresh, LLA also issues message
CSV217I and keeps the old directory
00000A50 If the caller is LLA or BLDL, the caller active. If the error occurred during an
takes an SVC dump and records the initial directory build, LLA issues
error in the logrec data set. Then, the abend X'023', reason code X'204' to
caller ends the LLA address space end its address space.
with an abend 312.
00000E03 If the error occurred during an LLA
00000B00 through 00000B02 directory refresh, LLA also issues
LLA takes an SVC dump and records message CSV217I and keeps the old
the error in the logrec data set. Then, directory active. If the error occurred
LLA’s resource manager subtask during an initial directory build, LLA
ends, and LLA also issues abend issues abend X'023', reason code 204
X'023', reason code X'00000102', to to end its address space.
end its address space.
00000E04 LLA issues message CSV242I, which
00000B50, 00000B51, 00000B52, 00000B53 includes the name of the data set
If the caller is BLDL, the caller takes which is not a PDS. If the error
an SVC dump, records the error in the occurred during an LLA directory
logrec data set. and abends the caller refresh, LLA also issues message
with a X'212' abend. If the caller is CSV217I and keeps the old directory
LLA, the caller takes an SVC dump, active. If the error occurred during an
records the error in the logrec data initial directory build, LLA issues
set, and provides the module using abend X'023', reason code X'204' to
program fetch. end its address space.
00000C00 LLA takes an SVC dump and records 00000E05 LLA issues message CSV245I, which
26 z/OS V1R10.0 MVS System Codes
023
includes the name of the data set for 00000203 Verify that the catalog for the LNKLST
which FREEZE or NOFREEZE was data sets is valid and has not been
specified. If the error occurred during overlaid.
an LLA directory refresh, LLA also
00000208 Ensure that the person who issues the
issues message CSV217I and keeps
LLA operator command has proper
the old directory active. If the error
RACF authorization (update) to the
occurred during an initial directory
LLA-managed data sets.
build, LLA issues abend X'023',
reason code X'204', to end its address 00000501 Make sure that the LLA staging
space. installation exit, CSVLLIX2, is AMODE
31 or AMODE ANY, and then link edit
00000E06 If the error occurred during an LLA
the exit again.
directory refresh, LLA issues CSV217I
and keeps the old directory active. If 00000A00 Follow the programmer response for
the error occurred during an initial CSV217I, and see the logrec data set,
directory build, LLA issues abend which may contain information on
X'023', reason code 204, to end its specific I/O errors. If no specific I/O
address space. error is evident, then stop and restart
LLA.
00000E07 LLA issues message CSV242I which
includes the name of the data-only or 00000A01 Follow the programmer response for
empty PDSE. If the error occurred CSV217I, and issue a complete LLA
during an LLA directory refresh, LLA refresh.
also issues message CSV217I and
keeps the old directory active. If the 00000A50 through 00000B02
error occurred during an initial Restart LLA.
directory build, LLA issues abend 00000B50, 00000B51, 00000B52, 00000B53
X'023', reason code X'00000204' to Respond to any related messages
end the address space. that appear in the system log
00001200 LLACOPY abends. (SYSLOG) and to any related abends.
Follow the programmer response for a
00001201 LLACOPY abends. X'212' abend.
00001202 LLACOPY abends. 00000C00 To regain component trace
capabilities, stop and then restart LLA.
00001203 LLACOPY abends.
00000E03 Verify that the parmlib members
00001204 LLACOPY abends.
specifying the list of data sets LLA is
00001205 LLACOPY abends. to manage is correct. Follow the
programmer response in for
00001206 LLACOPY abends.
messages CSV217I or CSV218I.
Operator response: Contact hardware support.
00000E06 Ensure that the person who issued
Application Programmer Response: Follow the the LLA operator command has
application programmer response for accompanying proper RACF authorization (update) to
CSV messages issued both to the console and the the LLA-managed data sets.
system log (SYSLOG). Follow the application
00000E07 Eliminate the PDSE data-only library
programmer response for any other accompanying
from the specified parmlib member.
abends.
00001200 Correct the DCB input parameter for
For the reason codes below, do the following:
the LLACOPY macro. Make sure that
Code Response the input DCB has been opened and
that the DCB is not being overlaid.
00000101 Make sure that the LLA fetch Run the job step again.
installation exit, CSVLLIX1, is
reentrant, and then link edit the exit 00001201 Correct the DCB input parameter for
again. the LLACOPY macro. Make sure that
the input DCB has been opened, and
00000103 Make sure that the LLA fetch that the DCB is not being overlaid and
installation exit, CSVLLIX1, is AMODE points to a valid DEB. Run the job
31 or AMODE ANY, and then link edit step again.
the exit again.
00001202 Ensure that the invoker of the
LLACOPY macro has sufficient RACF
Chapter 2. System Completion Codes 27
024 • 026
authority to the data sets described by Source: PSF for OS/390®
the LLACOPY input DCB. Run the job
step again.
025
00001203 Correct the DCB input parameter of
Explanation: The system was initiating a piece of
the LLACOPY macro. The input DCB
work when a system error occurred. The reason code is
must be a valid opened DCB. Run the
in register 15 at the time the system issues the abend.
job step again.
Code Explanation
00001204 Ensure that all reserved fields are
zero. Ensure that the macro library 0002 The APPC Asynchronous_Manager callable
used to compile or assemble the service returned an error code to the initiator.
program invoking LLACOPY
corresponds to the target 0003 The system found too many parameters on the
environment. Run the job step again. job used to start the scheduler.
00001205 Ensure that the invoker of the 0004 The user tried to run the initiator under the
LLACOPY macro is supervisor state. initiator.
Run the job step again. Others The system found an internal error.
00001206 Ensure that the input DCB represents System action: The system writes an SVC dump,
a PDS or PDSE. Run the job step writes the logrec data set error records, and ends
again. initiator processing.
System programmer response: Follow the system System programmer response: Depending on the
programmer response for any messages issued to the reason code, do the following:
console or the job log and for any accompanying
abends. Code Response
If the problem persists and the program is not in error, 0002 Contact the IBM Support Center.
search problem reporting data bases for a fix for the 0003 Check the parameters on the job used to start
problem. If no fix exists, contact the IBM Support the scheduler.
Center. Provide the following:
0004 Rename the program that is causing the
v All printed output and output data sets related to the
abend.
problem.
v The program listing for the job. For all other reason codes, search problem reporting
v The JCL for the job. data bases for a fix for the problem. If no fix exists,
v The Logrec data set error record. contact the IBM Support Center. Provide the SVC dump
and the logrec data set error records.
Source: Contents supervision (CSV)
Source: Initiator/terminator
024
026
Explanation: The Print Services Facility™ (PSF)
ESTAE routine detected a PSF functional subsystem Explanation: Cross-system extended services (XES)
application (FSA) error. An FSA is the print driver encountered an error. See z/OS MVS Diagnosis:
application that executes within the PSF functional Reference for more information on diagnosing sysplex
subsystem (FSS). problems.
System action: Depending on the error condition, A hexadecimal reason code in register 15 explains the
PSF restarts the FSA or terminates the FSA. PSF error:
issues a message indicating the action taken and may Code Explanation
take a SVC dump.
0A060002 XES processing could not prevent
Operator response: Inform your system programmer SRB to task percolation however its
that this error occurred. processing has continued successfully
Application Programmer Response: None. and no action need be taken on the
part of the user.
System programmer response: Review the console
log for all PSF messages and, if any, the PSF abend 0C010101 Error in user’s Complete Exit. The
reason code. Refer to PSF for z/OS: Messages and connector will be terminated. Review
Codes for more information on the PSF messages, PSF the exit processing of the application.
abend reason code, and to determine the appropriate The issue a dump.
response for this error. 0C150101 Error in user’s Contention Exit. The
28 z/OS V1R10.0 MVS System Codes
026
connector will be terminated. Review terminated by the system. The system issues an SVC
the exit processing of the application. dump, unless the abend is related to the failure of a
The system does not issue a dump. user exit.
0C150103 Return code error from user’s Operator response: The following reason codes
Contention Exit. The user specified represent errors internal to the XES component. Call the
that the Contention Exit was to be IBM Support Center for assistance with these errors.
deferred during rebuild processing, but
the structure was not being rebuilt. Reason Codes:
The connector will be terminated.
Review the exit processing of the 02040001 020A0001 020D0001 02120001 03200001
application. The system does not 05010001 05060001 070B0001 07160001 081A0001
issue a dump. 09100001 09100002 09100003 09100004 0A010001
0A010002 0A010102 0A020102 0A040103 0A060101
0C340102 Error in user’s Complete Exit for a list 0A060103 0A090101 0A0D0001 0A0D0002 0A0D0004
or cache connection. The connection
0A060003 0A0D0101 0A130103 0A130104 0A130106
is terminated.
0A160001 0A160101 0A160102 0C080001 0C090001
0C3F0101 Error in user’s Notify Exit. The 0C090020 0C0A0001 0C0B0106 0C0C0105 0C0D0101
connector will be terminated. Review 0C0E0001 0C130101 0C170101 0C190001 0C1Cxxxx
the exit processing of the application. 0C1D0101 0C21xxxx 0C23xxxx 0C26xxxx 0C2A0001
The system does not issue a dump. 0C2A0002 0C2A0003 0C2A0004 0C2A0005 0C2A0006
0C2A0007 0C2A0008 0C2A0009 0C2A000A 0C2A000B
0C5A0003 XES processing could not prevent
0C2A000C 0C2A000D 0C2A000E 0C2A000F 0C2A0010
SRB to task percolation. However, its
0C2A0011 0C2A0012 0C2A0013 0C2A0014 0C2A0020
processing has continued successfully
0C2D0001 0C2F0101 0C2F0102 0C30xxxx 0C340001
and no action need be taken on the
0C340002 0C340101 0C340103 0C340104 0C340105
part of the user.
0C340106 0C380001 0C380002 0C380003 0C380004
0C5A0004 XES processing could not prevent 0C380005 0C380009 0C380106 0C380107 0C380108
SRB to task percolation. However, its 0C390001 0C391013 0C3C0107 0C3C0108 0C400101
processing has continued successfully 0C41xxxx 0C440101 0C460101 0C4A0101 0C4A0103
and no action need be taken on the 0C54xxxx 0C560002 0C540101 0C560001 0C560003
part of the user. 0C560004 0C560005 0C560150 0C5A0101 0C5A0102
0C5B1013 0C650001 0C670101 0C680102 0C6C0001
0C680101 Error in user’s Notify Exit. The
connector will be terminated. Review 0C700102 0C740101 0C740103 0C760102 0C7C0001
the exit processing of the application. 0C7C0002 0C7C0003 0C830001 0C830002 0C830003
The system does not issue a dump. 0C890101 0C890102 0C920002 0C950001 0C950102
0C950103 0C9E0001 0C9E0101 0D010001 0D010101
0E0A0101 Error in user’s List Transition Exit. The 0D010102 0D010103 0D010104 0D070101 0D070102
connector will be terminated. Review 0D070103 0D070104 0D070105 0D0C0001 0D0C0150
the exit processing of the application. 0D120101 0D120102 0D120103 0D120007 0D120008
The system does not issue a dump. 0D120150 0D150004 0D150101 0D150102 0D150103
0E0D0001 Unexpected return code from user’s 0D150150 0D180101 0D1C0001 0D1C0150 0E0A0102
Event Exit. Register 0 contains the 0E0B0004 0E0C0103 0E0D0102 0E0F0101 0E120001
event code (EEPLevent) presented to 0E130004 0E130101 0E130102 11050001
the user’s Event Exit. Register 2
contains the return code System programmer response:
(EEPLretcode) returned by the user’s
Event Exit. See IXLYEEPL mapping Format the SVC dump with the following IPCS
macro for EEPL fields. The connector subcommands:
will be terminated. Review the exit v XESDATA, including all the reports at all levels -
processing of the application. The summary, detail, and exception.
system does not issue a dump. v CTRACE COMP(SYSXES) SUB((GLOBAL))
0E0D0101 Error in user’s Event Exit. The v CTRACE COMP(SYSXES) SUB((individual-
connector will be terminated. Review connections))
the exit processing of the application. You can determine the individual connections by
The system does not issue a dump. issuing the CTRACE QUERY command to see the
System action: Additional messages explaining the sub name traces associated with SYSXES.
error may precede the ABEND. If there is a
hexadecimal value of ’01’ in the third byte of the reason
code the connector issuing the IXLCONN service will be
Chapter 2. System Completion Codes 29
027 • 029
Search problem reporting data bases for a fix for the v An I/O error occurred when the system attempted to
problem. If no fix exists, contact the IBM Support transfer data from a data-in-virtual object into a
Center. Provide the formatted SVC dump. mapped window page.
Source: Cross-system extended services (XES) v A reason for the abend code X'028' can be due to an
mmap() failure.
027 System action: The system abnormally ends the
current task or address space.
Explanation: The Print Services Facility (PSF) ESTAE
routine detected a PSF functional subsystem (FSS) Operator response: If the system issued message
error. An FSS is a PSF address space. IEA928I, see the operator response for that message.
Otherwise, notify the system programmer.
System action: PSF terminates the FSS and issues a
message indicating the action taken and may take a System programmer response: Look for messages
SVC dump. indicating a hardware error. If you find any, contact
hardware support. Search problem reporting data bases
Operator response: Inform your system programmer for a fix for the problem. If no fix exists, contact the IBM
that this error occurred. Support Center. The logrec data set error record might
Application Programmer Response: None. not contain information regarding this abend.
System programmer response: Review the console Source: Auxiliary storage manager (ASM) and real
log for all PSF messages and, if any, the PSF abend storage manager (RSM)
reason code. Refer to PSF for z/OS: Messages and
Codes for more information on the PSF messages, PSF 029
abend reason code, and to determine the appropriate
response for this error. Explanation: The auxiliary storage manager’s (ASM)
page operations starter routine detected an incorrect
Source: PSF for OS/390 virtual I/O (VIO) request.
The logrec data set error record contains the incorrect
028 VIO request reason code:
Explanation: The system could not complete a paging Code Explanation
operation for one of the following reasons:
0004 The requested VIO logical group number is
v A permanent I/O error occurred during a page-in or
greater than the maximum allowable logical
swap-in operation. The data being paged in or
group number.
swapped in is lost.
v A page cannot be accessed on auxiliary storage 0008 The requested VIO logical group number is not
because of a previous I/O error. assigned to any logical group.
v An indeterminable error occurred during management 000C The calling program does not have access to
of central storage paging. The system ends the requested VIO logical group.
processing. Register 15 may contain a reason code.
0010 The requested VIO logical group cannot accept
v The operator canceled a Time Sharing Option new work because work is already pending for
Extensions (TSO/E) user before the TSO/E logon that logical group.
completed.
0014 The requested VIO page number is greater
v An address space referred to a pageable link pack
than the number of pages in the VIO data set.
area (PLPA) page that contains noncontiguous code
or large constant areas. The system had already 0018 The requested VIO page does not exist.
detected this error and issued message IEA928I. See
message IEA928I. 0020 The system could not create tables in storage
for the requested VIO pages.
v The system found an unexpected error while
processing a swap-in or swap-out request. The error 0024 The requested VIO page previously suffered an
is described by a reason code in register 6. I/O error.
v The only current copy of a page resides in a 0028 The system does not contain a valid auxiliary
defective frame on expanded storage. An error storage copy of the requested VIO page.
occurred when the system tried to bring the page into
central storage from the defective expanded frame. System action: The system abnormally ends the
current task. The system writes a logrec data set error
v An I/O error occurred when the system wrote the
record.
page to auxiliary storage.
System programmer response: If the problem cannot
be resolved, search problem reporting data bases for a
30 z/OS V1R10.0 MVS System Codes
02A • 02C
fix for the problem. If no fix exists, contact the IBM produces a dump. For reason codes X'0000000C' and
Support Center. X'00000020', the system terminates the job step, and
produces a dump.
Source: Auxiliary storage manager (ASM) and
Allocation System programmer response: Obtain the program
listing for the job. Look at the messages in the job log. If
the JOB statement did not specify MSGLEVEL=(1,1),
02A
specify it and run the job again.
Explanation: An error occurred during execution of a
Verify that the problem program did not modify data
data management request for a spool data set. The
management control blocks or the JES2 UBUF control
hexadecimal reason code in Register 2 indicates the
block. For reason codes X'0000000C' and X'00000020',
cause of the abend:
also verify that the problem program used proper
Code Explanation serialization techniques for sharing a SYSIN, SYSOUT
or internal reader data set among multiple tasks. After
| 00000004 HASP Access Method found that a making corrections, execute the job step again.
| data management control block (ACB
| or DEB) was not valid. If the problem recurs and if the program is not in error,
search problem reporting data bases for a fix for the
| 00000008 HASP Access Method found that a problem. If no fix exists, contact the IBM Support
| JES2 UBUF was not valid. Center.
| 0000000C HASP Access Method detected a | In case of reason codes X’00000030’ through
| serialization error for a spool data set. | X’0000003C’, contact the IBM Support Center with
| 00000010 HASP Access Method found that | dump and SYSLOG.
| SETPRT failed when printing UBUF. Source: JES2
| 0000001C HASP Access Method detected
| inconsistent temporary protected 02B
| buffer pointers.
Explanation: A user exit routine issued a return code
| 00000020 HASP Access Method detected a that is higher than the maximum return code value
| serialization error for an internal specified in the MAXRC parameter of the $EXITnnn
| reader data set. macro instruction.
| 00000024 HASP Access Method detected a System action: The system abnormally ends the user
| JES2 internal logic error when task and issues a dump.
| processing an internal reader data set.
Operator response: Use the $TEXIT command to
| 00000028 HASP Access Method found nonvalid disable EXITnnn.
| extent in MTTR during PUT
| processing. System programmer response: Collect all printed
output and output data sets related to the problem.
| 0000002C HASP Access Method found a spool
| control record that is not valid during If the exit routine is issuing an incorrect return code,
| PUT processing. correct the routine. If the routine is issuing the correct
return code, change the maximum return code value
| 00000030 HASP Access Method detected an specified on the $EXITnnn macro instruction. Then
| error (loop condition) in HPUTFULL rerun the job.
| processing.
Source: JES2
| 00000034 HASP Access Method detected an
| error (loop condition) in HAMFIX
| processing. 02C
| 00000038 HASP Access Method detected an Explanation: An error occurred in JES2 support of a
| error (loop condition) in HAMSIO functional subsystem address space.
| processing.
When this system completion code appears without a
| 0000003C HASP Access Method detected an JES2 message, the following information applies:
| error in HCPBUFND processing.
During a hot start, either:
| 00000040 HASP Access Method found v HASPWARM found an active Functional Subsystem
| unauthorized use of authorized (FSS) with no active FSA
| request parameter list (RPL) option v JES2 found that the FSS address space was being
| during protected PUT processing. connected with no active FSA.
System action: The system ends the task, and System action: HASPWARM uses CALLRTM macros
Chapter 2. System Completion Codes 31
02D • 02E
to abnormally end the FSS address space. 2 The system could not find an
entry point in the nucleus.
Operator response: Enter a $S PRT command to
restart the FSS. 12 The system could not find a
load module.
Application Programmer Response: This condition
occurred because a functional subsystem printer either 18 The primary availability
was drained or started during a JES2 hot start. manager load module was
HASPWARM ended the FSS address space in case the not started by started task
printer initialization parameter was changed across hot control (STC).
start.
19 Incorrect parameters were
One of the following messages may also accompany received through the START
this system completion code: AVM command. The
$HASP413 availability manager checks
$HASP415 for one of the following
$HASP750 values in the AVMMODE
parameter: OPERATOR,
See z/OS JES2 Messages for more information.
THINLAYER, or RESTART.
Source: JES2
28,2A,2B,48 The availability manager
continues to run normally.
02D However, no additional
subsystems may connect to
Explanation: The JES2 main task has abnormally the availability manager until
terminated. One of the following events caused the an equal number of current
termination. subsystem users disconnect
v The operator issued a $PJES2,ABEND command, from it. The availability
which terminated JES2. manager reached the
v A JES2 catastrophic error/abend has occurred. For maximum number of
further details concerning the abend, see message subsystems that it can
$HASP095. handle.
System action: The system invokes JES2 34,35,37 The availability manager
recovery/termination processing. received an error return code
from the I/O supervisor. The
Operator response: Notify the system programmer. IOS return code is located in
System programmer response: To help you the third byte of the
determine the nature of the problem, refer to error availability manager reason
messages $HASP08 and $HASP095. code. The fourth byte of the
availability manager reason
Source: JES2 code contains an associated
IOS reason code. The error
02E indicator specifies which IOS
service the availability
Explanation: The system found an error during manager was trying to use:
availability manager (AVM) processing. One of the
following contains a reason code that explains the error: 34 PREVENTIO
v Register 15 in the SDWA or RTM2WA data areas at 35 IOPIDENT-
the time of the error. RELEASE
v The SDWACRC field in the SDWA data area. 37 IOPIDENT- OBTAIN
v Message AVM010E.
39 The availability manager
could not access subsystem
The reason code is in the form mmrrssss. owned storage to store the
results of a CALLAVM
In the reason code: request. Most likely, from the
mm The identifier for the availability manager entry time the availability manager
point that issued the abend verified the CALLAVM
request to the time it
rr A hexadecimal error indicator, which is one of completed the request, the
the following: subsystem has freed the
Indicator Explanation storage.
32 z/OS V1R10.0 MVS System Codes
030 • 031
The following error indicators specify an Application Programmer Response: Make sure that
internal error in the availability manager and, in a valid mode of operation is specified in the MACRF
most cases, cause abnormal ending of the operand of the DCB macro instruction. Verify that the
availability manager address space: DCBMACRF field was not incorrectly set up or modified
v 01 by the problem program. After making corrections,
v 03-11 reassemble the program and run the job step again.
v 13-17
System programmer response: If the error recurs
v 1A-27
and the program is not in error, look at the messages in
v 29
the job log for more information. Search problem
v 2C-33
reporting data bases for a fix for the problem. If no fix
v 38
exists, contact the IBM Support Center. Provide the JCL
v 3A-47
and the program listing for the job.
v 49
Source: DFSMSdfp
ssss The related system service completion codes
System action: The system abends the current task.
031
Operator response: Depending on the error indicator
Explanation: An I/O error occurred during processing
rr, do one of the following:
using QISAM. The control program attempted to pass
Indicator Response control to an error analysis (SYNAD) routine, but found
that (1) the DCBSYNAD field of the data control block
18 Do not try to start the availability
did not contain the address of a valid SYNAD routine, or
manager under an initiator. Use the
(2) the error occurred after a CLOSE macro instruction
START command.
was run by task end (the problem program returned
19 When you issue the START AVM control to the supervisor without processing a CLOSE
command, omit the AVMMODE macro instruction). The task was abnormally ended. The
parameter. DCBEXCD1 and DCBEXCD2 fields of the data control
block indicate the possible causes of the original error:
Otherwise, notify the system programmer. DCBEXCD1:
System programmer response: Depending on the Bit Explanation
error indicator rr, do one of the following:
0 Record not found.
Indicator
Response 1 Incorrect actual address for lower limit.
2 Ensure that the availability manager was 2 Space not found.
installed correctly. Ensure that the availability
3 Incorrect request.
manager’s load modules contain all the correct
CSECTs. 4 Uncorrectable input error.
12 Ensure that the availability manager was 5 Uncorrectable output error.
installed correctly. Ensure that the load libraries
6 Block could not be reached (input).
contain the correct load modules.
7 Block could not be reached (update).
34,35,37
Correct the failing program.
DCBEXCD2:
Source: Availability manager (AVM)
Bit Explanation
030 0 Sequence check.
Explanation: The error occurred during processing of 1 Duplicate record.
a basic index sequential access method (BISAM) or 2 DCB closed when error detected.
queued indexed sequential access method (QISAM)
OPEN macro instruction. 3 Overflow record.
The control program found that the DCBMACRF field of 4 PUT: length of field greater than length
the data control block (DCB) did not indicate a valid indicated in DCBLRECL field of the data
mode of operation for BISAM or QISAM. The control block.
DCBMACRF field is set up by the MACRF operand of 5-7 (Reserved bits).
the DCB macro instruction or by the problem program
before the data control block is opened. Application Programmer Response: Examine the
DCBEXCD1 and DCBEXCD2 fields of the data control
Chapter 2. System Completion Codes 33
032 • 034
block to determine the cause of the error. Specify the data control block (DCB) contains the address
address of an error analysis routine to be given control of the last record in the prime area.
when an I/O error is detected and, for errors occurring
03 An I/O error occurred while searching for the
during CLOSE, run a QISAM CLOSE macro instruction
end-of-file mark following the last data record
prior to returning control to the supervisor. For errors
in the independent overflow area. The
occurring during the processing of a QISAM CLOSE
DCBLIOV field of the data control block (DCB)
macro instruction, respond as indicated by message
contains the address of the last record in the
IEC011I or IEC203I.
independent overflow area.
System programmer response: If the error recurs
04 The DCBMSHIA field of the data control block
and the program is not in error, look at the messages in
(DCB) contained an address that either
the job log for more information. Search problem
specified a location outside the boundaries of
reporting data bases for a fix for the problem. If no fix
the virtual storage assigned to the task or had
exists, contact the IBM Support Center. Provide the JCL
a storage protection key other than that
and the program listing for the job.
specified in the task control block (TCB).
Source: DFSMSdfp
05 An I/O error occurred while reading the last
prime data block during open processing for
032 resume load.
Explanation: An error occurred during processing of a v All volumes of a multivolume ISAM data set
basic index sequential access method (BISAM) or were not mounted.
queued indexed sequential access method (QISAM)
Application Programmer Response: Verify that the
OPEN macro instruction.
DCBLPDA, DCBLIOV, and DCBMSHIA fields were not
The control program found that the DCBMACRF field of incorrectly specified or modified by the problem
the data control block (DCB) did not contain valid program. At the time of the abnormal end, register 4
information for ISAM. contains the address of the DCB. After making
corrections, reassemble the program and run the job
Application Programmer Response: Make sure that
step again.
valid information is specified in the MACRF operand of
the DCB macro instruction. Verify that the DCBMACRF System programmer response: If the error recurs
field was not incorrectly modified by the problem and the program is not in error, look at the messages in
program before the opening process. the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
After making corrections, reassemble the program and
exists, contact the IBM Support Center. Provide the JCL
run the job step again.
and the program listing for the job.
System programmer response: If the error recurs
Source: DFSMSdfp
and the program is not in error, look at the messages in
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix 034
exists, contact the IBM Support Center. Provide the JCL
Explanation: The error occurred during processing of
and the program listing for the job.
a BISAM OPEN macro instruction. For variable length
Source: DFSMSdfp records, the control program found that the address in
DCBMSWA was not valid. Either the address is outside
the boundaries of virtual storage or the protection key of
033
that address is not the same as the protection key in
Explanation: The error occurred during processing of the TCB.
an OPEN macro instruction for an indexed sequential
The control program found that the fields of the data
data set. If the error occurred during the processing of
control block (DCB) indicated a virtual storage area too
an indexed sequential access method (ISAM) OPEN
small to contain the highest level index for the data set.
executor, register 15 contains a hexadecimal reason
The size of the virtual storage area that should be
code:
reserved for the highest level index is placed in the
Code Explanation DCBNCRHI field of the data control block at OPEN exit
time.
01 An I/O error occurred while reading the highest
level index. Application Programmer Response: The error can
be corrected by one of the following:
02 An I/O error occurred while searching for the
end-of-file mark following the last data record v Specify a valid address in the MSWA operand of the
in the prime area. The DCBLPDA field of the DCB. Verify that this field has not been incorrectly
modified.
34 z/OS V1R10.0 MVS System Codes
035 • 038
v Provide a sufficient virtual storage area by proper on a direct access device as the prime area for the data
specification of the DCBSMSI and DCBMSHIA fields. set:
v Provide no virtual storage area and either do not v In QISAM load mode, during data set generation, the
specify the contents of the DCBSMSI and SPACE parameter of the DD statement did not
DCBMSHIA fields or set the fields to zero. The specify a primary quantity.
highest level index can then be processed without v The data set control block (DSCB) for the data set
being loaded into virtual storage. was incorrectly modified by the problem program.
After making corrections, reassemble the program and Application Programmer Response: In the first case,
run the job step again. the data set should be dumped sequentially and
recreated using QISAM load mode. The job should be
System programmer response: If the error recurs restarted with a primary quantity specified in the SPACE
and the program is not in error, look at the messages in parameter of the DD statement. If the prime area is to
the job log for more information. Search problem span more than one volume, the number of volumes
reporting data bases for a fix for the problem. If no fix and the number of units required should be specified.
exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job. In the second case, verify that the data set control block
was not incorrectly modified by the problem program.
Source: DFSMSdfp After making corrections, reassemble the program and
run the job step again.
035 System programmer response: If the error recurs
Explanation: The error occurred during processing of and the program is not in error, look at the messages in
a BISAM OPEN macro instruction. the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
The control program found that new records were to be exists, contact the IBM Support Center. Provide the JCL
added to the data set, but the DCBMSWA and and the program listing for the job.
DCBSMSW fields of the data control block (DCB)
indicated a virtual storage area too small to contain one Source: DFSMSdfp
track from the prime area. The appropriate
ISAM-calculated value that you should specify in 037
DCBSMSW is returned in register 15. If this value is
greater than 65535, you must let ISAM obtain this work Explanation: The error occurred during processing of
area for you. a BISAM or QISAM OPEN macro instruction. The
control program found that the buffers supplied by the
Application Programmer Response: The error can programmer were inadequate for the records to be
be corrected by one of the following: processed:
v Provide a sufficient area by proper specification of v If the buffers were acquired by use of the BUILD
the DCBMSWA and DCBSMSW fields. macro instruction, either the BUFNO operand of the
v For fixed-length records, provide no virtual storage DCB macro instruction was not specified or the BUFL
area. Either do not specify the contents of the operand specified too small a value.
DCBMSWA and DCBSMSW fields or set the fields to v If the buffers were acquired by use of the GETPOOL
zero. A virtual storage work area is required only for macro instruction, the buffer length operand specified
variable-length records. too small a value.
After making corrections, reassemble the program and Application Programmer Response: Specify the
run the job step again. buffers correctly. Then run the job step again.
System programmer response: If the error recurs System programmer response: If the error recurs
and the program is not in error, look at the messages in and the program is not in error, look at the messages in
the job log for more information. Search problem the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job. and the program listing for the job.
Source: DFSMSdfp Source: DFSMSdfp
036 038
Explanation: The error occurred during processing of Explanation: The error occurred during processing of
a BISAM or QISAM OPEN macro instruction. an OPEN macro instruction for QISAM load mode.
The control program found that no space was allocated The control program found that the space on a direct
Chapter 2. System Completion Codes 35
039 • 03B
access device that had been allocated for the index When the ISAM interface is used to process a VSAM
area was either exhausted or occupied more than one data set, this system completion code can be
volume. The index for an ISAM data set must reside on accompanied by message IEC251I. If it is, refer to the
one volume. explanation of message IEC251I for information about
the task that ended.
Application Programmer Response: If a new data
set is being created, the job must be restarted with Application Programmer Response: Determine the
larger space allocation specified in the SPACE data set for which the problem occurred and the nature
parameter of the DD statement. of the problem.
If an old data set is being updated, the data set should If this system completion code is accompanied by
be dumped sequentially, the old data set scratched, and message IEC251I, respond as indicated by message
the data set recreated from the sequential data set IEC251I.
using QISAM load mode. The job should be restarted
At the time of the ABEND, register 4 points to the
with larger space allocation specified in the SPACE
OPEN/CLOSE/END-OF-VOLUME work area. At X'64' in
parameter of the DD statement.
the work area is the address of the job file control block
System programmer response: If the error recurs (JFCB) whose contents begin with the 44 character data
and the program is not in error, look at the messages in set name. The address of the unit control block (UCB),
the job log for more information. Search problem which contains the device address for the data set, is
reporting data bases for a fix for the problem. If no fix located and X'230' in the work area. The address of the
exists, contact the IBM Support Center. Provide the JCL user’s DCB which contains the address of the data
and the program listing for the job. event block (DEB) is located at X'238' in the work area.
Correct the problem with the data set and rerun the job.
Source: DFSMSdfp
System programmer response: If the error recurs
and the program is not in error, look at the messages in
039
the job log for more information. Search problem
Explanation: The error occurred in scanning a data reporting data bases for a fix for the problem. If no fix
set using QISAM. exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
The end of the data set (EOD) was reached. The
control program found that the DCBEODAD field of the Source: DFSMSdfp
data control block (DCB) did not contain an
end-of-data-set exit routine address.
03B
Application Programmer Response: Make sure that
Explanation: The error occurred during processing of
the address of a routine to be given control when the
an OPEN macro instruction for an indexed sequential
end of the data set is reached is specified either in the
data set. If register 15 does not contain a hexadecimal
EODAD operand of the DCB macro instruction or in the
reason code, then no records could be processed
problem program before the end of the data set is
because:
reached. Then reassemble the program and run the job
step again. v The block size (DCBBLKSI) is less than the logical
record length (DCBLRECL).
System programmer response: If the error recurs
v The block size (DCBBLKSI) is not a multiple of the
and the program is not in error, look at the messages in
logical record length.
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
If the error occurred during the processing of an ISAM
exists, contact the IBM Support Center. Provide the JCL
OPEN executor, register 15 contains a hexadecimal
and the program listing for the job.
reason code. No records could be processed because:
Source: DFSMSdfp
Code Explanation
01 The format-2 data set control block (DSCB)
03A
indicated that 1/2 1/21/21/2MSG 8028 1/2
Explanation: The error occurred during processing of 1/21/21/2MSG 8028 the data set had not been
a BISAM or QISAM CLOSE macro instruction. created (DS2STIND is not equal to X'20'), or
the format-2 DSCB indicated that the data
A format 2 data set control block (DSCB), read from a
control block (DCB) had not been closed after
direct access device into virtual storage, was updated
the data set had been created.
from various fields of the data control block (DCB).
When an attempt was made to write the updated data 03 For variable length records, the relative key
set control block back to the direct access device, an position (DCBRKP) field in the data control
I/O error occurred. block (DCB) is less than four.
36 z/OS V1R10.0 MVS System Codes
03B
04 The relative key position (DCBRKP) plus the 01 Make sure that the data set has been
key length (DCBKEYLE) is greater than the properly created and that the creating
logical record length (DCBLRECL). task closes the data control block.
05 The DCBKEYLE field of the data control block 03 If variable length records are used,
contained zero. make sure that the value of the
DCBRKP field is not less than four.
06 The DCBKEYLE field of the data control block
(DCB) does not equal the value in the 04 Make sure that the value of the
DS1KEYL field of the format-1 DSCB. DCBRKP field of the data control
block, when added to the value of in
07 A QISAM data control block was being opened
the DCBKEYLE field, does not exceed
in preparation for a PUT operation, but the
the value in the DCBLRECL field.
OPEN macro instruction had not been issued
for output. 05, 06 Correct the DCBKEYLE field. For an
existing ISAM data set, omit the
09 The logical record length in the data control
KEYLEN operand on the DCB macro
block (DCBLRECL) is zero.
instruction. This allows the data set
0A The record format in the format-1 DSCB control block to supply the key length
(DS1RECFM) indicates fixed blocked records, value.
but the block size (DCBBLKSI) equals the
07 Make sure that OUTPUT is specified
logical record length (DCBLRECL).
as option 1 in the OPEN macro
0B The block size (DCBBLKSI) differs from the instruction.
format-1 DSCB block size (DS1BLKL).
09, 0A, 0B, 0C Make sure that the block size
0C The logical record length (DCBLRECL) differs (BLKSIZE) and logical record length
for the format-1 DSCB logical record length (LRECL) have been specified correctly
(DS1LRECL). on the data control block (DCB) and
that they are compatible.
0D QISAM data control block was being opened in
preparation for a PUT operation and 0D Code DISP=OLD in the JCL for the
DISP=SHR was coded in the JCL. QISAM data control block that is being
opened for a PUT operation.
0E The value for the record format (DCBRECFM)
is zero. 0E, 0F Make sure that the record format has
been specified correctly. For an
0F The value for the record format (DCBRECFM) existing ISAM data set, list the VTOC
is not the same as the record format value to determine the correct format of the
specified when the data set was created data set.
(DS1RECFM).
If register 15 does not contain a hexadecimal reason
Register 2 contains the address of the DCB for which code, then make sure that:
the abend was issued.
1. the blocksize (BLKSIZE) and logical record length
(LRECL) have been specified correctly on the data
When the ISAM interface is used to process a VSAM
control block (DCB).
data set, this system completion code can be
accompanied by message IEC161I. If it is, refer to 2. the BLKSIZE and LRECL are compatible.
message IEC161I for information about the task that
ended. The ISAM interface of VSAM issues system In cases when the ISAM interface issued an ABEND,
completion code 03B for one of the following reasons: make sure that a valid mode of operation is specified in
v The access method service’s and DCB values for the MACRF operand of the DCB macro. Additionally,
LRECL, KEYLE, RKP do not match. make sure that the DCB is not being opened for load
mode while there are records in the data set.
v DISP=OLD was specified and the DCB was opened
for output and the number of logical records is
In all cases, run the job step again.
greater than zero (RELOAD is implied).
v An OPEN ACB error code 116 was returned for a If message IEC161I accompanies this system
request to open a VSAM structure. completion code, respond as indicated for message
Application Programmer Response: Take the IEC161I.
following actions depending on the reason code you System programmer response: If the error recurs
received: and the program is not in error, look at the messages in
Code Response the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
Chapter 2. System Completion Codes 37
03C • 03F
exists, contact the IBM Support Center. Provide the JCL This system completion code is sometimes
and the program listing for the job. accompanied by message IEC156I. If so, refer to the
explanation of message IEC156I for complete
Source: DFSMSdfp
information about the task that was ended and for an
explanation of the return code (rc in the message text)
03C in register 15.
Explanation: A page, a segment, or an ASTE fault Application Programmer Response: Correct the
occurred. RSM detected one of the following conditions. DCB parameter or SER subparameter, as necessary,
and run the job step again.
Register 15 contains a hexadecimal reason code. In the
reason code, the bytes designated x contain diagnostic If this system completion code is accompanied by
data that may be requested by IBM. message IEC156I, respond as indicated for the
message.
Code Explanation
System programmer response: If the error recurs
xxxx08xx A program disabled for interrupts held and the program is not in error, look at the messages in
the RSM lock, or a higher lock, when the job log for more information. Search problem
a fault occurred. reporting data bases for a fix for the problem. If no fix
xxxx0Dxx No central storage frames were exists, contact the IBM Support Center. Provide the JCL
available to resolve a page fault when and the program listing for the job.
the unit of work was running disabled Source: DFSMSdfp
for interrupts.
System action: The system issues an abend to the 03E
current task.
Explanation: The error occurred during processing of
Application Programmer Response: For reason a QISAM OPEN macro instruction. The position of the
code X'xxxx0Dxx', run the job again. If the error recurs, last prime data record indicated that there is no room to
contact the system programmer. add records with resume load.
System programmer response: Search problem The loading of an indexed sequential data set must be
reporting data bases for a fix for the problem. If no fix completed during the initial OPEN/PUT/CLOSE cycle for
exists, contact the IBM Support Center. that data set. An indexed sequential data set that has
Source: Real storage manager (RSM) been opened and closed for loading may be
subsequently loaded if no data was created.
03D Possibly, an attempt was made to add records with
resume load to the prime area of an ISAM data set that
Explanation: The error occurred during processing of had no space available for additional records.
(1) a QISAM or BISAM OPEN macro instruction or (2) a
BDAM OPEN macro instruction. Application Programmer Response: Either load the
data set again with a larger space allocation, or add
One of the following occurred: records using BISAM.
v In case (1), the DD statement did not specify an
After making corrections, run the job step again.
indexed sequential organization (which can be
specified by a DSORG=IS or DSORG=ISU System programmer response: If the error recurs
subparameter of the DCB parameter). and the program is not in error, look at the messages in
v In case (1), if the data set resides on multiple the job log for more information. Search problem
volumes, either the volume serial numbers in the reporting data bases for a fix for the problem. If no fix
SER subparameter of the VOLUME parameter of the exists, contact the IBM Support Center. Provide the JCL
DD statement were not in proper sequence, or not all and the program listing for the job.
volume serial numbers were specified. The serial Source: DFSMSdfp
number of the volume containing the index must be
listed first. The number of volumes and the number of
units allocated must be the same, and all volumes 03F
must be mounted.
Explanation: An error has been detected during
v In case (2), the volume serial numbers in the SER checkpoint restart processing. This completion code is
subparameter of the VOLUME parameter of the DD accompanied by message IHJxxxI and the appropriate
statement were not in proper sequence. reason code.
v In case (2), the DCB DSORG=DA and the DD
System action: The job is abnormally ended and a
statement specifies an indexed sequential data set
dump is produced.
name.
38 z/OS V1R10.0 MVS System Codes
040 • 042
Application Programmer Response: Respond as | 00010001
indicated in the accompanying message. | For a call to the HWICMD service, the
| parameters passed by the caller are not
Source: DFSMSdfp
| accessible.
| 00010002
040
| For a call to the HWICMD service, the number
Explanation: The error occurred during processing of | of the parameters passed by the caller is not
an OPEN macro for a telecommunications access | correct.
method (TCAM) line group data set.
| 00020000
System action: The error code is inserted into register | For a call to the HWICONN service, the
0 if the user has coded an address in the EXLST= | parameters passed by the caller are not in the
operand of the line group DCB macro. The exit routine | primary address space.
may examine the code in register 0. If no user exit is
| 00020001
specified, an indication of the error type may be found
| For a call to the HWICONN service, the
in the explanation of console message IED008I.
| parameters passed by the caller are not
Application Programmer Response: See the | accessible.
documentation of message IED008I for the appropriate
| 00020002
responses.
| For a call to the HWICONN service, the
Source: Teleprocessing | number of the parameters passed by the caller
| is not correct.
041 | 00030000
| For a call to the HWIDISC service, the
Explanation: The error occurred during processing of | parameters passed by the caller are not in the
an OPEN macro for a telecommunications access | primary address space.
method (TCAM) message queue data set.
| 00030001
System action: The error code is inserted into register | For a call to the HWIDISC service, the
0 if the user has coded an address in the EXLST= | parameters passed by the caller are not
operand of the message queue DCB macro instruction. | accessible.
The exit routine may examine the code in register 0. If
no installation exit is specified, an indication of the error | 00030002
type may be found in the explanation of console | For a call to the HWIDISC service, the number
message IED008I. | of the parameters passed by the caller is not
| correct.
Application Programmer Response: See the
documentation of message IED008I for the appropriate | 00040000
responses. If your system has the advanced | For a call to the HWIEVENT service, the
communications function (ACF)/TCAM program product | parameters passed by the caller are not in the
installed, see the appropriate ACF/TCAM messages | primary address space.
book .
| 00040001
Source: Teleprocessing | For a call to the HWIEVENT service, the
| parameters passed by the caller are not
| accessible.
| 042
| 00040002
| Explanation: A call for a base control program internal | For a call to the HWIEVENT service, the
| interface (BCPii) service was issued in an incorrect | number of the parameters passed by the caller
| environment, or BCPii detects an unrecoverable error. | is not correct.
| A hexadecimal reason code in register 15 explains the | 00050000
| error: | For a call to the HWILIST service, the
| Code Explanation | parameters passed by the caller are not in the
| primary address space.
| 00010000
| For a call to the HWICMD service, the | 00050001
| parameters passed by the caller are not in the | For a call to the HWILIST service, the
| primary address space. | parameters passed by the caller are not
| accessible.
Chapter 2. System Completion Codes 39
042
| 00050002 | xxxx000D
| For a call to the HWILIST service, the number | xxxx is greater than or equal to 0100. An
| of the parameters passed by the caller is not | internal error occurred in BCPii.
| correct.
| xxxx000E
| 00060000 | xxxx is greater than or equal to 0100. An
| For a call to the HWIQUERY service, the | internal error occurred in BCPii.
| parameters passed by the caller are not in the
| xxxx000F
| primary address space.
| xxxx is greater than or equal to 0100. An
| 00060001 | internal error occurred in BCPii.
| For a call to the HWIQUERY service, the
| xxxx0010
| parameters passed by the caller are not
| xxxx is greater than or equal to 0100. An
| accessible.
| internal error occurred in BCPii.
| 00060002
| xxxx0011
| For a call to the HWIQUERY service, the
| xxxx is greater than or equal to 0100. An
| number of the parameters passed by the caller
| internal error occurred in BCPii.
| is not correct.
| xxxx0012
| xxxx0001
| xxxx is greater than or equal to 0100. An
| xxxx is greater than or equal to 0100. An
| internal error occurred in BCPii.
| internal error occurred in BCPii.
| xxxx0013
| xxxx0002
| xxxx is greater than or equal to 0100. An
| xxxx is greater than or equal to 0100. An
| internal error occurred in BCPii.
| internal error occurred in BCPii.
| xxxx0014
| xxxx0003
| xxxx is greater than or equal to 0100. An
| xxxx is greater than or equal to 0100. An
| internal error occurred in BCPii.
| internal error occurred in BCPii.
| xxxx0015
| xxxx0004
| xxxx is greater than or equal to 0100. An
| xxxx is greater than or equal to 0100. An
| internal error occurred in BCPii.
| internal error occurred in BCPii.
| xxxx0016
| xxxx0005
| xxxx is greater than or equal to 0100. An
| xxxx is greater than or equal to 0100. An
| internal error occurred in BCPii.
| internal error occurred in BCPii.
| xxxx0017
| xxxx0006
| xxxx is greater than or equal to 0100. An
| xxxx is greater than or equal to 0100. An
| internal error occurred in BCPii.
| internal error occurred in BCPii.
| System action: Specific system actions for each
| xxxx0007
| reason code are as follows:
| xxxx is greater than or equal to 0100. An
| internal error occurred in BCPii. | Code System Action
| xxxx0008 | 00010000 through 00060002
| xxxx is greater than or equal to 0100. An | The system rejects the service call.
| internal error occurred in BCPii.
| xxxx0003,xxxx0005,xxxx0006,xxxx0007,xxxx0008,
| xxxx0009 | xxxx0009,xxxx000C,xxxx000D,xxxx000E,xxxx000F,
| xxxx is greater than or equal to 0100. An | xxxx0010,xxxx0011,xxxx0012,xxxx0013,xxxx0014,
| internal error occurred in BCPii. | xxxx0016,xxxx0017
| BCPii continues processing, but the system
| xxxx000A
| does not perform the requested service. The
| xxxx is greater than or equal to 0100. An
| system takes an SVC dump.
| internal error occurred in BCPii.
| xxxx0001,xxxx0002,xxxx0004,xxxx000A,xxxx000B,
| xxxx000B
| xxxx0015,xxxx0017
| xxxx is greater than or equal to 0100. An
| The system abnormally ends the BCPii
| internal error occurred in BCPii.
| address space, and takes an SVC dump. No
| xxxx000C | BCPii callable services are accepted by the
| xxxx is greater than or equal to 0100. An | system until the address space is manually
| internal error occurred in BCPii. | restarted.
40 z/OS V1R10.0 MVS System Codes
043
| Application Programmer Response: Respond as 07 The application program is not an authorized
| indicated for the specific reason code: program, but the user has either coded
AUTHA=YES or taken YES as the default
| Code Programmer Response
value for AUTHA parameter on the TCAM
| 00010000 through 00060002 INTRO macro.
| Check the calling program for a probable
08 Page control block (PCB) error. OPEN was
| coding error; correct the program and run it
issued for a TPROCESS entry while its PCB
| again.
was in use by another task.
| All other codes 09 A TCAM job name was not found with the
| Contact the IBM Support Center.
same name as the TCAM job name that was
| Operator response: If the abend recurs, notify the qualified on the DD statement as input to
| system programmer. IGG01946 (DCB OPEN).
| System programmer response: If the error recurs, 0A The number of environmental checkpoint
| search problem reporting data bases for a fix for the records that can be written is less than the
| problem. If no fix exists, contact the IBM Support number of environmental checkpoint records
| Center. requested.
| Source: HWIBCPII (BCPii) address space System action: If an ABEND installation exit is
provided in the EXLST= operand of the DCB macro for
the data set, the system gives control to the routine. If it
043 returns, or if no ABEND installation exit is provided, the
Explanation: The error occurred during processing of system abnormally ends the task. Message IED015I
an OPEN macro for a telecommunications access may accompany this system completion code.
method (TCAM) application program data set. Application Programmer Response: No action is
Register 0 contains a hexadecimal reason code that required if an ABEND installation exit has been provided
explains the error: in the EXLST= operand of the DCB macro for the
application program data set.
Code Explanation
The contents of register 0 indicate the action to be
01 An OPEN macro for a TCAM application taken:
program data set has been issued but there is
no message control program (MCP) active in Register 0 Response
the system. 01 Ensure that an MCP is active before
02 The QNAME= parameter of a DD statement attempting to start an application
associated with an application program is not program.
the name of a process entry defined in the 02 Recode the QNAME= parameter
terminal table, or the QUEUES= operand specifying the name of a valid process
appeared in the TPROCESS macro instruction entry.
when an application program data control block
(DCB) was being opened for output only, or the 03 Recode the QNAME= parameter
QUEUES= operand was not specified when an specifying the name of a valid process
application program DCB was being opened for entry.
input.
04 Specify a larger region or partition
03 A process entry named by the QNAME= size on the JOB statement for the
parameter of a DD statement associated with MCP, or restart the system specifying
an application program is currently being used a larger system queue space.
by another application program.
05 Specify a larger partition size on the
04 Insufficient virtual storage was available in the JOB statement for the application
MCP to build internal control blocks, or the program.
PGFN macro failed for the process entry work
06 Recode the SECURE=YES operand
area.
associated with the queue, or instruct
05 Insufficient virtual storage was available in the the system operator to allow the
application program area to build internal queue to be opened.
control blocks.
07 Link edit the application program as
06 The application program attempted to open a an authorized program into an
secured queue. The system operator rejected
the request.
Chapter 2. System Completion Codes 41
044 • 045
authorized library, or specify 06 Ensure that the size of one half of the
AUTHA=NO on the TCAM INTRO trace table does not exceed the
macro. maximum block size specified for the
trace data set.
08 Open all TPROCESS entries for the
PCB in the same application program. Source: DFSMSdfp
09 Either start the TCAM with the
jobname wanted or change the 045
jobname on the
Explanation: The error occurred during processing of
QNAME=procname.jobname operand
a telecommunications access method (TCAM) message
and restart the application program.
control program (MCP). The MCP ends.
0A Either increase the number of
The low-order byte of register 15 contains a
environmental checkpoint records that
hexadecimal reason code that explains the error:
can be written, or decrease the
requested number of environmental Code Explanation
checkpoint records.
01 I/O has been requested on a nonreusable disk
Source: Teleprocessing record that is beyond the capacity of the data
set. The nonreusable disk data set cannot be
wrapped.
044
02 Logical read error caused by the reusable disk
Explanation: The error occurred during processing of
receiving a heavy burst of new traffic. This
the FE Common Write (COMWRITE) task. The
traffic causes unsent messages to be overlaid
COMWRITE task has been ended.
before being copied to the alternate destination
The hexadecimal contents of register 3 indicates the queue.
nature of the error:
03 Logical read error while trying to fetch a
Register 3 Explanation message for transmission to a terminal.
01 Permanent I/O error on output device. 04 The copy subtask needed to copy messages
Register 7 contains user ID; register 8 from one data set to another has not been
contains address of failing DECB. loaded by the disk OPEN. A multiple-route or
distribution list message has been enqueued to
02 STAE routine failed. Register 15
go to dissimilar message queue types. The
contains the return code.
copy subtask is needed to put the message on
03 User parameter list is incorrect, and the queue. Caused by failure to open
output required was specified. successfully a disk message queue data
Register 7 contains the address of the control block (DCB).
parameter list saved in COMWRITE.
05 I/O has been requested on an unopened disk
Register 11 contains the address of
message queue data set.
the error message.
06 FEATURE=(,,NOTIMER) has been specified on
05 The output DCB failed to open.
the INTRO macro, but a function requiring the
06 For one of the traces specified, the system timer has been called.
size of one half of the trace table is
07 A message longer than the reusable disk data
larger than the maximum block size
set has been entered.
specified for the trace data set.
08 A disk read error occurred. It was a hardware
Application Programmer Response: Response
error, not a logical read error.
depends upon the hexadecimal contents of register 3:
09 Either insufficient space was allocated for the
Register 3 Response
checkpoint data set, or a read error occurred
01 Check the status of the recording when attempting to read records from the
medium. If it is valid, call your checkpoint data set during a restart.
hardware support personnel.
0A Either the checkpoint data set is too small, or
02 Call your hardware support personnel. the number of checkpoint records specified in
the INTRO macro is too large.
03 Check the parameter list.
System action: The system abnormally ends. The
05 Missing DD statement. Include the DD system writes an error to the logrec data set.
statement and rerun the job.
Application Programmer Response: Except for
42 z/OS V1R10.0 MVS System Codes
046 • 048
return code X'08', this is a probable user error. To v Resides in an APF-authorized library
determine the action for a specific reason code, follow
System action: The system writes a logrec data set
these procedures based on the reason code in register
error record.
15:
Operator response: If the system programmer asks
Code Response
for an SVC dump, set the following SLIP trap:
01 Either specify a larger data set or SLIP SET,COMP=047,ACTION=SVCD,END
request that close down occur at an
earlier point. System programmer response: Do the following:
1. Ask the operator to set a SLIP trap to obtain an
02,03,07 Specify a larger data set or one that
SVC dump.
occupies more than one extent.
2. In the system trace, look for the SVC D or *SVCE D
04,05 Before issuing the OPEN macro for entry for abend X'047'.
the lines, test for successful open of
3. Look for an SVC entry preceding the entry found in
the message queue data set.
step 2. The SVC entry should be for the same TCB
06 Specify FEATURE=(,,TIMER). and have the same ASID as the entry found in step
Assemble and run the MCP again. 2. The PSW for this SVC entry contains the address
of the unauthorized program that issued a restricted
09 The message issued to the operator
SVC.
just before ABEND describes the
cause of failure, and the message 4. Use the PSW found in step 3 to identify the
description provides a response. unauthorized module that issued the restricted SVC.
v For an installation-provided module, continue
0A Either allocate more space for the
diagnosis with the module.
checkpoint data set, or specify fewer
checkpoint records in the INTRO v For an IBM module whose module prefix is IED
macro. or IKJ, the module is most likely a TCAM module.
Specify AUTHA=NO on the INTRO macro in the
System programmer response: For return code TCAM MCP program and run the job again. If the
X'08', look at the messages in the job log for more problem recurs, search problem reporting data
information. Contact hardware support. Provide the bases for a fix for the problem. If no fix exists,
logrec data set error record and the SYSOUT output for contact the TCAM group at the IBM Support
the job. For all other return codes, search problem Center. Provide the SVC dump and the logrec
reporting data bases for a fix for the problem. If no fix data set error record.
exists, contact the IBM Support Center.
v For an IBM module that is not part of TCAM,
Source: Teleprocessing search problem reporting data bases for a fix for
the problem. If no fix exists, contact the
component group associated with this module at
046 the IBM Support Center. Provide the SVC dump
Explanation: The telecommunications access method and the logrec data set error record.
(TCAM) message control program (MCP) has ended but Source: Supervisor control
an application program data set is still open. The
application program data set is scheduled to be ended
with a system completion code of X'046'. 048
System action: The application program abnormally Explanation: A subsystem address space supported
ends. by advanced communications function/
telecommunications access method (ACF/TCAM) had
Application Programmer Response: See the an error condition. An ACF/TCAM subsystem has
programmer response for the system completion code determined that recovery could not occur. The
provided with the abnormal end of the MCP. subsystem abnormally ends. Register 0 contains one of
Source: Teleprocessing the following failure codes:
Code Explanation
047 001 The request parameter list (RPL) address was
Explanation: An unauthorized program issued a incorrect when the subsystem interface was
restricted Supervisor Call (SVC) instruction: not running with authorized path.
An authorized program: 002 An abnormal end occurred before the
subsystem was notified of function recovery
v runs in supervisor state
routines (FRR) recovery.
v Holds PSW key 0-7
Chapter 2. System Completion Codes 43
049 • 04E
System action: Restart the subsystem.
04B
Application Programmer Response: Print the SVC
Explanation: An incorrect operation code was passed
dump, which was stored in the SYS1.DUMP data set.
to a TSO linkage assist routine (LAR). Register 15
System programmer response: Format the SVC contains a hexadecimal code that indicates the reason
dump with the interactive problem control system for the termination.
(IPCS). Search problem reporting data bases for a fix
Code Explanation
for the problem. If no fix exists, contact the IBM Support
Center. 004 The LAR for the terminal monitor program
received an incorrect function number.
Source: Teleprocessing
008 The service routine’s LAR was invoked an
incorrect service routine entry point.
049
System action: TSO does not perform the requested
Explanation: A subsystem address space or
service. The system writes an ABEND dump. The
telecommunications access method (TCAM) appendage
system writes a logrec data set error record.
supported by advanced communications function
(ACF)/TCAM had an error condition. The FRR was Application Programmer Response: Determine the
unable to recover the subsystem. calling routine and correct the operation code.
System action: A logrec data set entry has been System programmer response: If the problem recurs
created that explains why recovery could not occur. An and if the program is not in error, search problem
SVC dump was written to SYS1.DUMP. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
Operator response: Restart the system.
ABEND dump and the logrec data set record.
Application Programmer Response: Print the dump
Source: Time Sharing Option Extensions (TSO/E)
and logrec entry.
System programmer response: Format the SVC
04C
dump with the interactive problem control system
(IPCS). Search problem reporting data bases for a fix Explanation: A user invoked the TMP (terminal
for the problem. If no fix exists, contact the IBM Support monitor program) and the TMP detached a program that
Center. completed with a nonzero completion code. The
nonzero completion code is in register 15.
Source: Teleprocessing
System action: The system does not change the user
return code.
04A
Source: Time Sharing Option Extensions (TSO/E)
Explanation: An MVSSERV program made an
incorrect request for data management services. A
reason code provides further information: 04E
Code Explanation Explanation: When the system detects an error in
internal IBM DATABASE 2 (DB2®) processing, it will
004 The program passed an incorrect operation
abnormally end a connected user task (TCB) or one of
code in a request for a data management
its own internal tasks. For information about the reason
service.
codes associated with this abend code, see DB2
008 The program made an unsupported request for Messages and Codes.
the data management GET macro.
System action: The system abnormally ends the
012 The program made an unsupported request for connected user task or the DB2 internal task.
the data management PUT macro.
Application Programmer Response: Check register
System action: The MVSSERV program ends 15 of the SDWA section ‘General Purpose Registers at
abnormally. The system writes an ABEND dump. Time of Error’, and locate the accompanying reason
code. In addition, check the information displayed at the
System programmer response: If the problem recurs user’s terminal, and in the corresponding logrec data set
and if the program is not in error, search problem entry.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the System programmer response: If the error recurs
ABEND dump. and the program is not in error, look at the messages in
the job log for more information. Search problem
Source: Time Sharing Option Extensions (TSO/E) reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
44 z/OS V1R10.0 MVS System Codes
04F • 052
SYSOUT output for the job and the logrec data set error xxxx042B
record. The job step task of TSO Server address
space is ending because the task that created
Source: DFSMSdfp
it is terminating.
xxxx0432
04F
The job step task of a TSO Server address
Explanation: To avoid data integrity problems, the space is terminating because the request timed
subsystem abnormally ends; one or more 04E system out.
completion codes will usually precede the end. During
xxxxyyyy
DATABASE 2 (DB2) abend, a user task with an active
All other internal errors.
DB2 connection can be abended with a X'04F' system
completion code; in rare instances, the entire connected System action: An SVC dump may be produced.
address will be abended (MEMTERM). However, if the
Operator response: Contact the System Programmer
subsystem ends an address space after numerous
for xxxxyyyy.
cancel attempts, this is not a DB2 internal error.
System programmer response: Contact IBM Service
System action: The subsystem abnormally ends DB2.
for xxxxyyyy.
Operator response: Message DSNV086E should
appear on your console screen. First, copy this
051
message and the accompanying subsystem end reason
code. Second, notify the system programmer. Explanation: An MVSSERV program made an
incorrect request for data management services. A
Application Programmer Response: If the
reason code provides further information:
subsystem abnormally ends DB2, then record the
subsystem end reason code that is displayed in Code Explanation
message DSNV086E. In addition, you should be aware
of the following situations. 004 The program passed an incorrect operation
code in a request for a data management
1. If you received any X'04E' system completion codes service.
prior to this subsystem end, perform the following
actions. Check register 15 of the SDWA section System action: The MVSSERV program ends. The
‘General Purpose Registers at Time of Error’, and system writes an ABEND dump.
locate the accompanying reason code. In addition,
System programmer response: If the problem recurs
check the information displayed at the user’s
and if the program is not in error, search problem
terminal, and in the corresponding logrec data set
reporting data bases for a fix for the problem. If no fix
entry.
exists, contact the IBM Support Center. Provide the
2. If you did not receive any X'04E' system completion ABEND dump.
codes prior to the subsystem end, you will need an
SVC dump, which is entitled ‘DB2 SUBSYSTEM Source: Time Sharing Option Extensions (TSO/E)
TERMINATION REQUESTED -
REASON=xxxxxxxx.’ The reason code in the 052
message and the one found in the MVS operator
message will be the same. Explanation: A program incorrectly issued a macro to
request processing by Program Call/authorization
System programmer response: If the error recurs (PC/AUTH) service routines.
and the program is not in error, look at the messages in
the job log for more information. Search problem Register 15 contains a hexadecimal reason code in the
reporting data bases for a fix for the problem. If no fix form xxyy, where x identifies the macro that was issued,
exists, contact the IBM Support Center. Provide the and yy identifies the error. See the system programmer
SYSOUT output for the job and the logrec data set error response for an explanation of these reason codes.
record. System action: The system abends the program that
Source: DFSMSdfp issued the macro. The system writes an ABEND dump.
System programmer response: Obtain the ABEND
050 dump and find the reason code associated with the
abend.
Explanation: An abend occurred in System REXX
processing. In the system trace table, look for the last *SVCE D
entry. The PC entry preceding it gives the address in
Code Explanation the program of the failing macro.
If the macro was issued by an installation-provided
program, correct the program. If the macro was issued
Chapter 2. System Completion Codes 45
052
by a system component, or if the problem persists, of the entry table description (ETD) specified in
search problem reporting data bases for a fix. If no fix the ENTRIES parameter.
exists, contact the IBM Support Center. Provide the
0302 The format number field in the entry table
ABEND dump.
description (ETD) is incorrect.
The reason codes in register 15 are:
0303 The request count in the ETDNUM field is not
Code Explanation valid.
01yy The program issued an LXRES macro. 0304 The caller passed a non-zero value in register
1.
0101 A reserved field in the parameter list is not 0.
Register 5 contains the first word of the 0311 A reserved field is not equal to 0 in one of the
parameter list. description elements in the entry table
description (ETD). Register 2 contains the
0102 The format number field in the parameter list is
entry index associated with the description
not valid. Register 5 contains the first word of
element.
the parameter list.
0312 The program identified in one of the description
0103 The request count in the linkage index (LX) list
elements could not be found. Register 2
is not valid. Register 5 contains the first word
contains the entry index associated with the
of the parameter list.
description element.
0104 A job step attempted to issue the LXRES
0313 The entry indexes are not in ascending order.
macro, but a prior job step owned space-switch
Register 2 contains the entry index that was
entry tables. (Subsequent job steps are not
not in ascending order.
permitted to issue PC/AUTH macros.)
0314 A job step attempted to issue an ETCRE
02yy The program issued an LXFRE macro.
macro, but a prior job step owned space-switch
0201 A reserved field in the parameter list is not 0. entry tables. (Subsequent job steps are not
Register 5 contains the first word of the permitted to issue PC/AUTH macros.)
parameter list.
0315 Reserved fields in the extended portion of the
0202 The format number field in the parameter list is entry table description (ETD) are non-zero.
not valid. Register 5 contains the first word of
0316 Options that are valid only for a stacking
the parameter list.
Program Call (PC) were specified for a basic
0203 The request count in the linkage index (LX) list PC.
is not valid. Register 5 contains the first word
0317 An incorrect combination of ETDPKMC and
of the parameter list.
ETDPKC was specified. On the ETDEF macro,
0211 A linkage index (LX) is incorrect. Register 5 either:
contains the incorrect LX. v PKM=REPLACE was specified without EK.
v EK value was not one of the keys specified
0212 A linkage index (LX) is not owned by the home in the EKM list.
address space. Register 5 contains the
incorrect LX. 0318 The extended authorization index (EAX) is not
in the range of valid authorization indexes
0213 The program attempted to free a non-reusable (AXs).
system linkage index (LX). Register 5 contains
the linkage index. 0319 The extended authorization index (EAX)
specified was not reserved by the home
0214 A linkage index (LX) has one or more entry address space.
tables connected and the LXFRE macro did
not specify FORCE=YES. 0320 The name of the associated recovery routine
(ARR) could not be found.
0215 A linkage index (LX) appeared more than once
in the LX list. 0321 An entry table descriptor (ETD) requested that
CANCEL/DETACH processing be deferred
0216 The sequence number for a linkage index (LX) while the associated recovery routine (ARR) is
was incorrect. Register 5 contains the linkage running. PC/AUTH is not authorized to defer
index and register 6 contains the sequence this processing because it might not run in
number. supervisor state or key 0.
03yy The program issued an ETCRE macro. 0322 An entry table descriptor (ETD) requested that
Register 2 contains the index of the entry in CANCEL/DETACH processing or asynchronous
which the error was found. exits be deferred while the ARR is running, but
0301 A reserved field is not equal to 0 in the header no ARR was specified.
46 z/OS V1R10.0 MVS System Codes
052
0323 The index specified in the entry table 0604 The caller passed a non-zero value in register
description (ETD) is greater than the maximum 1. Register 2 contains the value.
index allowed.
0611 A specified token is incorrect. Register 2
04yy The program issued an ETDES macro. contains the token.
0401 A reserved input field in the parameter list is 0612 The specified token is for a system entry table.
not 0. Register 2 contains the token.
0402 The format number field in the parameter list is 0613 A specified token is for an entry table that is
not valid. not connected. Register 2 contains the token.
0411 The specified token is not valid. 0614 A token appears more than once in the token
list. Register 2 contains the token.
0412 The program specified a token for a system
entry table but did not specify PURGE=YES. 0615 The LXFRE macro passed an incorrect
address space identifier (ASID) to the ETDIS
0413 The specified token is for an entry table that
macro. Register 2 contains the incorrect ASID.
the home address space does not own.
07yy The program issued an AXRES macro.
0414 The program specified a token for an entry
table that is in use, but the program did not 0703 The request count is not valid. Register 4
specify PURGE=YES. contains the request count.
05yy The program issued an ETCON macro. 0704 The caller passed a non-zero value in register
1.
0501 A reserved input field is not 0.
0705 A job step attempted to issue an AXRES
0502 The format number field is not valid.
macro, but a prior job step owned space-switch
0503 The token list count or the linkage index (LX) entry tables. (Subsequent job steps are not
list count is not valid. permitted to issue PC/AUTH macros.)
0511 The token list count and the linkage index (LX) 08yy A program issued an AXFRE macro.
list count are not equal.
0803 The request count is not valid. Register 4
0512 A specified linkage index (LX) is already in use. contains the request count.
Register 2 contains the incorrect LX.
0804 The caller passed a non-zero value in register
0513 A specified linkage index (LX) is not reserved. 1.
Register 2 contains the incorrect LX.
0813 An authorization index (AX) is not reserved by
0514 A specified token is incorrect. the home address space. Register 4 contains
the AX.
0515 A specified token is for an entry table that is
already connected to the home address 0814 An authorization index (AX) is still in use.
space’s linkage table. Register 2 contains the Register 4 contains the address of the address
incorrect token. space control block (ASCB) using the AX.
Register 5 contains the AX.
0516 A specified token is for an entry table that is
not authorized for connection. Register 2 0817 An authorization index (AX) appeared more
contains the incorrect token. than once in the authorization index list.
Register 4 contains the duplicate AX.
0517 An entry table and the corresponding linkage
index are not owned by the same address 0818 An authorization index (AX) may still be in use
space. Register 2 contains the LX. as an extended authorization index (EAX).
0519 A token appeared more than once in the token 0823 An authorization index (AX) equal to 0 or 1
list. Register 2 contains the token. appears in the authorization index list. An AX
of 0 or 1 cannot be freed. Register 4 contains
051A A linkage index (LX) appeared more than once the AX.
in the LX list.
09yy A program issued an AXEXT macro.
051B The sequence number for a linkage index (LX)
was incorrect. Register 5 contains the linkage 0901 A reserved input field is not 0.
index and register 6 contains the sequence
0904 The caller passed a non-zero value in register
number.
1.
06yy The program issued an ETDIS macro.
0918 The address space identifier (ASID) passed as
0603 The token count is not valid. Register 2 input is not for an active address space.
contains the incorrect count. Register 4 contains the ASID.
Chapter 2. System Completion Codes 47
053
0Ayy The program issued an AXSET macro. 1313 The specified token was for a PCLINK stack
element (STKE) that is not the most recently
0A01 A reserved input field is not 0.
stacked STKE.
0A04 The caller passed a non-zero value in register
Register 2 contains the token of the current
1.
element.
0A19 The authorization index (AX) is not within the
This problem can be caused by an application
authorization index allocation table (AXAT).
program or the system.
Register 4 contains the authorization index.
1314 The specified token is not valid. Register 2
0A20 The authorization index (AX) is not reserved.
contains the incorrect token.
Register 4 contains the authorization index.
1416 The program incorrectly modified either the
0A21 The home address space has one or more
system function table (SFT) or extended
connected SASN=OLD space switch entry
system vector table (SVTX). The sum of the
tables that could cause an address space
highest extended linkage index (LX) value (an
switch.
LX value above 2047) in the SFT and the
0A23 The authorization index (AX) for the master value in the SVTXNSBLX field of the SVTX is
address space must be 1. Register 4 contains greater than decimal 16383, which it should not
the requested AX value, which is not valid be. Register 2 contains the highest extended
because it is not 1. LX value in the SFT. Register 3 contains the
value in the SVTXNSBLX field.
0Byy The program issued an ATSET macro.
Source: Program Call/authorization (PC/AUTH)
0B01 A reserved input field is not 0.
0B04 The caller passed a non-zero value in register 053
1.
Explanation: A program requested processing by
0B19 The authorization index (AX) specified is not Program Call/authorization (PC/AUTH) service or a
within the authorization index allocation table program call linkage service. An error prevented
(AXAT). The second halfword of register 4 PC/AUTH from processing the macro normally. The
contains the AX value. The content of the first system records the registers in field SDWAGRSV in the
halfword of register 4 is undefined and system diagnostic work area (SDWA).
unpredictable.
Register 15 contains a hexadecimal reason code in the
0B20 The authorization index (AX) specified is not form xxyy, where xx identifies the macro that was
reserved. Register 4 contains the AX. issued and yy identifies the error. See the system
0B22 The specified authorization index (AX) is for a programmer response for an explanation of the reason
predefined authorization table entry. Register 4 codes.
contains the AX. System action: The system abends the program that
11yy The program issued a PCLINK macro with the issued the macro, unless PC/AUTH requests a retry.
STACK parameter. The system writes an SVC dump and a logrec data set
error record.
1112 The program held one or more locks that
caused an internal error in PCLINK processing. System programmer response: Look at the
If SAVE=NO was specified, register 5 contains explanation of the reason code. If you receive one of
the caller’s return code. If SAVE=YES was the reason codes below, do the following:
specified, register 8 contains the caller’s return v For reason code X'xx97': Look in the SDWA variable
code. recording area (SDWAVRA) for the original abend
and reason code and continue diagnosis with that
12yy The program issued a PCLINK macro with the
abend.
UNSTACK parameter.
v For reason code X'xx98': Look at message IEA139E,
1211 The macro included the UNSTACK,THRU or which PC/AUTH issued at the time of the original
the UNSTACK,TO parameter, but the current failure.
PCLINK stack element chain was empty.
v For reason code X'xx99': Look in the SDWA variable
1212 The specified token was for a PCLINK stack recording area (SDWAVRA) for a PC/AUTH control
element (STKE) that is not on the PCLINK block that is not valid.
stack element chain. Register 2 contains the v For reason code X'0112': Change the application
token. program to use fewer linkage indexes (LXs) or
13yy The program issued a PCLINK macro with the change the limit of system LXs with the NSYSLX
EXTRACT parameter. parameter in the IEASYSxx parmlib member.
48 z/OS V1R10.0 MVS System Codes
053
If you cannot correct the problem, search problem disconnect queue block (FDQB) in the program
reporting data bases for a fix for the problem. If no fix PC/AUTH address space’s pageable storage.
exists, contact the IBM Support Center. Provide the The request failed. Register 5 contains the
SVC dump, including the system trace table, and the return code from the request.
logrec data set error record.
0209 PC/AUTH requested that a force disconnect
queue block (FDQB) in the PC/AUTH address
The reason codes in Register 15 are:
space’s pageable storage be freed. The
Code Explanation request failed. Register 5 contains the return
code from the request.
01yy The program issued an LXRES macro.
020A PC/AUTH requested that a dynamic work area
0101 PC/AUTH requested dynamic work area be freed, but the request failed. Register 5
storage, but the request failed. Register 5 contains the return code from the request.
contains the return code from the request.
0211 PC/AUTH was building the force disconnect
0105 PC/AUTH requested storage for a new linkage queue (FDQ) to process a FORCE request.
index allocation table (LXAT) in the pageable The service found more than one connection
storage of (PC/AUTH) address space. The description (ETIXCD) with the same address
request failed. Register 5 contains the return space identifier(ASID)/linkage index (LX)
code from the request. values while searching the entry table
0109 PC/AUTH requested that an old linkage index information block (ETIB) chain.
allocation table (LXAT) in the PC/AUTH 0297 An unexpected error occurred. Another abend
address space’s pageable storage be freed. occurred while PC/AUTH was processing. The
The request failed. Register 5 contains the system converted this abend to X'053'. Look in
return code from the request. the SDWA variable recording area (SDWAVRA)
010A PC/AUTH requested that a dynamic work area for the original abend and reason codes and
be freed, but the request failed. Register 5 continue diagnosis with that code.
contains the return code from the request. 0298 PC/AUTH previously failed and cannot process
0111 PC/AUTH could not reserve one or more requests.
linkage indexes (LX) because the maximum 0299 The acronym at the beginning of a PC/AUTH
number of LXs the system supports would be control block is incorrect. Register 5 contains
exceeded. Register 5 contains the number of the expected acronym.
LXs that are currently unreserved.
03yy The program issued an ETCRE macro.
0112 The program tried to reserve more system
linkage indexes (system LXs) then were 0301 PC/AUTH requested storage for a dynamic
available. The total number of system linkage work area, but the request failed. Register 2
indexes is the sum of the number of LXs in the contains the return code from the request.
system function table and the value of the
0302 PC/AUTH requested storage in the system
NSYSLX parameter of the IEASYSxx parmlib
queue area (SQA), but the request failed.
member. The default value for NSYSLX is 165.
Register 2 contains the return code from the
0197 An unexpected error occurred. Another abend request.
occurred while PC/AUTH was processing. The
0303 PC/AUTH requested storage in the PC/AUTH
system converted the abend to X'053'. Look in
address space’s local system queue area
the SDWA variable recording area (SDWAVRA)
(LSQA). The request failed. Register 2 contains
for the original abend and reason codes and
the return code from the request.
continue diagnosis with that code.
0305 PC/AUTH requested storage in the PC/AUTH
0198 PC/AUTH previously failed and cannot process
address space’s pageable storage. the request
requests.
failed. Register 2 contains the return code from
0199 The acronym at the beginning of a PC/AUTH the request.
control block is incorrect. Register 5 contains
0306 PC/AUTH requested that storage in the system
the expected acronym.
queue area (SQA) be freed, but the request
02yy The program issued an LXFRE macro. failed. Register 2 contains the return code from
the request.
0201 PC/AUTH requested storage for a dynamic
work area, but the request failed. Register 5 0307 PC/AUTH requested that storage in the
contains the return code from the request. PC/AUTH address space’s local system queue
0205 PC/AUTH requested storage for a new force
Chapter 2. System Completion Codes 49
053
area (LSQA) be freed. The request failed. 0501 PC/AUTH requested storage for a dynamic
Register 2 contains the return code from the work area, but the request failed. Register 2
request. contains the return code from the request.
0309 PC/AUTH requested that storage in the 0503 PC/AUTH requested storage in the PC/AUTH
PC/AUTH address space’s pageable storage address space’s local system queue area
area be freed. The request failed. Register 2 (LSQA). The request failed. Register 2 contains
contains the return code from the request. the return code from the request..
030A PC/AUTH requested that a dynamic work area 0505 PC/AUTH requested storage in the PC/AUTH
be freed, but the request failed. Register 2 address space’s pageable storage. the request
contains the return code from the request. failed. Register 2 contains the return code from
the request.
0397 An unexpected error occurred. Another abend
occurred while PC/AUTH was processing and 0507 PC/AUTH requested that storage in the
the system converted the abend to X'053'. PC/AUTH address space’s local system queue
Look in the SDWA variable recording area area (LSQA) be freed. The request failed.
(SDWAVRA) for the original abend and reason Register 2 contains the return code from the
codes and continue diagnosis with that code. request.
0398 PC/AUTH previously failed and cannot process 050A PC/AUTH requested that a dynamic work area
requests. be freed, but the request failed. Register 2
contains the return code from the request.
0399 The acronym at the beginning of a PC/AUTH
control block is incorrect. Register 2 contains 0597 An unexpected error occurred. Another abend
the expected acronym. occurred while PC/AUTH was processing and
the system converted the abend to X'053'.
04yy The program issued an ETDES macro.
Look in the SDWA variable recording area
0401 PC/AUTH requested storage for a dynamic (SDWAVRA) for the original abend and reason
work area, but the request failed. Register 2 codes and continue diagnosis with that code.
contains the return code from the request.
0598 PC/AUTH previously failed and cannot process
0406 PC/AUTH requested that storage in the system requests.
queue area (SQA) be freed, but the request
0599 The acronym at the beginning of a PC/AUTH
failed. Register 2 contains the return code from
control block is incorrect. Register 2 contains
the request.
the expected acronym.
0407 PC/AUTH requested that storage in the
06yy The program issued an ETDIS macro.
PC/AUTH address space’s local system queue
area (LSQA) be freed. The request failed. 0601 PC/AUTH requested storage for a dynamic
Register 2 contains the return code from the work area, but the request failed. Register 2
request. contains the return code from the request.
0409 PC/AUTH requested that storage in the 0609 PC/AUTH requested that storage in the
PC/AUTH address space’s pageable storage PC/AUTH address space’s pageable storage
be freed. The request failed. Register 2 area be freed. The request failed. Register 2
contains the return code from the request. contains the return code from the request.
040A PC/AUTH requested that a dynamic work area 060A PC/AUTH requested that a dynamic work area
be freed, but the request failed. Register 2 be freed, but the request failed. Register 2
contains the return code from the request. contains the return code from the request.
0497 An unexpected error occurred. Another abend 0697 An unexpected error occurred. Another abend
occurred while PC/AUTH was processing and occurred while PC/AUTH was processing and
the system converted the abend to X'053'. the system converted the abend to X'053'.
Look in the SDWA variable recording area Look in the SDWA variable recording area
(SDWAVRA) for the original abend and reason (SDWAVRA) for the original abend and reason
codes and continue diagnosis with that code. codes and continue diagnosis with that code.
0498 PC/AUTH previously failed and cannot process 0698 PC/AUTH previously failed and cannot process
requests. requests.
0499 The acronym at the beginning of a PC/AUTH 0699 The acronym at the beginning of a PC/AUTH
control block is incorrect. Register 2 contains control block is incorrect. Register 2 contains
the expected acronym. the expected acronym.
05yy The program issued an ETCON macro. 07yy The program issued an AXRES macro.
50 z/OS V1R10.0 MVS System Codes
053
0701 PC/AUTH requested storage for a dynamic 090A PC/AUTH requested that a dynamic work area
work area, but the request failed. Register 4 be freed, but the request failed. Register 4
contains the return code from the request. contains the return code from the request.
0705 PC/AUTH requested storage in the PC/AUTH 0997 An unexpected error occurred. Another abend
address space’s pageable storage. the request occurred while PC/AUTH was processing and
failed. Register 4 contains the return code from the system converted the abend to X'053'.
the request. Look in the SDWA variable recording area
(SDWAVRA) for the original abend and reason
0709 PC/AUTH requested that storage in the
codes and continue diagnosis with that code.
PC/AUTH address space’s pageable storage
area be freed. The request failed. Register 4 0998 PC/AUTH previously failed and cannot process
contains the return code from the request. requests.
070A PC/AUTH requested that a dynamic work area 0999 The acronym at the beginning of a PC/AUTH
be freed, but the request failed. Register 4 control block is incorrect. Register 4 contains
contains the return code from the request. the expected acronym.
0712 PC/AUTH cannot satisfy the request because 0Ayy The program issued an AXSET macro.
the authorization index (AX) count would cause
0A01 PC/AUTH requested storage for a dynamic
the total number of AXs to exceed the
work area, but the request failed. Register 4
maximum number that the system supports.
contains the return code from the request.
Register 4 contains the AX count for the
request. 0A0A PC/AUTH requested that a dynamic work area
be freed, but the request failed. Register 4
0797 An unexpected error occurred. Another abend
contains the return code from the request.
occurred while PC/AUTH was processing and
the system converted the abend to X'053'. 0A30 An unexpected error occurred before the
Look in the SDWA variable recording area service set the authorization index (AX) of the
(SDWAVRA) for the original abend and reason home address space.
codes and continue diagnosis with that code.
0A31 An unexpected error occurred after the service
0798 PC/AUTH previously failed and cannot process set the authorization index (AX) of the home
requests. address space, but before the bind break
routine could break all binds to other address
0799 The acronym at the beginning of a PC/AUTH
spaces.
control block is incorrect. Register 4 contains
the expected acronym. 0A32 An unexpected error occurred after the service
set the authorization index (AX) of the home
08yy The program issued an AXFRE macro.
address space and the bind break routine
0801 PC/AUTH requested storage for a dynamic broke all binds to other address spaces.
work area, but the request failed. Register 4
0A97 An unexpected error occurred. Another abend
contains the return code from the request.
occurred while PC/AUTH was processing and
080A PC/AUTH requested that a dynamic work area the system converted the abend to X'053'.
be freed, but the request failed. Register 4 Look in the SDWA variable recording area
contains the return code from the request. (SDWAVRA) for the original abend and reason
codes and continue diagnosis with that code.
0897 An unexpected error occurred. Another abend
occurred while PC/AUTH was processing and 0A98 PC/AUTH previously failed and cannot process
the system converted the abend to X'053'. requests.
Look in the SDWA variable recording area
0A99 The acronym at the beginning of program
(SDWAVRA) for the original abend and reason
PC/AUTH control block is incorrect. Register 4
codes and continue diagnosis with that code.
contains the expected acronym.
0898 PC/AUTH previously failed and cannot process
0Byy The program issued an ATSET macro.
requests.
0B01 PC/AUTH requested storage for a dynamic
0899 The acronym at the beginning of program
work area, but the request failed. Register 4
PC/AUTH control block is incorrect. Register 4
contains the return code from the request.
contains the expected acronym.
0B03 PC/AUTH requested storage in the PC/AUTH
09yy The program issued an AXEXT macro.
address space’s local system queue area
0901 PC/AUTH requested storage for a dynamic (LSQA). The request failed. Register 4 contains
work area, but the request failed. Register 4 the return code from the request.
contains the return code from the request.
Chapter 2. System Completion Codes 51
053
0B07 PC/AUTH requested that storage in the dynamic work area be freed, but the request
PC/AUTH address space’s local system queue failed. Register 2 contains the return code from
area (LSQA) be freed. The request failed. the request.
Register 4 contains the return code from the
0C97 An unexpected error occurred. Another abend
request.
occurred while PC/AUTH was processing and
0B0A PC/AUTH requested that a dynamic work area the system converted the abend to X'053'.
be freed, but the request failed. Register 4 Look in the SDWA variable recording area
contains the return code from the request. (SDWAVRA) for the original abend and reason
codes and continue diagnosis with that code.
0B30 An unexpected error occurred before the
service set the authorization bits in the 0C99 The acronym at the beginning of a PC/AUTH
authorization table (AT) of the home address control block is incorrect. Register 2 contains
space. the expected acronym.
0B31 An unexpected error occurred after the service 0CC1 The ASCBAXR count in the address space
set the authorization bits in the authorization control block (ASCB) for the ending address
table (AT) of the home address space, but space was too low.
before the bind break routine broke all binds to
0CC2 The ASCBLXR count in the address space
other address spaces.
control block (ASCB) for the ending address
0B32 An unexpected error occurred after the service space was too low.
set the authorization bits in the authorization
0CC3 The bind break routine issued a non-zero
table (AT) of the home address space and the
return code.
bind break routine broke all binds to other
address spaces. 0Dyy The Program Call authorization functional
recovery routine (PC/AUTH FRR), detected an
0B97 An unexpected error occurred. Another abend
error. For any yy value except 88 and 89, the
occurred while PC/AUTH was processing and
PC/AUTH FRR detected an incorrect
the system converted the abend to X'053'.
service-in-control code and cannot determine
Look in the SDWA variable recording area
which PC/AUTH service is running; the dump
(SDWAVRA) for the original abend and reason
title contains PCRAEERC =nnnn, where nnnn
codes and continue diagnosis with that code.
is the value in the PCRAEERC field of the
0B98 PC/AUTH previously failed and cannot process Program Call recovery area (PCRA) at the time
requests. the FRR got control.
0B99 The acronym at the beginning of a PC/AUTH 0D88 The FRR received return code X'18' after
control block is incorrect. Register 4 contains single-threaded queue verification.
the expected acronym.
0D89 The FRR received return code X'18' after
0Cyy PC/AUTH resource manager detected an error. double-threaded queue verification.
0C01 The resource manager requested storage for a 11yy The program issued a PCLINK macro with the
dynamic work area, but the request failed. STACK parameter.
Register 2 contains the return code from the
1110 PC/AUTH requested storage for storage in the
request.
common storage area (CSA). the request
0C06 The resource manager requested that storage failed. Register 2 contains the return code from
in the system queue area (SQA) be freed, but the request.
the request failed. Register 2 contains the
12yy The program issued a PCLINK macro with the
return code from the request.
UNSTACK parameter.
0C07 The resource manager requested that storage
1211 On the stack element queue (STKE), one of
in the PC/AUTH address space’s local system
the pointers to the next STKE is incorrect.
queue area (LSQA) be freed. The request
Register 2 contains the incorrect pointer.
failed. Register 2 contains the return code from
the request. 1212 On the stack element queue, one of the fields
containing the address space identifier (ASID)
0C09 The resource manager requested that storage
of the next stack element (STKE) is incorrect.
in the PC/AUTH address space’s pageable
Register 2 contains the incorrect ASID.
storage be freed. The request failed. Register 2
contains the return code from the request. 1297 The cause of the error is unknown. Look in the
SDWA variable recording area (SDWAVRA) for
0C0A The resource manager requested that a
the original abend and reason codes issued by
52 z/OS V1R10.0 MVS System Codes
054 • 055
the PCLINK macro. The abend code is in the 1 2 3 4 5
VRAOA field and the reason code is in the 6 7 8 9 10
VRAOR15 field. 11 12 13 14 15
14yy An error occurred during PC/AUTH 16 17 18 19 20
initialization. The system does not write an 21 23 24 25 26
SVC dump or a logrec data set error record. 27 29 30 31 32
33 34 35 36 37
1411 A program received a non-zero return code 38 39 40 41 42
from the system address space creation. 43 100
Register 2 contains the original return code
and register 3 contains the original reason
code. System action: The system abnormally ends SJF
processing.
1412 A routine received a non-zero return code from
the system address space initialization. System programmer response: Search problem
Register 2 contains the original return code reporting data bases for a fix for the problem. If no fix
and register 3 contains the original reason exists, contact the IBM Support Center.
code. Source: Scheduler JCL facility (SJF)
1413 A routine issued the NUCLKUP macro but the
system was unable to process the request. 055
Register 2 contains the original return code
and register 3 contains the parameter passed Explanation: The system found an error while
to NUCLKUP. processing a listen or signal request for event
notification. Register 15 contains a hexadecimal reason
1414 The sum of the highest linkage index (LX) code that explains the error:
value in the system function table (SFT) and
the value in the SVTNSLX field of the system Code Explanation
vector table (SVT) is greater than decimal 24 The storage containing the requestor’s event
1023. This condition indicates that the SFT or parameter list was overlaid after initial
the SVT was incorrectly modified. Register 2 validation.
contains the highest LX value in the SFT, and
register 3 contains the value in the SVTNSLX 28 An error occurred in one of the listen requests
field. waiting to be processed.
1415 The routine received an incorrect return code 30 An ENF signal pre-processing routine returned
from the bind break. Register 2 contains the a non-valid return code.
return code.
34 During ENF initialization, ENF could not obtain
15yy A PC/AUTH service abnormally ended. the address of a needed signal pre-processing
routine.
1501 An unexpected error occurred while updating
the primary address space number (PASN) 38 The control blocks representing a listen request
access list. contain instructions that are not valid for
comparing the listener’s bit-mapped qualifier
Source: Program Call/authorization (PC/AUTH) with the bit-mapped qualifier associated with
the current event.
054 3C The system could not create the IEFSCHAS
Explanation: An unrecoverable error occurred when a address space. Time-of-error registers 2 and 3
program requested a scheduler JCL facility (SJF) contain the return and reason codes,
service. respectively, from the ASCRE macro.
The error is internal. The valid reason codes, in decimal 40 The system could not join or create ENF’s XCF
format, to report to the IBM Support Center are as group. Time-of-error registers 2 and 3 contain
follows: the return and reason codes, respectively, from
the IXCJOIN macro.
Reason Codes:
44 The system could not obtain information about
the other members of ENF’s XCF group.
Time-of-error registers 2 and 3 contain the
return and reason codes, respectively, from the
IXCQUERY macro.
48 The system could not send an event
notification to other systems in the sysplex.
Chapter 2. System Completion Codes 53
056 • 058
Time-of-error registers 2 and 3 contain the
057
return and reason codes, respectively, from the
IXCMSGO macro. Explanation: The error occurred during processing of
the graphic attention service routine for the IBM 2250
4C The system could not receive an event
Display Unit. The routine referred to a unit control block
notification from some other system in the
(UCB) that was associated with a device other than a
sysplex. Time-of-error registers 2 and 3 contain
graphic device. The routine obtained the reference to
the return and reason codes, respectively, from
the unit control block through a data control block
the IXCMSGI macro.
(DCB). The user gives the routine the addresses of data
System action: For reason code X'34', ENF control blocks through the poll list address in the first
initialization fails. For reason codes X'3C', X'40', and operand of the ANALYZ macro instruction or the
X'44', ENF sysplex-wide notification is not available. For address of one data control block through the list item
all other reason codes, the system abnormally ends the address in the first operand of the GSERV macro
current task. All other processing continues. instruction. The DCBDEBAD field in the data control
block points to a data extent block (DEB), which in turn
Application Programmer Response: Respecify the points to the unit control block. The unit control block is
data on the event parameter list. used by the control program to obtain information about
System programmer response: If the problem an I/O; each unit control block is associated with one
persists, search problem reporting data bases for a fix I/O device.
for the problem. If no fix exists, contact the IBM Support Application Programmer Response: Check the first
Center. operand in the ANALYZ or GSERV macro instruction to
Source: Event notification facility (ENF) make sure that it correctly specified the poll list address
or list item address. If the first operand was correct,
make sure that the macro expansion and the data
056 control block were not incorrectly modified by program
Explanation: The error occurred during processing of errors. After correcting the error, run the job step again.
the graphic attention service routine for the IBM 2250 System programmer response: If the error recurs
Display Unit. The routine referred to an incorrect unit and the program is not in error, look at the messages in
control block (UCB). The routine obtained the reference the job log for more information. Search problem
to the unit control block through a data control block reporting data bases for a fix for the problem. If no fix
(DCB). The user gives the routine the addresses of data exists, contact the IBM Support Center. Provide the JCL
control blocks through the poll list address in the first and the program listing for the job.
operand of the ANALYZ macro instruction or the
address of a data control block through the list item Source: DFSMSdfp
address in the first operand of the GSERV macro
instruction. The DCBDEBAD field in the data control 058
block points to a data extent block (DEB), which in turn
points to the unit control block. The unit control block is Explanation: Supervisor control detected an error
used by the control program to obtain information about when establishing a work unit’s cross memory
an I/O device; each unit control block is associated with environment. Register 15 contains a hexadecimal
one I/O device. reason code to be used when searching problem
reporting data bases or when reporting the problem to
Application Programmer Response: Check the first the IBM Support Center. The reason code in register 15
operand in the ANALYZ or GSERV macro instruction to is one of the following:
make sure that it correctly specified the poll list address
or list item address. If the first operand was correct, Code Explanation
make sure that the macro expansion and the data
00 An attempt to establish a cross memory
control block were not incorrectly modified by program
environment failed. The target ASID was not
errors. After correcting the error, run the job step again.
valid for the cross memory address.
System programmer response: If the error recurs
04 The work unit’s primary address space job step
and the program is not in error, look at the messages in
task has ended. The low order halfword of
the job log for more information. Search problem
register 12 contains the primary ASID number.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL 08 The work unit had addressability to an incorrect
and the program listing for the job. primary ASID. The low order halfword of
register 12 contains the primary ASID number.
Source: DFSMSdfp
Termination of the primary address space is
the likely cause of this error.
0C The work unit’s secondary address space job
54 z/OS V1R10.0 MVS System Codes
059
step task has ended. The low order halfword of 2. Search problem reporting data bases for a fix for the
register 11 contains the secondary ASID | problem. If no fix exists, and the abend is not
number. | expected (e.g. the unit of work owning the cross
| memory resources was not ended), ask the operator
10 The work unit had addressability to an incorrect
to set a SLIP trap to obtain an SVC dump. Contact
secondary ASID. The low order halfword of
the component group associated with this module at
register 11 contains the secondary ASID
the IBM Support Center. Provide the SVC dump, the
number. Termination of the secondary address
reason code of the failure, and, if available, the
space is the likely cause of this error.
logrec data set error record.
14 Internal error. Contact the IBM Support Center.
Source: Supervisor control
18 Internal error. Contact the IBM Support Center.
1C Internal error. Contact the IBM Support Center. 059
20 Internal error. Contact the IBM Support Center. Explanation: Supervisor control detected an error
during stop or reset processing. A hexadecimal reason
24 Internal error. Contact the IBM Support Center. code in register 15 explains the error:
28 An attempt to establish a cross memory Code Explanation
address failed. The ASCB for the target ASID
did not pass validity checks. The first four 00 Stop processing received as input a disabled
bytes of the target ASCB did not contain the program status word (PSW).
character ’ASCB’. Register 12 contains the
08 An unrecoverable error occurred during
address of the invalid ASCB.
stop/reset processing.
2C The work unit had addressability to an incorrect
0C Stop processing detected a request to stop a
primary ASID. The low order halfword of
task with an unlocked task control block (TCB).
register 12 contains the primary ASID number.
The task was already stopped.
Termination of the primary address space is
the likely cause of this error. 10 Reset processing detected a request to reset a
locked TCB. The task did not hold a local lock
30 The work unit had addressability to an incorrect
or cross memory local (CML) lock.
secondary ASID. The low order halfword of
register 11 contains the secondary ASID 14 Reset processing detected a request to reset a
number. Termination of the secondary address locked TCB, but the address space control
space is the likely cause of this error. block (ASCB) lockword did not contain a
suspend value of X'7FFFFFFF'.
34 Internal error. Contact the IBM Support Center.
18 A program requested that functional recovery
38 Internal error. Contact the IBM Support Center.
routines (FRR) be deleted from the normal
3C Internal error. Contact the IBM Support Center. stack, but the program is not currently running
with the normal stack.
For the above listed reason codes, this abend may be 1C Stop/reset processing was unable to obtain a
normal. That is, if a work unit’s primary or secondary linkage stack for a routine running under a
address space ends or if the primary or secondary service request block (SRB).
address space job step task ends, the required cross
memory connection cannot be made and the work unit 20 Reset processing detected a request to reset a
abnormally ends with abend X'058'. Use the reason locked SRB, but the ASCB lockword did not
code to perform a search in the IBM database and contain the suspend value X'7FFFFFFF'.
indicate the findings when reporting the problem to the
System action: The system abnormally ends the
IBM Support Center.
program that requested the stop or reset processing.
System action: The system abnormally ends the The system may write a logrec data set error record.
program that requested the cross memory service. The
Operator response: If the system programmer asks
system may write a logrec data set error record.
for an SVC dump, set the following SLIP trap:
Operator response: If the system programmer asks SLIP SET,COMP=059,ACTION=SVCD,END
for an SVC dump, set the following SLIP trap:
System programmer response: Do the following:
SLIP SET,COMP=058,ACTION=SVCD,END
1. For reason code X'08' or X'1C', ask the operator to
System programmer response: Do the following: set a SLIP trap to obtain an SVC dump. Contact the
1. Use the address in register 14 at the time of error to supervisor control component group at the IBM
identify the module that requested the cross memory Support Center. Provide the SVC dump and, if
services. available, the logrec data set error record.
Chapter 2. System Completion Codes 55
05A • 05C
2. For any other reason code, use the address in
05C
register 14 at the time of error to identify which
module requested stop or reset processing. Explanation: An error occurred during allocation of the
v For an installation-provided module, continue data sets for a job step. Register 15 contains a
diagnosis with the module. hexadecimal reason code that you should report to the
IBM Support Center.
v For an IBM module, search problem reporting
data bases for a fix for the problem. If no fix | The following are valid hexadecimal reason codes, for
exists, ask the operator to set a SLIP trap to | cases where the system programmer might or might not
obtain an SVC dump. Contact the component | be able to take corrective actions. There are other
group associated with this module at the IBM | internal reason codes that are not listed here. For any
Support Center. Provide the SVC dump and, if | reason code not documenented here, contact the IBM
available, the logrec data set error record. | Support Center.
Source: Supervisor control Code Explanation
001 System address space initialization
05A denied the request to create the
allocation address space.
Explanation: Supervisor control detected an error in a
request to free a service request block (SRB) or to free 002 The allocation address space received
a suspended SRB (SSRB). Register 15 contains a a nonzero return code from GETMAIN
hexadecimal reason code to be used when searching processing.
problem reporting data bases or when reporting the
003 The display allocation tables manager
problem to the IBM Support Center.
received a request which, if
System action: The system abnormally ends the processed, would cause the
program that tried to free the SRB or SSRB. The DALTUSE count to be less than zero.
system may write a logrec data set error record.
004 An allocation module issued the
Operator response: If the system programmer asks POST macro instruction, and the
for an SVC dump, set the following SLIP trap: macro processing has entered the
SLIP SET,COMP=05A,ACTION=SVCD,END routine specified on the ERRET
parameter.
System programmer response: Do the following:
005 An allocation module issued the
1. Use the address in register 14 at the time of error to
ESTAE macro instruction, and the
identify the module that tried to free an SRB or an
return code from ESTAE processing
SSRB.
was not zero.
2. Search problem reporting data bases for a fix for the
problem. If no fix exists, and no dump was written 006 An allocation module issued the
with the abend, ask the operator to set a SLIP trap STIMERM macro instruction, and the
to obtain an SVC dump. Contact the component macro processing has entered the
group associated with this module at the IBM routine specified on the ERRET
Support Center. Provide the dump used, the reason parameter.
code of the failure, and, if available, the logrec data 101 The ATTACH macro instruction was
set error record. issued for the eligible device table
Source: Supervisor control (EDT) verification routine during
allocation initialization processing. The
return code from the ATTACH routine
05B was not zero.
Explanation: A system service running in service 102 An error occurred during an RESMGR
request block (SRB) mode issued an SRBTIMER macro ADD TYPE(ADDRSPC) when
to set a processing time limit. When the time limit establishing the ATS Address Space
expired, timer supervision ended the service. Resource Manager.
System action: The system abnormally ends the 103 An error occurred during an RESMGR
system service. ADD TYPE(TASK) when establishing
Operator response: Retain the logrec data set error the ATS Task Resource Manager.
records. Contact hardware support. 200 IEFAB4F7 was called to read a single
Source: Timer supervision SWA block, and the SWAREQ was
unsuccessful.
201 Allocation was invoked during DDR
56 z/OS V1R10.0 MVS System Codes
05C
SWAP to update the unit control block 238 Recovery was entered after an abend
(UCB) pointer list (UPL) so that the or cancel and the ATS Service
UPL would reflect the swapped UCBs. Routines Recovery block (IEFZATRB)
However, one or both of the swapped or Allocation Automatic Tape Sharing
UCB addresses is not in the UPL. (ATS) Parameter List (IEFZATSP)was
corrupted. The address space has
202 Invalid UCB address.
been taken down to clean up ATS
203 IEFAB4FP discovered that SIOTDDIB ENQs and Latches.
does not point to a DDIB.
240 An Autoswitchable (AS) device
210 Invalid JCT in the JSCB. chosen for allocation is not assigned.
211 Invalid SCT in the JSCB. 241 DDR Swap failed because GRS failed
trying to swap Device ENQs.
212 Invalid ACT in the JCT.
243 IEFASWAP failed, issued against the
213 Invalid ACT in the SCT. target task.
214 Invalid SVA found in IEFAB4FE. 244 IEFASWAP failed, issued against the
220 Device is not automatically switchable DDR/SWAP task.
for a function that requires it. 245 ENQ/DEQ for Tape device failed.
221 Device is not registered to this 246 Allocation Recovery is unable to verify
system. all Automatic Tape Sharing (ATS)
224 Device type ENQ not held before Device ENQs have been released.
requesting more than one Device 253 A loop was detected in Queue
ENQ on a single request. Manager Queue Control Block.
225 Device ENQ not held before 254 Detected a corrupted hash value.
requesting a function on a device that
requires it. 255 The request attempted to assign
ownership to another TCB
226 Needed device array was not passed unconditionally.
to the IEFAB4FX service.
257 Error in determining the UCB common
227 Needed device type array was not extension address by IOS.
passed to the IEFAB4FX service.
301 At the end of processing all allocation
228 Invalid function request for the requests for a job step, an unsatisfied
IEFAB4FX service. request is detected. An incorrectly
229 Individual General Device Element modified eligible device table (EDT) or
(IGDE) not found. specifying VSAM parameters for a
non-VSAM data set is the probable
230 NED not found for self-describing cause.
device.
303 Error encountered in the EDL storage
231 Invalid Queue Manager Queue Block manager.
Chain (used by QMQBLK processing,
not IEFAB4FX) 304 Unexpected return code for
IEFAB480.
232 Unrecognized return code from
IEFOIGDE methods. 305 Either the EDT library section does
not exist or an error occurred while
233 IGDE was not built when it was obtaining the library names from the
expected to be. current configuration.
234 TCB and/or ASCB address not 306 IEFAB480 found a cost adjustment
supplied when requesting clean up for value of zero which would fail to
terminating TCB or ASCB. decrease any transformed costs
235 Non-zero return code received from (TCs).
?IXCMSGO. 307 IEFAB480 found an edge with a valid
236 IGDE not owned when it should have transformed cost (TC), but never
been. adjusted the transformed cost.
237 Attempt to push a non-AS device. 308 Two jobs are allocated to the same
tape drive.
Chapter 2. System Completion Codes 57
05D
309 Devices selected by JES3 are not in IEFMSGBL) was attempting to build a
the Allocation Eligible Device List message, but the message text was
(EDL). Check the Job Log of the too long.
failing job for messages
701 The scheduler JCL facility (SJF)
IEF202I/IEF272I. Message IEF202I
returned an unexpected return code
indicates that a previous step was not
or reason code.
run because of:
v condition codes 702 SVC 99 caller does not hold the
SYSZTIOT resource and has
v COND=even
requested that TIOT resource be
v COND=only obtained.
Message IEF272I indicates that a 704 SIOT to be dechained is not found in
previous step was not executed. the SIOT chain.
311 Array bounds were exceeded for an 804 Allocation tried to remove a DSAB
internal control block during Tape entry from the dynamic
Device Allocation. Contact the IBM communication table, but the entry did
Support Center and provide the dump. not exist.
313 Internal error in the allocation dynamic 807 Allocation tried to mark a DSAB entry
storage manager. in the dynamic communication table
30A Invalid JCT in the JSCB. as eligible for remove in-use
processing, but the entry did not exist.
30B Invalid first SCT in the JCT.
80B Allocation tried to change the TCB
30C Invalid next SCT in the SCT. address of a DSAB entry in the
30D An allocation module called SMS for dynamic communication table, but the
the Data Set Stacking operation. SMS entry did not exist.
returned an unrecognized return code. 8FF Allocation’s dynamic communication
30E An allocation module called SMS for table manager was called with an
the Device Pool Services. SMS invalid function code.
returned an unrecognized return code. | xxxxxA90 The system takes a dump for
30F SIOT not found for affed DD | diagnostic purposes because it could
(UNIT=AFF). Issued from IEFAB4FE. | not allocate one or more devices to a
| step. Contact the system programmer.
501 Undefined return code from JES3.
System action: The system issues message IEF100I
604 IEFAB4MG (called by macro or message IEF197I with the abend code and the
IEFMSGBL) was attempting to build a reason code. The system stops allocation processing for
message, but no message definition the step. The system ends the job, writes an SVC
was found. dump, and writes a logrec data set error record.
608 IEFAB4MG (called by macro For reason code 229, if the number of the device can
IEFMSGBL) was attempting to build a be determined, message IEF707I is issued indicating
message, but the SIOT pointer the device number.
required for this message was not
found. System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
60C IEFAB4MG (called by macro exists, contact the IBM Support Center.
IEFMSGBL) was attempting to build a
message, but an incorrect number of For reason code 229, message IEF707I might be issued
variables was supplied. to indicate the number of the device that cannot be
found. If IEF707I is issued, see the Operator Response
610 IEFAB4MG (called by macro and System Programmer Response for that message.
IEFMSGBL) was attempting to build a
message, but an invalid buffer was Source: Allocation/unallocation
passed.
614 IEFAB4MG (called by macro 05D
IEFMSGBL) was attempting to build a Explanation: A program issued a CALLDISP macro
message, but no storage was defined that is not valid. A hexadecimal reason code in register
for the message buffer. 15 explains the error:
618 IEFAB4MG (called by macro
58 z/OS V1R10.0 MVS System Codes
05E
Code Explanation
05E
00 The program is disabled and has super bits
Explanation: A program issued the SRBSTAT macro,
set.
but this program either:
04 The current functional recovery routine (FRR) v Is in an environment that is not valid
stack is not the normal FRR stack. v Specified parameters that are not valid
08 The macro specified FRRSTK=SAVE while the A hexadecimal reason code in register 15 explains the
program holds a lock, or the macro specified error:
FRRSTK=NOSAVE while the program holds a
Code Explanation
lock other than the LOCAL lock or the cross
memory local (CML) lock. 00 The program holds a lock.
0C The program is the first level of the recovery 04 The current functional recovery routine (FRR)
termination manager (RTM1), a service stack is not the normal FRR stack.
invoked by RTM1, or an FRR.
08 The program has super bits set.
10 The program was not in task control block
0C The program is not in service request block
(TCB) mode.
(SRB) mode.
14 Register 0, on input, contained a function code
10 The program is disabled.
that is not valid.
14 The first level of the recovery termination
18 Register 1, on input, did not contain 0.
manager (RTM1), a service invoked by RTM1,
System action: The system abnormally ends the or an FRR used the RESTORE parameter on
program that issued the CALLDISP macro. The system the SRBSTAT macro.
may write a logrec data set error record.
18 The PCLINK stack header was not zero on
Operator response: If the system programmer asks entry to processing for the RESTORE
for an SVC dump, set the following SLIP trap: parameter of the macro.
SLIP SET,COMP=05D,ACTION=SVCD,MATCHLIM=1,END 1C The program specified RESTORE or MODIFY
System programmer response: Do the following: on the macro, and the status save area does
not contain valid status.
1. Ask the operator to set a SLIP trap to obtain an
SVC dump. 20 Processing for the RESTORE parameter of the
2. Analyze the dump to see if the program that macro scheduled an SRB to obtain correct
abended was entered by a Supervisor Call (SVC) or processor affinity, but the SRB was unable to
Branch instruction, as follows. In the system trace, run.
look for an SVC X'74' entry. Routing code 08 will be 24 The program specified MODIFY on the macro,
in the UNIQUE-1 column. but register 0 contains a MODIFY identifier
v If found, the program was entered by an SVC code that is not valid.
instruction. Use the address in the PSW ADDR
System action: The system abnormally ends the
column for this SVC entry to identify the module
program that issued the SRBSTAT macro. The system
that issued the CALLDISP macro.
may write a logrec data set error record.
v If not found, the program was entered by a
Branch instruction. Register 14 contains the Operator response: If the system programmer asks
address of the caller. Use the address in register for an SVC dump, set the following SLIP trap:
14 to identify the module that issued the SLIP SET,COMP=05E,ACTION=SVCD,END
CALLDISP macro.
System programmer response: Use the address in
3. After identifying the module, do one of the following: register 14 at the time of error to identify the module
v For an installation-provided module, continue that issued the SRBSTAT macro.
diagnosis with the module. v For an installation-provided module, continue
v For an IBM module, search problem reporting diagnosis with the module.
data bases for a fix for the problem. If no fix v For an IBM module, search problem reporting data
exists, contact the component group associated bases for a fix for the problem. If no fix exists, ask
with this module at the IBM Support Center. the operator to set a SLIP trap to obtain an SVC
Provide the SVC dump and, if available, the dump. Contact the component group associated with
logrec data set error record. this module at the IBM Support Center. Provide the
Source: Supervisor control SVC dump and, if available, the logrec data set error
record.
Source: Supervisor control
Chapter 2. System Completion Codes 59
05F • 062
System action: BDT or its subtask end and may issue
05F
a dump. This abend code is accompanied by messages
Explanation: The VSPC address space encountered explaining the error.
an error.
System programmer response: Use the dump and
System action: The VSPC address space and all accompanying codes and messages to determine the
address spaces that depend on the VSPC address cause of the error. For more information, see the z/OS
space are abnormally ended. The system writes a BDT Messages and Codes.
logrec data set error record.
Source: Bulk Data Transfer (BDT)
The system issues messages about the job to the job
log. The system writes an ABEND dump for the failing
061
job step.
Explanation: The error was detected during
Operator response: Notify the system programmer.
processing of a CLOSE macro instruction for a graphic
System programmer response: Look at the data control block.
messages in the job log. If the JOB statement did not
The graphic CLOSE executor issued a DAR macro
specify MSGLEVEL=(1,1), specify it and run the job
instruction for a graphic attention control block (GACB)
again. Obtain the JCL for the job. Obtain the SYSOUT
that was not specified (via a SPAR macro instruction) by
output for the job. Obtain the ABEND dump for the
the closing task.
failing job step. Collect all printed output and output
data sets related to the problem. Obtain the logrec data System action: An abnormal end occurred for the
set error record. task that issued the SPAR macro instruction for the
graphic attention control block.
If the problem recurs and if the program is not in error,
search problem reporting data bases for a fix for the Application Programmer Response: Issue a DAR
problem. If no fix exists, contact the IBM Support macro instruction, for the graphic attention control block,
Center. in the task that issued the SPAR macro instruction,
before the closing task issues the CLOSE macro
Source: Vector processing
instruction. Then run the job step again.
System programmer response: If the error recurs
060
and the program is not in error, look at the messages in
Explanation: Bulk data transfer (BDT), BDT TQI, or a the job log for more information. Search problem
subtask within either address space is ending. One or reporting data bases for a fix for the problem. If no fix
more accompanying error messages explain why. exists, contact the IBM Support Center. Provide the JCL
Register 15 may contain one of the following reason and the program listing for the job.
codes:
Source: DFSMSdfp
Code Explanation
3014 A spool error was detected in BDTINGL. 062
3024 There are more than 300 DYNALLOC and Explanation: The error occurred during processing of
CELLPOOL statements (BDTINGL). a routine of the graphic subroutine package (GSP) for
FORTRAN IV, COBOL, and PL/I.
8000 A non-zero code was returned from the master
ESTAE for BDTINIT. A condition was encountered that produced a return
code equal to or greater than the absolute value
9000 An error was detected in the FAILDAP routine
specified by the programmer as the ‘null’ argument in
in BDTABMN.
the call to the INGSP subroutine. The GSPARRAY field
A000 A non-zero code was returned from the ESTAE in the GSPCB identifies the return code produced,
is BDTGSC1. register 2 contains the address of the status table entry
last invoked, and register 3 contains the address of the
C000 The ABEND macro was issued by BDTINTK. GSPARRAY field.
D000 BDT was unable to register both the FTF and Application Programmer Response: Determine the
NJE features. condition that caused the job step to be abnormally
E000 A non-zero code was returned from the ESTAE ended and change the program accordingly. Then, run
in BDTTQIAS. the job step again.
F000 A non-zero code was returned from the ESTAE System programmer response: If the error recurs
in BDTTQMSG. and the program is not in error, look at the messages in
the job log for more information. Search problem
F800 A non-zero code was returned from the retry reporting data bases for a fix for the problem. If no fix
ESTAE in BDTTQMSG.
60 z/OS V1R10.0 MVS System Codes
063 • 066
exists, contact the IBM Support Center. Provide the JCL 1C The caller’s address did not have
and the program listing for the job. addressability to the home address space.
Source: DFSMSdfp 20 The specified TCB is not the currently active
TCB or a subtask of the currently active TCB.
063 24 The caller issued the SSAFF macro while
holding locks.
Explanation: During processing of a graphic program,
the 2250 operator pressed the CANCEL key on the 28 Unexpected error percolated to system
alphameric keyboard of the display unit. The 2250 recovery.
operator selected either the TERMINATE option or the
System action: The system abnormally ends the
DUMP option on the end option display. The problem
program that issued the SSAFF macro. The system
program was ended either with or without a dump.
writes a logrec data set error record and a dump.
Operator response: If you were having a problem,
Application Programmer Response:
report the conditions that caused you to end the
program to the system programmer. v Reason codes 04, 08, 10, 14, 1C, 20, 24 and 28
indicate an error in the calling program. Fix the
Application Programmer Response: Respond problem using the reason code information and run
according to the information provided by the 2250 the job again.
operator.
v Reason code 0C indicates a system error. Notify the
Source: DFSMSdfp system programmer.
System programmer response: Collect all printed
064 output and output data sets related to the problem.
Search problem reporting data bases for a fix for the
Explanation: An address space that holds a cross
problem. If no fix exists, contact the IBM Support
memory local lock (CML) ended abnormally before it
Center. Provide the logrec data set record and the
freed the lock.
dump.
Note: This abend is directly related to the address Source: Task management
space completion. This abend is informational
and does not need to be pursued independent of
066
the address space completion.
Explanation: The dispatcher of tasks and service
System action: The system gives control to recovery
routines detected an error. A hexadecimal reason code
for CML lock processing. Other system processing
in register 15 explains the error:
continues.
Code Explanation
Source: Supervisor control
04 A completed routine that ran under a service
request block (SRB) held a system lock when it
065
returned to the dispatcher.
Explanation: When processing an SSAFF macro, the
0C A routine that ran under a suspended service
system detected an error.
request block (SSRB) held the cross memory
Register 15 contains a hexadecimal reason code that local (CML) lock of a failing address space.
explains the error: The ASCBFAIL bit is on. The ASCBFAIL bit is
in the address space control block (ASCB) of
Code Explanation the failing address space.
04 The index into the subsystem affinity table 10 The SRBASCB field of an SRB or an SSRB
(SSAT) is greater than the number of points to an ASCB that has an erroneous
subsystems currently defined. acronym.
08 The caller is not in task control block (TCB) 14 A task holds the CML lock of a failing address
mode. space. The ASCBFAIL bit for the failing
0C There is insufficient local system queue area address space is on.
(LSQA) storage to build the SSAT. 18 Status could not be saved for the current task
10 The specified TCB is incorrect. It does not due to an error in the dispatcher.
include the TCB acronym. 1C A task attempted to reenter the dispatcher
14 The caller is disabled. through the SRB entry point.
Chapter 2. System Completion Codes 61
067
20 A routine that ran under an SRB attempted to 00000004 A program encountered a page fault,
reenter the dispatcher through a task entry segment fault, or address space
point. secondary entry table (ASTE) validity
fault on a data space that was
24 Status could not be saved for the current SRB
deleted.
due to an error in the dispatcher.
00000008 The target address space was created
28 Task could not be dispatched because the
after the access list entry (ALE) was
CML lock was stolen.
created.
System action: The system abends the task or SRB
0000000C The interrupted program’s extended
and may write a logrec data set error record.
authority index (EAX) does not have
Operator response: If the system programmer asks Set Storage Address Register (SSAR)
for an SVC dump, set the following SLIP trap: authority to the target address space
SLIP SET,ENABLE,COMP=066 specified by a private ALE.
System programmer response: Do the following: 00000010 The EAX in the ALE does not have
SSAR authority to the target address
1. For reason code X'04', go to step 3. space.
2. For any other reason code, go to step 6.
00000014 An ASTE sequence exception
3. For reason code X'04', if a logrec data set error occurred while attempting to reference
record is not written with the abend, ask the an incorrect or deleted data space.
operator to set a SLIP trap to obtain an SVC dump.
Format the dump to see: 00000018 An unexpected error occurred in the
v Register 2 through register 8 access register translation second
v Register 10 through register 13 level interrupt handler (SLIH).
00000020 An ASTE validity exception occurred
These are the SRB routine’s registers at the time it when a program tried to access a
gave up control. subspace that had been deleted.
4. Check these registers to see if one looks like a base
register, as follows. Look for a group of registers 00000024 An ASTE sequence exception
containing addresses near the same place in occurred when a program tried to
storage. If you find such a group of registers, look access a subspace that had been
for the register with the lowest address. This is deleted.
possibly a base register. Identify the module that is 00000064 A system error occurred during the
using this register as its base register. fetch of a PR, PTI, or SSAIR
5. Determine which lock was held when the problem instruction.
occurred. The current lock held string can be found
00000068 The target PASN or SASN is no
in two different places:
longer valid.
v Register 14 at the time of error
00000072 A system error occurred.
v In the PSACLHS field of the SVCE D trace entry
for abend X'066' 00000076 The desired target PASN or SASN
6. Search problem reporting data bases for a fix for the has a non-matching instance number.
problem. If no fix exists, and an SVC dump has not xxxx0Axx A program attempted to reference a
be obtained, ask the operator to set a SLIP trap to data space that has been deleted.
obtain an SVC dump. Contact the IBM Support
Center. Provide: xxxx0Bxx An unexpected error occurred when
v The SVC dump the system tried to bring a data space
v The system trace page into real storage.
v The logrec data set error record, if available System action: The system abends the task and
Source: Supervisor control writes an ABEND dump for the failing job step.
System programmer response: Do the following:
067 1. Obtain the ABEND dump for the failing job step. If
the JCL for the step did not contain a DD statement
Explanation: An access register translation exception
for an ABEND dump, add a SYSMDUMP DD
occurred. A hexadecimal reason code in register 15
statement.
explains the error; x in the reason code contains
diagnostic data: 2. Find the reason code in register 15.
3. Use the PSW address at the time of the error to
Code Explanation
obtain the name of the load module.
62 z/OS V1R10.0 MVS System Codes
068
4. If the module is installation-provided, correct it and Code System Action
run the job step again.
100 The subtask will recover and recopy the entire
5. If the module is an IBM module, or if the problem checkpoint data set next time the data set is
persists, search problem reporting data bases for a posted. Application programs looking at the
fix. If no fix exists, contact the IBM Support Center. checkpoint data can detect this abend by
Source: Program Call/authorization (PC/AUTH) looking at the bad copy indicator.
104 The subtask will recover and resume normal
068 processing.
Explanation: A JES2 subtask has abnormally 108 The subtask will recover and resume normal
terminated. Register 15 contains a hexadecimal reason processing.
code which identifies the abending subtask. 200 The subtask will attempt to recover and
Code Abending Subtask Name resume its search for work. One or more
requests might be lost. This might result in the
100 HASPCKVR - JES2 DEBUG option detected temporary loss of the corresponding processor
an error building the APPLCOPY. because it will not be posted.
104 HASPCKVR - Data integrity error detected. 300 JES2 main task will ABEND and recovery will
108 HASPCKVR - JES2 DEBUG option detected rebuild the network path manager control
an error building a Checkpoint Version. blocks or disable the network path manager if
appropriate.
200 HASPSUBS - Subtask work dequeue error has
occurred. 304 JES2 main task will ABEND and recovery will
rebuild the network path manager control
300 HASPSUBS - The Network Path Manager blocks or disable the network path manager if
encountered an unexpected return code from appropriate.
the $NATGET service.
400 The JES2 address space will be terminated.
304 HASPSUBS - Error detected in the Network
Path Manager full path work queue. 600 The subtask attempts to recover if retry is
allowed. If retry is not allowed, JES2
400 HASPACCT - Error detected in the $SMFBUSY percolates.
queue.
604 JES2 treats this as a logical I/O error on the
600 CFEVENT - JES2 coupling facility exit checkpoint and enters checkpoint
abnormally ended. reconfiguration.
604 HASPCKCF - A coupling facility write request 608-61C
(IXLLIST REQUEST=WRITE) timed out. JES2 treats this as a logical I/O error on the
checkpoint and enters checkpoint
608 HASPCKCF - An unexpected return code from
reconfiguration.
a coupling facility read request (IXLLIST
REQUEST=READ) was encountered. Operator response: Notify the system programmer.
60C HASPCKCF - An unexpected return code from System programmer response: Respond as
a coupling facility write request (IXLLIST indicated for the specific reason code:
REQUEST=WRITE) was encountered.
Code Response
610 HASPCKCF - An incorrect list element control
value was detected associated with an element 100 Determine the reason for the copy failure. If the
in a JES2 checkpoint structure. problem persists, disable the application copy
of the checkpoint.
614 HASPCKCF - An unexpected return code from
a coupling facility read request (IXLLIST 104 Determine the reason for the failure. Contact
REQUEST=WRITE) was encountered. the IBM support center.
618 HASPCKCF - An unexpected return code from 108 Determine the reason for the failure. Contact
a coupling facility request (IXLLIST) was the IBM support center.
encountered while processing LIST 0. 200 Determine the reason for the failure. JES2
61C HASPCKCF - An unexpected return code from should be restarted to recover any lost JES2
a coupling facility request (IXLLIST) was processors.
encountered while processing LIST 0. 300 Determine the reason for the failure. Contact
System action: Specific system actions for each the IBM support center.
reason code are as follows:
Chapter 2. System Completion Codes 63
069 • 06B
304 Determine the reason for the failure. Contact 2. If you cannot resolve this problem, search problem
the IBM support center. reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide
400 Determine the reason for the failure. JES2
the dump and the logrec data error record.
should be restarted. Contact the IBM support
center.
For reason code 04, no action is necessary.
600 Determine the reason for the failure. Contact
Source: Master scheduler
the IBM support center.
604 Respond to any reconfiguration messages.
06A
Determine the reason for the failure. Contact
the IBM support center. Explanation: The functional recovery routine (FRR) for
a service request block issued a SETRP macro with the
608-61C
SERIAL=YES option. The macro requests serial
Respond to any reconfiguration messages.
percolation to the recovery routine for the task with
Determine the reason for the failure. Contact
which the SRB is associated. To prepare for percolation,
the IBM support center.
the recovery termination manager (RTM) requested
Source: JES2 storage in the task’s local system queue area (LSQA).
The request failed.
069 System action: RTM abnormally ends the task. The
system writes an ABEND dump for the failing job step.
Explanation: An address space has ended. A reason
Note that this dump contains no time-of-error
code in the SDWACRC field of the system diagnostic
information for the original problem that caused entry
work area (SDWA) provides an explanation.
into the FRR. The system may write a logrec data set
Code Explanation error record.
00 An error occurred during the creation of a new Operator response: If the system programmer asks
address space from one of the following for an SVC dump, set the following SLIP trap:
requests: SLIP SET,COMP=06A,ACTION=SVCD,END
v ASCRE macro
v CALL IEEMB881 System programmer response: Do the following:
v LOGON command 1. Search problem reporting data bases for a fix for
v MOUNT command this problem. If no fix exists, obtain the ABEND
v START command dump for the abend.
04 A request by the caller to destroy an 2. Look in the dump for the reason why the GETMAIN
ASCRE-created address space has completed. macro failed. Check for the possibility of an LSQA
GETMAIN loop.
System action: For reason code 00, the system:
3. If the reason for the failure cannot be determined,
v Ends the new address space
and you need further information from a dump, ask
v Writes a dump
the operator to set a SLIP trap to obtain an SVC
v Writes a logrec data set error record
dump.
v Issues messages
4. Contact the IBM Support Center. Provide the dump
For reason code 04, the system: and, if available, the logrec data set error record.
v Ends the new address space Source: Recovery termination manager (RTM)
System programmer response: For reason code 00,
do the following: 06B
1. Determine why a new address space could not be
Explanation: At least one of the input parameters to
created:
the excessive spin loop notification routine is not valid.
v If a module issued the ASCRE macro, check the This is probably a system error. Register 4 contains the
return and reason codes returned from ASCRE. input spin loop reason code, and register 5 contains the
See the z/OS MVS Programming: Authorized target processor identifier.
Assembler Services Reference ALE-DYN for a
description of the return and reason codes. System action: The system abnormally ends the
caller of the excessive spin loop notification routine.
v If a module did a direct call to IEEMB881 or if the
operator entered a command to create the new System programmer response: Search problem
address space, check the return codes returned reporting data bases for a fix for the problem. If no fix
by module IEEMB881. exists, contact the IBM Support Center.
Source: Loadwait/Restart
64 z/OS V1R10.0 MVS System Codes
06C • 070
SLIP SET,COMP=06E,ACTION=SVCD,END
06C
System programmer response: Search problem
Explanation: One of the following occurred during
reporting data bases for a fix for the problem. If no fix
SLIP processing:
exists, obtain a dump for the abend. Then contact the
v While processing a program event recording (PER) IBM Support Center.
interrupt, the program being monitored issued a Move
Character Long (MVCL) instruction that would overlay Source: Recovery termination manager (RTM)
low storage.
v The environmental indicators that control SLIP 06F
processing were overlaid or not valid for some other
reason. Explanation: An active SLIP trap requests
ACTION=RECOVERY. SLIP found a match for the
System action: The system ends SLIP processing for program event recording (PER) trap that was defined in
the current event. The status of PER in the system and the command. For the RECOVERY action, SLIP gives
of the existing SLIP traps is unchanged. control to the recovery termination manager (RTM). This
completion code is used to take a dump for SLIPs
System programmer response: If the program being
which specify ″MSGID=″ and is considered normal in
monitored caused the problem, correct the program. If
that case.
the problem cannot be resolved, search problem
reporting data bases for a fix for the problem. If no fix System action: RTM abnormally ends the task being
exists, contact the IBM Support Center. monitored. SLIP processing continues.
Source: Recovery termination manager (RTM) Source: Recovery termination manager (RTM)
06D 070
Explanation: SLIP processing found that an incorrect Explanation: A program issued the SUSPEND,
parameter list was passed to SLIP. RESUME, or TCTL macro, but the program issuing the
macro either:
System action: The system ends SLIP processing for
v Is in an environment that is not valid
the current event. The status of program event
v Specified parameters that are not valid
recording (PER) in the system and of the existing SLIP
traps is unchanged. The system sends messages about A hexadecimal reason code in register 15 explains the
the problem to the job log. error:
Operator response: If the system programmer asks Code Explanation
for an SVC dump, set the following SLIP trap:
0C The program issued the RESUME macro with
SLIP SET,COMP=06D,ACTION=SVCD,END the RETURN=N parameter, but the program
System programmer response: Search problem was not in service request block (SRB) mode.
reporting data bases for a fix for the problem. If no fix 10 The program issued the RESUME macro, but
exists, try to obtain the ABEND dump for the abend. If the specified task control block (TCB) was not
no dump exists, ask the operator to set a SLIP trap to valid.
obtain an SVC dump. Contact the IBM Support Center.
Provide the dump. 14 The program issued the RESUME macro, but
could not address the specified address space
Source: Recovery termination manager (RTM) control block (ASCB).
18 The program issued the RESUME macro with
06E the RETURN=N parameter, but the program
Explanation: One of the following occurred while SLIP was not in primary address space control
was activating or deactivating a program event mode.
recording (PER) trap: 1C The program issued the RESUME macro with
v For a global PER trap, SLIP requested cell pool the RETURN=N parameter while holding one
storage. The request returned a nonzero return code, or more locks or while running with a PCLINK
indicating an error. stack that was not empty.
v SLIP requested that cell pool storage be freed. The 20 The program issued the TCTL macro, but was
request returned a return code other than 0 or 20, not in SRB mode.
indicating an error.
24 The program issued the TCTL macro, but was
System action: SLIP processing ends. not in primary address space control mode.
Operator response: If the system programmer asks
for an SVC dump, set the following SLIP trap:
Chapter 2. System Completion Codes 65
071
28 The program issued the TCTL macro while Provide the SVC dump, including registers 14 and
holding one or more locks. 15, and, if available, the logrec data set error
record.
2C The program issued the RESUME macro with
the MODE=UNCOND parameter and the Source: Supervisor control
ASYNC=N parameter, but the program held the
local lock of an address space other than the
071
target address space.
Explanation: An error occurred when the operator
30 The program issued the SUSPEND macro, but
initiated a restart.
the request block (RB) suspend count was not
0. Register 15 contains a hexadecimal reason code that
explains the error:
34 The program issued the SUSPEND macro with
the RB=PREVIOUS parameter, but no previous Code Explanation
RB existed.
| 00 The operator replied ″ABEND″ to message
38 Processing for a RESUME macro detected a | BLW004A.
request to resume an RB that had a suspend
count other than 0 or 1. | 04 The operator replied ″REPAIR″ to message
| BLW004A.
3C A RESUME macro with unconditional
synchronous options required the local lock. 08 A programming error caused the program that
The issuer was disabled and did not hold the was currently running to branch directly to the
necessary local lock. restart interruption handler.
40 Processing for a RESUME macro detected a 0C The operator selected RESTART option 0 on a
request from reset processing to resume an processor that is in a valid spin waiting for a
RB. The RB does not exist on the RB chain for global resource held by a second processor
the specified TCB. that is in an erroneous disabled loop. A DSGNL
RESTART command, directed to the second
44 The program issued the TCTL macro, but the processor, failed.
specified task control block (TCB) was not
valid. 10 The system started writing logrec data set error
records after detecting an excessive spin loop
System action: The system abnormally ends the condition. The interrupted unit of work
program that issued the macro. The system may write a continues to run.
logrec data set error record.
20 The system abnormally ended the program that
Operator response: If the system programmer asks was causing a system excessive spin loop.
for an SVC dump, set the following SLIP trap: Recovery routines are not allowed to retry
SLIP SET,COMP=070,ACTION=SVCD,END because the recovery action for the spin loop
was TERM.
System programmer response: Do the following:
30 The system abnormally ended the program that
1. If a dump or a logrec data set error record was not
was causing a system excessive spin-loop
written with the abend, ask the operator to set a
condition. Recovery routines are allowed to
SLIP trap to obtain an SVC dump.
retry because the recovery action for the spin
2. The registers at the time of error contain the loop was ABEND.
following information:
System action: The system does one of the following:
v Register 14 contains the address of the module
that issued the macro. v For reason code X'00', X'08', X'0C', X'20', or X'30',
the system abnormally ends the program currently
v Register 15 contains the reason code and
running.
indicates whether the error is a SUSPEND,
RESUME, or TCTL error. v For reason code X'04', the system detects and
repairs, where possible, errors in critical system
3. Use the address in register 14 to identify the module
areas. The system refreshes selected system control
that issued the macro.
blocks and validates and repairs selected system
v For an installation-provided module, fix the error resources. The system logs the old values of some
described by the reason code and rerun the job. refreshed control block fields in the variable recording
v For an IBM module, search problem reporting area (VRA) of the system diagnostic work area
data bases for a fix for the problem. If no fix (SDWA). The system writes these old values in the
exists, contact the component group associated logrec data set error record. Then the system returns
with this module at the IBM Support Center. control to the interrupted program.
66 z/OS V1R10.0 MVS System Codes
072 • 073
v For reason code X'10', the system records the 1. Get the program status word (PSW) at the time
excessive spin loop in a logrec data set error record. of error as follows:
Operator response: If requested by the system v For reason code X'10', X'20', or X'30', obtain
programmer, set a SLIP trap to obtain a dump. the PSW from the logrec data set error
record.
System programmer response: Depending on the
v For reason code X'0C', X'20', or X'30', ask
reason code, do the following:
the operator to obtain an SVC dump. Format
Reason Code X'00' the dump to see the PSW at the time of
| Message BLW004A should have identified the work error.
| that was in progress at the time of the interruption. 2. Use the address in the PSW to obtain the name
1. If a logrec data set error record is not produced of the spinning module.
with the abend, ask the operator to obtain an v If the module is not an IBM module, continue
SVC dump. diagnosis with the module.
2. Examine the program status word (PSW) at the v If the module is an IBM module, search
time of error in the logrec data set error record. problem reporting data bases for a fix for the
The PSW points to the location where problem. If no fix exists, contact the IBM
RESTART was entered by the operator. If the Support Center. Provide the dump and the
program was in a loop, the PSW address will logrec data set error record.
be within the loop.
3. Examine the system trace table for evidence of See z/OS Problem Management for information
a loop or a wait. If a loop or a wait is about diagnosing a loop.
suspected, use the address in the PSW to
Source: Loadwait/Restart
obtain the name of the looping module.
v If the module is not an IBM module, continue
diagnosis with the module. 072
v If the module is an IBM module, search Explanation: The system abnormally ended a
problem reporting data bases for a fix for the program that had a processor affinity requirement
problem. If no fix exists, contact the IBM because no processors on which it can run are online. A
Support Center. Provide the dump and the hexadecimal reason code in register 15 indicates the
logrec data set error record. type of program:
Reason code X'08' Code Explanation
Determine which program branched incorrectly, as
follows: 0004 A task running under a task control block
(TCB).
1. If a logrec data set error record is not produced
with the abend, ask the operator to obtain an 0008 A routine running under a service request block
SVC dump. (SRB).
2. Look at register 14 at the time of the error. If System action: The system abnormally ends the
the illegal branch was made by a BALR 14,15 program that had a processor affinity requirement.
instruction, register 14 points to the instruction
following the instruction that took the bad Application Programmer Response: Resubmit the
branch. If this instruction is a branch instruction, job when the processor affinity requirements can be
then this instruction probably branched directly met.
into the restart interrupt handler. Source: Supervisor control
3. Use the address in register 14 to get the name
of the module that issued the bad branch
073
instruction.
v If the module is not an IBM module, continue Explanation: Supervisor control detected an error
diagnosis with the module. while processing a SETLOCK OBTAIN or SETLOCK
RELEASE macro. The hexadecimal reason code in
v If the module is an IBM module, search
register 15 explains the error:
problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Code Explanation
Support Center. Provide the dump and the
logrec data set error record. 00 While spinning for a disabled spin lock, the
system found that the lockword contains a
Reason code X'0C', X'10', X'20', or X'30' processor identifier that is not valid. Register
Determine why an excessive spin condition 10 contains the lockword value that is not valid.
occurred, as follows:
04 The system detected serialization that is not
Chapter 2. System Completion Codes 67
073
valid. The caller was disabled but requested 324 The caller tried to obtain a SHR/EXCL lock
the LOCAL, cross memory local (CML), or unconditionally SHR, but the lock was held
cross memory services (CMS) lock EXCL by the caller.
unconditionally. The lock was not immediately
424 The caller tried to obtain a SHR/EXCL lock
available.
conditionally SHR, but the lock was held EXCL
08 The system detected a hierarchy violation. by the caller.
v If a SETLOCK OBTAIN macro was being 524 The caller tried to release a SHR/EXCL lock
processed, one of the following occurred: SHR, but the lock was held EXCL by the caller.
– The requested lock was lower in the
28 A caller unconditionally requested a class lock
locking hierarchy than the locks currently
that was held by the processor as a class lock
held.
at a different level of the lock hierarchy.
– Another lock of the same type was
already held. 2C The caller specified release of locks according
to a bit string mask in register 11. However, the
– A CMS lock was requested, but a local
caller does not hold all the locks that the mask
lock was not held.
specifies.
– A local or CML lock was requested
unconditionally, but the PSASUPER field 30 The system was invoked recursively for an
was nonzero. unconditional lock obtain.
v If a SETLOCK RELEASE macro was being 34 The caller issued a SETLOCK RELEASE
processed, one of the following occurred: macro to release a lock from PSACLHS, but
– A local lock was specified while a CMS the caller is not holding the lock.
lock was still held. 38 The caller issued a SETLOCK RELEASE
– All CMS locks were specified, but not all macro to release a lock from PSACLHSE, but
CMS locks were held. the caller is not holding the lock.
0C The caller requested a CML lock. The caller 3C The caller issued a SETLOCK RELEASE
passed an address space control block (ASCB) macro to release a spin lock, but the caller is
address that was not valid. Register 11 not holding the lock. Lock manager was
contains the ASCB address. invoked for a lock obtain, and the caller was
enabled but specified DISABLED.
10 The caller requested another address space’s
CML lock but did not establish an active bind 40 While spinning for a disabled spin lock, the
to that address space. Register 11 contains the system found that global recovery was active.
ASCB address.
140 The caller tried to obtain a SHR/EXCL lock
14 The caller specified an ASCB for an address conditionally EXCL, the lock was not held SHR,
space that was being ended. Register 11 and an unexpected error occurred.
contains the ASCB address.
240 The caller tried to obtain a SHR/EXCL lock
18 The caller requested the CML lock of an conditionally EXCL, the lock was held SHR,
address space that was not dispatchable. and an unexpected error occurred.
Register 11 contains the ASCB address.
340 The caller tried to obtain a SHR/EXCL lock
1C The caller requested the CML lock of the unconditionally EXCL and an unexpected error
master address space or the WAIT address occurred.
space.
System action: The system abends the program that
20 The caller requested a lock type that is no issued the SETLOCK macro. The system may write a
longer supported. logrec data set error record.
24 The caller tried to obtain a SHR/EXCL lock Operator response: If the system programmer asks
unconditionally EXCL, but the lock was held for an SVC dump, set the following SLIP trap:
SHR by the caller. SLIP SET,COMP=073,ACTION=SVCD,END
124 The caller tried to obtain a SHR/EXCL lock System programmer response: Do the following:
conditionally EXCL, but the lock was held SHR
by the caller. 1. If a dump or a logrec data set error record was not
written with the abend, ask the operator to set a
224 The caller tried to release a SHR/EXCL lock SLIP trap to obtain an SVC dump.
EXCL, but the lock was held SHR by the caller. 2. Identify the module that issued the SETLOCK macro
by using the address in register 14 at the time of
error.
68 z/OS V1R10.0 MVS System Codes
074 • 075
v For an installation-provided module, continue 2. If a dump is not produced with the abend, ask the
diagnosis with the module. operator to set a SLIP trap to obtain an SVC dump.
v For an IBM module, identify lock information as In the system trace, find the SVC D entry for abend
follows: X'074'. In the entry, note the address space identifier
(ASID) in the ASID column. Back up to look for a
– Register 9 contains the current lock held string
PGM entry with the same ASID. This indicates that
extension (PSACLHSE).
a program check occurred.
– Register 12 contains the PSASUPER bits at
3. Search problem reporting data bases for a fix for the
the time of abend.
problem. If no fix exists, contact the component
– Register 13 contains the current locks held group associated with the module that took the
string (PSACLHS) that was current when the program check at the IBM Support Center. Provide
lock request was made. all problem data collected and the logrec data set
error record.
See the PSA section of z/OS MVS Data Areas,
Vol 3 (IVT-RCWK) for the meaning of the bits in Source: Supervisor control
the PSASUPER, PSACLHS, and PSACLHSE
fields. 075
3. Search problem reporting data bases for a fix for the
Explanation: A program running in supervisor state,
problem. Include in the search argument:
key 0 issued a SCHEDULE macro to schedule a service
v PSASUPER bits at the time of abend:
request block (SRB). The system checked the acronym
GPR12/hhhhhhhh
in the address space control block (ASCB) pointed to by
v PSACLHS bits at the time of abend:
SRBASCB. The acronym failed the check. Possible
GPR13/hhhhhhhh
reasons are:
If no fix exists, contact component group associated v The issuer of the SCHEDULE macro put an incorrect
with the module that issued the SETLOCK macro at address into SRBASCB. Consequently, SRBASCB
the IBM Support Center. Provide, if available, the did not point to a valid ASCB.
SVC dump and the logrec data set error record. v SRBASCB pointed to a valid ASCB, but the ASCB
has gone away normally or abnormally.
Source: Supervisor control
v SRBASCB pointed to a valid ASCB, but the ASCB
was overlaid.
074
Explanation: A program issued the SETLOCK macro. Register 14 contains the value from SRBASCB.
Supervisor control could not finish processing the macro Register 15 at the time of error points to the SRB that
for one of these reasons: was being scheduled.
v The lockword address specified on the SETLOCK System action: The system ends processing of the
macro is not on a fullword boundary. SCHEDULE macro. The system may write an SVC
v A page fault occurs when the lockword address dump, a logrec data set error record, or both.
specified on the SETLOCK macro is used. Operator response: If the system programmer asks
v A machine check occurs in the lockword specified on for an SVC dump, set the following SLIP trap:
the SETLOCK macro. SLIP SET,ENABLE,COMP=075,ACTION=SVCD,END
System action: The system writes a logrec data set System programmer response: Do the following:
error record and may write messages about the error.
1. If an SVC dump is not produced with the abend, ask
Operator response: Check messages and the logrec the operator to set a SLIP trap to obtain an SVC
data set error record to determine if a machine check dump.
occurred just before the abend. If so, the problem is a 2. Examine SRBASCB to see if it contains a valid
hardware problem. Contact hardware support. If not, address. Check for an incorrect address in the
notify the system programmer. If the system SRBASCB field. The address in SRBASCB is not
programmer asks for an SVC dump, set the following valid if:
SLIP trap: v It is all zeros
SLIP SET,COMP=074,ACTION=SVCD,END v It does not end in X'00' or X'80'
v It is not an address in the system queue area
System programmer response: Do the following: (SQA)
1. Examine messages and the logrec data set error
record for previous abend codes. Look at the If the address in SRBASCB does not look like a
explanations of any previous abend codes. A valid address, contact the IBM Support Center.
previous problem could have caused this problem. Provide all problem data collected.
Chapter 2. System Completion Codes 69
076 • 077
3. If SRBASCB looks like a valid ASCB address, check 0010 An unexpected error occurred in a command
the address space vector table (ASVT) for this processing module.
address. The ASVT contains a list of ASCB
System action: The system:
addresses. The CVTASVT field of the
communications vector table (CVT) points to the v Ends the START, MOUNT, or LOGON command
ASVT. ASVTENTY begins the ASCB addresses. v Deletes the partially created address space
Scan for the address that is in SRBASCB. v Issues message IEA890I to identify which command
4. If the address in SRBASCB is in the ASVT, then the was ended as a result of the failure
ASCB pointed to by SRBASCB has been overlaid.
See if you recognize the overlay by looking for any System programmer response: If the problem
EBCDIC eye-catchers around the overlay. Search recurs, search problem reporting data bases for a fix for
problem reporting data bases for a fix for the the problem. If no fix exists, contact the component
problem. Include in the search argument: group for command processing at the IBM Support
v EBCDIC eye-catcher that is a module name: Center.
PIDS/cccccccc Source: Supervisor control
v Abend X'075': AB/S075
v Overlay of the ASCB: OVS/ASCB
077
The size and content of the overlay can also be Explanation: While the system was processing a
added to the search argument. console service request, an error occurred.
If no fix exists, contact the supervisor control Register 15 contains a hexadecimal error code in the
component group at the IBM Support Center. format xxxxyyyy. The fields in this error code are the
Provide data collected in previous steps and, if following:
available, the logrec data set error record. xxxx This halfword is for IBM internal use only.
5. If the address in SRBASCB cannot be found in the
yyyy This halfword is the unique reason code
ASVT, then either:
identifier. Only yyyy is listed below.
v The ASCB was deleted when the address space
went away abnormally. The following are the yyyy values and their meanings:
v The ASCB went away normally.
Code Explanation
v The ASCB is not valid. The issuer of the
SCHEDULE macro put a bad address into 0000 In a request to start or stop MONITOR
SRBASCB. JOBNAMES, STATUS, or SESSIONS
processing, the caller passed an incorrect
Contact the supervisor control component group at console name or address space identifier
the IBM Support Center. Provide data collected in (ASID).
previous steps and, if available, the logrec data set
error record. 0004 The parameter list passed to the
communications task was not valid.
Source: Supervisor control
0008 The system found that a caller asked to delete
a nonexistent buffer.
076
000C The system could not establish a recovery
Explanation: An error occurred while attempting to environment.
create or initialize an address space. One of the
following hexadecimal reason codes explain the error: 0010 The parameter list passed was not valid.
Code Explanation 0014 A caller was not running in the Console
address space.
0004 Command processing received a nonzero
return code from the virtual storage 0018 The system could not obtain a needed area.
management (VSM). Register 5 contains the 001C The system could not process a console
return code. request because of conflicting requests in the
0008 Command processing requested virtual storage parameter list.
for a service request block (SRB). The request 0020 The system could not process a console
returned a nonzero return code. Register 5 request because of incomplete or incorrect
contains the return code. data in the parameter list.
000C Command processing received a nonzero 0024 The system could not process a console
return code from another command processing request because the specified console was not
module. Register 5 contains the return code. dedicated to the requesting component.
70 z/OS V1R10.0 MVS System Codes
077
0028 The system encountered an error in the request made by the caller. The caller
| CommTask processing. invoked a service in AR mode with a non-zero
ALET associated with the input parameter list.
002C The SMCS Logical Error exit determined that
The service however requires that input
there was a logical error associated with a
parameter list is addressable from the primary
SMCS console session.
address space.
002D SMCS could not initialize or a session with an
0400–3FFF
LU could not be established. Message IEE052I
These codes are for IBM internal use only with
or IEE053I has been issued with more specific
the following exceptions: 0F00, 0A08.
information.
0A08 A subsystem console request was made to
002E An unexpected condition has occurred in
module IEAVG700 with a Subsystem Console
SMCS attempting to establish a session with
Service Routine Parameter List (SCSR
an LU. Message IEE053I or IEE057I may be
mapped in macro IEZVG100) with a version
issued with more specific information.
value in field SCSVER that is no longer
002F A storage overlay within DIDOCS has been supported.
detected.
| 0F00 An unexpected return code was received from
0030 A storage overlay within SMCS has been | the IXCMSGO service while sending
detected. SMCS will continue; however, | information to other systems in the sysplex.
performance may be degraded.
System action: If the error occurred during MONITOR
| 0034 The tracking facility issued an abend. To help or STOPMN command processing, the MONITOR
| identify the occurrence of what is being function is not changed. Otherwise, the system
| tracked, the following registers are set: abnormally ends the calling routine.
The following reason code also has a unique System
Note: The information stored in these registers Action:
is the same information recorded and
displayed in message CNZ1001I when Reason Code
the instance is made. System Action
| R2 The value found in
003C The IEEVARYD service returns return code
| TRPL_TRACK_VALUE that was
X'10'.
| tracked
R3 Address of the CNZTRKR parameter | 003D The service called is unable to process the
list (mapped by CNZTRPL) that the | request.
tracking facility was processing
Operator response: If the error occurred during
R4 Address of the jobname under which
MONITOR command processing, reenter the MONITOR
the caller of the tracking facility was
or STOPMN command.
running
R5 Address of the program name which For other errors, contact the system programmer.
called the service that invoked the
tracking facility The following reason code also has a unique Operator
| R6 Address of the location where what is Response:
| being tracked occurred. Reason Code
| R7 Offset within the program where what Operator Response
| is being tracked occurred
| R8 ASID of the occurrence of what is 0018 Look for a message backlog. Ease the backlog
| being tracked by allowing the messages to roll off the screen
or purging the messages with a CONTROL Q
0038 UCME look-up error. Either the requested command.
UCME could not be located, or the console ID
supplied for the look-up was invalid. Application Programmer Response: The following
reason code has a unique Application Programmer
| 0039 The version of the CNZZVMXT message exit Response:
| and the version of the shared common SQA
| data area (SQAAREA) are different. Reason Code
| CNZZVMXT cannot use the shared common Application Programmer Response
| data area because the mapping of the data 0A08 Update the application to use a Subsystem
| area may have changed. Console Service Routine Parameter List that is
003C IEEVARYD found a parameter or option that is supported and set SCSVER to the current
not valid. version (constant SCSVERSN as defined in
IEZVG100).
003D The CnzConv service was unable to process
Chapter 2. System Completion Codes 71
078 • 079
System programmer response: Search problem | serialization required to bring the device online
reporting data bases for a fix for the problem. If no fix | (that is, SYSIEFSD.VARYDEV and
exists, contact the IBM Support Center. | SYSIEFSD.Q4).
The following reason codes also have a unique System | 003D Correct the program that called the CNZCONV
Programmer Response: | service, so that the request can be successfully
| completed.
Reason Code
System Programmer Response Source: Console services
0034 No dump is taken for this ABEND, and the
| occurrence of what is being tracked continues 078
normally. If a dump is needed, a SLIP trap can
Explanation: There was an error in one of the
be set for this ABEND. An example SLIP trap
following routines invoked by the region control task
follows.
(RCT):
SLIP SET,ENABLE,ID=TRAK,COMP=077,
REASON=34,ACTION=SVCD,END v ATTACH of the dump task
v ATTACH of started task control (STC) during RCT
| After determining what is being tracked, notify initialization
the vendor that a change to their product is v PURGE I/O during QUIESCE processing
required. If the application or program is an v The real storage manager (RSM) swap out routine
IBM product, contact the IBM Support Center during QUIESCE processing
to determine if this is a known instance. If it is
| not known, inform IBM of the occurrence being RCT received an unacceptable return code from the
| tracked. IBM will correct this interface in a routine and cannot continue processing. This abend
future release. may indicate a storage shortage.
| 0039 This error is usually caused by installing a System action: The system gives RCT recovery
| newer level of the CNZZVMXT message exit control. The system:
| without freeing the SQA data area first using v Requests that the address space end
| the SETMF FREE command. To recover the
v Issues an SVC dump for the address space if the
| problem, follow these steps:
error was unrecoverable or recursive
| 1. Restore the previous version of the
v Writes a logrec data set error record
| CNZZVMXT message exit to the system
| library (doing an LLA refresh if necessary). v Performs resource clean-up
| The K M command runs in the CONSOLE System programmer response: Look for errors in the
| address space. If you restore the previous logrec data set error record or the SVC dump indicating
| version of CNZZVMXT by changing the a prior failure in the same address space. Search
| libraries referred to in the LINKLIST problem reporting data bases for a fix for the problem. If
| concatenation, you must issue a no fix exists, contact the IBM Support Center. Provide
| SETPROG the logrec data set error record and the SVC dump.
| LNKLST,UPDATE,JOB=CONSOLE
Source: Region control task (RCT)
| command to cause the CONSOLE address
| space to use the new LINKLIST
| concatenation. However, there is some risk 079
| associated with the SETPROG command
| (ABEND106 errors might result), and Explanation: An error occurred while the region
| therefore use this command only when control task (RCT) attention request was trying to obtain
| necessary to prevent an IPL. or release the local lock.
| 2. Activate the message exit using a K System action: The system gives RCT recovery
| M,UEXIT=Y command. control. The system:
| 3. Follow the correct migration steps for v Issues a Time Sharing Option (TSO) error message
| message flood automation. See z/OS MVS to the terminal indicating that the attention request
| Planning: Operations for details. was ignored or requests an SVC dump of the
address space
| 003C Correct the program invoking the IEEVARYD
| service. If the VDEV_ENQS_HELD flag (found v Performs resource clean-up
| in mapping IEEZB833) is being used, the code v Writes a logrec data set error record
| must be updated to remove this option (it is no v May request an SVC dump
| longer supported), and to release the ENQ
System programmer response: If a TSO error
message is issued to the terminal, you can either
72 z/OS V1R10.0 MVS System Codes
07A • 07C
regenerate the attention request or continue processing. 14 For a DSGNL macro, the caller passed an
incorrect order code for the SIGP instruction.
Search problem reporting data bases for a fix for the
This order code is not supported.
problem. If no fix exists, report the problem to the IBM
Support Center. Provide the logrec data set error record 18 You were on a 2066 machine type with an
and the SVC dump if available. LPAR name of ZOSExxxx. You must change
the LPAR name to something other than
Source: Region control task (RCT)
ZOSExxxx.
System action: One of the following:
07A
v For reason code X'00', X'04', X'08', X'0C', or X'14',
Explanation: An unrecoverable error occurred during the system abnormally ends the caller.
region control task (RCT) processing such as:
v For reason code X'10', the system writes a logrec
v A system interruption request block (SIRB) failure
data set error record.
v A swap-out processing error
Operator response: If the system programmer asks
System action: The system gives RCT recovery
for an SVC dump, set the following SLIP trap:
control. To avoid an address space interlock, RCT
abends the address space without cleaning up address SLIP SET,COMP=07B,ACTION=SVCD,END
space-related resources. The system may or may not System programmer response: Do the following:
write a logrec data set error record.
1. If a logrec data set error record is not produced with
System programmer response: Search problem the abend, ask the operator to set a SLIP trap to
reporting data bases for a fix for the problem. If no fix obtain an SVC dump.
exists, report the problem to the IBM Support Center. 2. Use the address in register 14 at the time of error to
Provide the logrec data set error records if any were identify the module that issued the macro or caused
written. the emergency signal interruption.
Source: Region control task (RCT) v For an installation-provided module, continue
diagnosis with the module.
07B v For an IBM module, search problem reporting
data bases for a fix for the problem. If no fix
Explanation: The system detected an error in exists, contact the component group associated
interprocessor communications (IPC). A hexadecimal with this module at the IBM Support Center.
reason code in register 15 explains the error: Provide, if available, the SVC dump and the
Code Explanation logrec data set error record.
00 For a RISGNL macro, the caller passed an Source: Supervisor control
incorrect physical configuration
communications area (PCCA) address. 07C
Registers 2 and 3 contain the values of
registers 0 and 1 that were input from the Explanation: The system has detected a recursive
caller. ABEND macro (SVC 13). Field ASCBARC of the
address space control block (ASCB) contains a
04 For a RPSGNL macro, the caller passed an hexadecimal reason code, as follows:
incorrect PCCA address. Registers 2 and 3
contain the values of registers 0 and 1 that Code Explanation
were input from the caller. 00 The system abnormally ended the task or the
08 For a DSGNL macro, the caller passed an address space.
incorrect PCCA address. Registers 2 and 3 04 The SVC first level interrupt handler (FLIH)
contain the values of registers 0 and 1 that recovery abnormally ended the address space.
were input from the caller.
System action: The system ends either the current
0C For a RISGNL macro, the caller’s serial task or the current address space. The system may
receiving routine abnormally ended on the write an SVC dump, a logrec data set error record, or
processor processing the emergency signal both.
interrupt. Registers 2 and 3 contain the values
of registers 0 and 1 that were input from the Operator response: If the system programmer asks
caller. for an SVC dump, set the following SLIP trap:
SLIP SET,COMP=07C,ACTION=SVCD,END
10 The emergency signal second level interrupt
handler (SLIH) detected second level System programmer response: Do the following:
recursion.
Chapter 2. System Completion Codes 73
07D
1. If an SVC dump was not produced with the abend, v An FRR with EUT=YES exists
ask the operator to set a SLIP trap to obtain an SVC
System action: The system abnormally ends the unit
dump.
of work that issued the SETFRR macro. The system
2. In the dump, find the reason code in the ASCBARC may write a logrec data set error record. The unit of
field. work may request a dump.
3. Search problem reporting data bases for a fix for the
Operator response: If the system programmer asks
problem. If no fix exists, continue with step 4.
for an SVC dump, set the following SLIP trap:
4. Analyze the dump to find the original abend causing
SLIP SET,COMP=07D,ACTION=SVCD,END
the recursive loop, as follows. In the system trace,
SLIP SET,COMP= 0DC,RE=8,ACTION=SVCD,END
find the SVC D entry for abend X'07C'. Note the
address space identifier (ASID) in the ASID column System programmer response: Do the following:
of this entry. 1. Check for the problem in all installation-provided
Back up to the next SVC D entry with this ASID. programs that are in protection key 0 and that issue
Note the abend code in the UNIQUE-3 column. This SETFRR. At the time of the abend, register 14
is the original abend code. points to the program that invoked SETFRR. This
5. Develop a second search argument, using the program is likely to have caused the problem.
abend code found in step 4. If no fix exists, contact 2. Format the dump for the abend to see the prefixed
the IBM Support Center. Provide all problem data save area (PSA) for the system on which the abend
collected in the previous steps and, if available, the occurred. The first 3 words in the PSASTAK field
logrec data set error record. should contain the following:
Source: Supervisor control | 00000BB8 00000DB8 00000020
3. If the PSASTAK field is incorrect, an overlay
occurred. Use the following SLIP storage alteration
07D
trap to determine which routine caused the overlay:
Explanation: The system found an error while adding | SLIP SET,SA,RANGE=(B80,B8B),A=WAIT,END
or deleting a functional recovery routine (FRR) from one
4. For S07D-0, a dump cannot be taken. Trace entries
of the FRR recovery stacks.
similar to the following will be found in the S0DC-8
The reason codes are as follows: dump which follows an S07D-0:
Code Explanation 01 014E *SVCE D 040C2000 800003FA 00FF050C
816A2E88 8007D000
00 The FRR recovery stack could not hold any 01 014E *SVCE D 040C2000 800003FA 00FF050C
more FRRs because all of the available slots 01371EC4 8007D000
were filled. This abend is probably caused by 01 014E *SVCE D 040C2000 800003FA 00FF050C
an installation-provided program that issued 816C50F8 8007D000
01 014E *SVCE D 040C2000 800003FA 00FF050C
SETFRR incorrectly as follows:
01371EC4 8007D000
v Adding FRRs without deleting them. 01 014E *SVCE D 040C2000 800003FA 00FF050C
v In a loop that includes a SETFRR macro. 816C50F8 8007D000
01 014E *SVCE D 040C2000 800003FA 00FF050C
v Adding too many FRRs. The system only 01371EC4 8007D000
guarantees that installations can add two 01 014E *RCVY ABRT
FRRs. 3C000304
01 014E *RCVY MEM 813305A8 840DC000
As system services also need to add FRRs, 00000008 00000000
dump processing and LOGREC recording
cannot be performed. S07D is normally The SVCE D entries with R1=8007D000 indicate
followed by an S0DC-8 abend which will that S07D-0 has occurred. Although the FRR stack
contain recursive S07D SVCE entries in the current pointer will be reset in the S0DC-8 dump,
system trace. there will be residual data in the FRR stack which
can be used to determine the FRR entries that filled
04 The caller of SETFRR DELETE was not in a the stack.
legal state to be holding FRRs at the time that
SETFRR DELETE was issued. 5. Search problem reporting data bases for a fix for the
problem. If you suspect an overlay, include in the
From the time an FRR is established until the search argument:
time it is deleted, at least one of the following v Program identifier: PIDS/5752SCRTM
things must be true: v System abend code: AB/S007D
v Some lock is held v The name of the field that is overlaid:
v The unit of work is running disabled FLDS/PSASTAK
v The unit of work is an SRB
74 z/OS V1R10.0 MVS System Codes
07E • 083
Note: Prior to OS/390 the program identifier to problem. If no fix exists, contact the IBM Support
search for is PIDS/5752SC1CM. If no fix Center. Provide the logrec data set record and dump.
exists, contact the IBM Support Center.
Source: Task management
Provide problem data collected in the
previous steps.
080
Source: Recovery termination manager (RTM)
Explanation: An unexpected error occurred during
system processing except for the following reason
07E
code:.
Explanation: A CONFIG or VARY command
Code Explanation
requested addition or removal of hardware units from a
configuration. To process the command, the system 6B000121
checked the availability of device paths. While checking Indicates that a task which owned high virtual
the device paths, the system encountered an error. A fixed storage terminated without first unfixing
hexadecimal reason code in register 15 explains the the pages.
error:
System action: The system issues an abend to the
Code Explanation current address space or to the current unit of work.
The system writes a logrec data set error record. This
04 The unit control block (UCB) address, passed
abend may be accompanied by messages.
to the device path checking routine, did not
point to the common segment of the UCB. For reason code 6B000121, the address space owning
the fixed page is terminated.
0C An incorrect function code was passed to the
device path checking routine. System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
14 The system received a return code from a
exists, contact the IBM Support Center. Provide the
device path checking routine indicating that an
logrec data set record and the SYSOUT output for the
unrecoverable program or hardware error
job.
occurred.
For reason code of 6B000121, correct the application so
System action: The system ends the CONFIG or
that it unfixes the high virtual pages that it owns prior to
VARY command.
task termination.
Operator response: Depending on the reason code,
Source: Real storage manager (RSM)
do the following:
v For reason code X'04' or X'0C', contact the system
programmer. 081
v For reason code X'14', if you entered the VARY or Explanation: A GETMAIN macro requested virtual
CONFIG command to bring a device online, try to storage for the system queue area (SQA) or the local
vary the individual paths to the device. If this is SQA (LSQA). The request passed an incorrect virtual
unsuccessful, contact hardware support. address. This is a problem in the system.
System programmer response: Search problem System action: The system denies the request for a
reporting bases for a fix for the problem. If no fix exists, central storage frame. The system writes messages and
contact the IBM Support Center. a dump.
Source: Reconfiguration System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
07F
messages and the dump.
Explanation: During recovery, the system found that
Source: Real storage manager (RSM)
the task control block (TCB) queue associated with the
abnormally ended address space was empty.
083
System action: The system abnormally ends the
address space or job. The system writes messages, a Explanation: Auxiliary storage manager (ASM) was
logrec data set error record, and a dump. unable to convert a logical slot identifier (LSID) to a full
seek address. The relative byte address (RBA) is
Application Programmer Response: Run the job
outside the range of the extension data block (EDB)
again. If the error recurs, notify the system programmer.
entries.
System programmer response: Collect all printed
System action: The ASM I/O request area (AIA) being
output and output data sets related to the problem.
processed is marked in error. The system writes a
Search problem reporting data bases for a fix for the
Chapter 2. System Completion Codes 75
084 • 087
logrec data set error record containing a copy of the AIA will put the record on the WAIT queue
and EDB. Processing continues. and wait for an ECB to be posted.
System programmer response: Search problem 0028005C VSAM GET had insufficient storage to
reporting data bases for a fix for the problem. If no fix process the request.
exists, contact the IBM Support Center.
00xx0060 VSAM GET received a return code
Source: Auxiliary storage manager (ASM) from VSAM other than 0 or those
listed here.
084 00400064 VSAM GET was processing the
maximum number of requests already.
Explanation: For an I/O operation, the auxiliary
storage manager (ASM) detected an error. 00xx0070 VSAM GENCB macro did not build a
request parameter list on a PUT
System action: The system writes a logrec data set
request.
error record and attempts to continue processing.
000C0074 VSAM PUT had a physical I/O error.
System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix 00140078 VSAM PUT found the record was held
exists, contact the IBM Support Center. exclusively by another requestor. ASM
will put the record on its WAIT queue
Source: Auxiliary storage manager (ASM)
and wait for an ECB to be posted.
0028007C VSAM PUT had insufficient storage to
085
process the request.
Explanation: The auxiliary storage manager (ASM)
00xx0080 VSAM PUT received a return code
detected an internal error.
from VSAM other than 0 or those
System action: The system writes a logrec data set listed here.
error record. Processing continues.
00400084 VSAM PUT was processing the
System programmer response: Search problem maximum number or request already.
reporting data bases for a fix for the problem. If no fix
Notes:
exists, contact the IBM Support Center.
1. The high-order byte might not be X'00', but it
Source: Auxiliary storage manager (ASM) contains the VSAM component code (the
component being processed when the error
086 occurred).
2. xx=Return Code or feedback code from VSAM.
Explanation: The auxiliary storage manager (ASM) These codes are documented in the VSAM Macro
received an error from VSAM during an I/O operation. Instruction Reference manual .
Register 15 contains the VSAM return code or feedback System action: The system writes a logrec data set
code in the first half-word and an ASM return code in error record. Processing continues.
the other half-word. The ASM return code identifies the
operation that was being attempted when the VSAM System programmer response: Contact hardware
error occurred. support.
Code Explanation Source: Auxiliary storage manager (ASM)
00000008 VSAM did not find the requested
record. 087
00000014 VIO journaling data set is full. Explanation: The system detected an error while
attempting to free virtual storage.
0000001C Could not obtain storage for buffer.
System action: The system writes a logrec data set
00000030 Partially retrieved ASPCT for release error record. Processing continues.
request.
System programmer response: Search problem
00xx0050 VSAM GENCB macro did not build a reporting data bases for a fix for the problem. If no fix
request parameter list (RPL) on a exists, contact the IBM Support Center.
GET request.
Source: Auxiliary storage manager (ASM)
000C0054 VSAM GET had a physical I/O error.
00140058 VSAM GET found the record was held
exclusively by another requestor. ASM
76 z/OS V1R10.0 MVS System Codes
089 • 08B
0007 The primary and home address spaces are not
089
equal.
Explanation: A paging I/O operation for the auxiliary
0008 The macro specified an incorrect TYPE
storage manager (ASM) resulted in a permanent I/O
parameter.
error caused by either hardware or software problems.
0009 The ID parameter is either incorrect or an ID
System action: If the I/O error occurred during a read
that the caller cannot use.
operation, the system writes a logrec data set error
record for abend X'089'. The system then abnormally 000A Data-in-virtual is processing another
ends the task that required the page with abend code data-in-virtual request with the specified ID.
X'028'.
000B The system already accessed an object with
If the I/O error occurred during a write operation, ASM the specified ID.
retries the write to a different location in the page data
set. ASM also writes a logrec data set error record. 000C The caller does not have the proper resource
access control facility (RACF) authorization to
If the I/O error was caused by hardware problems, the requested object. (Or, the caller is
logrec data set may contain a second error record, an attempting to use a password-protected data
outboard record (OBR) for the I/O error. set for an object. Data-in-virtual does not
support passwords.)
System programmer response: For a hardware
problem, contact hardware support. Otherwise, search 000D The specified range exceeds the maximum
problem reporting data bases for a fix for the problem. If allowable size for the object.
no fix exists, contact the IBM Support Center.
000E The system does not have access to an object
Source: Auxiliary storage manager (ASM) for the specified ID.
000F The specified range overlaps with a range
08A already mapped for the ID.
Explanation: The auxiliary storage manager (ASM) 0010 The specified virtual range overlaps with an
detected a paging I/O error. The problem may have already mapped virtual range in the current
been caused by either the hardware or the software. address space or the specified data space.
System action: ASM writes a logrec data set error 0011 An undetermined system or caller error
record. occurred while data-in-virtual was attempting to
access data from the object; all data was not
System programmer response: For a hardware
retained.
problem, contact hardware support. Otherwise, search
problem reporting data bases for a fix for the problem. If 0012 The virtual storage specified does not begin on
no fix exists, contact the IBM Support Center. a 4-kilobyte boundary.
Source: Auxiliary storage manager (ASM) 0013 The virtual storage specified is not in a
pageable private area subpool.
08B 0014 The system cannot use the virtual storage
specified to map an object. For example, the
Explanation: An error occurred while the system
virtual storage may contain storage assigned to
processed a data-in-virtual service request. Either a
virtual input output (VIO).
parameter on the DIV macro or another condition that
existed when the DIV macro was issued caused the 0015 The specified range of virtual storage contains
error. The 2 low-order bytes in register 15 contain a at least one page that was not in a virtual
hexadecimal reason code that explains the error: range obtained by a GETMAIN macro.
Code Explanation 0016 The specified virtual storage contains at least
one page in a range that is specified on a
0001 The caller requested an unknown service.
current PAGE FIX request; however,
0002 Data-in-virtual does not recognize the RETAIN=YES was not specified.
parameter list format.
0017 Portions of virtual storage that mapped the
0003 The input parameter list cannot be addressed. object were not addressable, and could not be
saved. Either a paging error occurred or data
0004 The parameter list specifies storage that
occupied a bad central storage frame.
data-in-virtual cannot address.
0018 The caller does not have UPDATE ACCESS to
0005 The parameter list contains a reserved field
the object.
that does not contain binary zeroes.
0019 Data-in-virtual marked as non-pageable a page
0006 The caller is not running in task mode.
Chapter 2. System Completion Codes 77
08B
in a range to be saved or reset. That is, a v A data space map while one or more
PAGE FIX was outstanding against the page. address space maps were still active under
a given ID
001A The specified range is not in any mapped area
of the object. v An address space map while one or more
data space maps were still active under a
001B The virtual storage area specified to be given ID
unmapped is not currently mapped.
002D Data-in-virtual deleted the data space.
001C Data-in-virtual cannot access the object at the However, the requested operation completed
current time; the object data set is in use. successfully.
001D The accessed object is not a virtual storage 002E Data-in-virtual deleted the data space. The
access method (VSAM) linear data set, and requested operation cannot be performed.
thus does not have the correct control interval
size that is implicit for a VSAM linear data set. 002F A page to be saved was in the define I/O on
(IOON) state.
001E The length of the DDNAME parameter value
exceeds the maximum size allowed. 0030 The virtual range specified contained at least
one define I/O on (IOON) page and
001F The caller’s storage key is not the same as RETAIN=YES was not specified.
when data-in-virtual issued the IDENTIFY.
0031 The caller specified an incorrect TTOKEN.
0020 A task that does not own the specified ID
issued a DIV macro with an ACCESS 0032 The caller is not authorized.
parameter. 0036 The DIV macro supplied an STOKEN value
0021 Data-in-virtual could not access portions of the that does not represent a valid data space that
object on permanent storage; therefore, all the requester can use.
data was not retained. 0037 The caller accessed an object that was defined
0022 A task issued a DIV macro with an IDENTIFY with SHAREOPTIONS other than (1,3), and
parameter for an object. The task does not LOCVIEW=YES was not specified.
own the virtual storage specified to be mapped. 0038 The caller attempted to access a non-linear
For authorized programs, that task or one of its data set.
subtasks does not own the storage.
0039 The DIV macro requested a SAVE or RESET
0023 The caller’s storage key does not permit on a data space range with DREF pages.
access to part or all of the specified storage to
be mapped. 003A Data-in-virtual attempted to MAP the virtual
storage of a ESO type Hiperspace.
0024 The caller issued a DIV macro while holding
the local lock. 003B Data-in-virtual attempted to UNMAP
Hiperspace storage, but RETAIN=YES was not
0025 The caller issued a DIV macro while in an specified.
environment that precludes the use of
Supervisor Call (SVC) instructions. 003C Data-in-virtual attempted to UNMAP virtual
storage that maps a Hiperspace data object,
0026 The caller issued a DIV macro, but was not in but RETAIN=YES was specified.
31-bit addressing mode.
003D The STOKEN for the object associated with the
0027 The specified OFFSET and SPAN parameters specified ID does not represent a valid
describe a range that exceeds the maximum Hiperspace that may be used with this request.
supported object size.
003E The Hiperspace object may not be accessed at
0028 Data-in-virtual attempted to access an empty this time. Either the maximum for READs has
data set for a DIV macro with MODE=READ. been reached, or there is a violation of SHARE
0029 Data-in-virtual attempted to map into a disabled options.
reference (DREF) data space. 003F The DIV macro specified LOCVIEW=MAP for
002A Data-in-virtual attempted to establish a mapped an ID associated with a Hiperspace object.
local view into a data space. LOCVIEW=MAP 0040 The specified MAP range would cause the
was specified on a previous DIV macro with an Hiperspace object to be extended such that the
ACCESS parameter. installation data space limits for the address
002B The specified virtual range exceeds the bounds space would be exceeded.
of the specified data space. 0041 The DIV macro specified an STOKEN with an
002C The caller requested either: ID that represents a Hiperspace data-in-virtual
78 z/OS V1R10.0 MVS System Codes
08B
object. Data space virtual storage cannot be 0050 The caller issued the DIV macro with the MAP
mapped into a Hiperspace. parameter for a Hiperspace object into shared
storage.
0042 The DIV macro tried to access a Hiperspace,
but the ALESERV ADD command already had 0051 The caller issued the DIV macro with the MAP
been entered for this Hiperspace. parameter for one member of a sharing group,
but this sharing group contains a member that
0046 The caller issued the DIV macro with the SAVE
is currently fixed.
or the SAVELIST parameter and specified an
incorrect LISTSIZE value. 0052 The virtual storage specified contains at least
one protected page and RETAIN=YES was not
0047 The caller issued a DIV macro with the SAVE
specified.
parameter with one of the required keywords
missing. The missing keyword is either 0053 The caller attempted to DIV MAP a page that
LISTADDR or LISTSIZE. is part of an address space view of a shared
segment.
0048 The caller issued a DIV macro with the SAVE
parameter and LISTADDR and LISTSIZE 0801 The storage available was insufficient for
keywords to specify a user list. One of the building the necessary data-in-virtual control
following problems occurred: block structure.
v The ranges specified for the user list do not 0802 An I/O driver failure occurred.
intersect with a mapped range.
0803 The system could not read a required page
v The user list contains incorrect data.
table into central storage.
0049 The caller issued a DIV macro with the SAVE
0804 The catalog update failed.
parameter using incorrect keywords. One of
the following is true: 0805 An undetermined system error occurred.
v The caller used keyword LISTADDR and 0806 An I/O error occurred.
LISTSIZE to specify a user list, but also
used one or both of the OFFSET or SPAN 0807 Data may be damaged in the allocated space
keywords. The LISTSIZE and LISTADDR on a direct access storage device (DASD). The
keywords are not compatible with the space is currently beyond the saved portion of
OFFSET and SPAN keywords. the object.
v The caller specified the STOKEN keyword 0808 The system has not completed I/O from a
with either the OFFSET or SPAN keywords. previous request.
The STOKEN keyword is incompatible with
the OFFSET and SPAN keywords. System action: The system abends the program that
issued the DIV macro. The system writes a logrec data
004A The caller issued a DIV macro with the SAVE set error record, and it may write a dump. If the reason
parameter but specified incorrect addresses in code is X'0805', data-in-virtual requested an SVC dump
the user list. Either an address was not on a with the title COMPON=DATA-IN-VIRTUAL.
page boundary or the start address was higher
than the end address. System programmer response: For reason code
0052, remove the protection status from the protected
004B The caller issued the DIV macro with SAVE pages in the specified virtual range. Then issue the DIV
parameter but specified a range in the user list macro again. If you want to invoke MAP or UNMAP and
that spans multiple data spaces or want to preserve the protection status, specify
Hiperspaces. RETAIN=YES when you issue the macro.
004C The caller issued the DIV macro with the SAVE For other reason codes, look in the system trace for the
parameter for a data space or Hiperspace but first PC entry with 00307 in the UNIQUE-1 column
did not specify the STOKEN keyword. above the SVC 0D entry for the X'08B' abend. The
004D The user is not authorized to ACCESS the address column contains the address of the program
requested data. that issued the DIV macro. Identify this program.
004E The caller issued the DIV macro with the MAP If the program is installation-provided, continue
parameter for a shared data page that does diagnosis with the program. If it is IBM-provided, search
not meet the requirement that it reside in the problem reporting data bases for a fix for the
non-swappable storage and have a problem. If no fix exists, contact the data-in-virtual
SHAREDWRITE view mode. component at the IBM support center.
004F The caller issued the DIV macro with the MAP Source: Data-in-virtual
parameter for another member of the same
sharing group.
Chapter 2. System Completion Codes 79
08C • 08D
ensure the SCHEDULE macro is being used with an
08C
SRB that is in common storage. For all other reason
Explanation: A program issued a SCHEDULE macro codes, do the following:
to schedule a service request block (SRB). The system 1. Ask the operator to set a SLIP trap to obtain an
detected an error while processing the macro. Register SVC dump.
2 contains the SRB address. Register 3 contains the
2. In the system trace, find the system service event
return address of the issuing program. A hexadecimal
(SSRV) entry for abend X'08C'. Diagnostic data in
reason code in register 15 explains the error:
this entry is as follows:
Code Explanation v The return address for the issuer of the
04 The address specified in field SRBASCB of the SCHEDULE macro is in the ADDR column.
service request block (SRB) does not point to a v The input SRB address is in the UNIQUE-1
valid address space control block (ASCB). column.
08 The ASCB specified in the SRB has the v The target address space ASCB address is in the
ASCBFAIL flag set on. The flag indicates that UNIQUE-2 column.
the address space is ending. v The STOKEN representing the target address
space is in the UNIQUE-3 column.
0C The specified STOKEN does not represent the
same address space as the ASCB specified in 3. Use the address in the ADDR column of the SSRV
the SRB. entry to identify the module that issued the
SCHEDULE macro.
10 A feature was requested using the SCHEDULE
v For an installation-provided module, continue
macro but there are no online processors with
diagnosis with the module.
the specified feature.
v For an IBM module, search problem reporting
14 An entry point was requested using the data bases for a fix for the problem. If no fix
SCHEDULE macro but an incorrect feature exists, contact the component group associated
indicator was specified. with this module at the IBM Support Center.
18 A feature was requested using the SCHEDULE Provide all problem data collected and, if
macro but an non-valid feature indicator was available, the logrec data set error record.
specified. Source: Supervisor control
1C An internal error occurred during schedule
processing. 08D
20 A program issued a SCHEDULE macro to Explanation: A system error occurred during converter
schedule an SRB with the SPTOKEN option processing. A hexadecimal reason code in register 15
while holding a lock higher than or equal to the explains the error:
DISP lock in the locking hierarchy. You cannot
use the SPTOKEN option while holding a lock Code Explanation
equal to or higher than the DISP lock. 0001 The system found a storage management
24 DISABLED was specified on the SCHEDULE error.
macro, but the caller was not disabled. 0002 The system found an error while processing an
28 The caller was in AR ASC mode but did not IF statement.
specify this via the SYSSTATE macro. 0003 The system found an error in the statement
2C The SRB was not in common storage. ordering routing processing.
System action: The system abnormally ends the 0004 The system could not find more storage for the
program that issued the SCHEDULE macro. The converter text data space. Either a large
system may write a logrec data set error record. amount of JCL or an internal error caused the
lack of storage.
Operator response: If the system programmer asks
for an SVC dump, set the following SLIP trap: 0005 The system found an error in the symbol table
processor.
SLIP SET,COMP=08C,ACTION=SVCD,END
0006 The system found an error in the build
System programmer response: For reason code 10,
message processor.
resubmit the job on a processor complex that has the
feature installed. For reason code 24, you must obtain 0008 During merge processing, the system found a
the CPU lock before using the SCHEDULE macro. For statement type that is not valid.
reason code 28, specify SYSSTATE ASCENV=AR prior
020x The system found an internal error while
to issuing the SCHEDULE macro in order to ensure the
macro expansion will be correct. For reason code 2C,
80 z/OS V1R10.0 MVS System Codes
08E • 08F
processing an Advanced Program-to-Program 10 At least one page in the specified virtual
Communications (APPC) transaction program storage range is part of a sharing group that
(TP). has been defined by the IARVSERV macro.
Other The system found an internal error. The system restores all storage keys to their
previous value.
System action: The system ends converter
processing and does not run the job. 14 An unexpected internal error occurred.
System programmer response: Search problem The system restores all pages processed by
reporting data bases for a fix for the problem. If no fix the CHANGKEY macro before the error to their
exists, contact the group for the converter component at previous key.
the IBM support center.
18 A request was made to change a key to 0.
Source: Converter
The system restores all pages processed by
the CHANGKEY macro before the error to their
08E previous key.
Explanation: The address space was abended by an 2C One of the following is true:
IMS™ address space. v The beginning address of the virtual storage
System action: The address space is abnormally range specified on the CHANGKEY macro is
ended. greater than the ending address
v At least one page in the specified virtual
Application Programmer Response: If the ending
storage range is in an unauthorized subpool.
address space is a CCTL that is hooked up to IMS
(DBCTL), then the S08E abend is a result of an
The system does not restore all pages
operator CANCEL request for that address space.
processed by the CHANGKEY macro before
CICS® is an example of a CCTL. No further action is
the error to their previous key.
needed if the address space ends to completion. If not,
then the operator should try the FORCE command, 34 The parameter list specified by the LISTAD
which IMS will internally change to a CANCEL parameter was in pageable storage.
command. If the address space still doesn’t end after
this first FORCE attempt, then the operator can enter The system does not restore all pages
the FORCE command again. IMS will not change this processed by the CHANGKEY macro before
FORCE attempt, and MVS will process the FORCE to the error to their previous key.
end the address space. 38 At least one page in the specified virtual
Source: DFSMSdfp storage range is part of a sharing group.
The system does not restore all pages
08F processed by the CHANGKEY macro before
the error to their previous key.
Explanation: An error occurred during processing of a
CHANGKEY macro. 3C An unexpected internal error occurred.
Register 15 contains a hexadecimal reason code: The system does not restore all pages
processed by the CHANGKEY macro before
Code Explanation the error to their previous key.
04 One of the following is true: System action: The system issues an abend to the
v The beginning address of the virtual storage caller of the CHANGKEY macro. The system writes
range specified on the CHANGKEY macro is messages, the logrec data set error record, and the
greater than the ending address SYSOUT output for the job.
v At least one page in the specified virtual Application Programmer Response: For return code
storage range is in an unauthorized subpool. 04, 18, 0C, 2C, or 34, correct the error condition
indicated.
The system restores all pages processed by
For return code 14 or 3C, run the job step again.
the CHANGKEY macro before the error to their
previous key. For return code 10 or 38, modify the program to correct
the IARVSERV macro with the SHARE parameter for
0C The parameter list specified by the LISTAD
the virtual storage range in error. Return code 10 and
parameter was in pageable storage.
38 are relevant only with a READONLY or
The system restores all pages processed by SHAREWRITE view. If the program did not issue the
the CHANGKEY macro before the error to their IARVSERV macro, contact the system programmer.
previous key.
Chapter 2. System Completion Codes 81
090 • 094
System programmer response: Search problem
092
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the Explanation: The error occurred during processing of
messages, the logrec data set record, and the SYSOUT a basic telecommunications access method (BTAM)
output for the job. OPEN macro. An OPEN routine found an incorrect or
unsupported type of terminal control or terminal adapter
Source: Real storage manager (RSM)
specified in the unit control block (UCB) for the device
allocated to the data control block (DCB) being opened.
090
Application Programmer Response: Check for
Explanation: The error occurred during processing of improper specification of the ADAPTER parameter in
a basic telecommunications access method (BTAM) the IODEVICE macro used in generating the system.
OPEN macro. An OPEN routine found that a device Also, check for program errors that could have
other than a communications device was allocated to improperly modified control information. Correct the
the data control block (DCB) being opened. That is, the error, and run the job step again.
device class code in the unit control block (UCB) for the
System programmer response: If the error recurs
device allocated to the data control block was not equal
and the program is not in error, look at the messages in
to X'40'.
the job log for more information. Search problem
Application Programmer Response: Either the UNIT reporting data bases for a fix for the problem. If no fix
parameter of the DD statement for the communications exists, contact the IBM Support Center. Provide the JCL
device is incorrect or the UCB generated during system and the program listing for the job.
generation is incorrect. Check for improper specification
Source: Teleprocessing
of the UNIT parameter or the IODEVICE macro used in
generating the system. Also, check for program errors
that could have improperly modified control information. 093
After correcting the error, run the job step again.
Explanation: The error occurred during processing of
System programmer response: If the error recurs a basic telecommunications access method (BTAM)
and the program is not in error, look at the messages in OPEN macro. An OPEN routine found an incorrect or
the job log for more information. Search problem unsupported type of terminal specified in the unit control
reporting data bases for a fix for the problem. If no fix block (UCB) for the device allocated to the data control
exists, contact the IBM Support Center. Provide the JCL block (DCB) being opened.
and the program listing for the job.
Application Programmer Response: Check for
Source: Teleprocessing improper specification of the UNIT parameter in the
IODEVICE macro used in generating the system. Also,
check for program errors that could have improperly
091
modified control information. Correct the error, and run
Explanation: The error occurred during processing of the job step again.
a basic telecommunications access method (BTAM)
System programmer response: If the error recurs
OPEN macro. An OPEN routine found an incorrect or
and the program is not in error, look at the messages in
unsupported type of transmission control unit specified
the job log for more information. Search problem
in the unit control block (UCB) for the device allocated
reporting data bases for a fix for the problem. If no fix
to the data control block (DCB) being opened.
exists, contact the IBM Support Center. Provide the JCL
Application Programmer Response: Check for and the program listing for the job.
improper specification of the IODEVICE macro used in
Source: Teleprocessing
generating the system. Also, check for program errors
that could have improperly modified control information.
After correcting the error, run the job step again. 094
System programmer response: If the error recurs Explanation: The error occurred during processing of
and the program is not in error, look at the messages in a basic telecommunications access method (BTAM)
the job log for more information. Search problem OPEN macro. An OPEN routine found an incorrect or
reporting data bases for a fix for the problem. If no fix unsupported optional feature or mode of operation
exists, contact the IBM Support Center. Provide the JCL specified in the unit control block (UCB) for the device
and the program listing for the job. allocated to the data control block (DCB) being opened.
Source: Teleprocessing Application Programmer Response: Check for
improper specification of the FEATURE parameter in the
IODEVICE macro used in generating the system. Also,
check for program errors that could have improperly
82 z/OS V1R10.0 MVS System Codes
095 • 099
modified control information. Correct the error, and run and the program listing for the job.
the job step again.
Source: Teleprocessing
System programmer response: If the error recurs
and the program is not in error, look at the messages in
097
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix Explanation: The error occurred during processing of
exists, contact the IBM Support Center. Provide the JCL a basic telecommunications access method (BTAM)
and the program listing for the job. OPEN macro. The open routine required an additional
entry in the device I/O directory. However, the directory
Source: Teleprocessing
was already full. Since the last system start, the
maximum number of device types has already been
095 opened. Normally, the maximum number of device types
is 30.
Explanation: The error occurred during processing of
a basic telecommunications access method (BTAM) Application Programmer Response: Additional
OPEN macro. An OPEN routine found that the lines space in the device I/O directory can be provided by
allocated to the line group did not have identical changing one statement in the read/write routine. The
terminal types and/or optional features. statement following the one labeled IOD must be
changed. The duplication factor must be increased to
Application Programmer Response: Determine
correspond to the number of different device types
which line group contains different terminals and
being used. The new read/write routine must be
redefine its lines through DD statements.
reassembled and link edited to SVCLIB.
System programmer response: If the error recurs
System programmer response: If the error recurs
and the program is not in error, look at the messages in
and the program is not in error, look at the messages in
the job log for more information. Search problem
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
exists, contact the IBM Support Center. Provide the JCL
JCL.
and the program listing for the job.
Source: Teleprocessing
Source: Teleprocessing
096
098
Explanation: The error occurred during processing of
Explanation: The error occurred during processing of
a basic telecommunications access method (BTAM)
a basic telecommunications access method (BTAM)
OPEN macro. An OPEN routine found that dynamic
OPEN macro. Dual communication interface B or dual
buffer allocation had been specified in the DCBBFTEK
code feature B was specified. However, the
field of the data control block (DCB). However, the
transmission control unit was not a 2701, the
OPEN routine could not dynamically allocate buffers
transmission control unit was not the dual
because the data control block specified neither the
communication interface, or the dual code feature was
address of a buffer pool control block (in the
not specified in the unit control block (UCB).
DCBBUFCB field) nor the number and length of the
buffers (in the DCBBUFNO and DCBBUFL fields). Application Programmer Response: Correct
program errors. Run the job again.
Application Programmer Response: Correct the
error by doing one of the following: System programmer response: If the error recurs
v Providing a buffer pool and specifying the address of and the program is not in error, look at the messages in
its control block in the DCBBUFCB field. the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
v Specifying the number and length of the buffers in
exists, contact the IBM Support Center. Provide the JCL
the DCBBUFNO and DCBBUFL fields.
and the program listing for the job.
v Handling buffering in the program and deleting the
BFTEK=D operand in the DCB macro or DCB Source: Teleprocessing
parameter of the DD statement.
099
Then run the job step again.
Explanation: The error occurred during processing of
System programmer response: If the error recurs a basic telecommunications access method (BTAM)
and the program is not in error, look at the messages in OPEN macro. An OPEN routine found that dynamic
the job log for more information. Search problem buffering was being initiated while the BTAM application
reporting data bases for a fix for the problem. If no fix was running V=V. BTAM dynamic buffering is not
exists, contact the IBM Support Center. Provide the JCL supported for V=V.
Chapter 2. System Completion Codes 83
09A
Application Programmer Response: Add the was received from MSGSERV. This
ADDRSPC=REAL operand to the job statement and typically occurs when the user issues
initiate the BTAM application again (V=R). a form of the command that generates
too much output, ″D GRS,ALL″ or ″D
System programmer response: If the error recurs
GRS,RES=(*,SYSDSN)″, for example.
and the program is not in error, look at the messages in
the job log for more information. Search problem 4814 An error occurred in the Queue Merge
reporting data bases for a fix for the problem. If no fix processing when this system tried to
exists, contact the IBM Support Center. Provide the JCL rejoin the GRS ring.
and the program listing for the job.
4818 An error occurred in Queue Merge
Source: Teleprocessing processing when this system tried to
rejoin the GRS ring.
09A 6324 Issued when an attempt is made to
initiate I/O on a CTC that has I/O still
Explanation: Global resource serialization
pending.
encountered an error.
68C8 Indicates a non-zero return code from
Note: The X'09A' abend code does not propagate to an IXCMOD request. GRS issues
GQSCAN’s caller. IXCMOD to change its XCF
monitoring interval.
The two low-order bytes of register 15 contain a 68CA An IXCPART partition request
hexadecimal function and reason code: returned a return code or reason code
Code Explanation that is not expected. GRS issues
IXCPART to remove a system from
1208 Issued when the GRS receives the sysplex.
notification for a global resource that
is not known to GRS. 81xx or 85xx An error occurred in storage manager
allocation processing while trying to
1210 Issued when the GRS receives allocate a cell.
notification for a global ENQ or DEQ
request that is not known to GRS. 82xx or 87xx An error occurred in storage manager
deallocation processing while trying to
1904 An invalid control block was detected deallocate a cell.
while running in GRS=STAR mode.
A114 Issued when the GQSCAN RESNAME
2204 Issued by when the system cannot specification contains a QNAME
create the GRS address space. ADDR and QNAME length of 0-7, but
| 2505 GRS could not create a dependent with RNAME ADDR, RNAME length,
| enclave for the GRS EQDQ monitor to and specific/generic omitted (for
| use because of an unexpected return example, RESNAME=(QNAME,,,,7)).
| or reason code from the WLM A142 Indicates a GQSCAN with SYSNAME
| IWMECREA service. The IWMECREA was in progress, but the SYSNAME
| return and reason codes were placed was unknown. This can occur when
| in registers 2 and 3 before the abend normal ENQ/DEQ processing changes
| is issued. control blocks while GQSCAN
3106 Issued by the GRS Lock Structure processing is looking at them. A dump
Complete Exit and indicates the is produced because recovery cannot
resource specified in the exit is not determine the cause the cause of the
known to GRS. changing control blocks (for example,
if they changed because of normal
3705 Issued when GRS STAR Mode global ENQ/DEQ activity, or if they changed
GQSCAN processing could not add because of an overlay or other serious
the ISGQSCAN dataspace to the event).
DU-AL.
A2xx ISGQSCNR, which is the GQSCAN
xxD5 Issued when the GRS Message Exit service’s functional recovery routine,
failed to receive an incoming message converted the ABEND.
through the IXCMSGI macro.
A220 An undefined error occurred during
46FA Issued by ISGCDSP as part of execution of the GQSCAN service,
″DISPLAY GRS″ D GRS processing. which is the GQSCAN service routine.
X'FA' indicates a non-zero return code The system saves the original
84 z/OS V1R10.0 MVS System Codes
09A
completion code in register 2 and the Operator response: For C50C: Inform the system
original reason code in register 3. programmer.
A22C An unexpected error occurred when For some 09A abends, you should obtain a dump of the
the ISGQSCAN information routine GRS address space from each system in the global
was activated to obtain requestor resource serialization complex. The IBM Support Center
information from the service address will request the dumps for diagnosis. The following
space. GQSCAN recovery will not function and reason codes require a dump from each
percolate to the GQSCAN caller’s system in the complex:
recovery since retry is requested. v 43yy
C50C The GRS STAR sysplex wide global v 44yy
resource contention notification server v 45yy
task, ENF 51 issuer, has determined
v 62yy
that the length of its processing queue
has reached a critical threshold. This v 65yy
indicates that the task can not keep v 66yy
up with the amount of work asked of v 67yy
it. This could be due to dispatch
priority, a large amount of sysplex v 6Ayy
wide contention, or a problem with the v 6Cyy
server. v C1yy
C544 Function code C5 is module ISGGCN v E1yy
the contention notification task. v E3yy
Subfunction 44 indicates GQSCAN.
This reason code indicates a failure You do not need to obtain a dump for the codes above
occurred in GQSCAN during when yy is one of the following:
contention notification processing. v 45
Others Internal error. IBM might request this v 90
| information for diagnosis. The v B2
| contents of registers 3 through 5 may v B6
| contain diagnostic data. v E0
v EC
System action: System processing continues. The v FA
system usually writes a logrec data set error record and v FC
issues an SVC dump. For reason codes X'4814' and
X'4818', the system will attempt to force a dump on the Application Programmer Response: Do one of the
system in the complex which was assisting with the following:
rejoin process. v If mmff is 4808, 480C, or 4810, this is probably a
user error. Correct the problem and resubmit the job.
For C50C: The contention notification task:
v If mmff is 46FA, check to see if the problem was
1. Takes an SVC dump to identify the instance and to
caused by a shortage of WTO buffer space. If not,
gather diagnostic data.
contact the IBM Support Center and provide the
2. Prevents any more elements from being queued. return code in register 2.
3. Informs ENF listeners that the ENF 51 data is v If the reason and function codes are A2xx, the
temporarily suppressed and that some data could be problem is with the GQSCAN macro. Respecify the
lost. GQSCAN macro.
4. Purges all queued elements.
5. Gives up ownership of the sysplex wide function. If the problem persists, search problem reporting data
Because ownership is relinquished, another bases for a fix for the problem. If no fix exists, contact
contention notification server on a different sysplex the IBM Support Center.
system, who may or may not have more resources, System programmer response: If the problem
could become the sysplex wide notification server. If persists, search problem reporting data bases for a fix
there is no other system, the same system will for the problem. If no fix exists, contact the IBM Support
continue being the owner. Use the DISPLAY GRS Center. Provide the function and reason codes, the
command, found in z/OS MVS System Commands logrec data set error record, and the dump. For the
to determine which system is the notification server. appropriate reason and function codes, provide a dump
6. The new owner will inform ENF listeners that the of the GRS address space dumps for each system in
data is valid again. the global resource serialization complex. Provide all
dumps taken by GRS recovery for the ABEND.
Chapter 2. System Completion Codes 85
09B • 09E
For C50C, before you contact the IBM support center,
09E
use the monitors to determine if an application created
an abnormal amount of contention. If so, consider Explanation: During processing of a system trace
changing the application, or use the following installation routine, the system detected an error.
exits to suppress notification of specific high frequency
Register 15 contains a hexadecimal reason code that
contention cases:
explains the error:
v ISGCNFXITSYSTEM
Code Explanation
v ISGCNFXITSYSPLEX.
0251 The system trace address space could not be
Also, check for any possible dispatch priority issues.
created. The nonzero return code was placed
Source: Global resource serialization in register 2. The reason code was placed in
register 3.
09B 0252 The system trace function could not be
initialized. The nonzero return code was placed
Explanation: An abnormal end occurred in IP
in register 2.
PrintWay™. This system completion code and the IP
PrintWay abend reason code are contained in either 0261 The ESTAE macro failed to establish a
message ANFM102I or ANFM105I. See z/OS Infoprint recovery environment. The nonzero return
Server Messages and Diagnosis for an explanation of code from ESTAE was placed in register 2.
the abend reason code.
0351 An error occurred while waiting for the master
Application Programmer Response: Respond as address space to complete initialization. A
indicated for message ANFM102I or ANFM105I. nonzero return code was passed in register 15.
A reason code was passed in register 0. The
Problem determination: If the error recurs, search
return code was placed in register 2.
problem-reporting data bases for a fix for the problem. If
no fix exists, contact the IBM support center. 0361 The ESTAE macro failed to establish a
recovery environment. The nonzero return
Source: IP PrintWay
code from ESTAE was placed in register 2.
1211 The system detected an incorrect control block
09D
acronym. Register 2 contains the real address
Explanation: A PTRACE macro was issued requesting of the control block. Register 3 contains the
the creation of a trace table entry to be placed in the expected acronym.
system trace table. A system trace service routine
1212 The system detected an incorrect control block
detected an error in the PTRACE macro.
level number. Register 2 contains the real
Register 15 contains a hexadecimal reason code that address of the control block. Register 3
explains the error: contains the acronym of the control block.
Register 4 contains the detected and expected
Code Explanation level numbers.
1151 Input register 1 of the PTRACE macro issuer 2100 The request for a system trace was not issued
contains an incorrect register range. Register 2 in task mode.
contains the incorrect register range that was
input in register 1. 2101 The system trace request is incorrect because
the option is not valid. The request is received
1152 The parameter area of the PTRACE macro in register 1 and placed in register 2.
issuer contains more than 1024 words of data
to be traced. Register 2 contains the address 2102 The trace request is incorrect because the
of the user parameter area (input register 1). request type is not valid. The request is
Register 3 contains the number of words of received in register 0 and placed in register 2.
data to be traced from the user parameter
2201 The trace request is incorrect for one of the
area.
following reasons:
System action: The system abnormally ends the task v Register 0 did not contain the address of a
associated with the program that issued the PTRACE physical configuration communication area
macro. (PCCA) or X'FFFFFFFF'.
Application Programmer Response: Correct the v The request type in register 1 was not
PTRACE macro. Run the job again. TRACEON, TRACEOFF, or TRACEFIX.
Source: System trace
86 z/OS V1R10.0 MVS System Codes
09E
The request input is received in registers 0 and 2411 The system found an incorrect acronym in the
1 and the detected request is placed in system trace option block (TOB). Register 2
registers 2 and 3. contains the address of the TOB. Register 3
contains the detected acronym.
2202 Trace requests conflict for one of the following
reasons: 2412 The system found an incorrect level number in
v A single processor request specified a the system trace option block (TOB). Register
change in the trace options or number of 2 contains the address of the TOB. Register 3
buffers. contains the detected and expected level
numbers.
v Both ON and OFF were requested for the
AS, BR, or EX options. 2413 The system found an incorrect acronym in a
v The reserved bits were not zero. system trace buffer vector table (TBVT).
Register 2 contains the address of the TBVT.
The request input is received in registers 0 and Register 3 contains the detected acronym.
1 and the detected request is placed in 2414 The system found an incorrect level number in
registers 2 and 3. a system trace buffer vector table (TBVT).
2211 The system found an incorrect acronym in the Register 2 contains the address of the TBVT.
system trace option block (TOB). Register 2 Register 3 contains the detected and expected
contains the address of the TOB. Register 3 level numbers.
contains the detected acronym. 2501 The system found an incorrect acronym in the
2212 The system found an incorrect level number in system trace SNAPTRC parameter list (TRSN).
the system trace option block (TOB). Register Register 2 contains the address of the TRSN.
2 contains the address of the TOB. Register 3 Register 3 contains the detected acronym.
contains the detected and expected level 2502 The system found an incorrect level number in
numbers. the system trace SNAPTRC parameter list
2301 The system found an incorrect acronym in the (TRSN). Register 2 contains the address of the
system trace services parameter list (TRSP). TRSN. Register 3 contains the detected and
Register 2 contains the address of the TRSP. expected level numbers.
Register 3 contains the detected acronym. 2503 The system found an incorrect request type in
2302 The system found an incorrect level number in the system trace SNAPTRC parameter list
the system trace services parameter list (TRSN). The request type is not one of the
(TRSP). Register 2 contains the address of the expected constants:
TRSP. Register 3 contains the detected and v TRSNASFR
expected level numbers. v TRSNFREE
v TRSNSNAP
2311 The system found an incorrect acronym in the v TRSNTKFR
system trace option block (TOB). Register 2
contains the address of the TOB. Register 3 Register 2 contains the address of the TRSN.
contains the detected acronym. Register 3 contains the detected request type.
2312 The system found an incorrect level number in 2601 The system found an incorrect acronym in the
the system trace option block (TOB). Register system trace services parameter list (TRSP).
2 contains the address of the TOB. Register 3 Register 2 contains the address of the TRSP.
contains the detected and expected level Register 3 contains the detected acronym.
numbers.
2602 The system found an incorrect level number in
2313 The system found an incorrect acronym in a the system trace services parameter list
system trace buffer vector table (TBVT). (TRSP). Register 2 contains the address of the
Register 2 contains the address of the TBVT. TRSP. Register 3 contains the detected and
Register 3 contains the detected acronym. expected level numbers.
2314 The system found an incorrect level number in 2701 The system found an incorrect acronym in the
a system trace buffer vector table (TBVT). system trace services parameter list (TRSP).
Register 2 contains the address of the TBVT. Register 2 contains the address of the TRSP.
Register 3 contains the detected and expected Register 3 contains the detected acronym.
level numbers.
2702 The system found an incorrect level number in
2401 The trace request could not be recognized. the system trace services parameter list
The specified option is not SUSPEND, (TRSP). Register 2 contains the address of the
RESUME, or PSTART. The request was TRSP. Register 3 contains the detected and
received in register 1 and placed in register 2. expected level numbers.
Chapter 2. System Completion Codes 87
09E
2801 The system found an incorrect acronym in the a parameter. Register 3 contains the control
system trace COPYTRC parameter list (TRCT). block address. Register 4 contains the
Register 2 contains the address of the TRCT. acronym of the control block. Register 5
Register 3 contains the detected acronym. contains the detected and expected level
numbers.
2802 The system found an incorrect level number in
the system trace COPYTRC parameter list 4203 The system detected an incorrect parameter.
(TRCT). Register 2 contains the address of the Register 3 contains the control block address.
TRCT. Register 3 contains the detected and Register 4 contains the acronym of the
expected level numbers. incorrect control block. Register 5 contains the
offset into the control block of the error.
2811 The system found an incorrect acronym in a
Register 6 contains the content of the incorrect
system trace table snapshot copy header
field.
(TTCH). Register 2 contains the address of the
TTCH. Register 3 contains the detected 5101 The system found an incorrect acronym in the
acronym. system trace table format request parameter
list (TRFM). Register 2 contains the address of
2812 The system found an incorrect level number in
the TRFM. Register 3 contains the detected
a system trace table snapshot copy header
acronym.
(TTCH). Register 2 contains the address of the
TTCH. Register 3 contains the detected and 5102 The system found an incorrect level number in
expected level numbers. the system trace table format request
parameter list (TRFM). Register 2 contains the
2901 The system found an incorrect acronym in the
address of the TRFM. Register 3 contains the
system trace SNAPTRC parameter list (TRSN).
detected and expected level numbers.
Register 2 contains the address of the TRSN.
Register 3 contains the detected acronym. 5151 The address of the current system trace table
entry (TTE) is past the expected end of data in
2902 The system found an incorrect level number in
the buffer for the current processor. Register 2
the system trace SNAPTRC parameter list
contains the address of the TTE. Register 3
(TRSN). Register 2 contains the address of the
contains the address of the expected end of
TRSN. Register 3 contains the detected and
data. Register 4 contains the processor index
expected level numbers.
into the trace formatter work area (TFWA).
2911 The system found an incorrect acronym in a
5161 An ESTAE macro issued to establish a
system trace table snapshot copy header
recovery environment failed. Register 2
(TTCH). Register 2 contains the address of the
contains the ESTAE return code.
TTCH. Register 3 contains the detected
acronym. 5201 The system found an incorrect acronym in the
trace formatter work area (TFWA). Register 2
2912 The system found an incorrect level number in
contains the address of the TFWA. Register 3
a system trace table snapshot copy header
contains the detected acronym.
(TTCH). Register 2 contains the address of the
TTCH. Register 3 contains the detected and 5202 The system found an incorrect level number in
expected level numbers. the trace formatter work area (TFWA). Register
2 contains the address of the TFWA. Register
4101 The system found an incorrect acronym in a
3 contains the detected and expected level
parameter. Register 3 contains the control
numbers.
block address. Register 4 contains the
expected acronym. Register 5 contains the 5301 The system found an incorrect acronym in the
detected acronym. trace formatter work area (TFWA). Register 2
contains the address of the TFWA. Register 3
4102 The system found an incorrect level number in
contains the detected acronym.
a parameter. Register 3 contains the control
block address. Register 4 contains the 5302 The system found an incorrect level number in
acronym of the control block. Register 5 the trace formatter work area (TFWA). Register
contains the detected and expected level 2 contains the address of the TFWA. Register
numbers. 3 contains the detected and expected level
numbers.
4201 The system found an incorrect acronym in a
parameter. Register 3 contains the control 5351 The system has determined that no valid ASID
block address. Register 4 contains the filtering options were specified. Register 2
expected acronym. Register 5 contains the contains the address of the TFWA. Register 3
detected acronym. contains the contents of TFWAFLG1.
4202 The system found an incorrect level number in 5401 The system found an incorrect acronym in the
88 z/OS V1R10.0 MVS System Codes
09E
trace formatter work area (TFWA). Register 2 5902 The system found an incorrect level number in
contains the address of the TFWA. Register 3 the trace formatter work area (TFWA). Register
contains the detected acronym. 2 contains the address of the TFWA. Register
3 contains the detected and expected level
5402 The system found an incorrect level number in
numbers.
the trace formatter work area (TFWA). Register
2 contains the address of the TFWA. Register 5A01 The system found an incorrect acronym in the
3 contains the detected and expected level trace formatter work area (TFWA). Register 2
numbers. contains the address of the TFWA. Register 3
contains the detected acronym.
5501 The system found an incorrect acronym in the
trace formatter work area (TFWA). Register 2 5A02 The system found an incorrect level number in
contains the address of the TFWA. Register 3 the trace formatter work area (TFWA). Register
contains the detected acronym. 2 contains the address of the TFWA. Register
3 contains the detected and expected level
5502 The system found an incorrect level number in
numbers.
the trace formatter work area (TFWA). Register
2 contains the address of the TFWA. Register 5B01 The system found an incorrect acronym in the
3 contains the detected and expected level trace formatter work area (TFWA). Register 2
numbers. contains the address of the TFWA. Register 3
contains the detected acronym.
5601 The system found an incorrect acronym in the
trace formatter work area (TFWA). Register 2 5B02 The system found an incorrect level number in
contains the address of the TFWA. Register 3 the trace formatter work area (TFWA). Register
contains the detected acronym. 2 contains the address of the TFWA. Register
3 contains the detected and expected level
5602 The system found an incorrect level number in
numbers.
the trace formatter work area (TFWA). Register
2 contains the address of the TFWA. Register 5C01 The system found an incorrect acronym in the
3 contains the detected and expected level trace formatter work area (TFWA). Register 2
numbers. contains the address of the TFWA. Register 3
contains the detected acronym.
5701 The system found an incorrect acronym in the
trace formatter work area (TFWA). Register 2 5C02 The system found an incorrect level number in
contains the address of the TFWA. Register 3 the trace formatter work area (TFWA). Register
contains the detected acronym. 2 contains the address of the TFWA. Register
3 contains the detected and expected level
5702 The system found an incorrect level number in
numbers.
the trace formatter work area (TFWA). Register
2 contains the address of the TFWA. Register 5D01 The system found an incorrect acronym in the
3 contains the detected and expected level trace formatter work area (TFWA). Register 2
numbers. contains the address of the TFWA. Register 3
contains the detected acronym.
5703 The system requested that the work buffer for
a processor be refilled while the processor’s 5D02 The system found an incorrect level number in
end of trace data bit was turned on. Register 2 the trace formatter work area (TFWA). Register
contains the address of the trace formatter 2 contains the address of the TFWA. Register
work area (TFWA). Register 3 contains the 3 contains the detected and expected level
processor index into the TFWA. Register 4 numbers.
contains the physical address of the processor.
5E01 The system found an incorrect acronym in the
5801 The system found an incorrect acronym in the trace formatter work area (TFWA). Register 2
trace formatter work area (TFWA). Register 2 contains the address of the TFWA. Register 3
contains the address of the TFWA. Register 3 contains the detected acronym.
contains the detected acronym.
5E02 The system found an incorrect level number in
5802 The system found an incorrect level number in the trace formatter work area (TFWA). Register
the trace formatter work area (TFWA). Register 2 contains the address of the TFWA. Register
2 contains the address of the TFWA. Register 3 contains the detected and expected level
3 contains the detected and expected level numbers.
numbers.
5F01 The system found an incorrect acronym in the
5901 The system found an incorrect acronym in the trace formatter work area (TFWA). Register 2
trace formatter work area (TFWA). Register 2 contains the address of the TFWA. Register 3
contains the address of the TFWA. Register 3 contains the detected acronym.
contains the detected acronym.
5F02 The system found an incorrect level number in
Chapter 2. System Completion Codes 89
09E
the trace formatter work area (TFWA). Register 2 contains the address of the TFWA. Register
2 contains the address of the TFWA. Register 3 contains the detected and expected level
3 contains the detected and expected level numbers.
numbers.
6801 Incorrect TFWA parameter acronym.
6101 The system found an incorrect acronym in the
6802 Incorrect TFWA parameter level number.
trace formatter work area (TFWA). Register 2
contains the address of the TFWA. Register 3 7451 The system found an incorrect acronym in the
contains the detected acronym. system trace vector table (TRVT). A CALLRTM
TYPE=MEMTERM had been issued for the
6102 The system found an incorrect level number in
trace address space.
the trace formatter work area (TFWA). Register
2 contains the address of the TFWA. Register 7452 The system found an incorrect level number in
3 contains the detected and expected level the system trace vector table (TRVT). A
numbers. CALLRTM TYPE=MEMTERM had been issued
for the trace address space.
6301 The system found an incorrect acronym in the
trace formatter work area (TFWA). Register 2 7461 The system found an incorrect acronym in the
contains the address of the TFWA. Register 3 system trace option block (TOB). A CALLRTM
contains the detected acronym. TYPE=MEMTERM had been issued for the
trace address space.
6302 The system found an incorrect level number in
the trace formatter work area (TFWA). Register 7462 The system found an incorrect level number in
2 contains the address of the TFWA. Register the system trace option block (TOB). A
3 contains the detected and expected level CALLRTM TYPE=MEMTERM had been issued
numbers. for the trace address space.
6401 The system found an incorrect acronym in the 7470 The system found errors in the system trace
trace formatter work area (TFWA). Register 2 control blocks or queues. The functional
contains the address of the TFWA. Register 3 recovery routine (FRR) IEAVETRR, entry point
contains the detected acronym. IEAVETFR, records the errors.
6402 The system found an incorrect level number in 7501 The system found an incorrect acronym in the
the trace formatter work area (TFWA). Register system trace services parameter list (TRSP).
2 contains the address of the TFWA. Register Register 2 contains the address of the TRSP.
3 contains the detected and expected level Register 3 contains the detected acronym.
numbers.
7502 The system found an incorrect level number in
6501 The system found an incorrect acronym in the the system trace services parameter list
trace formatter work area (TFWA). Register 2 (TRSP). Register 2 contains the address of the
contains the address of the TFWA. Register 3 TRSP. Register 3 contains the detected and
contains the detected acronym. expected level numbers.
6502 The system found an incorrect level number in System action: The system abnormally ends the
the trace formatter work area (TFWA). Register current task. The system may abnormally end the trace
2 contains the address of the TFWA. Register address space. The system writes a logrec data set
3 contains the detected and expected level error record and a dump.
numbers.
The system may issue message IEA133E.
6601 The system found an incorrect acronym in the
trace formatter work area (TFWA). Register 2 Operator response: Enter the TRACE command to
contains the address of the TFWA. Register 3 restart the trace address space. Notify the system
contains the detected acronym. programmer.
6602 The system found an incorrect level number in System programmer response: If the error recurs,
the trace formatter work area (TFWA). Register search problem reporting data bases for a fix for the
2 contains the address of the TFWA. Register problem. If no fix exists, contact the IBM Support
3 contains the detected and expected level Center. Provide the logrec data set error record, the
numbers. dump, and all printed output and output data sets
related to the problem.
6701 The system found an incorrect acronym in the
trace formatter work area (TFWA). Register 2 Source: System trace
contains the address of the TFWA. Register 3
contains the detected acronym.
6702 The system found an incorrect level number in
the trace formatter work area (TFWA). Register
90 z/OS V1R10.0 MVS System Codes
09F • 0A0
2. Use the program status word (PSW) at the time of
09F
error to identify the module that issued the vector
Explanation: A program issued a vector instruction, instruction.
but the system cannot create the proper environment for v For an installation-provided module, continue
the vector operation. The program is running under a diagnosis with the module.
task control block (TCB) or service request block (SRB).
v For an IBM module, search problem reporting
A hexadecimal reason code in register 15 explains the
data bases for a fix for the problem. If no fix
error:
exists, contact the component group associated
Code Explanation with this module at the IBM Support Center.
Provide, if available, the SVC dump and the
00 The program issued the vector operation in
logrec data set error record.
SRB mode.
Source: Supervisor control
04 The program issued the vector operation while
disabled.
0A0
08 None of the online processors with an attached
Vector Facility met the task’s affinity Explanation: During initial program load (IPL), an
requirements. error occurred while the system was starting the master
scheduler. Register 15 contains a hexadecimal reason
0C The program cannot create the vector
code:
environment. The vector second level interrupt
handler (SLIH) detects the error. Code Explanation
10 The vector SLIH failed due to a system error. 01 The system detected a converter, interpreter, or
system error during master scheduler
14 The system encounters a vector environment
initialization.
that is not valid.
02 The system detected an allocation error, an
18 A machine check in the Vector Facility causes
OPEN catalog error, or a locked catalog error
the vector status for a task to be lost.
during master scheduler initialization.
1C The issuing task holds a local lock.
03 The system could not obtain a special region
20 The system encounters a secondary task for the master scheduler.
control block (STCB) that is not valid.
System action: The system does not start the master
24 No Vector Facility exists in the complex. scheduler. System initialization ends. The system writes
an SVC dump. The system may issue message
28 Resource Access Control Facility (RACF) has IEE479W.
indicated that the user is not authorized to use
the Vector Facility. Operator response: If the system issues message
IEE479W, see the operator response for message
2C The program issued the vector instruction and IEE479W. Otherwise, notify the system programmer.
had established enabled, unlocked task (EUT)
mode functional recovery routines (FRR). System programmer response: Examine the SVC
dump, looking at the master trace table for messages
System action: The system abnormally ends the which will pinpoint the problem with the JCL (for RC=01)
program that issued the vector instruction. The system or with allocation (for RC=02). If the master JCL data
may write an logrec data set error record. set (MSTJCLxx) was updated recently, check that the
Operator response: If the system programmer asks changes are correct. The messages associated with the
for an SVC dump, set the following SLIP trap: processing of MSTJCLxx are sent to the console if you
specify the L option (,L) on the MSTRJCL system
SLIP SET,COMP=09F,ACTION=SVCD,END
parameter. Respond to messages issued by the
Application Programmer Response: Do the converter, interpreter, or allocation.
following:
If the problem recurs and if the program is not in error,
v For reason code X'00', X'04', X'1C', or X'2C', ensure search problem reporting data bases for a fix for the
that the program issues vector instructions in the problem. If no fix exists, contact the IBM Support
proper mode. Center. Provide the dump.
v For reason code X'08', a program that uses a Vector
Source: Initiator/terminator
Facility should not specify affinity requirements.
System programmer response: Do the following:
1. If a logrec data set error record is not produced with
the abend, ask the operator to set a SLIP trap to
obtain an SVC dump.
Chapter 2. System Completion Codes 91
0A1 • 0A5
Application Programmer Response: Do the
0A1
following:
Explanation: An incorrect condition was detected by 1. Check for messages identifying the cause of the
the Graphics Access Method/System Product (GAM/SP) error. If these are GAM/SP messages, (that is, the
OPEN executor routine, IGG0193Y. The error occurred message number is of the form ‘GABnnn’), they are
in either GAM/SP or the operating system. described in IBM Graphics Access Method/System
System action: A message appears on the system Product: Messages and Codes.
console that identifies the cause of the error; and 2. Check the module identifiers and PTF levels for
GAM/SP produces a dump on the system dump data modules IGG019OE and IGG0193Y.
set. 3. Get a listing of the system dump.
Application Programmer Response: Do the 4. Contact your programming support personnel.
following:
Source: DFSMSdfp
1. Check for messages identifying the cause of the
error. If these are GAM/SP messages, (that is, the
message number is of the form ‘GABnnn’), they are 0A4
described in IBM Graphics Access Method/System Explanation: An error occurred either in the Graphics
Product: Messages and Codes. Access Method/System Product (GAM/SP) or in the
2. Get a listing of the system dump. operating system.
3. Contact your programming support personnel. This completion code is issued when:
Source: DFSMSdfp 1. A program check or abnormal end occurs in the
Graphics Access Method/System Product (GAM/SP)
attention handler module.
0A2
2. The GAM/SP attention handler module detects an
Explanation: An incorrect condition was detected by incorrect condition.
the Graphics Access Method/System Product (GAM/SP)
CLOSE executor routine, IGG0203Y. The error occurred System action: A message appears on the system
in either GAM/SP or the operating system. console, accompanied by a reason code identifying the
area of processing in which the error occurred. In
System action: A message appears on the system addition, GAM/SP writes a record to the logrec data set
console that identifies the cause of the error and data set and produces a dump on the system dump
GAM/SP produces a dump on the system dump data data set.
set.
Application Programmer Response: You should take
Application Programmer Response: Do the the following actions: Do the following:
following:
1. Check for messages identifying the cause of the
1. Check for messages identifying the cause of the error. If these are GAM/SP messages, (that is, the
error. If these are GAM/SP messages, (that is, the message number is of the form ‘GABnnn’), they are
message number is of the form ‘GABnnn’), they are described in IBM Graphics Access Method/System
described in IBM Graphics Access Method/System Product: Messages and Codes.
Product: Messages and Codes.
2. Get a listing of the system dump.
2. Get a listing of the system dump.
3. Contact your programming support personnel.
3. Contact your programming support personnel.
Source: DFSMSdfp
Source: DFSMSdfp
0A5
0A3
Explanation: A program check or abnormal end
Explanation: An error was detected in the Graphics occurred within the Graphics Access Method/System
Access Method/System Product (GAM/SP) attention Product (GAM/SP) attention handler module,
handler module, IGG019OE. The error may have IGG019OE. The recovery routine for IGG019OE
originated in the GAM/SP OPEN executor, IGG0193Y. It determined that the problem was caused by an
could also be caused by modules IGG019OE and application error.
IGG0193Y being at inconsistent maintenance levels.
System action: Message GAB333 appears on the
System action: A message appears on the system system console and diagnostic data is provided. The
console that describes the error. In addition, GAM/SP message and the diagnostic data are described in IBM
writes a record to the logrec data set data set and Graphics Access Method/System Product: Messages
produces a dump on the system dump data set. and Codes.
Application Programmer Response: Check for
92 z/OS V1R10.0 MVS System Codes
0A6 • 0A8
messages identifying the cause of the problem. Using 7001 The user’s RPL control block, or event control
the message and other diagnostic information, correct block (ECB) is incorrect.
the application program. IBM Graphics Access
7002 A VTAM request for storage failed.
Method/System Product: Messages and Codes contains
information on application recovery from this problem. 7003 The pointer to the request parameter list (RPL)
is not valid.
Source: DFSMSdfp
7004 An ACB OPEN failed due to an access method
control block (ACB) address that is not valid.
0A6
7005 Storage pointed to by RPLAREA is not valid.
Explanation: The Print Services Facility (PSF) ESTAE
routine detected an error in the Page Printer 7006 Storage pointed to by RPLAAREA is not valid.
Communications Component (PPCC) of PSF.
7007 The request parameter list (RPL) is not valid.
System action: Depending on the error condition, Unable to find ACB.
PSF restarts the functional subsystem application (FSA)
or terminates the FSA. PSF issues a message 7008 RPL6 pointed to by RPLAAREA is not valid.
indicating the action taken and may take a SVC dump. 7009 Node initialization block(s) (NIB) pointed to by
Operator response: Inform your system programmer the request parameter list (RPL) is not valid.
that this error occurred. 700A Model Terminal Support (MTS) data pointed to
Application Programmer Response: None. by node initialization block (NIB) is not valid.
System programmer response: Review the console 700B Restore parameter list pointed to by node
log for all PSF messages and, if any, the PSF abend initialization block (NIB) is not valid.
reason code. Refer to PSF for z/OS: Messages and 700C Application-supplied dial parameters storage
Codes formore information on the PSF messages, PSF pointed to by node initialization block (NIB) is
abend reason code, and to determine the appropriate not valid.
response for this error.
700D Bind area pointed to by node initialization block
Source: PSF for OS/390 (NIB) is not valid.
FC01 Network management interface abend.
0A7
FC02 VTAM agent user’s read queue PAB had a
Explanation: During VTAM® HALT QUICK, VTAM storage failure.
HALT, VTAM HALT CANCEL, or VTAM abnormal
termination processing, VTAM found that no storage FF01 A session awareness (SAW) data buffer that is
was available to schedule a TPEND exit for an access not valid was passed to VTAM’s data space
method control block (ACB) opened by a user’s services release routine.
application program or VTAM subtask. or the ACB System action: The task abnormally ends. The
storage was freed. system may issue a dump.
This abend code is also issued during VTAM HALT Application Programmer Response: This is probably
CANCEL or VTAM abnormal termination processing if a a user error. Do one of the following:
TPEND exit for an ACB does not exist, the ACB was not
v For reason codes 2101, 7001, 7003, 7005, 7006,
valid, or the ACB storage was freed.
7007, 7008, 7009, 700A, 700B, and 700C, verify that
System action: The caller’s task abnormally ends. the RPL and ECB pointers are correct, and execute
the job step again.
Source: Teleprocessing
v For reason code 7002, verify that the operator
entered the buffer pool or CSA start options as
0A8 specified in the start procedures.
Explanation: Virtual telecommunications access Increase storage as required. For insufficient storage
method (VTAM) detected an error while processing a errors, you might want to redefine your buffer pool or
user’s application program. The two low-order bytes of CSA limits. If the start option cannot be modified
register 15 contain a hexadecimal reason code that using the MODIFY VTAMOPTS command, you must
explains the error. modify the VTAM start options file (ATCSTRxx) and
restart VTAM to use the new start option.
Code Explanation
– Use the Estimating Storage for VTAM diskette to
2101 A VTAM validity check of the user’s request determine the storage requirements for VTAM.
parameter list (RPL) failed because the RPL
does not have the same protection key as the
application program’s task control block (TCB).
Chapter 2. System Completion Codes 93
0A9
– Refer to the z/OS Communications Server: SNA program listing for the job, and all printed output and
Resource Definition Reference for a description of output data sets related to the problem.
VTAM start options.
Source: Teleprocessing
– Refer to the z/OS Communications Server: SNA
Operation for information about the DISPLAY
BFRUSE command, the DISPLAY STORUSE 0A9
command, and the MODIFY VTAMOPTS Explanation: One of the following occurred:
command.
v If this abend is accompanied by a zero value in
– Refer to the z/OS Communications Server: SNA register 15, a VTAM HALT command has been
Network Implementation Guide for an explanation successfully completed.
and description of buffer pools, and for general
information about buffer pool specification and v If register 15 is not zero, an error has occurred during
allocation. the execution of a VTAM module. The contents of the
2 low-order bytes of register 15 indicate the cause of
– See z/OS Communications Server: SNA Diagnosis the error:
Vol 1, Techniques and Procedures for information
about analyzing dumps and for information about Code Explanation
analyzing storage using the VIT analysis tool if
0000 A VTAM HALT CANCEL has been
external trace is active.
successfully completed.
v For reason code 7004, verify that the ACB pointer is
valid and check the storage to be sure it resides in 10F1 The ABEND was issued by VTAM’s retry
the application’s storage protection key. functional recovery routine (FRR) to pass
the original abend to the next recovery
v For reason code 700D, check the application
routine (if any) associated with the task
program.
control block (TCB). See the original abend,
v For reason code FC01, save the dump for problem which was recorded in SYS1.LOGREC and
determination. appears just prior to the supervisor call
v For reason code FF01: (SVC) dump that was generated and
– If you have access to IBMLink™, search for known indicated by reason code 10F1.
problems in this area. If no applicable matches are 2101 The request parameter list (RPL) is not in
found, report the problem to IBM by using the the correct storage key.
electronic technical report (ETR) option on
IBMLink. 6901 Error in CP-CP sessions processing. Missing
element on list pointed to by
– If you do not have access to IBMLink, report the
AND_BOTH_CP_STATUS_STORAGE_PTR.
problem to the IBM software support center.
6902 Error in CP-CP sessions processing. Missing
System programmer response: Do the following:
element on list pointed to by
v See the reason code in register 15. Register 15 and AND_CW_CP_STATUS_STORAGE_PTR.
its contents can be found in the SDWA or by issuing
the IPCS VERBEXIT LOGDATA subcommand. The 6903 Error in CP-CP sessions processing. Missing
generalized trace facility (GTF) trace record, SVC element on list pointed to by
trace (comprehensive), also displays the contents of AND_CL_CP_STATUS_STORAGE_PTR.
register 15. 7002 Storage was not available to drive a user
v If MSGLEVEL=(1,1) was not specified in the JOB exit.
statement, specify it and rerun the job.
7005 VTAM was unable to restore its registers
v Make sure that the failing job step includes the from the RPH after a user exit routine
SYSABEND DD statement. returned to VTAM.
v Collect the following for the failing job:
7006 CPPROC was unable to obtain adequate
– Console log from the primary or remote console.
storage from the vary work area (VWA).
– Job stream associated with the job.
– All associated output. 7007 TPEXIT code was entered while VTAM was
– Program listing for the job. holding a lock.
– The dump, if one is issued.
– Linkage editor or loader map. 7008 A CPWAIT was attempted with an event ID
length greater than EIDMAX.
If the error recurs and the program is not in error, look 7009 A message module needs more vary work
at the messages in the job log for more information. area (VWA) storage within the component
Search problem reporting data bases for a fix for the recovery area (CRA) than is currently
problem. If no fix exists, contact the IBM Support available.
Center. Provide the JCL, the linkage editor output, the
94 z/OS V1R10.0 MVS System Codes
0A9
700F Encountered a session awareness block FF04 A request, response, or vector was not
(SAB) that was not valid. defined to the RU information table.
7010 A GETRDTE or RDTFIND for a resource FF05 The main entry for the extended router was
failed because the resource definition table invoked but processing was already
entry (RDTE) chain has been corrupted. occurring within a CALLSSCP environment.
7012 A lock’s count shows no user is holding the FF06 No sense code was set, but one should
lock, but the lock is held. have been.
7013 Lock hierarchy violation. FF07 The CPCBURC field contained no format,
but the response has a format.
7014 TSLINK found the component recovery area
(CRA) too small to hold all of the data. FF08 The limit of topology elements
(SWBVDCVD) has been exceeded. D3/D4
7015 A transmission subsystem control block
vectors for elements exceeding limit were
(TSCB) was encountered that is not valid.
not built.
7071 A RELSTORE was issued for a previously
FF09 The VWA area in use is too small to satisfy
freed buffer.
this request.
7072 A VTFREE was issued for a previously freed
FF10 A request was made to queue a response to
area.
a process anchor block (PAB).
7074 A VTFREE was issued for a buffer that is
FF11 A suspend code that is not valid was passed
not valid.
to suspend.
7075 A VTFREE was issued for a previously freed
FF12 A SENDER invocation that is not valid was
storage area.
made.
7076 C/370™ code ran out of ISA storage for
FF13 An unexpected value was received. The
autodata.
value may be valid in another context.
7077 Storage management header has been
FF14 An unexpected finite state machine (FSM)
overlaid.
state was encountered.
7078 The last word in the buffer being
FF15 An unexpected field value was encountered
RELSTOREd is not BFPPCBA (fence
for an enumerated type.
corrupted).
FF16 An unexpected control block was received
7079 Header in REQSTORE buffer being
as input.
allocated is not valid (no match on fence
word). FF17 A session information block (SIB) or SIB
address that is not valid was passed to
707A A FREESTOR was issued for a previously
FREESIB.
freed storage area.
FF18 The SENDER buffer area is not large
CD01 CDRM error detected.
enough.
CF01 An error was found and corrected in a
FF19 The DETERMINER routine returned results
CDRM minor node during CDRM major
that are not valid.
node deactivation.
FF20 The BUILD routine returned results that are
FA01 DS process error.
not valid.
FA02 The DS disk I/O subtask has abended due
FF22 SRTDEL failed.
to insufficient storage. The checkpoint has
been disabled. FF25 Secondary Access Point (SAP) table
overflow.
FA09 Initialization error.
FF26 HPRCTL was issued with the TOKEN option
FE02 A pool has been defined by the POOLDEF
and the value passed was not valid.
macro with an unacceptable length or the
lengths in a variable-length pool were not FF99 Indicates that a FFST™ probe was tripped.
defined in ascending order. Console messages with prefix EPW will be
issued by FFST to provide information about
FF02 A FREEBLK macro returned a nonzero
the probe trip. See z/OS Communications
return code.
Server: SNA Diagnosis Vol 1, Techniques
FF03 A utility module detected a function code and Procedures for a description of FFST
that is not valid. probes.
Chapter 2. System Completion Codes 95
0AA • 0AB
System action: The task that initiated the VTAM v Save the console log from the primary console. For
request abnormally ends. systems with remote consoles, save the remote
console log. In systems with multiple-console support
Application Programmer Response: Do the
(MCS), save a copy of the hard copy log.
following:
v Make sure that the failing job step includes the
v If MSGLEVEL=(1,1) was not specified in the JOB
SYSABEND DD statement.
statement, specify it and rerun the job.
v Save all the associated output.
v Save the console log from the primary console. For
systems with remote consoles, save the remote v Save the dump.
console log. For systems with multiple-console v Have the linkage editor/loader map available.
support (MCS), save a copy of the hard copy log.
System programmer response: If the error recurs
v Save the job stream associated with the job. and an installation-provided program is not in error, look
v Make sure that the failing job step includes the: at the messages in the job log for more information.
1. SYSABEND DD statement Search problem reporting data bases for a fix for the
2. SYSUDUMP DD statement. problem. If no fix exists, contact the IBM Support
v Save all the associated output. Center. Provide the linkage editor and all printed output
and output data sets related to the problem.
v Save the dump.
v Execute the EREP service aid to dump the LOGREC Source: Teleprocessing
file, and save the resulting output. For MSS, execute
the following program to dump the LOGREC file: 0AB
1. Service aid IFCISDA0
2. Program ISDASDAO with the DETAIL(ALL) Explanation: The error occurred while TSO/VTAM
parameter. was in operation and a VTIOC module was processing
a VTAM macro. See the VTAM Messages and Codes
v If register 15 is 0015, take the following actions to try
manual or the VTAM Diagnosis Guide for additional
to determine the cause of the TSCB integrity loss:
information.
1. Save the dump.
2. If VTAM internal trace is running MODE=EXT, This error is usually due to a storage problem with the
save this trace. LPBUF or CRPL buffers.
The two low-order bytes of register 15 contain a
Note: The default trace internal options may not
hexadecimal reason code that explains the error:
be enough to resolve this problem. All
options but LOCK, with a trace table of at Code Explanation
least SIZE=200, may be required.
0101 The terminal-input manager for LU1 (for
System programmer response: If the error recurs example, IBM 3767 and IBM 3770 terminals)
and an installation-provided program is not in error, look encountered an unrecoverable error while
at the messages in the job log for more information. executing a VTAM macro instruction that uses
Search problem reporting data bases for a fix for the a request parameter list (RPL).
problem. If no fix exists, contact the IBM Support
Center. Provide the SYSOUT output for the job, the 0102 The terminal-output manager for LU1 (for
logrec data set error record, and all printed output and example, IBM 3767 and IBM 3770 terminals)
output data sets related to the problem. encountered an unrecoverable error while
executing a VTAM macro instruction that uses
Source: Teleprocessing an RPL.
0103 The terminal-input manager for LU0 and LU2
0AA (for example, IBM 3270 SNA terminals)
encountered an unrecoverable error while
Explanation: An abend condition occurred during
executing a VTAM macro instruction that uses
processing of virtual telecommunications access method
an RPL.
(VTAM). VTAM functional recovery routines (FRRs)
were unable to associate the failure with any particular 0104 The terminal-output manager for LU0 and LU2
task control block (TCB) in the address space. (for example, IBM 3270 SNA terminals)
encountered an unrecoverable error while
System action: The system abnormally ends all the
executing a VTAM macro that uses an RPL.
tasks in the address space.
0105 The VTIOC LOSTERM exit routine
Application Programmer Response:
encountered an error during execution of a
v If MSGLEVEL=(1,1) was not specified in the JOB SNA BIND or UNBIND command that used an
statement, specify it and rerun the job. RPL.
0201 An application ID problem was encountered
96 z/OS V1R10.0 MVS System Codes
0AC • 0AD
during execution of a VTAM OPEN macro. The 14 The TCAS main task was unable to attach the
error occurred during initialization of a user-interface subtask.
TSO/VTAM user-address space.
18 The TCAS main task was unable to attach the
0202 An error occurred during execution of a VTAM console-communication subtask.
OPEN macro. The ERROR field of the ACB
1C TCAS was unable to obtain storage for the
indicates the problem.
TCAS table (TCAST) in the common service
0203 An error occurred during execution of a VTAM area (CSA).
CLOSE macro. The code in the ERROR field
20 The TCAS main task abnormally terminated
of the ACB is X'42', indicating that the ACB has
and was unable to recover.
been closed, but a VTAM error has prevented
the successful disconnection of one or more 30 The VTAM interface subtask abnormally
TSO terminals. terminated and was unable to recover.
System action: The terminal session in which the 34 The user-interface subtask abnormally
error occurred ends. terminated and was unable to recover.
Application Programmer Response: Do the 38 The console-communication subtask
following: abnormally terminated and was unable to
v Save the console log from the primary console. For recover.
systems with remote consoles, save the remote System action: The system abnormally ends TCAS.
console log. For systems with multiple-console
support (MCS), save a copy of the hard copy log. Operator response: Reply ‘DUMP’ to the TCAS
v Save all the associated output. abnormal end message IKT012D to obtain a dump.
v Save the dump. Application Programmer Response: Do the
v Execute the EREP service aid to dump the LOGREC following:
file, and save the resulting output. For MSS, execute v Save the console log from the primary console. For
the following program to dump the LOGREC file: systems with remote consoles, save the remote
1. Service aid IFCISDA0 console log. For systems with multiple-console
2. Program ISDASDAO with the DETAIL(ALL) support (MCS), save a copy of the hard copy log.
parameter. v Save the system output (SYSOUT) associated with
v Have the linkage editor/loader map available. the job.
System programmer response: If the error recurs v Save all the associated output.
and an installation-provided program is not in error, look v Save the dump.
at the messages in the job log for more information. v Print the associated SVC dump data set, using IPCS.
Search problem reporting data bases for a fix for the See z/OS Communications Server: SNA Diagnosis
problem. If no fix exists, contact the IBM Support Vol 1, Techniques and Procedures for information
Center. Provide the logrec data set error record, the about IPCS.
linkage editor output. and all printed output and output
data sets related to the problem. Source: Teleprocessing
Source: Teleprocessing
0AD
0AC Explanation: An error occurred while Time Sharing
Option/ Virtual Telecommunications Access Method
Explanation: The terminal control address space (TSO/VTAM) time sharing was in operation. VTAM
(TCAS) was unable to continue its normal processing terminal I/O coordinator’s (VTIOC) queue manager was
due to an error. The two low-order bytes of register 15 executing a GETCELL or FREECELL macro.
and TCAS work area (TWAR) field TWARSON both
contain the hexadecimal reason code that indicates the The two low-order bytes (hexadecimal) of register 15
cause of the error: indicate the cause of the error:
Code Explanation Contents Explanation
00 A STOP command was entered. 0108 The cell address supplied to the
FREECELL macro instruction was
04 A START command that is not valid was incorrect.
entered.
010C No cell pool existed for the
10 The TCAS main task was unable to attach the FREECELL request.
VTAM interface subtask.
Chapter 2. System Completion Codes 97
0AE • 0AF
0110 An incorrect cell pool ID was specified Facility files were available for you to receive.
for the FREECELL request. The JES subsystem request was not
successful. Reason code 0025 is associated
020C No cell pool existed for the GETCELL
with message INMR037I.
request.
002A The TRANSMIT command attempted to
0210 An incorrect cell pool ID was specified
allocate the SYSPRINT message file for
for the GETCELL request.
IEBCOPY using SVC 99, and the allocation
System action: The queue manager ends abnormally, failed. The SYSPRINT message file is usually
and the terminal session in which the error occurred allocated to either the terminal or to a SYSOUT
ends. The system writes a logrec data set error record class. You can specify where you want it to be
and an ABEND dump. allocated in either in CSECT INMXPARM or on
the TRANSEC keyword of parmlib member
Application Programmer Response: IKJTSO00. Reason code 002A is associated
v Save the console log from the primary console. For with messages INMX040I and INMX042I.
systems with remote consoles, save the remote
console log. In systems with multiple-console support 0043 The TRANSMIT command was issued with the
(MCS), save a copy of the hard copy log. DATASET or DSNAME keyword and the
OBTAIN SVC was issued to get information
v Save the program listing associated with the job. about the data set. The OBTAIN SVC set a
v Execute the EREP service aid to dump the LOGREC return code other than 0 (successful
file, and save the resulting output. For MSS, execute termination), 8 (data set not on volume), or 12
the following program to dump the LOGREC file: (VTOC I/O error). Reason code 0043 is
1. Service aid IFCISDA0 associated with message INMX067I.
2. Program ISDASDAO with the DETAIL(ALL)
parameter. 0053 The TRANSMIT command attempted to OPEN
a data set previously written by the IEBCOPY
v Have the linkage editor/loader map available. utility or the AMS REPRO command. The
v Print the associated SVC dump data set, using IPCS. OPEN failed. The data set is a temporary data
See z/OS Communications Server: SNA Diagnosis set the TRANSMIT command allocates to
Vol 1, Techniques and Procedures for information contain intermediate data. Normally, the
about IPCS. TRANSMIT command reads, transmits, and
deletes the temporary data set. Reason code
Source: Time Sharing Option Extensions (TSO/E)
0053 is associated with message INMX083I.
007F The RECEIVE command attempted to allocate
0AE
a spool file and the allocation failed. The
Explanation: The system cannot purge a completed RECEIVE command obtained the name of the
I/O request. spool file from JES. Reason code X'007F' is
associated with message INMR127I.
System action: The system abnormally ends all tasks
in the address space where the system was waiting to 0084 The RECEIVE command was issued with the
purge the I/O request. INDATASET or INDSNAME keyword.
System programmer response: Search problem The data set specified with the keyword failed
reporting data bases for a fix for the problem. If no fix to OPEN. The data set was allocated
exists, contact the IBM Support Center. successfully. Reason code 0084 is associated
with message INMR132I.
Source: Input/output supervisor (IOS)
0085 The RECEIVE command attempted to OPEN a
file for incoming network files from the JES
0AF
spool, but the OPEN failed. The process
Explanation: The Time Sharing Option Extensions sysout subsystem interface successfully
(TSO/E) interactive data transmission facility detected a selected a name for the spool file and the
system error during the processing of a TRANSMIT or dynamic allocation SVC successfully allocated
RECEIVE command. Register 15 contains a reason the spool file. Reason code 0085 is associated
code: with message INMR133I.
Code Explanation 0086 The RECEIVE command attempted to
deallocate a data set using SVC 99, and the
0025 The RECEIVE command encountered an error unallocation failed. The data set was a JES
while invoking the Job Entry Subsystem (JES) input file or was specified by an INDATASET or
interface. INDSNAME keyword. Reason code 0086 is
The RECEIVE command was issued to associated with message INMR134I.
determine if any Interactive Data Transmission
98 z/OS V1R10.0 MVS System Codes
0B0
0089 The RECEIVE command encountered an error an incorrect count field. For move mode, an
while attempting to end the external writer incorrect count is 0 for a READ, WRITE, or
interface with JES. After all files have been ASSIGN function, and 00 for WRITE/ASSIGN.
processed or after a unrecoverable error, the
18 The routine that called SWA manager by
RECEIVE command invokes the process
issuing the QMNGRIO macro specified both or
sysout subsystem interface, specifying that this
neither of the READ or WRITE options.
is the final call to the subsystem interface. The
subsystem returned a nonzero return code 1C The routine that called SWA manager tried to
indicating an error. Reason code 0089 is write into a SWA block for the first time and
associated with message INMR137I. has either passed a nonexistent ID, or has
failed to pass an ID at all and the block does
009C The TRANSMIT or RECEIVE command
not have an embedded ID.
processor received an unknown return code
from the module IKJSMS1. The reason code 20 The system tried to write a block using an
009C is associated with message INMC156I. incorrect pointer to the block.
00CC The TRANSMIT command processor 24 An error occurred while the system was
encountered an error while opening the JES translating an SVA for an SWA block that is
output file. Reason code 00CC is associated above 16 megabytes.
with message INMX204I.
28 The routine that called the SWA manager
00D2 The TRANSMIT command processor specified zero on the EPA parameter of the
encountered an error while opening the output SWAREQ macro. The EPA parameter must be
data set. Reason code 00D2 is associated with the address of a fullword pointer to the EPA.
message INMX210I. Check the value specified on the EPA
parameter of the SWAREQ macro to ensure
System action: The system issues one of the
that it is the address of a pointer to the EPA
following messages: INMC156I, INMR037I, INMX067I,
and not the EPA itself.
INMX083I, INMR127I, INMR132I, INMR133I, INMR134I,
INMR137I, INMX040I, INMX042I, INMX204I, INMX210I. 34 An attempt has been made to allocate or
delete an SWA block in an unauthorized
The system issues an SVC dump.
environment.
System programmer response: If the problem recurs
3C While attempting to process an assign request,
and if the program is not in error, search problem
the SWA manager encountered a zero value
reporting data bases for a fix for the problem. If no fix
as the pointer to the QMPA. The most likely
exists, contact the IBM Support Center. Provide the
cause of this error condition is that a task
SVC dump and hardcopy of the TSO session if
running under the master subsystem
possible.
(SUB=MSTR) attempted a dynamic allocation
Source: Time Sharing Option Extensions (TSO/E) in its own address space, but that address
space is not yet totally established.
0B0 Some specific causes are as follows:
Explanation: The scheduler work area (SWA) 1. Attempting to run a started JOB as
manager detected an uncorrectable error. Register 15 SUB=MSTR or under a WLM initiator
contains a reason code explaining the error: (INIT), when the JOB to be started has an
instream procedure (proc). The converter
Code Explanation issues a dynamic allocation to create a
04 The routine that called SWA manager temporary PDS to hold the procedure being
requested an incorrect function. read in.
2. Attempting to run a started task (STC) as
08 The routine that called SWA manager passed SUB=MSTR, but not all of the data sets
an incorrect SVA (SWA virtual address). The needed for that started task are cataloged
SVA does not point to the beginning of a SWA in the MASTER CATALOG. Either a
prefix or the SWA prefix was destroyed. JOBCAT or STEPCAT is included in the
0C A SWA manager routine tried to read a record JCL, or simply one of the data sets in the
not yet written into SWA. JCL is cataloged in a USER catalog
(usercat). Allocation issues a dynamic
10 The system tried to read or write a block that is allocation for the required catalog.
not 176 bytes or the system tried to assign a
3. The device type in the catalog for one of
block with a specified length of 0 or a negative
the data sets that is started as SUB=MSTR
number.
is incorrect (for example, the information
14 The routine that called SWA manager specified
Chapter 2. System Completion Codes 99
0B1
specifies that the data set is on a 3380 x Irrelevant information.
device, but the data set is really on a 3390
rr A hexadecimal reason code indicating the
device.).
reason for the failure.
Corrective actions are: www The wait state code.
1. You cannot run started jobs with PROC
statements as SUB=MSTR. The reason code (rr) is one of the following:
Do one of the following actions: 01 The required data set was not found.
v Remove the PROC statement, or 02 The IODF occupies more than one extent.
v Remove the JOB statement and run it as
a started task 03 A required device is not defined.
v Run it as SUB=JES2 (or JES3) 04 MSCH instruction failed for a required device.
2. Ensure that all data sets required by jobs 05 The IODF is not valid for an IPL.
or tasks running SUB=MSTR are cataloged
in the master catalog or are directly pointed 06 The configuration ID specified in the LOADxx
to by the specification of UNIT and member does not match any I/O configuration
VOL=SER parameters on the DD contained in the IODF.
statement. 07 The LOADxx member contains blanks as the
3. Ensure that the device types for all required configuration ID. If there is only one I/O
catalogued data sets and any UNIT configuration defined in the IODF, then the
parameters on DD statements are correct. system ignores the blanks and uses the I/O
configuration. In this case, the IODF contains
System action: The task ends and the system writes
multiple definitions and the system requires
a dump.
that you specify a valid configuration ID in the
Operator response: Notify the system programmer. LOADxx member.
Application Programmer Response: If the program 08 The IODF suffix is not valid.
that ended was a started task, and the code in register
09 The IODF data set name high level qualifier is
15 is X‘08’ or X‘0C’, check the JCL for this task. For all
not valid.
started tasks, the JCL must either:
v refer to existing data sets that are cataloged in the 0A The IODF is not valid for an IPL. It must be a
master catalog; or VSAM data set.
v include unit and volume information on the DD
Note: This wait state can also occur because of an
statements for existing data sets.
invalid IODF statement. In addition to incorrect
Modify the JCL to meet one of these requirements, and data entries this wait state can also be caused
resubmit the job. by incorrect keyword filtering using the
HWNAME, LPAR NAME, and VMUSERID
System programmer response: If the problem recurs
keywords.
and if the program is not in error, search problem
reporting data bases for a fix for the problem. If no fix System action: The system enters nonrestartable wait
exists, contact the IBM Support Center. It is the state X'0B1'. The system issues the following messages
responsibility of the caller to SWA manager to take the with the following wait state reason codes:
dump, and if none was taken, then a SLIP would need
Code Accompanying Message
to be set up to capture the failure. Provide the dump to
the IBM Support Center. 01 IEA513W.
Source: Scheduler work area (SWA) manager 02 IEA514W.
03 IEA515W, to display the device number.
0B1
04 IEA516W, to display the device number.
Explanation: System initialization cannot continue
because of a problem in the LOADxx member, the I/O 05 IEA517W.
definition file (IODF) data set, or a device. 06 IEA518W.
The right-most four bytes of the program status word 07 None.
(PSW) have the following format:
08 IEA512W.
xrr00www
09 None.
where:
Operator response: Notify the system programmer.
100 z/OS V1R10.0 MVS System Codes
0B2 • 0B4
System programmer response: Depending on the
0B2
hexadecimal reason code, one of the following:
Explanation: The system detected an incorrect
Code Action
statement in the MSTRJCL data set. The system could
01 Verify that the correct device number was not convert the MSTRJCL nor start the master
specified on the LOAD parameter. Enter the scheduler.
correct IODF data set name in the LOADxx
System action: The system does not start the master
member.
scheduler. The system abnormally ends master
02 Ensure that the IODF data set is allocated as a scheduler initialization.
single extent data set.
System programmer response: If the MSTRJCL data
03 Verify that the device specified on the LOAD set in the LINKLIB was updated manually, check it for a
parameter is defined to the channel subsystem. statement without a // in columns 1 and 2. Ensure that
(There is no device with the proper subchannel the MSTRJCL is delimited by a /* or a // (null) card. If
identifier.) Verify that the correct device number the problem persists, search problem reporting data
was specified on the LOAD parameter. Verify bases for a fix for the problem. If no fix exists, contact
that the hardware configuration matches the the IBM Support Center.
definitions in the IODF.
Source: Initiator/terminator
04 Move any of the following data sets (that are
on the device specified on the LOAD
0B3
parameter) to a different device:
v IODF Explanation: A caller of the master subsystem incore
v SYS1.PARMLIB access method attempted an incorrect or not
v SYSn.IPLPARM serviceable access request.
05 Change the LOADxx member to specify System action: The system abnormally ends the task
another IODF. Be sure to specify the name of a using the access method.
production-IODF (instead of work-IODF).
System programmer response: Search problem
06 Change the LOADxx member to specify the reporting data bases for a fix for the problem. If no fix
correct IODF or to specify the correct operating exists, contact the IBM Support Center.
system configuration ID.
Source: Initiator/terminator
07 Specify the correct operating system
configuration identifier.
0B4
08 Verify that the IODF data set name suffix
Explanation: The master subsystem could not make
specified in the LOADxx member is a valid
use of the SYS1.PROCLIB data set defined by the
hexadecimal number X'00' through X'FF'. Enter
IEFPDSI statement in the MSTRJCL. This occurred for
the correct IODF data set name in the LOADxx
one of the following reasons:
member.
v The master subsystem was unable to OPEN the
In each case, ask the operator to reIPL the system. PROCLIB data set.
v The blocksize of the opened SYS1.PROCLIB data
Problem determination: If the problem persists,
set was not a multiple of 80.
search problem reporting data bases for a fix for the
problem. Provide the following search argument: System action: The system cannot function without
v WS/D0B1: Wait state code an open SYS1.PROCLIB data control block (DCB). The
v PRCS/00000rrr: Reason code system does not start the requested subsystem.
v MS/IEAnnnW: Message identifier
System programmer response: Check for a valid
If no fix exists, ask the operator to obtain the data set name on the IEFPDSI card in the MSTRJCL
stand-alone dump. Contact the IBM Support Center. data set. Check for a valid blocksize either on the
Provide the stand-alone dump, the accompanying IEFPDSI card or in the data set’s format data set control
message, and the reason code. block (DSCB) in the VTOC. If the problem persists,
search problem reporting data bases for a fix for the
Source: Input/output supervisor (IOS)
problem. If no fix exists, contact the IBM Support
Center.
Source: Initiator/terminator
Chapter 2. System Completion Codes 101
0B5 • 0B7
check and an error recovery action (ERA)
0B5
code. The mount request was for a scratch
Explanation: The master subsystem was unable to volume, but the ERA code is appropriate only
attach the converter. for a specific volume.
System action: The system does not start the 2C During the processing of a library mount or
requested subsystem. demount request, an order has been sent to
the library. The library has responded with a
System programmer response: Search problem
unit check and an error recovery action (ERA)
reporting data bases for a fix for the problem. If no fix
code. The ERA code is an unexpected and
exists, contact the IBM Support Center.
inappropriate response to the order.
Source: Initiator/terminator
30 During the processing of a library mount
request, the library has indicated that the
0B6 mount operation completed successfully, but
the external volume serial number of the
Explanation: Library automation communication mounted volume does not match the requested
services (LACS) has detected an error condition. The volume serial number.
specific error is identified by a reason code in register
15. 34 The return code from the Library Control
System (LCS) CBRXLIB service indicates that
Code Explanation a parameter error has been detected.
04 The return code from the Asynchronous System action: The system abnormally ends the task.
Operations Manager (AOM) LIBSERV service An SVC dump is requested and the error is recorded in
indicates that a parameter error has been SYS1.LOGREC. The system resumes processing of the
detected. task. LACS sets the permanent error return code and
08 The return code and reason code from the an appropriate reason code, and returns control to the
AOM AOMQUE service indicate that an invalid caller. The job for which the LACS service was
request was made. requested fails.
0C The return code from the Library Control Operator response: Resubmit the failing job. If the
System (LCS) CBRXVOL service indicates that failure persists, notify the system programmer.
a parameter error has been detected. System programmer response: For reason codes
10 The return code from the LCS CBRXLCS 04, 08, 0C, 10, 14, and 18, the problem is probably
service indicates that a parameter error has caused by incorrect LACS software. For reason codes
been detected. 1C and 20, the problem is probably caused by incorrect
software in the caller of LACS or in AOM. For reason
14 A non-zero return code has been received from codes 24, 28, 2C, and 30, the problem is probably
the OAM message construction service. caused by incorrect library micro-code. Save the
18 The return code and reason code from the console log and the dump data set, print the contents of
IEEMIFSV message buffer manager service SYS1.LOGREC, then contact the IBM Support Center.
indicate that a parameter error has been
detected. 0B7
1C The return code and reason code from the Explanation: A CONFIG or VARY command
AOM LIBSERV service indicate that no requested addition or removal of hardware units from a
libraries have been defined to AOM. configuration. While processing the command, the
20 The return code and reason code from the system detected an error. A hexadecimal reason code in
AOM LIBSERV service indicate that the library register 15 explains the error:
configuration has not yet been set to AOM. Code Explanation
24 During the processing of a library mount 00000301 The system detected an incorrect
request, a mount order has been sent to the parameter.
library. The library has responded with a unit
check and an error recovery action (ERA) 00000302 The caller was not authorized to use
code. The mount request was for a specific the vary path interface.
volume, but the ERA code is appropriate only 00000303 For the processing, the system
for a scratch volume. requested virtual storage but failed to
28 During the processing of a library mount obtain it.
request, a mount order has been sent to the 00000304 The vary path interface detected a
library. The library has responded with a unit
102 z/OS V1R10.0 MVS System Codes
0B7
failing return code from the 00000702 The system received an unexpected
reconfiguration message service. return code when requesting that
storage be logically varied online.
00000401 The service processor was running a
CONFIG STOR ONLINE command. 00000703 The system received return code 8
The service processor varied the when requesting that storage be
requested storage physically online, logically varied offline. This code
but the system was unable to vary the indicates that the requested storage
storage logically online. The service range contains permanently resident
processor then tried unsuccessfully to storage.
vary the storage physically offline.
00000704 The system received an unexpected
00000402 The system returned an unexpected return code when requesting that
return code. storage be logically varied offline.
00000403 The system tried to vary storage 00000705 The system failed to establish a
online or offline, but received an recovery environment.
unexpected response code from the
00000706 The system received an unexpected
service processor.
response code for a Store Extended
00000404 Processing for vary path Storage Usability Map command from
reconfiguration received an the service processor.
unexpected response code from the
00000707 The system received an unexpected
service processor.
return code for a Store Extended
00000405 The system tried to obtain storage Storage Usability Map command from
element information, but received an a service processor routine.
unexpected response code from the
xxxx0B01 Processing for the DISPLAY MATRIX
service processor.
command received a nonzero return
00000406 The system failed to establish a code.
recovery environment.
xxxx0B02 Processing for the DISPLAY MATRIX
00000501 The system received an unexpected command tried to issue a message,
return code from the service but could not find the associated
processor call SVC routine. message text.
00000502 The system tried to vary a storage xxxx0B04 The system received a nonzero return
element online or offline, but received code from the ESTAE macro. xxxx is
an unexpected response code from the return code.
the service processor.
xxxx0C01 A command identified a processor on
00000503 The system tried to obtain storage which it is to run. The processor
element information, but received an identifier is not in the system table of
unexpected response code from the identifiers.
service processor.
xxxx0C02 Reconfiguration message processing
00000504 The system tried to copy and reassign returned a nonzero return code to
storage, but received an unexpected reconfiguration.
response code from the service
xxxx0D01 The system could not establish a
processor.
recovery environment.
00000505 The system failed to establish a
xxxx0D02 The system tried to call
recovery environment.
reconfiguration message processing,
00000601 The system returned an unexpected but an error occurred.
return code.
00000E01 Reconfiguration message processing
00000602 The system failed to establish a received an incorrect address for the
recovery environment. message buffer.
00000603 The system received an unexpected 00041001 Processing for the VARY PATH
return code for reconfiguration command received an unidentified or
message processing. failing return code from reconfiguration
message processing. The message
00000701 The system received an unexpected
text was too long.
return code when requesting storage
status. 00081001 Processing for the VARY PATH
Chapter 2. System Completion Codes 103
0B7
command received an unidentified or reconfiguration received a nonzero
failing return code from reconfiguration return code indicating one of the
message processing. The return code following errors:
indicates that reconfiguration message v The system was unable to obtain
processing was to issue a WTOR enough storage to process the
macro and await a reply, but no online request.
replies exist in the static message
v The system encountered an
area.
unrecoverable program error.
000C1001 Processing for the VARY PATH
00001504 The operator replied CANCEL to
command received an unidentified or
message IEE717D, then one of the
failing return code from reconfiguration
following occurred:
message processing. The number of
message inserts was incorrect. v The system encountered a
programming error while processing
00101001 Processing for the VARY PATH a request to bring a path online.
command received an unidentified or
v Processing for vary path
failing return code from reconfiguration
reconfiguration encountered a
message processing. The return code
programming error. The pointer to
indicates that the system could not
the current vary request block is 0.
establish a recovery environment.
00001505 Processing for vary path
00141001 Processing for the VARY PATH
reconfiguration received an
command received an unidentified or
unidentified or failing return code.
failing return code from reconfiguration
message processing. The return code xxxx1601 Reconfiguration requested virtual
indicates that the message buffer area storage. The request failed.
could not be obtained.
xxxx The GETMAIN return code.
00181001 Processing for the VARY PATH
command received an unidentified or xxxx1602 Processing to force a channel path
failing return code from reconfiguration offline encountered an error.
message processing. The return code xxxx The last return code
indicates that the message buffer encountered.
identifier was incorrect.
xxxx1603 A service processor failure occurred.
001C1001 Processing for the VARY PATH
command received an unidentified or xxxx The last service processor
failing return code from reconfiguration call return code.
message processing. The return code 00001604 A service processor command is
indicates that an abend occurred. incorrect.
xxxx1201 Processing for channel path xxxx1605 Processing to force a channel path
reconfiguration received a nonzero offline received an unidentified service
return code. processor response code.
xxxx1202 Processing for channel path xxxx The service processor
reconfiguration received a nonzero response code.
return code during vary processing.
xxxx1606 The service processor took more than
xxxx1204 Processing for channel path 45 seconds to process a request.
reconfiguration detected an incorrect
post code during vary processing. xxxx The last service processor
call return code.
00001501 Processing for vary path
reconfiguration received an xxxx1701 Reconfiguration requested virtual
unexpected return code. storage. The request failed.
00001502 Processing for vary path xxxx The GETMAIN return code.
reconfiguration received an xxxx1702 A service processor failure occurred.
unexpected return code. The system
was processing a request to bring xxxx The service processor
online a Teleprocessing (TP) device response code.
with active I/O.
xxxx1801 Reconfiguration received a nonzero
00001503 Processing for vary path return code from an ESTAE macro.
104 z/OS V1R10.0 MVS System Codes
0B7
xxxx The return code. the reason and response codes were
either not recognized or expected.
xxxx1904 Reconfiguration received a nonzero
Reconfiguration records diagnostic
return code from an ESTAE macro.
information in the system diagnostic
xxxx The return code. work area (SDWA), in the variable
recording area (VRA), or for CPU/VF
xxxx1A01 Reconfiguration received a nonzero reconfiguration, SYMREC.
return code from an ESTAE macro. Reconfiguration returns control to the
xxxx The return code. caller with return code X'1C'.
xxxx1A02 Reconfiguration called the service xxxx The reason or response
processor, but the service processor code.
did not return information. xxxx2120 Reconfiguration requested virtual
xxxx The response code from the storage. The request returned a
service processor. nonzero return code. Reconfiguration
records diagnostic information in the
xxxx1B01 Reconfiguration received a nonzero SDWA, in the VRA, or for CPU/VF
return code from an ESTAE macro. reconfiguration, SYMREC.
xxxx The return code. Reconfiguration returns control to the
caller with return code X'20'.
xxxx1B02 Reconfiguration called the service
processor, but the service processor xxxx The GETMAIN return code.
did not return CHP information. 00002128 Reconfiguration received an incorrect
xxxx The response code from the request. The request is incorrect for
service processor. one of the following reasons:
v The parameter list control block
xxxx1C01 Reconfiguration received a nonzero
identifier or version number was
return code from an ESTAE macro.
incorrect.
xxxx The return code. v The function code was
xxxx1C02 A reconfiguration call to the service unrecognized.
processor failed. v The side information block control
block identifier or version number
xxxx The response code from the was incorrect.
service processor.
0000212C Reconfiguration was running on a
xxxx2001 Reconfiguration could not set up an central processor that does not
ESTAE environment. support the service processor
xxxx2002 Reconfiguration message processing architecture.
could not find a message identifier. xxxx2201 Reconfiguration received a nonzero
xxxx2003 Reconfiguration message processing return code from an ESTAE macro.
found that the number of inserts xxxx The ESTAE return code.
received in the parameters does not
match the message definition. xxxx2202 Reconfiguration received an incorrect
function code.
xxxx2004 Reconfiguration message processing
found that the specified message xxxx The incorrect function code.
does not fit into the 72-byte buffer.
xxxx2281 Reconfiguration received a nonzero
xxxx2005 Reconfiguration message processing return code.
found that the parameters passed to it
xxxx The return code.
specified more than 4 bytes for the
length of a table insert or a xxxx2282 Reconfiguration requested virtual
hexadecimal or decimal insert. storage. The request returned a
nonzero return code.
xxxx2006 Reconfiguration message processing
found that the parameters passed to it xxxx The GETMAIN return code.
specified a table insert that was
xxxx22C1 Reconfiguration received a nonzero
beyond the insert table in the
return code from a service processor
message definition.
call SVC.
xxxx211C A reconfiguration call to the service
xxxx The return code.
processor did not return information;
Chapter 2. System Completion Codes 105
0B8 • 0B9
xxxx22C2 Reconfiguration received an
0B8
unexpected response from the service
processor. Explanation: A START, MOUNT, or LOGON command
requested the creation or initialization of a new address
xxxx The service processor
space. The system detected an error while processing
response.
the command. A hexadecimal reason code in register 15
xxxx2302 The system called reconfiguration explains the error:
message processing; an error
Code Explanation
occurred.
04 The command code in the command
xxxx2402 The system called reconfiguration
scheduling control block (CSCB) for the
message processing; an error
START, MOUNT, or LOGON command was
occurred.
incorrect.
xxxx2502 The system called reconfiguration
08 The system tried to build a task I/O table
message processing; an error
(TIOT) for the START, MOUNT, or LOGON
occurred.
processing, but failed.
xxxx2602 The system called reconfiguration
0C While processing the START, MOUNT, or
message processing; an error
LOGON command, the system could not open
occurred.
or write to an internal reader.
xxxx2702 The system called reconfiguration
10 Processing to initialize the address space
message processing; an error
returned an undefined return code; the defined
occurred.
codes are 0 and 4.
xxxx2802 The system called reconfiguration
14 The newly created address space cannot be
message processing; an error
made nonswappable.
occurred.
18 To create the requested address space, the
xxxx2902 The system called reconfiguration
system issued a REQSWAP SYSEVENT
message processing; an error
macro. The macro failed.
occurred.
1C The newly created address space did not
xxxx2A02 The system called reconfiguration
initialize completely.
message processing; an error
occurred. 20 Dynamic allocation or unallocation failed for an
internal reader.
System action: The system:
v Frees all resources related to the reconfiguration System action: The system:
command. v Ends the START, MOUNT, or LOGON command.
v Writes a logrec data set error record. v Writes a dump.
v May issue message IEE174I or IEE521I. v Writes a logrec data set error record.
v Writes a dump. v Issues messages. For a START or MOUNT
command, the system issues message IEE824I.
Operator response: Enter the command again. If the
command fails again, look at message IEE521I. System programmer response: If the problem
Depending on the text of message IEE521I, do the recurs, search problem reporting data bases for a fix for
following: the problem. If no fix exists, contact the IBM support
Center. Provide the dump and the logrec data set error
STATUS NOT OBTAINED: SERVICE PROCESSOR
record.
FAILURE
Contact hardware support. Provide the logrec data Source: Master scheduler
set error record.
STATUS NOT OBTAINED: SERVICE PROCESSOR 0B9
CALL FAILED
Explanation: A START, MOUNT, or LOGON command
Contact the system programmer.
requested creation or initialization of an address space.
System programmer response: Search problem The started task control (STC) queried the master
reporting data bases for a fix for the problem. If no fix subsystem to determine if a subsystem was started.
exists, contact the IBM Support Center. Provide the STC received a return code that was not valid from the
dump and the logrec data set error record. master subsystem.
Source: Reconfiguration System action: The system:
v Ends the START, MOUNT, or LOGON command.
106 z/OS V1R10.0 MVS System Codes
0BA • 0Cx
v Writes a dump. LOGON task. In the initiator, the system issues
v Writes a logrec data set error record. message IEF187I and ends the job. The system writes
a logrec data set error record. The system may write an
v Issues messages. For a START or MOUNT
SVC dump.
command, the system issues message IEE824I.
Operator response: Enter the command again. If it
System programmer response: If the problem
fails again, contact the system programmer.
recurs, search problem reporting data bases for a fix for
the problem. If no fix exists, contact the IBM support System programmer response: Search problem
Center. Provide the dump and the logrec data set error reporting data bases for a fix for the problem. If no fix
record. exists, contact the IBM Support Center. Provide the
SVC dump, if available, and the logrec data set error
Source: Master scheduler
record.
Source: Master scheduler or initiator/terminator
0BA
Explanation: Started task control was processing a
0BB
START, MOUNT, or LOGON command and issued a
request to a subsystem. The subsystem or subsystem Explanation: During initialization of a job step or
interface (SSI) returned an incorrect return code, which processing of a START or LOGON command, the
is contained in Register 15. initiator issued an ATTACH macro to attach the job step
task, the started task, or the LOGON task. The ATTACH
Valid return codes are:
failed.
v 0 - Request processed by a subsystem.
System action: The initiator is abnormally ended
v 4 - Subsystem does not support the requested
causing failure of the job, START or LOGON. Register
function.
15 contains the return code from ATTACH.
v 8 - Subsystem exists, but is not up.
Operator response: Retry the command. If the
v C - Subsystem does not exist.
problem persists, tell the system programmer.
Invalid return codes are: System programmer response: Search problem
v 10 - Function not completed - disastrous error reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center, providing the
– SSOB unavailable (for example, SSOB pointer SVC dump and the logrec data set error records.
invalid)
– SSIB unavailable (for example, SSIB pointer Source: Initiator/terminator
invalid)
– The JES detected an abend or other major error 0Cx
Explanation: A program interruption occurred, but no
Note: In most cases, the 0BA abend with return routine had been specified to handle this type of
code 10 will have been preceded by another interruption. Refer to the instruction description in
error - usually an abend. If this is the case, Principles of Operation to find out how the instruction
then the 0BA should be ignored and the stops processing for the error condition.
preceding error (or abend) should be
researched and resolved. If no preceding The last digit of this completion code is a hexadecimal
abend is found, check to see if anything was number that indicates the cause of the program
written to the logrec data set. interruption. Each X'0Cx' system completion code has a
v 14 - Logical error reason code, which in most cases equals the last digit.
X'0C4' however, has several reason codes.
– SSOB block identifier not = ″SSOB″
– SSOB length invalid Code Explanation
– SSIB block identifier not = ″SSIB″ 0C1 Operation exception. The reason code is 1.
– SSIB length invalid 0C2 Privileged-operation exception. The reason
v Any value other than those previously listed. code is 2.
0C3 Execute exception. The reason code is 3.
Note: In certain cases in which the subsystem must be
available to process the request, ’0’ will be 0C4 One of the following exceptions occurred:
considered to be the only valid return code.
4 Protection exception. The key of the
System action: In started task control, if the command storage area that the running program
is START, MOUNT, or LOGON the system issues tries to access is different from that of
message IEE824I and ends the START, MOUNT, or the running program. The key of the
Chapter 2. System Completion Codes 107
0Cx
running program can be obtained from To correct the error, allocate the
the PSW key field. The key of the storage before attempting to
storage can be obtained using the reference it.
IPCS LIST subcommand if the v A program running in a subspace
DISPLAY(MACHINE) option is in attempted to reference storage that
effect. The DISPLAY(MACHINE) was not accessible to the subspace
option is not the IPCS-supplied default at the time of error. To correct the
and must be enabled by explicitly error, ensure that the program
asking for the data or as a running in a subspace references
consequence of having used SETDEF only the storage assigned to that
to make the DISPLAY(MACHINE) subspace, or storage that can be
option the default. The programmer referenced by all subspaces.
should determine whether the
v SMS abend. The reason code is
program is running with the correct
X'12C'.
key or whether the storage address is
set up correctly. 2B ASTE-validity exception. This error is
caused by one of the following:
The protection exception might have
occurred when the program v During access-register translation,
referenced a page that is protected except as in the case of the
with the PGSER PROTECT service, following bullet, the access-list entry
or is defined as shared by the used designates an
IARVSERV service with a view of ASN-second-table entry in which bit
read-only. 0 is not zero. The access-list entry
is the one designated by the
10 Segment-translation exception. This access register used.
error is caused by one of the
v During access-register translation of
following:
ALET 1 by BRANCH IN
v A program that was running SUBSPACE GROUP, the
disabled attempted to reference subspace-ASTE origin (SSASTEO)
storage while the page table for in the dispatchable-unit control
that storage was paged out. To table designates an
correct the error, page-fix the ASN-second-table entry in which bit
storage before a program running 0 is not zero.
disabled attempts to reference it.
v During a subspace-replacement
v A program attempted to reference operation, the subspace-ASTE
storage that had not been obtained. origin (SSASTEO) in the
To correct the error, allocate the dispatchable-unit control table
storage before attempting to designates an ASN-second-table
reference it. entry in which bit 0 is not zero.
v A program running in a subspace
38 ASCE Type exception. This error is
attempted to reference storage that
caused by one of the following:
was not accessible to the subspace
at the time of error. To correct the v A program attempted to reference
error, ensure that the program storage that had not been obtained.
running in a subspace references To correct the error, allocate the
only the storage assigned to that storage before attempting to
subspace, or storage that can be reference it.
referenced by all subspaces. v A program running in 64-bit
addressing mode used a 31-bit
11 Page-translation exception. This error
pointer that had the high order bit
is caused by one of the following:
on.
v A program that was running
disabled attempted to reference Note: Programs running in 31-bit
storage while that storage was mode using 4-byte pointers
paged out. To correct the error, often use the high order bit
page-fix the storage before a of a 4-byte pointer to
program running disabled attempts indicate 31-bit addressing
to reference it. mode, versus 24-bit mode.
v A program attempted to reference Also, certain instructions will
storage that had not been obtained. set the high order bit on in
108 z/OS V1R10.0 MVS System Codes
0Cx
registers to indicate To correct the error, allocate the
addressing mode. storage before attempting to
v A program running in 64-bit reference it.
addressing mode loaded a 31-bit v A program running in 64-bit
pointer into a 64-bit register and did addressing mode used a 31-bit
not clear the high half of the pointer that had the high order bit
register. To correct the error, ensure on.
that the program running in 64-bit
addressing mode clears the 33 Note: Programs running in 31-bit
high-order bits of any register when mode using 4-byte pointers
loading a 31-bit pointer into that often use the high order bit
register. of a 4-byte pointer to
| v A program that was running indicate 31-bit addressing
| disabled attempted to access mode, versus 24-bit mode.
| storage that was not obtained as Also, certain instructions will
| DREF. set the high order bit on in
registers to indicate
39 Region-First exception. This error is addressing mode.
caused by one of the following:
v A program running in 64-bit
v A program attempted to reference addressing mode loaded a 31-bit
storage that had not been obtained. pointer into a 64-bit register and did
To correct the error, allocate the not clear the high half of the
storage before attempting to register. To correct the error, ensure
reference it. that the program running in 64-bit
v A program running in 64-bit addressing mode clears the 33
addressing mode used a 31-bit high-order bits of any register when
pointer that had the high order bit loading a 31-bit pointer into that
on. register.
| v A program that was running
Note: Programs running in 31-bit | disabled attempted to access
mode using 4-byte pointers | storage that was not obtained as
often use the high order bit | DREF.
of a 4-byte pointer to
indicate 31-bit addressing 3B Region-Third exception. This error is
mode, versus 24-bit mode. caused by one of the following:
Also, certain instructions will v A program attempted to reference
set the high order bit on in storage that had not been obtained.
registers to indicate To correct the error, allocate the
addressing mode. storage before attempting to
v A program running in 64-bit reference it.
addressing mode loaded a 31-bit v A program running in 64-bit
pointer into a 64-bit register and did addressing mode used a 31-bit
not clear the high half of the pointer that had the high order bit
register. To correct the error, ensure on.
that the program running in 64-bit
addressing mode clears the 33 Note: Programs running in 31-bit
high-order bits of any register when mode using 4-byte pointers
loading a 31-bit pointer into that often use the high order bit
register. of a 4-byte pointer to
| v A program that was running indicate 31-bit addressing
| disabled attempted to access mode, versus 24-bit mode.
| storage that was not obtained as Also, certain instructions will
| DREF. set the high order bit on in
registers to indicate
3A Region-Second exception. This error addressing mode.
is caused by one of the following:
v A program running in 64-bit
v A program attempted to reference addressing mode loaded a 31-bit
storage that had not been obtained. pointer into a 64-bit register and did
not clear the high half of the
register. To correct the error, ensure
Chapter 2. System Completion Codes 109
0D2 • 0D4
that the program running in 64-bit experiencing the program check. If the task cannot be
addressing mode clears the 33 ended because of the translation problems, the system
high-order bits of any register when tries to end the address space. If this fails, the system
loading a 31-bit pointer into that enters a disabled wait state, for example, wait state
register. X'014'.
| v A program that was running Application Programmer Response: Correct the
| disabled attempted to access error. Rerun the program.
| storage that was not obtained as
| DREF. Source: Supervisor control
0C5 Addressing exception. The reason code is 5.
0D3
0C6 Specification exception. The reason code is 6.
Explanation: A program check occurred; the
0C7 Data exception. The reason code is whatever interruption code is X'13' for a special operation error.
the data exception code is in field SDWADXC See Principles of Operation for more information about
in the SDWA (systems diagnostic work area). special operation errors.
0C8 Fixed-point-overflow exception. The reason System action: The system abnormally ends the task
code is 8. experiencing the program check.
0C9 Fixed-point-divide exception. The reason code Application Programmer Response: Check to see if
is 9. the program issued a PC in secondary mode. Remove
0CA Decimal-overflow exception. The reason code the Set System Mask (SSM) instruction. This instruction
is A. is not valid in the system.
0CB Decimal-divide exception. The reason code is Source: Supervisor control
B.
0CC Exponent-overflow exception. The reason code 0D4
is C. Explanation: A program issued a Program Call (PC),
0CD Exponent-underflow exception. The reason Program Return (PR), Program Transfer (PT), or Set
code is D. Storage Address Register (SSAR) instruction. During
processing of the instruction, an address space number
0CE Significance exception. The reason code is E. (ASN) translation specification exception occurred. The
0CF Floating-point-divide exception. The reason ASN translation exception is also known as an address
code is F. space identifier (ASID) translation exception. The
program interruption code if X'17'. The address space
System action: The system abnormally ends the task, first table (AFT) or the address space second table
unless a recovery routine was provided to handle the (AST) contains incorrect data.
interruption. The hardware action is given in Principles
of Operation. System action: The system abends the program that
issued the PC, PR, PT, or SSAR instruction. The
System programmer response: Determine whether system writes an SVC dump or a logrec data set error
the problem program or control program was in error. record or both.
If the problem program contained an error, correct it, System programmer response: If a search of the
and run the job step again. problem reporting data bases does not show a fix for
the problem, contact the IBM Support Center. Provide:
Source: Supervisor control
v The SVC dump and the logrec data set error record,
which contains control registers 3, 4, and 14
0D2
v The instruction being processed by PC/AUTH when
Explanation: A program check occurred; the the problem occurred.
interruption code is X'12' for a translation specification To determine the instruction, start at the bottom of the
error. The error was caused by incorrect data in control system trace table and back up to a *PGM 017 entry.
registers 0 or 1 or a segment or page table. The Continue backing up to the first PC, PT, or SSAR
incorrect data is due to: entry, which is the instruction that was being
v A hardware error processed at the time of the failure.
v Damage by a program running in key 0
Source: Program Call/authorization (PC/AUTH)
See Principles of Operation for more information about
translation specification errors.
System action: The system tries to end the task
110 z/OS V1R10.0 MVS System Codes
0D5 • 0D6
50000511
0D5
A disabled caller suffered a page fault due to
Explanation: A program issued a Program Call (PC), an invalid attempt to reference storage in a
Program Return (PR), Program Transfer (PT) or Set data space owned by a logically swapped out
Storage Address Register (SSAR) instruction for cross address space.
memory access. One of the following occurred:
System programmer response:
v An address space first table index (AFX) translation
v For a program interrupt code X'20' or X'21':
exception (program interruption code X'20') occurred.
Look for a problem with the PC/AUTH macros
The value in the address space first table (AFT)
that established the cross memory service.
corresponding to the address space identifier (ASID)
Correct any problems.
is not valid. Either no such address space exists or
Check the failing program for logic that changes
the system had swapped it out.
general register 3, 4, or 14.
v An address space second table index (ASX) Search problem reporting data bases for a fix for
translation exception (program interruption code the problem. If no fix exists, contact the IBM
X'21') occurred. The value in the address space Support Center.
second table (AST) corresponding to the ASID is not
v For cross memory access to a swappable address
valid. Either no such address space exists or the
space:
system had swapped it out.
Ensure that the address spaces that provide cross
v The cross memory access is to a swappable address memory services are non-swappable.
space, which is a violation of MVS cross memory Search problem reporting data bases for a fix for
access protocol. the problem. If no fix exists, contact the IBM
System action: For program interrupt code X'20' or Support Center. Provide the SVC dump.
X'21', the system attempts to correct any errors in the Source: Either:
AFT. The system abnormally ends the program that v Real storage manager (RSM)
issued the PC, PR, PT or SSAR instruction. v Program Call/Authorization (PC/AUTH)
If the error was cross memory I/O in progress for a
swappable address space, the system abnormally ends 0D6
the program that was waiting for the I/O to complete.
The system continues swapping out the address space. Explanation: A program issued a Program Call (PC)
instruction that specified an incorrect PC number. A
If the error was an incorrect cross memory reference to hexadecimal reason code or interrupt code explains the
a swappable address space, the system abends that error:
address space. For example, if additional pages are to
be fixed in a logically swapped address space, the Code Explanation
system ends the logically swapped address space. 00 The PC number specified in the PC instruction
Check the return code located in register 15 for is undefined.
additional information:
Code Explanation
Return Code
Meaning 22 A linkage index (LX) translation exception
occurred; the program interruption code is
04001300 X'22'.
An enabled caller suffered a page fault due to
an invalid attempt to reference storage in a 23 An entry table (EX) translation exception
logically swapped out address space. occurred; the program interruption code if
X'23'.
2D001310
A disabled caller suffered a page fault due to 26 Linkage first index translation exception.
an invalid attempt to reference storage in a
27 Linkage second index translation exception.
logically swapped out address space.
| 2E An LSTE-Sequence Exception interrupt
05000302
| occurred. The linkage-second-table-entry
An enabled caller suffered a segment fault due
| sequence number in bits 0-31 of 64-bit general
to an invalid attemp to reference storage in a
| register 15 for a PROGRAM CALL instruction
logically swapped out address space.
| does not have the required value.
4F000510
System action: The system abends the program that
An enabled caller suffered a page fault due to
issued the PC instruction. The system writes an ABEND
an invalid attempt to reference storage in a
dump.
data space owned by a logically swapped out
address space. System programmer response: Look for a problem
with the PC/AUTH macros that established the cross
Chapter 2. System Completion Codes 111
0D7 • 0DA
memory service being used by the failing program. address space is still active, look for a problem with the
PC/AUTH macros that established the cross memory
For reason code X'00', register 14 points to the next
service being used by the failing program.
instruction after the PC instruction. Bit 31 of register 14
is the PSW problem state bit at the time the PC If no problems were found or if the problem recurs,
instruction was issued. Registers 0, 2, 5-11, and 13 search problem reporting data bases for a fix for the
contain the values they had when the PC instruction | problem. If no fix exists, and the abend is not expected
was issued. | (e.g. the unit of work owning the cross memory
| resources was not ended), contact the IBM Support
If the program that abended is a TCPIP application, see
Center.
z/OS Communications Server: IP Diagnosis Guide
Source: Program Call/authorization (PC/AUTH)
If no problems were found or the problem recurs,
search problem reporting data bases for a fix for the
problem. if no fix exists, contact the IBM Support 0D8
Center. Provide the ABEND dump.
Explanation: A space switch exception occurred. A
Source: Program Call/authorization (PC/AUTH) program issued a Program Call (PC), Program Return
(PR), or Program Transfer (PT) instruction, but the cross
memory resource ownership task in the target address
0D7
space has ended. The target address space is not the
Explanation: A problem occurred while the system home address space of the program that issued the PC
processed a Program Return (PR), Program Transfer or PT instruction. The program interruption code if
(PT) or Set Storage Address Register (SSAR) X'1C'.
instruction, as follows.
System action: The system abends the program that
v A program issued the PT instruction, but a primary issued the PC, PR, or PT instruction.
authority exception occurred. The primary address
space is not authorized to issue a PT instruction to System programmer response: Look for a problem
the target address space. with the PC/AUTH macros that established the cross
memory service being used by the failing program.
Either:
Correct any problems in the program and resubmit it.
– The authorization index (AX) is greater than the
number of elements in the target address space’s If no problems were found or if the problem recurs,
authorization table (AT) search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support
– The P bit is off in the target address space’s AT.
Center.
The program interruption code is X'24'.
v A program issued the SSAR instruction, but a Source: Program Call/authorization (PC/AUTH)
secondary authority exception occurred. The primary
address space is not authorized to issue an SSAR 0D9
instruction to the target address space.
Explanation: One of the following system errors
Either:
occurred:
– The AX is greater than the number of elements in
v A program check occurred because of a hardware
the target address space’s AT.
problem.
– The S bit is off in the target address space’s AT.
v A program running storage key zero caused data
The program interruption code is X'25'.
damage.
v A program issued the PR instruction, but a secondary
authority exception occurred. The primary address System action: The system abnormally ends the
space is not authorized to issue an PR instruction to current task.
the target address space. Application Programmer Response: Rerun the job.
Either:
| Source: Program Call/authorization (PC/AUTH)
– The AX is greater than the number of elements in
the target address space’s AT.
– The S bit is off in the target address space’s AT. 0DA
The program interruption code is X'25'. Explanation: A program issued a Program Call (PC)
System action: The system abended the program that instruction and a PC translation specification exception
issued the PR, PT or the SSAR instruction. occurred. The program interruption code is X'1F'.
| System programmer response: This error might be Either the linkage table (LT) or the entry tables (ET)
| normal and can occur if an address space involved in contain incorrect data. This can be either an application
the cross memory environment has terminated. If the program or system program error.
112 z/OS V1R10.0 MVS System Codes
0DB • 0DC
System action: The system abended the program that ABEND dump, add one of the following and run the job
issued the PC instruction. The system may write an step again. Use a SYSMDUMP DD statement if you
SVC dump for this abend. plan to analyze and format the dump with the interactive
problem control system (IPCS).
Operator response: If requested by the system
SYSABEND DD statement
programmer, set a SLIP trap to obtain an SVC dump.
SYSMDUMP DD statement
Specify the address space for the failing program as the
SYSUDUMP DD statement
first address space identifier (ASID) in the ASIDLIST
parameter as follows: Source: Recovery termination manager (RTM)
SLIP SET,ID=C0DA,COMP0DA,ACTION=SVCD,ASIDLIST=
(02),END 0DC
System programmer response: Do the following: Explanation: The recovery termination manager
1. Check the addressing mode of the PC routine. If it is (RTM) encountered an unrecoverable error while
24-bit, ensure that there is no extraneous data in processing a functional recovery routine (FRR) stack.
bits 1-7 of the address. RTM issues this abend when:
2. Obtain the SVC dump, if one was written. If no v It detects a problem while processing another abend.
dump was produced, but the problem can be v It detects that critical fields in important control blocks
recreated, ask the operator to set a SLIP trap to for the address space or system are overlaid. These
obtain the dump. control blocks include the:
3. In the SVC dump, determine the PC number of the – Address space control block (ASCB)
PC instruction processing at the time of the failure – Extended status block (XSB)
by doing the following: – Request block (RB)
a. Starting at the bottom of the system trace table, – Task control block (TCB)
back up to to a *PGM 01F entry. RTM ends the address space. This abend code is found
b. Continue backing up to the first PC entry. This is in the ASCBMCC field in the ASCB for the ended
the PC entry for the instruction that was being address space and in message IEF402I.
processed. The PC number is in the UNIQUE-1
column. A hexadecimal reason code in field ASCBARC of the
4. If the failing PC instruction was for an ETCRE or ASCB and in message IEF402I explains the error:
ETCON macro in an installation-provided program,
Code Explanation
obtain the following data to fix the problem:
v The input to the ETCRE macro 04 RTM recovery received control after RTM FRR
v The parameters on the ETDEF macro, if used. processing encountered an unrecoverable error
5. If the failing PC instruction is in an IBM module, and abnormally ended the address space.
search problem reporting data bases for a fix for the 08 RTM FRR processing that is not covered by an
problem. If no fix exists, contact the component FRR encountered an unrecoverable error.
group for the module. Provide the SVC dump. RTM’s default recovery received control and
Source: Program Call/authorization (PC/AUTH) abnormally ended the address space.
0C During second level interrupt handler (SLIH)
0DB processing, RTM detected an incorrect value in
the TCBTCBID field of the current TCB. RTM’s
Explanation: A program check was detected. An recovery received control and abnormally
interruption code of X‘15’, an operand exception, has ended the address space.
occurred.
10 During SLIH processing, RTM found 0 in the
System action: The task ends. TCBRBP field. RTM’s recovery received control
Application Programmer Response: This is a and abnormally ended the address space.
system error. Run the job again. 14 During SLIH processing, RTM detected an
System programmer response: If the error recurs invalid value for the current FRR pointer in
and the program is not in error, look at the messages in PSASTAK (FRRSCURR). Due to this damage,
the job log for more information. Search problem RTM can not determine which FRRs are
reporting data bases for a fix for the problem. If no fix available to the current unit of work. A
exists, contact the IBM Support Center. Provide the LOGREC record is written that shows the
JCL, the program listing for the job, and all printed damaged and corrected versions of PSASTAK,
output and output data sets related to the problem. and the current Address Space is abnormally
ended.
Obtain the ABEND dump for the failing job step. If the
JCL for the step did not contain a DD statement for an System action: The system abnormally ends the
Chapter 2. System Completion Codes 113
0E0 • 0E1
address space, places the abend code and reason code this bit in a linkage stack entry to prevent SVC
into the ASCB for the ended address space, and issues routines from unstacking entries they did not
message IEF402I. add to the stack.
System programmer response: Do the following: nnn An unexpected interrupt code. A possible
1. Obtain the reason code from message IEF402I or cause of this is that the level of MVS is not the
from field ASCBARC of the ASCB. correct one for the hardware.
2. Search problem reporting data bases for a fix for the System action: The system abnormally ends the task
problem. If no fix exists, contact the IBM Support experiencing the program check, unless the task
Center. provides recovery to handle the interruption. The system
may write a logrec data set error record.
Source: Recovery termination manager (RTM)
Operator response: If the system programmer asks
for an SVC dump, set the following SLIP trap:
0E0
SLIP SET,COMP=0E0,ACTION=SVCD,END
Explanation: A program check occurred. The
hexadecimal interruption code is as follows: Application Programmer Response: Do one of the
following:
Code Explanation
v For reason code X'30', determine if your program has
1D A square root exception occurred. improperly added entries to the linkage stack. For
example, unintentionally executing a BAKR many
1E An unnormalized operand exception occurred. times can fill the linkage stack. If your program is not
28 Reserved bit positions in an access list entry improperly adding entries to the linkage stack, then
token (ALET) were nonzero. use an LSEXPAND macro to increase the size of the
linkage stack.
29 An ALET specified an access list entry (ALE)
v For reason code X'32' or X'33', see Principles of
that is not valid.
Operation.
2A An ALET specified a previously deleted ALE. v For other reason codes, determine if the problem
2B Either an ALE specified a data space that is program or the system was in error. If the problem
not valid or there is an ASTE validity check for program contained an error, correct it, and run the job
an address space on an access list. step again.
2C An ALE refers to a sequence number in the System programmer response: Do the following:
address space second table entry (ASTE). The 1. If a logrec data set error record was not written for
sequence number is not equal to the number in the program check, ask the operator to set a SLIP
the ALE. trap to obtain an SVC dump.
2D A private ALE is specified, but the current 2. Look at the program status word (PSW) at the time
extended authorization index (EAX) is not of error. Use the address in the PSW to identify the
authorized to the target address space. module that experienced the X'0E0' program check.
v For an installation-provided module, continue
2F An ASTE-Instance Exception interrupt
diagnosis with the module.
occurred. An ASTE instance number
associated with a PROGRAM TRANSFER v For an IBM module, search problem reporting
WITH INSTANCE instruction, a PROGRAM data bases for a fix for the problem. If no fix
RETURN instruction, or a SET SECONDARY exists, contact the component group associated
ASN WITH INSTANCE instruction, does not with this module at the IBM Support Center.
have the required value. Provide, if available, the SVC dump and the
logrec data set error record.
30 A stacking instruction was issued when the
linkage stack was full. Source: Supervisor control
31 An unstacking instruction such as PR or EREG
was issued when the linkage stack was empty. 0E1
32 A linkage stack specification interrupt occurred. Explanation: An error was encountered while
processing the first EXCP against a virtual I/O (VIO)
33 The hardware or an unstacking operation data set. Register 15 contains a hexadecimal reason
found a linkage stack entry (LSE) type that is code:
not valid.
Code Explanation
34 A Program Return (PR) instruction was issued
against a linkage stack entry that has the 2xx RSM was unable to ‘assign null’ the virtual
unstack suppression bit set. The system sets track buffer or the DSPCT map. Where xx is:
114 z/OS V1R10.0 MVS System Codes
0E2 • 0E3
xx Explanation SYSOUT output for the job and the logrec data set error
record.
04 An assign (move-in) error occurred.
The page identified by the VCBVSA Source: DFSMSdfp
field is not available.
08 A write (move-out) error occurred. The 0E2
page identified by the VCBVSA field is
Explanation: The error was detected while processing
fixed in real storage and cannot be
the first EXCP for the VIO data set after a restart.
written to the data set in auxiliary
Register 15 contains one of the following hexadecimal
storage.
reason codes:
0C The request was incorrect; it was not
Code Explanation
an assign or a write request.
2xx RSM was unable to ‘assign null’ the virtual
10 The page identified by the VCBVSA
track buffer or the DSPCT map. Refer to code
field is not written to the data set
0E1 for an explanation of xx.
because it was not brought into real
storage by the prior read request or System action: The input parm list (IDAVOP1),
because data in the page has not DSPCT header (IDAVBPH) and SWA are dumped to the
been modified. SYS1.DUMP data set.
20 The page identified by the VCBVSA Application Programmer Response: System error.
field belongs to an LPID other than Rerun the job.
the LPID in the VCBLPID field.
System programmer response: If the error recurs
40 The virtual storage address in the and the program is not in error, look at the messages in
VCBVSA field was incorrect. A the job log for more information. Search problem
GETMAIN macro was not issued for reporting data bases for a fix for the problem. If no fix
the page identified by the VCBVSA exists, contact the IBM Support Center. Provide the
field. SYSOUT output for the job and the logrec data set error
record.
80 An assign error occurred. The page
identified by the VCBVSA field was Source: DFSMSdfp
read previously but was not
disconnected by a move-out or
move-out-null request before the 0E3
current read (assign) operation. Explanation: The error occurred while processing a
3xx The auxiliary storage manager (ASM) was VIO data set. Register 15 contains one of the following
unable to ASSIGN a logical group for this VIO hexadecimal reason codes:
data set. Where xx is: Code Explanation
xx Explanation 004 An incorrect RBA was passed to VBP.
1C One of the following occurred: Probable causes of error code are (1) DEB
with extent descriptions that do not fall within
v ASM could not obtain storage to the allocated extents as described in the virtual
process the request. data set control block (VDSCB) (2) EXCP was
v ASM could not assign a logical issued to read the format 1 DSCB on the
group because the requested volume.
maximum relative page number
was too large. 2xx RSM was unable to assign or move out pages
in the virtual track buffer. Refer to code 0E1 for
System action: The input parm list (IDAVOP1), the an explanation of xx.
DSPCT header (IDAVBPH) and SWA are dumped to the
SYS1.DUMP data set. System action: The following are dumped to the
SYS1.DUMP data set:
Application Programmer Response: System error. v Input parameter list (IDABUFC)
Rerun the job. v DSPCT header (IDAVBPH)
v SWA
System programmer response: If the error recurs
v LSQA
and the program is not in error, look at the messages in
v The region (in some cases)
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix Application Programmer Response: System error.
exists, contact the IBM Support Center. Provide the Rerun the job.
System programmer response: If the error recurs
Chapter 2. System Completion Codes 115
0E4 • 0E7
and the program is not in error, look at the messages in Application Programmer Response: System error.
the job log for more information. Search problem Rerun the job.
reporting data bases for a fix for the problem. If no fix
System programmer response: If the error recurs
exists, contact the IBM Support Center. Provide the
and the program is not in error, look at the messages in
SYSOUT output for the job and the logrec data set error
the job log for more information. Search problem
record.
reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp exists, contact the IBM Support Center. Provide the
SYSOUT output for the job and the logrec data set error
record.
0E4
Source: DFSMSdfp
Explanation: The error occurred while trying to
scratch a VIO data set.
0E6
Register 15 contains one of the following hexadecimal
reason codes: Explanation: Unable to process against a VIO data
set that has already been scratched.
Code Explanation
System action: The VDSCB (IDDVDSCB) is dumped
3xx ASM could not RELEASE the logical group for
to the SYS1.DUMP data set.
this data set. Where xx is:
Application Programmer Response: Do not access
xx Explanation
a scratched data set.
04 Incorrect LGN.
System programmer response: If the error recurs
1C Unable to obtain storage to process and the program is not in error, look at the messages in
request. the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
20 Incorrect operation code is supplied in exists, contact the IBM Support Center. Provide the
the auxiliary storage manager control SYSOUT output for the job and the logrec data set error
area (ACA). record.
28 Incorrect identifier type when an LGN Source: DFSMSdfp
was given, but ‘S’ type symbol is
required.
0E7
System action: The DSPCT header is dumped to the
SYS1.DUMPxx data set. Explanation: The error occurred while journaling the
DSPCT header (IDAVBPH) at step end or at checkpoint.
Application Programmer Response: System error. Register 15 contains one of the following hexadecimal
Rerun the job. reason codes:
System programmer response: If the error recurs Code Explanation
and the program is not in error, look at the messages in
the job log for more information. Search problem 2xx RSM was unable to ASSIGN or MOVE OUT
reporting data bases for a fix for the problem. If no fix pages in the virtual track buffer. Refer to code
exists, contact the IBM Support Center. Provide the 0E1 for explanation of xx.
SYSOUT output for the job and the logrec data set error
3xx ASM was unable to ‘SAVE’ the logical group
record.
for this data set. Where xx is:
Source: DFSMSdfp
xx Explanation
04 Incorrect LGN.
0E5
14 Unrecoverable error occurred while
Explanation: Unable to disconnect the virtual track
writing to VIO journaling data set.
buffer from the VIO data set.
1C Unable to obtain storage to process
Register 15 contains one of the following hexadecimal
request.
reason codes:
20 Incorrect operation code is supplied in
Code Explanation
the auxiliary storage manager control
2xx RSM was unable to ‘MOVE OUT’ pages in the area (ACA).
virtual track buffer. Refer to code 0E1 for an
2C Indeterminate error has occurred.
explanation of xx.
System action: The DSPCT header (IDAVBPH) and
System action: The DSPCT header and SWA are
SWA are dumped on the SYS1.DUMP data set.
dumped to the SYS1.DUMP data set.
116 z/OS V1R10.0 MVS System Codes
0E8 • 0F2
Application Programmer Response: System error. v Register 5 contains the offset in module IATGRSC
Rerun the job. where the error was detected.
System programmer response: If the error recurs v Register 6 contains the logical IATXSEC index, which
and the program is not in error, look at the messages in indicates the type of processing in progress when the
the job log for more information. Search problem security request was made.
reporting data bases for a fix for the problem. If no fix v Register 8 contains the address of the security check
exists, contact the IBM Support Center. Provide the parameter list.
SYSOUT output for the job and the logrec data set error
Code Explanation
record.
01 IATUX58 exit returned an incorrect return code
Source: DFSMSdfp
in register 2.
02 System authorization facility (SAF) returned an
0E8
incorrect return code in register 2. Register 3
Explanation: The error occurred while processing the contains the security product return code, and
VIO data sets for the job after an abnormal system or register 4 contains the security product reason
job step task failure. Register 15 contains one of the code.
following hexadecimal reason codes:
03 IATUX59 exit returned an incorrect return code
Code Explanation in register 2.
3xx ASM was unable to release the logical group 04 IATGRSC module issued this return code to
for this data set. See code 0E4 for an cause entry into the caller’s recovery routine.
explanation of xx.
05 The system rejected a security request for
System action: The input parm list (RMPL) and the authorization to create a SYSIN data set.
ASCB are dumped to the SYS1.DUMP data set.
06 The system rejected a security request for
Application Programmer Response: System error. authorization to create a SYSOUT data set.
Rerun the job.
07 A multi-line write to operator text extraction
System programmer response: If the error recurs service, IEAVM703, returned a non-zero return
and the program is not in error, look at the messages in code in register 2. Register 3 contains the
the job log for more information. Search problem reason code.
reporting data bases for a fix for the problem. If no fix
08 The JES3 security subtask received incorrect
exists, contact the IBM Support Center. Provide the
input.
SYSOUT output for the job and the logrec data set error
record. 09 Unexpected return code from a SAF call in
module IATISEN.
Source: DFSMSdfp
System action: The security request processing is
ended.
0F0
Operator response: Request a dump of the address
Explanation: When the system tried to process a
space, save all associated print output, and notify the
machine check interruption, an error occurred when the
system programmer.
function recovery routine (FRR) stack was active.
Application Programmer Response: Depending on
System action: The system issues error messages.
the reason code, do the following:
The system writes an SVC dump. The system
v For reason code X'01', code a valid return code in
abnormally ends the task that was running when the
installation exit IATUX58.
machine check interruption occurred.
v For reason code X'03', code a valid return code in
Application Programmer Response: Run the job installation exit IATUX59.
again. v For reason codes X'02, 04, 05, 06, 07, 08', contact
the IBM Support Center.
Source: Machine check handler (MCH)
Source: JES3
0F1
0F2
Explanation: While processing a security request,
JES3 received an unexpected return code. Register 15 Explanation: An error occurred when the system was
contains a hexadecimal reason code that indicates the processing an I/O interrupt. An I/O recovery routine
type of error. failed.
For reason codes X'01, 02, 03, 04, or 07':
Chapter 2. System Completion Codes 117
0F3 • 0F6
System action: The system abnormally ends the the system will be able to recover completely. The SLIP
current task. 0F4 should be ignored in these cases if there are no
other symptoms of a problem.
Application Programmer Response: Rerun the job.
Problem determination: If the error recurs and the
System programmer response: Search problem
program is not in error, look for a logrec record related
reporting data bases for a fix for the problem. If no fix
to this abend. In the logrec record, look for the abend
exists, contact the IBM Support Center.
return and reason codes. See z/OS DFSMSdfp
Source: Input/output supervisor (IOS) Diagnosis for a description of the return and reason
codes. If none found, search problem reporting data
bases for a fix for the problem. If no fix exists, contact
0F3 the IBM Support Center. Provide the JCL, the SYSOUT
Explanation: A hard machine check interruption output for the job, and the logrec data set error record.
occurred. Source: DFSMSdfp, Binder, SPZAP, VSAM RLS, TVS,
System action: The system abnormally ends the task or CICS VR Logger
that was running when the machine check interruption Detecting Module: Many modules.
occurred.
Application Programmer Response: If the data on 0F6
external storage devices is still valid, run the job step
again. If the data is not valid, notify the system Explanation: During processing of a SETEVENT
programmer. macro for the generalized trace facility (GTF), an error
occurred. Register 15 contains a hexadecimal reason
System programmer response: Search problem code that explains the error:
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Code Explanation
Source: Machine check handler (MCH) 00 The issuer of the SETEVENT macro was not
authorized through the authorized program
facility (APF), was not in protect key 0-7, or
0F4 was not in supervisor state.
Explanation: An error was detected by some system 04 The parameter list passed to SETEVENT was
components. The ABEND reason code (in register 15) is incorrect.
the service return code. The service reason code is in
register 0 and its first byte can be used to aid in 08 An incorrect address for the monitor call queue
identifying the reporting component:. element (MCQE) was passed to SETEVENT.
v X’04’ - IGWSPZAP 0C The MCQE at the address passed to
v X’71’ - CICS VR Logger SETEVENT is incorrect for the function
v X’77’ - CICS VR Logger requested.
v X’83’ - Program Management Binder 20 The call to SETEVENT:
v In most other cases, DFSMSdfp is the source v Attempted to add elements to an existing
event directory
System action: Most commonly, recovery routines
retry to allow the failing module to return to its caller. If v Would have resulted in multiple MCQEs.
DFSMS or CICS VR Logger issued the abend, an SVC System action: The system writes messages and a
dump will usually have been taken. A failure in the dump.
binder will ordinarily produce an extensive snap dump if
an IEWDUMP DD has been allocated. Failure System programmer response: If an
information for IGWSPZAP can be captured through installation-provided program issued the SETEVENT,
one of the following: ensure that the program is authorized. Correct the error
indicated by the reason code. Run the job again.
v SYSUDUMP
v SYSABEND If an IBM-provided program issued the SETEVENT,
collect all printed output and output data sets related to
v SYSMDUMP
the problem. Search problem reporting data bases for a
Application Programmer Response: System error. fix for the problem. If no fix exists, contact the IBM
Rerun the job providing any diagnostic DD indicated Support Center. Provide the SYSOUT output and the
above under System Action. dump for the job.
System programmer response: See the problem Source: Generalized trace facility (GTF)
determination information for this abend. In some cases
a SLIP trap on 0F4 may catch a situation from which
118 z/OS V1R10.0 MVS System Codes
0F7
could not nullify the joblet-related spool dataset
0F7
so that it could be reused for the next joblet.
Explanation: The system found a serious error Following is the text associated with this
condition in the JES2 component specific user reason code: ‘UNABLE TO FIND JOB
environment (HASCxxxx) load modules. The REASON JOURNAL PDDB’.
parameter on the ABEND macro specifies a
18 The common storage $RETURN service
hexadecimal reason code that further explains the error.
determined that there was no previous save
The system records the hexadecimal reason code
area address associated with the current save
associated with this abend in a logrec data set record.
area. Therefore, the service was unable to
Code Explanation return to the proper location. Following is the
text associated with this reason code: ‘NO
00 A subsystem interface (SSI) function was
PREVIOUS SAVE AREA FOUND’.
unable to cancel an outstanding ESTAE
recovery program, probably because the 1C The JES2 exit effector determined that the exit
TRETOKEN field in the TCB recovery element was invoked from an FSS assembly
($TRE) control block was overlaid during that environment. However, while attempting to load
SSI function. Following is the text associated the address of the HFCT control block for the
with this reason code: ‘UNABLE TO CANCEL exit, the exit effector found that the address
ESTAE’. space was not properly initialized. Following is
the text associated with this reason code:
04 A task attempted to acquire the lock of two
‘ASXBJSVT DOES NOT CONTAIN FSVT
distinct subsystem job blocks (SJBs); a task
ADDRESS’.
may lock only one SJB at a time. Following is
the text associated with this reason code: 20 While attempting to write the job control table
‘ATTEMPT MADE TO LOCK TWO SJBS AT (JCT) to spool, the job termination routine
ONCE’. received a nonzero return code, probably
because of one of the following:
08 While attempting to return a common storage
v An I/O error
area (CSA) cell to the cell pool, $FRECEL
v JCT storage was overlaid.
routine found one of the following error
conditions: Following is the text associated with this
v The cell being returned does not have a reason code: ‘UNABLE TO WRITE JCT’.
valid cell control element (CCE) address at
24 Without holding a subsystem job block (SJB)
offset 0
lock, the caller attempted to obtain the job
v The cell being returned has not been
communication queues lock ($SVJLOK) that
allocated.
serializes communication between address
spaces. Following is the text associated with
Storage has been overlaid in either the first
this reason code: ‘$SVJ LOCK REQUEST
four bytes of the cell being returned, or in the
FAILED’.
CCE associated with the cell. Following is the
text associated with this reason code: 28 A TCB attempted to preempt a holder of the
‘INVALID/UNCLAIMED CELL ADDRESS’. SJB lock while producing a dump for an abend
that occurred while the SJB lock was held.
0C During a functional subsystem or functional
Following is the text associated with this
subsystem application (FSS/FSA) disconnect, a
reason code: ‘UNABLE TO OBTAIN SJB
GETMAIN failed to obtain storage from subpool
LOCK’.
230 for a parameter list. Following is the text
associated with this reason code: 2C Storage could not be obtained for the service
‘DISCONNECT DENIED-- GETMAIN request block (SRB) work area. Following is
FAILURE’. the text associated with this reason code:
‘HASCDSS DATA SPACE SERVICES
10 During the Job Termination SSI function, the
FAILURE’.
final input/output table (IOT) could not be
written to spool. Following is the text 30 HASCDSS was entered with a function other
associated with this reason code: ‘UNABLE TO than CREATE or DELETE. Following is the text
WRITE FINAL IOT CHAIN’. associated with this reason code: ‘HASCDSS
DATA SPACE SERVICES FAILURE’.
14 While attempting to end processing for a job
under the control of an execution batch monitor 34 The value given for the BLOCKS parameter
(joblet), the Job Termination SSI was unable to was either negative or zero. Following is the
locate the PDDB for the job journal. (The text associated with this reason code:
PDDB is the control block that defines a spool ‘HASCDSS DATA SPACE SERVICES
data set.) Therefore, the Job Termination SSI FAILURE’.
Chapter 2. System Completion Codes 119
0F7
38 RMTR EXIT recovery processing was entered. 6C JES2 detected an error while grouping
Following is the text associated with this SYSOUT. Following is the text associated with
reason code: ‘HASCDSS DATA SPACE this reason code: ‘INVALID STORAGE BLOCK
SERVICES FAILURE’. POINTER’.
3C FRR recovery processing was entered. 70 JES2 detected an error while grouping
Following is the text associated with this SYSOUT. Following is the text associated with
reason code: ‘HASCDSS DATA SPACE this reason code: ‘SJFREQ KEYLIST ERROR’.
SERVICES FAILURE’.
74 JES2 detected an error while building a generic
40 The MVS macro DSPSERV failed. Following is grouping token. Following is the text associated
the text associated with this reason code: with this reason code: ‘UNEXPECTED
‘HASCDSS DATA SPACE SERVICES NUMBER OF SWBIT BUFFERS’.
FAILURE’.
78 JES2 SAVE/RETURN services detected an
44 The MVS macro ALESERV failed. Following is error. Following is the text associated with this
the text associated with this reason code: reason code: ‘ENTERED $SSIEND WITH AN
‘HASCDSS DATA SPACE SERVICES OUTSTANDING $ESTAE’.
FAILURE’.
7C JES2 detected an error while unlocking a
48 The address space control block (ASCB) for $SJB. Following is the text associated with this
the address space that will own the data space reason code: ‘SJB UNLOCK NOT BY LOCK
is not equal to the current ASCB. Following is HOLDER’.
the text associated with this reason code:
80 JES2 detected an error while freeing storage
‘HASCDSS DATA SPACE SERVICES
buffers. Following is the text associated with
FAILURE’.
this reason code: ‘NOT ALL PROTECTED
4C Incorrect $DSWA version number. Following is BUFFERS $FREEBUFED’.
the text associated with this reason code:
84 The $GETHP service detected an error while
‘HASCDSS DATA SPACE SERVICES
freeing a task control block recovery element
FAILURE’.
($TRE). Following is the text associated with
50 JES2 SAVE/RETURN services detected an this reason code: ‘$GETHP ERROR -
error. Following is the text associated with this ATTEMPTED TO FREE THE TRE’.
reason code: ‘CALLER ADDRESS ARRAY
88 The FRETRE service detected a loop in the
FILLED UP’.
cell pool chain.
54 JES2 SAVE/RETURN services detected an
8C The GETTRE service detected an error in the
error. Following is the text associated with this
$TRE cell pool chain. Following is the text
reason code: ‘NO ENTRY IN CALLER
associated with this reason code: ‘GETTRE
ADDRESS ARRAY.’
ERROR’.
58 JES2 SAVE/RETURN services detected an
90 The system encountered a failure while
error. Following is the text associated with this
serializing a JES2 trace table entry. Following
reason code: ‘$RETURN - SAVE AREA HAS
is the text associated with this reason code:
IMPROPER FORMAT.’
‘$TRACER Trace Table ENQ Error’
5C JES2 SAVE/RETURN services detected an
98 A routine in CSECT HASCRQUE detected an
error. Following is the text associated with this
erroneous input parameter.
reason code: ‘ENTERED $SSIEND WITH AN
OUTSTANDING $SAVE’. 9C An incorrect resource number was passed to
the $$POST macro.
60 JES2 detected an error while processing a
scheduler JCL facility request. Following is the A0 JES2 detected inconsistent temporary
text associated with this reason code: ‘SJF protected buffer pointers.
SERVICE REQUEST FAILED’.
A4 JES2 requested an ENQ for the SVJ lock but
64 JES2 detected an error while grouping received an unexpected return code. The
SYSOUT. Following is the text associated with return code from ENQ is in register 2.
this reason code: ‘INVALID GROUPING
STRINGS OBJECT’. A8 JES2 detected a problem in an SJB. The SJB
is not on the expected queue. The SJB
68 JES2 detected an error while grouping address is in register 10.
SYSOUT. Following is the text associated with
this reason code: ‘SWBTUREQ RETRIEVE AC JES2 detected a problem in an SJB. The
ERROR’. SJBQUEUE field is not valid. The SJB address
is in register 10.
120 z/OS V1R10.0 MVS System Codes
0F7
B0 JES2 detected a problem in an SJB. The SJB E8 JES2 end of memory processing was unable to
is not on the queue indicated in SJBQUEUE. access an SJB that is associated with the
The SJB address is in register 10. terminating address space. A VSMLOC for the
SJB storage failed. Following is the text
B4 JES2 detected a problem in an SJB. The SJB
associated with this reason code: ’SJB
is not on the queue indicated in SJBQUEUE.
MEMORY NOT AVAILABLE’.
The SJB address is in register 10.
EC $SUBIT request was made from an address
B8 Following an unrecoverable I/O error, JES2
space that does not support $SUBIT requests
detected that channel-end processing
(not a NETSERV address space). Following is
requested, incorrectly, to re-drive the I/O. The
the text associated with this reason code:
text associated with the reason code is:
’SUBIT, NOT A NJE SERVER ADDRESS
INTERNAL ERROR IN CHANNEL END
SPACE’.
PROCESSING
F0 A request buffer queued by JES2 to a
BC JES2 detected a problem during a rebuild of
NETSERV address space does not have a
the SJB queues. Either the $HAVT is bad, or
valid request type (TBFTYPE or NRQEYE is
the SVJ lock was not held at entry to the
not valid). Following is the text associated with
rebuild routine.
this reason code: ’UNRECOGNIZED TBUF
C0 The caller of SJBRQ attempted to move the DATA’.
SJB to a different job communication queue,
F4 A JES2 owned subtask in the NETSERV
but did not hold the SVJ lock.
address space has terminated in such a way
C4 An invalid SAPID pointer was passed in the that the NETSERV address space must come
SSS2 (SAPI, IAZSSS2) SSOB extension. down.
C8 The fields that should be zeroes in the SSS2 F8 The $GETTBUF or $FRETBUF service was
(SAPI, IAZSSS2) SSOB extension were not called from outside a NETSERV or the JES2
zeros. address space. Following is the text associated
with this reason code: ’$FRETBUF CALLED
CC An SJF Request error occurred on an FROM INCORRECT ADDRSPC’ or
GETDS/SAPI request. ’$GETTBUF CALLED FROM INCORRECT
D4 The MVS Cell Pool Service returns a non-zero ADDRSPC’.
return code when JES2 calls the MVS service FC The $GETABLE service has located a table
to process $CPOOL ACTION=GET request. pair in which the JES2 table pointer points to a
Following is the text associated with the reason USER table, or the USER table pointer points
code: ’$CPOOL ACTION=GET FAILED TO to a HASP table, or a dynamic table pointer
ALLOCATE THE CELL’. does not point to a dynamic table. The
D8 The MVS Cell Pool Service returns a non-zero probable cause is either a mismatch of levels
return code when JES2 calls the MVS service of the $MCT macro, or a failure to use the
to process $CPOOL ACTION=FREE request. $PAIR macro to define a table pair. Following
Following is the text associated with the reason is the text associated with this reason code:
code: ’$CPOOL ACTION=FREE FAILED TO ’$GETABLE - INVALID TABLE ENTRY’.
FREE THE CELL’. 100 The NETSERV early init routine (in
DC When processing a PSO SSI request, JES2 HASCNJEX) has been entered more than
discovered that the $PSO control block is in once. Following is the text associated with this
error. Following is the text associated with the reason code: ’MULTIPLE ROUTINE CALLS’.
reason code: ’$PSO NOT VALID’. 104 The length of the message passed to the
E0 An inconsistency was detected between the $NOTIFY service exceeds the maximum length
input parameter list (XMPLIST) supplied to allowed (132 bytes). Following is the text
$XMPOST, and the parameters specified to associated with this reason code:
$XMPOST. Following is the text associated ’INCORRECT NOTIFY MESSAGE LENGTH’.
with the reason code: ’$XMPOST 108 Storage key of the ECB encountered by the
PARAMETER LIST NOT VALID’. $ECBEXIT service is 8 or greater. This implies
E4 An error was encountered removing a element either a bad ECB pointer was passed to
using $FIFODEQ which specified $XECBSRV or an unauthorized user is
ABENDERR=YES. The requested element was attempting to use a service illegally. Following
not found on the chain. Following is the text is the text associated with this reason code:
associated with this reason code: ’FIFODEQ ’$ECBEXIT - UNAUTHORIZED ECB
ElEMENT NOT ON QUEUE’. DETECTED’.
Chapter 2. System Completion Codes 121
0F7
10C JES2 (CJOBVFY service) detected an error in | 140 A recursive call has been detected in module
the parameter list passed to the Security | HASCSISC.
Authorization Facility (SAF) to validate the job.
System action: If an SSI function took the $ERROR,
Following is the text associated with this
the system produces a dump (unless the dump is
reason code: ’JOBVALM PARM LIST ERROR’.
suppressed by dump analysis elimination (DAE)), and
110 JES2 (CJOBVFY service) is validating a job the SSI function’s caller receives a disastrous error
that is to execute locally, however the SAF indication upon return. Otherwise, the system
token returned by JOBVALM is a submitter abnormally ends the program.
token. The job being processed will be purged.
Application Programmer Response: Take one of the
Following is the text associated with this
following actions, depending on the reason code
reason code: ’JOBVALM TOKEN TYPE
associated with this abend. If the application
ERROR’.
programmer response is not specified here, then
114 NJE JOB header passed to CJOBVFY is in contact the IBM Support Center for assistance.
error. Following is the text associated with this
Code Response
reason code: ’CJOBVFY NJE HEADER
ERROR’. 00 Determine whether the task control block
recovery element ($TRE) control block was
118 NJE JOB header corruption detected when
properly addressed, and whether that control
trying to locate the SPOOL offload section.
block has been overlaid.
Following is the text associated with this
reason code: ’NJE JOB HEADER/TRAILER 04 Ensure that you release the lock for one SJB
CORRUPTED’. before you attempt to acquire the lock of
another SJB.
11C ENQ error encountered while attempting to
serialize SPOOL space allocation (TRKCELL 08 Verify that offset 0 of the cell points to a valid
routine, TRACK GROUP ALLOCATION ENQ CCE, and shows that the cell is allocated.
minor name). Following is the text associated
with this reason code: ’TBLOB ENQ ERROR’. 0C Determine why subpool 230 has been
depleted. Correct the error.
120 ENQ error encountered while attempting to
serialize CPOOL build processing (CPBUILD 10 Determine why $CBIO failed while attempting
routine, ’cell_pool_type’ CPOOL EXPAND to write the IOT chain. Refer to z/OS JES2
minor name). Following is the text associated Macros for information about the return codes
with this reason code: ’$CPOOL BUILD ENQ for $CBIO.
FAILED’ or ’$CPOOL EXPAND ENQ FAILED’. 14 Determine why the PDDB cannot be located.
124 JES2 CPOOL GET service detected an update Correct the error. Note that an SSI ESTAE
to a free cell. This update occurred after the recovery program is not active for this abend
cell had been freed. Following is the text because the call to end the job originates from
associated with this reason code: ’STORAGE the HASCHAM assembly module.
DEBUG CHECK FAILED’. 18 Determine whether the save area has been
128 JES2 CPOOL FREE service detected an overlaid; if not, determine whether the caller
alteration to a guard byte past the end of a intended to issue a $RETSAVE macro instead
cell. The user of the cell updated storage and correct any errors found in the $RETSAVE
beyond the end of the cell. Following is the text macro.
associated with this reason code: ’INVALID 1C Ensure that the following conditions are met:
STORAGE REFERENCE’. v The assembly module that issued the $EXIT
12C $NSSTLOK service was called requesting call is assembled with the correct ENVIRON
shared access to a JES2 NSST lock by a parameter on the $MODULE statement.
subtask not known to JES2. Following is the v The FSS address space is fully initialized
text associated with this reason code: before the $EXIT call is attempted.
’INCORRECT $NSSTLOK ENVIRONMENT’. 20 Determine why $CBIO failed while attempting
| 138 A return code of X'18' was returned to JES2 to write the IOT chain. Refer to z/OS JES2
| when attempting to perform an ENQ with the Macros for information about the return codes
| minor name of ’WAITING FOR SPOOL for $CBIO.
| SPACE″. The text is ″TBLOBE ENQ ERROR″. 24 Ensure that the caller holds an SJB lock before
| 13C An error occurred when a JESXCF service to attempting to obtain the $SVJLOK.
| retrieve messages was invoked. The text 28 Determine the caller of the $SJBLOCK routine.
| associated with this reason code is FAILURE Notify your programming support personnel.
| FROM AN JESXCF SERVICE.
122 z/OS V1R10.0 MVS System Codes
0F8 • 0F9
FC Ensure that table pairs have been defined 1. If a logrec data set error record is not written with
correctly. Ensure that all modules referencing the abend, ask the operator to set a SLIP trap to
table pair definitions have been assembled with obtain an SVC dump.
the same level of the $MCT macro. 2. Identify the address space where the abend
104 Ensure that the message passed to the occurred by doing one of the following:
$NOTIFY service is not longer than 132 v In the logrec data set error record, find the
characters. address space identifier (ASID) of the address
space.
124 Determine if the data area being updated was
previously owned by JES2 or by a user exit. v In the system trace, get the ASID from the SVCE
Since the data area itself had been zeroed, it D entry for abend X'0F8'.
may require a search of the System Trace to 3. Use the program status word (PSW) address at the
determine who last owned the data area. time of error to identify the module that abended.
Attempt to determine where the update access v For an installation-provided module, continue
was made and if in IBM code, contact the IBM diagnosis with the module.
Support Center for assistance.
v For an IBM module, continue diagnosis as
128 The data area being freed is the most likely follows:
cause of the error. Ensure that the modules – For reason code X'08', go to step 4.
referencing the data areas have all been – For any other reason code, go to step 5.
assembled with the correct level of macros 4. For reason code X'08', determine which lock was
(including HASCPOOL). If the data area was held by the issuer of the SVC. If you have not
owned and managed by IBM code, contact the already obtained an SVC dump, ask the operator to
IBM Support Center for assistance. set a SLIP trap to obtain an SVC dump. In the
Source: JES2 system trace, look at the SVCE D entry for
completion code X'0F8'. The PSACLHS column
contains the current lock held string at the time of
0F8 the error.
Explanation: The issuer of a Supervisor Call (SVC) Use the PSACLHS field in the prefix save area
instruction was not in the correct mode to issue the (PSA) to determine which lock was held at the time
SVC. A hexadecimal reason code in the RTM2CRC field of error.
of the RTM2WA data area explains the error: 5. Search problem reporting data bases for a fix for the
Code Explanation problem. For reason code X'08', include in the
search argument the name of the lock held, as
04 The issuer was in a mode other than task determined in step 4. If no fix exists, contact the
control block (TCB) mode. IBM Support Center. Provide, if available, the SVC
dump and the logrec data set error record.
08 The issuer held a lock.
Source: Supervisor control
0C The issuer was disabled.
10 The issuer was in cross memory mode.
0F9
14 The issuer had established an enabled,
Explanation: An error occurred when the system
unlocked task (EUT) mode functional recovery
attempted to acquire or release a supervisor request
routine (FRR) by specifying EUT=YES on a
block (SVRB) in order to process a Supervisor Call
SETFRR macro.
(SVC) instruction. This is probably an error in a
18 The issuer was in access register (AR) address program, but not necessarily in the program that
space control mode. This error applies to only abnormally ended. A hexadecimal return code in register
those SVCs that cannot be issued in AR 15 explains the error:
address space control mode.
Code Explanation
1C The issuer is not authorized to use the SVC
00 The local system queue area (LSQA) has been
microcode assist instruction.
exhausted, so that the SVRB space is not
System action: The system abnormally ends the available to honor an SVC instruction in the
program that issued the SVC. The system may write a address space. This problem may be caused
logrec data set error record. by a loop in the program issuing the SVC.
Operator response: If the system programmer asks 04 An SVRB is being freed, but the system cannot
for an SVC dump, set the following SLIP trap: identify it as belonging to the SVRB pool.
SLIP SET,ENABLE,COMP=0F8,END 08 A type 2, 3, or 4 SVC routine exited, but the
System programmer response: Do the following: data in its SVRB in field RBSID was not valid.
Chapter 2. System Completion Codes 123
0FB • 0FD
System action: The system writes a logrec data set
0FC
error record. The system abnormally ends the program
that was running. Explanation: A program referenced data in an
address space other than its home address space. That
For reason code X'08', the system writes a logrec data
address space has either:
set error record. One of the data items recorded in the
VRA is the number of the returning SVC. The system v Incorrect data in its dynamic address translation
does not abnormally terminate the program that was (DAT) tables
running. v An incorrect segment table origin (STO) address
System programmer response: Do the following: This error is probably in the system.
1. For reason code X'00', examine the REGION System action: The system abnormally ends the
parameter on the JCL JOB or EXEC statement for program and ends the address space.
the job. If the REGION parameter allocates too
much private storage, this may be causing a System programmer response: Search problem
shortage of available storage for the LSQA. Reduce reporting data bases for a fix for the problem. If no fix
the value of the REGION parameter. exists, contact the IBM Support Center.
2. For reason code X'04', contact the supervisor Source: Recovery termination manager (RTM)
control component group at the IBM Support Center.
Provide the logrec data set error record.
0FD
3. If the REGION parameter for the job is determined
to be reasonable, a complete SVC dump will be Explanation: The Type 6 SVC routine issued the
needed to diagnose the cause of the abend X'0F9' T6EXIT macro to schedule a cross memory service
reason code X'00.'. Since a SLIP on an abend request block (SRB), but the SRBASCB address is not
X'0F9' with A=SVCD will not produce a complete the same as the current memory address. This is a
SVC dump, and since an abend X'0F9' is nearly probably an error in the SVC routine.
always preceded by either an abend X'878' or
System action: The system abnormally ends the
X'80A', the following two SLIPs should be set to
program that issued the T6EXIT macro. The system
obtain a useful SVC dump.
may write a logrec data set error record.
SLIP SET,C=878,A=SVCD,J=failingjob,END
SLIP SET,C=80A,A=SVCD,J=failingjob,END Operator response: If the system programmer asks
for an SVC dump, set the following SLIP trap:
4. For reason code X'08', the SVC routine must be
updated to not modify the SCB in the SVRB. Report SLIP SET,COMP=0FD,ACTION=SVCD,END
the problem to the owner of the SVC routine. System programmer response: Do the following:
Source: Supervisor control 1. Ask the operator to set a SLIP trap to obtain an
SVC dump.
0FB 2. In the system trace, back up to the *RCVY entry for
abend X'0FD'. Look for an SVC entry, other than
Explanation: A translation exception has occurred. SVC D, prior to the *RCVY entry for this abend. In
The system detected an incorrect value in control the entry, note the address in the PSW ADDR
register 0. column.
System action: The system abnormally ends the 3. Use the address in the PSW to identify the module
program experiencing the error. The system may write a that issued the T6EXIT macro.
logrec data set error record. v For an installation-provided module, continue
Operator response: If the system programmer asks diagnosis with the module.
for an SVC dump, set the following SLIP trap: v For an IBM module, search problem reporting
SLIP SET,COMP=0FB,ACTION=SVCD,END data bases for a fix for the problem. If no fix
exists, contact the component group associated
System programmer response: Search problem with this module at the IBM Support Center.
reporting data bases for a fix for the problem. If no fix Provide the SVC dump and, if available, the
exists, ask the operator to set a SLIP trap to obtain an logrec data set error record.
SVC dump. Contact the IBM Support Center. Provide
the SVC dump and, if available, the logrec data set Source: Supervisor control
error record.
Source: Supervisor control
124 z/OS V1R10.0 MVS System Codes
0FE • 104
System programmer response: If the error recurs
0FE
and the program is not in error, look at the messages in
Explanation: An error was detected while RMF™ was the job log for more information. Search problem
sampling data about the state of the system. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
System action: All RMF measurement collection is
program listing for the job.
terminated. Reinstatement of RMF can be attempted,
and, if successful, RMF continues under the control of Source: Task management
the original options. If reinstatement fails, RMF is
terminated.
102
The system writes an ABEND dump for the failing job
Explanation: During processing of a POST macro, the
step.
system found an incorrect address for an event control
System programmer response: block (ECB).
Obtain the ABEND dump for the failing job step. If the Register 15 contains a hexadecimal reason code that
JCL for the step did not contain a DD statement for an explains the error:
ABEND dump, add one of the following statements and
Code Explanation
run the job step again:
SYSABEND DD statement 00 Incorrect ECB and the linkage from the caller is
SYSMDUMP DD statement through an SVC instruction (LINKAGE=SVC).
SYSUDUMP DD statement
04 Incorrect ECB for a cross memory POST
(XMPOST) macro.
Use a SYSMDUMP DD statement if you plan to analyze
and format the dump with the interactive problem 08 The problem program passed an incorrect ECB
control system (IPCS). address.
10 An ECB address of 0 was specified.
Obtain the logrec data set error record.
System action: The system abnormally ends the
Search problem reporting data bases for a fix for the program that issued the POST macro.
problem. If no fix exists, report the problem to the IBM
Application Programmer Response: Ensure that the
Support Center.
specified ECB address is a valid virtual storage address
Source: Resource Measurement Facility (RMF) and that the address was not incorrectly modified. Also,
ensure that the program issuing the POST macro has a
storage protection key that allows it to update the ECB.
0FF
Correct the error. Run the job again.
Explanation: The system encountered an error while
System programmer response: If the error recurs
processing a DATOFF Move Long (MVCL) instruction. A
and the program is not in error, look at the messages in
hexadecimal reason code in register 15 explains the
the job log for more information. Search problem
error:
reporting data bases for a fix for the problem. If no fix
Code Explanation exists, contact the IBM Support Center. Provide the
program listing for the job.
04 Index given to DATOFF was out of range.
Source: Task management
System action: The system abnormally ends the
program that issued the instruction.
104
Source: Supervisor control
Explanation: An error occurred when the system tried
to process an EU, LU, or VU form of the GETMAIN
101 macro. The GETMAIN requested virtual storage that
Explanation: During processing of a WAIT macro, the requires more central storage than is available. A
system found that the problem program specified more reason code in the SDWACRC field of the system
events than there were event control blocks (ECB). diagnostic work area (SDWA) explains the error:
System action: The system abnormally ends the Code Explanation
program that issued the WAIT macro. 04 There is not enough central storage available
Application Programmer Response: Change the to back a request for space in a system queue
events specified to less than or equal to the number of area (SQA) subpool.
ECBs. If the specification was correct, ensure that it 08 There is not enough central storage available
was not incorrectly modified. Correct the error. Run the
job again.
Chapter 2. System Completion Codes 125
106
to back a request for space in a fixed common 0D The control program found an incorrect record
service area (CSA) subpool. type in the load module.
0C There is not enough central storage available 0E The control program found an incorrect
to back a request for space in a local system address in the load module.
queue area (LSQA) subpool.
Code Explanation
1C The system could not satisfy a request for an
20 Error converting TTR. One of the
LSQA subpool. The page table for the segment
following occurred:
describing the area to be obtained was paged
out. v A job opened a data set with
DISP=SHR, and another job
20 The system could not satisfy a request for an updates the data set causing the
authorized private area subpool. The page extents in the data set to increase.
table for the segment describing the area to be
v An error occurred in an application
obtained was paged out.
program, for example, while
System action: The system issues message IEA705I. retrieving a directory entry using
The system abnormally ends the current task. build link-list (BLDL) from one DCB
and passing that entry and a
Application Programmer Response: Ensure that the
different DCB to the LOAD or LINK
calling program is not requesting too much central
macro.
storage.
24 Block is outside of the module.
If the system issues this abend frequently, notify the
system programmer. 28 The address constant location is
incorrect.
System programmer response: See installation
procedures to increase the central storage 0F Either an uncorrectable I/O error occurred, or
requirements. an error in the load module caused the channel
program to fail. See the accompanying IEW
Source: Virtual storage manager (VSM)
message for a description of the data set error.
Code Explanation
106
40 I/O error on a PDS.
Explanation: An error occurred during processing of a
LINK(X), LOAD, ATTACH(X), or XCTL(X) macro. 44 Error on a virtual DS.
An error was detected by the control program when it 48 Seek address outside extent.
attempted to fetch the requested program into virtual
4C Possible program-controlled interrupt
storage. The return code in register 15 identifies the
(PCI) logic error.
error; see accompanying messages CSV031I and
CSV028I to determine the reason code. For 10 The control program detected a relocation error
PMLOADER internal errors not listed, contact the IBM in the load module.
Support Center.
28 Internal error occurred during fetch processing.
Code Explanation
System action: The task is ended unless ERRET was
0B An error occurred during FETCH processing or specified on the macro. The system issues message
in one of the routines that gets control as a CSV011I.
result of FETCH processing.
Operator response: Notify the system programmer.
0C Not enough storage was available for FETCH
to get storage for the module or control blocks. Application Programmer Response: For a return
code of:
Code Explanation v X'0C' with a reason code of:
04 No storage for DATD. – X'14', increase the region size.
08 No storage for data extent block – X'04', X'08', or X'10' try decreasing the region
(DEB). size. If the problem recurs, notify the system
programmer.
0C No storage for I/O supervisor block
v X'0D', or X'0E' (reason code of X'24' or X'28'), ensure
(IOSB).
that the load module was not altered so that it is no
10 No storage for EXLIST. longer valid. If the load module is valid, then notify
the system programmer.
14 No storage for module.
18 Unable to fix storage.
126 z/OS V1R10.0 MVS System Codes
10A • 10E
v X'0E' (reason code of X'20'), if the error occurred Source: Virtual storage manager (VSM)
because a different job updated the data set extents,
then restart the job so that the extent list is updated
10B
(if the error occurred with the LINKLIST, the system
must be IPLed to fix the problem). Explanation: Timer supervision found an error on the
input parameters for the TIME macro.
System programmer response: For a return code of:
v X'0F', resubmit the job. Then have the operator enter System action: The system takes an SVC dump.
a START GTF command specifying tape output, System programmer response: Use the program
MODE=EXT and TIME=YES. Have the operator reply status word (PSW) address in the CLK entry to identify
TRACE=IO in response to message AHL100A. the caller. Do one of the following:
Format the output with the IPCS GTFDATA v If the caller is provided by the installation, check the
subcommand. parameters on the TIME macro. If MIC or STCK was
v X'0B', X'0D', X'0E' (reason code of X'24' or X'28'), specified, the area specified by the address must
X'28', or if the problem persists, search problem have the caller’s storage protect key.
reporting data bases for a fix for the problem. If no fix v If the caller is provided by IBM, search problem
exists, contact the IBM Support Center. reporting data bases for a fix for the problem.
Source: Contents supervision (CSV) v If the PSW does not contain the caller’s address,
contact the IBM Support Center.
10A Source: Timer supervision
Explanation: An error occurred when the system tried
to process an R form of the GETMAIN macro. The 10D
GETMAIN requested virtual storage that required more
central storage than is available. A reason code in the Explanation: A job step task abnormally ended, but it
SDWACRC field of the system diagnostic work area had a subtask with a status of step must complete
(SDWA) explains the error: (MC). This completion code is found only in the job step
task.
Code Explanation
System action: The system abnormally ends the
04 There is not enough central storage available subtask. The system sends messages about the
to back a request for space in a system queue problem to the job log.
area (SQA) subpool.
System programmer response: Find the abend code
08 There is not enough central storage available for the task that attached the abended subtask in:
to back a request for space in a fixed common v Messages in the job log
service area (CSA) subpool.
v The logrec data set error record
0C There is not enough central storage available v The TCBCMP field of the task control block (TCB) for
to back a request for space in a local system the attaching task, if a dump is available
queue area (LSQA) subpool.
Diagnose the original abend in the attaching task.
1C The system could not satisfy a request for an
LSQA subpool. The page table for the segment Source: Recovery termination manager (RTM)
describing the area to be obtained was paged
out.
10E
20 The system could not satisfy a request for an
Explanation: A program issued a SPIE macro. The
authorized private area subpool. The page
macro specified an incorrect address for the program
table for the segment describing the area to be
interruption control area (PICA).
obtained was paged out.
System action: The system sends messages about
System action: The system issues message IEA705I.
the problem to the job log. The system abends the
The system abnormally ends the current task.
program.
Application Programmer Response: Ensure that the
Operator response: If the system programmer asks
calling program is not requesting too much central
for an SVC dump, set the following SLIP trap:
storage.
SLIP SET,COMP=10E,ACTION=SVCD,END
If the system issues this abend frequently, notify the
system programmer. System programmer response: Do the following:
v If the program is installation-provided code, correct
System programmer response: See installation
the PICA address.
procedures to increase the central storage
requirements.
Chapter 2. System Completion Codes 127
110 • 117
v If the program is IBM code, search problem reporting
113
data bases for a problem fix. If no fix exists, contact
the IBM Support Center. Provide: Explanation: The error occurred during processing of
– Messages from the job log an OPEN macro instruction or an OPEN macro
– The ABEND or SVC dump instruction with a TYPE=J operand. This system
– The assembly listing for the job completion code is accompanied by message IEC142I.
– The JCL for the job Refer to the explanation of message IEC142I for
– The program listing for the job complete information about the task that was ended and
for an explanation of the return code (rc in the message
Source: Recovery termination manager (RTM)
text) in register 15.
Application Programmer Response: Respond as
110
indicated for message IEC142I.
Explanation: While the system was processing a
System programmer response: If the error recurs
PURGE macro, an error occurred when the system tried
and the program is not in error, look at the messages in
to process the parameter list for the macro.
the job log for more information. Search problem
System action: The system ends the program that reporting data bases for a fix for the problem. If no fix
issued the PURGE macro. exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
Application Programmer Response: Correct the
pointer to the purge parameter list in the PURGE Source: DFSMSdfp
macro.
Source: Input/output supervisor (IOS) 115
Explanation: The error occurred during the processing
112 of SVC 21 (STOW). The DCB did not point to a valid
DEB, or the DEB did not point back to the DCB.
Explanation: Incorrect input was passed to SVC 18 by
the BLDL or FIND macro instruction. This system System action: An unsuccessful attempt was made to
completion code is accompanied by message IEC908I. invoke the STOW task recovery routine.
Refer to the explanation of message IEC908I for
Application Programmer Response: Verify that
complete information about the task that was ended and
register 1 contained the correct DCB address prior to
for an explanation of the return code found in register
issuing SVC 21, and that the DCB has not been
15.
overlaid since it was opened.
System action: For return codes 13 and 14, the DCB
System programmer response: If the error recurs
was written to the GTF trace data set.
and the program is not in error, look at the messages in
Operator response: Start a generalized trace facility the job log for more information. Search problem
(GTF) trace, and re-create the problem. Reply to reporting data bases for a fix for the problem. If no fix
message AHL100A with: exists, contact the IBM Support Center. Provide the JCL
TRACE=SYS,USR,SLIP and the program listing for the job.
Source: DFSMSdfp
On the DD statement for the data set in error, specify:
DCB=DIAGNS=TRACE 117
Application Programmer Response: Correct the Explanation: The error occurred during processing of
BLDL or FIND macro instruction. For return codes 03, a BSAM CLOSE macro instruction with a TYPE=T
13, 04, and 14, make sure that the DCB is not being operand. This system completion code is accompanied
overlaid, in particular, the fields DCBEBAD and by message IEC218I. Refer to the explanation of
DCBPOINT. Recompile the program and run the job message IEC218I for complete information about the
step again. task that was ended and for an explanation of the return
System programmer response: If the error recurs code (rc in the message text) in register 15.
and the program is not in error, look at the messages in Application Programmer Response: Respond as
the job log for more information. Search problem indicated for message IEC218I.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL System programmer response: If the error recurs
and the program listing for the job. and the program is not in error, look at the messages in
the job log for more information. Search problem
Source: DFSMSdfp reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
128 z/OS V1R10.0 MVS System Codes
118 • 128
Source: DFSMSdfp
11A
Explanation: The error occurred trying to store into a
118
user-supplied OS/VS CAMLST work area.
Explanation: Incorrect parameters were passed to
System action: SVC 26 received a protection check
DEVTYPE (SVC 24). This system completion code is
because the protect key of the supplied work area did
accompanied by message IEC912I. Refer to the
not match the user’s protect key.
explanation of message IEC912I for complete
information about the task that was ended and for an Application Programmer Response: Correct the
explanation of the return code found in register 15. pointer in the OS/VS LOCATE parameter list to the
LOCATE work area, and run the job step again.
Application Programmer Response: Correct the
DEVTYPE macro instruction, recompile the program, System programmer response: If the error recurs
and rerun the job step. and the program is not in error, look at the messages in
the job log for more information. Search problem
System programmer response: If the error recurs
reporting data bases for a fix for the problem. If no fix
and the program is not in error, look at the messages in
exists, contact the IBM Support Center. Provide the JCL
the job log for more information. Search problem
and the program listing for the job.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL Source: DFSMSdfp
and the program listing for the job.
Source: DFSMSdfp 121
Explanation: A module tried to stop I/O activity by
119 issuing the IOHALT macro with the low order bit of
register 1 off.
Explanation: Incorrect input was passed to SVC 25.
This system completion code is accompanied by System action: The system abnormally ends the
message IEC914I. Refer to the explanation of message program that issued the IOHALT macro.
IEC914I for complete information about the task that
Application Programmer Response: Change the
was ended and for an explanation of the return code
program that issued the IOHALT macro so it sets the
found in register 15.
low order bit of register 1 on.
System action: For return codes 12 and 13, the DCB
System programmer response: If the IOHALT macro
is written to the GTF trace data set. For return code 14,
is issued within the system code, search problem
both the DCB and IOB are written.
reporting data bases for a fix for the problem. If no fix
Operator response: Start a generalized trace facility exists, contact the IBM Support Center.
(GTF) trace, and re-create the problem. Reply to
Source: Input/output supervisor (IOS)
message AHL100A with:
TRACE=SYS,USR,SLIP
122
On the DD statement for the data set in error, specify: Explanation: The operator canceled the job and
DCB=DIAGNS=TRACE requested a dump.
Application Programmer Response: Make sure that System action: The system ends the job. The system
your program does not overlay the DCB and IOB fields writes a dump to the data set described by the
described by the error code. Correct the error, and rerun SYSABEND, SYSMDUMP or SYSUDUMP DD
the job step. statement in the canceled job step.
System programmer response: If the error recurs Application Programmer Response: Find out why
and the program is not in error, look at the messages in the operator canceled the job. Correct the error(s).
the job log for more information. Search problem Resubmit the job.
reporting data bases for a fix for the problem. If no fix
Source: Master scheduler
exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
128
Source: DFSMSdfp
Explanation: During processing of an EXTRACT
macro, the system found an incorrect address for the
list to hold the requester fields. The beginning address
for the list did not define a fullword boundary, or the list
did not begin and end within the storage assigned to
the job step.
Chapter 2. System Completion Codes 129
12A • 12E
The first operand of the macro specifies the beginning
12C
address of the list. The number of fields requested
determines the length of the list. Explanation: During processing of a CHAP macro, the
system found an incorrect address for the task control
System action: The system abnormally ends the
block (TCB) for the subtask whose priority was to be
program that issued the EXTRACT macro.
changed. The second operand of a CHAP macro points
Application Programmer Response: Determine if the to a fullword that contains the TCB address.
first operand of the macro was specified correctly or if
The address was incorrect for one of the following
program errors had incorrectly modified the EXTRACT
reasons:
macro expansion. Correct the error. Run the job again.
v It was not a valid TCB address.
System programmer response: If the error recurs
v The valid TCB at the address was not associated
and the program is not in error, look at the messages in
with a subtask of the task issuing the macro.
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix v It was not a multiple of 4.
exists, contact the IBM Support Center. Provide the v The valid task has abnormally ended.
source program listing for the job.
System action: The system abnormally ends the
Source: Task management program that issued the CHAP macro.
Application Programmer Response: Change the
12A address specification. Ensure that it and the TCB were
not incorrectly modified by the problem program.
Explanation: During processing of an ATTACH macro,
Correct the error. Run the job again.
the system found an error. In a GSPV or GSPL
operand, the macro specified that a subpool was to be System programmer response: If the error recurs
given to the subtask being created. and the program is not in error, look at the messages in
the job log for more information. Search problem
Register 15 contains a hexadecimal reason code that
reporting data bases for a fix for the problem. If no fix
explains the error:
exists, contact the IBM Support Center. Provide the
Code Explanation source program listing for the job.
00 The attaching task owned the subpool, but had Source: Task management
previously shared it with other subtasks
through SHSPV and/or SHSPL operands. A
12D
task cannot give an owned subpool to a
subtask if that task shared the subpool with Explanation: A program requested an overlay. When
other subtasks. trying to answer the request, the overlay supervisor
found that words 3 and 4 of the overlay segment table
04 The specified subpool contains data-in-virtual
are incorrect.
(DIV) mapped storage; such a subpool cannot
be specified with GSPV or GSPL. The overlay segment table is used by the overlay
supervisor; it resides in the load module and is in the
08 The specified subpool contains storage that
same storage protection key as the application program.
had been specified on the IARSUBSP macro
with the IDENTIFY parameter, and the storage
Note: Overlay programs run only in 24-bit addressing
is eligible to be assigned to a subspace.
mode, not in 31-bit addressing mode.
Ownership of a subpool eligible to be assigned
to a subspace cannot be passed to an System action: The system abnormally ends the
attached subtask. program that requested the overlay. The system writes
an ABEND dump, if a dump DD statement is provided.
System action: The system abnormally ends the
program that issued the ATTACH macro. Application Programmer Response: Check the
program for errors that caused the overlay segment
Application Programmer Response: Change the
table to be incorrectly modified. Correct the errors; then
ATTACH macro to specify the subpool in an SHSPV or
assemble, link edit, and run the program again.
SHSPL operand. Correct the error. Run the job again.
Source: Overlay supervisor
System programmer response: If the error recurs
and the program is not in error, look at the messages in
the job log for more information. Search problem 12E
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the Explanation: A program issued a TTIMER macro with
source program listing for the job. incorrect parameters.
Source: Task management System programmer response: Use the program
130 z/OS V1R10.0 MVS System Codes
12F • 130
status word (PSW) address in the CLK entry to identify v The virtual subpools that contain the parameter list
the caller. Do one of the following: passed to STIMER
v If the caller is provided by the installation, check the Application Programmer Response: Depending on
parameters on the TIME macro. If MIC or STCK was the reason code, one of the following:
specified, the area specified by the address must
have the caller’s storage protect key. Code Explanation
v If the caller is provided by IBM, search problem 00 Check the spelling of the data area name on
reporting data bases for a fix for the problem. the STIMER request.
v If the PSW does not contain the caller’s address, 04 Do not specify the TASK parameter with the
contact the IBM Support Center. GMT and TOD parameters on the STIMER
Source: Timer supervision request.
0C Change the value for the GMT and/or TOD
12F parameter(s) to one that is less than 2400.
Explanation: A program issued an STIMER macro 14 Check that a program running in 31-bit
with incorrect parameters. A reason code in register 15 addressing mode uses the MVS/SP Version 2
explains the error: or later version of the STIMER macro.
Code Explanation 10 Change the parameter address so it is in the
caller’s addressable storage.
00 The system could not find a data area that was
specified on a parameter for an STIMER 28 Ensure that the specified time interval is
request. correct.
04 The Coordinated universal time (UTC) or local Source: Timer supervision
time of day (LT or TOD) parameter was
specified for a TASK type STIMER request. 130
0C The value for the Coordinated universal time Explanation: Global resource serialization found an
(UTC) or local time of day (LT or TOD) error during processing of the DEQ macro instruction.
parameter was greater than 24:00:00.00.
The DEQ macro instruction specified a resource not
10 The STIMER service routine cannot access the previously specified by an ENQ macro instruction under
storage containing the user-specified the same task. In other words, the program was
parameters for the STIMER macro. attempting to release a resource that was not previously
14 The STIMER service routine received an requested. The DEQ macro instruction did not specify a
STIMER macro parameter that was not valid. RET=HAVE operand.
For example, a program running in 31-bit System action: The system issued an ABEND dump.
addressing mode is not using the MVS/SP
Version 2 or later version of the STIMER Application Programmer Response: Do one of the
macro. following:
v Check the DEQ macro instruction for incorrect qname
28 The requested time interval was too large. One or rname operands
of these situations occurred: For TASK type v Specify RET=HAVE in the DEQ macro instruction
requests, the requested MICVL time interval v Add an ENQ macro instruction for the same resource
was larger than X'7FFFFFFFFFFFFFFF'. For before the DEQ macro instruction
REAL/WAIT type requests, the requested time
interval (BINTVL, DINTVL, MICVL, or Then recompile and rerun the program.
TUINTVL) added to the current TOD clock
contents would have exceeded If the problem persists, do the following:
X'FFFFFFFFFFFFFFFF' (a value that would 1. Obtain the address of the DEQ parameter list from
expire on September 17, 2042). A value register 1 in the UNIQUE-3 column of the SVC 30 or
greater than X'7FFFFFFF' was specified for SVC 38 entry in the system trace.
BINTVL.
2. Check the parameter list against the SVC 30 or 38
System action: The STIMER routine produces a mapping. When analyzing the parameter list,
tailored dump that provides the following information: remember that the unit control block (UCB) pointer,
v The control blocks associated with the task that if present, is the address of a field that, in turn,
issued the STIMER request contains the address of the UCB.
v The register contents for the task that issued the If the parameter list contains incorrect data, continue
STIMER request diagnosis in the program that issued the macro.
Chapter 2. System Completion Codes 131
133 • 138
System programmer response: If the problem System action: Message IEC903I is issued.
persists, search problem reporting data bases for a fix
Operator response: Notify the system programmer.
for the problem. If no fix exists, contact the IBM Support
Center. Provide the ABEND dump. System programmer response: If the error recurs
and the program is not in error, search problem
Source: Global resource serialization
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
133 SYSOUT output for the job and all printed output and
output data sets related to the problem.
Explanation: An unauthorized program requested an
SVC dump. Source: DFSMSdfp
To request an SVC dump through an SDUMP macro
(SVC 51), the program must be one of the following: 137
v Authorized by the authorized program facility (APF) Explanation: The error occurred at an end-of-volume
v In storage key 0-7 on a magnetic tape. This system completion code is
accompanied by message IEC022I. Refer to the
To request an SVC dump by a branch entry, the explanation of message IEC022I for complete
program must be one of the following: information about the task that was ended and for an
v In storage key 0, supervisor state. explanation of the return code (rc in the message text)
in register 15.
v One of the following must be true:
– The caller is in SRB mode. Application Programmer Response: Respond as
indicated for message IEC022I.
– The caller owns a lock.
– The caller is disabled and has a PSASUPER bit System programmer response: If the error recurs
set on. and the program is not in error, look at the messages in
the job log for more information. Search problem
– The caller is in enabled unlocked task (EUT) reporting data bases for a fix for the problem. If no fix
mode. That is, the caller specified EUT=YES for exists, contact the IBM Support Center. Provide the JCL
the SETFRR macro. and the program listing for the job.
Generally, those modules that cannot issue Supervisor Source: DFSMSdfp
Call (SVC) instructions can do a branch entry to request
an SVC dump. 138
System action: The system abnormally ends the Explanation: Global resource serialization
program. If a recovery routine is available, it is given encountered an error occurred during processing of an
control. SVC dump processing issues message ENQ macro. One of the following is true:
IEA911E or IEA611I. This message indicates whether
the dump is complete or partial. 1. One ENQ macro instruction was issued for a list of
resources. The same resource appears more than
System programmer response: For an unauthorized once in the list.
program, request an ABEND dump. If the branch entry 2. Two ENQ macro instructions were issued for the
is being used incorrectly, correct the error or use an same resource in the same task without an
SDUMP macro. intervening DEQ macro instruction to release the
If the problem persists or is in an IBM-provided resource. The second ENQ macro instruction did not
program, search problem reporting data bases for a fix specify TEST, USE, or HAVE in its RET operand.
for the problem. If no fix exists, contact the IBM Support System action: Processing continues.
Center. Provide the assembly listing and the linkage
editor output for the job. Application Programmer Response:
Source: Dumping services For the first type of error, delete duplicate resources
from the list on the ENQ macro instruction.
135 For the second type of error, do one of the following:
Explanation: An error occurred during the processing v Specify RET=TEST, RET=USE, or RET=HAVE in the
associated with SVC 53, which obtains and releases second ENQ macro instruction
exclusive control of a resource associated with a BDAM v Add a DEQ macro instruction between the two ENQ
data set. The task recovery routine for this SVC macro instructions
determined that all user control blocks required as input v Delete one of the ENQ macro instructions.
to the SVC were in the user’s region and key, hence the
error could not be ascribed to any user control block. If the problem persists, do the following:
132 z/OS V1R10.0 MVS System Codes
139 • 13C
1. Obtain the address of the DEQ parameter list from v The macro specified an EXIT address of 0
register 1 in the UNIQUE-3 column of the SVC 30 or with CT.
SVC 38 entry in the system trace. v The macro specified OV.
2. Check the parameter list against the SVC 30 or 38 v The macro specified an incorrect task
mapping. When analyzing the parameter list, control block (TCB) address, or did not
remember that the unit control block (UCB) pointer, specify a TCB address at all.
if present, is the address of a field that, in turn,
v The program calling the ATTACH macro
contains the address of the UCB.
service routine is not the ATTACH macro.
If the parameter list contains incorrect data, continue
diagnosis in the program that issued the macro. 0C An ESTAE or ESTAEX macro with
BRANCH=YES was issued. One of the
System programmer response: If the problem following errors occurred:
persists, search problem reporting data bases for a fix
v The macro is not running under a supervisor
for the problem. If no fix exists, contact the IBM Support
request block (SVRB).
Center. Provide the ABEND dump.
v The program calling the ESTAE service
Source: Global resource serialization routine is not the ESTAE macro.
v The issuer of the macro did not obtain the
139 local lock.
Explanation: An error occurred during the processing 10 A TOKEN parameter was incorrectly specified
associated with SVC 57, which frees a buffer or extends as follows:
the unscheduled test (via the FREEDBUF macro issued v A program specified the TOKEN parameter
either by the user or the system). The BDAM task on a macro other than the ESTAE macro.
recovery routine for this SVC determined that all user
v An unauthorized program issued an ESTAE
control blocks required as input to the SVC were in the
macro with the TOKEN parameter.
user’s region and key, hence the error could not be
ascribed to any user control block. 14 A STAE macro was issued by a program
running in 31-bit addressing mode (AMODE).
System action: Message IEC905I is issued.
This is not valid.
Operator response: Notify the system programmer.
18 An ESTAE or ESTAEX macro with
System programmer response: If the error recurs CANCEL=NO parameter was issued by a
and the program is not in error, search problem program that:
reporting data bases for a fix for the problem. If no fix v Is not authorized by APF to do so
exists, contact the IBM Support Center. Provide the v Is not running in key 0 supervisor state
SYSOUT output for the job and all printed output and
System action: The system abnormally ends the
output data sets related to the problem.
program issuing the macro. If a recovery routine is
Source: DFSMSdfp available, RTM gives it control. The system may write
an ABEND dump for the abend if the job step provides
a dump data set. If so, the LSQA dump option is
13C
specified with the ABEND macro.
Explanation: A program issued one of the following
Operator response: If the system programmer asks
macros:
for an SVC dump, set the following SLIP trap:
v ATTACH with an ESTAI parameter
v ATTACHX with an ESTAI parameter SLIP SET,COMP=13C,ACTION=SVCD,END
v ESTAE System programmer response: Do the following:
v ESTAEX
v If an installation-provided program issued the
v STAE
incorrect macro, rewrite the macro or modify the
The macro specified an incorrect value, or the parameter list built by the ESTAE macro.
environment in which the macro was running was For reason code X'10', be sure that the TOKEN
incorrect. parameter is specified only by authorized programs
and only on the ESTAE macro.
A hexadecimal reason code in register 15 explains the
v If it was an IBM program, search problem reporting
error:
data bases for a fix for the problem. If no fix exists,
Code Explanation contact the IBM Support Center. Provide:
– The assembly listing for the job
08 An ATTACH or ATTACHX macro with ESTAI – The ABEND or SVC dump
was issued. One of the following errors
occurred: Source: Recovery termination manager (RTM)
Chapter 2. System Completion Codes 133
13E • 147
13E 145
Explanation: The task that created a subtask issued a Explanation: The error occurred during the processing
DETACH macro for that subtask, specifying STAE=NO, of SVC 69 (BSP). Register 15 contains a return code
before the subtask ended. indicating the cause of the error. See message IEC916I
for a complete description of the possible return codes
This may or may not be an error, depending on the
and their meanings.
intent of the user. Consequently, the system does not
abnormally end the task issuing the DETACH macro. System action: The backspace task recovery routine
has been invoked. If the caller’s DCB or BSAM control
System action: The system abnormally ends the
blocks are in this region, an attempt was made to trace
subtask to force its completion.
them to the SYS1.TRACE data set.
Application Programmer Response: If the subtask
Operator response: Start a generalized trace facility
must complete its processing before being detached,
(GTF) trace, and re-create the problem. Reply to
use an ECB or ETXR operand on the ATTACH macro
message AHL100A with:
that creates the subtask to achieve synchronization.
TRACE=SYS,USR,SLIP
System programmer response: If the error recurs
and the program is not in error, look at the messages in On the DD statement for the data set in error, specify:
the job log for more information. Search problem
DCB=DIAGNS=TRACE
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the Application Programmer Response: Verify that
source program listing for the job. register 1 contained the correct DCB address prior to
issuing BSP and that the DCB has not been overlaid
Source: Task management
since being opened. If the DCB is valid, verify that it
contains the correct IOB and/or ICB addresses and that
13F neither the IOBs and/or ICBs have been overlaid.
Explanation: An error has been detected during System programmer response: If the error recurs
checkpoint restart processing. This completion code is and the program is not in error, look at the messages in
accompanied by message IHJxxxI with the appropriate the job log for more information. Search problem
reason code. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL
System action: The job is abnormally ended, and if a
and the program listing for the job.
SYSABEND statement was included in the job, a dump
is produced. Source: DFSMSdfp
Application Programmer Response: Respond as
indicated in the accompanying message. 147
Source: DFSMSdfp Explanation: A program check or abnormal end
occurred in the Graphics Access Method/System
Product (GAM/SP) buffer management routine,
144
IGC0007A. The error occurred either in GAM/SP or in
Explanation: The error occurred during the processing the operating system.
of SYNADAF, where it was determined that an incorrect
System action: Message GAB260 appears on the
access method code was specified in the high order
system console, identifying the cause of the error and
byte of register 15.
the original system completion code. In addition,
Application Programmer Response: Make sure that GAM/SP writes a record to the logrec data set and
the ACSMETH parameter on the SYNADAF macro produces a dump on the system dump data set.
instruction is correctly coded, or that the high order byte
Application Programmer Response: Do the
of register 15 contains a valid access method code
following:
before issuing SVC 68.
1. Check for messages identifying the cause of the
System programmer response: If the error recurs error. If these are GAM/SP messages, (that is, the
and the program is not in error, look at the messages in message number is of the form ’GABnnn’), they are
the job log for more information. Search problem described in IBM Graphics Access Method/SP:
reporting data bases for a fix for the problem. If no fix Messages and Codes
exists, contact the IBM Support Center. Provide the JCL
2. Perform any corrective actions associated with the
and the program listing for the job.
original system completion code.
Source: DFSMSdfp 3. Get a listing of the system dump.
4. Contact your programming support personnel.
134 z/OS V1R10.0 MVS System Codes
149 • 14C
Source: DFSMSdfp
14B
Explanation: An error occurred in either the Graphics
149
Access Method/System Product (GAM/SP), or the
Explanation: An error occurred in either the Graphics operating system.
Access Method/System Product (GAM/SP), or the
This completion code appears when:
operating system.
1. A program check or abnormal end occurs in the
This completion code appears when: GAM/SP attention inquiry (ATTNINQ) routine,
1. A program check or abnormal end occurs in the IGC0007E.
GAM/SP specify-attention (SPAR) routine,
2. IGC0007E detects an incorrect condition.
IGC0007C.
2. IGC0007C detects an incorrect condition. System action: A message appears on the system
console, accompanied by a reason code identifying the
System action: A message appears on the system
area of processing where the error occurred. In addition,
console, accompanied by a reason code identifying the
GAM/SP writes a record to the logrec data set and
area of processing where the error occurred. In addition,
produces a dump on the system dump data set.
GAM/SP writes a record to the logrec data set and
produces a dump on the system dump data set. Application Programmer Response: Do the
following:
Application Programmer Response: Do the
following: 1. Check for messages identifying the cause of the
error. If these are GAM/SP messages, (that is, the
1. Check for messages identifying the cause of the
message number is of the form ’GABnnn’), they are
error. If these are GAM/SP messages, (that is, the
described in IBM Graphics Access Method/SP:
message number is of the form ’GABnnn’), they are
Messages and Codes.
described in IBM Graphics Access Method/SP:
Messages and Codes. 2. Get a listing of the system dump.
2. Get a listing of the system dump. 3. Contact your programming support personnel.
3. Contact your programming support personnel. Source: DFSMSdfp
Source: DFSMSdfp
14C
14A Explanation: An error occurred in the system
environmental recording (LOGREC) component.
Explanation: An error occurred in either the Graphics
Access Method/System Product (GAM/SP), or the Register 15 contains a hexadecimal reason code that
operating system. explains the error:
This completion code appears when: Code Explanation
1. A program check or abnormal end occurs in the
01 An incorrect input request to build a logrec
GAM/SP delete-attention (DAR) routine, IGC0007D.
data set record was specified.
2. IGC0007D detects an incorrect condition.
10 The name/token create service returned an
System action: A message appears on the system
unexpected return code.
console, accompanied by a reason code identifying the
area of processing where the error occurred. In addition, 11 An attempt to load module IEANTRT failed.
GAM/SP writes a record to the logrec data set and
produces a dump on the system dump data set. 12 The ENFREQ signal event returned an
unexpected return code.
Application Programmer Response: Do the
following: 13 The ENF 49 parameter area storage obtain
request returned an error return code.
1. Check for messages identifying the cause of the
error. If these are GAM/SP messages, (that is, the 20 The ENFREQ event code 48 listen request
message number is of the form ’GABnnn’), they are returned an unexpected return code.
described in IBM Graphics Access Method/SP:
21 The ENFREQ event code 36 listen request
Messages and Codes.
returned an unexpected return code.
2. Get a listing of the system dump.
30 The input parameter list, IXGENF, is not valid.
3. Contact your programming support personnel.
31 An error occurred during a storage obtain
Source: DFSMSdfp
request for an IFBLISCB element.
38 The input parameter list, IFBENF36, is not
valid.
Chapter 2. System Completion Codes 135
14F
39 Storage could not be obtained for the An STOP. You must issue the STATUS macro with
record. the START option before issuing another
STATUS STOP.
40 An IXGSXCMP validation error occurred.
18 The input mask you specified on the STATUS
41 Unable to obtain storage (IFBSXCB).
SET,SD invocation set TCBSTPP. This bit can
42 Unable to obtain storage (IFBSXCBG). only be set by specifying STATUS STOP.
43 Unable to obtain storage for log block area. 1C The mask you specified on the STATUS
SET,ND invocation set TCBSTP. This bit can
44 The OPEN data area validation failed. only be set by specifying STATUS SET,MC or
45 The CLOSE data area validation failed. STATUS SET,MC,STEP.
46 The unallocation data area validation failed. 20 A routine running under a service request block
(SRB) cannot use a STATUS macro to set a
47 An error occurred on browse options. step nondispatchable.
50 This event is unsupported. 24 In the parameter list on a SET or RESET
51 An error occurred accessing IFBSXCB or request, the caller specified an incorrect
IFBSXCBG. address for a task control block (TCB).
System action: The system writes a record to logrec 28 The caller does not hold a needed local lock.
and requests a dump. Processing continues. 2C The caller does not hold a needed local lock.
System programmer response: Search problem 30 The specified TCB did not pass an acronym
reporting data bases for a fix for the problem. If no fix check. The TCB was probably overlaid or
exists, contact the IBM Support Center. Provide the incorrect.
dump, logrec data set and SYSLOG.
34 The mask of nondispatchability bits specified
Note, for reason code X'10' and X'11', the system could with the SD parameter includes the
not establish the DSNLOGREC name/token, so the TCBSRBND bit. This nondispatchability bit can
name of the logrec data set cannot be retrieved using be set only by specifying STATUS STOP,SRB.
the name/token retrieve service.
38 The STATUS macro specified an incorrect
Source: System Environmental Recording (LOGREC) function code.
3C A program issuing either STATUS
14F SET,MC,PROCESS or STATUS
Explanation: During processing of a STATUS macro, RESET,MC,PROCESS was not running in task
the system found an error. mode. The calling program must be running in
task mode.
Register 15 contains a hexadecimal reason code that
explains the error: 44 The input mask you specified on the STATUS
SET,ND invocation, set the TCBPNDSP bit.
Code Explanation The caller can not set TCBPNDSP.
04 The STATUS macro specified an incorrect 48 A routine running under a service request block
function code. Register 2 contains the function (SRB) cannot use a STATUS macro for the
code. requested function.
08 Only a program in supervisor state with PSW 4C You specified an input address space identifier
key 0-7 can request the specified STATUS (ASID) or enclave token on a STATUS
function. invocation that is not valid.
0C You specified an address space identifier 50 The input TCB specified on a STATUS STOP
(ASID) for the STATUS STOP function. The or STATUS START invocation was the caller’s
ASID parameter is valid only on the STATUS TCB. The caller cannot perform this operation
START function. on itself.
10 You issued the STATUS macro with the must 54 A STATUS invocation to set a caller’s
complete (MC) parameter, but you had already nondispatchability bit was invoked using SVC.
specified the MC parameter on a previous
invocation. You must issue the STATUS macro 58 STATUS STOP,SRB was invoked, but had
with the RESET,MC,STEP parameter before been invoked previously. Invoke STATUS
issuing another SET,MC,STEP. START,SRB before invoking STATUS
STOP,SRB again.
14 You issued a STATUS macro with the STOP
option, but you had already issued a STATUS 5C The system detected a possible overlay of a
136 z/OS V1R10.0 MVS System Codes
150 • 157
TCB field for a task that is the target of a
153
STATUS macro request.
Explanation: An error occurred while system
60 The input TCB specified on a STATUS
management facilities (SMF) processed a record. SMF
SET,ND,E or STATUS SET,SD,E invocation
was unable to handle the new record because of buffer
was the caller’s TCB. The caller cannot
contention.
perform this operation on itself.
System action: The system abnormally ends SMF
System action: The system abnormally ends the
processing. The system requests an SVC dump.
program that issued the STATUS macro.
System programmer response: Search problem
Application Programmer Response: Correct the
reporting data bases for a fix for the problem. If no fix
error. Run the job again.
exists, contact the IBM Support Center.
System programmer response: If the error recurs
Source: System Management Facilities (SMF)
and the program is not in error, look at the messages in
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix 157
exists, contact the IBM Support Center. Provide the
Explanation: An error occurred when the system was
program listing for the job.
processing a DOM macro.
Source: Task management
Register 15 contains a hexadecimal error code in the
format xxxxyyyy. The fields in this error code are the
| 150 following:
| Explanation: A non-recoverable System REXX error xxxx This halfword is for IBM internal use only.
| was encountered.
yyyy This halfword is the unique reason code
| Code Explanation identifier. Only yyyy is listed below.
| xxxx0401
The following are the yyyy values and their meanings:
| During recovery processing, a key System
| REXX control block was found to be incorrect Code Explanation
| System action: The AXR address space is 0004 The caller passed an incorrect value in register
| terminated. 0.
| Application Programmer Response: Contact the | 0008 Either caller was not a task in the same job
| System Programmer. | step and address space as the issuer of the
| WTOR macro that created the message to be
| System programmer response: Contact IBM service.
| deleted, or the caller was not in key 0-7 or APF
| Source: System REXX | authorized.
000C A program check occurred while the system
151 was verifying that the caller could access each
byte of a multiple DOM parameter list.
Explanation: The error occurred during the processing
of SETPRT. The parameter list whose address was | 0010 An unauthorized caller tried to delete a WTO
passed to SETPRT in register 1 was not in the user’s | message that was not created by the same
region. | task in the same address space.
System action: Message IEC918I is issued. 0014 The entry was by a branch, but the caller is not
authorized.
Application Programmer Response: Make sure that
the SETPRT macro instruction is correctly coded. 0018 An unauthorized caller tried to delete a
Correct the error and rerun the job step. message that was issued on another system.
System programmer response: If the error recurs yy1C The system could not obtain needed storage.
and the program is not in error, look at the messages in The return code from the STORAGE service is
the job log for more information. Search problem found in the yy field.
reporting data bases for a fix for the problem. If no fix
| yy40 A recovery environment could not be
exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
| established. The return code from the ESTAE
| macro is found in the yy field.
Source: DFSMSdfp
0050 A DOMCBLK request specified an invalid
DOMC length.
Chapter 2. System Completion Codes 137
15B • 15F
0051 A failure occurred when broadcasting the DOM more information. Search problem reporting data bases
to the sysplex. for a fix for the problem. If no fix exists, contact the IBM
Support Center.
0052 A failure occurred when attempting to DOM a
message found in the parking lot. Source: Execute channel program (EXCP)
| yy53 A failure occurred in the data block create
| routine. The return code from the data block 15D
| create routine is found in the yy field.
Explanation: User specified an incorrect data area to
Fyyy An internal processing error occurred. The yyy SVC 93 (TGET/TPUT).
contains the abend code of the failure.
System action: The user is abnormally ended and
System action: The system ignores the DOM macro. processing continues.
The DOM parameter list and the failing message
Application Programmer Response: Supply a data
identifier are shown in the dump. The system ignores
area for access by the program invoking SVC 93. A
any other message identifiers in the parameter list.
TPUT request requires read access, a TGET request
Application Programmer Response: Ensure that the requires write access.
correct message identifier is being used in the DOM
System programmer response: If the error recurs
macro. Ensure that the DOM issuer is in the same job
and the program is not in error, search problem
step as the WTOR issuer.
reporting data bases for a fix for the problem. If no fix
System programmer response: For a yy53 reason exists, contact the IBM Support Center. Provide the
code, search problem reporting data bases for a fix for program listing for the job.
the problem. If no fix exists, contact the IBM Support
Source: VTAM, or TSO/E if Session Manager is being
Center with the reason code.
used.
| Source: Console services
15F
15B
Explanation: A SYSEVENT macro incorrectly invoked
Explanation: A VOLSTAT macro can be issued only the system resources manager (SRM). Register 15
by an authorized program. While processing a contains a hexadecimal reason code that explains the
VOLSTAT macro, the system determined that the error:
issuing program was not:
Code Explanation
v An authorized program facility (APF) authorized
program 04 The address space identifier (ASID), the
SYSEVENT code, or an input parameter was
v In supervisor state
incorrect.
v In storage protection key 0 through 7
08 Program was not authorized to issue the
System action: The system abnormally ends the SYSEVENT.
program that issued the VOLSTAT macro.
0C A page fault occurred when the system
Application Programmer Response: Correct the referred to a data area assumed to be fixed.
program so that an authorized program issues the
VOLSTAT macro. 10 A protection check occurred; the program
issuing the macro did not have the correct
Source: DFSMSdfp storage key for storing in the parameter data
area.
15C 14 A program held the SRM lock before the
Explanation: Execute channel program (EXCP) SYSEVENT macro invoked SRM.
processing found that the program issuing an SVC 92 18 The SRM recovery routine converts this reason
request was not running in supervisor state. code to completion code X'25F'.
System action: The system abnormally ends the 1C A SYSEVENT TRANSWAP or REQSWAP with
current task. an event control block (ECB) was issued when
Application Programmer Response: Ensure that the the maximum allowed number of pending
program is authorized to issue TCBEXCP or the EXCP TRANSWAPs or REQSWAPs with ECBs had
macro. already been reached.
System programmer response: If the error recurs 20 An SRM stack overflow was detected.
and the program issuing the XDAP or EXCP macro is 24 The SRM entry point did not receive an SRM
not in error, look at the messages in the job log for recovery parameter area (RRPA).
138 z/OS V1R10.0 MVS System Codes
169 • 16D
28 An unexpected condition occurred while (GTF) trace, and re-create the problem. Reply to
enforcing a defined capacity limit. message AHL100A with:
One reason is that the partition weight is too TRACE=SYS,USR,SLIP
high relative to the defined capacity limit. As a
result, the phantom weight SRM tries to assign On the DD statement for the data set in error, specify:
is not valid. If this is the case, check the DCB=DIAGNS=TRACE
phantom weight assigned to the LPAR. The
phantom weight is calculated based on the Application Programmer Response: Make sure that
defined LPAR capacity, the total CEC capacity the IMGLIB CLOSE macro instruction is correctly coded.
and the partition weight. The value specified for Make sure that the DCB address passed to IMGLIB is
a phantom weight should not exceed 1000 the same address returned to your program by a
times the number of active LPARs. For more previous IMGLIB OPEN, and that your program has not
information about how to calculate the phantom issued a prior IMGLIB CLOSE specifying this DCB
weight, see Workload Management address. Correct the error and rerun the job step.
Participants, Workload Management and System programmer response: If the error recurs
Workload Licence Charges in z/OS MVS and the program is not in error, look at the messages in
Planning: Workload Management. the job log for more information. Search problem
If the phantom weight is correct, open a reporting data bases for a fix for the problem. If no fix
problem record and provide the dump to the exists, contact the IBM Support Center. Provide the JCL
IBM Support Center for diagnosis. and the program listing for the job.
Other Internal SRM error. Save the dump and contact Source: DFSMSdfp
IBM support.
System action: Take action according to the different 16B
reason codes. Explanation: During processing of a MODESET
For reason codes 04 to 24: The system abnormally macro, the system found an error.
ends the issuer of the SYSEVENT macro. The system Register 15 contains a hexadecimal reason code that
writes messages and a logrec data set error record. explains the error:
For reason code 28: The system can no longer enforce Code Explanation
a defined capacity limit.
04 The macro parameter list was null.
System programmer response: Take action
according to different reason codes. 08 The macro specified reserved bits.
For reason codes 04 to 24: If an installation-provided 0C The macro requested an incorrect mode.
program issued the SYSEVENT, ensure that the 10 The macro requested an incorrect key.
program is authorized. Correct the error indicated by the
reason code. Run the job again. If an IBM-provided System action: The system abnormally ends the
program issued the SYSEVENT, run the job again. In program that issued the MODESET macro.
either case, if the error recurs, search problem reporting Application Programmer Response: Correct the
data bases for a fix for the problem. If no fix exists, macro or the program errors that incorrectly modified
contact the IBM Support Center. Provide the logrec data the parameter list. Run the job again.
set error record and the SYSOUT output for the job.
System programmer response: If the error recurs
For reason code 28: Increase the defined capacity limit, and the program is not in error, look at the messages in
or adjust the weight of the partition. the job log for more information. Search problem
Source: System resources manager (SRM) reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
source program listing for the job.
169
Source: Task management
Explanation: The error occurred during the processing
of IMGLIB with the CLOSE option. The DCB address
passed to IMGLIB in register 1 was incorrect. This 16D
system completion code is accompanied by message Explanation: The system was processing one of the
IEC919I. Refer to the explanation of message IEC919I following Supervisor Call (SVC) extended service
for complete information about the task that was ended routines (ESR):
and for an explanation of the return code in register 15. 109
Operator response: Start a generalized trace facility 116
122
Chapter 2. System Completion Codes 139
16E
137 Code Explanation
04 The DEB pointer is not in the DEB table. A
The system detected an incorrect ESR code in register
DEB whose address is not in the DEB table
15. This error is the result of a program specifying
cannot be verified, deleted, or purged.
either:
v An incorrect ESR code 08 The TYPE specified in the DEBCHK macro is
v An unsupported ESR code incorrect. The TYPE must be VERIFY, ADD,
DELETE, or PURGE.
A hexadecimal reason code in register 15 explains the
0C A DEBCHK macro that specified a TYPE other
error:
than VERIFY was issued by a program that is
Code Explanation not authorized.
0004 A program specified an incorrect ESR code. 10 The system found that the DEBDCBAD field in
The ESR code was too large. the DEB does not point to a DCB. DEBDCBAD
must point to a DCB when TYPE is VERIFY,
0008 A program specified an unsupported ESR ADD, or DELETE.
code.
14 AM value in the DEBCHK macro does not
System action: The system moves the incorrect ESR equal the DEBAMTYP value in the DEB. When
code from register 15 to register 2. The system a DEB pointer is added to the DEB table, the
abnormally ends the program that issued the incorrect access method (AM) value, if given, is placed
SVC instruction. The system may write a logrec data set in the DEBAMTYP field of the DEB. If no AM
error record. value is coded, a 0 is inserted in DEBAMTYP.
Operator response: If the system programmer asks Subsequent DEBCHKs issued to verify or
for an SVC dump, set the following SLIP trap: delete that DEB pointer must either specify the
same AM value or omit the operand. When the
SLIP SET,COMP=16D,ACTION=SVCD,END
operand is omitted, no comparison is made.
System programmer response: Do the following:
If you run programs that use batch LSR, see
1. Ask the operator to set a SLIP trap to obtain an MVS Batch Local Shared Resources for more
SVC dump. information about S16E-14 abends.
2. In the system trace, back up to the *RCVY entry for
18 The DEBCHK macro specified TYPE=ADD;
abend X'16D'. Look for an SVC entry, other than
however, the DEB was not queued on the TCB
SVC D, prior to the *RCVY entry. In the entry, note
DEB chain. Before the DEB pointer can be
the address in the PSW ADDR column.
added to the table, the DEB itself must be
3. Use the address in the PSW to identify the module queued on the current TCB DEB chain. The
that called supervisor control. TCBDEB field points to the first DEB in the
v For an installation-provided module, correct the chain.
problem as follows:
1C The DEBCHK macro specified TYPE=ADD, but
– For reason code X'0004', correct the ESR the DEBCHK routine found one of the
code, and run the job step again. following:
– For reason code X'0008', be sure that the v The DEBAMTYP or DEBTBLOF field in the
requested ESR is installed in the system. DEB contains zero.
v For an IBM module, search problem reporting v The DEB table already contains a pointer to
data bases for a fix for the problem. If no fix the DEB.
exists, contact the component group associated
v The DEB to be added is in fetch-protected
with this module at the IBM Support Center.
main storage.
Provide the SVC dump and, if available, the
logrec data set error record. 20 The DEBCHK macro specified TYPE=ADD;
however, the DEB table contains 32760 bytes,
Source: Supervisor control
which is its maximum size. The current DEB
table does not have space for this new DEB
16E pointer.
Explanation: The system control program issued a Application Programmer Response: Correct the
DEBCHK macro for the data extent block (DEB) pointed error indicated by the reason code.
to in the DCBDEBAD field of a data control block (DCB)
Source: DFSMSdfp
passed by the program. The DEBCHK function could
not be performed. Register 15 contains a hexadecimal
reason code:
140 z/OS V1R10.0 MVS System Codes
171
equal to the second byte of
171
the reason code issued the
Explanation: A PGFIX, PGFREE, PGLOAD, PGOUT, reason code.
PGRLSE, or PGANY macro requested a paging service.
3B000401 The starting address in a
The request was not valid. The storage range specified
virtual subarea list
by the input parameters may not have been requested
(VSL)/page service list (PSL)
first by a GETMAIN macro.
entry is greater than the
The registers contain the following: ending address.
v Register 0: A hexadecimal reason code, which is one 3B000601 The starting address in a
of the following: VSL/PSL entry is greater
than the ending address.
Note: If you don’t find your reason code in Register
0, see the error code listed in Register 15. 3C000101
Code Explanation 3C000102 The SVC caller’s storage
key was not zero and did not
06000101 The starting address in a match the event control
virtual subarea list (VSL) block (ECB) storage key.
entry is greater than the
ending address. 3C000201 The ECB page had not been
obtained by a GETMAIN
06F20101 macro.
07F20101 51000101 through 51000105
0AF20101 An incompatible function
combination exists in a VSL
32F20101 entry.
33F20201 51000201 A VSL entry did not request
a valid function.
3BF20101
51000301 A caller requested 24-bit
6FF20101 A program check occurred
interface and a real address
when the paging services
in the VSL entry.
was accessing the caller’s
service list (SL) entry. 51000302 Register format entry and a
starting address was greater
07000101
than an ending address.
09000101
55000101 The caller is not in key 0.
0A000101 The key for the page did not
match the caller’s.
34000101
55000201 The caller requested that a
51000401 The starting address in a
permanently resident page
virtual subarea list (VSL)
be released.
entry is greater than the
ending address. 6A000101 The caller specified a
nonzero ECB address with a
35000201 The page is part of a virtual
cross memory page services
I/O (VIO) window.
request.
35000301
6A000201 The caller specified a
36000101 The page had not been nonzero ECB address with a
obtained by a GETMAIN PGOUT, PGRLSE or
macro. PGANY request.
36000201 Permanent error. 6A000301 An ECB address contained a
negative number. The
3AF20101 A program check occurred request was a PGFIX,
when the paging services PGFREE or PGLOAD.
was accessing the caller’s
service list (SL) entry. The 6A000401 An ECB was not on a word
entry point whose ID is boundary. The request was
a PGFIX, PGFREE or
PGLOAD.
Chapter 2. System Completion Codes 141
172
6A000601 The caller is not authorized Code Explanation
to perform the page service
04 This is a PGFIX request. The caller did not
function requested. The
obtain the VSL storage using a GETMAIN
request was a PGFIX or
macro.
PGFREE.
10 The input ECB, TCB, or PSL/SSL failed to
6A000701 The caller specified a cross
pass validity checks.
memory mode request and a
nonzero task control block System action: The system issues an abend to the
(TCB) address with a page current task.
service function to which the
TCB address was System programmer response: Correct the problem
applicable. in the request and run the job again. If PGFIX or
PGFREE was requested and the caller was not
6A000801 The caller specified an authorized, obtain proper authorization and run the job
incorrect TCB. The request again.
was a PGFIX, PGFREE,
PGLOAD or PGOUT. Source: Real storage manager (RSM)
6A000901 through 6A000906
The caller specified incorrect 172
options with the page Explanation: Execute channel program (EXCP)
services request. processing found that an unauthorized program issued
6A000A01 The caller did not specify a the EXCPVR macro. One of the following conditions
valid function in the must be present for the program to be authorized:
VSL/PSL entry. v The program must run under system protection key 0
through 7.
6A000B01
v The program must be in supervisor state.
6A000B02 The caller specified an ECB v The SVC 114 authorization bit is set on in the job
address, and the page step control block (JSCB).
containing it had not been
obtained by a GETMAIN v The SVC 114 authorization bit is set on in the data
macro. extent block (DEB).
6A000C01 A caller that is not in key 0 System action: The system abnormally ends the
specified an ECB address. current task.
The key of the page Application Programmer Response: Ensure that the
containing it did not match program is authorized to issue the EXCPVR macro or
the caller’s key. SVC 0, the EXCP macro. Check the problem program
v Register 3: If an SVC entry, the contents of register for the error. If the error cannot be determined, run the
3 are destroyed. job again, requesting an ABEND dump. Notify the
v Register 4: If LIST-FORMAT entry, address of the system programmer.
caller’s erroneous VSL entry. If REGISTER-FORMAT System programmer response: If the system wrote a
entry, register 4 contains zero. dump, look at field TCBEXCPD at offset X'C0' in the
v Registers 5-9: If branch entry, registers 5-9 are the task control block (TCB) of the current task.
same as the caller’s input registers. If SVC entry, TCBEXCPD points to the EXCP debugging area
registers 5-9 contain zero. (XDBA). The XDBA contains diagnostic data associated
v Register 10: If the error is related to paging address with the EXCP processor.
of the page in error. If the error is not related to If the error recurs and the program issuing the EXCPVR
paging, register 10 contains zero. or EXCP macro is not in error, look at the messages in
v Register 11: If LIST-FORMAT entry, address of the the job log for more information. Search problem
caller’s first VSL entry. If REGISTER-FORMAT entry, reporting data bases for a fix for the problem. If no fix
register 11 contains 0. exists, contact the IBM Support Center.
v Register 12: Address of the input ECB. If no ECB Source: Execute channel program (EXCP)
address was supplied, register 12 contains zero.
v Registers 13-14: The VSL entry in error. If the VSL
was in pageable storage or if the VSL storage key
did not match a nonzero caller’s storage key,
registers 13-14 contain zero.
v Register 15: Hexadecimal error code, as follows:
142 z/OS V1R10.0 MVS System Codes
177 • 179
table for the segment describing the area to be
177
obtained was paged out.
Explanation: During processing of a TESTAUTH
System action: The system issues message IEA705I.
macro, the system detected incorrect input parameters,
The system abnormally ends the current task.
as follows:
v An incorrect bit mask is in register 1. Application Programmer Response: Ensure that the
calling program is not requesting too much central
v RBLEVEL=2, but the request block (RB) is the last
storage.
RB chained or is out of range.
v The function code is greater than 256 or is out of If the system issues this abend frequently, notify the
range. system programmer.
v The authorization code is greater than 256 or is out System programmer response: See installation
of range. procedures to increase the central storage
requirements.
System action: The system abnormally ends the
program that issued the TESTAUTH macro. Source: Virtual storage manager (VSM)
Application Programmer Response: Ensure that the
TESTAUTH parameter list is valid. The only valid 179
IBM-supplied authorization or function code is one (1). If
the installation supplied an authorization matrix, check Explanation: While processing an I/O request, the
to see that the function and authorization codes fall system found an error in the I/O parameters.
within the range of the installation-defined codes. Register 2 contains a reason code, as follows:
System programmer response: If the error recurs Code Explanation
and the program is not in error, look at the messages in
the job log for more information. Search problem 04 An error occurred when a program issued the
reporting data bases for a fix for the problem. If no fix SETLOCK macro.
exists, contact the IBM Support Center. Provide the 08 The system found an incorrect access method
program listing for the job. block (AMB) or I/O management block (IOMB).
Source: Task management 0C The system found an incorrect channel
program area (CPA).
178 10 The system could not fix a page in storage.
Explanation: An error occurred when the system tried 14 The system found an incorrect buffer address.
to process an RU or VRU form of the GETMAIN macro
or the STORAGE OBTAIN macro. The GETMAIN or 18 The system found incorrect addresses in a
STORAGE OBTAIN requested virtual storage that chain of channel control words (CCW).
requires more central storage than is available. A 1C The storage block size is not 4 kilobytes.
reason code in the SDWACRC field of the system
diagnostic work area (SDWA) explains the error: 40 IOMVEB points to a VEB that has incorrect
data.
Code Explanation
44 IOMVEB is zero, but the media manager return
04 There is not enough central storage available code indicates it should point to a VEB.
to support a request for space in a system
queue area (SQA) subpool. 48 AMB MRET pointer is incorrect.
08 There is not enough central storage available 4C MRET MREB pointer is incorrect, or MREB
to support a request for space in a fixed does not point back to BUFC that points to it.
common service area (CSA) subpool.
50 For shared resources, no MRET entry pointed
0C There is not enough central storage available to IOMBUFC that points to BUFC.
to support a request for space in a local
54 Received unexpected MMCALL return code.
system queue area (LSQA) subpool.
58 Could not find BUFC in error, but the media
1C The system could not satisfy a request for an
manager return code indicates some MMRE is
LSQA subpool. The page table for the segment
posted with an error.
describing the area to be obtained was paged
out. System action: The system abnormally ends the
current task.
20 The system could not satisfy a request for an
authorized private area subpool. The page Application Programmer Response: Do the
following:
Chapter 2. System Completion Codes 143
17A • 183
1. Check to see if the program incorrectly modified the
17D
I/O parameters. Correct any errors.
2. Recompile the job step. Explanation: During processing of an EVENTS macro
for a wait request, the system found an incorrect
3. Run the job step again.
address specified for the EVENTS table.
Source: VSAM
System action: The system abnormally ends the
program that issued the EVENTS macro.
17A
Application Programmer Response: Ensure that an
Explanation: During processing of an EVENTS macro EVENTS macro was issued to construct the EVENTS
for a table creation or deletion, the system found an table. Correct the error. Run the job again.
incorrect address specified for the EVENTS table.
System programmer response: If the error recurs
System action: The system abnormally ends the and the program is not in error, look at the messages in
program that issued the EVENTS macro. the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
Application Programmer Response: Ensure that an exists, contact the IBM Support Center. Provide the
EVENTS macro was issued to construct the EVENTS program listing and the assembly listing associated with
table. Correct the error. Run the job again. the job.
System programmer response: If the error recurs Source: Task management
and the program is not in error, look at the messages in
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix 182
exists, contact the IBM Support Center. Provide the
Explanation: RACF could not successfully establish
program listing and the assembly listing associated with
an ESTAE recovery environment when processing a
the job.
RACHECK request.
Source: Task management
System action: The system ends the task.
System programmer response: Register 15 contains
17B
the nonzero return code passed back from the ESTAE
Explanation: A program running in supervisor state, macro. For a description of the ESTAE return code, see
key 0 issued the PURGEDQ macro with an incorrect z/OS MVS Programming: Authorized Assembler
value in the ASID parameter. The address space for the Services Reference EDT-IXG.
specified ASID does not exist.
See z/OS Security Server RACF Diagnosis Guide for
System action: The system abnormally ends the task information on diagnosing RACF abends and reporting
that issued the PURGEDQ macro. The system may abend problems to IBM.
write a logrec data set error record.
Note: For batch jobs, if you need to do dump analysis
Operator response: If the system programmer asks
but do not have a dump, run the job again. For
for an SVC dump, set the following SLIP trap:
batch jobs using DSMON, a RACF command, or
SLIP SET,COMP=17B,ACTION=SVCD,END the RACF report writer, specify a SYSABEND
System programmer response: Do the following: DD statement in the job. This will ensure that a
dump is taken.
1. Ask the operator to set a SLIP trap to obtain an
SVC dump. Source: Resource Access Control Facility (RACF)
2. In the system trace, look for an SVC 7B entry. The
address in the PSW ADDR column for this SVC 183
entry is the address of the calling module.
Explanation: RACF could not successfully establish
3. Use the PSW address to identify the module that
an ESTAE recovery environment when processing a
issued the PURGEDQ macro.
RACINIT request.
v For an installation-provided module, continue
diagnosis with the module. System action: The system ends the task.
v For an IBM module, search problem reporting System programmer response: Register 15 contains
data bases for a fix for the problem. If no fix the nonzero return code passed back from the ESTAE
exists, contact the component group associated macro. For a description of the ESTAE return code, see
with this module at the IBM Support Center. z/OS MVS Programming: Authorized Assembler
Provide the SVC dump and the logrec data set Services Reference EDT-IXG.
error record.
See z/OS Security Server RACF Diagnosis Guide for
Source: Supervisor control
144 z/OS V1R10.0 MVS System Codes
185 • 18A
information on diagnosing RACF abends and reporting 35000301 The page had not been obtained by
abend problems to IBM. a GETMAIN macro.
36000101 The page had not been obtained by
Note: For batch jobs, if you need to do dump analysis
a GETMAIN macro.
but do not have a dump, run the job again. For
batch jobs using DSMON, a RACF command, or 36000201 Permanent error.
the RACF report writer, specify a SYSABEND
3AF20101 A program check occurred when
DD statement in the job. This will ensure that a
the paging services was accessing
dump is taken.
the caller’s service list (SL) entry.
Source: Resource Access Control Facility (RACF) The entry point whose ID is equal
to the second byte of the reason
code issued the reason code.
185
3B000401 The starting address in a virtual
Explanation: RACF could not successfully establish
subarea list (VSL)/page service list
an ESTAE recovery environment when processing a
(PSL) entry is greater than the
RACDEF request.
ending address.
System action: The system ends the task.
3B000501 The caller’s page service list (PSL)
System programmer response: Register 15 contains entry contains the reserved flag.
the nonzero return code passed back from the ESTAE
3B000601 The starting address in a VSL/PSL
macro. For a description of the ESTAE return code, see
entry is greater than the ending
z/OS MVS Programming: Authorized Assembler
address.
Services Reference EDT-IXG.
3BF20101 A program check occurred when
See z/OS Security Server RACF Diagnosis Guide for
the paging services was accessing
information on diagnosing RACF abends and reporting
the caller’s service list (SL) entry.
abend problems to IBM.
55000101 The caller is not in key 0. The key
Note: For batch jobs, if you need to do dump analysis for the page did not match the
but do not have a dump, run the job again. For caller’s.
batch jobs using DSMON, a RACF command, or
55000201 The caller requested that a
the RACF report writer, specify a SYSABEND
permanently resident page be
DD statement in the job. This will ensure that the
released.
system produces a dump.
6A000101 The caller specified a nonzero
Source: Resource Access Control Facility (RACF)
event control block (ECB) address
with a cross memory page services
18A request.
Explanation: A PGSER macro requested a paging 6A000201 The caller specified a nonzero ECB
service (FIX, FREE, LOAD, RELEASE, ANYWHER, address with a PGOUT, PGRLSE
PROTECT, or UNPROTECT). The request was not or PGANY request.
valid. The caller used 31-bit addressing.
6A000301 An ECB address contained a
The registers contain the following: negative number. The request was
v Register 0: A hexadecimal reason code, which is one a PGFIX, PGFREE or PGLOAD.
of the following: 6A000401 An ECB was not on a word
Code Explanation boundary. The request was a
PGFIX, PGFREE or PGLOAD.
08000101 On a branch request, the start
address is greater than the end 6A000601 The caller is not authorized to
address. The request was a perform the page service function
register-format input. requested. The request was a
PGFIX or PGFREE.
0B000101 On an SVC request, the start
address is greater than the end 6A000701 The caller specified a cross
address. The request was a memory mode request and a
register-format input. nonzero task control block (TCB)
address with a page service
35000201 The page is part of a virtual I/O function to which the TCB address
(VIO) window. was applicable.
Chapter 2. System Completion Codes 145
18A
6A000801 The caller specified an incorrect with a key that does not match the
TCB. The request was a PGFIX, PSW key under which the program
PGFREE, PGLOAD or PGOUT. runs. The program issuing the
PGSER UNPROTECT macro must
6A000901 through 6A000906
be either key zero or else run under
The caller specified incorrect
a PSW key that matches the key of
options with the page services
the storage being unprotected.
request.
xx0802xx The caller tried to issue the PGSER
6A000A01 The caller did not specify a valid
macro with the UNPROTECT
function in the VSL/PSL entry.
parameter for virtual storage in
6A000B01 The caller specified an ECB either the PSA or any VIO window.
address, and the page containing it Neither storage area can be
had not been obtained by a specified with the UNPROTECT
GETMAIN macro. keyword.
6A000B02 The caller specified an ECB v Register 3: If branch entry, caller’s return address.
address, and the page containing it v Register 4: If LIST-FORMAT entry, address of the
had not been obtained by a caller’s erroneous page service list entry (PSL)/short
GETMAIN macro. page service list (SSL). If REGISTER-FORMAT entry,
register 4 contains zero.
6A000C01 A caller that is not in key 0
specified an ECB address. The key v Registers 5-7: If SSL format entry, registers 5-7
of the page containing it did not contain the caller’s input registers.
match the caller’s key. If PSL format SVC entry, registers 5-7 contain zero.
6FF20101 A program check occurred when If PSL format branch entry, registers 5-7 are
the paging services was accessing irrelevant.
the caller’s service list (SL) entry. v Register 8: If SSL format entry, register 8 is the
same as the caller’s input register.
xx0008xx The caller tried to release a page of
protected storage. If PSL format SVC entry, register 8 contains zero.
If PSL format branch entry, register 8 contains the
xx000907 The caller issued a PGSER macro caller’s input TCB address, or, if no TCB address was
with the PROTECT parameter, but supplied, register 8 contains zero.
one of the other parameters
specified was either incorrect or v Register 9: If PSL format entry, address of the input
incompatible. ECB. If no ECB address was supplied, register 9
contains zero.
xx000908 The caller issued a PGSER macro If SSL format entry, register 9 is the same as the
with the UNPROTECT parameter, caller’s input register.
but one of the other parameters
specified was either incorrect or v Register 10: If the error is related to paging, the
incompatible. address of the page in error. If the error is not related
to paging, register 10 contains zero.
xx0701xx The caller issued a PGSER macro v Register 11: If LIST-FORMAT entry, address of the
with the PROTECT parameter for caller’s first PSL/SSL entry. If REGISTER-FORMAT
storage with a key that does not entry, register 11 contains 0.
match the PSW key under which
the program runs. The program v Registers 12-14: If PSL format entry, the PSL entry
issuing the PGSER macro with the in error. If the PSL was in pageable storage or if the
PROTECT parameter must be PSL storage key did not match a nonzero caller’s
either key zero or else run under a storage key, registers 12-14 contain zero.
PSW key that matches the key of If SSL format entry, register 12 contains zero.
the storage being protected. Registers 13-14 contain the SSL entry in error, or, if
the SSL was in pageable storage, registers 13-14
xx0702xx The caller tried to issue the PGSER contain zero.
macro with the PROTECT
parameter for virtual storage in v Register 15: Hexadecimal reason code, as follows:
either the PSA or any VIO window. Code Explanation
Neither storage area can be
specified with the PROTECT 04 A caller issued a PGFIX request but did not
keyword. obtain the PSL storage using a GETMAIN
macro, or a page release operation failed
xx0801xx The caller issued a PGSER macro because either the caller attempted to
with the UNPROTECT parameter
146 z/OS V1R10.0 MVS System Codes
18B • 18F
release permanently backed storage or a
18F
non-system key caller attempted to release
storage in a different key. Explanation: An abend occurred during the
processing of the Integrated Cryptographic Service
10 The input ECB, TCB, or PSL/SSL failed
Facility/MVS (ICSF/MVS) main task.
validity checks.
Reason codes are as follows:
System action: The system issues an abend to the
current task. Code Explanation Reason codes for ICSF
mainline routines:
System programmer response: Correct the problem
in the request and run the job again. If PGFIX or 01 The ICSF mainline process could not establish
PGFREE was requested and the caller was not a data space.
authorized, obtain proper authorization and run the job
03 Error in the ICSF mainline cross memory
again.
environment.
Source: Real storage manager (RSM)
04 Error loading or calling installation exits.
05 The entry code in the component trace
18B
environment is not valid.
Explanation: The common VTOC access facility
07 Error in the master key validation routine.
(CVAF) encountered one of the following conditions:
v A structure error in the VTOC index 08 Error in creating an in-storage cryptographic
key data set (CKDS).
v The CVAF return code is not consistent with the
CVAF status code. 09 Error in the interface to the event notification
facility.
System action: A dump is written to SYS1.DUMP and
an error record is written to the logrec data set. The 0A Error from the component trace routine.
task is not ended. If CVAF encountered a structure error
in the VTOC index: 0B ICSF could not load a required exit.
v Message IEC606I is issued. 0C Exit number is not valid.
v CVAF disables the VTOC index. 0D ICSF could not obtain a cross memory linkage
v If the caller of CVAF requests a read or write of a index.
format 1 or 4 DSCB, CVAF performs the function and
0E ICSF could not set a cross memory
returns a code of yes to its caller.
authorization index.
v If the caller of CVAF requested a CVAF function that
requires the VTOC index, CVAF returns an error 0F ICSF could not create an entry table for
return code to its caller. This may cause the caller to space-switching PC routines.
end. 10 ICSF could not connect its entry table to the
If the CVAF return code is not consistent with the CVAF system tables.
status code, CVAF returns an I/O error return code to its 11 Error reading the CKDS into storage.
caller. This may cause the caller to end.
12 ICSF could not establish an ENF listen exit.
Application Programmer Response: If a structure
error in the VTOC index was encountered and the 13 ICSF could not issue a broadcast ENF signal.
program ended, it may be rerun if it does not depend 14 ICSF could not establish an ESTAE during
upon the VTOC index. Run the IEHLIST utility to list the initialization.
VTOC and the disabled VTOC index. An inconsistency
between the CVAF return code and status code 16 The entry code in the termination resource
indicates a logic error in CVAF. You may not be able to manager is not valid.
successfully run the job until the problem is corrected.
17 ICSF could not establish a termination
System programmer response: If the error recurs resource manager.
and the program is not in error, search problem
1A ICSF could not OPEN, READ, WRITE, or
reporting data bases for a fix for the problem. If no fix
CLOSE a data set.
exists, contact the IBM Support Center. Provide the
logrec data set error record and all printed output and 1B ICSF could not interpret the options data set.
output data sets related to the problem.
1C Serious error encountered during processing of
Source: DFSMSdfp the CICS Wait List data set.
1E The entry code to the data space create
routine is not valid.
Chapter 2. System Completion Codes 147
18F
1F Error from DSPSERV CREATE in the data 4E Error from DETACH in CSFMCCPC.
space create routine.
4F Erroneous result from PCI Cryptographic
20 Error from ALESERV ADD in the data space Coprocessor controller.
create routine.
50 ICSF error interface to PCI Cryptographic
21 Error from ALESERV EXTRACT in the data Coprocessor controller.
space create routine.
51 Error from latch manager in CSFACCPR
22 Error from ALESERV DELETE in the data module.
space create routine.
52 Error from resource manager in CSFACCPR
23 Error from DSPSERV DELETE in the data module.
space create routine.
53 Attempt to free zero storage in CSFMCCPC
28 Error in the look for disabled cryptographic module.
feature routine.
54 SYSPLEXTKDS(YES,FAIL(YES)) was specified
29 Error from ATTACH in the look for disabled in the ICSF Installation Options Data Set and
cryptographic feature routine. the IXCJOIN request failed, which is issued by
the ICSF Cross-System Services Controller
2A Error from DETACH in the look for disabled
task to join the ICSF sysplex group.
cryptographic feature routine.
55 One of the following conditions occurs:
2C The refresh code in the component trace
routine is not valid. v Error from latch manager in ICSF
Cross-System Services.
32 Error in the generic service loader routine.
v An attempt to create the TKDS latch set
33 ICSF could not load a required installation failed.
service.
56 Unexpected return code from ISGENQ in ICSF
37 Error loading an application service. Cross-System Services.
38 ICSF could not install the compatibility 57 Unexpected return code from ESTAE in ICSF
cryptographic SVC. Cross-System Services.
3C Invalid domain index specified in ICSF 58 IXCQUERY failed.
parameters.
59 Incorrect entry code passed to CSFMTDS.
3D Error in CPOOL manager.
5A Incorrect entry code passed to CSFMTDSC.
3E Error in I/O subtask control routine.
60 CSVDYLPA call failed in module CSFMENFC.
3F Error from ATTACH in the I/O subtask control
61 Problem encountered during CSVDYLPA in
routine.
module CSFMENF1.
40 Error from DETACH in the I/O subtask control
| 6D Error from ATTACH of CSFINQKP.
routine.
Reason codes for application services routines:
41 Error in initialization.
80 Parameter block for the compatibility services
42 Error in initialization - ATTACH.
is not valid.
43 Error in initialization - DETACH.
84 An unrecognized service number was passed
46 Error in serialization. from the user application.
47 Error in resource manager. 8C The master key version number is not valid.
48 Cryptographic public key operation disabled. 90 The status word from the hardware contained a
response code that is not valid.
49 Cryptographic public key operation not
initialized. 92 The key encrypting key (KEK) was the wrong
type or was not a no control vector (NOCV)
4A Cryptographic public key operation not KEK.
available.
94 The variant passed to the twist processing
4B CCC’s do not match. routine is not valid.
4C Error in CSFMCCPC module. 98 ICSF ended abnormally. An exit installed with
4D Error from ATTACH in CSFMCCPC. the FAIL=ICSF option has ended abnormally.
148 z/OS V1R10.0 MVS System Codes
18F
A0 Error in the CKDS retrieval routine. C0 The storage allocated to the TKDS data space
or to the session object data space becomes
A1 Requested system key was not found in the
full.
in-storage and/or the DASD CKDS.
C1 A bad entry code is passed to the TKDS I/O
A2 Error in the CKDS retrieval routine. The
subtask controller.
requested system key has a MAC that is not
valid. C2 Error in ATTACH processing while attaching
the TKDS I/O subtask.
A3 Error in the CKDS retrieval routine. The
requested dummy key was not found. C3 Error in DETACH processing while attaching
the TKDS I/O subtask.
A4 Output type not valid.
C4 The FUNCTION parameter is unrecognizable
A5 Error in internal ICSF parameters service calls.
on a call to CSFATKDS.
A6 Cryptographic public key request not valid.
C5 Error from an attempt to create or access a
A7 Public key token type not valid. PKCS #11 data space.
A8 Hardware configuration is not enabled. C6 Error in CSFMTXCC.
A9 Hardware configuration contains wrong key C7 Error from ATTACH in CSFMTXCC.
size.
C8 Error from DETACH in CSFMTXCC.
AA Arithmetic operand is not valid.
C9 Error in the CKDS retrieval routine. The
AC Error in public key processing. sysplex entry point was not called properly.
AD Error in public key processing. | CC Unable to attach the PKDS cross system
| services task.
AE Value for the FUNCTION parameter is
unrecognized on call to CSFAPKDS. | CD Failure detaching the PKDS cross system
| services task during termination.
AF Error occurred in module CSFMIOPC.
| D0 Internal parameter error during ICSF sysplex
B0 Error occurred in ATTACH macro issued in | processing.
CSFMIOPC.
Common reason codes (issued by more than one
B1 Error occurred in DETACH macro issued in function):
CSFMIOPC.
100 The return code from an installation exit is not
B2 Unable to obtain storage for CPRB. valid.
B3 Domain in CPRB does not match CCVE. 101 Compatibility mode service was requested but
B4 Length of CPRB in SPB is wrong. has not been available since z/OS V1R3.
B5 Return code 16 from PCI Cryptographic 102 Condition code from the ICSF (instruction)
Coprocessor application. macro is not valid.
B6 Too much data for the CPRB/parameter block. 103 Return code from the RCFSTAT macro is not
valid.
B7 The reply CPRB or parameter block can not be
processed because of invalid format or invalid 104 Return code from the RCFCONF macro is not
data. valid.
B8 Reencipher of the CKDS failed due to an error 105 A master key version change occurred during
in processing on the PCI Cryptographic the re-encipher, conversion or dynamic CKDS
Coprocessor. update process.
B9 Unexpected failure reading PKDS header. 106 Invalid CCC or invalid algorithm bits in
CSFMPMKV module.
BA Error in Pause processing.
107 Error in public key processing.
BB Error in Release processing.
108 Error in interprocessor communication.
BC Error in Allocate_Pause_Element processing.
109 Bad response code for PKSC/PKA request.
BD Error in CSFMXCFC.
10A Bad PKSC/PKA request block.
BE Error from ATTACH in CSFMXCFC.
10B PCI Cryptographic Coprocessor queue full
BF Error from DETACH in CSFMXCFC. error from CSFACCPS.
Chapter 2. System Completion Codes 149
1C2
10C Unknown response code from PCI 205 The control vector (CV) in the cryptographic
Cryptographic Coprocessor instructions. key data set (CKDS) record is not valid.
10D Storage exception during dequeue process. 206 The conversion service received a CKDS that
is not valid.
10E Bad message ID during enque process.
207 WLM encountered a bad data area.
10F Bad AP TYPE returned from a TESTQ
operation to a cryptographic coprocessor. Reason codes for dialog routines:
Reason codes for key generator utility program 300 A function that was passed to the dialog
(KGUP) and common services: service routine is not valid.
144 Cannot build LSR in CSFIO003 module. Reason codes for component trace:
148 Cannot use LSR in CSFIO003 module. 380 A message ID that was used in the component
trace routine is not valid.
180 Error found in the message queue.
381 The control block in the component trace
181 The exit list in the common I/O routine is not
routine is not valid.
valid.
System action: If the abend occurred during ICSF
182 The access control block in the common I/O
initialization, ICSF ends abnormally.
routine is not valid.
In general, if the abend occurred after ICSF is available
183 The request parameter list in the common I/O
and running, your application or unit of work ends. ICSF
routine is not valid.
is still available. However, if the error occurred when
184 MAC_generation or Mac_verification failed with trying to set the cryptographic domain index or if an exit
RC=12 during dynamic CKDS update that is installed with the FAIL=ICSF option abends,
processing. ICSF ends abnormally.
185 An incorrect function request was passed to Application Programmer Response: Review the
common I/O routines for dynamic CKDS reason codes on the dump title to see if the abend was
update processing. an installation or user error. Also check to see if the
reason code was an installation-generated reason code.
186 Unexpected return or reason codes were If you cannot resolve the problem, save the dump,
returned from common I/O routines during gather the dump header record, and contact the IBM
dynamic CKDS update processing. support center.
187 Incorrect CKDS record created during dynamic Debugging aids and recovery-related information are
CKDS update processing. discussed in ICSF System Programmer’s Guide.
Reason codes for ICSF message processing: Source: Integrated Cryptographic Service Facility
190 Message processing block (MPB) is not valid. (ICSF)
191 A blank message skeleton was retrieved.
1C2
192 A matching message table was not found.
Explanation: The MQSeries® Workflow for OS/390
193 The message was not found server address space encountered a severe internal
194 The substitution tag is not valid. error.
195 The message buffer size was exceeded. The reason code identifies the source of the error. It has
the format X'rrmmnnnn', where rr denotes the resource
196 The Message variable not found in the MPB. class (as detailed in the table that follows), mm denotes
197 CAMQ reply PSMID does not match. the method of the resource class, and nnnn identifies
the place within the method where the error was
198 CCP reply PSMID does not match. encountered.
199 Unknown response code after dequeue CAM. Resource Resource Resource
Reason codes for ICSF callable services: Class Code Name Description
200 An error occurred in the encode or decode 01 Resource abstract class for
callable service. workflow server
resources
202 An error occurred in the key generate callable
service. The parameter to CSFKGN1 called 02 FmSrvRes abstract class for
IK_PROCESS_RULE has an unknown value, workflow server
and processing cannot continue. instance resources
150 z/OS V1R10.0 MVS System Codes
1C3
Resource Resource Resource Resource Resource Resource
Class Code Name Description Class Code Name Description
03 FmDevRes abstract class for 20 XMemServ implementation class
workflow server for the cross-memory
input/output device services
resources
04 SystCons implementation class System action: The system issues an ABEND dump.
for the system
console interface Application Programmer Response: None.
05 Diagnose implementation class System programmer response: For reason code
for the flight recorder X'1505nnnn', verify the setup for the component trace
and restart the server. For reason code X'1705nnnn',
06 FifoLock implementation class verify the setup for the workload manager application
for the queue environment and restart the server.
serialization
For other reason codes, search the problem reporting
07 MvsMsgSv implementation class
data bases for a fix for the problem. If no fix exists,
for the MVS message
contact the IBM Support Center and provide the ABEND
services interface
dump.
08 DevQueue implementation class
Source: MQSeries Worklfow for OS/390
for the in-storage
queues
09 ErrStack implementation class 1C3
for the error recovery Explanation: An error occurred during IBM License
10 ServerDS implementation class Manager (ILM) processing. The accompanying reason
for the data set codes identify either an internal IBM License Manager
access error or an external error code as follows:
11 Security implementation class Value Description
for the security server
0403 Bad input parameters.
interface
12 SrvGroup implementation class Action: Search problem reporting data bases
for the subtask for a fix for the problem. If no fix exists,
management contact the IBM Support Center. Provide the
dump and, if this problem caused multiple
13 SynchEcb implementation class abends, the portion of the logrec log
for the subtask containing the relevant logrec records.
synchronization
0414 Bad return code from ETCRE macro.
14 TimeServ implementation class
for the timer interface Action: Search problem reporting data bases
for a fix for the problem. If no fix exists,
15 ExtTrace implementation class contact the IBM Support Center. Provide the
for the component dump and, if this problem caused multiple
trace interface abends, the portion of the logrec log
16 TaskServ implementation class containing the relevant logrec records.
for the subtask 0415 Bad return code from ETCON macro.
services
Action: Search problem reporting data bases
17 WkldMgmt implementation class for a fix for the problem. If no fix exists,
for the workload contact the IBM Support Center. Provide the
manager interface dump and, if this problem caused multiple
18 XcfGroup implementation class abends, the portion of the logrec log
for the cross-system containing the relevant logrec records.
coupling facility
interface
19 XLngServ implementation class
for the
cross-language
services
Chapter 2. System Completion Codes 151
1C3
Value Description Value Description
0418 Bad return code from ESTAE macro. 0427 Attach of BPXBATSL to execute Agent C
Daemon failed.
Action: Search problem reporting data bases
for a fix for the problem. If no fix exists, Action: Search problem reporting data bases
contact the IBM Support Center. Provide the for a fix for the problem. If no fix exists,
dump and, if this problem caused multiple contact the IBM Support Center. Provide the
abends, the portion of the logrec log dump and, if this problem caused multiple
containing the relevant logrec records. abends, the portion of the logrec log
containing the relevant logrec records.
0419 Bad return code from VSM Locate macro.
0428 Taking dump as requested by Agent C
Action: Search problem reporting data bases
Daemon.
for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the Action: Search problem reporting data bases
dump and, if this problem caused multiple for a fix for the problem. If no fix exists,
abends, the portion of the logrec log contact the IBM Support Center. Provide the
containing the relevant logrec records. dump and, if this problem caused multiple
abends, the portion of the logrec log
0420 Bad return code from LOAD or NUCLKUP
containing the relevant logrec records.
macros.
0429 Taking dump as requested by Server C
Action: Search problem reporting data bases
Daemon.
for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the Action: Search problem reporting data bases
dump and, if this problem caused multiple for a fix for the problem. If no fix exists,
abends, the portion of the logrec log contact the IBM Support Center. Provide the
containing the relevant logrec records. dump and, if this problem caused multiple
abends, the portion of the logrec log
0422 Bad return code from DSPSERV Create.
containing the relevant logrec records.
Action: Search problem reporting data bases
05C4 Cell storage address required.
for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the Action: Search problem reporting data bases
dump and, if this problem caused multiple for a fix for the problem. If no fix exists,
abends, the portion of the logrec log contact the IBM Support Center. Provide the
containing the relevant logrec records. dump and, if this problem caused multiple
abends, the portion of the logrec log
0423 Bad return code from ALESERV Add.
containing the relevant logrec records.
Action: Search problem reporting data bases
05C5 Cannot do DSPSERV RELEASE for this cell
for a fix for the problem. If no fix exists,
pool.
contact the IBM Support Center. Provide the
dump and, if this problem caused multiple Action: Search problem reporting data bases
abends, the portion of the logrec log for a fix for the problem. If no fix exists,
containing the relevant logrec records. contact the IBM Support Center. Provide the
dump and, if this problem caused multiple
0424 Bad return code from EnfReq Listen.
abends, the portion of the logrec log
Action: Search problem reporting data bases containing the relevant logrec records.
for a fix for the problem. If no fix exists,
05C6 Bad return code from Csrpbld service.
contact the IBM Support Center. Provide the
dump and, if this problem caused multiple Action: Search problem reporting data bases
abends, the portion of the logrec log for a fix for the problem. If no fix exists,
containing the relevant logrec records. contact the IBM Support Center. Provide the
dump and, if this problem caused multiple
0425 C Daemon not responding to termination
abends, the portion of the logrec log
request.
containing the relevant logrec records.
Action: Search problem reporting data bases
for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the
dump and, if this problem caused multiple
abends, the portion of the logrec log
containing the relevant logrec records.
152 z/OS V1R10.0 MVS System Codes
1C3
Value Description Value Description
05C7 Bad return code from Csrpexp service. 05CF Bad return code from Csrpfre service.
Action: Search problem reporting data bases Action: Search problem reporting data bases
for a fix for the problem. If no fix exists, for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the contact the IBM Support Center. Provide the
dump and, if this problem caused multiple dump and, if this problem caused multiple
abends, the portion of the logrec log abends, the portion of the logrec log
containing the relevant logrec records. containing the relevant logrec records.
05C8 A Storage Manager Control Block stack is 05D0 Bad return code from Csrpget service.
invalid.
Action: Search problem reporting data bases
Action: Search problem reporting data bases for a fix for the problem. If no fix exists,
for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the
contact the IBM Support Center. Provide the dump and, if this problem caused multiple
dump and, if this problem caused multiple abends, the portion of the logrec log
abends, the portion of the logrec log containing the relevant logrec records.
containing the relevant logrec records.
05D1 Bad return code from Csrpqpl service.
05C9 A Storage Manager Control Block stack
Action: Search problem reporting data bases
overflowed.
for a fix for the problem. If no fix exists,
Action: Search problem reporting data bases contact the IBM Support Center. Provide the
for a fix for the problem. If no fix exists, dump and, if this problem caused multiple
contact the IBM Support Center. Provide the abends, the portion of the logrec log
dump and, if this problem caused multiple containing the relevant logrec records.
abends, the portion of the logrec log
05D2 Incorrect data in a certificate.
containing the relevant logrec records.
Action: Search problem reporting data bases
05CA A Master Cell Pool is out of extent storage
for a fix for the problem. If no fix exists,
cells.
contact the IBM Support Center. Provide the
Action: Search problem reporting data bases dump and, if this problem caused multiple
for a fix for the problem. If no fix exists, abends, the portion of the logrec log
contact the IBM Support Center. Provide the containing the relevant logrec records.
dump and, if this problem caused multiple
05D3 The set of certificates had no IBM global
abends, the portion of the logrec log
certificate.
containing the relevant logrec records.
Action: Search problem reporting data bases
05CC Cell pool token is invalid.
for a fix for the problem. If no fix exists,
Action: Search problem reporting data bases contact the IBM Support Center. Provide the
for a fix for the problem. If no fix exists, dump and, if this problem caused multiple
contact the IBM Support Center. Provide the abends, the portion of the logrec log
dump and, if this problem caused multiple containing the relevant logrec records.
abends, the portion of the logrec log
05D4 The agent provided a DOM ID of 0 to be
containing the relevant logrec records.
saved.
05CD Cell pool is out of cells.
Action: Search problem reporting data bases
Action: Search problem reporting data bases for a fix for the problem. If no fix exists,
for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the
contact the IBM Support Center. Provide the dump and, if this problem caused multiple
dump and, if this problem caused multiple abends, the portion of the logrec log
abends, the portion of the logrec log containing the relevant logrec records.
containing the relevant logrec records.
05D5 The server provided a DOM ID of 0 to be
05CE Cell address is invalid. saved.
Action: Search problem reporting data bases Action: Search problem reporting data bases
for a fix for the problem. If no fix exists, for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the contact the IBM Support Center. Provide the
dump and, if this problem caused multiple dump and, if this problem caused multiple
abends, the portion of the logrec log abends, the portion of the logrec log
containing the relevant logrec records. containing the relevant logrec records.
Chapter 2. System Completion Codes 153
1C5
Value Description Value Description
05D6 The agent provided a stall time of 0. C009 The parameter list contains an incorrect
number of parameters.
Action: Search problem reporting data bases
for a fix for the problem. If no fix exists, Action: An error was encountered that
contact the IBM Support Center. Provide the prevents the running of the callable service.
dump and, if this problem caused multiple However, the system cannot set an error
abends, the portion of the logrec log return code for the caller because the input
containing the relevant logrec records. parameter list is incorrectly specified.
05D7 The agent or server provided a DOM ID of 0 An ABDUMP or symptom dump has been
to be deleted.. requested for the caller. In the dump, register
2 contains the return code value and register
Action: Search problem reporting data bases
3 contains the reason code value of the
for a fix for the problem. If no fix exists,
original failure. Do both of the following:
contact the IBM Support Center. Provide the
dump and, if this problem caused multiple v Analyze the return code and reason code
abends, the portion of the logrec log for the cause of the original problem.
containing the relevant logrec records. v Check for incorrect input parameters
8005 The callable service was issued by a passed to the callable service.
program running with an EUT FRR set. C00E An incorrect address was encountered when
trying to move user parameter data. This can
Action: You must not issue the callable
be caused by one of the following conditions:
service when an FRR is set. FRRs must be
deleted before calling the service. v The total number of parameters is
incorrect for the callable service being
8006 The callable service was issued by a issued.
program running with a system lock held.
v Action:There is an error in one of the
Action: You must not issue the callable passed user parameters causing the IBM
service when a lock is held. Release the License Manager to program check when
locks before calling the service. the parameter is accessed. Check for the
C001 The IBM License Manager is not supported following conditions:
on this system. – A parameter that points to non-existent
storage.
Action: Start the IBM License Manager on a
processor that supports this capability. – A parameter that cannot be accessed in
the current user PSW key.
C003 The callable service was not issued by a
program running under a task.
Any other reason codes indicate that an internal error
Action: You must issue the callable service has occurred.
only in task mode. SRB mode is not
System action:
supported.
For the reason codes listed above, use the system
C004 The CVTILM bit is off, which means no calls
actions specifically listed.
to the IBM License Manager should be made.
System programmer response: Try the request
Action: User error. If the official stubs are
again. If the problem persists, contact the IBM Support
used to call the IBM License Manager, the
Center. Provide the dump and logrec entries associated
stub will test the CVTILM bit. If you are
with this abend.
calling the IBM License Manager without the
stub, you must check CVTILM and call only if For the reason codes listed above, use the system
the flag is ON. programmer response specifically listed.
C007 The callable service was issued in Source: IBM License Manager
cross-memory mode.
Detecting Module: Many
Action: You cannot issue the callable service
in cross-memory mode. Correct the problem
and resubmit the job. 1C5
Explanation: An error occurred during System Logger
processing. The accompanying reason codes identify
either an internal recoverable Logger error or an
external error code as follows:
154 z/OS V1R10.0 MVS System Codes
1C5
Code Explanation System Programmer Response:
Contact the IBM Support Center.
00000804 An IXGBRWSE or IXGDELET request
failed because the block identifier 00010009 Logger is attempting to read from or
could not be found in the log stream. write to an offload data set, but a
Media Manager access method error
System Action: The request is not
was encountered.
honored and a return code 8, reason
code 00000804 (or corresponding System Action: Logger will issue
missing data reason code) is returned message IXG063I to attempt to
to the caller. identify the log stream and it will
request a dump. For offload
System Programmer
processing, if Logger can recover from
Response:Ensure that the value in
the error, it will close the current data
the request references an existing
set, allocate a new one, and continue
portion of the log stream.
with the offload. If Logger cannot
You can run the utility IXCMIAPU with recover, it will issue message IXG301I
LIST LOGSTREAM (logstream-name) and the offload will fail. Browse
DETAIL(YES) to help you determine if (IXGBRWSE) requests to the log
the requested blockid is in a valid streams that encounter this error
range, and it is not in a loss of data might result in warning or error gap
range. conditions.
If the blockid is valid contact the IBM System Programmer Response: If
Support Center Provide the dump and the operation in question fails, contact
LOGREC entries associated with this the IBM Support Center and provide
ABEND. the diagnostic information.
0000085F Control percolated to the service 00030006 An abend occurred after system
requester’s task due to an abend logger called an application’s
during system logger processing. complete exit. Either the complete exit
Retry was not possible. abended and percolated to system
logger recovery, or the address of the
System Programmer Response: complete exit specified on the
Request the service again. If the COMPLETEEXIT parameter of the
problem persists, contact the IBM IXGCONN request for the log stream
Support Center. was incorrect.
00010001 Logger encountered an error that System Action: System logger ends
would have resulted in overwriting log the task that owned the connection to
data on DASD. the log stream in order to end the
System Action: System Logger ends connection.
the task. System Programmer
System Programmer Response: If Response:Ensure that the complete
the operation in question fails, refer to exit address specified on the
message IXG269I for diagnostic IXGCONN request was correct and
procedures. Then contact the IBM that the address does not change.
Support Center and provide the System logger requires that the
diagnostic information. caller’s complete exit remain loaded in
storage at the address specified on
00010008 Logger is unable to interpret the IXGCONN until the application
contents of an offload data set. receives control after successfully
System Action: The request to read disconnecting from the log stream.
the data set fails. Logger will issue Then, if necessary, restart the
message IXG063I to attempt to application.
identify the log stream, and it will If the problem persists, contact the
request a dump. Logger may have IBM Support Center. Provide the
also issued message IXG0269I to dump and logrec entries associated
identify the data set in error. Browse with this abend.
(IXGBRWSE) requests to a log stream
that encounters this error might result 00030009 System logger was unable to
in warning or error gap conditions. complete an offload during log stream
recovery. The operator response to
Chapter 2. System Completion Codes 155
1C6
message IXG115A caused system after the clock (time) adjustment, then
logger to abnormally terminate the the system has previously issued
structure connect task. message IXG218A, warning of this
condition. Once the issue is
System Action: System logger ends
encountered, no IXGWRITE requests
the task that owned the connection to
for this log stream can be completed
the log stream and the structure for
until the date/time becomes current
which the offload was processing.
(as indicated in Message IXG218A).
System Programmer Until the appropriate date and time
Response:Restart any applications are reached, Logger will reject
that use the log stream identified in IXGWRITE requests with a return
message IXG114A. code X'0C'. A dump will be requested
to provide diagnostic information.
If the problem persists, contact the
IBM Support Center. Provide the
System Programmer Response: The
dump and logrec entries associated
most likely cause of this problem is
with this abend.
that the clock value for the sysplex
00040003 System Logger has detected that the has been adjusted backwards in time,
timestamp of the last block written for and that this log stream was written to
the current logstream is well in the while the clock was adjusted forward.
future. It is likely that this log stream If the time difference from the clock
was used in a clock adjusted testing adjustment or wait time indicated in
environment, and an attempt has message IXG218A is unacceptable, it
been made to reuse the log stream will be necessary to disconnect from
once testing was complete and the the log stream, delete it, redefine it,
clock has been set back to the and reconnect.
present or appropriate date/time. This
type of Logger ABEND condition has Any other reason codes indicate that an internal error
been known to occur during the has occurred.
following types of testing situations:
System action: The system will have issued message
v during Y2K testing. IXG063I in an attempt to identify the log stream (and CF
v during reverse migration from a structure) resources Logger was operating on at the
Mixed-CTN to an ETR-only network time of the ABEND. The system writes a dump and
on z/OS images on the CPC for records the error in logrec.
which the ETR ports are enabled. A
For the reason codes listed above, use the system
Coordinated Timing Network (CTN)
actions specifically listed.
is a collection of servers and
Coupling Facilities that are time System programmer response: Try disconnecting a
synchronized to a time value called log stream and connecting again. If the problem
Coordinated Server Time. A persists, contact the IBM Support Center. Provide the
Mixed-Coordinated Timing Network dump and logrec entries associated with this abend.
(Mixed-CTN) requires a Sysplex
Timer®, and allows for both an For the reason codes listed above, use the system
External Time Reference (ETR) programmers response specifically listed.
network and a Server Time Protocol Source: System Logger
(STP). Depending on how long the
stratum 2 server resides in
STP-timing mode, the TOD clock 1C6
may drift enough for Logger to Explanation: The system detected a possible overlay
detect that a system on an of a TCB field for a task that is the target of a STATUS
ETR-timing CPC might be less macro request. For more information about the STATUS
advanced than one on the macro, see z/OS MVS Programming: Authorized
STP-Timing CPC. This might be Assembler Services Reference SET-WTO.
encountered on any image on the
STP-timing server if they are System action: The system abnormally ends the
actively writing log blocks to a CF address space in which the task is running.
structure based log stream. System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
System Action: If the log stream had exists, contact the IBM support center.
been newly connected on a system
156 z/OS V1R10.0 MVS System Codes
1C7 • 1D0
Source: Task Management v WLM could not copy a local copy of
the parameter list back into the
caller’s copy.
1C7
Check the parameter list areas for the
Explanation: An error occurred during workload
service definition, service classification
manager (WLM) processing. The accompanying reason
rules, and notepad area. Ensure that
code identifies either an internal recoverable WLM error
correct storage keys are specified.
or an external error code as follows:
Code Explanation For all other reason codes, contact programmer service
support.
0Axx0004 An attempt to reference a caller’s
parameters caused an 0C4 abend. System programmer response:
xxxx0005 This is issued by WLM Module Code Response
IRASAQUE (Queue delay samples
1030003 This problem can result from an
gatherer). The QM sampling routine,
incorrect ″PTF apply″, that is, a PTF
QMSAM, has either returned with an
was not installed successfully. If you
error code, or it has abended an
cannot identify the respective PTF and
excessive number of times. This may
fix the problem, create a stand-alone
be the result of damage to the QM/EM
dump and contact the IBM Support
data structures, or it could also be a
Center. Provide the dump issued by
consequence of QMSAM running
the system.
unserialized.
WLM is rebuilding its internal For other reason codes, search problem reporting data
structure. bases for a fix for the problem. If no fix exists, contact
the IBM Support Center. Provide the dump.
1030003 This is issued during initialization of
the WLM address space when the
load of a WLM load module fails or 1D0
the load module is not in the nucleus.
Explanation: An error occurred during Common Event
System action: Adapter (CEA) processing. The accompanying reason
codes identify either an internal Common Event Adapter
Code System Action
error or an external error code as follows:
1030003 The system goes into a wait state.
Value Description
Operator response:
0001 The callable service was issued by a
Code Response program running with an FRR set.
0Axx0004 Notify the system programmer. Action: You must not issue the callable
xxxx0005 Ignore and continue, and notify service when an FRR is set. FRRs must be
system programmer if the problem deleted before calling the service.
persists. 0002 The callable service was issued by a
program running with a system lock held.
1030003 Notify the system programmer.
Action: You must not issue the callable
Application Programmer Response: Check for
service when a lock is held. Release the
possible programmer errors that might exist in a
locks before calling the service.
program that requests services from WLM.
0003 The callable service was not issued by a
Code Response
program running under a task.
0Axx0004 WLM could not access the parameter
Action: You must issue the callable service
list or parameters passed by the
only in task mode. SRB mode is not
IWMPQRY or IWMWQRY services.
supported.
The following are possible problems:
v WLM could not copy the parameter 0004 The callable service was issued in
list because the parameters could cross-memory mode.
not be accessed by storage key. Action: You must not issue the callable
v WLM could not copy the service service in cross-memory mode. Correct the
definition, service classification problem and resubmit the job.
rules, or the service notepad area
to a private copy.
Chapter 2. System Completion Codes 157
1E0 • 1FB
Value Description User response: Correct the application.
0005 The caller was not enabled. Operator response: None.
Action: You must enable the caller to invoke System programmer response: A LOGREC entry will
this service. be created to document that this error has occurred.
0007 The specified length for a CEA input Problem determination: Review SSI requirements in
argument is incorrect. z/OS MVS Using the Subsystem Interface.
Action: The length of a SIGNED or Source: JES2, JES3
UNSIGNED argument cannot be longer than
Detecting Module: HASCLINK, IATSIAU
8 bytes (64 bits).
0008 The specified type of a CEA input argument
1FA
is incorrect.
Explanation: The error occurred during execution of a
Action: Correct the type. The address of the
data management request for a spool data set. JES2
invalid type is in register 2.
found that the data management control blocks are no
0009 The input parameter list of the user is not longer valid.
accessible.
System programmer response: Obtain the program
Action: Check the input parameter list for the listing for the job. Look at the messages in the job log. If
service and verify that it is correct. the JOB statement did not specify MSGLEVEL=(1,1),
000A There is no security product. specify it and run the job again.
Action: Install a security product such as Probable user error. Verify that the problem program did
RACF and retry the request. not modify the data management control blocks. After
making the correction, execute the job step again.
Other reason codes from 0401 - 3FFF indicate that an If the problem recurs and if the program is not in error,
internal error has occurred. search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support
System action: Center.
Use the system actions specifically listed. Source: JES2 or DFSMSdfp
System programmer response: For the reason
codes listed above, contact the IBM Support Center. 1FB
Source: Common Event Adapter Explanation: JES3 may have issued one of the
following messages because of the indicated error:
Detecting Module: Many
IAT1601
The user is trying to perform I/O to a data set that
1E0
is closed.
Explanation: A JES SSI routine detected an error in
An incorrect IATYDAT was found on the data buffer
the information passed by the caller. Either an
block (DAT) queue.
unauthorized caller is attempting to use an SSI that
requires authorization or an SSI caller passed a data IAT1602
area to the SSI that it does not have access to. The One of the following control blocks either (1) could
return code in register 15 identifies the error. not be validated or (2) contains incorrect data:
IATYDAT, IATYDMC, IATYDSB or IATYDSS.
Code Explanation
IAT1603
04 An unauthorized caller (problem state and
A JES3 module passed, as a parameter to
non-authorized PSW storage key) invoked an
IATDMEB, a code that requested an incorrect data
SSI that requires the caller to be authorized.
management function.
08 A data area passed on an SSI could not be
IAT1604
accessed in the PSW storage key of the caller.
A start I/O operation in the user’s storage returned
Because this is a transformed ABEND code
an error code.
(original ABEND may have been an X'0C4'), it
is not possible to set a SLIP trap on this code IAT1605
to force an SVC dump. A start I/O operation in the user’s storage returned
an error code.
System action: The program invoking the SSI is
ABENDed.
158 z/OS V1R10.0 MVS System Codes
1FB
IAT1606 IAT6309
IATDMEB found an incorrect unprotected buffer A failure has occurred during an MVS LOAD or
(IATYDAT) address or the associated IATYDMC BLDL of a JES3 input service module.
address was incorrect.
If none of these messages appear, JES3 found an
IAT1607
incorrect IFGACB, IATYDSS, or IATYDSB control block
IATDMEB could not allocate an unprotected buffer.
or received an error return code as a result of a
IAT1609 SJFREQ request.
One of the following occurred:
System action: Depending on the error, the system
v When module IATDMEB or IATSIAD attempted ends either the job step or the user address space.
to set up a data management WAIT, the module
found a data management function already Application Programmer Response: If the problem
waiting. occurred in an I/O operation, correct any I/O errors in
your program. Then rerun the job.
v When module IATDMEB or IATSIAD attempted
to set up a subsystem interface WAIT, the If JES3 issued message IAT6309, correct the cause of
module found a subsystem function already the LOAD or BLDL failure. Then rerun the job.
waiting. Otherwise, notify your system programmer, supplying a
SYSABEND dump.
IAT1610
During ENDREQ processing, a request for macro System programmer response: If messages
IATYJDS failed. accompany this abend, register 3 in the dump points to
a copy of the data set status block (DSS). A
IAT1611
hexadecimal reason code explains the error. Use this
The JES3 SSVT was either (1) incorrect or (2)
reason code to determine the cause of the error.
could not be found.
Code Explanation
IAT1612
The SYSOUT class to be allocated is not 01 Module IATDMEB, while performing verification
alphanumeric. of the subsystem vector table (SVT), has found
that the SVT block ID (SVTID) is incorrect.
IAT1614
A failure occurred while processing a started task or 02 The data extent block (DEB) does not contain
TSO logon internal reader data set. the data set block (DSB) upon entry to
IATDMEB.
IAT1803
An attempt to move data from a JES3 protected 03 Module IATDMEB contains undefined function
buffer in the JES3 auxiliary address space to a user code.
storage unprotected buffer failed.
04 Module IATDMEB received an error code from
IAT6700 the IATXSIO macro while processing the GET
During deallocation, when attempting to update the routine.
JDSENTRY, the module could not find a job data
set (JDS) entry. 05 Module IATDMEB received an error code from
the IATXSIO macro while processing the data
IAT6703 management point routine.
When the module attempted communication, an
error that disrupted operations occurred in the 06 Module IATDMEB received an error code from
global processor. the IATXSIO macro while processing the SSI
point routine.
IAT6704
OPEN could not allocate a user address space 07 Module IATDMEB received an error code from
buffer to a data set. the IATXSIO macro while processing the GET
routine.
IAT6707
At deallocation of the external writer data set, the 08 Module IATDMEB received an error code from
module could not find an output scheduling element the IATXSIO macro while processing the
(OSE). PUT-Update routine.
IAT6708 09 Module IATDMEB contains a dynamic address
A permanent I/O error occurred on an output data translation (DAT) validation error. The DAT
set. address is out of range (too low).
IAT6711 0A Module IATDMEB contains a dynamic address
A SSISERV macro sent incorrect data to the global translation (DAT) validation error. The DAT
processor; the request could not be serviced. address is out of range (too high).
Chapter 2. System Completion Codes 159
1FB
0B Module IATDMEB received an error code from 1F Module IATSICC received a permanent I/O
the IATXSIO macro while processing error writing last buffer.
IATDMEBS routine.
20 Module IATDMFR received a failure in
0C Module IATDMEB received a busy return from IATDMEB channel end routine (IATDMEBS).
macro IATXUBAL while processing the buffer
21 Module IATDMEB received a cross memory
checkpoint routine.
move (IATXMVXM) error return.
0D Module IATDMEB received an error return from
22 Module IATDMEB detected the data set status
macro IATXUBAL while processing IATDMEBS
block id (DSSID) is not valid upon entry.
routine.
23 Module IATDMEB received an DSS validation
0E Module IATDMEB received an error code from
error. The SVT pointer (DSSSSVT) is incorrect.
the IATXSIO macro while processing
IATDMEBS routine. 24 Module IATDMEB received an DSB validation
error. DSB block ID (DSBID) is incorrect.
0F Module IATDMEB received an error code from
the IATXSIO macro while processing 25 Module IATDMEB received an error return from
IATDMEBS routine. UBUFF while processing the allocation routine.
10 Module IATDMEB received an error code from 26 Module IATDMEB received an error return from
the IATXSIO macro while processing IATXSIO while processing the IATDMEBS
IATDMEBS routine. routine.
11 Module IATDMEB received a busy return from 27 Module IATDMEB could not free user memory
macro IATXUBAL while processing IATDMEBS buffers. The DSS or DSB failed validation in
routine. module IATDMUB.
12 Module IATDMEB detected a CLOSE 28 Module IATDMEB received an DAT validation
serialization failure in the ENDREQ routine. error. DAT address is out of range (too low).
13 Module IATDMEB received a busy return form 29 Module IATDMEB received an DAT validation
macro IATXUBAL while processing IATDMEBS error. DAT address is out of range (too high).
routine.
2A Module IATDMEB received an SSISERV error
14 Module IATDMEB received an UBUFF while processing ENDREQ routine. The JIB
validation error while processing. DMC block ID block ID incorrect.
(DMCID) is incorrect.
2B Module IATDMEB received an error in JDS
15 Module IATDMEB found the data management access while processing ENDREQ routine.
wait already outstanding.
2C Module IATDMEB received an DMC validation
16 Module IATDMEB found the SSI wait already error. DMC address is out of range (too low).
outstanding.
2D Module IATDMEB received an DMC validation
17 Module IATDMEB received an error return from error. DMC address is out of range (too high).
macro IATXSIO.
2E Module IATDMEB received an DAT validation
18 Module IATDMEB received an DMC validation error. DAT address is out of range (too low).
error. The DMC block ID (DMCID) is incorrect.
2F Module IATDMEB received an DAT validation
19 Module IATDMEB received an DMC validation error. DAT address is out of range (too high).
error. DMC address is out of range (too low).
30 Module IATDMEB received an error return from
1A Module IATDMEB received an DMC validation spool record allocation (IATDMDKR).
error. DMC address is out of range (too high).
31 Module IATDMEB received an DAT validation
1B Module IATDMEB received an DAT validation error. DAT address out of range (too low).
error. DAT block ID (DATID) is incorrect.
32 Module IATDMEB received an DAT validation
1C Module IATDMEB received an DAT validation error. DAT address out of range (too high).
error. DAT address is out of range (too low).
33 Module IATDMEB received an DAT validation
1D Module IATDMEB received an DAT validation error. DAT block ID (DATID) is incorrect.
error. DAT address is out of range (too high).
34 Module IATDMEB received an DAT validation
1E Module IATDMEB received a GETMAIN failure error. DAT address out of range (too low).
while processing ENDREQ routine.
35 Module IATDMEB received an DAT validation
error. DAT address out of range (too high).
160 z/OS V1R10.0 MVS System Codes
1FB
36 Module IATDMEB received an DAT validation 4D GETMAIN failed while processing a started
error. DAT block ID (DATID) is incorrect. task or TSO logon request.
37 Module IATDMEB received an DAT validation 50 Module IATSIAD received an SSISERV error
error. DAT address is out of range (too low). return.
38 Module IATDMEB received an DAT validation 51 Module IATSIAD received an SSISERV error
error. DAT address is out of range (too high). return.
39 Module IATDMEB received an DAT validation 52 Module IATSIAD received an SSISERV error
error. DAT block ID (DATID) is incorrect. return. The job is marked delete only.
3A Module IATDMEB received an error while 53 Module IATSIAD received a catastrophic error
adding a data set status block (DSS) to the from SSISERV.
record allocation block (RAB) queue during
54 Module IATSIAD detected bad data was sent
write error recovery.
during SSISERV processing.
3B Module IATDMEB received an error while
55 Module IATSIAD received an error during PSO
adding a data set status block (DSS) to the
unallocation from SSISERV error return.
record allocation block (RAB) queue after
IATXSIO processing. 56 Module IATSIAD received an SSISERV error
return. There was no job number available.
3C Module IATDMEB received an error while
resetting a data set status block (DSS). 57 Module IATSIAD received an SSISERV error
return.
3D Module IATDMEB received an error while
adding the data set status block (DSS) to the 58 Module IATSIAD received an SSISERV error
record allocation block (RAB) queue. return.
40 Module IATDMDM received an incorrect ACB 59 Module IATSIAD received an DSB message
on entry. code not valid.
41 Module IATDMDM received an DSB validation 5A A JES3 module received an allocation request
error. DSB block ID (DSBID) incorrect. for a SYSOUT class that is not A-Z or 0-9.
42 Module IATDMDM received an DSS validation 60 Module IATSIOR detected an OPEN
error. DSS block ID (DSSID) incorrect. serialization failure.
43 Module IATDMDM received an incorrect DAT 61 Module IATSIOR detected an OPEN
address while processing the PUT routine. serialization failure.
44 Module IATDMDM received an incorrect buffer 62 Module IATSIOR found ORT not available.
point while processing the PUT routine.
63 Module IATSIOR found ORT not available.
45 Module IATDMDM found that no room remains
in the buffer while processing the PUT routine. 64 Module IATSIOR received an error return from
IATSIOD module.
46 Module IATDMDM received an DAT validation
error. DAT address out of range (too low). 65 Module IATSIOR found the user writer name
was not specified.
47 Module IATDMDM received an DAT validation
error. DAT address out of range (too high). 66 Module IATSIOR received an SSISERV error
return. The job was marked delete-only.
48 Module IATDMDM received an unsuccessful
GETMAIN while processing the ENDREQ 67 Module IATSIOR received a catastrophic error
routine. from SSISERV.
49 Module IATDMDM received an input service 68 Module IATSIOR did not find a job data set
error while processing the ENDREQ routine. (JDS).
4A Module IATDMDM did not receive the JOBID 69 Module IATSIOR received an SSISERV error
from input service while processing the return. There was no job number available.
ENDREQ routine. 6A Module IATSIOR received a BUSY return from
4B Module IATDMDM received an error re-opening the buffer allocation routine.
INTRDR data set while processing the PUT 6B Module IATSIOR received an error while
routine. adding a data set status block (DSS) to the
4C Module IATDMDM detected serialization failure record allocation block (RAB) queue after an
in the PUT routine. error during OPEN processing.
Chapter 2. System Completion Codes 161
1FB
6C Module IATSIOR received an SSISERV error 92 Module IATDMDM received an error code from
return. The job is marked delete only. a call to IXZXIXSM. SEGTYPE=FIRST was
specified on the call.
6D Module IATSIOR detected an OPEN
serialization failure. 93 Module IATDMDM received an error code from
a call to IXZXIXSM. SEGTYPE=LAST was
6E Module IATSIOR detected an OSE buffer
specified on the call.
number overflow.
94 Module IATDMDM received an error code from
| 6F A JES3 module received a JDS pointer value
a call to IXZXIXAC.
| that was zero during DS OPEN processing.
95 Module IATDMDM received an error code from
70 Module IATSICC received an SSISERV error
a STORAGE RELEASE request.
return. The job was marked delete-only.
96 Module IATDMDM found no output buffer or
71 Module IATSICC received an SSISERV error
the buffer failed validation.
return while processing INTRDR job.
A0 Module IATDMDS, while processing a chain of
72 Module IATSICC received a catastrophic error
DMCs, found them chained in a circular chain.
from SSISERV.
A1 Module IATDMDS, while in the Link-up routine,
73 Module IATSICC received an SSISERV error
detected an error in processing the Extent
return. Bad data was sent.
Busy queue.
74 Module IATSICC received an SSISERV error
A8 Module IATDMIT detected that the channel
return. The job number is not available.
program for I/O request was incomplete while
75 Module IATSICC detected a CLOSE the request complete normally.
serialization failure.
A9 Module IATDMIT detected a failure when
76 Module IATSICC detected a PUT serialization attempting to a DSS to the SRB Wait Queue.
failure.
AA Module IATDMIT detected a failure when
77 Module IATSICC detected an INTRDR attempting to reset a DSS after it had been
serialization failure. No task was holding the removed from the Protect Buffer (PBUF) Wait
DSBOCTCB lock. Queue.
78 Module IATSICC detected an INTRDR AB Module IATGRSP detected a failure when
serialization failure. Some other task was releasing the DSB spinoff lock.
already holding the DSBOCTCB lock.
AC Module IATGRSP detected a failure writing a
79 Module IATSICC detected an INTRDR buffer.
serialization failure. The DSBOCTCB lock was
AD Module IATGRSP detected a failure freeing
overlayed while processing the INTRDR close
unprotected buffers (UBUFs).
request.
AE Module IATGRSP detected a failure obtaining
80 Module IATDMFR received a failure in module
UBUFs .
IATSIAD while processing the IATSIADD
routine. AF Module IATGRSP detected a failure during a
dataset point operation.
| 81 Module IATDMDK failed when adding a DSS to
| the PBUF wait queue. B0 Module IATGRSP detected a failure during
spinoff processing.
| 82 Module IATDMDK failed when adding a DSS to
| the SRB wait queue. B1 Module IATGRSP detected a failure trying to
obtain the UBUF lock.
| 83 Module IATDMDK failed when attempting to
| reset the DSS after it was removed from the B2 Module IATGRSP detected a failure when
| RAB wait queue. freeing the UBUF lock.
| 84 Module IATDMER failed when adding a DSS to C0 Module IATDMEB detected an error in the
| the SRB wait queue. EBR000 routine. The EBGETUBF service
returned +0.
90 Module IATDMDM received an error code from
a STORAGE OBTAIN request. C1 Module IATDMEB detected an error in the
EBR000 routine. The EBGETUBF service
91 Module IATDMDM received an error code from
returned +0.
a call to IATGRAS.
162 z/OS V1R10.0 MVS System Codes
1FC • 200
C2 Module IATDMEB - the IATDMEBS routine - 2. Search problem reporting data bases for a fix for the
detected an error. The EBGETUBF returned problem. If no fix exists, ask the operator to set a
+0. SLIP trap to obtain an SVC dump. Contact the IBM
Support Center. Provide the SVC dump and, if
C3 Module IATDMEB detected an error in the Data
available, the logrec data set error record.
Management Point routine when the IATXSIO
call returned via its error return. Source: Supervisor control
C4 Module IATDMEB - the IATDMEBS routine -
detected an error when freeing the buffer 200
pointed to by DSBLSTBF.
Explanation: During a validity check of an I/O request,
C5 Module IATDMEB detected an error in the execute channel program (EXCP) processing
EBT000 routine. The EBGETUBF service encountered an error. Each X'200' abend code has a
returned +0. three digit reason code that explains the error. Each
digit of the reason code has a specific meaning:
C6 Module IATDMEB detected an error in the
EBT000 routine. The EBGETUBF service First Digit - The first digit in the reason code indicates
returned +0 the type of error:
C7 Module IATDMEB detected an error in the Code Explanation
EBG000 routine. The read buffers were not in
1nn Storage protection check. The storage
a sequential order.
protection key of one of the control blocks
C8 Module IATDMEB, the Data Management Point being tested was not the same as the storage
routine, detected an error when the IATXSIO protection key in the caller’s request block
call returned via its error return. (RB).
D0 Module IATDMEB or IATGRSP detected that a 2nn Segment translation error. A segment exception
job termination request was made before the occurred when EXCP processing was
data management request was processed. processing a control block.
| D1 Module IATDMEB detected zero DATPREV A segment exception occurs when EXCP uses
| when searching backward during a POINT an incorrect address. The incorrect address
| operation. results from one of the following:
| D2 Module IATDMEB found the current UBUF v The caller may have passed an incorrect
| chained to the list of waiting buffers. address.
v The storage area that the address is
| D3 The DMC failed validation in the GET routine
obtained from may have been overlaid.
| of IATDMEB.
v The control block that the address points to
| D4 Module IATDMEB was unable to allocate a may have been prematurely freed.
| buffer for a spool browse GET.
v Necessary data sets were prematurely
Source: JES3 closed.
3nn Page translation error.
1FC
A page translation error occurs when EXCP
Explanation: In response to a Supervisor Call (SVC) uses an incorrect address. The incorrect
instruction, the SVC first level interrupt handler (FLIH) address results from one of the following:
was running, but a system error occurred. v The caller may have passed an incorrect
System action: In an attempt to recover, the system address.
abnormally ends the task that issued the SVC v The storage area that the address was
instruction. The system writes a logrec data set error obtained from may have been overlaid.
record. v The control block that the address points to
Operator response: If the system programmer asks may have been prematurely freed.
for an SVC dump, set the following SLIP trap: v Necessary data sets were prematurely
SLIP SET,COMP=1FC,ACTION=SVCD,END closed.
System programmer response: Do the following: Second Digit - The second digit in the reason code
1. Find the original abend causing the problem in the indicates the phase of processing when that the error
system diagnostic work area (SDWA) in the logrec occurred:
data set error record for abend X'1FC'.
Code Explanation
Chapter 2. System Completion Codes 163
201 • 202
n1n EXCP encountered an error during the front
201
end processing.
Explanation: During processing of a WAIT macro, the
n2n EXCP encountered an error during the back
system found either:
end processing. Back end processing includes
DASD ERP, PCI, PURGE, and FRR routines. v The macro expansion contained an incorrect address
for an event control block (ECB)
n3n EXCP encountered an error during the
v The program issuing the WAIT macro was not
post-processing.
running under the same storage protection key as the
n4n EXCP encountered an error while updating the storage containing the ECB
data control block (DCB) during the validity
System action: The system abnormally ends the
check.
program that issued the WAIT macro.
n5n EXCP encountered an error while processing a
Application Programmer Response: Ensure that the
related. request.
ECB address specified is a valid virtual storage address
n5n EXCP encountered an error while processing and that it was not incorrectly modified. Correct the
the PCI appendage. error. Run the job again.
System programmer response: If the error recurs
Third Digit - The third digit in the reason code indicates and the program is not in error, look at the messages in
which control block was being tested when EXCP the job log for more information. Search problem
encountered the error: reporting data bases for a fix for the problem. If no fix
Code Explanation exists, contact the IBM Support Center. Provide the
program listing and the assembly listing associated with
nn1 Input/output block (IOB) the job.
nn2 Data control block (DCB) Source: Task management
nn3 Data extent block (DEB)
nn4 Event control block (ECB) 202
nn5 Input/output block extension (IOBE) Explanation: During processing of a POST macro, the
system found an error with an event control block
nn6 I/O error data block (IEDB) (ECB).
System action: The system abnormally ends the Register 15 contains a hexadecimal reason code that
current task and issues a SNAP dump. explains the error:
Application Programmer Response: Correct the Code Explanation
problem that the reason code indicates. Verify also that
the data set was opened and that the control block 00 The system found an incorrect address for a
indicated was correctly modified by the problem request block (RB) in the 3 low-order bytes of
program. the ECB specified by the problem program.
If the EXCP access method is being used, ensure that The system places the address of the RB in
the IOB and the ECB are correctly built. Correct the the ECB during processing of a WAIT macro.
error. Run the job again. This address must remain in the ECB until a
POST macro places a post code or zeros in
If the error recurs and you cannot determine the cause, the ECB.
run the job again, requesting an ABEND dump. Notify
the system programmer. 04 The waiting RB is not enabled for interrupts.
System programmer response: In the dump, look at 08 For a POST in a problem program protection
field TCBEXCPD at offset X'C0' in the task control block key and a WAIT in a system protection key, the
(TCB) of the current task. TCBEXCPD points to the ECB to be posted does not match any ECB
EXCP debugging area (XDBA). The XDBA contains being waited on.
diagnostic data associated with the EXCP processor. 0C For a WAIT in a problem program protection
If the error recurs and the program is not in error, look key, the ECB address is incorrect. This can
at the messages in the job log for more information. also mean that the program issuing the WAIT
Search problem reporting data bases for a fix for the has specified a list of ECBs and one of those
problem. If no fix exists, contact the IBM Support ECBs is not valid. This could happen if the
Center. Provide the JCL for the job and the dump. ECB storage has been released by another
process.
Source: Execute channel program (EXCP)
System action: The system abnormally ends the
program that issued the POST macro.
164 z/OS V1R10.0 MVS System Codes
204 • 206
Application Programmer Response: Ensure that the v The address of the parameter list specified in the
contents of the ECB were not modified after the WAIT macro instruction was erroneous.
macro and before the POST macro. Correct the error. v The address of the name (if EP or EPLOC was
Run the job again. specified), or the address of the directory entry (if DE
System programmer response: If the error recurs was specified) was erroneous.
and the program is not in error, look at the messages in v The parameter list pointed to by the macro contains a
the job log for more information. Search problem nonzero value in an undefined field.
reporting data bases for a fix for the problem. If no fix v The caller is not authorized to use the options
exists, contact the IBM Support Center. Provide the specified in the macro.
program listing and the assembly listing associated with
v The LOAD macro includes conflicting options.
the job.
v The LOAD macro includes the ADDR parameter, but
Source: Task management addr is not a doubleword boundary.
v An incorrect alias name was detected.
204
The reason code in register code 15 identifies the error:
Explanation: An error occurred when the system tried
to process an EC, EU, LC, LU, VC or VU form of the Code Explanation
GETMAIN macro. During request processing, the
system tried to get local system queue area (LSQA) 04 A LOAD macro was issued with conflicting
storage to support the request, but no central storage is options. One of the following occurred:
available to back the LSQA storage. v The EOM (delete module at end of memory)
keyword, with the GLOBAL keyword omitted.
System action: The system abnormally ends the The EOM keyword applies only if the
address space where the job was running. module is loaded into CSA storage.
Application Programmer Response: Run the job v The GLOBAL and ADDR keywords are both
step again. If the system issues this abend again, notify specified.
the system programmer. v The ADDR and LOADPT keywords are both
System programmer response: Search problem specified.
reporting data bases for a fix for the problem. If no fix 08 An unauthorized program attempted to run a
exists, contact the IBM Support Center. LOAD macro that had the load to global
Source: Virtual storage manager (VSM) feature (GLOBAL keyword).
0C An unauthorized program attempted to run a
205 LOAD macro that had the explicit load option
(ADDR keyword).
Explanation: An error occurred when the system tried
to process an EC, EU, LC, LU, VC or VU form of the 10 One of the following occurred:
FREEMAIN macro. During request processing, the v An unauthorized program attempted to run a
system attempted to get local system queue area SYNCH macro having the KEYADDR,
(LSQA) storage to support the request, but no central STATE, or KEYMASK operands. These
storage is available to back the LSQA storage. operands are available only to authorized
programs.
System action: The system abnormally ends the
address space where the job was running. v Reserved bits in the first word of the SYNCH
macro parameter list have nonzero values.
Application Programmer Response: Run the job
step again. If the system issues this abend again, notify 14 The requested name is an alias for another,
the system programmer. already loaded, alias.
System programmer response: Search problem 18 A LOAD macro was issued with the ADDR
reporting data bases for a fix for the problem. If no fix keyword but the value of the ADDR keyword,
exists, contact the IBM Support Center. the address, is not a doubleword boundary.
Source: Virtual storage manager (VSM) 1C A SYNCHX macro was issued with an XMENV
operand that contains an incorrect length
indicator.
206
20 The macro level for this macro is not
Explanation: An error occurred during processing of a compatible with this system.
LINK(X), LOAD, XCTL(X), DELETE, or SYNCH macro.
The control program detected one of these errors: 24 The program issuing the macro is in AR mode,
but the parameter list address does not have
an access list entry table (ALET) of zero.
Chapter 2. System Completion Codes 165
20A • 20E
Callers in AR mode must qualify the parameter modified. After making corrections, run the job step
list address with an ALET of zero. again.
28 Either the EP (entry point) keyword parameter System programmer response: See the system
or the DE (list entry address) keyword programmer response for messages issued to the
parameter does not have an ALET of zero. console or the job log.
2C The data control block (DCB) address (DE) If the error recurs and the program is not in error,
keyword parameter does not have an ALET of search problem reporting data bases for a fix for the
zero. problem. If no fix exists, contact the IBM Support
Center. Provide the ABEND dump and the source
30 An incompatible level of TSO/E is being used
program listing for the job.
with a PDSE load module.
Source: Contents supervision (CSV)
34 An incorrect byte was supplied in the DE
parameter.
20A
C0 A parameter was not addressable or was in the
wrong storage key. Explanation: An error occurred when the system tried
to process an R form of the GETMAIN or FREEMAIN
C4 The directory entry passed in the data control
macro. During request processing, the system
block (DCB) address (DE) keyword parameter
attempted to get local system queue area storage
was not addressable or was in the wrong
(LSQA) to support the request, but no central storage is
storage key.
available to back the LSQA storage.
C8 The data control block (DCB) was not
System action: The system abnormally ends the
addressable or was in the wrong storage key.
address space where the job was running.
CC The data extent block (DEB) was not
Application Programmer Response: Run the job
addressable or was in the wrong storage key.
step again. If the system issues this abend again, notify
System action: The system issues an ABEND dump. the system programmer.
The system issues a message depending on the reason
System programmer response: Search problem
code accompanying the abend:
reporting data bases for a fix for the problem. If no fix
Code Explanation Message exists, contact the IBM Support Center.
04 CSV010I Source: Virtual storage manager (VSM)
08 CSV014I
20D
0C CSV018I
Explanation: An abend occurred in a subtask. The
10 CSV012I subtask either:
14 CSV023I v Operated in step-must-complete (MC) status
v Issued an ABEND macro with the STEP option
18 CSV022I
As a result, the system abnormally ended the job step.
1C CSV012I
20 CSV029I Note: The original abend code is in the TCBCMP field
of the task control block (TCB) for the subtask
24 CSV029I that caused the error.
28 CSV029I System action: The system ends the job step. The
2C CSV029I system writes an ABEND dump for the failing job step, if
it provides a dump data set.
30 CSV040I
Application Programmer Response: Find the original
Application Programmer Response: See the abend code in the TCB of the subtask that caused the
application programmer response for messages error. Continue diagnosis with that abend.
accompanying this abend issued to the console or the
job log. Source: Recovery termination manager (RTM)
Check for program errors that incorrectly modify the
parameter list. If the DE operand is specified, check that 20E
the macro is correct for the attributes of the requested Explanation: A program issued a SPIE macro that
module. Ensure that the address specified in the EP, specified an incorrect address for the SPIE program
EPLOC or DE operand is not incorrectly specified or interruption element (PIE).
166 z/OS V1R10.0 MVS System Codes
20F • 215
System action: The system sends messages about Source: DFSMSdfp
the problem to the job log. The system abends the
program that issued the SPIE macro.
213
Operator response: If the system programmer asks
Explanation: The error occurred during processing of
for an SVC dump, set the following SLIP trap:
an OPEN macro instruction for a direct access device.
SLIP SET,COMP=20E,ACTION=SVCD,END This system completion code is accompanied by
Application Programmer Response: If an application message IEC143I. Refer to the explanation of message
program issued the incorrect macro, correct the PIE IEC143I for complete information about the task that
address, ensuring that it is a valid virtual storage was ended and for an explanation of the return code (rc
address assigned to the job step. Rerun the job. in the message text) in register 15.
System programmer response: If an IBM program Application Programmer Response: Respond as
issued the macro, search problem reporting data bases indicated to the applicable message.
for a fix for the problem. If no fix exists, contact the IBM System programmer response: If the error recurs
Support Center. Provide: and the program is not in error, look at the messages in
v Messages from the job log the job log for more information. Search problem
v The ABEND or SVC dump reporting data bases for a fix for the problem. If no fix
v The assembly listing for the job exists, contact the IBM Support Center. Provide the JCL
v The JCL for the job and the program listing for the job.
v The program listing for the job
Source: DFSMSdfp
Source: Recovery termination manager (RTM)
214
20F
Explanation: The error occurred during processing of
Explanation: A program tried to issue the ERREXCP a CLOSE macro instruction for a data set on magnetic
macro. The program was not in supervisor state. tape. This system completion code is accompanied by
System action: The system abnormally ends the message IEC210I. Refer to the explanation of message
current task. The system does not process the macro. IEC210I for complete information about the task that
was ended and for an explanation of the return code (rc
Application Programmer Response: Remove the in the message text) in register 15.
ERREXCP macro from the program.
Application Programmer Response: Respond as
Source: Input/output supervisor (IOS) indicated for message IEC210I.
System programmer response: If the error recurs
212 and the program is not in error, look at the messages in
Explanation: An error occurred during the processing the job log for more information. Search problem
of SVC 18; the error could not be attributed to incorrect reporting data bases for a fix for the problem. If no fix
user input. This system completion code is exists, contact the IBM Support Center. Provide the JCL
accompanied by message IEC909I. Refer to the and the program listing for the job.
explanation of message IEC909I for complete Source: DFSMSdfp
information about the task that was ended and for an
explanation of the return code in register 15.
215
System action: Message IEC909I is issued indicating
whether a dump was taken to the SYS1.DUMP data Explanation: The error occurred during the processing
set. of SVC 21 (STOW). This system completion code is
accompanied by message IEC910I. Refer to the
Application Programmer Response: Make sure that explanation of message IEC910I for complete
the BLDL or FIND macro instruction is correctly coded, information about the task that was ended and for an
and that the parameter list and control blocks involved explanation of the return code in register 15.
are not modified by your program during the processing
of SVC 18. System action: The STOW task recovery routine has
been invoked. If the caller’s DCB is in the caller’s
System programmer response: If the error recurs region, an attempt was made to trace it to the
and the program is not in error, look at the messages in SYS1.TRACE data set.
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix Operator response: Start a generalized trace facility
exists, contact the IBM Support Center. Provide the (GTF) trace, and re-create the problem. Reply to
JCL, the program listing for the job, and the logrec data message AHL100A with:
set error record. TRACE=SYS,USR,SLIP
Chapter 2. System Completion Codes 167
218 • 22A
On the DD statement for the data set in error, specify: the job log for more information. Search problem
DCB=DIAGNS=TRACE reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL
Application Programmer Response: For return and the program listing for the job.
codes 01, 02, and 03, verify that register 1 contained
the correct DCB address prior to issuing SVC 21 and Source: DFSMSdfp
that the DCB has not been overlaid since being opened.
For return code 04, verify that register 0 contained the 222
correct parameter list address and that the list is within
the caller’s region prior to issuing SVC 21. Explanation: The operator, or an authorized time
sharing option extensions (TSO/E) user, canceled the
System programmer response: If the error recurs job without requesting a dump.
and the program is not in error, look at the messages in
the job log for more information. Search problem System action: The system ends the job. In some
reporting data bases for a fix for the problem. If no fix cases, the system might write a dump even though a
exists, contact the IBM Support Center. Provide the JCL dump was not requested, depending on which system
and the program listing for the job. routine has control.
Source: DFSMSdfp Application Programmer Response: Find out why
the operator or TSO/E user canceled the job. Correct
any errors and resubmit the job. If you want a dump,
218 have the operator resubmit the job and then cancel it
Explanation: An error occurred during the processing using the command CANCEL jobname, DUMP.
of DEVTYPE (SVC 24) that could not be attributed to Source: Master scheduler
incorrect user input. This system completion code is
accompanied by message IEC913I.
228
Refer to the explanation of message IEC913I for
complete information about the task that was ended and Explanation: During processing of an EXTRACT
for an explanation of the return code in register 15. macro, the system found that the location of the input
parameter list was incorrect. The input parameter list,
Application Programmer Response: Make sure that ordinarily created through expansion of the standard or
the DEVTYPE macro instruction is correctly coded, and MF=L form of the EXTRACT macro, describes the
that the areas passed to DEVTYPE are not freed by function to be performed.
your program during the processing of SVC 24.
The starting address indicated that the parameter list
System programmer response: If the error recurs did not begin either on a fullword boundary or within the
and the program is not in error, look at the messages in storage assigned to the job step.
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix System action: The system abnormally ends the
exists, contact the IBM Support Center. Provide the JCL program that issued the EXTRACT macro.
and the program listing for the job. Application Programmer Response: Correct the
Source: DFSMSdfp program so that the address of the input parameter list
is valid. Run the job again.
219 System programmer response: If the error recurs
and the program is not in error, look at the messages in
Explanation: An error occurred during the processing the job log for more information. Search problem
of SVC 25 that could not be attributed to incorrect user reporting data bases for a fix for the problem. If no fix
input. This system completion code is accompanied by exists, contact the IBM Support Center. Provide the
message IEC915I. Refer to the explanation of message source program listing for the job.
IEC915I for complete information about the task that
was ended and for an explanation of the return code in Source: Task management
register 15.
System action: Message IEC915I is issued to indicate 22A
whether a dump was taken to the SYS1.DUMP data Explanation: During processing of an ATTACH macro,
set. the system found an error.
Application Programmer Response: Make sure that Register 15 contains a hexadecimal code that explains
your program does not alter the DCB or IOB during the the error:
processing of SVC 25.
Code Explanation
System programmer response: If the error recurs
and the program is not in error, look at the messages in 00 The issuer of the ATTACH macro specified a
168 z/OS V1R10.0 MVS System Codes
22C • 230
GSPV, GSPL, SHSPV, or SHSPL parameter
22D
with a subpool ID greater than 127.
Explanation: A program requested an overlay. When
System action: The system abnormally ends the
trying to answer the request, the overlay supervisor
program that issued the ATTACH macro.
found an incorrect address in the overlay segment table
Application Programmer Response: Change the or the entry table. The address points to a location
macro to specify a problem program subpool (1 through outside the boundaries of the virtual storage assigned to
127). If the macro is specified correctly, check for the job step.
program errors that incorrectly modify it. Correct the
The overlay segment table is used by the overlay
error. Run the job again.
supervisor; it resides in the load module and is in the
System programmer response: If the error recurs same storage protection key as the application program.
and the program is not in error, look at the messages in
the job log for more information. Gather GTF trace data Note: Overlay programs run only in 24-bit addressing
using trace option keyword TRACE=SYSP and event mode, not in 31-bit addressing mode.
keyword SVC=42,END.
System action: The system abnormally ends the
Search problem reporting data bases for a fix for the program that requested the overlay. The system writes
problem. If no fix exists, contact the IBM Support an ABEND dump, if a dump DD statement is provided.
Center. Provide the source program listing for the job.
Application Programmer Response: Check the
Source: Task management program for errors that caused the overlay segment
table or the entry table to be incorrectly modified.
Correct the errors; then assemble, link edit, and run the
22C
program again.
Explanation: During processing of a CHAP macro, the
Source: Overlay supervisor
system found that the address of the fullword specified
in the second operand is incorrect. This fullword
contains the address of the task control block (TCB) for 22F
the subtask whose priority was to be changed.
Explanation: No usable combination of time-of-day
The address was incorrect for one of the following (TOD) clock and clock comparator (REAL or WAIT type
reasons: request) or no usable CPU timer (TASK type request) is
v It was not a multiple of 4. available.
v The addressed virtual storage has not been
Application Programmer Response: Probable
allocated.
hardware error with the system clocks. Contact
v The protection key of the fullword does not match the
hardware support.
protection key of the issuer of the CHAP macro.
Source: Supervisor control and timer supervision
System action: The system abnormally ends the
program that issued the CHAP macro.
230
Application Programmer Response: Change the
CHAP macro to specify a valid fullword address. Ensure Explanation: Global resource serialization
that this fullword will contain the address of the TCB encountered an error during processing of a DEQ
when the CHAP macro is processed. Also, ensure that macro.
the problem program does not incorrectly modify the
specification. Correct the error. Run the job again. The DEQ macro specified an incorrect length for the
resource name. The length was specified in the rname
System programmer response: If the error recurs length operand of the DEQ macro instruction, was
and the program is not in error, look at the messages in supplied by the assembler program, or was contained in
the job log for more information. Format a GTF trace, the byte immediately preceding the resource name.
using trace option keyword TRACE=SVCP and using
event keywords SVC=44,END. System action: The system issues an ABEND dump.
Search problem reporting data bases for a fix for the Application Programmer Response: Correct the
problem. If no fix exists, contact the IBM Support incorrect macro instruction or the program errors that
Center. Provide the source program listing for the job. incorrectly modified the length. Recompile the program
and run the job step again.
Source: Task management
System programmer response: If the problem
persists, search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support
Center. Provide the abend dump.
Source: Global resource serialization
Chapter 2. System Completion Codes 169
233
58 The caller’s storage list is not accessible.
233
5C The caller’s header data is not accessible.
Explanation: The caller passed incorrect parameters
in a request for an SVC dump. 60 The caller-supplied event control block (ECB)
is not accessible.
Register 15 contains a hexadecimal reason code that
explains the error: 64 The caller’s ASID list is not accessible.
Code Explanation 68 The caller’s SUMLIST is not accessible.
04 The address of the parameter list is zero, or 6C The caller’s subpool identification (ID) list is not
the caller is in AR ASCMODE and the access accessible.
register of the parameter list is non-zero.
70 The caller’s storage key list is not accessible.
08 The parameter list is not a valid SVC dump or
SNAP parameter list. 74 A copy of SLIP registers and a copy of the
program status word (PSW) are not accessible.
0C The caller-supplied data set is on an
unsupported device. 78 The caller-supplied SRB is not accessible.
10 One of the following: 7C An incorrect version number is in the
parameter list.
v In a caller-supplied storage range, the start
address is greater than or equal to the end 80 The caller-supplied LISTD or LIST64 list is not
address. accessible.
v For any of the LIST, STORAGE and 84 The caller-supplied SUMLSTL or SUMLIST64
SUMLIST parameters, the high-order bit of list is not accessible.
the last ending address was not set to B'1'.
88 SDUMPX parameter list contained conflicting
v For any of the LISTA, LISTD, LIST64,
parameters.
SUMLSTA, SUMLSTL and SUMLIST64
parameters, the length of the list or the 8C The ID is longer than 50 characters.
number of ranges was not correctly
90 The ID is not addressable.
specified.
94 The PSW/register area is an incorrect length.
14 The caller-supplied data for the HDR or
HDRAD option is greater than 100 characters. 98 The PSWREGS is not addressable.
18 The caller requested the 4-kilobyte system 9C The symptom record is incorrect.
queue area (SQA) buffer, but it is not
serialized. A0 The symptom record is not addressable.
1C The parameter list or what it points to is in the A4 The data extent block (DEB) for the
4-kilobyte SQA buffer. caller-supplied DCB is not accessible.
20 The caller supplied a data control block (DCB) AC The STRLIST area supplied by the caller is not
address, and the DCB is not open or the accessible.
address is not valid. B0 The caller-supplied INTOKEN area is not
28 An address space identifier (ASID) specified in accessible.
the ASIDLST, ASID, or SUBPLST parameter is B4 The caller-supplied REMOTE area is not
incorrect. The ASID is less than zero or greater accessible.
than the maximum value.
B8 The caller-supplied PROBDESC area is not
38 The caller specified the 4-kilobyte SQA buffer, accessible.
but an SVC dump function was already in
progress. BC The caller-supplied JOBLIST area is not
accessible.
44 The caller specified a subpool greater than the
maximum value allowed (255). C0 The caller-supplied DSPLIST area is not
accessible.
| 47 An inconsistency was detected in the SDUMP
| parameter list that might be resolved by C4 The caller-supplied REMOTE area is not valid;
| zeroing the storage for the list before calling the length of a field in the area is specified as
| the SDUMPX macro. less than 4 bytes.
50 Not all of the parameter list is accessible. System action: The system writes a logrec data set
error record. SVC dump processing attempts retry and
54 The caller-supplied DCB is not accessible. gives the caller a return code of 8 and an associated
170 z/OS V1R10.0 MVS System Codes
235 • 239
reason code. If retry is not possible, the system in the message text) in register 15.
abnormally ends the caller. SVC dump processing
Application Programmer Response: Respond as
issues message IEA911E or IEA611I. This message
indicated for message IEC023I.
indicates whether the dump is complete or partial.
System programmer response: If the error recurs
System programmer response: For reason code
and the program is not in error, look at the messages in
X'AC', make sure the STRLIST area specified is
the job log for more information. Search problem
addressable from the caller’s current address space.
reporting data bases for a fix for the problem. If no fix
Then request the dump again.
exists, contact the IBM Support Center. Provide the JCL
For all other reason codes, correct the incorrect and the program listing for the job.
parameters and issue the SDUMP macro again.
Source: DFSMSdfp
If the problem persists or is in an IBM-provided
program, search problem reporting data bases for a fix
238
for the problem. If no fix exists, contact the IBM Support
Center. Provide the assembly listing for the job. Explanation: The error occurred during processing of
an ENQ macro instruction during the processing of
Source: Dumping services
global resource serialization. An incorrect length was
specified for the name representing the resource. This
235 length was specified in the rname length operand of the
ENQ macro instruction, was supplied by the assembler
Explanation: An error occurred during processing
program, or was contained in the byte immediately
associated with SVC 53, which obtains and releases
preceding the resource name.
exclusive control of a resource associated with a BDAM
data set. The task recovery routine for this SVC System action: The system issues an ABEND dump.
determined that a control block required as input to SVC
Application Programmer Response: Correct the
53 was not in the user’s region and/or key. This system
incorrect macro instruction or the program errors that
completion code is accompanied by message IEC902I.
incorrectly modified the length. Recompile the program,
Refer to the explanation of message IEC902I for
and run the job step again.
complete information about the task that was ended and
for an explanation of the return code in register 15. System programmer response: If the problem
persists, search problem reporting data bases for a fix
System action: Message IEC902I is issued,
for the problem. If no fix exists, contact the IBM Support
specifying a cleanup code that indicates the results of
Center. Provide the ABEND dump.
the cleanup of resources attempted by the recovery
routine. Source: Global resource serialization
Application Programmer Response: Insure the
validity of the control block from which the address of 239
the block in error was taken. For example, make sure
that the input specified in the RELEX macro, the Explanation: An error occurred during the processing
BLKREF address, is valid and in the correct format and associated with SVC 57, which frees a buffer or extends
that the DCB address passed is valid. If a RELEX the unscheduled text (via the FREEDBUF macro issued
macro was not issued, make sure that the IOB related either by the user or the system). The BDAM task
to the exclusive control request is correct and contains recovery routine for this SVC determined that a control
the correct DECB address (IOBECBPT) and DCB block required as input to SVC 57 was not in the user’s
address (IOBDCBPT). region and/or key. This system completion code is
accompanied by message IEC902I. Refer to the
In addition, check the DCBEBAD field in the DCB to explanation of message IEC902I for complete
ensure that it contains the correct DEB address, and information about the task that was ended and for an
that the DEB (DEBDCBAD) points back to this DCB. If explanation of the return code in register 15.
the next IOB is found to be in error, find the entry in the
read exclusive list associated with the requested block System action: Message IEC902I is issued,
and ensure that the RDXIOBUQ field is correct. specifying a cleanup code that indicates the results of
the cleanup of resources attempted by the recovery
Source: DFSMSdfp routine.
Operator response: Start a generalized trace facility
237 (GTF) trace, and re-create the problem. Reply to
message AHL100A with:
Explanation: The error occurred at an end-of-volume.
This system completion code is accompanied by TRACE=SYS,USR,SLIP
message IEC023I. Refer to the explanation of message
IEC023I for complete information about the task that On the DD statement for the data set in error, specify:
was ended and for an explanation of the return code (rc
Chapter 2. System Completion Codes 171
23E • 244
DCB=DIAGNS=TRACE
23F
Application Programmer Response: Insure the
Explanation: A security violation has been detected
validity of the control block from which the address of
during checkpoint restart processing. This completion
the block in error was taken. The DECB and DCB were
code is accompanied by message IHJxxxI with the
specified in the FREEDBUF macro as input to the SVC.
appropriate reason code.
Make sure that the DCBBUFCB field in the DCB
contains the correct address of the buffer control block System action: The job is abnormally ended.
and the DCBDYNB field contains the correct address of
Application Programmer Response: Respond as
the unscheduled list (if address space was virtual). The
indicated in the accompanying message.
BCB or USL contain the address of the next IOB waiting
to get a buffer, if one was not available. Ensure that this Source: DFSMSdfp
address has not been overlaid. Make sure also that the
input DECB contains the address of the buffer being
freed (DECAREA field) and, if a buffer was requested 240
for keys also, that the DECKYADR field contains the Explanation: The error occurred during processing of
correct address. a RDJFCB macro instruction. This system completion
System programmer response: If the error recurs code is accompanied by message IEC155I. Refer to the
and the program is not in error, search problem explanation of message IEC155I for complete
reporting data bases for a fix for the problem. If no fix information about the task that was ended and for an
exists, contact the IBM Support Center. Provide the explanation of the return code (rc in the message text)
SYSOUT output for the job. in register 15.
Source: DFSMSdfp Application Programmer Response: Respond as
indicated for message IEC155I.
23E System programmer response: If the error recurs
and the program is not in error, look at the messages in
Explanation: During processing of a DETACH macro, the job log for more information. Search problem
the system found an error in the input parameters. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL
Register 15 contains a hexadecimal reason code that
and the program listing for the job.
explains the error:
Source: DFSMSdfp
Code Explanation
00 The protection key of the address does not
244
match the key of the issuer of the DETACH.
Explanation: The error occurred during the processing
04 Access register 1 was nonzero for a caller in
of SYNADAF. It was determined that the register save
access register address space control (ASC)
area provided by the user was incorrect.
mode.
Application Programmer Response: Probable user
08 The task control block (TCB) specified in the
error. Make sure that when SYNADAF (SVC 68) is
input parameter list is not a subtask of the
issued, register 13 points to a register save area within
caller’s TCB.
the user’s region. If SYNADAF is issued from a SYNAD
System action: The system abnormally ends the routine, make sure that register 13 has not been altered
program that issued the DETACH macro. since the SYNAD routine was entered, and that register
13 contained the address of a valid register save area
Application Programmer Response: This is probably
when the last data management macro was issued.
an error in the calling program. Change the DETACH
macro to specify a valid TCB address and ensure that it Correct the error and rerun the job step.
was not incorrectly modified by the problem program. If
System programmer response: If the error recurs
running in access register ASC mode, ensure that the
and the program is not in error, look at the messages in
problem program does not alter access register 1.
the job log for more information. Search problem
Correct the error. Run the job again.
reporting data bases for a fix for the problem. If no fix
System programmer response: If the error recurs exists, contact the IBM Support Center. Provide the JCL
and the program is not in error, look at the messages in and the program listing for the job.
the job log for more information. Search problem
Source: DFSMSdfp
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
source program listing for the job.
Source: Task management
172 z/OS V1R10.0 MVS System Codes
245 • 25F
message IEC918I for complete information about the
245
task that was ended and for an explanation of the return
Explanation: An error occurred during the processing code in register 15.
of SVC 69 (BSP) that could not be attributed to
System action: Message IEC918I is issued.
incorrect user input. This system completion code is
accompanied by message IEC917I. Refer to the Application Programmer Response: Make sure that
explanation of message IEC917I for complete the last entry in the exit list has a high-order bit set to
information about the task that was ended and for an B’1’. Make sure that any FCB image entry in the exit list
explanation of the return code in register 15. points to a valid FCB image, that the image is within the
user’s region, that any FCB image has a valid length
System action: The backspace task recovery routine
field and that it is ended by an end-of-FCB image
has been invoked. Low real storage and the caller’s
indicator. Correct the error and rerun the job step.
region have been dumped to the SYS1.DUMP data set.
The caller’s input register 1 and DCB have been written System programmer response: If the error recurs
to the logrec data set. and the program is not in error, look at the messages in
the job log for more information. Search problem
Application Programmer Response: Make sure that
reporting data bases for a fix for the problem. If no fix
the BSP instruction is correctly coded, and that the DCB
exists, contact the IBM Support Center. Provide the JCL
and IOBs and/or ICBs for the data set being processed
and the program listing for the job.
are not overlaid by your program during the processing
of SVC 69. Source: DFSMSdfp
System programmer response: If the error recurs
and the program is not in error, look at the messages in 253
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix Explanation: While writing to system management
exists, contact the IBM Support Center. Provide the facility (SMF) data sets, SMF encountered an error and
JCL, the program listing for the job, the logrec data set abnormally ended.
error record, and all printed output and output data sets System action: The system ends the SMF address
related to the problem. space and releases the resources used by SMF.
Source: DFSMSdfp Operator response: Notify the system programmer. If
SMF recording is essential for the system, restart the
247 SMF address space using the SMF SET command as
soon as the problem is corrected.
Explanation: An error occurred in either the Graphics
Access Method/System Product (GAM/SP), or the System programmer response: Check error
operating system. This completion code appears when messages and the SVC dump produced as a result of
an incorrect condition is detected by the GAM/SP buffer any previous abnormal endings.
management routine, IGC0007A. Source: System Management Facilities (SMF)
System action: A message appears on the system
console that identifies the cause of the error. In addition, 25F
GAM/SP writes a record to the logrec data set and
produces a dump on the system dump data set. Explanation: A system failure destroyed data used by
the system resources manager (SRM) in controlling an
Application Programmer Response: address space.
1. Check for messages identifying the cause of the
System action: If the ended task is the master
error. If these are GAM/SP messages, (that is, the
scheduler command processor and SRM was
message number is of the form ’GABnnn’), they are
processing a NEWIPS SYSEVENT, the new installation
described in IBM Graphics Access Method/SP:
performance specification (IPS) may have been lost.
Messages and Codes.
2. Get a listing of the system dump. In all other cases, data pertaining to the address
space’s swap status or performance characteristics may
3. Contact your programming support personnel.
have been lost. SRM may no longer be able to control
Source: DFSMSdfp the address space according to its previously assigned
performance specification.
251 The system does the following:
Explanation: The error occurred during the processing v Writes a logrec data set error record
of SETPRT. A user-provided area was determined to be
incorrect. This system completion code is accompanied
by message IEC918I. Refer to the explanation of
Chapter 2. System Completion Codes 173
260 • 278
v Inserts ’worst case’ substitute values in place of the bases for the fix for the problem. If no fix exists, contact
lost address space characteristics in case the specify the IBM Support Center.
task abnormal exit (STAE) routine or the abnormally
Source: Region control task (RCT)
ended task requests retry
v Abnormally ends the controlling task of the address
space or system component affected by the data loss 269
System programmer response: Search problem Explanation: An error occurred during the processing
reporting data bases for a fix for the problem. If no fix of IMGLIB that could not be attributed to incorrect input
exists, contact the IBM Support Center. Provide the to IMGLIB. Register 15 contains a return code that
logrec data set error record and the SYSOUT output for indicates whether a dump was taken to the
the job. SYS1.DUMP data set.
Source: System resources manager (SRM) System action: The IMGLIB task recovery routine has
attempted to take a storage dump to the SYS1.DUMP
data set; the result of the dump attempt is indicated by
260 the return code in register 15. See message IEC920I for
Explanation: A parameter of the STAX macro was a complete description of the possible return codes and
used incorrectly. A hexadecimal reason code in register their meanings. Additional diagnostic information was
15 explains the error. written to the logrec data set data set.
Code Explanation Application Programmer Response: Make sure that
the IMGLIB macro instruction is correctly coded.
00 A parameter list address is incorrect.
System programmer response: If the error recurs
04 The input buffer size is greater than 32 and the program is not in error, look at the messages in
kilobytes. the job log for more information. Search problem
08 The input buffer address is incorrect. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
0C The output buffer size is greater than 32 JCL, the program listing for the job, and the logrec data
kilobytes. set error record.
10 Both DEFER bits are on. Source: DFSMSdfp
14 The format number of the parameter list is
incorrect. 271
18 An IGNORE attention request was issued by a Explanation: The caller requested fixing or freeing of
routine that is not a CLIST capable attention a page. The request was in 24-bit addressing and was
exit routine. without proper authorization.
1C An IBUF or OBUF address has been specified, System action: The system denies the requested
but is not a clean 24-bit address. service. The system writes messages and a dump. The
system issues an abend to the current task.
20 The caller of STAX
DEFER=NO,LINKAGE=BRANCH is not running Application Programmer Response: Correct the
in task mode. program or obtain proper authorization from installation
management.
24 The caller of STAX
DEFER=NO,LINKAGE=BRANCH is locked. System programmer response: Look at the
messages in the job log. Search problem reporting data
28 The caller of STAX
bases for a fix for the problem. If no fix exists, contact
DEFER=NO,LINKAGE=BRANCH is disabled.
the IBM Support Center. Provide the messages and the
2C The caller of STAX dump.
DEFER=YES,LINKAGE=BRANCH is not
Source: Real storage manager (RSM)
running in task mode.
System action: The system abends the program that
278
issued the STAX macro.
Explanation: An error occurred when the system tried
System programmer response: Correct the STAX
to process an RC, RU, VRC, or VRU form of the
parameter list error indicated by the reason code. See
GETMAIN macro, or an RC or RU form of the
z/OS TSO/E Programming Services for the STAX macro
FREEMAIN macro or the STORAGE RELEASE macro.
parameters.
The system attempted to get local system queue area
If the problem persists, search problem reporting data (LSQA) storage to support the request, but no central
storage is available to back the LSQA storage.
174 z/OS V1R10.0 MVS System Codes
279 • 282
System action: The system abnormally ends the the SVC dump and, if available, the logrec data set
address space where the job was running. error record.
Application Programmer Response: Run the job Source: Supervisor control
step again. If the system issues this abend again, notify
the system programmer.
282
System programmer response: Search problem
Explanation: An error was detected by RACF in the
reporting data bases for a fix for the problem. If no fix
parameters passed to RACF for RACROUTE
exists, contact the IBM Support Center.
REQUEST=AUTH processing.
Source: Virtual storage manager (VSM)
System action: The system terminates the task.
Application Programmer Response: Register 15
279
contains a hexadecimal reason code (message
Explanation: While processing the end of an I/O ICH409I, if issued, also contains this reason code):
request, the system found an error in the I/O
Code Explanation
parameters.
04 Parameter list length not valid.
Register 2 contains a reason code, as follows:
10 APF authorization, or system key 0-7, or
Code Explanation
supervisor state required for CSA, LOG,
04 The system found an incorrect buffer control PRIVATE, PROFILE, ACEE, UTOKEN,
block (BUFC). USERID, or GROUPID option.
14 The system found an incorrect buffer address 14 ATTR option not valid.
while trying to perform I/O.
18 Volume serial required but not supplied.
System action: The system abnormally ends the
1C Inconsistent PROFILE/ENTITY flag settings.
current task.
20 No resource name or PROFILE specified.
Application Programmer Response: Do the
following: 24 No CLASS name specified.
1. Check to see if the program incorrectly modified the 2C Incorrect LOG option specified. (This code is
I/O parameters. Correct any errors. used only through RACF Version 1.4.)
2. Recompile the job step.
30 Volume serial specified for class other than
3. Run the job step again. DATASET.
Source: Input/output supervisor (IOS) 34 File sequence number not valid.
38 File sequence number specified for non-tape
27B data set.
Explanation: Processing for the PURGEDQ macro 3C Tape label parameter specified for non-tape
issued a FESTAE macro to establish recovery. An error data set.
occurred during FESTAE processing. The PURGEDQ
and FESTAE macros were issued correctly: They did 40 Tape label option not valid.
not cause the error. The problem is an environmental
44 Erase-on-scratch request not valid.
error.
48 USERID = * was specified on the
System action: The system abnormally ends the task
REQUEST=AUTH. * is an unacceptable RACF
that issued the PURGEDQ macro. The system may
user ID.
write a logrec data set error record.
4C For the ENTITYX keyword, both the entity
Operator response: If the system programmer asks
name length and the buffer length are zero.
for an SVC dump, set the following SLIP trap:
SLIP SET,COMP=27B,ACTION=SVCD,END 50 Buffer length is not valid:
v Less than zero
Application Programmer Response: Rerun the job. If
the problems recurs, contact the system programmer. v Greater than 255
v Not zero but less than the entity name
System programmer response: Search problem
length.
reporting data bases for a fix for the problem. If no fix
exists, ask the operator to set a SLIP trap to obtain an 54 Entity name length is not valid:
SVC dump. Contact the IBM Support Center. Provide v Less than zero
Chapter 2. System Completion Codes 175
283
v Greater than 44 if CLASS=DATASET, or 04 Incorrect parameter list length.
greater than the length for that class as
14 ENVIR data specified was not valid.
defined in the class-descriptor table
v Greater than 44 if CLASS=DATASET, or 18 USERID specified did not conform to length
greater than the maximum length for that requirements.
class as defined in the class-descriptor 1C PASSWRD specified did not conform to length
table. requirements.
58 The in-storage profile provided to the 20 GROUP specified did not conform to length
REQUEST=AUTH was not at the version requirements.
required by RACF. Ensure that the version of
the in-storage profile (addressed by the 24 NEWPASS specified did not conform to length
ENTITY parameter with CSA specified) is at requirements.
the required version number.
28 OIDCARD specified had length field=0.
5C The entity name contains a blank.
| 30 A parameter was specified that is not allowed
If the ENTITYX keyword is specified and the | in combination with ENVIR=CREATE.
entity name length is given, the name has a
34 Incorrect combination of ENVIR keyword data
blank in the beginning, in the middle, or at the
and GROUP specified.
end.
38 ENVIR = CHANGE specified but no ACEE
60 RTOKEN keyword is mutually exclusive with
exits.
the CSA and PRIVATE parameters of the
ENTITY keyword. 3C User ID specified is *NONE* and
REQUEST=VERIFY is not branch entered.
64 ACEE not valid.
40 Reserved
68 Unauthorized caller specified subpool greater
than 127 on RACROUTE MSGSP parameter. 44 ENVIR=CREATE and SESSION=APPCTP
were specified but POE was not specified and
6C The message chain pointed to by SAFPMSAD
is required in this case.
for an unauthorized caller contains too many
elements, indicating a chaining problem. 48 ENVIR=CREATE and SESSION=APPCTP
were specified but APPL was not specified and
Identify and correct the indicated error. is required in this case.
Problem determination: Use the reason code in 4C The ACEE specified does not appear to be a
Register 15 to identify the error. If the issuer of the valid ACEE.
RACF macro is a user routine (such as an installation
50 The ENVRIN keyword was specified and the
exit), correct the parameter list specified for the RACF
ENVR object storage area address was zero,
macro in the installation exit. If the issuer of the RACF
or, either the ENVRIN or ENVROUT keyword
macro is an IBM routine, see z/OS Security Server
was specified and the ENVR object storage
RACF Diagnosis Guide for information on diagnosing
area was not on a doubleword boundary.
abends and reporting abend problems to IBM.
54 The ENVRIN keyword was specified and the
Note: For batch jobs, if you need to do dump analysis ENVR object contained in the ENVR object
but do not have a dump, run the job again. For storage area was larger than the ENVR object
batch jobs using DSMON, a RACF command, or storage area specified.
the RACF report writer, specify a SYSABEND
This can be caused by using an ENVR object
DD statement in the job. This will ensure that a
from another external security manager. For
dump is taken.
example, MCS console services routes
commands from other systems with ENVRIN
283 data.
Explanation: An error was detected by RACF in the
Identify and correct the indicated error.
parameters passed to RACF for RACROUTE
REQUEST=VERIFY processing. System programmer response: Use the reason code
in Register 15 to identify the error. If the issuer of the
System action: The system terminates the task.
RACF macro is a user routine (such as an installation
Application Programmer Response: Register 15 exit), correct the parameter list specified for the RACF
contains a hexadecimal reason code. (Message macro in the installation exit. If the issuer of the RACF
ICH409I, if issued, also contains this reason code.) macro is an IBM routine, see z/OS Security Server
RACF Diagnosis Guide for information on diagnosing
Code Explanation
176 z/OS V1R10.0 MVS System Codes
285
abends and reporting abend problems to IBM. v The OWNER is a RACF-defined user ID but
that user ID is revoked.
Note: For batch jobs, if you need to do dump analysis
44 UACC value is not valid.
but do not have a dump, run the job again. For
batch jobs using DSMON, a RACF command, or 48 Rename request is not valid. Either ENTITY
the RACF report writer, specify a SYSABEND name or NEWNAME name, but not both, is a
DD statement in the job. This will ensure that a generic name. This reason code could occur
dump is taken. because of the attempt to create a data set
profile with a single-qualifier name, when
RACF protection for single-qualifier names has
285
not been activated (SETROPTS command with
Explanation: RACF detected an error in the PREFIX specified). Note that there are several
parameters passed to it for RACDEF request cases in which data set profiles can be created
processing. automatically: when users with the ADSP
attribute create data sets, when
System action: The system terminates the task. PROTECT=YES is specified in JCL, and when
Application Programmer Response: Register 15 a user issues the ADDSD command.
contains a hexadecimal reason code. (Message 4C Type=CHGVOL specified for TAPE.
ICH409I, if issued, also contains this reason code.)
50 Parameters specified for TAPE are not valid.
Code Explanation
54 FILESEQ omitted when required for TAPE.
04 Parameter list length is not valid.
58 Operands specified for DASD are not valid.
08 Level number is not valid.
5A The in-storage profile provided to the
0C TYPE option is not valid. RACHECK request was not at the version
10 Resource name required. Entity-name (and required by RACF. Ensure that the version of
newname keywords, if specified) must point to the in-storage profile (addressed by the
valid, non-blank resource names. ENTITY parameter with CSA specified) is at
the required version number.
14 New data set name or old volume serial
specified but address is zero. 5C FILESEQ value is not valid.
18 Volume serial required but not specified. 60 TAPELBL value is not valid.
1C New data set name and old volume serial flags 64 EXPDT/RETPD value is not valid.
both set. 68 NOTIFY user ID is not valid.
24 Parameters supplied which are inconsistent for 6C RESOWNER specified for other than
a general resource class other than DATASET. TYPE=DEFINE.
These incorrect parameters might be model
name, model volume serial, VSAM data set bit 70 Specified RESOWNER is not valid.
on, old volume serial, or new data set name.
74 MGMTCLAS and/or STORCLAS specified
28 Model resource information supplied with type without RESOWNER.
other than DEFINE for DATASET class.
78 Length for MGMTCLAS is not valid.
2C Model name supplied but model volume serial
7C Length for STORCLAS is not valid.
not supplied.
80 Length for RESOWNER is not valid.
30 Unqualified data set name specified. This
return code is not issued if RACFIND=NO was 84 Specified SECLABEL is not valid.
specified.
88 Buffer length specified with ENTITYX keyword
34 Old volume serial number is absent for is not valid:
CHGVOL request. v Less than zero
38 Length of the unit field is not valid. v Greater than 255
3C AUDIT value is not valid. v Not zero but less than the entity name
length
40 Specified OWNER is not valid. This reason
code can occur for several reasons. Among the 8C Name length specified with ENTITYX keyword
possible reasons are: is not valid.
v The OWNER is not a RACF-defined user ID v The specified length is less than zero.
or group ID.
Chapter 2. System Completion Codes 177
28A
v The specified length is greater than 44 if class does not contain at least two valid
CLASS=DATASET or greater than the qualifiers for keyword MENTITY or MENTX.
maximum length for that class as defined in v The profile name contains only one qualifier.
the class-descriptor table.
v The profile name begins with a period.
v The name which was supplied is longer than
v The second qualifier is longer than 8
44 if CLASS=DATASET or longer than the
characters.
maximum length for that class as defined in
the class-descriptor table. B4 The profile name for the FILE and DIRECTRY
class does not contain at least two valid
90 For the ENTITYX format, both the entity name
qualifiers for keyword NEWNAME or
length and the buffer length are zero.
NEWNAMX.
94 Buffer length specified with MENTX keyword is v The profile name contains only one qualifier.
not valid:
v The profile name begins with a period.
v Less than zero
v The second qualifier is longer than 8
v Greater than 255 characters.
v Not zero but less than the entity name
B8 The entity name contains a blank:
length
If the ENTITYX keyword is specified and the
98 Name length specified with MENTX keyword is
entity name length is given, the name has a
not valid:
blank in the beginning, in the middle, or at the
v The specified length is less than zero. end.
v The specified length is greater than 44 if
BC The model profile name contains a blank.
CLASS=DATASET or greater than the
maximum length for that class as defined in If the MENTX keyword is specified and the
the class-descriptor table. name length is given, the name has a blank in
the beginning, in the middle, or at the end.
9C For the MENTX keyword, both the entity name
length and the buffer lengths are zero. C0 The new profile name contains a blank.
A0 Buffer length specified with NEWNAMX If the NEWNAME keyword is specified and the
keyword is not valid: new name length is given, the name has a
v Less than zero blank in the beginning, in the middle, or at the
end.
v Greater than 255
v Not zero but less than the entity name C8 Specified SECLVL is not valid:
length. v The number of data fields is not zero or one.
A4 Name length specified with NEWNAMX v The value of the data fields is not within the
keyword is not valid: range of 1 - 254.
v The specified length is less than zero.
Identify and correct the indicated error.
v The specified length is greater than 44 if
CLASS=DATASET or greater than the System programmer response: Use the reason code
maximum length for that class as defined in in Register 15 to identify the error. If the issuer of the
the class-descriptor table. RACF macro is a user routine (such as an installation
v The name that was supplied is longer than exit), correct the parameter list specified for the RACF
44 if CLASS=DATASET or longer than the macro in the installation exit.
maximum length for that class as defined in
the class-descriptor table. Note: For batch jobs, if you need to do dump analysis
but do not have a dump, run the job again. For
A8 For the NEWNAMX keyword, both the entity batch jobs using DSMON, a RACF command, or
name length and the buffer lengths are zero. the RACF report writer, specify a SYSABEND
AC The profile name for the FILE and DIRECTRY DD statement in the job. This will ensure that a
class does not contain at least two valid dump is taken.
qualifiers for keyword ENTITY or ENTITYX.
v The profile name contains only one qualifier. 28A
v The profile name begins with a period. Explanation: A caller requested fixing or freeing of a
v The second qualifier is longer than 8 page. The request was in 31-bit addressing and was
characters. without proper authorization.
B0 The profile name for the FILE and DIRECTRY System action: The system denies the requested
178 z/OS V1R10.0 MVS System Codes
290
service. The system writes messages and a dump. The 4107 A variable described in the HZSMGB data area
system issues an abend to the current task. had a bad address or length.
Application Programmer Response: Correct the Action: Verify that you specified the correct
program or obtain proper authorization from installation address and length for the variable.
management.
4108 The message number provided in MGB_Id
System programmer response: Look at the does not exist in the message table.
messages in the job log. Search problem reporting data
Action: Verify that you specified the correct
bases for a fix for the problem. If no fix exists, contact
message ID on the HZSFMSG macro.
the IBM Support Center. Provide the messages and the
dump. 4109 The maximum number of variables allowed in a
check message is defined by Mgb_MaxInserts.
Source: Real storage manager (RSM)
Action: Verify that you specified the correct
number of variables on the HZSFMSG macro.
290
410A The message table requested a variable that is
Explanation: The IBM Health Checker for z/OS
out of sequence or too few inserts.
encountered an error. A reason code is displayed along
with the 290 abend code. The format of the abend code Action: Verify that you specified the correct
is cc-mm-rrrr, where rrrr is the halfword reason code. variable on the HZSFMSG macro.
The IBM Health Checker for z/OS reason codes for the 410B The message definition requires a variable that
290 abend code and actions that you can use to correct does not exist in the HZSMGB data area.
the problem are:
Action: Verify that you specified the correct
002D The HZSCPARS REQUEST=PARSE was variable on the HZSFMSG macro.
issued a second time without freeing the parse
area that was obtained for the first HZSCPARS 410C The HZSMGB data area contained variables
REQUEST=PARSE request. that were not requested in the associated
message.
Action: Verify that a HZSCPARS
REQUEST=FREE before a subsequent Action: Verify that you specified the correct
HZSCPARS REQUEST=PARSE is issued. variables on the HZSFMSG macro.
1xxx An internal error in the IBM Health Checker for 410D A variable described in the HZSMGB data area
z/OS component. had a bad address or length.
Action: Search problem reporting data bases Action: Verify that you specified the correct
for a fix to the problem. If no fix is found, address and length for the variable on the
contact the IBM Support Center. Provide the HZSFMSG macro.
LOGREC data set and SVC dump, if one is 410E A variable described in the HZSMGB data area
issued. had a bad address or length.
4009 HZSADDCK found a message table that is not Action: Verify that you specified the correct
supported on this release, or the message address and length for the variable on the
table was not created by HZSMSGEN. HZSFMSG macro.
Action: Verify the check and the message 410F The HZSFMSG macro parameter was not
table are intended for the release of MVS that accessible or not in the caller's key.
is active on this system and that it was created
by HZSMSGEN. Action: Verify that the parameter list for the
HZSFMSG macro is accessible and in the
4016 The variable defined in the HZSMGB area has caller’s key.
a length greater than the value defined by
Maxlen in the message table. 4110 The HZSFMSG request CHECKMSG requires
a valid HZSMGB data area.
Action: Verify that you specified the correct
length for the variable. Action: Verify that you specified a valid control
block on the HZSFMSG macro.
4106 The HZSMGB data area or the HZSMGB data
area variable array is not available or could not 4111 The HZSFMSG parameter list contained an
be accessed. unsupported version number.
Action: Verify that the input parameter is Action: Verify that you specified the correct
correct on the HZSFMSG macro. version number on the HZSFMSG macro.
Chapter 2. System Completion Codes 179
2C2
4112 The HZSFMSG request was issued by a Resource Resource Resource
program that was not a check routine. Class Code Name Description
Action: Verify that you did not issue the 01 Resource abstract class for
HZSFMSG macro from a program that was not workflow server
a check routine. resources
4113 The HANDLE parameter issued on the 02 FmSrvRes abstract class for
HZSFMSG contained an incorrect value. workflow server
instance resources
Action: Verify that the HANDLE parameter on
the HZSFMSG request contains a valid value. 03 FmDevRes abstract class for
workflow server
4114 The HZSFMSG macro was requested from a
input/output device
remote routine that was not a check routine.
resources
Action: Verify that the HZSFMSG macro is 04 SystCons implementation class
issued from a check routine. for the system
4115 The system could not set the ABENDRESULT console interface
parameter on the HZSFMSG macro request. 05 Diagnose implementation class
Action: Verify that the input parameter is for the flight recorder
correct on the HZSFMSG macro. 06 FifoLock implementation class
4116 The variable defined in the HZSMGB area has for the queue
a length greater than the value defined by serialization
Fieldsize in the message table. 07 MvsMsgSv implementation class
for the MVS message
Action: Verify that you specified the correct
services interface
length for the variable.
08 DevQueue implementation class
4117 The message table supplied by a remote check
for the in-storage
is not valid.
queues
Action: Verify that the message table was built 09 ErrStack implementation class
via the HZSMSGEN exec and has not been for the error recovery
overlaid.
10 ServerDS implementation class
4118 A remote check issued HZSFMSG other than for the data set
from the INITRUN or RUN function. access
Action: Verify that HZSFMSG is only issued 11 Security implementation class
the check has gotten control with for the security server
PQE_Function_code of either interface
PQE_Function_code_Init or
PQE_Function_Code_Check. 12 SrvGroup implementation class
for the subtask
System action: The system continues. management
System programmer response: See the appropriate 13 SynchEcb implementation class
reason code listed above and correct the error. for the subtask
synchronization
Source: IBM Health Checker for z/OS
14 TimeServ implementation class
for the timer interface
2C2
15 ExtTrace implementation class
Explanation: The MQSeries Workflow for OS/390 for the component
server instance subtask encountered a severe internal trace interface
error.
16 TaskServ implementation class
The reason code identifies the source of the error. It has for the subtask
the format X'rrmmnnnn', where rr denotes the resource services
class (as detailed in the table that follows), mm denotes
the method of the resource class, and nnnn identifies 17 WkldMgmt implementation class
the place within the method where the error was for the workload
encountered. manager interface
180 z/OS V1R10.0 MVS System Codes
2C3 • 2C6
Resource Resource Resource Table 1. Reason code explanations (continued)
Class Code Name Description Reason
18 XcfGroup implementation class code Explanation Action
for the cross-system 0384 F ZFS,ABORT None
coupling facility command was
interface issued
19 XLngServ implementation class 0385 The system this None
for the code issued on
cross-language is taking a zFS
services dump at the
20 XMemServ implementation class request of zFS
for the cross-memory running on
services another sysplex
member.
System action: The system issues an ABEND dump. 0410 The IOEAGFMT If possible, determine
utility has why the storage
Application Programmer Response: None. attempted to obtain failed and
obtain storage correct the problem.
System programmer response: Search the problem
and failed. Try to increase the
reporting data bases for a fix for the problem. If no fix
region size for the job
exists, contact the IBM Support Center and provide the
and run it again.
ABEND dump.
Ensure that a user
Source: MQSeries Workflow for OS/390 exit does not cause
the job to fail to obtain
storage.
2C3
0412 zFS marked a To recover the
Explanation: The zFS Physical File System (PFS) zFS aggregate compatibility mode
encountered an internal error. An internal reason code is dead because of aggregate, unmount it,
displayed along with the zFS 2C3 abend code. Each an internal run the zFS
reason code is made up of 4 bytes; cccc rrrr, where problem. zFS IOEAGSLV utility
cccc is a halfword reason code qualifier and rrrr is the will attempt to against it and then
halfword reason code. The high-order bytes of the dump on this mount it again. See
reason codes returned contain a value that is used to system and on z/OS Distributed File
qualify the contents of the 2 low-order bytes. zFS each member of Service zSeries File
reason code qualifiers are found within the range the sysplex (with System Administration
X'EA00' to X'EAFF'. The low-order bytes of the reason the same abend for information on
codes are found within the range X'0000' to X'FFFF'. reason code). IOEAGSLV.
System action: The system issues an ABEND dump
and then zFS might attempt to stop and restart. Source: zSeries® File System (zFS)
Additional messages can be issued.
Application Programmer Response: None. 2C6
System programmer response: Search the problem Explanation: The MIHQUERY service, the IOSCDR
reporting data bases for a fix for the problem. If no fix service, the IOSPTHV service, or the IOSCAPU service
exists, contact the IBM Support Center and provide the has encountered an abend condition while attempting to
ABEND dump and the internal reason code. satisfy the caller’s request.
If the automatic stop and restart of zFS is unsuccessful, MIHQUERY
cancel the zFS address space and then respond R to
the BPXF032D WTOR to restart zFS. The reason codes for the MIHQUERY service are as
follows:
Table 1. Reason code explanations
0001 Caller of MIHQUERY is not in supervisor state.
Reason
code Explanation Action 0002 Caller of MIHQUERY is not in key 0-7.
0342 F ZFS,DUMP None 0003 Incorrect parameter list. For one of the
command was following reasons, an error occurred when the
issued MIHQUERY service tried to copy the list:
Chapter 2. System Completion Codes 181
2C6
v The caller passed an incorrect parameter list v The caller passed an incorrect parameter list
address. address.
v The caller passed an address that the caller v The caller passed an address that the caller
did not own. did not own.
v The storage was in an incorrect key. v The storage was fetch protected.
0004 Incorrect parameter list. For one of the 0203 Incorrect parameter list. For one of the
following reasons, an error occurred when the following reasons, an error occurred when the
MIHQUERY service tried to update the list: service tried to update the list:
v The caller passed an incorrect parameter list v The caller passed an incorrect parameter list
address. address.
v The caller passed an address that the caller v The caller passed an address that the caller
did not own. did not own.
v The storage was in an incorrect key. v The storage was in a key that is not
accessible from the key of the caller.
The caller might have freed the parameter list
between the time when MIHQUERY copied the The caller might have freed the parameter list
parameter list and the time when it updated the between the time when the service read the
list. parameter list and the time when it updated the
list. In addition, if the storage is not accessible
0005 The caller of MIHQUERY passed an incorrect
from the key of the caller, then reads may
UCB address in the parameter list.
work, but updates may not.
0006 The caller of MIHQUERY is in cross memory
0204 Incorrect IOCTOKEN storage. For one of the
mode; that is, PASN=HASN=SASN is not in
following reasons, an error occurred when the
effect.
service tried to read the IOCTOKEN.
IOSCDR v The caller passed an incorrect IOCTOKEN
address.
The reason codes for the IOSCDR service are as v The caller passed an address that the caller
follows: did not own.
v The storage is fetch protected.
0100 Incorrect authorization. For LINKAGE=LINK
callers, the caller is not in supervisor state. For 0205 Incorrect IOCTOKEN. For one of the following
LINKAGE=SYSTEM callers, the caller is not reasons, an error occurred when the service
any one of the following: tried to update the IOCTOKEN:
v In supervisor state v The caller passed an incorrect IOCTOKEN
v In PKM 0-7 address.
v In problem state
v In PSW key 0-7 v The caller passed an address that the caller
v APF-authorized did not own.
v RACF authorized to the FACILITY class and v The storage was in a key that is not
the IOSCDR entity. accessible from the key of the caller.
0101 Caller of IOSCDR is not in task mode. The caller might have freed the IOCTOKEN
storage between the time when the service
0102 Caller of IOSCDR is locked. read it and the time when it attempted to
0103 Incorrect AMODE. Caller of IOSCDR is not in update it. In addition, if the storage is not
31-bit mode. accessible from the key of the caller, then
reads may work, but updates may not.
0200 Incorrect parameter list. Caller of IOSCDR
passed an incorrect version of the parameter 0206 Incorrect CDRAREA. For one of the following
list. reasons, an error occurred when the IOSCDR
service tried to update the CDRAREA.
0201 Incorrect parameter list. The integrity of the
v The caller passed an incorrect CDRAREA
parameter list was compromised. For example,
address.
more than one parameter in a list of mutually
exclusive parameters was specified. v The caller passed an address that the caller
did not own.
0202 Incorrect parameter list. For one of the
v The storage was in a key that is not
following reasons, an error occurred when the
accessible from the key of the caller.
IOSCDR service tried to read the list:
182 z/OS V1R10.0 MVS System Codes
2C6
The caller might have freed the CDRAREA v The caller passed an address that the caller
storage before IOSCDR attempted to update it. did not own.
v The storage was in a key that is not
IOSPTHV accessible from the key of the caller.
The reason codes for the IOSPTHV service are as The caller might have freed the IOCTOKEN
follows: storage between the time when the service
read it and the time when it attempted to
0100 Caller of IOSPTHV is not in supervisor state. update it. In addition, if the storage is not
accessible from the key of the caller, then
0101 Caller of IOSPTHV is not in task mode.
reads may work, but updates may not.
0102 Caller of IOSPTHV is locked.
0205 Incorrect MSGBUF. For one of the following
0103 Incorrect AMODE. Caller of IOSPTHV is not in reasons, an error occurred when the IOSPTHV
31-bit mode. service tried to update the MSGBUF.
0200 Incorrect parameter list. Caller of IOSPTHV v The caller passed an incorrect MSGBUF
passed an incorrect version of the parameter address.
list. v The caller passed an address that the caller
did not own.
0201 Incorrect parameter list. For one of the
following reasons, an error occurred when the v The storage was in a key that is not
IOSPTHV service tried to read the list: accessible from the key of the caller.
v The caller passed an incorrect parameter list The caller might have freed the MSGBUF
address. storage before IOSPTHV attempted to update
v The caller passed an address that the caller the MSGBUF.
did not own.
IOSCAPU
v The storage was fetch protected.
0202 Incorrect parameter list. For one of the The reason codes for the IOSCAPU service are as
following reasons, an error occurred when the follows:
IOSPTHV service tried to update the list:
01000100 Caller of IOSCAPU CAPTUCB or
v The caller passed an incorrect parameter list IOSCAPU UCAPTUCB is locked or is
address. not enabled.
v The caller passed an address that the caller
did not own. 01000101 Caller of IOSCAPU CAPTOACT is
locked.
v The storage was in a key that is not
accessible from the key of the caller. 01000102 Caller is in SRB mode during nucleus
initialization program (NIP) processing
The caller might have freed the parameter list and authorization for a PC routine is
between the time when the service read the not available.
parameter list and the time when it updated the
list. In addition, if the storage is not accessible 01000103 Caller of IOSCAPU CAPTUCB or
from the key of the caller, then reads may IOSCAPU UCAPTUCB is in cross
work, but updates may not. memory mode.
0203 Incorrect IOCTOKEN storage. For one of the 01000104 Caller of IOSCAPU CAPTUCB,
following reasons, an error occurred when the IOSCAPU UCAPTUCB, or IOSCAPU
IOSPTHV service tried to read the IOCTOKEN. CAPTOACT ASID is in problem state
v The caller passed an incorrect IOCTOKEN and is not in key 0-7.
address. 01000200 Caller of IOSCAPU passed an
v The caller passed an address that the caller incorrect version of the parameter list.
did not own.
01000201 For one of the following reasons, the
v The storage is fetch protected. integrity of the parameter list was
0204 Incorrect IOCTOKEN. For one of the following compromised:
reasons, an error occurred when the service v More than one parameter in a list of
tried to update the IOCTOKEN: mutually exclusive parameters was
v The caller passed an incorrect IOCTOKEN specified.
address. v A function parameter was not
specified.
v Reserved fields are not zero.
Chapter 2. System Completion Codes 183
2E0
v A required parameter associated | cases, the 2E0 abend is percolated to an application
with a function parameter was not | recovery routine or another system component recovery
specified. | routine.
01000202 For one of the following reasons, an | IOSHMSUS
error occurred when IOSCAPU tried to
read the parameter list:
| 00010001
| IXCSETUS macro returned a parameter error
v The caller passed an incorrect | or environment error return code.
parameter list address.
v The caller passed an address that
| 00010002
| IXCSETUS macro returned an unexpected
the caller did not own.
| return code.
v The storage was fetch protected.
01000203 For one of the following reasons, an | IOSHMMSG
error occurred when IOSCAPU tried to | 00020001
update the parameter list: | Input message request qualifier is not defined.
v The caller passed an incorrect
parameter list address. | 00020002
| Input message request type is not defined.
v The caller passed an address that
the caller did not own.
| IOSHIPCR
v The storage was in a key that is not
accessible from the key of the | 00030001
caller. | Redundant PC routine initialization call is
| detected.
01000204 The access list entry token (ALET) for
the parameter list is not valid. | 00030002
| IOSHMPCR entry point is unresolved.
01000205 The requested function does not exist.
| 00030003
01000300 The release of the specified captured | Basic HyperSwap address space authorization
UCB exceeds the number of captures | failed.
specified with the LASTING parameter
or in SRB mode. | 00030004
| Basic HyperSwap address space linkage table
System action: The system continues processing. | index reserve failed.
The caller ends abnormally with the appropriate reason
code. | 00030005
| IOSHMPCR ETCRE macro request failed.
Application Programmer Response: The application
recovery routine should have recorded and/or dumped | 00030006
the data needed to debug this problem. The dumped | IOSHMPCR ETCON macro request failed.
data should include the parameter list and its UCB
address, the caller’s key and the key of the storage that | IOSHMPAR
the caller was attempting to obtain. Correct the | 00040001
application and resubmit. If the recovery routine did not | Input message request type is not defined.
save the dump information, fix the recovery routine and
try to recreate the original problem. If the error recurs,
| IOSHMCIT
notify the system programmer.
| 00050001
System programmer response: If the application
| CSVDYNEX DEFINE IOSHSWAP_EXIT macro
programmer is unable to debug the error, search
| request failed.
problem reporting databases for a fix for the problem. If
no fix exists, contact the IBM Support Center. Provide | 00050002
the dump data from the application recovery routine. | Input message request type is not defined.
Source: Input/output supervisor (IOS) | 00050003
| CSVDYNEX UNDEFINE IOSHSWAP_EXIT
| macro request failed.
| 2E0
| Explanation: An unexpected error occurred during | IOSHMHST
| Basic HyperSwap™ processing. This abend can be used
| 00060001
| for entry into a recovery routine that captures additional
| Input message request type is not defined.
| documentation and then attempts to try again. In other
184 z/OS V1R10.0 MVS System Codes
2E0
| 00060002 | IOSHMPED
| Input message request is not received on the
| 00120001
| master processor.
| Input message request type is not defined.
| IOSHMCMT
| IOSHIMSG
| 00070001
| 00130001
| Input message request type is not defined.
| IXCQUERY macro request failed.
| 00070002
| 00130002
| IOSXTIM macro request failed.
| IXCJOIN macro request failed.
| 00070003
| Input message request was not received on | IOSHMEPT
| the master processor.
| 00140001
| Unrecognized Basic HyperSwap operator
| IOSHINTT
| command is received from SSI.
| 00080001
| 00140002
| Task termination wait time for a Basic
| Incorrect operator command parameter list
| HyperSwap task has been exceeded.
| (CSCB) is received from SSI.
| IOSHMENF | 00140003
| Unrecognized Basic HyperSwap command
| 000F0001 | from the application user exit.
| Unable to locate input device UCB.
| 00140004
| 000F0002 | Incorrect parameter list information from the
| Unable to retrieve configuration data record
| application user exit.
| (CRD) information.
| 00140005
| 000F0003 | Input message request type from the SSI
| Unable to locate device node descriptor (NED)
| (IOSHMSSM) is not defined.
| information.
| 00140006
| 000F0004 | Input message request qualifier from the SSI
| IOSHXSND macro request failed. Unable to
| (IOSHMSSM) is not defined.
| deliver ENF signal.
| 00140007
| IOSHMCFG | Input message request type from subordinate
| task (IOSHMEPT) is not defined.
| 00100001
| Input message request type is not defined. | 00140008
| Incorrect operator command parameter list
| 00100002 | (CSCB) length from subordinate task
| Response from the master member’s | (IOSHMEPT).
| configuration validation task (IOSHMCF2) is
| missing. | 00140009
| IOSHXSND macro failed to send request to
| 00100003 | IOSHMEPT on the master.
| Response from the configuration validation task
| (IOSHMCF2) on one of the slave members is | 0014000A
| missing. | IOSHXSND macro failed to send request to
| IOSHMHST on the master.
| 00100004
| Unable to locate member information in the | 0014000B
| Basic HyperSwap global information (GMI) | IOSHXSND macro failed to send request to
| table. | IOSHMCIT.
| 0014000C
| IOSHMCF2 | IOSHXMAC macro enable request failed.
| 00110001 | 0014000D
| Input message request type is not defined. | IOSHXMAC macro disable request failed.
| 00110002 | 0014000E
| Response from the HyperSwap API services | IOSHXMAC macro PPRC suspend request
| interface task is missing. | failed.
Chapter 2. System Completion Codes 185
2E0
| IOSHISSI | IOSHSAPI
| 00150001 | 80000001
| IEFSSVT macro CREATE request failed. | Dump option requested for HyperSwap API
| services wSwap (FC=3) request timeout.
| 00150002
| IEFSSVT macro EXCHANGE request failed.
| IOSHSSUB
| 00150003
| 80010001
| IEFSSVT macro DISABLE request failed.
| Query PPRC pair status I/O error encountered.
| 00150004
| 80010002
| IEFSSI macro PUT request failed.
| Terminate PPRC pair I/O error encountered.
| 00150005
| 80010003
| IEFSSI macro ACTIVATE request failed.
| IOSVSWAP routine call failed.
| 00150006
| 80010004
| IEFSSI macro DEACTIVATE request failed.
| Query unit address configuration I/O error
| 00150007 | encountered.
| IEFSSI macro QUERY request failed.
| 80010005
| 00150008 | UCBINFO macro on PAVINFO request failed.
| IEFSSI macro ADD request failed.
| 80010008
| 00150009 | Read DASD volume Label I/O error
| SSI Broadcast Message START request | encountered.
| (IEAVG700) failed.
| 80010009
| 0015000A | Write DASD volume Label I/O error
| SSI Broadcast Message STOP request | encountered.
| (IEAVG700) failed.
| 8001000A
| UCBLOOK macro request failed.
| IOSHMOPR
| 8001000B
| 00170001 | IOSVMSCQ routine request failed.
| Operator requested Basic HyperSwap SVC
| dump. | 8001000C
| IEFSSREQ macro request failed.
| IOSHMSND | 8001000D
| 00180001 | Establish PPRC pair I/O error encountered.
| IOSHXSND macro processing error occurred
| 8001000E
| and caller requested the DumpOnError
| Establish PPRC pair I/O error encountered.
| parameter option.
| 8001000F
| IOSHXREC | IOSCFT macro request failed.
| 00190001 | 80010011
| Rsn Code 1 - Unable to establish an ESTAE. | IOPTHVAL macro request failed.
| 80010012
| IOSHMMQM | IOSSLFD macro request failed.
| 001A0001
| IOSHXMAC macro processing error. Request | IOSHSENF
| code is not defined.
| 80020001
| UCBPIN macro request failed.
| IOSHMXUS
| 80020002
| 001B0001 | UCBPIN macro token count error encountered.
| IXCSTATUS macro request failed.
| System action: The system might request an SVC
| IOSHMTKX | dump and may write messages related to the problem.
| 001C0001 | Operator response: Notify the system programmer.
| Unable to locate TCB in the Basic HyperSwap | System programmer response: Search problem
| task table.
186 z/OS V1R10.0 MVS System Codes
2F3 • 300
| reporting databases for a fix for the problem. If no fix Operator response: In the first case, respond to
| exists, contact the IBM Support Center. Provide the message IAT3nnn.
| messages, the logrec data set record, the SYSOUT
Application Programmer Response: In the second
| output for the job, and the dump.
case, analyze the abend dump to find the cause of the
| Source: Input/output supervisor HyperSwap function error.
| (IOSH)
System programmer response: Obtain the abend
| Detecting Module: See individual reason codes. dump for the failing job step.
If the problem occurred in JES3 you should:
2F3 v Save the hardcopy log
v Provide a listing of the initialization deck (JES3OUT)
Explanation: One of the following has occurred to a
v Provide a console log from initialization
job which was journaled or was otherwise eligible for
v Check the JESYSMSG data set for error indications
restart (checkpoint/restart, step restart, or job restart):
v The job was running when a system failure occurred, Source: JES3
and a system restart (IPL and JES2 WARM start)
was performed. 2FC
v The initiator the job was running in terminated at End
Explanation: While the I/O first level interrupt handler
Of Memory (EOM).
(FLIH) was running, an error occurred.
A system job queue entry for the job existed at the time System action: In an attempt to recover, the system
of the failure, but the specific step to be restarted at abnormally ends the task that experienced the I/O
was not eligible for restart. interrupt. The system writes a logrec data set error
record.
Application Programmer Response: Resubmit the
job. Operator response: If the system programmer asks
for an SVC dump, set the following SLIP trap:
Source: Initiator/terminator
SLIP SET,COMP=2FC,ACTION=SVCD,END
Detecting Module: IEFIB605
System programmer response: Do the following:
v Find the original abend causing the problem in the
2FB
system diagnostic work area (SDWA) in the logrec
Explanation: The system has abnormally ended at data set error record for abend X'2FC'.
one of the following points in processing: v Search problem reporting data bases for a fix for the
1. A critical error occurred early in JES3 or the problem. If no fix exists, ask the operator to set a
functional subsystem (FSS) initialization or late in SLIP trap to obtain an SVC dump. Contact the IBM
JES3 abnormally ending. The JES3 ESTAE Support Center. Provide the SVC dump and the
environment had not yet been established or is logrec data set error records.
deleted, so no JES3-formatted ABEND dump is
Source: Supervisor control
available.
2. Once JES3 initialization has successfully
established the JES3 ESTAE routine (IATABMN), 300
the retry routine (IATABRT) uses this ABEND code Explanation: During processing of an I/O request,
to return to IATABMN in order to percolate. execute channel program (EXCP) processing
encountered an error. Each X'300' abend code has a
An MVS dump will always appear for a X'2FB' ABEND, reason code that explains the error:
regardless of the original abend code. The original
abend code is shown in message IAT3713 to the Code Explanation
operator and in the JES3-formatted dump. The dump by 1-2 EXCP encountered an incorrect data extent
itself does not tell whether the failing JES3 function block (DEB) at one of the following phases
recovered or had to be ended. during the validity check:
v Reason code 1 - front end processing
Note: An MVS dump with a 2FB means that IATABRT
or a routine used by module IATABRT failed, v Reason code 2 - while processing a related
thereby producing the 2FB abend. request (RRQE)
System action: In the first case, JES3 writes message The problem can be one of the following:
IAT3702 to the operator and to a dump data set of the v The DEB does not exist in the DEB TABLE.
type specified during JES3 initialization. This message
details critical debugging information.
Chapter 2. System Completion Codes 187
301 • 302
v The offset in the DEB TABLE (DEBTBLOF)
301
for this DEB is less than 1 or greater than
the number of entries in the DEB TABLE. Explanation: During processing of a WAIT macro, the
v The DEB address that was obtained from system found that the wait flag was already on in the
the data control block (DCB) does not match event control block (ECB). The flag on indicated that a
any entry in the DEB TABLE. previous WAIT macro was already waiting for posting of
the ECB.
3 The DEB is not an EXCP or Indexed
Sequential Access Method (ISAM) DEB. System action: The system abnormally ends the
program that issued the WAIT macro.
4 The system detected that the IOBM field in the
input/output block (IOB) is higher than the Application Programmer Response: Change the
maximum extent count (DEBNMEXT) in the problem program to eliminate a double wait on a single
DEB. event. If no double wait is found, ensure that the
program did not incorrectly modify the ECB. Then run
5 The Related Request Queue (RRQ) address in the job again.
the DEB does not match the RRQ address in
each Request Queue Element (RQE) System programmer response: If the error recurs
associated with the DEB. and the program is not in error, look at the messages in
the job log for more information. Search problem
6 Dataset Name Hiding is active and the user reporting data bases for a fix for the problem. If no fix
does not have RACF/SAF Facility Class exists, contact the IBM Support Center. Provide the
Authorization to read the VTOC. program listing and the assembly listing associated with
7 During EXCP purge processing an invalid the job.
input/output block (IOB) was found on the IOB Source: Task management
restore chain.
System action: The system abnormally ends the 302
current task and issues a SNAP dump.
Explanation: During processing of a POST macro, the
Application Programmer Response: Correct the system found an error in the caller’s environment.
problem that the reason code indicates. Verify that the Register 15 contains a hexadecimal reason code that
DCB contains the address of the DEB. Correct the error. explains the error:
Run the job again.
Code Explanation
For reason code 6, obtain read access to the
’STGADMIN.IFG.READVTOC.volser’ Facility Class 04 The caller does not hold the home address
profile and rerun the job. space’s local lock.
If the error recurs, check the problem program for the 08 The caller does not have addressability to the
error. If the error cannot be determined, run the job home address space.
again, requesting an ABEND dump. Notify the system 14 The caller does not hold the home address
programmer. space’s local lock.
System programmer response: In the dump, look at 18 The caller does not have addressability to the
field TCBEXCPD at offset X'C0' in the task control block home address space.
(TCB) for the current task. TCBEXCPD points to the
EXCP debugging area (XDBA). The XDBA contains 24 The caller does not hold the home address
diagnostic data associated with the EXCP processor. space’s local lock.
If the error recurs and the program is not in error, look 28 The caller does not have addressability to the
at the messages in the job log for more information. home address space.
Search problem reporting data bases for a fix for the 34 The caller does not hold the home address
problem. If no fix exists, contact the IBM Support space’s local lock.
Center. Provide the JCL for the job and the dump.
38 The caller does not have addressability to the
Source: Execute channel program (EXCP) home address space.
For reason code 5, also EXCP purge exit IECVEXPR. 3C A disabled caller issued a POST macro with
For reason code 7, IECVEXPR. the LINKAGE=SYSTEM option.
40 A caller who held a lock issued a POST macro
with the LINKAGE=SYSTEM option.
48 A caller who was not processing in primary
188 z/OS V1R10.0 MVS System Codes
305 • 306
address space control (ASC) mode issued a Application Programmer Response: Do the
POST macro with the LINKAGE=SYSTEM following:
option. v Ensure that the FREEMAIN operands A and LV do
4C A caller who was not authorized for a cross not specify a different subpool and/or key than the
memory POST (XMPOST) issued a POST subpool or key of the storage you are trying to free.
macro with the LINKAGE=SYSTEM option. v Ensure that the task control block (TCB) specified on
the FREEMAIN request is the same one specified on
System action: The system abnormally ends the
the corresponding GETMAIN request.
program that issued the POST macro.
v If a caller running in supervisor state and key 0 made
Application Programmer Response: This is probably the original GETMAIN request, ensure that the
an error in the calling program. Modify the code to allow corresponding FREEMAIN request is issued in
the POST macro to be issued in the correct supervisor state and key 0.
environment. Run the job again.
If a caller in supervisor state and key 0 requests
Source: Task management storage in subpool 0 or 250, the system will satisfy
this request with storage from a different subpool.
This situation is described in z/OS MVS Diagnosis:
305 Reference.
Explanation: An error occurred when the system tried v Check for program errors that incorrectly modify the
to process an EU, LU, or VU form of the FREEMAIN FREEMAIN macro expansion.
macro. A reason code in the SDWACRC field of the
system diagnostic work area (SDWA) explains the error: Source: Virtual storage manager (VSM)
Code Explanation
306
08 System queue area (SQA) storage is not in the
specified subpool. Explanation: The error occurred during processing of
a LINK(X), XCTL(X), ATTACH(X), or LOAD macro.
0C Common service area (CSA) storage is not in
the specified subpool. An incorrect load to global request was attempted, or
the authorized routine requested a module that could
10 Local system queue area (LSQA) storage is not be found in an authorized library. The module was
not in the specified subpool. found either in an unauthorized library or already loaded
in storage but marked as coming from an unauthorized
14 Private area storage is not in the specified
library.
subpool.
The reason code in register 15 identifies the error:
18 The system could not find a private area
subpool. Code Explanation
1C Zero length is not specified on a subpool 04 A LOAD macro requested, by the load to global
FREEMAIN. Zero length must be specified on option, a module residing in a library that is not
a subpool FREEMAIN. authorized program facility (APF) authorized.
08 A LOAD macro requested, by the load to global
Note: If this error is detected, the calling
option, a module that is not reentrant.
program is abnormally ended even
though EC, LC, or VC is specified on 0C An authorized program requested, by a
the FREEMAIN macro. LINK(X), LOAD, XCTL(X) or ATTACH(X)
macro, a module in a non-APF-authorized
20 One of the following:
library or concatenation of libraries.
v In the CSA, the area specified on a
FREEMAIN is larger than the area specified 10 A LOAD macro requested, using the
on the original GETMAIN. GLOBAL=(YES,F) keyword, a module that
requires page alignment.
v The FREEMAIN start address is not valid.
20 A job step module was found in a LNKLST
24 One of the following:
data set that was not APF authorized; an APF
v In the private area, the area specified on a authorized module was required.
FREEMAIN is larger than the area specified
on the original GETMAIN. 24 An authorized service attempted, via a
LINK(X), LOAD, XCTL(X), or ATTACH(X)
v The FREEMAIN start address is not valid.
macro, to access a copy of a load module
System action: The system issues message IEA705I. which is non-reentrant and loaded from an
The system abnormally ends the current task.
Chapter 2. System Completion Codes 189
30A
authorized library by an unauthorized caller.
30A
Another copy of the module could not be
found. Explanation: An error occurred when the system tried
to run an R form of the FREEMAIN macro. A reason
30 The user attempted to use a controlled
code in the SDWACRC field of the system diagnostic
program but is not authorized by RACF to use
work area (SDWA) explains the error:
that program. This can occur when a user has
EXECUTE access to a program library’s data Code Explanation
set profile, even if none of the program
08 System queue area (SQA) storage is not in the
modules involved are RACF program
specified subpool.
protected. Have the system security
administrator grant you READ access to the 0C Common service area (CSA) storage is not in
data set profile instead. the specified subpool.
34 The user attempted to use a program while a 10 Local system queue area (LSQA) storage is
program-accessed data set was open. not in the specified subpool.
38 The user requested access to an in-storage 14 One of the following:
program that is not RACF-controlled while a v Private area storage is not in the specified
program access data set (PADS) was open. subpool.
| 40 Signature verification for the module being v The TCB requesting the FREEMAIN is not
| loaded was required but failed. the same as the TCB which owns the
storage. Usually, the TCB that owns the
42 The user attempted to use a program that is
storage did the GETMAIN.
not program-controlled, while a must remain
controlled environment exists. v The key of storage does not match. This can
happen when the FREEMAIN is done under
System action: The system issues an ABEND dump. a different PSW key than the GETMAIN.
The system issues a message depending on the reason 18 The system could not find a private area
code accompanying the abend: subpool.
Code Message 1C Zero length is not specified on a subpool
04 CSV013I FREEMAIN. Zero length must be specified on
a subpool FREEMAIN.
08 CSV015I
20 One of the following:
0C CSV019I
v In the CSA, the area specified on a
10 CSV020I FREEMAIN is larger than the area specified
on the original GETMAIN.
20 CSV024I
v The FREEMAIN start address is not valid.
24 CSV027I
24 One of the following:
30 CSV025I v In the private area, the area specified on a
34 CSV026I FREEMAIN is larger than the area specified
on the original GETMAIN.
Application Programmer Response: If the requested
v The FREEMAIN start address is not valid.
module could not be found, make sure the module
exists on a system or user-defined authorized library. System action: The system issues message IEA705I.
Correct the error, and run the job step again. The system abnormally ends the current task.
System programmer response: If the error recurs Application Programmer Response: Do the
and the program is not in error, see the system following:
programmer response for accompanying messages in v Ensure that the FREEMAIN operands A and LV do
the job log for more information. not specify a different subpool and/or key than the
If the error recurs and the program is not in error, subpool or key of the storage you are trying to free.
search problem reporting data bases for a fix for the v Ensure that the task control block (TCB) specified on
problem. If no fix exists, contact the IBM Support the FREEMAIN request is the same one specified on
Center. Provide the source input for the job. the corresponding GETMAIN request.
Source: Contents supervision (CSV) v If a caller running in supervisor state and key 0 made
the original GETMAIN request, ensure that the
corresponding FREEMAIN request is issued in
supervisor state and key 0.
190 z/OS V1R10.0 MVS System Codes
30D • 312
If a caller in supervisor state and key 0 requests v A program in supervisor state issued the macro. The
storage in subpool 0 or 250, the system will satisfy macro should be issued by a program running in
this request with storage from a different subpool. problem state.
This situation is described in z/OS MVS Diagnosis: v The program that issued the macro had a program
Reference. status word (PSW) storage key that did not match the
v Check for program errors that incorrectly modify the task control block (TCB) key.
FREEMAIN macro expansion. v A program issued the macro in 31-bit addressing
Source: Virtual storage manager (VSM) mode.
System action: The system sends messages about
30D the problem to the job log. The system abends the
program that issued the macro.
Explanation: End of memory (EOM) processing has
detected that an EOM resource manager has been Application Programmer Response: If an application
inactive (not dispatched) for at least 4 minutes. That program issued the SPIE macro, check the program for
EOM resource manager is considered to have failed the errors listed in the explanation. If the program is in
and receives this abend. 31-bit addressing mode, use an ESPIE macro instead of
the SPIE macro. Correct the error. Run the job step
The hexadecimal reason codes are: again.
Code Explanation System programmer response: If an IBM program
00 The failing resource manager receives this issued the macro, search problem reporting data bases
reason code. for a fix for the problem. If no fix exists, contact the IBM
Support Center. Provide:
04 This reason code is used internally during the v Messages from the job log
detection process. This reason code may be v The ABEND or SVC dump
seen in the LOGREC record that the system v The assembly listing for the job
records for this abend. v The JCL for the job
v The program listing for the job
System action: The system takes a synchronous
SVCDUMP to capture the situation, then issues this Source: Recovery termination manager (RTM)
abend. The abend is retriable. If the EOM resource
manager’s recovery fails to retry, EOM processing will
continue with the next EOM resource manager. 312
Application Programmer Response: None. Explanation: An error occurred in a LNKLST or library
lookaside (LLA) directory data access routine. The
System programmer response: The title of the reason code in register 15 identifies the error:
SVCDUMP will begin with ″END OF MEMORY
RESOURCE MANAGER HANG DETECTED:″, and will Code Explanation
contain a TCB address as well as the name or address 1 LLA partitioned data set (PDS) search function
of the last EOM resource manager that was given failed. PDS search is used to obtain BLDL
control. The owner of that resource manager should format directory entries from the LLA directory.
examine the indicated TCB (which is in ASID 1) to
determine why it was not progressing and correct the 2 LLA fetch search function failed. Fetch search
situation that caused the resource manager to fail in this is used to obtain directory information needed
way. to retrieve a copy of a staged module from
LLA’s virtual lookaside facility (VLF) data
Note: Since the SVCDUMP is taken before ABEND30D space.
is issued (to provide a more clear picture of the 3 LLA logging function failed. LLA logging is used
problem), this abend will not be seen under the to record fetch statistics in the LLA directory for
failing TCB in the dump. It may be seen under a fetched module.
the detecting TCB (with reason code 04) and
should be ignored there. 4 LLA search failure count has reached the
allowed limit. The failures counted are only
Source: Recovery Termination Manager (RTM) those caused by an LLA directory problem
rather than those caused by a user problem.
30E System action: LLA does one of the following:
Explanation: A program incorrectly issued a SPIE v Issues message CSV222I and then initiates
macro in one of the following ways: automatic restart processing
v Issues message CSV218E and stops processing.
v An unauthorized program specified program
interruption code 17 on the macro.
Chapter 2. System Completion Codes 191
313 • 322
The system issues an SVC dump and writes a logrec System action: The STOW task recovery routine has
data set error record. been invoked. Low real storage and the caller’s region
have been dumped to the SYS1.DUMP data set. The
System programmer response: See the system
caller’s DCB and input registers 0 and 1 have been
programmer response for message CSV222I or
included in a software error record written to the logrec
CSV218E.
data set.
Source: Contents supervision (CSV)
Application Programmer Response: Make sure that
the STOW macro instruction is correctly coded, and that
313 the parameter list and DCB involved are not modified by
your program during the processing of SVC 21.
Explanation: The error occurred during processing of
an OPEN macro instruction for a data set on a direct System programmer response: If the error recurs
access device. This system completion code is and the program is not in error, look at the messages in
accompanied by message IEC144I. Refer to the the job log for more information. Search problem
explanation of message IEC144I for complete reporting data bases for a fix for the problem. If no fix
information about the task that was ended and for an exists, contact the IBM Support Center. Provide the
explanation of the return code (rc in the message text) JCL, the program listing for the job, the logrec data set
in register 15. error record, and all printed output and output data sets
related to the problem.
Application Programmer Response: Respond as
indicated for message IEC144I. Source: DFSMSdfp
System programmer response: If the error recurs
and the program is not in error, look at the messages in 317
the job log for more information. Search problem
Explanation: The error occurred during processing of
reporting data bases for a fix for the problem. If no fix
a BSAM CLOSE macro instruction with a TYPE=T
exists, contact the IBM Support Center. Provide the JCL
operand for a data set on a direct access device. This
and the program listing for the job.
system completion code is accompanied by message
Source: DFSMSdfp IEC220I. Refer to the explanation of message IEC220I
for complete information about the task that was ended
and for an explanation of the return code (rc in the
314 message text) in register 15.
Explanation: The error occurred during the processing Application Programmer Response: Respond as
of a CLOSE macro instruction for a data set on a direct indicated for message IEC220I.
access device. This system completion code is
accompanied by message IEC211I. Refer to the System programmer response: If the error recurs
explanation of message IEC211I for complete and the program is not in error, look at the messages in
information about the task that was ended and for an the job log for more information. Search problem
explanation of the return code (rc in the message text) reporting data bases for a fix for the problem. If no fix
in register 15. exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
Application Programmer Response: Respond as
indicated for message IEC211I. Source: DFSMSdfp
System programmer response: If the error recurs
and the program is not in error, look at the messages in 322
the job log for more information. Search problem
Explanation: One of the following occurred:
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL v The system took a longer time to run a job, job step,
and the program listing for the job. or procedure than the time specified in one of the
following:
Source: DFSMSdfp
– The TIME parameter of the EXEC or JOB
statement
315 – The standard time limit specified in the job entry
Explanation: An error occurred during the processing subsystem
of SVC 21 (STOW) that could not be attributed to v For a started task under the master subsystem, the
incorrect user input. This completion code is TIME parameter was not specified on the PROC
accompanied by message IEC911I. Refer to the statement of the catalogued procedure, and the PPT
explanation of message IEC911I for complete entry did not indicate a system task
information about the task that was ended and for an
System action: The system abnormally ends the job,
explanation of the return code in register 15.
job step, or procedure.
192 z/OS V1R10.0 MVS System Codes
328 • 32E
Application Programmer Response: If the TIME
32E
parameter was not specified on the PROC statement of
the catalogued procedure, add the TIME parameter or Explanation: When a program issued the STIMERM
add a PPT entry for the PGM parameter. Otherwise, service routine, an error occurred. Register 15 contains
check for program errors. If none exist, specify a longer a hexadecimal reason code:
time in the TIME parameter. Then run the job again.
Code Explanation
Source: System Management Facilities (SMF)
010C The Coordinated universal time (UTC),
time-of-day (TOD), or local time (LT) parameter
328 in a STIMERM SET macro specified a value
that was greater that 24 hours.
Explanation: During processing of an EXTRACT
macro, the system found that the task control block 0110 The TIMER service routine received an
(TCB) specified in the second operand was not for a incorrect STIMER or STIMER SET macro
subtask of the caller’s TCB. parameter. For example, a program running in
31-bit addressing mode is not using the
System action: The system abnormally ends the
MVS/SP Version 2 or later expansion of
program that issued the EXTRACT macro.
STIMER.
Application Programmer Response: Change the
011C The limit of concurrent STIMERM SET macro
EXTRACT macro to specify a TCB for a subtask. If the
requests was exceeded.
macro was specified correctly, check for program errors
that incorrectly modified the EXTRACT macro 0120 The timer service routine cannot access the
expansion. Correct the error. Run the job again. storage containing the parameters for the
STIMERM SET macro.
System programmer response: If the error recurs
and the program is not in error, look at the messages in 0128 The requested time interval was too large. One
the job log for more information. Search problem of these situations occurred: The time interval
reporting data bases for a fix for the problem. If no fix specified (BINTVL, DINTVL, MICVL, or
exists, contact the IBM Support Center. Provide the TUINTVL), added to the current TOD clock
source program listing for the job. contents, would have exceeded
X'FFFFFFFFFFFFFFFF' (a value that would
Source: Task management
expire on September 17, 2042). A value
greater than X'7FFFFFFF' was specified for
32D BINTVL.
Explanation: A program requested an overlay. In 0210 An incorrect parameter was specified on the
answer to the request, the overlay supervisor was using STIMERM TEST macro.
program fetch to load a program segment from the
0220 The timer service routine cannot access the
library. Fetch found one of the following:
storage containing the parameters for the
v A record of an incorrect length
STIMERM TEST macro.
v An uncorrectable input/output (I/O) error
0224 The STIMERM ID number specified for a TEST
Note: Overlay programs run only in 24-bit addressing request was 0, which is not valid.
mode, not in 31-bit addressing mode.
0310 An incorrect parameter was specified on the
System action: The system abnormally ends the STIMERM CANCEL macro.
program that requested the overlay. The system writes
0320 The timer service routine cannot access the
an ABEND dump, if a dump DD statement is provided.
storage containing the parameters for the
Operator response: If messages show an I/O error on STIMERM CANCEL macro.
the device containing the overlay segment, run the job
0324 The STIMERM ID number specified for a
step again. If the I/O error recurs, contact hardware
CANCEL request was 0, which is not valid.
support.
System action: The system abnormally ends the task
Application Programmer Response: If messages did
that issued the macro.
not show an I/O error, link edit and run the program
again. Application Programmer Response: Check and
correct the parameters specified on the STIMERM
Source: Overlay supervisor
macro. See z/OS MVS Programming: Assembler
Services Reference ABE-HSP for format and
restrictions. Check that a program running in 31-bit
addressing mode uses the MVS/SP Version 2 or later
expansion of STIMER.
Chapter 2. System Completion Codes 193
330 • 333
Source: Timer supervision Code Explanation
04 While dumping global storage, SVC Dump
330 (SDUMP) detected a start address that is
higher that the end address for a storage
Explanation: An unauthorized task attempted to use
range.
authorized options of the DEQ macro instruction during
the processing of global resource serialization. 08 The SDUMP VSM interface routine detected a
start address that is higher than the end
Register 15 may contain a reason code associated with
address for a storage range.
this error:
0C SDUMP has detected a LIST64 storage range
Code Explanation
with a start address that is higher than the end
xxxx0001 An unauthorized requester attempted address for a storage range.
to DEQ an authorized resource.
10 While dumping local storage, SDUMP detected
The list of authorized major names is a start address that is higher than the end
described in z/OS MVS Programming: address for a storage range.
Authorized Assembler Services
14 Before enqueueing on the SDUMP resource,
Reference ALE-DYN.
SDUMP detected that it was running in an
xxxx0002 An ISGNQXIT exit specified an address space that is not in the current dump.
authorized resource name for an
18 After enqueueing on the SDUMP resource,
unauthorized DEQ request.
SDUMP detected that it was running in an
The list of authorized major names is address space that is not part of the current
described in z/OS MVS Programming: dump.
Authorized Assembler Services
1C SDUMP is running in an environment that is
Reference ALE-DYN.
not valid.
xxxx0006 An unauthorized requester specified
20 While processing a synchronous dump, an
TCB or RMC.
SDUMP cross memory post failed to post a
xxxx0007 An unauthorized requester attempted task which was to complete the dump. SDUMP
to issue a generic request. recovery processing captured the local storage
which was still in real for the address space
The reason code could also be associated with an where the task was located, and then
ISGENQ Request=Release. See the reason codes terminated the address space. The dump is
listed for the ISGENO macro in z/OS MVS unavailable for user specified DCB SVC
Programming: Authorized Assembler Services dumps.
Reference EDT-IXG. 24 While dumping global storage, SDUMP
System action: The system issues an ABEND dump. experienced an internal error.
Application Programmer Response: Correct the 30 ABDUMP (SYSABEND, SYSUDUMP, or
macro instruction. Recompile and run the job step SYSMDUMP) did not produce a dump because
again. Either use an unauthorized major name or make another task holds a critical resource. Because
the program authorized. ABDUMP waited longer than the interval used
to determine if the resource was available, the
System programmer response: If the reason code is system determined that the task may never
X'0002', check your ISGNQXIT installation exits to release the resource. This abend was issued
ensure that they are not coded to specify an authorized and an SVC dump was requested instead of
major name for unauthorized requests. Otherwise, if the the ABDUMP dump. The dump title will include
problem persists, search problem reporting data bases the JOBNAME of the abending task. LOGREC
for a fix for the problem. If no fix exists, contact the IBM data contains the JOBNAME and the ENQ
Support Center. Provide the abend dump. name.
Source: Global resource serialization System action: Dump processing may write an error
record to the LOGREC data set. For ABDUMP reason
333 code 30 an SVC dump was requested instead with the
JOBNAME in the dump title and message IEA848I was
Explanation: During processing for a dump, an error issued.
occurred.
For the other codes:
Register 15 contains a hexadecimal reason code that
explains the error: Dump data collection ends and SDUMP proceeds to
clean up its system resources. Message IEA794I
194 z/OS V1R10.0 MVS System Codes
335 • 338
indicates which job requested the dump. When the exists, contact the IBM Support Center. Provide the
dump is written to DASD, message IEA911E or IEA611I JCL, the program listing, and the compiler output for the
contains the SDRSN bits which indicate the reasons for job.
an incomplete dump.
Source: DFSMSdfp
Operator response: Determined by the system
programmer.
338
System programmer response: For ABDUMP reason
Explanation: An unauthorized task attempted to use
code 30, see the information for message IEA848I. For
authorized options of the ENQ macro instruction during
SDUMP reason codes, when necessary, ask the
the processing of global resource serialization.
operator to set a SLIP trap with ACTION=WAIT to
obtain a standalone dump if abend X'333' recurs. Register 15 may contain a reason code associated with
this error:
Source: Dumping services
Code Explanation
335 xxxx0001 An unauthorized requester attempted
to ENQ an authorized resource.
Explanation: SVC 53, which obtains and releases
exclusive control of a resource associated with a BDAM The list of authorized major names is
data set, found that the block for which acquisition or described in z/OS MVS Programming:
release of exclusive control was requested was not in Authorized Assembler Services
the data set. Reference EDT-IXG
Application Programmer Response: If the RELEX xxxx0002 An ISGNQXIT exit specified an
macro was issued the user should ensure that the authorized resource name for an
BLKREF address supplied in the RELEX macro points unauthorized ENQ request.
to a valid address within the data set described by the
input DCB. Make sure that the address format is The list of authorized major names is
compatible with the addressing scheme specified in the described in z/OS MVS Programming:
DCBOPTCD field of the DCB. If the RELEX macro was Authorized Assembler Services
not issued, the block ID was taken from the IOBSEEK Reference EDT-IXG.
field, or in the case of write-add requests, the xxxx0003 An unauthorized requester attempted
IOBDNCRF field. These addresses are derived from to RESERVE a device that is not
conversion of the block ID pointed to by the allocated to the requesting task.
DECRECPT field of the DECB. Make sure that this
address is correct and that the format of the block ID is xxxx0004 An ISGNQXIT exit specified a UCB for
compatible with that specified in the DCBOPTCD field of a device that is not allocated to the
the DCB and that the format of the block ID is requesting, unauthorized task.
left-aligned. xxxx0005 An unauthorized requester attempted
System programmer response: If the error recurs to issue a MASID request.
and the program is not in error, search problem xxxx0006 An unauthorized requester specified
reporting data bases for a fix for the problem. If no fix TCB or SMC.
exists, contact the IBM Support Center.
xxxx0008 An unauthorized requester attempted
Source: DFSMSdfp to issue an ECB request.
337 The reason code could also be associated with an
ISGENQ Request=Obtain or Request=Change. See the
Explanation: The error occurred when the end of a reason codes listed for the ISGENQ macro in z/OS
data set was reached. This system completion code is MVS Programming: Authorized Assembler Services
accompanied by message IEC024I. Refer to the Reference EDT-IXG.
explanation of message IEC024I for complete
information about the task that was ended and for an System action: The system writes an ABEND dump.
explanation of the return code (rc in the message text) Application Programmer Response: Correct the
in register 15. macro instruction. Recompile and run the job step
Application Programmer Response: Respond as again.
indicated for message IEC024I. If the problem persists, do the following:
System programmer response: If the error recurs 1. Obtain the address of the ENQ parameter list from
and the program is not in error, look at the messages in register 1 in the UNIQUE-3 column of the SVC 30 or
the job log for more information. Search problem SVC 38 entry in the system trace.
reporting data bases for a fix for the problem. If no fix
Chapter 2. System Completion Codes 195
339 • 351
2. Check the parameter list against the SVC 30 or 38 System programmer response: If the error recurs
mapping. When analyzing the parameter list, and the program is not in error, look at the messages in
remember that the unit control block (UCB) pointer, the job log for more information. Search problem
if present, is the address of a field that, in turn, reporting data bases for a fix for the problem. If no fix
contains the address of the UCB. exists, contact the IBM Support Center. Provide the
If the parameter list contains incorrect data, continue source program listing for the job.
diagnosis in the program that issued the macro. Source: Task management
System programmer response: If the reason code is
X'0002', check your ISGNQXIT installation exits to 33F
ensure that they are not coded to specify an authorized
major name for unauthorized requests. If the reason Explanation: An error has been detected during
code is X'0004', ensure that the installation exits do not checkpoint restart processing. This completion code is
modify the UCB to specify one that is not allocated to accompanied by message IHJxxxI with the appropriate
an unauthorized requests. Otherwise, if the problem reason code.
persists, search problem reporting data bases for a fix System action: No dump is produced; the system
for the problem. If no fix exists, contact the IBM Support attempts to retry to the cleanup address.
Center. Provide the ABEND dump.
Application Programmer Response: Respond as
Source: Global resource serialization indicated in the accompanying message.
Source: DFSMSdfp
339
Explanation: SVC 57, which frees a buffer or extends 344
the unscheduled list (via a FREEDBUF macro issued
either by the user or by the system) found that the DEB Explanation: The error occurred during the processing
pointed to by the input DCB (DCBDEBAD) was not on of SYNADAF, where it was determined that the DCB
any DEB chain associated with that job step TCB, or did address was incorrect.
not point back to that DCB, or the request was issued
Application Programmer Response: Register 15
for a data set that was neither BDAM or ISAM.
contains the DCB address in error. For BDAM, BPAM,
Application Programmer Response: Make sure that QSAM, BISAM, and QISAM, the DCB address should
the input DCB address is correct and that the be passed to SYNADAF as the PARM1 operand on the
DCBDEBAD field of the input DCB has not been SYNADAF macro instruction. (For BDAM, BPAM,
overlaid. BSAM, and QSAM, the DCB address is in register 1 on
entry to the user’s SYNAD routine.) For EXCP access
System programmer response: If the error recurs method, verify that the IOBDCBPT field contains the
and the program is not in error, search problem correct DCB address. Correct the error and rerun the
reporting data bases for a fix for the problem. If no fix job.
exists, contact the IBM Support Center.
System programmer response: If the error recurs
Source: DFSMSdfp and the program is not in error, look at the messages in
the job log for more information. Search problem
33E reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL
Explanation: During processing of a DETACH macro and the program listing for the job.
that specified a STAE=YES operand, the system found
that the specified subtask had not completed Source: DFSMSdfp
processing.
System action: The system abnormally ends the 351
subtask. If the STAE macro was issued by the subtask, Explanation: An error was detected during the
the specified recovery routine gains control during processing of SETPRT that could not be attributed to
abend processing. However, if the STAE exit routine incorrect macro instruction invocation or incorrect
specified a retry routine, the retry routine does not gain control blocks. This system completion code is
control. accompanied by message IEC918I. Refer to the
Application Programmer Response: This may or explanation of message IEC918I for complete
may not be an error, depending on the programmer’s information about the task that was ended and for an
intent. If the subtask should complete processing before explanation of the return code in register 15.
it is detached, synchronize the processing through the Application Programmer Response: Make sure that
ECB or ETXR parameters on the ATTACH macro that the SETPRT macro instruction is correctly coded, and
creates the subtask. that the parameter list and DCB involved are not
196 z/OS V1R10.0 MVS System Codes
35F • 378
modified by your program during the processing of SVC The system writes an ABEND dump for the failing job
81. step.
System programmer response: If the error recurs System programmer response:
and the program is not in error, look at the messages in
Obtain the SYSOUT output for the job.
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix Obtain the ABEND dump for the failing job step. If the
exists, contact the IBM Support Center. Provide the JCL for the step did not contain a DD statement for an
JCL, the program listing for the job, and the logrec data ABEND dump, add one of the following statements and
set error record. run the job step again:
SYSABEND DD statement
Source: DFSMSdfp
SYSMDUMP DD statement
SYSUDUMP DD statement
35F
Use a SYSMDUMP DD statement if you plan to analyze
Explanation: In order to initiate a nonswappable
and format the dump with the interactive problem
program or V=R job step, the system issued a
control system (IPCS).
SYSEVENT TRANSWAP macro to swap out an address
space. One of the following situations occurred:
Obtain the logrec data set error record.
v Before the system could complete the swap, the
address space became unswappable.
Search problem reporting data bases for a fix for the
v The swap could not be executed because the swap problem. If no fix exists, report the problem to the IBM
HOLD count in the OUCB was non-zero. Support Center.
System action: The system abnormally ends the Source: Resource Measurement Facility (RMF)
initiator of the job. The system writes messages and a
logrec data set error record.
36F
System programmer response: This is probably a
system error. Resubmit the job. If the error recurs, Explanation: One of the following errors occurred
search problem reporting data bases for a fix for the during processing of a job entry subsystem SVC 111:
problem. If no fix exists, contact the IBM Support v An non-valid entry code was passed to SVC 111.
Center. Provide the logrec data set error record and the v DEBCHK processing found that the DEB (data extent
SYSOUT output for the job. block) was invalid.
Source: Initiator, based on a decision by the System v The DEB was not a subsystem DEB.
Resources Manager (SRM)
System action: The program issuing the SVC
Detecting Module: IEFSD263 terminates.
System programmer response: Be sure the program
36D is authorized to use SVC 111 and check that the SVC is
issued at the correct point in the program. Correct the
Explanation: An error was detected in
error and rerun the job.
communications between RMF and the System
Resources Manager while attempting to initialize, If the problem recurs and if the program is not in error,
collect, or reinitialize workload activity measurements. search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support
System action: All RMF measurement collection is
Center.
terminated. Reinstatement can be attempted and, if
successful, RMF will continue under the control of the Source: JES2
original options. If reinstatement fails, RMF is
terminated. Register 15 contains the return code from
378
the System Resources Manager depending on the
function attempted by RMF: Explanation: An error when the system tried to
process an RU or VRU form of the FREEMAIN macro
Byte Attempted Function
or the STORAGE RELEASE macro. A reason code in
0 N/A the SDWACRC field of the system diagnostic work area
(SDWA) explains the error:
1 Reinitialization of workload activity
measurement collection after a change in the Code Explanation
Installation Performance Specification (IPS).
08 System queue area (SQA) storage is not in the
2 Collection of workload activity measurements. specified subpool.
3 Initialization of workload activity measurements.
Chapter 2. System Completion Codes 197
37A • 37D
0C Common storage area (CSA) storage is not in v Check for program errors that incorrectly modify the
the specified subpool, or it is not in the FREEMAIN or STORAGE RELEASE macro
specified key. expansion.
10 Local system queue area (LSQA) storage is Source: Virtual storage manager (VSM)
not in the specified subpool.
14 Private area storage is not in the specified 37A
subpool, is not in the specific key or is not
Explanation: During processing of an EVENTS macro,
owned by the specified task.
the system found that another task was currently waiting
18 The system could not find a private area on the EVENTS table.
subpool.
System action: The system abnormally ends the
1C A user has requested that storage at virtual program that issued the EVENTS macro.
address 0 be freed. This can happen if the
Application Programmer Response: Ensure that
user intended an entire subpool, but has
only one task at one time can wait on the EVENTS
incorrectly specified a non-zero length with an
table. Correct the error. Run the job again.
address of 0. Zero length must be specified on
a subpool FREEMAIN or STORAGE System programmer response: If the error recurs
RELEASE. Another possibility is that the user and the program is not in error, look at the messages in
has specified the wrong address. the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
20 One of the following:
exists, contact the IBM Support Center. Provide the
v In the CSA, the area specified on a program listing and the assembly listing associated with
FREEMAIN or STORAGE RELEASE is the job.
larger than the area specified on the original
GETMAIN or STORAGE OBTAIN. Source: Task management
v The FREEMAIN or STORAGE RELEASE
start address is not valid. 37B
24 One of the following: Explanation: While the system was processing a
v In the private area, the area specified on a PURGEDQ macro, an error occurred in a resource
FREEMAIN or STORAGE RELEASE is manager termination routine (RMTR).
larger than the area specified on the original System action: The system records the address of
GETMAIN or STORAGE OBTAIN. the failing service request block (SRB) in a logrec data
v The FREEMAIN or STORAGE RELEASE set error record. The system asks for a retry and
start address is not valid. PURGEDQ processing continues. The system does not
return control to the RMTR in which the error occurred.
System action: The system issues message IEA705I.
The system abnormally ends the current task. System programmer response: Do the following:
Application Programmer Response: Do the v Use the program status word (PSW) address in the
following: logrec data set error record to identify the failing
RMTR.
v Ensure that the FREEMAIN or STORAGE RELEASE
operands A and LV do not specify a different subpool v Search problem reporting data bases for a fix for the
and/or key than the subpool or key of the storage you problem. If no fix exists, contact the component group
are trying to free. associated with this module at the IBM Support
Center. Provide the logrec data set error record.
v Ensure that the task control block (TCB) specified on
the FREEMAIN or STORAGE RELEASE request is Source: Supervisor control
the same one specified on the corresponding
GETMAIN or STORAGE OBTAIN request.
37D
v If a caller running in supervisor state and key 0 made
the original GETMAIN or STORAGE OBTAIN Explanation: During processing of an EVENTS macro,
request, ensure that the corresponding FREEMAIN or the system found that another task was currently waiting
STORAGE RELEASE request is issued in supervisor on the EVENTS table.
state and key 0.
System action: The system abnormally ends the
If a caller in supervisor state and key 0 requests program that issued the EVENTS macro.
storage in subpool 0 or 250, the system will satisfy
this request with storage from a different subpool. Application Programmer Response: Ensure that no
This situation is described in z/OS MVS Diagnosis: program can issue any EVENTS macro that specifies a
Reference. table currently being waited on. Correct the error. Run
the job again.
198 z/OS V1R10.0 MVS System Codes
382 • 3C2
System programmer response: If the error recurs
385
and the program is not in error, look at the messages in
the job log for more information. Search problem Explanation: The RACROUTE REQUEST=VERIFY
reporting data bases for a fix for the problem. If no fix preprocessing or postprocessing exit routine passed an
exists, contact the IBM Support Center. Provide the invalid return code to RACF. The return code was not
program listing and the assembly listing associated with part of the defined interface.
the job.
System action: The system abnormally terminates the
Source: Task management task.
Application Programmer Response: Possible user
382 error. Register 15 contains the return code from the exit
routine. Verify that the exit routine is issuing using valid
Explanation: The RACROUTE REQUEST=AUTH
return codes. See z/OS Security Server RACROUTE
preprocessing or postprocessing exit routine passed an
Macro Reference for the correct return codes.
invalid return code to RACF. The return code was not
part of the defined interface. System programmer response: If the installation exit
is issuing a correct return code and RACF still issues
System action: The system abnormally terminates the
this abend, call your IBM support center for advice
task.
about whether this is a documentation error or an
Application Programmer Response: Possible user incorrect output error. See z/OS Security Server RACF
error. Register 15 contains the return code from the exit Diagnosis Guide for information on reporting
routine. Verify that the exit routine is issuing valid return documentation errors or incorrect output to IBM.
codes.
Note: Before calling IBM, make sure the return code
System programmer response: If the installation exit
passed by the installation exit is correct.
is issuing a correct return code and RACF still issues
this abend, call your IBM support center for advice
about whether this is a documentation error or an 3C2
incorrect output error.
Explanation: The MQSeries Workflow for OS/390
workload manager selector subtask encountered a
Note: Before calling IBM, make sure the return code
severe internal error.
passed by the installation exit is correct.
The reason code identifies the source of the error. It has
the format X'rrmmnnnn', where rr denotes the resource
383
class (as detailed in the table that follows), mm denotes
Explanation: The RACROUTE REQUEST=VERIFY the method of the resource class, and nnnn identifies
preprocessing or postprocessing exit routine passed an the place within the method where the error was
invalid return code to RACF. The return code was not encountered.
part of the defined interface.
Resource Resource Resource
System action: The system abnormally terminates the Class Code Name Description
task.
01 Resource abstract class for
Application Programmer Response: Possible user workflow server
error. Register 15 contains the return code from the exit resources
routine. Verify that the exit routine is issuing valid return
02 FmSrvRes abstract class for
codes. See z/OS Security Server RACROUTE Macro
workflow server
Reference for the correct return codes.
instance resources
System programmer response: If the installation exit
03 RmDevRes abstract class for
is issuing a correct return code and RACF still issues
workflow server
this abend, call your IBM support center for advice
input/output device
about whether this is a documentation error or an
resources
incorrect output error. See z/OS Security Server RACF
Diagnosis Guide for information on reporting 04 SystCons implementation class
documentation errors or incorrect output to IBM. for the system
console interface
Note: Before calling IBM, make sure the return code 05 Diagnose implementation class
passed by the installation exit is correct. for the flight recorder
06 FifoLock implementation class
for the queue
serialization
Chapter 2. System Completion Codes 199
3C4
Resource Resource Resource contact the IBM Support Center and provide the ABEND
Class Code Name Description dump.
07 MvsMsgSv implementation class Source: MQSeries Workflow for OS/390
for the MVS message
services interface 3C4
08 DevQueue implementation class
Explanation: During system processing, an internal
for the in-storage
system request encountered an unexpected error.
queues
Register 15 contains a hexadecimal reason code.
09 ErrStack implementation class
for the error recovery Code Explanation
10 ServerDS implementation class 00000001 Recovery routine (ESTAEX) could not
for the data set be established.
access
00000002 The request came from an
11 Security implementation class unauthorized program.
for the security server
interface 00000003 Not enough storage was available.
12 SrvGroup implementation class 00000004 POST returned an an error code.
for the subtask
00000005 ATTACH did not complete
management
successfully.
13 SynchEcb implementation class
00000006 LXRES did not complete successfully.
for the subtask
synchronization 00000007 AXSET did not complete successfully.
14 TimeServ implementation class 00000008 Too many ETEs (entry table entries).
for the timer interface
00000009 Incorrect EX (entry index)
15 ExtTrace implementation class
for the component 0000000A ARR (associated recovery routine) not
trace interface found.
16 TaskServ implementation class 0000000B A PC integrity error occurred.
for the subtask
0000000C A PC provided an incorrect attribute.
services
0000000D ETCRE did not complete successfully.
17 WkldMgmt implementation class
for the workload 0000000E ETCON did not complete successfully.
manager interface
0000000F An unexpected error occurred.
18 XcfGroup implementation class
for the cross-system 00000010 ENQ did not complete successfully.
coupling facility 00000011 Start was incorrect.
interface
00000012 The SSCVT was incorrect.
19 XLngServ implementation class
for the 00000013 The DSCT was incorrect.
cross-language
00000014 Dispatcher control blocks were
services
incorrect.
20 XMemServ implementation class
00000015 ALESERV did not complete
for the cross-memory
successfully.
services
00000016 DSPSERV did not complete
successfully.
System action: The system issues an ABEND dump.
00000017 IEFJSVEC did not complete
Application Programmer Response: None.
successfully.
System programmer response: For reason code
00000018 A required routine could not be found.
X'1726nnnn', verify the setup for the workload manager
application environment and restart the server. 00000019 RESMGR did not complete
successfully.
For other reason codes, search the problem reporting
data bases for a fix for the problem. If no fix exists, 0000001A Recovery was entered and there was
200 z/OS V1R10.0 MVS System Codes
3C5 • 3C6
no available entry on the dynamic the first fullword of the range entry
area stack for the recovery routine to must be aligned on a segment
use. boundary. A segment is 1 megabyte
(1,048,576 bytes) long.
0000001B The stack storage has been used up.
Programmer Response: Correct the
System action: If the error occurred during address
first fullword of the range list entry to
space initialization, the initialization process terminates.
specify a storage address on a
Application Programmer Response: Search problem segment boundary, and resubmit the
reporting data bases for a fix for the problem. If no fix job.
exists, contact the IBM Support Center, providing the
xx0112xx IARSUBSP IDENTIFY failed. The
reason code that accompanies the abend.
storage specified by the range list
Source: MVS reuse entry must be pageable and located in
either high private or low private
storage, and must have been
3C5 previously obtained using the
Explanation: This abend is issued by the TCP/IP STORAGE or GETMAIN macro.
product. For more information, see TCP/IP abend 3C5 Programmer Response: Correct the
reason codes in z/OS Communications Server: IP and range list entry to specify pageable,
SNA Codes. private storage, or change the
subpool from which the storage was
3C6 obtained, and resubmit the job.
Explanation: An error occurred during IARSUBSP xx0113xx IARSUBSP IDENTIFY failed. The
macro processing. storage specified by the range list
entry must be owned by one of the
System action: The system fails the IARSUBSP following:
request. v The calling task
Application Programmer Response: Take the action v The task that previously issued
indicated by Programmer Response in the reason IARSUBSP IDENTIFY
code description. v A task higher in the task hierarchy
than the calling task or the task that
Source: Real Storage Manager (RSM) previously issued IARSUBSP
The reason code in register 15 identifies the error. IDENTIFY.
When an entry in the range list (specified on the
RANGLIST parameter) causes the abend, GPR 2 Programmer Response: Correct the
contains the address of the range list element in error range list entry to specify storage
and GPR 3 contains the address of the storage being owned by one of the tasks listed in
processed. the error description. If the range list
entry is correct, redesign the program
Code Meaning so that the task that issues the
xx0108xx IARSUBSP IDENTIFY failed. The IARSUBSP IDENTIFY (or a task
value specified in the NUMRANGE higher in the task hierarchy) owns the
parameter must be greater than zero storage and is the task that issued
and not greater than 16. any previous IARSUBSP IDENTIFY
requests.
Programmer Response: Correct the
value on the NUMRANGE parameter. xx0116xx Subspace identity failed. A segment in
the storage range is part of a shared
xx0109xx IARSUBSP IDENTIFY failed. The segment.
number of pages specified by the
second fullword of the range list entry Programmer Response: Correct the
must be greater than 0 and a multiple storage range list entry to specify a
of 256. storage range that does not include
pages that are part of a shared
Programmer Response: Correct the segment.
second fullword of the range list entry
to specify the correct amount of xx0211xx IARSUBSP CREATE failed. The
storage and resubmit the job. subspace name is incorrect. The
name must not be blank, or begin with
xx010Axx IARSUBSP IDENTIFY failed. The a numeric character. The name must
address of the storage specified by be left-justified, padded to the right
Chapter 2. System Completion Codes 201
3C6
with blanks, and must contain only above 16 megabytes. A segment is 1
alphanumeric characters and the megabyte (1,048,576 bytes) long.
characters @, $, and #.
Programmer Response: Correct the
Programmer Response: Correct the first fullword of the range list entry to
subspace name specified on the specify a storage address on a
NAME parameter, and resubmit the segment boundary, and resubmit the
job. job.
xx0301xx IARSUBSP ASSIGN failed. The xx030Bxx IARSUBSP ASSIGN failed. The range
caller’s primary and home address list entry must specify an address that
spaces must be the same. is aligned on a page boundary for
storage addresses below 16
Programmer Response: Change the
megabytes.
cross memory mode so that the
primary and home address spaces are Programmer Response: Correct the
the same, and resubmit the job. first fullword of the range list entry to
specify a storage address on a page
xx0302xx IARSUBSP ASSIGN failed. The caller
boundary, and resubmit the job.
held a lock.
xx030Cxx IARSUBSP ASSIGN failed. The
Programmer Response: Release all
specified STOKEN does not represent
locks and resubmit the job.
a valid subspace.
xx0303xx IARSUBSP ASSIGN failed. A
Programmer Response: Correct the
protection exception occurred while
value specified on the STOKEN
the caller was referencing the
parameter and resubmit the job.
parameter list.
xx0310xx IARSUBSP ASSIGN failed. The range
Programmer Response: The
must have been specified on a prior
parameter list must be in storage that
IARSUBSP IDENTIFY request before
the caller can access. Make sure the
it can be specified on IARSUBSP
storage was obtained by the caller or
ASSIGN.
passed to the caller by a task higher
in the task hierarchy. Programmer Response: Ensure that
you are supplying the correct range
xx0304xx IARSUBSP ASSIGN failed. The caller
list to IARSUBSP ASSIGN, and that
issued a macro version that is not
the values in the range list are correct.
valid.
If so, correct your program design to
Programmer Response: Use the issue IARSUBSP IDENTIFY before
IARSUBSP macro to generate the issuing IARSUBSP ASSIGN, and
parameter list. rerun the program.
xx0308xx IARSUBSP ASSIGN failed. The value xx0311xx IARSUBSP ASSIGN failed. The range
specified in the NUMRANGE already is assigned to another
parameter must be greater than zero subspace.
and not greater than 16.
Programmer Response: None
Programmer Response: Correct the necessary. However, you might want
value on the NUMRANGE parameter. to take some action depending on
your program. If you resubmit the job,
xx0309xx IARSUBSP ASSIGN failed. The specify a different range of storage
number of pages specified by the that is eligible to be assigned to a
second fullword of the range list entry subspace but not yet assigned.
must be greater than 0 and a multiple
of 256 for storage addresses above xx0312xx IARSUBSP ASSIGN failed. The range
16 megabytes. cannot span across either the
16-megabyte boundary or the
Programmer Response: Correct the 2-gigabyte boundary.
value specified in the second fullword
of the range list entry, and resubmit Programmer Response: Change the
the job. second fullword of the range list entry
to specify a valid storage range, and
xx030Axx IARSUBSP ASSIGN failed. The range resubmit the job.
entry must be aligned on a segment
boundary for storage addresses xx0401xx IARSUBSP UNASSIGN failed. The
202 z/OS V1R10.0 MVS System Codes
3C6
caller’s primary and home address address that is aligned on a page
spaces must be the same. boundary for storage addresses below
16 megabytes.
Programmer Response: Change the
cross memory mode so that the Programmer Response: Correct the
primary and home address spaces are first fullword of the range list entry to
the same, and resubmit the job. specify a storage address on a page
boundary, and resubmit the job.
xx0402xx IARSUBSP UNASSIGN failed. The
caller held a lock. xx040Cxx IARSUBSP UNASSIGN failed. The
specified STOKEN does not represent
Programmer Response: Release all
a valid subspace.
locks and resubmit the job.
Programmer Response: Correct the
xx0403xx IARSUBSP UNASSIGN failed. A
value specified on the STOKEN
protection exception occurred while
parameter and resubmit the job.
the caller was referencing the
parameter list. xx0412xx IARSUBSP UNASSIGN failed. The
range cannot span across either the
Programmer Response: The
16-megabyte boundary or the
parameter list must be in storage that
2-gigabyte boundary.
can be read by the calling program.
Programmer Response: Change the
xx0404xx IARSUBSP UNASSIGN failed. The
second fullword of the range list entry
caller issued a macro version that is
to specify a valid storage range, and
not valid.
resubmit the job.
Programmer Response: Use the
xx050Cxx IARSUBSP DELETE failed. The
IARSUBSP macro to generate the
specified STOKEN does not represent
parameter list.
a valid subspace.
xx0408xx IARSUBSP UNASSIGN failed. The
Programmer Response: Correct the
value specified in the NUMRANGE
value specified on the STOKEN
parameter must be greater than zero
parameter and resubmit the job.
and not greater than 16.
xx0510xx IARSUBSP DELETE failed. The caller
Programmer Response: Correct the
is running in or is eligible to run in the
value on the NUMRANGE parameter.
subspace that is to be deleted.
xx0409xx IARSUBSP UNASSIGN failed. The
Programmer Response: Correct the
number of pages specified by the
STOKEN supplied on the STOKEN
second fullword of the range list entry
parameter. If the STOKEN is correct,
must be greater than 0 and a multiple
change the program design to switch
of 256 for storage addresses above
to full address space addressability
16 megabytes.
before attempting to delete the
Programmer Response: Correct the subspace.
value specified in the second fullword
xx0511xx IARSUBSP DELETE failed. Another
of the range list entry and resubmit
program is running in or is eligible to
the job.
run in the subspace that is to be
xx040Axx IARSUBSP UNASSIGN failed. The deleted.
range entry must be aligned on a
Programmer Response: Correct the
segment boundary for storage
STOKEN supplied on the STOKEN
addresses above 16 megabytes. A
parameter. If the STOKEN is correct,
segment is 1 megabyte (1,048,576
change the program design to delete
bytes) long.
the subspace after the program has
Programmer Response: Correct the finished processing.
first fullword of the range list entry to
xx0512xx IARSUBSP DELETE failed. The caller
specify a storage address on a
does not own the subspace to be
segment boundary, and resubmit the
deleted.
job.
Programmer Response: Correct the
xx040Bxx IARSUBSP UNASSIGN failed. The
STOKEN supplied on the STOKEN
range list entry must specify an
parameter. If the STOKEN is correct,
Chapter 2. System Completion Codes 203
3C6
change the program design so the Programmer Response: Use the
task that created the subspace IARSUBSP macro to generate the
deletes it. parameter list.
xx0608xx IARSUBSP UNIDENTIFY failed. The xxFF05xx IARSUBSP failed. The reserved fields
value specified in the NUMRANGE in caller’s IARSUBSP parameter list
parameter must be greater than zero must be zeros.
and not greater than 16.
Programmer Response: Ensure that
Programmer Response: Correct the you are running the program on the
value on the NUMRANGE parameter. correct MVS release, and that you use
the IARSUBSP macro to generate the
xx0609xx IARSUBSP UNIDENTIFY failed. The
parameter list.
number of pages specified by the
second fullword of the range list entry xxFF06xx IARSUBSP failed. The caller
must be greater than 0 and a multiple requested a service that is not valid.
of 256.
Programmer Response: Use the
Programmer Response: Correct the IARSUBSP macro to generate the
second fullword of the range list entry parameter list.
to specify the correct amount of
xxFF07xx IARSUBSP failed. The caller must be
storage and resubmit the job.
in 31-bit addressing mode to use
xx060Axx IARSUBSP UNIDENTIFY failed. The IARSUBSP.
address of the storage specified by
Programmer Response: Change to
the first fullword of the range entry
31-bit addressing mode by issuing the
must be aligned on a segment
BASSM or BSM instruction, then
boundary. A segment is 1 megabyte
resubmit the job. BASSM and BSM
(1,048,576 bytes) long.
are described in Principles of
Programmer Response: Correct the Operation.
first fullword of the range list entry to
xxFF07xx IARSUBSP failed. The caller must be
specify a storage address on a
in 31-bit addressing mode to use
segment boundary, and resubmit the
IARSUBSP.
job.
Programmer Response: Change to
xxFF01xx IARSUBSP failed. The caller’s
31-bit addressing mode by issuing the
primary, secondary, and home
BASSM or BSM instruction, then
address spaces are not the same (the
resubmit the job. BASSM and BSM
caller is in cross memory mode.)
are described in Principles of
Programmer Response: Change the Operation.
cross memory mode so that the
xxFF08xx IARSUBSP failed; caller must not
primary, secondary, and home
have virtual space above 2G.
address spaces are the same, and
resubmit the job. Programmer Response: In order to
use subspaces, the program must be
xxFF02xx IARSUBSP failed. The caller held a
running in an address space that has
lock.
not previously used virtual storage
Programmer Response: Release all above 2 gigabyes. The programmer
locks and resubmit the job. should either run the program as a
started task, or submit the program to
xxFF03xx IARSUBSP failed. A protection
run in an initiator job class (set by the
exception occurred while the caller
installation) that limits address spaces
was referencing the parameter list.
to 2 gigabytes.
Programmer Response: The
xxFF0Exx IARSUBSP failed. The caller must be
parameter list must be in storage that
in task mode.
can be read by the calling program.
For a CREATE request, the parameter Programmer Response: Change the
list must be in storage that can also program design to ensure that the
be modified by the calling program. IARSUBSP macro is invoked in task
mode, and resubmit the job.
xxFF04xx IARSUBSP failed. The caller issued a
macro version that is not valid.
204 z/OS V1R10.0 MVS System Codes
3C7 • 3FC
Identify and correct the indicated error.
3C7
Explanation: An error occurred while RACF was
3FB
attempting to either allocate or unallocate dynamic
storage while RACF was running in SRB mode. Explanation: JES3 could not obtain enough storage to
either build a data set block (DSB) or to build a data set
System programmer response: Using IPCS, format
status block (DSS).
the dump taken for this abend. For an explanation of
the dump title, see z/OS Security Server RACF System action: The system ends the user address
Diagnosis Guide. space.
Look at the messages in the job log for more System programmer response: Rerun the job with a
information. Search problem reporting data bases for a SYSABEND DD statement. The problem may not recur.
fix for the problem. If no fix exists, contact the IBM If it does, notify the IBM Support Center.
Support Center.
Source: JES3
Source: Resource Access Control Facility (RACF)
The reason code in register 15 identifies the error: 3FC
Code Explanation Explanation: The system detected an error in the
processing following an external interrupt. The program
04 BAD LENGTH: The length of the area to get or
that experienced the external interrupt is running under
free is not greater than zero.
a task control block (TCB) or service request block
08 BAD ALIGNMENT: The pointer to the area to (SRB).
free is not on a doubleword boundary.
A hexadecimal reason code in register 15 explains the
0C DUPLICATE FREEMAIN: The area to free has error:
already been freed.
Code Explanation
10 INCORRECT SUBPOOL: The subpool for the
00 The system detected, but does not support, a
area to free is not the subpool in which the
third recursion of this interrupt.
area is allocated.
04 An error occurred during processing for the
14 INVALID OVERLAP: Part of the area to free
interrupt.
equals part of the area allocated, but the match
is not correct for either a full or partial 08 An error occurred during a first recursion.
FREEMAIN.
0C An error occurred during a second recursion.
18 NOT FOUND: The area to free does not have
a corresponding GETMAIN entry in the tracking System action: The system abnormally ends the
table, and the caller did not specify that it active task that experienced the external interrupt. The
should not have. system writes a logrec data set error record.
1C FOUND: The area to free has a corresponding Operator response: If the system programmer asks
GETMAIN entry in the tracking table, and the for an SVC dump, set the following SLIP trap:
caller specified that it should not have. SLIP SET,COMP=3FC,ACTION=SVCD,END
20 NOT FREED: There is a temporary area still Application Programmer Response: Resubmit the
allocated at the end of processing. job. If the error recurs, contact the system programmer.
A0 A RACF module issued a get-space request. System programmer response: Do the following:
However, register 1 is not equal to zero and v Find the original abend causing the problem in the
does not point to a buffer previously created by system diagnostic work area (SDWA) in the logrec
the program. data set error record.
A4 A RACF module issued a get-space request. v Search problem reporting data bases for a fix for the
However, the subpool in register 0 is not the problem. If no fix exists, ask the operator to set a
subpool in which the previously created buffer SLIP trap to obtain an SVC dump. Contact the IBM
is allocated. Support Center. Provide the SVC dump and the
logrec data set error records.
A8 A RACF module issued a free-space request.
However, register 1 is equal to zero. Source: Supervisor control
AC A RACF module issued a free-space request.
However, register 1 does not point to the buffer
previously created by the program.
Chapter 2. System Completion Codes 205
400 • 402
10 A caller who held a lock issued a WAIT macro
400
with the LINKAGE=SYSTEM option.
Explanation: Execute channel program (EXCP)
14 A caller who was not processing in task mode
processing found an error while processing an I/O
issued a WAIT macro with the
request. One of the following is true:
LINKAGE=SYSTEM option.
v The address for the data control block (DCB) in the
data extent block (DEB) is not the same as the DCB 18 A caller who was not processing in primary
address in the caller’s input/output block (IOB). This address space control (ASC) mode issued a
situation can occur if the data set is not open or if the WAIT macro with the LINKAGE=SYSTEM
control blocks are prematurely freed or overlaid. option.
v The program issued an EXCPVR macro for a DCB System action: The system abnormally ends the
that was opened for BSAM, BPAM, or QSAM. Those program that issued the WAIT macro.
access methods allow the user program to issue
EXCP or XDAP but not EXCPVR. Application Programmer Response: This is probably
an error in the calling program. Modify the code to allow
v BSAM, BPAM, or QSAM detected that control blocks the WAIT macro to be issued in the correct
that are internal to the access method were environment. Run the program again.
corrupted. The control blocks are in the application
program protection key, so the application program System programmer response: If the error recurs
might have overlaid them. The address being and the program is not in error, look at the messages in
checked is in register 11. the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
System action: The system abnormally ends the task exists, contact the IBM Support Center. Provide the
and may issue an SVC dump. program listing for the job.
Application Programmer Response: Verify that the Source: Task management
data set was opened and that the control blocks were
handled correctly in the problem program. Run the job
again. 402
If the system wrote a dump, look at field TCBEXCPD at Explanation: During processing of an EVENTS POST
offset X'C0' in the task control block (TCB) for the macro, the system found an error.
current task. The TCBEXCPD points to the EXCP
Register 15 contains a hexadecimal reason code that
debugging area (XDBA). The XDBA contains diagnostic
explains the error:
data associated with the EXCP processor.
Code Explanation
System programmer response: If the error recurs
and the program is not in error, look at the messages in 00 The system found an incorrect EVENTS table
the job log for more information. Search problem address in the low-order bytes of the extended
reporting data bases for a fix for the problem. If no fix format event control block (ECB) that was
exists, contact the IBM Support Center. Provide the specified.
JCL, the program and assembly listings for the job, and
04 The waiting request block (RB) is not enabled
the SVC dump.
for interrupts.
Source: Execute channel program (EXCP)
System action: The system abnormally ends the
program that issued the EVENTS macro.
401
Application Programmer Response: Correct the
Explanation: During processing of a WAIT macro, the error. Run the job again.
system found an error in the caller’s environment.
System programmer response: If the error recurs
Register 15 contains a hexadecimal reason code that and the program is not in error, look at the messages in
explains the error: the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
Code Explanation
exists, contact the IBM Support Center. Provide the
04 The caller does not hold the home address program listing and the assembly listing associated with
space’s local lock. the job.
08 The caller does not have addressability to the Source: Task management
home address space.
0C A disabled caller issued a WAIT macro with the
LINKAGE=SYSTEM option.
206 z/OS V1R10.0 MVS System Codes
406 • 40D
Only subpools defined as eligible for subpool
406
FREEMAIN may be freed as an entire subpool.
Explanation: The error occurred during processing of All other subpool storage areas must be freed
a LINK(X), ATTACH(X), or XCTL(X) macro. by individual requests explicitly describing the
area.
The reason code in register 15 identifies the error:
08 A problem program tried to free subpool zero.
Code Explanation
The control program releases subpool zero
04 The requested program is only loadable. The when a job step ends.
program was produced by linkage editor
System action: The system issues message IEA705I.
processing for which the EXEC statement
The system abnormally ends the current task.
contained OL in the PARM parameter field.
Application Programmer Response: If you intended
08 Attempt to fetch an AMODE 64 module when
the FREEMAIN macro to release subpool zero, remove
not running in z/Architecture mode.
it from the program. If you did not intend the
12 Attempt by a program running AMODE 24 or FREEMAIN macro to release subpool zero, check for
31 using the LINK or LINKX macro to link to an program errors that incorrectly modify the FREEMAIN
AMODE 64 module without having specified macro expansion. After making corrections, run the job
AMODE64OK=YES on the LINKX macro. step again.
System action: The task is ended unless ERRET is Source: Virtual storage manager (VSM)
specified on the macro instruction. For reason code 04,
the system issues message CSV009I. The system
40D
issues an ABEND dump.
Explanation: When the recovery termination manager
Application Programmer Response:
(RTM) was ending a task, recursive errors occurred.
Code Response RTM ends the address space. This abend code is in the
ASCBMCC field in the address space control block
04 Rewrite the problem program so that it (ASCB) for the ended address space and in message
specifies only loading, not processing, of the IEF402I.
only loadable program. Next, recompile and
run the job step again. A hexadecimal reason code in register 15, in message
IEF402I, and in the SVC dump title explains the error:
08 Avoid having the system attempt to fetch an
AMODE 64 module unless running in Code Explanation
z/Architecture mode.
00 At the time of the recursive abends, RTM had
12 Use LINKX and specify AMODE64=OK and established only critical error recursion
make sure that your program provides the processing. Therefore, RTM could determine
interface needed by the AMODE 64 target only that the error was not due to a problem
routine. identified by the other reason codes.
System programmer response: If the error recurs 04 RTM2 detected a critical error in RTM2
and the program is not in error, see the system processing.
programmer response for messages in the job log.
08 RTM experienced another error while
If the problem persists, search problem reporting data processing a recursive error. RTM2 was unable
bases for a fix for the problem. If no fix exists, contact to obtain the RTM2 work area (RTM2WA)
the IBM Support Center. Provide the ABEND dump and associated with the original error.
the source program listing for the job.
0C RTM2 could not obtain the previous RTM2WA
Source: Contents supervision (CSV) because the pointer to it was not valid.
10 No storage was available in either the local
40A system queue area (LSQA) or the extended
local system queue area (ELSQA) for the
Explanation: An error occurred when the system tried RTM2WA.
to process an R form of the FREEMAIN macro. A
reason code in the SDWACRC field of the system 14 RTM2 detected that an RTM request to get or
diagnostic work area (SDWA) explains the error: free virtual storage ended abnormally.
Code Explanation 18 RTM was entered recursively after it had
completed end-of-task processing.
04 The caller tried to FREEMAIN a subpool that
cannot be freed.
Chapter 2. System Completion Codes 207
413 • 417
1C RTM2 was entered recursively. RTM2 could not
413
find the request block (RB) for the previously
abended routine. Explanation: The error occurred during processing of
an OPEN macro instruction for a data set on magnetic
20 RTM2 was entered recursively to process an
tape or on a direct access device. This system
RTM-initiated abend of a daughter task. RTM2
completion code is accompanied by message IEC145I.
could not find the error RB for the previously
Refer to the explanation of message IEC145I for
abended mother task.
complete information about the task that was ended and
24 RTM2 tried to enter an exit, but found no exit for an explanation of the return code (rc in the message
flag on to indicate which exit to take. text) in register 15.
28 RTM2 experienced an unrecoverable recursive Application Programmer Response: Respond as
error while ending a daughter task of the indicated for message IEC145I.
current task.
System programmer response: If the error recurs
30 RTM2 has been recursively entered for multiple and the program is not in error, look at the messages in
DOD abends from a subtask. the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
34 RTM2 encountered a recursive abend due to a exists, contact the IBM Support Center. Provide the JCL
problem with the current Task’s Linkage Stack. and the program listing for the job.
System action: RTM ends the address space. The Source: DFSMSdfp
system issues message IEF402I. The system writes an
SVC dump. Critical problems in the address space can
prevent the SVC dump from completing successfully. 414
Even if successful, message IEA911E or IEA611I might
Explanation: The error occurred during processing of
not be issued to indicate the dump is complete.
a CLOSE macro instruction for a data set on a direct
Operator response: Obtain the SVC dump. The dump access device. This system completion code is
has the title: accompanied by message IEC212I. Refer to the
ABEND=40D,RC=xx,COMPON=RTM2,COMPID=SCRTM, explanation of message IEC212I for complete
ISSUER=IEAVTRT2, MEMTERM - UNRECOVERABLE ABEND FAILURE information about the task that was ended and for an
explanation of the return code (rc in the message text)
Note: Prior to OS/390 the COMPID is SC1CM. in register 15.
System programmer response: Do the following: Application Programmer Response: Respond as
1. Obtain the reason code from message IEF402I, indicated for message IEC212I.
register 15, or the SVC dump title.
System programmer response: If the error recurs
2. For reason code X'10', continue diagnosis with and the program is not in error, look at the messages in
virtual storage manager (VSM) to determine why the job log for more information. Search problem
there is not enough ELSQA available. If the problem reporting data bases for a fix for the problem. If no fix
cannot be determined, search problem reporting exists, contact the IBM Support Center. Provide the JCL
data bases for a fix for the problem. If no fix exists, and the program listing for the job.
contact the component group for VSM at the IBM
Support Center. Provide the problem data collected Source: DFSMSdfp
in previous steps.
3. For a reason code other than X'10', a critical 417
problem occurred while RTM was processing an
Explanation: The error occurred during processing of
abend. Search problem reporting data bases for a
a BSAM CLOSE macro instruction with a TYPE=T
fix for the problem. Include in the search argument:
operand for a data set on a direct access device. This
v Program identifier: PIDS/5752SCRTM
system completion code is accompanied by message
v Abend code: AB/S040D
IEC221I. Refer to the explanation of message IEC221I
v Abend reason code: PRCS/xx
for complete information about the task that was ended
and for an explanation of the return code (rc in the
If no fix exists, contact the IBM Support Center.
message text) in register 15.
Provide the dump and any messages about the
problem. Application Programmer Response: Respond as
indicated for message IEC221I.
Source: Recovery termination manager (RTM)
System programmer response: If the error recurs
and the program is not in error, look at the messages in
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL
208 z/OS V1R10.0 MVS System Codes
422
and the program listing for the job. BPX1EXI (_exit) service being issued
in a process with multiple threads.
Source: DFSMSdfp
The initial pthread_create task (IPT), if
not already exited, is abended with
422 this reason, if the thread calling
BPX1EXI is created by pthread
Explanation: This abend is a general use abend code. create.
It provides an abend that will be treated similarly to a
222 abend generated by a CANCEL. This abend will not xxxx0183 BPXPRMPC was requested to
be delivered to the target task if the task is already in terminate and clean up a process.
recovery processing. This required the Assembler
termination macro CALLRTM of the
This abend may be retryable or nonretryable depending initial pthread task.
on the reason code.
xxxx0184 The task is being ended because it is
The 422 abend reason codes are in the format: in a wait state controlled by the kernel
xxxxyyzz address space, which is being ended.
The parts of the reason code are: To prevent leaving the task in a
never-ending wait, the task is
xxxx The first halfword will be left to the component abended. If a recovery routine exists
to set. Some components use these two bytes in the task, the routine can retry for
for internal identification. this abend.
yy The 3rd byte will contain a component xxxx0185 A system error occurred during thread
identifier. This will allow the 422 abend to be creation. The process was terminated.
shared by multiple products and components.
The following yy values indicate which xxxx0186 A system error occurred during the
component or product generated the abend: processing of a local process exec.
The jobstep is terminated.
01 UNIX System Services
xxxx0187 A system error occurred during fork
02 JES2 processing. Fork is in the APPC
03 BCP console services Receive and Wait window trying to
create the child address space. Fork
04 TCP/IP Reason Codes maybe hung waiting for ASCH
05 JES3 initiators.
zz The last byte is used by the component to xxxx0189 The kernel has, at the request of the
create unique reason codes. user, terminated a thread that was in
a ENQ wait.
UNIX System Services Reason Codes (yy= 01): xxxx018A A system error occurred creating the
child process during fork processing.
Code Explanation
The child process address space is
xxxx01zz Where zz is between the values of terminated.
X'01' and X'7F' and represents the
xxxx018B A system error occurred during
signal that caused the task to end. An
server_init processing for a server
error occurred in an application
manager address space. The calling
program that uses z/OS UNIX System
task is terminated.
Services.
xxxx01A0 This abend is the result of the kernel
xxxx0109 The ending address space is the
terminating a thread. The thread and
target of a signal. A signal is
its associated task are terminated.
program-generated and causes the
job step task in the target user xxxx01A2 This retryable abend will drive the
process to be ended with an abend BPXOINIT process to clean up a
that cannot be retried. suspected growth of zombie
processes. This growth of zombies
xxxx0181 This abend is the result of the
could have been due to a cross
BPX1EXC (exec) or BPX1EXM
memory post failure that prevented
(execMVS) service being issued in a
BPXOINIT from waking up sooner to
process with multiple threads. All
clean up the zombies.
dubbed threads in the process are
terminated with the abend. xxxx01A3 This abend is the result of a request
to shutdown z/OS UNIX System
xxxx0182 This abend is the result of the
Chapter 2. System Completion Codes 209
422
Services. The thread and its terminated when the owner of the
associated task are terminated. mutex or condition variable
terminated.
xxxx01A4 The current owner of a mutex (mutual
exclusion lock) or condition variable xxxx01A5 Determine why the owner of the z/OS
abended thereby making unusable the UNIX System Services latch was
mutex or condition variable held at holding it for an excessive period of
that time. The system terminates the time. Correct the problem and
thread and any task(s) waiting for the resubmit the affected job(s) or restart
mutex or condition. the affected task(s).
xxxx01A5 The sytem has terminated a user task
Rerun the job and use a debugger if necessary to
that has held a z/OS UNIX System
determine why the signal has occurred.
Services latch for an excessively long
time.
Source: z/OS UNIX System Services (BPX)
System action: The unit of work is ended with a
nonretryable error. JES2 Reason Codes (yy = 02):
Application Programmer Response: Code Explanation
Code Response xxxx0200 xxxx is the identifier of the JES2
xxxx01zz The unit of work has terminated for a processor control element (PCEID)
signal that was either sent by the user currently active. A value of X'02' in the
or generated by the system. 3rd byte indicates the JES2
Determining the reason for the signal component. When xxxx=0003, this
generally requires an understanding of abend is the result of a job/TSU/STC
when signals are generated by the being canceled via an $C job or $C
system. For a list of signals, refer to job,D command while it is awaiting
z/OS UNIX System Services conversion or active in conversion.
Programming: Assembler Callable xxxx0204 The address space was terminated
Services Reference. (through CALLRTM TYPE=ABTERM)
xxxx0181 No action is required by the user. during job select processing by a
JES2 $C operator command. A dump
xxxx0182 No action is required by the user. was produced if the DUMP operand
was included on the $C command.
xxxx0183 No action is required by the user.
xxxx0208 The address space was terminated
xxxx0184 The task was in a wait at the time the
(through CALLRTM
kernel terminated. This is not an error.
TYPE=MEMTERM) as the result of a
xxxx0185 Retry the operation. If the error JES2 $C command with the FORCE
persists, report the error to the IBM operand.
Support Center.
00030200 Determine why the job is being
xxxx0186 No action is required by the user. canceled. If you require a dump, have
the operator resubmit the job, and
xxxx0187 Review the APPC/ASCH setup
then cancel it with the DUMP
relating to OMVS.
operand.
xxxx0189 No action is required by the user.
Source: JES2
xxxx018A No action is required by the user.
System action: The job/TSU/STC is ended with a
xxxx018B No action is required by the user. nonretryable error.
xxxx01A0 No action is required by the user. Console Component Reason Codes (yy=03):
xxxx01A2 No action is required by the user. This Code Explanation
is part of automated clean-up of
00010301 A command was cancelled at the
zombie storage that is no longer
operator’s request through the CMDS
needed.
ABEND command.
xxxx01A3 No action is required by the user.
Source: Console services
xxxx01A4 Resubmit those jobs that were
TCP/IP Reason Codes (yy=04):
See TCP/IP abend 422 reason codes in z/OS
210 z/OS V1R10.0 MVS System Codes
425 • 430
Communications Server: IP and SNA Codes.
42D
JES3 Reason Codes (yy=05):
Explanation: While an overlay program was running,
Code Explanation an error occurred in the processing of a SEGLD macro.
00000501 The job was cancelled during job
Note: Overlay programs run only in 24-bit addressing
initiation. No dump was requested.
mode, not in 31-bit addressing mode.
00000502 The job was cancelled with dump
System action: The system abnormally ends the
during job initiation.
program that requested the overlay. The system writes
00000503 The job was forced by using the an ABEND dump, if a dump DD statement is provided.
*MODIFY J=nn,FORCE command.
Application Programmer Response: Obtain the
address in register 12 at the time of the error. Add X'14'
425 to the address to find the address of the event
completion block (ECB) that contains the subtask
Explanation: A program requested an overlay. When completion code.
trying to answer the request, the overlay supervisor
found that the target segment for the request could be Look for errors in the program. Correct the errors; then
resolved but was not valid for an overlay. assemble, link edit, and run the program again.
System action: The system abnormally ends the Source: Overlay supervisor
program that requested the overlay. The system writes
an ABEND dump, if a dump DD statement is provided.
430
Application Programmer Response: Check the
Explanation: The error occurred during processing of
program for errors in selecting the segment to overlay.
a DEQ macro instruction during the processing of global
Correct the errors; then assemble, link edit, and run the
resource serialization.
program again.
The control program found that the parameter list
Source: Overlay supervisor
created from the macro instruction was incorrect.
Register 15 might contain a reason code associated
42A
with this error:
Explanation: During processing of an ATTACH macro,
Code Explanation
the system found that the ECB parameter specified an
incorrect address for the event control block (ECB) to xxxx0001 The input parameter list was altered
be posted when the subtask abnormally ends. during DEQ processing.
The address was incorrect for the following reasons: xxxx0002 The DEQ request specified UCB and
v It was not on a fullword boundary. RNL=NO.
v The addressed virtual storage is not allocated, or its xxxx0003 The storage specified by the input
protection key does not match the protection key of UCB address does not map to a valid
the issuer of the ATTACH. UCB.
System action: The system abnormally ends the xxxx0004 The storage specified by the UCB
program that issued the ATTACH macro. address specified by an ISGNQXIT
exit routine does not map to a valid
Application Programmer Response: Change the
UCB.
ATTACH macro to specify the correct ECB address and
ensure that the specification was not incorrectly xxxx0005 The storage passed to DEQ
modified by the problem program. Correct the error. Run processing could not be accessed in
the job again. the caller’s key.
System programmer response: If the error recurs xxxx0006 The storage containing the QNAME
and the program is not in error, look at the messages in could not be accessed in the caller’s
the job log for more information. Search problem key.
reporting data bases for a fix for the problem. If no fix
xxxx0007 The storage containing the RNAME
exists, contact the IBM Support Center. Provide the
could not be accessed in the caller’s
program listing for the job.
key.
Source: Task management
xxxx0008 The storage containing the pointer to
the UCB address could not be
accessed in the caller’s key.
Chapter 2. System Completion Codes 211
433 • 437
xxxx0009 The storage containing the UCB
433
address could not be accessed in the
caller’s key. Explanation: An error occurred while DAE was
processing a symptom record.
xxxx000A The number of local resources
specified in a DEQ list request has Register 15 contains a hexadecimal reason code that
exceeded the maximum value of explains the error:
X'FFFF' resources.
Code Explanation
xxxx000B The number of global resources
00000008 There is no more storage available for
specified in a DEQ list request has
keeping DAE symptom strings in
exceeded the maximum value of
storage, and the existing storage
X'FFFF' resources.
cannot be reused.
xxxx000D The storage specified by the input
System action: The system writes a logrec data set
TCB was invalid.
error record, and attempts to take an SVC dump. DAE
xxxx000E The storage specified by the input stops processing and issues message ADY015I.
TCB does not map to a valid TCB.
System programmer response: For reason code
xxxx0014 Request attempted to set an obsolete X'00000008', DAE processing may be restarted using
bit in the input parameter list. the MVS SET DAE command.
xxxx0015 Request illegally specified TCB with Source: Dump Analysis and Elimination (DAE)
RMC.
xxxx0016 The DEQ request illegally specified 435
MASID.
Explanation: SVC 53, which obtains and releases
xxxx0017 Request specified invalid RET= value. exclusive control of a resource associated with a BDAM
data set found that:
xxxx0018 Generic request specified invalid
RET= value or RMC. v The DEB pointed to by the input DCB (DCBDEBAD)
was not on any DEB chain associated with the job
xxxx0022 The storage containing the PEL Prefix step TCB, or did not point back to that DCB, or was
could not be accessed in the caller’s not for a BDAM data set.
key.
v The IOB has been altered by other than a system
xxxx0023 The RMC=STEP was specified when routine.
PASN was not equal to HASN.
Application Programmer Response: Make sure that
the input DCB address is correct and that the
The reason code could also be associated with an DCBDEBAD field of the input DCB has not been
ISGENQ Request=Release. See the reason codes overlaid.
listed for the ISGENQ macro in z/OS MVS
Programming: Authorized Assembler Services System programmer response: If the error recurs
Reference EDT-IXG. and the program is not in error, search problem
reporting data bases for a fix for the problem. If no fix
System action: The system writes an ABEND dump. exists, contact the IBM Support Center.
Application Programmer Response: Correct the Source: DFSMSdfp
macro instruction. Recompile and run the job step
again.
437
System programmer response: Do the following:
v For reason code X'0004', check your ISGNQXIT Explanation: The error occurred at an end-of-volume.
installation exits to ensure that they are coded to This system completion code is accompanied by
specify a valid UCB address. message IEC025I. Refer to the explanation of message
IEC025I for complete information about the task that
v For reason code X'000A/000B', make sure that no was ended and for an explanation of the return code (rc
single request is greater than the limit when you in the message text) in register 15.
issue multiple DEQ LIST requests.
Application Programmer Response: Respond as
If the problem persists, search problem reporting data indicated for message IEC025I.
bases for a fix for the problem. If no fix exists, contact System programmer response: If the error recurs
the IBM Support Center. Provide the ABEND dump. and the program is not in error, look at the messages in
Source: Global resource serialization the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
212 z/OS V1R10.0 MVS System Codes
438
exists, contact the IBM Support Center. Provide the JCL xxxx000F A MASID request incorrectly specified
and the program listing for the job. TCB or SMC.
Source: DFSMSdfp xxxx0010 A MASID request has an rname with
an invalid length.
438 xxxx0011 A MASID request specified invalid
RET= value.
Explanation: An error occurred processing an ENQ
macro instruction during processing of global resource xxxx0012 A MASID request has no TCB
serialization. associated with it.
The control program found that the parameter list xxxx0013 Issuing tasks TCB is a subtask of the
created from the macro instruction was incorrect. target TCB, illegal.
Register 15 might contain a reason code associated xxxx0014 Request attempted to set an obsolete
with this error: bit in the input parameter list.
Code Explanation xxxx0015 Request illegally specified TCB with
SMC.
xxxx0001 The input parameter list was altered
during ENQ processing. xxxx0017 Request specified invalid RET= value.
xxxx0002 The RESERVE request specified UCB xxxx0019 The ENQ request illegally attempted a
and RNL=NO. generic request.
xxxx0003 The storage specified by the input xxxx001A A directed ENQ request was issued
UCB address does not map to a valid with no matching TCB in the
UCB. requester’s address space.
xxxx0004 The storage specified by the UCB xxxx001B Directed ENQ request illegally
address specified by an ISGNQXIT specified UCB.
exit routine does not map to a valid
xxxx001C Directed ENQ request illegally
UCB.
specified no ECB with an invalid
xxxx0005 The storage passed to ENQ RET= value.
processing could not be accessed in
xxxx001D An ECB request but RET does not
the caller’s key.
specify ECB.
xxxx0006 The storage containing the QNAME
xxxx001E An ECB request illegally specified
could not be accessed in the caller’s
SMC.
key.
xxxx001F The storage containing the format
xxxx0007 The storage containing the RNAME
word could not be accessed in the
could not be accessed in the caller’s
caller’s key.
key.
xxxx0020 The storage containing the format
xxxx0008 The storage containing the pointer to
value could not be accessed in the
the UCB address could not be
caller’s key.
accessed in the caller’s key.
xxxx0022 The storage containing the PEL Prefix
xxxx0009 The storage containing the UCB
could not be accessed in the caller’s
address could not be accessed in the
key.
caller’s key.
xxxx0023 The RMC=STEP was specified when
xxxx000A The local resource count for this
PASN was not equal to HASN.
request exceeded X'FFFF' resources.
| xxxx0822 Unable to access the Userdata
xxxx000B The global resource count for this
| specified on the request.
request exceeded X'FFFF' resources.
xxxx000C The format word value specified in the
| xxxx0823 The ALET for the Userdata is bad.
input parameter list prefix was
incorrect. The reason code could also be associated with an
ISGENQ Request=Obtain or Request=Change. See the
xxxx000D The storage specified by the input reason codes listed for the ISGENQ macro in z/OS
TCB was invalid. MVS Programming: Authorized Assembler Services
Reference EDT-IXG.
xxxx000E The storage specified by the input
TCB does not map to a valid TCB. System action: The system issues an ABEND dump.
Chapter 2. System Completion Codes 213
43E • 451
Application Programmer Response: Correct the System action: The system produces a dump, and
macro instruction. Recompile and run the job step retries to the address in register 14.
again.
Application Programmer Response: Respond as
If the problem persists, do the following: indicated in the accompanying message.
1. Obtain the address of the ENQ parameter list from Source: DFSMSdfp
register 1 in the UNIQUE-3 column of the SVC 38
entry in the system trace.
444
2. Check the parameter list against the SVC 38
mapping. When analyzing the parameter list, Explanation: The error occurred during the processing
remember that the unit control block (UCB) pointer, of SYNADAF, where it was determined that the DECB
if present, is the address of a field that, in turn, address was incorrect.
contains the address of the UCB.
Application Programmer Response: Register 15
If the parameter list contains incorrect data, continue contains the DECB address in error:
diagnosis in the program that issued the macro.
v For BDAM, BPAM, and BSAM, the DECB address
System programmer response: If the reason code is should be passed to SYNADAF as the PARM2
X'0004', check your ISGNQXIT installation exits to operand on the macro instruction. For these access
ensure that they are coded to specify a valid UCB methods, the DECB address was in register 0 on
address. Otherwise, if the problem persists, search entry to the user’s SYNAD routine.
problem reporting data bases for a fix for the problem. If v For BISAM, the IOBECBPT field of the IOB in error
no fix exists, contact the IBM Support Center. Provide should contain the DECB address. Make sure that
the ABEND dump. the PARM2 operand on the SYNADAF macro
Source: Global resource serialization instruction (the address of the first sense byte within
the IOB) is correctly specified, and that the
IOBECBPT has not been overlaid.
43E
Explanation: The event control block (ECB) address Correct the error and rerun the job step.
specified with the ECB parameter on the ATTACH System programmer response: If the error recurs
macro instruction that created a task was not valid when and the program is not in error, look at the messages in
the subtask abnormally ended. the job log for more information. Search problem
System action: The ECB is not posted. The system reporting data bases for a fix for the problem. If no fix
abnormally ends the originating task of the caller. exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
Application Programmer Response: Determine if the
area containing the ECB was freed before the subtask Source: DFSMSdfp
completed processing. Correct the error. Run the job
again. 451
The ECB was specified in the ATTACH macro, and the Explanation: The error occurred during the processing
system checked it for validity while attaching the of SETPRT. Either the DCB whose address was passed
subtask. The ECB could be incorrect when the subtask in the SETPRT parameter list is incorrect, the DEB
is detached or at end of task through a request of the address located through the DCB was incorrect, the
storage containing the ECB. DCB EXIT LIST address located through the DEB was
System programmer response: If the error recurs incorrect, or the IOBs located through the DCB are
and the program is not in error, look at the messages in incorrect.
the job log for more information. Search problem This system completion code is accompanied by
reporting data bases for a fix for the problem. If no fix message IEC918I. Refer to the explanation of message
exists, contact the IBM Support Center. Provide the IEC918I for complete information about the task that
source program listing and the assembly listing was ended and for an explanation of the return code in
associated with the job. register 15.
Source: Task management Application Programmer Response:
v For return code 01, make sure that DCBEXLIST
43F points to a valid exit list in your region.
Explanation: An error has been detected during v For return code 02, make sure that the DCB fields
checkpoint restart processing. This completion code is DCBIOBAD and DCBIOBA have not been overlaid
accompanied by message IHJxxxI with the appropriate since the DCB was opened. Make sure that the IOB
reason code. or ICB link fields have not been overlaid.
214 z/OS V1R10.0 MVS System Codes
453 • 46D
v For return code 03, make sure that the DCB field 04 The ESPIE macro specified an option other
DCBDEBAD has not been overlaid since the DCB than SET, RESET, or TEST.
was opened.
08 The ESPIE SET or ESPIE TEST macro passed
v For return code 04, make sure that the SETPRT an address pointing to a parameter list. The
macro instruction correctly specifies the address of contents of the parameter list is not valid for
an open DCB within your region. one of the following reasons:
System programmer response: If the error recurs v The parameter list is not aligned on a
and the program is not in error, look at the messages in fullword boundary.
the job log for more information. Search problem v The parameter list is in storage that was not
reporting data bases for a fix for the problem. If no fix obtained by a GETMAIN macro.
exists, contact the IBM Support Center. Provide the JCL
v The parameter list is in storage that is
and the program listing for the job.
protected from the issuer of the ESPIE
Source: DFSMSdfp macro.
0C The ESPIE SET macro passed a parameter list
453 containing an exit routine address that is not
valid for one of the following reasons:
Explanation: A buffer queue error occurred while
system management facility (SMF) recording was v The high or low order bits of the address are
writing to the SMF data sets; the system determined not 0.
that SMF recording should be ended. v If the program issuing ESPIE is in 24-bit
addressing mode, the high order byte is not
System action: The system ends the SMF address
zero.
space and releases the resources used by SMF.
10 The ESPIE RESET macro attempted to delete
Operator response: Notify the system programmer. If
a SPIE or ESPIE that was created by some
SMF recording is essential for the system, restart the
other program.
SMF address space using the SET SMF command as
soon as the problem is corrected. 14 The ESPIE RESET macro passed an incorrect
TOKEN parameter. TOKEN is incorrect for one
System programmer response: Check error
of these reasons:
messages and the SVC dump produced as a result of
any previous abends. v The TOKEN itself is not valid.
v The exit that the TOKEN represents has
Source: System Management Facilities (SMF)
been deleted.
18 The program issuing an ESPIE macro is in a
45F
mode that is not valid for one of the following
Explanation: A SYSEVENT QUIESCE macro failed reasons:
while a SYSEVENT TRANSWAP or REQSWAP was v The program is in supervisor state.
pending. A retry was not possible.
v The program that issued the ESPIE macro
System action: The system abnormally ends the had a program status word (PSW) storage
address space being swapped. The system writes key that did not match the task control block
messages and a logrec data set error record. (TCB) key.
System programmer response: This is probably a 1C The ESPIE macro passed a pointer to a SPIE
system error. Resubmit the job. If the problem recurs, program interruption exit (PIE) control block.
search problem reporting data bases for a fix for the The PIE control block is not valid. The PIE
problem. If no fix exists, contact the IBM Support control block had probably been erroneously
Center. Provide the logrec data set error record and the freed by a FREEMAIN macro.
SYSOUT output for the job.
20 An unauthorized program issued a ESPIE
Source: System resources manager (SRM) macro to establish an ESPIE exit for page
faults.
46D System action: The system abnormally ends the task.
The system sends messages about the problem to the
Explanation: A program issued the ESPIE macro job log.
incorrectly:
Operator response: If the system programmer asks
A hexadecimal reason code in register 15 explains the for an SVC dump, set the following SLIP trap:
error:
SLIP SET,COMP=46D,ACTION=SVCD,END
Code Explanation
System programmer response: Search problem
Chapter 2. System Completion Codes 215
478 • 47D
reporting data bases for a fix for the problem. If no fix program listing and the assembly listing associated with
exists, contact the IBM Support Center. Provide: the job.
v Messages from the job log
Source: Task management
v The ABEND or SVC dump
v The assembly listing for the job
v The JCL for the job 47B
v The program listing for the job
Explanation: An error occurred during PURGEDQ
Source: Recovery termination manager (RTM) processing. The SDWACRC field of the system
diagnostic work area (SDWA) contains a hexadecimal
reason code that explains the error.
478
Code Explanation
Explanation: An error occurred when the system tried
to process an RC or RU form of the FREEMAIN macro 00 During processing of a PURGEDQ macro for
or the STORAGE RELEASE macro. A reason code in the current primary address space, the system
the SDWACRC field of the system diagnostic work area found a suspended SRB meeting the purge
(SDWA) explains the error: parameters. The system abended the SRB
routine to ensure that all SRB routines affected
Code Explanation
by PURGEDQ had run to completion.
04 The caller tried to FREEMAIN or STORAGE
04 An internal error occurred during PURGEDQ
RELEASE a subpool that cannot be freed.
processing. Contact the IBM Support Center.
Only subpools defined as eligible for subpool
08 During processing of a PURGEDQ macro for
FREEMAIN or STORAGE RELEASE may be
the current primary address space, the system
freed as an entire subpool. All other subpool
found a preemptable SRB meeting the purge
storage areas must be freed by individual
parameters. The system abended the SRB
requests explicitly describing the area.
routine to ensure that all SRB routines affected
08 A problem program tried to free subpool zero. by PURGEDQ had run to completion.
The control program releases subpool zero
System action: The system abnormally ends the SRB
when a job step ends.
routine.
System action: The system issues message IEA705I.
Application Programmer Response: If CANCEL
The system abnormally ends the current task.
command processing caused the error, resubmit the job.
Application Programmer Response: If you intended If a task-to-SRB routine serialization or abnormal TCB
the FREEMAIN or STORAGE RELEASE macro to ending caused the problem, modify the application to
release subpool zero, remove it from the program. If avoid the problem.
you did not intend the FREEMAIN or STORAGE
System programmer response: If the error recurs
RELEASE macro to release subpool zero, check for
and the program is not in error, look at the messages in
program errors that incorrectly modify the FREEMAIN or
the job log for more information. Search problem
STORAGE RELEASE macro expansion. After making
reporting data bases for a fix for the problem. If no fix
corrections, run the job step again.
exists, contact the IBM Support Center. Provide the
Source: Virtual storage manager (VSM) program listing and the assembly listing associated with
the job.
47A Source: Task management
Explanation: During processing of an EVENTS macro,
the system found an incorrect number of entries 47D
specified on the on the ENTRIES parameter. The
Explanation: During processing of an EVENTS macro,
number of entries must be 1 through 32,767.
the system found that the address specified on the
System action: The system abnormally ends the LAST parameter was incorrect.
caller of the EVENTS macro.
LAST must specify an address between the first and
Application Programmer Response: Ensure that the last valid entries in the EVENTS table.
number of entries specified on the ENTRIES parameter
System action: The system abnormally ends the
is 1 through 32,767.
program that issued the EVENTS macro.
System programmer response: If the error recurs
Application Programmer Response: Ensure that the
and the program is not in error, look at the messages in
LAST address is a valid table entry that has not been
the job log for more information. Search problem
previously purged from the EVENTS table. Correct the
reporting data bases for a fix for the problem. If no fix
error. Run the job again.
exists, contact the IBM Support Center. Provide the
216 z/OS V1R10.0 MVS System Codes
482 • 4C7
System programmer response: If the error recurs for this abend, use IPCS to format the dump. For an
and the program is not in error, look at the messages in explanation of the dump title, see the dump title
the job log for more information. Search problem beginning ICHRST00-RACF SVCS in z/OS Security
reporting data bases for a fix for the problem. If no fix Server RACF Diagnosis Guide.
exists, contact the IBM Support Center. Provide the
program listing and the assembly listing associated with
4C5
the job.
Explanation: This abend is issued by the TCP/IP
Source: Task management
product. For more information, see TCP/IP abend 4C5
reason codes in z/OS Communications Server: IP and
482 SNA Codes.
Explanation: While RACF was processing a
RACHECK request, the RACF manager returned a 4C6
return code that was not valid.
Explanation: An error occurred during Resource
System action: The system ends the task. Access Control Facility (RACF) processing for z/OS
UNIX System Services.
System programmer response: Register 15 contains
the hexadecimal return code from the RACF manager.. Code Explanation
Message ICH409I, if issued, contains the reason code
00000004 A service call to a RACF module did
from the RACF manager. For an explanation of RACF
not complete. No accessor
manager return and reason codes, see z/OS Security
environment element (ACEE) was
Server RACF Messages and Codes.
available to describe the user.
Using IPCS, format the dump taken for this abend. For
00000008 A service call to a RACF module did
an explanation of the dump title, see z/OS Security
not complete. No accessor
Server RACF Diagnosis Guide.
environment element extension
Source: Resource Access Control Facility (RACF) (ACEX) was available to describe the
user.
483 0000000C A service call to a RACF module did
not complete. No user security packet
Explanation: While RACF was processing a RACINIT
(USP) was available to describe the
request, the RACF manager returned an invalid return
user.
code.
System action: The system abnormally ends the task.
System action: The system terminates the task.
Application Programmer Response: The RACF
Application Programmer Response: Register 15
input/output parameter list IRRPCOMP contains a SAF
contains the return code from the RACF manager.
return code, RACF return code, and RACF reason code
Message ICH409I, if issued, contains the RACF
that describes an internal RACF error.
manager reason code. For an explanation of RACF
manager return and reason codes, see z/OS Security System programmer response: Run the job again, or
Server RACF Messages and Codes. have the user log on again while RACF is active. If the
abend occurs again, see z/OS Security Server RACF
System programmer response: If a dump was taken
Diagnosis Guide for information on diagnosing abends
for this abend, use IPCS to format the dump. For an
and reporting abend problems to IBM.
explanation of the dump title, see the dump title
beginning ICHRST00-RACF SVCS in z/OS Security Source: Resource Access Control Facility (RACF)
Server RACF Diagnosis Guide.
4C7
485
Explanation: While RACF was processing a non-SVC
Explanation: While RACF was processing a request, an error occurred in the RACF storage
RACROUTE REQUEST=DEFINE request, the RACF manager.
manager returned an invalid return code.
System action: The system terminates the task.
System action: The system terminates the task.
Application Programmer Response: Register 15
Application Programmer Response: Register 15 contains a hexadecimal reason code. (Message
contains the return code from the RACF manager. See ICH409I, if issued, also contains this reason code.)
z/OS Security Server RACF Messages and Codes for
Code Meaning
an explanation for RACF-manager return codes.
System programmer response: If a dump was taken
Chapter 2. System Completion Codes 217
4FB • 4FC
04 BAD LENGTH: The length of the area to get or Code Explanation
free is not greater than zero.
04 An error occurred during PUT processing.
08 BAD ALIGNMENT: The pointer to the area to
08 No storage was available for an SSISERV
free is not on a doubleword boundary.
request.
0C DUPLICATE FREEMAIN: The area to free has
0C No storage was available for excession limits
already been freed.
processing.
10 INCORRECT SUBPOOL: The subpool for the
10 An SJF error occurred during excession limits
area to free is not the subpool in which the
processing.
area is allocated.
14 Failure occurred while releasing storage for a
14 INVALID OVERLAP: Part of the area to free
JMU.
equals part of the area allocated, but the match
is not correct for either a full or partial 18 Failure occurred while releasing MEMJMULK in
FREEMAIN. the Rel_JMULOCK routine.
18 NOT FOUND: The area to free does not have 1C Failure occurred while releasing MEMJMULK in
a corresponding GETMAIN entry in the tracking the Cleanup_Retry routine.
table, and the caller did not specify that it
should not have. 20 Failure occurred while releasing MEMJMULK in
the IRB routine.
1C FOUND: The area to free has a corresponding
GETMAIN entry in the tracking table, and the 24 Failure occurred while releasing MEMJMULK in
caller specified that it should not have. the Check_Dump_Needed routine.
20 NOT FREED: There is a temporary area still 28 An error was detected while validity checking
allocated at the end of processing. the RRE and before the DSS could be
validated.
A0 A RACF module issued a get space request.
However, register 1 is not equal to zero and If no reason code is given, the job calling the SSI was
does not point to a buffer previously created by failed by a CALLRTM from JES3.
the program.
System action: The system ends the user address
A4 A RACF module issued a get space request. space.
However, the subpool in register 0 is not the
subpool in which the previously created buffer System programmer response: Rerun the job with a
is allocated. SYSABEND DD statement. The problem may not recur.
If it does, notify the IBM Support Center.
A8 A RACF module issued a free space request.
However, register 1 is equal to zero. Source: JES3
AC A RACF module issued a free space request.
However, register 1 does not point to the buffer 4FC
previously created by the program. Explanation: The system detected an error in the
System programmer response: Using IPCS, format processing following a program check interrupt. In an
the dump taken for this abend. For an explanation of attempt to recover, supervisor control abnormally ended
the dump title, see z/OS Security Server RACF the task that experienced the program check.
Diagnosis Guide. Look at the messages in the job log System action: The system abnormally ends the
for the name of the module calling RACF. For modules program that experienced the program check. The
supplied by IBM, search problem reporting databases system writes a logrec data set error record.
for a fix for the problem. If no fix exists, contact the IBM
support center. Operator response: If the system programmer asks
for an SVC dump, set the following SLIP trap:
Source: Resource Access Control Facility (RACF)
SLIP SET,COMP=4FC,ACTION=SVCD,END
Application Programmer Response: Resubmit the
4FB
job. If the problem recurs, contact the system
Explanation: During JES3 processing, module programmer.
IATDMDK, IATSIAD, IATSIWO, or IATSSJM detected an
System programmer response: Do the following:
error related to the subsystem interface and issued this
system completion code. In some cases the error is v Find the original abend causing the problem in the
further identified by one of the following hexadecimal system diagnostic work area (SDWA) in the logrec
reason codes: data set error record.
218 z/OS V1R10.0 MVS System Codes
500 • 505
v Search problem reporting data bases for a fix for the
502
problem. If no fix exists, ask the operator to set a
SLIP trap to obtain an SVC dump. Contact the IBM Explanation: During processing of a POST macro, the
Support Center. Provide the SVC dump and the system found that the EVENTS table specified in the
logrec data set error record. event control block (ECB) had no entries available for
the posted ECB address.
Source: Supervisor control
System action: The system abnormally ends the
program that issued the POST macro.
500
Application Programmer Response: Ensure that the
Explanation: During processing of an I/O request,
EVENTS table is large enough to contain entries for all
execute channel program (EXCP) processing
ECBs that can be posted to it. Correct the error. Run
encountered an error while validating a control block.
the job again.
Each X'500' abend code has a reason code that
explains the error: System programmer response: If the error recurs
and the program is not in error, look at the messages in
Code Explanation
the job log for more information. Search problem
1 The IOBM field of an Indexed Sequential reporting databases for a fix for the problem. If no fix
Access Method (ISAM) input/output block (IOB) exists, contact the IBM Support Center. Provide the
specified an extent of zero. program listing and the assembly listing associated with
the job.
2 A data extent block (DEB) points to a unit
control block (UCB) that is not valid. The third Source: Task management
byte of the UCB did not contain X'FF', as
required.
504
3 The IOBEID field of the Input/output block
Explanation: An error occurred when the system tried
extension (IOBE) control block does not
to process an EC, EU, LC, LU, VC, or VU form of the
contain the characters ‘IOBE’, which is
GETMAIN macro. A reason code in the SDWACRC field
required.
of the system diagnostic work area (SDWA) explains
4 The version field of the IOBE is not compatible the error:
with the IOBEVRSC version label. The version
Code Explanation
field must equal the IOBEVRSC version label.
04 Of the following, at least one overlapped the
5 The IEDBID field of the I/O error data block
other: length list, address list, or parameter list.
(IEDB) control block does not contain the
For example, the length list overlapped the
characters ‘IEDB’, which is required.
address list.
6 The version field of the IEDB is not compatible
System action: The system issues message IEA705I.
with the IEDBVRSC version label. The version
The system abnormally ends the current task.
field must equal the IEDBVRSC version label.
Application Programmer Response: Check for
System action: The system abnormally ends the
program errors that incorrectly modify the macro
current task and issues a SNAP dump.
expansion. Correct them. Run the job step again.
Application Programmer Response: Correct the
Source: Virtual storage manager (VSM)
problem that the reason code indicates. Ensure also
that the problem program correctly built or modified the
control blocks. If the program is correct, the problem is 505
a system problem. Run the job again, requesting an
Explanation: An error occurred when the system tried
ABEND dump. Notify the system programmer.
to process an EC, EU, LC, LU, VC, or VU form of the
System programmer response: In the dump, look at FREEMAIN macro. A reason code in the SDWACRC
field TCBEXCPD at offset X'C0' in the task control block field of the system diagnostic work area (SDWA)
(TCB) for the current task. TCBEXCPD points to the explains the error:
EXCP debugging area (XDBA). The XDBA contains
Code Explanation
diagnostic data associated with the EXCP processor.
04 Of the following, at least one overlapped the
If the error recurs and the program is not in error, look
other: length list, address list, or parameter list.
at the messages in the job log for more information.
For example, the length list overlapped the
Search problem reporting databases for a fix for the
address list.
problem. If no fix exists, contact the IBM Support
Center. Provide the JCL and the SNAP dump. System action: The system issues message IEA705I.
The system abnormally ends the current task.
Source: Execute channel program (EXCP)
Chapter 2. System Completion Codes 219
506 • 522
Application Programmer Response: Check for 08 CLOSE
program errors that incorrectly modify the macro
0C CLOSE-T
expansion. Correct them. Run the job step again.
10 EOV
Source: Virtual storage manager (VSM)
14 FEOV
506 18 EOV
Explanation: The error occurred during processing of 1C OPEN or CLOSE
a LINK(X), LOAD, ATTACH(X), or XCTL(X) macro in an
overlay program. 20 OPEN or CLOSE
System action: The task is ended.
Note: An overlay program can run only in 24-bit
addressing mode, not in 31-bit addressing mode. Application Programmer Response: Correct the
program so that it releases control of the TIOT resource
before one of the above functions is requested.
If the requested program had been loaded, not enough
Recompile the program and run the job step again.
virtual storage would have remained for the overlay
supervisor. Source: DFSMSdfp
System action: The system issues an ABEND dump.
The task ends abnormally. 513
Application Programmer Response: Reduce the size Explanation: The error occurred during processing of
of the entire program or of the overlay segment. If this an OPEN macro instruction for a data set on magnetic
is not possible, change the program from an overlay tape. This system completion code is accompanied by
program to a dynamically loaded program. Then message IEC146I. Refer to the explanation of message
recompile and run the job step again. IEC146I for complete information about the task that
was ended and for an explanation of the return code (rc
System programmer response: Have the operator
in the message text) in register 15.
enter a START GTF command specifying tape output,
MODE=EXT and TIME=YES. Have the operator reply Application Programmer Response: Respond as
TRACE=SYS in response to message AHL100A. indicated for message IEC146I.
Format the output with the IPCS GTFDATA System programmer response: If the error recurs
subcommand. and the program is not in error, look at the messages in
the job log for more information. Search problem
Problem determination: If the error recurs and the
reporting databases for a fix for the problem. If no fix
program is not in error, see the system program
exists, contact the IBM Support Center. Provide the JCL
response for the messages in the job log.
and the program listing for the job.
If the problem persists, search problem reporting
Source: DFSMSdfp
databases for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the ABEND
dump and the source program listing for the job. 522
Source: Contents supervision (CSV) Explanation: All of the tasks in a job step were in an
SVC wait state for the time specified in the JWT
parameter in the SMFPRMxx parmlib member.
50D
The event control block (ECB) specified in the wait
Explanation: Either the program:
request was never posted. This could be the result of
v Tried to use the OPEN, OPEN-J, CLOSE, CLOSE-T,
waiting on the wrong ECB or not posting the correct
EOV, or FEOV function while holding exclusive
ECB.
control of the TIOT (task input/output table) resource;
or System programmer response: Correct any errors
v Issued the OPEN, OPEN-J, CLOSE, or CLOSE-T and execute the job step again. If no errors are found
macro with inconsistent mode specifications between and the wait is expected for that particular job step,
the LIST and the EXECUTE forms of the macro. specify TIME=NOLIMIT in the EXEC statement to
bypass all job step timing.
Register 15 contains a code that identifies the function
Source: System Management Facilities (SMF)
that issued the abend:
Code Function
00 OPEN
04 OPEN-J
220 z/OS V1R10.0 MVS System Codes
52A • 538
52A 530
Explanation: During processing of an ATTACH macro, Explanation: Global resource serialization
the system found an error in the subtask ABEND encountered an error during processing of a DEQ
intercept (STAI) or the extended STAI (ESTAI) routine. macro instruction.
Register 15 contains a hexadecimal reason code that The DEQ macro instruction was issued in an
explains the error: asynchronous exit routine for a resource. That resource
was previously enqueued by another routine in the
Code Explanation
same task. However, the task had not yet received
00 There is not enough storage available to create control of the resource.
a new ESTAI specify task asynchronous exit
System action: The system issues an ABEND dump.
(STAE) control block (SCB) or to copy existing
STAI or ESTAI SCBs to the new task. Application Programmer Response: Correct the
program so that the DEQ macro instruction is issued
04 The issuer of ATTACH is processing with
only after the task has control of the resource. If
AMODE 31 and requested STAI. STAI is not
possible, avoid issuing the DEQ macro instruction in the
supported for AMODE 31 callers.
exit routine. Recompile and run the job step again.
System action: The system abnormally ends the
System programmer response: If the problem
program that issued the ATTACH macro.
persists, search problem reporting databases for a fix
Application Programmer Response: Reason code for the problem. If no fix exists, contact the IBM Support
00 indicates a probable system error. Notify the system Center. Provide the ABEND dump.
programmer.
Source: Global resource serialization
For reason code 04, identify the program that issued the
ATTACH macro. If an installation-provided program
535
issued the ATTACH, change the macro parameter from
STAI to ESTAI. If an IBM-provided program issued the Explanation: SVC 53, which obtains and releases
ATTACH, notify the system programmer. exclusive control of a resource associated with a BDAM
data set, issued a GETMAIN for storage to be used in
System programmer response: Search problem
its processing and found no storage was available.
reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Application Programmer Response: Rerun the job. If
the problem continues, storage may have to be freed by
Source: Task management
others before the exclusive control function is used.
System programmer response: If the error recurs
52D
and the program is not in error, search problem
Explanation: A program requested an overlay. The reporting databases for a fix for the problem. If no fix
overlay supervisor called the program loader to obtain exists, contact the IBM Support Center. Provide the
the module segment from a linear format data set (such JCL, the SYSOUT output for the job, and all printed
as a PDSE), and the program loader encountered a output and output data sets related to the problem.
problem while processing the request.
Source: DFSMSdfp
System action: The system abnormally ends the
program that requested the overlay. The system writes
538
an ABEND dump, if a dump DD statement is provided.
In addition, the program loader may issue ABEND0F4 Explanation: The system determined that a requested
and an SVCDUMP. ENQ or RESERVE would have exceeded the limit on
the number of concurrent ENQ/GQSCAN/RESERVE
Application Programmer Response: If an
requests for all tasks in the address space.
ABEND0F4 was issued, see the information in this
manual for that abend. Otherwise, check the program System action: The system ends the task that issued
for errors that might cause a problem with the overlay the ENQ or RESERVE. The system issues an ABEND
segment table. Correct any errors; then assemble, link dump.
edit, and run the program again.
Operator response: Obtain an SVC dump if the
Source: Overlay supervisor system programmer requests it.
System programmer response:
v Make sure that no tasks in the job step issue
repeated ENQ, ISGENQ or RESERVE macro
instructions for resources that are not required.
Chapter 2. System Completion Codes 221
53E • 544
v Make sure that all GQSCAN requests that return v An ETXR if the ETXR parameter was specified on
TOKENs are either run to completion or are the ATTACH macro
terminated by a QUIT=YES option on a subsequent
System action: The system abnormally ends the
GQSCAN macro instruction.
originating task for the task in error.
v Make sure that all ISGQUERY requests with
RESUMETOKENs have the corresponding Application Programmer Response: Run the job
SCANACTION=RESUME and SCANACTION=QUIT again. If the error recurs, notify the system programmer.
options. System programmer response: Search problem
reporting databases for a fix for the problem. If no fix
Prior to an abend, messages ISG368E and ISG369I exists, contact the IBM Support Center.
monitor address spaces that are approaching the
request maximum. If a particular subsystem requires Source: Task management
more ENQ than normal, use the ISGADMIN service to
raise that subsystem’s maximum for unauthorized and 53F
authorized requesters. As a temporary workaround, you
can raise the overall system maximum by issuing the Explanation: An error has been detected during
following commands: checkpoint restart processing. This completion code is
v SETGRS ENQMAXA for authorized accompanied by message IHJxxxI with the appropriate
reason code.
v SETGRS ENQMAXU for unauthorized
System action: A dump is produced and an entry is
If the problem persists, set a SLIP trap for abend X'538' written to the logrec data set.
and rerun the job step. When the trap matches, instruct Application Programmer Response: Respond as
the operator to obtain an SVC dump that includes the indicated in the accompanying message.
following:
v The global resource serialization private area. Source: DFSMSdfp
v The system queue area (SQA), to get the address
space control block (ASCB) for the failing program. 544
Explanation: The error occurred during the processing
Use the GRS QCBTRACE IPCS report to determine the of SYNADAF, where it was determined that the IOB
outstanding ENQs for the failed address space. If abend address was incorrect.
code X’538’ is issued for an authorized caller, an SVC
dump might not be possible. If the problem persists, System action: Register 15 contains the IOB address
search problem reporting databases for a fix. If no fix in error:
exists, contact the IBM Support Center. Provide the v For BDAM, BPAM, and BSAM, SYNADAF obtained
ABEND or SVC dump. the IOB address from the DECIOBPT field of the
DECB; for these access methods, the DECB address
If the problem persists, search problem reporting was passed to SYNADAF as the PARM2 operand on
databases for a fix for the problem. If no fix exists, the macro instruction, and was contained in register 0
contact the IBM Support Center. Provide the ABEND or on entry to the user’s SYNAD routine. Verify that the
SVC dump. PARM2 operand on the SYNADAF macro instruction
was correctly specified and that the DECIOBPT field
Source: Global resource serialization
has not been overlaid.
v For QSAM, BISAM, and QISAM, SYNADAF received
53E a pointer to the IOB as the PARM2 operand on the
Explanation: During end-of-task processing, the macro instruction. The address passed to SYNADAF
system found an error before: should have been the address contained in register 0
on entry to the user’s SYNAD routine. Verify that the
v The system could post an event control block (ECB)
PARM2 operand on the SYNADAF macro instruction
for the ending task
was correctly coded.
v The system could schedule an end-of-task exit
v For the EXCP access method, verify that the PARM1
routine (ETXR)
operand of the SYNADAF macro instruction specified
v The system could determine that the task had neither the correct IOB address.
an ECB nor an ETXR
Application Programmer Response: Correct the
The task contains either: error and rerun the job step.
v An end-of-task ECB, if the ECB parameter was System programmer response: If the error recurs
specified on the ATTACH macro that created the task and the program is not in error, look at the messages in
the job log for more information. Search problem
reporting databases for a fix for the problem. If no fix
222 z/OS V1R10.0 MVS System Codes
553 • 56D
exists, contact the IBM Support Center. Provide the JCL
55F
and the program listing for the job.
Explanation: This abend code describes cases in
Source: DFSMSdfp
which the System Resource Manager (SRM) terminates
an address spaces abnormally.
553
The hexadecimal reason code explains the error:
Explanation: System management facilities (SMF)
Code Explanation
detected that the SMF timer queue element (STQE)
chain was in error. | xxxx0000
| During the processing of a cross Memory
A hexadecimal reason code in register 15 explains the
| POST macro for a swap out complete
error:
| (SYSEVENT 15), the system encountered an
Code Explanation | error. The POST notified a SYSEVENT
| REALSWAP or TRANSWAP issuer that either
04 The forward pointer of an STQE contains | the swap had to be turned around or the swap
zeroes. The system produces an SVC dump, | was complete.
and SMF repairs the STQE chain.
| System Action: The system ends the issuer of
Note: Repairing the STQE chain results in the | the cross memory POST abnormally. The
loss of some STQEs. Therefore, some | system writes messages and a logrec data set
tasks no longer provide SMF interval | error record.
recording. | System Programmer Response: Determine if
08 The STQE chain points to an element that is | the POST macro passes a valid event control
not an STQE. | block (ECB) address. Resubmit the job. If the
| problem reoccurs, search the problem reporting
Note: Repairing the STQE chain results in the | databases for a fix for the problem. If no fix
loss of some STQEs. Therefore, some | exists, contact the IBM Support Center. Provide
tasks no longer provide SMF interval | the logrec data set error record with the
recording. | SYSOUT output of the job.
0C The backward pointer of an STQE contains | Module: IRARMPST
zeroes. The system produces an SVC dump, | xxxx0004
and SMF repairs the STQE chain. | The outstanding WTOR message IRA421D
| was answered with a reply of ‘1’ to ‘5’, which
Note: Repairing the STQE chain results in the | resulted in an abnormal termination of an
loss of some STQEs. Therefore, some | address space.
tasks no longer provide SMF interval
recording. | Module: IRARMWT1
System action: The SMF timer program ends, and the | xxxx0008
system produces an SVC dump. | The outstanding WTOR message IRA221D
| was answered with a reply of ‘1’ to ‘5’, which
Operator response: Notify the system programmer. | resulted in an abnormal termination of an
You can re-establish SMF interval recording for a | address space.
specific task by restarting that task. Consider restarting
tasks for which SMF interval recording is required. | Module: IRARMWT2
However, if you must re-establish SMF interval Source: System Resource Manager (SRM)
recording, but you can’t determine which tasks to
restart, reIPL the system.
56D
System programmer response: Check error
messages and the SVC dump produced as a result of Explanation: The system issued SVC 109 with routing
any previous abends. Check for any previous abend code 11 in register 15 (the Sort SVC). One of the
code X'0C4' that might indicate a storage overlay has following error conditions exists:
occurred. If there is no previous abend code X'0C4', v A task other than Sort issued SVC 109 with routing
search problem reporting databases for a fix for the code 11. Only Sort is authorized to issue it.
problem. If no fix exists, contact the IBM Support v The task that issued the SVC passed a record that
Center. was not in the task’s authorized area.
Source: System management facilities (SMF) v The task passed a record that contained one or more
incorrect fields.
System action: The task ends. The system issued an
Chapter 2. System Completion Codes 223
56F • 585
SVC dump and a logrec data set error record. exists, contact the IBM Support Center. Provide the
program listing and the assembly listing associated with
Application Programmer Response: If the problem
the job.
occurred because a task other than Sort issued SVC
109 with routing code 11, correct the task. Source: Task management
If the problem occurred while Sort was executing,
contact the system programmer. 582
System programmer response: If the problem recurs Explanation: While processing a RACROUTE
and if the program is not in error, search problem REQUEST=AUTH request, RACF was unable to verify
reporting databases for a fix for the problem. If no fix a user.
exists, contact the IBM Support Center. Provide the
System action: The system abnormally terminates the
SVC dump and the logrec data set error record.
task.
Source: Time Sharing Option Extensions (TSO/E)
Application Programmer Response: Register 15
contains a hexadecimal reason code. (Message
56F ICH409I, if issued, also contains this return code.)
Explanation: The error occurred during end-of-job Code Explanation
processing for a JES2 job that was being processed by
00 No accessor control environment (ACEE) was
an execution batch monitor. The execution batch
available to describe the user.
monitor pseudo job select procedure found that another
task was holding or waiting for a lock on the SJB
(subsystem job block). Note: This is normal if a job started or a user
logged on while RACF was inactive but
System action: The job terminates. has since been reactivated.
Application Programmer Response: Notify the 04 Reserved.
system programmer or installation manager of the
problem. Identify and correct the indicated error.
System programmer response: Make sure the failing Problem determination: Run the job again, or have
job step includes a SYSABEND DD statement. the user log on again while RACF is active. If the abend
If the problem recurs and if the program is not in error, occurs again, see z/OS Security Server RACF
search problem reporting databases for a fix for the Diagnosis Guide for information on diagnosing abends
problem. If no fix exists, contact the IBM Support and reporting abend problems to IBM.
Center.
Source: JES2 585
Explanation: While processing a RACROUTE
57D REQUEST=DEFINE request, RACF encountered an
error.
Explanation: During processing of an EVENTS macro,
the system found either: System action: The system terminates the task.
v An incorrect event control block (ECB) address Application Programmer Response: Register 15
v The program issuing the EVENTS macro instruction contains a hexadecimal reason code. (Message
is running under a protection key (8 through 15) that ICH409I, if issued, also contains this return code.)
is different from the protection key of the ECB Code Explanation
System action: The system abnormally ends the 00 No accessor environment element (ACEE) was
program that issued the EVENTS macro. available to describe the user.
Application Programmer Response: Ensure that the
ECB address specified is a valid virtual storage address Note: This is normal if a job started or a user
and that it was not incorrectly modified. Also, ensure logged on while RACF was inactive but
that the ECB is placed in storage belonging to the has since been reactivated.
program issuing the EVENTS macro or the program 04 No UCB was found to contain a volume serial
running under protection key 0 through 7. Correct the that matched the volume serial passed to
error. Run the job again. RACF in the REQUEST=DEFINE macro
System programmer response: If the error recurs instruction for a TYPE=DEFINE operation.
and the program is not in error, look at the messages in 08 The ADDVOL or CHGVOL function was
the job log for more information. Search problem requested but the user did not have at least
reporting databases for a fix for the problem. If no fix UPDATE authority to the data set.
224 z/OS V1R10.0 MVS System Codes
5C4
0C The ADDVOL function was requested and (1) 00040001 For a call to the End_Restart service,
the volume serial number is already defined the parameters are not addressable.
(for DATASET class), or (2) the new tape
00050000 For a call to the Retrieve_Log_Name
volume is already defined (for TAPEVOL
service, the parameters are not in the
class).
primary address space.
The CHGVOL function was requested and a
00050001 For a call to the Retrieve_Log_Name
data set profile with ENTITY name and a new
service, the parameters are not
volume serial number is already defined.
addressable.
Identify and correct the indicated error. 00060000 For a call to the Retrieve_UR_Interest
service, the parameters are not in the
System programmer response: For reason code 00,
primary address space.
run the job again, or have the user log on again while
RACF is active. If the abend occurs again, see z/OS 00060001 For a call to the Retrieve_UR_Interest
Security Server RACF Diagnosis Guide for information service, the parameters are not
on diagnosing abends and reporting abend problems to addressable.
IBM. For the other reason codes, correct the problem
00070000 For a call to the Process_Interest
indicated by the reason code. For assistance in
service, the parameters are not in the
gathering additional information about the request that
primary address space.
caused this abend (such as obtaining a dump or
identifying the caller of RACF), see z/OS Security 00070001 For a call to the Process_Interest
Server RACF Diagnosis Guide. If an IBM program service, the parameters are not
issued the REQUEST=DEFINE macro, see z/OS addressable.
Security Server RACF Diagnosis Guide for information
on reporting abend problems to IBM. 00080000 For a call to the Set_Log_Name
service, the parameters are not in the
primary address space.
5C4
00080001 For a call to the Set_Log_Name
Explanation: A call for a resource recovery services service, the parameters are not
(RRS) service was issued in an incorrect environment. addressable.
Register 15 contains a hexadecimal reason code.
00090000 For a call to the
Code Explanation Post_Deferred_UR_Exit routine
service, the parameters are not in the
xxxx000B RRS was unable to obtain a required
primary address space.
storage area. The storage area could
be in CSA. 00090001 For a call to the
Post_Deferred_UR_Exit routine
00010000 For a call to the Delete_UR_Interest
service, the parameters are not
service, the parameters are not in the
addressable.
primary address space.
000B0000 For a call to the
00010001 For a call to the Delete_UR_Interest
Retrieve_Interest_Data service, the
service, the parameters are not
parameters are not in the primary
addressable.
address space.
00020000 For a call to the Express_UR_Interest
000B0001 For a call to the
service, the parameters are not in the
Retrieve_Interest_Data service, the
primary address space.
parameters are not addressable.
00020001 For a call to the Express_UR_Interest
000C0000 For a call to the Retrieve_UR_Data
service, the parameters are not
service, the parameters are not in the
addressable.
primary address space.
00030000 For a call to the Begin_Restart
000C0001 For a call to the Retrieve_UR_Data
service, the parameters are not in the
service, the parameters are not
primary address space.
addressable.
00030001 For a call to the Begin_Restart
000D0000 For a call to the
service, the parameters are not
Retrieve_Side_Information service, the
addressable.
parameters are not in the primary
00040000 For a call to the End_Restart service, address space.
the parameters are not in the primary
000D0001 For a call to the
address space.
Chapter 2. System Completion Codes 225
5C4
Retrieve_Side_Information service, the Application_Backout_UR service, the
parameters are not addressable. parameters are not addressable.
000E0000 For a call to the 00150002 For a call to the
Retrieve_Work_Identifier service, the Application_Backout_UR service, the
parameters are not in the primary caller is disabled.
address space.
00150003 The program that called the
000E0001 For a call to the Application_Backout_UR service is
Retrieve_Work_Identifier service, the holding one or more locks; no locks
parameters are not addressable. must be held.
000F0000 For a call to the 00150004 The program called the
Change_Interest_Type service, the Application_Backout_UR service. The
parameters are not in the primary system release does not support this
address space. service.
000F0001 For a call to the 00150005 The program that called the
Change_Interest_Type service, the Application_Backout_UR service is in
parameters are not addressable. an unsupported ASC mode; the mode
must be primary.
00100000 For a call to the
Set_Persistent_Interest_Data service, 00150006 The program called the
the parameters are not in the primary Application_Backout_UR service. The
address space. UR is either:
00100001 For a call to the v not in a valid state for the service
Set_Persistent_Interest_Data service, call. The UR state must be in-reset
the parameters are not addressable. or in-flight; or,
v in local transaction mode. This
00110000 For a call to the Retain_Interest
service is only valid for a UR in
service, the parameters are not in the
global transaction mode.
primary address space.
00150007 The program called the
00110001 For a call to the Retain_Interest
Application_Backout_UR service. The
service, the parameters are not
service encountered an unexpected
addressable.
error. RRS writes a logrec record and
00120000 For a call to the Set_Sync- takes a dump.
point_Controls service, the parameters
00150009 The program that called the
are not in the primary address space.
Application_Backout_UR service is
00120001 For a call to the Set_Sync- not in task mode, which is required.
point_Controls service, the parameters
00150010 The program called the
are not addressable.
Application_Backout_UR service, but
00130000 For a call to the Set_Side_Information the current UR (the UR being
service, the parameters are not in the processed) encountered an
primary address space. unexpected error, and RRS cannot
continue to process the UR.
00130001 For a call to the Set_Side_Information
service, the parameters are not 00150011 The program called the
addressable. Application_Backout_UR service, but
the service encountered an
00140000 For a call to the Set_Work_Identifier unexpected error from a context
service, the parameters are not in the services service.
primary address space.
00160000 For a call to the
00140001 For a call to the Set_Work_Identifier Application_Commit_UR service, the
service, the parameters are not parameters are not in the primary
addressable. address space.
00150000 For a call to the 00160001 For a call to the
Application_Backout_UR service, the Application_Commit_UR service, the
parameters are not in the primary parameters are not addressable.
address space.
00160002 The program that called the
00150001 For a call to the Application_Commit_UR service is
226 z/OS V1R10.0 MVS System Codes
5C4
disabled; the interrupt status must be Only the top-level UR of a cascaded
enabled for I/O and external UR family can be committed.
interrupts.
00170000 For a call to the Backout_UR service,
00160003 The program that called the the parameters are not in the primary
Application_Commit_UR service is address space.
holding one or more locks; no locks
00170001 For a call to the Backout_UR service,
must be held.
the parameters are not addressable.
00160004 The program called the
00180000 For a call to the Commit_UR service,
Application_Commit_UR service. The
the parameters are not in the primary
system release does not support this
address space.
service.
00180001 For a call to the Commit_UR service,
00160005 The program that called the
the parameters are not addressable.
Application_Commit_UR service is in
an unsupported ASC mode; the mode 001A0000 For a call to the Backout_Agent_UR
must be primary. service, the parameters are not in the
primary address space.
00160006 The program called the
Application_Commit_UR service. The 001A0001 For a call to the Backout_Agent_UR
UR is either: service, the parameters are not
v not in a valid state for the service addressable.
call. The UR state must be in-reset 001B0000 For a call to the Commit_Agent_UR
or in-flight; or, service, the parameters are not in the
v in local transaction mode. This primary address space.
service is only valid for a UR in
global transaction mode. 001B0001 For a call to the Commit_Agent_UR
service, the parameters are not
00160007 The program called the addressable.
Application_Commit_UR service. The
service encountered an unexpected 001C0000 For a call to the Forget_Agent_UR
error. RRS writes a logrec record and service, the parameters are not in the
takes a dump. primary address space.
00160008 An application program called the 001C0001 For a call to the Forget_Agent_UR
Application_Commit_UR service but a service, the parameters are not
resource manager has already taken addressable.
the server distributed sync-point 001D0000 For a call to the Prepare_Agent_UR
resource manager role (SDSRM), and service, the parameters are not in the
only the SDSRM can initiate a primary address space.
syncpoint operation.
001D0001 For a call to the Prepare_Agent_UR
00160009 The program that called the service, the parameters are not
Application_Commit_UR service is not addressable.
in task mode, which is required.
001F0000 For a call to the
00160010 The program called the Create_Cascaded_UR service, the
Application_Commit_UR service, but parameters passed by the caller are
the current UR (the UR being not in the primary address space.
processed) encountered an
unexpected error, and RRS cannot 001F0001 For a call to the
continue to process the UR. Create_Cascaded_UR service, the
parameters passed by the caller are
00160011 The program called the not addressable.
Application_Commit_UR service, but
the service encountered an 00200000 For a call to the Set_Post_Sync_PET
unexpected error from a context service, the parameters passed by the
services service. caller are not in the primary address
space.
00160012 The program called the
Application_Commit_UR service, but 00200001 For a call to the Set_Post_Sync_PET
the current UR (the UR being service, the parameters passed by the
processed) is a child cascaded UR. caller are not addressable.
00210000 For a call to the
Chapter 2. System Completion Codes 227
5C6
Delete_Post_Sync_PET service, the Application Programmer Response: For most of the
parameters passed by the caller are reason codes, check the calling program for a probable
not in the primary address space. coding error; correct the program and rerun it.
00210001 For a call to the For reason code X'xxxx000B', either enlarge CSA or
Delete_Post_Sync_PET service, the contact the IBM Support Center and provide the dump.
parameters passed by the caller are
For reason code X'00150004' or X'00160004', remove
not addressable.
the calling program from the system, and install it on a
00220000 For a call to the system that supports RRS. Then rerun the program.
Delegate_Commit_Agent_UR service,
For reason code X'00150007' or X'00160007', obtain the
the parameters passed by the caller
related logrec record and dump, then contact IBM
are not in the primary address space.
support.
00220001 For a call to the
For reason code X'00150010' or X'00160010', check
Delegate_Commit_Agent_UR service,
other diagnostic information to determine why RRS
the parameters passed by the caller
encountered the error. To ensure resource consistency,
are not addressable.
you might need to intervene manually.
00230000 For a call to the Begin_Transaction
For reason code X'00150011' or X'00160011', check
service, the parameters passed by the
diagnostic information, such as the dump, from context
caller are not in the primary address
services to determine why the error occurred.
space.
For reason code X'01010005', check that coupling
00230001 For a call to the Begin_Transaction
facilities are active.
service, the parameters passed by the
caller are not addressable. For reason code X'FFFF2222', no action is necessary.
00240000 For a call to the End_Transaction For any other reason code, save any dump related to
service, the parameters passed by the the problem and call the IBM Support Center.
caller are not in the primary address
space. Source: Resource recovery services (RRS)
00240001 For a call to the End_Transaction
service, the parameters passed by the 5C6
caller are not addressable. Explanation: When the system detects an error in
00260000 For a call to the Set_Environment internal WebSphere® MQSeries processing, it will
service, the parameters passed by the abnormally end a connected user task (TCB) or one of
caller are not in the primary address its own internal tasks. See the WebSphere MQ for z/OS
space. Problem Determination Guide V5.3.1 for a description of
diagnostic approaches to either a X'5C6' or X'6C6'
00260001 For a call to the Set_Environment abend. For information about the reason codes
service, the parameters passed by the associated with either abend, see the WebSphere MQ
caller are not addressable. for z/OS Messages and Codes V5.3.1.
00270000 For a call to the Retrieve_Environment System action: The system abnormally ends the
service, the parameters passed by the connected user task or the MQSeries internal task.
caller are not in the primary address
space. Application Programmer Response: Check register
15 of the SDWA section ’General Purpose Registers at
00270001 For a call to the Retrieve_Environment Time of Error’, and locate the accompanying reason
service, the parameters passed by the code. In addition, check the information displayed at the
caller are not addressable. console screen, and in the corresponding logrec data
set entry.
01010005 RRS WHEN CFS ARE DOWN
System programmer response: If the error recurs
021F0001 An RRS service was called, but the
and the program is not in error, look at the messages in
RRS service could not be processed
the job log for more information. Search problem
because the RRS address space was
reporting databases for a fix for the problem. If no fix
down.
exists, contact the IBM Support Center. Provide the
FFFF2222 The SETRRS CANCEL command has SYSOUT output for the job and the logrec data set error
cancelled RRS processing record.
System action: The system rejects the service call. Source: MQSeries
The system abnormally ends the calling program.
228 z/OS V1R10.0 MVS System Codes
5FB • 602
Register 3 contains the macro return code for reason
5FB
code X'02', X'03', X'04', X'06', or X'0A'.
Explanation: During processing of an MVS-JES3
System action: The system abnormally ends the task.
allocation subsystem interface routine, an error
occurred. A hexadecimal reason code in register 15 System programmer response: Search problem
explains the error. reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
Code Explanation
Provide the JCL and the program listing for the job.
01 In common allocation, the number of devices
requested by MVS does not equal the number Source: JES3
to be allocated by JES3. Register 3 contains
the number requested by MVS; register 5
contains the number passed by JES3. Register 5FC
2 contains the address of the DDNAME. Explanation: Following a restart interrupt, an error
02 During deallocation processing, JES3 cannot occurred in the restart first level interrupt handler (FLIH).
successfully issue an ESTAE macro. System action: The system abnormally ends the task
03 JES3 cannot obtain storage for a dynamic that experienced the restart interrupt.
allocation buffer. | Operator response: Perform another restart operation
04 JES3 cannot obtain storage for a change | to restart the system. If the problem recurs, notify the
DDNAME buffer. system programmer.
05 JES3 cannot find, in any address space Application Programmer Response: Submit the job
header, the address space identifier (ASID) again. If the problem recurs, notify the system
associated with the request. Register 2 programmer.
contains the address of the job step control System programmer response: Ask the operator to
block (JSCB); register 3 contains the ASID. set a SLIP trap to obtain an SVC dump. Search
06 A job summary table (JST) pointer error problem reporting databases for a fix for the problem. If
occurred during common allocation or no fix exists, contact the IBM Support Center. Provide
deallocation. the SVC dump and, if available, the logrec data set
error record for the abend.
07 Module IATSICA cannot find an active
MEMDATA entry for the address space. Source: Loadwait/Restart
Register 2 contains the address of the job step
control block (JSCB); register 3 contains the 602
address space ID (ASID) of the requesting
address space; register 8 contains the address Explanation: An error occurred during processing of a
of the MEMDATA header. POST macro instruction. The system issues this abend
only in association with cross memory post processing.
08 Module IATSIMS cannot find an active
MEMDATA entry for the address space. The hexadecimal return code in register 15 indicates the
Register 4 contains the address of the nature of the error:
subsystem identification block (SSIB); register Code Explanation
6 contains field SSIBSUSE of the SSIB.
However, both registers 4 and 6 may be 00 The target address space control block (ASCB)
incorrect. is incorrect.
09 JES3 found a duplicate volume. The volume System action: The system abnormally ends the
cannot be loaded. Register 2 contains the program that issued the POST macro.
address of the SETUNIT; register 6 contains Application Programmer Response: Correct the
the address of the job summary table (JST). error identified by the return code. Run the job step
0A The GETMAIN macro failed for a work area for again.
the subsystem interface (SSI). System programmer response: If the error recurs
0B JES3 cannot process the number of and the program is not in error, search problem
concatenated DD statements passed in a reporting data bases for a fix for the problem. If no fix
change DD name request. The number of DD exists, contact the IBM Support Center.
statements is variable; the approximate Source: Task management
maximum number is 187.
Chapter 2. System Completion Codes 229
604 • 60D
604 60D
Explanation: An error occurred when the system tried Explanation: The recovery termination manager
to process an EC, EU, LC, LU, VC, or VU form of the (RTM) discovered an error in a calling program.
GETMAIN macro. A reason code in the SDWACRC field
A hexadecimal reason code in the following explains the
of the system diagnostic work area (SDWA) explains
error:
the error:
v Field RTM2CRC of the RTM2 work area (RTM2WA)
Code Explanation v Message IEA995I
v TCBARC field of the task control block (TCB)
04 The parameter list is not on a word boundary.
Code Explanation
08 The parameter list is in protected storage.
00 RTM percolates past the previous exit routine
0C The length list is not on a word boundary.
because the recursion limit had been reached
10 The length list is in protected storage. for that routine.
14 The address list is not on a word boundary. 04 A program issued the ABEND, CALLRTM, or
SETRP macro with the DUMPOPT or
18 The address list is in protected storage. DUMPOPX parameter. DUMPOPT or
1C The parameter list request flags are not valid. DUMPOPX contains a pointer to a parameter
list, but RTM cannot access the parameter list.
System action: The system issues message IEA705I.
The system abnormally ends the current task. 08 A program issued the ABEND, CALLRTM, or
SETRP macro with the DUMPOPT or
Application Programmer Response: Ensure that the DUMPOPX parameter. DUMPOPT or
length list and address list are aligned on word DUMPOPX contains a pointer to a parameter
boundaries. Check for program errors that incorrectly list. The parameter list contains a storage
modify the parameter list. Correct them. Run the job range list, but RTM cannot access the storage
step again. range list.
Source: Virtual storage manager (VSM) 0C A program issued the ABEND, CALLRTM, or
SETRP macro with the DUMPOPT or
605 DUMPOPX parameter. DUMPOPT or
DUMPOPX contains a pointer to a parameter
Explanation: An error occurred when the system tried list. The parameter list contains a subpool list,
to process an EC, EU, LC, LU, VC, or VU form of the but RTM cannot access the subpool list.
FREEMAIN macro. A reason code in the SDWACRC
field of the system diagnostic work area (SDWA) 10 A program issued the ABEND, CALLRTM, or
explains the error: SETRP macro with the DUMPOPT or
DUMPOPX parameter. DUMPOPT or
Code Explanation DUMPOPX contains a pointer to a parameter
04 The parameter list is not on a word boundary. list. The parameter list contains a range of data
space storage to be dumped, but RTM cannot
08 The parameter list is in protected storage. access this storage.
0C The length list is not on a word boundary. 14 Retry was attempted from an FRR, but the
retry linkage stack is inconsistent with the
10 The length list is in protected storage.
requested retry environment.
14 The address list is not on a word boundary.
18 Retry was attempted from an FRR, but the
18 The address list is in protected storage. linkage stack entry is not in the currently active
linkage stack range.
1C The parameter list request flags are not valid.
System action: Depending on the reason code, the
System action: The system issues message IEA705I.
system does the following:
The system abnormally ends the current task.
v For reason code X'00', RTM:
Application Programmer Response: Ensure that the
– Gives control to any previous exit routines that are
length list and address list are aligned on word
valid
boundaries. Check for program errors that incorrectly
modify the parameter list. Correct them. Run the job – Resets the recursion count to 0
step again. – Requests a dump
Source: Virtual storage manager (VSM) – Issues message IEA995I
230 z/OS V1R10.0 MVS System Codes
613 • 622
v For reason codes 4 - 10, RTM continues processing
614
the current recovery routine and issues message
IEA995I. Explanation: The error occurred during processing of
v For reason codes 14 - 18, the retry is not performed. a CLOSE macro instruction for a data set on a direct
access device. This system completion code is
System programmer response: For reason code accompanied by message IEC214I. Refer to the
X'00': explanation of message IEC214I for complete
v Look in the dump for a task control block (TCB) with information about the job that was ended and for an
X'60D' in the TCBCMP field. Look at the explanation of the return code (rc in the message text)
accompanying STAE control blocks (SCB). There will in register 15.
be at least 32 SCBs. The SCBEXIT field contains the
Application Programmer Response: Respond as
address of the recovery routine. Many of the SCBs
indicated for message IEC214I.
will have the same recovery routine address. Use the
SCBEXIT value which is contained in many of the System programmer response: If the error recurs
SCBs to get the name of the module of the recovery and the program is not in error, look at the messages in
routine. the job log for more information. Search problem
v Identify the component for the module. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL
– If the recovery routine is an installation-provided
and the program listing for the job.
module, correct the original error and the exit
routine that ended recursively, or correct the Source: DFSMSdfp
problem with the DUMPOPT or DUMPOPX
parameter list.
622
– If the recovery routine is an IBM module, search
problem reporting data bases for a fix for the Explanation: A task entered from a Time Sharing
problem. If no fix exists, contact the component Option (TSO) terminal ended for one of the following
group for the module at the IBM Support Center. reasons:
Provide problem data collected in previous steps. 1. The system encountered one of the following errors
v For reason codes 04 - 10, identify the program that while constructing control blocks for TSO:
issued ABEND, CALLRTM, or SETUP with the a. The system encountered a multiple-step
DUMPPT/DUMPOPX parameter. If it is an installation procedure.
module, correct the problem. If it is an IBM module, b. The prompting task ended abnormally.
search problem reporting data bases for a fix for the 2. The terminal user signaled ATTN during LOGON
problem. If no fix exists, contact the IBM Support scheduling.
Center. 3. The user submitting the job disconnected his or her
v For reason codes 14 -18, contact the IBM Support terminal from the system.
Center. 4. The terminal malfunctioned.
Source: Recovery termination manager (RTM) System action: In cases 1, the system issued
messages to the terminal describing the error
613 conditions.
Explanation: The error occurred during processing of Application Programmer Response: In the first case,
an OPEN macro instruction for a data set on magnetic respond to the messages accompanying this abend:
tape. This system completion code is accompanied by v For case 1a, specify a different procedure or consult
message IEC147I. Refer to the explanation of message your system programmer. Try running the job again.
IEC147I for complete information about the job that was v For case 1b, consult your system programmer.
ended and for an explanation of the return code (rc in
the message text) in register 15.
In the second case, LOGON again; make sure that you
Application Programmer Response: Respond as do not signal ATTN inadvertently.
indicated for message IEC147I.
In the third case, try running the job again when the
System programmer response: If the error recurs
terminal is reconnected to the system.
and the program is not in error, look at the messages in
the job log for more information. Search problem
In the fourth case, contact hardware support.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL System programmer response: If the problem recurs
and the program listing for the job. and if the program is not in error, search problem
reporting data bases for a fix for the problem. If no fix
Source: DFSMSdfp
exists, contact the IBM Support Center. Provide the
terminal sheet available and a record of the current
Chapter 2. System Completion Codes 231
637 • 653
display on the graphics device. Operator Response: Notify the system
programmer.
Source: Time Sharing Option Extensions (TSO/E)
System Programmer Response: It is likely
the SMFEWTM or SMFWTM caller is
637
experiencing storage problems. Check for an
Explanation: The error occurred at an end-of-volume ABEND878 or other prior virtual storage
for a data set on magnetic tape or an end-of-volume abends, and follow the recommended actions
during concatenation. This system completion code is accordingly.
accompanied by message IEC026I. Refer to the
| 09 IXGWRITE failure. The IXGWRITE operation
explanation of message IEC026I for complete
| used for writing a block of data to the
information about the task that was ended and for an
| logstream failed because of an internal error.
explanation of the return code (rc in the message text)
| For this error, registers 2 and 3 contain the
in register 15.
| return and reason codes that were returned
Application Programmer Response: Respond as | following the IXGWRITE operation. The
indicated for message IEC026I. | IXGWRITE return and reason codes are
| described in z/OS MVS Programming:
System programmer response: If the error recurs | Assembler Services Reference IAR-XCT.
and the program is not in error, look at the messages in
the job log for more information. Search problem | System Action: SMF disconnects the log
reporting data bases for a fix for the problem. If no fix | stream that was to receive the data at the time
exists, contact the IBM Support Center. Provide the JCL | when the failing IXGWRITE was issued. SMF
and the program listing for the job. | processing continues, and the data that SMF
| collects that are directed to be written to the
Source: DFSMSdfp | now disconnected log stream are buffered until
| the log stream is connected.
644 | Operator Response: Notify the system
Explanation: The error occurred during the processing | programmer.
of SYNADAF, where it was determined that the | System Programmer Response: Capture the
message buffer obtained in the user’s region had been | dump and report the problem to the IBM
modified or freed. | support center.
Application Programmer Response: Register 15 | 101-111
contains the address of the message buffer area. Make | Error in IFASEXIT processing. For all of these
sure that your program does not modify or free this area | error codes:
until SYNADAF processing is complete. Correct the
error and rerun the job step. | System Action: IFASEXIT processing is
| discontinued for the current SMF record.
System programmer response: If the error recurs
and the program is not in error, look at the messages in | Operator Response: Notify the system
the job log for more information. Search problem | programmer.
reporting data bases for a fix for the problem. If no fix
| System Programmer Response: Capture the
exists, contact the IBM Support Center. Provide the JCL
| dump and report the problem to the IBM
and the program listing for the job.
| support center.
Source: DFSMSdfp
| 101 IFASEXIT failed to establish recovery.
| 102 Incorrect input parameter list.
653
| 103 Failure obtaining storage for
Explanation: System management facilities (SMF)
| IFASXCB.
encountered an error while attempting to write an SMF
record. | 104 Failure obtaining storage for
| IFASXCBG.
Register 15 contains a hexadecimal reason code that
explains the error: | 105 Failure obtaining storage for the log
| stream block (buffer).
Code Explanation
| 106 OPEN validation error because the
04 GETMAIN failure.
| IFASXCB token area is not correct.
System Action: The SMFEWTM or SMFWTM
| 108 Error on browse option because of
request fails and SMF continues processing.
| incomplete browse parameters.
| 110 IFASXGET input event error.
232 z/OS V1R10.0 MVS System Codes
65F • 66D
| 111 IFASXGET browse session was not by the caller. This is an internal error. TSO
| established. does not perform the requested function.
Source: System Management Facilities (SMF) 05 A input stack address is supplied in ECTIOWA
but no stack exists.
65F 06 No input stack exists.
Explanation: The system resources manager (SRM) 07 No input stack exists, but one is being created
stopped the collection of channel measurement data in by another program. I/O service processing
the channel measurement block (CMB) because of an encountered an error in a multitasking
error condition. environment. Two tasks cannot create the first
stack at the same time.
System action: The system writes message IRA602I
to identify the error. The system writes a logrec data set 08 An abend X'0C4' occurred when validating user
error record. The system abnormally ends the current pointers.
task. It cannot be resumed until the next IPL.
09 The input stack is in use.
The SRM functions, device selection and I/O balancing,
0A An ECT was provided, but no stack exists.
use algorithms that do not make use of CMB data.
0B The ECTIOWA field does not contain the
System programmer response: Look at the reason
address of a valid stack.
code in message IRA602I. Search problem reporting
data bases for a fix for the problem. If no fix exists, 0C The user is trying to delete a stack which
contact the IBM Support Center. Provide the logrec data someone else is waiting on.
set error record.
0D REXX is unable to serialize on an internal
Source: System resources manager (SRM) resource.
0E Unable to locate the REXX data stack.
66D
0F IRXESTK1 found an incorrect count of
Explanation: This abend may be issued from three elements in the REXX data stack.
different areas in TSO/E: I/O services, REXX, and
CLIST processing. A hexadecimal reason code identifies 10 IRXESTK1 found an incorrect REXX data stack
the error. This code appears either on user’s terminal, size.
along with the abend notification, or in the dump taken 11 IRXESTK failed when called by IRXESTK1.
for the abend.
12 IRXESTK failed to purge the number of stack
Note: The reason code appears on the user’s terminal elements requested by IRXESTK1.
as a four-byte field. The rightmost two bytes 13 REXX stack processing failed to release an
contain the abend reason code. If these two internal REXX resource.
bytes are between X'000D' and X'0013', then the
leftmost two bytes (if they are non-zero) contain 14 IRXINIT failed.
the return code of the function called by the 15 REXX variable protection failed. This error can
module that issued the abend. occur if sufficient storage is not available to
properly protect or unprotect variables when
For example, if the reason code is X'0008000D', the attempting to invoke an authorized command
abend reason code is X'000D' and the return code of or program under REXX. If this error occurs,
the function called by the module is X'0008'. try changing your TSO/E PROFILE setting to
Code Explanation PROFILE VARSTORAGE(HIGH). You might
also try using a larger REGION size when
01 Recovery cannot be established. This is an logging onto TSO/E.
internal error. TSO does not perform the
requested function. 16 The MARKTERM function of IRXESTK failed.
While processing the data stack, TSO I/O
02 ECTIOWA contains an non-valid input stack services encountered an error. TSO does not
address. perform the requested function.
03 The input stack was in use by another task 17 The DROPTERM function of IRXESTK failed.
when re-serialization was done. I/O services, While processing the data stack, TSO I/O
REXX, or CLIST processing encountered an services encountered an error. TSO does not
error in a multitasking environment. perform the requested function.
04 An non-valid I/O service identifier was supplied 18 The PULL function of IRXESTK failed. While
Chapter 2. System Completion Codes 233
66D
processing the data stack, TSO I/O services 2F The REXX storage manager could not free the
encountered an error. TSO does not perform requested storage.
the requested function.
30 Module IGX00043 was invoked with
19 The input stack size limit was exceeded. parameters that were not valid. TSO/E I/O
services encountered an internal error. TSO
1E The REXX storage manager was passed a
does not perform the requested function.
control block that is not valid.
31 A TSO/E service that requires a TSO/E
1F The REXX storage manager was requested to
environment was invoked in a non-TSO/E
free storage for a control block that is not valid.
environment.
20 The REXX storage manager could not allocate
3C The QUEUED function of IRXESTK failed.
storage from the requested control block due to
While processing the data stack, TSO I/O
an internal error.
services encountered an error. TSO does not
21 The REXX storage manager could not free perform the requested function.
storage for the requested control block
40 GETMAIN failure. This error can occur if
because the storage was freed previously.
sufficient storage is not available in the CLIST
22 The REXX storage manager could not free the or Authorized REXX variable pool. If this error
storage because the storage tree is not valid. occurs, try changing your TSO/E PROFILE
setting to PROFILE VARSTORAGE(HIGH).
23 The REXX storage manager could not free the
storage because the storage tree is not valid. 41 Stack serialization token has wrapped.
24 The REXX storage manager could not allocate 42 The token which was associated with the top
the requested storage. The tree used to stack element has changed. This means that
manage the storage has an incorrect format. the stack has been modified while the lock was
released.
25 The REXX storage manager could not allocate
the requested storage. An internal 43 A TSO/E Service Routine detected a
tree-management routine failed. serialization error with the ALTLIB or VLF
environment.
26 The REXX storage manager could not allocate
the requested storage. The tree was 44 The user is trying to OPENFILE a dataset
determined to be not valid after storage which is marked EXECUTE-ONLY.
allocation occurred.
45 The user is trying to submit a member of a
27 The REXX storage manager could not allocate dataset which is marked EXECUTE-ONLY.
the requested storage. The tree was
46 The user is trying to execute a CLIST from a
determined to be not valid after storage
dataset which is marked EXECUTE-ONLY.
allocation occurred.
47 The user invoked the TSO/E environment
28 The REXX storage manager could not assign
service with a bad parameter list.
the new extent.
48 The user tried to invoke the TSO/E
29 The REXX storage manager could not obtain
environment service on an incorrect version of
additional storage from the main REXX storage
TSO/E.
manager control block.
49 The user attempted to run an authorized
2A The REXX storage manager determined that a
command or program. This is not supported in
tree is not valid. An incorrect control block was
the TSO/E environment created by the TSO/E
present at the top of the tree.
environment service.
2B The REXX storage manager determined that a
4A The user attempted to attach the TSO/E TMP
tree is not valid. An incorrect control block was
routine (IKJEFT01) while in a dynamic TSO/E
passed.
environment.
2C The REXX storage manager determined that a
4B REXX output processing failed in a TSO/E
tree is not valid. An inner vertex appeared in
environment. No command processor
place of the top of the tree.
parameter list (CPPL) was available.
2D While invoking an internal routine, the REXX
4C REXX output processing failed in a TSO/E
storage manager determined that no dynamic
environment.
storage was available.
4D TSO/E has detected an overlay condition while
2E The REXX storage manager could not obtain
reading a member from a concatenated data
the requested storage.
set. One possible reason for this overlay
234 z/OS V1R10.0 MVS System Codes
66D
condition is the concatenation of data sets with monitor program (TMP) initialization function
unlike RECFM specifications. before calling this service, or use the
stack-create service.
50 The user entered the REXX immediate
command HE in order to halt execution of the 08 Verify that all addresses in the I/O service
current REXX exec. This abend does not parameter list (and the IKJCT441 parameter
represent an error condition. list if applicable) are correct.
51 Incorrect key or state at invocation. 0B Provide a valid stack address in the ECTIOWA.
The stack address may be obtained from the
52 An ESTAE environment could not be
ECT provided by the ECT pointed to from the
established.
CPPL or the stack-create service.
53 Caller is not at the expected operating system
14 If your installation has replaced a parameters
level (OS/390 Release 3 or higher).
module, verify that the correct module was
54 Invalid request passed from caller. called during REXX initialization.
15 The READY state resumes; retry the TSO
Note: If you are not able to locate the abend reason function.
code in the above table, see the note at the
beginning of the ABEND66D description section. 19 Log off from TSO/E and log back on. If the
problem occurs again, check your programs
System action: The action of the system varies that were running around the time of the
depending on the error and on the level of ESTAE that abend. Any programs that perform input stack
receives control. In all cases, the TSO/E or REXX operations using the stack service routine
function is not performed. However, for a TSO/E CLIST should be examined for possible looping
or a REXX exec, a retry may be attempted following the conditions.
statement that encountered the error. In most cases, the
TSO/E READY mode will be reinstated. If the abend 31 Rerun the program in a TSO/E environment or
occurs during TSO/E logon, the user will need to logon address space.
again.
44 Obtain READ access from the owner of the
Code System Action dataset. The user cannot OPENFILE a dataset
marked EXECUTE-ONLY.
02 - 0B An SVC dump is not taken for the abend.
45 Obtain READ access from the owner of the
0D - 13 See the note at the beginning of the dataset. The user cannot submit a member
ABEND66D description section. An SVC dump from a dataset marked EXECUTE-ONLY.
is not taken for the abend.
46 Obtain READ access from the owner of the
14 - 19 An SVC dump is not taken for the abend. dataset. The user cannot run CLISTs from a
Application Programmer Response: Try rerunning dataset marked EXECUTE-ONLY.
the REXX exec or re-invoking the TSO/E function. The 47 See z/OS TSO/E Programming Services for
error may have been due to a temporary condition information on invoking the TSO/E environment
(such as insufficient storage), and your job may service. Correct the error and invoke the
succeed on a second attempt. TSO/E environment service again.
If the error is severe, the TSO/E session may need to 48 Make sure the installation has the proper
be restarted. version of TSO/E installed.
Code Response 49 Remove the TSO/E authorized command or
02 Check the validity of the I/O service parameter program that you tried to run.
list and the command processor parameter list 4B If you are using the IRXEXEC programming
(CPPL). Verify that the ECT address in both of service, provide a CPPL and retry the
these parameter lists is correct, that is, the operation.
ECT address supplied to a command
processor is in fact, in the CPPL. 4C Ensure that the TSO/E I/O services are
available in the address space.
05 Check the validity of the I/O service parameter
list and the command processor parameter list 4D Invalid record length found. One possible
(CPPL). Verify that the ECT address in both of reason is the concatenation of FB and VB data
these parameter lists is correct, that is, the sets being used for CLIST input.
ECT address supplied to a command
System programmer response: If no fix exists,
processor is in fact, in the CPPL.
contact the IBM Support Center.
06 Wait until the stack is created by the terminal
Source: Time Sharing Option Extensions (TSO/E)
Chapter 2. System Completion Codes 235
67D • 6C4
System action: The system abnormally terminates the
67D
task.
Explanation: During processing of an EVENTS macro,
the system found that the wait flag was already on in Note: If the NEWPASS keyword is not specified on the
the event control block (ECB). The flag on indicated that REQUEST=VERIFY, you can authorize the
a previous EVENTS or WAIT macro was already waiting calling module by entering it in the
for posting of the ECB. RACF-authorized caller table. However, IBM
does not recommend placing entries in the
System action: The system abnormally ends the
RACF-authorized caller table.
program that issued the EVENTS macro.
Application Programmer Response: Possible user
Application Programmer Response: Change the
error. Verify that the module is an authorized caller.
problem program to eliminate a double wait on a single
event. If no double wait is found, ensure that the ECB System programmer response: If the request
was not incorrectly modified by the program. Then run originated as a RACF command (that in turn resulted in
the job again. a call to the RACF manager or the REQUEST=LIST),
check to make sure the RACF command is in the list of
System programmer response: If the error recurs
APF-authorized commands for your system.
and the program is not in error, look at the messages in
the job log for more information. Search problem If the module making the request is an IBM routine, see
reporting data bases for a fix for the problem. If no fix z/OS Security Server RACF Diagnosis Guide for
exists, contact the IBM Support Center. Provide the information on diagnosing abends and reporting abend
program listing and the assembly listing associated with problems to IBM.
the job.
Source: Task management 685
Explanation: The module calling RACROUTE
683 REQUEST=DEFINE is not authorized (is not
APF-authorized, in system key 0-7, or in supervisor
Explanation: The module calling RACROUTE
state). To issue a REQUEST=DEFINE, the calling
REQUEST=VERIFY is not authorized (is not
module must be authorized (APF-authorized, in system
APF-authorized, in system key 0-7, or in supervisor
key 0-7, or in supervisor state).
state).
System action: The system abnormally terminates the
Note: If the NEWPASS keyword is not specified on the task.
REQUEST=VERIFY, you can authorize the
Application Programmer Response: Possible user
calling module by entering it in the
error. Verify that the calling module was executing in an
RACF-authorized caller table. However, IBM
authorized state.
does not recommend placing entries in the
RACF-authorized caller table. System programmer response: If the request
originated as a RACF command (that in turn resulted in
System action: The task is terminated.
the issuing of the REQUEST=DEFINE), check to make
Application Programmer Response: Possible user sure the RACF command is in the list of APF-authorized
error. Verify that the module is an authorized caller. commands for your system.
Problem determination: If the request originated as a If the module making the request is an IBM routine, see
RACF command (that in turn resulted in the issuing of z/OS Security Server RACF Diagnosis Guide for
the REQUEST=VERIFY), check to make sure the RACF information on diagnosing abends and reporting abend
command is in the list of APF-authorized commands for problems to IBM.
your system.
If the module making the request is an IBM routine, see 6C4
z/OS Security Server RACF Diagnosis Guide for
Explanation: The SOM® subsystem could not be
information on diagnosing abends and reporting abend
initialized because one of the following occurred:
problems to IBM.
v Another SOM subsystem is already active
v Another SOM subsystem ended without cleaning up
684
its resources.
Explanation: The module calling the RACF manager,
System action: The SOM subsystem subsystem is
or the RACROUTE REQUEST=LIST function, or the
not initialized. The system abnormally ends the
RACROUTE REQUEST=EXTRACT function is not
command. The system continues other processing.
authorized (is not APF-authorized, in system key 0-7, or
in supervisor state). System programmer response: Stop the DSOM
236 z/OS V1R10.0 MVS System Codes
6C4
subsystem that is active before starting this SOM Module: GOSAMCCP
subsystem. If the subsystem is already stopped and the
System Action: The system issues
problem persists, start the new SOM subsystem with
abend X'6C4' and ends the command
the same name as the SOM subsystem that previously
processing.
stopped. If the problem persists, contact the IBM
Support Center. For more information about starting and Programmer Response: Contact the
stopping a SOM subsystem, see OS/390 SOMobjects® system programmer.
Configuration and Administration Guide.
System Programmer Response:
A reason code further describes the error: Increase the amount of common
storage specified on the CSA
Code Explanation
parameter in IEASYSxx parmlib
000A1000 The activation of a logical unit failed member. ReIPL the system to activate
because the VTAM application for the the change. If the problem persists,
logical unit is not APPC-capable. contact the IBM Support Center.
Check the VTAM APPL statement for
02020003 An asynchronous cross memory post
the logical unit to ensure that you
failed. A DSOM command might have
specified APPC=YES.
been entered while the system was
System Action: The system also processing a command to stop the
issues abend X'EC7' with reason code SOM subsystem.
X'000A0037', which can be ignored.
Module: GOSAMCCP
000100xx An internal error occurred.
System Action: The system
System Action: The system abnormally ends the command.
continues processing, but the
Operator Response: Start DSOM
requested APPC/MVS service fails.
again. Once DSOM is started,enter
The system writes an SVC dump.
the DSOM command again.
010F0002 DSOM could not open the data control
System Programmer Response:
block (DCB) for the C runtime library
Restart the SOM subsystem. If the
for the SOM subsystem. The SOM
problem persists, contact the IBM
subsystem might not be installed
Support Center.
properly.
02080002 The system could not obtain common
Module: GOSAMCEE
storage.
System Action: The system ends the
Module: GOSAMCST
application.
System Action: The system
System Programmer Response:
abnormally ends the command.
Ensure that the SOM subsystem is
properly installed. Ensure that the System Programmer Response:
GOSRTL1 data sets are correct and Increase the amount of common
accessible to the userid associated storage specified on the CSA
with the SOM subsystem. If the parameter in IEASYSxx parmlib
problem persists, contact the IBM member. ReIPL the system to activate
Support Center. the change. If the problem persists,
contact the IBM Support Center.
02020001 The caller of a service is not in
supervisor state. 02080003 An asynchronous cross memory post
failed. A DSOM command might have
Module: GOSAMCCP
been entered while the system was
System Action: The application is processing a STOP DSOM command.
abnormally ended.
Module: GOSAMCST
System Programmer Response:
System Action: The system
Verify that the application is using
abnormally ends the command.
standard interfaces. If the problem
persists, contact the IBM Support Operator Response: Enter a START
Center. DSOM command to start DSOM
again.
02020002 Common area storage could not be
obtained.
Chapter 2. System Completion Codes 237
6C4
System Programmer Response: If command to start the server. If the
the problem persists, contact the IBM problem persists, contact the IBM
Support Center. Support Center.
05000001 Unsupported DSOM subsystem 05020007 The caller of a service is not valid.
service.
Module: GOSAPTRC
Module: GOSAPBAD
System Action: The system
System Action: The system abnormally ends the application.
abnormally ends the application.
System Programmer Response:
User Response: Contact the system Verify that the application is using
programmer. standard interfaces. If the problem
persists, contact the IBM Support
System Programmer Response:
Center.
Verify that the application is using
standard interfaces. If the problem 05030001 Input to a service routine is missing.
persists, contact the IBM Support The caller of the service is not valid.
Center.
Module: GOSAPRC1
05010001 Input to a service routine is missing.
System Action: The system
The caller of the service is not valid.
abnormally ends the application.
save
System Programmer Response:
Module: GOSAPASC
Verify that the application is using
System Action: The system standard interfaces. If the problem
abnormally ends the application. persists, contact the IBM Support
Center.
System Programmer Response:
Verify that the application is using 05030003 The caller passed a parameter list that
standard interfaces. If the problem is not valid.
persists, contact the IBM Support
Module: GOSAPRC1
Center.
System Action: The system
05010002 The caller of a DSOM service is not
abnormally ends the application.
valid.
System Programmer Response:
Module: GOSAPASC
Verify that the application is using
System Action: The system standard interfaces. If the problem
abnormally ends the application. persists, contact the IBM Support
Center.
System Programmer Response:
Verify that the application is using 05030004 The caller requested a security
standard interfaces. If the problem function that is not valid. The caller of
persists, contact the IBM Support the service is not valid.
Center.
Module: GOSAPRC1
05010003 The system could not create a server
System Action: The system
address space.
abnormally ends the application.
Module: GOSAPASC
System Programmer Response:
System Action: The system records Verify that the application is using
the error and continues processing. standard interfaces. If the problem
The system does not start the server. persists, contact the IBM Support
Center.
System Programmer Response:
Obtain the return code from the 0503000A The caller is not authorized to invoke
ASCRE macro in register 0. Verify that the requested function. The caller of
the server PROC is defined correctly. the service is not valid.
See the section on using a JCL
Module: GOSAPRC1
procedure to start a DSOM server in
OS/390 SOMobjects Configuration System Action: The system
and Administration Guide for more abnormally ends the application.
information. Enter the START
238 z/OS V1R10.0 MVS System Codes
6C4
System Programmer Response: 05040004 Function requested from service
Verify that the application is using routine is not valid. The caller of the
standard interfaces. If the problem service is not valid.
persists, contact the IBM Support
Module: GOSAPRC2
Center.
System Action: The system
05030109 The system could not process a
abnormally ends the application.
RACROUTE REQUEST=AUTH
request when checking command System Programmer Response:
authorization to a server. Verify that the application is using
standard interfaces. If the problem
Module: GOSAPRC1
persists, contact the IBM Support
System Action: The system Center.
abnormally ends the application.
0504000A The caller is not authorized to invoke
System Programmer Response: the requested function. The caller of a
Verify that the application is using service is not valid.
standard interfaces. If the problem
Module: GOSAPRC2
persists, contact the IBM Support
Center. System Action: The system
abnormally ends the application.
0503000B A PC routine is not available.
System Programmer Response:
Module: GOSAGCRT, GOSAGCAU
Verify that the application is using
System Action: The system issues standard interfaces. If the problem
abend X'6C4' to the caller of the persists, contact the IBM Support
DSOM service. The system might Center.
issue message GOS009I.
0504000B SOM subsystem services not
Operator Response: Enter a START available.
DSOM command to start DSOM
Module: GOSACACE, GOSACACE,
again. If DSOM is already started and
GOSACAUT, GOSADACE,
the system issued message GOS009I,
GOSAGRTO, GOSAMAUT,
contact the system programmer.
GOSASAUT, GOSASECI,
System Programmer Response: If GOSASECU
you cannot start DSOM, contact the
System Action: The system issues
IBM Support Center.
abend X'6C4' to the caller of the
05040001 Input to service routine missing. The DSOM service. The system might
caller of the service is not valid. issue message GOS009I.
Module: GOSAPRC2 Operator Response: Enter a START
DSOM command to start DSOM
System Action: The system
again. If DSOM is already started and
abnormally ends the application.
the system issued message GOS009I,
System Programmer Response: contact the system programmer.
Verify that the application is using
System Programmer Response: If
standard interfaces. If the problem
you cannot start DSOM, contact the
persists, contact the IBM Support
IBM Support Center.
Center.
05040100 During security initialization, the
05040003 The parameter list that was passed to
system could not process a
a service routine is not valid because
RACROUTE
the caller of the service is not valid.
REQUEST=LIST,ENVIR=CREATE
Module: GOSAPRC2 request for the SOMDOBJS RACF
security class.
System Action: The system
abnormally ends the application. Module: GOSAPRC2
System Programmer Response: System Action: The system
Verify that the application is using abnormally ends the application.
standard interfaces. If the problem
System Programmer Response:
persists, contact the IBM Support
Register 0 contains diagnostic
Center.
Chapter 2. System Completion Codes 239
6C4
information in the form X'00wwyyzz', where X'ww' is the SAF return code,
where X'ww' is the SAF return code, X'yy' is the RACF return code, and
X'yy' is the RACF return code, and X'zz' is the RACF reason code. See
X'zz' is the RACF reason code. See z/OS Security Server RACROUTE
z/OS Security Server RACROUTE Macro Reference for a description of
Macro Reference for a description of the return and reason codes from
the return and reason codes from RACROUTE.
RACROUTE.
05040104 During client authentication or
05040101 During security initialization, the client/server disconnect, the system
system could not process a could not process a RACROUTE
RACROUTE REQUEST=VERIFY ENVIR=DELETE
REQUEST=LIST,ENVIR=CREATE request.
request for the CBIND RACF security
Module: GOSAPRC2
class.
System Action: The system
Module: GOSAPRC2
abnormally ends the application.
System Action: The system
System Programmer Response:
abnormally ends the application.
Register 0 contains diagnostic
System Programmer Response: information in the form X'00wwyyzz',
Register 0 contains diagnostic where X'ww' is the SAF return code,
information in the form X'00wwyyzz', X'yy' is the RACF return code, and
where X'ww' is the SAF return code, X'zz' is the RACF reason code. See
X'yy' is the RACF return code, and z/OS Security Server RACROUTE
X'zz' is the RACF reason code. See Macro Reference for a description of
z/OS Security Server RACROUTE the return and reason codes from
Macro Reference for a description of RACROUTE.
the return and reason codes from
05040105 During security cleanup processing,
RACROUTE.
the system could not process a
05040102 During client authentication, the RACROUTE REQUEST=LIST
system could not process a ENVIR=DELETE request.
RACROUTE
Module: GOSAPRC2
REQUEST=LIST,ENVIR=CREATE
request. System Action: The system
abnormally ends the application.
Module: GOSAPRC2
System Programmer Response:
System Action: The system
Register 0 contains diagnostic
abnormally ends the application.
information in the form X'00wwyyzz',
System Programmer Response: where X'ww' is the SAF return code,
Register 0 contains diagnostic X'yy' is the RACF return code, and
information in the form X'00wwyyzz', X'zz' is the RACF reason code. See
where X'ww' is the SAF return code, z/OS Security Server RACROUTE
X'yy' is the RACF return code, and Macro Reference for a description of
X'zz' is the RACF reason code. See the return and reason codes from
z/OS Security Server RACROUTE RACROUTE.
Macro Reference for a description of
05040106 During security cleanup processing,
the return and reason codes from
the system could not process a
RACROUTE.
RACROUTE REQUEST=LIST
05040103 During client authentication, the ENVIR=DELETE request for the
system could not process a CBIND RACF security class.
RACROUTE REQUEST=FASTAUTH
Module: GOSAPRC2
request.
System Action: The system
Module: GOSAPRC2
abnormally ends the application.
System Action: The system
System Programmer Response:
abnormally ends the application.
Register 0 contains diagnostic
System Programmer Response: information in the form X'00wwyyzz',
Register 0 contains diagnostic where X'ww' is the SAF return code,
information in the form X'00wwyyzz', X'yy' is the RACF return code, and
240 z/OS V1R10.0 MVS System Codes
6C4
X'zz' is the RACF reason code. See Macro Reference for a description of
z/OS Security Server RACROUTE the return and reason codes from
Macro Reference for a description of RACROUTE.
the return and reason codes from
0504010A During server authorization or client
RACROUTE.
authentication processing, the system
05040107 During client/server connect could not process a RACROUTE
processing, the system could not REQUEST=EXTRACT,TYPE=
process a RACROUTE ENCRYPT request.
REQUEST=LIST REQUEST=VERIFY
Module: GOSAPRC2
ENVIR=CREATE PASSCHK=NO
request. System Action: The system
abnormally ends the application.
Module: GOSAPRC2
System Programmer Response:
System Action: The system
Register 0 contains diagnostic
abnormally ends the application.
information in the form X'00wwyyzz',
System Programmer Response: where X'ww' is the SAF return code,
Register 0 contains diagnostic X'yy' is the RACF return code, and
information in the form X'00wwyyzz', X'zz' is the RACF reason code. See
where X'ww' is the SAF return code, z/OS Security Server RACROUTE
X'yy' is the RACF return code, and Macro Reference for a description of
X'zz' is the RACF reason code. See the return and reason codes from
z/OS Security Server RACROUTE RACROUTE.
Macro Reference for a description of
0504010B During method level authorization
the return and reason codes from
processing, a bad parameter was
RACROUTE.
passed to the service. The caller of
05040108 During method level authorization the service is not valid.
processing, the system could not
Module: GOSAPRC2
process a RACROUTE
REQUEST=FASTAUTH request. System Action: The system
abnormally ends the application.
Module: GOSAPRC2
System Programmer Response:
System Action: The system
Register 0 contains diagnostic
abnormally ends the application.
information in the form X'00wwyyzz',
System Programmer Response: where X'ww' is the SAF return code,
Register 0 contains diagnostic X'yy' is the RACF return code, and
information in the form X'00wwyyzz', X'zz' is the RACF reason code. See
where X'ww' is the SAF return code, z/OS Security Server RACROUTE
X'yy' is the RACF return code, and Macro Reference for a description of
X'zz' is the RACF reason code. See the return and reason codes from
z/OS Security Server RACROUTE RACROUTE.
Macro Reference for a description of
0507000A The caller is not authorized to invoke
the return and reason codes from
the requested function. The caller of
RACROUTE.
the service is not valid.
05040109 During server authorization
Module: GOSAPRST
processing, the system could not
process a RACROUTE System Action: The system
REQUEST=AUTH request. abnormally ends the application.
Module: GOSAPRC2 System Programmer Response:
Verify that the application is using
System Action: The system
standard interfaces. If the problem
abnormally ends the application.
persists, contact the IBM Support
System Programmer Response: Center.
Register 0 contains diagnostic
050B0001 Input to a service routine is missing.
information in the form X'00wwyyzz',
The caller of the service is not valid.
where X'ww' is the SAF return code,
X'yy' is the RACF return code, and Module: GOSAPIOK
X'zz' is the RACF reason code. See
z/OS Security Server RACROUTE
Chapter 2. System Completion Codes 241
6C5
System Action: The system System Action: The system
abnormally ends the application. abnormally ends the application.
System Programmer Response: System Programmer Response:
Verify that the application is using Obtain the return code from the latch
standard interfaces. If the problem obtain service (ISGLCRT) in register
persists, contact the IBM Support zero. See z/OS MVS Programming:
Center. Authorized Assembler Services
Reference EDT-IXG for descriptions of
050B0002 The caller of a DSOM service is not
return codes from ISGLCRT.
valid.
050C0006 Unable to obtain DSOM latch
Module: GOSAPIOK
Module: GOSAPSER
System Action: The system
abnormally ends the application. System Action: The system
abnormally ends the application.
System Programmer Response:
Verify that the application is using System Programmer Response:
standard interfaces. If the problem Obtain the return code from the latch
persists, contact the IBM Support obtain service (ISGLOBT) in register
Center. zero. See z/OS MVS Programming:
Authorized Assembler Services
050C0001 Input to service routine missing. The
Reference EDT-IXG for descriptions of
caller of the service is not valid.
return codes from ISGLOBT.
Module: GOSAPSER
050C0007 Unable to release DSOM latch
System Action: The system
Module: GOSAPSER
abnormally ends the application.
System Action: The system
System Programmer Response:
abnormally ends the application.
Verify that the application is using
standard interfaces. If the problem System Programmer Response:
persists, contact the IBM Support Obtain the return code from the latch
Center. release service (ISGLREL) in register
zero. See z/OS MVS Programming:
050C0003 The parameter list that was passed to
Authorized Assembler Services
a service routine is not valid because
Reference EDT-IXG for descriptions of
the caller of the service is not valid.
return codes from ISGLREL.
Module: GOSAPSER
Source: GOSAMISP
System Action: The system
abnormally ends the application.
6C5
System Programmer Response:
Explanation: During processing of an IARVSERV
Verify that the application is using
macro, the system found a non-environmental error. The
standard interfaces. If the problem
macro processing failed. Register 15 contains one of
persists, contact the IBM Support
the following hexadecimal reason codes.
Center.
Code Explanation
050C0004 Function requested from service
routine is not valid. The caller of the xx0120xx For a SHARE request, the STOKEN
service is not valid. for the source area does not represent
a valid data space token.
Module: GOSAPSER
xx0121xx For a SHARE request, the STOKEN
System Action: The system
for the target area does not represent
abnormally ends the application.
a valid data space token.
System Programmer Response:
xx0122xx For a SHARE request, the beginning
Verify that the application is using
address of the source area specified
standard interfaces. If the problem
in the range list entry is not
persists, contact the IBM Support
page-boundary aligned.
Center.
xx0123xx For a SHARE request, the beginning
050C0005 Unable to create DSOM latch
address of the target area specified in
Module: GOSAPSER
242 z/OS V1R10.0 MVS System Codes
6C5
the range list entry is not contains unacceptable pages, such as
page-boundary aligned. pages that are page-protected or
page-fixed.
xx0124xx For a SHARE request, the source and
target areas are not different. xx0132xx For a SHARE request, the source and
the target areas do not meet the
xx0125xx For a SHARE request, specified
storage attribute requirements for
storage has not been obtained with
sharing.
GETMAIN macro or STORAGE macro
with the OBTAIN parameter as part of xx0133xx For a SHARE request, READONLY
the pageable private region of the sharing pages cannot be made
caller’s address space, nor within the shared with SHAREDWRITE.
size of an existing data space as
xx0134xx For a SHARE request, the source
pageable storage.
area contains pages that are shared
xx0126xx For a SHARE request, the caller does with a target view of TARGETWRITE.
not have legal access to the source
xx0135xx For a SHARE request, the source
area with the given ALET.
area contains pages that are currently
xx0127xx For a SHARE request, the caller does to a hiperspace object through the
not have legal access to the source DIV macro.
area with the given STOKEN.
xx0136xx For a SHARE request, the target area
xx0128xx For a SHARE request, the caller does contains pages that are currently
not have legal access to the target mapped through the DIV macro.
area with the given ALET.
xx0137xx For a SHARE request, part of the
xx0129xx For a SHARE request, the caller does source area is in a hiperspace, VIO
not have legal access to the target window, V=R region, or PSA.
area with the given STOKEN.
xx0138xx For a SHARE request, part of the
xx012Axx For a SHARE request, the address target area is in a hiperspace, VIO
space that owns the source is not window, V=R region, or PSA.
swapped in.
xx0139xx For a SHARE request, the number of
xx012Bxx For a SHARE request, the address pages specified in a range list entry is
space that owns the target is not not valid.
swapped in.
xx013Axx For a SHARE request, the specified
xx012Cxx For a SHARE request, the caller’s source ALET represents a subspace.
PSW key is insufficient for altering the
xx013Bxx For a SHARE request, the specified
target area.
target ALET represents a subspace.
xx012Dxx For a SHARE request, the
xx013Dxx For a SHARE request, the specified
TARGET_VIEW(SHAREDWRITE)
target storage was not obtained by
option is specified but the caller’s
the GETMAIN macro or STORAGE
PSW key is insufficient for altering the
macro with the OBTAIN parameter as
source area.
part of the caller’s pageable private
xx012Exx For a SHARE request, one page in region, or within the size of an existing
the source area and its corresponding data space as pageable storage.
page in the target area do not have
xx013Exx For a SHARE request, the specified
the same storage protect key and
source ALET is not valid. It is not on
fetch-protection status.
the current access list.
xx012Fxx For a SHARE request, the source
xx013Fxx For a SHARE request, the specified
area is not acceptable because it
target ALET is not valid. It is not on
contains system data that is not
the current access list.
eligible for sharing.
xx0140xx For a SHARE request, the source
xx0130xx For a SHARE request, the target area
area contains HIDDEN pages.
is not acceptable because it contains
system data that should not be altered xx0141xx IARVSERV-SHARE failed. The source
by the caller. page is part of a shared segment.
xx0131xx For a SHARE request, the target area xx0142xx IARVSERV-SHARE failed. The target
page is part of a shared segment.
Chapter 2. System Completion Codes 243
6C5
xx0221xx For an UNSHARE request, the caller does not have access to the
STOKEN for the target area does not target area with the given ALET.
represent a valid data space
xx0329xx For a CHANGEACCESS request, the
STOKEN.
caller does not have access to the
xx0223xx For an UNSHARE request, the target area with the given STOKEN.
beginning address of the target area
xx032Bxx For a CHANGEACCESS request, the
specified in the range list entry is not
address space that owns the target
page-boundary aligned.
area is not swapped in.
xx0225xx For an UNSHARE request, the
xx032Cxx For a CHANGEACCESS request, the
specified storage has not been
caller’s PSW key is insufficient for
obtained with GETMAIN macro or
altering the target area.
STORAGE macro with the OBTAIN
parameter as part of the pageable xx0330xx For a CHANGEACCESS request, the
private region of the caller’s address target area contains unacceptable
space, or within an existing data pages, such as pages that are fixed
space. by PGSER or in permanent storage.
xx0228xx For an UNSHARE request, the caller xx0331xx For a CHANGEACCESS request, the
does not have valid access to the target area is not acceptable because
address of the target area with the it contains data that the caller should
given ALET. not alter.
xx0229xx For an UNSHARE request, the caller xx0338xx For a CHANGEACCESS request, part
does not have valid access to the of the target area is in a hiperspace
address of the target area with the window, a VIO window or V=R region,
given STOKEN. or in a PSA.
xx022Bxx For an UNSHARE request, the xx0339xx For a CHANGEACCESS request, the
address space that owns the target is number of pages specified in a range
not swapped in. list is not valid.
xx022Cxx For an UNSHARE request, the caller’s xx033Bxx For a CHANGEACCESS request, the
PSW key is insufficient for altering the specified target ALET represents a
target area. subspace.
xx0231xx For an UNSHARE request, the target xx033Dxx For a CHANGEACCESS request, the
area contains unacceptable pages, storage was not obtained using the
such as pages that are GETMAIN or STORAGE OBTAIN
page-protected or page-fixed pages. macro as part of the pageable private
region of the caller’s address space,
xx0238xx For an UNSHARE request, part of the
nor within any existing data space.
target area is in a Hiperspace, VIO
window, V=R region, or PSA. xx033Fxx For a CHANGEACCESS request, the
specified target ALET is not valid.
xx0239xx For an UNSHARE request, the
number of pages specified in a range xx04xxxx For a xx04xxxx reason code please
list entry is not valid. contact the IBM service center.
xx023Bxx For an UNSHARE request, the xxFF10xx The caller held a lock other than the
specified target ALET represents a local lock.
subspace.
xxFF11xx The input parameter list or range list
xx023Fxx For an UNSHARE request, the is not accessible to the service using
specified target ALET is not valid. the caller’s PSW key.
xx0321xx For a CHANGEACCESS request, the xxFF12xx The caller issued a macro version that
STOKEN for the target area does not is not valid.
represent a valid space STOKEN.
xxFF13xx Reserved fields in the caller’s macro
xx0323xx For a CHANGEACCESS request, the parameter list are not zeros.
beginning address of the target area
specified in the range is not aligned xxFF14xx The caller requested a service that is
on a page-boundary. not valid.
xx0328xx For a CHANGEACCESS request, the xxFF15xx The caller is not in 31-bit addressing
mode.
244 z/OS V1R10.0 MVS System Codes
6C6 • 6C7
xxFF16xx The range list entry count message and the one found in the MVS operator
(NUMRANGE) is less than one or message will be the same.
greater than 16.
System programmer response: If the error recurs
System action: The system sends messages about and the program is not in error, look at the messages in
the job to the job log, writes an ABEND dump for the the job log for more information. Search problem
failing job step, and writes the JCL and SYSOUT output reporting data bases for a fix for the problem. If no fix
for the job. exists, contact the IBM Support Center. Provide the
SYSOUT output for the job and the logrec data set error
Application Programmer Response: Correct the
record.
program and run the job again.
Source: MQSeries
System programmer response: If the caller was
provided by the installation, correct it. Look at
accompanying messages in the job log, the JCL and the 6C7
SYSOUT output.
Explanation: During processing of a REFPAT macro,
If the caller was an IBM-supplied program, search the system found a non-environmental error. The macro
problem reporting data bases for a fix for the problem. If processing failed. Register 15 contains a hexadecimal
no fix exists, contact the IBM Support Center. Provide reason code.
the messages, the JCL, the SYSOUT output, and the
Code Explanation
ABEND dump.
xx0005xx The INSTALL request failed because
Source: Real storage manager (RSM)
the caller does not own the specified
data space.
6C6
xx0006xx The INSTALL request failed because
Explanation: To avoid data integrity problems, the the caller specified a data space that
subsystem abnormally ends; one or more X'5C6' system does not exist.
completion codes will usually precede the end. During
xx0102xx The REMOVE request failed because
MQSeries abend, a user task with an active MQSeries
the caller does not own the specified
connection can be abended with a X'6C6' system
data space.
completion code; in rare instances, the entire connected
address will be abended (MEMTERM). However, if the xx0103xx The REMOVE request failed because
subsystem ends an address space after numerous the caller specified a data space that
cancel attempts, this is not an MQSeries internal error. does not exist.
System action: The subsystem abnormally ends xxFF01xx The REFPAT macro request failed
MQSeries. because the caller was in
cross-memory mode.
Operator response: Message CSQV086E should
appear on your console screen. First, copy this xxFF02xx The REFPAT macro request failed
message and the accompanying subsystem end reason because the caller held one or more
code. Second, notify the system programmer. locks needed by the system to
process the request.
Application Programmer Response: If the
subsystem abnormally ends MQSeries, then record the xxFF03xx The REFPAT macro request failed
subsystem end reason code that is displayed in because a protection exception
message CSQV086E. In addition, you should be aware occurred while referencing the caller’s
of the following situations. parameter list.
1. If you received any X'5C6' system completion codes xxFF04xx The REFPAT macro request failed
prior to this subsystem end, perform the following because reserved fields in the macro
actions. Check register 15 of the SDWA section parameter list are not zeros.
’General Purpose Registers at Time of Error’, and
locate the accompanying reason code. In addition, xxFF05xx The REFPAT macro request failed
check the information displayed at the console because the caller requested an
screen, and in the corresponding logrec data set unknown service.
entry.
xxFF06xx The REFPAT macro request failed
2. If you did not receive any X'5C6' system completion because the caller must be in 31-bit
codes prior to the subsystem end, you will need an addressing mode to use any service
SVC dump, which is entitled ″MQSERIES of the REFPAT macro.
SUBSYSTEM TERMINATION REQUESTED -
REASON=xxxxxxxx″. The reason code in the
Chapter 2. System Completion Codes 245
6FB
xxFF07xx The REFPAT macro request failed 23 The common area data space (CADS) buffer,
because the caller cannot be in SRB provided as input to the JES3 SRB reply exit
mode. routine (SSRECRXT) in module IATSSRE,
contained a bad JESXCF acknowledgement
xxFF08xx The REFPAT macro request failed
message. The eye-catcher for the JESXCF
because the virtual storage addresses
acknowledgement message was not correct.
specified on PSTART and PEND
straddle a common area boundary. 24 The CADS buffer, provided as input to the
JES3 SRB reply exit routine (SSRECRXT) in
System action: The system sends messages about
module IATSSRE, contained a bad staging
the job to the job log, writes an ABEND dump for the
area header. The eye-catcher for the staging
failing job step, and writes the JCL and SYSOUT output
area header was not correct.
for the job.
25 The CADS buffer prefix, provided as input to
Application Programmer Response: If the caller was
the JES3 SRB reply exit routine (SSRECRXT)
an application program, correct the program and run the
in module IATSSRE, contained a bad response
job again.
exit address. The response exit address must
System programmer response: If the caller was be non-zero.
provided by the installation, correct it. Look at
26 The CADS buffer prefix, provided as input to
accompanying messages in the job log, the JCL and the
the JES3 SRB reply exit routine (SSRECRXT)
SYSOUT output.
in module IATSSRE, contained an incorrect
If the caller was an IBM-supplied program, search buffer length. The buffer length must be
problem reporting data bases for a fix for the problem. If non-zero.
no fix exists, contact the IBM Support Center. Provide
27 The JESXCF Acknowledgement Message,
the messages, the JCL, the SYSOUT output, and the
passed as input within the CADS buffer to the
ABEND dump.
JES3 SRB reply exit routine (SSRECRXT) in
Source: Real storage manager (RSM) module IATSSRE, contained a bad user return
code. The user return code was non-zero.
6FB 28 The JES3 SRB reply exit routine (SSRECRXT)
within module IATSSRE attempted to obtain
Explanation: storage for the staging area buffer using the
STORAGE service. The attempt was
unsuccessful and a non-zero return code was
JES3 4.2.1 or prior level returned from the STORAGE service.
If you are at JES3 4.2.1 or a prior level of JES3,
the following information applies: 31 The JES3 global status routine (SSRESTAT) in
module IATSSRE invoked the IXZXIXIF service
to obtain JES3 complex status information. The
During JES3 processing, module IATSSCM, IATSSRN buffer returned by the service contains a bad
or IATSSRE detected an error related to the subsystem JESXCF member information record. The
interface and issued this system completion code. The eye-catcher was not correct.
error is identified by a hexadecimal reason code in
32 The JES3 global status routine (SSRESTAT) in
register 15.
module IATSSRE was unable to find the global
Code Explanation MPC entry within the main processor control
table.
10 IATSSRN - Module IATSSRN received a bad
return code from the JESXCF message reroute 33 The JES3 global status routine (SSRESTAT) in
service (IXZXIXRR). module IATSSRE attempted to obtain storage
v Register 3 - Return Code from IXZXIXRR for the JESXCF Information Record buffer
service (IXZXIXIF) via the STORAGE service. The
attempt was unsuccessful and a non-zero
v Register 4 - Reason Code from IXZXIXRR return code was returned from the STORAGE
service service.
21 A bad SRB address was passed as input to 34 The JES3 global status routine (SSRESTAT) in
the JES3 SRB reply exit routine (SSRECRXT) module IATSSRE invoked the IXZXIXIF service
in module IATSSRE. to obtain JES3 complex status information. The
22 A bad service request block (SRB) extension service was unsuccessful and provided the
address was passed as input to the JES3 SRB SSRESTAT routine with a bad return and/or
reply exit routine (SSRECRXT) in module reason code.
IATSSRE. v Register 3 - Return Code
246 z/OS V1R10.0 MVS System Codes
6FB
v Register 4 - Reason Code unsuccessful and a non-zero return code was
returned from the STORAGE service.
35 The JES3 global status routine (SSRESTAT) in
module IATSSRE invoked the IXZXIXIF service v Register 2 - Return Code from STORAGE
to obtain JES3 complex status information. The service
JESXCF Information Records returned by the 107 Module IATSSCM attempted to create a
service did not contain any information for the TTOKEN for the current task using the
global processor. TCBTOKEN service while processing an
100 Module IATSSCM encountered a JES3 SSISERV TYPE=REPLY request. The attempt
subsystem communications service entrance was unsuccessful and a non-zero return code
list (SEL) which was already in use by another was returned from the TCBTOKEN service.
caller. v Register 2 - Return Code from TCBTOKEN
service
101 Module IATSSCM determined the caller was
not authorized to issue the SSISERV service. 111 Module IATSSCM attempted to release storage
it had obtained for a memory data block
102 Module IATSSCM encountered a bad memory
(IATYMEM) using the STORAGE service. The
data block (MEMDATA) pointer. The
attempt was unsuccessful and a non-zero
eye-catcher for the MEMDATA header was not
return code was returned from the STORAGE
correct.
service.
103 The JES3 subsystem communications service v Register 2 - Return Code from STORAGE
entrance list (SEL) passed into module service
IATSSCM had an incorrect length. This could
be a result of a zero SELDATA pointer or a 112 Module IATSSCM attempted to obtain a CADS
length of zero or a length exceeding the buffer using the JESXCF IXZXCADS service.
maximum staging area data size. This applies The attempt was unsuccessful and a non-zero
to all SSISERV service requests except return code was returned from the IXZXCADS
TYPE=RESPONSE request. service.
v Register 2 - Return Code from IXZXCADS
104 Module IATSSCM encountered bad parameters
service
specified for an SSISERV TYPE=WAIT
request. One of the following problems was v Register 3 - Reason Code from IXZXCADS
found with the parameters: service
v A response buffer was not specified. A 113 Module IATSSCM attempted to release a
response buffer is required for SSISERV CADS buffer using the JESXCF IXZXCADS
TYPE=WAIT. service. The attempt was unsuccessful and a
v An EXIT address was specified. An exit non-zero return code was returned from the
address must not be specified for SSISERV IXZXCADS service.
TYPE=WAIT. v Register 2 - Return Code from IXZXCADS
service
105 Module IATSSCM encountered bad parameters
specified for an SSISERV TYPE=REPLY v Register 3 - Reason Code from IXZXCADS
request. One of the following problems was service
found with the parameters: 120 Module IATSSCM received a bad return code
v Both the ECB and EXIT address were from the JESXCF acknowledge processed
specified. Only one of these parameters can message service (IXZXIXAC) while processing
be specified. an SSISERV TYPE=PURGE request.
v A response buffer address was not specified v Register 2 - Return Code from IXZXIXAC
for a request that did not specify an EXIT service
address. If a response buffer address is not v Register 3 - Reason Code from IXZXIXAC
specified, an EXIT address must be service
specified.
121 Module IATSSCM received a bad return code
106 Module IATSSCM was unable to find an entry from the JESXCF send message service
in the Main Processor Control table for the (IXZXIXSM) while processing an SSISERV
JESXCF member that is to receive this TYPE=WAIT request.
request.
v Register 2 - Return Code from IXZXIXSM
110 Module IATSSCM attempted to obtain storage service
for a memory data block (IATYMEM) using the v Register 3 - Reason Code from IXZXIXSM
STORAGE service. The attempt was service
Chapter 2. System Completion Codes 247
6FB
122 Module IATSSCM received a non-zero user System action: The system writes the current address
return code from the response to a JESXCF space along with the JES3 and JESXCF address
send message service (IXZXIXSM) request spaces and related storage areas to a SYS1.DUMP
while processing an SSISERV TYPE=WAIT data set. If the current address space is not the JES3
request. address space, the system abnormally ends the current
address space.
123 Module IATSSCM received a bad return code
from the JESXCF acknowledge processed System programmer response: Search problem
message service (IXZXIXAC) while processing reporting data bases for a fix for the problem. If no fix
an SSISERV TYPE=WAIT request. exists and the problem occurred in JES3, you should:
v Register 2 - Return Code from IXZXIXAC v Save the hardcopy log
service v Provide a listing of the initialization deck (JES3OUT)
v Provide a console log from initialization
v Register 3 - Reason Code from IXZXIXAC
v Check the JESYSMSG data set for error indications
service
124 Module IATSSCM received a bad return code After gathering the necessary data, contact the IBM
from the JESXCF send message service Support Center. If an SVC dump was taken, provide the
(IXZXIXSM) while processing an SSISERV SVC dump, the reason code, and, if available, the data
TYPE=REPLY request. set error record.
v Register 2 - Return Code from IXZXIXSM
service
JES3 4.2.1 or prior level
v Register 3 - Reason Code from IXZXIXSM
If you are at JES3 4.2.1 or a prior level of JES3,
service
the following information applies:
125 Module IATSSCM received a bad return code
from the JESXCF send message service Explanation: During JES3 processing, module
(IXZXIXSM) while processing an SSISERV IATSSCM or IATSSRE detected an error and issued this
TYPE=ACK request. system completion code. The error is identified by a
v Register 2 - Return Code from IXZXIXSM hexadecimal reason code in the high-order byte of
service register 15 and, for some reason codes, a hexadecimal
v Register 3 - Reason Code from IXZXIXSM return code in the low-order byte of register 15.
service Code Explanation
126 Module IATSSCM received a bad return code 00 The subsystem interface common service
from the JESXCF send message service (SSICS) routine detected an error in its calling
(IXZXIXSM) while processing an SSISERV parameters or in the system status. Return
TYPE=COMM request. codes are:
v Register 2 - Return Code from IXZXIXSM
service X'18' The caller of SSICS is not in system
protection key 0 through 7.
v Register 3 - Reason Code from IXZXIXSM
service X'1C' The SYSID parameter in a SSISERV
macro specified a processor that is
127 Module IATSSCM received a bad return code not defined.
from the JESXCF acknowledge processed
message service (IXZXIXAC) while processing X'20' An incorrect combination of the fields
an SSISERV TYPE=RESP request. SELECBF, SELEXIT, SELBUFF was
v Register 2 - Return Code from IXZXIXAC found in the IATYSEL control block for
service a WAIT or REPLY type SSISERV
macro request.
v Register 3 - Reason Code from IXZXIXAC
service X'24' An error occurred when the SSICS
routine attempted to write a staging
128 Module IATSSCM received a zero response area.
data address from the JESXCF send message
service (IXZXIXSM) while processing an X'28' The primary and all secondary staging
SSISERV TYPE=WAIT request. area extents have been exhausted.
v Register 2 - Return Code from IXZXIXSM X'2C' The service entrance list (SEL)
service contained an incorrect MEMDATA
v Register 3 - Reason Code from IXZXIXSM pointer.
service
X'30' The channel-to-channel (CTC) adaptor
Source: JES3 address is incorrect.
248 z/OS V1R10.0 MVS System Codes
6FB
X'34' An attempt was made to post a wait call a specific routine in module IATSSXM.
that cannot be posted. IATSSXM returns in the low-order byte of
register 15 the ECODE parameter value from
01 The IATXBGM or IATXBFM macro passed an
the IATXSSXM macro. z/OS JES3
error return code back to JES3 module
Customization describes the IATXSSXM
IATSSCM:
macro.
X'08' A GETMAIN or FREEMAIN failed.
13 The system abnormally ended JES3 during
02 The MVS FREECELL macro passed an error staging area initialization.
return code back to JES3 module IATSSCM:
14 The system abnormally ended JES3 during
X'04' The cell was not allocated from the processing to move a staging area to make it a
subpool indicated by the specified cell dedicated staging area.
pool identifier.
15 The system abnormally ended the processing
X'08' The cell address is incorrect. following an end of memory (EOM) or an end
of task (EOT) call.
X'0C' FREECELL could not find the cell
pool. 16 The system abnormally ended FREEMAIN
processing of the staging area wait queue
X'10' The cell pool identifier is incorrect. (SAW Q).
03 The MVS BLDCPOOL macro passed an error 17 The system abnormally ended FREEMAIN
return code back to JES3 module IATSSCM: processing of the staging area pending queue
X'04' GETMAIN failed. (SAP Q).
X'08' The cell pool identifier is incorrect. 18 The system abnormally ended an attempt to
page-fix the staging area pending queue (SAP
X'0C' The specified subpool was not global. Q).
X'10' The cell size was greater than the 19 The system abnormally ended copying of the
pool size. staging area pending queue (SAP Q) from
X'14' BLDCPOOL found a DELETE subpool JES3 auxiliary storage to the common service
in progress for the specified pool. area (CSA).
04 The MVS GETCELL macro passed an error 1A Module IATSSCM detected an error, which
return code back to JES3 module IATSSCM: may have caused another ABEND, during
GETCELL processing for JES3 auxiliary
X'04' GETCELL could not find any available storage.
cells.
1B Module IATSSCM detected an error during
X'08' The chain pointers had been validation of a staging area queue.
destroyed.
40 Module IATSSRE detected an error:
X'0C' The cell pool format was incorrect.
X'04' The passed staging area was not
X'10' The cell pool identifier is incorrect. found on the staging area pending
05 The JES3 subsystem interface read-end (SAP) queue.
module IATSSRE failed to obtain storage; the X'08' IATSSRE failed while processing a
storage would have held a copy of a staging wait or reply request. The module
area destined for an functional subsystem produces a dump that indicates the
(FSS) address space. The three low-order failure IATSSRE encountered.
bytes of register 15 contain the return code
from the MVS GETMAIN macro. The passed staging area was not
found on the GETMAINED staging
06 The JES3 subsystem interface read-end area (SAG) queue.
module IATSSRE could not find the FSID in
the staging area; the FSID identifies the Source: JES3
dynamic destination queue (DESTQ) for which System action: The system writes the common
the staging area is intended. service area (CSA), system queue area (SQA), and the
07 The JES3 subsystem interface read-end MVS trace table to a SYS1.DUMP data set and
module IATSSRE could not find the proper abnormally ends the current address space. If the
control block structure required for queuing the address space is the JES3 address space, the system
staging area in an FSS address space. does not write a dump.
11 A JES3 routine issued the IATXSSXM macro to For reason code X'40', return code X'08', the system
Chapter 2. System Completion Codes 249
6FC • 702
abnormally ends the requesting task so that no user
700
must wait for a response that cannot be received.
Explanation: During processing of an I/O request, a
System programmer response: If the problem
program check occurred in a supervisor service routine
occurred in JES3 you should:
called by the execute channel program (EXCP).
v Save the MLOG listing or get a print of DLOG
v Provide a listing of the initialization deck (JES3OUT) System action: The system abnormally ends the
v Provide a console log from initialization current task. The system writes a logrec data set error
v Check the JESYSMSG data set for error indications record.
Application Programmer Response: Check the
6FC problem program for the error. If the error cannot be
determined, run the job again, requesting an ABEND
Explanation: During processing following a program
dump. Notify the system programmer.
check interruption, the system detected an error in a
SPIE or ESPIE macro. The SDWACRC field of the System programmer response: In the ABEND dump,
system diagnostic work area (SDWA) contains a look at field TCBEXCPD at offset X'C0' in the task
hexadecimal reason code to be used when searching control block (TCB) for the current task. TCBEXCP
problem reporting data bases or when reporting the points to the EXCP debugging area (XDBA). The XDBA
problem to the IBM Support Center. contains diagnostic data associated with the EXCP
processor.
Code Explanation
Look for the problem in one of the service routines used
04 The user’s PICA contains an invalid bit setting
by EXCP. If the error recurs and the program is not in
in the program mask.
error, look at the messages in the job log for more
08 The user’s PICA is unavailable. information.
12 The SCA, pointed to by the TCBPIE, is Search problem reporting data bases for a fix for the
unavailable. problem. If no fix exists, contact the IBM Support
Center. Provide the logrec data set error record and the
16 The RPP, pointed to by the SCARPPTR, is source program listing for the job.
unavailable.
Source: Execute channel program (EXCP)
20 The PIE, pointed to by the SCAPIE or
SCAPPIE, is unavailable.
702
24 The SCA, pointed to by the TCBPIE, is
unavailable. Explanation: During processing of a POST macro, the
system found either incorrect input data or an
28 The RPP, pointed to by the SCARPPTR, is unauthorized POST exit routine request.
unavailable.
Register 15 contains a hexadecimal reason code that
32 The PIE, pointed to by the SCAPIE or explains the error:
SCAPPIE, is unavailable.
Code Explanation
36 Unable to reference SPIE/ESPIE control blocks
or an error occurred while handling a 00 A function request was incorrect.
SPIE/ESPIE exit.
04 The address is incorrect for an exit routine for
System action: The system abnormally ends the task a CREATE or DELETE request.
that experienced the program check. The system may
08 During an attempt to post an extended event
write a logrec data set error record.
control block (ECB), the descriptor word of the
Operator response: If the system programmer asks ECB extension contained incorrect data.
for an SVC dump, set the following SLIP trap:
0C During an attempt to post an extended ECB,
SLIP SET,COMP=6FC,ACTION=SVCD,END the ECB extension contained an incorrect exit
Application Programmer Response: Resubmit the routine address.
job. If the error recurs, contact the system programmer. 10 A POST exit routine attempted to post an
System programmer response: Search problem extended ECB.
reporting data bases for a fix for the problem. If no fix 14 During an attempt to post an extended ECB,
exists, ask the operator to set a SLIP trap to obtain an either the ECB address or ECB extension
SVC dump. Contact the IBM Support Center. Provide address was incorrect.
the SVC dump, the reason code, and, if available, the
logrec data set error record. 18 Without use of the local lock for serialization,
the ECB has been updated from an initialized
Source: Supervisor control extended state to a waited state.
250 z/OS V1R10.0 MVS System Codes
704 • 705
System action: The system abnormally ends the However, when the system attempted to
program that issued the POST macro. release the lock, the release request
failed.
Application Programmer Response: This code is
only associated with extended ECB processing. If an 08 A system service routine returned an
extended ECB was being posted, ensure that it contains incorrect return code to the virtual
valid data. Then correct the error identified by the return storage manager (VSM) interface
code. Run the job again. module.
System programmer response: If the error recurs 09 While getting or freeing storage in a
and the program is not in error, look at the messages in local or global SQA subpool, the service
the job log for more information. Search problem routine that builds double free elements
reporting data bases for a fix for the problem. If no fix (DFE) tried to place virtual storage on
exists, contact the IBM Support Center. Provide the the DFE queue, but could not do so
source program listing for the job. because the storage was described by
another DFE already on the queue.
Source: Task management
10 While in recovery processing, the
system detected a condition that is
704
normally considered a user error, such
Explanation: A system error, uncorrectable machine as an error in the parameter list.
error, or error that cannot be determined occurred when However, it is likely that the error is not
the system tried to process an EC, EU, LC, LU, VC, or a user error because recovery
VU form of the GETMAIN macro. A reason code in the processing is in control.
SDWACRC field of the system diagnostic work area
System action: The system writes a logrec data set
(SDWA) explains the error:
error record. The system continues processing.
Note: Some VSM return codes may be a half-word in Application Programmer Response: Run the job
length. In these cases, the high-order byte is the again. If the error recurs, contact the system
module id of the issuing module, and the programmer.
low-order byte is the return code.
System programmer response: Search problem
Module ID Module Name reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
1 IGGVVSMRT
Source: Virtual storage manager (VSM)
3 IGVVSM24
4 IGVVSM31 705
6 IGVGSQA Explanation: A system error, uncorrectable machine
7 IGVFSQA error, or error that cannot be determined occurred when
the system tried to process an EC, EU, LC, LU, VC, or
A IGVGLSQA VU form of the FREEMAIN macro. A reason code in the
B IGVFLSQA SDWACRC field of the system diagnostic work area
(SDWA) explains the error:
C IGVGAPVT
E IGVFSP Note: Some VSM return codes may be a half-word in
length. In these cases, the high-order byte is the
44 IGVVSMRF module id of the issuing module, and the
Code Explanation low-order byte is the return code.
01 While processing the GETMAIN request, Module ID Module Name
the system tried to release central 1 IGGVVSMRT
storage backing global or local system
queue area (SQA or LSQA) storage. A 3 IGVVSM24
program page fixed the virtual storage. 4 IGVVSM31
However, it is a basic property of the
system that SQA and LSQA storage is 6 IGVGSQA
page fixed. 7 IGVFSQA
04 Status information indicates that the A IGVGLSQA
system has obtained a global lock to
support the GETMAIN request. B IGVFLSQA
Chapter 2. System Completion Codes 251
706 • 70A
C IGVGAPVT
706
E IGVFSP
Explanation: The error occurred during processing of
44 IGVVSMRF a LINK(X), XCTL(X), ATTACH(X), or LOAD macro.
Code Explanation The requested load module was marked not executable.
01 While processing the FREEMAIN System action: The task is ended unless ERRET is
request, the system tried to release specified on the macro.
central storage backing global or local
The system issues message CSV016I and an ABEND
system queue area (SQA or LSQA)
dump.
storage. A program page fixed the
virtual storage. However, it is a basic Application Programmer Response: Ensure that the
property of the system that SQA and target load module is executable and the linkage editor
LSQA storage is page fixed. did not find errors in the module. Have the module
edited by the linkage editor again. Then recompile, and
02 While processing a subpool FREEMAIN
run the job step again.
of a local system queue area subpool, a
service routine was called to free System programmer response: If the error recurs
storage described by an allocated and the program is not in error, see the system
element (AE). The service routine programmer response for the messages in the job log.
returned a return code indicating that
If the problem persists, search problem reporting data
the storage is not described by an AE.
bases for a fix for the problem. If no fix exists, contact
04 Status information indicates that the the IBM Support Center. Provide the ABEND dump and
system has obtained a global lock in the source program listing for the job.
support of the FREEMAIN request.
Source: Contents supervision (CSV)
However, when the system attempted to
release the lock, the release request
failed. 70A
09 While getting or freeing storage in a Explanation: A system error, uncorrectable machine
local or global system queue area error, or error that cannot be determined, occurred when
subpool, the service routine that builds the system tried to process an R form of the GETMAIN
double free elements (DFE) tried to or FREEMAIN macro. A reason code in the SDWACRC
place virtual storage on the DFE queue, field of the system diagnostic work area (SDWA)
but could not do so because the storage explains the error:
was described by another DFE already
on the queue. Note: Some VSM return codes may be a half-word in
0C A FREEMAIN service routine returned length. In these cases, the high-order byte is the
an incorrect return code to the virtual module id of the issuing module, and the
storage manager (VSM) interface low-order byte is the return code.
module. Module ID Module Name
10 While in recovery processing, the 1 IGGVVSMRT
system detected a condition that is
normally considered a user error, such 3 IGVVSM24
as an error in the parameter list. 4 IGVVSM31
However, the error is most likely not a
user error because recovery processing 6 IGVGSQA
is in control. 7 IGVFSQA
System action: The system writes a logrec data set A IGVGLSQA
error record. The system continues processing.
B IGVFLSQA
Application Programmer Response: Run the job
again. If the error recurs, contact the system C IGVGAPVT
programmer.
E IGVFSP
System programmer response: Search problem
44 IGVVSMRF
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Code Explanation
Source: Virtual storage manager (VSM) 01 While processing the FREEMAIN
request, the system tried to release
252 z/OS V1R10.0 MVS System Codes
70D
central storage backing global or local
70D
system queue area (SQA or LSQA)
storage. A program page fixed the Explanation: A program issued a CALLRTM
virtual storage. However, it is a basic TYPE=ABTERM macro. In response, the recovery
property of the system that SQA and termination manager (RTM) was validating entry into
LSQA storage is page fixed. RTM1. RTM determined that the entry mode
requirements were not met.
02 While processing a subpool FREEMAIN
of a local system queue area subpool, a A hexadecimal reason code in the following explains the
service routine was called to free error:
storage described by an allocated v Field RTM2CRC of the RTM2 work area (RTM2WA)
element (AE). The service routine v Message IEA995I
returned a return code indicating that v TCBARC field of the task control block (TCB)
the storage is not described by an AE.
Code Explanation
04 Status information indicates that the
04 A program that is not disabled issued the
system has obtained a global lock in
CALLRTM macro with TYPE=ABTERM,TCB=0
support of the FREEMAIN request.
or TYPE=ABTERM,TCB=(the current TCB).
However, when the system attempted to
release the lock, the release request 08 A program that does not hold the local lock
failed. issued the CALLRTM TYPE=ABTERM macro
specifying the address of a task control block
08 A GETMAIN storage management
(TCB) that is not current.
service routine returned an incorrect
return code to the virtual storage 0C RTM1 was entered through CVTBTERM, but
manager (VSM) interface module. without the local lock.
09 While getting or freeing storage in a System action: RTM abnormally ends the program
local or global system queue area that issued the CALLRTM TYPE=ABTERM macro. If the
subpool, the service routine that builds caller requested ending of another task, RTM also ends
double free elements (DFE) tried to that task using the abend code and reason code
place virtual storage on the DFE queue, supplied by the caller.
but could not do so because the storage
was described by another DFE already The system issues message IEA995I. The system may
on the queue. write an SVC dump.
0C A FREEMAIN storage management Operator response: If RTM did not write a dump and
service routine returned an incorrect the system programmer asks for an SVC dump, set the
return code to the virtual storage following SLIP trap:
manager (VSM) interface module. SLIP SET,COMP=70D,ACTION=SVCD,END
10 While in recovery processing, the System programmer response: The return address
system detected a condition that is of the issuer of the CALLRTM TYPE=ABTERM macro is
normally considered a user error, such in:
as an error in the parameter list. v Register 14 at the time of error
However, the error is most likely not a
v The RCVY entry for the ABTERM request in the
user error because recovery processing
system trace.
is in control.
Analyze the dump to identify the module issuing the
System action: The system writes a logrec data set
CALLRTM TYPE=ABTERM macro:
error record. The system continues processing.
v For an installation-provided module, correct the
Application Programmer Response: Run the job program to obtain the correct serialization.
again. If the error recurs, contact the system
v For an IBM-provided module, search problem
programmer.
reporting data bases for a fix for the problem. If no fix
System programmer response: Search problem exists, contact the IBM Support Center. Provide
reporting data bases for a fix for the problem. If no fix problem data collected.
exists, contact the IBM Support Center.
Source: Recovery termination manager (RTM)
Source: Virtual storage manager (VSM)
Chapter 2. System Completion Codes 253
713 • 72A
Source: DFSMSdfp
713
Explanation: The error occurred during processing of
71A
an OPEN macro instruction for a data set on magnetic
tape or on a direct access device. This system Explanation: This system completion code is used to
completion code is accompanied by message IEC148I. end a catalog address space service task when (1) the
Refer to the explanation of message IEC148I for catalog address space is ending and restarting or (2) an
complete information about the task that was ended and abend has already occurred in a user address space
for an explanation of the return code (rc in the message during catalog processing. System completion code 71A
text) in register 15. is intended for catalog internal communication only, and
no further diagnosis is necessary.
Application Programmer Response: Respond as
indicated for message IEC148I. System action: None.
System programmer response: If the error recurs Source: DFSMSdfp
and the program is not in error, look at the messages in
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix 722
exists, contact the IBM Support Center. Provide the JCL Explanation: One of the following output limits was
and the program listing for the job. exceeded:
Source: DFSMSdfp v The output limit specified by the OUTLIM keyword on
the SYSOUT DD statement
714 v The job output limit specified in the LINES and
CARDS parameters of the JES2 JOBPARM
Explanation: The error occurred during processing of statement
a CLOSE macro instruction for a data set on magnetic v The job output limit specified in the BYTES, CARDS,
tape. This system completion code is accompanied by LINES, and PAGES parameters on the STANDARDS
message IEC215I. Refer to the explanation of message initialization statement or the JES3 MAIN statement
IEC215I for complete information about the task that
was ended and for an explanation of the return code (rc System action: The system ends processing of the
in the message text) in register 15. job step.
Application Programmer Response: Respond as Application Programmer Response: Check for
indicated for message IEC215I. input/output (I/O) loops. Verify that the parameter value
does not conflict with any installation requirements. If no
System programmer response: If the error recurs errors are found, increase the value in the statement.
and the program is not in error, look at the messages in Then run the job again.
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix Source: JES
exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
72A
Source: DFSMSdfp
Explanation: During processing for an ATTACH
macro, the system encountered an error.
717
Register 15 contains a hexadecimal reason code that
Explanation: The error occurred during processing of explains the error:
a BSAM CLOSE macro instruction with a TYPE=T
Code Explanation
operand for a data set on magnetic tape. This system
completion code is accompanied by message IEC222I. 00 The system found an incorrect parameter
Refer to the explanation of message IEC222I for address when processing the ATTACH
complete information about the task that was ended and parameter list.
for an explanation of the return code (rc in the message
04 An end-of-task exit routine (ETXR) address is
text) in register 15.
incorrect because both of the following
Application Programmer Response: Respond as situations exist:
indicated for message IEC222I. v The ETXR is already in effect as an ETXR
System programmer response: If the error recurs for a subtask of the task
and the program is not in error, look at the messages in v The current ATTACH was issued in a
the job log for more information. Search problem different addressing mode than the ATTACH
reporting data bases for a fix for the problem. If no fix that created the matching ETXR
exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
254 z/OS V1R10.0 MVS System Codes
730 • 737
08 The length of the ATTACH parameter list is xxxx0008 DEQ processing could not obtain the
incorrect. ALET of the GRS address space.
0C The format number of the parameter list is xxxx0009 ENQ processing could not obtain
incorrect. storage in the primary address space.
10 A caller using the ATTACHX macro xxxx00FE Abend in dynamic exit.
encountered nonzero access list entry tokens
(ALETs). The ALETs should have been set to The reason code could also be associated with an
zero, but they were not. ISGENQ Request=Release. See the reason codes
listed for the ISGENQ macro in z/OS MVS
14 A caller in access register ASC mode used the
Programming: Authorized Assembler Services
ATTACH macro instead of the ATTACHX
Reference EDT-IXG.
macro.
System action: The system writes a logrec data set
18 An unauthorized caller issued ATTACH or
error record. The system issues an ABEND dump.
ATTACHX with the DISP=RESET parameter.
The caller must be authorized. Application Programmer Response: Do the
following:
1C A caller issued ATTACHX with the KEY=NINE
parameter, but the storage protection override 1. Obtain the address of the DEQ parameter list from
facility is not installed. Only specify KEY=NINE register 1 in the UNIQUE-3 column of the SVC 30
when this facility (indicated by bit CVTOVER in entry in the system trace.
mapping macro CVT being on) is installed. 2. Check the parameter list against the SVC 30
mapping. When analyzing the parameter list,
System action: The system abnormally ends the
remember that the unit control block (UCB) pointer,
program that issued the ATTACH macro. The system
if present, is the address of a field that, in turn,
does not create the new subtask.
contains the address of the UCB.
Application Programmer Response: This is probably If the parameter list contains incorrect data, continue
an error in the program. Correct the error indicated by diagnosis in the program that issued the macro.
the reason code by changing the ATTACH macro or the
3. For abend X'730' and reason code X'xxxx0009',
environment in which the macro runs. Run the job
determine or relieve the cause of the storage
again.
shortage and try the request again.
System programmer response: If the error recurs
System programmer response: If the problem
and the program is not in error, look at the messages in
persists, search problem reporting data bases for a fix
the job log for more information. Search problem
for the problem. If no fix exists, contact the IBM Support
reporting data bases for a fix for the problem. If no fix
Center. Provide the ABEND dump.
exists, contact the IBM Support Center.
Source: Global resource serialization
Source: Task management
737
730
Explanation: The error occurred at an end-of-volume
Explanation: Global resource serialization
or during allocation of a secondary quantity of direct
encountered an unexpected error occurred during the
access storage as requested in the SPACE parameter
processing of a DEQ macro.
of the DD statement for the data set. This system
Register 15 may contain a reason code associated with completion code is accompanied by message IEC027I.
this error: Refer to the explanation of message IEC027I for
complete information about the task that was ended and
Code Explanation
for an explanation of the return code (rc in the message
xxxx0000 General module failure in DEQ text) in register 15.
processing.
Application Programmer Response: Respond as
xxxx0004 DEQ processing could not obtain indicated for message IEC027I.
storage in the home address space.
System programmer response: If the data set does
xxxx0005 DEQ processing could not obtain exist on the specified volumes and the problem recurs,
storage in the common area. look at the messages in the job log for more
information. Search problem reporting data bases for a
xxxx0006 DEQ processing could not obtain the fix for the problem. If no fix exists, contact the IBM
ALET of the caller’s primary address Support Center. Provide the JCL and the program listing
space. for the job.
Source: DFSMSdfp
Chapter 2. System Completion Codes 255
738
the return code from the linkage stack
738
query/update service.
Explanation: Global resource serialization
encountered an unexpected error during the processing The reason code could also be associated with an
of an ENQ macro instruction. ISGENQ Request=Obtain or Request=Change. See the
reason codes listed for the ISGENQ macro in z/OS
Register 15 may contain a reason code associated with
MVS Programming: Authorized Assembler Services
this error:
Reference EDT-IXG.
Code Explanation
Additionally, there are 738 abends that occur without
xxxx0000 General module failure in ENQ
reason codes. These include:
processing.
v If there are ENQs on resources and the number of
xxxx0001 jobs suspended exceeds 12,000 on a system during
An ISGENQ REQUEST=OBTAIN, a resource name list (RNL) change. When the
RESERVEVOLUME=YES, number reaches 800, the system cancels the RNL
SYNCHRES=YES, request resulted in change.
device I/O error when performing the v If there is a control block corruption in the GRS
reserve device state transitioning. address space.
There is something wrong with the
System action: The system writes a logrec data set
device rather than a GRS problem.
error record and an ABEND dump.
Note that for ISGENQ
Application Programmer Response: Do the
SYNCHRES=SYSTEM
following:
RESERVEVOLUME=YES requests,
the result of the device state 1. Obtain the address of the ENQ parameter list from
transitioning is not provided back to register 1 in the UNIQUE-3 column of the SVC X'38'
the user. entry in the system trace.
2. Check the parameter list against the SVC X'38'
xxxx0002 RESERVE start processing failed.
mapping. When analyzing the parameter list,
xxxx0003 Synchronous RESERVE done remember that the unit control block (UCB) pointer,
processing failed. if present, is the address of a field that, in turn,
contains the address of the UCB.
xxxx0004 ENQ processing could not obtain
storage in the home address space. If the parameter list contains incorrect data, continue
diagnosis in the program that issued the macro.
xxxx0005 ENQ processing could not obtain
3. For abend X'738' and reason code X'000000FF',
storage in the common area.
none.
xxxx0006 ENQ processing could not obtain the 4. For abend X'738' and reason code X'xxxx0009',
ALET of the caller’s primary address determine or relieve the cause of the storage
space. shortage and try the request again.
xxxx0007 ENQ processing could not obtain a System programmer response: If the problem
DSQE to suspend a request for a persists, search problem reporting data bases for a fix
RNL change. for the problem. If no fix exists, contact the IBM Support
xxxx0008 ENQ processing could not obtain the Center. Provide the logrec data set error record and the
ALET of the GRS address space. ABEND dump. If abend X'738' with reason code
X'000000FF' persists, issue D GRS,DEV=xxxx (xxxx is
xxxx0009 ENQ processing could not obtain the device number in hexadecimal) command to
storage in the primary address space. determine what are the reserve requests on the device.
xxxx00FE Abend in dynamic exit. For reason code X'00FF', do the following:
xxxx00FF RESERVE processing detected an v Obtain the address of the parameter list from register
overflow when updating the reserve 1 in the UNIQUE-3 column of the SVC X'30' or SVC
count. X'38' entry in the system trace.
v Check the parameter list against the SVC X'30' or
xxxx01yy ENQ processing was unable to query
SVC X'38' mapping. When analyzing the parameter
the linkage stack entry. yy is the
list, remember that the unit control block (UCB)
return code from the linkage stack
pointer, if present, is the address of the field that
query/update service.
contains the address of the UCB.
xxxx02yy ENQ processing was unable to
update the linkage stack entry. yy is
256 z/OS V1R10.0 MVS System Codes
744 • 778
The UCB mapping will contain the device number that v The system abnormally ends the program that issued
had more than 255 simultaneous RESERVE requests the macro, or returns to the macro caller with a return
outstanding. code of X'10'.
Application Programmer Response: Check for
For all other reason codes, if the problem persists,
incorrect input parameters passed to the OUTADD or
search the problem reporting databases for a fix for the
OUTDEL macro. Submit the job again.
problem. If no fix exists, contact the IBM Support
Center, providing the logrec data set error record and System programmer response: If the problem
the ABEND dump. persists, search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support
Source: Global resource serialization
Center.
Source: Dynamic output
744
Explanation: A program check occurred during the
778
processing of SYNADAF or SYNADRLS. This error
could not be attributed to incorrect user input. Explanation: A system error, uncorrectable machine
error, or error that cannot be determined occurred under
System action: The SYNADAF recovery routine tried
one of the following conditions:
to take a dump of LSQA and the user’s region. The
dump header includes the job name, step name, and v While the system was attempting to satisfy a request
procedure step name. See message IEC907I to made through the STORAGE macro
determine whether the dump attempt was successful. A v While the system was trying to process an RC, RU,
software error record was written to the logrec data set. VRC, or VRU form GETMAIN macro
Application Programmer Response: Rerun the job v While the system was trying to process an RC or RU
step. form FREEMAIN macro
System programmer response: If the error recurs A reason code in the SDWACRC field of the system
and the program is not in error, look at the messages in diagnostic work area (SDWA) explains the error:
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix Note: Some VSM return codes may be a half-word in
exists, contact the IBM Support Center. Provide the length. In these cases, the high-order byte is the
JCL, the program listing for the job, and the logrec data module id of the issuing module, and the
set error record. low-order byte is the return code.
Source: DFSMSdfp Module ID Module Name
1 IGGVVSMRT
75F 3 IGVVSM24
Explanation: The system resources manager (SRM) 4 IGVVSM31
detected that the system timer queue element (TQE)
exceeded the expected interval. 6 IGVGSQA
System action: SRM performs normal TQE expiration 7 IGVFSQA
processing and requeues the TQE. The system
A IGVGLSQA
abnormally ends the current task. The system writes
messages and a logrec data set error record. B IGVFLSQA
System programmer response: Search problem C IGVGAPVT
reporting data bases for a fix for the problem. If no fix
E IGVFSP
exists, contact the IBM Support Center. Provide the
logrec data set error record. 44 IGVVSMRF
Source: System resources manager (SRM) Code Explanation
01 While attempting to free storage, the
76D system tried to release central storage
backing global or local system queue
Explanation: The system found an error while
area (SQA or LSQA) storage. A program
processing an OUTADD or OUTDEL macro.
page fixed the virtual storage. However,
System action: The system does the following: it is a basic property of the system that
v The system writes a logrec data set error record. SQA and LSQA storage is page fixed.
v The system writes an SVC dump. 02 While attempting to release an entire
Chapter 2. System Completion Codes 257
77D • 7B0
LSQA subpool, a service routine was
77D
called to free storage described by an
allocated element (AE). The service Explanation: During processing of an EVENTS macro,
routine returned a return code indicating the system found an error in the macro input
that the storage is not described by an parameters.
AE.
Register 15 contains a hexadecimal reason code that
04 Status information indicates that the explains the error:
system has obtained a global lock in
Code Explanation
support of a request to release storage.
However, when the system attempted to 04 A caller issued an incompatible level of the
release the lock, the release request EVENTS macro.
failed.
08 Both WAIT=YES and WAIT=NO were
08 While attempting to obtain storage, a specified.
storage management service routine
returned an incorrect return code to the System action: The system abnormally ends the
virtual storage manager (VSM) interface program that issued the EVENTS macro.
module. Application Programmer Response: Verify the
09 While getting or freeing storage in a EVENTS macro input parameters, the level of the
local or global system queue area macro, and the contents of register 0. Correct the error.
subpool, the service routine that builds Run the job again.
double free elements (DFE) tried to System programmer response: If the error recurs
place virtual storage on the DFE queue, and the program is not in error, look at the messages in
but could not do so because the storage the job log for more information. Search problem
was described by another DFE already reporting data bases for a fix for the problem. If no fix
on the queue. exists, contact the IBM Support Center. Provide the
0C While attempting to free storage, a assembly listing for the job.
storage management service routine Source: Task management
returned an incorrect return code to the
virtual storage manager (VSM) interface
module. | 7B0
10 While in recovery processing, the | Explanation: An error occurred during processing of
system detected a condition that is | the hardware instrumentation services (HIS). Register
normally considered a user error. | 15 contains a hexadecimal reason code describing the
However, it is not likely that the error is | error. The first halfword of each reason code (xxxx) is
a user error because recovery | set by the system and contains internal information. The
processing is in control. | following reason codes only list the external errors. Any
| unlisted reason codes are internal and should be
14 VSM failed to backout the acquisition of | reported to the IBM Support Center.
a new address queue anchor table
(AQAT) stack. In this case, the system | Reason code
issues abend X'778' only to record the | Explanation
error. The system continues processing | xxxx8001
upon retry from VSM recovery. | System storage is exhausted or not available.
20 The STORAGE service routine has | System Action: HIS does not perform the
failed unexpectedly. The failure is | requested operation. The HIS address space is
probably not a user error. | not initialized if system storage cannot be
System action: The system writes a logrec data set | obtained.
error record. The system continues processing. | Programmer Response: Free up system
Application Programmer Response: Run the job | storage and resubmit the HIS job.
again. If the error recurs, contact the system | xxxx8003
programmer. | It takes too long to write the sampling data.
System programmer response: Search problem | System Action: The data collection activities
reporting data bases for a fix for the problem. If no fix | are stopped. HIS waits for the sample data to
exists, contact the IBM Support Center. | be written out. However, a preset wait time
Source: Virtual storage manager (VSM) | expires and not all data have been written.
258 z/OS V1R10.0 MVS System Codes
7C4 • 7C6
| Programmer Response: Assign a sufficiently 05 During JES3 initialization processing, module
| high dispatch priority to the HIS task, so that IATINC2 detected an error while invoking an
| the sampling data can be written to the output IXZXCNSV order. An IXZXCNSV
| in a timely manner. If the problem still exists, ORDER(SYNCPT) returned with a bad return
| contact the IBM Support Center. code. The return and reason code for the
IXZXCNSV macro invocation is within the
| xxxx8005 IXZXCNSV parameter list. The parameter list is
| The CALLRTM macro was issued against HIS
contained within the automatic area of
| main task.
IATCS04. The automatic area is pointed to by
| System Action: The HIS main task is being general register 8 at the time of failure. Use the
| abnormally ended by calling the recovery return and reason codes to determine why
| termination manager (RTM). This is a generic JESXCF failed to process the SYNCPT order
| abend reason code. The specific reason for the successfully.
| CALLRTM action can be found in the
System action: For reason codes X'01' and X'03',
| accompanying error messages, or SVC dumps
varies with invoking function. For reason codes X'04'
| (for unexpected errors).
and X'05', JES3 initialization continues but the remote
| Programmer Response: Analyze the console function may be lost or produce unpredictable
| accompanying error messages for the cause. results.
| Resubmit the HIS job after the error has been
System programmer response: To determine the
| corrected.
error, refer to reason code descriptions.
| System action: The system abnormally ends the HIS Source: JES3
| address space.
| System programmer response: If the error recurs
7C6
| and the program is not in error, look at the messages in
| the job log for more information. Search problem Explanation: The system encountered an error while
| reporting databases for a fix for the problem. If no fix processing the UCBPIN macro with the UNPIN option. A
| exists, contact the IBM Support Center. hexadecimal reason code in register 15 explains the
error:
| Source: Hardware instrumentation services (HIS).
Code Explanation
7C4 01 The PTOKEN supplied as input on the
UCBPIN macro request contains incorrect data.
Explanation: JES3 encountered an error when calling
a JESXCF console-related function. The abend reason 02 The PTOKEN supplied as input on the
code identifies the specific error. UCBPIN macro request contains
non-addressable data.
Code Explanation
System action: The system abnormally ends the task,
01 IATXCSIF SERVICE=XAUTH was passed a
unless a recovery routine was provided to handle the
bad parameter list (service routine IATCS01).
interruption.
Analyze the parameter list to determine the
problem. Application Programmer Response: Check your
programs for one of the following possible scenarios
03 IATXCSIF SERVICE=CONSTYPE was passed
causing the abend:
a bad parameter list (service routine IATCS03).
Analyze the parameter list to determine the v A task does the following:
problem. 1. Pins a unit control block (UCB) without specifying
the LASTING parameter on the UCBPIN macro.
04 During JES3 initialization processing, module
IATINC2 detected an error while invoking an 2. Schedules a service request block (SRB) to unpin
IXZXCNSV order. An IXZXCNSV the UCB.
ORDER(START) returned with a bad return Because the program did not specify LASTING on
code. The return and reason code for the the UCBPIN macro, the task ends before the SRB is
IXZXCNSV macro invocation is within the dispatched. When the task ends, the system unpins
IXZXCNSV parameter list. The parameter list is the UCB. When the SRB subsequently tries to unpin
contained within the automatic area of the same UCB, the system issues this abend.
IATCS04. The automatic area is pointed to by
v The PTOKEN specified on the UCBPIN macro is
general register 8 at the time of failure. Use the
overlaid or altered by the application program.
return and reason codes to determine why
JESXCF failed to process the START order Source: Input/output supervisor (IOS)
successfully.
Chapter 2. System Completion Codes 259
7C7 • 804
error can occur when there is an error in the
7C7
channel program. Correct the channel
Explanation: The batch local shared resources (LSR) program.
subsystem encountered an unexpected error. Register
2 System error. Contact the IBM Support Center.
15 contains diagnostic information in the format
X‘mm0002rr’. The mm field identifies the issuing 3 An error occurred during page-fix or page-unfix
module; the 02 identifies the batch LSR subcomponent processing. A page-fix error can occur if the
of the callable service request (CSR) component. rr is EXCP processor tries to fix pages that are not
the reason code associated with the abend. assigned to the caller’s address space identifier
(ASID).
System action: The subsystem schedules an SVC
dump, and does not perform the request. 4 A program issued SVC 114, the EXCPVR
macro, but an error occurred during page-fix or
Operator response: Report the problem to the system
page-unfix processing. A page-fix error can
programmer.
occur if the EXCP processor tries to fix pages
System programmer response: Search problem that are not assigned to the caller’s ASID.
reporting data bases for a fix for the problem. If no fix
5 The IOBE specified that 64-bit IDAWs are to
exists, contact the IBM Support Center. Report the
be used for an EXCPVR request, but they are
diagnostic information in register 15.
not supported by the hardware.
Source: Callable Service Requests (CSR)
6 The IOBE specified that 64-bit IDAWs are to
be used for an EXCPVR request but they are
7FB not supported by the device support code
Explanation: An uncorrectable error occurred while 7 The IOBE specified that format 1 CCWs are to
one of the MVS-JES3 dynamic device reconfiguration be used for an EXCP request, but format 1
(DDR) subsystem interface (SSI) routines was running. CCWs are only supported with EXCPVR
requests.
System action: The system ends the reconfiguration.
8 The IOBE specified that MIDAWs are to be
Operator response: If you initiated the
used for an EXCP request, but MIDAWs are
reconfiguration, retry it. If the system initiated the
only supported with EXCPVR requests.
reconfiguration, notify the system programmer.
System action: The system abnormally ends the
System programmer response: Search problem
current task. The system writes a logrec data set error
reporting data bases for a fix for the problem. If no fix
record and issues a system dump.
exists, contact the IBM Support Center.
Application Programmer Response: Correct the
Source: Dynamic device reconfiguration (DDR)
problem that the reason code indicates.
If you get reason code 3 or 4, or if the error cannot be
800
determined, run the job again, requesting an ABEND
Explanation: During processing of an I/O request, dump. Notify the system programmer.
execute channel program (EXCP) processing
System programmer response: In the dump, look at
encountered an error. Most instances of the X'800'
field TCBEXCPD at offset X'C0' in the task control block
ABEND code have a reason code that explains the
(TCB) for the current task. TCBEXCPD points to the
error. After the pages for a buffer were fixed, an LRA
EXCP debugging area (XDBA). The XDBA contains
instruction for a page in the buffer got a nonzero
diagnostic data associated with the EXCP processor.
condition code. This means that page is not valid.
If the error recurs and the program is not in error, look
Code Explanation
at the messages in the job log for more information.
1 An error occurred during indirect address word Search problem reporting data bases for a fix for the
(IDAW) or channel command word (CCW) problem. If no fix exists, contact the IBM Support
validity check processing. An access protection Center. Provide the logrec data set error record, the
error occurred when: JCL for the job, and the SNAP dump.
v The EXCP IDAW routine tried to access the
Source: Execute channel program (EXCP)
IDAW using an incorrect storage protection
key.
v The EXCP CCW validity check routine tried 804
to access the virtual channel program using
Explanation: An error occurred when the system tried
an incorrect storage protection key.
to process an EC, EU, LC, LU, VC, or VU form of the
v The channel program attempted to execute
GETMAIN macro. A reason code in the SDWACRC field
a restricted operation. An access protection
260 z/OS V1R10.0 MVS System Codes
805 • 806
of the system diagnostic work area (SDWA) explains Note: If this error is detected, the calling
the error: program abnormally ends even though
RC, EC, LC, or VC is specified for
Code Explanation
FREEMAIN.
04 There is not enough virtual system queue area
1C During request processing, the system tried to
(SQA) storage available to satisfy the request.
get local system queue area (LSQA) virtual
08 There is not enough virtual common service storage for virtual storage management’s
area (CSA) storage available to satisfy the (VSM) cell pool. There was not enough LSQA
request. virtual storage available.
0C There is not enough virtual local system queue 20 There is not enough virtual storage in the
area (LSQA) storage available to satisfy the LSQA to build a new address queue anchor
request. table (AQAT) stack.
10 There is not enough virtual private area System action: The system issues message IEA705I.
storage available to satisfy the request. The system abnormally ends the current task.
Application Programmer Response: Check for
Note: This error can occur if an installation program errors that incorrectly modify the macro
exit is requesting virtual storage from a expansion. Correct them. If necessary, change the
V=R region before the system program to request less virtual storage.
completely initializes the region.
Source: Virtual storage management (VSM)
14 A negative amount of storage was specified on
the GETMAIN.
806
Note: If this error is detected, the calling Explanation: The supervisor, or the Supervisor Call
program abnormally ends even though (SVC) for the BLDL (build a directory entry list) macro,
RC, EC, LC, or VC is specified for detected an error during the processing of a LINK(X),
GETMAIN, or COND=YES is specified XCTL(X), ATTACH(X), or LOAD macro with the EP
for STORAGE. (entry point) or EPLOC (EP location (address)) operand.
1C During request processing, the system tried to The reason code in register 15 identifies the error:
get LSQA virtual storage for virtual storage
management’s (VSM) cell pool. There was not Code Explanation
enough LSQA virtual storage available.
04 The system could not find the module, whose
20 There is not enough virtual storage in the entry point is the value of the EP or EPLOC
LSQA to build a new address queue anchor operand, in the indicated library (private library,
table (AQAT) stack. job library, or link library). This situation can
occur when LSEARCH=YES is specified on the
System action: The system issues message IEA705I. macro and the limited library search fails to
The system abnormally ends the current task. locate the module. For an alias name, ensure
Application Programmer Response: Check for that the entry point attributes match that of the
program errors that incorrectly modify the macro load module which was previously loaded (that
expansion. Correct them. If necessary, change the is, authorization, RMODE, entry point
program to request less virtual storage. displacement).
Source: Virtual storage management (VSM) 08 An uncorrectable I/O error occurred when the
BLDL control program routine attempted to
search the directory of the library that
805 contained the program whose entry point was
Explanation: An error occurred when the system tried specified in the EP or EPLOC operand. This
to process an EC, EU, LC, LU, VC, or VU form of the can occur if the specified library is an
FREEMAIN macro. A reason code in the SDWACRC uninitialized partitioned data set (PDS).
field of the system diagnostic work area (SDWA) An incorrect data extent block (DEB) has been
explains the error: detected by the BLDL control program. The
Code Explanation DEB was built in other than protect key 0
through 7.
18 A negative amount of storage was specified on
the FREEMAIN macro. 0C The supervisor attempted to search a library
for the program that the EP or EPLOC operand
specifies and found that the library data control
block (DCB) is not open.
Chapter 2. System Completion Codes 261
80A
10 A program issued a LOAD macro with the valid and open. Correct the error and run the job step
explicit load option, but there is no DCB again.
parameter. For explicit loads, the program must
System programmer response: For reason code
supply the DCB parameter with the macro
X'08', resubmit the job. Then have the operator enter a
because the system searches for the module
START GTF command specifying tape output,
that the LOAD specifies only in the library that
MODE=EXT and TIME=YES. Have the operator reply
the DCB parameter specifies.
TRACE=IO in response to message AHL100A.
14 The system could not find the module, whose
Format the output with the IPCS GTFTRACE
entry point is the value of an EP or EPLOC
subcommand.
operand of a XCTL(X) macro, in the link pack
area (LPA), which is where the module must If the error recurs and the program is not in error, see
be when the module is requested by an SVC the system programmer response for messages in the
routine. job log.
18 An SVC routine issued a XCTL(X) macro for a For reason code X'2C' or if the problem persists, search
module. The system tried to search the link problem reporting data bases for a fix for the problem. If
pack area directory to find the module, but the no fix exists, contact the IBM Support Center. Provide
directory had not as yet been built. the ABEND dump and the source program listing for the
job.
1C The data control block (DCB), included as part
of a LINK(X), LOAD, XCTL(X), or ATTACH(X) Source: Contents supervision (CSV)
macro is incorrect.
2C Internal error. 80A
System action: The system issues a message Explanation: An error occurred when the system tried
depending on the reason code accompanying the to process an R form of the GETMAIN or FREEMAIN
abend: macro. A reason code in the SDWACRC field of the
system diagnostic work area (SDWA) explains the error:
Code Message
Code Explanation
04 CSV003I
04 There is not enough virtual system queue area
08 CSV004I
(SQA) storage available to satisfy the request.
0C CSV005I
08 There is not enough virtual common service
10 CSV007I area (CSA) storage available to satisfy the
request.
14 CSV008I
0C There is not enough virtual local system queue
18 CSV006I
area (LSQA) storage available to satisfy the
1C CSV021I request.
10 There is not enough virtual private area
The system issues an ABEND dump. storage available to satisfy the request.
Application Programmer Response: If the reason
code is X'04', this is probably a user error. Make sure Note: This error can occur if an installation
that the requesting program was not incorrectly exit is requesting virtual storage from a
modified. Make sure that the source library was V=R region before the system
indicated correctly and that the indicated library does completely initializes the region.
contain the requested program. For an alias name,
1C During request processing, the system tried to
make sure the alias attributes match the attributes of
get LSQA virtual storage for VSM’s cell pool.
the load module which was already loaded; check the
There was not enough LSQA virtual storage
library authorization, RMODE, and alias entry point
available.
displacement). Also, check that there are no duplicate
aliases or related primary module names in the library 20 There is not enough virtual storage in LSQA to
concatenation. MVS expects that all module names, build a new address queue anchor table
and aliases, are unique across every library. Correct the (AQAT) stack.
error, and run the job step again.
System action: The system issues message IEA705I.
If the reason code is X'14' or X'18', report this The system abnormally ends the current task.
completion code to the system programmer.
Application Programmer Response: A complete
If the reason code is X'0C' or a X'1C', it is a probable dump is necessary to diagnose this out of storage
user error. Make sure that the DCB for the library is condition. If no dump was produced, SLIPs should be
262 z/OS V1R10.0 MVS System Codes
813 • 830
set to obtain a dump on problem recurrence. An abend System programmer response: A complete dump is
878 can cause this same condition, so both SLIPs necessary to diagnose this out of storage condition. If
should be set as follows: no dump was produced, a SLIP should be set to obtain
SLIP SET,COMP=80A,A=SVCD,SDATA=(ALLNUC, a dump on problem recurrence.
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END SLIP SET,COMP=822,A=SVCD,SDATA=(ALLNUC,
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END
SLIP SET,COMP=878,A=SVCD,SDATA=(ALLNUC,
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END Also, search problem reporting data bases for a fix for
the problem. If no fix exists, contact the IBM Support
Also, check for program errors that incorrectly modify Center.
the macro expansion. Correct them. If necessary,
change the program to request less virtual storage. Source: Initiator/terminator
Further debugging information may be found in
Informational APAR II05506. 82A
Source: Virtual storage management (VSM) Explanation: During processing of an ATTACH macro,
the system found an incorrect subpool specified by an
813 authorized task with the NSHSPV or the NSHSPL
parameter. The authorized task is in system key,
Explanation: The error occurred during processing of supervisor state, or authorized by the authorized
an OPEN macro instruction for a data set on magnetic program facility (APF).
tape. This system completion code is accompanied by
message IEC149I. Refer to the explanation of message System action: The system abnormally ends the
IEC149I for complete information about the task that program that issued the ATTACH macro. The system
was ended and for an explanation of the return code (rc does not create the new subtask.
in the message text) in register 15. Application Programmer Response: Change the
Application Programmer Response: Respond as incorrect parameter. Only subpool 236 or 237 may be
indicated for message IEC149I. specified with the NSHSPV or the NSHSPL parameter.
Correct the error. Run the job again.
System programmer response: If the error recurs
and the program is not in error, look at the messages in System programmer response: If the error recurs
the job log for more information. Search problem and the program is not in error, look at the messages in
reporting data bases for a fix for the problem. If no fix the job log for more information. Search problem
exists, contact the IBM Support Center. Provide the JCL reporting data bases for a fix for the problem. If no fix
and the program listing for the job. exists, contact the IBM Support Center. Provide the
assembly listing for the job.
Source: DFSMSdfp
Source: Task management
81A
830
Explanation: A request to abnormally end the catalog
address space (CAS) mother task was issued either Explanation: Global resource serialization
through the MODIFY CATALOG,RESTART command, or encountered an error during processing of a DEQ
through catalog analysis task processing. macro instruction.
System action: The system re-drives all catalog The resource specified by the DEQ is the target of an
requests in process. outstanding ENQ macro instruction with the MASID and
MTCB options specified. The task that issued the ENQ
Source: DFSMSdfp macro instruction with MASID and MTCB should issue
the DEQ macro instruction before this task.
822 System action: The system issues an ABEND dump.
Explanation: During initialization of a job, the initiator Application Programmer Response: Correct the
could not obtain a region required to run the step. program so that the DEQ macro instruction is issued
System action: The system issues message IEF085I only after DEQs have been issued for any outstanding
when the job is an ordinary job. The system issues MASID/MTCB ENQs. Recompile and run the job step
message IEF186I when the job is a deferred checkpoint again.
restart. System programmer response: If the problem
Operator response: If more than one 822 abend is persists, search problem reporting data bases for a fix
received for the same initiator, stop and restart the for the problem. If no fix exists, contact the IBM Support
initiator in which the failing job ran. Center. Provide the dump.
Chapter 2. System Completion Codes 263
837 • 878
Source: Global resource serialization 8 A restart was attempted but was not
successful.
837 System action: The system issues message IRA604I
in conjunction with this system completion code.
Explanation: The error occurred at an end-of-volume
for a sequential data set. This system completion code System programmer response: Correlate this event
is accompanied by message IEC028I. Refer to the to disruptions in CPMF data collection. A CPMF restart
explanation of message IEC028I for complete will be attempted at the next system IPL. See further
information about the task that was ended and for an documentation regarding CPMF in z/OS MVS Data
explanation of the return code (rc in the message text) Areas, Vol 2 (DCCB-ITZYRETC) under IRACPMB.
in register 15.
Source: System resource manager (SRM)
Application Programmer Response: Respond as
indicated for message IEC028I.
878
System programmer response: If the error recurs
Explanation: The error occurred when the system was
and the program is not in error, look at the messages in
trying to do one of the following:
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix v Satisfy a request made through the STORAGE macro
exists, contact the IBM Support Center. Provide the JCL v Process an RU or VRU form of the GETMAIN macro
and the program listing for the job. v Process an RU form of the FREEMAIN macro
Source: DFSMSdfp
A reason code in the SDWACRC field of the system
diagnostic work area (SDWA) explains the error:
838
Code Explanation
Explanation: The system denied an ENQ macro
request because of serious damage to the ENQ/DEQ 04 There is not enough virtual system queue area
control blocks. (SQA) storage available to satisfy the request.
System action: The system issues an ABEND dump. 08 There is not enough virtual common service
area (CSA) storage available to satisfy the
Application Programmer Response: Resubmit the request.
job after the system has been re-IPLed. Do the
following: 0C There is not enough virtual local system queue
1. Obtain the address of the DEQ parameter list from area (LSQA) storage available to satisfy the
register 1 in the UNIQUE-3 column of the SVC 30 or request.
SVC 38 entry in the system trace. 10 There is not enough virtual private area
2. Check the parameter list against the SVC 30 or 38 storage available to satisfy the request. This is
mapping. When analyzing the parameter list, due to one of the following:
remember that the unit control block (UCB) pointer, v A program is requesting virtual storage, but
if present, is the address of a field that, in turn, not subsequently freeing the storage.
contains the address of the UCB.
v The region size specified is too small.
If the parameter list contains incorrect data, continue
v An installation exit is requesting virtual
diagnosis in the program that issued the macro.
storage from a V=R region before
System programmer response: If the problem initialization of the region has completed.
persists, search problem reporting data bases for a fix
14 A negative amount of storage was specified on
for the problem. If no fix exists, contact the IBM Support
a GETMAIN macro.
Center. Provide the ABEND dump.
Source: Global resource serialization Note: If this error is detected, the calling
program abnormally ends even though
RC, EC, LC, or VC is specified for
85F
GETMAIN, or COND=YES is specified
Explanation: The channel path measurement facility for STORAGE.
(CPMF) is not available because of a hardware error.
18 A negative amount of storage was specified on
Code Explanation the FREEMAIN or STORAGE macro.
4 A restart was not attempted either because the
Note: If this error is detected, the calling
restart threshold was exceeded or because the
program abnormally ends even though
hardware error was not recoverable.
264 z/OS V1R10.0 MVS System Codes
87D • 8C3
RC, EC, LC, or VC is specified for v The desired subpool or key.
FREEMAIN, or COND=YES is specified v The target address space for the STORAGE
for STORAGE. macro.
1C During request processing, the system tried to v The TCB address for the STORAGE macro.
get LSQA virtual storage for virtual storage
Make sure also that the area of storage you are
management’s (VSM) cell pool. There was not
requesting is completely free. If part of the area
enough LSQA virtual storage available.
requested is in a page that is already allocated,
20 There is not enough virtual storage in the make sure that the central storage backing
LSQA to build a new address queue anchor specified on the LOC=EXPLICIT keyword matches
table (AQAT) stack. that of the allocated storage.
24 A GETMAIN or STORAGE OBTAIN request 28 Ensure that the calling program specifies the
with the LOC=EXPLICIT keyword specified following correctly:
failed for one of the following reasons: v The storage address on the INADDR keyword.
v Part of the requested area was already
v The length on the LENGTH keyword for the
allocated.
STORAGE macro or the LV keyword for the
v Storage was already allocated in the same
GETMAIN macro.
page as this request, but one of the
following characteristics of the storage was Make sure also that the calling program correctly
different: specifies the value on the JCL REGION
– The subpool keyword. If the JCL REGION value is not large
– The key enough for the requested storage area, increase
– Central storage backing the size of the JCL REGION and resubmit the
job.
28 A GETMAIN or STORAGE OBTAIN request
with the LOC=EXPLICIT keyword specified 04-0C, 14-20
failed because part of the requested area Check for program errors that incorrectly modify the
exceeds the bounds of the region. macro expansion and correct them. If necessary,
change the program to request less virtual storage.
System action: The system issues message IEA705I.
The system abnormally ends the current task. Source: Virtual storage management (VSM)
Application Programmer Response: A complete
dump is necessary to diagnose this out of storage 87D
condition. If no dump was produced, SLIPs should be Explanation: During processing of an EVENTS macro,
set to obtain a dump on problem recurrence. Further the system found that the EVENTS table specified in
debugging information may be found in Informational the event control block (ECB) had no entries available
APAR II05506. An abend 80A can cause this same for the posted ECB address.
condition, so both SLIPs should be set as follows:
SLIP SET,COMP=878,A=SVCD,SDATA=(ALLNUC, System action: The system abnormally ends the
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END program that issued the EVENTS macro.
Application Programmer Response: Ensure that the
SLIP SET,COMP=80A,A=SVCD,SDATA=(ALLNUC,
EVENTS table is large enough to contain entries for all
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END
ECBs that can be posted to it. Correct the error. Run
the job again.
Also, depending on the reason code, do one of the
following: System programmer response: If the error recurs
and the program is not in error, look at the messages in
10 Try increasing the region size specified in the
the job log for more information. Search problem
region parameter on the JOB or EXEC statement in
reporting data bases for a fix for the problem. If no fix
the JCL for the job. However, if the cause of the
exists, contact the IBM Support Center. Provide the
problem is actually that a program is requesting
program listing and the assembly listing associated with
virtual storage and not freeing it, the abend will
the job.
recur when the program uses the virtual storage in
the larger region. Source: Task management
24 Ensure that the calling program specifies the
following correctly: 8C3
v The storage address on the INADDR keyword. Explanation: An abnormal end occurred in NetSpool™.
v The length on the LENGTH keyword for the This system completion code and a NetSpool abend
STORAGE macro or the LV keyword for the reason code are provided at the time of the dump. See
GETMAIN macro. the z/OS Infoprint Server Messages and Diagnosisfor
Chapter 2. System Completion Codes 265
8C4 • 8C5
an explanation of the abend reason code. 11 An SRB mode caller requested a dynamic SSI
service
Application Programmer Response: If the error
recurs, search problem reporting data bases for a fix for 12 A caller holding a lock requested a dynamic
the problem. If no fix exists, contact the IBM Support SSI service.
Center.
13 An unexpected error was encountered in
validating the SSOB and SSIB provided as
8C4 input to a subsystem function request.
Explanation: During the processing of an automatic 14 An unauthorized caller of the IEFSSI query
restart manager function, JES detected an error. service requested that the information be
returned in storage obtained from an
Register 15 contains a hexadecimal reason code that
authorized subpool.
explains the error:
15 A caller in cross-memory mode requested a
Code Explanation
dynamic SSI service.
04 Unexpected return code from IEFSSREQ
System action: The system action depends on the
macro.
reason code:
System action: The system issues an SVC dump.
Code System Action
Application Programmer Response: Search problem
01, 03, 04, 06, 07
reporting data bases for a fix for the problem. If no fix
The system requests a dump and
exists, contact the IBM Support Center. Provide the
enters a permanent wait state (either
SVC dump.
code 00B or 00D).
Source: Functional subsystem interface (FSI)
05, 08, 13 A dump is produced. If these reason
codes occurred during system
8C5 initialization, the system may enter a
permanent wait state.
Explanation: The Subsystem Interface (SSI)
encountered a system or user error when either 10, 11, 12, 14, 15
initializing dynamic SSI services or responding to a A user error occurred. A dump is not
dynamic SSI service request issued through the IEFSSI produced.
or IEFSSVT macros.
Operator response: If the system enters a permanent
Register 15 contains a hexadecimal reason code that wait state, reIPL the system.
explains the error:
Application Programmer Response: The
Code Explanation programmer response depends on the reason code:
01 The system was unable to obtain storage for Code Programmer Response
the subsystem vector table (SSVT).
10, 11, 12, 15 Revise the program issuing either the
03 The system was unable to establish a PC entry IEFSSI macro or the IEFSSVT macro
table to support internal SSI services. to ensure that the correct environment
is established. Requestors must be
04 The system was unable to establish the PC unlocked, in task mode, may not be in
entry table to support the dynamic SSI cross-memory mode, and must be
services. authorized for all requests other than
05 An invalid request type was passed to an IEFSSI REQUEST=QUERY.
internal SSI or dynamic SSI service. 14 Change the requested subpool to an
06 The system was unable to obtain storage for unauthorized subpool.
internal SSI control structures. System programmer response: Analyze the dump to
07 The MSTR subsystem could not be initialized. determine why the system was unable to either obtain
storage, establish a PC entry table or establish an
08 An SSI routine was unable to establish an ESTAE.
ESTAE.
Source: Subsystem Interface (SSI)
10 An unauthorized caller requested a dynamic
SSI service. All dynamic SSI services with the
exception of the IEFSSI REQUEST=QUERY
require the caller to be authorized.
266 z/OS V1R10.0 MVS System Codes
8C6 • 8FB
return code from that processing, and register
8C6
3 contains the reason code.
Explanation: A program attempted to free a CIB
03 Module IATLVLC detected a subsystem
control block that was not properly chained for
interface error during storage management
execution.
subsystem (SMS) pre-locate catalog orientation
System action: The attempt is rejected, and the CIB processing. Register 2 contains the subsystem
is not freed. interface return code.
System programmer response: Using the information 05 While creating the system work area (SWA),
that was dumped for the abend (CIB and associated module IATIIII detected an error. The error
CSCB), identify the program that attempted to free the occurred when the module was either reading
CIB. Change the program to avoid chaining a CIB that or mapping SWA control blocks.
is not valid. IBM recommends using the MODIFY macro
06 Module IATDMGR detected an error in a JES3
for this purpose.
user spool access method (USAM) POINT or
Source: Master Scheduler Address Space/SVC 34 WRITE operation. Register 2 contains the
return code from the failing operation.
8C7 07 Module IATDMGR detected an error during the
initialization of either a data set status block
Explanation: MVS message service (MMS)
(DSS) or a data set block (DSB). Register 2
processing failed. Due to the error, MMS could not issue
contains the return code from the failing
an error message to explain the error. A hexadecimal
operation.
reason code in register 15 explains the reason that
MMS could not issue the error message. 08 Module IATDMGR detected a user spool
access method (USAM) buffer initialization
System action: The system abnormally ends all MMS
error. Register 2 contains the return code from
processing with completion code X'8C7'. MMS functions
the failing operation.
are not available. The system writes an SVC dump.
09 While incrementing the JCL statement count,
System programmer response: Search problem
module IATIICX detected an overflow condition.
reporting data bases for a fix for the problem. If no fix
exists, enter the IPCS VERBEXIT MMSDATA 0A Module IATLVLC detected a subsystem
subcommand to format the SVC dump. Contact the IBM interface error during storage management
Support Center. Provide the VERBEXIT MMSDATA subsystem (SMS) VOLREF services
output. Provide the reason code associated with the processing. Register 2 contains the subsystem
X'8C7' abend code. interface return code.
Source: MVS message service (MMS) 0C Module IATMDST detected a subsystem
interface error during storage management
subsystem (SMS) system select processing.
8FB
Register 2 contains the subsystem interface
Explanation: One of the following routines detected return code.
an error in a subtask:
0D SMS system select processing returned an
v Converter/interpreter (C/I)
unexpected return or reason code to module
v Locate
IATMDST. Register 2 contains the return code
v Main device scheduling (MDS)
from that processing, and register 3 contains
v JES3 interface
the reason code.
A hexadecimal reason code in register 15 explains the 0E Module IATSISA detected an error during a
error. PUT operation. Register 2 contains the return
code from that operation.
Code Explanation
0F The reader/interpreter passed an incorrect
01 Module IATIIPL detected a subsystem interface return code to JES3.
error during storage management subsystem
(SMS) pre-locate catalog orientation 10 Module IATIISP detected an error during a user
processing. Register 2 contains the subsystem spool access method (USAM) PUT operation.
interface return code.
11 Module IATDMGR detected an incorrect
02 Storage management subsystem (SMS) function code.
pre-locate catalog orientation processing
12 Module IATDMGR detected an error in the
returned an unexpected return or reason code
block spooler. Register 2 contains the return
to module IATIIPL. Register 2 contains the
code from the block spooler.
Chapter 2. System Completion Codes 267
8FB
13 Module IATLVLC detected an error in the block System action: The system action depends on the
spooler. Register 2 contains the return code abend reason code:
from the block spooler.
Code System Action
14 Module IATMDST detected an error in the
01, 02, 1D The system ends the generalized
block spooler. Register 2 contains the return
subtask; when the subtask’s ESTAE
code from the block spooler.
gets control, the system writes a
15 Module IATSISA detected an error during a dump. Then, with a DM146 abend, the
GET operation. Register 2 contains the return system fails the converter/interpreter
code from that operation. or postscan dynamic support program
(DSP) that was using the subtask.
16 Module IATLVLC detected that the ESTAE
Also, the system cancels with print the
service could not set up a recovery
job that the DSP was processing.
environment. Register 2 contains the return
code from that service. 03, 04, 06, 07, 08, 0A, 0B, 13, 18, 1A, 1B, 1C
The system ends the locate subtask;
17 Module IATMDST could not find a job data set
when the subtask’s ESTAE gets
(JDS) entry.
control, the system produces a dump.
18 Module IATLVLC either could not find a locate Then, the system cancels with print
request table (LVS), or encountered an the job that the subtask was
incorrect LVS entry. processing.
19 Module IATIIST detected an error during a PUT 05 The system ends the address space;
operation. when the ESTAE gets control, the
system produces a dump. Then, the
1A Storage management subsystem (SMS) system cancels with print the job that
VOLREF services returned incorrect was processing.
information to module IATLVLC.
09, 10, 19, 21 The system ends the
1C Catalog management (SVC 26) returned converter/interpreter (C/I) subtask.
incorrect information to module IATLVLC. When the subtask’s ESTAE receives
1D Module IATIIPL detected that the ESTAE control, the system produces a dump.
service could not set up a recovery Then, the system cancels and prints
environment. Register 2 contains the return the job that the subtask was
code from that service. processing and reinstates the subtask.
1F Invalid LRSIZE, larger than allowed maximum 0C, 0D, 14, 17, 22
issued by IATLVLC. The system ends the main device
scheduling (MDS) subtask. When the
20 Module IATIICX received a return code of 4 subtask’s ESTAE gets control, the
from IATUX03 indicating that the JCL limit has system produces a dump. Then, the
been exceeded. system either cancels and prints the
21 Module IATIIST detected a zero for the number job that the subtask was processing or
of systems eligible to access SMS resources places it on the MDS error queue. The
(field SSSABNUM in IEFSSSA). system reinstates the subtask.
22 Module IATMDST detected a zero for the 0E, 11, 12, 15 The system ends the subtask; when
number of systems eligible to access SMS the subtask’s ESTAE gets control, the
resources (field SSSACNUM in IEFSSSA). system writes a dump. Then, the
system cancels with print the job that
5E OAM or SMS subsystem called return code the subtask was processing.
nonzero.
0F The system ends the job and
5F OAM or SMS subsystem called SSOB return continues other processing.
code nonzero.
16 The system ends the locate subtask.
60 LIBSERV FUNC=build error.
Operator response: Save all associated print output,
61 LIBSERV FUNC=call error. and notify the system programmer.
62 LIBSERV FUNC=delete error. System programmer response: Obtain the JCL for
63 SMS subsystem called invalid subfunction. the job.
64 UCBLOOK failure. For a return code of X'05', rerun the job with the
DEBUG=ALL option after a //* PROCESS CI JECL
statement.
268 z/OS V1R10.0 MVS System Codes
905 • 90A
For a return code of X'21', examine the IEFSSSA data count (responsibility count), indicating the
area and determine the reason for the zero in the number of load requests for a module, is
SSSABNUM field. Also, examine the SSSABSAC and greater than the allowable maximum, which is
SSSABSAR fields (failing service return code and 32767.
reason code). Notify SMS support.
08 An error was detected during processing of a
For return code X'22', examine IEFSSSA and determine LINK(X), XCTL(X), ATTACH(X), or LOAD
the reason for the zero in the SSSACNUM field. Also, macro. The CDE (contents directory element)
examine the SSSACSAC and SSSACSAR fields (failing use count, indicating the number of LINK(X),
service return code and reason code). Notify SMS XCTL(X), ATTACH(X), or LOAD requests for a
support. module, is greater than the allowable
maximum, which is 32767.
For all other return codes, examine the print output to
find and correct the error. 0C The failing program has issued an XCTL(X)
request, but the program has an outstanding
If the problem occurs in JES3 and the return code is an
program linkage that has not completed
X'05' you should:
properly. This commonly occurs when a
v Obtain a stand-alone dump of the system by program issues a program call (PC) and then
specifying DUMP=PRDUMP on the OPTIONS issues an XCTL(X) request before issuing a
statement in the initialization deck. program return (PR).
v Save the hardcopy log
100 An error was detected during processing of a
v Provide a listing of the initialization deck (JESOUT) CSVINFO request. It was determined that an
v Determine the MVS and JES3 PTF levels Extent List (XTLST) control block contained
v Rerun the job with //*PROCESS CBPRINT and save incorrect information.
the output after interpreter DSP. System action: For reason codes X'04' X'08', the task
ends unless ERRET is specified on the macro. For
If the problem is not for X'05', check the JESYSMSG reason codes X'0C' and X'100', the request is
data set for error indications. terminated. The system issues a message depending
on the reason code accompanying the abend:
Source: JES3
Code Message/ABEND Type
905 04 CSV001I/ABDUMP
Explanation: An error occurred when the system tried 08 CSV002I/ABDUMP
to process an EC, EU, LC, LU, VC, or VU form of the
FREEMAIN macro. 0C CSV030I/ABDUMP
A reason code in the SDWACRC field of the system 100 /SVCDUMP
diagnostic work area (SDWA) explains the error: Application Programmer Response: Check for
Code Explanation program errors, such as endless loops, that cause
macros to be run too often. Ensure that the program
04 The virtual storage area that the FREEMAIN logic does not permit improper program linkage. After
macro tried to release is not on a double word making corrections, recompile and run the job step
boundary. again.
System action: The system issues message IEA705I. System programmer response: For reason code
The system abnormally ends the current task. X'100', contact the IBM Support Center. Provide the
dump and logrec entries associated with with abend.
Application Programmer Response: Check for
For the other reason codes, if the error recurs and the
program errors that incorrectly modify the macro
program is not in error, see the system programmer
expansion. Correct them. If necessary, change the
response for the messages in the job log.
program to request less virtual storage.
Source: Contents supervision (CSV)
Source: Virtual storage manager (VSM)
90A
906
Explanation: An error occurred when the system tried
Explanation: A reason code in register 15 identifies
to process an R form of the FREEMAIN macro. A
the error:
reason code in the SDWACRC field of the system
Code Explanation diagnostic work area (SDWA) explains the error:
04 An error was detected during the processing of Code Explanation
a LOAD macro. The LLE (load list element)
Chapter 2. System Completion Codes 269
913 • 92A
04 The virtual storage area that the FREEMAIN Application Programmer Response: Submit the job
macro tried to release is not on a doubleword again.
boundary.
System programmer response: Search problem
System action: The system issues message IEA705I. reporting data bases for a fix for the problem. If no fix
The system abnormally ends the current task. exists, contact the IBM Support Center, providing the
SVC dump and logrec data set error records.
Application Programmer Response: Check for
program errors that incorrectly modify the macro Source: Initiator/terminator
expansion. Correct them. If necessary, change the
Detecting Module: IEFIB621
program to request less virtual storage.
Source: Virtual storage manager (VSM)
92A
Explanation: During processing of an ATTACH macro,
913
an environmental error occurred that was not caused by
Explanation: The error occurred during processing of the current task.
an OPEN macro instruction. This system completion
Register 15 contains a hexadecimal reason code that
code is accompanied by message IEC150I. Refer to the
explains the error:
explanation of message IEC150I for complete
information about the task that was ended and for an Code Explanation
explanation of the return code in register 15.
00 An error occurred in the extended subtask
Application Programmer Response: Respond as ABEND exit (ESTAE) SVC issued to establish
indicated in message IEC150I. a recovery environment for ATTACH
processing.
System programmer response: If the error recurs
and the program is not in error, look at the messages in 04 Storage in subpool 255 was not available for
the job log for more information. Search problem the new supervisor request block (SVRB),
reporting data bases for a fix for the problem. If no fix subpool queue elements (SPQEs), and
exists, contact the IBM Support Center. Provide the JCL parameter save area.
and the program listing for the job.
08 An error occurred in SVC 60 (STAI/ESTAI)
Source: DFSMSdfp issued to propagate STAI/ESTAI storage
control blocks (SCBs) from the current task
control block (TCB) to the new TCB, and to
91A
build a new SCB if STAI or ESTAI was
Explanation: A request to abnormally end the catalog specified on the ATTACH macro. The SVC 60
address space (CAS) service task was issued either was a STAI entry if the STAI keyword was
through the MODIFY CATALOG,RESTART command, or specified on the ATTACH macro; otherwise, it
through catalog analysis task processing. is an ESTAI entry.
System action: The system re-drives the catalog 0C An error occurred when the system tried to
request currently in process. obtain the local lock.
Source: DFSMSdfp 10 An error occurred when SETLOCK was
entered to release the local lock.
922 14 The parameter list passed to ATTACH
processing contains an error.
Explanation: During initialization of a job step, after all
of the job step’s data sets had been allocated, or during 18 ATTACH is unable to obtain a linkage stack for
termination of a job step, before any of the job step’s the task.
data sets had been unallocated, the initiator’s ESTAE
System action: The system abnormally ends the
routine was invoked for one of the following conditions:
program that issued the ATTACH macro. The system
v An abend
does not create the new subtask.
v A program check
v Depression of the RESTART key Application Programmer Response: Run the job
v A machine check again. If the error recurs, notify the system programmer.
System action: The system ends the job step and System programmer response: Search problem
writes an SVC dump unless the ESTAE routine was reporting data bases for a fix for the problem. If no fix
entered recursively or was percolated to. The system exists, contact the IBM Support Center.
writes a logrec data set error record, except in the case
of an OPEN failure. Job processing continues, subject Source: Task management
to normal conditional processing.
270 z/OS V1R10.0 MVS System Codes
930 • 9C4
Code Explanation
930
04 The virtual storage area that the FREEMAIN
Explanation: A job issued an DEQ macro instruction
macro tried to release is not on a doubleword
that included the TCB operand. However, the TCB
boundary.
operand identified a task that was ending.
System action: The system issues message IEA705I.
System action: The system writes a logrec data set
The system abnormally ends the current task.
error record and issues an ABEND dump.
Application Programmer Response: Check for
Application Programmer Response: Determine why
program errors that incorrectly modify the macro
the task identified in the TCB operand was terminated.
expansion. Correct them. If necessary, change the
Correct that error and resubmit the job that caused the
program to request less virtual storage.
abend.
Source: Virtual storage manager (VSM)
System programmer response: If the problem
persists, search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support 9C4
Center. Provide the ABEND dump.
Explanation: An abend has been issued by the
Source: Global resource serialization system data mover function.
Register 15 contains one of the following reason codes.
937 You may also receive message ANTX5000E,
ANTX5001E, or ANTX5002E with this abend. These
Explanation: The error occurred at an end-of-volume
messages can contain information that is related to this
for a checkpoint data set or a RACF-protected data set.
abend code.
This system completion code is accompanied by
message IEC029I. Refer to the explanation of message Code Explanation
IEC029I for complete information about the task that
was terminated and for an explanation of the return 4 The ANTMAIN address space has restarted
code (rc in the message text) in register 15. due to an operator-initiated CANCEL
command, or due to an error condition that
System programmer response: See the system ended the session. The session can be a
programmer response for message IEC029I. concurrent copy, FlashCopy®, XRC, or PPRC
session. Any program that attempts to access
Source: Resource Access Control Facility (RACF)
the ANTMAIN address space is ended with this
abend condition. Check the results of the
938 ended jobs to determine if data movement was
successful before the jobs ended. Resubmit
Explanation: The job issued an ENQ macro
the job if data movement was unsuccessful.
instruction that included the TCB operand. However, the
TCB operand identified a task that was in the process of 8-100 The XRC function has detected an error that
ending. requires an abend dump to isolate the cause.
The reason codes contain specific diagnostic
System action: The system records the error in logrec
information to help isolate the specific error
data set and issues an ABEND dump.
condition. In all cases, data on the secondary
Application Programmer Response: Determine why volumes is preserved at a known consistent
the task identified in the TCB operand ended. Correct state as reported by XRC messages. A dump
that error and resubmit the job that caused the abend. is generated only if the XRCTRAP function is
ON.
System programmer response: If the problem
persists, search problem reporting data bases for a fix The following are some of the more common
for the problem. If no fix exists, contact the IBM Support reason codes for configuration ration-type
Center. Provide the ABEND dump. errors that can produce 9C4 abend dumps:
Source: Global resource serialization 10 A record from the storage control cannot
be found.
978 2C An invalid track format error has occurred
when writing to a secondary volume.
Explanation: An error occurred when the system tried
to process one of the following: 30
v A STORAGE macro 34 The data mover has not read from the
v An RC or RU form of the FREEMAIN macro storage control for at least the timeout
interval specified. The storage control
A reason code in the SDWACRC field of the system session has been canceled; all XRC
diagnostic work area (SDWA) explains the error:
Chapter 2. System Completion Codes 271
9C5 • 9C6
volume pairs associated with this storage pairs as a result of the error and the error level
control must be reinitialized. specified. You can usually issue an XADDPAIR
command to return the volume pairs to the session, and
38 A storage control logic error has occurred.
then resynchronize them. In some cases, you may need
54 A nonstandard Record 0 has been to issue the MODIFY ANTAS001,RESTART command,
detected on the primary volume. followed by XADDPAIR commands, to rebuild the failed
data mover sessions.
The reason codes indicate why the abend was Source: System data mover (ANT).
generated. In every case, data on the
secondary volumes is left in a consistent,
recoverable state. The following are some of 9C5
the reasons why a 9C4 can occur:
Explanation: A NetView® RODM abend occurred. The
v A volume has been initialized using an following reason codes describe the error:
XADDPAIR command with NOCOPY
specified, but the volume contents were not Code Explanation
identical. 0 RODM has cancelled the transaction based on
v The secondary volume has been updated by the reply to message EKG132D. Message
a function other than the data mover. The EKG1326D is issued when there are still
secondary volume must be dedicated to the transactions running in RODM during
data mover for all update operations. Other checkpoint or RODM termination.
functions may read the volume, but only the
System Action:Task is cancelled.
data mover can make updates.
v Multiple data movers are updating the 33 A RODM internal error has occurred.
secondary volume. It is possible that more System Action:Task is ended.
than one data mover is copying data to the
same secondary volume. Only one data System Programmer Response: Contact IBM
mover may have ownership of a secondary service for assistance.
volume.
v I/O has stopped in a subsystem. I/O may not 9C6
be active on a primary storage control,
secondary volumes, or journal volumes. Explanation: An error occurred when a task or SRB
Activity may be stopped because the routine called a global resource serialization latch
subsystem is not accepting I/Os or because manager service.
of a line failure in a channel extended Notes:
environment.
1. In the description of this system code, the term
v A session has been restarted after requestor refers to a task or SRB routine that calls a
maintenance has been applied to the data latch manager callable service to:
mover system. If incompatibilities exist in the v Request ownership of a latch, or
journal, state, or control data sets, a 9C4 v Release a granted or pending request to obtain
abend with reason codes 10 or 2C may ownership of a latch.
result. Ensure that the data sets have been
2. Equate symbols defined in the latch manager IDFs
properly allocated before starting or
are followed by their numeric equivalents; you may
restarting the data mover.
specify either when coding calls to Latch_Obtain.
System action: The system abnormally ends the task For example, “ISGLOBT_COND (value of 1)”
that encountered the abend condition. indicates the equate symbol ISGLOBT_COND and
its associated value, 1.
System programmer response: Register 15 contains
the nonzero return code that describes the reason the Source: Global resource serialization
abend was issued. The abend error may be the result of
General purpose register (GPR) 15 contains a
a hardware- or software-detected error. Search problem
hexadecimal reason code that explains the error. xxxx
reporting data bases for a solution. If no solution exists,
indicates internal information. If
contact the IBM Support Center. Provide the console
log, the dump data set, and the LOGREC data set error Code Explanation
record.
xxxxyyyy Some of the 9C6 reason codes
The data mover issues the 9C4 abend to freeze the indicate internal errors. If the high
environment for problem diagnosis, and to ensure that order bit is on in the second half of
the error does not result in data integrity errors. the reason code (xxxx8yyy, for
example), or if the reason code is not
In most cases, XRC suspends one or more volume
included in the following list, the error
272 z/OS V1R10.0 MVS System Codes
9C6
is an internal component error. Search v ISGLOBT_ASYNC_ECB (value of
problem data bases for any matching 2)
problems. If none found, report this
problem to your IBM support center. System Action: The latch manager
does not obtain the latch.
xxxx0001 A caller of a latch manager service
specified an incorrect value on the
latch_set_token parameter. Programmer Response: On the call
to the Latch_Obtain service, specify
System Action: The latch manager one of the values listed above on the
does not perform the requested obtain_option parameter.
operation.
xxxx0004 A caller of the Latch_Release service
Programmer Response: Specify a specified an incorrect value on the
latch_set_token value that was release_option parameter. The
returned by a previous call to the release_option must be
Latch_Create service. ISGLREL_UNCOND (value of 0) or
ISGLREL_COND (value of 1).
xxxx0002 One of the following occurred:
v The caller of the Latch_Create System Action: The latch manager
service specified an incorrect value does not release the latch.
on the number_of_latches Programmer Response: On the call
parameter. This value must be a to the Latch_Release service, specify
non-zero fullword integer. ISGLREL_UNCOND (value of 0) or
v The caller of the Latch_Obtain ISGLOBT_COND (value of 1) on the
service specified an incorrect value release_option parameter.
on the latch_number parameter.
The latch_number must be a xxxx0005 A caller of a latch manager service
fullword integer that is in the range specified an incorrect requestor_ID of
between 0 and the number of all binary zeroes. The requestor_ID
latches in the associated latch set can be any value except all binary
minus one. zeroes.
System Action: The latch manager
System Action: If the error occurred does not perform the requested
when calling the Latch_Create operation.
service, the system does not create
the latch set. If the error occurred Programmer Response: Specify a
when calling the Latch_Obtain requestor_ID that is not all binary
service, the latch manager does not zeroes.
obtain the latch. xxxx0006 A caller of the Latch_Obtain service
specified an obtain_option of
Programmer Response: ISGLOBT_ASYNC_ECB and an
v If the error occurred on a call to the ECB_address that was all binary
Latch_Create service, specify a zeroes. When the obtain_option is
non-zero fullword integer on the ISGLOBT_ASYNC_ECB, the
number_of_latches parameter. ECB_address must be a non-zero
address that points to an event control
v If the error occurred on a call to the
block (ECB).
Latch_Obtain service, specify a
value on the latch_number System Action: The latch manager
parameter in the range between 0 does not obtain the latch.
and the number of latches specified
on the call to the Latch_Create Programmer Response: Specify an
service. ECB_address that points to a valid
ECB.
xxxx0003 A caller of the Latch_Obtain service
specified an incorrect value on the xxxx0007 A caller of the Latch_Release service
obtain_option parameter. The specified a release_option of
obtain_option parameter must contain ISGLREL_UNCOND (value of 0). The
one of the following values: latch manager did not grant ownership
of the latch to the original caller of the
v ISGLOBT_SYNC (value of 0) Latch_Obtain service. The system did
v ISGLOBT_COND (value of 1)
Chapter 2. System Completion Codes 273
9C6
not post the ECB specified on the xxxx000B A requestor called a latch manager
original call to Latch_Obtain. service while disabled for I/O and
external interrupts.
System Action: The latch manager
does not release the latch. System Action: The latch manager
might not perform the requested
Programmer Response: Wait until
operation.
the system posts an ECB to indicate
that the caller of Latch_Obtain has Programmer Response: Call the
obtained the latch. Then call the latch manager service while enabled
Latch_Release service to release the for I/O or external interrupts.
latch.
xxxx000C A requestor called a latch manager
xxxx0008 A requestor called the Latch_Release service while in 24-bit addressing
service before the original caller of the mode.
Latch_Obtain service could obtain the
System Action: The latch manager
latch.
does not perform the requested
System Action: The latch manager operation.
does not obtain or release the latch.
Programmer Response: Call the
The Latch_Manager returns a return
latch manager service again while
code of 0 to the caller of
running in 31-bit addressing mode.
Latch_Release. The system passes
control to the recovery routine for the xxxx000D A requestor called a latch manager
caller of Latch_Obtain. service while holding a lock.
Programmer Response: Check the System Action: The latch manager
application code to ensure that the might not perform the requested
correct latch token is passed to the operation.
caller of the Latch_Release service.
Programmer Response: Issue the
xxxx0009 A caller of the Latch_Release service SETLOCK RELEASE macro to
specified a release_option of release the lock that the requestor
ISGLREL_UNCOND (value of 0). The currently holds.
latch manager did not grant ownership
of the latch to the original caller of the xxxx000E A requestor called a latch manager
Latch_Obtain service because the service while in access register (AR)
original caller is suspended while address space control (ASC) mode.
waiting to obtain the latch. System Action: The latch manager
System Action: The latch manager might not perform the requested
does not release the latch. operation.
Programmer Response: Check the Programmer Response: Call the
application code to ensure that the latch manager service again while
correct latch token is passed to the running in primary ASC mode.
caller of the Latch_Release service. xxxx000F One of the following:
xxxx000A A caller of the Latch_Release service v A requestor called the
specified a latch_token that: Latch_Release service and
v Did not match a latch_token specified an incorrect value on the
returned from the original call to the latch_token parameter
Latch_Obtain service, or v An internal error occurred in a latch
v Matched a latch_token for a latch manager service.
that was previously released or
purged. System Action: The latch manager
might not perform the requested
System Action: The latch manager operation.
does not release the latch.
Programmer Response: Check the
Programmer Response: On the call application code to ensure that the
to Latch_Release, specify a correct latch token is passed to the
latch_token that matches a valid caller of the Latch_Release service. If
latch_token. the problem persists, search problem
reporting data bases for a fix for the
274 z/OS V1R10.0 MVS System Codes
9C6
problem. If no fix exists, contact the value that had a first character of zero
IBM Support Center. or blank. The latch_set_name can
contain any 48-byte hexadecimal
xxxx0010 A requestor the Latch_Obtain service
value as long as the first character is
to obtain a latch. The requestor is
not binary zeroes or an EBCDIC
currently suspended and waiting for
blank.
the latch. The system is ending the
requestor because the latch set job System Action: The latch manager
step task (the task that created the does not create the latch set.
latch set) or latch set address space
Programmer Response: On the
(the address space in which the latch
latch_set_name parameter, specify a
set resides) is ending.
value with a first character is not
System Action: The latch manager binary zeroes or an EBCDIC blank.
does not obtain the latch.
xxxx0014 A caller of a latch manager service
Programmer Response: If has a PSW key that does not allow
necessary, call the Latch_Create access to the latch set storage.
service to create a new latch set.
System Action: The latch manager
xxxx0011 A requestor called the Latch_Create does not perform the requested
service to create a latch set. The operation.
maximum number of latch sets
Programmer Response: Call the
allowed by the system has been
latch manager service with a PSW
reached.
key that matches the storage key of
System Action: The latch manager the latch set.
does not create the latch set.
xxxx0015 An internal error occurred in a latch
Programmer Response: Identify manager service.
programs that are creating an
System Action: The latch manager
unnecessarily large number of latch
does not perform the requested
sets. Correct any problems with those
operation.
programs. If the problem persists,
contact the IBM Support Center. Programmer Response: Search
problem reporting data bases for a fix
xxxx0012 A requestor called the Latch_Create
for the problem. If no fix exists,
service with an incorrect value on the
contact the IBM Support Center.
create_option parameter. The
create_option must be a fullword xxxx0016 The system could not obtain enough
integer with one of the following storage for a particular latch set. GPR
values: 2 contains the return code from the
v ISGLCRT_PRIVATE (value of 0), STORAGE OBTAIN macro.
v ISGLCRT_PRIVATE + System Action: The latch manager
ISGLCRT_DEADLOCKDET1 (value does not create the latch set.
of 64), or
Programmer Response: See the
v ISGLCRT_PRIVATE + description of the return codes for the
ISGLCRT_DEADLOCKDET2 (value STORAGE OBTAIN macro in z/OS
of 128). MVS Programming: Authorized
Assembler Services Reference
System Action: The latch manager SET-WTO to diagnose the error.
does not create the latch set.
xxxx0017 A requestor called the Latch_Obtain
Programmer Response: Specify a service with an incorrect
valid create_option on the call to the access_option. The access_option
Latch_Create service. See z/OS MVS must be a fullword integer with a
Programming: Authorized Assembler value of ISGLOBT_EXCLUSIVE
Services Reference SET-WTO for (value of 0) or ISGLOBT_SHARED
more details on the valid (value of 1).
create_options. System Action: The latch manager
xxxx0013 On a call to the Latch_Create service, does not obtain the latch.
a requestor specified a
latch_set_name parameter with a
Chapter 2. System Completion Codes 275
9C6
Programmer Response: Specify an Programming: Authorized Assembler
access_option of Services Reference SET-WTO.
ISGLOBT_EXCLUSIVE (value of 0) or
xxxx0025 A caller of a 64-bit latch manager
ISGLOBT_SHARED (value of 1) on
service was not in 64-bit addressing
the call to the Latch_Obtain service.
mode.
xxxx0019 A requestor called the Latch_Obtain
System Action: The latch manager
service to obtain a latch. The
does not perform the requested
maximum number of Latch_Obtain
operation.
requests allowed by the system has
been reached. Programmer Response: Call the
latch manager service again while in
System Action: The latch manager
64-bit addressing mode.
does not obtain the latch.
xxxx002E A requestor called the Latch_Obtain
Programmer Response: Consider
service to obtain a latch, specifying an
placing limits or the number of tasks
access_option of
or SRB routines that can request
ISGLOBT_EXCLUSIVE (value of 0).
latches, or release held latches or
The latch has already been obtained
requests to obtain latches to reduce
by the same unit of work earlier with
contention for resources. If the
the ISGLOBT_EXCLUSIVE
problem persists, contact the IBM
access_option and it has not yet been
Support Center.
released.
xxxx0020 A requestor called the Latch_Obtain
service to obtain a latch. The Note: This reason code can only
requestor ended before the latch happen if the
manager could finish processing the ISGLCRT_DEADLOCKDET1
Latch_Obtain request. (value of 64) create_option is
specified in ISGLCRT.
System Action: The latch manager
does not obtain the latch.
System Action: The latch manager
Programmer Response: Call the does not perform the requested
Latch_Obtain service again, if the operation. Proceeding with the
requestor still requires access to the requested operation will result in a
latch. latch hang condition.
xxxx0023 A requestor called the Latch_Obtain
service to obtain a latch. The user Programmer Response: Check the
provided invalid latch information. application code to ensure that the
first latch has been released via the
System Action: The system Latch_Release service before the
terminates the request. second latch obtain request is issued.
Programmer Response: Correct your xxxx002F A requestor called the Latch_Obtain
parameters and call the Latch_Obtain service to obtain a latch, specifying an
service again. access_option of ISGLOBT_SHARED
(value of 1). The latch has already
xxxx0024 The system could not obtain enough
been obtained by the same unit of
storage for a particular latch request.
work earlier with the
GPR 2 contains the return code from
ISGLOBT_EXCLUSIVE access_option
the STORAGE OBTAIN macro.
(value of 0) and it has not yet been
System Action: The latch manager released.
does not perform the requested
operation. Note: This reason code can only
happen if the
Programmer Response: Call the
ISGLCRT_DEADLOCKDET1
latch manager service again while in
(value of 64) create_option is
64-bit addressing mode.
specified in ISGLCRT.
System Programmer Response: To
diagnose the error, see the description System Action: The latch manager
of the return codes for the STORAGE does not perform the requested
OBTAIN macro in z/OS MVS operation. Proceeding with the
276 z/OS V1R10.0 MVS System Codes
9C6
requested operation will result in a (value of 0) from
latch hang condition. within the
SUSPEND exit.
Programmer Response: Check the
20 An error occurred in
application code to ensure that the
the SUSPEND exit
first latch has been released via the
routine.
Latch_Release service before the
second latch obtain request is issued. 22 A system error
occurred.
xxxx0036 A requestor called the Latch_Obtain
service to obtain a latch, specifying an FE The system was not
access_option of able to
ISGLOBT_EXCLUSIVE (value of 0). PAUSE/SUSPEND
The latch has already been obtained because a
by the same unit of work earlier with PURGDEQ is
the ISGLOBT_SHARED pending against the
access_option (value of 1) and it has SRB. Only the
not yet been released. Purge, Release, or
conditional OBTAIN
Note: This reason code can only (ISGLOBT_COND
happen if the (value of 1)) can be
ISGLCRT_DEADLOCKDET2 used after an SRB
(value of 128) create_option is has a PURGDQ
specified in ISGLCRT. pending against it.
FF The requested
System Action: The latch manager function is not
does not perform the requested supported after an
operation. Proceeding with the SRB has abended
requested operation will result in a with X'47B'. Only the
latch hang condition. Purge, Release, or
conditional OBTAIN
Programmer Response: Check the (ISGLOBT_COND
application code to ensure that the (value of 1)) can be
first latch has been released via the used by an SRB
Latch_Release service before the that has been
second latch obtain request is issued. abended by a code
xxxx01yy A requestor called the Latch_Obtain X'47B'.
service to obtain a latch. The system
found an error when it tried to issue System Action: The latch manager
the SUSPEND macro. A return code does not obtain the latch.
from the SUSPEND macro (yy)
indicates the reason for the error: Programmer Response: Depending
on the return code from the
Code (yy) Explanation SUSPEND macro, do one of the
8 A program tried to following:
call the Code (yy) Action
Latch_Obtain
service with an 8 Correct the program
obtain option of so it does not try to
ISGLOBT_SYNC call the
(value of 0) from an Latch_Obtain
SRB after the SRB service with an
abended with code obtain option of
X'47B'. ISGLOBT_SYNC
(value of 0) from an
C A program tried to SRB that abended
call the with code X'47B'.
Latch_Obtain
service with an C Correct the program
obtain option of so it does not try to
ISGLOBT_SYNC call the
Chapter 2. System Completion Codes 277
9C7 • A00
Latch_Obtain 28 SUSERID has length greater than 8.
service with an
2C SNODE has length greater than 8.
obtain option of
ISGLOBT_SYNC 30 SGROUP has length greater than 8.
(value of 0) from
within the 34 TOKNOUT version is greater than the current
SUSPEND exit. maximum.
20, 22 Search problem System action: The system abnormally ends the task.
reporting data bases Application Programmer Response: This is possibly
for a fix for the a user error. Verify that the token interface is correct.
problem. If no fix
exists, contact the System programmer response: Check the reason
IBM Support Center. code and make sure you pass the correct token in the
request.
FE Terminate the SRB
processing so the Source: Resource Access Control Facility (RACF)
system can
complete the 9FB
PURGEDQ of the
SRB. Explanation: JES3 output service module IATOSDR
or IATOSPS abnormally ended an MVS service routine,
FF Correct the program usually SETPRT, in order to process a JES writer
so it does not try to function or an operator command. This completion code
call any service does not indicate a program failure.
other than Purge
and Release from System action: The system continues processing.
an SRB that Source: JES3
abended with code
X'47B'.
A00
For more information about the Explanation: During processing of an I/O request,
SUSPEND macro, see z/OS MVS execute channel program (EXCP) encountered an error
Programming: Authorized Assembler while an appendage was running. Each X'A00' abend
Services Reference SET-WTO. code has a reason code that shows which appendage
contained the error:
9C7 Code Explanation
Explanation: RACROUTE functions that use tokens 1 Program controlled interrupt (PCI) appendage
(such as VERIFY, VERIFYX, TOKENBLD, TOKENMAP)
abend 9C7 when an incorrect token is detected. 2 Start I/O (SIO) appendage
The following reason codes will be issued with abend 3 End of extent (EOE) appendage
9C7:
4 Channel end (CHE) normal end appendage
Code Explanation
5 Abnormal end (ABE) appendage
01 STOKEN area is too small.
6 Caller’s page fix appendage
02 TOKNIN area is too small.
System action: The system abnormally ends the
04 TOKNIN keyword is missing. current task. The system writes a logrec data set error
record and issues a SNAP dump.
08 TOKNOUT keyword is missing.
Application Programmer Response: If EXCP is
0C TOKNOUT area is too small. being used for I/O operations, this is an error in the
10 VERSION=0. appendage identified by the reason code. Fix the
appendage and run the job again. If the error persists,
14 USERID has length greater than 8. run the job again requesting an ABEND dump and then
18 PASSWORD has length greater than 8. notify the system programmer.
1C GROUPID has length greater than 8. System programmer response: In the dump, look at
field TCBEXCPD at offset X'C0' in the task control block
20 NEWPASSWORD has length greater than 8. (TCB) for the current task. TCBEXCPD points to the
24 EXENODE has length greater than 8. EXCP debugging area (XDBA). The XDBA contains
diagnostic data associated with the EXCP processor. To
278 z/OS V1R10.0 MVS System Codes
A03 • A05
determine which appendage was active, see the Support Center. Provide the dump.
microfiche mapping for data area XFRR of the
Source: Recovery termination manager (RTM)
EXCP/EXFR FRR parameter area.
If the error recurs and the program is not in error, look
A05
at the messages in the job log for more information.
Search problem reporting data bases for a fix for the Explanation: An error occurred when the system tried
problem. If no fix exists, contact the IBM Support to process an EC, EU, LC, LU, VC, or VU form of the
Center. Provide the logrec data set error record, the FREEMAIN macro. A reason code in the SDWACRC
JCL for the job, and the SNAP dump. field of the system diagnostic work area (SDWA)
explains the error.
Source: Execute channel program (EXCP)
Code Explanation
A03 04 The system queue area (SQA) storage to be
freed overlaps free storage.
Explanation: A task tried to end normally by issuing a
RETURN macro or by branching to the return address 08 The common service area (CSA) storage to be
in register 14. The task was not ready to end freed overlaps free storage.
processing because either:
0C The local system queue area (LSQA) storage
v The task had attached one or more subtasks that had to be freed overlaps free storage.
not ended.
v The task did not detach a subtask that it had 10 The private area storage to be freed overlaps
previously attached with the event control block free storage.
(ECB) option. 14 Part of the CSA to be freed is fixed.
System action: The system abends the task. 18 Part of the private area to be freed is fixed.
Operator response: If the system or application 1C The private area to be freed is associated with
programmer asks for an SVC dump, set the following a data-in-virtual object.
SLIP trap:
20 The private area to be freed has been
SLIP SET,COMP=A03,ACTION=SVCD,END
specified on the IARSUBSP IDENTIFY request,
Application Programmer Response: Do the and is eligible to be assigned to a subspace.
following:
24 The task or service request block (SRB)
1. If a dump is not produced with the abend, ask the routine tried to free SQA storage that either
operator to set a SLIP trap to obtain an SVC dump. overlaps free storage or was obtained by more
2. From the dump, identify the abnormally ended than one request.
module from the contents directory entry (CDE) or
28 The task or SRB routine tried to free CSA
from the PRBRSV field in the associated RB.
storage that either overlaps free storage or was
3. If the module is an installation-provided program, obtained by more than one request.
change the program so that, before the task ends,
all its subtasks will end. A task can determine that System action: The system issues message IEA705I.
its subtasks have ended by specifying event control The system abnormally ends the current task.
block (ECB) operands in ATTACH macros that Application Programmer Response: Do the
initiate the subtasks, and then issuing WAIT macros following:
that specify ECBs representing the end of its
v Ensure that the FREEMAIN operands do not specify
subtasks.
a different subpool and/or key than the subpool or
When the ECB option has been specified with the key of the storage you are trying to free.
ATTACH macro, the task must detach its subtask
v Ensure that the task control block (TCB) specified on
once notification of subtask ending has been
the FREEMAIN request is the same one specified on
received. Failure to do so will result in this abend.
the corresponding GETMAIN request.
If a WAIT macro had been issued and the ECBs
v If a caller running in supervisor state and key 0 made
indicated that all subtasks had ended, check for
the original GETMAIN request, ensure that the
program errors that incorrectly modified the WAIT
corresponding FREEMAIN request is also issued in
macros or ECBs.
supervisor state and key 0.
After making corrections, recompile the program.
If a caller in supervisor state and key 0 requests
Run the job step again.
storage in subpool 0 or 250, the system satisfies this
System programmer response: If the module is an request with storage from a different subpool. This
IBM program, search problem reporting data bases for a situation is described in z/OS MVS Diagnosis:
fix for the problem. If no fix exists, contact the IBM Reference.
Chapter 2. System Completion Codes 279
A06 • A13
v If the storage is eligible to be assigned to a 1C The private area to be freed is associated with
subspace, make the storage ineligible by specifying a data-in-virtual object.
the storage range on an IARSUBSP UNIDENTIFY
20 The private area to be freed has been
request before attempting to release the storage.
specified on the IARSUBSP IDENTIFY request,
v Check for program errors that incorrectly modify the and is eligible to be assigned to a subspace.
FREEMAIN macro expansion.
24 The task or service request block (SRB)
Source: Virtual storage manager (VSM) routine tried to free SQA storage that either
overlaps free storage or was obtained by more
A06 than one request.
Explanation: The error was detected during 28 The task or SRB routine tried to free CSA
processing of either a LINK(X), LOAD, XCTL(X) or storage that either overlaps free storage or was
ATTACH(X) macro instruction. obtained by more than one request.
Code Explanation System action: The system issues message IEA705I.
The system abnormally ends the current task.
04 A request block (RB) is requesting a serially
reusable program. Another RB associated with Application Programmer Response: Do the
the task requested the same program, and that following:
request has not yet been satisfied. v Ensure that the FREEMAIN operands do not specify
a different subpool and/or key than the subpool or
System action: The task ends unless ERRET is
key of the storage you are trying to free.
specified on the macro. The system issues message
CSV000I. The system issues an ABEND dump. v Ensure that the task control block (TCB) specified on
the FREEMAIN request is the same one specified on
Application Programmer Response: Change the the corresponding GETMAIN request.
program to wait until the serially reusable load module
v If a caller running in supervisor state and key 0 made
is run before issuing the LINK(X), LOAD, XCTL(X) or
the original GETMAIN request, ensure that the
ATTACH(X) macro for the load module. After making
corresponding FREEMAIN request is also issued in
corrections, recompile and run the job step again.
supervisor state and key 0.
System programmer response: If the error recurs If a caller in supervisor state and key 0 requests
and the program is not in error, see the system storage in subpool 0 or 250, the system satisfies this
programmer for the messages in the job log. request with storage from a different subpool. This
If the problem persists, search problem reporting data situation is described in z/OS MVS Diagnosis:
bases for a fix for the problem. If no fix exists, contact Reference.
the IBM Support Center. Provide the ABEND dump and v If the storage is eligible to be assigned to a
the source program listing for the job. subspace, make the storage ineligible by specifying
the storage range on an IARSUBSP UNIDENTIFY
Source: Contents supervision (CSV) request before attempting to release the storage.
v Check for program errors that incorrectly modify the
A0A FREEMAIN macro expansion.
Explanation: An error occurred when the system tried Source: Virtual storage manager (VSM)
to process an R form of the FREEMAIN macro. A
reason code in the SDWACRC field of the system
diagnostic work area (SDWA) explains the error: A13
Code Explanation Explanation: The error occurred during processing of
an OPEN macro instruction for a data set on magnetic
04 The system queue area (SQA) storage to be tape. This system completion code is accompanied by
freed overlaps free storage. message IEC151I. Refer to the explanation of message
IEC151I for complete information about the task that
08 The common service area (CSA) storage to be
was ended and for an explanation of the return code (rc
freed overlaps free storage.
in the message text) in register 15.
0C The local system queue area (LSQA) storage
Application Programmer Response: Respond as
to be freed overlaps free storage.
indicated for message IEC151I.
10 The private area storage to be freed overlaps
System programmer response: If the error recurs
free storage.
and the program is not in error, look at the messages in
14 Part of the CSA to be freed is fixed. the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix
18 Part of the private area to be freed is fixed.
exists, contact the IBM Support Center. Provide the JCL
280 z/OS V1R10.0 MVS System Codes
A14 • A37
and the program listing for the job.
A22
Source: DFSMSdfp
Explanation: A FORCE command requested that a
job be canceled, possibly for one of these reasons:
A14 v The CANCEL command could not cancel the job.
Explanation: The error occurred during processing of v The system was in a deadlock. For example, two
a CLOSE macro instruction for a data set on a direct tasks were enqueued on a resource without an
access device. This system completion code is intervening dequeue.
accompanied by message IEC216I. Refer to the v An installation-established procedure was violated by
explanation of message IEC216I for complete the job.
information about the task that was ended and for an
explanation of the return code (rc in the message text) There may be nothing wrong with the job itself.
in register 15.
System action: The system ends the address space
Application Programmer Response: Respond as associated with the job. The system ends all tasks
indicated for message IEC216I. running in the address space.
System programmer response: If the error recurs Application Programmer Response: Find out why
and the program is not in error, look at the messages in the operator canceled the job and make any necessary
the job log for more information. Search problem corrections. Rerun the job, ensuring that the operator
reporting data bases for a fix for the problem. If no fix enters a CANCEL jjj,DUMP command, if necessary.
exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job. Source: Reconfiguration
Source: DFSMSdfp
A23
A1A Explanation: The system was trying to process a
macro instruction issued by the communications task
Explanation: The catalog address space (CAS) (COMMTASK). An error occurred because an incorrect
modify task ended abnormally because the modify task address was specified.
exceeded the allotted time for processing. The task may
have been waiting for some system resource that is System action: The system issues messages about
permanently unavailable. the problem.
System action: The system attaches a new task to Application Programmer Response: Run the job
restore the modify function. again. If the error persists, contact the system
programmer.
Source: DFSMSdfp
System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
A1C exists, contact the IBM Support Center.
Explanation: The Device Manager Address Space | Source: Console services
(DEVMAN) encountered an unexpected error. The
reason code is in register 15 at the time the system
issues the abend. A37
Code Explanation Explanation: The error occurred during end-of-volume
processing. This system completion code is
0001 The DEVMAN VTOC Convert Routine call to accompanied by message IEC015I. Refer to the
UCBLOOK failed. explanation of message IEC015I for complete
0002 The DEVMAN VTOC Convert Routine call to information about the task that was ended and for an
DSPSERV to extend the data space failed. explanation of the return code (rc in the message text)
in register 15.
0003 The DEVMAN VTOC Convert Routine
encountered an unexpected error processing Operator response: Start a generalized trace facility
the VTOC DSCBs. (GTF) trace, and re-create the problem. Reply to
message AHL100A with:
System action: The system writes an SVC Dump.
TRACE=SYS,USR,SLIP
System programmer response: Contact the IBM
Support Center On the DD statement for the data set in error, specify:
Source: DFSMSdfp DCB=DIAGNS=TRACE
Application Programmer Response: Respond as
Chapter 2. System Completion Codes 281
A78 • AC4
indicated for message IEC015I. v Ensure that the FREEMAIN or STORAGE RELEASE
operands do not specify a different subpool and/or
System programmer response: If the error recurs
key than the subpool or key of the storage you are
and the program is not in error, look at the messages in
trying to free.
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix v Ensure that the task control block (TCB) specified on
exists, contact the IBM Support Center. Provide the the FREEMAIN or STORAGE RELEASE request is
SYSOUT output and the program listing for the job. the same one specified on the corresponding
GETMAIN or STORAGE OBTAIN request.
Source: DFSMSdfp
v If a caller running in supervisor state and key 0 made
the original GETMAIN or STORAGE OBTAIN
A78 request, ensure that the corresponding FREEMAIN or
STORAGE RELEASE request is also issued in
Explanation: An error occurred when the system tried supervisor state and key 0.
to process an RU or RC form of the FREEMAIN macro
or the STORAGE RELEASE macro. A reason code in If a caller in supervisor state and key 0 requests
the SDWACRC field of the system diagnostic work area storage in subpool 0 or 250, the system satisfies this
(SDWA) explains the error: request with storage from a different subpool. This
situation is described in z/OS MVS Diagnosis:
Code Explanation Reference.
04 The system queue area (SQA) storage to be v If the storage is eligible to be assigned to a
freed overlaps free storage. subspace, make the storage ineligible by specifying
the storage range on an IARSUBSP UNIDENTIFY
08 The common service area (CSA) storage to be request before attempting to release the storage.
freed overlaps free storage.
v Check for program errors that incorrectly modify the
0C The local system queue area (LSQA) storage FREEMAIN or STORAGE RELEASE macro
to be freed overlaps free storage. expansion.
10 The private area storage to be freed overlaps Source: Virtual storage manager (VSM)
free storage.
14 Part of the CSA to be freed is fixed. A7A
18 Part of the private area to be freed is fixed. Explanation: The system detected an error in the
input from an invoker of the Service Processor
1C The private area to be freed is associated with
Interface, or an internal error in MVS. Register 15
a data-in-virtual object.
contains the reason code in the format X'0000xxrr',
20 The private area to be freed has been where rr is the reason code.
specified on the IARSUBSP IDENTIFY request,
Code Explanation
and is eligible to be assigned to a subspace.
06 The Service Processor Interface is unable to
24 The task or SRB routine tried to free either
establish the recovery environment.
SQA storage that overlaps free storage or SQA
storage that was obtained by more than one Others The Service Processor Interface detected an
request. unrecoverable error.
28 The task or SRB routine tried to free either System action: The system abnormally ends the
CSA storage that overlaps free storage or CSA invoker of the Service Processor Interface.
storage that was obtained by more than one
System programmer response: For reason code
request.
X'06', determine why the system could not establish a
System action: The system issues message IEA705I. recovery environment. If this cannot be done, or if the
The system abnormally ends the current task. reason code is other than one previously listed, search
problem reporting data bases for a fix. If no fix exists,
Application Programmer Response: Do the
contact the IBM Support Center.
following:
v For reason code X'1C', ensure that the program Source: Service Processor Interface
issued a DIV UNIDENTIFY request before any
FREEMAIN or STORAGE RELEASE request. AC4
v For reason code X'24' or X'28', ensure that the start
Explanation: JES3 encountered an error while
address, length and subpool specified on the
processing an IATXCNDB service call which specified
FREEMAIN or STORAGE RELEASE macro do not
(or defaulted to) ABEND=YES. The abend reason code
contain errors.
identifies the specific error.
282 z/OS V1R10.0 MVS System Codes
AC4
Code Explanation 3C The input IATYCNDB (CNDB parameter)
passed to the IATXCNDB TRANSCONSID
00 Operation was successfully performed.
service did not have ’CNDB’ as its eyecatcher.
04 The OPERATION requested is not supported
40 The output IATYCNDB (OUTCNDB parameter)
by the IATXCNDB macro.
address passed to the IATXCNDB
08 An invalid IATXCNDB parameter list was TRANSCONSID service was zero.
passed to the IATCNDB module. The
44 The input IATYCNDB (CNDB parameter)
eyecatcher in the parameter list is not ’YCNDB
address passed to the IATXCNDB
’
TRANSROUT service was zero.
0C An invalid IATXCNDB parameter list was
48 The input IATYCNDB (CNDB parameter)
passed to the IATCNDB module. The version
passed to the IATXCNDB TRANSROUT
indicator in the parameter list was not equal to
service did not have ’CNDB’ as its eyecatcher.
the the current version.
4C The output IATYCNDB (OUTCNDB parameter)
10 The input IATYCNDB (INCNDB parameter)
address passed to the IATXCNDB
passed to the IATXCNDB INITIALIZE service
TRANSROUT service was zero.
did not have ’CNDB’ as its eyecatcher.
50 The input IATYCNDB (CNDB parameter)
14 The console id and console name parameters
address passed to the IATXCNDB
were passed to the INITIALIZE service. These
EXTRACTCONSID service was zero.
parameters are mutually exclusive.
54 The input IATYCNDB (CNDB parameter)
18 An error return (>4) was received from the call
passed to the IATXCNDB EXTRACTCONSID
to CONVCON by the IATXCNDB INITIALIZE
service did not have ’CNDB’ as its eyecatcher.
operation.
58 The OUTCONSID address passed to the
1C The IATYCNDB was successfully initialized, but
IATXCNDB EXTRACTCONSID service was
the console name/ID passed to the INITIALIZE
zero.
routine was not found in the JES3 console
table. The IATYCNDB has been initialized with 5C The input IATYCNDB (CNDB parameter)
a ″non-JES3″ console type and the console ID address passed to the IATXCNDB
and console name passed on the IATXCNDB EXTRACTCONSNAME service was zero.
invocation and returned by MCS.
60 The input IATYCNDB (CNDB parameter)
20 The input IATYCNDB (CNDB parameter) passed to the IATXCNDB
address passed to the IATXCNDB TRANSFER EXTRACTCONSNAME service did not have
service was zero. ’CNDB’ as its eyecatcher.
24 The input IATYCNDB (CNDB parameter) 64 The OUTCONSNAME address passed to the
passed to the IATXCNDB TRANSFER service IATXCNDB EXTRACTCONSNAME service
did not have ’CNDB’ as its eyecatcher. was zero.
28 The output IATYCNDB (OUTCNDB parameter) 68 The input IATYCNDB (CNDB parameter)
address passed to the IATXCNDB TRANSFER address passed to the IATXCNDB
service was zero. EXTRACTCONSTYPE service was zero.
2C The IATYCNDB passed to the VERIFY service 6C The input IATYCNDB (CNDB parameter)
did not have ’CNDB’ as its eyecatcher. passed to the IATXCNDB
EXTRACTCONSTYPE service did not have
30 An error return (>4) was received from the call
’CNDB’ as its eyecatcher.
to CONVCON by the IATXCNDB service
VERIFY operation. 70 The OUTCONSTYPE address passed to the
IATXCNDB EXTRACTCONSTYPE service was
34 The IATYCNDB was successfully converted to
zero.
an IATYCNDB at the current release level, but
the console name in the down level CNDB was 74 The input IATYCNDB (CNDB parameter)
not found in the JES3 console table. The address passed to the IATXCNDB
IATYCNDB has been initialized with a EXTRACTROUT service was zero.
″non-JES3″ console type and the console ID
78 The input IATYCNDB (CNDB parameter)
returned by MCS.
passed to the IATXCNDB EXTRACTROUT
38 The input IATYCNDB (CNDB parameter) service did not have ’CNDB’ as its eyecatcher.
address passed to the IATXCNDB
7C The OUTROUT address passed to the
TRANSCONSID service was zero.
IATXCNDB EXTRACTROUT service was zero.
Chapter 2. System Completion Codes 283
AC5 • AC6
80 The input IATYCNDB (CNDB parameter) 6. Correct the parameter list in the module that issued
address passed to the IATXCNDB UPDATE the IATXCNDB macro.
service was zero.
Source: JES3
84 The input IATYCNDB (CNDB parameter)
passed to the IATXCNDB UPDATE service did
AC5
not have ’CNDB’ as its eyecatcher.
Explanation: An unexpected error was encountered
88 An attempt was made to pass the CONSID
during internal RACF processing datasharing or sysplex
and CONSNM parameters to the IATXCNDB
communication functions. A hexadecimal reason code is
service for an UPDATE operation. These
given in register 15.
parameters are mutually exclusive.
Code Explanation
8C An error return (>4) was received from the call
to CONVCON by the IATXCNDB UPDATE 03 An error occurred when attempting to obtain
operation. storage.
90 The IATYCNDB was successfully updated, but 05 An error occurred when attempting to free
the console name/ID passed to the UPDATE storage.
routine was not found in the JES3 console
table. The IATYCNDB has been Updated with 07 After IXCJOIN, all other members left the data
a ″non-JES3″ console type and the console ID sharing group before the group data set name
and console name passed on the IATXCNDB and range table were received. One reason
invocation and returned by MCS. this can happen is that you are IPLing a
system and all other systems in the group were
94 The input IATYCNDB (CNDB parameter) simultaneously re-IPLed. If this is the case,
address passed to the IATXCNDB RESET re-IPL your system. Otherwise, contact the IBM
service was zero. support center.
98 The input IATYCNDB (CNDB parameter) 08 An XCF service failed during sysplex
passed to the IATXCNDB RESET service did communication.
not have ’CNDB’ as its eyecatcher.
0F XCF services failed. RACF will try to restart the
A8 The input IATYCNDB (CNDB parameter) RACF datasharing address space.
address passed to the IATXCNDB
EXTRACTCART service was zero. 10 This abend occurs when a system in
datasharing mode is put into failsoft mode due
AC The input IATYCNDB (CNDB parameter) to the occurrence of some other error.
passed to the IATXCNDB EXTRACTCART
service did not have ’CNDB’ as its eyecatcher. nn An internal RACF error has occurred. Contact
the IBM support center.
B0 The OUTROUT address passed to the
IATXCNDB EXTRACTCART service was zero. System action: A dump is taken in all cases. If the
abend occurs in the RACF data sharing address space,
System action: The IATXCNDB request processing is the address space will be restarted. If the abend occurs
ended. in the master address space, the system will enter
failsoft mode.
System programmer response: To determine the
error, perform the following: Application Programmer Response: If the abend
1. If called from the JES3 main task, locate the ACALL occurred in the master address space, the system will
and RETURN trace entry for the IATXCNDB macro. need to be re-IPLed in order for RACF to be made
active again. If necessary, contact your programming
2. Register 1 of the ACALL trace entry contains the
support personnel.
address of the parameter list used by the
IATXCNDB macro. The parameter list is mapped by
a DSECT generated from an IATXCNDB MF=L call. AC6
3. Use the trace table to locate the module that issued Explanation: IMS uses this code when forcibly
the IATXCNDB macro. Register 14 of the ACALL terminating one MVS task from another MVS task.
entry in the trace table contains the return address There are two situations where this occurs:
and register 10 contains the base register.
1. An ESTAE routine has gained control due to an
4. When IATXCNDB is invoked from a user’s address abend in the system. The abended task (ESTAE)
space, the caller issued a BASSM R14,R15 from the attempts to purge the log buffers and signals the
IATXCNDB macro. The registers are then saved on physical log task of its intention. If the ESTAE task
the linkage stack by IATCNDB via ’BAKR R14,R0’. does not receive a response within one second, the
5. Use the abend reason code to identify the cause of physical log task is terminated with this abend code
the error. and log buffers are purged.
284 z/OS V1R10.0 MVS System Codes
AC7
2. The DBRC instance required for this instance of ILS Action: Contact the IBM support
has terminated. All remaining ILS instances center.
dependent upon the abended DBRC will wait for
00010000 Explanation: The IEAMCPUF macro
that DBRC and abend with reason code X'01'.
was issued by an enabled caller.
System action: IMS continues termination.
Action: Correct the program so that
System programmer response: Determine primary IEAMCPUF is issued while running
cause of failure and take appropriate action. disabled.
00020000 Explanation: The affinity service,
AC7 IEAAFFN, was invoked by a caller in
access register (AR) mode.
Explanation: A supervisor service was issued in an
incorrect environment. Register 15 contains a Action Correct the program so that
hexadecimal reason code. IEAAFFN is invoked in primary ASC
mode.
System action: The system ends the current unit of
work. 00020001 Explanation: The affinity service,
IEAAFFN, could not access the
Application Programmer Response: Respond
storage containing the caller’s
according to the reason code:
parameter list.
Code Explanation/Programmer Response
Action: Correct the program so that
00000000 Explanation: The caller of the the storage containing the caller’s
enqueue timer queue element (TQE) parameter list is accessible.
service did not hold the dispatcher
00030000 Explanation: A name/token callable
lock.
service, IEANTCRS or IEANTDLS,
Action: Correct the program to obtain could not access the storage
the dispatcher lock before calling the containing the caller’s parameter list
enqueue TQE service. or parameter storage.
00000001 Explanation: The caller of the Action: Correct the program so that
dequeue TQE service did not hold the the storage containing the caller’s
dispatcher lock. parameter list or parameter storage is
accessible.
Action: Correct the program to obtain
the dispatcher lock before calling the 00030001 Explanation: A name/token callable
dequeue TQE service. service, IEANTCRS or IEANTDLS,
could not access the caller’s home
00000002 Explanation: The STIMER/STIMERM address space.
service detected an error when
processing an STIMER/STIMERM Action: Retry the request.
WAIT request.
00030002 Explanation: The name/token pair
Action: Contact the IBM Support callable service, IEANTDLS, found an
Center. internal error.
00000003 Explanation: An enqueue request for Action: Retry the request.
a TQE failed because the TQE to be
00040000 Explanation: Internal error.
added is already on the real TQE
queue. The original STIMER or Action: Contact the IBM support
SETDIE request represented by this center.
TQE will not occur. For this reason
00040001 Explanation: Internal error.
code, register 2 contains the address
of the caller of Timer services. Action: Contact the IBM support
center.
Action: Correct the program to not
schedule the same TQE twice. 00040002 Explanation: Internal error.
00000004 Explanation: Internal error Action: Contact the IBM support
center.
Action: Contact the IBM support
center. 00040003 Explanation: Internal error.
00000005 Explanation: Internal error Action: Contact the IBM support
center.
Chapter 2. System Completion Codes 285
AC7
00040004 Explanation: Internal error. 00050005 Explanation: The caller of the
SCHEDIRB macro scheduled a
Action: Contact the IBM support
directed IRB to the current task.
center.
However, the current task is an error
00040005 Explanation: Internal error. task and the error IRB is active.
Action: Contact the IBM support Action: Correct the program so that it
center. does not specify the RBPTR keyword
on the SCHEDIRB if the current task
00050000 Explanation: The caller of the is the error task and the error IRB is
SCHEDIRB macro did not hold the active.
local lock.
00050006 Explanation: The caller of the
Action: Correct the program so that it SCHEDIRB macro specified and IQE
holds the local lock before invoking whose IQETCB field pointed to a TCB
the SCHEDIRB macro. which is not valid.
00050001 Explanation: A program invoked the Action: Correct the program so that it
SCHEDIRB macro with one of the specifies a valid TCB address in the
following errors: IQE field IQETCB.
v The caller’s cross memory mode
was not HASN=PASN, which is 00060000 Explanation: Internal error
required. Action: Contact the IBM support
v The caller’s ASC mode of AR was center.
correct, but AR1 does not contain
00070000 Explanation: The request block (RB)
the primary ALET.
chain is circular or there are a very
large number or RBs on the RB chain.
Action: Correct the program so that
the cross memory mode is Action: This may be caused by a
HASN=PASN or PASN=HASN. loop which caused many RBs to be
created. If the source of the problem
00050002 Explanation: The caller of the cannot be determined, search problem
SCHEDIRB macro specified the reporting data bases for a fix of the
RBPTR keyword to schedule a problem. If no fix exits, contact the
directed interrupt request block (IRB) IBM support center.
while in SRB mode. The calling
program cannot schedule directed 00080001 Explanation: The space token
IRBs while in SRB mode. specified via the TARGETSTOKEN
keyword on IEAMSCHD is not valid.
Action: Correct the program so that it
is not in SRB mode if you want to Action: Retry the request specifying a
specify the RBPTR keyword on the valid address space token.
SCHEDIRB macro to schedule a
00080002 Explanation: The enclave token
directed IRB.
specified on IEAMSCHD was not a
00050003 Explanation: The caller of the valid token.
SCHEDIRB macro specified an
Action: Retry the request specifying a
incorrect task control block (TCB)
valid enclave token.
address on the TCBPTR keyword.
00080003 Explanation: CRYPTO was specified
Action: Correct the program so that it
on the FEATURE keyword of
specifies a valid TCB address in the
IEAMSCHD, but there are no
TCBPTR keyword on the SCHEDIRB
processors with the Integrated
macro.
Cryptographic Feature online.
00050004 Explanation: The caller of the
Action:
SCHEDIRB macro specified an
incorrect interrupt queue element 00080004 Explanation: A DIE routine issued
(IQE) address on the IQEPTR IEAMSCHD to attempt to schedule an
keyword. SRB with PRIORITY=CURRENT.
Action: Correct the program so that it Action: Correct the program so that
specifies a valid IQE address on the the routine does not specify
IQEPTR keyword on the SCHEDIRB PRIORITY=CURRENT on
macro. IEAMSCHD.
286 z/OS V1R10.0 MVS System Codes
AC7
00080005 Explanation: The space token reason may be that the SCHEDULE
specified via the PURGESTOKEN macro was issued more than once for
keyword on IEAMSCHD is not valid. an SRB.
Action: Retry the request specifying a Action: Ensure that the program does
valid PURGESTOKEN token. not issue SCHEDULE for the SRB
again before the SRB is dispatched.
00080006 Explanation: The space token
General purpose register 3 points to
specified via the CLIENTSTOKEN
the SRB.
keyword on IEAMSCHD is not valid.
000D0001 Explanation The PURGEDQ macro
Action: Retry the request specifying a
detected a circular SRB chain. The
valid CLIENTSTOKEN.
reason may be that the SCHEDULE
00080007 Explanation: The parameter list for macro was issued more than once for
IEAMSCHD is not in the user’s an SRB.
primary address space.
Action: Ensure that the program does
Action: Correct the program so that not issue SCHEDULE for the SRB
the parameter list is addressable. again before the SRB is dispatched.
General purpose register 3 points to
00080009 Explanation: The caller of the SRB.
IEAMSCHD specified SYNCH=YES
but held a lock. 000D0002 Explanation: Internal error
Action: Ensure that no locks are held Action: Contact the IBM support
when SYNCH=YES is specified on center.
IEAMSCHD.
000D0003 Explanation: The SCHEDULE macro
00090000 Explanation: Internal error detected an SRB which is not valid.
The reason may be that the
Action: Contact the IBM support SCHEDULE macro was issued more
center. than once for an SRB.
00090001 Explanation: Internal error Action: Ensure that the program does
Action: Contact the IBM support not issue SCHEDULE for the SRB
center. again before the SRB is dispatched.
The SRB and the associated WEB are
00090002 Explanation: Internal error recorded in LOGREC.
Action: Contact the IBM support 000E0000 Explanation: Internal error
center.
Action: Contact the IBM support
00090003 Explanation: Internal error center.
Action: Contact the IBM support 000E0001 Explanation: Internal error
center.
Action: Contact the IBM support
000A0000 Explanation: Internal error center.
Action: Contact the IBM support 000E0002 Explanation: Internal error
center.
Action: Contact the IBM support
000B0000 Explanation: Internal error center.
Action: Contact the IBM support 000F0000 Explanation: Internal error
center.
Action: Contact the IBM support
000C0000 Explanation: Internal error center.
Action: Contact the IBM support 00100000 Explanation: Internal error
center.
Action: Contact the IBM support
000C0001 Explanation: Internal error center.
Action: Contact the IBM support 00100001 Explanation: Internal error
center.
Action: Contact the IBM support
000D0000 Explanation The SCHEDULE macro center.
detected a circular SRB chain. The
00110000 Explanation: For a call to the
Chapter 2. System Completion Codes 287
AC7
Begin_Context service, the are not in the primary address space.
parameters are not in the primary The system rejects the service call.
address space. The system rejects The system abnormally ends the
the service call. The system calling program.
abnormally ends the calling program.
Action: Check the calling program for
Action: Check the calling program for a probable coding error. Correct the
a probable coding error. Correct the program and rerun it.
program and rerun it.
00140001 Explanation: For a call to the
00110001 Explanation: For a call to the End_Context service, the parameters
Begin_Context service, the are not addressable. The system
parameters are not addressable. The rejects the service call. The system
system rejects the service call. The abnormally ends the calling program.
system abnormally ends the calling
Action: Check the calling program for
program.
a probable coding error. Correct the
Action: Check the calling program for program and rerun it.
a probable coding error. Correct the
00150000 Explanation: For a call to the
program and rerun it.
Switch_Context service, the
00120000 Explanation: For a call to the parameters are not in the primary
Delete_Context_Interest service, the address space. The system rejects
parameters are not in the primary the service call. The system
address space. The system rejects abnormally ends the calling program.
the service call. The system
Action: Check the calling program for
abnormally ends the calling program.
a probable coding error. Correct the
Action: Check the calling program for program and rerun it.
a probable coding error. Correct the
00150001 Explanation: For a call to the
program and rerun it.
Switch_Context service, the
00120001 Explanation: For a call to the parameters are not addressable. The
Delete_Context_Interest service, the system rejects the service call. The
parameters are not addressable. The system abnormally ends the calling
system rejects the service call. The program.
system abnormally ends the calling
Action: Check the calling program for
program.
a probable coding error. Correct the
Action: Check the calling program for program and rerun it.
a probable coding error. Correct the
00160000 Explanation: For a call to the
program and rerun it.
Retrieve_Context_Interest_Data
00130000 Explanation: For a call to the service, the parameters are not in the
Express_Context_Interest service, the primary address space. The system
parameters are not in the primary rejects the service call. The system
address space. The system rejects abnormally ends the calling program.
the service call. The system
Action: Check the calling program for
abnormally ends the calling program.
a probable coding error. Correct the
Action: Check the calling program for program and rerun it.
a probable coding error. Correct the
00160001 Explanation: For a call to the
program and rerun it.
Retrieve_Context_Interest_Data
00130001 Explanation: For a call to the service, the parameters are not
Express_Context_Interest service, the addressable. The system rejects the
parameters are not addressable. The service call. The system abnormally
system rejects the service call. The ends the calling program.
system abnormally ends the calling
Action: Check the calling program for
program.
a probable coding error. Correct the
Action: Check the calling program for program and rerun it.
a probable coding error. Correct the
00170000 Explanation: For a call to the
program and rerun it.
Set_Context_Interest_Data service,
00140000 Explanation: For a call to the the parameters are not in the primary
End_Context service, the parameters address space. The system rejects
288 z/OS V1R10.0 MVS System Codes
AC7
the service call. The system 0019000A Explanation:Internal Error
abnormally ends the calling program.
Action:Contact the IBM Support
Action: Check the calling program for Center.
a probable coding error. Correct the
0019000B Explanation:Internal Error
program and rerun it.
Action:Contact the IBM Support
00170001 Explanation: For a call to the
Center.
Set_Context_Interest_Data service,
the parameters are not addressable. 001B0000 Explanation:This completion code
The system rejects the service call. and reason code are used to permit
The system abnormally ends the MVS to take a system dump the first
calling program. time MVS issues message IEA059E
for the current IPL.
Action: Check the calling program for
a probable coding error. Correct the Action:This reason code should not
program and rerun it. be treated as an error. Refer to
message IEA059E for additional
00180000 Explanation:Internal Error
information.
Action:Contact the IBM Support
00200000 Explanation:For a call to the
Center.
Set_Context_Data service, the
00180001 Explanation:Internal Error parameters are not in the primary
address space. The system rejects
Action:Contact the IBM Support
the service call. The system
Center.
abnormally ends the calling program.
00190001 Explanation:Internal Error
Action:Check the calling program for
Action:Contact the IBM Support a probable coding error. Correct the
Center. problem and rerun it.
00190002 Explanation:Internal Error 00200001 Explanation:For a call to the
Set_Context_Data service, the
Action:Contact the IBM Support parameters are not addressable. The
Center. system rejects the service call. The
00190003 Explanation:Internal Error system abnormally ends the calling
program.
Action:Contact the IBM Support
Center. Action:Check the calling program for
a probable coding error. Correct the
00190004 Explanation:Internal Error problem and rerun it.
Action:Contact the IBM Support 00210000 Explanation:For a call to the
Center. Retrieve_Context_Data service, the
00190005 Explanation:Internal Error parameters are not in the primary
address space. The system rejects
Action:Contact the IBM Support the service call. The system
Center. abnormally ends the calling program.
00190006 Explanation:Internal Error Action:Check the calling program for
Action:Contact the IBM Support a probable coding error. Correct the
Center. problem and rerun it.
00190007 Explanation:Internal Error 00210001 Explanation:For a call to the
Retrieve_Context_Data service, the
Action:Contact the IBM Support parameters are not addressable. The
Center. system rejects the service call. The
system abnormally ends the calling
00190008 Explanation:Internal Error
program.
Action:Contact the IBM Support
Action:Check the calling program for
Center.
a probable coding error. Correct the
00190009 Explanation:Internal Error problem and rerun it.
Action:Contact the IBM Support 00220000 Explanation:For a call to the
Center. Retrieve_Current_Context_Token
Chapter 2. System Completion Codes 289
AC7
service, the parameters are not in the primary address space. The system
primary address space. The system rejects the service call. The system
rejects the service call. The system abnormally ends the calling program.
abnormally ends the calling program.
Action: Check the calling program for
Action:Check the calling program for a probable coding error. Correct the
a probable coding error. Correct the program and rerun it.
problem and rerun it.
00350001 Explanation: For a call to the
00220001 Explanation:For a call to the Retrieve_Resource_Manager_Data
Retrieve_Current_Context_Token service, the parameters are not
service, the parameters are not addressable. The system rejects the
addressable. The system rejects the service call. The system abnormally
service call. The system abnormally ends the calling program.
ends the calling program.
Action: Check the calling program for
Action:Check the calling program for a probable coding error. Correct the
a probable coding error. Correct the program and rerun it.
problem and rerun it.
00360000 Explanation: For a call to the
00310000 Explanation: For a call to the Set_Exit_Information service, the
Unregister_Resource_Manager parameters are not in the primary
service, the parameters are not in the address space. The system rejects
primary address space. The system the service call. The system
rejects the service call. The system abnormally ends the calling program.
abnormally ends the calling program.
Action: Check the calling program for
Action: Check the calling program for a probable coding error. Correct the
a probable coding error. Correct the program and rerun it.
program and rerun it.
00360001 Explanation: For a call to the
00310001 Explanation: For a call to the Set_Exit_Information service, the
Unregister_Resource_Manager parameters are not addressable. The
service, the parameters are not system rejects the service call. The
addressable. The system rejects the system abnormally ends the calling
service call. The system abnormally program.
ends the calling program.
Action: Check the calling program for
Action: Check the calling program for a probable coding error. Correct the
a probable coding error. Correct the program and rerun it.
program and rerun it.
00360002 Explanation: For a call to the
00330000 Explanation: For a call to the Set_Exit_Information service, the
Register_Resource_Manager service, parameters are not addressable.
the parameters are not in the primary However, the call successfully set exit
address space. The system rejects routines with the exit manager. The
the service call. The system system abnormally ends the calling
abnormally ends the calling program. program.
Action: Check the calling program for Action: Check the calling program for
a probable coding error. Correct the a probable coding error. Correct the
program and rerun it. program and rerun it.
00330001 Explanation: For a call to the 00400000 Explanation: Internal Error
Register_Resource_Manager service,
Action: Contact the IBM Support
the parameters are not addressable.
Center.
The system rejects the service call.
The system abnormally ends the 00400001 Explanation: Internal Error
calling program.
Action: Contact the IBM Support
Action: Check the calling program for Center.
a probable coding error. Correct the
program and rerun it. 00400002 Explanation: Internal Error
00350000 Explanation: For a call to the Action: Contact the IBM Support
Retrieve_Resource_Manager_Data Center.
service, the parameters are not in the
290 z/OS V1R10.0 MVS System Codes
AC8 • B04
Source: Timer supervision, supervisor control, context diagnostic data associated with the EXCP processor.
services, or registration services
If the error recurs and the program is not in error, look
at the messages in the job log for more information.
AC8 Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support
Explanation: Unicode Services detected an error in
Center. Provide the logrec data set error record, the job
processing.
control language (JCL), the program listing, and the
Code Explanation assembly listing for the job.
04 Unicode detected an unexpected Source: Execute channel program (EXCP)
return code from the IEANTRT service
and register 3 contains the return
B04
code.
Explanation: An error occurred when the system tried
08 Unicode detected critical overlay
to process an EC, EU, LC, LU, VC, or VU form of the
information.
GETMAIN macro. A reason code in the SDWACRC field
System action: The system abnormally ends the task. of the system diagnostic work area (SDWA) explains
the error:
System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix Code Explanation
exists, contact the IBM Support Center.
04 The GETMAIN macro requested an undefined
Source: Unicode Services subpool.
08 The program issuing the GETMAIN macro is
AFB not authorized to request system subpools.
Explanation: While JES3 dynamic support program 14 A local branch entry caller of the GETMAIN
(DSP) for systems network architecture (SNA) remote macro did not hold the local lock for the
job processing (RJP) was executing as a JES3 subtask address space that is currently addressable.
or under an SRB, a JES3 module IATSNDA, IATSNDE,
18 An incorrect task control block (TCB) address
IATSNDM, IATSNDR, IATSNDT, IATSNDU, or IATSNDV
was specified on a branch entry request.
attempted to reuse a still-active request parameter list
(RPL). 1C The address space control block (ASCB)
address specified on a branch entry request
System action: The system cancels the session
was not the current ASCB.
associated with the RPL and writes a dump. The system
continues processing all other sessions, including those 20 Using the GETMAIN macro or its equivalent
associated with the same work station. branch entry, the caller tried to obtain disabled
reference storage that resides above 16
Application Programmer Response: Analyze the
megabytes. This entry only satisfies requests
dump to determine which RPL is about to be overlaid
for storage below 16 megabytes.
and what data is about to be sent or received.
5C A program attempted to obtain user key (8-F)
Source: JES3
storage from a CSA subpool, and
ALLOWUSERKEYCSA(NO) was specified in a
B00 DIAGxx PARMLIB member.
Explanation: During processing of an I/O request, a System action: The system issues message IEA705I.
program check occurred in an execute channel program The system abnormally ends the current task.
(EXCP) procedure.
Application Programmer Response: Depending on
System action: The system abnormally ends the the reason code, do one of the following:
current task. The system writes a logrec data set error
Code Response
record.
04 Ensure that the subpool is not incorrectly
Application Programmer Response: Check the
specified or modified.
problem program for the error. If the error cannot be
determined, run the job again, requesting an ABEND 08 If the program requires system subpools,
dump. Notify the system programmer. ensure that the program resides in an
authorized program library.
System programmer response: In the dump, look at
field TCBEXCPD at offset X'C0' in the task control block 1C Specify the correct ASCB address on the
(TCB) for the current task. TCBEXCPD points to the FREEMAIN macro.
EXCP debugging area (XDBA). The XDBA contains
Chapter 2. System Completion Codes 291
B05 • B0A
20 Change the program to request expanded
B06
storage.
Explanation: During input/output activity, a system
ALL Check for program errors that could modify the
error task operating in behalf of a user task was
parameter list.
abnormally ending.
Source: Virtual storage manager (VSM)
System action: The system reinstates the system
error task and abnormally ends the user task.
B05
Application Programmer Response: Run the job
Explanation: An error occurred when the system tried again.
to process an EC, EU, LC, LU, VC, or VU form of the
Source: Input/output supervisor (IOS)
FREEMAIN macro. A reason code in the SDWACRC
field of the system diagnostic work area (SDWA)
explains the error: B0A
Code Explanation Explanation: An error occurred when the system tried
to process an R form of the GETMAIN or FREEMAIN
04 The FREEMAIN macro tried to free storage in
macro. A reason code in the SDWACRC field of the
an undefined subpool.
system diagnostic work area (SDWA) explains the error:
08 The program issuing the FREEMAIN macro is
Code Explanation
not authorized to free storage in system
subpools. 04 The macro tried to obtain or free storage in an
undefined subpool.
14 A local branch entry caller of the FREEMAIN
macro did not hold the local lock for the 08 The program issuing the macro is not
address space that is currently addressable. authorized to obtain or free storage in system
subpools.
18 Incorrect task control block (TCB) address
specified on a branch entry request. 14 A local branch entry caller of the GETMAIN or
FREEMAIN macro did not hold the local lock
1C The address space control block (ASCB)
for the address space that is currently
address specified on a branch entry request
addressable.
was not the current ASCB.
18 An incorrect task control block (TCB) address
20 Using a FREEMAIN macro or its equivalent
specified on a branch entry request.
branch entry, the caller attempted to free
disabled reference storage that resides above 1C The address space control block (ASCB)
16 megabytes. This entry only satisfies address specified on a branch entry request
requests for storage below 16 megabytes. was not the current ASCB.
System action: The system issues message IEA705I. 20 The caller tried to release disabled reference
The system abnormally ends the current task. storage using a GETMAIN/FREEMAIN macro
with the R operand or its equivalent branch
Application Programmer Response: Depending on
entry. This entry only satisfies requests for
the reason code, do one of the following:
storage below 16 megabytes. Disabled
Code Response reference subpools do not reside below 16
megabytes.
04 Ensure that the subpool is not incorrectly
specified or modified. 5C A program attempted to obtain user key (8-F)
storage from a CSA subpool, and
08 If the program requires system subpools, ALLOWUSERKEYCSA(NO) was specified in a
ensure that the program resides in an DIAGxx PARMLIB member.
authorized program library.
System action: The system issues message IEA705I.
1C Specify the correct ASCB address on the The system abnormally ends the current task.
FREEMAIN macro.
Application Programmer Response: Depending on
20 Change the program to request expanded the reason code, do one of the following:
storage.
Code Response
ALL Check for program errors that could modify the
parameter list. 04 Ensure that the subpool is not incorrectly
specified or modified.
Source: Virtual storage manager (VSM)
08 If the program requires system subpools,
292 z/OS V1R10.0 MVS System Codes
B13 • B37
ensure that the program resides in an end occurred in the user address space during catalog
authorized program library. recall processing.
1C Specify the correct ASCB address on the Application Programmer Response: Use the
FREEMAIN macro. following information to determine the cause of the
error:
20 Change the program to request expanded
storage. v The SYS1.DUMP produced for this abnormal end.
v The SYS.DUMP produced by the abnormal end of
ALL Check for program errors that could modify the
the user address space.
parameter list.
Source: DFSMSdfp
Source: Virtual storage manager (VSM)
B23
B13
Explanation: A task issued a WTOR macro. Before
Explanation: The error occurred during processing of
the operator replied to the WTOR message, a system
an OPEN macro for a data set on an impact printer.
problem occurred, leaving the message unanswered.
This system completion code is accompanied by
message IEC152I. Refer to the explanation of message System action: The system abnormally ends the task
IEC152I for complete information about the task that that issued the WTOR. The system issues message
was ended and for an explanation of the return code (rc IEE824A or IEE824E.
in the message text) in register 15.
Operator response: See the operator response for
Application Programmer Response: Respond as message IEE824A or IEE824E. Restart the task that
indicated for message IEC152I. ended with abend code X'B23'.
System programmer response: If the error recurs | Source: Console services
and the program is not in error, look at the messages in
the job log for more information. Search problem
B2D
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL Explanation: A program requested an overlay. In
and the program listing for the job. answer to the request, the overlay supervisor was using
program fetch to load a program segment from the
Source: DFSMSdfp
library. While the fetch recovery routine was processing
because of a previous abend, a program check
B14 occurred.
Explanation: The error occurred during processing of
Note: Overlay programs run only in 24-bit addressing
a CLOSE macro instruction for a partitioned data set
mode, not in 31-bit addressing mode.
opened for output to a member. This system completion
code is accompanied by message IEC217I. Refer to the System action: The system abnormally ends the
explanation of message IEC217I for complete program that requested the overlay. The system writes
information about the task that was ended and for an an ABEND dump, if a dump DD statement is provided.
explanation of the return code (rc in the message text)
in register 15. Application Programmer Response: Check the
linkage editor input to be sure the program is designed
Application Programmer Response: Respond as correctly. Correct the errors; then assemble, link edit,
indicated for message IEC217I. and run the program again.
System programmer response: If the error recurs Source: Overlay supervisor
and the program is not in error, look at the messages in
the job log for more information. Search problem
reporting data bases for a fix for the problem. If no fix B37
exists, contact the IBM Support Center. Provide the JCL Explanation: The error was detected by the
and the program listing for the job. end-of-volume routine. This system completion code is
Source: DFSMSdfp accompanied by message IEC030I. Refer to the
explanation of message IEC030I for complete
information about the task that was ended and for an
B1A explanation of the return code (rc in the message text)
in register 15.
Explanation: The user address space catalog ESTAE
module IGG0CLHC requested the abnormal end of the Application Programmer Response: Respond as
catalog address space (CAS) service task. An abnormal indicated for message IEC030I.
System programmer response: If the error recurs
Chapter 2. System Completion Codes 293
B78
and the program is not in error, look at the messages in locking restrictions by holding a suspend lock
the job log for more information. Search problem that is not the local lock of the target address
reporting data bases for a fix for the problem. If no fix space.
exists, contact the IBM Support Center. Provide the JCL
30 The specified ALET does not translate to a
and the program listing for the job.
valid STOKEN.
Source: DFSMSdfp
34 The STOKEN does not translate to a valid
ASCB; the address space from which the
B78 storage is to be obtained or released is not
valid for cross memory access.
Explanation: The error occurred when the system
tried to run one of the following: 38 The target address space is the master
v An RC, RU, VRC, or VRU GETMAIN macro scheduler’s address space, which is not the
v An RC or RU FREEMAIN macro home address space.
v A STORAGE macro.
3C The target address space is either in the
A reason code in the SDWACRC field of the system process of ending, or has ended.
diagnostic work area (SDWA) explains the error. The
40 A user violated serialization requirements by
reason code appears in the form xxxxxxyy, where
calling global branch entry GETMAIN or
xxxxxx is the internal reason for the error, and yy is
FREEMAIN while enabled.
described in the following table:
44 A program issued a SETLOCK
Code Explanation
OBTAIN,TYPE=VSMFIX macro before issuing
04 The macro tried to obtain or free storage in an a VSMLIST or VSMLOC request. The program
undefined subpool. or an associated FRR issued a GETMAIN,
FREEMAIN, or STORAGE request before
08 The program issuing the macro is not
issuing SETLOCK RELEASE,TYPE=VSMFIX.
authorized to obtain or free storage in system
subpools. GETMAIN or FREEMAIN users must 48 A program issued a SETLOCK
be supervisor state, key 0, or authorized OBTAIN,TYPE=VSMPAG macro before issuing
program facility (APF) authorized. STORAGE a VSMLOC request. The program or an
users must be supervisor state, or key 0. associated FRR issued a GETMAIN,
FREEMAIN, or STORAGE request before
0C A global branch entry caller of the GETMAIN or
issuing SETLOCK RELEASE,TYPE=VSMPAG.
FREEMAIN macro tried to obtain or free a
nonglobal subpool. 4C An incorrect subpool was specified on a
GETMAIN or STORAGE OBTAIN request with
10 The LOC parameter is not valid. Virtual storage
the LOC=EXPLICIT keyword specified. Valid
manager (VSM) received a request for either a
subpools for unauthorized programs are:
fetch-protected local system queue area
v 0-127
(LSQA) or a disabled reference subpool that
v 131-132
resides below 16 megabytes. Fetch-protected
LSQA and disabled reference subpools are Valid subpools for authorized programs are:
supported only above 16 megabytes. v 0-127
v 129-132
14 A local branch entry caller of the GETMAIN or
v 240
FREEMAIN macro did not hold the local lock
v 250-252
for the address space that is currently
addressable. 50 A GETMAIN or STORAGE OBTAIN request
failed because the address specified on the
18 An incorrect task control block (TCB) address
INADDR keyword was greater than 16
was specified on a branch entry or STORAGE
megabytes and the central storage backing
request.
specified on the LOC keyword was BELOW.
1C The address space control block (ASCB) The virtual storage address specified on
address specified on a branch entry request INADDR and the central storage backing
was not the current ASCB. specified on the LOC=EXPLICIT must be a
valid combination. For example, if the address
24 The user of the STORAGE macro is disabled. specified on INADDR is for virtual storage
28 A caller that is not in supervisor state, or keys above 16 megabytes, specify LOC=EXPLICIT
0 through 7, specified the ALET parameter or or LOC=(EXPLICIT,ANY). The following
the TCBADDR parameter on the STORAGE combinations are valid:
macro. v virtual above, central any
v virtual any, central any
2C The caller violated the STORAGE service’s v virtual below, central below
294 z/OS V1R10.0 MVS System Codes
BC2 • BC3
v virtual below, central any RELEASE,TYPE=VSMPAG macro before you
issue a GETMAIN, FREEMAIN, or STORAGE
54 A GETMAIN or STORAGE OBTAIN request
macro.
failed because the address specified on the
INADDR keyword was not on an doubleword ALL Check for program errors that modify the
boundary. parameter list.
58 Branch entry caller for local storage request is Source: Virtual storage manager (VSM)
running in AR mode.
5C A program attempted to obtain user key (8-F) BC2
storage from a CSA subpool, and
Explanation: During the processing of an FSI call,
ALLOWUSERKEYCSA(NO) was specified in a
validation of cell failed before returning it to cellpool.
DIAGxx PARMLIB member.
Code Explanation
60 The boundary indicated by the CONTBDY
parameter on a GETMAIN or STORAGE 04 IAZFSIT work area cell pool.
OBTAIN request was less than the requested
storage area length. 08 FSI trace work area cell pool.
64 CONTBDY or STARTBDY was specified on a 0C Save area across FSI function call cell pool.
variable-length GETMAIN or STORAGE 10 FSI trace connected FSS chain cell pool.
OBTAIN request.
14 FSI trace connected FSS chain cell pool.
68 CONTBDY or STARTBDY was specified with
LOC=EXPLICIT on a GETMAIN or STORAGE 18 FSI trace connected FSS chain cell pool.
OBTAIN request. 1C FSI trace connected FSS chain cell pool.
6C CONTBDY or STARTBDY was specified with
BNDRY=PAGE on a GETMAIN or STORAGE For all codes, the associated component module is JES
OBTAIN request. common, and the detecting module is IAZFSIT.
70 Storage overlay detected while freeing storage. System action: The system issues an SVC dump.
VSM processing has recovered this error. Application Programmer Response: Search problem
System action: The system issues message IEA705I. reporting data bases for a fix for the problem. If no fix
The system abnormally ends the current task. exists, contact the IBM Support Center and provide the
SVC dump.
Application Programmer Response: Depending on
the reason code, do one of the following: Source: Functional subsystem interface (FSI)
Code Response
BC3
04 Ensure that the specified subpool is not
incorrectly specified or modified. Explanation: The JES3 dump job server address
space encountered an error. The abend reason code
08 If the program requires system subpools, identifies the specific error.
ensure that the program resides in an
authorized program library. Users of the Code Explanation
STORAGE macro must also switch to 01 The ASEXT macro returned a non-zero return
supervisor state, or key 0. code while the dump job server space was
0C Note that a global branch entry request can attempting to extract the address space
only request global subpools, that is, system parameters. Registers 2 and 3 when the BC3
queue area (SQA) subpools or common abend is issued contain the return and reason
service area (CSA) subpools. codes from the ASEXT macro call.
10 An incorrect bit combination for the LOC 02 The address of the extracted parameter string
operand was put into an input register. returned from the ASEXT macro is zero.
14 Ensure that a local branch entry caller holds 03 The ALESERV macro returned a non-zero
the local lock for the currently addressable return code while the dump job server space
address space. was attempting to add JES3’s ALET to its
access list. Registers 2 and 3 when the BC3
44 Issue the SETLOCK RELEASE,TYPE=VSMFIX abend is issued contain the return and reason
macro before you issue a GETMAIN, codes from the ALESERV macro call.
FREEMAIN, or STORAGE macro.
04 The ALESERV macro returned a non-zero
48 Issue the SETLOCK return code while the dump job server address
Chapter 2. System Completion Codes 295
BC5 • C03
space was attempting to extract its STOKEN. reporting data bases for a fix for the problem. If no fix
Registers 2 and 3 when the BC3 abend is exists, contact the IBM support center.
issued contain the return and reason codes
Source: Supervisor Control
from the ALESERV macro call.
05 The ALESERV macro returned a non-zero
BFB
return code while the dump job server address
space was attempting to extract JES3’s Explanation: During JES3 abnormal termination
STOKEN. Registers 2 and 3 when the BC3 recovery processing, JES3 was unable to invalidate the
abend is issued contain the return and reason spool space allocation checkpoint record (PTC). The
codes from the ALESERV macro call. invalidation failed due to an error in the checkpoint
access method or an unrecoverable I/O error in the
06 The STOKEN associated with the JES3
checkpoint data set(s).
address space that started the dump job server
address space is not the same as the current Message IAT6352 accompanies this completion code.
JES3 address space. JES3 could not invalidate the spool space allocation
checkpoint record (PTC) during JES3 abnormal
07 The STIMERM macro returned a non-zero
termination recovery processing.
return code while the dump job server address
space was attempting to setup status When message IAT1025 accompanies this completion
monitoring for the JES3 address space. code, JES3 could not invalidate the only copy or both
Register 2 when the BC3 abend is issued copies of a partition track allocation table (PTAT) during
contains the return code from the STIMERM JES3 initialization or after JES3 failsoft processing.
macro call.
System action: After issuing the message, JES3
08 The dump job server’s ECB was posted with ends. IAT6352 contains the checkpoint access method
an incorrect function code. Register 2 when the return code, which identifies the error.
BC3 abend is issued contains the function
code. If message IAT1025 appears, the system writes an error
record to the logrec data set.
System action: A dump of the JES3 dump job server
address and the JES3 address space is taken. The Application Programmer Response: Using message
dump job server address space ends and the Dump Job IAT6352, analyze the return code and correct the error,
DSP in the JES3 address space that controls the server then restart JES3.
address space also ends. For message IAT1025, analyze the error record in the
Application Programmer Response: Contact IBM logrec data set and the accompanying messages. In
support and provide the following documentation: case the error is caused by a bad track, assign another
track to the checkpoint data set and restart JES3 with a
v The BC3 abend reason code. warm start. Otherwise, reallocate the checkpoint data
v The information in registers 2 and 3 at the time of set and perform a cold start.
error (if applicable).
System programmer response: If the problem occurs
v The dump taken by the JES3 server address space. in JES3, take a system dump by specifying
v The SYSLOG around the time of error. DUMP=MVS on the OPTIONS card in the initialization
v The *CALL DJ command that caused the JES3 dump deck Make sure that the failing job step includes a
job server address space to be started. SYSABEND statement.
v The dump job DSP log (if available). Source: JES3
Source: JES3
C03
BC5 Explanation: A task tried to end normally by issuing a
RETURN macro or by branching to the return address
Explanation: The system terminated an address
in register 14. The task was not ready to end
space.
processing because the task had opened one or more
Code Explanation data sets that had not been closed.
01 The system attempted to rebuild its work unit The system received a nonzero return code from Data
queues and encountered an address space Facility Product (DFP) indicating one of the following:
whose queues it could not rebuild. v DFP returned a nonzero return code.
System action: The system ends the address space. v DFP could not successfully close one or more data
sets still open because a previous error or abend had
System programmer response: If the source of the
been ignored by a recovery routine or a data control
problem cannot be determined, search problem
block (DCB) abend exit routine.
296 z/OS V1R10.0 MVS System Codes
C0D
v DFP could not successfully close one or more of the specific instance of this C0D abend.
task’s data sets that was still open because the DCB
for the data set had been incorrectly modified. Note: Some Common C0D reason codes are
Examples of how the DCB could be incorrectly documented below for convenience. This is not
modified are: an all inclusive list. In most cases you will need
IBM assistance to interpret the reason codes
– A program containing an open DCB issued an
based on the specific component which issues
XCTL(X) macro.
the abend.
– A program freed virtual storage that contained an
open DCB. The system may provide a hexadecimal reason code to
– The program modified the DCB incorrectly. describe the error.
System action: The system may issue message Code Explanation
IEC999I. Message IEC999I provides the address of the
DEB that could not be properly closed. 2A00010x or 2A00020x
After a page fixing request that
Operator response: If the application or system specified a task control block (TCB)
programmer asks for an SVC dump, set the following address of zero, the system received
SLIP trap: a corresponding page freeing request
SLIP SET,COMP=C03,ACTION=SVCD,END with a specific TCB address. The
system could not locate the necessary
Application Programmer Response: Do the control blocks to process the request.
following:
5E000101 While processing a page fixing
1. If a dump is not produced with the abend, ask the
request, the system encountered a
operator to set a SLIP trap to obtain an SVC dump.
fixed page that was not backed with
2. From the dump, find the data extent block (DEB) central storage. To satisfy the request,
from the IEC999I message. The DEB + X'18' points the page must be backed.
to the associated DCB or ACB.
3. If the DCB or ACB has been freed, then this is a The reason code, if any, and the location at which the
user error. C0D ABEND was issued, are shown in an entry of type
RCVY ABT in the system trace table.
This is a common user error during subtask processing.
A user must close a DCB or ACB before freeing the For an indexed sequential access method (ISAM)
storage where the DCB or ACB resides. If the DCB or request, the system found an excess number of error
ACB has been overlaid, you must determine the cause input output blocks (IOB). The probable cause of the
of the overlay. problem is that an application neglected to free the
dynamic buffers associated with a READ macro.
System programmer response: If the module is an
IBM program, search problem reporting data bases for a
fix for the problem. If no fix exists, contact the IBM | The following reason codes are used by the input/output
Support Center. Provide the dump. | supervisor HyperSwap function (IOSH):
Source: Recovery termination manager (RTM) | IOSHSAPI
| 80000002
C0D | Attach macro request failure.
Explanation: An unexpected error occurred. For | 80000003
example , a system component experienced an | Error attaching subtask.
unexpected program check or perhaps an I/O device
returned data that was not expected. This abend may | 80000004
be used for entry into a recovery routine that will | ETCRE macro request failure.
capture additional documentation and then attempt retry. | 80000005
In other cases, the C0D abend will be percolated to an | CSVQUERY macro request failure.
application recovery routine or another system
component recovery routine. | 80000006
| IEANTDL macro request failure.
Several components utilize C0D for these unexpected
error situations and therefore it becomes necessary to | 80000007
utilize additional information to determine the specific | IEANTRT macro request failure.
component to determine the exact nature of this | 80000008
unexpected error. Continue reading for additional | IEANTCR macro request failure.
diagnostic techniques to help identify the nature of your
Chapter 2. System Completion Codes 297
C13
| 80000009 both to identify the component that is the source of
| Error removing SSID name from master the ABEND. See the chapter topics on Recording
| SSID_Array. Logrec Error Records and on System Trace in z/OS
MVS Diagnosis: Tools and Service Aids for details
| 8000000A on how to interpret logrec records and System Trace
| RESMGR macro ADD request failure.
entries. The failing PSW address, in most cases, will
| 8000000B reflect the component that issued the ABEND
| RESMGR macro DELETE request failure. macro. To ensure that the PSW address
corresponds to an ABEND macro invocation, refer to
| 8000000C the failing instruction text in the logrec record or
| ENFREQ macro LISTEN request failure. dump. The failing instruction should have been
| 8000000D ″0A0D″.
| ENFREQ DELETE request failure. There are some cases where the CALLRTM
TYPE=ABTERM macro is used and this will cause
| 8000000F
the error PSW instruction address to reference a
| IDENTIFY macro request failure.
system or a user program that might be in some
| 80000010 kind of wait. Hence, the failing instruction text might
| Maximum number of subtask restart attempts be an ″0A01″ or some other instruction. This might
| reached. be due to the asynchronous nature of the recovery
associated with a CALLRTM. For this case, you will
| IOSHSSUB need a dump that contains SYSTEM TRACE.
| 80010001 3. Search the System Trace for an entry of the type
| ESTAEX macro request failure. RCVY ABT corresponding to the C0D ABEND, and
note the PSW address. Once you have determined
| 80010002 the PSW address for the program responsible for
| NUCLKUP macro request failure. invoking the ABEND or CALLRTM macro, use the
IPCS WHERE command to find the module name.
| IOSHSENF v If the module is not an IBM module, continue
| 80020001 diagnosis with the module.
| UCBPIN macro request failure. v If the module is an IBM module, search problem
reporting data bases for a fix for the problem. If
| 80010002 no fix exists, contact the IBM Support Center.
| NUCLKUP token count error occurred.
Provide the messages, the logrec data set record,
the SYSOUT output for the job, and the dump.
| IOSHSRDR
Source: Code C0D can be issued by many
| 80030001 components, including:
| IRXEXCOM routine call failure. v Real storage manager (RSM)
System action: The system may write a logrec data v Auxiliary storage manager (ASM)
set error record, may write a dump, and may write v Contents supervision (CSV)
messages about the problem. The system issues an v Program Call/authorization (PC/AUTH)
abend to the current task. v Input/output supervisor (IOS)
v Access methods (e.g. BSAM, QSAM)
Operator response: If the system programmer asks
for an SVC dump, set the following SLIP trap:
C13
SLIP SET,COMP=C0D,ACTION=SVCD,END
Explanation: The error occurred during processing of
Application Programmer Response: For an ISAM
an OPEN macro instruction for a concatenated
request error, fix the program and run the job again. For
partitioned data set or a graphic device. This system
a problem in obtaining storage, fix the storage request
completion code is accompanied by message IEC153I
and run the job again.
(or for graphics, message IEC157I). Refer to the
System programmer response: Do the following: explanation of message IEC153I (or message IEC157I)
1. If a dump or a logrec data set error record was not for complete information about the task that was ended
written with the abend, ask the operator to set a and for an explanation of the return code (rc in the
SLIP trap to obtain an SVC dump. message text) in register 15.
2. Application Programmer Response: Respond as
If you are unable to identify a responsible indicated for message IEC153I (or message IEC157I).
component from the logrec record symptoms such System programmer response: If the error recurs
as CSECT NAME and COMPID, then use additional and the program is not in error, look at the messages in
information from logrec data set records, dumps, or
298 z/OS V1R10.0 MVS System Codes
C1A • C78
the job log for more information. Search problem assemble, link edit, and run the program again.
reporting data bases for a fix for the problem. If no fix
Source: Overlay supervisor
exists, contact the IBM Support Center. Provide the
source program listing for the job.
C37
Source: DFSMSdfp
Explanation: The error occurred when an input
operation was requested. The data set was on a direct
C1A
access device. This system completion code is
Explanation: Through the MODIFY CATALOG,ABEND accompanied by message IEC033I. Refer to the
command, a request was issued to abnormally end explanation of message IEC033I for complete
either the catalog address space (CAS) information about the task that was ended and for an
allocation/unallocation, analysis, or modify task. explanation of the return code (rc in the message text)
in register 15.
System action: The system attaches a new task to
restore the allocation/unallocation, analysis, or modify Application Programmer Response: Respond as
function. indicated for message IEC033I.
Source: DFSMSdfp System programmer response: If the error recurs
and the program is not in error, look at the messages in
the job log for more information. Search problem
C22
reporting data bases for a fix for the problem. If no fix
Explanation: The execute channel program (EXCP) exists, contact the IBM Support Center. Provide all
processor abnormally ended the job because the printed output and output data sets related to the
maximum number of EXCP/EXCPVR macro requests problem.
permitted for an address space was exceeded. The
Source: DFSMSdfp
maximum number of outstanding requests is defined in
the ASCBXCNT in the address space control block
(ASCB). C78
System action: The EXCP processor abnormally ends Explanation: An error occurred when the system tried
the job. to process a virtual storage management (VSM) service.
A reason code in the SDWACRC field of the system
Application Programmer Response: Check the job
diagnostic work area (SDWA) explains the error:
for a loop that could result in EXCP/EXCPVR macros
being issued repeatedly without intervening WAIT Code Explanation
macros. If the reason for the error cannot be
04 For the CPOOL BUILD or GET options, there
determined, notify the system programmer.
is not enough virtual storage available to build
System programmer response: If the error recurs or extend a cell pool.
and an installation provided program is not in error, look
08 For the CPOOL BUILD or GET options, there
at the messages in the job log for more information.
is not enough central storage available to build
Search problem reporting data bases for a fix for the
or extend a cell pool.
problem. If no fix exists, contact the IBM Support
Center. Provide the source program listing for the job. 0C For the CPOOL BUILD or GET options, page
tables are paged out for the storage obtained
Source: Execute channel program (EXCP)
for the pool or pool control blocks.
10 For the CPOOL BUILD GET or DELETE
C2D
options, an unauthorized user tried to build get
Explanation: A program requested an overlay. In or delete storage from an authorized subpool.
answer to the request, the overlay supervisor was using
14 For the CPOOL BUILD option, an unauthorized
program fetch to load a program segment from the
caller specified the task control block (TCB)
library. Fetch could not get enough storage for the
parameter.
module or control blocks.
18 For the CPOOL GET or DELETE option, an
Note: Overlay programs run only in 24-bit addressing incorrect cell pool identifier (CPID) is specified.
mode, not in 31-bit addressing mode.
1C For the CPOOL BUILD DELETE or GET
System action: The system abnormally ends the option, there is not enough storage available
program that requested the overlay. The system writes for a module’s work area.
an ABEND dump, if a dump DD statement is provided.
20 For the CPOOL BUILD option, an incorrect cell
Application Programmer Response: Determine why count is specified.
no storage was available. Correct the errors; then
Chapter 2. System Completion Codes 299
C78
24 For the CPOOL BUILD option, a reserved field 74 The reserved bits of the VSMLIST parameter
in the parameter list is nonzero. list are not zero.
28 For the CPOOL BUILD, GET, or DELETE 78 The return code field in the work area passed
options, the invoker of the VSM service is in to the VSMLIST routine is not zero (first call) or
service request block (SRB) mode and problem four (restart).
state, which is not allowed by the system.
7C The SP™ operand of VSMLIST is not valid.
2C For the CPOOL BUILD option, the invoker of
80 The SPACE operand of VSMLIST is not valid.
the VSM service is in SRB mode requesting a
Note: SPACE=UNALLOC is not allowed if
local area subpool. However, the invoker did
SP=SQA, SP=LSQA, or SP=(subpool list) is
not specify the TCB parameter.
specified.
30 A FREEMAIN routine returned a nonzero return
84 VSMLIST was invoked again. Control
code unexpectedly when a task ended.
information that was saved in the work area,
Recovery attempts a retry.
provided by the caller, is not valid.
34 For the CPOOL BUILD or DELETE option, the
88 The TCB address is not valid or not in the
subpool identifier is incorrect.
currently addressable address space.
38 For the CPOOL BUILD option, the LOC
8C On VSMLIST, the subpool list address is zero.
parameter is incorrect.
90 On VSMLIST, the work area size is less than 4
3C For the CPOOL BUILD option, the PSATOLD
kilobytes.
field points to a TCB that is not in the currently
addressable address space. A0 On CPOOL, the primary cell count, cell size or
cells per CPU specified is too large. Ensure
40 For the CPOOL BUILD option, the invoker of
that the cell count, cells per CPU and cell size
the VSM service holds the VSMPAG lock. This
values are specified correctly. If they are,
is not valid because the system BUILD routine
decrease one or more values.
must obtain the CMS lock, which is lower in
the hierarchy than the VSMPAG lock. A4 On CPOOL Build, the secondary cell count,
cell size or cells per CPU specified is too large.
44 For the CPOOL BUILD option, the cell size is
Ensure that the cell count, cells per CPU and
less than 4 bytes. This is not valid.
cell size values are specified correctly. If they
48 On a request to free a central or virtual region, are, decrease one or more values.
the subpool FREEMAIN failed.
A8 CPOOL FREE attempted to free a cell which is
4C The address space that is making a request to already free.
free a virtual region is nonswappable.
B0 During an address space create operation,
50 On a request to get a real region, the system RSM returned a failing reason code. In the
assigned virtual=real (V=R) storage that VSM LOGREC record associated with the abend,
allocated in virtual storage. register 0 contains the RSM reason code.
54 On a request to get a real region, the request B4 An unauthorized caller of CPOOL Build
for a VSM cell failed. specified the MULTIHDR=YES parameter. The
caller must be running Supervisor State or
58 For the CPOOL GET option, BNDRY=QWORD
PSW Key 0-7 or APF Authorized to use this
was requested but the cell size is not a
option. Ensure that the caller has the authority
multiple of 16 bytes.
to perform the requested action.
60 The system detected one of the following:
System action: The system writes a logrec data set
v The reserved bits of register 15 are not zero. error record. The system abnormally ends the current
v The storage type indicator passed to task.
VSMLOC is not valid. Valid storage types
Application Programmer Response: Depending on
are the system queue area (SQA) SQA,
the reason code, do one of the following:
local system queue area (LSQA), common
service area (CSA), and private area. Code Response
v The size passed to VSMLOC is zero or 04, 08, 0C, 1C Run the job again. If
negative. the error recurs,
v The sum of the address passed to VSMLOC notify the system
plus the size passed is greater than 2 programmer.
gigabytes.
300 z/OS V1R10.0 MVS System Codes
CC2 • CC7
18, 20, 30, 34, 38, 44 Ensure that the
CC2
correct values are
specified. Explanation: The error occurred while processing an
IXCMSGO macro. Register 2 contains the IXCMSGO
10, 14, 28, 2C, B4 Ensure that the
return code. Register 3 contains the IXCMSGO reason
caller has the
code.
authority to perform
the requested System action: System processing continues.
action.
System programmer response: If the problem
24, 74, 78, 7C, 80, and 8C Ensure that the persists, search the problem reporting data bases for a
parameter list is fix for the problem. If no fix exists, contact the IBM
properly initialized. Support Center. Provide the return and reason codes
and the dump.
40 Change the program
so it releases the Source: Transaction trace.
VSMPAG lock
before issuing the
CC3
CPOOL macro with
the BUILD Explanation: This abend code is used by WebSphere
parameter. Application Server on z/OS. This abend code is used by
WebSphere Application Server on z/OS. See
3C Ensure that the
WebSphere Application Server on z/OS for further
program passes the
information.
proper TCB
address.
CC4
48, 4C, 50, 54, 58 Notify the system
programmer. Explanation: This abend code is issued as a part of
normal processing by JES2 during task termination
60 Ensure that the
when resolving a deadlock condition involving an
input registers are
internal lock. This is not considered an error.
properly initialized.
System action: Normal task termination continues.
84 Ensure that the
information in the System programmer response: None
work area does not
change before the Source: JES2
VSMLIST macro is
invoked again. CC7
88 Ensure that the TCB Explanation: A work unit (a task or a system service
specified and all running under an SRB) issued an instruction requiring
subtasks of the TCB the presence of an Integrated Cryptographic Feature
are correct. (ICRF) on a processor that does not have the feature
90 Ensure that the work installed. The system was unable to move the work to a
area size is at least processor with the feature. A hexadecimal reason code
4 kilobytes. in register 15 further describes the error condition.
A0, A4 Ensure that the cell Code Explanation
count and cell size 00 The work unit was disabled.
values are specified
correctly. If they are, 04 The ICRF is not available in the processor
decrease one value complex.
or both values. 08 No processors with the feature satisfy the work
System programmer response: Search problem unit’s restrictive processor affinity requirements.
reporting data bases for a fix for the problem. If no fix 10 An unexpected error occurred.
exists, contact the IBM Support Center.
System action: The system ends the work unit.
Source: Virtual storage manager (VSM)
Application Programmer Response: Respond
according to the reason code:
Chapter 2. System Completion Codes 301
CFB • D05
00 Correct the program so that the instruction v Obtain system dump by specifying DUMP=JES on
requiring the ICRF is issued while running the OPTIONS card in the initialization deck and save
enabled. the output
04 Resubmit the job to a processor complex that v Provide a console log from initialization
has the ICRF installed. In a recovery routine, if v Provide a listing of the JES3 start up procedure,
this condition is temporary, the routine could: containing all JCL used to start the subsystem.
v Retry the instruction later
v Issue a message to the end users to retry If module IATAUX abnormally ended, the system sends
the request later messages about the job to one of the following:
v Terminate the part of the program that v The primary console
requires the feature.
v The remote console, for a system with remote
08 Remove the restrictive processor affinity which consoles
might have been assigned to the work unit in v The hard-copy log for a system with multiple console
one of the following ways: support (MCS)
v In the program properties table (PPT) (using
the AFF keyword in SYS1.PARMLIB Make sure that the failing job step includes a
member SCHEDxx) SYSABEND statement.
v In the SRB (in the SRBCPAFF field)
Collect all printed output and output data sets related to
10 Collect diagnostic data and call your IBM
the problem.
service representative.
Source: JES3
Source: Supervisor control
D04
CFB
Explanation: An error occurred when the system tried
Explanation: One of the following occurred:
to process an EU, LU, or VU form of the GETMAIN
v During JES3 initialization, JES3 could not attach the macro. A reason code in the SDWACRC field of the
JES3 auxiliary task, module IATAUX. ATTACH system diagnostic work area (SDWA) explains the error:
processing writes message IAT3005 to the console.
Code Explanation
v After JES3 initialization, the JES3 auxiliary task,
module IATAUX, could not recover from an error and 08 The system could not satisfy a request for local
abnormally ended. The ESTAI routine in module system queue area (LSQA) storage because
IATABMN requests a dump of module IATAUX to the there is not enough central storage for the
SYSABEND or SYSUDUMP data set. control blocks needed to support the request.
System action: JES3 ends. System action: The system issues message IEA705I.
The system abnormally ends the current task.
Application Programmer Response: If JES3 wrote
message IAT3005 to the console, make sure that Application Programmer Response: Resubmit the
module IATAUX is in one of the following: job. If the system issues this abend frequently, notify the
v The library concatenation defined by the JES3LIB system programmer.
initialization statements, if used. System programmer response: See installation
v The STEPLIB concatenation defined in the JES3 procedures to decrease the fixed central storage
procedure. requirements of the system.
v The linklist specified in response to message Source: Virtual storage manager (VSM)
IEA101A.
If JES3 did not write message IAT3005, look in the D05
dump of module IATAUX to find the system completion Explanation: An error occurred when the system tried
code for the module’s failure. Respond to that to process an EU, LU, or VU form of the FREEMAIN
completion code. macro. A reason code in the SDWACRC field of the
System programmer response: If module IATAUX system diagnostic work area (SDWA) explains the error:
could not be attached, the system issues messages Code Explanation
about the job. Make sure that the failing job step
includes a SYSABEND statement. 04 A FREEMAIN request was specified for local
system queue area (LSQA) virtual storage that
Collect all printed output and output data sets related to is associated with a task. However, the virtual
the problem. If the problem occurs in JES3 you should: storage area specified is not associated with
the task.
302 z/OS V1R10.0 MVS System Codes
D06 • D0D
08 The system could not satisfy a request for
D0A
LSQA storage because there is not enough
central storage for the control blocks needed to Explanation: An error occurred when the system tried
support the request. to process an R form of the GETMAIN or FREEMAIN
macro. A reason code in the SDWACRC field of the
System action: The system issues message IEA705I.
system diagnostic work area (SDWA) explains the error:
The system abnormally ends the current task.
Code Explanation
Application Programmer Response: For reason
code X'04', change the FREEMAIN request to obtain 04 A FREEMAIN request was specified for local
storage owned by the task. Run the job step again. system queue area (LSQA) virtual storage that
is associated with a task. However, the virtual
For reason code X'08', resubmit the job. If the system
storage area specified is not associated with
issues this abend frequently, notify the system
the task.
programmer.
08 The system could not satisfy a request for
System programmer response: See installation
LSQA storage because there is not enough
procedures to decrease the fixed central storage
central storage for the control blocks needed to
requirements of the system.
support the request.
Source: Virtual storage manager (VSM)
System action: The system issues message IEA705I.
The system abnormally ends the current task.
D06
Application Programmer Response: For reason
Explanation: A program issued the LOAD macro for a code X'04', change the FREEMAIN request to obtain
module. The macro included some form of the GLOBAL storage owned by the task. Run the job step again.
parameter. However, within the same job step task
For reason code X'08', resubmit the job. If the system
structure, a task control block (TCB) already loaded the
issues this abend frequently, notify the system
requested module with different variables on the
programmer.
GLOBAL parameter. For example, a program issues the
LOAD macro for module MYPROG1 with the parameter System programmer response: See installation
GLOBAL=(YES,P). However, a TCB already loaded procedures to decrease the fixed central storage
module MYPROG1 with the parameter requirements of the system.
GLOBAL=(YES,F) or GLOBAL=NO.
Source: Virtual storage manager (VSM)
If a user tries to load the same module twice - once into
a fixed subpool and once into a pageable subpool, or
D0D
once into global storage and once into local storage,
this situation arises. Explanation: The system abnormally ended a
subtask. While processing the subtask’s end, the
System action: The system abnormally ends the
recovery termination manager 2 (RTM2) was reentered
program that issued the LOAD macro abnormally ends
incorrectly. Therefore, RTM abnormally ended all tasks
unless the macro included the ERRET parameter. The
in the job step.
system issues message CSV017I. The system issues
an ABEND dump.
Note: The original abend code is in the supervisor
Application Programmer Response: Change the request block (SVRB) for the original SVC 13
GLOBAL parameter on the LOAD macro. Resubmit the (ABEND macro). This SVRB is queued from the
job. task that experienced the original error.
System programmer response: If the error recurs System action: RTM2 attempts to end the job step.
and the program is not in error, see the system The system may write an SVC dump, or the program
programmer response for the messages in the job log. may write an ABEND dump. The system sends
messages about the problem to the job log.
If the problem persists, search problem reporting data
bases for a fix for the problem. If no fix exists, contact Operator response: If the system programmer asks
the IBM Support Center. Provide the ABEND dump and for an SVC dump, set the following SLIP trap:
the source program listing for the job. SLIP SET,COMP=D0D,ACTION=SVCD,END
Source: Contents supervision (CSV) System programmer response: Do the following:
1. If a dump is not produced with the abend, ask the
operator to set a SLIP trap to obtain an SVC dump.
Chapter 2. System Completion Codes 303
D13 • D22
2. Examine the abend code for the original subtask.
D1A
This abend code can be found in the SVRB of the
original SVC 13 SVRB queued from the task that Explanation: The catalog address space (CAS)
experienced the error. analysis task ended abnormally because the analysis
Continue diagnosis for that abend code. If the task exceeded the allotted time for processing. The task
problem cannot be resolved, continue with step 3. may have been waiting for some system resource that
is permanently unavailable.
3. Look at the messages in the job log.
4. Search problem reporting data bases for a fix for the System action: The system attaches a new task to
problem. If no fix exists, contact the IBM Support restore the analysis function.
Center. Provide: Source: DFSMSdfp
v An ABEND or SVC dump
v Messages from the job log
v The assembly listing associated with the job D22
Source: Recovery termination manager (RTM) Explanation: A program issued the MGCR or MGCRE
macro (SVC 34) or an operator issued a command.
While processing the request, the system detected an
D13 error. A hexadecimal reason code in register 15 explains
Explanation: The error occurred during processing of the error:
an OPEN macro instruction for a graphic data control Code Explanation
block. This system completion code is usually
accompanied by message IEC158I. Refer to the 04 The request specified both
explanation of message IEC158I for complete CMDFLAG=SUBSYS and
information about the task that was ended and for an CMDFLAG=COMMTASK. These parameter
explanation of the return code (rc in the message text) values are mutually exclusive.
in register 15. 08 On the TEXT parameter, the request specified
Application Programmer Response: Respond as a length field that is either greater than 126
indicated for message IEC158I. characters or zero.
System programmer response: If the error recurs | 0C The request parameter list did not include the
and the program is not in error, look at the messages in | control block acronym MGCRE.
the job log for more information. Search problem 10 The request required the CONSID or
reporting data bases for a fix for the problem. If no fix CONSNAME parameter, but neither was
exists, contact the IBM Support Center. Provide the specified.
source program listing for the job and all printed output
and output data sets related to the problem. 14 The request specified both the CONSNAME
and CONSID parameters. These are mutually
Source: DFSMSdfp exclusive.
18 The request specified a CONSNAME
D14 parameter value that does not represent a valid
Explanation: The error occurred during processing of console.
a CLOSE macro instruction for a graphic data control 1C The request specified a CONSID parameter
block. value that is out the defined range for a
The graphic device to be closed was not opened by the multiple console support (MCS) console.
closing task. 20 The program is not authorized to issue the
Application Programmer Response: Issue the MGCR or MGCRE macro. The program must
CLOSE macro instruction within the same task that be in supervisor state and PSW key 0-7.
issues the OPEN macro instruction, or remove the 24 Recovery could not be established while
incorrect CLOSE macro instruction. Then run the job processing a command, whether issued by the
step again. operator or issued using the MGCR or MGCRE
System programmer response: If the error recurs macros.
and the program is not in error, look at the messages in 28 Parameters specified on the MGCR or MGCRE
the job log for more information. Search problem cannot be accessed because they are
reporting data bases for a fix for the problem. If no fix specified incorrectly.
exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job. 2C The command abended because the security
product took longer than 30 seconds to
Source: DFSMSdfp process the command authorization
304 z/OS V1R10.0 MVS System Codes
D23
(RACROUTE). It was causing a wait in the yyyy This halfword is the unique reason code
Console main task, which cannot be tolerated. identifier. Only yyyy is listed below.
30 The request specified both
The following are the yyyy values and their meanings:
CMDFLAG=SUBSYS and CMDFLAG=TSO.
These parameter values are mutually Code Explanation
exclusive.
0002 The caller issued a WTO or WTOR specifying
34 The request specified both CMDFLAG=TSO an incorrect number of lines. Possible errors:
and CMDFLAG=COMMTASK. These v A WTOR was specified with SYNCH=NO
parameter values are mutually exclusive. and more than one line was specified
38 The request specified CMDFLAG=TSO, but did v A multiple-line WTO with zero lines was
not specify CONSID. CONSID is required with specified
CMDFLAG=TSO. v A WTO or WTOR was specified with
| 3C The request specified CONSNAME or CONSID SYNCH=YES, and more than 14 lines were
| and found the console name or ID to be specified
| defined, but the control blocks that represent 0003 The parameter list that the caller passed does
| the console could not be accessed. not reside in storage that the caller can access.
40 The request parameter list indicated that a 0004 The caller requested a WTO or WTOR with a
UTOKEN address was provided, but the text length of zero, or a multiple-line WTO was
UTOKEN address contains a zero. specified with one of the lines having a text
System action: If reason code X'24' was issued, the length of zero.
system does not process the command. 0005 A caller requested a WTO or WTOR with a text
If reason code X'2C' was issued, the command will be length too long for the type of line. The text
abended to fail the command. was truncated to the maximum length for that
type of line.
For all other reason codes, the system does not
process the MGCR or MGCRE macro. 0006 A caller that was not in key 0-7 or not
APF-authorized requested one or more of the
System programmer response: If reason code X'24' authorized WTO keywords.
was issued, ask the operator to issue the command
again. If the problem persists, search problem reporting 0007 The caller requested mutually exclusive
data bases for a fix for the problem. If no fix exists, functions. Examples:
contact the IBM Support Center. v Both CONSID and CONSNAME were
specified
If reason code X'2C' was issued, check the security
product’s database to determine why the RACROUTE is v A multiple-line message requested
taking longer than usual. incompatible or invalid line types for a line
v A WTOR prefix was specified with a WPX
For all other reason codes, determine which module
issued the MGCR or MGCRE macro: | 0008 The caller supplied an incorrect parameter list
v If the module is installation-provided code, correct the | structure. Here are possible reasons:
MGCR or MGCRE macro. Recompile and run the job | v WPX length was not correct.
step again. | v WQEBLK parameter was specified with an
v If the module is an IBM module, search problem | incorrect WPL.
reporting data bases for a fix for the problem. If no fix | v Zero address was specified for the WPL.
exists, contact the component group for the module
at the IBM Support Center. 0009 The caller requested a WTO or WTOR with a
zero text address, or a multiple-line WTO was
Source: Master scheduler specified with one of its lines having a zero text
address.
D23 000B The caller specified LINKAGE=BRANCH with
Explanation: An error occurred in processing for a unsupported keywords.
write to operator (WTO) or write to operator with reply 000C The caller issued a WTOR with SYNCH=NO
(WTOR). and LINKAGE=BRANCH.
Register 15 contains a hexadecimal error code in the 000E This processor does not hold the restart
format xxxxyyyy. The fields in this error code are the resource.
following:
xxxx This halfword is for IBM internal use only.
Chapter 2. System Completion Codes 305
D24 • D37
000F The system could not access the action code persists, notify the system programmer.
storage.
System programmer response: Search problem
0010 The system found an incorrect value in the reporting data bases for a fix for the problem. If no fix
write-to-operator queue element (WQE). exists, contact the IBM Support Center.
0011 The console name is reserved or incorrect. | If the reason code is X'0012', then increase the
| SQA/ESQA values in IEASYSxx in parmlib.
yy12 The system was unable to create or expand an
SQA cellpool. The return code from the failing | Source: Console services
STORCSR will be found in yy.
yy20 A GETCELL for an operator reply element | D24
(ORE) failed. The return code from the
GETCELL macro will be found in yy.
| Explanation: An error occurred in the Write To Log
| (WTL) parameter list.
yy21 The system could not build a cellpool for an
| Here are the reason codes and their meanings:
operator reply element (ORE). The return code
from the BLDCPOOL macro will be found in yy. | Code Explanation
yy22 The system could not obtain storage for an | 01 No WTLBLK address was specified.
operator reply element (ORE). The return code
from the STORAGE macro will be found in yy. | 02 The WTLBLK parameter is not valid. The
| acronym is not valid.
0030 A write-to-operator queue element (WQE) for
an operator reply could not be obtained. | 03 The WTLBLK parameter is not valid. The
| version level is incorrect.
yy40 A recovery environment could not be
established. The return code from the ESTAE | 04 The WTLBLK parameter is not valid. The
macro will be found in yy. | length of the WTLBLK parameter is not correct
| for the version level.
yy50 A LOADWAIT request failed. The return code
from the BLWLDWT service will be found in yy. | 05 The WTLBLK parameter is not valid. Reserved
| fields or bits are not zeros.
yy51 The system could not obtain needed storage.
The return code from the STORAGE macro will | 06 The WTLBLK parameter is not valid. Field
be found in yy. When yy equals 00, a WTO | WTLBLen does not contain a valid length of
multi-line exceeded the maximum 65533 total | the header and text.
lines allowed. The WTO multi-line connect was
too large. D2D
yy52 A failure occurred in the data block create Explanation: A program requested an overlay. In
routine. The return code from the data block answer to the request, the overlay supervisor was using
routine will be found in yy. program fetch to load a program segment from the
| 0053 Storage could not be obtained for the dummy library. Fetch found an incorrect record type in the
| SSI control blocks (SSOB, SSWT, WQE, ORE). segment to be loaded.
| Processing continues for this message;
| however, the SSI is not called for this Note: Overlay programs run only in 24-bit addressing
| message. mode, not in 31-bit addressing mode.
0055 The caller requested a function that requires System action: The system abnormally ends the
additional parameters. program that requested the overlay. The system writes
an ABEND dump, if a dump DD statement is provided.
| 0060 Delayed issued WTO subtask timed out.
Application Programmer Response: Link edit and
| yy61 Delayed issued WTO subtask could not run the program again.
| establish recovery, where yy is the ESTAEX
return code. Source: Overlay supervisor
| yy62 Delayed Issued WTO task could not attach a
| subtask where yy is the ATTACH return code. D37
Fyyy An internal processing error occurred. The yyy Explanation: The error occurred when an output
field contains the abend code of the failure. operation to a direct access device was requested. This
system completion code is accompanied by message
Application Programmer Response: Correct the IEC031I.
program issuing the WTO or WTOR macro. Recompile
the program. Run the job step again. If the problem Refer to the explanation of message IEC031I for
complete information about the task that was ended and
306 z/OS V1R10.0 MVS System Codes
D78 • D83
for an explanation of the return code (rc in the message 04 BAD LENGTH: The length of the area to get or
text) in register 15. free is not greater than zero.
Application Programmer Response: Respond as 08 BAD ALIGNMENT: The pointer to the area to
indicated for message IEC031I. free is not on a doubleword boundary.
System programmer response: If the error recurs 0C DUPLICATE FREEMAIN: The area to free has
and the program is not in error, look at the messages in already been freed.
the job log for more information. Search problem
10 INCORRECT SUBPOOL: The subpool for the
reporting data bases for a fix for the problem. If no fix
area to free is not the subpool in which the
exists, contact the IBM Support Center. Provide the JCL
area is allocated.
and the program listing for the job.
14 INVALID OVERLAP: Part of the area to free
Source: DFSMSdfp
equals part of the area allocated, but the match
is not correct for either a full or partial
D78 FREEMAIN.
Explanation: An error occurred when the system tried 18 NOT FOUND: The area to free does not have
to process an RU or VRU form of the GETMAIN or an a corresponding GETMAIN entry in the tracking
RU form of the FREEMAIN macro. A reason code in the table, and the caller did not specify that it
SDWACRC field of the system diagnostic work area should not have.
(SDWA) explains the error:
1C FOUND: The area to free has a corresponding
Code Explanation GETMAIN entry in the tracking table, and the
caller specified that it should not have.
04 A FREEMAIN request was specified for local
system queue area (LSQA) virtual storage that 20 NOT FREED: There is a temporary area still
is associated with a task. However, the virtual allocated at the end of SVC processing.
storage area specified is not associated with
A0 A RACF module issued a get-space request.
the task.
However, register 1 is not equal to zero and
08 The system could not satisfy a request for does not point to a buffer previously created by
LSQA storage because there is not enough the program.
central storage for the control blocks needed to
A4 A RACF module issued a get-space request.
support the request.
However, the subpool in register 0 is not the
System action: The system issues message IEA705I. subpool in which the previously created buffer
The system abnormally ends the current task. is allocated.
Application Programmer Response: For reason A8 A RACF module issued a free-space request.
code X'04', change the FREEMAIN request to obtain However, register 1 is equal to zero.
storage owned by the task. Run the job step again.
AC A RACF module issued a free-space request.
For reason code X'08', resubmit the job. If the system However, register 1 does not point to the buffer
issues this abend frequently, notify the system previously created by the program.
programmer.
Identify and correct the indicated error.
System programmer response: See installation
procedures to decrease the fixed central storage System programmer response: Using IPCS, format
requirements of the system. the dump taken for this abend. For an explanation of
the dump title, see z/OS Security Server RACF
Source: Virtual storage manager (VSM)
Diagnosis Guide.
D82
D83
Explanation: While RACF was processing a
Explanation: While RACF was processing a
RACROUTE REQUEST=AUTH, an error occurred in the
RACROUTE REQUEST=VERIFY, an error occurred in
RACF storage manager.
the RACF storage manager.
System action: The system terminates the task.
System action: The system terminates the task.
Application Programmer Response: Register 15
Application Programmer Response: Register 15
contains a hexadecimal reason code. (Message
contains a hexadecimal reason code. (Message
ICH409I, if issued, also contains this reason code.)
ICH409I, if issued, also contains this reason code.)
Code Explanation
Code Explanation
Chapter 2. System Completion Codes 307
D84 • D85
04 BAD LENGTH: The length of the area to get or 04 BAD LENGTH: The length of the area to get or
free is not greater than zero. free is not greater than zero.
08 BAD ALIGNMENT: The pointer to the area to 08 BAD ALIGNMENT: The pointer to the area to
free is not on a doubleword boundary. free is not on a doubleword boundary.
0C DUPLICATE FREEMAIN: The area to free has 0C DUPLICATE FREEMAIN: The area to free has
already been freed. already been freed.
10 INCORRECT SUBPOOL: The subpool for the 10 INCORRECT SUBPOOL: The subpool for the
area to free is not the subpool in which the area to free is not the subpool in which the
area is allocated. area is allocated.
14 INVALID OVERLAP: Part of the area to free 14 INVALID OVERLAP: Part of the area to free
equals part of the area allocated, but the match equals part of the area allocated, but the match
is not correct for either a full or partial is not correct for either a full or partial
FREEMAIN. FREEMAIN.
18 NOT FOUND: The area to free does not have 18 NOT FOUND: The area to free does not have
a corresponding GETMAIN entry in the tracking a corresponding GETMAIN entry in the tracking
table, and the caller did not specify that it table, and the caller did not specify that it
should not have. should not have.
1C FOUND: The area to free has a corresponding 1C FOUND: The area to free has a corresponding
GETMAIN entry in the tracking table, and the GETMAIN entry in the tracking table, and the
caller specified that it should not have. caller specified that it should not have.
20 NOT FREED: There is a temporary area still 20 NOT FREED: There is a temporary area still
allocated at the end of SVC processing. allocated at the end of SVC processing.
A0 A RACF module issued a get-space request. 44 Too many actions specified on ICHEINTY
However, register 1 is not equal to zero and macro.
does not point to a buffer previously created by
A0 A RACF module issued a get-space request.
the program.
However, register 1 is not equal to zero and
A4 A RACF module issued a get-space request. does not point to a buffer previously created by
However, the subpool in register 0 is not the the program.
subpool in which the previously created buffer
A4 A RACF module issued a get-space request.
is allocated.
However, the subpool in register 0 is not the
A8 A RACF module issued a free-space request. subpool in which the previously created buffer
However, register 1 is equal to zero. is allocated.
AC A RACF module issued a free-space request. A8 A RACF module issued a free-space request.
However, register 1 does not point to the buffer However, register 1 is equal to zero.
previously created by the program.
AC A RACF module issued a free-space request.
However, register 1 does not point to the buffer
Identify and correct the indicated error.
previously created by the program.
System programmer response: Using IPCS, format
the dump taken for this abend. For an explanation of Identify and correct the indicated error.
the dump title, see z/OS Security Server RACF
System programmer response: Using IPCS, format
Diagnosis Guide.
the dump taken for this abend. For an explanation of
the dump title, see the z/OS Security Server RACF
D84 Diagnosis Guide.
Explanation: While RACF was processing a
RACROUTE REQUEST=LIST, an error occurred in the D85
RACF storage manager.
Explanation: While RACF was processing a
System action: The system terminates the task. RACROUTE REQUEST=DEFINE, an error occurred in
the RACF storage manager.
Application Programmer Response: Register 15
contains a hexadecimal reason code. (Message System action: The system terminates the task.
ICH409I, if issued, also contains this reason code.)
Application Programmer Response: Register 15
Code Explanation contains a hexadecimal reason code. (Message
ICH409I, if issued, also contains this reason code.)
308 z/OS V1R10.0 MVS System Codes
DC2
Code Explanation | error. The following are the RRRR values and their
| meanings:
04 BAD LENGTH: The length of the area to get or
free is not greater than zero. Code Explanation
08 BAD ALIGNMENT: The pointer to the area to 0004 Virtual address specified is not valid.
free is not on a doubleword boundary.
0010 Spin locks held.
0C DUPLICATE FREEMAIN: The area to free has
0011 Local lock held.
already been freed.
0012 Subspaces exist in target space.
10 INCORRECT SUBPOOL: The subpool for the
area to free is not the subpool in which the 0013 Caller in amode 24.
area is allocated.
0014 Target address space does not exist.
14 INVALID OVERLAP: Part of the area to free
equals part of the area allocated, but the match 0015 Maximum number of segments have been
is not correct for either a full or partial obtained.
FREEMAIN. 0016 Memory limit exceeded.
18 NOT FOUND: The area to free does not have 0017 Insufficient free space to satisfy request.
a corresponding GETMAIN entry in the tracking
table, and the caller did not specify that it 0018 Could not obtain storage to manage request.
should not have. 0019 Caller must be authorized to perform request.
1C FOUND: The area to free has a corresponding 001A No memory objects above 4GB have been
GETMAIN entry in the tracking table, and the allocated.
caller specified that it should not have.
001B Frame/pagefix request conflict.
20 NOT FREED: There is a temporary area still
allocated at the end of SVC processing. 001C Page is lost.
A0 A RACF module issued a get-space request. | 001D No 64BIT Shared or 64BIT Common storage
However, register 1 is not equal to zero and | above 4G has been allocated.
does not point to a buffer previously created by 001E Fixed page found.
the program.
001F ChangeGuard request in progress for the
A4 A RACF module issued a get-space request. memory object.
However, the subpool in register 0 is not the
subpool in which the previously created buffer 0020 User environment has changed (usually after
is allocated. enablement).
A8 A RACF module issued a free-space request. 0021 Memlimit was zero.
However, register 1 is equal to zero.
| 0022 Pageframesize=1MEG is specified, but large
AC A RACF module issued a free-space request. | frame area is not available.
However, register 1 does not point to the buffer
0030 Parameter list is not accessible.
previously created by the program.
0031 Range list is not accessible.
Identify and correct the indicated error.
0032 Version is not supported.
System programmer response: Using IPCS, format
0033 Range list must be specified.
the dump taken for this abend. For an explanation of
the dump title, see the z/OS Security Server RACF 0034 ALET not valid.
Diagnosis Guide.
0035 ALET not allowed for problem program invoker.
0036 Unauthorized caller specified
DC2
CONTROL(AUTH).
Explanation: RSM virtual services failed.
0037 Key specified is not valid for caller.
A DC2 abend will be issued for an invalid request and
0038 Bits 0–31 of user token are non-zero for
can be issued for a valid request which cannot be
authorized caller.
successfully processed by RSM. DC2 abends are today
only generated when an IARV64 request is issued. 0039 Bits 32–63 of user token are zero for
unauthorized caller.
An IARV64 macro invocation to manage storage above
| 2 gigabytes failed. The 4 byte hexadecimal reason code 003A Specified MATCH=USERTOKEN and no token
| is in the format xxRRRRyy, where RRRR describes the specified.
Chapter 2. System Completion Codes 309
DC2
003B No memory objects were found for the 0056 Affinity=System Detach already performed.
specified user token.
0057 Reserve field not zero.
003C Memory object were found for this request but
none were detached.
| 0058 Range or address specified includes shared
| storage or pages backed by large frames or
003D User token specified does not match the | common storage that is not supported by the
memory object for the specified address. | service requested.
003E User token was specified, and address 0059 Invalid request for 0 segments.
specified is for a memory object that was
005A A bad CONVERT parameter specified by
created without a user token.
CHANGEGUARD.
003F Requested memory object could not be found.
005C Work area length is too small.
0040 Address specified is not valid.
| 005D There were not enough frames available for
0041 OWNER value specified is not valid for caller. | backing large pages.
0042 Guard size is greater than object size. 0060 A range was specified that contains hidden
pages.
0043 Caller must be authorized for memory object
specified. 0061 A range was specified that contains protected
pages.
0044 Memory object not created with
CONTROL=AUTH attr; required for this 0062 A range was specified that contains guarded
request. pages.
0045 A range was specified that is not contained 0081 A cross-memory error has occurred.
within a single memory object.
0082 An I/O error has occurred.
0047 A range was specified that does not start on a
00AA Unable to access parmlist or workarea.
page boundary.
| 00AC Keyword CONVERTSTART is not allowed on a
0048 TCB TOKEN for calling task does not match
| large page request.
TCB TOKEN for memory object.
0049 TCB TOKEN specified does not match TCB
| 00AE AFFINITY=SYSTEM was specified with a
TOKEN for memory object.
| MEMOBJSTART address that is not in the
| 64BIT Common or the 64BIT Shared areas.
004A TCB TOKEN specified does not map to valid
00EB Internal system error previously detected. The
task.
request could not be processed.
004B TCB TOKEN specified does not map to valid
00EC Inconsistent data.
address space.
00ED Internal service failed.
004C TCB TOKEN specified does not map to valid
address space. 00EF A page with I/O in progress has no pagefix
PCB.
004D TCB TOKEN specified does not map to valid
task. 00F0 Parameter not valid.
004E TCB TOKEN required but not specified. 00F1 Duplicate memory object found.
004F Request not supported. 00F2 Memory object is damaged
0050 Request to unfix a page that is not currently 00F3 User Token Block is damaged.
fixed.
00F4 Unable to obtain TCB Token.
0051 The range or starting address specified does
not start on a segment boundry. 00F5 Internal control block damaged.
0052 Invalid View was specified. 00F6 Parameter not valid.
| 0053 Pageframesize=1MEG/Max is specified, but the 00F7 Parameter not valid.
| caller is not authorized. 00F8 Internal control block damaged.
| 0054 Pageframesize=1MEG is specified, but the 00F9 Memory object detected is not for specified
| enhanced DAT architecture is not available. address.
0055 A duplicate UToken already exists for the 00FA Common release failed.
memory object specified for the address space.
00FB Internal control block damaged.
310 z/OS V1R10.0 MVS System Codes
DC3 • DC5
00FE Unable to free storage. 04 The XCF member name passed on the
IXZXIXAT macro contains imbedded blanks.
00FF System Error.
05 JESXCF validation of the member name on the
System action: The IARV64 request has failed. The
IXZXIXAT macro failed.
system was unable to complete operation requested
using IARV64 macro. 06 The XCF group name passed on the IXZXIXAT
macro either contains a character that is not
Operator response: None.
valid or is all blanks.
Application Programmer Response:
07 The XCF group name passed on the IXZXIXAT
v If the reason code is memory limit exceeded (0016), macro contains imbedded blanks.
determine if the MEMLIMIT value for the address
space can be raised to accommodate its storage 08 Validation of the group name on the IXZXIXAT
needs. macro failed.
v If the reason code indicates an internal RSM error 09 Validation of the IXZXIXAT/IXZXIXDT
except common release (00FA), then rerun the job to parameter list failed.
determine if the error happens again, and collect the
0A An internal error occurred.
appropriate diagnostic information.
0B An internal error occurred.
System programmer response:
v If the reason code indicates a parameter or 0C An internal error occurred.
request–specific error, then correct the parameters 0D An internal error occurred.
the application code uses to issue the IARV64 macro.
v If the reason code is common release (00FA), then 0E An internal error occurred.
the application has tried to detach a memory object 0F The group token passed on the IXZXIXDT
which contains fixed pages or a task that owns pages macro contains an eyecatcher that is not valid.
which are still fixed has terminated.
10 The group token passed on the IXZXIXDT
v If the reason code is memory limit exceeded (0016),
macro contains a version number that is not
and the MEMLIMIT for the address space cannot be
valid.
raised to meet the applications needed, then the
application needs to be changed to reduce the 12 The JES indicator flag bit (WHICHJES) in the
storage consumption within the address space. parameter list had both or none of the JES
flags set.
Source: RSM
13 The release in the IXZYIXAT mapping macro is
not supported.
DC3
14 The release validation of the IXZYIXAT
Explanation: This abend code is used by WebSphere
mapping macro returned an unknown reason
Application Server on z/OS. This abend code is used by
code.
WebSphere Application Server on z/OS. See
WebSphere Application Server on z/OS for further 15 The maintenance level of the IXZYIXAT
information. mapping macro parameter list is not current.
16 An internal error occurred.
DC5
17 An internal error occurred.
Explanation: JES common coupling services
18 An internal error occurred.
(JESXCF) detected an unrecoverable error during its
processing. A hexadecimal reason code returned in 19 An internal error occurred.
register 0 describes the error:
1A An internal error occurred.
Code Explanation
1B An internal error occurred.
01 The parameter list passed to the IXZXIXAT or
IXZXIXDT macro service does not have a valid 1C The IXZXIXAT macro failed because the
eyecatcher. member was already active in that group.
02 The parameter list passed to the IXZXIXAT or 1D The member name specified on the IXZXIXDT
IXZXIXDT macro service has an incorrect level. macro could not be found.
03 The XCF member name passed on the 1E An internal error occurred.
IXZXIXAT macro either contains a character 1F The data space could not be created for the
that is not valid or is all blanks. IXZXIXAT macro request.
Chapter 2. System Completion Codes 311
DC4
20 JESXCF could not add the JES member to the
| DC4
specified XCF group.
| Explanation: An error occurred in processing for
21 The XCF group maximum has been reached.
| either IARCP64 or IARST64.
22 The XCF member maximum has been
| Here are the values and their meanings for IARCP64:
reached.
| Code Explanation
23 JESXCF could not add the JES member to the
specified XCF group. | xx0410xx (IARCP64AbendRsnCellAddrLow)
| The cell address passed to the IARCP64
24 An internal error occurred.
| FREE service is within a meg used for storage
25 The IXZXIXDT macro failed, because it was | pools, but the address is less than the address
issued from a different ASCB and TCB than | of the first usable storage address.
the issuer of the IXZXIXAT macro that created
| Action: Correct the address passed to
the specified member.
| IARCP64 FREE, making sure that it is the
26 An internal error occurred. | same address that was returned from IARCP64
| GET.
27 An internal error occurred.
| xx0412xx
32 An internal error occurred, probably because | (IARCP64AbendRsnBuildMotherFromCmro)
the JESXCF address space was forced and | The OWNINGTASK was specified as the
restarted. | mother task, but the caller is running on the
33 An internal error occurred. | CMRO task. This is not supported.
34 An internal error occurred. | Action: Correct the specification of
| OWNINGTASK. If you need the storage to
35 An internal error occurred. | survive job step termination, then specify RCT
36 An internal error occurred. | as the owner. If you are unauthorized, use
| OWNINGTASK that is set to either CMRO or
System action: JESXCF produces a dump for the | JOBSTEP.
error (unless the dump is suppressed by DAE), and
return code X'C' is returned to the caller of the service. | xx0413xx (IARCP64AbendRsnCellNotInExtent )
| The request was to the IARCP64 or IARST64
Operator response: Notify your system programmer. | FREE service, and the address of the storage
System programmer response: If this abend was | passed in, is not within the bounds of a cell
issued due to an error in an installation invocation of the | pool.
IXZXIXAT or IXZXIXDT macro, correct the error based | Action: Correct the address passed to
on the reason code provided. Refer to z/OS MVS | IARCP64 FREE or IARST64 FREE, making
Programming: JES Common Coupling Services for | sure that it is the same address that was
information about using and coding IXZXIXAT and | returned from IARCP64 GET or IARST64 GET.
IXZXIXDT.
| xx0414xx (IARCP64AbendRsnBuildNotRctOrCmro )
Interpret the return and reason code provided and | The parameter list passed to the IARCP64
determine if the problem is due to a configuration error | BUILD service from an SRB or cross memory
or coding error. If the problem is due to a configuration | environment did not specify RCT or CMRO as
error, then correct the problem and restart JES. If the | the owning task.
problem is due to a coding error, search the problem
reporting data bases for a fix to the problem. If none | Action: Fix the OWNINGTASK parameter to
exist, contact the IBM support center with the return and | specify RCT or CMRO. Alternatively, build the
reason codes and the dump produced by the error. | pool from a different environment.
For additional information on dumping the JES and | xx0415xx (IARCP64AbendRsnBuildCellSizeZero )
JESXCF address spaces, as well as restarting the | The parameter list passed to the IARCP64
JESXCF address space, see z/OS MVS Programming: | BUILD service specified the CELLSIZE as
JES Common Coupling Services. | zero.
Source: JES common coupling services (JESXCF) | Action: Change the cell size to be in the range
| of 1 to 520 192.
| xx0416xx (IARCP64AbendRsnBuildNotAuth)
| The parameter list passed to the IARCP64
| BUILD service from an unauthorized caller
| requested an authorized option: system key,
312 z/OS V1R10.0 MVS System Codes
DC4
| common storage, RCT ownership, | Action: Correct the address passed to
| MEMLIMIT=NO, MOTKN, TYPE=FIXED or | IARCP64 FREE, making sure that it is the
| DREF. | same address that was returned from IARCP64
| GET.
| Action: Either correct the environment such
| that the caller is authorized, or change the | xx041Cxx (IARCP64AbendRsnIARV64Error)
| options on IARCP64 BUILD such that it does | During processing of IARCP64 BUILD or GET,
| not request options that require authorization. | a call to the IARV64 service for GETSTOR,
| GETCOMMON, PAGEFIX, or PROTECT failed.
| xx0417xx (IARCP64AbendRsnBuildCellSizeTooBig ) | The failing return code from IARV64 was
| The parameter list passed to the IARCP64
| placed in register 2 before the abend. The
| BUILD service specified a cell size larger than
| failing reason code from IARV64 was placed in
| the maximum size supported.
| register 3 prior to the abend.
| Action: Specify a size between 1 and 520 192.
| Action: Examine the return and reason code
| If a larger storage area is needed, consider
| as documented under IARV64 to determine if
| using IARV64 REQUEST=GETSTOR or
| you can resolve the problem.
| GETCOMMON.
| xx041Dxx
| xx0418xx (IARCP64AbendRsnBuildKeyNot9) | (IARCP64AbendRsnCellPoolHeaderKeyNot0)
| The parameter list passed to the IARCP64
| The cell pool header points to a key 0 control
| BUILD service from an unauthorized caller,
| block used to protect cell pool information. The
| specified a storage key other than 9.
| pointer did not point to key 0 storage. This
| Action: Either remove the key specification for | would happen if a caller tried to trick the
| an unauthorized caller, specify key 9, or | service into getting storage that the user was
| change the program to run in an authorized | not normally allowed to get.
| environment.
| Action: Correct the cell pool address passed
| xx0419xx (ARCP64AbendRsnCellOverRun) | to IARCP64 GET, making sure that it is the
| The request was to the IARCP64 or IARST64 | same address that was returned from IARCP64
| FREE service, and the trailer data at the end of | BUILD. Do not modify the cell pool header,
| the cell was detected as being overrun. If the | other than through IARCP64 services.
| overrun is sufficiently large, it causes damage
| xx041Exx
| to the following cell. The caller is abended, so
| (IARCP64AbendRsnHeaderFailedValidityCheck)
| they can fix the code to not use more storage
| The cell pool header points to a key 0 control
| than is requested.
| block used to protect cell pool information. The
| Action: Determine whether the storage has | pointer did not point to a valid structure used
| been overrun or whether the trailer data was | by IARCP64. This would happen if a caller
| overlaid by some other code. Fix the code so | tried to trick the service into getting storage
| that it only uses the amount of storage | that the user was not normally allowed to get.
| requested. Possibly increase the cell size to
| Action: Correct the cell pool address passed
| meet the program’s needs.
| to IARCP64 GET, making sure that it is the
| xx041Axx (IARCP64AbendRsnCellNotInUse) | same address that was returned from IARCP64
| The request was to the IARCP64 or IARST64 | BUILD.
| FREE service, and the address of the storage
| xx041Fxx (IARCP64AbendRsnHeaderDamaged)
| passed in, is already in the freed state. This
| The cell pool header authorized area was
| happens when an application frees the storage
| damaged. This could be caused by a storage
| twice.
| overlay or by a user deleting a cell pool while
| Action: Determine whether the current | other work units are trying to obtain a cell from
| application is freeing the storage twice or | the pool.
| whether it is using a cell that some other
| Action: Make sure that the application does
| program is freeing twice.
| not request cells during or after the cell pool is
| xx041Bxx (IARCP64AbendRsnNotOnCellBoundary) | deleted.
| The request was to the IARCP64 or IARST64
| xx0420xx (IARCP64AbendRsnCphaNotQueued)
| FREE service, and the address of the storage
| The cell pool header authorized area was not
| passed in is not on a cell boundary in the cell
| queued to the owning task as expected. This
| pool from which the GET request was satisfied.
| could happen due to storage overlays, or
| possibly the user doing IARCP64 DELETE
| while the pool was still in use.
Chapter 2. System Completion Codes 313
DC4
| Action: Make sure that the application does | Action: Collect a dump and report the problem
| not request cells during or after the cell pool is | to IBM
| deleted. If the problem persists, collect a dump
| xx0428xx (IARCP64AbendRsnUnexpectedError)
| and contact IBM service.
| During processing of IARCP64 BUILD,
| xx0421xx (IARCP64AbendRsnBuildVersionHigh) | DELETE or the cell pool expansion on a GET,
| The parameter list passed to the IARCP64 | an unexpected abend occurred. An SDUMP
| BUILD service has a version level higher than | should have been generated.
| the current implementation can support.
| Action: Collect the dump and report the
| Action: Correct the call of IARCP64 such that | problem to IBM.
| you don’t specify a level or use parameters
| xx052Axx (IARCP64AbendRsnValidationError)
| that are not supported on the release of the
| The call to the IARCP64 GET service detected
| operating system on which it is intended to run.
| a validation error when locating the storage
| xx0422xx (IARCP64AbendRsnBuildBadParmlist) | pool to be used. The possible cause is the
| The parameter list passed to IARCP64 BUILD | storage overlay of the storage pool control
| is not addressable in the caller’s key or is not | block in the caller’s key.
| valid storage.
| Action: Collect a dump and report the problem
| Action: Correct the calling program to place | to IBM.
| the parameter list in storage addressable in the
| xx052Cxx (IARST64AbendRsnCellLT4Gig)
| primary address space.
| The call to the IARCP64 or IARST64 FREE
| xx0423xx (IARCP64AbendRsnBuildNoOwner) | service is passed to a cell address less than
| The parameter list passed to the IARCP64 | 4GB, so it cannot be a valid cell address in a
| BUILD service for a common cell pool does not | 64-bit cell pool.
| have an owner option specified.
| Action: Pass a storage address that is
| Action: Add the OWNER keyword to the call of | obtained with IARCP64 or IARST64 GET.
| IARCP64 BUILD when building a cell pool in
| common. | Here are the values and their meanings for IARST64:
| xx0424xx (IARCP64AbendRsnDeleteNotChained) | Code Explanation
| A request was made to the IARCP64 DELETE
| service for a user key cell pool. The control | xx0410xx (IARST64AbendRsnCellAddrLow
| information for this cell pool was missing from | The storage address passed to the IARST64
| the system queue used to maintain it. This can | FREE service is within a meg used for storage
| only happen if the caller has two tasks racing | pools, but the address is less than the address
| to delete the same cell pool. | of the first usable storage address.
| Action: Fix the application cleanup logic so | Action: Correct the address passed to
| that the cell pool is only deleted once. | IARST64 FREE, making sure that it is the
| same address that was returned from IARST64
| xx0425xx (IARCP64AbendRsnPoolNotInCallerKey) | GET.
| The request to IARCP64 GET or DELETE was
| against a pool that was not in the key of the | xx0413xx (IARST64AbendRsnCellNotInExtent)
| caller. | The request was to the IARCP64 or IARST64
| FREE service, and the address of the storage
| Action: You must be in a key that has the | passed in is not within the bounds of a cell
| ability to modify the pool storage for the | pool.
| request to be processed.
| Action: The address passed to IARST64
| xx0426xx | REQUEST=FREE must be the same as the
| (IARCP64AbendRsnPrimaryExtentOverlaid) | address obtained from IARST64
| The request to IARST64 or IARCP64 GET was | REQUEST=GET.
| against a storage pool where the primary
| extent control information had been overlaid. | xx0419xx (IARST64AbendRsnCellOverRun)
| The request was to the IARCP64 or IARST64
| Action: Collect a dump and report the problem | FREE service, and the trailer data at the end of
| to IBM. | the cell was detected as being overrun. If the
| overrun is sufficiently large, it causes damage
| xx0427xx
| to the following cell. The caller is abended so
| (IARCP64AbendRsnSecondaryExtentOverlaid)
| that they can fix the code to not use more
| The request to IARST64 or IARCP64 GET was
| storage than is requested.
| against a storage pool where the secondary
| extent control information had been overlaid.
314 z/OS V1R10.0 MVS System Codes
DC4
| Action: Determine whether the storage has | Action: You must be in a key that has the
| been overrun or whether the trailer data was | ability to modify the pool storage for the
| overlaid by some other code. Fix the code so | request to be processed.
| that it only uses the amount of storage
| xx0426xx
| requested.
| (IARST64AbendRsnPrimaryExtentOverlaid)
| xx041Axx (IARST64AbendRsnCellNotInUse) | The request to IARST64 or IARCP64 GET was
| The request was to the IARCP64 or IARST64 | against a storage pool where the primary
| FREE service, and the address of the storage | extent control information had been overlaid.
| passed in is already in the freed state. This
| Action: Collect a dump and report the problem
| happens when an application frees the storage
| to IBM.
| twice.
| xx0427xx
| Action: Determine whether the current
| (IARST64AbendRsnSecondaryExtentOverlaid)
| application is freeing the storage twice or
| The request to IARST64 or IARCP64 GET was
| whether it is using a cell that some other
| against a storage pool where the secondary
| storage is freeing twice.
| extent control information had been overlaid.
| xx041Bxx (IARST64AbendRsnNotOnCellBoundary)
| Action: Collect a dump and report the problem
| The request was to the IARCP64 or IARST64
| to IBM.
| FREE service, and the address of the storage
| passed in is not on a cell boundary in the cell | xx0428xx (IARST64AbendRsnUnexpectedError)
| pool from which the GET request was satisfied. | During processing of IARST64 GET, an
| unexpected abend occurred. An SDUMP
| Action: When freeing storage with IARST64
| should have been generated.
| REQUEST=FREE, make sure to specify the
| address that was returned by IARST64 | Action: Collect the dump and report the
| REQUEST=GET. | problem to IBM.
| xx041Cxx (IARST64AbendRsnIARV64Error) | xx0511xx (IARST64AbendRsnKeyGT7Common)
| During processing of IARST64 GET, a call to | The request to IARST64 GET was for common
| the IARV64 service for GETSTOR, | storage, but the requested or caller key was
| GETCOMMON, PAGEFIX, or PROTECT failed. | greater than key 7. You cannot allocate
| The failing return code from IARV64 was | common storage in key 8 or above.
| placed in register 2 before the abend. The
| failing reason code from IARV64 was placed in | Action: Correct the key passed to IARST64
| register 3 before the abend. | GET or change your request to get private
| storage.
| Action: Examine the return and reason code
| as documented under IARV64 to determine if | xx0512xx (IARST64AbendRsnGetMotherFromCmro)
| you can resolve the problem. | The request was to the IARST64 GET service
| and specified OWNINGTASK(MOTHER), but
| xx0420xx (IARST64AbendRsnCphaNotQueue) | the caller is running on the CMRO task. You
| The cell pool header authorized area was not | cannot request that the mother task be the
| queued to the owning task as expected. This | storage owner from the CMRO task.
| could happen due to storage overlays or the
| caller bypassing the IARST64 macro and | Action: Either specify CMRO as the owner or
| PCing directly to the service with incorrect | specify RCT if you want the storage to persist
| input paramters. | across termination of the CMRO.
| Action: Make sure that the application is using | xx0514xx (IARST64AbendRsnGetNotRctOrCmro)
| the IARST64 macro to request storage. If the | The request was to the IARST64 GET service
| problem persists, collect a dump and contact | for private storage, and the caller was running
| IBM service. | in cross memory mode or SRB mode. In these
| environments, the OWNINGTASK parameter
| xx0425xx (IARST64AbendRsnPoolNotInCallerKey) | must be set to RCT or CMRO. Neither of these
| The request to IARST64 GET was against a | was specified, so the request failed.
| storage pool that was not in the key of the
| caller. Normally, this abends with an 0C4, but if | Action: Specify the OWNINGTASK parameter
| the pool is out of cells and is in storage that is | as RCT or CMRO.
| not fetch protected, the pool expand routine | xx0515xx (IARST64AbendRsnGetCellSizeZero)
| verifies that the caller is allowed to modify this | The request was to the IARST64 GET service
| storage pool. | and specified a length of zero.
Chapter 2. System Completion Codes 315
DC7
| Action: Specify a length between 1 and 64 | service is passed to a cell address less than
| KB. | 4GB, so it cannot be a valid cell address in a
| 64-bit cell pool.
| xx0516xx (IARST64AbendRsnGetNotAuth)
| The request was to the IARST64 GET service | Action: Pass a storage address that was
| and specified a parameter that requires the | obtained with IARCP64 or IARST64 GET.
| caller to be running in key 0-7. The caller is not
| System action: The abend is delivered to the
| authorized to use authorized options of
| applications recovery routine (if any). The application
| COMMON, DREF, FIXED,
| can retry or percolate.
| OWNINGTASK(RCT), CALLERKEY(NO), and
| Key00ToF0 set to a system key. | Operator response: None.
| Action: Either run the code in key 0-7 or do | Application Programmer Response: The
| not use authorized options. | programmer needs to determine whether the problem
| was caused by bad input, improper use of authorized
| xx0517xx (IARST64AbendRsnGetCellSizeTooBig)
| option, a structure damaged by the application, or a
| The request was to the IARST64 GET service
| defect in the service. For user-triggered problems,
| and specified a length greater than 64 KB.
| correct the error. For suspected damaged control
| Action: Specify a size between 1 and 64 KB. If | blocks, collect a dump and contact IBM service.
| larger storage is needed, consider using
| System programmer response: None.
| IARCP64 or IARV64 GETSTOR or
| GETCOMMON. | Problem determination: If the caller is authorized,
| some of the abends trigger a system SVC DUMP. For
| xx0518xx (IARST64AbendRsnGetKeyNot9)
| unauthorized callers, no dump will be taken. You can
| The request was to the IARST64 GET service
| either allocate a SYSMDUMP DD to gather a
| and specified a CALLERKEY(NO) and a value
| SYSMDUMP or use a SLIP on DC4 abends to collect a
| for Key00ToF0 that was not key 9, and the
| dump.
| caller is not authorized.
| Detecting Module: IAXCV, IAXCY, or IAXSV
| Action: The only key that an unauthorized
| user can specify is key 9. Either request key 9
| or change the specification to DC7
| CALLERKEY(YES).
Explanation: While running the APPC/MVS
| xx0529xx (IARST64AbendRsnGetSizeTooBig) transaction scheduler, the system found an
| The call to the IARST64 GET service specified unrecoverable error.
| a cell size larger than the maximum size
| supported. A reason code further describes the error:
| Action: Specify a size between 1 and 64 KB. If Code Explanation
| a larger storage area is needed, consider using 01 A CLASSADD statement in parmlib tried to
| IARCP64 or IARV64 REQUEST=GETSTOR or modify the characteristics of a class that
| GETCOMMON. already existed.
| xx052Axx (IARST64AbendRsnValidationError) 03 The system found an incorrect transaction
| The call to the IARST64 GET service detected scheduling type for a transaction program (TP).
| a validation error when locating the storage
| pool to be used. The possible cause is the 04 The system could not run the Resource Access
| storage overlay of the storage pool control Control Facility (RACF).
| block in the caller’s key. 05 The system could not create a security
| Action: Collect a dump and report the problem environment.
| to IBM. 07 The system could not delete the security
| xx052Bxx (IARST64AbendRsnMemLimitNoUnauth ) environment.
| The call to the IARST64 GET service 08 The system could not obtain SYSOUT and
| requested MEMLIMIT=NO, but is running accounting information from RACF.
| unauthorized (key 8-15 and problem program
| state). 10 The GETTRANS service could not notify
system management of a new TP.
| Action: Either specify MEMLIMIT=YES or call
| from an authorized environment. 11-20 An internal error occurred.
| xx052Cxx IARST64AbendRsnCellLT4Gig 21, 22, 23
| The call to the IARCP64 or IARST64 FREE The system could not initialize the APPC/MVS
transaction scheduler.
316 z/OS V1R10.0 MVS System Codes
DC7
24, 25 The system could not create a new ASCH receives a return code indicating that the
initiator. conversation was deallocated.
28-32 An internal error occurred. 04-07 Unpredictable.
33 The system could not obtain a transaction from 08 The initiator address space where the TP was
APPC. scheduled to run ends. The requestor of the
TP receives a return code indicating that the
34 The system could not initialize the APPC/MVS
conversation was deallocated.
transaction scheduler.
10 If the TP provided recovery, recovery receives
35 An attempt was made to start the ASCH
control. Otherwise, the TP ends.
address space by something other than a
START command. 11-20 Unpredictable.
36 The system could not initialize the ASCH. 21-23 The APPC/MVS transaction scheduler ends.
No restart is possible.
37 An internal error occurred.
24-25 The system continues processing with the
38-41 The system could not create a new ASCH
existing initiator.
initiator.
26-27 The system continues processing. If this error
42, 43 While APPC was active, the system could not
occurs again in a certain time period, the
initialize ASCH.
system attempts an automatic restart. If restart
44 The system could not verify the subsystem is unsuccessful, the APPC/MVS transaction
specified on the SUBSYS keyword in the scheduler ends.
current parmlib configuration.
28-32 Unpredictable.
45 While the system was processing a DISPLAY
33 The system continues processing. If this error
ASCH command, an error occurred.
occurs again in a certain time period, the
46 When the system tried to invoke the APPC system attempts an automatic restart. If restart
associate service, an error occurred. is unsuccessful, the APPC/MVS transaction
scheduler ends.
47 The system could not verify the subsystem
specified on the SUBSYS keyword in the 34 The APPC/MVS transaction scheduler ends.
current parmlib configuration. No restart is possible.
48, 49, 50 35 The system does not initialize the ASCH
After being notified that APPC was active, the address space.
system could not initialize the APPC/MVS
36-37 The APPC/MVS transaction scheduler ends.
transaction scheduler.
No restart is possible.
51 The ASCH failed while it was ending.
38-41 The system continues processing with the
52, 53, 54 existing initiator.
The system could not initialize the APPC/MVS
42-43 The system automatically attempts a restart. If
transaction scheduler.
this error occurs again, the APPC/MVS
56 After being notified that APPC was active, the transaction scheduler ends.
system could not initialize the APPC/MVS
44 The system continues processing with the
transaction scheduler.
existing initiator.
57 The system could not initialize the APPC/MVS
45 The system rejects the DISPLAY ASCH
transaction scheduler.
command.
59-65 An internal error occurred.
46 The system continues processing. The
System action: Depending on the reason code, one requestor of the transaction receives a return
of following: code indicating that the conversation was
deallocated.
Code System Action
47 The system continues processing with the
01 The system does not process the incorrect existing initiator.
CLASSADD statement. Other processing
continues. 48-50 The system automatically attempts a restart. If
this error occurs again, the APPC/MVS
03 The APPC scheduler does not schedule the transaction scheduler ends.
TP. The initiator address space where the TP
should have run ends. The requestor of the TP
Chapter 2. System Completion Codes 317
DC7
51-55 The APPC/MVS transaction scheduler ends. 38, 39, 40
No restart is possible. Notify the system programmer.
56 The system automatically attempts a restart. If 41 If the APPC/MVS transaction scheduler is not
this error occurs again, the APPC/MVS processing critical work, enter a CANCEL
transaction scheduler ends. ASCH command to end the APPC/MVS
transaction scheduler. Then enter the START
57 The APPC/MVS transaction scheduler ends.
ASCH command to restart the APPC/MVS
No restart is possible.
transaction scheduler. Otherwise, notify the
58-60 Unpredictable. system programmer.
61, 62 The system continues processing. 42 Notify the system programmer.
63, 64 The system automatically attempts a restart. If 43 If the APPC/MVS transaction scheduler ends,
this error occurs again, the APPC/MVS notify the system programmer. Enter a START
transaction scheduler ends. ASCH command.
Operator response: Depending on the reason code, 44 If the error occurs again, notify the system
do one of the following: programmer.
Code Explanation 45 Enter the DISPLAY ASCH command again. If
the error occurs again, notify the system
01, 03, 04 programmer.
Enter a DISPLAY ASCH command to find the
incorrect CLASSADD statement. Notify the 46 Notify the system programmer.
system programmer.
47 If the APPC/MVS transaction scheduler is not
08 Contact the RACF administrator to check the processing critical work, enter a CANCEL
installation’s security package for information ASCH command to end the APPC/MVS
identifying the error. transaction scheduler. Then enter the START
ASCH command to restart the APPC/MVS
10-22 Notify the system programmer. transaction scheduler. Otherwise, notify the
23 Enter a START ASCH command. If the error system programmer.
occurs again, notify the system programmer. 48, 49 Notify the system programmer.
24 Notify the system programmer. 50 If the APPC/MVS transaction scheduler ends,
25 If the APPC/MVS transaction scheduler is not notify the system programmer. Enter a START
processing critical work, enter a CANCEL ASCH command.
ASCH command to end the APPC/MVS 51-54 Notify the system programmer.
transaction scheduler. Then enter the START
ASCH command to restart the APPC/MVS 55 If the APPC/MVS transaction scheduler ends,
transaction scheduler. Otherwise, notify the notify the system programmer. Enter a START
system programmer. ASCH command.
26 Notify the system programmer. 56 If the APPC/MVS transaction scheduler ends,
enter a START ASCH command. If the error
27 If the APPC/MVS transaction scheduler ends, occurs again, notify the system programmer.
notify the system programmer. Enter a START
ASCH command. 57-61 Notify the system programmer.
28-32 Notify the system programmer. 62 If the APPC/MVS transaction scheduler is not
processing critical work, enter a CANCEL
33 The system continues processing. The ASCH command to end the APPC/MVS
requestor of the transaction receives a return transaction scheduler. Then enter the START
code indicating the conversation was ASCH command to restart the APPC/MVS
deallocated. transaction scheduler. Otherwise, notify the
34 Enter a START ASCH command. If the error system programmer.
occurs again, notify the system programmer. 63, 64 If the error occurs again, notify the system
35 Notify the system programmer. programmer.
36 If the APPC/MVS transaction scheduler ends, System programmer response: Depending on the
notify the system programmer. Enter a START reason code, do one of the following:
ASCH command. Code Explanation
37 Enter a START ASCH command. If the error 01 Delete the incorrect class using a CLASSDEL
occurs again, notify the system programmer.
318 z/OS V1R10.0 MVS System Codes
DFB
statement in the current parmlib configuration. 03 The connect subsystem interface (SSI) routine
Then try to add the class again, using a in module IATSICD could not establish the
CLASSADD statement. If the error occurs listen task, IATFCLT, for the FSS or the FSA.
again, contact the IBM Support Center.
05 Module IATSICD encountered an error during
03, 04 Search problem reporting data bases for a fix JESXCF attach processing (IXZXIXAT service).
for the problem. If no fix exists, contact the IBM
06 Module IATSICD encountered an error during
Support Center.
JESXCF mailbox build processing (IXZXIXMB
05 Check to see whether a program issued the service) for the default mailbox.
UNIX System Services spawn callable service,
07 Module IATSICD encountered an error during
passing a user ID that is not valid. If the user
JESXCF mailbox delete processing (IXZXIXMD
ID is valid, search problem reporting data
service) for the default mailbox.
bases for a fix for the problem. If no fix exists,
contact the IBM Support Center. 08 Module IATSICD encountered an error during
JESXCF detach processing (IXZXIXDT
07 Search problem reporting data bases for a fix
service).
for the problem. If no fix exists, contact the IBM
Support Center. 0B The common end-of-task exit routine in module
IATSICD found that a task in the FSS address
08 Contact the RACF administrator. Check the
space had ended unexpectedly.
installation’s security package for information
identifying the error. 0C The common end-of-task exit routine in module
IATSICD could not identify a task that had
10-34 Search problem reporting data bases for a fix
ended.
for the problem. If no fix exists, contact the IBM
Support Center. 15 The writer FSA specific connect routine,
IATFPCC, could not initialize for GETDS spool
35 Determine how APPC/MVS transaction
access using the block spooler.
scheduler initialization was invoked and take
appropriate actions to prevent re-occurrences. 16 The writer FSA specific connect routine,
The only proper way to initialize the scheduler IATFPCC, could not establish the read-ahead
is with the START command. task for the FSA.
36-43 Search problem reporting data bases for a fix 17 The writer FSA specific connect routine,
for the problem. If no fix exists, contact the IBM IATFPCC, could not establish the checkpoint
Support Center. writer task for the FSA.
44 Enter a valid JES subsystem on the SUBSYS 1F The FSI order interface routine, IATFCOR,
keyword in the current parmlib configuration. received a nonzero return code from the FSS
or FSA order routine.
45-65 Search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM 20 The FSI post interface routine, IATFCPT,
Support Center. received a nonzero return code from the FSA
post routine.
Source: APPC/MVS transaction scheduler
21 Module IATFCLT encountered an error during
JESXCF mailbox build processing (IXZXIXMB
DFB
Service) for a FSS/FSA mailbox.
Explanation: During processing in a functional
22 Module IATFCLT encountered an error during
subsystem (FSS) address space, a JES3 module
JESXCF mailbox clear processing (IXZXIXMC
detected an error. A hexadecimal reason code in
Service) for a FSS/FSA mailbox.
register 15 and/or the SDWA explains the error. (Note:
when the reason code is X'26', it will appear only in the 23 Module IATFCLT encountered an error during
SDWA, not in register 15.) JESXCF receive message processing
(IXZXIXRM Service) for a FSS/FSA mailbox.
Code Explanation
24 Module IATFCLT encountered an error during
01 The connect subsystem interface (SSI) routine
JESXCF acknowledge message processing
in module IATSICD determined that the START
(IXZXIXAC Service) for a FSS/FSA mailbox.
command for the FSS address space did not
contain a token. 25 Module IATFCLT encountered an error during
JESXCF mailbox delete processing
02 The connect subsystem interface (SSI) routine
(IXZXIXMD) for a FSS/FSA mailbox.
in module IATSICD could not locate the
MEMDATA header for the FSS address space. 26 A stop FSA abnormal order has been received
Chapter 2. System Completion Codes 319
DFB
from JES3. If a dump has been requested, a block spooler routine; the error return indicated
dump will be taken as part of abend processing that an error occurred during a cross-address
of the FSA task. space move.
29 The C/I FSS order processing routine, IATIIFO, 4A The scheduler JCL facility (SJF) PUTSWB
found that the FSI parameter list did not function returned an error code to the writer
contain an order. FSA scheduler work block (SWB) processing
service routine, IATFPSB.
2A The C/I FSS order processing routine, IATIIFO,
received an incorrect order type. 4B The scheduler JCL facility (SJF) UPDATE
function returned an error code to the writer
2B The C/I FSS order processing routine, IATIIFO,
FSA scheduler work block (SWB) processing
received an incorrect stop FSS order.
service routine, IATFPSB.
2C The C/I FSS order processing routine, IATIIFO,
4C The scheduler JCL facility (SJF) DELETESWB
could not locate the C/I communications block
function returned an error code to the writer
(CCB).
FSA scheduler work block (SWB) processing
33 The writer FSA quick-cell service routine, service routine, IATFPSB.
IATFPQC, failed to get an index, because the
51 The writer FSA read-ahead task, IATFPRA,
first free index was incorrect.
could not initialize for spool access using the
34 The writer FSA quick-cell service routine, block spooler.
IATFPQC, failed to get a buffer, because the
52 While reading data from spool, the writer FSA
first free buffer was incorrect.
read-ahead task, IATFPRA, received an error
35 The writer FSA quick-cell service routine, return from the block spooler routine; the error
IATFPQC, failed to free an index, because the return indicated that the parameter list was
index passed in the request was incorrect. incorrect.
36 The writer FSA quick-cell service routine, 53 While reading data from spool, the writer FSA
IATFPQC, failed to free a buffer, because the read-ahead task, IATFPRA, received an error
buffer passed in the request was incorrect. return from the block spooler routine; the error
return indicated that the spool address was
3D While reading a data set checkpoint record, the incorrect.
writer FSA GETDS routine, IATFPGD, received
an error return from the block spooler routine; 54 While reading data from spool, the writer FSA
the error return indicated that the parameter list read-ahead task, IATFPRA, received an error
was incorrect. return from the block spooler routine; the error
return indicated that an error occurred during a
3E While reading a data set checkpoint record, the cross-address space move.
writer FSA GETDS routine, IATFPGD, received
an error return from the block spooler routine; 55 The writer FSA read-ahead task, IATFPRA,
the error return indicated that the spool found an error in the format of a spool data
address was incorrect. buffer.
3F While reading a data set checkpoint record, the 56 The writer FSA read-ahead task, IATFPRA,
writer FSA GETDS routine, IATFPGD, received found an error in the format of a JESNEWS
an error return from the block spooler routine; data buffer.
the error return indicated that an error occurred
5B The writer FSA checkpoint writer task,
during a cross-address space move.
IATFPCW, could not initialize for spool access
47 While reading the scheduler work block (SWB), using the block spooler.
the writer FSA SWB processing service routine,
5C While writing a data set checkpoint record, the
IATFPSB, received an error return from the
writer FSA checkpoint writer task, IATFPCW,
block spooler routine; the error return indicated
received an error return from the block spooler
that the parameter list was incorrect.
routine; the error return indicated that the
48 While reading the scheduler work block (SWB), parameter list was incorrect.
the writer FSA SWB processing service routine,
5D While writing a data set checkpoint record, the
IATFPSB, received an error return from the
writer FSA checkpoint writer task, IATFPCW,
block spooler routine; the error return indicated
received an error return from the block spooler
that the spool address was incorrect.
routine; the error return indicated that the spool
49 While reading the scheduler work block (SWB), address was incorrect.
the writer FSA SWB processing service routine,
5E While writing a data set checkpoint record, the
IATFPSB, received an error return from the
writer FSA checkpoint writer task, IATFPCW,
320 z/OS V1R10.0 MVS System Codes
E00 • E06
received an error return from the block spooler
E03
routine; the error return indicated that an error
occurred during a cross-address space move. Explanation: A task tried to end normally by issuing a
RETURN macro or by branching to the return address
System action: The system abnormally ends the task.
in register 14. The task was not ready to end
Most failures in the read-ahead task, IATFPRA, and in processing because the task issued one of the following
the checkpoint writer task, IATFPCW, cause processing macros with a SET,MC (must complete) parameter:
of the current data set to be ended. The task is v STATUS
reinstated to resume processing with the next data set. v RESERVE
v ENQ
All other failures result in the FSA or of the entire FSS
address space ending. The task did not issue an accompanying STATUS
RESET,MC or DEQ RESET,MC macro to reset the
Operator response: Notify the system programmer. If step-must-complete status before attempting to end.
the FSS address space was ended and if this is not a
recurring error, issue the appropriate command to System action: The system abnormally ends the task.
restart the FSS.
Operator response: If the application or system
System programmer response: Format the SVC programmer asks for an SVC dump, set the following
dump with the interactive problem control system SLIP trap:
(IPCS). SLIP SET,COMP=E03,ACTION=SVCD,END
If the problem occurs in JES3, save the hardcopy log. Application Programmer Response: Do the
Source: JES3 following:
1. If a dump is not produced with the abend, ask the
operator to set a SLIP trap to obtain an SVC dump.
E00
2. From the dump, identify the abnormally ended
Explanation: During processing of an I/O request, module.
execute channel program (EXCP) processing 3. If the module is an installation-provided program,
encountered one of the following errors: ensure that each ENQ, RESERVE, or STATUS
v A program check or machine check occurred while macro with the SET,MC parameter is paired with a
the input/output supervisor (IOS) interruption DEQ or STATUS macro with the RESET,MC
response block (IRB) analysis modules were parameter.
processing or IOS POST was processing.
System programmer response: If the module is an
v The operator pressed the RESTART key while the I/O IBM module, search problem reporting data bases for a
request was being processed. fix for the problem. If no fix exists, contact the
v A program check or machine check occurred while a component group for the module at the IBM Support
nonresident error recovery program (ERP) was Center. Provide problem data collected.
processing or the ERP loader module was
processing. Source: Recovery termination manager (RTM)
System action: The system abnormally ends the
current task. The system writes a logrec data set error E06
record. The previous error record in the logrec data Explanation: An error occurred during contents
should indicate the cause of the abend. The system supervisor processing of an z/OS UNIX System
does not provide the EXCP debugging area (XDBA). Services (z/OS UNIX) exec, fork, loadhfs, or deletehfs
System programmer response: Look at the function.
messages in the logrec data set error record for the A hexadecimal reason code in register 15 describes the
probable cause of the error. If the reason for the error error. The reason codes are in the form xx yy, where xx
cannot be determined or if an IBM-provided program is represents the 1-byte function ID of the function that
causing the error, look at the messages in the job log caused the error, and yy represents the reason code for
for more information. Search problem reporting data the error. The possible values for the function code xx
bases for a fix for the problem. If no fix exists, contact are:
the IBM Support Center. Provide the logrec data set
error record, the JCL, the program listing, and the Code Explanation
assembly listing for the job. 00 An exec or fork function failed.
Source: Execute channel program (EXCP) 01 A loadhfs function failed.
02 A deletehfs function failed.
Chapter 2. System Completion Codes 321
E13 • E1A
The reason code value yy can have one of the following Code Response
values:
00 No system dump is taken and no LOGREC
Code Explanation record is written.
00 An unauthorized program requested contents 04-1C Contact the system programmer.
supervisor processing for the z/OS UNIX exec,
20 Refer to accompanying message CSV034I.
loadhfs, or deletehfs function.
24 Contact the system programmer.
04-1C An internal error occurred while processing the
exec, loadhfs, or deletehfs z/OS UNIX 30 Correct the program.
callable service.
34 Correct the pathname to refer to an executable
20 A PGMF FIND was not successful. Message file.
CSV034I accompanies this abend.
38 Correct the pathname to refer to an executable
24 A PGMF FIND for the requested module file.
program checked or ended abnormally.
Message CSV036I accompanies this abend. 3C Correct the pathname to refer to an executable
file.
2C An unexpected error occurred during contents
supervisor processing for an z/OS UNIX 40 Refer to accompanying message CSV034I.
callable service. 44 Contact the system programmer.
30 The requested pathname resulted in a fetch of 50-54 Contact the system programmer.
a loadable-only file. Message CSV039I
accompanies this abend. The requested System programmer response: Some of the reason
pathname references a loadable-only file, codes may indicate that there is a problem with the file
which is not valid as the target of an exec system or the underlying PGMF mechanism. For reason
callable service. codes other than 00, a system dump is normally taken.
Provide the dump to the IBM Support Center.
34 The requested pathname resulted in a fetch of
a nonexecutable file. Message CSV038I For reason codes 04 through 18 and 50 through 54, an
accompanies this abend. internal error occurred. Report the error to the IBM
Support Center.
38 The requested pathname resulted in a fetch of
a nonexecutable file. The module was marked Source: Contents Supervision
as being an overlay module. This should not
occur for an exec executable file. Message E13
CSV038I accompanies this abend.
Explanation: The error occurred during processing of
3C The requested pathname resulted in a fetch of an OPEN macro instruction for a graphic data control
a nonexecutable file. Message CSV038I block. This system completion code is accompanied by
accompanies this abend. message IEC159I. Refer to the explanation of message
40 An internal error occurred while attempting to IEC159I for complete information about the task that
fetch the executable file. was ended and for an explanation of the return code (rc
in the message text) in register 15.
44 A PGMF FIND for the requested module
program checked or ended abnormally. Application Programmer Response: Respond as
Message CSV036I accompanies this abend. indicated for message IEC159I.
48 The callable service was unable to establish System programmer response: If the error recurs
ESTAE recovery. and the program is not in error, look at the messages in
the job log for more information. Search problem
4C The caller had more than one RB on its TCB reporting data bases for a fix for the problem. If no fix
chain. exists, contact the IBM Support Center. Provide the
50-54 These reason codes indicate an internal error source program listing for the job and all printed output
occurred during fork callable service and output data sets related to the problem.
processing. Source: DFSMSdfp
58 An internal error occurred while attempting to
remove a program from storage. E1A
System action: The system abnormally ends the Explanation: The catalog address space (CAS)
program issuing the callable service. allocate task ended abnormally because the allocate
Application Programmer Response: task exceeded the allotted time for processing. The task
322 z/OS V1R10.0 MVS System Codes
E23 • E85
may have been waiting for some system resource that Source: DFSMSdfp
is permanently unavailable.
System action: The system attaches a new task to E82
restore the allocate function.
Explanation: SVC 130 (RACROUTE
Source: DFSMSdfp REQUEST=AUTH macro) was invoked; however, SVC
130 is inactive because RACF is not properly installed
on the system.
E23
System action: The task is terminated.
Explanation: An error occurred during processing of a
write to operator with reply (WTOR) macro. The macro System programmer response: If you have installed
specified one of the following incorrectly: RACF on your system, make sure that RACF is properly
v The address of the event control block (ECB) enabled. Check the IFAPRDxx member pointed to by
v The address of the request block (RB) in the ECB the PROD= statement in the IEASYSxx parmlib member
v The address of the virtual storage area that was used when the system was initialized. For
more information, see z/OS Security Server RACF
Application Programmer Response: Correct the
System Programmer’s Guide.
macro or program errors that incorrectly modified the
macro expansion. Ensure that the ECB address is a If you have not installed RACF on your system, this
fullword on a fullword boundary. Recompile the program abend could be issued when a data set has the RACF
and run the job step again. indicator bit on. This could occur if the data set came
from a system with RACF installed.
| Source: Console services
E83
E2D
Explanation: SVC 131 (RACROUTE
Explanation: A program requested an overlay. In
REQUEST=VERIFY macro) was invoked; however,
answer to the request, the overlay supervisor was using
SVC 131 is inactive because RACF is not properly
program fetch to load a program segment from the
installed on the system.
library. Fetch found an incorrect address.
System action: The task is terminated.
Note: Overlay programs run only in 24-bit addressing
System programmer response: If you have installed
mode, not in 31-bit addressing mode.
RACF on your system, make sure that RACF is properly
System action: The system abnormally ends the enabled. Check the IFAPRDxx member pointed to by
program that requested the overlay. The system writes the PROD= statement in the IEASYSxx parmlib member
an ABEND dump, if a dump DD statement is provided. that was used when the system was initialized. For
more information, see z/OS Security Server RACF
Application Programmer Response: Link edit and System Programmer’s Guide.
run the program again.
Source: Overlay supervisor E84
Explanation: SVC 132 (RACROUTE REQUEST=LIST
E37 macro) was invoked; however, SVC 132 is inactive
Explanation: The error occurred when an output because RACF is not properly installed on the system.
operation was requested. The data set was on a direct System action: The task is terminated.
access or magnetic tape device. This system
completion code is accompanied by message IEC032I. System programmer response: If you have installed
Refer to the explanation of message IEC032I for RACF on your system, make sure that RACF is properly
complete information about the task that was ended and enabled. Check the IFAPRDxx member pointed to by
for an explanation of the return code (rc in the message the PROD= statement in the IEASYSxx parmlib member
text) in register 15. that was used when the system was initialized. For
more information, see z/OS Security Server RACF
Application Programmer Response: Respond as System Programmer’s Guide.
indicated for message IEC032I.
System programmer response: If the error recurs E85
and the program is not in error, look at the messages in
the job log for more information. Search problem Explanation: SVC 133 (RACROUTE
reporting data bases for a fix for the problem. If no fix REQUEST=DEFINE macro) was invoked; however,
exists, contact the IBM Support Center. Provide the JCL SVC 133 is inactive because RACF is not properly
and the program listing for the job. installed on the system.
Chapter 2. System Completion Codes 323
EC3 • EC6
System action: The task is terminated. other problem determination needed to find and fix
either customer or IBM programming defects.
System programmer response: If you have installed
RACF on your system, make sure that RACF is properly
enabled. Check the IFAPRDxx member pointed to by EC5
the PROD= statement in the IEASYSxx parmlib member
Explanation: JES common coupling services
that was used when the system was initialized. For
(JESXCF) detected an unrecoverable error that causes
more information, see z/OS Security Server RACF
the JES member to terminate abnormally. The
System Programmer’s Guide.
hexadecimal reason code returned in register 0
describes the error:
EC3
Code Explanation
Explanation: This abend code is used by WebSphere
00 An error was detected in the JESXCF recovery
Application Server on z/OS. This abend code is used by
environment.
WebSphere Application Server on z/OS. See
WebSphere Application Server on z/OS for further System action: The system abnormally terminates the
information. JES member.
Operator response: Notify your system programmer.
EC4
System programmer response: Find the associated
Explanation: NetView issues abend EC4 using JESXCF abend and the associated JESXCF dump. Use
CALLRTM in order to terminate NetView tasks in error these to diagnose the error. If the problem is due to a
situations. NetView uses abend EC4 during the NetView coding error, search the problem reporting data bases
commands: for a fix to the problem. Fix the problem and restart
JES. If a fix does not exist, contact the IBM support
STOP FORCE
center with the return and reason codes and the dumps
produced by the error.
To cause a NetView task that will not respond
For additional information on dumping JES and JESXCF
to other signals to abend and recover or
address spaces, as well as restarting the JESXCF
terminate.
address space, see z/OS MVS Programming: JES
CLOSE IMMED Common Coupling Services.
Source: JES common coupling services (JESXCF)
To cause a NetView task to shut down after
approximately 1 minute if the task is still active
EC6
after the CLOSE IMMED is processed.
Explanation: An error occurred during processing of a
System action: Abend EC4 means that NetView
callable service to z/OS UNIX System Services (z/OS
decided the only way to stop the task was to intervene
UNIX). The callable service may have been originally
using a system abend.
issued as a function in a program or as a shell
System programmer response: If you are using the command.
STOP FORCE command or the CLOSE IMMED
A hexadecimal reason code in register 15 describes the
command to recover from errors, notify your system
error. The reason codes are in the form xxxx yyyy,
programmer to determine whether customer or IBM
where xxxx represents internal information (not
programming is failing. The NetView product provides
described here) and yyyy represents external
the STOP FORCE and CLOSE IMMED commands as a
information shown below.
means of recovering from user or IBM product errors
until the cause can be remedied. Using STOP FORCE Only external reason codes are documented. There are
or CLOSE IMMED as a normal operations practice is many other possible reason codes for internal errors.
otherwise a misuse of the product. The internal errors should be reported to IBM.
If you observe a high number of abend EC4 reports: Code Explanation
v Advise your operators that excessive use of error 000D A failing physical file system requested that the
recovery commands can cause storage loss and z/OS UNIX kernel be ended.
affect system performance. Ask them to use the
non-abend STOP TASK and CLOSE STOP before 0016 An ESTAE macro returned an error return
resorting to STOP FORCE or CLOSE IMMED. code.
v If tasks will not stop when using STOP TASK, or 0025 An unsupported entry code was specified to a
NetView does not close down when using CLOSE file system service.
STOP, call NetView Service for advise on dumps or
324 z/OS V1R10.0 MVS System Codes
EC6
0026 While building osi_thread support a failure was 0445 Invalid entry to PC.
reported by the set_dub_default service.
0446 This thread is not known.
0027 The Dspserv to create an address space failed.
0447 Bad function request code.
0029 The z/OS UNIX couple dataset is not
0481 Bad Entry code to module.
accessible.
0482 Not an z/OS UNIX thread.
002A The z/OS UNIX couple dataset data not as
expected. 0483 Too many events requested.
002B The z/OS UNIX address space could not be 0484 Mask contains an undefined event.
created.
0485 No events in list.
002C The z/OS UNIX address space could not be
initialized. 0486 Invalid KSER address.
002E The request was made by a process that was 0488 Invalid combination of events in list.
not properly dubbed. 0489 The task is not properly setup to wait.
0030 Issuing Syscalls from SRBs not allowed. 048A Bad Return code from ESTAE macro.
0031 The syscall requested is not supported in SRB 048B The input ECB list was longer than 1013
mode. entries.
0037 Specified port in use. 048C Kernel wait and User Kernel Wait not
003F A large open count is being re-established interchangeable.
between a shared file system client and server, 048D Unable to obtain latch for KSER storage pool.
and may result in delays.
048E Failed to release latch for KSER storage pool.
| 0040 A shared object is in an unknown state, and
| the object is not usable. 048F Set Ktimer failed.
| 0041 The OAPB address specified in register 2 for 0490 Hash table count is invalid.
| an SRB SYSCALL was not zero and did not 04C1 Bad Entry code to module.
| point to a valid OAPB.
04C2 Bad RC from DSPSERV Create.
0042 An error occurred on a file mapped by mmap().
04C3 Bad RC from ALESERV Add.
0043 One of the following conditions:
04C4 Bad RC from ALESERV Extract.
v An error occurred during opening or reading
the /etc/inittab file. 04C5 Bad RC from ALESERV Delete.
v An error occurred during opening the STDIN 04C6 Bad RC from DSPSERV Delete.
or STDOUT file.
v A /etc/inittab file entry could not be spawned. 04C7 Bad RC from TCBTOKEN macro.
0044 An error occurred trying to send an I/O 04C8 Bad RC from LXRES macro.
Complete Notification to the AIO#MsgQ 04C9 Bad RC from AXSET macro.
message queue.
04CA Bad RC from ETCRE macro.
0045 A syscall detected that the USTA control block
might have been corrupted. 04CB Bad RC from ETCON macro.
0401 Bad Entry code to module. 04CC Bad RC from ESTAE macro.
0402 Unexpected error. 04CD Bad RC from VSM Locate macro.
0403 Set Ktimer (BPXXKTIM) failed. 04CE Bad RC from LOAD or NUCLKUP macros.
0405 Bad input parameters. 04CF Bad RC from ETDES macro.
0407 Validity checks of Kernel Blocks failed. 04D0 Bad Parms in ParmLib.
0421 Bad Entry code to module. 04D1 Bad RC from CSVQUERY macro.
0441 Invalid entry into the syscall layer. 04D2 Bad RC from Pgser macro.
0442 Environmental Error. 04D3 Bad RC from Axres macro.
0444 Invoking PC Number is not recognized. 04D4 Bad RC from Asext macro.
Chapter 2. System Completion Codes 325
EC6
04D5 Bad RC from BPXFSIT during sysplex 0555 No free Ppra slots while PpraActiveCount
initialization. lifetime MaxProcSys.
04D6 Bad RC from Lxfre macro. 0556 Create Latch failure during process
initialization.
04D7 A colony AS ended due to Mother Thread
termination. 0557 PID not found in PPRA.
04D8 IXCJOIN of Sysplex failed. 0558 Obtain Latch failure during process
initialization.
04D9 XCF IXCQUERY operation failed.
0559 PprtLatchedToken only with its PprtPprp, R4.
04DA BPXXQHIT queue manager processing failed.
055C Invokers BPXXJPID area date does not match.
04DB Sysplex initialization failed.
055D Invokers BPXXJPID NEXT holds other latch,
04DC XCF IXCMSGI Message-In macro processing
R4.
failed.
055E Request for latch held by ancestor, R4, R5.
04DD BPXOPIT failed to ATTACH command
processor BPXOTASK. 055F Invoker of BPXXJPID holds too many latches,
R4.
0501 Bad Entry code to module.
0560 Invalid Function # passed to internal
0503 OSAB already exists for the new task.
MvsIptAffinity.
0506 _Exit Abend Reason Code.
0561 SLTB has been clobbered, contents
0507 Bad RC from StorMan Create. inconsistent.
0508 Edsa does not exist in calling process. 0581 Bad RC from RESMGR macro.
0509 Load of program failed, program not found. 0582 Bad Entry code to module.
050A Load macro failed with unexpected abend 0583 Critical control blocks have been damaged.
code.
0584 Bad return code from Estae.
050D Invalid Function # passed to BPXPKEXC.
0585 EOM recovery time out.
050E Bad RC from Attach Macro.
0586 Tcb/Ecb table is full.
050F Bad RC from call to BPXPTCAC.
0587 Bad return code from ATTACH.
0510 BPXXNXMS(FREE) not issued to free
05C0 Bad Entry code to module.
allocated resources.
05C1 Storage Manager Latch Set already exists in
0511 Required response not issued to
this AS.
BPXXNXMS(SYNC) request.
05C2 Storage Manager Latch Create out of storage.
0512 Response not allowed for
BPXXNXMS(ASYNC) request. 05C3 Bad RC from Isglcrt service.
0515 The L16J in BPXJCPRC failed unexpectedly. 05C4 Cell storage addr required.
0516 SAF failure during ACEE create/delete in 05C5 Bad RC from Aleserv macro.
BPXMRCSI.
05C6 Cannot do DSPSERV RELEASE for this cell
0517 Required BPXXNXMS(DEFER) not issued pool.
before DEFERRESP or DEFERFREE.
05C7 Bad RC from Csrpbld service.
0518 Current buffer is also on the free chain.
05C8 Bad RC from Csrpexp service.
0519 Resource is already freed.
05C9 Cell pool token invalid.
054F Current buffer is also on the free chain.
05CA Cell address is invalid.
0550 PPRT, KSER or PPRP ID overlayed.
05CB Bad RC from Csrpget service.
0551 PPRA has been clobbered, contents
05CC Bad RC from Csrpfre service.
inconsistent.
05CD Bad RC from Csrpqpl service.
0553 Failure occurred during vdac task initialization.
05CE Bad RC from Csrpcon service.
0554 Unexpected failure of IVTCSM invocation.
05CF Bad RC from Csrpact service.
326 z/OS V1R10.0 MVS System Codes
EC6
05D0 A Storage Manager Control Block stack is 0648 The Audit Trail EVENT is invalid.
invalid.
0649 A Count discrepancy was found in the PTY
05D1 A Storage Manager Control Block stack Buffers.
overflowed.
064A A Count discrepancy was found in the PTY
05D2 A Master Cell Pool is out of extent storage Buffers.
cells.
064B A Count discrepancy was found in the PTY
05D3 A Master Cell Pool is out of control block cells. Buffers.
05D4 A Cell Pool for stack storage is out of cells. 064C Bad RC from ESTAE macro.
05D5 Expand stack invoked with an invalid cell pool 064D Internal logic error in Pty support.
ID.
064E Invalid Recovery Code during EOT/EOM
05D6 Unexpected failure of IUTL invocation. processing.
05D7 Bad return code from Estae. 0650 Invalid select()criteria.
05D8 Bad RC from Csrpqex service. 0651 Invalid select()function.
05D9 Bad RC from Csrpdac service. 0652 Invalid value in SBCS scan TRT table.
05DA Bad RC from Csrpdis service. 0653 Invalid value in DBCS scan TRT table.
05DB Length of requested storage exceeds the 065B Unexpected return code from BPXXKTIM Set.
maximum.
065C Unexpected return code from BPXXKTIM
05DC Invalid data space group ID is passed. Cancel.
05DD Invalid data space alet is passed. 0680 Bad Entry code to module.
05DE Invalid data space Stoken is passed. 0685 Unexpected error in Load 16 and Jump.
05DF Unexpected error from BPXSMDSP data space 0686 Ptrace request code in Ptrb is invalid.
manager.
0688 SVCUPDATE for ptrace SVC 144 failed.
0601 Sleep or Alarm had a system failure.
0689 Bad caller id to module.
0603 An error occurred while closing a file.
0700 Bad Entry code to module.
0605 Process could not notify parent of status
0703 Bad RC from Attach Macro.
change.
0704 The File System that owns the root was not
0606 Signal Code Failed to Obtain Local Lock.
started.
0607 Signal generation failed.
0705 Bad return from storage manager during
060A Bad Return Code from Save Signal initialization.
Environment Service.
0706 Bad return from PFS that owns root file
060B Process could not be stopped. system.
060C Unexpected error in Load 16 and Jump from 0707 No ROOT statement was specified in
OESIR. SYS1.PARMLIB.
060D The OESIR was passed an invalid PPSD. 0708 Invalid vnode address returned on vn_create
by PFS.
060E Ppsqs exceeded the space available on
InitPpsqChunck. 0709 Queue Manager failed to Initialize.
0641 No Storage to create PTY Latchset. 070A Queue Manager failed to Connect.
0642 Duplicate Latchset Name detected. 070B An invalid Pnode was passed.
0643 Unexpected Return Code from Latch Manager. 070C No KSER for Dispatchable Unit to be waited.
0644 Storage not obtained for input queue. 070D No Pnwt was found.
0645 Storage not obtained for output queue. 070E The Pipe GFS was not found.
0646 The PTY device state is invalid or unexpected. 070F The GRS Latch Manager request failed.
0647 The PTY Device Driver input event is invalid. 0710 File System latch service error during Umask
request.
Chapter 2. System Completion Codes 327
EC6
0711 Umask input error. Invalid bits set on in Mode. 0734 Could not create a msgq for colony thread
support.
0714 Received invalid ALET as a parameter.
0735 No saved CDSI token for request which
0715 Bad command code passed to module.
requires token.
0716 Bad RC from file/directory close service.
0736 Saved CDSI token valid from previous request.
0717 Read/Write invoked with an invalid syscall
0737 IXCXCDSI return and reason code indicate
request.
code error.
0718 The Vnode received is invalid.
0738 Internal structure of CDS inconsistent.
0719 Pointer to next filedes table page is 0.
0739 Socket is not in a valid state.
071A The requested function requires a parent
073A Error on read or write of CDS.
directory vnode.
0781 Byte Range Lock Manager cannot be
071B The length passed is negative - not valid.
initialized.
071C Attempt made to stop a colony PFS that was
0782 Byte Range Lock Manager cannot be
not started.
terminated.
071D File System module is overlaying a latch
0783 Unexpected error occurred while unlocking a
handle.
byte range.
071E Invalid Vnode address was referenced.
0784 Unexpected error occurred while registering a
071F BPXFRLOC caller did not have FRLOC on its process.
BPXXFENT.
0785 Unexpected error occurred while registering an
0720 BPXFTCLN detected a bad vnode cache object.
queue.
0786 The Byte Range Lock Mgr detected an internal
0721 Module Exit while holding Vnode Latches. error.
0722 BPXXCALL EXCL when held latches were 0787 Error occurred while trying to get lock
locked SHR. information.
0723 PFS Recovery Token Stack overflow. See 0788 Unexpected error occurred while unregistering
BPXZFSRB. process.
0724 Invalid Snode or socket detected. 0789 Unexpected error occurred while unregistering
object.
0725 Error in socket read/write queue.
078A Unexpected error occurred while setting a lock.
0726 Error in setting up interface to TCP/IP.
078B Unexpected error occurred while calling
0727 Invalid control block address found. MarkBroken.
0729 Bad RC from PGSER Fix or Free. 078C PprtFd field already used to hold a Vde ptr.
072A Current system is already the owner. 078D Vnode Vde count is about to go negative.
072B Different vnod returned after vget or mount. 078E Oapb Chain has not been cleaned up properly.
072D CSVDYNEX in error attempting to call the 078F IEAVLSUP query service failed.
pre-process initialization exits.
0790 IEAVLSUP update service failed.
072E CSVDYNEX in error attempting to call the
post-process initialization. 0791 Unix System Services has terminated
unexpectedly.
072F CSVDYNEX in error attempting to call the
image initialization exits (during exec). 07E0 Level mismatch between kernel and TFS.
0730 Colony AS was canceled when the z/OS UNIX 07E1 Bad TFS mount table for filesys token.
AS was canceled.
07E2 Attempt to add a file to a non-directory.
0731 Invalid retval from dd_configure.
07E3 Bad chain pointer, data block not in file.
0732 CSFS DDWT detected invalid DDWE.
07E4 Bad chain pointer, freeing block not in file.
0733 On PFS restart, a request was made to
07E5 Allocating an already allocated block.
allocate a restartbyte beyond the end of the
Cabc. 07E6 Freeing an already freed block.
328 z/OS V1R10.0 MVS System Codes
EC6
07E7 Attempt to free the superblock. 8002 z/OS UNIX is not running.
07E8 Attempt to lookup in a non-directory. 8004 The kernel has been terminated and restarted.
Connection to the old kernel is no longer valid.
07E9 Bad length for a WTO.
8006 The current process is being ended.
0800 Reg2 -> offending parameter in BPXXQHIT
(see QhitT). 800C An error occurred because of a duplicate file
system name.
0801 Unexpected return code from BPXXQHIT
macro. 8010 The caller has an incorrect PSW key.
0802 Incorrect UDP-plus flag combination. 8011 The caller is running in AR mode.
0803 Structure of QHIT queue damaged. 8012 The caller has an incorrect signal data area
(PPSD).
0804 Channel program check occurred.
8013 A ptrace router was invoked while the calling
0805 Counter goes negative.
program was not being traced using ptrace.
0806 The buffer length passed is zero or incorrect.
8014 A ptrace router was invoked in an incorrect
0807 Unexpected buffer sequence number detected. thread.
0808 BPXUIIOC processing failed. 8015 A ptrace router was invoked in an authorized
process.
0809 BPXXKSOC processing failed.
8017 A sleep callable service was invoked while
080A Master socket not created. z/OS UNIX was not running.
080B Invalid value to an internal counter. 8018 An invoker of a callable service had an
080C Unexpected ERRNO from BPXUTBIN. incorrect PSW key.
080D QnodSeqNum mismatch found during accept. 8022 A ptrace router was invoked in an exited
thread.
080E Unexpected TCP state detected.
8024 A ptrace router was invoked in a process with
080F Attempt to DEQ UTBQEs on empty backlog a controlled environment.
queue.
8028 The local INET failed to initialize.
0810 Requested wait time is either too long or too
short. 8033 Duplicate NETWORK parmlib statements with
DOMAINNAME(AF_INET) and
0811 Timer processing caught its tail in a circular TYPE(OESTACK) not supported.
array.
8034 The specified Network type is not supported
0812 TCP Readable BFQE chain is corrupted. under DOMAINNAME(AF_INET).
0813 TCP Send BFQE chain is corrupted. 8035 TCP/IP BASE feature is required but not
0814 The transport provider unexpectedly ran out of enabled.
latching resources for TCP sockets. 8038 The sysplex server for the byte range lock
0815 The buffer chain has been corrupted. manager has terminated.
0816 Bad return code from BPXXFAST NEWODB. 8039 The PARM= value is incorrect in the Colony
proc.
0817 Waitlist post failure unexpectedly.
803A The specified TCPIP stack was not configured
0818 tcp_drop() invalidly invoked. under Cinet.
0819 UTTC2 invoked with 0 Bfqe and FIN not 8487 The task has already been pseudo-dubbed.
received.
8502 Required VSMLIST absent.
081A Unexpected return code from ?IWMELEAV
macro. 8504 Bad RC from Exec Kernel syscall.
081B Osenv cell is no longer valid for use. 8514 An unexpected error occured in BPXJCSE
while changing the address space/process
081C A new ACEE was created when only a use identity for a socket.
count update on an existing one is expected.
8604 Signal processing detected kernel shutdown.
081D Invalid VFS or no VFS found when expected.
864F Cannot get the Pty Latch in device driver.
081E Invalid Xnod returned to client from server.
Chapter 2. System Completion Codes 329
EC6
865A Cannot get the Rty Latch in device driver. C021 The status specified on the _exit callable
service is not valid.
8681 Sigaction callable service from Ptrace failed.
C023 The callable service was rejected because the
8682 Kill callable service from Ptrace failed.
requesting thread is in termination.
8683 Sigprocmask callable service from Ptrace
C02F Caller is not authorized for this callable service.
failed.
C032 Exec Phase 2 failed because a sticky program
8684 Ptrace initialization of fork child failed.
was not found in the MVS library search order.
8687 Ptrace kernel function failed.
C036 Exec Phase 2 failed because the execution of
868A Quiesce callable service from Ptrace failed. a HFS executable was attempted from a
controlled environment.
8701 The LFS Mother Task did not initialize.
C443 Parameter Rules not present for the callable
8702 Bad RC from Estae Macro. service.
8712 Mask not changed. Security support not C448 Unexpected error in Load 16 and Jump.
installed.
C552 Proc init invoker not key 0 and not supervisor
8713 Security service error during Umask request. state.
8728 A file system latch could not be obtained during C55A Unauthorized caller to BPXPRTRM internal
term. callable service.
C001 The callable service is incorrect or is not FDxx Terminating signal with dump.
supported.
FDF1 Unauthorized Caller to Exec2 internal callable
C003 The callable service was not issued by a service.
program running under a task control block
(TCB). FDF2 Osab does not exist in calling process.
C005 Callable services cannot be nested. FDF3 Bad Return Code from RACF Exec Set Uid/Gid
Service.
C007 The callable service was issued in
cross-memory mode. FDF4 Caller not authorized (key 0 | supervisor) for
BPXMRKIN.
C008 The calling process cannot be dubbed.
FFxx Terminating signal with no dump.
C009 The parameter list contains an incorrect
number of parameters. FFF7 z/OS UNIX is not running and the caller does
not expect a return code.
C00A A parameter length is negative.
FFF8 z/OS UNIX is not running and the parameter
C00E An incorrect address was encountered when list is too long.
trying to move user parameter data.
FFFA Kernel termination or error with user in wait.
C00F There is insufficient storage to copy user
parameters. FFFE Normal end of Exec Phase 1, with multiple
TCB/RBs.
C019 The calling program was running in an
incorrect request block (RB) state. System action: The system abnormally ends the
program issuing the callable service.
C01A A security product is not installed.
Application Programmer Response:
C01B The user ID is not defined to the security
product. Code Response
C01C The user ID is in a group that does not have 000D The failing file system indicated that, should it
access to z/OS UNIX. fail, all of z/OS UNIX should be terminated
also.
C01D The user ID does not have access to z/OS
UNIX. 0016 Ptrace was invoked to process a ptraceable
event, but was unable to establish a recovery
C01E The user ID does not have a UID. environment. The probable cause is a shortage
C01F The user ID is in a group that has does not of system resources. Obtain more system
have a GID. resources or reduce the use of system
resources.
C020 An internal error is reported by the security
product. 0025 The entry code specified on the interface to a
330 z/OS V1R10.0 MVS System Codes
EC6
file system service is not within the range of 002E Contact your IBM Technical Support personnel.
codes supported by that interface. The request
0030 The calling process is either in termination or
is not processed.
has reached its limit on concurrent SRBs
0026 Ensure that the procedure for this colony has issuing z/OS UNIX callable service. If the
an entry in the security product’s started process is not in termination, reissue the
procedures table, and that it specifies a valid callable service.
userid.
0031 Either issue the callable service from task
0027 A possible reason for this failure is that the mode or use another callable service to
dataspace already exists. Verify that there are perform the function required.
no duplicate entrypoint names specified in the
0037 There may be a parameter specification error.
parmlib member.
Refer to message BPXF219I, which was
0029 Run the XCF couple dataset utility for TYPE issued along with this abend and follow the
BPXMCDS to create the z/OS UNIX couple instructions listed there. If the problem can not
dataset. Issue the SETXCF COUPLE operator be corrected, forward this dump to IBM
command to add the new TYPE=BPXMCDS Technical Support personnel.
couple data set.
003F Delays may be experienced in the shared file
0043 This abend is percolated to the /usr/sbin/init system environment on multiple systems due
process so that /usr/sbin/init ends abnormally to this situation. If the condition appears to be
and causes the installation to see a failure for preventing systems from completing
the ETCINIT job. This is an unexpected type of initialization, it may be necessary to IPL this
error that can only occur for a privileged caller system to relieve the contention.
during system initialization. You can request a
0401-081C
system dump by the kernel to capture the
See your IBM service representative.
environment of the failure. This dump also
allows immediate debugging of the problem 8002 If z/OS UNIX has not been started, request the
without requiring a recreate. operator to issue the command to start z/OS
UNIX. Verify that z/OS UNIX completes its
0044
initialization before running the job again.
A BPX1AIO asynchronous I/O operation has
8004 z/OS UNIX has been stopped and restarted.
completed and the attempt to invoke msgsnd()
Either issue a call to BPX1MPC (MVS process
for the I/O Completion message has failed.
cleanup) to clean up the process before issuing
This usually means that the queue has filled
another callable service, or end the job.
up. The return and reason codes from this
attempt are recorded in the VRA section of the 8006 A new callable service cannot be issued until
dump and they are also loaded into registers 4 this termination is complete.
and 5 just before the abend is taken.
800C During file system initialization, an error
Only one dump will be taken for this type of occurred while processing a duplicate file
error but each failed attempt will abend and system name. Verify in the parmlib member
generate a logrec record for diagnostic used that there are no duplicate file system
purposes. If the message queue is full or the names in either the ROOT or any MOUNT
system limit on number of messages has been statements in the BPXPRMxx parmlib member.
reached, the application involved may be hung This includes a duplicate that may be caused
and not able to receive these messages so it by any names when DSNAMEs are specified.
may need to be recycled.
8010 Ptrace was invoked to process a ptraceable
002A Run the XCF couple dataset utility for TYPE event, but the PSW key was not valid. You can
BPXMCDS to create the z/OS UNIX couple only debug programs using ptrace that are run
dataset. Issue the SETXCF COUPLE operator with a PSW key of 8.
command to add the new TYPE=BPXMCDS
couple data set. 8011 Ptrace was invoked to process a ptraceable
event, but the ASC mode was not valid. Ptrace
002B Consult registers 2 and 3 at time of error in the only supports non-AR mode programs. Only
resulting dump to extract the ASCRE return debug programs with ptrace that are non-AR
and reason codes indicating the nature of the mode.
error and contact your IBM Technical Support
personnel. 8012 Ptrace was invoked to process a ptraceable
event, but the PPSD was not valid. Invoke
002C A cross memory post failure occurred during ptrace with a valid PPSD. The PPSD is
z/OS UNIX address space initialization. mapped by macro BPXYPPSD.
Contact your IBM Technical Support personnel.
Chapter 2. System Completion Codes 331
EC6
8013 Ptrace was invoked to process a ptraceable FILESYSTYPE OESTACK. Enable the feature
event, but the process ptrace was invoked in is in the IFAPRDxx member.
not currently being debugged using ptrace.
8038 The byte – range lock manager will be
Invoke ptrace to process ptraceable events
reactivated on another system. To protect the
only in processes being debugged by ptrace.
integrity of previously locked files, any process
8014 Ptrace was invoked to process a ptraceable that has been locking files must be terminated
event, but the thread ptrace was invoked under and will have to be restarted. If you do not
was not dubbed. Invoke ptrace to process wish to terminate the process that has done or
ptraceable events only under dubbed threads. is doing byte-range locking, then specify
preferred signal using pfsctl support.
8015 Ptrace was invoked to process a ptraceable
event, but the process was authorized. Do not 8039 In the Colony proc’s EXEC
attempt to debug programs using ptrace in an PGM=BPXVCLNY,PARM=TP(TPNAME)
authorized process. statement, the PARM= value has a syntax
error. It must be TP(TPNAME), where:
8017 Callable service sleep (BPX1SLP) was invoked
when z/OS UNIX became inactive. Have the v Everthing is in upper case EBCDIC.
system operator use the DISPLAY OMVS v "TP(" is contained in the first three
operator console command to determine the characters.
status of z/OS UNIX. The operator will v TPNAME is 1 to 8 characters, left justified
probably need to restart z/OS UNIX. and followed by a blank or ")".
8018 An z/OS UNIX callable service requires the Correct the value to conform the previously
invoker to have a PSW key that would allow described rules, and reply to the console
signals to be delivered. Change the application prompt to restart the Colony.
to invoke the z/OS UNIX callable service with a
PSW key that allows signals to be delivered. 803A In a Common Inet, Cinet, configuration, the
TCPIP stack name specified by the TPNAME
8022 Ptrace was invoked to process a ptraceable value in the Colony proc’s EXEC
event, but the thread ptrace was invoked under PGM=BPXVCLNY,PARM=TP(TPNAME)
has already exited. Do not invoke ptrace to statement was not configured under Cinet or is
process ptraceable events under exited not in upper case. Issue D OMVS,P from the
threads. console to see a list of the configured TCPIP
8024 Ptrace was invoked to process a ptraceable stacks, and check the spelling of the TPNAME
event, but the process had security product used. Check the BPXPRMxx parmlib member
controlled data sets open. Do not attempt to used for the names specified on the
debug programs using ptrace in this controlled SUBFILESYSTYPE NAME(TPNAME)
environment. statements. Correct the name and reply to the
console prompt to restart the Colony.
8028 Either the local INET was started without
bringing up the converged sockets file system, 8487-8728
or the converged sockets file system was See your IBM service representative.
started with only the local INET. Converged C001 Specify the correct callable service number and
sockets must be brought up with at least one resubmit the job.
other file system in order for the local INET to
be started. C003 Callable services can be issued only in TCB
mode. SRB mode is not supported.
8033 During file system initialization, an error
occurred while processing a duplicate C005 The system has detected a nested callable
NETWORK parmlib statement with service. For example:
DOMAINNAME(AF_INET) and The request block (RB) issues a callable
TYPE(OESTACK). Verify that only one such service. An interrupt request block (IRB), for
statement is specified in the BPXPRMxx example, in an STIMER exit, interrupts the RB
parmlib member. and attempts to issue another callable service.
8034 During file system initialization, an error The second callable service request is
occurred while processing a detected and flagged as an error.
SUBFILESYSTYPE parmlib statement with Correct the problem and resubmit the job.
DOMAINNAME(AF_INET). The specified
NAME is not accepted. Only NAME(OESTACK) C007 You cannot issue callable services in
can be specified. cross-memory mode.
8035 The TCP/IP BASE feature is required for Correct the problem and resubmit the job.
332 z/OS V1R10.0 MVS System Codes
EC6
C008 An error occurred while trying to make the C00E An error occurred while accessing the user
calling process an z/OS UNIX process. The parameter data. This can be caused by one of
system cannot set an error return code for the the following conditions:
caller because the caller does not expect a v The total number of parameters is incorrect
return code. A user ABDUMP has been for the callable service being issued.
requested. The cause of the error can be
v There is an error in one of the passed user
determined from either the ABDUMP or the
parameters causing z/OS UNIX to program
symptom dump. In the dump, register 2
check when the parameter is accessed.
contains the return code value and register 3
Check for the following conditions:
contains the reason code value of the failure.
Analyze the return code and reason code for – A parameter that points to non-existent
the cause of the problem. For detailed storage.
information, see z/OS UNIX System Services – A parameter that cannot be accessed in
Messages and Codes. the current user PSW key.
C009 An error was encountered that prevents the
running of the callable service. However, the Check for incorrect input parameters passed to
system cannot set an error return code for the the callable service.
caller because the input parameter list is C00F z/OS UNIX cannot obtain storage to make a
incorrectly specified. copy of the passed user parameters. This can
An ABDUMP or symptom dump has been be caused by one of the following conditions:
requested for the caller. In the dump, register 2 v The user region is filled up and the
contains the return code value and register 3 STORAGE request cannot be satisfied.
contains the reason code value of the original v There is an error in one of the passed user
failure. parameters, causing z/OS UNIX to issue a
Do both of the following: STORAGE request for a large amount of
storage that cannot be satisfied.
v Analyze the return code and reason code for
the cause of the original problem.
Check for incorrect input parameters passed to
v Verify that the high-order bit of the last the callable service. If the parameters are
parameter list entry is set on. Currently, a correct, consider increasing the user REGION
maximum of 25 parameter list entries is size.
supported for a callable service.
C019 Fix the application program. An z/OS UNIX
C00A Check for incorrect input parameters passed to callable service, which requires that it be
the callable service. One of the following invoked from a specific request block, was
conditions may have occurred: invoked from an incorrect request block. The
v The specified length of a variable-length problem may have been caused by a previous
parameter is negative. (This error can occur invocation of callable service mvssigsetup
only in programs issuing Assembler callable from a different request block. Because signals
services.) can be delivered only to the request block that
The length of a variable-length parameter issued mvssigsetup, z/OS UNIX cannot
cannot be negative. Callable services with perform the callable service.
variable-length parameters normally specify C01A A security access facility (for example, RACF)
them in pairs. The first of the pair specifies is required, but not installed in the system.
the length of the variable-length parameter
that comes next. C01B Define the user to the security product.
v The length of a fixed-length parameter C01C Define the current group as an z/OS UNIX
exceeds the allowable value. The maximum group.
length of any fixed-length parameter cannot
C01D Define the user as an z/OS UNIX user.
exceed 5000 bytes.
v The size of an input buffer to be used for C01E Define the user as an z/OS UNIX user.
holding an output variable length parameter C01F Define the current group as an z/OS UNIX
is specified as more than 5000 bytes. The group.
actual maximum size of the parameter is
much less. This error is reported for C020 The security access facility (for example,
performance reasons, to avoid inefficient RACF) has reported an error condition. A dump
usage of system resources, including should have already been taken by the security
storage and processing time. Specify a product. The cause of the error can be
smaller size for the input buffer. determined from the dump.
Chapter 2. System Completion Codes 333
EC7
A user ABDUMP has also been requested by FFF8 An error was encountered that prevents the
the z/OS UNIX kernel. The error return code running of the callable service. However, the
from the security product can be determined system cannot set an error return code for the
from either the ABDUMP or the symptom caller because the input parameter list is
dump. In the dump, register 4 contains the incorrectly specified. Verify that the high-order
error return code value and register 5 contains bit of the last parameter list entry is set on.
the error reason code value as reported by the Currently, a maximum of 25 parameter list
security product. Analyze the return code and entries is supported for a callable service.
reason code for the cause of the problem.
FFFA-FFFE
C021 Specify a valid exit status on the _exit call. See See your IBM service representative.
the BPXYWAST macro for a definition of the
Source: z/OS UNIX System Services (BPX)
accepted exit status values.
C023 The BPX1PTX callable service should be
EC7
issued to complete the termination of the
thread and to obtain a new thread to process. Explanation: Advanced Program-to-Program
Other z/OS UNIX callable services are not Communications (APPC) issues abend X'EC7' when it
supported while a thread is in this state. detects an unrecoverable error.
C02F Caller must be APF authorized to issue a A reason code further describes the error:
callable service.
Code Explanation
C032 Caller must insure that the program is either in
LPA, LINKLIST or the STEPLIB that the 000A1000 The activation of a logical unit failed
program is targeted to run with. because the VTAM application for the
logical unit is not APPC-capable.
C036 Caller must ensure that the program is marked Check the VTAM APPL statement for
as program controlled in the HFS, or place the the logical unit to ensure that you
program in the MVS library search order and specified APPC=YES.
define it to SAF program control.
System Action: The system also
C443-C55A issues abend X'EC7' with reason code
See your IBM service representative. X'000A0037', which can be ignored.
FDxx If xx is in the range of X'01' to X'7F', a signal 000100xx An internal error occurred.
was received causing termination and a dump
to be taken. This condition is usually the result System Action: The system
of an application programming exception. For a continues processing, but the
description of the signal represented by the requested APPC/MVS service fails.
value xx, check the appropriate appendix The system writes an SVC dump.
“BPXYSIGH - Signal Constants” or “Signal 00020001 A program called the Cleanup_AS
Defaults” in z/OS UNIX System Services service, but either did not provide the
Programming: Assembler Callable Services correct number of parameters or did
Reference. not follow VLIST conventions.
FDF1-FDF4 System Action: The system
See your IBM service representative. continues processing, but the
FFxx If xx is in the range of X'01'to X'7F', a signal requested APPC/MVS service fails.
was received causing termination. This 00020002 A program called the Cleanup_TP
condition is usually the result of a process service but either did not provide the
explicitly sending a terminating signal to either correct number of parameters or did
itself or to another process in the process not follow VLIST conventions.
group. For a description of the signal
represented by the value xx, check the System Action: The system
appropriate appendix “BPXYSIGH - Signal continues processing, but the
Constants” or “Signal Defaults” in z/OS UNIX requested APPC/MVS service fails.
System Services Programming: Assembler 00020003 - 00020006
Callable Services Reference. An internal error occurred.
FFF7 If z/OS UNIX has not been started, request the System Action: The system
operator to issue the START OMVS command. continues processing, but APPC/MVS
Verify that z/OS UNIX completes initialization initialization fails.
before running the job again.
00020007 A program called the unauthorized
334 z/OS V1R10.0 MVS System Codes
EC7
Cleanup_TP service but either did not System Action: The system
provide the correct number of continues processing, but the
parameters or did not follow VLIST requested APPC/MVS service fails.
conventions.
00050420 - 00050424
System Action: The system A system error occurred during
continues processing, but the transaction program (TP) profile
requested APPC/MVS service fails. processing.
00020008 A program issued a version of the System Action: The system does not
Cleanup_Address_Space service that use the TP profile.
is not valid on the release of MVS
00050800 - 00050822
installed on the system.
An internal error occurred during TP
System Action: The system profile or side information processing.
continues processing, but the
System Action: The system
requested APPC/MVS service fails.
continues processing, but the
00020009 A program called a version of the requested APPC/MVS service fails.
unauthorized Cleanup_TP service that
00050200 An internal error occurred during
is not valid on the release of MVS
APPC initialization
installed on the system.
System Action: The system
System Action: The system
continues processing, but APPC/MVS
continues processing, but the
initialization fails.
requested APPC/MVS service fails.
00050602 - 00050657
0002000A A program called the ATBCUC1
An internal error occurred during TP
service, which is not valid on the
profile or side information processing.
release of MVS installed on the
system. 00060001 - 00060004
An internal error occurred.
System Action: The system
continues processing, but the System Action: The system
requested APPC/MVS service fails. abnormally ends APPC. If the restart
criteria are met, APPC restarts in a
0002000B An abend occurred when the system
new address space.
tried to access the input parameters
for a callable service. The caller of the 00060005 - 00060009
program does not have read or write An internal error occurred.
access to the parameters.
System Action: APPC continues
00030001 An internal error occurred while the processing, but inbound processing
DISPLAY APPC command processor could be affected.
was trying to extract data for display.
0006000A An internal error occurred.
System Action: The system ends the
DISPLAY command but APPC System Action: The system
continues processing. abnormally ends APPC. If the restart
criteria are met, APPC restarts in a
00050001 A system error occurred during new address space.
conversion of a transaction program
(TP) profile. 0006000B An internal error occurred.
System Action: The system does not System Action: APPC continues
use the TP profile. processing, but inbound processing
could be affected.
00050002 An internal error occurred.
0006000C - 0006000E
System Action: The system does not An internal error occurred.
use the TP profile.
System Action: The system
00050300 - 000503E0 abnormally ends APPC. If the restart
An internal error occurred during criteria are met, APPC restarts in a
VSAM processing. new address space.
0006000F - 00060014
An internal error occurred.
Chapter 2. System Completion Codes 335
EC7
System Action: APPC continues 00070008 An illegal state transition was
processing, but inbound processing requested for APPC.
could be affected.
System Action: The system sends
00070001 - 00070002 messages to the operator console to
An internal error occurred. show APPC’s status following the
abend. If restart conditions are met,
System Action: The system sends
APPC will restart itself in another
messages to the operator console to
address space.
show APPC’s status following the
abend. If restart conditions are met, 00070009 APPC was unable to obtain required
APPC will restart itself in another private storage. Register 2 contains
address space. the return code from the system
STORAGE macro.
00070003 Initialization of the APPC/cross-system
coupling facility (XCF) group name System Action: The system sends
failed. messages to the operator console to
show APPC’s status following the
System Action: The system
abend. If restart conditions are met,
continues processing, but APPC
APPC will restart itself in another
resources are not available. If the
address space.
operator enters the START APPC
command in response to this problem. 0007000A An internal error occurred.
APPC initialization will fail.
System Action: The system sends
00070004 The system failed to initialize the messages to the operator console to
APPC/XCF group name. The system show APPC’s status following the
could not find a match for abend. If restart conditions are met,
CVTSNAME in the system information APPC will restart itself in another
returned from the IXCQUERY macro. address space.
The system has not initialized the
0007000B An illegal state transition was
APPC/XCF group name.
requested for one of APPC’s divisions.
System Action: The system
System Action: The system sends
continues processing, but APPC
messages to the operator console to
resources are not available. If the
show APPC’s status following the
operator enters the START APPC
abend. If restart conditions are met,
command in response to this problem.
APPC will restart itself in another
APPC initialization will fail.
address space.
00070005 An unauthorized attempt was made to
0007000C The system cannot load the
start APPC. APPC can only be
ATBINPVT load module.
invoked by the installation as a started
task using the START APPC System Action: The system sends
command. messages to the operator console to
show APPC’s status following the
System Action: The system sends
abend. If restart conditions are met,
messages to the operator console to
APPC will restart itself in another
show APPC’s status following the
address space.
abend. If restart conditions are met,
APPC will restart itself in another 0007000D - 0007000E
address space. An internal error occurred.
00070006 APPC was unable to obtain required System Action: The system sends
common storage. Register 2 contains messages to the operator console to
the return code from the system show APPC’s status following the
STORAGE macro. abend. If restart conditions are met,
APPC will restart itself in another
System Action: The system sends
address space.
messages to the operator console to
show APPC’s status following the 0007000F An initialization error occurred. The
abend. If restart conditions are met, system was unable to obtain an APPC
APPC will restart itself in another resource.
address space.
System Action: The system
continues processing, but the error will
336 z/OS V1R10.0 MVS System Codes
EC7
cause the failure of APPC initialization 00090001 The caller specified a parameter list
processing if the operator enters a that contained too many or too few
START APPC command. parameters for the service being
invoked,
00070010 An internal error occurred.
System Action: The system denies
System Action: The system sends
the request. No conversations end as
messages to the operator console to
a result of the error, unless it results in
show APPC’s status following the
the abnormal ending of the address
abend. If restart conditions are met,
space. If the address space
APPC will restart itself in another
abnormally ends, all conversations
address space.
owned by the address space will be
00070011 The system was unable to load the cleaned up as part of normal APPC
ATBINPVT load module. Register 2 processing.
contains the return code from the
00090002 An abend occurred while the system
system LOAD macro.
tried to access one of the following:
System Action: The system sends v Input parameters to which the caller
messages to the operator console to does not have read access.
show APPC’s status following the v Output parameters to which the
abend. If restart conditions are met, caller does not have write access.
APPC will restart itself in another
00090003 - 00090051
address space.
An internal error occurred.
00070012 The system was unable to load the
00090052 An internal error occurred.
ATBINLPA load module. Register 2
contains the return code from the System Action: The system
system LOAD macro. continues processing, but the
requested APPC/MVS service fails.
System Action: The system sends
The system issues an SVC dump.
messages to the operator console to
show APPC’s status following the 00090054 APPC/MVS cannot access the
abend. If restart conditions are met, conversation_ID parameter for the
APPC will restart itself in another Error_Extract service.
address space.
System Action: The system does not
00070013 The system was unable to load the process the call to Error_Extract. The
ATBINMIG load module. Register 2 system continues other processing.
contains the return code from the
00090055 APPC/MVS cannot access the
system LOAD macro.
service_name parameter for the
System Action: The system sends Error_Extract service.
messages to the operator console to
System Action: The system does not
show APPC’s status following the
process the call to Error_Extract. The
abend. If restart conditions are met,
system continues other processing.
APPC will restart itself in another
address space. 00090056 APPC/MVS cannot access the
service_reason_code parameter for
00070015 An attempt was made to update the
the Error_Extract service.
state of a division, but the division
identifier is not defined. System Action: The system does not
process the call to Error_Extract. The
System Action: The system sends
system continues other processing.
messages to the operator console to
show APPC’s status following the 00090057 APPC/MVS cannot access the
abend. If restart conditions are met, message_text_length parameter for
APPC will restart itself in another the Error_Extract service.
address space.
System Action: The system does not
00070019 - 0007001D process the call to Error_Extract. The
An internal error occurred. system continues other processing.
System Action: APPC cannot restart 00090058 APPC/MVS cannot access the
itself in another address space. APPC message_text parameter for the
services remain unavailable. Error_Extract service.
Chapter 2. System Completion Codes 337
EC7
System Action: The system does not 00090069 APPC/MVS cannot access the
process the call to Error_Extract. The parameter list for the Error_Extract
system continues other processing. service.
00090059 APPC/MVS cannot access the System Action: The system does not
error_log_product_set_ID_length process the call to Error_Extract. The
parameter for the Error_Extract system continues other processing.
service.
00090070 - 00090072
System Action: The system does not An internal error occurred in
process the call to Error_Extract. The APPC/MVS.
system continues other processing.
System Action: The system
00090060 APPC/MVS cannot access the continues processing, but the
error_log_product_set_ID parameter requested APPC/MVS service fails.
for the Error_Extract service. The system takes an SVC dump.
System Action: The system does not 000A00xx An internal error occurred.
process the call to Error_Extract. The
System Action: APPC continues
system continues other processing.
processing.
00090061 APPC/MVS cannot access the
000A1000 The activation of a logical unit failed
error_log_data_length parameter for
because the VTAM application for the
the Error_Extract service.
logical unit is not APPC-capable.
System Action: The system does not Check the VTAM APPL statement for
process the call to Error_Extract. The the logical unit to ensure that you
system continues other processing. specified APPC=YES.
00090062 APPC/MVS cannot access the 00100003 The join group service abnormally
error_log_data parameter for the ended while trying to access the
Error_Extract service. XCFMSGIN_EXIT_ADDRESS input
parameter.
System Action: The system does not
process the call to Error_Extract. The System Action: The system rejects
system continues other processing. the request. The system does not join
the caller to the APPC group.
00090063 APPC/MVS cannot access the
return_code parameter for the 00100004 The join group service abnormally
Error_Extract service. ended while trying to access the
XCFMSGIN_MEMDATA input
System Action: The system does not
parameter.
process the call to Error_Extract. The
system continues other processing. System Action: The system rejects
the request. The system does not join
00090064 APPC/MVS cannot access the
the caller to the APPC group.
reason_code parameter for the
Error_Extract service. 00100005 The join group service abnormally
ended while trying to access the
System Action: The system does not
XCF_RETURN_CODE input
process the call to Error_Extract. The
parameter.
system continues other processing.
System Action: The system rejects
00090065 A program specified an incorrect
the request. The system does not join
number of parameters on a call to
the caller to the APPC group.
Error_Extract.
00100006 The join group service abnormally
System Action: The system does not
ended while trying to access the
process the call to Error_Extract. The
XCF_REASON_CODE input
system continues other processing.
parameter.
00090066 - 00090068
System Action: The system rejects
An internal error occurred in
the request. The system does not join
APPC/MVS.
the caller to the APPC group.
System Action: The system does not
00100007 The join group service abnormally
process the call to Error_Extract. The
ended while trying to access the
system continues other processing.
RETURN_CODE input parameter.
338 z/OS V1R10.0 MVS System Codes
EC7
System Action: The system rejects Unidentify Service contained an
the request. The system does not join incorrect number of parameters.
the caller to the APPC group.
System Action: APPC continues
00100008 The join group service abnormally processing, but the system does not
ended while trying to access the perform the requested service.
MEMBER_TOKEN input parameter.
00100012 The parameter list passed to the
System Action: The system rejects Define Local TP Service contained an
the request. The system does not join incorrect number of parameters.
the caller to the APPC group.
System Action: APPC continues
00100009 An incorrect number of parameters processing, but the system does not
was passed to the join group service. perform the requested service.
System Action: The system rejects 00100013 The parameter list passed to a
the request. The system does not join transaction scheduler interface service
the caller to the APPC group. contains inaccessible parameters.
0010000A - 0010000B System Action: APPC continues
An internal error occurred. processing, but the system does not
perform the requested service.
System Action: The system
automatically restarts APPC. If a 00100014 The join service failed while trying to
second failure occurs, APPC will access the parameter pointers. The
abnormally end. parameter list is inaccessible.
0010000C The parameter list passed to the System Action: The system rejects
Associate Service contained an the request. The system does not join
incorrect number of parameters. the caller to the APPC group.
System Action: APPC continues 00100015 The parameter list passed to the
processing, but the system does not Set_AS_Attributes service contained
perform the requested service. an incorrect number of parameters.
0010000D The parameter list passed to the System Action: The system
Connect Service contained an continues processing, but the
incorrect number of parameters. requested APPC/MVS service fails.
System Action: APPC continues 00100016 The parameter list passed to the
processing, but the system does not Set_AS_Attributes service contains
perform the requested service. inaccessible parameters.
0010000E The parameter list passed to the 00100017 - 00100018
Control Service contained an incorrect An internal error occurred.
number of parameters.
System Action: The system
System Action: APPC continues automatically restarts APPC. If a
processing, but the system does not second failure occurs, APPC
perform the requested service. abnormally abends.
0010000F The parameter list passed to the 00100019 An internal error occurred.
Disconnect Service contained an
System Action: The callers task is
incorrect number of parameters.
ended.
System Action: APPC continues
0010001F A program issued a version of the
processing, but the system does not
Identify service that is not valid on the
perform the requested service.
release of MVS installed on the
00100010 The parameter list passed to the system.
Identify Service contained an incorrect
System Action: The system
number of parameters.
continues processing, but the
System Action: APPC continues requested APPC/MVS service fails.
processing, but the system does not
00100020 A program issued a version of the
perform the requested service.
Unidentify service that is not valid on
00100011 The parameter list passed to the the release of MVS installed on the
system.
Chapter 2. System Completion Codes 339
EC7
System Action: The system abnormally ended because the caller
continues processing, but the specified a parameter list that
requested APPC/MVS service fails. contained too many or too few
parameters.
00100023 A program issued a version of the
Join_Sysappc_Group service that is 00140002 The Register_For_Allocates service
not valid on the release of MVS abnormally ended because the
installed on the system. system tried to access one of the
following:
System Action: The system
v Input parameters to which the caller
continues processing, but the
does not have read access
requested APPC/MVS service fails.
v Output parameters to which the
00100025 A program passed a parameter list caller does not have write access.
containing an incorrect number of
00140003 The Receive_Allocates service
parameters to the Version_Service.
abnormally ended because the caller
00100026 A program passed an inaccessible specified a parameter list that
parameter list to the Version_Service. contained too many or too few
parameters.
00100027 A program passed a parameter list
containing inaccessible parameters to 00140004 The Receive_Allocates service
the Version_Service. abnormally ended because the
system tried to access one of the
System Action: The system following:
continues processing, but the v Input parameters to which the caller
requested APPC/MVS service fails. does not have read access
00100028 An internal error occurred during v Output parameters to which the
processing of the Identify service. caller does not have write access.
System Action: The system ends the 00140005 The Reject_Conversation service
caller’s task. abnormally ended because the caller
specified a parameter list that
00100029 An internal error occurred during contained too many or too few
processing of the Unidentify service. parameters.
System Action: The system ends the 00140006 The Reject_Conversation service
caller’s task. abnormally ended because the
00120001 The Accept_Test service abnormally system tried to access one of the
ended because the caller’s parameter following:
list was incorrect. v Input parameters to which the caller
does not have read access
00120002 The Accept_Test service abnormally v Output parameters to which the
ended while trying to write to caller’s caller does not have write access.
parameter list.
00140007 The Set_Allocate_Queue_Notification
00120003 The Register_Test service abnormally service abnormally ended because
ended because the caller’s parameter the caller specified a parameter list
list was incorrect. that contained too many or too few
00120004 The Register_Test service abnormally parameters.
ended while trying to write to caller’s 00140008 The Set_Allocate_Queue_Notification
parameter list. service abnormally ended because
00120005 The Unregister_Test service the system tried to access one of the
abnormally ended because the caller’s following:
parameter list was incorrect. v Input parameters to which the caller
does not have read access
00120006 The Unregister_Test service v Output parameters to which the
abnormally ended while trying to write caller does not have write access.
to caller’s parameter list.
00140009 The Get_Event service abnormally
001300xx An internal error occurred. ended because the caller specified a
parameter list that contained too many
System Action: The system action is
or too few parameters.
unpredictable. -->
0014000A The Get_Event service abnormally
00140001 The Register_For_Allocates service
340 z/OS V1R10.0 MVS System Codes
EC7
ended because the system tried to v Output parameters to which the
access one of the following: caller does not have write access.
v Input parameters to which the caller
00140013 - 00140020
does not have read access
An internal error occurred.
v Output parameters to which the
caller does not have write access. 00150001 - 00150004
During the activation of a logical unit
0014000B The Query_Allocate_Queue service
(LU), APPC/MVS encountered an
abnormally ended because the caller
error while attempting to perform
specified a parameter list that
resource manager restart processing.
contained too many or too few
parameters. System Action: The system writes an
SVC dump and continues processing.
0014000C The Query_Allocate_Queue service
APPC/MVS adds the LU to the
abnormally ended because the
configuration, but the LU can process
system tried to access one of the
only conversations with a
following:
synchronization level of none or
v Input parameters to which the caller
confirm.
does not have read access
v Output parameters to which the 00150005 An internal error occurred.
caller does not have write access.
System Action: The system writes an
0014000D The Set_Allocate_Queue_Attributes SVC dump and continues processing.
service abnormally ended because APPC/MVS accepts Allocate requests
the caller specified a parameter list for only conversations with a
that contained too many or too few synchronization level of none or
parameters. confirm.
0014000E The Set_Allocate_Queue_Attributes 00150006 During the activation of a logical unit
service abnormally ended because (LU), APPC/MVS encountered an
the system tried to access one of the error while attempting to perform
following: resource manager restart processing.
v Input parameters to which the caller
does not have read access System Action: The system writes an
v Output parameters to which the SVC dump and continues processing.
caller does not have write access. APPC/MVS adds the LU to the
configuration, but the LU can process
0014000F The Set_Conversation_Accounting_ only conversations with a
Information service abnormally ended synchronization level of none or
because the caller specified a confirm.
parameter list that contained too many
or too few parameters. 00150008 During the processing of a
synchronization request, a partner LU
00140010 The Set_Conversation_Accounting_ detected a syncpoint architecture
Information service abnormally ended protocol violation made by APPC/MVS
because the system tried to access during the syncpoint transaction
one of the following: exchange.
v Input parameters to which the caller
does not have read access System Action: The system writes an
v Output parameters to which the SVC dump and continues processing.
caller does not have write access. The syncpoint request completes, but
the state of the distributed resources
00140011 The Unregister_For_Allocates service is unknown; a heuristic condition
abnormally ended because the caller might exist. The syncpoint
specified a parameter list that conversation is deallocated by the
contained too many or too few partner.
parameters.
00150009 - 0015000B
00140012 The Unregister_For_Allocates service An internal error occurred while the
abnormally ended because the DISPLAY APPC command processor
system tried to access one of the was trying to extract data for display.
following:
v Input parameters to which the caller System Action: The system writes an
does not have read access SVC dump and continues processing.
The system ends the DISPLAY
Chapter 2. System Completion Codes 341
EC7
command processing. Other for only conversations with a
APPC/MVS work continues. synchronization level of none or
confirm.
0015000C An APPC LOGNAME mismatch has
occurred between APPC and RRS. 00150013 - 00150017
APPC/MVS received an unexpected
System Action: The system writes an
return code from an RRS callable
SVC dump and continues processing.
service during resynchronization
APPC/MVS adds the LU to the
processing for a unit of recovery,
configuration, but the LU can process
associated with a protected
only conversations with a
conversation.
synchronization level of none or
confirm. System Action: The system writes an
SVC dump and continues processing.
System programmer response: The
The resynchronization transaction
logging value may have been
processing ends, and the unit of
changed in the APPC PROC from
recovery remains incomplete.
either:
v LEGACY to RRSGNAME or 00150018 An internal error occurred, causing the
APPC/MVS resource manager exits
v RRSGNAME to LEGACY
for an LU to become unset. Message
ATB208I identifies the LU whose
If the LOGGING value has been resource manager exits have been
changed, then check the following: unset.
v If the APPC logging value is
incorrect, change it back to either System Action: The system writes an
LEGACY or RRSGNAME (the SVC dump and continues processing.
opposite of what was currently All active protected conversations
specified), and cancel and restart associated with the LU have ended
APPC. abnormally. APPC/MVS automatically
re-registers the LU’s exits.
v If the APPC logging value is correct
and conversations with a 0015001A - 0015001B
synchronization level of synchpoint An internal error occurred.
are required, then it is necessary to
System Action: The system writes an
cancel both APPC and RRS using
SVC dump and continues processing.
the following procedure:
The system does not purge log-name
– COLD START RRS's logstreams affinities for partner LUs that
– Restart both APPC and RRS established protected conversations
with an APPC/MVS LU.
For more information, see 0015001C During the activation of a logical unit
Considerations when using the APPC (LU), APPC/MVS encountered an
LOGGING keyword in z/OS MVS error while attempting to perform
Planning: APPC/MVS Management. resource manager restart processing.
0015000D - 00150011 System Action: The system writes an
During the activation of a logical unit SVC dump and continues processing.
(LU), APPC/MVS encountered an APPC/MVS adds the LU to the
error while attempting to perform configuration, but the LU can process
resource manager restart processing. only conversations with a
System Action: The system writes an synchronization level of none or
SVC dump and continues processing. confirm.
APPC/MVS adds the LU to the 0015001D - 00150028
configuration, but the LU can process An internal error occurred.
only conversations with a
synchronization level of none or System Action: The system writes an
confirm. SVC dump and continues processing.
The system does not purge log-name
00150012 An internal error occurred. affinities for partner LUs that
System Action: The system writes an established protected conversations
SVC dump and continues processing. with an APPC/MVS LU.
APPC/MVS accepts Allocate requests
342 z/OS V1R10.0 MVS System Codes
EC7
00150029 - 0015002A System Action: Ensure that the
During the activation of a logical unit GNAME specified on the RRSPROC
(LU), APPC/MVS encountered an when RRS was restarted is correct. If
error while attempting to perform the GNAME is specified correctly then
resource manager restart processing. CANCEL and RESTART APPC.
System Action: The system writes an v Allocate requests for conversations
SVC dump and continues processing. with a synchronization level of
APPC/MVS adds the LU to the syncpt
configuration, but the LU can process v Resynchronization processing to
only conversations with a resolve incomplete units of recovery
synchronization level of none or and bring distributed resources to a
confirm. consistent state.
0015002B APPC/MVS reported an asynchronous Operator response: If APPC abends and does not
abend during syncpoint processing. restart itself automatically, enter the START command to
restart APPC.
System Action: APPC/MVS
continues to process the syncpoint. For errors during FMH-5 manager inbound processing,
An asynchronous abend may require reason code 0006xxxx, quiesce APPC by deleting all of
APPC/MVS to perform the logical units (LU) that are active in order to reject
re-synchronization to resolve the unit any new inbound TPs. Allow TPs in progress to end
of recovery. normally. When APPC has quiesced, enter a START
command to restart APPC.
0015002C An internal error occurred in
APPC/MVS during syncpoint If the system failed to initialize APPC, and APPC is an
processing. integral part of the installation, then reIPL the system.
System Action: The system See the system messages written to the console to
continues processing. The system track the status of APPC’s ending/restart processing.
issues an SVC dump.
If multiple system abends occur or if a reIPL does not
0015002D An internal error occurred in correct the problem, notify the system programmer.
APPC/MVS during syncpoint
Application Programmer Response: Depending on
processing.
the reason code, do one of the following:
System Action: The system
00020001 - 00020002
continues processing. APPC/MVS
Ensure that your program provides all the
may perform re-synchronization to
parameters for the requested APPC/MVS
resolve the unit of recovery.
service. Ensure that all bits except for the high
00150030 RRS has been restarted with a order bit are off. The high order bit must be on.
different GNAME while APPC is Correct the parameter list for the requested
active. service and submit the program again.
System Action: The system writes an 00020008 - 0002000A
SVC dump and continues processing. Do one of the following:
APPC/MVS adds the LU to the v Invoke the indicated call on a system where
configuration, but the LU can process the corresponding version of MVS is
only conversations with a installed.
synchronization level of none or
v Invoke the version of the service that is
confirm.
appropriate for the release of MVS installed
System Programmer Response: on the system.
Ensure that the GNAME specified on
00010000C - 000100016
the RRS PROC when RRS was
Ensure that your program provides all the
restarted is correct. If the GNAME is
parameters for the requested APPC/MVS
specified correctly, then cancel and
service. Ensure that all bits except for the high
restart APPC. For more information,
order bit are off. The high order bit must be on.
see Considerations when using the
Correct the parameter list for the requested
APPC LOGGING keyword in z/OS
service and submit the program again.
MVS Planning: APPC/MVS
Management. 0010001F - 00100023
Do one of the following:
0016xxxx An internal error occurred.
Chapter 2. System Completion Codes 343
EC8 • EFB
v Call the service on a system where a
EFB
version of MVS that supports the service is
installed. Explanation: JES3 DLOG processing encountered an
v Call the version of the service that is error. The abend reason code identifies the specific
supported on the release of MVS that is error.
currently installed. Code Explanation
00100025 - 00100027 01 The ASEXT macro returned a non-zero return
Ensure that the call to the Version_Service is code while the JES3DLOG address space was
coded correctly. attempting to extract the address space
parameters. Registers 2 and 3 when the EFB
For other parameter errors, check the program to abend is issued contain the return and reason
ensure that all services are correctly coded and that all codes from the ASEXT macro call.
parameters are correctly specified.
02 The MCSOPER macro returned a non-zero
If the problem recurs, notify the system programmer. return code while the JES3DLOG address
space was attempting to activate its extended
System programmer response: Examine the SVC MCS console. Registers 2 and 3 when the EFB
dump and the APPC trace records, if available, for the abend is issued contain the return and reason
cause of the problem. For the following return codes, try codes from the MCSOPER macro call.
using LUDEL followed by LUADD, or VTAM VARY
INACT followed by VARY ACT, to reactivate the LU: 03 Reserved - not used
v 00150001 - 00150004 04 The IXZXIXAT macro returned a non-zero
v 00150006 return code while the JES3DLOG address
v 0015000C - 00150011 space was attempting to attach to the JESXCF
v 0015001C group. Registers 2 and 3 when the EFB abend
v 00150029 - 0015002A is issued contain the return and reason codes
from the IXZXIXAT macro call.
If the problem cannot be resolved or if the reason code
indicates an internal error, search problem reporting 05 The IXZXIXMB macro returned a non-zero
data bases for a fix for the problem. If no fix exists, return code while the JES3DLOG address
contact the IBM Support Center. Provide the SVC space was attempting to attach to the default
dump. mailbox. Registers 2 and 3 when the EFB
abend is issued contain the return and reason
Source: APPC/MVS codes from the IXZXIXMB macro call.
06 The IXZXIXMD macro returned a non-zero
EC8 return code while the JES3DLOG address
space was attempting to delete the default
Explanation: An error occurred in the NETSERV
mailbox. Registers 2 and 3 when the EFB
address space during JES TCP/IP NJE processing.
abend is issued contain the return and reason
Register 15 contains the hexadecimal reason code for codes from the IXZXIXMD macro call.
the error. The error is explained in the IAZ0nnnI
07 The MCSOPMSG macro returned a return
message (where nnn = decimal value of reason code)
code greater than 12 while the JES3DLOG
preceding the abend. For example, if the reason code
address space was attempting to access the
(in R15) = X'64' = 100, it would be described in
next message in its message data space.
IAZ0100I.
Registers 2 and 3 when the EFB abend is
System action, operator response and system issued contain the return and reason codes
programmer response are documented in the IAZ0nnnI from the MCSOPMSG macro call.
message description.
08 IATCNDFM returned a non-zero return code
Code Explanation: when it was called by IATCNDMS to format an
MDB in JES3 DLOG format. Registers 2 and 3
See descriptions of messages IAZ0001I to
when the EFB abend is issued contain the
IAZ0499I in z/OS MVS System Messages, Vol 6
return and reason codes from IATCNDFM.
(GOS-IEA) for all possible abend error messages.
09 An invalid function code was passed to
Source: JES TCP/IP NJE Server (NETSERV)
IATCNDAL. Register 2 when the EFB abend is
issued contains the function code.
0A An invalid function code was passed to
IATCNDIT. Register 2 when the EFB abend is
issued contains the function code.
344 z/OS V1R10.0 MVS System Codes
EFB
0B An invalid function code was passed to from the IXZXIXAT service routine (e.g. DC5
IATCNDTR. Register 2 when the EFB abend is abend). If a dump was taken of the JESXCF
issued contains the function code. address space as a result of that abend, that
dump should also be provided as part of the
0C An invalid message pointer cell was returned
documentation.
by IATCNDFM when it was called by
IATCNDIT to format an MDB in JES3 DLOG 05 See z/OS MVS Programming: JES Common
format. Coupling Services for a description of the
IXZXIXMB return and reason codes.
0D The RESMGR macro returned a non-zero
return code while the JES3DLOG address The following additional documentation should
space was attempting to setup a task level be provided:
resource manager. Registers 2 and 3 when the v Compiler listing for module IATCNDIT.
EFB abend is issued contain the return and
v A non-zero return code from the IXZXIXMB
reason codes from the RESMGR macro call.
macro is usually preceded by an ABEND
System action: A dump of the JES3DLOG address from the IXZXIXMB service routine (e.g.
space and its message data space is taken, the DC5 abend). If a dump was taken of the
JES3DLOG address space is terminated, and the JESXCF address space as a result of that
DLOG facility is disabled. abend, that dump should also be provided
as part of the documentation.
Note: A dump will not be taken for reason code 2 if a
06 See z/OS MVS Programming: JES Common
return code of four (extended MCS console
Coupling Services for a description of the
already active) is returned from the MCSOPER
IXZXIXMD return and reason codes.
macro.
The following additional documentation should
System programmer response: Contact IBM support
be provided:
and provide the following documentation:
v Compiler listing for module IATCNDIT.
v The EFB abend reason code
v A non-zero return code from the IXZXIXMD
v The return and reason codes from the service that
macro is usually preceded by an ABEND
was called (if applicable)
from the IXZXIXMD service routine (e.g.
v The dump taken by the JES3DLOG address space (if DC5 abend). If a dump was taken of the
any) JESXCF address space as a result of that
v The SYSLOG around the time of error abend, that dump should also be provided
as part of the documentation.
01 See z/OS MVS Programming: Authorized
Assembler Services Reference ALE-DYN for a 07 See z/OS MVS Programming: Authorized
description of the ASEXT return and reason Assembler Services Reference EDT-IXG for a
codes. description of the MCSOPMSG return and
reason codes.
The following additional documentation should
be provided: The following additional documentation should
v Compiler listings for modules IATCNDS and be provided:
IATCNDIT. v Compiler listings for modules IATCNDIT and
IATCNDMS.
02 See z/OS MVS Programming: Authorized
Assembler Services Reference LLA-SDU for a 08 See macro IATYCNDF for a description of the
description of the MCSOPER return and return codes from IATCNDFM.
reason codes.
The following additional documentation should
The following additional documentation should be provided:
be provided: v Compiler listings for modules IATCNDMS
v Compiler listing for module IATCNDIT. and IATCNDFM.
04 See z/OS MVS Programming: JES Common 09 The following additional documentation should
Coupling Services for a description of the be provided:
IXZXIXAT return and reason codes. v Compiler listings for modules IATCNDTK
The following additional documentation should and IATCNDAL.
be provided: 0A The following additional documentation should
v Compiler listing for module IATCNDIT. be provided:
v A non-zero return code from the IXZXIXAT
macro is usually preceded by an ABEND
Chapter 2. System Completion Codes 345
Fnn
v Compiler listings for module IATCNDIT and v When nn is not equal to 13, 14, 17, or 37, the
the module that called IATCNDIT (usually system records in register 2 the address of the
IATCNDTK or IATCNDRR) request block prefix for the program that issued the
incorrect SVC.
0B The following additional documentation should
be provided: Operator response: If the system programmer asks
v Compiler listings for module IATCNDTR and for an SVC dump, set the following SLIP trap:
the module that invoked it via the IATXDLTR SLIP SET,COMP=Fnn,ACTION=SVCD,END
macro. The caller of IATCNDTR can be
System programmer response: Depending on the
found by examining the linkage stack in the
value of nn, do one of the following:
dump at the time of error. When the caller’s
registers and return address are saved on v When nn is equal to 13, 14, 17, or 37, see message
the linkage stack via a ″BAKR R14,0″ IEC900I. Search the problem reporting data bases for
instruction. a fix for the problem. If no fix exists, ask the operator
to set a SLIP trap to obtain an SVC dump. Contact
0C The following additional documentation should the IBM Support Center. Provide the SVC dump and,
be provided: if available, the logrec data set error record.
v Compiler listings for modules IATCNDFM v When nn is not equal to the above values, do the
and IATCNDMS. following:
0D See z/OS MVS Programming: Authorized For recently installed SVCs, if the number (nn) is
Assembler Services Reference LLA-SDU for a X'C8' thru X'FF', it is an installation defined SVC. If
description of the RESMGR return and reason the SVC number is X'00' thru X'C7', and you continue
codes. to have a problem after following the next steps,
contact the IBM Support Center.
The following additional documentation should
be provided: 1. Correct the error as follows:
v Compiler listing for module IATCNDIT. – Make sure that the SVC instruction was not
incorrectly modified.
Source: JES3
– Check the operand against the valid codes for
the system being used.
Fnn – Determine if the SVC that was issued has
Explanation: The system detected an error while been installed correctly in the system. For a
processing a Supervisor Call (SVC) instruction. The last detailed description on creating installation
2 digits of this completion code, nn, are the operand of defined SVCs, see z/OS MVS Programming:
the SVC instruction in hexadecimal. For example, Authorized Assembler Services Guide, or z/OS
completion code X'F0D' means that the error occurred MVS Initialization and Tuning Reference.
while the system was processing SVC X'0D', that is, a. Ensure that the EPNAME specified in
SVC 13. IEASVCxx parmlib member or on the
SVCUPDTE macro, matches the name
One of the following occurred: specified in the LINKEDIT JCL used to link
v When nn is equal to 13, 14, 17, or 37, recovery for the SVC routine into SYS1.NUCLEUS or
OPEN/CLOSE/EOV failed to recognize a passed the LPA.
internal abend code. Register 12 contains the passed b. Ensure that the system has been reIPLed
internal abend code. This is probably a system error. after the linkedit of the SVC routine to the
If the ABEND is accompanied by message IEC900I, modified LPA. See z/OS MVS Initialization
the code was issued by DFSMSdfp and the code and Tuning Reference for information
explanations are provided in this section . If the about the CLPA and MLPA system
ABEND is accompanied by error messages starting parameters.
with message prefix EDG, the code was issued by
DFSMSrmm™. See z/OS DFSMSrmm Implementation 2. Run the job step again.
and Customization Guide for explanations of the
codes when they are issued by DFSMSrmm. Also, the are a couple of other common situations that
can cause this ABEND:
v When nn is not equal to 13, 14, 17, or 37, the
system detected an incorrect SVC instruction. v Programs coded or compiled to run on CMS systems
commonly issue SVCs 200-204 (X'C8'- X'CC'). If one
System action: Depending on the value of nn, the of these objects is linked into an MVS load module, it
system does the following: will get the corresponding Fnn ABEND when that
v When nn is equal to 13, 14, 17, or 37, the system instruction is executed. The fix is to write such code
records the unrecognized internal abend code in so that it detects which operating system it’s running
register 12. It issues message IEC900I. on and execute the appropriate instructions.
346 z/OS V1R10.0 MVS System Codes
v Another variation on this (and more likely to occur) is
REXX EXECs that have been compiled into object
format. These have to be link-edited with the
appropriate stub code CSECT (EAGSxxxx). If the
compiler output is linked into a load module by itself
(or the entry point is not set to the stub), the resultant
load module will get a FCA ABEND. The programmer
should refer to IBM Compiler and Library for SAA®
REXX/370 - User’s Guide and Reference for details.
Source: Supervisor control
Chapter 2. System Completion Codes 347
348 z/OS V1R10.0 MVS System Codes
Chapter 3. Wait State Codes
(at location X'BA') of the 4-byte subchannel
002
identification word at location X'B8'.
Explanation: During initial program load (IPL), an I/O 2. Bring up the Device Configuration Display. Enter the
operation was not initiated; the subchannel status word 2-byte subchannel number found in step 1. This
(SCSW) was stored, and the channel was not busy. displays the device number, unit address, and the
Operator response: This is probably a hardware installed channel paths for the selected subchannel
error. ReIPL the system. If the problem recurs, contact number.
hardware support. If there is only one channel path to the device, there
is no need for the system operator to continue
Source: Input/output supervisor (IOS)
problem determination. Contact hardware support.
3. It is likely that the failing path is the last path used.
003 Display subchannel status information. On
Explanation: Initial program load (IPL) cannot CMOS-based processors, this is the Analyze
continue processing because the subchannel for one of Subchannel Data display. Read the last path used
the following devices is not operational: mask (LPUM) field to determine the last path used.
The LPUM field consists of 8 bits. If bit n is on, then
v The IPL device. CHPIDn is the last path used. For example, if the
v The IODF volume, as specified in the first four LPUM field shows B'01000000', bit 1 is on and the
characters of the LOAD parameter. CHPID1 field identifies the last path used.
4. Bring up the CHPID menu and configure the last
Note: If you did not specify an IODF volume in the used channel path offline.
LOAD parameter, this wait state is due to a
5. ReIPL the system.
problem with the subchannel for the IPL device.
6. If the problem does not recur, you have identified
System action: The system enters a non-restartable the failing path.
wait state.
If the problem recurs and there are other paths to
Operator response: Do one of the following: the device, configure the other paths offline one by
v Make sure the IPL device and the IODF volume are one until you have identified the failing path. If this
enabled and reIPL the system. does not identify a failing path, the problem is
caused either by the remaining online path or by the
v IPL from a different device, or IPL using a different
device. Contact hardware support.
IODF volume.
v Contact hardware support. Source: Input/output supervisor (IOS)
Source: Initial program load (IPL)
005
004 Explanation: An I/O interruption during initial program
load (IPL) indicated a unit check.
Explanation: During system initialization, the system
did not initiate an I/O operation. The channel was not A sense operation was unable to determine the cause
busy after the system tried to store control and status of the unit check, but the unit check was not caused by
information for the subchannel. one of the following:
v No record found
System action: The system enters wait state X'004'. v File mask violation
The system does not store the subchannel status word v End of cylinder
(SCSW). v Track condition check
Operator response: Report this problem to the System action: The system enters a non-restartable
system programmer. wait state.
System programmer response: You need to Operator response: This problem can indicate either
determine whether a device or a path to the device that:
caused the problem. The most likely path is the last v The system programmer either modified the IPL text
path used to access the device. Take the following or the IODF data set (if defined).
steps: v The system detected a hardware error on the IODF
1. Using the hardware Alter/Display facility, read the volume or the SYSRES volume.
4-byte subchannel address in central storage at
X'B8'. The subchannel number is the last two bytes
© Copyright IBM Corp. 1988, 2009 349
006 • 007
If a system programmer modified the IPL text or the
006
IODF data set, notify the system programmer.
Otherwise, make sure the IPL pack is ready, and reIPL Explanation: During initial program load (IPL), an I/O
the system. error occurred while IPL was reading from the SYSRES
or IODF volume. The error can be one or more of the
For other situations, a hardware problem is affecting the following:
system. The steps below will assist to find the address v An interface control check
of the device that received the unit check, and you need v A channel control check
to determine whether a device or a path to the device v A channel data check
caused the problem. The most likely path is the last v A program check
path used to access the device. Take the following v A channel chaining check
steps: v STATE CHANGE INTERRUPT detected due to
1. Using the hardware Alter/Display facility, read the SETCACHE SUBSYS OFF issued on sharing
4-byte subchannel address in central storage at system.
X'B8'. The subchannel number is the last two bytes
(at location X'BA') of the 4-byte subchannel Note: One commonly seen cause for this problem is
identification word at location X'B8'. having the nucleus in secondary extents. This
problem has also been caused by the nucleus
2. Bring up the Device Configuration Display. Enter the
containing a not-executable SVC. Browse
2-byte subchannel number found in step 1. This
SYS1.NUCLEUS for any member with an
displays the device number, unit address, and the
attribute of NX.
installed channel paths for the selected subchannel
number. System action: The system enters a non-restartable
If there is only one channel path to the device, there wait state.
is no need for the system operator to continue Operator response: Use the hardware Problem
problem determination. Contact hardware support. Determination facilities to see if any errors occurred
3. It is likely that the failing path is the last path used. during the IPL process. If channel errors occurred, try
Display subchannel status information. On configuring the channel paths offline and reipling the
CMOS-based processors, this is the Analyze system.
Subchannel Data display. Read the last path used
If the problem recurs, notify the system programmer.
mask (LPUM) field to determine the last path used.
The LPUM field consists of 8 bits. If bit n is on, then If the system programmer requests, obtain a standalone
CHPIDn is the last path used. For example, if the dump.
LPUM field shows B'01000000', bit 1 is on and the
CHPID1 field identifies the last path used. System programmer response: Search problem
reporting databases for a fix for the problem. If no fix
4. Bring up the CHPID menu and configure the last exists, contact the IBM Support Center. Provide the
used channel path offline. stand-alone dump.
5. ReIPL the system.
Source: Initial program load (IPL)
6. If the problem does not recur, you have identified
the failing path.
If the problem recurs and there are other paths to 007
the device, configure the other paths offline one by Explanation: During system initialization, a console
one until you have identified the failing path. If this was not available to the system.
does not identify a failing path, the problem is
caused either by the remaining online path or by the Operator response: Check to see if the console is
device. Contact hardware support. available. If so, reIPL. If not, contact the system
programmer.
Finally, if the above steps do not locate the failing
hardware, notify the system programmer. System programmer response: Check the Console
Report, contained in the HCD Operating System report
System programmer response: If the IPL text or the (OS), to verify that at least one nucleus initialization
IODF data set was modified, look for a problem in the program (NIP) console is configured. HCD builds the
modified text or data set and fix it. If the failing OS report based on the IODF configuration data. Do the
hardware is not found using the steps in the Operator following:
Response, ask the operator to obtain a stand-alone
v See z/OS HCD User’s Guide for information
dump. Contact the IBM Support Center and provide the
regarding IODF.
stand-alone dump.
v Obtain a stand-alone dump.
Source: Initial program load (IPL)/nucleus initialization
v Search problem reporting databases for a fix to the
program (NIP)
problem. If no fix exists, contact the IBM Support
Center.
350 z/OS V1R10.0 MVS System Codes
009 • 00E
| Source: Console services v If the system programmer asks for a stand-alone
dump, obtain one.
009 System programmer response: Search problem
reporting databases for a fix for the problem. If no fix
Explanation: There is a system build error. The
exists, obtain the dump. If no dump exists, ask the
required release is not installed. A reason code
operator to obtain a stand-alone dump. Contact the IBM
identifies the error:
Support Center. Provide the dump.
Code Explanation
Source: Master scheduler
0 The required release of DFSMS is not
installed.
00D
System action: The system issues wait state code
Explanation: During system initialization, the master
X'009' reason 0 and message IEA016W.
scheduler ended abnormally.
Operator response: Notify the system programmer.
System action: The system ends system initialization.
System programmer response: Install the proper The system enters wait state X'00D'.
release of DFSMS, and then re-IPL.
Operator response: Try to reIPL the system. If
Source: System initialization (IPL/NIP) unsuccessful, contact the system programmer. If the
system programmer asks for a stand-alone dump,
obtain one.
00A
System programmer response: Search problem
Explanation: For one or more of the following data reporting databases for a fix for the problem. If no fix
sets: exists, ask the operator to obtain a stand-alone dump.
v SYS1.LINKLIB Contact the IBM Support Center. Provide the
v SYS1.MIGLIB stand-alone dump.
v SYS1.CSSLIB Source: Master scheduler
v SYS1.SIEALNKE
v SYS1.SIEAMIGE 00E
Their catalog entries could not be found on, or could not Explanation: Initial program load (IPL) cannot
be retrieved from the system catalog. This wait state is continue due to a problem on the system residence
preceded by message IEA326I. (SYSRES) volume.
System action: The system issues message IEA326I The right-most four bytes of the program status word
before entering a non-restartable wait state. (PSW) have the following format:
Operator response: Notify the system programmer. x rr00www
System programmer response: Ensure that all of the where:
above data sets are in the catalog, and then restart the
system. x Irrelevant information.
If the problem persists, search problem reporting rr A hexadecimal reason code indicating the
databases for a fix for the problem. If no fix exists, reason for the failure.
contact the IBM Support Center.
www The wait state code.
Source: Initial program load (IPL)
The reason code (rr) is one of the following:
00B Reason Code
Explanation
Explanation: During system initialization, the master
scheduler ended abnormally. 01
System action: The system ends system initialization. IPL cannot locate the SYS1.NUCLEUS data
The system writes a dump. The system enters wait set or the system nucleus member of the
state X'00B'. SYS1.NUCLEUS data set on the system
residence volume. The nucleus member is one
Operator response: Do the following:
of the following:
v Try to reIPL the system. If unsuccessful, contact the
v IEANUC01, which is DAT-on nucleus
system programmer.
IEANUC01
v Obtain the dump written by the system.
Chapter 3. Wait State Codes 351
00F • 017
v IEANUC0x, which is an alternate DAT-on fix for the problem. If no fix exists, ask the operator to
nucleus where x is not 1 obtain a stand-alone dump. Contact the IBM Support
v IEAVEDAT, which is the DAT-off nucleus Center. Provide the stand-alone dump.
DAT is the acronym for dynamic address
translation. 013
02 An incorrect system residence (SYSRES) Explanation: During processing of the nucleus
volume has been chosen for the IPL. initialization program (NIP), an error occurred from
which recovery is impossible. Check the system
System action: The system enters a non-restartable completion code to determine the problem.
wait state.
Operator response: If requested by the system
Operator response: programmer, obtain a stand-alone dump. ReIPL the
Reason Code system.
Action System programmer response: If the problem cannot
01 If you selected an alternate DAT-on nucleus be resolved, search problem reporting databases for a
member, make sure that the alternate nucleus fix for the problem. If no fix exists, ask the operator to
identifier (x of IEANUC0x) was correctly obtain a stand-alone dump. contact the IBM Support
entered through the console frame, or at Center. Provide the stand-alone dump.
absolute storage location X'F'. Then reIPL the
system. 014
02 Ensure that the correct SYSRES volume is Explanation: The system encountered recursive
specified for the IPL then reIPL the system. program checks. Usually, this is the result of an overlay
of a critical system control block, such as PSA, ASCB,
If the error persists, notify the system programmer. SGTE, or PGTE.
Obtain a stand-alone dump if requested by the system
programmer. System action: The system enters a non-restartable
wait state.
System programmer response:
Operator response: If the system programmer
Reason Code requests a stand-alone dump, obtain one. ReIPL the
Action system.
01 Make sure that the SYS1.NUCLEUS data set System programmer response: Do the following:
resides on the system residence volume and 1. Ask the operator to obtain a stand-alone dump.
that it contains the members you want to load.
2. Determine the control block that has been overlaid
02 Ensure that the correct SYSRES volume is and the module that did the overlay. In many cases,
specified for the IPL and that the hardware the last program to be dispatched on that processor
management console (HMC) load profile points caused the overlay. The last program dispatched
to this volume. Then reIPL the system. can be determined from the system trace table.
3. Search problem reporting databases for a fix for the
If the problem persists, search problem reporting problem. If no fix exists, contact the IBM Support
databases for a fix for the problem. If no fix exists, Center. Because of the possibility that a hardware
contact the IBM Support Center. Provide the malfunction contributed to this problem, you should
stand-alone dump. For reason code 01, also provide the also contact hardware support. Provide to the IBM
name of the SYS1.NUCLEUS member that the IPL Support Center and to hardware support the
program could not find. stand-alone dump.
Source: Initial program load (IPL) Source: Supervisor control
00F 017
Explanation: For initial program load (IPL), a volume Explanation: During initial program load (IPL), a unit
has been loaded that does not contain IPL text. check occurred after an I/O operation was successfully
Operator response: Correctly identify the correct started. The I/O operation was:
volume to be loaded. Verify that the correct volume is v A sense I/O
mounted. If requested by the system programmer, v An attempt to read the home address and record 0 of
obtain a stand-alone dump. ReIPL the system. a track that previously caused a track condition check
System programmer response: If the problem cannot The 4-byte address of the subchannel identifier can be
be resolved, search problem reporting databases for a found in central storage at decimal address 184 (X'B8').
352 z/OS V1R10.0 MVS System Codes
019 • 01B
System action: The system enters a non-restartable v The IODF being used for IPL may be empty.
wait state.
System action: The system enters a non-restartable
Operator response: Report this problem to the wait state.
system programmer.
Operator response: Do one of the following:
System programmer response: You need to v If this wait state occurred because an operator
determine whether a device or a path to the device pressed the START key during system initialization,
caused the problem. The most likely path is the last let the IPL continue. It is not necessary to reIPL; the
path used to access the device. Take the following system will start the waiting processors automatically.
steps:
v Make sure the SYS1.NUCLEUS data set does not
1. Using the hardware Alter/Display facility, read the have secondary extents. If there are no secondary
4-byte subchannel address in central storage at extents, the error is probably the result of a hardware
X'B8'. The subchannel number is the last two bytes problem. Contact hardware support. When the
(at location X'BA') of the 4-byte subchannel problem has been corrected, reIPL the system.
identification word at location X'B8'.
v Ensure that the IPL text program installed is at the
2. Bring up the Device Configuration Display. Enter the correct level for the operating system. If not, reinstall
2-byte subchannel number found in step 1. This IPLTEXT as described in the MVS program directory.
displays the device number, unit address, and the
installed channel paths for the selected subchannel Source: Initial program load (IPL)
number.
If there is only one channel path to the device, there 01B
is no need for the system operator to continue
problem determination. Contact hardware support. Explanation: An active SLIP trap requests an action
of WAIT. The conditions specified on the SLIP command
3. It is likely that the failing path is the last path used. have been met. The system enters a wait state, as
Display subchannel status information. On requested.
CMOS-based processors, this is the Analyze
Subchannel Data display. Read the last path used PSAWTCOD in the prefixed storage area (PSA) points
mask (LPUM) field to determine the last path used. to a 28-byte field:
The LPUM field consists of 8 bits. If bit n is on, then 01ccccxxrrrrrrrrppppppppssssssssllllllllzzzzzzzzgggggggg
Recovery termination manager 1 (RTM1) functional recovery
CHPIDn is the last path used. For example, if the routine (FRR)type of entry.
LPUM field shows B'01000000', bit 1 is on and the
2ccccxxrrrrrrrrppppppppwwwwwwwwllllllllzzzzzzzzgggggggg
CHPID1 field identifies the last path used. RTM2 ESTAE type of entry (RTM2WA).
4. Bring up the CHPID menu and configure the last 03ccccxxrrrrrrrrppppppppaaaaaaaallllllllzzzzzzzzgggggggg
used channel path offline. Address space ending type of entry.
5. ReIPL the system. 04ccccxxrrrrrrrrppppppppiiiiiiiillllllllzzzzzzzzgggggggg
Program event recording (PER) interrupt type of entry.
6. If the problem does not recur, you have identified
the failing path. The variable information in the field is as follows:
If the problem recurs and there are other paths to
cccc A pointer to the logical CPU id of the
the device, configure the other paths offline one by
processor where the event was
one until you have identified the failing path. If this
detected.
does not identify a failing path, the problem is
caused either by the remaining online path or by the xx Irrelevant information.
device. Contact hardware support.
rrrrrrrr A pointer to the general registers.
Source: Initial program load (IPL)
pppppppp A pointer to the program status word
(PSW).
019
ssssssss A pointer to the system diagnostic
Explanation: During initial program load (IPL), an work area (SDWA).
unexpected program interruption occurred. IPL did not
complete loading the resident nucleus. If this wait state llllllll A pointer to control registers 3 and 4.
occurred because the IPL program is in error, a stand zzzzzzzz A pointer to the access registers.
alone dump should be taken so that the cause of the
program error can be diagnosed. wwwwwwww A pointer to the RTM2 work entry.
The problem is one of the following: aaaaaaaa A pointer to the address space control
v The operator pressed START during system block (ASCB).
initialization. iiiiiiii A pointer to the PER interrupt code.
v The IPL program is in error.
v The storage in which IPL resides is failing.
Chapter 3. Wait State Codes 353
01C • 022
gggggggg A pointer to the high 32 bits of the x Irrelevant information.
64-bit GPRs, or 0 if not available.
rrrr A hexadecimal reason code indicating the
System action: The system issues message IEA992I reason for the failure.
before the system enters the restartable, disabled wait
www The wait state code.
state.
Operator response: Follow the directions of the The reason code (rrrr) is one of the following:
system programmer for the SLIP trap. Then restart the
system by invoking the restart function. 0010 The service processor could not provide
channel path information to reconfiguration.
Source: Recovery termination manager (RTM) This is a hardware problem.
0030 The service processor could not provide side
01C information to reconfiguration. This is a
hardware problem.
Explanation: Supervisor control experienced a
recursive abnormal end in its super functional recovery 0040 Reconfiguration failed to determine the amount
routine (FRR). This is probably a software error. of storage needed for side information.
The right-most four bytes of the program status word System action: The system ends the initialization. The
(PSW) have the following format: system enters nonrestartable wait state X'020'.
x0rrrwww Operator response: For reason code X'0010' or
X'0030', obtain a stand-alone dump. Contact hardware
where: support, providing the recorded contents of the wait
x Irrelevant information. state PSW. Check the processor controller. Try to do a
switch-over or reIPL. If this does not work, partition the
rrr A hexadecimal reason code indicating the machine and use the side with a good service
reason for the failure. processor.
www The wait state code. For reason code X'0040', contact the system
programmer.
The reason code (rrr) is one of the following:
System programmer response: For reason code
000 Supervisor control experienced a double X'0040', search problem reporting databases for a fix for
recursive abend. the problem. If no fix exists, contact the IBM Support
Center. Ask the operator to obtain the stand-alone dump
004 Supervisor control experienced a recursive
and provide it to IBM.
abend during list transition processing.
Source: Reconfiguration
System action: The system may issue message
IEA967W. The system writes a logrec error record.
022
Operator response: If the system programmer
requests a stand-alone dump, obtain one. ReIPL the Explanation: A page fault occurred for a page with a
system. primary and secondary copy. The primary and
secondary devices are in one of the following states:
System programmer response: Search problem
v Quiesced
reporting databases for a fix for the problem. If no fix
v Not ready
exists, ask the operator to obtain a stand-alone dump.
Contact the IBM Support Center. Provide the The error occurred in a system facility invoked by direct
stand-alone dump and, if available, the logrec error access volume verification (DAVV).
record.
Operator response: Do the following:
Source: Supervisor control v Display the contents of register 7 to see if the correct
volume is mounted. Register 7 contains the address
020 of the unit control block (UCB) that contains the
following:
Explanation: Reconfiguration initialization failed. The
– The device address
wait state reason code specifies the error.
– The volume serial number of the volume that
The right-most four bytes of the program status word should be mounted
(PSW) have the following format:
xrrrrwww ATTENTION: If you do not mount the correct volume
before restarting the system, some system data may
where: be lost.
354 z/OS V1R10.0 MVS System Codes
023 • 02E
v ReIPL the system. v Use MQE+X'0' of the oldest MQE to find the MQE of
the next oldest message. Again, the message text for
Source: Input/output supervisor (IOS)
this MQE begins at MQE+X'8'.
v Repeat this sequence (using MQE+X'0' of the current
023 MQE to locate the next MQE), until the message text
Explanation: During the creation of the system trace for the appropriate IEA51xW message is displayed.
address space or during the initialization of the system Notify the system programmer, providing the texts of
trace function, the system detected an error. System IEA087W messages. If the system programmer
trace returned a nonzero return code. requests it, obtain a stand-alone dump.
System action: The system abnormally ends the System programmer response: Translate the text of
system trace initialization with a nonrestartable wait IEA087W messages from hexadecimal into EBCDIC.
state. The system writes message IEA416W.
If a NUCLSTxx member is being used (the LOADxx
Operator response: Notify the system programmer. member has a NUCLST statement which refers to a
System programmer response: Search problem NUCLSTxx member), and the NUCLST member
reporting databases for a fix for the problem. If no fix includes one or both of the modules in the message
exists, contact the IBM Support Center. text, the problem may be that the module being
included has entry points in common with a module that
Source: System trace is already included. If this is the case, the NUCLST
member must be changed, or the entry point(s) in the
module being included must be changed to have
025
different entry point names.
Explanation: The system detected a duplicate entry
If either module in the message text is supplied by the
point name appearing in modules being loaded into the
installation, change the entry point name.
DAT-on nucleus. (DAT is the acronym for dynamic
address translation.) If one of the modules is IEANUC0x, look in the link-edit
map to find which CSECT contains the duplicate
System action: The system issues message
CSECT name.
IEA087W to identify the entry point names and the
modules in which the entry points appear. IEA087W If IBM supplies both modules, contact the IBM Support
appears one or more times in the IPL WTO buffer. Center. Provide a stand-alone dump and the IEA087W
message text.
The system enters a non-restartable wait state.
Source: Initial program load (IPL)
Operator response: Do the following as soon as
possible to find the WTO buffer and locate message
IEA087W in the buffer. Do not write a stand-alone dump 02E
before doing this procedure, because the dump might
overlay storage. Explanation: The auxiliary storage manager (ASM) is
unable to function because of recovery problems or an
v Using the hardware Alter/Display facility, display the unusual number of permanent I/O errors on one or
address at location X'14' in central storage. This more necessary page data sets. The accompanying
address points to the IPL diagnostics area. Primary reason code further describes the error:
Real Storage must be displayed to find the IPL
diagnostic area. Code Explanation
v Add X'28' to the address of the IPL diagnostic area 00 The cause of the error cannot be determined.
and display the resulting location in central storage.
This location contains the 31-bit virtual address of the 01 The PLPA data set is now bad.
IPL vector table (IVT). Henceforth, all addresses are 02 The common data set is now bad.
31-bit virtual and you must switch to displaying
Primary Virtual Storage to display remaining 03 Both the PLPA and common data sets are not
storage locations. available.
v Add X'E0' to the IVT address. The result is the 04 The PLPA data set is now bad.
address of the IVTMQHP field. IVTMQHP contains
the address of the message queue header (MQH). 05 The common data set is now bad.
v MQH+X'0' contains the address of the oldest 06 The last local page data set is now bad.
message queue element (MQE) available. The
07 The catalog entry for the data set has been
message text for the oldest MQE begins at
deleted while in use.
MQE+X'8'.
08 The catalog data set extents, volume, device
type, or page data set attributes have changed.
Chapter 3. Wait State Codes 355
030 • 031
09 The status information record header has
031
become unrecognizable.
Explanation: The system did not find a unit control
0A The status information record has been
block for the device containing the system residence
updated.
(SYSRES) volume, for one of the following reasons:
System action: System processing ends. The system v The system was IPLed using the wrong SYSRES
issued message ILR008W or ILR035W prior to the wait volume
state. The system may have issued messages ILR007I,
v The SYSRES volume was not specified in the I/O
ILR009E, and ILR010I previously; these messages
configuration definition
indicate what conditions led to the wait state.
v The system did not select the desired I/O
Operator response: Report this wait state to the configuration.
system programmer. Provide the system programmer
with the system messages for problem analysis. System action: The system enters wait state X'031'.
If necessary, at the IPL, replace the page data sets Operator response: Depending on the reason that
referenced in the preceding messages or add more this wait state code was issued, do the following:
page data sets. Then IPL the system. v If the system was IPLed using the wrong SYSRES
volume, then mount the correct SYSRES volume and
System programmer response: Analyze the
reIPL the system.
messages provided by the operator to determine the
cause of the error. Look at any I/O, machine check, v If the SYSRES volume was not specified in the I/O
missing interrupt handler, or disabled console configuration definition, then notify the system
communication messages that occurred prior to the programmer to rebuild the I/O configuration to include
wait. Determine which page data sets are no longer the correct SYSRES volume.
usable. Correct or replace these data sets. v If the system did not select the desired I/O
configuration, use the following steps to determine
Source: Auxiliary storage manager (ASM)
which I/O configuration was selected; then notify the
system programmer:
030 1. Using the hardware Alter/Display facility, read the
Explanation: The system abended a task during real address in central storage at X'14',
nucleus initialization program (NIP) processing. The representing the address of the IPL diagnostic
hexadecimal abend code ccc appears in the right-most area.
four bytes of the wait state program status word (PSW). 2. Add X'28' to the address in X'14', and also read
The wait state PSW can appear in either of the this as a real address in central storage. The
following formats: result is a 31-bit virtual address, which is the IPL
x0cccwww vector table (IVT). Henceforth, all addresses are
xccc0www 31-bit virtual and you must switch to displaying
Primary Virtual Storage to display remaining
System action: The system abends the task and storage locations. Note that the following
enters a non-restartable wait state. addresses are also 31-bit virtual addresses.
Operator response: Record the wait state PSW and 3. Add X'E0' to the address of IVT to locate the
notify the system programmer. If the system IVTMQHP field, which points to the message
programmer requests it, obtain a stand-alone dump. queue header (MQH).
System programmer response: See the system 4. MQH + X'0' points to the oldest message queue
programmer response for the abend code. element (MQE) available. Message text beings at
MQH + X'8'. This message should be IEA371I,
The abend SVC entry in the system’s SVC table showing the device number and data set
contains the address of a trap routine in NIP and not (SYS1.PARMLIB or SYS1.IPLPARM) used to
the address of the abend SVC. The registers at the time located the selected LOADxx member.
of the abend SVC request are found in the Type I SVC 5. MQE + X'0' of the oldest MQE points to the
save area. second oldest MQE. This message should be
If the problem persists, search problem reporting IEA246I, showing which LOADxx member was
databases for a fix for the problem. If no fix exists, selected.
contact the IBM support Center. Provide the contents of 6. MQE + X'0' of the oldest MQE points to the third
the wait state PSW. oldest MQE. This message should be either
IEA097I, showing which MVSCP IOCONFIG was
Source: Nucleus initialization program (NIP)
selected, or IEA519I, showing which IODF was
selected.
System programmer response: If the SYSRES
356 z/OS V1R10.0 MVS System Codes
032 • 035
volume was not specified in the I/O configuration reason code can appear in the right-most four bytes of
definition, then rebuild the I/O configuration to include the wait state program status word (PSW). The wait
the correct SYSRES volume. state PSW can appear in either of the following formats:
If the system did not select the desired I/O x0rrrwww
configuration, then ensure that the device number, data xrrr0www
set (SYS1.PARMLIB or SYS1.IPLPARM), LOADxx
member, and I/O configuration were selected. To identify the NIP module, see the explanation for wait
state X'032'.
Source: Input/output supervisor (IOS)
System action: The system enters a non-restartable
wait state.
032
Operator response: This is probably a hardware
Explanation: A module required for nucleus error. ReIPL the system. If the error persists, contact
initialization (NIP) is missing from the SYS1.NUCLEUS hardware support. Provide the number of the IPL device
data set. where the I/O error occurred and the contents of the
The reason code identifies the missing module. You can wait state PSW.
determine the name of the missing module by Source: Nucleus initialization program (NIP)
appending the last 2-digits of the reason code after
IEAVNP. For example, if the reason code is 003, the
missing module is IEAVNP03. 035
Exceptions are 7D4, 7E1, and 7E7, as follows: Explanation: During system initialization, the system
could not find an entry point in the nucleus. The system
Reason Code Module in Component loaded one of the following:
(hex) SYS1.NUCLEUS v An incomplete nucleus
7D4 IEAVNIPM NIP v An incomplete I/O configuration
7E1 IEAVNPX1 NIP
v Both an incomplete nucleus and an incomplete I/O
7E7 IEAVNIPX NIP
configuration
System action: The system enters wait state X'035'.
The reason code rrr can appear in the right-most four
The system places message IEA084W in the initial
bytes of the wait state program status word (PSW). The
program load (IPL) write to operator (WTO) buffer.
wait state PSW can appear in either of the following
formats: Operator response: Do the following as soon as
x0rrrwww possible to find the WTO buffer and locate message
xrrr0www IEA084W in the buffer. Do not write a stand-alone dump
before doing this procedure, since the dump might
System action: The system enters a non-restartable overlay storage.
wait state.
1. Using the hardware Alter/Display facility, read the
Operator response: Record the contents of the wait real address in central storage at X'14'. This
state PSW and notify the system programmer. If the address points to the IPL diagnostic area.
system programmer requests it, obtain a stand-alone 2. Add X'28' to the address at real X'14', and also read
dump. this as a real address in central storage. The result
System programmer response: If no modules are is the 31-bit virtual address of the IPL vector table
missing from the data set, search problem reporting (IVT). Henceforth, all addresses are 31-bit virtual
databases for a fix for the problem. If no fix exists, and you must switch to displaying Primary
contact the IBM Support Center. Provide the Virtual Storage to display remaining storage
stand-alone dump. locations.
3. Add X'E0' to the IVT address. The result is the
Note to IBM Support Center: The source code for
31-bit address of the IVTMQHP field. IVTMQHP
module IEADRIMS contains the correspondences
contains the address of the message queue header
between module names and components.
(MQH).
Source: Nucleus initialization program (NIP) 4. MQH+X'0' contains the address of the oldest
message queue element (MQE) available. The
033 message text for the oldest MQE begins at
MQE+X'8'.
Explanation: An I/O error occurred in build link-list 5. Use MQE+X'0' of the oldest MQE to find the MQE
request (BLDL macro) processing for a required nucleus of the next oldest message. Again, the message text
initialization program (NIP) module. for this MQE begins at MQE+ X'8'.
The reason code rrr identifies the missing module. The
Chapter 3. Wait State Codes 357
037 • 03A
6. Repeat this sequence (using MQE+X'0' of the
038
current MQE to locate the next MQE), until the
message text for the appropriate message is Explanation: The operating system cannot initialize
displayed. itself because there is not enough central storage. One
of the following is true:
Notify the system programmer, providing the texts of the
v There are not enough usable online frames
IEA084W messages. If the system programmer
v There are not enough usable contiguous frames
requests it, obtain a stand-alone dump. Then reIPL the
system, using a different nucleus member, if possible. Operator response: Notify the system programmer.
System programmer response: Do the following: System programmer response: Ensure that there is
1. Look in the stand-alone dump for message enough central storage available for IPL processing.
IEA084W. Note the entry point given in the message You may have to reduce the number of optional system
text. facilities selected for this system configuration. Then ask
2. Use the IEHLIST program to print the the operator to IPL the system.
SYS1.NUCLEUS directory.
Source: Auxiliary storage manager (ASM), initial
3. Search problem reporting databases for a fix for the
program load (IPL), and nucleus initialization program
problem. If no fix exists, call the IBM Support
Center. Provide the stand-alone dump and the
SYS1.NUCLEUS directory listing. 039
Source: Input/output supervisor (IOS) Explanation: The system could not mount a direct
access volume because the mount request conflicted
with another volume. One of the following occurred:
037
v Both volumes were required by the system.
Explanation: The data space control block (DSCB) for
v Both volumes had the same volume serial.
logrec, SYS1.SVCLIB, SYS1.PARMLIB, or
SYS1.LINKLIB could not be successfully read from the v The volume to be mounted required a different device
volume where the data set resides for one of the type than that containing the online volume.
following reasons: v The system could not find a proper device on which
v The data set does not exist on this volume. to mount the volume.
v An unrecoverable input/output (I/O) error occurred System action: The system enters wait state X'039'.
during the attempt to read the related data space
control block (DSCB). System programmer response: If any IGGNxxx
messages are issued with this wait state code, perform
v An error occurred during nucleus initialization the system programmer response for these messages.
program (NIP) OPEN processing. Otherwise, change the volume where one of the two
data sets resides. Update the catalogue to contain the
Register 1 contains a pointer to the input/output buffer volume of the moved data set.
(IOB) for the failing I/O operation (EXCP). Diagnostic
messages explaining the reason for the wait state and Source: Input/output supervisor (IOS)
identifying the name of the data set involved precede
the system wait. 03A
Operator response: Report this wait state code and Explanation: An error occurred during an attempt to
the diagnostic messages that precede it to the system build the link pack area (LPA) during a cold start.
programmer.
System action: The system issues message
System programmer response: If any IGGNxxx IEA304W to identify the error. The system may also
messages are issued with this wait state code, perform issue message IEA353I and/or IEA354I.
the system programmer response for those messages.
Otherwise, ensure that the data set is not cataloged Operator response: Report this wait state code and
with an esoteric device name. Correct the error that the preceding diagnostic messages to the system
caused the DSCB read I/O operation. Ask the operator programmer.
to reIPL the system.
If requested by the system programmer, obtain a
If the error recurs and the program is not in error, stand-alone dump.
search problem reporting databases for a fix for the
System programmer response: See the programmer
problem. If no fix exists, contact the IBM Support
response for message IEA304A. Correct the conditions
Center.
that caused the LPA cold start to fail. Ask the operator
Source: Logrec to reIPL the system.
If the error recurs and the program is not in error,
search problem reporting databases for a fix for the
358 z/OS V1R10.0 MVS System Codes
03B • 03E
problem. If no fix exists, contact the IBM Support 02 The PLPA data set is full, duplexing is not
Center. Provide the stand-alone dump. active, and the common data set is
unavailable.
Source: Contents supervision (CSV)
03 The common data set is full, duplexing is not
active, and the PLPA data set is unavailable.
03B
04 The duplex data set is full, and both the PLPA
Explanation: A module required for continued system
and common data sets are unavailable.
operation cannot be found in the system link pack area
(LPA). System action: During IPL, the system issues
message IEA935W, then enters this wait state. After
System action: The system may issue message
IPL, the system issues message ILR008W, then enters
IEA363I to indicate which module could not be found.
this wait state, unless all the local page data sets were
The system enters a non-restartable wait state.
unusable; in that case, the system does not issue a
Operator response: Report this wait state code to the message before entering this wait state.
system programmer and save the console listing.
Operator response: Notify the system programmer.
System programmer response: Examine the console ReIPL the system, specifying larger page data sets or
listing and look for message IEA363I to determine the additional page data sets.
name of the missing module. Execute the IEHLIST
System programmer response: Do one of the
utility program to obtain a directory listing of the
following:
SYS1.LPALIB data set. Examine this list to determine
v Redefine spaces to conform with the description
which required system modules are missing. The
provided in paging planning specifications. Ask the
missing modules should then be copied into
operator to reIPL with the CLPA option.
SYS1.LPALIB from the starter system libraries or from a
v Provide additional paging spaces and make them
similar back-up source. Ask the operator to reIPL the
available through either the PAGE parameter or the
system and add the missing module to the LPA either
IEASYSxx parmlib member during reIPL
by requesting an LPA cold start or by using the MLPA or
v After additional paging spaces are added and the
FIX options.
system is re-IPLed, issue the D ASM command to
If the problem recurs and the program is correct, search monitor the available paging space to help prevent a
problem reporting databases for a fix for the problem. If reoccurrence of the wait state condition.
no fix exists, contact the IBM Support Center. Provide
Source: Auxiliary storage manager (ASM)
the contents of the wait PSW available.
Source: Contents supervision (CSV)
03D
Explanation: When the nucleus initialization program
03C
was running, an error occurred while the system was
Explanation: The auxiliary storage manager (ASM) building common area page tables. There may not be
found that not enough auxiliary storage space is enough central storage available to initialize the system.
available for system operation:
System action: The system may issue message
During IPL IEA907W. The system enters wait state X'03D'.
Either the needed number of page data sets was
Operator response: Notify the system programmer.
not specified or ASM has detected a problem with a
required page data set. System programmer response: Increase the amount
of available central storage.
After IPL
ASM has run out of usable auxiliary storage for the Source: Virtual storage management (VSM)
pageable link pack area (PLPA), common, or local
page data sets. Either all the local page data sets
03E
were full or damaged, or the PLPA, common, or
duplex data set was full or damaged. Explanation: The auxiliary storage manager (ASM)
determined that there were not enough slots to back
A reason code identifies the error: master scheduler initialization.
Code Explanation System action: The system ends IPL.
00 The cause of the error cannot be determined Operator response: Notify the system programmer.
because of an error in recovery processing. ReIPL the system, specifying larger page data sets or
additional page data sets, as indicated by the system
01 The last local page is full, so there is
programmer.
insufficient local paging space.
System programmer response: Increase the amount
Chapter 3. Wait State Codes 359
03F • 046
of auxiliary storage for system operation.
044
Source: Auxiliary storage manager (ASM)
Explanation: During nucleus initialization program
(NIP) processing, a machine check occurred on a
03F central processor.
Explanation: A program invoked a nucleus The right-most four bytes of the program status word
initialization program (NIP) function incorrectly. (PSW) have the following format:
System action: The system enters a non-restartable xaaa0www
wait state.
where:
Operator response: If the system programmer
requests it, obtain a stand-alone dump. x Irrelevant information.
System programmer response: If the problem recurs aaa The logical address of the central processor on
or if the program is correct, search problem reporting which the machine check occurred.
databases for a fix for the problem. If no fix exists, www The wait state code.
contact the IBM Support Center. Provide the
stand-alone dump. System action: The system issues messages about
the problem. The system enters a non-restartable wait
Source: Nucleus initialization program (NIP) state.
Operator response: This is probably a hardware
040 error. ReIPL the system. If the error persists, configure
Explanation: The system abended a task during the failing central processor offline. This action requires
nucleus initialization program (NIP) processing. a power-on-reset. Contact hardware support.
The right-most four bytes of the program status word Source: Nucleus initialization program (NIP)
(PSW) have the following format:
x0cccwww 045
Explanation: While initializing the recovery termination
where:
manager (RTM), the nucleus initialization program (NIP)
x Irrelevant information. requested cell pool storage in the system queue area
(SQA). The request failed. System initialization cannot
ccc A hexadecimal abend code indicating the continue.
reason for the failure.
System action: The system may issue message
www The wait state code. IEA897I.
System action: The system issues message Operator response: If requested by the system
IEA303W. The system enters a non-restartable wait programmer, obtain a stand-alone dump. Then try again
state. to IPL the system.
Operator response: Record the wait state PSW and System programmer response: Search problem
report the problem to the system programmer. If the reporting databases for a fix for the problem. If no fix
system programmer requests it, obtain a stand-alone exists, contact the IBM Support Center. Provide the
dump. stand-alone dump.
System programmer response: See the system Source: Recovery termination manager (RTM)
programmer response for the abend code displayed in
message IEA303W.
046
The abend SVC entry in the system’s SVC table
contains the address of a trap routine in NIP, and not Explanation: During nucleus initialization program
the address of the abend SVC. The registers (0 through (NIP) processing, an unexpected program check
15) at the time of the abend SVC request are found in occurred.
the area pointed to by field NVTDIAGA (mapped by
System action: The system enters a non-restartable
macro IHANVT).
wait state.
If the problem persists, search problem reporting
Operator response: Notify the system programmer. If
databases for a fix for the problem. If no fix exists,
the system programmer requests it, obtain a
contact the IBM Support Center. Providing the contents
stand-alone dump.
of the wait state PSW.
System programmer response: Search problem
Source: Nucleus initialization program (NIP)
reporting databases for a fix for the problem. If no fix
360 z/OS V1R10.0 MVS System Codes
04A • 053
exists, contact the IBM Support Center. Provide the Center. Provide the stand-alone dump the logrec error
stand-alone dump. records.
Source: Nucleus initialization program (NIP) Source: Alternate CPU recovery (ACR)
04A 052
Explanation: A time-of-day (TOD) clock on one of the Explanation: Alternate CPU recovery (ACR)
central processors is in error. The clock must be set to encountered an unrecoverable error while recovery was
avoid generating a machine check later in nucleus in progress for another processor. This is probably a
initialization program (NIP) processing. hardware error.
System action: Every central processor with a clock System action: The system:
that needs setting will enter restartable wait state v Issues message IEA857W
X'04A'.
v Writes a logrec error record for the failed processor
Operator response: Perform restart function, then v Places all processors in a wait state X'052'
press the TOD ENABLE and ALT keys at the system
console to set the clock. IPL will continue. Operator response: Look at accompanying message
IEA857W and the logrec error record to identify the
Source: Nucleus initialization program (NIP) error.
If message IEA857W indicates that this is a hardware
050 error, remove the failing hardware from the system, or
Explanation: The system determined that alternate remove the system with the failure from the complex.
CPU recovery (ACR) was recursively invoked. Then reIPL the other systems. Contact hardware
support.
System action: The system issues message
BLW007W. Then the system enters disabled wait state Otherwise, report the problem to system programmer.
X'050'. System programmer response: Search problem
Operator response: Retain the SYS1.LOGREC error reporting databases for a fix for the problem. If no fix
records. Take a stand-along dump and reIPL the exists, contact the IBM Support Center. Provide the
system. Contact the system programmer. logrec error record and the text of message IEA857W.
System programmer response: Search the problem Source: Alternate CPU recovery (ACR)
reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the 053
stand-alone dump and the SYS1.LOGREC error
records. Explanation: A program requested processing by
Program Call/authorization (PC/AUTH) service or a
Source: Loadwait/Restart program call linkage service. An error prevented
PC/AUTH from processing the macro normally. The
051 system records the registers in field SDWAGRSV in the
system diagnostic work area (SDWA).
Explanation: Alternate CPU recovery (ACR)
encountered an unrecoverable error while recovery was Register 15 contains a hexadecimal reason code in the
in progress for another processor. ACR attempted to form xxyy, where xx identifies the macro that was
recover but was unsuccessful. This is probably a issued and yy identifies the error. See the system
software error. programmer response for an explanation of the reason
codes.
System action: The system:
System action: The system abends the program that
v Issues message IEA857W
issued the macro, unless PC/AUTH requests a retry.
v Tries to write a logrec error record for the failed The system writes an SVC dump and a logrec data set
processor error record.
v Places all processors in a wait state X'051'
System programmer response: Look at the
Operator response: If requested by the system explanation of the reason code. If you receive one of
programmer, obtain a stand-alone dump. ReIPL the the reason codes below, do the following:
system. v For reason code X'xx97': Look in the SDWA variable
System programmer response: Look at recording area (SDWAVRA) for the original abend
accompanying message IEA857W to identify the error. If and reason code and continue diagnosis with that
a search of the program reporting databases shows no abend.
existing fix, report the problem to the IBM Support
Chapter 3. Wait State Codes 361
054 • 055
v For reason code X'xx98': Look at message IEA139E, and you must switch to displaying Primary
which PC/AUTH issued at the time of the original Virtual Storage to display remaining storage
failure. locations.
v For reason code X'xx99': Look in the SDWA variable 3. Add X'E0' to the IVT address. The result is the
recording area (SDWAVRA) for a PC/AUTH control 31-bit address of the IVTMQHP field. IVTMQHP
block that is not valid. contains the address of the message queue header
v For reason code X'0112': Change the application (MQH).
program to use fewer linkage indexes (LXs) or 4. MQH+X'0' contains the address of the oldest
change the limit of system LXs with the NSYSLX message queue element (MQE) available. The
parameter in the IEASYSxx parmlib member. message text for the oldest MQE begins at
MQE+X'8'.
If you cannot correct the problem, search problem 5. Use MQE+X'0' of the oldest MQE to find the MQE
reporting data bases for a fix for the problem. If no fix of the next oldest message. Again, the message text
exists, contact the IBM Support Center. Provide the for this MQE begins at MQE+ X'8'.
SVC dump, including the system trace table, and the
6. Repeat this sequence (using MQE+X'0' of the
logrec data set error record.
current MQE to locate the next MQE), until the
message text for the appropriate message is
The reason codes in Register 15 are: displayed.
Code Explanation If the system programmer requests it, obtain a
1416 The program incorrectly modified either the stand-alone dump.
system function table (SFT) or extended System programmer response: Link edit the nucleus
system vector table (SVTX). The sum of the again using the SCTR option.
highest extended linkage index (LX) value (an
LX value above 2047) in the SFT and the If the problem recurs, have the operator retrieve
value in the SVTXNSBLX field of the SVTX is message IEA089W from the WTO buffer. Translate the
greater than decimal 16383, which it should not text of message IEA089W from hexadecimal into
be. Register 2 contains the highest extended EBCDIC. The translated message text will show which
LX value in the SFT. Register 3 contains the module or member was in error.
value in the SVTXNSBLX field.
If the member identified in message IEA089W belongs
Source: Program Call/authorization (PC/AUTH) to IBM, search problem reporting databases for a fix for
the problem. If no fix exists, contact the IBM Support
Center. Provide a stand-alone dump.
054
Source: Initial program load (IPL)
Explanation: The system detected an error with a
member being loaded into the dynamic address
translation (DAT)-on nucleus region during system 055
initialization.
Explanation: The initial program load (IPL) program
If bits 36 through 43 in the wait state program status was unable to locate a necessary member in the
word (PSW) contain reason code X'1', the member SYS1.NUCLEUS data set.
being loaded contained more than one control section
The right-most four bytes of the program status word
(CSECT). The member was not link-edited with the
(PSW) have the following format:
SCTR option.
xrr00www
System action: The system issues message
IEA089W to the IPL WTO buffer to identifies the where:
member. The system enters a non-restartable wait
state. x Irrelevant information.
Operator response: If the system programmer rr A hexadecimal reason code indicating the
requests, do the following to find the WTO buffer and reason for the failure.
locate message IEA089W: www The wait state code.
1. Using the hardware Alter/Display facility, read the
real address in central storage at X'14'. This The reason code (rr) is one of the following:
address points to the IPL diagnostic area.
01 IPL could not find a DAT-off nucleus module.
2. Add X'28' to the address at real X'14', and also read
(DAT is the acronym for dynamic address
this as a real address in central storage. The result
translation.)
is the 31-bit virtual address of the IPL vector table
(IVT). Henceforth, all addresses are 31-bit virtual 02 IPL could not find a DAT-on nucleus module.
362 z/OS V1R10.0 MVS System Codes
056
04 IPL could not find one or more required module IEA086W from the IPL WTO buffer and translate it from
list tables (MLT) in SYS1.NUCLEUS. hexadecimal into EBCDIC. The translated message text
will show which module or member was not found in
05 IPL could not find a module required for IPL
SYS1.NUCLEUS:
processing. This reason code indicates that
MVS is not properly installed. v If memname is IEANUC0x, IEANUC1x, or
IEANUC2x, make sure that x is the correct identifier
06 IPL could not find a DAT-on nucleus module. for the nucleus you need. Specifically, if memname is
System action: For reason codes X'01' through X'04', IEANUC1x or IEANUC2x, make sure both that x
IPL writes one or more IEA086W messages in the IPL refers to the correct IEANUC0x and that the
WTO buffer. The system enters a non-restartable wait corresponding IEANUC1x or IEANUC2x exists. For
state. example, if x is 5 (you are defining an alternate
nucleus named IEANUC05), you also need to create
For reason code X'06', IPL writes one or more IEA086W the corresponding IEANUC15 and IEANUC25
messages in the IPL WTO buffer. The system enters a members.
restartable wait state. If x is incorrect, ask the operator to reIPL the system
Operator response: For reason code X'01', if you and specify the correct identifier for the nucleus on
selected an alternate I/O configuration ensure that you the SYSCTL frame load parameter.
correctly entered the alternate I/O configuration identifier v If memname is a member name other than
(xx) through the console frame or at storage location IEANUC0x, IEANUC1x, and IEANUC2x, reason code
9-10. ReIPL the system. If the error persists, notify the X'04' identifies the module as an MLT, and reason
system programmer. code X'02' or X'06' indicates either a nucleus device
support module, a nucleus extension module, or a
For reason codes X'02' and X'06', make sure that the
module specified on an INCLUDE statement in a
load parameter fifth and sixth digits are correct.
NUCLSTxx member (identified on the NUCLST
For reason code X'01', X'02', X'04', and X'06', do the statement in the LOADxx member).
following to find the WTO buffer and locate message If the member is a module specified on an INCLUDE
IEA086W in the buffer: statement, verify that the module was specified
1. Using the hardware Alter/Display facility, read the correctly.
real address in central storage at X'14'. This If the member is an MLT or a nucleus device support
address points to the IPL diagnostic area. module, find the MLT name and the corresponding
2. Add X'28' to the address in X'14', and also read this user information module (UIM) name in the MVS
as a real address in central storage. The result is device report from HCD. If the UIM was
the 31-bit virtual address of the IPL vector table installation-provided:
(IVT). Henceforth, all addresses are 31-bit virtual – Verify that the UIM logic is correct and that the
and you must switch to displaying Primary UIM provided the correct MLT name.
Virtual Storage to display remaining storage
– Make sure the SYS1.NUCLEUS directory contains
locations.
a directory entry for the MLT.
3. Add X'E0' to the IVT address. The result is the
31-bit address of the IVTMQHP field. IVTMQHP If the UIM was not installation-provided, determine
contains the address of the message queue header which product contains the member and why the
(MQH). member was not installed in SYS1.NUCLEUS.
4. MQH+X'0' contains the address of the oldest
message queue element (MQE) available. The If the reason code is X'05' or if you cannot solve the
message text for the oldest MQE begins at problem, search problem reporting databases for a fix
MQE+X'08'. for the problem. If no fix exists, contact the IBM Support
Center. Provide the text of accompanying message
5. Use MQE+X'0' of the oldest MQE to find the MQE IEA086W if issued.
of the next oldest message. Again, the message text
for this MQE begins at MQE+ X'08'. Source: Initial program load (IPL)
6. Repeat this sequence (using MQE+X'0' of the
current MQE to locate the next MQE), until the 056
message text for the appropriate message is
displayed. Explanation: DFP encountered a terminating error
during NIP initialization. See message IGW008D for
For all reason codes, notify the system programmer. For further information.
reason codes X'01' through X'04' and X'06', provide the
text of message IEA086W. If the system programmer System action: System is in a disabled wait state
requests it, obtain a stand-alone dump. without restart capability.
System programmer response: For reason codes Operator response: Report this wait state code to the
X'01' through X'04' and X'06', get the text of message system programmer.
Chapter 3. Wait State Codes 363
059 • 05D
Application Programmer Response: See message The pointer to the master catalog should be in the
IGW008D for further information. SYSCATLG or SYSCATnn member in the
SYS1.NUCLEUS data set.
System programmer response: Provide software
support personnel with console listing and stand alone System action: The system issues messages about
dump. Also include a copy of message IGW010I in the the problem. The system enters a non-restartable wait
console listing. state.
Source: DFSMSdfp Operator response: ReIPL the system. If the problem
persists, notify the system programmer.
059 System programmer response: Ask the operator to
IPL a different system. Use it to determine if the
Explanation: During nucleus initialization program
SYSCATLG or SYSCATnn member exists in the
(NIP) processing, a build link-list request (BLDL macro)
SYS1.NUCLEUS data set and is in the correct format:
returned an undefined return code. System initialization
cannot continue. v Run the IEHLIST utility with LISTPDS to list the
directory of the SYS1.NUCLEUS data set.
System action: The system enters a non-restartable
v Run the IEBPTPCH utility to print the SYSCATLG or
wait state.
SYSCATnn member of SYS1.NUCLEUS.
Operator response: Notify the system programmer. If
Add the SYSCATLG or SYSCATnn member to the
the system programmer requests it, obtain a
SYS1.NUCLEUS data set.
stand-alone dump.
System programmer response: Search problem If the problem persists, search problem reporting
reporting databases for a fix for the problem. If no fix databases for a fix for the problem. If no fix exists,
exists, contact the IBM Support Center. Provide the contact the IBM Support Center.
stand-alone dump.
Source: DFSMSdfp
Source: Nucleus initialization program (NIP)
05D
05A
Explanation: During initialization, DFP could not find a
Explanation: Alternate CPU recovery (ACR) data set control block (DSCB) for the master catalog or
attempted to remove the last standard CP. There must could not read the DSCB from the volume pointed to by
be at least one standard CP online in order for the the SYS1.NUCLEUS data set.
system to run.
For an integrated catalog facility (ICF) master catalog,
System action: The system issues message NIP could not read the DSCB for the VSAM volume
IEA856W and enters a non-restartable wait state. data set (VVDS) of the volume that it required. For
example, a page data set is specified that resides on a
Operator response: Notify the system programmer.
different volume than the master catalog, and the
System programmer response: The system has lost volume containing the page data set has a damaged
access to the last standard CP and can not run in this VVDS.
mode. If the CP was lost due to hardware failure, it will
Possible causes include:
require the LPAR to be reconfigured to have at least
one usable standard CP. If the CP was taken offline due v Hardware errors
to a software error, then reIPL the system. v The wrong volume is mounted
Source: Alternate CPU recovery (ACR) v The pointer to the master catalog is incorrect in the
SYSCATLG member of SYS1.NUCLEUS data set.
05C System action: The system issues messages about
the problem. The system enters a non-restartable wait
Explanation: During nucleus initialization program state.
(NIP) processing, the pointer to the master catalog
could not be obtained from the SYS1.NUCLEUS data Operator response: ReIPL the system. Notify the
set. Possible causes are: system programmer.
v I/O errors while attempting a build link-list request System programmer response: IPL a different
(BLDL macro) to find the member. system. Use it to determine whether the volume table of
v Member not found. contents (VTOC) of the volume containing the master
catalog or the VVDS are correct:
v I/O errors attempting to read records from the
member. v Run the IEHLIST utility with LISTVTOC FORMAT to
format the VTOC for the volume associated with the
problem.
364 z/OS V1R10.0 MVS System Codes
05E • 05F
v Run the IEBPTPCH utility to print the SYSCATLG
05F
member of SYS1.NUCLEUS.
Explanation: DFP processing found an error related to
If the problem persists, contact hardware support.
the master catalog. The problem was caused by one of
Source: DFSMSdfp the following:
v The catalog information found during IPL was
05E incorrect. This information can be supplied by
SYSCATLG or SYSCATxx members of the
Explanation: An I/O error occurred while the system SYS1.NUCLEUS data set, or in the LOADxx
attempted to read the master catalog self-describing members of the SYS1.PARMLIB or SYSn.IPLPARM
records. data sets.
The wait state can be caused by one of the following: v Either the SYSCATLG member or an alternate
SYSCATxx member of SYS1.NUCLEUS contains
v The VVDS entry for the master catalog is damaged.
incorrect data.
v The master catalog name, volume serial or both in
v Either the master catalog’s VSAM volume record
the SYSCATxx member of SYS1.NUCLEUS is
(VVRs) or its first ten records have been improperly
incorrect.
written over or damaged.
v A hardware error was detected.
v A catalog was moved to a different volume serial and The first ten records in the master catalog data set
the SYSCATxx member was not updated. describe the master catalog itself. They are the catalog
| v The SYSCAT entry of LOADxx produced an incorrect entry for the master catalog.
| master catalog name. System action: The system issues messages about
The first ten records in the master catalog data set the problem. The system enters a non-restartable wait
describe the master catalog itself. They are the catalog state.
entry for the master catalog. Operator response: Notify the system programmer.
System action: The system enters a non-restartable After the system programmer corrects the error in the
wait state. SYSCATLG member or alternate SYSCATxx member,
reIPL the system.
Operator response: ReIPL the system and report this
wait state code to the system programmer. System programmer response: Check to see if the
catalog information was correctly specified. This
System programmer response: Do the following: information will be taken from the first of these places it
v Check the the master catalog name and volume is found during IPL:
serial in the SYSCATxx member of the 1. The SYSCAT parameter found in the specified
SYS1.NUCLEUS. If the name or volume serial is LOADxx member of the first SYS0.IPLPARM
incorrect, correct it and have the operator reIPL the through SYS9.IPLPARM data set found on the IODF
system. volume.
v If the master catalog name is correct, look for a 2. The SYSCAT parameter found in the specified
problem with the VVDS entry for the master catalog. LOADxx member of SYS1.PARMLIB on the IODF
v If neither the master catalog name nor the VVDS volume.
entry for the master catalog are in error, this is 3. The SYSCAT parameter found in the specified
probably a hardware error. Contact hardware support, LOADxx member of SYS1.PARMLIB on the system
providing one of the following: residence volume.
– Run the IEBPTCH utility to print the cataloged 4. The specified SYSCATxx member of the
procedure. SYS1.NUCLEUS data set used for IPL (if none is
– Issue the access method services LISTCAT specified, SYSCATLG is the default).
command to list catalog entries and information
Confirm that the data in the SYSCATLG member or
about objects defined in the catalog.
alternate SYSCATxx member, including the volume
serial number and the device type, are correct. To look
The master catalog must either be recreated or restored
at the master catalog, run the IEBPTPCH utility to print
to the proper volume after the damage to that volume is
the SYS1.NUCLEUS data set.
corrected.
Source: DFSMSdfp If the member is correct, either restore the master
catalog to the proper volume or recreate it.
If the problem persists, search problem reporting
databases for a fix for the problem. If no fix exists,
contact the IBM Support Center.
Chapter 3. Wait State Codes 365
060 • 064
Source: DFSMSdfp 3. After the system issues message IOS201E, do one
of the following:
060 v If the IOACTION STOP command was
successful, enter the IOACTION RESUME
Explanation: While saving or rebuilding the pageable command.
link pack area (PLPA) or extended PLPA (EPLPA), the
v Otherwise, restart sharing processors.
auxiliary storage manager (ASM) detected an error in
processing external page table entries.
For errors on channel paths with at least one non-DASD
System action: The system issues message or non-assignable device:
IEA943W. The system ends the IPL. 1. Stop sharing processors to prevent I/O activity to the
Operator response: Notify the system programmer of shared devices.
this wait state. ReIPL, specifying the CLPA system 2. Restart the system that has the error.
parameter. For a hardware error, contact hardware 3. After the system issues message IOS201E, restart
support. sharing processors.
System programmer response: Try to determine the
cause of the problem. Check for hardware and software See z/OS Problem Management for further information
errors. about restarting the system.
Source: Auxiliary storage manager (ASM) Source: Input/output supervisor (IOS)
061 063
Explanation: The auxiliary storage manager (ASM) Explanation: The nucleus initialization program (NIP)
detected an error with the time-of-day (TOD) clock while was unable to obtain storage. The probable cause of
processing the store clock (STCK) instruction. this error is that insufficient system queue area (SQA)
was available to provide the options requested for this
System action: The system issues message IPL. Another possibility is a system error resulting in
IEA945W. The system ends IPL. excessive demands on the NIP region.
Operator response: Correct the TOD clock. ReIPL the Operator response: Notify the system programmer.
system. If the problem persists, contact hardware
support to repair the clock. System programmer response: If the request was for
SQA after NIP processes the SQA parameter, the
Source: Auxiliary storage manager (ASM) problem can be corrected by specifying a larger value
on the ’SQA’ parameter. However, the problem can
062 occur before NIP processes the SQA parameter.
Explanation: An error occurred on one or more If the system was initialized with insufficient central
channel paths to reserved devices (such as DASD) or storage available to back the SQA requests, then it may
assigned devices (such as tapes). be necessary to increase the amount of online storage
before attempting to reIPL, or to reduce the number of
System action: The system does not use the channel optional system facilities selected for this system
path(s) until recovery is complete. Recovery waits until configuration.
the operator restarts the system.
If the problem persists, search problem reporting
The system issues message IOS201E when the I/O on databases for a fix for the problem. If no fix exists,
other processors that share devices can be started. contact the IBM Support Center.
Operator response: The correct response varies, Source: Auxiliary storage manager (ASM)
depending on whether there are non-DASD devices on
any channel paths where an error occurred.
064
For errors on channel paths with DASD or assignable
devices only: Explanation: During nucleus initialization program
(NIP) processing, NIP detected a software or hardware
1. Enter the IOACTION STOP command to prevent
error. An attempt was made to enter the recovery
other processors that share devices from initiating
termination manager (RTM). This was trapped by NIP
I/O. If the IOACTION STOP command fails, stop
because the system is in a variable state of initialization
sharing processors to prevent I/O activity to the
and, in particular, RTM is not fully initialized.
shared devices.
2. After the IOACTION STOP command is successful The right-most four bytes of the program status word
or sharing processors have been stopped, restart (PSW) have the following format:
the system that has the error. x0rrrwww
366 z/OS V1R10.0 MVS System Codes
064
where: 00D A module specified the ITERM option on the
CALLRTM macro.
x Irrelevant information.
00E A module specified the SABEND option on the
rrr A hexadecimal reason code indicating the
CALLRTM macro.
reason for the failure.
00F A call to ABTERM processing was issued with
www The wait state code.
RETRY=NO.
The reason code (rrr) is one of the following: 010 A call to cross-memory ABTERM processing
was issued with RETRY=NO.
001 A module branched to abnormal ending
processing. System action: The system issues messages about
the problem. The system may issue message IEA304A.
002 A dynamic address translation (DAT) error The system enters a restartable wait state.
occurred.
Operator response: Do one of the following:
003 The operator pressed the RESTART key
instead of the time-of-day (TOD) key. v For table entry code X'003' reIPL the system.
v For table entry code X'004', do the following:
004 A machine check occurred. This can be caused
by: – Use the hardware Problem Determination facilities
to see if any unexpected events occurred during
v An I/O interrupt from a device that was not the IPL process.
defined in the I/O configuration program
(IOCP). The channel subsystem presents – Check that the system is using the correct I/O
the interruption as a machine check. configuration data set (IOCDS).
v The system is changing the state of a – Notify the system programmer and provide the
resource during system initialization. text of the message.
005 A Supervisor Call (SVC) instruction was issued Do not:
in an incorrect mode. However, this is not – Detach, attach, or define any I/O service during
usually the actual error, because it is common system initialization.
for system routines to issue an abend while – Configure on or offline any channel path identifiers
holding a lock. (CHPID) to the logical partition where the system
Code X'05' can occur when: is initialized if the system is running in logically
partitioned (LPAR) mode.
v NIP is reading from SYS1.PARMLIB
v For table entry code X'009', try restarting the system,
v NIP is trying to process an incorrect load specifying CLPA in the reply to accompanying
module message IEA101A. Table entry code X'009' may
v I/O errors occurred on the system residence occur on a warm or quick start if the previous cold
volume start failed before or during master scheduler
initialization.
006 A paging I/O error occurred.
v For other entry codes, check the READ/WRITE
007 A call to abnormal ending processing was switch on direct access storage devices (DASD)
issued without providing an address space before reporting this wait state code to the system
identifier (ASID). programmer.
008 A request for memory ending occurred.
If the system programmer requests it, obtain a
009 A program check occurred. Accompanying stand-alone dump.
message IEA304W further explains this wait
state and entry code. If the message does not System programmer response: Do the following
appear on the console, you can find the before contacting the IBM Support Center:
message in the wait state message area v For table entry code X'005', determine if an SVC 13
(WSMA). The WSMA is described in z/OS was the last SVC issued by looking at the SVC OLD
MVS Data Areas, Vol 5 (SSAG-XTLST). PSW or the trace table in a stand-alone dump. If this
is the case, register 1 in the trace table contains the
00A NIP called the alternate CPU recovery (ACR)
abend codes and register 15 contains the reason
component.
code. The abend code may indicate which SVC
00B A call to cross-memory abend processing was issued the abend. If it does, the trace table may show
issued with the address space identification the module that issued the SVC.
(ASID) provided. If SVC 13 was not the last SVC issued, then it is a
00C A routine entered RTM holding a cross memory true SVC error. The problem could be:
local (CML) lock.
Chapter 3. Wait State Codes 367
065 • 06F
– A module is incorrectly issuing an SVC while 2. Enters wait state X'06F' because it cannot issue
holding a lock. message IOS427A.
– A routine that was in control returned to its caller 3. Expects an operator action, but does not prompt the
without releasing a lock. In this case, the operator for a reply.
SVC-issuer is not at fault.
Operator response: Do the following:
v For table entry code X'009', the program check OLD
1. Find the address of the error information by using
PSW indicates the type of exception and where it
the hardware Alter/Display facility to display the
occurred. The registers at the time of the exception
contents of location X'40C'. Record the first 4 bytes
are saved at displacement X'48' into the logical
of data at this location.
configuration communication area (LCCA). If it was a
translation exception (program interrupt code X'10' or 2. Use the hardware Alter/Display facility to display the
X'11'), location X'90' contains the address that could storage pointed to by location X'40C'.
not be translated. The system trace also contains this
information. Note: This is indirect addressing.
Search problem reporting databases for a fix. If no fix The system displays the contents of the error
exists, contact the IBM Support Center. Provide the information area:
information gathered above, including the wait state
Offset 0 The channel path identifier (or
PSW.
X'FFFF', if the CHPID could not be
Source: Nucleus initialization program (NIP) determined).
Offset 2 The device number (or X'FFFF', if
065 the device number could not be
determined).
Explanation: During nucleus initialization program
(NIP) processing, a program issued type 3 or 4 3. Use the hardware Alter/Display facility to change
Supervisor Control (SVC) instruction before these types location X'30E' to one of the following recovery
were loaded. This SVC interrupt was trapped by NIP. codes:
System action: The system enters a non-restartable Code Explanation
wait state. 00 Try to restart the device without attempting
Operator response: Notify the system programmer. If recovery. (Entering this code is the same
the system programmer requests it, obtain a as replying ’NOOP’ to message IOS427A).
stand-alone dump. If the problem persists, the system issues
message IOS427A again (or wait state
System programmer response: Search problem code X'06F' if the system cannot issue
reporting databases for a fix for the problem. If no fix IOS427A); consider entering one of the
exists, contact the IBM Support Center. Provide a other recovery codes.
stand-alone dump.
Use the Restart facility to restart the waiting
Source: Nucleus initialization program (NIP) processor.
01 Attempt to recovery access to the device
06F through an alternate channel path.
(Entering this code is the same as replying
Explanation: The system found one of the following
X'UR' to message IOS427A). Before
along a path to a device:
entering this recovery code and restarting
v An inoperative control unit
the processor, all other processors that
v A channel error
share the device you must prevent from
v An undetermined error
initiating I/O to this device by issuing the
IOACTION STOP command. If this
There is no device reservation or active I/O operation
command fails, you must stop all sharing
on the path to indicate which system owns the device.
processors to prevent I/O activity to the
shared device.
If the system could not determine the channel path
identifier and/or device number, the system substitutes Use the Restart facility to restart the waiting
X'FFFF' for the channel path identifier and/or device processor. The system might issue one of
number. the following messages:
IOS428I - the attempt to access the
System action: The system: device through an alternate channel
1. Disables the device. path was successful.
368 z/OS V1R10.0 MVS System Codes
070 • 071
IOS104I - the attempt to access the 04 The operator selected RESTART option 1 to
device through an alternate channel initiate system diagnosis and repair.
path was not successful.
08 A programming error caused the program that
was currently running to branch directly to the
After the system issues either message,
restart interruption handler.
start I/O to the shared device either by
issuing the IOACTION RESUME command 0C The operator selected RESTART option 0 on a
or by restarting the sharing processors if processor that is in a valid spin waiting for a
they were stopped in step 11. global resource held by a second processor
that is in an erroneous disabled loop. A DSGNL
02 Force the device offline. (Entering this code
RESTART command, directed to the second
is the same as replying X'BOX' to message
processor, failed.
IOS427A). The system issues message
IOS501I. Use the Restart facility to restart 10 The system started writing logrec error records
the waiting processor. after detecting an excessive spin loop
condition. The interrupted unit of work
See message IOS427A in z/OS MVS System continues to run.
Messages, Vol 10 (IXC-IZP) for additional information.
20 The system abnormally ended the program that
Source: Input/output supervisor (IOS) was causing a system excessive spin loop.
Recovery routines are not allowed to retry
because the recovery action for the spin loop
070 was TERM.
Explanation: During initial program load (IPL) 30 The system abnormally ended the program that
processing, IPL did not find enough contiguous central was causing a system excessive spin-loop
storage to satisfy a request that requires contiguous condition. Recovery routines are allowed to
storage. This is probably a hardware error. retry because the recovery action for the spin
Operator response: Check the configuration of loop was ABEND.
storage. If hardware errors have made too many frames System action: The system does one of the following:
unusable, contact hardware support. Otherwise, notify
the system programmer. v For reason code X'00', X'08', X'0C', X'20', or X'30',
the system abnormally ends the program currently
System programmer response: Make sure that running.
enough central storage is available for IPL processing. v For reason code X'00', the system might issue either
You may have to reduce the number of optional system message IEA500A or BLW004A.
facilities selected for this system configuration.
v For reason code X'04', the system detects and
Source: Initial program load (IPL) repairs, where possible, errors in critical system
areas. The system refreshes selected system control
blocks and validates and repairs selected system
071
resources. The system logs the old values of some
Explanation: Either the system or the operator refreshed control block fields in the variable recording
initiated a restart. The reason code, located in SDWA, area (VRA) of the system diagnostic work area
explains the reason for the abnormal end: (SDWA). The system writes these old values in the
logrec error record. Then the system returns control
Code Explanation
to the interrupted program.
00 One of the following occurred: v For reason code X'10', the system records the
v The operator selected RESTART option 0 to excessive spin loop in a logrec error record.
initiate the abnormal end.
Operator response: If requested by the system
v The operator replied ABEND to either programmer, set a SLIP trap to obtain a dump.
message IEA500A or BLW004A.
System programmer response: Depending on the
v The operator selected RESTART with no
reason code, do the following:
option. When no option is specified, the
system uses the default, which is option 0. Reason code X'00':
v The operator did not reply to either message Either message IEA500A or BLW004A might
IEA500A or IEA502A within 125 seconds. accompany this reason code and identify the work
that was in progress at the time of the interruption.
v The system could not determine the reason
for the restart, and uses the default, which is 1. If a logrec error record is not produced with the
option 0. abend, ask the operator to obtain an SVC
dump.
Chapter 3. Wait State Codes 369
072 • 073
2. Examine the program status word (PSW) at the v If the module is an IBM module, search
time of error in the logrec error record. The problem reporting databases for a fix for the
PSW points to the location where RESTART problem. If no fix exists, contact the IBM
was entered by the operator. If the program was Support Center. Provide the dump and the
in a loop, the PSW address will be within the logrec error record.
loop.
3. Examine the system trace table for evidence of See z/OS Problem Management for information
a loop or a wait. If a loop or a wait is about diagnosing a loop.
suspected, use the address in the PSW to Source: Loadwait/Restart
obtain the name of the looping module.
v If the module is not an IBM module, continue
diagnosis with the module. 072
v If the module is an IBM module, search Explanation: There is no more room in the work
problem reporting data bases for a fix for the space allocated to initial program load (IPL).
problem. If no fix exists, contact the IBM
System action: The system enters a non-restartable
Support Center. Provide the dump and the
wait state.
logrec error record.
System programmer response: Search problem
Reason code X'08'
reporting databases for a fix for the problem. If no fix
Determine which program branched incorrectly, as
exists, contact the IBM Support Center.
follows:
1. If a logrec error record is not produced with the Source: Initial program load (IPL)
abend, ask the operator to obtain an SVC
dump. 073
2. Look at register 14 at the time of the error. If
Explanation: Initial program load (IPL) is waiting for
the illegal branch was made by a BALR 14,15
an I/O or external interrupt.
instruction, register 14 points to the instruction
following the instruction that took the bad The right-most four bytes of the program status word
branch. If this instruction is a branch instruction, (PSW) have the following format:
then this instruction probably branched directly x0r00www
into the restart interrupt handler.
3. Use the address in register 14 to get the name where:
of the module that issued the bad branch
instruction. x Irrelevant information.
v If the module is not an IBM module, continue r A hexadecimal reason code indicating the
diagnosis with the module. reason for the failure.
v If the module is an IBM module, search www The wait state code.
problem reporting databases for a fix for the
problem. If no fix exists, contact the IBM The reason code (r) is one of the following:
Support Center. Provide the dump and the
logrec error record. 1 IPL is waiting for an I/O interrupt.
Reason code X'0C', X'10', X'20', or X'30' 2 IPL is waiting for an external interrupt.
Determine why an excessive spin condition
System action: The system enters an enabled wait
occurred, as follows:
state.
1. Get the program status word (PSW) at the time
of error as follows: Operator response: The wait time might vary
between 30 seconds and three minutes. If the system is
v For reason code X'10', X'20', or X'30', obtain
still in a wait state after three minutes, record the wait
the PSW from the logrec error record.
state PSW and inform the system programmer.
v For reason code X'0C', X'20', or X'30', ask
the operator to obtain an SVC dump. Format System programmer response: Take the following
the dump to see the PSW at the time of steps:
error. 1. Using the hardware Alter/Display facility, examine
2. Use the address in the PSW to obtain the name the reason code in bits 40 through 43 of the wait
of the module that was causing the spin. state PSW.
v If the module is not an IBM module, continue v If the reason code is X'1', the system is waiting
diagnosis with the module. for an I/O operation to complete. Continue
problem determination with step 2 on page 371.
370 z/OS V1R10.0 MVS System Codes
074
v If the reason code is X'2', a hardware problem failing path. If none of these IPL attempts succeeds,
exists. Have the operator retry the IPL. If the IPL the device is causing the problem. Contact hardware
is not successful, contact hardware support. support.
2. If the reason code is X'1', the system is waiting for Source: Initial program load (IPL)
an I/O operation to complete. This wait state
indicates that an I/O interrupt is outstanding. During
IPL, I/O is done to either the SYSRES volume or the 074
IODF volume. The IPL program issues SSCH to Explanation: Initial program load (IPL) contains a
initiate the I/O, then loads a wait PSW that is program logic error.
enabled for I/O (X'010A0000 00100073'). This PSW
remains loaded until the I/O interrupt comes in. If The right-most four bytes of the program status word
the I/O interrupt never comes in, the system remains (PSW) have the following format:
in a wait state. xrr00www
If the system is still in a wait state after three
minutes, have the operator retry the IPL. If the where:
system enters a wait state again for three minutes,
x Irrelevant information.
you need to determine whether a device or a path to
the device is causing the problem. Continue with the rr A hexadecimal reason code indicating the
next step. reason for the failure.
3. Using the hardware Alter/Display facility, read the www The wait state code.
4-byte subchannel address in central storage at
X'B8'. The subchannel number is the last two bytes
The reason code (rr) is one of the following:
(at location X'BA') of the 4-byte subchannel
identification word at location X'B8'. 01 An incorrect Supervisor Call (SVC) instruction
4. Bring up the Device Configuration Display. Enter the was issued.
2-byte subchannel number found in step 2. This 02 IPL SVC stack overflow.
displays the device number, unit address, and one
or more installed channel paths to the device for the 03 IPL SVC stack underflow.
selected subchannel number. 04 IPL received an unexpected condition code of
If there is only one channel path to the device, the 2 on a Start Subchannel (SSCH) instruction.
problem is caused either by the path or by the
device. There is no need for the system operator to 05 IPL received an unexpected condition code of
continue problem determination. Contact hardware 1 on a Test Subchannel (TSCH) instruction.
support. 06 IPL received an unexpected condition code on
If there is more than one channel path to the device, a Load Real Address (LRA) instruction.
configure offline one path at a time and attempt to Message IEA090W, which appears in the IPL
reIPL. If one of these IPL attempts succeeds, the WTO buffer, accompanies this reason code.
offline path is the failing path. If none of these IPL
07 IPL received an incorrect parameter list.
attempts succeeds, the device is causing the
problem. 08 IPL received a nonzero condition code on a
5. It is likely that the failing path is the last path used. Modify Subchannel (MSCH) instruction.
Display subchannel status information. On 09 Code was loaded from a new restart PSW.
CMOS-based processors, this is the Analyze This code will be loaded when a restart is
Subchannel Data display. Read the last path used issued on a processor that has a zero prefix
mask (LPUM) field to determine the last path used. register. The prefix register is zero when the
The LPUM field consists of 8 bits. If bit n is on, then operator attempts to do a restart too early in
CHPIDn is the last path used. For example, if the IPL or in a logically offline processor in LPAR
LPUM field shows B'01000000', bit 1 is on and the mode.
CHPID1 field identifies the last path used.
System action: The system may issue message
6. Bring up the CHPID menu and configure the last
IEA090W to the IPL WTO buffer. The system enters a
used channel path offline.
non-restartable wait state.
7. ReIPL the system.
Operator response: For a reason code other than
8. If the problem does not recur, you have identified
X'05' or X'06', notify the system programmer.
the failing path.
If the problem recurs, continue attempting to reIPL For reason code X'05', check that the devices are: not a
the system with one path configured offline. If one of secondary PPRC; not experiencing I/O errors; and not
these IPL attempts succeeds, you have identified a unavailable due to a Reserve in the control unit.
For reason code X'06', do the following to find the WTO
Chapter 3. Wait State Codes 371
075 • 076
buffer and locate message IEA090W in the buffer: www The wait state code.
1. Using the hardware Alter/Display facility, read the
real address in central storage at X'14'. This The reason code (rr) is one of the following:
address points to the IPL diagnostic area. 01 IPL could not find IRIM IEAIPL01 in the
2. Add X'28' to the address at real X'14', and also read SYS1.NUCLEUS data set. This could be
this as a real address in central storage. The result caused by:
is the 31-bit virtual address of the IPL vector table v Previous I/O error reading SYS1.NUCLEUS
(IVT). Henceforth, all addresses are 31-bit virtual
and you must switch to displaying Primary v Mismatch in IODF or IOCDS of true system
Virtual Storage to display remaining storage configuration
locations. v Device cabling error for IODF or IOCDS
3. Add X'E0' to the IVT address. The result is the 02 A module is too large; it is longer than 4096
31-bit address of the IVTMQHP field. IVTMQHP bytes.
contains the address of the message queue header
(MQH). 03 Either the delimiter for the end of the IPL
resource initialization module (IRIM) list was
4. MQH+X'0' contains the address of the oldest
encountered before IPL found all the IRIMs or
message queue element (MQE) available. The
a pre-MVS SP 4.3 IPL text was attempting to
message text for the oldest MQE begins at
IPL a system at a level of MVS SP 4.3 or
MQE+X'8'.
higher.
5. Use MQE+X'0' of the oldest MQE to find the MQE
of the next oldest message. Again, the message text 04 IPL could not find an IRIM member in
for this MQE begins at MQE+ X'8'. SYS1.NUCLEUS.
6. Repeat this sequence (using MQE+X'0' of the 05 An IRIM module is too large; it is longer than
current MQE to locate the next MQE), until the 4096 bytes.
message text for the appropriate message is
06 The IPL text on the volume used to IPL did not
displayed.
match the nucleus code resident on that
Notify the system programmer, providing the text of volume.
message IEA090W. If the system programmer requests
System action: The system enters a non-restartable
it, obtain a stand-alone dump.
wait state.
System programmer response: Search problem
Operator response: Record the wait state PSW.
reporting databases for a fix for the problem. If no fix
Notify the system programmer, and obtain a stand-alone
exists, contact the IBM Support Center. Provide the
dump, if requested.
stand-alone dump.
System programmer response: Make sure that the
For reason code X'06', provide the text of message
module is properly link-edited into SYS1.NUCLEUS.
IEA090W translated from hexadecimal into EBCDIC.
Then ask the operator to reIPL. For reason code 06 or
Reason code X'09' can also be the result of another 03 (in the case of an IPL text error), run ICKDSF to
problem. install the proper level of the IPL text on the volume
used to IPL.
For subchannel related reason codes, the IODF might
not be on the volume that the LOADPARM indicated, or Source: Initial program load (IPL)
the volume might be experiencing problems.
Source: Initial program load (IPL) 076
Explanation: During initial program load (IPL)
075 processing, the system attempted to load an IPL
resource initialization module (IRIM) or the DAT-off
Explanation: Initial program load (IPL) could not load
nucleus, but the system encountered a relocatable
a module.
address constant that is not a fullword. (DAT is the
The right-most four bytes of the program status word acronym for dynamic address translation.)
(PSW) have the following format:
System action: The system enters a non-restartable
xrr00www wait state.
where: Operator response: Notify the system programmer.
x Irrelevant information. System programmer response: Make sure that the
IRIM module is properly link-edited into
rr A hexadecimal reason code indicating the SYS1.NUCLEUS on the system residence volume.
reason for the failure.
372 z/OS V1R10.0 MVS System Codes
077 • 07C
Source: Initial program load (IPL) 3 Suppress on Protection with Virtual-Address
Enhancement is not available.
077 4 Storage-Protection Override is not available.
Explanation: The system cannot resolve the entry 5 Subspace Group support is not available.
point of a supervisor call (SVC) or extended SVC router
6 Set Address Space Control Fast support is not
(ESR) routine.
available.
Operator response: Report this wait state to the
7 Compare until Substring Equal support is not
system programmer. If requested by the system
available.
programmer, obtain a stand-alone dump.
9 Perform Locked Operation support is not
System programmer response: Make sure that the
available.
IEANUC0x module is properly link-edited. If the problem
cannot be resolved, search problem reporting A Lock Page support is not available.
databases for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the B Compression support is not available.
stand-alone dump. C PER 2 support is not available.
D String support is not available.
078
E Checksum support is not available.
Explanation: The master catalog could not be opened
successfully. Message IEC161I precedes this wait state F Move Inverse support is not available.
and identifies the specific open failure. 11 Compare and Move extended support is not
Operator response: Probable I/O error. ReIPL the available.
system and report this wait state code to the system 12 Branch and Set Authority (BSA) instruction is
programmer. not available.
Application Programmer Response: Correct the 13 Compare Swap and Purge (CSP) instruction is
error identified by message IEC161I. not available.
System programmer response: If the error recurs 14 Store System Information (STSI) instruction is
and the program is not in error, search problem not available.
reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center. 15 Extended TOD Clock facility is not available.
Source: DFSMSdfp 16 Extended Translation facility is not available.
17 LICENSE=z/OSe was specified, but you were
07B not on a 2066 machine type on a ZOSExxxx
LPAR.
Explanation: A required processor facility is not
available. The wait state reason code identifies the 18 LICENSE=z/OSe was not specified, but you
missing facility. were on a 2066 machine on a ZOSExxxx
LPAR.
The right-most four-bytes of the program status word
(PSW) have the following format: System action: The system enters a non-restartable
wait state.
xrrr0www
Operator response: Notify the system programmer.
where:
System programmer response: Upgrade the
x Irrelevant information. processor to one which supports all of the required
facilities.
rrr A hexadecimal reason code indicating the
reason for the failure. Source: Nucleus initialization program (NIP)
www The wait state code.
07C
The reason code (rrr) is one of the following:
Explanation: During system initialization an error was
1 Access register support is not available. detected in the system configuration. The error needs to
be corrected before the system will properly initialize. A
2 Immediate-and-Relative instructions are not reason code in the wait PSW explains the error:
available.
Code Explanation
Chapter 3. Wait State Codes 373
07D • 07E
01 A system was IPLed in a partition with a
07D
non-zero logical channel subsystem identifier
(CSSID). The level of z/OS installed on this Explanation: During system initialization, an error
system does not support non-zero CSSIDs. occurred when the system tried to process the
IEASYMxx parmlib member. A reason code in register
System Action: Message IEA004W
15 explains the error:
accompanies the wait state.
Code Explanation
System Programmer Response: Either IPL
the z/OS system in a logical partition with a 00 The system found a circular system symbol
CSSID of 0 or modify your I/O configuration to definition in IEASYMxx. A circular system
define this partition in CSS 0. See z/OS HCD symbol definition is one that contains another
Planning or z/OS HCD User’s Guide for system symbol that is not resolved.
information on how to associate a logical
System Action: The system issues message
partition with a logical channel subsystem.
IEA012E, which further describes the error, to
02 A system was IPLed in a partition with an the NIP console. The system enters a
logical partition identifier greater than hex F. non-restartable wait state.
The level of z/OS installed on this system does
System Programmer Response: See the
not support logical partition identifiers greater
system programmer response for message
than X'F'.
IEA012E.
System Action: Message IEA006W
04 The system found an error in IEASYMxx from
accompanies the wait state.
which it could not recover. The error occurred
System Programmer Response: Change the when the system tried to determine the
LPAR identifier assigned to the partition in the substitution text for a system symbol definition.
LPAR image profile to a number in the range of
System Action: The system issues message
X'0–F'. See PR/SM™ Planning Guide.
IEA013E, which further describes the error, to
03 More CPUs were defined for the partition than the NIP console. The system enters a
the level of z/OS installed supports. The non-restartable wait state.
system encountered a CPU address space that
Operator Response: Contact the system
is greater than the maximum allowed by this
programmer. Provide the text of message
level of z/OS. Releases before z/OS V1R6
IEA013E.
support no more than 16 CPUs. z/OS V1R6
and later releases support no more than 32 System Programmer Response: See the
CPUs. system programmer response for message
IEA013E.
System Programmer Response: Change the
number of logical CPUs defined for the Source: Nucleus initialization program (NIP)
partition in the LPAR image profile to a number
less than or equal to the number of CPUs
supported by the current installed level of 07E
z/OS. See PR/SM Planning Guide. Explanation: The system was unable to obtain
04 The system contained the following mutually storage from LSQA which was needed to process an
exclusive facilities: SVC instruction. The system loaded a wait state
because it was unable to terminate the address space
v an Integrated Facility for Applications (IFA) of the program which issued the SVC.
,and
v a CPU with the Integrated Cryptographic System action: The system enters a non-restartable
Feature. wait state and issues message IEA297W.
Operator response: Provide a stand-alone dump if
System Action: The system enters a requested by the system programmer. ReIPL the
non-restartable wait state. system.
System programmer response: The problem may be
Operator response: Contact the system
caused by a loop which causes LSQA to be exhausted.
programmer.
If the source of the problem cannot be determined,
search problem reporting databases for a fix. If no fix
System Programmer Response: Contact
exists, contact IBM support center. Provide the
hardware support.
stand-alone dump.
Source: Initial program load (IPL) and Nucleus
Source: Supervisor Control
initialization program (NIP)
374 z/OS V1R10.0 MVS System Codes
081 • 084
maintenance to be applied and the appropriate APAR to
081
apply.
Explanation: Initial program load (IPL) tried to load a
System programmer response: Read the information
module from the SYS1.NUCLEUS data set. The
regarding installation of the appropriate APAR(s).
SYS1.NUCLEUS data set or an IEANUC0x or
IEAVEDAT member occupies more than one extent.
083
System action: The system enters a non-restartable
wait state. Explanation: The system found an incorrect address
in a critical prefixed storage area (PSA) field. The
Operator response: Notify the system programmer.
damage could not be corrected by supervisor recovery.
System programmer response: Make sure that the This error is probably a software error.
SYS1.NUCLEUS data set is allocated to single extent.
The right-most four bytes of the program status word
Then ask the operator to reIPL the system.
(PSW) have the following format:
Source: Initial program load (IPL) xrrr0www
082 where:
Explanation: The system entering the sysplex is x Irrelevant information.
removed to prevent sysplex data corruption. The system rrr A hexadecimal reason code indicating the
being partitioned either requires maintenance to be reason for the failure.
installed to be able to coexist with the other systems in
the sysplex, or a system already active in the sysplex www The wait state code.
requires maintenance to be installed to be able to
coexist with the failing system. A reason code in register The reason code (rrr) is one of the following:
15 explains the error:
001 Field PSALCCAV or PSASCWA
Code Explanation
002 Field PSAPCCAV
00
System action: The system may write a logrec error
| A pre V1R8 system without APAR OA10632 record.
| applied is attempting to enter a sysplex that
Operator response: If the system programmer
| has a V1R8 system active in the sysplex. The
requests a stand-alone dump, stop all other systems
| V1R8 system issues message IEA002I, and
and obtain a stand-alone dump. ReIPL the system.
| the pre-V1R8 system loads wait state X'082'.
System programmer response: Do the following:
| A V1R8 system is attempting to enter a sysplex
| that has an active system in the sysplex that is 1. If necessary, ask the operator to obtain a
| pre-V1R8 and does not have APAR OA10632 stand-alone dump.
| applied. The V1R8 system issues message 2. Examine the damaged PSA for the system that is in
| IEA002I and loads wait state X'082'. wait state X'083'. See if you can recognize the
damage.
| A pre V1R10 system without APAR OA18204
| applied is attempting to enter a sysplex that 3. Search problem reporting databases for a fix for the
| has a V1R10 system active in the sysplex. The problem. If no fix exists, contact the IBM Support
| V1R10 system issues message IEA002I, and Center. Provide the stand-alone dump and, if
| the pre-V1R10 system loads wait state X'082'. available, the logrec error record.
| A V1R10 system is attempting to enter a Source: Supervisor control
| sysplex that has an active system in the
| sysplex that is pre-V1R10 and does not have 084
| APAR OA18204 applied. The V1R10 system
| issues message IEA002I and loads wait state Explanation: The recovery termination manager
| X'082'. (RTM) encountered an error that could not be corrected
while:
System action: The system entering the sysplex is v Supporting recovery or ending of a system routine
partitioned from the sysplex and wait state X'082' is v Supporting recovery or ending of a task of an
loaded on that system to prevent global sysplex data application program
corruption.
For reason code X'00', message IEA002I is issued, The right-most four bytes of the program status word
either on the failing system or on an active system in (PSW) have the following format:
the sysplex, indicating which system requires x0rrrwww
Chapter 3. Wait State Codes 375
085 • 087
where: – Wait state code: WS/D0084
– Reason code: PRCS/hhhhhhhh
x Irrelevant information.
– Module name: RIDS/cccccccc
rrr A hexadecimal reason code indicating the
reason for the failure. If no fix exists, contact the IBM Support Center.
www The wait state code. v X'008', X'00C', X'010', or X'014' RTM experienced
recursive errors while processing an error. This
The reason code (rrr) is one of the following: problem could be due to overlays of critical fields in
control blocks such as:
004 A first level interruption handler (FLIH) – PSA
determined that the interruption, which was in a – Address space control block (ASCB)
PSW-disabled routine, was an error condition. – Task control block (TCB)
The FLIH called RTM to recover or to end the – Request block (RB)
routine that was interrupted. While processing – Extended status block (XSB)
the request, RTM found uncorrectable damage
to at least one functional recovery routine Do the following:
(FRR) stack pointer in the recovery stack
1. Analyze the dump and logrec error records for
vector table (PSARSVT) of the prefixed save
recursive errors. Identify the RTM module that
area (PSA).
experienced the recursive errors. Determine the
008 The FRR recovery routine for RTM’s FRR offset into the module at which the recursive
processing could not recover from an error in errors occurred.
RTM. The system invoked the super FRR. The 2. Search problem reporting databases for a fix for
super FRR scheduled RTM recovery as the the problem. Include in the search argument:
retry attempt for the original error. This RTM – Name of the overlaid control block field:
recovery tried to end the current address space FLDS/cccccccc
but encountered a second error. – Wait state code: WS/D0084
00C RTM found an error while processing the FRR – Reason code: PRCS/hhhhhhhh
stack. RTM processing is not covered by an – Module name: RIDS/cccccccc
FRR recovery routine. Therefore, RTM
attempted to end the address space but If no fix exists, contact the IBM Support Center.
encountered a second error. Source: Recovery termination manager (RTM)
010 The system entered the program check FLIH
recursively for segment exceptions, and 085
detected a dynamic address translation (DAT)
error in an address space. The system invoked Explanation: During this warm start IPL, the auxiliary
RTM’s FRR processing to end the address storage manager (ASM) forced a switch to a cold start.
space experiencing the DAT error, but RTM’s ASM determined that one of the following is true:
FRR processing encountered a second error. v The pageable link pack area (PLPA) page data set is
This is an unrecoverable software error. behind a cached device. The cache must be reset.
v PLPA has overflowed to the COMMON page data set
014 RTM detected a bad PSATOLD value while and the common data set is on a cached device.
running in task mode. RTM could not end the Warm or quick start has failed. The cache must be
failing address space to resolve the problem. reset.
System action: The system issues message System action: The system ends processing and
IEA020W and enters the X'084' wait state. enters the wait state.
Operator response: If requested by the system Operator response: To reset the cache, reIPL the
programmer, obtain a stand-alone dump. ReIPL the system with the CLPA option.
system.
Source: Auxiliary storage manager (ASM)
System programmer response: For reason code:
v X'004', do the following:
087
1. Look at message IEA020W for an indication of
which CPU had damaged stack pointers and Explanation: At the end of removing a system from a
which pointers were damaged. sysplex, the system enters this wait state. A
hexadecimal reason code in register 15 indicates the
2. Search problem reporting databases for a fix for
reason why the system was removed:
the problem. Include in the search argument:
– Name of the overlaid control block field: Code Explanation
FLDS/cccccccc
01 Communications task (COMMTASK)
376 z/OS V1R10.0 MVS System Codes
088
initialization could not establish a member of 19 A bad return code was received from
the SYSMCS group because the maximum ALESERV ADD for a required data space.
number of members per cross-system coupling
| 1D Both CNZ_MainDsm and CNZ_AuxDsm were
facility (XCF) group was reached.
| damaged.
02 A recursive abend occurred while processing
the console services sysplex update task.
| 22 A basic test of the CLT failed.
| 27 A basic test of the CDUH failed.
03 A recursive abend occurred while processing
the console services cross-system update | 30 Console initialization could not establish
subtask. | appropriate serialization. Message CNZ0006W
05 A recursive abend occurred while processing
| has been issued with additional codes.
the console services sysplex send data | 31 Console migration detected inconsistencies in
processor. | its data and cannot let the migration continue.
06 A recursive abend occurred while processing
| Message CNZ0006W has been issued with
| additional error codes.
the console services sysplex receive data
processor. | 33 Console migration task had an unrecoverable
07 A recursive abend occurred while processing
| error.
the console services cross-system service 34 Essential console services function failed.
group exit.
| 35 The IPLing system does not support distributed
08 A recursive abend occurred while processing | mode.
the console services cross-system service
message exit. | 36 The IPLing system could not obtain console
| data from an existing system in the sysplex.
09 A recursive abend occurred while processing | Message CNZ0008I identifies the existing
the console services sysplex command | system.
processor.
| 37 through 43
0A A recursive abend occurred when the system | During initialization, a module failed and could
processed a message. | not be reattached because module IEAVN701
0B A recursive abend occurred while processing
| had not finished its initialization.
the console services sysplex data queuer. System action: The system enters wait state X'087'.
0C A recursive abend occurred while processing System programmer response: Search problem
the console services sysplex cleanup task. reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0D Another system was unable to accept the
system into the sysplex because of a storage | Source: Console services
shortage.
0E A recursive abend occurred while the system 088
was processing the sysplex reply ID task.
Explanation: During initial program load (IPL), the
0F A recursive abend occurred while processing system encountered an error in processing the LOADxx
the console services sysplex recovery module. or NUCLSTxx members of SYS1.PARMLIB.
11 The system could not join the XCF SYSMCS2 The following format shows the location of the reason
group. code in bits 36 through 43 of the PSW:
12 The system could not create control members X'000A0000 8rrxxwww'
in the XCF SYSMCS2 group. 000A0000
13 The system could not initialize reply ID The A is bits 12 through 15 (the CMWP bits).
processing. 8 If bits 33-39 are not zero then bit 32 must be on
14 Message cache could not be created. indicating AMODE (31-bit addressing mode).
| 15 A recursive abend occurred while processing rr A hexadecimal reason code indicating the reason
| the console services general-purpose task. for the failure.
| 16 Console definition initialization had an xx Irrelevant information.
| unrecoverable error. www
18 Data space could not be created. The wait state code.
Chapter 3. Wait State Codes 377
089
The reason code (rr) is one of the following: System programmer response: Do one of the
following:
00 IPL could not find the LOADxx member in
SYSn.IPLPARM on the IODF volume or v For reason code X'00', create the LOADxx member
SYS1.PARMLIB on the IODF volume or on of SYSn.IPLPARM on the IODF volume or
SYSRES. Either the system programmer did SYS1.PARMLIB on the IODF volume or on SYSRES.
not create the member or the operator typed Tell the operator what value to use for the LOAD
the wrong value for the LOAD parameter. parameter.
v For reason code X'02' make sure that the NUCLST
02 The system could not find the NUCLSTxx
statement was specified correctly in the LOADxx
member of SYSn.IPLPARM or SYS1.PARMLIB
member of SYSn.IPLPARM or SYS1.PARMLIB. Make
that was specified on the NUCLST statement
sure also that the NUCLSTxx parmlib member
in the LOADxx SYS1.PARMLIB member.
resides in the same data set as the LOADxx parmlib
04 The SYSn.IPLPARM or SYS1.PARMLIB member.
directory entry for the LOADxx member v For reason code X'06' or X'0A', delete the NUCLSTxx
contains incorrect information. IPL cannot read member of SYS1.PARMLIB. Then either recreate the
the LOADxx member. NUCLSTxx member, or create a different one. Tell
06 The SYSn.IPLPARM or SYS1.PARMLIB the operator what value to use for the LOAD
directory entry for the NUCLSTxx member parameter.
contains incorrect information, and IPL cannot v For reason code X'04' and X'08' delete the LOADxx
read it. member. Then either recreate the LOADxx member,
or create a different one. Tell the operator what value
08 While reading the LOADxx member, IPL to use for the LOAD parameter.
reached the end-of-file where there should
have been more data. The contents of the v For reason code X'0C', correct the NUCLSTxx
LOADxx member are incorrect. member so that it does not exclude IEANUC0x.
v For reason code X'0E', if IPLing with ARCHLVL 1
0A While reading the NUCLSTxx member, IPL specified in LOADxx, create nucleus extension
reached the end-of-file where there should IEANUC1x, or if by IPLing with ARCHLVL 2, create
have been more data. The contents of the nucleus extension IEANUC2x.
NUCLSTxx member are incorrect.
v For reason code X'10', do not specify ARCHLVL 2 in
0C The member of SYS1.NUCLEUS selected was LOADxx.
excluded by a NUCLSTxx EXCLUDE v For reason code X'14', IPL this z/OS release only on
statement. There was no alternate IEANUC0x a machine that supports z/Architecture.
member of SYS1.NUCLEUS included.
v For reason code X'80', remove the MVSCP statement
0E Could not locate nucleus extension IEANUC1x from the LOADxx member used to IPL. An IODF
or IEANUC2x. must be used to specify I/O configuration data. See
z/OS HCD User’s Guide for information about IODF.
10 z/Architecture mode was requested on the
ARCHLVL parameter in the LOADxx parmlib Source: Initial program load (IPL)
member, but the processor does not support
z/Architecture mode.
089
14 You attempted to IPL a level of z/OS that
requires z/Architecture, but the machine does Explanation: During NIP processing, the system found
not support z/Architecture. an error with a unit control block (UCB) while trying to
create the eligible devices table (EDT).
80 An MVSCP statement was found in the
LOADxx member that was used to IPL. System action: The system enters a non-restartable
wait state.
System action: The system enters a non-restartable
wait state. System programmer response: Determine if the
problem is a device error. If not, take a stand-alone
Operator response: For reason codes X'04', X'08' or dump of the system. Try to IPL with an IODF that is
X'80' notify the system programmer. known to be good.
For reason code X'00', check the value specified in the If the source of the problem cannot be determined,
LOAD parameter. If it is incorrect, use the correct value search problem reporting databases for a fix for the
and reIPL. If it is correct, notify the system programmer problem. If no fix exists, contact the IBM support center.
that the LOADxx member is missing from Provide the dump.
SYSn.IPLPARM on the IODF volume or SYS1.PARMLIB
on the IODF volume or on SYSRES. Source: Allocation/unallocation
378 z/OS V1R10.0 MVS System Codes
08A • 08C
Detecting EP (?IWMXLWT issuer): IWMLTATT
08A
003 Wait state/reason code for WLM Sysplex Mgmt
Explanation: An error occurred while requesting a
(IWMSMTSK) SubTask IWMSMTSK failed
wait state with the WSPARM option on the write to
operator (WTO) macro. Detecting EP (?IWMXLWT issuer): IWMLTETX,
IWMLTATT
The right-most four bytes of the program status word
(PSW) have the following format: 004 Wait state/reason code for WLM Data Mgmt
x0rrrwww (IWMDMTSK) SubTask IWMDMTSK failed
Detecting EP (?IWMXLWT issuer): IWMLTETX,
where: IWMLTATT
x Irrelevant information. 005 Wait state/reason code for WLM Policy Mgmt
rrrr A hexadecimal reason code indicating the (IWMPMTSK) SubTask IWMPMTSK failed
reason for the failure. Detecting EP (?IWMXLWT issuer): IWMLTETX,
www The wait state code. IWMLTATT
006 Wait state/reason code for WLM Performance
The reason code (rrr) is one of the following: Mgmt (IMMDCTSK) SubTask IWMDCTSK
001 Two callers, running on the same processor, failed
tried to load the same wait state. Detecting EP (?IWMXLWT issuer): IWMLTETX,
002 The system abended wait state processing. IWMLTATT
System action: The system issues message 007 Wait state/reason code for WLM
IEA548W. The system enters wait state X'08A'. Linkage/Tasking (IWMLTETX) Restart of a
WLM subtask failed. Failing TCB@ not found
Operator response: If the system programmer asks on FTDE queue.
for a dump, request a stand-alone dump. ReIPL the
system. Detecting EP (?IWMXLWT issuer): IWMLTETX
System programmer response: Depending on the 008 Wait state/reason code for WLM Work Mgmt
reason code, do one of the following: (IWMWMTSK) SubTask IWMWMTSK failed
001 See the system programmer response for the Detecting EP (?IWMXLWT issuer): IWMLTETX,
requesting wait state. IWMLTATT
002 See the system programmer response for the 009 Wait state/reason code for WLM Workload
abend displayed in message IEA548W. reporting (IWMWRTSK) SubTask IWMWRTSK
failed
| Source: Console services
Detecting EP (?IWMXLWT issuer): IWMLTETX,
IWMLTATT
08C
00A No policy available
Explanation: An error occurred during workload
manager (WLM) processing due to recurring abends in Detecting EP (?IWMXLWT issuer): IWMPMxxx
the WLM address space. The accompanying 00B Wait state/reason code for WLM (IWMLTLWT)
hexadecimal reason code identifies an internal, WLM address space termination occurred.
unrecoverable WLM error.
Code Description Note: Unlikely WS; see following task level
RESMGR waitstates.
001 Wait state/reason code for nonspecific WLM
failure. This WaitState code is by the WLM Job Detecting EP (?IWMXLWT issuer): None
Step Tasks Resource Manager Routine as well
as the WLM Address Space Resource 00C Wait state/reason code for WLM (IWMLTLWT)
Manager Routine should IWMINTSK or WLM Job Step Task IWMINTSK abnormally
IWMINJST terminate for any reason terminated, and is non-restartable, therefore
degrading WLM/SRM and system function. IPL
Detecting EP (?IWMXLWT issuer): IWMLTLWT required.
002 Wait state/reason code for WLM initialization Detecting EP (?IWMXLWT issuer): None
(IWMLTATT) IWMLTATT was invoked to attach
a WLM subtask but the epid is not a known 00D Wait state/reason code for WLM (IWMLTLWT)
WLM subtask routine WLM Job Step Task IWMINJST abnormally
Chapter 3. Wait State Codes 379
08E • 09x
terminated, is non-restartable therefore Source: Workload manager (WLM)
degrading WLM/SRM and system ability, IPL
required.
08E
Detecting EP (?IWMXLWT issuer): None
Explanation: A recursive, unrecoverable error
00F Wait state/reason code for WLM Environment occurred during the processing of the NEWIPS
Manager (IWMEMTSK) SubTask IWMEMTSK SYSEVENT.
failed
System action: The system places the processor into
Detecting EP (?IWMXLWT issuer): IWMLTETX, a wait state.
IWMLTATT
Operator response: Notify the system programmer.
010 Wait state/reason code for WLM Device ReIPL the system. After reIPL, avoid issuing any of the
Clustering (IWMDVTSK) SubTask IWMDVTSK following commands, if possible, because the wait state
failed occurred during the processing of one of them:
Detecting EP (?IWMXLWT issuer): IWMLTETX, v Issuing the V WLM,POLICY=XXXXXX command
IWMLTATT v Activating a service policy from the WLM ISPF
application
011 Wait state/reason code for WLM Workload
Balancing (IWMWBTSK) SubTask IWMWBTSK System programmer response: Search problem
failed reporting databases for a fix for the problem. If no fix
exists, contact the IBM support center. Provide the
Detecting EP (?IWMXLWT issuer): IWMLTETX,
hardcopy log and the dump.
IWMLTATT
Source: Workload manager (WLM)
012 Wait state/reason code for WLM Operations
(IWMOPTSK) SubTask IWMOPTSK failed
08F
Detecting EP (?IWMXLWT issuer): IWMLTETX,
IWMLTATT Explanation: The system attempted to rebuild the
work unit queues, but was unable to do so.
013 Wait state/reason code for WLM Scheduling
Environment (IWMSETSK) SubTask System action: The system enters a non-restartable
IWMSETSK failed wait state, and issues message IEA460W.
Detecting EP (?IWMXLWT issuer): IWMLTETX, Operator response: If the system programmer asks
IWMLTATT for a dump, request a stand-alone dump. ReIPL the
system.
014 Wait state/reason code for WLM Coupling
Facility Manager (IWMCFTSK) SubTask System programmer response: If the source of the
IWMCFTSK failed problem cannot be determined, search problem
reporting databases for a fix for the problem. If no fix
Detecting EP (?IWMXLWT issuer): IWMLTETX,
exists, contact the IBM support center. Provide the
IWMLTATT
dump.
015 Wait state/reason code for WLM LPAR
Source: Supervisor Control
Manager (IWMLMTSK) SubTask IWMLMTSK
failed
09x
Detecting EP (?IWMXLWT issuer): IWMLTETX,
IWMLTATT Explanation: The system put a processor into wait
state X'09x' because the following occurred:
016 Wait state/reason code for WLM CHPID
Manager (IWMCMTSK) SubTask IWMCMTSK 1. The processor was in a spin loop, waiting for an
failed event to occur on another processor. The spin loop
exceeded the time normally required for the event to
Detecting EP (?IWMXLWT issuer): IWMLTETX, occur.
IWMLTATT
2. The system was unable to issue the excessive spin
System action: The system places the processor into notification message, IEE331A.
a wait state.
The third digit (x) of the wait state code identifies the
Operator response: Notify the system programmer.
event for which the processor waited, as follows:
System programmer response: Search problem
x Event
reporting databases for a fix for the problem. If no fix
exists, contact the IBM support center. Provide the 1 RISGNL response
hardcopy log and the dump.
2 Lock release
380 z/OS V1R10.0 MVS System Codes
0A1
4 Restart resource 1. Display location X'30E' of the processor in
the X'09x' wait state.
5 Address space to QUIESCE
2. Store the action code (X'CC' or X'BB') at
6 Central processor (CPU) in stopped state location X'30E'.
7 Intersect release 3. Restart the processor in the X'09x' wait
state. The system ignores the restart
9 Operator intervening state reason.
E Successful bind break release ACR
1. Stop all the processors in this system.
The right-most four bytes of the program status word
(PSW) have the following format: 2. Display location X'30E' of the processor in
the X'09x' wait state.
0aaa009x
3. Store action code X'AA' at location X'30E'.
where: 4. Identify the processor that is causing the
spin loop (the failing processor) from the
aaa The logical address of the processor causing
sixth byte of the X'09x' wait state PSW. The
the spin loop.
characters 4x will appear in this byte. x is
x The third digit of the wait state code (x in 09x). the identifier for the failing processor.
System action: The processor in the spin loop enters 5. Start all processors except the failing
restartable wait state X'09x'. The system may issue a processor and the processor in the X'09x'
message that describes the problem. wait state.
6. Restart the processor in the X'09x' wait
Operator response: Before restarting the processor, state (the system ignores the restart
store an action code in storage location X'30E' of the reason).
processor. The action code indicates the recovery action
that the processor will take in an attempt to resolve the 7. After ACR processing is complete, enter a
excessive spin-loop condition. The action codes, in CONFIG CPU(x),ONLINE command at a
order of severity, and the related recovery actions are console with master authority, where x is
the following: the identifier for the failing processor.
Code Recovery Action Performed by System If wait state X'09x' occurs again within approximately
None SPIN - Continue in the spin loop, waiting for one spin-loop interval, respond with recovery action of
the expected event to occur. To start the SPIN the next greatest severity. Notify service personnel.
action, restart the processor in the X'09x' wait Source: Loadwait/Restart
state.
CC ABEND - Abnormally end the current unit of 0A1
work on the processor on which the expected
event did not occur. In this case, the system Explanation: All system-initiated recovery actions
does allow the recovery routines to retry. were exhausted without resolving an excessive spin
loop.
BB TERM - Abnormally end the current unit of
work on the processor on which the expected System action: The system issues message
event did not occur. In this case, the system IEE183W before loading the wait state. Message
does not allow recovery routines to retry. IEE178I might have appeared at least once prior to the
wait state, and may provide additional information.
AA ACR - Start alternate recovery (ACR) for the
processor on which the expected event did not Operator response: Notify the system programmer.
occur. This will take the processor offline and Obtain a stand-alone dump. ReIPL the system.
initiate an abnormal end (with retry allowed) for System programmer response: Collect all printed
the current unit of work on that processor. output and output data sets related to the problem.
Search problem reporting databases for a fix for the
Depending on the type of recovery action, do the problem. If no fix exists, contact the IBM Support
following to start the recovery action: Center.
Action Procedure Source: Loadwait/Restart
SPIN Restart the processor in the X'09x' wait state.
ABEND
TERM
Chapter 3. Wait State Codes 381
0A2
030 An ETR failure on another system has
0A2
occurred. The operator has restarted that
Explanation: Cross-system coupling facility (XCF) or system. All other systems are stopped. Another
cross-system extended services encountered a system is removing this system from the
non-recoverable error and stopped the system. The sysplex because of an external time reference
system also issues this wait state in response to an (ETR) failure. When there is an ETR failure,
operator request to stop the system. See z/OS MVS only one system can remain in the sysplex.
Diagnosis: Reference for information on diagnosing The remaining system removes all others from
sysplex problems. the sysplex.
The right-most four bytes of the program status word 078 The set of sysplex couple data sets in use by
(PSW) have the following format: the sysplex was changed while it was marking
x0rrrwww itself active.
07C System checks indicate that there are no
where: allowable configurations (XCF-local, monoplex,
x Irrelevant information. and sysplex) for this system based on current
settings.
rrr A hexadecimal reason code indicating the
reason for the failure. 08C XCF will not accept this system into the
sysplex because a couple data set
www The wait state code. inconsistency was detected.
09C The CFRM couple data set has been lost.
The reason code (rrr) is one of the following:
091 Internal XCF error
004 The operator entered the VARY
XCF,sysname,OFFLINE command to remove 104 I/O has been prevented as a result of a system
the system from the sysplex. being fenced.
008 XCF lost signalling path connectivity between 108 The system was partitioned out of the sysplex
systems. as specified by XCFPOLxx.
010 XCF lost access to all couple data sets. 10C The system was found to be in a status update
missing condition and was partitioned out of
014 During IPL, XCF removed a system from the
the sysplex as specified by the Sysplex Failure
sysplex.
Management policy.
020 XCF removed the system from the sysplex.
110 The system experienced a signalling
One of the following occurred: connectivity failure and was partitioned out of
v An I/O error was encountered by this system the sysplex as specified by the Sysplex Failure
on either the primary or the alternate couple Management policy.
data set after this system joined the sysplex 114 This is a non-restartable wait state due to the
but before it could complete initialization of loss of the ETR link or the ETR itself.
the couple data sets.
11C Not enough storage to define subchannel
v An I/O error was encountered by another
notification vectors.
system in the sysplex on either the primary
or the alternate couple data set after this 14C The wait state occurred because one of the
system joined the sysplex but before it could names being declared by the operating system
complete initialization of the couple data sets was already declared via logical partition
v The operator on another system in the definition at the hardware console, and the
sysplex initiated a data set transition by previously-declared name does not match the
making a new alternate available via the name being declared by the operating system.
SETXCF COUPLE,ACOUPLE command or | 158 The system has lost time synchronization with
by replacing the primary couple data set with | the Server Time Protocol (STP) time source.
the alternate couple data set via the
SETXCF COUPLE,PSWITCH command. | 15A The system has been partitioned out of the
This action was taken after the time that this | sysplex because it has lost time
system joined the sysplex but before it could | synchronization with the other systems in the
complete initialization of the couple data | sysplex.
sets.
160 A member of XCF group SYSGRS, SYSMCS,
v The operator replied DOWN to message or SYSXCF appeared to be causing signaling
IXC402D to specify that XCF was to remove sympathy sickness. The system was removed
the system from the sysplex. from the sysplex to terminate the member.
382 z/OS V1R10.0 MVS System Codes
0A3
| 164 XES common storage control block CADS You can determine the individual connections by
| initialization failed. issuing the CTRACE QUERY command to see the
sub name traces associated with SYSXES.
| 17C Operator requested partitioning with the VARY
| XCF command and REIPL AutoIPL option v CTRACE COMP(SYSXCF) to obtain XCF trace data.
| specified.
Issue the D XCF,COUPLE command from a system
| 180 Operator requested partitioning with the VARY currently active in the sysplex. Check the connectivity to
| XCF command and SADMP AutoIPL option the volumes that contain the couple data sets. Refer to
| specified. z/OS MVS Setting Up a Sysplex for additional
| 184 Operator requested partitioning with the VARY information on couple data set placement for avoidance
| XCF command and SADMP and REIPL of a single point of failure in couple data set availability.
| AutoIPL options specified.
Search problem reporting databases for a fix for the
System action: The system enters a nonrestartable problem. If no fix exists, contact the IBM Support
wait state and issues message IXC220W or IXL004W. Center. Provide the formatted stand-alone dump.
Operator response: The following reason codes are Include all the reports and the summary, detail, and
possible hardware errors: exception levels for each report.
v 010 Source: Cross-system coupling facility (XCF)
v 08C
v 110
v 114 0A3
Look in the LOGREC data set for hardware errors. Explanation: A system could not successfully
Correct the hardware configuration. If the problem participate in a global resource serialization complex. In
persists, contact hardware support. order for a system to join a sysplex, it must also be a
member of the global resource serialization complex,
The following reason codes represent errors internal to but the system cannot join the global resource
the XCF component. Call the IBM Support Center for serialization complex for one of the following reasons:
assistance with these errors. v The global resource serialization system parameters
specified are incorrect.
Reason Codes:
v Global resource serialization encountered an
unrecoverable error.
018 024 028 040 050
054 058 05C 060 064 The right-most four bytes of the program status word
06C 070 074 080 084 (PSW) have the following format:
088 090 091 094 098 x0rrrwww
118 120 130 134 140
144 148 150 154 where:
x Irrelevant information.
For other reason codes, see the operator response for rrr A hexadecimal reason code indicating the
any preceding messages. reason for the failure.
If the system programmer requests it, obtain a www The wait state code.
stand-alone dump.
The reason code (rrr) is one of the following:
System programmer response: See the system
programmer response for message IXC220W. 004 The system IPLed into a sysplex with
GRS=JOIN or TRYJOIN parameters, but global
Format the stand-alone dump with the following IPCS resource serialization was unable to join the
subcommands: global resource serialization complex. Systems
v XESDATA, including all the reports and the summary, in a sysplex must be in the same global
detail, and exception levels. resource serialization ring. The wait state is
v COUPLE, including all the reports and the summary, accompanied by message ISG167W.
detail, and exception levels. 008 The system IPLed into the sysplex with
v CTRACE COMP(SYSXES) SUB((GLOBAL)) GRS=JOIN, START, TRYJOIN or STAR system
v CTRACE COMP(SYSXES) SUB((individual- parameter, and when global resource
connections)) serialization attempted to use the cross-system
coupling facility (XCF) during initialization, the
service failed with an unexpected error.
Chapter 3. Wait State Codes 383
0A3
When this wait state occurs, message 044 The global resource serialization complex is
ISG152W is issued to the console. This unable to restart after a ring disruption. No
message identifies the XCF service and the active global resource serialization ring exists,
return and reason codes. and this system has repetitively failed in its
attempts to initiate one. The wait state may be
00C Global resource serialization found an error in
accompanied by messages ISG011I, ISG015I,
parmlib member GRSCNFxx. The wait state is
ISG021I, ISG025I, ISG173I, ISG176I, or
accompanied by message ISG043I or ISG044I.
ISG180E.
010 Global resource serialization found an error in
04C The operator entered a VARY GRS,PURGE
parmlib member GRSRNLxx. The wait state is
command for this system, removing it from the
accompanied by messages ISG062I and
global resource serialization complex.
ISG063I.
050 This system is unable to enter the global
014 Global resource serialization could not
resource serialization ring. A current member of
establish the event notification (ENF) exits. The
the global resource serialization complex
wait state is accompanied by message
belongs to a different multisystem sysplex than
ISG021I.
the rest of the members of the global resource
018 Global resource serialization found an error in serialization complex. Global resource
parmlib member GRSCNFxx. The parmlib serialization only supports one multisystem
member specifies a device that is already in sysplex per global resource serialization
use. The wait state is accompanied by complex. The wait state is accompanied by
message ISG045I. message ISG182W.
01C The system IPLed with GRS=NONE and 054 This system is unable to reactivate a global
PLEXCFG=MULTISYSTEM. These two resource serialization ring from the quiesced
parameters are mutually exclusive. The wait state. It became quiesced because of a ring
state is accompanied by message ISG159W. disruption, system failure, or an
operator-issued VARY GRS,QUIESCE
020 Global resource serialization tried to remove command. No active global resource
this system from the complex, but the attempt serialization system exists. This system had
failed. The wait state is accompanied by the most current global request information of
message ISG152W. all systems in the complex.
026 Global resource serialization detected an 058 This system encountered an unrecoverable
unrecoverable error in an XCF exit. software error in recovery for global resource
028 Global resource serialization detected an serialization ring processing.
internal error. 05C This system encountered an unrecoverable
02C Global resource serialization detected an software error in recovery for global resource
unrecoverable failure while running in a serialization internal or external command
sysplex. The wait state is accompanied by processing.
message ISG168W. 060 Global resource serialization tried to invoke the
030 Global resource serialization detected an XCF Query service to gather information about
internal error. the sysplex, but the attempt failed. The wait
state is accompanied by message ISG152W.
034 The system IPLed with GRS=JOIN or
TRYJOIN, but global resource serialization 064 This system’s inclusion resource name list
could not invoke the XCF Set User State (GRS RNL parmlib member) is not exactly the
service. The wait state is accompanied by same as the one the global resource
message ISG152W. serialization complex is currently using. All
RNLs must be the same within the GRS
038 Global resource serialization could not find the complex. Note that RNLs that may have the
systems exclusion RNL exit (ISGGSEEA) while same results are not considered to be exact
trying to process a GRSRNL=EXCLUDE matches. They should be the exact same RNL
system parameter. values in the exact same order. If they appear
03C Global resource serialization could not find the to be the same, then obtain a stand-alone
systems inclusion RNL exit (ISGGSIEA) while dump; in a sysplex, a SDUMP will be taken on
trying to process a GRSRNL=EXCLUDE the assisting system. This dump should also be
system parameter. provided to the IBM Service Center.
040 The system could not send a message via the 068 This system’s exclusion resource name list
XCF message out service. (GRS RNL parmlib member) is not exactly the
same as the one the global resource
384 z/OS V1R10.0 MVS System Codes
0A3
serialization complex is currently using. All If the system partitioned out of the complex
RNLs must be the same within the GRS and was put into a wait state as a result of
complex. Note that RNLs that may have the action taken by an already active system that
same results are not considered to be exact detected the error, then message ISG307W is
matches. They should be the exact same RNL not issued.
values in the exact same order. If they appear
088 Global resource serialization invoked a system
to be the same, then obtain a stand-alone
service which did not successfully complete.
dump; in a sysplex, a SDUMP will be taken on
Message ISG308W is issued, identifying the
the assisting system. This dump should also be
system service along with the error return and
provided to the IBM Service Center.
reason code.
06C This system’s RESERVE conversion RNL
08A During system initialization, global resource
(GRS RNL parmlib member) is not exactly the
serialization was unable to access the global
same as the one the global resource
resource serialization record on the sysplex
serialization complex is using. All RNLs must
couple dataset.
be the same within the GRS complex. Note
that RNLs that may have the same results are When this wait state occurs, message
not considered to be exact matches. They ISG342W is issued to the console. This
should be the exact same RNL values in the message identifies the reason the record could
exact same order. If they appear to be the not be accessed.
same, then obtain a stand-alone dump; in a
sysplex, a SDUMP will be taken on the 08E During the initialization, GRS GRQA was
assisting system. This dump should also be allocated too high by the IARV64 service to
provided to the IBM Service Center. guarantee IXLLOCK processing integrity. The
wait state is accompanied by message
070 This system encountered an unrecoverable ISG373W. See message ISG373W for
software error during global resource additional diagnostic data that should be
serialization queue merge processing. Obtain a provided to IBM service.
stand-alone dump; in a sysplex, a SDUMP will
be taken on the ’assisting system’. This dump 090 Global resource serialization processing failed
should also be provided to the IBM Service due to the unexpected termination on one of its
Center. tasks that is critical to global resource
processing.
07C Global resource serialization address
initialization failed. A system service called to When this wait state occurs, message
initialize one of its modules was not successful. ISG315W is issued to the console. An error
code in this message identifies the task that
When this wait state occurs, message failed.
ISG305W is issued to the console. This
message identifies the service, the module and 094 During global resource serialization processing,
the non-zero return code passed back from the one of its critical task terminated. Global
service. resource serialization is unable to reinstate the
task because the ATTACH for the task failed
080 Global resource serialization initialization failed. with an error return code.
A critical task terminated.
When this wait state occurs, message
When this wait state occurs, message ISG316W is issued to the console. This
ISG306W is issued to the console. An error message identifies the module the could not be
code in this message identifies the particular ATTACHed and the error return code from
task that failed. ATTACH.
084 Global resource serialization failed. The type of 098 During recovery, a primary global resource
complex the system initialized is not compatible serialization control block was damaged.
with the complex currently active in the Global resource serialization is unable to
sysplex. A system IPLed with GRS=START, recover from this error.
JOIN or TRYJOIN, cannot join an existing
global resource serialization star complex. When this wait state occurs, message
Similarly, when a system is IPLed with ISG317W is issued to the console.
GRS=STAR, it cannot join an existing global 09C During GRS Star initialization, the system was
resource serialization ring complex. unable to access the GRS lock structure
If the system detected the error condition itself (ISGLOCK).
and issued the wait state, message ISG307W This wait state might occur if CFRM is not
is issued. available for the first system trying to come up
Chapter 3. Wait State Codes 385
0A3
in STAR mode, and CFRMPOL is not specified 0C8 During a rebuild of the global resource
in the COUPLExx parmlib member. serialization lock structure, global resource
serialization received a request to stop the
When this wait state occurs, message
rebuild. Global resource serialization can not
ISG342W is issued to the console. The
resume processing with the original global
message describes what kind of access to the
resource serialization lock structure, due to a
structure failed.
structure failure or loss of connectivity.
0A0 During GRS processing, an unexpected error
When this wait state occurs, message
occurred in one of the GRS XCF exits. GRS is
ISG309W is issued to the console.
unable to recover from the failure. (Message
ISG310W is issued to the console.) 0CC During a rebuild of the global resource
serialization lock structure, sysplex failure
0AC The top level global resource serialization task
management (SFM) determined that this
from which all other task are anchored
system should not disconnect from the
unexpectedly received control at a point in its
structure. Global resource serialization
processing that should not occur and is unable
partitioned the system from the sysplex to
to recover.
insure data integrity is maintained.
When this wait state occurs, message
When this wait state occurs, message
ISG329W is issued to the console.
ISG309W is issued to the console.
| 0BC During initialization of a star complex, global
0D0 During a rebuild of the global resource
| resource serialization was not able to allocate
serialization lock structure, sysplex failure
| the global resource serialization lock structure.
management (SFM) determined that the
| The reason can be one of the following:
original lock structure has better connectivity
| 1. Connection to the structure failed with than the new structure. Global resource
| IXLCONN RC=0C and RSN=0C08 or serialization could not resume processing with
| RSN=0C27. | the original lock structure due to a structure
| 2. Storage on the coupling facility is | failure or a loss of connectivity condition.
| insufficient or the policy size is too small for Global resource serialization partitions the
| the minimum structure size needed. system from the sysplex to insure data integrity
is maintained.
When this wait state occurs, message | Additionally, this code is issued for a failure
ISG338W is issued to the console. This | when the lock structure rebuild was issued on
message identifies the name of the structure | behalf of a GRSRNL=EXCLUDE to standard
causing the failure. | RNLs migration. The original structure does not
0C0 An unexpected error occurred in one of the | contain an accurate reflection of all globally
Global resource serialization lock structure | managed resources and therefore cannot be
exits. Global resource serialization is unable to | used.
recover from this error. When this wait state occurs, message
When this wait state occurs, message ISG309W is issued to the console.
ISG310W is issued to the console. This 0D4 During a rebuild of the global resource
message identifies the name of the global serialization lock structure, global resource
resource serialization lock structure that failed. serialization was unable to connect to the new
0C4 During a rebuild of the global resource structure. Global resource serialization
serialization lock structure detected damage to partitions the system from the sysplex to insure
the global request queue on the system. data integrity is maintained.
Global resource serialization is not able to When this wait state occurs, message
continue using the original lock structure due to ISG309W is issued to the console.
a structure failure or loss of connectivity.
0D8 During a rebuild of the global resource
| Additionally, this code is issued for a failure serialization lock structure, global resource
| when the lock structure rebuild was issued on serialization received an unrecoverable
| behalf of a GRSRNL=EXCLUDE to standard response from a XES service. Global resource
| RNLs migration. The original structure does not serialization is not able to continue processing.
| contain an accurate reflection of all globally
| managed resources and therefore cannot be When this wait state occurs, message
| used. ISG308W or ISG309W is issued to the
console.
When this wait state occurs, message
ISG309W is issued to the console. 0DC During a rebuild of the global resource
386 z/OS V1R10.0 MVS System Codes
0A4
serialization lock structure, global resource v To IPL a system without global resource serialization,
serialization received an unexpected event, IPL with COUPLE=00,GRS=NONE. The system will
violating the rebuild protocol. Global resource IPL in XCF-local mode. Do not start any jobs that
serialization is not able to continue. access shared sysplex resources.
When this wait state occurs, message v To IPL a system into the sysplex and the global
ISG309W is issued to the console. resource serialization complex,
– If you want to IPL a global resource serialization
0E0 During a rebuild of the global resource
ring complex, correct the GRS= specification (in
serialization lock structure, global resource
IEASYSxx parmlib member or in response to
serialization stopped for an unknown reason.
message IEA101A) to be one of the following:
Global resource serialization is not able to
continue processing. - START
- JOIN
When this wait state occurs, message
ISG309W is issued to the console. - TRYJOIN
– If you want to IPL a global resource serialization
0E4 During migration from a global resource
star complex, check the following:
serialization ring to a star complex, a structure
error occurred. Global resource serialization is 1. The global resource serialization record was
not able to continue processing. formatted on the sysplex couple data set via
the IXCL1DSU formatting utility.
When this wait state occurs, message
2. The sysplex couple data set with the global
ISG309W is issued to the console.
resource serialization record is the current
0E8 During migration from a global resource primary sysplex couple data set.
serialization ring to a star complex, global v To resolve the problem preventing the system from
resource serialization queue damage was joining global resource serialization, do the following:
detected. Global resource serialization is not
v See the explanations for accompanying messages for
able to continue processing.
information about the problem.
When this wait state occurs, message ISG332I v Obtain the SVC dump, if one was issued, and format
is issued to the console. it with the IPCS VERBEXIT MTRACE command to
0EA The system attempted to IPL while global find the last message global resource serialization
resource serialization was migrating from a issued. See the explanation for any message found.
global resource serialization ring to a star v For reason codes 64, 68, 6C, and 70, obtain a
complex. The system cannot join the complex stand-alone dump; in a sysplex, a SDUMP will be
during this processing. taken on the ’assisting system’. This dump should
also be provided to the IBM Service Center.
When this wait state occurs, message
ISG301W is issued to the console. v If you cannot find the problem, or the problem
persists, search problem reporting databases for a fix
0EC During migration from a global resource for the problem. If no fix exists, contact the IBM
serialization ring to a star complex, an Support Center. Provide the logrec error record and
unexpected error occurred. the SVC dump if they were issued.
When this wait state occurs, message Source: Global resource serialization
ISG304W is issued to the console.
| 0EE During migration from GRSRNL=EXCLUDE to 0A4
| standard RNLs, an unexpected error occurred.
Explanation: Two or more processors could not
| When this wait state occurs, message complete external time reference (ETR) synchronization
| ISG373W is issued to the console. check processing. ETR is the MVS generic name for the
IBM Sysplex Timer (9037) or equivalent.
System action: The system enters a non-restartable
wait state. For reason codes X'026', X'058', and X'05C', System action: The system enters wait state X'0A4'.
the system writes a logrec error record and issues an This wait state is accompanied by message IEA503W.
SVC dump.
Operator response: Retain the logrec error records.
For reason codes X'064' through X'070', the system Contact hardware support.
issues message ISG015I. The system may also issue
message ISG183W. Source: Timer supervision
System programmer response: Do one of the
following:
Chapter 3. Wait State Codes 387
0A5
081 Two UIMs made multiple attempts to build a
0A5
UIT for the indicated device. The first UIM is
Explanation: The system detected a logic error in one flagged as in error.
of the hardware configuration definition (HCD) modules.
082 The indicated UIM specified more than 24
The right-most four bytes of the program status word bytes of device-dependent segment data. The
(PSW) have the following format: indicated UIM is flagged as in error.
xrrr0www 083 The indicated UIM specified a device number
greater than the maximum allowed device
where: number.
x Irrelevant information. v Message reason code 1: Device number in
the relocation information is greater than the
rrr A hexadecimal reason code indicating the maximum allowed device number.
reason for the failure.
v Message reason code 2: Device number in
www The wait state code. the device class extension area is greater
than the maximum allowed device number.
The reason code (rrr) is one of the following:
The indicated UIM is flagged as in error.
070 Two UIMs made multiple attempts to build a
084 The indicated UIM specified an non-valid
GIT. The first UIM is flagged as in error.
device class in the DFPTBYT3 field. The
071 Two UIMs specified the same generic indicated UIM is flagged as in error.
preference value. The last UIM is flagged as in
085 The DCT information specified for a DASD
error.
does not match the previously specified
072 A UIM defines a generic device type with a information for this DASD type.
compatible list that contains duplicate entries.
086 A UIM specified a DCT entry length greater
073 Two UIMs made multiple attempts to build a than the allowed maximum.
CIT for the indicated control unit. The first UIM
087 Insufficient space in DCT for current DCT entry.
is flagged as in error.
088 The indicated UIM tried to build a CIT by
074 A UIM specified an non-valid device number in
passing a CIP that does not specify an
DFP.
attachable device list.
v Message reason code 1: The device number
in the DFP is greater than the maximum 091 The indicated generic name as specified in the
allowed device number. list of compatible generics could not be found
in the list of GITs. The first indicated generic is
v Message reason code 2: A DFT exists
deleted from the list of compatible generics.
already for the device number specified in
The UIM is flagged as in error.
the DFP.
System action: The system enters wait state X'0A5'.
075 A UIM specified either in the DFP or UIP a
The system issues the following hardware configuration
generic name for which the GIT could not be
definition (HCD) messages with the following wait state
found. The indicated UIM is flagged as in error.
reason codes:
076 The indicated UIM specified more than 5 MLT
Code Accompanying Message
names or specified no MLT names. The
indicated UIM is flagged as in error. 070 CBDA070I, to display the UIM name and the
generic name.
077 The indicated UIM specified more than the 256
bytes of device-dependent information. The 071 CBDA071I, to display the UIM name and the
indicated UIM is flagged as in error. generic names.
078 The indicated UIM specified an non-valid UCB 072 CBDA072I, to display the UIM name and the
segment type for an ACON position pointer. generic name.
The indicated UIM is flagged as in error.
073 CBDA073I, to display the UIM name and the
079 The indicated UIM specified an non-valid UCB control unit type/model.
segment type for an ACON relocation pointer.
The indicated UIM is flagged as in error. 074 CBDA074I, to display the UIM name, device
number, and reason code.
080 The indicated UIM specified an offset for an
ACON position pointer that is not within the 075 CBDA075I, to display the UIM name and the
specified UCB segment. The indicated UIM is DFP or UIP, as applicable.
flagged as in error. 076 CBDA076I, to display the UIM name.
388 z/OS V1R10.0 MVS System Codes
0A7 • 0B0
077 CBDA077I, to display the UIM name. Source: Allocation Build EDT Resource Initialization
Module (RIM) IEAVNP88.
078 CBDA078I, to display the UIM name and UCB
segment type.
0B0
079 CBDA079I, to display the UIM name and the
UCB segment type. Explanation: The system could not recognize the I/O
definition file (IODF) specified in the LOADxx parmlib
080 CBDA080I, to display the UIM name.
member.
081 CBDA081I, to display the UIM names and the
device type/model. Note: If equals (’==’) was specified as the IODF suffix
in the LOADxx parmlib member, MVS uses the
082 CBDA082I, to display the UIM name.
IODF suffix obtained from the hardware token in
083 CBDA083I, to display the UIM name, device the Hardware System Area (HSA). If equals
number, and reason code. (’========’) was specified as the IODF
high-level qualifier in the LOADxx parmlib
084 CBDA084I, to display the UIM name, device member, MVS uses the high-level qualifier
number, and Ucbtype3. obtained from the hardware token in the HSA. If
085 CBDA085I, to display the DASD type. the characters ’IODF’ are not found, or the IODF
suffix is not X'00' to X'FF', MVS will load wait
086 CBDA086I, to display the UIM name. state X'0B1' reason code X'00B'. MVS uses the
087 CBDA087I. same rules for determining its ability to use the
IODF name explicitly specified in LOADxx.
088 CBDA088I, to display the UIM name and
control unit type/model. The right-most four bytes of the program status word
091 CBDA091I, to display the generic names. (PSW) have the following format:
xrr00www
Operator response: Notify the system programmer. If
requested by the system programmer, obtain a
where:
stand-alone dump.
x Irrelevant information.
System programmer response: Search problem
reporting databases for a fix for the problem. Use the rr A hexadecimal reason code indicating the
following search argument: reason for the failure.
v WS/D0A5: Wait state code
v PRCS/hhhhhhhh: Reason code www The wait state code.
v PIDS/name of UIM: Program name
v VALU/Ccccccccc: Message variable text The reason code (rr) is one of the following:
If no fix exists, ask the operator to obtain the 01 The input/output supervisor (IOS) section of the
stand-alone dump. Contact the IBM Support Center. IODF is not compatible with the system code.
Provide the stand-alone dump, the UIM name, if 02 The allocation section of the IODF is not valid.
available, and the accompanying message. The most likely reason for this is that the IODF
Source: Hardware configuration definition (HCD) was created by a system with a higher release
level than the system that is attempting to use
the IODF.
0A7
System action: The system enters nonrestartable wait
Explanation: There is insufficient Extended System state X'0B0'.
Queue Area (ESQA) or Extended Common Storage
Area (ECSA) storage available to build the Eligible System programmer response: If the correct IODF is
Device Table (EDT) during the Nucleus Initialization being used, it is likely that a recent release of the
Program (NIP). operating system has converted the IODF to a format
not supported by the current release and service level.
System action: The system enters a non-restartable Search RETAIN for an appropriate compatibility PTF to
Wait State. bring this system up to the required service level.
Operator response: Notify the System Programmer. If the correct IODF is not being used, enter the correct
System programmer response: Increase the ESQA IODF data set name in the LOADxx PARMLIB member.
and ECSA storage size specifications on the SQA and Ask the operator to REIPL the system.
CSA parameters in the appropriate IEASYSxx Source: Input/output supervisor (IOS)
member(s) and reIPL.
Chapter 3. Wait State Codes 389
0B1
high-level qualifier obtained from the
0B1
hardware token in the HSA. If the
Explanation: System initialization cannot continue characters ’IODF’ are not found, or the
because of a problem in the LOADxx parmlib member, IODF suffix is not X'00' to X'FF', MVS
the I/O definition file (IODF) data set, or a device. will load wait state X'0B1' reason code
X'00B'. MVS uses the same rules for
The right-most four bytes of the program status word
determining its ability to use the IODF
(PSW) have the following format:
name explicitly specified in LOADxx.
xrr00www
0C An incorrect IODF volume has been chosen for
where: the initial program load (IPL).
x Irrelevant information. | Note: This wait state can also occur because of an
rr A hexadecimal reason code indicating the | IODF statement that is not valid. In addition to
reason for the failure. | incorrect data entries, this wait state can also be
| caused by incorrect keyword filtering that uses
www The wait state code. | the HWNAME, LPAR NAME, and VMUSERID
| keywords.
The reason code (rr) is one of the following:
01 The required data set was not found.
| Note: Ensure that the LOADxx member has not been
| compressed by the ISPF Edit PACK option. This
02 The IODF occupies more than one extent. | can be checked by using the PROFILE
| command from the ISPF edit command line to
03 A required device is not defined.
| display the state of the edit options. When PACK
04 MSCH instruction failed for a required device. | ON is used, the ISPF editor stores the data set
| in a compressed form that is not detected by the
05 The IODF is not valid for an IPL. | operating system.
06 The IODF did not contain an operating system System action: The system enters nonrestartable wait
configuration definition matching the state X'0B1'. The system issues the following messages
configuration ID specified in the LOADxx with the following wait state reason codes:
member.
Code Accompanying Message
07 The IODF is not valid for an IPL. The
configuration ID was blank in LOADxx, but 01 IEA513W.
there was more than one operating system
02 IEA514W.
configuration definition. If the configuration ID
is blank, then IPL will use a single-defined 03 IEA515W, to display the device number.
operating system configuration definition as the
04 IEA516W, to display the device number.
default.
05 IEA517W.
08 The IODF suffix is not valid.
06 IEA518W.
| 09 After parsing the LOADxx member and
| applying any specified filtering keywords, the 07 None.
| high-level qualifier for the IODF data set name
| is not valid. 08 None.
0A The IODF is not valid for an IPL. It must be a 09 None.
VSAM dataset. 0A IEA517W.
0B Equals (’==’) were specified as the IODF suffix 0B IEA511W.
or equals (’========’) were specified as the
IODF high-level qualifier in the member and 0C None.
the configuration hardware token was not able
to be obtained from the Hardware System Area To view any accompanying message, perform the
(HSA), the IODF suffix found in the hardware following:
token did not contain a valid hexadecimal 1. Using the hardware Alter/Display facility, read the
number or the characters ’IODF’ were not real address in central storage at X'14'. This
found in the token. address points to the IPL diagnostic area.
2. Add X'28' to the address in X'14', and also read this
Note: If equals (’========’) were specified as as a real address in central storage. The result is
the IODF high-level qualifier in the the 31-bit virtual address of the IPL vector table
LOADxx parmlib member, MVS uses the (IVT). Henceforth, all addresses are 31-bit virtual
390 z/OS V1R10.0 MVS System Codes
0B2
and you must switch to displaying Primary 06 Change the LOADxx member to specify
Virtual Storage to display remaining storage another IODF or the correct operation system
locations. configuration ID.
3. Add X'E0' to the IVT address. The result is the 07 Specify the correct operating system
31-bit address of the IVTMQHP field. IVTMQHP configuration identifier.
contains the address of the message queue header
(MQH). 08 Correct the suffix to be within the range X'00'
to X'FF'.
4. MQH+X'0' contains the address of the oldest
message queue element (MQE) available. The | 09 Check to ensure that the IODF Statement
message text for the oldest MQE begins at | correctly specifies the high-level qualifier that is
MQE+X'08'. | wanted. Then check for any usage of filtering
5. Use MQE+X'0' of the oldest MQE to find the MQE | keywords, HWNAME, LPAR NAME, or
of the next oldest message. Again, the message text | VMUSERID, to ensure that a valid IODF
for this MQE begins at MQE+ X'08'. | Statement can be found. If the filtering
| keywords are incorrectly specified, the
6. Repeat this sequence (using MQE+X'0' of the
| high-level qualifier for the IODF statement
current MQE to locate the next MQE), until the
message text for the appropriate message is
| resolves to blanks and this reason code
displayed.
| results. Read carefully the rules for specifying
| these filter keywords.
Operator response: Ensure that the correct IODF
0A Change the Loadxx member to specify another
volume is specified for the IPL and then reIPL the
IODF. Be sure to specify the name of a VSAM
system. Device numbers are four digits in length. ReIPL
data set (instead of a sequential or partitioned
and run the job again. Set LOAD parameter to the
data set).
device number of the device that contains or
SYS1.PARMLIB. Device numbers can be four digits in 0B Change the Loadxx member to specify another
length, reIPL. Notify the system programmer. IODF. Be sure to specify the name of a
production-IODF or specify pluses (’++’),
System programmer response: Depending on the
minuses (’--’), blanks (’ ’) or asterisks (’**’) and
reason code, one of the following:
let the system locate a valid IODF. If equals
Code Action (’========’) were specified as the high-level
qualifier, specify the high-level qualifier of a
01 Verify that the correct device number was
production-IODF.
specified on the LOAD parameter. Verify that
the IODF resides on the same volume as 0C Ensure that the correct IODF volume is
SYSn.IPLPARM or SYS1.PARMLIB. Enter the specified for the IPL and that the hardware
correct IODF data set name in the LOAD xx management console (HMC) load profile points
parmlib member. to this volume. Then reIPL the system.
02 Ensure that the IODF data set is allocated as a
In each case, ask the operator to reIPL the system.
single extent data set.
Problem determination: If the problem persists,
03 Load device does not have the proper
search problem reporting databases for a fix for the
subchannel identifier. Verify that the device on
problem. Provide the following search argument:
which the IODF resides is defined. Verify that
the correct device number was specified on the v WS/D0B1: Wait state code
LOAD parameter. Verify that the hardware v PRCS/000000rr: Reason code
configuration matches the definitions in the v MS/IEAnnnW: Message identifier
IODF.
If no fix exists, ask the operator to obtain the
04 Move any of the following data sets (that are stand-alone dump. Contact the IBM Support Center.
on the device specified on the LOAD Provide the stand-alone dump, the accompanying
parameter) to a different device: message, and the reason code.
v IODF
Source: Input/Output supervisor (IOS)
v SYS1.PARMLIB
v SYSn.IPLPARM
0B2
05 Change the LOADxx member to specify
another IODF. Be sure to specify the name of a Explanation: No devices were defined in the I/O
production-IODF. definition file (IODF).
System action: The system enters nonrestartable wait
state X'0B2'. The system may issue message IEA523W.
Chapter 3. Wait State Codes 391
0B3 • 0E0
System programmer response: See the explanation If no fix exists, ask the operator to obtain the
for message IEA523W. Verify that the IODF contains stand-alone dump. Contact the IBM Support Center.
devices that are defined to MVS. Verify that the Provide the stand-alone dump.
necessary UIMs supporting these devices are present in
Source: Input/output supervisor (IOS)
SYS1.NUCLEUS. If the problem persists, search
problem reporting databases for a fix for the problem. If
no fix exists, ask the operator to obtain the stand-alone 0B5
dump. Contact the IBM Support Center. Provide the
stand-alone dump and the accompanying message. | Explanation: Basic HyperSwap has partitioned a
| member out of the SYSPLEX due to an error condition.
Source: Hardware configuration definition (HCD) | Basic HyperSwap can partition a system out of a
| sysplex for the following reasons:
0B3 | v Reason 1 - User-specified policy indicates that a
| member failure, while a Basic HyperSwap is in
Explanation: Initial program load (IPL), found incorrect | progress, is to be partitioned out of the sysplex. This
information in the LOAD parameter. The first four | includes a new system joining the sysplex while a
characters of the LOAD parameters should contain the | Basic HyperSwap is already in progress.
device number of the direct access storage device
| v Reason 2 - User-specified policy indicates that a new
(DASD) volume containing the SYS1.PARMLIB data set.
| sysplex member should be partitioned if it is unable
The value specified in the LOAD parameter is not a
| to successfully load and monitor a Basic HyperSwap
valid device number.
| configuration.
System action: The system enters a non-restartable
| System action: XCF services are used to partition the
wait state.
| failing member out of the sysplex. Basic HyperSwap
Operator response: Check the LOAD parameter on | message IOSHM0428I can result if XCF services are
the hardware frame you used to IPL the system. The | not available to perform the partition request.
first four characters are supposed to be hexadecimal
digits (0 through 9, A through F) that form the device
| System programmer response: Ask the operator to
| obtain the stand-alone dump. Contact the IBM Support
number where the IODF resides. For three digit device
| Center. Provide the stand-alone dump. Review the
numbers, add a leading zero so that all four characters
are valid hexadecimal digits.
| Basic HyperSwap policy in effect at the time of the
| failure to ensure that the required actions were
If the value is incorrect, enter the correct value and | performed.
reIPL the system. If the value is correct, record the
Source: Input/output supervisor (IOS)
contents of the LOAD parameter, and notify the system
programmer.
0E0
System programmer response: If the LOAD
parameter specifies the correct four digit hexadecimal Explanation: During nucleus initialization program
device number and the problem persists, search (NIP) processing, the system could not signal an online
problem reporting databases for a fix for the problem. If processor to update control register 14.
no fix exists, contact the IBM Support Center.
System action: The system sends messages about
Source: Initial program load (IPL) the job to one of the following:
v The primary console.
0B4 v The remote console, for a system with remote
consoles.
Explanation: A unit information module (UIM)
specified an undefined device number. v The hard-copy log for a system with multiple console
support (MCS).
System action: The system issues message
IEA525W to identify the UIM in error. The system enters The system enters a nonrestartable wait state.
nonrestartable wait state X'0B4'. Operator response: This is probably a hardware
System programmer response: See message error. Try to reIPL the system.
IEA525W for the name of the failing UIM. Check if the If the problem persists, switch to uniprocessor mode
failing UIM is an installation-provided or IBM-provided and reIPL the system. Then try to vary the other
UIM. If it is an IBM-provided UIM, search problem processor online. If necessary, contact hardware
reporting databases for a fix for the problem. Provide support.
the following search argument:
v WS/D0B4: Wait state code Source: Supervisor control
v MS/IEA525W: Message identifier
v VAlu/Cuim_name: Message variable text
392 z/OS V1R10.0 MVS System Codes
0E1 • 101
0E1 0E8
Explanation: A configure CPU online command failed. Explanation: During nucleus initialization program
(NIP) processing, the machine check handler (MCH)
The following format shows the location of the reason
resource initialization module (RIM) failed.
code and wait state code in the PSW:
X'000A0000 00000000 00000000 000rrwww' The right-most four bytes of the program status word
(PSW) have the following format:
000A0000
x01rrwww
The A is bits 12 through 15 (the CMWP bits). x02rrwww
rr A hexadecimal reason code indicating the x03rrwww
reason for the failure.
where:
www The wait state code.
x Irrelevant information.
The reason code (rr) is one of the following: 1rr, 2rr, 3rr
10 While IEEVWKUP was processing a CF CPU A hexadecimal return code indicating the
online request on the target CPU, another reason for the failure.
RESTART signal was received on the same www The wait state code.
CPU.
11 A program-check occurred on the new The return code is one of the following:
processor prior to the architecture mode being 1rr A request to allocate MCH control blocks
properly set for that processor. returned nonzero return code rr.
12 A machine-check occurred on the new 2rr A request to initialize the control registers
processor prior to the architecture mode being returned nonzero return code rr.
properly set for that processor.
3rr A request for virtual storage returned nonzero
20 A RESTART was received on the target CPU return code rr.
after IEEVCVSR timed out waiting for DSGNL
RESTART to finish. System action: The system enters nonrestartable wait
state X'0E8'.
30 During CPU online processing, IEEVWKUP
detected that IEEVCVSR decided to back out Operator response: Record the wait state PSW.
of CPU online processing. Notify the system programmer. ReIPL the system.
System action: The system ends command If the system programmer requests it, obtain a
processing and loads wait state X'0E1'. stand-alone dump.
Operator response: Enter the command again. If the System programmer response: Search problem
problem recurs, contact hardware support. reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
Source: Loadwait/Reconfiguration stand-alone dump.
Source: Machine check handler (MCH)
0E3
Explanation: There is not enough virtual storage 101
available to initialize the common service area (CSA).
Explanation: A program running in supervisor state
System action: The system may issue message tried to obtain more storage from the system queue
IEA140W. The system enters wait state X'0E3'. area (SQA) than was available.
Operator response: Notify the system programmer. System action: The system may issue message
System programmer response: Modify the virtual IEA946W. The system enters wait state X'101'.
storage allocated to the nucleus, system queue area Operator response: ReIPL the system. If this code
(SQA), or link pack areas (LPA). occurs frequently, notify the system programmer.
Source: Virtual storage management (VSM) System programmer response: Increase the space
allowed for the SQA, or specify more space for the SQA
in response to message IEA101A at the next system
initialization.
Source: Virtual storage management (VSM)
Chapter 3. Wait State Codes 393
102 • 110
v If the device was online, the system
102
marks it pending offline. A pending
Explanation: During processing for a GETMAIN offline device goes offline when the
macro for a program running in supervisor state, an following conditions occur, in this
error occurred. More pages of central storage were order:
requested for the system queue area (SQA) than were 1. The device is no longer
available. allocated to any job.
System action: The system may issue message 2. Allocation processing allocates
IEA946W. The system enters wait state X'102'. any device in the system.
Operator response: ReIPL the system. If this code v If the device was offline, it remains
occurs frequently, notify the system programmer. offline.
System programmer response: Increase the fixed 04 The system tries to recover the
central storage requirements for the system. channel path. If channel path recovery
is successful, the system:
Source: Virtual storage management (VSM) v Issues message IOS203I
v Leaves the channel path online
104 v Clears the pending status of the hot
device
Explanation: While the system was processing the
Supervisor Call (SVC) instruction for an ABEND macro, If channel path recovery is not
a program check occurred recursively. successful, the system issues
message IOS202I and forces the
System action: The system writes a logrec data set channel path offline.
error record. The system may issue message IEA740W.
The system loads the X'104' wait state PSW. 05 The system forces the channel path
offline. The system issues message
Operator response: If the system programmer IOS202I.
requests a stand-alone dump, obtain one. ReIPL the
system. 06 The system tries to recover the control
unit. If recovery is successful, the
System programmer response: Search problem system:
reporting databases for a fix for the problem. If no fix v Issues message IOS208I
exists, ask the operator to obtain a stand-alone dump.
Contact the IBM Support Center. Provide the v Leaves the device paths online for
stand-alone dump and the logrec data set error record. all devices on the same control unit
v Clears the pending status of the
Source: Supervisor control cleared device
If recovery is not successful, the
110 system issues message IOS207I.
Explanation: The system detected a hot I/O condition Operator response: Do the following:
on a device other than a direct access storage device
(DASD). 1. Find the address of the status collection data (SCD)
area by using the hardware Alter/Display facility to
System action: The system leaves the device status display the contents of location X'40C'. Record the
pending and issues message IOS110D. Depending on first 4 bytes of data at this location.
the recovery code entered by the operator, the system 2. Use the hardware Alter/Display facility to display the
does the following: storage pointed to by location X'40C'.
Response System Action 3. Contact hardware support.
01 The system clears the device status. 4. Use the hardware Alter/Display facility to change
The device remains online. The location X'30E' to one of the following recovery
system does not attempt channel path codes:
recovery. Processing continues. Code Explanation
02 or 03 The system boxes the device, as 01 Do not attempt channel path recovery.
follows:
v The I/O on the device is ended. 02 Box the device.
v Any new I/O requests result in 03 Allow the operator to store the device
permanent I/O errors. number of each device on the control unit
v The system does not perform new in the operator reply area for IOS110D.
allocations for the device.
394 z/OS V1R10.0 MVS System Codes
111 • 112
04 Try to recover the channel path. v Clears the pending status of the cleared device
05 Force the channel path offline. If recovery is not successful, the system issues
message IOS207I.
06 Try to recover the control unit.
5. Use the Restart facility to restart the waiting Operator response: Do the following:
processor 1. Find the address of the status collection data (SCD)
area by using the hardware Alter/Display facility to
Source: Input/output supervisor (IOS)
display the contents of location X'40C'. Record the
first 4 bytes of data at this location.
111 2. Use the hardware Alter/Display facility to display the
Explanation: The system detected a hot I/O condition storage pointed to by location X'40C'.
on a direct access storage device (DASD). 3. Contact hardware support.
System action: The system leaves the device status 4. Use the hardware Alter/Display facility to change
pending and issues message IOS111D. Depending on location X'30E' to one of the following recovery
the recovery code entered by the operator, the system codes:
does the following: Code Explanation
Code Response 01 Do not attempt channel path recovery.
01 The system clears the device status. The 02 Box the device.
device remains online. The system does not
attempt channel path recovery. Processing 03 Allow the operator to store the device
continues. number of each device on the control unit
in the operator reply area for IOS110D.
02 or 03
The system boxes the device, as follows: 04 Try to recover the channel path.
v The I/O on the device is ended. 05 Force the channel path offline.
v Any new I/O requests result in permanent 06 Try to recover the control unit.
I/O errors.
5. Use the Restart facility to restart the waiting
v The system does not perform new processor
allocations for the device.
Source: Input/output supervisor (IOS)
v If the device was online, the system marks it
pending offline. A pending offline device
goes offline when the following conditions 112
occur, in this order:
Explanation: The system detected a hot I/O condition
1. The device is no longer allocated to any on a reserved direct access storage device (DASD).
job.
2. Allocation processing allocates any System action: The system leaves the device status
device in the system. pending and issues message IOS112D. Depending on
the recovery code entered by the operator, one of the
v If the device was offline, it remains offline. following:
04 The system tries to recover the channel path. If Code Response
channel path recovery is successful, the
system: 01 The system clears the device status. The
v Issues message IOS203I device remains online. The system does not
v Leaves the channel path online attempt channel path recovery. Processing
v Clears the pending status of the hot device continues.
If channel path recovery is not successful, the 02 or 03
system issues message IOS202I and forces The system boxes the device:
the channel path offline. v The I/O on the device is ended.
05 The system forces the channel path offline. v Any new I/O requests result in permanent
The system issues message IOS202I. I/O errors.
06 The system tries to recover the control unit. If v The system does not perform new
recovery is successful, the system: allocations for the device.
v Issues message IOS208I v If the device was online, the system marks it
pending offline. A pending offline device
v Leaves the device paths online for all goes offline when the following conditions
devices on the same control unit occur, in this order:
Chapter 3. Wait State Codes 395
113 • 114
1. The device is no longer allocated to any
113
job.
2. Allocation processing allocates any Explanation: The system could not recover from an
device in the system. error that occurred while the system was performing
channel path recovery.
v If the device was offline, it remains offline.
The system may have released reserved devices. Data
04 The system tries to recover the channel path. If
may be lost or written over.
channel path recovery is successful, the
system: System action: The system may issue message
v Issues message IOS203I IOS113W. The system enters wait state X'113'.
v Leaves the channel path online The system issues message IOS113W.
v Clears the pending status of the hot device Operator response: Do the following:
If channel path recovery is not successful, the v Verify data sets.
system issues message IOS202I and forces v Refer to installation procedures for diagnosing an
the channel path offline. error in channel path recovery. If none exist, obtain a
05 The system forces the channel path offline. stand-alone dump and reIPL the system.
The system issues message IOS202I. v Notify the system programmer.
06 The system tries to recover the control unit. If System programmer response: Search problem
recovery is successful, the system: reporting databases for a fix for the problem. If no fix
v Issues message IOS208I exists, contact the IBM Support Center. Provide the
stand-alone dump.
v Leaves the device paths online for all
devices on the same control unit Source: Input/output supervisor (IOS)
v Clears the pending status of the cleared
device 114
If recovery is not successful, the system issues Explanation: A previous error required that the
message IOS207I. operator stop sharing processors. The system
Operator response: Do the following: recovered from the error.
1. Find the address of the status collection data (SCD) The right-most four bytes of the program status word
area by using the hardware Alter/Display facility to (PSW) have the following format:
display the contents of location X'40C'. Record the xrrr0www
first 4 bytes of data at this location.
2. Use the hardware Alter/Display facility to display the where:
storage pointed to by location X'40C'.
x Irrelevant information.
3. Contact hardware support.
4. Use the hardware Alter/Display facility to change rrr A hexadecimal reason code indicating the
location X'30E' to one of the following recovery reason for the failure.
codes: www The wait state code.
Code Explanation
The reason code (rrr) is one of the following:
01 Do not attempt channel path recovery.
001 Reserves are intact. The system successfully
02 Box the device. recovered the reserved devices.
03 Allow the operator to store the device 002 Reserves are lost. The system forced one or
number of each device on the control unit more devices that are reserved for the system
in the operator reply area for IOS110D. offline.
04 Try to recover the channel path. System action: The system enters wait state X'114'
05 Force the channel path offline. because it could not issue message IOS201E. The
system waits for the operator to restart the system.
06 Try to recover the control unit.
Operator response: Do the following:
5. Use the Restart facility to restart the waiting
processor 1. Isolate the failing channel path for repair.
2. Identify and recover failing tasks.
Source: Input/output supervisor (IOS)
3. If the reason code indicates that reserves are intact,
do the following:
396 z/OS V1R10.0 MVS System Codes
115 • 117
a. Enter the IOACTION RESUME command for the 30-31 Zeros.
device on all other sharing systems if the device
32-35 The address of the complete sense data.
was stopped, or restart any stopped systems, or
vary the device back online. Start the stopped System action: The system enters wait state X'115'.
processors by pressing the START key at the
system console of each sharing system or Operator response: Do the following:
logical partition. 1. Verify that the proper pack is mounted on the device
b. Perform a system restart on the system that specified. Then ready the device.
detected the stopped processor. 2. Restart the waiting processor.
4. If the reason code indicates that reserves are lost, 3. If the reason code indicates that the device is not
do the following: operational, verify that the channel and the control
a. Enter the IOACTION RESUME command for the unit are powered on and properly connected.
device on all other sharing systems if the device Source: Input/output supervisor (IOS)
was stopped, or restart any stopped systems, or
vary the device back online. Start the stopped
processor by pressing the START key at the 116
system console of each sharing system or Explanation: During restart processing, the system
logical partition. found a missing interruption for a paging device.
b. Perform a system restart on the system that
Storage location X'40C' contains the paging device
detected the stopped processor.
number.
c. Notify the system programmer.
System action: The system enters wait state X'116'.
Source: Input/output supervisor (IOS)
Operator response: Do the following:
1. Check the paging device for hardware problems.
115
2. Check control units and switching units for proper
Explanation: A direct access storage device (DASD) connections.
containing a page data set is unavailable for an I/O
3. Restart the waiting processor.
operation.
4. If you just mounted the device, enter a VARY
Location X'40C' in central storage points to an area that DEVICE ONLINE command to generate a simulated
contains the following: device end.
Byte Contents Source: Input/output supervisor (IOS)
0-3 The number of bytes in the following area.
4-7 The wait state code. 117
8-15 The name of the module issuing wait state Explanation: Joining this system to a clustered LPAR
code X'015' group after updating the IOS Couple Dataset failed.
16-23 The time stamp. The right most four bytes of the program status word
(PSW) have the following format: xxrrrwww
24 The reason code. It is one of the following:
where:
Code Explanation
xx Irrelevant information.
10 A permanent I/O error occurred when
the system was reading the volume rrr A hexidecimal reason code indicating the reason for
serial number for the specified device. the failure.
20 The device is not operational. www
The wait state code.
40 Intervention is required for the
specified device. The reason code (rrr) is one of the following:
80 The pack mounted does not contain xyy
the proper volume serial number for XCF JOIN failed. This code can be interpreted as
the device. follows:
25 Zero. v x is the return code from the IXCJOIN service
divided by four.
26-27 The device address.
v yy is the reason code from the IXCJOIN service
28-29 The first 2 bytes of sense data. divided by four.
Chapter 3. Wait State Codes 397
11A • 202
F01 Code Explanation
If retry was possible but a suitable retry point could
001 or 002 While the system was creating the
not be determined.
console communications address
System action: The system is partitioned from the space, a failure occurred.
sysplex and enters a non-restartable wait state.
Fccc An abend occurred. The completion
System programmer response: Look at the code is ccc.
explanation of the return and reason code from the
IXCJOIN service in MVS Programming: Sysplex and where www is the wait state code.
Services Reference.
Operator response: Record the contents of the wait
Source: Input/output supervisor (IOS) state PSW. Notify the system programmer. ReIPL the
system.
11A System programmer response: If the reason code is
Fccc, see the system programmer response for abend
Explanation: The SVC 26 routine received a
ccc.
protection exception when the routine tried to store into
a user-supplied CAMLST work area. The storage If the reason code is 8xxx, search problem reporting
protection key of the work area did not match the user’s databases for a fix for the problem. If no fix exists,
protection key. contact the IBM Support Center.
Application Programmer Response: Correct the | Source: Console services
pointer in the LOCATE parameter list to the LOCATE
work area, and execute the job step again.
202
System programmer response: If the error recurs
and the program is not in error, look at the messages in Explanation: During system initialization, the system
the job log for more information. Search problem was initializing the address space to be used for
reporting databases for a fix for the problem. If no fix console communications. Initialization of the address
exists, contact the IBM Support Center. Provide the JCL space failed.
and the program listing for the job. A hexadecimal reason code in field PSAWTCOD in the
Source: DFSMSdfp prefixed save area (PSA) explains the error:
Code Explanation
120 00008001 Console communication could not
Explanation: Geographically Dispersed Parallel establish a recovery environment.
Sysplex® (GDPS®) processing has stopped a system. 00008002 An error occurred when the system
See GDPS/PPRC Installation and Customization Guide tried to load a module.
for additional information.
00008003 An error occurred during POST macro
System action: GDPS processing places the z/OS processing.
image(s) affected in wait state X'120' with reason code
4 or wait state X'CCC'. GDPS also issues message 00008004 An error occurred during POST macro
GEO557E, which is delivered to the console specified in processing.
the SYNCHDEST definition in your CONSOLxx | 00008005 An error occurred when the system
member. | updated the command address space
Source: GDPS | table (CAST).
| 00008007 An error occurred when the system
201 | tried to post IEEVIPL.
Explanation: A failure occurred when the system was | 00008008 An error occurred when the system
trying to create the console communications task | tried to attach IEAVM613.
(COMMTASK) address space. This code is associated | 00008009 An error occurred when the system
with message IEA366W. | tried to attach IEAVM605.
The following shows the right-most four bytes of the | 0000800C An error occurred when the system
wait state PSW in z/Architecture mode: | tried to attach CNZM1TIM.
0rrrxwww
0000Fccc An abend occurred. The completion
code is ccc.
Where rrr is one of the following hexadecimal reason
codes: System action: The system enters restartable wait
state X'202'. The system may issue message IEA367A.
398 z/OS V1R10.0 MVS System Codes
204 • 5C7
Operator response: Do the following: | If the reason code is X'0008', take a stand-alone dump
1. Find the reason code by using the hardware | and contact the IBM Support Center. If a new IODF
Alter/Display facility to display the contents of | configuration is used for IPLing, return to the previous
location X'40C'. Report the reason code to the | configuration in the interim.
systems programmer. For all other reason codes, search problem reporting
2. Perform the restart operation to restart the system. databases for a fix for the problem. If no fix exists,
contact the IBM Support Center.
System programmer response: Do the following:
1. Look at the explanation of message IEA367A, if Source: Allocation
issued.
2. Continue diagnosis according to the reason code: 205
v For reason code X'0000F'ccc, see the description Explanation: During nucleus initialization program
of the abend code. (NIP) processing, the system tried to load a module that
v For reason code X'00008'xxx, search problem was not in the data set in the linklist (as defined by
reporting databases for a fix for the problem. If no PROGxx or LNKLSTxx parmlib members).
fix exists, contact the IBM Support Center.
System action: The system enters a non-restartable
| Source: Console services wait state X'205'.
System programmer response: Search problem
204 reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
Explanation: An error occurred during Allocation
processing. A reason code appears in bits 36 through Source: Allocation
51 of the wait state PSW and explains the error:
Code Explanation 206
0000 During system initialization, the system found Explanation: During system initialization, a sysplex
an eligible devices table (EDT) identifier test datesource partition specified OPERATOR
specified in the LOADxx parmlib member that PROMPT.
does not exist in the I/O definition file.
System action: The system enters a non-restartable
0001 During system initialization the system could wait state.
not build the AGT.
Operator response: Notify the system programmer.
0002 During system initialization, the system could
System programmer response: Modify the CLOCKxx
not build the TSRA.
parmlib member for the sysplex datesource LPAR to
0003 During system initialization or ABEND recovery specify OPERATOR NOPROMPT.
processing, the system could not attach or
Source: Timer supervision
reattach the Tape Switch work task.
0004 During system initialization, the system could
5C7
not join the sysplex.
Explanation: An error occurred during processor or
0005 The Tape Switch work task encountered too
system termination.
many errors.
The right-most four bytes of the program status word
0006 ATS initialization error.
(PSW) has one of the following formats:
0007 IEFHBPDB task failed. rrrr0www
| 0008 During ALLOCAS initialization, the system 8rrrrwww
0rrrrwww
| could not obtain storage for device information.
0040 IEFHBPDC could not be attached. where:
System action: The system enters a non-restartable rrrr A hexadecimal reason code indicating the
wait state X'204'. reason for the failure.
System programmer response: If the reason code is www The wait state code.
X'0000', check that the EDT identifier specified in
| LOADxx exists in the I/O definition file. If filtering In z/Architecture mode, the reason code (rrrr) is one of
| keywords such as HWNAME, LPARNAME, and the following:
| VMUSERID are used, verify that they allow the desired
| IODF to be found. ReIPL the system. 0101 Three processors each attempted to load a
Chapter 3. Wait State Codes 399
A00 • A19
wait state. There is not enough storage exists, contact the IBM Support Center. Provide the
available to support the third request. stand-alone dump.
0201 Two concurrent wait state requests were in Source: Recovery termination manager (RTM)
progress.
0907 An error occurred during ACR processing. A01
1904 An error occurred while the system was Explanation: One of the following hardware errors
processing a write to operator (WTO) to display occurred on the only online processor:
a message and load a system wait state. v A predefined number of hard machine check
1905 An error occurred in the processor stop routine. interruptions
v A hard machine check interruption from which the
1906 The system could not start alternate CPU
system cannot recover
recovery (ACR) on a target processor.
System action: The system enters wait state X'A01'.
System action: For reason code X'0101', the system
rejects the third request and loads temporary disabled Operator response: To recover possible unrecorded
wait state X'5C7' on one processor. Then the system machine check error records, write a stand-alone dump.
(all processors) enters the first successfully loaded wait Contact hardware support.
state.
Source: Machine check handler (MCH)
For reason code X'0201', the system rejects one of the
requests and loads temporary disabled wait state X'5C7'
A18
on one processor. Then the system (all processors)
enters the other requested wait state. Explanation: The system received an unsolicited
device end interruption for a volume containing a paging
For all other reason codes, the system enters a
data set. Volume serial verification failed for one or
non-restartable wait state X'5C7'. For reason codes
more of the following reasons:
X'9906' and X'1906' the system also issues message
BLW006W. v The device address contained a volume with a
different volume serial number.
Operator response: Notify the system programmer. If
v An I/O error occurred while attempting to read the
necessary, obtain a stand-alone dump. ReIPL the
volume label.
system.
v The device went from ready to not ready status when
System programmer response: For reason code volume verification attempted to read the volume
X'0101'and X'0201', see the system programmer label.
response for the wait state that the processor enters
after wait state X'5C7'. For all other reason codes, System action: The system enters wait state X'A18'.
search problem reporting databases for a fix for the Operator response: Do the following:
problem. If no fix exists, contact the IBM Support
Center. 1. Ensure that all volumes containing paging data sets
are on the same device addresses as they were at
Source: Loadwait/Restart system initialization.
2. Ensure that all devices are ready.
A00 3. Restart the waiting processor.
Explanation: A dynamic address translation (DAT) Source: Input/output supervisor (IOS)
error occurred for a system address space. The
recovery termination manager (RTM) does not end the
address space because the ASCBNOMT and A19
ASCBNOMD fields of the address space control block Explanation: The system can no longer perform I/O.
(ASCB) show that the MEMTERM option of the
CALLRTM macro is not valid for the address space. System action: The system issues message
The address space is critical for system operation. IOS019W. The system enters nonrestartable wait state
X'A19'.
System action: The system may issue message
IEA802W. The system enters the wait state. Operator response: Contact hardware support.
Operator response: If requested by the system Source: Input/output supervisor (IOS)
programmer, obtain the stand-alone dump. ReIPL the
system.
System programmer response: Search problem
reporting databases for a fix for the problem. If no fix
400 z/OS V1R10.0 MVS System Codes
A1E • A26
reporting databases for a fix for the problem. If no fix
A1E
exists, ask the operator to obtain a stand-alone dump.
Explanation: The only online time-of-day (TOD) clock Contact the IBM Support Center. Provide the dump.
failed. This wait state is accompanied by message
Source: Real storage manager (RSM)
IEA274W.
System action: The system enters wait state X'A1E'.
A22
Operator response: Retain the logrec data set error
Explanation: An error, such as a hot I/O condition in a
records. Contact hardware support.
multiprocessing configuration, caused the disabled
Source: Timer supervision console communications facility (DCCF) to load this
interim wait state. While in this wait state, DCCF issues
a message requesting a reply, or enters another wait
A1F
state.
Explanation: The processor controller is not available.
System action: The processor on which the DCCF is
Time-of-day synchronization cannot occur.
running waits for responses to the messages that the
System action: The system enters wait state X'A1F'. DCCF sent to the console with master authority, or the
alternate or system console. When message processing
Operator response: ReIPL the system. is complete, the system restarts the processors that are
Source: Timer supervision in the X'A22' wait state.
Operator response: Respond to DCCF messages.
A20 | Source: Console services or master scheduler
Explanation: The system found a page in the fixed
link pack area (FLPA) that is not fixed. A23
System action: The system enters wait state X'A20'. Explanation: A program check interruption occurred
The system writes message IAR011W. while the machine check handler was running on the
Operator response: If requested by the system only online processor. No recovery was possible.
programmer, obtain a stand-alone dump. Attempt to System action: The system issues message
reIPL the system without the FLPA. BLW006W. Processing continues on other processors.
System programmer response: Search problem Operator response: To recover possible unrecorded
reporting databases for a fix for the problem. If no fix machine check error records, write a stand-alone dump.
exists, collect a stand-alone dump from the operator Retain the dump. Contact hardware support.
and contact the IBM Support Center. Provide the
stand-alone dump. Source: Machine check handler (MCH)
Source: Real storage manager (RSM)
A24
A21 Explanation: The system detected a loop while the
machine check handler was running on the only online
Explanation: The system attempted to page-protect a processor. No recovery was possible.
storage area. The segment table entry (SGTE) for this
area was incorrect. The error occurred in the modified System action: The system issues message
link pack area (MLPA), the extended pageable link pack BLW006W. The system enters wait state X'A24'.
area (PLPA), the fixed link pack area (FLPA), or the
Operator response: To recover possible unrecorded
extended FLPA.
machine check error records, write a stand-alone dump.
System action: The system enters wait state X'A21'. Contact hardware support.
The system issues message IAR012W.
Source: Machine check handler (MCH)
Operator response: If requested by the system
programmer, obtain a stand-alone dump.
A26
If the error occurred in MLPA, EXTENDED MLPA,
Explanation: A machine check interruption occurred
BLDL, FLPA, or EXTENDED FLPA, attempt to reIPL the
on the only online processor. The machine check
system without this area. If the error occurred in MLPA
interruption code associated with the interruption is
or EXTENDED MLPA, try to reIPL the system without
incorrect. No recovery was possible.
the default page protection for this area. Use the
NOPROT option on the MLPA parameter. System action: The system issues message
BLW006W. The system enters wait state X'A26'.
System programmer response: Search the problem
Chapter 3. Wait State Codes 401
A27 • A2C
Operator response: To recover possible unrecorded
A2A
machine check error records, write a stand-alone dump.
Retain the dump. Contact hardware support. Explanation: The system detected a page within the
range of the pageable link pack area (PLPA), extended
Source: Machine check handler (MCH)
PLPA, the modified link pack area (MLPA), or the
extended MLPA that was never paged into auxiliary
A27 storage. Ranges of system storage that are page
protected must have a copy on auxiliary storage so the
Explanation: One of the following occurred: system can refresh the page if necessary.
v A machine check interruption or a program check
interruption occurred System action: The system enters wait state X'A2A'.
v The processor issued a malfunction alert (MFA) and Operator response: If requested by the system
did not enter or remain in check-stop state programmer, obtain a stand-alone dump. Try to reIPL
v The system simulated a malfunction alert when the the system using the no-protect option on the MLPA
operator replied alternate CPU recovery (ACR) to system parameter in the IEASYSxx parmlib member.
message IEE331A, but the processor did not enter or See the explanation of messages IAR012W and
remain in check-stop state IEA928I for more information.
System action: The system enters wait state X'A27'. System programmer response: Fix the MLPA
Processing continues on other processors in the parameter in the IEASYSxx parmlib member so that the
sysplex. error does not recur. If the error does recur, search
problem reporting databases for a fix for the problem. If
Operator response: To recover possible unrecorded no fix exists, ask the operator to obtain a stand-alone
error records, write a stand-alone dump. Retain the dump. Contact the IBM Support Center. Provide the
dump. Contact hardware support. dump.
Source: Loadwait/Restart Source: Real storage manager (RSM)
A28 A2B
Explanation: The DAT-off machine check handler Explanation: A hardware error exists in extended
(MCH) routine (DAT is Dynamic Address Translation) storage. Recovery is not possible.
cannot reach the DAT-on MCH routine. This situation
can arise when a second machine check occurs when System action: The system issues message
the load program status word (LPSW) assembler IGF912W. The system enters wait state X'A2B'.
instruction gives control to the DAT-on MCH routine. Operator response: ReIPL the system.
System action: The system enters wait state X'A28'. Source: Machine check handler (MCH)
Operator response: To recover possible unrecorded
machine check error records, request a stand-alone | A2C
dump. Retain the dump. Contact hardware support.
| Explanation: The system could not allocate storage
Source: Machine check handler (MCH) | for a memory object in the high virtual common area.
| The address portion of the program status word (PSW)
A29 | contains X'xxxrrA2C', where rr is the reason code.
Explanation: The system was stopping itself when a | The following reason codes explain the failure:
program or machine check occurred. While trying to | Code Explanation
recover from this program or machine check, another
program or machine check occurred. This problem is | 01 Error in creating the control structures used to
probably a software error. | manage high virtual common storage.
System action: The system enters wait state X'A29'. | 02 There is insufficient free space in the high
Processing continues on other processors in the | virtual common area to hold the memory object
sysplex. | being created.
System programmer response: If the problem | System action: Message IAR024W is issued and the
reporting databases do not show a fix for the problem, | system enters wait state X'A2C'.
contact the IBM Support Center. | Operator response: If requested by the system
Source: Loadwait/Restart | programmer, obtain a stand-alone dump.
| System programmer response: Search problem
| reporting databases for a fix for the problem. If no fix
402 z/OS V1R10.0 MVS System Codes
A70 • B01
| exists, collect a stand-alone dump from the operator
A7A
| and contact the IBM Support Center. Provide the
| stand-alone dump. Explanation: Initialization of the service processor
interface (SPI) failed. The reason code appears in the
| Source: Real storage manager (RSM) program status word (PSW). The address portion of the
PSW contains X'x0rrrA7A', where rr is the reason code.
A70 The following reason codes explain the failure:
Explanation: During system initialization, the console Code Explanation
is unavailable, and the system could not deliver a write
001 The service processor interface task
to operator with reply (WTOR) or synchronous
could not be attached.
message.
002 The recovery environment could not
System action: The system issues message
be established.
IEA548W. The system issues the first 8 lines of the text
of the failing message. The system enters wait state 004 The required service processor
X'A70'. facilities are not installed.
Operator response: ReIPL when the console 006 The service processor is busy during
becomes available. system initialization.
| Source: Console services 007 A service processor malfunction
occurred during system initialization.
A71 008 Service processor damage is detected
during system initialization.
Explanation: During initialization, the reconfiguration
component either could not complete initialization or 009 Service processor interface
could not establish a recovery environment. The component trace could not be
address portion of the program status word (PSW) initialized.
contains X'x0rrrA71', where rr is the reason code.
00A The service processor interface could
The following reason codes explain the failure: not load a module.
Code Explanation 00B The service processor interface could
not obtain storage.
030 A reconfiguration module could not determine
the cause of error. 00C, 00D, 00E, 00F
An internal error occurred.
032 A reconfiguration module could not establish a
recovery environment. 011 The enabled wait PSW was used for
looping during a disabled write to
033 A reconfiguration module could not be loaded.
operator.
034 A reconfiguration module could not be called.
013 An internal error occurred.
035 A reconfiguration module could not obtain a
System action: The system loads nonrestartable wait
message buffer.
state X'A7A'.
036 A reconfiguration module could not obtain a
Operator response: For reason code X'06', X'07', or
required resource.
X'08', contact hardware support. For other reason
099 A reconfiguration module could not initialize the codes, notify the system programmer.
IPLing processor.
System programmer response: Search problem
System action: The system loads a non-restartable reporting databases for a fix. If no fix exists, contact the
wait state. IBM Support Center.
Operator response: Notify the system programmer. Source: Service processor interface
System programmer response: Search problem
reporting databases for a fix for the problem. If no fix B01
exists, contact the IBM Support Center.
Explanation: The 3203/3211 utility has completed
Source: Reconfiguration normally.
Operator response: Verify the printed image and
restart the system.
Source: DFSMSdfp
Chapter 3. Wait State Codes 403
B02 • B0B
reporting databases for a fix for the problem. If no fix
B02
exists, contact the IBM Support Center.
Explanation: This wait state code is issued by the
Source: DFSMSdfp
3203/3211 utility. A control statement is missing or out of
order. The JOB and END control statements must be
the first and last statements, respectively. The DFN, B06
UCS, and FCB statements can be included in any order.
Explanation: This wait state code is issued by the
Operator response: Correct the control statement 3203/3211 utility. The FCB statement is incorrect.
sequence, insert any missing statements, and rerun the
program. If requested by the system programmer, obtain Operator response: Correct the FCB statement and
a stand-alone dump. rerun the program. Have the 3203/3211 utility and
control statements available. If requested by the system
System programmer response: If the error recurs programmer, obtain a stand-alone dump.
and the program is not in error, search problem
reporting databases for a fix for the problem. If no fix System programmer response: If the error recurs
exists, contact the IBM Support Center. and the program is not in error, search problem
reporting databases for a fix for the problem. If no fix
Source: DFSMSdfp exists, contact the IBM Support Center.
Source: DFSMSdfp
B03
Explanation: This wait state code is issued by the B07
3203/3211 utility. The JOB statement is incorrect.
Explanation: This wait state code is issued by the
Operator response: Correct the JOB statement and 3203/3211 utility. The END statement is incorrect.
rerun the program. Have the 3203/3211 utility and
control statements available. If requested by the system Operator response: Correct the END statement and
programmer, obtain a stand-alone dump. rerun the program. Have the 3203/3211 utility and
control statements available. If requested by the system
System programmer response: If the error recurs programmer, obtain a stand-alone dump.
and the program is not in error, search problem
reporting databases for a fix for the problem. If no fix System programmer response: If the error recurs
exists, contact the IBM Support Center. and the program is not in error, search problem
reporting databases for a fix for the problem. If no fix
Source: DFSMSdfp exists, contact the IBM Support Center.
Source: DFSMSdfp
B04
Explanation: This wait state code is issued by the B0A
3203/3211 utility. The DFN statement is incorrect.
Explanation: This wait state code is issued by the
Operator response: Correct the DFN statement and 3203/3211 utility. An external interrupt has occurred.
rerun the program. Have the 3203/3211 utility and
control statements available. If requested by the system Operator response: Rerun the program.
programmer, obtain a stand-alone dump. Source: DFSMSdfp
System programmer response: If the error recurs
and the program is not in error, search problem B0B
reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Explanation: This wait state code is issued by the
3203/3211 utility. A program check interrupt has
Source: DFSMSdfp occurred.
Operator response: Have the 3203/3211 utility and
B05 control statements available. If requested by the system
Explanation: This wait state code is issued by the programmer, obtain a stand-alone dump.
3203/3211 utility. The UCS statement is incorrect. System programmer response: If the error recurs
Operator response: Correct the UCS statement and and the program is not in error, search problem
rerun the program. Have the 3203/3211 utility and reporting databases for a fix for the problem. If no fix
control statements available. If requested by the system exists, contact the IBM Support Center.
programmer, obtain a stand-alone dump. Source: DFSMSdfp
System programmer response: If the error recurs
and the program is not in error, search problem
404 z/OS V1R10.0 MVS System Codes
B0C • B1D
B0C B15
Explanation: This wait state code is issued by the Explanation: This wait state code is issued by the
3203/3211 utility. A machine check interrupt has 3203/3211 utility. No device end is indicated on the
occurred. reader.
Operator response: Execute the SEREP program and Operator response: Probable hardware error. Rerun
save the output. Rerun the job. the job.
Source: DFSMSdfp Source: DFSMSdfp
B11 B19
Explanation: This wait state code is issued by the Explanation: This wait state code is issued by the
3203/3211 utility. The reader is not online. This will 3203/3211 utility. The printer is not online. This will
occur when the reader’s control unit has no power or occur when the printer’s control unit has no power,
when the control unit has been switched off the I/O when the control unit has been switched off the I/O
interface. interface, or when the control unit is not a part of the
system.
Operator response: Put the specified control unit
online and rerun the program. If the error recurs, Operator response: Ensure that the address of the
contact your hardware support personnel. printer specified in the DFN statement is correct. Ensure
that the control unit is online, and rerun the job. If the
Source: DFSMSdfp
error recurs, contact your hardware support personnel.
Source: DFSMSdfp
B12
Explanation: This wait state code is issued by the
B1B
3203/3211 utility. The reader is not ready.
Explanation: This wait state code is issued by the
Operator response: Ready the reader and rerun the
3203/3211 utility. A unit check has occurred on the
program.
printer.
Source: DFSMSdfp
Operator response: If the error condition is not
apparent, display low storage location 2-7 for sense
B13 information. Correct the faulty condition and rerun the
job. If the problem recurs, contact your hardware
Explanation: This wait state code is issued by the support personnel.
3203/3211 utility. The reader is not ready.
Source: DFSMSdfp
Operator response: If the error condition is not
apparent, display location 3 for sense information. (An
interpretation of sense bit settings can be found in the B1C
component description book for the control unit being
Explanation: This wait state code is issued by the
used.) Correct the faulty condition and clear the reader
3203/3211 utility. A printer channel error has occurred.
check. Rerun the program. If reader checks occur
frequently, use a card guide to check for off-punched Operator response: Probable hardware error. Rerun
cards. If the cards are punched correctly and are in the job.
good condition and read checks continue, contact your
Source: DFSMSdfp
hardware support personnel.
Source: DFSMSdfp
B1D
Explanation: This wait state code is issued by the
B14
3203/3211 utility. No device end is indicated on the
Explanation: This wait state code is issued by the printer.
3203/3211 utility. A reader channel error has occurred.
Operator response: Probable hardware error. Rerun
Operator response: Probable hardware error. Rerun the job. If the error recurs, contact your hardware
the job. support personnel.
Source: DFSMSdfp Source: DFSMSdfp
Chapter 3. Wait State Codes 405
B20 • D0D
B20 B24
Explanation: The operator running the stand-alone Explanation: During processing of the stand-alone
version of the input/output configuration program (IOCP) version of the input/output configuration program
has ended IOCP. (IOCP), IOCP encountered an error in the hardware
processor controller and cannot communicate with the
Operator response: Notify the system programmer.
IOCP operator.
System programmer response: Search problem
Operator response: Notify the system programmer.
reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center. System programmer response: Search problem
reporting databases for a fix for the problem. If no fix
Source: Input/output configuration program (IOCP)
exists, contact the IBM Support Center. Provide all
printed output and output data sets related to the
B21 problem.
Explanation: A program check interruption has Source: Input/output configuration program (IOCP)
occurred during processing of the stand-alone version of
the input/output configuration program (IOCP).
CCC
Operator response: Notify the system programmer.
Explanation: When the system runs the QUIESCE
System programmer response: Search problem function, the system is placed in restartable wait state
reporting databases for a fix for the problem. If no fix X'CCC'.
exists, contact the IBM Support Center. Provide all
System action: The system issues message BLW002I
printed output and output data sets related to the
before entering wait state X'CCC'.
problem.
Operator response: Perform the restart function on
Source: Input/output configuration program (IOCP)
the waiting processor, when you want the system out of
QUIESCE.
B22
Source: Loadwait/Restart
Explanation: A machine check interruption has
occurred during processing of the stand-alone version of
D0D
the input/output configuration program (IOCP).
Explanation: System management facilities (SMF)
Operator response: Notify the system programmer.
encountered a resource shortage. Bits 40-51 in the wait
System programmer response: Search problem state program status word (PSW) contain one of the
reporting databases for a fix for the problem. If no fix following reason codes:
exists, contact the IBM Support Center. Provide all
Code Explanation
printed output and output data sets related to the
problem. 00 This reason code is associated with message
IEE987E. No SMF buffer space is available.
Source: Input/output configuration program (IOCP)
SMF has used up all the available storage for
its internal buffers and has stopped the system,
B23 as requested by the NOBUFFS(HALT) in the
SMFPRMxx parmlib member.
Explanation: An unrecoverable I/O error has occurred
during processing of the stand-alone version of the 01 This reason code is associated with message
input/output configuration program (IOCP). IEE988E. No SMF data sets are available.
SMF has used up all the available data sets for
Operator response: Notify the system programmer. its data. SMF stopped the system, as
System programmer response: Search problem requested by the LASTDS(HALT) in the
reporting databases for a fix for the problem. If no fix SMFPRMxx parmlib member.
exists, contact the IBM Support Center. Provide all System action: SMF enters restartable wait state
printed output and output data sets related to the X'D0D'.
problem.
Operator response: Respond as indicated for the
Source: Input/output configuration program (IOCP) specific reason code:
Code Response
00 Do one of the following:
| v Perform a restart operation to restart the
system and operate in the ’data lost’ mode.
406 z/OS V1R10.0 MVS System Codes
EC7 • FFx
v ReIPL the system. the software service level of that system. The
If you do restart the system, request a dump detecting system has requested that this
of the SMF address space. system be partitioned out of the sysplex. The
detecting system has also issued operator
01 Do one of the following: message BPXF077S indicating that this system
| v Perform a restart operation to restart the is executing with an incompatible software
| system. service level.
v ReIPL the system using the SMF=xx System action: Either this system or another system
parameter to provide empty SMF data sets in the sysplex issues operator messages about the
for SMF recording. problem.
If you do restart the system, SMF will start
Operator response: Refer to the console log of all
buffering data until a data set becomes
systems in this sysplex, including this system, for any
available. If no data sets become available,
messages associated with this wait state. Contact the
the system will eventually use up all
system programmer.
available storage for its internal buffers and
generate wait state code D0D, reason code System programmer response: Review the message
00. documentation associated with this wait state.
System programmer response: Use the IPCS Source: z/OS UNIX System Services
SMFDATA subcommand to retrieve the data that was in
the SMF buffers at the time of the error.
FFx
Source: System Management Facilities (SMF)
Explanation: Non-IBM programs can use wait state
codes X'FF0' through X'FFE'.
EC7
Operator response: See installation-supplied
Explanation: A severe error has occurred in the z/OS information for these codes.
UNIX System Services component that prohibits this
System programmer response: See
system from executing.
installation-supplied information for these codes.
The right-most four bytes of the program status word
Source: Non-IBM
(PSW) have the following format:
x0rrrwww
where:
x Irrelevant information.
rrrr A hexadecimal reason code indicating the
reason for the failure.
www The wait state code (EC7).
The reason code is as follows:
001 Shared file system support is enabled by the
SYSPLEX(YES) parmlib statement that is
specified in the BPXPRM parmlib member
used to initialize the system. The shared file
system support has detected that it is
executing with a software service level that is
incompatible with the software service level of
at least one active system in the sysplex that is
also configured for shared file system support.
Operator message BPXF078W is issued to the
system console.
002 Shared file system support is enabled by the
SYSPLEX(YES) parmlib statement that is
specified in the BPXPRM parmlib member
used to initialize the system. The shared file
system support on another active system has
detected that this system is executing with a
software service level that is incompatible with
Chapter 3. Wait State Codes 407
408 z/OS V1R10.0 MVS System Codes
Chapter 4. System Completion Code to Module Table
This table correlates system completion codes with module numbers. For each system completion code,
the associated component and detecting module are listed.
If the system completion code you require does not appear in the table, contact the IBM Support Center.
Provide the system completion code.
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
00B Scheduler restart IEFXBCHK IEFXBDYS
IEFXBGDG IEFXBRDC
IEFXBSJX IEFXBSWA
IEFXBSWB IEFXBUSJ
00C 16xx00xx XCF IXCA3ARP IXCA3ASE
IXCA3ASS IXCA3CKW
IXCA3ECU IXCA3ERS
IXCA3EV IXCA3MST
IXCA3FAI IXCA3GAP
IXCA3INT IXCA3IOX
IXCA3IO2 IXCA3IO3
IXCA3IO6 IXCA3MSI
IXCA3PCC IXCA3PCT
IXCA3REG IXCA3RGT
IXCA3RPR IXCA3SAP
IXCA3SG0 IXCA3SJT
IXCA3TOP IXCA3WPD
IXCA3XRP IXCM2TMR
00D 01 02 03 04 05 101 102 CTRACE ITTCT
012 Timer supervision IEATTUSD
01D RSM IARCA IARCD IARCF
IARCI IARCL IARCR
IARCS IARCV IARCW
IARCX IARCZ IARDD
IARDK IARDM IARDO
IARDP IARDR IARDS
IARDT IARDU IARFF
IARSO IARXG
022 Vector processing IGTDSR
023 CSV CSVLLBLD CSVLLCPY
CSVLLDCL CSVLLDSB
CSVLLDYN CSVLLEXT
CSVLLINF CSVLLIN2
CSVLLPRS CSVLLREF
CSVLLSCH CSVLLSTA
CSVLLSTC CSVLLST2
CSVLLTRC
025 Initiator IEFSD161 IEFIB600
ILRSWAP
028 ASM IARCE IARDO IARDP
IARDX IARFA IARFP
IARFS IARFZ IARMA
IARPF IARPM IARPU
IARPX IARSR IARYA
IARXV
© Copyright IBM Corp. 1988, 2009 409
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
029 ASM ILRPOS
02C JES2 HASPFSSM HASPWARM
02E AVM AVFGB AVFGR AVFIC
AVFIW AVFJB AVFKO
AVFKP AVFKS AVFLA
AVFLR AVFLT AVFMB
AVFMC AVFME AVFMF
AVFMG AVFMH AVFML
AVFMN AVFMS AVFNS
AVFNY AVFPC AVFSI
AVFSQ AVFSR AVFSS
AVFSW AVFSX AVFTA
AVFTB AVFTD AVFUT
AVFWA AVFWM
03C RSM IARFF IARFP
047 Supervisor control IEAVESVC
04B TSO/E IKJEFTSL IKJTSLAR
04E DFP
04F DFP DSNWDSDM DSNWSDWA
DSNYESWE DSN3RDMP
DSN3RDMP DSN3RDMP
DSN3RDMP DSN3RDMP
051 TSO/E
052 PC/AUTH IEAVXLRE
053 PC/AUTH IEAVXLRE
054 SJF IEFSJBLD IEFSJDEF
IEFSJDEL IEFSJFND
IEFSJJDV IEFSJEXT
IEFSJGET IEFSJIRT
IEFSJPUT IEFSJRET
IEFSJUPD IEFSJVAL
IEFSJWRT IEFSJINT
055 30 34 36 40 52 ENF IEFENFNM IEAVNP47
058 00 04 08 0C 10 28 2C Supervisor control IEAVECMS
30 34 38
058 14 18 1C Supervisor control IEAVESSE
058 20 Supervisor control IEAVEDSR
058 24 Supervisor control IEAVEE1R
059 Supervisor control IEAVESRT
05B Timer supervision IEAVRTI0
05D Supervisor control IEAVECMS
05E Supervisor control IEAVESTS
064 Supervisor control IEAVLKRM
065 Task management IEAVESSI
066 Supervisor control IEAVEDSR
06B Loadwait IEEVEXSN
06C RTM IEAVTSLP
410 z/OS V1R10.0 MVS System Codes
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
06D RTM IEAVTADR
06E RTM IEAVTGLB IEAVTLCL
06F RTM IEAVTRT1
070 Supervisor control IEAVETCL
071 Loadwait IEAVEREX
072 Supervisor control IEAVEDS0
073 Supervisor control IEAVESLK IEAVELK
IEAVELKB
074 Supervisor control IEAVESLR
075 Supervisor control IEAVESC0
076 Supervisor control IEAVEMCR
| 077 Console services Various console services
| modules
078 RCT IEAVAR00 IEAVAR02
079 RCT IEAVAR04
07A RCT IEAVAR00 IEAVAR02
07C Supervisor control IEAVESPR
07E Reconfiguration IEEVDEV
07F Task management IEAVECH0
080 RSM IARDM IARDT IARFS
IARKC IARKI IARKM
IARMA IARMS IARPI
IARPV IARRI IARRQ
IARSC IARSH IARSI
IARSO IARSQ IARSR
IARSU IARSX IARVF
IARXM IARXV IARXW
IARYB IARYF
083 ASM ILRSLSQA
084 ASM ILRCMP ILRSWPDR
085 ASM ILRSAV
086 ASM ILRVSAMI
087 ASM ILRSAV ILRACT ILRRLG
ILRVSAMI ILRTMRLG
089 ASM ILRCMP ILRCMP01
08B DIV ITVCC ITVCD ITVCF
ITVRA ITVRB ITVRE ITVRF
ITVRR ITVSA ITVSB ITVSF
ITVSG ITVSI ITVSL ITVSM
ITVSU ITVTR ITVTS
ITVXM ITVXN
08F RSM IARXK
09D System trace IEAVETRC
Chapter 4. System Completion Code to Module Table 411
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
09E System trace IEAVETAC IEAVETAI
IEAVETIH IEAVETEA
IEAVETPA IEAVETSP
IEAVETSN IEAVETPS
IEAVETRR IEAVETSD
IEAVETTF IEECB924
IEECB925 IEAVETFC
IEAVETEF IEAVETFA
IEAVETVP IEAVETNP
IEAVETPW IEAVETRW
IEAVETCV IEAVETPV
ITRFHEX ITRFBR
ITRF0001 ITRF0003
ITRF0005 ITRF0007
ITRF000B ITRF000F
ITRF0013 ITRF0015
ITRF0017 ITRF0019
ITRF001B
09F Supervisor control IEAVEVS IEAVVSR
0A0 01 02 03 Initiator IEFSD161 IEFSD164
IEFSD263
0A1 DFP IGG0193Y
0A2 DFP IGG0203Y
0A3 DFP IGG019OE
0A4 DFP IGG019OE
0A5 DFP IGG019OE
0AE IOS IOSVRSTS
0B0 SWA manager IEFQB551 IEFQB556
IEFQB580
0B1 SSI IEFJACTL IEFJCNTL
IEFJJCLS IEFJJOBS
IEFJWTOM
0B2 SSI IEFJJOBS
0B3 SSI IEFJACTL
0B4 SSI IEFJCNTL
0B5 SSI IEFJCNTL
0B7 Reconfiguration IEEVCPR IEEVCONF
IEECB927 IEEVCPLF
IEEVVFLF IEEVCPLN
IEEVCVSR IEEVTOD
IEEVCPRA IEEVCVPH
IEEVCPVF IEEVCRLF
IEEVMSI. IEEVCPUT
IEEVEXTR
0B6 OAM CBRLLCAN CBRLLDMT
CBRLLERR CBRLLMT
CBRLLMTL CBRLLVER
CBRLLWT
0B8 Master scheduler IEEPRWI2
0B9 Master scheduler IEESB605
412 z/OS V1R10.0 MVS System Codes
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
0BA Master scheduler Initiator IEESB605 IEFSD161
IEFSD162 IEFSD166
0BB Initiator IEFSD263
0BF Master scheduler IEEMB816
0Cx Supervisor control IEAVEPC.
0D2 Supervisor control IEAVEPC
0D3 Supervisor control IEAVEPC
0D5 RSM PC/AUTH IARDX IARPE IARYB
0D9 COMMTASK IEAVPIX
0F2 IOS IECVPST
0F6 GTF AHLSETEV
0F7 JES2 IECVPST IECVPST
IECVPST IECVPST
IECVPST IECVPST
0F8 Supervisor control IEAVESVC
0F9 Supervisor control IEAVESVC
0FB Supervisor control IEAVEPC
0FD Supervisor control IEAVESVC
0FF Supervisor control IEAVMVC0
101 Task management IEAVEWAT
102 Task management IEAVEPST
104 VSM IGVGLSQA
106 CSV CSVGETMD
10A VSM IGVGLSQA
10B Timer supervision IEAVRT01
10D RTM IEAVTRTC
10E RTM IEAVTESP
110 IOS IOSPURGA
121 IOS IGC0003C
122 Master scheduler IEE3703D
128 Task management IEAVTB00
12A Task management IEAVEAT0
12C Task management IEAVECH0
12E Timer supervision IEAVRT00
12F Timer supervision IEAVRT00
130 GRS ISGGNRM ISGGFP
133 Dumping services IEAVAD00 IEAVTSDX
138 GRS ISGGNRM
13C RTM IGC00060
13E Task management IEAVEED0
147 DFP IGC0007A
149 DFP IGC0007C
Chapter 4. System Completion Code to Module Table 413
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
14A DFP IGC0007D
14B DFP IGC0007E
14C 01 10 11 System Environmental Recording IFBBLD76 IFBSMFNT
(LOGREC)
14F Task management IEAVSETS
153 SMF IFASMFDT
157 Console services CNZS1DOM IEAVBWTO
15C EXCP IECVEXCP
15F SRM IRARMINT
16B Task management IEAVMODE
16D Supervisor control IEAVESVC
171 RSM IARPF IARPI IARPR IARPS
IARPU IARPV IARXW
172 EXCP IECVEXCP
177 Task management IEAVTEST
178 VSM IGVGLSQA
17A Task management IEAVEVT0
17B Supervisor control IEAVEPD0
17D Task management IEAVEVT0
182 RACF ICHRCK00
183 RACF ICHRIN00
185 RACF ICHRDF00
18A RSM IARPF IARPI IARPR IARPU
IARPV IARXV
1C5 00010001 System logger IXGA1WRT
1C5 00010002 System logger IXGA1WRT
1C5 00010003 System logger IXGA1SWT
1C5 00010004 System logger IXGA1DEL
1C5 00010005 System logger IXGA1SET
1C5 00020001 System logger IXGA1HSM
1C5 00020002 System logger IXGBLF01
1C5 00020003 System logger IXGBLF01
1C5 00030000 System logger IXGC3SEX
1C5 00030002 System logger IXGC3SEX IXGWORKT
1C5 00030003 System logger IXGC3SEX
1C5 00030004 System logger
1C5 00030006 System logger IXGF2EXT
1C5 00030009 System logger IXGC4RSC
1C5 00040001 System logger IXGF2WRT
1C5 00050001 System logger IXGI3DIR
1C5 00050002 System logger IXGI3DIR IXGI3RPT
1C5 00050003 System logger IXGI3DIR
414 z/OS V1R10.0 MVS System Codes
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
1C5 00060001 System logger IXGL1SRB
1C5 00070001 System logger IXGF1TRX
1C5 00070002 System logger IXGF1TRX
1C5 00070003 System logger IXGF1TRX
1C5 00070004 System logger IXGF1TRX
1C5 00070005 System logger IXGF1TRX
1C5 00070006 System logger IXGF1TRX
1C5 00070007 System logger IXGF1TRX
1C5 00070008 System logger IXGF1TRX
1C5 00070009 System logger IXGF1TRX
1C5 00070010 System logger IXGF1TRX
1C5 00070011 System logger IXGF1TRX
1C5 00070012 System logger IXGF1TRX
1C5 00070013 System logger IXGF1TRX
1C5 00070014 System logger IXGF1TRX
1C5 00070015 System logger IXGF1TRX
1C5 00070016 System logger IXGF1TRX
1C5 00080202 System logger IXGSDSIN
1C5 00080302 System logger IXGSDSIN
1C5 00080401 System logger IXGSDSOC
1C5 00080402 System logger IXGSDSOC
1C5 00080403 System logger IXGSDSOC
1C5 00080501 System logger IXGSDSUN
1C5 00080502 System logger IXGSDSUN
1C5 00080601 System logger IXGSDSGT
1C5 00080602 System logger IXGSDSGT
1C5 00080702 System logger IXGSEXIT
1C5 00080703 System logger IXGSEXIT
1C5 00080704 System logger IXGSEXIT
1C5 00080705 System logger IXGSEXIT
1C5 00080706 System logger IXGSEXIT
1C5 00080707 System logger IXGSEXIT
1C5 00080801 System logger IXGSXGET
1C5 00080802 System logger IXGSXGET
1C5 00090000 System logger IXGX1LSN
1C5 00090001 System logger IXGX1LSN
1C5 00090002 System logger IXGX1LSN
1C5 00090003 System logger IXGX1LSN
1C5 00090004 System logger IXGX1LSN
1C6 Task Management IEAVSETS
1FC Supervisor control IEAVESVR
Chapter 4. System Completion Code to Module Table 415
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
200 EXCP IECVEXFR
201 Task management IEAVEWAT
202 Task management IEAVEPST
204 VSM IGVGLSQA
205 VSM IGVGLSQA
206 CSV CSVGETMD
20A VSM IGVGLSQA
20D RTM IEAVTRTE
20E RTM IEAVTESP
20F IOS IECVPST
222 Master scheduler IEE3703D
228 Task management IEAVTB00
22A Task management IEAVEAT0
22C Task management IEAVECH0
22F Timer Supervision IEAVRTI0
230 GRS ISGGNRM ISGGFP
ISGGIFP
233 Dumping services IEAVAD00 IEAVTSDT
IEAVTSDX
238 GRS ISGGNRM ISGGFP
23E Task management IEAVEED0
247 DFP IGC0007A
| 253 SMF IEEMB830 IEEMB834
| IEEMB839
25F SRM IRARMERR
260 RCT IEAVAX00
271 RSM IARPV
278 VSM IGVGLSQA
27B Supervisor control IEAVEPD0
282 RACF ICHRCK00
283 RACF ICHRIN00
285 RACF ICHRDF00
28A RSM
2C6 IOS IOSVMIHQ IOSVPTHV
IOSVCDRI
2F3 Initiator IEFIB605
2FC Supervisor control IEAVEIOR
300 EXCP IECVEXCP
301 Task management IEAVEWAT
305 VSM IGVAAQAT
306 CSV CSVGETMD
30A VSM IGVAAQAT
416 z/OS V1R10.0 MVS System Codes
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
30E RTM IEAVTESP
312 CSV IGC018
322 SMF IEATLEXT
328 Task management IEAVTB00
32E Timer supervision IEAVRT00
330 GRS ISGGNRM
333 Dumping services IEAVTSDG IEAVTVSM
IEAVTSDH IEAVTSDL
IEAVTSDT
338 GRS ISGGNRM
33E Task management IEAVEED0
35F Initiator IEFSD263
378 VSM IGVAAQAT
37A Task management IEAVEVT0
37B Supervisor control IEAVEPDR
37D Task management IEAVEVT0
382 RACF ICHRCK00
383 RACF ICHRIN00
385 RACF ICHRDF00
3FC Supervisor control IEAVEE1R
400 DFP IECVEXCP
402 Task management IEAVEPST
406 CSV CSVSBRTN
40A VSM IGVVSMRF
42A Task management IEAVEAT0
430 GRS ISGGNRM ISGGRT
ISGGFP ISGGIFP
433 00000008 Dump Analysis and Elimination ADYTRNS
(DAE)
438 GRS ISGGNRM ISGGRT
ISGGFP ISGGIFP
43E Task management IEAVEED0
45F SRM IRARMEVT
46D RTM IEAVTESP
478 VSM IGVVSMRF
47A Task management IEAVEVT0
47D Task management IEAVEVT0
482 RACF ICHRCK00
483 RACF ICHRIN00
485 RACF ICHRDF00
4FC Supervisor control IEAVEPCR
500 EXCP IECVEXCP
Chapter 4. System Completion Code to Module Table 417
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
502 Task management IEAVEPST
504 VSM IGVVSM24
505 VSM IGVVSM24
522 SMF IEATLEXT
52A Task management IEAVEAT0
530 GRS ISGGNRM
538 GRS ISGGNRM
53E Task management IEAVEED0
553 SMF IEEMB839
55F SRM IRARMSRV
57D Task management IEAVEVT0
582 RACF ICHRCK00
585 RACF ICHRDF00
5FC Loadwait IEAVERER
604 VSM IGVVSM24
605 VSM IGVVSM24
622 TSO/E IKJEFLJ IKJEFLG
65F SRM IRARMCHM
67D Task management IEAVEVT0
683 RACF ICHRIN00
684 RACF ICHRSV00
685 RACF ICHRDF00
6FC Supervisor control IEAVEPC
700 EXCP IECVEXCP
702 Task management IEAVEPST
704 VSM IGVVSMRT
705 VSM IGVVSMRF
706 CSV CSVGETMD
70A VSM IGVVSMRF
71A DFP IGG0CLA9 IGG0CLA9
72A Task management IEAVEAT0
730 GRS ISGGNRM ISGGRT
738 GRS ISGGNRM ISGGRT
75F SRM IRARMINT
76D Dynamic Output IEFDOCNL
778 VSM IGVVSM31
77D Task management IEAVEVT0
7C4 JES3 IATCS01 IATCS03 IATCS04
7C6 IOS IOSVUSER
800 EXCP IECVEXCP
804 VSM IGVGSQA
418 z/OS V1R10.0 MVS System Codes
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
805 VSM IGVVSMRF
806 CSV CSVGETMD
80A VSM IGVGSQA
822 Initiator IEFSD263
82A Task management IEAVEAT0
830 GRS ISGGNRM
838 GRS IEAVENQ1
878 VSM IGVGSQA
87D Task management IEAVEVT0
8C4 04 JES IAZPJCL
905 VSM IGVVSMRF
906 CSV CSVSBRTN
90A VSM IGVVSMRF
922 Initiator IEFIB621
92A Task management IEAVEAT0
930 GRS ISGGNRM
938 GRS ISGGNRM
978 VSM IGVVSMRF
9C6 GRS ISGLOBTS ISGLRELS
ISGLPRGS ISGLCRTS
ISGLRTR ISGLTM
A00 EXCP IECVEXCP IECVEXFR
A03 RTM IEAVTSKT
A05 VSM IGVBDFE
A06 CSV CSVRBENQ
A0A VSM IGVBDFE
A22 Reconfiguration IEE3703D
A23 Console services IEAVMFRR
A78 VSM IGVBDFE
AC4 JES3 IATCNDB
AC7 01 Timer supervision IEAVRTI0
B00 EXCP IECVEXFR
B04 VSM IGVVSMRT
B05 VSM IGVVSMRF
B0A VSM IGVVSMRF
B23 Console services IEAVSTAA
B78 VSM IGVVSMRF
Chapter 4. System Completion Code to Module Table 419
Code (Hex) Reason Code (Hex) Associated Component Detecting Module
C0D RSM ASM PC/AUTH CSV IOS IARDG IARDP IAREI
SAM and others IARER IARFP IARGA
IARGD IARGI IARKE IARKI
IARKO IARKR IARKS
IARLS IARMB IARME
IARPB IARPH IARPP
IARPR IARRR IARRW
IARSC IARSI IARSO
IARSP IARSQ IARSS
IARSX IARUA IARUI
IARUM IARUR IARVF
IARXI IARXR IARXS
IARXW IARYA IARYR and
others
C22 EXCP IECVEXCP
C78 VSM IGVSLIST IGVCPBLD
CFB JES3 IATABMN
D04 VSM IGVAAQAT
D05 VSM IGVFLSQA
D06 CSV CSVSBRTN
D0A VSM IGVAAQAT
D0D RTM IEAVTRTE
D22 Master scheduler IEE0003D
D23 Console services CNZS1WTO IEAVBWTO
IEAVBNLK IEAVBWGL
| IEAVBLWT IEAVG715
| IEAVM613 IEAVM619
| IEAVNPGD CNZQ1MTC
| D24 Console services IEEMB804
D78 VSM IGVAAQAT
DFB JES3 IATFCLT
E00 EXCP IECVEXCP
E03 RTM IEAVTSKT
E23 Console services IEAVVRP2
EFB JES3 IATCNDAL IATCNDIT
IATCNDMS IATCNDTR
420 z/OS V1R10.0 MVS System Codes
Chapter 5. Wait State Code to Module Table
This table correlates wait state codes with module numbers. For each code, the associated component
and detecting module are listed.
If the wait state code you require does not appear in the table, contact the IBM Support Center. Provide
the wait state code.
Code (Hex) Associated Component Detecting Module
002 IOS IEAIPL00
003 IPL, IOS IEAIPL00 IEAIPL03
004 IOS IEAIPL03
005 IPL IEAIPL00
006 IPL IEAIPL00
007 Console services IEAVNPCA
009 NIP IEAVNPC4
00A IPL IEAVNP03
00B Master scheduler IEEVIPL
00D Master scheduler IEEVIPL
00E IPL IEAIPL00
014 Supervisor control IEAVEPCO IEAV9PCO
017 IPL IEAIPL00
019 IPL IEAIPL00
01B RTM IEESTPRS
01C Supervisor control IEAVESPR
020 Reconfiguration IEAVNP27
021 IOS IEAVNPM2
022 IOS IECVDAVV
023 System trace IEAVNP51
024 MCH IGFPTREC
025 IPL IEAIPL41
028 IOS IEAIPL40
02E ASM ILRMSG00
030 NIP IEAVNIP0
031 IOS IEAIPL03
032 NIP IEAVNIPM IEAVNIP0
033 NIP IEAVNIPM IEAVNIP0
035 IOS IEAIPL03
037 System Environmental Recording IEAVNP76
038 ASM IPL IEAIPL00 IEAVNP05 ILRASRIM
039 IOS IEAVNPM3
03A CSV IEAVNP05
03B CSV IEAVNP05
© Copyright IBM Corp. 1988, 2009 421
Code (Hex) Associated Component Detecting Module
03C ASM ILRASRIM ILRIODRV ILRMSG00
03D VSM IEAVNP08
03E ASM ILRTMI00
03F NIP IEAVNPM2
040 NIP IEAVNIPM
044 NIP IEAVNIP0
045 RTM IEAVNIPM
046 NIP IEAVNIP0
04A NIP IEAVNIP0
050 Loadwait IGFPTSIG
051 ACR IGFPTERM
052 ACR IGFPTERM
053 IOS IPL NIP IEAIPL03 IEAIPL99 IEAVNIP0 IOSIUCB
054 IPL IEAIPL02
055 IOS IPL IEAIPL31 IEAIPL41 IEAIPL02 IEAIPL40
059 NIP IEAVNIP0
05C DFSMSdfp IEAVNP11
05D DFSMSdfp IEAVNP11
05E DFSMSdfp IEAVNP11
05F DFSMSdfp IEAVNP11
060 ASM ILRASRIM
061 ASM ILRASRIM
062 IOS IOSRCHPR
063 ASM IEAVNP03 IEAVNP11 IEAVNP19 ILRASRIM
064 NIP IEAVNIPM IEAVNIP0
065 NIP IEAVNIPM
06F IOS IOSVMSLG
070 IPL IEAIPL00
071 IPL IEAIPL41
072 IPL, IOS IEAIPL30 IEAIPL41 IEAIPL40 IEAIPL43
IEAIPL46 IEAIPL70 IEAIPL71 IEAIDRIA
IOSISTOR
073 IPL IEAIPL00
074 IPL,IOS IEAIPL35 IEAIPL00 IEAIPL02 IEAIPL03
075 IPL IEAIPL00
076 IPL IEAIPL00
077 IEAIPL07
079 IOS IEAIPL40
07B NIP IEAVNIP0
07D NIP IEAVNPCF
07E Supervisor Control IEAVESVC IEAV9SVC
422 z/OS V1R10.0 MVS System Codes
Code (Hex) Associated Component Detecting Module
081 IPL IEAIPL00
| 082 Console services IEAVG603 IEAVN703
083 Supervisor control IEAVESAR
084 RTM IGFPEMER
085 ASM ILRASRIM ILRASRIM
| 087 Console services IEAVG603 IEAVG604 IEAVG605 IEAVG610
| IEAVG611 IEAVM605 IEAVM613 IEAVM616
| CNZQ1CNQ IEAVMFRR CNZQ1MT2
| CNZI1DLI CNZM1TIM CNZM1TSK
| CNZM1TST CNZQ1DCQ CNZQ1SLG
| CNZX1MGX IEAVN701 CNZX1MIG
| IEAVN703 IEECVSMA IEEVWAIT
088 IPL IEAIPL50
08A Console services IEAVBLWT
08B IOS IEAIPL40
08C WLM IWML2LWT
08E SRM IEAVNP10 IRARMERR
08F Supervisor Control IEAVEGR
09x Loadwait IEEVEXSN
0A1 Loadwait IEEVEXSN
0A2 XCF IXCI2IST IXCI2ETX IXCI2PH1
0A3 GRS ISGNLD
0A4 Timer supervision IEATESC2 IEATESCH
0B0 IOS IEAIPL43
0B1 IOS IOSIOFR IEAIPL43
0B2 IOS IEAIPL71
0B3 IPL IEAIPL49
0B4 IOS IOSIUCB
0E1 Loadwait/Restart IEEVSTOP
0E3 VSM IEAVNP08
0E8 MCH IEAVNP06
101 VSM IEAVGM00
102 VSM IEAVGM00
104 Supervisor control IEAVESVR
110 IOS IOSRHREC
111 IOS IOSRHREC
112 IOS IOSRHREC
113 IOS IOSRCHPR
114 IOS IOSRCHPR
115 IOS IECVPST IOSVDAVV IECVPST
116 IOS IOSVRSTS
200 ALC IEFAB4I0 IEFEB400
Chapter 5. Wait State Code to Module Table 423
Code (Hex) Associated Component Detecting Module
201 Console services IEAVN700
202 Console services IEAVN701
204 Allocation IEAIPL08
206 Timer IEAVNP21
5C7 Loadwait/Restart BLWLDWT BLWPTERM BLWPTSIG
BLWRSTOP
A00 RTM RTM
A01 MCH IGFPMCIH
A19 IOS IOSRMCH
A1E Timer supervision NIP IEATESC2 IEAVRTOD IEATVTOD IEATTSCH
IEATTFDH IEATESCH IEAVNIP0
A1F Timer supervision IEATESC2
A20 RSM IARMN
A21 RSM IARMN
A22 Master scheduler IEEVDCSR
A23 MCH IGFPMAIN
A24 MCH IGFPMAIN
A26 MCH IGFPMAIN
A27 Loadwait/Restart IEEVSTOP
A28 MCH IGFPMCIH
A29 Loadwait IGFPTERM
A2A RSM IEAVNPD8
A2B MCH IGFPMAIN
| A2C RSM IARMN
A70 Console services IEAVBWTO
A7A Service processor interface ISNAINIT ISNATACH ISNDAMAG ISNIH
ISNIRIM ISNMSI ISNRIM
B23 IOCP IEAVSTAA
CCC Loadwait IEEMPS03
D0D SMF IEEMB829
FF0 Installation-provided N/A
FF1 Installation-provided N/A
FF2 Installation-provided N/A
FF3 Installation-provided N/A
FF4 Installation-provided N/A
FF5 Installation-provided N/A
FF6 Installation-provided N/A
FF7 Installation-provided N/A
FF8 Installation-provided N/A
FF9 Installation-provided N/A
FFA Installation-provided N/A
FFB Installation-provided N/A
424 z/OS V1R10.0 MVS System Codes
Code (Hex) Associated Component Detecting Module
FFC Installation-provided N/A
FFD Installation-provided N/A
FFE Installation-provided N/A
Chapter 5. Wait State Code to Module Table 425
426 z/OS V1R10.0 MVS System Codes
Chapter 6. Stand-Alone Dump Wait State Codes
When producing a stand-alone dump, a stand-alone dump program loads wait state codes into the PSW to
tell the operator about certain problems.
In z/Architecture mode, the PSW for one of these wait states has the format:
X'00020000 00000000 00000000 00wwrrrr'
2 Bits 12-15 (the CMWP bits).
ww The hexadecimal wait state code.
rrrr The hexadecimal reason code.
Wait State Reason
Code Code Explanation Operator Response
21 0000 The stand-alone dump program is waiting None.
for I/O on the IPL device.
22 0000 The stand-alone dump program is waiting Ready the IPL device.
for intervention on the IPL device.
24 The stand-alone dump program detected If the dump program did not issue
an error. message AMD005I, try a system restart. If
system restart fails, reIPL the stand-alone
dump program, preferably from a different
volume.
0100 The stand-alone dump program cannot Use another volume or regenerate the
read the volume label. label. Other data sets on the volume
might be unusable.
0200 The volume label is nonstandard. Use another volume or regenerate the
label. Other data sets on the volume
might be unusable.
0300 The stand-alone dump program cannot Use another volume or change the DSCB.
read the format 4 data set control block Other data sets on the volume might be
(DSCB). unusable.
0400 The system does not support the IPL Use a device type that the system
device type. supports.
0500 The SYS1.PAGEDUMP data set is not on None.
the IPL volume.
0600 The stand-alone dump program cannot None.
read the stand-alone dump common
communication table (CCT).
0700 The stand-alone dump program cannot None.
write to the stand-alone dump file.
For a tape IPL version, this could be due If tape IPL, check for the needed write
to a missing write ring in the IPL volume. ring, or disable file protection.
0800 The stand-alone dump program cannot None.
read module AMDSARDM.
0900 The stand-alone dump program cannot None.
read module AMDSADIP.
0A00 The stand-alone dump program cannot None.
read module AMDSAPGE.
© Copyright IBM Corp. 1988, 2009 427
Wait State Reason
Code Code Explanation Operator Response
25 0200 A program check or other unexpected None.
error was detected during output DASD
dump data set processing. The system
ends the dump.
27 0010 The validity check of the devices and None.
dump options table (DDO) failed after the
system loaded it from SYS1.PAGEDUMP.
The system ends the dump.
0020 The validity check of the dump relocation None.
table (RLT) failed after the system loaded
the AMDSAPGE load module from
SYS1.PAGEDUMP. The system ends the
dump.
0030 An error occurred while the system read None.
the AMDSAPGE load module from
SYS1.PAGEDUMP The system ends the
dump.
0040 The system detected an internal logic None.
error in the SADMP dump initialization
program. The system ends the dump.
28 0100 The DASD IPL program is unable to read None.
the label on the IPL device. The system
ends the dump.
0200 The DASD IPL program encountered a None.
non-standard label on the IPL device. The
system ends the dump.
0300 The DASD IPL program is unable to read None.
the format 4 data set control block
(DSCB) on the IPL device. The system
ends the dump.
0400 The DASD IPL program detected an None.
unsupported device type for the IPL
device. The system ends the dump.
0500 The DASD IPL program could not locate None.
SYS1.PAGEDUMP on the IPL device. The
system ends the dump.
0600 The DASD IPL program could not read None.
the stand-alone dump common
communication table (CCT) from the IPL
device. The system ends the dump.
0700 A permanent I/O error occurred while None.
performing I/O to the SYS1.PAGEDUMP
work file on the DASD IPL device. The
system ends the dump.
0800 A permanent I/O error occurred while None.
performing I/O to the SYS1.PAGEDUMP
work file on the DASD IPL device. The
system ends the dump.
0900 A program check or other unexpected None.
error was encountered in the DASD IPL
module or subroutine. The system ends
the dump.
428 z/OS V1R10.0 MVS System Codes
Wait State Reason
Code Code Explanation Operator Response
0A00 The work file interface in the DASD IPL None.
module was passed incorrect parameters.
The system ends the dump.
0B00 The DASD IPL program detected an error None.
when performing a Sense-ID to the IPD
device. The system ends the dump.
0C00 The DASD IPL program could not read None.
the DAT validation and initialization
routine (AMDSADVI) from the IPL device.
The system ends the dump.
0D00 The DASD IPL program could not write None.
page 1 to the work file on the IPL device.
The system ends the dump.
0E00 The DASD IPL program could not read None.
the IPL initialization routine (AMDSAIPI)
from the IPL device. The system ends the
dump.
29 0700 The tape IPL module was unable to write None.
to the work file on the IPL tape. The
system ends the dump.
0800 The tape IPL module was unable to read None.
the dump program loader (AMDSADPL)
from the IPL tape. The system ends the
dump.
0900 A program check or other unexpected None.
error was encountered in the tape IPL
module or subroutine. The system ends
the dump.
0A00 The work file interface in the tape IPL None.
module was passed incorrect parameters.
The system ends the dump.
0C00 The tape IPL program could not read the None.
DAT validation and initialization routine
(AMDSADVI).
0D00 The tape IPL program could not write None.
page 1 to the work file on the IPL device.
The system ends the dump.
0E00 The tape IPL program could not read the None.
IPL initialization routine (AMDSAIPI) from
the IPL device. The system ends the
dump.
31 dddd The stand-alone dump program is waiting None.
for I/O to the device.
32 dddd The stand-alone dump program is waiting Mount and ready a tape.
for intervention on the device.
33 0mmm The stand-alone dump program is waiting Reply to the message.
for a reply to message AMDmmmA or
AMDmmmD.
34 dddd The stand-alone dump program detected None.
an I/O error on the device and is waiting
for a sense command to complete.
Chapter 6. Stand-Alone Dump Wait State Codes 429
Wait State Reason
Code Code Explanation Operator Response
35 dddd The stand-alone dump program restarted None.
I/O on the device and is waiting for I/O to
complete.
36 0100 The output tape is labelled and cannot be Mount another tape and ready it.
used.
0200 The output tape needs a file protect ring. Insert a ring into the tape and ready it, or
disable file protection.
0300 The output tape is full. Save the previous tape and mount a new
one.
37 0ddd The stand-alone dump program is waiting None.
for I/O that is neither a sense nor a restart
to complete on the device.
| 38 0000 The stand-alone dump program is waiting None.
| for I/O to complete on any of the output
| devices.
3E 0000 The system is waiting for one of the Select the system console or press
following: ENTER on one of the consoles defined in
v An attention interrupt from the operator the AMDSADMP macro. If a console is
selected console not available, ready a tape on the tape
v An interrupt from the system console drive that you defined on the AMDSADMP
v An external key interrupt to indicate a macro, then cause an external
no-console condition. interruption.
0100 All storage was cleared to binary zeroes None. If SADMP is restarted at this point,
prior to the loading of stand-alone dump. a dump will be produced that contains the
central processor status records, a
summary of the cleared storage, and the
stand-alone dump message log.
0200 The default console was not usable. To restart, clear the load parm and
Either the device specified in the load perform a restart.
parm was not found, or an I/O occurred
when trying to write to the device. The
system ends the dump.
3F 0100 The generated output device cannot be None.
used, and due to a no-console condition,
a replacement cannot be specified. The
system ends the dump.
0101 The generated output DASD data set is Do one of the following:
not initialized and REUSEDS=NEVER v Reinitialize the output data set from
was specified on the AMDSADMP macro. another system and perform a system
Because of a no-console condition, a restart.
replacement cannot be specified. The
v Perform a system restart and select a
system ends the dump.
usable console so that a different
output device can be specified.
0102 The generated output DASD data set is Do one of the following:
initialized and REUSEDS=CHOICE was v Reinitialize the output data set from
specified on the AMDSADMP macro. another system and perform a system
Because of a no-console condition, restart.
SADMP cannot issue message AMD096A
v Perform a system restart and select a
to determine if the data set should be
usable console so that SADMP can
reused.
issue AMD096A.
430 z/OS V1R10.0 MVS System Codes
Wait State Reason
Code Code Explanation Operator Response
0200 A program check or other unexpected None.
error was detected during output device
initialization. The system ends the dump.
40 0100 The generated output device address is None.
not usable, and due to a no-console
condition, a replacement cannot be
specified. The system ends the dump.
0200 A program check or other unexpected None.
error was detected during output device
address processing. The system ends the
dump.
41 0000 The SADMP program ended normally; Save the dump.
dumping is complete.
Note: Message AMD104I can be an
indication of successful completion of
dump.
47 0000 An unexpected machine check occurred. Record the wait state code. If necessary,
rewind and unload the output tape; the
normal end-of-file is not present.
0001 An unrecoverable machine check with Record the wait state code. If necessary,
invalid registers occurred. rewind and unload the output tape; the
normal end-of-file is not present.
4F ssee The virtual storage dump program ended Record the wait state code. If necessary,
due to an internal error. rewind and unload the output tape; the
v ss denotes the failing module or normal end-of-file is not present.
service.
v ee denotes the specific type of error.
Common codes are listed below. The
stand-alone dump program tries to write a
self-dump to the output device. Message
AMD066I also contains these wait reason
codes.
0D01 An unexpected error occurred during None.
SADMP error recovery and program
ending processing.
0D02 The stand-alone dump program requested None.
too many self-dumps.
0D03 The system ended SADMP error recovery None.
and program ending processing because
of I/O errors.
0D05 The system did not find any SADMP error None.
recovery module on the recovery stack.
0E10 The system cannot continue processing None.
because there are not enough SADMP
internal storage blocks (BCT) on the
available queue.
0F01 A permanent I/O error occurred on the Perform a system restart to dump to
output DASD and the operator replied ’T’ another output device.
to message AMD098A.
Chapter 6. Stand-Alone Dump Wait State Codes 431
Wait State Reason
Code Code Explanation Operator Response
13F1 A permanent I/O error occurred on the Perform a system restart to dump to
output tape and the operator replied ’T’ to another output device.
message AMD098A.
14F1 A permanent I/O error occurred on the Perform a system restart to dump to
output tape, and the operator replied ‘T’ to another output device.
message AMD098A.
1C13 A system restart occurred. None.
1D12 An external interruption occurred. None.
1E20 The operator replied ‘T’ to message None.
AMD088D.
1E30 The prefix storage area (PSA) was None.
incorrect. The system cannot dump virtual
storage.
1E40 The segment table (SGT) was incorrect. None.
The system cannot dump virtual storage.
1E50 The page table (PGT) was incorrect. The None.
system cannot dump virtual storage.
1E60 The communication vector table (CVT) None.
was incorrect. The system cannot dump
virtual storage.
1E70 The paging vector table (PVT) was None.
incorrect. The system cannot dump virtual
storage.
1E80 The real storage manager (RSM) internal None.
table (RIT) was incorrect. The system
cannot dump virtual storage.
1E90 The page frame table (PFT) was None.
incorrect. The system cannot dump virtual
storage.
1EA0 No contiguous storage could be found for None.
a swap SGT. The system could not dump
virtual storage.
22F1 A permanent I/O error occurred on the Perform a system restart to dump to
output tape volume and the operator another output device.
replied ’T’ to message AMD098A.
4701 A program check or other unexpected None.
error was detected during dump title
processing. The system ends the dump.
ssF1 An I/O error occurred on the output Perform a system restart to dump to
device. another output device.
FEcc A program check occurred. cc is the None.
rightmost byte of the program interruption
code.
52 0200 The IPL initialization routine found a None.
non-standard label on the IPL device. The
system ends the dump.
0400 The IPL initialization routine found the IPL None.
device to be an unsupported device. The
system ends the dump.
432 z/OS V1R10.0 MVS System Codes
Wait State Reason
Code Code Explanation Operator Response
0500 The IPL initialization routine was unable to None.
locate the SYS1.PAGEDUMP.Vvolser on
the IPL device. The system ends the
dump.
0F00 The stand-alone dump program was None.
IPLed on a processor which does not
support z/Architecture.
Chapter 6. Stand-Alone Dump Wait State Codes 433
434 z/OS V1R10.0 MVS System Codes
Chapter 7. IPCS User Completion Codes
Use this procedure if IPCS processing ends with a user completion code. The code is 4 decimal digits.
Problems in either IBM-provided IPCS code or in installation exit routines can cause IPCS to issue an
abend. Do the following for most IPCS user completion codes:
1. Check to see if IPCS issued any messages that might provide more information about the problem.
These messages have the form of BLSnnnnnc, unless they were issued from an exit routine.
2. Look at the following explanation of the user completion code for a description of the problem. Follow
the diagnostic steps for the code.
3. Check for a failing installation exit routine.
v Use the IPCS TRAP subcommand to isolate problems relating to the use of exit services.
v If your installation provides exit routines, check the dump to see if one of them is identified as the
failing module.
The IPCSTOC file might contain information to help identify exits.
v If the problem appears to be in an installation exit routine, attempt to by-pass the problem by using
the NOTEST keyword.
v For an additional check:
– Remove all command options that cause installation exit routines to be invoked from the IPCS
input stream.
– Rerun IPCS. If the problem goes away, an installation exit routine probably has a logic problem.
If an installation exit routine caused the problem, use the dump data to isolate the reason for the
failure. Correct the exit routine.
The following list contains the IPCS completion codes:
Explanation: The system detected an error while
0100 (hexadecimal 064)
attempting to close the problem or data set directory.
Explanation: The system detected an error while
System action: A set of messages that describe the
attempting to open the problem or data set directory for
problem in more detail precedes the abend. The system
reading.
ends subcommand processing.
System action: The abend follows messages that
System programmer response: Follow the
indicate the nature of the problem. The system ends
programmer response for the BLS03nnnt messages that
subcommand processing.
precede the abend.
System programmer response: Follow the
programmer response for the BLS03nnnt messages that
0103 (hexadecimal 067)
precede the abend.
Explanation: The system detected an internal error.
0101 (hexadecimal 065) System action: The system ends subcommand
processing.
Explanation: The system detected an error while
attempting to get a record from the problem or data set System programmer response: Search problem
directory. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
System action: A set of messages that describe the
problem in more detail precedes the abend. The system
ends subcommand processing. 0104 (hexadecimal 068)
System programmer response: Follow the Explanation: An attempt was made to acquire a
programmer response for the BLS03nnnt messages that problem resource while either the problem directory or
precede the abend. the data set directory was open.
System action: The system ends subcommand
0102 (hexadecimal 066) processing.
© Copyright IBM Corp. 1988, 2009 435
0105 (hexadecimal 069) • 0113 (hexadecimal 071)
System programmer response: Search problem exists, contact the IBM Support Center.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0109 (hexadecimal 06D)
Explanation: A dump-directory equate-symbol record
0105 (hexadecimal 069)
was passed to a service routine to have an action
Explanation: The system detected an error during a performed on its contents. The record contents were
message production procedure. A reason code is in incorrect. The system issues the abend only if the TEST
general purpose register 15, as follows: operand is specified.
Reason Code Explanation System action: The system ends subcommand
processing.
60 The system could not obtain enough
storage for the current output System programmer response: Search problem
message. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
Other An internal problem occurred.
System action: The system does not issue the
0110 (hexadecimal 06E)
message. The system ends subcommand processing.
Explanation: The system detected an internal error.
System programmer response: If the reason code is
60, increase the region size and try again. If the System action: A message that indicates the type of
problem persists or if the reason code is other than 60, internal error detected precedes the abend. The system
search problem reporting data bases for a fix for the ends subcommand processing.
problem. If no fix exists, contact the IBM Support
System programmer response: Search problem
Center.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0106 (hexadecimal 06A)
Explanation: The system detected an I/O error during 0111 (hexadecimal 06F)
processing of a DELPROB subcommand. The type of
Explanation: Records passed for comparison do not
problem is indicated by one of the following messages:
contain the same VSAM key.
BLS04042I, BLS04043I, or BLS04045I and their
associated messages. System action: Message BLS04064I precedes the
abend. The system ends subcommand processing.
System action: The system ends DELPROB
subcommand processing. System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
System programmer response: Search problem
exists, contact the IBM Support Center.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0112 (hexadecimal 070)
0107 (hexadecimal 06B) Explanation: The system detected an internal error.
Explanation: The system detected an internal error. System action: Message BLS04061I precedes the
abend. The system ends subcommand processing.
System action: The system ends subcommand
processing. System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
System programmer response: Search problem
exists, contact the IBM Support Center.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0113 (hexadecimal 071)
0108 (hexadecimal 06C) Explanation: The system detected an error while
opening the data set directory. An attempt to free the
Explanation: The system detected an error while
data set directory did not succeed.
performing an open or close operation on the problem
directory during confirmation processing. System action: Message BLS04052I precedes the
abend. The system ends subcommand processing.
System action: Message BLS04042I or BLS04045I
precedes the abend. The system ends DELPROB System programmer response: Search problem
subcommand processing. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
436 z/OS V1R10.0 MVS System Codes
0114 (hexadecimal 072) • 0123 (hexadecimal 07B)
0114 (hexadecimal 072) 0119 (hexadecimal 077)
Explanation: The user instructed the IPCS attention Explanation: The system detected a permanent error
processor to issue a diagnostic abend by entering while attempting to close the data set directory.
’abend’.
System action: Message BLS04055I precedes the
System action: The system ends the IPCS session. abend. The system ends subcommand processing.
System programmer response: The purpose of the System programmer response: Search problem
IPCS attention-exit abend function is to permit reporting data bases for a fix for the problem. If no fix
diagnostic information to be collected regarding exists, contact the IBM Support Center.
apparent IPCS problems. Use the dump to confirm this
diagnosis.
0120 (hexadecimal 078)
Explanation: The system detected an error while
0115 (hexadecimal 073)
attempting to close the data set directory.
Explanation: The system detected an error while
System action: Message BLS04055I precedes the
reading the data set directory.
abend. The system ends subcommand processing.
System action: Message BLS04053I precedes the
System programmer response: Search problem
abend. The system ends subcommand processing.
reporting data bases for a fix for the problem. If no fix
System programmer response: Search problem exists, contact the IBM Support Center.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0121 (hexadecimal 079)
Explanation: The system detected an error while
0116 (hexadecimal 074)
attempting to open the problem directory. The attempt to
Explanation: The system detected an incorrect write free the problem directory was unsuccessful.
request while writing a record to the data set directory.
System action: Message BLS04042I precedes the
System action: Message BLS04054I precedes the abend. The system ends subcommand processing.
abend. The system ends subcommand processing.
System programmer response: Search problem
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix
reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
exists, contact the IBM Support Center.
0122 (hexadecimal 07A)
0117 (hexadecimal 075)
Explanation: The system could not obtain enough
Explanation: The system detected a permanent write virtual storage.
problem while writing a record to the data set directory.
System action: Message BLS04015I precedes the
System action: Message BLS04054I precedes the abend. The system ends subcommand processing.
abend. The system ends subcommand processing.
System programmer response: Ensure that the
System programmer response: Search problem region size is large enough for IPCS execution.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0123 (hexadecimal 07B)
Explanation: The system detected an error while
0118 (hexadecimal 076)
reading the problem directory.
Explanation: The system detected an error while
System action: Message BLS04043I precedes the
attempting to write a record to the data set directory.
abend. The system ends subcommand processing.
System action: The informational message
System programmer response: Search problem
BLS04054I precedes the abend. The system ends
reporting data bases for a fix for the problem. If no fix
subcommand processing.
exists, contact the IBM Support Center.
System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
Chapter 7. IPCS User Completion Codes 437
0124 (hexadecimal 07C) • 0134 (hexadecimal 086)
0124 (hexadecimal 07C) 0129 (hexadecimal 081)
Explanation: The system detected an incorrect write Explanation: The system detected an internal error.
request while attempting to write to the problem
System action: The system ends subcommand
directory.
processing.
System action: Message BLS04044I precedes the
System programmer response: Search problem
abend. The system ends subcommand processing.
reporting data bases for a fix for the problem. If no fix
System programmer response: Search problem exists, contact the IBM Support Center.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0130 (hexadecimal 082)
Explanation: The system detected an internal error.
0125 (hexadecimal 07D)
System action: The system ends subcommand
Explanation: The system detected a permanent write
processing.
error while writing a record to the problem directory.
System programmer response: Search problem
System action: Message BLS04044I precedes the
reporting data bases for a fix for the problem. If no fix
abend. The system ends subcommand processing.
exists, contact the IBM Support Center.
System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
0131 (hexadecimal 083)
exists, contact the IBM Support Center.
Explanation: The system detected an internal error.
0126 (hexadecimal 07E) System action: The system ends subcommand
processing.
Explanation: A problem occurred while writing a
record to the problem directory. System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
System action: Message BLS04044I precedes the
exists, contact the IBM Support Center.
abend. The system ends subcommand processing.
System programmer response: Search problem
0132 (hexadecimal 084)
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Explanation: The system detected an error while
attempting to write a record into a data set. The
messages that precede this abend specify in more
0127 (hexadecimal 07F)
detail the nature of the problem.
Explanation: The system detected a permanent error
System action: The system ends subcommand
while closing the problem directory.
processing.
System action: Message BLS04045I precedes the
System programmer response: Search problem
abend. The system ends subcommand processing.
reporting data bases for a fix for the problem. If no fix
System programmer response: Search problem exists, contact the IBM Support Center.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0133 (hexadecimal 085)
Explanation: The system detected an internal error.
0128 (hexadecimal 080)
System action: Any existing messages on the
Explanation: The system detected an error while
message queue were routed to the terminal prior to the
attempting to close the problem directory.
abend. The system ends subcommand processing.
System action: Message BLS04045I precedes the
System programmer response: Follow the
abend. The system ends subcommand processing.
programmer response(s) for any messages issued prior
System programmer response: Search problem to the abend.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0134 (hexadecimal 086)
Explanation: The system detected an internal error.
System action: The system ends subcommand
processing.
438 z/OS V1R10.0 MVS System Codes
0135 (hexadecimal 087) • 0150 (hexadecimal 096)
System programmer response: Search problem
0141 (hexadecimal 08D)
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Explanation: The system detected an internal error.
System action: The system ends subcommand
0135 (hexadecimal 087) processing.
Explanation: The system detected an internal error. System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
System action: The system ends subcommand
exists, contact the IBM Support Center.
processing.
System programmer response: Search problem
0145 (hexadecimal 091)
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Explanation: The area pointed to by the control block
pointer specified in message BLS04072I does not
contain the specified control block.
0137 (hexadecimal 089)
System action: Message BLS04072I precedes the
Explanation: The system detected an error while
abend. The system ends subcommand processing.
attempting to close a data set. Messages that precede
this abend specify in more detail the nature of the System programmer response: Search problem
problem. reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
System action: The system ends subcommand
processing.
0147 (hexadecimal 093)
System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix Explanation: The system detected an internal error.
exists, contact the IBM Support Center.
System action: The system ends subcommand
processing.
0138 (hexadecimal 08A)
System programmer response: Search problem
Explanation: The system detected an error while reporting data bases for a fix for the problem. If no fix
attempting to open a data set. Messages that precede exists, contact the IBM Support Center.
this abend specify in more detail the nature of the
problem.
0148 (hexadecimal 094)
System action: The system ends subcommand
Explanation: The system detected an internal error.
processing.
System action: The system ends subcommand
System programmer response: Search problem
processing.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0139 (hexadecimal 08B)
Explanation: The system detected an internal error.
0149 (hexadecimal 095)
System action: The system ends subcommand
Explanation: The system detected an internal error.
processing.
System action: The system ends subcommand
System programmer response: Search problem
processing.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
0140 (hexadecimal 08C)
Explanation: The system could not close a data set.
0150 (hexadecimal 096)
System action: Message BLS03114I precedes the
Explanation: The system detected an internal error.
abend. The system ends subcommand processing.
Either the data set may not be closed or freed. System action: The system ends subcommand
processing.
System programmer response: If the data set is not
properly closed, use IDCAMS VERIFY to close it. If the System programmer response: Search problem
data set is not freed, issue a TSO/E FREE command. reporting data bases for a fix for the problem. If no fix
Chapter 7. IPCS User Completion Codes 439
0151 (hexadecimal 097) • 2052 (hexadecimal 804)
exists, contact the IBM Support Center. exists, contact the IBM Support Center.
0151 (hexadecimal 097) 2049 (hexadecimal 801)
Explanation: The system detected an internal error. Explanation: The system detected an internal error.
System action: Message BLS04014I precedes the System action: The system ends subcommand
abend. The system ends subcommand processing. processing.
System programmer response: Search problem System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. exists, contact the IBM Support Center.
0152 (hexadecimal 098) 2050 (hexadecimal 802)
Explanation: The system detected an internal error. Explanation: The system detected an internal error.
System action: Message BLS03102I precedes the System action: The system ends subcommand
abend. The system ends IPCS processing. processing.
System programmer response: Search problem System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. exists, contact the IBM Support Center.
0200 (hexadecimal 0C8) 2051 (hexadecimal 803)
Explanation: The system detected an internal error. Explanation: The system detected an internal error.
System action: The system ends subcommand System action: The system ends subcommand
processing. processing.
System programmer response: Search problem System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. exists, contact the IBM Support Center.
0201 (hexadecimal 0C9) 2052 (hexadecimal 804)
Explanation: The system detected an internal error. Explanation: The system detected an internal error.
System action: The system ends subcommand System action: The system ends subcommand
processing. processing.
System programmer response: Search problem System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. exists, contact the IBM Support Center.
0999 (hexadecimal 3E7)
Explanation: The system detected an internal error.
System action: The system ends subcommand
processing.
System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
2048 (hexadecimal 800)
Explanation: The system detected an internal error.
System action: The system ends subcommand
processing.
System programmer response: Search problem
reporting data bases for a fix for the problem. If no fix
440 z/OS V1R10.0 MVS System Codes
Appendix. Accessibility
Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision,
to use software products successfully. The major accessibility features in z/OS enable users to:
v Use assistive technologies such as screen readers and screen magnifier software
v Operate specific or equivalent features using only the keyboard
v Customize display attributes such as color, contrast, and font size
Using assistive technologies
Assistive technology products, such as screen readers, function with the user interfaces found in z/OS.
Consult the assistive technology documentation for specific information when using such products to
access z/OS interfaces.
Keyboard navigation of the user interface
Users can access z/OS user interfaces using TSO/E or ISPF. Refer to z/OS TSO/E Primer, z/OS TSO/E
User’s Guide, and z/OS ISPF User’s Guide Vol I for information about accessing TSO/E and ISPF
interfaces. These guides describe how to use TSO/E and ISPF, including the use of keyboard shortcuts or
function keys (PF keys). Each guide includes the default settings for the PF keys and explains how to
modify their functions.
z/OS information
z/OS information is accessible using screen readers with the BookServer/Library Server versions of z/OS
books in the Internet library at:
http://www.ibm.com/systems/z/os/zos/bkserv/
© Copyright IBM Corp. 1988, 2009 441
442 z/OS V1R10.0 MVS System Codes
Notices
This information was developed for products and services offered in the USA.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that only
that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
USA
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
Mail Station P300
2455 South Road
Poughkeepsie, NY 12601-5400
USA
© Copyright IBM Corp. 1988, 2009 443
Such information may be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.
The licensed program described in this information and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any
equivalent agreement between us.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Policy for unsupported hardware
Various z/OS elements, such as DFSMS, HCD, JES2, JES3, and MVS, contain code that supports specific
hardware servers or devices. In some cases, this device-related element support remains in the product
even after the hardware devices pass their announced End of Service date. z/OS may continue to service
element code; however, it will not provide service related to unsupported hardware devices. Software
problems related to these devices will not be accepted for service, and current service activity will cease if
a problem is determined to be associated with out-of-support devices. In such cases, fixes will not be
issued.
Trademarks
The following terms are trademarks of the IBM Corporation in the United States or other countries or both:
v AIX
v C/370
v CICS
v DB2
v DFSMS
v DFSMS/MVS
v DFSMSdfp
v DFSMSrmm
v FFST
v FlashCopy
v GDPS
v Hiperspace
v HyperSwap
v IBM
v IBMLink
v IMS
v MQSeries
v MVS
v MVS/SP
v NetSpool
v NetView
v OS/390
v Parallel Sysplex
v PR/SM
v Print Services Facility
v PrintWay
v RACF
v Resource Link
v REXX
v RMF
v SAA
v SOM
v SOMobjects
v SP
444 z/OS V1R10.0 MVS System Codes
v Sysplex Timer
v VTAM
v WebSphere
v z/Architecture
v z/OS
v z/VM
v zSeries
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.
Notices 445
446 z/OS V1R10.0 MVS System Codes
Readers’ Comments — We’d Like to Hear from You
z/OS
MVS System Codes
Publication No. SA22-7626-19
We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,
organization, subject matter, or completeness of this book. The comments you send should pertain to only the
information in this manual or product and the way in which the information is presented.
For technical questions and information about products and prices, please contact your IBM branch office, your IBM
business partner, or your authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use the
personal information that you supply to contact you about the issues that you state on this form.
Comments:
Thank you for your support.
Submit your comments using one of these channels:
v Send your comments to the address on the reverse side of this form.
v Send your comments via e-mail to: [email protected]
If you would like a response from IBM, please fill in the following information:
Name Address
Company or Organization
Phone No. E-mail address
___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
SA22-7626-19 Along Line
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL
FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
IBM Corporation
MHVRCFS, Mail Station P181
2455 South Road
Poughkeepsie, NY
12601-5400
_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
SA22-7626-19 Along Line
Program Number: 5694-A01
Printed in USA
SA22-7626-19
You might also like
- GC28-1780-10 OS390 MVS System Codes PDFNo ratings yetGC28-1780-10 OS390 MVS System Codes PDF320 pages
- GDB Internals: John Gilmore Cygnus Solutions Second Edition: Stan Shebs Cygnus SolutionsNo ratings yetGDB Internals: John Gilmore Cygnus Solutions Second Edition: Stan Shebs Cygnus Solutions113 pages
- IWF Metadata Harvester Manual: Laurence D. FinstonNo ratings yetIWF Metadata Harvester Manual: Laurence D. Finston181 pages
- IBM FlexSystem InterOp Guide Dec02-2014No ratings yetIBM FlexSystem InterOp Guide Dec02-201482 pages
- Manual For Version 1.8.10 Written by Dimitri Van Heesch ©1997-2015No ratings yetManual For Version 1.8.10 Written by Dimitri Van Heesch ©1997-2015224 pages
- zPDT-vol2-Installation and Basic Use-Sg247722 PDFNo ratings yetzPDT-vol2-Installation and Basic Use-Sg247722 PDF86 pages
- The Julius Book: Akinobu LEE May 17, 2010No ratings yetThe Julius Book: Akinobu LEE May 17, 201067 pages
- Programming the Photon: Getting Started with the Internet of ThingsFrom EverandProgramming the Photon: Getting Started with the Internet of Things5/5 (1)
- Presentations with LaTeX: Which package, which command, which syntax?From EverandPresentations with LaTeX: Which package, which command, which syntax?No ratings yet
- Smart Card Applications: Design models for using and programming smart cardsFrom EverandSmart Card Applications: Design models for using and programming smart cardsNo ratings yet
- Programming the Intel Galileo: Getting Started with the Arduino -Compatible Development BoardFrom EverandProgramming the Intel Galileo: Getting Started with the Arduino -Compatible Development Board5/5 (1)
- Programming Arduino Next Steps: Going Further with Sketches, Second EditionFrom EverandProgramming Arduino Next Steps: Going Further with Sketches, Second Edition3/5 (3)
- Programming Arduino: Getting Started with Sketches, Third EditionFrom EverandProgramming Arduino: Getting Started with Sketches, Third EditionNo ratings yet
- Building with Virtual LEGO: Getting Started with LEGO Digital Designer, LDraw, and MecabricksFrom EverandBuilding with Virtual LEGO: Getting Started with LEGO Digital Designer, LDraw, and MecabricksNo ratings yet
- Maina - Planning For Recreation and Open Space, Eastlands, NairobiNo ratings yetMaina - Planning For Recreation and Open Space, Eastlands, Nairobi163 pages
- CIAP-PCAB Citizen's Charter - AMO Seminar and Exam - 26sep2016 PDFNo ratings yetCIAP-PCAB Citizen's Charter - AMO Seminar and Exam - 26sep2016 PDF1 page
- 6th Grade Lesson Plan June 03 - June 07 MathNo ratings yet6th Grade Lesson Plan June 03 - June 07 Math4 pages
- Bernadith F. Fernandez: Address: 05 Salapingao Binmaley, Pangasinan Contact No: (0927) 235-8859No ratings yetBernadith F. Fernandez: Address: 05 Salapingao Binmaley, Pangasinan Contact No: (0927) 235-88593 pages
- DM GTU Study Material Presentations Unit-5 21052021124400PMNo ratings yetDM GTU Study Material Presentations Unit-5 21052021124400PM63 pages
- Rheological Properties and Stability of Emulsion Explosive MatrixNo ratings yetRheological Properties and Stability of Emulsion Explosive Matrix7 pages
- Culture Moves Europe Residency Call Application Form TemplateNo ratings yetCulture Moves Europe Residency Call Application Form Template14 pages
- Ch.03 Modeling in Time Domain - AssignmentNo ratings yetCh.03 Modeling in Time Domain - Assignment3 pages
- Capsaicin Recovery From A Cell Culture BrothNo ratings yetCapsaicin Recovery From A Cell Culture Broth5 pages
- The Sierra Leone Energy Sector: Prospects & ChallengesNo ratings yetThe Sierra Leone Energy Sector: Prospects & Challenges10 pages
- 03c_9FM0-3A_Further_Pure_Mathematics_1_mock_mark_schemeNo ratings yet03c_9FM0-3A_Further_Pure_Mathematics_1_mock_mark_scheme11 pages
- Validation: WHO Technical Report Series, No. 961, 2011. Annex 5No ratings yetValidation: WHO Technical Report Series, No. 961, 2011. Annex 548 pages
