mopdf.com

How to send your comments to IBMWe appreciate your input on this publication. Feel free to comment on the clarity,accuracy, and completeness of the information or give us any other feedback thatyou might have.Use one of the following methods to send us your comments:1. Send an email to [email protected]. Visit the Contact z/OS web page at http://www.ibm.com/systems/z/os/zos/webqs.html3. Mail the comments to the following address:IBM CorporationAttention: MHVRCFS Reader CommentsDepartment H6MA, Building 7072455 South RoadPoughkeepsie, NY 12601-5400U.S.A.4. Fax the comments to us as follows:From the United States and Canada: 1 845 432-9405From all other countries: Your international access code 1 845 432-9405Include the following information:v Your name and addressv Your email addressv Your telephone or fax numberv The publication title and order number:z/OS V1R12.0 MVS System CodesSA22-7626-22v The topic and page number related to your commentv The text of your comment.When you send comments to IBM, you grant IBM a nonexclusive right to use ordistribute your comments in any way it believes appropriate without incurring anyobligation to you.IBM or any other organizations will only use the personal information that yousupply to contact you about the issues that you submit.If you have a technical problemDo not use the feedback methods listed above. Instead, do one of the following:v Contact your IBM service representativev Call IBM technical supportv Visit the IBM zSeries support web page at http://www.ibm.com/systems/z/support/ Copyright IBM Corp. 1988, 2010ix

xz/OS V1R12.0 MVS System Codes

Summary of changesSummary of changesfor SA22-7626-22z/OS Version 1 Release 12The document contains information previously presented in z/OS MVS SystemCodes, SA22-7626-21, which supports z/OS Version 1 Release 11.New informationThe following system completion code has been added:v 007v 50EChanged informationThe following system completion codes have changed:v 00Cv 01Dvvvvv02602805C07708Fv 0B7v 0F7v 13Cv 18Fv 1FBv 300vvvvv33033843043850Dv 6C5v 730v 738v EC6The following wait state codes have changed:v 088v 0A2v 0B1v D0D Copyright IBM Corp. 1988, 2010xi

The "Readers' Comments - We'd Like to Hear from You" section at the back of thispublication has been replaced with a new section “How to send your comments toIBM” on page ix. The hardcopy mail-in form has been replaced with a page thatprovides information appropriate for submitting readers comments to IBM.You may notice changes in the style and structure of some content in thisdocument—for example, headings that use uppercase for the first letter of initialwords only, and procedures that have a different look and format. The changes areongoing improvements to the consistency and retrievability of information in ourdocuments.This document contains terminology, maintenance, and editorial changes. Technicalchanges or additions to the text and illustrations are indicated by a vertical line tothe left of the change.Summary of changesfor SA22-7626-21z/OS Version 1 Release 11as updated April 2010The document contains information previously presented in z/OS MVS SystemCodes, SA22-7626-20, which supports z/OS Version 1 Release 11.Changed informationThe following system completion code has changed:v 042You may notice changes in the style and structure of some content in thisdocument—for example, headings that use uppercase for the first letter of initialwords only, and procedures that have a different look and format. The changes areongoing improvements to the consistency and retrievability of information in ourdocuments.This document contains terminology, maintenance, and editorial changes. Technicalchanges or additions to the text and illustrations are indicated by a vertical line tothe left of the change.Summary of changesfor SA22-7626-20z/OS Version 1 Release 11The document contains information previously presented in z/OS MVS SystemCodes, SA22-7626-19, which supports z/OS Version 1 Release 10.New informationThe following system completion code has been added:v 654Changed informationThe following system completion codes have changed:v 00Cv 02Axiiz/OS V1R12.0 MVS System Codes

vvvvv042050077106150vvvvvv15F1FB7309C6DC2EC6The following wait state codes have changed:vvvvv00E01C03105E082v 0A2v 0A7v 0B1v 24This document contains terminology, maintenance, and editorial changes, includingchanges to improve consistency and retrievability.Summary of changesfor SA22-7626-19z/OS Version 1 Release 10as updated in April 2009The document contains information previously presented in z/OS MVS SystemCodes, SA22-7626-18, which supports z/OS Version 1 Release 10.New informationThe following system completion codes have been added:v 150v 7D0Changed informationThe following system completion codes have changed:v 042v 058v 05Cv 071v 07Dv 0C4Summary of changesxiii

