GC28-1780-10 OS390 MVS System Codes PDF
Uploaded by
nyzhGC28-1780-10 OS390 MVS System Codes PDF
Uploaded by
nyzhOS/390 IBM
MVS System Codes
GC28-1780-10
OS/390 IBM
MVS System Codes
GC28-1780-10
Note
Before using this information and the product it supports, be sure to read the general information under Appendix A, “Notices” on
page A-1.
Eleventh Edition, December 1999
This is a major revision of GC28-1780-09.
This edition applies to OS/390 Version 2 (5647-A01), OS/390 Version 1 (5645-001), MVS/ESA System Product Version 5 (5655-068 or
5655-069), and to all subsequent releases and modifications until otherwise indicated in new editions.
Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address
below.
IBM welcomes your comments. A form for readers' comments may be provided at the back of this publication, or you may address your
comments to the following address:
International Business Machines Corporation
Department 55JA, Mail Station P384
522 South Road
Poughkeepsie, NY 12601-5400
United States of America
FAX (United States & Canada): 1+914+432-9405
FAX (Other Countries):
Your International Access Code +1+914+432-9405
IBMLink (United States customers only): IBMUSM10(MHVRCFS)
IBM Mail Exchange: USIB6TC9 at IBMMAIL
Internet e-mail: [email protected]
World Wide Web: http://www.ibm.com/s390/os390/
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:
Title and order number of this book
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, 1999. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Who Should Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
How to Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Code Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Location of User Completion Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Where to Find More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTRO-1
Completion Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTRO-1
Abend of a Task or Address Space . . . . . . . . . . . . . . . . . . . . . . . INTRO-1
Abend of a System Service . . . . . . . . . . . . . . . . . . . . . . . . . . . INTRO-1
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTRO-1
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTRO-1
Abnormal End of Subtasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTRO-1
Wait State Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTRO-2
Wait State Codes from a Stand-Alone Dump Program . . . . . . . . . . . . . . . INTRO-2
IPCS User Completion Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTRO-2
System Completion Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCC-1
Wait State Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WSC-1
System Completion Code to Module Table . . . . . . . . . . . . . . . . . . . . CMT-1
Wait State Code to Module Table . . . . . . . . . . . . . . . . . . . . . . . . . . WSM-1
Stand-Alone Dump Wait State Codes . . . . . . . . . . . . . . . . . . . . . . . SDW-1
IPCS User Completion Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . IPCS-1
Appendix A. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Copyright IBM Corp. 1988, 1999 iii
iv OS/390 V2R8.0 MVS System Codes
About This Book
This book describes the system completion codes and wait state codes issued by compo-
nents, products, and subsystems of OS/390. The book 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 Book
OS/390 MVS System Codes is for all people who receive abend and wait state codes from
the system. Usually, these people are system operators, system programmers, and applica-
tion programmers who do any of the following tasks:
Initialize the operating system and its subsystems
Keep the system running correctly
Diagnose and correct system problems
Diagnose and correct errors in problem programs
How to Use This Book
OS/390 MVS System Codes contains:
An introduction to the format of system and user completion codes and of wait state
codes
Descriptions of system completion codes issued by system components, products, and
subsystems
Descriptions of wait state codes loaded during system operation
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:
Explains why the code was issued.
Identifies the component, subsystem, or product issuing the code.
Describes the actions taken by the system.
Suggests actions that the operator, user, application programmer, or system pro-
grammer can take, if appropriate, in response to the code.
The system programmer responses assume that the programmer has performed the cus-
tomary diagnosis described in the OS/390 MVS Diagnosis: Procedures.
Location of User Completion Codes
OS/390 MVS System Codes does not contain the 4-digit decimal user completion codes that
some IBM-provided components, subsystems, or products issue. These codes appear in
books for the component, subsystem, or product that issues the codes. Codes issued by
installation-provided programs do not appear in IBM books.
Copyright IBM Corp. 1988, 1999 v
Where to Find More Information
Where necessary, this book references information in other books, using the shortened
version of the book title. For complete titles and order numbers of the books for all products
that are part of OS/390, see OS/390 Information Roadmap.
The following table lists the titles and order numbers of books for other IBM products.
Order
Title Number
IBM Graphics Access Method/System Product: Messages and Codes SC33-0143
IBM Enterprise Systems Architecture/390 Principles of Operation SA22-7201
IBM Enterprise Systems Architecture/370 Principles of Operation SA22-7200
Print Services Access Facility for MVS User's Guide and Reference S544-3100
vi OS/390 V2R8.0 MVS System Codes
Summary of Changes
| Summary of Changes
| for GC28-1780-10
| as Updated December, 1999
| online only for SK2T-6700-15
| The following changes appear only in the online version of this publication. A vertical bar
| ( | ) in the left margin indicates changes to the text and illustrations.
| This revision reflects the deletion, addition, or changing of information from service items and
| maintenance, including the following APARs:
| OW36099
| OW38034
| OW39236
Summary of Changes
for GC28-1780-09
OS/390 Version 2 Release 8
This book contains information previously presented in GC28-1780-08, which supports
OS/390 Version 2 Release 7.
This book includes 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.
Please note that any new, changed, or deleted messages can affect your installation's
automation package. Ensure that your installation's automation package is updated
with these changes.
The following summarizes the changes to that information.
This revision reflects the deletion, addition, or changing of information to support the fol-
lowing APARs:
OW32574
OW36220
OW37334
New Information:
The following system completion codes are new:
1C2
2C2
3C2
BC3
Changed Information:
The following system completion codes have changed:
00C
026
05C
068
09A
Copyright IBM Corp. 1988, 1999 vii
178
18F
1FB
278
283
378
478
5C4
5C6
A78
AC7
D23
The following wait state codes have changed:
032
0A3
A7A
The following stand-alone dump wait state codes have changed:
31
32
33
34
35
Summary of Changes
for GC28-1780-08
as Updated June, 1999
online only for SK2T-6700-13
The following changes appear only in the online version of this publication. A vertical bar
( | ) in the left margin indicates changes to the text and illustrations.
This revision reflects the deletion, addition, or changing of information from service items and
maintenance, including the following APARs:
OW32574
OW37334
Summary of Changes
for GC28-1780-07
OS/390 Version 2 Release 7
This book contains information previously presented in GC28-1780-08, which supports
OS/390 Version 2 Release 6.
This book includes terminology, maintenance, and editorial changes.
Please note that any new, changed, or deleted messages can affect your installation's
automation package. Ensure that your installation's automation package is updated
with these changes.
The following summarizes the changes to that information.
viii OS/390 V2R8.0 MVS System Codes
This revision reflects the deletion, addition, or changing of information to support the fol-
lowing APARs:
OW32704
OW31978
OW31978
OW26737
OW35843
OW36474
New Information:
The following system completion codes are new:
E06
The following wait state codes are new:
206
Changed Information:
The following system completion codes have changed:
023
069
0A7
0A8
0A9
0AB
0AC
0AD
0B0
0F7
16E
30A
40D
422
4C6
60D
738
806
9C4
906
CC5
DC5
EC5
EC6
The following wait state codes have changed:
05E
Summary of Changes ix
088
0A3
Summary of Changes
for GC28-1780-06
as Updated December, 1998
online only for SK2T-6700-11
The following changes appear only in the online version of this publication.
This revision reflects the deletion, addition, or changing of information to support the fol-
lowing APARs:
OW26737
OW31978
Summary of Changes
for GC28-1780-05
OS/390 Version 2 Release 6
This book contains information previously presented in GC28-1780-04, which supports
OS/390 Version 2 Release 5.
This book includes terminology, maintenance, and editorial changes.
Please note that any new, changed, or deleted messages can affect your installation's
automation package. Ensure that your installation's automation package is updated
with these changes.
The following summarizes the changes to that information.
This revision reflects the deletion, addition, or changing of information to support the fol-
lowing APARs:
OW28330
New Information:
The following system completion codes have new reason codes:
00C
01D
026
08B
3C6
422
6C5
AC7
EC7
Changed Information:
The following system completion codes have changed information:
0Cx - changed abend code
AC7 - changed reason code
Changes have been made to the following topics:
As part of the name change of OpenEdition to OS/390 UNIX System Services, occur-
rences of OS/390 OpenEdition have been changed to OS/390 UNIX System Services or
x OS/390 V2R8.0 MVS System Codes
its abbreviated name, OS/390 UNIX. OpenEdition may continue to appear in messages,
panel text, and other code with OS/390 UNIX System Services.
Complete support for IEEE floating point requires PTFs to OS/390 Release 6 and specific
releases of some software. See OS/390 Planning for Installation for the software require-
ments for IEEE floating point.
Summary of Changes
for GC28-1780-04
OS/390 Version 2 Release 5
This book contains information previously presented in GC28-1780-03, which supports
OS/390 Version 2 Release 4.
This book includes terminology, maintenance, and editorial changes.
Please note that any new, changed, or deleted messages can affect your installation's
automation package. Ensure that your installation's automation package is updated
with these changes.
The following summarizes the changes to that information.
This revision reflects the deletion, addition, or changing of information to support the fol-
lowing APARs:
OW21321
New Information: The following system completion codes have new reason codes:
AC7
EC6
00C
026
0F1
18F
Changed Information: Changes have been made to the following topics:
System Completion Code to Module Table
The following have changes to this revision.
SCC 0AB
Explanation has changed.
SCC 0B1
Explanation has changed.
SCC 0D4
Explanation and system action have changed.
SCC 0D5
Explanation and system action have changed.
SCC 0D6
Explanation has changed.
SCC 0D7
Explanation, system action, and system programmer response have changed.
SCC 0D8
Explanation has changed.
Summary of Changes xi
SCC 0E0
Explanation has changed.
SCC 16D
System programmer response has changed.
WSC 025
Operator response has changed.
WSC 035
Operator response has changed.
WSC 054
Operator response has changed.
WSC 055
Operator response has changed.
WCC 074
Operator response has changed.
WSC 0B1
Explanation has changed.
WSC 0B3
Explanation has changed.
Summary of Changes
for GC28-1780-03
as Updated December, 1997
online only for SK2T-6700-07
The following changes appear only in the online version of this publication.
This revision reflects the deletion, addition, or changing of information to support the fol-
lowing APARs:
OW19368
OW22516
OW24532
OW24703
OW25342
OW26322
OW27279
OW27405
OW28330
Summary of Changes
for GC28-1780-03
OS/390 Version 2 Release 4
This book contains information previously presented in GC28-1780-02, which supports
OS/390 Version 1 Release 3.
This book includes terminology, maintenance, and editorial changes.
Please note that any new, changed, or deleted messages can affect your installation's
automation package. Ensure that your installation's automation package is updated
with these changes.
The following summarizes the changes to that information.
xii OS/390 V2R8.0 MVS System Codes
This revision reflects the deletion, addition, or changing of information to support the fol-
lowing APARs:
OW20124
OW22516
OW23383
OW24703
OW27292
Summary of Changes
for GC28-1780-02
as Updated June, 1997
online only for SK2T-6700-05
The following changes appear only in the online version of this publication.
New Information
System abend code X'026' has new reason codes added.
System abend code X'5C4' has been added.
System abend code X'AC7' has new reason codes added.
System abend code X'EC7' has new reason codes added.
Changed Information
System completion code X'053' has been changed to reflect changes to reason code
0112.
This revision also reflects the deletion, addition, or modification of information to support mis-
cellaneous maintenance items.
Summary of Changes
for GC28-1780-02
OS/390 Version 1 Release 3
This book contains information previously presented in GC28-1780-01, which supports
OS/390 Version 1 Release 2.
Please note that any new, changed, or deleted messages can affect your installation's
automation package. Ensure that your installation's automation package is updated
with these changes.
The following summarizes the changes to that information.
This revision reflects the deletion, addition, or changing of information to support the fol-
lowing APARs:
OW15587
OW22259
OW22381
OW23882
New Information
System abend code X'09B' has been added.
System abend code X' 3C4' has been added.
System abend code X'6C4' has been added.
System abend code X'EC4' has been added.
Summary of Changes xiii
System abend code X'026' has new reason codes added.
Wait state code X'0A7' has been added.
Changed Information
System abend code X'0F4' has been updated to reflect changes to the explanation.
System abend code X'09B' has been updated with new reason codes.
Summary of Changes
for GC28-1780-01
OS/390 Version 1 Release 2
This book contains information previously presented in GC28-1780-00, which supports
OS/390 Version 1 Release 1.
This book includes terminology, maintenance, and editorial changes.
Please note that any new, changed, or deleted messages can affect your installation's
automation package. Ensure that your installation's automation package is updated
with these changes.
The following summarizes the changes to that information.
New Information
System abend code X'00C' has new reason code added.
System abend code X'4C5' has been added.
System abend code X'5C6' has been added.
System abend code X'6C6' has been added.
System abend code X'9C4' has been added.
Changed Information
System abend code X'09A' no longer propagates to GQSCAN's caller. Reason codes
A1xx and A228 have been removed and replaced by new reason codes on the
GQSCAN macro.
System abend code X'055' has new reason codes.
System wait state code X'0A3' has new reason codes.
System abend code X'0B6' has been update to reflect changes to the explanation.
System abend code X'Fnn' has been update to reflect changes to the system pro-
grammer response.
Wait state code X'05F' has been updated to reflect changes to the explanation.
Wait state code X'5C7' has been updated to reflect changes to the explanation.
Summary of Changes
for GC28-1780-00
OS/390 Version 1 Release 1
This book contains information previously presented in MVS/ESA System Codes,
GC28-1486, which supports MVS/ESA System Product Version 5.
The following summarizes the changes to that information.
New Information
System abend code X'026' has new reason codes added.
System abend code X'047' has been updated to reflect changes to the explanation.
System abend code X'05C' has new reason codes added.
System abend code X'0D3' has been added.
xiv OS/390 V2R8.0 MVS System Codes
System abend code X'9C5' has been added.
System abend code X'D22' has new reason code added.
Wait state code X'07E' has been added.
Changed Information
System abend code X'07D' has been update to reflect changes to the system pro-
grammer response.
System abend code X'333' has been update to reflect changes to the explanation.
System abend code X'40D' has been update to reflect changes to the explanation.
System abend code X'AC7' has been updated to reflect changes to the explanation
and system action.
Wait state code X'019' has been updated to reflect changes to the explanation.
This book includes terminology, maintenance, and editorial changes.
Summary of Changes xv
xvi OS/390 V2R8.0 MVS System Codes
Introduction
This chapter introduces system and user completion codes Abend of a System Service
and wait state codes.
If a system service represented by a service request block
(SRB) experiences a problem, the system gives control to
Completion Codes the recovery routine for the service; the routine can issue a
SETRP macro to place a system completion code in the
The system or an application program issues a completion system diagnostic work area (SDWA). The system service
code when abnormally ending processing by a task, address stops processing. If the service was processing a request
space, or system module. The completion code indicates the from a task, the system abnormally ends the task with the
reason for the abnormal end. A completion code can be same system completion code.
specified by the following:
Note that another task can request the system service to do
ABEND macro processing.
CALLRTM macro
SETRP macro
Format
Abend of a Task or Address Space The format of completion codes is:
For a System-Detected Problem System completion code (or abend code):
3 hexadecimal digits
The system abnormally ends a task or address space when User completion code: 4 decimal digits
the system determines that the task or address space cannot Note: Only system completion codes appear in this book;
continue processing and produce valid results. user completion codes do not. User completion codes
are in books for the IBM-provided component, sub-
For example, a task may incorrectly specify a request for a
system, or product that issues the user completion
system service. Because the system cannot perform the
codes. IPCS user completion codes are documented
service with incorrect input, the system abnormally ends the
in OS/390 MVS Diagnosis: Reference. Codes issued
task requesting the service. This task is also referred to as a
by installation-provided programs do not appear in
caller.
IBM books.
For a Hardware-Detected Problem
Location
The system also abnormally ends a task with a completion
code when the system receives control after a hardware- The codes can be obtained from the following:
generated interruption that indicates an error in the task.
Messages accompanying the abend
For example, an instruction in an application running in The header in any ABEND dump accompanying the
storage key 7 branches to low central storage, which is abend
always in storage key 0. The difference in storage key Search arguments and, sometimes, the title in any SVC
causes a protection exception. The system recovers from this dump accompanying the abend
hardware problem by ending the application's task with an Search arguments in any logrec data set error record
abend X'0C1'. If the application has a recovery routine, the written for the abend
system gives control to the routine; the routine can clean up The system diagnostic work area (SDWA)
resources being used by the application and can request a Use of the EXTRACT macro with keyword CMC to
dump. determine the completion code for the ended task.
For an Application-Detected Problem
Abnormal End of Subtasks
An application program abnormally ends itself when it deter-
mines that it cannot continue processing and produce valid When the highest-level task in a job step ends abnormally,
results. the job step ends abnormally.
For example, an application may be calculating a total by When a subtask ends abnormally, only the subtask itself and
successive additions. After each addition, the application its subtasks end. To get the abend code for an abnormal end
checks the new total against a limit. If the total exceeds the of a subtask:
limit, the application issues an ABEND macro to end abnor- Examine the event control block (ECB) specified by the
mally and, perhaps, to ask for an ABEND dump. The ABEND task that attached the subtask
macro specifies a user completion code.
Copyright IBM Corp. 1988, 1999 INTRO-1
Issue the EXTRACT macro with the CMC keyword rr The reason code for the accompanying the wait state
code which appears in bits 36 through 43.
A low-level subtask that ends abnormally has two ways to
The wait state determines the size and position of the
cause the entire job step to end abnormally:
supplement code.
Each task in the job step's task chain, including the job
Usually the supplement code is a reason code. Some
step task, must end itself abnormally when it detects an
wait states do not provide a supplement code in the
abend code from one of its subtasks. To end the job
PSW. See the description of the individual wait state
step with the abend code for the original error, each task
code for more information.
must use the abend code from its subtask as its own
abend code. www
A subtask can abnormally end the entire job step if it The wait state code. The IBM-supplied wait state codes
specifies a STEP parameter on the ABEND macro. appear in this book. Installation-supplied programs can
use wait state codes X'FF0' through X'FFE'; see
installation-supplied information for these codes.
Wait State Codes No Work Wait
The wait state code appears in the program status word If the system hangs because it has no work waiting to be
(PSW) when the operating system enters a wait state. A dispatched, either because the work is waiting for a resource
valid PSW for a coded wait state has one of the following or because no work remained on the system queues, the
general formats: PSW contains:
X'ðððAðððð 8rrrrwww' X'ð7ðEðððð ðððððððð'
000A0000 A no work wait may not reflect an error. See the OS/390
The A is bits 12 through 15 (the CMWP bits). MVS Diagnosis: Procedures for diagnosis of a hang or wait.
8rrrr
A supplement code for the accompanying the wait state
code appears in bits 32 through 51. Wait State Codes from a Stand-Alone
Dump Program
The wait state determines the size and position of the sup-
plement code. See “Stand-Alone Dump Wait State Codes” on page SDW-1
for information about reading stand-alone dump wait state
Usually the supplement code is a reason code. Some wait codes.
states do not provide a supplement code in the PSW. See
the description of the individual wait state code for more
information.
IPCS User Completion Codes
X'ðððAðððð xrrxxwww'
IPCS issues a 4 digit decimal user code when it encounters
000A0000
errors in either IBM-provided IPCS code or in installation exit
The A is bits 12 through 15 (the CMWP bits).
routines. See “IPCS User Completion Codes” on
xrr Bit 32, x must be on (x=1), indicating 31 bit addressing page IPCS-1 for more information.
mode.
INTRO-2 OS/390 V2R8.0 MVS System Codes
001 004
System Completion Codes
001 003
Explanation: An I/O error condition was encountered during BDAM, Explanation: The error occurred during end-of-block processing
BISAM, BPAM, BSAM, QISAM, or QSAM processing. using either BSAM or QSAM. The error occurred because the I/O
macro instructions for a 3525-associated data set were not run in the
okms completion code can be issued if CLOSE processing called
proper sequence.
end-of-volume (EOV), and EOV processing detected an out-of-space
condition. Refer to the explanation of message IEC020I in OS/390 The hexadecimal reason code in register 15 indicates the nature of
MVS System Messages, Vol 4 (IEC-IFD) for information about the the error:
task that was ended.
Code Explanation
Source: DFSMSdfp
01 A READ sequence error
Programmer Response: Respond as indicated for message
02 A PUNCH sequence error
IEC020I.
03 A PRINT sequence error
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more Source: DFSMSdfp
information. Search problem reporting data bases for a fix for the System Action: The system ends the task.
problem. If no fix exists, contact the IBM Support Center. Provide the
Programmer Response: Specify the I/O macro instructions in the
JCL and the program listing for the job.
proper sequence, and rerun the job.
002 System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
Explanation: For all return codes except 2C, the error occurred information. Search problem reporting data bases for a fix for the
while the control program was processing a sequential data set with problem. If no fix exists, contact the IBM Support Center. Provide the
BSAM or QSAM, or creating a direct organization data set. This program listing for the job.
system completion code is accompanied by message IEC036I. Refer
to the explanation of message IEC036I for complete information
004
about the task that was ended and for an explanation of the return
code found in register 15. Explanation: The error occurred during OPEN processing using
either BSAM or QSAM because a conflicting or incorrect DCB
For return code 2C, the error occurred while the control program was
parameter (FUNC or related parameter) is specified. The
opening an ISAM data set for QISAM load mode. Too many tracks
hexadecimal reason code in register 15 indicates the nature of the
were specified for cylinder overflow, or DCB BLKSIZE was not a
error:
multiple of DCB LRECL, or DCB BLKSIZE was greater than the track
size. Code Explanation
Source: DFSMSdfp 01 Incorrect DCB FUNC parameter specified.
System Action: For all return codes except 2C, pertinent control 02 Incorrect combination of DCB FUNC parameter and
blocks are written to the GTF trace data set, the user's DCB ABEND CNTRL macro specified.
exit is taken if one is provided, and message IEC036I is issued.
03 Conflicting access methods specified.
Operator Response: Start a generalized trace facility (GTF) trace,
04 Incorrect DCB specified for 3505 or 3525.
and re-create the problem. Reply to message AHL100A with:
05 Incorrect format card or an incorrect device specified
TRACE=SYS,USR,SLIP
with Optical Mark Read (OMR).
On the DD statement for the data set in error, specify:
06 Data protection image not found in the SYS1.IMAGELIB
DCB=DIAGNS=TRACE data set, volume containing SYS1.IMAGELIB not
Programmer Response: See message IEC036I for the appropriate mounted, or SYS1.IMAGELIB data set not cataloged.
responses for each return code except 2C. For return code 2C, Source: DFSMSdfp
change the CYLOFL operand of the DCB macro instruction to reflect
System Action: In all cases, the system ends the task.
the correct number of tracks, or correct the DCB BLKSIZE.
Programmer Response: In all cases, correct the incorrect fields of
System Programmer Response: If the error recurs and the
the DCB macro instruction and rerun the job.
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 System Programmer Response: If the error recurs and the
problem. If no fix exists, contact the IBM Support Center. Provide the program is not in error, look at the messages in the job log for more
JCL and the program listing for the job. information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
program listing for the job.
Copyright IBM Corp. 1988, 1999 SCC-1
005 00B
Source: Supervisor control
005
System Action: The system abends the program that branch-
Explanation: The error occurred because of an incorrect DECB
entered the stage 2 exit effector. The system may also write a
during READ processing using BSAM. This system completion code
logrec data set error record and an SVC dump.
is accompanied by message IEC041I. Refer to the explanation of
message IEC041I for complete information about the task that was Operator Response: If the system programmer asks for an SVC
ended and for an explanation of the return code. dump, set the following SLIP trap:
Source: DFSMSdfp SLIP SET,COMP=ððA,ACTION=SVCD,END
System Action: The task is ended. System Programmer Response: Do the following:
Programmer Response: Make sure that the RBL type of read is If an SVC dump or a logrec data set error record is not written
used and that the area address and header address parameters are with the abend, ask the operator to set a SLIP trap to obtain an
specified so that the DECB is valid. SVC dump.
System Programmer Response: If the error recurs and the Use the address in register 14 at the time of error to identify
program is not in error, look at the messages in the job log for more program that branch-entered the stage 2 exit effector.
information. Search problem reporting data bases for a fix for the – For an installation-provided module, continue diagnosis with
problem. If no fix exists, contact the IBM Support Center. Provide the the module.
program listing for the job.
– For an IBM module, search problem reporting data bases
for a fix for the problem. If no fix exists, contact the compo-
008 nent group for the module at the IBM Support Center.
Explanation: The error occurred during processing of a SYNAD Provide, if available, the SVC dump and the logrec data set
routine. The routine was given control following processing of a error record.
BSAM CHECK macro instruction.
The SYNAD routine returned control to the control program for the 00B
CHECK macro instruction. Explanation: During restart of a checkpointed job, the system
Source: DFSMSdfp detected an error. A reason code in the SDWACRC field of the
system diagnostic work area (SDWA) accompanies the abend and
Programmer Response: Correct the SYNAD routine so that the explains the error:
control program save area is not destroyed. Then run the job step
again. Code Explanation
System Programmer Response: If the error recurs and the 001 The system failed to obtain enough storage from the
program is not in error, look at the messages in the job log for more pre-allocated storage area.
information. Search problem reporting data bases for a fix for the 002 A storage pointer pointed to an area outside the pre-
problem. If no fix exists, contact the IBM Support Center. Provide the allocated storage area.
JCL and the program listing for the job.
1F4 A parameter list contained an error.
00A 1F5 An error was detected during initialization of scheduler
restart.
Explanation: A program attempted to schedule an asynchronous or
installation exit by branch-entering the stage 2 exit effector. The 1F6 An error occurred while processing a find request.
stage 2 exit effector detected a problem. 1F7 An error occurred while processing a get request.
A hexadecimal reason code in register 15 explains the error: 1F8 An error occurred while building a DD names table
Code Explanation (DDNT) record for a scheduler work area (SWA) DDNT.
0004 IQETCB did not point to a valid TCB. A program sets up 1F9 An error occurred while building a DD names table
the IQE by putting a TCB address into the IQETCB field. (DDNT) record for unallocated step input output tables
The program then branch-enters the stage 2 exit effector (SIOTs).
to schedule an asynchronous or installation exit, passing 1FA An error occurred while building a Type 1 data set
the address of the IQE. descriptor record (DSDR) for a step input output table /
0008 RQETCB did not point to a valid TCB. A program sets job file control block (SIOT/JFCB).
up the RQE by putting a TCB address into the RQETCB 1FB An error occurred while building a Type 2 data set
field. The program then branch-enters the stage 2 exit descriptor record (DSDR) for a job file control block
effector to schedule an asynchronous or installation exit, extension (JFCBX).
passing the address of the RQE.
1FC An error occurred while building a Type 2 data set
000C The program branch-entering the stage 2 exit effector descriptor record (DSDR) for a job file control block
did not hold the local lock for the home address space. extension (JFCBE).
0010 The program branch-entering the stage 2 exit effector 1FD An error occurred while building a Type 3 data set
did not have addressability to the address space in descriptor record (DSDR) for a generation data group
which the asynchronous or installation exit was to be name table (GDGNT).
dispatched.
1FE An error occurred while writing an updated step input
0014 The program branch-entering the stage 2 exit effector output table (SIOT) to the scheduler work area (SWA).
was not in primary or secondary address space control
1FF An error occurred when the system tried to end the
(ASC) mode.
scheduler JCL facility (SJF).
SCC-2 OS/390 V2R8.0 MVS System Codes
00C 00C
200 An error occurred when a program issued the DELETE 02070001 A non-retryable error occurred and the signal data might
macro. not have been delivered to a member message exit.
201 An error occurred when a program issued the WTO If the message exit routine was called, the failure
macro. occurred before the exit could successfully return to
XCF.
202 The system found an error in the parameter list passed
by the routine that reads and writes from data sets. If the message exit was not called, XCF discarded
the message, in which case a signal was lost.
Source: Scheduler restart
XCF percolates to the task to which the member is asso-
System Action: The system writes an error record to the logrec
ciated. The task can retry in its recovery routine. The
data set and writes an SVC dump.
system issues a LOGREC data set error record. If the
Operator Response: If the abend recurs, notify the system pro- ABEND occurred while XCF was in control, the system
grammer. issues an SVC dump.
System Programmer Response: If the error recurs, search 020F0006 Message delivery appears to be stalled.
problem reporting data bases for a fix for the problem. If no fix
Delivery of signals to a member appears to have stalled.
exists, contact the IBM Support Center.
Signals queued to the member message delivery queue
have not been processed within the last monitoring
00C interval (one minute). This could be due to a user error,
Explanation: Cross-system coupling facility (XCF) encountered an an internal XCF error, a system error (such as storage
error. See OS/390 MVS Diagnosis: Reference for more information overlay or lost SRB), or could be normal behavior. The
on diagnosing sysplex problems. system is initiating recovery actions to document the
problem, to verify/repair internal XCF control blocks, and
The reason code in register 15 is:
to provide replacement member message delivery cell(s)
Code Explanation in hopes that signal delivery can resume. If signal
00000004 A group member abended another group member using delivery does not resume, signalling resources (for
the IXCTERM macro. example, MMDCs or SIOCBs) may be consumed/lost for
the life of the member. This consumption of signalling
0000004C Data Space IXCDSCBE cannot be created or accessed. resources could surface itself in many ways, such as:
00000040 A group member abended another group member using common storage growth, degradation of signal delivery
the IXCTERM macro. (possible to the point where no signals can be deliv-
ered), rejected message-out requests, or repeated path
00000044 Data space IXCDSMEM cannot be created or accessed.
restarts.
00000048 Data space IXCDSCBD cannot be created or accessed.
05070000 An error occurred while XCF was processing a Status
0000005C Either the system encountered an error while loading an Exit. XCF continues processing the Status Exit.
XCF module or an XCF module is missing from the
XCF tries to end the task that owns the Status Exit. The
nucleus.
system writes a LOGREC data set error record. If the
00000074 XCF detected an I/O error while reading or writing to a ABEND occurred while XCF was in control, the system
couple data set. This may be a hardware error. issues an SVC dump.
If XCF cannot recover from the I/O error, it may end one 060B0000 An error occurred while XCF was processing a Group
or more groups or members using the couple data set, Exit. XCF continues processing the Group Exit.
or else stop using the couple data set. XCF writes a
XCF tries to end the task that owns the Group Exit. The
LOGREC data set error record.
system writes a LOGREC data set error record. If the
00000078 Failure of a previous write to the couple data set was ABEND occurred while XCF was in control, the system
detected. issues an SVC dump.
00000100 Data Space IXCDSLO1 cannot be created or accessed. 060B0001 An error occurred while XCF was processing a Group
00000104 Data Space IXCDSLK1 cannot be created or accessed. Exit. Some group event information may have been lost.
00000108 Data Space IXCAP1DS cannot be created or accessed. XCF tries to end the task that owns the Group Exit.
Some group event information may have been lost. The
02070000 A non-retryable error occurred and the function is con- system writes a LOGREC data set error record. If the
sidered complete. ABEND occurred while XCF was in control, the system
If the message exit was not called, the signal has issues an SVC dump.
been preserved and will be presented later. 060C0000 A non-retryable error has occurred on the first invocation
If the message exit was called, the exit returned of the users Group Exit for this event. The exit will be
before the error occurred, so the signal was deliv- rescheduled and presented with the same event.
ered successfully. 060C0001 Group information may have been lost due to either a
XCF percolates to the task to which the member is asso- non-recoverable error in XCF or the users Group Exit
ciated. The task can retry in its recovery routine. The has ABENDed two consecutive times. This code indi-
system issues a LOGREC data set error record and an cates the user may want to issue a IXCQUERY macro to
SVC dump. If the ABEND occurred while XCF was in see what may have been lost.
control, the system issues an SVC dump.
System Completion Codes SCC-3
00C 00C
081C0001 XCF forcibly ended processing of a SETXCF STOP 00000050 00000054 00000058 00000060 00000064
command that was stopping a signalling path. This can 00000068 0000006C 00000070 00000080 0000008C
happen when an operator specifies UNCOND=YES on a 00000120 00000124 00000134 02030001 02030002
02030003 02070002 020F0001 020F0002 020F0003
SETXCF STOP command.
020F0005 020F0007 020F0008 020F0009 020F000A
The XCF signalling service may have lost some mes- 02130001 02140001 02140002 02140003 02140005
sages as a result of this ABEND. There may be unpre- 02160001 02160002 02160003 02160005 02170001
dictable results for the XCF groups whose messages got 02170002 02170003 02170004 02170006 02170007
02170008 021A0001 02220001 02220002 02220003
lost.
02220004 02220005 02220006 022D0002 02330001
081CFF01 Unconditional stop processing is terminating the task 02330002 02380002 02430001 05010084 05030088
that is currently processing a signalling path START, 05050090 08030001 08030002 08040001 08060002
STOP, or RESTART request. 08080001 08080002 080A0001 080C0001 08201002
08201003 0820100C 08221001 08221007 08240001
16140003 Internal error. 08300001 08300002 08321001 08340001 085A1006
08600001 08600002 08690001 08691001 086B0001
Source: Cross-system coupling facility (XCF) 08750001 08750002 08750003 087A1001 087E1002
System Action: XCF tries to end a member of a group in the 08801004 08891001 088E0001 08960001 08FB0100
sysplex. The system may issue a LOGREC data set error record or 08FD0001 08FF0001 08FF0224 09030001 09031001
09080001 09080002 09080003 09080004 090A0001
an SVC dump. Messages explaining the error might precede this
090A0002 090E0001 09110001 091C0001 0F01008C
ABEND. Depending on the reason code, the system also does the 0F07006E 0F080060 0F08006C 0F0F008C 12B10001
following: 12B10002 16030001 16050010 16090010 16090030
Code Explanation 16090050 16090070 160B0010 160B0030 160D0001
160F0001 160F0002 160F0003 160F0004 160F0005
00000004 XCF ends the group member. 16100001 16120001 16140001 16140002 16160001
16160002 16160003 16160004 16160005 16160006
Others XCF tries to end a member of a group in the sysplex.
161E0002 161E0003 161E0004 161E0005 161E0006
The system may issue a LOGREC data set error record 161E0007 161E0008 16200001 16200002 16240030
or an SVC dump. Messages explaining the error might 16280001 16280002 16280003 162A0001 162A0002
precede this ABEND. 162A0003 162A0004 162A0005 162A0006 162A0007
162A0008 162A0009 162A000A 162A000B 162A000C
Operator Response: Depending on the reason code, do the 162A000D 162A000E 162C0010 162C0030 16320001
following: 16320002 163C0001 163C0002 163E0001 163E0002
Code Explanation 16400010 16400020 16400030 16420001 16440010
16440030 16440050 16440070 16440090 164400B0
74 Determine the cause of the I/O error. If the error is 164E0001 164E0002 164E0003 164E0004 164E0005
caused by a hardware problem, contact hardware 16500001 16500003 16500004 16500005 16500006
support. 16560001 16560002 16560003 16560004 16580001
16580002 165B0001 xxxx1008 xxxx100C
Others See the operator response for the preceding messages.
Obtain the LOGREC data set and SVC dump, if one is Programmer Response: Depending on the reason code, do the
issued. Notify the system programmer. following:
The following reason codes represent errors internal to the XCF Code Explanation
component. Call the IBM Support Center for assistance with these
02070001 Make sure that the program that owns the message exit
errors. Provide the LOGREC data set and SVC dump, if one is
has recovery established for missing messages. The
issued.
recovery routine might do one of the following:
Reason Codes: Send a request to other active group members
requesting that they resend the message.
Back up to a previous point in the program and con-
tinue processing from there.
End the task if the function cannot tolerate any
missing messages.
060B0001 Determine which program owned the Group Exit. Make
sure that the program that owns the Group Exit has
recovery established to handle missing group event
information. The recovery routine should do one of the
following:
Issue the IXCQUERY macro to determine whether
group event information was lost.
Back up to a previous point in the program and con-
tinue processing from there.
End the task if the function cannot tolerate missing
information.
System Programmer Response: See the system programmer
response for the messages preceding this abend.
If the problem persists, do the following:
SCC-4 OS/390 V2R8.0 MVS System Codes
00D 014
Format the SVC dump with the IPCS COUPLE subcommand. System Programmer Response: See OS/390 HCD User's Guide
Include all the reports and the summary, detail, and exception for diagnosing abend X'00F'.
levels for each report.
Format the SVC dump with the IPCS CTRACE COMP(SYSXCF) 012
subcommand to obtain XCF component trace data. Explanation: A program incorrectly issued a TIMEUSED macro. A
Search problem reporting data bases for a fix for the problem. If reason code in register 15 explains the error:
no fix exists, contact the IBM Support Center. Provide the for- Code Explanation
matted SVC dump.
4 The program issued TIMEUSED with
LINKAGE=SYSTEM, but the program was not in task
00D
control block (TCB) mode.
Explanation: An error occurred during processing of a CTRACE or
8 The program issued TIMEUSED with
CTRACEWR macro. Register 15 contains a reason code that further
LINKAGE=SYSTEM, but the program held one or more
describes the error.
locks.
Code Explanation
C The program issued TIMEUSED with
00000101 For the CTRACE DEFINE macro, the parameter list LINKAGE=SYSTEM when enabled unlocked task (EUT)
version number is incorrect. recovery routine was running.
00000102 For the CTRACE DEFINE macro, the component name Source: Timer supervision
either does not begin with an alphabetic or national char-
System Action: The system abnormally ends the program that
acter, or it contains one or more characters that are not
issued the TIMEUSED macro.
alphanumeric or national characters.
Programmer Response: Modify the code so that TIMEUSED will
00000301 The system found either nonzero values in the reserved
be issued in the correct environment. Run the program again.
fields or unused fields for the requested service in the
CTRACE DEFINE macro parameter list.
013
00000302 The system found either nonzero values in the reserved
fields or unused fields for the requested service in the Explanation: The error occurred during processing of an OPEN
CTRACE DELETE macro parameter list. macro instruction. This system completion code is accompanied by
message IEC141I. Refer to the explanation of message IEC141I for
00000401 For the CTRACE macro, an incorrect service request complete information about the task that was ended and for an
code was specified. Valid services are DEFINE and explanation of the return code in register 15 (which is provided in the
DELETE. IEC141I message text).
00000501 For the CTRACE DEFINE macro, the length of the Source: DFSMSdfp
minimum options string is greater than 256 bytes.
Programmer Response: Respond as indicated for message
00010100 For the CTRACEWR macro, the parameter list version IEC141I.
number is incorrect.
System Programmer Response: If the error recurs and the
00010200 The system found either nonzero values in the reserved program is not in error, look at the messages in the job log for more
fields or unused fields for the requested service in the information. Search problem reporting data bases for a fix for the
CTRACEWR macro parameter list. problem. If no fix exists, contact the IBM Support Center. Provide the
00010300 For the CTRACEWR macro, the buffer length was JCL and the program listing for the job.
passed was zero or less.
Source: Component trace 014
System Action: The component trace service abnormally ends. Explanation: An error occurred during processing of a CLOSE
macro instruction for a basic direct access method (BDAM) data set.
Programmer Response: Correct the input on the CTRACE or This completion code is accompanied by message IEC208I. Refer to
CTRACEWR macro. See the OS/390 MVS Programming: Authorized the explanation of message IEC208I for complete information about
Assembler Services Reference ALE-DYN for the CTRACE and the task that was ended and for an explanation of the return code in
CTRACEWR macros. register 15 (which is provided in the IEC208I message text).
System Programmer Response: If the problem recurs, search Source: DFSMSdfp
problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Programmer Response: Respond as indicated for message
IEC208I.
00F System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
Explanation: The system detected a logic error in a hardware con-
information. Search problem reporting data bases for a fix for the
figuration definition (HCD) module.
problem. If no fix exists, contact the IBM Support Center. Provide the
Source: Hardware configuration definition (HCD) JCL and the program listing for the job.
System Action: The system issues message CBDA099I. The
system abends the current task.
Operator Response: Notify the system programmer.
System Completion Codes SCC-5
015 017
010C The issuer of a SUSPEND macro with SPTOKEN was
015
not running under a service request block (SRB).
Explanation: The print services access facility (PSAF) detected an
0110 The SUSPEND EXIT (specified by the EXIT keyword on
error condition that is identified by the unique reason code accompa-
the SUSPEND macro) returned an incorrect return code
nying this abend.
to the system.
Source: DFSMSdfp
0114 Recursive errors occurred while processing a SUSPEND
Operator Response: For an explanation of the system action, the macro with SPTOKEN.
programmer response, and the reason codes, see Print Services
0200 The caller of the RESUME SPTOKEN= service held a
Access Facility for MVS User's Guide and Reference
lock higher than or equal to the DISP lock in the locking
hierarchy.
016
0204 The content of access register 1, and passed for a
Explanation: An error occurred in the sequential access method RESUME macro, is not valid.
(SAM) SIO/PAGE FIX or direct access storage device (DASD) end-
0208 The ALET used to address the SPTOKEN, and passed
of-block modules. A reason code (hexadecimal) further explains the
for a RESUME macro, is not valid.
error:
020C The SPTOKEN passed for a RESUME macro is not
Code Explanation
valid.
04 The DASD end-of-block modules issued an EXCPVR
0300 The issuer of a RESUME macro with SPTOKEN and
SVC request on behalf of a user request, but a previous
PURGE=YES requested that an SRB be purged. This
EXCPVR SVC request has not yet completed. One of
issuer held a lock higher than or equal to the DISP lock.
the following occurred:
The macro issuer must not hold such a lock.
A data event control block (DECB) was used twice.
0304 The content of access register 1, passed for a RESUME
Multiple READs or WRITEs were issued, but macro with PURGE=YES, is not valid.
CHECK macros were not issued for those requests
0308 The ALET, used to address the SPTOKEN and passed
in the same order.
for a RESUME macro with SPTOKEN and
The SAM SIO/PAGE FIX appendage issued this abend. PURGE=YES, is not valid.
08 An EXCPVR SVC request on behalf of a user request 030C The SPTOKEN, passed for a RESUME macro with
was going to be issued to read a data set that is RACF SPTOKEN and PURGE=YES, is not valid.
EXECUTE access protected, but the user is not in
Source: Supervisor control
supervisor state. The SAM SIO appendage issued this
abend. System Action: For all reason codes, the system abends the
issuer of the SUSPEND or RESUME macro.
Source: DFSMSdfp
For reason code X'0114' only, the system writes a logrec data set
System Action: The system abnormally ends the task.
error record and an SVC dump.
System Programmer Response: If the EXCPVR SVC request was
Operator Response: If the system programmer asks for an SVC
issued before the first request was completed, ensure that the DECB
dump, set the following SLIP trap:
that is created for the READ/WRITE operation is tested for suc-
cessful completion before it is reused. Also, ensure that the CHECK SLIP SET,COMP=ð17,ACTION=SVCD,END
macros are issued in the same order as the associated READ or System Programmer Response: Do the following:
WRITE macros.
1. If an SVC dump is not produced with the abend, ask the oper-
Otherwise, unless the task is in supervisor state, do not attempt to ator to set a SLIP trap to obtain an SVC dump.
read a data set that is protected with RACF EXECUTE access
authority. 2. For reason code X'0110', look at the registers at the time of
error for the following:
017 Register 2 contains the return code from SUSPEND macro
processing.
Explanation: A program issued the SUSPEND or RESUME macro
with an SPTOKEN macro incorrectly. A hexadecimal reason code in Registers 3 and 4 contain the SPTOKEN.
register 15 explains the error: 3. Identify the module that issued the SUSPEND or RESUME
Code Explanation macro by using the program status word (PSW) of the current
entry in the linkage stack.
0100 The issuer of a SUSPEND macro with SPTOKEN held a
lock other than a local or CML lock. For an installation-provided module, continue diagnosis with
the module.
0104 The content of access register 1, passed for a
SUSPEND macro with SPTOKEN, was not valid. For an IBM module, search problem reporting data bases
for a fix for the problem. If no fix exists, contact the compo-
0108 The access list entry token (ALET), used to address the nent group associated with this module at the IBM Support
SPTOKEN and passed for a SUSPEND macro with Center. Provide, if available, the SVC dump and the logrec
SPTOKEN, is not valid. data set error record. For reason code X'0110', provide the
problem data collected in step 2.
SCC-6 OS/390 V2R8.0 MVS System Codes
019 01A
00000164 EVW request failed. Specified offset is larger than the
019
maximum size of the object.
Explanation: A callable service request was made either:
00000166 EVW request failed. Span extends beyond the maximum
With an input parameter value that is not valid size of the object.
Without a required input parameter value
Source: Contents supervision (CSV)
The following hexadecimal reason codes provide further information
System Action: The system abnormally ends the task.
about the error:
Programmer Response: Check your parameters for valid values
Code Explanation
and rerun your job.
00000000 Request failed. Routine on down-level system.
System Programmer Response: If the parameters are correct and
00000110 Identify and access request failed. Operation type is not the problem persists, search problem reporting data bases for a fix
valid. for the problem. If no fix exists, contact the IBM Support Center.
00000111 Identify and access request failed. Object type is not
valid. 01A
00000112 Identify and access request failed. Scroll area value is Explanation: The system found a problem during TSO/E LOGON
not valid. processing. The following hexadecimal reason codes provide further
information about the error:
00000113 Identify and access request failed. Object state is not
valid. Code Explanation
00000114 Identify and access request failed. Access mode is not 04 The LOGON RACF interface routine received an incor-
valid. rect function type.
00000115 Identify and access request failed. Object size is not 08 The RACROUTE macro received incorrect parameters
valid. for storing logon information in the RACF data base.
00000116 Identify and access request failed. Object identifier is not 10 The RACROUTE macro received incorrect parameters
valid. for obtaining logon information from the RACF data
base.
00000120 View request failed. Operation type is not valid.
18 The RACROUTE macro returned an incorrect segment
00000121 View request failed. Object identifier is not valid.
length.
00000122 View request failed. Usage type is not valid.
1C The LOGON panel load module IKJLPxxx (xxx is the
00000123 View request failed. Disposition is not valid. 3-character code for the language in which the panel is
00000124 View request failed. Specified offset is larger than the written) is in error. The variable recording area (VRA)
maximum size of the object. contains the LOGON panel address and the offset being
accessed in the panel.
00000126 View request failed. Span extends beyond the maximum
size of the object. 20 The LOGON command detected an error in data sup-
plied by either installation exit IKJEFLN1 or installation
00000130 Scroll out request failed. Object identifier is not valid. exit IKJEFLN2. The VRA will contain the parameter
00000131 Scroll out request failed. Specified offset is larger than number and the parameter entry in error.
the maximum size of the object. 24 The LOGON command detected an error in validated
00000132 Scroll out request failed. Cannot perform the data. One of the following is true:
SCROLLOUT service because the data object does not Either installation exit IKJEFLN1 or installation exit
have a scroll area. IKJEFLN2 validated a field by setting the key to
00000140 Save request failed. Object identifier is not valid. X‘04’. The LOGON processor has found that this
value is not valid. For example, one of the exits may
00000141 Save request failed. Specified offset is larger than the
have validated the new password field. However, on
maximum size of the object.
the RACROUTE REQUEST=VERIFY that is done
00000142 Save request failed. The SAVE service is not allowed, by LOGON, RACF may reject the password.
because the data object was identified and accessed in
Either installation exit IKJEFLN1 or installation exit
READ ONLY mode.
IKJEFLN2 changed the key of a field that was
00000150 Refresh request failed. Object identifier is not valid. already validated (the key was X‘04’).
00000151 Refresh request failed. Specified offset is larger than the Either installation exit IKJEFLN1 or installation exit
maximum size of the object. IKJEFLN2 requested that the LOGON processor
00000160 EVW request failed. The operation type must be prompt the user for a field that has already been
“BEGIN” or “END.” validated (the key is X‘04’).
00000161 EVW request failed. The object ID specified is not valid. The VRA contains the LOGON panel field number and
the parameter entry in error.
00000162 EVW request failed. The usage type must be “SEQ.”
28 The LOGON help text load module IKJLHxxx (xxx is the
00000163 EVW request failed. The disposition input value must be 3-character code for the language in which the help text
“REPLACE” or “RETAIN.” is written) is in error. The VRA will contain the LOGON
help panel address and offset being accessed in the
panel.
System Completion Codes SCC-7
01B 01D
2C Either installation exit IKJEFLN1 or installation exit xxzz0Axx The system does not recognize the macro request.
IKJEFLN2 validated the account number field on the
xxzz0Bxx A storage key violation occurred on the specified
LOGON panel for a user defined only in the UADS data
Hiperspace virtual storage.
set, but the exit did not supply a procedure name.
xxzz0Cxx The caller did not issue a GETMAIN macro for the indi-
Source: Time Sharing Option Extensions (TSO/E)
cated address space virtual storage.
System Action: The system ends the TSO/E LOGON attempt. The
xxzz0Dxx A storage key violation occurred on the specified
system writes an ABEND dump.
address space virtual storage.
Operator Response: Notify the system programmer.
xxzz0Exx The specified address space virtual storage did not start
System Programmer Response: If the problem recurs and if the on a 4-kilobyte boundary or was not within the bounds of
program is not in error, search problem reporting data bases for a fix the private area.
for the problem. If no fix exists, contact the IBM Support Center.
xxzz0Fxx The specified Hiperspace virtual storage did not start on
a 4-kilobyte boundary or was not within the bounds of
01B the Hiperspace.
Explanation: An error occurred during RACONVRT processing; the xxzz10xx The SREAD or SWRITE request failed because it was
following hexadecimal reason codes provide further information issued against address space virtual storage that maps
about the error: a data-in-virtual object, but the storage is virtual I/O
Code Explanation (VIO) storage, fixed, or part of a disabled reference
(DREF) subpool.
04 The RACROUTE macro returned an unexpected return
code. xxzz11xx The caller specified a value for NUMRANGE that was
not in the acceptable range.
08 The RACONVRT I/O routine received an incorrect data
management request. xxzz12xx The SREAD or SWRITE request failed because the
caller was in cross-memory mode.
Source: Time Sharing Option Extensions (TSO/E)
xxzz13xx The SREAD or SWRITE request failed because it was
System Action: The system abnormally ends the command. issued against an ESO Hiperspace.
Operator Response: Notify the system programmer. xxzz14xx The request failed because the caller is not in 31-bit
System Programmer Response: Obtain the JCL for the job. addressing mode.
Obtain the SYSOUT output for the job. Collect all printed output and xxzz15xx The specified parameter list or range list is not acces-
output data sets related to the problem. If the problem recurs and if sible.
the program is not in error, search problem reporting data bases for
a fix for the problem. If no fix exists, contact the IBM Support Center. xxzz16xx The caller specified an incorrect parameter list version.
xxzz17xx The parameter list contains inconsistent data or data that
01C is not valid.
Explanation: The RACROUTE macro returned an unexpected xxzz18xx The SWRITE request failed because the caller issued it
return code. against Hiperspace storage while a DIV SAVE macro
was active.
Source: Time Sharing Option Extensions (TSO/E)
| xxzz19xx The HSPSERV macro failed because an unauthorized
System Action: The system abnormally ends the command.
| caller requested it against a shared standard Hiperspace
Operator Response: Notify the system programmer. | without supplying an access list entry token. (ALET).
System Programmer Response: Obtain the JCL for the job. | xxzz1Axx The supplied access list entry token (ALET) does not
Obtain the SYSOUT output for the job. Collect all printed output and | belong to the Hiperspace as indicated by the specified
output data sets related to the problem. If the problem recurs and if | STOKEN.
the program is not in error, search problem reporting data bases for
xx0001xx A problem-state program with PSW key 8-F attempted
a fix for the problem. If no fix exists, contact the IBM Support Center.
either to create a SCOPE=ALL or SCOPE=COMMON
data space, a disabled reference (DREF) data space, or
01D a non-fetch protected data space, or to assign ownership
Explanation: During processing of a DSPSERV or HSPSERV of a Hiperspace to another task.
macro, the system found a non-environmental error. The macro proc- xx0002xx A supervisor-state caller attempted to create a data
essing failed. Register 15 contains a hexadecimal reason code. space on behalf of an owner that is not in the caller's
In the reason code, zz is 07 for CREAD, 08 for CWRITE, 09 for home or primary address space.
SREAD, and 0A for SWRITE. If the service requested cannot be xx0003xx A service request block (SRB) mode request did not
determined, then zz is FE. specify the owner of the data space or Hiperspace.
Code Explanation xx0004xx The caller requested that a storage key be assigned to
xxzz07xx The CREAD or CWRITE request failed because the the data space, but the caller was not in supervisor
caller was unauthorized. state.
xxzz08xx The indicated address space does not exist or cannot be xx0008xx The system did not create a data space because the
accessed by the caller. designated owner does not exist.
xxzz09xx The indicated Hiperspace does not exist or cannot be xx000Axx The problem-state program with PSW key 8-F attempted
accessed by the caller. This could be caused by the to prefix the data space name with “SYS”, which is
owner of the Hiperspace being swapped out. reserved for system use.
SCC-8 OS/390 V2R8.0 MVS System Codes
01D 01D
xx000Bxx The caller specified an incorrect number of blocks for the xx0201xx The RELEASE request failed because the data space
data space size. does not exist.
xx000Dxx The specified data space name is not correct. It must be xx0202xx The RELEASE request failed because the start address
left-justified or non-blank, can contain only alphabetic, is not on a page boundary.
numeric and national characters, cannot start with a
xx0203xx The RELEASE request failed because the input
numeric character, and must be padded on the right with
STOKEN is not valid.
blanks.
xx0204xx The RELEASE request failed because the number of
xx000Exx A supervisor-state caller attempted to prefix the data
blocks is not valid.
space name with “SYSDS”, which is reserved for system
use. xx0205xx The RELEASE request failed because the requested
range of blocks is not in the addressable range of the
xx000Fxx An unauthorized caller requested creation of an ESO
data space.
Hiperspace.
xx0206xx The RELEASE request failed because the problem
xx0011xx The parameter list is inconsistent.
program caller attempted to release a SCOPE=ALL or
xx0012xx An unauthorized caller requested creation of a shared SCOPE=COMMON data space.
standard Hiperspace.
xx0207xx The RELEASE request failed because the problem-state
xx0013xx An problem-state program with PSW key 8-F tried to program tried to release storage in either a Hiperspace it
create a data space and assign ownership of the data does not own or a SCOPE=SINGLE data space it does
space to a task that is neither the caller's own task nor not own or did not create, or to release a data space on
the caller's job step task. behalf of an owner that is not in its primary address
space or is not the current dispatching task.
xx0014xx The creation of a SCOPE=COMMON data space failed
because the caller was swappable or because the xx0208xx The RELEASE request failed because the supervisor
system detected that the owner of a SCOPE=COMMON state program attempted to release a private data space
data space has become swappable. on behalf of an owner that is not in the supervisor state's
home or primary address space.
xx0101xx The DELETE request failed because a problem program
cannot specify TTOKEN. xx0209xx The RELEASE request failed because the caller is not in
key 0, and the key for the data space page did not
xx0102xx An authorized program specified a TTOKEN that is not
match the caller's key.
valid.
xx020Axx The RELEASE request failed because the data space
xx0103xx An authorized program attempted to delete a data space
page is fixed, or fixed in another view of a sharing
on behalf of an owner that is not its home or primary
group.
address space.
xx020Bxx The RELEASE request failed because the caller was
xx0104xx A service request block (SRB) mode request failed
disabled and requested release of enabled reference
because it did not specify a TTOKEN, which is required
storage.
to determine the owner.
xx020Cxx The RELEASE request failed because the caller
xx0105xx A specified STOKEN does not represent a valid data
requested a page that is READONLY.
space.
xx0213xx The RELEASE request failed because the range list con-
xx0106xx The specified STOKEN's owner (as specified by the
tains a non-zero value in one or more reserved fields.
TTOKEN) is not the owner of the data space.
xx0301xx The DEFINE IOON request failed because the data
xx0107xx The specified data space contains I/O defined pages.
space does not exist.
xx0108xx The specified data space contains pages mapped by the
xx0302xx The DEFINE IOON request failed because the start
DIV macro.
address is not on a 4-kilobyte boundary.
xx0109xx The specified data space contained pages for which a
xx0303xx The DEFINE IOON request failed because the input
DIV SAVE operation was in progress.
STOKEN is not valid.
xx010Axx A problem program attempted to delete a SCOPE=ALL
xx0304xx The DEFINE IOON request failed because the number
or SCOPE=COMMON data space.
of blocks is less than one.
xx010Bxx A problem program attempted to delete a
xx0305xx The DEFINE IOON request failed because the requested
SCOPE=SINGLE data space that has a key different
addressable range of blocks is not in the range of the
than the caller's key.
data space.
xx010Cxx A problem-state program with PSW key 8-F tried to
xx0306xx The DEFINE IOON request failed because the caller
delete a SCOPE=SINGLE data space, created by the
was in problem program state and not in system key.
caller's task, that was assigned ownership to a task
other than the caller's task or the caller's job step task. xx0307xx The DEFINE IOON request failed because the caller
attempted to DEFINE IOON for a SCOPE=SINGLE data
xx010Dxx The caller attempted to delete a Hiperspace while the
space on behalf of an owner that is not in the caller's
Asynchronous Data Mover Facility (ADMF) was still
home or primary address space.
processing a request to transfer data to or from the
Hiperspace. xx0308xx The DEFINE IOON request failed because the data
space page has a DIV SAVE operation in progress.
xx010Exx The caller attempted to delete a data space which has
one or more shared segments. xx0309xx The DEFINE IOON request failed because it was issued
for a hiperspace.
System Completion Codes SCC-9
01D 01D
xx030Bxx The DEFINE IOON request failed because the caller xx060Bxx The DEFINE DREFON request failed because the caller
was disabled and specified storage that was neither in a was disabled and specified storage that was neither in a
disabled reference (DREF) state or an IOON state. disabled reference (DREF) state nor an IOON state.
xx030Cxx The DEFINE IOON request failed because the input xx060Cxx The DEFINE DREFON request failed because the input
range list contains a non-zero value in one or more range list contains a non-zero value in one or more
reserved fields. reserved fields.
xx0401xx The DEFINE IOOFF request failed because the data xx060Dxx The requestor tried to DEFINE DREFON for a data
space does not exist. space with shared segments.
xx0402xx The DEFINE IOOFF request failed because the start xx071Bxx CREAD processing detected a PGSER fix in progress
address is not on a 4-kilobyte boundary. for the address space virtual storage.
xx0403xx The DEFINE IOOFF request failed because the input xx0B01xx An OUT failed because the data space does not exist.
STOKEN is not valid.
xx0B02xx An OUT failed because the start address is not on a
xx0404xx The DEFINE IOOFF request failed because the number page boundary.
of blocks is less than one.
xx0B03xx An OUT failed because the input STOKEN is not repres-
xx0405xx The DEFINE IOOFF request failed because the enting a caller's data space.
requested addressable range of blocks is not in the data
xx0B04xx An OUT failed because the number of blocks is not
space.
valid.
xx0406xx The DEFINE IOOFF request failed because the caller
xx0B05xx An OUT failed because the requested range of blocks is
was in problem program state and not in system key.
not in the range of the data space.
xx0407xx The DEFINE IOOFF request failed because the caller
xx0B06xx An OUT failed because the problem program caller
attempted to DEFINE IOOFF for a SCOPE=SINGLE
attempted to OUT a SCOPE ALL or SCOPE COMMON
data space on behalf of an owner that is not in the call-
data space.
er's home or primary address space.
xx0B07xx An OUT failed because the problem program caller
xx0408xx The DEFINE IOOFF request failed because it was
attempted to OUT a data space on behalf of an owner
issued for a Hiperspace.
that is not in its primary address space.
xx040Cxx The DEFINE IOOFF request failed because the input
xx0B08xx An OUT failed because the supervisor state program
range list contains a non-zero value in one or more
attempted to OUT a scope single data space on behalf
reserved fields.
of an owner that is not in its home address space.
xx0501xx The specified STOKEN does not represent a valid data
xx0B09xx An OUT failed because the data space is a Hiperspace.
space or represents a data space for which the caller is
not authorized. xx0C01xx A LOAD failed because the data space does not exist.
xx0503xx The new current size exceeds the maximum size for the xx0C02xx A LOAD failed because the start address is not on a
data space and Hiperspace. page boundary.
xx0601xx The DEFINE DREFON request failed because the data xx0C03xx A LOAD failed because the input STOKEN is not valid.
space does not exist. xx0C04xx A LOAD failed because the number of blocks is not
xx0602xx The DEFINE DREFON request failed because the start valid.
address is not on a 4-kilobyte boundary. xx0C05xx A LOAD failed because the requested range of blocks is
xx0603xx The DEFINE DREFON request failed because the input not in the range of the data space.
STOKEN is not valid. xx0C06xx A LOAD failed because the problem program caller
xx0604xx The DEFINE DREFON request failed because the attempted to LOAD a SCOPE ALL or SCOPE COMMON
number of blocks is less than one. data space.
xx0605xx The DEFINE DREFON request failed because the xx0C07xx A LOAD failed because the problem state program caller
requested addressable range of blocks extends beyond attempted to load a data space on behalf of the data
the end of the data space. space owner, but the data space is not in the owner's
primary address space.
xx0606xx The DEFINE DREFON request failed because the caller
was not in supervisor state. xx0C08xx A LOAD failed because the supervisor state program
attempted to load a scope single data space on behalf of
xx0607xx The DEFINE DREFON request failed because the caller
the data space owner, but the data space is not in the
attempted to use DREFON against storage in a scope-
owner's home address space.
single data space on behalf of an owner that is not in
the home or primary address space. xx0C09xx A LOAD failed because the data space is a Hiperspace.
xx0608xx The DEFINE DREFON request failed because the data xx0D01xx The DEFINE DREFOFF failed because the data space
space page has a DIV SAVE operation in progress. does not exist.
xx0609xx The DEFINE DREFON request failed because the input xx0D02xx The DEFINE DREFOFF failed because the start address
STOKEN is for a Hiperspace. is not on a 4-kilobyte boundary.
xx060Axx The DEFINE DREFON request failed because the speci- xx0D03xx The DEFINE DREFOFF failed because the input
fied area is part of a data space that was created with a STOKEN is not valid.
disabled reference (DREF) attribute. xx0D04xx The DEFINE DREFOFF failed because the number of
blocks is less than one.
SCC-10 OS/390 V2R8.0 MVS System Codes
01F 020
xx0D05xx The DEFINE DREFOFF failed because the requested System Programmer Response: If the caller was provided by the
addressable range of blocks is not in the range of the installation, correct it. Look at accompanying messages in the job
data space. log, the JCL and the SYSOUT output.
xx0D06xx The DEFINE DREFOFF failed because the caller was If the caller was an IBM-supplied program, search problem reporting
not processing in supervisor state with a system data bases for a fix for the problem. If no fix exists, contact the IBM
program status word (PSW) key. Support Center. Provide the messages, the JCL, the SYSOUT
output, and the ABEND dump.
xx0D07xx The DEFINE DREFOFF failed because the caller
attempted to DEFINE DREFOFF a SCOPE SINGLE or
data space on behalf of an owner that is not in its home 01F
or primary address space. Explanation: A unit of work attempted to end without removing all
xx0D09xx The DEFINE DREFOFF failed because the input its entries from the linkage stack. A hexadecimal reason code in reg-
STOKEN is for a Hiperspace. ister 15 explains the abend:
xx0D0Axx The DEFINE DREFOFF failed because the specified Code Explanation
area is part of a data space that was created with the 04 The unit of work issued an EXIT macro (SVC 3) without
disabled reference attribute. unstacking the linkage stack entries of the corresponding
xx0D0Dxx The requestor tried to DEFINE DREFOFF for a data request block (RB).
space with shared segments. 08 An RB routine did not unstack the linkage stack entries it
xxFF01xx The DSPSERV macro request failed because a sec- had added.
ondary address space identifier (ASID) is not valid. Source: Supervisor control
xxFF02xx The request failed because the caller held locks but indi- System Action: The system abends the task and may write a
cated DISABLED=NO. dump.
xxFF03xx The DSPSERV macro request failed because the caller Operator Response: If the system programmer asks for an SVC
issued a macro version that is not valid. dump, set the following SLIP trap:
xxFF04xx The DSPSERV macro request failed because reserved SLIP SET,COMP=ð1F,ACTION=SVCD,MATCHLIM=1,END
fields in the macro parameter list are not zeros.
System Programmer Response: Do the following:
xxFF05xx The DSPSERV macro request failed because the caller
1. If an SVC dump is not produced with the abend, ask the oper-
requested an unknown service.
ator to set a SLIP trap to obtain an SVC dump.
xxFF06xx The DSPSERV macro request failed because a pro-
2. In the system trace, find an SVC D or SVCE D entry for abend
tection exception occurred while referencing the caller's
X'01F'. Use this entry to determine which address space and
parameter list.
task control block (TCB) was active at the time of error. Note the
xxFF07xx The DSPSERV macro request failed because the caller address space identifier (ASID).
must be in 31-bit addressing mode to use any service of
3. Look at the linkage stacks for the TCBs associated with the
the DSPSERV macro.
active address space.
xxFF08xx The request failed because the caller was disabled but
4. Determine which linkage stack entries were not unstacked by
requested a service that requires the caller to be
examining the entries on the stack after the entry with the
enabled.
unstack suppression bit set on. The high-order bit of the linkage
xxFF09xx The request failed because the caller held one or more stack entry descriptor (LSED) is the unstack suppression bit.
locks needed by the system to process the request.
5. Identify the module that failed to remove its linkage stack entries
xxFF0Axx The request failed because the caller specified an input by using the program status word (PSW) address associated
range list for a service that does not support a range list. with the unstacked linkage stack entry.
xxFF0Bxx The request failed because the caller specified an incor- If the module is not an IBM module, continue diagnosis with
rect value for NUMRANGE. It must be greater than zero. the module.
xxFF0Cxx The request failed because the caller specified a value If the module is an IBM module, search problem reporting
for NUMRANGE that exceeded the maximum of 16 for data bases for a fix for the problem. If no fix exists, contact
an unauthorized caller. the component group associated with this module at the
xxFF0Dxx The request failed because the caller specified an input IBM Support Center. Provide all data collected and, if avail-
range list that is not accessible to the service using the able, the logrec data set error record.
caller's PSW key.
xxFF10xx The DEFINE request failed because IOON or IOOFF 020
was incorrectly coded. Explanation: The error occurred during processing of a BDAM
Source: Real storage manager (RSM) OPEN macro instruction.
System Action: The system sends messages about the job to the The control program found that the DCBMACRF field of the data
job log, writes an ABEND dump for the failing job step, and writes control block did not contain an A, K, or I, or an attempt was made
the JCL and SYSOUT output for the job. to open a BDAM data set that contained zero extents.
Programmer Response: If the caller was an application program, Source: DFSMSdfp
correct the program and run the job again. System Action: The system ends the task.
Programmer Response: In the first case, make sure that A, K, or I
is specified in the MACRF operand of the DCB macro instruction.
System Completion Codes SCC-11
021 023
Verify that the DCBMACRF field was correctly modified by the
023
problem program before the opening process. After making cor-
rections, reassemble the program and run the job step again. Explanation: LNKLST or library lookaside (LLA) encountered an
error that prevented LLA from completing some processing. LLA
In the second case, create the data set before attempting to open it
issues other contents supervision (CSV) messages with the abend
as a BDAM file.
code. When more than one abend has occurred, LLA includes the
System Programmer Response: If the error recurs and the original abend and reason code in the message or messages it
program is not in error, look at the messages in the job log for more issues for the sequence of abends.
information. Search problem reporting data bases for a fix for the
The hexadecimal reason code that describes the cause of the abend
problem. If no fix exists, contact the IBM Support Center. Provide the
is one of the following:
JCL and the program listing for the job.
Code Explanation
021 00000001 While LLA was copying directory entries from a LNKLST
Explanation: A task management macro passed an address space library to build a new LLA directory, dynamic allocation
control block (ASCB) address with an error indicated in the following or unallocation failed.
reason codes: 00000002 While LLA was copying directory entries from a LNKLST
Code Explanation library to build a new LLA directory, OPEN failed.
00 High order bits are set on in the input ASCB for move or 00000003 While LLA was building a new LLA directory, LLA found
add processing. a partitioned data set (PDS) directory block with a record
key equal to X'0000000000000000'.
04 ASCBNOQ bit is off in the ASCB for add processing.
00000004 While LLA was building a new LLA directory, LLA found
08 Attempt to add, move or delete the master scheduler a PDS directory block with an incorrect record key; the
address space. PDS directory block that contained the final PDS direc-
0C Acronym check for the input ASCB fails. tory entry did not have the correct record key of
X'FFFFFFFFFFFFFFFF'.
10 Incorrect CHAP entry function code.
00000005 While LLA was building a new LLA directory, LLA found
14 Incorrect EXTENDED MOVE function code.
a PDS directory entry with the name
18 Incorrect EXCNT count passed from the system. X'0000000000000000'.
1C Acronym check for the input enclave control block fails. 00000006 While LLA was building a new LLA directory, LLA found
Source: Task management a PDS directory block whose given length was too small
to contain an integral number of PDS directory entries.
System Action: The system abnormally ends the program that
issued the macro, writes a logrec data set error record, and writes a 00000007 While LLA was building a new LLA directory, LLA found
dump. a PDS directory block for which both of the following
were true:
Programmer Response: When calling the routine, ensure that the
high-order byte of the ASCB address is set to zero. Correct the error. The block did not contain the final directory entry in
Run the job again. the directory
The block's record key differed from the name of the
System Programmer Response: Collect all printed output and last PDS directory entry in the block.
output data sets related to the problem. Search problem reporting
data bases for a fix for the problem. If no fix exists, contact the IBM 00000008 While LLA was building a new LLA directory, LLA had
Support Center. Provide the logrec data set record and the dump. an I/O error.
00000009 While LLA was building a new LLA directory, LLA
022 reached the physical end of the PDS directory before
finding the last PDS directory block. The last block must
Explanation: The vector processing subsystem support (VPSS)
have a record key of X'FFFFFFFFFFFFFFFF'.
encountered a missing device end condition on control port 0. The
VPSS cannot continue processing or respond to operator com- 0000000A While LLA was building a new LLA directory, the direc-
mands. tory for an LLA-managed data set contained too many
directory entries for LLA to fit into its available virtual
Source: Vector processing
storage.
System Action: The VPSS missing interruption handler exit abnor-
0000000B LLA failed unexpectedly.
mally ends the VPSS monitor address space with system completion
code X'022'. The system issues message IGF991I to identify the 00000014 An I/O error occurred during LLA processing.
3838 Array Processor that caused the VPSS monitor address space 00000015 A media error occurred during LLA processing.
to end. The system writes a logrec data set error record.
00000016 An error occurred during data set processing.
Operator Response: Contact hardware support.
00000017 An error occurred during SMS processing.
Programmer Response: Determine why the 3838 Array Processor
is not responding with a device end. You may let the system oper- 00000018 SMS failed to obtain required resources.
ator restart the VPSS so that the operator may enter VPSS com- 00000019 An error occurred during LLA processing.
mands for other 3838 devices.
00000100 During LLA address space initialization processing, the
ATTACH of LLA's resource manager subtask failed.
SCC-12 OS/390 V2R8.0 MVS System Codes
023 023
00000101 LLA address space initialization processing determined 00000A04 LLA directory refresh processing failed unexpectedly
that the LLA fetch installation exit CSVLLIX1 was not while parsing the LLA parmlib member CSVLLAxx,
reentrant. which contains the control statements needed to perform
the LLA directory update.
00000102 LLA detected that its resource manager subtask abnor-
mally ended. 00000A05 LLA was unable to refresh a PDSE library.
00000103 LLA fetch installation exit CSVLLIX1 was AMODE 24. 00000A50 LLA's cross memory directory access routine was
entered with incorrect parameters.
00000201 While building a new LLA directory, LLA failed while
making a table of PDS or PDSE directory entries from 00000B00 LLA module staging processing did not convert a floating
the directory of an LLA-managed data set. point number to 64-bit unsigned binary because the
number was less than one.
00000202 LLA failed while building an index for a new LLA direc-
tory. 00000B01 LLA module staging processing was unable to convert a
floating point number to 64-bit unsigned binary because
00000203 While building a new LLA directory, LLA found no
the number was too big to be represented by 64 bits.
modules in the LNKLST.
00000B02 LLA module staging processing was unable to convert a
00000204 LLA directory build processing of the list of data sets to
floating point number to 64-bit unsigned binary because
be managed by LLA failed unexpectedly.
the number was not normalized.
00000205 LLA directory build processing failed because incorrect
00000B50 An incorrect LLPM parameter area has been passed to
data was detected while parsing the LLA parmlib
the LLA search routine.
member CSVLLAxx.
00000B51 The LLA search routine was called from a program
00000206 LLA directory build processing failed because LLA failed
which was not running under an supervisor request
unexpectedly while parsing the LLA parmlib member
block (SVRB).
CSVLLAxx.
00000B52 The LLA search routine was called with an incorrect
00000207 LLA directory build processing failed because LLA failed
DEB as input.
unexpectedly while processing a refresh request for spe-
cific members of an LLA-managed data set. 00000B53 The LLA search routine was called with an incorrect
value in LLPPCNCT.
00000208 During LLA MVS operator command processing, the
user did not have proper security authorization facility 00000C00 The pointer to LLA's component trace buffer was outside
(SAF) and security product (RACF) authorization to an of the projected storage range for the buffer.
LLA parmlib data set resource.
00000D00 LLA directory build processing failed unexpectedly while
00000401 Dynamic allocation (SVC 99) failed. LLA may have been: processing the LLA parmlib member CSVLLAxx.
Allocating an LLA-managed data set to read its 00000D01 LLA directory update processing failed while reading the
directory to build a new LLA directory. LLA parmlib member CSVLLAxx, which contains the
Allocating an LLA-managed data set to copy control statements needed to perform the LLA directory
modules from it while staging modules. update. The parmlib read routine detected that the input
Allocating SYS1.parmlib or another parmlib data set parameter list contained incorrect data.
to process an LLA start or update request.
00000D02 LLA directory refresh processing failed unexpectedly
Unallocating a data set that LLA had previously allo-
while reading the LLA parmlib member CSVLLAxx,
cated.
which contains the control statements needed to perform
00000500 Dynamic allocation or unallocation failed while LLA was the LLA directory update.
staging modules for an LLA-managed library into the
00000D03 LLA directory refresh processing failed unexpectedly
virtual lookaside facility (VLF) data space.
while parsing the LLA parmlib member CSVLLAxx,
00000501 The LLA staging installation exit CSVLLIX2 was AMODE which contains the control statements needed to perform
24. the LLA directory update.
00000A00 While LLA was obtaining PDS directory entries for an 00000D05 LLA directory refresh processing failed unexpectedly
LLA-managed data set during a selective module while allocating the LLA parmlib member CSVLLAxx,
refresh, BLDL returned with a return code greater than which contains the control statements needed to perform
4. the LLA directory update. The allocation was performed
using the IEFPRMLB service. A previous message
00000A01 LLA directory refresh processing could not obtain suffi-
issued by the IEFPRMLB service accompanies this
cient storage to hold all the PDS directory entries accu-
ABEND.
mulated from selective LLA directory refreshes.
00000E01 While LLA was building a new LLA directory, dynamic
00000A02 LLA directory update processing failed while reading the
allocation or unallocation failed.
LLA parmlib member CSVLLAxx, which contains the
control statements needed to perform the LLA directory 00000E02 While LLA was building a new LLA directory, OPEN
update. The parmlib read routine detected that the input failed.
parameter list contained incorrect data.
00000E03 While LLA was building a new LLA directory, LLA found
00000A03 LLA directory refresh processing failed unexpectedly no data sets to manage.
while reading the LLA parmlib member CSVLLAxx,
00000E04 While LLA was building a new LLA directory, LLA found
which contains the control statements needed to perform
that a data set to be managed by LLA was not a PDS.
the LLA directory update.
System Completion Codes SCC-13
023 023
00000E05 While LLA was building a new LLA directory, LLA found 00000101 LLA initialization issues message CSV232I, and con-
that FREEZE or NOFREEZE was specified for a tinues processing as if CSVLLIX1 was not installed in
non-LLA data set. the LNKLST.
00000E06 During LLA MVS operator command processing, the 00000102 LLA's resource management subtask abnormally ends,
user did not have proper SAF and security product and then the LLA address space also abnormally ends.
(RACF) authorization to an LLA-managed data set
00000103 LLA initialization issues message CSV232I, and con-
resource.
tinues processing as if CSVLLIX1 was not installed in
| 00000E07 While LLA was building a new LLA directory, LLA found the LNKLST.
| that a data set to be managed by LLA was a PDSE that
00000201 For dynamic allocation errors, LLA issues message
| was not known to be a load library. Make sure that the
CSV224I; for PDS related I/O errors, LLA issues
| data set was not empty and had at least one program
message CSV225I, for PDSE related errors, LLA issues
| object in it.
message CSV247I. In any case, LLA issues message
00001200 The caller invoked an LLACOPY macro with an incorrect CSV221I to show how far the LLA directory build had
data control block (DCB) parameter. progressed prior to the error, and includes a reason
code that identifies the specific error. Then, if the error
00001201 The caller invoked an LLACOPY macro with an incorrect
occurred during an LLA directory refresh, LLA issues
DCB parameter. The DCB does not point to a valid DEB.
CSV217I and keeps the old directory active. Otherwise,
00001202 The caller invoked an LLACOPY macro whose DCB ref- the LLA address space ends.
erences a data set for which the user does not have
00000202, 00000204, 00000206, 00000207 For the original abend
proper SAF security (RACF) authorization.
that LLA detected, LLA takes an SVC dump and records
00001203 The caller invoked an LLACOPY macro with a zero DCB the error in the logrec data set. LLA then issues this
parameter. abend. If the error occurred during initial build proc-
00001204 The caller invoked an LLACOPY macro with an incorrect essing, LLA ends its address space. Otherwise, LLA
level parameter list or non-zero reserved fields. keeps the old directory active.
00001205 The user invoked an LLACOPY macro while in problem 00000203 LLA takes an SVC dump and records the error in the
state. logrec data set. Then, if the error occurred during an
LLA directory refresh, LLA issues CSV217I and keeps
Source: Contents supervision (CSV)
the old directory active. Otherwise, the LLA address
System Action: If the LLA address space ends because of this space ends.
error, the system usually attempts to restart LLA in another address
00000205 LLA issues message CSV235I, CSV236I. If the error
space. LLA issues one or more of the following messages: CSV222I,
occurred during an LLA directory refresh, LLA issues
CSV226E, CSV227I, CSV247I.
message CSV217I and keeps the old directory active.
If the failed LLA address space had not become active and had Otherwise, the LLA address space ends.
been created to recover from a prior LLA address space failure, the
00000208 If the error occurred during an LLA directory refresh, LLA
system issues message CSV218E without restarting LLA.
issues CSV217I and keeps the old directory active. If the
Specific system actions for each reason code are as follows: error occurred during an initial directory build, LLA
issues abend X'023', reason code 204, to end its
Code System Action
address space.
00000001 This error was preceded by an abend for which LLA took
00000401 LLA issues message CSV224I, which includes dynamic
an SVC dump and recorded the error in logrec data set.
allocation's specific error and information codes. LLA
If SVC 99 itself failed, LLA issues abend X'023', reason
takes an SVC dump and records the error in logrec data
code X'00000401', and message CSV224I. If this error
set. LLA's subsequent actions depend on the task LLA
occurred during an initial LLA directory build, LLA also
was performing when the dynamic allocation was
issues abend X'023', reason code X'00000201', to
requested:
end its address space.
For MVS/SP 3.1, if LLA was allocating a data set to
00000002 through 00000019 DFSMS may take an SVC dump. LLA
read its directory to build a new directory, then LLA
records this error in the logrec data set. The indicated
issues message CSV221I. If the error occurred
library will not be processed. LLA issues message
during an LLA directory refresh, LLA also issues
CSV221I or CSV247I, which contains this reason code
message CSV217I and keeps the old directory
in its message text. If this error occurred during an initial
active. If the error occurred during an initial directory
LLA directory build, LLA also issues abend X'023',
build, LLA issues abend X'023', reason code
reason code X'00000201', to end its address space.
X'00000201', to end its address space.
00000100 LLA takes an SVC dump and records this error in the
For MVS/SP 3.1.0e or higher, if LLA was allocating
logrec data set. The next system action depends on
a data set to read its directory to build a new direc-
what release you are using; for MVS/SP 3.1, the LLA
tory, then LLA issues message CSV241I. If the error
address space ends. For MVS/SP 3.1.0 or higher, LLA
occurred during an LLA directory refresh, LLA also
continues processing without its resource management
issues message CSV217I and keeps the old direc-
subtask until it determines if the reattach threshold has
tory active. If the error occurred during an initial
been reached. If the threshold has not been reached,
directory build, LLA issues abend X'023', reason
LLA attempts to reattach the subtask. Otherwise, LLA
code X'00000204', to end its address space.
continues processing without its resource management
subtask. If LLA was allocating a data set to copy modules
from it while staging modules, then LLA does not
stage modules from this library.
SCC-14 OS/390 V2R8.0 MVS System Codes
023 023
If LLA was allocating a parmlib data set to process issues abend X'023', reason code X'204' to end its
a start LLA request, LLA issues message CSV235I, address space.
CSV236I, and does not start the LLA address
00000E02 LLA issues message CSV240I, which includes the name
space.
of the data set which could not be opened. This error is
If LLA was allocating a parmlib data set to process preceded by an abend for which LLA takes an SVC
a LLA refresh request, LLA issues message dump and records this error in the logrec data set. If the
CSV235I, CSV236I and keeps the old directory error occurred during an LLA directory refresh, LLA also
active. issues message CSV217I and keeps the old directory
active. If the error occurred during an initial directory
If LLA was unallocating a data set that it had previ-
build, LLA issues abend X'023', reason code X'204' to
ously allocated, then LLA takes no further action.
end its address space.
00000500 If SVC 99 itself failed, LLA issues abend X'023', reason
00000E03 If the error occurred during an LLA directory refresh, LLA
code 401, and message CSV224I. LLA's subsequent
also issues message CSV217I and keeps the old direc-
actions depend on what release you are using.
tory active. If the error occurred during an initial directory
For MVS/SP 3.1, this error was preceded by an abend build, LLA issues abend X'023', reason code 204 to
for which LLA took an SVC dump and recorded the error end its address space.
in the logrec data set. LLA's resource manager subtask
00000E04 LLA issues message CSV242I, which includes the name
ends, causing the LLA address space to end.
of the data set which is not a PDS. If the error occurred
For MVS/SP 3.1.0e or higher, LLA's resource manager during an LLA directory refresh, LLA also issues
subtask ends and LLA continues processing without its message CSV217I and keeps the old directory active. If
resources management subtask until it determines if the the error occurred during an initial directory build, LLA
reattach threshold has been reached. If the threshold issues abend X'023', reason code X'204' to end its
has not been reached, LLA attempts to reattach the address space.
subtask. Otherwise, LLA continues processing without its
00000E05 LLA issues message CSV245I, which includes the name
resource management subtask.
of the data set for which FREEZE or NOFREEZE was
00000501 LLA issues message CSV232I, and continues proc- specified. If the error occurred during an LLA directory
essing as if CSVLLIX2 was not installed in the LNKLST. refresh, LLA also issues message CSV217I and keeps
00000A00 through 00000A05 LLA takes an SVC dump and records the old directory active. If the error occurred during an
the error in the logrec data set. Then, LLA issues initial directory build, LLA issues abend X'023', reason
message CSV217I, and does not perform the requested code X'204', to end its address space.
LLA refresh. 00000E06 If the error occurred during an LLA directory refresh, LLA
00000A50 If the caller is LLA or BLDL, the caller takes an SVC issues CSV217I and keeps the old directory active. If the
dump and records the error in the logrec data set. Then, error occurred during an initial directory build, LLA
the caller ends the LLA address space with an abend issues abend X'023', reason code 204, to end its
312. address space.
00000B00 through 00000B02 LLA takes an SVC dump and records 00000E07 LLA issues message CSV242I which includes the name
the error in the logrec data set. Then, LLA's resource of the data-only or empty PDSE. If the error occurred
manager subtask ends, and LLA also issues abend during an LLA directory refresh, LLA also issues
X'023', reason code X'00000102', to end its address message CSV217I and keeps the old directory active. If
space. the error occurred during an initial directory build, LLA
issues abend X'023', reason code X'00000204' to end
00000B50, 00000B51, 00000B52, 00000B53 If the caller is BLDL,
the address space.
the caller takes an SVC dump, records the error in the
logrec data set. and abends the caller with a X'212' 00001200 LLACOPY abends.
abend. If the caller is LLA, the caller takes an SVC 00001201 LLACOPY abends.
dump, records the error in the logrec data set, and pro-
00001202 LLACOPY abends.
vides the module using program fetch.
00001203 LLACOPY abends.
00000C00 LLA takes an SVC dump and records the error in the
logrec data set. Then, LLA trace is deactivated, and LLA 00001204 LLACOPY abends.
continues without component trace capabilities.
00001205 LLACOPY abends.
00000D00, 00000D01, 00000D02, 00000D03 LLA takes an SVC
Operator Response: Contact hardware support.
dump and records the error in the logrec data set. If the
error occurred during an LLA directory refresh, LLA Programmer Response: Follow the application programmer
issues message CSV217I and keeps the old directory response for accompanying CSV messages issued both to the
active. Otherwise, the LLA address space ends. console and the system log (SYSLOG). Follow the application pro-
grammer response for any other accompanying abends.
00000E01 LLA issues message CSV224I, which includes dynamic
allocation's specific error and information codes. If the For the reason codes below, do the following:
error occurred while allocating the data set, LLA issues Code Response
message CSV241I which includes the name of the data
00000101 Make sure that the LLA fetch installation exit, CSVLLIX1,
set which could not be allocated. If the error occurred
is reentrant, and then link edit the exit again.
during an LLA directory refresh, LLA also issues
message CSV217I and keeps the old directory active. If 00000103 Make sure that the LLA fetch installation exit, CSVLLIX1,
the error occurred during an initial directory build, LLA is AMODE 31 or AMODE ANY, and then link edit the
exit again.
System Completion Codes SCC-15
024 026
00000203 Verify that the catalog for the LNKLST data sets is valid The Logrec data set error record.
and has not been overlaid.
00000208 Ensure that the person who issues the LLA operator 024
command has proper RACF authorization (update) to the Explanation: An abnormal end occurred in Print Services Facility
LLA-managed data sets. (PSF). The PSF ESTAE routs determine whether PSF can be
00000501 Make sure that the LLA staging installation exit, restarted and the recovery end manager requests a PSF restart. This
CSVLLIX2, is AMODE 31 or AMODE ANY, and then link system completion code and a PSF abend reason code are con-
edit the exit again. tained in either message APS050I or APS521I.
00000A00 Follow the programmer response for CSV217I, and see Source: DFSMSdfp
the logrec data set, which may contain information on Programmer Response: Respond as indicated for messages
specific I/O errors. If no specific I/O error is evident, then APS050I or APS521I.
stop and restart LLA.
System Programmer Response: If the error recurs and the
00000A01 Follow the programmer response for CSV217I, and issue program is not in error, search problem reporting data bases for a fix
a complete LLA refresh. for the problem. If no fix exists, contact the IBM Support Center.
00000A50 through 00000B02 Restart LLA.
00000B50, 00000B51, 00000B52, 00000B53 Respond to any 025
related messages that appear in the system log Explanation: The system was initiating a piece of work when a
(SYSLOG) and to any related abends. Follow the pro- system error occurred. The reason code is in register 15 at the time
grammer response for a X'212' abend. the system issues the abend.
00000C00 To regain component trace capabilities, stop and then Code Explanation
restart LLA.
0002 The APPC Asynchronous_Manager callable service
00000E03 Verify that the parmlib members specifying the list of returned an error code to the initiator.
data sets LLA is to manage is correct. Follow the pro-
0003 The system found too many parameters on the job used
grammer response in for messages CSV217I or
to start the scheduler.
CSV218I.
0004 The user tried to run the initiator under the initiator.
00000E06 Ensure that the person who issued the LLA operator
command has proper RACF authorization (update) to the Others The system found an internal error.
LLA-managed data sets. Source: Initiator/terminator
00000E07 Eliminate the PDSE data-only library from the specified System Action: The system writes an SVC dump, writes the logrec
parmlib member. data set error records, and ends initiator processing.
00001200 Correct the DCB input parameter for the LLACOPY System Programmer Response: Depending on the reason code,
macro. Make sure that the input DCB has been opened do the following:
and that the DCB is not being overlaid. Run the job step
again. Code Response
00001201 Correct the DCB input parameter for the LLACOPY 0002 Contact the IBM Support Center.
macro. Make sure that the input DCB has been opened, 0003 Check the parameters on the job used to start the
and that the DCB is not being overlaid and points to a scheduler.
valid DEB. Run the job step again.
0004 Rename the program that is causing the abend.
00001202 Ensure that the invoker of the LLACOPY macro has suf-
For all other reason codes, search problem reporting data bases for
ficient RACF authority to the data sets described by the
a fix for the problem. If no fix exists, contact the IBM Support Center.
LLACOPY input DCB. Run the job step again.
Provide the SVC dump and the logrec data set error records.
00001203 Correct the DCB input parameter of the LLACOPY
macro. The input DCB must be a valid opened DCB.
026
Run the job step again.
Explanation: Cross-system extended services (XES) encountered
00001204 Ensure that all reserved fields are zero. Ensure that the
an error. See OS/390 MVS Diagnosis: Reference for more informa-
macro library used to compile or assemble the program
tion on diagnosing sysplex problems.
invoking LLACOPY corresponds to the target environ-
ment. Run the job step again. A hexadecimal reason code in register 15 explains the error:
00001205 Ensure that the invoker of the LLACOPY macro is super- Code Explanation
visor state. Run the job step again. 0A060002 XES processing could not prevent SRB to task
System Programmer Response: Follow the system programmer percolation however its processing has continued suc-
response for any messages issued to the console or the job log and cessfully and no action need be taken on the part of the
for any accompanying abends. user.
If the problem persists and the program is not in error, search 0C010101 Error in user's Complete Exit. The connector will be ter-
problem reporting data bases for a fix for the problem. If no fix minated. Review the exit processing of the application.
exists, contact the IBM Support Center. Provide the following: The issue a dump.
All printed output and output data sets related to the problem. 0C150101 Error in user's Contention Exit. The connector will be ter-
minated. Review the exit processing of the application.
The program listing for the job.
The system does not issue a dump.
The JCL for the job.
SCC-16 OS/390 V2R8.0 MVS System Codes
027 027
0C150103 Return code error from user's Contention Exit. The user 02040001 020A0001 020D0001 02120001 03200001
specified that the Contention Exit was to be deferred 05010001 05060001 070B0001 07160001 081A0001
during rebuild processing, but the structure was not 0A010001 0A010002 0A010102 0A020102 0A040103
0A060101 0A060103 0A090101 0A0D0001 0A0D0002
being rebuilt. The connector will be terminated. Review
0A0D0004 0A060003 0A0D0101 0A130103 0A130104
the exit processing of the application. The system does 0A130106 0A160001 0A160101 0A160102 0C090001
not issue a dump. 0C0A0001 0C0B0106 0C0C0105 0C0D0101 0C130101
0C340102 Error in user's Complete Exit for a list or cache con- 0C170101 0C190001 0C1Cxxxx 0C1D0101 0C21xxxx
0C23xxxx 0C26xxxx 0C2A0001 0C2A0002 0C2A0003
nection. The connection is terminated.
0C2A0004 0C2A0005 0C2A0006 0C2A0007 0C2A0008
0C3F0101 Error in user's Notify Exit. The connector will be termi- 0C2A0009 0C2A000A 0C2A000B 0C2A000C 0C2A000D
nated. Review the exit processing of the application. The 0C2A000E 0C2A000F 0C2A0010 0C2A0011 0C2A0012
system does not issue a dump. 0C2A0013 0C2A0014 0C2D0001 0C2F0101 0C2F0102
0C30xxxx 0C340001 0C340002 0C340101 0C340103
0C5A0003 XES processing could not prevent SRB to task 0C340104 0C340105 0C340106 0C380001 0C380002
percolation. However, its processing has continued suc- 0C380003 0C380004 0C380005 0C380009 0C380106
cessfully and no action need be taken on the part of the 0C380107 0C380108 0C390001 0C391013 0C3C0107
user. 0C3C0108 0C400101 0C41xxxx 0C440101 0C460101
0C4A0101 0C4A0103 0C54xxxx 0C540101 0C560001
0C5A0004 XES processing could not prevent SRB to task 0C560002 0C560003 0C560004 0C560005 0C560150
percolation. However, its processing has continued suc- 0C5A0101 0C5A0102 0C5B1013 0C650001 0C670101
cessfully and no action need be taken on the part of the 0C680102 0C6C0001 0C700102 0C740101 0C740103
0C760102 0C7C0001 0C7C0002 0C7C0003 0C830001
user.
0C830002 0C830003 0C890101 0C890102 0C920002
0C680101 Error in user's Notify Exit. The connector will be termi- 0C950001 0C950102 0C950103 0C9E0001 0C9E0101
nated. Review the exit processing of the application. The 0D010001 0D010101 0D010102 0D010103 0D010104
system does not issue a dump. 0D070101 0D070102 0D070103 0D070104 0D070105
0D0C0001 0D0C0150 0D120101 0D120102 0D120103
0E0A0101 Error in user's List Transition Exit. The connector will be 0D120007 0D120008 0D120150 0D150004 0D150101
terminated. Review the exit processing of the applica- 0D150102 0D150103 0D150150 0D180101 0D1C0001
tion. The system does not issue a dump. 0D1C0150 0E0A0102 0E0B0004 0E0C0103 0E0D0102
0E0F0101 0E120001 0E130004 0E130101 0E130102
0E0D0001 Unexpected return code from user Event Exit. The con- 11050001
nector will be terminated. Review the exit processing of
the application. The system does not issue a dump. System Programmer Response:
0E0D0101 Error in user's Event Exit. The connector will be termi- Format the SVC dump with the following IPCS subcommands:
nated. Review the exit processing of the application. The XESDATA, including all the reports at all levels - summary,
system does not issue a dump. detail, and exception.
Source: Cross-system extended services (XES) CTRACE COMP(SYSXES) SUB((GLOBAL))
System Action: Additional messages explaining the error may CTRACE COMP(SYSXES) SUB((individual-connections))
precede the ABEND. If there is a hexadecimal value of '01' in the
third byte of the reason code the connector issuing the IXLCONN You can determine the individual connections by issuing the
service will be terminated by the system. The system issues an SVC CTRACE QUERY command to see the sub name traces associ-
dump, unless the abend is related to the failure of a user exit. ated with SYSXES.
Operator Response: The following reason codes represent errors Search problem reporting data bases for a fix for the problem. If no
internal to the XES component. Call the IBM Support Center for fix exists, contact the IBM Support Center. Provide the formatted
assistance with these errors. SVC dump.
Reason Codes: 027
Explanation: An abnormal end occurred in Print Services Facility
(PSF). The PSF ESTAE routs determine whether PSF can be
restarted but the recovery end manager does not request a PSF
restart. This system completion code and a PSF abend reason code
are contained in either message APS050I or APS521I.
Source: DFSMSdfp
Programmer Response: Respond as indicated for messages
APS050I or APS521I.
System Programmer Response: If the error recurs and the
program is not in error, search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support Center.
System Completion Codes SCC-17
028 02A
0014 The requested VIO page number is greater than the
028
number of pages in the VIO data set.
Explanation: The system could not complete a paging operation for
0018 The requested VIO page does not exist.
one of the following reasons:
0020 The system could not create tables in storage for the
A permanent I/O error occurred during a page-in or swap-in
requested VIO pages.
operation. The data being paged in or swapped in is lost.
0024 The requested VIO page previously suffered an I/O
A page cannot be accessed on auxiliary storage because of a
error.
previous I/O error.
0028 The system does not contain a valid auxiliary storage
An indeterminable error occurred during management of central
copy of the requested VIO page.
storage paging. The system ends processing. Register 15 may
contain a reason code. Source: Auxiliary storage manager (ASM) and Allocation
The operator canceled a Time Sharing Option Extensions System Action: The system abnormally ends the current task. The
(TSO/E) user before the TSO/E logon completed. system writes a logrec data set error record.
An address space referred to a pageable link pack area (PLPA) System Programmer Response: If the problem cannot be
page that contains noncontiguous code or large constant areas. resolved, search problem reporting data bases for a fix for the
The system had already detected this error and issued message problem. If no fix exists, contact the IBM Support Center.
IEA928I. See message IEA928I.
The system found an unexpected error while processing a 02A
swap-in or swap-out request. The error is described by a reason Explanation: An error occurred during execution of a data manage-
code in register 6. ment request for a spool data set. The hexadecimal reason code in
The only current copy of a page resides in a defective frame on Register 2 indicates the cause of the abend:
expanded storage. An error occurred when the system tried to Code Explanation
bring the page into central storage from the defective expanded
00000004 HASCHAM found that a data management control block
frame.
(ACB or DEB) was not valid.
An I/O error occurred when the system wrote the page to auxil-
00000008 HASCHAM found that a JES2 UBUF was not valid.
iary storage.
0000000C HASCHAM detected a serialization error for a spool data
An I/O error occurred when the system attempted to transfer
set.
data from a data-in-virtual object into a mapped window page.
00000014 JES2 detected an error during CLOSE or ENDREQ
Source: Auxiliary storage manager (ASM) and real storage manager
processing for an internal reader. The JES2 access
(RSM)
method did not receive the correct response from the
System Action: The system abnormally ends the current task or JES2 address space.
address space.
00000018 JES2 detected an error when processing an internal
Operator Response: If the system issued message IEA928I, see reader data set. JES2 issued the $HASP095 message to
the operator response for that message. Otherwise, notify the system describe the error.
programmer.
0000001C JES2 detected inconsistent temporary protected buffer
System Programmer Response: Look for messages indicating a pointers.
hardware error. If you find any, contact hardware support. Search
00000020 HASCHAM detected a serialization error for an internal
problem reporting data bases for a fix for the problem. If no fix
reader data set.
exists, contact the IBM Support Center. The logrec data set error
record might not contain information regarding this abend. 00000024 HASCHAM detected a JES2 internal logic error when
processing an internal reader data set.
029 Source: JES2
Explanation: The auxiliary storage manager's (ASM) page oper- System Action: The system ends the task, and produces a dump.
ations starter routine detected an incorrect virtual I/O (VIO) request. For reason codes X'0000000C' and X'00000020', the system ter-
The logrec data set error record contains the incorrect VIO request minates the job step, and produces a dump.
reason code: System Programmer Response: Obtain the program listing for the
Code Explanation job. Look at the messages in the job log. If the JOB statement did
not specify MSGLEVEL=(1,1), specify it and run the job again.
0004 The requested VIO logical group number is greater than
the maximum allowable logical group number. Verify that the problem program did not modify data management
control blocks or the JES2 UBUF control block. For reason codes
0008 The requested VIO logical group number is not assigned X'0000000C' and X'00000020', also verify that the problem
to any logical group. program used proper serialization techniques for sharing a SYSIN,
000C The calling program does not have access to the SYSOUT or internal reader data set among multiple tasks. After
requested VIO logical group. making corrections, execute the job step again.
0010 The requested VIO logical group cannot accept new If the problem recurs and if the program is not in error, search
work because work is already pending for that logical problem reporting data bases for a fix for the problem. If no fix
group. exists, contact the IBM Support Center.
SCC-18 OS/390 V2R8.0 MVS System Codes
02B 02E
02B 02E
Explanation: A user exit routine issued a return code that is higher Explanation: The system found an error during availability manager
than the maximum return code value specified in the MAXRC param- (AVM) processing. One of the following contains a reason code that
eter of the $EXITnnn macro instruction. explains the error:
Source: JES2 Register 15 in the SDWA or RTM2WA data areas at the time of
the error.
System Action: The system abnormally ends the user task and
issues a dump. The SDWACRC field in the SDWA data area.
Operator Response: Use the $TEXIT command to disable Message AVM010E.
EXITnnn.
The reason code is in the form mmrrssss.
System Programmer Response: Collect all printed output and
In the reason code:
output data sets related to the problem.
mm The identifier for the availability manager entry point that
If the exit routine is issuing an incorrect return code, correct the
issued the abend
routine. If the routine is issuing the correct return code, change the
maximum return code value specified on the $EXITnnn macro rr A hexadecimal error indicator, which is one of the
instruction. Then rerun the job. following:
Indicator Explanation
02C 2 The system could not find an entry point in
Explanation: An error occurred in JES2 support of a functional the nucleus.
subsystem address space. 12 The system could not find a load module.
When this system completion code appears without a JES2 18 The primary availability manager load
message, the following information applies: module was not started by started task
During a hot start, either: control (STC).
HASPWARM found an active Functional Subsystem (FSS) with 19 Incorrect parameters were received through
no active FSA the START AVM command. The availability
JES2 found that the FSS address space was being connected manager checks for one of the following
with no active FSA. values in the AVMMODE parameter: OPER-
ATOR, THINLAYER, or RESTART.
Source: JES2
28,2A,2B,48 The availability manager continues to run
System Action: HASPWARM uses CALLRTM macros to abnor-
normally. However, no additional subsys-
mally end the FSS address space.
tems may connect to the availability
Operator Response: Enter a $S PRT command to restart the FSS. manager until an equal number of current
Programmer Response: This condition occurred because a func- subsystem users disconnect from it. The
tional subsystem printer either was drained or started during a JES2 availability manager reached the maximum
hot start. HASPWARM ended the FSS address space in case the number of subsystems that it can handle.
printer initialization parameter was changed across hot start. 34,35,37 The availability manager received an error
One of the following messages may also accompany this system return code from the I/O supervisor. The
completion code: IOS return code is located in the third byte
of the availability manager reason code. The
$HASP413 fourth byte of the availability manager
$HASP415 reason code contains an associated IOS
$HASP750 reason code. The error indicator specifies
See OS/390 JES2 Messages for more information. which IOS service the availability manager
was trying to use:
02D 34 PREVENTIO
Explanation: The JES2 main task has abnormally terminated. One 35 IOPIDENT-RELEASE
of the following events caused the termination.
37 IOPIDENT-OBTAIN
The operator issued a $PJES2,ABEND command, which termi-
39 The availability manager could not access
nated JES2.
subsystem owned storage to store the
A JES2 catastrophic error/abend has occurred. For further results of a CALLAVM request. Most likely,
details concerning the abend, see message $HASP095. from the time the availability manager veri-
Source: JES2 fied the CALLAVM request to the time it
completed the request, the subsystem has
System Action: The system invokes JES2 recovery/termination freed the storage.
processing.
The following error indicators specify an internal error in
Operator Response: Notify the system programmer. the availability manager and, in most cases, cause
System Programmer Response: To help you determine the nature abnormal ending of the availability manager address
of the problem, refer to error messages $HASP088 and $HASP095. space:
01
03-11
System Completion Codes SCC-19
030 032
13-17 the data control block indicate the possible causes of the original
1A-27 error:
29
DCBEXCD1:
2C-33
38 Bit Explanation
3A-47 0 Record not found.
49
1 Incorrect actual address for lower limit.
ssss The related system service completion codes
2 Space not found.
Source: Availability manager (AVM)
3 Incorrect request.
System Action: The system abends the current task.
4 Uncorrectable input error.
Operator Response: Depending on the error indicator rr, do one of
5 Uncorrectable output error.
the following:
6 Block could not be reached (input).
Indicator Response
7 Block could not be reached (update).
18 Do not try to start the availability manager under an initi-
ator. Use the START command. DCBEXCD2:
19 When you issue the START AVM command, omit the Bit Explanation
AVMMODE parameter.
0 Sequence check.
Otherwise, notify the system programmer.
1 Duplicate record.
System Programmer Response: Depending on the error indicator
2 DCB closed when error detected.
rr, do one of the following:
3 Overflow record.
Indicator Response
4 PUT: length of field greater than length indicated in
2 Ensure that the availability manager was installed cor-
DCBLRECL field of the data control block.
rectly. Ensure that the availability manager's load
modules contain all the correct CSECTs. 5-7 (Reserved bits).
12 Ensure that the availability manager was installed cor- Source: DFSMSdfp
rectly. Ensure that the load libraries contain the correct Programmer Response: Examine the DCBEXCD1 and
load modules. DCBEXCD2 fields of the data control block to determine the cause of
34,35,37 Correct the failing program. the error. Specify the address of an error analysis routine to be given
control when an I/O error is detected and, for errors occurring during
CLOSE, run a QISAM CLOSE macro instruction prior to returning
030
control to the supervisor. For errors occurring during the processing
Explanation: The error occurred during processing of a basic index of a QISAM CLOSE macro instruction, respond as indicated by
sequential access method (BISAM) or queued indexed sequential message IEC011I or IEC203I.
access method (QISAM) OPEN macro instruction.
System Programmer Response: If the error recurs and the
The control program found that the DCBMACRF field of the data program is not in error, look at the messages in the job log for more
control block (DCB) did not indicate a valid mode of operation for information. Search problem reporting data bases for a fix for the
BISAM or QISAM. The DCBMACRF field is set up by the MACRF problem. If no fix exists, contact the IBM Support Center. Provide the
operand of the DCB macro instruction or by the problem program JCL and the program listing for the job.
before the data control block is opened.
Source: DFSMSdfp 032
Programmer Response: Make sure that a valid mode of operation Explanation: An error occurred during processing of a basic index
is specified in the MACRF operand of the DCB macro instruction. sequential access method (BISAM) or queued indexed sequential
Verify that the DCBMACRF field was not incorrectly set up or modi- access method (QISAM) OPEN macro instruction.
fied by the problem program. After making corrections, reassemble
The control program found that the DCBMACRF field of the data
the program and run the job step again.
control block (DCB) did not contain valid information for ISAM.
System Programmer Response: If the error recurs and the
Source: DFSMSdfp
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 Programmer Response: Make sure that valid information is speci-
problem. If no fix exists, contact the IBM Support Center. Provide the fied in the MACRF operand of the DCB macro instruction. Verify that
JCL and the program listing for the job. the DCBMACRF field was not incorrectly modified by the problem
program before the opening process.
031 After making corrections, reassemble the program and run the job
step again.
Explanation: An I/O error occurred during processing using
QISAM. The control program attempted to pass control to an error System Programmer Response: If the error recurs and the
analysis (SYNAD) routine, but found that (1) the DCBSYNAD field of program is not in error, look at the messages in the job log for more
the data control block did not contain the address of a valid SYNAD information. Search problem reporting data bases for a fix for the
routine, or (2) the error occurred after a CLOSE macro instruction problem. If no fix exists, contact the IBM Support Center. Provide the
was run by task end (the problem program returned control to the JCL and the program listing for the job.
supervisor without processing a CLOSE macro instruction). The task
was abnormally ended. The DCBEXCD1 and DCBEXCD2 fields of
SCC-20 OS/390 V2R8.0 MVS System Codes
033 036
Provide no virtual storage area and either do not specify the
033
contents of the DCBSMSI and DCBMSHIA fields or set the fields
Explanation: The error occurred during processing of an OPEN to zero. The highest level index can then be processed without
macro instruction for an indexed sequential data set. If the error being loaded into virtual storage.
occurred during the processing of an indexed sequential access
After making corrections, reassemble the program and run the job
method (ISAM) OPEN executor, register 15 contains a hexadecimal
step again.
reason code:
System Programmer Response: If the error recurs and the
Code Explanation
program is not in error, look at the messages in the job log for more
01 An I/O error occurred while reading the highest level information. Search problem reporting data bases for a fix for the
index. problem. If no fix exists, contact the IBM Support Center. Provide the
02 An I/O error occurred while searching for the end-of-file JCL and the program listing for the job.
mark following the last data record in the prime area.
The DCBLPDA field of the data control block (DCB) con- 035
tains the address of the last record in the prime area. Explanation: The error occurred during processing of a BISAM
03 An I/O error occurred while searching for the end-of-file OPEN macro instruction.
mark following the last data record in the independent The control program found that new records were to be added to the
overflow area. The DCBLIOV field of the data control data set, but the DCBMSWA and DCBSMSW fields of the data
block (DCB) contains the address of the last record in control block (DCB) indicated a virtual storage area too small to
the independent overflow area. contain one track from the prime area. The appropriate
04 The DCBMSHIA field of the data control block (DCB) ISAM-calculated value that you should specify in DCBSMSW is
contained an address that either specified a location returned in register 15. If this value is greater than 65535, you must
outside the boundaries of the virtual storage assigned to let ISAM obtain this work area for you.
the task or had a storage protection key other than that Source: DFSMSdfp
specified in the task control block (TCB).
Programmer Response: The error can be corrected by one of the
05 An I/O error occurred while reading the last prime data following:
block during open processing for resume load.
Provide a sufficient area by proper specification of the
All volumes of a multivolume ISAM data set were not DCBMSWA and DCBSMSW fields.
mounted.
For fixed-length records, provide no virtual storage area. Either
Source: DFSMSdfp do not specify the contents of the DCBMSWA and DCBSMSW
Programmer Response: Verify that the DCBLPDA, DCBLIOV, and fields or set the fields to zero. A virtual storage work area is
DCBMSHIA fields were not incorrectly specified or modified by the required only for variable-length records.
problem program. At the time of the abnormal end, register 4 con- After making corrections, reassemble the program and run the job
tains the address of the DCB. After making corrections, reassemble step again.
the program and run the job step again.
System Programmer Response: If the error recurs and the
System Programmer Response: If the error recurs and the program is not in error, look at the messages in the job log for more
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
information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the
problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the program listing for the job.
JCL and the program listing for the job.
036
034
Explanation: The error occurred during processing of a BISAM or
Explanation: The error occurred during processing of a BISAM QISAM OPEN macro instruction.
OPEN macro instruction. For variable length records, the control
program found that the address in DCBMSWA was not valid. Either The control program found that no space was allocated on a direct
the address is outside the boundaries of virtual storage or the pro- access device as the prime area for the data set:
tection key of that address is not the same as the protection key in In QISAM load mode, during data set generation, the SPACE
the TCB. parameter of the DD statement did not specify a primary quan-
The control program found that the fields of the data control block tity.
(DCB) indicated a virtual storage area too small to contain the The data set control block (DSCB) for the data set was incor-
highest level index for the data set. The size of the virtual storage rectly modified by the problem program.
area that should be reserved for the highest level index is placed in
Source: DFSMSdfp
the DCBNCRHI field of the data control block at OPEN exit time.
Programmer Response: In the first case, the data set should be
Source: DFSMSdfp
dumped sequentially and recreated using QISAM load mode. The job
Programmer Response: The error can be corrected by one of the should be restarted with a primary quantity specified in the SPACE
following: parameter of the DD statement. If the prime area is to span more
Specify a valid address in the MSWA operand of the DCB. than one volume, the number of volumes and the number of units
Verify that this field has not been incorrectly modified. required should be specified.
Provide a sufficient virtual storage area by proper specification In the second case, verify that the data set control block was not
of the DCBSMSI and DCBMSHIA fields. incorrectly modified by the problem program. After making cor-
rections, reassemble the program and run the job step again.
System Completion Codes SCC-21
037 03B
System Programmer Response: If the error recurs and the System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 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 information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job. JCL and the program listing for the job.
037 03A
Explanation: The error occurred during processing of a BISAM or Explanation: The error occurred during processing of a BISAM or
QISAM OPEN macro instruction. The control program found that the QISAM CLOSE macro instruction.
buffers supplied by the programmer were inadequate for the records
A format 2 data set control block (DSCB), read from a direct access
to be processed:
device into virtual storage, was updated from various fields of the
If the buffers were acquired by use of the BUILD macro instruc- data control block (DCB). When an attempt was made to write the
tion, either the BUFNO operand of the DCB macro instruction updated data set control block back to the direct access device, an
was not specified or the BUFL operand specified too small a I/O error occurred.
value.
When the ISAM interface is used to process a VSAM data set, this
If the buffers were acquired by use of the GETPOOL macro system completion code can be accompanied by message IEC251I.
instruction, the buffer length operand specified too small a value. If it is, refer to the explanation of message IEC251I for information
about the task that ended.
Source: DFSMSdfp
Source: DFSMSdfp
Programmer Response: Specify the buffers correctly. Then run the
job step again. Programmer Response: Determine the data set for which the
problem occurred and the nature of the problem.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more If this system completion code is accompanied by message IEC251I,
information. Search problem reporting data bases for a fix for the respond as indicated by message IEC251I.
problem. If no fix exists, contact the IBM Support Center. Provide the
At the time of the ABEND, register 4 points to the
JCL and the program listing for the job.
OPEN/CLOSE/END-OF-VOLUME work area. At X'64' in the work
area is the address of the job file control block (JFCB) whose con-
038 tents begin with the 44 character data set name. The address of the
Explanation: The error occurred during processing of an OPEN unit control block (UCB), which contains the device address for the
macro instruction for QISAM load mode. data set, is located and X'230' in the work area. The address of the
user's DCB which contains the address of the data event block
The control program found that the space on a direct access device (DEB) is located at X'238' in the work area. Correct the problem
that had been allocated for the index area was either exhausted or with the data set and rerun the job.
occupied more than one volume. The index for an ISAM data set
must reside on one volume. System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
Source: DFSMSdfp information. Search problem reporting data bases for a fix for the
Programmer Response: If a new data set is being created, the job problem. If no fix exists, contact the IBM Support Center. Provide the
must be restarted with larger space allocation specified in the JCL and the program listing for the job.
SPACE parameter of the DD statement.
If an old data set is being updated, the data set should be dumped 03B
sequentially, the old data set scratched, and the data set recreated Explanation: The error occurred during processing of an OPEN
from the sequential data set using QISAM load mode. The job macro instruction for an indexed sequential data set. If register 15
should be restarted with larger space allocation specified in the does not contain a hexadecimal reason code, then no records could
SPACE parameter of the DD statement. be processed because:
System Programmer Response: If the error recurs and the The block size (DCBBLKSI) is less than the logical record length
program is not in error, look at the messages in the job log for more (DCBLRECL).
information. Search problem reporting data bases for a fix for the
The block size (DCBBLKSI) is not a multiple of the logical record
problem. If no fix exists, contact the IBM Support Center. Provide the
length.
JCL and the program listing for the job.
If the error occurred during the processing of an ISAM OPEN exec-
039 utor, register 15 contains a hexadecimal reason code. No records
could be processed because:
Explanation: The error occurred in scanning a data set using
QISAM. Code Explanation
The end of the data set (EOD) was reached. The control program 01 The format-2 data set control block (DSCB) indicated
found that the DCBEODAD field of the data control block (DCB) did that 1/2 1/21/21/2MSG 8028 1/2 1/21/21/2MSG 8028 the
not contain an end-of-data-set exit routine address. data set had not been created (DS2STIND is not equal
to X'20'), or the format-2 DSCB indicated that the data
Source: DFSMSdfp control block (DCB) had not been closed after the data
Programmer Response: Make sure that the address of a routine set had been created.
to be given control when the end of the data set is reached is speci- 03 For variable length records, the relative key position
fied either in the EODAD operand of the DCB macro instruction or in (DCBRKP) field in the data control block (DCB) is less
the problem program before the end of the data set is reached. Then than four.
reassemble the program and run the job step again.
SCC-22 OS/390 V2R8.0 MVS System Codes
03C 03C
04 The relative key position (DCBRKP) plus the key length 05, 06 Correct the DCBKEYLE field. For an existing
(DCBKEYLE) is greater than the logical record length ISAM data set, omit the KEYLEN operand on the
(DCBLRECL). DCB macro instruction. This allows the data set
control block to supply the key length value.
05 The DCBKEYLE field of the data control block contained
zero. 07 Make sure that OUTPUT is specified as option 1
in the OPEN macro instruction.
06 The DCBKEYLE field of the data control block (DCB)
does not equal the value in the DS1KEYL field of the 09, 0A, 0B, 0C Make sure that the block size (BLKSIZE) and
format-1 DSCB. logical record length (LRECL) have been speci-
fied correctly on the data control block (DCB)
07 A QISAM data control block was being opened in prepa-
and that they are compatible.
ration for a PUT operation, but the OPEN macro instruc-
tion had not been issued for output. 0D Code DISP=OLD in the JCL for the QISAM data
control block that is being opened for a PUT
09 The logical record length in the data control block
operation.
(DCBLRECL) is zero.
0E, 0F Make sure that the record format has been spec-
0A The record format in the format-1 DSCB (DS1RECFM)
ified correctly. For an existing ISAM data set, list
indicates fixed blocked records, but the block size
the VTOC to determine the correct format of the
(DCBBLKSI) equals the logical record length
data set.
(DCBLRECL).
If register 15 does not contain a hexadecimal reason code, then
0B The block size (DCBBLKSI) differs from the format-1
make sure that:
DSCB block size (DS1BLKL).
1. the blocksize (BLKSIZE) and logical record length (LRECL) have
0C The logical record length (DCBLRECL) differs for the
been specified correctly on the data control block (DCB).
format-1 DSCB logical record length (DS1LRECL).
2. the BLKSIZE and LRECL are compatible.
0D QISAM data control block was being opened in prepara-
tion for a PUT operation and DISP=SHR was coded in In cases when the ISAM interface issued an ABEND, make sure that
the JCL. a valid mode of operation is specified in the MACRF operand of the
DCB macro. Additionally, make sure that the DCB is not being
0E The value for the record format (DCBRECFM) is zero.
opened for load mode while there are records in the data set.
0F The value for the record format (DCBRECFM) is not the
In all cases, run the job step again.
same as the record format value specified when the data
set was created (DS1RECFM). If message IEC161I accompanies this system completion code,
respond as indicated for message IEC161I.
Register 2 contains the address of the DCB for which the abend was
issued. System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
When the ISAM interface is used to process a VSAM data set, this
information. Search problem reporting data bases for a fix for the
system completion code can be accompanied by message IEC161I.
problem. If no fix exists, contact the IBM Support Center. Provide the
If it is, refer to message IEC161I for information about the task that
JCL and the program listing for the job.
ended. The ISAM interface of VSAM issues system completion code
03B for one of the following reasons:
03C
The access method service's and DCB values for LRECL,
KEYLE, RKP do not match. Explanation: A page, a segment, or an ASTE fault occurred. RSM
detected one of the following conditions.
DISP=OLD was specified and the DCB was opened for output
and the number of logical records is greater than zero (RELOAD Register 15 contains a hexadecimal reason code. In the reason
is implied). code, the bytes designated x contain diagnostic data that may be
requested by IBM.
An OPEN ACB error code 116 was returned for a request to
open a VSAM structure. Code Explanation
Source: DFSMSdfp xxxx08xx A program disabled for interrupts held the RSM lock, or
a higher lock, when a fault occurred.
Programmer Response: Take the following actions depending on
the reason code you received: xxxx0Dxx No central storage frames were available to resolve a
page fault when the unit of work was running disabled
Code Response
for interrupts.
01 Make sure that the data set has been properly
Source: Real storage manager (RSM)
created and that the creating task closes the
data control block. System Action: The system issues an abend to the current task.
03 If variable length records are used, make sure Programmer Response: For reason code X'xxxx0Dxx', run the
that the value of the DCBRKP field is not less job again. If the error recurs, contact the system programmer.
than four. System Programmer Response: Search problem reporting data
04 Make sure that the value of the DCBRKP field of bases for a fix for the problem. If no fix exists, contact the IBM
the data control block, when added to the value Support Center.
of in the DCBKEYLE field, does not exceed the
value in the DCBLRECL field.
System Completion Codes SCC-23
03D 043
03D 03F
Explanation: The error occurred during processing of (1) a QISAM Explanation: An error has been detected during checkpoint restart
or BISAM OPEN macro instruction or (2) a BDAM OPEN macro processing. This completion code is accompanied by message
instruction. IHJxxxI and the appropriate reason code.
One of the following occurred: Source: DFSMSdfp
In case (1), the DD statement did not specify an indexed System Action: The job is abnormally ended and a dump is
sequential organization (which can be specified by a DSORG=IS produced.
or DSORG=ISU subparameter of the DCB parameter).
Programmer Response: Respond as indicated in the accompa-
In case (1), if the data set resides on multiple volumes, either nying message.
the volume serial numbers in the SER subparameter of the
VOLUME parameter of the DD statement were not in proper 040
sequence, or not all volume serial numbers were specified. The
serial number of the volume containing the index must be listed Explanation: The error occurred during processing of an OPEN
first. The number of volumes and the number of units allocated macro for a telecommunications access method (TCAM) line group
must be the same, and all volumes must be mounted. data set.
In case (2), the volume serial numbers in the SER subparameter Source: Teleprocessing
of the VOLUME parameter of the DD statement were not in System Action: The error code is inserted into register 0 if the user
proper sequence. has coded an address in the EXLST= operand of the line group DCB
In case (2), the DCB DSORG=DA and the DD statement speci- macro. The exit routine may examine the code in register 0. If no
fies an indexed sequential data set name. user exit is specified, an indication of the error type may be found in
the explanation of console message IED008I.
This system completion code is sometimes accompanied by
message IEC156I. If so, refer to the explanation of message IEC156I Programmer Response: See the documentation of message
for complete information about the task that was ended and for an IED008I for the appropriate responses.
explanation of the return code (rc in the message text) in register 15.
041
Source: DFSMSdfp
Explanation: The error occurred during processing of an OPEN
Programmer Response: Correct the DCB parameter or SER sub-
macro for a telecommunications access method (TCAM) message
parameter, as necessary, and run the job step again.
queue data set.
If this system completion code is accompanied by message IEC156I,
Source: Teleprocessing
respond as indicated for the message.
System Action: The error code is inserted into register 0 if the user
System Programmer Response: If the error recurs and the
has coded an address in the EXLST= operand of the message
program is not in error, look at the messages in the job log for more
queue DCB macro instruction. The exit routine may examine the
information. Search problem reporting data bases for a fix for the
code in register 0. If no installation exit is specified, an indication of
problem. If no fix exists, contact the IBM Support Center. Provide the
the error type may be found in the explanation of console message
JCL and the program listing for the job.
IED008I.
03E Programmer Response: See the documentation of message
IED008I for the appropriate responses. If your system has the
Explanation: The error occurred during processing of a QISAM advanced communications function (ACF)/TCAM program product
OPEN macro instruction. The position of the last prime data record installed, see the appropriate ACF/TCAM messages book.
indicated that there is no room to add records with resume load.
The loading of an indexed sequential data set must be completed 043
during the initial OPEN/PUT/CLOSE cycle for that data set. An
Explanation: The error occurred during processing of an OPEN
indexed sequential data set that has been opened and closed for
macro for a telecommunications access method (TCAM) application
loading may be subsequently loaded if no data was created.
program data set.
Possibly, an attempt was made to add records with resume load to
Register 0 contains a hexadecimal reason code that explains the
the prime area of an ISAM data set that had no space available for
error:
additional records.
Code Explanation
Source: DFSMSdfp
01 An OPEN macro for a TCAM application program data set
Programmer Response: Either load the data set again with a
has been issued but there is no message control program
larger space allocation, or add records using BISAM.
(MCP) active in the system.
After making corrections, run the job step again.
02 The QNAME= parameter of a DD statement associated
System Programmer Response: If the error recurs and the with an application program is not the name of a process
program is not in error, look at the messages in the job log for more entry defined in the terminal table, or the QUEUES=
information. Search problem reporting data bases for a fix for the operand appeared in the TPROCESS macro instruction
problem. If no fix exists, contact the IBM Support Center. Provide the when an application program data control block (DCB) was
JCL and the program listing for the job. being opened for output only, or the QUEUES= operand
was not specified when an application program DCB was
being opened for input.
SCC-24 OS/390 V2R8.0 MVS System Codes
044 045
03 A process entry named by the QNAME= parameter of a 0A Either increase the number of environmental checkpoint
DD statement associated with an application program is records that can be written, or decrease the requested
currently being used by another application program. number of environmental checkpoint records.
04 Insufficient virtual storage was available in the MCP to
build internal control blocks, or the PGFN macro failed for 044
the process entry work area. Explanation: The error occurred during processing of the FE
05 Insufficient virtual storage was available in the application Common Write (COMWRITE) task. The COMWRITE task has been
program area to build internal control blocks. ended.
06 The application program attempted to open a secured The hexadecimal contents of register 3 indicates the nature of the
queue. The system operator rejected the request. error:
07 The application program is not an authorized program, but Register 3 Explanation
the user has either coded AUTHA=YES or taken YES as 01 Permanent I/O error on output device. Register 7 contains
the default value for AUTHA parameter on the TCAM user ID; register 8 contains address of failing DECB.
INTRO macro.
02 STAE routine failed. Register 15 contains the return code.
08 Page control block (PCB) error. OPEN was issued for a
TPROCESS entry while its PCB was in use by another 03 User parameter list is incorrect, and output required was
task. specified. Register 7 contains the address of the param-
eter list saved in COMWRITE. Register 11 contains the
09 A TCAM job name was not found with the same name as address of the error message.
the TCAM job name that was qualified on the DD state-
ment as input to IGG01946 (DCB OPEN). 05 The output DCB failed to open.
0A The number of environmental checkpoint records that can 06 For one of the traces specified, the size of one half of the
be written is less than the number of environmental check- trace table is larger than the maximum block size specified
point records requested. for the trace data set.
Source: Teleprocessing Source: DFSMSdfp
System Action: If an ABEND installation exit is provided in the Programmer Response: Response depends upon the hexadecimal
EXLST= operand of the DCB macro for the data set, the system contents of register 3:
gives control to the routine. If it returns, or if no ABEND installation Register 3 Response
exit is provided, the system abnormally ends the task. Message
01 Check the status of the recording medium. If it is valid,
IED015I may accompany this system completion code.
call your hardware support personnel.
Programmer Response: No action is required if an ABEND instal-
02 Call your hardware support personnel.
lation exit has been provided in the EXLST= operand of the DCB
macro for the application program data set. 03 Check the parameter list.
The contents of register 0 indicate the action to be taken: 05 Missing DD statement. Include the DD statement and
rerun the job.
Register 0 Response
06 Ensure that the size of one half of the trace table does
01 Ensure that an MCP is active before attempting to start
not exceed the maximum block size specified for the
an application program.
trace data set.
02 Recode the QNAME= parameter specifying the name of
a valid process entry. 045
03 Recode the QNAME= parameter specifying the name of Explanation: The error occurred during processing of a telecommu-
a valid process entry. nications access method (TCAM) message control program (MCP).
04 Specify a larger region or partition size on the JOB The MCP ends.
statement for the MCP, or restart the system specifying The low-order byte of register 15 contains a hexadecimal reason
a larger system queue space. code that explains the error:
05 Specify a larger partition size on the JOB statement for Code Explanation
the application program.
01 I/O has been requested on a nonreusable disk record
06 Recode the SECURE=YES operand associated with the that is beyond the capacity of the data set. The nonreus-
queue, or instruct the system operator to allow the able disk data set cannot be wrapped.
queue to be opened.
02 Logical read error caused by the reusable disk receiving
07 Link edit the application program as an authorized a heavy burst of new traffic. This traffic causes unsent
program into an authorized library, or specify messages to be overlaid before being copied to the
AUTHA=NO on the TCAM INTRO macro. alternate destination queue.
08 Open all TPROCESS entries for the PCB in the same 03 Logical read error while trying to fetch a message for
application program. transmission to a terminal.
09 Either start the TCAM with the jobname wanted or 04 The copy subtask needed to copy messages from one
change the jobname on the QNAME=procname.jobname data set to another has not been loaded by the disk
operand and restart the application program. OPEN. A multiple-route or distribution list message has
been enqueued to go to dissimilar message queue
types. The copy subtask is needed to put the message
System Completion Codes SCC-25
046 048
on the queue. Caused by failure to open successfully a
047
disk message queue data control block (DCB).
Explanation: An unauthorized program issued a restricted Super-
05 I/O has been requested on an unopened disk message
visor Call (SVC) instruction:
queue data set.
An authorized program:
06 FEATURE=(,,NOTIMER) has been specified on the
INTRO macro, but a function requiring the system timer runs in supervisor state
has been called. Holds PSW key 0-7
07 A message longer than the reusable disk data set has Resides in an APF-authorized library
been entered.
Source: Supervisor control
08 A disk read error occurred. It was a hardware error, not
a logical read error. System Action: The system writes a logrec data set error record.
09 Either insufficient space was allocated for the checkpoint Operator Response: If the system programmer asks for an SVC
data set, or a read error occurred when attempting to dump, set the following SLIP trap:
read records from the checkpoint data set during a SLIP SET,COMP=ð47,ACTION=SVCD,END
restart.
System Programmer Response: Do the following:
0A Either the checkpoint data set is too small, or the
1. Ask the operator to set a SLIP trap to obtain an SVC dump.
number of checkpoint records specified in the INTRO
macro is too large. 2. In the system trace, look for the SVC D or *SVCE D entry for
abend X'047'.
Source: Teleprocessing
3. Look for an SVC entry preceding the entry found in step 2. The
System Action: The system abnormally ends. The system writes
SVC entry should be for the same TCB and have the same
an error to the logrec data set.
ASID as the entry found in step 2. The PSW for this SVC entry
Programmer Response: Except for return code X'08', this is a contains the address of the unauthorized program that issued a
probable user error. To determine the action for a specific reason restricted SVC.
code, follow these procedures based on the reason code in register
4. Use the PSW found in step 3 to identify the unauthorized
15:
module that issued the restricted SVC.
Code Response
For an installation-provided module, continue diagnosis with
01 Either specify a larger data set or request that close the module.
down occur at an earlier point.
For an IBM module whose module prefix is IED or IKJ, the
02,03,07 Specify a larger data set or one that occupies more than module is most likely a TCAM module. Specify AUTHA=NO
one extent. on the INTRO macro in the TCAM MCP program and run
04,05 Before issuing the OPEN macro for the lines, test for the job again. If the problem recurs, search problem
successful open of the message queue data set. reporting data bases for a fix for the problem. If no fix
exists, contact the TCAM group at the IBM Support Center.
06 Specify FEATURE=(,,TIMER). Assemble and run the Provide the SVC dump and the logrec data set error record.
MCP again.
For an IBM module that is not part of TCAM, search
09 The message issued to the operator just before ABEND problem reporting data bases for a fix for the problem. If no
describes the cause of failure, and the message fix exists, contact the component group associated with this
description provides a response. module at the IBM Support Center. Provide the SVC dump
0A Either allocate more space for the checkpoint data set, and the logrec data set error record.
or specify fewer checkpoint records in the INTRO macro.
System Programmer Response: For return code X'08', look at 048
the messages in the job log for more information. Contact hardware Explanation: A subsystem address space supported by advanced
support. Provide the logrec data set error record and the SYSOUT communications function/telecommunications access method
output for the job. For all other return codes, search problem (ACF/TCAM) had an error condition. An ACF/TCAM subsystem has
reporting data bases for a fix for the problem. If no fix exists, contact determined that recovery could not occur. The subsystem abnormally
the IBM Support Center. ends. Register 0 contains one of the following failure codes:
Code Explanation
046
001 The request parameter list (RPL) address was incorrect
Explanation: The telecommunications access method (TCAM) when the subsystem interface was not running with
message control program (MCP) has ended but an application authorized path.
program data set is still open. The application program data set is
scheduled to be ended with a system completion code of X'046'. 002 An abnormal end occurred before the subsystem was
notified of function recovery routines (FRR) recovery.
Source: Teleprocessing
Source: Teleprocessing
System Action: The application program abnormally ends.
System Action: Restart the subsystem.
Programmer Response: See the programmer response for the
system completion code provided with the abnormal end of the MCP. Programmer Response: Print the SVC dump, which was stored in
the SYS1.DUMP data set.
System Programmer Response: Format the SVC dump with the
interactive problem control system (IPCS). Search problem reporting
SCC-26 OS/390 V2R8.0 MVS System Codes
049 04F
data bases for a fix for the problem. If no fix exists, contact the IBM for the problem. If no fix exists, contact the IBM Support Center.
Support Center. Provide the ABEND dump and the logrec data set record.
049 04C
Explanation: A subsystem address space or telecommunications Explanation: A user invoked the TMP (terminal monitor program)
access method (TCAM) appendage supported by advanced commu- and the TMP detaches a program that completed with a nonzero
nications function (ACF)/TCAM had an error condition. The FRR was completion code. The nonzero completion code is in register 15.
unable to recover the subsystem.
Source: Time Sharing Option Extensions (TSO/E)
Source: Teleprocessing
System Action: The system does not change the user return code.
System Action: A logrec data set entry has been created that
explains why recovery could not occur. An SVC dump was written to 04E
SYS1.DUMP.
Explanation: When the system detects an error in internal IBM
Operator Response: Restart the system. DATABASE 2 (DB2) processing, it will abnormally end a connected
Programmer Response: Print the dump and logrec entry. user task (TCB) or one of its own internal tasks. For information
about the reason codes associated with this abend code, see DB2
System Programmer Response: Format the SVC dump with the
Messages and Codes.
interactive problem control system (IPCS). Search problem reporting
data bases for a fix for the problem. If no fix exists, contact the IBM Source: DFSMSdfp
Support Center. System Action: The system abnormally ends the connected user
task or the DB2 internal task.
04A
Programmer Response: Check register 15 of the SDWA section
Explanation: An MVSSERV program made an incorrect request for ‘General Purpose Registers at Time of Error’, and locate the accom-
data management services. A reason code provides further panying reason code. In addition, check the information displayed at
information: the user's terminal, and in the corresponding logrec data set entry.
Code Explanation System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
004 The program passed an incorrect operation code in a
information. Search problem reporting data bases for a fix for the
request for a data management service.
problem. If no fix exists, contact the IBM Support Center. Provide the
008 The program made an unsupported request for the data SYSOUT output for the job and the logrec data set error record.
management GET macro.
012 The program made an unsupported request for the data 04F
management PUT macro.
Explanation: To avoid data integrity problems, the subsystem
Source: Time Sharing Option Extensions (TSO/E) abnormally ends; one or more 04E system completion codes will
System Action: The MVSSERV program ends abnormally. The usually precede the end. During DATABASE 2 (DB2) abend, a user
system writes an ABEND dump. task with an active DB2 connection can be abended with a X'04F'
system completion code; in rare instances, the entire connected
System Programmer Response: If the problem recurs and if the address will be abended (MEMTERM). However, if the subsystem
program is not in error, search problem reporting data bases for a fix ends an address space after numerous cancel attempts, this is not a
for the problem. If no fix exists, contact the IBM Support Center. DB2 internal error.
Provide the ABEND dump.
Source: DFSMSdfp
04B System Action: The subsystem abnormally ends DB2.
Explanation: An incorrect operation code was passed to a TSO Operator Response: Message DSNV086E should appear on your
linkage assist routine (LAR). Register 15 contains a hexadecimal console screen. First, copy this message and the accompanying sub-
code that indicates the reason for the termination. system end reason code. Second, notify the system programmer.
Code Explanation Programmer Response: If the subsystem abnormally ends DB2,
then record the subsystem end reason code that is displayed in
004 The LAR for the terminal monitor program received an
message DSNV086E. In addition, you should be aware of the fol-
incorrect function number.
lowing situations.
008 The service routine's LAR was invoked an incorrect
1. If you received any X'04E' system completion codes prior to
service routine entry point.
this subsystem end, perform the following actions. Check reg-
Source: Time Sharing Option Extensions (TSO/E) ister 15 of the SDWA section ‘General Purpose Registers at
Time of Error’, and locate the accompanying reason code. In
Source: Time Sharing Option Extensions (TSO/E)
addition, check the information displayed at the user's terminal,
System Action: TSO does not perform the requested service. The and in the corresponding logrec data set entry.
system writes an ABEND dump. The system writes a logrec data
2. If you did not receive any X'04E' system completion codes
set error record.
prior to the subsystem end, you will need an SVC dump, which
Programmer Response: Determine the calling routine and correct is entitled ‘DB2 SUBSYSTEM TERMINATION REQUESTED -
the operation code. REASON=xxxxxxxx.’ The reason code in the message and the
System Programmer Response: If the problem recurs and if the one found in the MVS operator message will be the same.
program is not in error, search problem reporting data bases for a fix System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
System Completion Codes SCC-27
051 052
information. Search problem reporting data bases for a fix for the 0202 The format number field in the parameter list is not valid.
problem. If no fix exists, contact the IBM Support Center. Provide the Register 5 contains the first word of the parameter list.
SYSOUT output for the job and the logrec data set error record.
0203 The request count in the linkage index (LX) list is not
valid. Register 5 contains the first word of the parameter
051 list.
Explanation: An MVSSERV program made an incorrect request for 0211 A linkage index (LX) is incorrect. Register 5 contains the
data management services. A reason code provides further incorrect LX.
information:
0212 A linkage index (LX) is not owned by the home address
Code Explanation space. Register 5 contains the incorrect LX.
004 The program passed an incorrect operation code in a 0213 A linkage index (LX) is incorrect because it is a system
request for a data management service. LX. Register 5 contains the linkage index.
Source: Time Sharing Option Extensions (TSO/E) 0214 A linkage index (LX) has one or more entry tables con-
System Action: The MVSSERV program ends. The system writes nected and the LXFRE macro did not specify
an ABEND dump. FORCE=YES.
System Programmer Response: If the problem recurs and if the 0215 A linkage index (LX) appeared more than once in the LX
program is not in error, search problem reporting data bases for a fix list.
for the problem. If no fix exists, contact the IBM Support Center. 03yy The program issued an ETCRE macro. Register 2 con-
Provide the ABEND dump. tains the index of the entry in which the error was found.
0301 A reserved field is not equal to 0 in the header of the
052 entry table description (ETD) specified in the ENTRIES
Explanation: A program incorrectly issued a macro to request proc- parameter.
essing by Program Call/authorization (PC/AUTH) service routines. 0302 The format number field in the entry table description
Register 15 contains a hexadecimal reason code in the form xxyy, (ETD) is incorrect.
where x identifies the macro that was issued, and yy identifies the 0303 The request count in the ETDNUM field is not valid.
error. See the system programmer response for an explanation of
these reason codes. 0304 The caller passed a non-zero value in register 1.
Source: Program Call/authorization (PC/AUTH) 0311 A reserved field is not equal to 0 in one of the 20-byte
description elements in the entry table description (ETD).
System Action: The system abends the program that issued the Register 2 contains the entry index associated with the
macro. The system writes an ABEND dump. description element.
System Programmer Response: Obtain the ABEND dump and 0312 The program identified in one of the 20-byte description
find the reason code associated with the abend. elements could not be found. Register 2 contains the
In the system trace table, look for the last *SVCE D entry. The PC entry index associated with the description element.
entry preceding it gives the address in the program of the failing 0313 The entry indexes are not in ascending order. Register 2
macro. contains the entry index that was not in ascending order.
If the macro was issued by an installation-provided program, correct 0314 A job step attempted to issue an ETCRE macro, but a
the program. If the macro was issued by a system component, or if prior job step owned space-switch entry tables. (Subse-
the problem persists, search problem reporting data bases for a fix. If quent job steps are not permitted to issue PC/AUTH
no fix exists, contact the IBM Support Center. Provide the ABEND macros.)
dump.
0315 Reserved fields in the extended portion of the entry table
The reason codes in register 15 are: description (ETD) are non-zero.
Code Explanation 0316 Options that are valid only for a stacking Program Call
01yy The program issued an LXRES macro. (PC) were specified for a basic PC.
0101 A reserved field in the parameter list is not 0. Register 5 0317 An incorrect combination of ETDPKMC and ETDPKC
contains the first word of the parameter list. was specified. On the ETDEF macro, either:
0102 The format number field in the parameter list is not valid. PKM=REPLACE was specified without EK.
Register 5 contains the first word of the parameter list. EK value was not one of the keys specified in the
EKM list.
0103 The request count in the linkage index (LX) list is not
valid. Register 5 contains the first word of the parameter 0318 The extended authorization index (EAX) is not in the
list. range of valid authorization indexes (AXs).
0104 A job step attempted to issue the LXRES macro, but a 0319 The extended authorization index (EAX) specified was
prior job step owned space-switch entry tables. (Subse- not reserved by the home address space.
quent job steps are not permitted to issue PC/AUTH 0320 The name of the associated recovery routine (ARR)
macros.) could not be found.
02yy The program issued an LXFRE macro. 0321 An entry table descriptor (ETD) requested that
0201 A reserved field in the parameter list is not 0. Register 5 CANCEL/DETACH processing be deferred while the
contains the first word of the parameter list. associated recovery routine (ARR) is running. PC/AUTH
is not authorized to defer this processing because it
might not run in supervisor state or key 0.
SCC-28 OS/390 V2R8.0 MVS System Codes
052 052
0322 An entry table descriptor (ETD) requested that 0615 The LXFRE macro passed an incorrect address space
CANCEL/DETACH processing or asynchronous exits be identifier (ASID) to the ETDIS macro. Register 2 con-
deferred while the ARR is running, but no ARR was tains the incorrect ASID.
specified.
07yy The program issued an AXRES macro.
0323 The index specified in the entry table description (ETD)
0703 The request count is not valid. Register 4 contains the
is greater than the maximum index allowed.
request count.
04yy The program issued an ETDES macro.
0704 The caller passed a non-zero value in register 1.
0401 A reserved input field in the parameter list is not 0.
0705 A job step attempted to issue an AXRES macro, but a
0402 The format number field in the parameter list is not valid. prior job step owned space-switch entry tables. (Subse-
quent job steps are not permitted to issue PC/AUTH
0411 The specified token is not valid.
macros.)
0412 The program specified a token for a system entry table
08yy A program issued an AXFRE macro.
but did not specify PURGE=YES.
0803 The request count is not valid. Register 4 contains the
0413 The specified token is for an entry table that the home
request count.
address space does not own.
0804 The caller passed a non-zero value in register 1.
0414 The program specified a token for an entry table that is
in use, but the program did not specify PURGE=YES. 0813 An authorization index (AX) is not reserved by the home
address space. Register 4 contains the AX.
05yy The program issued an ETCON macro.
0814 An authorization index (AX) is still in use. Register 4
0501 A reserved input field is not 0.
contains the address of the address space control block
0502 The format number field is not valid. (ASCB) using the AX. Register 5 contains the AX.
0503 The token list count or the linkage index (LX) list count is 0817 An authorization index (AX) appeared more than once in
not valid. the authorization index list. Register 4 contains the dupli-
0511 The token list count and the linkage index (LX) list count cate AX.
are not equal. 0818 An authorization index (AX) may still be in use as an
0512 A specified linkage index (LX) is already in use. Register extended authorization index (EAX).
2 contains the incorrect LX. 0823 An authorization index (AX) equal to 0 or 1 appears in
0513 A specified linkage index (LX) is not reserved. Register 2 the authorization index list. An AX of 0 or 1 cannot be
contains the incorrect LX. freed. Register 4 contains the AX.
0514 A specified token is incorrect. 09yy A program issued an AXEXT macro.
0515 A specified token is for an entry table that is already 0901 A reserved input field is not 0.
connected to the home address space's linkage table. 0904 The caller passed a non-zero value in register 1.
Register 2 contains the incorrect token.
0918 The address space identifier (ASID) passed as input is
0516 A specified token is for an entry table that is not author- not for an active address space. Register 4 contains the
ized for connection. Register 2 contains the incorrect ASID.
token.
0Ayy The program issued an AXSET macro.
0517 An entry table and the corresponding linkage index are
0A01 A reserved input field is not 0.
not owned by the same address space. Register 2 con-
tains the LX. 0A04 The caller passed a non-zero value in register 1.
0519 A token appeared more than once in the token list. Reg- 0A19 The authorization index (AX) is not within the authori-
ister 2 contains the token. zation index allocation table (AXAT). Register 4 contains
the authorization index.
051A A linkage index (LX) appeared more than once in the LX
list. 0A20 The authorization index (AX) is not reserved. Register 4
contains the authorization index.
06yy The program issued an ETDIS macro.
0A21 The home address space has one or more connected
0603 The token count is not valid. Register 2 contains the
SASN=OLD space switch entry tables that could cause
incorrect count.
an address space switch.
0604 The caller passed a non-zero value in register 1. Reg-
0A23 The authorization index (AX) for the master address
ister 2 contains the value.
space must be 1. Register 4 contains the requested AX
0611 A specified token is incorrect. Register 2 contains the value, which is not valid because it is not 1.
token.
0Byy The program issued an ATSET macro.
0612 The specified token is for a system entry table. Register
0B01 A reserved input field is not 0.
2 contains the token.
0B04 The caller passed a non-zero value in register 1.
0613 A specified token is for an entry table that is not con-
nected. Register 2 contains the token. 0B19 The authorization index (AX) specified is not within the
authorization index allocation table (AXAT). The second
0614 A token appears more than once in the token list. Reg-
halfword of register 4 contains the AX value. The content
ister 2 contains the token.
of the first halfword of register 4 is undefined and unpre-
dictable.
System Completion Codes SCC-29
053 053
0B20 The authorization index (AX) specified is not reserved. Support Center. Provide the SVC dump, including the system trace
Register 4 contains the AX. table, and the logrec data set error record.
0B22 The specified authorization index (AX) is for a predefined The reason codes in Register 15 are:
authorization table entry. Register 4 contains the AX.
Code Explanation
11yy The program issued a PCLINK macro with the STACK
01yy The program issued an LXRES macro.
parameter.
0101 PC/AUTH requested dynamic work area storage, but the
1112 The program held one or more locks that caused an
request failed. Register 5 contains the return code from
internal error in PCLINK processing. If SAVE=NO was
the request.
specified, register 5 contains the caller's return code. If
SAVE=YES was specified, register 8 contains the call- 0105 PC/AUTH requested storage for a new linkage index
er's return code. allocation table (LXAT) in the pageable storage of
(PC/AUTH) address space. The request failed. Register
12yy The program issued a PCLINK macro with the
5 contains the return code from the request.
UNSTACK parameter.
0109 PC/AUTH requested that an old linkage index allocation
1211 The macro included the UNSTACK,THRU or the
table (LXAT) in the PC/AUTH address space's pageable
UNSTACK,TO parameter, but the current PCLINK stack
storage be freed. The request failed. Register 5 con-
element chain was empty.
tains the return code from the request.
1212 The specified token was for a PCLINK stack element
010A PC/AUTH requested that a dynamic work area be freed,
(STKE) that is not on the PCLINK stack element chain.
but the request failed. Register 5 contains the return
Register 2 contains the token.
code from the request.
13yy The program issued a PCLINK macro with the
0111 PC/AUTH could not reserve one or more linkage indexes
EXTRACT parameter.
(LX) because the maximum number of LXs the system
1313 The specified token was for a PCLINK stack element supports would be exceeded. Register 5 contains the
(STKE) that is not the most recently stacked STKE. number of LXs that are currently unreserved.
Register 2 contains the token of the current element. 0112 The program tried to reserve more system linkage
indexes (system LXs) then were available. The total
This problem can be caused by an application program
number of system linkage indexes is the sum of the
or the system.
number of LXs in the system function table and the
1314 The specified token is not valid. Register 2 contains the value of the NSYSLX parameter of the IEASYSxx
incorrect token. parmlib member. The default value for NSYSLX is 165.
0197 An unexpected error occurred. Another abend occurred
053 while PC/AUTH was processing. The system converted
Explanation: A program requested processing by Program the abend to X'053'. Look in the SDWA variable
Call/authorization (PC/AUTH) service or a program call linkage recording area (SDWAVRA) for the original abend and
service. An error prevented PC/AUTH from processing the macro reason codes and continue diagnosis with that code.
normally. The system records the registers in field SDWAGRSV in 0198 PC/AUTH previously failed and cannot process requests.
the system diagnostic work area (SDWA).
0199 The acronym at the beginning of a PC/AUTH control
Register 15 contains a hexadecimal reason code in the form xxyy, block is incorrect. Register 5 contains the expected
where xx identifies the macro that was issued and yy identifies the acronym.
error. See the system programmer response for an explanation of
the reason codes. 02yy The program issued an LXFRE macro.
Source: Program Call/authorization (PC/AUTH) 0201 PC/AUTH requested storage for a dynamic work area,
but the request failed. Register 5 contains the return
System Action: The system abends the program that issued the code from the request.
macro, unless PC/AUTH requests a retry. The system writes an SVC
dump and a logrec data set error record. 0205 PC/AUTH requested storage for a new force disconnect
queue block (FDQB) in the program PC/AUTH address
System Programmer Response: Look at the explanation of the space's pageable storage. The request failed. Register
reason code. If you receive one of the reason codes below, do the 5 contains the return code from the request.
following:
0209 PC/AUTH requested that a force disconnect queue block
For reason code X'xx97': Look in the SDWA variable recording (FDQB) in the PC/AUTH address space's pageable
area (SDWAVRA) for the original abend and reason code and storage be freed. The request failed. Register 5 con-
continue diagnosis with that abend. tains the return code from the request.
For reason code X'xx98': Look at message IEA139E, which 020A PC/AUTH requested that a dynamic work area be freed,
PC/AUTH issued at the time of the original failure. but the request failed. Register 5 contains the return
For reason code X'xx99': Look in the SDWA variable recording code from the request.
area (SDWAVRA) for a PC/AUTH control block that is not valid. 0211 PC/AUTH was building the force disconnect queue
For reason code X'0112': Change the application program to (FDQ) to process a FORCE request. The service found
use fewer linkage indexes (LXs) or change the limit of system more than one connection description (ETIXCD) with the
LXs with the NSYSLX parameter in the IEASYSxx parmlib same address space identifier(ASID)/linkage index (LX)
member. values while searching the entry table information block
(ETIB) chain.
If you cannot correct the problem, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
SCC-30 OS/390 V2R8.0 MVS System Codes
053 053
0297 An unexpected error occurred. Another abend occurred 0409 PC/AUTH requested that storage in the PC/AUTH
while PC/AUTH was processing. The system converted address space's pageable storage be freed. The request
this abend to X'053'. Look in the SDWA variable failed. Register 2 contains the return code from the
recording area (SDWAVRA) for the original abend and request.
reason codes and continue diagnosis with that code.
040A PC/AUTH requested that a dynamic work area be freed,
0298 PC/AUTH previously failed and cannot process requests. but the request failed. Register 2 contains the return
code from the request.
0299 The acronym at the beginning of a PC/AUTH control
block is incorrect. Register 5 contains the expected 0497 An unexpected error occurred. Another abend occurred
acronym. while PC/AUTH was processing and the system con-
verted the abend to X'053'. Look in the SDWA variable
03yy The program issued an ETCRE macro.
recording area (SDWAVRA) for the original abend and
0301 PC/AUTH requested storage for a dynamic work area, reason codes and continue diagnosis with that code.
but the request failed. Register 2 contains the return
0498 PC/AUTH previously failed and cannot process requests.
code from the request.
0499 The acronym at the beginning of a PC/AUTH control
0302 PC/AUTH requested storage in the system queue area
block is incorrect. Register 2 contains the expected
(SQA), but the request failed. Register 2 contains the
acronym.
return code from the request.
05yy The program issued an ETCON macro.
0303 PC/AUTH requested storage in the PC/AUTH address
space's local system queue area (LSQA). The request 0501 PC/AUTH requested storage for a dynamic work area,
failed. Register 2 contains the return code from the but the request failed. Register 2 contains the return
request. code from the request.
0305 PC/AUTH requested storage in the PC/AUTH address 0503 PC/AUTH requested storage in the PC/AUTH address
space's pageable storage. the request failed. Register 2 space's local system queue area (LSQA). The request
contains the return code from the request. failed. Register 2 contains the return code from the
request..
0306 PC/AUTH requested that storage in the system queue
area (SQA) be freed, but the request failed. Register 2 0505 PC/AUTH requested storage in the PC/AUTH address
contains the return code from the request. space's pageable storage. the request failed. Register 2
contains the return code from the request.
0307 PC/AUTH requested that storage in the PC/AUTH
address space's local system queue area (LSQA) be 0507 PC/AUTH requested that storage in the PC/AUTH
freed. The request failed. Register 2 contains the return address space's local system queue area (LSQA) be
code from the request. freed. The request failed. Register 2 contains the return
code from the request.
0309 PC/AUTH requested that storage in the PC/AUTH
address space's pageable storage area be freed. The 050A PC/AUTH requested that a dynamic work area be freed,
request failed. Register 2 contains the return code from but the request failed. Register 2 contains the return
the request. code from the request.
030A PC/AUTH requested that a dynamic work area be freed, 0597 An unexpected error occurred. Another abend occurred
but the request failed. Register 2 contains the return while PC/AUTH was processing and the system con-
code from the request. verted the abend to X'053'. Look in the SDWA variable
recording area (SDWAVRA) for the original abend and
0397 An unexpected error occurred. Another abend occurred
reason codes and continue diagnosis with that code.
while PC/AUTH was processing and the system con-
verted the abend to X'053'. Look in the SDWA variable 0598 PC/AUTH previously failed and cannot process requests.
recording area (SDWAVRA) for the original abend and
0599 The acronym at the beginning of a PC/AUTH control
reason codes and continue diagnosis with that code.
block is incorrect. Register 2 contains the expected
0398 PC/AUTH previously failed and cannot process requests. acronym.
0399 The acronym at the beginning of a PC/AUTH control 06yy The program issued an ETDIS macro.
block is incorrect. Register 2 contains the expected
0601 PC/AUTH requested storage for a dynamic work area,
acronym.
but the request failed. Register 2 contains the return
04yy The program issued an ETDES macro. code from the request.
0401 PC/AUTH requested storage for a dynamic work area, 0609 PC/AUTH requested that storage in the PC/AUTH
but the request failed. Register 2 contains the return address space's pageable storage area be freed. The
code from the request. request failed. Register 2 contains the return code from
the request.
0406 PC/AUTH requested that storage in the system queue
area (SQA) be freed, but the request failed. Register 2 060A PC/AUTH requested that a dynamic work area be freed,
contains the return code from the request. but the request failed. Register 2 contains the return
code from the request.
0407 PC/AUTH requested that storage in the PC/AUTH
address space's local system queue area (LSQA) be 0697 An unexpected error occurred. Another abend occurred
freed. The request failed. Register 2 contains the return while PC/AUTH was processing and the system con-
code from the request. verted the abend to X'053'. Look in the SDWA variable
recording area (SDWAVRA) for the original abend and
reason codes and continue diagnosis with that code.
System Completion Codes SCC-31
053 053
0698 PC/AUTH previously failed and cannot process requests. recording area (SDWAVRA) for the original abend and
reason codes and continue diagnosis with that code.
0699 The acronym at the beginning of a PC/AUTH control
block is incorrect. Register 2 contains the expected 0998 PC/AUTH previously failed and cannot process requests.
acronym.
0999 The acronym at the beginning of a PC/AUTH control
07yy The program issued an AXRES macro. block is incorrect. Register 4 contains the expected
acronym.
0701 PC/AUTH requested storage for a dynamic work area,
but the request failed. Register 4 contains the return 0Ayy The program issued an AXSET macro.
code from the request.
0A01 PC/AUTH requested storage for a dynamic work area,
0705 PC/AUTH requested storage in the PC/AUTH address but the request failed. Register 4 contains the return
space's pageable storage. the request failed. Register 4 code from the request.
contains the return code from the request.
0A0A PC/AUTH requested that a dynamic work area be freed,
0709 PC/AUTH requested that storage in the PC/AUTH but the request failed. Register 4 contains the return
address space's pageable storage area be freed. The code from the request.
request failed. Register 4 contains the return code from
0A30 An unexpected error occurred before the service set the
the request.
authorization index (AX) of the home address space.
070A PC/AUTH requested that a dynamic work area be freed,
0A31 An unexpected error occurred after the service set the
but the request failed. Register 4 contains the return
authorization index (AX) of the home address space, but
code from the request.
before the bind break routine could break all binds to
0712 PC/AUTH cannot satisfy the request because the author- other address spaces.
ization index (AX) count would cause the total number of
0A32 An unexpected error occurred after the service set the
AXs to exceed the maximum number that the system
authorization index (AX) of the home address space and
supports. Register 4 contains the AX count for the
the bind break routine broke all binds to other address
request.
spaces.
0797 An unexpected error occurred. Another abend occurred
0A97 An unexpected error occurred. Another abend occurred
while PC/AUTH was processing and the system con-
while PC/AUTH was processing and the system con-
verted the abend to X'053'. Look in the SDWA variable
verted the abend to X'053'. Look in the SDWA variable
recording area (SDWAVRA) for the original abend and
recording area (SDWAVRA) for the original abend and
reason codes and continue diagnosis with that code.
reason codes and continue diagnosis with that code.
0798 PC/AUTH previously failed and cannot process requests.
0A98 PC/AUTH previously failed and cannot process requests.
0799 The acronym at the beginning of a PC/AUTH control
0A99 The acronym at the beginning of program PC/AUTH
block is incorrect. Register 4 contains the expected
control block is incorrect. Register 4 contains the
acronym.
expected acronym.
08yy The program issued an AXFRE macro.
0Byy The program issued an ATSET macro.
0801 PC/AUTH requested storage for a dynamic work area,
0B01 PC/AUTH requested storage for a dynamic work area,
but the request failed. Register 4 contains the return
but the request failed. Register 4 contains the return
code from the request.
code from the request.
080A PC/AUTH requested that a dynamic work area be freed,
0B03 PC/AUTH requested storage in the PC/AUTH address
but the request failed. Register 4 contains the return
space's local system queue area (LSQA). The request
code from the request.
failed. Register 4 contains the return code from the
0897 An unexpected error occurred. Another abend occurred request.
while PC/AUTH was processing and the system con-
0B07 PC/AUTH requested that storage in the PC/AUTH
verted the abend to X'053'. Look in the SDWA variable
address space's local system queue area (LSQA) be
recording area (SDWAVRA) for the original abend and
freed. The request failed. Register 4 contains the return
reason codes and continue diagnosis with that code.
code from the request.
0898 PC/AUTH previously failed and cannot process requests.
0B0A PC/AUTH requested that a dynamic work area be freed,
0899 The acronym at the beginning of program PC/AUTH but the request failed. Register 4 contains the return
control block is incorrect. Register 4 contains the code from the request.
expected acronym.
0B30 An unexpected error occurred before the service set the
09yy The program issued an AXEXT macro. authorization bits in the authorization table (AT) of the
home address space.
0901 PC/AUTH requested storage for a dynamic work area,
but the request failed. Register 4 contains the return 0B31 An unexpected error occurred after the service set the
code from the request. authorization bits in the authorization table (AT) of the
home address space, but before the bind break routine
090A PC/AUTH requested that a dynamic work area be freed,
broke all binds to other address spaces.
but the request failed. Register 4 contains the return
code from the request. 0B32 An unexpected error occurred after the service set the
authorization bits in the authorization table (AT) of the
0997 An unexpected error occurred. Another abend occurred
home address space and the bind break routine broke
while PC/AUTH was processing and the system con-
all binds to other address spaces.
verted the abend to X'053'. Look in the SDWA variable
SCC-32 OS/390 V2R8.0 MVS System Codes
054 054
0B97 An unexpected error occurred. Another abend occurred 12yy The program issued a PCLINK macro with the
while PC/AUTH was processing and the system con- UNSTACK parameter.
verted the abend to X'053'. Look in the SDWA variable
1211 On the stack element queue (STKE), one of the pointers
recording area (SDWAVRA) for the original abend and
to the next STKE is incorrect. Register 2 contains the
reason codes and continue diagnosis with that code.
incorrect pointer.
0B98 PC/AUTH previously failed and cannot process requests.
1212 On the stack element queue, one of the fields containing
0B99 The acronym at the beginning of a PC/AUTH control the address space identifier (ASID) of the next stack
block is incorrect. Register 4 contains the expected element (STKE) is incorrect. Register 2 contains the
acronym. incorrect ASID.
0Cyy PC/AUTH resource manager detected an error. 1297 The cause of the error is unknown. Look in the SDWA
variable recording area (SDWAVRA) for the original
0C01 The resource manager requested storage for a dynamic
abend and reason codes issued by the PCLINK macro.
work area, but the request failed. Register 2 contains the
The abend code is in the VRAOA field and the reason
return code from the request.
code is in the VRAOR15 field.
0C06 The resource manager requested that storage in the
14yy An error occurred during PC/AUTH initialization. The
system queue area (SQA) be freed, but the request
system does not write an SVC dump or a logrec data set
failed. Register 2 contains the return code from the
error record.
request.
1411 A program received a non-zero return code from the
0C07 The resource manager requested that storage in the
system address space creation. Register 2 contains the
PC/AUTH address space's local system queue area
original return code and register 3 contains the original
(LSQA) be freed. The request failed. Register 2 con-
reason code.
tains the return code from the request.
1412 A routine received a non-zero return code from the
0C09 The resource manager requested that storage in the
system address space initialization. Register 2 contains
PC/AUTH address space's pageable storage be freed.
the original return code and register 3 contains the ori-
The request failed. Register 2 contains the return code
ginal reason code.
from the request.
1413 A routine issued the NUCLKUP macro but the system
0C0A The resource manager requested that a dynamic work
was unable to process the request. Register 2 contains
area be freed, but the request failed. Register 2 contains
the original return code and register 3 contains the
the return code from the request.
parameter passed to NUCLKUP.
0C97 An unexpected error occurred. Another abend occurred
1414 The sum of the highest linkage index (LX) value in the
while PC/AUTH was processing and the system con-
system function table (SFT) and the value in the
verted the abend to X'053'. Look in the SDWA variable
SVTNSLX field of the system vector table (SVT) is
recording area (SDWAVRA) for the original abend and
greater than decimal 1023. This condition indicates that
reason codes and continue diagnosis with that code.
the SFT or the SVT was incorrectly modified. Register 2
0C99 The acronym at the beginning of a PC/AUTH control contains the highest LX value in the SFT, and register 3
block is incorrect. Register 2 contains the expected contains the value in the SVTNSLX field.
acronym.
1415 The routine received an incorrect return code from the
0CC1 The ASCBAXR count in the address space control block bind break. Register 2 contains the return code.
(ASCB) for the ending address space was too low.
15yy A PC/AUTH service abnormally ended.
0CC2 The ASCBLXR count in the address space control block
1501 An unexpected error occurred while updating the primary
(ASCB) for the ending address space was too low.
address space number (PASN) access list.
0CC3 The bind break routine issued a non-zero return code.
0Dyy The Program Call authorization functional recovery 054
routine (PC/AUTH FRR), detected an error. For any yy
Explanation: An unrecoverable error occurred when a program
value except 88 and 89, the PC/AUTH FRR detected an
requested a scheduler JCL facility (SJF) service.
incorrect service-in-control code and cannot determine
which PC/AUTH service is running; the dump title con- The error is internal. The valid reason codes, in decimal format, to
tains PCRAEERC =nnnn, where nnnn is the value in the report to the IBM Support Center are as follows:
PCRAEERC field of the Program Call recovery area
(PCRA) at the time the FRR got control. Reason Codes:
0D88 The FRR received return code X'18' after single- 1 2 3 4 5
threaded queue verification. 6 7 8 9 10
11 12 13 14 15
0D89 The FRR received return code X'18' after double- 16 17 18 19 20
threaded queue verification. 21 23 24 25 26
27 29 30 31 32
11yy The program issued a PCLINK macro with the STACK 33 34 35 36 37
parameter. 38 39 40 41 42
1110 PC/AUTH requested storage for storage in the common 43 100
storage area (CSA). the request failed. Register 2 con-
Source: Scheduler JCL facility (SJF)
tains the return code from the request.
System Action: The system abnormally ends SJF processing.
System Completion Codes SCC-33
055 058
System Programmer Response: Search problem reporting data macro instruction. The DCBDEBAD field in the data control block
bases for a fix for the problem. If no fix exists, contact the IBM points to a data extent block (DEB), which in turn points to the unit
Support Center. control block. The unit control block is used by the control program
to obtain information about an I/O device; each unit control block is
055 associated with one I/O device.
Explanation: The system found an error while processing a listen Source: DFSMSdfp
or signal request for event notification. Register 15 contains a Programmer Response: toeck the first operand in the ANALYZ or
hexadecimal reason code that explains the error: GSERV macro instruction to make sure that it correctly specified the
Code Explanation poll list address or list item address. If the first operand was correct,
make sure that the macro expansion and the data control block were
24 The storage containing the requestor's event parameter not incorrectly modified by program errors. After correcting the error,
list was overlaid after initial validation. run the job step again.
28 An error occurred in one of the listen requests waiting to System Programmer Response: If the error recurs and the
be processed. program is not in error, look at the messages in the job log for more
30 An ENF signal pre-processing routine returned a non- information. Search problem reporting data bases for a fix for the
valid return code. problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job.
34 During ENF initialization, ENF could not obtain the
address of a needed signal pre-processing routine.
057
38 The control blocks representing a listen request contain
instructions that are not valid for comparing the listener's Explanation: The error occurred during processing of the graphic
bit-mapped qualifier with the bit-mapped qualifier associ- attention service routine for the IBM 2250 Display Unit. The routine
ated with the current event. referred to a unit control block (UCB) that was associated with a
device other than a graphic device. The routine obtained the refer-
3C The system could not create the IEFSCHAS address
ence to the unit control block through a data control block (DCB).
space. Time-of-error registers 2 and 3 contain the return
The user gives the routine the addresses of data control blocks
and reason codes, respectively, from the ASCRE macro.
through the poll list address in the first operand of the ANALYZ
40 The system could not join or create ENF's XCF group. macro instruction or the address of one data control block through
Time-of-error registers 2 and 3 contain the return and the list item address in the first operand of the GSERV macro
reason codes, respectively, from the IXCJOIN macro. instruction. The DCBDEBAD field in the data control block points to a
data extent block (DEB), which in turn points to the unit control
44 The system could not obtain information about the other
block. The unit control block is used by the control program to obtain
members of ENF's XCF group. Time-of-error registers 2
information about an I/O; each unit control block is associated with
and 3 contain the return and reason codes, respectively,
one I/O device.
from the IXCQUERY macro.
Source: DFSMSdfp
48 The system could not send an event notification to other
systems in the sysplex. Time-of-error registers 2 and 3 Programmer Response: Check the first operand in the ANALYZ or
contain the return and reason codes, respectively, from GSERV macro instruction to make sure that it correctly specified the
the IXCMSGO macro. poll list address or list item address. If the first operand was correct,
make sure that the macro expansion and the data control block were
4C The system could not receive an event notification from
not incorrectly modified by program errors. After correcting the error,
some other system in the sysplex. Time-of-error regis-
run the job step again.
ters 2 and 3 contain the return and reason codes,
respectively, from the IXCMSGI macro. System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
Source: Event notification facility (ENF)
information. Search problem reporting data bases for a fix for the
System Action: For reason code X'34', ENF initialization fails. For problem. If no fix exists, contact the IBM Support Center. Provide the
reason codes X'3C', X'40', and X'44', ENF sysplex-wide notifica- JCL and the program listing for the job.
tion is not available. For all other reason codes, the system abnor-
mally ends the current task. All other processing continues.
058
Programmer Response: Respecify the data on the event param-
Explanation: Supervisor control detected an error when estab-
eter list.
lishing a work unit's cross memory environment. Register 15 con-
System Programmer Response: If the problem persists, search tains a hexadecimal reason code to be used when searching
problem reporting data bases for a fix for the problem. If no fix problem reporting data bases or when reporting the problem to the
exists, contact the IBM Support Center. IBM Support Center. The reason code in register 15 is one of the
following:
056 Code Explanation
Explanation: The error occurred during processing of the graphic 00 An attempt to establish a cross memory environment
attention service routine for the IBM 2250 Display Unit. The routine failed. The target ASID was not valid for the cross
referred to an incorrect unit control block (UCB). The routine memory address.
obtained the reference to the unit control block through a data
04 The work unit's primary address space job step task has
control block (DCB). The user gives the routine the addresses of
ended. The low order halfword of register 12 contains
data control blocks through the poll list address in the first operand
the primary ASID number.
of the ANALYZ macro instruction or the address of a data control
block through the list item address in the first operand of the GSERV
SCC-34 OS/390 V2R8.0 MVS System Codes
059 059
08 The work unit had addressability to an incorrect primary reason code of the failure, and, if available, the logrec data set
ASID. The low order halfword of register 12 contains the error record.
primary ASID number. Termination of the primary
address space is the likely cause of this error. 059
0C The work unit's secondary address space job step task Explanation: Supervisor control detected an error during stop or
has ended. The low order halfword of register 11 con- reset processing. A hexadecimal reason code in register 15 explains
tains the secondary ASID number. the error:
10 The work unit had addressability to an incorrect sec- Code Explanation
ondary ASID. The low order halfword of register 11 con-
tains the secondary ASID number. Termination of the 00 Stop processing received as input a disabled program
secondary address space is the likely cause of this error. status word (PSW).
14 Internal error. Contact the IBM Support Center. 08 An unrecoverable error occurred during stop/reset proc-
essing.
18 Internal error. Contact the IBM Support Center.
0C Stop processing detected a request to stop a task with
1C Internal error. Contact the IBM Support Center. an unlocked task control block (TCB). The task was
20 Internal error. Contact the IBM Support Center. already stopped.
24 Internal error. Contact the IBM Support Center. 10 Reset processing detected a request to reset a locked
TCB. The task did not hold a local lock or cross memory
28 An attempt to establish a cross memory address failed.
local (CML) lock.
The ASCB for the target ASID did not pass validity
checks. The first four bytes of the target ASCB did not 14 Reset processing detected a request to reset a locked
contain the character 'ASCB'. Register 12 contains the TCB, but the address space control block (ASCB)
address of the invalid ASCB. lockword did not contain a suspend value of
X'7FFFFFFF'.
2C The work unit had addressability to an incorrect primary
ASID. The low order halfword of register 12 contains the 18 A program requested that functional recovery routines
primary ASID number. Termination of the primary (FRR) be deleted from the normal stack, but the
address space is the likely cause of this error. program is not currently running with the normal stack.
30 The work unit had addressability to an incorrect sec- 1C Stop/reset processing was unable to obtain a linkage
ondary ASID. The low order halfword of register 11 con- stack for a routine running under a service request block
tains the secondary ASID number. Termination of the (SRB).
secondary address space is the likely cause of this error. 20 Reset processing detected a request to reset a locked
34 Internal error. Contact the IBM Support Center. SRB, but the ASCB lockword did not contain the
suspend value X'7FFFFFFF'.
38 Internal error. Contact the IBM Support Center.
Source: Supervisor control
3C Internal error. Contact the IBM Support Center.
System Action: The system abnormally ends the program that
For the above listed reason codes this abend may be normal. That
requested the stop or reset processing. The system may write a
is, if a work unit's primary or secondary address space ends or if the
logrec data set error record.
primary or secondary address space job step task ends, the required
cross memory connection cannot be made and the work unit abnor- Operator Response: If the system programmer asks for an SVC
mally ends with abend X'058'. Use the reason code to perform a dump, set the following SLIP trap:
search in the IBM database and indicate the findings when reporting SLIP SET,COMP=ð59,ACTION=SVCD,END
the problem to the IBM Support Center.
System Programmer Response: Do the following:
Source: Supervisor control
1. For reason code X'08' or X'1C', ask the operator to set a
System Action: The system abnormally ends the program that SLIP trap to obtain an SVC dump. Contact the supervisor
requested the cross memory service. The system may write a logrec control component group at the IBM Support Center. Provide the
data set error record. SVC dump and, if available, the logrec data set error record.
Operator Response: If the system programmer asks for an SVC 2. For any other reason code, use the address in register 14 at the
dump, set the following SLIP trap: time of error to identify which module requested stop or reset
SLIP SET,COMP=ð58,ACTION=SVCD,END processing.
System Programmer Response: Do the following: For an installation-provided module, continue diagnosis with
the module.
1. Use the address in register 14 at the time of error to identify the
module that requested the cross memory services. For an IBM module, search problem reporting data bases
for a fix for the problem. If no fix exists, ask the operator to
2. Search problem reporting data bases for a fix for the problem. If
set a SLIP trap to obtain an SVC dump. Contact the compo-
no fix exists, ask the operator to set a SLIP trap to obtain an
nent group associated with this module at the IBM Support
SVC dump. Contact the component group associated with this
Center. Provide the SVC dump and, if available, the logrec
module at the IBM Support Center. Provide the SVC dump, the
data set error record.
System Completion Codes SCC-35
05A 05C
101 The ATTACH macro instruction was issued for the eli-
05A
gible device table (EDT) verification routine during allo-
Explanation: Supervisor control detected an error in a request to cation initialization processing. The return code from the
free a service request block (SRB) or to free a suspended SRB ATTACH routine was not zero.
(SSRB). Register 15 contains a hexadecimal reason code to be used
201 Allocation was invoked during DDR SWAP to update the
when searching problem reporting data bases or when reporting the
unit control block (UCB) pointer list (UPL) so that the
problem to the IBM Support Center.
UPL would reflect the swapped UCBs. However, one or
Source: Supervisor control both of the swapped UCB addresses is not in the UPL.
System Action: The system abnormally ends the program that 202 Error in read locate of a single SWA block or invalid
tried to free the SRB or SSRB. The system may write a logrec data UCB address passed to IEFAB4A4.
set error record.
203 IEFAB4FP discovered that SIOTDDIB does not point to
Operator Response: If the system programmer asks for an SVC a DDIB.
dump, set the following SLIP trap:
224 IEFAUTOS ENQ not held.
SLIP SET,COMP=ð5A,ACTION=SVCD,END
225 No required device array.
System Programmer Response: Do the following:
226 No required device type array.
1. Use the address in register 14 at the time of error to identify the
227 Invalid function request.
module that tried to free an SRB or an SSRB.
228 Coupling Facility (CF) locks already held.
2. Search problem reporting data bases for a fix for the problem. If
no fix exists, and no dump was written with the abend, ask the 229 Required XES locks not held.
operator to set a SLIP trap to obtain an SVC dump. Contact the 230 Unknown return code from IEFSALOC.
component group associated with this module at the IBM
Support Center. Provide the the dump used, the reason code of 231 Invalid Queue Manager Queue Block Pointer.
the failure, and, if available, the logrec data set error record. 301 At the end of processing all allocation requests for a job
step, an unsatisfied request is detected. An incorrectly
05B modified eligible device table (EDT) or specifying VSAM
parameters for a non-VSAM data set is the probable
Explanation: A system service running in service request block
cause.
(SRB) mode issued an SRBTIMER macro to set a processing time
limit. When the time limit expired, timer supervision ended the 303 Error encountered in the EDL storage manager.
service. 304 Unexpected return code for IEFAB480.
Source: Timer supervision 305 Either the EDT library section does not exist or an error
System Action: The system abnormally ends the system service. occurred while obtaining the library names from the
current configuration.
Operator Response: Retain the logrec data set error records.
Contact hardware support. 306 IEFAB480 found a cost adjustment value of zero which
would fail to decrease any transformed costs (TCs).
Reason codes '00090011'x, '00090024'x, and '0009002C'x are
missing and should not be in the lists. 307 IEFAB480 found an edge with a valid transformed cost
(TC), but never adjusted the transformed cost.
05C 308 Two jobs are allocated to the same tape drive.
Explanation: An error occurred during allocation of the data sets 309 Devices selected by JES3 are not in the Allocation Eli-
for a job step. Register 15 contains a hexadecimal reason code that gible Device List (EDL).
you should report to the IBM Support Center. 501 Undefined return code from JES3.
The following are valid hexadecimal reason codes: 604 IEFAB4MG (called by macro IEFMSGBL) was
Code Explanation attempting to build a message, but no message defi-
nition was found.
001 System address space initialization denied the request to
create the allocation address space. 608 IEFAB4MG (called by macro IEFMSGBL) was
attempting to build a message, but the SIOT pointer
002 The allocation address space received a nonzero return
required for this message was not found.
code from GETMAIN processing.
60C IEFAB4MG (called by macro IEFMSGBL) was
003 The display allocation tables manager received a
attempting to build a message, but an incorrect number
request which, if processed, would cause the DALTUSE
of variables was supplied.
count to be less than zero.
610 IEFAB4MG (called by macro IEFMSGBL) was
004 An allocation module issued the POST macro instruc-
attempting to build a message, but an invalid buffer was
tion, and the macro processing has entered the routine
passed.
specified on the ERRET parameter.
614 IEFAB4MG (called by macro IEFMSGBL) was
005 An allocation module issued the ESTAE macro instruc-
attempting to build a message, but no storage was
tion, and the return code from ESTAE processing was
defined for the message buffer.
not zero.
618 IEFAB4MG (called by macro IEFMSGBL) was
006 An allocation module issued the STIMERM macro
attempting to build a message, but the message text
instruction, and the macro processing has entered the
was too long.
routine specified on the ERRET parameter.
SCC-36 OS/390 V2R8.0 MVS System Codes
05D 05D
701 The scheduler JCL facility (SJF) returned an unexpected 90026 IXLEERSP failed for DISCFAIL.
return code or reason code.
90027 IXLREBLD failed.
702 SVC 99 caller does not hold the SYSZTIOT resource
90028 IXLEERSP failed for QUIESCE.
and has requested that TIOT resource be obtained.
90029 IXLEERSP failed for CLEANUP.
704 SIOT to be dechained is not found in the SIOT chain.
9002A IXLEERSP failed for REBUILDSTOP.
804 Allocation tried to remove a DSAB entry from the
dynamic communication table, but the entry did not exist. 9002B IXLREBLD failed.
807 Allocation tried to mark a DSAB entry in the dynamic 9002D IEFAUTOS structure full.
communication table as eligible for remove in-use proc- 9002E IXLCONN failed.
essing, but the entry did not exist.
9002F IXLLIST service failed.
80B Allocation tried to change the TCB address of a DSAB
90030 IXLLIST monitor list failed.
entry in the dynamic communication table, but the entry
did not exist. Source: Allocation/unallocation
8FF Allocation's dynamic communication table manager was System Action: The system issues message IEF100I or message
called with an invalid function code. IEF197I with the abend code and the reason code. The system stops
allocation processing for the step. The system ends the job, writes
90001 LOAD of EXTR IEFHB431 failed.
an SVC dump, and writes a logrec data set error record.
90002 ATTACH of IEFHB430 failed.
System Programmer Response: Search problem reporting data
90003 IXLCONN returned a parameter error. bases for a fix for the problem. If no fix exists, contact the IBM
90004 ENFREQ service failed. Support Center. Report the reason code accompanying the abend.
90005 Failed to release an XES lock.
05D
90006 ATTACH of IEFHB430 failed.
Explanation: A program issued a CALLDISP macro that is not
90007 Rebuild complete (IXLEERSP) response failed. valid. A hexadecimal reason code in register 15 explains the error:
90008 IEFHB430 failed and is not restartable. Code Explanation
90009 Failed to release an XES lock. 00 The program is disabled and has super bits set.
9000A OASD list is corrupted. 04 The current functional recovery routine (FRR) stack is
9000B AWTR CPOOL create failed. not the normal FRR stack.
9000C IXLDISC service failed. 08 The macro specified FRRSTK=SAVE while the program
holds a lock, or the macro specified FRRSTK=NOSAVE
9000D AWTR CPOOL create failed.
while the program holds a lock other than the LOCAL
9000E GRS latch create (ISGLCRT) failed. lock or the cross memory local (CML) lock.
9000F IXLCONN failed. 0C The program is the first level of the recovery termination
90010 IXLLIST service failed initializing IEFAUTOS. manager (RTM1), a service invoked by RTM1, or an
FRR.
90012 IXLLIST service failed initializing IEFAUTOS.
10 The program was not in task control block (TCB) mode.
90013 IXLLIST service failed initializing IEFAUTOS.
14 Register 0, on input, contained a function code that is
90014 IXLLIST service failed initializing IEFAUTOS. not valid.
90015 IXLLIST service failed initializing IEFAUTOS. 18 Register 1, on input, did not contain 0.
90016 ATTACH of IEFHB430 failed. 1C *** This reason code was deleted as of MVS/ESA SP
90017 Failed to release an XES lock. 5.2. ** * The macro specified FRRSTK=SAVE while the
program holds the LOCAL lock or CML lock, but no
90018 IXLLIST failed during rebuild.
enabled, unlocked task (EUT) FRRs exist on the normal
90019 LOCK failed during cleanup processing. FRR stack.
9001A IXLLIST failed during cleanup processing. Source: Supervisor control
9001B Failed to release an XES lock. System Action: The system abnormally ends the program that
9001C IXLLIST failed during cleanup processing. issued the CALLDISP macro. The system may write a logrec data
set error record.
9001D IXLLIST monitor list failed.
Operator Response: If the system programmer asks for an SVC
9001E Vector size too small. dump, set the following SLIP trap:
9001F IEFAUTOS not defined during reconnect. SLIP SET,COMP=ð5D,ACTION=SVCD,MATCHLIM=1,END
90020 No active policy during reconnect. System Programmer Response: Do the following:
90021 IXLLIST service failed. 1. Ask the operator to set a SLIP trap to obtain an SVC dump.
90022 IXLCONN service failed. 2. Analyze the dump to see if the program that abended was
90023 IXLCONN service failed. entered by a Supervisor Call (SVC) or Branch instruction, as
follows. In the system trace, look for an SVC X'74' entry.
90025 IXLDISC service failed during rebuild. Routing code 08 will be in the UNIQUE-1 column.
System Completion Codes SCC-37
05E 060
If found, the program was entered by an SVC instruction. For an installation-provided module, continue diagnosis with the
Use the address in the PSW ADDR column for this SVC module.
entry to identify the module that issued the CALLDISP
For an IBM module, search problem reporting data bases for a
macro.
fix for the problem. If no fix exists, ask the operator to set a
If not found, the program was entered by a Branch instruc- SLIP trap to obtain an SVC dump. Contact the component group
tion. Register 14 contains the address of the caller. Use the associated with this module at the IBM Support Center. Provide
address in register 14 to identify the module that issued the the SVC dump and, if available, the logrec data set error record.
CALLDISP macro.
3. After identifying the module, do one of the following: 05F
For an installation-provided module, continue diagnosis with Explanation: The VSPC address space encountered an error.
the module. Source: Vector processing
For an IBM module, search problem reporting data bases System Action: The VSPC address space and all address spaces
for a fix for the problem. If no fix exists, contact the compo- that depend on the VSPC address space are abnormally ended. The
nent group associated with this module at the IBM Support system writes a logrec data set error record.
Center. Provide the SVC dump and, if available, the logrec
data set error record. The system issues messages about the job to the job log. The
system writes an ABEND dump for the failing job step.
05E Operator Response: Notify the system programmer.
Explanation: A program issued the SRBSTAT macro, but this System Programmer Response: Look at the messages in the job
program either: log. If the JOB statement did not specify MSGLEVEL=(1,1), specify it
and run the job again. Obtain the JCL for the job. Obtain the
Is in an environment that is not valid
SYSOUT output for the job. Obtain the ABEND dump for the failing
Specified parameters that are not valid
job step. Collect all printed output and output data sets related to the
A hexadecimal reason code in register 15 explains the error: problem. Obtain the logrec data set error record.
Code Explanation If the problem recurs and if the program is not in error, search
problem reporting data bases for a fix for the problem. If no fix
00 The program holds a lock.
exists, contact the IBM Support Center.
04 The current functional recovery routine (FRR) stack is
not the normal FRR stack.
060
08 The program has super bits set.
Explanation: Bulk data transfer (BDT), BDT TQI, or a subtask
0C The program is not in service request block (SRB) within either address space is ending. One or more accompanying
mode. error messages explain why. Register 15 may contain one of the fol-
10 The program is disabled. lowing reason codes:
14 The first level of the recovery termination manager Code Explanation
(RTM1), a service invoked by RTM1, or an FRR used 3014 A spool error was detected in BDTINGL.
the RESTORE parameter on the SRBSTAT macro.
3024 There are more than 300 DYNALLOC and CELLPOOL
18 The PCLINK stack header was not zero on entry to statements (BDTINGL).
processing for the RESTORE parameter of the macro.
8000 A non-zero code was returned from the master ESTAE
1C The program specified RESTORE or MODIFY on the for BDTINIT.
macro, and the status save area does not contain valid
9000 An error was detected in the FAILDAP routine in
status.
BDTABMN.
20 Processing for the RESTORE parameter of the macro
A000 A non-zero code was returned from the ESTAE is
scheduled an SRB to obtain correct processor affinity,
BDTGSC1.
but the SRB was unable to run.
C000 The ABEND macro was issued by BDTINTK.
24 The program specified MODIFY on the macro, but reg-
ister 0 contains a MODIFY identifier code that is not D000 BDT was unable to register both the FTF and NJE fea-
valid. tures.
Source: Supervisor control E000 A non-zero code was returned from the ESTAE in
BDTTQIAS.
System Action: The system abnormally ends the program that
issued the SRBSTAT macro. The system may write a logrec data set F000 A non-zero code was returned from the ESTAE in
error record. BDTTQMSG.
Operator Response: If the system programmer asks for an SVC F800 A non-zero code was returned from the retry ESTAE in
dump, set the following SLIP trap: BDTTQMSG.
SLIP SET,COMP=ð5E,ACTION=SVCD,END Source: Bulk Data Transfer (BDT)
System Programmer Response: Use the address in register 14 at System Action: BDT or its subtask end and may issue a dump.
the time of error to identify the module that issued the SRBSTAT This abend code is accompanied by messages explaining the error.
macro. System Programmer Response: Use the dump and accompa-
nying codes and messages to determine the cause of the error. For
more information, see the OS/390 BDT Messages and Codes.
SCC-38 OS/390 V2R8.0 MVS System Codes
061 066
061 064
Explanation: The error was detected during processing of a Explanation: An address space that holds a cross memory local
CLOSE macro instruction for a graphic data control block. lock (CML) ended abnormally before it freed the lock.
The graphic CLOSE executor issued a DAR macro instruction for a Note: This abend is directly related to the address space com-
graphic attention control block (GACB) that was not specified (via a pletion. This abend is informational and does not need to be
SPAR macro instruction) by the closing task. pursued independent of the address space completion.
Source: DFSMSdfp Source: Supervisor control
System Action: An abnormal end occurred for the task that issued System Action: The system gives control to recovery for CML lock
the SPAR macro instruction for the graphic attention control block. processing. Other system processing continues.
Programmer Response: Issue a DAR macro instruction, for the
graphic attention control block, in the task that issued the SPAR 065
macro instruction, before the closing task issues the CLOSE macro Explanation: When processing an SSAFF macro, the system
instruction. Then run the job step again. detected an error.
System Programmer Response: If the error recurs and the Register 15 contains a hexadecimal reason code that explains the
program is not in error, look at the messages in the job log for more error:
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the Code Explanation
JCL and the program listing for the job. 04 The index into the subsystem affinity table (SSAT) is
greater than the number of subsystems currently
062 defined.
Explanation: The error occurred during processing of a routine of 08 The caller is not in task control block (TCB) mode.
the graphic subroutine package (GSP) for FORTRAN IV, COBOL, 0C There is insufficient local system queue area (LSQA)
and PL/I. storage to build the SSAT.
A condition was encountered that produced a return code equal to or 10 The specified TCB is incorrect. It does not include the
greater than the absolute value specified by the programmer as the TCB acronym.
‘null’ argument in the call to the INGSP subroutine. The GSPARRAY
14 The caller is disabled.
field in the GSPCB identifies the return code produced, register 2
contains the address of the status table entry last invoked, and reg- 1C The caller's address did not have addressability to the
ister 3 contains the address of the GSPARRAY field. home address space.
Source: DFSMSdfp 20 The specified TCB is not the currently active TCB or a
subtask of the currently active TCB.
Programmer Response: Determine the condition that caused the
job step to be abnormally ended and change the program accord- Source: Task management
ingly. Then, run the job step again.
System Action: The system abnormally ends the program that
System Programmer Response: If the error recurs and the issued the SSAFF macro. The system writes a logrec data set error
program is not in error, look at the messages in the job log for more record and a dump.
information. Search problem reporting data bases for a fix for the
Programmer Response: This is probably an error in the caller for
problem. If no fix exists, contact the IBM Support Center. Provide the
reason codes 04, 08, 10, 14, 1C, and 20. Correct the error. Run the
JCL and the program listing for the job.
job again.
This is probably a system error for reason code 0C. Notify the
063
system programmer.
Explanation: During processing of a graphic program, the 2250
System Programmer Response: Collect all printed output and
operator pressed the CANCEL key on the alphameric keyboard of
output data sets related to the problem. Search problem reporting
the display unit. The 2250 operator selected either the TERMINATE
data bases for a fix for the problem. If no fix exists, contact the IBM
option or the DUMP option on the end option display. The problem
Support Center. Provide the logrec data set record and the dump.
program was ended either with or without a dump.
Source: DFSMSdfp
066
Operator Response: If you were having a problem, report the con-
Explanation: The dispatcher of tasks and service routines detected
ditions that caused you to end the program to the system pro-
an error. A hexadecimal reason code in register 15 explains the
grammer.
error:
Programmer Response: Respond according to the information
Code Explanation
provided by the 2250 operator.
04 A completed routine that ran under a service request
block (SRB) held a system lock when it returned to the
dispatcher.
0C A routine that ran under a suspended service request
block (SSRB) held the cross memory local (CML) lock of
a failing address space. The ASCBFAIL bit is on. The
ASCBFAIL bit is in the address space control block
(ASCB) of the failing address space.
System Completion Codes SCC-39
067 068
10 The SRBASCB field of an SRB or an SSRB points to an 0000000C The interrupted program's extended authority index
ASCB that has an erroneous acronym. (EAX) does not have Set Storage Address Register
(SSAR) authority to the target address space specified
14 A task holds the CML lock of a failing address space.
by a private ALE.
The ASCBFAIL bit for the failing address space is on.
00000010 The EAX in the ALE does not have SSAR authority to
18 Status could not be saved for the current task due to an
the target address space.
error in the dispatcher.
00000014 An ASTE sequence exception occurred while attempting
1C A task attempted to reenter the dispatcher through the
to reference an incorrect or deleted data space.
SRB entry point.
00000018 An unexpected error occurred in the access register
20 A routine that ran under an SRB attempted to reenter
translation second level interrupt handler (SLIH).
the dispatcher through a task entry point.
00000020 An ASTE validity exception occurred when a program
Source: Supervisor control
tried to access a subspace that had been deleted.
System Action: The system abends the task and may write a
00000024 An ASTE sequence exception occurred when a program
logrec data set error record.
tried to access a subspace that had been deleted.
Operator Response: If the system programmer asks for an SVC
xxxx0Axx A program attempted to reference a data space that has
dump, set the following SLIP trap:
been deleted.
SLIP SET,ENABLE,COMP=ð66
xxxx0Bxx An unexpected error occurred when the system tried to
System Programmer Response: Do the following: bring a data space page into real storage.
1. For reason code X'04', go to step 3. Source: Program Call/authorization (PC/AUTH)
2. For any other reason code, go to step 6. System Action: The system abends the task and writes an ABEND
3. For reason code X'04', if a logrec data set error record is not dump for the failing job step.
written with the abend, ask the operator to set a SLIP trap to System Programmer Response: Do the following:
obtain an SVC dump. Format the dump to see:
1. Obtain the ABEND dump for the failing job step. If the JCL for
Register 2 through register 8 the step did not contain a DD statement for an ABEND dump,
Register 10 through register 13 add a SYSMDUMP DD statement.
These are the SRB routine's registers at the time it gave up 2. Find the reason code in register 15.
control.
3. Use the PSW address at the time of the error to obtain the
4. Check these registers to see if one looks like a base register, as name of the load module.
follows. Look for a group of registers containing addresses near
the same place in storage. If you find such a group of registers, 4. If the module is installation-provided, correct it and run the job
look for the register with the lowest address. This is possibly a step again.
base register. Identify the module that is using this register as its 5. If the module is an IBM module, or if the problem persists,
base register. search problem reporting data bases for a fix. If no fix exists,
5. Determine which lock was held when the problem occurred. The contact the IBM Support Center.
current lock held string can be found in two different places:
068
Register 14 at the time of error
Explanation: A JES2 subtask has abnormally terminated. Register
In the PSACLHS field of the SVCE D trace entry for abend
15 contains a hexadecimal reason code which identifies the
X'066'
abending subtask.
6. Search problem reporting data bases for a fix for the problem. If
Code Abending Subtask Name
no fix exists, and an SVC dump has not be obtained, ask the
operator to set a SLIP trap to obtain an SVC dump. Contact the 100 HASPCKVR - JES2 DEBUG option detected an error
IBM Support Center. Provide: building the APPLCOPY.
The SVC dump 104 HASPCKVR - Data integrity error detected.
The system trace 108 HASPCKVR - JES2 DEBUG option detected an error
The logrec data set error record, if available building a Checkpoint Version.
200 HASPSUBS - Subtask work dequeue error has occurred.
067
300 HASPSUBS - The Network Path Manager encountered
Explanation: An access register translation exception occurred. A
an unexpected return code from the $NATGET service.
hexadecimal reason code in register 15 explains the error; x in the
reason code contains diagnostic data: 304 HASPSUBS - Error detected in the Network Path
Manager full path work queue.
Code Explanation
400 HASPACCT - Error detected in the $SMFBUSY queue.
00000004 A program encountered a page fault, segment fault, or
address space secondary entry table (ASTE) validity 600 CFEVENT - JES2 coupling facility exit abnormally
fault on a data space that was deleted. ended.
00000008 The target address space was created after the access 604 HASPCKCF - A coupling facility write request (IXLLIST
list entry (ALE) was created. REQUEST=WRITE) timed out.
SCC-40 OS/390 V2R8.0 MVS System Codes
069 069
608 HASPCKCF - An unexpected return code from a cou- 200 Determine the reason for the failure. JES2 should be
pling facility read request (IXLLIST REQUEST=READ) restarted to recover any lost JES2 processors.
was encountered.
300 Determine the reason for the failure. Contact the IBM
60C HASPCKCF - An unexpected return code from a cou- support center.
pling facility write request (IXLLIST REQUEST=WRITE)
304 Determine the reason for the failure. Contact the IBM
was encountered.
support center.
610 HASPCKCF - An incorrect list element control value was
400 Determine the reason for the failure. JES2 should be
detected associated with an element in a JES2 check-
restarted. Contact the IBM support center.
point structure.
600 Determine the reason for the failure. Contact the IBM
614 HASPCKCF - An unexpected return code from a cou-
support center.
pling facility read request (IXLLIST REQUEST=WRITE)
was encountered. 604 Respond to any reconfiguration messages. Determine
the reason for the failure. Contact the IBM support
618 HASPCKCF - An unexpected return code from a cou-
center.
pling facility request (IXLLIST) was encountered while
processing LIST 0. 608-61C Respond to any reconfiguration messages. Determine
the reason for the failure. Contact the IBM support
61C HASPCKCF - An unexpected return code from a cou-
center.
pling facility request (IXLLIST) was encountered while
processing LIST 0.
069
Source: JES2
Explanation: An address space has ended. A reason code in the
System Action: Specific system actions for each reason code are SDWACRC field of the system diagnostic work area (SDWA) pro-
as follows: vides an explanation.
Code System Action Code Explanation
100 The subtask will recover and recopy the entire check- 00 An error occurred during the creation of a new address
point data set next time the data set is posted. Applica- space from one of the following requests:
tion programs looking at the checkpoint data can detect
this abend by looking at the bad copy indicator. ASCRE macro
CALL IEEMB881
104 The subtask will recover and resume normal processing. LOGON command
108 The subtask will recover and resume normal processing. MOUNT command
START command
200 The subtask will attempt to recover and resume its
search for work. One or more requests might be lost. 04 A request by the caller to destroy an ASCRE-created
This might result in the temporary loss of the corre- address space has completed.
sponding processor because it will not be posted. Source: Master scheduler
300 JES2 main task will ABEND and recovery will rebuild the System Action: For reason code 00, the system:
network path manager control blocks or disable the
network path manager if appropriate. Ends the new address space
Writes a dump
304 JES2 main task will ABEND and recovery will rebuild the Writes a logrec data set error record
network path manager control blocks or disable the Issues messages
network path manager if appropriate.
For reason code 04, the system:
400 The JES2 address space will be terminated.
Ends the new address space
600 The subtask attempts to recover if retry is allowed. If
retry is not allowed, JES2 percolates. System Programmer Response: For reason code 00, do the
following:
604 JES2 treats this as a logical I/O error on the checkpoint
and enters checkpoint reconfiguration. 1. Determine why a new address space could not be created:
608-61C JES2 treats this as a logical I/O error on the checkpoint If a module issued the ASCRE macro, check the return and
and enters checkpoint reconfiguration. reason codes returned from ASCRE. See the OS/390 MVS
Programming: Authorized Assembler Services Reference
Operator Response: Notify the system programmer. ALE-DYN for a description of the return and reason codes.
System Programmer Response: Respond as indicated for the If a module did a direct call to IEEMB881 or if the operator
specific reason code: entered a command to create the new address space,
Code Response check the return codes returned by module IEEMB881.
100 Determine the reason for the copy failure. If the problem 2. If you cannot resolve this problem, search problem reporting
persists, disable the application copy of the checkpoint. data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the dump and the logrec data
104 Determine the reason for the failure. Contact the IBM
error record.
support center.
For reason code 04, no action is necessary.
108 Determine the reason for the failure. Contact the IBM
support center.
System Completion Codes SCC-41
06A 070
06A 06D
Explanation: The functional recovery routine (FRR) for a service Explanation: SLIP processing found that an incorrect parameter list
request block issued a SETRP macro with the SERIAL=YES option. was passed to SLIP.
The macro requests serial percolation to the recovery routine for the
Source: Recovery termination manager (RTM)
task with which the SRB is associated. To prepare for percolation,
the recovery termination manager (RTM) requested storage in the System Action: The system ends SLIP processing for the current
task's local system queue area (LSQA). The request failed. event. The status of program event recording (PER) in the system
and of the existing SLIP traps is unchanged. The system sends mes-
Source: Recovery termination manager (RTM)
sages about the problem to the job log.
System Action: RTM abnormally ends the task. The system writes
Operator Response: If the system programmer asks for an SVC
an ABEND dump for the failing job step. Note that this dump con-
dump, set the following SLIP trap:
tains no time-of-error information for the original problem that caused
entry into the FRR. The system may write a logrec data set error SLIP SET,COMP=ð6D,ACTION=SVCD,END
record. System Programmer Response: Search problem reporting data
Operator Response: If the system programmer asks for an SVC bases for a fix for the problem. If no fix exists, try to obtain the
dump, set the following SLIP trap: ABEND dump for the abend. If no dump exists, ask the operator to
set a SLIP trap to obtain an SVC dump. Contact the IBM Support
SLIP SET,COMP=ð6A,ACTION=SVCD,END
Center. Provide the dump.
System Programmer Response: Do the following:
1. Search problem reporting data bases for a fix for this problem. 06E
If no fix exists, obtain the ABEND dump for the abend. Explanation: One of the following occurred while SLIP was acti-
2. Look in the dump for the reason why the GETMAIN macro vating or deactivating a program event recording (PER) trap:
failed. Check for the possibility of an LSQA GETMAIN loop. For a global PER trap, SLIP requested cell pool storage. The
3. If the reason for the failure cannot be determined, and you need request returned a nonzero return code, indicating an error.
further information from a dump, ask the operator to set a SLIP SLIP requested that cell pool storage be freed. The request
trap to obtain an SVC dump. returned a return code other than 0 or 20, indicating an error.
4. Contact the IBM Support Center. Provide the dump and, if avail- Source: Recovery termination manager (RTM)
able, the logrec data set error record.
System Action: SLIP processing ends.
06B Operator Response: If the system programmer asks for an SVC
dump, set the following SLIP trap:
Explanation: At least one of the input parameters to the excessive
spin loop notification routine is not valid. This is probably a system SLIP SET,COMP=ð6E,ACTION=SVCD,END
error. Register 4 contains the input spin loop reason code, and reg- System Programmer Response: Search problem reporting data
ister 5 contains the target processor identifier. bases for a fix for the problem. If no fix exists, obtain a dump for the
Source: Loadwait/Restart abend. Then contact the IBM Support Center.
System Action: The system abnormally ends the caller of the
06F
excessive spin loop notification routine.
Explanation: An active SLIP trap requests ACTION=RECOVERY.
System Programmer Response: Search problem reporting data
SLIP found a match for the program event recording (PER) trap that
bases for a fix for the problem. If no fix exists, contact the IBM
was defined in the command. For the RECOVERY action, SLIP
Support Center.
gives control to the recovery termination manager (RTM).
06C Source: Recovery termination manager (RTM)
Explanation: One of the following occurred during SLIP processing: System Action: RTM abnormally ends the task being monitored.
SLIP processing continues.
While processing a program event recording (PER) interrupt, the
program being monitored issued a Move Character Long
070
(MVCL) instruction that would overlay low storage.
Explanation: A program issued the SUSPEND, RESUME, or TCTL
The environmental indicators that control SLIP processing were
macro, but the program issuing the macro either:
overlaid or not valid for some other reason.
Is in an environment that is not valid
Source: Recovery termination manager (RTM)
Specified parameters that are not valid
System Action: The system ends SLIP processing for the current
A hexadecimal reason code in register 15 explains the error:
event. The status of PER in the system and of the existing SLIP
traps is unchanged. Code Explanation
System Programmer Response: If the program being monitored 0C The program issued the RESUME macro with the
caused the problem, correct the program. If the problem cannot be RETURN=N parameter, but the program was not in
resolved, search problem reporting data bases for a fix for the service request block (SRB) mode.
problem. If no fix exists, contact the IBM Support Center. 10 The program issued the RESUME macro, but the speci-
fied task control block (TCB) was not valid.
SCC-42 OS/390 V2R8.0 MVS System Codes
071 071
14 The program issued the RESUME macro, but could not Center. Provide the SVC dump, including registers 14 and
address the specified address space control block 15, and, if available, the logrec data set error record.
(ASCB).
18 The program issued the RESUME macro with the 071
RETURN=N parameter, but the program was not in Explanation: An error occurred when the operator initiated a
primary address space control mode. restart.
1C The program issued the RESUME macro with the Register 15 contains a hexadecimal reason code that explains the
RETURN=N parameter while holding one or more locks error:
or while running with a PCLINK stack that was not
empty. Code Explanation
20 The program issued the TCTL macro, but was not in 00 A program was in a loop or wait that the operator could not
SRB mode. cancel. The operator did one of the following:
24 The program issued the TCTL macro, but was not in Selected RESTART option 0.
primary address space control mode. Selected RESTART with no option. When no option is
28 The program issued the TCTL macro while holding one specified, the system defaults to option 0.
or more locks. Did not reply to message IEA502I within 125 seconds.
2C The program issued the RESUME macro with the 04 The operator selected RESTART option 1 to initiate
MODE=UNCOND parameter and the ASYNC=N param- system diagnosis and repair.
eter, but the program held the local lock of an address
08 A programming error caused the program that was cur-
space other than the target address space.
rently running to branch directly to the restart interruption
30 The program issued the SUSPEND macro, but the handler.
request block (RB) suspend count was not 0.
0C The operator selected RESTART option 0 on a processor
34 The program issued the SUSPEND macro with the that is in a valid spin waiting for a global resource held by
RB=PREVIOUS parameter, but no previous RB existed. a second processor that is in an erroneous disabled loop.
38 Processing for a RESUME macro detected a request to A DSGNL RESTART command, directed to the second
resume an RB that had a suspend count other than 0 or processor, failed.
1. 10 The system started writing logrec data set error records
3C A RESUME macro with unconditional synchronous after detecting an excessive spin loop condition. The inter-
options required the local lock. The issuer was disabled rupted unit of work continues to run.
and did not hold the necessary local lock. 20 The system abnormally ended the program that was
40 Processing for a RESUME macro detected a request causing a system excessive spin loop. Recovery routines
from reset processing to resume an RB. The RB does are not allowed to retry because the recovery action for the
not exist on the RB chain for the specified TCB. spin loop was TERM.
Source: Supervisor control 30 The system abnormally ended the program that was
causing a system excessive spin-loop condition. Recovery
System Action: The system abnormally ends the program that routines are allowed to retry because the recovery action
issued the macro. The system may write a logrec data set error for the spin loop was ABEND.
record.
Source: Loadwait/Restart
Operator Response: If the system programmer asks for an SVC
dump, set the following SLIP trap: System Action: The system does one of the following:
SLIP SET,COMP=ð7ð,ACTION=SVCD,END For reason code X'00', X'08', X'0C', X'20', or X'30', the
system abnormally ends the program currently running.
System Programmer Response: Do the following:
For reason code X'00', the system may issue message
1. If a dump or a logrec data set error record was not written with IEA500A.
the abend, ask the operator to set a SLIP trap to obtain an SVC
dump. For reason code X'04', the system detects and repairs, where
possible, errors in critical system areas. The system refreshes
2. The registers at the time of error contain the following selected system control blocks and validates and repairs
information: selected system resources. The system logs the old values of
Register 14 contains the address of the module that issued some refreshed control block fields in the variable recording
the macro. area (VRA) of the system diagnostic work area (SDWA). The
system writes these old values in the logrec data set error
Register 15 contains the reason code and indicates whether
record. Then the system returns control to the interrupted
the error is a SUSPEND, RESUME, or TCTL error.
program.
3. Use the address in register 14 to identify the module that issued
For reason code X'10', the system records the excessive spin
the macro.
loop in a logrec data set error record.
For an installation-provided module, fix the error described
Operator Response: If requested by the system programmer, set a
by the reason code and rerun the job.
SLIP trap to obtain a dump.
For an IBM module, search problem reporting data bases
System Programmer Response: Depending on the reason code,
for a fix for the problem. If no fix exists, contact the compo-
do the following:
nent group associated with this module at the IBM Support
System Completion Codes SCC-43
072 073
Reason Code X'00'
072
Message IEA500A may accompany this reason code and iden-
tify the work that was in progress at the time of the interruption. Explanation: The system abnormally ended a program that had a
processor affinity requirement because no processors on which it
1. If a logrec data set error record is not produced with the can run are online. A hexadecimal reason code in register 15 indi-
abend, ask the operator to obtain an SVC dump. cates the type of program:
2. Examine the program status word (PSW) at the time of Code Explanation
error in the logrec data set error record. The PSW points to
the location where RESTART was entered by the operator. 0004 A task running under a task control block (TCB).
If the program was in a loop, the PSW address will be 0008 A routine running under a service request block (SRB).
within the loop.
Source: Supervisor control
3. Examine the system trace table for evidence of a loop or a
System Action: The system abnormally ends the program that had
wait. If a loop or a wait is suspected, use the address in the
a processor affinity requirement.
PSW to obtain the name of the looping module.
Programmer Response: Resubmit the job when the processor
If the module is not an IBM module, continue diagnosis
affinity requirements can be met.
with the module.
If the module is an IBM module, search problem
073
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the Explanation: Supervisor control detected an error while processing
dump and the logrec data set error record. a SETLOCK OBTAIN or SETLOCK RELEASE macro. The
hexadecimal reason code in register 15 explains the error:
Reason code X'08'
Determine which program branched incorrectly, as follows: Code Explanation
00 While spinning for a disabled spin lock, the system found
1. If a logrec data set error record is not produced with the
that the lockword contains a processor identifier that is
abend, ask the operator to obtain an SVC dump.
not valid. Register 10 contains the lockword value that is
2. Look at register 14 at the time of the error. If the illegal not valid.
branch was made by a BALR 14,15 instruction, register 14
04 The system detected serialization that is not valid. The
points to the instruction following the instruction that took
caller was disabled but requested the LOCAL, cross
the bad branch. If this instruction is a branch instruction,
memory local (CML), or cross memory services (CMS)
then this instruction probably branched directly into the
lock unconditionally. The lock was not immediately avail-
restart interrupt handler.
able.
3. Use the address in register 14 to get the name of the
08 The system detected a hierarchy violation.
module that issued the bad branch instruction.
If a SETLOCK OBTAIN macro was being proc-
If the module is not an IBM module, continue diagnosis
essed, one of the following occurred:
with the module.
– The requested lock was lower in the locking
If the module is an IBM module, search problem
hierarchy than the locks currently held.
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the – Another lock of the same type was already
dump and the logrec data set error record. held.
Reason code X'0C', X'10', X'20', or X'30' – A CMS lock was requested, but a local lock
Determine why an excessive spin condition occurred, as follows: was not held.
– A local or CML lock was requested uncondi-
1. Get the program status word (PSW) at the time of error as
tionally, but the PSASUPER field was nonzero.
follows:
If a SETLOCK RELEASE macro was being proc-
For reason code X'10', X'20', or X'30', obtain the
essed, one of the following occurred:
PSW from the logrec data set error record.
– A local lock was specified while a CMS lock
For reason code X'0C', X'20', or X'30', ask the
was still held.
operator to obtain an SVC dump. Format the dump to
see the PSW at the time of error. – All CMS locks were specified, but not all CMS
locks were held.
2. Use the address in the PSW to obtain the name of the spin-
ning module. 0C The caller requested a CML lock. The caller passed an
address space control block (ASCB) address that was
If the module is not an IBM module, continue diagnosis
not valid. Register 11 contains the ASCB address.
with the module.
10 The caller requested another address space's CML lock
If the module is an IBM module, search problem
but did not establish an active bind to that address
reporting data bases for a fix for the problem. If no fix
space. Register 11 contains the ASCB address.
exists, contact the IBM Support Center. Provide the
dump and the logrec data set error record. 14 The caller specified an ASCB for an address space that
was being ended. Register 11 contains the ASCB
See OS/390 MVS Diagnosis: Procedures for information about address.
diagnosing a loop. 18 The caller requested the CML lock of an address space
that was not dispatchable. Register 11 contains the
ASCB address.
SCC-44 OS/390 V2R8.0 MVS System Codes
074 075
1C The caller requested the CML lock of the master PSASUPER bits at the time of abend: GPR12/hhhhhhhh
address space or the WAIT address space. PSACLHS bits at the time of abend: GPR13/hhhhhhhh
20 The caller requested a lock type that is no longer sup- If no fix exists, contact component group associated with the
ported. module that issued the SETLOCK macro at the IBM Support
Center. Provide, if available, the SVC dump and the logrec data
24 A caller requested the real storage manager (RSM) or
set error record.
TRACE lock in one of the following ways that is not
valid:
074
With SCOPE=SHR (share), but the caller holds the
lock with SCOPE=EXCL (exclusive) Explanation: A program issued the SETLOCK macro. Supervisor
control could not finish processing the macro for one of these
With SCOPE=EXCL, but the caller holds the lock
reasons:
with SCOPE=SHR
The lockword address specified on the SETLOCK macro is not
28 A caller unconditionally requested a class lock that was
on a fullword boundary.
held by the processor as a class lock at a different level
of the lock hierarchy. A page fault occurs when the lockword address specified on the
SETLOCK macro is used.
2C The caller specified release of locks according to a bit
string mask in register 11. However, the caller does not A machine check occurs in the lockword specified on the
hold all the locks that the mask specifies. SETLOCK macro.
30 The system was invoked recursively for an unconditional Source: Supervisor control
lock obtain. System Action: The system writes a logrec data set error record
34 The caller issued a SETLOCK RELEASE macro to and may write messages about the error.
release a lock from PSACLHS, but the caller is not Operator Response: Check messages and the logrec data set
holding the lock. error record to determine if a machine check occurred just before the
38 The caller issued a SETLOCK RELEASE macro to abend. If so, the problem is a hardware problem. Contact hardware
release a lock from PSACLHSE, but the caller is not support. If not, notify the system programmer. If the system pro-
holding the lock. grammer asks for an SVC dump, set the following SLIP trap:
3C The caller issued a SETLOCK RELEASE macro to
release a spin lock, but the caller is not holding the lock. SLIP SET,COMP=ð74,ACTION=SVCD,END
40 While spinning for a disabled spin lock, the system found System Programmer Response: Do the following:
that global recovery was active. 1. Examine messages and the logrec data set error record for pre-
Source: Supervisor control vious abend codes. Look at the explanations of any previous
abend codes. A previous problem could have caused this
System Action: The system abends the program that issued the problem.
SETLOCK macro. The system may write a logrec data set error
record. 2. If a dump is not produced with the abend, ask the operator to
set a SLIP trap to obtain an SVC dump. In the system trace, find
Operator Response: If the system programmer asks for an SVC the SVC D entry for abend X'074'. In the entry, note the
dump, set the following SLIP trap: address space identifier (ASID) in the ASID column. Back up to
SLIP SET,COMP=ð73,ACTION=SVCD,END look for a PGM entry with the same ASID. This indicates that a
System Programmer Response: Do the following: program check occurred.
1. If a dump or a logrec data set error record was not written with 3. Search problem reporting data bases for a fix for the problem. If
the abend, ask the operator to set a SLIP trap to obtain an SVC no fix exists, contact the component group associated with the
dump. module that took the program check at the IBM Support Center.
Provide all problem data collected and the logrec data set error
2. Identify the module that issued the SETLOCK macro by using record.
the address in register 14 at the time of error.
For an installation-provided module, continue diagnosis with 075
the module.
Explanation: A program running in supervisor state, key 0 issued a
For an IBM module, identify lock information as follows: SCHEDULE macro to schedule a service request block (SRB). The
– Register 9 contains the current lock held string exten- system checked the acronym in the address space control block
sion (PSACLHSE). (ASCB) pointed to by SRBASCB. The acronym failed the check.
Possible reasons are:
– Register 12 contains the PSASUPER bits at the time of
abend. The issuer of the SCHEDULE macro put an incorrect address
into SRBASCB. Consequently, SRBASCB did not point to a
– Register 13 contains the current locks held string valid ASCB.
(PSACLHS) that was current when the lock request
was made. SRBASCB pointed to a valid ASCB, but the ASCB has gone
away normally or abnormally.
See the PSA section of OS/390 MVS Data Areas, Vol 3
(IVT-RCWK) for the meaning of the bits in the PSASUPER, SRBASCB pointed to a valid ASCB, but the ASCB was overlaid.
PSACLHS, and PSACLHSE fields. Source: Supervisor control
3. Search problem reporting data bases for a fix for the problem.
Include in the search argument:
System Completion Codes SCC-45
076 077
System Action: The system ends processing of the SCHEDULE 0008 Command processing requested virtual storage for a
macro. The system may write an SVC dump, a logrec data set error service request block (SRB). The request returned a
record, or both. nonzero return code. Register 5 contains the return
code.
Operator Response: If the system programmer asks for an SVC
dump, set the following SLIP trap: 000C Command processing received a nonzero return code
SLIP SET,ENABLE,COMP=ð75,ACTION=SVCD,END from another command processing module. Register 5
contains the return code.
System Programmer Response: Do the following:
0010 An unexpected error occurred in a command processing
1. If an SVC dump is not produced with the abend, ask the oper- module.
ator to set a SLIP trap to obtain an SVC dump.
Source: Supervisor control
2. Examine SRBASCB to see if it contains a valid address. Reg-
ister 15 at the time of error points to the SRB that was being System Action: The system:
scheduled. Check for an incorrect address in the SRBASCB Ends the START, MOUNT, or LOGON command
field. The address in SRBASCB is not valid if:
Deletes the partially created address space
It is all zeros
Issues message IEA890I to identify which command was ended
It does not end in X'00' or X'80'
as a result of the failure
It is not an address in the system queue area (SQA)
System Programmer Response: If the problem recurs, search
If the address in SRBASCB does not look like a valid address,
problem reporting data bases for a fix for the problem. If no fix
contact the IBM Support Center. Provide all problem data col-
exists, contact the component group for command processing at the
lected.
IBM Support Center.
3. If SRBASCB looks like a valid ASCB address, check the
address space vector table (ASVT) for this address. The ASVT 077
contains a list of ASCB addresses. The CVTASVT field of the
communications vector table (CVT) points to the ASVT. Explanation: While the system was processing a console commu-
ASVTENTY begins the ASCB addresses. Scan for the address nications task (COMMTASK) request, an error occurred. Register 15
that is in SRBASCB. contains a hexadecimal reason code:
4. If the address in SRBASCB is in the ASVT, then the ASCB Code Explanation
pointed to by SRBASCB has been overlaid. See if you recognize 00 In a request to start or stop MONITOR JOBNAMES,
the overlay by looking for any EBCDIC eye-catchers around the STATUS, or SESSIONS processing, the caller passed
overlay. Search problem reporting data bases for a fix for the an incorrect console name or address space identifier
problem. Include in the search argument: (ASID).
EBCDIC eye-catcher that is a module name: PIDS/cccccccc 04 The parameter list passed to the communications task
Abend X'075': AB/S075 was not valid.
Overlay of the ASCB: OVS/ASCB
08 The system found that a caller asked to delete a nonex-
The size and content of the overlay can also be added to the istent buffer.
search argument.
0C The system could not establish a recovery environment.
If no fix exists, contact the supervisor control component group
10 The parameter list passed was not valid.
at the IBM Support Center. Provide data collected in previous
steps and, if available, the logrec data set error record. 14 A caller was not running in the COMMTASK address
space.
5. If the address in SRBASCB cannot be found in the ASVT, then
either: 18 The system could not obtain a needed area.
The ASCB was deleted when the address space went away 1C The system could not process a console request
abnormally. because of conflicting requests in the parameter list.
The ASCB went away normally. 20 The system could not process a console request
because of incomplete or incorrect data in the parameter
The ASCB is not valid. The issuer of the SCHEDULE macro
list.
put a bad address into SRBASCB.
24 The system could not process a console request
Contact the supervisor control component group at the IBM
because the specified console was not dedicated to the
Support Center. Provide data collected in previous steps and, if
requesting component.
available, the logrec data set error record.
28 The system encountered an error in COMMTASK proc-
076 essing.
Explanation: An error occurred while attempting to create or ini- Source: Communications task (COMMTASK)
tialize an address space. One of the following hexadecimal reason System Action: If the error occurred during MONITOR or STOPMN
codes explain the error: command processing, the MONITOR function is not changed. Other-
Code Explanation wise, the system abnormally ends the calling routine.
0004 Command processing received a nonzero return code Operator Response: If the error occurred during MONITOR
from the virtual storage management (VSM). Register 5 command processing, reenter the MONITOR or STOPMN command.
contains the return code. For reason code X'18', look for a message backlog. Ease the
backlog by allowing the messages to roll off the screen or rerouting
the messages to the system log with a CONTROL Q command.
SCC-46 OS/390 V2R8.0 MVS System Codes
078 07B
For other errors, contact the system programmer.
07A
System Programmer Response: Search problem reporting data
Explanation: An unrecoverable error occurred during region control
bases for a fix for the problem. If no fix exists, contact the IBM
task (RCT) processing such as:
Support Center.
A system interruption request block (SIRB) failure
078 A swap-out processing error
Explanation: There was an error in one of the following routines Source: Region control task (RCT)
invoked by the region control task (RCT): System Action: The system gives RCT recovery control. To avoid
ATTACH of the dump task an address space interlock, RCT abends the address space without
cleaning up address space-related resources. The system may or
ATTACH of started task control (STC) during RCT initialization may not write a logrec data set error record.
PURGE I/O during QUIESCE processing System Programmer Response: Search problem reporting data
The real storage manager (RSM) swap out routine during bases for a fix for the problem. If no fix exists, report the problem to
QUIESCE processing the IBM Support Center. Provide the logrec data set error records if
any were written.
RCT received an unacceptable return code from the routine and
cannot continue processing. This abend may indicate a storage
shortage. 07B
Source: Region control task (RCT) Explanation: The system detected an error in interprocessor com-
munications (IPC). A hexadecimal reason code in register 15
System Action: The system gives RCT recovery control. The explains the error:
system:
Code Explanation
Requests that the address space end
00 For a RISGNL macro, the caller passed an incorrect
Issues an SVC dump for the address space if the error was physical configuration communications area (PCCA)
unrecoverable or recursive address. Registers 2 and 3 contain the values of regis-
Writes a logrec data set error record ters 0 and 1 that were input from the caller.
Performs resource clean-up 04 For a RPSGNL macro, the caller passed an incorrect
PCCA address. Registers 2 and 3 contain the values of
System Programmer Response: Look for errors in the logrec data
registers 0 and 1 that were input from the caller.
set error record or the SVC dump indicating a prior failure in the
same address space. Search problem reporting data bases for a fix 08 For a DSGNL macro, the caller passed an incorrect
for the problem. If no fix exists, contact the IBM Support Center. PCCA address. Registers 2 and 3 contain the values of
Provide the logrec data set error record and the SVC dump. registers 0 and 1 that were input from the caller.
0C For a RISGNL macro, the caller's serial receiving routine
079 abnormally ended on the processor processing the
Explanation: An error occurred while the region control task (RCT) emergency signal interrupt. Registers 2 and 3 contain
attention request was trying to obtain or release the local lock. the values of registers 0 and 1 that were input from the
caller.
Source: Region control task (RCT)
10 The emergency signal second level interrupt handler
System Action: The system gives RCT recovery control. The (SLIH) detected second level recursion.
system:
14 For a DSGNL macro, the caller passed an incorrect
Issues a Time Sharing Option (TSO) error message to the ter- order code for the SIGP instruction. This order code is
minal indicating that the attention request was ignored or not supported.
requests an SVC dump of the address space
Source: Supervisor control
Performs resource clean-up
System Action: One of the following:
Writes a logrec data set error record
For reason code X'00', X'04', X'08', X'0C', or X'14', the
May request an SVC dump system abnormally ends the caller.
System Programmer Response: If a TSO error message is issued For reason code X'10', the system writes a logrec data set
to the terminal, you can either regenerate the attention request or error record.
continue processing.
Operator Response: If the system programmer asks for an SVC
Search problem reporting data bases for a fix for the problem. If no dump, set the following SLIP trap:
fix exists, report the problem to the IBM Support Center. Provide the
logrec data set error record and the SVC dump if available. SLIP SET,COMP=ð7B,ACTION=SVCD,END
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.
2. Use the address in register 14 at the time of error to identify the
module that issued the macro or caused the emergency signal
interruption.
For an installation-provided module, continue diagnosis with
the module.
System Completion Codes SCC-47
07C 07E
For an IBM module, search problem reporting data bases From the time an FRR is established until the time it is
for a fix for the problem. If no fix exists, contact the compo- deleted, at least one of the following things must be true:
nent group associated with this module at the IBM Support
Some lock is held
Center. Provide, if available, the SVC dump and the logrec
The unit of work is running disabled
data set error record.
The unit of work is an SRB
An FRR with EUT=YES exists
07C
Source: Recovery termination manager (RTM)
Explanation: The system has detected a recursive ABEND macro
System Action: The system abnormally ends the unit of work that
(SVC 13). Field ASCBARC of the address space control block
issued the SETFRR macro. The system may write a logrec data set
(ASCB) contains a hexadecimal reason code, as follows:
error record. The unit of work may request a dump.
Code Explanation
Operator Response: If the system programmer asks for an SVC
00 The system abnormally ended the task or the address dump, set the following SLIP trap:
space.
SLIP SET,COMP=ð7D,ACTION=SVCD,END
04 The SVC first level interrupt handler (FLIH) recovery
System Programmer Response: Do the following:
abnormally ended the address space.
1. Check for the problem in all installation-provided programs that
Source: Supervisor control
are in protection key 0 and that issue SETFRR. At the time of
System Action: The system ends either the current task or the the abend, register 14 points to the program that invoked
current address space. The system may write an SVC dump, a SETFRR. This program is likely to have caused the problem.
logrec data set error record, or both.
2. Format the dump for the abend to see the prefixed save area
Operator Response: If the system programmer asks for an SVC (PSA) for the system on which the abend occurred. The first 3
dump, set the following SLIP trap: words in the PSASTAK field should contain the following:
SLIP SET,COMP=ð7C,ACTION=SVCD,END ðððððC38 ðððððE38 ðððððð2ð
System Programmer Response: Do the following: 3. If the PSASTAK field is incorrect, an overlay occurred. Use the
1. If an SVC dump was not produced with the abend, ask the oper- following SLIP storage alteration trap to determine which routine
ator to set a SLIP trap to obtain an SVC dump. caused the overlay:
SLIP SET,SA,RANGE=(Cðð,CðB),A=WAIT,END
2. In the dump, find the reason code in the ASCBARC field.
4. Search problem reporting data bases for a fix for the problem. If
3. Search problem reporting data bases for a fix for the problem. If
you suspect an overlay, include in the search argument:
no fix exists, continue with step 4.
Program identifier: PIDS/5752SCRTM
4. Analyze the dump to find the original abend causing the recur-
System abend code: AB/S007D
sive loop, as follows. In the system trace, find the SVC D entry
The name of the field that is overlaid: FLDS/PSASTAK
for abend X'07C'. Note the address space identifier (ASID) in
the ASID column of this entry. Note: Prior to OS/390 the program identifier to search for is
PIDS/5752SC1CM. If no fix exists, contact the IBM
Back up to the next SVC D entry with this ASID. Note the abend
Support Center. Provide problem data collected in the
code in the UNIQUE-3 column. This is the original abend code.
previous steps.
5. Develop a second search argument, using the abend code
found in step 4. If no fix exists, contact the IBM Support Center.
07E
Provide all problem data collected in the previous steps and, if
available, the logrec data set error record. Explanation: A CONFIG or VARY command requested addition or
removal of hardware units from a configuration. To process the
command, the system checked the availability of device paths. While
07D
checking the device paths, the system encountered an error. A
Explanation: The system found an error while adding or deleting a hexadecimal reason code in register 15 explains the error:
functional recovery routine (FRR) from one of the FRR recovery
Code Explanation
stacks.
04 The unit control block (UCB) address, passed to the
The reason codes are as follows:
device path checking routine, did not point to the
Code Explanation common segment of the UCB.
00 The FRR recovery stack could not hold any more FRRs 0C An incorrect function code was passed to the device
because all of the available slots were filled. This abend path checking routine.
is probably caused by an installation-provided program
14 The system received a return code from a device path
that issued SETFRR incorrectly as follows:
checking routine indicating that an unrecoverable
Adding FRRs without deleting them. program or hardware error occurred.
In a loop that includes a SETFRR macro. Source: Reconfiguration
Adding too many FRRs. The system only guaran- System Action: The system ends the CONFIG or VARY command.
tees that installations can add two FRRs.
Operator Response: Depending on the reason code, do the
04 The caller of SETFRR DELETE was not in a legal state following:
to be holding FRRs at the time that SETFRR DELETE
For reason code X'04' or X'0C', contact the system pro-
was issued.
grammer.
SCC-48 OS/390 V2R8.0 MVS System Codes
07F 086
For reason code X'14', if you entered the VARY or CONFIG
084
command to bring a device online, try to vary the individual
paths to the device. If this is unsuccessful, contact hardware Explanation: For an I/O operation, the auxiliary storage manager
support. (ASM) detected an error.
System Programmer Response: Search problem reporting bases Source: Auxiliary storage manager (ASM)
for a fix for the problem. If no fix exists, contact the IBM Support System Action: The system writes a logrec data set error record
Center. and attempts to continue processing.
System Programmer Response: Search problem reporting data
07F
bases for a fix for the problem. If no fix exists, contact the IBM
Explanation: During recovery, the system found that the task Support Center.
control block (TCB) queue associated with the abnormally ended
address space was empty. 085
Source: Task management Explanation: The auxiliary storage manager (ASM) detected an
System Action: The system abnormally ends the address space or internal error.
job. The system writes messages, a logrec data set error record, and Source: Auxiliary storage manager (ASM)
a dump.
System Action: The system writes a logrec data set error record.
Programmer Response: Run the job again. If the error recurs, Processing continues.
notify the system programmer.
System Programmer Response: Search problem reporting data
System Programmer Response: Collect all printed output and bases for a fix for the problem. If no fix exists, contact the IBM
output data sets related to the problem. Search problem reporting Support Center.
data bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Provide the logrec data set record and dump.
086
080 Explanation: The auxiliary storage manager (ASM) received an
error from VSAM during an I/O operation.
Explanation: An unexpected error occurred during system proc-
essing. Register 15 contains the VSAM return code or feedback code in the
first half-word and an ASM return code in the other half-word. The
Source: Real storage manager (RSM) ASM return code identifies the operation that was being attempted
System Action: The system issues an abend to the current when the VSAM error occurred.
address space or to the current unit of work. The system writes a Code Explanation
logrec data set error record. This abend may be accompanied by
messages. 00000008 VSAM did not find the requested record.
System Programmer Response: Search problem reporting data 00000014 VIO journaling data set is full.
bases for a fix for the problem. If no fix exists, contact the IBM 0000001C Could not obtain storage for buffer.
Support Center. Provide the logrec data set record and the SYSOUT
00000030 Partially retrieved ASPCT for release request.
output for the job.
00xx0050 VSAM GENCB macro did not build a request parameter
081 list (RPL) on a GET request.
Explanation: A GETMAIN macro requested virtual storage for the 000C0054 VSAM GET had a physical I/O error.
system queue area (SQA) or the local SQA (LSQA). The request 00140058 VSAM GET found the record was held exclusively by
passed an incorrect virtual address. This is a problem in the system. another requestor. ASM will put the record on the WAIT
Source: Real storage manager (RSM) queue and wait for an ECB to be posted.
System Action: The system denies the request for a central 0028005C VSAM GET had insufficient storage to process the
storage frame. The system writes messages and a dump. request.
System Programmer Response: Search problem reporting data 00xx0060 VSAM GET received a return code from VSAM other
bases for a fix for the problem. If no fix exists, contact the IBM than 0 or those listed here.
Support Center. Provide the messages and the dump. 00400064 VSAM GET was processing the maximum number of
requests already.
083 00xx0070 VSAM GENCB macro did not build a request parameter
Explanation: Auxiliary storage manager (ASM) was unable to list on a PUT request.
convert a logical slot identifier (LSID) to a full seek address. The rel- 000C0074 VSAM PUT had a physical I/O error.
ative byte address (RBA) is outside the range of the extension data
block (EDB) entries. 00140078 VSAM PUT found the record was held exclusively by
another requestor. ASM will put the record on its WAIT
Source: Auxiliary storage manager (ASM) queue and wait for an ECB to be posted.
System Action: The ASM I/O request area (AIA) being processed 0028007C VSAM PUT had insufficient storage to process the
is marked in error. The system writes a logrec data set error record request.
containing a copy of the AIA and EDB. Processing continues.
00xx0080 VSAM PUT received a return code from VSAM other
System Programmer Response: Search problem reporting data than 0 or those listed here.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
System Completion Codes SCC-49
087 08B
00400084 VSAM PUT was processing the maximum number or
08B
request already.
Explanation: An error occurred while the system processed a data-
Notes:
in-virtual service request. Either a parameter on the DIV macro or
1. The high-order byte might not be X'00', but it contains the another condition that existed when the DIV macro was issued
VSAM component code (the component being processed when caused the error. The 2 low-order bytes in register 15 contain a
the error occurred). hexadecimal reason code that explains the error:
2. xx=Return Code or feedback code from VSAM. These codes are Code Explanation
documented in the VSAM Macro Instruction Reference manual.
0001 The caller requested an unknown service.
Source: Auxiliary storage manager (ASM)
0002 Data-in-virtual does not recognize the parameter list
System Action: The system writes a logrec data set error record. format.
Processing continues.
0003 The input parameter list cannot be addressed.
System Programmer Response: Contact hardware support.
0004 The parameter list specifies storage that data-in-virtual
cannot address.
087
0005 The parameter list contains a reserved field that does not
Explanation: The system detected an error while attempting to free contain binary zeroes.
virtual storage.
0006 The caller is not running in task mode.
Source: Auxiliary storage manager (ASM)
0007 The primary and home address spaces are not equal.
System Action: The system writes a logrec data set error record.
Processing continues. 0008 The macro specified an incorrect TYPE parameter.
System Programmer Response: Search problem reporting data 0009 The ID parameter is either incorrect or an ID that the caller
bases for a fix for the problem. If no fix exists, contact the IBM cannot use.
Support Center. 000A Data-in-virtual is processing another data-in-virtual request
with the specified ID.
089 000B The system already accessed an object with the specified
Explanation: A paging I/O operation for the auxiliary storage ID.
manager (ASM) resulted in a permanent I/O error caused by either 000C The caller does not have the proper resource access
hardware or software problems. control facility (RACF) authorization to the requested
Source: Auxiliary storage manager (ASM) object. (Or, the caller is attempting to use a password-
protected data set for an object. Data-in-virtual does not
System Action: If the I/O error occurred during a read operation,
support passwords.)
the system writes a logrec data set error record for abend X'089'.
The system then abnormally ends the task that required the page 000D The specified range exceeds the maximum allowable size
with abend code X'028'. for the object.
If the I/O error occurred during a write operation, ASM retries the 000E The system does not have access to an object for the
write to a different location in the page data set. ASM also writes a specified ID.
logrec data set error record. 000F The specified range overlaps with a range already mapped
If the I/O error was caused by hardware problems, logrec data set for the ID.
may contain a second error record, an outboard record (OBR) for the 0010 The specified virtual range overlaps with an already
I/O error. mapped virtual range in the current address space or the
System Programmer Response: For a hardware problem, contact specified data space.
hardware support. Otherwise, search problem reporting data bases 0011 An undetermined system or caller error occurred while
for a fix for the problem. If no fix exists, contact the IBM Support data-in-virtual was attempting to access data from the
Center. object; all data was not retained.
0012 The virtual storage specified does not begin on a 4-kilobyte
08A boundary.
Explanation: The auxiliary storage manager (ASM) detected a 0013 The virtual storage specified is not in a pageable private
paging I/O error. The problem may have been caused by either the area subpool.
hardware or the software.
0014 The system cannot use the virtual storage specified to map
Source: Auxiliary storage manager (ASM) an object. For example, the virtual storage may contain
System Action: ASM writes a logrec data set error record. storage assigned to virtual input output (VIO).
System Programmer Response: For a hardware problem, contact 0015 The specified range of virtual storage contains at least one
hardware support. Otherwise, search problem reporting data bases page that was not in a virtual range obtained by a
for a fix for the problem. If no fix exists, contact the IBM Support GETMAIN macro.
Center. 0016 The specified virtual storage contains at least one page in
a range that is specified on a current PAGE FIX request;
however, RETAIN=YES was not specified.
0017 Portions of virtual storage that mapped the object were not
addressable, and could not be saved. Either a paging error
occurred or data occupied a bad central storage frame.
SCC-50 OS/390 V2R8.0 MVS System Codes
08B 08B
0018 The caller does not have UPDATE ACCESS to the object. 0030 The virtual range specified contained at least one define
I/O on (IOON) page and RETAIN=YES was not specified.
0019 Data-in-virtual marked as non-pageable a page in a range
to be saved or reset. That is, a PAGE FIX was outstanding 0031 The caller specified an incorrect TTOKEN.
against the page.
0032 The caller is not authorized.
001A The specified range is not in any mapped area of the
0036 The DIV macro supplied an STOKEN value that does not
object.
represent a valid data space that the requester can use.
001B The virtual storage area specified to be unmapped is not
0037 The caller accessed an object that was defined with
currently mapped.
SHAREOPTIONS other than (1,3), and LOCVIEW=YES
001C Data-in-virtual cannot access the object at the current time; was not specified.
the object data set is in use.
0038 The caller attempted to access a non-linear data set.
001D The accessed object is not a virtual storage access
0039 The DIV macro requested a SAVE or RESET on a data
method (VSAM) linear data set, and thus does not have
space range with DREF pages.
the correct control interval size that is implicit for a VSAM
linear data set. 003A Data-in-virtual attempted to MAP the virtual storage of a
ESO type Hiperspace.
001E The length of the DDNAME parameter value exceeds the
maximum size allowed. 003B Data-in-virtual attempted to UNMAP Hiperspace storage,
but RETAIN=YES was not specified.
001F The caller's storage key is not the same as when data-in-
virtual issued the IDENTIFY. 003C Data-in-virtual attempted to UNMAP virtual storage that
maps a Hiperspace data object, but RETAIN=YES was
0020 A task that does not own the specified ID issued a DIV
specified.
macro with an ACCESS parameter.
003D The STOKEN for the object associated with the specified
0021 Data-in-virtual could not access portions of the object on
ID does not represent a valid Hiperspace that may be used
permanent storage; therefore, all data was not retained.
with this request.
0022 A task issued a DIV macro with an IDENTIFY parameter
003E The Hiperspace object may not be accessed at this time.
for an object. The task does not own the virtual storage
Either the maximum for READs has been reached, or
specified to be mapped. For authorized programs, that task
there is a violation of SHARE options.
or one of its subtasks does not own the storage.
003F The DIV macro specified LOCVIEW=MAP for an ID associ-
0023 The caller's storage key does not permit access to part or
ated with a Hiperspace object.
all of the specified storage to be mapped.
0040 The specified MAP range would cause the Hiperspace
0024 The caller issued a DIV macro while holding the local lock.
object to be extended such that the installation data space
0025 The caller issued a DIV macro while in an environment limits for the address space would be exceeded.
that precludes the use of Supervisor Call (SVC)
0041 The DIV macro specified an STOKEN with an ID that
instructions.
represents a Hiperspace data-in-virtual object. Data space
0026 The caller issued a DIV macro, but was not in 31-bit virtual storage cannot be mapped into a Hiperspace.
addressing mode.
0042 The DIV macro tried to access a Hiperspace, but the
0027 The specified OFFSET and SPAN parameters describe a ALESERV ADD command already had been entered for
range that exceeds the maximum supported object size. this Hiperspace.
0028 Data-in-virtual attempted to access an empty data set for a 0046 The caller issued the DIV macro with the SAVE or the
DIV macro with MODE=READ. SAVELIST parameter and specified an incorrect LISTSIZE
value.
0029 Data-in-virtual attempted to map into a disabled reference
(DREF) data space. 0047 The caller issued a DIV macro with the SAVE parameter
with one of the required keywords missing. The missing
002A Data-in-virtual attempted to establish a mapped local view
keyword is either LISTADDR or LISTSIZE.
into a data space. LOCVIEW=MAP was specified on a pre-
vious DIV macro with an ACCESS parameter. 0048 The caller issued a DIV macro with the SAVE parameter
and LISTADDR and LISTSIZE keywords to specify a user
002B The specified virtual range exceeds the bounds of the
list. One of the following problems occurred:
specified data space.
The ranges specified for the user list do not intersect
002C The caller requested either:
with a mapped range.
A data space map while one or more address space
The user list contains incorrect data.
maps were still active under a given ID
0049 The caller issued a DIV macro with the SAVE parameter
An address space map while one or more data space
using incorrect keywords. One of the following is true:
maps were still active under a given ID
The caller used keyword LISTADDR and LISTSIZE to
002D Data-in-virtual deleted the data space. However, the
specify a user list, but also used one or both of the
requested operation completed successfully.
OFFSET or SPAN keywords. The LISTSIZE and
002E Data-in-virtual deleted the data space. The requested oper- LISTADDR keywords are not compatible with the
ation cannot be performed. OFFSET and SPAN keywords.
002F A page to be saved was in the define I/O on (IOON) state. The caller specified the STOKEN keyword with either
the OFFSET or SPAN keywords. The STOKEN
System Completion Codes SCC-51
08C 08C
keyword is incompatible with the OFFSET and SPAN bases for a fix for the problem. If no fix exists, contact the data-in-
keywords. virtual component at the IBM support center.
004A The caller issued a DIV macro with the SAVE parameter
but specified incorrect addresses in the user list. Either an 08C
address was not on a page boundary or the start address Explanation: A program issued a SCHEDULE macro to schedule a
was higher than the end address. service request block (SRB). The system detected an error while
004B The caller issued the DIV macro with SAVE parameter but processing the macro. Register 2 contains the SRB address. Reg-
specified a range in the user list that spans multiple data ister 3 contains the the return address of the issuing program. A
spaces or Hiperspaces. hexadecimal reason code in register 15 explains the error:
004C The caller issued the DIV macro with the SAVE parameter Code Explanation
for a data space or Hiperspace but did not specify the 04 The address specified in field SRBASCB of the service
STOKEN keyword. request block (SRB) does not point to a valid address
004D The user is not authorized to ACCESS the requested data. space control block (ASCB).
004E The caller issued the DIV macro with the MAP parameter 08 The ASCB specified in the SRB has the ASCBFAIL flag
for a shared data page that does not meet the requirement set on. The flag indicates that the address space is ending.
that it reside in non-swappable storage and have a 0C The specified STOKEN does not represent the same
SHAREDWRITE view mode. address space as the ASCB specified in the SRB.
004F The caller issued the DIV macro with the MAP parameter 10 A feature was requested using the SCHEDULE macro but
for another member of the same sharing group. there are no online processors with the specified feature.
0050 The caller issued the DIV macro with the MAP parameter 14 An entry point was requested using the SCHEDULE macro
for a Hiperspace object into shared storage. but an incorrect feature indicator was specified.
0051 The caller issued the DIV macro with the MAP parameter 18 A feature was requested using the SCHEDULE macro but
for one member of a sharing group, but this sharing group an non-valid feature indicator was specified.
contains a member that is currently fixed.
1C An internal error occurred during schedule processing.
0052 The virtual storage specified contains at least one pro-
tected page and RETAIN=YES was not specified. 20 A program issued a SCHEDULE macro to schedule an
SRB with the SPTOKEN option while holding a lock higher
0053 The caller attempted to DIV MAP a page that is part of an than or equal to the DISP lock in the locking hierarchy.
address space view of a shared segment. You cannot use the SPTOKEN option while holding a lock
0801 The storage available was insufficient for building the nec- equal to or higher than the DISP lock.
essary data-in-virtual control block structure. Source: Supervisor control
0802 An I/O driver failure occurred. System Action: The system abnormally ends the program that
0803 The system could not read a required page table into issued the SCHEDULE macro. The system may write a logrec data
central storage. set error record.
0804 The catalog update failed. Operator Response: If the system programmer asks for an SVC
dump, set the following SLIP trap:
0805 An undetermined system error occurred.
SLIP SET,COMP=ð8C,ACTION=SVCD,END
0806 An I/O error occurred.
System Programmer Response: For reason code 10, resubmit the
0807 Data may be damaged in the allocated space on a direct job on a processor complex that has the feature installed. For all
access storage device (DASD). The space is currently other reason codes, do the following:
beyond the saved portion of the object.
1. Ask the operator to set a SLIP trap to obtain an SVC dump.
0808 The system has not completed I/O from a previous
request. 2. In the system trace, find the system service event (SSRV) entry
for abend X'08C'. Diagnostic data in this entry is as follows:
Source: Data-in-virtual
The return address for the issuer of the SCHEDULE macro
System Action: The system abends the program that issued the is in the ADDR column.
DIV macro. The system writes a logrec data set error record, and it
may write a dump. If the reason code is X'0805', data-in-virtual The input SRB address is in the UNIQUE-1 column.
requested an SVC dump with the title COMPON=DATA-IN-VIRTUAL. The target address space ASCB address is in the
System Programmer Response: For reason code 0052, remove UNIQUE-2 column.
the protection status from the protected pages in the specified virtual The STOKEN representing the target address space is in
range. Then issue the DIV macro again. If you want to invoke MAP the UNIQUE-3 column.
or UNMAP and want to preserve the protection status, specify
3. Use the address in the ADDR column of the SSRV entry to
RETAIN=YES when you issue the macro.
identify the module that issued the SCHEDULE macro.
For other reason codes, look in the system trace for the first PC
For an installation-provided module, continue diagnosis with
entry with 0037 in the UNIQUE-1 column above the SVC 0D entry
the module.
for the X'08B' abend. The address column contains the address of
the program that issued the DIV macro. Identify this program. For an IBM module, search problem reporting data bases
for a fix for the problem. If no fix exists, contact the compo-
If the program is installation-provided, continue diagnosis with the
nent group associated with this module at the IBM Support
program. If it is IBM-provided, search the problem reporting data
SCC-52 OS/390 V2R8.0 MVS System Codes
08D 08F
Center. Provide all problem data collected and, if available,
08F
the logrec data set error record.
Explanation: An error occurred during processing of a CHANGKEY
08D macro.
Explanation: A system error occurred during converter processing. Register 15 contains a hexadecimal reason code:
A hexadecimal reason code in register 15 explains the error: Code Explanation
Code Explanation 04 One of the following is true:
0001 The system found a storage management error. The beginning address of the virtual storage range
0002 The system found an error while processing an IF state- specified on the CHANGKEY macro is greater than
ment. the ending address
0003 The system found an error in the statement ordering At least one page in the specified virtual storage
routing processing. range is in an unauthorized subpool.
0004 The system could not find more storage for the converter The system restores all pages processed by the
text data space. Either a large amount of JCL or an CHANGKEY macro before the error to their previous
internal error caused the lack of storage. key.
0005 The system found an error in the symbol table 0C The parameter list specified by the LISTAD parameter
processor. was in pageable storage.
0006 The system found an error in the build message The system restores all pages processed by the
processor. CHANGKEY macro before the error to their previous
key.
0008 During merge processing, the system found a statement
type that is not valid. 10 At least one page in the specified virtual storage range
is part of a sharing group that has been defined by the
020x The system found an internal error while processing an IARVSERV macro.
Advanced Program-to-Program Communications (APPC)
transaction program (TP). The system restores all storage keys to their previous
value.
Other The system found an internal error.
14 An unexpected internal error occurred.
Source: Converter
The system restores all pages processed by the
System Action: The system ends converter processing and does CHANGKEY macro before the error to their previous
not run the job. key.
System Programmer Response: Search problem reporting data 18 A request was made to change a key to 0.
bases for a fix for the problem. If no fix exists, contact the group for
the converter component at the IBM support center. The system restores all pages processed by the
CHANGKEY macro before the error to their previous
key.
08E
2C One of the following is true:
Explanation: The address space was abended by an IMS address
space. The beginning address of the virtual storage range
specified on the CHANGKEY macro is greater than
Source: DFSMSdfp
the ending address
System Action: The address space is abnormally ended.
At least one page in the specified virtual storage
Programmer Response: If the ending address space is a CCTL range is in an unauthorized subpool.
that is hooked up to IMS (DBCTL), then the S08E abend is a result
The system does not restore all pages processed by the
of an operator CANCEL request for that address space. CICS is an
CHANGKEY macro before the error to their previous
example of a CCTL. No further action is needed if the address space
key.
ends to completion. If not, then the operator should try the FORCE
command, which IMS will internally change to a CANCEL command. 34 The parameter list specified by the LISTAD parameter
If the address space still doesn't end after this first FORCE attempt, was in pageable storage.
then the operator can enter the FORCE command again. IMS will The system does not restore all pages processed by the
not change this FORCE attempt, and MVS will process the FORCE CHANGKEY macro before the error to their previous
to end the address space. key.
38 At least one page in the specified virtual storage range
is part of a sharing group.
The system does not restore all pages processed by the
CHANGKEY macro before the error to their previous
key.
3C An unexpected internal error occurred.
The system does not restore all pages processed by the
CHANGKEY macro before the error to their previous
key.
Source: Real storage manager (RSM)
System Completion Codes SCC-53
090 094
System Action: The system issues an abend to the caller of the
092
CHANGKEY macro. The system writes messages, the logrec data
set error record, and the SYSOUT output for the job. Explanation: The error occurred during processing of a basic tele-
communications access method (BTAM) OPEN macro. An OPEN
Programmer Response: For return code 04, 18, 0C, 2C, or 34,
routine found an incorrect or unsupported type of terminal control or
correct the error condition indicated.
terminal adapter specified in the unit control block (UCB) for the
For return code 14 or 3C, run the job step again. device allocated to the data control block (DCB) being opened.
For return code 10 or 38, modify the program to correct the Source: Teleprocessing
IARVSERV macro with the SHARE parameter for the virtual storage
Programmer Response: Check for improper specification of the
range in error. Return code 10 and 38 are relevant only with a
ADAPTER parameter in the IODEVICE macro used in generating the
READONLY or SHAREWRITE view. If the program did not issue the
system. Also, check for program errors that could have improperly
IARVSERV macro, contact the system programmer.
modified control information. Correct the error, and run the job step
System Programmer Response: Search problem reporting data again.
bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: If the error recurs and the
Support Center. Provide the messages, the logrec data set record,
program is not in error, look at the messages in the job log for more
and the SYSOUT output for the job.
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
090 JCL and the program listing for the job.
Explanation: The error occurred during processing of a basic tele-
communications access method (BTAM) OPEN macro. An OPEN 093
routine found that a device other than a communications device was
Explanation: The error occurred during processing of a basic tele-
allocated to the data control block (DCB) being opened. That is, the
communications access method (BTAM) OPEN macro. An OPEN
device class code in the unit control block (UCB) for the device allo-
routine found an incorrect or unsupported type of terminal specified
cated to the data control block was not equal to X'40'.
in the unit control block (UCB) for the device allocated to the data
Source: Teleprocessing control block (DCB) being opened.
Programmer Response: Either the UNIT parameter of the DD Source: Teleprocessing
statement for the communications device is incorrect or the UCB
Programmer Response: Check for improper specification of the
generated during system generation is incorrect. Check for improper
UNIT parameter in the IODEVICE macro used in generating the
specification of the UNIT parameter or the IODEVICE macro used in
system. Also, check for program errors that could have improperly
generating the system. Also, check for program errors that could
modified control information. Correct the error, and run the job step
have improperly modified control information. After correcting the
again.
error, run the job step again.
System Programmer Response: If the error recurs and the
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
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
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job.
JCL and the program listing for the job.
094
091
Explanation: The error occurred during processing of a basic tele-
Explanation: The error occurred during processing of a basic tele-
communications access method (BTAM) OPEN macro. An OPEN
communications access method (BTAM) OPEN macro. An OPEN
routine found an incorrect or unsupported optional feature or mode of
routine found an incorrect or unsupported type of transmission
operation specified in the unit control block (UCB) for the device allo-
control unit specified in the unit control block (UCB) for the device
cated to the data control block (DCB) being opened.
allocated to the data control block (DCB) being opened.
Source: Teleprocessing
Source: Teleprocessing
Programmer Response: Check for improper specification of the
Programmer Response: Check for improper specification of the
FEATURE parameter in the IODEVICE macro used in generating the
IODEVICE macro used in generating the system. Also, check for
system. Also, check for program errors that could have improperly
program errors that could have improperly modified control informa-
modified control information. Correct the error, and run the job step
tion. After correcting the error, run the job step again.
again.
System Programmer Response: If the error recurs and the
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
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
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job.
JCL and the program listing for the job.
SCC-54 OS/390 V2R8.0 MVS System Codes
095 09A
095 098
Explanation: The error occurred during processing of a basic tele- Explanation: The error occurred during processing of a basic tele-
communications access method (BTAM) OPEN macro. An OPEN communications access method (BTAM) OPEN macro. Dual commu-
routine found that the lines allocated to the line group did not have nication interface B or dual code feature B was specified. However,
identical terminal types and/or optional features. the transmission control unit was not a 2701, the transmission
control unit was not the dual communication interface, or the dual
Source: Teleprocessing
code feature was not specified in the unit control block (UCB).
Programmer Response: Determine which line group contains dif-
Source: Teleprocessing
ferent terminals and redefine its lines through DD statements.
Programmer Response: Correct program errors. Run the job
System Programmer Response: If the error recurs and the
again.
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 System Programmer Response: If the error recurs and the
problem. If no fix exists, contact the IBM Support Center. Provide the program is not in error, look at the messages in the job log for more
JCL. information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
096 JCL and the program listing for the job.
Explanation: The error occurred during processing of a basic tele-
099
communications access method (BTAM) OPEN macro. An OPEN
routine found that dynamic buffer allocation had been specified in the Explanation: The error occurred during processing of a basic tele-
DCBBFTEK field of the data control block (DCB). However, the communications access method (BTAM) OPEN macro. An OPEN
OPEN routine could not dynamically allocate buffers because the routine found that dynamic buffering was being initiated while the
data control block specified neither the address of a buffer pool BTAM application was running V=V. BTAM dynamic buffering is not
control block (in the DCBBUFCB field) nor the number and length of supported for V=V.
the buffers (in the DCBBUFNO and DCBBUFL fields).
Source: Teleprocessing
Source: Teleprocessing
Programmer Response: Add the ADDRSPC=REAL operand to the
Programmer Response: Correct the error by doing one of the job statement and initiate the BTAM application again (V=R).
following:
System Programmer Response: If the error recurs and the
Providing a buffer pool and specifying the address of its control program is not in error, look at the messages in the job log for more
block in the DCBBUFCB field. information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
Specifying the number and length of the buffers in the
JCL and the program listing for the job.
DCBBUFNO and DCBBUFL fields.
Handling buffering in the program and deleting the BFTEK=D
09A
operand in the DCB macro or DCB parameter of the DD state-
ment. Explanation: Global resource serialization encountered an error.
Then run the job step again. Note: The X'09A' abend code does not propagate to GQSCAN's
caller.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more The two low-order bytes of register 15 contain a hexadecimal func-
information. Search problem reporting data bases for a fix for the tion and reason code:
problem. If no fix exists, contact the IBM Support Center. Provide the Code Explanation
JCL and the program listing for the job.
46FA Indicates one of the following:
097 An internal error
Explanation: The error occurred during processing of a basic tele- A shortage of WTO buffer space
communications access method (BTAM) OPEN macro. The open See the programmer response for this return code.
routine required an additional entry in the device I/O directory.
4814 An error occurred in the Queue Merge processing when
However, the directory was already full. Since the last system start,
this system tried to rejoin the GRS ring.
the maximum number of device types has already been opened.
Normally, the maximum number of device types is 30. 4818 An error occurred in Queue Merge processing when this
system tried to rejoin the GRS ring.
Source: Teleprocessing
68CA An IXCMOD request returned a non-zero return code.
Programmer Response: Additional space in the device I/O direc-
GRS issues IXCMOD to change its XCF monitoring
tory can be provided by changing one statement in the read/write
interval.
routine. The statement following the one labeled IOD must be
changed. The duplication factor must be increased to correspond to 8108 There are no more pages available in GRS private
the number of different device types being used. The new read/write storage.
routine must be reassembled and link edited to SVCLIB.
8122-8126 An error occurred in storage manager allocation proc-
System Programmer Response: If the error recurs and the essing while trying to allocate a cell.
program is not in error, look at the messages in the job log for more
8221-8226 An error occurred in storage manager deallocation proc-
information. Search problem reporting data bases for a fix for the
essing while trying to deallocate a cell.
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job.
System Completion Codes SCC-55
09B 09E
A2xx ISGQSCNR, which is the GQSCAN service's functional Programmer Response: If the reason and function codes are
recovery routine, converted the ABEND. A2xx, the problem is with the GQSCAN macro. Respecify the
GQSCAN macro.
A220 An undefined error occurred during execution of the
GQSCAN service, which is the GQSCAN service routine. System Programmer Response: If the problem persists, search
The system saves the original completion code in reg- problem reporting data bases for a fix for the problem. If no fix
ister 2 and the original reason code in register 3. exists, contact the IBM Support Center. Provide the function and
reason codes, the logrec data set error record, and the dump. For
A22C An unexpected error occurred when the ISGQSCAN
the appropriate reason and function codes, provide a dump of the
information routine was activated to obtain requestor
GRS address space dumps for each system in the global resource
information from the service address space. GQSCAN
serialization complex. Provide all dumps taken by GRS recovery for
recovery will not percolate to the GQSCAN caller's
the ABEND.
recovery since retry is requested.
Others Internal error. IBM might request this information for
09B
diagnosis.
Explanation: An abnormal end occurred in IP PrintWay. This
Source: Global resource serialization
system completion code and the IP PrintWay abend reason code are
System Action: System processing continues. The system usually contained in either message ANFM102I or ANFM105I. See IBM IP
writes a logrec data set error record and issues an SVC dump. For PrintWay Guide for an explanation of the abend reason code.
reason codes X'4814' and X'4818', the system will attempt to force
Source: IP PrintWay
a dump on the system in the complex which was assisting with the
rejoin process. This dump will only be taken if the assisting system is Programmer Response: Respond as indicated for message
in the sysplex with the rejoining system and the assisting system is ANFM102I or ANFM105I.
at least at MVS/ESA SP5.1.0. Programmer Response: If the error recurs, search problem-
Operator Response: For some 09A abends, you should obtain a reporting data bases for a fix for the problem. If no fix exists, contact
dump of the GRS address space from each system in the global the IBM support center.
resource serialization complex. The IBM Support Center will request
the dumps for diagnosis. The following function and reason codes 09D
require a dump from each system in the complex:
Explanation: A PTRACE macro was issued requesting the creation
43yy of a trace table entry to be placed in the system trace table. A
44yy system trace service routine detected an error in the PTRACE
macro.
45yy
Register 15 contains a hexadecimal reason code that explains the
62yy error:
65yy Code Explanation
66yy 1151 Input register 1 of the PTRACE macro issuer contains an
67yy incorrect register range. Register 2 contains the incorrect
register range that was input in register 1.
6Ayy
1152 The parameter area of the PTRACE macro issuer contains
6Cyy
more than 1024 words of data to be traced. Register 2
C1yy contains the address of the user parameter area (input
E1yy register 1). Register 3 contains the number of words of
data to be traced from the user parameter area.
E3yy
Source: System trace
You do not need to obtain a dump for the codes above when yy is
one of the following: System Action: The system abnormally ends the task associated
with the program that issued the PTRACE macro.
45
90 Programmer Response: Correct the PTRACE macro. Run the job
B2 again.
B6
E0 09E
EC
Explanation: During processing of a system trace routine, the
FA
system detected an error.
FC
Register 15 contains a hexadecimal reason code that explains the
Programmer Response: Do one of the following:
error:
If mmff is 4808, 480C, or 4810, this is probably a user error.
Code Explanation
Correct the problem and resubmit the job.
0251 The system trace address space could not be created. The
If mmff is 46FA, check to see if the problem was caused by a
nonzero return code was placed in register 2. The reason
shortage of WTO buffer space. If not, contact the IBM Support
code was placed in register 3.
Center and provide the return code in register 2.
0252 The system trace function could not be initialized. The
If the problem persists, search problem reporting data bases for a fix
nonzero return code was placed in register 2.
for the problem. If no fix exists, contact the IBM Support Center.
SCC-56 OS/390 V2R8.0 MVS System Codes
09E 09E
0261 The ESTAE macro failed to establish a recovery environ- 2311 The system found an incorrect acronym in the system
ment. The nonzero return code from ESTAE was placed in trace option block (TOB). Register 2 contains the address
register 2. of the TOB. Register 3 contains the detected acronym.
0351 An error occurred while waiting for the master address 2312 The system found an incorrect level number in the system
space to complete initialization. A nonzero return code was trace option block (TOB). Register 2 contains the address
passed in register 15. A reason code was passed in reg- of the TOB. Register 3 contains the detected and expected
ister 0. The return code was placed in register 2. level numbers.
0361 The ESTAE macro failed to establish a recovery environ- 2313 The system found an incorrect acronym in a system trace
ment. The nonzero return code from ESTAE was placed in buffer vector table (TBVT). Register 2 contains the address
register 2. of the TBVT. Register 3 contains the detected acronym.
1211 The system detected an incorrect control block acronym. 2314 The system found an incorrect level number in a system
Register 2 contains the real address of the control block. trace buffer vector table (TBVT). Register 2 contains the
Register 3 contains the expected acronym. address of the TBVT. Register 3 contains the detected and
expected level numbers.
1212 The system detected an incorrect control block level
number. Register 2 contains the real address of the control 2401 The trace request could not be recognized. The specified
block. Register 3 contains the acronym of the control option is not SUSPEND, RESUME, or PSTART. The
block. Register 4 contains the detected and expected level request was received in register 1 and placed in register 2.
numbers.
2411 The system found an incorrect acronym in the system
2100 The request for a system trace was not issued in task trace option block (TOB). Register 2 contains the address
mode. of the TOB. Register 3 contains the detected acronym.
2101 The system trace request is incorrect because the option is 2412 The system found an incorrect level number in the system
not valid. The request is received in register 1 and placed trace option block (TOB). Register 2 contains the address
in register 2. of the TOB. Register 3 contains the detected and expected
level numbers.
2102 The trace request is incorrect because the request type is
not valid. The request is received in register 0 and placed 2413 The system found an incorrect acronym in a system trace
in register 2. buffer vector table (TBVT). Register 2 contains the address
of the TBVT. Register 3 contains the detected acronym.
2201 The trace request is incorrect for one of the following
reasons: 2414 The system found an incorrect level number in a system
trace buffer vector table (TBVT). Register 2 contains the
Register 0 did not contain the address of a physical
address of the TBVT. Register 3 contains the detected and
configuration communication area (PCCA) or
expected level numbers.
X'FFFFFFFF'.
2501 The system found an incorrect acronym in the system
The request type in register 1 was not TRACEON,
trace SNAPTRC parameter list (TRSN). Register 2 con-
TRACEOFF, or TRACEFIX.
tains the address of the TRSN. Register 3 contains the
The request input is received in registers 0 and 1 and the detected acronym.
detected request is placed in registers 2 and 3.
2502 The system found an incorrect level number in the system
2202 Trace requests conflict for one of the following reasons: trace SNAPTRC parameter list (TRSN). Register 2 con-
A single processor request specified a change in the tains the address of the TRSN. Register 3 contains the
trace options or number of buffers. detected and expected level numbers.
Both ON and OFF were requested for the AS, BR, or 2503 The system found an incorrect request type in the system
EX options. trace SNAPTRC parameter list (TRSN). The request type
is not one of the expected constants:
The reserved bits were not zero.
TRSNASFR
The request input is received in registers 0 and 1 and the
TRSNFREE
detected request is placed in registers 2 and 3.
TRSNSNAP
2211 The system found an incorrect acronym in the system TRSNTKFR
trace option block (TOB). Register 2 contains the address
Register 2 contains the address of the TRSN. Register 3
of the TOB. Register 3 contains the detected acronym.
contains the detected request type.
2212 The system found an incorrect level number in the system
2601 The system found an incorrect acronym in the system
trace option block (TOB). Register 2 contains the address
trace services parameter list (TRSP). Register 2 contains
of the TOB. Register 3 contains the detected and expected
the address of the TRSP. Register 3 contains the detected
level numbers.
acronym.
2301 The system found an incorrect acronym in the system
2602 The system found an incorrect level number in the system
trace services parameter list (TRSP). Register 2 contains
trace services parameter list (TRSP). Register 2 contains
the address of the TRSP. Register 3 contains the detected
the address of the TRSP. Register 3 contains the detected
acronym.
and expected level numbers.
2302 The system found an incorrect level number in the system
2701 The system found an incorrect acronym in the system
trace services parameter list (TRSP). Register 2 contains
trace services parameter list (TRSP). Register 2 contains
the address of the TRSP. Register 3 contains the detected
the address of the TRSP. Register 3 contains the detected
and expected level numbers.
acronym.
System Completion Codes SCC-57
09E 09E
2702 The system found an incorrect level number in the system 5102 The system found an incorrect level number in the system
trace services parameter list (TRSP). Register 2 contains trace table format request parameter list (TRFM). Register
the address of the TRSP. Register 3 contains the detected 2 contains the address of the TRFM. Register 3 contains
and expected level numbers. the detected and expected level numbers.
2801 The system found an incorrect acronym in the system 5151 The address of the current system trace table entry (TTE)
trace COPYTRC parameter list (TRCT). Register 2 con- is past the expected end of data in the buffer for the
tains the address of the TRCT. Register 3 contains the current processor. Register 2 contains the address of the
detected acronym. TTE. Register 3 contains the address of the expected end
of data. Register 4 contains the processor index into the
2802 The system found an incorrect level number in the system
trace formatter work area (TFWA).
trace COPYTRC parameter list (TRCT). Register 2 con-
tains the address of the TRCT. Register 3 contains the 5161 An ESTAE macro issued to establish a recovery environ-
detected and expected level numbers. ment failed. Register 2 contains the ESTAE return code.
2811 The system found an incorrect acronym in a system trace 5201 The system found an incorrect acronym in the trace for-
table snapshot copy header (TTCH). Register 2 contains matter work area (TFWA). Register 2 contains the address
the address of the TTCH. Register 3 contains the detected of the TFWA. Register 3 contains the detected acronym.
acronym.
5202 The system found an incorrect level number in the trace
2812 The system found an incorrect level number in a system formatter work area (TFWA). Register 2 contains the
trace table snapshot copy header (TTCH). Register 2 con- address of the TFWA. Register 3 contains the detected
tains the address of the TTCH. Register 3 contains the and expected level numbers.
detected and expected level numbers.
5301 The system found an incorrect acronym in the trace for-
2901 The system found an incorrect acronym in the system matter work area (TFWA). Register 2 contains the address
trace SNAPTRC parameter list (TRSN). Register 2 con- of the TFWA. Register 3 contains the detected acronym.
tains the address of the TRSN. Register 3 contains the
5302 The system found an incorrect level number in the trace
detected acronym.
formatter work area (TFWA). Register 2 contains the
2902 The system found an incorrect level number in the system address of the TFWA. Register 3 contains the detected
trace SNAPTRC parameter list (TRSN). Register 2 con- and expected level numbers.
tains the address of the TRSN. Register 3 contains the
5351 The system has determined that no valid ASID filtering
detected and expected level numbers.
options were specified. Register 2 contains the address of
2911 The system found an incorrect acronym in a system trace the TFWA. Register 3 contains the contents of
table snapshot copy header (TTCH). Register 2 contains TFWAFLG1.
the address of the TTCH. Register 3 contains the detected
5401 The system found an incorrect acronym in the trace for-
acronym.
matter work area (TFWA). Register 2 contains the address
2912 The system found an incorrect level number in a system of the TFWA. Register 3 contains the detected acronym.
trace table snapshot copy header (TTCH). Register 2 con-
5402 The system found an incorrect level number in the trace
tains the address of the TTCH. Register 3 contains the
formatter work area (TFWA). Register 2 contains the
detected and expected level numbers.
address of the TFWA. Register 3 contains the detected
4101 The system found an incorrect acronym in a parameter. and expected level numbers.
Register 3 contains the control block address. Register 4
5501 The system found an incorrect acronym in the trace for-
contains the expected acronym. Register 5 contains the
matter work area (TFWA). Register 2 contains the address
detected acronym.
of the TFWA. Register 3 contains the detected acronym.
4102 The system found an incorrect level number in a param-
5502 The system found an incorrect level number in the trace
eter. Register 3 contains the control block address. Reg-
formatter work area (TFWA). Register 2 contains the
ister 4 contains the acronym of the control block. Register
address of the TFWA. Register 3 contains the detected
5 contains the detected and expected level numbers.
and expected level numbers.
4201 The system found an incorrect acronym in a parameter.
5601 The system found an incorrect acronym in the trace for-
Register 3 contains the control block address. Register 4
matter work area (TFWA). Register 2 contains the address
contains the expected acronym. Register 5 contains the
of the TFWA. Register 3 contains the detected acronym.
detected acronym.
5602 The system found an incorrect level number in the trace
4202 The system found an incorrect level number in a param-
formatter work area (TFWA). Register 2 contains the
eter. Register 3 contains the control block address. Reg-
address of the TFWA. Register 3 contains the detected
ister 4 contains the acronym of the control block. Register
and expected level numbers.
5 contains the detected and expected level numbers.
5701 The system found an incorrect acronym in the trace for-
4203 The system detected an incorrect parameter. Register 3
matter work area (TFWA). Register 2 contains the address
contains the control block address. Register 4 contains the
of the TFWA. Register 3 contains the detected acronym.
acronym of the incorrect control block. Register 5 contains
the offset into the control block of the error. Register 6 5702 The system found an incorrect level number in the trace
contains the content of the incorrect field. formatter work area (TFWA). Register 2 contains the
address of the TFWA. Register 3 contains the detected
5101 The system found an incorrect acronym in the system
and expected level numbers.
trace table format request parameter list (TRFM). Register
2 contains the address of the TRFM. Register 3 contains 5703 The system requested that the work buffer for a processor
the detected acronym. be refilled while the processor's end of trace data bit was
turned on. Register 2 contains the address of the trace for-
SCC-58 OS/390 V2R8.0 MVS System Codes
09E 09E
matter work area (TFWA). Register 3 contains the 6101 The system found an incorrect acronym in the trace for-
processor index into the TFWA. Register 4 contains the matter work area (TFWA). Register 2 contains the address
physical address of the processor. of the TFWA. Register 3 contains the detected acronym.
5801 The system found an incorrect acronym in the trace for- 6102 The system found an incorrect level number in the trace
matter work area (TFWA). Register 2 contains the address formatter work area (TFWA). Register 2 contains the
of the TFWA. Register 3 contains the detected acronym. address of the TFWA. Register 3 contains the detected
and expected level numbers.
5802 The system found an incorrect level number in the trace
formatter work area (TFWA). Register 2 contains the 6301 The system found an incorrect acronym in the trace for-
address of the TFWA. Register 3 contains the detected matter work area (TFWA). Register 2 contains the address
and expected level numbers. of the TFWA. Register 3 contains the detected acronym.
5901 The system found an incorrect acronym in the trace for- 6302 The system found an incorrect level number in the trace
matter work area (TFWA). Register 2 contains the address formatter work area (TFWA). Register 2 contains the
of the TFWA. Register 3 contains the detected acronym. address of the TFWA. Register 3 contains the detected
and expected level numbers.
5902 The system found an incorrect level number in the trace
formatter work area (TFWA). Register 2 contains the 6401 The system found an incorrect acronym in the trace for-
address of the TFWA. Register 3 contains the detected matter work area (TFWA). Register 2 contains the address
and expected level numbers. of the TFWA. Register 3 contains the detected acronym.
5A01 The system found an incorrect acronym in the trace for- 6402 The system found an incorrect level number in the trace
matter work area (TFWA). Register 2 contains the address formatter work area (TFWA). Register 2 contains the
of the TFWA. Register 3 contains the detected acronym. address of the TFWA. Register 3 contains the detected
and expected level numbers.
5A02 The system found an incorrect level number in the trace
formatter work area (TFWA). Register 2 contains the 6501 The system found an incorrect acronym in the trace for-
address of the TFWA. Register 3 contains the detected matter work area (TFWA). Register 2 contains the address
and expected level numbers. of the TFWA. Register 3 contains the detected acronym.
5B01 The system found an incorrect acronym in the trace for- 6502 The system found an incorrect level number in the trace
matter work area (TFWA). Register 2 contains the address formatter work area (TFWA). Register 2 contains the
of the TFWA. Register 3 contains the detected acronym. address of the TFWA. Register 3 contains the detected
and expected level numbers.
5B02 The system found an incorrect level number in the trace
formatter work area (TFWA). Register 2 contains the 6601 The system found an incorrect acronym in the trace for-
address of the TFWA. Register 3 contains the detected matter work area (TFWA). Register 2 contains the address
and expected level numbers. of the TFWA. Register 3 contains the detected acronym.
5C01 The system found an incorrect acronym in the trace for- 6602 The system found an incorrect level number in the trace
matter work area (TFWA). Register 2 contains the address formatter work area (TFWA). Register 2 contains the
of the TFWA. Register 3 contains the detected acronym. address of the TFWA. Register 3 contains the detected
and expected level numbers.
5C02 The system found an incorrect level number in the trace
formatter work area (TFWA). Register 2 contains the 6701 The system found an incorrect acronym in the trace for-
address of the TFWA. Register 3 contains the detected matter work area (TFWA). Register 2 contains the address
and expected level numbers. of the TFWA. Register 3 contains the detected acronym.
5D01 The system found an incorrect acronym in the trace for- 6702 The system found an incorrect level number in the trace
matter work area (TFWA). Register 2 contains the address formatter work area (TFWA). Register 2 contains the
of the TFWA. Register 3 contains the detected acronym. address of the TFWA. Register 3 contains the detected
and expected level numbers.
5D02 The system found an incorrect level number in the trace
formatter work area (TFWA). Register 2 contains the 6801 Incorrect TFWA parameter acronym.
address of the TFWA. Register 3 contains the detected
6802 Incorrect TFWA parameter level number.
and expected level numbers.
7451 The system found an incorrect acronym in the system
5E01 The system found an incorrect acronym in the trace for-
trace vector table (TRVT). A CALLRTM TYPE=MEMTERM
matter work area (TFWA). Register 2 contains the address
had been issued for the trace address space.
of the TFWA. Register 3 contains the detected acronym.
7452 The system found an incorrect level number in the system
5E02 The system found an incorrect level number in the trace
trace vector table (TRVT). A CALLRTM TYPE=MEMTERM
formatter work area (TFWA). Register 2 contains the
had been issued for the trace address space.
address of the TFWA. Register 3 contains the detected
and expected level numbers. 7461 The system found an incorrect acronym in the system
trace option block (TOB). A CALLRTM TYPE=MEMTERM
5F01 The system found an incorrect acronym in the trace for-
had been issued for the trace address space.
matter work area (TFWA). Register 2 contains the address
of the TFWA. Register 3 contains the detected acronym. 7462 The system found an incorrect level number in the system
trace option block (TOB). A CALLRTM TYPE=MEMTERM
5F02 The system found an incorrect level number in the trace
had been issued for the trace address space.
formatter work area (TFWA). Register 2 contains the
address of the TFWA. Register 3 contains the detected 7470 The system found errors in the system trace control blocks
and expected level numbers. or queues. The functional recovery routine (FRR)
IEAVETRR, entry point IEAVETFR, records the errors.
System Completion Codes SCC-59
09F 0A1
7501 The system found an incorrect acronym in the system For reason code X'00', X'04', X'1C', or X'2C', ensure that
trace services parameter list (TRSP). Register 2 contains the program issues vector instructions in the proper mode.
the address of the TRSP. Register 3 contains the detected
For reason code X'08', a program that uses a Vector Facility
acronym.
should not specify affinity requirements.
7502 The system found an incorrect level number in the system
System Programmer Response: Do the following:
trace services parameter list (TRSP). Register 2 contains
the address of the TRSP. Register 3 contains the detected 1. If a logrec data set error record is not produced with the abend,
and expected level numbers. ask the operator to set a SLIP trap to obtain an SVC dump.
Source: System trace 2. Use the program status word (PSW) at the time of error to iden-
tify the module that issued the vector instruction.
System Action: The system abnormally ends the current task. The
system may abnormally end the trace address space. The system For an installation-provided module, continue diagnosis with
writes a logrec data set error record and a dump. the module.
The system may issue message IEA133E. For an IBM module, search problem reporting data bases
for a fix for the problem. If no fix exists, contact the compo-
Operator Response: Enter the TRACE command to restart the
nent group associated with this module at the IBM Support
trace address space. Notify the system programmer.
Center. Provide, if available, the SVC dump and the logrec
System Programmer Response: If the error recurs, search data set error record.
problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the logrec data set 0A0
error record, the dump, and all printed output and output data sets
related to the problem. Explanation: During initial program load (IPL), an error occurred
while the system was starting the master scheduler. Register 15 con-
tains a hexadecimal reason code:
09F
Code Explanation
Explanation: A program issued a vector instruction, but the system
cannot create the proper environment for the vector operation. The 01 The system detected a converter, interpreter, or system
program is running under a task control block (TCB) or service error during master scheduler initialization.
request block (SRB). A hexadecimal reason code in register 15 02 The system detected an allocation error, an OPEN catalog
explains the error: error, or a locked catalog error during master scheduler
Code Explanation initialization.
00 The program issued the vector operation in SRB mode. 03 The system could not obtain a special region for the
master scheduler.
04 The program issued the vector operation while disabled.
Source: Initiator/terminator
08 None of the online processors with an attached Vector
Facility met the task's affinity requirements. System Action: The system does not start the master scheduler.
System initialization ends. The system writes an SVC dump. The
0C The program cannot create the vector environment. The
system may issue message IEE479W.
vector second level interrupt handler (SLIH) detects the
error. Operator Response: If the system issues message IEE479W, see
the operator response for message IEE479W. Otherwise, notify the
10 The vector SLIH failed due to a system error.
system programmer.
14 The system encounters a vector environment that is not
System Programmer Response: Examine the SVC dump, looking
valid.
at the master trace table for messages which will pinpoint the
18 A machine check in the Vector Facility causes the vector problem with the JCL (for RC=01) or with allocation (for RC=02). If
status for a task to be lost. the master JCL data set (MSTJCLxx) was updated recently, check
that the changes are correct. The messages associated with the
1C The issuing task holds a local lock.
processing of MSTJCLxx are sent to the console if you specify the L
20 The system encounters a secondary task control block option (,L) on the MSTRJCL system parameter. Respond to mes-
(STCB) that is not valid. sages issued by the converter, interpreter, or allocation.
24 No Vector Facility exists in the complex. If the problem recurs and if the program is not in error, search
28 Resource Access Control Facility (RACF) has indicated problem reporting data bases for a fix for the problem. If no fix
that the user is not authorized to use the Vector Facility. exists, contact the IBM Support Center. Provide the dump.
2C The program issued the vector instruction and had
established enabled, unlocked task (EUT) mode func- 0A1
tional recovery routines (FRR). Explanation: An incorrect condition was detected by the Graphics
Source: Supervisor control Access Method/System Product (GAM/SP) OPEN executor routine,
IGG0193Y. The error occurred in either GAM/SP or the operating
System Action: The system abnormally ends the program that system.
issued the vector instruction. The system may write an logrec data
set error record. Source: DFSMSdfp
Operator Response: If the system programmer asks for an SVC System Action: A message appears on the system console that
dump, set the following SLIP trap: identifies the cause of the error; and GAM/SP produces a dump on
the system dump data set.
SLIP SET,COMP=ð9F,ACTION=SVCD,END
Programmer Response: Do the following:
Programmer Response: Do the following:
SCC-60 OS/390 V2R8.0 MVS System Codes
0A2 0A7
1. Check for messages identifying the cause of the error. If these Source: DFSMSdfp
are GAM/SP messages, (that is, the message number is of the
System Action: A message appears on the system console,
form ‘GABnnn’), they are described in IBM Graphics Access
accompanied by a reason code identifying the area of processing in
Method/System Product: Messages and Codes. which the error occurred. In addition, GAM/SP writes a record to the
2. Get a listing of the system dump. logrec data set data set and produces a dump on the system dump
data set.
3. Contact your programming support personnel.
Programmer Response: You should take the following actions: Do
0A2 the following:
Explanation: An incorrect condition was detected by the Graphics 1. Check for messages identifying the cause of the error. If these
Access Method/System Product (GAM/SP) CLOSE executor routine, are GAM/SP messages, (that is, the message number is of the
IGG0203Y. The error occurred in either GAM/SP or the operating form ‘GABnnn’), they are described in IBM Graphics Access
system. Method/System Product: Messages and Codes.
Source: DFSMSdfp 2. Get a listing of the system dump.
System Action: A message appears on the system console that 3. Contact your programming support personnel.
identifies the cause of the error and GAM/SP produces a dump on
the system dump data set. 0A5
Programmer Response: Do the following: Explanation: A program check or abnormal end occurred within the
Graphics Access Method/System Product (GAM/SP) attention
1. Check for messages identifying the cause of the error. If these
handler module, IGG019OE. The recovery routine for IGG019OE
are GAM/SP messages, (that is, the message number is of the
determined that the problem was caused by an application error.
form ‘GABnnn’), they are described in IBM Graphics Access
Method/System Product: Messages and Codes. Source: DFSMSdfp
2. Get a listing of the system dump. System Action: Message GAB333 appears on the system console
and diagnostic data is provided. The message and the diagnostic
3. Contact your programming support personnel.
data are described in IBM Graphics Access Method/System Product:
Messages and Codes.
0A3
Programmer Response: Check for messages identifying the cause
Explanation: An error was detected in the Graphics Access of the problem. Using the message and other diagnostic information,
Method/System Product (GAM/SP) attention handler module, correct the application program. IBM Graphics Access
IGG019OE. The error may have originated in the GAM/SP OPEN Method/System Product: Messages and Codes contains information
executor, IGG0193Y. It could also be caused by modules IGG019OE on application recovery from this problem.
and IGG0193Y being at inconsistent maintenance levels.
Source: DFSMSdfp 0A6
System Action: A message appears on the system console that Explanation: An abnormal end occurred in the page printer com-
describes the error. In addition, GAM/SP writes a record to the munications component (PPCC). The print services facility (PSF)
logrec data set data set and produces a dump on the system dump ESTAE routines determine whether PSF can be restarted, but the
data set. recovery end manager (RTM) does not request a PSF restart.
Programmer Response: Do the following: Source: DFSMSdfp
1. Check for messages identifying the cause of the error. If these Programmer Response: Respond as indicated for message
are GAM/SP messages, (that is, the message number is of the APS050I or APS055I.
form ‘GABnnn’), they are described in IBM Graphics Access
System Programmer Response: If the error recurs and the
Method/System Product: Messages and Codes.
program is not in error, search problem reporting data bases for a fix
2. Check the module identifiers and PTF levels for modules for the problem. If no fix exists, contact the IBM Support Center.
IGG019OE and IGG0193Y.
3. Get a listing of the system dump. 0A7
4. Contact your programming support personnel. Explanation: During VTAM HALT QUICK, VTAM HALT, VTAM
HALT CANCEL, or VTAM abnormal termination processing, VTAM
0A4 found that no storage was available to schedule a TPEND exit for an
access method control block (ACB) opened by a user’s application
Explanation: An error occurred either in the Graphics Access
program or VTAM subtask. or the ACB storage was freed.
Method/System Product (GAM/SP) or in the operating system.
This abend code is also issued during VTAM HALT CANCEL or
This completion code is issued when:
VTAM abnormal termination processing if a TPEND exit for an ACB
1. A program check or abnormal end occurs in the Graphics does not exist, the ACB was not valid, or the ACB storage was
Access Method/System Product (GAM/SP) attention handler freed.
module.
Source: Teleprocessing
2. The GAM/SP attention handler module detects an incorrect con-
System Action: The caller's task abnormally ends.
dition.
System Completion Codes SCC-61
0A8 0A8
command, you must modify the VTAM start options file
0A8
(ATCSTRxx) and restart VTAM to use the new start option.
Explanation: Virtual telecommunications access method (VTAM)
– Use the Estimating Storage for VTAM diskette to determine
detected an error while processing a user's application program. The
the storage requirements for VTAM.
two low-order bytes of register 15 contain a hexadecimal reason
code that explains the error. – Refer to the OS/390 SecureWay Communications Server:
SNA Resource Definition Reference for a description of
Code Explanation
VTAM start options.
2101 A VTAM validity check of the user's request parameter
– Refer to the OS/390 SecureWay Communications Server:
list (RPL) failed because the RPL does not have the
SNA Operation for information about the DISPLAY BFRUSE
same protection key as the application program's task
command, the DISPLAY STORUSE command, and the
control block (TCB).
MODIFY VTAMOPTS command.
7001 The user's RPL control block, or event control block
– Refer to the OS/390 SecureWay Communications Server:
(ECB) is incorrect.
SNA Network Implementation for an explanation and
7002 A VTAM request for storage failed. description of buffer pools, and for general information
7003 The pointer to the request parameter list (RPL) is not about buffer pool specification and allocation.
valid. – See OS/390 SecureWay Communications Server: SNA
7004 An ACB OPEN failed due to an access method control Diagnosis V1 Techniques and Procedures for information
block (ACB) address that is not valid. about analyzing dumps and for information about analyzing
storage using the VIT analysis tool if external trace is active.
7005 Storage pointed to by RPLAREA is not valid.
For reason code 7004, verify that the ACB pointer is valid and
7006 Storage pointed to by RPLAAREA is not valid. check the storage to be sure it resides in the application's
7007 The request parameter list (RPL) is not valid. Unable to storage protection key.
find ACB. For reason code 700D, check the application program.
7008 RPL6 pointed to by RPLAAREA is not valid. For reason code FC01, save the dump for problem determi-
7009 Node initialization block(s) (NIB) pointed to by the nation.
request parameter list (RPL) is not valid. For reason code FF01:
700A Model Terminal Support (MTS) data pointed to by node – If you have access to IBMLink, search for known problems
initialization block (NIB) is not valid. in this area. If no applicable matches are found, report the
700B Restore parameter list pointed to by node initialization problem to IBM by using the electronic technical report
block (NIB) is not valid. (ETR) option on IBMLink.
700C Application-supplied dial parameters storage pointed to – If you do not have access to IBMLink, report the problem to
by node initialization block (NIB) is not valid. the IBM software support center.
700D Bind area pointed to by node initialization block (NIB) is System Programmer Response: Do the following:
not valid. See the reason code in register 15. Register 15 and its contents
FC01 Network management interface abend. can be found in the SDWA or by issuing the IPCS VERBEXIT
LOGDATA subcommand. The generalized trace facility (GTF)
FC02 VTAM agent user's read queue PAB had a storage
trace record, SVC trace (comprehensive), also displays the con-
failure.
tents of register 15.
FF01 A session awareness (SAW) data buffer that is not valid
If MSGLEVEL=(1,1) was not specified in the JOB statement,
was passed to VTAM's data space services release
specify it and rerun the job.
routine.
Make sure that the failing job step includes the SYSABEND DD
Source: Teleprocessing
statement.
System Action: The task abnormally ends. The system may issue
Collect the following for the failing job:
a dump.
– Console log from the primary or remote console.
Programmer Response: This is probably a user error. Do one of
– Job stream associated with the job.
the following:
– All associated output.
For reason codes 2101, 7001, 7003, 7005, 7006, 7007, 7008, – Program listing for the job.
7009, 700A, 700B, and 700C, verify that the RPL and ECB – The dump, if one is issued.
pointers are correct, and execute the job step again. – Linkage editor or loader map.
For reason code 7002, verify that the operator entered the buffer If the error recurs and the program is not in error, look at the mes-
pool or CSA start options as specified in the start procedures. sages in the job log for more information. Search problem reporting
Increase storage as required. For insufficient storage errors, you data bases for a fix for the problem. If no fix exists, contact the IBM
might want to redefine your buffer pool or CSA limits. If the start Support Center. Provide the JCL, the linkage editor output, the
option cannot be modified using the MODIFY VTAMOPTS program listing for the job, and all printed output and output data
sets related to the problem.
SCC-62 OS/390 V2R8.0 MVS System Codes
0A9 0A9
7075 A VTFREE was issued for a previously freed
0A9
storage area.
Explanation: One of the following occurred:
7076 C/370 code ran out of ISA storage for autodata.
If this abend is accompanied by a zero value in register 15, a
7077 Storage management header has been overlaid.
VTAM HALT command has been successfully completed.
7078 The last word in the buffer being RELSTOREd is
If register 15 is not zero, an error has occurred during the exe-
not BFPPCBA (fence corrupted).
cution of a VTAM module. The contents of the 2 low-order bytes
of register 15 indicate the cause of the error: 7079 Header in REQSTORE buffer being allocated is not
valid (no match on fence word).
Code Explanation
707A A FREESTOR was issued for a previously freed
0000 A VTAM HALT CANCEL has been successfully
storage area.
completed.
CD01 CDRM error detected.
10F1 The ABEND was issued by VTAM’s retry functional
recovery routine (FRR) to pass the original abend to CF01 An error was found and corrected in a CDRM minor
the next recovery routine (if any) associated with the node during CDRM major node deactivation.
task control block (TCB). See the original abend, FA01 DS process error.
which was recorded in SYS1.LOGREC and appears
just prior to the supervisor call (SVC) dump that was FA02 The DS disk I/O subtask has abended due to insuffi-
generated and indicated by reason code 10F1. cient storage. The checkpoint has been disabled.
2101 The request parameter list (RPL) is not in the FA09 Initialization error.
correct storage key. FE02 A pool has been defined by the POOLDEF macro
6901 Error in CP-CP sessions processing. Missing with an unacceptable length or the lengths in a
element on list pointed to by variable-length pool were not defined in ascending
AND_BOTH_CP_STATUS_STORAGE_PTR. order.
6902 Error in CP-CP sessions processing. Missing FF02 A FREEBLK macro returned a nonzero return code.
element on list pointed to by FF03 A utility module detected a function code that is not
AND_CW_CP_STATUS_STORAGE_PTR. valid.
6903 Error in CP-CP sessions processing. Missing FF04 A request, response, or vector was not defined to
element on list pointed to by the RU information table.
AND_CL_CP_STATUS_STORAGE_PTR.
FF05 The main entry for the extended router was invoked
7002 Storage was not available to drive a user exit. but processing was already occurring within a
7005 VTAM was unable to restore its registers from the CALLSSCP environment.
RPH after a user exit routine returned to VTAM. FF06 No sense code was set, but one should have been.
7006 CPPROC was unable to obtain adequate storage FF07 The CPCBURC field contained no format, but the
from the vary work area (VWA). response has a format.
7007 TPEXIT code was entered while VTAM was holding FF08 The limit of topology elements (SWBVDCVD) has
a lock. been exceeded. D3/D4 vectors for elements
7008 A CPWAIT was attempted with an event ID length exceeding limit were not built.
greater than EIDMAX. FF09 The VWA area in use is too small to satisfy this
7009 A message module needs more vary work area request.
(VWA) storage within the component recovery area FF10 A request was made to queue a response to a
(CRA) than is currently available. process anchor block (PAB).
700F Encountered a session awareness block (SAB) that FF11 A suspend code that is not valid was passed to
was not valid. suspend.
7010 A GETRDTE or RDTFIND for a resource failed FF12 A SENDER invocation that is not valid was made.
because the resource definition table entry (RDTE)
FF13 An unexpected value was received. The value may
chain has been corrupted.
be valid in another context.
7012 A lock's count shows no user is holding the lock, but
FF14 An unexpected finite state machine (FSM) state was
the lock is held.
encountered.
7013 Lock hierarchy violation.
FF15 An unexpected field value was encountered for an
7014 TSLINK found the component recovery area (CRA) enumerated type.
too small to hold all of the data.
FF16 An unexpected control block was received as input.
7015 A transmission subsystem control block (TSCB) was
FF17 A session information block (SIB) or SIB address
encountered that is not valid.
that is not valid was passed to FREESIB.
7071 A RELSTORE was issued for a previously freed
FF18 The SENDER buffer area is not large enough.
buffer.
FF19 The DETERMINER routine returned results that are
7072 A VTFREE was issued for a previously freed area.
not valid.
7074 A VTFREE was issued for a buffer that is not valid.
System Completion Codes SCC-63
0AA 0AB
FF20 The BUILD routine returned results that are not
0AA
valid.
Explanation: An abend condition occurred during processing of
FF22 SRTDEL failed.
virtual telecommunications access method (VTAM). VTAM functional
FF25 Secondary Access Point (SAP) table overflow. recovery routines (FRRs) were unable to associate the failure with
FF26 HPRCTL was issued with the TOKEN option and any particular task control block (TCB) in the address space.
the value passed was not valid. Source: Teleprocessing
FF99 Indicates that a FFST probe was tripped. Console System Action: The system abnormally ends all the tasks in the
messages with prefix EPW will be issued by FFST address space.
to provide information about the probe trip. See
Programmer Response:
OS/390 SecureWay Communications Server: SNA
Diagnosis V1 Techniques and Procedures for a If MSGLEVEL=(1,1) was not specified in the JOB statement,
description of FFST probes. specify it and rerun the job.
Source: Teleprocessing Save the console log from the primary console. For systems
with remote consoles, save the remote console log. In systems
System Action: The task that initiated the VTAM request abnor-
with multiple-console support (MCS), save a copy of the hard
mally ends.
copy log.
Programmer Response: Do the following:
Make sure that the failing job step includes the SYSABEND DD
If MSGLEVEL=(1,1) was not specified in the JOB statement, statement.
specify it and rerun the job.
Save all the associated output.
Save the console log from the primary console. For systems
Save the dump.
with remote consoles, save the remote console log. For systems
with multiple-console support (MCS), save a copy of the hard Have the linkage editor/loader map available.
copy log. System Programmer Response: If the error recurs and an
Save the job stream associated with the job. installation-provided program is not in error, look at the messages in
the job log for more information. Search problem reporting data
Make sure that the failing job step includes the:
bases for a fix for the problem. If no fix exists, contact the IBM
1. SYSABEND DD statement Support Center. Provide the linkage editor and all printed output and
2. SYSUDUMP DD statement. output data sets related to the problem.
Save all the associated output.
Save the dump. 0AB
Execute the EREP service aid to dump the LOGREC file, and Explanation: The error occurred while TSO/VTAM was in operation
save the resulting output. For MSS, execute the following and a VTIOC module was processing a VTAM macro. See the
program to dump the LOGREC file: VTAM Messages and Codes manual or the VTAM Diagnosis Guide
for additional information.
1. Service aid IFCISDA0
2. Program ISDASDAO with the DETAIL(ALL) parameter. This error is usually due to a storage problem with the LPBUF or
CRPL buffers.
If register 15 is 0015, take the following actions to try to deter-
mine the cause of the TSCB integrity loss: The two low-order bytes of register 15 contain a hexadecimal reason
code that explains the error:
1. Save the dump.
2. If VTAM internal trace is running MODE=EXT, save this Code Explanation
trace. 0101 The terminal-input manager for LU1 (for example, IBM
Note: The default trace internal options may not be 3767 and IBM 3770 terminals) encountered an unrecov-
enough to resolve this problem. All options but erable error while executing a VTAM macro instruction
LOCK, with a trace table of at least SIZE=200, may that uses a request parameter list (RPL).
be required. 0102 The terminal-output manager for LU1 (for example, IBM
3767 and IBM 3770 terminals) encountered an unrecov-
System Programmer Response: If the error recurs and an erable error while executing a VTAM macro instruction
installation-provided program is not in error, look at the messages in that uses an RPL.
the job log for more information. Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM 0103 The terminal-input manager for LU0 and LU2 (for
Support Center. Provide the SYSOUT output for the job, the logrec example, IBM 3270 SNA terminals) encountered an
data set error record, and all printed output and output data sets unrecoverable error while executing a VTAM macro
related to the problem. instruction that uses an RPL.
0104 The terminal-output manager for LU0 and LU2 (for
example, IBM 3270 SNA terminals) encountered an
unrecoverable error while executing a VTAM macro that
uses an RPL.
0105 The VTIOC LOSTERM exit routine encountered an error
during execution of a SNA BIND or UNBIND command
that used an RPL.
SCC-64 OS/390 V2R8.0 MVS System Codes
0AC 0AD
0201 An application ID problem was encountered during exe- 34 The user-interface subtask abnormally terminated and
cution of a VTAM OPEN macro. The error occurred was unable to recover.
during initialization of a TSO/VTAM user-address space.
38 The console-communication subtask abnormally termi-
0202 An error occurred during execution of a VTAM OPEN nated and was unable to recover.
macro. The ERROR field of the ACB indicates the
Source: Teleprocessing
problem.
System Action: The system abnormally ends TCAS.
0203 An error occurred during execution of a VTAM CLOSE
macro. The code in the ERROR field of the ACB is Operator Response: Reply ‘DUMP’ to the TCAS abnormal end
X'42', indicating that the ACB has been closed, but a message IKT012D to obtain a dump.
VTAM error has prevented the successful disconnection Programmer Response: Do the following:
of one or more TSO terminals.
Save the console log from the primary console. For systems
Source: Teleprocessing with remote consoles, save the remote console log. For systems
System Action: The terminal session in which the error occurred with multiple-console support (MCS), save a copy of the hard
ends. copy log.
Programmer Response: Do the following: Save the system output (SYSOUT) associated with the job.
Save the console log from the primary console. For systems Save all the associated output.
with remote consoles, save the remote console log. For systems Save the dump.
with multiple-console support (MCS), save a copy of the hard
Print the associated SVC dump data set, using IPCS. See
copy log.
OS/390 SecureWay Communications Server: SNA Diagnosis V1
Save all the associated output. Techniques and Procedures for information about IPCS.
Save the dump.
Execute the EREP service aid to dump the LOGREC file, and 0AD
save the resulting output. For MSS, execute the following Explanation: An error occurred while Time Sharing Option/ Virtual
program to dump the LOGREC file: Telecommunications Access Method (TSO/VTAM) time sharing was
1. Service aid IFCISDA0 in operation. VTAM terminal I/O coordinator's (VTIOC) queue
2. Program ISDASDAO with the DETAIL(ALL) parameter. manager was executing a GETCELL or FREECELL macro.
Have the linkage editor/loader map available. The two low-order bytes (hexadecimal) of register 15 indicate the
cause of the error:
System Programmer Response: If the error recurs and an
installation-provided program is not in error, look at the messages in Contents Explanation
the job log for more information. Search problem reporting data 0108 The cell address supplied to the FREECELL macro
bases for a fix for the problem. If no fix exists, contact the IBM instruction was incorrect.
Support Center. Provide the logrec data set error record, the linkage
010C No cell pool existed for the FREECELL request.
editor output. and all printed output and output data sets related to
the problem. 0110 An incorrect cell pool ID was specified for the
FREECELL request.
0AC 020C No cell pool existed for the GETCELL request.
Explanation: The terminal control address space (TCAS) was 0210 An incorrect cell pool ID was specified for the GETCELL
unable to continue its normal processing due to an error. The two request.
low-order bytes of register 15 and TCAS work area (TWAR) field
Source: Time Sharing Option Extensions (TSO/E)
TWARSON both contain the hexadecimal reason code that indicates
the cause of the error: System Action: The queue manager ends abnormally, and the ter-
minal session in which the error occurred ends. The system writes a
Code Explanation
logrec data set error record and an ABEND dump.
00 A STOP command was entered.
Programmer Response:
04 A START command that is not valid was entered.
Save the console log from the primary console. For systems
10 The TCAS main task was unable to attach the VTAM with remote consoles, save the remote console log. In systems
interface subtask. with multiple-console support (MCS), save a copy of the hard
copy log.
14 The TCAS main task was unable to attach the user-
interface subtask. Save the program listing associated with the job.
18 The TCAS main task was unable to attach the console- Execute the EREP service aid to dump the LOGREC file, and
communication subtask. save the resulting output. For MSS, execute the following
program to dump the LOGREC file:
1C TCAS was unable to obtain storage for the TCAS table
(TCAST) in the common service area (CSA). 1. Service aid IFCISDA0
2. Program ISDASDAO with the DETAIL(ALL) parameter.
20 The TCAS main task abnormally terminated and was
unable to recover. Have the linkage editor/loader map available.
30 The VTAM interface subtask abnormally terminated and Print the associated SVC dump data set, using IPCS. See
was unable to recover. OS/390 SecureWay Communications Server: SNA Diagnosis V1
Techniques and Procedures for information about IPCS.
System Completion Codes SCC-65
0AE 0B0
successfully selected a name for the spool file and the
0AE
dynamic allocation SVC successfully allocated the spool
Explanation: The system cannot purge a completed I/O request. file. Reason code 0085 is associated with message
Source: Input/output supervisor (IOS) INMR133I.
System Action: The system abnormally ends all tasks in the 0086 The RECEIVE command attempted to deallocate a data
address space where the system was waiting to purge the I/O set using SVC 99, and the unallocation failed. The data
request. set was a JES input file or was specified by an INDA-
TASET or INDSNAME keyword. Reason code 0086 is
System Programmer Response: Search problem reporting data associated with message INMR134I.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. 0089 The RECEIVE command encountered an error while
attempting to end the external writer interface with JES.
After all files have been processed or after a unrecover-
0AF able error, the RECEIVE command invokes the process
Explanation: The Time Sharing Option Extensions (TSO/E) interac- sysout subsystem interface, specifying that this is the
tive data transmission facility detected a system error during the final call to the subsystem interface. The subsystem
processing of a TRANSMIT or RECEIVE command. Register 15 con- returned a nonzero return code indicating an error.
tains a reason code: Reason code 0089 is associated with message
INMR137I.
Code Explanation
009C The TRANSMIT or RECEIVE command processor
0025 The RECEIVE command encountered an error while
received an unknown return code from the module
invoking the Job Entry Subsystem (JES) interface.
IKJSMS1. The reason code 009C is associated with
The RECEIVE command was issued to determine if any message INMC156I.
Interactive Data Transmission Facility files were avail-
00CC The TRANSMIT command processor encountered an
able for you to receive. The JES subsystem request was
error while opening the JES output file. Reason code
not successful. Reason code 0025 is associated with
00CC is associated with message INMX204I.
message INMR037I.
00D2 The TRANSMIT command processor encountered an
002A The TRANSMIT command attempted to allocate the
error while opening the output data set. Reason code
SYSPRINT message file for IEBCOPY using SVC 99,
00D2 is associated with message INMX210I.
and the allocation failed. The SYSPRINT message file is
usually allocated to either the terminal or to a SYSOUT Source: Time Sharing Option Extensions (TSO/E)
class. You can specify where you want it to be allocated System Action: The system issues one of the following messages:
in either in CSECT INMXPARM or on the TRANSEC INMC156I, INMR037I, INMX067I, INMX083I, INMR127I, INMR132I,
keyword of parmlib member IKJTSO00. Reason code INMR133I, INMR134I, INMR137I, INMX040I, INMX042I, INMX204I,
002A is associated with messages INMX040I and INMX210I.
INMX042I.
The system issues an SVC dump.
0043 The TRANSMIT command was issued with the
DATASET or DSNAME keyword and the OBTAIN SVC System Programmer Response: If the problem recurs and if the
was issued to get information about the data set. The program is not in error, search problem reporting data bases for a fix
OBTAIN SVC set a return code other than 0 (successful for the problem. If no fix exists, contact the IBM Support Center.
termination), 8 (data set not on volume), or 12 (VTOC Provide the SVC dump and hardcopy of the TSO session if possible.
I/O error). Reason code 0043 is associated with
message INMX067I. 0B0
0053 The TRANSMIT command attempted to OPEN a data Explanation: The scheduler work area (SWA) manager detected
set previously written by the IEBCOPY utility or the AMS an uncorrectable error. Register 15 contains a reason code
REPRO command. The OPEN failed. The data set is a explaining the error:
temporary data set the TRANSMIT command allocates
Code Explanation
to contain intermediate data. Normally, the TRANSMIT
command reads, transmits, and deletes the temporary 04 The routine that called SWA manager requested an
data set. Reason code 0053 is associated with message incorrect function.
INMX083I. 08 The routine that called SWA manager passed an incor-
007F The RECEIVE command attempted to allocate a spool rect SVA (SWA virtual address). The SVA does not point
file and the allocation failed. The RECEIVE command to the beginning of a SWA prefix or the SWA prefix was
obtained the name of the spool file from JES. Reason destroyed.
code X'007F' is associated with message INMR127I. 0C A SWA manager routine tried read a record not yet
0084 The RECEIVE command was issued with the INDA- written into SWA.
TASET or INDSNAME keyword. 10 The system tried to read or write a block that is not 176
The data set specified with the keyword failed to OPEN. bytes or the system tried to assign a block with a speci-
The data set was allocated successfully. Reason code fied length of 0 or a negative number.
0084 is associated with message INMR132I. 14 The routine that called SWA manager specified an incor-
0085 The RECEIVE command attempted to OPEN a file for rect count field. For move mode, an incorrect count is 0
incoming network files from the JES spool, but the for a READ, WRITE, or ASSIGN function, and 00 for
OPEN failed. The process sysout subsystem interface WRITE/ASSIGN.
SCC-66 OS/390 V2R8.0 MVS System Codes
0B1 0B1
18 The routine that called SWA manager by issuing the the I/O configuration. In this case, the IODF contains
QMNGRIO macro specified both or neither of the READ multiple definitions and the system requires that you
or WRITE options. specify a valid configuration ID in the LOADxx member.
1C The routine that called SWA manager tried to write into 008 The IODF suffix is not valid.
a SWA block for the first time and has either passed a
009 The IODF data set name high level qualifier is not valid.
nonexistent ID, or has failed to pass an ID at all and the
block does not have an embedded ID. 00A The IODF is not valid for an IPL. It must be a VSAM
data set.
20 The system tried to write a block using an incorrect
pointer to the block. Note: We have found that this wait state can also be received due
to an invalid IODF statement. In addition to incorrect data
24 An error occurred while the system was translating an
entries this can also be caused by incorrect keyword filtering
SVA for an SWA block that is above 16 megabytes.
using HWNAME, LPAR NAME, and VMUSERID keywords.
28 The routine that called the SWA manager specified zero
Source: Input/output supervisor (IOS)
on the EPA parameter of the SWAREQ macro. The EPA
parameter must be the address of a fullword pointer to System Action: The system enters nonrestartable wait state
the EPA. Check the value specified on the EPA param- X'0B1'. The system issues the following messages with the fol-
eter of the SWAREQ macro to ensure that it is the lowing wait state reason codes:
address of a pointer to the EPA and not the EPA itself. Code Accompanying Message
34 An attempt has been made to allocate or delete an SWA 001 IEA513W.
block in an unauthorized environment.
002 IEA514W.
Source: Scheduler work area (SWA) manager
003 IEA515W, to display the device number.
System Action: The task ends and the system writes a dump.
004 IEA516W, to display the device number.
Operator Response: Notify the system programmer.
005 IEA517W.
Programmer Response: If the program that ended was a started
006 IEA518W.
task, and the code in register 15 is X‘08’ or X‘0C’, check the JCL for
this task. For all started tasks, the JCL must either: 007 None.
refer to existing data sets that are cataloged in the master 008 None.
catalog; or
009 None.
include unit and volume information on the DD statements for
Operator Response: Notify the system programmer.
existing data sets.
System Programmer Response: Depending on the hexadecimal
Modify the JCL to meet one of these requirements, and resubmit the
reason code, one of the following:
job.
Code Action
System Programmer Response: If the problem recurs and if the
program is not in error, search problem reporting data bases for a fix 001 Verify that the correct device number was specified on
for the problem. If no fix exists, contact the IBM Support Center. It is the LOAD parameter. Enter the correct IODF data set
the responsibility of the caller to SWA manager to take the dump, name in the LOADxx member.
and if none was taken, then a SLIP would need to be set up to 002 Ensure that the IODF data set is allocated as a single
capture the failure. Provide the dump to the IBM Support Center. extent data set.
003 Verify that the device specified on the LOAD parameter
0B1 is defined to the channel subsystem. (There is no device
Explanation: System initialization cannot continue because of a with the proper subchannel identifier.) Verify that the
problem in the LOADxx member, the I/O definition file (IODF) data correct device number was specified on the LOAD
set, or a device. parameter. Verify that the hardware configuration
matches the definitions in the IODF.
Bits 32 through 43 of the wait state program status word (PSW)
contain one of the following reason codes: 004 Move any of the following data sets (that are on the
device specified on the LOAD parameter) to a different
Code Explanation
device:
001 The required data set was not found.
IODF
002 The IODF occupies more than one extent. SYS1.PARMLIB
003 A required device is not defined. SYSn.IPLPARM
004 MSCH instruction failed for a required device. 005 Change the LOADxx member to specify another IODF.
Be sure to specify the name of a production-IODF
005 The IODF is not valid for an IPL. (instead of work-IODF).
006 The configuration ID specified in the LOADxx member 006 Change the LOADxx member to specify the correct
does not match any I/O configuration contained in the IODF or to specify the correct operating system config-
IODF. uration ID.
007 The LOADxx member contains blanks as the configura- 007 Specify the correct operating system configuration identi-
tion ID. If there is only one I/O configuration defined in fier.
the IODF, then the system ignores the blanks and uses
In each case, ask the operator to reIPL the system.
System Completion Codes SCC-67
0B2 0B6
System Programmer Response: If the problem persists, search
0B5
problem reporting data bases for a fix for the problem. Provide the
following search argument: Explanation: The master subsystem was unable to attach the con-
verter.
WS/D0B1: Wait state code
PRCS/rrrrrrrr: Reason code Source: Initiator/terminator
MS/IEAnnnW: Message identifier System Action: The system does not start the requested sub-
If no fix exists, ask the operator to obtain the stand-alone dump. system.
Contact the IBM Support Center. Provide the stand-alone dump, the System Programmer Response: Search problem reporting data
accompanying message, and the reason code. bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
0B2
Explanation: The system detected an incorrect statement in the 0B6
MSTRJCL data set. The system could not convert the MSTRJCL nor Explanation: Library automation communication services (LACS)
start the master scheduler. has detected an error condition. The specific error is identified by a
Source: Initiator/terminator reason code in register 15.
System Action: The system does not start the master scheduler. Code Explanation
The system abnormally ends master scheduler initialization. 04 The return code from the Asynchronous Operations
System Programmer Response: If the MSTRJCL data set in the Manager (AOM) LIBSERV service indicates that a
LINKLIB was updated manually, check it for a statement without a // parameter error has been detected.
in columns 1 and 2. Ensure that the MSTRJCL is delimited by a /* or 08 The return code and reason code from the AOM
a // (null) card. If the problem persists, search problem reporting data AOMQUE service indicate that an invalid request was
bases for a fix for the problem. If no fix exists, contact the IBM made.
Support Center.
0C The return code from the Library Control System (LCS)
CBRXVOL service indicates that a parameter error has
0B3
been detected.
Explanation: A caller of the master subsystem incore access
10 The return code from the LCS CBRXLCS service indi-
method attempted an incorrect or not serviceable access request.
cates that a parameter error has been detected.
Source: Initiator/terminator
14 A non-zero return code has been received from the
System Action: The system abnormally ends the task using the OAM message construction service.
access method.
18 The return code and reason code from the IEEMIFSV
System Programmer Response: Search problem reporting data message buffer manager service indicate that a param-
bases for a fix for the problem. If no fix exists, contact the IBM eter error has been detected.
Support Center.
1C The return code and reason code from the AOM
LIBSERV service indicate that no libraries have been
0B4 defined to AOM.
Explanation: The master subsystem could not make use of the 20 The return code and reason code from the AOM
SYS1.PROCLIB data set defined by the IEFPDSI statement in the LIBSERV service indicate that the library configuration
MSTRJCL. This occurred for one of the following reasons: has not yet been set to AOM.
The master subsystem was unable to OPEN the PROCLIB data 24 During the processing of a library mount request, a
set. mount order has been sent to the library. The library has
The blocksize of the opened SYS1.PROCLIB data set was not a responded with a unit check and an error recovery
multiple of 80. action (ERA) code. The mount request was for a specific
volume, but the ERA code is appropriate only for a
Source: Initiator/terminator
scratch volume.
System Action: The system cannot function without an open
28 During the processing of a library mount request, a
SYS1.PROCLIB data control block (DCB). The system does not start
mount order has been sent to the library. The library has
the requested subsystem.
responded with a unit check and an error recovery
System Programmer Response: Check for a valid data set name action (ERA) code. The mount request was for a scratch
on the IEFPDSI card in the MSTRJCL data set. Check for a valid volume, but the ERA code is appropriate only for a spe-
blocksize either on the IEFPDSI card or in the data set's format data cific volume.
set control block (DSCB) in the VTOC. If the problem persists,
2C During the processing of a library mount or demount
search problem reporting data bases for a fix for the problem. If no
request, an order has been sent to the library. The
fix exists, contact the IBM Support Center.
library has responded with a unit check and an error
recovery action (ERA) code. The ERA code is an unex-
pected and inappropriate response to the order.
30 During the processing of a library mount request, the
library has indicated that the mount operation completed
successfully, but the external volume serial number of
the mounted volume does not match the requested
volume serial number.
SCC-68 OS/390 V2R8.0 MVS System Codes
0B7 0B7
34 The return code from the Library Control System (LCS) 00000504 The system tried to copy and reassign storage, but
CBRXLIB service indicates that a parameter error has received an unexpected response code from the service
been detected. processor.
System Action: The system abnormally ends the task. An SVC 00000505 The system failed to establish a recovery environment.
dump is requested and the error is recorded in SYS1.LOGREC. The
00000601 The system returned an unexpected return code.
system resumes processing of the task. LACS sets the permanent
error return code and an appropriate reason code, and returns 00000602 The system failed to establish a recovery environment.
control to the caller. The job for which the LACS service was 00000603 The system received an unexpected return code for
requested fails. reconfiguration message processing.
Operator Response: Resubmit the failing job. If the failure persists, 00000701 The system received an unexpected return code when
notify the system programmer. requesting storage status.
System Programmer Response: For reason codes 04, 08, 0C, 10, 00000702 The system received an unexpected return code when
14, and 18, the problem is probably caused by incorrect LACS soft- requesting that storage be logically varied online.
ware. For reason codes 1C and 20, the problem is probably caused
00000703 The system received return code 8 when requesting that
by incorrect software in the caller of LACS or in AOM. For reason
storage be logically varied offline. This code indicates
codes 24, 28, 2C, and 30, the problem is probably caused by incor-
that the requested storage range contains permanently
rect library micro-code. Save the console log and the dump data set,
resident storage.
print the contents of SYS1.LOGREC, then contact the IBM Support
Center. 00000704 The system received an unexpected return code when
requesting that storage be logically varied offline.
0B7 00000705 The system failed to establish a recovery environment.
Explanation: A CONFIG or VARY command requested addition or 00000706 The system received an unexpected response code for a
removal of hardware units from a configuration. While processing the Store Extended Storage Usability Map command from
command, the system detected an error. A hexadecimal reason code the service processor.
in register 15 explains the error:
00000707 The system received an unexpected return code for a
Code Explanation Store Extended Storage Usability Map command from a
00000301 The system detected an incorrect parameter. service processor routine.
00000302 The caller was not authorized to use the vary path inter- xxxx0B01 Processing for the DISPLAY MATRIX command
face. received a nonzero return code.
00000303 For the processing, the system requested virtual storage xxxx0B02 Processing for the DISPLAY MATRIX command tried to
but failed to obtain it. issue a message, but could not find the associated
message text.
00000304 The vary path interface detected a failing return code
from the reconfiguration message service. xxxx0B04 The system received a nonzero return code from the
ESTAE macro. xxxx is the return code.
00000401 The service processor was running a CONFIG STOR
ONLINE command. The service processor varied the xxxx0C01 A command identified a processor on which it is to run.
requested storage physically online, but the system was The processor identifier is not in the system table of
unable to vary the storage logically online. The service identifiers.
processor then tried unsuccessfully to vary the storage xxxx0C02 Reconfiguration message processing returned a nonzero
physically offline. return code to reconfiguration.
00000402 The system returned an unexpected return code. xxxx0D01 The system could not establish a recovery environment.
00000403 The system tried to vary storage online or offline, but xxxx0D02 The system tried to call reconfiguration message proc-
received an unexpected response code from the service essing, but an error occurred.
processor.
00000E01 Reconfiguration message processing received an incor-
00000404 Processing for vary path reconfiguration received an rect address for the message buffer.
unexpected response code from the service processor.
00041001 Processing for the VARY PATH command received an
00000405 The system tried to obtain storage element information, unidentified or failing return code from reconfiguration
but received an unexpected response code from the message processing. The message text was too long.
service processor.
00081001 Processing for the VARY PATH command received an
00000406 The system failed to establish a recovery environment. unidentified or failing return code from reconfiguration
00000501 The system received an unexpected return code from message processing. The return code indicates that
the service processor call SVC routine. reconfiguration message processing was to issue a
WTOR macro and await a reply, but no replies exist in
00000502 The system tried to vary a storage element online or the static message area.
offline, but received an unexpected response code from
the service processor. 000C1001 Processing for the VARY PATH command received an
unidentified or failing return code from reconfiguration
00000503 The system tried to obtain storage element information, message processing. The number of message inserts
but received an unexpected response code from the was incorrect.
service processor.
System Completion Codes SCC-69
0B7 0B7
00101001 Processing for the VARY PATH command received an xxxx1606 The service processor took more than 45 seconds to
unidentified or failing return code from reconfiguration process a request.
message processing. The return code indicates that the
xxxx The last service processor call return code.
system could not establish a recovery environment.
xxxx1701 Reconfiguration requested virtual storage. The request
00141001 Processing for the VARY PATH command received an
failed.
unidentified or failing return code from reconfiguration
message processing. The return code indicates that the xxxx The GETMAIN return code.
message buffer area could not be obtained. xxxx1702 A service processor failure occurred.
00181001 Processing for the VARY PATH command received an xxxx The service processor response code.
unidentified or failing return code from reconfiguration
message processing. The return code indicates that the
xxxx1801 Reconfiguration received a nonzero return code from an
ESTAE macro.
message buffer identifier was incorrect.
xxxx The return code.
001C1001 Processing for the VARY PATH command received an
unidentified or failing return code from reconfiguration xxxx1904 Reconfiguration received a nonzero return code from an
message processing. The return code indicates that an ESTAE macro.
abend occurred.
xxxx The return code.
xxxx1201 Processing for channel path reconfiguration received a
xxxx1A01 Reconfiguration received a nonzero return code from an
nonzero return code.
ESTAE macro.
xxxx1202 Processing for channel path reconfiguration received a
xxxx The return code.
nonzero return code during vary processing.
xxxx1A02 Reconfiguration called the service processor, but the
xxxx1204 Processing for channel path reconfiguration detected an
service processor did not return information.
incorrect post code during vary processing.
xxxx The response code from the service
00001501 Processing for vary path reconfiguration received an
processor.
unexpected return code.
xxxx1B01 Reconfiguration received a nonzero return code from an
00001502 Processing for vary path reconfiguration received an
ESTAE macro.
unexpected return code. The system was processing a
request to bring online a Teleprocessing (TP) device xxxx The return code.
with active I/O. xxxx1B02 Reconfiguration called the service processor, but the
00001503 Processing for vary path reconfiguration received a service processor did not return CHP information.
nonzero return code indicating one of the following xxxx The response code from the service
errors: processor.
The system was unable to obtain enough storage to xxxx1C01 Reconfiguration received a nonzero return code from an
process the online request. ESTAE macro.
The system encountered an unrecoverable program xxxx The return code.
error.
xxxx1C02 A reconfiguration call to the service processor failed.
00001504 The operator replied CANCEL to message IEE717D,
xxxx The response code from the service
then one of the following occurred:
processor.
The system encountered a programming error while
xxxx2001 Reconfiguration could not set up an ESTAE environ-
processing a request to bring a path online.
ment.
Processing for vary path reconfiguration encount-
xxxx2002 Reconfiguration message processing could not find a
ered a programming error. The pointer to the
message identifier.
current vary request block is 0.
xxxx2003 Reconfiguration message processing found that the
00001505 Processing for vary path reconfiguration received an uni-
number of inserts received in the parameters does not
dentified or failing return code.
match the message definition.
xxxx1601 Reconfiguration requested virtual storage. The request
xxxx2004 Reconfiguration message processing found that the
failed.
specified message does not fit into the 72-byte buffer.
xxxx The GETMAIN return code.
xxxx2005 Reconfiguration message processing found that the
xxxx1602 Processing to force a channel path offline encountered parameters passed to it specified more than 4 bytes for
an error. the length of a table insert or a hexadecimal or decimal
xxxx The last return code encountered. insert.
xxxx1603 A service processor failure occurred. xxxx2006 Reconfiguration message processing found that the
parameters passed to it specified a table insert that was
xxxx The last service processor call return code.
beyond the insert table in the message definition.
00001604 A service processor command is incorrect.
xxxx211C A reconfiguration call to the service processor did not
xxxx1605 Processing to force a channel path offline received an return information; the reason and response codes were
unidentified service processor response code. either not recognized or expected. Reconfiguration
records diagnostic information in the system diagnostic
xxxx The service processor response code.
work area (SDWA), in the variable recording area (VRA),
SCC-70 OS/390 V2R8.0 MVS System Codes
0B8 0B8
or for CPU/VF reconfiguration, SYMREC. Reconfigura- Frees all resources related to the reconfiguration command.
tion returns control to the caller with return code X'1C'.
Writes a logrec data set error record.
xxxx The reason or response code.
May issue message IEE174I or IEE521I.
xxxx2120 Reconfiguration requested virtual storage. The request
Writes a dump.
returned a nonzero return code. Reconfiguration records
diagnostic information in the SDWA, in the VRA, or for Operator Response: Enter the command again. If the command
CPU/VF reconfiguration, SYMREC. Reconfiguration fails again, look at message IEE521I. Depending on the text of
returns control to the caller with return code X'20'. message IEE521I, do the following:
xxxx The GETMAIN return code. STATUS NOT OBTAINED: SERVICE PROCESSOR FAILURE
Contact hardware support. Provide the logrec data set error
00002128 Reconfiguration received an incorrect request. The
record.
request is incorrect for one of the following reasons:
The parameter list control block identifier or version STATUS NOT OBTAINED: SERVICE PROCESSOR CALL FAILED
number was incorrect. Contact the system programmer.
The function code was unrecognized. System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
The side information block control block identifier or
Support Center. Provide the dump and the logrec data set error
version number was incorrect.
record.
0000212C Reconfiguration was running on a central processor that
does not support the service processor architecture.
0B8
xxxx2201 Reconfiguration received a nonzero return code from an
Explanation: A START, MOUNT, or LOGON command requested
ESTAE macro.
the creation or initialization of a new address space. The system
xxxx The ESTAE return code. detected an error while processing the command. A hexadecimal
xxxx2202 Reconfiguration received an incorrect function code. reason code in register 15 explains the error:
xxxx The incorrect function code. Code Explanation
xxxx2281 Reconfiguration received a nonzero return code. 04 The command code in the command scheduling control
block (CSCB) for the START, MOUNT, or LOGON
xxxx The return code. command was incorrect.
xxxx2282 Reconfiguration requested virtual storage. The request 08 The system tried to build a task I/O table (TIOT) for the
returned a nonzero return code. START, MOUNT, or LOGON processing, but failed.
xxxx The GETMAIN return code. 0C While processing the START, MOUNT, or LOGON
xxxx22C1 Reconfiguration received a nonzero return code from a command, the system could not open or write to an
service processor call SVC. internal reader.
xxxx The return code. 10 Processing to initialize the address space returned an
undefined return code; the defined codes are 0 and 4.
xxxx22C2 Reconfiguration received an unexpected response from
the service processor. 14 The newly created address space cannot be made
nonswappable.
xxxx The service processor response.
18 To create the requested address space, the system
xxxx2302 The system called reconfiguration message processing;
issued a REQSWAP SYSEVENT macro. The macro
an error occurred.
failed.
xxxx2402 The system called reconfiguration message processing;
1C The newly created address space did not initialize com-
an error occurred.
pletely.
xxxx2502 The system called reconfiguration message processing;
20 Dynamic allocation or unallocation failed for an internal
an error occurred.
reader.
xxxx2602 The system called reconfiguration message processing;
Source: Master scheduler
an error occurred.
System Action: The system:
xxxx2702 The system called reconfiguration message processing;
an error occurred. Ends the START, MOUNT, or LOGON command.
xxxx2802 The system called reconfiguration message processing; Writes a dump.
an error occurred. Writes a logrec data set error record.
xxxx2902 The system called reconfiguration message processing; Issues messages. For a START or MOUNT command, the
an error occurred. system issues message IEE824I.
xxxx2A02 The system called reconfiguration message processing; System Programmer Response: If the problem recurs, search
an error occurred. problem reporting data bases for a fix for the problem. If no fix
Source: Reconfiguration exists, contact the IBM support Center. Provide the dump and the
logrec data set error record.
System Action: The system:
System Completion Codes SCC-71
0B9 0Cx
0B9 0BD
Explanation: A START, MOUNT, or LOGON command requested Explanation: While processing a TRACE command to start, modify,
creation or initialization of an address space. The started task control or end the master trace, the system found that the parameter list for
(STC) queried the master subsystem to determine if a subsystem master trace processing is incorrect or cannot be obtained.
was started. STC received a return code that was not valid from the
Source: Master scheduler
master subsystem.
System Action: The system ends master tracing. There is no
Source: Master scheduler
change in the status of the master tracing facility. The system issues
System Action: The system: messages and writes a dump.
Ends the START, MOUNT, or LOGON command. Operator Response: Contact the system programmer.
Writes a dump. System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
Writes a logrec data set error record.
support Center. Provide the dump and messages.
Issues messages. For a START or MOUNT command, the
system issues message IEE824I.
0BE
System Programmer Response: If the problem recurs, search
Explanation: While processing a TRACE command to start, modify,
problem reporting data bases for a fix for the problem. If no fix
or end the master trace, the system requested that virtual storage be
exists, contact the IBM support Center. Provide the dump and the
freed. The request failed.
logrec data set error record.
Source: Master scheduler
0BA System Action: The system:
Explanation: Started task control was processing a START, Ends master trace processing.
LOGON or MOUNT command and issued a request to a subsystem.
Issues message IEE480I or IEE481I.
The subsystem returned an incorrect return code.
Issues message IEE839I to describe the status of the master
Source: Master scheduler or initiator/terminator
tracing facility.
System Action: In started task control, if the command is START
Writes a dump.
or MOUNT, the system issues message IEE824I and ends the
START, MOUNT, or LOGON task. In the initiator, the system issues Operator Response: Contact the system programmer.
message IEF187I and ends the job. The system writes a logrec data System Programmer Response: Search problem reporting data
set error record. The system may write an SVC dump. bases for a fix for the problem. If no fix exists, contact the IBM
Operator Response: Enter the command again. If it fails again, support Center. Provide the dump and messages.
contact the system programmer.
System Programmer Response: Search problem reporting data 0BF
bases for a fix for the problem. If no fix exists, contact the IBM Explanation: Master tracing failed during a recovery attempt.
Support Center. Provide the SVC dump, if available, and the logrec
Source: Master scheduler
data set error record.
System Action: The system ends master trace processing. The
system issues message IEE480I or IEE481I to describe the status of
0BB
master tracing. The system writes a dump.
Explanation: During initialization of a job step or processing of a
System Programmer Response: Search problem reporting data
START or LOGON command, the initiator issued an ATTACH macro
bases for a fix for the problem. If no fix exists, contact the IBM
to attach the job step task, the started task, or the LOGON task. The
support Center. Provide the dump.
ATTACH failed.
Source: Initiator/terminator
0Cx
System Action: The initiator is abnormally ended causing failure of
Explanation: A program interruption occurred, but no routine had
the job, START or LOGON. Register 15 contains the return code
been specified to handle this type of interruption. Refer to the
from ATTACH.
instruction description in Principles of Operation to find out how the
Operator Response: Retry the command. If the problem persists, instruction stops processing for the error condition.
tell the system programmer.
The last digit of this completion code is a hexadecimal number that
System Programmer Response: Search problem reporting data indicates the cause of the program interruption. Each X'0Cx' system
bases for a fix for the problem. If no fix exists, contact the IBM completion code has a reason code, which in most cases equals the
Support Center, providing the SVC dump and the logrec data set last digit. X'0C4' however, has several reason codes.
error records.
Code Explanation
0C1 Operation exception. The reason code is 1.
0C2 Privileged-operation exception. The reason code is 2.
0C3 Execute exception. The reason code is 3.
0C4 One of the following exceptions occurred:
SCC-72 OS/390 V2R8.0 MVS System Codes
0D2 0D3
4 Protection exception. The key of the storage SMS abend. The reason code is
area that the running program tries to X'12C'.
access is different from that of the running
0C5 Addressing exception. The reason code is 5.
program. The key of the running program
can be obtained from the PSW key field. 0C6 Specification exception. The reason code is 6.
The key of the storage can be obtained 0C7 Data exception. The reason code is whatever the data
using the IPCS LIST subcommand. The pro- exception code is in field SDWADXC in the SDWA
grammer should determine whether the (systems diagnostic work area).
program is running with the correct key or
0C8 Fixed-point-overflow exception. The reason code is 8.
whether the storage address is set up cor-
rectly. 0C9 Fixed-point-divide exception. The reason code is 9.
The protection exception might have 0CA Decimal-overflow exception. The reason code is A.
occurred when the program referenced a
0CB Decimal-divide exception. The reason code is B.
page that is protected with the PGSER
PROTECT service, or is defined as shared 0CC Exponent-overflow exception. The reason code is C.
by the IARVSERV service with a view of 0CD Exponent-underflow exception. The reason code is D.
read-only.
0CE Significance exception. The reason code is E.
10 Segment-translation exception. This error is
0CF Floating-point-divide exception. The reason code is F.
caused by one of the following:
Source: Supervisor control
A program that was running disabled
attempted to reference storage while System Action: The system abnormally ends the task, unless a
the page table for that storage was recovery routine was provided to handle the interruption. The hard-
paged out. To correct the error, page-fix ware action is given in Principles of Operation.
the storage before a program running
System Programmer Response: Determine whether the problem
disabled attempts to reference it.
program or control program was in error.
A program attempted to reference
If the problem program contained an error, correct it, and run the job
storage that had not been obtained. To
step again.
correct the error, allocate the storage
before attempting to reference it.
0D2
A program running in a subspace
attempted to reference storage that was Explanation: A program check occurred; the interruption code is
not accessible to the subspace at the X'12' for a translation specification error. The error was caused by
time of error. To correct the error, incorrect data in control registers 0 or 1 or a segment or page table.
ensure that the program running in a The incorrect data is due to:
subspace references only the storage A hardware error
assigned to that subspace, or storage Damage by a program running in key 0
that can be referenced by all sub-
See Principles of Operation for more information about translation
spaces.
specification errors.
11 Page-translation exception. This error is
Source: Supervisor control
caused by one of the following:
System Action: The system tries to end the task experiencing the
A program that was running disabled
program check. If the task cannot be ended because of the trans-
attempted to reference storage while
lation problems, the system tries to end the address space. If this
that storage was paged out. To correct
fails, the system enters a disabled wait state, for example, wait state
the error, page-fix the storage before a
X'014'.
program running disabled attempts to
reference it. Programmer Response: Correct the error. Rerun the program.
A program attempted to reference
storage that had not been obtained. To 0D3
correct the error, allocate the storage Explanation: A program check occurred; the interruption code is
before attempting to reference it. X'13' for a special operation error. See Principles of Operation for
A program running in a subspace more information about special operation errors.
attempted to reference storage that was Source: Supervisor control
not accessible to the subspace at the
System Action: The system abnormally ends the task experiencing
time of error. To correct the error,
the program check.
ensure that the program running in a
subspace references only the storage Programmer Response: Check to see if the program issued a PC
assigned to that subspace, or storage in secondary mode. Remove the Set System Mask (SSM) instruc-
that can be referenced by all sub- tion. This instruction is not valid in the system.
spaces.
System Completion Codes SCC-73
0D4 0D7
Look for a problem with the PC/AUTH macros that estab-
0D4
lished the cross memory service. Correct any problems.
Explanation: A program issued a Program Call (PC), Program Check the failing program for logic that changes general
Return (PR), Program Transfer (PT), or Set Storage Address Reg- register 3, 4, or 14.
ister (SSAR) instruction. During processing of the instruction, an Search problem reporting data bases for a fix for the
address space number (ASN) translation specification exception problem. If no fix exists, contact the IBM Support Center.
occurred. The ASN translation exception is also known as an
For cross memory access to a swappable address space:
address space identifier (ASID) translation exception. The program
interruption code if X'17'. The address space first table (AFT) or the Ensure that the address spaces that provide cross memory
address space second table (AST) contains incorrect data. services are non-swappable.
Search problem reporting data bases for a fix for the
Source: Program Call/authorization (PC/AUTH)
problem. If no fix exists, contact the IBM Support Center.
System Action: The system abends the program that issued the Provide the SVC dump.
PC, PR, PT, or SSAR instruction. The system writes an SVC dump
or a logrec data set error record or both. 0D6
System Programmer Response: If a search of the problem Explanation: A program issued a Program Call (PC) instruction
reporting data bases does not show a fix for the problem, contact the that specified an incorrect PC number. A hexadecimal reason code
IBM Support Center. Provide: or interrupt code explains the error:
The SVC dump and the logrec data set error record, which con- Code Explanation
tains control registers 3, 4, and 14
00 The PC number specified in the PC instruction is unde-
The instruction being processed by PC/AUTH when the problem fined.
occurred.
Code Explanation
To determine the instruction, start at the bottom of the system
trace table and back up to a *PGM 017 entry. Continue backing 22 A linkage index (LX) translation exception occurred; the
up to the first PC, PT, or SSAR entry, which is the instruction program interruption code is X'22'.
that was being processed at the time of the failure. 23 An entry table (EX) translation exception occurred; the
program interruption code if X'23'.
0D5 Source: Program Call/authorization (PC/AUTH)
Explanation: A program issued a Program Call (PC), Program System Action: The system abends the program that issued the
Return (PR), Program Transfer (PT) or Set Storage Address Register PC instruction. The system writes an ABEND dump.
(SSAR) instruction for cross memory access. One of the following
occurred: System Programmer Response: Look for a problem with the
PC/AUTH macros that established the cross memory service being
An address space first table index (AFX) translation exception used by the failing program.
(program interruption code X'20') occurred. The value in the
address space first table (AFT) corresponding to the address For reason code X'00', register 14 points to the next instruction
space identifier (ASID) is not valid. Either no such address after the PC instruction. Bit 31 of register 14 is the PSW problem
space exists or the system had swapped it out. state bit at the time the PC instruction was issued. Registers 0, 2,
5-11, and 13 contain the values they had when the PC instruction
An address space second table index (ASX) translation excep- was issued.
tion (program interruption code X'21') occurred. The value in
the address space second table (AST) corresponding to the If no problems were found or the problem recurs, search problem
ASID is not valid. Either no such address space exists or the reporting data bases for a fix for the problem. if no fix exists, contact
system had swapped it out. the IBM Support Center. Provide the ABEND dump.
The cross memory access is to a swappable address space,
0D7
which is a violation of MVS cross memory access protocol.
Explanation: A problem occurred while the system processed a
Source: Either:
Program Return (PR), Program Transfer (PT) or Set Storage
Real storage manager (RSM) Address Register (SSAR) instruction, as follows.
Program Call/Authorization (PC/AUTH)
A program issued the PT instruction, but a primary authority
System Action: For program interrupt code X'20' or X'21', the exception occurred. The primary address space is not author-
system attempts to correct any errors in the AFT. The system abnor- ized to issue a PT instruction to the target address space.
mally ends the program that issued the PC, PR, PT or SSAR instruc-
Either:
tion.
– The authorization index (AX) is greater than the number of
If the error was cross memory I/O in progress for a swappable
elements in the target address space's authorization table
address space, the system abnormally ends the program that was
(AT)
waiting for the I/O to complete. The system continues swapping out
the address space. – The P bit is off in the target address space's AT. The
program interruption code is X'24'.
If the error was an incorrect cross memory reference to a swappable
address space, the system abends that address space. For example, A program issued the SSAR instruction, but a secondary
if additional pages are to be fixed in a logically swapped address authority exception occurred. The primary address space is not
space, the system ends the logically swapped address space. authorized to issue an SSAR instruction to the target address
space.
System Programmer Response:
Either:
For a program interrupt code X'20' or X'21':
SCC-74 OS/390 V2R8.0 MVS System Codes
0D8 0DB
– The AX is greater than the number of elements in the target
0DA
address space's AT.
Explanation: A program issued a Program Call (PC) instruction
– The S bit is off in the target address space's AT. The
and a PC translation specification exception occurred. The program
program interruption code is X'25'.
interruption code is X'1F'.
A program issued the PR instruction, but a secondary authority
Either the linkage table (LT) or the entry tables (ET) contain incorrect
exception occurred. The primary address space is not author-
data. This can be either an application program or system program
ized to issue an PR instruction to the target address space.
error.
Either:
Source: Program Call/authorization (PC/AUTH)
– The AX is greater than the number of elements in the target
System Action: The system abended the program that issued the
address space's AT.
PC instruction. The system may write an SVC dump for this abend.
– The S bit is off in the target address space's AT. The
Operator Response: If requested by the system programmer, set a
program interruption code is X'25'.
SLIP trap to obtain an SVC dump. Specify the address space for
Source: Program Call/authorization (PC/AUTH) the failing program as the first address space identifier (ASID) in the
System Action: The system abended the program that issued the ASIDLIST parameter as follows:
PR, PT or the SSAR instruction. SLIP SET,ID=CðDA,COMPðDA,ACTION=SVCD,ASIDLIST=(ð2),END
System Programmer Response: This error may occur if an System Programmer Response: Do the following:
address space involved in the cross memory environment has termi-
1. Check the addressing mode of the PC routine. If it is 24-bit,
nated. If the address space is still active, look for a problem with the
ensure that there is no extraneous data in bits 1-7 of the
PC/AUTH macros that established the cross memory service being
address.
used by the failing program.
2. Obtain the SVC dump, if one was written. If no dump was
If no problems were found or if the problem recurs, search problem
produced, but the problem can be recreated, ask the operator to
reporting data bases for a fix for the problem. If no fix exists, contact
set a SLIP trap to obtain the dump.
the IBM Support Center.
3. In the SVC dump, determine the PC number of the PC instruc-
0D8 tion processing at the time of the failure by doing the following:
Explanation: A space switch exception occurred. A program issued a. Starting at the bottom of the system trace table, back up to
a Program Call (PC), Program Return (PR), or Program Transfer to a *PGM 01F entry.
(PT) instruction, but the cross memory resource ownership task in b. Continue backing up to the first PC entry. This is the PC
the target address space has ended. The target address space is not entry for the instruction that was being processed. The PC
the home address space of the program that issued the PC or PT number is in the UNIQUE-1 column.
instruction. The program interruption code if X'1C'.
4. If the failing PC instruction was for an ETCRE or ETCON macro
Source: Program Call/authorization (PC/AUTH) in an installation-provided program, obtain the following data to
System Action: The system abends the program that issued the fix the problem:
PC, PR, or PT instruction. The input to the ETCRE macro
System Programmer Response: Look for a problem with the The parameters on the ETDEF macro, if used.
PC/AUTH macros that established the cross memory service being 5. If the failing PC instruction is in an IBM module, search problem
used by the failing program. Correct any problems in the program reporting data bases for a fix for the problem. If no fix exists,
and resubmit it. contact the component group for the module. Provide the SVC
If no problems were found or if the problem recurs, search problem dump.
reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center. 0DB
Explanation: A program check was detected. An interruption code
0D9 of X‘15’, an operand exception, has occurred.
Explanation: One of the following system errors occurred: Source: Recovery termination manager (RTM)
A program check occurred because of a hardware problem. System Action: The task ends.
A program running storage key zero caused data damage. Programmer Response: This is a system error. Run the job again.
Source: Communications task (COMMTASK) System Programmer Response: If the error recurs and the
System Action: The system abnormally ends the current task. 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
Programmer Response: Rerun the job. problem. If no fix exists, contact the IBM Support Center. Provide the
JCL, the program listing for the job, and all printed output and output
data sets related to the problem.
Obtain the ABEND dump for the failing job step. If the JCL for the
step did not contain a DD statement for an ABEND dump, add one
of the following and run the job step again. Use a SYSMDUMP DD
statement if you plan to analyze and format the dump with the inter-
active problem control system (IPCS).
SYSABEND DD statement
SYSMDUMP DD statement
System Completion Codes SCC-75
0DC 0E0
SYSUDUMP DD statement 2B Either an ALE specified a data space that is not valid or
there is an ASTE validity check for an address space on
0DC an access list.
Explanation: The recovery termination manager (RTM) encount- 2C An ALE refers to a sequence number in the address
ered an unrecoverable error while processing a functional recovery space second table entry (ASTE). The sequence number
routine (FRR) stack. RTM issues this abend when: is not equal to the number in the ALE.
It detects a problem while processing another abend. 2D A private ALE is specified, but the current extended
authorization index (EAX) is not authorized to the target
It detects that critical fields in important control blocks for the address space.
address space or system are overlaid. These control blocks
include the: 30 A stacking instruction was issued when the linkage stack
was full.
– Address space control block (ASCB)
– Extended status block (XSB) 31 An unstacking instruction such as PR or EREG was
– Request block (RB) issued when the linkage stack was empty.
– Task control block (TCB) 32 A linkage stack specification interrupt occurred.
RTM ends the address space. This abend code is found in the 33 The hardware or an unstacking operation found a
ASCBMCC field in the ASCB for the ended address space and in linkage stack entry (LSE) type that is not valid.
message IEF402I.
34 A Program Return (PR) instruction was issued against a
A hexadecimal reason code in field ASCBARC of the ASCB and in linkage stack entry that has the unstack suppression bit
message IEF402I explains the error: set. The system sets this bit in a linkage stack entry to
Code Explanation prevent SVC routines from unstacking entries they did
not add to the stack.
04 RTM recovery received control after RTM FRR proc-
essing encountered an unrecoverable error and abnor- nnn An unexpected interrupt code. A possible cause of this is
mally ended the address space. that the level of MVS is not the correct one for the hard-
ware.
08 RTM FRR processing that is not covered by an FRR
encountered an unrecoverable error. RTM's default Source: Supervisor control
recovery received control and abnormally ended the System Action: The system abnormally ends the task experiencing
address space. the program check, unless the task provides recovery to handle the
0C During second level interrupt handler (SLIH) processing, interruption. The system may write a logrec data set error record.
RTM detected an incorrect value in the TCBTCBID field Operator Response: If the system programmer asks for an SVC
of the current TCB. RTM's recovery received control and dump, set the following SLIP trap:
abnormally ended the address space.
SLIP SET,COMP=ðEð,ACTION=SVCD,END
10 During SLIH processing, RTM found 0 in the TCBRBP
Programmer Response: Do one of the following:
field. RTM's recovery received control and abnormally
ended the address space. For reason code X'30', determine if your program has improp-
erly added entries to the linkage stack. For example, uninten-
Source: Recovery termination manager (RTM)
tionally executing a BAKR many times can fill the linkage stack.
System Action: The system abnormally ends the address space, If your program is not improperly adding entries to the linkage
places the abend code and reason code into the ASCB for the stack, then use an LSEXPAND macro to increase the size of the
ended address space, and issues message IEF402I. linkage stack.
System Programmer Response: Do the following: For reason code X'32' or X'33', see Principles of Operation.
1. Obtain the reason code from message IEF402I or from field For other reason codes, determine if the problem program or the
ASCBARC of the ASCB. system was in error. If the problem program contained an error,
2. Search problem reporting data bases for a fix for the problem. If correct it, and run the job step again.
no fix exists, contact the IBM Support Center. System Programmer Response: Do the following:
1. If a logrec data set error record was not written for the program
0E0 check, ask the operator to set a SLIP trap to obtain an SVC
Explanation: A program check occurred. The hexadecimal inter- dump.
ruption code is as follows: 2. Look at the program status word (PSW) at the time of error. Use
Code Explanation the address in the PSW to identify the module that experienced
the X'0E0' program check.
1D A square root exception occurred.
For an installation-provided module, continue diagnosis with
1E An unnormalized operand exception occurred. the module.
28 Reserved bit positions in an access list entry token For an IBM module, search problem reporting data bases
(ALET) were nonzero. for a fix for the problem. If no fix exists, contact the compo-
29 An ALET specified an access list entry (ALE) that is not nent group associated with this module at the IBM Support
valid. Center. Provide, if available, the SVC dump and the logrec
data set error record.
2A An ALET specified a previously deleted ALE.
SCC-76 OS/390 V2R8.0 MVS System Codes
0E1 0E4
0E1 0E2
Explanation: An error was encountered while processing the first Explanation: The error was detected while processing the first
EXCP against a virtual I/O (VIO) data set. Register 15 contains a EXCP for the VIO data set after a restart. Register 15 contains one
hexadecimal reason code: of the following hexadecimal reason codes:
Code Explanation Code Explanation
2xx RSM was unable to ‘assign null’ the virtual track buffer 2xx RSM was unable to ‘assign null’ the virtual track buffer
or the DSPCT map. Where xx is: or the DSPCT map. Refer to code 0E1 for an explana-
tion of xx.
xx Explanation
Source: DFSMSdfp
04 An assign (move-in) error occurred. The
page identified by the VCBVSA field is not System Action: The input parm list (IDAVOP1), DSPCT header
available. (IDAVBPH) and SWA are dumped to the SYS1.DUMP data set.
08 A write (move-out) error occurred. The page Programmer Response: System error. Rerun the job.
identified by the VCBVSA field is fixed in
System Programmer Response: If the error recurs and the
real storage and cannot be written to the
program is not in error, look at the messages in the job log for more
data set in auxiliary storage.
information. Search problem reporting data bases for a fix for the
0C The request was incorrect; it was not an problem. If no fix exists, contact the IBM Support Center. Provide the
assign or a write request. SYSOUT output for the job and the logrec data set error record.
10 The page identified by the VCBVSA field is
not written to the data set because it was 0E3
not brought into real storage by the prior Explanation: The error occurred while processing a VIO data set.
read request or because data in the page Register 15 contains one of the following hexadecimal reason codes:
has not been modified.
Code Explanation
20 The page identified by the VCBVSA field
belongs to an LPID other than the LPID in 004 An incorrect RBA was passed to VBP. Probable causes
the VCBLPID field. of error code are (1) DEB with extent descriptions that
do not fall within the allocated extents as described in
40 The virtual storage address in the VCBVSA the virtual data set control block (VDSCB) (2) EXCP was
field was incorrect. A GETMAIN macro was issued to read the format 1 DSCB on the volume.
not issued for the page identified by the
VCBVSA field. 2xx RSM was unable to assign or move out pages in the
virtual track buffer. Refer to code 0E1 for an explanation
80 An assign error occurred. The page identi- of xx.
fied by the VCBVSA field was read previ-
ously but was not disconnected by a Source: DFSMSdfp
move-out or move-out-null request before System Action: The following are dumped to the SYS1.DUMP data
the current read (assign) operation. set:
3xx The auxiliary storage manager (ASM) was unable to Input parameter list (IDABUFC)
ASSIGN a logical group for this VIO data set. Where xx DSPCT header (IDAVBPH)
is: SWA
xx Explanation LSQA
The region (in some cases)
1C One of the following occurred:
Programmer Response: System error. Rerun the job.
ASM could not obtain storage to
process the request. System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
ASM could not assign a logical group information. Search problem reporting data bases for a fix for the
because the requested maximum rela- problem. If no fix exists, contact the IBM Support Center. Provide the
tive page number was too large. SYSOUT output for the job and the logrec data set error record.
Source: DFSMSdfp
System Action: The input parm list (IDAVOP1), the DSPCT header 0E4
(IDAVBPH) and SWA are dumped to the SYS1.DUMP data set. Explanation: The error occurred while trying to scratch a VIO data
Programmer Response: System error. Rerun the job. set.
System Programmer Response: If the error recurs and the Register 15 contains one of the following hexadecimal reason codes:
program is not in error, look at the messages in the job log for more Code Explanation
information. Search problem reporting data bases for a fix for the
3xx ASM could not RELEASE the logical group for this data
problem. If no fix exists, contact the IBM Support Center. Provide the
set. Where xx is:
SYSOUT output for the job and the logrec data set error record.
xx Explanation
04 Incorrect LGN.
1C Unable to obtain storage to process request.
System Completion Codes SCC-77
0E5 0F1
20 Incorrect operation code is supplied in the 3xx ASM was unable to ‘SAVE’ the logical group for this
auxiliary storage manager control area data set. Where xx is:
(ACA).
xx Explanation
28 Incorrect identifier type when an LGN was
04 Incorrect LGN.
given, but ‘S’ type symbol is required.
14 Unrecoverable error occurred while writing
Source: DFSMSdfp
to VIO journaling data set.
System Action: The DSPCT header is dumped to the
1C Unable to obtain storage to process request.
SYS1.DUMPxx data set.
20 Incorrect operation code is supplied in the
Programmer Response: System error. Rerun the job.
auxiliary storage manager control area
System Programmer Response: If the error recurs and the (ACA).
program is not in error, look at the messages in the job log for more
2C Indeterminate error has occurred.
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the Source: DFSMSdfp
SYSOUT output for the job and the logrec data set error record. System Action: The DSPCT header (IDAVBPH) and SWA are
dumped on the SYS1.DUMP data set.
0E5 Programmer Response: System error. Rerun the job.
Explanation: Unable to disconnect the virtual track buffer from the System Programmer Response: If the error recurs and the
VIO data set. program is not in error, look at the messages in the job log for more
Register 15 contains one of the following hexadecimal reason codes: information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
Code Explanation
SYSOUT output for the job and the logrec data set error record.
2xx RSM was unable to ‘MOVE OUT’ pages in the virtual
track buffer. Refer to code 0E1 for an explanation of xx.
0E8
Source: DFSMSdfp
Explanation: The error occurred while processing the VIO data
System Action: The DSPCT header and SWA are dumped to the sets for the job after an abnormal system or job step task failure.
SYS1.DUMP data set. Register 15 contains one of the following hexadecimal reason codes:
Programmer Response: System error. Rerun the job. Code Explanation
System Programmer Response: If the error recurs and the 3xx ASM was unable to release the logical group for this
program is not in error, look at the messages in the job log for more data set. See code 0E4 for an explanation of xx.
information. Search problem reporting data bases for a fix for the
Source: DFSMSdfp
problem. If no fix exists, contact the IBM Support Center. Provide the
SYSOUT output for the job and the logrec data set error record. System Action: The input parm list (RMPL) and the ASCB are
dumped to the SYS1.DUMP data set.
0E6 Programmer Response: System error. Rerun the job.
Explanation: Unable to process against a VIO data set that has System Programmer Response: If the error recurs and the
already been scratched. 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
Source: DFSMSdfp
problem. If no fix exists, contact the IBM Support Center. Provide the
System Action: The VDSCB (IDDVDSCB) is dumped to the SYSOUT output for the job and the logrec data set error record.
SYS1.DUMP data set.
Programmer Response: Do not access a scratched data set. 0F0
System Programmer Response: If the error recurs and the Explanation: When the system tried to process a machine check
program is not in error, look at the messages in the job log for more interruption, an error occurred when the function recovery routine
information. Search problem reporting data bases for a fix for the (FRR) stack was active.
problem. If no fix exists, contact the IBM Support Center. Provide the
Source: Machine check handler (MCH)
SYSOUT output for the job and the logrec data set error record.
System Action: The system issues error messages. The system
writes an SVC dump. The system abnormally ends the task that was
0E7
running when the machine check interruption occurred.
Explanation: The error occurred while journaling the DSPCT
Programmer Response: Run the job again.
header (IDAVBPH) at step end or at checkpoint. Register 15 con-
tains one of the following hexadecimal reason codes:
0F1
Code Explanation
Explanation: While processing a security request, JES3 received
2xx RSM was unable to ASSIGN or MOVE OUT pages in
an unexpected return code. Register 15 contains a hexadecimal
the virtual track buffer. Refer to code 0E1 for explana-
reason code that indicates the type of error.
tion of xx.
For reason codes X'01, 02, 03, 04, or 07':
Register 5 contains the offset in module IATGRSC where the
error was detected.
Register 6 contains the logical IATXSEC index, which indicates
SCC-78 OS/390 V2R8.0 MVS System Codes
0F2 0F6
the type of processing in progress when the security request System Programmer Response: Search problem reporting data
was made. bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
Register 8 contains the address of the security check parameter
list.
0F4
Code Explanation
Explanation: An error occurred in DFSMSdfp support.
01 IATUX58 exit returned an incorrect return code in reg-
ister 2. Source: DFSMSdfp
02 System authorization facility (SAF) returned an incorrect System Action: Prior to the ABEND error occurring, a return code
return code in register 2. Register 3 contains the security was placed in the general register 15 and a reason code in general
product return code, and register 4 contains the security register 0. An SVC dump has been taken unless the failure is in
product reason code. IGWSPZAP, where register 15 contains 10. The DFSMSdfp recovery
routines retry to allow the failing module to return to its caller. See
03 IATUX59 exit returned an incorrect return code in reg-
DFSMS/MVS DFSMSdfp Diagnosis Guide for return code informa-
ister 2.
tion.
04 IATGRSC module issued this return code to cause entry
Programmer Response: System error. Rerun the job.
into the caller's recovery routine.
System Programmer Response: If the error recurs and the
05 The system rejected a security request for authorization
program is not in error, search problem reporting data bases for a fix
to create a SYSIN data set.
for the problem. If no fix exists, contact the IBM Support Center.
06 The system rejected a security request for authorization Provide the JCL, the SYSOUT output for the job, and the logrec data
to create a SYSOUT data set. set error record.
07 A multi-line write to operator text extraction service,
IEAVM703, returned a non-zero return code in register 0F6
2. Register 3 contains the reason code. Explanation: During processing of a SETEVENT macro for the
08 The JES3 security subtask received incorrect input. generalized trace facility (GTF), an error occurred. Register 15 con-
tains a hexadecimal reason code that explains the error:
09 Unexpected return code from a SAF call in module
IATISEN. Code Explanation
Source: JES3 00 The issuer of the SETEVENT macro was not authorized
through the authorized program facility (APF), was not in
System Action: The security request processing is ended.
protect key 0-7, or was not in supervisor state.
Operator Response: Request a dump of the address space, save
04 The parameter list passed to SETEVENT was incorrect.
all associated print output, and notify the system programmer.
08 An incorrect address for the monitor call queue element
Programmer Response: Depending on the reason code, do the
(MCQE) was passed to SETEVENT.
following:
0C The MCQE at the address passed to SETEVENT is
For reason code X'01', code a valid return code in installation
incorrect for the function requested.
exit IATUX58.
For reason code X'03', code a valid return code in installation 20 The call to SETEVENT:
exit IATUX59. Attempted to add elements to an existing event
For reason codes X'02, 04, 05, 06, 07, 08', contact the IBM directory
Support Center.
Would have resulted in multiple MCQEs.
0F2 Source: Generalized trace facility (GTF)
Explanation: An error occurred when the system was processing System Action: The system writes messages and a dump.
an I/O interrupt. An I/O recovery routine failed. System Programmer Response: If an installation-provided
Source: Input/output supervisor (IOS) program issued the SETEVENT, ensure that the program is author-
ized. Correct the error indicated by the reason code. Run the job
System Action: The system abnormally ends the current task.
again.
Programmer Response: Rerun the job.
If an IBM-provided program issued the SETEVENT, collect all printed
System Programmer Response: Search problem reporting data output and output data sets related to the problem. Search problem
bases for a fix for the problem. If no fix exists, contact the IBM reporting data bases for a fix for the problem. If no fix exists, contact
Support Center. the IBM Support Center. Provide the SYSOUT output and the dump
for the job.
0F3
Explanation: A hard machine check interruption occurred.
Source: Machine check handler (MCH)
System Action: The system abnormally ends the task that was
running when the machine check interruption occurred.
Programmer Response: If the data on external storage devices is
still valid, run the job step again. If the data is not valid, notify the
system programmer.
System Completion Codes SCC-79
0F7 0F7
20 While attempting to write the job control table (JCT) to
0F7
spool, the job termination routine received a nonzero
Explanation: The system found a serious error condition in the return code, probably because of one of the following:
JES2 component specific user environment (HASCxxxx) load
An I/O error
modules. The REASON parameter on the ABEND macro specifies a
JCT storage was overlaid.
hexadecimal reason code that further explains the error. The system
records the hexadecimal reason code associated with this abend in a Following is the text associated with this reason code:
logrec data set record. ‘UNABLE TO WRITE JCT’.
Code Explanation 24 Without holding a subsystem job block (SJB) lock, the
caller attempted to obtain the job communication queues
00 A subsystem interface (SSI) function was unable to
lock ($SVJLOK) that serializes communication between
cancel an outstanding ESTAE recovery program, prob-
address spaces. Following is the text associated with
ably because the TRETOKEN field in the TCB recovery
this reason code: ‘$SVJ LOCK REQUEST FAILED’.
element ($TRE) control block was overlaid during that
SSI function. Following is the text associated with this 28 A TCB attempted to preempt a holder of the SJB lock
reason code: ‘UNABLE TO CANCEL ESTAE’. while producing a dump for an abend that occurred while
the SJB lock was held. Following is the text associated
04 A task attempted to acquire the lock of two distinct sub-
with this reason code: ‘UNABLE TO OBTAIN SJB
system job blocks (SJBs); a task may lock only one SJB
LOCK’.
at a time. Following is the text associated with this
reason code: ‘ATTEMPT MADE TO LOCK TWO SJBS 2C Storage could not be obtained for the service request
AT ONCE’. block (SRB) work area. Following is the text associated
with this reason code: ‘HASCDSS DATA SPACE SER-
08 While attempting to return a common storage area
VICES FAILURE’.
(CSA) cell to the cell pool, $FRECEL routine found one
of the following error conditions: 30 HASCDSS was entered with a function other than
CREATE or DELETE. Following is the text associated
The cell being returned does not have a valid cell
with this reason code: ‘HASCDSS DATA SPACE SER-
control element (CCE) address at offset 0
VICES FAILURE’.
The cell being returned has not been allocated.
34 The value given for the BLOCKS parameter was either
Storage has been overlaid in either the first four bytes of
negative or zero. Following is the text associated with
the cell being returned, or in the CCE associated with
this reason code: ‘HASCDSS DATA SPACE SERVICES
the cell. Following is the text associated with this reason
FAILURE’.
code: ‘INVALID/UNCLAIMED CELL ADDRESS’.
38 RMTR EXIT recovery processing was entered. Following
0C During a functional subsystem or functional subsystem
is the text associated with this reason code: ‘HASCDSS
application (FSS/FSA) disconnect, a GETMAIN failed to
DATA SPACE SERVICES FAILURE’.
obtain storage from subpool 230 for a parameter list.
Following is the text associated with this reason code: 3C FRR recovery processing was entered. Following is the
‘DISCONNECT DENIED-- GETMAIN FAILURE’. text associated with this reason code: ‘HASCDSS DATA
SPACE SERVICES FAILURE’.
10 During the Job Termination SSI function, the final
input/output table (IOT) could not be written to spool. 40 The MVS macro DSPSERV failed. Following is the text
Following is the text associated with this reason code: associated with this reason code: ‘HASCDSS DATA
‘UNABLE TO WRITE FINAL IOT CHAIN’. SPACE SERVICES FAILURE’.
14 While attempting to end processing for a job under the 44 The MVS macro ALESERV failed. Following is the text
control of an execution batch monitor (joblet), the Job associated with this reason code: ‘HASCDSS DATA
Termination SSI was unable to locate the PDDB for the SPACE SERVICES FAILURE’.
job journal. (The PDDB is the control block that defines 48 The address space control block (ASCB) for the address
a spool data set.) Therefore, the Job Termination SSI space that will own the data space is not equal to the
could not nullify the joblet-related spool dataset so that it current ASCB. Following is the text associated with this
could be reused for the next joblet. Following is the text reason code: ‘HASCDSS DATA SPACE SERVICES
associated with this reason code: ‘UNABLE TO FIND FAILURE’.
JOB JOURNAL PDDB’.
4C Incorrect $DSWA version number. Following is the text
18 The common storage $RETURN service determined that associated with this reason code: ‘HASCDSS DATA
there was no previous save area address associated SPACE SERVICES FAILURE’.
with the current save area. Therefore, the service was
unable to return to the proper location. Following is the 50 JES2 SAVE/RETURN services detected an error. Fol-
text associated with this reason code: ‘NO PREVIOUS lowing is the text associated with this reason code:
SAVE AREA FOUND’. ‘CALLER ADDRESS ARRAY FILLED UP’.
1C The JES2 exit effector determined that the exit was 54 JES2 SAVE/RETURN services detected an error. Fol-
invoked from an FSS assembly environment. However, lowing is the text associated with this reason code: ‘NO
while attempting to load the address of the HFCT control ENTRY IN CALLER ADDRESS ARRAY.’
block for the exit, the exit effector found that the address 58 JES2 SAVE/RETURN services detected an error. Fol-
space was not properly initialized. Following is the text lowing is the text associated with this reason code:
associated with this reason code: ‘ASXBJSVT DOES ‘$RETURN - SAVE AREA HAS IMPROPER FORMAT.’
NOT CONTAIN FSVT ADDRESS’.
SCC-80 OS/390 V2R8.0 MVS System Codes
0F7 0F7
5C JES2 SAVE/RETURN services detected an error. Fol- B0 JES2 detected a problem in an SJB. The SJB is not on
lowing is the text associated with this reason code: the queue indicated in SJBQUEUE. The SJB address is
‘ENTERED $SSIEND WITH AN OUTSTANDING in register 10.
$SAVE’.
B4 JES2 detected a problem in an SJB. The SJB is not on
60 JES2 detected an error while processing a scheduler the queue indicated in SJBQUEUE. The SJB address is
JCL facility request. Following is the text associated in register 10.
with this reason code: ‘SJF SERVICE REQUEST
B8 Following an unrecoverable I/O error, JES2 detected that
FAILED’.
channel-end processing requested, incorrectly, to re-
64 JES2 detected an error while grouping SYSOUT. Fol- drive the I/O. The text associated with the reason code
lowing is the text associated with this reason code: is: INTERNAL ERROR IN CHANNEL END PROC-
‘INVALID GROUPING STRINGS OBJECT’. ESSING
68 JES2 detected an error while grouping SYSOUT. Fol- BC JES2 detected a problem during a rebuild of the SJB
lowing is the text associated with this reason code: queues. Either the $HAVT is bad, or the SVJ lock was
‘SWBTUREQ RETRIEVE ERROR’. not held at entry to the rebuild routine.
6C JES2 detected an error while grouping SYSOUT. Fol- C0 The caller of SJBRQ attempted to move the SJB to a
lowing is the text associated with this reason code: different job communication queue, but did not hold the
‘INVALID STORAGE BLOCK POINTER’. SVJ lock.
70 JES2 detected an error while grouping SYSOUT. Fol- C4 An invalid SAPID pointer was passed in the SSS2
lowing is the text associated with this reason code: (SAPI, IAZSSS2) SSOB extension.
‘SJFREQ KEYLIST ERROR’.
C8 The fields that should be zeroes in the SSS2 (SAPI,
74 JES2 detected an error while building a generic grouping IAZSSS2) SSOB extension were not zeros.
token. Following is the text associated with this reason
CC An SJF Request error occurred on an GETDS/SAPI
code: ‘UNEXPECTED NUMBER OF SWBIT BUFFERS’.
request.
78 JES2 SAVE/RETURN services detected an error. Fol-
D4 The MVS Cell Pool Service returns a non-zero return
lowing is the text associated with this reason code:
code when JES2 calls the MVS service to process
‘ENTERED $SSIEND WITH AN OUTSTANDING
$CPOOL ACTION=GET request. Following is the text
$ESTAE’.
associated with the reason code: ‘$CPOOL
7C JES2 detected an error while unlocking a $SJB. Fol- ACTION=GET FAILED TO ALLOCATE THE CELL’.
lowing is the text associated with this reason code: ‘SJB
D8 The MVS Cell Pool Service returns a non-zero return
UNLOCK NOT BY LOCK HOLDER’.
code when JES2 calls the MVS service to process
80 JES2 detected an error while freeing storage buffers. $CPOOL ACTION=FREE request. Following is the text
Following is the text associated with this reason code: associated with the reason code: ‘$CPOOL
‘NOT ALL PROTECTED BUFFERS $FREEBUFED’. ACTION=FREE FAILED TO FREE THE CELL’.
84 The $GETHP service detected an error while freeing a | DC When processing a PSO SSI request, JES2 discovered
task control block recovery element ($TRE). Following is | that the $PSO control block is in error. Following is the
the text associated with this reason code: ‘$GETHP | text associated with the reason code: ’$PSO NOT
ERROR - ATTEMPTED TO FREE THE TRE’. | VALID’.
88 The FRETRE service detected a loop in the cell pool System Action: If an SSI function took the $ERROR, the system
chain. produces a dump (unless the dump is suppressed by dump analysis
elimination (DAE)), and the SSI function's caller receives a disas-
8C The GETTRE service detected an error in the $TRE cell
trous error indication upon return. Otherwise, the system abnormally
pool chain. Following is the text associated with this
ends the program.
reason code: ‘GETTRE ERROR’.
Programmer Response: Take one of the following actions,
90 The system encountered a failure while serializing a
depending on the reason code associated with this abend:
JES2 trace table entry. Following is the text associated
with this reason code: ‘$TRACER Trace Table ENQ Code Response
Error’
00 Determine whether the task control block recovery
98 A routine in CSECT HASCRQUE detected an erroneous element ($TRE) control block was properly addressed,
input parameter. and whether that control block has been overlaid.
9C An incorrect resource number was passed to the 04 Ensure that you release the lock for one SJB before you
$$POST macro. attempt to acquire the lock of another SJB.
A0 JES2 detected inconsistent temporary protected buffer 08 Verify that offset 0 of the cell points to a valid CCE, and
pointers. shows that the cell is allocated.
A4 JES2 requested an ENQ for the SVJ lock but received 0C Determine why subpool 230 has been depleted. Correct
an unexpected return code. The return code from ENQ the error.
is in register 2.
10 Determine why $CBIO failed while attempting to write
A8 JES2 detected a problem in an SJB. The SJB is not on the IOT chain. Refer to OS/390 JES2 Macros for infor-
the expected queue. The SJB address is in register 10. mation about the return codes for $CBIO.
AC JES2 detected a problem in an SJB. The SJBQUEUE
field is not valid. The SJB address is in register 10.
System Completion Codes SCC-81
0F8 0F9
14 Determine why the PDDB cannot be located. Correct the In the system trace, get the ASID from the SVCE D entry
error. Note that an SSI ESTAE recovery program is not for abend X'0F8'.
active for this abend because the call to end the job
3. Use the program status word (PSW) address at the time of error
originates from the HASCHAM assembly module.
to identify the module that abended.
18 Determine whether the save area has been overlaid; if
For an installation-provided module, continue diagnosis with
not, determine whether the caller intended to issue a
the module.
$RETSAVE macro instead and correct any errors found
in the $RETSAVE macro. For an IBM module, continue diagnosis as follows:
1C Ensure that the following conditions are met: – For reason code X'08', go to step 4.
– For any other reason code, go to step 5.
The assembly module that issued the $EXIT call is
assembled with the correct ENVIRON parameter on 4. For reason code X'08', determine which lock was held by the
the $MODULE statement. issuer of the SVC. If you have not already obtained an SVC
The FSS address space is fully initialized before the dump, ask the operator to set a SLIP trap to obtain an SVC
$EXIT call is attempted. dump. In the system trace, look at the SVCE D entry for com-
pletion code X'0F8'. The PSACLHS column contains the
20 Determine why $CBIO failed while attempting to write
current lock held string at the time of the error.
the IOT chain. Refer to OS/390 JES2 Macros for infor-
mation about the return codes for $CBIO. Use the PSACLHS field in the prefix save area (PSA) to deter-
mine which lock was held at the time of error.
24 Ensure that the caller holds an SJB lock before
attempting to obtain the $SVJLOK. 5. Search problem reporting data bases for a fix for the problem.
For reason code X'08', include in the search argument the
28 Determine the caller of the $SJBLOCK routine. Notify
name of the lock held, as determined in step 4. If no fix exists,
your programming support personnel.
contact the IBM Support Center. Provide, if available, the SVC
| 2C through DC Contact the IBM Support Center for assistance. dump and the logrec data set error record.
0F8 0F9
Explanation: The issuer of a Supervisor Call (SVC) instruction was Explanation: An error occurred when the system attempted to
not in the correct mode to issue the SVC. A hexadecimal reason acquire or release a supervisor request block (SVRB) in order to
code in the RTM2CRC field of the RTM2WA data area explains the process a Supervisor Call (SVC) instruction. This is probably an
error: error in a program, but not necessarily in the program that abnor-
mally ended. A hexadecimal return code in register 15 explains the
Code Explanation
error:
04 The issuer was in a mode other than task control block
Code Explanation
(TCB) mode.
00 The local system queue area (LSQA) has been
08 The issuer held a lock.
exhausted, so that the SVRB space is not available to
0C The issuer was disabled. honor an SVC instruction in the address space. This
10 The issuer was in cross memory mode. problem may be caused by a loop in the program
issuing the SVC.
14 The issuer had established an enabled, unlocked task
(EUT) mode functional recovery routine (FRR) by speci- 04 An SVRB is being freed, but the system cannot identify it
fying EUT=YES on a SETFRR macro. as belonging to the SVRB pool.
18 The issuer was in access register (AR) address space Source: Supervisor control
control mode. This error applies to only those SVCs that System Action: The system writes a logrec data set error record.
cannot be issued in AR address space control mode. The system abnormally ends the program that was running.
1C The issuer is not authorized to use the SVC microcode System Programmer Response: Do the following:
assist instruction.
1. For reason code X'00', examine the REGION parameter on the
Source: Supervisor control JCL JOB or EXEC statement for the job. If the REGION param-
System Action: The system abnormally ends the program that eter allocates too much private storage, this may be causing a
issued the SVC. The system may write a logrec data set error shortage of available storage for the LSQA. Reduce the value of
record. the REGION parameter.
Operator Response: If the system programmer asks for an SVC 2. For reason code X'04', contact the supervisor control compo-
dump, set the following SLIP trap: nent group at the IBM Support Center. Provide the logrec data
set error record.
SLIP SET,ENABLE,COMP=ðF8,END
3. If the REGION parameter for the job is determined to be reason-
System Programmer Response: Do the following:
able, a complete SVC dump will be needed to diagnose the
1. If a logrec data set error record is not written with the abend, cause of the abend X'0F9' reason code X'00.'. Since a SLIP
ask the operator to set a SLIP trap to obtain an SVC dump. on an abend X'0F9' with A=SVCD will not produce a complete
2. Identify the address space where the abend occurred by doing SVC dump, and since an abend X'0F9' is nearly always pre-
one of the following: ceded by either an abend X'878' or X'80A', the following two
SLIPs should be set to obtain a useful SVC dump.
In the logrec data set error record, find the address space
SLIP SET,C=878,A=SVCD,J=failingjob,END
identifier (ASID) of the address space.
SLIP SET,C=8ðA,A=SVCD,J=failingjob,END
SCC-82 OS/390 V2R8.0 MVS System Codes
0FB 0FF
nent group associated with this module at the IBM Support
0FB
Center. Provide the SVC dump and, if available, the logrec
Explanation: A translation exception has occurred. The system data set error record.
detected an incorrect value in control register 0.
Source: Supervisor control 0FE
System Action: The system abnormally ends the program experi- Explanation: An error was detected while RMF was sampling data
encing the error. The system may write a logrec data set error about the state of the system.
record. Source: Resource Measurement Facility (RMF)
Operator Response: If the system programmer asks for an SVC System Action: All RMF measurement collection is terminated.
dump, set the following SLIP trap: Reinstatement of RMF can be attempted, and, if successful, RMF
SLIP SET,COMP=ðFB,ACTION=SVCD,END continues under the control of the original options. If reinstatement
fails, RMF is terminated.
System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, ask the operator to The system writes an ABEND dump for the failing job step.
set a SLIP trap to obtain an SVC dump. Contact the IBM Support System Programmer Response:
Center. Provide the SVC dump and, if available, the logrec data set
error record. Obtain the ABEND dump for the failing job step. If the JCL for the
step did not contain a DD statement for an ABEND dump, add one
of the following statements and run the job step again:
0FC
SYSABEND DD statement
Explanation: A program referenced data in an address space other
SYSMDUMP DD statement
than its home address space. That address space has either:
SYSUDUMP DD statement
Incorrect data in its dynamic address translation (DAT) tables
Use a SYSMDUMP DD statement if you plan to analyze and format
An incorrect segment table origin (STO) address the dump with the interactive problem control system (IPCS).
This error is probably in the system. Obtain the logrec data set error record.
Source: Recovery termination manager (RTM) Search problem reporting data bases for a fix for the problem. If no
System Action: The system abnormally ends the program and fix exists, report the problem to the IBM Support Center.
ends the address space.
0FF
System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Explanation: The system encountered an error while processing a
Support Center. DATOFF Move Long (MVCL) instruction. A hexadecimal reason code
in register 15 explains the error:
0FD Code Explanation
Explanation: The Type 6 SVC routine issued the T6EXIT macro to 04 Index given to DATOFF was out of range.
schedule a cross memory service request block (SRB), but the
Source: Supervisor control
SRBASCB address is not the same as the current memory address.
This is a probably an error in the SVC routine. System Action: The system abnormally ends the program that
issued the instruction.
Source: Supervisor control
System Action: The system abnormally ends the program that
issued the T6EXIT macro. The system may write a logrec data set 101
error record.
Explanation: During processing of a WAIT macro, the system
Operator Response: If the system programmer asks for an SVC found that the problem program specified more events than there
dump, set the following SLIP trap: were event control blocks (ECB).
SLIP SET,COMP=ðFD,ACTION=SVCD,END Source: Task management
System Programmer Response: Do the following: System Action: The system abnormally ends the program that
1. Ask the operator to set a SLIP trap to obtain an SVC dump. issued the WAIT macro.
2. In the system trace, back up to the *RCVY entry for abend Programmer Response: Change the events specified to less than
X'0FD'. Look for an SVC entry, other than SVC D, prior to the or equal to the number of ECBs. If the specification was correct,
*RCVY entry for this abend. In the entry, note the address in the ensure that it was not incorrectly modified. Correct the error. Run
PSW ADDR column. the job again.
3. Use the address in the PSW to identify the module that issued System Programmer Response: If the error recurs and the
the T6EXIT macro. 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
For an installation-provided module, continue diagnosis with
problem. If no fix exists, contact the IBM Support Center. Provide the
the module.
program listing for the job.
For an IBM module, search problem reporting data bases
for a fix for the problem. If no fix exists, contact the compo-
System Completion Codes SCC-83
102 106
System Programmer Response: See installation procedures to
102
increase the central storage requirements.
Explanation: During processing of a POST macro, the system
found an incorrect address for an event control block (ECB). 106
Register 15 contains a hexadecimal reason code that explains the Explanation: An error occurred during processing of a LINK(X),
error: LOAD, ATTACH(X), or XCTL(X) macro.
Code Explanation An error was detected by the control program when it attempted to
00 Incorrect ECB for a POST macro in the caller's key. That fetch the requested program into virtual storage. The return code in
is, the caller's key does not match the storage protection register 15 identifies the error; see accompanying message CSV011I
key. to determine the reason code.
04 Incorrect ECB for a cross memory POST (XMPOST) Code Explanation
macro. 0B An error occurred during FETCH processing or in one of
08 The problem program passed an incorrect ECB address. the routines that gets control as a result of FETCH proc-
essing.
0C The caller passed an incorrect ECB address for an
XMPOST. 0C Not enough storage was available for FETCH to get
storage for the module or control blocks.
Source: Task management
Code Explanation
System Action: The system abnormally ends the program that
issued the POST macro. 04 No storage for DATD.
Programmer Response: Ensure that the specified ECB address is 08 No storage for data extent block (DEB).
a valid virtual storage address and that the address was not incor- 0C No storage for I/O supervisor block (IOSB).
rectly modified. Also, ensure that the program issuing the POST
macro has a storage protection key that allows it to update the ECB. 10 No storage for EXLIST.
Correct the error. Run the job again. 14 No storage for module.
System Programmer Response: If the error recurs and the 18 Unable to fix storage.
program is not in error, look at the messages in the job log for more
0D The control program found an incorrect record type in
information. Search problem reporting data bases for a fix for the
the load module.
problem. If no fix exists, contact the IBM Support Center. Provide the
program listing for the job. 0E The control program found an incorrect address in the
load module.
104 Code Explanation
Explanation: An error occurred when the system tried to process 20 Error converting TTR. One of the following
an EU, LU, or VU form of the GETMAIN macro. The GETMAIN occurred:
requested virtual storage that requires more central storage than is
A job opened a data set with
available. A reason code in the SDWACRC field of the system diag-
DISP=SHR, and another job updates
nostic work area (SDWA) explains the error:
the data set causing the extents in the
Code Explanation data set to increase.
04 There is not enough central storage available to back a An error occurred in an application
request for space in a system queue area (SQA) program, for example, while retrieving a
subpool. directory entry using build link-list
08 There is not enough central storage available to back a (BLDL) from one DCB and passing that
request for space in a fixed common service area (CSA) entry and a different DCB to the LOAD
subpool. or LINK macro.
0C There is not enough central storage available to back a 24 Block is outside of the module.
request for space in a local system queue area (LSQA) 28 The address constant location is incorrect.
subpool.
0F Either an uncorrectable I/O error occurred, or an error in
1C The system could not satisfy a request for an LSQA the load module caused the channel program to fail. See
subpool. The page table for the segment describing the the accompanying IEW message for a description of the
area to be obtained was paged out. data set error.
20 The system could not satisfy a request for an authorized Code Explanation
private area subpool. The page table for the segment
40 I/O error on a PDS.
describing the area to be obtained was paged out.
44 Error on a virtual DS.
Source: Virtual storage manager (VSM)
48 Seek address outside extent.
System Action: The system issues message IEA705I. The system
abnormally ends the current task. 4C Possible program-controlled interrupt (PCI)
logic error.
Programmer Response: Ensure that the calling program is not
requesting too much central storage. 10 The control program detected a relocation error in the
load module.
If the system issues this abend frequently, notify the system pro-
grammer. 28 Internal error occurred during fetch processing.
SCC-84 OS/390 V2R8.0 MVS System Codes
10A 10E
Source: Contents supervision (CSV) System Programmer Response: See installation procedures to
increase the central storage requirements.
System Action: The task is ended unless ERRET was specified on
the macro. The system issues message CSV011I.
10B
Operator Response: Notify the system programmer.
Explanation: Timer supervision found an error on the input param-
Programmer Response: For a return code of:
eters for the TIME macro.
X'0C' with a reason code of:
Source: Timer supervision
– X'14', increase the region size.
System Action: The system takes an SVC dump.
– X'04', X'08', or X'10' try decreasing the region size. If
System Programmer Response: Use the program status word
the problem recurs, notify the system programmer.
(PSW) address in the CLK entry to identify the caller. Do one of the
X'0D', or X'0E' (reason code of X'24' or X'28'), ensure that following:
the load module was not altered so that it is no longer valid. If
If the caller is provided by the installation, check the parameters
the load module is valid, then notify the system programmer.
on the TIME macro. If MIC or STCK was specified, the area
X'0E' (reason code of X'20'), if the error occurred because a specified by the address must have the caller's storage protect
different job updated the data set extents, then restart the job so key.
that the extent list is updated (if the error occurred with the
If the caller is provided by IBM, search problem reporting data
LINKLIST, the system must be IPLed to fix the problem).
bases for a fix for the problem.
System Programmer Response: For a return code of:
If the PSW does not contain the caller's address, contact the
X'0F', resubmit the job. Then have the operator enter a START IBM Support Center.
GTF command specifying tape output, MODE=EXT and
TIME=YES. Have the operator reply TRACE=IO in response to 10D
message AHL100A.
Explanation: A job step task abnormally ended, but it had a
Format the output with the IPCS GTFDATA subcommand. subtask with a status of step must complete (MC). This completion
X'0B', X'0D', X'0E' (reason code of X'24' or X'28'), X'28', code is found only in the job step task.
or if the problem persists, search problem reporting data bases Source: Recovery termination manager (RTM)
for a fix for the problem. If no fix exists, contact the IBM Support
Center. System Action: The system abnormally ends the subtask. The
system sends messages about the problem to the job log.
10A System Programmer Response: Find the abend code for the task
that attached the abended subtask in:
Explanation: An error occurred when the system tried to process
an R form of the GETMAIN macro. The GETMAIN requested virtual Messages in the job log
storage that required more central storage than is available. A The logrec data set error record
reason code in the SDWACRC field of the system diagnostic work
area (SDWA) explains the error: The TCBCMP field of the task control block (TCB) for the
attaching task, if a dump is available
Code Explanation
Diagnose the original abend in the attaching task.
04 There is not enough central storage available to back a
request for space in a system queue area (SQA)
10E
subpool.
Explanation: A program issued a SPIE macro. The macro specified
08 There is not enough central storage available to back a
an incorrect address for the program interruption control area (PICA).
request for space in a fixed common service area (CSA)
subpool. Source: Recovery termination manager (RTM)
0C There is not enough central storage available to back a System Action: The system sends messages about the problem to
request for space in a local system queue area (LSQA) the job log. The system abends the program.
subpool. Operator Response: If the system programmer asks for an SVC
1C The system could not satisfy a request for an LSQA dump, set the following SLIP trap:
subpool. The page table for the segment describing the SLIP SET,COMP=1ðE,ACTION=SVCD,END
area to be obtained was paged out.
System Programmer Response: Do the following:
20 The system could not satisfy a request for an authorized
private area subpool. The page table for the segment If the program is installation-provided code, correct the PICA
describing the area to be obtained was paged out. address.
Source: Virtual storage manager (VSM) If the program is IBM code, search problem reporting data bases
for a problem fix. If no fix exists, contact the IBM Support
System Action: The system issues message IEA705I. The system Center. Provide:
abnormally ends the current task.
– Messages from the job log
Programmer Response: Ensure that the calling program is not – The ABEND or SVC dump
requesting too much central storage. – The assembly listing for the job
If the system issues this abend frequently, notify the system pro- – The JCL for the job
grammer. – The program listing for the job
System Completion Codes SCC-85
110 119
DCB address prior to issuing SVC 21, and that the DCB has not
110
been overlaid since it was opened.
Explanation: While the system was processing a PURGE macro,
System Programmer Response: If the error recurs and the
an error occurred when the system tried to process the parameter
program is not in error, look at the messages in the job log for more
list for the macro.
information. 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. Provide the
System Action: The system ends the program that issued the JCL and the program listing for the job.
PURGE macro.
117
Programmer Response: Correct the pointer to the purge param-
eter list in the PURGE macro. Explanation: The error occurred during processing of a BSAM
CLOSE macro instruction with a TYPE=T operand. This system com-
112 pletion code is accompanied by message IEC218I. Refer to the
explanation of message IEC218I for complete information about the
Explanation: Incorrect input was passed to SVC 18 by the BLDL or task that was ended and for an explanation of the return code (rc in
FIND macro instruction. This system completion code is accompa- the message text) in register 15.
nied by message IEC908I. Refer to the explanation of message
IEC908I for complete information about the task that was ended and Source: DFSMSdfp
for an explanation of the return code found in register 15. Programmer Response: Respond as indicated for message
Source: DFSMSdfp IEC218I.
System Action: For return codes 13 and 14, the DCB was written System Programmer Response: If the error recurs and the
to the GTF trace data set. 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
Operator Response: Start a generalized trace facility (GTF) trace, problem. If no fix exists, contact the IBM Support Center. Provide the
and re-create the problem. Reply to message AHL100A with: JCL and the program listing for the job.
TRACE=SYS,USR,SLIP
On the DD statement for the data set in error, specify: 118
DCB=DIAGNS=TRACE Explanation: Incorrect parameters were passed to DEVTYPE (SVC
24). This system completion code is accompanied by message
Programmer Response: Correct the BLDL or FIND macro instruc-
IEC912I. Refer to the explanation of message IEC912I for complete
tion. For return codes 03, 13, 04, and 14, make sure that the DCB is
information about the task that was ended and for an explanation of
not being overlaid, in particular, the fields DCBEBAD and
the return code found in register 15.
DCBPOINT. Recompile the program and run the job step again.
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 Programmer Response: Correct the DEVTYPE macro instruction,
information. Search problem reporting data bases for a fix for the recompile the program, and rerun the job step.
problem. If no fix exists, contact the IBM Support Center. Provide the System Programmer Response: If the error recurs and the
JCL and the program listing for the job. 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
113 problem. If no fix exists, contact the IBM Support Center. Provide the
Explanation: The error occurred during processing of an OPEN JCL and the program listing for the job.
macro instruction or an OPEN macro instruction with a TYPE=J
operand. This system completion code is accompanied by message 119
IEC142I. Refer to the explanation of message IEC142I for complete Explanation: Incorrect input was passed to SVC 25. This system
information about the task that was ended and for an explanation of completion code is accompanied by message IEC914I. Refer to the
the return code (rc in the message text) in register 15. explanation of message IEC914I for complete information about the
Source: DFSMSdfp task that was ended and for an explanation of the return code found
in register 15.
Programmer Response: Respond as indicated for message
IEC142I. Source: DFSMSdfp
System Programmer Response: If the error recurs and the System Action: For return codes 12 and 13, the DCB is written to
program is not in error, look at the messages in the job log for more the GTF trace data set. For return code 14, both the DCB and IOB
information. Search problem reporting data bases for a fix for the are written.
problem. If no fix exists, contact the IBM Support Center. Provide the Operator Response: Start a generalized trace facility (GTF) trace,
JCL and the program listing for the job. and re-create the problem. Reply to message AHL100A with:
TRACE=SYS,USR,SLIP
115
On the DD statement for the data set in error, specify:
Explanation: The error occurred during the processing of SVC 21
(STOW). The DCB did not point to a valid DEB, or the DEB did not DCB=DIAGNS=TRACE
point back to the DCB. Programmer Response: Make sure that your program does not
Source: DFSMSdfp overlay the DCB and IOB fields described by the error code. Correct
the error, and rerun the job step.
System Action: An unsuccessful attempt was made to invoke the
STOW task recovery routine. System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
Programmer Response: Verify that register 1 contained the correct
SCC-86 OS/390 V2R8.0 MVS System Codes
11A 12C
information. Search problem reporting data bases for a fix for the information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job. source program listing for the job.
11A 12A
Explanation: The error occurred trying to store into a user-supplied Explanation: During processing of an ATTACH macro, the system
OS/VS CAMLST work area. found an error. In a GSPV or GSPL operand, the macro specified
that a subpool was to be given to the subtask being created.
Source: DFSMSdfp
Register 15 contains a hexadecimal reason code that explains the
System Action: SVC 26 received a protection check because the
error:
protect key of the supplied work area did not match the user's
protect key. Code Explanation
Programmer Response: Correct the pointer in the OS/VS 00 The attaching task owned the subpool, but had previ-
LOCATE parameter list to the LOCATE work area, and run the job ously shared it with other subtasks through SHSPV
step again. and/or SHSPL operands. A task cannot give an owned
subpool to a subtask if that task shared the subpool with
System Programmer Response: If the error recurs and the
other subtasks.
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 04 The specified subpool contains data-in-virtual (DIV)
problem. If no fix exists, contact the IBM Support Center. Provide the mapped storage; such a subpool cannot be specified
JCL and the program listing for the job. with GSPV or GSPL.
08 The specified subpool contains storage that had been
121 specified on the IARSUBSP macro with the IDENTIFY
Explanation: A module tried to stop I/O activity by issuing the parameter, and the storage is eligible to be assigned to
IOHALT macro with the low order bit of register 1 off. a subspace. Ownership of a subpool eligible to be
assigned to a subspace cannot be passed to an
Source: Input/output supervisor (IOS) attached subtask.
System Action: The system abnormally ends the program that Source: Task management
issued the IOHALT macro.
System Action: The system abnormally ends the program that
Programmer Response: Change the program that issued the issued the ATTACH macro.
IOHALT macro so it sets the low order bit of register 1 on.
Programmer Response: Change the ATTACH macro to specify
System Programmer Response: If the IOHALT macro is issued the subpool in an SHSPV or SHSPL operand. Correct the error.
within the system code, search problem reporting data bases for a fix Run the job again.
for the problem. If no fix exists, contact the IBM Support Center.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
122
information. Search problem reporting data bases for a fix for the
Explanation: The operator canceled the job and requested a dump. problem. If no fix exists, contact the IBM Support Center. Provide the
Source: Master scheduler source program listing for the job.
System Action: The system ends the job. The system writes a
12C
dump to the data set described by the SYSABEND, SYSMDUMP or
SYSUDUMP DD statement in the canceled job step. Explanation: During processing of a CHAP macro, the system
found an incorrect address for the task control block (TCB) for the
Programmer Response: Find out why the operator canceled the
subtask whose priority was to be changed. The second operand of
job. Correct the error(s). Resubmit the job.
a CHAP macro points to a fullword that contains the TCB address.
128 The address was incorrect for one of the following reasons:
Explanation: During processing of an EXTRACT macro, the It was not a valid TCB address.
system found an incorrect address for the list to hold the requester The valid TCB at the address was not associated with a subtask
fields. The beginning address for the list did not define a fullword of the task issuing the macro.
boundary, or the list did not begin and end within the storage
It was not a multiple of 4.
assigned to the job step.
The valid task has abnormally ended.
The first operand of the macro specifies the beginning address of the
list. The number of fields requested determines the length of the list. Source: Task management
Source: Task management System Action: The system abnormally ends the program that
issued the CHAP macro.
System Action: The system abnormally ends the program that
issued the EXTRACT macro. Programmer Response: Change the address specification. Ensure
that it and the TCB were not incorrectly modified by the problem
Programmer Response: Determine if the first operand of the
program. Correct the error. Run the job again.
macro was specified correctly or if program errors had incorrectly
modified the EXTRACT macro expansion. Correct the error. Run the System Programmer Response: If the error recurs and the
job again. 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
System Programmer Response: If the error recurs and the
problem. If no fix exists, contact the IBM Support Center. Provide the
program is not in error, look at the messages in the job log for more
source program listing for the job.
System Completion Codes SCC-87
12D 130
requests, the requested time interval (BINTVL, DINTVL,
12D
MICVL, or TUINTVL) added to the current TOD clock
Explanation: A program requested an overlay. When trying to contents would have exceeded
answer the request, the overlay supervisor found that words 3 and 4 X'FFFFFFFFFFFFFFFF' (a value that would expire on
of the overlay segment table are incorrect. September 17, 2042). A value greater than
The overlay segment table is used by the overlay supervisor; it X'7FFFFFFF' was specified for BINTVL.
resides in the load module and is in the same storage protection key Source: Timer supervision
as the application program.
System Action: The STIMER routine produces a tailored dump
Note: Overlay programs run only in 24-bit addressing mode, not in that provides the following information:
31-bit addressing mode.
The control blocks associated with the task that issued the
Source: Overlay supervisor STIMER request
System Action: The system abnormally ends the program that The register contents for the task that issued the STIMER
requested the overlay. The system writes an ABEND dump, if a request
dump DD statement is provided.
The virtual subpools that contain the parameter list passed to
Programmer Response: Check the program for errors that caused STIMER
the overlay segment table to be incorrectly modified. Correct the
Programmer Response: Depending on the reason code, one of
errors; then assemble, link edit, and run the program again.
the following:
Code Explanation
12E
00 Check the spelling of the data area name on the
Explanation: A program issued a TTIMER macro with incorrect
STIMER request.
parameters.
04 Do not specify the TASK parameter with the GMT and
Source: Timer supervision
TOD parameters on the STIMER request.
System Programmer Response: Use the program status word
0C Change the value for the GMT and/or TOD parameter(s)
(PSW) address in the CLK entry to identify the caller. Do one of the
to one that is less than 2400.
following:
14 Check that a program running in 31-bit addressing mode
If the caller is provided by the installation, check the parameters
uses the MVS/SP Version 2 or later version of the
on the TIME macro. If MIC or STCK was specified, the area
STIMER macro.
specified by the address must have the caller's storage protect
key. 10 Change the parameter address so it is in the caller's
addressable storage.
If the caller is provided by IBM, search problem reporting data
bases for a fix for the problem. 28 Ensure that the specified time interval is correct.
If the PSW does not contain the caller's address, contact the
IBM Support Center. 130
Explanation: Global resource serialization found an error during
12F processing of the DEQ macro instruction.
Explanation: A program issued an STIMER macro with incorrect The DEQ macro instruction specified a resource not previously spec-
parameters. A reason code in register 15 explains the error: ified by an ENQ macro instruction under the same task. In other
words, the program was attempting to release a resource that was
Code Explanation
not previously requested. The DEQ macro instruction did not specify
00 The system could not find a data area that was specified a RET=HAVE operand.
on a parameter for an STIMER request.
System Action: The system issued an ABEND dump.
04 The Greenwich mean time (GMT) or local time of day
Source: Global resource serialization
(LT or TOD) parameter was specified for a TASK type
STIMER request. System Action: The system issues an ABEND dump.
0C The value for the Greenwich mean time (GMT) or local Programmer Response: Do one of the following:
time of day (LT or TOD) parameter was greater than Check the DEQ macro instruction for incorrect qname or rname
24:00:00.00. operands
10 The STIMER service routine cannot access the storage Specify RET=HAVE in the DEQ macro instruction
containing the user-specified parameters for the STIMER Add an ENQ macro instruction for the same resource before the
macro. DEQ macro instruction
14 The STIMER service routine received an STIMER macro Then recompile and rerun the program.
parameter that was not valid. For example, a program If the problem persists, do the following:
running in 31-bit addressing mode is not using the
MVS/SP Version 2 or later version of the STIMER 1. Obtain the address of the DEQ parameter list from register 1 in
macro. the UNIQUE-3 column of the SVC 30 or SVC 38 entry in the
system trace.
28 The requested time interval was too large. One of these
situations occurred: For TASK type requests, the 2. Check the parameter list against the SVC 30 or 38 mapping.
requested MICVL time interval was larger than When analyzing the parameter list, remember that the unit
X'7FFFFFFFFFFFFFFF'. For REAL/WAIT type control block (UCB) pointer, if present, is the address of a field
that, in turn, contains the address of the UCB.
SCC-88 OS/390 V2R8.0 MVS System Codes
133 138
If the parameter list contains incorrect data, continue diagnosis Provide the SYSOUT output for the job and all printed output and
in the program that issued the macro. output data sets related to the problem.
System Programmer Response: If the problem persists, search
problem reporting data bases for a fix for the problem. If no fix 137
exists, contact the IBM Support Center. Provide the ABEND dump. Explanation: The error occurred at an end-of-volume on a mag-
netic tape. This system completion code is accompanied by
133 message IEC022I. Refer to the explanation of message IEC022I for
complete information about the task that was ended and for an
Explanation: An unauthorized program requested an SVC dump.
explanation of the return code (rc in the message text) in register 15.
To request an SVC dump through an SDUMP macro (SVC 51), the
Source: DFSMSdfp
program must be one of the following:
Programmer Response: Respond as indicated for message
Authorized by the authorized program facility (APF)
IEC022I.
In storage key 0-7
System Programmer Response: If the error recurs and the
To request an SVC dump by a branch entry, the program must be program is not in error, look at the messages in the job log for more
one of the following: information. Search problem reporting data bases for a fix for the
In storage key 0, supervisor state. problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job.
One of the following must be true:
– The caller is in SRB mode. 138
– The caller owns a lock. Explanation: Global resource serialization encountered an error
– The caller is disabled and has a PSASUPER bit set on. occurred during processing of an ENQ macro. One of the following is
true:
– The caller is in enabled unlocked task (EUT) mode. That is,
the caller specified EUT=YES for the SETFRR macro. 1. One ENQ macro instruction was issued for a list of resources.
The same resource appears more than once in the list.
Generally, those modules that cannot issue Supervisor Call (SVC)
instructions can do a branch entry to request an SVC dump. 2. Two ENQ macro instructions were issued for the same resource
in the same task without an intervening DEQ macro instruction
Source: Dumping services
to release the resource. The second ENQ macro instruction did
System Action: The system abnormally ends the program. If a not specify TEST, USE, or HAVE in its RET operand.
recovery routine is available, it is given control. SVC dump proc-
Source: Global resource serialization
essing issues message IEA911E. This message indicates whether
the dump is complete or partial. System Action: Processing continues.
System Programmer Response: For an unauthorized program, Programmer Response:
request an ABEND dump. If the branch entry is being used incor- For the first type of error, delete duplicate resources from the list on
rectly, correct the error or use an SDUMP macro. the ENQ macro instruction.
If the problem persists or is in an IBM-provided program, search For the second type of error, do one of the following:
problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the assembly listing Specify RET=TEST, RET=USE, or RET=HAVE in the second
and the linkage editor output for the job. ENQ macro instruction
Add a DEQ macro instruction between the two ENQ macro
135 instructions
Explanation: An error occurred during the processing associated Delete one of the ENQ macro instructions.
with SVC 53, which obtains and releases exclusive control of a If the problem persists, do the following:
resource associated with a BDAM data set. The task recovery
1. Obtain the address of the DEQ parameter list from register 1 in
routine for this SVC determined that all user control blocks required
the UNIQUE-3 column of the SVC 30 or SVC 38 entry in the
as input to the SVC were in the user's region and key, hence the
system trace.
error could not be ascribed to any user control block.
2. Check the parameter list against the SVC 30 or 38 mapping.
Source: DFSMSdfp
When analyzing the parameter list, remember that the unit
System Action: Message IEC903I is issued. control block (UCB) pointer, if present, is the address of a field
Operator Response: Notify the system programmer. that, in turn, contains the address of the UCB.
System Programmer Response: If the error recurs and the If the parameter list contains incorrect data, continue diagnosis
program is not in error, search problem reporting data bases for a fix in the program that issued the macro.
for the problem. If no fix exists, contact the IBM Support Center. 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.
System Completion Codes SCC-89
139 13E
The issuer of the macro did not obtain the local
139
lock.
Explanation: An error occurred during the processing associated
10 A TOKEN parameter was incorrectly specified as
with SVC 57, which frees a buffer or extends the unscheduled test
follows:
(via the FREEDBUF macro issued either by the user or the system).
The BDAM task recovery routine for this SVC determined that all A program specified the TOKEN parameter on a
user control blocks required as input to the SVC were in the user's macro other than the ESTAE macro.
region and key, hence the error could not be ascribed to any user An unauthorized program issued an ESTAE macro
control block. with the TOKEN parameter.
Source: DFSMSdfp 14 A STAE macro was issued by a program running in
System Action: Message IEC905I is issued. 31-bit addressing mode (AMODE). This is not valid.
Operator Response: Notify the system programmer. 18 An ESTAE or ESTAEX macro with CANCEL=NO param-
eter was issued by a program that:
System Programmer Response: If the error recurs and the
program is not in error, search problem reporting data bases for a fix Is not authorized by APF to do so
for the problem. If no fix exists, contact the IBM Support Center. Is not running in key 0 supervisor state
Provide the SYSOUT output for the job and all printed output and Source: Recovery termination manager (RTM)
output data sets related to the problem.
System Action: The system abnormally ends the program issuing
the macro. If a recovery routine is available, RTM gives it control.
13C The system may write an ABEND dump for the abend if the job step
Explanation: A program issued one of the following macros: provides a dump data set. If so, the LSQA dump option is specified
with the ABEND macro.
ATTACH with an ESTAI parameter
ATTACHX with an ESTAI parameter Operator Response: If the system programmer asks for an SVC
ESTAE dump, set the following SLIP trap:
ESTAEX SLIP SET,COMP=13C,ACTION=SVCD,END
STAE
System Programmer Response: Do the following:
The macro specified an incorrect value, or the environment in which
the macro was running was incorrect. If an installation-provided program issued the incorrect macro,
rewrite the macro or modify the parameter list built by the
A hexadecimal reason code in register 15 explains the error: ESTAE macro.
Code Explanation For reason code X'10', be sure that the TOKEN parameter is
04 An ESTAE or ESTAEX macro was issued. One of the specified only by authorized programs and only on the ESTAE
following errors occurred: macro.
The program is not authorized to issue the macro If it was an IBM program, search problem reporting data bases
for one of these reasons: for a fix for the problem. If no fix exists, contact the IBM Support
Center. Provide:
– The program is not in key 0 through 7
– The assembly listing for the job
– The program is not in supervisor mode
– The ABEND or SVC dump
The macro specified an EXIT address of 0.
The macro specified ESTAE CT, but an exit already 13E
exists. Explanation: The task that created a subtask issued a DETACH
The macro specified ESTAE OV, but the most macro for that subtask, specifying STAE=NO, before the subtask
recent exit is not an ESTAE exit. ended.
08 An ATTACH or ATTACHX macro with ESTAI was This may or may not be an error, depending on the intent of the
issued. One of the following errors occurred: user. Consequently, the system does not abnormally end the task
issuing the DETACH macro.
The macro specified an EXIT address of 0 with CT.
Source: Task management
The macro specified OV.
System Action: The system abnormally ends the subtask to force
The macro specified an incorrect task control block
its completion.
(TCB) address, or did not specify a TCB address at
all. Programmer Response: If the subtask must complete its proc-
essing before being detached, use an ECB or ETXR operand on the
The program calling the ATTACH macro service
ATTACH macro that creates the subtask to achieve synchronization.
routine is not the ATTACH macro.
System Programmer Response: If the error recurs and the
0C An ESTAE or ESTAEX macro with BRANCH=YES was
program is not in error, look at the messages in the job log for more
issued. One of the following errors occurred:
information. Search problem reporting data bases for a fix for the
The macro is not running under a supervisor problem. If no fix exists, contact the IBM Support Center. Provide the
request block (SVRB). source program listing for the job.
The program calling the ESTAE service routine is
not the ESTAE macro.
SCC-90 OS/390 V2R8.0 MVS System Codes
13F 14A
13F 147
Explanation: An error has been detected during checkpoint restart Explanation: A program check or abnormal end occurred in the
processing. This completion code is accompanied by message Graphics Access Method/System Product (GAM/SP) buffer manage-
IHJxxxI with the appropriate reason code. ment routine, IGC0007A. The error occurred either in GAM/SP or in
the operating system.
Source: DFSMSdfp
Source: DFSMSdfp
System Action: The job is abnormally ended, and if a SYSABEND
statement was included in the job, a dump is produced. System Action: Message GAB260 appears on the system console,
identifying the cause of the error and the original system completion
Programmer Response: Respond as indicated in the accompa-
code. In addition, GAM/SP writes a record to the logrec data set and
nying message.
produces a dump on the system dump data set.
144 Programmer Response: Do the following:
Explanation: The error occurred during the processing of 1. Check for messages identifying the cause of the error. If these
SYNADAF, where it was determined that an incorrect access method are GAM/SP messages, (that is, the message number is of the
code was specified in the high order byte of register 15. form ‘GABnnn’), they are described in IBM Graphics Access
Method/SP: Messages and Codes
Source: DFSMSdfp
2. Perform any corrective actions associated with the original
Programmer Response: Make sure that the ACSMETH parameter system completion code.
on the SYNADAF macro instruction is correctly coded, or that the
high order byte of register 15 contains a valid access method code 3. Get a listing of the system dump.
before issuing SVC 68. 4. Contact your programming support personnel.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 149
information. Search problem reporting data bases for a fix for the
Explanation: An error occurred in either the Graphics Access
problem. If no fix exists, contact the IBM Support Center. Provide the
Method/System Product (GAM/SP), or the operating system.
JCL and the program listing for the job.
This completion code appears when:
145 1. A program check or abnormal end occurs in the GAM/SP
specify-attention (SPAR) routine, IGC0007C.
Explanation: The error occurred during the processing of SVC 69
2. IGC0007C detects an incorrect condition.
(BSP). Register 15 contains a return code indicating the cause of the
error. See message IEC916I for a complete description of the pos- Source: DFSMSdfp
sible return codes and their meanings. System Action: A message appears on the system console,
Source: DFSMSdfp accompanied by a reason code identifying the area of processing
where the error occurred. In addition, GAM/SP writes a record to the
System Action: The backspace task recovery routine has been
logrec data set and produces a dump on the system dump data set.
invoked. If the caller's DCB or BSAM control blocks are in this
region, an attempt was made to trace them to the SYS1.TRACE data Programmer Response: Do the following:
set. 1. Check for messages identifying the cause of the error. If these
Operator Response: Start a generalized trace facility (GTF) trace, are GAM/SP messages, (that is, the message number is of the
and re-create the problem. Reply to message AHL100A with: form ‘GABnnn’), they are described in IBM Graphics Access
TRACE=SYS,USR,SLIP Method/SP: Messages and Codes.
On the DD statement for the data set in error, specify: 2. Get a listing of the system dump.
DCB=DIAGNS=TRACE 3. Contact your programming support personnel.
Programmer Response: Verify that register 1 contained the correct
14A
DCB address prior to issuing BSP and that the DCB has not been
overlaid since being opened. If the DCB is valid, verify that it con- Explanation: An error occurred in either the Graphics Access
tains the correct IOB and/or ICB addresses and that neither the IOBs Method/System Product (GAM/SP), or the operating system.
and/or ICBs have been overlaid. This completion code appears when:
System Programmer Response: If the error recurs and the 1. A program check or abnormal end occurs in the GAM/SP delete-
program is not in error, look at the messages in the job log for more attention (DAR) routine, IGC0007D.
information. Search problem reporting data bases for a fix for the 2. IGC0007D detects an incorrect condition.
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job. Source: DFSMSdfp
System Action: A message appears on the system console,
accompanied by a reason code identifying the area of processing
where the error occurred. In addition, GAM/SP writes a record to the
logrec data set and produces a dump on the system dump data set.
Programmer Response: Do the following:
1. Check for messages identifying the cause of the error. If these
are GAM/SP messages, (that is, the message number is of the
System Completion Codes SCC-91
14B 14F
form ‘GABnnn’), they are described in IBM Graphics Access 45 The CLOSE data area validation failed.
Method/SP: Messages and Codes. 46 The unallocation data area validation failed.
2. Get a listing of the system dump.
47 An error occurred on browse options.
3. Contact your programming support personnel.
50 This event is unsupported.
51 An error occurred accessing IFBSXCB or IFBSXCBG.
14B
Source: System Environmental Recording (LOGREC)
Explanation: An error occurred in either the Graphics Access
Method/System Product (GAM/SP), or the operating system. System Action: The system writes a record to logrec and requests
a dump. Processing continues.
This completion code appears when:
System Programmer Response: Search problem reporting data
1. A program check or abnormal end occurs in the GAM/SP atten-
bases for a fix for the problem. If no fix exists, contact the IBM
tion inquiry (ATTNINQ) routine, IGC0007E.
Support Center. Provide the dump, logrec data set and Syslog.
2. IGC0007E detects an incorrect condition.
Note, for reason code X'10' and X'11', the system could not estab-
Source: DFSMSdfp lish the DSNLOGREC name/token, so the name of the logrec data
System Action: A message appears on the system console, set cannot be retrieved using the name/token retrieve service.
accompanied by a reason code identifying the area of processing
where the error occurred. In addition, GAM/SP writes a record to the 14F
logrec data set and produces a dump on the system dump data set.
Explanation: During processing of a STATUS macro, the system
Programmer Response: Do the following: found an error.
1. Check for messages identifying the cause of the error. If these Register 15 contains a hexadecimal reason code that explains the
are GAM/SP messages, (that is, the message number is of the error:
form ‘GABnnn’), they are described in IBM Graphics Access
Code Explanation
Method/SP: Messages and Codes.
04 The STATUS macro specified an incorrect function code.
2. Get a listing of the system dump.
Register 2 contains the function code.
3. Contact your programming support personnel.
08 Only a program in supervisor state with PSW key 0-7
can request the specified STATUS function.
14C
0C You specified an address space identifier (ASID) for the
Explanation: An error occurred in the system environmental STATUS STOP function. The ASID parameter is valid
recording (LOGREC) component. only on the STATUS START function.
Register 15 contains a hexadecimal reason code that explains the 10 You issued the STATUS macro with the must complete
error: (MC) parameter, but you had already specified the MC
Code Explanation parameter on a previous invocation. You must issue the
STATUS macro with the RESET,MC,STEP parameter
01 An incorrect input request to build a logrec data set before issuing another SET,MC,STEP.
record was specified.
14 You issued a STATUS macro with the STOP option, but
10 The name/token create service returned an unexpected you had already issued a STATUS STOP. You must
return code. issue the STATUS macro with the START option before
11 An attempt to load module IEANTRT failed. issuing another STATUS STOP.
12 The ENFREQ signal event returned an unexpected 18 The input mask you specified on the STATUS SET,SD
return code. invocation set TCBSTPP. This bit can only be set by
specifying STATUS STOP.
13 The ENF 49 parameter area storage obtain request
returned an error return code. 1C The mask you specified on the STATUS SET,ND invo-
cation set TCBSTP. This bit can only be set by speci-
20 The ENFREQ event code 48 listen request returned an
fying STATUS SET,MC or STATUS SET,MC,STEP.
unexpected return code.
20 A routine running under a service request block (SRB)
21 The ENFREQ event code 36 listen request returned an
cannot use a STATUS macro to set a step
unexpected return code.
nondispatchable.
30 The input parameter list, IXGENF, is not valid.
24 In the parameter list on a SET or RESET request, the
31 An error occurred during a storage obtain request for an caller specified an incorrect address for a task control
IFBLISCB element. block (TCB).
38 The input parameter list, IFBENF36, is not valid. 28 The caller does not hold a needed local lock.
39 Storage could not be obtained for the An record. 2C The caller does not hold a needed local lock.
40 An IXGSXCMP validation error occurred. 30 The specified TCB did not pass an acronym check. The
41 Unable to obtain storage (IFBSXCB). TCB was probably overlaid or incorrect.
42 Unable to obtain storage (IFBSXCBG). 34 The mask of nondispatchability bits specified with the SD
parameter includes the TCBSRBND bit. This
43 Unable to obtain storage for log block area. nondispatchability bit can be set only by specifying
44 The OPEN data area validation failed. STATUS STOP,SRB.
SCC-92 OS/390 V2R8.0 MVS System Codes
151 15C
38 The STATUS macro specified an incorrect function code. bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
3C A program issuing either STATUS SET,MC,PROCESS
or STATUS RESET,MC,PROCESS was not running in
task mode. The calling program must be running in task 157
mode. Explanation: An error occurred when the system was processing a
44 The input mask you specified on the STATUS SET,ND DOM macro. A hexadecimal reason code in register 15 explains the
invocation, set the TCBPNDSP bit. The caller can not error:
set TCBPNDSP. Code Meaning
48 A routine running under a service request block (SRB) 04 The caller passed an incorrect value in register 0.
cannot use a STATUS macro for the requested function.
08 The caller was not the following:
4C You specified an input address space identifier (ASID) or
enclave token on a STATUS invocation that is not valid. A task in the same job step and address space as
the issuer of the WTOR macro that created the
50 The input TCB specified on a STATUS STOP or message to be deleted
STATUS START invocation was the caller's TCB. The
caller cannot perform this operation on itself. The caller was not in key 0-7 or APF authorized
54 A STATUS invocation to set a caller's nondispatchability 0C A program check occurred while the system was veri-
bit was invoked using SVC. fying that the caller could access each byte of a multiple
DOM parameter list.
58 STATUS STOP,SRB was invoked, but had been invoked
previously. Invoke STATUS START,SRB before invoking 10 An unauthorized caller tried to delete a write to operator
STATUS STOP,SRB again. (WTO) message that was not created by the same task
in the same address space
5C The system detected a possible overlay of a TCB field
for a task that is the target of a STATUS macro request. 14 The entry was by a branch, but the caller is not author-
ized.
60 The input TCB specified on a STATUS SET,ND,E or
STATUS SET,SD,E invocation was the caller's TCB. The 18 An unauthorized caller tried to delete a message that
caller cannot perform this operation on itself. was issued on another system.
Source: Task management Source: Communications task (COMMTASK)
System Action: The system abnormally ends the program that System Action: The system ignores the DOM macro. The DOM
issued the STATUS macro. parameter list and the failing message identifier are shown in the
dump. The system ignores any other message identifiers in the
Programmer Response: Correct the error. Run the job again. parameter list.
System Programmer Response: If the error recurs and the Programmer Response: Ensure that the correct message identifier
program is not in error, look at the messages in the job log for more is being used in the DOM macro. Ensure that the DOM issuer is in
information. Search problem reporting data bases for a fix for the the same job step as the WTOR issuer.
problem. If no fix exists, contact the IBM Support Center. Provide the
program listing for the job.
15B
151 Explanation: A VOLSTAT macro can be issued only by an author-
ized program. While processing a VOLSTAT macro, the system
Explanation: The error occurred during the processing of SETPRT. determined that the issuing program was not:
The parameter list whose address was passed to SETPRT in reg-
ister 1 was not in the user's region. An authorized program facility (APF) authorized program
Source: DFSMSdfp In supervisor state
System Action: Message IEC918I is issued. In storage protection key 0 through 7
Programmer Response: Make sure that the SETPRT macro Source: DFSMSdfp
instruction is correctly coded. Correct the error and rerun the job System Action: The system abnormally ends the program that
step. issued the VOLSTAT macro.
System Programmer Response: If the error recurs and the Programmer Response: Correct the program so that an authorized
program is not in error, look at the messages in the job log for more program issues the VOLSTAT macro.
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the 15C
JCL and the program listing for the job.
Explanation: Execute channel program (EXCP) processing found
that the program issuing an SVC 92 request was not running in
153
supervisor state.
Explanation: An error occurred while system management facilities
Source: Execute channel program (EXCP)
(SMF) processed a record. SMF was unable to handle the new
record because of buffer contention. System Action: The system abnormally ends the current task.
Source: System Management Facilities (SMF) Programmer Response: Ensure that the program is authorized to
issue TCBEXCP or the EXCP macro.
System Action: The system abnormally ends SMF processing. The
system requests an SVC dump. System Programmer Response: If the error recurs and the
program issuing the XDAP or EXCP macro is not in error, look at the
System Programmer Response: Search problem reporting data
System Completion Codes SCC-93
15D 16D
messages in the job log for more information. Search problem
169
reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center. Explanation: The error occurred during the processing of IMGLIB
with the CLOSE option. The DCB address passed to IMGLIB in reg-
15D ister 1 was incorrect. This system completion code is accompanied
by message IEC919I. Refer to the explanation of message IEC919I
Explanation: User specified an incorrect data area to SVC 93 for complete information about the task that was ended and for an
(TGET/TPUT). explanation of the return code in register 15.
Source: VTAM, or TSO/E if Session Manager is being used. Source: DFSMSdfp
System Action: The user is abnormally ended and processing con- Operator Response: Start a generalized trace facility (GTF) trace,
tinues. and re-create the problem. Reply to message AHL100A with:
Programmer Response: Supply a data area for access by the TRACE=SYS,USR,SLIP
program invoking SVC 93. A TPUT request requires read access, a
TGET request requires write access. On the DD statement for the data set in error, specify:
DCB=DIAGNS=TRACE
System Programmer Response: If the error recurs and the
program is not in error, search problem reporting data bases for a fix Programmer Response: Make sure that the IMGLIB CLOSE
for the problem. If no fix exists, contact the IBM Support Center. macro instruction is correctly coded. Make sure that the DCB
Provide the program listing for the job. address passed to IMGLIB is the same address returned to your
program by a previous IMGLIB OPEN, and that your program has
15F not issued a prior IMGLIB CLOSE specifying this DCB address.
Correct the error and rerun the job step.
Explanation: A SYSEVENT macro incorrectly invoked the system
resources manager (SRM). Register 15 contains a hexadecimal System Programmer Response: If the error recurs and the
reason code that explains the error: 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
Code Explanation problem. If no fix exists, contact the IBM Support Center. Provide the
04 The address space identifier (ASID), the SYSEVENT JCL and the program listing for the job.
code, or an input parameter was incorrect.
08 Program was not authorized to issue the SYSEVENT. 16B
0C A page fault occurred when the system referred to a Explanation: During processing of a MODESET macro, the system
data area assumed to be fixed. found an error.
10 A protection check occurred; the program issuing the Register 15 contains a hexadecimal reason code that explains the
macro did not have the correct storage key for storing in error:
the parameter data area. Code Explanation
14 A program held the SRM lock before the SYSEVENT 04 The macro parameter list was null.
macro invoked SRM.
08 The macro specified reserved bits.
18 The SRM recovery routine converts this reason code to
0C The macro requested an incorrect mode.
completion code X'25F'.
10 The macro requested an incorrect key.
1C A SYSEVENT TRANSWAP or REQSWAP with an event
control block (ECB) was issued when the maximum Source: Task management
allowed number of pending TRANSWAPs or System Action: The system abnormally ends the program that
REQSWAPs with ECBs had already been reached. issued the MODESET macro.
20 An SRM stack overflow was detected. Programmer Response: Correct the macro or the program errors
24 The SRM entry point did not receive an SRM recovery that incorrectly modified the parameter list. Run the job again.
parameter area (RRPA). System Programmer Response: If the error recurs and the
Other Internal SRM error. Save the dump and contact IBM program is not in error, look at the messages in the job log for more
support. information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
Source: System resources manager (SRM)
source program listing for the job.
System Action: The system abnormally ends the issuer of the
SYSEVENT macro. The system writes messages and a logrec data 16D
set error record.
Explanation: The system was processing one of the following
System Programmer Response: If an installation-provided Supervisor Call (SVC) extended service routines (ESR):
program issued the SYSEVENT, ensure that the program is author-
ized. Correct the error indicated by the reason code. Run the job 109
again. If an IBM-provided program issued the SYSEVENT run the 116
job again. In either case, if the error recurs, search problem 122
reporting data bases for a fix for the problem. If no fix exists, contact 137
the IBM Support Center. Provide the logrec data set error record and The system detected an incorrect ESR code in register 15. This error
the SYSOUT output for the job. is the result of a program specifying either:
An incorrect ESR code
An unsupported ESR code
SCC-94 OS/390 V2R8.0 MVS System Codes
16E 171
A hexadecimal reason code in register 15 explains the error: omit the operand. When the operand is omitted, no com-
parison is made.
Code Explanation
If you run programs that use batch LSR, see MVS Batch
0004 A program specified an incorrect ESR code. The ESR
code was too large.
Local Shared Resources for more information about
S16E-14 abends.
0008 A program specified an unsupported ESR code.
18 The DEBCHK macro specified TYPE=ADD; however,
Source: Supervisor control the DEB was not queued on the TCB DEB chain. Before
System Action: The system moves the incorrect ESR code from the DEB pointer can be added to the table, the DEB
register 15 to register 2. The system abnormally ends the program itself must be queued on the current TCB DEB chain.
that issued the incorrect SVC instruction. The system may write a The TCBDEB field points to the first DEB in the chain.
logrec data set error record. 1C The DEBCHK macro specified TYPE=ADD, but the
Operator Response: If the system programmer asks for an SVC DEBCHK routine found one of the following:
dump, set the following SLIP trap: The DEBAMTYP or DEBTBLOF field in the DEB
SLIP SET,COMP=16D,ACTION=SVCD,END contains zero.
System Programmer Response: Do the following: The DEB table already contains a pointer to the
DEB.
1. Ask the operator to set a SLIP trap to obtain an SVC dump.
The DEB to be added is in fetch-protected main
2. In the system trace, back up to the *RCVY entry for abend
storage.
X'16D'. Look for an SVC entry, other than SVC D, prior to the
*RCVY entry. In the entry, note the address in the PSW ADDR 20 The DEBCHK macro specified TYPE=ADD; however,
column. the DEB table has reached its maximum size. The
current DEB table does not have space for this new
3. Use the address in the PSW to identify the module that called
DEB pointer.
supervisor control.
20 The DEBCHK macro specified TYPE=ADD; however,
For an installation-provided module, correct the problem as
the DEB table contains 32760 bytes, which is its
follows:
maximum size. The current DEB table does not have
– For reason code X'0004', correct the ESR code, and space for this new DEB pointer.
run the job step again.
Source: DFSMSdfp
– For reason code X'0008', be sure that the requested
Programmer Response: Correct the error indicated by the reason
ESR is installed in the system.
code.
For an IBM module, search problem reporting data bases
for a fix for the problem. If no fix exists, contact the compo- 171
nent group associated with this module at the IBM Support
Center. Provide the SVC dump and, if available, the logrec Explanation: A PGFIX, PGFREE, PGLOAD, PGOUT, PGRLSE, or
data set error record. PGANY macro requested a paging service. The request was not
valid. The storage range specified by the input parameters may not
have been requested first by a GETMAIN macro.
16E
The registers contain the following:
Explanation: The system control program issued a DEBCHK
macro for the data extent block (DEB) pointed to in the DCBDEBAD Register 0: A hexadecimal reason code, which is one of the
field of a data control block (DCB) passed by the program. The following:
DEBCHK function could not be performed. Register 15 contains a Note: If you don't find your reason code in Register 0, see the
hexadecimal reason code: error code listed in Register 15.
Code Explanation Code Explanation
04 The DEB pointer is not in the DEB table. A DEB whose 06000101 The starting address in a virtual subarea list
address is not in the DEB table cannot be verified, (VSL) entry is greater than the ending
deleted, or purged. address.
08 The TYPE specified in the DEBCHK macro is incorrect. 06F20101
The TYPE must be VERIFY, ADD, DELETE, or PURGE.
07F20101
0C A DEBCHK macro that specified a TYPE other than
VERIFY was issued by a program that is not authorized. 0AF20101
10 The system found that the DEBDCBAD field in the DEB 32F20101
does not point to a DCB. DEBDCBAD must point to a 33F20201
DCB when TYPE is VERIFY, ADD, or DELETE.
3BF20101
14 AM value in the DEBCHK macro does not equal the
6FF20101 A program check occurred when the paging
DEBAMTYP value in the DEB. When a DEB pointer is
services was accessing the caller's service
added to the DEB table, the access method (AM) value,
list (SL) entry.
if given, is placed in the DEBAMTYP field of the DEB. If
no AM value is coded, a 0 is inserted in DEBAMTYP. 07000101
Subsequent DEBCHKs issued to verify or delete that 09000101
DEB pointer must either specify the same AM value or
0A000101
System Completion Codes SCC-95
172 172
34000101 6A000901 through 6A000906 The caller specified incor-
rect options with the page services request.
51000401 The starting address in a virtual subarea list
(VSL) entry is greater than the ending 6A000A01 The caller did not specify a valid function in
address. the VSL/PSL entry.
35000201 The page is part of a virtual I/O (VIO) 6A000B01
window.
6A000B02 The caller specified an ECB address, and
35000301 the page containing it had not been obtained
by a GETMAIN macro.
36000101 The page had not been obtained by a
GETMAIN macro. 6A000C01 A caller that is not in key 0 specified an ECB
address. The key of the page containing it
36000201 Permanent error.
did not match the caller's key.
3AF20101 A program check occurred when the paging
Register 3: If an SVC entry, the contents of register 3 are
services was accessing the caller's service
destroyed.
list (SL) entry. The entry point whose ID is
equal to the second byte of the reason code Register 4: If LIST-FORMAT entry, address of the caller's erro-
issued the reason code. neous VSL entry. If REGISTER-FORMAT entry, register 4 con-
tains zero.
3B000401 The starting address in a virtual subarea list
(VSL)/page service list (PSL) entry is greater Registers 5-9: If branch entry, registers 5-9 are the same as the
than the ending address. caller's input registers. If SVC entry, registers 5-9 contain zero.
3B000601 The starting address in a VSL/PSL entry is Register 10: If the error is related to paging address of the page
greater than the ending address. in error. If the error is not related to paging, register 10 contains
zero.
3C000101
Register 11: If LIST-FORMAT entry, address of the caller's first
3C000102 The SVC caller's storage key was not zero
VSL entry. If REGISTER-FORMAT entry, register 11 contains 0.
and did not match the event control block
(ECB) storage key. Register 12: Address of the input ECB. If no ECB address was
supplied, register 12 contains zero.
3C000201 The ECB page had not been obtained by a
GETMAIN macro. 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
51000101 through 51000105 An incompatible function
nonzero caller's storage key, registers 13-14 contain zero.
combination exists in a VSL entry.
Register 15: Hexadecimal error code, as follows:
51000201 A VSL entry did not request a valid function.
Code Explanation
51000301 A caller requested 24-bit interface and a real
address in the VSL entry. 04 This is a PGFIX request. The caller did not obtain
the VSL storage using a GETMAIN macro.
51000302 Register format entry and a starting address
was greater than an ending address. 10 The input ECB, TCB, or PSL/SSL failed to pass
validity checks.
55000101 The caller is not in key 0. The key for the
page did not match the caller's. Source: Real storage manager (RSM)
55000201 The caller requested that a permanently resi- System Action: The system issues an abend to the current task.
dent page be released.
System Programmer Response: Correct the problem in the
6A000101 The caller specified a nonzero ECB address request and run the job again. If PGFIX or PGFREE was requested
with a cross memory page services request. and the caller was not authorized, obtain proper authorization and
run the job again.
6A000201 The caller specified a nonzero ECB address
with a PGOUT, PGRLSE or PGANY request.
172
6A000301 An ECB address contained a negative
number. The request was a PGFIX, Explanation: Execute channel program (EXCP) processing found
PGFREE or PGLOAD. that an unauthorized program issued the EXCPVR macro. One of
the following conditions must be present for the program to be
6A000401 An ECB was not on a word boundary. The
authorized:
request was a PGFIX, PGFREE or
PGLOAD. The program must run under system protection key 0 through 7.
6A000601 The caller is not authorized to perform the The program must be in supervisor state.
page service function requested. The The SVC 114 authorization bit is set on in the job step control
request was a PGFIX or PGFREE. block (JSCB).
6A000701 The caller specified a cross memory mode The SVC 114 authorization bit is set on in the data extent block
request and a nonzero task control block (DEB).
(TCB) address with a page service function
to which the TCB address was applicable. Source: Execute channel program (EXCP)
6A000801 The caller specified an incorrect TCB. The System Action: The system abnormally ends the current task.
request was a PGFIX, PGFREE, PGLOAD Programmer Response: Ensure that the program is authorized to
or PGOUT. issue the EXCPVR macro or SVC 0, the EXCP macro. Check the
SCC-96 OS/390 V2R8.0 MVS System Codes
177 17A
problem program for the error. If the error cannot be determined, run System Action: The system issues message IEA705I. The system
the job again, requesting an ABEND dump. Notify the system pro- abnormally ends the current task.
grammer.
Programmer Response: Ensure that the calling program is not
System Programmer Response: If the system wrote a dump, look requesting too much central storage.
at field TCBEXCPD at offset X'C0' in the task control block (TCB)
If the system issues this abend frequently, notify the system pro-
of the current task. TCBEXCPD points to the EXCP debugging area
grammer.
(XDBA). The XDBA contains diagnostic data associated with the
EXCP processor. System Programmer Response: See installation procedures to
increase the central storage requirements.
If the error recurs and the program issuing the EXCPVR or EXCP
macro 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 179
problem. If no fix exists, contact the IBM Support Center. Explanation: While processing an I/O request, the system found an
error in the I/O parameters.
177 Register 2 contains a reason code, as follows:
Explanation: During processing of a TESTAUTH macro, the Code Explanation
system detected incorrect input parameters, as follows:
04 An error occurred when a program issued the SETLOCK
An incorrect bit mask is in register 1. macro.
RBLEVEL=2, but the request block (RB) is the last RB chained 08 The system found an incorrect access method block
or is out of range. (AMB) or I/O management block (IOMB).
The function code is greater than 256 or is out of range. 0C The system found an incorrect channel program area
The authorization code is greater than 256 or is out of range. (CPA).
Source: Task management 10 The system could not fix a page in storage.
System Action: The system abnormally ends the program that 14 The system found an incorrect buffer address.
issued the TESTAUTH macro. 18 The system found incorrect addresses in a chain of
Programmer Response: Ensure that the TESTAUTH parameter channel control words (CCW).
list is valid. The only valid IBM-supplied authorization or function 1C The storage block size is not 4 kilobytes.
code is one (1). If the installation supplied an authorization matrix,
40 IOMVEB points to a VEB that has incorrect data.
check to see that the function and authorization codes fall within the
range of the installation-defined codes. 44 IOMVEB is zero, but the media manager return code
indicates it should point to a VEB.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 48 AMB MRET pointer is incorrect.
information. Search problem reporting data bases for a fix for the
4C MRET MREB pointer is incorrect, or MREB does not
problem. If no fix exists, contact the IBM Support Center. Provide the
point back to BUFC that points to it.
program listing for the job.
50 For shared resources, no MRET entry pointed to
IOMBUFC that points to BUFC.
178
54 Received unexpected MMCALL return code.
Explanation: An error occurred when the system tried to process
an RU or VRU form of the GETMAIN macro or the STORAGE 58 Could not find BUFC in error, but the media manager
OBTAIN macro. The GETMAIN or STORAGE OBTAIN requested return code indicates some MMRE is posted with an
virtual storage that requires more central storage than is available. A error.
reason code in the SDWACRC field of the system diagnostic work Source: VSAM
area (SDWA) explains the error:
System Action: The system abnormally ends the current task.
Code Explanation
Programmer Response: Do the following:
04 There is not enough central storage available to support
a request for space in a system queue area (SQA) 1. Check to see if the program incorrectly modified the I/O parame-
subpool. ters. Correct any errors.
08 There is not enough central storage available to support 2. Recompile the job step.
a request for space in a fixed common service area 3. Run the job step again.
(CSA) subpool.
0C There is not enough central storage available to support 17A
a request for space in a local system queue area
Explanation: During processing of an EVENTS macro for a table
(LSQA) subpool.
creation or deletion, the system found an incorrect address specified
1C The system could not satisfy a request for an LSQA for the EVENTS table.
subpool. The page table for the segment describing the
Source: Task management
area to be obtained was paged out.
System Action: The system abnormally ends the program that
20 The system could not satisfy a request for an authorized
issued the EVENTS macro.
private area subpool. The page table for the segment
describing the area to be obtained was paged out. Programmer Response: Ensure that an EVENTS macro was
issued to construct the EVENTS table. Correct the error. Run the job
Source: Virtual storage manager (VSM)
again.
System Completion Codes SCC-97
17B 18A
System Programmer Response: If the error recurs and the See OS/390 Security Server (RACF) Diagnosis Guide for information
program is not in error, look at the messages in the job log for more on diagnosing RACF abends and reporting abend problems to IBM.
information. Search problem reporting data bases for a fix for the
Note: For batch jobs, if you need to do dump analysis but do not
problem. If no fix exists, contact the IBM Support Center. Provide the
have a dump, run the job again. For batch jobs using
program listing and the assembly listing associated with the job.
DSMON, a RACF command, or the RACF report writer,
specify a SYSABEND DD statement in the job. This will
17B ensure that a dump is taken.
Explanation: A program running in supervisor state, key 0 issued
the PURGEDQ macro with an incorrect value in the ASID parameter. 183
The address space for the specified ASID does not exist.
Explanation: RACF could not successfully establish an ESTAE
Source: Supervisor control recovery environment when processing a RACINIT request.
System Action: The system abnormally ends the task that issued Source: Resource Access Control Facility (RACF)
the PURGEDQ macro. The system may write a logrec data set error
System Action: The system ends the task.
record.
System Programmer Response: Register 15 contains the nonzero
Operator Response: If the system programmer asks for an SVC
return code passed back from the ESTAE macro. For a description
dump, set the following SLIP trap:
of the ESTAE return code, see OS/390 MVS Programming: Author-
SLIP SET,COMP=17B,ACTION=SVCD,END ized Assembler Services Reference ENF-IXG.
System Programmer Response: Do the following: See OS/390 Security Server (RACF) Diagnosis Guide for information
1. Ask the operator to set a SLIP trap to obtain an SVC dump. on diagnosing RACF abends and reporting abend problems to IBM.
2. In the system trace, look for an SVC 7B entry. The address in Note: For batch jobs, if you need to do dump analysis but do not
the PSW ADDR column for this SVC entry is the address of the have a dump, run the job again. For batch jobs using
calling module. DSMON, a RACF command, or the RACF report writer,
specify a SYSABEND DD statement in the job. This will
3. Use the PSW address to identify the module that issued the ensure that a dump is taken.
PURGEDQ macro.
For an installation-provided module, continue diagnosis with 185
the module.
Explanation: RACF could not successfully establish an ESTAE
For an IBM module, search problem reporting data bases recovery environment when processing a RACDEF request.
for a fix for the problem. If no fix exists, contact the compo-
Source: Resource Access Control Facility (RACF)
nent group associated with this module at the IBM Support
Center. Provide the SVC dump and the logrec data set error System Action: The system ends the task.
record. System Programmer Response: Register 15 contains the nonzero
return code passed back from the ESTAE macro. For a description
17D of the ESTAE return code, see OS/390 MVS Programming: Author-
Explanation: During processing of an EVENTS macro for a wait ized Assembler Services Reference ENF-IXG.
request, the system found an incorrect address specified for the See OS/390 Security Server (RACF) Diagnosis Guide for information
EVENTS table. on diagnosing RACF abends and reporting abend problems to IBM.
Source: Task management Note: For batch jobs, if you need to do dump analysis but do not
System Action: The system abnormally ends the program that have a dump, run the job again. For batch jobs using
issued the EVENTS macro. DSMON, a RACF command, or the RACF report writer,
specify a SYSABEND DD statement in the job. This will
Programmer Response: Ensure that an EVENTS macro was ensure that the system produces a dump.
issued to construct the EVENTS table. Correct the error. Run the job
again.
18A
System Programmer Response: If the error recurs and the
Explanation: A PGSER macro requested a paging service (FIX,
program is not in error, look at the messages in the job log for more
FREE, LOAD, RELEASE, ANYWHER, PROTECT, or UNPROTECT).
information. Search problem reporting data bases for a fix for the
The request was not valid. The caller used 31-bit addressing.
problem. If no fix exists, contact the IBM Support Center. Provide the
program listing and the assembly listing associated with the job. The registers contain the following:
Register 0: A hexadecimal reason code, which is one of the
182 following:
Explanation: RACF could not successfully establish an ESTAE Code Explanation
recovery environment when processing a RACHECK request.
08000101 On a branch request, the start address is greater
Source: Resource Access Control Facility (RACF) than the end address. The request was a register-
System Action: The system ends the task. format input.
System Programmer Response: Register 15 contains the nonzero 0B000101 On an SVC request, the start address is greater
return code passed back from the ESTAE macro. For a description than the end address. The request was a register-
of the ESTAE return code, see OS/390 MVS Programming: Author- format input.
ized Assembler Services Reference ENF-IXG. 35000201 The page is part of a virtual I/O (VIO) window.
SCC-98 OS/390 V2R8.0 MVS System Codes
18A 18A
35000301 The page had not been obtained by a GETMAIN xx0008xx The caller tried to release a page of protected
macro. storage.
36000101 The page had not been obtained by a GETMAIN xx000907 The caller issued a PGSER macro with the
macro. PROTECT parameter, but one of the other parame-
ters specified was either incorrect or incompatible.
36000201 Permanent error.
xx000908 The caller issued a PGSER macro with the UNPRO-
3AF20101 A program check occurred when the paging ser-
TECT parameter, but one of the other parameters
vices was accessing the caller's service list (SL)
specified was either incorrect or incompatible.
entry. The entry point whose ID is equal to the
second byte of the reason code issued the reason xx0701xx The caller issued a PGSER macro with the
code. PROTECT parameter for storage with a key that
does not match the PSW key under which the
3B000401 The starting address in a virtual subarea list
program runs. The program issuing the PGSER
(VSL)/page service list (PSL) entry is greater than
macro with the PROTECT parameter must be either
the ending address.
key zero or else run under a PSW key that matches
3B000501 The caller's page service list (PSL) entry contains the key of the storage being protected.
the reserved flag.
xx0702xx The caller tried to issue the PGSER macro with the
3B000601 The starting address in a VSL/PSL entry is greater PROTECT parameter for virtual storage in either the
than the ending address. PSA or any VIO window. Neither storage area can
3BF20101 A program check occurred when the paging ser- be specified with the PROTECT keyword.
vices was accessing the caller's service list (SL) xx0801xx The caller issued a PGSER macro with the UNPRO-
entry. TECT parameter with a key that does not match the
55000101 The caller is not in key 0. The key for the page did PSW key under which the program runs. The
not match the caller's. program issuing the PGSER UNPROTECT macro
must be either key zero or else run under a PSW
55000201 The caller requested that a permanently resident
key that matches the key of the storage being
page be released.
unprotected.
6A000101 The caller specified a nonzero event control block
xx0802xx The caller tried to issue the PGSER macro with the
(ECB) address with a cross memory page services
UNPROTECT parameter for virtual storage in either
request.
the PSA or any VIO window. Neither storage area
6A000201 The caller specified a nonzero ECB address with a can be specified with the UNPROTECT keyword.
PGOUT, PGRLSE or PGANY request.
Register 3: If branch entry, caller's return address.
6A000301 An ECB address contained a negative number. The
Register 4: If LIST-FORMAT entry, address of the caller's erro-
request was a PGFIX, PGFREE or PGLOAD.
neous page service list entry (PSL)/short page service list (SSL).
6A000401 An ECB was not on a word boundary. The request If REGISTER-FORMAT entry, register 4 contains zero.
was a PGFIX, PGFREE or PGLOAD.
Registers 5-7: If SSL format entry, registers 5-7 contain the
6A000601 The caller is not authorized to perform the page caller's input registers.
service function requested. The request was a
If PSL format SVC entry, registers 5-7 contain zero.
PGFIX or PGFREE.
If PSL format branch entry, registers 5-7 are irrelevant.
6A000701 The caller specified a cross memory mode request
and a nonzero task control block (TCB) address Register 8: If SSL format entry, register 8 is the same as the
with a page service function to which the TCB caller's input register.
address was applicable. If PSL format SVC entry, register 8 contains zero.
6A000801 The caller specified an incorrect TCB. The request If PSL format branch entry, register 8 contains the caller's input
was a PGFIX, PGFREE, PGLOAD or PGOUT. TCB address, or, if no TCB address was supplied, register 8
6A000901 through 6A000906 The caller specified incorrect contains zero.
options with the page services request. Register 9: If PSL format entry, address of the input ECB. If no
6A000A01 The caller did not specify a valid function in the ECB address was supplied, register 9 contains zero.
VSL/PSL entry. If SSL format entry, register 9 is the same as the caller's input
6A000B01 The caller specified an ECB address, and the page register.
containing it had not been obtained by a GETMAIN Register 10: If the error is related to paging, the address of the
macro. page in error. If the error is not related to paging, register 10
6A000B02 The caller specified an ECB address, and the page contains zero.
containing it had not been obtained by a GETMAIN Register 11: If LIST-FORMAT entry, address of the caller's first
macro. PSL/SSL entry. If REGISTER-FORMAT entry, register 11 con-
6A000C01 A caller that is not in key 0 specified an ECB tains 0.
address. The key of the page containing it did not Registers 12-14: If PSL format entry, the PSL entry in error. If
match the caller's key. the PSL was in pageable storage or if the PSL storage key did
6FF20101 A program check occurred when the paging ser- not match a nonzero caller's storage key, registers 12-14
vices was accessing the caller's service list (SL) contain zero.
entry.
System Completion Codes SCC-99
18B 18F
If SSL format entry, register 12 contains zero. Registers 13-14
18F
contain the SSL entry in error, or, if the SSL was in pageable
storage, registers 13-14 contain zero. Explanation: An abend occurred during the processing of the Inte-
grated Cryptographic Service Facility/MVS (ICSF/MVS) main task.
Register 15: Hexadecimal reason code, as follows:
Reason codes are as follows:
Code Explanation
Code Explanation
04 A caller issued a PGFIX request but did not obtain
the PSL storage using a GETMAIN macro, or a Reason codes for ICSF/MVS mainline routines:
page release operation failed because either the
caller attempted to release permanently backed 01 The ICSF/MVS mainline process could not establish a
storage or a non-system key caller attempted to data space.
release storage in a different key. 03 Error in the ICSF/MVS mainline cross memory environ-
10 The input ECB, TCB, or PSL/SSL failed validity ment.
checks. 04 Error loading or calling installation exits.
Source: Real storage manager (RSM) 05 The entry code in the component trace environment is
System Action: The system issues an abend to the current task. not valid.
System Programmer Response: Correct the problem in the 06 Error in the storage manager routine.
request and run the job again. If PGFIX or PGFREE was requested 07 Error in the master key validation routine.
and the caller was not authorized, obtain proper authorization and
08 Error in creating an in-storage cryptographic key data set
run the job again.
(CKDS).
18B 09 Error in the interface to the event notification facility.
Explanation: The common VTOC access facility (CVAF) encount- 0A Error from the component trace routine.
ered one of the following conditions: 0B ICSF/MVS could not load a required exit.
A structure error in the VTOC index 0C Exit number is not valid.
The CVAF return code is not consistent with the CVAF status 0D ICSF/MVS could not obtain a cross memory linkage
code. index.
Source: DFSMSdfp 0E ICSF/MVS could not set a cross memory authorization
System Action: A dump is written to SYS1.DUMP and an error index.
record is written to the logrec data set. The task is not ended. If 0F ICSF/MVS could not create an entry table for space-
CVAF encountered a structure error in the VTOC index: switching PC routines.
Message IEC606I is issued. 10 ICSF/MVS could not connect its entry table to the
CVAF disables the VTOC index. system tables.
If the caller of CVAF requests a read or write of a format 1 or 4 11 Error reading the CKDS into storage.
DSCB, CVAF performs the function and returns a code of yes to 12 ICSF/MVS could not establish an ENF listen exit.
its caller.
13 ICSF/MVS could not issue a broadcast ENF signal.
If the caller of CVAF requested a CVAF function that requires
14 ICSF/MVS could not establish an ESTAE during initial-
the VTOC index, CVAF returns an error return code to its caller.
ization.
This may cause the caller to end.
16 The entry code in the termination resource manager is
If the CVAF return code is not consistent with the CVAF status code,
not valid.
CVAF returns an I/O error return code to its caller. This may cause
the caller to end. 17 ICSF/MVS could not establish a termination resource
manager.
Programmer Response: If a structure error in the VTOC index was
encountered and the program ended, it may be rerun if it does not 1A ICSF/MVS could not OPEN, READ, WRITE, or CLOSE
depend upon the VTOC index. Run the IEHLIST utility to list the a data set.
VTOC and the disabled VTOC index. An inconsistency between the 1B ICSF/MVS could not interpret the options data set.
CVAF return code and status code indicates a logic error in CVAF.
You may not be able to successfully run the job until the problem is 1E The entry code to the data space create routine is not
corrected. valid.
System Programmer Response: If the error recurs and the 1F Error from DSPSERV CREATE in the data space create
program is not in error, search problem reporting data bases for a fix routine.
for the problem. If no fix exists, contact the IBM Support Center. 20 Error from ALESERV ADD in the data space create
Provide the logrec data set error record and all printed output and routine.
output data sets related to the problem.
21 Error from ALESERV EXTRACT in the data space
create routine.
22 Error from ALESERV DELETE in the data space create
routine.
23 Error from DSPSERV DELETE in the data space create
routine.
SCC-100 OS/390 V2R8.0 MVS System Codes
18F 18F
28 Error in the look for disabled cryptographic feature A6 Request not valid.
routine.
A7 Public key token type not valid.
29 Error from ATTACH in the look for disabled
A8 Hardware configuration is not enabled.
cryptographic feature routine.
A9 Hardware configuration contains wrong key size.
2A Error from DETACH in the look for disabled
cryptographic feature routine. AA Arithmetic operand is not valid.
2C The refresh code in the component trace routine is not AB No match found after queue.
valid. AC Error in public key processing.
32 Error in the generic service loader routine. AD Error in public key processing.
33 ICSF/MVS could not load a required installation service.
Common reason codes (issued by more than one function):
37 Error loading an application service.
AE Value for the FUNCTION parameter is unrecognized on
38 ICSF/MVS could not install the compatibility call to CSFAPKDS.
cryptographic SVC.
AF Error occurred in module CSFMIOPC.
3C The specified domain index is not valid for ICSF/MVS.
B0 Error occurred in ATTACH macro issued in CSFMIOPC.
3D Error in CPOOL manager.
B1 Error occurred in ATTACH macro issued in CSFMIOPC.
3E Error in I/O subtask control routine.
100 The return code from an installation exit is not valid.
3F Error from ATTACH in the I/O subtask control routine.
101 Compatibility mode service was requested when
40 Error from DETACH in the I/O subtask control routine. COMPAT=NO.
41 Error in initialization. 102 Condition code from the ICSF/MVS (instruction) macro is
42 Error in initialization - ATTACH. not valid.
43 Error in initialization - DETACH. 103 Return code from the RCFSTAT macro is not valid.
44 Error in parameter block. 104 Return code from the RCFCONF macro is not valid.
46 Error in serialization. 105 A master key version change occurred during the re-
encipher, conversion or dynamic CKDS update process.
47 Error in resource manager.
106 Configuration not valid.
48 Error in public key operation.
107 Error in public key processing.
49 Cryptographic public key operation not initialized.
108 Error in interprocessor communication.
4A Cryptographic public key operation not available.
109 Bad response code for PKSC/PKA request.
4B Configuration error.
10A Bad PKSC/PKA request block.
80 Parameter block for the compatibility services is not
valid. 180 Error found in the message queue.
84 An unrecognized service number was passed from the 181 The exit list in the common I/O routine is not valid.
user application. 182 The access control block in the common I/O routine is
8C The master key version number that was detected while not valid.
running in compatibility mode is not valid. 183 The request parameter list in the common I/O routine is
90 The status word from the hardware contained a not valid.
response code that is not valid. 184 MAC_generation or Mac_verification failed with RC=12
92 The key encrypting key (KEK) was the wrong type or during dynamic CKDS update processing.
was not a no control vector (NOCV) KEK. 185 An incorrect function request was passed to common I/O
94 The variant passed to the twist processing routine is not routines for dynamic CKDS update processing.
valid. 186 Unexpected return or reason codes were returned from
98 ICSF/MVS ended abnormally. An exit installed with the common I/O routines during dynamic CKDS update
FAIL=ICSF option has ended abnormally. processing.
9C The storage length for dynamic storage is not valid. 187 Incorrect CKDS record created during dynamic CKDS
update processing.
A0 Error in the CKDS retrieval routine.
A1 Requested system key was not found in the in-storage Reason codes for ICSF/MVS message processing:
and/or the DASD CKDS. 190 Message processing block (MPB) is not valid.
A2 Error in the CKDS retrieval routine. The requested 191 A blank message skeleton was retrieved.
system key has a MAC that is not valid.
192 A matching message table was not found.
A3 Error in the CKDS retrieval routine. The requested
193 The message was not found
dummy key was not found.
194 The substitution tag is not valid.
A4 Output type not valid.
195 The message buffer size was exceeded.
A5 Error in internal ICSF parameters service calls.
System Completion Codes SCC-101
1C2 1C5
196 The Message variable not found in the MPB. Resource Class
Code Resource Name Resource Description
Reason codes for ICSF/MVS callable services: 07 MvsMsgSv implementation class for the
MVS message services interface
200 An error occurred in the encode or decode callable
service. 08 DevQueue implementation class for the in-
storage queues
202 An error occurred in the key generate callable service. 09 ErrStack implementation class for the
The parameter to CSFKGN1 called error recovery
IK_PROCESS_RULE has an unknown value, and proc- 10 ServerDS implementation class for the data
essing cannot continue. set access
11 Security implementation class for the
205 The control vector (CV) in the cryptographic key data set security server interface
(CKDS) record is not valid.
12 SrvGroup implementation class for the
206 The conversion service received a CKDS that is not subtask management
valid. 13 SynchEcb implementation class for the
subtask synchronization
Reason codes for dialog routines: 14 TimeServ implementation class for the
timer interface
300 A function that was passed to the dialog service routine
15 ExtTrace implementation class for the
is not valid. component trace interface
16 TaskServ implementation class for the
Reason codes for component trace: subtask services
380 A message ID that was used in the component trace 17 WkldMgmt implementation class for the
workload manager interface
routine is not valid.
18 XcfGroup implementation class for the
381 The control block in the component trace routine is not cross-system coupling facility
valid. interface
19 XLngServ implementation class for the
Source: Integrated Cryptographic Service Facility (ICSF/MVS) cross-language services
System Action: If the abend occurred during ICSF/MVS initializa- 20 XMemServ implementation class for the
tion, ICSF/MVS ends abnormally. cross-memory services
In general, if the abend occurred after ICSF/MVS is available and
Source: MQSeries Worklfow for OS/390
running, your application or unit of work ends. ICSF/MVS is still
available. However, if the error occurred when trying to set the System Action: The system issues an ABEND dump.
cryptographic domain index or if an exit that is installed with the Programmer Response: None.
FAIL=ICSF option abends, ICSF/MVS ends abnormally.
System Programmer Response: For reason code X'1505nnnn',
Programmer Response: Review the reason codes on the dump verify the setup for the component trace and restart the server. For
title to see if the abend was an installation or user error. Also check reason code X'1705nnnn', verify the setup for the workload
to see if the reason code was an installation-generated reason code. manager application environment and restart the server.
If you cannot resolve the problem, save the dump, gather the dump
header record, and contact the IBM support center. For other reason codes, search the problem reporting data bases for
a fix for the problem. If no fix exists, contact the IBM Support Center
Debugging aids and recovery-related information are discussed in and provide the ABEND dump.
ICSF/MVS System Programmer's Guide.
1C5
1C2
Explanation: System logger detected an unrecoverable error.
Explanation: The MQSeries Workflow for OS/390 server address
space encountered a severe inernal error. The following hexadecimal reason code, in register 15, describes an
external error:
The reason code identifies the source of the error. It has the format
X'rrmmnnnn', where rr denotes the resource class (as detailed in Code Explanation
the table that follows), mm denotes the method of the resource 00000804 An IXGBRWSE or IXGDELET request failed because
class, and nnnn identifies the place within the method where the the block identifier could not be found in the logstream.
error was encountered.
System Action: The request is not honored and a
Resource Class
return code 8, reason code 00000804 (or corresponding
Code Resource Name Resource Description missing data reason code) is returned to the caller.
01 Resource abstract class for workflow System Programmer Response:Ensure that the value
server resources
in the request references an existing portion of the log
02 FmSrvRes abstract class for workflow
server instance resources
stream.
03 FmDevRes abstract class for workflow You can run the utility IXCMIAPU with LIST
server input/output device LOGSTREAM (logstream-name) DETAIL(YES) to help
resources
you determine if the requested blockid is in a valid
04 SystCons implementation class for the range, and it is not in a loss of data range.
system console interface
05 Diagnose implementation class for the If the blockid is valid contact the IBM Support Center
flight recorder Provide the dump and LOGREC entries associated with
06 FifoLock implementation class for the this ABEND.
queue serialization
SCC-102 OS/390 V2R8.0 MVS System Codes
1C6 1FA
0000085F Control percolated to the service requester's task due to
1C6
an abend during system logger processing. Retry was
not possible. Explanation: The system detected a possible overlay of a TCB
field for a task that is the target of a STATUS macro request. For
System Programmer Response: Request the service
more information about the STATUS macro, see OS/390 MVS
again. If the problem persists, contact the IBM Support
Programming: Authorized Assembler Services Reference SET-WTO.
Center.
Source: Task Management
00030006 An abend occurred after system logger called an appli-
cation's complete exit. Either the complete exit abended System Action: The system abnormally ends the address space in
and percolated to system logger recovery, or the which the task is running.
address of the complete exit specified on the System Programmer Response: Search problem reporting data
COMPLETEEXIT parameter of the IXGCONN request bases for a fix for the problem. If no fix exists, contact the IBM
for the log stream was incorrect. support center.
System Action: System logger ends the task that
owned the connection to the log stream in order to end 1C7
the connection.
Explanation: An error occurred during workload manager (WLM)
System Programmer Response:Ensure that the com- processing. The accompanying reason code identifies either an
plete exit address specified on the IXGCONN request internal recoverable WLM error or an external error code as follows:
was correct and that the address does not change.
System logger requires that the caller's complete exit Code Explanation
remain loaded in storage at the address specified on 0Axx0004 An attempt to reference a caller's parameters caused an
IXGCONN until the application receives control after suc- 0C4 abend.
cessfully disconnecting from the log stream. Then, if
Programmer Response: Check for possible programmer errors
necessary, restart the application.
that might exist in a program that requests services from WLM.
If the problem persists, contact the IBM Support Center.
Code Response
Provide the dump and logrec entries associated with this
abend. 0Axx0004 WLM could not access the parameter list or parameters
passed by the IWMPQRY or IWMWQRY services. The
00030009 System logger was unable to complete an offload during
following are possible problems:
log stream recovery. The operator response to message
IXG115A caused system logger to abnormally terminate WLM could not copy the parameter list because the
the structure connect task. parameters could not be accessed by storage key.
System Action: System logger ends the task that WLM could not copy the service definition, service
owned the connection to the log stream and the struc- classification rules, or the service notepad area to a
ture for which the offload was processing. private copy.
System Programmer Response:Restart any applica- WLM could not copy a local copy of the parameter
tions that use the log stream identified in message list back into the caller's copy.
IXG114A. Check the parameter list areas for the service definition,
If the problem persists, contact the IBM Support Center. service classification rules, and notepad area. Ensure
Provide the dump and logrec entries associated with this that correct storage keys are specified.
abend. For all other reason codes, contact programmer service support.
Any other reason codes in register 15 indicate that an internal error Operator Response: Notify the system programmer.
has occurred.
System Programmer Response: Search problem reporting data
Source: System logger bases for a fix for the problem. If no fix exists, contact the IBM
System Action: The system rejects all future write requests for the support center. Provide the dump.
current log stream. The system writes a dump and records the error
in logrec. 1FA
For the reason codes listed above use the system actions specif- Explanation: The error occurred during execution of a data man-
ically listed. agement request for a spool data set. JES2 found that the data man-
System Programmer Response: Try disconnecting a log stream agement control blocks are no longer valid.
and connecting again. If the problem persists, contact the IBM Source: JES2 or DFSMSdfp
Support Center. Provide the dump and logrec entries associated with
System Programmer Response: Obtain the program listing for the
this abend.
job. Look at the messages in the job log. If the JOB statement did
For the reason codes listed above use the system programmers not specify MSGLEVEL=(1,1), specify it and run the job again.
response specifically listed.
Probable user error. Verify that the problem program did not modify
the data management control blocks. After making the correction,
execute the job step again.
If the problem recurs and if the program is not in error, search
problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
System Completion Codes SCC-103
1FB 1FB
IAT6704
1FB
OPEN could not allocate a user address space buffer to a data
Explanation: JES3 may have issued one of the following mes- set.
sages because of the indicated error:
IAT6707
IAT1601 At deallocation of the external writer data set, the module could
The user is trying to perform I/O to a data set that is closed. not find an output scheduling element (OSE).
An incorrect IATYDAT was found on the data buffer block (DAT) IAT6708
queue. A permanent I/O error occurred on an output data set.
IAT1602 IAT6711
One of the following control blocks either (1) could not be vali- A SSISERV macro sent incorrect data to the global processor;
dated or (2) contains incorrect data: IATYDAT, IATYDMC, the request could not be serviced.
IATYDSB or IATYDSS.
IAT6309
IAT1603 A failure has occurred during an MVS LOAD or BLDL of a JES3
A JES3 module passed, as a parameter to IATDMEB, a code input service module.
that requested an incorrect data management function.
If none of these messages appear, JES3 found an incorrect
IAT1604 IFGACB, IATYDSS, or IATYDSB control block or received an error
A start I/O operation in the user's storage returned an error return code as a result of a SJFREQ request.
code.
Source: JES3
IAT1605
System Action: Depending on the error, the system ends either
A start I/O operation in the user's storage returned an error
the job step or the user address space.
code.
Programmer Response: If the problem occurred in an I/O opera-
IAT1606 tion, correct any I/O errors in your program. Then rerun the job.
IATDMEB found an incorrect unprotected buffer (IATYDAT)
address or the associated IATYDMC address was incorrect. If JES3 issued message IAT6309, correct the cause of the LOAD or
BLDL failure. Then rerun the job. Otherwise, notify your system pro-
IAT1607 grammer, supplying a SYSABEND dump.
IATDMEB could not allocate an unprotected buffer.
System Programmer Response: If messages accompany this
IAT1609 abend, register 3 in the dump points to a copy of the data set status
One of the following occurred: block (DSS). A hexadecimal reason code explains the error. Use
this reason code to determine the cause of the error.
When module IATDMEB or IATSIAD attempted to set up a
data management WAIT, the module found a data manage- Code Explanation
ment function already waiting. 01 Module IATDMEB, while performing verification of the
When module IATDMEB or IATSIAD attempted to set up a subsystem vector table (SVT), has found that the SVT
subsystem interface WAIT, the module found a subsystem block ID (SVTID) is incorrect.
function already waiting. 02 The data extent block (DEB) does not contain the data
set block (DSB) upon entry to IATDMEB.
IAT1610
During ENDREQ processing, a request for macro IATYJDS 03 Module IATDMEB contains undefined function code.
failed. 04 Module IATDMEB received an error code from the
IAT1611 IATXSIO macro while processing the GET routine.
The JES3 SSVT was either (1) incorrect or (2) could not be 05 Module IATDMEB received an error code from the
found. IATXSIO macro while processing the data management
point routine.
IAT1612
The SYSOUT class to be allocated is not alphanumeric. 06 Module IATDMEB received an error code from the
IATXSIO macro while processing the SSI point routine.
IAT1614
A failure occurred while processing a started task or TSO logon 07 Module IATDMEB received an error code from the
internal reader data set. IATXSIO macro while processing the GET routine.
08 Module IATDMEB received an error code from the
IAT1803
IATXSIO macro while processing the PUT-Update
An attempt to move data from a JES3 protected buffer in the
routine.
JES3 auxiliary address space to a user storage unprotected
buffer failed. 09 Module IATDMEB contains a dynamic address trans-
lation (DAT) validation error. The DAT address is out of
IAT6700 range (too low).
During deallocation, when attempting to update the JDSENTRY,
the module could not find a job data set (JDS) entry. 0A Module IATDMEB contains a dynamic address trans-
lation (DAT) validation error. The DAT address is out of
IAT6703 range (too high).
When the module attempted communication, an error that dis-
0B Module IATDMEB received an error code from the
rupted operations occurred in the global processor.
IATXSIO macro while processing IATDMEBS routine.
SCC-104 OS/390 V2R8.0 MVS System Codes
1FB 1FB
0C Module IATDMEB received a busy return from macro | 27 Module IATDMEB could not free user memory buffers.
IATXUBAL while processing the buffer checkpoint | The DSS or DSB failed validation in module IATDMUB.
routine.
29 Module IATDMEB received an DAT validation error. DAT
0D Module IATDMEB received an error return from macro address is out of range (too high).
IATXUBAL while processing IATDMEBS routine.
2A Module IATDMEB received an SSISERV error while
0E Module IATDMEB received an error code from the processing ENDREQ routine. The JIB block ID incor-
IATXSIO macro while processing IATDMEBS routine. rect.
0F Module IATDMEB received an error code from the 2B Module IATDMEB received an error in JDS access while
IATXSIO macro while processing IATDMEBS routine. processing ENDREQ routine.
10 Module IATDMEB received an error code from the 2C Module IATDMEB received an DMC validation error.
IATXSIO macro while processing IATDMEBS routine. DMC address is out of range (too low).
11 Module IATDMEB received a busy return from macro 2D Module IATDMEB received an DMC validation error.
IATXUBAL while processing IATDMEBS routine. DMC address is out of range (too high).
12 Module IATDMEB detected a CLOSE serialization failure 2E Module IATDMEB received an DAT validation error. DAT
in the ENDREQ routine. address is out of range (too low).
13 Module IATDMEB received a busy return form macro 2F Module IATDMEB received an DAT validation error. DAT
IATXUBAL while processing IATDMEBS routine. address is out of range (too high).
14 Module IATDMEB received an UBUFF validation error 30 Module IATDMEB received an error return from spool
while processing. DMC block ID (DMCID) is incorrect. record allocation (IATDMDKR).
15 Module IATDMEB found the data management wait 31 Module IATDMEB received an DAT validation error. DAT
already outstanding. address out of range (too low).
16 Module IATDMEB found the SSI wait already out- 32 Module IATDMEB received an DAT validation error. DAT
standing. address out of range (too high).
17 Module IATDMEB received an error return from macro 33 Module IATDMEB received an DAT validation error. DAT
IATXSIO. block ID (DATID) is incorrect.
18 Module IATDMEB received an DMC validation error. The 34 Module IATDMEB received an DAT validation error. DAT
DMC block ID (DMCID) is incorrect. address out of range (too low).
19 Module IATDMEB received an DMC validation error. 35 Module IATDMEB received an DAT validation error. DAT
DMC address is out of range (too low). address out of range (too high).
1A Module IATDMEB received an DMC validation error. 36 Module IATDMEB received an DAT validation error. DAT
DMC address is out of range (too high). block ID (DATID) is incorrect.
1B Module IATDMEB received an DAT validation error. DAT 37 Module IATDMEB received an DAT validation error. DAT
block ID (DATID) is incorrect. address is out of range (too low).
1C Module IATDMEB received an DAT validation error. DAT 38 Module IATDMEB received an DAT validation error. DAT
address is out of range (too low). address is out of range (too high).
1D Module IATDMEB received an DAT validation error. DAT 39 Module IATDMEB received an DAT validation error. DAT
address is out of range (too high). block ID (DATID) is incorrect.
1E Module IATDMEB received a GETMAIN failure while 3A Module IATDMEB received an error while adding a data
processing ENDREQ routine. set status block (DSS) to the record allocation block
(RAB) queue during write error recovery.
1F Module IATSICC received a permanent I/O error writing
last buffer. 3B Module IATDMEB received an error while adding a data
set status block (DSS) to the record allocation block
20 Module IATDMFR received a failure in IATDMEB
(RAB) queue after IATXSIO processing.
channel end routine (IATDMEBS).
3C Module IATDMEB received an error while resetting a
21 Module IATDMEB received a cross memory move
data set status block (DSS).
(IATXMVXM) error return.
3D Module IATDMEB received an error while adding the
22 Module IATDMEB detected the data set status block id
data set status block (DSS) to the record allocation block
(DSSID) is not valid upon entry.
(RAB) queue.
23 Module IATDMEB received an DSS validation error. The
40 Module IATDMDM received an incorrect ACB on entry.
SVT pointer (DSSSSVT) is incorrect.
41 Module IATDMDM received an DSB validation error.
24 Module IATDMEB received an DSB validation error.
DSB block ID (DSBID) incorrect.
DSB block ID (DSBID) is incorrect.
42 Module IATDMDM received an DSS validation error.
25 Module IATDMEB received an error return from UBUFF
DSS block ID (DSSID) incorrect.
while processing the allocation routine.
43 Module IATDMDM received an incorrect DAT address
26 Module IATDMEB received an error return from IATXSIO
while processing the PUT routine.
while processing the IATDMEBS routine.
System Completion Codes SCC-105
1FB 1FB
44 Module IATDMDM received an incorrect buffer point 6A Module IATSIOR received a BUSY return from the buffer
while processing the PUT routine. allocation routine.
45 Module IATDMDM found that no room remains in the 6B Module IATSIOR received an error while adding a data
buffer while processing the PUT routine. set status block (DSS) to the record allocation block
(RAB) queue after an error during OPEN processing.
46 Module IATDMDM received an DAT validation error.
DAT address out of range (too low). 6C Module IATSIOR received an SSISERV error return. The
job is marked delete only.
47 Module IATDMDM received an DAT validation error.
DAT address out of range (too high). 70 Module IATSICC received an SSISERV error return. The
job was marked delete-only.
48 Module IATDMDM received an unsuccessful GETMAIN
while processing the ENDREQ routine. 71 Module IATSICC received an SSISERV error return
while processing INTRDR job.
49 Module IATDMDM received an input service error while
processing the ENDREQ routine. 72 Module IATSICC received a catastrophic error from
SSISERV.
4A Module IATDMDM did not receive the JOBID from input
service while processing the ENDREQ routine. 73 Module IATSICC received an SSISERV error return. Bad
data was sent.
4B Module IATDMDM received an error re-opening INTRDR
data set while processing the PUT routine. 74 Module IATSICC received an SSISERV error return. The
job number is not available.
4C Module IATDMDM detected serialization failure in the
PUT routine. 75 Module IATSICC detected a CLOSE serialization failure.
4D GETMAIN failed while processing a started task or TSO 76 Module IATSICC detected a PUT serialization failure.
logon request.
77 Module IATSICC detected an INTRDR serialization
50 Module IATSIAD received an SSISERV error return. failure. No task was holding the DSBOCTCB lock.
51 Module IATSIAD received an SSISERV error return. 78 Module IATSICC detected an INTRDR serialization
failure. Some other task was already holding the
52 Module IATSIAD received an SSISERV error return. The
DSBOCTCB lock.
job is marked delete only.
79 Module IATSICC detected an INTRDR serialization
53 Module IATSIAD received a catastrophic error from
failure. The DSBOCTCB lock was overlayed while proc-
SSISERV.
essing the INTRDR close request.
54 Module IATSIAD detected bad data was sent during
80 Module IATDMFR received a failure in module IATSIAD
SSISERV processing.
while processing the IATSIADD routine.
55 Module IATSIAD received an error during PSO unallo-
81 Module IATDMFR received a failure in routine
cation from SSISERV error return.
IATDMDKW.
56 Module IATSIAD received an SSISERV error return.
90 Module IATDMDM received an error code from a
There was no job number available.
STORAGE OBTAIN request.
57 Module IATSIAD received an SSISERV error return.
91 Module IATDMDM received an error code from a call to
58 Module IATSIAD received an SSISERV error return. IATGRAS.
59 Module IATSIAD received an DSB message code not 92 Module IATDMDM received an error code from a call to
valid. IXZXIXSM. SEGTYPE=FIRST was specified on the call.
5A A JES3 module received an allocation request for a 93 Module IATDMDM received an error code from a call to
SYSOUT class that is not A-Z or 0-9. IXZXIXSM. SEGTYPE=LAST was specified on the call.
60 Module IATSIOR detected an OPEN serialization failure. 94 Module IATDMDM received an error code from a call to
61 Module IATSIOR detected an OPEN serialization failure. IXZXIXAC.
62 Module IATSIOR found ORT not available. 95 Module IATDMDM received an error code from a
STORAGE RELEASE request.
63 Module IATSIOR found ORT not available.
A0 Module IATDMDS, while processing a chain of DMCs,
64 Module IATSIOR received an error return from IATSIOD
found them chained in a circular chain.
module.
A1 Module IATDMDS, while in the Link-up routine, detected
65 Module IATSIOR found the user writer name was not
an error in processing the Extent Busy queue.
specified.
A8 Module IATDMIT detected that the channel program for
66 Module IATSIOR received an SSISERV error return. The
I/O request was incomplete while the request complete
job was marked delete-only.
normally.
67 Module IATSIOR received a catastrophic error from
A9 Module IATDMIT detected a failure when attempting to a
SSISERV.
DSS to the SRB Wait Queue.
68 Module IATSIOR did not find a job data set (JDS).
AA Module IATDMIT detected a failure when attempting to
69 Module IATSIOR received an SSISERV error return. reset a DSS after it had been removed from the Protect
There was no job number available. Buffer (PBUF) Wait Queue.
SCC-106 OS/390 V2R8.0 MVS System Codes
1FC 1FC
Second Digit - The second digit in the reason code indicates the
1FC
phase of processing when that the error occurred:
Explanation: In response to a Supervisor Call (SVC) instruction,
Code Explanation
the SVC first level interrupt handler (FLIH) was running, but a system
error occurred. n1n EXCP encountered an error during the front end proc-
essing.
Source: Supervisor control
n2n EXCP encountered an error during the back end proc-
System Action: In an attempt to recover, the system abnormally
essing. Back end processing includes DASD ERP, PCI,
ends the task that issued the SVC instruction. The system writes a
PURGE, and FRR routines.
logrec data set error record.
n3n EXCP encountered an error during the post-processing.
Operator Response: If the system programmer asks for an SVC
dump, set the following SLIP trap: n4n EXCP encountered an error while updating the data
control block (DCB) during the validity check.
SLIP SET,COMP=1FC,ACTION=SVCD,END
n5n EXCP encountered an error while processing a related.
System Programmer Response: Do the following:
request.
1. Find the original abend causing the problem in the system diag-
n5n EXCP encountered an error while processing the PCI
nostic work area (SDWA) in the logrec data set error record for
appendage.
abend X'1FC'.
Third Digit - The third digit in the reason code indicates which
2. Search problem reporting data bases for a fix for the problem. If
control block was being tested when EXCP encountered the error:
no fix exists, ask the operator to set a SLIP trap to obtain an
SVC dump. Contact the IBM Support Center. Provide the SVC Code Explanation
dump and, if available, the logrec data set error record. nn1 Input/output block (IOB)
nn2 Data control block (DCB)
nn3 Data extent block (DEB)
200
nn4 Event control block (ECB)
Explanation: During a validity check of an I/O request, execute
channel program (EXCP) processing encountered an error. Each nn5 Input/output block extension (IOBE)
X'200' abend code has a three digit reason code that explains the nn6 I/O error data block (IEDB)
error. Each digit of the reason code has a specific meaning:
Source: Execute channel program (EXCP)
First Digit - The first digit in the reason code indicates the type of
error: System Action: The system abnormally ends the current task and
issues a SNAP dump.
Code Explanation
Programmer Response: Correct the problem that the reason code
1nn Storage protection check. The storage protection key of indicates. Verify also that the data set was opened and that the
one of the control blocks being tested was not the same control block indicated was correctly modified by the problem
as the storage protection key in the caller's request program.
block (RB).
If the EXCP access method is being used, ensure that the IOB and
2nn Segment translation error. A segment exception the ECB are correctly built. Correct the error. Run the job again.
occurred when EXCP processing was processing a
control block. If the error recurs and you cannot determine the cause, run the job
again, requesting an ABEND dump. Notify the system programmer.
A segment exception occurs when EXCP uses an incor-
rect address. The incorrect address results from one of System Programmer Response: In the dump, look at field
the following: TCBEXCPD at offset X'C0' in the task control block (TCB) of the
current task. TCBEXCPD points to the EXCP debugging area
The caller may have passed an incorrect address. (XDBA). The XDBA contains diagnostic data associated with the
The storage area that the address is obtained from EXCP processor.
may have been overlaid. If the error recurs and the program is not in error, look at the mes-
The control block that the address points to may sages in the job log for more information. Search problem reporting
have been prematurely freed. data bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Provide the JCL for the job and the dump.
Necessary data sets were prematurely closed.
3nn Page translation error. 201
A page translation error occurs when EXCP uses an Explanation: During processing of a WAIT macro, the system
incorrect address. The incorrect address results from found either:
one of the following:
The macro expansion contained an incorrect address for an
The caller may have passed an incorrect address. event control block (ECB)
The storage area that the address was obtained The program issuing the WAIT macro was not running under the
from may have been overlaid. same storage protection key as the storage containing the ECB
The control block that the address points to may Source: Task management
have been prematurely freed.
System Action: The system abnormally ends the program that
Necessary data sets were prematurely closed. issued the WAIT macro.
System Completion Codes SCC-107
202 206
Programmer Response: Ensure that the ECB address specified is
205
a valid virtual storage address and that it was not incorrectly modi-
fied. Correct the error. Run the job again. Explanation: An error occurred when the system tried to process
an EC, EU, LC, LU, VC or VU form of the FREEMAIN macro. During
System Programmer Response: If the error recurs and the
request processing, the system attempted to get local system queue
program is not in error, look at the messages in the job log for more
area (LSQA) storage to support the request, but no central storage is
information. Search problem reporting data bases for a fix for the
available to back the LSQA storage.
problem. If no fix exists, contact the IBM Support Center. Provide the
program listing and the assembly listing associated with the job. Source: Virtual storage manager (VSM)
System Action: The system abnormally ends the address space
202 where the job was running.
Explanation: During processing of a POST macro, the system Programmer Response: Run the job step again. If the system
found an error with an event control block (ECB). issues this abend again, notify the system programmer.
Register 15 contains a hexadecimal reason code that explains the System Programmer Response: Search problem reporting data
error: bases for a fix for the problem. If no fix exists, contact the IBM
Code Explanation Support Center.
00 The system found an incorrect address for a request
206
block (RB) in the 3 low-order bytes of the ECB specified
by the problem program. Explanation: An error occurred during processing of a LINK(X),
LOAD, XCTL(X), DELETE, or SYNCH macro. The control program
The system places the address of the RB in the ECB
detected one of these errors:
during processing of a WAIT macro. This address must
remain in the ECB until a POST macro places a post The address of the parameter list specified in the macro instruc-
code or zeros in the ECB. tion was erroneous.
04 The waiting RB is not enabled for interrupts. The address of the name (if EP or EPLOC was specified), or the
address of the directory entry (if DE was specified) was erro-
08 For a POST in a problem program protection key and a
neous.
WAIT in a system protection key, the ECB to be posted
does not match any ECB being waited on. The parameter list pointed to by the macro contains a nonzero
value in an undefined field.
0C For a WAIT in a problem program protection key, the
ECB address is incorrect. The caller is not authorized to use the options specified in the
macro.
Source: Task management
The LOAD macro includes conflicting options.
System Action: The system abnormally ends the program that
issued the POST macro. The LOAD macro includes the ADDR parameter, but addr is not
a doubleword boundary.
Programmer Response: Ensure that the contents of the ECB were
not modified after the WAIT macro and before the POST macro. An incorrect alias name was detected.
Correct the error. Run the job again. The reason code in register code 15 identifies the error:
System Programmer Response: If the error recurs and the Code Explanation
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 04 A LOAD macro was issued with conflicting options. One
problem. If no fix exists, contact the IBM Support Center. Provide the of the following occurred:
program listing and the assembly listing associated with the job. The EOM (delete module at end of memory)
keyword, with the GLOBAL keyword omitted. The
204 EOM keyword applies only if the module is loaded
into CSA storage.
Explanation: An error occurred when the system tried to process
an EC, EU, LC, LU, VC or VU form of the GETMAIN macro. During The GLOBAL and ADDR keywords are both speci-
request processing, the system tried to get local system queue area fied.
(LSQA) storage to support the request, but no central storage is The ADDR and LOADPT keywords are both speci-
available to back the LSQA storage. fied.
Source: Virtual storage manager (VSM) 08 An unauthorized program attempted to run a LOAD
System Action: The system abnormally ends the address space macro that had the load to global feature (GLOBAL
where the job was running. keyword).
Programmer Response: Run the job step again. If the system 0C An unauthorized program attempted to run a LOAD
issues this abend again, notify the system programmer. macro that had the explicit load option (ADDR keyword).
System Programmer Response: Search problem reporting data 10 One of the following occurred:
bases for a fix for the problem. If no fix exists, contact the IBM An unauthorized program attempted to run a
Support Center. SYNCH macro having the KEYADDR, STATE, or
KEYMASK operands. These operands are available
only to authorized programs.
Reserved bits in the first word of the SYNCH macro
parameter list have nonzero values.
SCC-108 OS/390 V2R8.0 MVS System Codes
20A 20E
14 The requested name is an alias for another, already System Programmer Response: See the system programmer
loaded, alias. response for messages issued to the console or the job log.
18 A LOAD macro was issued with the ADDR keyword but If the error recurs and the program is not in error, search problem
the value of the ADDR keyword, the address, is not a reporting data bases for a fix for the problem. If no fix exists, contact
doubleword boundary. the IBM Support Center. Provide the ABEND dump and the source
program listing for the job.
1C A SYNCHX macro was issued with an XMENV operand
that contains an incorrect length indicator.
20A
20 The macro level for this macro is not compatible with
this system. Explanation: An error occurred when the system tried to process
an R form of the GETMAIN or FREEMAIN macro. During request
24 The program issuing the macro is in AR mode, but the
processing, the system attempted to get local system queue area
parameter list address does not have an access list
storage (LSQA) to support the request, but no central storage is
entry table (ALET) of zero. Callers in AR mode must
available to back the LSQA storage.
qualify the parameter list address with an ALET of zero.
Source: Virtual storage manager (VSM)
28 Either the EP (entry point) keyword parameter or the DE
(list entry address) keyword parameter does not have an System Action: The system abnormally ends the address space
ALET of zero. where the job was running.
2C The data control block (DCB) address (DE) keyword Programmer Response: Run the job step again. If the system
parameter does not have an ALET of zero. issues this abend again, notify the system programmer.
30 An incompatible level of TSO/E is being used with a System Programmer Response: Search problem reporting data
PDSE load module. bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
34 An incorrect byte was supplied in the DE parameter.
C0 A parameter was not addressable or was in the wrong 20D
storage key.
Explanation: An abend occurred in a subtask. The subtask either:
C4 The directory entry passed in the data control block
(DCB) address (DE) keyword parameter was not Operated in step-must-complete (MC) status
addressable or was in the wrong storage key. Issued an ABEND macro with the STEP option
C8 The data control block (DCB) was not addressable or As a result, the system abnormally ended the job step.
was in the wrong storage key. Note: The original abend code is in the TCBCMP field of the task
CC The data extent block (DEB) was not addressable or control block (TCB) for the subtask that caused the error.
was in the wrong storage key. Source: Recovery termination manager (RTM)
Source: Contents supervision (CSV) System Action: The system ends the job step. The system writes
System Action: The system issues an ABEND dump. The system an ABEND dump for the failing job step, if it provides a dump data
issues a message depending on the reason code accompanying the set.
abend: Programmer Response: Find the original abend code in the TCB
Code Explanation Message of the subtask that caused the error. Continue diagnosis with that
abend.
04 CSV010I
08 CSV014I 20E
0C CSV018I Explanation: A program issued a SPIE macro that specified an
10 CSV012I incorrect address for the SPIE program interruption element (PIE).
14 CSV023I Source: Recovery termination manager (RTM)
18 CSV022I System Action: The system sends messages about the problem to
the job log. The system abends the program that issued the SPIE
1C CSV012I
macro.
20 CSV029I
Operator Response: If the system programmer asks for an SVC
24 CSV029I dump, set the following SLIP trap:
28 CSV029I SLIP SET,COMP=2ðE,ACTION=SVCD,END
2C CSV029I Programmer Response: If an application program issued the
incorrect macro, correct the PIE address, ensuring that it is a valid
30 CSV040I
virtual storage address assigned to the job step. Rerun the job.
Programmer Response: See the application programmer response
System Programmer Response: If an IBM program issued the
for messages accompanying this abend issued to the console or the
macro, search problem reporting data bases for a fix for the problem.
job log.
If no fix exists, contact the IBM Support Center. Provide:
Check for program errors that incorrectly modify the parameter list. If
Messages from the job log
the DE operand is specified, check that the macro is correct for the
The ABEND or SVC dump
attributes of the requested module. Ensure that the address specified
The assembly listing for the job
in the EP, EPLOC or DE operand is not incorrectly specified or modi-
The JCL for the job
fied. After making corrections, run the job step again.
The program listing for the job
System Completion Codes SCC-109
20F 219
information. Search problem reporting data bases for a fix for the
20F
problem. If no fix exists, contact the IBM Support Center. Provide the
Explanation: A program tried to issue the ERREXCP macro. The JCL and the program listing for the job.
program was not in supervisor state.
Source: Input/output supervisor (IOS) 215
System Action: The system abnormally ends the current task. The Explanation: The error occurred during the processing of SVC 21
system does not process the macro. (STOW). This system completion code is accompanied by message
IEC910I. Refer to the explanation of message IEC910I for complete
Programmer Response: Remove the ERREXCP macro from the
information about the task that was ended and for an explanation of
program.
the return code in register 15.
212 Source: DFSMSdfp
Explanation: An error occurred during the processing of SVC 18; System Action: The STOW task recovery routine has been
the error could not be attributed to incorrect user input. This system invoked. If the caller's DCB is in the caller's region, an attempt was
completion code is accompanied by message IEC909I. Refer to the made to trace it to the SYS1.TRACE data set.
explanation of message IEC909I for complete information about the Operator Response: Start a generalized trace facility (GTF) trace,
task that was ended and for an explanation of the return code in reg- and re-create the problem. Reply to message AHL100A with:
ister 15. TRACE=SYS,USR,SLIP
Source: DFSMSdfp On the DD statement for the data set in error, specify:
System Action: Message IEC909I is issued indicating whether a DCB=DIAGNS=TRACE
dump was taken to the SYS1.DUMP data set.
Programmer Response: For return codes 01, 02, and 03, verify
Programmer Response: Make sure that the BLDL or FIND macro that register 1 contained the correct DCB address prior to issuing
instruction is correctly coded, and that the parameter list and control SVC 21 and that the DCB has not been overlaid since being opened.
blocks involved are not modified by your program during the proc- For return code 04, verify that register 0 contained the correct
essing of SVC 18. parameter list address and that the list is within the caller's region
System Programmer Response: If the error recurs and the prior to issuing SVC 21.
program is not in error, look at the messages in the job log for more System Programmer Response: If the error recurs and the
information. Search problem reporting data bases for a fix for the program is not in error, look at the messages in the job log for more
problem. If no fix exists, contact the IBM Support Center. Provide the information. Search problem reporting data bases for a fix for the
JCL, the program listing for the job, and the logrec data set error problem. If no fix exists, contact the IBM Support Center. Provide the
record. JCL and the program listing for the job.
213 218
Explanation: The error occurred during processing of an OPEN Explanation: An error occurred during the processing of DEVTYPE
macro instruction for a direct access device. This system completion (SVC 24) that could not be attributed to incorrect user input. This
code is accompanied by message IEC143I. Refer to the explanation system completion code is accompanied by message IEC913I.
of message IEC143I for complete information about the task that
was ended and for an explanation of the return code (rc in the Refer to the explanation of message IEC913I for complete informa-
message text) in register 15. tion about the task that was ended and for an explanation of the
return code in register 15.
Source: DFSMSdfp
Source: DFSMSdfp
Programmer Response: Respond as indicated to the applicable
message. Programmer Response: Make sure that the DEVTYPE macro
instruction is correctly coded, and that the areas passed to
System Programmer Response: If the error recurs and the DEVTYPE are not freed by your program during the processing of
program is not in error, look at the messages in the job log for more SVC 24.
information. Search problem 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 and the
JCL and the program listing for the job. 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
214 JCL and the program listing for the job.
Explanation: The error occurred during processing of a CLOSE
macro instruction for a data set on magnetic tape. This system com- 219
pletion code is accompanied by message IEC210I. Refer to the
explanation of message IEC210I for complete information about the Explanation: An error occurred during the processing of SVC 25
task that was ended and for an explanation of the return code (rc in that could not be attributed to incorrect user input. This system com-
the message text) in register 15. pletion code is accompanied by message IEC915I. Refer to the
explanation of message IEC915I for complete information about the
Source: DFSMSdfp task that was ended and for an explanation of the return code in reg-
Programmer Response: Respond as indicated for message ister 15.
IEC210I. Source: DFSMSdfp
System Programmer Response: If the error recurs and the System Action: Message IEC915I is issued to indicate whether a
program is not in error, look at the messages in the job log for more dump was taken to the SYS1.DUMP data set.
SCC-110 OS/390 V2R8.0 MVS System Codes
222 22D
Programmer Response: Make sure that your program does not check for program errors that incorrectly modify it. Correct the error.
alter the DCB or IOB during the processing of SVC 25. Run the job again.
System Programmer Response: If the error recurs and the System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 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 information. Gather GTF trace data using trace option keyword
problem. If no fix exists, contact the IBM Support Center. Provide the TRACE=SYSP and event keyword SVC=42,END.
JCL and the program listing for the job.
Search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the source
222 program listing for the job.
Explanation: The operator, or an authorized time sharing option
extensions (TSO/E) user, canceled the job without requesting a 22C
dump.
Explanation: During processing of a CHAP macro, the system
Source: Master scheduler found that the address of the fullword specified in the second
operand is incorrect. This fullword contains the address of the task
System Action: The system ends the job. In some cases, the
control block (TCB) for the subtask whose priority was to be
system might write a dump even though a dump was not requested,
changed.
depending on which system routine has control.
The address was incorrect for one of the following reasons:
Programmer Response: Find out why the operator or TSO/E user
canceled the job. Correct any errors and resubmit the job. If you It was not a multiple of 4.
want a dump, have the operator resubmit the job and then cancel it The addressed virtual storage has not been allocated.
using the command CANCEL jobname, DUMP. The protection key of the fullword does not match the protection
key of the issuer of the CHAP macro.
228 Source: Task management
Explanation: During processing of an EXTRACT macro, the System Action: The system abnormally ends the program that
system found that the location of the input parameter list was incor- issued the CHAP macro.
rect. The input parameter list, ordinarily created through expansion of
Programmer Response: Change the CHAP macro to specify a
the standard or MF=L form of the EXTRACT macro, describes the
valid fullword address. Ensure that this fullword will contain the
function to be performed.
address of the TCB when the CHAP macro is processed. Also,
The starting address indicated that the parameter list did not begin ensure that the problem program does not incorrectly modify the
either on a fullword boundary or within the storage assigned to the specification. Correct the error. Run the job again.
job step.
System Programmer Response: If the error recurs and the
Source: Task management program is not in error, look at the messages in the job log for more
System Action: The system abnormally ends the program that information. Format a GTF trace, using trace option keyword
issued the EXTRACT macro. TRACE=SVCP and using event keywords SVC=44,END.
Programmer Response: Correct the program so that the address Search problem reporting data bases for a fix for the problem. If no
of the input parameter list is valid. Run the job again. fix exists, contact the IBM Support Center. Provide the source
program listing for the job.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
22D
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the Explanation: A program requested an overlay. When trying to
source program listing for the job. answer the request, the overlay supervisor found an incorrect
address in the overlay segment table or the entry table. The address
22A points to a location outside the boundaries of the virtual storage
assigned to the job step.
Explanation: During processing of an ATTACH macro, the system
found an error. The overlay segment table is used by the overlay supervisor; it
resides in the load module and is in the same storage protection key
Register 15 contains a hexadecimal code that explains the error: as the application program.
Code Explanation Note: Overlay programs run only in 24-bit addressing mode, not in
00 The issuer of the ATTACH macro specified a GSPV, 31-bit addressing mode.
GSPL, SHSPV, or SHSPL parameter with a subpool ID Source: Overlay supervisor
greater than 127.
System Action: The system abnormally ends the program that
Source: Task management requested the overlay. The system writes an ABEND dump, if a
System Action: The system abnormally ends the program that dump DD statement is provided.
issued the ATTACH macro. Programmer Response: Check the program for errors that caused
Programmer Response: Change the macro to specify a problem the overlay segment table or the entry table to be incorrectly modi-
program subpool (1 through 127). If the macro is specified correctly, fied. Correct the errors; then assemble, link edit, and run the
program again.
System Completion Codes SCC-111
22F 233
50 Not all of the parameter list is accessible.
22F
54 The caller-supplied DCB is not accessible.
Explanation: No usable combination of time-of-day (TOD) clock
and clock comparator (REAL or WAIT type request) or no usable 58 The caller's storage list is not accessible.
CPU timer (TASK type request) is available. 5C The caller's header data is not accessible.
Source: Supervisor control and timer supervision 60 The caller-supplied event control block (ECB) is not
Programmer Response: Probable hardware error with the system accessible.
clocks. Contact hardware support. 64 The caller's ASID list is not accessible.
68 The caller's SUMLIST is not accessible.
230
6C The caller's subpool identification (ID) list is not acces-
Explanation: Global resource serialization encountered an error sible.
during processing of a DEQ macro.
70 The caller's storage key list is not accessible.
The DEQ macro specified an incorrect length for the resource name.
The length was specified in the rname length operand of the DEQ 74 A copy of SLIP registers and a copy of the program
macro instruction, was supplied by the assembler program, or was status word (PSW) are not accessible.
contained in the byte immediately preceding the resource name. 78 The caller-supplied SRB is not accessible.
Source: Global resource serialization 7C An incorrect version number is in the parameter list.
System Action: The system issues an ABEND dump. 80 The caller-supplied LISTD list is not accessible.
Programmer Response: Correct the incorrect macro instruction or 84 The caller-supplied SUMLSTL list is not accessible.
the program errors that incorrectly modified the length. Recompile
8C The ID is longer than 50 characters.
the program and run the job step again.
90 The ID is not addressable.
System Programmer Response: If the problem persists, search
problem reporting data bases for a fix for the problem. If no fix 94 The PSW/register area is an incorrect length.
exists, contact the IBM Support Center. Provide the abend dump. 98 The PSWREGS is not addressable.
9C The symptom record is incorrect.
233
A0 The symptom record is not addressable.
Explanation: The caller passed incorrect parameters in a request
for an SVC dump. A4 The data extent block (DEB) for the caller-supplied DCB
is not accessible.
Register 15 contains a hexadecimal reason code that explains the
error: AC The STRLIST area supplied by the caller is not acces-
sible.
Code Explanation
B0 The caller-supplied INTOKEN area is not accessible.
04 The address of the parameter list is zero.
B4 The caller-supplied REMOTE area is not accessible.
08 The parameter list is not a valid SVC dump or SNAP
parameter list. B8 The caller-supplied PROBDESC area is not accessible.
0C The caller-supplied data set is on an unsupported BC The caller-supplied JOBLIST area is not accessible.
device. C0 The caller-supplied DSPLIST area is not accessible.
10 In a caller-supplied storage range, the start address is C4 The caller-supplied REMOTE area is not valid; the
greater than or equal to the end address. length of a field in the area is specified as less than 4
14 The caller-supplied data for the HDR or HDRAD option bytes.
is greater than 100 characters. Source: Dumping services
18 The caller requested the 4-kilobyte system queue area System Action: The system writes a logrec data set error record.
(SQA) buffer, but it is not serialized. SVC dump processing attempts retry and gives the caller a return
1C The parameter list or what it points to is in the 4-kilobyte code of 8 and an associated reason code. If retry is not possible,
SQA buffer. the system abnormally ends the caller. SVC dump processing issues
message IEA911E. This message indicates whether the dump is
20 The caller supplied a data control block (DCB) address,
complete or partial.
and the DCB is not open or the address is not valid.
System Programmer Response: For reason code X'AC', make
28 An address space identifier (ASID) specified in the
sure the STRLIST area specified is addressable from the caller's
ASIDLST, ASID, or SUBPLST parameter is incorrect.
current address space. Then request the dump again.
The ASID is less than zero or greater than the maximum
value. For all other reason codes, correct the incorrect parameters and
issue the SDUMP macro again.
38 The caller specified the 4-kilobyte SQA buffer, but an
SVC dump function was already in progress. If the problem persists or is in an IBM-provided program, search
problem reporting data bases for a fix for the problem. If no fix
44 The caller specified a subpool greater than the maximum
exists, contact the IBM Support Center. Provide the assembly listing
value allowed (255).
for the job.
SCC-112 OS/390 V2R8.0 MVS System Codes
235 23E
235 239
Explanation: An error occurred during processing associated with Explanation: An error occurred during the processing associated
SVC 53, which obtains and releases exclusive control of a resource with SVC 57, which frees a buffer or extends the unscheduled text
associated with a BDAM data set. The task recovery routine for this (via the FREEDBUF macro issued either by the user or the system).
SVC determined that a control block required as input to SVC 53 The BDAM task recovery routine for this SVC determined that a
was not in the user's region and/or key. This system completion control block required as input to SVC 57 was not in the user's
code is accompanied by message IEC902I. Refer to the explanation region and/or key. This system completion code is accompanied by
of message IEC902I for complete information about the task that message IEC902I. Refer to the explanation of message IEC902I for
was ended and for an explanation of the return code in register 15. complete information about the task that was ended and for an
explanation of the return code in register 15.
Source: DFSMSdfp
Source: DFSMSdfp
System Action: Message IEC902I is issued, specifying a cleanup
code that indicates the results of the cleanup of resources attempted System Action: Message IEC902I is issued, specifying a cleanup
by the recovery routine. code that indicates the results of the cleanup of resources attempted
by the recovery routine.
Programmer Response: Insure the validity of the control block
from which the address of the block in error was taken. For example, Operator Response: Start a generalized trace facility (GTF) trace,
make sure that the input specified in the RELEX macro, the BLKREF and re-create the problem. Reply to message AHL100A with:
address, is valid and in the correct format and that the DCB address TRACE=SYS,USR,SLIP
passed is valid. If a RELEX macro was not issued, make sure that
the IOB related to the exclusive control request is correct and con- On the DD statement for the data set in error, specify:
tains the correct DECB address (IOBECBPT) and DCB address DCB=DIAGNS=TRACE
(IOBDCBPT).
Programmer Response: Insure the validity of the control block
In addition, check the DCBEBAD field in the DCB to ensure that it from which the address of the block in error was taken. The DECB
contains the correct DEB address, and that the DEB (DEBDCBAD) and DCB were specified in the FREEDBUF macro as input to the
points back to this DCB. If the next IOB is found to be in error, find SVC. Make sure that the DCBBUFCB field in the DCB contains the
the entry in the read exclusive list associated with the requested correct address of the buffer control block and the DCBDYNB field
block and ensure that the RDXIOBUQ field is correct. contains the correct address of the unscheduled list (if address
space was virtual). The BCB or USL contain the address of the next
237 IOB waiting to get a buffer, if one was not available. Ensure that this
address has not been overlaid. Make sure also that the input DECB
Explanation: The error occurred at an end-of-volume. This system contains the address of the buffer being freed (DECAREA field) and,
completion code is accompanied by message IEC023I. Refer to the if a buffer was requested for keys also, that the DECKYADR field
explanation of message IEC023I for complete information about the contains the correct address.
task that was ended and for an explanation of the return code (rc in
the message text) in register 15. System Programmer Response: If the error recurs and the
program is not in error, search problem reporting data bases for a fix
Source: DFSMSdfp for the problem. If no fix exists, contact the IBM Support Center.
Programmer Response: Respond as indicated for message Provide the SYSOUT output for the job.
IEC023I.
System Programmer Response: If the error recurs and the 23E
program is not in error, look at the messages in the job log for more Explanation: During processing of a DETACH macro, the system
information. Search problem reporting data bases for a fix for the found an error in the input parameters.
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job. Register 15 contains a hexadecimal reason code that explains the
error:
238 Code Explanation
Explanation: The error occurred during processing of an ENQ 00 The protection key of the address does not match the
macro instruction during the processing of global resource serializa- key of the issuer of the DETACH.
tion. An incorrect length was specified for the name representing the 04 Access register 1 was nonzero for a caller in access reg-
resource. This length was specified in the rname length operand of ister address space control (ASC) mode.
the ENQ macro instruction, was supplied by the assembler program,
08 The task control block (TCB) specified in the input
or was contained in the byte immediately preceding the resource
parameter list is not a subtask of the caller's TCB.
name.
Source: Task management
Source: Global resource serialization
System Action: The system abnormally ends the program that
System Action: The system issues an ABEND dump.
issued the DETACH macro.
Programmer Response: Correct the incorrect macro instruction or
Programmer Response: This is probably an error in the calling
the program errors that incorrectly modified the length. Recompile
program. Change the DETACH macro to specify a valid TCB
the program, and run the job step again.
address and ensure that it was not incorrectly modified by the
System Programmer Response: If the problem persists, search problem program. If running in access register ASC mode, ensure
problem reporting data bases for a fix for the problem. If no fix that the problem program does not alter access register 1. Correct
exists, contact the IBM Support Center. Provide the ABEND dump. 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 the job log for more
System Completion Codes SCC-113
23F 253
information. Search problem reporting data bases for a fix for the Programmer Response: Make sure that the BSP instruction is cor-
problem. If no fix exists, contact the IBM Support Center. Provide the rectly coded, and that the DCB and IOBs and/or ICBs for the data
source program listing for the job. set being processed are not overlaid by your program during the
processing of SVC 69.
23F System Programmer Response: If the error recurs and the
Explanation: A security violation has been detected during check- program is not in error, look at the messages in the job log for more
point restart processing. This completion code is accompanied by information. Search problem reporting data bases for a fix for the
message IHJxxxI with the appropriate reason code. problem. If no fix exists, contact the IBM Support Center. Provide the
JCL, the program listing for the job, the logrec data set error record,
Source: DFSMSdfp and all printed output and output data sets related to the problem.
System Action: The job is abnormally ended.
Programmer Response: Respond as indicated in the accompa- 247
nying message. Explanation: An error occurred in either the Graphics Access
Method/System Product (GAM/SP), or the operating system. This
240 completion code appears when an incorrect condition is detected by
the GAM/SP buffer management routine, IGC0007A.
Explanation: The error occurred during processing of a RDJFCB
macro instruction. This system completion code is accompanied by Source: DFSMSdfp
message IEC155I. Refer to the explanation of message IEC155I for System Action: A message appears on the system console that
complete information about the task that was ended and for an identifies the cause of the error. In addition, GAM/SP writes a record
explanation of the return code (rc in the message text) in register 15. to the logrec data set and produces a dump on the system dump
Source: DFSMSdfp data set.
Programmer Response: Respond as indicated for message Programmer Response:
IEC155I. 1. Check for messages identifying the cause of the error. If these
System Programmer Response: If the error recurs and the are GAM/SP messages, (that is, the message number is of the
program is not in error, look at the messages in the job log for more form ‘GABnnn’), they are described in IBM Graphics Access
information. Search problem reporting data bases for a fix for the Method/SP: Messages and Codes.
problem. If no fix exists, contact the IBM Support Center. Provide the 2. Get a listing of the system dump.
JCL and the program listing for the job.
3. Contact your programming support personnel.
244
251
Explanation: The error occurred during the processing of
SYNADAF. It was determined that the register save area provided by Explanation: The error occurred during the processing of SETPRT.
the user was incorrect. A user-provided area was determined to be incorrect. This system
completion code is accompanied by message IEC918I. Refer to the
Source: DFSMSdfp explanation of message IEC918I for complete information about the
Programmer Response: Probable user error. Make sure that when task that was ended and for an explanation of the return code in reg-
SYNADAF (SVC 68) is issued, register 13 points to a register save ister 15.
area within the user's region. If SYNADAF is issued from a SYNAD Source: DFSMSdfp
routine, make sure that register 13 has not been altered since the
SYNAD routine was entered, and that register 13 contained the System Action: Message IEC918I is issued.
address of a valid register save area when the last data manage- Programmer Response: Make sure that the last entry in the exit
ment macro was issued. list has a high-order bit set to B‘1’. Make sure that any FCB image
Correct the error and rerun the job step. entry in the exit list points to a valid FCB image, that the image is
within the user's region, that any FCB image has a valid length field
System Programmer Response: If the error recurs and the and that it is ended by an end-of-FCB image indicator. Correct the
program is not in error, look at the messages in the job log for more error and rerun the job step.
information. Search problem 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 and the
JCL and the program listing for the job. 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
245
JCL and the program listing for the job.
Explanation: An error occurred during the processing of SVC 69
(BSP) that could not be attributed to incorrect user input. This 253
system completion code is accompanied by message IEC917I. Refer
to the explanation of message IEC917I for complete information Explanation: While writing to system management facility (SMF)
about the task that was ended and for an explanation of the return data sets, SMF encountered an error and abnormally ended.
code in register 15. Source: System Management Facilities (SMF)
Source: DFSMSdfp System Action: The system ends the SMF address space and
System Action: The backspace task recovery routine has been releases the resources used by SMF.
invoked. Low real storage and the caller's region have been dumped Operator Response: Notify the system programmer. If SMF
to the SYS1.DUMP data set. The caller's input register 1 and DCB recording is essential for the system, restart the SMF address space
have been written to the logrec data set. using the SMF SET command as soon as the problem is corrected.
SCC-114 OS/390 V2R8.0 MVS System Codes
25F 278
System Programmer Response: Check error messages and the System Programmer Response: Correct the STAX parameter list
SVC dump produced as a result of any previous abnormal endings. error indicated by the reason code. See OS/390 TSO/E Program-
ming Services for the STAX macro parameters.
25F If the problem persists, search problem reporting data bases for the
Explanation: A system failure destroyed data used by the system fix for the problem. If no fix exists, contact the IBM Support Center.
resources manager (SRM) in controlling an address space.
269
Source: System resources manager (SRM)
Explanation: An error occurred during the processing of IMGLIB
System Action: If the ended task is the master scheduler
that could not be attributed to incorrect input to IMGLIB. Register 15
command processor and SRM was processing a NEWIPS
contains a return code that indicates whether a dump was taken to
SYSEVENT, the new installation performance specification (IPS)
the SYS1.DUMP data set.
may have been lost.
Source: DFSMSdfp
In all other cases, data pertaining to the address space's swap
status or performance characteristics may have been lost. SRM may System Action: The IMGLIB task recovery routine has attempted
no longer be able to control the address space according to its previ- to take a storage dump to the SYS1.DUMP data set; the result of the
ously assigned performance specification. dump attempt is indicated by the return code in register 15. See
message IEC920I for a complete description of the possible return
The system does the following:
codes and their meanings. Additional diagnostic information was
Writes a logrec data set error record written to the logrec data set data set.
Inserts ‘worst case’ substitute values in place of the lost address Programmer Response: Make sure that the IMGLIB macro instruc-
space characteristics in case the specify task abnormal exit tion is correctly coded.
(STAE) routine or the abnormally ended task requests retry
System Programmer Response: If the error recurs and the
Abnormally ends the controlling task of the address space or program is not in error, look at the messages in the job log for more
system component affected by the data loss information. Search problem reporting data bases for a fix for the
System Programmer Response: Search problem reporting data problem. If no fix exists, contact the IBM Support Center. Provide the
bases for a fix for the problem. If no fix exists, contact the IBM JCL, the program listing for the job, and the logrec data set error
Support Center. Provide the logrec data set error record and the record.
SYSOUT output for the job.
271
260 Explanation: The caller requested fixing or freeing of a page. The
Explanation: A parameter of the STAX macro was used incorrectly. request was in 24-bit addressing and was without proper authori-
A hexadecimal reason code in register 15 explains the error. zation.
Code Explanation Source: Real storage manager (RSM)
00 A parameter list address is incorrect. System Action: The system denies the requested service. The
system writes messages and a dump. The system issues an abend
04 The input buffer size is greater than 32 kilobytes.
to the current task.
08 The input buffer address is incorrect.
Programmer Response: Correct the program or obtain proper
0C The output buffer size is greater than 32 kilobytes. authorization from installation management.
10 Both DEFER bits are on. System Programmer Response: Look at the messages in the job
log. Search problem reporting data bases for a fix for the problem. If
14 The format number of the parameter list is incorrect.
no fix exists, contact the IBM Support Center. Provide the messages
18 An IGNORE attention request was issued by a routine and the dump.
that is not a CLIST capable attention exit routine.
1C An IBUF or OBUF address has been specified, but is not 278
a clean 24-bit address.
Explanation: An error occurred when the system tried to process
20 The caller of STAX DEFER=NO,LINKAGE=BRANCH is an RC, RU, VRC, or VRU form of the GETMAIN macro, or an RC or
not running in task mode. RU form of the FREEMAIN macro or the STORAGE RELEASE
24 The caller of STAX DEFER=NO,LINKAGE=BRANCH is macro. The system attempted to get local system queue area
locked. (LSQA) storage to support the request, but no central storage is
available to back the LSQA storage.
28 The caller of STAX DEFER=NO,LINKAGE=BRANCH is
disabled. Source: Virtual storage manager (VSM)
2C The caller of STAX DEFER=YES,LINKAGE=BRANCH is System Action: The system abnormally ends the address space
not running in task mode. where the job was running.
Source: Region control task (RCT) Programmer Response: Run the job step again. If the system
issues this abend again, notify the system programmer.
System Action: The system abends the program that issued the
STAX macro. System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
System Completion Codes SCC-115
279 282
24 No CLASS name specified.
279
2C Incorrect LOG option specified. (This code is used only
Explanation: While processing the end of an I/O request, the
through RACF Version 1.4.)
system found an error in the I/O parameters.
30 Volume serial specified for class other than DATASET.
Register 2 contains a reason code, as follows:
34 File sequence number not valid.
Code Explanation
38 File sequence number specified for non-tape data set.
04 The system found an incorrect buffer control block
(BUFC). 3C Tape label parameter specified for non-tape data set.
14 The system found an incorrect buffer address while 40 Tape label option not valid.
trying to perform I/O. 44 Erase-on-scratch request not valid.
Source: Input/output supervisor (IOS) 48 USERID = * was specified on the REQUEST=AUTH. * is
System Action: The system abnormally ends the current task. an unacceptable RACF user ID.
Programmer Response: Do the following: 4C For the ENTITYX keyword, both the entity name length
and the buffer length are zero.
1. Check to see if the program incorrectly modified the I/O parame-
ters. Correct any errors. 50 Buffer length is not valid:
2. Recompile the job step. Less than zero
3. Run the job step again. Greater than 255
Not zero but less than the entity name length.
27B 54 Entity name length is not valid:
Explanation: Processing for the PURGEDQ macro issued a Less than zero
FESTAE macro to establish recovery. An error occurred during
FESTAE processing. The PURGEDQ and FESTAE macros were Greater than 44 if CLASS=DATASET, or greater
issued correctly: They did not cause the error. The problem is an than the length for that class as defined in the class-
environmental error. descriptor table
Source: Supervisor control Greater than 44 if CLASS=DATASET, or greater
than the maximum length for that class as defined in
System Action: The system abnormally ends the task that issued the class-descriptor table.
the PURGEDQ macro. The system may write a logrec data set error
record. 58 The in-storage profile provided to the REQUEST=AUTH
was not at the version required by RACF. Ensure that
Operator Response: If the system programmer asks for an SVC the version of the in-storage profile (addressed by the
dump, set the following SLIP trap: ENTITY parameter with CSA specified) is at the required
SLIP SET,COMP=27B,ACTION=SVCD,END version number.
Programmer Response: Rerun the job. If the problems recurs, 5C The entity name contains a blank.
contact the system programmer.
If the ENTITYX keyword is specified and the entity name
System Programmer Response: Search problem reporting data length is given, the name has a blank in the beginning,
bases for a fix for the problem. If no fix exists, ask the operator to in the middle, or at the end.
set a SLIP trap to obtain an SVC dump. Contact the IBM Support
60 RTOKEN keyword is mutually exclusive with the CSA
Center. Provide the SVC dump and, if available, the logrec data set
and PRIVATE parameters of the ENTITY keyword.
error record.
64 ACEE not valid.
282 68 Unauthorized caller specified subpool greater than 127
on RACROUTE MSGSP parameter.
Explanation: An error was detected by RACF in the parameters
passed to RACF for RACROUTE REQUEST=AUTH processing. 6C The message chain pointed to by SAFPMSAD for an
unauthorized caller contains too many elements, indi-
System Action: The system terminates the task.
cating a chaining problem.
Programmer Response: Register 15 contains a hexadecimal
Identify and correct the indicated error.
reason code (message ICH409I, if issued, also contains this reason
code): Problem Determination: Use the reason code in Register 15 to
identify the error. If the issuer of the RACF macro is a user routine
Code Explanation
(such as an installation exit), correct the parameter list specified for
04 Parameter list length not valid. the RACF macro in the installation exit. If the issuer of the RACF
10 APF authorization, or system key 0-7, or supervisor state macro is an IBM routine, see OS/390 Security Server (RACF) Diag-
required for CSA, LOG, PRIVATE, PROFILE, ACEE, nosis Guide for information on diagnosing abends and reporting
UTOKEN, USERID, or GROUPID option. abend problems to IBM.
14 ATTR option not valid. Note: For batch jobs, if you need to do dump analysis but do not
have a dump, run the job again. For batch jobs using
18 Volume serial required but not supplied. DSMON, a RACF command, or the RACF report writer,
1C Inconsistent PROFILE/ENTITY flag settings. specify a SYSABEND DD statement in the job. This will
ensure that a dump is taken.
20 No resource name or PROFILE specified.
SCC-116 OS/390 V2R8.0 MVS System Codes
283 285
Diagnosis Guide for information on diagnosing abends and reporting
283
abend problems to IBM.
Explanation: An error was detected by RACF in the parameters
Note: For batch jobs, if you need to do dump analysis but do not
passed to RACF for RACROUTE REQUEST=VERIFY processing.
have a dump, run the job again. For batch jobs using
System Action: The system terminates the task. DSMON, a RACF command, or the RACF report writer,
Programmer Response: Register 15 contains a hexadecimal specify a SYSABEND DD statement in the job. This will
reason code. (Message ICH409I, if issued, also contains this reason ensure that a dump is taken.
code.)
285
Code Explanation
Explanation: RACF detected an error in the parameters passed to
04 Incorrect parameter list length.
it for RACDEF request processing.
14 ENVIR data specified was not valid.
System Action: The system terminates the task.
18 USERID specified did not conform to length require-
Programmer Response: Register 15 contains a hexadecimal
ments.
reason code. (Message ICH409I, if issued, also contains this reason
1C PASSWRD specified did not conform to length require- code.)
ments.
Code Explanation
20 GROUP specified did not conform to length require-
04 Parameter list length is not valid.
ments.
08 Level number is not valid.
24 NEWPASS specified did not conform to length require-
ments. 0C TYPE option is not valid.
28 OIDCARD specified had length field=0. 10 Resource name required. Entity-name (and newname
keywords, if specified) must point to valid, non-blank
30 Incorrect combination of ENVIR keyword data and
resource names.
USERID, PASSWRD, NEWPASS, START, OIDCARD,
TERMID, APPL SESSION, TRUSTED, REMOTE, 14 New data set name or old volume serial specified but
SECLABEL, EXENODE, SUSERID, SNODE, SGROUP, address is zero.
POE, TOKNIN, and STOKEN specified. 18 Volume serial required but not specified.
34 Incorrect combination of ENVIR keyword data and 1C New data set name and old volume serial flags both set.
GROUP specified.
24 Parameters supplied which are inconsistent for a general
38 ENVIR = CHANGE specified but no ACEE exits. resource class other than DATASET. These incorrect
3C User ID specified is *NONE* and REQUEST=VERIFY is parameters might be model name, model volume serial,
not branch entered. VSAM data set bit on, old volume serial, or new data set
name.
40 Reserved
28 Model resource information supplied with type other than
44 ENVIR=CREATE and SESSION=APPCTP were speci-
DEFINE for DATASET class.
fied but POE was not specified and is required in this
case. 2C Model name supplied but model volume serial not sup-
plied.
48 ENVIR=CREATE and SESSION=APPCTP were speci-
fied but APPL was not specified and is required in this 30 Unqualified data set name specified. This return code is
case. not issued if RACFIND=NO was specified.
4C The ACEE specified does not appear to be a valid 34 Old volume serial number is absent for CHGVOL
ACEE. request.
50 The ENVRIN keyword was specified and the ENVR 38 Length of the unit field is not valid.
object storage area address was zero, or, either the 3C AUDIT value is not valid.
ENVRIN or ENVROUT keyword was specified and the
ENVR object storage area was not on a doubleword 40 Specified OWNER is not valid. This reason code can
boundary. occur for several reasons. Among the possible reasons
are:
54 The ENVRIN keyword was specified and the ENVR
object contained in the ENVR object storage area was The OWNER is not a RACF-defined user ID or
larger than the ENVR object storage area specified. group ID.
This can be caused by using an ENVR object from The OWNER is a RACF-defined user ID but that
another external security manager. For example, MCS user ID is revoked.
console services routes commands from other systems 44 UACC value is not valid.
with ENVRIN data.
48 Rename request is not valid. Either ENTITY name or
Identify and correct the indicated error. NEWNAME name, but not both, is a generic name. This
System Programmer Response: Use the reason code in Register reason code could occur because of the attempt to
15 to identify the error. If the issuer of the RACF macro is a user create a data set profile with a single-qualifier name,
routine (such as an installation exit), correct the parameter list speci- when RACF protection for single-qualifier names has not
fied for the RACF macro in the installation exit. If the issuer of the been activated (SETROPTS command with PREFIX
RACF macro is an IBM routine, see OS/390 Security Server (RACF) specified). Note that there are several cases in which
data set profiles can be created automatically: when
System Completion Codes SCC-117
285 285
users with the ADSP attribute create data sets, when A0 Buffer length specified with NEWNAMX keyword is not
PROTECT=YES is specified in JCL, and when a user valid:
issues the ADDSD command.
Less than zero
4C Type=CHGVOL specified for TAPE.
Greater than 255
50 Parameters specified for TAPE are not valid.
Not zero but less than the entity name length.
54 FILESEQ omitted when required for TAPE.
A4 Name length specified with NEWNAMX keyword is not
58 Operands specified for DASD are not valid. valid:
5A The in-storage profile provided to the RACHECK request The specified length is less than zero.
was not at the version required by RACF. Ensure that
The specified length is greater than 44 if
the version of the in-storage profile (addressed by the
CLASS=DATASET or greater than the maximum
ENTITY parameter with CSA specified) is at the required
length for that class as defined in the class-
version number.
descriptor table.
5C FILESEQ value is not valid.
The name that was supplied is longer than 44 if
60 TAPELBL value is not valid. CLASS=DATASET or longer than the maximum
length for that class as defined in the class-
64 EXPDT/RETPD value is not valid.
descriptor table.
68 NOTIFY user ID is not valid.
A8 For the NEWNAMX keyword, both the entity name
6C RESOWNER specified for other than TYPE=DEFINE. length and the buffer lengths are zero.
70 Specified RESOWNER is not valid. AC The profile name for the FILE and DIRECTRY class
74 MGMTCLAS and/or STORCLAS specified without does not contain at least two valid qualifiers for keyword
RESOWNER. ENTITY or ENTITYX.
78 Length for MGMTCLAS is not valid. The profile name contains only one qualifier.
7C Length for STORCLAS is not valid. The profile name begins with a period.
80 Length for RESOWNER is not valid. The second qualifier is longer than 8 characters.
84 Specified SECLABEL is not valid. B0 The profile name for the FILE and DIRECTRY class
does not contain at least two valid qualifiers for keyword
88 Buffer length specified with ENTITYX keyword is not
MENTITY or MENTX.
valid:
The profile name contains only one qualifier.
Less than zero
The profile name begins with a period.
Greater than 255
The second qualifier is longer than 8 characters.
Not zero but less than the entity name length
B4 The profile name for the FILE and DIRECTRY class
8C Name length specified with ENTITYX keyword is not
does not contain at least two valid qualifiers for keyword
valid.
NEWNAME or NEWNAMX.
The specified length is less than zero.
The profile name contains only one qualifier.
The specified length is greater than 44 if
The profile name begins with a period.
CLASS=DATASET or greater than the maximum
length for that class as defined in the class- The second qualifier is longer than 8 characters.
descriptor table. B8 The entity name contains a blank:
The name which was supplied is longer than 44 if If the ENTITYX keyword is specified and the entity name
CLASS=DATASET or longer than the maximum length is given, the name has a blank in the beginning,
length for that class as defined in the class- in the middle, or at the end.
descriptor table.
BC The model profile name contains a blank.
90 For the ENTITYX format, both the entity name length
If the MENTX keyword is specified and the name length
and the buffer length are zero.
is given, the name has a blank in the beginning, in the
94 Buffer length specified with MENTX keyword is not valid: middle, or at the end.
Less than zero C0 The new profile name contains a blank.
Greater than 255 If the NEWNAME keyword is specified and the new
Not zero but less than the entity name length name length is given, the name has a blank in the
beginning, in the middle, or at the end.
98 Name length specified with MENTX keyword is not valid:
C8 Specified SECLVL is not valid:
The specified length is less than zero.
The number of data fields is not zero or one.
The specified length is greater than 44 if
CLASS=DATASET or greater than the maximum The value of the data fields is not within the range
length for that class as defined in the class- of 1 - 254.
descriptor table. Identify and correct the indicated error.
9C For the MENTX keyword, both the entity name length System Programmer Response: Use the reason code in Register
and the buffer lengths are zero. 15 to identify the error. If the issuer of the RACF macro is a user
SCC-118 OS/390 V2R8.0 MVS System Codes
28A 2C6
routine (such as an installation exit), correct the parameter list speci- Resource Class
fied for the RACF macro in the installation exit. Code Resource Name Resource Description
16 TaskServ implementation class for the
Note: For batch jobs, if you need to do dump analysis but do not
subtask services
have a dump, run the job again. For batch jobs using
17 WkldMgmt implementation class for the
DSMON, a RACF command, or the RACF report writer, workload manager interface
specify a SYSABEND DD statement in the job. This will
18 XcfGroup implementation class for the
ensure that a dump is taken. cross-system coupling facility
interface
28A 19 XLngServ implementation class for the
cross-language services
Explanation: A caller requested fixing or freeing of a page. The 20 XMemServ implementation class for the
request was in 31-bit addressing and was without proper authori- cross-memory services
zation.
Source: Real storage manager (RSM) Source: MQSeries Workflow for OS/390
System Action: The system denies the requested service. The System Action: The system issues an ABEND dump.
system writes messages and a dump. The system issues an abend Programmer Response: None.
to the current task.
System Programmer Response: Search the problem reporting
Programmer Response: Correct the program or obtain proper data bases for a fix for the problem. If no fix exists, contact the IBM
authorization from installation management. Support Center and provide the ABEND dump.
System Programmer Response: Look at the messages in the job
log. Search problem reporting data bases for a fix for the problem. If 2C6
no fix exists, contact the IBM Support Center. Provide the messages
Explanation: The MIHQUERY service, the IOSCDR service, the
and the dump.
IOSPTHV service, or the IOSCAPU service has encountered an
abend condition while attempting to satisfy the caller's request.
2C2
MIHQUERY
Explanation: The MQSeries Workflow for OS/390 server instance
The reason codes for the MIHQUERY service are as follows:
subtask encountered a severe internal error.
0001 Caller of MIHQUERY is not in supervisor state.
The reason code identifies the source of the error. It has the format
X'rrmmnnnn', where rr denotes the resource class (as detailed in 0002 Caller of MIHQUERY is not in key 0-7.
the table that follows), mm denotes the method of the resource 0003 Incorrect parameter list. For one of the following
class, and nnnn identifies the place within the method where the reasons, an error occurred when the MIHQUERY service
error was encountered. tried to copy the list:
Resource Class The caller passed an incorrect parameter list
Code Resource Name Resource Description address.
01 Resource abstract class for workflow
server resources
The caller passed an address that the caller did not
own.
02 FmSrvRes abstract class for workflow
server instance resources The storage was in an incorrect key.
03 FmDevRes abstract class for workflow
server input/output device
0004 Incorrect parameter list. For one of the following
resources reasons, an error occurred when the MIHQUERY service
04 SystCons implementation class for the tried to update the list:
system console interface
The caller passed an incorrect parameter list
05 Diagnose implementation class for the
flight recorder
address.
06 FifoLock implementation class for the The caller passed an address that the caller did not
queue serialization own.
07 MvsMsgSv implementation class for the
MVS message services interface
The storage was in an incorrect key.
08 DevQueue implementation class for the in- The caller might have freed the parameter list between
storage queues the time when MIHQUERY copied the parameter list and
09 ErrStack implementation class for the the time when it updated the list.
error recovery
10 ServerDS implementation class for the data
0005 The caller of MIHQUERY passed an incorrect UCB
set access address in the parameter list.
11 Security implementation class for the 0006 The caller of MIHQUERY is in cross memory mode; that
security server interface
is, PASN=HASN=SASN is not in effect.
12 SrvGroup implementation class for the
subtask management IOSCDR
13 SynchEcb implementation class for the The reason codes for the IOSCDR service are as follows:
subtask synchronization
14 TimeServ implementation class for the 0100 Incorrect authorization. For LINKAGE=LINK callers, the
timer interface caller is not in supervisor state. For LINKAGE=SYSTEM
15 ExtTrace implementation class for the callers, the caller is not any one of the following:
component trace interface
In supervisor state
System Completion Codes SCC-119
2C6 2C6
In PKM 0-7 0206 Incorrect CDRAREA. For one of the following reasons,
In problem state an error occurred when the IOSCDR service tried to
In PSW key 0-7 update the CDRAREA.
APF-authorized
The caller passed an incorrect CDRAREA address.
RACF authorized to the FACILITY class and the
IOSCDR entity. The caller passed an address that the caller did not
own.
0101 Caller of IOSCDR is not in task mode.
The storage was in a key that is not accessible from
0102 Caller of IOSCDR is locked.
the key of the caller.
0103 Incorrect AMODE. Caller of IOSCDR is not in 31-bit
The caller might have freed the CDRAREA storage
mode.
before IOSCDR attempted to update it.
0200 Incorrect parameter list. Caller of IOSCDR passed an
IOSPTHV
incorrect version of the parameter list.
The reason codes for the IOSPTHV service are as follows:
0201 Incorrect parameter list. The integrity of the parameter
list was compromised. For example, more than one 0100 Caller of IOSPTHV is not in supervisor state.
parameter in a list of mutually exclusive parameters was 0101 Caller of IOSPTHV is not in task mode.
specified.
0102 Caller of IOSPTHV is locked.
0202 Incorrect parameter list. For one of the following
0103 Incorrect AMODE. Caller of IOSPTHV is not in 31-bit
reasons, an error occurred when the IOSCDR service
mode.
tried to read the list:
0200 Incorrect parameter list. Caller of IOSPTHV passed an
The caller passed an incorrect parameter list
incorrect version of the parameter list.
address.
0201 Incorrect parameter list. For one of the following
The caller passed an address that the caller did not
reasons, an error occurred when the IOSPTHV service
own.
tried to read the list:
The storage was fetch protected.
The caller passed an incorrect parameter list
0203 Incorrect parameter list. For one of the following address.
reasons, an error occurred when the service tried to
The caller passed an address that the caller did not
update the list:
own.
The caller passed an incorrect parameter list
The storage was fetch protected.
address.
0202 Incorrect parameter list. For one of the following
The caller passed an address that the caller did not
reasons, an error occurred when the IOSPTHV service
own.
tried to update the list:
The storage was in a key that is not accessible from
The caller passed an incorrect parameter list
the key of the caller.
address.
The caller might have freed the parameter list between
The caller passed an address that the caller did not
the time when the service read the parameter list and
own.
the time when it updated the list. In addition, if the
storage is not accessible from the key of the caller, then The storage was in a key that is not accessible from
reads may work, but updates may not. the key of the caller.
0204 Incorrect IOCTOKEN storage. For one of the following The caller might have freed the parameter list between
reasons, an error occurred when the service tried to the time when the service read the parameter list and
read the IOCTOKEN. the time when it updated the list. In addition, if the
storage is not accessible from the key of the caller, then
The caller passed an incorrect IOCTOKEN address.
reads may work, but updates may not.
The caller passed an address that the caller did not
0203 Incorrect IOCTOKEN storage. For one of the following
own.
reasons, an error occurred when the IOSPTHV service
The storage is fetch protected. tried to read the IOCTOKEN.
0205 Incorrect IOCTOKEN. For one of the following reasons, The caller passed an incorrect IOCTOKEN address.
an error occurred when the service tried to update the
The caller passed an address that the caller did not
IOCTOKEN:
own.
The caller passed an incorrect IOCTOKEN address.
The storage is fetch protected.
The caller passed an address that the caller did not
0204 Incorrect IOCTOKEN. For one of the following reasons,
own.
an error occurred when the service tried to update the
The storage was in a key that is not accessible from IOCTOKEN:
the key of the caller.
The caller passed an incorrect IOCTOKEN address.
The caller might have freed the IOCTOKEN storage
The caller passed an address that the caller did not
between the time when the service read it and the time
own.
when it attempted to update it. In addition, if the storage
is not accessible from the key of the caller, then reads The storage was in a key that is not accessible from
may work, but updates may not. the key of the caller.
SCC-120 OS/390 V2R8.0 MVS System Codes
2F3 2FB
The caller might have freed the IOCTOKEN storage 01000300 The release of the specified captured UCB exceeds the
between the time when the service read it and the time number of captures specified with the LASTING param-
when it attempted to update it. In addition, if the storage eter or in SRB mode.
is not accessible from the key of the caller, then reads
Source: Input/Output Supervisor (IOS)
may work, but updates may not.
System Action: The system continues processing. The caller ends
0205 Incorrect MSGBUF. For one of the following reasons, an
abnormally with the appropriate reason code.
error occurred when the IOSPTHV service tried to
update the MSGBUF. Application Programmer Response: The application recovery
routine should have recorded and/or dumped the data needed to
The caller passed an incorrect MSGBUF address.
debug this problem. The dumped data should include the parameter
The caller passed an address that the caller did not list and its UCB address, the caller's key and the key of the storage
own. that the caller was attempting to obtain. Correct the application and
resubmit. If the recovery routine did not save the dump information,
The storage was in a key that is not accessible from
fix the recovery routine and try to recreate the original problem. If the
the key of the caller.
error recurs, notify the system programmer.
The caller might have freed the MSGBUF storage before
System Programmer Response: If the application programmer is
IOSPTHV attempted to update the MSGBUF.
unable to debug the error, search problem reporting databases for a
IOSCAPU fix for the problem. If no fix exists, contact the IBM Support Center.
The reason codes for the IOSCAPU service are as follows: Provide the dump data from the application recovery routine.
01000100 Caller of IOSCAPU CAPTUCB or IOSCAPU UCAPTUCB
is locked or is not enabled. 2F3
01000101 Caller of IOSCAPU CAPTOACT is locked. Explanation: The job was running when a system failure occurred,
and a system restart was performed. A system job queue entry for
01000102 Caller is in SRB mode during nucleus initialization the job existed at the time of the failure.
program (NIP) processing and authorization for a PC
routine is not available. Source: Initiator/terminator
01000103 Caller of IOSCAPU CAPTUCB or IOSCAPU UCAPTUCB Programmer Response: Resubmit the job.
is in cross memory mode.
2FB
01000104 Caller of IOSCAPU CAPTUCB, IOSCAPU UCAPTUCB,
or IOSCAPU CAPTOACT ASID is in problem state and Explanation: The system has abnormally ended at one of the fol-
is not in key 0-7. lowing points in processing:
01000200 Caller of IOSCAPU passed an incorrect version of the 1. A critical error occurred early in JES3 or the functional sub-
parameter list. system (FSS) initialization or late in JES3 abnormally ending.
The JES3 ESTAE environment had not yet been established or
01000201 For one of the following reasons, the integrity of the
is deleted, so no JES3-formatted ABEND dump is available.
parameter list was compromised:
2. Once JES3 initialization has successfully established the JES3
More than one parameter in a list of mutually exclu-
ESTAE routine (IATABMN), the retry routine (IATABRT) uses
sive parameters was specified.
this ABEND code to return to IATABMN in order to percolate.
A function parameter was not specified.
An MVS dump will always appear for a X'2FB' ABEND, regardless
Reserved fields are not zero. of the original abend code. The original abend code is shown in
A required parameter associated with a function message IAT3713 to the operator and in the JES3-formatted dump.
parameter was not specified. The dump by itself does not tell whether the failing JES3 function
recovered or had to be ended.
01000202 For one of the following reasons, an error occurred when
IOSCAPU tried to read the parameter list: Note: An MVS dump with a 2FB means that IATABRT or a routine
used by module IATABRT failed, thereby producing the 2FB
The caller passed an incorrect parameter list abend.
address.
Source: JES3
The caller passed an address that the caller did not
own. System Action: In the first case, JES3 writes message IAT3702 to
the operator and to a dump data set of the type specified during
The storage was fetch protected. JES3 initialization. This message details critical debugging informa-
01000203 For one of the following reasons, an error occurred when tion.
IOSCAPU tried to update the parameter list: Operator Response: In the first case, respond to message
The caller passed an incorrect parameter list IAT3nnn.
address. Programmer Response: In the second case, analyze the abend
The caller passed an address that the caller did not dump to find the cause of the error.
own. System Programmer Response: Obtain the abend dump for the
The storage was in a key that is not accessible from failing job step.
the key of the caller. If the problem occurred in JES3 you should:
01000204 The access list entry token (ALET) for the parameter list Save the hardcopy log
is not valid. Provide a listing of the initialization deck (JES3OUT)
01000205 The requested function does not exist. Provide a console log from initialization
System Completion Codes SCC-121
2FC 2FC
Check the JESYSMSG data set for error indications current task. TCBEXCPD points to the EXCP debugging area
(XDBA). The XDBA contains diagnostic data associated with the
2FC EXCP processor.
Explanation: While the I/O first level interrupt handler (FLIH) was If the error recurs and the program is not in error, look at the mes-
running, an error occurred. sages 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
Source: Supervisor control Support Center. Provide the JCL for the job and the dump.
System Action: In an attempt to recover, the system abnormally
ends the task that experienced the I/O interrupt. The system writes a 301
logrec data set error record.
Explanation: During processing of a WAIT macro, the system
Operator Response: If the system programmer asks for an SVC found that the wait flag was already on in the event control block
dump, set the following SLIP trap: (ECB). The flag on indicated that a previous WAIT macro was
SLIP SET,COMP=2FC,ACTION=SVCD,END already waiting for posting of the ECB.
System Programmer Response: Do the following: Source: Task management
Find the original abend causing the problem in the system diag- System Action: The system abnormally ends the program that
nostic work area (SDWA) in the logrec data set error record for issued the WAIT macro.
abend X'2FC'. Programmer Response: Change the problem program to eliminate
Search problem reporting data bases for a fix for the problem. If a double wait on a single event. If no double wait is found, ensure
no fix exists, ask the operator to set a SLIP trap to obtain an that the program did not incorrectly modify the ECB. Then run the
SVC dump. Contact the IBM Support Center. Provide the SVC job again.
dump and the logrec data set error records. 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
300 problem. If no fix exists, contact the IBM Support Center. Provide the
program listing and the assembly listing associated with the job.
Explanation: During processing of an I/O request, execute channel
program (EXCP) processing encountered an error. Each X'300'
302
abend code has a reason code that explains the error:
Explanation: During processing of a POST macro, the system
Code Explanation
found an error in the caller's environment. Register 15 contains a
1-2 EXCP encountered an incorrect data extent block (DEB) at hexadecimal reason code that explains the error:
one of the following phases during the validity check:
Code Explanation
Reason code 1 - front end processing
04 The caller does not hold the home address space's local
Reason code 2 - while processing a related request lock.
(RRQE)
08 The caller does not have addressability to the home
The problem can be one of the following: address space.
The DEB does not exist in the DEB TABLE. 14 The caller does not hold the home address space's local
The offset in the DEB TABLE (DEBTBLOF) for this lock.
DEB is less than 1 or greater than the number of 18 The caller does not have addressability to the home
entries in the DEB TABLE. address space.
The DEB address that was obtained from the data 24 The caller does not hold the home address space's local
control block (DCB) does not match any entry in the lock.
DEB TABLE.
28 The caller does not have addressability to the home
3 The DEB is not an EXCP or Indexed Sequential Access address space.
Method (ISAM) DEB.
34 The caller does not hold the home address space's local
4 The system detected that the IOBM field in the input/output lock.
block (IOB) is higher than the maximum extent count
38 The caller does not have addressability to the home
(DEBNMEXT) in the DEB.
address space.
Source: Execute channel program (EXCP)
3C A disabled caller issued a POST macro with the
System Action: The system abnormally ends the current task and LINKAGE=SYSTEM option.
issues a SNAP dump.
40 A caller who held a lock issued a POST macro with the
Programmer Response: Correct the problem that the reason code LINKAGE=SYSTEM option.
indicates. Verify also that the DCB contains the address of the DEB.
48 A caller who was not processing in primary address
Correct the error. Run the job again.
space control (ASC) mode issued a POST macro with
If the error recurs, check the problem program for the error. If the the LINKAGE=SYSTEM option.
error cannot be determined, run the job again, requesting an ABEND
4C A caller who was not authorized for a cross memory
dump. Notify the system programmer.
POST (XMPOST) issued a POST macro with the
System Programmer Response: In the dump, look at field LINKAGE=SYSTEM option.
TCBEXCPD at offset X'C0' in the task control block (TCB) for the
Source: Task management
SCC-122 OS/390 V2R8.0 MVS System Codes
305 306
System Action: The system abnormally ends the program that
306
issued the POST macro.
Explanation: The error occurred during processing of a LINK(X),
Programmer Response: This is probably an error in the calling
XCTL(X), ATTACH(X), or LOAD macro.
program. Modify the code to allow the POST macro to be issued in
the correct environment. Run the job again. An incorrect load to global request was attempted, or the authorized
routine requested a module that could not be found in an authorized
305 library. The module was found either in an unauthorized library or
already loaded in storage but marked as coming from an unauthor-
Explanation: An error occurred when the system tried to process ized library.
an EU, LU, or VU form of the FREEMAIN macro. A reason code in
the SDWACRC field of the system diagnostic work area (SDWA) The reason code in register 15 identifies the error:
explains the error: Code Explanation
Code Explanation 04 A LOAD macro requested, by the load to global option, a
08 System queue area (SQA) storage is not in the specified module residing in a library that is not authorized
subpool. program facility (APF) authorized.
0C Common service area (CSA) storage is not in the speci- 08 A LOAD macro requested, by the load to global option, a
fied subpool. module that is not reentrant.
10 Local system queue area (LSQA) storage is not in the 0C An authorized program requested, by a LINK(X), LOAD,
specified subpool. XCTL(X) or ATTACH(X) macro, a module in a
non-APF-authorized library or concatenation of libraries.
14 Private area storage is not in the specified subpool.
10 A LOAD macro requested, using the GLOBAL=(YES,F)
18 The system could not find a private area subpool. keyword, a module that requires page alignment.
1C Zero length is not specified on a subpool FREEMAIN. 20 A job step module was found in a LNKLST data set that
Zero length must be specified on a subpool FREEMAIN. was not APF authorized; an APF authorized module was
Note: If this error is detected, the calling program is required.
abnormally ended even though EC, LC, or VC is 24 An authorized service attempted, via a LINK(X), LOAD,
specified on the FREEMAIN macro. XCTL(X), or ATTACH(X) macro, to access a copy of a
20 One of the following: load module which is non-reentrant and loaded from an
authorized library by an unauthorized caller. Another
In the CSA, the area specified on a FREEMAIN is
copy of the module could not be found.
larger than the area specified on the original
GETMAIN. 30 The user attempted to use a controlled program but is
not authorized by RACF to use that program. This can
The FREEMAIN start address is not valid.
occur when a user has EXECUTE access to a program
24 One of the following: library's data set profile, even if none of the program
In the private area, the area specified on a modules involved are RACF program protected. Have
FREEMAIN is larger than the area specified on the the system security administrator grant you READ
original GETMAIN. access to the data set profile instead.
The FREEMAIN start address is not valid. 34 The user attempted to use a program while a program-
accessed data set was open.
Source: Virtual storage manager (VSM)
38 The user requested access to an in-storage program
System Action: The system issues message IEA705I. The system that is not RACF-controlled while a program access data
abnormally ends the current task. set (PADS) was open.
Programmer Response: Do the following: Source: Contents supervision (CSV)
Ensure that the FREEMAIN operands A and LV do not specify a System Action: The system issues an ABEND dump.
different subpool and/or key than the subpool or key of the
storage you are trying to free. The system issues a message depending on the reason code
accompanying the abend:
Ensure that the task control block (TCB) specified on the
FREEMAIN request is the same one specified on the corre- Code Message
sponding GETMAIN request. 04 CSV013I
If a caller running in supervisor state and key 0 made the ori- 08 CSV015I
ginal GETMAIN request, ensure that the corresponding
0C CSV019I
FREEMAIN request is also issued in supervisor state and key 0.
10 CSV020I
If a caller in supervisor state and key 0 requests storage in
subpool 0 or 250, the system will satisfy this request with 20 CSV024I
storage from a different subpool. This situation is described in 24 CSV027I
OS/390 MVS Diagnosis: Reference.
30 CSV025I
Check for program errors that incorrectly modify the FREEMAIN
macro expansion. 34 CSV026I
Programmer Response: If the requested module could not be
found, make sure the module exists on a system or user-defined
authorized library. Correct the error, and run the job step again.
System Completion Codes SCC-123
30A 312
System Programmer Response: If the error recurs and the Check for program errors that incorrectly modify the FREEMAIN
program is not in error, see the system programmer response for macro expansion.
accompanying messages in the job log for more information.
If the error recurs and the program is not in error, search problem 30E
reporting data bases for a fix for the problem. If no fix exists, contact Explanation: A program incorrectly issued a SPIE macro in one of
the IBM Support Center. Provide the source input for the job. the following ways:
An unauthorized program specified program interruption code 17
30A
on the macro.
Explanation: An error occurred when the system tried to run an R
A program in supervisor state issued the macro. The macro
form of the FREEMAIN macro. A reason code in the SDWACRC
should be issued by a program running in problem state.
field of the system diagnostic work area (SDWA) explains the error:
The program that issued the macro had a program status word
Code Explanation
(PSW) storage key that did not match the task control block
08 System queue area (SQA) storage is not in the specified (TCB) key.
subpool.
A program issued the macro in 31-bit addressing mode.
0C Common service area (CSA) storage is not in the speci-
Source: Recovery termination manager (RTM)
fied subpool.
System Action: The system sends messages about the problem to
10 Local system queue area (LSQA) storage is not in the
the job log. The system abends the program that issued the macro.
specified subpool.
Programmer Response: If an application program issued the SPIE
14 One of the following:
macro, check the program for the errors listed in the explanation. If
Private area storage is not in the specified subpool. the program is in 31-bit addressing mode, use an ESPIE macro
instead of the SPIE macro. Correct the error. Run the job step again.
The TCB requesting the FREEMAIN is not the same
as the TCB which owns the storage. Usually, the System Programmer Response: If an IBM program issued the
TCB that owns the storage did the GETMAIN. macro, search problem reporting data bases for a fix for the problem.
If no fix exists, contact the IBM Support Center. Provide:
The key of storage does not match. This can
happen when the FREEMAIN is done under a dif- Messages from the job log
ferent PSW key than the GETMAIN. The ABEND or SVC dump
The assembly listing for the job
18 The system could not find a private area subpool.
The JCL for the job
1C Zero length is not specified on a subpool FREEMAIN. The program listing for the job
Zero length must be specified on a subpool FREEMAIN.
20 One of the following: 312
In the CSA, the area specified on a FREEMAIN is Explanation: An error occurred in a LNKLST or library lookaside
larger than the area specified on the original (LLA) directory data access routine. The reason code in register 15
GETMAIN. identifies the error:
The FREEMAIN start address is not valid. Code Explanation
24 One of the following: 1 LLA partitioned data set (PDS) search function failed.
In the private area, the area specified on a PDS search is used to obtain BLDL format directory
FREEMAIN is larger than the area specified on the entries from the LLA directory.
original GETMAIN. 2 LLA fetch search function failed. Fetch search is used to
The FREEMAIN start address is not valid. obtain directory information needed to retrieve a copy of
a staged module from LLA's virtual lookaside facility
Source: Virtual storage manager (VSM) (VLF) data space.
System Action: The system issues message IEA705I. The system 3 LLA logging function failed. LLA logging is used to
abnormally ends the current task. record fetch statistics in the LLA directory for a fetched
Programmer Response: Do the following: module.
Ensure that the FREEMAIN operands A and LV do not specify a 4 LLA search failure count has reached the allowed limit.
different subpool and/or key than the subpool or key of the The failures counted are only those caused by an LLA
storage you are trying to free. directory problem rather than those caused by a user
problem.
Ensure that the task control block (TCB) specified on the
FREEMAIN request is the same one specified on the corre- Source: Contents supervision (CSV)
sponding GETMAIN request. System Action: LLA does one of the following:
If a caller running in supervisor state and key 0 made the ori- Issues message CSV222I and then initiates automatic restart
ginal GETMAIN request, ensure that the corresponding processing
FREEMAIN request is also issued in supervisor state and key 0. Issues message CSV218E and stops processing.
If a caller in supervisor state and key 0 requests storage in The system issues an SVC dump and writes a logrec data set error
subpool 0 or 250, the system will satisfy this request with record.
storage from a different subpool. This situation is described in
OS/390 MVS Diagnosis: Reference. System Programmer Response: See the system programmer
response for message CSV222I or CSV218E.
SCC-124 OS/390 V2R8.0 MVS System Codes
313 328
313 317
Explanation: The error occurred during processing of an OPEN Explanation: The error occurred during processing of a BSAM
macro instruction for a data set on a direct access device. This CLOSE macro instruction with a TYPE=T operand for a data set on
system completion code is accompanied by message IEC144I. Refer a direct access device. This system completion code is accompanied
to the explanation of message IEC144I for complete information by message IEC220I. Refer to the explanation of message IEC220I
about the task that was ended and for an explanation of the return for complete information about the task that was ended and for an
code (rc in the message text) in register 15. explanation of the return code (rc in the message text) in register 15.
Source: DFSMSdfp Source: DFSMSdfp
Programmer Response: Respond as indicated for message Programmer Response: Respond as indicated for message
IEC144I. IEC220I.
System Programmer Response: If the error recurs and the System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 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 information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job. JCL and the program listing for the job.
314 322
Explanation: The error occurred during the processing of a CLOSE Explanation: One of the following occurred:
macro instruction for a data set on a direct access device. This
The system took a longer time to run a job, job step, or proce-
system completion code is accompanied by message IEC211I. Refer
dure than the time specified in one of the following:
to the explanation of message IEC211I for complete information
about the task that was ended and for an explanation of the return – The TIME parameter of the EXEC or JOB statement
code (rc in the message text) in register 15. – The standard time limit specified in the job entry subsystem
Source: DFSMSdfp For a started task under the master subsystem, the TIME
Programmer Response: Respond as indicated for message parameter was not specified on the PROC statement of the cat-
IEC211I. alogued procedure, and the PPT entry did not indicate a system
task
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more Source: System Management Facilities (SMF)
information. Search problem reporting data bases for a fix for the System Action: The system abnormally ends the job, job step, or
problem. If no fix exists, contact the IBM Support Center. Provide the procedure.
JCL and the program listing for the job.
Programmer Response: If the TIME parameter was not specified
on the PROC statement of the catalogued procedure, add the TIME
315 parameter or add a PPT entry for the PGM parameter. Otherwise,
Explanation: An error occurred during the processing of SVC 21 check for program errors. If none exist, specify a longer time in the
(STOW) that could not be attributed to incorrect user input. This TIME parameter. Then run the job again.
completion code is accompanied by message IEC911I. Refer to the
explanation of message IEC911I for complete information about the 328
task that was ended and for an explanation of the return code in reg-
Explanation: During processing of an EXTRACT macro, the
ister 15.
system found that the task control block (TCB) specified in the
Source: DFSMSdfp second operand was not for a subtask of the caller's TCB.
System Action: The STOW task recovery routine has been Source: Task management
invoked. Low real storage and the caller's region have been dumped
System Action: The system abnormally ends the program that
to the SYS1.DUMP data set. The caller's DCB and input registers 0
issued the EXTRACT macro.
and 1 have been included in a software error record written to the
logrec data set. Programmer Response: Change the EXTRACT macro to specify a
TCB for a subtask. If the macro was specified correctly, check for
Programmer Response: Make sure that the STOW macro instruc-
program errors that incorrectly modified the EXTRACT macro expan-
tion is correctly coded, and that the parameter list and DCB involved
sion. Correct the error. Run the job again.
are not modified by your program during the processing of SVC 21.
System Programmer Response: If the error recurs and the
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
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
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
problem. If no fix exists, contact the IBM Support Center. Provide the
source program listing for the job.
JCL, the program listing for the job, the logrec data set error record,
and all printed output and output data sets related to the problem.
System Completion Codes SCC-125
32D 333
0324 The STIMERM CANCEL macro contained an incorrect
32D
STIMERM ID number. The number was either 0 or
Explanation: A program requested an overlay. In answer to the greater than the highest identifier assigned by the
request, the overlay supervisor was using program fetch to load a system.
program segment from the library. Fetch found one of the following:
Source: Timer supervision
A record of an incorrect length
System Action: The system abnormally ends the task that issued
An uncorrectable input/output (I/O) error
the macro.
Note: Overlay programs run only in 24-bit addressing mode, not in
Programmer Response: Check and correct the parameters speci-
31-bit addressing mode.
fied on the STIMERM macro. See OS/390 MVS Programming:
Source: Overlay supervisor Assembler Services Reference for format and restrictions. Check that
System Action: The system abnormally ends the program that a program running in 31-bit addressing mode uses the MVS/SP
requested the overlay. The system writes an ABEND dump, if a Version 2 or later expansion of STIMER.
dump DD statement is provided.
330
Operator Response: If messages show an I/O error on the device
containing the overlay segment, run the job step again. If the I/O Explanation: An unauthorized task attempted to use authorized
error recurs, contact hardware support. options of the DEQ macro instruction during the processing of global
resource serialization.
Programmer Response: If messages did not show an I/O error,
link edit and run the program again. Source: Global resource serialization
System Action: The system issues an ABEND dump.
32E
Programmer Response: Correct the macro instruction. Recompile
Explanation: When a program issued the STIMERM service and run the job step again.
routine, an error occurred. Register 15 contains a hexadecimal
System Programmer Response: If the problem persists, search
reason code:
problem reporting data bases for a fix for the problem. If no fix
Code Explanation exists, contact the IBM Support Center. Provide the abend dump.
010C The Greenwich mean time (GMT), time-of-day (TOD), or
local time (LT) parameter in a STIMERM SET macro 333
specified a value that was greater that 24 hours. Explanation: During processing for an SVC dump, an error
0110 The TIMER service routine received an incorrect occurred.
STIMER or STIMER SET macro parameter. For Register 15 contains a hexadecimal reason code that explains the
example, a program running in 31-bit addressing mode error:
is not using the MVS/SP Version 2 or later expansion of
STIMER. Code Explanation
011C The limit of concurrent STIMERM SET macro requests 04 While dumping global storage, SVC Dump (SDUMP)
was exceeded. detected a start address that is higher that the end
address for a storage range.
0120 The timer service routine cannot access the storage con-
taining the parameters for the STIMERM SET macro. 08 The SDUMP VSM interface routine detected a start
address that is higher than the end address for a
0128 The requested time interval was too large. One of these storage range.
situations occurred: The time interval specified (BINTVL,
DINTVL, MICVL, or TUINTVL), added to the current 10 While dumping local storage, SDUMP detected a start
TOD clock contents, would have exceeded address that is higher than the end address for a
X'FFFFFFFFFFFFFFFF' (a value that would expire on storage range.
September 17, 2042). A value greater than 14 Before enqueueing on the SDUMP resource, SDUMP
X'7FFFFFFF' was specified for BINTVL. detected that it was running in an address space that is
0210 An incorrect parameter was specified on the STIMERM not in the current dump.
TEST macro. 18 After enqueueing on the SDUMP resource, SDUMP
0220 The timer service routine cannot access the storage con- detected that it was running in an address space that is
taining the parameters for the STIMERM TEST macro. not part of the current dump.
0224 The STIMERM TEST macro contained an incorrect 1C SDUMP is running in an environment that is not valid.
STIMERM ID number. The number was either 0 or 20 While processing a synchronous dump, an SDUMP
greater than the highest identifier assigned by the cross memory post failed to post a task which was to
system. complete the dump. SDUMP recovery processing cap-
0310 An incorrect parameter was specified on the STIMERM tured the local storage which was still in real for the
CANCEL macro. address space where the task was located, and then ter-
minated the address space. The dump is unavailable for
0320 The timer service routine cannot access the storage con- user specified DCB SVC dumps.
taining the parameters for the STIMERM CANCEL
macro. Source: Dumping services
System Action: SDUMP may write a logrec data set error record.
Dump data collection ends, and SDUMP proceeds to clean up its
system resources. Message IEA794I indicates which job requested
the dump. When the dump is written to DASD, message IEA911E or
SCC-126 OS/390 V2R8.0 MVS System Codes
335 33F
IEA611I contains the SDRSN bits which indicate the reasons for an 2. Check the parameter list against the SVC 30 or 38 mapping.
incomplete dump. When analyzing the parameter list, remember that the unit
control block (UCB) pointer, if present, is the address of a field
Operator Response: Determined by the system programmer.
that, in turn, contains the address of the UCB.
System Programmer Response: When necessary, ask the oper-
If the parameter list contains incorrect data, continue diagnosis
ator to set a SLIP trap with ACTION=WAIT to obtain a stand-alone
in the program that issued the macro.
dump if abend X'333' recurs.
System Programmer Response: If the problem persists, search
335 problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the ABEND dump.
Explanation: SVC 53, which obtains and releases exclusive control
of a resource associated with a BDAM data set, found that the block
339
for which acquisition or release of exclusive control was requested
was not in the data set. Explanation: SVC 57, which frees a buffer or extends the unsched-
uled list (via a FREEDBUF macro issued either by the user or by the
Source: DFSMSdfp
system) found that the DEB pointed to by the input DCB
Programmer Response: If the RELEX macro was issued the user (DCBDEBAD) was not on any DEB chain associated with that job
should ensure that the BLKREF address supplied in the RELEX step TCB, or did not point back to that DCB, or the request was
macro points to a valid address within the data set described by the issued for a data set that was neither BDAM or ISAM.
input DCB. Make sure also that the address format is compatible
Source: DFSMSdfp
with the addressing scheme specified in the DCBOPTCD field of the
DCB. If the RELEX macro was not issued, the block ID was taken Programmer Response: Make sure that the input DCB address is
from the IOBSEEK field, or in the case of write-add requests, the correct and that the DCBDEBAD field of the input DCB has not been
IOBDNCRF field. These addresses are derived from conversion of overlaid.
the block ID pointed to by the DECRECPT field of the DECB. Make
System Programmer Response: If the error recurs and the
sure that this address is correct and that the format of the block ID is
program is not in error, search problem reporting data bases for a fix
compatible with that specified in the DCBOPTCD field of the DCB
for the problem. If no fix exists, contact the IBM Support Center.
and that the format of the block ID is left-aligned.
System Programmer Response: If the error recurs and the 33E
program is not in error, search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support Center. Explanation: During processing of a DETACH macro that specified
a STAE=YES operand, the system found that the specified subtask
had not completed processing.
337
Source: Task management
Explanation: The error occurred when the end of a data set was
reached. This system completion code is accompanied by message System Action: The system abnormally ends the subtask. If the
IEC024I. Refer to the explanation of message IEC024I for complete STAE macro was issued by the subtask, the specified recovery
information about the task that was ended and for an explanation of routine gains control during abend processing. However, if the
the return code (rc in the message text) in register 15. STAE exit routine specified a retry routine, the retry routine does not
gain control.
Source: DFSMSdfp
Programmer Response: This may or may not be an error,
Programmer Response: Respond as indicated for message
depending on the programmer's intent. If the subtask should com-
IEC024I.
plete processing before it is detached, synchronize the processing
System Programmer Response: If the error recurs and the through the ECB or ETXR parameters on the ATTACH macro that
program is not in error, look at the messages in the job log for more creates the subtask.
information. Search problem reporting data bases for a fix for the
System Programmer Response: If the error recurs and the
problem. If no fix exists, contact the IBM Support Center. Provide the
program is not in error, look at the messages in the job log for more
JCL, the program listing, and the compiler output for the job.
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
338 source program listing for the job.
Explanation: An unauthorized task attempted to use authorized
options of the ENQ macro instruction during the processing of global 33F
resource serialization.
Explanation: An error has been detected during checkpoint restart
Source: Global resource serialization processing. This completion code is accompanied by message
IHJxxxI with the appropriate reason code.
System Action: The system writes an ABEND dump.
Source: DFSMSdfp
Programmer Response: Correct the macro instruction. Recompile
and run the job step again. System Action: No dump is produced; the system attempts to retry
to the cleanup address.
If the problem persists, do the following:
Programmer Response: Respond as indicated in the accompa-
1. Obtain the address of the DEQ parameter list from register 1 in
nying message.
the UNIQUE-3 column of the SVC 30 or SVC 38 entry in the
system trace.
System Completion Codes SCC-127
344 378
RMF is terminated. Register 15 contains the return code from the
344
System Resources Manager depending on the function attempted by
Explanation: The error occurred during the processing of RMF:
SYNADAF, where it was determined that the DCB address was
Byte Attempted Function
incorrect.
0 N/A
Source: DFSMSdfp
1 Reinitialization of workload activity measurement col-
Programmer Response: Register 15 contains the DCB address in
lection after a change in the Installation Performance
error. For BDAM, BPAM, QSAM, BISAM, and QISAM, the DCB
Specification (IPS).
address should be passed to SYNADAF as the PARM1 operand on
the SYNADAF macro instruction. (For BDAM, BPAM, BSAM, and 2 Collection of workload activity measurements.
QSAM, the DCB address is in register 1 on entry to the user's 3 Initialization of workload activity measurements.
SYNAD routine.) For EXCP access method, verify that the
IOBDCBPT field contains the correct DCB address. Correct the error The system writes an ABEND dump for the failing job step.
and rerun the job. System Programmer Response:
System Programmer Response: If the error recurs and the Obtain the SYSOUT output for the job.
program is not in error, look at the messages in the job log for more
Obtain the ABEND dump for the failing job step. If the JCL for the
information. Search problem reporting data bases for a fix for the
step did not contain a DD statement for an ABEND dump, add one
problem. If no fix exists, contact the IBM Support Center. Provide the
of the following statements and run the job step again:
JCL and the program listing for the job.
SYSABEND DD statement
SYSMDUMP DD statement
351
SYSUDUMP DD statement
Explanation: An error was detected during the processing of
Use a SYSMDUMP DD statement if you plan to analyze and format
SETPRT that could not be attributed to incorrect macro instruction
the dump with the interactive problem control system (IPCS).
invocation or incorrect control blocks. This system completion code is
accompanied by message IEC918I. Refer to the explanation of Obtain the logrec data set error record.
message IEC918I for complete information about the task that was Search problem reporting data bases for a fix for the problem. If no
ended and for an explanation of the return code in register 15. fix exists, report the problem to the IBM Support Center.
Source: DFSMSdfp
Programmer Response: Make sure that the SETPRT macro 36F
instruction is correctly coded, and that the parameter list and DCB Explanation: One of the following errors occurred during proc-
involved are not modified by your program during the processing of essing of a job entry subsystem SVC 111:
SVC 81.
An non-valid entry code was passed to SVC 111.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more DEBCHK processing found that the DEB (data extent block) was
information. Search problem reporting data bases for a fix for the invalid.
problem. If no fix exists, contact the IBM Support Center. Provide the The DEB was not a subsystem DEB.
JCL, the program listing for the job, and the logrec data set error
Source: JES2
record.
System Action: The program issuing the SVC terminates.
35F System Programmer Response: Be sure the program is author-
ized to use SVC 111 and check that the SVC is issued at the correct
Explanation: In order to initiate a nonswappable program or V=R
point in the program. Correct the error and rerun the job.
job step, the system issued a SYSEVENT TRANSWAP macro to
swap out an address space. Before the system could complete the If the problem recurs and if the program is not in error, search
swap, the address space became unswappable. problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
Source: System resources manager (SRM)
System Action: The system abnormally ends the initiator of the
378
job. The system writes messages and a logrec data set error record.
Explanation: An error when the system tried to process an RU or
System Programmer Response: This is probably a system error.
VRU form of the FREEMAIN macro or the STORAGE RELEASE
Resubmit the job. If the error recurs, search problem reporting data
macro. A reason code in the SDWACRC field of the system diag-
bases for a fix for the problem. If no fix exists, contact the IBM
nostic work area (SDWA) explains the error:
Support Center. Provide the logrec data set error record and the
SYSOUT output for the job. Code Explanation
08 System queue area (SQA) storage is not in the specified
36D subpool.
Explanation: An error was detected in communications between 0C Common storage area (CSA) storage is not in the speci-
RMF and the System Resources Manager while attempting to ini- fied subpool, or it is not in the specified key.
tialize, collect, or reinitialize workload activity measurements. 10 Local system queue area (LSQA) storage is not in the
Source: Resource Measurement Facility (RMF) specified subpool.
System Action: All RMF measurement collection is terminated. 14 Private area storage is not in the specified subpool, or it
Reinstatement can be attempted and, if successful, RMF will con- is not in the specified key.
tinue under the control of the original options. If reinstatement fails,
SCC-128 OS/390 V2R8.0 MVS System Codes
37A 383
18 The system could not find a private area subpool.
37B
1C A user has requested that storage at virtual address 0
Explanation: While the system was processing a PURGEDQ
be freed. This can happen if the user intended an entire
macro, an error occurred in a resource manager termination routine
subpool, but has incorrectly specified a non-zero length
(RMTR).
with an address of 0. Zero length must be specified on a
subpool FREEMAIN or STORAGE RELEASE. Another Source: Supervisor control
possibility is that the user has specified the wrong System Action: The system records the address of the failing
address. service request block (SRB) in a logrec data set error record. The
20 One of the following: system asks for a retry and PURGEDQ processing continues. The
system does not return control to the RMTR in which the error
In the CSA, the area specified on a FREEMAIN or
occurred.
STORAGE RELEASE is larger than the area speci-
fied on the original GETMAIN or STORAGE System Programmer Response: Do the following:
OBTAIN. Use the program status word (PSW) address in the logrec data
The FREEMAIN or STORAGE RELEASE start set error record to identify the failing RMTR.
address is not valid. Search problem reporting data bases for a fix for the problem. If
24 One of the following: no fix exists, contact the component group associated with this
module at the IBM Support Center. Provide the logrec data set
In the private area, the area specified on a
error record.
FREEMAIN or STORAGE RELEASE is larger than
the area specified on the original GETMAIN or
STORAGE OBTAIN. 37D
The FREEMAIN or STORAGE RELEASE start Explanation: During processing of an EVENTS macro, the system
address is not valid. found that another task was currently waiting on the EVENTS table.
Source: Virtual storage manager (VSM) Source: Task management
System Action: The system issues message IEA705I. The system System Action: The system abnormally ends the program that
abnormally ends the current task. issued the EVENTS macro.
Programmer Response: Do the following: Programmer Response: Ensure that no program can issue any
EVENTS macro that specifies a table currently being waited on.
Ensure that the FREEMAIN or STORAGE RELEASE operands
Correct the error. Run the job again.
A and LV do not specify a different subpool and/or key than the
subpool or key of the storage you are trying to free. System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
Ensure that the task control block (TCB) specified on the
information. Search problem reporting data bases for a fix for the
FREEMAIN or STORAGE RELEASE request is the same one
problem. If no fix exists, contact the IBM Support Center. Provide the
specified on the corresponding GETMAIN or STORAGE
program listing and the assembly listing associated with the job.
OBTAIN request.
If a caller running in supervisor state and key 0 made the ori- 382
ginal GETMAIN or STORAGE OBTAIN request, ensure that the
corresponding FREEMAIN or STORAGE RELEASE request is Explanation: The RACROUTE REQUEST=AUTH preprocessing or
also issued in supervisor state and key 0. postprocessing exit routine passed an invalid return code to RACF.
The return code was not part of the defined interface.
If a caller in supervisor state and key 0 requests storage in
subpool 0 or 250, the system will satisfy this request with System Action: The system abnormally terminates the task.
storage from a different subpool. This situation is described in Programmer Response: Possible user error. Register 15 contains
OS/390 MVS Diagnosis: Reference. the return code from the exit routine. Verify that the exit routine is
Check for program errors that incorrectly modify the FREEMAIN issuing valid return codes.
or STORAGE RELEASE macro expansion. System Programmer Response: If the installation exit is issuing a
correct return code and RACF still issues this abend, call your IBM
37A support center for advice about whether this is a documentation error
or an incorrect output error.
Explanation: During processing of an EVENTS macro, the system
found that another task was currently waiting on the EVENTS table. Note: Before calling IBM, make sure the return code passed by the
installation exit is correct.
Source: Task management
System Action: The system abnormally ends the program that 383
issued the EVENTS macro.
Explanation: The RACROUTE REQUEST=VERIFY preprocessing
Programmer Response: Ensure that only one task at one time can or postprocessing exit routine passed an invalid return code to
wait on the EVENTS table. Correct the error. Run the job again. RACF. The return code was not part of the defined interface.
System Programmer Response: If the error recurs and the System Action: The system abnormally terminates the task.
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 Programmer Response: Possible user error. Register 15 contains
problem. If no fix exists, contact the IBM Support Center. Provide the the return code from the exit routine. Verify that the exit routine is
program listing and the assembly listing associated with the job. issuing valid return codes. See OS/390 Security Server External
Security Interface (RACROUTE) Macro Reference for the correct
return codes.
System Completion Codes SCC-129
385 3C4
System Programmer Response: If the installation exit is issuing a Resource Class
correct return code and RACF still issues this abend, call your IBM Code Resource Name Resource Description
support center for advice about whether this is a documentation error 13 SynchEcb implementation class for the
or an incorrect output error. See OS/390 Security Server (RACF) subtask synchronization
Diagnosis Guide for information on reporting documentation errors or 14 TimeServ implementation class for the
incorrect output to IBM. timer interface
15 ExtTrace implementation class for the
Note: Before calling IBM, make sure the return code passed by the component trace interface
installation exit is correct. 16 TaskServ implementation class for the
subtask services
385 17 WkldMgmt implementation class for the
workload manager interface
Explanation: The RACROUTE REQUEST=VERIFY preprocessing 18 XcfGroup implementation class for the
or postprocessing exit routine passed an invalid return code to cross-system coupling facility
RACF. The return code was not part of the defined interface. interface
19 XLngServ implementation class for the
System Action: The system abnormally terminates the task. cross-language services
Programmer Response: Possible user error. Register 15 contains 20 XMemServ implementation class for the
the return code from the exit routine. Verify that the exit routine is cross-memory services
issuing using valid return codes. See OS/390 Security Server
External Security Interface (RACROUTE) Macro Reference for the Source: MQSeries Workflow for OS/390
correct return codes. System Action: The system issues an ABEND dump.
System Programmer Response: If the installation exit is issuing a Programmer Response: None.
correct return code and RACF still issues this abend, call your IBM
support center for advice about whether this is a documentation error System Programmer Response: For reason code X'1726nnnn',
or an incorrect output error. See OS/390 Security Server (RACF) verify the setup for the workload manager application environment
Diagnosis Guide for information on reporting documentation errors or and restart the server.
incorrect output to IBM. For other reason codes, search the problem reporting data bases for
Note: Before calling IBM, make sure the return code passed by the a fix for the problem. If no fix exists, contact the IBM Support Center
installation exit is correct. and provide the ABEND dump.
3C2 3C4
Explanation: The MQSeries Workflow for OS/390 workload Explanation: During system processing, an internal system request
manager selector subtask encountered a severe internal error. encountered an unexpected error.
The reason code identifies the source of the error. It has the format Register 15 contains a hexadecimal reason code.
X'rrmmnnnn', where rr denotes the resource class (as detailed in Code Explanation
the table that follows), mm denotes the method of the resource
00000001 Recovery routine (ESTAEX) could not be established.
class, and nnnn identifies the place within the method where the
error was encountered. 00000002 The request came from an unauthorized program.
00000003 Not enough storage was available.
Resource Class
Code Resource Name Resource Description 00000004 POST returned an an error code.
01 Resource abstract class for workflow
server resources
00000005 ATTACH did not complete successfully.
02 FmSrvRes abstract class for workflow 00000006 LXRES did not complete successfully.
server instance resources
00000007 AXSET did not complete successfully.
03 RmDevRes abstract class for workflow
server input/output device 00000008 Too many ETEs (entry table entries).
resources
04 SystCons implementation class for the
00000009 Incorrect EX (entry index)
system console interface 0000000A ARR (associated recovery routine) not found.
05 Diagnose implementation class for the
flight recorder 0000000B A PC integrity error occurred.
06 FifoLock implementation class for the 0000000C A PC provided an incorrect attribute.
queue serialization
07 MvsMsgSv implementation class for the
0000000D ETCRE did not complete successfully.
MVS message services interface 0000000E ETCON did not complete successfully.
08 DevQueue implementation class for the in-
storage queues 0000000F An unexpected error occurred.
09 ErrStack implementation class for the 00000010 ENQ did not complete successfully.
error recovery
10 ServerDS implementation class for the data
00000011 Start was incorrect.
set access 00000012 The SSCVT was incorrect.
11 Security implementation class for the
security server interface 00000013 The DSCT was incorrect.
12 SrvGroup implementation class for the 00000014 Dispatcher control blocks were incorrect.
subtask management
00000015 ALESERV did not complete successfully.
SCC-130 OS/390 V2R8.0 MVS System Codes
3C5 3C6
00000016 DSPSERV did not complete successfully. The calling task
The task that previously issued IARSUBSP IDEN-
00000017 IEFJSVEC did not complete successfully.
TIFY
00000018 A required routine could not be found. A task higher in the task hierarchy than the calling
| 00000019 RESMGR did not complete successfully. task or the task that previously issued IARSUBSP
IDENTIFY.
| 0000001A Recovery was entered and there was no available entry
| on the dynamic area stack for the recovery routine to Programmer Response: Correct the range list entry to
| use. specify storage owned by one of the tasks listed in the
error description. If the range list entry is correct, rede-
Source: MVS reuse
sign the program so that the task that issues the
System Action: If the error occurred during address space initial- IARSUBSP IDENTIFY (or a task higher in the task hier-
ization, the initialization process terminates. archy) owns the storage and is the task that issued any
previous IARSUBSP IDENTIFY requests.
Programmer Response: Search problem reporting data bases for
a fix for the problem. If no fix exists, contact the IBM Support Center, xx0116xx Subspace identity failed. A segment in the storage range
providing the reason code that accompanies the abend. is part of a shared segment.
Programmer Response: Correct the storage range list
3C5 entry to specify a storage range that does not include
Explanation: This abend is issued by the TCP/IP product. Please pages that are part of a shared segment.
see the TCP/IP documentation for more information. xx0211xx IARSUBSP CREATE failed. The subspace name is
incorrect. The name must not be blank, or begin with a
3C6 numeric character. The name must be left-justified,
padded to the right with blanks, and must contain only
Explanation: An error occurred during IARSUBSP macro proc-
alphanumeric characters and the characters @, $, and
essing.
#.
Source: Real Storage Manager (RSM)
Programmer Response: Correct the subspace name
The reason code in register 15 identifies the error. When an entry in specified on the NAME parameter, and resubmit the job.
the range list (specified on the RANGLIST parameter) causes the
xx0301xx IARSUBSP ASSIGN failed. The caller's primary and
abend, GPR 2 contains the address of the range list element in error
home address spaces must be the same.
and GPR 3 contains the address of the storage being processed.
Programmer Response: Change the cross memory
Code Meaning
mode so that the primary and home address spaces are
xx0108xx IARSUBSP IDENTIFY failed. The value specified in the the same, and resubmit the job.
NUMRANGE parameter must be greater than zero and
xx0302xx IARSUBSP ASSIGN failed. The caller held a lock.
not greater than 16.
Programmer Response: Release all locks and resubmit
Programmer Response: Correct the value on the
the job.
NUMRANGE parameter.
xx0303xx IARSUBSP ASSIGN failed. A protection exception
xx0109xx IARSUBSP IDENTIFY failed. The number of pages
occurred while the caller was referencing the parameter
specified by the second fullword of the range list entry
list.
must be greater than 0 and a multiple of 256.
Programmer Response: The parameter list must be in
storage that the caller can access. Make sure the
Programmer Response: Correct the second fullword of
storage was obtained by the caller or passed to the
the range list entry to specify the correct amount of
caller by a task higher in the task hierarchy.
storage and resubmit the job.
xx0304xx IARSUBSP ASSIGN failed. The caller issued a macro
xx010Axx IARSUBSP IDENTIFY failed. The address of the storage
version that is not valid.
specified by the first fullword of the range entry must be
aligned on a segment boundary. A segment is 1 mega- Programmer Response: Use the IARSUBSP macro to
byte (1,048,576 bytes) long. generate the parameter list.
Programmer Response: Correct the first fullword of the xx0308xx IARSUBSP ASSIGN failed. The value specified in the
range list entry to specify a storage address on a NUMRANGE parameter must be greater than zero and
segment boundary, and resubmit the job. not greater than 16.
xx0112xx IARSUBSP IDENTIFY failed. The storage specified by Programmer Response: Correct the value on the
the range list entry must be pageable and located in NUMRANGE parameter.
either high private or low private storage, and must have xx0309xx IARSUBSP ASSIGN failed. The number of pages speci-
been previously obtained using the STORAGE or fied by the second fullword of the range list entry must
GETMAIN macro. be greater than 0 and a multiple of 256 for storage
Programmer Response: Correct the range list entry to addresses above 16 megabytes.
specify pageable, private storage, or change the subpool Programmer Response: Correct the value specified in
from which the storage was obtained, and resubmit the the second fullword of the range list entry, and resubmit
job. the job.
xx0113xx IARSUBSP IDENTIFY failed. The storage specified by
the range list entry must be owned by one of the
following:
System Completion Codes SCC-131
3C6 3C6
xx030Axx IARSUBSP ASSIGN failed. The range entry must be Programmer Response: Correct the value on the
aligned on a segment boundary for storage addresses NUMRANGE parameter.
above 16 megabytes. A segment is 1 megabyte
xx0409xx IARSUBSP UNASSIGN failed. The number of pages
(1,048,576 bytes) long.
specified by the second fullword of the range list entry
Programmer Response: Correct the first fullword of the must be greater than 0 and a multiple of 256 for storage
range list entry to specify a storage address on a addresses above 16 megabytes.
segment boundary, and resubmit the job.
Programmer Response: Correct the value specified in
xx030Bxx IARSUBSP ASSIGN failed. The range list entry must the second fullword of the range list entry and resubmit
specify an address that is aligned on a page boundary the job.
for storage addresses below 16 megabytes.
xx040Axx IARSUBSP UNASSIGN failed. The range entry must be
Programmer Response: Correct the first fullword of the aligned on a segment boundary for storage addresses
range list entry to specify a storage address on a page above 16 megabytes. A segment is 1 megabyte
boundary, and resubmit the job. (1,048,576 bytes) long.
xx030Cxx IARSUBSP ASSIGN failed. The specified STOKEN does Programmer Response: Correct the first fullword of the
not represent a valid subspace. range list entry to specify a storage address on a
segment boundary, and resubmit the job.
Programmer Response: Correct the value specified on
the STOKEN parameter and resubmit the job. xx040Bxx IARSUBSP UNASSIGN failed. The range list entry must
specify an address that is aligned on a page boundary
xx0310xx IARSUBSP ASSIGN failed. The range must have been
for storage addresses below 16 megabytes.
specified on a prior IARSUBSP IDENTIFY request
before it can be specified on IARSUBSP ASSIGN. Programmer Response: Correct the first fullword of the
range list entry to specify a storage address on a page
Programmer Response: Ensure that you are supplying
boundary, and resubmit the job.
the correct range list to IARSUBSP ASSIGN, and that
the values in the range list are correct. If so, correct your xx040Cxx IARSUBSP UNASSIGN failed. The specified STOKEN
program design to issue IARSUBSP IDENTIFY before does not represent a valid subspace.
issuing IARSUBSP ASSIGN, and rerun the program.
Programmer Response: Correct the value specified on
xx0311xx IARSUBSP ASSIGN failed. The range already is the STOKEN parameter and resubmit the job.
assigned to another subspace.
xx0412xx IARSUBSP UNASSIGN failed. The range cannot span
across either the 16-megabyte boundary or the
Programmer Response: None necessary. However, 2-gigabyte boundary.
you might want to take some action depending on your
Programmer Response: Change the second fullword of
program. If you resubmit the job, specify a different
the range list entry to specify a valid storage range, and
range of storage that is eligible to be assigned to a sub-
resubmit the job.
space but not yet assigned.
xx050Cxx IARSUBSP DELETE failed. The specified STOKEN does
xx0312xx IARSUBSP ASSIGN failed. The range cannot span
not represent a valid subspace.
across either the 16-megabyte boundary or the
2-gigabyte boundary. Programmer Response: Correct the value specified on
the STOKEN parameter and resubmit the job.
Programmer Response: Change the second fullword of
the range list entry to specify a valid storage range, and xx0510xx IARSUBSP DELETE failed. The caller is running in or is
resubmit the job. eligible to run in the subspace that is to be deleted.
xx0401xx IARSUBSP UNASSIGN failed. The caller's primary and Programmer Response: Correct the STOKEN supplied
home address spaces must be the same. on the STOKEN parameter. If the STOKEN is correct,
change the program design to switch to full address
Programmer Response: Change the cross memory
space addressability before attempting to delete the sub-
mode so that the primary and home address spaces are
space.
the same, and resubmit the job.
xx0511xx IARSUBSP DELETE failed. Another program is running
xx0402xx IARSUBSP UNASSIGN failed. The caller held a lock.
in or is eligible to run in the subspace that is to be
Programmer Response: Release all locks and resubmit deleted.
the job.
Programmer Response: Correct the STOKEN supplied
xx0403xx IARSUBSP UNASSIGN failed. A protection exception on the STOKEN parameter. If the STOKEN is correct,
occurred while the caller was referencing the parameter change the program design to delete the subspace after
list. the program has finished processing.
Programmer Response: The parameter list must be in xx0512xx IARSUBSP DELETE failed. The caller does not own the
storage that can be read by the calling program. subspace to be deleted.
xx0404xx IARSUBSP UNASSIGN failed. The caller issued a macro Programmer Response: Correct the STOKEN supplied
version that is not valid. on the STOKEN parameter. If the STOKEN is correct,
change the program design so the task that created the
Programmer Response: Use the IARSUBSP macro to
subspace deletes it.
generate the parameter list.
xx0608xx IARSUBSP UNIDENTIFY failed. The value specified in
xx0408xx IARSUBSP UNASSIGN failed. The value specified in the
the NUMRANGE parameter must be greater than zero
NUMRANGE parameter must be greater than zero and
and not greater than 16.
not greater than 16.
SCC-132 OS/390 V2R8.0 MVS System Codes
3C7 3C7
Programmer Response: Correct the value on the Programmer Response: Invoke the MODESET macro
NUMRANGE parameter. to change the caller's state or PSW key.
xx0609xx IARSUBSP UNIDENTIFY failed. The number of pages xxFF0Exx IARSUBSP failed. The caller must be in task mode.
specified by the second fullword of the range list entry
Programmer Response: Change the program design to
must be greater than 0 and a multiple of 256.
ensure that the IARSUBSP macro is invoked in task
mode, and resubmit the job.
Programmer Response: Correct the second fullword of
System Action: The system fails the IARSUBSP request.
the range list entry to specify the correct amount of
storage and resubmit the job. Programmer Response: Take the action indicated by Pro-
grammer Response in the reason code description.
xx060Axx IARSUBSP UNIDENTIFY failed. The address of the
storage specified by the first fullword of the range entry
must be aligned on a segment boundary. A segment is 1 3C7
megabyte (1,048,576 bytes) long. Explanation: An error occurred while RACF was attempting to
Programmer Response: Correct the first fullword of the either allocate or unallocate dynamic storage while RACF was
range list entry to specify a storage address on a running in SRB mode.
segment boundary, and resubmit the job. Source: Resource Access Control Facility (RACF)
xxFF01xx IARSUBSP failed. The caller's primary, secondary, and The reason code in register 15 identifies the error:
home address spaces are not the same (the caller is in
Code Explanation
cross memory mode.)
04 BAD LENGTH: The length of the area to get or free is
Programmer Response: Change the cross memory
not greater than zero.
mode so that the primary, secondary, and home address
spaces are the same, and resubmit the job. 08 BAD ALIGNMENT: The pointer to the area to free is not
on a doubleword boundary.
xxFF02xx IARSUBSP failed. The caller held a lock.
0C DUPLICATE FREEMAIN: The area to free has already
Programmer Response: Release all locks and resubmit
been freed.
the job.
10 INCORRECT SUBPOOL: The subpool for the area to
xxFF03xx IARSUBSP failed. A protection exception occurred while
free is not the subpool in which the area is allocated.
the caller was referencing the parameter list.
14 INVALID OVERLAP: Part of the area to free equals part
Programmer Response: The parameter list must be in
of the area allocated, but the match is not correct for
storage that can be read by the calling program. For a
either a full or partial FREEMAIN.
CREATE request, the parameter list must be in storage
that also can be modified by the calling program. 18 NOT FOUND: The area to free does not have a corre-
sponding GETMAIN entry in the tracking table, and the
xxFF04xx IARSUBSP failed. The caller issued a macro version that
caller did not specify that it should not have.
is not valid.
1C FOUND: The area to free has a corresponding
Programmer Response: Use the IARSUBSP macro to
GETMAIN entry in the tracking table, and the caller
generate the parameter list.
specified that it should not have.
xxFF05xx IARSUBSP failed. The reserved fields in caller's
20 NOT FREED: There is a temporary area still allocated at
IARSUBSP parameter list must be zeros.
the end of processing.
Programmer Response: Ensure that you are running
A0 A RACF module issued a get-space request. However,
the program on the correct MVS release, and that you
register 1 is not equal to zero and does not point to a
use the IARSUBSP macro to generate the parameter
buffer previously created by the program.
list.
A4 A RACF module issued a get-space request. However,
xxFF06xx IARSUBSP failed. The caller requested a service that is
the subpool in register 0 is not the subpool in which the
not valid.
previously created buffer is allocated.
Programmer Response: Use the IARSUBSP macro to
A8 A RACF module issued a free-space request. However,
generate the parameter list.
register 1 is equal to zero.
xxFF07xx IARSUBSP failed. The caller must be in 31-bit
AC A RACF module issued a free-space request. However,
addressing mode to use IARSUBSP.
register 1 does not point to the buffer previously created
Programmer Response: Change to 31-bit addressing by the program.
mode by issuing the BASSM or BSM instruction, then
Identify and correct the indicated error.
resubmit the job. BASSM and BSM are described in
Principles of Operation. System Programmer Response: Using IPCS, format the dump
taken for this abend. For an explanation of the dump title, see
xxFF0Dxx IARSUBSP IDENTIFY, CREATE, DELETE, or UNIDEN-
OS/390 Security Server (RACF) Diagnosis Guide.
TIFY failed. The caller must be in supervisor state or
have PSW key 0 - 7. 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.
System Completion Codes SCC-133
3FB 3FC
System Programmer Response: If the error recurs and the
3FB
program is not in error, look at the messages in the job log for more
Explanation: JES3 could not obtain enough storage to either build information. Search problem reporting data bases for a fix for the
a data set block (DSB) or to build a data set status block (DSS). problem. If no fix exists, contact the IBM Support Center. Provide the
Source: JES3 JCL, the program and assembly listings for the job, and the SVC
dump.
System Action: The system ends the user address space.
System Programmer Response: Rerun the job with a SYSABEND 401
DD statement. The problem may not recur. If it does, notify the IBM
Explanation: During processing of a WAIT macro, the system
Support Center.
found an error in the caller's environment.
3FC Register 15 contains a hexadecimal reason code that explains the
error:
Explanation: The system detected an error in the processing fol-
lowing an external interrupt. The program that experienced the Code Explanation
external interrupt is running under a task control block (TCB) or 04 The caller does not hold the home address space's local
service request block (SRB). lock.
A hexadecimal reason code in register 15 explains the error: 08 The caller does not have addressability to the home
Code Explanation address space.
00 The system detected, but does not support, a third 0C A disabled caller issued a WAIT macro with the
recursion of this interrupt. LINKAGE=SYSTEM option.
04 An error occurred during processing for the interrupt. 10 A caller who held a lock issued a WAIT macro with the
LINKAGE=SYSTEM option.
08 An error occurred during a first recursion.
14 A caller who was not processing in task mode issued a
0C An error occurred during a second recursion. WAIT macro with the LINKAGE=SYSTEM option.
Source: Supervisor control 18 A caller who was not processing in primary address
System Action: The system abnormally ends the active task that space control (ASC) mode issued a WAIT macro with
experienced the external interrupt. The system writes a logrec data the LINKAGE=SYSTEM option.
set error record. Source: Task management
Operator Response: If the system programmer asks for an SVC System Action: The system abnormally ends the program that
dump, set the following SLIP trap: issued the WAIT macro.
SLIP SET,COMP=3FC,ACTION=SVCD,END Programmer Response: This is probably an error in the calling
Programmer Response: Resubmit the job. If the error recurs, program. Modify the code to allow the WAIT macro to be issued in
contact the system programmer. the correct environment. Run the program again.
System Programmer Response: Do the following: System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
Find the original abend causing the problem in the system diag-
information. Search problem reporting data bases for a fix for the
nostic work area (SDWA) in the logrec data set error record.
problem. If no fix exists, contact the IBM Support Center. Provide the
Search problem reporting data bases for a fix for the problem. If program listing for the job.
no fix exists, ask the operator to set a SLIP trap to obtain an
SVC dump. Contact the IBM Support Center. Provide the SVC 402
dump and the logrec data set error records.
Explanation: During processing of an EVENTS POST macro, the
system found an error.
Register 15 contains a hexadecimal reason code that explains the
400
error:
Explanation: Execute channel program (EXCP) processing found
Code Explanation
an error while processing an I/O request. The address for the data
control block (DCB) in the data extent block (DEB) is not the same 00 The system found an incorrect EVENTS table address in
as the DCB address in the caller's input/output block (IOB). This situ- the low-order bytes of the extended format event control
ation can occur if the data set is not open or if the control blocks are block (ECB) that was specified.
prematurely freed or overlaid. 04 The waiting request block (RB) is not enabled for inter-
Source: Execute channel program (EXCP) rupts.
System Action: The system abnormally ends the task and may 08 For a WAIT or POST in a problem program protection
issue an SVC dump. key, the ECB address is incorrect.
Programmer Response: Verify that the data set was opened and System Action: The system abnormally ends the program that
that the control blocks were handled correctly in the problem issued the EVENTS macro.
program. Run the job again. Source: Task management
If the system wrote a dump, look at field TCBEXCPD at offset X'C0' Programmer Response: Correct the error. Run the job again.
in the task control block (TCB) for the current task. The TCBEXCPD
points to the EXCP debugging area (XDBA). The XDBA contains System Programmer Response: If the error recurs and the
diagnostic data associated with the EXCP processor. program is not in error, look at the messages in the job log for more
SCC-134 OS/390 V2R8.0 MVS System Codes
406 40D
information. Search problem reporting data bases for a fix for the Code Explanation
problem. If no fix exists, contact the IBM Support Center. Provide the
00 At the time of the recursive abends, RTM had estab-
program listing and the assembly listing associated with the job.
lished only critical error recursion processing. Therefore,
RTM could determine only that the error was not due to
406 a problem identified by the other reason codes.
Explanation: The error occurred during processing of a LINK(X), 04 RTM2 detected a critical error in RTM2 processing.
ATTACH(X), or XCTL(X) macro.
08 RTM experienced another error while processing a
The requested program is only loadable. The program was produced recursive error. RTM2 was unable to obtain the RTM2
by a linkage editor processing for which the EXEC statement con- work area (RTM2WA) associated with the original error.
tained OL in the PARM parameter field.
0C RTM2 could not obtain the previous RTM2WA because
Source: Contents supervision (CSV) the pointer to it was not valid.
System Action: The task is ended unless ERRET is specified on 10 No storage was available in either the local system
the macro instruction. The system issues message CSV009I and queue area (LSQA) or the extended local system queue
issues an ABEND dump. area (ELSQA) for the RTM2WA.
Programmer Response: Rewrite the problem program so that it 14 RTM2 detected that an RTM request to get or free
specifies only loading, but not processing, of the only loadable virtual storage ended abnormally.
program. Then recompile and run the job step again.
18 RTM was entered recursively after it had completed end-
System Programmer Response: If the error recurs and the of-task processing.
program is not in error, see the system programmer response for at
1C RTM2 was entered recursively. RTM2 could not find the
the messages in the job log.
request block (RB) for the previously abended routine.
If the problem persists, search problem reporting data bases for a fix
20 RTM2 was entered recursively to process an
for the problem. If no fix exists, contact the IBM Support Center.
RTM-initiated abend of a daughter task. RTM2 could not
Provide the ABEND dump and the source program listing for the job.
find the error RB for the previously abended mother
task.
40A
24 RTM2 tried to enter an exit, but found no exit flag on to
Explanation: An error occurred when the system tried to process indicate which exit to take.
an R form of the FREEMAIN macro. A reason code in the
SDWACRC field of the system diagnostic work area (SDWA) 28 RTM2 experienced an unrecoverable recursive error
explains the error: while ending a daughter task of the current task.
Code Explanation 30 RTM2 has been recursively entered for multiple DOD
abends from a subtask.
04 The caller tried to FREEMAIN a subpool that cannot be
freed. 34 RTM2 encountered a recursive abend due to a problem
with the current Task's Linkage Stack.
Only subpools defined as eligible for subpool
FREEMAIN may be freed as an entire subpool. All other Source: Recovery termination manager (RTM)
subpool storage areas must be freed by individual System Action: RTM ends the address space. The system issues
requests explicitly describing the area. message IEF402I. The system writes an SVC dump. Critical prob-
08 A problem program tried to free subpool zero. The lems in the address space can prevent the SVC dump from com-
control program releases subpool zero when a job step pleting successfully. Even if successful, message IEA911E might not
ends. be issued to indicate the dump is complete.
Source: Virtual storage manager (VSM) Operator Response: Obtain the SVC dump. The dump has the
title:
System Action: The system issues message IEA705I. The system
ABEND=4ðD,RC=xx,COMPON=RTM2,COMPID=SCRTM,
abnormally ends the current task.
ISSUER=IEAVTRT2, MEMTERM - UNRECOVERABLE ABEND FAILURE
Programmer Response: If you intended the FREEMAIN macro to
Note: Prior to OS/390 the COMPID is SC1CM.
release subpool zero, remove it from the program. If you did not
intend the FREEMAIN macro to release subpool zero, check for System Programmer Response: Do the following:
program errors that incorrectly modify the FREEMAIN macro expan- 1. Obtain the reason code from message IEF402I, register 15, or
sion. After making corrections, run the job step again. the SVC dump title.
2. For reason code X'10', continue diagnosis with virtual storage
40D
manager (VSM) to determine why there is not enough ELSQA
Explanation: When the recovery termination manager (RTM) was available. If the problem cannot be determined, search problem
ending a task, recursive errors occurred. RTM ends the address reporting data bases for a fix for the problem. If no fix exists,
space. This abend code is in the ASCBMCC field in the address contact the component group for VSM at the IBM Support
space control block (ASCB) for the ended address space and in Center. Provide the problem data collected in previous steps.
message IEF402I.
3. For a reason code other than X'10', a critical problem occurred
A hexadecimal reason code in register 15, in message IEF402I, and while RTM was processing an abend. Search problem reporting
in the SVC dump title explains the error: data bases for a fix for the problem. Include in the search
argument:
Program identifier: PIDS/5752SCRTM
Abend code: AB/S040D
System Completion Codes SCC-135
413 422
Abend reason code: PRCS/xx The parts of the reason code are:
If no fix exists, contact the IBM Support Center. Provide the xxxx The first halfword will be left to the component to set.
dump and any messages about the problem. Some components use these two bytes for internal identifi-
cation.
413 yy The 3rd byte will contain a component identifier. This will
Explanation: The error occurred during processing of an OPEN allow the 422 abend to be shared by multiple products and
macro instruction for a data set on magnetic tape or on a direct components. The following yy values indicate which com-
access device. This system completion code is accompanied by ponent or product generated the abend:
message IEC145I. Refer to the explanation of message IEC145I for zz The last byte is used by the component to create unique
complete information about the task that was ended and for an reason codes.
explanation of the return code (rc in the message text) in register 15.
A reason code in register 15 describes the error:
Source: DFSMSdfp
Code Explanation
Programmer Response: Respond as indicated for message
01xx Where xx is between the values of X'01' and X'7F'
IEC145I.
and represents the signal that caused the task to end.
System Programmer Response: If the error recurs and the An error occurred in an application program that uses
program is not in error, look at the messages in the job log for more OS/390 UNIX System Services.
information. Search problem reporting data bases for a fix for the
0109 The ending address space is the target of a signal. A
problem. If no fix exists, contact the IBM Support Center. Provide the
signal is program-generated and causes the job step
JCL and the program listing for the job.
task in the target user process to be ended with an
abend that cannot be retried.
414
0181 This abend is the result of the BPX1EXI (_exit) service
Explanation: The error occurred during processing of a CLOSE being issued in a process with multiple threads. The
macro instruction for a data set on a direct access device. This initial pthread_create task (IPT), if not already exited, is
system completion code is accompanied by message IEC212I. Refer abended with this reason, if the thread calling BPX1EXI
to the explanation of message IEC212I for complete information is created by pthread create.
about the task that was ended and for an explanation of the return
code (rc in the message text) in register 15. 0182 This abend is the result of the BPX1EXC (exec) or
BPX1EXM (execMVS) service being issued in a process
Source: DFSMSdfp with multiple threads. All dubbed threads in the process
Programmer Response: Respond as indicated for message are terminated with the abend.
IEC212I. 0183 BPXPRMPC was requested to terminate and clean up a
System Programmer Response: If the error recurs and the process. This required the Assembler termination macro
program is not in error, look at the messages in the job log for more CALLRTM of the initial pthread task.
information. Search problem reporting data bases for a fix for the 0184 The task is being ended because it is in a wait state
problem. If no fix exists, contact the IBM Support Center. Provide the controlled by the kernel address space, which is being
JCL and the program listing for the job. ended. To prevent leaving the task in a never-ending
wait, the task is abended. If a recovery routine exists in
417 the task, the routine can retry for this abend.
Explanation: The error occurred during processing of a BSAM 0185 A system error occurred during thread creation. The
CLOSE macro instruction with a TYPE=T operand for a data set on process was terminated.
a direct access device. This system completion code is accompanied 0186 A system error occurred during the processing of a local
by message IEC221I. Refer to the explanation of message IEC221I process exec. The jobstep is terminated.
for complete information about the task that was ended and for an
explanation of the return code (rc in the message text) in register 15. 0187 A system error occurred during fork processing. Fork is
in the APPC Receive and Wait window trying to create
Source: DFSMSdfp the child address space. Fork maybe hung waiting for
Programmer Response: Respond as indicated for message ASCH initiators.
IEC221I. 0189 The kernel has, at the request of the user, terminated a
System Programmer Response: If the error recurs and the thread that was in a ENQ wait.
program is not in error, look at the messages in the job log for more 018A A system error occurred creating the child process
information. Search problem reporting data bases for a fix for the during fork processing. The child process address
problem. If no fix exists, contact the IBM Support Center. Provide the space is terminated.
JCL and the program listing for the job.
018B A system error occurred during server_init processing for
a server manager address space. The calling task is ter-
422
minated.
Explanation: This abend is a general use abend code. It provides
01A0 This abend is the result of the kernel terminating a
an abend that will be treated similarly to a 222 abend generated by a
thread. The thread and its associated task are termi-
CANCEL. This abend will not be delivered to the target task if the
nated.
task is already in recovery processing.
Source: OS/390 UNIX System Services (BPX)
This abend may be retryable or nonretryable depending on the
reason code. System Action: The unit of work is ended with a nonretryable
error.
The 422 abend reason codes are in the format: xxxxyyzz
SCC-136 OS/390 V2R8.0 MVS System Codes
42A 433
Programmer Response: Programmer Response: Change the ATTACH macro to specify
the correct ECB address and ensure that the specification was not
Code Response
incorrectly modified by the problem program. Correct the error. Run
01xx The unit of work has terminated for a signal that was the job again.
either sent by the user or generated by the system.
System Programmer Response: If the error recurs and the
Determining the reason for the signal generally requires
program is not in error, look at the messages in the job log for more
an understanding of when signals are generated by the
information. Search problem reporting data bases for a fix for the
system. For a list of signals, refer to OS/390 UNIX
problem. If no fix exists, contact the IBM Support Center. Provide the
System Services Programming: Assembler Callable Ser-
program listing for the job.
vices Reference.
0181 No action is required by the user.
42D
0182 No action is required by the user.
Explanation: While an overlay program was running, an error
0183 No action is required by the user. occurred in the processing of a SEGLD macro.
0184 The task was in a wait at the time the kernel terminated. Note: Overlay programs run only in 24-bit addressing mode, not in
This is not an error. 31-bit addressing mode.
0185 Retry the operation. If the error persists, report the error Source: Overlay supervisor
to the IBM Support Center.
System Action: The system abnormally ends the program that
0186 No action is required by the user. requested the overlay. The system writes an ABEND dump, if a
0187 Review the APPC/ASCH setup relating to OMVS. dump DD statement is provided.
0189 No action is required by the user. Programmer Response: Obtain the address in register 12 at the
time of the error. Add X'14' to the address to find the address of the
018A No action is required by the user. event completion block (ECB) that contains the subtask completion
018B No action is required by the user. code.
01A0 No action is required by the user. Look for errors in the program. Correct the errors; then assemble,
link edit, and run the program again.
Rerun the job and use a debugger if necessary to determine why the
signal has occurred.
430
A reason code in register 15 describes the error:
Explanation: The error occurred during processing of a DEQ
Code Explanation macro instruction during the processing of global resource serializa-
xxxx0200 xxxx is the identifier of the JES2 processor control tion.
element (PCEID) currently active. A value of X'02' in The control program found that the parameter list created from the
the 3rd byte indicates the JES2 component. When macro instruction was incorrect.
xxxx=0003, this abend is the result of a job/TSU/STC
being canceled via an $Cjob or $Cjob,D command while Source: Global resource serialization
it is awaiting for conversion or active in conversion. System Action: The system writes an ABEND dump.
Source: JES2 Programmer Response: Correct the DEQ macro instruction spec-
System Action: The job/TSU/STC is ended with a nonretryable ification or the program errors that incorrectly modified the parameter
error. list. Recompile and run the job step again.
Programmer Response: System Programmer Response: If the problem persists, search
problem reporting data bases for a fix for the problem. If no fix
Code Response exists, contact the IBM Support Center. Provide the ABEND dump.
00030200 Determine why the job is being canceled. If you require
a dump, have the operator resubmit the job, and then 433
cancel it with the DUMP operand.
Explanation: An error occurred while DAE was processing a
symptom record.
42A
Register 15 contains a hexadecimal reason code that explains the
Explanation: During processing of an ATTACH macro, the system error:
found that the ECB parameter specified an incorrect address for the
event control block (ECB) to be posted when the subtask abnormally Code Explanation
ends. 00000008 There is no more storage available for keeping DAE
The address was incorrect for the following reasons: symptom strings in storage, and the existing storage
cannot be reused.
It was not on a fullword boundary.
Source: Dump Analysis and Elimination (DAE)
The addressed virtual storage is not allocated, or its protection
key does not match the protection key of the issuer of the System Action: The system writes a logrec data set error record,
ATTACH. and attempts to take an SVC dump. DAE stops processing and
issues message ADY015I.
Source: Task management
System Programmer Response: For reason code X'00000008',
System Action: The system abnormally ends the program that DAE processing may be restarted using the MVS SET DAE
issued the ATTACH macro. command.
System Completion Codes SCC-137
435 444
435 43E
Explanation: SVC 53, which obtains and releases exclusive control Explanation: The event control block (ECB) address specified with
of a resource associated with a BDAM data set found that: the ECB parameter on the ATTACH macro instruction that created a
task was not valid when the subtask abnormally ended.
The DEB pointed to by the input DCB (DCBDEBAD) was not on
any DEB chain associated with the job step TCB, or did not Source: Task management
point back to that DCB, or was not for a BDAM data set.
System Action: The ECB is not posted. The system abnormally
The IOB has been altered by other than a system routine. ends the originating task of the caller.
Source: DFSMSdfp Programmer Response: Determine if the area containing the ECB
was freed before the subtask completed processing. Correct the
Programmer Response: Make sure that the input DCB address is
error. Run the job again.
correct and that the DCBDEBAD field of the input DCB has not been
overlaid. The ECB was specified in the ATTACH macro, and the system
checked it for validity while attaching the subtask. The ECB could be
System Programmer Response: If the error recurs and the
incorrect when the subtask is detached or at end of task through a
program is not in error, search problem reporting data bases for a fix
request of the storage containing the ECB.
for the problem. If no fix exists, contact the IBM Support Center.
System Programmer Response: If the error recurs and the
437 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
Explanation: The error occurred at an end-of-volume. This system problem. If no fix exists, contact the IBM Support Center. Provide the
completion code is accompanied by message IEC025I. Refer to the source program listing and the assembly listing associated with the
explanation of message IEC025I for complete information about the job.
task that was ended and for an explanation of the return code (rc in
the message text) in register 15.
43F
Source: DFSMSdfp
Explanation: An error has been detected during checkpoint restart
Programmer Response: Respond as indicated for message processing. This completion code is accompanied by message
IEC025I. IHJxxxI with the appropriate reason code.
System Programmer Response: If the error recurs and the Source: DFSMSdfp
program is not in error, look at the messages in the job log for more
System Action: The system produces a dump, and retries to the
information. Search problem reporting data bases for a fix for the
address in register 14.
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job. Programmer Response: Respond as indicated in the accompa-
nying message.
438
444
Explanation: Global resource serialization encountered an error
during processing of an ENQ macro instruction during the processing Explanation: The error occurred during the processing of
of global resource serialization. SYNADAF, where it was determined that the DECB address was
incorrect.
The control program found that the parameter list created from the
macro instruction was incorrect. Source: DFSMSdfp
Source: Global resource serialization Programmer Response: Register 15 contains the DECB address
in error:
System Action: The system issues an ABEND dump.
For BDAM, BPAM, and BSAM, the DECB address should be
Programmer Response: Correct the macro instruction or the
passed to SYNADAF as the PARM2 operand on the macro
program errors that incorrectly modified the parameter list. Recom-
instruction. For these access methods, the DECB address was
pile and run the job step again.
in register 0 on entry to the user's SYNAD routine.
If the problem persists, do the following:
For BISAM, the IOBECBPT field of the IOB in error should
1. Obtain the address of the DEQ parameter list from register 1 in contain the DECB address. Make sure that the PARM2 operand
the UNIQUE-3 column of the SVC 30 or SVC 38 entry in the on the SYNADAF macro instruction (the address of the first
system trace. sense byte within the IOB) is correctly specified, and that the
2. Check the parameter list against the SVC 30 or 38 mapping. IOBECBPT has not been overlaid.
When analyzing the parameter list, remember that the unit Correct the error and rerun the job step.
control block (UCB) pointer, if present, is the address of a field
System Programmer Response: If the error recurs and the
that, in turn, contains the address of the UCB.
program is not in error, look at the messages in the job log for more
If the parameter list contains incorrect data, continue diagnosis information. Search problem reporting data bases for a fix for the
in the program that issued the macro. problem. If no fix exists, contact the IBM Support Center. Provide the
System Programmer Response: If the problem persists, search JCL and the program listing for the job.
problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the ABEND dump.
SCC-138 OS/390 V2R8.0 MVS System Codes
451 46D
451 46D
Explanation: The error occurred during the processing of SETPRT. Explanation: A program issued the ESPIE macro incorrectly:
Either the DCB whose address was passed in the SETPRT param-
A hexadecimal reason code in register 15 explains the error:
eter list is incorrect, the DEB address located through the DCB was
incorrect, the DCB EXIT LIST address located through the DEB was Code Explanation
incorrect, or the IOBs located through the DCB are incorrect. 04 The ESPIE macro specified an option other than SET,
This system completion code is accompanied by message IEC918I. RESET, or TEST.
Refer to the explanation of message IEC918I for complete informa- 08 The ESPIE SET or ESPIE TEST macro passed an
tion about the task that was ended and for an explanation of the address pointing to a parameter list. The contents of the
return code in register 15. parameter list is not valid for one of the following
Source: DFSMSdfp reasons:
Programmer Response: The parameter list is not aligned on a fullword
boundary.
For return code 01, make sure that DCBEXLIST points to a valid
exit list in your region. The parameter list is in storage that was not
obtained by a GETMAIN macro.
For return code 02, make sure that the DCB fields DCBIOBAD
and DCBIOBA have not been overlaid since the DCB was The parameter list is in storage that is protected
opened. Make sure that the IOB or ICB link fields have not been from the issuer of the ESPIE macro.
overlaid. 0C The ESPIE SET macro passed a parameter list con-
For return code 03, make sure that the DCB field DCBDEBAD taining an exit routine address that is not valid for one of
has not been overlaid since the DCB was opened. the following reasons:
For return code 04, make sure that the SETPRT macro instruc- The high or low order bits of the address are not 0.
tion correctly specifies the address of an open DCB within your If the program issuing ESPIE is in 24-bit addressing
region. mode, the high order byte is not zero.
System Programmer Response: If the error recurs and the 10 The ESPIE RESET macro attempted to delete a SPIE or
program is not in error, look at the messages in the job log for more ESPIE that was created by some other program.
information. Search problem reporting data bases for a fix for the
14 The ESPIE RESET macro passed an incorrect TOKEN
problem. If no fix exists, contact the IBM Support Center. Provide the
parameter. TOKEN is incorrect for one of these reasons:
JCL and the program listing for the job.
The TOKEN itself is not valid.
453 The exit that the TOKEN represents has been
Explanation: A buffer queue error occurred while system manage- deleted.
ment facility (SMF) recording was writing to the SMF data sets; the 18 The program issuing an ESPIE macro is in a mode that
system determined that SMF recording should be ended. is not valid for one of the following reasons:
Source: System Management Facilities (SMF) The program is in supervisor state.
System Action: The system ends the SMF address space and The program that issued the ESPIE macro had a
releases the resources used by SMF. program status word (PSW) storage key that did not
Operator Response: Notify the system programmer. If SMF match the task control block (TCB) key.
recording is essential for the system, restart the SMF address space 1C The ESPIE macro passed a pointer to a SPIE program
using the SET SMF command as soon as the problem is corrected. interruption exit (PIE) control block. The PIE control
System Programmer Response: Check error messages and the block is not valid. The PIE control block had probably
SVC dump produced as a result of any previous abends. been erroneously freed by a FREEMAIN macro.
20 An unauthorized program issued a ESPIE macro to
45F establish an ESPIE exit for page faults.
Explanation: A SYSEVENT QUIESCE macro failed while a Source: Recovery termination manager (RTM)
SYSEVENT TRANSWAP or REQSWAP was pending. A retry was System Action: The system abnormally ends the task. The system
not possible. sends messages about the problem to the job log.
Source: System resources manager (SRM) Operator Response: If the system programmer asks for an SVC
System Action: The system abnormally ends the address space dump, set the following SLIP trap:
being swapped. The system writes messages and a logrec data set SLIP SET,COMP=46D,ACTION=SVCD,END
error record.
System Programmer Response: Search problem reporting data
System Programmer Response: This is probably a system error. bases for a fix for the problem. If no fix exists, contact the IBM
Resubmit the job. If the problem recurs, search problem reporting Support Center. Provide:
data bases for a fix for the problem. If no fix exists, contact the IBM
Messages from the job log
Support Center. Provide the logrec data set error record and the
The ABEND or SVC dump
SYSOUT output for the job.
The assembly listing for the job
The JCL for the job
The program listing for the job
System Completion Codes SCC-139
478 483
System Action: The system abnormally ends the SRB routine.
478
Programmer Response: If CANCEL command processing caused
Explanation: An error occurred when the system tried to process
the error, resubmit the job. If a task-to-SRB routine serialization or
an RC or RU form of the FREEMAIN macro or the STORAGE
abnormal TCB ending caused the problem, modify the application to
RELEASE macro. A reason code in the SDWACRC field of the
avoid the problem.
system diagnostic work area (SDWA) explains the error:
System Programmer Response: If the error recurs and the
Code Explanation
program is not in error, look at the messages in the job log for more
04 The caller tried to FREEMAIN or STORAGE RELEASE information. Search problem reporting data bases for a fix for the
a subpool that cannot be freed. problem. If no fix exists, contact the IBM Support Center. Provide the
Only subpools defined as eligible for subpool program listing and the assembly listing associated with the job.
FREEMAIN or STORAGE RELEASE may be freed as
an entire subpool. All other subpool storage areas must 47D
be freed by individual requests explicitly describing the Explanation: During processing of an EVENTS macro, the system
area. found that the address specified on the LAST parameter was incor-
08 A problem program tried to free subpool zero. The rect.
control program releases subpool zero when a job step LAST must specify an address between the first and last valid
ends. entries in the EVENTS table.
Source: Virtual storage manager (VSM) Source: Task management
System Action: The system issues message IEA705I. The system System Action: The system abnormally ends the program that
abnormally ends the current task. issued the EVENTS macro.
Programmer Response: If you intended the FREEMAIN or Programmer Response: Ensure that the LAST address is a valid
STORAGE RELEASE macro to release subpool zero, remove it from table entry that has not been previously purged from the EVENTS
the program. If you did not intend the FREEMAIN or STORAGE table. Correct the error. Run the job again.
RELEASE macro to release subpool zero, check for program errors
that incorrectly modify the FREEMAIN or STORAGE RELEASE System Programmer Response: If the error recurs and the
macro expansion. After making corrections, run the job step again. 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
47A
program listing and the assembly listing associated with the job.
Explanation: During processing of an EVENTS macro, the system
found an incorrect number of entries specified on the on the 482
ENTRIES parameter. The number of entries must be 1 through
32,767. Explanation: While RACF was processing a RACHECK request,
the RACF manager returned a return code that was not valid.
Source: Task management
Source: Resource Access Control Facility (RACF)
System Action: The system abnormally ends the caller of the
EVENTS macro. System Action: The system ends the task.
Programmer Response: Ensure that the number of entries speci- System Programmer Response: Register 15 contains the
fied on the ENTRIES parameter is 1 through 32,767. hexadecimal return code from the RACF manager.. Message
ICH409I, if issued, contains the reason code from the RACF
System Programmer Response: If the error recurs and the manager. For an explanation of RACF manager return and reason
program is not in error, look at the messages in the job log for more codes, see OS/390 Security Server (RACF) Messages and Codes.
information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the Using IPCS, format the dump taken for this abend. For an explana-
program listing and the assembly listing associated with the job. tion of the dump title, see OS/390 Security Server (RACF) Diagnosis
Guide.
47B
483
Explanation: An error occurred during PURGEDQ processing. The
SDWACRC field of the system diagnostic work area (SDWA) con- Explanation: While RACF was processing a RACINIT request, the
tains a hexadecimal reason code that explains the error. RACF manager returned an invalid return code.
Code Explanation System Action: The system terminates the task.
00 During processing of a PURGEDQ macro for the current Programmer Response: Register 15 contains the return code from
primary address space, the system found a suspended the RACF manager. Message ICH409I, if issued, contains the RACF
SRB meeting the purge parameters. The system manager reason code. For an explanation of RACF manager return
abended the SRB routine to ensure that all SRB routines and reason codes, see OS/390 Security Server (RACF) Messages
affected by PURGEDQ had run to completion. and Codes.
04 An internal error occurred during PURGEDQ processing. System Programmer Response: If a dump was taken for this
Contact the IBM Support Center. abend, use IPCS to format the dump. For an explanation of the
dump title, see the dump title beginning ICHRST00-RACF SVCS in
Source: Task management OS/390 Security Server (RACF) Diagnosis Guide.
SCC-140 OS/390 V2R8.0 MVS System Codes
485 4FC
10 INCORRECT SUBPOOL: The subpool for the area to
485
free is not the subpool in which the area is allocated.
Explanation: While RACF was processing a RACROUTE
14 INVALID OVERLAP: Part of the area to free equals part
REQUEST=DEFINE request, the RACF manager returned an invalid
of the area allocated, but the match is not correct for
return code.
either a full or partial FREEMAIN.
System Action: The system terminates the task.
18 NOT FOUND: The area to free does not have a corre-
Programmer Response: Register 15 contains the return code from sponding GETMAIN entry in the tracking table, and the
the RACF manager. See OS/390 Security Server (RACF) Messages caller did not specify that it should not have.
and Codes for an explanation for RACF-manager return codes.
1C FOUND: The area to free has a corresponding
System Programmer Response: If a dump was taken for this GETMAIN entry in the tracking table, and the caller
abend, use IPCS to format the dump. For an explanation of the specified that it should not have.
dump title, see the dump title beginning ICHRST00-RACF SVCS in
20 NOT FREED: There is a temporary area still allocated at
OS/390 Security Server (RACF) Diagnosis Guide.
the end of processing.
A0 A RACF module issued a get space request. However,
4C5
register 1 is not equal to zero and does not point to a
Explanation: This abend is issued by the TCP/IP product. Please buffer previously created by the program.
see the TCP/IP documentation for more information.
A4 A RACF module issued a get space request. However,
the subpool in register 0 is not the subpool in which the
4C6 previously created buffer is allocated.
Explanation: An error occurred during Resource Access Control A8 A RACF module issued a free space request. However,
Facility (RACF) processing for OS/390 UNIX System Services. register 1 is equal to zero.
Code Explanation AC A RACF module issued a free space request. However,
00000004 A service call to a RACF module did not complete. No register 1 does not point to the buffer previously created
accessor environment element (ACEE) was available to by the program.
describe the user. System Programmer Response: Using IPCS, format the dump
00000008 A service call to a RACF module did not complete. No taken for this abend. For an explanation of the dump title, see
accessor environment element extension (ACEX) was OS/390 Security Server (RACF) Diagnosis Guide. Look at the mes-
available to describe the user. sages in the job log for the name of the module calling RACF. For
modules supplied by IBM, search problem reporting databases for a
0000000C A service call to a RACF module did not complete. No
fix for the problem. If no fix exists, contact the IBM support center.
user security packet (USP) was available to describe the
user.
4FB
Source: Resource Access Control Facility (RACF)
Explanation: One of the following errors occurred:
Programmer Response: The RACF input/output parameter list
IRRPCOMP contains a SAF return code, RACF return code, and JES3 could not obtain sufficient storage for a SSISERV macro
RACF reason code that describes an internal RACF error. request.
System Action: The system abnormally ends the task. JES3 could not obtain sufficient storage for user address space
buffers.
System Programmer Response: Run the job again, or have the
user log on again while RACF is active. If the abend occurs again, JES3 detected an error while processing the record allocation
see OS/390 Security Server (RACF) Diagnosis Guide for information block (RAB) refresh element (RRE) for additional track groups.
on diagnosing abends and reporting abend problems to IBM. JES3 attempted to obtain storage in subpool 0, but failed.
The specified REGION size value was too small.
4C7
Source: JES3
Explanation: While RACF was processing a non-SVC request, an
error occurred in the RACF storage manager. System Action: The system ends the user address space.
System Action: The system terminates the task. System Programmer Response: Rerun the job with a SYSABEND
DD statement. The problem may not recur. If it does, notify the IBM
Source: Resource Access Control Facility (RACF) Support Center.
Programmer Response: Register 15 contains a hexadecimal
reason code. (Message ICH409I, if issued, also contains this reason 4FC
code.)
Explanation: The system detected an error in the processing fol-
Code Meaning lowing a program check interrupt. In an attempt to recover, super-
04 BAD LENGTH: The length of the area to get or free is visor control abnormally ended the task that experienced the
not greater than zero. program check.
08 BAD ALIGNMENT: The pointer to the area to free is not Source: Supervisor control
on a doubleword boundary. System Action: The system abnormally ends the program that
0C DUPLICATE FREEMAIN: The area to free has already experienced the program check. The system writes a logrec data set
been freed. error record.
Operator Response: If the system programmer asks for an SVC
dump, set the following SLIP trap:
System Completion Codes SCC-141
500 506
SLIP SET,COMP=4FC,ACTION=SVCD,END
502
Programmer Response: Resubmit the job. If the problem recurs,
Explanation: During processing of a POST macro, the system
contact the system programmer.
found that the EVENTS table specified in the event control block
System Programmer Response: Do the following: (ECB) had no entries available for the posted ECB address.
Find the original abend causing the problem in the system diag- Source: Task management
nostic work area (SDWA) in the logrec data set error record.
System Action: The system abnormally ends the program that
Search problem reporting data bases for a fix for the problem. If issued the POST macro.
no fix exists, ask the operator to set a SLIP trap to obtain an
Programmer Response: Ensure that the EVENTS table is large
SVC dump. Contact the IBM Support Center. Provide the SVC
enough to contain entries for all ECBs that can be posted to it.
dump and the logrec data set error record.
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 the job log for more
500 information. Search problem reporting data bases for a fix for the
Explanation: During processing of an I/O request, execute channel problem. If no fix exists, contact the IBM Support Center. Provide the
program (EXCP) processing encountered an error while validating a program listing and the assembly listing associated with the job.
control block. Each X'500' abend code has a reason code that
explains the error: 504
Code Explanation Explanation: An error occurred when the system tried to process
1 The IOBM field of an Indexed Sequential Access Method an EC, EU, LC, LU, VC, or VU form of the GETMAIN macro. A
(ISAM) input/output block (IOB) specified an extent of zero. reason code in the SDWACRC field of the system diagnostic work
area (SDWA) explains the error:
2 A data extent block (DEB) points to a unit control block
(UCB) that is not valid. The third byte of the UCB did not Code Explanation
contain X'FF', as required. 04 Of the following, at least one overlapped the other:
3 The IOBEID field of the Input/output block extension length list, address list, or parameter list. For example,
(IOBE) control block does not contain the characters the length list overlapped the address list.
‘IOBE’, which is required. Source: Virtual storage manager (VSM)
4 The version field of the IOBE is not compatible with the System Action: The system issues message IEA705I. The system
IOBEVRSC version label. The version field must equal the abnormally ends the current task.
IOBEVRSC version label.
Programmer Response: Check for program errors that incorrectly
5 The IEDBID field of the I/O error data block (IEDB) control modify the macro expansion. Correct them. Run the job step again.
block does not contain the characters ‘IEDB’, which is
required.
505
6 The version field of the IEDB is not compatible with the
Explanation: An error occurred when the system tried to process
IEDBVRSC version label. The version field must equal the
an EC, EU, LC, LU, VC, or VU form of the FREEMAIN macro. A
IEDBVRSC version label.
reason code in the SDWACRC field of the system diagnostic work
Source: Execute channel program (EXCP) area (SDWA) explains the error:
System Action: The system abnormally ends the current task and Code Explanation
issues a SNAP dump.
04 Of the following, at least one overlapped the other:
Programmer Response: Correct the problem that the reason code length list, address list, or parameter list. For example,
indicates. Ensure also that the problem program correctly built or the length list overlapped the address list.
modified the control blocks. If the program is correct, the problem is
Source: Virtual storage manager (VSM)
a system problem. Run the job again, requesting an ABEND dump.
Notify the system programmer. System Action: The system issues message IEA705I. The system
abnormally ends the current task.
System Programmer Response: In the dump, look at field
TCBEXCPD at offset X'C0' in the task control block (TCB) for the Programmer Response: Check for program errors that incorrectly
current task. TCBEXCPD points to the EXCP debugging area modify the macro expansion. Correct them. Run the job step again.
(XDBA). The XDBA contains diagnostic data associated with the
EXCP processor. 506
If the error recurs and the program is not in error, look at the mes- Explanation: The error occurred during processing of a LINK(X),
sages in the job log for more information. Search problem reporting LOAD, ATTACH(X), or XCTL(X) macro in an overlay program.
data bases for a fix for the problem. If no fix exists, contact the IBM
Note: An overlay program can run only in 24-bit addressing mode,
Support Center. Provide the JCL and the SNAP dump.
not in 31-bit addressing mode.
If the requested program had been loaded, not enough virtual
storage would have remained for the overlay supervisor.
Source: Contents supervision (CSV)
System Action: The system issues an ABEND dump. The task
ends abnormally.
SCC-142 OS/390 V2R8.0 MVS System Codes
50D 530
Programmer Response: Reduce the size of the entire program or
522
of the overlay segment. If this is not possible, change the program
from an overlay program to a dynamically loaded program. Then Explanation: All of the tasks in a job step were in an SVC wait
recompile and run the job step again. state for the time specified in the JWT parameter in the SMFPRMxx
parmlib member.
System Programmer Response: Have the operator enter a
START GTF command specifying tape output, MODE=EXT and The event control block (ECB) specified in the wait request was
TIME=YES. Have the operator reply TRACE=SYS in response to never posted. This could be the result of waiting on the wrong ECB
message AHL100A. or not posting the correct ECB.
Format the output with the IPCS GTFDATA subcommand. Source: System Management Facilities (SMF)
System Programmer Response: If the error recurs and the System Programmer Response: Correct any errors and execute
program is not in error, see the system program response for the the job step again. If no errors are found and the wait is expected for
messages in the job log. that particular job step, specify TIME=NOLIMIT in the EXEC state-
ment to bypass all job step timing.
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 and the source program listing for the job. 52A
Explanation: During processing of an ATTACH macro, the system
50D found an error in the subtask ABEND intercept (STAI) or the
extended STAI (ESTAI) routine.
Explanation: Either the program:
Register 15 contains a hexadecimal reason code that explains the
Tried to use the OPEN, OPEN-J, CLOSE, CLOSE-T, EOV, or
error:
FEOV function while holding exclusive control of the TIOT (task
input/output table) resource; or Code Explanation
Issued the OPEN, OPEN-J, CLOSE, or CLOSE-T macro with 00 There is not enough storage available to create a new
inconsistent mode specifications between the LIST and the ESTAI specify task asynchronous exit (STAE) control
EXECUTE forms of the macro. block (SCB) or to copy existing STAI or ESTAI SCBs to
Register 15 contains a code that identifies the function that issued the new task.
the abend: 04 The issuer of ATTACH is processing with AMODE 31
Code Function and requested STAI. STAI is not supported for AMODE
31 callers.
00 OPEN
Source: Task management
04 OPEN-J
System Action: The system abnormally ends the program that
08 CLOSE
issued the ATTACH macro.
0C CLOSE-T
Programmer Response: Reason code 00 indicates a probable
10 EOV system error. Notify the system programmer.
14 FEOV For reason code 04, identify the program that issued the ATTACH
18 EOV macro. If an installation-provided program issued the ATTACH,
change the macro parameter from STAI to ESTAI. If an
1C OPEN or CLOSE IBM-provided program issued the ATTACH, notify the system pro-
20 OPEN or CLOSE grammer.
Source: DFSMSdfp System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
System Action: The task is ended.
Support Center.
Programmer Response: Correct the program so that it releases
control of the TIOT resource before one of the above functions is
530
requested. Recompile the program and run the job step again.
Explanation: Global resource serialization encountered an error
during processing of a DEQ macro instruction.
513
The DEQ macro instruction was issued in an asynchronous exit
Explanation: The error occurred during processing of an OPEN
routine for a resource. That resource was previously enqueued by
macro instruction for a data set on magnetic tape. This system com-
another routine in the same task. However, the task had not yet
pletion code is accompanied by message IEC146I. Refer to the
received control of the resource.
explanation of message IEC146I for complete information about the
task that was ended and for an explanation of the return code (rc in Source: Global resource serialization
the message text) in register 15. System Action: The system issues an ABEND dump.
Source: DFSMSdfp Programmer Response: Correct the program so that the DEQ
Programmer Response: Respond as indicated for message macro instruction is issued only after the task has control of the
IEC146I. resource. If possible, avoid issuing the DEQ macro instruction in the
exit routine. Recompile and run the job step again.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more System Programmer Response: If the problem persists, search
information. Search problem reporting data bases for a fix for the problem reporting data bases for a fix for the problem. If no fix
problem. If no fix exists, contact the IBM Support Center. Provide the exists, contact the IBM Support Center. Provide the ABEND dump.
JCL and the program listing for the job.
System Completion Codes SCC-143
535 544
535 53E
Explanation: SVC 53, which obtains and releases exclusive control Explanation: During end-of-task processing, the system found an
of a resource associated with a BDAM data set, issued a GETMAIN error before:
for storage to be used in its processing and found no storage was
The system could post an event control block (ECB) for the
available.
ending task
Source: DFSMSdfp
The system could schedule an end-of-task exit routine (ETXR)
Programmer Response: Rerun the job. If the problem continues,
The system could determine that the task had neither an ECB
storage may have to be freed by others before the exclusive control
nor an ETXR
function is used.
The task contains either:
System Programmer Response: If the error recurs and the
program is not in error, search problem reporting data bases for a fix An end-of-task ECB, if the ECB parameter was specified on the
for the problem. If no fix exists, contact the IBM Support Center. ATTACH macro that created the task
Provide the JCL, the SYSOUT output for the job, and all printed An ETXR if the ETXR parameter was specified on the ATTACH
output and output data sets related to the problem. macro
Source: Task management
538
System Action: The system abnormally ends the originating task
Explanation: The system determined that a requested ENQ or for the task in error.
RESERVE would have exceeded the limit on the number of concur-
rent ENQ/GQSCAN/RESERVE requests for all tasks in the address Programmer Response: Run the job again. If the error recurs,
space. notify the system programmer.
Source: Global resource serialization System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
System Action: The system ends the task that issued the ENQ or Support Center.
RESERVE. The system issues an ABEND dump.
Operator Response: Obtain an SVC dump if the system pro- 53F
grammer requests it.
Explanation: An error has been detected during checkpoint restart
System Programmer Response: Make sure that no tasks in the processing. This completion code is accompanied by message
job step issue repeated ENQ or RESERVE macro instructions for IHJxxxI with the appropriate reason code.
resources that are not required. Also, make sure that all GQSCAN
Source: DFSMSdfp
requests that return a TOKEN are either run to completion or are
terminated by a QUIT=YES option on a subsequent GQSCAN macro System Action: A dump is produced and an entry is written to the
instruction. logrec data set.
If the problem persists, set a SLIP trap for abend X'538' and rerun Programmer Response: Respond as indicated in the accompa-
the job step. When the trap matches, instruct the operator to obtain nying message.
an SVC dump that includes the following:
The global resource serialization private area. 544
The DAT-on nucleus, to get the global resource serialization Explanation: The error occurred during the processing of
vector table (GVT) in order to see the constants GVTCREQ and SYNADAF, where it was determined that the IOB address was incor-
GVTCREQA. rect.
The system queue area (SQA), to get the address space control Source: DFSMSdfp
block (ASCB) for the failing program. System Action: Register 15 contains the IOB address in error:
If abend code X'538' is issued for an authorized caller, an SVC For BDAM, BPAM, and BSAM, SYNADAF obtained the IOB
dump may not be possible. address from the DECIOBPT field of the DECB; for these
Use the ASCBLQEL and ASCBGQEL queue anchors to locate all access methods, the DECB address was passed to SYNADAF
currently outstanding global resource serialization requests for the as the PARM2 operand on the macro instruction, and was con-
failing address space. tained in register 0 on entry to the user's SYNAD routine. Verify
that the PARM2 operand on the SYNADAF macro instruction
If the default value for GVTCREQ or GVTCREQA is too low for the
was correctly specified and that the DECIOBPT field has not
program terminating with the 538 abend, analyze the program to
been overlaid.
determine an acceptable value for GVTCREQ. Refer to OS/390 MVS
Programming: Authorized Assembler Services Guide for information For QSAM, BISAM, and QISAM, SYNADAF received a pointer
on changing the values for GVTCREQ or GVTCREQA. to the IOB as the PARM2 operand on the macro instruction. The
address passed to SYNADAF should have been the address
If the problem persists, search problem reporting data bases for a fix
contained in register 0 on entry to the user's SYNAD routine.
for the problem. If no fix exists, contact the IBM Support Center.
Verify that the PARM2 operand on the SYNADAF macro instruc-
Provide the ABEND or SVC dump.
tion was correctly coded.
For the EXCP access method, verify that the PARM1 operand of
the SYNADAF macro instruction specified the correct IOB
address.
Programmer Response: Correct the error and rerun the job step.
SCC-144 OS/390 V2R8.0 MVS System Codes
553 57D
System Programmer Response: If the error recurs and the
56D
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 Explanation: The system issued SVC 109 with routing code 11 in
problem. If no fix exists, contact the IBM Support Center. Provide the register 15 (the Sort SVC). One of the following error conditions
JCL and the program listing for the job. exists:
A task other than Sort issued SVC 109 with routing code 11.
553 Only Sort is authorized to issue it.
Explanation: System management facilities (SMF) detected that The task that issued the SVC passed a record that was not in
the SMF timer queue element (STQE) chain was in error. the task's authorized area.
A hexadecimal reason code in register 15 explains the error: The task passed a record that contained one or more incorrect
Code Explanation fields.
| 04 The forward pointer of an STQE contains zeroes. The Source: Time Sharing Option Extensions (TSO/E)
| system produces an SVC dump, and SMF repairs the System Action: The task ends. The system issued an SVC dump
| STQE chain. and a logrec data set error record.
| Note: Repairing the STQE chain results in the loss of Programmer Response: If the problem occurred because a task
| some STQEs. Therefore, some tasks no longer other than Sort issued SVC 109 with routing code 11, correct the
| provide SMF interval recording. task.
08 The STQE chain points to an element that is not an If the problem occurred while Sort was executing, contact the system
STQE. programmer.
| Note: Repairing the STQE chain results in the loss of System Programmer Response: If the problem recurs and if the
| some STQEs. Therefore, some tasks no longer program is not in error, search problem reporting data bases for a fix
| provide SMF interval recording. for the problem. If no fix exists, contact the IBM Support Center.
| 0C The backward pointer of an STQE contains zeroes. The Provide the SVC dump and the logrec data set error record.
| system produces an SVC dump, and SMF repairs the
| STQE chain. 56F
| Note: Repairing the STQE chain results in the loss of Explanation: The error occurred during end-of-job processing for a
| some STQEs. Therefore, some tasks no longer JES2 job that was being processed by an execution batch monitor.
| provide SMF interval recording. The execution batch monitor pseudo job select procedure found that
another task was holding or waiting for a lock on the SJB (sub-
Source: System management facilities (SMF)
system job block).
System Action: The SMF timer program ends, and the system
Source: JES2
produces an SVC dump.
System Action: The job terminates.
Operator Response: Notify the system programmer. You can re-
establish SMF interval recording for a specific task by restarting that Programmer Response: Notify the system programmer or installa-
task. Consider restarting tasks for which SMF interval recording is tion manager of the problem.
required. However, if you must re-establish SMF interval recording, System Programmer Response: Make sure the failing job step
but you can't determine which tasks to restart, reIPL the system. includes a SYSABEND DD statement.
System Programmer Response: Check error messages and the If the problem recurs and if the program is not in error, search
SVC dump produced as a result of any previous abends. Check for problem reporting data bases for a fix for the problem. If no fix
any previous abend code X'0C4' that might indicate a storage exists, contact the IBM Support Center.
overlay has occurred. If there is no previous abend code X'0C4',
search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. 57D
Explanation: During processing of an EVENTS macro, the system
55F found either:
Explanation: During processing of a cross memory POST macro An incorrect event control block (ECB) address
for a swap out complete (SYSEVENT 15), the system encountered The program issuing the EVENTS macro instruction is running
an error. The POST was to notify a SYSEVENT REQSWAP or under a protection key (8 through 15) that is different from the
TRANSWAP issuer that either the swap had to be turned around or protection key of the ECB
the swap is complete.
Source: Task management
Source: System resources manager (SRM)
System Action: The system abnormally ends the program that
System Action: The system abnormally ends the issuer of the issued the EVENTS macro.
cross memory POST. The system writes messages and a logrec
Programmer Response: Ensure that the ECB address specified is
data set error record.
a valid virtual storage address and that it was not incorrectly modi-
System Programmer Response: Determine if the POST macro fied. Also, ensure that the ECB is placed in storage belonging to the
passes a valid event control block (ECB) address. Resubmit the job. program issuing the EVENTS macro or the program running under
If the problem recurs, search problem reporting data bases for a fix protection key 0 through 7. Correct the error. Run the job again.
for the problem. If no fix exists, contact the IBM Support Center. System Programmer Response: If the error recurs and the
Provide the logrec data set error record and the SYSOUT output for program is not in error, look at the messages in the job log for more
the job. information. Search problem reporting data bases for a fix for the
System Completion Codes SCC-145
582 5C4
problem. If no fix exists, contact the IBM Support Center. Provide the indicated by the reason code. For assistance in gathering additional
program listing and the assembly listing associated with the job. information about the request that caused this abend (such as
obtaining a dump or identifying the caller of RACF), see OS/390
582 Security Server (RACF) Diagnosis Guide. If an IBM program issued
the REQUEST=DEFINE macro, see OS/390 Security Server (RACF)
Explanation: While processing a RACROUTE REQUEST=AUTH Diagnosis Guide for information on reporting abend problems to IBM.
request, RACF was unable to verify a user.
System Action: The system abnormally terminates the task. 5C4
Programmer Response: Register 15 contains a hexadecimal Explanation: A call for a resource recovery services (RRS) service
reason code. (Message ICH409I, if issued, also contains this return was issued in an incorrect environment. Register 15 contains a
code.) hexadecimal reason code.
Code Explanation Code Explanation
00 No accessor control environment (ACEE) was available xxxx000B RRS was unable to obtain a required storage area. The
to describe the user. storage area could be in CSA.
00010000 For a call to the Delete_UR_Interest service, the param-
Note: This is normal if a job started or a user logged eters are not in the primary address space.
on while RACF was inactive but has since been
00010001 For a call to the Delete_UR_Interest service, the param-
reactivated.
eters are not addressable.
04 Reserved.
00020000 For a call to the Express_UR_Interest service, the
Identify and correct the indicated error. parameters are not in the primary address space.
Problem Determination: Run the job again, or have the user log 00020001 For a call to the Express_UR_Interest service, the
on again while RACF is active. If the abend occurs again, see parameters are not addressable.
OS/390 Security Server (RACF) Diagnosis Guide for information on
00030000 For a call to the Begin_Restart service, the parameters
diagnosing abends and reporting abend problems to IBM.
are not in the primary address space.
585 00030001 For a call to the Begin_Restart service, the parameters
are not addressable.
Explanation: While processing a RACROUTE REQUEST=DEFINE
request, RACF encountered an error. 00040000 For a call to the End_Restart service, the parameters
are not in the primary address space.
System Action: The system terminates the task.
00040001 For a call to the End_Restart service, the parameters
Programmer Response: Register 15 contains a hexadecimal are not addressable.
reason code. (Message ICH409I, if issued, also contains this return
code.) 00050000 For a call to the Retrieve_Log_Name service, the param-
eters are not in the primary address space.
Code Explanation
00050001 For a call to the Retrieve_Log_Name service, the param-
00 No accessor environment element (ACEE) was available eters are not addressable.
to describe the user.
00060000 For a call to the Retrieve_UR_Interest service, the
parameters are not in the primary address space.
Note: This is normal if a job started or a user logged
on while RACF was inactive but has since been 00060001 For a call to the Retrieve_UR_Interest service, the
reactivated. parameters are not addressable.
04 No UCB was found to contain a volume serial that 00070000 For a call to the Process_Interest service, the parame-
matched the volume serial passed to RACF in the ters are not in the primary address space.
REQUEST=DEFINE macro instruction for a 00070001 For a call to the Process_Interest service, the parame-
TYPE=DEFINE operation. ters are not addressable.
08 The ADDVOL or CHGVOL function was requested but 00080000 For a call to the Set_Log_Name service, the parameters
the user did not have at least UPDATE authority to the are not in the primary address space.
data set.
00080001 For a call to the Set_Log_Name service, the parameters
0C The ADDVOL function was requested and (1) the are not addressable.
volume serial number is already defined (for DATASET
00090000 For a call to the Post_Deferred_UR_Exit routine service,
class), or (2) the new tape volume is already defined (for
the parameters are not in the primary address space.
TAPEVOL class).
00090001 For a call to the Post_Deferred_UR_Exit routine service,
The CHGVOL function was requested and a data set
the parameters are not addressable.
profile with ENTITY name and a new volume serial
number is already defined. 000B0000 For a call to the Retrieve_Interest_Data service, the
parameters are not in the primary address space.
Identify and correct the indicated error.
000B0001 For a call to the Retrieve_Interest_Data service, the
System Programmer Response: For reason code 00, run the job
parameters are not addressable.
again, or have the user log on again while RACF is active. If the
abend occurs again, see OS/390 Security Server (RACF) Diagnosis 000C0000 For a call to the Retrieve_UR_Data service, the parame-
Guide for information on diagnosing abends and reporting abend ters are not in the primary address space.
problems to IBM. For the other reason codes, correct the problem
SCC-146 OS/390 V2R8.0 MVS System Codes
5C4 5C4
000C0001 For a call to the Retrieve_UR_Data service, the parame- 00150010 The program called the Application_Backout_UR service,
ters are not addressable. but the current UR (the UR being processed) encount-
ered an unexpected error, and RRS cannot continue to
000D0000 For a call to the Retrieve_Side_Information service, the
process the UR.
parameters are not in the primary address space.
00150011 The program called the Application_Backout_UR service,
000D0001 For a call to the Retrieve_Side_Information service, the
but the service encountered an unexpected error from a
parameters are not addressable.
context services service.
000E0000 For a call to the Retrieve_Work_Identifier service, the
00160000 For a call to the Application_Commit_UR service, the
parameters are not in the primary address space.
parameters are not in the primary address space.
000E0001 For a call to the Retrieve_Work_Identifier service, the
00160001 For a call to the Application_Commit_UR service, the
parameters are not addressable.
parameters are not addressable.
000F0000 For a call to the Change_Interest_Type service, the
00160002 The program that called the Application_Commit_UR
parameters are not in the primary address space.
service is disabled; the interrupt status must be enabled
000F0001 For a call to the Change_Interest_Type service, the for I/O and external interrupts.
parameters are not addressable.
00160003 The program that called the Application_Commit_UR
00100000 For a call to the Set_Persistent_Interest_Data service, service is holding one or more locks; no locks must be
the parameters are not in the primary address space. held.
00100001 For a call to the Set_Persistent_Interest_Data service, 00160004 The program called the Application_Commit_UR service.
the parameters are not addressable. The system release does not support this service.
00110000 For a call to the Retain_Interest service, the parameters 00160005 The program that called the Application_Commit_UR
are not in the primary address space. service is in an unsupported ASC mode; the mode must
00110001 For a call to the Retain_Interest service, the parameters be primary.
are not addressable. 00160006 The program called the Application_Commit_UR service.
00120000 For a call to the Set_Sync-point_Controls service, the The UR is not in a valid state for the service call. The
parameters are not in the primary address space. UR state must be in-reset or in-flight.
00120001 For a call to the Set_Sync-point_Controls service, the 00160007 The program called the Application_Commit_UR service.
parameters are not addressable. The service encountered an unexpected error. RRS
writes a logrec record and takes a dump.
00130000 For a call to the Set_Side_Information service, the
parameters are not in the primary address space. 00160008 An application program called the
Application_Commit_UR service but a resource manager
00130001 For a call to the Set_Side_Information service, the
has already taken the server distributed sync-point
parameters are not addressable.
resource manager role (SDSRM), and only the SDSRM
00140000 For a call to the Set_Work_Identifier service, the param- can initiate a syncpoint operation.
eters are not in the primary address space.
00160009 The program that called the Application_Commit_UR
00140001 For a call to the Set_Work_Identifier service, the param- service is not in task mode, which is required.
eters are not addressable.
00160010 The program called the Application_Commit_UR service,
00150000 For a call to the Application_Backout_UR service, the but the current UR (the UR being processed) encount-
parameters are not in the primary address space. ered an unexpected error, and RRS cannot continue to
process the UR.
00150001 For a call to the Application_Backout_UR service, the
parameters are not addressable. 00160011 The program called the Application_Commit_UR service,
but the service encountered an unexpected error from a
00150002 For a call to the Application_Backout_UR service, the
context services service.
caller is disabled.
00170000 For a call to the Backout_UR service, the parameters
00150003 The program that called the Application_Backout_UR
are not in the primary address space.
service is holding one or more locks; no locks must be
held. 00170001 For a call to the Backout_UR service, the parameters
are not addressable.
00150004 The program called the Application_Backout_UR service.
The system release does not support this service. 00180000 For a call to the Commit_UR service, the parameters are
not in the primary address space.
00150005 The program that called the Application_Backout UR
service is in an unsupported ASC mode; the mode must 00180001 For a call to the Commit_UR service, the parameters are
be primary. not addressable.
00150006 The program called the Application_Backout_UR service. 001A0000 For a call to the Backout_Agent_UR service, the param-
The UR is not in a valid state for the service call. The eters are not in the primary address space.
UR state must be in-reset or in-flight.
001A0001 For a call to the Backout_Agent_UR service, the param-
00150007 The program called the Application_Backout_UR service. eters are not addressable.
The service encountered an unexpected error. RRS
001B0000 For a call to the Commit_Agent_UR service, the parame-
writes a logrec record and takes a dump.
ters are not in the primary address space.
00150009 The program that called the Application_Backout_UR
001B0001 For a call to the Commit_Agent_UR service, the parame-
service is not in task mode, which is required.
ters are not addressable.
System Completion Codes SCC-147
5C6 5FB
001C0000 For a call to the Forget_Agent_UR service, the parame- information. Search problem reporting data bases for a fix for the
ters are not in the primary address space. problem. If no fix exists, contact the IBM Support Center. Provide the
SYSOUT output for the job and the logrec data set error record.
001C0001 For a call to the Forget_Agent_UR service, the parame-
ters are not addressable.
5FB
001D0000 For a call to the Prepare_Agent_UR service, the param-
eters are not in the primary address space. Explanation: During processing of an MVS-JES3 allocation sub-
system interface routine, an error occurred. A hexadecimal reason
001D0001 For a call to the Prepare_Agent_UR service, the param-
code in register 15 explains the error.
eters are not addressable.
Code Explanation
01010005 RRS WHEN CFS ARE DOWN
01 In common allocation, the number of devices requested
FFFF2222 The SETRRS CANCEL command has cancelled RRS
by MVS does not equal the number to be allocated by
processing
JES3. Register 3 contains the number requested by
Source: Resource recovery services (RRS) MVS; register 5 contains the number passed by JES3.
System Action: The system rejects the service call. The system Register 2 contains the address of the DDNAME.
abnormally ends the calling program. 02 During deallocation processing, JES3 cannot success-
Programmer Response: For most of the reason codes, check the fully issue an ESTAE macro.
calling program for a probable coding error; correct the program and 03 JES3 cannot obtain storage for a dynamic allocation
rerun it. buffer.
For reason code X'xxxx000B', either enlarge CSA or contact the 04 JES3 cannot obtain storage for a change DDNAME
IBM Support Center and provide the dump. buffer.
For reason code X'00150004' or X'00160004', remove the calling 05 JES3 cannot find, in any address space header, the
program from the system, and install it on a system that supports address space identifier (ASID) associated with the
RRS. Then rerun the program. request. Register 2 contains the address of the job step
For reason code X'00150007' or X'00160007', obtain the related control block (JSCB); register 3 contains the ASID.
logrec record and dump, then contact IBM support. 06 A job summary table (JST) pointer error occurred during
For reason code X'00150010' or X'00160010', check other diag- common allocation or deallocation.
nostic information to determine why RRS encountered the error. To 07 Module IATSICA cannot find an active MEMDATA entry
ensure resource consistency, you might need to intervene manually. for the address space. Register 2 contains the address
For reason code X'00150011' or X'00160011', check diagnostic of the job step control block (JSCB); register 3 contains
information, such as the dump, from context services to determine the address space ID (ASID) of the requesting address
why the error occurred. space; register 8 contains the address of the MEMDATA
header.
For reason code X'01010005', check that coupling facilities are
active. 08 Module IATSIMS cannot find an active MEMDATA entry
for the address space. Register 4 contains the address
For reason code X'FFFF2222', no action is necessary. of the subsystem identification block (SSIB); register 6
For any other reason code, save any dump related to the problem contains field SSIBSUSE of the SSIB. However, both
and call the IBM Support Center. registers 4 and 6 may be incorrect.
09 JES3 found a duplicate volume. The volume cannot be
5C6 loaded. Register 2 contains the address of the
SETUNIT; register 6 contains the address of the job
Explanation: When the system detects an error in internal IBM
summary table (JST).
MQSeries processing, it will abnormally end a connected user task
(TCB) or one of its own internal tasks. See the MQSeries for 0A The GETMAIN macro failed for a work area for the sub-
MVS/ESA V1.2 Problem Determination Guide for a description of system interface (SSI).
diagnostic approaches to either a X'5C6' or X'6C6' abend. For
0B JES3 cannot process the number of concatenated DD
information about the reason codes associated with either abend,
statements passed in a change DD name request. The
see the MQSeries for MVS/ESA V1.2 Messages and Codes.
number of DD statements is variable; the approximate
Source: MQSeries maximum number is 187.
System Action: The system abnormally ends the connected user Register 3 contains the macro return code for reason code X'02',
task or the MQSeries internal task. X'03', X'04', X'06', or X'0A'.
Programmer Response: Check register 15 of the SDWA section Source: JES3
'General Purpose Registers at Time of Error', and locate the accom-
System Action: The system abnormally ends the task.
panying reason code. In addition, check the information displayed at
the console screen, and in the corresponding logrec data set entry. System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: If the error recurs and the
Support Center.
program is not in error, look at the messages in the job log for more
Provide the JCL and the program listing for the job.
SCC-148 OS/390 V2R8.0 MVS System Codes
5FC 5FC
5FC 605
Explanation: Following a restart interrupt, an error occurred in the Explanation: An error occurred when the system tried to process
restart first level interrupt handler (FLIH). an EC, EU, LC, LU, VC, or VU form of the FREEMAIN macro. A
reason code in the SDWACRC field of the system diagnostic work
Source: Loadwait/Restart
area (SDWA) explains the error:
System Action: The system abnormally ends the task that experi-
Code Explanation
enced the restart interrupt.
04 The parameter list is not on a word boundary.
Operator Response: Press the restart button again. If the problem
recurs, notify the system programmer. 08 The parameter list is in protected storage.
Programmer Response: Submit the job again. If the problem 0C The length list is not on a word boundary.
recurs, notify the system programmer.
10 The length list is in protected storage.
System Programmer Response: Ask the operator to set a SLIP
14 The address list is not on a word boundary.
trap to obtain an SVC dump. Search problem reporting data bases
for a fix for the problem. If no fix exists, contact the IBM Support 18 The address list is in protected storage.
Center. Provide the SVC dump and, if available, the logrec data set 1C The parameter list request flags are not valid.
error record for the abend.
Source: Virtual storage manager (VSM)
System Action: The system issues message IEA705I. The system
602 abnormally ends the current task.
Explanation: An error occurred during processing of a POST Programmer Response: Ensure that the length list and address
macro instruction. The system issues this abend only in association list are aligned on word boundaries. Check for program errors that
with cross memory post processing. incorrectly modify the parameter list. Correct them. Run the job step
again.
The hexadecimal return code in register 15 indicates the nature of
the error:
60D
Code Explanation
Explanation: The recovery termination manager (RTM) discovered
00 The target address space control block (ASCB) is incor- an error in a calling program.
rect.
A hexadecimal reason code in the following explains the error:
Source: Task management
Field RTM2CRC of the RTM2 work area (RTM2WA)
System Action: The system abnormally ends the program that Message IEA995I
issued the POST macro. TCBARC field of the task control block (TCB)
Programmer Response: Correct the error identified by the return Code Explanation
code. Run the job step again.
00 RTM percolates past the previous exit routine because
System Programmer Response: If the error recurs and the the recursion limit had been reached for that routine.
program is not in error, search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support Center. 04 A program issued the ABEND, CALLRTM, or SETRP
macro with the DUMPOPT or DUMPOPX parameter.
DUMPOPT or DUMPOPX contains a pointer to a param-
604
eter list, but RTM cannot access the parameter list.
Explanation: An error occurred when the system tried to process
08 A program issued the ABEND, CALLRTM, or SETRP
an EC, EU, LC, LU, VC, or VU form of the GETMAIN macro. A
macro with the DUMPOPT or DUMPOPX parameter.
reason code in the SDWACRC field of the system diagnostic work
DUMPOPT or DUMPOPX contains a pointer to a param-
area (SDWA) explains the error:
eter list. The parameter list contains a storage range
Code Explanation list, but RTM cannot access the storage range list.
04 The parameter list is not on a word boundary. 0C A program issued the ABEND, CALLRTM, or SETRP
08 The parameter list is in protected storage. macro with the DUMPOPT or DUMPOPX parameter.
DUMPOPT or DUMPOPX contains a pointer to a param-
0C The length list is not on a word boundary. eter list. The parameter list contains a subpool list, but
10 The length list is in protected storage. RTM cannot access the subpool list.
14 The address list is not on a word boundary. 10 A program issued the ABEND, CALLRTM, or SETRP
macro with the DUMPOPT or DUMPOPX parameter.
18 The address list is in protected storage.
DUMPOPT or DUMPOPX contains a pointer to a param-
1C The parameter list request flags are not valid. eter list. The parameter list contains a range of data
Source: Virtual storage manager (VSM) space storage to be dumped, but RTM cannot access
this storage.
System Action: The system issues message IEA705I. The system
abnormally ends the current task. 14 Retry was attempted from an FRR, but the retry linkage
stack is inconsistent with the requested retry environ-
Programmer Response: Ensure that the length list and address ment.
list are aligned on word boundaries. Check for program errors that
incorrectly modify the parameter list. Correct them. Run the job step 18 Retry was attempted from an FRR, but the linkage stack
again. entry is not in the currently active linkage stack range.
Source: Recovery termination manager (RTM)
System Completion Codes SCC-149
613 622
System Action: Depending on the reason code, the system does
614
the following:
Explanation: The error occurred during processing of a CLOSE
For reason code X'00', RTM:
macro instruction for a data set on a direct access device. This
– Gives control to any previous exit routines that are valid system completion code is accompanied by message IEC214I. Refer
– Resets the recursion count to 0 to the explanation of message IEC214I for complete information
about the job that was ended and for an explanation of the return
– Requests a dump code (rc in the message text) in register 15.
– Issues message IEA995I Source: DFSMSdfp
For reason codes 4 - 10, RTM continues processing the current Programmer Response: Respond as indicated for message
recovery routine and issues message IEA995I. IEC214I.
For reason codes 14 - 18, the retry is not performed. System Programmer Response: If the error recurs and the
System Programmer Response: For reason code X'00': 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
Look in the dump for a task control block (TCB) with X'60D' in
problem. If no fix exists, contact the IBM Support Center. Provide the
the TCBCMP field. Look at the accompanying STAE control
JCL and the program listing for the job.
blocks (SCB). There will be at least 32 SCBs. The SCBEXIT
field contains the address of the recovery routine. Many of the
SCBs will have the same recovery routine address. Use the 622
SCBEXIT value which is contained in many of the SCBs to get Explanation: A task entered from a Time Sharing Option (TSO) ter-
the name of the module of the recovery routine. minal ended for one of the following reasons:
Identify the component for the module. 1. The system encountered one of the following errors while con-
– If the recovery routine is an installation-provided module, structing control blocks for TSO:
correct the original error and the exit routine that ended a. The system encountered a multiple-step procedure.
recursively, or correct the problem with the DUMPOPT or b. The prompting task ended abnormally.
DUMPOPX parameter list.
2. The operator issued a MODIFY TCAM,TS=STOP command.
– If the recovery routine is an IBM module, search problem
reporting data bases for a fix for the problem. If no fix 3. The terminal user signaled ATTN during LOGON scheduling.
exists, contact the component group for the module at the 4. The user submitting the job disconnected his or her terminal
IBM Support Center. Provide problem data collected in pre- from the system.
vious steps.
5. TCAM disconnected the terminal because of an I/O error.
For reason codes 04 - 10, identify the program that issued
6. The terminal malfunctioned.
ABEND, CALLRTM, or SETUP with the DUMPPT/DUMPOPX
parameter. If it is an installation module, correct the problem. If it Source: Time Sharing Option Extensions (TSO/E)
is an IBM module, search problem reporting data bases for a fix System Action: In cases 1 and 2, the system issued messages to
for the problem. If no fix exists, contact the IBM Support Center. the terminal describing the error conditions.
For reason codes 14 -18, contact the IBM Support Center. Programmer Response: In the first case, respond to the mes-
sages accompanying this abend:
613 For case 1a, specify a different procedure or consult your
Explanation: The error occurred during processing of an OPEN system programmer. Try running the job again.
macro instruction for a data set on magnetic tape. This system com- For case 1b, consult your system programmer.
pletion code is accompanied by message IEC147I. Refer to the
explanation of message IEC147I for complete information about the In the second case, try running the job again when TSO is started.
job that was ended and for an explanation of the return code (rc in In the third case, LOGON again; make sure that you do not signal
the message text) in register 15. ATTN inadvertently.
Source: DFSMSdfp In the fourth case, try running the job again when the terminal is
Programmer Response: Respond as indicated for message reconnected to the system.
IEC147I. In the fifth case, find the cause of the I/O error, correct the condition,
System Programmer Response: If the error recurs and the and rerun the job.
program is not in error, look at the messages in the job log for more In the sixth case, contact hardware support.
information. Search problem reporting data bases for a fix for the
System Programmer Response: If the problem recurs and if the
problem. If no fix exists, contact the IBM Support Center. Provide the
program is not in error, search problem reporting data bases for a fix
JCL and the program listing for the job.
for the problem. If no fix exists, contact the IBM Support Center.
Provide the terminal sheet available and a record of the current
display on the graphics device.
SCC-150 OS/390 V2R8.0 MVS System Codes
637 66D
For example, if the reason code is X'0008000D', the abend reason
637
code is X'000D' and the return code of the function called by the
Explanation: The error occurred at an end-of-volume for a data set module is X'0008'.
on magnetic tape or an end-of-volume during concatenation. This
Code Explanation
system completion code is accompanied by message IEC026I. Refer
to the explanation of message IEC026I for complete information 01 Recovery cannot be established. This is an internal
about the task that was ended and for an explanation of the return error. TSO does not perform the requested function.
code (rc in the message text) in register 15. 02 ECTIOWA contains an non-valid input stack address.
Source: DFSMSdfp 03 The input stack was in use by another task when re-
Programmer Response: Respond as indicated for message serialization was done. I/O services, REXX, or CLIST
IEC026I. processing encountered an error in a multitasking envi-
ronment.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 04 An non-valid I/O service identifier was supplied by the
information. Search problem reporting data bases for a fix for the caller. This is an internal error. TSO does not perform
problem. If no fix exists, contact the IBM Support Center. Provide the the requested function.
JCL and the program listing for the job. 05 A input stack address is supplied in ECTIOWA but no
stack exists.
644 06 No input stack exists.
Explanation: The error occurred during the processing of 07 No input stack exists, but one is being created by
SYNADAF, where it was determined that the message buffer another program. I/O service processing encountered an
obtained in the user's region had been modified or freed. error in a multitasking environment. Two tasks cannot
Source: DFSMSdfp create the first stack at the same time.
Programmer Response: Register 15 contains the address of the 08 An abend X'0C4' occurred when validating user
message buffer area. Make sure that your program does not modify pointers.
or free this area until SYNADAF processing is complete. Correct the 09 The input stack is in use.
error and rerun the job step.
0A An ECT was provided, but no stack exists.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 0B The ECTIOWA field does not contain the address of a
information. Search problem reporting data bases for a fix for the valid stack.
problem. If no fix exists, contact the IBM Support Center. Provide the 0C The user is trying to delete a stack which someone else
JCL and the program listing for the job. is waiting on.
0D REXX is unable to serialize on an internal resource.
65F
0E Unable to locate the REXX data stack.
Explanation: The system resources manager (SRM) stopped the
collection of channel measurement data in the channel measurement 0F IRXESTK1 found an incorrect count of elements in the
block (CMB) because of an error condition. REXX data stack.
Source: System resources manager (SRM) 10 IRXESTK1 found an incorrect REXX data stack size.
System Action: The system writes message IRA602I to identify the 11 IRXESTK failed when called by IRXESTK1.
error. The system writes a logrec data set error record. The system 12 IRXESTK failed to purge the number of stack elements
abnormally ends the current task. It cannot be resumed until the next requested by IRXESTK1.
IPL.
13 REXX stack processing failed to release an internal
The SRM functions, device selection and I/O balancing, use algo- REXX resource.
rithms that do not make use of CMB data.
14 IRXINIT failed.
System Programmer Response: Look at the reason code in
15 REXX variable protection failed.
message IRA602I. Search problem reporting data bases for a fix for
the problem. If no fix exists, contact the IBM Support Center. Provide 16 The MARKTERM function of IRXESTK failed. While
the logrec data set error record. processing the data stack, TSO I/O services encount-
ered an error. TSO does not perform the requested func-
66D tion.
Explanation: This abend may be issued from three different areas 17 The DROPTERM function of IRXESTK failed. While
in TSO/E: I/O services, REXX, and CLIST processing. A processing the data stack, TSO I/O services encount-
hexadecimal reason code identifies the error. This code appears ered an error. TSO does not perform the requested func-
either on user's terminal, along with the abend notification, or in the tion.
dump taken for the abend. 18 The PULL function of IRXESTK failed. While processing
Note: The reason code appears on the user's terminal as a four- the data stack, TSO I/O services encountered an error.
byte field. The rightmost two bytes contain the abend reason TSO does not perform the requested function.
code. If these two bytes are between X'000D' and X'0013', 19 The input stack size limit was exceeded.
then the leftmost two bytes (if they are non-zero) contain the
1E The REXX storage manager was passed a control block
return code of the function called by the module that issued
that is not valid.
the abend.
System Completion Codes SCC-151
66D 66D
1F The REXX storage manager was requested to free 43 A TSO/E Service Routine detected a serialization error
storage for a control block that is not valid. with the ALTLIB or VLF environment.
20 The REXX storage manager could not allocate storage 44 The user is trying to OPENFILE a dataset which is
from the requested control block due to an internal error. marked EXECUTE-ONLY.
21 The REXX storage manager could not free storage for 45 The user is trying to submit a member of a dataset
the requested control block because the storage was which is marked EXECUTE-ONLY.
freed previously.
46 The user is trying to execute a CLIST from a dataset
22 The REXX storage manager could not free the storage which is marked EXECUTE-ONLY.
because the storage tree is not valid.
47 The user invoked the TSO/E environment service with a
23 The REXX storage manager could not free the storage bad parameter list.
because the storage tree is not valid.
48 The user tried to invoke the TSO/E environment service
24 The REXX storage manager could not allocate the on an incorrect version of TSO/E.
requested storage. The tree used to manage the storage
49 The user attempted to run an authorized command or
has an incorrect format.
program. This is not supported in the TSO/E environ-
25 The REXX storage manager could not allocate the ment created by the TSO/E environment service.
requested storage. An internal tree-management routine
4A The user attempted to attach the TSO/E TMP routine
failed.
(IKJEFT01) while in a dynamic TSO/E environment.
26 The REXX storage manager could not allocate the
4B REXX output processing failed in a TSO/E environment.
requested storage. The tree was determined to be not
No command processor parameter list (CPPL) was avail-
valid after storage allocation occurred.
able.
27 The REXX storage manager could not allocate the
4C REXX output processing failed in a TSO/E environment.
requested storage. The tree was determined to be not
valid after storage allocation occurred. 4D TSO/E has detected an overlay condition while reading a
member from a concatenated data set. One possible
28 The REXX storage manager could not assign the new
reason for this overlay condition is the concatenation of
extent.
data sets with unlike RECFM specifications.
29 The REXX storage manager could not obtain additional
50 The user entered the REXX immediate command HE in
storage from the main REXX storage manager control
order to halt execution of the current REXX exec. This
block.
abend does not represent an error condition.
2A The REXX storage manager determined that a tree is
81 Incorrect key or state at invocation.
not valid. An incorrect control block was present at the
top of the tree. 82 An ESTAE environment could not be established.
2B The REXX storage manager determined that a tree is 83 Caller is not at the expected operating system level
not valid. An incorrect control block was passed. (OS/390 Release 3 or higher).
2C The REXX storage manager determined that a tree is 84 Invalid request passed from caller.
not valid. An inner vertex appeared in place of the top of Note: If you are not able to locate the abend reason code in the
the tree. above table, see the note at the beginning of the ABEND66D
2D While invoking an internal routine, the REXX storage description section.
manager determined that no dynamic storage was avail- Source: Time Sharing Option Extensions (TSO/E)
able.
System Action: The action of the system varies depending on the
2E The REXX storage manager could not obtain the error and on the level of ESTAE that receives control. In all cases,
requested storage. the TSO/E or REXX function is not performed. However, for a TSO/E
2F The REXX storage manager could not free the CLIST or a REXX exec, a retry may be attempted following the
requested storage. statement that encountered the error. In most cases, the TSO/E
READY mode will be reinstated. If the abend occurs during TSO/E
30 Module IGX00043 was invoked with parameters that
logon, the user will need to logon again.
were not valid. TSO/E I/O services encountered an
internal error. TSO does not perform the requested func- Code System Action
tion. 02 - 0B An SVC dump is not taken for the abend.
31 A TSO/E service that requires a TSO/E environment was 0D - 13 See the note at the beginning of the ABEND66D
invoked in a non-TSO/E environment. description section. An SVC dump is not taken for the
3C The QUEUED function of IRXESTK failed. While proc- abend.
essing the data stack, TSO I/O services encountered an 14 - 19 An SVC dump is not taken for the abend.
error. TSO does not perform the requested function.
Programmer Response: Try rerunning the REXX exec or re-
40 GETMAIN failure. invoking the TSO/E function. The error may have been due to a tem-
41 Stack serialization token has wrapped. porary condition (such as insufficient storage), and your job may
succeed on a second attempt.
42 The token which was associated with the top stack
element has changed. This means that the stack has If the error is severe, the TSO/E session may need to be restarted.
been modified while the lock was released.
SCC-152 OS/390 V2R8.0 MVS System Codes
67D 684
Code Response
67D
02 Check the validity of the I/O service parameter list and
Explanation: During processing of an EVENTS macro, the system
the command processor parameter list (CPPL). Verify
found that the wait flag was already on in the event control block
that the ECT address in both of these parameter lists is
(ECB). The flag on indicated that a previous EVENTS or WAIT
correct, that is, the ECT address supplied to a command
macro was already waiting for posting of the ECB.
processor is in fact, in the CPPL.
Source: Task management
05 Check the validity of the I/O service parameter list and
the command processor parameter list (CPPL). Verify System Action: The system abnormally ends the program that
that the ECT address in both of these parameter lists is issued the EVENTS macro.
correct, that is, the ECT address supplied to a command Programmer Response: Change the problem program to eliminate
processor is in fact, in the CPPL. a double wait on a single event. If no double wait is found, ensure
06 Wait until the stack is created by the terminal monitor that the ECB was not incorrectly modified by the program. Then run
program (TMP) initialization function before calling this the job again.
service, or use the stack-create service. System Programmer Response: If the error recurs and the
08 Verify that all addresses in the I/O service parameter list program is not in error, look at the messages in the job log for more
(and the IKJCT441 parameter list if applicable) are information. Search problem reporting data bases for a fix for the
correct. problem. If no fix exists, contact the IBM Support Center. Provide the
program listing and the assembly listing associated with the job.
0B Provide a valid stack address in the ECTIOWA. The
stack address may be obtained from the ECT provided
by the ECT pointed to from the CPPL or the stack-create 683
service. Explanation: The module calling RACROUTE REQUEST=VERIFY
14 If your installation has replaced a parameters module, is not authorized (is not APF-authorized, in system key 0-7, or in
verify that the correct module was called during REXX supervisor state).
initialization. Note: If the NEWPASS keyword is not specified on the
15 The READY state resumes; retry the TSO function. REQUEST=VERIFY, you can authorize the calling module by
entering it in the RACF-authorized caller table. However, IBM
19 Log off from TSO/E and log back on. If the problem
does not recommend placing entries in the RACF-authorized
occurs again, check your programs that were running
caller table.
around the time of the abend. Any programs that
perform input stack operations using the stack service System Action: The task is terminated.
routine should be examined for possible looping condi- Programmer Response: Possible user error. Verify that the
tions. module is an authorized caller.
31 Rerun the program in a TSO/E environment or address Problem Determination: If the request originated as a RACF
space. command (that in turn resulted in the issuing of the
44 Obtain READ access from the owner of the dataset. The REQUEST=VERIFY), check to make sure the RACF command is in
user cannot OPENFILE a dataset marked the list of APF-authorized commands for your system.
EXECUTE-ONLY. If the module making the request is an IBM routine, see OS/390
45 Obtain READ access from the owner of the dataset. The Security Server (RACF) Diagnosis Guide for information on diag-
user cannot submit a member from a dataset marked nosing abends and reporting abend problems to IBM.
EXECUTE-ONLY.
46 Obtain READ access from the owner of the dataset. The 684
user cannot run CLISTs from a dataset marked Explanation: The module calling the RACF manager or the
EXECUTE-ONLY. RACROUTE REQUEST=LIST function is not authorized (is not
47 See OS/390 TSO/E Programming Services for informa- APF-authorized, in system key 0-7, or in supervisor state).
tion on invoking the TSO/E environment service. Correct System Action: The system abnormally terminates the task.
the error and invoke the TSO/E environment service
Note: If the NEWPASS keyword is not specified on the
again.
REQUEST=VERIFY, you can authorize the calling module by
48 Make sure the installation has the proper version of entering it in the RACF-authorized caller table. However, IBM
TSO/E installed. does not recommend placing entries in the RACF-authorized
49 Remove the TSO/E authorized command or program caller table.
that you tried to run. System Action: The task is terminated.
4B If you are using the IRXEXEC programming service, Programmer Response: Possible user error. Verify that the
provide a CPPL and retry the operation. module is an authorized caller.
4C Ensure that the TSO/E I/O services are available in the System Programmer Response: If the request originated as a
address space. RACF command (that in turn resulted in a call to the RACF manager
4D Invalid record length found. One possible reason is the or the REQUEST=LIST), check to make sure the RACF command is
concatenation of FB and VB data sets being used for in the list of APF-authorized commands for your system.
CLIST input. If the module making the request is an IBM routine, see OS/390
System Programmer Response: If no fix exists, contact the IBM Security Server (RACF) Diagnosis Guide for information on diag-
Support Center. nosing abends and reporting abend problems to IBM.
System Completion Codes SCC-153
685 6C4
02020001 The caller of a service is not in supervisor state.
685
Module: GOSAMCCP
Explanation: The module calling RACROUTE REQUEST=DEFINE
is not authorized (is not APF-authorized, in system key 0-7, or in System Action: The application is abnormally ended.
supervisor state). To issue a REQUEST=DEFINE, the calling module System Programmer Response: Verify that the appli-
must be authorized (APF-authorized, in system key 0-7, or in super- cation is using standard interfaces. If the problem per-
visor state). sists, contact the IBM Support Center.
System Action: The system abnormally terminates the task. 02020002 Common area storage could not be obtained.
Programmer Response: Possible user error. Verify that the calling Module: GOSAMCCP
module was executing in an authorized state.
System Action: The system issues abend X'6C4' and
System Programmer Response: If the request originated as a ends the command processing.
RACF command (that in turn resulted in the issuing of the
REQUEST=DEFINE), check to make sure the RACF command is in Programmer Response: Contact the system pro-
the list of APF-authorized commands for your system. grammer.
If the module making the request is an IBM routine, see OS/390 System Programmer Response: Increase the amount
Security Server (RACF) Diagnosis Guide for information on diag- of common storage specified on the CSA parameter in
nosing abends and reporting abend problems to IBM. IEASYSxx parmlib member. ReIPL the system to acti-
vate the change. If the problem persists, contact the IBM
Support Center.
6C4
02020003 An asynchronous cross memory post failed. A DSOM
Explanation: The SOM subsystem could not be initialized because command might have been entered while the system
one of the following occurred: was processing a command to stop the SOM sub-
Another SOM subsystem is already active system.
Another SOM subsystem ended without cleaning up its Module: GOSAMCCP
resources. System Action: The system abnormally ends the
Source: GOSAMISP command.
System Action: The SOM subsystem subsystem is not initialized. Operator Response: Start DSOM again. Once DSOM is
The system abnormally ends the command. The system continues started,enter the DSOM command again.
other processing. System Programmer Response: Restart the SOM sub-
System Programmer Response: Stop the DSOM subsystem that system. If the problem persists, contact the IBM Support
is active before starting this SOM subsystem. If the subsystem is Center.
already stopped and the problem persists, start the new SOM sub- 02080002 The system could not obtain common storage.
system with the same name as the SOM subsystem that previously
stopped. If the problem persists, contact the IBM Support Center. For Module: GOSAMCST
more information about starting and stopping a SOM subsystem, see System Action: The system abnormally ends the
OS/390 SOMobjects Configuration and Administration Guide. command.
A reason code further describes the error: System Programmer Response: Increase the amount
Code Explanation of common storage specified on the CSA parameter in
IEASYSxx parmlib member. ReIPL the system to acti-
000A1000 The activation of a logical unit failed because the VTAM vate the change. If the problem persists, contact the IBM
application for the logical unit is not APPC-capable. Support Center.
Check the VTAM APPL statement for the logical unit to
ensure that you specified APPC=YES. 02080003 An asynchronous cross memory post failed. A DSOM
command might have been entered while the system
System Action: The system also issues abend X'EC7' was processing a STOP DSOM command.
with reason code X'000A0037', which can be ignored.
Module: GOSAMCST
000100xx An internal error occurred.
System Action: The system abnormally ends the
System Action: The system continues processing, but command.
the requested APPC/MVS service fails. The system
writes an SVC dump. Operator Response: Enter a START DSOM command
to start DSOM again.
010F0002 DSOM could not open the data control block (DCB) for
the C runtime library for the SOM subsystem. The SOM System Programmer Response: If the problem per-
subsystem might not be installed properly. sists, contact the IBM Support Center.
Module: GOSAMCEE 05000001 Unsupported DSOM subsystem service.
System Action: The system ends the application. Module: GOSAPBAD
System Programmer Response: Ensure that the SOM System Action: The system abnormally ends the appli-
subsystem is properly installed. Ensure that the cation.
GOSRTL1 data sets are correct and accessible to the
userid associated with the SOM subsystem. If the User Response: Contact the system programmer.
problem persists, contact the IBM Support Center.
SCC-154 OS/390 V2R8.0 MVS System Codes
6C4 6C4
System Programmer Response: Verify that the appli- 05030004 The caller requested a security function that is not valid.
cation is using standard interfaces. If the problem per- The caller of the service is not valid.
sists, contact the IBM Support Center.
Module: GOSAPRC1
05010001 Input to a service routine is missing. The caller of the
System Action: The system abnormally ends the appli-
service is not valid. save
cation.
Module: GOSAPASC
System Action: The system abnormally ends the appli- System Programmer Response: Verify that the appli-
cation. cation is using standard interfaces. If the problem per-
sists, contact the IBM Support Center.
System Programmer Response: Verify that the appli- 0503000A The caller is not authorized to invoke the requested
cation is using standard interfaces. If the problem per- function. The caller of the service is not valid.
sists, contact the IBM Support Center.
Module: GOSAPRC1
05010002 The caller of a DSOM service is not valid.
System Action: The system abnormally ends the appli-
Module: GOSAPASC cation.
System Action: The system abnormally ends the appli-
cation. System Programmer Response: Verify that the appli-
cation is using standard interfaces. If the problem per-
sists, contact the IBM Support Center.
System Programmer Response: Verify that the appli-
cation is using standard interfaces. If the problem per- 05030109 The system could not process a RACROUTE
sists, contact the IBM Support Center. REQUEST=AUTH request when checking command
authorization to a server.
05010003 The system could not create a server address space.
Module: GOSAPRC1
Module: GOSAPASC
System Action: The system abnormally ends the appli-
System Action: The system records the error and con-
cation.
tinues processing. The system does not start the server.
System Programmer Response: Obtain the return
System Programmer Response: Verify that the appli-
code from the ASCRE macro in register 0. Verify that
cation is using standard interfaces. If the problem per-
the server PROC is defined correctly. See the section on
sists, contact the IBM Support Center.
using a JCL procedure to start a DSOM server in
OS/390 SOMobjects Configuration and Administration 0503000B A PC routine is not available.
Guide for more information. Enter the START command Module: GOSAGCRT, GOSAGCAU
to start the server. If the problem persists, contact the
IBM Support Center. System Action: The system issues abend X'6C4' to
the caller of the DSOM service. The system might issue
05020007 The caller of a service is not valid.
message GOS009I.
Module: GOSAPTRC
Operator Response: Enter a START DSOM command
System Action: The system abnormally ends the appli- to start DSOM again. If DSOM is already started and the
cation. system issued message GOS009I, contact the system
programmer.
System Programmer Response: Verify that the appli- System Programmer Response: If you cannot start
cation is using standard interfaces. If the problem per- DSOM, contact the IBM Support Center.
sists, contact the IBM Support Center.
05040001 Input to service routine missing. The caller of the service
05030001 Input to a service routine is missing. The caller of the is not valid.
service is not valid.
Module: GOSAPRC2
Module: GOSAPRC1
System Action: The system abnormally ends the appli-
System Action: The system abnormally ends the appli- cation.
cation.
System Programmer Response: Verify that the appli-
System Programmer Response: Verify that the appli- cation is using standard interfaces. If the problem per-
cation is using standard interfaces. If the problem per- sists, contact the IBM Support Center.
sists, contact the IBM Support Center.
05040003 The parameter list that was passed to a service routine
05030003 The caller passed a parameter list that is not valid. is not valid because the caller of the service is not valid.
Module: GOSAPRC1 Module: GOSAPRC2
System Action: The system abnormally ends the appli- System Action: The system abnormally ends the appli-
cation. cation.
System Programmer Response: Verify that the appli- System Programmer Response: Verify that the appli-
cation is using standard interfaces. If the problem per- cation is using standard interfaces. If the problem per-
sists, contact the IBM Support Center. sists, contact the IBM Support Center.
System Completion Codes SCC-155
6C4 6C4
05040004 Function requested from service routine is not valid. The return code, and X'zz' is the RACF reason code. See
caller of the service is not valid. OS/390 Security Server External Security Interface
Module: GOSAPRC2
(RACROUTE) Macro Reference for a description of the
return and reason codes from RACROUTE.
System Action: The system abnormally ends the appli-
05040102 During client authentication, the system could not
cation.
process a RACROUTE
REQUEST=LIST,ENVIR=CREATE request.
System Programmer Response: Verify that the appli-
Module: GOSAPRC2
cation is using standard interfaces. If the problem per-
sists, contact the IBM Support Center. System Action: The system abnormally ends the appli-
cation.
0504000A The caller is not authorized to invoke the requested
function. The caller of a service is not valid.
System Programmer Response: Register 0 contains
Module: GOSAPRC2
diagnostic information in the form X'00wwyyzz', where
System Action: The system abnormally ends the appli- X'ww' is the SAF return code, X'yy' is the RACF
cation. return code, and X'zz' is the RACF reason code. See
OS/390 Security Server External Security Interface
System Programmer Response: Verify that the appli- (RACROUTE) Macro Reference for a description of the
cation is using standard interfaces. If the problem per- return and reason codes from RACROUTE.
sists, contact the IBM Support Center. 05040103 During client authentication, the system could not
0504000B SOM subsystem services not available. process a RACROUTE REQUEST=FASTAUTH request.
Module: GOSACACE, GOSACACE, GOSACAUT, Module: GOSAPRC2
GOSADACE, GOSAGRTO, GOSAMAUT, GOSASAUT, System Action: The system abnormally ends the appli-
GOSASECI, GOSASECU cation.
System Action: The system issues abend X'6C4' to
the caller of the DSOM service. The system might issue System Programmer Response: Register 0 contains
message GOS009I. diagnostic information in the form X'00wwyyzz', where
Operator Response: Enter a START DSOM command X'ww' is the SAF return code, X'yy' is the RACF
to start DSOM again. If DSOM is already started and the return code, and X'zz' is the RACF reason code. See
system issued message GOS009I, contact the system OS/390 Security Server External Security Interface
programmer. (RACROUTE) Macro Reference for a description of the
return and reason codes from RACROUTE.
System Programmer Response: If you cannot start
DSOM, contact the IBM Support Center. 05040104 During client authentication or client/server disconnect,
the system could not process a RACROUTE
05040100 During security initialization, the system could not
REQUEST=VERIFY ENVIR=DELETE request.
process a RACROUTE
REQUEST=LIST,ENVIR=CREATE request for the Module: GOSAPRC2
SOMDOBJS RACF security class. System Action: The system abnormally ends the appli-
Module: GOSAPRC2 cation.
System Action: The system abnormally ends the appli-
cation. System Programmer Response: Register 0 contains
diagnostic information in the form X'00wwyyzz', where
X'ww' is the SAF return code, X'yy' is the RACF
System Programmer Response: Register 0 contains
return code, and X'zz' is the RACF reason code. See
diagnostic information in the form X'00wwyyzz', where
OS/390 Security Server External Security Interface
X'ww' is the SAF return code, X'yy' is the RACF
(RACROUTE) Macro Reference for a description of the
return code, and X'zz' is the RACF reason code. See
return and reason codes from RACROUTE.
OS/390 Security Server External Security Interface
(RACROUTE) Macro Reference for a description of the 05040105 During security cleanup processing, the system could
return and reason codes from RACROUTE. not process a RACROUTE REQUEST=LIST
ENVIR=DELETE request.
05040101 During security initialization, the system could not
process a RACROUTE Module: GOSAPRC2
REQUEST=LIST,ENVIR=CREATE request for the System Action: The system abnormally ends the appli-
CBIND RACF security class. cation.
Module: GOSAPRC2
System Action: The system abnormally ends the appli- System Programmer Response: Register 0 contains
cation. diagnostic information in the form X'00wwyyzz', where
X'ww' is the SAF return code, X'yy' is the RACF
return code, and X'zz' is the RACF reason code. See
System Programmer Response: Register 0 contains
OS/390 Security Server External Security Interface
diagnostic information in the form X'00wwyyzz', where
(RACROUTE) Macro Reference for a description of the
X'ww' is the SAF return code, X'yy' is the RACF
return and reason codes from RACROUTE.
SCC-156 OS/390 V2R8.0 MVS System Codes
6C4 6C4
05040106 During security cleanup processing, the system could Module: GOSAPRC2
not process a RACROUTE REQUEST=LIST
System Action: The system abnormally ends the appli-
ENVIR=DELETE request for the CBIND RACF security
cation.
class.
Module: GOSAPRC2
System Programmer Response: Register 0 contains
System Action: The system abnormally ends the appli- diagnostic information in the form X'00wwyyzz', where
cation. X'ww' is the SAF return code, X'yy' is the RACF
return code, and X'zz' is the RACF reason code. See
System Programmer Response: Register 0 contains
OS/390 Security Server External Security Interface
diagnostic information in the form X'00wwyyzz', where
(RACROUTE) Macro Reference for a description of the
return and reason codes from RACROUTE.
X'ww' is the SAF return code, X'yy' is the RACF
return code, and X'zz' is the RACF reason code. See 0504010B During method level authorization processing, a bad
OS/390 Security Server External Security Interface parameter was passed to the service. The caller of the
(RACROUTE) Macro Reference for a description of the service is not valid.
return and reason codes from RACROUTE.
Module: GOSAPRC2
05040107 During client/server connect processing, the system
System Action: The system abnormally ends the appli-
could not process a RACROUTE REQUEST=LIST
cation.
REQUEST=VERIFY ENVIR=CREATE PASSCHK=NO
request.
System Programmer Response: Register 0 contains
Module: GOSAPRC2
diagnostic information in the form X'00wwyyzz', where
System Action: The system abnormally ends the appli- X'ww' is the SAF return code, X'yy' is the RACF
cation. return code, and X'zz' is the RACF reason code. See
OS/390 Security Server External Security Interface
System Programmer Response: Register 0 contains
(RACROUTE) Macro Reference for a description of the
return and reason codes from RACROUTE.
diagnostic information in the form X'00wwyyzz', where
X'ww' is the SAF return code, X'yy' is the RACF 0507000A The caller is not authorized to invoke the requested
return code, and X'zz' is the RACF reason code. See function. The caller of the service is not valid.
OS/390 Security Server External Security Interface Module: GOSAPRST
(RACROUTE) Macro Reference for a description of the
return and reason codes from RACROUTE. System Action: The system abnormally ends the appli-
cation.
05040108 During method level authorization processing, the
system could not process a RACROUTE
REQUEST=FASTAUTH request. System Programmer Response: Verify that the appli-
cation is using standard interfaces. If the problem per-
Module: GOSAPRC2
sists, contact the IBM Support Center.
System Action: The system abnormally ends the appli-
050B0001 Input to a service routine is missing. The caller of the
cation.
service is not valid.
Module: GOSAPIOK
System Programmer Response: Register 0 contains
diagnostic information in the form X'00wwyyzz', where System Action: The system abnormally ends the appli-
X'ww' is the SAF return code, X'yy' is the RACF cation.
return code, and X'zz' is the RACF reason code. See
OS/390 Security Server External Security Interface System Programmer Response: Verify that the appli-
(RACROUTE) Macro Reference for a description of the cation is using standard interfaces. If the problem per-
return and reason codes from RACROUTE. sists, contact the IBM Support Center.
05040109 During server authorization processing, the system could 050B0002 The caller of a DSOM service is not valid.
not process a RACROUTE REQUEST=AUTH request.
Module: GOSAPIOK
Module: GOSAPRC2
System Action: The system abnormally ends the appli-
System Action: The system abnormally ends the appli- cation.
cation.
System Programmer Response: Verify that the appli-
System Programmer Response: Register 0 contains cation is using standard interfaces. If the problem per-
diagnostic information in the form X'00wwyyzz', where sists, contact the IBM Support Center.
X'ww' is the SAF return code, X'yy' is the RACF
050C0001 Input to service routine missing. The caller of the service
return code, and X'zz' is the RACF reason code. See
is not valid.
OS/390 Security Server External Security Interface
(RACROUTE) Macro Reference for a description of the Module: GOSAPSER
return and reason codes from RACROUTE.
System Action: The system abnormally ends the appli-
0504010A During server authorization or client authentication proc- cation.
essing, the system could not process a RACROUTE
REQUEST=EXTRACT,TYPE=ENCRYPT request.
System Completion Codes SCC-157
6C5 6C5
System Programmer Response: Verify that the appli-
6C5
cation is using standard interfaces. If the problem per-
sists, contact the IBM Support Center. Explanation: During processing of an IARVSERV macro, the
system found a non-environmental error. The macro processing
050C0003 The parameter list that was passed to a service routine
failed. Register 15 contains one of the following hexadecimal reason
is not valid because the caller of the service is not valid.
codes.
Module: GOSAPSER
Code Explanation
System Action: The system abnormally ends the appli-
xx0120xx For a SHARE request, the STOKEN for the source area
cation.
does not represent a valid data space token.
xx0121xx For a SHARE request, the STOKEN for the target area
System Programmer Response: Verify that the appli-
does not represent a valid data space token.
cation is using standard interfaces. If the problem per-
sists, contact the IBM Support Center. xx0122xx For a SHARE request, the beginning address of the
source area specified in the range list entry is not page-
050C0004 Function requested from service routine is not valid. The
boundary aligned.
caller of the service is not valid.
xx0123xx For a SHARE request, the beginning address of the
Module: GOSAPSER
target area specified in the range list entry is not page-
System Action: The system abnormally ends the appli- boundary aligned.
cation.
xx0124xx For a SHARE request, the source and target areas are
not different.
System Programmer Response: Verify that the appli-
xx0125xx For a SHARE request, specified storage has not been
cation is using standard interfaces. If the problem per-
obtained with GETMAIN macro or STORAGE macro with
sists, contact the IBM Support Center.
the OBTAIN parameter as part of the pageable private
050C0005 Unable to create DSOM latch region of the caller's address space, nor within the size
Module: GOSAPSER of an existing data space as pageable storage.
System Action: The system abnormally ends the appli- xx0126xx For a SHARE request, the caller does not have legal
cation. access to the source area with the given ALET.
xx0127xx For a SHARE request, the caller does not have legal
System Programmer Response: Obtain the return access to the source area with the given STOKEN.
code from the latch obtain service (ISGLCRT) in register xx0128xx For a SHARE request, the caller does not have legal
zero. See OS/390 MVS Programming: Authorized access to the target area with the given ALET.
Assembler Services Reference ENF-IXG for descriptions
xx0129xx For a SHARE request, the caller does not have legal
of return codes from ISGLCRT.
access to the target area with the given STOKEN.
050C0006 Unable to obtain DSOM latch
xx012Axx For a SHARE request, the address space that owns the
Module: GOSAPSER source is not swapped in.
System Action: The system abnormally ends the appli- xx012Bxx For a SHARE request, the address space that owns the
cation. target is not swapped in.
xx012Cxx For a SHARE request, the caller's PSW key is insuffi-
System Programmer Response: Obtain the return cient for altering the target area.
code from the latch obtain service (ISGLOBT) in register
xx012Dxx For a SHARE request, the
zero. See OS/390 MVS Programming: Authorized
TARGET_VIEW(SHAREDWRITE) option is specified but
Assembler Services Reference ENF-IXG for descriptions
the caller's PSW key is insufficient for altering the source
of return codes from ISGLOBT.
area.
050C0007 Unable to release DSOM latch
xx012Exx For a SHARE request, one page in the source area and
Module: GOSAPSER its corresponding page in the target area do not have
System Action: The system abnormally ends the appli- the same storage protect key and fetch-protection status.
cation. xx012Fxx For a SHARE request, the source area is not acceptable
because it contains system data that is not eligible for
System Programmer Response: Obtain the return sharing.
code from the latch release service (ISGLREL) in reg- xx0130xx For a SHARE request, the target area is not acceptable
ister zero. See OS/390 MVS Programming: Authorized because it contains system data that should not be
Assembler Services Reference ENF-IXG for descriptions altered by the caller.
of return codes from ISGLREL.
xx0131xx For a SHARE request, the target area contains unac-
ceptable pages, such as pages that are page-protected
or page-fixed.
xx0132xx For a SHARE request, the source and the target areas
do not meet the storage attribute requirements for
sharing.
SCC-158 OS/390 V2R8.0 MVS System Codes
6C5 6C5
xx0133xx For a SHARE request, READONLY sharing pages xx0238xx For an UNSHARE request, part of the target area is in a
cannot be made shared with SHAREDWRITE. Hiperspace, VIO window, V=R region, or PSA.
xx0134xx For a SHARE request, the source area contains pages xx0239xx For an UNSHARE request, the number of pages speci-
that are shared with a target view of TARGETWRITE. fied in a range list entry is not valid.
xx0135xx For a SHARE request, the source area contains pages xx023Bxx For an UNSHARE request, the specified target ALET
that are currently to a hiperspace object through the DIV represents a subspace.
macro.
xx023Fxx For an UNSHARE request, the specified target ALET is
xx0136xx For a SHARE request, the target area contains pages not valid.
that are currently mapped through the DIV macro.
xx0321xx For a CHANGEACCESS request, the STOKEN for the
xx0137xx For a SHARE request, part of the source area is in a target area does not represent a valid space STOKEN.
hiperspace, VIO window, V=R region, or PSA.
xx0323xx For a CHANGEACCESS request, the beginning address
xx0138xx For a SHARE request, part of the target area is in a of the target area specified in the range is not aligned on
hiperspace, VIO window, V=R region, or PSA. a page-boundary.
xx0139xx For a SHARE request, the number of pages specified in xx0328xx For a CHANGEACCESS request, the caller does not
a range list entry is not valid. have access to the target area with the given ALET.
xx013Axx For a SHARE request, the specified source ALET xx0329xx For a CHANGEACCESS request, the caller does not
represents a subspace. have access to the target area with the given STOKEN.
xx013Bxx For a SHARE request, the specified target ALET repres- xx032Bxx For a CHANGEACCESS request, the address space
ents a subspace. that owns the target area is not swapped in.
xx013Dxx For a SHARE request, the specified target storage was xx032Cxx For a CHANGEACCESS request, the caller's PSW key
not obtained by the GETMAIN macro or STORAGE is insufficient for altering the target area.
macro with the OBTAIN parameter as part of the caller's
xx0330xx For a CHANGEACCESS request, the target area con-
pageable private region, or within the size of an existing
tains unacceptable pages, such as pages that are fixed
data space as pageable storage.
by PGSER or in permanent storage.
xx013Exx For a SHARE request, the specified source ALET is not
xx0331xx For a CHANGEACCESS request, the target area is not
valid. It is not on the current access list.
acceptable because it contains data that the caller
xx013Fxx For a SHARE request, the specified target ALET is not should not alter.
valid. It is not on the current access list.
xx0338xx For a CHANGEACCESS request, part of the target area
xx0140xx For a SHARE request, the source area contains is in a hiperspace window, a VIO window or V=R region,
HIDDEN pages. or in a PSA.
xx0141xx IARVSERV-SHARE failed. The source page is part of a xx0339xx For a CHANGEACCESS request, the number of pages
shared segment. specified in a range list is not valid.
xx0142xx IARVSERV-SHARE failed. The target page is part of a xx033Bxx For a CHANGEACCESS request, the specified target
shared segment. ALET represents a subspace.
xx0221xx For an UNSHARE request, the STOKEN for the target xx033Dxx For a CHANGEACCESS request, the storage was not
area does not represent a valid data space STOKEN. obtained using the GETMAIN or STORAGE OBTAIN
macro as part of the pageable private region of the call-
xx0223xx For an UNSHARE request, the beginning address of the
er's address space, nor within any existing data space.
target area specified in the range list entry is not page-
boundary aligned. xx033Fxx For a CHANGEACCESS request, the specified target
ALET is not valid.
xx0225xx For an UNSHARE request, the specified storage has not
been obtained with GETMAIN macro or STORAGE xx04xxxx For a xx04xxxx reason code please contact the IBM
macro with the OBTAIN parameter as part of the service center.
pageable private region of the caller's address space, or
xxFF10xx The caller held a lock other than the local lock.
within an existing data space.
xxFF11xx The input parameter list or range list is not accessible to
xx0228xx For an UNSHARE request, the caller does not have
the service using the caller's PSW key.
valid access to the address of the target area with the
given ALET. xxFF12xx The caller issued a macro version that is not valid.
xx0229xx For an UNSHARE request, the caller does not have xxFF13xx Reserved fields in the caller's macro parameter list are
valid access to the address of the target area with the not zeros.
given STOKEN. xxFF14xx The caller requested a service that is not valid.
xx022Bxx For an UNSHARE request, the address space that owns xxFF15xx The caller is not in 31-bit addressing mode.
the target is not swapped in.
xxFF16xx The range list entry count (NUMRANGE) is less than
xx022Cxx For an UNSHARE request, the caller's PSW key is insuf- one or greater than 16.
ficient for altering the target area.
Source: Real storage manager (RSM)
xx0231xx For an UNSHARE request, the target area contains
System Action: The system sends messages about the job to the
unacceptable pages, such as pages that are page-
job log, writes an ABEND dump for the failing job step, and writes
protected or page-fixed pages.
the JCL and SYSOUT output for the job.
System Completion Codes SCC-159
6C6 6FB
Programmer Response: Correct the program and run the job xxFF01xx The REFPAT macro request failed because the caller
again. was in cross-memory mode.
System Programmer Response: If the caller was provided by the xxFF02xx The REFPAT macro request failed because the caller
installation, correct it. Look at accompanying messages in the job held one or more locks needed by the system to process
log, the JCL and the SYSOUT output. the request.
If the caller was an IBM-supplied program, search problem reporting xxFF03xx The REFPAT macro request failed because a protection
data bases for a fix for the problem. If no fix exists, contact the IBM exception occurred while referencing the caller's param-
Support Center. Provide the messages, the JCL, the SYSOUT eter list.
output, and the ABEND dump.
xxFF04xx The REFPAT macro request failed because reserved
fields in the macro parameter list are not zeros.
6C6
xxFF05xx The REFPAT macro request failed because the caller
Explanation: To avoid data integrity problems, the subsystem requested an unknown service.
abnormally ends; one or more X'5C6' system completion codes will
xxFF06xx The REFPAT macro request failed because the caller
usually precede the end. During MQSeries abend, a user task with
must be in 31-bit addressing mode to use any service of
an active MQSeries connection can be abended with a X'6C6'
the REFPAT macro.
system completion code; in rare instances, the entire connected
address will be abended (MEMTERM). However, if the subsystem xxFF07xx The REFPAT macro request failed because the caller
ends an address space after numerous cancel attempts, this is not cannot be in SRB mode.
an MQSeries internal error. xxFF08xx The REFPAT macro request failed because the virtual
Source: MQSeries storage addresses specified on PSTART and PEND
straddle a common area boundary.
System Action: The subsystem abnormally ends MQSeries.
Source: Real storage manager (RSM)
Operator Response: Message CSQV086E should appear on your
console screen. First, copy this message and the accompanying sub- System Action: The system sends messages about the job to the
system end reason code. Second, notify the system programmer. job log, writes an ABEND dump for the failing job step, and writes
the JCL and SYSOUT output for the job.
Programmer Response: If the subsystem abnormally ends
MQSeries, then record the subsystem end reason code that is dis- Programmer Response: If the caller was an application program,
played in message CSQV086E. In addition, you should be aware of correct the program and run the job again.
the following situations. System Programmer Response: If the caller was provided by the
1. If you received any X'5C6' system completion codes prior to installation, correct it. Look at accompanying messages in the job
this subsystem end, perform the following actions. Check reg- log, the JCL and the SYSOUT output.
ister 15 of the SDWA section 'General Purpose Registers at If the caller was an IBM-supplied program, search problem reporting
Time of Error', and locate the accompanying reason code. In data bases for a fix for the problem. If no fix exists, contact the IBM
addition, check the information displayed at the console screen, Support Center. Provide the messages, the JCL, the SYSOUT
and in the corresponding logrec data set entry. output, and the ABEND dump.
2. If you did not receive any X'5C6' system completion codes
prior to the subsystem end, you will need an SVC dump, which 6FB
is entitled "MQSERIES SUBSYSTEM TERMINATION
Explanation:
REQUESTED - REASON=xxxxxxxx". The reason code in the
message and the one found in the MVS operator message will JES3 4.2.1 or prior level
be the same.
If you are at JES3 4.2.1 or a prior level of JES3, the following
System Programmer Response: If the error recurs and the information applies:
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 During JES3 processing, module IATSSCM, IATSSRN or IATSSRE
problem. If no fix exists, contact the IBM Support Center. Provide the detected an error related to the subsystem interface and issued this
SYSOUT output for the job and the logrec data set error record. system completion code. The error is identified by a hexadecimal
reason code in register 15.
6C7
Code Explanation
Explanation: During processing of a REFPAT macro, the system
10 IATSSRN - Module IATSSRN received a bad return
found a non-environmental error. The macro processing failed. Reg-
code from the JESXCF message reroute service
ister 15 contains a hexadecimal reason code.
(IXZXIXRR).
Code Explanation
Register 3 - Return Code from IXZXIXRR service
xx0005xx The INSTALL request failed because the caller does not
Register 4 - Reason Code from IXZXIXRR service
own the specified data space.
21 A bad SRB address was passed as input to the JES3
xx0006xx The INSTALL request failed because the caller specified
SRB reply exit routine (SSRECRXT) in module
a data space that does not exist.
IATSSRE.
xx0102xx The REMOVE request failed because the caller does not
22 A bad service request block (SRB) extension address
own the specified data space.
was passed as input to the JES3 SRB reply exit routine
xx0103xx The REMOVE request failed because the caller specified (SSRECRXT) in module IATSSRE.
a data space that does not exist.
SCC-160 OS/390 V2R8.0 MVS System Codes
6FB 6FB
23 The common area data space (CADS) buffer, provided 103 The JES3 subsystem communications service entrance
as input to the JES3 SRB reply exit routine list (SEL) passed into module IATSSCM had an incorrect
(SSRECRXT) in module IATSSRE, contained a bad length. This could be a result of a zero SELDATA
JESXCF acknowledgement message. The eye-catcher pointer or a length of zero or a length exceeding the
for the JESXCF acknowledgement message was not maximum staging area data size. This applies to all
correct. SSISERV service requests except TYPE=RESPONSE
request.
24 The CADS buffer, provided as input to the JES3 SRB
reply exit routine (SSRECRXT) in module IATSSRE, 104 Module IATSSCM encountered bad parameters specified
contained a bad staging area header. The eye-catcher for an SSISERV TYPE=WAIT request. One of the fol-
for the staging area header was not correct. lowing problems was found with the parameters:
25 The CADS buffer prefix, provided as input to the JES3 A response buffer was not specified. A response
SRB reply exit routine (SSRECRXT) in module buffer is required for SSISERV TYPE=WAIT.
IATSSRE, contained a bad response exit address. The
An EXIT address was specified. An exit address
response exit address must be non-zero.
must not be specified for SSISERV TYPE=WAIT.
26 The CADS buffer prefix, provided as input to the JES3
105 Module IATSSCM encountered bad parameters specified
SRB reply exit routine (SSRECRXT) in module
for an SSISERV TYPE=REPLY request. One of the fol-
IATSSRE, contained an incorrect buffer length. The
lowing problems was found with the parameters:
buffer length must be non-zero.
Both the ECB and EXIT address were specified.
27 The JESXCF Acknowledgement Message, passed as
Only one of these parameters can be specified.
input within the CADS buffer to the JES3 SRB reply exit
routine (SSRECRXT) in module IATSSRE, contained a A response buffer address was not specified for a
bad user return code. The user return code was non- request that did not specify an EXIT address. If a
zero. response buffer address is not specified, an EXIT
address must be specified.
28 The JES3 SRB reply exit routine (SSRECRXT) within
module IATSSRE attempted to obtain storage for the 106 Module IATSSCM was unable to find an entry in the
staging area buffer using the STORAGE service. The Main Processor Control table for the JESXCF member
attempt was unsuccessful and a non-zero return code that is to receive this request.
was returned from the STORAGE service. 110 Module IATSSCM attempted to obtain storage for a
31 The JES3 global status routine (SSRESTAT) in module memory data block (IATYMEM) using the STORAGE
IATSSRE invoked the IXZXIXIF service to obtain JES3 service. The attempt was unsuccessful and a non-zero
complex status information. The buffer returned by the return code was returned from the STORAGE service.
service contains a bad JESXCF member information Register 2 - Return Code from STORAGE service
record. The eye-catcher was not correct.
107 Module IATSSCM attempted to create a TTOKEN for the
32 The JES3 global status routine (SSRESTAT) in module current task using the TCBTOKEN service while proc-
IATSSRE was unable to find the global MPC entry within essing an SSISERV TYPE=REPLY request. The attempt
the main processor control table. was unsuccessful and a non-zero return code was
33 The JES3 global status routine (SSRESTAT) in module returned from the TCBTOKEN service.
IATSSRE attempted to obtain storage for the JESXCF Register 2 - Return Code from TCBTOKEN service
Information Record buffer (IXZXIXIF) via the STORAGE
111 Module IATSSCM attempted to release storage it had
service. The attempt was unsuccessful and a non-zero
obtained for a memory data block (IATYMEM) using the
return code was returned from the STORAGE service.
STORAGE service. The attempt was unsuccessful and a
34 The JES3 global status routine (SSRESTAT) in module non-zero return code was returned from the STORAGE
IATSSRE invoked the IXZXIXIF service to obtain JES3 service.
complex status information. The service was unsuc-
Register 2 - Return Code from STORAGE service
cessful and provided the SSRESTAT routine with a bad
return and/or reason code. 112 Module IATSSCM attempted to obtain a CADS buffer
using the JESXCF IXZXCADS service. The attempt was
Register 3 - Return Code
unsuccessful and a non-zero return code was returned
Register 4 - Reason Code from the IXZXCADS service.
35 The JES3 global status routine (SSRESTAT) in module Register 2 - Return Code from IXZXCADS service
IATSSRE invoked the IXZXIXIF service to obtain JES3
Register 3 - Reason Code from IXZXCADS service
complex status information. The JESXCF Information
Records returned by the service did not contain any 113 Module IATSSCM attempted to release a CADS buffer
information for the global processor. using the JESXCF IXZXCADS service. The attempt was
unsuccessful and a non-zero return code was returned
100 Module IATSSCM encountered a JES3 subsystem com-
from the IXZXCADS service.
munications service entrance list (SEL) which was
already in use by another caller. Register 2 - Return Code from IXZXCADS service
101 Module IATSSCM determined the caller was not author- Register 3 - Reason Code from IXZXCADS service
ized to issue the SSISERV service.
120 Module IATSSCM received a bad return code from the
102 Module IATSSCM encountered a bad memory data JESXCF acknowledge processed message service
block (MEMDATA) pointer. The eye-catcher for the (IXZXIXAC) while processing an SSISERV
MEMDATA header was not correct. TYPE=PURGE request.
System Completion Codes SCC-161
6FB 6FB
Register 2 - Return Code from IXZXIXAC service Check the JESYSMSG data set for error indications
Register 3 - Reason Code from IXZXIXAC service After gathering the necessary data, contact the IBM Support Center.
If an SVC dump was taken, provide the SVC dump, the reason code,
121 Module IATSSCM received a bad return code from the
and, if available, the data set error record.
JESXCF send message service (IXZXIXSM) while proc-
essing an SSISERV TYPE=WAIT request. JES3 4.2.1 or prior level
Register 2 - Return Code from IXZXIXSM service If you are at JES3 4.2.1 or a prior level of JES3, the following
Register 3 - Reason Code from IXZXIXSM service information applies:
122 Module IATSSCM received a non-zero user return code
Explanation: During JES3 processing, module IATSSCM or
from the response to a JESXCF send message service
IATSSRE detected an error and issued this system completion code.
(IXZXIXSM) request while processing an SSISERV
The error is identified by a hexadecimal reason code in the high-
TYPE=WAIT request.
order byte of register 15 and, for some reason codes, a hexadecimal
123 Module IATSSCM received a bad return code from the return code in the low-order byte of register 15.
JESXCF acknowledge processed message service
Code Explanation
(IXZXIXAC) while processing an SSISERV TYPE=WAIT
request. 00 The subsystem interface common service (SSICS)
routine detected an error in its calling parameters or in
Register 2 - Return Code from IXZXIXAC service
the system status. Return codes are:
Register 3 - Reason Code from IXZXIXAC service
X'18' The caller of SSICS is not in system pro-
124 Module IATSSCM received a bad return code from the tection key 0 through 7.
JESXCF send message service (IXZXIXSM) while proc-
X'1C' The SYSID parameter in a SSISERV macro
essing an SSISERV TYPE=REPLY request.
specified a processor that is not defined.
Register 2 - Return Code from IXZXIXSM service
X'20' An incorrect combination of the fields
Register 3 - Reason Code from IXZXIXSM service SELECBF, SELEXIT, SELBUFF was found
125 Module IATSSCM received a bad return code from the in the IATYSEL control block for a WAIT or
JESXCF send message service (IXZXIXSM) while proc- REPLY type SSISERV macro request.
essing an SSISERV TYPE=ACK request. X'24' An error occurred when the SSICS routine
Register 2 - Return Code from IXZXIXSM service attempted to write a staging area.
Register 3 - Reason Code from IXZXIXSM service X'28' The primary and all secondary staging area
extents have been exhausted.
126 Module IATSSCM received a bad return code from the
JESXCF send message service (IXZXIXSM) while proc- X'2C' The service entrance list (SEL) contained an
essing an SSISERV TYPE=COMM request. incorrect MEMDATA pointer.
Register 2 - Return Code from IXZXIXSM service X'30' The channel-to-channel (CTC) adaptor
address is incorrect.
Register 3 - Reason Code from IXZXIXSM service
X'34' An attempt was made to post a wait that
127 Module IATSSCM received a bad return code from the cannot be posted.
JESXCF acknowledge processed message service
(IXZXIXAC) while processing an SSISERV TYPE=RESP 01 The IATXBGM or IATXBFM macro passed an error
request. return code back to JES3 module IATSSCM:
Register 2 - Return Code from IXZXIXAC service X'08' A GETMAIN or FREEMAIN failed.
Register 3 - Reason Code from IXZXIXAC service 02 The MVS FREECELL macro passed an error return
code back to JES3 module IATSSCM:
128 Module IATSSCM received a zero response data
address from the JESXCF send message service X'04' The cell was not allocated from the subpool
(IXZXIXSM) while processing an SSISERV TYPE=WAIT indicated by the specified cell pool identifier.
request. X'08' The cell address is incorrect.
Register 2 - Return Code from IXZXIXSM service X'0C' FREECELL could not find the cell pool.
Register 3 - Reason Code from IXZXIXSM service X'10' The cell pool identifier is incorrect.
Source: JES3 03 The MVS BLDCPOOL macro passed an error return
System Action: The system writes the current address space code back to JES3 module IATSSCM:
along with the JES3 and JESXCF address spaces and related X'04' GETMAIN failed.
storage areas to a SYS1.DUMP data set. If the current address
X'08' The cell pool identifier is incorrect.
space is not the JES3 address space, the system abnormally ends
the current address space. X'0C' The specified subpool was not global.
System Programmer Response: Search problem reporting data X'10' The cell size was greater than the pool size.
bases for a fix for the problem. If no fix exists and the problem X'14' BLDCPOOL found a DELETE subpool in
occurred in JES3, you should: progress for the specified pool.
Save the hardcopy log 04 The MVS GETCELL macro passed an error return code
Provide a listing of the initialization deck (JES3OUT) back to JES3 module IATSSCM:
Provide a console log from initialization
SCC-162 OS/390 V2R8.0 MVS System Codes
6FC 6FC
X'04' GETCELL could not find any available cells. space. If the address space is the JES3 address space, the system
does not write a dump.
X'08' The chain pointers had been destroyed.
For reason code X'40', return code X'08', the system abnormally
X'0C' The cell pool format was incorrect.
ends the requesting task so that no user must wait for a response
X'10' The cell pool identifier is incorrect. that cannot be received.
05 The JES3 subsystem interface read-end module System Programmer Response: If the problem occurred in JES3
IATSSRE failed to obtain storage; the storage would you should:
have held a copy of a staging area destined for an func-
Save the MLOG listing or get a print of DLOG
tional subsystem (FSS) address space. The three low-
Provide a listing of the initialization deck (JES3OUT)
order bytes of register 15 contain the return code from
Provide a console log from initialization
the MVS GETMAIN macro.
Check the JESYSMSG data set for error indications
06 The JES3 subsystem interface read-end module
IATSSRE could not find the FSID in the staging area;
6FC
the FSID identifies the dynamic destination queue
(DESTQ) for which the staging area is intended. Explanation: During processing following a program check inter-
ruption, the system detected an error in a SPIE or ESPIE macro.
07 The JES3 subsystem interface read-end module
The SDWACRC field of the system diagnostic work area (SDWA)
IATSSRE could not find the proper control block struc-
contains a hexadecimal reason code to be used when searching
ture required for queuing the staging area in an FSS
problem reporting data bases or when reporting the problem to the
address space.
IBM Support Center.
11 A JES3 routine issued the IATXSSXM macro to call a
Code Explanation
specific routine in module IATSSXM. IATSSXM returns
in the low-order byte of register 15 the ECODE param- 04 The user's PICA contains an invalid bit setting in the
eter value from the IATXSSXM macro. OS/390 JES3 program mask.
Customization describes the IATXSSXM macro. 08 The user's PICA is unavailable.
13 The system abnormally ended JES3 during staging area 12 The SCA, pointed to by the TCBPIE, is unavailable.
initialization.
16 The RPP, pointed to by the SCARPPTR, is unavailable.
14 The system abnormally ended JES3 during processing
to move a staging area to make it a dedicated staging 20 The PIE, pointed to by the SCAPIE or SCAPPIE, is una-
area. vailable.
15 The system abnormally ended the processing following 24 The SCA, pointed to by the TCBPIE, is unavailable.
an end of memory (EOM) or an end of task (EOT) call. 28 The RPP, pointed to by the SCARPPTR, is unavailable.
16 The system abnormally ended FREEMAIN processing of 32 The PIE, pointed to by the SCAPIE or SCAPPIE, is una-
the staging area wait queue (SAW Q). vailable.
17 The system abnormally ended FREEMAIN processing of 36 Unable to reference SPIE/ESPIE control blocks or an
the staging area pending queue (SAP Q). error occurred while handling a SPIE/ESPIE exit.
18 The system abnormally ended an attempt to page-fix the Source: Supervisor control
staging area pending queue (SAP Q).
System Action: The system abnormally ends the task that experi-
19 The system abnormally ended copying of the staging enced the program check. The system may write a logrec data set
area pending queue (SAP Q) from JES3 auxiliary error record.
storage to the common service area (CSA).
Operator Response: If the system programmer asks for an SVC
1A Module IATSSCM detected an error, which may have dump, set the following SLIP trap:
caused another ABEND, during GETCELL processing SLIP SET,COMP=6FC,ACTION=SVCD,END
for JES3 auxiliary storage.
Programmer Response: Resubmit the job. If the error recurs,
1B Module IATSSCM detected an error during validation of contact the system programmer.
a staging area queue.
System Programmer Response: Search problem reporting data
40 Module IATSSRE detected an error: bases for a fix for the problem. If no fix exists, ask the operator to
X'04' The passed staging area was not found on set a SLIP trap to obtain an SVC dump. Contact the IBM Support
the staging area pending (SAP) queue. Center. Provide the SVC dump, the reason code, and, if available,
the logrec data set error record.
X'08' IATSSRE failed while processing a wait or
reply request. The module produces a dump
that indicates the failure IATSSRE encount-
ered. 700
The passed staging area was not found on Explanation: During processing of an I/O request, a program check
the GETMAINED staging area (SAG) queue. occurred in a supervisor service routine called by the execute
channel program (EXCP).
Source: JES3
Source: Execute channel program (EXCP)
System Action: The system writes the common service area
(CSA), system queue area (SQA), and the MVS trace table to a System Action: The system abnormally ends the current task. The
SYS1.DUMP data set and abnormally ends the current address system writes a logrec data set error record.
Programmer Response: Check the problem program for the error.
System Completion Codes SCC-163
702 705
If the error cannot be determined, run the job again, requesting an Module ID Module Name
ABEND dump. Notify the system programmer.
1 IGGVVSMRT
System Programmer Response: In the ABEND dump, look at field
3 IGVVSM24
TCBEXCPD at offset X'C0' in the task control block (TCB) for the
current task. TCBEXCP points to the EXCP debugging area (XDBA). 4 IGVVSM31
The XDBA contains diagnostic data associated with the EXCP 6 IGVGSQA
processor.
7 IGVFSQA
Look for the problem in one of the service routines used by EXCP. If
A IGVGLSQA
the error recurs and the program is not in error, look at the mes-
sages in the job log for more information. B IGVFLSQA
Search problem reporting data bases for a fix for the problem. If no C IGVGAPVT
fix exists, contact the IBM Support Center. Provide the logrec data
E IGVFSP
set error record and the source program listing for the job.
44 IGVVSMRF
702 Code Explanation
Explanation: During processing of a POST macro, the system 01 While processing the GETMAIN request, the
found either incorrect input data or an unauthorized POST exit system tried to release central storage backing
routine request. global or local system queue area (SQA or
LSQA) storage. A program page fixed the virtual
Register 15 contains a hexadecimal reason code that explains the
storage. However, it is a basic property of the
error:
system that SQA and LSQA storage is page
Code Explanation fixed.
00 A function request was incorrect. 04 Status information indicates that the system has
04 The address is incorrect for an exit routine for a obtained a global lock to support the GETMAIN
CREATE or DELETE request. request. However, when the system attempted to
release the lock, the release request failed.
08 During an attempt to post an extended event control
block (ECB), the descriptor word of the ECB extension 08 A system service routine returned an incorrect
contained incorrect data. return code to the virtual storage manager (VSM)
interface module.
0C During an attempt to post an extended ECB, the ECB
extension contained an incorrect exit routine address. 09 While getting or freeing storage in a local or
global SQA subpool, the service routine that
10 A POST exit routine attempted to post an extended builds double free elements (DFE) tried to place
ECB. virtual storage on the DFE queue, but could not
14 During an attempt to post an extended ECB, either the do so because the storage was described by
ECB address or ECB extension address was incorrect. another DFE already on the queue.
18 Without use of the local lock for serialization, the ECB 10 While in recovery processing, the system
has been updated from an initialized extended state to a detected a condition that is normally considered
waited state. a user error, such as an error in the parameter
list. However, it is likely that the error is not a
Source: Task management
user error because recovery processing is in
System Action: The system abnormally ends the program that control.
issued the POST macro.
Source: Virtual storage manager (VSM)
Programmer Response: This code is only associated with
System Action: The system writes a logrec data set error record.
extended ECB processing. If an extended ECB was being posted,
The system continues processing.
ensure that it contains valid data. Then correct the error identified by
the return code. Run the job again. Programmer Response: Run the job again. If the error recurs,
contact the system programmer.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more System Programmer Response: Search problem reporting data
information. Search problem reporting data bases for a fix for the bases for a fix for the problem. If no fix exists, contact the IBM
problem. If no fix exists, contact the IBM Support Center. Provide the Support Center.
source program listing for the job.
705
704 Explanation: A system error, uncorrectable machine error, or error
Explanation: A system error, uncorrectable machine error, or error that cannot be determined occurred when the system tried to
that cannot be determined occurred when the system tried to process an EC, EU, LC, LU, VC, or VU form of the FREEMAIN
process an EC, EU, LC, LU, VC, or VU form of the GETMAIN macro. A reason code in the SDWACRC field of the system diag-
macro. A reason code in the SDWACRC field of the system diag- nostic work area (SDWA) explains the error:
nostic work area (SDWA) explains the error: Note: Some VSM return codes may be a half-word in length. In
Note: Some VSM return codes may be a half-word in length. In these cases, the high-order byte is the module id of the
these cases, the high-order byte is the module id of the issuing module, and the low-order byte is the return code.
issuing module, and the low-order byte is the return code.
SCC-164 OS/390 V2R8.0 MVS System Codes
706 70A
Module ID Module Name
706
1 IGGVVSMRT
Explanation: The error occurred during processing of a LINK(X),
3 IGVVSM24 XCTL(X), ATTACH(X), or LOAD macro.
4 IGVVSM31 The requested load module was marked not executable.
6 IGVGSQA Source: Contents supervision (CSV)
7 IGVFSQA System Action: The task is ended unless ERRET is specified on
A IGVGLSQA the macro.
B IGVFLSQA The system issues message CSV016I and an ABEND dump.
C IGVGAPVT Programmer Response: Ensure that the target load module is
executable and the linkage editor did not find errors in the module.
E IGVFSP Have the module edited by the linkage editor again. Then recompile,
44 IGVVSMRF and run the job step again.
Code Explanation System Programmer Response: If the error recurs and the
program is not in error, see the system programmer response for the
01 While processing the FREEMAIN request, the
messages in the job log.
system tried to release central storage backing
global or local system queue area (SQA or If the problem persists, search problem reporting data bases for a fix
LSQA) storage. A program page fixed the virtual for the problem. If no fix exists, contact the IBM Support Center.
storage. However, it is a basic property of the Provide the ABEND dump and the source program listing for the job.
system that SQA and LSQA storage is page
fixed. 70A
02 While processing a subpool FREEMAIN of a Explanation: A system error, uncorrectable machine error, or error
local system queue area subpool, a service that cannot be determined, occurred when the system tried to
routine was called to free storage described by process an R form of the GETMAIN or FREEMAIN macro. A reason
an allocated element (AE). The service routine code in the SDWACRC field of the system diagnostic work area
returned a return code indicating that the storage (SDWA) explains the error:
is not described by an AE.
Note: Some VSM return codes may be a half-word in length. In
04 Status information indicates that the system has these cases, the high-order byte is the module id of the
obtained a global lock in support of the issuing module, and the low-order byte is the return code.
FREEMAIN request. However, when the system
attempted to release the lock, the release Module ID Module Name
request failed. 1 IGGVVSMRT
09 While getting or freeing storage in a local or 3 IGVVSM24
global system queue area subpool, the service
4 IGVVSM31
routine that builds double free elements (DFE)
tried to place virtual storage on the DFE queue, 6 IGVGSQA
but could not do so because the storage was 7 IGVFSQA
described by another DFE already on the queue.
A IGVGLSQA
0C A FREEMAIN service routine returned an incor-
rect return code to the virtual storage manager B IGVFLSQA
(VSM) interface module. C IGVGAPVT
10 While in recovery processing, the system E IGVFSP
detected a condition that is normally considered
44 IGVVSMRF
a user error, such as an error in the parameter
list. However, the error is most likely not a user Code Explanation
error because recovery processing is in control. 01 While processing the FREEMAIN request, the
Source: Virtual storage manager (VSM) system tried to release central storage backing
global or local system queue area (SQA or
System Action: The system writes a logrec data set error record.
LSQA) storage. A program page fixed the virtual
The system continues processing.
storage. However, it is a basic property of the
Programmer Response: Run the job again. If the error recurs, system that SQA and LSQA storage is page
contact the system programmer. fixed.
System Programmer Response: Search problem reporting data 02 While processing a subpool FREEMAIN of a
bases for a fix for the problem. If no fix exists, contact the IBM local system queue area subpool, a service
Support Center. routine was called to free storage described by
an allocated element (AE). The service routine
returned a return code indicating that the storage
is not described by an AE.
04 Status information indicates that the system has
obtained a global lock in support of the
FREEMAIN request. However, when the system
System Completion Codes SCC-165
70D 717
attempted to release the lock, the release Register 14 at the time of error
request failed.
The RCVY entry for the ABTERM request in the system trace.
08 A GETMAIN storage management service
Analyze the dump to identify the module issuing the CALLRTM
routine returned an incorrect return code to the
TYPE=ABTERM macro:
virtual storage manager (VSM) interface module.
For an installation-provided module, correct the program to
09 While getting or freeing storage in a local or
obtain the correct serialization.
global system queue area subpool, the service
routine that builds double free elements (DFE) For an IBM-provided module, search problem reporting data
tried to place virtual storage on the DFE queue, bases for a fix for the problem. If no fix exists, contact the IBM
but could not do so because the storage was Support Center. Provide problem data collected.
described by another DFE already on the queue.
0C A FREEMAIN storage management service 713
routine returned an incorrect return code to the Explanation: The error occurred during processing of an OPEN
virtual storage manager (VSM) interface module. macro instruction for a data set on magnetic tape or on a direct
10 While in recovery processing, the system access device. This system completion code is accompanied by
detected a condition that is normally considered message IEC148I. Refer to the explanation of message IEC148I for
a user error, such as an error in the parameter complete information about the task that was ended and for an
list. However, the error is most likely not a user explanation of the return code (rc in the message text) in register 15.
error because recovery processing is in control. Source: DFSMSdfp
Source: Virtual storage manager (VSM) Programmer Response: Respond as indicated for message
System Action: The system writes a logrec data set error record. IEC148I.
The system continues processing. System Programmer Response: If the error recurs and the
Programmer Response: Run the job again. If the error recurs, program is not in error, look at the messages in the job log for more
contact the system programmer. information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
System Programmer Response: Search problem reporting data JCL and the program listing for the job.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
714
70D Explanation: The error occurred during processing of a CLOSE
macro instruction for a data set on magnetic tape. This system com-
Explanation: A program issued a CALLRTM TYPE=ABTERM pletion code is accompanied by message IEC215I. Refer to the
macro. In response, the recovery termination manager (RTM) was explanation of message IEC215I for complete information about the
validating entry into RTM1. RTM determined that the entry mode task that was ended and for an explanation of the return code (rc in
requirements were not met. the message text) in register 15.
A hexadecimal reason code in the following explains the error: Source: DFSMSdfp
Field RTM2CRC of the RTM2 work area (RTM2WA) Programmer Response: Respond as indicated for message
Message IEA995I IEC215I.
TCBARC field of the task control block (TCB)
System Programmer Response: If the error recurs and the
Code Explanation program is not in error, look at the messages in the job log for more
04 A program that is not disabled issued the CALLRTM information. Search problem reporting data bases for a fix for the
macro with TYPE=ABTERM,TCB=0 or problem. If no fix exists, contact the IBM Support Center. Provide the
TYPE=ABTERM,TCB=(the current TCB). JCL and the program listing for the job.
08 A program that does not hold the local lock issued the
CALLRTM TYPE=ABTERM macro specifying the 717
address of a task control block (TCB) that is not current. Explanation: The error occurred during processing of a BSAM
0C RTM1 was entered through CVTBTERM, but without the CLOSE macro instruction with a TYPE=T operand for a data set on
local lock. magnetic tape. This system completion code is accompanied by
message IEC222I. Refer to the explanation of message IEC222I for
Source: Recovery termination manager (RTM) complete information about the task that was ended and for an
System Action: RTM abnormally ends the program that issued the explanation of the return code (rc in the message text) in register 15.
CALLRTM TYPE=ABTERM macro. If the caller requested ending of Source: DFSMSdfp
another task, RTM also ends that task using the abend code and
reason code supplied by the caller. Programmer Response: Respond as indicated for message
IEC222I.
The system issues message IEA995I. The system may write an SVC
dump. System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
Operator Response: If RTM did not write a dump and the system information. Search problem reporting data bases for a fix for the
programmer asks for an SVC dump, set the following SLIP trap: problem. If no fix exists, contact the IBM Support Center. Provide the
SLIP SET,COMP=7ðD,ACTION=SVCD,END JCL and the program listing for the job.
System Programmer Response: The return address of the issuer
of the CALLRTM TYPE=ABTERM macro is in:
SCC-166 OS/390 V2R8.0 MVS System Codes
71A 738
Programmer Response: This is probably an error in the program.
71A
Correct the error indicated by the reason code by changing the
Explanation: This system completion code is used to end a catalog ATTACH macro or the environment in which the macro runs. Run
address space service task when (1) the catalog address space is the job again.
ending and restarting or (2) an abend has already occurred in a user
System Programmer Response: If the error recurs and the
address space during catalog processing. System completion code
program is not in error, look at the messages in the job log for more
71A is intended for catalog internal communication only, and no
information. Search problem reporting data bases for a fix for the
further diagnosis is necessary.
problem. If no fix exists, contact the IBM Support Center.
Source: DFSMSdfp
System Action: None. 730
Explanation: Global resource serialization encountered an unex-
722 pected error occurred during the processing of a DEQ macro.
Explanation: One of the following output limits was exceeded: Source: Global resource serialization
The output limit specified by the OUTLIM keyword on the System Action: The system writes a logrec data set error record.
SYSOUT DD statement The system issues an ABEND dump.
The job output limit specified in the LINES and CARDS parame- Programmer Response: Do the following:
ters of the JES2 JOBPARM statement
1. Obtain the address of the ENQ parameter list from register 1 in
The job output limit specified in the BYTES, CARDS, LINES, the UNIQUE-3 column of the SVC 30 or SVC 38 entry in the
and PAGES parameters on the STANDARDS initialization state- system trace.
ment or the JES3 MAIN statement
2. Check the parameter list against the SVC 30 or 38 mapping.
Source: JES When analyzing the parameter list, remember that the unit
System Action: The system ends processing of the job step. control block (UCB) pointer, if present, is the address of a field
that, in turn, contains the address of the UCB.
Programmer Response: Check for input/output (I/O) loops. Verify
that the parameter value does not conflict with any installation If the parameter list contains incorrect data, continue diagnosis
requirements. If no errors are found, increase the value in the state- in the program that issued the macro.
ment. Then run the job again. System Programmer Response: If the problem persists, search
problem reporting data bases for a fix for the problem. If no fix
72A exists, contact the IBM Support Center. Provide the ABEND dump.
Explanation: During processing for an ATTACH macro, the system
encountered an error. 737
Register 15 contains a hexadecimal reason code that explains the Explanation: The error occurred at an end-of-volume or during allo-
error: cation of a secondary quantity of direct access storage as requested
in the SPACE parameter of the DD statement for the data set. This
Code Explanation system completion code is accompanied by message IEC027I. Refer
00 The system found an incorrect parameter address when to the explanation of message IEC027I for complete information
processing the ATTACH parameter list. about the task that was ended and for an explanation of the return
code (rc in the message text) in register 15.
04 An end-of-task exit routine (ETXR) address is incorrect
because both of the following situations exist: Source: DFSMSdfp
The ETXR is already in effect as an ETXR for a Programmer Response: Respond as indicated for message
subtask of the task IEC027I.
The current ATTACH was issued in a different System Programmer Response: If the data set does exist on the
addressing mode than the ATTACH that created the specified volumes and the problem recurs, look at the messages in
matching ETXR the job log for more information. Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
08 The length of the ATTACH parameter list is incorrect.
Support Center. Provide the JCL and the program listing for the job.
0C The format number of the parameter list is incorrect.
10 A caller using the ATTACHX macro encountered 738
nonzero access list entry tokens (ALETs). The ALETs Explanation: Global resource serialization encountered an unex-
should have been set to zero, but they were not. pected error during the processing of an ENQ macro instruction.
14 A caller in access register ASC mode used the ATTACH This abend may occur when there are ENQs on resources during a
macro instead of the ATTACHX macro. resource name list (RNL) change if the number of jobs suspended
18 An unauthorized caller issued ATTACH or ATTACHX due to the RNL change exceeds 12,000 on a system. When the
with the DISP=RESET parameter. The caller must be number reaches 8000 the system cancels the RNL change.
authorized. Reason code X'000000FF' is issued when the system deter-
Source: Task management mined that RESERVE requests on a specific shared device had
exceeded the limit.
System Action: The system abnormally ends the program that
issued the ATTACH macro. The system does not create the new Reason code X'00010001' is issued when the I/O scheduled to
subtask. RESERVE a device has failed.
System Completion Codes SCC-167
744 778
Reason code X'00010002' is issued when RESERVE start
76D
processing has failed.
Explanation: The system found an error while processing an
Reason code X'00010003' is issued when RESERVE done
OUTADD or OUTDEL macro.
processing has failed.
Source: Dynamic output
Source: Global resource serialization
System Action: The system does the following:
System Action: The system writes a logrec data set error record
and an ABEND dump. If RESERVE requests on a shared device had The system writes a logrec data set error record.
exceeded the limit, the system ends the task that issued the The system writes an SVC dump.
RESERVE with abend X'738' and reason code X'000000FF'.
The system abnormally ends the program that issued the macro,
Programmer Response: Do the following: or returns to the macro caller with a return code of X'10'.
1. Obtain the address of the DEQ parameter list from register 1 in Programmer Response: Check for incorrect input parameters
the UNIQUE-3 column of the SVC 30 or SVC 38 entry in the passed to the OUTADD or OUTDEL macro. Submit the job again.
system trace.
System Programmer Response: If the problem persists, search
2. Check the parameter list against the SVC 30 or 38 mapping. problem reporting data bases for a fix for the problem. If no fix
When analyzing the parameter list, remember that the unit exists, contact the IBM Support Center.
control block (UCB) pointer, if present, is the address of a field
that, in turn, contains the address of the UCB.
778
If the parameter list contains incorrect data, continue diagnosis
in the program that issued the macro. Explanation: A system error, uncorrectable machine error, or error
that cannot be determined occurred under one of the following
3. If abend X'738' and reason code X'000000FF', none. conditions:
System Programmer Response: If the problem persists, search While the system was attempting to satisfy a request made
problem reporting data bases for a fix for the problem. If no fix through the STORAGE macro
exists, contact the IBM Support Center. provide the logrec data set
error record and the ABEND dump. If abend X'738' with reason While the system was trying to process an RC, RU, VRC, or
code X'000000FF' persists, issue D GRS,DEV=xxxx (xxxx is the VRU form GETMAIN macro
device number in hexadecimal) command to determine what are the While the system was trying to process an RC or RU form
reserve requests on the device. FREEMAIN macro
A reason code in the SDWACRC field of the system diagnostic work
744 area (SDWA) explains the error:
Explanation: A program check occurred during the processing of Note: Some VSM return codes may be a half-word in length. In
SYNADAF or SYNADRLS. This error could not be attributed to incor- these cases, the high-order byte is the module id of the
rect user input. issuing module, and the low-order byte is the return code.
Source: DFSMSdfp Module ID Module Name
System Action: The SYNADAF recovery routine tried to take a 1 IGGVVSMRT
dump of LSQA and the user's region. The dump header includes the
3 IGVVSM24
job name, step name, and procedure step name. See message
IEC907I to determine whether the dump attempt was successful. A 4 IGVVSM31
software error record was written to the logrec data set. 6 IGVGSQA
Programmer Response: Rerun the job step. 7 IGVFSQA
System Programmer Response: If the error recurs and the A IGVGLSQA
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 B IGVFLSQA
problem. If no fix exists, contact the IBM Support Center. Provide the C IGVGAPVT
JCL, the program listing for the job, and the logrec data set error
E IGVFSP
record.
44 IGVVSMRF
75F Code Explanation
Explanation: The system resources manager (SRM) detected that 01 While attempting to free storage, the system tried
the system timer queue element (TQE) exceeded the expected to release central storage backing global or local
interval. system queue area (SQA or LSQA) storage. A
Source: System resources manager (SRM) program page fixed the virtual storage. However,
it is a basic property of the system that SQA and
System Action: SRM performs normal TQE expiration processing LSQA storage is page fixed.
and requeues the TQE. The system abnormally ends the current
task. The system writes messages and a logrec data set error 02 While attempting to release an entire LSQA
record. subpool, a service routine was called to free
storage described by an allocated element (AE).
System Programmer Response: Search problem reporting data The service routine returned a return code indi-
bases for a fix for the problem. If no fix exists, contact the IBM cating that the storage is not described by an
Support Center. Provide the logrec data set error record. AE.
SCC-168 OS/390 V2R8.0 MVS System Codes
77D 7C6
04 Status information indicates that the system has problem. If no fix exists, contact the IBM Support Center. Provide the
obtained a global lock in support of a request to assembly listing for the job.
release storage. However, when the system
attempted to release the lock, the release 7C4
request failed.
Explanation: JES3 encountered an error when calling a JESXCF
08 While attempting to obtain storage, a storage console-related function. The abend reason code identifies the spe-
management service routine returned an incor- cific error.
rect return code to the virtual storage manager
(VSM) interface module. Code Explanation
09 While getting or freeing storage in a local or 01 IATXCSIF SERVICE=XAUTH was passed a bad param-
global system queue area subpool, the service eter list (service routine IATCS01). Analyze the param-
routine that builds double free elements (DFE) eter list to determine the problem.
tried to place virtual storage on the DFE queue, 03 IATXCSIF SERVICE=CONSTYPE was passed a bad
but could not do so because the storage was parameter list (service routine IATCS03). Analyze the
described by another DFE already on the queue. parameter list to determine the problem.
0C While attempting to free storage, a storage man- 04 During JES3 initialization processing, module IATINC2
agement service routine returned an incorrect detected an error while invoking an IXZXCNSV order. An
return code to the virtual storage manager (VSM) IXZXCNSV ORDER(START) returned with a bad return
interface module. code. The return and reason code for the IXZXCNSV
10 While in recovery processing, the system macro invocation is within the IXZXCNSV parameter list.
detected a condition that is normally considered The parameter list is contained within the automatic area
a user error. However, it is not likely that the of IATCS04. The automatic area is pointed to by general
error is a user error because recovery processing register 8 at the time of failure. Use the return and
is in control. reason codes to determine why JESXCF failed to
process the START order successfully.
14 VSM failed to backout the acquisition of a new
address queue anchor table (AQAT) stack. In 05 During JES3 initialization processing, module IATINC2
this case, the system issues abend X'778' only detected an error while invoking an IXZXCNSV order. An
to record the error. The system continues proc- IXZXCNSV ORDER(SYNCPT) returned with a bad
essing upon retry from VSM recovery. return code. The return and reason code for the
IXZXCNSV macro invocation is within the IXZXCNSV
20 The STORAGE service routine has failed parameter list. The parameter list is contained within the
unexpectedly. The failure is probably not a user automatic area of IATCS04. The automatic area is
error. pointed to by general register 8 at the time of failure.
Source: Virtual storage manager (VSM) Use the return and reason codes to determine why
JESXCF failed to process the SYNCPT order success-
System Action: The system writes a logrec data set error record.
fully.
The system continues processing.
Source: JES3
Programmer Response: Run the job again. If the error recurs,
contact the system programmer. System Action: For reason codes X'01' and X'03', varies with
invoking function. For reason codes X'04' and X'05', JES3 initial-
System Programmer Response: Search problem reporting data
ization is terminated.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. System Programmer Response: To determine the error, refer to
reason code descriptions.
77D
7C6
Explanation: During processing of an EVENTS macro, the system
found an error in the macro input parameters. Explanation: The system encountered an error while processing
the UCBPIN macro with the UNPIN option. A hexadecimal reason
Register 15 contains a hexadecimal reason code that explains the
code in register 15 explains the error:
error:
Code Explanation
Code Explanation
01 The PTOKEN supplied as input on the UCBPIN macro
04 A caller issued an incompatible level of the EVENTS
request contains incorrect data.
macro.
02 The PTOKEN supplied as input on the UCBPIN macro
08 Both WAIT=YES and WAIT=NO were specified.
request contains non-addressable data.
Source: Task management
Source: Input/output supervisor (IOS)
System Action: The system abnormally ends the program that
System Action: The system abnormally ends the task, unless a
issued the EVENTS macro.
recovery routine was provided to handle the interruption.
Programmer Response: Verify the EVENTS macro input parame-
Programmer Response: Check your programs for one of the fol-
ters, the level of the macro, and the contents of register 0. Correct
lowing possible scenarios causing the abend:
the error. Run the job again.
A task does the following:
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 1. Pins a unit control block (UCB) without specifying the
information. Search problem reporting data bases for a fix for the LASTING parameter on the UCBPIN macro.
System Completion Codes SCC-169
7C7 7FB
2. Schedules a service request block (SRB) to unpin the UCB. 3 An error occurred during page-fix or page-unfix proc-
essing. A page-fix error can occur if the EXCP processor
Because the program did not specify LASTING on the UCBPIN
tries to fix pages that are not assigned to the caller's
macro, the task ends before the SRB is dispatched. When the
address space identifier (ASID).
task ends, the system unpins the UCB. When the SRB subse-
quently tries to unpin the same UCB, the system issues this 4 A program issued SVC 114, the EXCPVR macro, but an
abend. error occurred during page-fix or page-unfix processing.
A page-fix error can occur if the EXCP processor tries to
The PTOKEN specified on the UCBPIN macro is overlaid or
fix pages that are not assigned to the caller's ASID.
altered by the application program.
Source: Execute channel program (EXCP)
7C7 System Action: The system abnormally ends the current task. The
Explanation: The batch local shared resources (LSR) subsystem system writes a logrec data set error record and issues a SNAP
encountered an unexpected error. Register 15 contains diagnostic dump. If the job's JCL concatenates data sets with unequal
information in the format X‘mm0002rr’. The mm field identifies the blocksizes, the system abnormally ends the job with system com-
issuing module; the 02 identifies the batch LSR subcomponent of the pletion code X'171', which in turn causes system completion code
callable service request (CSR) component. rr is the reason code X'800'.
associated with the abend. Programmer Response: Correct the problem that the reason code
Source: Callable Service Requests (CSR) indicates.
System Action: The subsystem schedules an SVC dump, and If the job concatenated data sets with unequal blocksizes, change
does not perform the request. the JCL. Otherwise, check the problem program for the error.
Operator Response: Report the problem to the system pro- If you get reason code 3 or 4, or if the error cannot be determined,
grammer. run the job again, requesting an ABEND dump. Notify the system
programmer.
System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM System Programmer Response: In the dump, look at field
Support Center. Report the diagnostic information in register 15. TCBEXCPD at offset X'C0' in the task control block (TCB) for the
current task. TCBEXCPD points to the EXCP debugging area
(XDBA). The XDBA contains diagnostic data associated with the
7FB
EXCP processor.
Explanation: An uncorrectable error occurred while one of the
If the error recurs and the program is not in error, look at the mes-
MVS-JES3 dynamic device reconfiguration (DDR) subsystem inter-
sages in the job log for more information. Search problem reporting
face (SSI) routines was running.
data bases for a fix for the problem. If no fix exists, contact the IBM
Source: Dynamic device reconfiguration (DDR) Support Center. Provide the logrec data set error record, the JCL for
System Action: The system ends the reconfiguration. the job, and the SNAP dump.
Operator Response: If you initiated the reconfiguration, retry it. If
804
the system initiated the reconfiguration, notify the system pro-
grammer. Explanation: An error occurred when the system tried to process
an EC, EU, LC, LU, VC, or VU form of the GETMAIN macro. A
System Programmer Response: Search problem reporting data
reason code in the SDWACRC field of the system diagnostic work
bases for a fix for the problem. If no fix exists, contact the IBM
area (SDWA) explains the error:
Support Center.
Code Explanation
04 There is not enough virtual system queue area (SQA)
800 storage available to satisfy the request.
Explanation: During processing of an I/O request, execute channel 08 There is not enough virtual common service area (CSA)
program (EXCP) processing encountered an error. Each X'800' storage available to satisfy the request.
abend code has a reason code that explains the error:
0C There is not enough virtual local system queue area
Code Explanation (LSQA) storage available to satisfy the request.
1 An error occurred during indirect address word (IDAW) 10 There is not enough virtual private area storage avail-
or channel command word (CCW) validity check proc- able to satisfy the request.
essing. An access protection error occurred when:
Note: This error can occur if an installation exit is
The EXCP IDAW routine tried to access the IDAW requesting virtual storage from a V=R region
using an incorrect storage protection key. before the system completely initializes the
The EXCP CCW validity check routine tried to region.
access the virtual channel program using an incor-
14 A negative amount of storage was specified on the
rect storage protection key.
GETMAIN.
The channel program attempted to execute a
restricted operation. An access protection error can Note: If this error is detected, the calling program
occur when there is an error in the channel abnormally ends even though RC, EC, LC, or VC
program. Correct the channel program. is specified for GETMAIN, or COND=YES is
specified for STORAGE.
2 System error. Contact the IBM Support Center.
SCC-170 OS/390 V2R8.0 MVS System Codes
805 806
1C During request processing, the system tried to get LSQA 0C The supervisor attempted to search a library for the
virtual storage for virtual storage management's (VSM) program that the EP or EPLOC operand specifies and
cell pool. There was not enough LSQA virtual storage found that the library data control block (DCB) is not
available. open.
20 There is not enough virtual storage in the LSQA to build 10 A program issued a LOAD macro with the explicit load
a new address queue anchor table (AQAT) stack. option, but there is no DCB parameter. For explicit
loads, the program must supply the DCB parameter with
Source: Virtual storage management (VSM)
the macro because the system searches for the module
System Action: The system issues message IEA705I. The system that the LOAD specifies only in the library that the DCB
abnormally ends the current task. parameter specifies.
Programmer Response: Check for program errors that incorrectly 14 The system could not find the module, whose entry point
modify the macro expansion. Correct them. If necessary, change the is the value of an EP or EPLOC operand of a XCTL(X)
program to request less virtual storage. macro, in the link pack area (LPA), which is where the
module must be when the module is requested by an
805 SVC routine.
Explanation: An error occurred when the system tried to process 18 An SVC routine issued a XCTL(X) macro for a module.
an EC, EU, LC, LU, VC, or VU form of the FREEMAIN macro. A The system tried to search the link pack area directory
reason code in the SDWACRC field of the system diagnostic work to find the module, but the directory had not as yet been
area (SDWA) explains the error: built.
Code Explanation 1C The data control block (DCB), included as part of a
LINK(X), LOAD, XCTL(X), or ATTACH(X) macro is incor-
18 A negative amount of storage was specified on the
rect.
FREEMAIN macro.
2C Internal error.
Note: If this error is detected, the calling program
abnormally ends even though RC, EC, LC, or VC Source: Contents supervision (CSV)
is specified for FREEMAIN. System Action: The system issues a message depending on the
1C During request processing, the system tried to get local reason code accompanying the abend:
system queue area (LSQA) virtual storage for virtual Code Message
storage management's (VSM) cell pool. There was not
enough LSQA virtual storage available. 04 CSV003I
20 There is not enough virtual storage in the LSQA to build 08 CSV004I
a new address queue anchor table (AQAT) stack. 0C CSV005I
Source: Virtual storage management (VSM) 10 CSV007I
System Action: The system issues message IEA705I. The system 14 CSV008I
abnormally ends the current task.
18 CSV006I
Programmer Response: Check for program errors that incorrectly
1C CSV021I
modify the macro expansion. Correct them. If necessary, change the
program to request less virtual storage. The system issues an ABEND dump.
Programmer Response: If the reason code is X'04', this is prob-
806 ably a user error. Make sure that the requesting program was not
Explanation: The supervisor, or the Supervisor Call (SVC) for the incorrectly modified. Make sure that the source library was indicated
BLDL (build a directory entry list) macro, detected an error during the correctly and that the indicated library does contain the requested
processing of a LINK(X), XCTL(X), ATTACH(X), or LOAD macro with program. For an alias name, make sure the alias attributes match
the EP (entry point) or EPLOC (EP location (address)) operand. the attributes of the load module which was already loaded; check
the library authorization, RMODE, and alias entry point displace-
The reason code in register 15 identifies the error: ment). Correct the error, and run the job step again.
Code Explanation If the reason code is X'14' or X'18', report this completion code to
04 The system could not find the module, whose entry point the system programmer.
is the value of the EP or EPLOC operand, in the indi- If the reason code is X'0C' or a X'1C', it is a probable user error.
cated library (private library, job library, or link library). Make sure that the DCB for the library is valid and open. Correct the
This situation can occur when LSEARCH=YES is speci- error and run the job step again.
fied on the macro and the limited library search fails to
locate the module. System Programmer Response: For reason code X'08', resubmit
the job. Then have the operator enter a START GTF command
08 An uncorrectable I/O error occurred when the BLDL specifying tape output, MODE=EXT and TIME=YES. Have the oper-
control program routine attempted to search the directory ator reply TRACE=IO in response to message AHL100A.
of the library that contained the program whose entry
point was specified in the EP or EPLOC operand. This Format the output with the IPCS GTFTRACE subcommand.
can occur if the specified library is an uninitialized parti- If the error recurs and the program is not in error, see the system
tioned data set (PDS). programmer response for messages in the job log.
An incorrect data extent block (DEB) has been detected For reason code X'2C' or if the problem persists, search problem
by the BLDL control program. The DEB was built in reporting data bases for a fix for the problem. If no fix exists, contact
other than protect key 0 through 7.
System Completion Codes SCC-171
80A 830
the IBM Support Center. Provide the ABEND dump and the source
81A
program listing for the job.
Explanation: A request to abnormally end the catalog address
80A space (CAS) mother task was issued either through the MODIFY
CATALOG,RESTART command, or through catalog analysis task
Explanation: An error occurred when the system tried to process processing.
an R form of the GETMAIN or FREEMAIN macro. A reason code in
the SDWACRC field of the system diagnostic work area (SDWA) Source: DFSMSdfp
explains the error: System Action: The system re-drives all catalog requests in
Code Explanation process.
04 There is not enough virtual system queue area (SQA)
822
storage available to satisfy the request.
Explanation: During initialization of a job, the initiator could not
08 There is not enough virtual common service area (CSA)
obtain a region required to run the step.
storage available to satisfy the request.
Source: Initiator/terminator
0C There is not enough virtual local system queue area
(LSQA) storage available to satisfy the request. System Action: The system issues message IEF085I when the job
is an ordinary job. The system issues message IEF186I when the job
10 There is not enough virtual private area storage avail-
is a deferred checkpoint restart.
able to satisfy the request.
System Programmer Response: A complete dump is necessary to
Note: This error can occur if an installation exit is
diagnose this out of storage condition. If no dump was produced, a
requesting virtual storage from a V=R region
SLIP should be set to obtain a dump on problem recurrence.
before the system completely initializes the
region. SLIP SET,COMP=822,A=SVCD,SDATA=(ALLNUC,
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END
1C During request processing, the system tried to get LSQA
virtual storage for VSM's cell pool. There was not Also, search problem reporting data bases for a fix for the problem. If
enough LSQA virtual storage available. no fix exists, contact the IBM Support Center.
20 There is not enough virtual storage in LSQA to build a
new address queue anchor table (AQAT) stack. 82A
Source: Virtual storage management (VSM) Explanation: During processing of an ATTACH macro, the system
found an incorrect subpool specified by an authorized task with the
System Action: The system issues message IEA705I. The system NSHSPV or the NSHSPL parameter. The authorized task is in
abnormally ends the current task. system key, supervisor state, or authorized by the authorized
Programmer Response: A complete dump is necessary to diag- program facility (APF).
nose this out of storage condition. If no dump was produced, SLIPs Source: Task management
should be set to obtain a dump on problem recurrence. An abend
878 can cause this same condition, so both SLIPs should be set as System Action: The system abnormally ends the program that
follows: issued the ATTACH macro. The system does not create the new
subtask.
SLIP SET,COMP=8ðA,A=SVCD,SDATA=(ALLNUC,
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END Programmer Response: Change the incorrect parameter. Only
subpool 236 or 237 may be specified with the NSHSPV or the
SLIP SET,COMP=878,A=SVCD,SDATA=(ALLNUC, NSHSPL parameter. Correct the error. Run the job again.
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END
System Programmer Response: If the error recurs and the
Also, check for program errors that incorrectly modify the macro program is not in error, look at the messages in the job log for more
expansion. Correct them. If necessary, change the program to information. Search problem reporting data bases for a fix for the
request less virtual storage. Further debugging information may be problem. If no fix exists, contact the IBM Support Center. Provide the
found in Informational APAR II05506. assembly listing for the job.
813 830
Explanation: The error occurred during processing of an OPEN Explanation: Global resource serialization encountered an error
macro instruction for a data set on magnetic tape. This system com- during processing of a DEQ macro instruction.
pletion code is accompanied by message IEC149I. Refer to the
The resource specified by the DEQ is the target of an outstanding
explanation of message IEC149I for complete information about the
ENQ macro instruction with the MASID and MTCB options specified.
task that was ended and for an explanation of the return code (rc in
The task that issued the ENQ macro instruction with MASID and
the message text) in register 15.
MTCB should issue the DEQ macro instruction before this task.
Source: DFSMSdfp
Source: Global resource serialization
Programmer Response: Respond as indicated for message
System Action: The system issues an ABEND dump.
IEC149I.
Programmer Response: Correct the program so that the DEQ
System Programmer Response: If the error recurs and the
macro instruction is issued only after DEQs have been issued for
program is not in error, look at the messages in the job log for more
any outstanding MASID/MTCB ENQs. Recompile and run the job
information. Search problem reporting data bases for a fix for the
step again.
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job.
SCC-172 OS/390 V2R8.0 MVS System Codes
837 878
System Programmer Response: If the problem persists, search
878
problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the dump. Explanation: The error occurred when the system was trying to do
one of the following:
837 Satisfy a request made through the STORAGE macro
Explanation: The error occurred at an end-of-volume for a sequen- Process an RU or VRU form of the GETMAIN macro
tial data set. This system completion code is accompanied by
Process an RU form of the FREEMAIN macro
message IEC028I. Refer to the explanation of message IEC028I for
complete information about the task that was ended and for an A reason code in the SDWACRC field of the system diagnostic work
explanation of the return code (rc in the message text) in register 15. area (SDWA) explains the error:
Source: DFSMSdfp Code Explanation
Programmer Response: Respond as indicated for message 04 There is not enough virtual system queue area (SQA)
IEC028I. storage available to satisfy the request.
System Programmer Response: If the error recurs and the 08 There is not enough virtual common service area (CSA)
program is not in error, look at the messages in the job log for more storage available to satisfy the request.
information. Search problem reporting data bases for a fix for the 0C There is not enough virtual local system queue area
problem. If no fix exists, contact the IBM Support Center. Provide the (LSQA) storage available to satisfy the request.
JCL and the program listing for the job.
10 There is not enough virtual private area storage avail-
able to satisfy the request. This is due to one of the
838
following:
Explanation: The system denied an ENQ macro request because
A program is requesting virtual storage, but not sub-
of serious damage to the ENQ/DEQ control blocks.
sequently freeing the storage.
Source: Global resource serialization
The region size specified is too small.
System Action: The system issues an ABEND dump.
An installation exit is requesting virtual storage from
Programmer Response: Resubmit the job after the system has a V=R region before initialization of the region has
been re-IPLed. Do the following: completed.
1. Obtain the address of the DEQ parameter list from register 1 in 14 A negative amount of storage was specified on a
the UNIQUE-3 column of the SVC 30 or SVC 38 entry in the GETMAIN macro.
system trace.
Note: If this error is detected, the calling program
2. Check the parameter list against the SVC 30 or 38 mapping. abnormally ends even though RC, EC, LC, or VC
When analyzing the parameter list, remember that the unit is specified for GETMAIN, or COND=YES is
control block (UCB) pointer, if present, is the address of a field specified for STORAGE.
that, in turn, contains the address of the UCB.
18 A negative amount of storage was specified on the
If the parameter list contains incorrect data, continue diagnosis FREEMAIN or STORAGE macro.
in the program that issued the macro.
Note: If this error is detected, the calling program
System Programmer Response: If the problem persists, search abnormally ends even though RC, EC, LC, or VC
problem reporting data bases for a fix for the problem. If no fix is specified for FREEMAIN, or COND=YES is
exists, contact the IBM Support Center. Provide the ABEND dump. specified for STORAGE.
1C During request processing, the system tried to get LSQA
85F virtual storage for virtual storage management's (VSM)
Explanation: The channel path measurement facility (CPMF) is not cell pool. There was not enough LSQA virtual storage
available because of a hardware error. available.
Code Explanation 20 There is not enough virtual storage in the LSQA to build
a new address queue anchor table (AQAT) stack.
4 A restart was not attempted either because the restart
threshold was exceeded or because the hardware error 24 A GETMAIN or STORAGE OBTAIN request with the
was not recoverable. LOC=EXPLICIT keyword specified failed for one of the
following reasons:
8 A restart was attempted but was not successful.
Part of the requested area was already allocated.
Source: System resource manager (SRM) Storage was already allocated in the same page as
System Action: The system issues message IRA604I in conjunc- this request, but one of the following characteristics
tion with this system completion code. of the storage was different:
– The subpool
System Programmer Response: Correlate this event to dis-
– The key
ruptions in CPMF data collection. A CPMF restart will be attempted
– Central storage backing
at the next system IPL. See further documentation regarding CPMF
in OS/390 MVS Data Areas, Vol 2 (DCCB-ITTCTE) under IRACPMB. 28 A GETMAIN or STORAGE OBTAIN request with the
LOC=EXPLICIT keyword specified failed because part of
the requested area exceeds the bounds of the region.
Source: Virtual storage management (VSM)
System Completion Codes SCC-173
87D 8C5
System Action: The system issues message IEA705I. The system problem. If no fix exists, contact the IBM Support Center. Provide the
abnormally ends the current task. program listing and the assembly listing associated with the job.
Programmer Response: A complete dump is necessary to diag-
nose this out of storage condition. If no dump was produced, SLIPs 8C4
should be set to obtain a dump on problem recurrence. Further Explanation: During the processing of an automatic restart
debugging information may be found in Informational APAR II05506. manager function, JES detected an error.
An abend 80A can cause this same condition, so both SLIPs should
be set as follows: Register 15 contains a hexadecimal reason code that explains the
error:
SLIP SET,COMP=878,A=SVCD,SDATA=(ALLNUC,
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END Code Explanation
04 Unexpected return code from IEFSSREQ macro.
SLIP SET,COMP=8ðA,A=SVCD,SDATA=(ALLNUC,
PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END Source: Functional subsystem interface (FSI)
Also, depending on the reason code, do one of the following: System Action: The system issues an SVC dump.
10 Try increasing the region size specified in the region parameter Programmer Response: Search problem reporting data bases for
on the JOB or EXEC statement in the JCL for the job. However, a fix for the problem. If no fix exists, contact the IBM Support Center.
if the cause of the problem is actually that a program is Provide the SVC dump.
requesting virtual storage and not freeing it, the abend will recur
when the program uses the virtual storage in the larger region. 8C5
24 Ensure that the calling program specifies the following correctly: Explanation: The Subsystem Interface (SSI) encountered a system
or user error when either initializing dynamic SSI services or
The storage address on the INADDR keyword. responding to a dynamic SSI service request issued through the
The length on the LENGTH keyword for the STORAGE IEFSSI or IEFSSVT macros.
macro or the LV keyword for the GETMAIN macro. Register 15 contains a hexadecimal reason code that explains the
The desired subpool or key. error:
The target address space for the STORAGE macro. Code Explanation
The TCB address for the STORAGE macro. 01 The system was unable to obtain storage for the sub-
system vector table (SSVT).
Make sure also that the area of storage you are requesting is
03 The system was unable to establish a PC entry table to
completely free. If part of the area requested is in a page that is
support internal SSI services.
already allocated, make sure that the central storage backing
specified on the LOC=EXPLICIT keyword matches that of the 04 The system was unable to establish the PC entry table
allocated storage. to support the dynamic SSI services.
28 Ensure that the calling program specifies the following correctly: 05 An invalid request type was passed to an internal SSI or
dynamic SSI service.
The storage address on the INADDR keyword.
06 The system was unable to obtain storage for internal SSI
The length on the LENGTH keyword for the STORAGE control structures.
macro or the LV keyword for the GETMAIN macro.
07 The MSTR subsystem could not be initialized.
Make sure also that the calling program correctly specifies
08 An SSI routine was unable to establish an ESTAE.
the value on the JCL REGION keyword. If the JCL REGION
value is not large enough for the requested storage area, 10 An unauthorized caller requested a dynamic SSI service.
increase the size of the JCL REGION and resubmit the job. All dynamic SSI services with the exception of the
IEFSSI REQUEST=QUERY require the caller to be
04-0C, 14-20 authorized.
Check for program errors that incorrectly modify the macro
expansion and correct them. If necessary, change the program 11 An SRB mode caller requested a dynamic SSI service
to request less virtual storage. 12 A caller holding a lock requested a dynamic SSI service.
13 An unexpected error was encountered in validating the
87D SSOB and SSIB provided as input to a subsystem func-
Explanation: During processing of an EVENTS macro, the system tion request.
found that the EVENTS table specified in the event control block 14 An unauthorized caller of the IEFSSI query service
(ECB) had no entries available for the posted ECB address. requested that the information be returned in storage
Source: Task management obtained from an authorized subpool.
System Action: The system abnormally ends the program that 15 A caller in cross-memory mode requested a dynamic
issued the EVENTS macro. SSI service.
Programmer Response: Ensure that the EVENTS table is large Source: Subsystem Interface (SSI)
enough to contain entries for all ECBs that can be posted to it. System Action: The system action depends on the reason code:
Correct the error. Run the job again.
Code System Action
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 01, 03, 04, 06, 07 The system requests a dump and enters a per-
information. Search problem reporting data bases for a fix for the manent wait state (either code 00B or 00D).
SCC-174 OS/390 V2R8.0 MVS System Codes
8C6 8FB
05, 08, 13 A dump is produced. If these reason codes Code Explanation
occurred during system initialization, the system
01 Module IATIIPL detected a subsystem interface error
may enter a permanent wait state.
during storage management subsystem (SMS) pre-
10, 11, 12, 14, 15 A user error occurred. A dump is not produced. locate catalog orientation processing. Register 2 con-
tains the subsystem interface return code.
Operator Response: If the system enters a permanent wait state,
reIPL the system. 02 Storage management subsystem (SMS) pre-locate
catalog orientation processing returned an unexpected
Programmer Response: The programmer response depends on
return or reason code to module IATIIPL. Register 2
the reason code:
contains the return code from that processing, and reg-
Code Programmer Response ister 3 contains the reason code.
10, 11, 12, 15 Revise the program issuing either the IEFSSI 03 Module IATLVLC detected a subsystem interface error
macro or the IEFSSVT macro to ensure that the during storage management subsystem (SMS) pre-
correct environment is established. Requestors locate catalog orientation processing. Register 2 con-
must be unlocked, in task mode, may not be in tains the subsystem interface return code.
cross-memory mode, and must be authorized for
05 While creating the system work area (SWA), module
all requests other than IEFSSI
IATIIII detected an error. The error occurred when the
REQUEST=QUERY.
module was either reading or mapping SWA control
14 Change the requested subpool to an unauthor- blocks.
ized subpool.
06 Module IATDMGR detected an error in a JES3 user
System Programmer Response: Analyze the dump to determine spool access method (USAM) POINT or WRITE opera-
why the system was unable to either obtain storage, establish a PC tion. Register 2 contains the return code from the failing
entry table or establish an ESTAE. operation.
07 Module IATDMGR detected an error during the initializa-
8C6 tion of either a data set status block (DSS) or a data set
Explanation: A program attempted to free a CIB control block that block (DSB). Register 2 contains the return code from
was not properly chained for execution. the failing operation.
Source: Master Scheduler Address Space/SVC 34 08 Module IATDMGR detected a user spool access method
(USAM) buffer initialization error. Register 2 contains the
System Action: The attempt is rejected, and the CIB is not freed.
return code from the failing operation.
System Programmer Response: Using the information that was
09 While incrementing the JCL statement count, module
dumped for the abend (CIB and associated CSCB), identify the
IATIICX detected an overflow condition.
program that attempted to free the CIB. Change the program to
avoid chaining a CIB that is not valid. IBM recommends using the 0A Module IATLVLC detected a subsystem interface error
MODIFY macro for this purpose. during storage management subsystem (SMS) VOLREF
services processing. Register 2 contains the subsystem
8C7 interface return code.
Explanation: MVS message service (MMS) processing failed. Due 0C Module IATMDST detected a subsystem interface error
to the error, MMS could not issue an error message to explain the during storage management subsystem (SMS) system
error. A hexadecimal reason code in register 15 explains the reason select processing. Register 2 contains the subsystem
that MMS could not issue the error message. interface return code.
Source: MVS message service (MMS) 0D SMS system select processing returned an unexpected
return or reason code to module IATMDST. Register 2
System Action: The system abnormally ends all MMS processing contains the return code from that processing, and reg-
with completion code X'8C7'. MMS functions are not available. The ister 3 contains the reason code.
system writes an SVC dump.
0E Module IATSISA detected an error during a PUT opera-
System Programmer Response: Search problem reporting data tion. Register 2 contains the return code from that opera-
bases for a fix for the problem. If no fix exists, enter the IPCS tion.
VERBEXIT MMSDATA subcommand to format the SVC dump.
Contact the IBM Support Center. Provide the VERBEXIT MMSDATA 0F The reader/interpreter passed an incorrect return code to
output. Provide the reason code associated with the X'8C7' abend JES3.
code. 10 Module IATIISP detected an error during a user spool
access method (USAM) PUT operation.
8FB 11 Module IATDMGR detected an incorrect function code.
Explanation: One of the following routines detected an error in a 12 Module IATDMGR detected an error in the block
subtask: spooler. Register 2 contains the return code from the
Converter/interpreter (C/I) block spooler.
Locate 13 Module IATLVLC detected an error in the block spooler.
Main device scheduling (MDS) Register 2 contains the return code from the block
JES3 interface spooler.
A hexadecimal reason code in register 15 explains the error. 14 Module IATMDST detected an error in the block spooler.
Register 2 contains the return code from the block
spooler.
System Completion Codes SCC-175
9C4 9C4
15 Module IATSISA detected an error during a GET opera- 0E, 11, 12, 15 The system ends the subtask; when the sub-
tion. Register 2 contains the return code from that opera- task's ESTAE gets control, the system writes a
tion. dump. Then, the system cancels with print the
job that the subtask was processing.
16 Module IATLVLC detected that the ESTAE service could
not set up a recovery environment. Register 2 contains 0F The system ends the job and continues other
the return code from that service. processing.
17 Module IATMDST could not find a job data set (JDS) 16 The system ends the locate subtask.
entry.
Operator Response: Save all associated print output, and notify
18 Module IATLVLC either could not find a locate request the system programmer.
table (LVS), or encountered an incorrect LVS entry.
System Programmer Response: Obtain the JCL for the job.
19 Module IATIIST detected an error during a PUT opera-
For a return code of X'05', rerun the job with the DEBUG=ALL
tion.
option after a //* PROCESS CI JECL statement.
1A Storage management subsystem (SMS) VOLREF ser-
For a return code of X'21', examine the IEFSSSA data area and
vices returned incorrect information to module IATLVLC.
determine the reason for the zero in the SSSABNUM field. Also,
1C Catalog management (SVC 26) returned incorrect infor- examine the SSSABSAC and SSSABSAR fields (failing service
mation to module IATLVLC. return code and reason code). Notify SMS support.
1D Module IATIIPL detected that the ESTAE service could For return code X'22', examine IEFSSSA and determine the reason
not set up a recovery environment. Register 2 contains for the zero in the SSSACNUM field. Also, examine the SSSACSAC
the return code from that service. and SSSACSAR fields (failing service return code and reason code).
Notify SMS support.
20 Module IATIICX received a return code of 4 from
IATUX03 indicating that the JCL limit has been For all other return codes, examine the print output to find and
exceeded. correct the error.
21 Module IATIIST detected a zero for the number of If the problem occurs in JES3 and the return code is an X'05' you
systems eligible to access SMS resources (field should:
SSSABNUM in IEFSSSA).
Obtain a stand-alone dump of the system by specifying
22 Module IATMDST detected a zero for the number of DUMP=PRDUMP on the OPTIONS statement in the initialization
systems eligible to access SMS resources (field deck.
SSSACNUM in IEFSSSA).
Save the hardcopy log
Source: JES3
Provide a listing of the initialization deck (JESOUT)
System Action: The system action depends on the abend reason
Determine the MVS and JES3 PTF levels
code:
Rerun the job with //*PROCESS CBPRINT and save the output
Code System Action
after interpreter DSP.
01, 02, 1D The system ends the generalized subtask; when
If the problem is not for X'05', check the JESYSMSG data set for
the subtask's ESTAE gets control, the system
error indications.
writes a dump. Then, with a DM146 abend, the
system fails the converter/interpreter or postscan
dynamic support program (DSP) that was using
9C4
the subtask. Also, the system cancels with print
the job that the DSP was processing. Explanation: An abend has been issued by the system data mover
function.
03, 04, 06, 07, 08, 0A, 0B, 13, 18, 1A, 1B, 1C The system ends the
locate subtask; when the subtask's ESTAE gets Register 15 contains one of the following reason codes:
control, the system produces a dump. Then, the Code Explanation
system cancels with print the job that the
subtask was processing. 4 The ANTMAIN address space has restarted due to an
error condition that ended the XRC session, or due to an
05 The system ends the address space; when the operator-initiated CANCEL command. Any program that
ESTAE gets control, the system produces a attempts to access the ANTMAIN address space is
dump. Then, the system cancels with print the ended with this abend condition. Check the results of the
job that was processing. ended jobs to determine if data movement was suc-
09, 10, 19, 21 The system ends the converter/interpreter (C/I) cessful before the jobs ended. Resubmit the job if data
subtask. When the subtask's ESTAE receives movement was unsuccessful.
control, the system produces a dump. Then, the 8-100 The XRC function has detected an error that requires an
system cancels and prints the job that the abend dump to isolate the cause. The reason codes
subtask was processing and reinstates the contain specific diagnostic information to help isolate the
subtask. specific error condition. In all cases, data on the sec-
0C, 0D, 14, 17, 22 The system ends the main device scheduling ondary volumes is preserved at a known consistent state
(MDS) subtask. When the subtask's ESTAE gets as reported by XRC messages.
control, the system produces a dump. Then, the The following are some of the more common reason
system either cancels and prints the job that the codes for configuration ration-type errors that can
subtask was processing or places it on the MDS produce 9C4 abend dumps:
error queue. The system reinstates the subtask.
SCC-176 OS/390 V2R8.0 MVS System Codes
905 906
10 A record cannot be found.
905
2C An invalid format error has occurred. Explanation: An error occurred when the system tried to process
30 an EC, EU, LC, LU, VC, or VU form of the FREEMAIN macro.
34 The data mover has not read from the storage A reason code in the SDWACRC field of the system diagnostic work
control for at least the timeout interval specified. area (SDWA) explains the error:
The storage control session has been canceled; all
Code Explanation
XRC volume pairs associated with this storage
control must be reinitialized. 04 The virtual storage area that the FREEMAIN macro tried
to release is not on a double word boundary.
38 A storage control logic error has occurred.
Source: Virtual storage manager (VSM)
54 A nonstandard Record 0 has been detected on the
System Action: The system issues message IEA705I. The system
volume.
abnormally ends the current task.
The reason codes indicate why the abend was gener- Programmer Response: Check for program errors that incorrectly
ated. In every case, data on the secondary volumes is modify the macro expansion. Correct them. If necessary, change the
left in a consistent, recoverable state. The following are program to request less virtual storage.
some of the reasons why a 9C4 can occur:
A volume has been initialized using an XADDPAIR 906
command with NOCOPY specified, but the volume
contents were not identical. Explanation: A reason code in register 15 identifies the error:
The secondary volume has been updated by a func- Code Explanation
tion other than the data mover. The secondary 04 An error was detected during the processing of a LOAD
volume must be dedicated to the data mover for all macro. The LLE (load list element) count (responsibility
update operations. Other functions may read the count), indicating the number of load requests for a
volume, but only the data mover can make updates. module, is greater than the allowable maximum, which is
Multiple data movers are updating the secondary 32767.
volume. It is possible that more than one data 08 An error was detected during processing of a LINK(X),
mover is copying data to the same secondary XCTL(X), ATTACH(X), or LOAD macro. The CDE (con-
volume. Only one data mover may have ownership tents directory element) use count, indicating the number
of a secondary volume. of LINK(X), XCTL(X), ATTACH(X), or LOAD requests for
I/O has stopped in a subsystem. I/O may not be a module, is greater than the allowable maximum, which
active on a primary storage control, secondary is 32767.
volumes, or journal volumes. Activity may be 0C The failing program has issued an XCTL(X) request, but
stopped because the subsystem is not accepting the program has an outstanding program linkage that
I/Os or because of a line failure in a channel has not completed properly. This commonly occurs when
extended environment. a program issues a program call (PC) and then issues
A session has been restarted after maintenance has an XCTL(X) request before issuing a program return
been applied to the data mover system. If incompat- (PR).
ibilities exist in the journal, state, or control data 100 An error was detected during processing of a CSVINFO
sets, a 9C4 abend with reason codes 10 or 2C may request. It was determined that an Extent List (XTLST)
result. Ensure that the data sets have been properly control block contained incorrect information.
allocated before starting or restarting the data
Source: Contents supervision (CSV)
mover.
System Action: For reason codes X'04' X'08', the task ends
Source: System data mover (ANT).
unless ERRET is specified on the macro. For reason codes X'0C'
System Action: The system abnormally ends the task that and X'100', the request is terminated. The system issues a
encountered the abend condition. message depending on the reason code accompanying the abend:
System Programmer Response: Register 15 contains the nonzero Code Message/ABEND Type
return code that describes the reason the abend was issued. The
04 CSV001I/ABDUMP
abend error may be the result of a hardware- or software-detected
error. Search problem reporting data bases for a solution. If no sol- 08 CSV002I/ABDUMP
ution exists, contact the IBM Support Center. Provide the console 0C CSV030I/ABDUMP
log, the dump data set, and the LOGREC data set error record.
100 /SVCDUMP
In most cases, XRC suspends one or more volume pairs as a result
of the error and the error level specified. You can usually issue an Programmer Response: Check for program errors, such as
XADDPAIR command to return the volume pairs to the session, and endless loops, that cause macros to be run too often. Ensure that
then resynchronize them. In some cases, you may need to issue the the program logic does not permit improper program linkage. After
MODIFY ANTAS001,RESTART command, followed by XADDPAIR making corrections, recompile and run the job step again.
commands, to rebuild the failed data mover sessions. System Programmer Response: For reason code X'100', contact
the IBM Support Center. Provide the dump and logrec entries associ-
ated with with abend. For the other reason codes, if the error recurs
and the program is not in error, see the system programmer
response for the messages in the job log.
System Completion Codes SCC-177
90A 930
System Programmer Response: Search problem reporting data
90A
bases for a fix for the problem. If no fix exists, contact the IBM
Explanation: An error occurred when the system tried to process Support Center, providing the SVC dump and logrec data set error
an R form of the FREEMAIN macro. A reason code in the records.
SDWACRC field of the system diagnostic work area (SDWA)
explains the error: 92A
Code Explanation Explanation: During processing of an ATTACH macro, an environ-
04 The virtual storage area that the FREEMAIN macro tried mental error occurred that was not caused by the current task.
to release is not on a doubleword boundary. Register 15 contains a hexadecimal reason code that explains the
Source: Virtual storage manager (VSM) error:
System Action: The system issues message IEA705I. The system Code Explanation
abnormally ends the current task. 00 An error occurred in the extended subtask ABEND exit
Programmer Response: Check for program errors that incorrectly (ESTAE) SVC issued to establish a recovery environ-
modify the macro expansion. Correct them. If necessary, change the ment for ATTACH processing.
program to request less virtual storage. 04 Storage in subpool 255 was not available for the new
supervisor request block (SVRB), subpool queue ele-
913 ments (SPQEs), and parameter save area.
Explanation: The error occurred during processing of an OPEN 08 An error occurred in SVC 60 (STAI/ESTAI) issued to
macro instruction. This system completion code is accompanied by propagate STAI/ESTAI storage control blocks (SCBs)
message IEC150I. Refer to the explanation of message IEC150I for from the current task control block (TCB) to the new
complete information about the task that was ended and for an TCB, and to build a new SCB if STAI or ESTAI was
explanation of the return code in register 15. specified on the ATTACH macro. The SVC 60 was a
Source: DFSMSdfp STAI entry if the STAI keyword was specified on the
ATTACH macro; otherwise, it is an ESTAI entry.
Programmer Response: Respond as indicated in message
IEC150I. 0C An error occurred when the system tried to obtain the
local lock.
System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more 10 An error occurred when SETLOCK was entered to
information. Search problem reporting data bases for a fix for the release the local lock.
problem. If no fix exists, contact the IBM Support Center. Provide the 14 The parameter list passed to ATTACH processing con-
JCL and the program listing for the job. tains an error.
18 ATTACH is unable to obtain a linkage stack for the task.
91A
Source: Task management
Explanation: A request to abnormally end the catalog address
System Action: The system abnormally ends the program that
space (CAS) service task was issued either through the MODIFY
issued the ATTACH macro. The system does not create the new
CATALOG,RESTART command, or through catalog analysis task
subtask.
processing.
Programmer Response: Run the job again. If the error recurs,
Source: DFSMSdfp
notify the system programmer.
System Action: The system re-drives the catalog request currently
System Programmer Response: Search problem reporting data
in process.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
922
Explanation: During initialization of a job step, the initiator detected 930
one of the following:
Explanation: A job issued an DEQ macro instruction that included
An abend the TCB operand. However, the TCB operand identified a task that
A program check was ending.
Depression of the RESTART key
Source: Global resource serialization
A machine check
System Action: The system writes a logrec data set error record
Source: Initiator/terminator
and issues an ABEND dump.
System Action: The system ends the job step and writes an SVC
Programmer Response: Determine why the task identified in the
dump. The system writes a logrec data set error record, except in
TCB operand was terminated. Correct that error and resubmit the job
the case of an OPEN failure. Job processing continues subject to
that caused the abend.
normal conditional processing.
System Programmer Response: If the problem persists, search
Programmer Response: Submit the job again.
problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the ABEND dump.
SCC-178 OS/390 V2R8.0 MVS System Codes
937 9C6
937 9C6
Explanation: The error occurred at an end-of-volume for a check- Explanation: An error occurred when a task or SRB routine called
point data set or a RACF-protected data set. This system completion a global resource serialization latch manager service.
code is accompanied by message IEC029I. Refer to the explanation
Notes:
of message IEC029I for complete information about the task that
was terminated and for an explanation of the return code (rc in the 1. In the description of this system code, the term requestor refers
message text) in register 15. to a task or SRB routine that calls a latch manager callable
service to:
Source: Resource Access Control Facility (RACF)
Request ownership of a latch, or
System Programmer Response: See the system programmer
Release a granted or pending request to obtain ownership
response for message IEC029I.
of a latch.
2. Equate symbols defined in the latch manager IDFs are followed
938
by their numeric equivalents; you may specify either when
Explanation: The job issued an ENQ macro instruction that coding calls to Latch_Obtain. For example, “ISGLOBT_COND
included the TCB operand. However, the TCB operand identified a (value of 1)” indicates the equate symbol ISGLOBT_COND and
task that was in the process of ending. its associated value, 1.
Source: Global resource serialization Source: Global resource serialization
System Action: The system records the error in logrec data set GPR 15 contains a hexadecimal reason code that explains the error.
and issues an ABEND dump. xxxx indicates internal information.
Programmer Response: Determine why the task identified in the Code Explanation
TCB operand ended. Correct that error and resubmit the job that
xxxx0001 A caller of a latch manager service specified an incorrect
caused the abend.
value on the latch_set_token parameter.
System Programmer Response: If the problem persists, search
System Action: The latch manager does not perform
problem reporting data bases for a fix for the problem. If no fix
the requested operation.
exists, contact the IBM Support Center. Provide the ABEND dump.
Programmer Response: Specify a latch_set_token
978 value that was returned by a previous call to the
Latch_Create service.
Explanation: An error occurred when the system tried to process
one of the following: xxxx0002 One of the following occurred:
A STORAGE macro The caller of the Latch_Create service specified an
An RC or RU form of the FREEMAIN macro incorrect value on the number_of_latches param-
eter. This value must be a non-zero fullword integer.
A reason code in the SDWACRC field of the system diagnostic work
area (SDWA) explains the error: The caller of the Latch_Obtain service specified an
incorrect value on the latch_number parameter. The
Code Explanation latch_number must be a fullword integer that is in
04 The virtual storage area that the FREEMAIN macro tried the range between 0 and the number of latches in
to release is not on a doubleword boundary. the associated latch set minus one.
Source: Virtual storage manager (VSM) System Action: If the error occurred when calling the
Latch_Create service, the system does not create the
System Action: The system issues message IEA705I. The system
latch set. If the error occurred when calling the
abnormally ends the current task.
Latch_Obtain service, the latch manager does not obtain
Programmer Response: Check for program errors that incorrectly the latch.
modify the macro expansion. Correct them. If necessary, change the
Programmer Response:
program to request less virtual storage.
If the error occurred on a call to the Latch_Create
service, specify a non-zero fullword integer on the
9C5
number_of_latches parameter.
Explanation: A NetView RODM abend occurred. The following
If the error occurred on a call to the Latch_Obtain
reason codes describe the error:
service, specify a value on the latch_number param-
Code Explanation eter in the range between 0 and the number of
0 RODM has cancelled the transaction based on the reply latches specified on the call to the Latch_Create
to message EKG132D. Message EKG1326D is issued service.
when there are still transactions running in RODM during xxxx0003 A caller of the Latch_Obtain service specified an incor-
checkpoint or RODM termination. rect value on the obtain_option parameter. The
System Action:Task is cancelled. obtain_option parameter must contain one of the fol-
lowing values:
33 A RODM internal error has occurred.
ISGLOBT_SYNC (value of 0)
System Action:Task is ended.
ISGLOBT_COND (value of 1)
System Programmer Response: Contact IBM service
for assistance. ISGLOBT_ASYNC_ECB (value of 2)
System Completion Codes SCC-179
9C6 9C6
System Action: The latch manager does not obtain the original caller of the Latch_Obtain service because the
latch. original caller is suspended while waiting to obtain the
latch.
Programmer Response: On the call to the
Latch_Obtain service, specify one of the values listed System Action: The latch manager does not release
above on the obtain_option parameter. the latch.
xxxx0004 A caller of the Latch_Release service specified an incor- Programmer Response: Check the application code to
rect value on the release_option parameter. The ensure that the correct latch token is passed to the caller
release_option must be ISGLREL_UNCOND (value of 0) of the Latch_Release service.
or ISGLREL_COND (value of 1).
xxxx000A A caller of the Latch_Release service specified a
System Action: The latch manager does not release latch_token that:
the latch.
Did not match a latch_token returned from the ori-
Programmer Response: On the call to the ginal call to the Latch_Obtain service, or
Latch_Release service, specify ISGLREL_UNCOND
Matched a latch_token for a latch that was previ-
(value of 0) or ISGLOBT_COND (value of 1) on the
ously released or purged.
release_option parameter.
System Action: The latch manager does not release
xxxx0005 A caller of a latch manager service specified an incorrect
the latch.
requestor_ID of all binary zeroes. The requestor_ID can
be any value except all binary zeroes. Programmer Response: On the call to Latch_Release,
specify a latch_token that matches a valid latch_token.
System Action: The latch manager does not perform xxxx000B A requestor called a latch manager service while disa-
the requested operation. bled for I/O and external interrupts.
Programmer Response: Specify a requestor_ID that is System Action: The latch manager might not perform
not all binary zeroes. the requested operation.
xxxx0006 A caller of the Latch_Obtain service specified an Programmer Response: Call the latch manager service
obtain_option of ISGLOBT_ASYNC_ECB and an while enabled for I/O or external interrupts.
ECB_address that was all binary zeroes. When the xxxx000C A requestor called a latch manager service while in
obtain_option is ISGLOBT_ASYNC_ECB, the 24-bit addressing mode.
ECB_address must be a non-zero address that points to
System Action: The latch manager does not perform
an event control block (ECB).
the requested operation.
System Action: The latch manager does not obtain the
Programmer Response: Call the latch manager service
latch.
again while running in 31-bit addressing mode.
Programmer Response: Specify an ECB_address that
points to a valid ECB.
xxxx000D A requestor called a latch manager service while holding
a lock.
xxxx0007 A caller of the Latch_Release service specified a
System Action: The latch manager might not perform
release_option of ISGLREL_UNCOND (value of 0). The
the requested operation.
latch manager did not grant ownership of the latch to the
original caller of the Latch_Obtain service. The system Programmer Response: Issue the SETLOCK
did not post the ECB specified on the original call to RELEASE macro to release the lock that the requestor
Latch_Obtain. currently holds.
System Action: The latch manager does not release xxxx000E A requestor called a latch manager service while in
the latch. access register (AR) address space control (ASC) mode.
Programmer Response: Wait until the system posts an System Action: The latch manager might not perform
ECB to indicate that the caller of Latch_Obtain has the requested operation.
obtained the latch. Then call the Latch_Release service
Programmer Response: Call the latch manager service
to release the latch.
again while running in primary ASC mode.
xxxx0008 A requestor called the Latch_Release service before the
xxxx000F One of the following:
original caller of the Latch_Obtain service could obtain
the latch. A requestor called the Latch_Release service and
specified an incorrect value on the latch_token
System Action: The latch manager does not obtain or
parameter
release the latch. The Latch_Manager returns a return
code of 0 to the caller of Latch_Release. The system An internal error occurred in a latch manager
passes control to the recovery routine for the caller of service.
Latch_Obtain. System Action: The latch manager might not perform
Programmer Response: Check the application code to the requested operation.
ensure that the correct latch token is passed to the caller Programmer Response: Check the application code to
of the Latch_Release service. ensure that the correct latch token is passed to the caller
xxxx0009 A caller of the Latch_Release service specified a of the Latch_Release service. If the problem persists,
release_option of ISGLREL_UNCOND (value of 0). The search problem reporting data bases for a fix for the
latch manager did not grant ownership of the latch to the problem. If no fix exists, contact the IBM Support Center.
SCC-180 OS/390 V2R8.0 MVS System Codes
9C6 9C6
xxxx0010 A requestor the Latch_Obtain service to obtain a latch. OS/390 MVS Programming: Authorized Assembler Ser-
The requestor is currently suspended and waiting for the vices Reference SET-WTO to diagnose the error.
latch. The system is ending the requestor because the
xxxx0017 A requestor called the Latch_Obtain service with an
latch set job step task (the task that created the latch
incorrect access_option. The access_option must be a
set) or latch set address space (the address space in
fullword integer with a value of ISGLOBT_EXCLUSIVE
which the latch set resides) is ending.
(value of 0) or ISGLOBT_SHARED (value of 1).
System Action: The latch manager does not obtain the
System Action: The latch manager does not obtain the
latch.
latch.
Programmer Response: If necessary, call the
Programmer Response: Specify an access_option of
Latch_Create service to create a new latch set.
ISGLOBT_EXCLUSIVE (value of 0) or
xxxx0011 A requestor called the Latch_Create service to create a ISGLOBT_SHARED (value of 1) on the call to the
latch set. The maximum number of latch sets allowed by Latch_Obtain service.
the system has been reached.
xxxx0019 A requestor called the Latch_Obtain service to obtain a
System Action: The latch manager does not create the latch. The maximum number of Latch_Obtain requests
latch set. allowed by the system has been reached.
Programmer Response: Identify programs that are cre- System Action: The latch manager does not obtain the
ating an unnecessarily large number of latch sets. latch.
Correct any problems with those programs. If the
Programmer Response: Consider placing limits or the
problem persists, contact the IBM Support Center.
number of tasks or SRB routines that can request
xxxx0012 A requestor called the Latch_Create service with an latches, or release held latches or requests to obtain
incorrect value on the create_option parameter. The latches to reduce contention for resources. If the
create_option must be a fullword integer with a value of problem persists, contact the IBM Support Center.
ISGLCRT_PRIVATE (value of 0).
xxxx0020 A requestor called the Latch_Obtain service to obtain a
System Action: The latch manager does not create the latch. The requestor ended before the latch manager
latch set. could finish processing the Latch_Obtain request.
Programmer Response: Specify a create_option of System Action: The latch manager does not obtain the
ISGLCRT_PRIVATE (value of 0) on the call to the latch.
Latch_Create service.
Programmer Response: Call the Latch_Obtain service
xxxx0013 On a call to the Latch_Create service, a requestor speci- again, if the requestor still requires access to the latch.
fied a latch_set_name parameter with a value that had a
xxxx01yy A requestor called the Latch_Obtain service to obtain a
first character of zero or blank. The latch_set_name can
latch. The system found an error when it tried to issue
contain any 48-byte hexadecimal value as long as the
the SUSPEND macro. A return code from the SUSPEND
first character is not binary zeroes or an EBCDIC blank.
macro (yy) indicates the reason for the error:
System Action: The latch manager does not create the
Code (yy) Explanation
latch set.
8 A program tried to call the Latch_Obtain
Programmer Response: On the latch_set_name
service with an obtain option of
parameter, specify a value with a first character is not
ISGLOBT_SYNC (value of 0) from an SRB
binary zeroes or an EBCDIC blank.
after the SRB abended with code X'47B'.
xxxx0014 A caller of a latch manager service has a PSW key that
C A program tried to call the Latch_Obtain
does not allow access to the latch set storage.
service with an obtain option of
System Action: The latch manager does not perform ISGLOBT_SYNC (value of 0) from within the
the requested operation. SUSPEND exit.
Programmer Response: Call the latch manager service 20 An error occurred in the SUSPEND exit
with a PSW key that matches the storage key of the routine.
latch set.
22 A system error occurred.
xxxx0015 An internal error occurred in a latch manager service.
System Action: The latch manager does not obtain the
System Action: The latch manager does not perform latch.
the requested operation.
Programmer Response: Depending on the return code
Programmer Response: Search problem reporting data from the SUSPEND macro, do one of the following:
bases for a fix for the problem. If no fix exists, contact
Code (yy) Action
the IBM Support Center.
8 Correct the program so it does not try to call
xxxx0016 The system could not obtain enough storage for a partic-
the Latch_Obtain service with an obtain
ular latch set. General purpose register (GPR) 2 con-
option of ISGLOBT_SYNC (value of 0) from
tains the return code from the STORAGE OBTAIN
an SRB that abended with code X'47B'.
macro.
C Correct the program so it does not try to call
System Action: The latch manager does not create the
the Latch_Obtain service with an obtain
latch set.
option of ISGLOBT_SYNC (value of 0) from
Programmer Response: See the description of the within the SUSPEND exit.
return codes for the STORAGE OBTAIN macro in
System Completion Codes SCC-181
9C7 9FB
20, 22 Search problem reporting data bases for a 4 Channel end (CHE) normal end appendage
fix for the problem. If no fix exists, contact
5 Abnormal end (ABE) appendage
the IBM Support Center.
6 Caller's page fix appendage
For more information about the SUSPEND macro, see
OS/390 MVS Programming: Authorized Assembler Ser- Source: Execute channel program (EXCP)
vices Reference SET-WTO. System Action: The system abnormally ends the current task. The
system writes a logrec data set error record and issues a SNAP
9C7 dump.
Explanation: RACROUTE functions that use tokens (such as Programmer Response: If EXCP is being used for I/O operations,
VERIFY, VERIFYX, TOKENBLD, TOKENMAP) abend 9C7 when an this is an error in the appendage identified by the reason code. Fix
incorrect token is detected. the appendage and run the job again. If the error persists, run the
job again requesting an ABEND dump and then notify the system
The following reason codes will be issued with abend 9C7:
programmer.
Code Explanation
System Programmer Response: In the dump, look at field
01 STOKEN area is too small. TCBEXCPD at offset X'C0' in the task control block (TCB) for the
02 TOKNIN area is too small. current task. TCBEXCPD points to the EXCP debugging area
(XDBA). The XDBA contains diagnostic data associated with the
04 TOKNIN keyword is missing. EXCP processor. To determine which appendage was active, see
08 TOKNOUT keyword is missing. the microfiche mapping for data area XFRR of the EXCP/EXFR FRR
parameter area.
0C TOKNOUT area is too small.
If the error recurs and the program is not in error, look at the mes-
10 VERSION=0.
sages in the job log for more information. Search problem reporting
14 USERID has length greater than 8. data bases for a fix for the problem. If no fix exists, contact the IBM
18 PASSWORD has length greater than 8. Support Center. Provide the logrec data set error record, the JCL for
the job, and the SNAP dump.
1C GROUPID has length greater than 8.
20 NEWPASSWORD has length greater than 8. A03
24 EXENODE has length greater than 8. Explanation: A task tried to end normally by issuing a RETURN
28 SUSERID has length greater than 8. macro or by branching to the return address in register 14. The task
was not ready to end processing because either:
2C SNODE has length greater than 8.
The task had attached one or more subtasks that had not
30 SGROUP has length greater than 8.
ended.
34 TOKNOUT version is greater than the current maximum.
The task did not detach a subtask that it had previously attached
Source: Resource Access Control Facility (RACF) with the event control block (ECB) option.
System Action: The system abnormally ends the task. Source: Recovery termination manager (RTM)
Programmer Response: This is possibly a user error. Verify that System Action: The system abends the task.
the token interface is correct.
Operator Response: If the system or application programmer asks
System Programmer Response: Check the reason code and for an SVC dump, set the following SLIP trap:
make sure you pass the correct token in the request. SLIP SET,COMP=Að3,ACTION=SVCD,END
Programmer Response: Do the following:
9FB
1. If a dump is not produced with the abend, ask the operator to
Explanation: JES3 output service module IATOSDR or IATOSPS
set a SLIP trap to obtain an SVC dump.
abnormally ended an MVS service routine, usually SETPRT, in order
to process a JES writer function or an operator command. This com- 2. From the dump, identify the abnormally ended module from the
pletion code does not indicate a program failure. contents directory entry (CDE) or from the PRBRSV field in the
associated RB.
Source: JES3
3. If the module is an installation-provided program, change the
System Action: The system continues processing.
program so that, before the task ends, all its subtasks will end.
A task can determine that its subtasks have ended by specifying
event control block (ECB) operands in ATTACH macros that ini-
A00 tiate the subtasks, and then issuing WAIT macros that specify
Explanation: During processing of an I/O request, execute channel ECBs representing the end of its subtasks.
program (EXCP) encountered an error while an appendage was When the ECB option has been specified with the ATTACH
running. Each X'A00' abend code has a reason code that shows macro, the task must detach its subtask once notification of
which appendage contained the error: subtask ending has been received. Failure to do so will result in
Code Explanation this abend.
1 Program controlled interrupt (PCI) appendage If a WAIT macro had been issued and the ECBs indicated that
all subtasks had ended, check for program errors that incorrectly
2 Start I/O (SIO) appendage
modified the WAIT macros or ECBs.
3 End of extent (EOE) appendage
SCC-182 OS/390 V2R8.0 MVS System Codes
A05 A0A
After making corrections, recompile the program. Run the job
A06
step again.
Explanation: The error was detected during processing of either a
System Programmer Response: If the module is an IBM program,
LINK(X), LOAD, XCTL(X) or ATTACH(X) macro instruction.
search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the dump. Code Explanation
04 A request block (RB) is requesting a serially reusable
A05 program. Another RB associated with the task requested
Explanation: An error occurred when the system tried to process the same program, and that request has not yet been
an EC, EU, LC, LU, VC, or VU form of the FREEMAIN macro. A satisfied.
reason code in the SDWACRC field of the system diagnostic work Source: Contents supervision (CSV)
area (SDWA) explains the error.
System Action: The task ends unless ERRET is specified on the
Code Explanation macro. The system issues message CSV000I. The system issues an
04 The system queue area (SQA) storage to be freed over- ABEND dump.
laps free storage. Programmer Response: Change the program to wait until the seri-
08 The common service area (CSA) storage to be freed ally reusable load module is run before issuing the LINK(X), LOAD,
overlaps free storage. XCTL(X) or ATTACH(X) macro for the load module. After making
corrections, recompile and run the job step again.
0C The local system queue area (LSQA) storage to be freed
overlaps free storage. System Programmer Response: If the error recurs and the
program is not in error, see the system programmer for the mes-
10 The private area storage to be freed overlaps free sages in the job log.
storage.
If the problem persists, search problem reporting data bases for a fix
14 Part of the CSA to be freed is fixed. for the problem. If no fix exists, contact the IBM Support Center.
18 Part of the private area to be freed is fixed. Provide the ABEND dump and the source program listing for the job.
1C The private area to be freed is associated with a data-in-
virtual object. A0A
20 The private area to be freed has been specified on the Explanation: An error occurred when the system tried to process
IARSUBSP IDENTIFY request, and is eligible to be an R form of the FREEMAIN macro. A reason code in the
assigned to a subspace. SDWACRC field of the system diagnostic work area (SDWA)
explains the error:
24 The task or service request block (SRB) routine tried to
free SQA storage that either overlaps free storage or Code Explanation
was obtained by more than one request. 04 The system queue area (SQA) storage to be freed over-
28 The task or SRB routine tried to free CSA storage that laps free storage.
either overlaps free storage or was obtained by more 08 The common service area (CSA) storage to be freed
than one request. overlaps free storage.
Source: Virtual storage manager (VSM) 0C The local system queue area (LSQA) storage to be freed
System Action: The system issues message IEA705I. The system overlaps free storage.
abnormally ends the current task. 10 The private area storage to be freed overlaps free
Programmer Response: Do the following: storage.
Ensure that the FREEMAIN operands do not specify a different 14 Part of the CSA to be freed is fixed.
subpool and/or key than the subpool or key of the storage you 18 Part of the private area to be freed is fixed.
are trying to free.
1C The private area to be freed is associated with a data-in-
Ensure that the task control block (TCB) specified on the virtual object.
FREEMAIN request is the same one specified on the corre-
20 The private area to be freed has been specified on the
sponding GETMAIN request.
IARSUBSP IDENTIFY request, and is eligible to be
If a caller running in supervisor state and key 0 made the ori- assigned to a subspace.
ginal GETMAIN request, ensure that the corresponding
24 The task or service request block (SRB) routine tried to
FREEMAIN request is also issued in supervisor state and key 0.
free SQA storage that either overlaps free storage or
If a caller in supervisor state and key 0 requests storage in was obtained by more than one request.
subpool 0 or 250, the system satisfies this request with storage
28 The task or SRB routine tried to free CSA storage that
from a different subpool. This situation is described in OS/390
either overlaps free storage or was obtained by more
MVS Diagnosis: Reference.
than one request.
If the storage is eligible to be assigned to a subspace, make the
Source: Virtual storage manager (VSM)
storage ineligible by specifying the storage range on an
IARSUBSP UNIDENTIFY request before attempting to release System Action: The system issues message IEA705I. The system
the storage. abnormally ends the current task.
Check for program errors that incorrectly modify the FREEMAIN Programmer Response: Do the following:
macro expansion. Ensure that the FREEMAIN operands do not specify a different
subpool and/or key than the subpool or key of the storage you
are trying to free.
System Completion Codes SCC-183
A13 A37
Ensure that the task control block (TCB) specified on the
A22
FREEMAIN request is the same one specified on the corre-
sponding GETMAIN request. Explanation: A FORCE command requested that a job be can-
celed, possibly for one of these reasons:
If a caller running in supervisor state and key 0 made the ori-
ginal GETMAIN request, ensure that the corresponding The CANCEL command could not cancel the job.
FREEMAIN request is also issued in supervisor state and key 0. The system was in a deadlock. For example, two tasks were
If a caller in supervisor state and key 0 requests storage in enqueued on a resource without an intervening dequeue.
subpool 0 or 250, the system satisfies this request with storage An installation-established procedure was violated by the job.
from a different subpool. This situation is described in OS/390
MVS Diagnosis: Reference. There may be nothing wrong with the job itself.
If the storage is eligible to be assigned to a subspace, make the Source: Reconfiguration
storage ineligible by specifying the storage range on an System Action: The system ends the address space associated
IARSUBSP UNIDENTIFY request before attempting to release with the job. The system ends all tasks running in the address
the storage. space.
Check for program errors that incorrectly modify the FREEMAIN Programmer Response: Find out why the operator canceled the
macro expansion. job and make any necessary corrections. Rerun the job, ensuring
that the operator enters a CANCEL jjj,DUMP command, if neces-
A13 sary.
Explanation: The error occurred during processing of an OPEN
macro instruction for a data set on magnetic tape. This system com- A23
pletion code is accompanied by message IEC151I. Refer to the Explanation: The system was trying to process a macro instruction
explanation of message IEC151I for complete information about the issued by the communications task (COMMTASK). An error occurred
task that was ended and for an explanation of the return code (rc in because an incorrect address was specified.
the message text) in register 15.
Source: Communications task (COMMTASK)
Source: DFSMSdfp
System Action: The system issues messages about the problem.
Programmer Response: Respond as indicated for message
Programmer Response: Run the job again. If the error persists,
IEC151I.
contact the system programmer.
System Programmer Response: If the error recurs and the
System Programmer Response: Search problem reporting data
program is not in error, look at the messages in the job log for more
bases for a fix for the problem. If no fix exists, contact the IBM
information. Search problem reporting data bases for a fix for the
Support Center.
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job.
A37
A14 Explanation: The error occurred during end-of-volume processing.
This system completion code is accompanied by message IEC015I.
Explanation: The error occurred during processing of a CLOSE
Refer to the explanation of message IEC015I for complete informa-
macro instruction for a data set on a direct access device. This
tion about the task that was ended and for an explanation of the
system completion code is accompanied by message IEC216I. Refer
return code (rc in the message text) in register 15.
to the explanation of message IEC216I for complete information
about the task that was ended and for an explanation of the return Source: DFSMSdfp
code (rc in the message text) in register 15. Operator Response: Start a generalized trace facility (GTF) trace,
Source: DFSMSdfp and re-create the problem. Reply to message AHL100A with:
Programmer Response: Respond as indicated for message TRACE=SYS,USR,SLIP
IEC216I. On the DD statement for the data set in error, specify:
System Programmer Response: If the error recurs and the DCB=DIAGNS=TRACE
program is not in error, look at the messages in the job log for more
Programmer Response: Respond as indicated for message
information. Search problem reporting data bases for a fix for the
IEC015I.
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job. System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
A1A information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
Explanation: The catalog address space (CAS) modify task ended SYSOUT output and the program listing for the job.
abnormally because the modify task exceeded the allotted time for
processing. The task may have been waiting for some system
resource that is permanently unavailable.
Source: DFSMSdfp
System Action: The system attaches a new task to restore the
modify function.
SCC-184 OS/390 V2R8.0 MVS System Codes
A78 AC4
Check for program errors that incorrectly modify the FREEMAIN
A78
or STORAGE RELEASE macro expansion.
Explanation: An error occurred when the system tried to process
an RU or RC form of the FREEMAIN macro or the STORAGE A7A
RELEASE macro. A reason code in the SDWACRC field of the
system diagnostic work area (SDWA) explains the error: Explanation: The system detected an error in the input from an
invoker of the Service Processor Interface, or an internal error in
Code Explanation MVS. Register 15 contains the reason code in the format
04 The system queue area (SQA) storage to be freed over- X'0000xxrr', where rr is the reason code.
laps free storage. Code Explanation
08 The common service area (CSA) storage to be freed 06 The Service Processor Interface is unable to establish
overlaps free storage. the recovery environment.
0C The local system queue area (LSQA) storage to be freed Others The Service Processor Interface detected an unrecover-
overlaps free storage. able error.
10 The private area storage to be freed overlaps free Source: Service Processor Interface
storage.
System Action: The system abnormally ends the invoker of the
14 Part of the CSA to be freed is fixed. Service Processor Interface.
18 Part of the private area to be freed is fixed. System Programmer Response: For reason code X'06', deter-
1C The private area to be freed is associated with a data-in- mine why the system could not establish a recovery environment. If
virtual object. this cannot be done, or if the reason code is other than one previ-
ously listed, search problem reporting data bases for a fix. If no fix
20 The private area to be freed has been specified on the
exists, contact the IBM Support Center.
IARSUBSP IDENTIFY request, and is eligible to be
assigned to a subspace.
AC4
24 The task or SRB routine tried to free either SQA storage
that overlaps free storage or SQA storage that was Explanation: JES3 encountered an error while processing an
obtained by more than one request. IATXCNDB service call which specified (or defaulted to)
ABEND=YES. The abend reason code identifies the specific error.
28 The task or SRB routine tried to free either CSA storage
that overlaps free storage or CSA storage that was Code Explanation
obtained by more than one request. 00 Operation was successfully performed.
Source: Virtual storage manager (VSM) 04 The OPERATION requested is not supported by the
System Action: The system issues message IEA705I. The system IATXCNDB macro.
abnormally ends the current task. 08 An invalid IATXCNDB parameter list was passed to the
Programmer Response: Do the following: IATCNDB module. The eyecatcher in the parameter list
is not 'YCNDB '
For reason code X'1C', ensure that the program issued a DIV
UNIDENTIFY request before any FREEMAIN or STORAGE 0C An invalid IATXCNDB parameter list was passed to the
RELEASE request. IATCNDB module. The version indicator in the param-
eter list was not equal to the the current version.
For reason code X'24' or X'28', ensure that the start address,
length and subpool specified on the FREEMAIN or STORAGE 10 The input IATYCNDB (INCNDB parameter) passed to
RELEASE macro do not contain errors. the IATXCNDB INITIALIZE service did not have 'CNDB'
as its eyecatcher.
Ensure that the FREEMAIN or STORAGE RELEASE operands
do not specify a different subpool and/or key than the subpool or 14 The console id and console name parameters were
key of the storage you are trying to free. passed to the INITIALIZE service. These parameters are
mutually exclusive.
Ensure that the task control block (TCB) specified on the
FREEMAIN or STORAGE RELEASE request is the same one 18 An error return (>4) was received from the call to
specified on the corresponding GETMAIN or STORAGE CONVCON by the IATXCNDB INITIALIZE operation.
OBTAIN request. 1C The IATYCNDB was successfully initialized, but the
If a caller running in supervisor state and key 0 made the ori- console name/ID passed to the INITIALIZE routine was
ginal GETMAIN or STORAGE OBTAIN request, ensure that the not found in the JES3 console table. The IATYCNDB
corresponding FREEMAIN or STORAGE RELEASE request is has been initialized with a "non-JES3" console type and
also issued in supervisor state and key 0. the console ID and console name passed on the
IATXCNDB invocation and returned by MCS.
If a caller in supervisor state and key 0 requests storage in
subpool 0 or 250, the system satisfies this request with storage 20 The input IATYCNDB (CNDB parameter) address
from a different subpool. This situation is described in OS/390 passed to the IATXCNDB TRANSFER service was zero.
MVS Diagnosis: Reference. 24 The input IATYCNDB (CNDB parameter) passed to the
If the storage is eligible to be assigned to a subspace, make the IATXCNDB TRANSFER service did not have 'CNDB' as
storage ineligible by specifying the storage range on an its eyecatcher.
IARSUBSP UNIDENTIFY request before attempting to release 28 The output IATYCNDB (OUTCNDB parameter) address
the storage. passed to the IATXCNDB TRANSFER service was zero.
System Completion Codes SCC-185
AC4 AC4
2C The IATYCNDB passed to the VERIFY service did not 78 The input IATYCNDB (CNDB parameter) passed to the
have 'CNDB' as its eyecatcher. IATXCNDB EXTRACTROUT service did not have
'CNDB' as its eyecatcher.
30 An error return (>4) was received from the call to
CONVCON by the IATXCNDB service VERIFY opera- 7C The OUTROUT address passed to the IATXCNDB
tion. EXTRACTROUT service was zero.
34 The IATYCNDB was successfully converted to an 80 The input IATYCNDB (CNDB parameter) address
IATYCNDB at the current release level, but the console passed to the IATXCNDB UPDATE service was zero.
name in the down level CNDB was not found in the
84 The input IATYCNDB (CNDB parameter) passed to the
JES3 console table. The IATYCNDB has been initialized
IATXCNDB UPDATE service did not have 'CNDB' as its
with a "non-JES3" console type and the console ID
eyecatcher.
returned by MCS.
88 An attempt was made to pass the CONSID and
38 The input IATYCNDB (CNDB parameter) address
CONSNM parameters to the IATXCNDB service for an
passed to the IATXCNDB TRANSCONSID service was
UPDATE operation. These parameters are mutually
zero.
exclusive.
3C The input IATYCNDB (CNDB parameter) passed to the
8C An error return (>4) was received from the call to
IATXCNDB TRANSCONSID service did not have 'CNDB'
CONVCON by the IATXCNDB UPDATE operation.
as its eyecatcher.
90 The IATYCNDB was successfully updated, but the
40 The output IATYCNDB (OUTCNDB parameter) address
console name/ID passed to the UPDATE routine was not
passed to the IATXCNDB TRANSCONSID service was
found in the JES3 console table. The IATYCNDB has
zero.
been Updated with a "non-JES3" console type and the
44 The input IATYCNDB (CNDB parameter) address console ID and console name passed on the IATXCNDB
passed to the IATXCNDB TRANSROUT service was invocation and returned by MCS.
zero.
94 The input IATYCNDB (CNDB parameter) address
48 The input IATYCNDB (CNDB parameter) passed to the passed to the IATXCNDB RESET service was zero.
IATXCNDB TRANSROUT service did not have 'CNDB'
98 The input IATYCNDB (CNDB parameter) passed to the
as its eyecatcher.
IATXCNDB RESET service did not have 'CNDB' as its
4C The output IATYCNDB (OUTCNDB parameter) address eyecatcher.
passed to the IATXCNDB TRANSROUT service was
A8 The input IATYCNDB (CNDB parameter) address
zero.
passed to the IATXCNDB EXTRACTCART service was
50 The input IATYCNDB (CNDB parameter) address zero.
passed to the IATXCNDB EXTRACTCONSID service
AC The input IATYCNDB (CNDB parameter) passed to the
was zero.
IATXCNDB EXTRACTCART service did not have
54 The input IATYCNDB (CNDB parameter) passed to the 'CNDB' as its eyecatcher.
IATXCNDB EXTRACTCONSID service did not have
B0 The OUTROUT address passed to the IATXCNDB
'CNDB' as its eyecatcher.
EXTRACTCART service was zero.
58 The OUTCONSID address passed to the IATXCNDB
Source: JES3
EXTRACTCONSID service was zero.
System Action: The IATXCNDB request processing is ended.
5C The input IATYCNDB (CNDB parameter) address
passed to the IATXCNDB EXTRACTCONSNAME System Programmer Response: To determine the error, perform
service was zero. the following:
60 The input IATYCNDB (CNDB parameter) passed to the 1. If called from the JES3 main task, locate the ACALL and
IATXCNDB EXTRACTCONSNAME service did not have RETURN trace entry for the IATXCNDB macro.
'CNDB' as its eyecatcher. 2. Register 1 of the ACALL trace entry contains the address of the
64 The OUTCONSNAME address passed to the parameter list used by the IATXCNDB macro. The parameter list
IATXCNDB EXTRACTCONSNAME service was zero. is mapped by a DSECT generated from an IATXCNDB MF=L
call.
68 The input IATYCNDB (CNDB parameter) address
passed to the IATXCNDB EXTRACTCONSTYPE service 3. Use the trace table to locate the module that issued the
was zero. IATXCNDB macro. Register 14 of the ACALL entry in the trace
table contains the return address and register 10 contains the
6C The input IATYCNDB (CNDB parameter) passed to the
base register.
IATXCNDB EXTRACTCONSTYPE service did not have
'CNDB' as its eyecatcher. 4. When IATXCNDB is invoked from a user's address space, the
caller issued a BASSM R14,R15 from the IATXCNDB macro.
70 The OUTCONSTYPE address passed to the IATXCNDB
The registers are then saved on the linkage stack by IATCNDB
EXTRACTCONSTYPE service was zero.
via 'BAKR R14,R0'.
74 The input IATYCNDB (CNDB parameter) address
5. Use the abend reason code to identify the cause of the error.
passed to the IATXCNDB EXTRACTROUT service was
zero. 6. Correct the parameter list in the module that issued the
IATXCNDB macro.
SCC-186 OS/390 V2R8.0 MVS System Codes
AC5 AC7
Code Explanation and Programmer Response
AC5
00000000 Explanation: The caller of the enqueue timer queue
Explanation: An unexpected error was encountered during internal
element (TQE) service did not hold the dispatcher lock.
RACF processing datasharing or sysplex communication functions. A
hexadecimal reason code is given in register 15. Action: Correct the program to obtain the dispatcher
lock before calling the enqueue TQE service.
Code Explanation
00000001 Explanation: The caller of the dequeue TQE service did
03 An error occurred when attempting to obtain storage.
not hold the dispatcher lock.
05 An error occurred when attempting to free storage.
Action: Correct the program to obtain the dispatcher
07 After IXCJOIN, all other members left the data sharing lock before calling the dequeue TQE service.
group before the group data set name and range table
00000002 Explanation: The STIMER/STIMERM service detected
were received. One reason this can happen is that you
an error when processing an STIMER/STIMERM WAIT
are IPLing a system and all other systems in the group
request.
were simultaneously re-IPLed. If this is the case, re-IPL
your system. Otherwise, contact the IBM support center. Action: Contact the IBM Support Center.
08 An XCF service failed during sysplex communication. | 00000003 Explanation: An enqueue request for a TQE failed
| because the TQE to be added is already on the real
0F XCF services failed. RACF will try to restart the RACF
| TQE queue. The original STIMER or SETDIE request
datasharing address space.
| represented by ths TQE will not occur. For this reason
10 This abend occurs when a system in datasharing mode | code, register 2 contains the address of the caller of
is put into failsoft mode due to the occurrence of some | Timer services.
other error.
| Action: Correct the program to not schedule the same
nn An internal RACF error has occurred. Contact the IBM | TQE twice.
support center.
00000004 Explanation: Internal error
System Action: A dump is taken in all cases. If the abend occurs
Action: Contact the IBM support center.
in the RACF data sharing address space, the address space will be
restarted. If the abend occurs in the master address space, the 00000005 Explanation: Internal error
system will enter failsoft mode. Action: Contact the IBM support center.
Programmer Response: If the abend occurred in the master 00010000 Explanation: The IEAMCPUF macro was issued by an
address space, the system will need to be re-IPLed in order for enabled caller.
RACF to be made active again. If necessary, contact your program-
ming support personnel. Action: Correct the program so that IEAMCPUF is
issued while running disabled.
AC6 00020000 Explanation: The affinity service, IEAAFFN, was
invoked by a caller in access register (AR) mode.
Explanation: IMS uses this code when forcibly terminating one
MVS task from another MVS task. There are two situations where Action Correct the program so that IEAAFFN is invoked
this occurs: in primary ASC mode.
1. An ESTAE routine has gained control due to an abend in the 00020001 Explanation: The affinity service, IEAAFFN, could not
system. The abended task (ESTAE) attempts to purge the log access the storage containing the caller's parameter list.
buffers and signals the physical log task of its intention. If the Action: Correct the program so that the storage con-
ESTAE task does not receive a response within one second, the taining the caller's parameter list is accessible.
physical log task is terminated with this abend code and log
00030000 Explanation: A name/token callable service, IEANTCRS
buffers are purged.
or IEANTDLS, could not access the storage containing
2. The DBRC instance required for this instance of ILS has termi- the caller's parameter list or parameter storage.
nated. All remaining ILS instances dependent upon the abended
Action: Correct the program so that the storage con-
DBRC will wait for that DBRC and abend with reason code
taining the caller's parameter list or parameter storage is
X'01'.
accessible.
System Action: IMS continues termination.
00030001 Explanation: A name/token callable service, IEANTCRS
System Programmer Response: Determine primary cause of or IEANTDLS, could not access the caller's home
failure and take appropriate action. address space.
Action: Retry the request.
AC7
00030002 Explanation: The name/token pair callable service,
Explanation: A supervisor service was issued in an incorrect envi- IEANTDLS, found an internal error.
ronment. Register 15 contains a hexadecimal reason code.
Action: Retry the request.
Source: Timer supervision, supervisor control, context services, or
registration services 00040000 Explanation: Internal error.
System Action: The system ends the current unit of work. Action: Contact the IBM support center.
Programmer Response: Respond according to the reason code: 00040001 Explanation: Internal error.
Action: Contact the IBM support center.
System Completion Codes SCC-187
AC7 AC7
00040002 Explanation: Internal error. many RBs to be created. If the source of the problem
cannot be determined, search problem reporting data
Action: Contact the IBM support center.
bases for a fix of the problem. If no fix exits, contact the
00040003 Explanation: Internal error. IBM support center.
Action: Contact the IBM support center. 00080000 Explanation: The invocation version of the IEAMSCHD
00040004 Explanation: Internal error. macro is not supported by this level of the service
routine.
Action: Contact the IBM support center.
Action: You must be at least at level MVS/ESA SP 5.2
00040005 Explanation: Internal error.
to use this service.
Action: Contact the IBM support center.
00080001 Explanation: The space token specified via the
00050000 Explanation: The caller of the SCHEDIRB macro did TARGETSTOKEN keyword on IEAMSCHD is not valid.
not hold the local lock.
Action: Retry the request specifying a valid address
Action: Correct the program so that it holds the local space token.
lock before invoking the SCHEDIRB macro.
00080002 Explanation: The enclave token specified on
00050001 Explanation: A program invoked the SCHEDIRB macro IEAMSCHD was not a valid token.
with one of the following errors:
Action: Retry the request specifying a valid enclave
The caller's cross memory mode was not token.
HASN=PASN, which is required.
00080003 Explanation: CRYPTO was specified on the FEATURE
The caller's ASC mode of AR was correct, but AR1 keyword of IEAMSCHD, but there are no processors
does not contain the primary ALET. with the Integrated Cryptographic Feature online.
Action: Correct the program so that the cross memory Action:
mode is HASN=PASN or PASN=HASN.
00080004 Explanation: A DIE routine issued IEAMSCHD to
00050002 Explanation: The caller of the SCHEDIRB macro speci- attempt to schedule an SRB with PRIORITY=CURRENT.
fied the RBPTR keyword to schedule a directed interrupt
Action: Correct the program so that the routine does not
request block (IRB) while in SRB mode. The calling
specify PRIORITY=CURRENT on IEAMSCHD.
program cannot schedule directed IRBs while in SRB
mode. 00080005 Explanation: The space token specified via the
PURGESTOKEN keyword on IEAMSCHD is not valid.
Action: Correct the program so that it is not in SRB
mode if you want to specify the RBPTR keyword on the Action: Retry the request specifying a valid
SCHEDIRB macro to schedule a directed IRB. PURGESTOKEN token.
00050003 Explanation: The caller of the SCHEDIRB macro speci- 00080006 Explanation: The space token specified via the
fied an incorrect task control block (TCB) address on the CLIENTSTOKEN keyword on IEAMSCHD is not valid.
TCBPTR keyword. Action: Retry the request specifying a valid
Action: Correct the program so that it specifies a valid CLIENTSTOKEN.
TCB address in the TCBPTR keyword on the 00080007 Explanation: The parameter list for IEAMSCHD is not in
SCHEDIRB macro. the user's primary address space.
00050004 Explanation: The caller of the SCHEDIRB macro speci- Action: Correct the program so that the parameter list is
fied an incorrect interrupt queue element (IQE) address addressable.
on the IQEPTR keyword.
00080009 Explanation: The caller of IEAMSCHD specified
Action: Correct the program so that it specifies a valid SYNCH=YES but held a lock.
IQE address on the IQEPTR keyword on the SCHEDIRB
Action: Ensure that no locks are held when
macro.
SYNCH=YES is specified on IEAMSCHD.
00050005 Explanation: The caller of the SCHEDIRB macro sched-
00090000 Explanation: Internal error
uled a directed IRB to the current task. However, the
current task is an error task and the error IRB is active. Action: Contact the IBM support center.
Action: Correct the program so that it does not specify 00090001 Explanation: Internal error
the RBPTR keyword on the SCHEDIRB if the current
Action: Contact the IBM support center.
task is the error task and the error IRB is active.
00090002 Explanation: Internal error
00050006 Explanation: The caller of the SCHEDIRB macro speci-
fied and IQE whose IQETCB field pointed to a TCB Action: Contact the IBM support center.
which is not valid. 00090003 Explanation: Internal error
Action: Correct the program so that it specifies a valid Action: Contact the IBM support center.
TCB address in the IQE field IQETCB.
000A0000 Explanation: Internal error
00060000 Explanation: Internal error
Action: Contact the IBM support center.
Action: Contact the IBM support center.
000B0000 Explanation: Internal error
00070000 Explanation: The request block (RB) chain is circular or
Action: Contact the IBM support center.
there are a very large number or RBs on the RB chain.
Action: This may be caused by a loop which caused
SCC-188 OS/390 V2R8.0 MVS System Codes
AC7 AC7
000C0000 Explanation: Internal error 00120001 Explanation: For a call to the Delete_Context_Interest
service, the parameters are not addressable. The
Action: Contact the IBM support center.
system rejects the service call. The system abnormally
000C0001 Explanation: Internal error ends the calling program.
Action: Contact the IBM support center. Action: Check the calling program for a probable coding
000D0000 Explanation The SCHEDULE macro detected a circular error. Correct the program and rerun it.
SRB chain. The reason may be that the SCHEDULE 00130000 Explanation: For a call to the Express_Context_Interest
macro was issued more than once for an SRB. service, the parameters are not in the primary address
Action: Ensure that the program does not issue space. The system rejects the service call. The system
SCHEDULE for the SRB again before the SRB is dis- abnormally ends the calling program.
patched. General purpose register 3 points to the SRB. Action: Check the calling program for a probable coding
000D0001 Explanation The PURGEDQ macro detected a circular error. Correct the program and rerun it.
SRB chain. The reason may be that the SCHEDULE 00130001 Explanation: For a call to the Express_Context_Interest
macro was issued more than once for an SRB. service, the parameters are not addressable. The
Action: Ensure that the program does not issue system rejects the service call. The system abnormally
SCHEDULE for the SRB again before the SRB is dis- ends the calling program.
patched. General purpose register 3 points to the SRB. Action: Check the calling program for a probable coding
000D0002 Explanation: Internal error error. Correct the program and rerun it.
Action: Contact the IBM support center. 00140000 Explanation: For a call to the End_Context service, the
parameters are not in the primary address space. The
000D0003 Explanation: The SCHEDULE macro detected an SRB
system rejects the service call. The system abnormally
which is not valid. The reason may be that the
ends the calling program.
SCHEDULE macro was issued more than once for an
SRB. Action: Check the calling program for a probable coding
error. Correct the program and rerun it.
Action: Ensure that the program does not issue
SCHEDULE for the SRB again before the SRB is dis- 00140001 Explanation: For a call to the End_Context service, the
patched. The SRB and the associated WEB are parameters are not addressable. The system rejects the
recorded in LOGREC. service call. The system abnormally ends the calling
program.
000E0000 Explanation: Internal error
Action: Check the calling program for a probable coding
Action: Contact the IBM support center.
error. Correct the program and rerun it.
000E0001 Explanation: Internal error
00150000 Explanation: For a call to the Switch_Context service,
Action: Contact the IBM support center. the parameters are not in the primary address space.
The system rejects the service call. The system abnor-
000F0000 Explanation: Internal error
mally ends the calling program.
Action: Contact the IBM support center.
Action: Check the calling program for a probable coding
00100000 Explanation: Internal error error. Correct the program and rerun it.
Action: Contact the IBM support center. 00150001 Explanation: For a call to the Switch_Context service,
00100001 Explanation: Internal error the parameters are not addressable. The system rejects
the service call. The system abnormally ends the calling
Action: Contact the IBM support center.
program.
00110000 Explanation: For a call to the Begin_Context service,
Action: Check the calling program for a probable coding
the parameters are not in the primary address space.
error. Correct the program and rerun it.
The system rejects the service call. The system abnor-
mally ends the calling program. 00160000 Explanation: For a call to the
Retrieve_Context_Interest_Data service, the parameters
Action: Check the calling program for a probable coding
are not in the primary address space. The system
error. Correct the program and rerun it.
rejects the service call. The system abnormally ends the
00110001 Explanation: For a call to the Begin_Context service, calling program.
the parameters are not addressable. The system rejects
Action: Check the calling program for a probable coding
the service call. The system abnormally ends the calling
error. Correct the program and rerun it.
program.
00160001 Explanation: For a call to the
Action: Check the calling program for a probable coding
Retrieve_Context_Interest_Data service, the parameters
error. Correct the program and rerun it.
are not addressable. The system rejects the service
00120000 Explanation: For a call to the Delete_Context_Interest call. The system abnormally ends the calling program.
service, the parameters are not in the primary address
Action: Check the calling program for a probable coding
space. The system rejects the service call. The system
error. Correct the program and rerun it.
abnormally ends the calling program.
00170000 Explanation: For a call to the
Action: Check the calling program for a probable coding
Set_Context_Interest_Data service, the parameters are
error. Correct the program and rerun it.
not in the primary address space. The system rejects the
service call. The system abnormally ends the calling
program.
System Completion Codes SCC-189
AC7 AC7
Action: Check the calling program for a probable coding rejects the service call. The system abnormally ends the
error. Correct the program and rerun it. calling program.
00170001 Explanation: For a call to the Action:Check the calling program for a probable coding
Set_Context_Interest_Data service, the parameters are error. Correct the problem and rerun it.
not addressable. The system rejects the service call.
00220001 Explanation:For a call to the
The system abnormally ends the calling program.
Retrieve_Current_Context_Token service, the parame-
Action: Check the calling program for a probable coding ters are not addressable. The system rejects the service
error. Correct the program and rerun it. call. The system abnormally ends the calling program.
00180000 Explanation:Internal Error Action:Check the calling program for a probable coding
error. Correct the problem and rerun it.
Action:Contact the IBM Support Center.
00310000 Explanation: For a call to the
00180001 Explanation:Internal Error
Unregister_Resource_Manager service, the parameters
Action:Contact the IBM Support Center. are not in the primary address space. The system
00190001 Explanation:Internal Error rejects the service call. The system abnormally ends the
calling program.
Action:Contact the IBM Support Center.
Action: Check the calling program for a probable coding
00190002 Explanation:Internal Error
error. Correct the program and rerun it.
Action:Contact the IBM Support Center.
00310001 Explanation: For a call to the
00190003 Explanation:Internal Error Unregister_Resource_Manager service, the parameters
are not addressable. The system rejects the service call.
Action:Contact the IBM Support Center.
The system abnormally ends the calling program.
00190004 Explanation:Internal Error
Action: Check the calling program for a probable coding
Action:Contact the IBM Support Center. error. Correct the program and rerun it.
00190005 Explanation:Internal Error 00330000 Explanation: For a call to the
Action:Contact the IBM Support Center. Register_Resource_Manager service, the parameters
are not in the primary address space. The system
00190006 Explanation:Internal Error
rejects the service call. The system abnormally ends the
Action:Contact the IBM Support Center. calling program.
00190007 Explanation:Internal Error Action: Check the calling program for a probable coding
error. Correct the program and rerun it.
Action:Contact the IBM Support Center.
00330001 Explanation: For a call to the
00190008 Explanation:Internal Error
Register_Resource_Manager service, the parameters
Action:Contact the IBM Support Center. are not addressable. The system rejects the service call.
00200000 Explanation:For a call to the Set_Context_Data service, The system abnormally ends the calling program.
the parameters are not in the primary address space. Action: Check the calling program for a probable coding
The system rejects the service call. The system abnor- error. Correct the program and rerun it.
mally ends the calling program.
00350000 Explanation: For a call to the
Action:Check the calling program for a probable coding Retrieve_Resource_Manager_Data service, the parame-
error. Correct the problem and rerun it. ters are not in the primary address space. The system
00200001 Explanation:For a call to the Set_Context_Data service, rejects the service call. The system abnormally ends the
the parameters are not addressable. The system rejects calling program.
the service call. The system abnormally ends the calling Action: Check the calling program for a probable coding
program. error. Correct the program and rerun it.
Action:Check the calling program for a probable coding 00350001 Explanation: For a call to the
error. Correct the problem and rerun it. Retrieve_Resource_Manager_Data service, the parame-
00210000 Explanation:For a call to the Retrieve_Context_Data ters are not addressable. The system rejects the service
service, the parameters are not in the primary address call. The system abnormally ends the calling program.
space. The system rejects the service call. The system Action: Check the calling program for a probable coding
abnormally ends the calling program. error. Correct the program and rerun it.
Action:Check the calling program for a probable coding 00360000 Explanation: For a call to the Set_Exit_Information
error. Correct the problem and rerun it. service, the parameters are not in the primary address
00210001 Explanation:For a call to the Retrieve_Context_Data space. The system rejects the service call. The system
service, the parameters are not addressable. The abnormally ends the calling program.
system rejects the service call. The system abnormally Action: Check the calling program for a probable coding
ends the calling program. error. Correct the program and rerun it.
Action:Check the calling program for a probable coding 00360001 Explanation: For a call to the Set_Exit_Information
error. Correct the problem and rerun it. service, the parameters are not addressable. The
00220000 Explanation:For a call to the system rejects the service call. The system abnormally
Retrieve_Current_Context_Token service, the parame- ends the calling program.
ters are not in the primary address space. The system
SCC-190 OS/390 V2R8.0 MVS System Codes
AFB AFB
Action: Check the calling program for a probable coding
B04
error. Correct the program and rerun it.
Explanation: An error occurred when the system tried to process
00360002 Explanation: For a call to the Set_Exit_Information
an EC, EU, LC, LU, VC, or VU form of the GETMAIN macro. A
service, the parameters are not addressable. However,
reason code in the SDWACRC field of the system diagnostic work
the call successfully set exit routines with the exit
area (SDWA) explains the error:
manager. The system abnormally ends the calling
program. Code Explanation
Action: Check the calling program for a probable coding 04 The GETMAIN macro requested an undefined subpool.
error. Correct the program and rerun it. 08 The program issuing the GETMAIN macro is not author-
00400000 Explanation: Internal Error ized to request system subpools.
Action: Contact the IBM Support Center. 14 A local branch entry caller of the GETMAIN macro did
not hold the local lock for the address space that is cur-
00400001 Explanation: Internal Error
rently addressable.
Action: Contact the IBM Support Center.
18 An incorrect task control block (TCB) address was speci-
00400002 Explanation: Internal Error fied on a branch entry request.
Action: Contact the IBM Support Center. 1C The address space control block (ASCB) address speci-
fied on a branch entry request was not the current
AFB ASCB.
Explanation: While JES3 dynamic support program (DSP) for 20 Using the GETMAIN macro or its equivalent branch
systems network architecture (SNA) remote job processing (RJP) entry, the caller tried to obtain disabled reference
was executing as a JES3 subtask or under an SRB, a JES3 module storage that resides above 16 megabytes. This entry
IATSNDA, IATSNDE, IATSNDM, IATSNDR, IATSNDT, IATSNDU, or only satisfies requests for storage below 16 megabytes.
IATSNDV attempted to reuse a still-active request parameter list Source: Virtual storage manager (VSM)
(RPL).
System Action: The system issues message IEA705I. The system
Source: JES3 abnormally ends the current task.
System Action: The system cancels the session associated with Programmer Response: Depending on the reason code, do one of
the RPL and writes a dump. The system continues processing all the following:
other sessions, including those associated with the same work
station. Code Response
Programmer Response: Analyze the dump to determine which 04 Ensure that the subpool is not incorrectly specified or
RPL is about to be overlaid and what data is about to be sent or modified.
received. 08 If the program requires system subpools, ensure that the
program resides in an authorized program library.
1C Specify the correct ASCB address on the FREEMAIN
B00 macro.
Explanation: During processing of an I/O request, a program check 20 Change the program to request expanded storage.
occurred in an execute channel program (EXCP) procedure.
ALL Check for program errors that could modify the param-
Source: Execute channel program (EXCP) eter list.
System Action: The system abnormally ends the current task. The
system writes a logrec data set error record. B05
Programmer Response: Check the problem program for the error. Explanation: An error occurred when the system tried to process
If the error cannot be determined, run the job again, requesting an an EC, EU, LC, LU, VC, or VU form of the FREEMAIN macro. A
ABEND dump. Notify the system programmer. reason code in the SDWACRC field of the system diagnostic work
System Programmer Response: In the dump, look at field area (SDWA) explains the error:
TCBEXCPD at offset X'C0' in the task control block (TCB) for the Code Explanation
current task. TCBEXCPD points to the EXCP debugging area
(XDBA). The XDBA contains diagnostic data associated with the 04 The FREEMAIN macro tried to free storage in an unde-
EXCP processor. fined subpool.
If the error recurs and the program is not in error, look at the mes- 08 The program issuing the FREEMAIN macro is not
sages in the job log for more information. Search problem reporting authorized to free storage in system subpools.
data bases for a fix for the problem. If no fix exists, contact the IBM 14 A local branch entry caller of the FREEMAIN macro did
Support Center. Provide the logrec data set error record, the job not hold the local lock for the address space that is cur-
control language (JCL), the program listing, and the assembly listing rently addressable.
for the job.
18 Incorrect task control block (TCB) address specified on a
branch entry request.
1C The address space control block (ASCB) address speci-
fied on a branch entry request was not the current
ASCB.
System Completion Codes SCC-191
B06 B1A
20 Using a FREEMAIN macro or its equivalent branch Programmer Response: Depending on the reason code, do one of
entry, the caller attempted to free disabled reference the following:
storage that resides above 16 megabytes. This entry
Code Response
only satisfies requests for storage below 16 megabytes.
04 Ensure that the subpool is not incorrectly specified or
Source: Virtual storage manager (VSM)
modified.
System Action: The system issues message IEA705I. The system
08 If the program requires system subpools, ensure that the
abnormally ends the current task.
program resides in an authorized program library.
Programmer Response: Depending on the reason code, do one of
1C Specify the correct ASCB address on the FREEMAIN
the following:
macro.
Code Response
20 Change the program to request expanded storage.
04 Ensure that the subpool is not incorrectly specified or
ALL Check for program errors that could modify the param-
modified.
eter list.
08 If the program requires system subpools, ensure that the
program resides in an authorized program library. B13
1C Specify the correct ASCB address on the FREEMAIN Explanation: The error occurred during processing of an OPEN
macro. macro for a data set on an impact printer. This system completion
20 Change the program to request expanded storage. code is accompanied by message IEC152I. Refer to the explanation
of message IEC152I for complete information about the task that
ALL Check for program errors that could modify the param-
was ended and for an explanation of the return code (rc in the
eter list.
message text) in register 15.
Source: DFSMSdfp
B06
Programmer Response: Respond as indicated for message
Explanation: During input/output activity, a system error task oper-
IEC152I.
ating in behalf of a user task was abnormally ending.
System Programmer Response: If the error recurs and the
Source: Input/output supervisor (IOS)
program is not in error, look at the messages in the job log for more
System Action: The system reinstates the system error task and information. Search problem reporting data bases for a fix for the
abnormally ends the user task. problem. If no fix exists, contact the IBM Support Center. Provide the
Programmer Response: Run the job again. JCL and the program listing for the job.
B0A B14
Explanation: An error occurred when the system tried to process Explanation: The error occurred during processing of a CLOSE
an R form of the GETMAIN or FREEMAIN macro. A reason code in macro instruction for a partitioned data set opened for output to a
the SDWACRC field of the system diagnostic work area (SDWA) member. This system completion code is accompanied by message
explains the error: IEC217I. Refer to the explanation of message IEC217I for complete
information about the task that was ended and for an explanation of
Code Explanation
the return code (rc in the message text) in register 15.
04 The macro tried to obtain or free storage in an undefined
Source: DFSMSdfp
subpool.
Programmer Response: Respond as indicated for message
08 The program issuing the macro is not authorized to
IEC217I.
obtain or free storage in system subpools.
System Programmer Response: If the error recurs and the
14 A local branch entry caller of the GETMAIN or
program is not in error, look at the messages in the job log for more
FREEMAIN macro did not hold the local lock for the
information. Search problem reporting data bases for a fix for the
address space that is currently addressable.
problem. If no fix exists, contact the IBM Support Center. Provide the
18 An incorrect task control block (TCB) address specified JCL and the program listing for the job.
on a branch entry request.
1C The address space control block (ASCB) address speci- B1A
fied on a branch entry request was not the current Explanation: The user address space catalog ESTAE module
ASCB. IGG0CLHC requested the abnormal end of the catalog address
20 The caller tried to release disabled reference storage space (CAS) service task. An abnormal end occurred in the user
using a GETMAIN/FREEMAIN macro with the R operand address space during catalog recall processing.
or its equivalent branch entry. This entry only satisfies Source: DFSMSdfp
requests for storage below 16 megabytes. Disabled ref-
erence subpools do not reside below 16 megabytes. Programmer Response: Use the following information to deter-
mine the cause of the error:
Source: Virtual storage manager (VSM)
The SYS1.DUMP produced for this abnormal end.
System Action: The system issues message IEA705I. The system
abnormally ends the current task. The SYS.DUMP produced by the abnormal end of the user
address space.
SCC-192 OS/390 V2R8.0 MVS System Codes
B23 B78
authorized program facility (APF) authorized. STORAGE
B23
users must be supervisor state, or key 0.
Explanation: A task issued a WTOR macro. Before the operator
0C A global branch entry caller of the GETMAIN or
replied to the WTOR message, a system problem occurred, leaving
FREEMAIN macro tried to obtain or free a nonglobal
the message unanswered.
subpool.
Source: Communications task (COMMTASK)
10 The LOC parameter is not valid. Virtual storage manager
System Action: The system abnormally ends the task that issued (VSM) received a request for either a fetch-protected
the WTOR. The system issues message IEE824A or IEE824E. local system queue area (LSQA) or a disabled reference
Operator Response: See the operator response for message subpool that resides below 16 megabytes. Fetch-
IEE824A or IEE824E. Restart the task that ended with abend code protected LSQA and disabled reference subpools are
X'B23'. supported only above 16 megabytes.
14 A local branch entry caller of the GETMAIN or
B2D FREEMAIN macro did not hold the local lock for the
address space that is currently addressable.
Explanation: A program requested an overlay. In answer to the
request, the overlay supervisor was using program fetch to load a 18 An incorrect task control block (TCB) address was speci-
program segment from the library. While the fetch recovery routine fied on a branch entry or STORAGE request.
was processing because of a previous abend, a program check 1C The address space control block (ASCB) address speci-
occurred. fied on a branch entry request was not the current
Note: Overlay programs run only in 24-bit addressing mode, not in ASCB.
31-bit addressing mode. 24 The user of the STORAGE macro is disabled.
Source: Overlay supervisor 28 A caller that is not in supervisor state, or keys 0 through
System Action: The system abnormally ends the program that 7, specified the ALET parameter or the TCBADDR
requested the overlay. The system writes an ABEND dump, if a parameter on the STORAGE macro.
dump DD statement is provided. 2C The caller violated the STORAGE service's locking
Programmer Response: Check the linkage editor input to be sure restrictions by holding a suspend lock that is not the
the program is designed correctly. Correct the errors; then local lock of the target address space.
assemble, link edit, and run the program again. 30 The specified ALET does not translate to a valid
STOKEN.
B37 34 The STOKEN does not translate to a valid ASCB; the
Explanation: The error was detected by the end-of-volume routine. address space from which the storage is to be obtained
This system completion code is accompanied by message IEC030I. or released is not valid for cross memory access.
Refer to the explanation of message IEC030I for complete informa- 38 The target address space is the master scheduler's
tion about the task that was ended and for an explanation of the address space, which is not the home address space.
return code (rc in the message text) in register 15.
3C The target address space is either in the process of
Source: DFSMSdfp ending, or has ended.
Programmer Response: Respond as indicated for message 40 A user violated serialization requirements by calling
IEC030I. global branch entry GETMAIN or FREEMAIN while
System Programmer Response: If the error recurs and the enabled.
program is not in error, look at the messages in the job log for more 44 A program issued a SETLOCK OBTAIN,TYPE=VSMFIX
information. Search problem reporting data bases for a fix for the macro before issuing a VSMLIST or VSMLOC request.
problem. If no fix exists, contact the IBM Support Center. Provide the The program or an associated FRR issued a GETMAIN,
JCL and the program listing for the job. FREEMAIN, or STORAGE request before issuing
SETLOCK RELEASE,TYPE=VSMFIX.
B78
48 A program issued a SETLOCK
Explanation: The error occurred when the system tried to run one OBTAIN,TYPE=VSMPAG macro before issuing a
of the following: VSMLOC request. The program or an associated FRR
An RC, RU, VRC, or VRU GETMAIN macro issued a GETMAIN, FREEMAIN, or STORAGE request
An RC or RU FREEMAIN macro before issuing SETLOCK RELEASE,TYPE=VSMPAG.
A STORAGE macro. 4C An incorrect subpool was specified on a GETMAIN or
A reason code in the SDWACRC field of the system diagnostic work STORAGE OBTAIN request with the LOC=EXPLICIT
area (SDWA) explains the error. The reason code appears in the keyword specified. Valid subpools for unauthorized pro-
form xxxxxxyy, where xxxxxx is the internal reason for the error, and grams are:
yy is described in the following table: 0-127
Code Explanation 131-132
04 The macro tried to obtain or free storage in an undefined Valid subpools for authorized programs are:
subpool. 0-127
08 The program issuing the macro is not authorized to 129-132
obtain or free storage in system subpools. GETMAIN or 240
FREEMAIN users must be supervisor state, key 0, or 250-252
System Completion Codes SCC-193
BC2 BC3
50 A GETMAIN or STORAGE OBTAIN request failed | Application Programmer Response: Search problem reporting data
because the address specified on the INADDR keyword | bases for a fix for the problem. If no fix exists, contact the IBM
was greater than 16 megabytes and the central storage | Support Center and provide the SVC dump.
backing specified on the LOC keyword was BELOW.
The virtual storage address specified on INADDR and BC3
the central storage backing specified on the
LOC=EXPLICIT must be a valid combination. For Explanation: The JES3 dump job server address space encount-
example, if the address specified on INADDR is for ered an error. The abend reason code identifies the specific error.
virtual storage above 16 megabytes, specify Code Explanation
LOC=EXPLICIT or LOC=(EXPLICIT,ANY). The following
01 The ASEXT macro returned a non-zero return code
combinations are valid:
while the dump job server space was attempting to
virtual above, central any extract the address space parameters. Registers 2 and 3
virtual any, central any when the BC3 abend is issued contain the return and
virtual below, central below reason codes from the ASEXT macro call.
virtual below, central any
02 The address of the extracted parameter string returned
54 A GETMAIN or STORAGE OBTAIN request failed from the ASEXT macro is zero.
because the address specified on the INADDR keyword
03 The ALESERV macro returned a non-zero return code
was not on an doubleword boundary.
while the dump job server space was attempting to add
Source: Virtual storage manager (VSM) JES3's ALET to its access list. Registers 2 and 3 when
System Action: The system issues message IEA705I. The system the BC3 abend is issued contain the return and reason
abnormally ends the current task. codes from the ALESERV macro call.
Programmer Response: Depending on the reason code, do one of 04 The ALESERV macro returned a non-zero return code
the following: while the dump job server address space was attempting
to extract its STOKEN. Registers 2 and 3 when the BC3
Code Response abend is issued contain the return and reason codes
04 Ensure that the specified subpool is not incorrectly spec- from the ALESERV macro call.
ified or modified. 05 The ALESERV macro returned a non-zero return code
08 If the program requires system subpools, ensure that the while the dump job server address space was attempting
program resides in an authorized program library. Users to extract JES3's STOKEN. Registers 2 and 3 when the
of the STORAGE macro must also switch to supervisor BC3 abend is issued contain the return and reason
state, or key 0. codes from the ALESERV macro call.
0C Note that a global branch entry request can only request 06 The STOKEN associated with the JES3 address space
global subpools, that is, system queue area (SQA) sub- that started the dump job server address space is not
pools or common service area (CSA) subpools. the same as the current JES3 address space.
10 An incorrect bit combination for the LOC operand was 07 The STIMERM macro returned a non-zero return code
put into an input register. while the dump job server address space was attempting
to setup status monitoring for the JES3 address space.
14 Ensure that a local branch entry caller holds the local
Register 2 when the BC3 abend is issued contains the
lock for the currently addressable address space.
return code from the STIMERM macro call.
44 Issue the SETLOCK RELEASE,TYPE=VSMFIX macro
08 The dump job server's ECB was posted with an incorrect
before you issue a GETMAIN, FREEMAIN, or
function code. Register 2 when the BC3 abend is
STORAGE macro.
issued contains the function code.
48 Issue the SETLOCK RELEASE,TYPE=VSMPAG macro
Source: JES3
before you issue a GETMAIN, FREEMAIN, or
STORAGE macro. System Action: A dump of the JES3 dump job server address and
the JES3 address space is taken. The dump job server address
ALL Check for program errors that modify the parameter list.
space ends and the Dump Job DSP in the JES3 address space that
controls the server address space also ends.
| BC2
Programmer Response: Contact IBM support and provide the fol-
| Explanation: During the processing of an FSI call, validation of cell lowing documentation:
| failed before returning it to cellpool.
The BC3 abend reason code.
| Code Explanation
The information in registers 2 and 3 at the time of error (if appli-
| 04 IAZFSIT work area cell pool. cable).
| 08 FSI trace work area cell pool. The dump taken by the JES3 server address space.
| 0C Save area across FSI function call cell pool. The SYSLOG around the time of error.
| Source: Functional subsystem interface (FSI) The *CALL DJ command that caused the JES3 dump job server
| System Action: The system issues an SVC dump. address space to be started.
The dump job DSP log (if available).
SCC-194 OS/390 V2R8.0 MVS System Codes
BC5 BFB
DFP could not successfully close one or more of the task's data
BC5
sets that was still open because the DCB for the data set had
Explanation: The system terminated an address space. been incorrectly modified.
Code Explanation Examples of how the DCB could be incorrectly modified are:
01 The system attempted to rebuild its work unit queues – A program containing an open DCB issued an XCTL(X)
and encountered an address space whose queues it macro.
could not rebuild.
– A program freed virtual storage that contained an open
Source: Supervisor Control DCB.
System Action: The system ends the address space. – The program modified the DCB incorrectly.
System Programmer Response: If the source of the problem Source: Recovery termination manager (RTM)
cannot be determined, search problem reporting data bases for a fix
System Action: The system may issue message IEC999I.
for the problem. If no fix exists, contact the IBM support center.
Message IEC999I provides the address of the DEB that could not be
properly closed.
BFB
Operator Response: If the application or system programmer asks
Explanation: During JES3 abnormal termination recovery proc- for an SVC dump, set the following SLIP trap:
essing, JES3 was unable to invalidate the spool space allocation
SLIP SET,COMP=Cð3,ACTION=SVCD,END
checkpoint record (PTC). The invalidation failed due to an error in
the checkpoint access method or an unrecoverable I/O error in the Programmer Response: Do the following:
checkpoint data set(s). 1. If a dump is not produced with the abend, ask the operator to
Message IAT6352 accompanies this completion code. JES3 could set a SLIP trap to obtain an SVC dump.
not invalidate the spool space allocation checkpoint record (PTC) 2. From the dump, find the data extent block (DEB) from the
during JES3 abnormal termination recovery processing. IEC999I message. The DEB + X'18' points to the associated
When message IAT1025 accompanies this completion code, JES3 DCB or ACB.
could not invalidate the only copy or both copies of a partition track 3. If the DCB or ACB has been freed, then this is a user error.
allocation table (PTAT) during JES3 initialization or after JES3 failsoft
processing. This is a common user error during subtask processing. A user must
close a DCB or ACB before freeing the storage where the DCB or
Source: JES3 ACB resides. If the DCB or ACB has been overlaid, you must deter-
System Action: After issuing the message, JES3 ends. IAT6352 mine the cause of the overlay.
contains the checkpoint access method return code, which identifies System Programmer Response: If the module is an IBM program,
the error. search problem reporting data bases for a fix for the problem. If no
If message IAT1025 appears, the system writes an error record to fix exists, contact the IBM Support Center. Provide the dump.
the logrec data set.
Programmer Response: Using message IAT6352, analyze the C0D
return code and correct the error, then restart JES3. Explanation: An unexpected error occurred. For example, the
For message IAT1025, analyze the error record in the logrec data system returns a return code that is not valid. This abend may be
set and the accompanying messages. In case the error is caused by used for entry into a recovery routine that will attempt retry.
a bad track, assign another track to the checkpoint data set and For a paging request, the system provides a hexadecimal reason
restart JES3 with a warm start. Otherwise, reallocate the checkpoint code to describe the error.
data set and perform a cold start.
Code Explanation
System Programmer Response: If the problem occurs in JES3,
2A00010x and 2A00020x After a page fixing request
take a system dump by specifying DUMP=MVS on the OPTIONS
that specified a task control
card in the initialization deck Make sure that the failing job step
block (TCB) address of zero,
includes a SYSABEND statement.
the system received a corre-
sponding page freeing
request with a specific TCB
C03 address. The system could
Explanation: A task tried to end normally by issuing a RETURN not locate the necessary
macro or by branching to the return address in register 14. The task control blocks to process the
was not ready to end processing because the task had opened one request.
or more data sets that had not been closed. 5E000101 While processing a page
The system received a nonzero return code from Data Facility fixing request, the system
Product (DFP) indicating one of the following: encountered a fixed page
that was not backed with
DFP returned a nonzero return code.
preferred storage. To satisfy
DFP could not successfully close one or more data sets still the request, the page must
open because a previous error or abend had been ignored by a be backed.
recovery routine or a data control block (DCB) abend exit
For an indexed sequential access method (ISAM) request, the
routine.
system found an excess number of error input output blocks (IOB).
The probable cause of the problem is that an application neglected
to free the dynamic buffers associated with a READ macro.
System Completion Codes SCC-195
C13 C78
Source: One of the following:
C2D
Real storage manager (RSM)
Explanation: A program requested an overlay. In answer to the
Auxiliary storage manager (ASM)
request, the overlay supervisor was using program fetch to load a
Contents supervision (CSV)
program segment from the library. Fetch could not get enough
System Action: The system writes a logrec data set error record, a storage for the module or control blocks.
SYSOUT output for the job, and a dump. The system writes mes-
Note: Overlay programs run only in 24-bit addressing mode, not in
sages about the problem. The system issues an abend to the current
31-bit addressing mode.
task.
Source: Overlay supervisor
Programmer Response: For an ISAM request error, fix the
program and run the job again. For a problem in obtaining storage, System Action: The system abnormally ends the program that
fix the storage request and run the job again. requested the overlay. The system writes an ABEND dump, if a
dump DD statement is provided.
System Programmer Response: If an application or installation-
supplied program did not cause the problem, search problem Programmer Response: Determine why no storage was available.
reporting data bases for a fix for the problem. If no fix exists, contact Correct the errors; then assemble, link edit, and run the program
the IBM Support Center. Provide the messages, the logrec data set again.
record, the SYSOUT output for the job, and the dump.
C37
C13 Explanation: The error occurred when an input operation was
Explanation: The error occurred during processing of an OPEN requested. The data set was on a direct access device. This system
macro instruction for a concatenated partitioned data set or a graphic completion code is accompanied by message IEC033I. Refer to the
device. This system completion code is accompanied by message explanation of message IEC033I for complete information about the
IEC153I (or for graphics, message IEC157I). Refer to the explana- task that was ended and for an explanation of the return code (rc in
tion of message IEC153I (or message IEC157I) for complete infor- the message text) in register 15.
mation about the task that was ended and for an explanation of the Source: DFSMSdfp
return code (rc in the message text) in register 15.
Programmer Response: Respond as indicated for message
Source: DFSMSdfp IEC033I.
Programmer Response: Respond as indicated for message System Programmer Response: If the error recurs and the
IEC153I (or message IEC157I). program is not in error, look at the messages in the job log for more
System Programmer Response: If the error recurs and the information. Search problem reporting data bases for a fix for the
program is not in error, look at the messages in the job log for more problem. If no fix exists, contact the IBM Support Center. Provide all
information. Search problem reporting data bases for a fix for the printed output and output data sets related to the problem.
problem. If no fix exists, contact the IBM Support Center. Provide the
source program listing for the job. C78
Explanation: An error occurred when the system tried to process a
C1A virtual storage management (VSM) service. A reason code in the
Explanation: Through the MODIFY CATALOG,ABEND command, SDWACRC field of the system diagnostic work area (SDWA)
a request was issued to abnormally end either the catalog address explains the error:
space (CAS) allocation/unallocation, analysis, or modify task. Code Explanation
Source: DFSMSdfp 04 For the CPOOL BUILD or GET options, there is not
System Action: The system attaches a new task to restore the enough virtual storage available to build or extend a cell
allocation/unallocation, analysis, or modify function. pool.
08 For the CPOOL BUILD or GET options, there is not
C22 enough central storage available to build or extend a cell
Explanation: The execute channel program (EXCP) processor pool.
abnormally ended the job because the maximum number of 0C For the CPOOL BUILD or GET options, page tables are
EXCP/EXCPVR macro requests permitted for an address space was paged out for the storage obtained for the pool or pool
exceeded. The maximum number of outstanding requests is defined control blocks.
in the ASCBXCNT in the address space control block (ASCB).
10 For the CPOOL BUILD GET or DELETE options, an
Source: Execute channel program (EXCP) unauthorized user tried to build get or delete storage
System Action: The EXCP processor abnormally ends the job. from an authorized subpool.
Programmer Response: Check the job for a loop that could result 14 For the CPOOL BUILD option, an unauthorized caller
in EXCP/EXCPVR macros being issued repeatedly without inter- specified the task control block (TCB) parameter.
vening WAIT macros. If the reason for the error cannot be deter- 18 For the CPOOL GET or DELETE option, an incorrect
mined, notify the system programmer. cell pool identifier (CPID) is specified.
System Programmer Response: If the error recurs and an instal- 1C For the CPOOL BUILD DELETE or GET option, there is
lation provided program is not in error, look at the messages in the not enough storage available for a module's work area.
job log for more information. Search problem reporting data bases
20 For the CPOOL BUILD option, an incorrect cell count is
for a fix for the problem. If no fix exists, contact the IBM Support
specified.
Center. Provide the source program listing for the job.
SCC-196 OS/390 V2R8.0 MVS System Codes
C78 C78
24 For the CPOOL BUILD option, a reserved field in the 8C On VSMLIST, the subpool list address is zero.
parameter list is nonzero.
90 On VSMLIST, the work area size is less than 4 kilo-
28 For the CPOOL BUILD, GET, or DELETE options, the bytes.
invoker of the VSM service is in service request block
A0 On CPOOL, the primary cell count or cell size specified
(SRB) mode and problem state, which is not allowed by
is too large.
the system.
A4 On CPOOL, the secondary cell count or cell size speci-
2C For the CPOOL BUILD option, the invoker of the VSM
fied is too large.
service is in SRB mode requesting a local area subpool.
However, the invoker did not specify the TCB parameter. B0 During an address space create operation, RSM
returned a failing reason code. In the LOGREC record
30 A FREEMAIN routine returned a nonzero return code
associated with the abend, register 0 contains the RSM
unexpectedly when a task ended. Recovery attempts a
reason code.
retry.
Source: Virtual storage manager (VSM)
34 For the CPOOL BUILD or DELETE option, the subpool
identifier is incorrect. System Action: The system writes a logrec data set error record.
The system abnormally ends the current task.
38 For the CPOOL BUILD option, the LOC parameter is
incorrect. Programmer Response: Depending on the reason code, do one of
the following:
3C For the CPOOL BUILD option, the PSATOLD field points
to a TCB that is not in the currently addressable address Code Response
space. 04, 08, 0C, 1C Run the job again. If the
40 For the CPOOL BUILD option, the invoker of the VSM error recurs, notify the
service holds the VSMPAG lock. This is not valid system programmer.
because the system BUILD routine must obtain the CMS 18, 20, 30, 34, 38, 44 Ensure that the correct
lock, which is lower in the hierarchy than the VSMPAG values are specified.
lock.
10, 14, 28, 2C Ensure that the caller has
44 For the CPOOL BUILD option, the cell size is less than the authority to perform the
4 bytes. This is not valid. requested action.
48 On a request to free a central or virtual region, the 24, 74, 78, 7C, 80, and 8C Ensure that the parameter
subpool FREEMAIN failed. list is properly initialized.
4C The address space that is making a request to free a 40 Change the program so it
virtual region is nonswappable. releases the VSMPAG lock
50 On a request to get a real region, the system assigned before issuing the CPOOL
virtual=real (V=R) storage that VSM allocated in virtual macro with the BUILD
storage. parameter.
54 On a request to get a real region, the request for a VSM 3C Ensure that the program
cell failed. passes the proper TCB
address.
60 The system detected one of the following:
48, 4C, 50, 54 Notify the system pro-
The reserved bits of register 15 are not zero.
grammer.
The storage type indicator passed to VSMLOC is
60 Ensure that the input regis-
not valid. Valid storage types are the system queue
ters are properly initialized.
area (SQA) SQA, local system queue area (LSQA),
common service area (CSA), and private area. 84 Ensure that the information
in the work area does not
The size passed to VSMLOC is zero or negative.
change before the VSMLIST
The sum of the address passed to VSMLOC plus macro is invoked again.
the size passed is greater than 2 gigabytes.
88 Ensure that the TCB speci-
74 The reserved bits of the VSMLIST parameter list are not fied and all subtasks of the
zero. TCB are correct.
78 The return code field in the work area passed to the 90 Ensure that the work area
VSMLIST routine is not zero (first call) or four (restart). size is at least 4 kilobytes.
7C The SP operand of VSMLIST is not valid. A0, A4 Ensure that the cell count
and cell size values are
80 The SPACE operand of VSMLIST is not valid. Note:
specified correctly. If they
SPACE=UNALLOC is not allowed if SP=SQA,
are, decrease one value or
SP=LSQA, or SP=(subpool list) is specified.
both values.
84 VSMLIST was invoked again. Control information that
System Programmer Response: Search problem reporting data
was saved in the work area, provided by the caller, is
bases for a fix for the problem. If no fix exists, contact the IBM
not valid.
Support Center.
88 The TCB address is not valid or not in the currently
addressable address space.
System Completion Codes SCC-197
CC4 CC7
0851 Unable to establish ESTAE.
CC4
0852 Bad parameters passed to abending module.
Explanation: This abend code is issued as a part of normal proc-
essing by JES2 during task termination when resolving a deadlock 0853 OSI_SETUP failed.
condition involving an internal lock. This is not considered an error. 0854 Latch create failed.
Source: JES2 0855 Queue post failed.
System Action: Normal task termination continues. 0856 Trace failure.
System Programmer Response: None 0857 A user thread SRB was cancelled.
0893 Occurs due to attempting to decrement the counter for
CC5 special IPC events when the counter is already zero.
Explanation: CC5 is the abend completion code for abends issued System Action: The system issues a dump.
from sockets-over-SNA. See register 15 for the cause of the error.
The 2 low-order bytes of register 15 indicate, in hex, the cause of the Programmer Response: Do the following:
error. Save the console log from the primary console. For systems
Error Explanation with remote consoles, save the remote console log. In systems
with multiple-console support (MCS), save a copy of the hard
0826 Indicates an error in the routine that copy log.
increments/decrements the target task's updates-in-
progress counter. Abend when trying to decrement a Save the program listing associated with the job. See OS/390
zero counter. SecureWay Communications Server: SNA Diagnosis V1 Tech-
niques and Procedures for more information.
0827 Abend for a connection that was not accepted and the
connection control block is not valid.
CC7
0828 Indicates a previous failure in sockets-over-SNA and an
ALESERV ADD MVS macro instruction failure. Explanation: A work unit (a task or a system service running under
an SRB) issued an instruction requiring the presence of an Inte-
0829 Indicates a previous failure in sockets-over-SNA and an grated Cryptographic Feature (ICRF) on a processor that does not
ETCON MVS macro instruction failure. have the feature installed. The system was unable to move the work
0830 Indicates an ALESERV ADD macro instruction failure. to a processor with the feature. A hexadecimal reason code in reg-
ister 15 further describes the error condition.
0831 Indicates that ISU1 subsystem was not found.
Code Explanation
0832 Indicates that ISU1 subsystem was not initialized.
00 The work unit was disabled.
0833 Indicates an ALESERV DELETE MVS macro instruction
failure. 04 The ICRF is not available in the processor complex.
0834 A request to close a communication group was issued 08 No processors with the feature satisfy the work unit's
from an address space other than the one for which the restrictive processor affinity requirements.
group was defined. 10 An unexpected error occurred.
0836 Indicates a RESMGR ADD MVS macro instruction Source: Supervisor control
failure.
System Action: The system ends the work unit.
0837 Indicates a RESMGR DELETE MVS macro instruction
failure. Programmer Response: Respond according to the reason code:
0838 Indicates a ETCON MVS macro instruction failure. 00 Correct the program so that the instruction requiring the
ICRF is issued while running enabled.
0839 Indicates an ALESERV ADD MVS macro instruction
failure. 04 Resubmit the job to a processor complex that has the
ICRF installed. In a recovery routine, if this condition is
0840 Sockets-over-SNA attempted to decrement the target temporary, the routine could:
task's updates-in-progress counter when it registered
zero. Retry the instruction later
Issue a message to the end users to retry the
0841 The updates-in-progress counter overflowed. request later
0842 Indicates an attempt to decrement the counter when the Terminate the part of the program that requires the
counter registered zero. feature.
0843 Indicates an attempt to close the communication group 08 Remove the restrictive processor affinity which might
before all endpoints were closed. have been assigned to the work unit in one of the fol-
lowing ways:
0844 Indicates an attempt to close the communication group
that is not defined. In the program properties table (PPT) (using the
AFF keyword in SYS1.PARMLIB member
0845 A request was made to free a connection. That con-
SCHEDxx)
nection was not found.
In the SRB (in the SRBCPAFF field)
0847 A name or token has been created.
10 Collect diagnostic data and call your IBM service repre-
0850 Unable to obtain storage. sentative.
SCC-198 OS/390 V2R8.0 MVS System Codes
CFB CFB
System Action: The system issues message IEA705I. The system
CFB
abnormally ends the current task.
Explanation: One of the following occurred:
Programmer Response: Resubmit the job. If the system issues
During JES3 initialization, JES3 could not attach the JES3 auxil- this abend frequently, notify the system programmer.
iary task, module IATAUX. ATTACH processing writes message
System Programmer Response: See installation procedures to
IAT3005 to the console.
decrease the fixed central storage requirements of the system.
After JES3 initialization, the JES3 auxiliary task, module
IATAUX, could not recover from an error and abnormally ended. D05
The ESTAI routine in module IATABMN requests a dump of
module IATAUX to the SYSABEND or SYSUDUMP data set. Explanation: An error occurred when the system tried to process
an EU, LU, or VU form of the FREEMAIN macro. A reason code in
Source: JES3 the SDWACRC field of the system diagnostic work area (SDWA)
System Action: JES3 ends. explains the error:
Programmer Response: If JES3 wrote message IAT3005 to the Code Explanation
console, make sure that module IATAUX is in one of the following: 04 A FREEMAIN request was specified for local system
The library concatenation defined by the JES3LIB initialization queue area (LSQA) virtual storage that is associated
statements, if used. with a task. However, the virtual storage area specified
is not associated with the task.
The STEPLIB concatenation defined in the JES3 procedure.
08 The system could not satisfy a request for LSQA storage
The linklist specified in response to message IEA101A.
because there is not enough central storage for the
If JES3 did not write message IAT3005, look in the dump of module control blocks needed to support the request.
IATAUX to find the system completion code for the module's failure.
Source: Virtual storage manager (VSM)
Respond to that completion code.
System Action: The system issues message IEA705I. The system
System Programmer Response: If module IATAUX could not be
abnormally ends the current task.
attached, the system issues messages about the job. Make sure that
the failing job step includes a SYSABEND statement. Programmer Response: For reason code X'04', change the
FREEMAIN request to obtain storage owned by the task. Run the job
Collect all printed output and output data sets related to the problem.
step again.
If the problem occurs in JES3 you should:
For reason code X'08', resubmit the job. If the system issues this
Obtain system dump by specifying DUMP=JES on the
abend frequently, notify the system programmer.
OPTIONS card in the initialization deck and save the output
System Programmer Response: See installation procedures to
Provide a console log from initialization
decrease the fixed central storage requirements of the system.
Provide a listing of the JES3 start up procedure, containing all
JCL used to start the subsystem. D06
If module IATAUX abnormally ended, the system sends messages Explanation: A program issued the LOAD macro for a module. The
about the job to one of the following: macro included some form of the GLOBAL parameter. However,
The primary console within the same job step task structure, a task control block (TCB)
already loaded the requested module with different variables on the
The remote console, for a system with remote consoles
GLOBAL parameter. For example, a program issues the LOAD
The hard-copy log for a system with multiple console support macro for module MYPROG1 with the parameter GLOBAL=(YES,P).
(MCS) However, a TCB already loaded module MYPROG1 with the param-
Make sure that the failing job step includes a SYSABEND statement. eter GLOBAL=(YES,F) or GLOBAL=NO.
Collect all printed output and output data sets related to the problem. If a user tries to load the same module twice - once into a fixed
subpool and once into a pageable subpool, or once into global
storage and once into local storage, this situation arises.
D04 Source: Contents supervision (CSV)
Explanation: An error occurred when the system tried to process System Action: The system abnormally ends the program that
an EU, LU, or VU form of the GETMAIN macro. A reason code in issued the LOAD macro abnormally ends unless the macro included
the SDWACRC field of the system diagnostic work area (SDWA) the ERRET parameter. The system issues message CSV017I. The
explains the error: system issues an ABEND dump.
Code Explanation Programmer Response: Change the GLOBAL parameter on the
LOAD macro. Resubmit the job.
08 The system could not satisfy a request for local system
queue area (LSQA) storage because there is not enough System Programmer Response: If the error recurs and the
central storage for the control blocks needed to support program is not in error, see the system programmer response for the
the request. messages in the job log.
Source: Virtual storage manager (VSM) 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 and the source program listing for the job.
System Completion Codes SCC-199
D0A D22
D0A D13
Explanation: An error occurred when the system tried to process Explanation: The error occurred during processing of an OPEN
an R form of the GETMAIN or FREEMAIN macro. A reason code in macro instruction for a graphic data control block. This system com-
the SDWACRC field of the system diagnostic work area (SDWA) pletion code is usually accompanied by message IEC158I. Refer to
explains the error: the explanation of message IEC158I for complete information about
the task that was ended and for an explanation of the return code (rc
Code Explanation
in the message text) in register 15.
04 A FREEMAIN request was specified for local system
Source: DFSMSdfp
queue area (LSQA) virtual storage that is associated
with a task. However, the virtual storage area specified Programmer Response: Respond as indicated for message
is not associated with the task. IEC158I.
08 The system could not satisfy a request for LSQA storage System Programmer Response: If the error recurs and the
because there is not enough central storage for the program is not in error, look at the messages in the job log for more
control blocks needed to support the request. information. Search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center. Provide the
Source: Virtual storage manager (VSM)
source program listing for the job and all printed output and output
System Action: The system issues message IEA705I. The system data sets related to the problem.
abnormally ends the current task.
Programmer Response: For reason code X'04', change the D14
FREEMAIN request to obtain storage owned by the task. Run the job
Explanation: The error occurred during processing of a CLOSE
step again.
macro instruction for a graphic data control block.
For reason code X'08', resubmit the job. If the system issues this
The graphic device to be closed was not opened by the closing task.
abend frequently, notify the system programmer.
Source: DFSMSdfp
System Programmer Response: See installation procedures to
decrease the fixed central storage requirements of the system. Programmer Response: Issue the CLOSE macro instruction within
the same task that issues the OPEN macro instruction, or remove
the incorrect CLOSE macro instruction. Then run the job step again.
D0D
System Programmer Response: If the error recurs and the
Explanation: The system abnormally ended a subtask. While proc-
program is not in error, look at the messages in the job log for more
essing the subtask's end, the recovery termination manager 2
information. Search problem reporting data bases for a fix for the
(RTM2) was reentered incorrectly. Therefore, RTM abnormally
problem. If no fix exists, contact the IBM Support Center. Provide the
ended all tasks in the job step.
JCL and the program listing for the job.
Note: The original abend code is in the supervisor request block
(SVRB) for the original SVC 13 (ABEND macro). This SVRB
D1A
is queued from the task that experienced the original error.
Explanation: The catalog address space (CAS) analysis task
Source: Recovery termination manager (RTM)
ended abnormally because the analysis task exceeded the allotted
System Action: RTM2 attempts to end the job step. The system time for processing. The task may have been waiting for some
may write an SVC dump, or the program may write an ABEND system resource that is permanently unavailable.
dump. The system sends messages about the problem to the job
Source: DFSMSdfp
log.
System Action: The system attaches a new task to restore the
Operator Response: If the system programmer asks for an SVC
analysis function.
dump, set the following SLIP trap:
SLIP SET,COMP=DðD,ACTION=SVCD,END
D22
System Programmer Response: Do the following:
Explanation: A program issued the MGCR or MGCRE macro (SVC
1. If a dump is not produced with the abend, ask the operator to 34) or an operator issued a command. While processing the request,
set a SLIP trap to obtain an SVC dump. the system detected an error. A hexadecimal reason code in register
2. Examine the abend code for the original subtask. This abend 15 explains the error:
code can be found in the SVRB of the original SVC 13 SVRB Code Explanation
queued from the task that experienced the error.
04 The request specified both CMDFLAG=SUBSYS and
Continue diagnosis for that abend code. If the problem cannot CMDFLAG=COMMTASK. These parameter values are
be resolved, continue with step 3. mutually exclusive.
3. Look at the messages in the job log. 08 On the TEXT parameter, the request specified a length
4. Search problem reporting data bases for a fix for the problem. If field that is either greater than 126 characters or zero.
no fix exists, contact the IBM Support Center. Provide: 0C The request parameter list did not include the control
An ABEND or SVC dump block acronym MGCR or MGCRE.
Messages from the job log 10 The request required the CONSID or CONSNAME
The assembly listing associated with the job parameter, but neither was specified.
14 The request specified both the CONSNAME and
CONSID parameters. These are mutually exclusive.
SCC-200 OS/390 V2R8.0 MVS System Codes
D23 D23
18 The request specified a CONSNAME parameter value 04 The caller requested a WTOR with a text
that does not represent a valid console. length of zero.
1C The request specified a CONSID parameter value that is 05 The user modified the parameter list during
out the defined range for a multiple console support WTO processing, or a multi-line WTO
(MCS) console. parameter list contains a line with a text
length of zero.
20 The program is not authorized to issue the MGCR or
MGCRE macro. The program must be in supervisor 06 A caller not in key 0-7 or APF-authorized
state and PSW key 0-7. requested one or more of the authorized
WTO keywords.
24 Recovery could not be established while processing a
command, whether issued by the operator or issued 07 The caller requested mutually exclusive
using the MGCR or MGCRE macros. functions.
28 Parameters specified on the MGCR or MGCRE cannot 08 The caller supplied an incorrect parameter
be accessed because they are specified incorrectly. list structure.
Source: Master scheduler 0A The caller specified more than 14 lines of
text.
System Action: If reason code X'24' was issued, the system does
not process the command. For all other reason codes, the system 0B During system initialization, the caller issued
does not process the MGCR or MGCRE macro. a WTO.
System Programmer Response: If reason code X'24' was 0C The caller issued a WTOR to be processed
issued, ask the operator to issue the command again. If the problem synchronously with branch linkage.
persists, search problem reporting data bases for a fix for the
0D The caller issued a WTOR with more than
problem. If no fix exists, contact the IBM Support Center.
one line.
For all other reason codes, determine which module issued the
0E This processor does not hold the restart
MGCR or MGCRE macro:
resource.
If the module is installation-provided code, correct the MGCR or
0F The system could not access the action
MGCRE macro. Recompile and run the job step again.
code storage.
If the module is an IBM module, search problem reporting data
10 The system found an incorrect value in the
bases for a fix for the problem. If no fix exists, contact the com-
write-to-operator queue element.
ponent group for the module at the IBM Support Center.
11 The console name is reserved or incorrect.
D23 20 A GETCELL for an operator reply element (ORE) failed.
Explanation: An error occurred in processing for a write to operator 21 The system could not build a cellpool for an operator
(WTO) or write to operator with reply (WTOR). reply.
Register 15 contains a hexadecimal error code in the format 22 The system could not obtain storage for an operator
xxyy00zz or xxyy0www. The fields in this error code are the reply.
following: 30 A GETCELL for a write queue element (WQE) failed.
xx Identifies the processing that was taking place when the 31 The system could not build a subpool for a WTO
error occurred. message.
yy Identifies the module that requested the abend. 32 The system could not obtain storage for a WTO
zz If xx is 10, the error occurred during a validity check of a message.
parameter list, and the zz field identifies the error. 42 The system could not obtain storage for the dynamic
If xx is 20 or greater, the zz field contains the return work area.
code that was issued by system processing. 50 A LOADWAIT request failed.
www If xx is 99, the www field contains the abend code of the 51 The system could not obtain needed storage.
failure that caused the D23 abend
52 A failure occurred in the data block create routine.
The following are xx values and their associated zz values:
53 A failure occurred in the storage handler.
xx Meaning
99 An internal processing error occurred in the module
10 The error occurred during a validity check of a param- identified by yy. The www field contains the abend code
eter list. The zz value identifies the error: of the failure.
zz Meaning The following are yy values and their meanings:
01 The parameter list supplied to the WTOR yy Meaning
macro does not begin on a fullword
boundary. 01, 02 The WTO and WTOR service routine requested the
ABEND.
02 The caller issued a WTOR with more than
one line. 03-08 A system module requested the ABEND.
03 The parameter list that the caller passed Source: Communications task (COMMTASK)
does not reside in storage that the caller can
access.
System Completion Codes SCC-201
D2D D83
Programmer Response: Correct the program issuing the WTO or System Programmer Response: See installation procedures to
WTOR macro. Recompile the program. Run the job step again. If the decrease the fixed central storage requirements of the system.
problem persists, notify the system programmer.
System Programmer Response: Search problem reporting data D82
bases for a fix for the problem. If no fix exists, contact the IBM Explanation: While RACF was processing a RACROUTE
Support Center. REQUEST=AUTH, an error occurred in the RACF storage manager.
System Action: The system terminates the task.
D2D
Programmer Response: Register 15 contains a hexadecimal
Explanation: A program requested an overlay. In answer to the
reason code. (Message ICH409I, if issued, also contains this reason
request, the overlay supervisor was using program fetch to load a
code.)
program segment from the library. Fetch found an incorrect record
type in the segment to be loaded. Code Explanation
Note: Overlay programs run only in 24-bit addressing mode, not in 04 BAD LENGTH: The length of the area to get or free is
31-bit addressing mode. not greater than zero.
Source: Overlay supervisor 08 BAD ALIGNMENT: The pointer to the area to free is not
on a doubleword boundary.
System Action: The system abnormally ends the program that
requested the overlay. The system writes an ABEND dump, if a 0C DUPLICATE FREEMAIN: The area to free has already
dump DD statement is provided. been freed.
Programmer Response: Link edit and run the program again. 10 INCORRECT SUBPOOL: The subpool for the area to
free is not the subpool in which the area is allocated.
D37 14 INVALID OVERLAP: Part of the area to free equals part
of the area allocated, but the match is not correct for
Explanation: The error occurred when an output operation to a
either a full or partial FREEMAIN.
direct access device was requested. This system completion code is
accompanied by message IEC031I. 18 NOT FOUND: The area to free does not have a corre-
sponding GETMAIN entry in the tracking table, and the
Refer to the explanation of message IEC031I for complete informa-
caller did not specify that it should not have.
tion about the task that was ended and for an explanation of the
return code (rc in the message text) in register 15. 1C FOUND: The area to free has a corresponding
GETMAIN entry in the tracking table, and the caller
Source: DFSMSdfp
specified that it should not have.
Programmer Response: Respond as indicated for message
20 NOT FREED: There is a temporary area still allocated at
IEC031I.
the end of SVC processing.
System Programmer Response: If the error recurs and the
A0 A RACF module issued a get-space request. However,
program is not in error, look at the messages in the job log for more
register 1 is not equal to zero and does not point to a
information. Search problem reporting data bases for a fix for the
buffer previously created by the program.
problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the program listing for the job. A4 A RACF module issued a get-space request. However,
the subpool in register 0 is not the subpool in which the
D78 previously created buffer is allocated.
Explanation: An error occurred when the system tried to process A8 A RACF module issued a free-space request. However,
an RU or VRU form of the GETMAIN or an RU form of the register 1 is equal to zero.
FREEMAIN macro. A reason code in the SDWACRC field of the AC A RACF module issued a free-space request. However,
system diagnostic work area (SDWA) explains the error: register 1 does not point to the buffer previously created
Code Explanation by the program.
04 A FREEMAIN request was specified for local system Identify and correct the indicated error.
queue area (LSQA) virtual storage that is associated System Programmer Response: Using IPCS, format the dump
with a task. However, the virtual storage area specified taken for this abend. For an explanation of the dump title, see
is not associated with the task. OS/390 Security Server (RACF) Diagnosis Guide.
08 The system could not satisfy a request for LSQA storage
because there is not enough central storage for the D83
control blocks needed to support the request. Explanation: While RACF was processing a RACROUTE
Source: Virtual storage manager (VSM) REQUEST=VERIFY, an error occurred in the RACF storage
manager.
System Action: The system issues message IEA705I. The system
abnormally ends the current task. System Action: The system terminates the task.
Programmer Response: For reason code X'04', change the Programmer Response: Register 15 contains a hexadecimal
FREEMAIN request to obtain storage owned by the task. Run the job reason code. (Message ICH409I, if issued, also contains this reason
step again. code.)
For reason code X'08', resubmit the job. If the system issues this Code Explanation
abend frequently, notify the system programmer. 04 BAD LENGTH: The length of the area to get or free is
not greater than zero.
SCC-202 OS/390 V2R8.0 MVS System Codes
D84 D85
08 BAD ALIGNMENT: The pointer to the area to free is not 20 NOT FREED: There is a temporary area still allocated at
on a doubleword boundary. the end of SVC processing.
0C DUPLICATE FREEMAIN: The area to free has already 44 Too many actions specified on ICHEINTY macro.
been freed.
A0 A RACF module issued a get-space request. However,
10 INCORRECT SUBPOOL: The subpool for the area to register 1 is not equal to zero and does not point to a
free is not the subpool in which the area is allocated. buffer previously created by the program.
14 INVALID OVERLAP: Part of the area to free equals part A4 A RACF module issued a get-space request. However,
of the area allocated, but the match is not correct for the subpool in register 0 is not the subpool in which the
either a full or partial FREEMAIN. previously created buffer is allocated.
18 NOT FOUND: The area to free does not have a corre- A8 A RACF module issued a free-space request. However,
sponding GETMAIN entry in the tracking table, and the register 1 is equal to zero.
caller did not specify that it should not have.
AC A RACF module issued a free-space request. However,
1C FOUND: The area to free has a corresponding register 1 does not point to the buffer previously created
GETMAIN entry in the tracking table, and the caller by the program.
specified that it should not have.
Identify and correct the indicated error.
20 NOT FREED: There is a temporary area still allocated at
System Programmer Response: Using IPCS, format the dump
the end of SVC processing.
taken for this abend. For an explanation of the dump title, see the
A0 A RACF module issued a get-space request. However, OS/390 Security Server (RACF) Diagnosis Guide.
register 1 is not equal to zero and does not point to a
buffer previously created by the program. D85
A4 A RACF module issued a get-space request. However, Explanation: While RACF was processing a RACROUTE
the subpool in register 0 is not the subpool in which the REQUEST=DEFINE, an error occurred in the RACF storage
previously created buffer is allocated. manager.
A8 A RACF module issued a free-space request. However, System Action: The system terminates the task.
register 1 is equal to zero.
Programmer Response: Register 15 contains a hexadecimal
AC A RACF module issued a free-space request. However, reason code. (Message ICH409I, if issued, also contains this reason
register 1 does not point to the buffer previously created code.)
by the program.
Code Explanation
Identify and correct the indicated error.
04 BAD LENGTH: The length of the area to get or free is
System Programmer Response: Using IPCS, format the dump not greater than zero.
taken for this abend. For an explanation of the dump title, see
OS/390 Security Server (RACF) Diagnosis Guide. 08 BAD ALIGNMENT: The pointer to the area to free is not
on a doubleword boundary.
D84 0C DUPLICATE FREEMAIN: The area to free has already
been freed.
Explanation: While RACF was processing a RACROUTE
REQUEST=LIST, an error occurred in the RACF storage manager. 10 INCORRECT SUBPOOL: The subpool for the area to
free is not the subpool in which the area is allocated.
System Action: The system terminates the task.
14 INVALID OVERLAP: Part of the area to free equals part
Programmer Response: Register 15 contains a hexadecimal
of the area allocated, but the match is not correct for
reason code. (Message ICH409I, if issued, also contains this reason
either a full or partial FREEMAIN.
code.)
18 NOT FOUND: The area to free does not have a corre-
Code Explanation
sponding GETMAIN entry in the tracking table, and the
04 BAD LENGTH: The length of the area to get or free is caller did not specify that it should not have.
not greater than zero.
1C FOUND: The area to free has a corresponding
08 BAD ALIGNMENT: The pointer to the area to free is not GETMAIN entry in the tracking table, and the caller
on a doubleword boundary. specified that it should not have.
0C DUPLICATE FREEMAIN: The area to free has already 20 NOT FREED: There is a temporary area still allocated at
been freed. the end of SVC processing.
10 INCORRECT SUBPOOL: The subpool for the area to A0 A RACF module issued a get-space request. However,
free is not the subpool in which the area is allocated. register 1 is not equal to zero and does not point to a
buffer previously created by the program.
14 INVALID OVERLAP: Part of the area to free equals part
of the area allocated, but the match is not correct for A4 A RACF module issued a get-space request. However,
either a full or partial FREEMAIN. the subpool in register 0 is not the subpool in which the
previously created buffer is allocated.
18 NOT FOUND: The area to free does not have a corre-
sponding GETMAIN entry in the tracking table, and the A8 A RACF module issued a free-space request. However,
caller did not specify that it should not have. register 1 is equal to zero.
1C FOUND: The area to free has a corresponding
GETMAIN entry in the tracking table, and the caller
specified that it should not have.
System Completion Codes SCC-203
DC5 DC7
AC A RACF module issued a free-space request. However, 1B An internal error occurred.
register 1 does not point to the buffer previously created
1C The IXZXIXAT macro failed because the member was
by the program.
already active in that group.
Identify and correct the indicated error.
1D The member name specified on the IXZXIXDT macro
System Programmer Response: Using IPCS, format the dump could not be found.
taken for this abend. For an explanation of the dump title, see the
1E An internal error occurred.
OS/390 Security Server (RACF) Diagnosis Guide.
1F The data space could not be created for the IXZXIXAT
macro request.
DC5
20 JESXCF could not add the JES member to the specified
Explanation: JES common coupling services (JESXCF) detected
XCF group.
an unrecoverable error during its processing. A hexadecimal reason
code returned in register 0 describes the error: 21 The XCF group maximum has been reached.
Code Explanation 22 The XCF member maximum has been reached.
01 The parameter list passed to the IXZXIXAT or IXZXIXDT 23 JESXCF could not add the JES member to the specified
macro service does not have a valid eyecatcher. XCF group.
02 The parameter list passed to the IXZXIXAT or IXZXIXDT 24 An internal error occurred.
macro service has an incorrect level. 25 The IXZXIXDT macro failed, because it was issued from
03 The XCF member name passed on the IXZXIXAT macro a different ASCB and TCB than the issuer of the
either contains a character that is not valid or is all IXZXIXAT macro that created the specified member.
blanks. 26 An internal error occurred.
04 The XCF member name passed on the IXZXIXAT macro 27 An internal error occurred.
contains imbedded blanks.
32 An internal error occurred, probably because the
05 JESXCF validation of the member name on the JESXCF address space was forced and restarted.
IXZXIXAT macro failed.
33 An internal error occurred.
06 The XCF group name passed on the IXZXIXAT macro
either contains a character that is not valid or is all 34 An internal error occurred.
blanks. 35 An internal error occurred.
07 The XCF group name passed on the IXZXIXAT macro 36 An internal error occurred.
contains imbedded blanks.
Source: JES common coupling services (JESXCF)
08 Validation of the group name on the IXZXIXAT macro
System Action: JESXCF produces a dump for the error (unless the
failed.
dump is suppressed by DAE), and return code X'C' is returned to
09 Validation of the IXZXIXAT/IXZXIXDT parameter list the caller of the service.
failed.
Operator Response: Notify your system programmer.
0A An internal error occurred.
System Programmer Response: If this abend was issued due to
0B An internal error occurred. an error in an installation invocation of the IXZXIXAT or IXZXIXDT
0C An internal error occurred. macro, correct the error based on the reason code provided. Refer to
OS/390 MVS Programming: JES Common Coupling Services for
0D An internal error occurred. information about using and coding IXZXIXAT and IXZXIXDT.
0E An internal error occurred. Interpret the return and reason code provided and determine if the
0F The group token passed on the IXZXIXDT macro con- problem is due to a configuration error or coding error. If the problem
tains an eyecatcher that is not valid. is due to a configuration error, then correct the problem and restart
JES. If the problem is due to a coding error, search the problem
10 The group token passed on the IXZXIXDT macro con-
reporting data bases for a fix to the problem. If none exist, contact
tains a version number that is not valid.
the IBM support center with the return and reason codes and the
12 The JES indicator flag bit (WHICHJES) in the parameter dump produced by the error.
list had both or none of the JES flags set.
For additional information on dumping the JES and JESXCF address
13 The release in the IXZYIXAT mapping macro is not sup- spaces, as well as restarting the JESXCF address space, see
ported. OS/390 MVS Programming: JES Common Coupling Services.
14 The release validation of the IXZYIXAT mapping macro
returned an unknown reason code. DC7
15 The maintenance level of the IXZYIXAT mapping macro Explanation: While running the APPC/MVS transaction scheduler,
parameter list is not current. the system found an unrecoverable error.
16 An internal error occurred. A reason code further describes the error:
17 An internal error occurred. Code Explanation
18 An internal error occurred. 01 A CLASSADD statement in parmlib tried to modify the
characteristics of a class that already existed.
19 An internal error occurred.
1A An internal error occurred.
SCC-204 OS/390 V2R8.0 MVS System Codes
DC7 DC7
03 The system found an incorrect transaction scheduling 04-07 Unpredictable.
type for a transaction program (TP).
08 The initiator address space where the TP was scheduled
04 The system could not run the Resource Access Control to run ends. The requestor of the TP receives a return
Facility (RACF). code indicating that the conversation was deallocated.
05 The system could not create a security environment. 10 If the TP provided recovery, recovery receives control.
Otherwise, the TP ends.
07 The system could not delete the security environment.
11-20 Unpredictable.
08 The system could not obtain SYSOUT and accounting
information from RACF. 21-23 The APPC/MVS transaction scheduler ends. No restart
is possible.
10 The GETTRANS service could not notify system man-
agement of a new TP. 24-25 The system continues processing with the existing initi-
ator.
11-20 An internal error occurred.
26-27 The system continues processing. If this error occurs
21, 22, 23 The system could not initialize the APPC/MVS trans-
again in a certain time period, the system attempts an
action scheduler.
automatic restart. If restart is unsuccessful, the
24, 25 The system could not create a new ASCH initiator. APPC/MVS transaction scheduler ends.
28-32 An internal error occurred. 28-32 Unpredictable.
33 The system could not obtain a transaction from APPC. 33 The system continues processing. If this error occurs
34 The system could not initialize the APPC/MVS trans- again in a certain time period, the system attempts an
action scheduler. automatic restart. If restart is unsuccessful, the
APPC/MVS transaction scheduler ends.
35 An attempt was made to start the ASCH address space
by something other than a START command. 34 The APPC/MVS transaction scheduler ends. No restart
is possible.
36 The system could not initialize the ASCH.
35 The system does not initialize the ASCH address space.
37 An internal error occurred.
36-37 The APPC/MVS transaction scheduler ends. No restart
38-41 The system could not create a new ASCH initiator.
is possible.
42, 43 While APPC was active, the system could not initialize
38-41 The system continues processing with the existing initi-
ASCH.
ator.
44 The system could not verify the subsystem specified on
42-43 The system automatically attempts a restart. If this error
the SUBSYS keyword in the current parmlib configura-
occurs again, the APPC/MVS transaction scheduler
tion.
ends.
45 While the system was processing a DISPLAY ASCH
44 The system continues processing with the existing initi-
command, an error occurred.
ator.
46 When the system tried to invoke the APPC associate
45 The system rejects the DISPLAY ASCH command.
service, an error occurred.
46 The system continues processing. The requestor of the
47 The system could not verify the subsystem specified on
transaction receives a return code indicating that the
the SUBSYS keyword in the current parmlib configura-
conversation was deallocated.
tion.
47 The system continues processing with the existing initi-
48, 49, 50 After being notified that APPC was active, the system
ator.
could not initialize the APPC/MVS transaction scheduler.
48-50 The system automatically attempts a restart. If this error
51 The ASCH failed while it was ending.
occurs again, the APPC/MVS transaction scheduler
52, 53, 54 The system could not initialize the APPC/MVS trans- ends.
action scheduler.
51-55 The APPC/MVS transaction scheduler ends. No restart
56 After being notified that APPC was active, the system is possible.
could not initialize the APPC/MVS transaction scheduler.
56 The system automatically attempts a restart. If this error
57 The system could not initialize the APPC/MVS trans- occurs again, the APPC/MVS transaction scheduler
action scheduler. ends.
59-65 An internal error occurred. 57 The APPC/MVS transaction scheduler ends. No restart
is possible.
Source: APPC/MVS transaction scheduler
58-60 Unpredictable.
System Action: Depending on the reason code, one of following:
61, 62 The system continues processing.
Code System Action
63, 64 The system automatically attempts a restart. If this error
01 The system does not process the incorrect CLASSADD
occurs again, the APPC/MVS transaction scheduler
statement. Other processing continues.
ends.
03 The APPC scheduler does not schedule the TP. The ini-
Operator Response: Depending on the reason code, do one of the
tiator address space where the TP should have run
following:
ends. The requestor of the TP receives a return code
indicating that the conversation was deallocated.
System Completion Codes SCC-205
DFB DFB
Code Explanation 56 If the APPC/MVS transaction scheduler ends, enter a
START ASCH command. If the error occurs again, notify
01, 03, 04 Enter a DISPLAY ASCH command to find the incorrect
the system programmer.
CLASSADD statement. Notify the system programmer.
57-61 Notify the system programmer.
08 Contact the RACF administrator to check the installa-
tion's security package for information identifying the 62 If the APPC/MVS transaction scheduler is not processing
error. critical work, enter a CANCEL ASCH command to end
the APPC/MVS transaction scheduler. Then enter the
10-22 Notify the system programmer.
START ASCH command to restart the APPC/MVS trans-
23 Enter a START ASCH command. If the error occurs action scheduler. Otherwise, notify the system pro-
again, notify the system programmer. grammer.
24 Notify the system programmer. 63, 64 If the error occurs again, notify the system programmer.
25 If the APPC/MVS transaction scheduler is not processing System Programmer Response: Depending on the reason code,
critical work, enter a CANCEL ASCH command to end do one of the following:
the APPC/MVS transaction scheduler. Then enter the
Code Explanation
START ASCH command to restart the APPC/MVS trans-
action scheduler. Otherwise, notify the system pro- 01 Delete the incorrect class using a CLASSDEL statement
grammer. in the current parmlib configuration. Then try to add the
class again, using a CLASSADD statement. If the error
26 Notify the system programmer.
occurs again, contact the IBM Support Center.
27 If the APPC/MVS transaction scheduler ends, notify the
03, 04 Search problem reporting data bases for a fix for the
system programmer. Enter a START ASCH command.
problem. If no fix exists, contact the IBM Support Center.
28-32 Notify the system programmer.
05 Check to see whether a program issued the UNIX
33 The system continues processing. The requestor of the System Services spawn callable service, passing a user
transaction receives a return code indicating the conver- ID that is not valid. If the user ID is valid, search
sation was deallocated. problem reporting data bases for a fix for the problem. If
34 Enter a START ASCH command. If the error occurs no fix exists, contact the IBM Support Center.
again, notify the system programmer. 07 Search problem reporting data bases for a fix for the
35 Notify the system programmer. problem. If no fix exists, contact the IBM Support Center.
36 If the APPC/MVS transaction scheduler ends, notify the 08 Contact the RACF administrator. Check the installation's
system programmer. Enter a START ASCH command. security package for information identifying the error.
37 Enter a START ASCH command. If the error occurs 10-34 Search problem reporting data bases for a fix for the
again, notify the system programmer. problem. If no fix exists, contact the IBM Support Center.
38, 39, 40 Notify the system programmer. 35 Determine how APPC/MVS transaction scheduler initial-
ization was invoked and take appropriate actions to
41 If the APPC/MVS transaction scheduler is not processing
prevent re-occurrences. The only proper way to initialize
critical work, enter a CANCEL ASCH command to end
the scheduler is with the START command.
the APPC/MVS transaction scheduler. Then enter the
START ASCH command to restart the APPC/MVS trans- 36-43 Search problem reporting data bases for a fix for the
action scheduler. Otherwise, notify the system pro- problem. If no fix exists, contact the IBM Support Center.
grammer. 44 Enter a valid JES subsystem on the SUBSYS keyword
42 Notify the system programmer. in the current parmlib configuration.
43 If the APPC/MVS transaction scheduler ends, notify the 45-65 Search problem reporting data bases for a fix for the
system programmer. Enter a START ASCH command. problem. If no fix exists, contact the IBM Support Center.
44 If the error occurs again, notify the system programmer.
DFB
45 Enter the DISPLAY ASCH command again. If the error
occurs again, notify the system programmer. Explanation: During processing in a functional subsystem (FSS)
address space, a JES3 module detected an error. A hexadecimal
46 Notify the system programmer. reason code in register 15 and/or the SDWA explains the error.
47 If the APPC/MVS transaction scheduler is not processing (Note: when the reason code is X'26', it will appear only in the
critical work, enter a CANCEL ASCH command to end SDWA, not in register 15.)
the APPC/MVS transaction scheduler. Then enter the Code Explanation
START ASCH command to restart the APPC/MVS trans-
action scheduler. Otherwise, notify the system pro- 01 The connect subsystem interface (SSI) routine in module
grammer. IATSICD determined that the START command for the
FSS address space did not contain a token.
48, 49 Notify the system programmer.
02 The connect subsystem interface (SSI) routine in module
50 If the APPC/MVS transaction scheduler ends, notify the IATSICD could not locate the MEMDATA header for the
system programmer. Enter a START ASCH command. FSS address space.
51-54 Notify the system programmer. 03 The connect subsystem interface (SSI) routine in module
55 If the APPC/MVS transaction scheduler ends, notify the IATSICD could not establish the listen task, IATFCLT,
system programmer. Enter a START ASCH command. for the FSS or the FSA.
SCC-206 OS/390 V2R8.0 MVS System Codes
05 Module IATSICD encountered an error during JESXCF 35 The writer FSA quick-cell service routine, IATFPQC,
attach processing (IXZXIXAT service). failed to free an index, because the index passed in the
request was incorrect.
06 Module IATSICD encountered an error during JESXCF
mailbox build processing (IXZXIXMB service) for the 36 The writer FSA quick-cell service routine, IATFPQC,
default mailbox. failed to free a buffer, because the buffer passed in the
request was incorrect.
07 Module IATSICD encountered an error during JESXCF
mailbox delete processing (IXZXIXMD service) for the 3D While reading a data set checkpoint record, the writer
default mailbox. FSA GETDS routine, IATFPGD, received an error return
from the block spooler routine; the error return indicated
08 Module IATSICD encountered an error during JESXCF
that the parameter list was incorrect.
detach processing (IXZXIXDT service).
3E While reading a data set checkpoint record, the writer
0B The common end-of-task exit routine in module IATSICD
FSA GETDS routine, IATFPGD, received an error return
found that a task in the FSS address space had ended
from the block spooler routine; the error return indicated
unexpectedly.
that the spool address was incorrect.
0C The common end-of-task exit routine in module IATSICD
3F While reading a data set checkpoint record, the writer
could not identify a task that had ended.
FSA GETDS routine, IATFPGD, received an error return
15 The writer FSA specific connect routine, IATFPCC, could from the block spooler routine; the error return indicated
not initialize for GETDS spool access using the block that an error occurred during a cross-address space
spooler. move.
16 The writer FSA specific connect routine, IATFPCC, could 47 While reading the scheduler work block (SWB), the
not establish the read-ahead task for the FSA. writer FSA SWB processing service routine, IATFPSB,
17 The writer FSA specific connect routine, IATFPCC, could received an error return from the block spooler routine;
not establish the checkpoint writer task for the FSA. the error return indicated that the parameter list was
incorrect.
1F The FSI order interface routine, IATFCOR, received a
nonzero return code from the FSS or FSA order routine. 48 While reading the scheduler work block (SWB), the
writer FSA SWB processing service routine, IATFPSB,
20 The FSI post interface routine, IATFCPT, received a
received an error return from the block spooler routine;
nonzero return code from the FSA post routine.
the error return indicated that the spool address was
21 Module IATFCLT encountered an error during JESXCF incorrect.
mailbox build processing (IXZXIXMB Service) for a
49 While reading the scheduler work block (SWB), the
FSS/FSA mailbox.
writer FSA SWB processing service routine, IATFPSB,
22 Module IATFCLT encountered an error during JESXCF received an error return from the block spooler routine;
mailbox clear processing (IXZXIXMC Service) for a the error return indicated that an error occurred during a
FSS/FSA mailbox. cross-address space move.
23 Module IATFCLT encountered an error during JESXCF 4A The scheduler JCL facility (SJF) PUTSWB function
receive message processing (IXZXIXRM Service) for a returned an error code to the writer FSA scheduler work
FSS/FSA mailbox. block (SWB) processing service routine, IATFPSB.
24 Module IATFCLT encountered an error during JESXCF 4B The scheduler JCL facility (SJF) UPDATE function
acknowledge message processing (IXZXIXAC Service) returned an error code to the writer FSA scheduler work
for a FSS/FSA mailbox. block (SWB) processing service routine, IATFPSB.
25 Module IATFCLT encountered an error during JESXCF 4C The scheduler JCL facility (SJF) DELETESWB function
mailbox delete processing (IXZXIXMD) for a FSS/FSA returned an error code to the writer FSA scheduler work
mailbox. block (SWB) processing service routine, IATFPSB.
26 A stop FSA abnormal order has been received from 51 The writer FSA read-ahead task, IATFPRA, could not ini-
JES3. If a dump has been requested, a dump will be tialize for spool access using the block spooler.
taken as part of abend processing of the FSA task.
52 While reading data from spool, the writer FSA read-
29 The C/I FSS order processing routine, IATIIFO, found ahead task, IATFPRA, received an error return from the
that the FSI parameter list did not contain an order. block spooler routine; the error return indicated that the
parameter list was incorrect.
2A The C/I FSS order processing routine, IATIIFO, received
an incorrect order type. 53 While reading data from spool, the writer FSA read-
ahead task, IATFPRA, received an error return from the
2B The C/I FSS order processing routine, IATIIFO, received
block spooler routine; the error return indicated that the
an incorrect stop FSS order.
spool address was incorrect.
2C The C/I FSS order processing routine, IATIIFO, could
54 While reading data from spool, the writer FSA read-
not locate the C/I communications block (CCB).
ahead task, IATFPRA, received an error return from the
33 The writer FSA quick-cell service routine, IATFPQC, block spooler routine; the error return indicated that an
failed to get an index, because the first free index was error occurred during a cross-address space move.
incorrect.
55 The writer FSA read-ahead task, IATFPRA, found an
34 The writer FSA quick-cell service routine, IATFPQC, error in the format of a spool data buffer.
failed to get a buffer, because the first free buffer was
incorrect.
System Completion Codes SCC-207
E00 E06
56 The writer FSA read-ahead task, IATFPRA, found an
E03
error in the format of a JESNEWS data buffer.
Explanation: A task tried to end normally by issuing a RETURN
5B The writer FSA checkpoint writer task, IATFPCW, could
macro or by branching to the return address in register 14. The task
not initialize for spool access using the block spooler.
was not ready to end processing because the task issued one of the
5C While writing a data set checkpoint record, the writer following macros with a SET,MC (must complete) parameter:
FSA checkpoint writer task, IATFPCW, received an error
STATUS
return from the block spooler routine; the error return
RESERVE
indicated that the parameter list was incorrect.
ENQ
5D While writing a data set checkpoint record, the writer
The task did not issue an accompanying STATUS RESET,MC or
FSA checkpoint writer task, IATFPCW, received an error
DEQ RESET,MC macro to reset the step-must-complete status
return from the block spooler routine; the error return
before attempting to end.
indicated that the spool address was incorrect.
Source: Recovery termination manager (RTM)
5E While writing a data set checkpoint record, the writer
FSA checkpoint writer task, IATFPCW, received an error System Action: The system abnormally ends the task.
return from the block spooler routine; the error return Operator Response: If the application or system programmer asks
indicated that an error occurred during a cross-address for an SVC dump, set the following SLIP trap:
space move.
SLIP SET,COMP=Eð3,ACTION=SVCD,END
Source: JES3
Programmer Response: Do the following:
System Action: The system abnormally ends the task.
1. If a dump is not produced with the abend, ask the operator to
Most failures in the read-ahead task, IATFPRA, and in the check- set a SLIP trap to obtain an SVC dump.
point writer task, IATFPCW, cause processing of the current data set
to be ended. The task is reinstated to resume processing with the 2. From the dump, identify the abnormally ended module.
next data set. 3. If the module is an installation-provided program, ensure that
All other failures result in the FSA or of the entire FSS address each ENQ, RESERVE, or STATUS macro with the SET,MC
space ending. parameter is paired with a DEQ or STATUS macro with the
RESET,MC parameter.
Operator Response: Notify the system programmer. If the FSS
address space was ended and if this is not a recurring error, issue System Programmer Response: If the module is an IBM module,
the appropriate command to restart the FSS. search problem reporting data bases for a fix for the problem. If no
fix exists, contact the component group for the module at the IBM
System Programmer Response: Format the SVC dump with the Support Center. Provide problem data collected.
interactive problem control system (IPCS).
If the problem occurs in JES3, save the hardcopy log. E06
Explanation: An error occurred during contents supervisor proc-
essing of an OS/390 UNIX System Services (OS/390 UNIX) exec,
E00 fork, loadhfs, or deletehfs function.
Explanation: During processing of an I/O request, execute channel A hexadecimal reason code in register 15 describes the error. The
program (EXCP) processing encountered one of the following errors: reason codes are in the form xx yy, where xx represents the 1-byte
A program check or machine check occurred while the function ID of the function that caused the error, and yy represents
input/output supervisor (IOS) interruption response block (IRB) the reason code for the error. The possible values for the function
analysis modules were processing or IOS POST was proc- code xx are:
essing. Code Explanation
The operator pressed the RESTART key while the I/O request 00 An exec or fork function failed.
was being processed.
01 A loadhfs function failed.
A program check or machine check occurred while a nonresi-
dent error recovery program (ERP) was processing or the ERP 02 A deletehfs function failed.
loader module was processing. The reason code value yy can have one of the following values:
Source: Execute channel program (EXCP) Code Explanation
System Action: The system abnormally ends the current task. The 00 An unauthorized program requested contents supervisor
system writes a logrec data set error record. The previous error processing for the OS/390 UNIX exec, loadhfs, or
record in the logrec data should indicate the cause of the abend. The deletehfs function.
system does not provide the EXCP debugging area (XDBA).
04-1C An internal error occurred while processing the exec,
System Programmer Response: Look at the messages in the loadhfs, or deletehfs OS/390 UNIX callable service.
logrec data set error record for the probable cause of the error. If the
20 A PGMF FIND was not successful. Message CSV034I
reason for the error cannot be determined or if an IBM-provided
accompanies this abend.
program is causing the error, look at the messages in the job log for
more information. Search problem reporting data bases for a fix for 24 A PGMF FIND for the requested module program
the problem. If no fix exists, contact the IBM Support Center. Provide checked or ended abnormally. Message CSV036I
the logrec data set error record, the JCL, the program listing, and the accompanies this abend.
assembly listing for the job. 2C An unexpected error occurred during contents supervisor
processing for an OS/390 UNIX callable service.
SCC-208 OS/390 V2R8.0 MVS System Codes
E13 E2D
30 The requested pathname resulted in a fetch of a For reason codes 04 through 18 and 50 through 54, an internal error
loadable-only file. Message CSV039I accompanies this occurred. Report the error to the IBM Support Center.
abend. The requested pathname references a loadable-
only file, which is not valid as the target of an exec call- E13
able service.
Explanation: The error occurred during processing of an OPEN
34 The requested pathname resulted in a fetch of a nonex- macro instruction for a graphic data control block. This system com-
ecutable file. Message CSV038I accompanies this pletion code is accompanied by message IEC159I. Refer to the
abend. explanation of message IEC159I for complete information about the
38 The requested pathname resulted in a fetch of a nonex- task that was ended and for an explanation of the return code (rc in
ecutable file. The module was marked as being an the message text) in register 15.
overlay module. This should not occur for an exec exe- Source: DFSMSdfp
cutable file. Message CSV038I accompanies this abend.
Programmer Response: Respond as indicated for message
3C The requested pathname resulted in a fetch of a nonex- IEC159I.
ecutable file. Message CSV038I accompanies this
abend. System Programmer Response: If the error recurs and the
program is not in error, look at the messages in the job log for more
40 An internal error occurred while attempting to fetch the information. Search problem reporting data bases for a fix for the
executable file. problem. If no fix exists, contact the IBM Support Center. Provide the
44 A PGMF FIND for the requested module program source program listing for the job and all printed output and output
checked or ended abnormally. Message CSV036I data sets related to the problem.
accompanies this abend.
48 The callable service was unable to establish ESTAE E1A
recovery. Explanation: The catalog address space (CAS) allocate task ended
4C The caller had more than one RB on its TCB chain. abnormally because the allocate task exceeded the allotted time for
processing. The task may have been waiting for some system
50-54 These reason codes indicate an internal error occurred resource that is permanently unavailable.
during fork callable service processing.
Source: DFSMSdfp
58 An internal error occurred while attempting to remove a
program from storage. System Action: The system attaches a new task to restore the
allocate function.
Source: Contents Supervision
System Action: The system abnormally ends the program issuing E23
the callable service.
Explanation: An error occurred during processing of a write to
Programmer Response: operator with reply (WTOR) macro. The macro specified one of the
Code Response following incorrectly:
00 No system dump is taken and no LOGREC record is The address of the event control block (ECB)
written. The address of the request block (RB) in the ECB
The address of the virtual storage area
04-1C Contact the system programmer.
Source: Communications task (COMMTASK)
20 Refer to accompanying message CSV034I.
Programmer Response: Correct the macro or program errors that
24 Contact the system programmer.
incorrectly modified the macro expansion. Ensure that the ECB
30 Correct the program. address is a fullword on a fullword boundary. Recompile the
34 Correct the pathname to refer to an executable file. program and run the job step again.
38 Correct the pathname to refer to an executable file.
E2D
3C Correct the pathname to refer to an executable file.
Explanation: A program requested an overlay. In answer to the
40 Refer to accompanying message CSV034I. request, the overlay supervisor was using program fetch to load a
44 Contact the system programmer. program segment from the library. Fetch found an incorrect address.
50-54 Contact the system programmer. Note: Overlay programs run only in 24-bit addressing mode, not in
31-bit addressing mode.
System Programmer Response: Some of the reason codes may
indicate that there is a problem with the file system or the underlying Source: Overlay supervisor
PGMF mechanism. For reason codes other than 00, a system dump System Action: The system abnormally ends the program that
is normally taken. Provide the dump to the IBM Support Center. requested the overlay. The system writes an ABEND dump, if a
dump DD statement is provided.
Programmer Response: Link edit and run the program again.
System Completion Codes SCC-209
E37 EC5
E37 E85
Explanation: The error occurred when an output operation was Explanation: SVC 133 (RACROUTE REQUEST=DEFINE macro)
requested. The data set was on a direct access or magnetic tape was invoked; however, SVC 133 is inactive because RACF is not
device. This system completion code is accompanied by message properly installed on the system.
IEC032I. Refer to the explanation of message IEC032I for complete
System Action: The task is terminated.
information about the task that was ended and for an explanation of
the return code (rc in the message text) in register 15. System Programmer Response: If you have installed RACF on
your system, make sure that RACF is properly enabled. Check the
Source: DFSMSdfp
IFAPRDxx member pointed to by the PROD= statement in the
Programmer Response: Respond as indicated for message IEASYSxx parmlib member that was used when the system was ini-
IEC032I. tialized. For more information, see OS/390 Security Server (RACF)
System Programmer Response: If the error recurs and the
System Programmer's Guide.
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 EC4
problem. If no fix exists, contact the IBM Support Center. Provide the Explanation: NetView issues abend EC4 using CALLRTM in order
JCL and the program listing for the job. to terminate NetView tasks in error situations. NetView uses abend
EC4 during the NetView commands:
E82
STOP FORCE
Explanation: SVC 130 (RACROUTE REQUEST=AUTH macro)
To cause a NetView task that will not respond to other
was invoked; however, SVC 130 is inactive because RACF is not
signals to abend and recover or terminate.
properly installed on the system.
CLOSE IMMED
System Action: The task is terminated.
To cause a NetView task to shut down after approxi-
System Programmer Response: If you have installed RACF on
mately 1 minute if the task is still active after the CLOSE
your system, make sure that RACF is properly enabled. Check the
IMMED is processed.
IFAPRDxx member pointed to by the PROD= statement in the
IEASYSxx parmlib member that was used when the system was ini- System Action: Abend EC4 means that NetView decided the only
tialized. For more information, see OS/390 Security Server (RACF) way to stop the task was to intervene using a system abend.
System Programmer's Guide. System Programmer Response: If you are using the STOP
If you have not installed RACF on your system, this abend could be FORCE command or the CLOSE IMMED command to recover from
issued when a data set has the RACF indicator bit on. This could errors, notify your system programmer to determine whether cus-
occur if the data set came from a system with RACF installed. tomer or IBM programming is failing. The NetView product provides
the STOP FORCE and CLOSE IMMED commands as a means of
recovering from user or IBM product errors until the cause can be
E83
remedied. Using STOP FORCE or CLOSE IMMED as a normal
Explanation: SVC 131 (RACROUTE REQUEST=VERIFY macro) operations practice is otherwise a misuse of the product.
was invoked; however, SVC 131 is inactive because RACF is not
If you observe a high number of abend EC4 reports:
properly installed on the system.
Advise your operators that excessive use of error recovery com-
System Action: The task is terminated.
mands can cause storage loss and affect system performance.
System Programmer Response: If you have installed RACF on Ask them to use the non-abend STOP TASK and CLOSE STOP
your system, make sure that RACF is properly enabled. Check the before resorting to STOP FORCE or CLOSE IMMED.
IFAPRDxx member pointed to by the PROD= statement in the
If tasks will not stop when using STOP TASK, or NetView does
IEASYSxx parmlib member that was used when the system was ini-
not close down when using CLOSE STOP, call NetView Service
tialized. For more information, see OS/390 Security Server (RACF)
for advise on dumps or other problem determination needed to
System Programmer's Guide.
find and fix either customer or IBM programming defects.
E84
EC5
Explanation: SVC 132 (RACROUTE REQUEST=LIST macro) was
Explanation: JES common coupling services (JESXCF) detected
invoked; however, SVC 132 is inactive because RACF is not prop-
an unrecoverable error that causes the JES member to terminate
erly installed on the system.
abnormally. The hexadecimal reason code returned in register 0
System Action: The task is terminated. describes the error:
System Programmer Response: If you have installed RACF on Code Explanation
your system, make sure that RACF is properly enabled. Check the
00 An error was detected in the JESXCF recovery environ-
IFAPRDxx member pointed to by the PROD= statement in the
ment.
IEASYSxx parmlib member that was used when the system was ini-
tialized. For more information, see OS/390 Security Server (RACF) Source: JES common coupling services (JESXCF)
System Programmer's Guide. System Action: The system abnormally terminates the JES
member.
Operator Response: Notify your system programmer.
System Programmer Response: Find the associated JESXCF
abend and the associated JESXCF dump. Use these to diagnose the
error. If the problem is due to a coding error, search the problem
SCC-210 OS/390 V2R8.0 MVS System Codes
EC6 EC6
reporting data bases for a fix to the problem. Fix the problem and 0488 Invalid combination of events in list.
restart JES. If a fix does not exist, contact the IBM support center
0489 The task is not properly setup to wait.
with the return and reason codes and the dumps produced by the
error. 048A Bad Return code from ESTAE macro.
For additional information on dumping JES and JESXCF address 048B The input ECB list was longer than 1013 entries.
spaces, as well as restarting the JESXCF address space, see 048C Kernel wait and User Kernel Wait not interchangeable.
OS/390 MVS Programming: JES Common Coupling Services.
048D Unable to obtain latch for KSER storage pool.
EC6 048E Failed to release latch for KSER storage pool.
Explanation: An error occurred during processing of a callable 048F Set Ktimer failed.
service to OS/390 UNIX System Services (OS/390 UNIX). The call- 0490 Hash table count is invalid.
able service may have been originally issued as a function in a
04C1 Bad Entry code to module.
program or as a shell command.
04C2 Bad RC from DSPSERV Create.
A hexadecimal reason code in register 15 describes the error. The
reason codes are in the form xxxx yyyy, where xxxx represents 04C3 Bad RC from ALESERV Add.
internal information (not described here) and yyyy represents 04C4 Bad RC from ALESERV Extract.
external information shown below.
04C5 Bad RC from ALESERV Delete.
Only external reason codes are documented. There are many other
possible reason codes for internal errors. The internal errors should 04C6 Bad RC from DSPSERV Delete.
be reported to IBM. 04C7 Bad RC from TCBTOKEN macro.
Code Explanation 04C8 Bad RC from LXRES macro.
000D A failing physical file system requested that the OS/390 04C9 Bad RC from AXSET macro.
UNIX kernel be ended.
04CA Bad RC from ETCRE macro.
0016 An ESTAE macro returned an error return code.
04CB Bad RC from ETCON macro.
0025 An unsupported entry code was specified to a file
04CC Bad RC from ESTAE macro.
system service.
04CD Bad RC from VSM Locate macro.
0026 While building osi_thread support a failure was reported
by the set_dub_default service. 04CE Bad RC from LOAD or NUCLKUP macros.
0027 The Dspserv to create an address space failed. 04CF Bad RC from ETDES macro.
0029 The OMVS couple dataset is not accessible. 04D0 Bad Parms in ParmLib.
002A The OMVS couple dataset data not as expected. 04D1 Bad RC from CSVQUERY macro.
002B The OMVS address space could not be created. 04D2 Bad RC from Pgser macro.
002C The OMVS address space could not be initialized. 04D3 Bad RC from Axres macro.
002E The request was made by a process that was not prop- 04D4 Bad RC from Asext macro.
erly dubbed. 04D5 Bad RC from BPXFSIT during sysplex initialization.
0030 Issuing Syscalls from SRBs not allowed. 04D6 Bad RC from Lxfre macro.
0031 The syscall requested is not supported in SRB mode. 04D7 A colony AS ended due to Mother Thread termination.
0401 Bad Entry code to module. 04D8 IXCJOIN of Sysplex failed.
0402 Unexpected error. 04D9 XCF IXCQUERY operation failed.
0403 Set Ktimer (BPXXKTIM) failed. 04DA BPXXQHIT queue manager processing failed.
0421 Bad Entry code to module. 04DB Sysplex initialization failed.
0441 Invalid entry into the syscall layer. 04DC XCF IXCMSGI Message-In macro processing failed.
0442 Environmental Error. 04DD BPXOPIT failed to ATTACH command processor
0444 Invoking PC Number is not recognized. BPXOTASK.
0445 Invalid entry to PC. 0501 Bad Entry code to module.
0446 This thread is not known. 0503 OSAB already exists for the new task.
0447 Bad function request code. 0506 _Exit Abend Reason Code.
0481 Bad Entry code to module. 0507 Bad RC from StorMan Create.
0482 Not an OS/390 UNIX thread. 0508 Edsa does not exist in calling process.
0483 Too many events requested. 0509 Load of program failed, program not found.
0484 Mask contains an undefined event. 050A Load macro failed with unexpected abend code.
0485 No events in list. 050D Invalid Function # passed to BPXPKEXC.
0486 Invalid KSER address. 050E Bad RC from Attach Macro.
System Completion Codes SCC-211
EC6 EC6
050F Bad RC from call to BPXPTCAC. 05D1 A Storage Manager Control Block stack overflowed.
0510 BPXXNXMS(FREE) not issued to free allocated 05D2 A Master Cell Pool is out of extent storage cells.
resources.
05D3 A Master Cell Pool is out of control block cells.
0511 Required response not issued to BPXXNXMS(SYNC)
05D4 A Cell Pool for stack storage is out of cells.
request.
05D5 Expand stack invoked with an invalid cell pool ID.
0512 Response not allowed for BPXXNXMS(ASYNC) request.
05D6 Unexpected failure of IUTL invocation.
0515 The L16J in BPXJCPRC failed unexpectedly.
05D7 Bad return code from Estae.
0516 SAF failure during ACEE create/delete in BPXMRCSI.
05D8 Bad RC from Csrpqex service.
054F Current buffer is also on the free chain.
05D9 Bad RC from Csrpdac service.
0550 PPRT, KSER or PPRP ID overlayed.
05DA Bad RC from Csrpdis service.
0551 PPRA has been clobbered, contents inconsistent.
05DB Length of requested storage exceeds the maximum.
0553 Failure occurred during vdac task initialization.
05DC Invalid data space group ID is passed.
0554 Unexpected failure of IVTCSM invocation.
05DD Invalid data space alet is passed.
0555 No free Ppra slots while PpraActiveCount lifetime
MaxProcSys. 05DE Invalid data space Stoken is passed.
0556 Create Latch failure during process initialization. 0601 Sleep or Alarm had a system failure.
0557 PID not found in PPRA. 0603 An error occurred while closing a file.
0558 Obtain Latch failure during process initialization. 0605 Process could not notify parent of status change.
0559 PprtLatchedToken only with its PprtPprp, R4. 0606 Signal Code Failed to Obtain Local Lock.
055C Invokers BPXXJPID area date does not match. 0607 Signal generation failed.
055D Invokers BPXXJPID NEXT holds other latch, R4. 060A Bad Return Code from Save Signal Environment
Service.
055E Request for latch held by ancestor, R4, R5.
060B Process could not be stopped.
055F Invoker of BPXXJPID holds too many latches, R4.
060C Unexpected error in Load 16 and Jump from OESIR.
0560 Invalid Function # passed to internal MvsIptAffinity.
060D The OESIR was passed an invalid PPSD.
0561 SLTB has been clobbered, contents inconsistent.
0641 No Storage to create PTY Latchset.
0581 Bad RC from RESMGR macro.
0642 Duplicate Latchset Name detected.
0582 Bad Entry code to module.
0643 Unexpected Return Code from Latch Manager.
0583 Critical control blocks have been damaged.
0644 Storage not obtained for input queue.
0584 Bad return code from Estae.
0645 Storage not obtained for output queue.
0585 EOM recovery time out.
0646 The PTY device state is invalid or unexpected.
0586 Tcb/Ecb table is full.
0647 The PTY Device Driver input event is invalid.
0587 Bad return code from ATTACH.
0648 The Audit Trail EVENT is invalid.
05C0 Bad Entry code to module.
0649 A Count discrepancy was found in the PTY Buffers.
05C1 Storage Manager Latch Set already exists in this AS.
064A A Count discrepancy was found in the PTY Buffers.
05C2 Storage Manager Latch Create out of storage.
064B A Count discrepancy was found in the PTY Buffers.
05C3 Bad RC from Isglcrt service.
064C Bad RC from ESTAE macro.
05C4 Cell storage addr required.
064D Internal logic error in Pty support.
05C5 Bad RC from Aleserv macro.
064E Invalid Recovery Code during EOT/EOM processing.
05C6 Cannot do DSPSERV RELEASE for this cell pool.
0650 Invalid select()criteria.
05C7 Bad RC from Csrpbld service.
0651 Invalid select()function.
05C8 Bad RC from Csrpexp service.
0652 Invalid value in SBCS scan TRT table.
05C9 Cell pool token invalid.
0653 Invalid value in DBCS scan TRT table.
05CA Cell address is invalid.
0654 Input Device Driver type is not valid.
05CB Bad RC from Csrpget service.
0655 Invalid syscall type.
05CC Bad RC from Csrpfre service.
0656 Bad RC from ALESERV macro.
05CD Bad RC from Csrpqpl service.
0657 Bad RC from SmDsp allocate dataspace storage.
05CE Bad RC from Csrpcon service.
0658 Ocs Rty dd_config input buffer in error.
05CF Bad RC from Csrpact service.
0659 Ocs Rty dd_config output buffer exceeded.
05D0 A Storage Manager Control Block stack is invalid.
SCC-212 OS/390 V2R8.0 MVS System Codes
EC6 EC6
065B Unexpected return code from BPXXKTIM Set. 0731 Invalid retval from dd_configure.
065C Unexpected return code from BPXXKTIM Cancel. 0732 CSFS DDWT detected invalid DDWE.
065D Ocs Rty passed an invalid UIO to an OSI service. 0733 On PFS restart, a request was made to allocate a
restartbyte beyond the end of the Cabc.
0680 Bad Entry code to module.
0734 Could not create a msgq for colony thread support.
0685 Unexpected error in Load 16 and Jump.
0735 No saved CDSI token for request which requires token.
0686 Ptrace request code in Ptrb is invalid.
0736 Saved CDSI token valid from previous request.
0688 SVCUPDATE for ptrace SVC 144 failed.
0737 IXCXCDSI return and reason code indicate code error.
0689 Bad caller id to module.
0738 Internal structure of CDS inconsistent.
0700 Bad Entry code to module.
0739 Socket is not in a valid state.
0703 Bad RC from Attach Macro.
0781 Byte Range Lock Manager cannot be initialized.
0704 The File System that owns the root was not started.
0782 Byte Range Lock Manager cannot be terminated.
0705 Bad return from storage manager during initialization.
0783 Unexpected error occurred while unlocking a byte range.
0706 Bad return from PFS that owns root file system.
0784 Unexpected error occurred while registering a process.
0707 No ROOT statement was specified in SYS1.PARMLIB.
0785 Unexpected error occurred while registering an object.
0708 Invalid vnode address returned on vn_create by PFS.
0786 The Byte Range Lock Mgr detected an internal error.
0709 Queue Manager failed to Initialize.
0787 Error occurred while trying to get lock information.
070A Queue Manager failed to Connect.
0788 Unexpected error occurred while unregistering process.
070B An invalid Pnode was passed.
0789 Unexpected error occurred while unregistering object.
070C No KSER for Dispatchable Unit to be waited.
078A Unexpected error occurred while setting a lock.
070D No Pnwt was found.
078B Unexpected error occurred while calling MarkBroken.
070E The Pipe GFS was not found.
078C PprtFd field already used to hold a Vde ptr.
070F The GRS Latch Manager request failed.
078D Vnode Vde count is about to go negative.
0710 File System latch service error during Umask request.
078E Oapb Chain has not been cleaned up properly.
0711 Umask input error. Invalid bits set on in Mode.
078F IEAVLSUP query service failed.
0714 Received invalid ALET as a parameter.
0790 IEAVLSUP update service failed.
0715 Bad command code passed to module.
07E0 Level mismatch between kernel and TFS.
0716 Bad RC from file/directory close service.
07E1 Bad TFS mount table for filesys token.
0717 Read/Write invoked with an invalid syscall request.
07E2 Attempt to add a file to a non-directory.
0718 The Vnode received is invalid.
07E3 Bad chain pointer, data block not in file.
0719 Pointer to next filedes table page is 0.
07E4 Bad chain pointer, freeing block not in file.
071A The requested function requires a parent directory
vnode. 07E5 Allocating an already allocated block.
071B The length passed is negative - not valid. 07E6 Freeing an already freed block.
071C Attempt made to stop a colony PFS that was not started. 07E7 Attempt to free the superblock.
071D File System module is overlaying a latch handle. 07E8 Attempt to lookup in a non-directory.
071E Invalid Vnode address was referenced. 07E9 Bad length for a WTO.
071F BPXFRLOC caller did not have FRLOC on its 0800 Reg2 -> offending parameter in BPXXQHIT (see QhitT).
BPXXFENT.
0801 Unexpected return code from BPXXQHIT macro.
0720 BPXFTCLN detected a bad vnode cache queue.
0802 Incorrect UDP-plus flag combination.
0721 Module Exit while holding Vnode Latches.
0803 Structure of QHIT queue damaged.
0722 BPXXCALL EXCL when held latches were locked SHR.
0804 Channel program check occurred.
0723 PFS Recovery Token Stack overflow. See BPXZFSRB.
0805 Counter goes negative.
0724 Invalid Snode or socket detected.
0806 The buffer length passed is zero or incorrect.
0725 Error in socket read/write queue.
0807 Unexpected buffer sequence number detected.
0726 Error in setting up interface to TCP/IP.
0808 BPXUIIOC processing failed.
0727 Invalid control block address found.
0809 BPXXKSOC processing failed.
0729 Bad RC from PGSER Fix or Free.
080A Master socket not created.
0730 Colony AS was canceled when the OMVS AS was can-
080B Invalid value to an internal counter.
celed.
System Completion Codes SCC-213
EC6 EC6
080C Unexpected ERRNO from BPXUTBIN. 8604 Signal processing detected kernel shutdown.
080D QnodSeqNum mismatch found during accept. 864F Cannot get the Pty Latch in device driver.
080E Unexpected TCP state detected. 865A Cannot get the Rty Latch in device driver.
080F Attempt to DEQ UTBQEs on empty backlog queue. 8681 Sigaction callable service from Ptrace failed.
0810 Requested wait time is either too long or too short. 8682 Kill callable service from Ptrace failed.
0811 Timer processing caught its tail in a circular array. 8683 Sigprocmask callable service from Ptrace failed.
0812 TCP Readable BFQE chain is corrupted. 8684 Ptrace initialization of fork child failed.
0813 TCP Send BFQE chain is corrupted. 8687 Ptrace kernel function failed.
0814 The transport provider unexpectedly ran out of latching 868A Quiesce callable service from Ptrace failed.
resources for TCP sockets.
8701 The LFS Mother Task did not initialize.
0815 The buffer chain has been corrupted.
8702 Bad RC from Estae Macro.
0816 Bad return code from BPXXFAST NEWODB.
8712 Mask not changed. Security support not installed.
0817 Waitlist post failure unexpectedly.
8713 Security service error during Umask request.
0818 tcp_drop() invalidly invoked.
8728 A file system latch could not be obtained during term.
0819 UTTC2 invoked with 0 Bfqe and FIN not received.
C001 The callable service is incorrect or is not supported.
081A Unexpected return code from ?IWMELEAV macro.
C003 The callable service was not issued by a program
081B Osenv cell is no longer valid for use. running under a task control block (TCB).
081C A new ACEE was created when only a use count update C005 Callable services cannot be nested.
on an existing one is expected.
C007 The callable service was issued in cross-memory mode.
8002 OS/390 UNIX is not running.
C008 The calling process cannot be dubbed.
8004 The kernel has been terminated and restarted. Con-
C009 The parameter list contains an incorrect number of
nection to the old kernel is no longer valid.
parameters.
8006 The current process is being ended.
C00A A parameter length is negative.
800C An error occurred because of a duplicate file system
C00E An incorrect address was encountered when trying to
name.
move user parameter data.
8010 The caller has an incorrect PSW key.
C00F There is insufficient storage to copy user parameters.
8011 The caller is running in AR mode.
C019 The calling program was running in an incorrect request
8012 The caller has an incorrect signal data area (PPSD). block (RB) state.
8013 A ptrace funnel was invoked while the calling program C01A A security product is not installed.
was not being traced using ptrace.
C01B The user ID is not defined to the security product.
8014 A ptrace funnel was invoked in an incorrect thread.
C01C The user ID is in a group that does not have access to
8015 A ptrace funnel was invoked in an authorized process. OS/390 UNIX.
8017 A sleep callable service was invoked while OS/390 UNIX C01D The user ID does not have access to OS/390 UNIX.
was not running.
C01E The user ID does not have a UID.
8018 An invoker of a callable service had an incorrect PSW
C01F The user ID is in a group that has does not have a GID.
key.
C020 An internal error is reported by the security product.
8022 A ptrace funnel was invoked in an exited thread.
C021 The status specified on the _exit callable service is not
8024 A ptrace funnel was invoked in a process with a con-
valid.
trolled environment.
C023 The callable service was rejected because the
8028 The local INET failed to initialize.
requesting thread is in termination.
8033 Duplicate NETWORK parmlib statements with
C02F Caller is not authorized for this callable service.
DOMAINNAME(AF_INET) and TYPE(OESTACK) not
supported. C032 Exec Phase 2 failed because a sticky program was not
found in the MVS library search order.
8034 The specified Network type is not supported under
DOMAINNAME(AF_INET). C036 Exec Phase 2 failed because the execution of a HFS
executable was attempted from a controlled environ-
8035 TCP/IP BASE feature is required but not enabled.
ment.
8487 The task has already been pseudo-dubbed.
C443 Parameter Rules not present for the callable service.
8502 Required VSMLIST absent.
C448 Unexpected error in Load 16 and Jump.
8504 Bad RC from Exec Kernel syscall.
C552 Proc init invoker not key 0 and not supervisor state.
8514 An unexpected error occured in BPXJCSE while
C55A Unauthorized caller to BPXPRTRM internal callable
changing the address space/process identity for a
service.
socket.
SCC-214 OS/390 V2R8.0 MVS System Codes
EC6 EC6
FDxx Terminating signal with dump. 0401-081C See your IBM service representative.
FDF1 Unauthorized Caller to Exec2 internal callable service. 8002 If OS/390 UNIX has not been started, request the oper-
ator to issue the command to start OS/390 UNIX. Verify
FDF2 Osab does not exist in calling process.
that OS/390 UNIX completes its initialization before
FDF3 Bad Return Code from RACF Exec Set Uid/Gid Service. running the job again.
FDF4 Caller not authorized (key 0 | supervisor) for 8004 OS/390 UNIX has been stopped and restarted. Either
BPXMRKIN. issue a call to BPX1MPC (MVS process cleanup) to
FFxx Terminating signal with no dump. clean up the process before issuing another callable
service, or end the job.
FFF7 OS/390 UNIX is not running and the caller does not
expect a return code. 8006 A new callable service cannot be issued until this termi-
nation is complete.
FFF8 OS/390 UNIX is not running and the parameter list is too
long. 800C During file system initialization, an error occurred while
processing a duplicate file system name. Verify in the
FFFA Kernel termination or error with user in wait.
parmlib member used that there are no duplicate file
FFFE Normal end of Exec Phase 1, with multiple TCB/RBs. system names in either the ROOT or any MOUNT state-
ments in the BPXPRMxx parmlib member. This includes
Source: OS/390 UNIX System Services (BPX)
a duplicate that may be caused by any names when
System Action: The system abnormally ends the program issuing DSNAMEs are specified.
the callable service.
8010 Ptrace was invoked to process a ptraceable event, but
Programmer Response: the PSW key was not valid. You can only debug pro-
Code Response grams using ptrace that are run with a PSW key of 8.
000D The failing file system indicated that, should it fail, all of 8011 Ptrace was invoked to process a ptraceable event, but
OS/390 UNIX should be terminated also. the ASC mode was not valid. Ptrace only supports
non-AR mode programs. Only debug programs with
0016 Ptrace was invoked to process a ptraceable event, but
ptrace that are non-AR mode.
was unable to establish a recovery environment. The
probable cause is a shortage of system resources. 8012 Ptrace was invoked to process a ptraceable event, but
Obtain more system resources or reduce the use of the PPSD was not valid. Invoke ptrace with a valid
system resources. PPSD. The PPSD is mapped by macro BPXYPPSD.
0025 The entry code specified on the interface to a file system 8013 Ptrace was invoked to process a ptraceable event, but
service is not within the range of codes supported by the process ptrace was invoked in is not currently being
that interface. The request is not processed. debugged using ptrace. Invoke ptrace to process
ptraceable events only in processes being debugged by
0026 Ensure that the procedure for this colony has an entry in
ptrace.
the security product's started procedures table, and that
it specifies a valid userid. 8014 Ptrace was invoked to process a ptraceable event, but
the thread ptrace was invoked under was not dubbed.
0027 A possible reason for this failure is that the dataspace
Invoke ptrace to process ptraceable events only under
already exists. Verify that there are no duplicate
dubbed threads.
entrypoint names specified in the parmlib member.
8015 Ptrace was invoked to process a ptraceable event, but
0029 Run the XCF couple dataset utility for TYPE BPXMCDS
the process was authorized. Do not attempt to debug
to create the OMVS couple dataset. Issue the SETXCF
programs using ptrace in an authorized process.
COUPLE operator command to add the new
TYPE=BPXMCDS couple data set. 8017 Callable service sleep (BPX1SLP) was invoked when
OS/390 UNIX became inactive. Have the system oper-
002A Run the XCF couple dataset utility for TYPE BPXMCDS
ator use the DISPLAY OMVS operator console
to create the OMVS couple dataset. Issue the SETXCF
command to determine the status of OS/390 UNIX. The
COUPLE operator command to add the new
operator will probably need to restart OS/390 UNIX.
TYPE=BPXMCDS couple data set.
8018 An OS/390 UNIX callable service requires the invoker to
002B Consult registers 2 and 3 at time of error in the resulting
have a PSW key that would allow signals to be deliv-
dump to extract the ASCRE return and reason codes
ered. Change the application to invoke the OS/390 UNIX
indicating the nature of the error and contact your IBM
callable service with a PSW key that allows signals to be
Technical Support personnel.
delivered.
002C A cross memory post failure occurred during OMVS
8022 Ptrace was invoked to process a ptraceable event, but
address space initialization. Contact your IBM Technical
the thread ptrace was invoked under has already exited.
Support personnel.
Do not invoke ptrace to process ptraceable events under
002E Contact your IBM Technical Support personnel. exited threads.
0030 The calling process is either in termination or has 8024 Ptrace was invoked to process a ptraceable event, but
reached its limit on concurrent SRBs issuing OS/390 the process had security product controlled data sets
UNIX callable service. If the process is not in termi- open. Do not attempt to debug programs using ptrace in
nation, reissue the callable service. this controlled environment.
0031 Either issue the callable service from task mode or use 8028 Either the local INET was started without bringing up the
another callable service to perform the function required. converged sockets file system, or the converged sockets
file system was started with only the local INET. Con-
System Completion Codes SCC-215
EC6 EC6
verged sockets must be brought up with at least one The specified length of a variable-length parameter
other file system in order for the local INET to be is negative. (This error can occur only in programs
started. issuing Assembler callable services.)
8033 During file system initialization, an error occurred while The length of a variable-length parameter cannot be
processing a duplicate NETWORK parmlib statement negative. Callable services with variable-length
with DOMAINNAME(AF_INET) and TYPE(OESTACK). parameters normally specify them in pairs. The first
Verify that only one such statement is specified in the of the pair specifies the length of the variable-length
BPXPRMxx parmlib member. parameter that comes next.
8034 During file system initialization, an error occurred while The length of a fixed-length parameter exceeds the
processing a SUBFILESYSTYPE parmlib statement with allowable value. The maximum length of any fixed-
DOMAINNAME(AF_INET). The specified NAME is not length parameter cannot exceed 5000 bytes.
accepted. Only NAME(OESTACK) can be specified.
The size of an input buffer to be used for holding an
8035 The TCP/IP BASE feature is required for FILESYSTYPE output variable length parameter is specified as
OESTACK. Enable the feature in the IFAPRDxx more than 5000 bytes. The actual maximum size of
member. the parameter is much less. This error is reported
for performance reasons, to avoid inefficient usage
8487-8728 See your IBM service representative.
of system resources, including storage and proc-
C001 Specify the correct callable service number and resubmit essing time. Specify a smaller size for the input
the job. buffer.
C003 Callable services can be issued only in TCB mode. SRB C00E An error occurred while accessing the user parameter
mode is not supported. data. This can be caused by one of the following
C005 The system has detected a nested callable service. For conditions:
example: The total number of parameters is incorrect for the
The request block (RB) issues a callable service. An callable service being issued.
interrupt request block (IRB), for example, in an STIMER There is an error in one of the passed user parame-
exit, interrupts the RB and attempts to issue another ters causing OS/390 UNIX to program check when
callable service. The second callable service request is the parameter is accessed. Check for the following
detected and flagged as an error. conditions:
Correct the problem and resubmit the job. – A parameter that points to non-existent storage.
C007 You cannot issue callable services in cross-memory – A parameter that cannot be accessed in the
mode. current user PSW key.
Correct the problem and resubmit the job. Check for incorrect input parameters passed to the call-
C008 An error occurred while trying to make the calling able service.
process an OS/390 UNIX process. The system cannot C00F OS/390 UNIX cannot obtain storage to make a copy of
set an error return code for the caller because the caller the passed user parameters. This can be caused by one
does not expect a return code. A user ABDUMP has of the following conditions:
been requested. The cause of the error can be deter-
The user region is filled up and the STORAGE
mined from either the ABDUMP or the symptom dump.
request cannot be satisfied.
In the dump, register 2 contains the return code value
and register 3 contains the reason code value of the There is an error in one of the passed user parame-
failure. Analyze the return code and reason code for the ters, causing OS/390 UNIX to issue a STORAGE
cause of the problem. request for a large amount of storage that cannot be
satisfied.
C009 An error was encountered that prevents the running of
the callable service. However, the system cannot set an Check for incorrect input parameters passed to the call-
error return code for the caller because the input param- able service. If the parameters are correct, consider
eter list is incorrectly specified. increasing the user REGION size.
An ABDUMP or symptom dump has been requested for C019 Fix the application program. An OS/390 UNIX callable
the caller. In the dump, register 2 contains the return service, which requires that it be invoked from a specific
code value and register 3 contains the reason code request block, was invoked from an incorrect request
value of the original failure. block. The problem may have been caused by a pre-
vious invocation of callable service mvssigsetup from a
Do both of the following:
different request block. Because signals can be deliv-
Analyze the return code and reason code for the ered only to the request block that issued mvssigsetup,
cause of the original problem. OS/390 UNIX cannot perform the callable service.
Verify that the high-order bit of the last parameter C01A A security access facility (for example, RACF) is
list entry is set on. Currently, a maximum of 25 required, but not installed in the system.
parameter list entries is supported for a callable
C01B Define the user to the security product.
service.
C01C Define the current group as an OS/390 UNIX group.
C00A Check for incorrect input parameters passed to the call-
able service. One of the following conditions may have C01D Define the user as an OS/390 UNIX user.
occurred:
C01E Define the user as an OS/390 UNIX user.
SCC-216 OS/390 V2R8.0 MVS System Codes
EC7 EC7
C01F Define the current group as an OS/390 UNIX group.
EC7
C020 The security access facility (for example, RACF) has
Explanation: Advanced Program-to-Program Communications
reported an error condition. A dump should have already
(APPC) issues abend X'EC7' when it detects an unrecoverable
been taken by the security product. The cause of the
error.
error can be determined from the dump.
A reason code further describes the error:
A user ABDUMP has also been requested by the
OS/390 UNIX kernel. The error return code from the Code Explanation
security product can be determined from either the 000A1000 The activation of a logical unit failed because the VTAM
ABDUMP or the symptom dump. In the dump, register 4 application for the logical unit is not APPC-capable.
contains the error return code value and register 5 con- Check the VTAM APPL statement for the logical unit to
tains the error reason code value as reported by the ensure that you specified APPC=YES.
security product. Analyze the return code and reason
code for the cause of the problem. System Action: The system also issues abend X'EC7'
with reason code X'000A0037', which can be ignored.
C021 Specify a valid exit status on the _exit call. See the
BPXYWAST macro for a definition of the accepted exit 000100xx An internal error occurred.
status values. System Action: The system continues processing, but
C023 The BPX1PTX callable service should be issued to com- the requested APPC/MVS service fails. The system
plete the termination of the thread and to obtain a new writes an SVC dump.
thread to process. Other OS/390 UNIX callable services 00020001 A program called the Cleanup_AS service, but either did
are not supported while a thread is in this state. not provide the correct number of parameters or did not
C02F Caller must be APF authorized to issue a callable follow VLIST conventions.
service. System Action: The system continues processing, but
C032 Caller must insure that the program is either in LPA, the requested APPC/MVS service fails.
LINKLIST or the STEPLIB that the program is targeted 00020002 A program called the Cleanup_TP service but either did
to run with. not provide the correct number of parameters or did not
C036 Caller must ensure that the program is marked as follow VLIST conventions.
program controlled in the HFS, or place the program in System Action: The system continues processing, but
the MVS library search order and define it to SAF the requested APPC/MVS service fails.
program control.
00020003 - 00020006 An internal error occurred.
C443-C55A See your IBM service representative.
System Action: The system continues processing, but
FDxx If xx is in the range of X'01' to X'7F', a signal was APPC/MVS initialization fails.
received causing termination and a dump to be taken.
00020007 A program called the unauthorized Cleanup_TP service
This condition is usually the result of an application pro-
but either did not provide the correct number of parame-
gramming exception. For a description of the signal
ters or did not follow VLIST conventions.
represented by the value xx, check the appropriate
appendix “BPXYSIGH - Signal Constants” or “Signal System Action: The system continues processing, but
Defaults” in OS/390 UNIX System Services the requested APPC/MVS service fails.
Programming: Assembler Callable Services Reference. 00020008 A program issued a version of the
FDF1-FDF4 See your IBM service representative. Cleanup_Address_Space service that is not valid on the
release of MVS installed on the system.
FFxx If xx is in the range of X'01'to X'7F', a signal was
received causing termination. This condition is usually System Action: The system continues processing, but
the result of a process explicitly sending a terminating the requested APPC/MVS service fails.
signal to either itself or to another process in the process 00020009 A program called a version of the unauthorized
group. For a description of the signal represented by the Cleanup_TP service that is not valid on the release of
value xx, check the appropriate appendix “BPXYSIGH - MVS installed on the system.
Signal Constants” or “Signal Defaults” in OS/390 UNIX
System Services Programming: Assembler Callable Ser- System Action: The system continues processing, but
vices Reference. the requested APPC/MVS service fails.
FFF7 If OS/390 UNIX has not been started, request the oper- 0002000A A program called the ATBCUC1 service, which is not
ator to issue the START OMVS command. Verify that valid on the release of MVS installed on the system.
OS/390 UNIX completes initialization before running the System Action: The system continues processing, but
job again. the requested APPC/MVS service fails.
FFF8 An error was encountered that prevents the running of 0002000B An abend occurred when the system tried to access the
the callable service. However, the system cannot set an input parameters for a callable service. The caller of the
error return code for the caller because the input param- program does not have read or write access to the
eter list is incorrectly specified. Verify that the high-order parameters.
bit of the last parameter list entry is set on. Currently, a
00030001 An internal error occurred while the DISPLAY APPC
maximum of 25 parameter list entries is supported for a
command processor was trying to extract data for
callable service.
display.
FFFA-FFFE See your IBM service representative.
System Action: The system ends the DISPLAY
command but APPC continues processing.
System Completion Codes SCC-217
EC7 EC7
00050001 A system error occurred during conversion of a trans- 00070004 The system failed to initialize the APPC/XCF group
action program (TP) profile. name. The system could not find a match for
CVTSNAME in the system information returned from the
System Action: The system does not use the TP
IXCQUERY macro. The system has not initialized the
profile.
APPC/XCF group name.
00050002 An internal error occurred.
System Action: The system continues processing, but
System Action: The system does not use the TP APPC resources are not available. If the operator enters
profile. the START APPC command in response to this problem.
00050300 - 000503E0 An internal error occurred during VSAM proc- APPC initialization will fail.
essing. 00070005 An unauthorized attempt was made to start APPC.
System Action: The system continues processing, but APPC can only be invoked by the installation as a
the requested APPC/MVS service fails. started task using the START APPC command.
00050420 - 00050424 A system error occurred during transaction System Action: The system sends messages to the
program (TP) profile processing. operator console to show APPC's status following the
abend. If restart conditions are met, APPC will restart
System Action: The system does not use the TP
itself in another address space.
profile.
00070006 APPC was unable to obtain required common storage.
00050800 - 00050822 An internal error occurred during TP profile or
Register 2 contains the return code from the system
side information processing.
STORAGE macro.
System Action: The system continues processing, but
System Action: The system sends messages to the
the requested APPC/MVS service fails.
operator console to show APPC's status following the
00050200 An internal error occurred during APPC initialization abend. If restart conditions are met, APPC will restart
itself in another address space.
System Action: The system continues processing, but
APPC/MVS initialization fails. 00070008 An illegal state transition was requested for APPC.
00050602 - 00050657 An internal error occurred during TP profile or System Action: The system sends messages to the
side information processing. operator console to show APPC's status following the
abend. If restart conditions are met, APPC will restart
00060001 - 00060004 An internal error occurred.
itself in another address space.
System Action: The system abnormally ends APPC. If
00070009 APPC was unable to obtain required private storage.
the restart criteria are met, APPC restarts in a new
Register 2 contains the return code from the system
address space.
STORAGE macro.
00060005 - 00060009 An internal error occurred.
System Action: The system sends messages to the
System Action: APPC continues processing, but operator console to show APPC's status following the
inbound processing could be affected. abend. If restart conditions are met, APPC will restart
0006000A An internal error occurred. itself in another address space.
System Action: The system abnormally ends APPC. If 0007000A An internal error occurred.
the restart criteria are met, APPC restarts in a new System Action: The system sends messages to the
address space. operator console to show APPC's status following the
0006000B An internal error occurred. abend. If restart conditions are met, APPC will restart
itself in another address space.
System Action: APPC continues processing, but
inbound processing could be affected. 0007000B An illegal state transition was requested for one of
APPC's divisions.
0006000C - 0006000E An internal error occurred.
System Action: The system sends messages to the
System Action: The system abnormally ends APPC. If
operator console to show APPC's status following the
the restart criteria are met, APPC restarts in a new
abend. If restart conditions are met, APPC will restart
address space.
itself in another address space.
0006000F - 00060014 An internal error occurred.
0007000C The system cannot load the ATBINPVT load module.
System Action: APPC continues processing, but
System Action: The system sends messages to the
inbound processing could be affected.
operator console to show APPC's status following the
00070001 - 00070002 An internal error occurred. abend. If restart conditions are met, APPC will restart
itself in another address space.
System Action: The system sends messages to the
operator console to show APPC's status following the 0007000D - 0007000E An internal error occurred.
abend. If restart conditions are met, APPC will restart
System Action: The system sends messages to the
itself in another address space.
operator console to show APPC's status following the
00070003 Initialization of the APPC/cross-system coupling facility abend. If restart conditions are met, APPC will restart
(XCF) group name failed. itself in another address space.
System Action: The system continues processing, but 0007000F An initialization error occurred. The system was unable
APPC resources are not available. If the operator enters to obtain an APPC resource.
the START APPC command in response to this problem.
System Action: The system continues processing, but
APPC initialization will fail.
SCC-218 OS/390 V2R8.0 MVS System Codes
EC7 EC7
the error will cause the failure of APPC initialization 00090054 APPC/MVS cannot access the conversation_ID param-
processing if the operator enters a START APPC eter for the Error_Extract service.
command.
System Action: The system does not process the call
00070010 An internal error occurred. to Error_Extract. The system continues other processing.
System Action: The system sends messages to the 00090055 APPC/MVS cannot access the service_name parameter
operator console to show APPC's status following the for the Error_Extract service.
abend. If restart conditions are met, APPC will restart
System Action: The system does not process the call
itself in another address space.
to Error_Extract. The system continues other processing.
00070011 The system was unable to load the ATBINPVT load
00090056 APPC/MVS cannot access the service_reason_code
module. Register 2 contains the return code from the
parameter for the Error_Extract service.
system LOAD macro.
System Action: The system does not process the call
System Action: The system sends messages to the
to Error_Extract. The system continues other processing.
operator console to show APPC's status following the
abend. If restart conditions are met, APPC will restart 00090057 APPC/MVS cannot access the message_text_length
itself in another address space. parameter for the Error_Extract service.
00070012 The system was unable to load the ATBINLPA load System Action: The system does not process the call
module. Register 2 contains the return code from the to Error_Extract. The system continues other processing.
system LOAD macro. 00090058 APPC/MVS cannot access the message_text parameter
System Action: The system sends messages to the for the Error_Extract service.
operator console to show APPC's status following the System Action: The system does not process the call
abend. If restart conditions are met, APPC will restart to Error_Extract. The system continues other processing.
itself in another address space.
00090059 APPC/MVS cannot access the
00070013 The system was unable to load the ATBINMIG load error_log_product_set_ID_length parameter for the
module. Register 2 contains the return code from the Error_Extract service.
system LOAD macro.
System Action: The system does not process the call
System Action: The system sends messages to the to Error_Extract. The system continues other processing.
operator console to show APPC's status following the
00090060 APPC/MVS cannot access the error_log_product_set_ID
abend. If restart conditions are met, APPC will restart
parameter for the Error_Extract service.
itself in another address space.
System Action: The system does not process the call
00070015 An attempt was made to update the state of a division,
to Error_Extract. The system continues other processing.
but the division identifier is not defined.
00090061 APPC/MVS cannot access the error_log_data_length
System Action: The system sends messages to the
parameter for the Error_Extract service.
operator console to show APPC's status following the
abend. If restart conditions are met, APPC will restart System Action: The system does not process the call
itself in another address space. to Error_Extract. The system continues other processing.
00070019 - 0007001D An internal error occurred. 00090062 APPC/MVS cannot access the error_log_data parameter
for the Error_Extract service.
System Action: APPC cannot restart itself in another
address space. APPC services remain unavailable. System Action: The system does not process the call
to Error_Extract. The system continues other processing.
00090001 The caller specified a parameter list that contained too
many or too few parameters for the service being 00090063 APPC/MVS cannot access the return_code parameter
invoked, for the Error_Extract service.
System Action: The system denies the request. No System Action: The system does not process the call
conversations end as a result of the error, unless it to Error_Extract. The system continues other processing.
results in the abnormal ending of the address space. If
00090064 APPC/MVS cannot access the reason_code parameter
the address space abnormally ends, all conversations
for the Error_Extract service.
owned by the address space will be cleaned up as part
of normal APPC processing. System Action: The system does not process the call
to Error_Extract. The system continues other processing.
00090002 An abend occurred while the system tried to access one
of the following: 00090065 A program specified an incorrect number of parameters
on a call to Error_Extract.
Input parameters to which the caller does not have
read access. System Action: The system does not process the call
Output parameters to which the caller does not have to Error_Extract. The system continues other processing.
write access. 00090066 - 00090068 An internal error occurred in APPC/MVS.
00090003 - 00090051 An internal error occurred. System Action: The system does not process the call
00090052 An internal error occurred. to Error_Extract. The system continues other processing.
System Action: The system continues processing, but 00090069 APPC/MVS cannot access the parameter list for the
the requested APPC/MVS service fails. The system Error_Extract service.
issues an SVC dump. System Action: The system does not process the call
to Error_Extract. The system continues other processing.
System Completion Codes SCC-219
EC7 EC7
00090070 - 00090072 An internal error occurred in APPC/MVS. 0010000F The parameter list passed to the Disconnect Service
contained an incorrect number of parameters.
System Action: The system continues processing, but
the requested APPC/MVS service fails. The system System Action: APPC continues processing, but the
takes an SVC dump. system does not perform the requested service.
000A00xx An internal error occurred. 00100010 The parameter list passed to the Identify Service con-
tained an incorrect number of parameters.
System Action: APPC continues processing.
System Action: APPC continues processing, but the
000A1000 The activation of a logical unit failed because the VTAM
system does not perform the requested service.
application for the logical unit is not APPC-capable.
Check the VTAM APPL statement for the logical unit to 00100011 The parameter list passed to the Unidentify Service con-
ensure that you specified APPC=YES. tained an incorrect number of parameters.
00100003 The join group service abnormally ended while trying to System Action: APPC continues processing, but the
access the XCFMSGIN_EXIT_ADDRESS input param- system does not perform the requested service.
eter.
00100012 The parameter list passed to the Define Local TP
System Action: The system rejects the request. The Service contained an incorrect number of parameters.
system does not join the caller to the APPC group.
System Action: APPC continues processing, but the
00100004 The join group service abnormally ended while trying to system does not perform the requested service.
access the XCFMSGIN_MEMDATA input parameter.
00100013 The parameter list passed to a transaction scheduler
System Action: The system rejects the request. The interface service contains inaccessible parameters.
system does not join the caller to the APPC group.
System Action: APPC continues processing, but the
00100005 The join group service abnormally ended while trying to system does not perform the requested service.
access the XCF_RETURN_CODE input parameter.
00100014 The join service failed while trying to access the param-
System Action: The system rejects the request. The eter pointers. The parameter list is inaccessible.
system does not join the caller to the APPC group.
System Action: The system rejects the request. The
00100006 The join group service abnormally ended while trying to system does not join the caller to the APPC group.
access the XCF_REASON_CODE input parameter.
00100015 The parameter list passed to the Set_AS_Attributes
System Action: The system rejects the request. The service contained an incorrect number of parameters.
system does not join the caller to the APPC group.
System Action: The system continues processing, but
00100007 The join group service abnormally ended while trying to the requested APPC/MVS service fails.
access the RETURN_CODE input parameter.
00100016 The parameter list passed to the Set_AS_Attributes
System Action: The system rejects the request. The service contains inaccessible parameters.
system does not join the caller to the APPC group.
00100017 - 00100018 An internal error occurred.
00100008 The join group service abnormally ended while trying to
System Action: The system automatically restarts
access the MEMBER_TOKEN input parameter.
APPC. If a second failure occurs, APPC abnormally
System Action: The system rejects the request. The abends.
system does not join the caller to the APPC group.
00100019 An internal error occurred.
00100009 An incorrect number of parameters was passed to the
System Action: The callers task is ended.
join group service.
0010001F A program issued a version of the Identify service that is
System Action: The system rejects the request. The
not valid on the release of MVS installed on the system.
system does not join the caller to the APPC group.
System Action: The system continues processing, but
0010000A - 0010000B An internal error occurred.
the requested APPC/MVS service fails.
System Action: The system automatically restarts
00100020 A program issued a version of the Unidentify service that
APPC. If a second failure occurs, APPC will abnormally
is not valid on the release of MVS installed on the
end.
system.
0010000C The parameter list passed to the Associate Service con-
System Action: The system continues processing, but
tained an incorrect number of parameters.
the requested APPC/MVS service fails.
System Action: APPC continues processing, but the
00100023 A program issued a version of the Join_Sysappc_Group
system does not perform the requested service.
service that is not valid on the release of MVS installed
0010000D The parameter list passed to the Connect Service con- on the system.
tained an incorrect number of parameters.
System Action: The system continues processing, but
System Action: APPC continues processing, but the the requested APPC/MVS service fails.
system does not perform the requested service.
00100025 A program passed a parameter list containing an incor-
0010000E The parameter list passed to the Control Service con- rect number of parameters to the Version_Service.
tained an incorrect number of parameters.
00100026 A program passed an inaccessible parameter list to the
System Action: APPC continues processing, but the Version_Service.
system does not perform the requested service.
SCC-220 OS/390 V2R8.0 MVS System Codes
EC7 EC7
00100027 A program passed a parameter list containing inacces- Input parameters to which the caller does not have
sible parameters to the Version_Service. read access
Output parameters to which the caller does not have
System Action: The system continues processing, but
write access.
the requested APPC/MVS service fails.
00140009 The Get_Event service abnormally ended because the
00100028 An internal error occurred during processing of the Iden-
caller specified a parameter list that contained too many
tify service.
or too few parameters.
System Action: The system ends the caller's task.
0014000A The Get_Event service abnormally ended because the
00100029 An internal error occurred during processing of the Uni- system tried to access one of the following:
dentify service.
Input parameters to which the caller does not have
System Action: The system ends the caller's task. read access
00120001 The Accept_Test service abnormally ended because the Output parameters to which the caller does not have
caller's parameter list was incorrect. write access.
00120002 The Accept_Test service abnormally ended while trying 0014000B The Query_Allocate_Queue service abnormally ended
to write to caller's parameter list. because the caller specified a parameter list that con-
tained too many or too few parameters.
00120003 The Register_Test service abnormally ended because
the caller's parameter list was incorrect. 0014000C The Query_Allocate_Queue service abnormally ended
because the system tried to access one of the following:
00120004 The Register_Test service abnormally ended while trying
to write to caller's parameter list. Input parameters to which the caller does not have
read access
00120005 The Unregister_Test service abnormally ended because
Output parameters to which the caller does not have
the caller's parameter list was incorrect.
write access.
00120006 The Unregister_Test service abnormally ended while
0014000D The Set_Allocate_Queue_Attributes service abnormally
trying to write to caller's parameter list.
ended because the caller specified a parameter list that
001300xx An internal error occurred. contained too many or too few parameters.
System Action: The system action is unpredictable. 0014000E The Set_Allocate_Queue_Attributes service abnormally
ended because the system tried to access one of the
00140001 The Register_For_Allocates service abnormally ended
following:
because the caller specified a parameter list that con-
tained too many or too few parameters. Input parameters to which the caller does not have
read access
00140002 The Register_For_Allocates service abnormally ended
Output parameters to which the caller does not have
because the system tried to access one of the following:
write access.
Input parameters to which the caller does not have
0014000F The Set_Conversation_Accounting_Information service
read access
abnormally ended because the caller specified a param-
Output parameters to which the caller does not have
eter list that contained too many or too few parameters.
write access.
00140010 The Set_Conversation_Accounting_Information service
00140003 The Receive_Allocates service abnormally ended
abnormally ended because the system tried to access
because the caller specified a parameter list that con-
one of the following:
tained too many or too few parameters.
Input parameters to which the caller does not have
00140004 The Receive_Allocates service abnormally ended
read access
because the system tried to access one of the following:
Output parameters to which the caller does not have
Input parameters to which the caller does not have write access.
read access
00140011 The Unregister_For_Allocates service abnormally ended
Output parameters to which the caller does not have
because the caller specified a parameter list that con-
write access.
tained too many or too few parameters.
00140005 The Reject_Conversation service abnormally ended
00140012 The Unregister_For_Allocates service abnormally ended
because the caller specified a parameter list that con-
because the system tried to access one of the following:
tained too many or too few parameters.
Input parameters to which the caller does not have
00140006 The Reject_Conversation service abnormally ended
read access
because the system tried to access one of the following:
Output parameters to which the caller does not have
Input parameters to which the caller does not have write access.
read access
00140013 - 00140020 An internal error occurred.
Output parameters to which the caller does not have
write access. 00150001 - 00150004 During the activation of a logical unit (LU),
APPC/MVS encountered an error while attempting to
00140007 The Set_Allocate_Queue_Notification service abnormally
perform resource manager restart processing.
ended because the caller specified a parameter list that
contained too many or too few parameters. System Action: The system writes an SVC dump and
continues processing. APPC/MVS adds the LU to the
00140008 The Set_Allocate_Queue_Notification service abnormally
configuration, but the LU can process only conversations
ended because the system tried to access one of the
with a synchronization level of none or confirm.
following:
System Completion Codes SCC-221
EC7 EC7
00150005 An internal error occurred. 0015001C During the activation of a logical unit (LU), APPC/MVS
encountered an error while attempting to perform
System Action: The system writes an SVC dump and
resource manager restart processing.
continues processing. APPC/MVS accepts Allocate
requests for only conversations with a synchronization System Action: The system writes an SVC dump and
level of none or confirm. continues processing. APPC/MVS adds the LU to the
configuration, but the LU can process only conversations
00150006 During the activation of a logical unit (LU), APPC/MVS
with a synchronization level of none or confirm.
encountered an error while attempting to perform
resource manager restart processing. 0015001D - 00150028 An internal error occurred.
System Action: The system writes an SVC dump and System Action: The system writes an SVC dump and
continues processing. APPC/MVS adds the LU to the continues processing. The system does not purge log-
configuration, but the LU can process only conversations name affinities for partner LUs that established protected
with a synchronization level of none or confirm. conversations with an APPC/MVS LU.
00150008 During the processing of a synchronization request, a 00150029 - 0015002A During the activation of a logical unit (LU),
partner LU detected a syncpoint architecture protocol APPC/MVS encountered an error while attempting to
violation made by APPC/MVS during the syncpoint perform resource manager restart processing.
transaction exchange.
System Action: The system writes an SVC dump and
System Action: The system writes an SVC dump and continues processing. APPC/MVS adds the LU to the
continues processing. The syncpoint request completes, configuration, but the LU can process only conversations
but the state of the distributed resources is unknown; a with a synchronization level of none or confirm.
heuristic condition might exist. The syncpoint conversa-
0015002B APPC/MVS reported an asynchronous abend during
tion is deallocated by the partner.
syncpoint processing.
00150009 - 0015000B An internal error occurred while the DISPLAY
System Action: APPC/MVS continues to process the
APPC command processor was trying to extract data for
syncpoint. An asynchronous abend may require
display.
APPC/MVS to perform re-synchronization to resolve the
System Action: The system writes an SVC dump and unit of recovery.
continues processing. The system ends the DISPLAY
0015002C An internal error occurred in APPC/MVS during
command processing. Other APPC/MVS work continues.
syncpoint processing.
0015000C - 00150011 During the activation of a logical unit (LU),
System Action: The system continues processing. The
APPC/MVS encountered an error while attempting to
system issues an SVC dump.
perform resource manager restart processing.
0015002D An internal error occurred in APPC/MVS during
System Action: The system writes an SVC dump and
syncpoint processing.
continues processing. APPC/MVS adds the LU to the
configuration, but the LU can process only conversations System Action: The system continues processing.
with a synchronization level of none or confirm. APPC/MVS may perform re-synchronization to resolve
the unit of recovery.
00150012 An internal error occurred.
0016xxxx An internal error occurred.
System Action: The system writes an SVC dump and
continues processing. APPC/MVS accepts Allocate System Action: The system writes an SVC dump and
requests for only conversations with a synchronization continues processing. APPC/MVS continues processing,
level of none or confirm. but the results of the following syncpoint processing
could be unpredictable:
00150013 - 00150017 APPC/MVS received an unexpected return
code from an RRS callable service during resynchroniza- Allocate requests for conversations with a synchro-
tion processing for a unit of recovery, associated with a nization level of syncpt
protected conversation. Resynchronization processing to resolve incomplete
System Action: The system writes an SVC dump and units of recovery and bring distributed resources to
continues processing. The resynchronization transaction a consistent state.
processing ends, and the unit of recovery remains Source: APPC/MVS
incomplete.
Operator Response: If APPC abends and does not restart itself
00150018 An internal error occurred, causing the APPC/MVS automatically, enter the START command to restart APPC.
resource manager exits for an LU to become unset.
For errors during FMH-5 manager inbound processing, reason code
Message ATB208I identifies the LU whose resource
0006xxxx, quiesce APPC by deleting all of the logical units (LU) that
manager exits have been unset.
are active in order to reject any new inbound TPs. Allow TPs in
System Action: The system writes an SVC dump and progress to end normally. When APPC has quiesced, enter a
continues processing. All active protected conversations START command to restart APPC.
associated with the LU have ended abnormally.
If the system failed to initialize APPC, and APPC is an integral part
APPC/MVS automatically re-registers the LU's exits.
of the installation, then reIPL the system.
0015001A - 0015001B An internal error occurred.
See the system messages written to the console to track the status
System Action: The system writes an SVC dump and of APPC's ending/restart processing.
continues processing. The system does not purge log-
If multiple system abends occur or if a reIPL does not correct the
name affinities for partner LUs that established protected
problem, notify the system programmer.
conversations with an APPC/MVS LU.
SCC-222 OS/390 V2R8.0 MVS System Codes
EFB EFB
Programmer Response: Depending on the reason code, do one of 04 The IXZXIXAT macro returned a non-zero return code
the following: while the JES3DLOG address space was attempting to
attach to the JESXCF group. Registers 2 and 3 when
00020001 - 00020002 Ensure that your program provides all the
the EFB abend is issued contain the return and reason
parameters for the requested APPC/MVS service.
codes from the IXZXIXAT macro call.
Ensure that all bits except for the high order bit are off.
The high order bit must be on. Correct the parameter list 05 The IXZXIXMB macro returned a non-zero return code
for the requested service and submit the program again. while the JES3DLOG address space was attempting to
attach to the default mailbox. Registers 2 and 3 when
00020008 - 0002000A Do one of the following:
the EFB abend is issued contain the return and reason
Invoke the indicated call on a system where the cor- codes from the IXZXIXMB macro call.
responding version of MVS is installed.
06 The IXZXIXMD macro returned a non-zero return code
Invoke the version of the service that is appropriate while the JES3DLOG address space was attempting to
for the release of MVS installed on the system. delete the default mailbox. Registers 2 and 3 when the
00010000C - 000100016 Ensure that your program provides all the EFB abend is issued contain the return and reason
parameters for the requested APPC/MVS service. codes from the IXZXIXMD macro call.
Ensure that all bits except for the high order bit are off. 07 The MCSOPMSG macro returned a return code greater
The high order bit must be on. Correct the parameter list than 12 while the JES3DLOG address space was
for the requested service and submit the program again. attempting to access the next message in its message
0010001F - 00100023 Do one of the following: data space. Registers 2 and 3 when the EFB abend is
issued contain the return and reason codes from the
Call the service on a system where a version of
MCSOPMSG macro call.
MVS that supports the service is installed.
08 IATCNDFM returned a non-zero return code when it was
Call the version of the service that is supported on
called by IATCNDMS to format an MDB in JES3 DLOG
the release of MVS that is currently installed.
format. Registers 2 and 3 when the EFB abend is issued
00100025 - 00100027 Ensure that the call to the Version_Service is contain the return and reason codes from IATCNDFM.
coded correctly.
09 An invalid function code was passed to IATCNDAL. Reg-
For other parameter errors, check the program to ensure that all ser- ister 2 when the EFB abend is issued contains the func-
vices are correctly coded and that all parameters are correctly speci- tion code.
fied.
0A An invalid function code was passed to IATCNDIT. Reg-
If the problem recurs, notify the system programmer. ister 2 when the EFB abend is issued contains the func-
tion code.
System Programmer Response: Examine the SVC dump and the
APPC trace records, if available, for the cause of the problem. For 0B An invalid function code was passed to IATCNDTR.
the following return codes, try using LUDEL followed by LUADD, or Register 2 when the EFB abend is issued contains the
VTAM VARY INACT followed by VARY ACT, to reactivate the LU: function code.
00150001 - 00150004 0C An invalid message pointer cell was returned by
00150006 IATCNDFM when it was called by IATCNDIT to format
0015000C - 00150011 an MDB in JES3 DLOG format.
0015001C
0D The RESMGR macro returned a non-zero return code
00150029 - 0015002A
while the JES3DLOG address space was attempting to
If the problem cannot be resolved or if the reason code indicates an setup a task level resource manager. Registers 2 and 3
internal error, search problem reporting data bases for a fix for the when the EFB abend is issued contain the return and
problem. If no fix exists, contact the IBM Support Center. Provide reason codes from the RESMGR macro call.
the SVC dump.
Source: JES3
System Action: A dump of the JES3DLOG address space and its
EFB
message data space is taken, the JES3DLOG address space is ter-
Explanation: JES3 DLOG processing encountered an error. The minated, and the DLOG facility is disabled.
abend reason code identifies the specific error.
Note: A dump will not be taken for reason code 2 if a return code
Code Explanation of four (extended MCS console already active) is returned
01 The ASEXT macro returned a non-zero return code from the MCSOPER macro.
while the JES3DLOG address space was attempting to System Programmer Response: Contact IBM support and provide
extract the address space parameters. Registers 2 and 3 the following documentation:
when the EFB abend is issued contain the return and
The EFB abend reason code
reason codes from the ASEXT macro call.
The return and reason codes from the service that was called (if
02 The MCSOPER macro returned a non-zero return code
applicable)
while the JES3DLOG address space was attempting to
activate its extended MCS console. Registers 2 and 3 The dump taken by the JES3DLOG address space (if any)
when the EFB abend is issued contain the return and The SYSLOG around the time of error
reason codes from the MCSOPER macro call.
01 See OS/390 MVS Programming: Authorized Assembler
03 Reserved - not used Services Reference ALE-DYN for a description of the
ASEXT return and reason codes.
System Completion Codes SCC-223
Fnn Fnn
The following additional documentation should be Compiler listings for modules IATCNDMS and
provided: IATCNDFM.
Compiler listings for modules IATCNDS and 09 The following additional documentation should be
IATCNDIT. provided:
02 See OS/390 MVS Programming: Authorized Assembler Compiler listings for modules IATCNDTK and
Services Reference LLA-SDU for a description of the IATCNDAL.
MCSOPER return and reason codes.
0A The following additional documentation should be
The following additional documentation should be provided:
provided:
Compiler listings for module IATCNDIT and the
Compiler listing for module IATCNDIT. module that called IATCNDIT (usually IATCNDTK or
IATCNDRR)
04 See OS/390 MVS Programming: JES Common Coupling
Services for a description of the IXZXIXAT return and 0B The following additional documentation should be
reason codes. provided:
The following additional documentation should be Compiler listings for module IATCNDTR and the
provided: module that invoked it via the IATXDLTR macro.
The caller of IATCNDTR can be found by examining
Compiler listing for module IATCNDIT.
the linkage stack in the dump at the time of error.
A non-zero return code from the IXZXIXAT macro is When the caller's registers and return address are
usually preceded by an ABEND from the IXZXIXAT saved on the linkage stack via a "BAKR R14,0"
service routine (e.g. DC5 abend). If a dump was instruction.
taken of the JESXCF address space as a result of
0C The following additional documentation should be
that abend, that dump should also be provided as
provided:
part of the documentation.
Compiler listings for modules IATCNDFM and
05 See OS/390 MVS Programming: JES Common Coupling
IATCNDMS.
Services for a description of the IXZXIXMB return and
reason codes. 0D See OS/390 MVS Programming: Authorized Assembler
The following additional documentation should be
Services Reference LLA-SDU for a description of the
RESMGR return and reason codes.
provided:
The following additional documentation should be
Compiler listing for module IATCNDIT.
provided:
A non-zero return code from the IXZXIXMB macro is
Compiler listing for module IATCNDIT.
usually preceded by an ABEND from the IXZXIXMB
service routine (e.g. DC5 abend). If a dump was
taken of the JESXCF address space as a result of
that abend, that dump should also be provided as Fnn
part of the documentation.
Explanation: The system detected an error while processing a
06 See OS/390 MVS Programming: JES Common Coupling Supervisor Call (SVC) instruction. The last 2 digits of this completion
Services for a description of the IXZXIXMD return and code, nn, are the operand of the SVC instruction in hexadecimal. For
reason codes. example, completion code X'F0D' means that the error occurred
The following additional documentation should be while the system was processing SVC X'0D', that is, SVC 13.
provided: One of the following occurred:
Compiler listing for module IATCNDIT. | When nn is equal to 13, 14, 17, or 37, recovery for
A non-zero return code from the IXZXIXMD macro | OPEN/CLOSE/EOV failed to recognize a passed internal abend
is usually preceded by an ABEND from the | code. Register 12 contains the passed internal abend code. This
IXZXIXMD service routine (e.g. DC5 abend). If a | is probably a system error. If the ABEND is accompanied by
dump was taken of the JESXCF address space as a | message IEC900I, the code was issued by DFSMSdfp and the
result of that abend, that dump should also be pro- | code explanations are provided in this section. If the ABEND is
vided as part of the documentation. | accompanied by error messages starting with message prefix
| EDG, the code was issued by DFSMSrmm. See DFSMS/MVS
07 See OS/390 MVS Programming: Authorized Assembler
| DFSMSrmm Implementation and Customization Guide for expla-
Services Reference ENF-IXG for a description of the
| nations of the codes when they are issued by DFSMSrmm.
MCSOPMSG return and reason codes.
When nn is not equal to 13, 14, 17, or 37, the system detected
The following additional documentation should be
an incorrect SVC instruction.
provided:
Source: Supervisor control
Compiler listings for modules IATCNDIT and
IATCNDMS. System Action: Depending on the value of nn, the system does
the following:
08 See macro IATYCNDF for a description of the return
codes from IATCNDFM. When nn is equal to 13, 14, 17, or 37, the system records the
unrecognized internal abend code in register 12. It issues
The following additional documentation should be
message IEC900I.
provided:
SCC-224 OS/390 V2R8.0 MVS System Codes
When nn is not equal to 13, 14, 17, or 37, the system records in – Make sure that the SVC instruction was not incorrectly
register 2 the address of the request block (RB) for the program modified.
that issued the incorrect SVC.
– Check the operand against the valid codes for the
Operator Response: If the system programmer asks for an SVC system being used.
dump, set the following SLIP trap:
– Determine if the SVC that was issued has been
SLIP SET,COMP=Fnn,ACTION=SVCD,END installed correctly in the system. For a detailed
System Programmer Response: Depending on the value of nn, description on creating installation defined SVCs, see
do one of the following: OS/390 MVS Programming: Authorized Assembler Ser-
vices Guide, or OS/390 MVS Initialization and Tuning
When nn is equal to 13, 14, 17, or 37, see message IEC900I. Reference.
Search the problem reporting data bases for a fix for the
problem. If no fix exists, ask the operator to set a SLIP trap to a. Ensure that the EPNAME specified in IEASVCxx
obtain an SVC dump. Contact the IBM Support Center. Provide parmlib member or on the SVCUPDTE macro,
the SVC dump and, if available, the logrec data set error record. matches the name specified in the LINKEDIT JCL
used to link the SVC routine into SYS1.NUCLEUS
When nn is not equal to the above values, do the following: or the LPA.
For recently installed SVCs, if the number (nn) is X'C8' thru b. Ensure that the system has been reIPLed after the
X'FF', it is an installation defined SVC. If the SVC number is linkedit of the SVC routine to the modified LPA.
X'00' thru X'C7', and you continue to have a problem after fol- See OS/390 MVS Initialization and Tuning Refer-
lowing the next steps, contact the IBM Support Center. ence for information about the CLPA and MLPA
1. Correct the error as follows: system parameters.
2. Run the job step again.
System Completion Codes SCC-225
SCC-226 OS/390 V2R8.0 MVS System Codes
002 005
Wait State Codes
9. Enter IOPD option A3 to determine the failing path to the device.
002
The last past used mask (LPUM) field contains the identifier for
Explanation: During initial program load (IPL), an I/O operation the failing path to the device.
was not initiated; the subchannel status word (SCSW) was stored,
10. Use the service language commands to vary all but one path to
and the channel was not busy.
the IPL volume offline.
Source: Input/output supervisor (IOS)
11. ReIPL the system.
Operator Response: This is probably a hardware error. ReIPL the
12. If the problem recurs, contact hardware support.
system. If the problem recurs, contact hardware support.
005
003
Explanation: An I/O interruption during initial program load (IPL)
Explanation: Initial program load (IPL) cannot continue processing
indicated a unit check.
because the subchannel for one of the following devices is not
operational: A sense operation was unable to determine the cause of the unit
check, but the unit check was not caused by one of the following:
The IPL device.
No record found
The IODF device, as specified in the first four characters of the
File mask violation
LOAD parameter.
End of cylinder
Note: If you did not specify an IODF device in the LOAD param- Track condition check
eter, this wait state is due to a problem with the subchannel
Source: Initial program load (IPL)/nucleus initialization program (NIP)
for the IPL device.
System Action: The system enters a non-restartable wait state.
Source: Initial program load (IPL)
Operator Response: This problem can indicate either that:
System Action: The system enters a non-restartable wait state.
The system programmer either modified the IPL text or the IODF
Operator Response: Do one of the following:
data set (if defined).
Make sure the IPL device and the IODF device are enabled and The system detected a hardware error on the SYSRES device
reIPL the system. or the device containing the IODF data set (if defined).
IPL from a different device, or IPL using a different IODF device. If a system programmer modified the IPL text or the IODF data set,
Contact hardware support. notify the system programmer. Otherwise, make sure the IPL pack is
ready, and reIPL the system.
004 If the problem occurs, do the following to find the device address of
the device that received the unit check:
Explanation: During system initialization, the system did not initiate
an I/O operation. The channel was not busy after the system tried to 1. Using the hardware ALTER/DISPLAY facility, read the 4-byte
store control and status information for the subchannel. address in central storage at X'B8'. The last 2 bytes, X'BA'
and X'BB', contain the subchannel number.
Source: Input/output supervisor (IOS)
2. Invoke the I/O problem determination (IOPD) frame by either:
System Action: The system enters wait state X'004'. The system
does not store the subchannel status word (SCSW). Entering:
Operator Response: Do the following: F IOPD
1. At the system console, enter the F ALTCP command to invoke Selecting 08 on the INDEX0 frame.
the ALTER/DISPLAY frame. When frame IOPD-00 is displayed, select A5 for device con-
2. When the system displays the ALTCP frame, enter the number figuration.
of a processor that is not in a disabled wait state. 3. Enter the 2 byte subchannel number found in step 1 to bring up
3. Enter A2 B2 to display central storage. frame IOPD-50, the Device Configuration Display. This frame
contains, for the selected subchannel number, the device
4. Enter B8 at the following prompt: number, unit address, and the installed channel paths.
Address(hex) = >
4. Determine the failing path to the device using the IOPD option
5. Record the first 4 bytes of data at storage location X'B8'. The A3. Observe the last path used mask (LPUM) field to determine
last 2 bytes contain the subchannel number. the last path used.
6. Enter F IOPD to invoke the I/O problem determination (IOPD) 5. Use the service language commands to vary offline all but one
frame. path to the IPL volume. Include the supposedly failing path.
7. Select device configuration (A5) on the IOPD frame to determine 6. ReIPL the system.
the device number.
7. If the problem recurs, remove the device from the configuration.
8. Enter the subchannel number found in the last 2 bytes at Then reIPL the system.
storage location X'B8'.
If the problem persists, contact hardware support.
The system displays the device configuration. This frame con-
tains the device number, unit address, and all installed channel
paths.
Copyright IBM Corp. 1988, 1999 WSC-1
006 00D
System Programmer Response: If the IPL text or the IODF data
007
set was modified, look for a problem in the modified text or data set
and fix it. Explanation: During system initialization, a console was not avail-
able to the system.
006 Source: Communications task (COMMTASK)
Explanation: During initial program load (IPL), an I/O error Operator Response: Check to see if the console is available. If so,
occurred while IPL was reading from the SYSRES or IODF device. reIPL. If not, contact the system programmer.
The error can be one or more of the following:
System Programmer Response: Check the Console Report, con-
An interface control check tained in the HCD Operating System report (OS), to verify that at
A channel control check least one nucleus initialization program (NIP) console is configured.
A channel data check HCD builds the OS report based on the IODF configuration data. Do
A program check the following:
A channel chaining check
See OS/390 HCD User's Guide for information regarding IODF.
STATE CHANGE INTERRUPT detected due to SETCACHE
SUBSYS OFF issued on sharing system. Obtain a stand-alone dump.
Note: One commonly seen cause for this problem is having the Search problem reporting databases for a fix to the problem. If
nucleus in secondary extents. no fix exists, contact the IBM Support Center.
Source: Initial program load (IPL)
00A
System Action: The system enters a non-restartable wait state.
Explanation: The catalog entry for the SYS1.LINKLIB or
Operator Response: Do the following: SYS1.CSSLIB data sets could not be found on, or could not be
1. At the system console, invoke the I/O problem determination retrieved from the system catalog. This wait state is preceded by
(IOPD) frame by entering: message IEA326I.
F IOPD Source: Initial program load (IPL)
2. When frame IOPD-00 is displayed, select A5 for device config- System Action: The system issues message IEA326I before
uration. entering a non-restartable wait state.
3. Enter the device number. The failure is associated with either Operator Response: Notify the system programmer.
the system residence device or the IODF device. Both are valid
System Programmer Response: Ensure that SYS1.LINKLIB or
options.
SYS1.CSSLIB is in the catalog, and restart the system.
Note the installed channel paths to the device.
If the problem persists, search problem reporting databases for a fix
4. At the service console, display the channel error log index frame for the problem. If no fix exists, contact the IBM Support Center.
by entering:
F CHERLG 00B
5. This frame displays a log of the channel error logs. Look to see Explanation: During system initialization, the master scheduler
if this panel shows an entry for one of the channel path identi- ended abnormally.
fiers (CHPID) to the system residence or IODF device at the
Source: Master scheduler
time this wait state occurred. If so, enter the following command
at the system console to remove the failing channel path: System Action: The system ends system initialization. The system
writes a dump. The system enters wait state X'00B'.
CHPID cc OFF
Operator Response: Do the following:
Try reIPLing without the failing CHPID.
Try to reIPL the system. If unsuccessful, contact the system pro-
If the problem recurs, notify the system programmer.
grammer.
If the system programmer requests, obtain a stand-alone dump.
Obtain the dump written by the system.
For a 9221, do the following:
If the system programmer asks for a stand-alone dump, obtain
1. From the Monitor the System panel, select Analyze from the one.
action bar.
System Programmer Response: Search problem reporting data-
2. Select Use Problem Analysis from the pull-down menu. bases for a fix for the problem. If no fix exists, obtain the dump. If no
3. A PA panel is displayed, showing channels with IFCCs. Select dump exists, ask the operator to obtain a stand-alone dump. Contact
Channel (CHPID); then select Next. the IBM Support Center. Provide the dump.
4. Another PA panel is displaying, showing time and date that the
IFCCs occurred. Select error, then select Next. 00D
5. A summary of the error is displayed. Explanation: During system initialization, the master scheduler
ended abnormally.
System Programmer Response: Search problem reporting data-
bases for a fix for the problem. If no fix exists, contact the IBM Source: Master scheduler
Support Center. Provide the stand-alone dump. System Action: The system ends system initialization. The system
enters wait state X'00D'.
Operator Response: Try to reIPL the system. If unsuccessful,
contact the system programmer. If the system programmer asks for
a stand-alone dump, obtain one.
WSC-2 OS/390 V2R8.0 MVS System Codes
00E 017
System Programmer Response: Search problem reporting data-
014
bases for a fix for the problem. If no fix exists, ask the operator to
obtain a stand-alone dump. Contact the IBM Support Center. Provide Explanation: The system encountered recursive program checks.
the stand-alone dump. Usually, this is the result of an overlay of a critical system control
block, such as PSA, ASCB, SGTE, or PGTE.
00E Source: Supervisor control
Explanation: Initial program load (IPL) cannot locate the System Action: The system enters a non-restartable wait state.
SYS1.NUCLEUS data set or the system nucleus member of the
Operator Response: If the system programmer requests a stand-
SYS1.NUCLEUS data set on the system residence volume. The
alone dump, obtain one. Re-IPL the system.
nucleus member is one of the following:
System Programmer Response: Do the following:
IEANUC01, which is DAT-on nucleus IEANUC01
1. Ask the operator to obtain a stand-alone dump.
IEANUC0x, which is an alternate DAT-on nucleus where x is not
1 2. Determine the control block that has been overlaid and the
module that did the overlay. In many cases, the last program to
IEAVEDAT, which is the DAT-off nucleus
be dispatched on that processor caused the overlay. The last
DAT is the acronym for dynamic address translation. program dispatched can be determined from the system trace
Source: Initial program load (IPL) table.
System Action: The system enters a non-restartable wait state. 3. Search problem reporting databases for a fix for the problem. If
no fix exists, contact the IBM Support Center. Because of the
Operator Response: If you selected an alternate DAT-on nucleus possibility that a hardware malfunction contributed to this
member, make sure that the alternate nucleus identifier (x of problem, you should also contact hardware support. Provide to
IEANUC0x) was correctly entered through the console frame, or at the IBM Support Center and to hardware support the stand-
absolute storage location X'F'. Then reIPL the system. alone dump.
If the error persists, notify the system programmer. Obtain a stand-
alone dump if requested by the system programmer. 017
System Programmer Response: Make sure that the Explanation: During initial program load (IPL), a unit check
SYS1.NUCLEUS data set resides on the system residence volume occurred after an I/O operation was successfully started. The I/O
and that it contains the members you want to load. operation was:
If the problem persists, search problem reporting databases for a fix A sense I/O
for the problem. If no fix exists, contact the IBM Support Center.
An attempt to read the home address and record 0 of a track
Provide the stand-alone dump and the name of the SYS1.NUCLEUS
that previously caused a track condition check
member that the IPL program could not find.
The 4-byte address of the subchannel identifier can be found in
00F central storage at decimal address 186 (X'BA').
Explanation: For initial program load (IPL), a volume has been Source: Initial program load (IPL)
loaded that does not contain IPL text. System Action: The system enters a non-restartable wait state.
Operator Response: Correctly identify the correct volume to be | Operator Response: You need to determine whether a device or a
loaded. Verify that the correct volume is mounted. If requested by | path to the device caused the problem. The most likely path is the
the system programmer, obtain a stand-alone dump. ReIPL the | last path used to access the device. Take the following steps:
system.
| 1. Using the hardware Alter / Display CP facility, read the 4-byte
System Programmer Response: If the problem cannot be | subchannel address in central storage at X'BA'. The sub-
resolved, search problem reporting databases for a fix for the | channel number is the last two bytes (at location X'BA') of the
problem. If no fix exists, ask the operator to obtain a stand-alone | 4-byte subchannel identification word at location X'B8'.
dump. Contact the IBM Support Center. Provide the stand-alone
| 2. Bring up the Device Configuration Display. Enter the 2-byte sub-
dump.
| channel number found in step 1. This displays, for the selected
| subchannel number, the device number, unit address, and the
013 | installed channel paths.
Explanation: During processing of the nucleus initialization | If there is only one channel path to the device, there is no need
program (NIP), an error occurred from which recovery is impossible. | for the system operator to continue problem determination.
Check the system completion code to determine the problem. | Contact hardware support.
Operator Response: If requested by the system programmer, 3. Bring up the Subchannel Status display. It is likely that the last
obtain a stand-alone dump. ReIPL the system. path used is the failing path. Read the last path used mask
System Programmer Response: If the problem cannot be (LPUM) field to determine the last path used. The LPUM field
resolved, search problem reporting databases for a fix for the consists of 8 bits. If, for example, the second bit is turned on
problem. If no fix exists, ask the operator to obtain a stand-alone (B'01000000'), CHPID1 is the last path used.
dump. contact the IBM Support Center. Provide the stand-alone 4. Use service language commands to configure offline the last
dump. path used. For example:
chpid address off
5. ReIPL the system.
Wait State Codes WSC-3
019 020
6. If the problem does not recur, you have identified the failing ssssssss A pointer to the system diagnostic work area
path. (SDWA).
| If the problem recurs, and there are other paths to the device, llllllll A pointer to control registers 3 and 4.
| configure the other paths offline one by one, until you have iden-
zzzzzzzz A pointer to the access registers.
| tified the failing path. If this does not identify a failing path, the
| problem is caused either by the remaining online path or by the wwwwwwww A pointer to the RTM2 work entry.
| device. Contact hardware support. aaaaaaaa A pointer to the address space control block
(ASCB).
019 iiiiiiii A pointer to the PER interrupt code.
Explanation: During initial program load (IPL), an unexpected Source: Recovery termination manager (RTM)
program interruption occurred. IPL did not complete loading the resi-
dent nucleus. If this wait state occurred because the IPL program is System Action: The system issues message IEA992I before the
in error, a stand alone dump should be taken so that the cause of system enters the restartable, disabled wait state.
the program error can be diagnosed. Operator Response: Follow the directions of the system pro-
The problem is one of the following: grammer for the SLIP trap. Then restart the system by invoking the
restart function.
The operator pressed START during system initialization.
The IPL program is in error.
01C
The storage in which IPL resides is failing.
The IODF being used for IPL may be empty. Explanation: Supervisor control experienced a recursive abnormal
end in its super functional recovery routine (FRR). This is probably a
Source: Initial program load (IPL)
software error.
System Action: The system enters a non-restartable wait state.
A hexadecimal reason code in bits 33 through 51 of the PSW
Operator Response: Do one of the following: explains the error:
If this wait state occurred because an operator pressed the Code Explanation
START key during system initialization, let the IPL continue. It is
00 Supervisor control experienced a double recursive
not necessary to reIPL; the system will start the waiting
abend.
processors automatically.
04 Supervisor control experienced a recursive abend during
Make sure the SYS1.NUCLEUS data set does not have sec-
list transition processing.
ondary extents. If there are no secondary extents, the error is
probably the result of a hardware problem. Contact hardware Source: Supervisor control
support. When the problem has been corrected, reIPL the
System Action: The system may issue message IEA967W. The
system.
system writes a logrec error record.
Ensure that the IPL text program installed is at the correct level
Operator Response: If the system programmer requests a stand-
for the operating system. If not, reinstall IPLTEXT as described
alone dump, obtain one. ReIPL the system.
in the MVS program directory.
System Programmer Response: Search problem reporting data-
bases for a fix for the problem. If no fix exists, ask the operator to
01B
obtain a stand-alone dump. Contact the IBM Support Center. Provide
Explanation: An active SLIP trap requests an action of WAIT. The the stand-alone dump and, if available, the logrec error record.
conditions specified on the SLIP command have been met. The
system enters a wait state, as requested.
020
PSAWTCOD in the prefixed storage area (PSA) points to a 16-byte
Explanation: Reconfiguration initialization failed. The wait state
field. When the field begins as follows, it means:
reason code specifies the error.
Entry Explanation
The content of the right half of the program status word (PSW) is:
01ccccxxrrrrrrrrppppppppssssssssllllllllzzzzzzzz Recovery termination
xrrrrcde
manager 1 (RTM1) functional recovery routine (FRR)
type of entry. This half of the PSW describes the following:
02ccccxxrrrrrrrrppppppppwwwwwwwwllllllllzzzzzzzz RTM2 ESTAE x Irrelevant information.
type of entry (RTM2WA). rrrr Reason code indicating reason for the failure.
03ccccxxrrrrrrrrppppppppaaaaaaaallllllllzzzzzzzz Address space The possible values of rrrr are:
ending type of entry.
0010 The service processor could
04ccccxxrrrrrrrrppppppppiiiiiiiillllllllzzzzzzzz Program event recording not provide channel path
(PER) interrupt type of entry. information to reconfigura-
The variable information in the field is as follows: tion. This is a hardware
problem.
cccc A pointer to the logical CPU id of the processor
where the event was detected. 0030 The service processor could
not provide side information
xx Irrelevant information.
to reconfiguration. This is a
rrrrrrrr A pointer to the general registers. hardware problem.
pppppppp A pointer to the program status word (PSW).
WSC-4 OS/390 V2R8.0 MVS System Codes
022 02E
0040 Reconfiguration failed to
025
determine the amount of
storage needed for side Explanation: The system detected a duplicate entry point name
information. appearing in modules being loaded into the DAT-on nucleus. (DAT is
the acronym for dynamic address translation.)
cde The wait state code.
Source: Initial program load (IPL)
Source: Reconfiguration
System Action: The system issues message IEA087W to identify
System Action: The system ends the initialization. The system
the entry point names and the modules in which the entry points
enters nonrestartable wait state X'020'.
appear. IEA087W appears one or more times in the IPL WTO buffer.
Operator Response: For reason code X'0010' or X'0030', obtain
The system enters a non-restartable wait state.
a stand-alone dump. Contact hardware support, providing the
recorded contents of the wait state PSW. Check the processor con- Operator Response: Do the following as soon as possible to find
troller. Try to do a switch-over or reIPL. If this does not work, parti- the WTO buffer and locate message IEA087W in the buffer. Do not
tion the machine and use the side with a good service processor. write a stand-alone dump before doing this procedure, because the
dump might overlay storage.
For reason code X'0040', contact the system programmer.
1. Using the hardware ALTER/DISPLAY facility, read the real
System Programmer Response: For reason code X'0040',
address in central storage at X'14'. This address points to the
search problem reporting databases for a fix for the problem. If no fix
IPL diagnostic area.
exists, contact the IBM Support Center. Ask the operator to obtain
the stand-alone dump and provide it to IBM. 2. Add X'28' to the address at real X'14', and also read this as a
real address in central storage. The result is the 31-bit virtual
022 address of the IPL vector table (IVT).
Explanation: A page fault occurred for a page with a primary and 3. Add X'E0' to the IVT address. The result is the 31-bit address
secondary copy. The primary and secondary devices are in one of of the IVTMQHP field. IVTMQHP contains the address of the
the following states: message queue header (MQH).
Quiesced 4. MQH+X'0' contains the address of the oldest message queue
Not ready element (MQE) available. The message text for the oldest MQE
begins at MQE+X'8'.
The error occurred in a system facility invoked by direct access
volume verification (DAVV). 5. Use MQE+X'0' of the oldest MQE to find the MQE of the next
oldest message. Again, the message text for this MQE begins at
Source: Input/output supervisor (IOS) MQE+ X'8'.
Operator Response: Do the following: 6. Repeat this sequence (using MQE+X'0' of the current MQE to
Display the contents of register 7 to see if the correct volume is locate the next MQE), until the message text for the appropriate
mounted. Register 7 contains the address of the unit control message is displayed.
block (UCB) that contains the following: Notify the system programmer, providing the texts of IEA087W mes-
– The device address sages. If the system programmer requests it, obtain a stand-alone
dump.
– The volume serial number of the volume that should be
mounted System Programmer Response: Translate the text of IEA087W
messages from hexadecimal into EBCDIC.
ATTENTION: If you do not mount the correct volume before
restarting the system, some system data may be lost. If a NUCLSTxx member is being used (the LOADxx member has a
NUCLST statement which refers to a NUCLSTxx member), and the
ReIPL the system.
NUCLST member includes one or both of the modules in the
message text, the problem may be that the module being included
023 has entry points in common with a module that is already included. If
Explanation: During the creation of the system trace address this is the case, the NUCLST member must be changed, or the entry
space or during the initialization of the system trace function, the point(s) in the module being included must be changed to have dif-
system detected an error. System trace returned a nonzero return ferent entry point names.
code. If either module in the message text is supplied by the installation,
Source: System trace change the entry point name.
System Action: The system abnormally ends the system trace If one of the modules is IEANUC0x, look in the link-edit map to find
initialization with a nonrestartable wait state. The system writes which CSECT contains the duplicate CSECT name.
message IEA416W. If IBM supplies both modules, contact the IBM Support Center.
Operator Response: Notify the system programmer. Provide a stand-alone dump and the IEA087W message text.
System Programmer Response: Search problem reporting data-
bases for a fix for the problem. If no fix exists, contact the IBM 02E
Support Center. Explanation: The auxiliary storage manager (ASM) is unable to
function because of recovery problems or an unusual number of per-
manent I/O errors on one or more necessary page data sets. The
accompanying reason code further describes the error:
Code Explanation
00 The cause of the error cannot be determined.
Wait State Codes WSC-5
030 032
01 Duplexing is not active, and the PLPA data set is now Source: Input/output supervisor (IOS)
bad.
System Action: The system enters wait state X'031'.
02 Duplexing is not active, and the common data set is now
Operator Response: Depending on the reason that this wait state
bad.
code was issued, do the following:
03 The duplex data set is now bad, and both the PLPA and
If the system was IPLed using the wrong SYSRES device, then
common data sets are not available.
mount the correct SYSRES device and reIPL the system.
04 Both the duplex and PLPA data sets are now bad.
If the SYSRES device was not specified in the I/O configuration
05 Both the duplex and common data sets are now bad. definition, then notify the system programmer to rebuild the I/O
configuration to include the correct SYSRES device.
06 The last local page data set is now bad.
If the system did not select the desired I/O configuration, use the
Source: Auxiliary storage manager (ASM)
following steps to determine which I/O configuration was
System Action: System processing ends. The system issued selected; then notify the system programmer:
message ILR008W prior to the wait state. The system may have
1. Using the hardware ALTER/DISPLAY facility, read the real
issued messages ILR007I, ILR009E, and ILR010I previously; these
address in central storage at X'14', representing the
messages indicate what conditions led to the wait state.
address of the IPL diagnostic area.
Operator Response: Report this wait state to the system pro-
2. Add X'28' to the address in X'14', and also read this as a
grammer. Provide the system programmer with the system mes-
real address in central storage. The result is a 31-bit virtual
sages for problem analysis.
address, which is the IPL vector table (IVT). Note that the
If necessary, at the IPL, replace the page data sets referenced in the following addresses are also 31-bit virtual addresses.
preceding messages or add more page data sets. Then IPL the
3. Add X'E0' to the address of IVT to locate the IVTMQHP
system.
field, which points to the message queue header (MQH).
System Programmer Response: Analyze the messages provided
4. MQH + X'0' points to the oldest message queue element
by the operator to determine the cause of the I/O error. Look at any
(MQE) available. Message text beings at MQH + X'8'. This
I/O, machine check, missing interrupt handler, or disabled console
message should be IEA371I, showing the device number
communication messages that occurred prior to the wait. Determine
and data set (SYS1.PARMLIB or SYS1.IPLPARM) used to
which page data sets are no longer usable. Correct or replace these
located the selected LOADxx member.
data sets.
5. MQE + X'0' of the oldest MQE points to the second oldest
030 MQE. This message should be IEA246I, showing which
LOADxx member was selected.
Explanation: The system abended a task during nucleus initializa-
tion program (NIP) processing. The hexadecimal abend code rrr 6. MQE + X'0' of the oldest MQE points to the third oldest
appears in one of the following formats of the wait state program MQE. This message should be either IEA097I, showing
status word (PSW): which MVSCP IOCONFIG was selected, or IEA519I,
showing which IODF was selected.
ðððAðððð 8ðrr rwww
ðððAðððð ðrrr ðwww System Programmer Response: If the SYSRES device was not
specified in the I/O configuration definition, then rebuild the I/O con-
Source: Nucleus initialization program (NIP)
figuration to include the correct SYSRES device.
System Action: The system abends the task and enters a non-
If the system did not select the desired I/O configuration, then ensure
restartable wait state.
that the device number, data set (SYS1.PARMLIB or
Operator Response: Record the wait state PSW and notify the SYS1.IPLPARM), LOADxx member, and I/O configuration were
system programmer. If the system programmer requests it, obtain a selected.
stand-alone dump.
System Programmer Response: See the system programmer 032
response for the abend code. Explanation: A module required for nucleus initialization (NIP) is
The abend SVC entry in the system's SVC table contains the missing from the SYS1.NUCLEUS data set.
address of a trap routine in NIP and not the address of the abend The reason code identifies the missing module. You can determine
SVC. The registers at the time of the abend SVC request are found the name of the missing module by appending the last 2-digits of the
in the Type I SVC save area. reason code after IEAVNP. For example, if the reason code is 003,
If the problem persists, search problem reporting databases for a fix the missing module is IEAVNP03.
for the problem. If no fix exists, contact the IBM support Center. Exceptions are 7D4, 7E1, and 7E7, as follows:
Provide the contents of the wait state PSW.
Reason Module in Component
Code SYS1.NUCLEUS
031 (hex)
Explanation: The system did not find a unit control block for the 7D4 IEAVNIPM NIP
7E1 IEAVNPX1 NIP
device containing the system residence (SYSRES) volume, for one 7E7 IEAVNIPX NIP
of the following reasons:
The system was IPLed using the wrong SYSRES device The reason code rrr can appear in the wait state program status
word (PSW) in one of the following formats:
The SYSRES device was not specified in the I/O configuration
definition ðððAðððð 8ðrr rwww
ðððAðððð ðrrr ðwww
The system did not select the desired I/O configuration.
WSC-6 OS/390 V2R8.0 MVS System Codes
033 038
Source: Nucleus initialization program (NIP) 5. Use MQE+X'0' of the oldest MQE to find the MQE of the next
oldest message. Again, the message text for this MQE begins at
System Action: The system enters a non-restartable wait state.
MQE+ X'8'.
Operator Response: Record the contents of the wait state PSW
6. Repeat this sequence (using MQE+X'0' of the current MQE to
and notify the system programmer. If the system programmer
locate the next MQE), until the message text for the appropriate
requests it, obtain a stand-alone dump.
message is displayed.
System Programmer Response: If no modules are missing from
Notify the system programmer, providing the texts of the IEA084W
the data set, search problem reporting databases for a fix for the
messages. If the system programmer requests it, obtain a stand-
problem. If no fix exists, contact the IBM Support Center. Provide the
alone dump. Then reIPL the system, using a different nucleus
stand-alone dump.
member, if possible.
033 System Programmer Response: Do the following:
Explanation: An I/O error occurred in build link-list request (BLDL 1. Look in the stand-alone dump for message IEA084W. Note the
macro) processing for a required nucleus initialization program (NIP) entry point given in the message text.
module. 2. Use the IEHLIST program to print the SYS1.NUCLEUS direc-
tory.
The reason code rrridentifies the missing module. The reason code 3. Search problem reporting databases for a fix for the problem. If
can appear in the wait state program status word (PSW) in one of no fix exists, call the IBM Support Center. Provide the stand-
the following formats: alone dump and the SYS1.NUCLEUS directory listing.
ðððAðððð 8ðrr rwww
ðððAðððð ðrrr ðwww 037
See the explanation for wait state X'032' to identify the NIP module. Explanation: The data space control block (DSCB) for logrec,
Source: Nucleus initialization program (NIP) SYS1.SVCLIB, SYS1.PARMLIB, or SYS1.LINKLIB could not be suc-
cessfully read from the volume where the data set resides for one of
System Action: The system enters a non-restartable wait state.
the following reasons:
Operator Response: This is probably a hardware error. ReIPL the
The data set does not exist on this volume.
system. If the error persists, contact hardware support. Provide the
number of the IPL device where the I/O error occurred and the con- An unrecoverable input/output (I/O) error occurred during the
tents of the wait state PSW. attempt to read the related data space control block (DSCB).
An error occurred during nucleus initialization program (NIP)
035 OPEN processing.
Explanation: During system initialization, the system could not find Register 1 contains a pointer to the input/output buffer (IOB) for the
an entry point in the nucleus. The system loaded one of the failing I/O operation (EXCP). Diagnostic messages explaining the
following: reason for the wait state and identifying the name of the data set
An incomplete nucleus involved precede the system wait.
An incomplete I/O configuration Source: Logrec
Both an incomplete nucleus and an incomplete I/O configuration Operator Response: Report this wait state code and the diagnostic
messages that precede it to the system programmer.
Source: Input/output supervisor (IOS)
System Programmer Response: If any IGGNxxx messages are
System Action: The system enters wait state X'035'. The system issued with this wait state code, perform the system programmer
places message IEA084W in the initial program load (IPL) write to response for those messages. Otherwise, ensure that the data set is
operator (WTO) buffer. not cataloged with an esoteric device name. Correct the error that
Operator Response: Do the following as soon as possible to find caused the DSCB read I/O operation. Ask the operator to reIPL the
the WTO buffer and locate message IEA084W in the buffer. Do not system.
write a stand-alone dump before doing this procedure, since the If the error recurs and the program is not in error, search problem
dump might overlay storage. reporting databases for a fix for the problem. If no fix exists, contact
1. Using the hardware ALTER/DISPLAY facility, read the real the IBM Support Center.
address in central storage at X'14'. This address points to the
IPL diagnostic area. 038
2. Add X'28' to the address at real X'14', and also read this as a Explanation: The operating system cannot initialize itself because
real address in central storage. The result is the 31-bit virtual there is not enough central storage. One of the following is true:
address of the IPL vector table (IVT).
There are not enough usable online frames
3. Add X' E0' to the IVT address. The result is the 31-bit address There are not enough usable contiguous frames
of the IVTMQHP field. IVTMQHP contains the address of the
Source: Auxiliary storage manager (ASM) and initial program load
message queue header (MQH).
(IPL)
4. MQH+X'0' contains the address of the oldest message queue
Operator Response: Notify the system programmer.
element (MQE) available. The message text for the oldest MQE
begins at MQE+X'8'. System Programmer Response: Ensure that there is enough
central storage available for IPL processing. You may have to reduce
the number of optional system facilities selected for this system con-
figuration. Then ask the operator to IPL the system.
Wait State Codes WSC-7
039 03D
the IBM Support Center. Provide the contents of the wait PSW avail-
039
able.
Explanation: The system could not mount a direct access volume
because the mount request conflicted with another volume. One of 03C
the following occurred:
Explanation: The auxiliary storage manager (ASM) found that not
Both volumes were required by the system. enough auxiliary storage space is available for system operation:
Both volumes had the same volume serial.
During IPL
The volume to be mounted required a different device type than Either the needed number of page data sets was not specified
that containing the online volume. or ASM has detected a problem with a required page data set.
The system could not find a proper device on which to mount After IPL
the volume. ASM has run out of usable auxiliary storage for the pageable
Source: Input/output supervisor (IOS) link pack area (PLPA), common, or local page data sets. Either
all the local page data sets were full or damaged, or the PLPA,
System Action: The system enters wait state X'039'.
common, or duplex data set was full or damaged.
System Programmer Response: If any IGGNxxx messages are
issued with this wait state code, perform the system programmer A reason code identifies the error:
response for these messages. Otherwise, change the volume where Code Explanation
one of the two data sets resides. Update the catalogue to contain
00 The cause of the error cannot be determined because of
the volume of the moved data set.
an error in recovery processing.
03A 01 The last local page is full, so there is insufficient local
paging space.
Explanation: An error occurred during an attempt to build the link
pack area (LPA) during a cold start. 02 The PLPA data set is full, duplexing is not active, and
the common data set is unavailable.
Source: Contents supervision (CSV)
03 The common data set is full, duplexing is not active, and
System Action: The system issues message IEA304W to identify the PLPA data set is unavailable.
the error. The system may also issue message IEA353I and/or
IEA354I. 04 The duplex data set is full, and both the PLPA and
common data sets are unavailable.
Operator Response: Report this wait state code and the preceding
diagnostic messages to the system programmer. Source: Auxiliary storage manager (ASM)
If requested by the system programmer, obtain a stand-alone dump. System Action: During IPL, the system issues message IEA935W,
then enters this wait state. After IPL, the system issues message
System Programmer Response: See the programmer response ILR008W, then enters this wait state, unless all the local page data
for message IEA304A. Correct the conditions that caused the LPA sets were unusable; in that case, the system does not issue a
cold start to fail. Ask the operator to reIPL the system. message before entering this wait state.
If the error recurs and the program is not in error, search problem Operator Response: Notify the system programmer. ReIPL the
reporting databases for a fix for the problem. If no fix exists, contact system, specifying larger page data sets or additional page data
the IBM Support Center. Provide the stand-alone dump. sets.
System Programmer Response: Do one of the following:
03B
Redefine spaces to conform with the description provided in
Explanation: A module required for continued system operation paging planning specifications. Ask the operator to reIPL with
cannot be found in the system link pack area (LPA). the CLPA option.
Source: Contents supervision (CSV) Provide additional paging spaces and make them available
through either the PAGE parameter or the IEASYSxx parmlib
System Action: The system may issue message IEA363I to indi-
member during reIPL.
cate which module could not be found. The system enters a non-
restartable wait state.
03D
Operator Response: Report this wait state code to the system pro-
grammer and save the console listing. Explanation: When the nucleus initialization program was running,
an error occurred while the system was building common area page
System Programmer Response: Examine the console listing and
tables. There may not be enough central storage available to ini-
look for message IEA363I to determine the name of the missing
tialize the system.
module. Execute the IEHLIST utility program to obtain a directory
listing of the SYS1.LPALIB data set. Examine this list to determine Source: Virtual storage management (VSM)
which required system modules are missing. The missing modules System Action: The system may issue message IEA907W. The
should then be copied into SYS1.LPALIB from the starter system system enters wait state X'03D'.
libraries or from a similar back-up source. Ask the operator to reIPL
the system and add the missing module to the LPA either by Operator Response: Notify the system programmer.
requesting an LPA cold start or by using the MLPA or FIX options. System Programmer Response: Increase the amount of available
If the problem recurs and the program is correct, search problem central storage.
reporting databases for a fix for the problem. If no fix exists, contact
WSC-8 OS/390 V2R8.0 MVS System Codes
03E 050
Operator Response: This is probably a hardware error. ReIPL the
03E
system. If the error persists, configure the failing central processor
Explanation: The auxiliary storage manager (ASM) determined that offline. This action requires a power-on-reset. Contact hardware
there were not enough slots to back master scheduler initialization. support.
Source: Auxiliary storage manager (ASM)
045
System Action: The system ends IPL.
Explanation: While initializing the recovery termination manager
Operator Response: Notify the system programmer. ReIPL the
(RTM), the nucleus initialization program (NIP) requested cell pool
system, specifying larger page data sets or additional page data
storage in the system queue area (SQA). The request failed. System
sets, as indicated by the system programmer.
initialization cannot continue.
System Programmer Response: Increase the amount of auxiliary
Source: Recovery termination manager (RTM)
storage for system operation.
System Action: The system may issue message IEA897I.
03F Operator Response: If requested by the system programmer,
Explanation: A program invoked a nucleus initialization program obtain a stand-alone dump. Then try again to IPL the system.
(NIP) function incorrectly. System Programmer Response: Search problem reporting data-
Source: Nucleus initialization program (NIP) bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Provide the stand-alone dump.
System Action: The system enters a non-restartable wait state.
Operator Response: If the system programmer requests it, obtain 046
a stand-alone dump.
Explanation: During nucleus initialization program (NIP) proc-
System Programmer Response: If the problem recurs or if the essing, an unexpected program check occurred.
program is correct, search problem reporting databases for a fix for
Source: Nucleus initialization program (NIP)
the problem. If no fix exists, contact the IBM Support Center. Provide
the stand-alone dump. System Action: The system enters a non-restartable wait state.
Operator Response: Notify the system programmer. If the system
040 programmer requests it, obtain a stand-alone dump.
Explanation: The system abended a task during nucleus initializa- System Programmer Response: Search problem reporting data-
tion program (NIP) processing. The hexadecimal abend code can be bases for a fix for the problem. If no fix exists, contact the IBM
found in bits 33 through 51 of the wait state program status word Support Center. Provide the stand-alone dump.
(PSW).
Source: Nucleus initialization program (NIP) 04A
System Action: The system issues message IEA303W. The Explanation: A time-of-day (TOD) clock on one of the central
system enters a non-restartable wait state. processors is in error. The clock must be set to avoid generating a
machine check later in nucleus initialization program (NIP) proc-
Operator Response: Record the wait state PSW and report the
essing.
problem to the system programmer. If the system programmer
requests it, obtain a stand-alone dump. Source: Nucleus initialization program (NIP)
System Programmer Response: See the system programmer System Action: Every central processor with a clock that needs
response for the abend code displayed in message IEA303W. setting will enter restartable wait state X'04A'.
The abend SVC entry in the system's SVC table contains the Operator Response: Perform restart function, then press the TOD
address of a trap routine in NIP, and not the address of the abend ENABLE and ALT keys at the system console to set the clock. IPL
SVC. The registers at the time of the abend SVC request are found will continue.
in the service request block (SVRB) for the abend SVC.
If the problem persists, search problem reporting databases for a fix 050
for the problem. If no fix exists, contact the IBM support Center. Pro- Explanation: The system determined that alternate CPU recovery
viding the contents of the wait state PSW. (ACR) was recursively invoked.
Source: Loadwait/Restart
044
System Action: The system issues message BLW007W. Then the
Explanation: During nucleus initialization program (NIP) proc- system enters disabled wait state X'050'.
essing, a machine check occurred on a central processor. The
logical address of the central processor on which the machine check Operator Response: Retain the SYS1.LOGREC error records.
occurred is in bits 40 through 47 of the wait state PSW. Take a stand-along dump and reIPL the system. Contact the system
programmer.
Source: Nucleus initialization program (NIP)
System Programmer Response: Search the problem reporting
System Action: The system issues messages about the problem. databases for a fix for the problem. If no fix exists, contact the IBM
The system enters a non-restartable wait state. Support Center. Provide the stand-alone dump and the
SYS1.LOGREC error records.
Wait State Codes WSC-9
051 055
051 054
Explanation: Alternate CPU recovery (ACR) encountered an unre- Explanation: The system detected an error with a member being
coverable error while recovery was in progress for another loaded into the dynamic address translation (DAT)-on nucleus region
processor. ACR attempted to recover but was unsuccessful. This is during system initialization.
probably a software error.
If bits 40 through 43 in the wait state program status word (PSW)
Source: Alternate CPU recovery (ACR) contain reason code X'1', the member being loaded contained more
than one control section (CSECT). The member was not link-edited
System Action: The system:
with the SCTR option.
Issues message IEA857W
Source: Initial program load (IPL)
Tries to write a logrec error record for the failed processor
System Action: The system issues message IEA089W to the IPL
Places all processors in a wait state X'051' WTO buffer to identifies the member. The system enters a non-
Operator Response: If requested by the system programmer, restartable wait state.
obtain a stand-alone dump. ReIPL the system. Operator Response: If the system programmer requests, do the
System Programmer Response: Look at accompanying message following to find the WTO buffer and locate message IEA089W:
IEA857W to identify the error. If a search of the program reporting 1. Using the hardware ALTER/DISPLAY facility, read the real
databases shows no existing fix, report the problem to the IBM address in central storage at X'14'. This address points to the
Support Center. Provide the stand-alone dump the logrec error IPL diagnostic area.
records.
2. Add X'28' to the address at real X'14', and also read this as a
real address in central storage. The result is the 31-bit virtual
052 address of the IPL vector table (IVT).
Explanation: Alternate CPU recovery (ACR) encountered an unre- 3. Add X' E0' to the IVT address. The result is the 31-bit address
coverable error while recovery was in progress for another of the IVTMQHP field. IVTMQHP contains the address of the
processor. This is probably a hardware error. message queue header (MQH).
Source: Alternate CPU recovery (ACR) 4. MQH+X'0' contains the address of the oldest message queue
System Action: The system: element (MQE) available. The message text for the oldest MQE
begins at MQE+X'8'.
Issues message IEA857W
5. Use MQE+X'0' of the oldest MQE to find the MQE of the next
Writes a logrec error record for the failed processor
oldest message. Again, the message text for this MQE begins at
Places all processors in a wait state X'052' MQE+ X'8'.
Operator Response: Look at accompanying message IEA857W 6. Repeat this sequence (using MQE+X'0' of the current MQE to
and the logrec error record to identify the error. locate the next MQE), until the message text for the appropriate
If message IEA857W indicates that this is a hardware error, remove message is displayed.
the failing hardware from the system, or remove the system with the If the system programmer requests it, obtain a stand-alone dump.
failure from the complex. Then reIPL the other systems. Contact
System Programmer Response: Link edit the nucleus again using
hardware support.
the SCTR option.
Otherwise, report the problem to system programmer.
If the problem recurs, have the operator retrieve message IEA089W
System Programmer Response: Search problem reporting data- from the WTO buffer. Translate the text of message IEA089W from
bases for a fix for the problem. If no fix exists, contact the IBM hexadecimal into EBCDIC. The translated message text will show
Support Center. Provide the logrec error record and the text of which module or member was in error.
message IEA857W.
If the member identified in message IEA089W belongs to IBM,
search problem reporting databases for a fix for the problem. If no fix
053 exists, contact the IBM Support Center. Provide a stand-alone dump.
Explanation: During system initialization, the system used up the
storage available in the system queue area (SQA). 055
Source: Initial program load (IPL) Explanation: The initial program load (IPL) program was unable to
System Action: The system enters a non-restartable wait state. locate a necessary member in the SYS1.NUCLEUS data set. Bits 40
through 43 in the program status word (PSW) contain one of the fol-
Operator Response: Notify the system programmer. lowing reason codes:
System Programmer Response: If the problem persists, search Code Explanation
problem reporting databases for a fix for the problem. If no fix exists,
contact the IBM Support Center. 1 IPL could not find a DAT-off nucleus module. (DAT is
the acronym for dynamic address translation.)
2 IPL could not find a DAT-on nucleus module.
4 IPL could not find one or more required module list
tables (MLT) in SYS1.NUCLEUS.
5 IPL could not find a module required for IPL processing.
This reason code indicates that MVS is not properly
installed.
Source: Initial program load (IPL)
WSC-10 OS/390 V2R8.0 MVS System Codes
056 05C
System Action: For reason codes X'1' through X'4', IPL writes If the UIM was not installation-provided, determine which product
one or more IEA086W messages in the IPL WTO buffer. The system contains the member and why the member was not installed in
enters a non-restartable wait state. SYS1.NUCLEUS.
Operator Response: For reason code X'1', if you selected an If the reason code is X'5' or if you cannot solve the problem, search
alternate I/O configuration, ensure that you correctly entered the problem reporting databases for a fix for the problem. If no fix exists,
alternate I/O configuration identifier (xx) through the console frame or contact the IBM Support Center. Provide the text of accompanying
at storage location 9-10. ReIPL the system. If the error persists, message IEA086W if issued.
notify the system programmer.
For reason code X'2', make sure that the load parameter fifth and 056
sixth digits are correct. Explanation: DFP encountered a terminating error during NIP
For reason code X'1', X'2', and X'4', do the following to find the initialization. See message IGW008D for further information.
WTO buffer and locate message IEA086W in the buffer: Source: DFSMSdfp
1. Using the hardware ALTER/DISPLAY facility, read the real System Action: System is in a disabled wait state without restart
address in central storage at X'14'. This address points to the capability.
IPL diagnostic area.
Operator Response: Report this wait state code to the system pro-
2. Add X'28' to the address in X'14', and also read this as a real grammer.
address in central storage. The result is the 31-bit virtual
address of the IPL vector table (IVT). Programmer Response: See message IGW008D for further infor-
mation.
3. Add X' E0' to the IVT address. The result is the 31-bit address
of the IVTMQHP field. IVTMQHP contains the address of the System Programmer Response: Provide software support per-
message queue header (MQH). sonnel with console listing and stand alone dump. Also include a
copy of message IGW010I in the console listing.
4. MQH+X'0' contains the address of the oldest message queue
element (MQE) available. The message text for the oldest MQE
059
begins at MQE+X'8'.
Explanation: During nucleus initialization program (NIP) proc-
5. Use MQE+X'0' of the oldest MQE to find the MQE of the next
essing, a build link-list request (BLDL macro) returned an undefined
oldest message. Again, the message text for this MQE begins at
return code. System initialization cannot continue.
MQE+ X'8'.
Source: Nucleus initialization program (NIP)
6. Repeat this sequence (using MQE+X'0' of the current MQE to
locate the next MQE), until the message text for the appropriate System Action: The system enters a non-restartable wait state.
message is displayed. Operator Response: Notify the system programmer. If the system
For all reason codes, notify the system programmer. For reason programmer requests it, obtain a stand-alone dump.
codes X'1' through X'4', provide the text of message IEA086W. If System Programmer Response: Search problem reporting data-
the system programmer requests it, obtain a stand-alone dump. bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: For reason codes X'1' through Support Center. Provide the stand-alone dump.
X'4', get the text of message IEA086W from the IPL WTO buffer
and translate it from hexadecimal into EBCDIC. The translated 05C
message text will show which module or member was not found in
SYS1.NUCLEUS: Explanation: During nucleus initialization program (NIP) proc-
essing, the pointer to the master catalog could not be obtained from
If memname is IEANUC0x, make sure that x is the correct iden- the SYS1.NUCLEUS data set. Possible causes are:
tifier for the nucleus you need. If x is incorrect, ask the operator
to reIPL the system and specify the correct identifier for the I/O errors while attempting a build link-list request (BLDL macro)
nucleus on the SYSCTL frame load parameter. to find the member.
If memname is a member name other than IEANUC0x, reason Member not found.
code X'4' identifies the module as an MLT, and reason code I/O errors attempting to read records from the member.
X'2' indicates either a nucleus device support module or a
The pointer to the master catalog should be in the SYSCATLG or
module specified on an INCLUDE statement in a NUCLSTxx
SYSCATnn member in the SYS1.NUCLEUS data set.
member (identified on the NUCLST statement in the LOADxx
member). Source: DFSMSdfp
If the member is a module specified on an INCLUDE statement, System Action: The system issues messages about the problem.
verify that the module was specified correctly. The system enters a non-restartable wait state.
If the member is an MLT or a nucleus device support module, Operator Response: ReIPL the system. If the problem persists,
find the MLT name and the corresponding user information notify the system programmer.
module (UIM) name in the MVS device report from HCD. If the System Programmer Response: Ask the operator to IPL a dif-
UIM was installation-provided: ferent system. Use it to determine if the SYSCATLG or SYSCATnn
– Verify that the UIM logic is correct and that the UIM pro- member exists in the SYS1.NUCLEUS data set and is in the correct
vided the correct MLT name. format:
– Make sure the SYS1.NUCLEUS directory contains a direc- Run the IEHLIST utility with LISTPDS to list the directory of the
tory entry for the MLT. SYS1.NUCLEUS data set.
Run the IEBPTPCH utility to print the SYSCATLG or SYSCATnn
member of SYS1.NUCLEUS.
Wait State Codes WSC-11
05D 05F
Add the SYSCATLG or SYSCATnn member to the SYS1.NUCLEUS volume serial is incorrect, correct it and have the operator reIPL
data set. the system.
If the problem persists, search problem reporting databases for a fix If the master catalog name is correct, look for a problem with the
for the problem. If no fix exists, contact the IBM Support Center. VVDS entry for the master catalog.
If neither the master catalog name nor the VVDS entry for the
05D master catalog are in error, this is probably a hardware error.
Explanation: During initialization, DFP could not find a data set Contact hardware support, providing one of the following:
control block (DSCB) for the master catalog or could not read the – Run the IEBPTCH utility to print the cataloged procedure.
DSCB from the volume pointed to by the SYS1.NUCLEUS data set.
– Issue the access method services LISTCAT command to list
For an integrated catalog facility (ICF) master catalog, NIP could not catalog entries and information about objects defined in the
read the DSCB for the VSAM volume data set (VVDS) of the volume catalog.
that it required. For example, a page data set is specified that
The master catalog must either be recreated or restored to the
resides on a different volume than the master catalog, and the
proper volume after the damage to that volume is corrected.
volume containing the page data set has a damaged VVDS.
Possible causes include:
05F
Hardware errors
Explanation: DFP processing found an error related to the master
The wrong volume is mounted catalog. The problem was caused by one of the following:
The pointer to the master catalog is incorrect in the SYSCATLG The catalog information found during IPL was incorrect. This
member of SYS1.NUCLEUS data set. information can be supplied by SYSCATLG or SYSCATxx
members of the SYS1.NUCLEUS data set, or in the LOADxx
Source: DFSMSdfp
members of the SYS1.PARMLIB or SYSn.IPLPARM data sets.
System Action: The system issues messages about the problem.
Either the SYSCATLG member or an alternate SYSCATxx
The system enters a non-restartable wait state.
member of SYS1.NUCLEUS contains incorrect data.
Operator Response: ReIPL the system. Notify the system pro-
Either the master catalog's VSAM volume record (VVRs) or its
grammer.
first ten records have been improperly written over or damaged.
System Programmer Response: IPL a different system. Use it to
The first ten records in the master catalog data set describe the
determine whether the volume table of contents (VTOC) of the
master catalog itself. They are the catalog entry for the master
volume containing the master catalog or the VVDS are correct:
catalog.
Run the IEHLIST utility with LISTVTOC FORMAT to format the
Source: DFSMSdfp
VTOC for the volume associated with the problem.
System Action: The system issues messages about the problem.
Run the IEBPTPCH utility to print the SYSCATLG member of
The system enters a non-restartable wait state.
SYS1.NUCLEUS.
Operator Response: Notify the system programmer. After the
If the problem persists, contact hardware support.
system programmer corrects the error in the SYSCATLG member or
alternate SYSCATxx member, reIPL the system.
05E
System Programmer Response: Check to see if the catalog infor-
Explanation: An I/O error occurred while the system attempted to mation was correctly specified. This information will be taken from
read the master catalog self-describing records. the first of these places it is found during IPL:
The wait state can be caused by one of the following: 1. The SYSCAT parameter found in the specified LOADxx member
The VVDS entry for the master catalog is damaged. of the first SYS0.IPLPARM through SYS9.IPLPARM data set
found on the IODF volume.
The master catalog name and/or volume serial in the SYSCATxx
member of SYS1.NUCLEUS is incorrect. 2. The SYSCAT parameter found in the specified LOADxx member
of SYS1.PARMLIB on the IODF volume.
A hardware error was detected.
3. The SYSCAT parameter found in the specified LOADxx member
A catalog was moved to a different volume serial and the
of SYS1.PARMLIB on the system residence volume.
SYSCATxx member was not updated.
4. The specified SYSCATxx member of the SYS1.NUCLEUS data
The first ten records in the master catalog data set describe the
set used for IPL (if none is specified, SYSCATLG is the default).
master catalog itself. They are the catalog entry for the master
catalog. Confirm that the data in the SYSCATLG member or alternate
SYSCATxx member, including the volume serial number and the
Source: DFSMSdfp
device type, are correct. To look at the master catalog, run the
System Action: The system enters a non-restartable wait state. IEBPTPCH utility to print the SYS1.NUCLEUS data set.
Operator Response: ReIPL the system and report this wait state If the member is correct, either restore the master catalog to the
code to the system programmer. proper volume or recreate it.
System Programmer Response: Do the following: If the problem persists, search problem reporting databases for a fix
Check the the master catalog name and volume serial in the for the problem. If no fix exists, contact the IBM Support Center.
SYSCATxx member of the SYS1.NUCLEUS. If the name or
WSC-12 OS/390 V2R8.0 MVS System Codes
060 064
See OS/390 MVS Recovery and Reconfiguration Guide for further
060
information about restarting the system.
Explanation: While saving or rebuilding the pageable link pack
area (PLPA) or extended PLPA (EPLPA), the auxiliary storage 063
manager (ASM) detected an error in processing external page table
entries. Explanation: The nucleus initialization program (NIP) was unable
to obtain storage. The probable cause of this error is that insufficient
Source: Auxiliary storage manager (ASM) system queue area (SQA) was available to provide the options
System Action: The system issues message IEA943W. The requested for this IPL. Another possibility is a system error resulting
system ends the IPL. in excessive demands on the NIP region.
Operator Response: Notify the system programmer of this wait Source: Auxiliary storage manager (ASM)
state. ReIPL, specifying the CLPA system parameter. For a hard- Operator Response: Notify the system programmer.
ware error, contact hardware support.
System Programmer Response: If the request was for SQA after
System Programmer Response: Try to determine the cause of the NIP processes the SQA parameter, the problem can be corrected by
problem. Check for hardware and software errors. specifying a larger value on the ‘SQA’ parameter. However, the
problem can occur before NIP processes the SQA parameter.
061
If the system was initialized with insufficient central storage available
Explanation: The auxiliary storage manager (ASM) detected an to back the SQA requests, then it may be necessary to increase the
error with the time-of-day (TOD) clock while processing the store amount of online storage before attempting to reIPL, or to reduce the
clock (STCK) instruction. number of optional system facilities selected for this system config-
Source: Auxiliary storage manager (ASM) uration.
System Action: The system issues message IEA945W. The If the problem persists, search problem reporting databases for a fix
system ends IPL. for the problem. If no fix exists, contact the IBM Support Center.
Operator Response: Correct the TOD clock. ReIPL the system. If
064
the problem persists, contact hardware support to repair the clock.
Explanation: During nucleus initialization program (NIP) proc-
062 essing, NIP detected a software or hardware error. An attempt was
made to enter the recovery termination manager (RTM). This was
Explanation: An error occurred on one or more channel paths to trapped by NIP because the system is in a variable state of initializa-
reserved devices. tion and, in particular, RTM is not fully initialized.
Source: Input/output supervisor (IOS) Bits 44 to 51 of the instruction address in the program status word
System Action: The system does not use the channel path(s) until (PSW) contains a table entry code. The code explains the error as
recovery is complete. Recovery waits until the operator restarts the follows:
system. Code Explanation
The system issues message IOS201E when the I/O on other 01 A module branched to abnormal ending processing.
processors that share devices can be started.
02 A dynamic address translation (DAT) error occurred.
Operator Response: The correct response varies, depending on
whether there are non-DASD devices on any channel paths where 03 The operator pressed the RESTART key instead of the
an error occurred. time-of-day (TOD) key.
For errors on channel paths with DASD devices only: 04 A machine check occurred. This can be caused by:
1. Enter the IOACTION STOP command to prevent other An I/O interrupt from a device that was not defined
processors that share devices from initiating I/O. If the in the I/O configuration program (IOCP). The
IOACTION STOP command fails, stop sharing processors to channel subsystem presents the interruption as a
prevent I/O activity to the shared devices. machine check.
2. After the IOACTION STOP command is successful or sharing The system is changing the state of a resource
processors have been stopped, restart the system that has the during system initialization.
error. 05 A Supervisor Call (SVC) instruction was issued in an
3. After the system issues message IOS201E, do one of the incorrect mode. However, this is not usually the actual
following: error, because it is common for system routines to issue
an abend while holding a lock.
If the IOACTION STOP command was successful, enter the
IOACTION RESUME command. Code X'05' can occur when:
Otherwise, restart sharing processors. NIP is reading from SYS1.PARMLIB
For errors on channel paths with at least one non-DASD device: NIP is trying to process an incorrect load module
1. Stop sharing processors to prevent I/O activity to the shared I/O errors occurred on the system residence volume
devices. 06 A paging I/O error occurred.
2. Restart the system that has the error. 07 A call to abnormal ending processing was issued without
3. After the system issues message IOS201E, restart sharing providing an address space identifier (ASID).
processors. 08 A request for memory ending occurred.
Wait State Codes WSC-13
065 06F
09 A program check occurred. Accompanying message If SVC 13 was not the last SVC issued, then it is a true SVC
IEA304W further explains this wait state and entry code. error. The problem could be:
If the message does not appear on the console, you can
– A module is incorrectly issuing an SVC while holding a lock.
find the message in the wait state message area
(WSMA). The WSMA is described in OS/390 MVS Data – A routine that was in control returned to its caller without
Areas, Vol 5 (SSAG-XTLST). releasing a lock. In this case, the SVC-issuer is not at fault.
0A NIP called the alternate CPU recovery (ACR) compo- For table entry code X'09', the program check OLD PSW indi-
nent. cates the type of exception and where it occurred. The registers
at the time of the exception are saved at displacement X'48'
0B A call to cross-memory abend processing was issued
into the logical configuration communication area (LCCA). If it
with the address space identification (ASID) provided.
was a translation exception (program interrupt code X'10' or
0C A routine entered RTM holding a cross memory local X'11'), location X'90' contains the address that could not be
(CML) lock. translated. The system trace also contains this information.
0D A module specified the ITERM option on the CALLRTM Search problem reporting databases for a fix. If no fix exists, contact
macro. the IBM Support Center. Provide the information gathered above,
including the wait state PSW.
0E A module specified the SABEND option on the
CALLRTM macro.
065
0F A call to ABTERM processing was issued with
RETRY=NO. Explanation: During nucleus initialization program (NIP) proc-
essing, a program issued type 3 or 4 Supervisor Control (SVC)
10 A call to cross-memory ABTERM processing was issued
instruction before these types were loaded. This SVC interrupt was
with RETRY=NO.
trapped by NIP.
Source: Nucleus initialization program (NIP)
Source: Nucleus initialization program (NIP)
System Action: The system issues messages about the problem.
System Action: The system enters a non-restartable wait state.
The system may issue message IEA304A. The system enters a
restartable wait state. Operator Response: Notify the system programmer. If the system
programmer requests it, obtain a stand-alone dump.
Operator Response: Do one of the following:
System Programmer Response: Search problem reporting data-
For table entry code X'03' reIPL the system.
bases for a fix for the problem. If no fix exists, contact the IBM
For table entry code X'04', do the following: Support Center. Provide a stand-alone dump.
– At the system console, press the VIEWLOG key and look
for this message: 06F
INTERRUPTION FROM DEVICE NOT IN IOCDS. CHPID=6C, UA=E4. Explanation: The system found one of the following along a path to
– Check that the system is using the correct I/O configuration a device:
data set (IOCDS). An inoperative control unit
– Notify the system programmer and provide the text of the A channel error
message. An undetermined error
Do not: There is no device reservation or active I/O operation on the path to
indicate which system owns the device.
– Detach, attach, or define any I/O service during system
initialization. If the system could not determine the channel path identifier and/or
device number, the system substitutes X'FFFF' for the channel path
– Configure on or offline any channel path identifiers (CHPID) identifier and/or device number.
to the logical partition where the system is initialized if the
system is running in logically partitioned (LPAR) mode. Source: Input/output supervisor (IOS)
For table entry code X'09', try restarting the system, specifying System Action: The system:
CLPA in the reply to accompanying message IEA101A. Table 1. Disables the device.
entry code X'09' may occur on a warm or quick start if the pre-
2. Enters wait state X'06F' because it cannot issue message
vious cold start failed before or during master scheduler initial-
IOS427A.
ization.
3. Expects an operator action, but does not prompt the operator for
For other entry codes, check the READ/WRITE switch on direct
a reply.
access storage devices (DASD) before reporting this wait state
code to the system programmer. Operator Response: Do the following:
If the system programmer requests it, obtain a stand-alone dump. 1. At the system console, enter the F ALTCP command to invoke
the ALTER/DISPLAY frame.
System Programmer Response: Do the following before con-
tacting the IBM Support Center: 2. When the system displays the ALTCP frame, enter the number
of any processor in the system.
For table entry code X'05', determine if an SVC 13 was the last
SVC issued by looking at the SVC OLD PSW or the trace table 3. Enter A2 B3 to display primary virtual storage.
in a stand-alone dump. If this is the case, register 1 in the trace 4. Enter 40C at the following prompt:
table contains the abend codes and register 15 contains the
Address(hex) = >
reason code. The abend code may indicate which SVC issued
the abend. If it does, the trace table may show the module that 5. Record the first four bytes of data at storage location X'40C'.
issued the SVC.
WSC-14 OS/390 V2R8.0 MVS System Codes
070 071
6. Enter the address found at storage location X'40C' at the fol- See message IOS427A in OS/390 MVS System Messages, Vol 5
lowing prompt: (IGD-IZP) for additional information.
Address(hex) = >
070
Note: This is indirect addressing.
Explanation: During initial program load (IPL) processing, IPL did
The system displays the contents of the error information area:
not find enough contiguous central storage to satisfy a request that
Offset 0 The channel path identifier (or X'FFFF', if requires contiguous storage. This is probably a hardware error.
the CHPID could not be determined).
Source: Initial program load (IPL)
Offset 2 The device number (or X'FFFF', if the
Operator Response: Check the configuration of storage. If hard-
device number could not be determined).
ware errors have made too many frames unusable, contact hardware
7. Press the STOP key. support. Otherwise, notify the system programmer.
8. Enter A1 B3 to alter primary virtual storage. System Programmer Response: Make sure that enough central
9. Enter 30E at the following prompt: storage is available for IPL processing. You may have to reduce the
number of optional system facilities selected for this system config-
Address(hex) = >
uration.
10. Move the cursor to location X'30E'. Depending on your installa-
tion's procedures, enter one of the following recovery codes: 071
Code Explanation Explanation: Either the system or the operator initiated a restart.
00 Try to restart the device without attempting The reason code, located in SDWA, explains the reason for the
recovery. (Entering this code is the same as abnormal end:
replying 'NOOP' to message IOS427A). If the Code Explanation
problem persists, the system issues message
IOS427A again (or wait state code X'06F' if the 00 One of the following occurred:
system cannot issue IOS427A); consider entering The operator selected RESTART option 0 to initiate
one of the other recovery codes. the abnormal end.
Enter the RESTART x command to restart the The operator replied ABEND to either message
system; x is the processor ID selected in step 2. IEA500A or BLW004A.
01 Attempt to recovery access to the device through an The operator selected RESTART with no option.
alternate channel path. (Entering this code is the When no option is specified, the system uses the
same as replying X'UR' to message IOS427A). default, which is option 0.
Before entering this recovery code and restarting
The operator did not reply to either message
the processor, all other processors that share the
IEA500A or IEA502A within 125 seconds.
device you must prevent from initiating I/O to this
device by issuing the IOACTION STOP command. If The system could not determine the reason for the
this command fails, you must stop all sharing restart, and uses the default, which is option 0.
processors to prevent I/O activity to the shared 04 The operator selected RESTART option 1 to initiate
device. system diagnosis and repair.
08 A programming error caused the program that was cur-
Enter the RESTART x command to restart the rently running to branch directly to the restart interruption
system; x is the processor ID selected in step 2. handler.
The system might issue one of the following
messages: 0C The operator selected RESTART option 0 on a
processor that is in a valid spin waiting for a global
IOS428I - the attempt to access the device resource held by a second processor that is in an erro-
through an alternate channel path was suc- neous disabled loop. A DSGNL RESTART command,
cessful. directed to the second processor, failed.
IOS104I - the attempt to access the device
through an alternate channel path was not suc- 10 The system started writing logrec error records after
cessful. detecting an excessive spin loop condition. The inter-
rupted unit of work continues to run.
After the system issues either message, start I/O to 20 The system abnormally ended the program that was
the shared device either by issuing the IOACTION causing a system excessive spin loop. Recovery rou-
RESUME command or by restarting the sharing tines are not allowed to retry because the recovery
processors if they were stopped in step 11. action for the spin loop was TERM.
02 Force the device offline. (Entering this code is the 30 The system abnormally ended the program that was
same as replying X'BOX' to message IOS427A). causing a system excessive spin-loop condition.
The system issues message IOS501I. Enter the Recovery routines are allowed to retry because the
RESTART x command to restart the system; x is recovery action for the spin loop was ABEND.
the processor ID selected in step 2. Source: Loadwait/Restart
Enter the RESTART x command to restart the System Action: The system does one of the following:
system; x is the processor ID selected in step 2.
For reason code X'00', X'08', X'0C', X'20', or X'30', the
system abnormally ends the program currently running.
Wait State Codes WSC-15
072 074
For reason code X'00', the system might issue either message For reason code X'10', X'20', or X'30', obtain the
IEA500A or BLW004A. PSW from the logrec error record.
For reason code X'04', the system detects and repairs, where For reason code X'0C', X'20', or X'30', ask the
possible, errors in critical system areas. The system refreshes operator to obtain an SVC dump. Format the dump to
selected system control blocks and validates and repairs see the PSW at the time of error.
selected system resources. The system logs the old values of
2. Use the address in the PSW to obtain the name of the
some refreshed control block fields in the variable recording
module that was causing the spin.
area (VRA) of the system diagnostic work area (SDWA). The
system writes these old values in the logrec error record. Then If the module is not an IBM module, continue diagnosis
the system returns control to the interrupted program. with the module.
For reason code X'10', the system records the excessive spin If the module is an IBM module, search problem
loop in a logrec error record. reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the
Operator Response: If requested by the system programmer, set a
dump and the logrec error record.
SLIP trap to obtain a dump.
System Programmer Response: Depending on the reason code, See OS/390 MVS Diagnosis: Procedures for information about
do the following: diagnosing a loop.
Reason code X'00':
Either message IEA500A or BLW004A might accompany this 072
reason code and identify the work that was in progress at the Explanation: There is no more room in the work space allocated to
time of the interruption. initial program load (IPL).
1. If a logrec error record is not produced with the abend, ask Source: Initial program load (IPL)
the operator to obtain an SVC dump. System Action: The system enters a non-restartable wait state.
2. Examine the program status word (PSW) at the time of System Programmer Response: Search problem reporting data-
error in the logrec error record. The PSW points to the bases for a fix for the problem. If no fix exists, contact the IBM
location where RESTART was entered by the operator. If Support Center.
the program was in a loop, the PSW address will be within
the loop.
073
3. Examine the system trace table for evidence of a loop or a
Explanation: Initial program load (IPL) is waiting for an I/O or
wait. If a loop or a wait is suspected, use the address in the
external interrupt. Bits 40 through 43 of the program status word
PSW to obtain the name of the looping module.
(PSW) contain a reason code:
If the module is not an IBM module, continue diagnosis
Code Explanation
with the module.
1 IPL is waiting for an I/O interrupt.
If the module is an IBM module, search problem
reporting data bases for a fix for the problem. If no fix 2 IPL is waiting for an external interrupt.
exists, contact the IBM Support Center. Provide the Source: Initial program load (IPL)
dump and the logrec error record.
System Action: The system enters an enabled wait state.
Reason code X'08'
Operator Response: The wait time might vary between 30
Determine which program branched incorrectly, as follows:
seconds and three minutes. If the system is still in a wait state after
1. If a logrec error record is not produced with the abend, ask three minutes, record the wait state PSW and notify the system pro-
the operator to obtain an SVC dump. grammer.
2. Look at register 14 at the time of the error. If the illegal System Programmer Response: Examine the reason code in bits
branch was made by a BALR 14,15 instruction, register 14 40 - 43 of the wait state PSW. If the reason code is X'1', the
points to the instruction following the instruction that took system is waiting for an I/O operation to complete. Have the oper-
the bad branch. If this instruction is a branch instruction, ator retry the IPL after three minutes. If the reason code is X'2', a
then this instruction probably branched directly into the hardware problem exists. Have the operator retry the IPL. If the IPL
restart interrupt handler. is not successful, contact hardware support.
3. Use the address in register 14 to get the name of the
module that issued the bad branch instruction. 074
If the module is not an IBM module, continue diagnosis Explanation: Initial program load (IPL) contains a program logic
with the module. error. Bits 36 through 43 of the program status word (PSW) contain
a reason code:
If the module is an IBM module, search problem
reporting databases for a fix for the problem. If no fix Code Explanation
exists, contact the IBM Support Center. Provide the 01 An incorrect Supervisor Call (SVC) instruction was
dump and the logrec error record. issued.
Reason code X'0C', X'10', X'20', or X'30' 02 IPL SVC stack overflow.
Determine why an excessive spin condition occurred, as follows:
03 IPL SVC stack underflow.
1. Get the program status word (PSW) at the time of error as 04 IPL received an unexpected condition code of 2 on a
follows: Start Subchannel (SSCH) instruction.
WSC-16 OS/390 V2R8.0 MVS System Codes
075 077
05 IPL received an unexpected condition code of 1 on a
075
Test Subchannel (TSCH) instruction.
Explanation: Initial program load (IPL) could not load a module.
06 IPL received an unexpected condition code on a Load
Bits 36 through 43 of the program status word (PSW) contain a
Real Address (LRA) instruction. Message IEA090W,
reason code.
which appears in the IPL WTO buffer, accompanies this
reason code. Code Explanation
07 IPL received an incorrect parameter list. 01 IPL could not find IRIM IEAIPL01 in the
SYS1.NUCLEUS data set. This could be caused by:
08 IPL received a nonzero condition code on a Modify Sub-
channel (MSCH) instruction. Previous I/O error reading SYS1.NUCLEUS
09 Code was loaded from a new restart PSW. This code Mismatch in IODF or IOCDS of true system config-
will be loaded when a restart is issued on a processor uration
that has a zero prefix register. The prefix register is zero Device cabling error for IODF or IOCDS
when the operator attempts to do a restart too early in
IPL or in a logically offline processor in LPAR mode. 02 A module is too large; it is longer than 4096 bytes.
Source: Initial program load (IPL) 03 Either the delimiter for the end of the IPL resource initial-
ization module (IRIM) list was encountered before IPL
System Action: The system may issue message IEA090W to the found all the IRIMs or a pre-MVS SP 4.3 IPL text was
IPL WTO buffer. The system enters a non-restartable wait state. attempting to IPL a system at a level of MVS SP 4.3 or
Operator Response: For a reason code other than X'06', notify higher.
the system programmer. 04 IPL could not find an IRIM member in SYS1.NUCLEUS.
For reason code X'06', do the following to find the WTO buffer and 05 An IRIM module is too large; it is longer than 4096
locate message IEA090W in the buffer: bytes.
1. Using the hardware ALTER/DISPLAY facility, read the real 06 The IPL text on the volume used to IPL did not match
address in central storage at X'14'. This address points to the the nucleus code resident on that volume.
IPL diagnostic area.
Source: Initial program load (IPL)
2. Add X'28' to the address at real X'14', and also read this as a
real address in central storage. The result is the 31-bit virtual System Action: The system enters a non-restartable wait state.
address of the IPL vector table (IVT). Operator Response: Record the wait state PSW. Notify the system
3. Add X'E0' to the IVT address. The result is the 31-bit address programmer, and obtain a stand-alone dump, if requested.
of the IVTMQHP field. IVTMQHP contains the address of the System Programmer Response: Make sure that the module is
message queue header (MQH). properly link-edited into SYS1.NUCLEUS. Then ask the operator to
4. MQH+X'0' contains the address of the oldest message queue reIPL. For reason code 06 or 03 (in the case of an IPL text error),
element (MQE) available. The message text for the oldest MQE run ICKDSF to install the proper level of the IPL text on the volume
begins at MQE+X'8'. used to IPL.
5. Use MQE+X'0' of the oldest MQE to find the MQE of the next
oldest message. Again, the message text for this MQE begins at 076
MQE+ X'8'. Explanation: During initial program load (IPL) processing, the
6. Repeat this sequence (using MQE+X'0' of the current MQE to system attempted to load an IPL resource initialization module (IRIM)
locate the next MQE), until the message text for the appropriate or the DAT-off nucleus, but the system encountered a relocatable
message is displayed. address constant that is not a fullword. (DAT is the acronym for
dynamic address translation.)
Notify the system programmer, providing the text of message
IEA090W. If the system programmer requests it, obtain a stand- Source: Initial program load (IPL)
alone dump. System Action: The system enters a non-restartable wait state.
System Programmer Response: Search problem reporting data- Operator Response: Notify the system programmer.
bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: Make sure that the IRIM module
Support Center. Provide the stand-alone dump.
is properly link-edited into SYS1.NUCLEUS on the system residence
For reason code X'06', provide the text of message IEA090W trans- volume.
lated from hexadecimal into EBCDIC.
077
Explanation: The system cannot resolve the entry point of a super-
visor call (SVC) or extended SVC router (ESR) routine.
Operator Response: Report this wait state to the system pro-
grammer. If requested by the system programmer, obtain a stand-
alone dump.
System Programmer Response: Make sure that the IEANUC0x
module is properly link-edited. If the problem cannot be resolved,
search problem reporting databases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the stand-alone
dump.
Wait State Codes WSC-17
078 084
Operator Response: Provide a stand-alone dump if requested by
078
the system programmer. ReIPL the system.
Explanation: The master catalog could not be opened successfully.
System Programmer Response: The problem may be caused by
Message IEC161I precedes this wait state and identifies the specific
a loop which causes LSQA to be exhausted. If the source of the
open failure.
problem cannot be determined, search problem reporting databases
Source: DFSMSdfp for a fix. If no fix exists, contact IBM support center. Provide the
Operator Response: Probable I/O error. ReIPL the system and stand-alone dump.
report this wait state code to the system programmer.
081
Programmer Response: Correct the error identified by message
IEC161I. Explanation: Initial program load (IPL) tried to load a module from
the SYS1.NUCLEUS data set. The SYS1.NUCLEUS data set or an
System Programmer Response: If the error recurs and the
IEANUC0x or IEAVEDAT member occupies more than one extent.
program is not in error, search problem reporting databases for a fix
for the problem. If no fix exists, contact the IBM Support Center. Source: Initial program load (IPL)
System Action: The system enters a non-restartable wait state.
07B
Operator Response: Notify the system programmer.
Explanation: An operation exception occurred when a Load
System Programmer Response: Make sure that the
Address Extended (LAE) instruction was issued for a central
SYS1.NUCLEUS data set is allocated to single extent. Then ask the
processor other than an ESA/370. A reason code of X'1' accompa-
operator to reIPL the system.
nies this wait state.
Source: Nucleus initialization program (NIP) 083
System Action: The system enters a non-restartable wait state. Explanation: The system found an incorrect address in a critical
Operator Response: Contact hardware support. prefixed storage area (PSA) field. The damage could not be cor-
rected by supervisor recovery. This error is probably a software
07D error.
Explanation: During system initialization, an error occurred when Bits 40 to 47 of the wait state program status word (PSW) contain a
the system tried to process the IEASYMxx parmlib member. A hexadecimal reason code that identifies the PSA field containing the
reason code in register 15 explains the error: incorrect address:
Code Explanation Code PSA Field
00 The system found a circular system symbol definition in 01 Field PSALCCAV or PSASCWA
IEASYMxx. A circular system symbol definition is one 02 Field PSAPCCAV
that contains another system symbol that is not resolved.
Source: Supervisor control
System Action: The system issues message IEA012E,
System Action: The system may write a logrec error record.
which further describes the error, to the NIP console.
The system enters a non-restartable wait state. Operator Response: If the system programmer requests a stand-
alone dump, stop all other systems and obtain a stand-alone dump.
System Programmer Response: See the system pro-
ReIPL the system.
grammer response for message IEA012E.
System Programmer Response: Do the following:
04 The system found an error in IEASYMxx from which it
could not recover. The error occurred when the system 1. If necessary, ask the operator to obtain a stand-alone dump.
tried to determine the substitution text for a system 2. Examine the damaged PSA for the system that is in wait state
symbol definition. X'083'. See if you can recognize the damage.
System Action: The system issues message IEA013E, 3. Search problem reporting databases for a fix for the problem. If
which further describes the error, to the NIP console. no fix exists, contact the IBM Support Center. Provide the stand-
The system enters a non-restartable wait state. alone dump and, if available, the logrec error record.
Operator Response: Contact the system programmer.
Provide the text of message IEA013E. 084
System Programmer Response: See the system pro- Explanation: The recovery termination manager (RTM) encount-
grammer response for message IEA013E. ered an error that could not be corrected while:
Source: Nucleus initialization program (NIP) Supporting recovery or ending of a system routine
Supporting recovery or ending of a task of an application
07E program
Explanation: The system was unable to obtain storage from LSQA Bits 44 through 51 of the wait state program status word (PSW)
which was needed to process an SVC instruction. The system contain a hexadecimal reason code that describes the error:
loaded a wait state because it was unable to terminate the address
space of the program which issued the SVC.
Source: Supervisor Control
System Action: The system enters a non-restartable wait state and
issues message IEA297W.
WSC-18 OS/390 V2R8.0 MVS System Codes
085 087
Code Explanation sive errors. Determine the offset into the module at which
the recursive errors occurred.
04 A first level interruption handler (FLIH) determined that
the interruption, which was in a PSW-disabled routine, 2. Search problem reporting databases for a fix for the
was an error condition. The FLIH called RTM to recover problem. Include in the search argument:
or to end the routine that was interrupted. While proc-
– Name of the overlaid control block field: FLDS/cccccccc
essing the request, RTM found uncorrectable damage to
– Wait state code: WS/D0084
at least one functional recovery routine (FRR) stack
– Reason code: PRCS/hhhhhhhh
pointer in the recovery stack vector table (PSARSVT) of
– Module name: RIDS/cccccccc
the prefixed save area (PSA).
If no fix exists, contact the IBM Support Center.
08 The FRR recovery routine for RTM's FRR processing
could not recover from an error in RTM. The system
invoked the super FRR. The super FRR scheduled RTM 085
recovery as the retry attempt for the original error. This Explanation: During this warm start IPL, the auxiliary storage
RTM recovery tried to end the current address space but manager (ASM) forced a switch to a cold start. ASM determined that
encountered a second error. one of the following is true:
0C RTM found an error while processing the FRR stack. The pageable link pack area (PLPA) page data set is behind a
RTM processing is not covered by an FRR recovery cached device. The cache must be reset.
routine. Therefore, RTM attempted to end the address PLPA has overflowed to the COMMON page data set and the
space but encountered a second error. common data set is on a cached device. Warm or quick start
10 The system entered the program check FLIH recursively has failed. The cache must be reset.
for segment exceptions, and detected a dynamic Source: Auxiliary storage manager (ASM)
address translation (DAT) error in an address space.
System Action: The system ends processing and enters the wait
The system invoked RTM's FRR processing to end the
state.
address space experiencing the DAT error, but RTM's
FRR processing encountered a second error. This is an Operator Response: To reset the cache, reIPL the system with the
unrecoverable software error. CLPA option.
14 RTM detected a bad PSATOLD value while running in
task mode. RTM could not end the failing address space 087
to resolve the problem. Explanation: At the end of removing a system from a sysplex, the
Source: Recovery termination manager (RTM) system enters this wait state. A hexadecimal reason code in register
15 indicates the reason why the system was removed:
System Action: The system issues message IEA797W and enters
the X'084' wait state. Code Explanation
Operator Response: If requested by the system programmer, 01 Communications task (COMMTASK) initialization could
obtain a stand-alone dump. ReIPL the system. not establish a member of the SYSMCS group because
the maximum number of members per cross-system
System Programmer Response: For reason code: coupling facility (XCF) group was reached.
X'04', do the following: . 02 A recursive abend occurred while the system was proc-
1. In the dump, determine if the system queue area (SQA) and essing the sysplex update task.
extended SQA (ESQA) match the description given for the 03 A recursive abend occurred while the system was proc-
FRR stacks in the FRRS. See OS/390 MVS Data Areas, essing the cross-system update subtask.
Vol 2 (DCCB-ITTCTE) for the FRRS map. If the stacks and
SQA and ESQA do not match, an overlay occurred. 04 A recursive abend occurred during cross-system cou-
pling.
2. Search problem reporting databases for a fix for the
problem. Include in the search argument: 05 A recursive abend occurred while in the sysplex send
data processor.
– Name of the overlaid control block field: FLDS/cccccccc
– Wait state code: WS/D0084 06 A recursive abend occurred in the sysplex receive data
– Reason code: PRCS/hhhhhhhh processor.
– Module name: RIDS/cccccccc 07 A recursive abend occurred in the cross-system service
If no fix exists, contact the IBM Support Center. group exit.
X'08', X'0C', X'10', or X'14', RTM experienced recursive 08 A recursive abend occurred in the cross-system service
errors while processing an error. This problem could be due to message exit.
overlays of critical fields in control blocks such as: 09 A recursive abend occurred while the system processed
– PSA a command/delete operator message (DOM) processor.
– Address space control block (ASCB) 0A A recursive abend occurred when the system processed
– Task control block (TCB) a message.
– Request block (RB)
0B The system failed to join a cross-coupling facility (XCF)
– Extended status block (XSB)
group.
Do the following:
0C A system failed to create cross-coupling facility (XCF)
1. Analyze the dump and logrec error records for recursive control member.
errors. Identify the RTM module that experienced the recur-
Wait State Codes WSC-19
088 08A
0D Another system was unable to accept the system into Source: Initial program load (IPL)
the sysplex because of a storage shortage.
System Action: The system enters a non-restartable wait state.
0E A recursive abend occurred while the system was proc-
Operator Response: For reason codes X'04', X'08' or X'80'
essing the sysplex reply ID task.
notify the system programmer.
11 The system could not join the XCF SYSMCS2 group.
For reason code X'00', check the value specified in the LOAD
12 The system could not create control members in the parameter. If it is incorrect, use the correct value and reIPL. If it is
XCF SYSMCS2 group. correct, notify the system programmer that the LOADxx member is
missing from SYSn.IPLPARM on the IODF volume or
13 The system could not initialize reply ID processing.
SYS1.PARMLIB on the IODF volume or on SYSRES.
Source: Communications task (COMMTASK)
System Programmer Response: Do one of the following:
System Action: The system enters wait state X'087'.
For reason code X'00', create the LOADxx member of
System Programmer Response: Search problem reporting data- SYSn.IPLPARM on the IODF volume or SYS1.PARMLIB on the
bases for a fix for the problem. If no fix exists, contact the IBM IODF volume or on SYSRES. Tell the operator what value to
Support Center. use for the LOAD parameter.
For reason code X'02' make sure that the NUCLST statement
088 was specified correctly in the LOADxx member of
Explanation: During initial program load (IPL), the system encount- SYSn.IPLPARM or SYS1.PARMLIB. Make sure also that the
ered an error in processing the LOADxx or NUCLSTxx members of NUCLSTxx parmlib member resides in the same data set as the
SYS1.PARMLIB. LOADxx parmlib member.
The following format shows the location of the reason code in bits 36 For reason code X'06' or X'0A', delete the NUCLSTxx
through 43 of the PSW: member of SYS1.PARMLIB. Then either recreate the
X'ðððAðððð 8rrxxwww' NUCLSTxx member, or create a different one. Tell the operator
what value to use for the LOAD parameter.
000A0000
For reason code X'04' and X'08' delete the LOADxx member.
The A is bits 12 through 15 (the CMWP bits).
Then either recreate the LOADxx member, or create a different
8 If bits 33-39 are not zero then bit 32 must be on indicating one. Tell the operator what value to use for the LOAD param-
AMODE (31 bit addressing mode). eter.
rr The reason code. For reason code X'0C', correct the NUCLSTxx member so that
it does not exclude IEANUC0x.
www
For reason code X'80', remove the MVSCP statement from the
The wait state code.
LOADxx member used to IPL. An IODF must be used to specify
Code Explanation I/O configuration data. See OS/390 HCD User's Guide for infor-
mation about IODF.
00 IPL could not find the LOADxx member in
SYSn.IPLPARM on the IODF volume or SYS1.PARMLIB
on the IODF volume or on SYSRES. Either the system 089
programmer did not create the member or the operator Explanation: During NIP processing, the system found an error
typed the wrong value for the LOAD parameter. with a unit control block (UCB) while trying to create the eligible
02 The system could not find the NUCLSTxx member of devices table (EDT).
SYSn.IPLPARM or SYS1.PARMLIB that was specified Source: Allocation/unallocation
on the NUCLST statement in the LOADxx
System Action: The system enters a non-restartable wait state.
SYS1.PARMLIB member.
System Programmer Response: Determine if the problem is a
04 The SYSn.IPLPARM or SYS1.PARMLIB directory entry
device error. If not, take a stand-alone dump of the system. Try to
for the LOADxx member contains incorrect information.
IPL with an IODF that is known to be good.
IPL cannot read the LOADxx member.
If the source of the problem cannot be determined, search problem
06 The SYSn.IPLPARM or SYS1.PARMLIB directory entry
reporting databases for a fix for the problem. If no fix exists, contact
for the NUCLSTxx member contains incorrect informa-
the IBM support center. Provide the dump.
tion, and IPL cannot read it.
08 While reading the LOADxx member, IPL reached the 08A
end-of-file where there should have been more data.
The contents of the LOADxx member are incorrect. Explanation: An error occurred while requesting a wait state with
the WSPARM option on the write to operator (WTO) macro. Bits
0A While reading the NUCLSTxx member, IPL reached the 36-51 of the program status word (PSW) contain a reason code:
end-of-file where there should have been more data.
The contents of the NUCLSTxx member are incorrect. Code Explanation
0C The member of SYS1.NUCLEUS selected was excluded 0001 Two callers, running on the same processor, tried to
by a NUCLSTxx EXCLUDE statement. There was no load the same wait state.
alternate IEANUC0x member of SYS1.NUCLEUS 0002 The system abended wait state processing.
included.
Source: Communications task (COMMTASK)
80 An MVSCP statement was found in the LOADxx
System Action: The system issues message IEA548W. The
member that was used to IPL.
system enters wait state X'08A'.
WSC-20 OS/390 V2R8.0 MVS System Codes
08C 09x
Operator Response: If the system programmer asks for a dump,
09x
request a stand-alone dump. ReIPL the system.
Explanation: The system put a processor into wait state X'09x'
System Programmer Response: Depending on the reason code,
because the following occurred:
do one of the following:
1. The processor was in a spin loop, waiting for an event to occur
0001 See the system programmer response for the requesting
on another processor. The spin loop exceeded the time normally
wait state.
required for the event to occur.
0002 See the system programmer response for the abend dis-
2. The system was unable to issue the excessive spin notification
played in message IEA548W.
message, IEE331A.
08C The third digit (x) of the wait state code identifies the event for which
the processor waited, as follows:
Explanation: An error occurred during workload manager (WLM)
processing. The accompanying reason code identifies an internal, x Event
unrecoverable WLM error. 1 RISGNL response
Source: Workload manager (WLM) 2 Lock release
Operator Response: Notify the system programmer. 4 Restart resource
System Action: The system places the processor into a wait state. 5 Address space to QUIESCE
System Programmer Response: Search problem reporting data- 6 Central processor (CPU) in stopped state
bases for a fix for the problem. If no fix exists, contact the IBM
7 Intersect release
support center. Provide the hardcopy log and the dump.
9 Operator intervening state
08E E Successful bind break release
Explanation: A recursive, unrecoverable error occurred while proc- Bits 40-47 of the wait state program status word (PSW) contain the
essing the NEWIPS sysevent. logical address of the processor causing the spin loop.
Source: Workload manager (WLM) Source: Loadwait/Restart
System Action: The system places the processor into a wait state. System Action: The processor in the spin loop enters restartable
Operator Response: Notify the system programmer. ReIPL the wait state X'09x'. The system may issue a message that describes
system. After reIPL, avoid issuing any of the following commands, if the problem.
possible, because the wait state occurred during the processing of Operator Response: Before restarting the processor, store an
one of them: action code in storage location X'30E' of the processor. The action
Issuing any of the following commands: code indicates the recovery action that the processor will take in an
attempt to resolve the excessive spin-loop condition. The action
– F WLM,MODE=GOAL or COMPAT codes, in order of severity, and the related recovery actions are the
– SET IPS=XX following:
– V WLM,POLICY=XXXXXX when in goal mode Code Recovery Action Performed by System
Activating a service policy from the WLM ISPF application if None SPIN - Continue in the spin loop, waiting for the
running in goal mode. expected event to occur. To start the SPIN action,
restart the processor in the X'09x' wait state.
System Programmer Response: Search problem reporting data-
bases for a fix for the problem. If no fix exists, contact the IBM CC ABEND - Abnormally end the current unit of work on the
support center. Provide the hardcopy log and the dump. processor on which the expected event did not occur. In
this case, the system does allow the recovery routines to
retry.
08F
BB TERM - Abnormally end the current unit of work on the
Explanation: The system attempted to rebuild the work unit
processor on which the expected event did not occur. In
queues, but was unable to do so.
this case, the system does not allow recovery routines to
Source: Supervisor Control retry.
System Action: The system enters a non-restartable wait state, AA ACR - Start alternate recovery (ACR) for the processor
and issues message IEA460W. on which the expected event did not occur. This will take
Operator Response: If the system programmer asks for a dump, the processor offline and initiate an abnormal end (with
request a stand-alone dump. ReIPL the system. retry allowed) for the current unit of work on that
processor.
System Programmer Response: If the source of the problem
cannot be determined, search problem reporting databases for a fix Depending on the type of recovery action, do the following to start
for the problem. If no fix exists, contact the IBM support center. the recovery action:
Provide the dump. Action Procedure
SPIN Restart the processor in the X'09x' wait state.
ABEND
Wait State Codes WSC-21
0A1 0A2
TERM 10 XCF lost access to all couple data sets.
1. Display location X'30E' of the processor in the 14 During IPL, XCF removed a system from the sysplex.
X'09x' wait state.
20 XCF removed the system from the sysplex.
2. Store the action code (X'CC' or X'BB') at location
One of the following occurred:
X'30E'.
An I/O error was encountered by this system on
3. Restart the processor in the X'09x' wait state. The
either the primary or the alternate couple data set
system ignores the restart reason.
after this system joined the sysplex but before it
ACR could complete initialization of the couple data sets.
1. Display the index frame on the system console. An I/O error was encountered by another system in
the sysplex on either the primary or the alternate
2. Stop all the processors in this system.
couple data set after this system joined the sysplex
3. Display location X'30E' of the processor in the but before it could complete initialization of the
X'09x' wait state. couple data sets
4. Store action code X'AA' at location X'30E'. The operator on another system in the sysplex initi-
5. Identify the processor that is causing the spin loop ated a data set transition by making a new alternate
(the failing processor) from the sixth byte of the available via the SETXCF COUPLE,ACOUPLE
X'09x' wait state PSW. The characters 4x will command or by replacing the primary couple data
appear in this byte. x is the identifier for the failing set with the alternate couple data set via the
processor. SETXCF COUPLE,PSWITCH command. This action
was taken after the time that this system joined the
6. Start all processors except the failing processor and
sysplex but before it could complete initialization of
the processor in the X'09x' wait state.
the couple data sets.
7. Restart the processor in the X'09x' wait state (the
The operator replied DOWN to message IXC402D
system ignores the restart reason).
to specify that XCF was to remove the system from
8. After ACR processing is complete, enter a CONFIG the sysplex.
CPU(x),ONLINE command at a console with master
7C System checks indicate that there are no allowable con-
authority, where x is the identifier for the failing
figurations (XCF-local, monoplex, and sysplex) for this
processor.
system based on current settings.
If wait state X'09x' occurs again within approximately one spin-loop
8C XCF will not accept this system into the sysplex because
interval, respond with recovery action of the next greatest severity.
a couple data set inconsistency was detected.
Notify service personnel.
9C The CFRM couple data set has been lost.
0A1 91 Internal XCF error
Explanation: All system-initiated recovery actions were exhausted 104 I/O has been prevented as a result of a system being
without resolving an excessive spin loop. fenced.
Source: Loadwait/Restart 108 The system was partitioned out of the sysplex as speci-
fied by XCFPOLxx.
System Action: The system issues message IEE183W before
loading the wait state. Message IEE178I might have appeared at 10C The system was found to be in a status update missing
least once prior to the wait state, and may provide additional infor- condition and was partitioned out of the sysplex as spec-
mation. ified by the Sysplex Failure Management policy.
Operator Response: Notify the system programmer. Obtain a 110 The system experienced a signalling connectivity failure
stand-alone dump. ReIPL the system. and was partitioned out of the sysplex as specified by
the Sysplex Failure Management policy.
System Programmer Response: Collect all printed output and
output data sets related to the problem. Search problem reporting 114 This is a non-restartable wait state due to the loss of the
databases for a fix for the problem. If no fix exists, contact the IBM ETR link or the ETR itself.
Support Center. 11C Not enough storage to define subchannel notification
vectors.
0A2
Source: Cross-system coupling facility (XCF)
Explanation: Cross-system coupling facility (XCF) or cross-system
System Action: The system enters a nonrestartable wait state and
extended services encountered a non-recoverable error and stopped
issues message IXC220W.
the system. The system also issues this wait state in response to an
operator request to stop the system. See OS/390 MVS Diagnosis: Operator Response: The following reason codes are possible
Reference for information on diagnosing sysplex problems. hardware errors:
The reason codes are in bits 40-51 of the PSW. 10
8C
Code Explanation
110
04 The operator entered the VARY XCF,sysname,OFFLINE 114
command to remove the system from the sysplex.
Look in the LOGREC data set for hardware errors. Correct the hard-
08 XCF lost signalling path connectivity between systems. ware configuration. If the problem persists, contact hardware support.
WSC-22 OS/390 V2R8.0 MVS System Codes
0A3 0A3
The following reason codes represent errors internal to the XCF In conjunction with this wait state, message ISG152W is
component. Call the IBM Support Center for assistance with these issued to the console. This message identifies the XCF
errors. service and the return and reason codes.
C Global resource serialization found an error in parmlib
Reason Codes:
member GRSCNFxx. The wait state is accompanied by
18 24 28 40 50 message ISG043I or ISG044I.
54 58 5C 60 64
10 Global resource serialization found an error in parmlib
6C 70 74 78 80
84 88 90 91 94 member GRSRNLxx. The wait state is accompanied by
98 118 130 140 messages ISG062I and ISG063I.
14 Global resource serialization could not establish the
For other reason codes, see the operator response for any preceding
event notification (ENF) exits. The wait state is accom-
messages.
panied by message ISG021I.
If the system programmer requests it, obtain a stand-alone dump,
18 Global resource serialization found an error in parmlib
specifying:
member GRSCNFxx. The parmlib member specifies a
DUMP DATASPACES OF ASID('XCFAS') device that is already in use. The wait state is accompa-
DUMP RANGE(ALL) IN ASID('XCFAS') nied by message ISG045I.
System Programmer Response: See the system programmer 1C The system IPLed with GRS=NONE and
response for message IXC220W. PLEXCFG=MULTISYSTEM. These two parameters are
Format the stand-alone dump with the following IPCS subcommands: mutually exclusive. The wait state is accompanied by
message ISG159W.
XESDATA, including all the reports and the summary, detail,
and exception levels. 20 Global resource serialization tried to remove this system
from the complex, but the attempt failed. The wait state
COUPLE, including all the reports and the summary, detail, and is accompanied by message ISG152W.
exception levels.
26 Global resource serialization detected an unrecoverable
CTRACE COMP(SYSXES) SUB((GLOBAL)) error in an XCF exit.
CTRACE COMP(SYSXES) SUB((individual-connections)) 28 Global resource serialization detected an internal error.
You can determine the individual connections by issuing the 2C Global resource serialization detected an unrecoverable
CTRACE QUERY command to see the sub name traces associ- failure while running in a sysplex. The wait state is
ated with SYSXES. accompanied by message ISG168W.
CTRACE COMP(SYSXCF) to obtain XCF trace data. 30 Global resource serialization detected an internal error.
Search problem reporting databases for a fix for the problem. If no 34 The system IPLed with GRS=JOIN or TRYJOIN, but
fix exists, contact the IBM Support Center. Provide the formatted global resource serialization could not invoke the XCF
stand-alone dump. Include all the reports and the summary, detail, Set User State service. The wait state is accompanied
and exception levels for each report. by message ISG152W.
38 Global resource serialization could not find the systems
0A3
exclusion RNL exit (ISGGSEEA) while trying to process
Explanation: A system could not successfully participate in a global a GRSRNL=EXCLUDE system parameter.
resource serialization complex. In order for a system to join a
3C Global resource serialization could not find the systems
sysplex, it must also be a member of the global resource serializa-
inclusion RNL exit (ISGGSIEA) while trying to process a
tion complex, but the system cannot join the global resource serial-
GRSRNL=EXCLUDE system parameter.
ization complex for one of the following reasons:
40 The system could not send a message via the XCF
The global resource serialization system parameters specified
message out service.
are incorrect.
44 The global resource serialization complex is unable to
Global resource serialization encountered an unrecoverable
restart after a ring disruption. No active global resource
error.
serialization ring exists, and this system has repetitively
The reason codes are: failed in its attempts to initiate one. The wait state may
Code Explanation be accompanied by messages ISG011I, ISG015I,
ISG021I, ISG025I, ISG173I, ISG176I, or ISG180E.
4 The system IPLed into a sysplex with GRS=JOIN or
TRYJOIN parameters, but global resource serialization 4C The operator entered a VARY GRS,PURGE command
was unable to join the global resource serialization for this system, removing it from the global resource
complex. Systems in a sysplex must be in the same serialization complex.
global resource serialization ring. The wait state is 50 This system is unable to enter the global resource serial-
accompanied by message ISG167W. ization ring. A current member of the global resource
8 The system IPLed into the sysplex with GRS=JOIN, serialization complex belongs to a different multisystem
START, TRYJOIN or STAR system parameter, and sysplex than the rest of the members of the global
when global resource serialization attempted to use the resource serialization complex. Global resource serializa-
cross-system coupling facility (XCF) during initialization, tion only supports one multisystem sysplex per global
the service failed with an unexpected error. resource serialization complex. The wait state is accom-
panied by message ISG182W.
Wait State Codes WSC-23
0A3 0A3
54 This system is unable to reactivate a global resource
serialization ring from the quiesced state. It became qui-
In conjunction with this wait state condition, message
esced because of a ring disruption, system failure, or an
ISG342W is issued to the console. This message identi-
operator-issued VARY GRS,QUIESCE command. No
fies the reason the record could not be accessed.
active global resource serialization system exists. This
system had the most current global request information 90 Global resource serialization processing failed due to the
of all systems in the complex. unexpected termination on one of its tasks that is critical
to global resource processing.
58 This system encountered an unrecoverable software
error in recovery for global resource serialization ring In conjunction with this wait state condition, message
processing. ISG315W is issued to the console. An error code in this
message identifies the task that failed.
5C This system encountered an unrecoverable software
error in recovery for global resource serialization internal 94 During global resource serialization processing, one of
or external command processing. its critical task terminated. Global resource serialization
is unable to reinstate the task because the ATTACH for
60 Global resource serialization tried to invoke the XCF
the task failed with an error return code.
Query service to gather information about the sysplex,
but the attempt failed. The wait state is accompanied by In conjunction with this wait state condition, message
message ISG152W. ISG316W is issued to the console. This message identi-
fies the module the could not be ATTACHed and the
64 This system's inclusion resource name list (GRS RNL
error return code from ATTACH.
parmlib member) is not the same as the one the global
resource serialization complex is using. 98 During recovery, a primary global resource serialization
control block was damaged. Global resource serialization
68 This system's exclusion RNL (GRS RNL parmlib
is unable to recover from this error.
member) is not the same as the one the global resource
serialization complex is using. In conjunction with this wait state, message ISG317W is
issued to the console.
6C This system's RESERVE conversion RNL (GRS RNL
parmlib member) is not the same as the one the global 9C During GRS Star initialization, the system was unable to
resource serialization complex is using. access the GRS lock structure (ISGLOCK).
70 This system encountered an unrecoverable software In conjunction with this wait state, message ISG342W is
error during global resource serialization queue merge issued to the console. The message describes what kind
processing. of access to the structure failed.
7C Global resource serialization address initialization failed. A0 During GRS processing, an unexpected error occurred in
A system service called to initialize one of its modules one of the GRS XCF exits. GRS is unable to recover
was not successful. from the failure. (Message ISG310W is issued to the
console.)
In conjunction with this wait state condition, message
ISG305W is issued to the console. This message identi- AC The top level global resource serialization task from
fies the service, the module and the non-zero return which all other task are anchored unexpectedly received
code passed back from the service. control at a point in its processing that should not occur
and is unable to recover.
80 Global resource serialization initialization failed. A critical
task terminated. In conjunction with this wait state, message ISG329W is
issued to the console.
In conjunction with this wait state condition. message
ISG306W is issued to the console. An error code in this BC During initialization of a star complex, global resource
message identifies the particular task that failed. serialization was not able to allocate the global resource
serialization lock structure due to insufficient storage on
84 Global resource serialization failed. The type of complex
the coupling facility or the policy size is too small for the
the system initialized is not compatible with the complex
minimum structure size needed.
currently active in the sysplex. A system IPLed with
GRS=START, JOIN or TRYJOIN, cannot join an existing In conjunction with this wait state, message ISG338W is
global resource serialization star complex. Similarly, issued to the console. This message identifies the name
when a system is IPLed with GRS=STAR, it cannot join of the structure causing the failure.
an existing global resource serialization ring complex. C0 An unexpected error occurred in one of the Global
If the system detected the error condition itself and resource serialization lock structure exits. Global
issued the wait state, message ISG307W is issued. resource serialization is unable to recover from this
error.
If the system partitioned out of the complex and was put
into a wait state as a result of action taken by an already In conjunction with this wait state, message ISG310W is
active system that detected the error, then message issued to the console. This message identifies the name
ISG307W is not issued. of the global resource serialization lock structure that
failed.
88 Global resource serialization invoked a system service
which did not successfully complete. Message ISG308W C4 During a rebuild of the global resource serialization lock
is issued, identifying the system service along with the structure detected damage to the global request queue
error return and reason code. on the system. Global resource serialization is not able
to continue using the original lock structure due to a
8A During system initialization, global resource serialization
structure failure or loss of connectivity.
was unable to access the global resource serialization
record on the sysplex couple dataset.
WSC-24 OS/390 V2R8.0 MVS System Codes
0A3 0A3
In conjunction with this wait state, message ISG309W is E8 During migration from a global resource serialization ring
issued to the console. to a star complex, global resource serialization queue
damage was detected. Global resource serialization is
C8 During a rebuild of the global resource serialization lock
not able to continue processing.
structure, global resource serialization received a
request to stop the rebuild. Global resource serialization In conjunction with this wait state, message ISG332I is
can not resume processing with the original global issued to the console.
resource serialization lock structure, due to a structure
EA The system attempted to IPL while global resource
failure or loss of connectivity.
serialization was migrating from a global resource serial-
In conjunction with this wait state, message ISG309W is ization ring to a star complex. The system cannot join
issued to the console. the complex during this processing.
CC During a rebuild of the global resource serialization lock In conjunction with this wait state, message ISG301W is
structure, sysplex failure management (SFM) determined issued to the console.
that this system should not disconnect from the struc-
EC During migration from a global resource serialization ring
ture. Global resource serialization partitioned the system
to a star complex, an unexpected error occurred.
from the sysplex to insure data integrity is maintained.
In conjunction with this wait state, message ISG304W is
In conjunction with this wait state, message ISG309W is
issued to the console.
issued to the console.
Source: Global resource serialization
D0 During a rebuild of the global resource serialization lock
structure, sysplex failure management (SFM) determined System Action: The system enters a non-restartable wait state.
that the original lock structure has better connectivity For reason codes X'26', X'58', and X'5C', the system writes a
than the new structure. Global resource serialization logrec error record and issues an SVC dump.
could not resume processing with the original lock struc- For reason codes X'64' through X'70', the system issues message
ture due to a loss of connectivity condition. Global ISG015I. The system may also issue message ISG183W.
resource serialization partitions the system from the
System Programmer Response: Do one of the following:
sysplex to insure data integrity is maintained.
To IPL a system without global resource serialization, IPL with
In conjunction with this wait state, message ISG309W is
COUPLE=00,GRS=NONE. The system will IPL in XCF-local
issued to the console.
mode. Do not start any jobs that access shared sysplex
D4 During a rebuild of the global resource serialization lock resources.
structure, global resource serialization was unable to
To IPL a system into the sysplex and the global resource serial-
connect to the new structure. Global resource serializa-
ization complex,
tion partitions the system from the sysplex to insure data
integrity is maintained. – If you want to IPL a global resource serialization ring
complex, correct the GRS= specification (in IEASYSxx
In conjunction with this wait state, message ISG309W is
parmlib member or in response to message IEA101A) to be
issued to the console.
one of the following:
D8 During a rebuild of the global resource serialization lock
- START
structure, global resource serialization received an unre-
coverable response from a XES service. Global resource - JOIN
serialization is not able to continue processing.
- TRYJOIN
In conjunction with this wait state, message ISG308W or
– If you want to IPL a global resource serialization star
ISG309W is issued to the console.
complex, check the following:
DC During a rebuild of the global resource serialization lock
1. The global resource serialization record was formatted
structure, global resource serialization received an unex-
on the sysplex couple data set via the IXCL1DSU for-
pected event, violating the rebuild protocol. Global
matting utility.
resource serialization is not able to continue.
2. The sysplex couple data set with the global resource
In conjunction with this wait state, message ISG309W is
serialization record is the current primary sysplex
issued to the console.
couple data set.
E0 During a rebuild of the global resource serialization lock
To resolve the problem preventing the system from joining
structure, global resource serialization stopped for an
global resource serialization, do the following:
unknown reason. Global resource serialization is not
able to continue processing See the explanations for accompanying messages for informa-
tion about the problem.
In conjunction with this wait state, message ISG309W is
issued to the console. Obtain the SVC dump, if one was issued, and format it with the
IPCS VERBEXIT MTRACE command to find the last message
E4 During migration from a global resource serialization ring
global resource serialization issued. See the explanation for any
to a star complex, a structure error occurred. Global
message found.
resource serialization is not able to continue processing.
If you cannot find the problem, or the problem persists, search
In conjunction with this wait state, message ISG309W is
problem reporting databases for a fix for the problem. If no fix
issued to the console.
exists, contact the IBM Support Center. Provide the logrec error
record and the SVC dump if they were issued.
Wait State Codes WSC-25
0A4 0A5
083 The indicated UIM specified a device number greater
0A4
than the maximum allowed device number.
Explanation: Two or more processors could not complete external
Message reason code 1: Device number in the relo-
time reference (ETR) synchronization check processing. ETR is the
cation information is greater than the maximum
MVS generic name for the IBM Sysplex Timer (9037) or equivalent.
allowed device number.
Source: Timer supervision
Message reason code 2: Device number in the
System Action: The system enters wait state X'0A4'. This wait device class extension area is greater than the
state is accompanied by message IEA503W. maximum allowed device number.
Operator Response: Retain the logrec error records. Contact hard- The indicated UIM is flagged as in error.
ware support.
084 The indicated UIM specified an non-valid device class in
the DFPTBYT3 field. The indicated UIM is flagged as in
0A5 error.
Explanation: The system detected a logic error in one of the hard- 085 The DCT information specified for a DASD does not
ware configuration definition (HCD) modules. match the previously specified information for this DASD
Bits 36 to 47 of the wait state program status word (PSW) contain a type.
hexadecimal reason code. This reason code is the same as the 086 A UIM specified a DCT entry length greater than the
message identifier of the HCD message that accompanies the wait allowed maximum.
state code:
087 Insufficient space in DCT for current DCT entry.
Code Explanation
088 The indicated UIM tried to build a CIT by passing a CIP
070 Two UIMs made multiple attempts to build a GIT. The that does not specify an attachable device list.
first UIM is flagged as in error.
091 The indicated generic name as specified in the list of
071 Two UIMs specified the same generic preference value. compatible generics could not be found in the list of
The last UIM is flagged as in error. GITs. The first indicated generic is deleted from the list
072 A UIM defines a generic device type with a compatible of compatible generics. The UIM is flagged as in error.
list that contains duplicate entries. Source: Hardware configuration definition (HCD)
073 Two UIMs made multiple attempts to build a CIT for the System Action: The system enters wait state X'0A5'. The system
indicated control unit. The first UIM is flagged as in error. issues the following hardware configuration definition (HCD) mes-
074 A UIM specified an non-valid device number in DFP. sages with the following wait state reason codes:
Message reason code 1: The device number in the Code Accompanying Message
DFP is greater than the maximum allowed device 070 CBDA070I, to display the UIM name and the generic
number. name.
Message reason code 2: A DFT exists already for 071 CBDA071I, to display the UIM name and the generic
the device number specified in the DFP. names.
075 A UIM specified either in the DFP or UIP a generic 072 CBDA072I, to display the UIM name and the generic
name for which the GIT could not be found. The indi- name.
cated UIM is flagged as in error.
073 CBDA073I, to display the UIM name and the control unit
076 The indicated UIM specified more than 5 MLT names or type/model.
specified no MLT names. The indicated UIM is flagged
074 CBDA074I, to display the UIM name, device number,
as in error.
and reason code.
077 The indicated UIM specified more than the 256 bytes of
075 CBDA075I, to display the UIM name and the DFP or
device-dependent information. The indicated UIM is
UIP, as applicable.
flagged as in error.
076 CBDA076I, to display the UIM name.
078 The indicated UIM specified an non-valid UCB segment
type for an ACON position pointer. The indicated UIM is 077 CBDA077I, to display the UIM name.
flagged as in error. 078 CBDA078I, to display the UIM name and UCB segment
079 The indicated UIM specified an non-valid UCB segment type.
type for an ACON relocation pointer. The indicated UIM 079 CBDA079I, to display the UIM name and the UCB
is flagged as in error. segment type.
080 The indicated UIM specified an offset for an ACON posi- 080 CBDA080I, to display the UIM name.
tion pointer that is not within the specified UCB segment.
The indicated UIM is flagged as in error. 081 CBDA081I, to display the UIM names and the device
type/model.
081 Two UIMs made multiple attempts to build a UIT for the
indicated device. The first UIM is flagged as in error. 082 CBDA082I, to display the UIM name.
082 The indicated UIM specified more than 24 bytes of 083 CBDA083I, to display the UIM name, device number,
device-dependent segment data. The indicated UIM is and reason code.
flagged as in error. 084 CBDA084I, to display the UIM name, device number,
and Ucbtype3.
WSC-26 OS/390 V2R8.0 MVS System Codes
0A7 0B1
085 CBDA085I, to display the DASD type.
0B1
086 CBDA086I, to display the UIM name.
Explanation: System initialization cannot continue because of a
087 CBDA087I. problem in the LOADxx parmlib member, the I/O definition file (IODF)
088 CBDA088I, to display the UIM name and control unit data set, or a device.
type/model. Bits 32 through 43 of the wait state program status word (PSW)
091 CBDA091I, to display the generic names. contain one of the following reason codes:
Operator Response: Notify the system programmer. If requested Code Explanation
by the system programmer, obtain a stand-alone dump. 00A The IODF is not valid for IPL. It must be a VSAM
System Programmer Response: Search problem reporting data- dataset.
bases for a fix for the problem. Use the following search argument: 001 The required data set was not found.
WS/D0A5: Wait state code 002 The IODF occupies more than one extent.
PRCS/hhhhhhhh: Reason code
003 A required device is not defined.
PIDS/name of UIM: Program name
VALU/Ccccccccc: Message variable text 004 MSCH instruction failed for a required device.
If no fix exists, ask the operator to obtain the stand-alone dump. 005 The IODF is not valid for an IPL.
Contact the IBM Support Center. Provide the stand-alone dump, the 006 The IODF did not contain an operating system configura-
UIM name, if available, and the accompanying message. tion definition matching the configuration ID specified in
the LOADxx member.
0A7
007 The IODF is not valid for an IPL. The configuration ID
Explanation: There is insufficient Extended System Queue Area was blank in LOADxx, but there was more than one
(ESQA) or Extended Common Storage Area (ECSA) storage avail- operating system configuration definition. If the config-
able to build the Eligible Device Table (EDT) during the Nucleus uration ID is blank, then IPL will use a single-defined
Initialization Program (NIP). operating system configuration definition as the default.
Source: Allocation Build EDT Resource Initialization Module (RIM) 008 The IODF suffix is not valid.
IEAVNP88.
009 The IODF data set name high level qualifier is not valid.
System Action: The system enters a non-restartable Wait State.
00A The IODF is not valid for an IPL. It must be a VSAM
Operator Response: Notify the System Programmer. dataset.
System Programmer Response: Increase the ESQA and ECSA 00B Equals ('==') were specified as the IODF suffix or equals
storage size specifications on the SQA and CSA parameters in the ('========') were specified as the IODF high-level qual-
appropriate IEASYSxx member(s) and re-IPL. ifier in the member and the configuration hardware token
was not able to be obtained from the Hardware System
0B0 Area (HSA), the IODF suffix found in the hardware token
did not contain a valid hexadecimal number or the char-
Explanation: The system could not recognize the I/O definition file
acters 'IODF' were not found in the token.
(IODF) specified in the LOADxx parmlib member.
Note: If equals ('========') were specified as the IODF high-level
Note: If equals ('==') were specified as the IODF suffix in the
qualifier in the LOADxxparmlib member, MVS uses the high-
LOADxx parmlib member, MVS uses the IODF suffix
level qualifier obtained from the the hardware token in the
obtained from the hardware token in the Hardware System
HSA. If the characters 'IODF' are not found, or the IODF
Area (HSA). If equals ('========') were specified as the
suffix is not X'00' to X'FF', MVS will load wait state X'0B1'
IODF high-level qualifier in the LOADxx parmlib member,
reason code X'00B'. MVS uses the same rules for deter-
MVS uses the high-level qualifier obtained from the the hard-
mining its ability to use the IODF name explicitly specified in
ware token in the HSA. If the characters 'IODF' are not
LOADxx.
found, or the IODF suffix is not X'00' to X'FF', MVS will
load wait state X'0B1' reason code X'00B'. MVS uses the Source: Input/Output supervisor (IOS)
same rules for determining its ability to use the IODF name System Action: The system enters nonrestartable wait state
explicitly specified in LOADxx. X'0B1'. The system issues the following messages with the fol-
Bits 32-43 of the wait state program status word (PSW) contain one lowing wait state reason codes:
of the following reason codes: Code Accompanying Message
Code Explanation 00A IEA517W.
001 The input/output supervisor (IOS) section of the IODF is 001 IEA513W.
not compatible with the system code.
002 IEA514W.
002 The allocation section of the IODF is not compatible with
the system code. 003 IEA515W, to display the device number.
Source: Input/output supervisor (IOS) 004 IEA516W, to display the device number.
System Action: The system enters nonrestartable wait state 005 IEA517W.
X'0B0'. 006 IEA518W.
System Programmer Response: Enter the correct IODF data set 007 None.
name in the LOADxx parmlib member. Ask the operator to reIPL the
system.
Wait State Codes WSC-27
0B2 0B3
008 None. 006 Change the LOADxx member to specify another IODF or
the correct operation system configuration ID.
009 None.
007 Specify the correct operating system configuration identi-
00A IEA517W.
fier.
00B IEA511W.
008 Correct the suffix to be within the range X'00' to X'FF'.
To view any accompanying message, perform the following:
009 Start the high level qualifier in column 13.
Using the hardware ALTER/DISPLAY facility, display the
00A Change the Loadxx member to specify another IODF.
address at location X'14' in central storage. This address points
Be sure to specify the name of a VSAM data set
to the IPL diagnostics area. Primary Real Storage must be dis-
(instead of a sequential or partitioned data set).
played to find the IPL diagnostic area.
00B Change the Loadxx member to specify another IODF.
Add X'28' to the address of the IPL diagnostic area and display
Be sure to specify the name of a production-IODF or
the resulting location in central storage. This location contains
specify pluses ('++'), minuses ('--'), blanks (' ') or aster-
the 31-bit virtual address of the IPL vector table (IVT). Hence-
isks ('**') and let the system locate a valid IODF. If
forth, all addresses are 31-bit virtual. Primary Real Storage must
equals ('========') were specified as the high-level
be displayed to find the IPL diagnostic area.
qualifier, specify the high-level qualifier of a
Add X'E0' to the IVT address. The result is the address of the production-IODF.
IVTMQHP field. IVTMQHP contains the address of the message
In each case, ask the operator to reIPL the system.
queue header (MQH). Primary Real Storage must be displayed
to find the IPL diagnostic area. System Programmer Response: If the problem persists, search
problem reporting databases for a fix for the problem. Provide the
MQH+X'0' contains the address of the oldest message queue
following search argument:
element (MQE) available. The message text for the oldest MQE
begins at MQE+X'8'. WS/D0B1: Wait state code
Use MQE+X'0' of the oldest MQE to find the MQE of the next PRCS/rrrrrrrr: Reason code
oldest message. Again, the message text for this MQE begins at
MS/IEAnnnW: Message identifier
MQE+X'8'.
If no fix exists, ask the operator to obtain the stand-alone dump.
Repeat this sequence (using MQE+X'0' of the current MQE to
Contact the IBM Support Center. Provide the stand-alone dump, the
locate the next MQE), until the message text for the appropriate
accompanying message, and the reason code.
IEA51xW message is displayed.
Operator Response: Device numbers are four digits in length. 0B2
ReIPL and run the job again. Set LOAD parameter to the device
number of the device that contains or SYS1.PARMLIB. Device Explanation: No devices were defined in the I/O definition file
numbers can be four digits in length, ReIPL. Notify the system pro- (IODF).
grammer. Source: Hardware configuration definition (HCD)
System Programmer Response: Depending on the reason code, System Action: The system enters nonrestartable wait state
one of the following: X'0B2'. The system may issue message IEA523W.
Code Action System Programmer Response: See the explanation for message
00A Change the LOADxx member to specify another IODF. IEA523W. Verify that the IODF contains devices that are defined to
Be sure to specify the name of a VSAM data set MVS. Verify that the necessary UIMs supporting these devices are
(instead of a sequential or partitioned data set). present in SYS1.NUCLEUS. If the problem persists, search problem
reporting databases for a fix for the problem. If no fix exists, ask the
001 Verify that the correct device number was specified on operator to obtain the stand-alone dump. Contact the IBM Support
the LOAD parameter. Verify that the IODF resides on Center. Provide the stand-alone dump and the accompanying
the same volume as SYSn.IPLPARM or message.
SYS1.PARMLIB. Enter the correct IODF data set name
in the LOADxx parmlib member.
0B3
002 Ensure that the IODF data set is allocated as a single
Explanation: Initial program load (IPL), found incorrect information
extent data set.
in the LOAD parameter. The first four characters of the LOAD
003 Load device does not have the proper subchannel identi- parameters should contain the device number of the direct access
fier. Verify that the device on which the IODF resides is storage device (DASD) volume containing the SYS1.PARMLIB data
defined. Verify that the correct device number was speci- set. The value specified in the LOAD parameter is not a valid device
fied on the LOAD parameter. Verify that the hardware number.
configuration matches the definitions in the IODF.
Source: Initial program load (IPL)
004 Move any of the following data sets (that are on the
System Action: The system enters a non-restartable wait state.
device specified on the LOAD parameter) to a different
device: Operator Response: Check the LOAD parameter on the hardware
frame you used to IPL the system. The first four characters are sup-
IODF
posed to be hexadecimal digits (0 through 9, A through F) that form
SYS1.PARMLIB the device number where the IODF resides. For three digit device
SYSn.IPLPARM numbers, add a leading zero so that all four characters are valid
hexadecimal digits.
005 Change the LOADxx member to specify another IODF.
Be sure to specify the name of a production-IODF.
WSC-28 OS/390 V2R8.0 MVS System Codes
0B4 102
If the value is incorrect, enter the correct value and reIPL the
0E3
system. If the value is correct, record the contents of the LOAD
parameter, and notify the system programmer. Explanation: There is not enough virtual storage available to ini-
tialize the common service area (CSA).
System Programmer Response: If the LOAD parameter specifies
the correct four digit hexadecimal device number and the problem Source: Virtual storage management (VSM)
persists, search problem reporting databases for a fix for the System Action: The system may issue message IEA140W. The
problem. If no fix exists, contact the IBM Support Center. system enters wait state X'0E3'.
Operator Response: Notify the system programmer.
0B4
System Programmer Response: Modify the virtual storage allo-
Explanation: A unit information module (UIM) specified an unde-
cated to the nucleus, system queue area (SQA), or link pack areas
fined device number.
(LPA).
Source: Input/output supervisor (IOS)
System Action: The system issues message IEA525W to identify 0E8
the UIM in error. The system enters nonrestartable wait state Explanation: During nucleus initialization program (NIP) proc-
X'0B4'. essing, the machine check handler (MCH) resource initialization
System Programmer Response: See message IEA525W for the module (RIM) failed. Bits 36-51 of the wait state program status word
name of the failing UIM. Check if the failing UIM is an installation- (PSW) contain a reason code, as follows:
provided or IBM-provided UIM. If it is an IBM-provided UIM, search Code Explanation
problem reporting databases for a fix for the problem. Provide the
following search argument: 81rr A request to allocate MCH control blocks returned
nonzero return code rr.
WS/D0B4: Wait state code
MS/IEA525W: Message identifier 82rr A request to initialize the control registers returned
VAlu/Cuim_name: Message variable text nonzero return code rr.
If no fix exists, ask the operator to obtain the stand-alone dump. 83rr A request for virtual storage returned nonzero return
contact the IBM Support Center. Provide the stand-alone dump. code rr.
Source: Machine check handler (MCH)
0E0 System Action: The system enters nonrestartable wait state
Explanation: During nucleus initialization program (NIP) proc- X'0E8'.
essing, the system could not signal an online processor to update Operator Response: Record the wait state PSW. Notify the system
control register 14. programmer. ReIPL the system.
Source: Supervisor control If the system programmer requests it, obtain a stand-alone dump.
System Action: The system sends messages about the job to one System Programmer Response: Search problem reporting data-
of the following: bases for a fix for the problem. If no fix exists, contact the IBM
The primary console. Support Center. Provide the stand-alone dump.
The remote console, for a system with remote consoles.
101
The hard-copy log for a system with multiple console support
(MCS). Explanation: A program running in supervisor state tried to obtain
more storage from the system queue area (SQA) than was available.
The system enters a nonrestartable wait state.
Source: Virtual storage management (VSM)
Operator Response: This is probably a hardware error. Try to
reIPL the system. System Action: The system may issue message IEA946W. The
system enters wait state X'101'.
If the problem persists, switch to uniprocessor mode and reIPL the
system. Then try to vary the other processor online. If necessary, Operator Response: ReIPL the system. If this code occurs fre-
contact hardware support. quently, notify the system programmer.
System Programmer Response: Increase the space allowed for
0E1 the SQA, or specify more space for the SQA in response to
message IEA101A at the next system initialization.
Explanation: The SIGP STOP command was entered to stop a
processor. The request failed because the processor is not opera-
tional. 102
Source: Loadwait/Restart Explanation: During processing for a GETMAIN macro for a
program running in supervisor state, an error occurred. More pages
System Action: The system ends command processing and loads of central storage were requested for the system queue area (SQA)
wait state X'0E1'. than were available.
Operator Response: Enter the command again. If the problem Source: Virtual storage management (VSM)
recurs, contact hardware support.
System Action: The system may issue message IEA946W. The
system enters wait state X'102'.
Operator Response: ReIPL the system. If this code occurs fre-
quently, notify the system programmer.
Wait State Codes WSC-29
104 110
System Programmer Response: Increase the fixed central storage 06 The system tries to recover the control unit. If recovery
requirements for the system. is successful, the system:
Issues message IOS208I
104
Leaves the device paths online for all devices on
Explanation: While the system was processing the Supervisor Call the same control unit
(SVC) instruction for an ABEND macro, a program check occurred
Clears the pending status of the cleared device
recursively.
If recovery is not successful, the system issues message
Source: Supervisor control
IOS207I.
System Action: The system writes a logrec data set error record.
Operator Response: Do the following:
The system may issue message IEA740W. The system loads the
X'104' wait state PSW. 1. Enter ‘SETLP lpname’ to locate the device number of the hot
device. lpname is the name of the system that entered the disa-
Operator Response: If the system programmer requests a stand-
bled wait state.
alone dump, obtain one. ReIPL the system.
2. At the system console, enter the F ALTCP command to display
System Programmer Response: Search problem reporting data-
the ALTER/DISPLAY frame.
bases for a fix for the problem. If no fix exists, ask the operator to
obtain a stand-alone dump. Contact the IBM Support Center. Provide 3. When the system displays the ALTCP frame, enter the number
the stand-alone dump and the logrec data set error record. of the processor that detected the hot I/O.
4. Enter A2 B2 to display central storage.
110
5. Enter 40C, the address of the status collection data (SCD) area,
Explanation: The system detected a hot I/O condition on a device at the following prompt:
other than a direct access storage device (DASD). Address(hex) = >
Source: Input/output supervisor (IOS) 6. Record the first 4 bytes of data at storage location X'40C'.
System Action: The system leaves the device status pending and 7. Enter the data found at location X'40C' at the following prompt:
issues message IOS110D. Depending on the recovery code entered
by the operator, the system does the following: Address(hex) = >
Response System Action The system displays the contents of the SCD area:
01 The system clears the device status. The device remains Offset 0 The control block identifier of the SCD.
online. The system does not attempt channel path Offset 4 The device number.
recovery. Processing continues.
Offset 6 The channel path identifier.
02 or 03 The system boxes the device, as follows:
8. Contact hardware support.
The I/O on the device is ended.
9. To display location X'30E' in the prefixed save area (PSA),
Any new I/O requests result in permanent I/O errors. enter 30E at the following prompt:
The system does not perform new allocations for Address(hex) = >
the device. 10. Stop all processors by pressing ALT-STOP on the system
If the device was online, the system marks it console.
pending offline. A pending offline device goes offline 11. Enter A1 B3 on the command line.
when the following conditions occur, in this order:
12. Move the cursor to location X'30E' in storage. Enter one of the
1. The device is no longer allocated to any job. following recovery codes:
2. Allocation processing allocates any device in Code Explanation
the system.
01 Do not attempt channel path recovery.
If the device was offline, it remains offline.
02 Box the device.
04 The system tries to recover the channel path. If channel
path recovery is successful, the system: 03 Allow the operator to store the device number of
each device on the control unit in the operator reply
Issues message IOS203I area for IOS110D.
Leaves the channel path online
Clears the pending status of the hot device 04 Try to recover the channel path.
If channel path recovery is not successful, the system 05 Force the channel path offline.
issues message IOS202I and forces the channel path 06 Try to recover the control unit.
offline.
13. Start all processors.
05 The system forces the channel path offline. The system
14. Enter RESTART CPn to restart the waiting processor.
issues message IOS202I.
WSC-30 OS/390 V2R8.0 MVS System Codes
111 112
7. Enter the data found at location X'40C' at the following prompt:
111
Address(hex) = >
Explanation: The system detected a hot I/O condition on a direct
access storage device (DASD). The system displays the contents of the SCD area:
Source: Input/output supervisor (IOS) Offset 0 The control block identifier of the SCD.
System Action: The system leaves the device status pending and Offset 4 The device number.
issues message IOS111D. Depending on the recovery code entered Offset 6 The channel path identifier.
by the operator, the system does the following:
8. Contact hardware support.
Code Response
9. To display location X'30E' in the prefixed save area (PSA),
01 The system clears the device status. The device remains enter 30E at the following prompt:
online. The system does not attempt channel path
Address(hex) = >
recovery. Processing continues.
10. Stop all processors by pressing ALT-STOP on the system
02 or 03 The system boxes the device, as follows:
console.
The I/O on the device is ended.
11. Enter A1 B3 on the command line.
Any new I/O requests result in permanent I/O errors.
12. Move the cursor to location X'30E' in storage. Enter one of the
The system does not perform new allocations for following recovery codes:
the device.
Code Explanation
If the device was online, the system marks it
01 Do not attempt channel path recovery.
pending offline. A pending offline device goes offline
when the following conditions occur, in this order: 02 Box the device.
1. The device is no longer allocated to any job. 03 Allow the operator to store the device number of
each device on the control unit in the operator reply
2. Allocation processing allocates any device in
area.
the system.
04 Try to recover the channel path.
If the device was offline, it remains offline.
05 Force the channel path offline.
04 The system tries to recover the channel path. If channel
path recovery is successful, the system: 06 Try to recover the control unit.
Issues message IOS203I 13. Start all processors.
Leaves the channel path online 14. Enter RESTART CPn to restart the waiting processor.
Clears the pending status of the hot device
If channel path recovery is not successful, the system 112
issues message IOS202I and forces the channel path
Explanation: The system detected a hot I/O condition on a
offline.
reserved direct access storage device (DASD).
05 The system forces the channel path offline. The system
Source: Input/output supervisor (IOS)
issues message IOS202I.
System Action: The system leaves the device status pending and
06 The system tries to recover the control unit. If recovery
issues message IOS112D. Depending on the recovery code entered
is successful, the system:
by the operator, one of the following:
Issues message IOS208I
Code Response
Leaves the device paths online for all devices on
01 The system clears the device status. The device remains
the same control unit
online. The system does not attempt channel path
Clears the pending status of the cleared device recovery. Processing continues.
If recovery is not successful, the system issues message 02 or 03 The system boxes the device:
IOS207I.
The I/O on the device is ended.
Operator Response: Do the following:
Any new I/O requests result in permanent I/O errors.
1. Enter ‘SETLP lpname’ to locate the device number of the hot
The system does not perform new allocations for
device. lpname is the name of the system that entered the disa-
the device.
bled wait state.
If the device was online, the system marks it
2. At the system console, enter the F ALTCP command to display
pending offline. A pending offline device goes offline
the ALTER/DISPLAY frame.
when the following conditions occur, in this order:
3. When the system displays the ALTCP frame, enter the number
1. The device is no longer allocated to any job.
of the processor that detected the hot I/O.
2. Allocation processing allocates any device in
4. Enter A2 B2 to display central storage.
the system.
5. Enter 40C, the address of the status collection data (SCD) area,
If the device was offline, it remains offline.
at the following prompt:
04 The system tries to recover the channel path. If channel
Address(hex) = >
path recovery is successful, the system:
6. Record the first 4 bytes of data at storage location X'40C'.
Issues message IOS203I
Wait State Codes WSC-31
113 114
Leaves the channel path online 14. Enter RESTART CPn to restart the waiting processor.
Clears the pending status of the hot device
113
If channel path recovery is not successful, the system
issues message IOS202I and forces the channel path Explanation: The system could not recover from an error that
offline. occurred while the system was performing channel path recovery.
05 The system forces the channel path offline. The system The system may have released reserved devices. Data may be lost
issues message IOS202I. or written over.
06 The system tries to recover the control unit. If recovery Source: Input/output supervisor (IOS)
is successful, the system: System Action: The system may issue message IOS113W. The
Issues message IOS208I system enters wait state X'113'.
Leaves the device paths online for all devices on The system issues message IOS113W.
the same control unit Operator Response: Do the following:
Clears the pending status of the cleared device Verify data sets.
If recovery is not successful, the system issues message Refer to installation procedures for diagnosing an error in
IOS207I. channel path recovery. If none exist, obtain a stand-alone dump
Operator Response: Do the following: and reIPL the system.
1. Enter ‘SETLP lpname’ to locate the device number of the hot Notify the system programmer.
device. lpname is the name of the system that entered the disa- System Programmer Response: Search problem reporting data-
bled wait state. bases for a fix for the problem. If no fix exists, contact the IBM
2. At the system console, enter the F ALTCP command to display Support Center. Provide the stand-alone dump.
the ALTER/DISPLAY frame.
3. When the system displays the ALTCP frame, enter the number 114
of the processor that detected the hot I/O. Explanation: A previous error required that the operator stop
4. Enter A2 B2 to display central storage. sharing processors. The system recovered from the error.
5. Enter 40C, the address of the status collection data (SCD) area, Bits 40-47 of the wait state program status word (PSW) contain one
at the following prompt: of the following reason codes:
Address(hex) = > Code Explanation
6. Record the first four bytes of data at storage location X'40C'. 01 Reserves are intact. The system successfully recovered
the reserved devices.
7. Enter the data found at location X'40C' at the following prompt:
02 Reserves are lost. The system forced one or more
Address(hex) = >
devices that are reserved for the system offline.
The system displays the contents of the SCD area:
Source: Input/output supervisor (IOS)
Offset 0 The control block identifier of the SCD.
System Action: The system enters wait state X'114' because it
Offset 4 The device number. could not issue message IOS201E. The system waits for the oper-
Offset 6 The channel path identifier. ator to restart the system.
8. Contact hardware support. Operator Response: Do the following:
9. To display location X'30E' in the prefixed save area (PSA), 1. Isolate the failing channel path for repair.
enter 30E at the following prompt: 2. Identify and recover failing tasks.
Address(hex) = > 3. If the reason code indicates that reserves are intact, do the
10. Stop all processors by pressing ALT-STOP on the system following:
console. a. Enter the IOACTION RESUME command for the device on
11. Enter A1 B3 on the command line. all other sharing systems if the device was stopped, or
restart any stopped systems, or vary the device back online.
12. Move the cursor to location X'30E' in storage. Enter one of the
Start the stopped processors by pressing the START key at
following recovery codes:
the system console of each sharing system or logical parti-
Code Explanation tion.
01 Do not attempt channel path recovery. b. Perform a system restart on the system that detected the
02 Box the device. stopped processor.
03 Allow the operator to store the device number of 4. If the reason code indicates that reserves are lost, do the
each device on the control unit in the operator reply following:
area. a. Enter the IOACTION RESUME command for the device on
04 Try to recover the channel path. all other sharing systems if the device was stopped, or
restart any stopped systems, or vary the device back online.
05 Force the channel path offline. Start the stopped processor by pressing the START key at
06 Try to recover the control unit. the system console of each sharing system or logical parti-
tion.
13. Start all processors.
WSC-32 OS/390 V2R8.0 MVS System Codes
115 202
b. Perform a system restart on the system that detected the
11A
stopped processor.
Explanation: The SVC 26 routine received a protection exception
c. Notify the system programmer.
when the routine tried to store into a user-supplied CAMLST work
area. The storage protection key of the work area did not match the
115 user's protection key.
Explanation: A direct access storage device (DASD) containing a Source: DFSMSdfp
page data set is unavailable for an I/O operation.
Programmer Response: Correct the pointer in the LOCATE
Location X'40C' in central storage points to an area that contains parameter list to the LOCATE work area, and execute the job step
the following: again.
Byte Contents System Programmer Response: If the error recurs and the
0-3 The number of bytes in the following area. 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
4-7 The wait state code.
problem. If no fix exists, contact the IBM Support Center. Provide the
8-15 The name of the module issuing wait state code X'015' JCL and the program listing for the job.
16-23 The time stamp.
201
24 The reason code. It is one of the following:
Explanation: A failure occurred when the system was trying to
Code Explanation
create the console communications task (COMMTASK) address
10 A permanent I/O error occurred when the space. This code is associated with message IEA366A.
system was reading the volume serial number
Bits 32 through 47 of the wait state PSW contain one of the following
for the specified device.
hexadecimal reason codes:
20 The device is not operational.
Code Explanation
40 Intervention is required for the specified
8001 or 8002 While the system was creating the console com-
device.
munications address space, a failure occurred.
80 The pack mounted does not contain the proper
Fccc An abend occurred. The completion code is ccc.
volume serial number for the device.
Source: Communications task (COMMTASK)
25 Zero.
Operator Response: Record the contents of the wait state PSW.
26-27 The device address.
Notify the system programmer. ReIPL the system.
28-29 The first 2 bytes of sense data.
System Programmer Response: If the reason code is Fccc, see
30-31 Zeros. the system programmer response for abend ccc.
32-35 The address of the complete sense data. If the reason code is 8xxx, search problem reporting databases for a
Source: Input/output supervisor (IOS) fix for the problem. If no fix exists, contact the IBM Support Center.
System Action: The system enters wait state X'115'.
202
Operator Response: Do the following:
Explanation: During system initialization, the system was initializing
1. Verify that the proper pack is mounted on the device specified. the address space to be used for console communications. Initializa-
Then ready the device. tion of the address space failed.
2. Restart the waiting processor. A hexadecimal reason code in field PSAWTCOD in the prefixed save
3. If the reason code indicates that the device is not operational, area (PSA) explains the error:
verify that the channel and the control unit are powered on and Code Explanation
properly connected.
00008001 Console communication could not establish a recovery
environment.
116
00008002 An error occurred when the system tried to load a
Explanation: During restart processing, the system found a missing module.
interruption for a paging device.
00008003 An error occurred during POST macro processing.
Storage location X'40C' contains the paging device number.
00008004 An error occurred during POST macro processing.
Source: Input/output supervisor (IOS)
00008005 An error occurred when the system updated the table in
System Action: The system enters wait state X'116'. the command address space.
Operator Response: Do the following: 0000Fccc An abend occurred. The completion code is ccc.
1. Check the paging device for hardware problems. Source: Communications task (COMMTASK)
2. Check control units and switching units for proper connections. System Action: The system enters restartable wait state X'202'.
3. Restart the waiting processor. The system may issue message IEA367A.
4. If you just mounted the device, enter a VARY DEVICE ONLINE Operator Response: Find the reason code as follows:
command to generate a simulated device end. 1. At the system console, invoke the ALTER/DISPLAY frame with:
'F ALTCP'
Wait State Codes WSC-33
204 A00
2. When the ALTCP frame is displayed, specify the number of a
5C7
central processor (CP) that is not in the load or disabled wait
state. Explanation: An error occurred during processor or system termi-
nation. A reason code appears in bits 36 through 51 of the wait-state
3. Enter:
PSW and explains the error:
'A2 B3' (Display Primary Virtual Storage)
Code Explanation
4. Enter:
0101 Three processors each attempted to load a wait state.
'4ðC' at 'Address(hex) = >' There is not enough storage available to support the
5. Print the frame or write down the contents of location X'40C' third request.
Report this reason code to the system programmer. 0201 Two concurrent wait state requests were in progress.
Invoke the restart function to restart the system. 8907 An error occurred during ACR processing.
System Programmer Response: Do the following: 9904 An error occurred while the system was processing a
1. Look at the explanation of message IEA367A, if issued. write to operator (WTO) to display a message and load
a system wait state.
2. Continue diagnosis according to the reason code:
9905 An error occurred in the processor stop routine.
For reason code X'0000F'ccc, see the description of the
abend code. 9906 The system could not start alternate CPU recovery
(ACR) on a target processor.
For reason code X'00008'xxx, search problem reporting
databases for a fix for the problem. If no fix exists, contact Source: Loadwait/Restart
the IBM Support Center. System Action: For reason code X'0101', the system rejects the
third request and loads temporary disabled wait state X'5C7' on one
204 processor. Then the system (all processors) enters the first success-
Explanation: During system initialization, the system found an eli- fully loaded wait state.
gible devices table (EDT) identifier specified in the LOADxx parmlib For reason code X'0201', the system rejects one of the requests
member that does not exist in the I/O definition file. and loads temporary disabled wait state X'5C7' on one processor.
Source: Allocation Then the system (all processors) enters the other requested wait
state.
System Action: The system enters a non-restartable wait state
X'204'. For all other reason codes, the system enters a non-restartable wait
state X'5C7'. For reason code X'9906', the system also issues
System Programmer Response: Check that the EDT identifier message BLW006W.
specified in LOADxx exists in the I/O definition file. ReIPL the
system. Operator Response: Notify the system programmer. If necessary,
obtain a stand-alone dump. ReIPL the system.
205 System Programmer Response: For reason code X'0101'and
X'0201', see the system programmer response for the wait state
Explanation: During nucleus initialization program (NIP) proc-
that the processor enters after wait state X'5C7'. For all other
essing, the system tried to load a module that was not in the data
reason codes, search problem reporting databases for a fix for the
set in the linklist (as defined by PROGxx or LNKLSTxx parmlib
problem. If no fix exists, contact the IBM Support Center.
members).
Source: Allocation A00
System Action: The system enters a non-restartable wait state Explanation: A dynamic address translation (DAT) error occurred
X'205'. for a system address space. The recovery termination manager
System Programmer Response: Search problem reporting data- (RTM) does not end the address space because the ASCBNOMT
bases for a fix for the problem. If no fix exists, contact the IBM and ASCBNOMD fields of the address space control block (ASCB)
Support Center. show that the MEMTERM option of the CALLRTM macro is not valid
for the address space. The address space is critical for system oper-
206 ation.
Explanation: During system initialization, a sysplex test datesource Source: Recovery termination manager (RTM)
partition specified OPERATOR PROMPT. System Action: The system may issue message IEA802W. The
Source: Timer supervision system enters the wait state.
System Action: The system enters a non-restartable wait state. Operator Response: If requested by the system programmer,
obtain the stand-alone dump. ReIPL the system.
Operator Response: Notify the system programmer.
System Programmer Response: Search problem reporting data-
System Programmer Response: Modify the CLOCKxx parmlib bases for a fix for the problem. If no fix exists, contact the IBM
member for the systplex datesource LPAR to specify OPERATOR Support Center. Provide the stand-alone dump.
NOPROMPT.
WSC-34 OS/390 V2R8.0 MVS System Codes
A01 A23
A01 A20
Explanation: One of the following hardware errors occurred on the Explanation: The system found a page in the fixed link pack area
only online processor: (FLPA) that is not fixed.
A predefined number of hard machine check interruptions Source: Real storage manager (RSM)
A hard machine check interruption from which the system System Action: The system enters wait state X'A20'. The system
cannot recover writes message IAR011W.
Source: Machine check handler (MCH) Operator Response: If requested by the system programmer,
obtain a stand-alone dump. Attempt to reIPL the system without the
System Action: The system enters wait state X'A01'.
FLPA.
Operator Response: To recover possible unrecorded machine
System Programmer Response: Search problem reporting data-
check error records, write a stand-alone dump. Contact hardware
bases for a fix for the problem. If no fix exists, collect a stand-alone
support.
dump from the operator and contact the IBM Support Center.
Provide the stand-alone dump.
A18
Explanation: The system received an unsolicited device end inter- A21
ruption for a volume containing a paging data set. Volume serial ver-
Explanation: The system attempted to page-protect a storage area.
ification failed for one or more of the following reasons:
The segment table entry (SGTE) for this area was incorrect. The
The device address contained a volume with a different volume error occurred in the modified link pack area (MLPA), the extended
serial number. pageable link pack area (PLPA), the fixed link pack area (FLPA), or
An I/O error occurred while attempting to read the volume label. the extended FLPA.
The device went from ready to not ready status when volume Source: Real storage manager (RSM)
verification attempted to read the volume label. System Action: The system enters wait state X'A21'. The system
Source: Input/output supervisor (IOS) issues message IAR012W.
System Action: The system enters wait state X'A18'. Operator Response: If requested by the system programmer,
obtain a stand-alone dump.
Operator Response: Do the following:
If the error occurred in MLPA, EXTENDED MLPA, BLDL, FLPA, or
1. Ensure that all volumes containing paging data sets are on the
EXTENDED FLPA, attempt to reIPL the system without this area. If
same device addresses as they were at system initialization.
the error occurred in MLPA or EXTENDED MLPA, try to reIPL the
2. Ensure that all devices are ready. system without the default page protection for this area. Use the
NOPROT option on the MLPA parameter.
3. Restart the waiting processor.
System Programmer Response: Search the problem reporting
A19 databases for a fix for the problem. If no fix exists, ask the operator
to obtain a stand-alone dump. Contact the IBM Support Center.
Explanation: The system can no longer perform I/O. Provide the dump.
Source: Input/output supervisor (IOS)
System Action: The system issues message IOS019W. The A22
system enters nonrestartable wait state X'A19'. Explanation: An error, such as a hot I/O condition in a multiproc-
Operator Response: Contact hardware support. essing configuration, caused the disabled 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
A1E
state.
Explanation: The only online time-of-day (TOD) clock failed. This
Source: Communications task (COMMTASK) or master scheduler
wait state is accompanied by message IEA274W.
System Action: The processor on which the DCCF is running waits
Source: Timer supervision
for responses to the messages that the DCCF sent to the console
System Action: The system enters wait state X'A1E'. with master authority, or the alternate or system console. When
Operator Response: Retain the logrec data set error records. message processing is complete, the system restarts the processors
Contact hardware support. that are in the X'A22' wait state.
Operator Response: Respond to DCCF messages.
A1F
Explanation: The processor controller is not available. Time-of-day A23
synchronization cannot occur. Explanation: A program check interruption occurred while the
Source: Timer supervision machine check handler was running on the only online processor. No
recovery was possible.
System Action: The system enters wait state X'A1F'.
Source: Machine check handler (MCH)
Operator Response: ReIPL the system.
System Action: The system issues message BLW006W. Proc-
essing continues on other processors.
Operator Response: To recover possible unrecorded machine
Wait State Codes WSC-35
A24 A70
check error records, write a stand-alone dump. Retain the dump.
A29
Contact hardware support.
Explanation: The system was stopping itself when a program or
A24 machine check occurred. While trying to recover from this program
or machine check, another program or machine check occurred. This
Explanation: The system detected a loop while the machine check problem is probably a software error.
handler was running on the only online processor. No recovery was
possible. Source: Loadwait/Restart
Source: Machine check handler (MCH) System Action: The system enters wait state X'A29'. Processing
continues on other processors in the sysplex.
System Action: The system issues message BLW006W. The
system enters wait state X'A24'. System Programmer Response: If the problem reporting data-
bases do not show a fix for the problem, contact the IBM Support
Operator Response: To recover possible unrecorded machine Center.
check error records, write a stand-alone dump. Contact hardware
support.
A2A
A26 Explanation: The system detected a page within the range of the
pageable link pack area (PLPA), extended PLPA, the modified link
Explanation: A machine check interruption occurred on the only pack area (MLPA), or the extended MLPA that was never paged into
online processor. The machine check interruption code associated auxiliary storage. Ranges of system storage that are page protected
with the interruption is incorrect. No recovery was possible. must have a copy on auxiliary storage so the system can refresh the
Source: Machine check handler (MCH) page if necessary.
System Action: The system issues message BLW006W. The Source: Real storage manager (RSM)
system enters wait state X'A26'. System Action: The system enters wait state X'A2A'.
Operator Response: To recover possible unrecorded machine Operator Response: If requested by the system programmer,
check error records, write a stand-alone dump. Retain the dump. obtain a stand-alone dump. Try to reIPL the system using the no-
Contact hardware support. protect option on the MLPA system parameter in the IEASYSxx
parmlib member. See the explanation of messages IAR012W and
A27 IEA928I for more information.
Explanation: One of the following occurred: System Programmer Response: Fix the MLPA parameter in the
A machine check interruption or a program check interruption IEASYSxx parmlib member so that the error does not recur. If the
occurred error does recur, search problem reporting databases for a fix for the
problem. If no fix exists, ask the operator to obtain a stand-alone
The processor issued a malfunction alert (MFA) and did not dump. Contact the IBM Support Center. Provide the dump.
enter or remain in check-stop state
The system simulated a malfunction alert when the operator A2B
replied alternate CPU recovery (ACR) to message IEE331A, but
Explanation: A hardware error exists in extended storage.
the processor did not enter or remain in check-stop state
Recovery is not possible.
Source: Loadwait/Restart
Source: Machine check handler (MCH)
System Action: The system enters wait state X'A27'. Processing
System Action: The system issues message IGF912W. The
continues on other processors in the sysplex.
system enters wait state X'A2B'.
Operator Response: To recover possible unrecorded error records,
Operator Response: ReIPL the system.
write a stand-alone dump. Retain the dump. Contact hardware
support.
A70
A28 Explanation: During system initialization, the console is unavail-
able, and the system could not deliver a write to operator with reply
Explanation: The DAT-off machine check handler (MCH) routine
(WTOR) or synchronous message.
(DAT is Dynamic Address Translation) cannot reach the DAT-on
MCH routine. This situation can arise when a second machine check Source: Communications task (COMMTASK)
occurs when the load program status word (LPSW) assembler System Action: The system issues message IEA548W. The
instruction gives control to the DAT-on MCH routine. system issues the first 8 lines of the text of the failing message. The
Source: Machine check handler (MCH) system enters wait state X'A70'.
System Action: The system enters wait state X'A28'. Operator Response: ReIPL when the console becomes available.
Operator Response: To recover possible unrecorded machine
check error records, request a stand-alone dump. Retain the dump.
Contact hardware support.
WSC-36 OS/390 V2R8.0 MVS System Codes
A71 B05
System Programmer Response: Search problem reporting data-
A71
bases for a fix. If no fix exists, contact the IBM Support Center.
Explanation: During initialization, the reconfiguration component
either could not complete initialization or could not establish a B01
recovery environment. The address portion of the program status
word (PSW) contains X'8xxrrA71', where rr is the reason code. Explanation: The 3203/3211 utility has completed normally.
The following reason codes explain the failure: Source: DFSMSdfp
Code Explanation Operator Response: Verify the printed image and restart the
system.
30 A reconfiguration module could not determine the cause
of error.
B02
32 A reconfiguration module could not establish a recovery
Explanation: This wait state code is issued by the 3203/3211
environment.
utility. A control statement is missing or out of order. The JOB and
33 A reconfiguration module could not be loaded. END control statements must be the first and last statements,
34 A reconfiguration module could not be called. respectively. The DFN, UCS, and FCB statements can be included in
any order.
35 A reconfiguration module could not obtain a message
buffer. Source: DFSMSdfp
99 A reconfiguration module could not initialize the IPLing Operator Response: Correct the control statement sequence,
processor. insert any missing statements, and rerun the program. If requested
by the system programmer, obtain a stand-alone dump.
Source: Reconfiguration
System Programmer Response: If the error recurs and the
System Action: The system loads a non-restartable wait state. program is not in error, search problem reporting databases for a fix
Operator Response: Notify the system programmer. 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 B03
Support Center. Explanation: This wait state code is issued by the 3203/3211
utility. The JOB statement is incorrect.
A7A Source: DFSMSdfp
Explanation: Initialization of the service processor interface (SPI) Operator Response: Correct the JOB statement and rerun the
failed. The reason code appears in the program status word (PSW). program. Have the 3203/3211 utility and control statements avail-
The address portion of the PSW contains X'8xxrrA7A', where rr is able. If requested by the system programmer, obtain a stand-alone
the reason code. The following reason codes explain the failure: dump.
Code Explanation System Programmer Response: If the error recurs and the
01 The service processor interface task could not be program is not in error, search problem reporting databases for a fix
attached. for the problem. If no fix exists, contact the IBM Support Center.
02 The recovery environment could not be established.
B04
04 The required service processor facilities are not installed.
Explanation: This wait state code is issued by the 3203/3211
06 The service processor is busy during system initializa-
utility. The DFN statement is incorrect.
tion.
Source: DFSMSdfp
07 A service processor malfunction occurred during system
initialization. Operator Response: Correct the DFN statement and rerun the
program. Have the 3203/3211 utility and control statements avail-
08 Service processor damage is detected during system
able. If requested by the system programmer, obtain a stand-alone
initialization.
dump.
09 Service processor interface component trace could not
System Programmer Response: If the error recurs and the
be initialized.
program is not in error, search problem reporting databases for a fix
0A The service processor interface could not load a module. for the problem. If no fix exists, contact the IBM Support Center.
0B The service processor interface could not obtain storage.
B05
0C, 0D, 0E, 0F An internal error occurred.
Explanation: This wait state code is issued by the 3203/3211
11 The enabled wait PSW was used for looping during a
utility. The UCS statement is incorrect.
disabled write to operator.
Source: DFSMSdfp
13 An internal error occurred.
Operator Response: Correct the UCS statement and rerun the
Source: Service processor interface
program. Have the 3203/3211 utility and control statements avail-
System Action: The system loads nonrestartable wait state able. If requested by the system programmer, obtain a stand-alone
X'A7A'. dump.
Operator Response: For reason code X'06', X'07', or X'08', System Programmer Response: If the error recurs and the
contact hardware support. For other reason codes, notify the system program is not in error, search problem reporting databases for a fix
programmer. for the problem. If no fix exists, contact the IBM Support Center.
Wait State Codes WSC-37
B06 B1B
B06 B12
Explanation: This wait state code is issued by the 3203/3211 Explanation: This wait state code is issued by the 3203/3211
utility. The FCB statement is incorrect. utility. The reader is not ready.
Source: DFSMSdfp Source: DFSMSdfp
Operator Response: Correct the FCB statement and rerun the Operator Response: Ready the reader and rerun the program.
program. Have the 3203/3211 utility and control statements avail-
able. If requested by the system programmer, obtain a stand-alone B13
dump.
Explanation: This wait state code is issued by the 3203/3211
System Programmer Response: If the error recurs and the utility. The reader is not ready.
program is not in error, search problem reporting databases for a fix
for the problem. If no fix exists, contact the IBM Support Center. Source: DFSMSdfp
Operator Response: If the error condition is not apparent, display
B07 location 3 for sense information. (An interpretation of sense bit set-
tings can be found in the component description book for the control
Explanation: This wait state code is issued by the 3203/3211
unit being used.) Correct the faulty condition and clear the reader
utility. The END statement is incorrect.
check. Rerun the program. If reader checks occur frequently, use a
Source: DFSMSdfp card guide to check for off-punched cards. If the cards are punched
correctly and are in good condition and read checks continue,
Operator Response: Correct the END statement and rerun the
contact your hardware support personnel.
program. Have the 3203/3211 utility and control statements avail-
able. If requested by the system programmer, obtain a stand-alone
dump. B14
System Programmer Response: If the error recurs and the Explanation: This wait state code is issued by the 3203/3211
program is not in error, search problem reporting databases for a fix utility. A reader channel error has occurred.
for the problem. If no fix exists, contact the IBM Support Center. Source: DFSMSdfp
Operator Response: Probable hardware error. Rerun the job.
B0A
Explanation: This wait state code is issued by the 3203/3211 B15
utility. An external interrupt has occurred.
Explanation: This wait state code is issued by the 3203/3211
Source: DFSMSdfp utility. No device end is indicated on the reader.
Operator Response: Rerun the program. Source: DFSMSdfp
Operator Response: Probable hardware error. Rerun the job.
B0B
Explanation: This wait state code is issued by the 3203/3211 B19
utility. A program check interrupt has occurred.
Explanation: This wait state code is issued by the 3203/3211
Source: DFSMSdfp utility. The printer is not online. This will occur when the printer's
Operator Response: Have the 3203/3211 utility and control state- control unit has no power, when the control unit has been switched
ments available. If requested by the system programmer, obtain a off the I/O interface, or when the control unit is not a part of the
stand-alone dump. system.
System Programmer Response: If the error recurs and the Source: DFSMSdfp
program is not in error, search problem reporting databases for a fix Operator Response: Ensure that the address of the printer speci-
for the problem. If no fix exists, contact the IBM Support Center. fied in the DFN statement is correct. Ensure that the control unit is
online, and rerun the job. If the error recurs, contact your hardware
B0C support personnel.
Explanation: This wait state code is issued by the 3203/3211
utility. A machine check interrupt has occurred. B1B
Source: DFSMSdfp Explanation: This wait state code is issued by the 3203/3211
utility. A unit check has occurred on the printer.
Operator Response: Execute the SEREP program and save the
output. Rerun the job. Source: DFSMSdfp
Operator Response: If the error condition is not apparent, display
B11 low storage location 2-7 for sense information. Correct the faulty con-
dition and rerun the job. If the problem recurs, contact your hardware
Explanation: This wait state code is issued by the 3203/3211
support personnel.
utility. The reader is not online. This will occur when the reader's
control unit has no power or when the control unit has been switched
off the I/O interface.
Source: DFSMSdfp
Operator Response: Put the specified control unit online and rerun
the program. If the error recurs, contact your hardware support per-
sonnel.
WSC-38 OS/390 V2R8.0 MVS System Codes
B1C D0D
B1C B24
Explanation: This wait state code is issued by the 3203/3211 Explanation: During processing of the stand-alone version of the
utility. A printer channel error has occurred. input/output configuration program (IOCP), IOCP encountered an
error in the hardware processor controller and cannot communicate
Source: DFSMSdfp
with the IOCP operator.
Operator Response: Probable hardware error. Rerun the job.
Source: Input/output configuration program (IOCP)
B1D Operator Response: Notify the system programmer.
Explanation: This wait state code is issued by the 3203/3211 System Programmer Response: Search problem reporting data-
utility. No device end is indicated on the printer. bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Provide all printed output and output data sets
Source: DFSMSdfp related to the problem.
Operator Response: Probable hardware error. Rerun the job. If the
error recurs, contact your hardware support personnel. CCC
Explanation: When the system runs the QUIESCE function, the
B20 system is placed in restartable wait state X'CCC'.
Explanation: The operator running the stand-alone version of the Source: Loadwait/Restart
input/output configuration program (IOCP) has ended IOCP.
System Action: The system issues message BLW002I before
Source: Input/output configuration program (IOCP) entering wait state X'CCC'.
Operator Response: Notify the system programmer. Operator Response: Perform the restart function on the waiting
System Programmer Response: Search problem reporting data- processor, when you want the system out of QUIESCE.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. D0D
Explanation: System management facilities (SMF) encountered a
B21 resource shortage.
Explanation: A program check interruption has occurred during Code Explanation
processing of the stand-alone version of the input/output configura-
tion program (IOCP). 00 This reason code is associated with message IEE987E.
No SMF buffer space is available. SMF has used up all
Source: Input/output configuration program (IOCP) the available storage for its internal buffers and has
Operator Response: Notify the system programmer. stopped the system, as requested by the
NOBUFFS(HALT) in the SMFPRMxx parmlib member.
System Programmer Response: Search problem reporting data-
bases for a fix for the problem. If no fix exists, contact the IBM 01 This reason code is associated with message IEE988E.
Support Center. Provide all printed output and output data sets No SMF data sets are available. SMF has used up all
related to the problem. the available data sets for its data. SMF stopped the
system, as requested by the LASTDS(HALT) in the
B22 SMFPRMxx parmlib member.
Explanation: A machine check interruption has occurred during Source: System Management Facilities (SMF)
processing of the stand-alone version of the input/output configura- System Action: SMF enters restartable wait state X'D0D'.
tion program (IOCP).
Operator Response: Respond as indicated for the specific reason
Source: Input/output configuration program (IOCP) code:
Operator Response: Notify the system programmer. Code Response
System Programmer Response: Search problem reporting data- 00 Do one of the following:
bases for a fix for the problem. If no fix exists, contact the IBM
Press the restart button to restart the system and
Support Center. Provide all printed output and output data sets
operate in the ‘data lost’ mode.
related to the problem.
ReIPL the system.
B23 If you do restart the system, request a dump of the
SMF address space.
Explanation: An unrecoverable I/O error has occurred during proc-
essing of the stand-alone version of the input/output configuration 01 Do one of the following:
program (IOCP). Press the restart button to restart the system.
Source: Input/output configuration program (IOCP) ReIPL the system using the SMF=xx parameter to
Operator Response: Notify the system programmer. provide empty SMF data sets for SMF recording.
System Programmer Response: Search problem reporting data- If you do restart the system, SMF will start buffering
bases for a fix for the problem. If no fix exists, contact the IBM data until a data set becomes available. If no data
Support Center. Provide all printed output and output data sets sets become available, the system will eventually
related to the problem. use up all available storage for its internal buffers
and generate wait state code D0D, reason code 00.
Wait State Codes WSC-39
E02 FF0 through FFE
System Programmer Response: Use the IPCS SMFDATA sub- System Programmer Response: Search problem reporting data-
command to retrieve the data that was in the SMF buffers at the time bases for a fix for the problem. If no fix exists, contact the IBM
of the error. Support Center.
E02 FF0 through FFE
Explanation: While the system was using the IBM 2250 Display Explanation: Non-IBM programs can use wait state codes X'FF0'
Unit as the primary console, a permanent I/O error occurred. At the through X'FFE'.
time the error occurred, no alternate console was available.
Source: Non-IBM
Source: Communications task (COMMTASK)
Operator Response: See installation-supplied information for these
System Action: The system places the sense bytes in the 2 high- codes.
order bytes of register 15 and the status bytes in the 2 low-order
System Programmer Response: See installation-supplied informa-
bytes of register 15. Then the system enters wait state X'E02'.
tion for these codes.
Operator Response: If an alternate console is available, reIPL the
system, using the alternate console. If an alternate console is not
available, contact the system programmer.
WSC-40 OS/390 V2R8.0 MVS System Codes
System Completion Code to Module Table
This table correlates system completion codes with module If the system completion code you require does not appear in
numbers. For each system completion code, the associated the table, contact the IBM Support Center. Provide the
component and detecting module are listed. system completion code.
Reason Reason
Code Code Associated Detecting Code Code Associated Detecting
(Hex) (Hex) Component Module (Hex) (Hex) Component Module
00B Scheduler IEFXBCHK 01D RSM IARCA
restart IEFXBDYS IARCD
IEFXBGDG IARCF
IEFXBRDC IARCI
IEFXBSJX IARCL
IEFXBSWA IARCR
IEFXBSWB IARCS
IEFXBUSJ IARCV
IARCW
00C 16xx00xx XCF IXCA3ARP
IARCX
IXCA3ASE
IARCZ
IXCA3ASS
IARDD
IXCA3CKW
IARDK
IXCA3ECU
IARDM
IXCA3ERS
IARDO
IXCA3EV
IARDP
IXCA3MST
IARDR
IXCA3FAI
IARDS
IXCA3GAP
IARDT
IXCA3INT
IARDU
IXCA3IOX
IARFF
IXCA3IO2
IARSO
IXCA3IO3
IARXG
IXCA3IO6
IXCA3MSI 022 Vector proc- IGTDSR
IXCA3PCC essing
IXCA3PCT
023 CSV CSVLLBLD
IXCA3REG
CSVLLCPY
IXCA3RGT
CSVLLDCL
IXCA3RPR
CSVLLDSB
IXCA3SAP
CSVLLDYN
IXCA3SG0
CSVLLEXT
IXCA3SJT
CSVLLINF
IXCA3TOP
CSVLLIN2
IXCA3WPD
CSVLLPRS
IXCA3XRP
CSVLLREF
IXCM2TMR
CSVLLSCH
00D 01 02 03 CTRACE ITTCT CSVLLSTA
04 05 101 CSVLLSTC
102 CSVLLST2
CSVLLTRC
012 Timer super- IEATTUSD
vision 025 Initiator IEFSD161
IEFIB600
ILRSWAP
Copyright IBM Corp. 1988, 1999 CMT-1
Reason Reason
Code Code Associated Detecting Code Code Associated Detecting
(Hex) (Hex) Component Module (Hex) (Hex) Component Module
028 ASM IARCE 04E DFP
IARDO
04F DFP DSNWDSDM
IARDP
DSNWSDWA
IARDX
DSNYESWE
IARFA
DSN3RDMP
IARFP
DSN3RDMP
IARFS
DSN3RDMP
IARFZ
DSN3RDMP
IARMA
DSN3RDMP
IARPF
IARPM 051 TSO/E
IARPU
052 PC/AUTH IEAVXLRE
IARPX
IARSR 053 PC/AUTH IEAVXLRE
IARYA 054 SJF IEFSJBLD
IARXV IEFSJDEF
029 ASM ILRPOS IEFSJDEL
IEFSJFND
02C JES2 HASPFSSM
IEFSJJDV
HASPWARM
IEFSJEXT
02E AVM AVFGB IEFSJGET
AVFGR IEFSJIRT
AVFIC IEFSJPUT
AVFIW IEFSJRET
AVFJB IEFSJUPD
AVFKO IEFSJVAL
AVFKP IEFSJWRT
AVFKS IEFSJINT
AVFLA
055 30 34 36 ENF IEFENFNM
AVFLR
40 52 IEAVNP47
AVFLT
AVFMB 058 00 04 08 Supervisor IEAVECMS
AVFMC 0C 10 28 control
AVFME 2C 30 34
AVFMF 38
AVFMG 058 14 18 1C Supervisor IEAVESSE
AVFMH control
AVFML
AVFMN 058 20 Supervisor IEAVEDSR
AVFMS control
AVFNS 058 24 Supervisor IEAVEE1R
AVFNY control
AVFPC
AVFSI 059 Supervisor IEAVESRT
AVFSQ control
AVFSR 05B Timer super- IEAVRTI0
AVFSS vision
AVFSW
AVFSX 05D Supervisor IEAVECMS
AVFTA control
AVFTB 05E Supervisor IEAVESTS
AVFTD control
AVFUT
AVFWA 064 Supervisor IEAVLKRM
AVFWM control
03C RSM IARFF 065 Task manage- IEAVESSI
IARFP ment
047 Supervisor IEAVESVC 066 Supervisor IEAVEDSR
control control
04B TSO/E IKJEFTSL 06B Loadwait IEEVEXSN
IKJTSLAR 06C RTM IEAVTSLP
CMT-2 OS/390 V2R8.0 MVS System Codes
Reason Reason
Code Code Associated Detecting Code Code Associated Detecting
(Hex) (Hex) Component Module (Hex) (Hex) Component Module
06D RTM IEAVTADR 080 RSM IARDM
IARDT
06E RTM IEAVTGLB
IARFS
IEAVTLCL
IARKC
06F RTM IEAVTRT1 IARKI
IARKM
070 Supervisor IEAVETCL
IARMA
control
IARMS
071 Loadwait IEAVEREX IARPI
072 Supervisor IEAVEDS0 IARPV
control IARRI
IARRQ
074 Supervisor IEAVESLR IARSC
control IARSH
075 Supervisor IEAVESC0 IARSI
control IARSO
IARSQ
076 Supervisor IEAVEMCR IARSR
control IARSU
077 COMMTASK IEAVMNTR IARSX
IEAVMWSV IARVF
IEAVC700 IARXM
IEAVG700 IARXV
IEAVQ700 IARXW
IEE8B03D IARYB
IARYF
078 RCT IEAVAR00
IEAVAR02 083 ASM ILRSLSQA
079 RCT IEAVAR04 084 ASM ILRCMP
ILRSWPDR
07A RCT IEAVAR00
IEAVAR02 085 ASM ILRSAV
07C Supervisor IEAVESPR 086 ASM ILRVSAMI
control 087 ASM ILRSAV
07E Reconfiguration IEEVDEV ILRACT
ILRRLG
07F Task manage- IEAVECH0 ILRVSAMI
ment 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
System Completion Code to Module Table CMT-3
Reason Reason
Code Code Associated Detecting Code Code Associated Detecting
(Hex) (Hex) Component Module (Hex) (Hex) Component Module
09D System trace IEAVETRC 0B4 SSI IEFJCNTL
09E System trace IEAVETAC 0B5 SSI IEFJCNTL
IEAVETAI
0B7 Reconfiguration IEEVCPR
IEAVETIH
IEEVCONF
IEAVETEA
IEECB927
IEAVETPA
IEEVCPLF
IEAVETSP
IEEVVFLF
IEAVETSN
IEEVCPLN
IEAVETPS
IEEVCVSR
IEAVETRR
IEEVTOD
IEAVETSD
IEEVCPRA
IEAVETTF
IEEVCVPH
IEECB924
IEEVCPVF
IEECB925
IEEVCRLF
IEAVETFC
IEEVMSI.
IEAVETEF
IEEVCPUT
IEAVETFA
IEEVEXTR
IEAVETVP
IEAVETNP 0B6 OAM CBRLLCAN
IEAVETPW CBRLLDMT
IEAVETRW CBRLLERR
IEAVETCV CBRLLMT
IEAVETPV CBRLLMTL
ITRFHEX CBRLLVER
ITRFBR CBRLLWT
ITRF0001
0B8 Master sched- IEEPRWI2
ITRF0003
uler
ITRF0005
ITRF0007 0B9 Master sched- IEESB605
ITRF000B uler
ITRF000F 0BA Master sched- IEESB605
ITRF0013 uler Initiator IEFSD162
ITRF0015 IEFSD166
ITRF0017
ITRF0019 0BB Initiator IEFSD263
ITRF001B 0BD Master sched- IEEMB816
09F Supervisor IEAVEVS uler
control IEAVVSR 0BE Master sched- IEEMB809
0A0 01 02 03 Initiator IEFSD161 uler
IEFSD164 0BF Master sched- IEEMB816
IEFSD263 uler
0A1 DFP IGG0193Y 0Cx Supervisor IEAVEPC.
0A2 DFP IGG0203Y control
0A3 DFP IGG019OE 0D2 Supervisor IEAVEPC
control
0A4 DFP IGG019OE
0D3 Supervisor IEAVEPC
0A5 DFP IGG019OE control
0AE IOS IOSVRSTS 0D5 RSM PC/AUTH IARDX
0B0 SWA manager IEFQB551 IARPE
IEFQB556 IARYB
IEFQB580 0D9 COMMTASK IEAVPIX
0B1 SSI IEFJACTL 0F2 IOS IECVPST
IEFJCNTL
IEFJJCLS 0F6 GTF AHLSETEV
IEFJJOBS
IEFJWTOM
0B2 SSI IEFJJOBS
0B3 SSI IEFJACTL
CMT-4 OS/390 V2R8.0 MVS System Codes
Reason Reason
Code Code Associated Detecting Code Code Associated Detecting
(Hex) (Hex) Component Module (Hex) (Hex) Component Module
0F7 JES2 IECVPST 14A DFP IGC0007D
IECVPST
14B DFP IGC0007E
IECVPST
IECVPST 14C 01 10 11 System Environ- IFBBLD76
IECVPST mental IFBSMFNT
IECVPST Recording
(LOGREC)
0F8 Supervisor IEAVESVC
control 14F Task manage- IEAVSETS
ment
0F9 Supervisor IEAVESVC
control 153 SMF IFASMFDT
0FB Supervisor IEAVEPC 157 COMMTASK IEAVXDOM
control
15C EXCP IECVEXCP
0FD Supervisor IEAVESVC
15F SRM IRARMINT
control
16B Task manage- IEAVMODE
0FF Supervisor IEAVMVC0
ment
control
16D Supervisor IEAVESVC
101 Task manage- IEAVEWAT
control
ment
171 RSM IARPF
102 Task manage- IEAVEPST
IARPI
ment
IARPR
104 VSM IGVGLSQA IARPS
IARPU
106 CSV CSVGETMD
IARPV
10A VSM IGVGLSQA IARXW
10B Timer super- IEAVRT01 172 EXCP IECVEXCP
vision
177 Task manage- IEAVTEST
10D RTM IEAVTRTC ment
10E RTM IEAVTESP 178 VSM IGVGLSQA
110 IOS IOSPURGA 17A Task manage- IEAVEVT0
ment
121 IOS IGC0003C
17B Supervisor IEAVEPD0
122 Master sched- IEE3703D
control
uler
17D Task manage- IEAVEVT0
128 Task manage- IEAVTB00
ment
ment
182 RACF ICHRCK00
12A Task manage- IEAVEAT0
ment 183 RACF ICHRIN00
12C Task manage- IEAVECH0 185 RACF ICHRDF00
ment
18A RSM IARPF
12E Timer super- IEAVRT00 IARPI
vision IARPR
IARPU
12F Timer super- IEAVRT00
IARPV
vision
IARXV
130 GRS ISGGNQDQ
1C5 00010001 System logger IXGA1WRT
133 Dumping ser- IEAVAD00
1C5 00010002 System logger IXGA1WRT
vices IEAVTSDX
1C5 00010003 System logger IXGA1SWT
138 GRS ISGGNQDQ
1C5 00010004 System logger IXGA1DEL
13C RTM IGC00060
1C5 00010005 System logger IXGA1SET
13E Task manage- IEAVEED0
ment 1C5 00020001 System logger IXGA1HSM
147 DFP IGC0007A 1C5 00020002 System logger IXGBLF01
149 DFP IGC0007C 1C5 00020003 System logger IXGBLF01
System Completion Code to Module Table CMT-5
Reason Reason
Code Code Associated Detecting Code Code Associated Detecting
(Hex) (Hex) Component Module (Hex) (Hex) Component Module
1C5 00030000 System logger IXGC3SEX 1C5 00080707 System logger IXGSEXIT
1C5 00030002 System logger IXGC3SEX 1C5 00080801 System logger IXGSXGET
IXGWORKT
1C5 00080802 System logger IXGSXGET
1C5 00030003 System logger IXGC3SEX
1C5 00090000 System logger IXGX1LSN
1C5 00030004 System logger
1C5 00090001 System logger IXGX1LSN
1C5 00030006 System logger IXGF2EXT
1C5 00090002 System logger IXGX1LSN
1C5 00030009 System logger IXGC4RSC
1C5 00090003 System logger IXGX1LSN
1C5 00040001 System logger IXGF2WRT
1C5 00090004 System logger IXGX1LSN
1C5 00050001 System logger IXGI3DIR
1C6 Task Manage- IEAVSETS
1C5 00050002 System logger IXGI3DIR ment
IXGI3RPT
1FC Supervisor IEAVESVR
1C5 00050003 System logger IXGI3DIR control
1C5 00060001 System logger IXGL1SRB 200 EXCP IECVEXFR
1C5 00070001 System logger IXGF1TRX 201 Task manage- IEAVEWAT
ment
1C5 00070002 System logger IXGF1TRX
202 Task manage- IEAVEPST
1C5 00070003 System logger IXGF1TRX
ment
1C5 00070004 System logger IXGF1TRX
204 VSM IGVGLSQA
1C5 00070005 System logger IXGF1TRX
205 VSM IGVGLSQA
1C5 00070006 System logger IXGF1TRX
206 CSV CSVGETMD
1C5 00070007 System logger IXGF1TRX
20A VSM IGVGLSQA
1C5 00070008 System logger IXGF1TRX
20D RTM IEAVTRTE
1C5 00070009 System logger IXGF1TRX
20E RTM IEAVTESP
1C5 00070010 System logger IXGF1TRX
20F IOS IECVPST
1C5 00070011 System logger IXGF1TRX
222 Master sched- IEE3703D
1C5 00070012 System logger IXGF1TRX uler
1C5 00070013 System logger IXGF1TRX 228 Task manage- IEAVTB00
ment
1C5 00070014 System logger IXGF1TRX
22A Task manage- IEAVEAT0
1C5 00070015 System logger IXGF1TRX
ment
1C5 00070016 System logger IXGF1TRX
22C Task manage- IEAVECH0
1C5 00080202 System logger IXGSDSIN ment
1C5 00080302 System logger IXGSDSIN 22F Timer Super- IEAVRTI0
1C5 00080401 System logger IXGSDSOC vision
1C5 00080402 System logger IXGSDSOC 230 GRS ISGGNQDQ
1C5 00080403 System logger IXGSDSOC 233 Dumping ser- IEAVAD00
vices IEAVTSDT
1C5 00080501 System logger IXGSDSUN IEAVTSDX
1C5 00080502 System logger IXGSDSUN 238 GRS ISGGNQDQ
1C5 00080601 System logger IXGSDSGT 23E Task manage- IEAVEED0
1C5 00080602 System logger IXGSDSGT ment
1C5 00080702 System logger IXGSEXIT 247 DFP IGC0007A
1C5 00080703 System logger IXGSEXIT 253 SMF IFASMFDT
1C5 00080704 System logger IXGSEXIT 25F SRM IRARMERR
1C5 00080705 System logger IXGSEXIT 260 RCT IEAVAX00
1C5 00080706 System logger IXGSEXIT 271 RSM IARPV
278 VSM IGVGLSQA
CMT-6 OS/390 V2R8.0 MVS System Codes
Reason Reason
Code Code Associated Detecting Code Code Associated Detecting
(Hex) (Hex) Component Module (Hex) (Hex) Component Module
27B Supervisor IEAVEPD0 402 Task manage- IEAVEPST
control ment
282 RACF ICHRCK00 406 CSV CSVSBRTN
283 RACF ICHRIN00 40A VSM IGVVSMRF
285 RACF ICHRDF00 42A Task manage- IEAVEAT0
ment
28A RSM
430 GRS ISGGNQDQ
2C6 IOS IOSVMIHQ
ISGGFRR0
IOSVPTHV
IOSVCDRI 433 00000008 Dump Analysis ADYTRNS
and Elimination
2F3 Initiator IEFIB605
(DAE)
2FC Supervisor IEAVEIOR
438 GRS ISGGNQDQ
control
ISGGFRR0
300 EXCP IECVEXCP
43E Task manage- IEAVEED0
301 Task manage- IEAVEWAT ment
ment
45F SRM IRARMEVT
305 VSM IGVAAQAT
46D RTM IEAVTESP
306 CSV CSVGETMD
478 VSM IGVVSMRF
30A VSM IGVAAQAT
47A Task manage- IEAVEVT0
30E RTM IEAVTESP ment
312 CSV IGC018 47D Task manage- IEAVEVT0
ment
322 SMF IEATLEXT
482 RACF ICHRCK00
328 Task manage- IEAVTB00
ment 483 RACF ICHRIN00
32E Timer super- IEAVRT00 485 RACF ICHRDF00
vision
4FC Supervisor IEAVEPCR
330 GRS ISGGNQDQ control
333 Dumping ser- IEAVTSDG 500 EXCP IECVEXCP
vices IEAVTVSM
502 Task manage- IEAVEPST
IEAVTSDH
ment
IEAVTSDL
IEAVTSDT 504 VSM IGVVSM24
338 GRS ISGGNQDQ 505 VSM IGVVSM24
33E Task manage- IEAVEED0 522 SMF IEATLEXT
ment
52A Task manage- IEAVEAT0
35F Initiator IEFSD263 ment
378 VSM IGVAAQAT 530 GRS ISGGNQDQ
37A Task manage- IEAVEVT0 538 GRS ISGGNQDQ
ment
53E Task manage- IEAVEED0
37B Supervisor IEAVEPDR ment
control
553 SMF IEEMB839
37D Task manage- IEAVEVT0
55F SRM IRARMSRV
ment
57D Task manage- IEAVEVT0
382 RACF ICHRCK00
ment
383 RACF ICHRIN00
582 RACF ICHRCK00
385 RACF ICHRDF00
585 RACF ICHRDF00
3FC Supervisor IEAVEE1R
5FC Loadwait IEAVERER
control
604 VSM IGVVSM24
400 DFP IECVEXCP
System Completion Code to Module Table CMT-7
Reason Reason
Code Code Associated Detecting Code Code Associated Detecting
(Hex) (Hex) Component Module (Hex) (Hex) Component Module
605 VSM IGVVSM24 878 VSM IGVGSQA
622 TSO/E IKJEFLJ 87D Task manage- IEAVEVT0
IKJEFLG ment
65F SRM IRARMCHM 8C4 04 JES IAZPJCL
67D Task manage- IEAVEVT0 905 VSM IGVVSMRF
ment
906 CSV CSVSBRTN
683 RACF ICHRIN00
90A VSM IGVVSMRF
684 RACF ICHRSV00
922 Initiator IEFIB621
685 RACF ICHRDF00
92A Task manage- IEAVEAT0
6FC Supervisor IEAVEPC ment
control
930 GRS ISGGNQDQ
700 EXCP IECVEXCP
938 GRS ISGGNQDQ
702 Task manage- IEAVEPST
978 VSM IGVVSMRF
ment
9C6 global resource ISGLOBTS
704 VSM IGVVSMRT
serialization ISGLRELS
705 VSM IGVVSMRF ISGLPRGS
ISGLCRTS
706 CSV CSVGETMD
ISGLRTR
70A VSM IGVVSMRF ISGLTM
71A DFP IGG0CLA9 A00 EXCP IECVEXCP
IGG0CLA9 IECVEXFR
72A Task manage- IEAVEAT0 A03 RTM IEAVTSKT
ment
A05 VSM IGVBDFE
730 GRS ISGGNQDQ
A06 CSV CSVRBENQ
ISGLNQDQ
ISGGFRR0 A0A VSM IGVBDFE
738 GRS ISGGNQDQ A22 Reconfiguration IEE3703D
ISGLNQDQ
A23 COMMTASK IEAVMFRR
ISGGFRR0
A78 VSM IGVBDFE
75F SRM IRARMINT
AC4 JES3 IATCNDB
76D Dynamic Output IEFDOCNL
AC7 01 Timer super- IEAVRTI0
778 VSM IGVVSM31
vision
77D Task manage- IEAVEVT0
B00 EXCP IECVEXFR
ment
B04 VSM IGVVSMRT
7C4 JES3 IATCS01
IATCS03 B05 VSM IGVVSMRF
IATCS04
B0A VSM IGVVSMRF
7C6 IOS IOSVUSER
B23 COMMTASK IEAVSTAA
800 EXCP IECVEXCP
B78 VSM IGVVSMRF
804 VSM IGVGSQA
805 VSM IGVVSMRF
806 CSV CSVGETMD
80A VSM IGVGSQA
822 Initiator IEFSD263
82A Task manage- IEAVEAT0
ment
830 GRS ISGGNQDQ
838 GRS IEAVENQ1
CMT-8 OS/390 V2R8.0 MVS System Codes
Reason Reason
Code Code Associated Detecting Code Code Associated Detecting
(Hex) (Hex) Component Module (Hex) (Hex) Component Module
C0D RSM ASM IARDG E03 RTM IEAVTSKT
PC/AUTH IARDP
E23 COMMTASK IEAVVRP2
IAREI
IARER EFB JES3 IATCNDAL
IARFP IATCNDIT
IARGA IATCNDMS
IARGD IATCNDTR
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
C22 EXCP IECVEXCP
C78 VSM IGVSLIST
CFB JES3 IATABMN
D04 VSM IGVAAQAT
D05 VSM IGVFLSQA
D06 CSV CSVSBRTN
D0A VSM IGVAAQAT
D0D RTM IEAVTRTE
D22 Master sched- IEE0003D
uler
D23 COMMTASK IEAVVWTO
IEAVMWTO
IEAVM600
D78 VSM IGVAAQAT
DFB JES3 IATFCLT
E00 EXCP IECVEXCP
System Completion Code to Module Table CMT-9
CMT-10 OS/390 V2R8.0 MVS System Codes
Wait State Code to Module Table
This table correlates wait state codes with module numbers. If the wait state code you require does not appear in the
For each code, the associated component and detecting table, contact the IBM Support Center. Provide the wait state
module are listed. code.
Code Detecting Code Detecting
(Hex) Associated Component Module (Hex) Associated Component Module
002 IOS IEAIPL00 03D VSM IEAVNP08
003 IPL, IOS IEAIPL00 03E ASM ILRTMI00
IEAIPL03 03F NIP IEAVNPM2
004 IOS IEAIPL03 040 NIP IEAVNIPM
005 IPL IEAIPL00 044 NIP IEAVNIP0
006 IPL IEAIPL00 045 RTM IEAVNIPM
007 COMMTASK IEAVNPCA 046 NIP IEAVNIP0
00A IPL IEAVNP03 04A NIP IEAVNIP0
00B Master scheduler IEEVIPL 050 Loadwait IGFPTSIG
00D Master scheduler IEEVIPL 051 ACR IGFPTERM
00E IPL IEAIPL00 052 ACR IGFPTERM
017 IPL IEAIPL00 053 IOS IPL NIP IEAIPL03
IEAIPL99
019 IPL IEAIPL00
IEAVNIP0
01B RTM IEESTPRS IOSIUCB
01C Supervisor control IEAVESPR 054 IPL IEAIPL02
020 Reconfiguration IEAVNP27 055 IOS IPL IEAIPL31
IEAIPL41
021 IOS IEAVNPM2
IEAIPL02
022 IOS IECVDAVV IEAIPL40
023 System trace IEAVNP51 059 NIP IEAVNIP0
024 MCH IGFPTREC 05C DFSMSdfp IEAVNP11
025 IPL IEAIPL41 05D DFSMSdfp IEAVNP11
028 IOS IEAIPL40 05E DFSMSdfp IEAVNP11
02E ASM ILRMSG00 05F DFSMSdfp IEAVNP11
030 NIP IEAVNIP0 060 ASM ILRASRIM
031 IOS IEAIPL03 061 ASM ILRASRIM
032 NIP IEAVNIPM 062 IOS IOSRCHPR
IEAVNIP0 063 ASM IEAVNP03
033 NIP IEAVNIPM IEAVNP11
IEAVNP19
IEAVNIP0 ILRASRIM
035 IOS IEAIPL03 064 NIP IEAVNIPM
037 System Environmental IEAVNP76 IEAVNIP0
Recording 065 NIP IEAVNIPM
038 ASM IPL IEAIPL00 06F IOS IOSVMSLG
ILRASRIM IEAVNP05 070 IPL IEAIPL00
039 IOS IEAVNPM3 071 IPL IEAIPL41
03A CSV IEAVNP05
03B CSV IEAVNP05
03C ASM ILRASRIM
ILRIODRV
ILRMSG00
Copyright IBM Corp. 1988, 1999 WSM-1
Code Detecting Code Detecting
(Hex) Associated Component Module (Hex) Associated Component Module
072 IPL, IOS IEAIPL30 110 IOS IOSRHREC
IEAIPL41
111 IOS IOSRHREC
IEAIPL40
IEAIPL43 112 IOS IOSRHREC
IEAIPL46
113 IOS IOSRCHPR
IEAIPL70
IEAIPL71 114 IOS IOSRCHPR
IEAIDRIA 115 IOS IECVPST
IOSISTOR IOSVDAVV
073 IPL IEAIPL00 IECVPST
074 IPL,IOS IEAIPL35 116 IOS IOSVRSTS
IEAIPL00 200 ALC IEFAB4I0
IEAIPL02 IEFEB400
IEAIPL03
201 COMMTASK IEAVN700
075 IPL IEAIPL00
202 COMMTASK IEAVN701
076 IPL IEAIPL00
A00 RTM RTM
077 IEAIPL07
A01 MCH IGFPMCIH
079 IOS IEAIPL40
A19 IOS IOSRMCH
07B NIP IEAVNIP0
A1E Timer supervision NIP IEATESC2
07D NIP IEAVNPCF IEAVRTOD
081 IPL IEAIPL00 IEATVTOD
IEATTSCH
083 Supervisor control IEAVESAR
IEATTFDH
084 RTM IGFPEMER IEATESCH
IEAVNIP0
085 ASM ILRASRIM
ILRASRIM A1F Timer supervision IEATESC2
087 COMMTASK IEAVG603 A20 RSM IARMN
IEAVG604
A21 RSM IARMN
IEAVG605
A22 Master scheduler IEEVDCSR
088 IPL IEAIPL50
A23 MCH IGFPMAIN
08A COMMTASK IEAVBLWT
A24 MCH IGFPMAIN
08B IOS IEAIPL40
A26 MCH IGFPMAIN
09x Loadwait IEEVEXSN
A28 MCH IGFPMCIH
0A1 Loadwait IEEVEXSN
A29 Loadwait IGFPTERM
0A2 XCF IXCI2IST
IXCI2ETX A2A RSM IEAVNPD8
IXCI2PH1 A2B MCH IGFPMAIN
0A4 Timer supervision IEATESC2 A70 COMMTASK IEAVBWTO
IEATESCH
B23 IOCP IEAVSTAA
0B0 IOS IEAIPL43
CCC Loadwait IEEMPS03
0B1 IOS IOSIOFR
IEAIPL43 D0D SMF IEEMB829
0B2 IOS IEAIPL71 FF0 Installation-provided N/A
0B3 IPL IEAIPL49 FF1 Installation-provided N/A
0B4 IOS IOSIUCB FF2 Installation-provided N/A
0E3 VSM IEAVNP08 FF3 Installation-provided N/A
0E8 MCH IEAVNP06 FF4 Installation-provided N/A
101 VSM IEAVGM00 FF5 Installation-provided N/A
102 VSM IEAVGM00 FF6 Installation-provided N/A
104 Supervisor control IEAVESVR FF7 Installation-provided N/A
WSM-2 OS/390 V2R8.0 MVS System Codes
Code Detecting
(Hex) Associated Component Module
FF8 Installation-provided N/A
FF9 Installation-provided N/A
FFA Installation-provided N/A
FFB Installation-provided N/A
FFC Installation-provided N/A
FFD Installation-provided N/A
FFE Installation-provided N/A
Wait State Code to Module Table WSM-3
WSM-4 OS/390 V2R8.0 MVS System Codes
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. The PSW for one of these wait states has the format:
X'ðððAðððð
ððwwrrrr'
000A0000 00
The A is bits 12 through 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 for I/O on the IPL None.
device.
22 0000 The stand-alone dump program is waiting for intervention on the Ready the IPL device.
IPL device.
24 The stand-alone dump program detected an error. If the dump program did not
issue message AMD005I, try a
system restart. If system
restart fails, reIPL the stand-
alone dump program, prefer-
ably from a different volume.
0100 The stand-alone dump program cannot read the volume label. Use another volume or regen-
erate the label. Other data
sets on the volume might be
unusable.
0200 The volume label is nonstandard. Use another volume or regen-
erate the label. Other data
sets on the volume might be
unusable.
0300 The stand-alone dump program cannot read the format 4 data set Use another volume or change
control block (DSCB). the DSCB. Other data sets on
the volume might be unusable.
0400 The system does not support the IPL device type. Use a device type that the
system supports.
0500 The SYS1.PAGEDUMP data set is not on the IPL volume. None.
0600 The stand-alone dump program cannot read the stand-alone dump None.
common communication table (CCT).
0700 The stand-alone dump program cannot write to the stand-alone None.
dump file.
For a tape IPL version, this could be due to a missing write ring in If tape IPL, check for the
the IPL volume. needed write ring, or disable
file protection.
0800 The stand-alone dump program cannot read module AMDSARDM. None.
0900 The stand-alone dump program cannot read module AMDSADIP. None.
0A00 The stand-alone dump program cannot read module AMDSAPGE. None.
25 0200 A program check or other unexpected error was detected during None.
output DASD dump data set processing. The system ends the
dump.
27 0010 The validity check of the devices and dump options table (DDO) None.
failed after the system loaded it from SYS1.PAGEDUMP. The
system ends the dump.
Copyright IBM Corp. 1988, 1999 SDW-1
Wait State Reason
Code Code Explanation Operator Response
0020 The validity check of the dump relocation table (RLT) failed after None.
the system loaded the AMDSAPGE load module from
SYS1.PAGEDUMP. The system ends the dump.
0030 An error occurred while the system read the AMDSAPGE load None.
module from SYS1.PAGEDUMP The system ends the dump.
0040 The system detected an internal logic error in the SADMP dump None.
initialization program. The system ends the dump.
28 0100 The DASD IPL program is unable to read the label on the IPL None.
device. The system ends the dump.
0200 The DASD IPL program encountered a non-standard label on the None.
IPL device. The system ends the dump.
0300 The DASD IPL program is unable to read the format 4 data set None.
control block (DSCB) on the IPL device. The system ends the
dump.
0400 The DASD IPL program detected an unsupported device type for None.
the IPL device. The system ends the dump.
0500 The DASD IPL program could not locate SYS1.PAGEDUMP on None.
the IPL device. The system ends the dump.
0600 The DASD IPL program could not read the stand-alone dump None.
common communication table (CCT) from the IPL device. The
system ends the dump.
0700 A permanent I/O error occurred while performing I/O to the None.
SYS1.PAGEDUMP work file on the DASD IPL device. The system
ends the dump.
0800 A permanent I/O error occurred while performing I/O to the None.
SYS1.PAGEDUMP work file on the DASD IPL device. The system
ends the dump.
0900 A program check or other unexpected error was encountered in None.
the DASD IPL module or subroutine. The system ends the dump.
0A00 The work file interface in the DASD IPL module was passed incor- None.
rect parameters. The system ends the dump.
29 0700 The tape IPL module was unable to write to the work file on the None.
IPL tape. The system ends the dump.
0800 The tape IPL module was unable to read the dump program loader None.
(AMDSADPL) from the IPL tape. The system ends the dump.
0900 A program check or other unexpected error was encountered in None.
the tape IPL module or subroutine. The system ends the dump.
0A00 The work file interface in the tape IPL module was passed incor- None.
rect parameters. The system ends the dump.
31 dddd The stand-alone dump program is waiting for I/O to the device. None.
32 dddd The stand-alone dump program is waiting for intervention on the Mount and ready a tape.
device.
33 0mmm The stand-alone dump program is waiting for a reply to message Reply to the message.
AMDmmmA or AMDmmmD.
34 dddd The stand-alone dump program detected an I/O error on the None.
device and is waiting for a sense command to complete.
35 dddd The stand-alone dump program restarted I/O on the device and is None.
waiting for I/O to complete.
36 0100 The output tape is labelled and cannot be used. Mount another tape and ready
it.
0200 The output tape needs a file protect ring. Insert a ring into the tape and
ready it, or disable file pro-
tection.
SDW-2 OS/390 V2R8.0 MVS System Codes
Wait State Reason
Code Code Explanation Operator Response
0300 The output tape is full. Save the previous tape and
mount a new one.
37 0ddd The stand-alone dump program is waiting for I/O that is neither a None.
sense nor a restart to complete on the device.
3E 0000 The system is waiting for one of the following: Select the system console or
press ENTER on one of the
An attention interrupt from the operator selected console
consoles defined in the
An interrupt from the system console
AMDSADMP macro. If a
An external key interrupt to indicate a no-console condition.
console is not available, ready
a tape on the tape drive that
you defined on the
AMDSADMP macro, then
cause an external interruption.
0100 All storage was cleared to binary zeroes prior to the loading of None. If SADMP is restarted at
stand-alone dump. this point, 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.
3F 0100 The generated output device cannot be used, and due to a no- None.
console condition, a replacement cannot be specified. The system
ends the dump.
0101 The generated output DASD data set is not initialized and Do one of the following:
REUSEDS=NEVER was specified on the AMDSADMP macro.
Reinitialize the output data
Because of a no-console condition, a replacement cannot be spec-
set from another system
ified. The system ends the dump.
and perform a system
restart.
Perform a system restart
and select a usable
console so that a different
output device can be
specified.
0102 The generated output DASD data set is initialized and Do one of the following:
REUSEDS=CHOICE was specified on the AMDSADMP macro.
Reinitialize the output data
Because of a no-console condition, SADMP cannot issue message
set from another system
AMD096A to determine if the data set should be reused.
and perform a system
restart.
Perform a system restart
and select a usable
console so that SADMP
can issue AMD096A.
0200 A program check or other unexpected error was detected during None.
output device initialization. The system ends the dump.
40 0100 The generated output device address is not usable, and due to a None.
no-console condition, a replacement cannot be specified. The
system ends the dump.
0200 A program check or other unexpected error was detected during None.
output device address processing. The system ends the dump.
41 0000 The SADMP program ended normally; dumping is complete. Save the dump.
Note: Message AMD104I can be an indication of successful com-
pletion of dump.
Stand-Alone Dump Wait State Codes SDW-3
Wait State Reason
Code Code Explanation Operator Response
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.
4F ssee The virtual storage dump program ended due to an internal error. Record the wait state code. If
necessary, rewind and unload
ss denotes the failing module or service.
the output tape; the normal
ee denotes the specific type of error. end-of-file is not present.
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 SADMP error recovery and None.
program ending processing.
0D02 The stand-alone dump program requested too many self-dumps. None.
0D03 The system ended SADMP error recovery and program ending None.
processing because of I/O errors.
0D05 The system did not find any SADMP error recovery module on the None.
recovery stack.
0E10 The system cannot continue processing because there are not None.
enough SADMP internal storage blocks (BCT) on the available
queue.
0F01 A permanent I/O error occurred on the output DASD and the oper- Perform a system restart to
ator replied 'T' to message AMD098A. dump to another output
device.
13F1 A permanent I/O error occurred on the output tape and the oper- Perform a system restart to
ator replied 'T' to message AMD098A. dump to another output
device.
14F1 A permanent I/O error occurred on the output tape, and the oper- Perform a system restart to
ator replied ‘T’ to message AMD098A. dump to another output
device.
1C13 A system restart occurred. None.
1D12 An external interruption occurred. None.
1E20 The operator replied ‘T’ to message AMD088D. None.
1E30 The prefix storage area (PSA) was incorrect. The system cannot None.
dump virtual storage.
1E40 The segment table (SGT) was incorrect. The system cannot dump None.
virtual storage.
1E50 The page table (PGT) was incorrect. The system cannot dump None.
virtual storage.
1E60 The communication vector table (CVT) was incorrect. The system None.
cannot dump virtual storage.
1E70 The paging vector table (PVT) was incorrect. The system cannot None.
dump virtual storage.
1E80 The real storage manager (RSM) internal table (RIT) was incorrect. None.
The system cannot dump virtual storage.
1E90 The page frame table (PFT) was incorrect. The system cannot None.
dump virtual storage.
1EA0 No contiguous storage could be found for a swap SGT. The None.
system could not dump virtual storage.
22F1 A permanent I/O error occurred on the output tape volume and the Perform a system restart to
operator replied 'T' to message AMD098A. dump to another output
device.
SDW-4 OS/390 V2R8.0 MVS System Codes
Wait State Reason
Code Code Explanation Operator Response
4701 A program check or other unexpected error was detected during None.
dump title processing. The system ends the dump.
ssF1 An I/O error occurred on the output device. Perform a system restart to
dump to another output
device.
FEcc A program check occurred. cc is the rightmost byte of the program None.
interruption code.
Stand-Alone Dump Wait State Codes SDW-5
SDW-6 OS/390 V2R8.0 MVS System Codes
0100 0105
IPCS User Completion Codes
Use this procedure if IPCS processing ends with a user com- 0101 (hexadecimal 065)
pletion code. The code is 4 decimal digits.
Explanation: The system detected an error while attempting to get
a record from the problem or data set directory.
Problems in either IBM-provided IPCS code or in installation
exit routines can cause IPCS to issue an abend. Do the fol- System Action: A set of messages that describe the problem in
lowing for most IPCS user completion codes: more detail precedes the abend. The system ends subcommand
processing.
1. Check to see if IPCS issued any messages that might
System Programmer Response: Follow the programmer response
provide more information about the problem. These mes- for the BLS03nnnt messages that precede the abend.
sages have the form of BLSnnnnnc, unless they were
issued from an exit routine.
0102 (hexadecimal 066)
2. Look at the following explanation of the user completion Explanation: The system detected an error while attempting to
code for a description of the problem. Follow the diag- close the problem or data set directory.
nostic steps for the code. System Action: A set of messages that describe the problem in
3. Check for a failing installation exit routine. more detail precedes the abend. The system ends subcommand
processing.
Use the IPCS TRAP subcommand to isolate prob-
System Programmer Response: Follow the programmer response
lems relating to the use of exit services.
for the BLS03nnnt messages that precede the abend.
If your installation provides exit routines, check the
dump to see if one of them is identified as the failing 0103 (hexadecimal 067)
module. Explanation: The system detected an internal error.
The IPCSTOC file might contain information to help System Action: The system ends subcommand processing.
identify exits.
System Programmer Response: Search problem reporting data
If the problem appears to be in an installation exit bases for a fix for the problem. If no fix exists, contact the IBM
routine, attempt to by-pass the problem by using the Support Center.
NOTEST keyword.
0104 (hexadecimal 068)
For an additional check:
Explanation: An attempt was made to acquire a problem resource
– Remove all command options that cause instal- while either the problem directory or the data set directory was open.
lation exit routines to be invoked from the IPCS
System Action: The system ends subcommand processing.
input stream.
System Programmer Response: Search problem reporting data
– Rerun IPCS. If the problem goes away, an bases for a fix for the problem. If no fix exists, contact the IBM
installation exit routine probably has a logic Support Center.
problem.
If an installation exit routine caused the problem, use the 0105 (hexadecimal 069)
dump data to isolate the reason for the failure. Correct Explanation: The system detected an error during a message pro-
the exit routine. duction procedure. A reason code is in general purpose register 15,
as follows:
The following list contains the IPCS completion codes: Reason Code Explanation
60 The system could not obtain enough storage for the
current output message.
0100 (hexadecimal 064)
Other An internal problem occurred.
Explanation: The system detected an error while attempting to
open the problem or data set directory for reading. System Action: The system does not issue the message. The
system ends subcommand processing.
System Action: The abend follows messages that indicate the
nature of the problem. The system ends subcommand processing. System Programmer Response: If the reason code is 60,
increase the region size and try again. If the problem persists or if
System Programmer Response: Follow the programmer response the reason code is other than 60, search problem reporting data
for the BLS03nnnt messages that precede the abend. bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
Copyright IBM Corp. 1988, 1999 IPCS-1
0106 0117
0106 (hexadecimal 06A) 0112 (hexadecimal 070)
Explanation: The system detected an I/O error during processing Explanation: The system detected an internal error.
of a DELPROB subcommand. The type of problem is indicated by
System Action: Message BLS04061I precedes the abend. The
one of the following messages: BLS04042I, BLS04043I, or
system ends subcommand processing.
BLS04045I and their associated messages.
System Programmer Response: Search problem reporting data
System Action: The system ends DELPROB subcommand proc-
bases for a fix for the problem. If no fix exists, contact the IBM
essing.
Support Center.
System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM 0113 (hexadecimal 071)
Support Center.
Explanation: The system detected an error while opening the data
set directory. An attempt to free the data set directory did not
0107 (hexadecimal 06B)
succeed.
Explanation: The system detected an internal error.
System Action: Message BLS04052I precedes the abend. The
System Action: The system ends subcommand processing. system ends subcommand processing.
System Programmer Response: Search problem reporting data System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Support Center.
0108 (hexadecimal 06C) 0114 (hexadecimal 072)
Explanation: The system detected an error while performing an Explanation: The user instructed the IPCS attention processor to
open or close operation on the problem directory during confirmation issue a diagnostic abend by entering 'abend'.
processing.
System Action: The system ends the IPCS session.
System Action: Message BLS04042I or BLS04045I precedes the
System Programmer Response: The purpose of the IPCS
abend. The system ends DELPROB subcommand processing.
attention-exit abend function is to permit diagnostic information to be
System Programmer Response: Search problem reporting data collected regarding apparent IPCS problems. Use the dump to
bases for a fix for the problem. If no fix exists, contact the IBM confirm this diagnosis.
Support Center.
0115 (hexadecimal 073)
0109 (hexadecimal 06D)
Explanation: The system detected an error while reading the data
Explanation: A dump-directory equate-symbol record was passed set directory.
to a service routine to have an action performed on its contents. The
System Action: Message BLS04053I precedes the abend. The
record contents were incorrect. The system issues the abend only if
system ends subcommand processing.
the TEST operand is specified.
System Programmer Response: Search problem reporting data
System Action: The system ends subcommand processing.
bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: Search problem reporting data Support Center.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. 0116 (hexadecimal 074)
Explanation: The system detected an incorrect write request while
0110 (hexadecimal 06E)
writing a record to the data set directory.
Explanation: The system detected an internal error.
System Action: Message BLS04054I precedes the abend. The
System Action: A message that indicates the type of internal error system ends subcommand processing.
detected precedes the abend. The system ends subcommand proc-
System Programmer Response: Search problem reporting data
essing.
bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: Search problem reporting data Support Center.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. 0117 (hexadecimal 075)
Explanation: The system detected a permanent write problem
0111 (hexadecimal 06F)
while writing a record to the data set directory.
Explanation: Records passed for comparison do not contain the
System Action: Message BLS04054I precedes the abend. The
same VSAM key.
system ends subcommand processing.
System Action: Message BLS04064I precedes the abend. The
System Programmer Response: Search problem reporting data
system ends subcommand processing.
bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: Search problem reporting data Support Center.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
IPCS-2 OS/390 V2R8.0 MVS System Codes
0118 0129
0118 (hexadecimal 076) 0124 (hexadecimal 07C)
Explanation: The system detected an error while attempting to Explanation: The system detected an incorrect write request while
write a record to the data set directory. attempting to write to the problem directory.
System Action: The informational message BLS04054I precedes System Action: Message BLS04044I precedes the abend. The
the abend. The system ends subcommand processing. system ends subcommand processing.
System Programmer Response: Search problem reporting data System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Support Center.
0119 (hexadecimal 077) 0125 (hexadecimal 07D)
Explanation: The system detected a permanent error while Explanation: The system detected a permanent write error while
attempting to close the data set directory. writing a record to the problem directory.
System Action: Message BLS04055I precedes the abend. The System Action: Message BLS04044I precedes the abend. The
system ends subcommand processing. system ends subcommand processing.
System Programmer Response: Search problem reporting data System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Support Center.
0120 (hexadecimal 078) 0126 (hexadecimal 07E)
Explanation: The system detected an error while attempting to Explanation: A problem occurred while writing a record to the
close the data set directory. problem directory.
System Action: Message BLS04055I precedes the abend. The System Action: Message BLS04044I precedes the abend. The
system ends subcommand processing. system ends subcommand processing.
System Programmer Response: Search problem reporting data System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Support Center.
0121 (hexadecimal 079) 0127 (hexadecimal 07F)
Explanation: The system detected an error while attempting to Explanation: The system detected a permanent error while closing
open the problem directory. The attempt to free the problem direc- the problem directory.
tory was unsuccessful.
System Action: Message BLS04045I precedes the abend. The
System Action: Message BLS04042I precedes the abend. The system ends subcommand processing.
system ends subcommand processing.
System Programmer Response: Search problem reporting data
System Programmer Response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM
bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Support Center.
0128 (hexadecimal 080)
0122 (hexadecimal 07A)
Explanation: The system detected an error while attempting to
Explanation: The system could not obtain enough virtual storage. close the problem directory.
System Action: Message BLS04015I precedes the abend. The System Action: Message BLS04045I precedes the abend. The
system ends subcommand processing. system ends subcommand processing.
System Programmer Response: Ensure that the region size is System Programmer Response: Search problem reporting data
large enough for IPCS execution. bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
0123 (hexadecimal 07B)
0129 (hexadecimal 081)
Explanation: The system detected an error while reading the
problem directory. Explanation: The system detected an internal error.
System Action: Message BLS04043I precedes the abend. The System Action: The system ends subcommand processing.
system ends subcommand processing.
System Programmer Response: Search problem reporting data
System Programmer Response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM
bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Support Center.
IPCS User Completion Codes IPCS-3
0130 0148
0130 (hexadecimal 082) 0138 (hexadecimal 08A)
Explanation: The system detected an internal error. Explanation: The system detected an error while attempting to
open a data set. Messages that precede this abend specify in more
System Action: The system ends subcommand processing.
detail the nature of the problem.
System Programmer Response: Search problem reporting data
System Action: The system ends subcommand processing.
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
0131 (hexadecimal 083) Support Center.
Explanation: The system detected an internal error.
0139 (hexadecimal 08B)
System Action: The system ends subcommand processing.
Explanation: The system detected an internal error.
System Programmer Response: Search problem reporting data
System Action: The system ends subcommand processing.
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
0132 (hexadecimal 084) Support Center.
Explanation: The system detected an error while attempting to
0140 (hexadecimal 08C)
write a record into a data set. The messages that precede this abend
specify in more detail the nature of the problem. Explanation: The system could not close a data set.
System Action: The system ends subcommand processing. System Action: Message BLS03114I precedes the abend. The
system ends subcommand processing. Either the data set may not
System Programmer Response: Search problem reporting data
be closed or freed.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. System Programmer Response: If the data set is not properly
closed, use IDCAMS VERIFY to close it. If the data set is not freed,
0133 (hexadecimal 085) issue a TSO/E FREE command.
Explanation: The system detected an internal error.
0141 (hexadecimal 08D)
System Action: Any existing messages on the message queue
Explanation: The system detected an internal error.
were routed to the terminal prior to the abend. The system ends sub-
command processing. System Action: The system ends subcommand processing.
System Programmer Response: Follow the programmer System Programmer Response: Search problem reporting data
response(s) for any messages issued prior to the abend. bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
0134 (hexadecimal 086)
0145 (hexadecimal 091)
Explanation: The system detected an internal error.
Explanation: The area pointed to by the control block pointer spec-
System Action: The system ends subcommand processing.
ified in message BLS04072I does not contain the specified control
System Programmer Response: Search problem reporting data block.
bases for a fix for the problem. If no fix exists, contact the IBM
System Action: Message BLS04072I precedes the abend. The
Support Center.
system ends subcommand processing.
0135 (hexadecimal 087) System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
Explanation: The system detected an internal error. Support Center.
System Action: The system ends subcommand processing.
System Programmer Response: Search problem reporting data 0147 (hexadecimal 093)
bases for a fix for the problem. If no fix exists, contact the IBM Explanation: The system detected an internal error.
Support Center.
System Action: The system ends subcommand processing.
0137 (hexadecimal 089) System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM
Explanation: The system detected an error while attempting to Support Center.
close a data set. Messages that precede this abend specify in more
detail the nature of the problem.
0148 (hexadecimal 094)
System Action: The system ends subcommand processing.
Explanation: The system detected an internal error.
System Programmer Response: Search problem reporting data
System Action: The system ends subcommand processing.
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.
IPCS-4 OS/390 V2R8.0 MVS System Codes
0149 2052
0149 (hexadecimal 095) 0999 (hexadecimal 3E7)
Explanation: The system detected an internal error. Explanation: The system detected an internal error.
System Action: The system ends subcommand processing. System Action: The system ends subcommand processing.
System Programmer Response: Search problem reporting data System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Support Center.
0150 (hexadecimal 096) 2048 (hexadecimal 800)
Explanation: The system detected an internal error. Explanation: The system detected an internal error.
System Action: The system ends subcommand processing. System Action: The system ends subcommand processing.
System Programmer Response: Search problem reporting data System Programmer Response: Search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. 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 abend. The System Action: The system ends subcommand processing.
system ends subcommand processing.
System Programmer Response: Search problem reporting data
System Programmer Response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM
bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Support Center.
2050 (hexadecimal 802)
0152 (hexadecimal 098)
Explanation: The system detected an internal error.
Explanation: The system detected an internal error.
System Action: The system ends subcommand processing.
System Action: Message BLS03102I precedes the abend. The
System Programmer Response: Search problem reporting data
system ends IPCS processing.
bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: Search problem reporting data Support Center.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. 2051 (hexadecimal 803)
Explanation: The system detected an internal error.
0200 (hexadecimal 0C8)
System Action: The system ends subcommand processing.
Explanation: The system detected an internal error.
System Programmer Response: Search problem reporting data
System Action: The system ends subcommand processing.
bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: Search problem reporting data Support Center.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. 2052 (hexadecimal 804)
Explanation: The system detected an internal error.
0201 (hexadecimal 0C9)
System Action: The system ends subcommand processing.
Explanation: The system detected an internal error.
System Programmer Response: Search problem reporting data
System Action: The system ends subcommand processing.
bases for a fix for the problem. If no fix exists, contact the IBM
System Programmer Response: Search problem reporting data Support Center.
bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
IPCS User Completion Codes IPCS-5
IPCS-6 OS/390 V2R8.0 MVS System Codes
Appendix A. Notices
This information was developed for products and services at those Web sites are not part of the materials for this IBM
offered in the USA. product and use of those Web sites is at your own risk.
IBM may not offer the products, services, or features dis- IBM may use or distribute any of the information you supply
cussed in this document in other countries. Consult your in any way it believes appropriate without incurring any obli-
local IBM representative for information on the products and gation to you.
services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or Licensees of this program who wish to have information
imply that only that IBM product, program, or service may be about it for the purpose of enabling: (i) the exchange of infor-
used. Any functionally equivalent product, program, or mation between independently created programs and other
service that does not infringe any IBM intellectual property programs (including this one) and (ii) the mutual use of the
right may be used instead. However, it is the user's responsi- information which has been exchanged, should contact:
bility to evaluate and verify the operation of any non-IBM
IBM Corporation
product, program, or service.
Mail Station P300
IBM may have patents or pending patent applications cov- 522 South Road
ering subject matter described in this document. The fur- Poughkeepsie, NY 12601-5400
nishing of this document does not give you any license to USA
these patents. You can send license inquiries, in writing, to:
Such information may be available, subject to appropriate
IBM Director of Licensing terms and conditions, including in some cases, payment of a
IBM Corporation fee.
North Castle Drive
The licensed program described in this information and all
Armonk, NY 10504-1785
licensed material available for it are provided by IBM under
USA
terms of the IBM Customer Agreement, IBM International
For license inquiries regarding double-byte (DBCS) informa- Program License Agreement, or any equivalent agreement
tion, contact the IBM Intellectual Property Department in your between us.
country or send inquiries, in writing, to:
If you are viewing this information softcopy, the photographs
IBM World Trade Asia Corporation and color illustrations may not appear.
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan Trademarks
The following paragraph does not apply to the United The following terms are trademarks of the IBM Corporation in
Kingdom or any other country where such provisions the United States or other countries or both:
are inconsistent with local law: INTERNATIONAL BUSI-
NESS MACHINES CORPORATION PROVIDES THIS PUB- AD/Cycle
LICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, AFP
EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT AIX/ESA
LIMITED TO, THE IMPLIED WARRANTIES OF AIX/6000
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS AnyNet
FOR A PARTICULAR PURPOSE. Some states do not allow AT
disclaimer of express or implied warranties in certain trans- BatchPipeWorks
actions, therefore, this statement may not apply to you. BookManager
BookMaster
This information could include technical inaccuracies or C/370
typographical errors. Changes are periodically made to the C/MVS
information herein; these changes will be incorporated in new C++/MVS
editions of the publication. IBM may make improvements CBIPO
and/or changes in the product(s) and/or the program(s) CD Showcase
described in this publication at any time without notice. CICS
CICS OS/2
Any references in this information to non-IBM Web sites are CICS/ESA
provided for convenience only and do not in any manner CICSPlex
serve as an endorsement of those Web sites. The materials CT
DATABASE 2
Copyright IBM Corp. 1988, 1999 A-1
DB2 Open Class
DFS OPC
DFSMS OS/2
DFSMSdfp OS/390
DFSMSdss OS/390 EZ Application Technology
DFSMShsm Parallel Sysplex
DFSMSrmm Print Services Facility
DFSMS/MVS PR/SM
DFSORT PSF
Enterprise Systems Architecture/370 PSL
Enterprise Systems Architecture/390 RACF
ESA/370 Resource Measurement Facility
ESCON RETAIN
Extended Services RMF
FFST S/390
FFST/MVS SAA
GDDM SecureWay
Hardware Configuration Definition SOM
Hiperbatch SOMobjects
Hiperspace SP
IBM Sysplex Timer
IBMLink System/390
IMS SystemView
IMS/ESA VisualLift
IP PrintWay VTAM
Language Environment
MQSeries UNIX is a registered trademark in the United States and
MVS other countries licensed exclusively through X/Open
MVS/DFP Company Limited.
MVS/ESA
Other company, product, or service names may be trade-
MVS/SP
marks or service marks of others.
MVS/XA
NetView
A-2 OS/390 V2R8.0 MVS System Codes
Communicating Your Comments to IBM
OS/390
MVS System Codes
Publication No. GC28-1780-10
If you especially like or dislike anything about this book, please use one of the methods listed below to send your comments to
IBM. Whichever method you choose, make sure you send your name, address, and telephone number if you would like a
reply.
Feel free to comment on specific errors or omissions, accuracy, organization, subject matter, or completeness of this book.
However, the comments you send should pertain to only the information in this manual and the way in which the information is
presented. To request additional publications, or to ask questions or make comments about the functions of IBM products or
systems, you should talk to your IBM representative or to your IBM 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.
If you are mailing a readers' comment form (RCF) from a country other than the United States, you can give the RCF to the
local IBM branch office or IBM representative for postage-paid mailing.
If you prefer to send comments by mail, use the RCF at the back of this book.
If you prefer to send comments by FAX, use this number:
1-(914)-432-9405
If you prefer to send comments electronically, use this network ID:
[email protected]
Make sure to include the following in your note:
Title and publication number of this book
Page number or topic to which your comment applies.
Readers' Comments — We'd Like to Hear from You
OS/390
MVS System Codes
Publication No. GC28-1780-10
Overall, how satisfied are you with the information in this book?
Very Very
Satisfied Satisfied Neutral Dissatisfied Dissatisfied
Overall satisfaction Ø Ø Ø Ø Ø
How satisfied are you that the information in this book is:
Very Very
Satisfied Satisfied Neutral Dissatisfied Dissatisfied
Accurate Ø Ø Ø Ø Ø
Complete Ø Ø Ø Ø Ø
Easy to find Ø Ø Ø Ø Ø
Easy to understand Ø Ø Ø Ø Ø
Well organized Ø Ø Ø Ø Ø
Applicable to your tasks Ø Ø Ø Ø Ø
Please tell us how we can improve this book:
Thank you for your responses. May we contact you? Ø Yes Ø No
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.
Name Address
Company or Organization
Phone No.
Cut or Fold
Readers' Comments — We'd Like to Hear from You
IBM
Along Line
GC28-1780-10
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
Department 55JA, Mail Station P384
522 South Road
Poughkeepsie, NY 12601-5400
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
GC28-1780-10 Along Line
IBM
Program Number: 5647-A01
Printed in the United States of America
on recycled paper containing 10%
recovered post-consumer fiber.
GC28-178ð-1ð
You might also like
- Relevance of Free Jet Model For Soil Erosion by Impinging JetsNo ratings yetRelevance of Free Jet Model For Soil Erosion by Impinging Jets15 pages
- Cisco CCNA Command Guide: An Introductory Guide for CCNA & Computer Networking Beginners: Computer Networking, #3From EverandCisco CCNA Command Guide: An Introductory Guide for CCNA & Computer Networking Beginners: Computer Networking, #34.5/5 (2)
- 23 July 2024 - Comprehensive Review of Depression Detection Techniques Based On Machine Learning ApproachNo ratings yet23 July 2024 - Comprehensive Review of Depression Detection Techniques Based On Machine Learning Approach25 pages
- The Linux Shell Scripting Handbook - From Journeyman to MasterFrom EverandThe Linux Shell Scripting Handbook - From Journeyman to MasterNo ratings yet
- CAN Bus for Beginners: A Practical Guide to Automotive NetworkingFrom EverandCAN Bus for Beginners: A Practical Guide to Automotive NetworkingNo ratings yet
- Lab Report-03 (ME-339 Control Engineering Lab)No ratings yetLab Report-03 (ME-339 Control Engineering Lab)6 pages
- Paper - On-Site Investigation Techniques For The Structural Evaluation of Historic Masonry BuildingsNo ratings yetPaper - On-Site Investigation Techniques For The Structural Evaluation of Historic Masonry Buildings8 pages
- Term 1: Mechanics and Thermodynamics: Chapter 2: KinematicsNo ratings yetTerm 1: Mechanics and Thermodynamics: Chapter 2: Kinematics7 pages
- Adaptive Kalman Filtering For INS and GPSNo ratings yetAdaptive Kalman Filtering For INS and GPS11 pages
- Energy For Sustainable Development: Martin Anyi, Brian KirkeNo ratings yetEnergy For Sustainable Development: Martin Anyi, Brian Kirke7 pages
- The Linux Terminal for Advanced Users - The Command Line Made Easy: First EditionFrom EverandThe Linux Terminal for Advanced Users - The Command Line Made Easy: First EditionNo ratings yet
- GC28-1780-10 OS390 MVS System Codes PDFNo ratings yetGC28-1780-10 OS390 MVS System Codes PDF320 pages
- Systems OS/VS2 MVS Data Management Services GuideNo ratings yetSystems OS/VS2 MVS Data Management Services Guide215 pages
- Systems Introduction To VTAM: Virtual Telecommunications Access Method (VT AM)No ratings yetSystems Introduction To VTAM: Virtual Telecommunications Access Method (VT AM)56 pages
- Open Systems Adapter-Express Integrated Z9No ratings yetOpen Systems Adapter-Express Integrated Z982 pages
- School of Mechanical Engineering MEE437 Operations Research - FS 2016-17 - PBL Faculty: Siva Prasad Darla Project Based Learning CourseNo ratings yetSchool of Mechanical Engineering MEE437 Operations Research - FS 2016-17 - PBL Faculty: Siva Prasad Darla Project Based Learning Course5 pages
- CICS TS For ZOS - System Programming ReferenceNo ratings yetCICS TS For ZOS - System Programming Reference633 pages
- Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language ModelsFrom EverandSecuring ChatGPT: Best Practices for Protecting Sensitive Data in AI Language ModelsNo ratings yet
- Cybersecurity for Executives: A Guide to Protecting Your BusinessFrom EverandCybersecurity for Executives: A Guide to Protecting Your BusinessNo ratings yet
- GC28-0629-3 OS VS2 MVS System Programming Library TSONo ratings yetGC28-0629-3 OS VS2 MVS System Programming Library TSO127 pages
- Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ ScriptingFrom EverandAdvanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ ScriptingNo ratings yet
- PX-760/PX-860/AP-260/AP-460/PX-160 MIDI Implementation: Casio Computer Co., LTDNo ratings yetPX-760/PX-860/AP-260/AP-460/PX-160 MIDI Implementation: Casio Computer Co., LTD51 pages
- An Efficient Algorithm For 3D Rectangular Box PackingNo ratings yetAn Efficient Algorithm For 3D Rectangular Box Packing4 pages
- MVS System Messages, Vol 7 (IEB-IEE) PDFNo ratings yetMVS System Messages, Vol 7 (IEB-IEE) PDF622 pages
- OS - VS Message Library - VS2 System CodesNo ratings yetOS - VS Message Library - VS2 System Codes214 pages
- Xpediter/Tso and Xpediter/Ims Reference Manual: Release 7.2No ratings yetXpediter/Tso and Xpediter/Ims Reference Manual: Release 7.2228 pages
