CICS Messages And Codes

PrefaceWhat this manual is about: This manual contains messages unique to CICS Transaction Server for OS/390 Release 3and is intended for use as a quick reference. It is closely linked with the CICS Problem Determination Guide which should alsobe consulted if a message indicates that there is a CICS problem.Who this manual is for: This manual is for anybody who needs to understand and respond to CICS messages, includingsystem operators, system programmers, and certain terminal users.What you need to know to understand this manual: You can refer to this manual for the meaning of a messagewithout understanding the manual as a whole. Your understanding of CICS Transaction Server for OS/390 Release 3,however, will be enhanced by a knowledge of the types of message CICS produces, the different places it sends messages,and the different audiences it intends to reach.How to use this manual: When you are using CICS as a system operator or terminal user, or scanning a queuecontaining CICS messages, have this manual available as a reference.Online Messages and Codes: CICS Transaction Server for OS/390 Release 3 messages and abend code descriptionsdocumented in this manual (with the exception of AXM messages, a small number of numeric abends and Transaction DumpCodes) are available online using the CICS transaction CMAC. For guidance on using CMAC, see the CICS SuppliedTransactions manual.Notes on terminologyThe following terminology is used:CICS used without any qualification refers to the CICS element of IBM CICS Transaction Server for OS/390MVS refers to the operating system, which can either be an element of OS/390, or MVS/Enterprise System ArchitectureSystem Product (MVS/ESA SP).DL/I refers to IMS/ESA DL/I (Data Language/I)VTAM refers to ACF/VTAMTCAM refers to the DCB interface of ACF/TCAM.APPC is used throughout this manual to refer to LUTYPE6.2 (LU6.2).“Module” is used in this manual to refer to a program unit that is discrete and identifiable with respect to the input or outputfrom an assembler or compiler. For the purposes of this manual, a module is the minimal serviceable object.Determining if a publication is currentIBM regularly updates its publications with new and changed information. When first published, both hardcopy andBookManager softcopy versions of a publication are usually in step. However, due to the time required to print and distributehardcopy books, the BookManager version is more likely to have had last-minute changes made to it before publication.Subsequent updates will probably be available in softcopy before they are available in hardcopy. This means that at any timefrom the availability of a release, softcopy versions should be regarded as the most up-to-date.For CICS Transaction Server books, these softcopy updates appear regularly on the Transaction Processing and DataCollection Kit CD-ROM, SK2T-0730-xx. Each reissue of the collection kit is indicated by an updated order number suffix (the-xx part). For example, collection kit SK2T-0730-06 is more up-to-date than SK2T-0730-05. The collection kit is also clearlydated on the cover.Updates to the softcopy are clearly marked by revision codes (usually a “#” character) to the left of the changes. Copyright IBM Corp. 1977, 1999ix

Book structureThis book contains:Chapter 1, “DFH messages” on page 1Describes CICS Transaction Server for OS/390 Release 3 messages in alphanumeric order. These messages areidentified by the prefix “DFH”.Chapter 2, “AXM server environment messages” on page 781Describes authorized cross-memory server environment messages in alphanumeric order. These messages are identifiedby the prefix “AXM”.Chapter 3, “Transaction abend codes” on page 791Describes CICS Transaction Server for OS/390 Release 3 transaction abend codes in alphanumeric order.Chapter 4, “Transaction Dump Codes” on page 941Describes CICS Transaction Server for OS/390 Release 3 transaction dump codes in alphanumeric order.CICS Transaction Server for OS/390: Planning for InstallationOS/390 Release GuideOS/390 Migration GuideOS/390 Installation GuideOS/390 Program DirectoryOS/390 Licensed Program C33-1706GC33-1707CICS books for CICS Transaction Server for OS/390GeneralCICS Master IndexCICS User's HandbookCICS Glossary (softcopy only)AdministrationCICS System Definition GuideCICS Customization GuideCICS Resource Definition GuideCICS Operations and Utilities GuideCICS Supplied TransactionsProgrammingCICS Application Programming GuideCICS Application Programming ReferenceCICS System Programming ReferenceCICS Front End Programming Interface User's GuideCICS C OO Class LibrariesCICS Distributed Transaction Programming GuideCICS Business Transaction ServicesDiagnosisCICS Problem Determination GuideCICS Messages and CodesCICS Diagnosis ReferenceCICS Data AreasCICS Trace EntriesCICS Supplementary Data AreasCommunicationCICS Intercommunication GuideCICS Family: Interproduct CommunicationCICS Family: Communicating from CICS on System/390CICS External Interfaces GuideCICS Internet GuideSpecial topicsCICS Recovery and Restart GuideCICS Performance GuideCICS IMS Database Control GuidexCICS Messages and 33-1699SC33-1700

CICSCICSCICSCICSRACF Security GuideShared Data Tables GuideTransaction Affinities Utility GuideDB2 GuideSC33-1701SC33-1702SC33-1777SC33-1939CICSPlex SM books for CICS Transaction Server for OS/390GeneralCICSPlex SM Master IndexCICSPlex SM Concepts and PlanningCICSPlex SM User Interface GuideCICSPlex SM View Commands Reference SummaryAdministration and ManagementCICSPlex SM AdministrationCICSPlex SM Operations Views ReferenceCICSPlex SM Monitor Views ReferenceCICSPlex SM Managing WorkloadsCICSPlex SM Managing Resource UsageCICSPlex SM Managing Business ApplicationsProgrammingCICSPlex SM Application Programming GuideCICSPlex SM Application Programming ReferenceDiagnosisCICSPlex SM Resource Tables ReferenceCICSPlex SM Messages and CodesCICSPlex SM Problem her CICS booksCICS Application Programming Primer (VS COBOL II)CICS Application Migration Aid GuideCICS Family: API StructureCICS Family: Client/Server ProgrammingCICS Family: General InformationCICS 4.1 Sample Applications GuideCICS/ESA 3.3 XRF SC33-1173SC33-0661Books in related librariesIMS/VSIMS/VS Messages and Codes Reference Manual, SC26-4174IMS/VS Failure Analysis Structure Tables (FAST) for Dump Analysis, LY26-3992IMS/VS Diagnosis Guide and Reference, LY27-9526IMS/ESAIMS/ESA Diagnosis Guide and Reference, LY27-9539IMS/ESA Failure Analysis Structure Tables, LY27-9512IMS/ESA Messages and Codes, SC26-8028IMS/ESA Application Programming: Database Manager, SC26-8015IBM DATABASE 2IBM DATABASE2 Messages and Codes, SC26-4113MVSOS/390 MVS System Codes, GC28-1780OS/390 MVS System Messages, Volume 1 (ABA-ASA), GC28-1784OS/390 MVS System Messages, Volume 2 (ASB-EWX), GC28-1785OS/390 MVS System Messages, Volume 3 (GDE-IEB), GC28-1786Prefacexi

OS/390 MVS System Messages, Volume 4 (IEC-IFD), GC28-1787OS/390 MVS System Messages, Volume 5 (IGD-IZP), GC28-1788OS/390 MVS System Management Facilities (SMF), GC28-1783OS/390 MVS Initialization and Tuning Guide, SC28-1751OS/390 MVS JCL Reference, GC28-1757OS/390 MVS Sysplex Services Reference, GC28-1772OS/390 MVS Programming: Authorized Assembler Services Guide, GC28-1763OS/390 MVS Programming: Authorized Assembler Services Reference, GC28-1764DFPMVS/DFP Access Method Services for VSAM Catalogs, SC26-4570MVS/DFP Macro Instructions for VSAM Data Sets, SC26-4569OS/VSOS/VS VSAM Programmer’s Guide, GC26-3838OS/VS2 System Programming Library: Supervisor, GC28-0628OS/VS2 System Programming Library: Job Management, GC28-0627Access methodsSNA Formats, GA27-3136ACF/VTAM Messages and Codes, SC27-0470VTAM Programming, SC31-6436Programming languagesOS PL/I Optimizing Compiler: Programmer’s Guide, SC33-0006OS PL/I Version 2 Programming Guide SC26-4307IBM C/370 User’s Guide SC09-1264IBM OS/VS COBOL Compiler and Library Programmer’s Guide, SC28-6483VS COBOL II Application Programming: Debugging Guide, SC26-4049VS COBOL II Installation and Customization, SC26-4048Language Environment/370Programming Guide, SC26-4818Diagnosis Guide, SC26-4815Summary of changesThis book is based on the CICS Transaction Server for OS/390 Release 2 edition, GC33-1694-01. It has been updated toincorporate changes made for CICS Transaction Server for OS/390 Release 3. Changes since the last edition are indicated byvertical bars to the left of the changes.xiiCICS Messages and Codes

DFH messagesChapter 1. DFH messagesWhile CICS is running, it can produce several types of messages. Console messages advise the system operator of execution progress, or request a decision. Certain CICS-supplied support programs communicate directly with terminal operators. CICS management modules and support programs log significant events and error occurrences to transient datadestinations; for example, to the control system master terminal (CSMT), or to the CICS database control log (CDBC) forthe CICS-DBCTL interface. The CICS message switching program (DFHMSP) generates message switching responses (described in the CICSSupplied Transactions manual). CICS directs informational macro notes (mnotes) to programmers. These are not documented. Messages produced by CICS utility programs such as DFH MOLS and DFHMNDUP. These messages areself-explanatory and are not documented.With the exception of the AXM messages, a small number of numeric abends and the Transaction Dump Codes, the messagesdescribed in this book can also be viewed online using the CICS transaction CMAC. For guidance on using CMAC, see theCICS Supplied Transactions manual.CICS DFH message IdentifiersMessage identifiers are of two types.DFHnnnn identifiersThese consist of the prefix “DFH” followed by a four digit message number. “DFH” is the IBM assigned identifier for CICSmodules. The first two digits are the CICS module reference code as HCSDUP7xCommand-level translators52 DFHCSDUPThe last two digits are assigned by CICS to identify the message or group of messages within an assembled program.DFHccnnnn identifiersThese consist of the prefix “DFH” followed by a two-letter component identifier (cc), and a four-digit message number (nnnn).The component identifier shows the domain or the component which issues the message. Here is a list of componentidentifiers with associated domains and components:AC The abnormal condition program componentAIThe auto-install terminal model manager (AITM)CR The ISC remote scheduler component CZ The CICS class libraries domainAM The RDO allocation managerDB The CICS database control componentAP The application domainDD The directory managerAU The transaction affinities utility BA The CICS business transaction services (BTS) domain DH Document handler componentDM The domain manager domainBR Bridging to 3270 transactionsDS The dispatcher domainCA RDO command utility routineDU The dump domainCC The CICS catalog domain (local and global)DX The CICS database control componentCE The sign on program component CF CICS coupling facility data tables serverCP The CPI Communications component Copyright IBM Corp. 1977, 1999 EM The Event Manager domainER The user backout programEX The external CICS interface1

DFH messagesFC The file control component SH The Sheduler domainFE The FE terminal test program componentSIICThe interval control programSK The sub task control program componentINThe indoubt testing toolSM The storage manager domainIRThe interregion componentSN The signon componentJC The online journal control componentThe system initialization component SO The CICS Sockets domainKC The transaction/profile managerSR The system recovery componentKE The kernel domainST The statistics domainLD The loader domainSZ The front end programming interface (FEPI)LG The logger domainTC The terminal control program componentLM The lock manager domainTD The transient data componentMC The BMS message control program componentTFThe terminal facility managerME The message domainTIThe timer domainMN The monitor domainTM The system termination program componentMU The message editing utility programTO The terminal object resolution program componentMV The MVS RESMGR exit stubTP The BMS terminal page retrieval program component NC The Named counter sequence number serverTR The trace domainNQ The enqueue manager domainTS The temporary storage domainPA The parameter manager domainUP The measured usage license charging support macroPC The program control program componentUS The user domainPD The print dump exit routine DFHPDXWB The CICS Web InterfacePG The program manager domainXA The XRF alternate componentPR The partner resource managerXC The XRF CICS availability managerPS The system spooler interface control module componentXG The XRF general componentRD The RDO allocation managerXM The transaction managerRM The recovery managerXO The XRF CICS availability managerRP CICS ONC RPCXQ The shared temporary storage queue pool serverRS The communications resynchronization programXS The CICS security componentRT The ISC transaction routing componentZC The terminal control working set componentRU The recovery utility programZE The TCP error message writer component RX The RRS-coordinated EXCI domainZN The syncpoint componentThus the CICS message DFHAP0002 is issued from the application domain, identified by the two-character identifier AP.Action codesCertain messages (for example, DFHDB8208D) include an action code after the message identifier. Action codes giveguidance to the operator of the type of action needed when the message appears on the system console. The following actioncodes are used:AImmediate action (for example, mount a tape)DImmediate decision (reply to a request, for example, enter “GO” or “CANCEL”)EEventual – action is required, but does not have to be taken immediatelyINo action required (If issued via the message domain, these messages can be suppressed by specifying MSGLVL 0 as asystem initialization override.)2CICS Messages and Codes

DFH messagesSeverity codesCertain messages, especially those associated with messages to terminal operators and messages which come from CICSutilities, have a severity code. (DFHST0210 I, is an example.) A severity code indicates to the operator whether a message isassociated with an error, and if so, how serious it is. The following severity codes are used:EError. Something has gone wrong and action is required of the user before CICS processing can continue.IInformation only. No action is required.WAlert. Something may have gone wrong, a program loop for example, but CICS processing continues.SSevere error. Something serious has gone wrong and immediate action is required. CICS processing is suspended untilaction has been taken.Format of informationInformation about each message is presented in the following format: Message identifier – in the form DFHnnnn or DFHccnnnn Message text – the words and inserts which make up the message as displayed in CICS Explanation – the events leading to or following the production of the message System action – the action that has been or will be taken by CICS User response – the action recommended for the user (the console or terminal operator or system programmer) Destination – the device or log to which the message is sent. This is one of the following:– Console – refers to a terminal type attached t

Online Messages and Codes: CICS Transaction Server for OS/390 Release 3 messages and abend code descriptions documented in this manual (with the exception of AXM messages, a small number of numeric abends and Transaction Dump