vvvvv0D60D70F718F1FBvvvv253306DC2EC6This document contains terminology, maintenance, and editorial changes, includingchanges to improve consistency and retrievability.Summary of changesfor SA22-7626-18z/OS Version 1 Release 10as updated October 2008The document contains information previously presented in z/OS MVS SystemCodes, SA22-7626-17, which supports z/OS Version 1 Release 10.New informationThe following system completion codes have been added:v 7B0This document contains terminology, maintenance, and editorial changes, includingchanges to improve consistency and retrievability.Summary of changesfor SA22-7626-17z/OS Version 1 Release 10The document contains information previously presented in z/OS MVS SystemCodes, SA22-7626-16, which supports z/OS Version 1 Release 9.New informationThe following system completion codes have been added:v 2E0v 7B0v D24v DC4The following wait state codes have been added:v A2Cv 0B5Changed informationThe following system completion codes have changed:v 01Dxivz/OS V1R12.0 MVS System Codes

vvvvv02A05C07709A0F7vvvvvvv1571FB23343855F5FC653v C0Dv DC2v E23The following wait state codes have changed:v 007v 05Ev 082v 087vvvv08A0A20A30B1vvvv202204A22A70v D0DThis document contains terminology, maintenance, and editorial changes, includingchanges to improve consistency and retrievability.Summary of changesxv

xviz/OS V1R12.0 MVS System Codes

Chapter 1. IntroductionThis chapter topic introduces system and user completion codes and wait statecodes.Completion CodesThe system or an application program issues a completion code when abnormallyending processing by a task, address space, or system module. The completioncode indicates the reason for the abnormal end. A completion code can be specifiedby the following:v ABEND macrov CALLRTM macrov SETRP macroAbend of a Task or Address SpaceFor a System-Detected ProblemThe system abnormally ends a task or address space when the system determinesthat the task or address space cannot continue processing and produce validresults.For example, a task may incorrectly specify a request for a system service.Because the system cannot perform the service with incorrect input, the systemabnormally ends the task requesting the service. This task is also referred to as acaller.For a Hardware-Detected ProblemThe system also abnormally ends a task with a completion code when the systemreceives control after a hardware-generated interruption that indicates an error inthe task.For example, an instruction in an application running in storage key 7 branches tolow central storage, which is always in storage key 0. The difference in storage keycauses a protection exception. The system recovers from this hardware problem byending the application's task with an abend X'0C1'. If the application has a recoveryroutine, the system gives control to the routine; the routine can clean up resourcesbeing used by the application and can request a dump.For an Application-Detected ProblemAn application program abnormally ends itself when it determines that it cannotcontinue processing and produce valid results.For example, an application may be calculating a total by successive additions.After each addition, the application checks the new total against a limit. If the totalexceeds the limit, the application issues an ABEND macro to end abnormally and,perhaps, to ask for an ABEND dump. The ABEND macro specifies a usercompletion code.Abend of a System ServiceIf a system service represented by a service request block (SRB) experiences aproblem, the system gives control to the recovery routine for the service; the routine Copyright IBM Corp. 1988, 20101

can issue a SETRP macro to place a system completion code in the systemdiagnostic work area (SDWA). The system service stops processing. If the servicewas processing a request from a task, the system abnormally ends the task withthe same system completion code.Note that another task can request the system service to do processing.FormatThe format of completion codes is:v System completion code (or abend code): 3 hexadecimal digitsv User completion code: 4 decimal digitsNote: Only system completion codes appear in this book ; user completion codesdo not. User completion codes are in book for the IBM-provided component,subsystem, or product that issues the user completion codes. IPCS usercompletion codes are documented in Chapter 7, “IPCS User CompletionCodes,” on page 441. Codes issued by installation-provided programs do notappear in IBM book .LocationThe codes can be obtained from the following:v Messages accompanying the abendv The header in any ABEND dump accompanying the abendv Search arguments and, sometimes, the title in any SVC dump accompanying theabendv Search arguments in any logrec data set error record written for the abendv The system diagnostic work area (SDWA)v Use of the EXTRACT macro with keyword CMC to determine the completioncode for the ended task.Abnormal End of SubtasksWhen the highest-level task in a job step ends abnormally, the job step endsabnormally.When a subtask ends abnormally, only the subtask itself and its subtasks end. Toget the abend code for an abnormal end of a subtask:v Examine the event control block (ECB) specified by the task that attached thesubtaskv Issue the EXTRACT macro with the CMC keywordA low-level subtask that ends abnormally has two ways to cause the entire job stepto end abnormally:v Each task in the job step's task chain, including the job step task, must end itselfabnormally when it detects an abend code from one of its subtasks. To end thejob step with the abend code for the original error, each task must use the abendcode from its subtask as its own abend code.v A subtask can abnormally end the entire job step if it specifies a STEP parameteron the ABEND macro.2z/OS V1R12.0 MVS System Codes

