OS_VS Message Library_ VS2 System Codes

GC38-1008-9File No. S370-40

SystemsOS/VS MessageLibrary: VS2System Codes

Tenth Edition (December 1984)

This is a major revision of, and obsoletes, GC38-1008-8. See the Summary ofAmendments following the Contents for a summary of the changes made to this manual.Technical changes or additions to the text are indicated by a vertical line to the left of thechange.

This edition applies to MVS/System Product Version 1 through release 3.4 and to allsubsequent releases until otherwise indicated in new editions or Technical Newsletters.Changes are made periodically to the information herein; before using this publication inconnection with the operation of IBM systems, consult the IBM System/370 and 4300Processors Bibliography, GC20-0001, for the editions that are applicable and current.

References in this publication to IBM products, programs, or services do not imply thatIBM intends to make these available in all countries in which IBM operates. Anyreference to an IBM program product in this publication is not intended to state or implythat only IBM's program product may be used. Any functionally equivalent programmay be used instead.

Publications are not stocked at the address given below. Requests for IBM publicationsshould be made to your IBM representative or to the IBM branch office serving yourlocality.

A form for readers' comments is provided at the back of this publication. If the form hasbeen removed, comments may be addressed to IBM Corporation, InformationDevelopment, Department D58, Building 920-2, PO Box 390, Poughkeepsie, New York12602. IBM may use or distribute whatever information you supply in any way itbelieves appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 1982, 1984

Preface

This publication lists and describes:

• The completion codes issued by the MVS/370operating system when it uses an ABENDmacro instruction to terminate abnormally atask or address space.

• The wait state codes placed in the programstatus word (PSW) when the system begins await state.

• Causes of uncoded wait states.

• The wait state codes placed in the last fourbytes of the PSW when the stand-alone dumpprogram (SADMP) enters a wait state.

• Causes of loops.

The descriptions suggest responses by the operatorand, where appropriate, by the programmer. Manydescriptions state that an error record is written tothe SYS1.LOGREC data set. This error record isdescribed in OS/VS2 MVS System ProgrammingLibrary: SYS1.LOGREC Error Recording,GC28-0677, and in OS/VS2 System ProgrammingLibrary: Debugging Handbook, Volume 1,GC28-1047.

The description of most codes ends with a problemdetermination paragraph, which lists suggestedactions as items in tables; the problem

determination tables are at the back of thepublication. You should perform the actions forthe items listed in the code description beforeasking your IBM branch office for programming orhardware support.

The sections on system completion codes and waitstate codes begin with information useful to thosereceiving these codes. Remember to read theseintroductions.

The appendix lists the modules that detect and issuesystem completion codes and wait state codes.

Who Should Use this Publication

This publication is needed by operators, systemprogrammers, and applications programmers.

Associated Publications

Many system completion and wait state codes referto messages. See MVS/370 Message Library:System Messages, Volume 1, GC28-1374, andVolume 2, GC28-1375. These volumes give themessage text and explanation for many systemmessages and list the publications containing allother system messages.

Publications cited in this book or containingprocedures or concepts mentioned include:

Order Number

GA22-7000GA24-3343LC28-1371GC26-3792SH35-0060SC33-0143GC27-6995GC28-0674

Title

IBM System/370 Principles of OperationIBM 3203/3211 Printer and 3811 Control Unit Component DescriptionsJES3 System Programming Library: User Modifications and Macros

OS/VS2 System Generation ReferencePrint Services Facility MessagesIBM Graphics Access Method/System Product: Messages and CodesVTAM Macro Language Reference

OS/VS2 MVS System Programming Library: Service Aids

Preface iii

GC28-1029 OS/VS2 MVS System Programming Library: Initialization and Tuning Guide

GC28-0683 OS/VS2 MVS Supervisor Services and Macro Instructions

SY28-1133 OS/VS2 System Programming Library: MVS Diagnostic Techniques

GC28-1031 Operator's Library: OS/VS2 MVS System Commands

GC28-1046 OS/VS2 System Programming Library: Supervisor

SC30-3152 ACF/TCAM Version 2 Support for IBM Subsystems

SH2O-9028 IMS/VS V1 Operator's Reference

SY26-3823 OS/VS2 Input/ Output Supervisor Logic

LYB8-1051 OS/VS2 Data Areas (JES2)

LYB8-1055 OS/VS2 Data Areas (JES3)

iv OS/VS Message Library: VS2 System Codes

Contents

System Completion Codes SCC-1Completion Code Format SCC-1Abnormal Termination of Subtasks SCC-1

Wait State Codes WSC-1

Uncoded Wait States UWS-1

Stand-Alone Dump Wait State Codes SAD-1

Loops LOP-1

Problem Determination PRB-1TABLE I PRB-1TABLE II PRB-3TABLE III PRB-4

Appendix: Code to Module Tables CMT-1System Completion Code to Module Table CMT-2Wait State Code to Module Table CMT-7

Contents v

vi OS/VS Message Library: VS2 System Codes

Contents Directory

System Completion (ABEND) Codes ABEND

Wait State Codes WT CDS

Uncoded Wait States UNCDED

Stand-Alone Dump Wait State Codes SADMP

Loops LOOPS

Problem Determination PROB

Appendix: Code to Module Tables CD/MOD

Contents Directory V11

viii OS/VS Message Library: VS2 System Codes

Summary of Amendments

Summary of Amendmentsfor GC38-1008-9as updated December 21, 1984

This revision supports MVS/System Product - JES3Version Release 1.3.4 program number 5740-XYN.

Changes to the system completion codes issued byJES3 include: 1FB, 2FB, 3FB, 4FB, 5FB, 6FB,722, 7FB, 8FB, 9FB, AFB, BFB, and CFB.

This revision also includes the addition of one newcode: DFB.

Summary of Amendmentsfor GC38-1008-8as updated September 14, 1984

The technical changes and additions in this revisionare:

• New system completion codes 024 and 027 tosupport the Print Services. Facility (PSF).

• New system completion codes 0A1, 0A2, 0A3,0A4, 0A5, 147, 149, 14A, 14B and 247 tosupport the Graphics Access Method/SystemProduct.

• Service updates.

In addition to the technical information, thefollowing changes have been made to the format ofthis manual:

• This edition is printed in ten-point type, ratherthan the smaller eight-point type used inprevious editions.

• The seven separate sections listed in theContents Directory now have separate paging.

• The text following each system completion codeand each wait state code is indented to offsetthe code number and make them easier to find.

• Dictionary-type headings appear at the top ofeach page in the system completion codes andwait state codes sections of the manual. Theheadings indicate which code or codes aredocumented on the given page.

All of these changes have been made to improve theusability of this manual. Most of the changes weremade in response to user requests. If you have anycomments or suggestions to further improve thismanual please feel free to use the form for reader'scomments provided at the back of the manual.

Summary of Amendmentsfor GC38-1008-7as updated December 30, 1983by TNL GN28-0873

This TNL contains:

• A new system completion code, 02C, issued tosupport MVS/System Product - JES2 Version 1Release 3.4 program number 5740-XYS.

• Service updates.

Summary of Amendments ix

x OS/VS Message Library: VS2 System Codes

Introduction

The OS/VS Message Library is designed so that you can havethe messages and codes documentation that fits your specificneeds. You no longer have to maintain an enormous manual;instead, you can tailor message documentation to meet yourparticular needs. See Figure 1 for an overview of how tocustomize your OS/VS Message Library.If you are a system programmer or installation manager, youmay want to have all the books in the Message Library in aconsolidated document.If you are an operator, you may want to include SystemMessages and System Codes in your Operator's Library.If you are an assembler language programmer, you may wantto have System Messages, System Codes, Linkage Editor andLoader Messages, and the message section from the AssemblerLanguage Programmer's Guide in a consolidated document.If you are a COBOL programmer, you may want VS1 UtilitiesMessages or VS2 Utilities Messages added to your COBOLprogrammer's guide.In any case, you can select the appropriate books to build aMessage Library to meet your needs. For a list of the bookscontaining documentation for OS/VS messages and codes, seeFigure 2. Figure 3 can be used to locate the documentation fora specific message.

Basic Books

Each installation will require at least one copy of VS1 SystemMessages or VS2 System Messages. You will receive at theconsole or in your output listings, some subset of themessages in these books, no matter which options have beenincluded in your operating system. All programming personnel,especially operations personnel, will require access to thesebooks; although it may not be necessary forapplications-oriented personnel to have their own copies.Each installation must have at least one copy of VS1 SystemCodes or VS2 System Codes, which contains the systemcompletion codes and wait state codes. All programmingpersonnel, especially operations personnel, will require accessto one of these books, although applications-orientedpersonnel may not need to have their own copies.

Optional Books

Routing and Descriptor Codes contains routing and descriptorcodes for all messages that have these codes. Yourinstallation's system programmer will need this book, especiallyif your operating systems have multiple console support(MCS).Depending on your requirements, you may want to have copiesof VS 1 Utilities Messages or VS2 Utilities Messages or LinkageEditor and Loader Messages. Select the books that you need,and keep them either in the appropriate System Library Manualor in your customized Message Library.

Introduction 1

Figure 1. Customizing Your OS/VS Message Library

2 VS2 System Codes

OS/VS2 Message Library

Publication Order Number Contents

VS1 Utilities Messages GC26-3919 IBC, IEB, IEH messages

VS2 Utilities Messages GC26-3920 IBC, IEB, IEH messages

TCAM Level 10 Messages GC30-3044 IED messages (for TCAM level 10 and above)OS/VS Display Exception Monitoring Facility GC34-2003 BNG messages(DEMF) User's Guide

Interactive Problem Control System (IPCS) GC34-2007 BLS messagesMessages and Codes

Mass Storage System Messages GC38-1000 ICB, ICG, ISDA messagesVS1 System Messages GC38-1001 HHL, HMA, HMB, HMD, ICF, ICT, ICU, IDA,

IDC, IEA, IEC, IEE, IEF, IEI, IFA, IFB, IFCmessages for IFCDIPOO, IFD, IGF, IHB, IHJ,IHK, IMC, ISDA, IST messages

VS2 System Messages GC38-1002 AHL, AMx, ERB, HASP, ICF, ICP messages foroperator, ICT, ICU, IDA, IDC, IEA, IEC, IED,IEE, IEF, IEI, IFA, IFB, IFC, IFD, IGF, IHJ,IKJ, IKM, IKT, ILR, IPD, IRA, IRB, ISTmessages

VS1 System Codes GC38-1003 all VS1 completion and wait state codesLinkage Editor and Loader Messages GC38-1007 IEW messagesVS2 System Codes GC38-1008 all VS2 completion and wait state codes

VS1 RES RTAM and Account Messages GC38-1010 IFS and IKJ messagesSubsystem Support Services Messages GC38-1011 BQB messages

JES3 Messages GC38-1012 IAT messagesEREP Messages GC38-1045 IFC messages for IECEREPO and IFCEREP1 onlyVS2 TSO Terminal Messages GC38-1046 IKJ and IKT messagesVS1 Routing and Descriptor Codes GC38-1101 all VS1 routing and descriptor codesVS2 Routing and Descriptor Codes GC38-1102 all VS2 routing and descriptor codes

In other publications:

Emulator publications See: IBM emulator messagesSystem/370Bibliography,GC20-0001

IBM 3790 Communication System: Messages GA27-2789 BQI messagesOS/VS MVS VPSS Installation and Operation GC24-5124 IGT messagesGuide

OS/VS1 and OS/VS2 MVS VPSS GC24-5125 IGT messagesProgrammer's Guide

OS/VS and DOS/VS Analysis Program-1 (AP-1) GC26-3855 IAP messagesUser's Guide

IBM 3600 Finance Communication System: Host GC27-0005 BQK messagesService Programs Reference

IBM 3600 Finance Communication System: GC27-0003 BQK messagesInstructions and Macros Reference

Problem Determination Aids and Messages and GC27-6974 IFF messagesCodes for Graphic Programming Services(GPS) and Graphic Subroutine Package (GSP)

DOS/VS and OS/VS TOLTEP for VTAM GC28-0663 ITA messagesOS/VS System Modification Program (SMP) GC28-0673 HMA messagesOS/VS2 MVS and Stand-Alone Versions: GC28-1027 ICP messagesInput/Output Configuration Program User'sGuide and Reference

Figure 2. OS/VS Message Library (Part 1 of 2)

Introduction 3

Publication Order Number

Contents

IBM 3 704 and 3705 Control ProgramGeneration and Utilities Guide and ReferenceManual

IBM System 370 Subsystem Support ServicesUser's Guide

IBM 3 705 Advanced Communication Functionfor Network Control Program/VS Generationand Utilities Reference ManualOS/VS — VM/370 Assembler Programmer'sGuide

IBM 3 790 Communication System: Data EntryConfiguration Batch Transfer ProgramOS/VS I — OS/VS2 User's Guide

Device Support FacilitiesDocument Composition Facility MessagesDocument Library FacilityOS Assembler H MessagesNetwork Communications Control Facility:

MessagesOS/VS2 MVS TSO 3270 Extended DisplaySupport — Session Manager User's Guide andReference

IBM OS Full American National StandardCOBOL Compiler and Library, Version 4Programmer's Guide

IBM OS/VS COBOL Compiler and LibraryProgrammer's Guide

IBM System/360 OS/TSO Terminal User'sSupplement for FORTRAN IV (GI) Processorand TSO Fortran Prompter

IBM OS FORTRAN IV (H Extended) Compilerand Library (Mod II) Messages

OS PL/I Optimizing Compiler: MessagesOS PL/I Checkout Compiler: MessagesOS/VS Sort/Merge Programmer's GuideCICS/MS Version I, Release 3 Messages and

CodesNetwork Problem Determination Application:

Messages and CodesACF/VTAM Messages and Codes

OS/VS2 MVS Resource Access Control Facility(RACF) Messages and Codes

IMS/VS Version I: Messages and CodesVSPC FORTRAN Terminal User's GuideVS APL Installation Reference MaterialVS APL for CMS: Terminal User's GuideVS Personal Computing (VSPC): Installation

Reference Material DB/DC Data Dictionary: Terminal User's Guide

and Command ReferenceVS TSIO Guide and ReferenceOS/MVT and OS/VS DASDR User's Guide

OS/VS2 MVS Hierarchical Storage Manager:MessagesOS/VS Mass Storage System ExtensionsMessages

GC30-3008 IFL messages

GC30-3022 BQB messages

SC30-3116 IFL messages

GC33-4021 IFO messages

GC33-5901 BQM messages

GC35-0033 ICK messages

LYB0-8070 DSM messages

LYB0-8071 DSM messages

SC26-3770 IEV messages

SC27-0431 DSI messages

SC28-0912 ADF messages

SC28-6456 IKF messages

SC28-6483 IKF messages

SC28-6855 IGI, IHN messages

SC28-6865 IFE, IHO messages

SC33-0027 IBM, IEL, IKJ messages

SC33-0034 DMS, IEN, IKJ messages

SC33-4035 ICE messages

SC33-0081 DFH messages

SC34-2021 BNH messages

SC38-0271 IST messages

SC38-1014 ICH messages

SH20-9030 DBD, DFS, DBF messages

SH20-9062 AFP messages

SH20-9065 APLL, APLP messages

SH20-9067 APL messages

SH20-9072 ASU messages

SH20-9083 DBD messages

SH20-9107 DSGB messages

SH20-9111 DRU, DRW messages

SH35-0025 ARC messages

SH35-0041 ICB, ICG messages

Figure 2. OS/VS Message Library (Part 2 of 2)

4 VS2 System Codes

OS/VS Message Directory

Prefix Component Publication Title Order Number

ADF TSO Session Manager OS/VS2 MVS TSO 3270 Extended SC28-0912Display Support - Session ManagerUser's Guide and Reference

AFP VSPC FORTRAN VSPC FORTRAN Terminal User's SH20-9062Guide

AHL Generalized Trace Facility VS2 System Messages GC38-1002

AMA AMAPTFLE VS2 System Messages GC38-1002AMASPZAP

AMB AMBLIST VS2 System Messages GC38-1002

AMD AMDPRDMP VS2 System Messages GC38-1002AMDSADMP

APL VS APL under CMS VS APL for CMS: Terminal SH20-9067User's Guide

APLL VS APL Library Service Program VS APL Installation Reference SH20-9065Material

APLP VS APL under VSPC VS APL Installation Reference SH20-9065Material

ARC Hierarchical Storage Manager OS/VS2 MVS Hierarchical Storage SH35-0025Manager Messages

ASU VSPC . VS Personal Computing (VSPC): SH20-9072Installation Reference Material

BLS IPCS OS/VS2 MVS Interactive Problem GC34-2007Control System(IPCS) Messages and Codes

BNG DEMF OS/VS Display Exception Monitoring GC34-2003Facility (DEMF) User's Guide

BNH Network Problem Determination Application Network Problem Determination SC34-2012Application: Messages and Codes

BQB Subsystem Support Services IBM System/370 Subsystem Support GC38-1011Services MessagesIBM System/370 Subsystem Support GC30-3022Services User's Guide

BQI 3790 Communication System IBM 3790 Communication GA27-2789System: Messages

,

BQK 3600 Finance Communication System IBM 3600 Finance Communication GC27-0005System: Host Service ProgramsReferenceIBM 3600 Finance Communication GC27-0003

. System: Instructions andMacros Reference

Figure 3. OS/VS Message Directory (Part 1 of 5)

Introduction 5


BQM Batch Transfer IBM 3790 Communication System: GC33-5901Data Entry ConfigurationBatch Transfer ProgramOS/VS1 - OS/VS2 User's Guide

DBD DB/DC Data Dictionary DB/DC Data Dictionary SH20-9084Installation GuideDB/DC Data Dictionary 5H20-9083Terminal User's Guideand Command ReferenceIMS/VS Version 1: 5H20-9030Messages and Codes

DBF Fastpath IMS/VS Version 1: Messagesand Codes

5H20-9030

DFH CICS/VS CICS/VS Version 1, Release 4 SC33-0081Messages and Codes

DFS I MS /VS IMS/VS Version 1: Messagesand Codes

5H20-9030

DMS PL/I Checkout Compiler OS PL/I Checkout Compiler: SC33-0034Messages

DRU/ DASDR OS/MVT and OS/VS DASDR SH20-9111DRW User's Guide

DSGB VS TSIO VS TSIO Guide and Reference 5H20-9107

DSI Network Communications Control Facility Network Communications Control SC27-0431Facility: Messages

DSM Document Composition Facility Document Composition Facility LYBO-8070Messages

Document Library Facility Document Library Facility LYBO-8071Messages

ERB Resource Measurement Facility (RMF) VS2 System Messages GC38-1002

HASP JES2 VS2 System Messages GC38-1002Network Job Entry Facility for JES2

HHL Generalized Trace Facility VS1 System Messages GC38-1001

HMA HMAPTFLE VS1 System Messages GC38-1001HMASPZAPHMASMP System Modification Program GC28-0673

HMB HMBLIST VS1 System Messages GC38-1001

HMD HMDPRDMP VS1 System Messages GC38-1001HMDSADMP

IAP Analysis Program-1 OS/VS and DOS/VS Analysis GC26-3855Program-1 (AP1) User's Guide


6 VS2 System Codes


IAT JES3 JES3 Messages GC38-1012

IBC Independent Utility VS1 Utilities Messages GC26-3919VS2 Utilities Messages GC26-3920

IBM PL/I Transient Library PL/I Optimizing Compiler: SC33-0027Messages

ICB Mass Storage System Communicator Mass Storage System (MSS) GC38-1000MessagesMass Storage System SH35-0041Extensions Messages

ICE Sort/ Merge OS/VS Sort/Merge Programmer's SC33-4035Guide

ICF Power Warning Feature VS1 System Messages GC38-1001VS2 System Messages GC38-1002

ICG Mass Storage Control Table Createand Trace Reports

Mass Storage System (MSS)Messages

GC38-1000

Mass Storage System SH35-0041Extensions Messages

ICH RACF OS/VS2 MVS Resource Access SC38-1014Control Facility (RACF)Messages and Codes

ICK Device Support Facilities Device Support Facilities GC35-0033

ICP IOCP (messages for operator) VS2 System Messages GC38-1002IOCP (messages for programmer) OS/VS2 MVS and Stand-Alone GC28-1027

Versions:Input/Output Configuration ProgramUser's Guide and Reference

ICT Programmed Cryptographic Facility VS1 System Messages GC38-1001VS2 System Messages GC38-1002

ICU Cryptographic Unit Support VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IDA VSAM Control Block Expansion VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IDC Access Method Services VS1 System Messages GC38-1001VS2 System Messages GC38-1002

lEA Supervisor VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IEB Data Set Utility VS1 Utilities Messages GC26-3919VS2 Utilities Messages GC26-3920

IEC Data Management VS1 System Messages GC38-1001VS2 System Messages G C38-1002

IED TCAM Level 9 and below VS2 System Messages GC38-1002TCAM Level 10 TCAM Level 10 Messages GC30-3044ACF/TCAM ACF/TCAM Messages SC30-3120

IEE Master Scheduler VS1 System Messages GC38-1001VS2 System Messages GC38-1002


Introduction 7


IEF Job Scheduler VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IEH System Utility VS1 Utilities Messages GC26-3919VS2 Utilities Messages GC26-3920

IEl System Generation VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IEL PL/I Optimizing Compiler OS PL/I Optimizing Compiler: SC33-0027Messages

IEN PL/I Checkout Compiler OS PL/I Checkout Compiler: SC33-0034Messages

IEV Assembler H OS Assembler H Messages SC26-3770

IEW Loader and Linkage Editor Linkage Editor and Loader Messages GC38-1007

IFA SMF Dump Program VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IFB Environment Recording VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IFC IFCDIP00 (SYS1.LOGREC initialization) VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IFCEREPO and IFCEREP1 EREP Messages GC38-1045

IFD Online Test Executive VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IFE FORTRAN IV (H Extended) IBM OS FORTRAN IV (H Extended) SC28-6865Compiler and Library (MOD II)Messages

IFF Graphic Programming Services OS/VS Problem Determination GC27-6974Aids and Messages and Codesfor GPS and GSP

IFL Network Control Program IBM 3704 and 3705 Control Program GC30-3008Generation and Utilities Guideand Reference Manual

ACF for Network Control Program IBM 3705 Advanced Communications SC30-3116Function for Network ControlProgram/VS Generation andUtilities Reference Manual

IFO Assembler OS/VS - VM/370 Assembler GC33-4021Programmer's Guide

IFS Remote Terminal Access Method (RTAM) VS1 RES RTAM and Account GC38-1010Messages

IGF Recovery Management VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IGI FORTRAN IV (G1) IBM System/360 OS/TSO Terminal SC28-6855User's Supplement for FORTRANIV (G1) Processor and TSOFORTRAN Prompter

IGT Vector Processing Subsystem OS/VS2 MVS VPSS Installationand Operation Guide

GC24-5124

OS/VS1 OS/VS2 MVS VPSS GC24-5125Programmer's Guide


8 VS2 System Codes

Prefix Component Publication Title Order Number----

IHB Macro Expansion (documentedfor VS1 only)

VS1 System Messages GC38-1001

IHJ Checkpoint/ Restart VS1 System Messages GC38-1001VS2 System Messages GC38-1002

IHK Conversational Remote Job Entry (CRJE) VS1 System Messages GC38-1001

IHO FORTRAN IV Library IBM OS FORTRAN IV (H Extended) SC28-6865(Mod II) Compiler and Library (Mod II)

Messages

IKF Full American National Standard COBOL IBM OS Full American National SC28-6456Standard COBOL Compilerand Library, Version 4Programmer's GuideIBM OS/VS COBOL Compilerand Library Programmer's

SC28-6483

Guide

IKJ Time Sharing Option VS2 System Messages GC38-1002VS2 TSO Terminal Messages GC38-1046

Account Facility VS1 RES RTAM and Account GC38-1010Messages

PL/I Prompter OS PL/I Optimizing Compiler: 5C33-0027MessagesOS PL/I Checkout Compiler: SC33-0034Messages

IKM PL/I Syntax Checker VS2 System Messages GC38-1002

IKT TSO/VTAM VS2 System Messages GC38-1002VS2 TSO Terminal Messages GC38-1046

ACF/VTAM ACF/VTAM Messages and Codes,Release 1

5C38-0271

ACF/VTAM Messages and Codes,Release 2

SC27-0470

ILR Auxiliary Storage Management VS2 System Messages GC38-1002

IMC I MCJOBQD VS1 System Messages GC38-1001IMCOSJCD

IPD FORTRAN Syntax Checker VS2 System Messages GC38-1002

IRA System Resources Manager VS2 System Messages GC38-1002

IRB MF/1 VS2 System Messages GC38-1002

ISDA ISDASDAO VS1 System Messages GC38-1001Mass Storage System (MSS) GC38-1000MessagesMass Storage System 5H35-0041Extensions Messages

IST ACF/VTAM ACF/VTAM Messages and Codes,Release 1

SC38-0271

ACF/VTAM Messages and Codes,Release 2

5C27-0470

VTAM VS1 System Messages GC38-1001VS2 System Messages GC38-1002

ITA DOS/VS and OS/VS TOLTEP TOLTEP for VTAM GC28-0663


Introduction 9

10 VS2 System Codes

ABEND

System Completion Codes

Completion codes are issued by the system or by aproblem program when either uses an ABENDmacro instruction. The ABEND macro abnormallyterminates a task or address space. The codeindicates why the task or address space wasterminated.

The system issues an ABEND when it determinesthat a task or address space cannot continueprocessing and produce valid results. For example,a task may try an invalid operation. Or, aninput/output operation may fail.

A problem program issues an ABEND when itdetermines that it cannot continue processing andproduce valid results. For example, a problemprogram may be calculating a total by successiveadditions. After each addition, the new total ischecked against a limit. If the total exceeds thelimit, the problem program issues an ABENDmacro instruction to terminate abnormally and,perhaps, to ask for a diagnostic dump.

Completion Code Format

The system and user completion codes appeartogether in the task completion code field(TCBCMP) of the task control block (TCB) for theterminated task.

For abnormal termination by the system, thesystem completion code is a three-digit hexadecimalnumber, which is listed in this publication, and theuser code is 0000.

For abnormal termination by the problem program,the system completion code is 000 and the user codeis supplied by the problem program as a four-digitdecimal number coded in the ABEND macroinstruction.

Note: Only the system completion codes appear inthis publication. User codes are meaningful onlyfor the specific application.

Abnormal Termination of Subtasks

When the highest level task in a job step terminatesabnormally, the job step will terminate abnormally.

When a subtask terminates abnormally, only thesubtask itself and its subtasks are terminated.Subtask termination is indicated by the completioncode in the event control block (ECB) specifiedwhen the subtask was attached and in theTCBCMP field of the TCB for the subtask.

A low level subtask that terminates abnormally canindirectly cause the entire job step to terminateabnormally. To do so, each subtask in the job step'stask chain must terminate itself abnormally when itfinds an ABEND completion code from one of itssubtasks. To terminate the job step with thecompletion code indicating the error in the failingsubtask, each subtask must use the completion codefrom its subtask as its own completion code.

A subtask can also cause abnormal termination ofthe entire job step if the STEP operand wasspecified in the ABEND macro instruction.

System Completion Codes SCC-1

001 to 004

001

Explanation: An input/output error occurredduring BDAM, BISAM, BPAM, BSAM,QISAM, or QSAM processing.

Refer to message IEC020I for information aboutthe task that was terminated.

If message IEC020I was not issued, COBOL wasrunning. CLOSE processing calledend-of-volume (EOV), and EOV processingfound insufficient space.

Programmer Response: Respond as indicated formessage IEC020I.

Problem Determination: Table I, items 1, 2, 3,5a, 15, 29.

002

Explanation: This system completion code isaccompanied by message IEC036I. Refer tomessage IEC036I for information about the taskthat was terminated and for an explanation ofthe return code in register 15.

For all return codes except 2C, the erroroccurred while the control program wasprocessing a sequential data set with BSAM orQSAM, or creating a direct organization dataset.

For return code 2C, the error occurred while thecontrol program was opening an ISAM data setfor QISAM load mode. Too many tracks werespecified for cylinder overflow, or DCBBLKSIZE was not a multiple of DCB LRECL,or DCB BLKSIZE was greater than the tracksize.

System Action: For all return codes except 2C,pertinent control blocks are written to the GTFtrace data set, the user's DCB ABEND exit istaken, if provided, and message IEC036I isissued.

Programmer Response: See message IEC036I forresponses to each return code except 2C. Forreturn code 2C, change the CYLOFL operandof the DCB macro instruction to reflect the

correct number of tracks, or correct the DCBBLKSIZE.

Problem Determination: Table I, items 1, 3, 5a,15, 29. Table II, format 3.

003

Explanation: The error occurred duringend-of-block processing using either BSAM orQSAM. The error occurred because the I/Omacro instructions for a 3525-associated data setwere not executed in the proper sequence.

Register 15 contains a hexadecimal reason code:

ReasonCode Explanation

01 A READ sequence error02 A PUNCH sequence error03 A PRINT sequence error

System Action: The system terminates the task.

Programmer Response: Specify the I/O macroinstructions in the proper sequence, and rerunthe job.

Problem Determination: Table I, items 1, 5a, 15,16, 29.

004

Explanation: The error occurred during OPENprocessing using either BSAM or QSAMbecause a conflicting or invalid DCB parameter(FUNC or related parameter) is specified.



01 Invalid DCB FUNC parameter specified.

02 Invalid combination of DCB FUNC parameterand CNTRL macro specified.

03 Conflicting access methods specified.

04 Invalid DCB specified for 3505 or 3525.

05 Invalid format card or an invalid device specifiedwith Optical Mark Read (OMR).

06 Data protection image not found in theSYS1.IMAGELIB data set, volume containingSYS1.IMAGELIB not mounted, orSYS1.IMAGELIB data set not cataloged.

SCC-2 OS/VS Message Library: VS2 System Codes

005 to 020

ABEND

System Action: In all cases, the systemterminates the task.

Programmer Response: In all cases, correct theinvalid fields of the DCB macro instruction andrerun the job.


005

Explanation: The error occurred because of aninvalid DECB during READ processing usingBSAM. This system completion code isaccompanied by message IEC041I. Refer tomessage IEC041I for information about the taskthat was terminated and for an explanation ofthe return code, rc, in the message text.

System Action: The task is terminated.

Programmer Response: Make sure that the RBLtype of read is used and that the area addressand header address parameters are specified sothat the DECB is valid.


006

Explanation: The program had incorrectauthorization to run a 1419. This completioncode is accompanied by message IEC1021.


Programmer Response: See message IEC1021 forthe proper response.

Problem Determination: Table I, items 1, 17b,29.

008

Explanation: The error occurred duringexecution of a SYNAD routine. The routinewas given control following execution of aBSAM CHECK macro instruction.

The SYNAD routine returned control to thecontrol program for the CHECK macroinstruction.

Programmer Response: Correct the SYNADroutine so that the control program save area isnot destroyed. Then execute the job step again.

Problem Determination: Table I, items 1, 3, 5b,15, 29.

013

Explanation: The error occurred duringexecution of an OPEN macro instruction. Thissystem completion code is accompanied bymessage IEC141I. Refer to message IEC141 Ifor information about the task that wasterminated and for an explanation of the returncode (rc in the message text) in register 15.


Problem Determination: Table I, items 1, 3, 5b,15, 16, 29.

014

Explanation: An error occurred duringexecution of a CLOSE macro instruction for aBDAM data set. This completion code isaccompanied by message IEC208I. Refer tomessage IEC208I for information about the taskthat was terminated and for an explanation ofthe return code (rc in the message text) inregister 15.


Problem Determination: Table I, items 1, 3, 5a,15, 16, 29.

020

Explanation: The error occurred duringexecution of a BDAM OPEN macro instruction.

The control program found:

1. The DCBMACRF field of the data controlblock (DCB) did not contain an A, K, or I.

2. An attempt was made to open a BDAMdata set that contained zero extents.


021 to 027


Programmer Response: In the first case, makesure that A, K, or I is specified in the MACRFoperand of the DCB macro instruction. Verifythat the DCBMACRF field was not incorrectlymodified by the problem program before theopening process. After making corrections,reassemble the program and execute the job stepagain.

In the second case, create the data set beforeattempting to open it as a BDAM file.

Problem Determination: Table I; items 1, 3, 5b,15, 29.

021

Explanation: A caller of the ASCBCHAProutine passed to ASCBCHAP an ASCBaddress that had bits set to one in its high orderbyte.

System Action: Module IEAVEACO discoveredthat the bits in the high order byte of the ASCBaddress are set to one. The system terminatesthe caller of the ASCBCHAP routine with the021 completion code.

Programmer Response: If you call theASCBCHAP routine, make sure that the ASCBaddress you pass has the high order byte set tozero.

Problem Determination: Table I, item 18.

022

Explanation: The VPSS encountered a missingdevice end condition on control port 0. TheVPSS cannot continue processing or respond tooperator commands.

System Action: The VPSS missing interruptionhandler exit abnormally terminates the VPSSmonitor address space. Message IGF991E

identifies the 3838 Array Processor that causedthe VPSS monitor address space to terminate.

Programmer Response: Determine why the 3838Array Processor is not responding with a deviceend. You may let the system operator restartthe VPSS so that the operator may enter VPSScommands for other 3838 devices.

Problem Determination: Table I, items 2, 16, 18,and 30.

024

Explanation: Abnormal termination occurred inPrint Services Facility (PSF). The PSF ESTAEroutines determine whether PSF can be restartedand the recovery termination manager requests aPSF restart. This system completion code and aPSF abend reason code are contained in eithermessage APS050I or APS521I. APS050I,APS521I, and the PSF abend reason codes aredocumented in Print Services Facility Messages.

Programmer Response: Respond as indicated formessages APS050I or APS521I.

Problem Determination: Table 1, items 2, 16,and 29.

027

Explanation: Abnormal termination occurred inPrint Services Facility (PSF). The PSF ESTAEroutines determine whether PSF can be restartedbut the recovery termination manager does notrequest a PSF restart. This system completioncode and a PSF abend reason code arecontained in either message APS050I orAPS521I. APS050I, APS521I, and the PSFabend reason codes are documented in PrintServices Facility Messages.

Programmer Response: Respond as indicated formessages APS050I or APS521I.

Problem Determination: Table 1, items 2, 16,and 29.


ABEND

028 to 02B

028

Explanation: A paging operation has notcompleted successfully because of one of thefollowing:

• A permanent I/O error occurred whileattempting a page-in or swap-in operation.The data being paged in or swapped in islost.

• An address space referred to a pageable linkpack area (PLPA) page that containsnoncontiguous code or large constant areas.Paging initialization processing issuedmessage IEA928I. For additionalinformation, refer to message IEA928I.

• A real storage management (RSM) routine,or another system routine performing aservice for RSM, suffered an indeterminateerror. The function is terminated.

• An auxiliary storage management routinesuffered a translation error while using thecontrol register of another address space toupdate that address space's LSQA.

• The RSM window service routine(IEAVWND) issues an 028 ABEND ifeither (1) the requested window is already inuse (such as when an exit routine invokesthe window service), or (2) both of the inputreal addresses are less than 16Mb.

• Module IEAVPSI detected an internal RSMerror. Register 15 contains reason code

X'14'.

System Action: The system terminates the taskor address space.

Programmer Response: If an 028 ABENDrecord exists in SYS1.LOGREC, determine themodule and CSECT in control at the time of theerror and continue problem determination at thecomponent level. Lack of an 028 ABENDrecord usually indicates a hardware problem or

an auxiliary storage manager (ASM) problem.A real storage management (RSM) 028 ABENDis usually caused by an unexpected error whileRSM is in control. Consult MVS DiagnosticTechniques for a diagnostic approach.


02A

Explanation: The error occurred duringexecution of a data management request for aspool data set. JES2 found that the datamanagement control blocks were no longer validor that the JES2 UBUF control block was nolonger valid.

Programmer Response: Verify that the problemprogram did not modify data managementcontrol blocks or the JES2 UBUF controlblock. After making the correction, execute thejob step again.

Problem Determination: Table I, items 1, 3, 5b,15, 16 29.

02B

Explanation: A user exit routine issued a returncode that is higher than the maximum returncode value specified in the &MAXRC parameterof the $EXITnnn macro instruction.

System Action: The system abnormallyterminates the user task and writes a dump.

Operator Response: Use the $TEXIT commandto disable EXITnnn.

Programmer Response: If the exit routine isissuing an incorrect return code, correct theroutine. If the routine is issuing the correctreturn code, change the maximum return codevalue specified on the $EXITnnn macroinstruction. Then rerun the job.

Problem Determination: Table I, items 13, 16.


02C

02C

Explanation: An error occurred in JES2 supportof a functional subsystem address space. Thissystem completion code is accompanied by oneof these messages:

$HASP413During a hot start, JES2 did notreestablish the cross-memory interfacerequired to support a functional subsystemaddress space. HASPWARM detected theerror.

System Action: HASPWARM usesCALLRTM macros to terminateabnormally the functional subsystem andthe functional subsystem application(FSA). The functional subsystem andFSA are in a separate address space. Alldevices associated with the functionalsubsystem are drained.

Operator Response: Notify the systemprogrammer. To restart the functionalsubsystem, issue the $S PRT command. Ifthe functional subsystem devices are alsosupported directly by JES2, restart themby issuing the $T command withMODE=JES and then starting the deviceswith the $S command.

Programmer Response: Determine why theATSET system service failed. ATSET wasinvoked with an authorization index valuein the $SVTAXV field of the subsystemvector table (SSVT). See SupervisorServices and Macro Instructions for adescription of ATSET.

$HASP415During a hot start, HASPWARM did notfind a JES2 device with the same devicename and device address as the devicepreviously supported by the activefunctional subsystem application (FSA).$HASP415 gives the name and address ofthe previously supported device.

System Action: HASPWARM uses aCALLRTM macro to terminateabnormally the FSA task, which is in thefunctional subsystem address space.

Operator Response: Notify the systemprogrammer.

Programmer Response: Probable cause isinvalid JES2 initialization parameters. Ifnecessary, change the parameters and stopand restart JES2.

$HASP750A catastrophic error occurred in the JES2module HASPFSSM, which consists of thefunctional subsystem interface (FSI)support routines; because of the error,JES2 issued a $ERROR macro. The$ERROR macro invoked the HASPFSSMcatastrophic error routine, FSMCATER,which issued message $HASP750.

In the message, the CODE=cde field isone of the following:

cde Explanation

$F00 A GETCELL services error occurred in theFSMGETQC routine of module HASPFSSM.Register 15 and the RC=rc filed in $HASP750contain a hexadecimal reason code:

rc Meaning

00000001 The number of cells requested via$GETQC in register 1 is less than orequal to 0 or greater thanQCTLIMIT.

xxxx0002 A SETLOCK RELEASE requestfailed. xxxx is the return code fromSETLOCK.

xxxx0003 The GETCELL service failed. xxxx isthe return code from GETCELL, asfollows:

0004 No available cells.0008 Chain pointers destroyed.000C Invalid cell pool format.0010 Invalid cell pool ID.

$F01 A FREECELL services error occurred in theFSMFREQC routine of module HASPFSSM.Register 15 and the RC=rc field of $HASP750contain a hexadecimal reason code:

rc Meaning

00000001 The number of cells requested via$FREQC in register 1 is less than orequal to 0 or greater thanQCTLIMIT.


02C

ABEND

xxxx0002 The FREECELL service failed. xxxxis the return code from FREECELL,as follows:

0004 The cell was not allocatedfrom the subpool indicatedby the specified cell pool ID.

0008 Cell address is invalid.000C No cell pool.0010 Invalid cell pool ID.

$F02 A GETCELL extension error occurred in theFSMBLDQC routine of module HASPFSSM.Register 15 and the RC=rc field of $HASP750contain a hexadecimal reason code:

rc Meaning

xxxx0005 The BLDCPOOL service failed. xxxxis the return code from BLDCPOOL,as follows:

0004 GETMAIN failed.0008 Invalid cell pool ID.000C

Nonglobal subpool.0010 Cell size greater than pool

size.0014 A DELETE subpool was in

progress for the pool.

xxxx0006 The GETMAIN request for theadditional cell pool failed. xxxx is thereturn code from GETMAIN.

$F03 A QUICKCELL initialization error occurred in theFSMQCT routine of module HASPFSSM. Register15 and the RC=rc field of $HASP750 contain ahexadecimal reason code:

rc Meaning

xxxx0001 A GETMAIN request failed. xxxx isthe return code from GETMAIN.

$F04 An error occurred in a SJF request on GETDS; theerror was detected in the FSMSWBRD routine ofmodule HASPFSSM. Register 15 and the RC=rcfield of $HASP750 contain a hexadecimal reasoncode:

rc Meaning

xxxx0001 An SJF EXTRACT request insubroutine FSWBEXT failed. xxxx isthe return code from the SJF request.

xxxx0002 An SJF UPDATE request failed.xxxx is the return code from the SJFrequest.

xxxx0004 An SJF TERMINATE request insubroutine FSMSJTER failed. xxxxis the return code from the SJFrequest.

$F05 An error occurred in a SJF request on RELDS; theerror was detected in the FSMSWBDL routine ofmodule HASPFSSM. Register 15 and the RC=rcfield of $HASP750 contain a hexadecimal reasoncode:

rc Meaning

xxxx0001 The SJF DELETE request failed.xxxx is the return code from the SJFrequest.

xxxx0004 An SJF TERMINATE request insubroutine FSMSJTER failed. xxxxis the return code from the SJFrequest.

System Action: The functional subsystemESTAE recovery routine may attemptrecovery or may terminate the functionalsubsystem address space. If the recovery issuccessful, JES2 processing continues fromthe point of recovery. If the address spaceis terminated, JES2 processing continuesbut the device operated by the failedfunctional subsystem and FSA is drained.

Operator Response: Notify the systemprogrammer. If the functional subsystemaddress space is terminated and the devicedrained, issue a $S command to try torestart the device.

If the device does not restart or fails againand if the device can be managed directlyby JES2, then issue a $Tdev,MODE=JEScommand, followed by $Sdev commands,to switch the device to JES mode.

If recovery is successful, no operatorresponse is needed.

Programmer Response: Analyze themessages and dumps. If the reason code15 indicates that insufficient storage wasavailable, provide more storage and restartthe device.

Problem Determination: Table 1, items 2, 7, 16.For $HASP750, items 18 and 33 also.


030 to 032

030

Explanation: The error occurred duringexecution of a BISAM or QISAM OPEN macroinstruction.

The control program found that theDCBMACRF field of the data control block(DCB) did not indicate a valid mode ofoperation for BISAM or QISAM. TheDCBMACRF field is set up by the MACRFoperand of the DCB macro instruction or by theproblem program before the data control blockis opened.

Programmer Response: Make sure that a validmode of operation is specified in the MACRFoperand of the DCB macro instruction. Verifythat the DCBMACRF field was not incorrectlyset up or modified by the problem program.After making corrections, reassemble theprogram and execute the job step again.


031

Explanation: An input/output error occurredduring processing using QISAM. The controlprogram attempted to pass control to an erroranalysis (SYNAD) routine, but found:

1. The DCBSYNAD field of the data controlblock (DCB) did not contain the address ofa valid SYNAD routine.

2. The error occurred after a CLOSE macroinstruction was executed by tasktermination. The problem programreturned control to the supervisor withoutexecuting a CLOSE macro instruction.

The task was abnormally terminated. TheDCBEXCD1 and DCBEXCD2 fields of thedata control block indicate the possible causesof the original error:

DCBEXCD1:

Bit Explanation

0 Record not found.1 Invalid actual address for lower limit.2 Space not found.

3 Invalid request.4 Uncorrectable input error.5 Uncorrectable output error.6 Block could not be reached (input).7 Block could not be reached (update).

DCBEXCD2:

Bit Explanation

0 Sequence check.1 Duplicate record.2 DCB closed when error detected.3 Overflow record.4 PUT: length of field greater than length indicated in

DCBLRECL field of the data control block.5-7 (Reserved bits).

Programmer Response: Examine theDCBEXCD1 and DCBEXCD2 fields of thedata control block to determine the cause of theerror. Specify the address of an error analysisroutine to be given control when aninput/output error is detected and, for errorsoccurring during CLOSE, execute a QISAMCLOSE macro instruction prior to returningcontrol to the supervisor. For errors occurringduring the execution of a QISAM CLOSEmacro instruction, respond as indicated bymessage IEC011I or IEC203I.

Problem Determination: Table I, items 1, 3, 5a,15, 29.

032


The control program found that theDCBMACRF field of the data control block(DCB) did not contain valid information forISAM.

Programmer Response: Make sure that validinformation is specified in the MACRF operandof the DCB macro instruction. Verify that theDCBMACRF field was not incorrectly modifiedby the problem program before the openingprocess.

After making corrections, reassemble theprogram and execute the job step again.



ABEND

033 to 035

033

Explanation: The error occurred duringexecution of an OPEN macro instruction for anindexed sequential data set:

• An input/output error occurred whilereading the highest level index.

• An input/output error occurred whilesearching for the end-of-file mark followingthe last data record in the prime andindependent overflow areas. TheDCBLPDA and DCBLIOV fields of thedata control block (DCB) contain,respectively, the addresses of the last recordsin the prime and independent overflowareas.

• The DCBMSHI field of the data controlblock contained an address that eitherspecified a location outside the boundariesof the virtual storage assigned to the task orhad a storage protection key other than thatspecified in the task control block (TCB).

• An input/output error occurred whilereading the last prime data block duringopen processing for resume load.

• All volumes of a multivolume ISAM dataset were not mounted.

Programmer Response: Verify that theDCBLPDA, DCBLIOV, and DCBMSHI fieldswere not incorrectly specified or modified by theproblem program. At the time of the abnormaltermination, register 4 contains the address ofthe DCB. After making corrections, reassemblethe program and execute the job step again.


034

Explanation: The error occurred duringexecution of a BISAM OPEN macroinstruction. For variable length records, thecontrol program found that the address inDCBMSWA was not valid. Either the addressis outside the boundaries of virtual storage orthe protection key of that address is not thesame as the protection key in the TCB.

The control program found that the fields of thedata control block (DCB) indicated a virtualstorage area too small to contain the highestlevel index for the data set. The size of thevirtual storage area that should be reserved forthe highest level index is placed in theDCBNCBHI field of the data control block at

OPEN exit time.

Programmer Response: The error can becorrected by one of the following:

• Specify a valid address in the MSWAoperand of the DCB. Verify that this fieldhas not been incorrectly modified.

• Provide a sufficient virtual storage area byproper specification of the DCBSMSI andDCBMSHI fields.

• Provide no virtual storage area and eitherdo not specify the contents of theDCBSMSI and DCBMSHI fields or set thefields to zero. The highest level index canthen be processed without being loaded intovirtual storage.



035

Explanation: The error occurred duringexecution of a BISAM OPEN macroinstruction.

The control program found that new recordswere to be added to the data set, but theDCBMSWA and DCBSMSW fields of the datacontrol block (DCB) indicated a virtual storagearea too small to contain one track from theprime area.

Programmer Response: The error can becorrected by one of the following:

• Provide a sufficient area by properspecification of the DCBMSWA andDCBSMSW fields. The minimum


036 to 038

DCBSMSW field must indicate one trackcapacity plus one record.

• For fixed-length records, provide no virtualstorage area and either do not specify thecontents of the DCBMSWA andDCBSMSW fields or set the fields to zero.A virtual storage work area is required onlyfor variable-length records.



036


The control program found that no space wasallocated on a direct access device as the primearea for the data set:

1. In QISAM load mode, during data setgeneration, the SPACE parameter of theDD statement did not specify a primaryquantity.

2. The data set control block (DSCB) for thedata set was incorrectly modified by theproblem program.

Programmer Response: In the first case, the dataset should be dumped sequentially and recreatedusing QISAM load mode. The job should berestarted with a primary quantity specified inthe SPACE parameter of the DD statement. Ifthe prime area is to span more than one volume,the number of volumes and the number of unitsrequired should be specified.

In the second case, verify that the data setcontrol block was not incorrectly modified bythe problem program. After makingcorrections, reassemble the program and executethe job step again.


037

Explanation: The error occurred duringexecution of a BISAM or QISAM OPEN macroinstruction. The control program found that thebuffers supplied by the programmer wereinadequate for the records to be processed:

• If the buffers were acquired by use of theBUILD macro instruction, either theBUFNO operand of the DCB macroinstruction was not specified or the BUFLoperand specified too small a value.

• If the buffers were acquired by use of theGETPOOL macro instruction, the bufferlength operand specified too small a value.

Programmer Response: Specify the bufferscorrectly. Then execute the job step again.


038

Explanation: The error occurred duringexecution of an OPEN macro instruction forQISAM load mode.

The control program found that the space on adirect access device that had been allocated forthe index area was either exhausted or occupiedmore than one volume. The index for an ISAMdata set must reside on one volume.

Programmer Response: If a new data set is beingcreated, the job must be restarted with morespace allocated through the SPACE parameterof the DD statement.

If an old data set is being updated, the data setshould be dumped sequentially, the old data setscratched, and the data set recreated from thesequential data set using QISAM load mode.The job should be restarted with more spaceallocated through the SPACE parameter of theDD statement.



ABEND

039 to 03B

039

Explanation: The error occurred in scanning adata set using QISAM.

The end of the data set (EOD) was reached.The control program found that theDCBEODAD field of the data control block(DCB) did not contain an end-of-data-set exitroutine address.

Programmer Response: Make sure that theaddress of a routine to be given control whenthe end of the data set is reached is specifiedeither in the EODAD operand of the DCBmacro instruction or in the problem programbefore the end of the data set is reached. Thenreassemble the program, and execute the jobstep again.


03A

Explanation: The error occurred duringexecution of a BISAM or QISAM CLOSEmacro instruction.

A format-2 data set control block (DSCB), readfrom a direct access device into virtual storage,was updated from the data control block(DCB). When an attempt was made to writethe updated data set control block back to thedirect access device, an input/output erroroccurred.

When the ISAM interface is used to process aVSAM data set, this system completion codecan be accompanied by message IEC251I. If itis, refer to message IEC251I for informationabout the task that terminated.

Programmer Response: If this system completioncode is accompanied by message IEC251I,respond as indicated by message IEC251I.

At abnormal termination, register 4 points tothe OPEN/CLOSE/END-OF-VOLUME workarea. X'64' in the work area contains theaddress of the job file control block (JFCB); thecontents of the JFCB begin with the44-character name of the data set involved inthe input/output error. The address of the unit

control block (UCB), which contains the deviceaddress for the data set, is located at X'230' inthe work area. The address of the user's DCB,which contains the address of the data eventblock (DEB), is located at X'238' in the workarea.

Correct the problem with the data set, and rerunthe job.

Problem Determination: Table I, items 1, 3, 5a,15, 25b, 29.

03B

Explanation: The error occurred duringexecution of an OPEN macro instruction for anindexed sequential data set. No records couldbe processed because:

1. The format-2 data set control block (DSCB)indicated that the data set had not beencreated.

2. The format-2 DSCB indicated that the datacontrol block (DCB) had not been closedafter the data set had been created.

3. The DCBRKP field of the data controlblock was not valid.

4. The DCBKEYLE field of the data controlblock contained either zero or a value notequal to the value in the DS1KEYL field ofthe format-1 DSCB.

5. A QISAM data control block was beingopened in preparation for a PUT operation,but the OPEN macro instruction had notbeen issued for output.

6. There is an error in specification of LRECLor BLKSIZE. Either:

a. The block size (DCBBLKSI) is less thanthe logical record length (DCBLRECL).

b. The logical record length (DCBLRECL)is zero.

c. The block size (DCBBLKSI) is not amultiple of the logical record length(DCBLRECL).


03D

d. The blocksize (DCBBLKSI) and/or thelogical record length (DCBLRECL)differs from the DSCB blocksize and/orlogical record length.

7. A QISAM data control block was beingopened in preparation for a PUT operationand DISP=SHR was coded in the JCL.

8. RECFM was specified incorrectly. Thevalue for the record format (DCBRECFM)is not the same as the value for the recordformat specified when the data set wascreated.

Register 2 contains the address of the DCB forwhich the abend was issued.

When the ISAM interface is used to process aVSAM data set, this system completion codecan be accompanied by message IEC161I. If itis, refer to message IEC161I for informationabout the task that terminated. The ISAMinterface of VSAM issues abend code 03B forone of the following reasons:

• The access method service's and DCBvalues for LRECL, KEYLE, RKP do notmatch.

• DISP=OLD was specified and the DCBwas opened for output and the number oflogical records is greater than zero(RELOAD is implied).

• An OPEN ACB error code 116 wasreturned for a request to open a VSAMstructure.

Programmer Response: In cases 1 and 2, makesure that the data set has been properly createdand that the creating task closes the data controlblock.

In case 3, make sure that the value of theDCBRKP field of the data control block, whenadded to the value in the DCBKEYLE field,does not exceed the value in the DCBLRECLfield. If variable length records are used, makesure that the value of the DCBRKP field is notless than 4.

In case 4, make sure that the DCBKEYLE fieldin the data control block does not contain zero.

For an existing ISAM data set, omit theKEYLEN operand on the DCB macroinstruction, allowing the data set control blockto supply the key length value.

In case 5, make sure that OUTPUT is specifiedas option 1 in the OPEN macro instruction.

In case 6, make sure that the block size(BLKSIZE) and logical record length (LRECL)have been specified correctly and that they arecompatible.

In case 7, code DISP=OLD in the JCL for aQISAM data control block being opened for aPUT operation.

In case 8, list the VTOC to determine thecorrect record format of the data set.

In cases when the ISAM interface issued anABEND, make sure that a valid mode ofoperation is specified in the MACRF operandof the DCB macro. Additionally, make sure thatthe DCB is not being opened for load modewhile there are records in the data set.

In all cases, execute the job step again.

If this system completion code is accompaniedby message IEC161I, respond as indicated forthe message.


03D

Explanation: The error occurred duringexecution of an OPEN macro instruction.

For a QISAM or BISAM OPEN macroinstruction, one of the following occurred:

• The DD statement did not specify anindexed sequential organization, which canbe specified by the DSORG=IS orDSORG=ISU subparameter of the DCBparameter.

• If the data set resides on multiple volumes,either the volume serial numbers in the SERsubparameter of the VOLUME parameterof the DD statement were not in proper


ABEND

03E to 041

sequence, or not all volume serial numberswere specified. The serial number of thevolume containing the index must be listedfirst. The number of volumes and thenumber of units allocated must be the same,and all volumes must be mounted.

For a BDAM OPEN macro instruction, one ofthe following occurred:

• The volume serial numbers in the SERsubparameter of the VOLUME parameterof the DD statement were not in propersequence.

• The DCB DSORG=DA, but the DDstatement specified an indexed sequentialdata set name.

This system completion code is sometimesaccompanied by message IEC156I. If so, referto message IEC156I for information about thetask that was terminated and for an explanationof the return code (rc in the message text) inregister 15.

Programmer Response: Correct the DCBparameter or SER subparameter, as necessary,and execute the job step again.

If this system completion code is accompaniedby message IEC156I, respond as indicated forthe message.


03E

Explanation: The error occurred duringexecution of a QISAM OPEN macroinstruction. The position of the last prime datarecord indicated that there is no room to addrecords with resume load.

The loading of an indexed sequential data setmust be completed during the initialOPEN/PUT/CLOSE cycle for that data set. Anindexed sequential data set that has been openedand closed for loading may be subsequentlyloaded if no data was created.

Possibly, an attempt was made to add recordswith resume load to the prime area of an ISAMdata set that had no space available foradditional records.

Programmer Response: Either load the data setagain with a larger space allocation, or addrecords using BISAM.

After making corrections, execute the job stepagain.


040

Explanation: The error occurred duringexecution of an OPEN macro instruction for aTCAM line group data set.

System Action: An error code is inserted intoregister 0 if the user specified an address in theEXLST=operand of the line group DCBmacro instruction. The user exit routine mayexamine the code in register 0. If no user exitwas specified, the error type is indicated byconsole message IED008I.

Programmer Response: Respond as indicated formessage IED008I.

041

Explanation: The error occurred duringexecution of an OPEN macro instruction for aTCAM message queue data set.

System Action: An error code is inserted intoregister 0 if the user specified an address in theEXLST=operand of the message queue DCBmacro instruction. The user exit routine mayexamine the code in register 0. If no user exitwas specified, the error type is indicated byconsole message IED008I.

Programmer Response: Respond as indicated formessage IED008I. If your system has theACF/TCAM program product installed refer tothe appropriate ACF/TCAM messages book.Otherwise, refer to System Messages.


042 to 043

042

Explanation: An IPL command was issued for a3705 for which one or more terminal entriesindicate that the teleprocessing on-line testexecutive (TOTE) has control of the terminal asa control terminal, alternate printer, or testdevice.

System Action: All active on-line tests (OLTs)are forced to terminate. This forced cleanup isindicated on the system console by messageIED284I OLT xx ABEND 042000, where xx isthe OLT identification number.

Operator Response: Reenter the test requestmessage after the initial program load (IPL) iscomplete.

043

Explanation: The error occurred duringexecution of an OPEN macro instruction for aTCAM application program data set.



01 An OPEN macro for a TCAM applicationprogram data set has been issued, but the MessageControl Program (MCP) is not active in thesystem.

02 One of the following was found:

• The QNAME=parameter of a DDstatement associated with an applicationprogram is not the name of a process entrydefined in the terminal table.

• The QUEUES=operand appeared in aTPROCESS macro instruction when anapplication program DCB was being openedfor output only.

• The QUEUES=operand was not specifiedwhen an application program DCB was beingopened for input.

03 A process entry named by the QNAME=parameter of a DD statement associated with an

application program is currently being used byanother application program.

04 One of the following occurred:

• Not enough virtual storage was available inthe MCP to build internal control blocks.

• The PGFN macro failed for the process entrywork area.

05 Not enough virtual storage was available in theapplication program area to build internal controlblocks.

06 The application program attempted to open asecured queue. The system operator rejected therequest.

07 The application program is not an authorizedprogram, but the user has either codedAUTHA=YES or taken YES as the default valuefor the AUTHA parameter on the TCAM INTROmacro instruction.

08 PCB error. OPEN was issued for a TPROCESSentry while its PCB was in use by another task.

System Action: If a user ABEND exit isprovided in the EXLST=operand of the DCBmacro for the data set, the system gives controlto the routine. If it returns or if no userABEND exit is provided, the system terminatesthe task. Message IED015I may accompany thissystem completion code.

Programmer Response: No action is required ifa user ABEND exit has been provided in theEXLST=operand of the DCB macro for theapplication program data set. Responsedepends on the reason code in register 0:

ReasonCode Response

01 Make sure that an MCP is active beforeattempting to start an application program.

02 or 03 Recode the QNAME=parameter, specifying thename of a valid process entry.

04 Specify a larger region or partition size on the JOBstatement for the MCP, or re-IPL the systemspecifying a larger system queue space.

05 Specify a larger partition size on the JOBstatement for the application program.

06 Recode the SECURE=YES operand associatedwith the queue, or instruct the system operator toallow the queue to be opened.

07 Link edit the application program as anauthorized program into an authorized library, orspecify AUTHA=NO on the TCAM INTROmacro instruction.

08 Open all TPROCESS entries for the PCB in thesame application program.


ABEND

044 to 045

044

Explanation: The error occurred duringexecution of the FE Common Write(COMWRITE) task. The COMWRITE taskwas terminated.



01 Permanent I/O error on output device. Register 7contains user ID; register 8 contains address offailing DECB.

02 STAE routine failed. Register 15 contains thereturn code.

03 User parameter list is incorrect, and outputrequired was specified. Register 7 contains theaddress of the parameter list saved inCOMWRITE. Register 11 contains the address ofthe error message.

05 The output DCB failed to open.

06 For one of the traces specified, the size of one halfof the trace table is larger than the maximumblock size specified for the trace data set.

Programmer Response: Response depends on thereason code in register 3:

ReasonCode Response

01 Check the status of the recording medium. If it isvalid, call IBM for hardware support.

02 Call IBM for hardware support.

03 Check the parameter list.

05 Missing DD statement. Include the DDstatement, and rerun the job.

06 Ensure that the size of one half of the trace tabledoes not exceed the maximum block size specifiedfor the trace data set.

045

Explanation: The error occurred duringexecution of a TCAM Message ControlProgram (MCP). The MCP terminates.

The low-order byte of register 15 contains ahexadecimal reason code:


01 1,0 has been requested on a nonreusable diskrecord that is beyond the capacity of the data set.The nonreusable disk data set cannot be wrapped

02 Logical read error caused by the reusable diskreceiving a heavy burst of new traffic. This trafficcauses unsent messages to be overlaid before beingcopied to the alternate destination queue.

03 Logical read error while trying to fetch a messagefor transmission to a terminal.

04 The copy subtask needed to copy messa ges fromone data set to another has not been loaded by thedisk OPEN. A multiple-route or distribution listmessage has been enqueued to go to dissimilarmessage queue types. The copy subtask is neededto put the message on the queue. Caused byfailure to open successfully a disk message queueDCB.

05 I/O has been requested on an unopened diskmessage queue data set.

06 FEATURE=(„NOTIMER) was specified in theINTRO macro instruction, but a functionrequiring the system timer has been called.

07 A message longer than the reusable disk data sethas been entered.

08 A disk read error occurred. It was a hardwareerror, not a logical read error.

09 Either not enough space was allocated for thecheckpoint data set, or an I/O error occurred onthe checkpoint data set.

OA The checkpoint data set is too small.Alternatively, the number of checkpoint recordsspecified in the INTRO macro instruction is toolarge.

Programmer Response: Response depends on thereason code in the low-order byte of register 15:

ReasonCode Response

01 Either specify a larger data set or request thatclose down occur at an earlier point.

02,03,07 Specify a larger data set or one that occupiesmore than one extent. For further suggestedcorrections, refer to OS/VS2 TCAM SystemProgrammer's Guide.

04,05 Before issuing the OPEN macro instructions forthe lines, test for successful open of the messagequeue data set.

06 Specify FEATURE=(„TIMER); reassemble andrerun the MCP.


046 to 04C

09 Message issued to operator just before ABENDdescribes the cause of failure, and messagedescription provides response.

OA Allocate more space for the checkpoint data set,or specify fewer checkpoint records in theINTRO macro instruction.

Problem Determination: For return code 08, seeTable I, items 1, 2, 4, 5a, 18, 30. For all otherreturn codes, see Table I, items 5a, 10, 29.Obtain a listing of the message queue data set.

046

Explanation: The TCAM MCP was terminated,but an application program data set is still open.The system terminates the application programdata set and issues system completion code 046.

System Action: The application program isterminated.

Programmer Response: Respond as indicated forthe system completion code issued upontermination of the MCP.

047

Explanation: An unauthorized programrequested a restricted SVC.

The PSW indicates the last SVC issued. If SVC102 (66) was the last issued by an unauthorizedTCAM application program, the TCAM MCPprogram must specify in the INTRO macroinstruction, AUTHA=NO. If SVC 102 wasissued by other than a TCAM applicationprogram, the program must be authorized.

If SVC 104 (68) was last issued, the programmust be an authorized TCAM MCP.

Operator Response: Notify the installationmanager or system programmer immediately.Hold all output relevant to the job.

Programmer Response: Run the job again.

048

Explanation: A subsystem address spacesupported by ACF/TCAM had an error

condition. An ACF/TCAM subsystem hasdetermined that recovery could not occur. Thesubsystem terminates. Register 0 contains ahexadecimal reason code:


001 The RPL address was invalid when the subsysteminterface was not running with authorized path.

002 Abnormal termination occurred before thesubsystem was notified of FRR recovery.

System Action: Restart the subsystem.

Programmer Response: Print the SVC dump,which was stored in the SYS I .DUMP data set.For further detail, refer to ACF/TCAM Supportfor IBM Subsystems.

Problem Determination: Table I, items 10, 13,18, 32, 33, 49.

049

Explanation: A subsystem address spacesupported by ACF/TCAM had an errorcondition. The FRR was unable to recover thesubsystem. A SYS I .LOGREC entry wascreated to explain why recovery could not occur.An SVC dump was written to SYS I .DUMP.

System Action: Restart the subsystem.

Programmer Response: Print the dump andLOGREC entry. Refer to ACF/TCAM Supportfor IBM Subsystems.

Problem Determination: Table I, items 10, 13,18, 32, 33, 49.

04C

Explanation: The system issues completion code04C when both of the following occur:

• A user invokes the TMP (terminal monitorprogram) at entry point IKJEFT I A.

• The TMP detaches a program thatcompleted with a nonzero completion code.The nonzero completion code is in register15.


ABEND

04D to 052

System Action: The system does not change theuser completion code.

Operator Response: None.

Programmer Response: None.

Problem Determination: None.

04D

Explanation: A module that branch enteredIEAVGM00 violated the interface withGETMAIN or FREEMAIN. Register 14contains the address of the calling module.Register 15 contains a hexadecimal reason code:


04 The ASCB address in register 7 was not theaddress of the current ASCB.

08 A module branch entered IEAVGM00 without thelocal lock. Register 7 contains the PSAHLHIindicator.

0C A module branch entered IEAVGM00 at theglobal entry point without the SALLOC lock.Register 7 contains the PSAHLHI indicator.

Programmer Response: The module calling theGETMAIN or FREEMAIN macro(BRANCH=YES) is probably in error. Checkthe calling module to be sure it made therequest correctly.

Problem Determination: Table I, items 3, 4, 11,13, 16, 29, 33.

052

Explanation: A program requested a programcall/authorization (PC/AUTH) service or aprogram call linkage service, but the caller'srequest was invalid. Register 15 contains ahexadecimal return code in the form xxyy,where xx identifies the service that was calledand yy identifies the error.

System Action: The program that called theservice abnormally terminates.

Programmer Response: Find and correct theerror. Rerun the program.


01yy The program issued the LXRES macro instructionto call the linkage index reserve service(IEAVXLRE). Register 15 contains one of thesereason codes:

0101 A reserved field in the parameter list is notzero. Register 5 contains the first word ofthe parameter list.

0102 The format number field in the parameterlist is invalid. Register 5 contains the firstword of the parameter list.

0103 The request count in the linkage index listis invalid. Register 5 contains the first wordof the parameter list.

0104 A jobstep attempted to establish PCservices, but a prior jobstep ownedspace-switch entry tables. (Subsequentjobsteps are not permitted to establish PCservices.)

02yy The program issued the LXFRE macro instructionto call the linkage index free service (IEAVXLFR).Register 15 contains one of these reason codes:

0201 A reserved field in the parameter list is notzero Register 5 contains the first word ofthe parameter list.

0202 The format number field in the parameterlist is invalid. Register 5 contains the firstword of the parameter list.

0203 The request count in the linkage index listis invalid. Register 5 contains the first wordof the parameter list.

0211 A linkage index (LX) is invalid. Register 5contains the invalid linkage index.

0212 A linkage index is not owned by the homeaddress space. Register 5 contains theinvalid linkage index.

0213 A linkage index is invalid because it is asystem linkage index. Register 5 containsthe linkage index.

0214 A linkage index has one or more entrytables connected and FORCE=YES wasnot specified.

0215 A linkage index appeared more than oncein the linkage index list.

03yy The program issued the ETCRE macro instructionto call the entry table create service (IEAVXECR).Register 15 contains one of these reason codes:

0301 A reserved field is not equal to zero in theheader of the entry table description (ETD)specified in the ENTRIES parameter.


052

0302 The format number field in the entry tabledescription (ETD) is invalid.

0303 The request count in the EDTNUM field isinvalid.

0304 The caller passed a nonzero value inregister 1. (Register 1 is reserved for futureuse.)

0311 A reserved field is not equal to zero in oneof the 20-byte description elements in theentry table description (ETD). Register 2contains the entry index (EX) associatedwith the description element.

0312 The program identified in one of the20-byte description elements could not befound. Register 2 contains the entry index(EX) associated with the descriptionelement.

0313 The entry indexes are not in ascendingorder. Register 2 contains the entry index(EX) that was not in ascending order.


04yy The program issued the EXDES macro instructionto call the entry table destroy service (IEAVXEDE).Register 15 contains one of these reason codes:

0401 A reserved input field in the parameter listis not zero.

0402 The format number field in the parameterlist is invalid.

0411 The specified token is invalid.

0412 The program specified a token for a systementry table but did not specifyPURGE=YES.

0413 The specified token is for an entry tablethat the home address space does not own.

0414 The program specified a token for an entrytable that is in use, but the program did notspecify PURGE=YES.

05yy The program issued the ETCON macro instructionto call the entry table connect service (IEAVXECO).Register 15 contains one of these reason codes:

0501 A reserved input field is not zero.

0502 The format number field is invalid.

0503 The token list count or the linkage indexlist count is invalid.

0511 The token list count and the linkage indexlist count are not equal.

0512 A specified linkage index is already in use.Register 2 contains the invalid linkageindex.

0513 A specified linkage index is not reserved.Register 2 contains the invalid linkageindex.

0514 A specified token is invalid.

0515 A specified token is for an entry table thatis already connected to the home addressspace's linkage table. Register 2 containsthe invalid token.

0516 A specified token is for an entry table thatis not authorized for connection. Register 2contains the invalid token.

0517 An entry table and the correspondinglinkage index are not owned by the sameaddress space. Register 2 contains thelinkage index.

0519 A token appeared more than once in thetoken list. Register 2 contains the token.

051A A linkage index appeared more than oncein the linkage index list.

06yy The program issued the ETDIS macro instruction tocall the entry table disconnect service (IEAVXEDI).Register 15 contains one of these reason codes:

0603 The token count is invalid. Register 2contains the invalid count.

0604 The caller passed a nonzero value inregister 1. Register 2 contains the value.

0611 A specified token is invalid. Register 2contains the token.

0612 The specified token is for a system entrytable. Register 2 contains the token.

0613 The specified token is for an entry tablethat is not connected. Register 2 containsthe token.

0614 A token appears more than once in thetoken list. Register 2 contains the token.

0615 The linkage index free service called theentry table disconnect service and passed aninvalid ASID. Register 2 contains theinvalid ASID.


052

ABEND

07yy A program issued the AXRES macro instruction tocall the authorization index reserve service(IEAVXRFE). Register 15 contains one of thesereason codes:

0703 The request count is invalid. Register 4contains the request count.

0704 The caller passed a nonzero value inregister 1.


08yy A program issued the AXFRE macro instruction tocall the authorization index free service(IEAVXRFE). Register 15 contains one of thesereason codes:

0803 The request count is invalid. Register 4contains the request count.


0813 An authorization index (AX) is notreserved by the home address space.Register 4 contains the AX.

0814 An authorization index (AX) is still in use.Register 4 contains the address of theASCB using the AX. Register 5 containsthe AX.

0817 An authorization index (AX) appearedmore than once in the authorization indexlist. Register 4 contains the duplicate AX.

0823 An authorization index (AX) equal to 0 or1 appears in the authorization index list. AnAX of 0 or 1 cannot be freed. Register 4contains the AX.

09yy A program issued the AXEXT macro instruction tocall the authorization index extract service(IEAVXRFE). Register 15 contains one of thesereason codes:

0901 A reserved input field is not zero.


0918 The ASID passed as input is not the ID ofan active address space. Register 4 containsthe ASID.

0Ayy The program issued the AXSET macro instructionto call the authorization index set service(IEAVXSET). Register 15 contains one of thesereason codes:

0A01 A reserved input field is not zero.

0A04 The caller passed a nonzero value inregister 1.

0A19 The authorization index is not within theauthorization index allocation table(AXAT). Register 4 contains theauthorization index.

0A20 The authorization index is not reserved.Register 4 contains the authorization index.

0A21 The home address space has one or moreconnected space switch entry tables thatcould cause an address space switch.

0Byy The program issued the ATSET macro instructionto call the authorization table set service(IEAVXSET). Register 15 contains one of thesereason codes:

OB01 A reserved input field is not zero.

0B04 The caller passed a nonzero value inregister 1.

0B19 The authorization index (AX) specified isnot within the authorization indexallocation table (AXAT). The secondhalfword of register 4 contains the AXvalue. The content of the first halfword ofregister 4 is undefined and unpredictable.

0B20 The authorization index specified is notreserved. Register 4 contains the AX.

0B22 The specified authorization index (AX) isfor a predefined authorization table entry.Register 4 contains the AX.

11yy The program issued the PCLINK macro instructionwith the STACK parameter (IEAVXSTK). Register15 contains one of these reason codes:

1112 The program held one or more locks thatprevented PCLINK processing from gettingthe SALLOC lock. Register 2 contains amask showing the locks that the programheld.

12yy The program issued the PCLINK macro instructionwith the UNSTACK parameter (IEAVXSTK).Register 15 contains one of these reason codes:

1211 The macro instruction included theUNSTACK,THRU or the UNSTACK,TOparameter, but the current PCLINK stackelement chain was empty.

1212 The specified token was for a PCLINKstack element (STKE) that is not on thePCLINK stack element chain. Register 2contains the token.


053

13yy The program issued the PCLINK macro instructionwith the EXTRACT parameter (IEAVXSTK).Register 15 contains one of these reason codes:

1313 The specified token was for a PCLINKstack element (STKE) that is not thecurrent element (the most recently stackedelement).

Register 2 contains the token of the currentelement. (Either a user error or a systemerror can cause this condition.)

1314 The specified token is not valid. Register 2contains the invalid token.

053

Explanation: A program issued a macroinstruction to call a program call authorization(PC/AUTH) service or a program call linkageservice, but an error prevented the service fromcompleting normally. Register 15 contains ahexadecimal reason code in the form xxyy,where xx identifies the service that was calledand yy identifies the error. The registers arerecorded in SDWAGRSV.

System Action: The PC/AUTH functionalrecovery routine writes an SDUMP and an errorrecord to SYS1.LOGREC. The program thatcalled the service abnormally terminates, unlessthe service requests a retry.

Programmer Response: Find and correct theerror.



0lyy The program issued the LXRES macro instructionto call the linkage index reserve service(IEAVXLRE). Register 15 contains one of thesereason codes:

0101 The service issued a GETMAIN for adynamic work area, but the GETMAINfailed. Register 5 contains the GETMAINreturn code.

0105 The service issued a GETMAIN for a newlinkage index allocation table (LXAT) inthe pageable storage of the programcall/authorization (PC/AUTH) addressspace. The GETMAIN failed; register 5contains the GETMAIN return code.

0109 The service issued a FREEMAIN for anold linkage index allocation table (LXAT)in the program call/authorization(PC/AUTH) address space's pageablestorage. The FREEMAIN failed; register 5contains the FREEMAIN return code.

010A The service issued a FREEMAIN for adynamic work area, but the FREEMAINfailed. Register 5 contains the FREEMAINreturn code.

0111 The service could not reserve one or morelinkage indexes (LXs) because themaximum number of LXs the systemsupports would be exceeded. Register 5contains the number of LXs that arecurrently unreserved.

0197 An unexpected error occurred.

0198 The program call/authorization(PC/AUTH) services are inoperable.

0199 The acronym at the beginning of a programcall/authorization (PC/AUTH) controlblock is invalid. Register 5 contains theexpected acronym.

02yy The program issued the LXFRE macro instructionto call the linkage index free service (IEAVXLFR).Register 15 contains one of these reason codes:


0205 The service issued a GETMAIN for a newforce disconnect queue block (FDQB) inthe program call/authorization (PC/AUTH)address space's pageable storage. TheGETMAIN failed; register 5 contains theGETMAIN return code.

0209 The service issued a FREEMAIN for aforce disconnect queue block (FDQB) inthe program call/authorization (PC/AUTH)address space's pageable storage. TheFREEMAIN failed; register 5 contains theFREEMAIN return code.


0211 The service was building the forcedisconnect queue (FDQ) to process aFORCE request. The service found morethan one connection description (ETIXCD)with the same ASID/LX (address spaceID/linkage index) values while searching theETIB (entry table information block) chain.



053

ABEND



03yy The program issued the ETCRE macro instructionto call the entry table create service (IEAVXECR).Register 15 contains one of these reason codes:


0302 The service issued a GETMAIN for storagein the SQA, but the GETMAIN failed;register 2 contains the GETMAIN returncode.

0303 The service issued a GETMAIN for storagein the program call/authorization(PC/AUTH) address space's LSQA. TheGETMAIN failed; register 2 contains theGETMAIN return code.

0305 The service issued a GETMAIN for storagein the program call/authorization(PC/AUTH) address space's pageablestorage. The GETMAIN failed; register 2contains the GETMAIN return code.

0306 The service issued a FREEMAIN forstorage in the SQA, but the FREEMAINfailed; register 2 contains the FREEMAINreturn code.

0307 The service issued a FREEMAIN forstorage in the program call/authorization(PC/AUTH) address space's LSQA. TheFREEMAIN failed; register 2 contains theFREEMAIN return code.

0309 The service issued a FREEMAIN forstorage in the program call/authorization(PC/AUTH) address space's pageablestorage. The FREEMAIN failed; register 2contains the FREEMAIN return code.





04yy The program issued the ETDES macro instructionto call the entry table destroy service (IEAVXEDE).Register 15 contains one of these reason codes:


0406 The service issued a FREEMAIN forstorage in the SQA, but the FREEMAINfailed; register 2 contains the FREEMAINreturn code.







05yy The program issued the ETCON macro instructionto call the entry table connect service (IEAVXECO).Register 15 contains one of these reason codes:


0503 The service issued a GETMAIN for storagein the program call/authorization(PC/AUTH) address space's LSQA. TheGETMAIN failed; register 2 contains theGETMAIN return code.




053





06yy The program issued the ETDIS macro instruction tocall the entry table disconnect service (IEAVXEDI).Register 15 contains one of these reason codes:







07yy The program issued the AXRES macro instructionto call the authorization index reserve service(IEAVXRFE). Register 15 contains one of thesereason codes:





0712 The service cannot satisfy the requestbecause the authorization index (AX) countwould cause the total number of AXs toexceed the maximum number that thesystem supports. Register 4 contains theAX count for the request.




08yy The program issued the AXFRE macro instructionto call the authorization index free service(IEAVXRFE). Register 15 contains one of thesereason codes:






09yy The program issued the AXEXT macro instructionto call the authorization index extract service(IEAVXRFE). Register 15 contains one of thesereason codes:






053

A BEND


0Ayy The program issued the AXFRE macro instructionto call the authorization index free service(IEAVXRFE). Register 15 contains one of thesereason codes:

0A01 The service issued a GETMAIN for adynamic work area, but the GETMAINfailed. Register 4 contains the GETMAINreturn code.

0A0A The service issued a FREEMAIN for adynamic work area, but the FREEMAINfailed. Register 4 contains theFREEMAIN return code.

0A30 An unexpected error occurred before theservice set the authorization index (AX) ofthe home address space.

0A31 An unexpected error occurred after theservice set the authorization index (AX) ofthe home address space, but before the bindbreak routine could break all binds to otheraddress spaces.

0A32 An unexpected error occurred after theservice set the authorization index (AX) ofthe home address space and the bind breakroutine broke all binds to other addressspaces.

0A97 An unexpected error occurred.

0A98 The program call/authorization(PC/AUTH) services are inoperable.

0A99 The acronym at the beginning of programcall/authorization (PC/AUTH) controlblock is invalid. Register 4 contains theexpected acronym.

0Byy The program issued the ATSET macro instructionto call the authorization table set service(IEAVXSET). Register 15 contains one of thesereason codes:

0B01 The service issued a GETMAIN for adynamic work area, but the GETMAINfailed. Register 4 contains the GETMAINreturn code.

0B03 The service issued a GETMAIN for storagein the program call/authorization(PC/AUTH) address space's LSQA. TheGETMAIN failed; register 4 contains theGETMAIN return code.

0B07 The service issued a FREEMAIN forstorage in the program call/authorization(PC/AUTH) address space's LSQA. TheFREEMAIN failed; register 4 contains theFREEMAIN return code.

0B0A The service issued a FREEMAIN for adynamic work area, but the FREEMAINfailed. Register 4 contains theFREEMAIN return code.

0B30 An unexpected error occurred before theservice set the authorization bits in theauthorization table (AT) of the homeaddress space.

0B31 An unexpected error occurred after theservice set the authorization bits in theauthorization table (AT) of the homeaddress space, but before the bind breakroutine broke all binds to other addressspaces.

0B32 An unexpected error occurred after theservice set the authorization bits in theauthorization table (AT) of the homeaddress space and the bind break routinebroke all binds to other address spaces.

0B97 An unexpected error occurred.

0B98 The program call/authorization(PC/AUTH) services are inoperable.

0B99 The acronym at the beginning of a programcall/authorization (PC/AUTH) controlblock is invalid. Register 4 contains theexpected acronym.

0Cyy The program call/authorization (PC/AUTH)resource manager, IEAVXPAM, detected an error.Register 15 contains one of these reason codes:

0C01 The resource manager issued a GETMAINfor a dynamic work area, but theGETMAIN failed. Register 2 contains theGETMAIN return code.

0C06 The resource manager issued aFREEMAIN for storage in the SQA, butthe FREEMAIN failed; register 2 containsthe FREEMAIN return code.

0C07 The resource manager issued aFREEMAIN for storage in the PC/AUTHaddress space's LSQA. The FREEMAINfailed; register 2 contains the FREEMAINreturn code.

0C09 The resource manager issued aFREEMAIN for storage in the PC/AUTHaddress space's pageable storage. TheFREEMAIN failed; register 2 contains theFREEMAIN return code.

0C0A The resource manager issued aFREEMAIN for a dynamic work area, butthe FREEMAIN failed. Register 2contains the FREEMAIN return code.

0C97 An unexpected error occurred.


054

0C99 The acronym at the beginning of aPC/AUTH control block is invalid.Register 2 contains the expected acronym.

0CC1 The AkBAXR count for the terminatingaddress space was too low.

0CC2 The ASCBLXR count for the terminatingaddress space was too low.

0CC3 The bind break routine issued a nonzeroreturn code.

0Dyy IEAVXPCR, the program call authorizationfunctional recovery routine (PC/AUTH FRR),detected an error. For any yy value except 88 and89, the PC/AUTH FRR detected an invalidservice-in-control code and cannot determine whichPC/AUTH service is running; the dump titlecontains PCRAEERC=nnnn, where nnnn is thevalue in the PCRAEERC field of the PCRA(program call recovery area) at the time the FRRgot control. If register 15 contains 0D88 or 0D89,the explanation is:

0D88 The FRR received return code X'18'fromIEAVEQV1, the single-threaded queueverification routine.

0D89 The FRR received return code X'18' fromIEAVEQV3, the double-threaded queueverification routine.

11yy The program issued the PCLINK macro instructionwith the STACK parameter (IEAVXSTK). Register15 contains one of these reason codes:

1110 PCLINK processing issued a GETMAINfor storage in the CSA. The GETMAINfailed; register 2 contains the GETMAINreturn code. The system writes neither anSDUMP nor an error record toSYS1.LOGREC.

12yy The program issued the PCLINK macro instructionwith the UNSTACK parameter (IEAVXSTK).Register 15 contains one of these reason codes:

1211 On the stack element queue, one of thepointers to the next stack element (STKE)is invalid. Register 2 contains the invalidpointer.

1212 On the stack element queue, one of thefields containing the ASID of the next stackelement (STKE) is invalid. Register 2contains the invalid ASID.

1297 The cause of the error is unknown. Thevariable recording area of the systemdiagnostic work area (SDWA) contains thefirst completion code and reason code thatthe PCLINK macro processing issued. Thecompletion code is in the VRAOA field andthe reason code is in the VRAOR15 field.

14yy A program call/authorization (PC/AUTH)initialization routine (IEAVNPF5 or IEAVXMAS)detected an error. The system writes neither anSDUMP nor an error record to SYS1.LOGREC.Register 15 contains one of these reason codes:

1411 The routine received a nonzero return codefrom the system address space createroutine (IEEMB881). Registers 2 and 0contain, respectively, the return code thatIEEMB881 passed in register 15 and thereason code that IEEMB881 passed inregister 0.

1412 The routine received a nonzero return codefrom the system address space initializationwait/post routine (IEEMB883). Registers 2and 3 contain, respectively, the return codethat IEEMB883 passed in register 15 andthe reason code IEEMB883 passed inregister 0.

1413 The routine called IEAVXEPM (thenucleus entry point module search routine),but IEAVXEPM was unable to process therequest. Register 2 contains the return codefrom IEAVXEPM. Register 3 contains theparameter that IEAVNPF5 or IEAVXMASpassed to IEAVXEPM in register 1.

1414 The sum of the highest linkage index (LX)value in the system function table (SFT)and the value in the SVTNSLX field of thesystem vector table (SVT) is greater thandecimal 1023. This condition indicates thatthe SFT or the SVT was incorrectlymodified. Register 2 contains the highestLX value in the SFT, and register 3contains the value in the SVTNSLX field.

1415 The routine received an invalid return codefrom IEAVEBBR, the bind break routine.Register 2 contains the return code.

054

Explanation: A scheduler service routineencountered an unrecoverable error.

System Action: One of the following reasoncodes is placed in register 15 to indicate thecause of the error:


01 A Scheduler JCL Facility (SJF) routine was unableto obtain enough storage from the preallocatedSJF storage area.

02 A Scheduler JCL Facility (SJF) routine had astorage pointer pointing to an area outside of thepreallocated SJF storage area.


055 to 057

ABEND

03 The Scheduler JCL Facility (SJF) Define JDVTroutine returned an unexpected return code orreason code to the SJF JDVT initializationroutine.

Programmer Response: Probable system error.The SJF storage area or parameter list mighthave been overlaid.

Problem Determination: Table I, items 16, 18,29, and 33.

055

Explanation: An error was detected during theprocessing of an event notification facility(ENF) request.

System Action: The system stores a hexadecimalreason code in register 15:


36 The requestor's event parameter list was destroyedafter initial validation.

40 The listen queue for the event being processedcontains an error.

Programmer Response: Probable system error.The storage containing the event parameter listor the listen queue may have been overlaid.

Problem Determination: Table I, items 2, 16, 18,29, and 33.

056

Explanation: The error occurred duringexecution of the graphic attention serviceroutine for the IBM 2250 Display Unit or theIBM 2260 Display Station. The routine referredto an invalid unit control block (UCB). Theroutine obtained the reference to the unitcontrol block through a data control block(DCB).

The user gives the routine the addresses of datacontrol blocks through the poll list address inthe first operand of the ANALYZ macroinstruction or the address of a data controlblock through the list item address in the firstoperand of the GSERV macro instruction. TheDCBDEBAD field in the data control blockpoints to a data extent block (DEB), which inturn points to the unit control block. The unit

control block is used by the control program toobtain information about an input/outputdevice; each unit control block is associated withone input/output device.

Programmer Response: Check the first operandin the ANALYZ or GSERV macro instructionto make sure that it correctly specified the polllist address or list item address. If the firstoperand was correct, make sure that the macroexpansion and the data control block were notincorrectly modified by program errors. Aftercorrecting the error, execute the job step again.


057

Explanation: The error occurred duringexecution of the graphic attention serviceroutine for the IBM 2250 Display Unit or theIBM 2260 Display Station. The routine referredto a unit control block (UCB) that wasassociated with a device other than a graphicdevice. The routine obtained the reference tothe unit control block through a data controlblock (DCB).

The user gives the routine the addresses of datacontrol blocks through the poll list address inthe first operand of the ANALYZ macroinstruction or the address of one data controlblock through the list item address in the firstoperand of the GSERV macro instruction. TheDCBDEBAD field in the data control blockpoints to a data extent block (DEB), which inturn points to the unit control block. The unitcontrol block is used by the control program toobtain information about an input/outputdevice; each unit control block is associated withone input/output device.

Programmer Response: Check the first operandin the ANALYZ or GSERV macro instructionto make sure that it correctly specified the polllist address or list item address. If the firstoperand was correct, make sure that the macroexpansion and the data control block were notincorrectly modified by program errors. Aftercorrecting the error, execute the job step again.



058 to 059

058

Explanation: A supervisor control routine hasdetected an error situation. Register 15 containsa hexadecimal reason code:


00 IEAVECMS detected an invalid CMSETRESET,CHKAUTH=YES request. The requesttried to establish a primary ASID that is invalidfor cross memory access and is not the homeASID. Registers 11 and 12 contain the values ofcontrol registers 3 and 4, which were received asinput from the caller.

04 IEAVECMS detected an invalid CMSETRESET,CHKAUTH=YES request. The requesttried to establish a primary ASID whose job steptask has terminated. Registers 11 and 12 containthe values of control registers 3 and 4, which werereceived as input from the caller.

08 IEAVECMS detected an invalid CMSETRESET,CHKAUTH=YES request. The requesttried to establish a primary ASID but there is noaddress space with the specified ASID. Registers11 and 12 contain the values of control registers 3and 4, which were received as input from thecaller.

0C IEAVECMS detected an invalid CMSETRESET,CHKAUTH=YES request. The requesttried to establish a secondary ASID whose jobstep task has terminated. Registers 11 and 12contain the values of control registers 3 and 4,which were received as input from the caller.

10 IEAVECMS detected an invalid CMSETRESET,CHKAUTH=YES request. The requesttried to establish a secondary ASID but there is noaddress space with the specified ASID. Registers11 and 12 contain the values of control registers 3and 4, which were received as input from thecaller.

14 IEAVESSE detected the error. A reserved inputfield is not zero. Registers 2 and 3 contain thevalues of registers 0 and 1, which were received asinput from the caller.

18 IEAVESSE detected the error. The caller is notauthorized to set the space switch indicator.Registers 2 and 3 contain the values of registers 0and 1, which were received as input from thecaller.

1C IEAVESSE detected the error. The caller passedan invalid ASID as input. Registers 2 and 3contain the values of registers 0 and 1, which werereceived as input from the caller.

20 IEAVECMS detected the error. The dispatcher(IEAVEDSO) issued the CMSET macroinstruction with the RESET option to restore the

cross memory environment of a task or an SRB. Aprogram interruption occurred while IEAVECMSwas executing. The task or SRB is abnormallyterminated.

24 IEAVECMS detected the error. The externalFLIH (first level interrupt handler), IEAVEEXT,issued the CMSET macro with the RESET optionto restore the cross memory environment of thetask or SRB that was interrupted. The erroroccurred while IEAVECMS was executing. Theinterrupted program is abnormally terminated.

System Action: The program that called thesupervisor function abnormally terminates.

Programmer Response: Find and correct theerror.

Problem Determination: Table I, items 16, 18,and 29.

059

Explanation: The stop/reset service routine(IEAVESRT) detected an error. Register 15contains a hexadecimal reason code:


00 The stop service received a disabled input PSW.

08 An unrecoverable error occurred within thestop/reset service routine.

0C STOP processing detected a request to stop anunlocked TCB that was already stopped.

10 RESET processing detected a request to reset alocked TCB that did not hold a local lock or CML(cross memory local) lock.

14

RESET processing detected a request to reset alocked TCB, and the ASCB lock word did notcontain a suspend id value (X'7FFFFFFF').

System Action: The program that called thestop/reset service routine is abnormallyterminated.

Programmer Response: The error is a system orsubsystem error. Contact your systemprogrammer.

System Programmer Response: If the problempersists, contact IBM for programming support.



05A to 05D

ABEND

05A

Explanation: The FREESRB or the FREESSRBroutine detected an error in the input it received.Register 15 contains a hexadecimal reason code:


00 FREESRB received the address of an SRB thatwas not from the supervisor SRB pool or that hadan invalid SRBID field.

04 FREESSRB received the address of an SSRB thatwas not from the supervisor SSRB pool or thathad an invalid SSRBID field.

System Action: The program that called theFREESRB or the FREESSRB routineabnormally terminates.

Programmer Response: The error is a system orsubsystem error. Contact IBM forprogramming support.


05B

Explanation: A system service running in SRBmode issued the SRBTIMER macro instruction,and the time limit established on theSRBTIMER has expired.

System Action: The system service abnormallyterminates.

Programmer Response: The appropriateresponse depends on your reason for setting thetime limit. This abend is 'retryable'. You canwrite a recovery routine to continue processing;your routine could issue the SRBTIMER macroinstruction again.

05C

Explanation: An allocation module detected anerror. Register 15 contains a hexadecimalreason code:


001 System address space initialization denied therequest to create the allocation address space.

002 The allocation address space received a nonzeroreturn code from GETMAIN processing.

003 The display allocation tables manager received arequest which, if processed, would cause theDALTUSE count to be less than zero.

004 An allocation module issued the POST macroinstruction, and the macro processing has enteredthe routine specified on the ERRET parameter.

005 An allocation module issued the ESTAE macroinstruction, and the return code from ESTAEprocessing was not zero.

701 A dynamic allocation module received anunexpected return code or reason code from thescheduler JCL facility update routine.

System Action: The system inserts this abendcode and the reason code into theABEND=cde, REASON=rc fields of messageIEF100I and issues the message.


Programmer Response: Probable system error.If necessary, contact IBM for programmingsupport.


05D

Explanation: A program has issued the branchentry CALLDISP macro instruction, but therequest is invalid. Register 15 contains ahexadecimal reason code:


00 The program is disabled and has super bits set.

04 The current FRR stack is not the normal FRRstack.

08 The program used the FRRSTK=SAVE optionand holds a lock, or the program usedFRRSTK=NOSAVE and holds a lock other thanthe LOCAL lock or the CML lock.

0C The program is RTM1, a service invoked byRTM1, or an FRR.

10 The program was not in TCB mode.

14 Register 0, on input, contained an invalid functioncode.

18 Register 1, on input, did not contain 0.

System Action: The program that issued theCALLDISP abnormally terminates.


05E to 062

Programmer Response: Correct the error andrerun the program.

Problem Determination: Table I, items 3, 4, 13,18, 19, and 29.

05E

Explanation: A program issued the SRBSTATmacro instruction, but an error condition exists.Register 15 contains a hexadecimal reason code:


00 The program holds a lock.

04 The current FRR stack is not the normal FRRstack.

08 The program has super bits set.

0C The program is not in SRB mode.

10 The program is disabled.

14 RTM1, a service that RTM1 invoked, or an FRRused the RESTORE parameter on the SRBSTATmacro instruction.

18 The PCLINK stack header was not zero on entryto RESTORE processing.

1C The program specified RESTORE or MODIFY,and the status save area does not contain validstatus.

20 RESTORE processing scheduled an SRB to obtaincorrect CPU affinity, but the SRB was unable torun.

24 The program specified MODIFY, but register 0contains an invalid MODIFY identifier code.

System Action: The program that issued theSRBSTAT abnormally terminates.

Programmer Response: Correct the error andrerun the program.


05F

Explanation: The VSPC address spaceencountered an error.

System Action: The VSPC address space and alladdress spaces that depend on the VSPC addressspace are abnormally terminated.


Problem Determination: Table 1, items 1, 2, 4, 5,13, 16, 18, 29.

061

Explanation: The error was detected duringexecution of a CLOSE macro instruction for agraphic data control block.

The graphic CLOSE executor issued a DARmacro instruction for a graphic attention controlblock (GACB) that was not specified (via aSPAR macro instruction) by the closing task.

System Action: Abnormal termination occurredfor the task that issued the SPAR macroinstruction for the graphic attention controlblock.

Programmer Response: Issue a DAR macroinstruction, for the graphic attention controlblock, in the task that issued the SPAR macroinstruction, before the closing task issues theCLOSE macro instruction. Then execute thejob step again.


062

Explanation: The error occurred duringexecution of a routine of the graphic subroutinepackage (GSP) for FORTRAN IV, COBOL,and PL/I.

A condition was encountered that produced areturn code equal to or greater than the absolutevalue specified by the programmer as the 'null'argument in the call to the INGSP subroutine.The GSPARRAY field in the GSPCB identifiesthe return code produced, register 2 contains theaddress of the status table entry last invoked,and register 3 contains the address of theGSPARRAY field.

Programmer Response: Determine the conditionthat caused the job step to be abnormallyterminated and change the program accordingly.Then execute the job step again.


063 to 066

ABEND


063

Explanation: During execution of a graphicprogram, the 2250 operator pressed theCANCEL key on the alphameric keyboard ofthe display unit. The 2250 operator selectedeither the TERMINATE option or the DUMPoption on the termination option display, thusterminating the problem program either with orwithout a dump.

Programmer Response: Find out why the 2250operator terminated the program, and respondaccordingly.

064

Explanation: An address space that holds across memory local lock (CML lock) terminatedabnormally before it freed the lock.

System Action: The functional recovery routinesassociated with CML lock processing are givencontrol. Other system processing continues.

Programmer Response: Determine why theaddress space terminated, and correct the error.


065

Explanation: A program issued the SSAFFmacro instruction to call IEAVESSI, the TCBsubsystem affinity service routine. IEAVESSIdetected an error. Register 15 contains ahexadecimal reason code:


04 The index into the SSAT (subsystem affinitytable), specified in the SSAFF macro instruction,is greater than the number of subsystems currentlydefined.

08 The caller is not in TCB mode.

0C LSQA storage is too small to build the SSAT(subsystem affinity table).

10 The specified TCB is invalid. It does not includethe TCB acronym.

14 The caller is disabled.

1C The caller's current addressability was not to thehome address space.

20 The specified TCB is not the currently active TCBor a subtask of the currently active TCB.

System Action: The system abnormallyterminated the program that issued the SSAFFmacro instruction.

Programmer Response: For reason codes 04, 08,10, 14, 1 C, and 20, probable user error. Correctthe error and resubmit the job.

For reason code 0C, probable system error.Contact IBM for programming support.

Problem Determination: Table I, items 5a, 13,16, 18, and 29.

066

Explanation: An error condition wasencountered during the execution of the MVSdispatcher (IEAVEDSO). Register 15 contains ahexadecimal reason code:


04 A completed SRB held a system lock when itreturned to the dispatcher.

0C An SSRB holds the CML (cross memory local)lock of a failing address space. (The ASCBFAILbit is on.)

10 The SRBASCB field of an SRB or an SSRBpoints to an ASCB that does not have a validacronym.

14 A task holds the CML lock of a failing addressspace. (The ASCBFAIL bit is on.)

System Action: The system records the error inSYS1.LOGREC.

Programmer Response: Notify the systemprogrammer.

Problem Determination: Table I, items 2, 4, 5a,18, and 29.

System Completion Codes SCC -29

069 to 06E

069

Explanation: An error occurred in the systemaddress space create routine (IEEMB881) afteran ASCB was created for the new address space.

System Action: The system uses the CALLRTMmacro instruction with the MEMTERMparameter to abnormally terminate the newaddress space with the 069 completion code.

Programmer Response: Determine whyIEEMB881 failed and correct the error.


06A

Explanation: An SRB's FRR (functionalrecovery routine) issued the SETRP macroinstruction with the SERIAL=YES option torequest serial percolation to its related task.RTM (recovery termination management) issueda GETMAIN for storage in the task's LSQA torecord the registers and the PSW at the time oferror. The GETMAIN failed; the task cannotdetermine what the registers contained, or whatthe PSW was, when the error occurred.

System Action: RTM abnormally terminates thetask.

Programmer Response: Determine why theGETMAIN failed. (Check for the possibility ofan LSQA GETMAIN loop.)


06C

Explanation: The RTM/SLIP processor(IEAVTSLP) detected one of the followingconditions:

• While processing a PER interrupt, theRTM/SLIP processor found that the routinebeing monitored issued a Move Long(MVCL) instruction that would overlay lowstorage.

• The environment indicators that control theRTM/SLIP processor were overlaid orinvalid for some other reason.

System Action: RTM/SLIP processingterminates for the current event. The status ofPER in the system and of the existing SLIPtraps is unchanged.

Programmer Response: If the routine beingmonitored caused the problem, correct theprogram.


06D

Explanation: RTM/SLIP processing found thatan invalid parameter list was passed to the SLIPindirect address convert routine (IEAVTADR).

System Action: RTM/SLIP processingterminates for the current event. The status ofPER in the system and of the existing SLIPtraps is unchanged.

Programmer Response: Contact IBM forprogramming support.

Problem Determination: Table I, item 2, 16, 29.

06E

Explanation: One of the following conditionsoccurred during SLIP processing:

• The SLIP global PERactivation/deactivation routine(IEAVTGLB) received a nonzero returncode from BLDCPOOL macro processing,indicating that an error occurred.

• The SLIP local PER activation/deactivationroutine (IEAVTLCL) received a return codeother than 0 or 20 from FREECELL macroprocessing, indicating that an erroroccurred.

System Action: SLIP processing terminates.


Problem Determination: Table I, items 2, 16, 29.


06F to 073

ABEND

06F

Explanation: RTM was entered after a matchwas found for a SLIP PER trap, which wasdefined with the RECOVERY option.

System Action: The job being monitored entersnormal recovery processing. SLIP processingcontinues.


070

Explanation: A program issued the SUSPEND,RESUME, or TCTL macro instruction but anerror condition existed. Register 15 contains ahexadecimal reason code:


0C The program issued the RESUME macroinstruction with the RETURN=N parameter, butthe program was not in SRB mode.

10 The program issued the RESUME macroinstruction, but the specified TCB was invalid.

14 The program issued the RESUME macroinstruction, but could not address the specifiedASCB.

18 The program issued the RESUME macroinstruction with the RETURN=N parameter, butthe program was not in home addressing mode.

1C The program issued the RESUME macroinstruction with the RETURN=N parameterwhile holding one or more locks or while runningwith a PCLINK stack that was not empty.

20 The program issued the TCTL macro instruction,but was not in SRB mode.

24 The program issued the TCTL macro instruction,but was not in home addressing mode.

28 The program issued the TCTL macro instructionwhile holding one or more locks or while runningwith a PCLINK stack that was not empty.

2C The program issued the RESUME macroinstruction with the MODE=UNCONDparameter and the ASYNC=N parameter, but theprogram held the local lock of an address spaceother than the target address space.

30 The program issued the SUSPEND macroinstruction, but the RB suspend count was notzero.

34 The program issued the SUSPEND macroinstruction with the RB=PREVIOUS parameter,but no previous RB existed.

38 RESUME processing detected a request to resumean RB that had a suspend count other than 0 or 1.

40 A RESUME with the unconditional synchronousoptions required the local lock. The issuer wasdisabled and did not hold the necessary local lock.

System Action: The program that issued themacro instruction abnormally terminates.

Programmer Response: Correct the error, andrerun the program.


071

Explanation: The operator pressed theRESTART key to activate the system's recoveryand termination process. The program runningat the time the operator pressed the RESTARTbutton was sent through ABEND processingbecause the operator determined it was in anoncancelable loop or wait state.

Programmer Response: Correct the loopingprogram, and resubmit the job.

072

Explanation: A task or SRB (service requestblock) has been terminated because theprocessor on which it can run is offline.

Programmer Response: Resubmit the job whenthe job's processor affinity requirements aremet.

073

Explanation: The lock manager detected anerror during SETLOCK OBTAIN orSETLOCK RELEASE processing. Register 12contains the PSASUPER bits at the time of the


074

ABEND. Register 13 contains the highestlock-held indicator (PSAHLHI) current whenthe lock request was made. Register 15 contain;a hexadecimal reason code:


00 While spinning for a disabled spin lock, the lockmanager found that the lockword contains aninvalid processor ID. Register 10 contains theinvalid lockword value.

04 Invalid serialization. A disabled caller requestedthe LOCAL, CML, or CMS lock unconditionally,but the lock was not immediately available.

08 Hierarchy violation. If a SETLOCK OBTAINrequest was being processed, one of the followingoccurred:

• The requested lock was lower in the lockinghierarchy than the locks currently held.

• Another lock of the same type was alreadyheld.

• A CMS lock was requested but a local lockwas not held.

If a SETLOCK RELEASE request was beingprocessed, one of the following occurred:

• A local lock was specified while a CMS lockwas still held.

• All CMS locks were specified, but not allCMS locks were held.

0C A caller requesting a CML (cross memory local)lock passed an invalid ASCB address. Register 11contains the ASCB address.

10 The caller requested another address space's CML(cross memory local) lock but did not establish anactive bind to that address space. Register 11contains the ASCB address.

14 The caller specified an ASCB for an address spacethat was being terminated. Register 11 contains theASCB address.

18 The caller requested the CML (cross memorylocal) lock of an address space that was notdispatchable. Register 11 contains the ASCBaddress.

1C The caller requested the CML lock of the masteraddress space or the WAIT address space.

System Action: The program that requestedSETLOCK processing abnormally terminates.

Programmer Response: Check the programissuing the SETLOCK request to be sure therequest was made correctly.


074

Explanation: One the following occurred:

1. An invalid lockword address was specified,or the SETLOCK function could notcomplete. One of the following applies:

a. The lockword address was not on afullword boundary.

b. A page fault occurred when the systemused the specified lockword address.

c. A machine check occurred in alockword that a user supplied.

2. The RESTART key was hit while thesystem was in an enabled wait state with asuspended user holding a CMS (crossmemory services) lock. The lock managerrepair routine, IEAVELKR, stole the CMSlock and terminated the suspended holder ofthe CMS lock with this 074 completioncode.

Programmer Response: For cases la and lb,probable user error. Make sure the source codeis correct. For case lc, probable hardwareerror. You may retry the function. If theproblem occurs again and the function iscritical, place the system in a wait state with anassigned wait state code. If the function is notcritical, continue system operation without it.

Problem Determination: Table I, items 3, 4, 13,18, 29, 30.


075 to 077

ABEND

075

Explanation: The SRBASCB field of the SRBthat was being scheduled did not point to avalid ASCB.

System Action: The system abnormallyterminated the routine.

Programmer Response: A supervisor state key 0program scheduled an SRB that does not pointto a valid ASCB, because the acronym checkfailed. Correct the error, and resubmit the job.

Problem Determination: Table I, items 2, 3, 4,18, 19, 29, and 31.

076

Explanation: An error occurred whileattempting to create a new address space, or anunexpected abnormal termination occurred inaddress space create or address spaceinitialization.

System Action: Address space terminationdeletes the partially created address space.Message IEA890I is issued to identify thecommand that was aborted because of thefailure.

Programmer Response: Notify the systemprogrammer of this ABEND.


077

Explanation: An error occurred while processinga console communications task request.Register 15 contains a hexadecimal reason code:


00 A request to start or stop MONITORJOBNAMES, STATUS, or SESSIONS processingwas made using a console ID or address space ID(ASID) that is invalid for a terminal user.

04 The parameter list passed to module IEAVC700was invalid.

08 The caller requested deletion of a nonexistentcommand queue buffer (CQB).

0C Module IEAVC700 could not establish an ESTAEenvironment.

10 The parameter list passed to module IEAVQ700was invalid.

14 The caller of IEAVQ700 was not executing in the communications task's address space.

18 The console communications task was not able toobtain a console queue element (CQE).

1C A console request, processed by the subsystemconsole service routine, IEAVG700, could not behonored because of conflicting requests in thesubsystem console service routine parameter list.

20 A console request, processed by the subsystemconsole service routine, IEAVG700, could not behonored because incomplete or invalid data wasprovided in the subsystem console service routineparameter list.

24 A console request, processed by the subsystemconsole service routine, IEAVG700, could not behonored because the specified console was notdedicated to the requesting system component.

System Action: If the error occurred duringMONITOR or STOPMN command processing,the MONITOR function is not changed.Otherwise, the calling routine terminatesabnormally.

Operator Response: If the error occurred duringMONITOR command processing, reissue theMONITOR or STOPMN command.

For code X'18', a message backlog may exist onone or more consoles. Ease the backlog byeither allowing the messages to roll off thescreen or by rerouting the messages to SYSLOGwith the CONTROL Q command.

Otherwise, notify the system programmer.

System Programmer Response: For reason code1C, 20, or 24, verify that the system componentthat is requesting services of the subsystemconsole service routine has properly specified therequest in the subsystem console service routineparameter list.

Otherwise, contact IBM for programmingsupport.

Problem Determination: Table I, items 2, 13, 16,29, 43.


078 to 07C

078

Explanation: RCT processing has received anunacceptable return code from an invokedroutine and cannot continue processing.

System Action: RCT recovery receives controland does the following:

• Records the error in SYS1.LOGREC.• Performs resource clean-up.• Requests a SYS1.DUMP of the address

space.• Requests address space termination.


Problem Determination: Save themodule/function information recorded inSYS1.LOGREC. Table I, items 16, 29.

079

Explanation: RCT attention exit processingencountered an unacceptable return code froman invoked routine and cannot continueprocessing.

System Action: RCT recovery code receivescontrol and does the following:

• Records the error in SYS1.LOGREC.

• Performs resource clean-up.

• Issues an error message to the terminalindicating that the attention request wasignored, or requests a SYS1.DUMP of theaddress space.

Programmer Response: If an error message isissued to the terminal, either continue processingwithout regenerating the attention interrupt, orregenerate an attention interrupt to either thesame attention level or a different level. If aSYS1.DUMP was taken, no response is possible.

Problem Determination: Save themodule/function information recorded inSYS1.LOGREC. Table I, items 16, 29.

07A

Explanation: RCT recovery processing detectedthat it was invoked as the result of anunrecoverable error. To avoid an address spaceinterlock, RCT issued CALLRTM to terminatethe address space. The conditions that causeCALLRTM to be issued are:

• An SIRB failure• A serious error during swap-out processing

System Action: The system does not clean upthe address space-related resources; the systemabnormally terminates the address space. Thesystem may or may not write a record toSYS1.LOGREC.


Problem Determination: Table I, items 16, 18,29.

07B

Explanation: The error occurred during theexecution of a remote immediate, remotepending, or direct signal inter-processorcommunication service request. One of theseroutines was supplied with an invalid PCCAaddress.

System Action: The system abnormallyterminates the requestor and writes a dump.

Programmer Response: Check for programerrors that could have improperly loaded aninvalid PCCA address.


07C

Explanation: Supervisor control recoverydetected an error that requires termination ofthe current task or current address space.

System Action: The system abnormallyterminates either the current task or the currentaddress space.

Operator Response: Notify the systemprogrammer of this ABEND code.


07D to 081

ABEND


07D

Explanation: The system was executing aSETFRR macro instruction to add an FRR toone of the FRR recovery stacks. The systemfound that the recovery stack, for which theSETFRR was issued could hold no more FRRs;all available slots were filled.

System Action: The task associated with thisstack overflow condition is abnormallyterminated because recovery (FRRs, ESTAEs,etc.) for the task was unsuccessful.

Programmer Response: Probable error innon-IBM, key 0 code. The system programmershould determine if a non-IBM, key 0 programin the control system and used by the problemprogram is either adding FRRs without deletingthem or is in a SETFRR loop.

Problem Determination: Table I, items 5a, 13,15, 18, 23, 29. Table II, format I:TRACE=SYS,DSP.

07E

Explanation: The device path-test subroutine,IEEVDEV, cannot continue processing for oneof the following reasons:

• The UCB address, passed by IEEVDEV'scaller, did not point to the common segmentof the UCB.

• An unrecoverable error occurred duringIEEVDEV processing.

• An invalid processor ID was passed forfunction code 01 and 02.

System Action: Register 15 contains ahexadecimal reason code:


04 Invalid UCB address.

08 Unrecoverable error during IEEVDEV processing

0C Invalid function code passed to IEEVDEV.

10 Invalid processor ID.

14 Return code was received from IECVIOPMindicating that an unrecoverable program error orhardware error occurred.

Programmer Response: Verify the UCB addressof the UCB common segment. Verify that theprocessor ID represents a valid physicalprocessor. For reason code 14, if the intent is tobring the device online, try to vary theindividual paths to the device online.

Note: IEEVDEV is called only by systemfunctions. An abnormal termination willactivate the calling function's recovery routines;the caller will decide if the system operatorshould be notified.

07F

Explanation: During recovery, verification ofthe TCB queue associated with the terminatedaddress space resulted in an empty TCB queue.

System Action: The address space or job isterminated.

Programmer Response: Resubmit the job.


081

Explanation: GETMAIN and IEAVITAS havepassed an incorrect virtual address toIEAVSQA. A system function, GETMAIN orIEAVITAS (RSM), is in error.

System Action: The request for an LSQA orSQA real storage frame is denied.


Problem Determination: Table I, items 1, 5a, 16,29.


082 to 085

082

Explanation: When the system tried to release aSALLOC lock, SETLOCK returned code 8,which indicates that the lockword ID does notmatch caller's ID.

System Action: The FRR is entered to recordthe error, and the caller is terminated.

Programmer Response: Probable system error.None.


083

Explanation: Auxiliary storage manager (ASM)was unable to convert a logical slot identifier(LSID) to a full seek address. The relative byteaddress (RBA) is outside the range of theextension data block (EDB) entries.

System Action: The ASM I/O request area(AIA) being processed is marked in error. Thesystem writes a software error record containinga copy of the AIA and EDB toSYS1.LOGREC. Processing continues.


Programmer Response: Probable system error.Contact IBM for programming support.


084

Explanation: The I/O subsystem of ASM(auxiliary storage management) detected anerror. Register 15 contains a hexadecimalreason code:


4 The I/O termination routine received control withI/O requests that are not marked with a X'45'

code from IOS and that have not been processedby the disabled interrupt exit (DIE) or theabnormal end appendage.

12 The anchor in the page activity reference table(PART) or swap activity reference table (SART)entry for the ASM IORB-IOSB-SRB is zero.

Page data sets on drums and swap data setshave more than one IORB-IOSB-SRB.Therefore, the loss of one IORB-IOSB-SRB maynot cause this completion code to be issued.

System Action: For reason code 4, a softwareerror record is written to SYS1.LOGREC, andthe I/O is retried. Processing continues.

For reason code 12, the system does thefollowing:

• Attempts to obtain a new IORB-IOSB-SRB.

• If no storage is available for a newIORB-IOSB-SRB, message ILR009I isissued, and the data set identified inmessage ILR009I is no longer used.Processing continues, if possible.

O If processing cannot continue, messageILR008W is issued. A software error recordis written to SYS1.LOGREC.




085

Explanation: The VIO SAVE operator couldnot convert a relative page number (RPN) to alogical-to-physical mapping entry (LPME) in aretrieved auxiliary storage page correspondencetable (ASPCT).

System Action: A software error record iswritten to SYS1.LOGREC, and processingcontinues.




SCC-36 OS/VS Message Library: VS2 System Code;

086 to 090

ABEND

086

Explanation: The VIO SAVE or ACTIVATEoperator received an error from VSAM duringan I/O operation attempt.



Programmer Response: Probable hardwareerror.


087

Explanation: Routine ILRAFS00 received anerror return from FREEMAIN while attemptingto free the virtual storage containing anauxiliary storage page correspondence table(ASPCT).





08F

Explanation: An error occurred duringexecution of the CHANGKEY macroinstruction.



04 At least one page in the virtual address rangespecified in CHANGKEY is not in a problemprogram subpool.

08 At least one page in the virtual address rangespecified in CHANGKEY was not allocated viaGETMAIN. (The PGTPAM bit in the PGTE forthe page is zero.)

0C The user's parameter list, specified by the LISTADparameter, was not in real storage whenCHANGKEY was invoked.

10 No PGTE or XPTE exists for at least one page inthe virtual address range specified inCHANGKEY. (The return code from IEAVFP2is nonzero.)

14 An unexpected internal error occurred.

System Action: The invoker of CHANGKEY isabnormally terminated.

Programmer Response: For reason code 04 or0C, correct the error condition indicated.

For reason code 08 or 10, verify that all pageswithin the virtual address range(s) have beenallocated via GETMAIN, and have not beenfreed via FREEMAIN.

For reason code 14, execute the job step again.


090

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.An OPEN routine found that a device otherthan a communications device was allocated tothe data control block (DCB) being opened; thatis, the device class code in the unit control block(UCB) for the device allocated to the datacontrol block did not equal hexadecimal 40.

Programmer Response: Either the UNITparameter of the DD statement for thecommunications device is incorrect or the UCBgenerated during system generation is invalid.Check for improper specification of the UNITparameter or the IODEVICE macro instructionused in generating the system. Also, check forprogram errors that could have improperlymodified control information. After correctingthe error, execute the job step again.



091 to 095

091

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.An OPEN routine found an invalid orunsupported type of transmission control unitspecified in the unit control block (UCB) for thedevice allocated to the data control block(DCB) being opened.

Programmer Response: Check for improperspecification of the IODEVICE macroinstruction used in generating the system. Also,check for program errors that could haveimproperly modified control information. Aftercorrecting the error, execute the job step again.


092

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.An OPEN routine found an invalid orunsupported type of terminal control orterminal adapter specified in the unit controlblock (UCB) for the device allocated to the datacontrol block (DCB) being opened.

Programmer Response: Check for improperspecification of the ADAPTER parameter in theIODEVICE macro instruction used ingenerating the system. Also, check for programerrors that could have improperly modifiedcontrol information. Correct the error, andexecute the job step again.


093

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.An OPEN routine found an invalid orunsupported type of terminal specified in theunit control block (UCB) for the deviceallocated to the data control block (DCB) beingopened.

Programmer Response: Check for improperspecification of the UNIT parameter in theIODEVICE macro instruction used ingenerating the system. Also, check for programerrors that could have improperly modifiedcontrol information. Correct the error, andexecute the job step again.


094

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.An OPEN routine found an invalid orunsupported optional feature or mode ofoperation specified in the unit control block(UCB) for the device allocated to the datacontrol block (DCB) being opened.

Programmer Response: Check for improperspecification of the FEATURE parameter in theIODEVICE macro instruction used ingenerating the system. Also, check for programerrors that could have improperly modifiedcontrol information. Correct the error, andexecute the job step again.


095

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.An OPEN routine found that the lines allocatedto the line group did not have identical terminaltypes and/or optional features.

Programmer Response: Determine which linegroup contains different terminals, and redefineits lines through DD statements or a new systemgeneration.

Problem Determination: Table I, items 1, 3, 5a,29.


096 to 09A

ABEND

096

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.An OPEN routine found that dynamic bufferallocation had been specified in theDCBBFTEK field of the data control block(DCB). However, the OPEN routine could notdynamically allocate buffers because the datacontrol block specified neither the address of abuffer pool control block (in the DCBBUFCBfield) nor the number and length of the buffers(in the DCBBUFNO and DCBBUFL fields).

Programmer Response: Correct the error by (1)providing a buffer pool and specifying theaddress of its control block in the DCBBUFCBfield, (2) specifying the number and length ofthe buffers in the DCBBUFNO and DCBBUFLfields, or (3) handling buffering in the programand deleting the BFTEK=D operand in theDCB macro instruction or DCB parameter ofthe DD statement. Then execute the job stepagain.


097

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.The open routine required an additional entry inthe device I/O directory; however, the directorywas already full. Since the last system start, themaximum number of device types has alreadybeen opened. Normally, the maximum numberof device types is 30.

Programmer Response: Additional space in thedevice I/O directory can be provided bychanging one statement in the read/writeroutine. The statement following the onelabeled IOD must be changed. The duplicationfactor must be increased to correspond to thenumber of different device types being used.The new read/write routine must be reassembledand link edited to SVCLIB.


098

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.Dual Communication Interface B or Dual CodeFeature B was specified. However, thetransmission control unit was not a 2701, thetransmission control unit was not the DualCommunication Interface, or the Dual CodeFeature was not specified in the unit controlblock (UCB).

Programmer Response: Correct program errors,and execute the job step again.


099

Explanation: The error occurred duringexecution of a BTAM OPEN macro instruction.An OPEN routine found that dynamic bufferingwas being initiated while the BTAM applicationwas running V=V. BTAM dynamic bufferingis not supported for V=V.

Programmer Response: Add theADDRSPC=REAL operand to the jobstatement and initiate the BTAM applicationagain (V=R).


09A

Explanation: An error occurred duringexecution of a global resource serializationfunction. The two low-order bytes of register 15contain mmff, where mm is a one-byte codeidentifying the module that issued the ABENDand ff is a one-byte hexadecimal codeidentifying the function that the module wasperforming. The possible values for mm are:

mm module

22 ISGNTASC23 ISGNASIM25 ISGNWMSI26 ISGNGRSP41 ISGCMDI42 ISGCMDR43 ISGCRST44 ISGCQSC45 ISGCPRG


09A

46 ISGCDSP47 ISGMSG00

48 ISGCQMRG61 ISGBDR62 ISGBCI63 ISGBSR64 ISGBTC81 ISGSALCAl ISGQSCANA2 ISGQSCNREl ISGJFEE2 ISGGRP00

For an ff of 40 through FF, ff is the same forall values of mm and means:

RP00 Function

44 GQSCAN46 ISGMSG00

48 ISGGRNLV86 ISGGQS03A0 ADDSYSA2 BUFRECVA4 BUFSENDA6 DELSYSA8 SENDCMD (message broadcast)AA SENDCMD (message request)AC SENDCMD (quiesce)AE SENDCMD (assist in restart request)B0 SENDCMD (initiate restart request)B2 SERRELSB4 SNAPSHOTB6 STARTPOP (no communication)B8 STARTPOP (with communication)B9 STARTPOP (with permission)BA SUBSYSE0 ATTACHEC MSGSERV (get line)EE GETMAINFA MSGSERV (write message)FC WTO (multiple line)

For an ff of 00 through 3F, ff is different foreach module identified by mm:

mmff

22xx

Function

Module ISGNTASC issued the ABEND.

2204 IEEMB881 (the system address space createroutine) did not execute successfully.

23xx Module ISGNASIM issued the ABEND.

2304 ISGNASIM tried unsuccessfully to use the eventnotification facility (ENF) to establishISGNPGIM as a listener for the availability oftimer and console services.

2308 ISGNASIM tried unsuccessfully to establish arecovery environment with the ESTAE macroinstruction.

230C The ATTACH for ISGNWMSI (the routine thatwaits for master scheduler initialization tocomplete) was not successful.

2310 The ATTACH for ISGCMDR (the globalresource serialization command router) was notsuccessful.

2314 The ATTACH for ISGGRP00 (the global resourceprocessor) was not successful.

2318 ISGGRP00 (the global resource processor) did notsuccessfully complete initialization.

231C The ATTACH for ISGBTC (global resourceserialization ring processing control task) was notsuccessful.

2320 ISGBTC (global resource serialization ringprocessing control task) did not successfullycomplete initialization.

2324 The ATTACH for ISGNGRSP (the globalresource serialization option processor) was notsuccessful.

2328 ISGGRP00 (the global resource processor)abnormally terminated.

232C ISGBTC (the global resource serialization ringprocessing control task) abnormally terminated.

2330 ISGNGRSP (the global resource serializationoption processor) abnormally terminated.

25xx Module ISGNWMSI issued the ABEND.

2504 IEEMB883 (the system address space initializationWAIT/POST routine) did not execute successfully.

41xx Module ISGCMDI issued the ABEND.

4104 The ATTACH for ISGCDSP (the global resourceserialization DISPLAY processor) was notsuccessful.

42xx Module ISGCMDR issued the ABEND.

4204 The global resource serialization command routerfound a command request block (CRB) that hadan invalid request type.

4208 No resources were found on the commandclean-up queue for the command request mostrecently processed.

47xx Module ISGMSG00 issued the ABEND.

4704 The caller provided an invalid message ID.

4708 The caller provided a message option that isinvalid for the specified message.

470C The caller requested an informational message butspecified the ID of a reply message, or requested areply message but specified the ID of aninformational message.

48xx Module ISGCQMRG issued the ABEND.


09A

ABEND

4804 The version of global resource serialization in thissystem is not compatible with the version in therest of the global resource serialization complex.

4808 The inclusion resource name list defined for thissystem is not identical to the one that the activeglobal resource serialization systems are using.

480C The exclusion resource name list defined for thissystem is not identical to the one that the activeglobal resource serialization systems are using.

4810 The RESERVE conversion resource name listdefined for this system is not identical to the onethat the active global resource serialization systemsare using.

4814 This system's request for a particular resource ismissing from the queue information provided bythe active system. Queue damage possibly exists inthe global resource serialization queues of thissystem or the system assisting in bringing it intothe complex.

4818 This system's request for a particular resource ismissing from its own global resource serializationqueues. Queue damage possibly exists in theglobal resource serialization queues of this systemor the system assisting in bringing it into thecomplex.

481C The active global resource serialization system thatprovided this system with queue informationindicated that all data has been sent, but thissystem still expects more data. That is,ISGCQMRG expected to receive more data, butISGBCI showed a buffer length of zero wasreceived.

4820 Internal queue update processing lost track of thetype of item currently being processed.

4824 Internal queue update processing found data in itsbuffer or in the ring's buffer that it did not expectto find.

4828 Internal queue update processing expected to findmore data (RIBE) in its buffer, but the buffer wasempty.

482C Internal queue update processing reached the endof the ring's buffer before it reached the logicalend of the data in the buffer.

4834 Internal queue update processing found more datain the ring's buffer than it expected to find.

4838 Internal queue update processing found a ringbuffer that did not contain as many RIBs orRIBEs as indicated by the counts returned byGQSCAN services.

61xx Module ISGBDR issued the ABEND.

6104 ISGBDR attempted to queue a RSA(ring-processing system authority message)residence TQE (timer queue element), but therewas already a RSA residence TQE queued.

6108 The STCK (store clock) instruction failed.

62xx Module ISGBCI issued the ABEND.

6204 Module ISGBCI attempted a STIMER WAIT fora negative time interval, or for a single pauselonger than 2 minutes.

620C A channel end status was not received for animmediate write command to a CTC(channel-to-channel) link, which caused aSNAPSHOT operation to fail. The time allowedfor the channel end was: a times b times .01seconds (where a is the value in GVTICRRC, andb is the value in GVTICRRP). The time is twoseconds if the installation has not modified theGVT fields. Register 2 points to the RSL(ring-processing system link control block) thatrepresents the CTC link that did not respond withthe channel end.

63xx Module ISGBSR issued the ABEND.

6301 The received RSA (ring-processing systemauthority message) had an invalid format.

6302 The RSVWLOCK field of the RSV(ring-processing system vector table) contained aninvalid value.

6303 Entry point ISGJGVBF (module ISGJFE) gave anonzero return code to ISGBSRSR.

6304 Entry point ISGJSNBF (module ISGJFE) gave anonzero return code to ISGBSRSR.

6305 Entry point ISGBSRRM, the RMTR (resourcemanagement termination routine) for ringprocessing SRBs, was entered.

6306 The received RSA (ring-processing systemauthority message) did not agree with thein-storage fields in the RSV (ring-processingsystem vector table). The received RSA was thesecond RSA of an ENQ/DEQ request that did notfit in one RSA, but the RSV indicated the RSAwas the first RSA of the ENQ/DEQ request. Or,the received RSA was the first RSA of theENQ/DEQ request, but the RSV indicated theRSA was the second.

6321 The received RSAIRCD (ring-processing systemauthority identity message) had an invalid format.

6322 The RSLWLOCK field of the RSL(ring-processing system link control block) had ainvalid value.

6323 Entry point ISGJGVBF (module ISGJFE) gave areturn code that indicates an error condition toISGBSRRI.

6324 Entry point ISGJSNBF (module ISGJFE) gave areturn code that indicates an error condition toISGBSRRI.

64xx ISGBTC issued the ABEND.


09A

6404 ISGBTC called ISGBDR to establish themissing-event checking routine, but the systemclock was not working properly.

81xx Module ISGSALC issued the ABEND.

8104 ISGSALC cannot build a new PEXB (pool extentblock) because the resource queue area containsno available pages.

Alxx ISGQSCAN issued the ABEND.

A104 A program attempted to execute the GQSCANmacro instruction before the global resourceserialization address space was active.

A108 The area size specified in the AREA parameter istoo small for ISGQSCAN to copy a RIB andRIBE.

A10C The specified combination of the RESERVE,RESNAME, and SYSNAME parameters includedmutually exclusive parameters.

A110 A program holding a local lock other than the onefor the global resource serialization address spacespecified SCOPE=GLOBAL,SCOPE=SYSTEMS, or SCOPE=ALL, therebypreventing ISGQSCAN from obtaining the globalresource serialization local lock.

A114 The GQSCAN macro instruction includes one ofthese specification errors:

• The RESNAME parameter includes thername subparameter or the rname lengthsubparameter, but omits the qnamesubparameter.

• The RESNAME parameter includes thername length subparameter, but omits thername subparameter.

A118 The SYSNAME parameter on the GQSCANmacro instruction includes the asid subparameter,but omits the sysname addr subparameter.

A11C The GQSCAN macro instruction includes theREQCNT parameter and either the OWNERCTor the WAITCNT parameter.

Al2C The value specified on the TOKEN parameter onthe GQSCAN macro instruction is invalid.

A130 An unauthorized program specifiedSCOPE=LOCAL or SCOPE=GLOBAL.

A134 The QUIT=YES parameter is specified withoutthe TOKEN parameter.

A138 The QUIT=YES and the TOKEN parameters arespecified with other parameters.

A2xx ISGQSCNR (ISGQSCAN's functional recoveryroutine) converted the ABEND.

A220 An undefined error occurred during GQSCANservice routine processing (ISGQSCAN).

A228 The parameter list passed to GQSCAN serviceroutine (ISGQSCAN) was not in the caller'sstorage key.

Elxx ISGJFE issued the ABEND.

E104 ISGBTC tried to make an SRB available to theCTC driver, but the CTC driver already hadcontrol of the SRB.

E2xx ISGGRPOO issued the ABEND.

E200 ISGGRPOO received an undefined queue workblock (QWB).

E3xx Module ISGJENFO issued the ABEND.

E304 Entry point ISGJENF1 in ISGJENFO could notestablish an ESTAE environment.

E308 Entry point ISGJENF2 in ISGJENFO could notestablish an ESTAE environment.

E30C Entry point ISGJENF3 in ISGJENFO could notestablish an ESTAE environment.

System Action: The system writes a softwareerror record to SYS1.LOGREC for all of theseABENDs except the following:

• ABENDs issued by ISGNTASC (mm=22)• ABENDs issued by ISGNWMSI (mm=25)• ABENDs issued by ISGQSCAN (mm=Al)• The ABEND issued by ISGQSCNR with

mmff=A228Other system processing continues.

Programmer Response: For mmff fields of 4808,480C, 4810, Alxx, or A228, probable user error.Correct the problem, and resubmit the job.

For other values of mmff, probable systemerror. Contact IBM for programming support.



ABEND

0A1 to 0A4

0A1

Explanation: An invalid condition was detectedby the Graphics Access Method/System Product(GAM/SP) OPEN executor routine, IGG0193Y.The error occurred in either GAM/SP or theoperating system.

System Action: A message appears on thesystem console that identifies the cause of theerror; and GAM/SP produces a dump on thesystem dump data set.

Programmer Response:

1. Check for messages identifying the cause ofthe error. If these are GAM/SP messages,(that is, the message number is of the form

'GABnnn'), they are described in IBMGraphics Access Method/ System Product:Messages and Codes.

2. Get a listing of the system dump.

3. Contact IBM for programming support.

0A2

Explanation: An invalid condition was detectedby the Graphics Access Method/System Product(GAM/SP) CLOSE executor routine,IGG0203Y. The error occurred in eitherGAM/SP or the operating system.

System Action: A message appears on thesystem console that identifies the cause of theerror and GAM/SP produces a dump on thesystem dump data set.



'GABnnn'), they are described in IBMGraphics Access Method/System Product:Messages and Codes.



0A3

Explanation: An error was detected in theGraphics Access Method/System Product(GAM/SP) attention handler module,

IGG019OE. The error may have originated inthe GAM/SP OPEN executor, IGG0193Y. Itcould also be caused by modules IGG019OEand IGG0193Y being at inconsistentmaintenance levels.

System Action: A message appears on thesystem console that describes the error. Inaddition, GAM/SP writes a record to theSYS1.LOGREC dataset and produces a dumpon the system dump dataset.




2. Check the module identifiers and PTF levelsfor modules IGG019OE and IGG0193Y.



0A4

Explanation: An error occurred either in theGraphics Access Method/System Product(GAM/SP) or in the operating system.

This completion code is issued when:

1. A program check or abnormal terminationoccurs in the Graphics AccessMethod/System Product (GAM/SP)attention handler module, IGG019OE.

2. IGG019OE detects an invalid condition.

System Action: A message appears on thesystem console, accompanied by a reason codeidentifying the area of processing in which theerror occurred. In addition, GAM/SP writes arecord to the SYS1.LOGREC dataset andproduces a dump on the system dump dataset.


0A5 to 0A9






0A5

Explanation: A program check or abnormaltermination occurred within the Graphics AccessMethod/System Product (GAM/SP) attentionhandler module, IGGO19OE. The recoveryroutine for IGGO19OE determined that theproblem was caused by an application error.

System Action: Message GAB333 appears onthe system console and diagnostic data isprovided. The message and the diagnostic dataare described in IBM Graphics Access

Method/System Product: Messages and Codes.

Programmer Response: Check for messagesidentifying the cause of the problem. Using themessage and other diagnostic information,correct the application program. IBM GraphicsAccess Method/System Product: Messages andCodes contains information on applicationrecovery from this problem.

0A7

Explanation: During ZNET, CANCELcommand processing, VTAM found that a userhad not specified a TPEND exit routine, orVTAM could not schedule a user's TPEND exitroutine.

System Action: The system abnormallyterminates the user's task.

0A8

Explanation: The error occurred duringexecution of a user's application program andwas detected by VTAM. The two low-order

bytes of register 15 contain a hexadecimalreason code:


2101 A VTAM validity check of the user's requestparameter list (RPL) failed because the RPL doesnot have the same protection key as theapplication program's TCB.

7001 The user's request parameter list (RPL) controlblock, or event control block (ECB) is invalid.

Register 15 and its contents can be found inRTM2WA, which is formatted when theworkareas are available, or SYS1.LOGREC(LOGDATA option of AMDPRDMP). TheGTF trace record, SVC trace (comprehensive),also displays the contents of register 15.

System Action: The task abnormally terminates.

Programmer Response: Verify that the RPL andECB pointers are correct and execute the jobstep again.

Problem Determination: Table I, items 1, 2, 3,5a, 13, 15, 16, 27, 29.

0A9

Explanation: Either a HALT NET,CANCELcommand was entered or an error occurredduring execution of a VTAM module. The twolow-order bytes of register 15 contain ahexadecimal reason code:


0000 A HALT NET,CANCEL command has beenprocessed.

10F1 The ACF/VTAM STAE retry routine issuedABEND 0A9 in order to give control to the userrecovery routine (STAB exit routine).

3100 There are not enough I/O buffers to satisfy aVTAM storage request.

3111 A VTAM module finished processing before itreleased a lock.

3141 A VTAM destination vector table (DVT) entry isinvalid for the defined attachment.

7002 A VTAM request for storage failed.


ABEND

0AA to 0AC

7003 A VTAM request to release storage failed becausethe storage had already been released.

7004 VTAM could not obtain a local memory lock.

7009 VTAM was unable to restore its registers after auser exit routine returned control to VTAM.

7071 A RELSTORE was issued for a previously freedbuffer.

7141 Control cannot be passed to the proper VTAMmodule. Either a VTAM destination vector tableentry is invalid for the defined attachment orVTAM storage has been altered.

System Action: The task that initiated theVTAM request abnormally terminates.


Problem Determination: Table I, items 1, 2, 4,5a, 13, 16, 18, 29.

0AA

Explanation: An ABEND condition occurredduring execution of VTAM. VTAM'sFunctional Recovery Routines (FRR's) wereunable to associate the failure with anyparticular TCB in the address space.

System Action: All the tasks in the addressspace are abnormally terminated.


Problem Determination: Table I, items 1, 2, 5a,13, 16, 27, 29.

0AB

Explanation: The error occurred whileTSO/VTAM time sharing was in operation anda VTIOC module was executing a VTAM macroinstruction. The two low-order bytes of register15 contain a hexadecimal reason code:


0101 The terminal input manager for IBM 3767 andIBM 3770 terminals (IKTTIMRT) encountered an

unrecoverable error while executing a VTAMmacro instruction that uses a request parameterlist (RPL).

0102 The terminal output manager for IBM 3767 andIBM 3770 terminals (IKTTOMRT) encounteredan unrecoverable error while executing a VTAMmacro instruction that uses an RPL.

0103 The terminal input manager for IBM 3270 system;network architecture (SNA) terminals (IKTIMIDSor IKTIMLU2) encountered an unrecoverableerror while executing a VTAM macro instructionthat uses an RPL.

0104 The terminal output manager for IBM 3270systems network architecture (SNA) terminals(IKTOMIDS or IKTOMLU2) encountered anunrecoverable error while executing a VTAMmacro instruction that uses an RPL.

0105 The VTIOC LOSTERM exit routine encounteredan error during execution of a SNA BIND orUNBIND command that used an RPL.

0201 The error occurred during initialization of aTSO/VTAM user address space. An applicationID problem was encountered while executing aVTAM OPEN macro instruction.

0202 The error occurred during execution of a VTAMOPEN macro instruction. The ERROR field ofthe ACB indicates the problem. The values thatcan be set in the ERROR field are listed in VTAMMacro Language Reference,.

0203 The error occurred during execution of a VTAMCLOSE macro instruction. The code in theERROR field of the ACB is X'42', indicating thatthe ACB has been closed but a VTAM error hasprevented the successful disconnection of one ormore TSO terminals.

System Action: If register 15 contains 0101,0102, 0103, or 0104, a record is written toSYS1.LOGREC. In all cases, the terminalsession in which the error occurred terminates.



0AC

Explanation: The terminal control address space(TCAS) was unable to continue its normalprocessing due to an error. The two low-order


0AD to 0AF

bytes of register 15 and TCAS work area(TWAR) field TWARSON contain the samehexadecimal reason code:


10 The TCAS main task was unable to attach theVTAM interface subtask.

14 The TCAS main task was unable to attach theuser interface subtask.

18 The TCAS main task was unable to attach theconsole communication subtask.

1C TCAS was unable to obtain storage for the TCAStable (TCAST) in the common service area (CSA).

20 The TCAS main task abnormally terminated andwas unable to recover.

30 The VTAM interface subtask abnormallyterminated and was unable to recover.

34 The user interface subtask abnormally terminatedand was unable to recover.

38 The console communication subtask abnormallyterminated and was unable to recover.

System Action: TCAS abnormally terminates.

Operator Response: Reply 'DUMP' to TCAStermination message IKT012D to obtain adump.


0AD

Explanation: The error occurred whileTSO/VTAM time sharing was in operation andVTIOC's queue manager was executing aGETCELL or FREECELL macro instruction.The two low-order bytes of register 15 contain ahexadecimal reason code:


0108 The cell address supplied to the FREECELLmacro instruction was invalid.

010C No cell pool existed for the FREECELL request.

0110 An invalid cell pool ID was specified for theFREECELL request.

020C No cell pool existed for the GETCELL request.

0210 An invalid cell pool ID was specified for theGETCELL request.

System Action: The queue manager abnormallyterminates, and the terminal session in which theerror occurred terminates.



0AE

Explanation: IOS support of system restartprocessing has found the I/O purge module(IGC0001F) waiting for the completion of an

I/O request.

System Action: The system abnormallyterminates all the tasks in the address space inwhich the I/O purge module was waiting; thenthe system terminates the address space.


Problem Determination: Table I, items 13, 16, 23and 29.

0AF

Explanation: The TSO Interactive DataTransmission Facility detected a system errorduring the processing of a TRANSMIT orRECEIVE command. Register 15 contains ahexadecimal reason code:


0003 A TRANSMIT or RECEIVE command issued anOPEN macro instruction for a TSO DataTransmission Facility NAMES data set, and theOPEN failed. The NAMES data set was correctlyallocated just prior to the OPEN attempt. Reasoncode 0003 is associated with message INMC003I.

007F The RECEIVE command attempted to allocate aspool file and JES returned an allocation errorcode. The RECEIVE command obtained thename of the spool file from JES via the processsysout subsystem interface. However, whenRECEIVE attempted to allocate the spool file, JESconsidered the name invalid. The name should beconsidered valid. This error should not occur ifRECEIVE and JES are working properly. Reasoncode 007F is associated with message INMR127I.


ABEND

0B0

0084 The RECEIVE command was issued with theINDATASET or INDSNAME keyword and thedata set specified with the keyword failed toOPEN. The data set was allocated successfully.Reason code 0084 is associated with messageINMR132I.

0085 The RECEIVE command attempted to OPEN afile for incoming network files from the JES spool,but the OPEN failed. The process sysoutsubsystem interface successfully selected a namefor the spool file and the dynamic allocation SVCsuccessfully allocated the spool file. Reason code0085 is associated with message INMR133I.

0086 The RECEIVE command attempted to deallocatea data set using SVC 99, and the deallocationfailed. The data set was a JES input file or wasspecified by an INDATASET or INDSNAMEkeyword. Reason code 0086 is associated withmessage INMR134I.

0089 The RECEIVE command encountered an errorwhile attempting to terminate the external writerinterface with JES. After all files have beenprocessed or after a nonrecoverable error, theRECEIVE command invokes the process sysoutsubsystem interface, specifying that this is the finalcall to the subsystem interface. The subsystemreturned a nonzero return code indicating anerror. Reason code 0089 is associated withmessage INMR137I.

0426 The TRANSMIT command was issued with theDATASET or DSNAME keyword and the dataset specified with the keyword failed to OPEN.TRANSMIT had successfully allocated the dataset. Reason code 0426 is associated with messageINMX062I.

042B The TRANSMIT command was issued with theDATASET or DSNAME keyword and theOBTAIN SVC was issued to get informationabout the data set. The OBTAIN SVC set areturn code other than 0 (successful termination),8 (data set not on volume), or 12 (VTOC I/Oerror). Reason code 042B is associated withmessage INMX067I.

043B The TRANSMIT command attempted to OPEN adata set previously written by the IEBCOPY utilityor the AMS REPRO command. The OPENfailed. The data set is a temporary data set theTRANSMIT command allocates to containintermediate data. Normally, the TRANSMITcommand reads, transmits, and deletes thetemporary data set. Reason code 043B isassociated with message INMX083I.

04B3 The TRANSMIT command attempted to allocatea SYSOUT data set, and the allocation failed.This reason code occurs for all SYSOUT data setallocation errors except an invalid node name,normally a user error. Reason code 04B3 isassociated with message INMX203I.

04B4 The TRANSMIT command attempted to OPEN aSYSOUT data set and the OPEN failed.TRANSMIT was going to use the data set as an

output file. TRANSMIT had successfullyallocated the data set. Reason code 04B4 isassociated with message INMX204I.

System Action: The system issues a systemdump.

Programmer Response: Print the dump data set.


Problem Determination: Table I, items 16, and29; save a hardcopy of the TSO session ifpossible.

0B0

Explanation: An uncorrectable error wasdetected by the SWA manager. Register 15contains a hexadecimal reason code:


04 The routine that called SWA manager requestedan invalid function.

08 The routine that called SWA manager passed aninvalid SVA (SWA virtual address). The SVAdoes not point to the beginning of a SWA prefixor the SWA prefix has been destroyed.

0C A SWA manager routine has attempted to read arecord not yet written into SWA.

10 A SWA manager routine has attempted to read orwrite a block that is not 176 bytes or to assign ablock with a specified length of 0 or a negativenumber.

14 The routine that called SWA manager hasspecified an invalid count field. For move mode,an invalid count is 0 for a READ, WRITE, orASSIGN function. An invalid count forWRITE/ASSIGN is 00.

18 The routine that called SWA manager by issuingthe QMNGRIO macro instruction specified bothor neither of the READ or WRITE options.

IC The routine that called SWA manager wasattempting to write into a SWA block for the firsttime and has either passed a nonexistent ID, orhas failed to pass an ID at all and the block doesnot have an embedded ID.

20 A SWA manager routine has attempted to write ablock using an invalid pointer to the block.




0B1 to 0B7

Problem Determination: Table I, items 3, 4, 16,29.

0B1

Explanation: The error occurred when a mastersubsystem module detected invalid parametersbeing passed to it from another module, whilestarting either the master scheduler or asubsystem.

System Action: The START process is ended.

Programmer Response: None


0B2

Explanation: The error occurred when theMaster Subsystem JCL-to-JCLs conversionroutine detected an invalid card in theMSTRJCL data set. The MSTRJCL could notbe converted, and the Master Scheduler was notstarted.

System Action: The Master Scheduler is notstarted. The IPL is terminated at this point.

Programmer Response: If the MSTRJCL dataset in the LINKLIB has been updated manuallysince the system was generated, check it for acard without a // in columns 1 and 2. Alsocheck to insure that the MSTRJCL is delimitedby a /* or a // (null) card.


0B3

Explanation: The error occurred when a callerof the Master Subsystem access methodattempted an invalid, or not serviceable, accessrequest via the RPL/ACB interface.

System Action: The task using the accessmethod is abnormally terminated.



0B4

Explanation: The Master Subsystem could notmake use of the SYS1.PROCLIB data setdefined by the IEFPDSI card in the MSTRJCL.This occurred for one of the following reasons:

• The Master Subsystem was unable to OPENthe PROCLIB data set.

• The blocksize of the openedSYS1.PROCLIB data set was not a multipleof 80.

System Action: Without an openSYS 1.PROCLIB DCB, the converter cannot beoperated; therefore, the subsystem requested isnot started.

Programmer Response: Check for a valid dataset name on the IEFPDSI card in theMSTRJCL data set. Also, check for a validblocksize either on the IEFPDSI card or in thedata set's format DSCB in the VTOC.


0B5

Explanation: The Master Subsystem was unableto ATTACH the converter.

System Action: ATTACH passed a nonzerocode back to the master subsystem in register15. The subsystem requested is not started.



0B7

Explanation: During processing of areconfiguration command, a reconfigurationmodule issued ABEND 0B7. Register 15contains diagnostic information in the format

X'xxxxmmrr'. The mm field identifies themodule that issued the ABEND. Most modulesplace a return code in the rr field. Somemodules provide additional information in the


0B7

ABEND

xxxx field. The possible values, in hexadecimal,of mm, rr, and xxxx are:

mm Module

00 IEEMPVST

Module IEEMPVST does not assign values to the rrfield or the xxxx field.

01 IEEVCPU

rr Explanation

01 IEEVCPU called IEEVMESS to request a messagebuffer, but IEEVMESS failed; xxxx is the returncode from IEEVMESS. The possible values forxxxx are:

04 - message insert is too long or the index into atable of message inserts is invalid.

08 - no reply received to WTOR.

0C - wrong number of message inserts specified.

10 - IEEVMESS could not establish ESTAE.

02 IEEVCPU called IEEVMESS for some reasonother than to request a message buffer, butIEEVMESS failed; xxxx is the return code fromIEEVMESS. The possible values for xxxx are:





03 Failure in first level ESTAE routine. No value isassigned for xxxx.

02 IEEVCPR

rr Explanation

02 IEEVCPR called IEEVMESS for some reasonother than to request a message buffer, butIEEVMESS failed; xxxx is the return code fromIEEVMESS. The possible values for xxxx are:





04 Unable to establish ESTAE; xxxx is the returncode from the ESTAE macro instruction. Thepossible values of xxxx are explained in OS/VS2MVS System Programming Library: Supervisor.

05 Unable to fix pages; xxxx is the return code fromthe PGFIX macro instruction. The possible valuesfor xxxx are explained in OS/VS2 SystemProgramming Library: Supervisor.

06 Unexpected MSSFCALL SVC return code; xxxx isthe unexpected return code. The possible valuesfor xxxx are explained in OS/VS2 SystemProgramming Library: MVS Diagnostic Techniques.

07 IEEVCPR has received an invalid input parameterlist. No value is assigned for xxxx.

08 Invalid channel set table entry; processor addresscannot be determined from the SCPINFO MSSFdata block. No value is assigned for xxxx.

0A Channel set is not loaded. No value is assignedfor xxxx.

0B Processor address does not appear as the homeprocessor address for any channel set in thechannel set table, and the system is not inuniprocessor mode. No value is assigned for xxxx.

0C Unexpected response received from an internalMSSFCALL command; xxxx is the value in theresponse field of the MSSFCALL data block. Thepossible values for xxxx are explained in OS/VS2System Programming Library: MVS DiagnosticTechniques.

03 IEEVSTOR

rr Explanation

01 IEEVSTOR called IEEVMESS for some reasonother than to request a message buffer, butIEEVMESS failed. No value is assigned for xxxx.

04 IEEVSTGP

rr Explanation

01 The VARY command processor was executing aVARY STOR ONLINE command. The MSSFvaried the storage physically online, but the systemwas unable to vary the storage logically online.The system then tried unsuccessfully to use theMSSF to vary the storage physically offline. Novalue is assigned to xxxx.

02 Unexpected return code from RSM. No value isassigned for xxxx.

03 Unexpected return code from the MSSFCALLinternal vary storage physical online command orvary storage physical offline command. No valueis assigned for xxxx.

04 Unexpected return code from MSSFCALL SVC.No value is assigned for xxxx.

05 IEEVSTEL

IEEVSTEL does not assign values for xxxx.


0B7

rr Explanation

01 Unexpected return code from MSSFCALL SVC.

02 Unexpected response code or reject code from theinternal MSSFCALL vary storage elementcommand.

03 Unexpected response code or reject code from theinternal MSSFCALL vary storage element infocommand.

06 IEEVSTFA

IEEVSTFA does not assign values to xxxx.

rr Explanation

01 Unexpected return code from RSM.

02 ESTAE failed.

07 IEEVSTGL

IEEVSTGL does not assign values for xxxx.

rr Explanation

01 Return code from the real storage reconfigurationroutine (IEAVRCF3) shows that storage rangespecified overlaps permanently resident storage.

02 Unknown return code from RSM moduleIEAVRCF3.

09 IEECLEAN

rr Explanation

02 IEECLEAN called IEEVMESS for some reasonother than to request a message buffer, butIEEVMESS failed; xxxx is the return code fromIEEVMESS. The possible values of xxxx are:


08 - no reply received from WTOR.

0C - wrong number of message insert specified.


0B IEEMPDM

IEEMPDM does not assign values to xxxx.

rr Explanation

01 The real storage reconfiguration routine(IEAVRCF3) tested page frame status and issueda nonzero return code.

02 An invalid message ID was passed to an internalmessage subroutine.

03 A MLWTO was cancelled by the operator.

0E IEEVMESS

IEEVMESS does not assign values for xxxx.

rr Explanation

01 Invalid address for message buffer passed toIEEVMESS.

10 IEEVPTH

rr Explanation

01 Unexpected return code from an internal IOSGENconditional vary path offline; xxxx is theunexpected return code. The possible values forxxxx are documented in module IECVGENA.

02 Unexpected return code from an internal IOSGENunconditional vary path offline; xxxx is theunexpected return code. The possible values ofxxxx are documented in module IECVGENA.

03 Unexpected return code from an internal IOSGENvary path online; xxxx is the unexpected returncode. The possible values of xxxx are documentedin module IECVGENA.

13 IEEVCPRL

rr Explanation

02 IEEVCPRL called IEEVMESS for some reasonother than to obtain storage for a message buffer,but IEEVMESS failed; xxxx is the return codefrom IEEVMESS. The possible values of xxxxare:





0D IEEVCPRL called IEEVDEV. IEEVDEV testedfor the last-path condition, but issued an invalidreturn code; xxxx is the invalid return code.

0E IEEVCPRL tried unsuccessfully to use theRISGNL macro instruction to activate the testchannel routine (IEEVTCH) on an MP system;xxxx is the return code from the RISGNL macroinstruction. The possible values of xxxx aredocumented in OS/VS2 System ProgrammingLibrary: Supervisor.

0F IEEVCPRL called IGFPBUCR to allocatemachine check logout buffers. IGFPBUCR issueda nonzero return code; xxxx is the return code.The possible value for xxxx is:

04 - invalid function code in register 0, or invalidprocessor address in register 1, or the processorhas no physical configuration control area


0B8 to 0BB

ABEND

(PCCA), or the size of the LOGREC buffer (LRB)is greater than a page.

10 IEEVCPRL called IEAVSPSA to obtainprocessor-related save areas. IEAVSPSA issued anonzero return code ., xxxx is the return code. Thepossible value for xxxx is:

04 - error in issuing a GETMAIN, a FREEMAIN,or a SETLOCK to obtain or free the SALLOClock.

FF IEEMPVST

Modlue IEEMPVST does not assign values to the rr orthe xxxx field.

System Action: The command frees all relatedresources and may be reinvoked. A softwareerror is written to the SYS1.LOGREC data set.

Operator Response: Retry the command.


0B8

Explanation: The error occurred when a starttask control routine detected one of thefollowing situations while processing a START,MOUNT, or LOGON command. Register 15contains a hexadecimal reason code:


04 The command code in the CSCB is invalid. Thecommand code was incorrect for a START,MOUNT, or LOGON command.

08 A TIOT manager failure occurred while trying toobtain storage for a START, MOUNT, orLOGON TIOT.

0C An OPEN failure occurred while trying to writethe internal JCL text for the START, MOUNT, orLOGON command into the STCINRDR orTSOINRDR internal reader data set.

10 The system address space initialization routinepassed an undefined return code to IEEPRWI2.

14 Module IEEPRWI2 requested a SYSEVENTTRANSWAP (via the POST macro instruction)and received a nonzero completion code in theECB (event control block). This indicates that theaddress space cannot be made nonswappable.

System Action: If the command is START orMOUNT, message IEE824I is issued; theSTART, MOUNT, or LOGON task isterminated.


Problem Determination: Table I, items 2, 7c, 16,18, 29.

0B9

Explanation: The error occurred when thestarted task control received an invalid returncode from the master subsystem when therequest was issued to determine if a subsystemwas being started.

System Action: If the command is START orMOUNT, message IEE824I is issued; theSTART, MOUNT, or LOGON task isterminated.



0BA

Explanation: The error occurred when thestarted task control or the initiator received aninvalid return code from the subsystem interfacewhen a subsystem request was issued.

System Action: In started task control, if thecommand is START or MOUNT, messageIEE824I is issued; the START, MOUNT, orLOGON task is terminated. In the initiator,message IEF187I is issued, and the job isterminated.



0BB

Explanation: The initiator was unable toATTACH the job step task, started task, orLOGON task.

System Action: The initiator is abnormallyterminated causing failure of the job, START orLOGON. The return code from ATTACH isfound in register 15.



0BD to 0Cx


0BD

Explanation: The parameter list for master traceprocessing is incorrect; either the parameter listitself could not be accessed, or the data pointedto by the parameter list could not be accessed.

System Action: Master trace processingterminates. The status of the master tracingfacility does not change.

Operator Response: Save any accompanyingdump, and notify the system programmer.



0BE

Explanation: An error occurred while processinga FREEMAIN macro instruction during mastertrace create/deactivate processing. Thiscompletion code is accompanied by messageIEE480I or IEE481I and by message IEE839I.

System Action: Master trace create/deactivateprocessing terminates. The status of the mastertracing facility is described by message IEE839I.




0BF

Explanation: The master tracing facility failedduring a recovery attempt. This completioncode is accompanied by message IEE480I orIEE481I.

System Action: The status of master tracing isdescribed in message IEE480I or IEE481I.




0Cx

Explanation: A program interruption occurredand no routine had been specified to handle thistype of interruption. For these errors,instruction execution can be terminated in oneof several ways. Refer to Principles of Operationfor the instruction involved to determine howthe instruction stops execution for a particularerror.

The last digit of this completion code is ahexadecimal number that indicates the cause ofthe program interruption:

x Program Interruption Cause

1 Operation exception: an operation code is not assignedor the assigned operation is not available on theparticular model.

(The operation is suppressed. The instruction-lengthcode is 1, 2, or 3.)

2 Privileged-operation exception: a privileged operation isencountered in the problem state.

(The operation is suppressed. The instruction-lengthcode is 1 or 2.)

3 Execute exception: the subject instruction of EXECUTEis another EXECUTE.

(The operation is suppressed. The instruction-lengthcode is 2.)

4 A virtual address could not be translated into a realaddress because of one of the following:

• The key of an instruction halfword or an operand instorage does not match the protection key in thePSW (interrupt code 4).

• The virtual segment or page was never allocated(interrupt code 10 or 11).

• The page was paged out and the routine requestingthe page was disabled for I/O interrupts (interruptcode 11).

(The operation is suppressed on a store violation, exceptin the case of STORE MULTIPLE, READ DIRECT,TEST AND SET, and variable-length operations, whichare terminated. Except for EXECUTE, which issuppressed, the operation is terminated on a fetchviolation. The instruction-length code is 0, 2, or 3.)


ABEND

0Cx

5 Addressing exception: an address specifies any part ofdata, an instruction, or a control word outside theavailable real storage for the particular installation.Issued by program FLIH the instruction-length is 1, 2 or3.

6 Specification exception. One of the following occurred:

• A data, instruction, or control-word address doesnot specify an integral boundary for the unit ofinformation.

• The R field of an instruction specifies an oddregister address for a pair of general registers thatcontains a 64-bit operand.

• A floating-point register address other than 0, 2, 4,or 6 is specified.

• The multiplier or divisor in decimal arithmeticexceeds 15 digits and sign.

• The first operand field is shorter than or equal tothe second operand field in decimal multiplicationor division.

• The block address specified in SET STORAGEKEY or INSERT STORAGE KEY has the fourlow-order bits not all zero.

• A PSW with a nonzero protection key isencountered when protection is not installed.

(The operation is suppressed. The instruction-lengthcode is 1, 2, or 3.)

7 Data exception: one of the following occurred:

• The sign or digit codes of operands in decimalarithmetic or editing operations or in CONVERTTO BINARY are incorrect.

• Fields in decimal arithmetic overlap incorrectly.

• The decimal multiplicand has too many high-ordersignificant digits.

(The operation is terminated or suppressed. Theinstruction-length code is 2 or 3.)

8 Fixed-point-overflow exception: a high-order carryoccurs or high-order significant bits are lost in fixed-pointadd, subtract, shift, or sign-control operations.

(The operation is completed by ignoring the informationplaced outside the register. The interruption may bemasked by PSW bit 36. The instruction-length code is 1or 2.)

9 Fixed-point-divide exception: a quotient exceeds theregister size in fixed-point division, including division byzero, or the result of CONVERT TO BINARY exceeds31 bits.

(Division is suppressed. Conversion is completed byignoring the information placed outside the register. Theinstruction-length code is 1 or 2.)

A Decimal-overflow exception: the destination field is toosmall to contain the result field in a decimal operation.

(The operation is completed by ignoring the overflowinformation. The interruption may be masked by PSWbit 37. Issued by program FLIH the instruction-length is2 or 3.)

B Decimal-divide exception: a quotient exceeds thespecified data field size.

(The operation is suppressed. Issued by program FLIHthe instruction-length code is 2 or 3.)

C Exponent-overflow exception: the result characteristic infloating-point addition, subtraction, multiplication, ordivision exceeds 127 and the result fraction is not zero.

(The operation is completed. The fraction is normalized,and the sign and fraction of the result remain correct.The result characteristic is made 128 less than the correctcharacteristic. The instruction-length code is 1 or 2.)

D Exponent-underflow exception: the result characteristic infloating-point addition, subtraction, multiplication,halving, or division is less than zero and the resultfraction is not zero.

(The operation is completed. The setting of theexponent-underflow mask (PSW bit 38) affects the resultsof the operation. When the mask bit is zero, the sign,characteristic, and fraction are set to zero, making theresult a true zero. When the mask bit is one, the fractionis normalized, the characteristic is made 128 larger thanthe correct characteristic, and the sign and fractionremain correct. The instruction-length code is 1 or 2.)

E Significance exception: the result of a floating-pointaddition or subtraction has an all-zero fraction.

(The operation is completed. The interruption may bemasked by PSW bit 39. The manner in which theoperation is completed is determined by the mask bit.The instruction-length code is 1 or 2.)

F Floating-point-divide exception: division by afloating-point number with zero fraction is attempted.

(The operation is suppressed. The instruction-lengthcode is 1 or 2.)

System Action: The task is terminated if norecovery routine was specified to handle theinterrupt. Refer to the Principles of Operationfor the hardware action for the instructioninvolved.

Programmer Response: Determine whether theproblem program or control program was inerror. If the problem program contained anerror, correct it, and execute the job step again.

Problem Determination: Table I, items 5a, 16,23, 29.


0D2 to 0D6

0D2

Explanation: A program check, interruptioncode X'12' (translation specification error),occurred. Invalid data exists in control registerzero or one, or in a segment or page table.Either a hardware error exists, or a programrunning in key zero has caused data damage.

System Action: The system tries to terminate thetask with this error. If the task cannot beterminated because of translation problems, thesystem tries to terminate the address space. Ifthe address space cannot be terminated, thesystem enters a disabled wait state (codeX'040').

Programmer Response: Correct the error, andrerun the program.


0D3

Explanation: A program check, interruptioncode X'13' (special operation error), occurred.A privileged program issued a set system mask.


Programmer Response: Remove the set systemmask instruction. This instruction is not validin MVS.


0D4

Explanation: A program issued a PC, PT, orSSAR instruction, but an address space number(ASN) translation specification exceptionoccurred. (The address space number translationexception is also known as an address space ID(ASID) translation exception.) The programinterruption code is X'17'. Either the addressspace first table (AFT) or the address spacesecond table (AST) contains invalid data.

System Action: The program that issued the PC,PT, or SSAR instruction is abnormallyterminated.

Programmer Response: Probable system error.If necessary, contact IBM for programmingsupport.

Problem Determination: Table I, items 5, 11, 13,15 16, 18, 29, and 33.

0D5

Explanation: A program issued a PC, PT, orSSAR instruction, and an address space firsttable index (AFX) translation exception(program interruption code X'20') or an addressspace second table index (ASX) translationexception (program interruption code X'21')occurred. The values in the address space firsttable (AFT) or the address space second table(AST) generate an invalid ASID. Either theaddress space does not exist or it was swappedout.

System Action: The system attempts to correctany errors in the AFT. The program that issuedthe PC, PT or SSAR instruction abnormallyterminates.

Programmer Response: Determine why theASID is invalid. Correct the error, andresubmit the program.

Problem Determination: Table I, items 5, 11, 13,15, 16, 29 and 33.

0D6

Explanation: The program issued a PCinstruction with an invalid PC number. One ofthe following occurred:

• A linkage index (LX) translation exception(program interruption code X'22') or anentry table (EX) translation exception(program interruption code X'23') hasoccurred.

• The entry table field that the PC numberidentifies is not defined by the address spacethat owns the entry table. Register 14contains the next sequential instruction afterthe PC instruction.

System Action: The program that issued the PCinstruction abnormally terminates.


ABEND

0D7 to 0E1

Programmer Response: Determine why the PCnumber is invalid. Correct the error, andresubmit the program.


0D7

Explanation: One of the following occurred:

• A program issued the PT instruction, but aprimary authority exception occurred. Theprimary address space is not authorized toissue a PT instruction to the target addressspace. Either the authorization index (AX)is greater than the number of elements inthe target address space's authorizationtable (AT) or the P bit is off in the targetaddress space's AT. The programinterruption code is X'24'.

• A program issued the SSAR instruction, buta secondary authority exception occurred.The primary address space is not authorizedto issue an SSAR instruction to the targetaddress space. Either the authorizationindex (AX) is greater than the number ofelements in the target address space'sauthorization table (AT) or the S bit is offin the target address space's AT. Theprogram interruption code is X'25'.

System Action: The program that issued the PTor the SSAR instruction abnormally terminates.

Programmer Response: Correct the error, andresubmit the program.


0D8

Explanation: A space switch exception occurred.A program issued a PC or PT instruction, butthe cross memory resource ownership task in thetarget address space has terminated. The targetaddress space is not the home address space ofthe program that issued the PC or PTinstruction. Program interruption code X'1C' isassociated with the error.

System Action: The program that issued the PCor PT instruction abnormally terminates.

Programmer Response: Correct the error, andresubmit the program.


0D9

Explanation: A program check was detected. Aninterruption code of X'26', a page fault assistexception, has occurred. Either a hardwareerror occurred or a program running in key zerocaused data damage.


Programmer Response: System error. Rerun thejob.


0DA

Explanation: A program issued the PCinstruction, and a PC translation specificationexception occurred. The program interruptioncode is X'1F'. Either the linkage table (LT) orthe entry tables (ETs) contain incorrect data.

System Action: The program that issued the PCinstruction is abnormally terminated.

Programmer Response: Probable system error.Resubmit the program. If the error continues tooccur, contact IBM for programming support.

Problem Determination: Table I, items 5, 11, 13,15, 16, 18, 29, and 33.

0E1

Explanation: An error was encountered whileprocessing the first EXCP against a VIO dataset. Register 15 contains a hexadecimal reasoncode:


05B The LGCB (IDAVBPL) chain is invalid. TheASIDs in the LGCB and the ASCB do not match.


0E2 to 0E3

lxx Unable to fix or free the page containing theparameter list (VCB) for RSM.

xx Explanation

04 Operation abnormally terminated. Operationincomplete because of invalid address invirtual subarea list; ECB posted complete.

10 Operation abnormally terminated. Virtualsubarea list entry or ECB address invalid; noECB posted.

2xx RSM was unable to 'assign null' the virtual trackbuffer or the DSPCT map.

xx Explanation

04 Assign (move-in) error. The page identifiedby the VCBVSA field is not available.

08 Write (move-out) error. The page identifiedby the VCBVSA field is fixed in real storageand cannot be written to the data set inauxiliary storage.

0C Invalid request. Not a move-out or an assignrequest.

10 The page identified by the VCBVSA field willnot be written to the data set because it wasnot brought into real storage by the priorread request or because data in the page hasnot been modified.

20 The page identified by the VCBVSA fieldbelongs to an LPID other than the LPID inthe VCBLPID field.

40 Invalid virtual storage address. AGETMAIN macro instruction was not issuedfor the page identified by the VCBVSA field.

80 Assign error. The page identified by theVCBVSA field was previously read and wasnot disconnected by a move-out ormove-out-null request before the current read(assign) operation.

3xx ASM was unable to ASSIGN a logical group forthis VIO data set. Either ASM was unable toobtain storage to process the request or ASM ranout of paging slots to create VIO data sets. If theconsole sheet from the primary console showswarning messages that indicate a shortage ofpaging space or heavy VIO activity, then it may bepossible to re-IPL after increasing the constantILRSLOTV as described in OS/VS2 SystemProgramming Library: Initialization and TuningGuide.

xx Explanation

1C Not enough slots. Maximum number (1600)of LGNs exceeded. Unable to obtain storageto process request.

System Action: The input parm list (IDAVOP1),the DSPCT header (IDAVBPH) and SWA aredumped to the SYS 1.DUMP data set. ASCBand the LGCB (IDAVBPL) chain are alsodumped if the reason code was X'05B'.


Problem Determination: Table I, items 1, 2, 4,5a, 7d, 9b with MEMBER=IDDWI, 18, 29, 33.

0E2

Explanation: The error was detected whileprocessing the first EXCP for the VIO data setafter a restart. Register 15 contains ahexadecimal reason code:


05B The LGCB (IDAVBPL) chain is invalid. TheASIDs in the LGCB and the ASCB do not match.

lxx Unable to fix or free the page containing theparameter list (VCB) for RSM. Refer to code 0E1for an explanation of xx.

2xx RSM was unable to 'assign null' the virtual trackbuffer or the DSPCT map. Refer to code 0E1 foran explanation of xx.

System Action: The input parm list (IDAVOP1),DSPCT header (IDAVBPH) and SWA aredumped to the SYS1.DUMP data set. If thereason code is X'05B', ASCB and the LGCB(IDAVBPL) are also dumped.


Problem Determination: Table I, items 1, 4, 5a,7d, 9b with MEMBER=IDDWI, 18, 29, 33.

0E3

Explanation: The error occurred whileprocessing a VIO data set. Register 15 containsa hexadecimal reason code:


004 An invalid RBA was passed to VBP. Probablecauses of error code are (1) DEB with extentdescriptions that do not fall within the allocated


0E4 to 0E7

extents as described in the virtual data set controlblock (VDSCB) or (2) EXCP was issued to readthe format-1 DSCB on the volume.


2xx RSM was unable to ASSIGN or MOVE OUTpages in the virtual track buffer. Refer to code 0E1for an explanation of xx.

System Action: The following are dumped tothe SYS 1.DUMP data set:

• Input parameter list (IDABUFC)• DSPCT header (IDAVBPH)• SWA• LSQA• The region (in some cases)



0E4

Explanation: The error occurred while trying toscratch a VIO data set. Register 15 contains ahexadecimal reason code:


008 The ASIDs in the LGCB and ASCB do notmatch, indicating an error in the LGCB chain.

3xx ASM could not RELEASE the logical group forthis data set.

xx Explanation

04 Invalid LGN.

1C Unable to obtain storage to process request.

20 Invalid operation code is supplied in theauxiliary storage manager control area(ACA).

28 Invalid identifier type when an LGN wasgiven, but 'S' type symbol is required.

System Action: The ASCB and LGCB chainDSPCT header, and SWA are dumped onSYS1.DUMP data set.



0E5

Explanation: Unable to disconnect the virtualtrack buffer from the VIO data set. Register 15contains a hexadecimal reason code:



2xx RSM was unable to MOVE OUT pages in thevirtual track buffer. Refer to code 0E1 for anexplanation of xx.

System Action: The DSPCT header and SWAare dumped to the SYS1.DUMP data set.



0E6

Explanation: Unable to process against a dataset that has already been scratched.

System Action: The VDSCB (IDDVDSCB) isdumped to the SYS 1.DUMP data set.

Programmer Response: Do not access ascratched data set.


0E7

Explanation: The error occurred whilejournaling the DSPCT header (IDAVBPH) atstep termination or at checkpoint. Register 15contains a hexadecimal reason code:


008 Scheduler module IEFXB500 returned anunsuccessful completion code for a request towrite to the job journal.

ABEND


0E8 to 0F3

05B The LGCB (IDAVBPL) chain is invalid. TheASIDs of the LGCB (in the LGCB chain) and theASCB did not match.

lxx Unable to fix or free the page containing theparameter list (VCB) for RSM. Refer to code 0E1for explanation of xx.

2xx RSM was unable to ASSIGN or MOVE OUTpages in the virtual track buffer. Refer to code 0E1for explanation of xx.

3xx ASM was unable to SAVE the logical group forthis data set.

xx Explanation

04 Invalid LGN.

14 Unrecoverable error occurred while writingto SYS1.STGINDEX.

1C Unable to obtain storage to process request.

20 Invalid operation code is supplied in theauxiliary storage manager control area(ACA).

2C Indeterminate error has occurred.

408 Unable to obtain the local lock. The lockword iddoes not match the caller's id.

System Action: The DSPCT header(IDAVBPH) and SWA are dumped on theSYS1.DUMP data set.



0E8

Explanation: The error occurred whileprocessing the VIO data sets for the job after anabnormal system or job step task failure.Register 15 contains a hexadecimal reason code:


004 Unable to free the LGCB.

051 The ASID in the LGCB chain and the ASCB donot match.

3xx ASM was unable to release the logical group forthis data set. See code 0E4 for an explanation ofxx.

408 Unable to obtain the local lock. The lockword iddoes not match the caller's id.

System Action: The input parm list (RMPL),the ASCB and the LGCB (IDAVBPL) chain aredumped to the SYS1.DUMP data set.

Programmer Response: System Error. Rerun thejob.


0F0

Explanation: An error occurred while processinga machine check interruption with the machinecheck handler's FRR stack active. In anattempt to recover the system, the controlprogram terminated the task that wasinterrupted.



0F2

Explanation: The error occurred during I/Ointerrupt processing. An I/O recovery routinefailed.


Problem Determination: Table I, items 1, 5a, 7d,13, 16, 18, 29, 31, 32.

0F3

Explanation: A machine-check interruptionoccurred. After a machine check, the systemusually terminates one or more programs,issuing system completion code 0F3.

System Action: The system terminates thecurrent task.

Programmer Response: Probable hardwareerror. If the data on external storage devices isstill valid, execute the job step again.

Problem Determination: Table I, items 2, 18, 30. .


0F6 to 0FB

ABEND

0F6

Explanation: The error occurred during theprocessing of the SETEVENT service, acting onbehalf of GTF. Register 15 contains ahexadecimal reason code:


00 The caller of the SETEVENT service was notauthorized via APF, protect key 0-7, or supervisorstate.

04 The parameter list passed to SETEVENT wasinvalid.

08 An invalid monitor call queue element (MCQE)address was passed to SETEVENT.

0C The monitor call queue element (MCQE) at theaddress passed to SETEVENT is invalid for thefunction requested.

System Action: The caller of SETEVENT isterminated.

Programmer Response: Make sure that the callerof SETEVENT is an authorized program;protect key 0-7, supervisor state, or authorizedvia APF. If it does not, correct this condition,and restart the failing component.

Problem Determination: Table I, items 1, 2, 4,5a, 7d, 13, 16, 29.

0F8

Explanation: The issuer of an SVC was not inTCB mode, held a lock, was disabled, was incross memory mode, or had an enabledunlocked task mode FRR established (that is, -an FRR for which EUT=YES was specified onthe SETFRR macro instruction.)

System Action: The system abnormallyterminates the program that issued the SVC.

Programmer Response: Probable user error in anSVC routine or SRB routine attempting to issuean SVC. See the SVC error entry in the tracetable. Correct the error, and rerun the program.

Problem Determination: Table I, items 29 and31.

0F9

Explanation: The error occurred whileattempting to acquire or release an SVRB.

Programmer Response: Probable user error, butnot necessarily in the program that wasabnormally terminated.

If the return code in register 15 is 0, the LSQAhas been exhausted and the SVRB space is notavailable to honor an SVC request in theaddress space. This may be caused by a loop itthe program issuing the SVC.

If the return code in register 15 is 4, an SVRB ibeing freed that cannot be identified asbelonging to the SVRB pool.

Correct the error, and resubmit the job.


0FA

Explanation: Because both LSQA and SQAhave been exhausted, SVRB space is notavailable to honor an SVC request in theaddress space during ABEND processing.

Programmer Response: Probable system error.None.


0FB

Explanation: A translation exception occurred.The system detected invalid contents in controlregister 0.

Programmer Response: If control register 0 isbeing manipulated, check the contents beingplaced in this register. If control register 0 isnot being manipulated, then it is a systemproblem.



0FC to 104

0FC

Explanation: A translation error occurred whilethe job was referencing data in an address spaceother than its home address space. That addressspace either has invalid data in its DAT(dynamic address translation) tables or has anincorrect segment table origin address.

System Action: The job is abnormallyterminated.

Programmer Response: Probable system error.Contact your IBM representative forprogramming support.


0FD

Explanation: The error occurred when a type 6SVC requested the SVC first level interrupthandler to schedule a cross memory SRB.

Programmer Response: Probable user error inthe SVC routine. The type 6 SVC routineissued the T6EXIT macro with a schedule SRBrequest, but the SRBASCB address is not thesame as the current memory address. Correctthe error, and resubmit the job.


0FE

Explanation: An error was detected while RMFwas sampling data about the state of the system.

System Action: All RMF measurementcollection is terminated. Reinstatement of RMFcan be attempted, and, if successful, RMFcontinues under the control of the originaloptions. If reinstatement fails, RMF isterminated.


Problem Determination: Table I, items 5a, 16,18, and 29.

101

Explanation: The error occurred duringexecution of a WAIT macro instruction.

The problem program specified more eventsthan there were event control blocks (ECBs).

Programmer Response: Change the number ofevents specified so that it is less than or equal tothe number of event control blocks. If thespecification was correct, make sure it was notincorrectly modified. Correct the error, andexecute the job step again.


102

Explanation: The error occurred duringexecution of a POST macro instruction.

The control program found an invalid eventcontrol block (ECB) address.

Programmer Response: Make sure that theaddress specified for the ECB is a valid virtualstorage address, that it was not incorrectlymodified, and that it is aligned on a fullwordboundary. Make sure that the program issuingthe POST macro instruction has a storageprotection key that allows it to update the ECB.Correct the error, and rerun the job step.


104

Explanation: An error occurred during theexecution of a GETMAIN macro instruction foran authorized program. The GETMAINrequested virtual storage that requires more realstorage than is available.

System Action: The system abnormallyterminates the task.

Programmer Response: Make sure that theprogram issuing the GETMAIN macroinstruction is not requesting unnecessarily largeamounts of real storage. If this code occurs


ABEND

106 to 10B

frequently, installation action is required toincrease the available real storage on the system.


106

Explanation: During execution of a LINK,LOAD, ATTACH, or XCTL macro instruction,the control program detected an error whenattempting to fetch the requested program intovirtual storage. Register 15 contains ahexadecimal reason code:


0B An error occurred during FETCH processing or inone of the routines that gets control as a result ofFETCH processing.

0C Not enough storage was available for FETCH toexecute a GETMAIN for the load module orcontrol blocks.

0D The control program found an invalid record typein the load module.

0E The control program found an invalid address inthe load module.

0F One of the following occurred:

• An uncorrectable input/output error.

• An error in the load module; this errorcaused the channel program to fail.

• A data set in SYS1.LNKLST expanded intoanother extent. The system updates the dataextent block (DEB) extents only when a dataset is opened; data sets in SYS1.LNKLST areopened only by NIP during IPL.

At the time of abnormal termination, the ECB canbe found by adding X'400' to the address of theFETCH work area located at offset X'74' in thecaller's SVRB. The address of the failing IOSB islocated at offset X'528' in the FETCH work area.

Note: The storage area related to the IOB ECBmay be free unless the dump is takenimmediately after the ABEND macroinstruction is issued.

Programmer Response: If register 15 containseither a X'0D' or X'0E', it is a probable usererror. Ensure that the load request in theproblem program was specified correctly andwas not incorrectly modified. After makingcorrections, execute the job step again.

If register 15 contains X'0F' and you find that aLNKLST data set had expanded into extents,re-IPL the system.

Problem Determination: Table I, items 1, 5a,10c, 29. Table II, format 1: trace option -TRACE=SYS. If register 15 contains a X'0F',resubmit the job, and see Table I, item 30, andTable II, format 1: trace option - TRACE=JO.

10A

Explanation: The error occurred during theexecution of an R-form GETMAIN macroinstruction for an authorized program. Theprogram requested virtual storage that requiredmore real storage than is available.


Programmer Response: Make sure that thecalling program is not asking for unnecessarilylarge amounts of real storage. If this codeoccurs frequently, installation action is requiredto increase the available real storage on thesystem.


10B

Explanation: The error occurred in the TIMEservice routine. An error was found in the inputparameters.

Programmer Response: Check the parametersthat were used on the TIME macro instruction.If MIC or STCK was specified, the areaspecified by address must have the caller'sstorage protect key.


10D to 117

10D

Explanation: This completion code is foundonly in the jobstep tasks. It occurs when ajobstep task abnormally terminates and has ajobstep task as a subtask that is in STEP MUSTCOMPLETE status.

Note: The original ABEND code is found inthe mother task that abnormally terminated.

System Action: The job step subtask isabnormally terminated.

Programmer Response: Rerun the job with theoriginal ABEND corrected.

Problem Determination: Table I, items 1, 5a, 16,19, 23, 29.

10E

Explanation: The error occurred duringexecution of the SPIE macro instruction. ThePICA address is invalid.

Programmer Response: Correct the PICAaddress specified, ensuring that it is a validvirtual storage address assigned to the jobstep.Execute the job step again.


112

Explanation: Invalid input was passed to SVC18 by the BLDL or FIND macro instruction.This system completion code is accompanied bymessage IEC908I. Message IEC908I identifiesthe terminated task and explains the return codein register 15.

System Action: For return codes 13 and 14, theDCB was written to the GTF trace data set.

Programmer Response: Correct the BLDL orFIND macro instruction. For reason codes 03,13, 04, and 14, make sure that the DCB is notbeing overlaid, in particular, the fieldsDCBEBAD and DCBPOINT. Recompile theprogram, and execute the job step again.

Problem Determination: Table I, items 1, 3, 5b,15, 16, 29. Table II, format 3.

113

Explanation: The error occurred duringexecution of an OPEN macro instruction or anOPEN macro instruction with a TYPE=Joperand. This system completion code isaccompanied by message IEC142I. MessageIEC142I identifies the terminated task andexplains the return code in register 15.



115

Explanation: The error occurred during theexecution of SVC 21 (STOW). The DCB didnot point to a valid DEB, or the DEB did notpoint back to the DCB.

System Action: An unsuccessful attempt wasmade to invoke the STOW task recoveryroutine.

Programmer Response: Verify that register 1contained the correct DCB address prior toissuing SVC 21, and that the DCB has not beenoverlaid since it was opened.


117

Explanation: The error occurred duringexecution of a BSAM CLOSE macro instructionwith a TYPE=T operand. This systemcompletion code is accompanied by messageIEC218I. Message IEC218I identifies the

terminated task and explains the return code inregister 15.




118 to 128

ABEND

118

Explanation: Invalid parameters were passed toDEVTYPE (SVC 24). This system completioncode is accompanied by message IEC912I.Message IEC912I identifies the terminated taskand explains the return code found in register15.

Programmer Response: Correct the DEVTYPEmacro instruction, recompile the program, andrerun the job step.


119

Explanation: Invalid input was passed to SVC25. This system completion code isaccompanied by message IEC914I. MessageIEC914I identifies the terminated task andexplains the return code in register 15.

System Action: For return codes 12 and 13, theDCB is written to the GTF trace data set. Forreturn code 14, both the DCB and IOB arewritten.

Programmer Response: Make sure that yourprogram does not overlay the DCB and IOBfields described by the return code. Correct theerror, and rerun the job step.


11A

Explanation: A protection check occurred whenthe system tried to store into a user-supplied

OS/VS CAMLST work area.

System Action: SVC 26 received the protectioncheck because the protect key of the suppliedwork area did not match the user's protect key.

Programmer Response: Correct the pointer inthe OS/VS LOCATE parameter list to theLOCATE work area, and execute the job stepagain.


122

Explanation: The operator canceled the job andrequested a dump. The job may have beencanceled because it appeared to be in a loop orbecause it was waiting for resources that werenot immediately available (for example, directaccess space or devices). Perhaps the job wascanceled to correct a system interlock condition(for example, two tasks enqueued on a resourcewithout an intervening dequeue), or the job mayhave violated a procedure established for yourinstallation. An operator might cancel a job formany reasons. Your program may contain noerrors.

System Action: The system terminates the joband produces a dump to the data set describedby the SYSABEND, SYSMDUMP, orSYSUDUMP DD statement in the canceled jobstep.

Programmer Response: Find out why theoperator canceled your job. Make anynecessary corrections, and resubmit the job.

Problem Determination: Table I, items 1, 2, 5aor b, 16, 23, 29.

128

Explanation: The error was detected duringexecution of an EXTRACT macro instruction.

The address of the list in which the controlprogram was to store the requester fields wasinvalid. The beginning address for the list wasnot on a fullword boundary, or the list did notbegin and end within the storage assigned to thejob step. (The beginning address of the list isspecified in the first operand of the macroinstruction; the length of the list is determinedby the number of fields requested.)

Programmer Response: Determine if the firstoperand of the macro instruction was specifiedcorrectly or if program errors had incorrectlymodified the EXTRACT macro expansion.After making corrections, recompile and executethe job step again.



12A to 12F

12A

Explanation: The error was detected duringexecution of an ATTACH macro instruction.

In a GSPV or GSPL operand, the macroinstruction specified that a subpool was to begiven to the subtask being created. Theattaching task owned the subpool, but hadpreviously shared it with other subtasks throughSHSPV and/or SHSPL operands. A task is notpermitted to give an owned subpool to asubtask if it has shared the subpool with one ormore other subtasks.

Programmer Response: Change the ATTACHmacro instruction to specify the subpool in anSHSPV or SHSPL operand. Recompile theprogram, and execute the job step again.


12C

Explanation: The error was detected duringexecution of a CHAP macro instruction.

The address of the task control block (TCB) forthe subtask whose priority was to be changedwas invalid. This address is contained in thefullword addressed by the second operand of aCHAP macro instruction. The address wasinvalid for one of the following reasons:

• It was not a valid TCB address.

• The valid task control block at the addresswas not associated with a subtask of thetask issuing the macro instruction.

• It was not a multiple of 4.

• The valid task has terminated.

Programmer Response: Change the addressspecification, and ensure that it and the taskcontrol block were not incorrectly modified bythe problem program. Recompile the program,and execute the job step again.


12D

Explanation: The error occurred duringexecution of an overlay program.

The overlay supervisor found that words 3 and4 of the segment table were incorrect.

Programmer Response: Check for programerrors that caused the segment table to beincorrectly modified. After making corrections,assemble, link edit, and execute the programagain.

Problem Determination: Table I, items 1, 5a, 9.29.

12E

Explanation: The error occurred in theTTIMER service routine. An error was foundin the input parameters.

Programmer Response: Check the parametersspecified on the TTIMER macro instruction. IfMIC is specified, the area specified by addressmust have the caller's storage protect key.

12F

Explanation: An error was found in the inputparameters for the STIMER service routine.Register 15 contains a hexadecimal reason code:


04 The GMT or TOD parameter was specified for aTASK type STIMER request.

0C The value specified for the GMT or TODparameter was greater than 2400.

The STIMER routine produces a tailored dumpthat provides the following information:

• The control blocks associated with the taskthat issued the STIMER request

• The register contents for the task that issuedthe STIMER request

• The virtual subpools that contain theparameter list passed to STIMER


ABEND

130 to 137

Programmer Response: Check the parametersspecified on the STIMER macro instruction.Consult OS/ VS2 MVS Supervisor Services andMacro Instructions for format and restrictions.

130

Explanation: The error occurred duringexecution of a DEQ macro instruction.

The DEQ macro instruction specified a resourcenot previously specified by an ENQ macroinstruction under the same task. That is, theprogram had not requested control of a resourceit was attempting to release. the DEQ macroinstruction did not contain a RET=HAVEoperand.

Programmer Response: Check the DEQ macroinstruction for incorrect qname or rnameoperands, or specify RET=HAVE in the DEQmacro instruction, or add an ENQ macroinstruction before the DEQ macro instruction.Recompile, and execute the program again.


133

Explanation: An unauthorized caller hasinvoked SVC Dump via the SDUMP macro. Ifthe caller requested linkage by SVC 51, thecaller was not authorized by APF or was notrunning under a control program key. If thecaller tried to do a branch entry to SDUMP, thecaller did not meet these criteria:

1. The caller must be in key-0, supervisorstate.

2. One of the following must be true:

• The caller is in SRB mode.

• The caller owns a lock.

• The caller is disabled and has aPSASUPER bit set on.

• The caller is in enabled unlocked taskmode (EUT mode). That is, EUT=YES

was specified on the SETFRR macroinstruction.

Generally, those modules that cannot issueSVCs can do a branch entry to SDUMP.

System Action: The caller is abnormallyterminated. If a recovery routine is available, itis given control.

Programmer Response: Authorize the callingroutine of SVC Dump. If the calling routinecannot be authorized, use the SNAP dumpfunction. If the branch entry is being invalidlyused, correct the error or use the SVC entry.

Problem Determination: Table I, items 5ab, 7c,13, 19, 27, 29.

135

Explanation: An error occurred during theprocessing associated with SVC 53, whichobtains and releases exclusive control of aresource associated with a BDAM data set. Thetask recovery routine for this SVC determinedthat all user control blocks required as input tothe SVC were in the user's region and key,hence the error could not be ascribed to anyuser control block.

System Action: Message IEC903I is issued.



137

Explanation: The error occurred at anend-of-volume on a tape. This systemcompletion code is accompanied by messageIEC022I. Message IEC022I identifies the





138 to 13C

138

Explanation: The error occurred duringexecution of an ENQ macro instruction.

Two ENQ macro instructions were issued forthe same resource in the same task without anintervening DEQ macro instruction. The secondENQ macro instruction did not specify TEST,USE, or HAVE in its RET operand.


Specify RET=TEST, RET=USE, orRET=HAVE in the second ENQ macroinstruction, or add a DEQ macro instructionbetween the two ENQ macro instructions, ordelete one of the ENQ macro instructions.

Recompile, and execute the program again.


139

Explanation: An error occurred during theprocessing associated with SVC 57, which freesa buffer or extends the unscheduled test (via theFREEDBUF macro issued either by the user orthe system). The BDAM task recovery routinefor this SVC determined that all user controlblocks required as input to the SVC were in theuser's region and key, hence the error could notbe ascribed to any user control block.




13C

Explanation: An invalid request has beendetected. If register 15 contains X'04', aninvalid ESTAE request had been detected forone of the following reasons:

• Requestor is not authorized via APF or isnot in key 0-7 or is not in supervisor mode.

• An EXIT address of zero was specified.

• ESTAE CT was specified and an exitalready exists.

• ESTAE OV was specified and the mostrecent exit is not an ESTAE exit.

If register 15 contains X'08', an invalid ESTAIrequest had been detected for one of thefollowing reasons:

• Caller is not ATTACH.• An EXIT address of zero was specified with

CT.• OV was specified.• TCB address missing or invalid.

If register 15 contains X'0C', an invalid branchentry had been detected for one of the followingreasons:

• Requestor is not running under an SVRB.• Request is not for ESTAE.• The local lock was not obtained before

entry.

If register 15 contains X'10', one of thefollowing invalid TOKEN requests had beendetected:

• The TOKEN parameter was specified on amacro instruction other than the ESTAEmacro instruction.

• The requestor is not authorized to issue anESTAE macro instruction with the TOKENparameter.

System Action: The caller is abnormallyterminated. If a recovery routine is available, itis given control.

Programmer Response: Rewrite the programthat issues ESTAE or modifies the parameterlist built by the ESTAE macro, to correct thefailing request. If register 15 contains X'10', besure that the TOKEN parameter is specifiedonly by authorized programs and only on theESTAE macro instruction.

Note: The LSQS dump option is specified withthe ABEND macro instruction.


13E to 147

ABEND


13E

Explanation: A task that had created a subtaskissued a DETACH for that subtask, specifyingSTAE=NO, before the subtask has terminated.

System Action: The subtask is abnormallyterminated to force its completion.

Note: This may or may not be an error,depending on the intent of the user.Consequently, the task issuing the DETACH isnot terminated.

Programmer Response: If the subtask mustcomplete its processing before being detached,synchronization must be achieved by use of theECB or the EXTR operand on the ATTACHmacro instruction creating the subtask.


13F

Explanation: An error occurred duringexecution of a checkpoint restart.

System Action: The task is abnormallyterminated.

Programmer Response: Respond as indicated formessage IHJ007I, which appears on the console.

144

Explanation: The error occurred during theexecution of SYNADAF, where it wasdetermined that an invalid access method codewas specified in the high order byte of register15.

Programmer Response: Make sure that theACSMETH parameter on the SYNADAFmacro instruction is correctly coded, or that thehigh order byte of register 15 contains a validaccess method code before issuing SVC 68.


145

Explanation: The error occurred during theexecution of SVC 69 (BSP). Register 15 containsa return code indicating the cause of the error.See message IEC916I for the return codes andtheir meanings.

System Action: The backspace task recoveryroutine is invoked. If the caller's DCB, mainJOB, and first ICB for chained scheduling, orfirst JOB for normal scheduling are in its region,an attempt was made to trace them to theSYS1.TRACE data set.

Programmer Response: Verify that register 1contained the correct DCB address beforeissuing BSP and that the DCB has not beenoverlaid since being opened. If the DCB isvalid, verify that it contains the correct IOBand/or ICB addresses and that neither the IOBsand/or ICBs have been overlaid.

Problem Determination: Table I, items 1, 3, 5a,15, 16, 29. Table II, format 3.

147

Explanation: A program check or abnormaltermination occurred in the Graphics AccessMethod/System Product (GAM/SP) buffermanagement routine, IGC0007A. The erroroccurred either in GAM/SP or in the operatingsystem.

System Action: Message GAB260 appears onthe system console, identifying the cause of theerror and the original system completion code.In addition, GAM/SP writes a record to theSYS1.LOGREC data set and produces a dumpon the system dump data set.


1. Check for messages identifying the cause ofthe error. If these are GAM/SP messages,(that is, the message number is of the form'GABnnn'), they are described in IBM

Graphics Access Method/System Product:Messages and Codes.

2. Perform any corrective actions associatedwith the original system completion code.


149 to 14B



149

Explanation: An error occurred in either theGraphics Access Method/System Product(GAM/SP), or the operating system.

This completion code appears when:

1. A program check or abnormal terminationoccurs in the GAM/SP specify-attention(SPAR) routine, IGC0007C.

2. IGC0007C detects an invalid condition.

System Action: A message appears on thesystem console accompanied by a reason codeidentifying the area of processing where theerror occurred. In addition, GAM/SP writes arecord to the SYS1.LOGREC data set andproduces a dump on the system dump data set.






14A



1. A program check or abnormal terminationoccurs in the GAM/SP delete-attention(DAR) routine, IGC0007D.

2. IGC0007D detects an invalid condition.

System Action: A message appears on thesystem console, accompanied by a reason codeidentifying the area of processing where theerror occurred. In addition, GAM/SP writes arecord to the SYS1.LOGREC data set andproduces a dump on the system dump data set.






14B



1. A program check or abnormal terminationoccurs in the GAM/SP attention inquiry(ATTNINQ) routine, IGC0007E.

2. IGC0007E detects an invalid condition.

System Action: A message appears on thesystem console, accompanied by a reason codeidentifying the area of processing where theerror occurred. In addition, GAM/SP writes a

-record to the SYS1.LOGREC data set andproduces a dump on the system dump data set.







LEND

14F to 15B

14F

Explanation: An error was detected during theexecution of the STATUS macro instruction.

A routine tried to execute the STATUS macroinstruction for a function other than STOP,STOP SYNCH, or START, and the routine wasnot in storage protection key 0-7. Or, theparameter passed to STATUS processingcontained an invalid function code. Register 15contains a hexadecimal reason code:


20 An SRB (service request block) routine cannot seta step nondispatchable.

24 An invalid TCB address of zero was passed by thecaller.

System Action: If no recovery routine isspecified, the system terminates the issuer of theSTATUS macro instruction.

Programmer Response: Correct the error, andresubmit the job.

Problem Determination: Table I, items 1, 3, 5a,15, and 29.

151

Explanation: The error occurred during theexecution of SETPRT. The parameter listwhose address was passed to SETPRT inregister 1 was not in the user's region.


Programmer Response: Make sure that theSETPRT macro instruction is correctly coded.Correct the error, and rerun the job step.


153

Explanation: An error occurred while SMF wasprocessing a record. SMF was unable to handlethe new record because of buffer contention.

System Action: The task or SRB that attemptedto write an SMF record using the SMFWTM orSMFEWTM macro instruction terminatesabnormally. An SVC dump is scheduled.


Problem Determination: Table I, items 2, 7a, 7d,29, 33.

157

Explanation: An error occurred duringexecution of SVC 87, DOM (delete operatormessage) macro. Register 15 contains ahexadecimal reason code:


04 The caller passed an invalid value in register 0.

08 The issuer of the DOM request was neither a taskin the same job step and address space as theissuer of the WTOR, nor was the DOM issuer aprivileged task (supervisor mode or key 0-7 orAPF authorized).

0C A program check occurred while the system wasverifying that the caller could access each byte of amultiple DOM-id parameter list.

10 An unauthorized caller tried to delete a WTO thatwas not under the caller's ASID and TCB.

System Action: The DOM request is ignored.The DOM parameter list and the failingmessage id are shown in the dump. Any othermessage ids in the parameter list were alsoignored.

Programmer Response: Make sure that thecorrect message id is being used in the DOMrequest or make sure that the DOM issuer is inthe same job step as the WTOR issuer.


15B

Explanation: SVC 91 was issued by anunauthorized program. The error was detectedafter execution of a TESTAUTH macroinstruction. The program that issued SVC 91was not an APF authorized program, or wasnot in supervisor state, or was not executingunder storage protection key 0-7.


15C to 169

System Action: The program that issuedrestricted SVC 91 terminates abnormally.

Programmer Response: Correct the program sothat SVC 91 is issued only by an authorizedsystem routine.

15C

Explanation: An SVC 92 was issued; EXCPprocessing found that the program issuing therequest was not running in supervisor state.


Programmer Response: Ensure that the user isauthorized for use of SVC 92 (XDAP) or issueSVC 0 (EXCP).

Problem Determination: Table I, items 1, 2, 11and 29 if stopped on the address of ABTERMentry; otherwise, items 16 and 29.

15D

Explanation: The user specified an invalid dataarea to SVC 93 (TGET/TPUT).

System Action: The user is abnormallyterminated, and processing continues.

Programmer Response: Supply a data area foraccess by the program invoking SVC 93. ATPUT request requires read access; a TGETrequest requires write access.


15F

Explanation: The system resources manager wasinvoked incorrectly. During processing of aSYSEVENT, one of several possible errorconditions was discovered. Register 15 containsa hexadecimal reason code:


04 Invalid ASID, SYSEVENT code, or inputparameter.

08 Program was not authorized to issue theSYSEVENT.

0C A page fault occurred in referencing a data areaassumed to be fixed.

10 Protection check. The program did not have thecorrect storage key for storing in the parameterdata area.

14 SRM lock held prior to SRM invocation.

18 See the explanation for system completion code25F. (SRM's recovery routine converts this reasoncode to completion code 25F.)

1C A SYSEVENT TRANSWAP (or REQSWAP)with an ECB was issued when the maximumallowed number of pending TRANSWAPs (orREQSWAPs) with ECBs, had already beenreached.

System Action: The program issuing theSYSEVENT in which the error was detected isterminated.

Programmer Response: Determine whether theerror was the result of an invalid invocation ofthe system resources manager by a problemprogram. If the system resources manager wasinvoked by a system component and the errorrecurs, see Problem Determination.


169

Explanation: The error occurred during theexecution of IMGLIB with the CLOSE option.The DCB address passed to IMGLIB in register1 was invalid. This system completion code isaccompanied by message IEC919I. MessageIEC919I identifies the terminated task andexplains the return code in register 15.

Programmer Response: Make sure that theIMGLIB CLOSE macro instruction is correctlycoded. Make sure that the DCB address passedto IMGLIB is the same address returned toyour program by a previous IMGLIB OPEN,and that your program has not issued a priorIMGLIB CLOSE specifying this DCB address.Correct the error, and rerun the job step.



ABEND

16B to 171

16B

Explanation: The error occurred duringexecution of a MODESET macro instruction.The control program found that the parameterlist created from the macro instruction wasinvalid.

Programmer Response: Correct the specificationof the macro instruction or the program errorsthat incorrectly modified the parameter list.Recompile, and execute the job step again.

Problem Determination: Table I. items 1, 3, 5a,15, 16, 23, 29.

16D

Explanation: The error occurred duringprocessing of one of the extended SVC routers(ESR) for SVCs 109, 116, or 122. An invalidESR code was detected in register 15.

This error occurred because:

• The function invoked was not included inthe system.

• The ESR code passed by SVC 109, 116, or122 has no related function.

Programmer Response: In the first case, makesure that the item being invoked has beenincluded in the system. In the second case,correct the ESR code, and execute the job stepagain.


16E

Explanation: The control program requestedthat a DEBCHK function be performed on adata extent block (DEB) obtained from theDCB passed by the program. That functioncould not be completed. Register 15 contains ahexadecimal reason code.

Programmer Response: The response dependsupon the code in register 15:


04 The indicated DEB pointer is not in the DEBtable. A DEB whose address is not in the DEBtable cannot be verified, deleted, or purged.

08 Invalid TYPE specified (macro not issued).Acceptable types are ADD, DELETE, VERIFY,and PURGE.

10 DEBDCBAD does not point to DCB. It isassumed that the DCBDEBAD field of the DCBpoints to the DEB, but the DEBDCBAD field ofthe DEB must point to the DCB whenTYPE=VERIFY, ADD, or DELETE.

14 AM value does not equal DEBAMTYP value.When a DEB pointer is added to the table, theaccess method (AM) value, if given, is placed inthe DEBAMTYP field of the DEB. If no AMvalue is coded, a 0 is inserted in the field.Subsequent DEBCHKs issued to verify or deletethat DEB pointer must either specify the same AMvalue or omit the operand. When the operand isomitted, no comparison is made.

18 DEB not on TCB chain for TYPE=ADD. Beforethe DEB pointer can be added to the table, theDEB itself must be queued on the current TCBDEB chain (the TCBDEB field points to the firstDEB in the chain.)

1C DEBAMTYP or DEBTBLOF=0 forTYPE=ADD. Values other than 0 indicate apointer to this DEB already exists in the DEBtable.

20 DEB table contains 32760 bytes andTYPE=ADD. The current DEB table does nothave space for this new DEB pointer. To increasethe table size by an increment of 24 would causethe table to exceed its maximum size.

171

Explanation: The real storage manager wasinvoked with a request for a PGFIX, PGFREE,PGLOAD, PGOUT, or PGANY service; therequest was illegal or invalid. The request isconsidered illegal if the storage range specifiedby the input parameters does not exist, (aGETMAIN was not issued for it).

The following register contents are supplied fordiagnostic purposes:

Register 11 If LIST-FORMAT entry, address of theuser's first virtual subarea list (VSL)entry. If REGISTER-FORMAT entry,register 11 contains 0.

Register 12 Address of the input event control block(ECB). If no ECB address wassupplied, register 12 contains zero.


172 to 177

Registers 13-14 The VSL entry in error. See OS/VS2Data Areas for a description of theVSL.

Register 15 Hexadecimal error code as follows:

ErrorCode Explanation

04 The page services routinedetected the error; and the userdid not obtain the VSL storageusing a GETMAIN macroinstruction.

10 The input VSL or ECB failed topass the page services interfacevalidity check.

Possible errors are:

• Input parameter error in virtual subarea list(VSL):

– VSL not on a fullword boundary.

– VSL not in fixed storage.

– During a PGFREE, VSL specifiedfreeing the page containing the VSL,but the fix count of the page was one.

– Undefined or conflicting options flags.

• End address of range not greater thanbeginning address.

• An option was specified that is notsupported by MVS. These are RSAOPTand ECBIND.

– VSL is store-protected from the caller.

• Input parameter error on ECB:

– ECB not on fullword boundary.– ECB is store-protected from caller.– ECB not specified for PGFIX.– ECB specified for PGOUT or PGANY.

Programmer Response: Probable user error.Correct the program, and rerun the job. IfPGFIX or PGFREE was requested and the callwas not authorized, obtain proper authorizationfrom the installation manager, and rerun thejob.


172

Explanation: EXCP processing found that anunauthorized user has issued SVC 114(EXCPVR). For a user to be authorized, one ofthe following must true:

• The program issuing the request is runningunder system protection key 0-7.

• The program issuing the request is insupervisor state.

• The SVC 114 authorization bit is set in theJSCB.

• The SVC 114 authorization bit is set in theDEB.


Programmer Response: Ensure that the user isauthorized for use of SVC 114 (EXCPVR), orissue SVC 0 (EXCP).

Problem Determination: Table I, items 1, 2, 11and 29 if stopped on the address of ABTERMentry; otherwise, items 16, 29.

177

Explanation: The TESTAUTH routine detectedinvalid input parameters. One of the followinginvalid parameters was detected:

• An invalid bit mask in register 1.

• RBLEVEL=2 but RB is the last RBchained or out of range.

• The function code is greater than 256 or outof range.

• The authorization code is greater than 256or out of range.

Programmer Response: Make sure that theparameter list to TESTAUTH is valid. Theonly valid IBM-supplied authorization orfunction code is one. If the user's system


ABEND

178 to 17D

supplied an authorization matrix, check to seethat the function and authorization codes fallwithin the range of the user-defined codes.


178

Explanation: The error occurred during theexecution of an RU or RU form GETMAINmacro instruction for an authorized program.The program requested virtual storage thatrequires more real storage than is available.


Programmer Response: Make sure that theprogram issuing the GETMAIN macroinstruction is not asking for unnecessarily largeamounts of real storage. If this code occursfrequently, installation action is required toincrease the available real storage.


179

Explanation: During initial request processing,an error was discovered in the parametersassociated with an I/O request. At the time ofthe ABEND, register 3 contains a pointer to the

IOMB and register 2 contains a hexadecimalreason code:


04 Error return from SETLOCK macro.

08 Invalid AMB or IOMB.

0C Invalid CPA.

10 Error return from page fix.

14 Invalid buffer address. This error may appear asreason code 10.

18 Invalid addresses in chain CCW's.

1C Blocksize is not 4K for track overflow.

System Action: Processing continues.

Programmer Response: Make sure that theproblem program did not incorrectly modify thecontrol block structure or associated parameters.After making necessary corrections, recompile,and execute the job step again.

17A

Explanation: The error occurred duringexecution of an EVENTS macro instruction foreither a table creation or deletion. The controlprogram found that an invalid EVENTS tableaddress was specified.

Programmer Response: Make sure an EVENTSmacro was issued to construct the EVENTStable in question. Correct the error, and executethe job step again.


17B

Explanation: The PURGEDQ SVC was issuedand an invalid ASID was specified on theASID=parameter. The specified address spacedoes not exist.

Programmer Response: A supervisor state, key0, or authorized program has specified aninvalid ASID parameter as input to thePURGEDQ SVC routine. Check for invalidcoding of PURGEDQ input.


17D

Explanation: The error occurred duringexecution of an EVENTS macro instruction fora wait request. The control program found thatan invalid EVENTS table address was specified.

Programmer Response: Make sure an EVENTSmacro was issued to construct the EVENTStable in question. Correct the error and executethe job step again.



182 to 18B

182

Explanation: RACF was not successful atestablishing an ESTAE recovery environmentwhen processing the RACHECK SVC.


Programmer Response: Register 15 contains thenonzero return code passed back from ESTAE.Correct the indicated error.

Problem Determination: Table I, items 3, 4, 13,16, 33. Also refer to the publications OS/VS2MVS System Programming Library: Supervisorand OS/VS2 MVS Supervisor Services andMacro Instructions, for a description of ESTAEreturn codes.

183

Explanation: RACF was not successful atestablishing an ESTAE recovery environmentwhen processing the RACINIT SVC.



Problem Determination: (See code 182.)

185

Explanation: RACF was not successful atestablishing an ESTAE recovery environmentwhen processing the RACDEF SVC.



Problem Determination: (See code 182.)

18B

Explanation: The common VTOC access facility(CVAF) encountered one of the followingconditions:

• A structure error in the VTOC index.

• The CVAF return code is not consistentwith the CVAF status code.

System Action: A dump is written toSYS1.DUMP, and an error record is written toSYS1.LOGREC. The task is not terminated.If CVAF encountered a structure error in theVTOC index:

• Message IEC606I is issued.

• CVAF disables the VTOC index.

• If the caller of CVAF requests a read orwrite of a format-1 or 4 DSCB, CVAFperforms the function and returns a code ofyes to its caller.

• If the caller of CVAF requested a CVAFfunction that requires the VTOC index,CVAF returns an error return code to itscaller. This code may cause the caller toterminate.

If the CVAF return code is not consistent withthe CVAF status code, CVAF returns an I/Oerror return code to its caller. This code maycause the caller to terminate.

Programmer Response: If a structure error in theVTOC index was encountered and the programterminated, it may be rerun if it does notdepend upon the VTOC index. Execute theIEHLIST utility to list the VTOC and thedisabled VTOC index. An inconsistencybetween the CVAF return code and status codeindicates a logic error in CVAF. You may notbe able to run the job successfully until theproblem is corrected.

Problem Determination: Table I, items 2, 13, 18,25b, 29, and 33.


1FA to 1FB

ABEND

1FA

Explanation: The error occurred duringexecution of a data management request for aspool data set. JES2 found one of thefollowing:

• The data management control blocks are nolonger valid

• The JES2 UBUF control block is no longervalid.

Programmer Response: Probable use error.Verify that the terminated program did notmodify the data management control blocks orthe JES2 UBUF control block. Correct theerror, and execute the job step again.


1FB

Explanation: JES3 module IATDMEB issuedone of the following messages because of theindicated error:

Message Error

IAT1601 The user is trying to perform I/O to a data setthat is closed.

An invalid IATYDAT was found on the databuffer block (DAT) queue.

JES3 module IATSIAD issued one of thefollowing messages because of the indicatederror:

Message Error

IAT1602 (1) The IATYDSB and IATYSVT controlblocks were not valid, or (2) the IATYDATaddress is not within a correct address range.

IAT1603 A JES3 module passed, as a parameter toIATDMEB, a code that requested an invaliddata management function.

IAT1604 and IAT1605A start I/O operation in the user's addressspace returned an error code.

IAT1606 and IAT1608IATDMEB found an invalid unprotectedbuffer address.

IAT1607 IATDMEB could not allocate an unprotectedbuffer for a POINT operation.

JES3 module IATDMEB or IATSIAD issuedone of the following messages because of theindicated error:

Message Error

IAT1609 One of the following occurred:

• When IATDMEB or IATSIAD attemptedto set up a data management WAIT, themodule found a data managementfunction already waiting.

• When IATDMEB or IATSIAD attemptedto set up a subsystem interface WAIT, themodule found a subsystem functionalready waiting.

JES3 module IATSIOR, IATSIAD, orIATSICC issued one of the following messagesbecause of the indicated error:

Message Error

IAT6700 During unallocation, when attempting toupdate the JDSENTRY, the module could notfind a job data set (JDS) entry.

IAT6702 During OPEN processing, an error occurred inthe spool record address allocation routine.

IAT6703 When the module attempted communication, acatastrophic error occurred in the globalprocessor.

IAT6704 OPEN could not allocate a user address spacebuffer to a data set.

IAT6706 No storage was available for the globalinterface for the external writer data set.

IAT6707 At unallocation of the external writer data set,the module could not find an outputscheduling element (OSE).

IAT6708 A permanent I/O error occurred on an outputdata set.

IAT6711 A SSISERV macro sent invalid data to theglobal processor; the request could not beserviced.

IAT6716 A SYSOUT data set, which several tasks wereprocessing, failed to open properly.

JES3 module IATDMDM found an invalidIFGACB, IATYDSS, or IATYDSB controlblock. A message may not be issued in this case.

System Action: For IATDMEB, the systemterminates the job step. For IATSIOR,IATSIAD, or IATSICC, the system terminatesthe user address space.


1FC to 200

Programmer Response: If the problem occurredin an I/O operation, correct any I/O errors inyour program. Then rerun the job.

If not, notify your system programmer,supplying a SYSABEND dump.

Problem Determination: Table I, item 5k

If IATDMEB caused this system completioncode, register 15 in the dump points to a copyof the data set block (DSB). Offset X'8A' intothe DSB (field DSBMSGCD) contains themessage code that IATDMEB passed to theABEND routines. Use this message code todetermine the cause of the error. For example,for I/O operations, the message code identifieswhich issuance of the IATXSIO macro resultedin the error.


1FC

Explanation: A system error occurred during theexecution of the SVC first level interrupthandler. In an attempt to recover the system,the supervisory control program has abnormallyterminated the task that issued the SVC request.

System Action: The active task abnormallyterminated.


Problem Determination: Table I, items 1, 3, 5b,15 16, 29.

1FD

Explanation: An error was detected while MF/1was sampling data about the state of the system.

System Action: All MF/1 measurementcollection is terminated. As a result of thiserror, reinstatement of MF/1 may be attempted.If the reinstatement is successful, MF/1 willcontinue under the control of the originaloptions. If the reinstatement fails subsequently,MFG 1 is terminated.

Programmer Response: If the error persists,obtain a dump.

Problem Determination: Table I, items 5b, 16,18, 29.

200

Explanation: EXCP processing encountered oneof the following errors when checking thevalidity of an I/O request:

• The storage protection key of theinput/output block (IOB), the event controlblock (ECB), or the data control block(DCB) was not the same as the protectionkey value in the caller's request block (RB).

• A segment exception occurred when EXCPprocessing referenced the DCB address fieldin the IOB passed by the caller.

• A segment exception occurred when EXCPprocessing referenced the data extent block(DEB) address field in the DCB.

Note: A segment exception can occur ifcontrol blocks are prematurely freed oroverlaid or if the data set is not open.


Programmer Response: Verify that the data setwas opened and that the control blocks werecorrectly modified by the problem program. Ifthe EXCP access method is being used, makesure that the IOB and the ECB are correctlybuilt. After making corrections, execute the jobstep again.

If an abnormal termination dump is available,the TCB field TCBEXCPD (at offset C0) pointsto the EXCP problem determination area. Theitems in the problem determination area ofgreatest interest are:

• Offset 4 contains a copy of the programstatus word (PSW) when the error occurred.

• Offset E contains the interruption codewhen the error occurred.

• Offset 10 contains a copy of the registercontents when the error occurred.


ABEND

201 to 206

• Offset 50 contains the translation exceptionaddress, if applicable.

• Offset 54 contains the contents of therequest queue element (RQE), if allocated,when the error occurred.


201


The macro expansion contained an invalid eventcontrol block (ECB) address or the programissuing the WAIT macro instruction was notrunning under the same storage protection keyas the storage containing the ECB.

Programmer Response: Make sure that theaddress specified for the ECB is a valid virtualstorage address, that it was not incorrectlymodified, and that it is aligned on a fullwordboundary.

Correct the error, and execute the job stepagain.


202

Explanation: The POST macro instructionencountered an error while processing an ECB(event control block).

The control program found an invalid requestblock (RB) address in the 3 low-order bytes ofthe ECB specified by the problem program.

The address of the request block is placed in theevent control block during execution of a WAITmacro instruction. This address must remain inthe ECB until a POST macro instruction placesa post code or zeros in the ECB. The requestblock (RB) is a control block used for internalpurposes by the control program.

Programmer Response: Make sure that thecontents of the ECB were not modified after the

WAIT macro instruction and before the POSTmacro instruction.

Correct the error and execute the job step again.


206

Explanation: The error occurred duringexecution of a LINK, LOAD, XCTL,DELETE, or SYNCH macro instruction. Thecontrol program detected one of these errors:

• The address of the parameter list specifiedin the macro instruction was erroneous.

• The address of the name (if EP or EPLOCwas specified), or the address of thedirectory entry (if DE was specified) waserroneous.

• The parameter list pointed to by the macroinstruction contains a nonzero value in anundefined field.

• The caller is not authorized to use theoptions specified in the macro instruction.

• The LOAD macro instruction includes boththe ADDR=addr parameter (whichspecified an explicit LOAD) and theGLOBAL=YES parameter.

• The LOAD macro instruction includes theADDR=addr parameter, but addr is not adoubleword boundary.

• A request for an alias was made. However,the contents directory entry (CDE) that wasfound for the major name was already analias.

Message IEA807I accompanies this completioncode.

Programmer Response: Check for programerrors that incorrectly modify the parameter list.If the DE operand is specified, check that themacro instruction is correct for the attributes ofthe requested module. Ensure that the addressspecified in the EP, EPLOC, or DE operand isnot incorrectly specified or modified. Ensure

System Completion Codes SCC -77

20B to 213

that an alias is not being requested for a majorname that is already an alias. After makingcorrections, execute the job step again.


20B

Explanation: The error occurred in the TIMEservice routine. No usable time-of-day clockwas available in the system from which toobtain the correct time.

Programmer Response: None. Probablehardware error with the system time-of-dayclocks.


20D

Explanation: This completion code is foundonly in jobstep tasks. It indicates that an erroroccurred while a subtask was operating inSTEP=MUST COMPLETE status, or that asubtask issued an ABEND macro with theSTEP option. As a result, the abnormaltermination was extended to encompass theentire jobstep.

Note: The original completion code is found inthe TCB of the subtask that caused the error.

System Action: The jobstep tree is terminated.

Programmer Response: Correct the originalerror.


20E

Explanation: The error occurred duringexecution of the SPIE macro instruction. ThePIE address is invalid.

Programmer Response: Correct the PIE addressspecified, ensuring that it is a valid virtualstorage address assigned to the job step.Execute the job step again.


20F

Explanation: A module not in supervisor staterequested use of SVC 15 in IOS. SVC 15 isintended only for supervisor state modules. Noother requestor is authorized.

Operator Response: Notify the installationmanager or system programmer immediately.Hold all output relevant to the job.

Programmer Response: Check for possible usererror.

212

Explanation: An error occurred during theexecution of SVC 18; the error could not beattributed to invalid user input. This systemcompletion code is accompanied by messageIEC909I. Message IEC909I identifies theterminated task and explains the return code inregister 15.

System Action: Message IEC909I is issuedindicating whether a dump was written to theSYS1.DUMP data set.

Programmer Response: Make sure that theBLDL or FIND macro instruction is correctlycoded, and that the parameter list and controlblocks involved are not modified by yourprogram during the execution of SVC 18.


213

Explanation: The error occurred duringexecution of an OPEN macro instruction for adirect access device. This system completioncode is accompanied by message IEC143I.Message IEC143I identifies the terminated taskand explains the return code (rc in the messagetext) in register 15.



214 to 222

ABEND

Problem Determination: Table I, items 1, 3, 5a,15, 16, 25b, 29.

214

Explanation: The error occurred duringexecution of a CLOSE macro instruction for adata set on magnetic tape. This systemcompletion code is accompanied by messageIEC210I. Message IEC210I identifies theterminated task and explains the return code (rcin the message text) in register 15.



215

Explanation: The error occurred during theexecution of SVC 21 (STOW). This systemcompletion code is accompanied by messageIEC910I. Message IEC910I identifies theterminated task and explains the return code inregister 15.

System Action: The STOW task recoveryroutine has been invoked. If the calling taskand the DCB are in the same region, the systemattempts to trace the DCB to the SYS1.TRACEdata set.

Programmer Response: For return codes 01, 02,and 03, verify that register 1 contained thecorrect DCB address before issuing SVC 21 andthat the DCB was not overlaid since beingopened. For return code 04, verify that register0 contained the correct parameter list addressand that the list is within the caller's regionbefore SVC 21 is issued.


218

Explanation: During execution of DEVTYPE(SVC 24), an error occurred; it could not beattributed to invalid user input. This systemcompletion code is accompanied by messageIEC913I. Message IEC913I identifies the


Programmer Response: Make sure that theDEVTYPE macro instruction is correctly coded,and that the areas passed to DEVTYPE are notfreed by your program during the execution ofSVC 24.


219

Explanation: An error during execution of SVC25 could not be attributed to invalid user input.This system completion code is accompanied bymessage IEC915I. Message IEC915I identifiesthe terminated task and explains the return codein register 15.

System Action: Message IEC915I indicateswhether the system writes a dump to theSYS1.DUMP data set.

Programmer Response: Make sure that yourprogram does not alter the DCB or IOB duringthe execution of SVC 25.


222

Explanation: The operator or an authorizedTSO user with operator capability canceled thejob.

The job may have been canceled because itappeared to be in a loop or because it waswaiting for resources that were not immediatelyavailable (for example, direct access space ordevices). Perhaps the job was canceled tocorrect a system interlock (for example, twotasks enqueued on a resource without anintervening dequeue). Or the job may haveviolated a procedure established for yourinstallation. The operator or an authorizedTSO user with operator capability can havemany reasons for canceling a job. Yourprogram may contain no errors.

System Action: The system terminates the job;the system may write a dump, even though a


228 to 22D

dump was not requested, depending on whichsystem routine had control.

Programmer Response: Find out why theoperator or the authorized TSO user canceledyour job; make any necessary corrections. Ifyou want a dump but a dump was not written,resubmit the job and ask the operator to cancelit using the command CANCEL jobname,DUMP.

Problem Determination: Table I, items 1, 2, 5aor b, 16, 23, 29.

228

Explanation: During execution of anEXTRACT macro instruction, the location ofthe input parameter list was invalid. (The inputparameter list, ordinarily created throughexpansion of the standard or MF=L form ofthe EXTRACT macro instruction, describes thefunction to be performed.) The starting addressfor the parameter list was not on a fullwordboundary or within the area of storage assignedto the job step.

Programmer Response: Correct the program sothat the address of the input parameter list isvalid, recompile, and execute the job step again.


22A

Explanation: The error was detected duringexecution of an ATTACH macro instruction.The issuer of the ATTACH macro instructionspecified the GSPV, GSPL, SHSPV, or SHSPLparameter with a subpool ID greater than 127.Subpools above 127, that is, subpools 128through 255, are supervisor subpools; a problemprogram is not permitted to use these subpools.


Programmer Response: Change the macroinstruction to specify a problem programsubpool (1 through 127). If the macroinstruction is specified correctly, check forprogram errors that incorrectly modify it.

Recompile the program and execute the job stepagain.

Problem Determination: Table I, items 1, 5a, 16,23, 29. Table II, format 2: trace optionkeyword(s) - (TRACE=SVCP), eventkeyword(s) - (SVC=42,END).

22C

Explanation: The error occurred duringexecution of a CHAP macro instruction.

The address of the fullword specified in thesecond operand of the CHAP macro instructionis invalid for one of the following reasons:

• It was not a multiple of 4.

• The addressed virtual storage has not beenallocated.

• The storage key of the fullword does notmatch the protection key of the issuer of theCHAP macro.

This fullword contains the address of the TCBfor the subtask whose priority was to bechanged.

Programmer Response: Change the CHAPmacro instruction to specify a valid fullwordaddress. Ensure that this fullword will containthe address of the TCB when the CHAP macroinstruction is executed. Also, ensure that theproblem program does not incorrectly modifythe specification. Recompile, and execute the jobstep again.

Problem Determination: Table I, items 1, 5a, 16,23, 29. Table II, format 2: trace optionkeyword(s) - TRACE=SVCP, event keyword(s)- SVC=44,END.

22D


The overlay supervisor found an invalid addressin the segment table or the entry table. Theaddress pointed to a location outside theboundaries of the virtual storage assigned to thejob step.


ABEND

22E to 233

Programmer Response: Check for programerrors that caused the segment table or entrytable to be incorrectly modified. Correct theprogram, link-edit, and execute the job stepagain.


22E

Explanation: The error occurred in theTTIMER service routine. No usabletime-of-day clock was available in the systemfrom which to obtain the correct time.

Programmer Response: None. Probablehardware error with the system time-of-dayclocks.


22F

Explanation: The system has no usablecombination of time-of-day clock and clockcomparator (REAL or WAIT type request) orno usable CPU timer (TASK type request).

Programmer Response: None. Probablehardware error with the system clocks.


230


An invalid length was specified for the namerepresenting a resource. The length wasspecified in the rname length operand of theDEQ macro instruction, was supplied by theassembler program, or was contained in the byteimmediately preceding the resource name.

Programmer Response: Correct the invalidmacro instruction or the program errors thatincorrectly modified the length. Recompile theprogram, and execute the job step again.


233

Explanation: Invalid parameters have beenpassed to SVC dump. Register 15 contains ahexadecimal reason code:


04 The address of the parameter list is zero.

08 The parameter list is not a valid SVC dump orsnap parameter list for MVS.

0C The caller-supplied data set is on an unsupporteddevice.

10 In a user-supplied storage range, the start addressis greater than or equal to the end address.

14 The user-supplied data for HDR=or HDRAD=is greater than 100 characters.

18 The 4K SQA buffer has been requested(BUFFER=YES) but it is not serialized by settingto one the high order bit in the CVTSDBF.

1C The parameter list or what it points to is in the 4KSQA buffer.

20 The user-supplied DCB address is invalid, or theDCB is not open.

28 An ASID specified in the ASIDLST or ASIDparameter is syntactically invalid. The ASID isless than zero, or greater than the maximum value.

38 The caller specified the 4K SQA buffer(BUFFER=YES) but an SVC dump was alreadyin progress.

System Action: The system abnormallyterminates the caller and gives control to arecovery routine, if it had been specified.

Operator Response: Inform the systemprogrammer.

Programmer Response: Correct the invalidparameters, and reissue the SDUMP macroinstruction.

Problem Determination: Table I, items 5ab, 7c,13, 19, 29.


235 to 239

235

Explanation: An error occurred duringprocessing associated with SVC 53, whichobtains and releases exclusive control of aresource associated with a BDAM data set. Thetask recovery routine for this SVC determinedthat a control block required as input to SVC 53was not in the user's region and/or key. Thissystem completion code is accompanied bymessage IEC902I. Message IEC902I identifiesthe terminated task and the explains the returncode in register 15.

System Action: Message IEC902I specifies acleanup code, which indicates the results of thecleanup of resources attempted by the recoveryroutine.

Programmer Response: Insure the validity of thecontrol block from which the address of theblock in error was taken. For example, makesure that the BLKREF address specified in theRELEX macro is valid and in the correctformat and that the DCB address passed isvalid. If a RELEX macro was not issued, makesure that the IOB related to the exclusivecontrol request is correct and contains thecorrect DECB address (IOBECBPT) and DCBaddress (IOBDCBPT).

In addition, check the DCBEBAD field in theDCB to ensure that it contains the correct DEBaddress, and that the DEB (DEBDCBAD)points back to this DCB. If the next IOB isfound to be in error, find the entry in the readexclusive list associated with the requested blockand ensure that the RDXIOBUQ field is correct.

Problem Determination: Table I, items 4, 5b, 16.Table II, item 3.

237

Explanation: The error occurred at anend-of-volume. This system completion code isaccompanied by message IECO23I. MessageIECO23I identifies the terminated task andexplains the return code (rc in the message text)in register 15.

Programmer Response: Respond as indicated formessage IECO23I.


238


An invalid length was specified for the namerepresenting the resource. This length wasspecified in the rname length operand of theENQ macro instruction, was supplied by theassembler program, or was contained in the byteimmediately preceding the resource name.

Programmer Response: Correct the invalidmacro instruction or the program errors thatincorrectly modified the length. Recompile theprogram, and execute the job step again.


239

Explanation: An error occurred during theprocessing associated with SVC 57, which freesa buffer or extends the unscheduled text (via theFREEDBUF macro issued either by the user orthe system). The BDAM task recovery routinefor this SVC determined that a control blockrequired as input to SVC 57 was not in theuser's region and/or key. This systemcompletion code is accompanied by messageIEC902I. Message IEC902I identifies theterminated task and explains the return code inregister 15.

System Action: Message IEC902I specifies acleanup code, which indicates the results of thecleanup of resources attempted by the recoveryroutine.

Programmer Response: Insure the validity of thecontrol block from which the address of theblock in error was taken. The DECB and DCBwere specified in the FREEDBUF macro asinput to the SVC. Make sure that theDCBBUFCB field in the DCB contains thecorrect address of the buffer control block andthe DCBDYNB field contains the correctaddress of the unscheduled list (if address spacewas virtual). The BCB or USL contain theaddress of the next IOB waiting to get a buffer,


ABEND

23E to 245

if one was not available. Ensure that thisaddress has not been overlaid. Make sure alsothat the input DECB contains the address of thebuffer being freed (DECAREA field) and, if abuffer was requested for keys also, that theDECKYADR field contains the correct address.

Problem Determination: Table I, items 4, 5b, 16,29. Table II, format 3.

23E

Explanation: During execution of a DETACHmacro instruction, one of the following errorswas detected:

• The parameter passed to DETACH inregister 1 was not a fullword address

• The storage key of that address did notmatch that of the issuer of the DETACH.

• The parameter contained in the addressedfullword of the issuer was not the address ofa subtask of the issuer of the DETACH.

System Action: The system abnormallyterminates the issuer of the DETACH.

Programmer Response: Change the DETACHmacro instruction to specify a valid address ofthe TCB, and make sure that it was notincorrectly modified by the problem program.Recompile, and execute the job step again.


23F

Explanation: An unauthorized user attempted toread or write a checkpoint data set.

System Action: The system abnormallyterminates the task and issues message IEC954I.

Programmer Response: See message IEC954I forfurther details.

240

Explanation: The error occurred duringexecution of a RDJFCB macro instruction.This system completion code is accompanied by

message IEC155I. Message IEC155I identifiesthe terminated task and explains the return code(rc in the message text) in register 15.



244

Explanation: During execution of SYNADAF,the system found that the register saveareaprovided by the user was invalid.

Programmer Response: Make sure that whenSYNADAF (SVC 68) is issued, register 13points to a register savearea within the user'sregion. If SYNADAF is issued from a SYNADroutine, make sure that register 13 has not beenaltered since the SYNAD routine was entered,and that register 13 contained the address of avalid register savearea when the last datamanagement macro was issued.

Correct the error, and rerun the job step.


245

Explanation: An error during execution of SVC69 (BSP) could not be attributed to invalid userinput. This system completion code isaccompanied by message IEC917I. MessageIEC917I identifies the terminated task andexplains the return code in register 15.

System Action: The backspace task recoveryroutine was invoked. Low real storage and thecaller's region have been dumped to theSYS1.DUMP data set. The caller's inputregister 1 and DCB have been written to theSYS1.LOGREC data set.

Programmer Response: Make sure that the BSPinstruction is correctly coded, and that the DCBand IOBs and/or ICBs for the data set beingprocessed are not overlaid by your programduring the execution of SVC 69.


247 to 25F

Problem Determination: Table I, items 1, 2, 3,lab, 11, 13, 15, 18, 29.

247

Explanation: An error occurred in either theGraphics Access Method/System Product(GAM/SP), or the operating system. Thiscompletion code appears when an invalidcondition is detected by the GAM/SP buffermanagement routine, IGC0007A.

System Action: A message appears on thesystem console that identifies the cause of theerror. In addition, GAM/SP writes a record tothe SYS 1. LOGREC data set and produces adump on the system dump data set.






251

Explanation: During execution of SETPRT, theDCB exit list was determined to be invalid.This system completion code is accompanied bymessage IEC918I. Message IEC918I identifiesthe terminated task and explains the return codein register 15.

System Action: The system issues message1EC9181.

Programmer Response: Make sure that the lastentry in the exit list has a high-order bit set to

B'1'. Make sure that any FCB image entry inthe exit list points to a valid FCB image, thatthe image is within the user's region, that anyFCB image has a valid length field, and that itis terminated by an end-of-FCB image indicator.Correct the error, and rerun the job step.


253

Explanation: Because one or more errorsoccurred during SMF processing, the systemterminated SMF recording.

System Action: The system terminates the SMFwriter task and releases the resources used bySMF.

Operator Response: Notify the systemprogrammer. If SMF recording is essential forthe system, restart the system as soon as theproblem is corrected.

Programmer Response: Check the errormessage(s) and the SVC dump issued as a resultof the previous abnormal termination(s).


25F

Explanation: A system failure (machine check orrandom store, for example) has destroyed dataused by the system resource manager incontrolling this address space.

System Action: If the terminated task is themaster scheduler command processor, and thesystem resource manager has been processing aNEWIPS sysevent, the new IPS may have beenlost.

If the system measurement facility (MF/1) orresource measurement facility (RMF) has beenterminated, accumulated service and workloadmeasurements may not be valid.

In all other cases, data pertaining to the addressspace's swap status or performancecharacteristics may have been lost and thesystem resource manager may no longer be ableto control the address space according to itspreviously assigned performance specification.

The system does the following:

• Writes a record to SYS 1. LOGRECdescribing the error

• Inserts 'worst case' substitute values in placeof the lost address space characteristics in


ABEND

260 to 26D

case the STAE routine or the terminatedtask requests retry

• Terminates the controlling task of theaddress space or system component affectedby the data loss

Programmer Response: Resubmit the job, orrestart the terminated function.


260

Explanation: The STAX SVC detected aninvalid user parameter.

System Action: One of the following occurs:

• If one exists, the user's recovery routinereceives control.

• The user's TCB is abnormally terminated.

Programmer Response: The issuer of the STAXcan do one of the following:

• Continue processing without the STAXenvironment.

• Correct the parameters, and reissue STAX.

These actions are only possible if the caller hasan error recovery exit that will receive control asa result of the ABEND.

Note: Examples of conditions that could causethe ABEND are:

• Input or output buffer size greater than32K.

• Invalid input buffer address.• Both DEFER=YES and DEFER=NO

specified.

269

Explanation: An error during execution ofIMGLIB could not be attributed to invalidinput to IMGLIB. Register 15 contains a returncode that indicates whether the system wrote adump to the SYS1.DUMP data set.

System Action: The IMGLIB task recoveryroutine tried to write a dump to theSYS1.DUMP data set; the result is indicated bythe return code in register 15. See messageIEC920I for an explanation of the return codes.Additional diagnostic information was writtento the SYS1.LOGREC data set.

Programmer Response: Make sure that theIMGLIB macro instruction is correctly coded.


26D

Explanation: An error was detected incommunications between MF/1 and the systemresources manager while attempting to initialize,collect, or reinitialize workload activitymeasurements. Register 15 contains the returncode from the system resources manager in thefollowing byte location, depending on thefunction attempted by MF/l:

Byte Attempted Function

0 N/A.

I Reinitialization of workload activity measurementcollection after a change in the installationperformance specification (IPS).

2 Collection of workload activity measurements.

3 Initialization of workload activity measurements.

System Action: The system terminates all of theMF/1 measurement collection. As a result ofthis error, reinstatement of MF/1 may beattempted. If the reinstatement is successful,MF/1 continues under the control of theoriginal options. If the reinstatement fails,MF/1 is terminated.

Programmer Response: If the error persists,obtain a dump.



271 to 283

271

Explanation: The user is not authorized torequest a PGFIX or PGFREE service.

System Action: The requested service is denied.

User Response: Change the program, or obtainauthorization from installation management.

Problem Determination: Table I, items 1, 5a, 16,25c, 29.

279

Explanation: During I/O request terminationprocessing, an error was discovered in theparameters associated with an I/O request. Atabnormal termination, register 3 contains apointer to the IOMB and register 2 contains ahexadecimal reason code:


4 Invalid BUFC. The virtual storage originallyassigned to a BUFC no longer belongs to the user.

14 An invalid buffer address was discovered whileattempting I/O (a protection check occurred).

System Action: Processing continues.

Programmer Response: Make sure that theproblem program did not incorrectly modify thecontrol block structure or associated parameters.Make corrections, recompile, and execute thejob step again.


27B

Explanation: An error occurred in the FESTAEissued by PURGEDQ while attempting toestablish the recovery environment forPURGEDQ processing. The error was notcaused by any action of the current task, butwas a result of an environmental error.

System Action: The task that issued thePURGEDQ macro instruction is abnormallyterminated.

Operator Response: Rerun the job.

Problem Determination: Table I, items 5a, 16,18, and 29.

282

Explanation: An error was detected by RACFin the parameters passed to RACF forRACHECK SVC processing.


Programmer Response: Register 15 contains ahexadecimal reason code:

ReasonCode Meaning

04 Invalid parameter list length.

10 APF authorization, or system key 0-7, orsupervisor state required for CSA, LOG,PROFILE, or ACEE option.

14 Invalid ATTR option specified.

18 Volume serial required but not supplied.

1C Inconsistent PROFILE/ENTITY flag settings.

20 No resource name or PROFILE specified.

24 No CLASS name specified.

2C Invalid LOG option specified. (This code is usedonly through RACF version 1.4.)

30 Volume serial specified for class other thanDATASET.

Identify and correct the indicated error.


283

Explanation: An error was detected by RACFin the parameters passed to RACF forRACINIT SVC processing.


285 to 2F3

ABEND




04 Invalid parameter list length.

14 ENVIR data specified was invalid.

18 USERID specified did not conform to lengthrequirements.

1C PASSWRD specified did not conform to lengthrequirements.

20 GROUP specified did not conform to lengthrequirements.

24 NEWPASS specified did not conform to lengthrequirements.

28 OIDCARD specified had length field=0.

30 Invalid combination of ENVIR keyword data andUSERID, PASSWRD, NEWPASS, START,OIDCARD, TERMID, or APPL specified.

34 Invalid combination of ENVIR keyword data andGROUP specified.

38 ENVIR=CHANGE specified but no ACEEexits.



285

Explanation: RACF detected an error in theparameters passed to it for RACDEF SVCprocessing.




'04 Invalid parameter list length.

08 Invalid level number.

0C Invalid TYPE option specified. (This code is usedonly through RACF version 1.3.)

10 Resource name required.

14 New data set name or old volume serial specifiedbut addr is zero.

18 Volume serial required but not specified.

1C New data set name and old volume serial flagsboth set.

24 Inconsistent parameters for class other thanDATASET, that is: model name supplied, modelvolume serial supplied. VSAM data set bit on, oldvolume serial supplied or new data set namesupplied.

28 Model resource information supplied with typeother than DEFINE for DATASET class.

2C Model name supplied but model volume serial notsupplied.

30 Unqualified data set name specified.

34 Old volser is absent for CHGVOL request.

38 Unit field has invalid length.

3C Invalid AUDIT value.

40 Invalid OWNER specified.

44 Invalid UACC values.

48 Invalid rename request; either ENTITY name orNEWNAME name, but not both, is a genericname.



2F3

Explanation: The job was running when asystem failure occurred. A system restart wasperformed; a system job queue entry for the jobexisted at the time of failure.

Programmer Response: If results of the job areunsatisfactory, resubmit the job or job steps.


2FB to 300

2FB

Explanation: The JES3 or FSS address spacehas abnormally terminated at one of thefollowing points in processing:

1. A critical error occurred early in JES3 orFSS initialization or late in JES3termination. The JES3 ESTAEenvironment had not yet been established orhad been deleted, so no JES3-formattedABEND dump is available.

2. Once JES3 initialization has successfullyestablished the JES3 ESTAE routine(IATABMN), the retry routine (IATABRT)uses this ABEND code to return toIATABMN in order to percolate.

An MVS dump will always appear for a 2FBABEND, regardless of the original ABENDcode. The original ABEND code is shown inmessage IAT3713 to the operator and in theJES3-formatted dump. The 2FB dump by itselfdoes not tell whether the failing JES3 functionrecovered or had to be terminated.

Note: An MVS dump with a 2FB ABENDmeans that IATABRT or a routine used byIATABRT failed, thereby producing the 2FBABEND.

System Action: In the first case, JES3 writesmessage IAT3702 to the operator and to adump data set of the type specified during JES3initialization. This message details criticaldebugging information. The system writes anABEND dump of the type specified during JES3initialization.

Operator Response: In the first case, respond tomessage IAT3nnn.

Programmer Response: In the second case,analyze the ABEND dump to find the cause ofthe error.

Problem Determination: Table I, items 2, 5, 16.Table III, items 4, 5, 6, 20.

2FC

Explanation: An error occurred duringexecution of the I/O first level interrupt handler.In an attempt to recover the system, thesupervisory control program has abnormallyterminated the task that took the I/O interrupt.

System Action: The system abnormallyterminates the active task.



300

Explanation: EXCP processing encountered oneof the following errors while processing an I/Orequest:

• The DEB (data extent block) validity checkroutine (IFGDEBCK) returned a nonzeroreturn code to EXCP processing for one ofthe following reasons:

– The DEBTABLE does not exist.

– The DEBTBLOF value in the DEB isless than one or greater than thenumber of entries in the DEBTABLE.

– The address of the DEB, obtained fromthe DCB (data control block), does notmatch any entry in the DEBTABLE.

• The IOBM field in the IOB (input/outputblock) is not lower than the maximumextent count (DEBNMEXT) in the DEB.


Programmer Response: Verify that the datacontrol block (DCB) contains the address of theDEB. After making corrections, execute the jobstep again.

If an abnormal termination dump is available,the TCB field TCBEXCPD (at offset C0) points


ABEND

301 to 306

to the EXCP problem determination area. Theitems in the problem determination area ofinterest are:

• Offset 10 contains a copy of the registercontents existing when EXCP processingdetected the error.

• Offset 54 contains the contents of therequest queue element (RQE), if allocated,when EXCP processing detected the error.


301


The macro instruction specified an event controlblock (ECB) whose wait flag was already on.This indicated that a previous WAIT macroinstruction was already waiting for posting ofthe ECB.

Programmer Response: Change the problemprogram to eliminate a double wait on a singleevent. If no double wait is found, make surethat the program did not incorrectly modify theECB. Then execute the job step again.


304

Explanation: Cross Memory POSTasynchronous processing failed. Thiscompletion code is issued by PRTOERTN, theCross Memory POST asynchronous error exitroutine in module IEAVGPRR (theGETPART/FREEPART FRR).

System Action: The system terminates therequestor.

Programmer Response: Check for a valid ECBin the JSCB of the task requesting the V=Rregion.

Problem Determination: Table I, items 5a, 11,16,29.

305

Explanation: The error occurred duringexecution of a FREEMAIN macro instruction.

• The specified subpool could not be found.

• The SP parameter was specified, but thevirtual storage area to be released was notwithin the subpool specified.

• The SP parameter was not specified, but thevirtual storage area to be released was notwithin subpool zero.

• The SP parameter was specified correctly,but the boundaries of the storage area to befreed were not completely described by adescriptor queue element (DQE).



Programmer Response: Make sure that theFREEMAIN operands A and LV specify anarea within the subpool. If they do, check forprogram errors that incorrectly modify theFREEMAIN macro expansion. After makingcorrections, execute the job step again.

Problem Determination: Table I, items 1, 5a, 16,23, and 29.

306

Explanation: The error occurred duringexecution of the LINK, XCTL, ATTACH, orLOAD service routines.

An authorized routine requested a module thatcould not be found in an authorized library.The module was found either in anonauthorized library or in storage (alreadyloaded), but marked as coming from anunauthorized library.


30A to 30E



04 The requested program was not found in theindicated source (private library, job library, orlink library).

08 An uncorrectable I/O error occurred when thecontrol program attempted to search the directoryof the library containing the module.

0C The module could not be found on the LPA or inthe LPA directory or an authorized library.

14 The LOAD macro instruction was issued with theGLOBAL=YES operand, but the module to beloaded is not reentrant or is in an unauthorizedlibrary.

18 The LOAD macro instruction includes theGLOBAL=(YES,F) parameter for a module withpage boundary alignment.

Programmer Response: If the requested modulecould not be found, make sure the module existson a system or user-defined authorized library.Correct the error, and execute the job stepagain.

Problem Determination: Table I, items 1, 5a, 16,22, 25c, 29.

30A

Explanation: The error occurred during theexecution of an R-form FREEMAIN macroinstruction.

• A FREEMAIN for an entire subpool wasrequested (register 1 was zero), but thelength in register 0 was not set to zero.




• The SP parameter was specified correctly,but the boundaries of the storage area to befreed were not completely described by adescriptor queue element (DQE).





30E

Explanation: The error occurred during theexecution of the SPIE macro instruction.

1. An unauthorized program attempted tospecify program interruption code 17.

2. SPIE caller in supervisor state (SPIE mustbe issued in problem state).

3. SPIE caller's PSW key does not match thecaller's TCB key.

Programmer Response: In the first case, recodethe macro instruction to delete the specificationof interrupt code 17, or contact the systemprogrammer to have authorization assigned toyour program through the authorized programfacility (APF). In the second case, make sureSPIE was issued in problem state. In the thirdcase, make sure the PSW key matches the TCBkey. Then execute the job step again.



ABEND

313 to 322

313

Explanation: The error occurred duringexecution of an OPEN macro instruction for adata set on a direct access device. This systemcompletion code is accompanied by message

IEC144I. Message IEC144I identifies theterminated task and explains the return code (rcin the message text) in register 15.



314

Explanation: The error occurred during theexecution of a CLOSE macro instruction for adata set on a direct access device. This systemcompletion code is accompanied by messageIEC211I. Message IEC211I identifies theterminated task and explains the return code (rcin the message text) in register 15.



315

Explanation: An error during execution of SVC21 (STOW) could not be attributed to invaliduser input. This completion code isaccompanied by message IEC911I. MessageIEC911I identifies the terminated task andexplains the return code in register 15.

System Action: The STOW task recoveryroutine has been invoked. Low real storage andthe caller's region have been dumped to theSYS1.DUMP data set. The caller's inputregisters 0 and 1, and DCB have been written tothe SYS1.LOGREC data set.

Programmer Response: Make sure that theSTOW macro instruction is correctly coded, and

that the parameter list and DCB involved arenot modified by your program during theexecution of SVC 21.

Problem Determination: Table I, items 1, 2, 3,lab, 11, 13, 15, 18, 29.

317

Explanation: The error occurred duringexecution of a BSAM CLOSE macro instructionwith a TYPE=T operand for a data set on adirect access device. This system completioncode is accompanied by message IEC220I.Message IEC220I identifies the terminated taskand explains the return code (rc in the messagetext) in register 15.



322

Explanation: Execution of a job, job step, orcataloged procedure step took longer than thetime specified in:

• The TIME parameter of the EXEC or JOBstatement

• The standard time limit specified in the jobentry subsystem

System Action: The system abnormallyterminates the job, job step, procedure, orprocedure step.

Programmer Response: Check for programerrors, such as endless loops, that would causethe job step, procedure, or procedure step totake too long. Correct any such errors. If noerrors are found, specify a longer time in theTIME parameter. Then execute the job again.

Problem Determination: Table I, items 1, 5a, 7b,26d, 29.


328 to 337

328

Explanation: The error was detected duringexecution of an EXTRACT macro instruction.

The task control block (TCB) specified in thesecond operand of the macro instruction wasnot for a subtask of the task issuing theEXTRACT macro instruction.

Programmer Response: Change the EXTRACTmacro instruction to specify a task control blockfor a subtask. If the macro instruction wasspecified correctly, check for program errorsthat incorrectly modified the EXTRACT macroexpansion. Make corrections, recompile, andexecute the job step again.


32D


A record of an incorrect length was found or anuncorrectable input/output error occurred inloading a segment from the library.

Programmer Response: Link-edit the programagain, and execute the job step again.


330

Explanation: An unauthorized task attempted touse authorized options of the DEQ macroinstruction.

Programmer Response: Correct the macroinstruction, recompile, and execute the job stepagain.


335

Explanation: SVC 35, which obtains andreleases exclusive control of a resourceassociated with a BDAM data set, found thatthe block for which acquisition or release ofexclusive control was requested was not in thedata set.

Programmer Response: If the RELEX macrowas issued, the user should ensure that theBLKREF address supplied in the RELEXmacro points to a valid address within the dataset described by the input DCB. Make sure alsothat the address format is compatible with theaddressing scheme specified in the DCBOPTCDfield of the DCB. If the RELEX macro was notissued, the block ID was taken from theIOBSEEK field, or in the case of write-addrequests, the IOBDNCRF field. Theseaddresses are derived from conversion of theblock ID pointed to by the DECRECPT field ofthe DECB. Make sure that this address iscorrect and that the format of the block ID iscompatible with that specified in theDCBOPTCD field of the DCB and isleft-aligned.

Problem Determination: Table I, items 5b, 16,25a, 29.

337

Explanation: The error occurred when the endof a data set was reached. This systemcompletion code is accompanied by message



Problem Determination: Table I, items 1, 3, 5b,15, 16, 21, 29.


ABEND

338 to 35F

338

Explanation: An unauthorized task attempted touse authorized options of the ENQ macroinstruction.

Programmer Response: Correct the macroinstruction, recompile, and execute the job stepagain.

339

Explanation: SVC 57 frees a buffer or extendsthe unscheduled list via a FREEDBUF macroissued by the user or the system. SVC 57 foundthat the DEB pointed to by the input DCB(DCBDEBAD) was not on any DEB chainassociated with that job step TCB, or did notpoint back to that DCB, or was requested for adata set that was neither BDAM nor ISAM.

Programmer Response: Make sure that the inputDCB address is correct and that theDCBDEBAD field of the input DCB has notbeen overlaid.

Problem Determination: Table I, items 5b, 16,29.

33E

Explanation: A DETACH macro instructionspecifying the STAE=YES operand has beenissued by the originating task, but the specifiedsubtask has not completed execution.

System Action: The subtask is abnormallyterminated. If the STAE macro instruction wasissued by the subtask, the specified exit routinewill be given control during abnormaltermination processing. However, if the STAEexit routine specified a retry routine, the retryroutine will not be given control.

Programmer Response: This may or may not bean error. If you intend for the subtask tocomplete processing before it is detached, usethe ECB or EXTR operand on the ATTACHmacro instruction that creates the subtask toachieve synchronization.


344

Explanation: During execution of SYNADAF,the DCB address was determined to be invalid.

Programmer Response: Register 15 contains theDCB address in error. For BDAM, BPAM,QSAM, BISAM, and QISAM, the DCB addressshould be passed to SYNADAF as the PARM1operand on the SYNADAF macro instruction.(For BDAM, BPAM, BSAM, and QSAM, theDCB address is in register 1 on entry to theuser's SYNAD routine.) For EXCP accessmethod, verify that the IOBDCBPT fieldcontains the correct DCB address. Correct theerror, and rerun the job.


351

Explanation: An error detected during executionof SETPRT could not be attributed to invalidmacro instruction invocation or invalid controlblocks. This system completion code isaccompanied by message IEC918I. MessageIEC918I identifies the terminated task andexplains the return code in register 15.

Programmer Response: Make sure that theSETPRT macro instruction is correctly coded.Check for program errors that incorrectlymodify the parameter list and DCB duringexecution of SVC 81.


35F

Explanation: An address space becamenonswappable before it could be swapped outfor the SYSEVENT TRANSWAP. Theinitiator requested the TRANSWAP beforeattaching a nonswappable program or a V=Rjob step.

System Action: The initiator abnormallyterminates the job.

Programmer Response: Probable system error.Resubmit the job.


36D to 378

Problem Determination: Table I, items 1, 2, 4,5a, 18, and 29.

36D

Explanation: An error was detected incommunications between RMF and the SystemResources Manager while attempting toinitialize, collect, or reinitialize workloadactivity measurements.

System Action: All RMF measurementcollection is terminated. Reinstatement can beattempted and, if successful, RMF will continueunder the control of the original options. Ifreinstatement fails, RMF is terminated. Register15 contains the return code from the SystemResources Manager depending on the functionattempted by RMF:

Byte Attempted Function

0 N/A.

1 Reinitialization of workload activity measurementcollection after a change in the InstallationPerformance Specification (IPS).

2 Collection of workload activity measurements.

3 Initialization of workload activity measurements.


36F

Explanation: One of the following errorsoccurred during processing of a job entrysubsystem SVC 111:

• An invalid entry code was passed to SVC111.

• DEBCHK processing found that the DEB(data extent block) was invalid.

• The DEB was not a subsystem DEB.

System Action: The program issuing the SVCterminates.

Programmer Response: Be sure the program isauthorized to use SVC 111. Check that theSVC is issued at the correct point in theprogram. Correct the error, and rerun the job.

Problem Determination: Table I, items 5a, 16,29.

378

Explanation: The error occurred during theexecution of an RU or VRU form FREEMAINmacro instruction.

• A FREEMAIN for an entire subpool wasrequested (register 1 was zero) but thelength in register 0 was not set to zero.




• The SP parameter was specified correctly,but the boundaries of the storage area to befreed were not completely described by thedescriptor queue element (DQE).






ABEND

37A to 3FB

37A

Explanation: The error occurred during theexecution of an EVENTS macro instruction.The control program found that the EVENTStable specified on the EVENTS macro wascurrently being waited on.

Programmer Response: Make sure that only onetask at a time waits on the EVENTS table inquestion. Correct the error, and execute the jobstep again.


37D

Explanation: The error occurred duringexecution of an EVENTS macro instruction.The control program found that the EVENTStable specified on the EVENTS macro wascurrently being waited on.

Programmer Response: Make sure that only onetask at a time waits on the EVENTS table inquestion. Correct the error, and execute the jobstep again.


382

Explanation: The pre-processing orpost-processing installation-written exit routinecalled by RACF during RACHECK SVCprocessing passed back an invalid return code toRACF. The code was not part of the definedinterface.


Programmer Response: Possible user error.Register 15 contains the return code from theexit routine. Verify that the exit routine is usingvalid return codes.


383

Explanation: The pre-processing or-post-processing installation-written exit routinecalled by RACF during ACINIT SVCprocessing passed back an invalid return code toRACF. The code was not part of the definedinterface.




385

Explanation: The installation-written exitroutine called by RACF during RACDEF SVCprocessing passed back an invalid return code toRACF. The code was not part of the definedinterface.




3FB

Explanation: JES3 module IATSIAD could notobtain enough storage from subpool 230 tobuild a data set block (DSB) or from subpool241 to build a data set status block (DSS).

System Action: The system terminates the useraddress space.

Programmer Response: Rerun the job with aSYSABEND DD statement. The problem maynot recur. If it does, notify your systemprogrammer.


3FC to 402

3FC

Explanation: An error occurred duringexecution of the external first level interrupthandler. In an attempt to recover the system,the supervisory control program abnormallyterminated the task or SRB that took theexternal interrupt.



00 The first level interrupt handler (FLIH) detected(but does not support) a third recursion.

04 An error occurred during FLIH mainlineprocessing.

08 An error occurred during a first recursion.

0C An error occurred during a second recursion.

System Action: The system abnormallyterminates the active task and writes an errorrecord to SYS1.LOGREC.



400

Explanation: EXCP processing detected an errorwhile processing an I/O request; the DCB (datacontrol block) address in the DEB (data extentblock) is not the same as the DCB address inthe caller's IOB (input/output block). Thissituation can occur if the data set is not open orif the control blocks are prematurely freed oroverlaid.


Programmer Response: Verify that the data setwas opened and that the control blocks werehandled correctly in the problem program.Rerun the job.

In the abnormal termination dump, the TCBfield TCBEXCPD (at offset C0) points to theEXCP problem determination area. The itemsin the problem determination area of interestare:

• Offset 10 contains a copy of the registercontents present when EXCP processingdetected the error.




402

Explanation: The EVENTS POST macroinstruction routine encountered an error whileprocessing an extended format ECB (eventcontrol block). The control program found aninvalid EVENTS table address in the threelow-order bytes of the ECB.

The EVENTS table address is placed in theECB by the EVENTS macro instruction beforethe events associated with the ECB arecompleted. This address must remain in theECB until a POST macro instruction places acompletion code in the ECB.

Programmer Response: Make sure an EVENTSmacro was issued to construct an EVENTStable, and that an EVENTS macro was issued toinitialize the ECB in question. In addition,make sure that the contents of the ECB werenot modified after it was initialized as anextended format ECB and before the POSTmacro instruction was issued. Correct the error,and execute the jobstep again.

Problem Determination: Table I, items 1, 3, 5a,15, 19, and 29.


406 to 413

ABEND

406

Explanation: The error occurred duringexecution of a LINK, ATTACH, or XCTLmacro instruction.

The requested program was marked by thelinkage editor as only loadable. The programwas produced by a linkage editor execution forwhich the EXEC statement contained OL in thePARM parameter field.

Programmer Response: Rewrite the problemprogram so that it specifies only loading, butnot execution, of the only loadable program.Then recompile and execute the job step again.


40A

Explanation: The error was detected duringexecution of an R-form FREEMAIN macroinstruction:

• The macro instruction specified the releaseof all subpool zero storage. The entiresubpool zero cannot be released by problemprograms, that is, programs with storageprotection keys other than zero.

• An authorized program specified that all ofone of the following subpools was to befreed:

SQA

CSA

LSQA (subpool 254 or 255)

An invalid subpool (subpools 129 to228, 231, 232, 234, 235, 238 to 249)



Programmer Response: If you intended theFREEMAIN macro instruction to release

subpool zero, remove it from the program. Thecontrol program releases subpool zero when ajob step terminates. If you did not intend theFREEMAIN macro instruction to releasesubpool zero, check for program errors thatincorrectly modify the FREEMAIN macroexpansion.

Only subpools defined as eligible for subpoolFREEMAIN may be freed as an entire subpool.All other subpool storage areas must be freed byindividual requests explicitly describing the area.After making corrections, execute the job stepagain.


40D

Explanation: This completion code is foundonly in ASCBs. Because recursive errorsoccurred while trying to terminate a task, thesystem had to terminate the address space.

System Action: The RTM attempts to terminatethe address space. A dump may have beenwritten to the SYS 1. DUMP data set.

Programmer Response: Correct the originalerror.


413

Explanation: The error occurred duringexecution of an OPEN macro instruction for adata set on magnetic tape or on a direct accessdevice. This system completion code isaccompanied by message IEC145I. MessageIEC145I identifies the terminated task andexplains the return code (rc in the message text)in register 15.




414 to 435

414

Explanation: The error occurred duringexecution of a CLOSE macro instruction for adata set on a direct access device. This systemcompletion code is accompanied by messageIEC212I. Message IEC212I identifies theterminated task and explains the return code (rcin the message text) in register 15.



417

Explanation: The error occurred duringexecution of a BSAM CLOSE macro instructionwith a TYPE=T operand for a data set on adirect access device. This system completioncode is accompanied by message IEC221I.Message IEC221I identifies the terminated taskand explains the return code (rc in the messagetext) in register 15.



42A

Explanation: The error was detected duringexecution of an ATTACH macro instruction.

The ECB operand specified an invalid addressfor the event control block (ECB) to be postedwhen the subtask terminates. The address wasinvalid for one of the following reasons:

• It was not on a fullword boundary.

• The addressed virtual storage is notallocated, or the storage key does not matchthe protection key of the issuer of theATTACH.

Programmer Response: Change the ATTACHmacro instruction to specify the correct ECB,and ensure that the specification was not

incorrectly modified by the problem program.Recompile, and execute the job step again.


42D

Explanation: During execution of an overlayprogram, an error occurred while processing aSEGLD macro instruction.

Programmer Response: Check the subtaskcompletion code in the SEGLD ECB, which islocated at offset X'14' in the SEGTAB.Register 12 contains the address of theSEGTAB. After making corrections, executethe job step again.


430


The control program found that the parameterlist created from the macro instruction wasinvalid.

Programmer Response: Correct the DEQ macroinstruction specification or the program errorsthat incorrectly modified the parameter list.Recompile, and execute the job step again.


435

Explanation: SVC 53, which obtains andreleases exclusive control of a resourceassociated with a BDAM data set, found that:

• The DEB pointed to by the input DCB(DCBDEBAD) was not on any DEB chainassociated with the job step TCB, or did notpoint back to that DCB, or was not for aBDAM data set.

• The IOB has been altered by other than asystem routine.


ABEND

437 to 444

Programmer Response: Make sure that the inputDCB address is correct and that theDCBDEBAD field of the input DCB has notbeen overlaid.

Problem Determination: Table I, items 5b, 16,29.

437

Explanation: The error occurred at anend-of-volume. This system completion code isaccompanied by message IEC025I. Message

IEC025I identifies the terminated task andexplains the return code (rc in the message text)in register 15.



438


The control program found that the parameterlist created from the macro instruction wasinvalid.

Programmer Response: Correct the specificationof the macro instruction or the program errorsthat incorrectly modified the parameter list.Recompile, and execute the job step again.


43E

Explanation: The ECB address was not validwhen the task terminated. The ECB address isspecified with the ECB parameter in theATTACH macro instruction that created thetask.

System Action: The ECB is not posted. Thetask that originated the task with the invalid

ECB address is abnormally terminated. Theinvalid ECB address is contained in fieldTCBECB of the subtask's TCB.

Programmer Response: Determine if the areacontaining the ECB was freed before the subtaskcompleted processing. Correct the error and runthe job again.

Note: The ECB in question is specified at thetime of the ATTACH macro, and is checked forvalidity at that time. An invalid ECB atDETACH of the subtask or at the end-of-taskwould probably be caused by a FREEMAIN ofthe storage containing the ECB.

Problem Determination: Table I, items 5a, 16,19, 23, 29.

444

Explanation: The error occurred during theexecution of SYNADAF, where it wasdetermined that the DECB address was invalid.

Programmer Response: Register 15 contains theDECB address in error:

• For BDAM, BPAM, and BSAM, theDECB address should be passed toSYNADAF as the PARM2 operand on themacro instruction. For these accessmethods, the DECB address was in register0 on entry to the user's SYNAD routine.

• For BISAM, the IOBECBPT field of theIOB in error should contain the DECBaddress. Make sure that the PARM2operand in the SYNADAF macroinstruction (the address of the first sensebyte within the IOB) is correctly specified,and that the IOBECBPT has not beenoverlaid.

Correct the error, and rerun the job step.



451 to 478

451

Explanation: The error occurred during theexecution of SETPRT. Either the DCB whoseaddress was passed in the SETPRT parameterlist is invalid, the DEB address located throughthe DCB was invalid, the DCB EXIT LISTaddress located through the DEB was invalid, orthe IOBs located through the DCB are invalid.

This system completion code is accompanied bymessage IEC918I. Message IEC918I identifiesthe terminated task and explains the return codein register 15.


• For return code 01, make sure thatDCBEXLIST points to a valid exit list inyour region.

• For return code 02, make sure that theDCB fields DCBIOBAD and DCBIOBAhave not been overlaid since the DCB wasopened. Make sure that the IOB or ICBlink fields have not been overlaid.

• For return code 03, make sure that theDCB field DCBDEBAD has not beenoverlaid since the DCB was opened.

• For return code 04, make sure that theSETPRT macro instruction correctlyspecifies the address of an open DCB withinyour region.


45F

Explanation: Quiesce (SYSEVENT 18) failedwhile a TRANSWAP (SYSEVENT 14) orREQSWAP (SYSEVENT 43) was pending.Retry was not possible.

System Action: The system terminates theaddress space being swapped.

Programmer Response: Probable system error.Resubmit the job, or restart the terminatedfunction.

Problem Determination: Table I, items 1, 2, 4,5a, 18, and 29.

478

Explanation: The error was detected duringexecution of an RC or RU form FREEMAINmacro instruction:

• The macro instruction specified the releaseof all subpool zero storage. The entiresubpool zero cannot be released by problemprograms, that is, programs with storageprotection keys other than zero.

• An authorized program specified that all ofone of the following subpools was to befreed:

SQA

CSA

LSQA (subpool 254 or 255)

An invalid subpool (subpools 129 to228, 231, 232, 234, 235, 238 to 249)



Programmer Response: If you intended theFREEMAIN macro instruction to releasesubpool zero, remove it from the program. Thecontrol program releases subpool zero when ajob step terminates. If you did not intend theFREEMAIN macro instruction to releasesubpool zero, check for program errors thatincorrectly modify the FREEMAIN macroexpansion.

Only subpools defined as eligible for subpoolFREEMAIN may be freed as an entire subpool.All other subpool storage areas must be freed byindividual requests explicitly describing the area.After making corrections, execute the job stepagain.



47A to 482

ABEND

47A

Explanation: The error occurred duringexecution of an EVENTS macro instruction.The control program found that an incorrectnumber of entries was specified on the requestto create an EVENTS table. The number ofentries must be from 1 to 32,767.

Programmer Response: Make sure the numberof entries specified on the ENTRIES= operandof the EVENTS macro is from 1 to 32,767.


47D

Explanation: The error occurred duringexecution of an EVENTS macro instruction.The control program found that the addressspecified on the LAST= parameter of theEVENTS macro was incorrect.

The LAST specification must be an addressbetween the first and last valid entries in theEVENTS table in question.

Programmer Response: Make sure that theLAST address is for a valid table entry that hasnot been previously purged from the EVENTStable.


482

Explanation: While RACF was performingRACHECK SVC processing, the RACFmanager returned an invalid return code.


Programmer Response: Register 15 contains thehexadecimal return code from the RACFmanager:

ReturnCode Explanation

00 Successful operation.

04 RACF was unable to invoke the function. Ifregister 0 contains code 0, RACF was unable toestablish the ESTAE environment. If register 0contains code 1, the function code, which is in thethird byte of the parameter list, contains invaliddata.

08 The name to be added to the RACF data setalready exists.

0C The name does not exist.

14 No space was available on the RACF data set.

18 An input/output error occurred on the RACFdata set.

1C RACF is inactive; access to the RACF data set isdenied.

24 The input parameter list contains an error, asindicated by the code in register 0:

Code Error

1 Invalid entry name.2 Action specified for delete.3 Invalid field name.4 Test specified for rename request.7 Incorrect entry type.

2C The user work area is not large enough to hold allthe data.

30 The user work area is smaller than the minimumallowable size.

34 A test, which was not associated with action,failed.

38 RACF found a duplicate data set name, butVOLUME was not specified.

3C The VOLUME specified does not match a volumeentry in any data set profile.

40 User attempted to delete a restricted entry.

44 The ALTERI request was invalid.

48 The maximum number of index levels wasexceeded.

4C The index pointer chain was invalid.

50 The RACF data set has been used as input toutility ICHUT400 and was extended to a largercopy of itself. The input data set can no longer bemodified.



483 to 500

483

Explanation: While RACF was performingRACINIT SVC processing, the RACF managerreturned an invalid return code.


Programmer Response: Register 15 contains thereturn code from the RACF manager. Thiscode is given in completion code 482.


485

Explanation: While RACF was performingRACDEF SVC processing, the RACF managerreturned an invalid return code.


Programmer Response: Register 15 contains thereturn code from the RACF manager. Thiscode is given in completion code 482.


4FB

Explanation: One of the following errorsoccurred:

• JES3 could not obtain sufficient storagefrom subpool 241 for a SSISERV macrorequest.

• JES3 could not obtain sufficient storagefrom subpool 230 for user address spacebuffers.

• JES3 detected an error while processing therecord allocation block (RAB) refreshelement (RRE) for additional track groups.

System Action: The system terminates the useraddress space.

Programmer Response: Rerun the job with aSYSABEND DD statement. The problem maynot recur. If it does, notify your systemprogrammer.

Problem Determination: Table I, item 5A.

4FC

Explanation: An error occurred duringexecution of the program check first levelinterrupt handler. In an attempt to recover thesystem, the supervisory control programabnormally terminated the task that suffered theprogram check.




500

Explanation: EXCP processing detected an errorwhile handling an I/O request. Possible causesare:

• The IOB was incorrectly built or modified.

• Byte three of the UCB (unit control block)as specified in the UCB address field of aDEB (data extent block) did not contain

X'FF'.

• The index of an ISAM data set containederrors.


Programmer Response: Be sure your programcorrectly built or modified the lOB. If theprogram is correct, the problem is a systemproblem. Before calling the systemprogrammer, rerun the job, requesting anabnormal termination dump.

In the dump, the TCB field TCBEXCPD (atoffset C0) points to the EXCP problemdetermination area. The items in the problemdetermination area of interest are:

• Offset 10 contains a copy of the registercontents when EXCP processing detectedthe error.


ABEND

502 to 506


If the dump shows no errors, check the index ofthe ISAM data set. If the index contains errors,reorganize it.



502

Explanation: The error occurred duringexecution of a POST macro instruction. Thecontrol program found that the EVENTS tablespecified in the ECB had no available entries tocontain the posted ECB address.

Programmer Response: Make sure that theEVENTS table is large enough to containentries for all ECBs that can be posted to it.Correct the error, and execute the job stepagain.


504

Explanation: The error was detected duringexecution of a GETMAIN macro instructionthat requested allocation of one or more areasof virtual storage. The macro instructioncontained an LA operand (address of a list oflengths) and an A operand (address of a list ofbeginning addresses for the areas).

The length list and the address list occupiedoverlapping storage locations.

Message IEA700I 'accompanies this completioncode.


Programmer Response: Make sure that noprogram errors incorrectly modify the macro

expansion. After making corrections, executethe job step again.


505

Explanation: The error was detected duringexecution of a FREEMAIN macro instructionthat requested release of one or more areas ofvirtual storage. The macro instructioncontained an LA operand (address of a list oflengths) and an A operand (address of a list ofbeginning addresses for the areas).

The length list and the address list occupiedoverlapping storage locations.



Programmer Response: Make sure that noprogram errors incorrectly modify the macroexpansion. After making corrections, executethe job step again.


506

Explanation: The error occurred duringexecution of a LINK, LOAD, ATTACH, orXCTL macro instruction in an overlay program.

If the requested program had been loaded, notenough virtual storage would have remained forthe overlay supervisor.

Programmer Response: Reduce the size of theentire program or of the overlay segment. Ifthis is not possible, change the program from anoverlay program to a dynamically loadedprogram. Then recompile, and execute the jobstep again.

Problem Determination: Table I, items 1, 5a, 16,23, 29. Table II, format 1: trace option

-TRACE=SYS.


50D to 530

50D

Explanation: The program tried to use theOPEN, OPEN-J, CLOSE, CLOSE-T, EOV, orFEOV function while holding exclusive controlof the TIOT (task input/output table) resource.

Register 15 contains a code that identifies thefunction issuing the abnormal termination.

Code Function

00 OPEN04 OPEN-J08 CLOSE0C CLOSE-T10 EOV14 FEOV


Programmer Response: Correct the program sothat it releases control of the TIOT resourcebefore one of these functions is requested.Recompile, and execute the job step again.

513

Explanation: The error occurred duringexecution of an OPEN macro instruction for adata set on tape. This system completion codeis accompanied by message IEC146I. MessageIEC146I identifies the terminated task andexplains the return code (rc in the message text)in register 15.

Programmer Response: Respond as indicated formessage IEC 146I.


522

Explanation: All of the tasks in a job step werein an SVC wait state for the time specified inthe JWT parameter.

The event control block (ECB) specified in thewait request was never posted. This error couldbe the result of waiting on the wrong ECB ornot posting the correct ECB.

Programmer Response: Correct any errors, andexecute the job step again. If no errors arefound and the wait is expected for thatparticular job step, specify TIME=1440 on theEXEC statement to bypass all job step timing.

Problem Determination: Table I, items 7ab, 29.

52A

Explanation: The error occurred duringexecution of an ATTACH macro instruction.Although the STAI operand was not specified inthis macro instruction, it was specified for anantecedent task in the subtask queue for the jobstep. LSQA storage is too small to copy thenecessary STAI information for the subtaskspecified by this ATTACH macro instruction.

System Action: The subtask is not attached, andthe task that issued the ATTACH macroinstruction is abnormally terminated.

Programmer Response: Notify your systemprogrammer, and resubmit the job.

Problem Determination: Table I, items 1, 2, 5a,7a, 29. If the problem persists in a TSOenvironment, have the terminal sheet available.

530

Explanation: The error was detected duringexecution of a DEQ macro instruction.

A DEQ macro instruction was issued in anasynchronous exit routine for a resourcepreviously enqueued by another routine in thesame task. However, the task had not yetreceived control of the resource.

Programmer Response: Correct the program sothat the DEQ macro instruction is issued onlyafter the task has control of the resource. Ifpossible, avoid issuing the DEQ macroinstruction in the exit routine. Recompile, andexecute the job step again.



535 to 55F

ABEND

535

Explanation: SVC 53, which obtains andreleases exclusive control of a resourceassociated with a BDAM data set, issued aGETMAIN for storage to be used in itsprocessing and found that no storage wasavailable.

Programmer Response: Rerun the job. If theproblem continues, storage may have to be freedby others before the exclusive control function isused.


53E

Explanation: An error occurred duringend-of-task processing before an ECB for theterminating task could be posted, or before anend-of-task exit routine could be scheduled, orbefore it was determined that the task hadneither an ECB nor an end-of-task exit routine.

The task has an end-of-task ECB if the ECBparameter was specified on the ATTACH macroinstruction that created the task. The task hasan end-of-task exit routine if the EXTRparameter was specified on the ATTACHmacro.

System Action: The originating task for the taskthat suffered the error is abnormally terminated.

Programmer Response: Run the job again.


544

Explanation: During execution of SYNADAF,the IOB address was found to be invalid.

System Action: Register 15 contains the IOBaddress in error:

• For BDAM, BPAM, and BSAM,SYNADAF obtained the IOB address fromthe DECIOBPT field of the DECB; for

these access methods, the DECB addresswas passed to SYNADAF as the PARM2operand in the SYNADAF macroinstruction, and was contained in register 0on entry to the user's SYNAD routine.Verify that the PARM2 operand wascorrectly specified and that the DECIOBPTfield has not been overlaid.

• For QSAM, BISAM, and QISAM,SYNADAF received a pointer to the IOB asthe PARM2 operand in the SYNADAFmacro instruction. The address passed toSYNADAF should have been the addresscontained in register 0 on entry to the user'sSYNAD routine. Verify that the PARM2operand was coded correctly.

• For the EXCP access method, verify thatthe PARM1 operand of the SYNADAFmacro instruction specified the correct IOBaddress.

Programmer Response: Correct the error, andrerun the job step.


55F

Explanation: An error was encountered duringthe execution of the cross memory post SRBscheduled by swap out complete (SYSEVENT15). The post was to notify a REQSWAP orTRANSWAP issuer that either the swap had tobe turned around or the swap is complete.

System Action: Copy the current ASCB andOUCB into the dump buffer area in SQA (useof the buffer is mapped by SDMPBUFF inmodule IRARMSRV). Issue a SDUMP andterminate the address space that is waiting.

Programmer Response: Determine if a validECB address is being passed to the SYSEVENTTRANSWAP or REQSWAP. Resubmit thejob, or restart the terminated function.



56D to 582

56D

Explanation: SVC 109 with routing code X'11'in register 15 (the Sort SVC) was issued. One ofthe following errors exists:

• Some task other than Sort issued SVC 109with routing code X'11'. Only Sort isauthorized to issue it.

• The task that issued the SVC passed arecord that was not in the task's authorizedarea.

• The task passed a record that contained oneor more invalid fields.

• The task passed a DCB (data control block)pointer with an invalid DEB (data extentblock).


Programmer Response: If this ABEND occurredbecause some task other than Sort issued SVC109 with routing code X'11', correct the task.

If this ABEND occurred while Sort wasexecuting, a system error exists. Notify thesystem programmer.

Problem Determination: Table I, items 4, 5a, 16,and 29.

56F

Explanation: The error occurred duringend-of-job processing for a JES2 job that wasbeing processed by an execution batch monitor.The execution batch monitor pseudo job selectprocedure found that another task was holdingor waiting for a lock on the SJB (subsystem jobblock).

System Action: The system abnormallyterminates the job.

Programmer Response: Notify the systemprogrammer or installation manager.


57D

Explanation: The error occurred duringexecution of an EVENTS macro instruction.

The macro expansion contained an invalid eventcontrol block (ECB) address, or the programissuing the EVENTS macro instruction isrunning under a protection key (8 through 15)that is different from the storage protection keyof the ECB.

Programmer Response: Make sure that the ECBaddress specified is a valid virtual storageaddress and that it was not incorrectly modified.Also, be sure the ECB is initialized with thesame storage key as the protection key of theprogram issuing the EVENTS macroinstruction, or that the program is runningunder protection key 0 through 7. Correct theerror, and execute the job step again.


582

Explanation: RACF was not able to verify auser when called to perform RACHECK SVCprocessing.



ReasonCode Meaning

00 No access control environment (ACES) wasavailable to describe the user.




585 to 5FC

ABEND

585

Explanation: RACF was not able to verify auser when called to perform RACDEF SVCprocessing.




00 No access control environment (ACEE) wasavailable to describe the user.

04 No UCB was found to contain a volume serialthat matched the volume serial passed to RACF inthe RACDEF macro instruction for aTYPE=DEFINE operation.

08 ADDVOL function requested and user did nothave at least UPDATE authority to the data set.

0C ADDVOL function requested and (1) the volumeserial number is already defined (for DATASETclass), or (2) the new tape volume is alreadydefined (for TAPEVOL class).



5FB

Explanation: During execution of an MVS-JES3allocation subsystem interface routine, an erroroccurred; it is indicated by a hexadecimal reasoncode in register 15:


1 In common allocation, the number of devicesrequested by MVS does not equal the number tobe allocated by JES3. Register 3 contains thenumber requested by MVS; register 5 contains thenumber passed by JES3. Register 2 contains theaddress of the ddname.

2 During unallocation processing, JES3 cannotsuccessfully issue an ESTAE.

3 JES3 cannot obtain storage for a dynamicallocation buffer.

4 JES3 cannot obtain storage for a change ddnamebuffer.

5 ' JES3 cannot find in any address space header theaddress space ID (ASID) associated with therequest. Register 2 contains the address of the jobstep control block (JSCB); register 3 contains theASID.

6 A job summary table (JST) pointer error occurredduring common allocation or unallocation.

7 IATSICA cannot find an active MEMDATA entryfor the address space. Register 2 contains theaddress of the job step control block (JSCB);register 3 contains the address space ID (ASID) ofthe requesting address space; register 8 containsthe address of the MEMDATA header.

8 IATSIMS cannot find an active MEMDATAentry for the address space. Register 4 contains theaddress of the subsystem identification block(SSIB); register 6 contains field SSIBSUSE of theSSIB. However, both registers 4 and 6 may beinvalid.

9 JES3 found a duplicate volume. The volumecannot be loaded. Register 2 contains the addressof the SETUNIT; register 6 contains the addressof the job summary table (JST).

A The GETMAIN macro failed for a work area forthe subsystem interface (SSI) of the mass storagesystem (MSS). IATSIMS abnormally terminatesall MSS-related SSIs except mount equalization.

For codes 2, 3, 4, 6, and A, register 3 containsthe macro return code.

System Action: The system abnormallyterminates the affected task.

Problem Determination: Table I, items 1, 3, 5A,15, 16, 29.

5FC

Explanation: An error occurred duringexecution of the restart first level interrupthandler. In an attempt to recover the system,the supervisory control program abnormallyterminated the task that took the restartinterrupt.





604 to 614

604

Explanation: The error occurred duringexecution of a GETMAIN macro instruction:

• The address in the A or LA operandspecified a location outside the private areaassigned to the task or was not a multiple of4.

• The address of the parameter list for themacro instruction was erroneous. Thisaddress was in register 1.

• The parameter list, or the length list, orboth, were not valid for read access in theuser's key.



Programmer Response: Make sure that thelength list and address are aligned on wordboundaries, and that no program errorsincorrectly modify the parameter list. Aftermaking corrections, execute the job step again.


605

Explanation: The error occurred duringexecution of a FREEMAIN macro instruction:

• The address in the A or LA operandspecified a location outside the private areaassigned to the task or was not a multiple of4.

• The address of the parameter list for themacro instruction was erroneous. Thisaddress was in register 1.

• The parameter list, or the length list, orboth, were not valid for read access in theuser's key.



Programmer Response: Make sure that thelength list and address are aligned on wordboundaries, and that no program errorsincorrectly modify the parameter list. Aftermaking corrections, execute the job step again.


613

Explanation: The error occurred duringexecution of an OPEN macro instruction for adata set on magnetic tape. This systemcompletion code is accompanied by message




614

Explanation: The error occurred duringexecution of a CLOSE macro instruction for adata set on a direct access device. This systemcompletion code is accompanied by message





ABEND

622 to 638

622

Explanation: The system terminated initiation ofexecution of a task entered from a TSO terminalfor one of the following reasons:

1. The system encountered one of thefollowing errors while constructing controlblocks for TSO:

a. A multiple-step procedure was found.b. The prompting task terminated

abnormally.

2. The operator issued a MODIFYTCAM,TS=STOP command.

3. The terminal user signaled ATTN duringLOGON scheduling.

4. The user submitting the job disconnected histerminal from the system.

5. TCAM disconnected the terminal because ofan I/O error.

6. The terminal malfunctioned.

System Action: In cases 1 and 2, the systemissued terminal messages that describe the errorconditions.

Programmer Response: In the first case, respondto the terminal messages that accompany thistermination:

• For case 1a, specify a different procedure orconsult your system programmer. Attemptto execute the job again.

• For case 1b, consult your systemprogrammer.

In the second case, attempt to execute the jobagain when TSO is started.

In the third case, LOGON again; make surethat you do not signal ATTN inadvertently.

In the fourth case, attempt to execute the jobagain when the terminal is reconnected to thesystem.

In the fifth case, find the cause of the I/O error,correct the condition, and rerun the job.

In the sixth case, contact IBM for hardwaresupport.

Problem Determination: In all cases, have theterminal sheet available or record the currentdisplay on the graphics device before contactingIBM for programming support.

630

Explanation: An out-of-storage conditionoccurred during the execution of a DEQ macroinstruction.

Operator Response: Notify your systemprogrammer, and resubmit the job.


637

Explanation: The error occurred at anend-of-volume for a data set on magnetic tapeor an end-of-volume during concatenation. Thissystem completion code is accompanied bymessage IEC026I. Message IEC026I identifiesthe terminated task and explains the return code(rc in the message text) in register 15.


Problem Determination: Table I, items I , 3, 5a,15, 16, 29.

638

Explanation: An out-of-storage conditionoccurred during the execution of an ENQ macroinstruction.

Operator Response: Notify your systemprogrammer, and resubmit the job.



644 to 67A

644

Explanation: The error occurred during theexecution of SYNADAF, where it wasdetermined that the message buffer obtained inthe user's region had been modified or freed.

Programmer Response: Register 15 contains theaddress of the message buffer area. Make surethat your program does not modify or free thisarea until SYNADAF execution is complete.Correct the error, and rerun the job step.


67A

Explanation: An error occurred during theprocessing of an MSSFCALL SVC. Register 15contains a hexadecimal reason code:


01 IEAVMSF has found a storage protection errorfor one or more input parameters. One of thefollowing describes the error:

• The calling program is not in supervisor stateor PSW key 0 - 7, and one or more inputparameters do not match the caller's key.

• A buffer passed as input is less than 8 bytesor more than 2048 bytes long.

02 IEAVMSF has determined that the callingprogram is not in supervisor state or PSW key 0 -7, and requested a command other than a TPcommand. All commands except the TPcommands can be executed only by a supervisorstate, PSW key 0 - 7 caller.

03 One of the following describes the error:

• IEAVMSF has determined that the callingprogram is attempting to execute a TPcommand but does not have session control.The caller's address space must hold theENQ resourceMSFDC,SESSIONCONTROL.

• The ASID of a program requesting the TPport does not match the ASID of the currentTP port owner.

04 IEAVMSF has found that a calling program doinga branch entry tried to execute a TP command.

05 IEAVMSF has detected a possible overlay of theMSFCB or MSFAB control blocks.

06 IEAVMFIH has received control following anunexpected MSSF interrupt.

07 IEAVMFIH found invalid flags in the MSFCB.

08 IEAVMFIH found invalid flags in the MSFABwhile processing the MSFAB.

09 IEAVMFIH found invalid flags in the MSFABwhile processing the recovery disconnect block.

0A IEAVMSFS found invalid flags in the MSFCB.

0B IEAVMSFS found invalid flags in the MSFAB.

0C The caller of entry point IEAVMSF2 in moduleIEAVMSF requested an MSSF (maintenance andservice support facility) command other than code0071 read restart reason command.

0D The MSSF (maintenance and service facility) SLIH(second level interruption handler) detected invalidflag settings in the MSFKB (MSSFcommunications block).

System Action: For reason codes 01, 02, 03, 04,05, and 0C, the system abnormally terminatesthe task that issued the MSSFCALL SVC.

For reason codes 06, 07, 08, 09, 0A, 0B, and0D, the system records the error in

SYS1.LOGREC and attempts to recover.

For reason codes 07, 08, 09, 0A, 0B, and 0D,when the error occurs, the system puts theinvalid flags and the ASID into register 2 andthe TCB address into register 3. Check thecontents of these registers in SYS1.LOGRECand in the dump (if one is written) for thevalues at the time the error occurred. When itenters the recovery routine, the system recordsthe invalid flags, the ASID, and the TCBaddress in the SDWA variable work area. If thevalues in the SDWA work area are differentfrom the values in registers 2 and 3, it is becauseother system processing changed the valuesbetween the time the error occurred and thetime the system entered the recovery routine.

Programmer Response: For reason codes 01, 02,03, and 04, correct the problem, and rerun thejob. Reason codes 05, 07, 08, 09, 0A, 0B, 0C,and 0D indicate probable system errors.

Problem Determination: For reason code 06,Table 1, items 2, 18, 29, and 30. For reasoncodes 07, 08, 09, 0A, 0B, 0C, and 0D, Table I,items 2, 18, and 29.


ABEND

67D to 685

67D

Explanation: The error occurred duringexecution of an EVENT macro instruction.

The macro instruction specified an event controlblock (ECB) whose wait flag was already on.This indicated that a previous EVENTS orWAIT macro instruction was already waitingfor posting of the ECB.

Programmer Response: Change the problemprogram to eliminate a double wait on a singleevent. If no double wait is found, make surethat the ECB was not incorrectly modified bythe program. Then execute the job step again.


683

Explanation: The module calling RACINIT isnot authorized to use the SVC function. Toissue the RACINIT SVC with the NEWPASSkeyword, the calling module must be authorized(APF-authorized, in system key 0-7, or insupervisor state). To issue the RACINIT SVCwithout the NEWPASS keyword, the callingmodule must either be authorized(APF-authorized, in system key 0-7, or insupervisor state) or in the RACF-authorizedcaller table and fetched from an authorizedlibrary.


Programmer Response: Possible user error. IfNEWPASS was specified, verify that the callingmodule was executing in an authorized state. IfNEWPASS was not specified, verify that themodule name was entered in theRACF-authorized caller table and that thecalling module was link edited into anauthorized library.


684

Explanation: The module calling the RACFmanager or the RACLIST function is notauthorized to the SVC function. The modulecalling the RACF manager must be authorized(APF-authorized, in system key 0-7, or insupervisor state). The module calling theRACLIST function must either be authorized(APF-authorized, in system key 0-7, or insupervisor state) or in the RACF-authorizedcaller table and fetched from an authorizedlibrary.


Programmer Response: Possible user error. Ifthe RACF manager was called, verify that thecalling module was executing in an authorizedstate.

If the RACLIST function was called, verify thatthe module name was entered in theRACF-authorized caller table and that thecalling module was link edited into anauthorized library.


685

Explanation: The module calling RACDEF isnot authorized to use the SVC function. Toissue the RACDEF SVC, the calling modulemust be authorized (APF-authorized, in systemkey 0-7, or in supervisor state).


Programmer Response: Possible user error.Verify that the calling module was executing inan authorized state.



6FB

6FB

Explanation: During JES3 processing, moduleIATSSCM or IATSSRE detected an error andissued this system completion code. The error isidentified by a hexadecimal reason code in thehigh-order byte of register 15 and, for somereason codes, a hexadecimal return code in thelow-order byte of register 15.


00 The subsystem interface common service (SSICS)routine detected an error in its calling parametersor in the system status. Return codes are:

18 The caller of SSICS is not in systemprotection key 0 through 7.

1C The SYSID parameter in a SSISERVmacro specified a processor that is notdefined.

20 An invalid combination of the fieldsSELECBF, SELEXIT, SELBUFF wasfound in the IATYSEL control blockfor a WAIT or REPLY type SSISERVmacro request.

24 An error occurred when the SSICSroutine attempted to write a stagingarea.

28 The primary and all secondary stagingarea extents have been exhausted.

2C The service entrance list (SEL)contained an invalid MEMDATApointer.

30 The channel-to-channel adaptor (CTC)address is invalid.

34 An attempt was made to post a waitthat cannot be posted.

01 The IATXBGM or IATXBFM macro passed anerror return code back to JES3 moduleIATSSCM:

08 A GETMAIN or FREEMAIN failed.

02 The MVS FREECELL macro passed an errorreturn code back to JES3 module IATSSCM:

04 The cell was not allocated from thesubpool indicated by the specified cellpool ID.

08 The cell address is invalid.

0C FREECELL could not find the cellpool.

10 The cell pool ID was invalid.

03 The MVS BLDCPOOL macro passed an errorreturn code back to JES3 module IATSSCM:

04 GETMAIN failed.


0C The specified subpool was not global.

10 The cell size was greater than the poolsize.

14 BLDCPOOL found a DELETE subpoolin progress for the specified pool.

04 The MVS GETCELL macro passed an errorreturn code back to JES3 module IATSSCM:

04 GETCELL could not find any availablecells.

08 The chain pointers had been destroyed.

0C The cell pool format was invalid.


05 The JES3 subsystem interface read-end moduleIATSSRE failed to obtain storage; the storagewould have held a copy of a staging area destinedfor an FSS address space. The three low-orderbytes of register 15 contain the return code fromthe MVS GETMAIN service.

06 The JES3 subsystem interface read-end moduleIATSSRE could not find the FSID in the stagingarea; the FSID identifies the dynamic destinationqueue (DESTQ) for which the staging area isintended.

07 The JES3 subsystem interface read-end moduleIATSSRE could not find the proper control blockstructure required for queuing the staging area inan FSS address space.

11 A JES3 routine issued the IATXSSXM macro tocall a specific routine in module IATSSXM.IATSSXM returns in the low-order byte of register15 the ECODE parameter value from theIATXSSXM macro.

JES3 SPL: User Modifications and Macrosdescribes the IATXSSXM macro.

13 The system abnormally terminated JES3 duringstaging area initialization.

14 The system abnormally terminated JES3 duringprocessing to move a staging area to make it adedicated staging area.

15 The system abnormally terminated the processingfollowing an end of memory (EOM) or an end oftask (EOT) call.

16 The system abnormally terminated FREEMAINprocessing of the staging area wait queue (SAWQ).


6FC to 702

ABEND

17 The system abnormally terminated FREEMAINprocessing of the staging area pending queue (SAPQ).

18 The system abnormally terminated an attempt topage-fix the staging area pending queue (SAP Q).

19 The system abnormally terminated copying of thestaging area pending queue (SAP Q) from JES3auxiliary storage to the common service area(CSA).

1A Module IATSSCM detected an error, which mayhave caused another ABEND, during GETCELLprocessing for JES3 auxiliary storage.

1B Module IATSSCM detected an error duringvalidation of a staging area queue.

40 The passed staging area was not found on thestaging area queue.

System Action: The system writes the commonservice area (CSA), system queue area (SQA),and the MVS trace table to a SYS1.DUMP dataset and abnormally terminates the currentaddress space. If the address space is the JES3address space, the system does not write adump.

Problem Determination: Table III, items 4, 5, 6,20.

6FC

Explanation: An error has occurred while theprogram check first level interrupt handler wassetting up for a SPIE exit routine. In anattempt to recover the system, the supervisorcontrol program has abnormally terminated thetask that attempted the SPIE exit.




700

Explanation: A program check occurred duringEXCP processing of an I/O request. Theprogram check occurred in a supervisor serviceroutine called by EXCP.

System Action: The system abnormallyterminates the task and writes an error record toSYS1.LOGREC.

Programmer Response: Not a programmer error.Rerun the job requesting an abnormaltermination dump before calling the systemprogrammer.

For the system programmer, the problem isprobably in one of the several service routinesused by EXCP. In the abnormal terminationdump, the TCB field TCBEXCPD (at offset C0)points to the EXCP problem determinationarea. The items in the problem determinationarea of interest are:

• Offset 4 contains a copy of the programstatus word (PSW) for the service routine inwhich the program check occurred.

• Offset E contains the interruption codewhen the program check occurred.

• Offset 10 contains a copy of the registercontents when the program check occurred.

• Offset 54 contains the contents of therequest queue element (RQE), if allocated,when the program check occurred.



702

Explanation: An error occurred during anattempt to interface with one of the POSTservice routines. Either invalid input data or anunauthorized POST exit routine request wasencountered.

This code is associated only with extended ECBprocessing. If an extended ECB was beingposted, ensure that it contains valid data.



00 POST service routine IEAOPTOE encountered aninvalid function request.


704 to 713

04 POST service routine IEAOPTOE encountered adelete request for an exit not currently defined.

08 During an attempt to post an extended ECB, thedescriptor word of the ECB extension containedinvalid data.

0C During an attempt to post an extended ECB, theECB extension contained an invalid exit routineaddress.

10 A post of an extended ECB was attempted from aPOST exit routine.

14 During an attempt to post an extended ECB,either the ECB address or ECB extension addresswas invalid.

Programmer Response: Correct the error, andexecute the job step again.


704

Explanation: A system error, uncorrectablemachine error, or error that cannot bedetermined occurred during execution of aGETMAIN macro instruction.

System Action: The system abnormallyterminates the requesting task.

Programmer Response: Rerun the job. If theerror recurs, notify the system programmer orthe installation manager.

Problem Determination: Table I, items 1, 2, 3,5a, 16, 18, 29, or 30.

705

Explanation: A system error, uncorrectablemachine error, or error that cannot bedetermined occurred during execution of aFREEMAIN macro instruction.




706

Explanation: The error occurred duringexecution of a LINK, XCTL, ATTACH, orLOAD macro instruction.

The requested load module was marked by thelinkage editor as not executable.

Programmer Response: Correct the errors thatwere found by the linkage editor in the loadmodule, have the module edited by the linkageeditor again, recompile, and execute the job stepagain.


70A

Explanation: A system error, uncorrectablemachine error, or error that cannot bedetermined occurred during execution of anR-form GETMAIN or FREEMAIN macroinstruction.


Programmer Response: Execute the job again.If the error recurs, notify the systemprogrammer or the installation manager.


713

Explanation: The error occurred duringexecution of an OPEN macro instruction for adata set on tape or on a direct access device.This system completion code is accompanied bymessage IEC148I. Message IEC148I identifiesthe terminated task and explains the return code(rc in the message text) in register 15.


Problem Determination: Table I, items 1, 2, 3,5a, 15, 16, 29.


ABEND

714 to 737

714

Explanation: The error occurred duringexecution of a CLOSE macro instruction for adata set on tape. This system completion codeis accompanied by message IEC215I. MessageIEC215I identifies the terminated task andexplains the return code (rc in the message text)in register 15.



717

Explanation: The error occurred duringexecution of a BSAM CLOSE macro instructionwith a TYPE=T operand for a data set on tape.This system completion code is accompanied bymessage IEC222I. Message IEC222I identifiesthe terminated task and explains the return code(rc in the message text) in register 15.


Problem Determination: 1, 3, 5a, 15, 16, 29.

722

Explanation: One of the following output limitswas exceeded:

• The output limit specified by the OUTLIMkeyword on the SYSOUT DD statement.

• The job output limit specified in the LINESand CARDS parameters of the JES2JOBPARM statement.

• The job output limit specified in theBYTES, CARDS, LINES, and PAGESparameters on the STANDARDSinitialization statement or the JES3 MAINstatement.

Programmer Response: Probable user error.Check for input/output loops. Verify that theparameter value does not conflict with any

installation requirements; then, increase thevalue.

Problem Determination: Table I, items 5a, 7a,7b, 29.

72A

Explanation: During execution of an ATTACHmacro instruction, the system found an invalidparameter address.

Programmer Response: Correct the parameteraddresses, ensuring that they are valid virtualaddresses. Recompile, and execute the job stepagain.


730

Explanation: An unexpected error occurredduring execution of a DEQ macro instruction.

System Action: The system abnormallyterminates the task and records relatedinformation in SYS1.LOGREC.



737

Explanation: The error occurred at anend-of-volume or during allocation of asecondary quantity of direct access storage asrequested in the SPACE parameter of the DDstatement for the data set. This systemcompletion code is accompanied by messageIEC027I. Message IEC027I identifies theterminated task and explains the return code (rcin the message text) in register 15.


Problem Determination: If the data set doesexist on the specified volumes and the problemrecurs, see Table I, items 1, 3, 5a, 15, 16, 25b,29.


738 to 800

738

Explanation: An unexpected error occurredduring execution of an ENQ macro instruction.

System Action: The system abnormallyterminates the task and records relatedinformation in SYS1.LOGREC.



744

Explanation: A program check occurred duringthe execution of SYNADAF or SYNADRLS.This error could not be attributed to invaliduser input.

System Action: The SYNADAF recoveryroutine tried to write a dump of LSQA and theuser's region. The dump header includes the jobname, step name, and procedure step name. Seemessage IEC907I to determine whether thedump was successfully written. A software errorrecord was written to SYS1.LOGREC.

Programmer Response: Rerun the job step.


778

Explanation: A system error, uncorrectablemachine error, or error that cannot bedetermined occurred during execution of an RCor RU form GETMAIN or FREEMAIN macroinstruction.




77D

Explanation: The error occurred duringexecution of an EVENTS macro instruction.The control program found that the inputparameter flags contained an invalidcombination.

Programmer Response: Verify the EVENTSmacro input parameters and the contents ofregister 0 when the EVENTS service routine wasinvoked.


7FB

Explanation: An uncorrectable error occurredduring execution of the MVS-JES3 dynamicdevice reconfiguration (DDR) subsysteminterface (SSI) routines.

System Action: The system terminates thereconfiguration.

Operator Response: If you initiated thereconfiguration, retry it. If the system initiatedthe reconfiguration, notify the systemprogrammer.


800

Explanation: EXCP (execute channel program)processing encountered one of the followingerrors while processing an I/O request:

• If SVC 0 (EXCP) was issued, an erroroccurred during page-fix processing.

• If SVC 114 (EXCPVR) was issued, an erroroccurred in either the page-fix or page-unfixprocessing.

• The IDA bit was set to one in a virtualchannel program (detected in moduleIECVTCCW).


804 to 806

ABEND

804

Explanation: The error occurred during theexecution of an EU, LU, or VU formGETMAIN macro instruction:

• More virtual storage was requested thanwas available.

• A negative length was specified (EU or VUform only).



Programmer Response: Make sure that noprogram errors incorrectly modify the macroexpansion. If necessary, change the program torequest more storage for the job. Then executethe job step again.


806

Explanation: An error occurred duringexecution of a LINK, XCTL, ATTACH, orLOAD macro instruction, in which the EP orEPLOC operand was specified. The error wasdetected by the control program routine for theBLDL macro instruction.



00 The LOAD macro instruction was issued with theADDR=parameter, or the LSEARCH=YESparameter, but the specified module could not befound.

04 The program whose entry point was specified inthe EP or EPLOC operand was not found in theindicated library (private library, job library, orlink library). This situation can occur when theLOAD macro instruction includes the ADDR

=parameter but does not include the DCBparameter.

08 An uncorrectable input/output error occurredwhen the BLDL control program routineattempted to search the directory of the librarythat contained the program whose entry point wasspecified in the EP or EPLOC operand. This can


80A to 82A

occur if the specified library is an uninitializedpartitioned data set.

An invalid data extent block (DEB) has beendetected by the BLDL control program. The DEBwas built in other than storage protection key 0-7.

0C An SVC routine required by the system could notbe found in the link pack area.

10 The supervisor found that the data control block(DCB) for the library, used by the BLDL controlprogram routine to locate the requested module,was not open or was not valid.

Programmer Response: If register 15 contains aX'04', it is a probable user error. Make surethat the requesting program was not incorrectlymodified. Make sure that the source library wasindicated correctly and that the indicated librarydoes contain the requested program. Correctthe error, and execute the job step again.

If register 15 contains X'0C', report thiscompletion code to the system programmer.

If register 15 contains a X'10', it is a probableuser error. Make sure that the DCB for thelibrary is valid and open. Correct the error, andexecute the job step again.

Problem Determination: Table I, items 1, 5a, 16,23, 25c, 29. If register 15 contains a X'08', seeTable II, format 1: trace option - TRACE=IO.

80A

Explanation: The error occurred duringexecution of an R-form GETMAIN macroinstruction:


• A negative length was specified.



Programmer Response: Make sure that noprogram errors incorrectly modify the macroexpansion. If necessary, change the program torequest less virtual storage. Then execute thejob step again.


813




822

Explanation: A region required to run the stepcould not be obtained.

System Action: Message IEF085I or IEF186I iswritten to the programmer, depending uponwhether the job was an ordinary job or adeferred checkpoint restart.

Programmer Response: Respond as indicated forthe message.

Problem Determination: Table I, items 1, 2, 3,7a, 29.

82A

Explanation: An invalid subpool ID wasspecified by an authorized task with theNSHSPV or the NSHSPL parameter on theATTACH macro instruction. An authorizedtask is in storage protection 0-7, supervisorstate, or APF-authorized.

System Action: The new subtask is not created.The system abnormally terminates the task thatissued the ATTACH macro instruction.

Programmer Response: Change the invalidparameter (only subpool 236 or 237 may bespecified with the NSHSPV or the NSHSPLparameter).


837 to 8FB

ABEND


837

Explanation: The error occurred at anend-of-volume for a sequential data set. Thissystem completion code is accompanied bymessage IEC028I. Message IEC028I identifiesthe terminated task and explains the return code(rc in the message text) in register 15.



838

Explanation: An ENQ macro instruction requestwas denied due to serious damage of theENQ/DEQ control blocks.


Programmer Response: Resubmit the job afterthe system has been reinstated.


878

Explanation: The error occurred duringexecution of an RC or RU form GETMAINmacro instruction:


• A negative length was specified.



Programmer Response: Make sure that theprogram correctly modifies the macroexpansion. If necessary, change the program to

request less storage. Then execute the job stepagain.


87D

Explanation: The error occurred duringexecution of an EVENTS macro instruction.The control program found that the EVENTStable specified in the event control block (ECB)had no available entries to contain the postedECB address.

Programmer Response: Make sure that theEVENTS table is large enough to containentries for all ECBs that can be posted to it.Correct the error, and execute the job stepagain.


8FB

Explanation: An uncorrectable error occurredduring execution of an interpreter DSP-relatedfunction. One of the following failed: theconverter/interpreter (CI) subtask under controlof the DSP, the dynamic support program(DSP) itself, or the JES3 interface (moduleIATIIII) creating the system work area (SWA).Register 15 contains a hexadecimal reason code:


05 An error occurred in the SWA-create interface(module IATIIII), indicating a problem reading ormapping SWA control blocks. Register 9 points tothe interpreter work area (IIW).

06 An error occurred in a JES3 user spool accessmethod (USAM) POINT or WRITE operation foran interpreter subtask.

07 During initialization of the data set status block(DSS) or the data set block (DSB), theconverter/interpreter found that the DSS or DSBwas invalid.

08 An error has occurred in JES3 user spool accessmethod (USAM) buffer initialization for aninterpreter subtask.

09 Module IATIICX found too many JCLstatements; a JCL statement count overflowoccurred.


905 to 913

15 The reader/interpreter passed an invalid returncode back to JES3. The system writes a dump toSYS1.DUMP and detaches the current task.

System Action: The system terminates the joband continues other processing.

Operator Response: Notify your systemprogrammer. Save all associated print output.

Programmer Response: Supply the systemprogrammer with the dump, a listing of the JCLfor the job, a listing of the JCL for JES3, andthe JES3 initialization statements. For a returncode of 5, rerun the job with theDEBUG=ALL option after a //* PROCESS CIJECL statement.

Problem Determination: Table I, item 3. TableIII, items 1, 4, 5, 7, 14a (only for return code 5),20.

905

Explanation: The error occurred during theexecution of a FREEMAIN macro instruction.The address of the storage area to be released isnot on a doubleword boundary.



Programmer Response: Make sure that noprogram errors incorrectly modify the macroexpansion. If necessary, change the program torequest less storage. Then execute the job again.


906

Explanation: The error occurred duringexecution of a LINK, LOAD, XCTL, andATTACH. Either the maximum use count hasbeen exceeded, or the maximum use count andthe maximum responsibility count have bothbeen exceeded. This count is '7FFF' for

OS/VS2, Release 3.7.


Programmer Response: Check for programerrors, such as endless loops, that cause macroinstructions to be executed too often. Makecorrections, recompile, and execute the job stepagain.


90A


The address of the storage area to be releasedwas not on a doubleword boundary.



Programmer Response: Make sure that noprogram errors incorrectly modify the address ofthe virtual storage area to be released. Thenexecute the job again.


913

Explanation: The error occurred duringexecution of an OPEN macro instruction. Thissystem completion code is accompanied bymessage IEC150I. Message IEC150I identifiesthe terminated task and explains the return codein register 15.

Programmer Response: Respond as indicated inmessage IEC150I.


SCC - 120 OS/VS Message Library: VS2 System Codes

922 to 938

ABEND

922

Explanation: With the initiator in control, anABEND, program check, depression of theRESTART key, or machine check took place.The system terminates the job being processedat the time.

System Action: The system writes a recorddescribing the error to SYS1.LOGREC, unlessthe ABEND was an OPEN failure, and writes adump to SYS1.DUMP, when applicable.


Problem Determination: Table I, items 1, 2, 3,7a, 16, 18, 29.

92A

Explanation: During execution of an ATTACHmacro instruction, an environmental erroroccurred; the error was not the result of anyaction on the part of the current task. Register15 contains a hexadecimal reason code:


00 An error occurred in the ESTAE SVC issued toestablish a recovery environment for ATTACHprocessing.

04 Storage in subpool 255 was not available for thenew SVRB, SPQEs, and parameter save area.

08 An error occurred in SVC 60 (STAI/ESTAI)issued to propagate STAI/ESTAI SCBs from thecurrent TCB to the new TCB, and to build a newSCB if STAI or ESTAI was specified in theATTACH macro instruction. The SVC 60 issuedwas a STAI entry if the STAI keyword wasspecified in the ATTACH macro instruction;otherwise, it is an ESTAI entry.

0C An error occurred when SETLOCK was enteredto obtain the local lock.

10 An error occurred when SETLOCK was enteredto release the local lock.

System Action: The new subtask is not created.The system abnormally terminates the task thatissued the ATTACH macro instruction.

Operator Response: Run the job again.


930

Explanation: The job issued a DEQ macroinstruction that included the TCB operand, butthe TCB operand identified a task that was inthe process of terminating.


Programmer Response: Determine why the taskidentified in the TCB operand was terminated.Correct that error, and resubmit the job.


937

Explanation: The error occurred at anend-of-volume for a checkpoint data set or aRACF-protected data set. This systemcompletion code is accompanied by message



Problem Determination: Table I, items 1, 3, 4,5a, 29.

938

Explanation: The job issued an ENQ macroinstruction that included the TCB operand, butthe TCB operand identified a task that was inthe process of terminating.


Programmer Response: Determine why the taskidentified in the TCB operand was terminated.Correct that error, and resubmit the job.



978 to A03

978

Explanation: The error occurred during theexecution of an RC or RU form FREEMAINmacro instruction. The address of the storagearea to be released is not on a doublewordboundary.



Programmer Response: Make sure that noprogram errors incorrectly modify the addressspecified for the storage area to be released.


9FB

Explanation: JES3 output service moduleIATOSDR or IATOSPS abnormally terminatedan MVS service routine, usually SETPRT, inorder to process a JES writer function or anoperator command. This completion code doesnot indicate a program failure.


A00

Explanation: During EXCP processing of anI/O request, a program check occurred in an

appendage called by EXCP.


Programmer Response: Probably not aprogrammer error unless you are using EXCPfor I/O operations. Rerun the job, requestingan abnormal termination dump before callingthe system programmer.

In the dump, the TCB field TCBEXCPD (atoffset C0) points to the EXCP-provided

debugging area. The items in the debuggingarea of interest are:

• Offset 2 contains a flag byte indicatingwhich appendage was active when theprogram check occurred. The bit pattern isas follows:

1... .... Error in SVC portion of EXCP.1.. .... Error in SRB portion of EXCP..1. .... Error in PCI appendage...1 .... Error in CHE appendage.... 1... Error in ABE appendage.... .1.. Error in EOE appendage.... ..1. Error in PGFX appendage.... ...1 Appendage is active........ Error in SIO appendage

• Offset 4 contains a copy of the programstatus word (PSW) before RTM wasentered, giving the location in theappendage where the error occurred.

• Offset E contains the interruption code.

• Offset 10 contains a copy of the registercontents when EXCP processing issued theABEND macro instruction.

• Offset 54 contains the contents of therequest queue element (RQE) for the I/Orequest being processed.



A03

Explanation: The error occurred when a taskattempted to terminate normally with aRETURN macro instruction or a branch to thereturn address in register 14. The task hadinitiated one or more subtasks that had notterminated.

Programmer Response: Change the program sothat, before termination of the task, all itssubtasks will terminate. A task can determinethat its subtasks have terminated by specifyingECB operands in the ATTACH macroinstructions used to initiate the subtasks andthen issuing WAIT macro instruction(s) thatspecify the event control blocks (ECB)representing the subtask terminations.


A05 to A0A

ABEND

If WAIT macro instruction(s) had been issuedand had indicated that all subtasks hadterminated, check for program errors thatincorrectly modified the WAIT macroinstructions or ECBs.

Make corrections, recompile, and execute thejob step again.


A05


• The control program found that the addressand length specifications in the releaserequest defined an area to be freed thatoverlapped a free area in virtual storage.Specifications for free areas are contained inthe free area queue, which is composed ofqueue elements defining each free area.

• Part of the area being freed is still fixed inreal storage. Fixed storage blocks cannotbe freed.



Programmer Response: Make sure the addressor length of the storage that the FREEMAIN issupposed to free is not incorrectly specified ormodified. Also, for any storage that aGETMAIN macro instruction obtains and aprogram subsequently fixes, a PGFREE must beissued before it can be released by aFREEMAIN macro instruction. Probably thestorage is still being used by an authorizedfunction and should not be freed at that time.

Correct the error, and execute the job again.


A06

Explanation: The error was detected duringexecution of either a LINK, LOAD, XCTL orATTACH macro instruction.

An RB (request block) is requesting a seriallyreusable program. However, another RBassociated with the same task as the first RB isrequesting the same serially reusable program,and the request has not yet been satisfied.

Programmer Response: Change the program towait until the serially reusable load module isexecuted before issuing the LINK, LOAD,XCTL or ATTACH macro instruction for theload module. Make corrections, recompile, andexecute the job step again.


A0A





System Action: The system abnormallyterminates the task. If the FREEMAIN macroinstruction represents a FREEPART request,the system terminates the current address space.

Programmer Response: Make sure the addressor length of the storage that the FREEMAIN issupposed to free is not incorrectly specified ormodified. Also, for any storage that aGETMAIN macro instruction obtains and aprogram subsequently fixes, a PGFREE must be


A13 to A37

issued before it can be released by aFREEMAIN macro instruction. Probably thestorage is still being used by an authorizedfunction and should not be freed at that time.



A13




A14

Explanation: The error occurred duringexecution of a CLOSE macro instruction for adata set on a direct access device. This systemcompletion code is accompanied by messageIEC216I. Message IEC216I identifies theterminated task and explains the return code (rcin the message text) in register 15.



A22

Explanation: The operator entered the FORCEcommand for the job, possibly for one of thefollowing reasons:

• The job may have been forced if CANCELwas unable to remove the job.

• The job may have been canceled to correcta system interlock condition (for example,where two tasks were enqueued on aresource without an intervening dequeue).

• The job may have been canceled if aninstallation-established procedure wasviolated.

The program may contain no errors.

System Action: The system terminates theaddress space and all tasks running in theaddress space.

Programmer Response: Find out why theoperator canceled the job. Make any necessarycorrections. Rerun the job, ensuring that theoperator enters the command CANCELjjj,DUMP, if necessary.

Problem Determination: Table I, items 1, 2, 3, 4,5a, 7d, 13, 16, 18, 23, 29.

A23

Explanation: During execution of an XMPOSTmacro instruction issued by the communicationstask, the ECB address specified was found to beinvalid.

Operator Response: Probable system error.Re-IPL the system, and run the job again.


A37

Explanation: The error occurred duringend-of-volume processing. This systemcompletion code is accompanied by messageIEC015I. Message IEC015I identifies theterminated task and explains the return code (rcin the message text) in register 15.



SCC- 124 OS/VS Message Library: VS2 System Codes

A78 to B00

ABEND

A78

Explanation: The error occurred during theexecution of an RC or RU form FREEMAINmacro instruction.





Programmer Response: Make sure the addressor length of the storage that the FREEMAIN issupposed to free is not incorrectly specified ormodified. Also, for any storage that aGETMAIN macro instruction obtains and aprogram subsequently fixes, a PGFREE must beissued before it can be released by aFREEMAIN macro instruction. Probably thestorage is still being used by an authorizedfunction and should not be freed at that time.



AFB

Explanation: While JES3 dynamic supportprogram (DSP) for systems network architecture(SNA) remote job processing (RJP) wasexecuting as a JES3 subtask or under an SRB, aJES3 module IATSNDA, IATSNDE,IATSNDM, IATSNDR, IATSNDT,IATSNDU, or IATSNDV attempted to reuse astill-active request parameter list (RPL).

System Action: The system cancels the sessionassociated with the RPL and writes a dump.

The system continues processing all othersessions, including those associated with thesame work station.

Programmer Response: Analyze the dump todetermine which RPL was about to be overlaidand what data was about to be sent or received.

B00

Explanation: During EXCP processing of anI/O request, a program check occurred in anEXCP procedure.


Programmer Response: Normally not a programerror. Rerun the job requesting an abnormaltermination dump before notifying the systemprogrammer.

In the dump, the TCB field TCBEXCPD (atoffset C0) points to the EXCP debugging area.

The items in the debugging area of interest are:

• Offset 2 contains a flag byte indicatingwhere the error occurred. The bit pattern isas follows:

1... .... Error in SVC portion of EXCP.1.. .... Error in SRB portion of EXCP..1. .... Error in PCI appendage...1 .... Error in CHE appendage.... 1... Error in ABE appendage.... .1.. Error in EOE appendage.... ..1. Error in PGFX appendage.... ...1 Appendage is active........ Error in SIO appendage

• Offset 4 contains a copy of the programstatus word (PSW) before RTM wasentered.

• Offset E contains the interruption code.

• Offset 10 contains a copy of the registercontents at the time of the error.

• Offset 50 contains the translation exceptionaddress, if applicable.

• Offset 54 contains the contents of therequest queue element (RQE) for the I/Orequest being processed, if allocated.


B04 to B0A

• Offset 80 is the start of the 160-byte blocksinvolved in the I/O request, if allocated.



B04

Explanation: The error occurred duringexecution of a GETMAIN macro instruction:

• A subpool number greater than 127 wasspecified by a problem program, which isnot authorized to use subpool numbersgreater than 127.

• An authorized program requested an invalidsubpool.



Programmer Response: Make sure that therequest was specified correctly and not modifiedincorrectly.

Problem Determination: Table I, items 1, 5a, 16,23, 29

B05








B06

Explanation: During input/output activity, asystem error task operating for a user task wasabnormally terminating. Rather than have thesystem error task fail, the supervisor reinstatedthe error task and abnormally terminated theuser task.

Programmer Response: Retry the task.


B0A

Explanation: The error occurred duringexecution of an R-form GETMAIN orFREEMAIN macro instruction:








ABEND

B13 to B78

B13

Explanation: The error occurred duringexecution of an OPEN macro instruction for adata set on a 1403 printer that has the universalcharacter set (UCS) special feature. This systemcompletion code is accompanied by messageIEC152I. Message IEC152I identifies theterminated task and explains the return code (rcin the message text) in register 15.

Programmer Response: Respond as indicated formessage IEC1521.


B14

Explanation: The error occurred duringexecution of a CLOSE macro instruction for apartitioned data set opened for output to amember. This system completion code isaccompanied by message IEC217I. MessageIEC217I identifies the terminated task andexplains the return code (rc in the message text)in register 15.



B23

Explanation: The task issued a WTOR(write-to-operator with reply) request that wasstill unanswered when a communications taskABEND occurred.

System Action: The task issuing the WTOR isscheduled for termination.

Operator Response: Probable system error.Follow the Operator Response instructions formessage IEE824A or IEE824E, which is issuedwhen the communications task terminated.Then, if the task issuing the WTOR requestterminated, restart the task.


B2D

Explanation: During execution of a FETCHESTAE routine for an overlay program, aprogram check occurred while FETCHprocessing attempted to load a segment of theoverlay program.

Programmer Response: Check the linkage editorinput to be sure the overlay program is specifiedcorrectly.


B37

Explanation: The error was detected by theend-of-volume routine. This system completioncode is accompanied by message IEC030I.Message IEC030I identifies the terminated taskand explains the return code (rc in the messagetext) in register 15.



B78

Explanation: The error occurred duringexecution of an RC or RU form GETMAIN orFREEMAIN macro instruction:



Message IEA700I accompanies this message.


Programmer Response: Make sure that therequest was specified correctly and was notmodified incorrectly.


BFB to C03

Problem Determination: Table I, items 1, 5a, 16, 23, and 29.

BFB

Explanation: During JES3 abnormaltermination recovery processing, JES3 wasunable to invalidate the- spool space allocationcheckpoint record (PTC). The invalidation faileddue to an error in the checkpoint access methodor an unrecoverable I/O error in the checkpointdata set(s).

Message IAT6352 accompanies this completioncode. JES3 could not invalidate the spool spaceallocation checkpoint record (PTC) during JES3abnormal termination recovery processing.

When message IAT1025 accompanies thiscompletion code, JES3 could not invalidate theonly copy or both copies of a partition trackallocation table (PTAT) during JES3initialization or after JES3 failsoft processing.

System Action: After issuing the message, JES3terminates. IAT6352 contains the checkpointaccess method return code, which identifies theerror.

If message IAT1025 appears, the system writesan error record to SYS1.LOGREC.

Programmer Response: Using message IAT6352,analyze the return code and correct the error,then restart JES3.

For message IAT1025, analyze the error recordin SYS1.LOGREC and the accompanyingmessages. In case the error is caused by a badtrack, assign another track to the checkpointdata set and restart JES3 with a warm start.Otherwise, reallocate the checkpoint data setand perform a cold start.

Problem Determination: Table III, item 3.

C03

Explanation: The error occurred when a taskattempted to terminate normally with a

RETURN macro instruction or a branch to thereturn address in register 14. The task hadopened one or more data sets that had not beenclosed.

The control program received a nonzero returncode from the Data Management ResourceManager, TASK CLOSE, indicating one of thefollowing:

• A subroutine called by TASK CLOSEreturned a nonzero return code to TASKCLOSE.

• TASK CLOSE could not successfully closeone or more data sets still open attermination because a previous error orABEND had been ignored by a STAEroutine or a DCB ABEND exit routine (forexample, D37 ABEND).

• TASK CLOSE could not successfully closeone or more of the task's data sets that werestill open at termination, because the datacontrol block (DCB) for the data set hadbeen invalidly modified. Examples of howthe DCB could be invalidly modified are:

— A program containing an open DCBissued an XCTL macro instruction.

— A program freed virtual storage thatcontained an open DCB.

— The system program modified the DCBincorrectly.

Message IEC999I, giving the address of theDEB that could not be properly closed, mayaccompany this completion code.

Programmer Response: Correct the programerror that incorrectly modified the data controlblock. Make corrections, recompile, andexecute the job step again.



ABEND

C0D to C22

C0D

Explanation: A routine has found a conditionthat should not occur. For example, an invalidreturn code has been returned. This abnormaltermination code may be used for entry into arecovery routine that will attempt retry.

Use the SYS 1.LOGREC error record to obtainthe names of the module and CSECT thatfailed.

If the routine is part of Real StorageManagement or Auxiliary Storage Management,a reason code is provided that describes theerror. See OS/VS2 System ProgrammingLibrary: MVS Diagnostic Techniques for thereason codes and their meanings.

If the failing routine is part of the SVC Dumpfunction of the Recovery Termination Manager,one of the following has occurred:

• For CSECT IEAVTSDT, an invalid post orresume of the dump was detected.

• For CSECT IEAVTSDH, an unsupporteddump data set was detected after IPL.

• For module IECVSMGR, one of thefollowing has occurred:

— If register 7 contains X'F1F6F0C2'(160B in EBCDIC), a get request for a160 byte block has failed. Register 11contains the address of the 160-byteblock.

— If register 9 contains X'F1F6F0C2'(160B in EBCDIC), a free request for a160-byte block has failed. Register 11contains the address of the 160-byteblock.

— If register 7 contains X'F4F040C2' (40B in EBCDIC, a get request or a freerequest for a 40-byte block has failed.Register 11 contains the address of the40-byte block.

— If register 7 does not containX'F1F6F0C2' or X'F4F040C2' and

register 9 does not containX'F1F6F0C2' (that is, if none of the

three possibilities listed previously formodule IECVSMGR is true), a getrequest or a free request for a smallblock has failed. Register 11 containsthe address of the small block.

System Action: The system writes a softwareerror record to the SYS1.LOGREC data setand/or writes a dump.



C13

Explanation: The error occurred duringexecution of an OPEN macro instruction for aconcatenated partitioned data set or a graphicdevice. This system completion code isaccompanied by message IEC153I or, forgraphics, message IEC157I. Message IEC153Ior IEC157I identifies the terminated task andexplains the return code (rc in the message text)in register 15.

Programmer Response: Respond as indicated formessage IEC153I or IEC157I.


C22

Explanation: The EXCP processor found thatthe maximum number of outstandingEXCP/EXCPVR macro requests allowed for theaddress space has been exceeded. Themaximum number allowed is defined in fieldASCBXCNT, which has been initialized fromfield CVTXCPCT.

System Action: The system terminates the jobstep.

Programmer Response: Check the job for a loopthat could result in EXCP/EXCPVR macrosbeing repeatedly issued without interveningWAIT macros.



C2D to D05

C2D

Explanation: The error occurred duringexecution of an overlay program. Programfetch was unable to get enough storage for themodule or control blocks.

Programmer Response: Increase the region sizeand execute the job step again.

Problem Determination: Table I, items 1, 5a, 9b,29.

C37

Explanation: The error occurred when an inputoperation was requested. The data set was on adirect access device. This system completioncode is accompanied by message IEC033I.Message IEC033I identifies the terminated taskand explains the return code (rc in the messagetext) in register 15.


Problem Determination: Table I, items 1, 5a, 13,25a, 29.

CFB


• During JES3 initialization, JES3 could notattach the JES3 auxiliary task, moduleIATAUX. ATTACH processing writesmessage IAT3005 to the console.

• After JES3 initialization, the JES3 auxiliarytask, module IATAUX, could not recoverfrom an error and abnormally terminated.The ESTAI routine in module IATABMNrequests a dump of module IATAUX to theSYSABEND or SYSUDUMP data set.

System Action: JES3 terminates.

Programmer Response: If JES3 wrote messageIAT3005 to the console, make sure that moduleIATAUX is in one of the following:

• The library concatenation defined by theJES3LIB initialization statements, if used.

• The STEPLIB concatenation defined in theJES3 procedure.

• The linklist specified in response to messageIEA101A.

If JES3 did not write message IAT3005, look inthe dump of module IATAUX to find thesystem completion code for the module's failure.Respond to that completion code.

Problem Determination: If module IATAUXcould not be attached, see Table I, items 2, 5a,7c, 13, 16, and Table III, items 2, 6, 21.

If module IATAUX abnormally terminated, seeTable I, items 2, 5a, 13, 16.

D05

Explanation: The error occurred duringexecution of a FREEMAIN macro instruction.A task invoked a system function which, inturn, issued a FREEMAIN macro instruction.However, the FREEMAIN macro instructionattempted to free a local system queue areastorage that was not owned by the task. Forexample, a task issues a CLOSE macroinstruction for a data set that it does not own.During execution of the CLOSE macroinstruction, a FREEMAIN macro instruction isissued.



Programmer Response: Change the program tomake sure that requests for system functions donot result in an invalid FREEMAIN macroinstruction being issued; then, rerun the job.



D06 to D14

ABEND

D06

Explanation: A program issued the LOADmacro instruction for a module. The macroinstruction included some form of the GLOBALparameter. However, within the same job steptask structure, a TCB (task control block)already loaded the requested module withdifferent variables on the GLOBAL parameter.For example, a program issues the LOADmacro instruction for a module with theparameter GLOBAL=(YES,P). However, aTCB already loaded that module with theparameter GLOBAL=(YES,F) orGLOBAL=NO.

System Action: The system issues messageIEA703I. The system abnormally terminates theprogram that issued the LOAD macroinstruction, unless the macro instructionincluded the ERRET parameter.

Programmer Response: Change the GLOBALparameter in the LOAD macro instruction.


D0A

Explanation: A task invoked a system functionthat, in turn, issued an R-form FREEMAINmacro instruction. The FREEMAIN attemptedto free local system queue area storage that wasnot owned by the task.

For example, a task issues a CLOSE macroinstruction for a data set it does not own.During execution of the CLOSE macroinstruction, the R-form FREEMAIN is issued.





D0D

Explanation: An error occurred duringabnormal termination of a subtask of thejobstep task. RTM2 (recovery terminationmanagement) was reentered invalidly; therefore,the abnormal termination was altered to includeall tasks in the jobstep.

Note: The original completion code is in theSVRB of the original SVC 13 SVRB queuedfrom the task that incurred the error.

System Action: RTM2 attempts to terminate thejob step. The system may have written a dumpto the SYSABEND or SYSUDUMP data setand also to the SYS1.DUMP data set.

Programmer Response: Determine thecompletion code for the original subtask, andcorrect the error.


D13

Explanation: The error occurred duringexecution of an OPEN macro instruction for agraphic data control block. This systemcompletion code is usually accompanied bymessage IEC158I. Message IEC158I identifiesthe terminated task and explains the return code(rc in the message text) in register 15.



D14

Explanation: The error was detected duringexecution of a CLOSE macro instruction for agraphic data control block.

The graphic device to be closed had not beenopened by the closing task.

Programmer Response: Issue the CLOSE macroinstruction within the task that issues the OPENmacro instruction, or remove the invalid


D23 to D78

CLOSE macro instruction. Then execute thejob step again.


D23

Explanation: The error occurred duringexecution of a WTO or WTOR macroinstruction.

If the system does not successfully write adump, the error is one of those described below.If the system successfully writes a dump, register15 contains a hexadecimal error code in theformat xxyy00zz. The xx field identifies theprocessing that was taking place when the erroroccurred. The yy field identifies the modulethat requested the ABEND. If xx is 10, the zzfield identifies the cause of the error. If xx is 20or greater, the zz field contains the return codethat was issued by GETCELL, BLDCPOOL, orGETMAIN processing.

xx Meaning

10 The error was found during a validity check of aparameter list. The zz field identifies the error:

01 The parameter list supplied to the WTOR macroinstruction does not begin on a fullwordboundary.

02 A multiple-line WTOR was specified.

03 The parameter list the user passed does not residein storage that the user can access.

04 The user requested a WTOR with a text length ofzero.

05 The caller modified the WPL (WTO parameterlist) during WTO processing.

20 A GETCELL for an ORE (operator reply element)failed.

21 A BLDCPOOL for an ORE failed.

22 A GETMAIN for an ORE failed.

30 A GETCELL for a WQE (write queue element) failed.

31 A BLDCPOOL for a WQE failed.

32 A GETMAIN for a WQE failed.

42 A GETMAIN for a dynamic work area failed.

yy Meaning

01 IEAVVWTO requested the ABEND.02 IEAVMWTO requested the ABEND.

Programmer Response: Correct the programissuing the WTO or WTOR macro instruction,recompile, and execute the job step again.


D2D


The control program found an invalid recordtype when attempting to load a segment of theoverlay program.

Programmer Response: Link edit the programagain, and execute the job step again.


D37

Explanation: The error occurred when anoutput operation to a direct access device wasrequested. This system completion code isaccompanied by message IEC031I. Message

IEC031I identifies the terminated task andexplains the return code (rc in the message text)in register 15.



D78

Explanation: A task invoked a system functionthat, in turn, issued an RC or RU formFREEMAIN macro instruction. TheFREEMAIN attempted to free local systemqueue area storage that was not owned by thetask.

For example, a task issues a CLOSE macroinstruction for a data set it does not own.During execution of the CLOSE macro


DFB

ABEND

instruction, the RC or RU form FREEMAIN isissued.





DFB

Explanation: During processing in a functionalsubsystem (FSS) address space, a JES3 moduledetected the error indicated by the hexadecimalreason code in register 15.

ReasonCode inHex (Dec) Explanation

01 (01D) The connect subsystem interface (SSI) routinein module IATSICD determined that theSTART command for the FSS address spacedid not contain a token.

02 (02D) The connect subsystem interface (SSI) routinein module IATSICD could not locate theMEMDATA header for the FSS addressspace.

03 (03D) The connect subsystem interface (SSI) routinein module IATSICD could not establish thelisten task, IATFCLT, for the FSS or theFSA.

0B (11D) The common end-of-task exit routine inmodule IATSICD found that a task in theFSS address space had terminatedunexpectedly.

0C (12D) The common end-of-task exit routine inmodule IATSICD could not identify a taskthat had terminated.

15 (21D) The writer FSA specific connect routine,IATFPCC, could not initialize for GETDSspool access using the block spooler.

16 (22D) The writer FSA specific connect routine,IATFPCC, could not establish the read-aheadtask for the FSA.

17 (23D) The writer FSA specific connect routine,IATFPCC, could not establish the checkpointwriter task for the FSA.

1F (31D) The FSI order interface routine, IATFCOR,received a nonzero return code from the FSSor FSA order routine.

20 (32D) The FSI post interface routine, IATFCPT,received a nonzero return code from the FSApost routine.

29 (41D) The C/I FSS order processing routine,IATIIFO, found that the FSI parameter listdid not contain an order.

2A (42D) The C/I FSS order processing routine,IATIIFO, received an invalid order type.

2B (43D) The C/I FSS order processing routine,IATIIFO, received an invalid stop FSS order.

2C (44D) The C/I FSS order processing routine,IATIIFO, could not locate the C/Icommunications block (CCB).

33 (51D) The writer FSA quick-cell service routine,IATFPQC, failed to get an index, because thefirst free index was invalid.

34 (52D) The writer FSA quick-cell service routine,IATFPQC, failed to get a buffer, because thefirst free buffer was invalid.

35 (53D) The writer FSA quick-cell service routine,IATFPQC, failed to free an index, because theindex passed in the request was invalid.

36 (54D) The writer FSA quick-cell service routine,IATFPQC, failed to free a buffer, because thebuffer passed in the request was invalid.

3D (61D) While reading a data set checkpoint record,the writer FSA GETDS routine, IATFPGD,received an error return from the blockspooler routine; the error return indicated thatthe parameter list was invalid.

3E (62D) While reading a data set checkpoint record,the writer FSA GETDS routine, IATFPGD,received an error return from the blockspooler routine; the error return indicated thatthe spool address was invalid.

3F (63D) While reading a data set checkpoint record,the writer FSA GETDS routine, IATFPGD,received an error return from the blockspooler routine; the error return indicated thatan error occurred during a cross-address spacemove.

47 (71D) While reading the scheduler work block(SWB), the writer FSA SWB processingservice routine, IATFPSB, received an errorreturn from the block spooler routine; theerror return indicated that the parameter listwas invalid.

48 (72D) While reading the scheduler work block(SWB), the writer FSA SWB processingservice routine, IATFPSB, received an error


E00

return from the block spooler routine; theerror return indicated that the spool addresswas invalid.

49 (73D) While reading the scheduler work block(SWB), the writer FSA SWB processingservice routine, IATFPSB, received an errorreturn from the block spooler routine; theerror return indicated that an error occurredduring a cross-address space move.

4A (74D) The scheduler JCL facility (SJF) PUTSWBfunction returned an error code to the writerFSA scheduler work block (SWB) processingservice routine, IATFPSB.

4B (75D) The scheduler JCL facility (SJF) UPDATEfunction returned an error code to the writerFSA scheduler work block (SWB) processingservice routine, IATFPSB.

4C (76D) The scheduler JCL facility (SJF)DELETESWB function returned an error codeto the writer FSA scheduler work block(SWB) processing service routine, IATFPSB.

51 (81D) The writer FSA read-ahead task, IATFPRA,could not initialize for spool access using theblock spooler.

52 (82D) While reading data from spool, the writer FSAread-ahead task, IATFPRA, received an errorreturn from the block spooler routine; theerror return indicated that the parameter listwas invalid.

53 (83D) While reading data from spool, the writer FSAread-ahead task, IATFPRA, received an errorreturn from the block spooler routine; theerror return indicated that the spool addresswas invalid.

54 (84D) While reading data from spool, the writer FSAread-ahead task, IATFPRA, received an errorreturn from the block spooler routine; theerror return indicated that an error occurredduring a cross-address space move.

55 (85D) The writer FSA read-ahead task, IATFPRA,found an error in the format of a spool databuffer. .

56 (86D) The writer FSA read-ahead task, IATFPRA,found an error in the format of a JESNEWSdata buffer.

5B (91D) The writer FSA checkpoint writer task,IATFPCW, could not initialize for spoolaccess using the block spooler.

5C (92D) While writing a data set checkpoint record, thewriter FSA checkpoint writer task,IATFPCW, received an error return from theblock spooler routine; the error returnindicated that the parameter list was invalid.

5D (93D) While writing a data set checkpoint record, thewriter FSA checkpoint writer task,IATFPCW, received an error return from theblock spooler routine; the error returnindicated that the spool address was invalid.

5E (94D) While writing a data set checkpoint record, thewriter FSA checkpoint writer task,IATFPCW, received an error return from theblock spooler routine; the error returnindicated that an error occurred during across-address space move.


Most failures in the read-ahead task, IATFPRA,and in the checkpoint writer task, IATFPCW,cause processing of the current data set to beterminated. The task is reinstated to resumeprocessing with the next data set.

All other failures result in termination of theFSA or of the entire FSS address space.

Operator Response: Notify the systemprogrammer. If the FSS address space wasterminated and if this is not a recurring error,issue the appropriate command to restart theFSS.

Problem Determination: Table I, item 33. TableIII, item 4.

E00

Explanation: An error occurred during EXCPprocessing of an I/O request. The IOSB wasreturned to EXCP termination processing withthe IOSB completion code set to X'45'. The I/Orequest was terminated for one of the followingreasons:

• A program check or machine checkoccurred while module IECIOSCN orIECVPST was executing.

• The operator pressed the RESTART keywhile the I/O request was being processed.

• A program check or machine checkoccurred while a nonresident ERP or ERPloader module was executing.

System Action: The system abnormallyterminates the task and writes an error record to


ABEND

E03 to E37

SYS1.LOGREC. The previous error record inSYS1.LOGREC should indicate the cause of theABEND.

Programmer Response: Usually not a programerror. The E00 code indicates that no EXCPdebugging area is provided. Check the messagein SYS1.LOGREC for the probable cause of thetermination.


E03

Explanation: The error occurred when a taskattempted to terminate normally with aRETURN macro instruction or a branch to thereturn address in register 14. The task isoperating in must-complete status and did notreset must-complete.


Programmer Response: Make sure that eachENQ, RESERVE, or STATUS macroinstruction requesting must-complete status ispaired with a DEQ or STATUS macroinstruction requesting 'reset must-complete.'

Problem Determination: Table I, items 1, 5a, 16,19, 23, 29. Table II, format 1, TRACE=SVC.

E13

Explanation: The error occurred duringexecution of an OPEN macro instruction for agraphic data control block. This systemcompletion code is accompanied by message




E23

Explanation: The error occurred duringexecution of a WTOR macro instruction. Theaddress of the event control block (ECB), theaddress of the request block (RB) in the ECB,or of the virtual storage area for the reply wasinvalid.

Programmer Response: Correct the macroinstruction or program errors that incorrectlymodified the macro expansion. Be sure that theECB address is a fullword on a fullwordboundary. Recompile, and execute the job stepagain.


E2D

Explanation: The error occurred duringexecution of an overlay program. The controlprogram found an invalid address whenattempting to load a segment of the overlayprogram.

Programmer Response: Link edit the programagain, and execute the job step again.


E37

Explanation: The error occurred when anoutput operation was requested. The data setwas on a direct access or magnetic tape device.This system completion code is accompanied bymessage IEC032I. Message IEC032I identifiesthe terminated task and explains the return code(rc in the message text) in register 15.




E82 to Fnn

E82

Explanation: Disabled code was executing andinvoked SVC 130 (RACHECK macro).However, SVC 130 is inactive because RACF(resource access control facility) is not installedon the system.



Problem Determination: Table I, items 2, 3, 4,5a, 13, 16, 17a, 17b.

E83

Explanation: Disabled code was executing andinvoked SVC 131 (RACINIT macro). However,SVC 131 is inactive because RACF (resourceaccess control facility) is not installed on thesystem.




E84

Explanation: Disabled code was executing andinvoked SVC 132 (RACLIST macro). However,SVC 132 is inactive because RACF (resourceaccess control facility) is not installed on thesystem.




E85

Explanation: Disabled code was executing andinvoked SVC 133 (RACDEF macro). However,SVC 133 is inactive because RACF (resourceaccess control facility) is not installed on thesystem.




Fnn


1. The error occurred during execution of aninvalid supervisor call (SVC) instruction.The last 2 digits of this completion code arethe operand of the SVC in hexadecimal.For example, completion code FOD meansthat the error occurred during execution ofSVC X'0D', which is SVC 13.

2. If nn is 13, 14, 17, or 37, anOPEN/CLOSE/EOV problem determinationroutine failed to recognize the passedabnormal termination code. Register 12contains the abnormal termination code.

Programmer Response: In the first case,probable user error. Make sure that the SVCwas not incorrectly modified. Check theoperand against the valid codes for the controlprogram being used, and determine if the SVCthat was issued had been generated into thesystem. Correct the error and execute the jobstep again.

In the second case, see message IEC900I.



001 to 002

WT CDSWait State Codes

001

Explanation: During execution of the IPLprogram a "not operational" condition code wasproduced in response to a Test I/O instruction.The Test I/O instruction was issued to determinethe current status of the volume containing thenucleus being loaded. The two-byte address ofthe device on which the error occurred can befound in real storage at decimal address 185(X139').

This wait state may result if the operatorattempts to load (IPL) the system with the IPLvolume on a device not supported for systemsresidence.

Operator Response: Ensure that the device onwhich the volume was mounted is ready. If theproblem recurs, call IBM for programmingsupport.

002

Explanation: During execution of the IPLprogram, an input/output operation was notinitiated; the channel status word (CSW) wasstored; and the channel was not busy. Thetwo-byte address of the device on which theerror occurred can be found in real storage atdecimal address 185 (X139').

Operator Response: Probable hardware error.Re-IPL the system. If the problem recurs, callIBM for hardware support.


003 to 00A

003

Explanation: During execution of the IPLprogram, an input/output operation was notinitiated because a not operational response wasreceived from an SIO instruction. The channelstatus word (CSW) was not stored, and thechannel was not busy. The two-byte address ofthe device on which the error occurred can befound in real storage at decimal address 185(X'B9').

Operator Response: Probable hardware error.Restart the system.


004

Explanation: During execution of the IPLprogram, an input/output operation was notinitiated. The channel status word (CSW) wasnot stored and the channel was not busyfollowing execution of a Test I/O instruction.The two-byte address of the device on which theerror occurred can be found in real storage atdecimal address 185 (X'B9').


005

Explanation: During execution of the IPLprogram, either SYS1.NUCLEUS is in multipleextents, or an input/output interruptionoccurred because of a unit check.

In the case of an input/output interruption, thetwo-byte address of the device on which theerror occurred is in real storage at decimaladdress 185 (X139'). The address of the channelcommand word (CCW) causing the original unitcheck is at address X'4C'. The first four sensebytes describing the unit check are at address

X'54'. A sense operation to determine the causeof the unit check did not find any of thefollowing:

• No record found.• File mask violation.

• End of cylinder.• Track condition check.

Operator Response: Probable hardware error.Verify that SYS1.NUCLEUS does not havesecondary extents. Re-IPL the system.


006

Explanation: During execution of the IPLprogram one or more of the following occurred:

• An interface control check.• A channel control check.• A channel data check.• A program check.• A channel chaining check.

The problem can occur if secondary extentshave been allocated for SYS1.NUCLEUS andIPL is attempting to load a member from asecondary extent.

Operator Response: Verify thatSYS1.NUCLEUS does not have secondaryextents. Re-IPL the system.


007

Explanation: During execution of NIP, aconsole was not available.

Operator Response: Ensure that a console isavailable. Then restart the system.

Problem Determination: Table I, items 17b, 29.

00A

Explanation: This wait state is preceded bymessage 1EA3261. The catalog entry for theSYS1.LINKLIB data set could not be found on,or could not be retrieved from, the systemcatalog.


WSC-2 OS/VS Message Library: VS2 System Codes

WT CDS

00B to 00E

Programmer Response: Make sure that theSYS1.LINKLIB data set is in the catalog. Thenre-IPL the system.


00B

Explanation: During initialization, the masterscheduler terminated abnormally. A dump waswritten to the SYS1.DUMP data set.

Operator Response: Attempt to re-IPL thesystem.


00C

Explanation: The active nucleus member is notedited in scatter format. This nucleus cannot beloaded by the IPL program.


Programmer Response: Make sure that theIEANUCOx member of SYS1.NUCLEUS hasbeen link-edited with the SCTR option of thelinkage editor. If not, link-edit the IEANUCOxmember again, specifying the linkage editor JCLas indicated in the SYS1.NUCLEUS link-editingstep of system generation for this system.

Problem Determination: Table I, items 11, 29.Also do the following:

• Execute the IEHLIST utility program toobtain a directory listing of theSYS1.NUCLEUS data set and have thelisting available.

• Have available, if possible, a copy of thelast link-editing step for the failing nucleusmember, IEANUC0x.

• Have available the name of the IEANUCOxmember that was selected for the failing IPLprocess. Unless altered by one of thespecialized operator IPL procedures, which

are described in Operator's Library:OS/VS2 MVS System Commands, the

member name is IEANUC01.

00D

Explanation: During initialization, the masterscheduler terminated abnormally. No dumpwas written.

Operator Response: Attempt to re-IPL thesystem.


00E

Explanation: The IPL program cannot locatethe SYS1.NUCLEUS data set or the activemember, IEANUC0x, of SYS1.NUCLEUS onthe IPL volume. The two-byte address of thedevice searched by the IPL program is in realstorage at decimal address 185 (X139').

Operator Response: If an alternate nucleus wasselected during IPL through one of thespecialized operator IPL procedures, which aredescribed in Operator's Library: OS/VS2 MVSSystem Commands, make sure that the alternatenucleus ID (the x of IEANUC0x) was correctlyentered in its EBCDIC form at absolute storagelocation 9. If the error persists, report it to thesystem programmer.

If an alternate nucleus was not selected, theactive member is IEANUC01.

Programmer Response: Ensure that the correctIEANUCOx of SYS1.NUCLEUS is in theSYS1.NUCLEUS data set.

Problem Determination: Table I, items 11, 29.Also do the following:

• Execute the IEHLIST utility program toobtain a directory listing of theSYS1.NUCLEUS data set, and have thelisting available.

• Provide the name of the IEANUCOxmember that was not found.


00F to 017

00F

Explanation: A volume has been IPLed, but itdoes not contain IPL text.

Operator Response: Correct the load unitswitches to address the correct volume to beIPLed. Verify that the correct volume ismounted. Re-IPL the system.


013

Explanation: During execution of NIP, an erroroccurred from which recovery is impossible.Check the system completion code to determinethe problem.

Operator Response: Re-IPL the system.


014

Explanation: Recursive translation exceptionshave occurred because the master addressspace's segment table or common page tableshave not been initialized correctly or have beenoverlaid. This code is associated with messageIEA999W. Additional information is saved inthe MCH logrec buffer to aid in diagnosing therecursive translation exception.

Programmer Response: Probable system error.Determine why the master address space'ssegment tables and/or page tables have beenoverlaid.


015

Explanation: When NIP issued the MSSFCALLmacro instruction, one of the followingoccurred:

• The MSSFCALL instruction was issued toobtain the SCPINFO data block fromMSSF (maintenance and service facility).The instruction resulted in a condition codeof 2, indicating that the MSSF was busy.

However, this condition code is notexpected during NIP. Probable hardwareerror.

• When NIP requested load parameters or awrite restart text, MSSF was busy.Probable hardware error.

• The SCPINFO data block did not containthe required information, such as theparameter for physical storage, theprocessor, or HSA.

Operator Response: Re-IPL the system. Notifythe system programmer.

Programmer Response: Call IBM for hardwaresupport.


016

Explanation: NIP issued the MSSFCALLinstruction to obtain the SCPINFO data blockfrom MSSF. The instruction resulted in acondition code of 0, indicating that MSSFaccepted the instruction and had responded, butthe response received was not the expected one.Probable hardware error.

Operator Response: Re-IPL the system. Notifythe system programmer.

Programmer Response: Call IBM for hardwaresupport.


017

Explanation: During execution of the IPLprogram, a unit check occurred following asuccessfully started I/O operation. The start I/Ooperation was either a sense I/O or an attemptto read the home address and record 0 of atrack that previously caused a track conditioncheck. The two-byte address of the device onwhich the error occurred can be found in realstorage at decimal address 185 (X'B9').

Operator Response: Probable hardware error.Re-IPL the system.


WT CDS

018 to 01C


018

Explanation: During execution of the IPLprogram, one of the following was found:

• The nucleus was too big for the machinesize; that is, the space available forrelocation dictionary (RLD) records wasexceeded.

• SYS1.NUCLEUS is in multiple extents.


Programmer Response: Regenerate the system,decreasing the nucleus size by removing options.If the problem recurs, call IBM forprogramming support.

019

Explanation: During execution of the IPLprogram, an unexpected program interruptionoccurred. IPL did not finish loading theresident nucleus. The IPL program is in error,the storage in which IPL resides is failing, or theIPL program attempted to load a member of theSYS1.NUCLEUS data set that is in a secondaryextent.

Operator Response: Be sure theSYS1.NUCLEUS data set does not havesecondary extents. If it does not, the error isprobably a hardware problem. When theproblem is corrected, re-IPL the system.


01A

Explanation: An attempt was made to executemultiprocessing modules not included in thenucleus when the system was generated. Themultiprocessing modules were not included as aresult of specifying the parameterACRCODE=NO on the CTRLPROG system

generation macro instruction. This wait stateoccurs only in a system generated with a subsetof multiprocessing code deleted and then onlywhen a system error caused an attempt toexecute a deleted module.

System Action: The system enters a disabledwait state.

Operator Response: Probable system error.Notify the system programmer.


01B

Explanation: The error conditions specified on aSLIP command have been met, and the systemis placed in a wait state, as requested.

System Action: The system is in a disabled waitstate, with restart capability.

Operator Response: Notify the systemprogrammer that the SLIP trap has beenentered. With the system programmer'sapproval, restart the system by pressing theconsole RESTART key or, on systems without aRESTART key, executing the operator restartfunction.

Note: If the system programmer requestsdiagnostic data, do not restart the system.Write a stand-alone dump, then re-IPL thesystem.

01C

Explanation: Supervisor control has suffered adouble recursive abnormal termination insupervisor control super FRR. This wait statecode is associated with message IEA967W.

Operator Response: Probable software error.Report this wait state code to the systemprogrammer. Re-IPL the system.



01D to 024

01D

Explanation: The system configuration containschannel set switching, but the identifier for thechannel set connected to one of the processorscannot be determined.


01F

Explanation: This wait state occurs duringexecution of NIP in a multiprocessingconfiguration.

Either this processor has microcode support forcross memory instructions (the PC, PT, andSSAR instructions, for example) and the IPLprocessor does not have that support, or thisprocessor does not have microcode support forcross memory instructions and the IPLprocessor does have that support.

Operator Response: Do one of the following:

• Move the operating system to amultiprocessing configuration in which eachprocessor has microcode support for crossmemory instructions or each processor doesnot have that support, and re-IPL.

• Load an operating system that does notrequire microcode support for cross memoryinstructions, and re-IPL.

• Keep the current operating system, butswitch to uniprocessing mode.

Problem Determination: Record the contents ofthis wait state PSW. Table I, items 29 and 30.

021

Explanation: During nucleus initialization, aninput/output error occurred on the main consolefollowing an EXCP operation.

Register 1 contains the address of theinput/output block (IOB) for the failing EXCP

operation. You can find Register 1 in the tracetable entry for the initial SRB dispatch ofIECVPST. This entry follows the entry for theI/O interrupt that contains the error status.



022

Explanation: A page fault has occurred for apage with a primary and secondary copy(duplexed page), but the primary and secondarydevices are either in a quiesced or 'not ready'state. The error occurred in a system facility(such as WTO) invoked by direct access volumeverification (DAVV).

Operator Response: Re-IPL the system. If thesystem is restarted, the current volumeverification will not be completed. This couldlead to an integrity exposure if an incorrectvolume is mounted. Before restarting thesystem, check to be sure that the correct volumeis mounted. This can be done by displaying thecontents of register 7, which contains theaddress of the UCB for the device and volumebeing verified. The UCB in turn contains thedevice address and volume serial number of thevolume that should be mounted.

024

Explanation: The system termination facilityfailed to receive an expected interrupt whileattempting to write a record to theSYS1.LOGREC data set.

Operator Response: Probable hardware andprogramming errors. Check the READ/WRITEswitch on all disk devices, then re-IPL thesystem.

Problem Determination: Table I, items 11, 29, or30.


WT CDS

026 to 02B

026


1. A power interruption occurred. All of realstorage was dumped to one of the powerwarning data sets (SYS1.WARNA orSYS1.WARNB).

2. The operator replied 'REST' to messageICFTIM21, and real storage has beensuccessfully refreshed from a SYS1.WARNxdata set. (Note: In a multiprocessingconfiguration, an 026 wait state in bothprocessors indicates a successful refresh.)

System Action: The system terminates.

Operator Response: In case 1, re-IPL to refreshreal storage from a SYS1.WARNx data set orerase and reformat the data sets.

In case 2, re-IPL the system. IMS/VS usersshould refer to IMS/VS Version 1 Operator'sReference Manual for the power warningtermination procedure.

027

Explanation: This code is issued as a result ofone of the following:

1. The operator replied 'STOP' to one of thepower warning initialization messages.

2. The operator replied 'REST' to messageICFTIM21, but real storage has not beensuccessfully refreshed from a warm data set.

3. A power interruption occurred. All of realstorage has not been successfully dumped toone of the power warning data sets(SYS1.WARNA or SYS1.WARNB).

System Action: The system terminates.

Operator Response: In case 1, respond to thepreceding message, and re-IPL the system. Incases 2 and 3, re-IPL the system.

029

Explanation: NIP has found the time-of-dayclock in error; the system is put into a wait stateto allow the clock to be set.

Operator Response: Re-IPL the system whileholding the TOD-clock switch in the enable-setposition so that NIP will set the clock. Theswitch needs to be held only until the first NIPmessage is printed.

02A

Explanation: While attempting to signal alogically online processor, the SIGP resulted ina condition code 3, that is, the hardware couldnot signal the other processor because itappeared not to exist.

Operator Response: Place the other processor inthe manual state. Then, initiate the STORESTATUS function on the processor that enteredthe wait state. After the STORE STATUSfunction has been initiated, invoke theRESTART function on the waiting processor.When alternate recovery (ACR) has configuredthe other processor out of the system, a messagesaying ACR has completed will be sent to theoperator's console. Then schedule the EREPservice aid program for execution.

Call IBM for hardware support.


02B

Explanation: While attempting to signal alogically online processor, the SIGP resulted ina condition code 3, that is, the hardware couldnot signal the other processor because itappeared not to exist. However, the otherprocessor had experienced a similar problemand had already entered a 02A wait state.

Operator Response: Check the other processorfor a 02A wait state. Respond as indicated forthe 02A wait state.



02C to 02F

02C

Explanation: While attempting to signal alogically online processor, the SIGP resulted ina condition code 3, that is, the hardware couldnot signal the other processor because itappeared not to exist. Normally a 02A waitstate would have occurred, but NIP is activeand alternate recovery (ACR) will not beinitiated.

Operator Response: Call IBM for hardwaresupport. Re-IPL the system.


02D

Explanation: Mass storage system (MSS) devicesare not supported during NIP. Either the unitaddress of a 3850 type device, or the VOLSERof a volume mounted on a 3850 type device, wasspecified for a volume required during systeminitialization. In the latter case, messageIEA314I will specify the unit address with theconflicting volume.

Operator Response: Ensure that the unit addressof a 3850 type device is not specified as a systemparameter value and that an online 3850 volumeserial number is not the same as that for avolume required during system initialization.

02E

Explanation: Auxiliary storage manager (ASM)is unable to function due to unrecoverability oran unusual number of permanent I/O errors onnecessary page data set(s).

System Action: The system is terminated.Message ILR008W was issued before the waitstate. Messages ILR007I, ILR009E andILR010I may have been issued previously; thesemessages should indicate what conditions led tothe 02E wait state.

Operator Response: Notify the systemprogrammer. Provide the system programmerwith the console sheet for problem analysis. Ifnecessary, at the next IPL, replace the page data

sets referenced in the messages or add morepage data sets.

Programmer Response: Analyze the consoleoutput provided by the operator to determinethe cause of the I/O error (see MVS DiagnosticTechniques). Analyze any I/O, machine check,missing interrupt handler, or disabled consolecommunication messages that occurred beforethe wait. Determine which page data sets areno longer usable. Correct or replace these datasets.


02F

Explanation: A direct access device containing apage data set is unavailable for an I/Ooperation. Location X'40C' points to an areathat contains the pertinent data. The format ofthe area is as follows:

Byte 0-3 Number of bytes of data in the followingarea

Byte 4-7 Wait state codeByte 8-15 Time stampByte 16 Reason code. The values are as follows:

X'80' Pack mounted does not contain theproper volume serial number asspecified in the UCB for this device

X'40' Intervention required for thespecified device

X'20' Device not operational

X'10' Permanent I/O error reading thevolume serial number for thespecified device

Byte 17 ReservedByte 18-19 Device addressByte 20-21 First two bytes of the sense dataByte 22-23 ReservedByte 24-27 Address of the complete sense data

Operator Response: Verify that the proper packis mounted on the device specified, then readythe device. Restart the system. If the reasoncode indicates that the device is not operational,also verify that the channel and the control unitare powered on and properly connected.



WT CDS

030 to 032

030

Explanation: During NIP, an unanticipatedrequest for abnormal task termination(ABEND) has occurred. The system completioncode is in bits 36-47 of the wait state PSW.

Operator Response: Record the contents of thewait PSW, and notify the system programmer.

Programmer Response: Refer to the descriptionof the ABEND code for further problemdetermination data.

The ABEND SVC entry in the system's SVCtable reflects the address of a 'trap' routine inNIP, and not the address of the ABEND SVC.The registers at the time of the ABEND SVCrequest are found in the Type I SVC save area.

Problem Determination: Table I, items 11, 29.Have available the recorded contents of the waitPSW.

031

Explanation: The IPL volume resides on a unitfor which no UCB exists.

Operator Response: Remove the systemresidence volume from its present unit, andmount it on a unit defined at system generation.Re-IPL the system.

Programmer Response: Perform an I/O devicesystem generation specifying the addresses of alldevices accessible to the system in theIODEVICE macro instruction.


032

Explanation: A required NIP module has notbeen found (through BLDL) in theSYS1.NUCLEUS data set.

System Action: The missing module is identifiedin hexadecimal in bits 36-47 of the wait statePSW, as follows:

Bits 36-47Value Module Name

001 IEAVNP01003 IEAVNP03004 IEAVNP04005 IEAVNP05006 IEAVNP06007 IEAVNP07009 IEAVNP09010 IEAVNP10011 IEAVNP11013 IEAVNPI3015 IEAVNP15016 IEAVNP16017 IEAVNP17019 IEAVNP1901B IEAVNP1B023 IEAVNP23033 IEAVNP33047 IEAVNP47057 IEAVNP57OA1 IEAVNPA10A2 IEAVNPA20A6 IEAVNPA60A8 IEAVNPA80B2 IEAVNPB20B6 IEAVNPB60B8 IEAVNPB8006 IEAVNPC6008 IEAVNPC80E6 IEAVNPE60F2 IEAVNPF20F5 IEAVNPF57D4 IEAVNIPM7E7 IEAVNIPX7F1 IEAVNPX1

Operator Response: Record the contents of thewait state PSW. Notify the system programmer.

Programmer Response: Make sure that themissing module is included in theSYS1.NUCLEUS data set.

Note: If bits 36-48 of the wait state PSW areX'7D4', the system may have been loaded bythe OS/360 IPL program. The system must beloaded using the OS/VS2 IPL program(IEAIPL00) distributed in SYS1.PARMLIB.

Problem Determination: Table I, items 11 and29. Also do the following:

• Execute the IEHLIST utility program toobtain a directory listing of theSYS1.NUCLEUS data set and have thelisting available.

• Have available the recorded contents of thewait state PSW.


033 to 038

033

Explanation: An I/O error occurred duringBLDL processing for a required NIP module.The module can be identified as described forwait state code 032.

Operator Response: Probable hardware error.Record the address of the IPL device on whichthe input/output error occurred and have itavailable. Record the contents of the wait statePSW. Notify the system programmer. Re-IPLthe system.


034

Explanation: An operating system that requiresone or more of the following features has beenloaded on a processor or version of microcodethat does not include the feature(s).

• System/370 processor, or 4300 processor(with System/370 IML).

• System/370 Extended Facility.

• System/370 Extended Feature.

• Dynamic address translation (DAT) feature.

• Clock comparator feature.

• CS/CDS instructions.

• IPK/SPKA instructions.

Operator Response: Do one of the following:

• IML a version of microcode that includesthe required features, and re-IPL.

• Move the operating system to a processorthat includes the required features, andre-IPL.

• IPL an operating system that does notrequire the features, such as MVT.

Record the contents of the wait PSW and havethis information available.


036

Explanation: An attempt was made to expandthe storage allocated to the SQA beforeinitialization of the paging subsystem. Thiserror occurred because of an unusual demandfor storage (more than 20,480 bytes) in the SQAduring the early stages of the IPL procedure.

Operator Response: If system messages wereincorrectly responded to, restart the system. Ifthis error recurs, notify the system programmer.


037

Explanation: The DSCB for SYS1.LOGREC,SYS1.SVCLIB, SYS1.PARMLIB, orSYS1.LINKLIB could not be read from thevolume where the data set resides for one of thefollowing reasons:

• The data set does not ,exist on this volume.

• An unrecoverable I/O error occurred duringthe attempted read.

Register 1 contains a pointer to the IOB for thefailing I/O operation (EXCP). Diagnosticmessages explaining the reason for the wait stateand identifying the name of the data setinvolved precede the system wait.

Operator Response: Report this wait state codeand the preceding messages to the systemprogrammer.

Programmer Response: Correct the error thatcaused the DSCB read I/O operation to fail, andrestart the system.


038

Explanation: IPL processing cannot initialize thesystem because there is not enough real storage.One of the following is true:

• Not enough online frames that are usable.


WT CDS

039 to 03C

• Not enough contiguous frames near thelow-address end or near the high-addressend.

A defective frame near the low-address end ornear the high-address end of real storage mightcause a shortage of contiguous frames.


Programmer Response: Make sure that there isenough real storage available for IPLprocessing. You may have to reduce thenumber of optional system facilities selected forthis system configuration. For further detailsconcerning the storage requirements of thecurrent configuration, see OS/VS2 SystemProgramming Library: System GenerationReference.

If the problem is a defective frame, real storagemay have to be reconfigured or replaced.


039

Explanation: A required direct access volumecould not be successfully mounted because of aconflict with another online volume. Theconflict could not be resolved since bothvolumes were required by the system, and,although both volumes had the same volumeserial, the volume that was to be mountedrequired a different device type than thatcontaining the online volume.


Programmer Response: Change the volumewhere one of the - two data sets resides. If themoved data set is cataloged, the catalog must beupdated.

Problem Determination: Table I, items 2, 11, 29,34a.

03A

Explanation: An error occurred during anattempt to build the link pack area (LPA) witha cold start. Messages preceding messageIEA304W identify the error condition.

Operator Response: Report this wait state codeand the preceding messages to the systemprogrammer.

Programmer Response: Correct the conditionsthat caused the LPA cold start to fail, andrestart the system.


03B

Explanation: A module required for continuedsystem operation cannot be found in the systemlink pack area (LPA).

Operator Response: Notify the systemprogrammer. Save the console listing.

Programmer Response: Examine the consolelisting to determine the name of the missingmodule (see message IEA363I). Execute theIEHLIST utility program to obtain a directorylisting of the SYS1.LPALIB data set. Examinethis list to determine which required systemmodules are missing. The missing modulesshould then be copied into SYS1.LPALIB fromthe starter system libraries or from a similarback-up source. Restart the system, and addthe missing module to the LPA either byrequesting an LPA cold start or by using theMLPA or FIX options.

Problem Determination: Table I, items 2, 11, 29.Have the contents of the wait PSW available.

03C

Explanation: ASM detected insufficientauxiliary storage resources for system operation:

• During IPL, either the required number ofpage data sets was not specified by the useror ASM has detected a problem with arequired page data set.


03D to 041

• After IPL, ASM has run out of space towrite PLPA, COMMON or LOCAL pages.One of the following is true:

— The duplex data set is full and thePLPA data set and/or the COMMONdata set is bad or full.

— The PLPA and COMMON data setsare full and duplexing is not available.

— All local page data sets are full or bad.

System Action: During IPL, message IEA935Wprecedes this wait state. After IPL, message

ILR008W precedes this wait state if PLPA orCOMMON space is unavailable. No messageprecedes this wait state if local paging space wasunavailable.

Operator Response: Report this wait state to thesystem programmer. Re-IPL the system,specifying larger page data sets or additionalpage data sets.

Programmer Response: Provide sufficientauxiliary storage for system operation.


03D

Explanation: During NIP, subroutineIEAVCSEG returned a nonzero code, indicatingan error in creating:

• A segment table entry.• A page table.• An external page table.

The IEAVCSEG subroutine is used ininitializing space for the common service area(CSA) and for the SQA.



03F

Explanation: A NIP function has beenimproperly invoked.



040

Explanation: A request for abnormal tasktermination (ABEND) has occurred during NIPprocessing. The system completion code is inbits 31-47 of the wait state PSW.

Operator Response: Record the contents of thewait PSW, and notify the system programmer.

Programmer Response: Refer to the descriptionof the ABEND code for further problemdetermination data.

The ABEND SVC entry in the system's SVCtable reflects the address of a 'trap' routine inNIP, and not the address of the ABEND SVC.The registers at the time of the ABEND SVCrequest are found in the SVRB that representsthe ABEND SVC.

Problem Determination: Table I, items 11, 29.Have available the recorded contents of the waitPSW.

041

Explanation: A processor failed. The I/Osupervisor found devices reserved on channelsthat can be accessed only by the failingprocessor. The device's must be rereserved tochannels accessible by the operative processor.

To maintain data integrity during recoveryprocessing, all systems sharing the reserveddevices with the failing system must be stopped.

Operator Response: Try to rereserve the devicesas follows:

• Stop all systems sharing devices that arereserved on channels accessible by thefailing processor. The I/O restart reservetable contains a list of the reserved devices.


WT CDS

042 to 044

Use the console display facility to obtain theaddress at location X'40C'. This addresspoints to the I/O restart reserve table. Thereserve table consists of 104-byte segments:

— The first word (4 bytes) contains theaddress of the next segment in the table.

— The second word is not meaningful.

— The third word is the beginning of thefirst entry in the table. This segmentcontains 12 entries; each entry is 8 byteslong. The address of the reserveddevice is in the second 2 bytes of eachentry.

— The last segment of the table has zerosin the first word.

Stop only those systems that share any ofthe reserved devices found in the table.

• Restart the operative processor to continueprocessing. If a device can be rereserved onan alternate path, the device remains online.If an alternate path is not available, thedevice is forced offline and messageIEA026I is issued.

• Restart the stopped systems after messageIEA858I appears.

For devices that could not be rereserved, re-IPLthe system. To maintain data integrity, youshould also re-IPL any system that shares thereserved devices; however, if the sharing systemis part of the same JES3 complex and thedevices are managed by JES3, only the originalsystem needs to be re-IPLed.


042

Explanation: The I/O supervisor has founddevices that are reserved from the failingprocessor and that have no logically onlinepaths from the operative processor. If theconsole RESTART key is pressed, the I/Osupervisor will attempt to reserve each of thesedevices on all physical paths.

Operator Response: Take one of the followingactions:

• Press the console RESTART key. Thisaction causes the I/O supervisor to attemptto reserve devices on any physical path tothe device. (Determine which devices areinvolved as indicated in wait state code041.)

• Re-IPL the system. To ensure dataintegrity, any shared processor should alsobe re-IPLed.


043

Explanation: The I/O supervisor cannot reservea device that was previously reserved to thefailing processor. This is a nonrecoverable waitstate. If the console RESTART key is pressed,the I/O supervisor will cause the system toreenter the 043 wait state.

Operator Response: Re-IPL the system, afterdetermining which resources are unavailable (toprevent a repetition of the problem). Theresponsible device can be identified by locatingthe first nonzero entry in the table described inwait state code 041. To ensure data integrity,any sharing processor should also be re-IPLed.


044

Explanation: During execution of NIP, amachine check occurred on a processor in theconfiguration. The logical processor address ofthe processor on which the machine checkoccurred is in bits 40-47 of the wait state PSW.

A logical processor address is a physicalprocessor address with a 4 in front of it. Forexample, logical address 40 stands for physicaladdress 0.




045 to 04B

045

Explanation: During execution of NIP, aBLDCPOOL request for a cellpool in SQAfailed. System initialization cannot continue.



046

Explanation: During execution of NIP, anunexpected program check occurred.



047

Explanation: During execution of NIP for amultiprocessor configuration, a malfunctionalert interrupt was received by a processor in theconfiguration. The logical processor address ofthe processor that generated the malfunctionalert is found in bits 40-47 of the wait statePSW.

Operator Response: Probable hardware error.Record the contents of the wait state PSW, andre-IPL the system. Notify the systemprogrammer.

Problem Determination: Table I, items 2, 30.Also, have available the recorded contents of thewait state PSW.

048

Explanation: During execution of NIP,subroutine IEAVPCB returned an undefinedreturn code.

IEAVPCB allocates a cellpool and a pool ofpage control blocks (PCBs) for the real storagemanagement (RSM) component of thesupervisor.



049

Explanation: While analyzing the devicesattached to an unavailable channel, the systemfound at least one to be reserved by theprocessor that received a machine checkinterruption. The reserve for the device wasreleased. See message IEA410I for information.

Operator Response: Re-IPL the system. Thedevice(s) that were reserved but have beenreleased can be found by locating the nonzeroentries in the table described in wait state code041. To ensure data integrity, any sharingprocessor should also be re-IPLed.


04A

Explanation: A TOD Clock on one of theprocessors in the configuration is in an errorstate. The clock must be set to avoid generatinga machine check later in NIP processing.

Operator Response: Press the RESTART buttonon the IPL processor, or invoke the restartfunction on systems without a RESTARTbutton. Then operate the clock security switchfor several seconds. The initialization processwill then continue.

Note: If all clocks in the configuration are bad,a 04A wait state may occur for each processor.

04B

Explanation: A machine check interruptionroutine found a group of channels temporarilyunavailable.

Operator Response: Respond by storing one ofthe following action codes in location X'30E':

ActionCode Explanation

01 Used to force the unavailable channels offline.Message IEA410E is issued for each channel. Anywaiting or active I/O is restarted on alternate paths.If an alternate path is not available, messageIEA004I is issued, and the I/O is not completed.


04C

WT CDS

02 Used to attempt to recover the unavailable channels.Wait 60 seconds to allow recovery processing tocomplete. If recovery is successful, the channels areavailable for use. Any waiting or active I/O isrestarted using these channels. If recovery is notsuccessful, the system proceeds as if the reply wereX'01'.

You should try action code X'02' first.However, if the system suffers continuouslyfrom the 04B wait state, specify action codeX'01'. If any code other than X'01' or X'02' isstored, the 04B wait state code is reloaded.

Perform the RESTART function to restart thesystem.

For additional diagnostic information, thechannel mask can be located as follows:

• Using the console display facility, locate thechannel mask that is pointed to by location

X'40C'.

• The channel mask is 32 bits long.

— Bits 0-15 correspond to the 16 channels(0-15) of the processor.

— Any available channel will have a 1 inthe corresponding bit position (0-15).

— Bits 16-31 are the channel set ID.


04C

Explanation: A machine check interruptionroutine found a group of channels temporarilyunavailable. Devices are reserved on thesechannels.

To maintain data integrity for the devices orvolumes on the devices attached to theunavailable channels, all systems that sharedevices with this system must be stopped beforerecovery processing continues.

Operator Response: Stop all systems that shareany devices with this system. Then, respond bystoring one of the following action codes inlocation X'30E':


01 Used to force the unavailable channels offline.Message IEA410E is issued for each channel. Eachdevice reserved on one of the channels is rereservedover an alternate path. If a device cannot berereserved, it is varied offline, message IEA026I isissued, and all I/O requests for the device areterminated in error until the device is varied online.Any waiting or active I/O is restarted on alternatepaths. If an alternate path is not available, messageIEA004I is issued, and the I/O is not completed.

02 Used to attempt to recover the unavailable channels.Wait 60 seconds to allow recovery processing tocomplete. If recovery is successful, the channels areavailable for use and the reserved devices arerereserved on these channels. Any waiting or activeI/O is restarted using these channels. If recoveryprocessing is not successful, the system proceeds asif the reply were X'01'.

If any code other than X'01' or X'02' is stored,the 04C wait state code is reloaded.

Perform the RESTART function to restart thissystem. Start the other stopped systems aftermessage IEA421E appears.

Note: The table of devices reserved through thefailing channel can be located as follows:

• Using the console display facility, locate thechannel mask that is pointed to by locationX'40C'.

• The channel mask is 32 bits long.


— Any unavailable channel will have a 1in the corresponding bit position (0-15).


• The reserve table immediately follows thechannel mask. It consists of 104-bytesegments.



— The third word begins the first entry inthe table. The segment contains 12entries; each entry is 8 bytes long. The


04D to 04E

address of the reserved device is in thesecond 2 bytes of each entry.

— The last segment in the table has zerosin the first word.


04D

Explanation: An I/O interruption indicates thata channel is unavailable for use. At least onedevice is reserved on the channel.

To maintain data integrity for the devices orvolumes on the devices attached to the failingchannel, all systems that share devices with thissystem must be stopped before recoveryprocessing continues.

Operator Response: Stop all systems that shareany devices with this system. Then restart thissystem to continue recovery processing.

If recovery processing is successful, the channelis available for use, and the reserved devices arerereserved on the channel. The system restartsany waiting or active I/O using the channel.

If recovery processing is not successful, thesystem marks the channel offline and issuesmessage IEA410E. Each device reserved on thechannel is rereserved over an alternate path. Ifa device cannot be rereserved, the system variesit offline, issues message IEA026I andterminates in error all I/O requests for thedevice until the device is varied online. Anywaiting or active I/O is restarted on alternatepaths. If an alternate path is not available, thesystem issues message IEA004I and does notcomplete the I/O.

Start the other stopped systems after messageIEA421E appears.

Note: The table of devices reserved through thefailing channel can be located as follows:

• Using the console display facility, locate thechannel mask that is pointed to by location

X'40C'.

O The channel mask is 32 bits long.


— Any unavailable channel will have a 1in the corresponding bit position (0-15).


• The reserve table immediately follows thechannel mask. It consists of 104-bytesegments.



— The third word begins the first entry inthe table. The segment contains 12entries; each entry is 8 bytes long. Theaddress of the reserved device is in thesecond 2 bytes of each entry.

— The last segment in the table has zerosin the first word.


04E

Explanation: The system encountered an errorwhile attempting to place one or more devicesoffline in response to a previous hardware error.Message IEA151W precedes this wait state.Also, wait state 041, 04C, 04D, or 06F ormessage IEA427A, IEA438A, IEA439A, orIEA440A may precede this wait state.

Operator Response: Probable software error. Ifthe failing device, control unit, or channel isidentified by a previous wait state or message,bypass the problem by reconfiguring the systemto physically remove the failing equipment.Write a stand-alone dump, and re-IPL thesystem.

If you do not know which unit encountered thehardware error, proceed with the problemdetermination items, and re-IPL the system.

Contact IBM for programming support.


04F to 059

WT CDS


04F

Explanation: The system, while attempting torecover channels that are unavailable, detectedthe loss of an additional channel.

System Action: The system is unable to continueprocessing.

Operator Response: Re-IPL the system. Ifrestart is attempted before the re-IPL, the waitstate will be reloaded.


050

Explanation: Alternate recovery (ACR) hasdetermined that it has been recursively invoked.This wait state code is associated with messageIEA856W.

System Action: The system places all processorsin a wait state.

Operator Response: Probable hardware error onmore than one processor. Write a stand-alonedump, and re-IPL the system. Then scheduleexecution of the EREP service aid program.


051

Explanation: Alternate recovery (ACR) hasencountered an unrecoverable error whilerecovery was in progress for another processor.This wait state code is associated with messageIEA857W.


Operator Response: Probable software error.Re-IPL the system. Then schedule execution ofthe EREP service aid program.

Problem Determination: Table I, items 11, 18,29, or 30.

052

Explanation: Alternate recovery (ACR) hasencountered an unrecoverable error whilerecovery was in progress for another processor.This wait state code is associated with messageIEA857W.


Operator Response: Probable hardware error.Write a stand-alone dump, and re-IPL thesystem. Then schedule execution of the EREPservice aid program.


058

Explanation: During execution of NIP for amultiprocessor configuration, subroutineIEAVSPSA returned a code indicating one ofthe following:

• A failure to obtain or free the SALLOClock.

• A failure of a GETMAIN or FREEMAINfor space in SQA.

The IEAVSPSA subroutine is used to obtainspace for, and build supervisor routineword/save areas for, each non-IPL processor ina multiprocessor configuration.



059

Explanation: During execution of NIP, a BLDLrequest returned an undefined return code.System initialization cannot continue.



Wait State Codes WSC- 17

05A to 05C

05A

Explanation: During execution of NIP for amultiprocessor configuration, the processorbeing IPLed failed to set a synchronization flagfor a processor that it had signaled. Thesignaled processor loads this wait state code.

The most probable reason that the processorbeing IPLed failed to set the synchronizationflag is that it had a machine check.

Operator Response: Probable hardware error onthe processor being IPLed. Re-IPL the system.


05B

Explanation: During execution of NIP for amultiprocessor configuration, another processorwas signaled by the processor being IPLed tobegin initializing itself. One of the following hasoccurred:

• The signaled processor had detected that itwas a 'runaway' and loaded this wait statecode. The IPL process continues.

• The signaling processor has detected thatthe other processor could be a 'runaway'.The processor being IPLed has attempted toreset the other processor with a SIGP initialprogram reset but without success. It isunsafe to continue the IPL process with theother processor in an unknown state.Therefore, the processor being IPLed loadsthis wait state code and terminates the IPL.

A signaled processor is considered to be a'runaway' if the SIGP instruction for restart tothat processor, executed by the processor beingIPLed, sets the condition code to indicate theSIGP function was unsuccessful. However, therequested function could have, in fact, beenstarted on the signaled processor.

This contradiction between the SIGP instructioncondition code and the fact that the functionhas been started is probably due to a hardwareerror on the signaled processor. Thus, this

situation could arise on any of the processorsnot being IPLed in a multiprocessorconfiguration.

Operator Response: If the wait state was loadedon a processor that was not being IPLed, thereis a probable hardware error on that processor.If the processor must be online, execute aVARY CPU ONLINE to it after systeminitialization is complete, or re-IPL the system.If the wait state was loaded on the processorbeing IPLed, there is a probable hardware erroron the processor being IPLed. Configure thefailing processor out, and re-IPL. If the failingprocessor must be online, execute a VARY CPUONLINE to it after system initialization iscomplete. Register 1 contains the physicaladdress of the failing processor.


05C

Explanation: During execution of NIP, thepointer to the master catalog could not beobtained from the SYS1.NUCLEUS data set.

The pointer to the master catalog should be inthe SYSCATLG or SYSCATnn member in theSYS1.NUCLEUS data set. The member iscreated at system generation time.

Operator Response: Possible causes are: I/Oerrors while attempting a BLDL to find themember, member not found, or I/O errorsattempting to read records from the member.

Re-IPL the system, and notify the systemprogrammer,

Programmer Response: IPL a different system,and use it to determine if the SYSCATLG orSYSCATnn member exists in theSYS1.NUCLEUS data set and is in the correctformat. Add it to the data set as described inOS/VS2 System Programming Library: System

Generation Reference.

Problem Determination: Table I, items 2, 17ab,25c, 26c, 29 or 30.


05D to 05F

WT CDS

05D

Explanation: For a VSAM master catalog, NIPcould not find a DSCB (data set control block)for the VSAM master catalog or could not reada DSCB from the VTOC (volume table ofcontents) of the volume pointed to by theSYS1.NUCLEUS data set. The pointer to themaster catalog is in the SYSCATLG member inthe SYS1.NUCLEUS data set.

For an ICF (integrated catalog facility) mastercatalog, NIP could not find a DSCB for theVVDS (VSAM volume data set) or could notread a DSCB from the VTOC of the volumepointed to by the SYS1.NUCLEUS data set.

Operator Response: Possible causes are:hardware errors, the wrong volume mounted, oran incorrect pointer to the master catalog in theSYSCATLG member of the SYS1.NUCLEUSdata set. Re-IPL the system, and notify thesystem programmer.

Programmer Response: IPL a different system,and use it to determine one of the following:

• If the VTOC of the volume containing themaster catalog is correct.

• If the SYSCATLG member of theSYS1.NUCLEUS data set is in the correctformat, as described in OS/VS2 SystemProgramming Library: System GenerationReference.

Problem Determination: Table I, items 2, 25a,26c, 30.

05E

Explanation: For a VSAM master catalog, anI/O error occurred when NIP tried to read theVSAM master catalog self-describing records.

Note: The first ten records of the VSAMmaster catalog data set describe the VSAMmaster catalog itself. They are the catalog entryfor the VSAM master catalog.

For an ICF (integrated catalog facility) mastercatalog, one of the following occurred:

• An I/O error occurred when NIP tried toread the VVCR (VSAM volume controlrecord) of the VVDS (VSAM volume dataset).

• The VVCR did not specify the name of theICF master catalog in the SYSCATLGmember of the SYS1.NUCLEUS data set.

Operator Response: Probable hardware error, oran incorrect pointer to the ICF master catalogin the SYSCATLG member of theSYS1.NUCLEUS data set. Re-IPL the system.Notify the system programmer.

Programmer Response: For a VSAM mastercatalog, correct the VSAM master catalog asfollows:

• Restore it to the proper volume, after thedamage to that volume is corrected.

• Recreate it as described in OS/VS2 SystemProgramming Library: System GenerationReference.

For an ICF master catalog, IPL a differentsystem, and use it to determine if theSYSCATLG member of the SYS1.NUCLEUSdata set is in the correct format as described inOS/VS2 System Programming Library: System


Problem Determination: Table I, items 2, 26d or34a, 30.

05F

Explanation: NIP found one of the following:

• The VSAM master catalog self-describingrecords were damaged. For example, therecords were improperly written over ormodified.

Note: The first ten records of the VSAMmaster catalog data set describe the VSAMmaster catalog itself. They are the catalogentry for the VSAM master catalog.

• The SYSCATLG member, or alternateSYSCATnn member, of SYS 1 NUCLEUScontains incorrect data.


060 to 063


Programmer Response: Confirm that the data inthe SYSCATLG member, or alternateSYSCATnn member, of SYS1.NUCLEUS,including the volume serial number and thedevice type, are correct. After correcting anyerrors found in the SYSCATLG member, oralternate SYSCATnn member, ofSYS1.NUCLEUS, re-IPL the system. If theSYSCATLG member is correct, then restore themaster catalog to the proper volume, ifnecessary, or recreate it as described in OS/VS2System Programming Library: SystemGeneration Reference. Re-IPL the system.

Problem Determination: Table I, items 2, 25d or26b, 29.

060

Explanation: While saving or rebuilding thePLPA, ASM initialization detected an errorwhile processing external page table entries(XPTEs):

• On a cold start, ASM initialization wasunable to locate an XPTE.

• On a quick or warm start, ASMinitialization could not locate an XPTE orfound invalid information in the quick startrecord (ILRQSRCD).

System Action: Message IEA943W is issued,and IPL terminates.


Programmer Response: Re-IPL, specifying theCLPA system parameter.


061

Explanation: ASM initialization has detected anerror with the time-of-day (TOD) clock whileexecuting a store clock (STCK) instruction.

System Action: Message IEA945W is issued,and IPL terminates.

Operator Response: Correct the TOD clock, andre-IPL the system.


063

Explanation: During execution of NIP, aconditional GETMAIN failed.


Programmer Response: The probable cause ofthis error is that insufficient SQA was availableto provide the options requested for this IPL.Another possibility is a system error resulting inexcessive demands on the NIP region. Thesubpool requested may be determined byexamining the last GETMAIN entry reflected inthe system trace table. If the request was forSQA, the problem can be corrected byspecifying a larger value on the SQAinitialization parameter ('SQA='). Foradditional information, see the IEASYSxxsection in OS/VS2 MVS System ProgrammingLibrary: Initialization and Tuning Guide.

If the system was IPLed with insufficient realstorage available to back the SQA requests, youmay have to increase the amount of onlinestorage before attempting to re-IPL, or toreduce the number of optional system facilitiesselected for this system configuration. Forfurther details concerning the real storagerequirements for the current configuration, seeOS/VS2 System Programming Library: System




064 to 066

WT CDS

064

Explanation: During execution of NIP, asoftware or hardware system error was detectedand an attempt was made to enter the RecoveryTermination Manager (RTM). This attemptwas trapped by the NIP routines because thesystem is in a variable state of initialization and,in particular, RTM is not fully initialized. Thefirst byte of the instruction address portion ofthe PSW (bits 40 through 47) contains a tableentry code:

Table EntryCode Explanation

01 A module took a branch to ABTERM.

02 Dynamic Address Translation error occurred.

03 Operator pressed the RESTART key.

04 Machine check.

05 Occurs when an SVC instruction is issued inan invalid mode (SRB, locked, etc.).However, this is usually not the actual error,because it is common for system routines toissue an ABEND (SVC 13) while holding alock. Therefore, with a code 05, firstdetermine if an SVC 13 was the last SVCissued by looking at the SVC OLD PSW orthe trace table. If this is the case, the R1field in the trace table contains the ABENDcodes and the R15 field contains the reasoncode. The ABEND code may give some clueas to which SVC issued the ABEND. If itdoes, examine the trace table to find wherethe ABEND-issuing SVC was issued. Theinputs to that SVC may be in error.

If a code 05 occurs and SVC 13 was not thelast SVC issued, the error was caused by theSVC. Perhaps a module is invalidly issuingan SVC while holding a lock. However,some routine that was previously in controlmay have returned to its caller withoutreleasing a lock. In this case, the SVC-issueris not at fault.

Code 05 may have occurred while readingfrom SYS1.PARMLIB, which has gone tomultiple extents, or while trying to process anon-executable load module, or if I/O errorsoccurred on the system residence volume.

06 Paging I/O error.

07 Call to ABTERM issued and no ASIDprovided.

08 Request for address space termination.

09 Indicates that a program check, other than aresolvable translation exception, hasoccurred. The program check OLD PSWindicates the type of exception and where itoccurred. The registers at the time of theexception are saved at displacement X'48'into the LCCA. If it was a translationexception (program interrupt code X'10' or

X'11',) location X'90' contains the addressthat could not be translated. The trace tablealso contains this information. Code 09 mayoccur on a warm or quick start if theprevious cold start failed before or duringmaster scheduler initialization. Attempt torestart the system, specifying 'CLPA' in thereply to message IEA101A.

0A Alternate processor recovery.

0B Cross-address space ABTERM and an ASIDprovided.

Operator Response: Check the READ/WRITEswitch on the direct access devices; the systemmust be able to write on the system pack forLPALIB during IPL. Then notify the systemprogrammer.

Problem Determination: Table I, items 2, 11, 29.Also have the recorded contents of the waitstate PSW available.

065

Explanation: During execution of NIP, anattempt was made to execute a type 3 or 4 SVC.This attempt was trapped by the NIP routinesbecause, at the time the attempt was made, thetype 3 and 4 SVCs had not been loaded.



066

Explanation: IOS detected hot I/O (an invalidrepeated interruption condition caused by ahardware malfunction) on a non-direct accessdevice. No devices are reserved on the channel.

Operator Response: Respond as follows:

• Use the console display facility to locate theaddress of the hot non-direct access deviceand the operator reply area. Display thetwo words pointed to by location X'40C'.


067

The first word contains the address of theSCD (status collection data) control block.The second word contains the address of theoperator reply area (used for reply X'03'),which is initialized to blanks. The pertinentinformation in the SCD is:

— Offset 0 contains the 2-byte channel setID, in hexadecimal.

— Offset 2 contains the 2-byte deviceaddress, in hexadecimal.

• Correct the problem at the lowest possiblelevel: device first, then control unit, thenchannel.

• Inform IOS of the action taken by storingone of the following action codes in locationX'30E'.


01 No device, control unit or channel wasphysically removed. The device might havebeen reset.

02 The device was physically removed, forexample, powered off.

03 The control unit was physically removed, forexample, powered off or all interfaces disabled.The addresses of all the devices on the controlunit must be stored in the operator reply area.For example, if devices 250 through 254 and25E are on the control unit, store the followingin the operator reply area:

02508254025E40 or 025E0250825440

Note: Each unit address must be preceded by0 or 8. The 8 indicates a range of addresses ofdevices on the control unit. The range startswith the address preceding the 8, ends with theaddress following the 8, and contains allconsecutive addresses in between. The replymust end in X'40'.

04or

84 The channel was physically removed, forexample, powered off or all interfaces disabled.Reset the channel if it is a stand-alone channeland store X'84'. If it is not a stand-alonechannel, do not reset the channel; store X'04'.

• Perform the system restart function.

If necessary, contact hardware supportpersonnel. When the device is repaired, it canbe varied online.

System Action: The channel is disabled. Thesystem waits for the operator to take correctiveaction and then enter a response. The actionthe system takes depends on the action codeentered by the operator, as follows:


01 The channel is enabled and processing continues.

02 The device is boxed (forced offline) and messageIEA026I is issued. The channel is enabled andprocessing continues.

03 The devices included in the reply are boxed (forcedoffline) and message IEA026I is issued. The channelis enabled and processing continues.

04 The system attempts to reset the channel. If thechannel is reset successfully, message IEA071E isissued. The channel is left in the disabled state. Seethe description of message IEA071E.

If the channel is not reset successfully, wait state06A is issued; recovery has failed. The channel isleft in the disabled state. See the description of waitstate code 06A.

84 To complete the reset operation, the system issues aHalt Device and a Clear I/O instruction for eachdevice on the channel.

If the channel is reset successfully, message IEA071Eis issued. The channel is left in the disabled state.See the description of message IEA071E.

If the channel is not reset successfully, wait state06A is issued; recovery has failed. The channel isleft in the disabled wait state. See the description ofwait state code 06A.

Problem Determination: Table I, items 2, 18, 30.For more information about the hot device,check the contents of the SCD. The format ofthe SCD is described in OS/VS2 Data Areas(JES2) or (JES3).

067

Explanation: IOS detected hot I/O (an invalidrepeated interruption condition caused by ahardware malfunction) on a non-direct accessdevice. Devices are reserved on the channel.


067

WT CDS


• Use the console display facility to locate theaddress of the hot non-direct access deviceand the operator reply area. Display thetwo words pointed to by location X'40C'.The first word contains the address of theSCD (status collection data) control block.The second word contains the address of theoperator reply area (used for reply X'03'),which is initialized to blanks. The pertinentinformation in the SCD is:


— Offset 2 contains the 2-byte deviceaddress, in hexadecimal.

• Correct the problem at the lowest possiblelevel: device first, then control unit, thenchannel.

• If you plan to reply X'04' or X'84', stop allsystems that share reserved devices with thissystem before taking any action. The othersystems must be stopped to maintain dataintegrity on the reserved volumes.

• Inform IOS of the action taken by storingone of the following action codes in locationX‘30E'.


01 No device, control unit or channel wasphysically removed. The device might havebeen reset.

02 The device was physically removed, forexample, powered off.

03 The control unit was physically removed, forexample, powered off or all interfaces disabled.The addresses of all the devices on the controlunit must be stored in the operator reply area.For example, if devices 250 through 254 and25E are on the control unit, store the followingin the operator reply area.

02508254025E40 or 025E0250825440 _

Note: Each unit address must be preceded by0 or 8. The 8 indicates a range of addresses ofdevices on the control unit. The range startswith the address preceding the 8, ends with theaddress following the 8, and contains allconsecutive addresses in between. The replymust end in X'40'.

04or

84 The channel was physically removed, forexample, powered off or all interfaces disabled.Reset the channel if it is a stand-alone channeland store X'84'. If it is not a stand-alonechannel, do not reset the channel; store X'04'.


• Restart the stopped systems after messageIEA421E appears.


System Action: The channel is disabled. Thesystem waits for the operator to take correctiveaction and then enter a response. The actionthe system takes depends on the action codeentered by the operator, as follows:


01 The channel is enabled and processing continues.

02 The device is boxed (forced offline) and messageIEA026I is issued. The channel is enabled and

processing continues.

03 The devices included in the reply are boxed (forcedoffline) and message IEA026I is issued. The channelis enabled and processing continues.

04 The system attempts to reset the channel. If thechannel is reset successfully, message IEA071E isissued. The channel is left in the disabled state andmessage IEA421E is issued. See the description ofmessage IEA071E.

If the channel is not reset successfully, wait state06A is issued; recovery has failed. The channel isleft in the disabled state. See the description of waitstate code 06A.

84 To complete the reset operation, the system issues aHalt Device and a Clear I/O instruction for eachdevice on the channel.

If the channel is reset successfully, message IEA071Eis issued. The channel is left in the disabled stateand message IEA421E is issued. See the descriptionof message IEA071E.

If the channel is not reset successfully, wait state06A is issued; recovery has failed. The channel isleft in the disabled wait state. See the description ofwait state code 06A.

Problem Determination: Table I, items 2, 18, 30.For more information about the hot device,


068 to 069

check the contents of the SCD. The format ofthe SCD is described in OS/VS2 Data Areas(JES2) or (JES3).

068

Explanation: IOS detected hot I/O (an invalidrepeated interruption condition caused by ahardware malfunction) on a channel or a directaccess device. The system cannot reset thechannel. No devices are reserved on thechannel.


• Use the console display facility to locate theaddress of the hot channel or direct accessdevice. Display the word pointed to bylocation X'40C'. This word contains theaddress of the SCD (status collection data)control block. The pertinent information inthe SCD is:


— Offset 2 contains the channel number inthe format X'OCxx' where C is thechannel number.

• Reset the channel if it is a stand-alonechannel and store X'80' in location X'30E'.If it is not a stand-alone channel, do notreset the channel; store X'00' in location

X'30E'.



System Action: The channel is disabled. Thesystem waits for the operator to take correctiveaction and then enter a reply.

If the operator replied X'80' to reset thechannel, the system issues a Halt Device and aClear I/O instruction for each device on thechannel. The system then attempts to restartactive I/O operations. The first time theproblem occurs on this channel, the channel isenabled and processing continues. The secondtime the problem occurs, the channel is left in

the disabled state and message IEA071E isissued. See the description of messageIEA071E.

If the operator replied X'00', thus not resettingthe channel, wait state 06A is issued; recoveryhas failed. The channel is left in the disabledstate. See the description of wait state 06A.

Problem Determination: Table I, items 2, 18, 30.For more information about the hot channel ordirect access device, check the contents of theSCD. The format of the SCD is described in

OS/VS2 Data Areas (JES2) or (JES3).

069

Explanation: IOS detected hot I/O (invalidrepeated interruption condition caused by ahardware malfunction) on a channel or a directaccess device. Devices are reserved on thechannel.


• Use the console display facility to locate theaddress of the hot channel or direct accessdevice. Display the word pointed to bylocation X'40C'. This word contains theaddress of the SCD (status collection data)control block. The pertinent information inthe SCD is:


— Offset 2 contains the channel number inthe format X'0Cxx' where C is thechannel number.

• To maintain data integrity, stop any systemthat shares reserved devices with this systembefore taking any action; however, if thesharing system(s) are part of the same JES3complex and the devices are managed byJES3, the sharing systems do not need to bestopped.

• Reset the channel if it is a stand-alonechannel and store X'80' in location X'30E'.If it is not a stand-alone channel, do notreset the channel; store X'00' in location

X'30E'.


06A to 06B

WT CDS


• Restart the stopped systems after messageIEA421E appears.

If necessary, contact hardware hardware supportpersonnel. When the device is repaired, it canbe varied offline.

System Action: The channel is disabled. Thesystem waits for the operator to take correctiveaction and then enter a reply.

After the reply is entered, the system attempts toreset the channel. If it cannot, the systemchecks to see if the operator replied X'80' toreset the channel. If the operator reset thechannel, the system issues a Halt Drive and aClear I/O instruction for each device on thechannel.

If either the system or the operator reset thechannel successfully, devices reserved on thechannel are rereserved. If the system cannotrereserve a device, the system boxes it (forces itoffline), issues message IEA026I, and attemptsto restart active I/O operations. The first timethe problem occurs on a channel, the systemenables the channel, issues message IEA421E,and continues processing. The second time theproblem occurs, the system leaves the channeldisabled and issues messages IEA421E andIEA071E. See the description of IEA071E.

If the operator replied X'00', thus not resettingthe channel, wait state 06A is issued; recoveryhas failed. The channel is left in the disabledstate. See the description of wait state 06A.

Problem Determination: Table I, items 2, 18, 30.For more information about the hot channel ordirect access device, check the contents of theSCD. The format of the SCD is described in

OS/VS2 Data Areas (JES2) or (JES3).

06A

Explanation: A channel was not resetsuccessfully following a hot I/O condition (aninvalid repeated interruption caused by a

hardware malfunction). This wait state ispreceded by wait state 066, 067, 068, or 069 orby message IEA066A, IEA067A, IEA068A, orIEA069I.

Operator Response: Notify the systemprogrammer. Depending on the requirements ofyour installation, restart the system to continueprocessing, or re-IPL the system.

System Action: If the operator restarts thesystem, the channel is left disabled and offline.Each device on the channel that is not accessibleover an alternate path is boxed (forced offline)and message IEA004I is issued. Active I/O isnot redriven; that is, the system does notattempt to restart the I/O. Message IGF991Eappears later for any active I/O. If any devicesare reserved on the channel, the system neitherreleases them nor rereserves them over alternatepaths.

Operator Response: Notify the systemprogrammer. Depending on the requirements ofyour installation, restart the system to continueprocessing, or re-IPL the system.

Problem Determination: Table I, items 2, 18, 30.For more information about the hot channel ordirect access device, check the contents of theSCD (status collection data) control block in theSYS1.LOGREC data set. The format of theSCD is described in OS/VS2 Data Areas (JES2)or (JES3).

06B

Explanation: While channel set switching wasactive, an attempt was made to change channelsets. However, the hardware was unable toconnect any channel set to this processor,leaving the system with no I/O capability.

Operator Response: Probable hardware error.Call IBM for hardware support.

Programmer Response: Verify that the channelset table (CST) has not been overlaid.



06C to 06F

06C

Explanation: A machine check interruptionoccurred because of a serious error in a channel.While attempting to check the channel paths toidentify the channel in error, the systemencountered one of the following:

• The disconnected channel path cannot beconnected to this processor.

• The channel path that was connected to thisprocessor at the time the error occurredcannot be reconnected to this processor.

Storage location X'414' contains the channelpath ID of the channel path the system wasattempting to connect to this processor.

Operator Response: Probable hardware error.Record the contents of storage location X'414'and call IBM for hardware support.


06D

Explanation: During restart processing, IOS hasfound a missing interruption handler (MIH)condition waiting on paging device ddd formore than one installation-specified period oftime. Storage location X'40C' contains thepaging device number ddd.

System Action: The system enters the wait state.

Operator Response: Examine paging device dddfor hardware malfunctions, such as the SELECTLOCK indicator being on for a disk device.Check control units and switching units forproper connections. Then restart the system. Ifthe device was just mounted, issue the VARYDEVICE ONLINE command to generate asimulated device end.


06E

Explanation: The operator has entered theVARY CHANNEL OFFLINE FORCEcommand. In order to take the channel offline,devices that are reserved on the channel must berereserved on alternate paths. The system couldnot issue message IEA019A.

System Action: The system remains in the waitstate.

Operator Response: Stop the processors that aresharing devices on the channel that is to beforced offline. Then restart the system.Message IEA421E or wait state code 0E6 isissued when the stopped processors can bestarted.


06F

Explanation: One of the following was detectedalong a path to a device:

• An inoperative control unit.• A channel error.• An undetermined error.

The device on the failing path is a pagingdevice. No device reservation or active I/Ooperation exists on the path to indicate whichsystem owns the device.

Location X'40C' contains the address of alocation that contains the address of an errorinformation area. The failing path is identifiedby the following fields in the information area:

• Offset 0 contains the 2-byte channel set ID,in hexadecimal.

• Offset 2 contains the 2-byte device address,in hexadecimal.

System Action: The device is disabled. Theprocessor waits for the operator to takecorrective action and enter a response.


078 to 09x

WT CDS

Operator Response: Verify that the device isowned by this operating system to ensure thatyour reply does not usurp another system'sownership of the device. Then, respond bystoring one of the following action codes inlocation X'30E':


01 Used to attempt to recover access to the devicethrough an alternate path, if one exists.

Warning: Data set integrity might be lost if thedevice is online to more than one system. In thiscase, quiesce any other systems that have access tothe device and check with the system programmerbefore responding with action code X'01'.

The system issues the unconditional reservecommand. If the command is successful, the deviceis taken out of the quiesced state and an attempt ismade to restart it. If the command is not successful,the system proceeds as if action code X'02' werestored.

02 Used to force the device offline, which prevents itfrom being allocated in the future. All I/O requeststo the device are terminated in error. The devicecannot be allocated again until the VARY commandis used to make the device available.

00 Used to attempt to restart the device withoutmaking any attempt at recovery. If the error recurs,this wait state code is issued again.

078

Explanation: The master catalog could not beopened successfully. Message IEC161I precedesthis wait state and identifies the specific failure.

Operator Response: Probable I/O error. Re-IPLthe system, and notify the system programmer.

Programmer Response: Correct the erroridentified by message IEC161I. If the error isnot correctable, the master catalog must berecreated as described in OS/VS2 SystemProgramming Library: System GenerationReference.

Problem Determination: Table I, items 2, 25a,34a, 29 or 30.

09x

Explanation: The processor (Py) in this waitstate was in a spin loop while waiting for anevent to occur on another processor (Pz). Wherthe spin loop exceeded the time normallyrequired for the event to occur, processor Pytried to issue the excessive spin notificationmessage IEE331A through the disabled consolecommunications facility (IEEVDCCR). Thesystem put the processor into this wait state forone of three reasons: the notification messagecould not be issued, the response could not beread, or a response was not entered within theallotted time of two minutes.

The possible awaited events, identified by x inthe wait state code, are:

x Awaited Event

1 RISGNL response2 Lock release3 RPSGNL response4 Restart resource5 Address space to QUIESCE6 PTLB SYNC7 Intersect release8 SIGP (equipment check)9 SIGP (operator intervention)A SIGP (check stop)B SIGP (not ready)C SIGP (invalid order)D SIGP (receiver check) -E Successful bind break release

System Action: Processor Py entered restartablewait state 09x, waiting for the operator tospecify an action and restart it.

Operator Response: On a 308x system, firstmake sure that your system-console screen isassociated with processor Py. After doing thisyou have two options in responding to this waitstate:

1. Allow the wait state to continue: it mightnot indicate a problem.

• Issue a program restart to processor Py,which will continue in the spin-loop foranother interval.


0E0 to 0E6

2. Initiate alternate CPU recovery (ACR) forprocessor Pz on which the expected event has

not occurred:

• Identify processor Pz by displaying theword pointed to by location X'40C' inprocessor Py This word contains the ID(0 - F) of processor Pz

• Stop the processor (Pz) with this ID.

• Store action code X'AA' at locationX'30E' of processor Py.

For additional information on alteringand displaying storage, consult theappropriate processor operator's guide.

• Finally, issue a program restart toprocessor Py.

• After ACR processing is complete, youcan issue the VARY CPU(z), ONLINEcommand to bring processor Pz backinto the configuration.

Problem Determination: Table I, items 2, 11, 29.0E0

Explanation: During execution of NIP,IEAVNP09 could not signal an online processorto update control register 14.

System Action: The system terminates the IPLprocess.

Programmer Response: Probable hardwareerror. Try to re-IPL the system.

If this wait state recurs, switch to uniprocessormode, and re-IPL the system. Then try toVARY the other processor online. If necessary,contact IBM for hardware support.

Problem Determination: Table 1, items 2 and 30.

0E1

Explanation: During VARY CPU OFFLINEprocessing, the CPU shutdown routine(IEEVSTOP) checked the CVTSPD field of theCVT (communication vector table) and foundthat the MSSF (maintenance and servicesupport facility) was inoperative. Without theMSSF, the reconfiguration modules cannot issueSIGP instructions. Therefore, the processorbeing taken offline cannot be stopped.

System Action: IEEVSTOP places zeros in theprefix register of the processor being takenoffline and places that processor in the 0E1 waitstate. The system continues as a uniprocessoron the processor not in the 0E1 wait state.

Operator Response: Report this wait state to thesystem programmer. Loss of the MSSF is aserious problem. Do not try to restart thestopped processor or issue any reconfigurationcommands.

Problem Determination: None.

0E6

Explanation: The operator has entered theVARY CHANNEL OFFLINE FORCEcommand to force a channel offline. Inresponse to message IEA019A or wait state code06E, the operator then stopped all theprocessors that are sharing devices on thechannel to be forced offline. Once the deviceson the channel have been rereserved on alternatepaths, the operator can start the processors thatwere stopped in response to message IEA019A.

Note: The system could not issue messageIEA421E.


Operator Response: Start the processors thatwere stopped to rereserve devices. Then restartthe system.



101 to 202

WT CDS

101

Explanation: The error occurred duringexecution of a GETMAIN macro instruction fora program executing in supervisor mode. Morebytes were requested from the system queue area(SQA) than were available.

Operator Response: Re-IPL the system. If thiscode occurs frequently, installation action isneeded to increase the space allowed for thesystem queue; more space should be specified atsystem generation time or in response tomessage IEA101A during system IPL.


102

Explanation: The error occurred duringexecution of a GETMAIN macro instruction fora program executing in supervisor mode. Morepages of real storage were requested for thesystem queue area (SQA) than were available.

Operator Response: Re-IPL the system. If thiscode occurs frequently, installation action isrequired to decrease the fixed real storagerequirements of the system.


103

Explanation: Module IEAVEES compared thecontents of storage with the contents of thecache in the receiving processor and found theydid not match.


Operator Response: Probable hardware error.Report this wait state code to the systemprogrammer.

Problem Determination: Table 1, items 11, 29.

201

Explanation: A failure has occurred during theexecution of the console communicationsaddress space create routine (IEAVN700). Thiswait state code is associated with messageIEA366W.

Bits 32 through 47 of the wait state PSWcontains a hexadecimal reason code:


8001 A failure occurred while creating the consolecommunications address space.

8002 A failure occurred in module IEAVN700.

Fccc An ABEND occurred. where ccc is the systemcompletion code.

Operator Response: Record the contents of thewait state PSW, and notify the systemprogrammer. Re-IPL the system.

Programmer Response: If the reason code is inthe format Fccc, refer to the description ofABEND ccc for problem determination. If thereason code is in the format 8xxx, refer to thefollowing problem determination.


202

Explanation: A failure has occurred during theexecution of the console communicationsaddress space initialization routine (IEAVN701).This wait state code is associated with messageIEA367A.

Location X'40C' (field PSAWTCOD in thePSA) contains a hexadecimal reason code:


00008001 An ESTAE environment cannot be established.

00008002 An error occurred during ATTACH processingof module IEAVMQWR or IEEVWAIT.

00008003 An error occurred during POST processing formodule IEAVN700.


A00 to A22

00008004 An error occurred during POST processing formodule IEAVN701.

00008005 An error occurred during updating of thecommand address space table.

0000Fccc An ABEND occurred, where ccc is the systemcompletion code.

Operator Response: Record the contents oflocation X'40C', and notify the systemprogrammer. Re-IPL the system.

Programmer Response: If the reason code is inthe format X'0000Fccc', refer to the descriptionof ABEND ccc for problem determination. Ifthe reason code is in the format X'00008xxx',refer to the following problem determination.


A00

Explanation: A DAT (dynamic addresstranslation) error occurred for a system addressspace. RTM (recovery termination manager)did not terminate the address space because theASCBNOMT and ASCBNOMD fields of theASCB show that the MEMTERM option of theCALLRTM macro instruction is not valid forthe address space.

System Action: The system issues messageIEA802W.

Programmer Response: Find and correct theDAT error, and re-IPL the system.

Problem Determination: Table I, items 2 and 18.

A01

Explanation: Either a predefined number ofhard machine check interruptions occurred onthe only online processor with input/outputcapability, or a hard machine check interruptionoccurred from which recovery is impossible.


Problem Determination: Table I, items 18, 30.To recover possible unrecorded machine checkerror records, see Table I, item 11.

A18

Explanation: IOS received an unsolicited deviceend interruption for a volume containing apaging data set. Volume serial verificationfailed for at least one of the following reasons:

• The device address contained a volume witha different volume serial number.

• An I/O error occurred while attempting toread the volume label.

• The device changed from ready to not readystatus (intervention required) by the timevolume verification attempted to read thevolume label.

System Action: The system enters this disabledwait state.

Operator Response: Probable operator error.Ensure that all volumes containing paging datasets are on the same device addresses as theywere at IPL; make sure that all devices areready. Re-IPL the system. If the systemreenters this wait state, try again.

Note: Repeated failure indicates that a devicecontaining a volume with a paging data set isgiving uncorrectable I/O errors while trying toverify the volume containing the data set.

Problem Determination: Table I, items 11, 29 or30.

A22

Explanation: An error occurred on one of theprocessors in a multiprocessing configuration.The processor is stopped manually whileanother processor in the configuration performsrecovery processing.

System Action: The processor on which theerror occurred waits for responses to the 'help'messages it sent to the console of the processorperforming recovery. The 'help' messages weresent when the error occurred.

Operator Response: Check the master console orits alternate for a description of the conditionscausing the problem, and perform the actionsrequested by any messages. The processor on


A23 to B01

WT CDS

which the error occurred restarts automaticallyafter it receives the replies to the messages itsent.

A23

Explanation: This wait state code is associatedwith message IGF910W. A program checkinterruption occurred while the machine checkhandler was being executed on the only onlineprocessor. No recovery was possible.


Problem Determination: Table I, item 18, 30.To recover possible unrecorded machine checkrecords, see Table I, item 11.

A24

Explanation: This wait state code is associatedwith message IGF910W. A loop was detectedwhile the machine check handler was beingexecuted on the only online processor. Norecovery was possible.



A25

Explanation: A machine check interruption hasoccurred. The machine check interruption codeindicates that system damage has beensustained. No recovery was possible.


Problem Determination: Table I, items 18, 30.To recover possible unrecorded machine checkrecords, see Table I, item 11.

A26

Explanation: A machine check interruption hasoccurred. The machine check interruption codeis invalid. No recovery was possible.



A27

Explanation: A processor terminated for one ofthe following reasons:

• The machine check handler externally linkedto a routine in which a machine checkinterruption or a program checkinterruption occurred.

• The processor issued a malfunction alert(MFA) and did not enter or remain incheck-stop state.

• A malfunction alert was simulated when theoperator replied ACR to message IEE331A,and the processor did not enter or remain incheck-stop state.

System Action: The processor enters a disabledwait state. Processing continues on otherprocessors.


Problem Determination: Table I, items 18, 30.To recover possible unrecorded machine checkrecords, see Table I, item 11.

B01

Explanation: The 3203/3211 utility hascompleted normally.

Operator Response: Verify the printed image,and restart the system.


B02 to B0C

B02

Explanation: This wait state code is issued bythe 3203/3211 utility. A control card is missingor out of order. The JOB and END controlcards must be the first and last cardsrespectively. The DFN, UCS, and FCBstatements can be included in any order.

Operator Response: Correct the control cardsequence, insert any missing cards, and rerunthe program.


B03

Explanation: This wait state code is issued bythe 3203/3211 utility. The JOB statement isincorrect.

Operator Response: Correct the JOB statement,and rerun the program. Have the 3203/3211utility and control cards available.


B04

Explanation: This wait state code is issued bythe 3203/3211 utility. The DFN statement isincorrect.

Operator Response: Correct the DFN statement,and rerun the program. Have the 3203/3211utility and control cards available.


B05

Explanation: This wait state code is issued bythe 3203/3211 utility. The UCS statement isincorrect.

Operator Response: Correct the UCS statement,and rerun the program. Have the 3203/3211utility and control cards available.


B06

Explanation: This wait state code is issued bythe 3203/3211 utility. The FCB statement isincorrect.

Operator Response: Correct the FCB statement,and rerun the program. Have the 3203/3211utility and control cards available.


B07

Explanation: This wait state code is issued bythe 3203/3211 utility. The END statement isincorrect.

Operator Response: Correct the END statement,and rerun the program. Have the 3203/3211utility and control cards available.


B0A

Explanation: This wait state code is issued bythe 3203/3211 utility. An external interrupt hasoccurred.

Operator Response: Rerun the program.

B0B

Explanation: This wait state code is issued bythe 3203/3211 utility. A program checkinterrupt has occurred.

Operator Response: Have the 3203/3211 utilityand control cards available.


B0C

Explanation: This wait state code is issued bythe 3203/3211 utility. A machine checkinterrupt has occurred.

Operator Response: Execute the SEREPprogram, and save the output. Rerun the job.



WT CD

B11 to B1C

B11

Explanation: This whit state code is issued bythe 3203/3211 utility. The reader is not online.This error will occur when the reader's controlunit has no power or when the control unit hasbeen switched off the I/O interface.

Operator Response: Put the specified controlunit online, and rerun the program. If the errorrecurs, call IBM for hardware support.

B12

Explanation: This wait state code is issued bythe 3203/3211 utility. The reader is not ready.

Operator Response: Ready the reader, and rerunthe program.

B13

Explanation: This wait state code is issued bythe 3203/3211 utility. The reader is not ready.

Operator Response: If the error is not apparent,display low storage location 3 for senseinformation. An interpretation of sense bitsettings can be found in the componentdescription manual for the control unit beingused. Correct the faulty condition, and clear thereader check. Rerun the program. If readerchecks occur frequently, use a card guide tocheck for off-punched cards. If the cards arepunched correctly and are in good conditionand read checks continue, call IBM forhardware support.

B14

Explanation: This wait state code is issued bythe 3203/3211 utility. A reader channel errorhas occurred.

Operator Response: Probable hardware error.Rerun the job.


B15

Explanation: This wait state code is issued bythe 3203/3211 utility. No device end isindicated on the reader.



B19

Explanation: This wait state code is issued bythe 3203/3211 utility. The printer is not online.This error will occur when the printer's controlunit has no power, when the control unit hasbeen switched off the I/O interface, or when thecontrol unit is not a part of the system.

Operator Response: Ensure that the address ofthe printer specified in the DFN statement iscorrect. Ensure that the control unit is online,and rerun the job. If the error recurs, call IBMfor hardware support.

B1B

Explanation: This wait state code is issued bythe 3203/3211 utility. A unit check has occurredon the printer.

Operator Response: If the error condition is notapparent, display low storage location 2-7 forsense information. An interpretation of sensebit settings can be found in IBM 3203/3211Printer and 3811 Control Unit ComponentDescription. Correct the faulty condition, andrerun the job. If the problem recurs, call IBMfor hardware support.

B1C

Explanation: This wait state code is issued bythe 3203/3211 utility. A printer channel errorhas occurred.




B1D to CCC

B1D

Explanation: This wait state code is issued bythe 3203/3211 utility. No device end isindicated on the printer.

Operator Response: Probable hardware error.Rerun the job. If the error recurs, call IBM forhardware support.

B20

Explanation: The operator executing thestand-alone version of the input/outputconfiguration program (IOCP) terminatedIOCP.


B21

Explanation: A program check interruption hasoccurred during execution of the stand-aloneversion of the input/output configurationprogram (IOCP).



B22

Explanation: A machine check interruption hasoccurred during execution of the stand-aloneversion of the input/output configurationprogram (IOCP).



B23

Explanation: An unrecoverable I/O error hasoccurred during execution of the stand-aloneversion of the input/output configurationprogram (IOCP).



B24

Explanation: During execution of thestand-alone version of the input/outputconfiguration program (IOCP), IOCPencountered an error in the hardware processorcontroller and cannot communicate with theIOCP operator.



CCC


• In a uniprocessor configuration, when theprocessor executed the QUIESCE function,the system was placed in restartable waitstate CCC as part of normal operation.

• In a multiprocessor configuration,processors on which the QUIESCE functionis not executing are placed in a manual stopstate as well as the disabled wait state. Theprocessor executing the QUIESCE functionis then placed in disabled wait state CCC,but not in a manual stop state.

This wait state code is associated with messageIEE082I.

Operator Response: Invoke the restart function.


WT CDS

E02

E02

Explanation: A permanent input/output erroroccurred while the IBM 2250 Display Unit wasbeing used as the primary console. At the timethe error occurred, no alternate console wasavailable.

System Action: The sense bytes are placed in thetwo high-order bytes of register 15, and the

status bytes are placed in the two low-orderbytes of register 15. Then the system is placedin wait state E02.

Operator Response: If an alternate console isavailable, start the system again, using thealternate console. If an alternate console is notavailable, call IBM for programming support.



UNCDED

Uncoded Wait States

A system wait state is indicated in one of severalways, depending on the model of the processorbeing used. It might be indicated by the WAITlight on the operator control section of the systemcontrol panel, the appearance of the word WAITon the display console, or by a meter showing thepercent of active processor time. A system waitstate means that no instructions are being processedby the processor.

A system wait state is entered when bit 14 of thecurrent program status word (PSW) is set to 1. Toexit from this state, an interruption or initialprogram load (IPL) must occur to change thecurrent PSW. When the right half of the PSW doesnot match any of the wait state codes listed in thispublication, an uncoded wait state is occurring.

Explanation: An uncoded wait state could resultfrom normal operation; for example, the systemmight wait for a series of specified operator actionsbefore it can resume processing. An uncoded waitstate can also be a symptom of abnormal operation;for example, the system might enter a wait state if ahardware malfunction causes an input/outputinterruption to be lost.

System Action: The system may exit from anuncoded wait state without operator intervention(1) if an input/output interruption occurs, forexample when a user at a terminal signals attention,or (2) when an external interruption occurs, forexample when a specified time interval has expired.Otherwise, the system continues to wait for anappropriate operator response before it cancontinue processing.

Operator Response: If you can communicate withthe system through the master console device, dothe following in order:

• Enter a DISPLAY R,LIST command. Thesystem responds with message IEE110I orIEE112I if any operator action is required forprevious messages. This required action caninclude replies to messages or mounting ofvolumes. If all system requests have beensatisfied, message IEE111I is issued. Forsystems using JES3, enter *I,R and *I,R,S froma JES3 console. *I,R displays all outstandingmessages except SETUP messages. *I,R,Sdisplays all SETUP messages.

• Scan the console log to make sure that allmessages requiring operator action have beensatisfied. If JES2 issued message $HASP099,which indicates all JES2 functions werecompleted, the system has no more batch work,but TSO users might be logged on.

• Enter a DISPLAY A,LIST command todetermine if there are active tasks. The systemmight be waiting for work. For systems usingJES3, you can enter *I,A from a JES3 consoleto display all jobs currently active on one or allprocessors.

• Issue a DISPLAY U command. The systemresponds with message IEE450I, which lists thestatus of the devices in the system. The datalisted includes indications of BSY (busy), MTP(mount pending), NRD (not ready), and otherstatus information that might be useful to helpyou determine why the system is in the waitstate. (This command might cause a lengthytype-out.)

Uncoded Wait States UWS- 1

• As a last resort, issue the following sequence ofcommands until the uncoded wait statecondition is corrected:

1. If a SYS1.DUMP data set was createdduring or before nucleus initialization, issuethe DUMP command to obtain a storageimage dump of the condition causing thewait. Save the output in case the uncodedwait cannot be resolved.

If the waiting processor is a JES3 localprocessor, it might be useful to request adump of the JES3 global processor'sstorage.

2. For systems using JES2, enter $H Q toprevent initiation of new jobs. For systemsusing JES3, enter *F,Q,H from a JES3console to place the entire job queue in ahold status.

3. Enter MN JOBNAMES,T to getinformation about jobs starting andstopping.

4. Enter DISPLAY A,LIST to get current jobexecution status. For systems using JES3,you can enter *I,A from a JES3 console todisplay all jobs currently active on one orall processors.

5. Cancel jobs in reverse order of theirimportance and request dumps(CANCEL,jjj,DUMP).

6. Enter DISPLAY A,LIST on a hardcopyconsole and TRACK A,LIST on a graphicsconsole to monitor the changingenvironment. For systems using JES3,enter *I,A from a JES3 console to displayall jobs currently active on one or allprocessors.

7. For systems using JES2, enter $A Q toresume normal processing. For systemsusing JES3, enter *F,Q,R from a JES3console to release the entire job queue.

If you cannot communicate with the systemthrough the master console device, do the followingin order:

• Perform the RESTART function to activate thesystem's software recovery mechanisms.

• If the wait conditions are not eliminated, thenfollow the Problem Determination instructionslisted below.

Problem Determination: If the problem cannot becorrected or communication with the system cannotbe established, do the following before calling IBMfor programming support:

• Record the contents of the current PSW.

• Have the hardcopy log available.

• Perform the STORE STATUS function.

• Execute the AMDSADMP service aid programto dump the contents of real storage andselected areas of the page data sets on tape.

• After restarting the system, execute the GOfunction of the AMDPRDMP service aid toprint the real storage portion of the dump tapeproduced by AMDSADMP.

• Save both the tape from AMDSADMP (shouldfurther information from the tape be required)and the listing from AMDPRDMP.

If you cannot restart the system, execute thehardware system test for your system before callingIBM for hardware support.

UWS-2 OS/VS Message Library: VS2 System Codes

SADMP

Stand-Alone Dump Wait State Codes

During execution of a stand-alone dump, theSADMP program loads wait state codes in the righthalf of the PSW in order to communicate with theoperator. These codes appear in the console lightsas the last four bytes of the current PSW.

The SADMP program is described in OS/VS2 MVSSystem Programming Library: Service Aids.

X'00'

Explanation: The stand-alone dump programterminated normally. All tapes, if used, weretape marked, rewound, and unloaded.


X'01'-'27'

Explanation: SADMP terminated, but could notwrite to the console. The code, converted todecimal, indicates the message ID that could notbe written.

Operator Response: Check the message ID todiagnose the problem. Correct the error beforere-executing SADMP.

X`28'

Explanation: SADMP could not perform virtualdumping. The CVT was written to the workfileand could not be retrieved.


X`29'

Explanation: SADMP could not perform virtualdumping. The CVT pointer at X'4C' is invalid.


X'2A'

Explanation: The CVT pointer to the LPAdirectory is zero. If the value is valid, systeminitialization was incomplete. If the value isinvalid, SADMP cannot continue withoutoverlaying unknown real storage data.


X'2B'

Explanation: The segment table pointer atX'31C' is invalid. SADMP cannot perform

virtual dumping.


X'2C'

Explanation: An external interruption or aprogram check occurred while SADMP wasperforming termination processing.

Operator Response: To diagnose the problem inSADMP processing, restart SADMP.

X'2D'

Explanation: SADMP could not initialize theauxiliary storage management function.


X'2E'

Explanation: The operator canceled SADMP bycausing an external interrupt.


Stand-Alone Dump Wait State Codes SAD-1

X'2F'

Explanation: SADMP terminated afterencountering the maximum allowable number ofinternal errors.


X`30'

Explanation: A permanent input/output erroroccurred on an output device.


X`31'

Explanation: The page vector table (PVT)required for dumping is invalid.


X'32'

Explanation: SADMP terminated afterencountering the maximum allowable number ofmachine check errors.


X'FD'

Explanation: The precursor routine cannotobtain the dump program from theSYS1.PAGEDUMP data set.

Operator Response: Reinitialize the SADMPprogram.

X'FE'

Explanation: The precursor routine cannotlocate the SYS1.PAGEDUMP data set on theIPL volume. The format-4 DSCB (data setcontrol block) on this volume may be invalid.

Operator Response: Reinitialize the SADMPprogram. If the format-4 DSCB is invalid, useanother volume or correct the DSCB.

X'FF'

Explanation: The specified console address isnot available.

Operator Response: Ready a console of thesame type that was specified in the SADMPmacro instruction. On an MP (multiprocessing)system, this console must be addressable by theIPLed processor.

X'4000'

Explanation: A machine check interruptionoccurred.

Operator Response: Execute the SEREPprogram to diagnose the machine checkcondition.

X'5000'

Explanation: PSW restart was attempted.


X'E00cuu'

Explanation: SADMP is waiting for interventionon device cuu.

Operator Response: Ready device cuu.

X'F00cuu'

Explanation: SADMP is waiting for an I/Ointerruption from device cuu for a started I/Ooperation.

Operator Response: Ready device cuu.

X'FFFFFF'

Explanation: SADMP is currently executing onanother processor.


SAD-2 OS/VS Message Library: VS2 System Codes

LOOPS

Loops

A loop is the repeated execution of a sequence ofinstructions until a terminal condition occurs. Ifthe terminal condition does not occur, the sequenceof instructions will be endlessly executed, and, insuch a case, meaningful work is not accomplished.At times, it may be necessary for the operator toterminate such endless looping by canceling thelooping job.

You can recognize a loop by:

• A steady glow in the lights of the systemcontrol panel with the SYSTEM light on.

• A pointless recurrence of input/output activity;for example, tape oscillating.

• A job that does not change status for a longperiod of time.

• The PSW display appears to be repeating thesame addresses.

Explanation: A loop can result from severaldifferent, causes, some of which are:

• A deliberate loop designed by the programmer.This might be a debugging loop built duringprogram testing. Or it might be a loop to pollfor an event before it will exit.

• An apparent loop. This situation is notactually a loop. It can occur, for example,when a scientific data reduction program isdoing a lengthy repetitive operation on a largearray of numbers.

• A loop due to a logic error or coding error bythe programmer.

• A loop due to a logic error in a systemcomponent.

• A loop due to incorrect setup by the operator.

• A loop due to an error in the control program.

• A loop due to a hardware malfunction.

System Action: The system may exit from a loop,without operator intervention, if the execution timeof the program exceeds the time limit specified inthe TIME parameter of the EXEC statement or thestandard time limit of the RDR procedure,assuming your installation included interval timingin the system.

Operator Response: If you can communicate withthe system through the master console device, enterDISPLAY A,LIST. The system will list all activetasks. Use this command frequently. Identicalentries occurring on successive uses of theDISPLAY A command beyond the estimatedexecution time of a job indicate a possible loop.

If you are reasonably certain the program is in anendless loop, enter CANCEL jjj,DUMP toterminate the job. The programmer will receivesystem completion code 122 with the output. Code122 directs the programmer to take appropriateactions. A copy of the master console sheet shouldaccompany the output if the programmer calls IBMfor programming support.

Generally, if you cannot communicate with thesystem through the master console, recordinformation about the loop.

On processors that support the operator's systemcontrol (SC) frame, you can record the informationby selecting the loop recording option on the SCframe. Refer to Step 1 for instructions about whento select the loop recording option. This optionrecords approximately 470 values of the instructioncounter in the form of an instruction trace. Thisinformation becomes available when you write astand-alone dump or when the MVS SVC dumpprogram is invoked. Use the MVS print dump

Loops LOP-1

program (AMDPRDMP) to format and print eitherdump.

If you cannot communicate with the systemthrough the master console, do these specific steps:

Step 1: The first step depends on your processorand configuration.

• If your processor does not support the operatorSC frame, your first step depends on yourinstallation's priorities. Talk to your systemprogrammer.

If the system programmer wants specificinformation about the loop to use later indebugging, do step 3 and then step 2(RESTART).

If your installation's first priority is to get thesystem running again, go immediately to step 2.

In either case, if the system is still looping afteryou do the RESTART, proceed with steps 3and 4.

• If you have a uniprocessor and your processorsupports the operator's SC frame, select theloop recording option. After this optionrecords the instruction trace, it puts the systemin the STOP state.

• If you have an MP or AP configuration, andyour processors support the operator's SCframe, select the loop recording option on theprocessor that is looping. This option recordsthe instruction trace only on the loopingprocessor, but then puts both processors in theSTOP state. Activate the loop recording optionon the second processor.

Step 2: Perform the RESTART function.

If your processor supports the operator's SC frame,do the RESTART with REASON 0.

If you have an MP or AP configuration, do theRESTART on the processor that was looping.

Then perform the global MP/AP start function onthat same processor to start the second processor.

If doing steps 1 and 2 does not eliminate the loop,do steps 3 and 4 before you call IBM forprogramming support.

Step 3: Record information about the loop.

If your processor does not support the operator'sSC frame, do the following:

• Press stop.

• Record the contents of the PSW and thegeneral purpose registers.

• Press start.

• Repeat the actions in the previous three bulletsten or more times in order to record thecontents of the PSW and the registers at ten ormore different locations in the loop.

If your processor or processors support theoperator's SC frame, select the loop recordingoption.

Step 4: Write a stand-alone dump; remember toperform the STORE STATUS function first, if yourprocessor does not have the automatic store statusfunction.

After you write the stand-alone dump, re-IPL yoursystem and use the print dump program(AMDPRDMP) to format and print the dump.

If you cannot re-IPL the system, execute thehardware system test appropriate for your system.Do this before you call IBM for hardware support.

Programmer Response: The actions that theoperator and the system programmer take torecover from a loop may cause your job toabnormally terminate. Refer to the documentationfor the system completion code associated with theabnormal termination. This code is most likely tobe 122, 222, 322, or 071.

LOP-2 OS/VS Message Library: VS2 System Codes

PROB

Problem Determination

Problem determination is the activity required toidentify a failing hardware unit or program anddetermine who is responsible for support.

Problem determination is accomplished by usingprocedures specified by IBM. In some cases, theseprocedures may be initiated by a message or codewhich requires operator or programmer response.The response may include the requirement foradditional problem-related data to be collected and

TABLE I

If the problem recurs, follow the problem determination aidsspecified by the associated message or code before calling IBMfor support.

1. If MSGLEVEL=(1,1) was not specified in the JOBstatement, specify it and rerun the job.

2. Save the console sheet from the primary console. Forsystems with remote consoles, save the remote console sheet.In systems with Multiple Console Support (MCS), save acopy of the hard copy log.

3. Save the job stream associated with the job.

4. Save the system output (SYSOUT) associated with the job.

5. Make sure that the failing job step includes a:

a. SYSABEND DD statement.b. SYSUDUMP DD statement.c. PLIDUMP DD statement.d. SYSMDUMP DD statement.

6. Make sure that the PARM parameter of the EXECstatement specifies the following:

a. MAPb. LISTc. DIAGd. MSG=APe. CORE, if applicablef. XREFg. DUMP

7. If SMP is used to make all changes to the system, executethe LIST CDS and LIST PTFBY functions of SMP to

will attempt, where possible, to indicate "probable"failure responsibility.

Problem determination information is included forapplicable messages and codes under the heading"Problem Determination." Standard problemdetermination actions are identified as items ofTables I and II. Unique actions are identifiedfollowing the list of standard actions to be taken.In any case, it is intended that the specified actionsbe taken before calling IBM for support.

obtain a list of the current maintenance from the SMPcontrol data set (CDS).

If any changes are made to the system without using SMP,execute the LISTIDR function of the AMBLIST service aidprogram to obtain a list of all members with a PTF or localfix, and save the output. Execute the program against the:

a. SYS1.LINKLIB data set.b. SYS1.SVCLIB data set.c. library containing the program that issued the messaged. SYS1.LPALIB data set.

8. Execute the IMCJOBQD (stand-alone) or IMCOSJQD(system-assisted) service aid program to obtain a formattedcopy of the contents of the SYS1.SYSJOBQE orSYS1.SYSWADS data sets, SWADS or the resident job list.(Not applicable for VS2 MVS.)

9. Execute the AMBLIST service aid program to obtain:

a. an object module listing, specifying the LISTOBJfunction.

b. a load module map and cross-reference listing,specifying the OUTPUT=BOTH option of theLISTLOAD function.

10. Have a copy of the Message Control Program (MCP)available.

11. Execute the AMDSADMP service aid program to dump thecontents of real storage and page data sets on magnetictape.

After restarting the system, execute the appropriate functionof the AMDPRDMP service aid program to print therequired portion of the dump tape produced byAMDSADMP.

Problem Determination PRB-1

Save both the tape from AMDSADMP (should furtherinformation from the tape be required) and the listing fromAMDPRDMP.

12. Execute the SEREP program, and save the resulting output.

(Note: the SEREP program is not supported on processorsin the 4300 series.)

13. Save all the associated output.

14. The normal response to this message requests theprogrammer/operator to execute a specific program. Saveall output from that program.

15. Save the program listing associated with the job.

16. Save the dump.

17. Have the system generation (SYSGEN) output availablefrom:

a. Stage Ib. Stage II

18. Execute the EREP service aid, to dump the SYS1.LOGRECdata set and save the resulting output.

For MSS, execute the following program to dump theSYS1.LOGREC data set:

a. Service aid IFCISDAOb. Program ISDASDAO with the DETAIL(ALL)

parameter.

19. Save the assembly listing associated with the job.

20. Save the control cards associated with the job.

21. Save the compiler output associated with the job.

22. Save the source input associated with the job.

23. Save the source program listing associated with the job.

24. Run OLTEP diagnostics for the problem device and savethe output.

25. Execute the IEHLIST system utility program to obtain a listof the:

a. volume table of contents of the associated volume,specifying the FORMAT option.

b. volume table of contents of the associated volume,specifying the DUMP option.

c. directory of the associated data setd. (Not applicable for MVS.)

26. Execute the IEBPTPCH data set utility to print the:

a. directory of the applicable data set.b. applicable data set.c. applicable member.d. applicable procedure.

27. Have the linkage editor/loader map available.

28. Save the associated volume.

29. Contract IBM for programming support.

30. Contract IBM for hardware support.

31. Save the trace output data set.

32. Print the GTF trace data set with the AMDPRDMP serviceaid program using the EDIT statement.

33. Print the associated SVC Dump data set, using theAMDPRDMP service aid with the GO statement.

34. Execute the Access Method Services LISTCAT commandto:

a. list the contents of the applicable catalog.b. list the catalog entries for the applicable objects and

any related objects.

35. Execute the following Access Method Services command:

a. The MSS LISTMSF command for mountable volumes.b. The MSS LISTMSF command with the

CARTRIDGES parameter.c. The PRINT command to list the contents of the mass

storage volume control inventory data set.d. The LISTMSVI command.e. The LISTMSF command with the ALL parameter.

36. Execute the Access Methods Services PRINT command toprint the repair workfile.

37. Execute the AMASPZAP service aid program using theABSDUMP statement to print_ the contents of theapplicable:

a. Data set.b. Track.

38. Execute the Access Method Services AUDITMSS commandwith the following parameter:

a. The CHECK parameter.b. The MAP parameter.c. The READLABEL parameter.

39. Execute the Access Method Services CHECKMSScommand.

40. Execute the Access Method Services COMPARETcommand.

41. Execute the Access Method Services DUMPMSS commandto dump the following:

a. Formatted mass storage control storage.b. Mass storage control main storage.c. Mass storage control extended storage.d. Formatted Staging Adapter storage.e. Staging Adapter main storage.f. Staging Adapter extended storage.g. Mass storage control tables.

42. Save the latest output from the Mass Storage Control TableCreate program.

PRB-2 OS/VS Message Library: VS2 System Codes

PROF)

43. Display units for units associated with the problem area. Ifspecific unit(s) is not know, display range of all virtualunits. See your configuration path chart for address ranges.

44. Obtain the RACF profile of the associated data set, whereapplicable.

45. Stop the processor and use the hardwareALTER/DISPLAY facility to display:

a. all general purpose registers.b. the PSW.c. main storage locations 0 through 200 (hexadecimal)

and 7000 through 7080 (hexadecimal).

46. If the AMDSADMP program resides on tape, save the tape.If the AMDSADMP program resides on disk, use theDUMP feature of IEHDASDR to print theSYS1.PAGEDUMP data set and cylinder 0 track 0 of thisresidence disk.

47. Save the output (listings) of the stage 1 and stage 2AMDSADMP initialization jobs.

48. Follow the procedures for item 9b of this table for loadmodules AMDSAPGE, AMDSAPRO and AMDSALDR of

SYS1.LINKLIB. Use IEBUPDTE or IEBPTCH to printthe AMDSADMP and AMDSADM2 macros from

SYS1. MACLIB.

49. Save the AMDSADMP dump output (tape or listing).

50. If the program seems to be looping, use the display PSWfeature of the hardware ALTER/DISPLAY facility alongwith the hardware instruction Step facility to trace the loop,instruction by instruction.

51. If there is an error in the contents of a page data set dump,restart the system using a different page data set, then dumpthe original page data set using the DUMP feature ofIEHDASDR.

52. Use IEBCOPY to unload SYS1.IMAGELIB to tape.

53. Have a list of RACF-defined entities available.

54. Contract your IBM system engineer.

55. Save the console sheets from all active global resourceserialization systems, and from any systems that arerestarting or joining the global resource serializationcomplex.

TABLE IIGTF for Problem Determination

Format 1: Tracing Without Prompting for Event Keywords

Before reproducing the problem, have the system operator issue aSTART GTF command specifying tape output, MODE=EXTand TIME=YES. In response to message AHL100A she shouldtype TRACE=opt, where opt is the trace option indicated forthe particular message or code, within the text of his reply.

When data for the problem has been recorded, run theAMDPRDMP service aid program using the EDIT statement toformat the trace output, specifying DDNAME=(ddname of thetrace data set).

Format 2: Tracing With Prompting for Event Keywords

Before reproducing the problem, have the system operator issue aSTART GTF command specifying tape output, MODE=EXTand TIME=YES. In response to the message AHL100A sheshould specify the trace options indicated for the associatedmessage or code within the text of her reply. Then, in responseto the message AHL101A, she should specify the event keywordsalso indicated with the associated message or code.

When data for the problem has been recorded, run theAMDPRDMP service aid program using the EDIT statement to

format the trace output, specifying DDNAME=(ddname of thetrace data set).

Format 3: Specialized Tracing Action

Before reproducing the problem, have the system operator issue aSTART GTF command specifying tape output, MODE=EXTand TIME=YES. In response to message AHL100A she shouldtype 'TRACE=SYS,USR,SLIP'. The DD statement for a dataset in error should specify DCD=DIAGNS=TRACE.

When data for the problem has been recorded, execute the EDITfunction of AMDPRDMP specifying the options SYS,USR=FFF, and SLIP.

Format 4: Specialized Tracing Action for VSAM

Before reproducing the problem, have the system operator issue aSTART GTF command specifying tape output, MODE=EXTand TIME=YES. In response to message AHL100A she shouldtype 'TRACE=SYS,USR'. The DD statement for a data set inerror should specify AMP=TRACE.

When data for the problem has been recorded, execute the EDITfunction of AMDPRDMP specifying the options SYS andUSR=(FFF,FF5).

Problem Determination PRB-3

TABLE III

If a problem occurs in JES3, one or more of the following stepsmay be taken to assist in determining the cause:

1. Take a stand-alone dump of the system by specifyingDUMP=PRDMP on the OPTIONS card in theinitialization deck and save the output (SYS1.DUMPnn).

2. Take a standard dump of the system by specifyingDUMP=JES on the OPTIONS card in the initializationdeck and save the output (JESABEND).

3. Take an operating system dump including the nucleus andSQA by specifying DUMP=MVS on the OPTIONS card inthe initialization deck and save output (SYSABEND).

4. Save the MLOG listing or get a print of DLOG.

5. Provide listing of initialization deck (JES3OUT).

6. Provide console log from initialization.

7. Ascertain OS/VS level and JES3 PTF level.

8. Provide OS/VS nucleus LOADMOD map.

9. Issue *F T,L=linename, SNAPON and *X RJPSNPS.

10. Issue *F T,L-linename,TRCEON. This will give an RJPevent trace on the MLOG console. Save MLOG output.

11. Take a system dump by placing an INTDEBUG,n,message-text$$ card in the initialization deck. Themessage-text field is compared for occurrences of the chosen

message. The n field specifies the number of messageoccurrences before the system is dumped.

12. Issue *X DISPLAY and save output.

13. Issue *X DISPLAY,SNAPS and save the output.

14. Rerun job with //*PROCESS CBPRNT and save output.

a. After Interpreter DSPb. After Main Servicec. After Input Service

15. Rerun job with EXEC PGM=JCLTEST and save output.

16. Rerun job with EXEC PGM=JSTTEST and save output.

17. Rerun job with TYPRUN=SCAN specified on JOB cardand save output.

18. Issue *X DISPDJC when problem occurs and save output.

19. Restart system with specifying a start type of WA(Warmstart with queue analysis) and save output(JES3SNAP).

20. Check SYSMSG data set for error indications.

21. Provide a listing of the JES3 startup procedure, containingall JCL used to start the subsystem.

22. Save the IOERR trace that will be printed.

23. Rerun job with DEBUG=All immediately followingPROCESS CI or PROCESS RI card.

PRB-4 OS/VS Message Library: VS2 System Codes

CD/MOD

Appendix: Code to Module Tables

This appendix contains two tables. The first is forsystem completion codes (ABEND codes); thesecond is for wait state codes.

The tables identify the modules that detect the needfor each code and the modules that issue the code.

Appendix: Code to Module Tables CMT-1

System Completion Code to Module Table

SystemCompletionCode

ModuleDetecting

ModuleIssuing

022 IGTDSR IGTDSR028 IEAVAMSI IEAVAMSI

IEAVFXLD IEAVFXLDIEAVFXLD IEAVPSIIEAVOUT IEAVPSIIEAVPIOI IEAVPIOIIEAVPSI IEAVPSIIEAVRCF IEAVRCFIEAVRCV IEAVRCVIEAVSWIN IEAVSWINIEAVWND IEAVWNDILRCMP IEAVEPC

02C HASPFSSM HASPFSSMHASPWARM CALLRTM

047 IEAVESVC IEAVESVCIGC109 IGC109IGC116 IGC116IGC122 IGC122

04D IEAVGM00 IEAVGM00IEAVGM03 IEAVGM03

054 IEFSJBLD IEFSJBLDIEFSJDEF IEFSJDEFIEFSJDEL IEFSJDELIEFSJFND IEFSJFNDIEFSJJDV IEFSJJDVIEFSJEXT IEFSJEXTIEFSJGET IEFSJGETIEFSJPUT IEFSJPUTIEFSJRET IEFSJRETIEFSJUPD IEFSJUPDIEFSJWRT IEFSJWRTIEFSJINT IEFSJINT

06C IEAVTSLP IEAVTSLP

06D IEAVTADR IEAVTADR

06E IEAVTGLB IEAVTGLBIEAVTLCL IEAVTLCL

06F IEAVTRT1 IEAVTRT1

072 IEAVEDSO IEAVEDSO

073 IEAVELK IEAVELK

074 IEAVELKR IEAVELKR

075 IEAVESCO IEAVESCO

076 IEAVEMCR IEAVEMCR


ModuleDetecting

ModuleIssuing

077 IEAVC700 IEAVC700IEAVG700 IEAVG700IEAVMNTR IEAVMNTRIEAVQ700 IEAVQ700

078 IEAVAR00 IEAVAR00IEAVAR02 IEAVAR02IEAVAR03 IEAVAR03

079 IEAVAR04 IEAVAR04

07A IEAVAR00 IEAVAR00IEAVAR02 IEAVAR02

07B IEAVEDR IEAVEDRIEAVERI IEAVERIIEAVERP IEAVERP

07C IEAVESPR IEAVESPR

07E IEEVDEV IEEVDEV

07F IEAVECHO IEAVECHO

081 IEAVEQR IEAVEQRIEAVSQA IEAVSQA

082 IEAVPRTO IEAVGPRR

083 ILRSLSQA ILRSLSQAILRSRT ILRSRT

084 ILRCMP ILRCMPILRPTM ILRPTMILRSWPDR ILRSWPDR

085 ILRSAV ILRSAV

086 ILRVSAMI ILRVSAMI

087 ILRSAV ILRSAVILRACT ILRACTILRRLG ILRRLGILRVSAMI ILRVSAMIILRTMRLG ILRTMRLG

0A 1 IGG0193Y IGG0193Y

0A2 IGG0203Y IGG0203Y

0A3 IGG019OE IGG019OE



0AE IECVRSTS IECVRSTS

CMT-2 OS/VS Message Library: VS2 System Codes

CD/MOD

System Module ModuleCompletion Detecting IssuingCode

0B0 IEFQB550 IEFQB550IEFQB555 IEFQB555

IEFQB580 IEFQB 580

0B1 IEFJCNTL IEFJCNTLIEFJJCLS IEFJJCLSIEFJACTL IEFJACTLIEFJWTOM IEFJWTOM

0B2 IEFJJCLS IEFJJOBS

0B3 IEFJACTL IEFJACTL

0B4 IEFJNCTL IEFJNCTL

0B5 IEFJNCTL IEFJNCTL

0B7 IEEMPDM IEEMPDMIEEMPS03 IEEMPS03

IEEMPVST IEEMPVSTIEEVPTH IEEVPTH

0B8 IEFJSWT IEESB605

IEESB601 IEESB605

0B9 IEESB605 IEESB605

0BA IEFSD162 IEFSD162IEFSD166 IEFSD166

IEFSD605 IEFSD605

0BB IEFSD263 IEFSD263

0BD IEEMB816 IEEMB816

0BE IEEMB809 IEEMB809

0BF IEEMB816 IEEMB816

0Cx IEAVEPC IEAVEPC(wherex=1-F)

IEFAB4FC IEFAB4FC

0D2 IEAVEPC IEAVEPC

0D3 IEAVEPC IEAVEPC

0D9 IEAVPIX IEAVTRT1

0F8 IEAVESVC IEAVESVC

0F9 IEAVESVC IEAVESVC

0FA IEAVESVC IEAVESVC

0FB IEAVEPC IEAVEPC

101 IEAVGM00 IEAVGM00IEAVSY50 IEAVSY50

102 IEAVGM00 IEAVGM00

IEAVSY50 IEAVSY50


ModuleDetecting

ModuleIssuing


106 IEAVLK01 IEAVLKOO

10A IEAVGM00 IEAVGM00

10B IEAVRT01 IEAVRT01

10D IEAVTRTC IEAVTRTC

10E IEAVTBOO IEAVTBOO

122 IEE3703D IEE3703D

128 IEAVTBOO IEAVTBOO

12A IEAVEATO IEAVEATO

12C IEAVECHO IEAVECHO

12E IEAVRTOO IEAVRT00

12F IEAVRTOO IEAVRT00

130 IEAVENQ1 IEAVENQ1

133 IEAVADOO IEAVADOOIEAVTSDX IEAVTSDX


13C IGC00060 IGC00060

13E IEAVEEDO IEAVEEDO

147 IGC0007A IGC0007A

149 IGC0007C IGC0007C

14A IGC0007D IGC0007D

14B IGC0007E IGC0007E

14F IEAVSETS IEAVSETS

153 IEEMB830 IEEMB830IEASMFSP IEASMFSP

157 IEAVXDOM IEAVXDOM

15C IECVEXCP IECVEXCP

15F IRARMINT IRARMINT

16B IEAVMODE IEAVMODE

16D IGC109 IGC109IGC116 IGC116IGC122 IGC122



ModuleDetecting

ModuleIssuing

171 IEAVFREE IEAVPSIIEAVFXLD IEAVPSIIEAVOUT IEAVPSIIEAVPSI IEAVPSIIEAVRELS IEAVPSI

172 IECVEXCP IECVEXCP

177 IEAVTEST IEAVTEST


17A IEAVEVTO IEAVEVTO

17B IEAVEPDQ IEAVEPDQ

17D IEAVEVTO IEAVEVTO

182 ICHRCK00 ICHRCK00

183 ICHRIN00 ICHRIN00

185 ICHRDF00 ICHRDF00

1FC IEAVESVR IEAVESVR

1FD IRBMFEVT IRBMFEVT

200 IECVEXPR IECVEXPR

201 IEAVSY50 IEAVSY50


206 IEAVLK03 IEAVLK03

20B IEAVRT01 IEAVRT01

20D IEAVTRTE IEAVTRTE

20E IEAVTB00 IEAVTB00

222 IEE3703D IEE3703D

228 IEAVTB00 IEAVTB00


22C IEAVECHO IEAVECHO

22E IEAVRT00 IEAVRT00

22F IEAVRT00 IEAVRT00


233 IEAVAD00 IEAVAD00

IEAVTSDT IEAVTSDTIEAVTSDX IEAVTSDX



23E

ModuleDetecting

IEAVEEDO

ModuleIssuing

IEAVEEDO

247 IGC0007A IGC0007A

253 IEEMB822 IEEMB822IEEMB827 IEEMB827IEEMB830 IEEMB830IEEMB834 IEEMB834IEEMB839 IEEMB839

25F IRARMERR IRARMINT

260 IEAVAX00 IEAVAX00

26D IRBMFDWP IRBMFDWPIRBMFIWK IRBMFIWK

271 IEAVPSI IEAVPSI

27B IGC123 IGC123




2F3 IEFIB605 IEFIB605

2FC IEAVEIOR IEAVEIOR

300 IECVEXCP IEAVEXCP


304 IEAVGPRR IEAVGPRR


306 IEAVLK00 IEAVLK00IEAVLK01 IEAVLK00


30E IEAVTB00 IEAVTB00

322 IEATLEXT IEATLEXT

328 IEAVTB00 IEAVTB00

338 IEAVENQ 1 IEAVENQ1


35F IEFSD263 IEFSD263





CD/MOD


ModuleDetecting

ModuleIssuing




3FC IEAVEE1R IEAVEE1R

IEAVEE2R IEAVEE2RIEAVEE3R IEAVEE3R









45F IRARMEVT IRARMEVT







4FC IEAVEPCR IEAVEPCR





522 IEATLEXT IEATLEXT




55F IRARMSRV IRARMSRV



ModuleDetecting

ModuleIssuing



5FC IEAVERER IEAVERER



622 IKJEFLJ IEFSD263IKJEFLG IKJEFLG

630 IEAVENQ 1 IEAVENQ 1

638 IEAVENQ 1 IEAVENQ 1



684 ICHRSV00 ICHRSV00


6FC IEAVEPC IEAVEPC

700 IGC109 IGC109IGC116 IGC116IGC122 IGC122IECVEXCP IECVEXCPIECVEXPR IECVEXPR

702 IEAVSV50 IEAVSY50
















ModuleDetecting

ModuleIssuing

822 IEFSD263 IEFSD263




87D IEAVEVTO IEAVEVT0




922 IEFIB621 N/A



A00 IECVEXCP IECVEXCPIECVEXPR IECVEXPR

A03 IEAVTSKT IEAVTSKT

A05 IEAVMG00 IEAVGM00

A06 IEAVLK00 IEAVLK00

A0A IEAVGM00 IEAVGM00

A23 IEAVMFRR IEAVMFRR

A78 IEAVGM00 IEAVGM00

B00 IECVEXPR IECVEXPR

B04 IEAVGM00 IEAVGM00


B0A IEAVGM00 IEAVGM00

B23 IEAVSTAA IEAVSTAA


C0D IEAVAMSI IEAVAMSIIEAVCSEG IEAVCSEGIEAVDLAS IEAVDLASIEAVDSEG IEAVDSEGIEAVEQR IEAVEQRIEAVESCO IEAVESCOIEAVFREE IEAVFREEIEAVFXLD IEAVFXLDIEAVGFA IEAVGFAIEAVINV IEAVINVIEAVIOCP IEAVIOCPIEAVOUT IEAVOUT

System Module ModuleCompletion Detecting IssuingCode

IEAVPFTE IEAVPFTEIEAVPIOI IEAVPIOIIEAVPIOP IEAVPIOPIEAVPIX IEAVPIXIEAVPRSB IEAVPRSBIEAVPSI IEAVPSIIEAVRCF IEAVRCFIEAVRELS IEAVRELSIEAVRFR IEAVRFRIEAVSOUT _ IEAVSOUTIEAVSQA IEAVSQAIEAVSWIN IEAVSWINIEAVTERM IEAVTERMILRSLSQA ILRSLSQAILRGOS ILRGOSILRTERMR ILRTERMRILRSRBC ILRSRBC

C22 IECVEXCP IECVEXCP

CFB IATABMN IATABMN

D05 IEAVGM00 IEAVGM00

D0A IEAVGM00 IEAVGM00

D0D IEAVTRTE IEAVTRTE

D23 IEAVVWTO IEAVVWTO

D78 IEAVGM00 IEAVGM00

DFB IATFCLT IATFCLTIATFPCC IATFPCCIATFPCW IATFPCWIATFPGD IATFPGDIATFPQC IATFPQCIATFPRA IATFPRAIATFPSB IATFPSBIATIIFO IATIIFOIATSICD IATSICD

E00 IECVEXCP IECVEXCP

E03 IEAVTSKT IEAVTSKT

E23 IEAVVRP2 IEAVVRP2


CD/MOD

Wait State Code to Module Table

WaitStateCode

Detecting IssuingModule Module

001 IEAIPL00 IEAIPL00






007 IEAVNP01 IEAVNIPM

00A IEAVNP03 IEAVNIPM

00B IEEVIPL IEEVIPL

00C IEAIPL00 IEAIPL00

00D IEEVIPL IEEVIPL

00E IEAIPL00 IEAIPL00

014 IEAVEPC IGFPTERM




01A IEEVDUMY IGFPTERM

01B IEAVTSLP IEESTPRS

01C IEAVESPR IGFPTERM

01D IEAVNIP0 IEAVNIP0

021 IEAVNPM2 IEAVNIPM

022 IECVDAVV IECVDAVV

024 IGFPTREC IGFPTREC

026 ICFBIF00 ICFBIF00ICFBDF00 ICFBDF00

027 ICFBIF00 ICFBIF00ICFBDF00 ICFBDF00

02D IEAVNPM3 IEAVNIPM

02E ILRMSG00 ILRMSG00

02F IECVPST IECVPST

WaitStateCode


030 IEAVNIP0 IEAVNIP0


032 IEAVNIPM IEAVNIPMIEAVNIP0 IEAVNIP0

033 IEAVNIPM IEAVNIPM




038 IEAVNIP0 IEAVNIP0ILRASRIM ILRIMMSGIEAVNIPM IEAVNIPM


03A IEAVNP05 IEAVNIPM

03B IEAVNP05 IEAVNIPMIEAVNP07 IEAVNIPMIEAVNIPX IEAVNIPM

03C ILRASRIM ILRIMMSGILRIODRV ILRIODRVILRMSG00 ILRMSG00

03D IEAVNP08 IEAVNIPM

03F IEAVNPM2 IEAVNIPMIEAVNP05 IEAVNIPM


041 IECVRSTI IECVRSTI


045 IEAVNPA6 IEAVNIPMIEAVNIP0 IEAVNIP0




04A IEAVNIP0 IEAVNIP0

04C IECVIRST IECVIRST

04D IECVIRST IECVIRST

WaitState Detecting IssuingCode Module Module

04E IECVIRST IECVIRSTIECVHREC IECVHRECIECVRRSV IECVRRSVIECVRSTI IECVRSTI

050 IEAVTACR IGFPTERM

051 IEAVTCR1 IGFPTERM

052 IEAVTCR1 IGFPTERM



05A IEAVNIP0 IEAVNIP0

05B IEAVNIP0 IEAVNIP0

05C IEAVNP11 IEAVNIPM

05D IEAVNP11 IEAVNIPM

05E IEAVNP11 IEAVNIPM

05F IEAVNP11 IEAVNIPM

060 ILRASRIM ILRIMMSG

061 ILRASRIM ILRIMMSG

063 IEAVNP03 IEAVNIPMIEAVNP11 IEAVNIPMIEAVNP19 IEAVNIPMILRASRIM ILRIMMSG



066 IECVHREC IECVHREC




06A IECVHREC IECVHREC

06B IECVCINT IECVCINT

06C IGFCCHED IGFCCHED

06D IECVRSTS IEESTPRS


WaitStateCode


06E IECVFCHN IEESTPRS

06F IECVDURP IECVDURP

0E6 IECVFCHN IEESTPRS



103 IEAVEES IEAVEES

201 IEAVN700 IGFPTCON

202 IEAVN701 IEESTPRS

A01 IGFPMCIH IGFPMCIH

A22 IEEVDCCR IEEVDCCR





CCC IEEMPS03 IEESTPRS


OS/VS Message Library: VS2 System Codes

GC38-1008-9 S370-40

Printed in U.S.A.

OS/VS Message READER'SLibrary: VS2 COMMENTSystem Codes FORMGC38-1008-9

This manual is part of a library that serves as a reference source for systems analysts, programmers,and operators of IBM systems. You may use this form to communicate your comments about thispublication, its organization, or subject matter, with the understanding that IBM may use or distributewhatever information you supply in any way it believes appropriate without incurring any obligation toyou.

Note: Copies of IBM publications are not stocked at the location to which this form is addressed. Pleasedirect any requests for copies of publications, or for assistance in using your IBM system, to your IBMrepresentative or to the IBM branch office serving your locality.

Possible topics for comment are:

Clarity Accuracy Completeness Organization Coding Retrieval Legibility

If you wish a reply, give your name, company, mailing address, and date:

OS/VS Message Library: VS2 System Codes

GC38-1008-9 S370-40

Reader's Comment Form

Documents

OS_VS Message Library_ VS2 System Codes