Wait State Codes in z/Architecture ModeThe wait state code appears in the program status word (PSW) when the operatingsystem enters a wait state. A valid PSW for a coded wait state in z/Architecture mode has one of the following general formats:v 00020000 x0000000 00000000 0rrrrwwwv 00020000 x0000000 00000000 0rr00wwwv 00020000 x0000000 00000000 00rrrwwwv 00020000 x0000000 00000000 0rrr0www2Bits 12-15 (the CMWP bits, with the 'W' bit being on).xBits 32-35. Not part of the wait state information.rrrr, rr00, 0rrr, rrr0Bits 100-115, where r is the reason code for 8/12/16 bits and 0 zero.A supplementary code accompanying the wait state code.The wait state determines the size and position of the supplement code.Usually the supplementary code is a reason code. Some wait state codes donot provide a supplementary code in the PSW. See the description of theindividual wait state code for more information.wwwBits 116-127.The wait state code. The IBM-supplied wait state codes appear in this book .Installation-supplied programs can use the wait state codes X'FF0' throughX'FFE'; see installation-supplied information for these codes.No Work WaitIf the system hangs because it has no work waiting to be dispatched, eitherbecause the work is waiting for a resource or because no work remained on thesystem queues, the PSW contains:X'07060000 00000000 00000000 00000000'A no work wait may not reflect an error. See z/OS Problem Management fordiagnosis of a hang or wait.Wait State Codes from a Stand-Alone Dump ProgramSee Chapter 6, “Stand-Alone Dump Wait State Codes,” on page 433 for informationabout reading stand-alone dump wait state codes.IPCS User Completion CodesIPCS issues a 4 digit decimal user code when it encounters errors in eitherIBM-provided IPCS code or in installation exit routines. See Chapter 7, “IPCS UserCompletion Codes,” on page 441 for more information.Chapter 1. Introduction3

4z/OS V1R12.0 MVS System Codes

Chapter 2. System Completion Codes See VTAM abend codes in z/OS Communications Server: IP and SNA Codes forthe following codes:v 0A7v 0A8v 0A9v 0AAv 0ABv 0AC v 0AD001Explanation: An I/O error condition was encounteredduring BDAM, BISAM, BPAM, BSAM, QISAM, or QSAMprocessing.The completion code can be issued if CLOSEprocessing called end-of-volume (EOV), and EOVprocessing detected an out-of-space condition. Refer tothe explanation of message IEC020I in z/OS MVSSystem Messages, Vol 7 (IEB-IEE) for information aboutthe task that was ended.Operator response: Start a generalized trace facility(GTF) trace, and re-create the problem. Reply tomessage AHL100A with:TRACE SYS,USR,SLIPOn the DD statement for the data set in error, specify:DCB DIAGNS TRACEApplication Programmer Response: Respond asindicated for message IEC020I.Application Programmer Response: See messageIEC036I for the appropriate responses for each returncode except 2C. For return code 2C, change theCYLOFL operand of the DCB macro instruction toreflect the correct number of tracks, or correct the DCBBLKSIZE.System programmer response: If the error recursand the program is not in error, look at the messages inthe job log for more information. Search problemreporting data bases for a fix for the problem. If no fixexists, contact the IBM Support Center. Provide the JCLand the program listing for the job.System programmer response: If the error recursand the program is not in error, look at the messages inthe job log for more information. Search problemreporting data bases for a fix for the problem. If no fixexists, contact the IBM Support Center. Provide the JCLand the program listing for the job.Source: DFSMSdfpSource: DFSMSdfp002003Explanation: For all return codes except 2C, the erroroccurred while the control program was processing asequential data set with BSAM or QSAM, or creating adirect organization data set. This system completioncode is accompanied by message IEC036I. Refer to theexplanation of message IEC036I for completeinformation about the task that was ended and for anexplanation of the return code found in register 15.Explanation: The error occurred during end-of-blockprocessing using either BSAM or QSAM. The erroroccurred because the I/O macro instructions for a3525-associated data set were not run in the propersequence.For return code 2C, the error occurred while the controlprogram was opening an ISAM data set for QISAM loadmode. Too many tracks were specified for cylinderoverflow, or DCB BLKSIZE was not a multiple of DCBLRECL, or DCB BLKSIZE was greater than the tracksize.CodeExplanation01A READ sequence error02A PUNCH sequence error03A PRINT sequence errorSystem action: For all return codes except 2C,pertinent control blocks are written to the GTF tracedata set, the user's DCB ABEND exit is taken if one isprovided, and message IEC036I is issued. Copyright IBM Corp. 1988, 2010The hexadecimal reason code in register 15 indicatesthe nature of the error:System action: The system ends the task.Application Programmer Response: Specify the I/Omacro instructions in the proper sequence, and rerunthe job.5

004 00ASystem programmer response: If the error recursand the program is not in error, look at the messages inthe job log for more information. Search problemreporting data bases for a fix for the problem. If no fixexists, contact the IBM Support Center. Provide theprogram listing for the job.and the program is not in error, look at the messages inthe job log for more information. Search problemreporting data bases for a fix for the problem. If no fixexists, contact the IBM Support Center. Provide theprogram listing for the job.Source: DFSMSdfpSource: DFSMSdfp 007004Explanation: The error occurred during OPENprocessing using either BSAM or QSAM because aconflicting or incorrect DCB parameter (FUNC or relatedparameter) is specified. The hexadecimal reason codein register 15 indicates the nature of the error: Explanation: An abend occurred in Runtime Diagnostics (HZR component) processing. CodeExplanation xxxxyyyyInternal errors. CodeExplanation System action: An SVC dump might be produced.01Incorrect DCB FUNC parameter specified.02Incorrect combination of DCB FUNC parameterand CNTRL macro specified. Operator response: Contact the System Programmer for xxxxyyyy.03Conflicting access methods specified.04Incorrect DCB specified for 3505 or 3525.05Incorrect format card or an incorrect devicespecified with Optical Mark Read (OMR).06Data protection image not found in theSYS1.IMAGELIB data set, volume containingSYS1.IMAGELIB not mounted, orSYS1.IMAGELIB data set not cataloged.System action: In all cases, the system ends the task.Application Programmer Response: In all cases,correct the incorrect fields of the DCB macro instructionand rerun the job.System programmer response: If the error recursand the program is not in error, look at the messages inthe job log for more information. Search problemreporting data bases for a fix for the problem. If no fixexists, contact the IBM Support Center. Provide theprogram listing for the job.Source: DFSMSdfp Source: Runtime Diagnostics (HZR is the component name)008Explanation: The error occurred during processing ofa SYNAD routine. The routine was given controlfollowing processing of a BSAM CHECK macroinstruction.The SYNAD routine returned control to the controlprogram for the CHECK macro instruction.Application Programmer Response: Correct theSYNAD routine so that the control program save area isnot destroyed. Then run the job step again.System programmer response: If the error recursand the program is not in error, look at the messages inthe job log for more information. Search problemreporting data bases for a fix for the problem. If no fixexists, contact the IBM Support Center. Provide the JCLand the program listing for the job.Source: DFSMSdfp005Explanation: The error occurred because of anincorrect DECB during READ processing using BSAM.This system completion code is accompanied bymessage IEC041I. Refer to the explanation of messageIEC041I for complete information about the task thatwas ended and for an explanation of the return code.System action: The task is ended.Application P

How System Codes are Explained in this Book The following describes the different parts of system code explanations in this book: Explanation The meaning of the abend, including why the system issued the abend. System Action v What the system did as a result of the