CICS TS for z/OS: CICS Codes - IBM

CICS Transaction Server for z/OS5.6

CICS Codes

IBM

Note

Before using this information and the product it supports, read the information in Product Legal Notices.

This edition applies to the IBM® CICS® Transaction Server for z/OS®, Version 5 Release 6 (product number 5655-Y305655-BTA ) and to all subsequent releases and modifications until otherwise indicated in new editions.© Copyright International Business Machines Corporation 1974, 2021.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

https://www.ibm.com/docs/cics-ts/latest?topic=available-notices

Contents

About this PDF.......................................................................................................v

Chapter 1. Transaction abend codes.......................................................................1AAxx abend codes........................................................................................................................................2ABxx abend codes..................................................................................................................................... 19ACxx abend codes......................................................................................................................................41ADxx abend codes..................................................................................................................................... 78AExx abend codes....................................................................................................................................100AFxx abend codes....................................................................................................................................132AGxx abend code..................................................................................................................................... 142AIxx abend codes.................................................................................................................................... 143AJxx abend codes....................................................................................................................................167AKxx abend codes................................................................................................................................... 171ALxx abend codes....................................................................................................................................178AMxx abend codes...................................................................................................................................183ANxx abend codes................................................................................................................................... 188AOxx abend codes................................................................................................................................... 190APxx abend codes................................................................................................................................... 191ARxx abend codes................................................................................................................................... 211ASxx abend codes....................................................................................................................................221ATxx abend codes.................................................................................................................................... 238AUxx abend codes................................................................................................................................... 257AWxx abend codes.................................................................................................................................. 257AXxx abend codes................................................................................................................................... 267AZxx abend codes....................................................................................................................................282

Chapter 2. System abend and dump codes......................................................... 311CICS system dump codes........................................................................................................................311DHxx (IMS) abend codes......................................................................................................................... 31201xx (translator) abend codes................................................................................................................ 31202xx (DFHPD730) abend codes..............................................................................................................31303xx (DFHCSDUP) abend codes..............................................................................................................31304xx (external CICS interface) abend codes.......................................................................................... 3174xxx LE/370 abend codes....................................................................................................................... 322CICSPlex SM Abend and dump codes.....................................................................................................323

CICS abend and dump codes.............................................................................................................323Uxxxx abend codes............................................................................................................................ 324System dump codes...........................................................................................................................325

Notices..............................................................................................................327

iii

iv

About this PDF

This PDF is a reference of CICS transaction abend codes, and system abend codes. Before CICS TS V5.4,this information was in the PDF called CICS Messages and Codes, Volume 1.

For details of the terms and notation used in this book, see Conventions and terminology used in CICSdocumentation in IBM Documentation.

Date of this PDFThis PDF was created on 2022-09-10 (Year-Month-Date).

© Copyright IBM Corp. 1974, 2021 v

https://www.ibm.com/docs/cics-ts/latest?topic=available-conventions-used-in-documentation

https://www.ibm.com/docs/cics-ts/latest?topic=available-conventions-used-in-documentation

vi CICS TS for z/OS: CICS Codes

Chapter 1. Transaction abend codesWhen abnormal conditions occur, CICS can send a message to the CSMT transient data destination thatcontains the transaction ID, the program name, and the abend code.

Here is an example:DFHAC2236: date time applid Transaction tranid abend primary abcode in program program name term termid backout successful { batchid = }batchid. message

Alternatively, the application can intercept abends by including an active EXEC CICS HANDLE ABENDcommand. The actual abend code can be determined by issuing the EXEC CICS ASSIGN command withthe ABCODE option.

The transaction identification code tranid usually consists of the 4 characters defined to CICS. However,when a transaction is initiated by using a light pen, an operator identification (OPID) card reader, or 3270PA or PF keys (specified in the TASKREQ= operand), CICS creates an internal transaction identification inthe form of a 1-byte 3270 attention identification (AID) code followed by 3 bytes of X'FF'.

The code that may actually appear in the message in place of the internally-created transactionidentification will be *xx*, where xx is the character translation of the 3270 AID code. To preventambiguity, the user should avoid using these codes as transaction identifiers.

The keys, the light pen (LPA), and OPID, and their corresponding printed AID codes are given in thefollowing list:

PF1 *F1* PF13 *C1* LPA *7E*

PF2 *F2* PF14 *C2* OPID *E6*

PF3 *F3* PF15 *C3®* PA1 *6C*

PF4 *F4* PF16 *C4* PA2 *6E*

PF5 *F5* PF17 *C5* PA3 *6B*

PF6 *F6* PF18 *C6*

PF7 *F7* PF19 *C7*

PF8 *F8* PF20 *C8*

PF9 *F9* PF21 *C9*

PF10 *7A* PF22 *4A*

PF11 *7B* PF23 *4B*

PF12 *7C* PF24 *4C*

An abend code indicates the cause of an error that may have been originated by CICS or by a userprogram. For most of the abend codes described, a CICS transaction dump is provided at abnormaltermination.

All CICS transaction abend codes abcode are 4-character alphanumeric codes of the form Axxx.

Format of informationFor each transaction abend code, the following information is given:

• An explanation of events leading to or following the message.• The action that has been or will be taken by CICS (system action).• The action recommended for the user (console or terminal operator).

© Copyright IBM Corp. 1974, 2021 1

• The module or modules that can determine that the message should be sent (not necessarily themodule or modules that can issue the macro to write the message).

AAxx abend codesAACA

ExplanationAn invalid error code has been passed to the DFHTFPor DFHACP programs.

System actionCICS terminates the task abnormally with a dump.

User responseNotify the system programmer.

Module:DFHTFP,DFHACP

AAL1

ExplanationDFHALP was processing a request that deadlocked.The most likely reason for the abend is that anALLOCATE QUEUE request has been suspendedbecause there are no contention-winning linksavailable.

AAL1 is issued for non time-out related deadlocks, forinstance the task may have been cancelled.

AAL8 is issued for stall purges and deadlock time-outs.

System actionCICS terminates the task abnormally. A dump is taken.

User responseEnsure that there are enough contention-winningsessions available to satisfy the ALLOCATE QUEUErequest.

If you are running with modegroups, ensure that thereare contention-winning sessions available to satisfythe ALLOCATE request in that modegroup.

Module:DFHALP

AAL2

ExplanationEither an incorrect response (other than PURGED) wasreturned from the suspend of the allocated task, or anincorrect response was returned from the resume.

System actionThe transaction is abnormally terminated with a dump.

User responseCheck the return code from the resume or the suspendto determine the cause of the error.

Module:DFHALP

AAL3

ExplanationThe task has been purged before a GETMAIN requestto the storage manager (SM) domain was able tocomplete successfully. The task that first detected thepurged condition provides an exception trace.

System actionThe task is abnormally terminated with a CICStransaction dump.

User responseInvestigate the reason why the task was purged. It waspurged either by the main terminal operator or as aresult of a deadlock timeout.

Module:DFHALP

AAL4

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe storage manager (SM) domain. The domain thatdetected the original error provides an exception trace,a console message, and possibly a system dump(depending on the options specified in the dumptable).

2 CICS TS for z/OS: CICS Codes


User responseSee the related message produced by the domain thatdetected the original error.

Module:DFHALP

AAL6

ExplanationAn error (INVALID, DISASTER or EXCEPTIONresponse) has occurred on a call toSIGNOFF_TERMINAL_USER by DFHALP during sign-offfor a surrogate terminal session running CRTE. Thedomain that detected the original error provides anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).



Module:DFHALP

AAL7

ExplanationAn error (INVALID, DISASTER or EXCEPTIONresponse) has occurred on a call to schedule aremote terminal delete by DFHALP during sign-offfor a surrogate terminal session running CRTE. Thedomain that detected the original error provides anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).



Module:DFHALP

AAL8

ExplanationDFHALP was processing a request that deadlocked.The most likely reason for the abend is that anALLOCATE QUEUE request has been suspendedbecause there are no contention-winning linksavailable.

AAL1 is issued for non time-out related deadlocks.

AAL8 is issued for stall purges and deadlock time-outs.

System actionCICS terminates the task abnormally. A transaction orsystem dump is not taken unless the transaction dumptable has been modified for AAL8.

User responseEnsure that there are enough contention-winningsessions available to satisfy the ALLOCATE QUEUErequest.

If you are running with modegroups, ensure that thereare contention-winning sessions available to satisfythe ALLOCATE request in that modegroup.

It might be necessary to increase the deadlocktimeout (DTIMEOUT) value for the transaction toprevent this abend from recurring.

If you require a transaction or system dump for thisabend then add AAL8 to the transaction dump table.

Module:DFHALP

AALA

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theAtomservice Manager. The domain that detected theoriginal error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).


Chapter 1. Transaction abend codes 3

User responseInform the system programmer. Examine the trace andthe dump to identify the point of error.

Module:DFHAMW2

AALB

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe CICS/MQ Connection Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).



Module:DFHAMMQ

AALC

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe JVMSERVER Resource Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).



Module:DFHAMSJ

AALM

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to the logmanager (LM) domain. The domain that detected theoriginal error provides an exception trace, a consolemessage, and possibly a system dump (depending onthe options specified in the dump table).



Module:DFHAMLM

AALN

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theTD manager. The domain that detected the originalerror provides a trace entry and possibly a systemdump (depending on the options specified in the dumptable).



Module:DFHAMTD

AALO

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theCICS/DB2 table manager DFHD2TM. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).




Module:DFHAMD2

AALP

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe Program Manager. The domain that detected theoriginal error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).



Module:DFHAMPG

AALQ

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe Business Application Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).



Module:DFHAMBA

AALR

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe Temporary Storage Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).



Module:DFHAMBA

AALS

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theGlobal Enqueue Manager. The domain that detectedthe original error provides a trace entry and possiblya system dump (depending on the options specified inthe dump table).



Module:DFHAMBA

AALT

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theInternet Inter-Orb Protocol Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).




Module:DFHAMOP

AALU

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theSockets Domain Manager. The domain that detectedthe original error provides a trace entry and possiblya system dump (depending on the options specified inthe dump table).



Module:DFHAMSO

AALV

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theEnterprise Java Domain. The domain that detected theoriginal error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).



Module:DFHAMEJ

AALW

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theWeb Domain. The domain that detected the originalerror provides a trace entry and possibly a systemdump (depending on the options specified in the dumptable).



Module:DFHAMWB

AALX

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe Pipeline Manager. The domain that detected theoriginal error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).



Module:DFHAMPI

AALY

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theISC/IP Domain. The domain that detected the originalerror provides a trace entry and possibly a systemdump (depending on the options specified in the dumptable).




Module:DFHAMIS

AALZ

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theDocument Handler. The domain that detected theoriginal error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).



Module:DFHAMDH

AAM1

ExplanationDFHXMCL has returned an unexpected responseduring the install of a transaction class. This can becaused by the task being purged during the install.

System actionThe transaction is abnormally terminated with a CICStransaction dump.

If an error has occurred, at the time the erroris detected, CICS issues a DFHXMnnnn consolemessage, records an exception trace entry and takesa system dump.

User responseDetermine why the task has failed. If there is a systemdump, use it together with the trace entry and theconsole message to resolve the problem. If there isno system dump, the task has been purged either by

the main terminal operator or as a result of deadlocktimeout.

Module:DFHAMP

AAM2

ExplanationDFHXMXD has returned an unexpected responseduring the install of a transaction definition. This canbe caused by the task being purged during the install.


If an error has occurred, at the time the erroris detected, CICS issues a DFHXMnnnn consolemessage, records an exception trace entry and takesa system dump.

User responseDetermine why the task has failed. If there is a systemdump, use it together with the trace entry and theconsole message to resolve the problem. If there isno system dump, the task has been purged either bythe main terminal operator or as a result of deadlocktimeout.

Module:DFHAMP

AAM3

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theLoader Domain. The domain that detected the originalerror provides a trace entry and possibly a systemdump (depending on the options specified in the dumptable).



Module:DFHAMLD

AAM4


ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to theResource Lifecycle Manager. The domain that detectedthe original error provides a trace entry and possiblya system dump (depending on the options specified inthe dump table).



Module:DFHAMRL

AAMA

ExplanationThere is an internal logic error in DFHAMP.


User responseIf you need further assistance from IBM to resolve thisproblem, see Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHAMP

AAMC

ExplanationThe task was purged before a GETMAIN request tothe storage manager domain was able to completesuccessfully.


User responseInvestigate the reason the task was purged. It waspurged either by the main terminal operator or as aresult of deadlock timeout.

Module:DFHAMP

AAMD

ExplanationAn unexpected return code has been received fromDFHDMP. This is due to an internal logic error.



Module:DFHAMP

AAMF

ExplanationAn unexpected return code has been receivedfollowing a call to the kernel (KE) domain. This mightbe due to an internal logic error.



Module:DFHAMP

AAMH

ExplanationAn unexpected return code has been receivedfollowing a call to DFHFCMT. This might be due to aninternal logic error.



http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/troubleshooting/cics/dfhs14n.html




Module:DFHAMP

AAMI

ExplanationAn unexpected return code has been receivedfollowing a call to DFHFCRL. This might be due to aninternal logic error.

System actionCICS terminates the task abnormally with a dump. Ifyou need further assistance from IBM to resolve thisproblem, see Working with IBM to solve your problemfor guidance on how to proceed.

User response:

Module:DFHAMP

AAMJ

ExplanationWhile installing a file, using RDO, a call was made toDFHFCFS to enable the file. An irrecoverable error wasreturned from DFHFCFS.


At the time the error is detected, CICS writes amessage to the console, records an exception traceentry and takes a system dump.


Module:DFHAMP

AAMK

ExplanationWhile installing a file, using RDO, a call was made toDFHFCDN. An irrecoverable error was returned fromDFHFCDN.

System actionThe task is abnormally terminated with a CICStransaction dump. At the time the error is detected,CICS writes a message to the console, records anexception trace entry, and takes a system dump.

User responseInform the system programmer, Examine the trace anddump to identify the point of error.

Module:DFHAMP

AAMN

ExplanationThere has been an unexpected return code from a callto DFHPRPT. This might be due to an internal logicerror.



Module:DFHAMP

AAMO

ExplanationAn invalid return code was returned from DFHTOR, theCICS terminal object resolution program.



Module:DFHAMP

AAMP






ExplanationAn unexpected return code has been received fromDFHPUP. This might be due to an internal logic error.



Module:DFHAMP

AAMQ

ExplanationAn attempt has been made to install a partner usingRDO. However, the partner resource manager (PRM)is unavailable having failed to initialize during CICSinitialization.


User responseIf you need to use the PRM, correct the problem whichprevented the PRM from initializing, and restart CICS.

Module:DFHAMP

AAMS

ExplanationThere has been an unexpected return code following aGETMAIN request to the storage manager. This is dueto an internal logic error.



Module:

DFHAMP

AAMT

ExplanationThere is an internal logic error in DFHAMP due to anunexpected return code from DFHTMP.



Module:DFHAMP

AAMZ

ExplanationAn unexpected return code has been received fromDFHZCP. This is due to an internal logic error.



Module:DFHAMP

AAO2

ExplanationCPI Communications has detected an unexpectedresponse from DFHLUC.


User responseThis is a CICS internal logic error.






A level 2 CICS trace for 'CP' of the transactiondocuments the course of events prior to this error(such as the modules called and their parameters).The level 2 trace also provides details of the erroritself.

If you need further assistance from IBM to resolve thisproblem, see Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHCPCBA

AAO3

ExplanationThe CPI interface detected that a call was madeto a CPI Communications function without CPICommunications being initialized. This implies thatCPI Communications initialization failed while CICSwas initializing.

System actionThe transaction is abnormally terminated with a CICStransaction dump. An exception trace entry is alsowritten when this event occurs.

User responseCheck the console listing to determine the reason whyCPI Communications failed to initialize during CICSinitialization. Correct the problem and restart CICS.

If the console listing indicates that CPICommunications initialized successfully, you needfurther assistance to resolve the problem. Collect theconsole listing, the traces and the transaction dump.See Working with IBM to solve your problem forguidance on how to proceed.

Module:DFHCPI

AAO4

ExplanationDFHZARL, or a module called by DFHZARL, hasdetected a logic error. This error is almost certainlycaused by the module receiving invalid data orindicators from VTAM.

System actionBefore returning to the CPI Communicationslayer, DFHZARL calls DFHZNAC to clean up thesession and put out messages on the CSNE log.CPI Communications abnormally terminates the

transaction with a CICS transaction dump, andproduces an exception trace entry.

User responseCheck the CSNE log to determine the type of error.You may need further assistance from IBM to fullyresolve this problem. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHCPCLR

AAO5

ExplanationThe task was purged before a GETMAIN request to thestorage manager (SM) domain was able to completesuccessfully. The domain that first detected the purgedcondition provides an exception trace.


User responseInvestigate the reason why the task was purged. It waspurged either by the main terminal operator or as aresult of deadlock timeout.

Module:DFHCPCBA, DFHCPCBI, DFHCPCBS

AAO7

ExplanationThe CPI Communications syncpoint request handlerhas been passed an invalid DFHLUC parameter list.This is a CICS internal logic error.


User responseA level 2 trace for 'CP' of the transaction shows thecourse of events before this error occurred (such asthe modules called and their parameters) plus detailsof the error itself. If you need further assistance fromIBM to resolve this problem, see Working with IBM tosolve your problem for guidance on how to proceed.

Module:DFHCPSRH








AAO8

ExplanationThe CPI Communications syncpoint request handlerhas been passed an invalid conversation control block(CPC). This is a CICS internal logic error.



Module:DFHCPSRH

AAO9

ExplanationA task has been purged either as a result of apurge from the main terminal operator via the CEMTtransaction, or by the task being timed out afterwaiting for longer than the DTIMOUT (deadlocktimeout) value specified for the transaction.


User responseInvestigate why the task was purged.

If the task was purged by the main terminal operator,this may have been in an attempt to clear the systemwhich appeared to be deadlocked for some reason.

If the task was timed out automatically as a resultof the DTIMOUT value being exceeded, this may bedue to insufficient main storage being available forthe number of tasks in the system. If the amountof main storage cannot be increased, the number oftasks in the system should be reduced to avoid short-on-storage situations. Another possibility would beto increase the value of the DTIMOUT option for thetransaction.

Module:DFHCPCLR

AAOA

ExplanationAn application has issued a CPI verb which CICSdoes not support. The entry point referenced in theapplication program was resolved in the link edit stub,but the function requested could not be resolved whencontrol passed to CICS.

There are two possible reasons for this:

• You have linkedited your application program witha CPI stub which supports more function than thisrelease of CICS.

• The linkedit stub has been corrupted.

System actionThe transaction is abnormally terminated with a CICStransaction dump. An exception trace entry is alsowritten.

User responseAt the time of the error, general register 0 points to an8-byte character string which should match the nameof the issued CPI call. Use the trace or the dump toverify that this character string is the name of a CPIfunction which is supported.

If the character string is not an intelligible characterstring, the stub has probably been corrupted.

Module:DFHCPI

AAOB

ExplanationAn application has issued a CPI verb which specifiesmore than eight parameters.

System actionThe transaction is abnormally terminated with a CICStransaction dump and an exception trace entry is alsowritten.

User responseChange your application program so that the correctnumber of parameters is specified on the CPI call.

Module:DFHCPI

AAOC




ExplanationCPI Communications is invoked with an invalid numberof parameters for call


User responseThe exception trace point produced with this abendcontains the incorrectly issued CPI Communicationsverb name. Use this to determine where theapplication program was in error and amend itaccordingly.

The z/VM: CPI Communications User's Guide manual,SC26-4399, provides a detailed description of all theCPI Communications verbs and how they should becalled.

Module:DFHCPARH

AAOD




Module:DFHCPCBI

AAOE




Module:DFHCPCBA

AAOF




Module:DFHCPCBS

AAOG

ExplanationDuring the processing of CMACCP (acceptconversation), CPI Communications detected that theapplication was attached with an unsupported synclevel.


User responseThis condition is caused by a back-end CPICommunications transaction being attached with async level that is not CM_NONE (0) or CM_CONFIRM(1).

Change the front-end transaction, (that is, the initiatorof the conversation in the other system) so that itdefines the sync level correctly.


https://www.ibm.com/support/knowledgecenter/SSB27U_7.1.0/com.ibm.zvm.v710.hcpb5/intr.htm

Module:DFHCPCBA

AAOH

ExplanationJournaling of data sent on a CPI communicationsmapped conversation has failed. This condition iscaused by a nonzero response from the CICS logmanager.


User responseUse the dump to ascertain why the journal or logrecord could not be written correctly. If a journalrecord length error is indicated, TIOATDL may havebeen corrupted.

Problem determinationRegister 12 addresses the current TCA and fieldTCAJCAAD and register 4 address the JCA. The logmanager request is contained in JCATR2 and theresponse code is in JCAJCRC.

Possible request codes are:

X'8001' - WRITEX'8003' - PUT

Possible response codes are:

X'01' - IDERROR - Journal identification errorX'02' - INVREQ - Invalid requestX'03' - STATERR - Status errorX'05' - NOTOPEN - Journal not openX'06' - LERROR - Journal record length errorX'07' - IOERROR - I/O error.

The address of the TIOA is contained in register 8 andits data length is in TIOATDL.

Analysis:

Register Label Description

R4=@JCA TCZARQPJ JCAJCRC is nonzero.

Module:DFHCPCOJ

AAOI

ExplanationThe journaling of data received on a CPICommunications mapped conversation has failed.


User responseThis condition is caused by an invalid response fromthe log manager. Use the dump to ascertain why thejournal or log record could not be written correctly. Ifa journal record length error is indicated, TIOATDL mayhave been corrupted.

Problem determinationRegister 12 addresses the current TCA and fieldTCAJCAAD and register 4 address the JCA. The CICSlog manager request is contained in JCATR2 and theresponse code is in JCAJCRC.


X'8001' - WRITEX'8003' - PUT


X'01' - IDERROR - Journal identification errorX'02' - INVREQ - Invalid requestX'03' - STATERR - Status errorX'05' - NOTOPEN - Journal not openX'06' - LERROR - Journal record length errorX'07' - IOERROR - I/O error


Analysis:



Module:DFHCPCRI, DFHCPCRW

AAOJ

ExplanationCPI Communications has detected an unexpectedresponse from one of its internal routines.




A level 2 trace for 'CP' of the transaction shows thecourse of events prior to this error. For example, themodules called and their parameters. The level 2 tracealso provides details of the error itself.


Module:DFHCPIC

AAOK

ExplanationCPI Communications has detected an unexpected callto one of its internal routines.



A level 2 trace for 'CP' of the transaction shows thecourse of events prior to this error, for example, themodules called and their parameters. The level 2 tracealso provides details of the error itself.


Module:DFHCPIC

AAOL

ExplanationCPI Communications has made an invalid call toDFHLUC.





Module:DFHCPCLR

AAOM

ExplanationThe CPI Communications and the DFHZUSR statemachines are out of synchronization.



A level 2 trace for 'CP' of the transaction shows thecourse of events prior to this error. For example, themodules called and their parameters. The level 2 tracealso provides details of the error itself.


Module:DFHCPCLR, DFHCPSRH

AAON

ExplanationCPI Communications has detected an unexpectedresponse from DFHLUC.



A level 2 trace for 'CP' of the transaction shows thecourse of events prior to this error. For example, the






modules called and their parameters. The level 2 tracealso provides details of the error itself.


Module:DFHCPCLR, DFHCPCLC

AAOO

ExplanationCPI Communications has been invoked with an invalidfirst parameter. The first parameter should be the codeof the function to be performed. This is a CICS internallogic error.


User responseA level 2 trace for 'CP' of the transaction shows thecourse of events before this error occurred (such asthe modules called and their parameters) plus detailsof the error itself.


Module:DFHCPARH

AAOP

ExplanationThe CPI Communications state machine has beenrequested to perform a state transition request thatis considered to be an 'impossible' situation. (Thez/VM: CPI Communications User's Guide manual,(SC26-4399) documents all these situations.)

There are two possible causes of this error:

• The CPC (conversation control block) has beenoverwritten in such a way that the conversation statehas been altered, or

• There is an error in the CPI Communications statemachine.


User responseA level 2 trace for 'CP' of the transaction shows thecourse of events prior to this error, for example, themodules called and their parameters. The level 2 tracealso provides details of the error itself.

The transaction dump shows the CPC. You may needfurther assistance from IBM to fully resolve thisproblem. See Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHCPCFS

AAOQ

ExplanationThe return code generated by CPI Communicationsdoes not have an entry in the state table againstthe current CPI Communications verb. This error isdetected by the CPI Communications state machine.





Module:DFHCPCFS

AAOR

ExplanationCPI Communications has detected an invalid value inthe CPC (conversation control block).

There are 2 possible causes of this error:

• The CPC (conversation control block) has beenoverwritten, or

• There is an error in CPI Communications whichcauses it to reject valid values.




https://www.ibm.com/support/knowledgecenter/SSB27U_7.1.0/com.ibm.zvm.v710.hcpb5/intr.htm





Module:DFHCPIC

AAOS

ExplanationCPI Communications has detected that theconversation state is RESET for a situation where thisshould not occur. That is, the conversation controlblock (CPC) is about to be deleted.

There are two possible causes of this error:

• The CPC has been overwritten, or• There is an error in CPI communications.


User responseA level 2 trace for 'CP' of the transaction shows thecourse of events prior to this error, for example, themodules called and their parameters. The level 2trace also provides details of the error itself. You mayneed further assistance from IBM to fully resolve thisproblem. See Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHCPIC

AAOT

ExplanationWhile chaining through the CPCs (conversation controlblocks) for a given conversation, CPI Communicationsdetected that the chain was broken.

There are two possible causes of this error.

1. The CPC chain has been overwritten, or2. There is an error in the CPI Communications

chaining mechanism.


User responseDetermine which of the above caused the error.


You may need further assistance from IBM to fullyresolve this problem. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHCPCBI

AAOU

ExplanationCPI Communications has detected an error in theTP_name or partner_LU_name while processing aninitialize conversation request. The TP_name orpartner_LU_name is obtained by lookup of thesym_dest_name in the partner resource table (PRT).

There are two possible causes of this error.

1. The entry in the PRT contains invalid data, or2. There is an error in the mechanism that returns the

data from the PRT and interprets it.




Module:DFHCPCBI

AAOV

ExplanationCPI Communications has detected that its internalstate table is corrupted.






This error is detected by the CPI Communicationsstate machine.





Module:DFHCPCFS

AAOW

ExplanationCPI Communications has detected an internal logicerror in DFHCPCLC.





Module:DFHCPCLC

AAOX

ExplanationCPI Communications has detected a bad syncpointreturn code which has been set on a synclevel 0 or1 conversation. The bad return code is only expectedon a synclevel 2 conversation.





Module:DFHCPIC

AAOY

ExplanationCPI Communications detected an invalid LL field in theGDS records from which it was receiving on a mappedconversation.

Although it is possible that the remote system issending invalid records, it is more likely to be an errorin the receive logic because DFHZARRC (a lower levelreceive module) also checks the LLs before passingthem to CPI Communications.


User responseUse CICS traces and, possibly a VTAM trace, todetermine the data that was sent between bothsystems.



Module:DFHCPCRB

AAOZ







ExplanationCPI Communications has detected an invalid IDfield in the GDS records it was receiving on amapped conversation. The exception trace point thataccompanies this abend gives the ID field in data 3.The valid IDs are '12FF'X for application data and'12F1'X for null data.


User responseUse CICS traces and, possibly, a VTAM trace todetermine the data that was sent between bothsystems.



Module:DFHCPCRB

AASA

ExplanationAn unexpected EXCEPTION response was receivedfrom a call to the user (US) domain during initializationof a child task.

The call was issued during initialization of atransaction that was started without a terminal. Thecall was made as part of processing to associate thetransaction with its intended user.


User responseExamine the messages produced for the CICS job bythe external security manager (ESM). This may requirethe assistance of a security administrator.

It may be necessary to examine the transaction dumpto determine why the external security manager hasinformed CICS that the user is not correctly defined.

Module:DFHASXM

ABxx abend codesABAC

ExplanationAn activity issued EXEC CICS RETURN (without theENDACTIVITY option) but no events were processedduring the activation. The activity was executed with aRUN command.

System actionThe task is abnormally terminated with a CICStransaction dump. The EXEC CICS HANDLE ABENDcommand cannot handle this abend.

User responseInvestigate why the activity did not process anyevents.

Module:DFHBASP

ABAD

ExplanationAn activity issued EXEC CICS RETURN ENDACTIVITYwhile there were activity completion events pending.The activity was executed with a RUN command.

System actionThe task is abnormally terminated with a CICStransaction dump. The EXEC CICS HANDLE ABENDcommand cannot handle this abend.

User responseInvestigate why the activity had pending activitycompletion events.

Module:DFHBASP

ABAE

ExplanationAn activity issued EXEC CICS RETURN (without theENDACTIVITY option) but no events were processed




during the activation. The activity was executed with aLINK command.

System actionThe task which issued the LINK is abnormallyterminated with a CICS transaction dump. The EXECCICS HANDLE ABEND command cannot handle thisabend.

User responseInvestigate why the activity did not process anyevents.

Module:DFHEIBAM

ABAF

ExplanationAn activity issued EXEC CICS RETURN ENDACTIVITYwhile there were activity completion events pending.The activity was executed with a LINK command.

System actionThe task which issued the LINK is abnormallyterminated with a CICS transaction dump. The EXECCICS HANDLE ABEND command cannot handle thisabend.

User responseInvestigate why the activity had pending activitycompletion events.

Module:DFHEIBAM

ABLA



User responseInvestigate why the task was purged. It was purgedeither by the main terminal operator or as a result ofdeadlock timeout.


If the task was timed out automatically as a resultof the DTIMOUT value being exceeded, this may bedue to insufficient main storage being available forthe number of tasks in the system. If the amountof main storage cannot be increased, the number oftasks in the system should be reduced to avoid short-on-storage situations. Another possibility would beto increase the value of the DTIMOUT option for thetransaction.

Module:DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR

ABLB

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call tothe storage manager (SM) domain. The domain thatdetected the original error provides an exception trace,a console message and, possibly, a system dump(depending on the options in the dump table).


User responsePlease see the related message produced by thedomain that originally detected the error.

Module:DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR

ABM0

ExplanationThe map specified for a basic mapping support (BMS)request could not be located.


User responseCheck if the map has been defined. If it has, check thatit has been specified correctly.

Module:DFHMCP, DFHMCX, DFHMCY


ABM1

ExplanationA basic mapping support (BMS) service is requested bya task associated with a terminal that is not supportedby BMS. The request is not a routing request.


User responseDo not use terminals not supported by BMS forapplications using BMS services.

Check the terminal type and model number. Confirmthat it is a terminal that is not supported by BMS.A list of terminals supported by BMS is given in theDeveloping CICS Applications. Check that the resourcedefinition for the terminal accurately describes thephysical terminal.

Problem determinationAt the time of the abend, register 11 addresses theTCTTE, and TCTTETEA and register 6 address theTCTTE extension, TCTETTE.

Relevant fields are:

TCTTEDDS the device dependent suffix.TCTTEMSS the map set suffix.

Analysis: DFHRLR tests the device dependent suffixand the map set suffix in the TCTTE extension. If bothof these are zero, the terminal is not supported by BMSand DFHRLR abends the task with the abend codeABM1.


R4= RLRSFXCK TCTEDDS=X'00' and TCTEMSS=X'00'.@TCTTETE The device dependent suffix and the map set suffix have loaded into the lower two bytes of register 3 by the subroutine RLRSUFXS.

Module:DFHRLR

ABM2

ExplanationNo user data was supplied for this BMS request. Thatis, the address of a user data area was not found ineither TCTTEDA or TCAMSIOA.

When a BMS macro level output request is issued,the user must have placed the address of the data tobe passed to BMS in TCTTEDA or TCAMSIOA beforeissuing the macro. The choice is made on the followingcriteria:

• If the data is to be passed in a TIOA by a terminal-oriented task, the address of this TIOA may beplaced either at TCTTEDA, or in TCAMSIOA togetherwith the setting of binary zeros into TCTTEDA.

• If the data is being passed by a terminal-orientedtask but not in a TIOA, the address of the TIOA-likearea of this data must be placed in TCAMSIOA andbinary zeros set into TCTTEDA.

• If the data is being passed by a non-terminal-oriented task, the address of the TIOA-like area ofthis data must be placed in TCAMSIOA. TCTTEDAcannot be referenced, because there is no TCTTEassociated with this task.

If a task attempts to pass addresses from bothTCTTEDA and TCAMSIOA, the address in TCTTEDA isthe one selected.


User responseThe programmer must place the address of the datainto TCTTEDA or TCAMSIOA, whichever is appropriate.

Firstly, check that the user has loaded TCTTEDA orTCAMSIOA with the address of the user data, bychecking the application listing and the contents ofTCTTEDA and/or TCAMSIOA.

Next, check that the BMS request has been correctlydecoded by CICS by referring to the OSPWA requestbytes (OSPTR1-8) or decoding the last BMS entryin the trace table. See OSPIND01 to check correctdecoding of PAGEBLD or TEXTBLD, and TCAFCI bit 7to identify whether the task is terminal-oriented or not.

At the abend point, register 1 contains the user dataaddress last loaded, and register 4 the address ofOSPTIOA as an address of null data.

If a CICS error is suspected, concentrate initiallyon subroutine MCPFTIOA, because this is a simplepiece of code that shows the data-fetch logic. ABM2


https://www.ibm.com/support/knowledgecenter//applications/developing.html

condition is trapped early in the CICS decoding of theDFHBMS request and involves module DFHMCP only.

Case/Register Label Description

R9=@OSPWA MCPMAP OSPTR4 has OSPTRM (X'04') bit set for TYPE=MAP.

R9=@OSPWA MCPPGBLD OSPTR5 has OSPTRB (X'80') bit set and BMS sets bit OSPLMPB (X'08') in OSPIND01 for TYPE=PAGEBLD. OSPTR4 has X'40', X'80', or X'C0' set for DATA=NO, ONLY, or YES respectively, so should be X'80' or X'C0'.

R9=@OSPWA MCPTXBLD OSPTR7 has OSPTRX (X'80') bit set and BMS sets bit OSPLMTB (X'04') in OSPIND01 for TYPE=PAGEBLD. OSPTR4 has X'40', X'80', or X'C0' set for DATA=NO, ONLY, or YES respectively, so should be X'80' or X'C0'.

R9=@OSPWA MCPMAPNG OSPTR3 has OSPTSN (X'01'), OSPTSA (X'02'), or OSPTMN (X'04') bits set, or OSPTR4 has OSPTMA (X'10') bit set for mapping. OSPTR4 has X'04' or X'80' or X'C0' set for DATA=NO, ONLY, or YES respectively, so should be X'80' or X'C0'.

All R12=@TCA MCPFTIOA TCAFCI has TCAFCTRM (X'01') bit set if the task is terminal-oriented.

All R11=@TCTTE MCPFTIOA TCTTEDA could point to a use TIOA but does not, thus causing the abend.All R12=@TCA MCPFTIOA TCAMSIOA could point to a user data area (TIOA or otherwise), but does thus causing the abend.

All R9=@OSPWA MCPNTOTM OSPTIOA contains the address of the user area found, so is zero. OSPSIOA points to OSPIOA (which is copied from TCAMSIOA) as being the second-dry data area sought by BMS for data . OSPIA (TCAMSIOA) was also zero so causing the abend.

Module:

DFHMCP

ABM3

ExplanationA BMS input or output request has been issued from atask that is not terminal-oriented.

System actionThe task is abnormally terminated with a CICS dump.

User responseThe task issuing a BMS input or output request mustbe attached to a terminal.

Module:DFHMCP

ABM4

ExplanationAn invalid request response has been received toa temporary storage PUT or PUTQ request issuedby BMS. The data passed to the temporary storageprogram has an invalid length.



Determine from the trace table whether the abendoccurred in DFHMCP or DFHTPP.

Check the length of the appropriate area.

If the MCR length is invalid, possible reasons are:

• The title record specified in the TITLE option on aBMS ROUTE request has an invalid format, that is, itdoes not begin with a halfword length field or is morethan 64 characters.

• The message is being routed to more terminals thanintended. OSPTTCNT is very large, for example, ifLIST=ALL is specified on a ROUTE request and thereare a large number of terminals in the TCT.

If the page buffer length is too large, this may bebecause more data than intended is being built intothe page. If the page buffer length is greater than thelength of the storage area indicated in the preceding



storage accounting area, an error has occurred in pageor text building, and the page buffer extends beyondthe area allocated to it (that is, storage violation).

Problem determinationAbend in DFHMCP (see Analysis)

The OSPWA (output services work area) is in userstorage and is printed in a transaction dump. It isaddressed by register 9 at the time of the abend.Relevant fields are:

OSPTITLEOSPTTCNTOSPPLTIOSPTOTPG

The message control record (MCR) is an area of userstorage obtained by BMS. It is addressed by register8 at the time of the abend. The first 8 bytes containstorage accounting information. MCRLLBB contains thelength of the MCR (halfword) abend in DFHTPP.

The page buffer is addressed by register 7 at the timeof the abend. It contains storage accounting fields inthe first 8 bytes and a halfword length at offset 8(TSIOAVRL).

In both cases, the temporary storage usemap (DFHTSMAP) is addressed from CSATSATA.TSMAPCOM contains the number of available bytes ina control interval on the temporary storage data set.

Analysis: If the temporary storage request precedingthe abend is a DFHTS PUT, the abend occurred inDFHMCP. If the temporary storage request precedingthe abend is a DFHTS PUTQ, the abend occurred inDFHTPP. If the abend occurred in DFHMCP, DFHMCPis attempting to put the message control record totemporary storage. Check the length of the MCR(MCRLLBB). It may be negative.

The length of the MCR is calculated by code followinglabel MCPNODDS and is:

28 + 21 * OSPTTCNT + (length of title record) + (space for page/LDC table, if needed)

The address of the title record is at OSPTITLE andthe length is contained in the first halfword. Space forthe page/LDC table is required if OSPPLT1 is nonzero,which should occur only for messages routed to LDCdevices (3600, 3650, 3767, 3770, 3790). The numberof entries is in OSPTOTPG. 2 bytes are required perentry.

If the abend occurred in DFHTPP, BMS is attemptingto add a page to the temporary storage queue, and

the page buffer will not fit in the control interval.TSIOAVRL contains the length of the page buffer.

For messages directed to 3270 devices, the pagebuffer consists of a 3270 data stream with a 4-bytepage control area following it (a 3270 data streammay be larger than the number of characters availableon the screen, particularly if extended 3270 attributesare used). For messages directed to other devices, thepage buffer consists of a message formatted with NLcharacters, a 4-byte page control area following it. Thelength in TSIOAVRL should be less than the length inthe preceding storage accounting area, otherwise anerror has occurred in constructing the page, possibly inprior BMS requests.

In either of the above cases, if the length of the areabeing output appears valid, it is necessary to increasethe control interval size for the temporary storage dataset.


DFHMCPR8=@MCR MCPMCRTS The MCR is too long or has invalid length ($4).

DFHTPPR7=@pgbuf TPNOPGL The page buffer is or too large. TPNODDS

Module:DFHMCP, DFHTPP

ABM5

ExplanationA DFHTS TYPE=PURGE request has been issued withan invalid REQID. This incorrect request was issued bybasic mapping support (BMS).

DFHTPR cannot find the terminal identifier for thecurrent terminal in the terminal list in the messagecontrol record (MCR).


User responseCheck the trace table and find the preceding PUT/PUTQ TS requests. Check whether the identifier forthe PUT/PUTQ is the same as that for the PURGE. Ifit is not, find out how they differ. Check to see if theOSPWA has been corrupted.


This error is very unlikely, as the label indicates(TPRSNH - "Should Not Happen"). DFHTPS hasscanned the MCR to identify the terminals to whichthis message is directed, and has created an AID toinitiate CSPG (DFHTPR) at each of them. However,when DFHTPR retrieves the MCR, it cannot find thecurrent terminal identifier in the list of terminals.Presumably the MCR has been corrupted betweencreation of the AID and dispatching of CSPG at theterminal. Check back through the trace table to findthe instance of DFHTPS that built the AID for thisterminal (transaction CSPS); it will have issued a TCLOCATE request to verify that the terminal identifier isvalid, and this identifier can be seen in the trace entry.

Problem determinationThe TS identifier is built in TCATSDI before the TSpurge is issued, although this has probably beenoverwritten before the dump is taken. The trace tableentry for the DFHTS TYPE=PURGE contains the TSidentifier in the last 8 bytes.

The OSPWA is addressed by register 9.

OPSTSID temporary storage identifier (8 bytes).

Register 8 points to the MCR.

Register 5 points to the current entry.

Register 0 points to the end of table.

Register 9 points to the TCTTE.

The terminal list starts at MCRIDLST and the terminalidentifier is at the start of the terminal entry. Eachterminal entry is X'15' bytes long.

Analysis: DFHMCP uses the temporary storageidentifier in OSPTSID.

Cannot find the terminal identifier for this terminal inthe terminal list in the MCR.


R9=@(OSPWA) MCPCKPGS Code builds the temporary storage code in TCATSDI and issues DFHTS TYPE=PURGE macro, specifying IDERROR exit of MCPTSIDE, where the abend is raised.

R8=@(MCR) TPRCKID Code scans terminal list for a terminal entry that has the id of the current terminal, and if it cannot be found, links to TPRSNH to raise the abend.

Module:DFHMCP, DFHTPR

ABM6

ExplanationTransaction CSPS, scheduled internally by BMS, hasnot been installed.


User responseInstall the transaction CSPS (Group DFHBMS).

Module:DFHMCP

ABM7

ExplanationThe trailer specified to be used while building pages oftext data is longer than the page.


User responseCorrect the application program that issues therequest with too long a trailer.

Module:DFHPBP

ABM8

ExplanationA BMS text request specified a value for the JUSTIFYoption which is zero or too large for the page beingbuilt.


User responseCorrect the application program that specified toolarge or zero value for the JUSTIFY option.

Module:DFHPBP

ABM9


ExplanationThe text data overflow routines have been reenteredwhile text overflow was in process. This conditionoccurs when the line requirements for the text headerand/or trailer exceed the line capacity of the page forwhich data is being formatted.


User responseReduce the number of lines required for the headerand/or trailer or increase the page size of the terminal.

Module:DFHPBP

ABMA

ExplanationThe user has supplied a terminal I/O area (TIOA) withan invalid data length that was either equal to zero orgreater than the storage accounting length minus 12.

Alternatively, the length field of a header or trailer areaprovided by the application program is invalid (that is,not positive).


User responseCorrect the program that supplied the erroneous datalength.

Check the TIOA. If either of the conditions described ispresent, check the application program. For programsusing command-level interface, the TIOA is obtainedby CICS using the length of the data item passedin the FROM option on an EXEC CICS SEND MAP orEXEC CICS SEND TEXT command, or in the TRAILERor HEADER option on an EXEC CICS SEND TEXT or anEXEC CICS SEND PAGE command. Check the data itemfor zero length.

Header and trailer records have a special formatdescribed in the CICS Application developmentreference. An ABMA abend occurs if the first halfword(the length) is not positive. Check the remainder ofthe header/trailer record for validity when the length ischecked.

Problem determinationThe output services work area (OSPWA) is in userstorage and will be printed in a transaction dump. Itis addressed by register 2 at the time of the abend.Relevant fields are:

• OSPTR7• OSPHDRA• OSPTRLA

Register 4 or OSPTIOA points to the TIOA. In the TIOA,the following fields are relevant:

• TIOATDL• TIOASAL

Analysis:


R4=@TIOA PBCKTDL TIOATDL is zero or greater than TIOASAL-12.

R2=@OSPWA PBD20080 R0 (= first halfword ofR0=length trailer) is zero.of trailer R8=OSPTRLA.R8=@trailer OSPTR7 has X'20' bit set.

R2=@OSPWA PBDTXHDR R0 (= first halfword ofR8=@header header) is zero.R0=length R8=OSPHDRA. of header. OSPTR7 has X'40' bit set.

Module:DFHPBP, DFHMCP

ABMB

ExplanationThe user has specified a cursor position in the BMSoutput request. It is larger than the current screen sizefor the 3270 for which output is being built.


User responseCorrect the program that specified the incorrect cursorlocation.

Use trace to identify the statement issuing the request.Check that the cursor position is being correctly set.The program may have been designed to run inalternate screen size mode but is being run in defaultscreen size mode, or it may have been designed to runon a 3270 model different from the one in use. If the


https://www.ibm.com/support/knowledgecenter//reference-applications/reference-programming.html


program is routing a message, the route list should bechecked. If the program is to run with various 3270models, the cursor position should be within the sizeof the smallest screen.

Problem determinationIf the abend occurs in DFHPBP:

At the time of the abend, register 2 points to theOSPWA and register 1 to the TTP. Relevant fields are:

• OSPTR3 has X'10' bit set to indicate a user-specifiedcursor position

• OSPCP contains a halfword cursor position specifiedby user

• TTPSCSZ contains the halfword value of the screensize to compare against.

If the abend occurs in DFHMCP or DFHMCX:

• Register 6 points to the OSPWA (in LIFO storage)• OSPCP contains a halfword cursor position specified

by user• OSPTR3 has X'10' bit set to indicate a user-specified

cursor position• OSPSCSZ contains the halfword value of the screen

size to compare against.

Analysis:


In DFHPBP:R2=@OSPWA PBDBADC OSPTR3 X'10' bit set indicates the user-R1=@TTP specified cursor position. TTPSCSZ halfword screen size. OSPCP halfword cursor position.

In DFHKCP or DFHMCX:R6=@OSPWA MCENEAU2 OSPTR3 X'10' bit set indicates the user- specified cursor position. OSPSCSZ halfword screen size. OSPCP halfword cursor position.

Module:DFHPBP, DFHMCP (for minimum-function BMS),DFHMCX

ABMC

ExplanationThe CMSG transaction is attempting to send amessage to a greater number of terminals than is

possible. There is no fixed maximum because thevalue depends on the other operands specified on therouting command.


User responseRedefine the route list.

Module:DFHMCP

ABMD

ExplanationDFHTPR or DFHTPP has issued a DFHDI TYPE=SENDand has received a return code other than "FUNCERR-REQUEST FOR CHANGE DIRECTION SIGNALED" or"NORESP"


User responseInform your system programmer.

Module:DFHTPP, DFHTPR

ABME

ExplanationDFHTPR or DFHTPP has detected an invaliddatastream or DFHWBBMS detected invalid formsdata while processing a basic mapping support (BMS)request.

System actionThe transaction is abnormally terminated with a CICStransaction dump. If the ABEND was issued fromDFHTPR or DFHTPP then register 7 indicates thelocation at which the ABEND was detected.

User responseIf DFHTPR or DFHTPP issued the ABEND then examinethe transaction dump for bad data in the TIOA. Ifthe origin of the bad data is an application program,correct the program. If DFHWBBMS issued the ABEND


then check the validity of the incoming forms data inthe CICS trace.

Module:DFHTPP, DFHTPR, DFHWBBMS

ABMF

ExplanationThe value specified for the length option of the basicmapping support (BMS) send map is greater than thelength of the 'from' area.


User responseRedefine the value for the length option.

Module:DFHPBP

ABMG

ExplanationThe user has requested a basic mapping support(BMS) service that was not specified at systemgeneration, or at initialization.


User responseCorrelate services requested against options specifiedin the system generation of BMS.

Follow this procedure:

1. Scan the trace table for the transaction ID thatissued the abend. If this is CSPQ (page cleanup),module DFHTPQ abnormally terminated because amessage purge delay of zero has been specifiedand CSPQ has been entered via a terminal. Themessage purge delay is specified in the PRGDLAYof the DFHSIT macro, and its value can be found inSITPRGD.

2. Scan the trace table for the last BMS request (code'FA'). Use the option bytes at the start of the failingmodule to see if the requested functions have beengenerated. For example, paging may have beenrequested, but standard or minimum BMS wasspecified in the SIT.

3. If the BMS request is compatible with the BMSoptions in the CICS system generation, someincompatible suffixing amongst BMS modules musthave occurred. This can happen if the DFHSITmacro specified individual suffixes for the BMSmodules.

The following modules differ between standard andfull-function BMS:

DFHMCPDFHRLRDFHPBPDFHTPP

Module:DFHMCP, DFHTPQ

ABMH

ExplanationThe BMS mapping program DFHMCX or DFHMCY failedin an attempt to update the output TIOA because itdetected that storage outside the TIOA would havebeen corrupted.


User responseIdentify and inspect the BMS map being used with theBMS SEND command. Check the map for errors in themap definition such as inconsistencies between thelength specified on the DFHMDF macro and the actuallength of data included in the field. If no errors can beidentified contact IBM support for further assistance.

Module:DFHMCX, DFHMCY

ABMI

ExplanationThe map specified for a BMS input mapping requestwas not an input map.


User responseEither define another input map or redefine theexisting map.



ABML

ExplanationThe terminal control locate routine received invaliddata from DFHRLR and returns with an error returncode. DFHRLR is attempting to scan the TCT for aBMS ROUTE request with LIST=ALL or operator classor operator ID specified in the route list. The terminalcontrol table may have been corrupted.



The terminal control table has probably beencorrupted during execution. Attempt to scan throughthe TCT in a dump. (Because the system dump usesthe same technique for printing all TCTTEs, the systemdump fails at the same point.)

Determine which entry is incorrect. It may be thatthe TCTTE has been overwritten by user data that isrecognizable in the dump.

Check the application program for references to theTCTTE pointer. Check for user data that may beaddressed from the same pointer.

In an assembler program, there may be multipleequates for the TCTTE base register.

It may be that the TCT is being overwritten bysome earlier transaction. If this is so, it is probablyone associated with the terminal whose TCTTE isoverwritten.

Problem determinationRegister 11 points to the current TCTTE in the search.

The TCT prefix (DFHTCTFX) can be located fromCSATCTBA.

The first terminal entry (TCTTE) in the TCT isaddressed by TCTVTEBA.

TCTTETEL is the halfword offset from current TCTTE tothe next.

Analysis: The current TCTTE address is either not ona full-word boundary or is not within the limits of theTCT, or the address of the next TCTTE, obtained by

adding TCTTETEL to the current address, is invalid.This check is made by locate code (DFHZLOC) inDFHZCX.

Register Label DescriptionR11=@TCTTE RLRLOCN Issue DFHTC CTYPE=LOCATE

Module:DFHRLR for full-function BMS

ABMM

ExplanationAn invalid map was specified.


User responseUse the supplied dump to diagnose the problem.Register 6 contains the address of the BMS instructionbeing executed when the error was recognized.

Module:DFHPBP

ABMO

ExplanationThe map specified for a BMS output mapping requestwas not an output map.


User responseEither define another output map or redefine theexisting map.


ABMQ

ExplanationThe query transaction (CQRY) has been initiatedand either the task is not terminal-oriented, or theassociated terminal is not defined to CICS as a 3270or SCSPRINT device. This abend will occur if CQRY isentered at a console, even when the console is a 3270device, since the console has the appearance to CICS



of a keyboard/printer device. The CQRY transactiondoes not have an operator interface, and under normalconditions there is no need for an operator to invokeCQRY or for a user transaction to START the CQRYtransaction. CQRY is run automatically by CICS when a3270 or SCSPRINT device connects. In the transactiondump, register 8 contains the address of the TCTTEfor the associated terminal. If register 8 contains zero,this indicates that the task is not terminal-oriented.


User responseEnsure that the terminal associated with CQRY is ofthe 3270 or SCSPRINT family of devices.

Module:DFHQRY

ABMR

ExplanationThe Page Retrieval transaction (CSPG) has beeninitiated but the task is not terminal-oriented.


User responseEnsure that a terminal is associated with the CSPGtransaction.

Module:DFHTPR

ABMT

ExplanationA BMS request has been issued for a terminal typewhich does not support the level of BMS required bythe request. This might be a non-3270 type terminalfor an input or output request, or a non-bridge facilityfor a locate map request. Locate map requests are onlyissued internally by CICS 3270 bridge related code.

This abend might also be issued if the level of BMSrequired by the request is not supported by the CICSregion.

System actionThe task is abnormally ended with a CICS transactiondump.

User responseEnsure that the terminal and the CICS region supportsthe BMS request.

Module:DFHMCP, DFHMCX

ABMU

ExplanationThe application program supplied an address that isnot within region boundaries. The low-order 3 bytes ofgeneral register 1 in the transaction dump contain theerroneous address. The high-order byte of register 1indicates the address type as follows:

X'01' - Title address (TCAMSTA)X'02' - Alternate I/O area address (TCAMSIOA)X'03' - Map address (TCABMSMA)X'04' - Header address (TCAMSHDR)X'05' - Route list address (TCAMSRLA)X'06' - Trailer address (TCAMSTRL)X'07' - Map set address (TCAMSMSA)X'08' - TIOA address (TCTTEDA)


User responseCorrect the application program that is supplying theerroneous address.

Module:DFHMCP, DFHEMS

ABMV

ExplanationDFHRLR has detected an invalid route list entry.


User responseCheck that the route list is correctly built with reservedfield in the entry containing blank and a stopper ofhalfword X'FFFF' to terminate the list.

Module:DFHRLR

ABMX


ExplanationA text string passed to BMS contained a set attributeorder that was invalid for one of the following reasons:

1. The set attribute sequence was less than threecharacters.

2. The attribute type was invalid.


User responseCorrect the application program.

Module:DFHPBP

ABMY

ExplanationBMS is building a TTP (Terminal Type Parameter)control block but the pagesize selected for a terminalby BMS is zero because either the default or alternatescreensize has been defined as zero.

In the transaction dump, significant general purposeregister contents are as follows:

1. Register 6 points to the BMS extension of theTCTTE

2. Register 10 points to the TTP (Terminal TypeParameter) control block

3. Register 11 points to the TCTTE


User responseCheck the TERMINAL and TERMTYPE definitions whichdetermined the attributes of the offending TCTTE.

Module:DFHRLR

ABMZ

ExplanationThe address of the terminal I/O area (TIOA) inTCTTEDA was found to be zero.

When using BMS fast path as a result of anEXEC CICS RECEIVE MAP, DFHEMS always initializes

TCTTEDA with the address of the TIOA. If TCTTEDAis subsequently found to be zero by DFHMCX, anoverwrite must have occurred.


User responseInvestigate why TCTTEDA is zero.

Scan the trace table for the last BMS request (codeFA) for the failing task and try to determine whichuser programs have been given control since that BMSrequest.


ABNA

ExplanationNo route list was supplied with a route requestreceived from the :i1.DFHTPS abend codes remotesystem.



Module:DFHTPS

ABNB

ExplanationEither the principal facility of the task is not a TCTTE ofthe correct type, or the task has no principal facility.


User responseEnsure that DFHTPS has not been specified as theinitial program of a transaction other than CSPS. Checkthat the operator did not enter CSPS from the terminal.



Module:DFHTPS

ABNC

ExplanationAn attempt to access a temporary storage queuefailed.


User responseEnsure that temporary storage is correctly generated.

Module:DFHTPS

ABNE

ExplanationAn error response was received from an invocation of aBMS TYPE=ROUTE or TYPE=STORE request.


User responseCheck that BMS was correctly generated.

Module:DFHTPS

ABNF

ExplanationThe transaction was not in send mode when it sentdata to the remote system.



Module:DFHTPS

ABNG

ExplanationAn attach request was received from the remotesystem without any data indicating the reason for therequest.



Module:DFHTPS

ABNH

ExplanationAn attempt to ship data to the remote system failed.



Module:DFHTPS

ABNI

ExplanationCICS could not find a profile for an LU6.2 transactionrouting request.

System actionCICS terminates the task abnormally.

User responseEither you have specified an incorrect name in thePROFILE parameter of an EXEC CICS ALLOCATEcommand, or you have not installed the profile. Correctthe error before resubmitting the transaction.





Module:DFHTPS

ABNJ

ExplanationThe task was purged before a call to another domainwas able to complete successfully. The task that firstdetected the purged condition provides an exceptiontrace.



Module:DFHTPS

ABNK

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call anotherdomain. The domain that detected the original errorprovides an exception trace, a console message and,possibly, a system dump (depending on the optionsspecified in the dump table).



Module:DFHTPS

ABR3

ExplanationAn unsupported BMS request was received by thebridge exit.


User responseThe bridge only supports minimum function BMS andSEND TEXT. This transaction cannot be used in abridge environment.

Module:DFHEMS

ABR4

ExplanationThe link DFHL3270 command did not specify acommarea.


User responseThe link DFHL3270 command must specify acommarea to contain the BRIH and any messagevectors.

Module:DFHBRMR

ABR5

ExplanationThe commarea specified in the link DFHL3270command is shorter than the BRIH.


User responseThe link DFHL3270 command must specify acommarea to contain the BRIH and any messagevectors.

Module:DFHBRMR

ABR6


ExplanationThe commarea specified in the link DFHL3270command does not contain a valid BRIH.


User responseThe link DFHL3270 command must specify acommarea which must contain a valid BRIH.

Module:DFHBRMR

ABRC

ExplanationThe bridge exit is not defined and could not beautoinstalled.

System actionThe task is abnormally terminated with a CICStransaction dump. The user transaction will not bestarted.

User responseEither define the program using RDO or change theprogram autoinstall exit to allow it to be autoinstalled.

Module:DFHBRMS, DFHBRTC

ABRD

ExplanationThe bridge exit is disabled.


User responseIdentify why the bridge exit is disabled. Enable thebridge exit and retry the action.


ABRE

ExplanationThe bridge exit could not be loaded.


User responseInvestigate why it cannot be loaded. It may not havebeen defined in the DFHRPL library.


ABRF

ExplanationThe bridge exit is defined as remote.


User responseDefine the bridge exit as a local program.


ABRG

ExplanationAn invalid bridge facility token was specified


User responseThis error was probably caused by the incorrectdata being sent to the bridge exit from the clientapplication.

Check the data set by tracing the data sent from theclient application.

Ensure that the bridge facility token in the datatransmitted by the application is correct.

Module:


DFHBRXM

ABRH

ExplanationThe bridge facility token specified is not known toCICS.


User responseThe most likely error is that the client applicationspecified too small a keep time for the bridge facility.Before the client reused the bridge facility token, CICShad already discarded it. Check the bridge facility keeptime in the outbound messages. CICS will use thekeep time value specified in the last message used bya transaction. Alternatively use the trace or CEDX tolook at the keep time in the BRXA passed back on theterminate call to the bridge exit.

Another possible error is that the client applicationpassed a request to a CICS system other than that onwhich the original request was sent. Bridge facilitiesare only valid on a single CICS system.

Module:DFHBRXM

ABRI

ExplanationThere are no free bridge facility tokens available. Thisis probably due to excessive keep time values beingspecified on the bridge exit termination call.


User responseReview the keep time values used by the clientapplications. If some client applications are returningexcessive values, modify the bridge exit to specify alimit to the values.

Module:DFHBRXM

ABRJ

ExplanationAn invalid FACILITYLIKE value was specified.

The FACILITYLIKE value can be specified on thebridge exit initialization call. If the default value(blanks) is returned, the value in the user transactionprofile definition is used. If no FACILITYLIKE value isspecified in the profile definition, a value of CBRF isused.

The name must be that of an installed VTAM 3270terminal.


User responseDefine the terminal specified by FACILITYLIKE, changethe value on the profile definition, change the valuesupplied by the client application, or install a terminaldefinition for CBRF

Module:DFHBRXM

ABRK

ExplanationThe user ID check failed following the call to run theLink3270 bridge request, because it does not matchthe user ID that created the bridge facility that is beingused to service the request.


User responseA Link3270 bridge facility must run under the controlof a single userid for the lifetime of its use. Ensure thatall of the programs that use Link3270 sessions runuder the same user ID.

Module:DFHBRXM

ABRN

ExplanationThe bridge exit returned a value in BRXA_RESP that isnot valid for the command for which it was invoked.


System actionThe transaction is backed out.

User responseChange the bridge exit to only return valid responsesettings.

Module:DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC

ABRP

ExplanationThe bridge client is no longer available.


User responseDetermine why the bridge client is no longer available.It might have been purged.

Module:DFHBRME

ABRQ

ExplanationThe bridge exit issued an abend.

System actionThe transaction is backed out.

User responseIdentify why the bridge exit abended.


ABRR

ExplanationThe user transaction's profile could not be found.

System actionThe task is abnormally terminated with a CICStransaction dump. The user transaction is not started.

User responseCheck that the profile name in the user transactiondefinition is correct, and that this profile has beendefined.

Module:DFHBRXM

ABRX

ExplanationThe bridge facility was invalid when a transactionstarted. This can occur when MAXTASK is reset to alow value on a busy system. The bridge facility cantime out and be deleted before the user transaction isstarted.

System actionThe user transaction will abend during initialisation.

User responseNone.

Module:DFHBRXM

ABRY

ExplanationCICS returned an unexpected error running the bridgeexit. This is a CICS internal error.




ABRZ

ExplanationThe bridge exit returned invalid data in the BRXA.




User responseIf a user supplied bridge exit was used, review theformat of the data returned by the exit.

If a CICS supplied exit was used, this is a CICS error.If you need further assistance from IBM to resolve thisproblem, see Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, DFHXMBR

ABSA

ExplanationA message passed to DFHBSMSG is too long. This is aCICS internal error.



Module:DFHTBS

ABSX

ExplanationCICS has detected that a BMS protected field has beenupdated by the client.


User responseThe message DFHTF0200 will give details of the clientand the field updated.

Refer to this message for further actions.

Module:DFHMCPE

ABX1

ExplanationThe bridge exit or formatter was called with an invalidBRXA-HEADER. This indicates a storage overwrite.

System actionAn exception trace is made of the data in error. Thetask is abnormally terminated with a CICS transactiondump.

As CICS also does a check of the BRXA on return fromthe call to the exit, there will probably be a subsequentABRZ abend.

User responseInvestigate the cause of the storage error, and retry.

Module:DFH0CBAE,DFH0CBRE,DFH0CBRF

ABX2

ExplanationThe bridge exit or formatter was called with an invalidBRXA-TRANSACTION-AREA. This indicates a storageoverwrite.





ABX3

ExplanationThe bridge exit or formatter was called with an invalidBRXA-COMMAND-AREA. This indicates a storageoverwrite.








ABX5

ExplanationThe bridge exit or formatter was called without a user-area. This probably indicates an error in the bridgeexit.




ABX6

ExplanationThe bridge exit or formatter was called with an invaliduser-area. This indicates a storage overwrite or anerror in the bridge exit.




ABX7

ExplanationA TC command passed to the formatter, exceeded themaximum message size.

System actionAn exception trace is made of the first 4K of data inerror. The task is abnormally terminated with a CICStransaction dump.

User responseCheck that the user transaction is passing the correctdata. If it is, it will be necessary to change the size ofthe buffer. This is in field block-length in the sampleexit. Recompile and reload the exit and retry.

Module:DFH0CBRF

ABX8

ExplanationA next BMS BRMQ vector in the input messagepassed to the formatter does not contain the mapsetrequested to answer a RECEIVE MAP request.


User responseThis may just indicate that the transaction hasgone down an error path which should result in atransaction backout. If not, the input message shouldhave a BRMQ vector for this mapset. Change the clientapplication, recompile and retry.

Module:DFH0CBRF

ABXA

ExplanationA next BRMQ vector in the input message passed tothe formatter is the wrong type of a RECEIVE vector.RECEIVE and RECEIVE MAP have separate vectors.


User responseThis may just indicate that the transaction hasgone down an error path which should result in atransaction backout. If not, the input message shouldhave a BRMQ vector for this command. Change theclient application, recompile and retry.

Module:DFH0CBRF

ABXB


ExplanationThe BRIH requested that outbound BMS vector mustinclude the ADS descriptor. The map did not contain anADS descriptor. This means that the mapset was notassembled with CICS TS 1.2 or later.


User responseEither reassemble the mapset using the current levelof BMS macros, or set BRIH-ADSDESCRIPTOR toBRIHADSD-NO (the default value is BRIHADSD-YES).Note that BRIHADSD-YES is required when codepageconversion of the Link3270 message is required (e.g.using ECI). If you need to reassemble the mapset anddon't have the mapset source, the utility DFHBMSUPcan be used to recreate it.

Module:DFHBRMF

ABXC

ExplanationAn error occurred when a SYNCPOINT request wasissued by the bridge exit.


User responseCheck for other CICS messages and exception traceentries to investigate the cause of the SYNCPOINTerror.

Module:DFH0CBRE

ABXD

ExplanationAn error occurred when a SYNCPOINT ROLLBACKrequest was issued by the bridge exit.


User responseCheck for other CICS messages and exception traceentries to investigate the cause of the SYNCPOINTROLLBACK error.

Module:DFH0CBRE

ABXE

ExplanationThe bridge exit was expecting data to be passed on theBRDATA parameter of the START command. No datawas found.


User responseCorrect the transaction which issued the START.Recompile, reload and retry.

Module:DFH0CBAE,DFH0CBRE

ABXF

ExplanationAn error was detected by the bridge exit when it triedto input the next message.

System actionAn exception trace is made of any error information.The task is abnormally terminated with a CICStransaction dump.

User responseCheck for other CICS messages and exception traceentries to investigate the cause of the input error.

Module:DFH0CBAE,DFH0CBRE,DFH0CBAI

ABXG

ExplanationAn error was detected by the bridge exit when it triedto output the next message.



User responseCheck for other CICS messages and exception traceentries to investigate the cause of the output error.


ABXH

ExplanationThe user transaction issued a request which requiresmore data (such as a RECEIVE request). Nodata was available in the message, and mqcih-conversationaltask was set to mqcct-no whichspecifies that the transaction is non conversational.


User responseThis may be correct behaviour as defined by the clientapplication. If it is not, the client application shouldeither supply additional data, or be redesigned toallow the transaction to be conversational.

Module:DFH0CBRF

ABXI

ExplanationA message received by the bridge exit, exceeded themaximum message size.

System actionAn exception trace is made of the first 4K of data inerror. The task is abnormally terminated with a CICStransaction dump.

User responseCheck that the client application is passing the correctdata. If it is, it will be necessary to change the size ofthe buffer. This is in field block-length in the sampleexit. Recompile and reload the exit and retry.


ABXJ

ExplanationThe bridge exit detected an error in the MQCIH headerpassed by the client application.

System actionAn exception trace is written containing the MQCIHheader. The task is abnormally terminated with a CICStransaction dump.

User responseThe client application has either not set the MQCIHheader, or is using a version of the header which isincompatible with the bridge exit. Correct the clientapplication. Recompile, reload and retry.


ABXK

ExplanationThe bridge exit detected an error in the data passed onthe BRDATA parameter of the START command.


User responseCorrect the transaction which issued the START.Recompile, reload and retry.


ABXM

ExplanationThe bridge exit or formatter was called with a functionor command which it doesn't support. This eitherindicates a storage overwrite, or that the bridge exitis not designed for this command.



User responseCheck the BRXA data in the trace to see if there hasbeen a storage overwrite, or whether the exit supportsthis command.


ABXN

ExplanationThe formatter detected that the input message wastruncated.

System actionAn exception trace is made of the first 4K of themessage. The task is abnormally terminated with aCICS transaction dump.

User responseCheck that the transport mechanism allows formessages of this length. If this is correct, it indicatesthat the client application is issuing an incorrectmessage. Trace the outbound message on the clientapplication. Recompile, reload and retry.

Module:DFH0CBRF

ABXO

ExplanationThe formatter detected an error in a BRMQ vectorpassed by the client application.

System actionThe field MQCIH-ERROROFFSET is set to indicate theposition of the error in the message An exception traceis made of the MQCIH and BRMQ vector. The task isabnormally terminated with a CICS transaction dump.

User responseCorrect the client application. Recompile, reload andretry.

Module:DFH0CBRF

ABXP

ExplanationThe formatter detected an error in a BRMQ vectorheader passed by the client application.

System actionThe field MQCIH-ERROROFFSET is set to indicate theposition of the error in the message An exception traceis made of the MQCIH and BRMQ vector. The task isabnormally terminated with a CICS transaction dump.


Module:DFH0CBRF

ABXQ

ExplanationThe formatter could not find an ADSD vector as part ofthe BRMQ-RM vector when MQCIH-ADSDESCRIPTORspecified MQCADSD-MSGFORMAT.

System actionAn exception trace is made of the request. The task isabnormally terminated with a CICS transaction dump.


Module:DFH0CBRF

ABXS

ExplanationAn error was detected by the bridge exit when it triedto open the queue for the input or output message.


User responseCheck for other CICS messages and exception traceentries to investigate the cause of the open error.

Module:DFH0CBRE

ABXU


ExplanationThe conversion between client code page and servercode page is not supported by CICS/390; for exampleconversion has been requested between Japanesecode page 932 and Latin-1 code page 500.

System actionThe transaction is abnormally terminated with atransaction dump.

User responseEnsure that the Client codepage, both default andoverrides are in the same group as the Servercodepage. for example client code page 852 fromLatin-2 group, is only supported to server code page870.

Module:

DFHBRMF

ABXV

ExplanationThe client code page which has been requested by theclient is not one which CICS can support.


User responseEnsure that the Client codepage is valid.

Module:DFHBRMF

ACxx abend codesACAA

ExplanationThis explanation applies to the two transaction abendcodes, ACAA and ACAD. CICS cannot find a match for afunction code in the language definition table becausethe parameterized resource definition contains anunrecognized resource type code. The abend codeissued depends on the DFHCAP operation that wasinvoked before the error occurred:

AbendDFHCAP operation

ACAA

ANALYZE

ACAD

DEFAULTS

The cause of the abend is either:

• The language definition table, DFHEITCU, in thelibrary is invalid for the release of CICS you arerunning, or

• A CICS logic error has occurred.

System action• In a CICS environment, the CEDA transaction is

abnormally terminated with a CICS transactiondump.

• In a batch environment, processing is abnormallyterminated with an operating system dump.

User responseEnsure that the DFHEITCU module is in the library andis valid for this release of CICS.

If a valid version of DFHEITCU is already in the library,a CICS logic error has occurred. See Working with IBMto solve your problem for guidance on how to proceed.

Module:DFHCAP

ACAD

ExplanationSee ACAA.

System action:

User response:

Module:DFHCAP

ACAI

ExplanationAn internal error has occurred when module DFHCAPwas invoked. There was an invalid function code for adomain call to DFHCAP.








Module:DFHCAP

ACAJ

ExplanationAn internal error has occurred when module DFHCAPwas invoked while processing an EXEC CICS CREATEcommand. The preallocated dynamic storage area wastoo small.

System actionThe transaction executing the EXEC CICS CREATEcommand is abnormally terminated with a CICStransaction dump.


Module:DFHCAP

ACAM

ExplanationAn internal error has occurred when moduleDFHECBAM was invoked while processing a CBAMtransaction.

System actionCBAM is abnormally terminated with a CICStransaction dump.


Module:DFHECBAM

ACC1

ExplanationAbend codes with 'ACC' as the first three charactersare issued by the C/370 compiler running under CICS.These are documented in the IBM C/370 GeneralInformation.

System action:

User response:

Module:

ACC2


System action:

User response:

Module:

ACC3


System action:

User response:

Module:

ACC4


System action:

User response:

Module:

ACC5






https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=GC09-1386










System action:

User response:

Module:

ACC6


System action:

User response:

Module:

ACC7


System action:

User response:

Module:

ACC8


System action:

User response:

Module:

ACC9


System action:

User response:

Module:

ACCA


System action:

User response:

Module:

ACCB


System action:

User response:

Module:

ACCC


System action:

User response:

Module:

ACCD


System action:

User response:

Module:

ACCE





















System action:

User response:

Module:

ACCF


System action:

User response:

Module:

ACCG


System action:

User response:

Module:

ACCH


System action:

User response:

Module:

ACCI


System action:

User response:

Module:

ACCJ


System action:

User response:

Module:

ACCK


System action:

User response:

Module:

ACCL


System action:

User response:

Module:

ACCM


System action:

User response:

Module:

ACCN





















System action:

User response:

Module:

ACCO


System action:

User response:

Module:

ACCP


System action:

User response:

Module:

ACCQ


System action:

User response:

Module:

ACCR


System action:

User response:

Module:

ACCS


System action:

User response:

Module:

ACCT


System action:

User response:

Module:

ACCU


System action:

User response:

Module:

ACCV


System action:

User response:

Module:

ACCW





















System action:

User response:

Module:

ACCY


System action:

User response:

Module:

ACCZ


System action:

User response:

Module:

ACCX


System action:

User response:

Module:

ACFA

ExplanationDuring the loading of a Coupling Facility Data Tableby the CFCL transaction, an abend was detected or adomain call returned a response (such as DISASTER)after which normal processing could not continue.

System actionA message is issued (one of DFHFC7100, DFHFC7101,DFHFC7103 or DFHFC7104). Loading of the data tableis terminated and CFCL abends.

User responseIf this abend is produced as a result of an abend duringloading, message DFHFC7103 is issued. If it is a resultof a domain call failure, depending on which domainthe failure was returned by, one of the messagesDFHFC7100, DFHFC7101 or DFHFC7104 is issued.Refer to the description of the message for furtherinformation and guidance.

Module:DFHFCDL

ACFB

ExplanationA transaction has issued a request to a coupling facilitydata table for which it holds an active lock, but afterthe lock was acquired, the coupling facility data tableserver for the pool in which this coupling facility datatable resides failed and was restarted. This requestis of a type which cannot continue against a newinstance of the server, because it is reliant on the lockwhich was acquired before the server failed.

System actionThe requesting transaction abends with a transactiondump.

CICS continues normally.

User responseRetry the failed transaction.

Module:DFHEIFC

ACFC

ExplanationA transaction has issued a request to a coupling facilitydata table which was last accessed using a previousinstance of the coupling facility data table server (thatis, the server for the pool in which this coupling facilitydata table resides has failed and been restarted one ormore times since the last access). We therefore needto reopen the access between this CICS file and thecoupling facility data table, but the attempt to reopenaccess has failed.










User responseRetry the failed transaction. If the error continuesto occur, issue an explicit close request for the file,followed by an explicit open request.

Module:DFHEIFC

ACFD

ExplanationDuring the loading of a Coupling Facility Data Table bythe CFCL transaction, a call to the CICS TransactionManager has returned a response (such as DISASTER)after which normal processing could not continue.

System actionMessage DFHFC7121 is issued. Loading of the datatable is terminated and CFCL abends.

User responseRefer to the description of the message for furtherinformation and guidance.

Module:DFHFCDL

ACFE

ExplanationAn attempt was made to attach a transactionspecifying DFHFCDL as the program to be givencontrol, but the transaction was not internally attachedby CICS.

DFHFCDL is for use by CICS system transaction CFCL.This loads a Coupling Facility Data Table.

System actionThe transaction is abnormally terminated. CICSprocessing continues.

User responseEstablish why an attempt was made to attach CFCLillegally, or why a transaction definition specifiedDFHFCDL as the program to be given control.

Module:DFHFCDL

ACHA

ExplanationThe remote server transaction, CEHS, is not ata compatible level to operate with the CICS/CMSsystem. This usually indicates that the service levelsof CICS/CMS and the remote server are different.

System actionCICS terminates the remote server transactionabnormally with a dump.


Problem determinationTo diagnose a problem with the remote server, itis generally helpful to obtain a trace of the remoteserver's activity up to the point of failure.

A remote server trace is obtained by invoking theremote server with the TRACE option, (type CEHSTRACE). The remote server operates as normal butcauses entries to be written to a trace log in temporarystorage. Note that main storage, not auxiliary, is usedfor this queue hence large amounts of memory can beused up if this trace is left on for long.

The trace is found in a queue whose name is'CEHSxxxx', where 'xxxx' is the four-character terminalidentifier. The queue can be browsed in text form orin hexadecimal form using CEBR. To find the terminalidentifier, invoke CEBR on the terminal that has runCEHS, without giving a queue name. The queue namewill default to 'CEBRxxxx', where 'xxxx' is the terminalidentifier.

Note: CEBR requires the queue name to be in UPPERCASE.

For a description of the remote server and its traceentries and abend codes, see the CICS/VS RemoteServer Diagnosis Manual (LC33-0438).

Module:DFHCHS

ACHB

ExplanationThe remote server has received a data frame fromCICS/CMS that is out of sequence. A frame may havebeen lost in transmission.



https://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

https://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

System actionCICS terminates the remote server abnormally with adump.

User responseReestablish the connection between CICS/CMS andthe remote CICS system and try to use the remoteserver again. For further information, see the 'ProblemDetermination' section for abend code ACHA.

If the problem persists, you will need assistance fromIBM to resolve the problem. See Working with IBM tosolve your problem for guidance on how to proceed.

Module:DFHCHS

ACHC

ExplanationThe remote server did not receive the expectedacknowledgement type data frame from CICS/CMS.




Module:DFHCHS

ACHD

ExplanationThe remote server did not receive the expectedresponse type data frame from CICS/CMS.


User responseReestablish the connection between CICS/CMS andthe remote CICS system and try to use the remote

server again. For further information, see the 'ProblemDetermination' section for abend code ACHA.


Module:DFHCHS

ACHE

ExplanationThe remote server received an unexpected data framefrom CICS/CMS. This indicates a logic error in theremote server.




Module:DFHCHS

ACHF

ExplanationThe remote server attempted to send one of a seriesof data frames to CICS/CMS when, at this time, only asingle frame is allowed. This indicates a logic error inthe remote server.















Module:DFHCHS

ACHG

ExplanationThe remote server attempted to send data to CICS/CMS. However, it was not set to the correct mode to doso. This indicates a logic error in the remote server.




Module:DFHCHS

ACHH

ExplanationA TIOA has not been created from the data received bythe remote server from CICS/CMS.




Module:DFHCHS

ACHI

ExplanationThe remote server has received an unexpected returncode from the Transformer 2 program.


User responseFor further information, see the 'ProblemDetermination' section for abend code ACHA.

Module:DFHCHS

ACHJ

ExplanationAn error has occurred processing a request fromCICS/CMS which had the 'No-Reply' option. Theremote server cannot, therefore, return the errorcondition to CICS/CMS.


User responseReestablish the remote server and diagnose theproblem by executing the same command from CECIunder CICS/CMS without the NOCHECK option. Forfurther information, see the 'Problem Determination'section for abend code ACHA.

Module:DFHCHS

ACHK

ExplanationThe transformer program has requested neither EIPnor DLI to execute the request received from CICS/CMS. This indicates a logic error because the requesthas to be destined for either EIP or DLI.








Module:DFHCHS

ACHL

ExplanationCICS/CMS has supplied a buffer to the remote serverwhich is not large enough to hold the reply that theremote server has to return.




Module:DFHCHS

ACHM

ExplanationThe remote server has tried to receive a response fromCICS/CMS which failed repeatedly until the retry limitwas exceeded.




Module:DFHCHS

ACHN

ExplanationThe remote server has tried to receive a request fromCICS/CMS which failed repeatedly until the retry limitwas exceeded.




Module:DFHCHS

ACHO

ExplanationThe remote server has tried to receive a reply fromCICS/CMS which failed repeatedly until the retry limitwas exceeded.




Module:DFHCHS

ACHP

ExplanationCICS/CMS has made a request to the remote server forwhich the reply would need more than the maximum










storage allowed (32660 bytes). This indicates that alogic error has occurred.



Module:DFHCHS

ACHR

ExplanationThe CICS/CMS remote server transaction (CEHS) hasbeen initiated and either the task is not terminal-oriented, or the associated terminal is a console.

System actionCICS abnormally terminates the remote server with adump.

User responseEnsure the transaction is initiated with an associatedterminal and that the terminal is not defined as aconsole. For further information, see the 'ProblemDetermination' section for abend code ACHA.

Module:DFHCHS

ACHS

ExplanationThe CICS/OS2 remote server transaction (CEHP) hasbeen initiated and either the task is not terminal-oriented, or the associated terminal is a console.

System actionCICS abnormally terminates the remote server with adump.

User responseEnsure the transaction is initiated with an associatedterminal and that the terminal is not defined as aconsole. For further information, see the 'ProblemDetermination' section for abend code ACHA.

Module:

DFHCHS

ACL0

ExplanationThe new operator failed to allocate storage whilstcreating an object. This problem will occur if thereis insufficient storage available to the CICS region tosatisfy the request.

System actionCICS abnormally terminates the transaction.

User responseThis abend may occur if you are in a loop creatingobjects and not deleting them. Alternatively CICSmight be short on storage and you should tryresubmitting the transaction.

Module:ICCGLBIC

ACL1

ExplanationThe CICS Foundation Classes have thrown anexception which the application programmer failed tocatch.


User responseCheck that you have coded your application to catchexceptions. Interrogate the message object containedwithin the exception object to establish the cause ofthe exception being thrown.

Another possible cause of this abend is that you arerunning a Foundation Classes program on a machinethat does not have the C++ runtime installed. Checkthat your machine has the C++ runtime installed.

Module:ICCGLBIC

ACL2

ExplanationThe CICS Foundation Classes invoked the defaulthandleEvent method (defined in class IccResource)in order to handle a CICS condition because theapplication programmer did not implement his ownhandleEvent method.



User responseImplement your own handleEvent method orcustomize your resource objects so they do not callthe handleEvent method for any of the possible CICSconditions.

Module:ICCRESEC

ACL3

ExplanationThe CICS Foundation Classes responded to anapplication programmer's request to abend a CICStask.


User responseThe application programmer requested that the CICSFoundation Classes abend the transaction using theappropriate return enumeration from the handleEventmethod (see IccResource class).

Module:ICCRESIC

ACL4

ExplanationThe CICS Foundation Classes detected an internalerror.


User responseThis abend indicates a CICS Foundation Classesinternal problem. Please contact your supportorganization.

Module:ICCGLIBC

ACL5

ExplanationThe CICS Foundation Classes received an error froma CICS storage request (GETMAIN). In response toa new operator request the CICS Foundation Classesissued a CICS GETMAIN request to allocate storagewhich CICS was unable to satisfy.


User responseThis abend may occur if you are in a loop creatingobjects and not deleting them. Alternatively CICSmight be short on storage and you should tryresubmitting the transaction.

Module:ICCBASEC

ACL6

ExplanationThe CICS Foundation Classes detected an error whileprocessing a storage release request.


User responseThis abend can occur if you try to delete an object thatdoes not exist (that is, it has already been deleted).It may also indicate a CICS memory managementproblem, or a storage corruption problem. If the errorpersists, please contact your support organization.

Module:ICCBASEC

ACL7



User responseCheck that you have coded your application to catchexceptions. Interrogate the message object contained


within the exception object to establish the cause ofthe exception being thrown.


Module:ICCGLBIC

ACL8



User responseCheck that you have coded your application to catchexceptions. Interrogate the message object containedwithin the exception object to establish the cause ofthe exception being thrown.


Module:ICCGLBIC

ACL9

ExplanationThe CICS Foundation Classes responded to anapplication programmer's request to abend a CICStask.


User responseA resource object was customized to cause atransaction abend if a particular CICS condition wasraised, and this condition was subsequently raised byCICS.

Module:ICCRESIC

ACLA




Module:ICCGLIBC

ACLB




Module:ICCGLIBC

ACLC




Module:ICCGLIBC

ACLD





Module:ICCGLIBC

ACLE




Module:ICCGLIBC

ACLF




Module:ICCGLIBC

ACLG




Module:ICCGLIBC

ACLH

ExplanationThe CICS Foundation Classes detected an error whileprocessing a storage release request.


User responseThis abend can occur if you try to delete an object thatdoes not exist (that is, it has already been deleted).It may also indicate a CICS memory managementproblem, or a storage corruption problem. If the errorpersists, please contact your support organization.

Module:ICCBASEC

ACN1

ExplanationThe table DFHCNV cannot be loaded. This is probablybecause a table has not been pregenerated. It couldalso occur if the table DFHCNV has been linked above16MB but DFHCCNV has been linked below 16MB.


User responseCheck that the DFHCNV module is in the library andis valid for this release of CICS. Check the linkageof DFHCNV and relink it with the correct AMODE ifnecessary.


Module:DFHCCNV

ACN2

ExplanationThe table DFHCNV has been loaded but the first recordis in the wrong format. This is probably due to anerror during assembly or linkedit, but could also be theresult of a storage overwrite.


User responseThe table should be reassembled and linked. Checkthe assemble and linkedit output. Check for anymessages issued from CICS indicating that storageoverwrites have occurred.

Module:DFHCCNV

ACN3

ExplanationThe program DFHUCNV cannot be linked. A userconversion program must be available (even if it onlyreturns).


User responseCheck that the DFHUCNV module is in the library andis valid for this release of CICS. Check the linkageof DFHUCNV and relink it with the correct AMODE ifnecessary.

Module:DFHCCNV

ACN4

ExplanationAn unrecognized format of a DFHCNV table has beenencountered.


User responseRe-assemble and re-link edit the DFHCNV macro.

Module:DFHCCNV

ACN5

ExplanationAn override for the default client code page has beenreceived; however the value is not recognized.


User responseCheck that the client system is using one of the clientcode pages supported by CICS/390.

Module:DFHCCNV

ACN6

ExplanationThe client sent data in unicode but the client andserver code pages are not the same. Unicode data isonly tolerated provided that conversion is not required.


User responseEnsure that the Client codepage and the Servercodepage are the same.

Module:DFHCCNV

ACN7

ExplanationAn override for the default binary format has beenreceived; however the value is not recognized.



User responseData formats should be either S/370 or INTEL,anything else is unsupported by CICS/390.

Module:DFHCCNV

ACN8

ExplanationCICS data conversion is processing a FIELDdefined as containing GRAPHIC characters(which are only DBCS): that is DFHCNVTYPE=FIELD,DATATYP=GRAPHIC,... However theclient code page (defined in the CLINTCPoperand), and the server code page (definedin the SRVERCP operand) imply that the FIELDcontains only SBCS characters, for example DFHCNVTYPE=ENTRY,CLINTCP=437,SRVERCP=037


User responseCorrect the FIELD definition.

Module:DFHCCNV

ACN9

ExplanationThe table DFHCNV cannot be loaded. This abend codeis issued following a NOTAUTH condition being raisedduring loading of the DFHCNV table.


User responseEnsure the resource security definitions are correct.

Module:DFHCCNV

ACNA

ExplanationThe table DFHCNV cannot be loaded. This is a generalpurpose abend code indicating that the LOAD requestfor the conversion table, DFHCNV, has failed.


User responseExamine the transaction dump to determine the exactcondition returned from LOAD request.

Module:DFHCCNV

ACNB

ExplanationThe program DFHUCNV cannot be linked This is ageneral purpose abend code indicating that the LINKrequest for the conversion program DFHUCNV, hasfailed.


User responseExamine the transaction dump to determine the exactcondition returned from LINK request.

Module:DFHCCNV

ACNC

ExplanationThe client code page which has been requested by theclient is not one which CICS can support.


User responseEnsure that the Client codepage is valid.

Module:DFHCCNV

ACND


ExplanationThe conversion between client code page and servercode page is not supported by CICS/390; for exampleconversion has been requested between Japanesecode page 932 and Latin-1 code page 500.


User responseEnsure that the Client codepage, both default andoverrides are in the same group as the Servercodepage. for example client code page 852 fromLatin-2 group, is only supported to server code page870.

Module:DFHCCNV

ACNE

ExplanationThe conversion between client code page and servercode page is not supported by CICS/390. Although thecode pages are in the same group, CICS does not havea conversion table to match the requested server codepage for the client code page specified.


User responseEnsure that the Client codepage and the servercodepage are correct. If they are as intended, thenCICS can not support the requested conversion.

Module:DFHCCNV

ACP1

ExplanationDFHIC TYPE=GET response code is other than thenormal response during print key processing.

System actionThe transaction is abnormally terminated with a CICStransaction dump. The keyboard of the terminal onwhich the print key was depressed remains locked toindicate the failure of the operation.

User responseAnalyze the dump. The response code is in the loworder byte of register 0.

Module:DFHCPY

ACP2

ExplanationDFHIC TYPE=INITIATE response code is other thanthe normal response during print key processing.


User responseAnalyze the dump. The response code is in low-orderbyte of register 0.

Module:DFHCPY

ACQA

ExplanationThe Connection Quiesce Protocol transaction has beeninitiated by user action, such as a START command orby typing the transaction identifier at a terminal. Thetransaction is not intended to be initiated in this way.

System action1. If the transaction was not initiated by terminal

input, message DFHZC4951 is written todestination CSNE.

2. An exception trace record is written to all activetrace destinations.

3. The transaction is abnormally terminated with aCICS transaction dump.

User responseDetermine what caused the transaction to be initiated.The exception trace record contains information whichwill help you.

Module:DFHCLS5

ACQB


ExplanationThe Connection Quiesce Protocol transaction hasencountered an error when communicating withanother system on an APPC session.

System action1. Message DFHZC4951 is written to destination

CSNE.2. An exception trace record is written to all active

trace destinations.3. The transaction is abnormally terminated with a

CICS transaction dump.

User responseDetermine what caused the failure. A likely cause is afailure of the session with the partner system.

Module:DFHCLS5

ACQC

ExplanationThe Connection Quiesce Protocol transaction hasencountered an unexpected error.

System action1. Message DFHZC4951 is written to destination

CSNE.2. An exception trace record is written to all active

trace destinations.3. The transaction is abnormally terminated with a

CICS transaction dump.


Module:DFHCLS5

ACRA

ExplanationThe relay program has been invoked without aterminal as its principal facility.


User responseEnsure that DFHAPRT has not been specified as theinitial program of a task that is not terminal-related.

Module:DFHAPRT

ACRB

ExplanationThe relay program has been invoked by a transactionthat is not defined as remote.


User responseCheck that the relay program is defined correctly.Determine why DFHAPRT was invoked if thetransaction is not a remote transaction.

Module:DFHAPRT

ACRC

ExplanationThe relay program received an invalid response fromDFHZCX or DFHAPRR.



Module:DFHAPRT

ACRD

ExplanationThe system entry for the system to which routing isto be performed could not be found or, for CICS TS4.1 and earlier releases, an attempt has been made tosend a transaction that is defined as routable=yes overan IPIC connection.





User responseCheck the installed transaction definition to confirmthat the system was correctly specified. Check that thesystem entry is defined to CICS with a CONNECTIONor IPCONN resource definition.

Module:DFHAPRT

ACRE

ExplanationA transaction invoked from an APPC terminal andspecified in the installed transaction definition asremote has abnormally terminated because the link isout of service.

System actionThe task is abnormally terminated.

User responseWait until the link is available. The CICS suppliedtransaction CEMT INQUIRE CONNECTION can be usedto check the states of the links.

Module:DFHAPRT

ACRF

ExplanationThe relay program received a nonzero return codefrom the dynamic router following its first invocation.


User responseUse the dump to determine why the dynamic routingprogram has failed by checking the contents ofthe passed COMMAREA DFHDYE for correctness.The COMMAREA address can be found from fieldTCACOMM in the system TCA for the task. TheCOMMAREA fields are mapped via the DFHDYPDSDSECT.

Module:DFHAPRT

ACRG

ExplanationAn ATI initiated remote transaction defined withDYNAMIC(YES) has failed because there is nomatching entry in the AID chain.

Each AID in the chain has been checked and none hasbeen found where

• The AID terminal ID matches that of the TCTTE• The installed transaction definition and the AID

transaction IDs match• The AID is for a remote transaction• The AID has not been canceled.

System actionThe task is abnormally terminated with a CICS systemdump.

User responseThe dump can be used to help ascertain the mismatch.Check the transactions listed in the TCTTE and PCTfields of the system dump against the AID chain.

Module:DFHAPRT

ACRH

ExplanationThe profile for the session that will carry intersystemflows during transaction routing could not be found.


User responseCheck the installed transaction definition to confirmthat TRPROF is correctly specified.

Module:DFHAPRT

ACRI

ExplanationAn error occurred when attempting to link to thedynamic routing program.



A message in the range DFHRT4417 to DFHRT4420 iswritten to the CSMT log.

User responseRefer to the message sent to the CSMT log. Itidentifies the cause of the link failure and providesfurther user guidance.

Module:DFHAPRP, DFHAPRT, DFHEIIC, DFHEPC, DFHICXM

ACRJ

ExplanationAn abend has occurred in the dynamic routing programafter a link has been executed from DFHAPRT orDFHEPC.

System actionThe transaction is abnormally terminated with a CICStransaction dump. Message DFHRT4416 is written tothe CSMT log.

User responseRefer to message DFHRT4416. It identifies the abendin the dynamic routing program and provides furtheruser guidance.

Module:DFHAPRP, DFHAPRT, DFHEIIC, DFHEPC, DFHICXM

ACRK

ExplanationThe relay program has been invoked with no addressfor the principal facility.



Module:DFHAPRT

ACRL

ExplanationThe task does not own the facility.



Module:DFHAPRT

ACRM

ExplanationIn response to a request from the dynamic routingprogram, DFHAPRT has attempted an INITIAL_LINKto a program that is not the initial program of thetransaction for which the dynamic router has beeninvoked. The attempt has failed.


User responseExamine the following possibilities:

• The autoinstall user-replaceable module (URM) wascalled but is unable to do the autoinstall.

• The autoinstall URM was called but data supplied bythe autoinstall URM is invalid.

• The autoinstall URM was called, but there is nodefinition for the autoinstall model.

• There is a problem with the autoinstall URM.• There is no resource definition for the program and

either the autoinstall is not active or the autoinstallURM indicated that the program should not beautoinstalled.

• The program is disabled.• The program cannot be loaded.• The program is defined as remote.

Module:DFHAPRT

ACRN




ExplanationThe dynamic routing program has indicated that thetransaction should not be routed, but execute in thelocal system. Prior to invoking the application program,a security check is performed. This check has failed.


User responseEnsure that the transaction security definition iscorrect.

Module:DFHAPRT

ACRO

ExplanationAn attempt has been made to invoke the CRSQtransaction from a terminal. CRSQ is an internal CICStransaction and cannot be invoked in this way.


User responseNone. You can use CEMT and EXEC CICS commands tocancel AIDs.

Module:DFHCRQ

ACRP

ExplanationThe dynamic router has supplied a sysid whosesupported functions are unknown. This may be dueto either a backlevel release, or APPC is used forcommunication and no work has flowed across thisconnection.


User responseGive an alternative sysid, or revert to the oldstyle START, or flow some routed work across theconnection.

Module:DFHAPRT

ACRQ

ExplanationAn attempt has been made to route unsupportedfunction across an IPIC connection. If messageDFHIS1035 is issued immediately before the ACRQabend, the ACRQ abend is caused by an attempt toroute to a backlevel release. If message DFHIS1035 isnot issued, the ACRQ abend is caused by an attempt toroute an APPC device.


User responseProvide an alternative SYSID, or make an MRO or ISCconnection available.

Module:DFHAPRT

ACSA

ExplanationThe remote scheduler task (CRSR) does not own anintersystem link TCTTE as its principal facility.


User responseEnsure that DFHCRS is not specified as the initialprogram of a task other than CRSR. Check that theterminal operator did not enter CRSR.

Module:DFHCRS

ACSB

ExplanationAn unexpected reply was received from a remotesystem in response to a request to schedule a taskon that system.




Module:DFHCRS

ACSC

ExplanationAn unexpected request was received from a remotesystem when expecting a request to schedule a task.



Module:DFHCRS

ACSD

ExplanationAn internal logic error has been detected.



Module:DFHCRS

ACSE

ExplanationModule DFHCRS has been attached in an unsupportedmanner.

System actionCICS abnormally terminates the transaction with atransaction dump.

User responseModule DFHCRS should be executed only bytransaction CRSR, which executes with an MROsession, an LU6.1 session or an LU type 6.2conversation as its principal facility. Ensure that thetransaction is being attached by a CRSR transaction inthe connected system, and not by a user transaction.

If the transaction is being attached by a CRSRtransaction, you will need assistance from IBM toresolve the problem. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHCRS

ACSF

ExplanationThe task was purged before a GETMAIN request to thestorage manager (SM) domain was able to completesuccessfully. The task that first detects the purgedcondition provides an exception trace.



Module:DFHCRS

ACSG

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe storage manager (SM) domain. The domain thatdetected the original error will have provided anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).








User responsePlease see the related error message produced by thedomain that detected the original error.

Module:DFHCRS

ACSH

ExplanationThe processing of APPC mapped data requires thegeneration of an LU6.2 attach FMH with default values.In particular, the sync level requested is defaulted to2. However, the session that is to be used has beenbound with a sync level of 1.


User responseCheck that:

• The CONNECTION resource for the remote systemhas not been defined as single-session.

• The remote system can support a sync level of 2• The correct sync level has been requested.

Module:DFHCRS

ACSI

ExplanationAn APPC conversation failure occurred when an attachbetween CICS systems was issued.


User responseCheck the connection to the remote CICS system andtry to reestablish it.

Module:DFHCRS

ACSJ

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to the

recovery manager (RM) domain. The domain providesan exit trace, and possibly a console message and asystem dump (depending on the options specified inthe dump table). This failure is either the result of atask purge, or a CICS logic error.


User responseSee the related diagnostic material produced by therecovery manager domain and determine the reasonfor the failure.

In the case of a CICS logic error, you need furtherassistance from IBM. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHCRS

ACSK

ExplanationThe transaction wait was purged while waiting for aVTAM INQUIRE macro to complete.

CICS issued a VTAM INQUIRE OPTCD=NQN orINQUIRE OPTCD=SESSNAME request then waited forVTAM to post the ECB, but the wait was terminatedeither as a result of an explicit FORCEPURGE request,or due to a 3 minute time out.

System actionA transaction dump is taken together with CICS issuingmessage DFHZC0001.

User responseInvestigate the reason why the wait was terminated.

In the case of a time out, you may need furtherassistance from IBM. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHZGIN

ACSL

ExplanationCICS has been unable to attach a transaction toperform a mass flag (CFTS) or mass remote delete(CDTS) request.








Module:DFHCRS

ACSM

ExplanationTransaction CFTS has abended. The mass flagging ofterminals for deletion has failed.



Module:DFHCRS

ACSN

ExplanationTransaction CFTS has stalled. The mass flagging ofterminals for deletion has exceeded the expected timeand is therefore assumed to have failed.

System actionThe task is abnormally terminated with a CICStransaction dump. A flag is set in the remotework element (RWE) to indicate that the mainlinetransaction has assumed that CFTS has failed.


Module:DFHCRS

ACSO

ExplanationAn IPIC conversation failure occurred when an attachbetween CICS systems was issued.


User responseCheck the connection to the remote CICS system andtry to reestablish it. Use the transaction dump todetermine why the conversation failed. This may bethe result of a security error that occurred when invalidcredentials were sent, or if they were missing from theIPIC message when the connection was configured toexpect them.

Module:DFHCRS

ACTA

ExplanationThe relay program running in the terminal-owningregion has received an unexpected request from theapplication owning region. The request received is inviolation of CICS transaction routing protocols.

The request will be in the DFHLUCDS DSECT inDFHZTSP's LIFO - field LUCOPN0



Module:DFHZTSP

ACTB

ExplanationThe relay program running in the terminal-owningregion issued a terminal control WRITE,LAST requestto the application-owning system, and received anonzero return code from terminal control.

This is the usual return code from terminal control inTCATPAPR.







User responseUse the transaction dump to determine why terminalcontrol was unable to process the request.

Module:DFHZTSP

ACTC

ExplanationThe relay program running in the terminal-owningregion issued a terminal control request to freeits session to the application-owning system, andreceived a nonzero return code from terminal control.




Module:DFHZTSP

ACTD

ExplanationThe relay program running in the terminal-owningregion issued a terminal control WRITE,WAIT,READrequest to the application-owning system, andreceived a nonzero return code from terminal control.




Module:DFHZTSP

ACTE

ExplanationThe relay program running in the terminal-owningregion attempted to free its session with the APPCterminal, and received a nonzero return code fromterminal control.

The return code will be in the DFHLUCDS DSECT inDFHZTSP's LIFO field, LUCRCODE.


User responseUse the transaction dump to determine why terminalcontrol was unable to process the request. Theterminal session may have failed.

Module:DFHZTSP

ACTF

ExplanationThe relay program running in the terminal-owningregion issued a terminal control request to freeits session to the application-owning system, andreceived a nonzero return code from terminal control.

This return code can be found in the TCA field,TCATPAPR.


User responseUse the transaction dump to determine why terminalcontrol was unable to process the request. Thetransaction on the application-owning region may haveabnormally terminated or the session may have failed.

Module:DFHZTSP

ACTG

ExplanationThe relay program running in the terminal-owningregion issued a request to attach a transaction in theapplication-owning region, but the response receivedfrom that region was invalid.


The return code in the TCA (field TCATPAPR) willbe nonzero, and either there will be no TIOA (fieldTCTTEDA in the TCTTE is zero) or there will be noFMH7 at the start of the TIOA.


User responseUse the transaction dump to determine why terminalcontrol was unable to process the request. Thetransaction on the application-owning region may haveabnormally terminated or the session may have failed.

Module:DFHZTSP

ACTH

ExplanationA privileged allocate was issued against a remote LU6.2 system.



Module:DFHZISP

ACTI

ExplanationThe relay transaction has an ISC or MRO session as itsprincipal facility. However the TCTTE for that session isnot owned by the task.



Module:DFHCRT

ACTJ

ExplanationThe principal facility of the relay transaction is not aTCTTE.


User responseTask CXRT should only be started in a terminal-owning region by an ALLOCATE request issued inan application-owning region against a remote APPCdevice. The principal facility of the task should bean ISC or MRO link. Check that your CICS system isdefined in such a way that this will always be the case.Also ensure that program DFHCRT is started only bytask CXRT.

Module:DFHCRT

ACTK

ExplanationThe task was purged before a GETMAIN request to thestorage manager (SM) domain was able to completesuccessfully. The task that first detected the purgedcondition will have provided an exception trace.


User responseInvestigate the reason why the task was purged. It waseither purged by the main terminal operator or as aresult of a deadlock timeout.

Module:DFHZISP

ACTL

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe storage manager (SM) domain. The domain thatdetected the original error will have provided an




exception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).



Module:DFHZISP

ACU0

ExplanationThe transaction routing program in the application-owning region issued a terminal controlWRITE,LAST,WAIT request to the terminal-owningregion, and received a nonzero return code fromterminal control.

The return code is located both in TCATPAPR and inthe trace entry on return from DFHZARQ.

System actionThe task is abnormally terminated with a transactiondump and an exception trace entry.

User responseUse the transaction dump to determine why terminalcontrol was unable to process the request. This abendcode may result when:

• The relay program in the terminal-owning regionterminates abnormally. In this case, determine thereason why the relay program has abnormallyterminated.

• The session has failed.

Module:DFHZXRL

ACU1

ExplanationRefer to the description of abend ACUO.

System action:

User response:

Module:DFHZXRL

ACU2

ExplanationThe transaction routing program in the application-owning region received a response from the terminal-owning region which violates CICS transaction routingprotocols.

The trace from the terminal-owning region will showits response to the application-owning region.



Module:DFHZXRL

ACU3

ExplanationThe transaction routing program in the application-owning region attempted to set the conversation statemachine to a state which violates CICS transactionrouting protocols.

The register containing the state can be determinedfrom the assembler listing.



Module:DFHZXRL

ACU4

ExplanationThe transaction routing program in the application-owning region issued a SET request to theconversation state machine and received a nonzeroreturn code. This violates CICS transaction routingprotocols.




The trace entry on return from DFHZUSR will show therequest type and current state.



Module:DFHZXRL

ACU5

ExplanationAn program running in an application-owning regionhas issued an ALLOCATE against an APPC deviceattached to a terminal owning region, but theconnection between the two systems is not installed.


User responseInstall the connection between the two regions.

Module:DFHZXRL

ACU6

ExplanationA request to DFHRTSU to prepare the surrogateTCTTE for syncpoint gave an unexpected responseand reason code. The response and reason code areincluded in DFHRTSU's parameter list which is printedin the exception trace.



Module:

DFHZXRL

ACU7

ExplanationA request to allocate a session between theapplication-owning region and the terminal-owningregion was issued, but the connection with the remotesystem is not an APPC or MRO connection.


User responseRedefine the connection as APPC or MRO, or avoidusing transaction routing on this connection.

Module:DFHZXRL

ACU8

ExplanationA request to DFHRTSU to get the recovery statusof a surrogate TCTTE gave an unexpected responseand reason code. The response and reason code areincluded in DFHRTSU's parameter list which is printedin the exception trace.



Module:DFHZXRL

ACU9

ExplanationA request to recovery manager to set the recoverystatus of a link gave an unexpected response andreason code. The response and reason code areincluded in DFHRMLN's parameter list which is printedin the exception trace.







Module:DFHZXRL

ACUA

ExplanationDFHZXRL was called with a request which is notsupported for transaction routing.

The request is located in the DFHLUC parameter listwhich is printed in the exception trace. DFHZXRL iscalled from DFHZARL, which will put details of therequest in its trace entry.



Module:DFHZXRL

ACUB

ExplanationThe parameter list passed to DFHZXRL for anALLOCATE request does not contain the TCTSEaddress of a remote APPC terminal.

The TCTSE address is located in the DFHLUCparameter list which is printed in the exception trace.DFHZXRL is called from DFHZARL, which will putdetails of the request in its trace entry.



Module:DFHZXRL

ACUC

ExplanationThe TCTSE address passed to DFHZXRL is not that of aremote LU 6.2 terminal.

The TCTSE address is located in the DFHLUCparameter list which is printed in the exception trace.DFHZXRL is called from DFHZARL, which will putdetails of the request in its trace entry.



Module:DFHZXRL

ACUD

ExplanationThe profile DFHCICSR could not be located as aninstalled profile definition.


User responseCheck that the IBM-supplied profile DFHCICSR iscorrectly defined and installed to CICS.

Module:DFHZXRL

ACUE

ExplanationA request to DFHZTSP to build a surrogate TCTTE wasnot satisfied.








Module:DFHZXRL

ACUF

ExplanationA session between the application-owning region andthe terminal-owning region was not allocated becausethe request was incorrectly specified.



Module:DFHZXRL

ACUG

ExplanationA request to allocate a session between theapplication-owning region and the terminal-owningregion failed. The return code from the ALLOCATErequest indicated that the profile could not be locatedas an installed transaction definition, although anearlier attempt to locate it was successful.




Module:DFHZXRL

ACUH

ExplanationA request to allocate a session between theapplication-owning region and the terminal-owningregion failed. The return code from the ALLOCATErequest indicated that the requested session is alreadyowned by the TCA.




Module:DFHZXRL

ACUI

ExplanationAn ISC session between the application-owning regionand the terminal-owning region was not allocatedbecause the MODENAME named in the profile couldnot be found. The profile DFHCICSR as supplied byIBM does not specify a MODENAME. Therefore, thiserror will occur when a MODENAME has been addedto the IBM-supplied profile, but that MODENAME is notdefined in the SESSIONS definition for the terminal-owning region.


User responseEnsure that the MODENAME specified in profileDFHCICSR was also specified when defining theSESSIONS to the terminal-owning region.

Module:DFHZXRL

ACUJ






ExplanationA session between the application-owning region andthe terminal-owning region was not allocated becausethe maximum session count for the mode groupspecified in profile DFHCICSR is zero.


User responseUse the CEMT transaction to set sessions in therequired mode group available for use.

Module:DFHZXRL

ACUK

ExplanationNo TCT entry was found for the terminal-owning regionspecified in the TCTSE for the remote terminal.


User responseEnsure that the terminal-owning region defined in theremote system entry is also defined to CICS.

Module:DFHZXRL

ACUL

ExplanationThe transaction routing program in the application-owning region issued a terminal controlWRITE,WAIT,READ request to the terminal-owningregion, and received a nonzero return code fromterminal control.






Module:DFHZXRL

ACUM

ExplanationA request to DFHZTSP to free a surrogate TCTTE wasnot satisfied.



Module:DFHZXRL

ACUO

ExplanationA terminal control READ request has failed. Thetransaction routing program in the application-owningregion attempted to receive data from the terminal-owning region, and received a nonzero return codefrom terminal control.








Module:DFHZXRL

ACUP

ExplanationThe transaction routing program in the application-owning region did not receive a rollback from theterminal-owning region. This violates CICS transactionrouting protocols.




Module:DFHZXRL

ACUQ


System action:

User response:

Module:DFHZXRL

ACUR

ExplanationRefer to the description of abend ACUP.

System action:

User response:

Module:DFHZXRL

ACUS


System action:

User response:

Module:DFHZXRL

ACUT

ExplanationThe transaction routing program in the application-owning region did not receive either a syncpoint or arollback from the terminal-owning region. This violatesCICS transaction routing protocols.




Module:DFHZXRL

ACUV

ExplanationThe transaction routing program in the application-owning region issued a terminal control ISSUE ABENDrequest on an MRO link to the terminal-owning region,and received a nonzero return code from terminalcontrol.

The return code is located both in TCATPAPR and inthe trace entry on return from DFHZIS1.



• The relay program in the terminal-owning regionterminates abnormally. In this case, determine the




reason why the relay program has abnormallyterminated.


Module:DFHZXRL

ACUW

ExplanationThe transaction routing program in the application-owning region issued a terminal control ISSUE ERRORrequest on an MRO link to the terminal-owning region,and received a nonzero return code from terminalcontrol.






Module:DFHZXRL

ACUX

ExplanationRefer to the description of abend ACUL.

System action:

User response:

Module:DFHZXRL

ACUY

ExplanationThe transaction routing program in the application-owning region issued a terminal control WRITE,WAITrequest to the terminal-owning region, and received anonzero return code from terminal control.






Module:DFHZXRL

ACUZ

ExplanationRefer to the description of abend ACUL.

System action:

User response:

Module:DFHZXRL

ACVA

ExplanationThe transaction routing program in the terminal-owning region issued a terminal controlWRITE,WAIT,READ request to the application-owningregion, and received a nonzero return code fromterminal control.





• The program in the application-owning regionterminates abnormally. In this case, determine thereason why the program has abnormally terminated.


Module:DFHZXRT

ACVB

ExplanationThe transaction routing program in the terminal-owning region attempted to issue an ISSUE SIGNALrequest on an MRO link to the application-owningregion. This violates CICS transaction routingprotocols.



Module:DFHZXRT

ACVC

ExplanationThe transaction routing program in the terminal-owning region issued an ISSUE SIGNAL request onan LU 6.2 link to the application-owning region, andreceived a nonzero return code from terminal control.

The return code is located in the DFHLUC parameterlist which is printed in the exception trace.





Module:

DFHZXRT

ACVD

ExplanationThe transaction routing program in the terminal-owning region issued a READ,WAIT request to theapplication-owning region, and received a nonzeroreturn code from terminal control.






Module:DFHZXRT

ACVE

ExplanationThe transaction routing program in the terminal-owning region issued a WRITE request to theapplication-owning region, and received a nonzeroreturn code from terminal control.




• the program in the application-owning regionterminates abnormally. In this case, determine thereason why the program has abnormally terminated.

• the session has failed.



Module:DFHZXRT

ACVF

ExplanationThe transaction routing program in the terminal-owning region issued a WRITE,LAST,WAIT request tothe application-owning region, and received a nonzeroreturn code from terminal control.






Module:DFHZXRT

ACVG

ExplanationThe transaction routing program in the terminal-owning region issued a FREE request to free thesession with the LU 6.2 terminal, and received anonzero return code from terminal control.




Module:DFHZXRT

ACVH

ExplanationThe transaction routing program in the terminal-owning region issued a FREE request to free thesession with the application-owning region, andreceived a nonzero return code from terminal control.






Module:DFHZXRT

ACVK

ExplanationThe transaction routing program in the terminal-owning region issued an ISSUE ABEND request on anLU 6.2 link, and received a nonzero return code fromterminal control.




• The program in the connected region terminatesabnormally. In this case, determine the reason whythe program has abnormally terminated.


Module:DFHZXRT

ACVL


ExplanationThe transaction routing program in the terminal-owning region issued an ISSUE ABEND request onan MRO link to the application-owning region, andreceived a nonzero return code from terminal control.






Module:DFHZXRT

ACVM

ExplanationThe transaction routing program in the terminal-owning region issued an ISSUE ERROR request on anLU 6.2 link, and received a nonzero return code fromterminal control.






Module:DFHZXRT

ACVN

ExplanationThe transaction routing program in the terminal-owning region issued an ISSUE ERROR request onan MRO link to the application-owning region, andreceived a nonzero return code from terminal control.






Module:DFHZXRT

ACVO

ExplanationThe transaction routing program in the terminal-owning region issued an ISSUE PREPARE request andreceived either a nonzero return code or a responsewhich violates CICS transaction routing protocols.

The return code is located in TCASPRC and theresponse is located in TCASPSN1.


User responseUse the transaction dump to determine whether theproblem is caused by the return code or the response.If terminal control was unable to process the request,the abend may occur when:



Otherwise the distributed application programs mayhave violated APPC conversation protocols.


Module:DFHZXRT

ACVP

ExplanationThe transaction routing program in the terminal-owning region did not receive an FMH43 fromthe application-owning region. This violates CICStransaction routing protocols.

The trace from the application-owning region will showits response to the terminal-owning region.



Module:DFHZXRT

ACVQ

ExplanationThe transaction routing program in the terminal-owning region issued a request to the APPC terminal,and received a nonzero return code from terminalcontrol.

Both the request and the return code are located inthe DFHLUC parameter list which is printed in theexception trace.


User responseUse the transaction dump to determine why terminalcontrol was unable to process the request. Theterminal session may have failed or be in the wrongstate, for example, as the result of both the terminaland application issuing SYNCPOINT ROLLBACK at thesame time.

Module:DFHZXRT

ACVR

ExplanationThe transaction routing program in the terminal-owning region issued a SEND,LAST,WAIT request tothe LU 6.2 terminal, and received a nonzero returncode from terminal control.




Module:DFHZXRT

ACWA

ExplanationCICS CWTO transaction has failed because the taskdoes not own a terminal (TCTTE) as its principalfacility. This has probably happened because CWTOhas been started as an EXEC CICS START transidwithout a terminal ID.

System actionThe transaction is abnormally terminated without atransaction dump.

User responseRetry with a terminal ID value or enter CWTO from aterminal.

Module:DFHCWTO



ADxx abend codesAD21

ExplanationThe CICS-DB2 attachment facility received a requestfor a resource manager with the incorrect name.Message DFHDB2045 is output to transient datadetailing the invalid name.



Module:DFHD2EX1

AD22

ExplanationThe CICS-DB2 attachment facility EDF processor wasunable to interpret the SQL request.

System actionThe command is not interpreted by EDF. A CICStransaction dump is taken with abend code AD22.


Module:DFHD2EDF

AD23

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a LOCK callto the lock manager (LM) domain made by the CICS-DB2 attachment facility service transaction CEX2. Aconsole message is output, an exception trace writtenand, possibly, a system dump taken (depending on theoptions specified in the dump table).

System actionThe CICS-DB2 service task initiates a force shutdownof the CICS-DB2 interface.


Module:DFHD2EX2

AD24

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on an UNLOCKcall to the lock manager (LM) domain made bythe CICS-DB2 attachment facility service transactionCEX2. A console message is output, an exceptiontrace written and, possibly, a system dump taken(depending on the options specified in the dumptable).

System actionThe CICS-DB2 Service task initiates a force shutdownof the CICS-DB2 interface.


Module:DFHD2EX2

AD25

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a LOCK callto the lock manager (LM) domain made by the CICS-DB2 attachment facility while processing a DSNCcommand. A console message is output, an exceptiontrace written and, possibly, a system dump taken(depending on the options specified in the dumptable).

System actionThe DSNC command fails and the transaction isabnormally terminated with a transaction dump.







Module:DFHD2CC

AD26

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on an UNLOCKcall to the lock manager (LM) domain made by theCICS-DB2 attachment facility while processing a DSNCcommand. A console message is output, an exceptiontrace written and, possibly, a system dump taken(depending on the options specified in the dumptable).

System actionThe DSNC command fails and the transaction isabnormally terminated with a transaction dump.


Module:DFHD2CC

AD27

ExplanationThe CICS-DB2 attachment facility attempted to attacha TCB on which a DB2 thread was to be createdto service the SQL request from the application. Theattach of the TCB failed due to lack of storage.


User responseIncrease the size of the CICS region or lower theTCBLIMIT value specified in the DB2CONN.

Module:DFHD2EX1

AD28

ExplanationThe CICS-DB2 attachment facility attempted to attacha TCB on which a DB2 thread was to be createdto service the SQL request from the application. Theattach of the TCB failed.



Module:DFHD2EX1

AD29

ExplanationThe CICS-DB2 attachment facility was unable to link toits EDF processor DFHD2EDF.

System actionThe command is not interpreted by EDF. MessageDFHDB2048 is output to transient data and atransaction dump is taken with abend code AD29.

User responseExamine the trace in the CICS transaction dump todetermine why the link to module DFHD2EDF failed.

Module:DFHD2EDF

AD2A

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a LOCK callto the lock manager (LM) domain. A console messageis output, an exception trace written and, possibly,a system dump taken (depending on the optionsspecified in the dump table).







Module:DFHD2EX1

AD2B

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on an UNLOCKcall to the lock manager (LM) domain. A consolemessage is output, an exception trace written and,possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2EX1

AD2C

ExplanationAn unexpected EXCEPTION response has occurred ona locate call to directory manager (DD) domain tolocate a DB2TRAN control block. A console messageis output, an exception trace written and, possibly,a system dump taken (depending on the optionsspecified in the dump table).



Module:DFHD2EX1

AD2D

ExplanationAn error (INVALID or DISASTER response ) hasoccurred on a locate call to directory manager (DD)domain to locate a DB2TRAN control block. A consolemessage is output, an exception trace written and,possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2EX1

AD2E

ExplanationAn unexpected EXCEPTION response has occurred ona locate call to directory manager (DD) domain tolocate a DB2ENTRY control block. A console messageis output, an exception trace written and, possibly,a system dump taken (depending on the optionsspecified in the dump table).



Module:DFHD2EX1

AD2F

ExplanationAn error (INVALID or DISASTER response ) hasoccurred on a locate call to directory manager (DD)domain to locate a DB2ENTRY control block A consolemessage is output, an exception trace written and,possibly, a system dump taken (depending on theoptions specified in the dump table).









Module:DFHD2EX1

AD2G

ExplanationA transaction attempted to use a DB2ENTRY thatis DISABLED or is DISABLING. The DISABLEDACTattribute of the DB2ENTRY specified ABEND meaningthat new transactions that attempt to use theDB2ENTRY should be abended.


User responseUse CEMT INQ DB2TRAN TRANSID(tttt) where tttt isthe transid, to determine the name of the DB2ENTRYinvolved. Re-enable the DB2ENTRY or discard theDB2ENTRY so that the transid will use a pool thread.

Module:DFHD2EX1

AD2H

ExplanationThe CICS-DB2 attachment facility detected that adynamic plan exit program abended.

System actionCICS trapped the abend from the dynamic plan exit,issued message DFHDB2050, and then abnormallyterminated the task with a CICS transaction dump.

User responseSee the associated DFHDB2050 transient datamessage to determine the abend code with which thedynamic plan exit program abended. Determine whythe exit program abended.

Module:DFHD2EX1

AD2I

ExplanationThe CICS-DB2 attachment facility failed to link to adynamic plan exit program because it was not linkedited AMODE 31.


User responseSee the associated DFHDB2051 transient datamessage to determine the name of the dynamic planexit program involved. Re-linkedit the dynamic planexit program AMODE 31.

Module:DFHD2EX1

AD2J

ExplanationThe CICS-DB2 attachment facility failed to link to adynamic plan exit program because it is disabled.


User responseSee the associated DFHDB2053 transient datamessage to determine the name of the dynamic planexit program involved. Enable the dynamic plan exitprogram.

Module:DFHD2EX1

AD2K

ExplanationThe CICS-DB2 attachment facility failed to link toa dynamic plan exit program because no programdefinition was found.




User responseSee the associated DFHDB2057 transient datamessage to determine the name of the dynamic planexit program involved. Ensure that the dynamic planexit program has been correctly defined to CICS.

Module:DFHD2EX1

AD2L

ExplanationThe CICS-DB2 attachment facility failed to link to adynamic plan exit program because the program couldnot be loaded.


User responseSee the associated DFHDB2058 transient datamessage to determine the name of the dynamic planexit program involved. Ensure that the dynamic planexit program has been correctly defined and is in aload library accessible to CICS.

Module:DFHD2EX1

AD2M

ExplanationThe CICS-DB2 attachment facility failed to link to adynamic plan exit program because the program isdefined as remote.


User responseSee the associated DFHDB2066 transient datamessage to determine the name of the dynamic planexit program involved. Correct the program definitionfor the dynamic plan exit program so that it is definedas local.

Module:DFHD2EX1

AD2N

ExplanationThe CICS-DB2 attachment facility failed to link to adynamic plan exit program.


User responseSee the associated DFHDB2054 transient datamessage to determine the name of the dynamic planexit program involved. Examine the transaction dumpto determine why the link failed.

Module:DFHD2EX1

AD2O

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on an WAIT_MVScall to the dispatcher (DS) domain. A console messageis output, an exception trace written and, possibly,a system dump taken (depending on the optionsspecified in the dump table).



Module:DFHD2EX1

AD2P

ExplanationThe transaction was unable to obtain a DB2 threadfrom a DB2ENTRY or the pool. See the associatedtransient data message DFHDB2011 to determinewhich DB2ENTRY was involved or whether it wasthe pool. The transaction was abended becausethe DB2ENTRY or the pool specified threadwait(no)meaning do not wait for a thread if all threadsare currently in use. Note if message DFHDB2011indicates that the pool was being used, it means thetransaction was using the pool directly rather thanoverflowing to the pool. (An abend AD3T is produced



when a transaction overflows to the pool and no poolthreads are available.)


User responseDetermine whether more threads should be allocatedto the DB2ENTRY or the pool, or whether the numberof instances of this transaction should be limited usingTRANCLASS.

Module:DFHD2EX1

AD2Q

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on an getmaincall to the storage manager (SM) domain. A consolemessage is output, an exception trace written and,possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2EX1

AD2R

ExplanationThe CICS-DB2 attached TCB connection thatprocesses the DB2 request for this transaction hasabended. An exception trace, AP 319D, is writtencontaining the MVS abend code; MVS reason code;and the relevant CICS-DB2 control blocks that areused by the CICS task and by the CICS-DB2 TCBconnection. One of the control blocks returned isthe CSUB control block. This control block containsdata from the MVS SDWA at the time of the abend,for example, the CSB_SDWA_REGS (regs 0-15) andthe CSB_SDWA_PSW fields. The CSB_SDWA_REGS isthe 16 words following the SDWA eye catcher. The

CSB_SDWA_PSW field is the two words following theCSB_SDWA_REGS field.

The TCB connection is terminated if a CICS transactionis forcepurged from CICS when the thread is still activein DB2.


User responseExamine the trace in the CICS transaction dump todetermine why the CICS-DB2 thread TCB abended.

Module:DFHD2EX1

AD2S

ExplanationThe thread TCB servicing the DB2 request forthe transaction issued a sign-on request to DB2which failed. The installed DB2CONN specifiesTHREADERROR(N906D) or THREADERROR(ABEND).

System actionIf THREADERROR(N906D) is specified in theDB2CONN, processing continues. A -906 sqlcode isreturned to the application, and a transaction dump istaken with abend code AD2S.

If THREADERROR(ABEND) is specified in theDB2CONN, the task is abnormally terminated with aCICS transaction dump.

User responseExamine the dump to determine why the signonrequest to DB2 failed. One such reason could be thethread has been cancelled. For authorization failures,examine the AUTHID or AUTHTYPE parameter of theDB2ENTRY or pool used for the transaction. Ensure theid is authorised to access the plan in DB2.

Module:DFHD2EX1

AD2T

ExplanationAn attempt to create a DB2 thread by the TCBservicing the DB2 request for the transactionfailed with DB2 reason code 00F30040. Theinstalled DB2CONN specifies THREADERROR(N906D)or THREADERROR(ABEND).



System actionIf THREADERROR(N906D) is specified in theDB2CONN, processing continues. A -906 sqlcode isreturned to the application and a transaction dump istaken with abend code AD2T.


User responseEither the plan is unavailable or is not known to DB2.

Module:DFHD2EX1

AD2U

ExplanationAn attempt to create a DB2 thread by the TCBservicing the DB2 request failed. The installedDB2CONN specifies THREADERROR(N906D) orTHREADERROR(ABEND).

System actionIf THREADERROR(N906D) is specified in theDB2CONN, processing continues. A -906 sqlcode isreturned to the application and a transaction dump istaken with abend code AD2U.


User responseExamine the dump to determine why the create threadfailed.

Module:DFHD2EX1

AD2V

ExplanationThe CICS-DB2 attachment facility issued a commitor abort request to DB2 but received a reason code00F30805 indicating that connection to DB2 has beenlost. This is due to DB2 terminating abnormally orbeing in the process of terminating abnormally. Ifthe commit or abort request was preceded by aprepare request, DB2 may well still be indoubt. Inthis case, the CICS-DB2 attachment facility instructsCICS to remember the outcome of the UOW pendingresynchronisation, which will happen when CICS andDB2 are reconnected. For an abort request not

preceded by a prepare, i.e. a transaction abend orsyncpoint rollback, DB2 will not be indoubt as theUOW was still inflight. DB2 will backout updates madeby the UOW when restarted so there is no need forCICS to remember the outcome of the UOW.

System actionThe transaction completes normally but a transactiondump is taken with abend code AD2V. If DB2 isindoubt about the outcome of the UOW it will beresolved when CICS and DB2 are reconnected.

User responseContact your system programmer to restart the DB2subsystem.

Module:DFHD2EX1

AD2W

ExplanationThe CICS-DB2 attachment facility issued a single-phase commit call to DB2 but received an unexpectedresponse. Transient data message DFHDB2055 detailsthe DB2 reason code received. The commit requestmay have been processed or it may have been ended.There is no resynchronisation needed, as no CICSrecoverable resources were updated.

System actionThe CICS-DB2 attachment facility abnormallyterminates the transaction with abend code AD2W.The CICS recovery manager will supersede the AD2Wabend code with abend code ASPR. A transactiondump is taken.


Module:DFHD2EX1

AD2X

ExplanationThe CICS-DB2 attachment facility detected that theCICS task and the thread TCB were in an invalidstate. A console message is output, an exceptiontrace written and, possibly, a system dump taken(depending on the options specified in the dumptable).



System actionThe task is abnormally terminated with a transactiondump.


Module:DFHD2EX1

AD2Y

ExplanationThe transaction was unable to obtain a DB2thread from a DB2ENTRY or the pool becausethere were no TCBs available on which to createthe thread. The number of thread TCBs currentlyrunning is at the TCBLIMIT defined in the DB2CONN.Message DFHDB2010 is output to transient data. Thetransaction was abended because either:

• The DB2ENTRY specifies threadwait(no), meaning donot wait for a thread, including having to wait tocreate a thread because a TCB is not available - thatis, do not wait for a TCB either.

• The DB2ENTRY specified threadwait(pool), butthe pool definition within the DB2CONN specifiesthreadwait(no), and again there were no TCBsavailable.

• The transaction was using the pool directly, the poolspecifies threadwait(no) and no TCB was available.


User responseDetermine whether TCBLIMIT should be increasedor whether the number of transactions using DB2 atany one instance should be limited using transactionclasses.

Module:DFHD2EX1

AD2Z

ExplanationDB2 detected a deadlock and the CICS-DB2attachment facility attempted a syncpoint rollbackcommand for the transaction as DROLLBACK(YES) wasspecified for the DB2ENTRY or POOL. The syncpoint

rollback command failed. Message DFHDB2070 isoutput to transient data detailing the transid involvedand the EIBRESP2 from the failed syncpoint rollbackcommand.


User responseExamine the eibresp2 value to determine why thesyncpoint rollback request failed. One possible reasoncould be that the transaction running is a DPL servertransaction which was DPLed to by a client transactionwithout specifying the SYNCONRETURN parameter. Inthis case syncpoints, or syncpoint rollbacks, cannot betaken by the server transaction, so DROLLBACK(YES)is invalid in this case.

Module:DFHD2EX1

AD31

ExplanationAn unexpected EXCEPTION response has occurredon a locate call to directory manager (DD) domainto locate a PACKAGESET control block. A consolemessage is output, an exception trace written and,possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2EX1

AD32

ExplanationAn error (INVALID or DISASTER response ) hasoccurred on a locate call to directory manager (DD)domain to locate a PACKAGESET control block. Aconsole message is output, an exception trace writtenand, possibly, a system dump taken (depending on theoptions specified in the dump table).






Module:DFHD2EX1

AD33

ExplanationThe CICS-DB2 attachment facility detected that theset packageset program DFHD2SPS abended.

System actionCICS trapped the abend from DFHD2SPS, issuedmessage DFHDB2080, and then abnormallyterminated the task with a CICS transaction dump.

User responseSee the associated DFHDB2080 transient datamessage to determine the abend code with whichDFHD2SPS abended. Determine why DFHD2SPSabended.

Module:DFHD2EX1

AD35

ExplanationThe CICS-DB2 attachment facility failed to link tothe set packagset program DFHD2SPS because it isdisabled.


User responseEnable the DFHD2SPS program.

Module:DFHD2EX1

AD36

ExplanationThe CICS-DB2 attachment facility failed to link tothe set packagset program DFHD2SPS because noprogram definition was found.


User responseEnsure that DFHD2SPS has been correctly definedto CICS. The definition for DFHD2SPS cannot beautoinstalled.

The definition for DFHD2SPS is supplied in CICSdefined group DFHDB2. Ensure CSD definitions havebeen upgraded.

Module:DFHD2EX1

AD37

ExplanationThe CICS-DB2 attachment facility failed to link tothe set packageset program DFHD2SPS because theprogram could not be loaded.


User responseEnsure that DFHD2SPS has been correctly defined andis in a load library accessible to CICS.

Module:DFHD2EX1

AD38

ExplanationThe CICS-DB2 attachment facility failed to link tothe set packagset program DFHD2SPS because theprogram is defined as remote.




User responseCorrect the program definition for DFHD2SPS so that itis defined as local.

Module:DFHD2EX1

AD39

ExplanationThe CICS-DB2 attachment facility failed to link to theset packagset program DFHD2SPS.


User responseExamine the transaction dump to determine why thelink failed.

Module:DFHD2EX1

AD3A

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a LOCK callto the lock manager (LM) domain made by the CICS-DB2 attachment facility startup program. A consolemessage is output, an exception trace written and,possibly, a system dump taken (depending on theoptions specified in the dump table).

System actionStartup of the CICS-DB2 interface is terminated,and the interface is closed. The task is abnormallyterminated with a CICS transaction dump.


Module:DFHD2STR

AD3B

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on an UNLOCK

call to the lock manager (LM) domain made bythe CICS-DB2 Attachment facility startup program. Aconsole message is output, an exception trace writtenand, possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2STR

AD3C

ExplanationAn error (INVALID, DISASTER response) has occurredon a CONNECT_TO_DB2 function call to the CICS-DB2Coordinator program DFHD2CO made by the CICS-DB2 Attachment facility startup program. A consolemessage is output, an exception trace written and,possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2STR

AD3D

ExplanationAn unexpected response was received whileattempting to delete a record from a temporarystorage queue during processing of a DSNC STRTcommand. A console message is output, an exceptiontrace written and, possibly, a system dump taken(depending on the options specified in the dumptable).





System actionThe DSNC STRT command fails. The task is abnormallyterminated with a CICS transaction dump.


Module:DFHD2CM1

AD3E

ExplanationDuring processing of a DB2 request for the transaction,an identify request was made to identify the callingTCB to DB2. The identify request failed. A consolemessage is output, an exception trace written and,possibly, a system dump taken (depending on theoptions specified in the dump table).

System actionThe DB2 request fails. The task is abnormallyterminated with a CICS transaction dump.

User responseExamine the exception trace in the dump to determinewhy the identify request failed. The CSUB controlblock is output as part of the exception trace entry,and it contains a record of all calls to DB2 startingat field CSB_TRACE_ENTRIES_START. The identifyrequest contains eyecatcher "IDEN" and is followed bythe DB2 FRB response and reason codes.

Module:DFHD2D2

AD3F

ExplanationDuring processing of a DB2 request for the transaction,a terminate thread request was made to DB2 whichfailed. A console message is output, an exceptiontrace written and, possibly, a system dump taken(depending on the options specified in the dumptable).


User responseExamine the exception trace in the dump to determinewhy the terminate thread request failed. The CSUBcontrol block is output as part of the exception traceentry, and it contains a record of all calls to DB2starting at field CSB_TRACE_ENTRIES_START. Theterminate thread request contains eyecatcher "TERM"and is followed by the DB2 FRB response and reasoncodes.

Module:DFHD2D2

AD3G

ExplanationAn unexpected response was received from an EXECCICS GETMAIN issued during processing of a CICS-DB2 DSNC command. A console message is output, anexception trace written and, possibly, a system dumptaken (depending on the options specified in the dumptable).

System actionThe DSNC command fails. The task is abnormallyterminated with a CICS transaction dump.


Module:DFHD2CM1

AD3H

ExplanationThe issuing of an EXEC SQL command or IFI call from aDynamic Plan Exit is not allowed.


User responseRemove any EXEC SQL commands or IFI calls from theDynamic Plan Exit.

Module:DFHD2EX1

AD3I




ExplanationAn unexpected response was received from an EXECCICS INQUIRE DB2CONN command issued duringstartup of the CICS-DB2 interface. A console messageis output, an exception trace written and, possibly,a system dump taken (depending on the optionsspecified in the dump table).



Module:DFHD2CM1

AD3J

ExplanationA commit request to DB2, issued during the secondphase of syncpoint, failed. A console message isoutput, an exception trace written and, possibly,a system dump taken (depending on the optionsspecified in the dump table).

System actionThe task is abnormally terminated with a CICStransaction dump. CICS maintains a record that theUOW committed pending a future resynchronizationrequest with DB2.

User responseExamine the exception trace in the dump to determinewhy the commit request failed. The CSUB controlblock is output as part of the exception trace entry,and it contains a record of all calls to DB2 startingat field CSB_TRACE_ENTRIES_START. The commitrequest contains eyecatcher "COMM" and is followedby the DB2 FRB response and reason codes.

Module:DFHD2D2

AD3K

ExplanationAn abort request to DB2, issued during the secondphase of syncpoint, failed. A console message is

output, an exception trace written and, possibly,a system dump taken (depending on the optionsspecified in the dump table).

System actionThe task is abnormally terminated with a CICStransaction dump. CICS maintains a record that theUOW backed out pending a future resynchronizationrequest with DB2.

User responseExamine the exception trace in the dump to determinewhy the abort request failed. The CSUB control blockis output as part of the exception trace entry, andit contains a record of all calls to DB2 starting atfield CSB_TRACE_ENTRIES_START. The abort requestcontains eyecatcher "ABRT" and is followed by theDB2 FRB response and reason codes.

Module:DFHD2D2

AD3L

ExplanationDuring processing of a DB2 request for the transaction,an associate request was made to associate the DB2connection with the calling TCB. The associate requestfailed. A console message is output, an exceptiontrace written and, possibly, a system dump taken(depending on the options specified in the dumptable).


User responseExamine the exception trace in the dump to determinewhy the associate request failed. The CSUB controlblock is output as part of the exception trace entry,and it contains a record of all calls to DB2 startingat field CSB_TRACE_ENTRIES_START. The associaterequest contains eyecatcher "ASSO" and is followedby the DB2 FRB response and reason codes.

Module:DFHD2D2

AD3M

ExplanationAn unexpected error occurred during processing ofa DSNC MODIFY command. A console message is



output, an exception trace written and, possibly,a system dump taken (depending on the optionsspecified in the dump table).

System actionThe DSNC MODIFY command fails. The task isabnormally terminated with a CICS transaction dump.


Module:DFHD2CM1

AD3P

ExplanationAn unexpected error occurred during processing of aDSNC STOP command. A console message is output,an exception trace written and, possibly, a systemdump taken (depending on the options specified in thedump table).

System actionThe DSNC STOP command fails. The task is abnormallyterminated with a CICS transaction dump.


Module:DFHD2CM1

AD3Q

ExplanationAn unexpected response was received whileattempting to read a record from a temporary storagequeue during processing of a DSNC STRT command. Aconsole message is output, an exception trace writtenand, possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2CM1

AD3R

ExplanationAn unexpected response was received whileattempting to read a record from a temporary storagequeue during startup of the CICS-DB2 interface. Aconsole message is output, an exception trace writtenand, possibly, a system dump taken (depending on theoptions specified in the dump table).

System actionStartup of the CICS-DB2 interface is terminated, theinterface is closed. The task is abnormally terminatedwith a CICS transaction dump.


Module:DFHD2STR

AD3S

ExplanationAn unexpected response was received from an EXECCICS SET DB2CONN command issued during startupof the CICS-DB2 interface. A console message isoutput, an exception trace written and, possibly,a system dump taken (depending on the optionsspecified in the dump table).



Module:DFHD2CM1







AD3T

ExplanationThe transaction was unable to obtain a DB2 threadfrom the pool. Message DFHDB2011 is output totransient data. The transaction was abended becausethe transaction tried using a DB2ENTRY but allthreads were in use on the DB2ENTRY, and despitethreadwait(pool) being specified, all threads in thepool were also in use. The pool definition within theDB2CONN specifies threadwait(no).


User responseDetermine whether more threads should be allocatedto the DB2ENTRY or the pool, or whether the numberof instances of this transaction should be limited usingTRANCLASS.

Module:DFHD2EX1

AD3U

ExplanationAn error (INVALID or DISASTER response ) hasoccurred on a locate call to transaction manager (XM)domain to locate a transaction definition. A consolemessage is output, an exception trace written and,possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2EX1

AD3W

ExplanationAn unexpected response was received whileattempting to write a record to a temporary storagequeue during startup of the CICS-DB2 interface. A

console message is output, an exception trace writtenand, possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2STR

AD3X

ExplanationAn unexpected response was received whileattempting to write a record to a temporary storagequeue during processing of a DSNC STRT command. Aconsole message is output, an exception trace writtenand, possibly, a system dump taken (depending on theoptions specified in the dump table).



Module:DFHD2CM1

AD3Z

ExplanationThe CICS-DB2 thread TCB processing the DB2 requestfor this transaction has abended because the DB2adapter is being shutdown.


User responseIf this abend should occur at CICS or DB2 shutdownthen it can be ignored, because the DB2 adapter is





abending the task as part of shutdown processing,otherwise you will need assistance from IBM.

Module:DFHD2EX1

AD4A

ExplanationThe CICS-DB2 set packageset program issued anEXEC SQL SET CURRENT PACKAGESET commandwhich failed.


User responseExamine the transaction dump to determine why thecommand failed.

Module:DFHD2EX1

AD4B

ExplanationThe CICS-DB2 attachment facility failed to locate avalid dfhd2pkgset control block.



Module:DFHD2EX1

ADCA

ExplanationThis abend is issued if DBCTL returns a non-zeroresponse code when a DL/I request has been issuedfrom an application program.


User responseLook up accompanying message DFHDB8109 thatappears on the CDBC transient data destination.

Module:DFHDLIDP

ADCB

ExplanationThis abend occurs when DBCTL has notified CICS thata task has issued a DL/I request, but it did not havea PSB scheduled. If your application does have a PSBscheduled then a possible cause for this abend is thatthe DBCTL STOP THREAD command may have beenused to terminate the DBCTL thread that correspondsto this task.

System actionCICS abnormally terminates the transaction with atransaction dump. CICS processing continues.

User responseCheck if the DBCTL operator has issued a STOPTHREAD command for the task that has abnormallyterminated. Look up DBCTL response code 28 in theDBCTL return code section of the IMS messages andcodes.

Module:DFHDLIDP

ADCC

ExplanationThis abend occurs when DBCTL has notified CICS thata task has issued program specification block (PSB)request, but it has a PSB already scheduled. CICSprevents a task from issuing a PSB schedule requestto DBCTL when it has already issued a PSB schedulerequest by returning a PSBSCH response in UIBDLTR.However, in this case it is DBCTL that has rejected thesubsequent PSB schedule request. A possible causefor this abend is a storage over-write.


User responseCheck for any messages issued from your CICS systemindicating that storage over-writes have taken place.



https://www.ibm.com/support/knowledgecenter/SSEPH2_14.1.0/com.ibm.ims14.doc.msgs/common/mc.htm


Look up DBCTL response code 32 in the DBCTL returncode section of the IMS messages and codes.

Module:DFHDLIDP

ADCD

ExplanationThis abend is issued when a deadlock has beendetected by IMS and this transaction has beenselected for abnormal termination.

This abend can occur when a transaction is accessingIMS resources via DBCTL or via a remote DLI requestto a remote CICS region. The remote CICS region canbe accessing IMS via DBCTL, or if it is a CICS 4.1region or earlier, accessing IMS via local DLI.

System actionAccess to IMS resources via DBCTL is withdrawn forthis transaction. Further attempts to access IMS willresult in an AEY9 abend.

CICS abnormally terminates the transaction with atransaction dump. CICS processing continues.

User responseIf ADCD abends occur infrequently in your system, noaction is required although you may like to considersetting your system up in such a way that, after anADCD abend is issued, the transaction is automaticallyrestarted. See the Administering recovery and restartfor further information.

If ADCD abends are occurring frequently in yoursystem, you may need to review the design of yourapplications. Some general techniques for deadlockavoidance are described in the Administering recoveryand restart.

Module:DFHDLIDP

ADCE

ExplanationThis abend is issued when the module DFHDBATreturns a nonzero return code in reply to a DL/Irequest issued from an application program to DBCTL.DFHDBAT is a task related user exit and forms part ofthe CICS-DBCTL interface. This abend is accompaniedby message DFHDB8110.


User responseLook up the accompanying message DFHDB8110 thatappears on the CDBC transient data destination.

Module:DFHDLIDP

ADCF

ExplanationThis abend is issued when the module DFHDLIDPdetects that the CICS-DBCTL Interface has beenconfigured using a DRA startup table (DFSPZPxx)which specifies option PCBLOC=31, and theapplication is amode 24.

PCBLOC=31 specifies that the PCB address listand PCBs can be stored above the line. This isincompatible with amode 24 applications.


User responseLinkedit the application amode 31, or change the DRAstartup table option to PCBLOC=24.

Module:DFHDLIDP

ADCI

ExplanationThis abend is issued when IMS returns a user abend3303 response for a DL/I request issued from anapplication program.

System actionAccess to IMS resources via DBCTL is withdrawn forthis transaction. Further attempts to access IMS willresult in an AEY9 abend.

CICS abnormally terminates the transaction with atransaction dump. CICS processing continues.

User responseCheck the description in the IMS messages and codesfor the meaning of IMS user abend 3303.



https://www.ibm.com/support/knowledgecenter//administering/recovery/dfht20v.html




Module:DFHDLIDP

ADCJ

ExplanationThis abend is issued when an application has beenusing DBCTL, and while the application was stillscheduled to DBCTL, the CICS-DBCTL interface wasterminated.


User responseCheck the CDBC transient data destination formessages indicating the reason for termination of theCICS-DBCTL interface. If you do not know where theCDBC transient is, then please check with your systemprogrammer. Check for messages issued from theDBCTL system.

Module:DFHDLIDP

ADCP

ExplanationWhen checking the DBCTL program specification block(PSB), the external security manager checked theusage of the PSB, and found that:

• The user was unauthorized to access the PSB, or• The PSB was unknown to the external security

manager, or• The user was set to the capability of the default user.

The meaning of the term "user" in the above contextdepends on the way the transaction was invoked.

• If the transaction is being run from a local terminal,or has been routed from a remote terminal, the useris the terminal user. (For a routed transaction, ifPSBCHK=NO is specified in the SIT, or RESSEC=NOis specified in the transaction definition (CEDADEFINE TRANSACTION command), the securitymanager does not check the terminal user.)

• If the transaction is being run as a result of a requestfrom another CICS MRO region, the user is theowner of the other CICS system (as defined to theexternal security manager in the JOB statement ofthe initializing JCL).

• If the transaction is being run as a result of arequest from a connected ISC system, the user

is defined in the SECURITYNAME operand of theinstalled CONNECTION definition that defines thelink between the remote system and the localsystem. Ensure that the name in the SECURITYNAMEoperand is the same as that supplied by theconnected CICS system. This will depend upon thetype of CONNECTION between the two systems.For further information about this, refer to the CICSintercommunication.

Notes.

By the above definitions, a PSB used by a routedtransaction has two users, the terminal user andthe communicating region. Therefore, for routedtransactions, the external security manager makes twochecks, on the terminal user (as qualified in 1 above),and on the communicating region (2 or 3 above).

System actionCICS abnormally terminates the task attempting toschedule the PSB. CICS processing continues.

User responseEnsure that the PSB is defined to the external securitymanager, and that all users have the correct level ofauthorization. If the system setup is correct, note thesecurity violation.

Module:DFHDLIDP

ADCQ

ExplanationThis abend can occur when an application has issuedan EXEC DLI SCHD request for a PSB that containsno DBPCBs, and the SYSSERVE keyword was notspecified. Secondly this abend can occur when anapplication has issued a PCB request for a PSB thatcontains no DBPCBs and the IOPCB option was notspecified. Otherwise it may indicate an IMS processingerror.


User responseCheck that the application program has scheduled theappropriate PSB. If the PSB is correct, then contactyour IMS administrator.

Module:DFHDLIDP


https://www.ibm.com/support/knowledgecenter//fundamentals/connections/dfht11f.html


ADCR

ExplanationThis abend occurs when an application has issued aDL/I request other than a schedule request, and theDBCTL DRA return code of 40 indicates that there wasno active communication with DBCTL.


User responseCheck the CDBC transient data destination formessages indicating the reason for termination of theCICS-DBCTL interface. If you do not know where theCDBC transient data destination is, check with yoursystem programmer. Check for messages issued fromthe DBCTL system.

Module:DFHDLIDP

ADCS

ExplanationCICS issued a single-phase commit request to DBCTLand an unexpected response was returned fromDBCTL.

System actionCICS issues message DFHDB8119 to transient dataqueue CDBC, then terminates the task abnormally witha CICS transaction dump.

User responseMessage DFHDB8119 shows the unexpected responsefrom DBCTL, along with the recovery token of the LUWinvolved. The explanation of message DFHDB8119indicates how the outcome of the LUW can bedetermined.

Module:DFHDBAT

ADCT

ExplanationA user has attempted to invoke the CICS-DBCTLcontrol transaction from a terminal.

System actionCICS rejects the request.

User responseDo not try to invoke CICS internal transactions directly.

Module:DFHDBCT

ADCV

ExplanationThe connection to DBCTL was terminated and thenre-established. The failing task had issued a schedulerequest against an earlier run of DBCTL and istherefore no longer scheduled.


User responseNo action is required, although you may like toconsider setting your system up in such a way that,after an abend ADCV is issued, the transaction isautomatically restarted.

Module:DFHDLIDP

ADDA

ExplanationAn error (INVALID or DISASTER response) hasoccurred on a call to the storage manager domain.The domain that detected the original error providesan exception trace, a console message, and possibly asystem dump (depending on the options in the dumptable).

System actionThe task is abnormally terminated with a CICStransaction dump (depending on the options in thedump table).

User responseSee related message from the domain that detectedthe original error.

Module:DFHDBME, DFHDLI, DFHDLIDP

ADDB


ExplanationAn error (INVALID or DISASTER response) hasoccurred on a call to the catalog (CC) domain. Thedomain that detected the original error provides anexception trace, a console message, and possibly asystem dump (depending on the options in the dumptable).



Module:DFHDBCON, DFHDBDSC

ADDC

ExplanationAn error (INVALID or DISASTER response) hasoccurred on a call to the loader (LD) domain. Thedomain that detected the original error will haveprovided an exception trace, a console message, andpossibly a system dump (depending on the options inthe dump table).



Module:DFHDBCON, DFHDBDI

ADDI

ExplanationCICS has been notified of a DBCTL failure. However, ithas been unable to complete the search for a DBCTLalternate. This is possibly due to an unexpected returncode from an IEFSSREQ request.

System actionA CICS transaction dump is produced. CICS continuesas if no XRF DBCTL alternate has been found. Thisabend is accompanied by message DFHDX8323.

User responseRefer to message DFHDX8323 for further information.It may be necessary to restart DBCTL manually.

Module:DFHDBCT

ADDJ

ExplanationCICS has failed to connect to DBCTL because programDFHDBAT could not be ENABLED.

System actionA CICS transaction dump is produced. The state of theCICS/DBCTL interface remains not connected.

User responseRefer to the transaction dump to determine why theENABLE failed.

Module:DFHDBCON

ADDK

ExplanationCICS failed to obtain or release a lock on either theadapter's Global Work Area(GWA) or the DBCTL GlobalBlock (DGB).


User responseRefer to the transaction dump to determine why lockfailed.

Module:DFHDBAT

ADEF


ExplanationA severe error has been encountered when executingtransaction CLS3.

System actionCLS3 is abnormally terminated with a transactiondump. CICS issues message DFHZC4948.

User responseSee message DFHZC4948 for further guidance.

Module:DFHCLS3

ADIR

ExplanationThe abend code is issued for either of the followingreasons:

• A DFHDI or DFHBMS request was issued when theDFHDIP program was generated as a dummy.

• A DFHDI TYPE=RECEIVE or TYPE=NOTE wasattempted but the transaction identification did notspecify either INBFMH=DIP or INBFMH=ALL.

System actionA CICS transaction dump is provided to assist inproblem determination.

User responseEither generate a DFHDIP program into the system orspecify INBFMH correctly on the profile definition.

Module:DFHDIP

ADIS

ExplanationEXEC CICS ISSUE SEND request has been issued froma task that has a non-terminal principal facility.

System actionA CICS transaction dump is provided to assist inproblem determination.

User responseUse a terminal or device that is properly supported.

Module:DFHEDI

ADLE

ExplanationA DL/I request was made for a remote database,but the system named in the remote PDIR entry wasunknown to CICS, that is, not specified in a DFHTCTTYPE=SYSTEM macro or CEDA DEFINE CONNECTIONcommand.


User responseEither correct the SYSIDNT parameter in the relevantDFHDLPSB entry, or define the remote system toCICS with a DFHTCT TYPE=SYSTEM macro or a CEDADEFINE CONNECTION command.

Module:DFHDLIRP

ADLF

ExplanationA DL/I request was made for a remote database, butthe link to the system on which the database resideswas down.


User responseNotify the system programmer. Once the link to theremote system has been reestablished, resubmit thetransaction.

Module:DFHDLIRP

ADLG

ExplanationA DL/I request was made for a remote database, butthere were errors in the DL/I argument list that wasprovided by the user.



User responseEnsure that any errors in the DL/I argument arecorrected.

Module:DFHDLIRP

ADLP

ExplanationWhen checking the DLI program specification block(PSB), the external security manager checked theusage of the PSB, and found that:

• The user was unauthorized to access the PSB, or• The PSB was unknown to the external security

manager, or• The user was set to the capability of the default user.

The meaning of the term "user" in the above contextdepends on the way the transaction was invoked.

• If the transaction is being run from a local terminal,or has been routed from a remote terminal, the useris the terminal user. (For a routed transaction, ifPSBCHK=NO is specified in the SIT, or RESSEC=NOis specified in the transaction definition (CEDADEFINE TRANSACTION command), the securitymanager does not check the terminal user.)

• If the transaction is being run as a result of a requestfrom another CICS MRO region, the user is theowner of the other CICS system (as defined to theexternal security manager in the JOB statement ofthe initializing JCL).

• If the transaction is being run as a result of arequest from a connected ISC system, the useris defined in the SECURITYNAME operand of theinstalled CONNECTION definition that defines thelink between the remote system and the localsystem. Ensure that the name in the SECURITYNAMEoperand is the same as that supplied by theconnected CICS system. This will depend upon thetype of CONNECTION between the two systems.For further information about this, refer to the CICSintercommunication.

Note:

By the above definitions, a PSB used by a routedtransaction has two users, the terminal user andthe communicating region. Therefore, for routedtransactions, the external security manager makes twochecks, on the terminal user (as qualified in 1 above),and on the communicating region (2 or 3 above).

System actionThe task attempting to schedule the PSB abnormallyterminates.

User responseEnsure that the PSB is defined to the external securitymanager, and that all users have the correct level ofauthorization. If the system setup is correct, note thesecurity violation.

Module:DFHDLIRP

ADMA

ExplanationThe alternate CICS task responsible for tracking theDBCTL connection status of the active CICS hasreceived an error from the CICS Availability Manager(CAVM) message input service.

System actionThe tracking transaction terminates with a CICStransaction dump. No further action is taken inresponse to DBCTL status changes. The global exits,XXDFB and XXDTO, are never invoked and no attemptat a DBCTL restart is made in the event of a takeover.This abend is accompanied by DFHDX8331.

User responseCheck for any other messages relating the CAVMdataset problems. In the event of a takeover, it maybe necessary to restart DBCTL manually.

Module:DFHDBCR

ADMB

ExplanationThe CICS/XRF DBCTL tracking task has receivedan unrecognizable message from the CICS/XRFmessage manager. This abend is preceded by messageDFHDX8333.

System actionThe CICS/XRF DBCTL tracking task abends.

User responseRefer to the instructions for message DFHDX8333.

Module:DFHDBCR.




ADMD

ExplanationThe alternate CICS system task responsible fortracking the DBCTL connection status of the activeCICS has been unable to complete its search for aDBCTL alternate, possibly due to an unexpected returncode from an IEFSSREQ request.

System actionA CICS transaction dump is produced. The trackingtransaction continues as if no DBCTL alternate hadbeen found. This abend is accompanied by messageDFHDX8335.

User responseRefer to message DFHDX8335 for further information.It may be necessary to restart DBCTL manually.

Module:DFHDBCR.

ADPA

ExplanationThe CICS supplied transaction for managing debuggingprofiles, CADP, has received a exception responsefrom the file manager, with reason file error. The filemanager will have issued a message to the CICS joblogcontaining a code which indicates the precise nature ofthe error. For example this abend will be issued if theunderlying file DFHDPFMB used by CADP is disabled ordoesn't exist.

System actionCICS abends the transaction with a transaction dump.

User responseExamine the CICS joblog for associated messages,correct the problem and retry the CADP transaction.

Module:DFHDPLU

ADPB

ExplanationThe CICS supplied transaction for managing debuggingprofiles, CADP, has received a disaster response fromthe file manager, with reason internal error. There is anerror in the file manager program.


User responseExamine the CICS joblog for associated messages.Contact IBM for assistance with this type of error.

Module:DFHDPLU

ADPC

ExplanationThe CICS supplied transaction for managing debuggingprofiles, CADP, has received a disaster response fromthe file manager, with reason disaster percolation.There is an error in one of the CICS domains calledby the file manager.


User responseExamine the CICS joblog for associated messages.Contact IBM for assistance with this type of error.

Module:DFHDPLU

ADPD

ExplanationThe CICS supplied transaction for managing debuggingprofiles, CADP, has received a purged response fromthe file manager. reason disaster precolation. It islikely that an underlying request to CICS File Controlhas timed out because the record that CADP is tryingto access, is held up by another transaction. Forexample this would occur if CECI was bing used toaccess the underlying file, DFHDPFMB, at the sametime as using CADP.


User responseInvestigate if there are other tasks running against thefile used by CADP.

Module:DFHDPLU

ADPI


ExplanationThe CICS supplied program for inactivating alldebugging profiles, DFHDPIN, has received aexception response from the file manager, with reasonfile error. The file manager will have issued a messageto the CICS joblog containing a code which indicatesthe precise nature of the error. For example this abendwill be issued if the underlying file DFHDPFMB usedby CADP was disabled or deleted whilst DFHDPIN wasrunning.


User responseExamine the CICS joblog for associated messages,correct the problem and retry the CADP transaction.

Module:DFHDPIN

ADPL

ExplanationA server program has issued a command whichis restricted in the distributed program link (DPL)environment. Certain API and CPI-RR requests, andthe DL/I terminate request are not allowed in the DPLenvironment. See the Developing CICS Applications fora list of these restricted commands.

A server program is a program which has beenremotely linked, or a program defined to run with theDPL subset.


User responseRemove the restricted commands from the serverprogram, or run the server program locally.

Module:DFHEIP, DFHCPIR, DFHDLI

ADXA

ExplanationThe XRF DBCTL state catch-up transaction, DXCU, hasfailed.

System actionDXCU is abnormally terminated with a CICStransaction dump. This abend is accompanied byDFHDX8319.

User responseDiagnose the error from the CICS transaction dump.Refer to DFHDX8319 for further information.

Module:DFHDXCU

ADXB

ExplanationThe XRF DBCTL state catch-up transaction, DXCU, hasfailed.

System actionDXCU is abnormally terminated with a CICStransaction dump. This abend is accompanied byDFHDX8318.

User responseUse the dump to help diagnose the problem. Referto DFHDX8318 for further information. Check for anyother messages relating to CICS availability manager(CAVM) data set problems.

Module:DFHDXCU

AExx abend codesAEC1

ExplanationAn attempt has been made to use the Command LevelInterpreter (CECI) or the Enhanced Main Terminal(CEMT) or an RDO (CEDA, CEDB, CEDC) transaction ona terminal that is not supported.


User responseUse a terminal that is supported by the CommandLevel Interpreter, Enhanced Main Terminal, or RDOtransaction.



Module:DFHECIP, DFHECSP, DFHEMTP, DFHESTP, DFHEOTP,DFHEDAP

AEC2

ExplanationAn attempt has been made to use the Command LevelInterpreter (CECI) or the Enhanced Main Terminal(CEMT) or an RDO (CEDA, CEDB, CEDC) transaction ona display terminal of size less than 24 X 80.


User responseUse a display terminal that is supported by theCommand Level Interpreter or Enhanced MainTerminal or RDO transaction.

Module:DFHECIP, DFHECSP, DFHEMTP, DFHESTP, DFHEOTP,DFHEDAP

AEC7

ExplanationLanguage Environment has encountered anunexpected error during the THREAD INITIALIZATIONphase while attempting to execute a LanguageEnvironment enabled program. The return codereceived from Language Environment is placed into thefield EIBRESP2.

System actionMessage DFHAP1200 is issued and the transaction isabnormally terminated. The program is disabled.

User responseRefer to the error message or messages issued byLanguage Environment to determine the cause of theproblem.

Module:DFHAPLI

AEC8

ExplanationLanguage Environment has encountered anunexpected error during the RUNUNIT

INITIALIZATION phase while attempting to execute aLanguage Environment enabled program.

System actionThe return code received from Language Environmentis placed into the field EIBRESP2. MessageDFHAP1200 is issued and the transaction isabnormally terminated. The program is disabled.


Module:DFHAPLI

AEC9

ExplanationLanguage Environment has encountered anunexpected error during the RUNUNIT BEGININVOCATION phase while attempting to execute aLanguage Environment enabled program.

System actionThe return code received from Language Environmentis placed into the field EIBRESP2. MessageDFHAP1200 is issued and the transaction isabnormally terminated. The program is disabled.


Module:DFHAPLI

AECA

ExplanationAn attempt has been made to run one of the CICSinternal EP Adapter transactions: CEPQ, CEPT, CEPR,or CEPS as a user transaction.

System actionCICS terminates the task.

User responseInvestigate why the attempt was made to run a CICSsupplied EP Adapter as a user transaction.


Module:DFHECEAM, DFHECEAQ, DFHECEAS, DFHECEAT

AECC

ExplanationAn error occurred while emitting an event. Thisproblem is likely to have been caused by an error inthe specification of the event or in the configuration ofthe EP adapter.

System actionAn exception trace entry is written. The EP adaptertask is abnormally terminated with a CICS transactiondump.

User responseInspect the CICS trace and message log to determinethe cause of the failure.


AECE

ExplanationAn unexpected error occurred in the event processingdeferred filtering task CEPF.

System actionAn exception trace entry is written. The CEPF task isabnormally terminated with a CICS transaction dump.


Module:DFHECDF

AECM

ExplanationAn attempt was made to attach a CICS eventprocessing deferred filtering task CEPF, but thetransaction was not attached internally by CICS.

System actionAn exception trace entry is written. The CEPF task isabnormally terminated.

User responseInvestigate why an attempt was made to run a CICSsupplied event processing deferred filtering task as auser transaction.

Module:DFHECDF

AECO

ExplanationAn unexpected error occurred while emitting an event.

System actionAn exception trace entry is written. The EP adaptertask is abnormally terminated with a CICS transactiondump.



AED1

ExplanationThis abend is produced as a result of either:

• An attempt to use the execution diagnostic facility(EDF) on an unsupported terminal,

• Using the temporary storage browse transaction(CEBR) on an unsupported device, or

• An attempt to initiate the temporary storage browsetransaction (CEBR) with a non-terminal principalfacility.


User responseUse a terminal or device that is properly supported.

Module:DFHEDFP, DFHEDFBR

AED2

ExplanationThe program EDF has terminated a task and placedthis abend code in the terminated task's TCA. This


occurs because execution of EDF is about to beabnormally terminated. A probable reason for EDFbeing terminated is that a line, control unit, or aterminal has been put out of service.


User responseUse a terminal that is supported as a displayterminal by EDF. A CICS transaction dump of thetask terminated with this abend code is available forreview.

Module:DFHEDFX

AED3

ExplanationThe program EDF has terminated a task and placedthis abend code in the terminated task's TCA. Thetermination occurs because execution of EDF is aboutto be abnormally terminated.

One possible cause of an abend in EDF is incorrectdata being sent to the terminal by the user task.


User responseA CICS transaction dump of the terminated task andalso a similar dump for EDF, when its termination wasabnormally terminated, are available for review.

Module:DFHEDFX

AED4

ExplanationAn internal logic error has been detected in EDFmodule DFHEDFP.


User responseThis indicates a CICS logic error. If you need furtherassistance from IBM to resolve this problem, seeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHEDFP

AED5

ExplanationAn internal logic error was been detected in EDF.Insufficient dynamic storage was pre-allocated.

System actionEDF is terminated abnormally with dumps havingdump codes CXSP, RMIN, PAGE, LDIN. The user taskcontinues.

User responseThe problem may be avoided by less complex userinteractions with EDF. If the problem persists, youmay need further assistance. See Working with IBMto solve your problem for guidance on how to proceed.

Module:DFHEDFD

AED6

ExplanationAn internal logic error was detected in EDF.

System actionEDF is terminated abnormally with dumps havingdump codes CXSP, RMIN, PAGE, LDIN. The user taskcontinues.

User responseThe problem may be avoided by less complex userinteractions with EDF. If the problem persists, youmay need further assistance. See Working with IBMto solve your problem for guidance on how to proceed.

Module:DFHEDFU

AED7

ExplanationThe installed definition of the transaction CEDF has aTWA size which is too small.







System actionCICS abnormally terminates the transaction with aCICS transaction dump.

User responseIf you have an updated copy of the CEDF transactioninstalled, ensure that you have a TWA size at leastas big as the one defined by the IBM supplieddefinition. If you do not have an updated CEDF youmay need further assistance to resolve this problem.See Working with IBM to solve your problem forguidance on how to proceed.

Module:DFHEDFP

AED8

ExplanationA terminal control error has occurred in DFHEDFX.



Module:DFHEDFX

AED9

ExplanationA temporary storage error has occurred in EDF. Thiscould be caused by an input/output error on temporarystorage or because temporary storage data is full.

System actionEDF is abnormally terminated with a CICS transactiondump.

User responseInvestigate the reason for the temporary storagerequest failure. Ensure that the definition of thetemporary storage data set is correct.

See the Troubleshooting and support for furtherguidance in dealing with temporary storage problems.

Module:

DFHEDFD

AEDA

ExplanationThe CEDF transaction has been started with an invalidstart code. This could be the result of attempting tostart the execution diagnostic facility (EDF) with EXECCICS START(CEDF).


User responseUse the transaction dump to determine why the starthas failed.

Module:DFHEDFX

AEDB

ExplanationDFHEDFP has been passed an invalid EDFXA. This isan internal CICS error.



Module:DFHEDFX

AEDC

ExplanationThe program EDF has terminated because a GETMAINrequest to the storage manager failed.





http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/troubleshooting/troubleshooting.html


User responseUse the transaction dump to determine why therequest has failed.

Module:DFHEDFX

AEDD

ExplanationCICS has attempted to attach the EDF task to displaythe user request but the attach has failed.


User responseUse the transaction dump to determine why the attachhas failed.

Module:DFHEDFX

AEDE

ExplanationCICS has suspended the user task to allow the EDFtask to complete but an error has occurred whileperforming the suspend.


User responseUse the transaction dump to determine why thesuspend has failed.

Module:DFHEDFX

AEDF

ExplanationCICS has suspended the user task to allow the EDFtask to complete. The user task has been purged whilesuspended, before control was returned from EDF.


User responseThe task was probably purged by the main terminaloperator.

Investigate the reason why the task was purged. Thismay have been in an attempt to clear the systemwhich appeared to be deadlocked for some reason.

Module:DFHEDFX

AEDG

ExplanationCICS has suspended the user task to allow the EDFtask to complete. The user task has gone away whilesuspended, before control was returned from EDF.


User responseUse the transaction dump to determine the reasonwhy the task finished before being resumed.

Module:DFHEDFX

AEDH

ExplanationAn error occurred when CICS called the ProgramManager in order to discover details of the userprogram that has invoked EDF.


User responseUse the transaction dump to determine why the callhas failed.

Module:DFHEDFX

AEE0

ExplanationAn application that is executing in AMODE(64) calledCICS using a stub program that does not supportAMODE(64).



User responseEnsure that the application program calls the correctstub program in the correct AMODE.

The application must either call the AMODE(64)version of the stub program or switch AMODE beforecalling CICS with the stub program that it is currentlyusing.

For an application to call the AMODE(64) versionof the stub program, the SYSSTATE macro with theoption AMODE64=YES must be invoked before anyCICS-supplied macros are invoked.

Module:DFHCPI,DFHEIP, DFHEIPA, DFHERM

AEE1

ExplanationThe application program called an AMODE(64)command stub, but was not executing in AMODE(64).


User responseEnsure that the application program is in the correctAMODE and is calling the correct stub program.

The application must either call the non-AMODE(64)version of the stub program, or switch to AMODE(64)before calling CICS with the current stub program.

Module:DFHEIG, DFHEIGA

AEE2

ExplanationThe initial AMODE(64) command processor module,DFHEIG, detected an application program error. Anexception trace is produced immediately before theabend to identify the error.


User responseUse the exception trace to identify and correct theerror.

Module:DFHEIG

AEE3

ExplanationAn AMODE(64) assembler application used DFHEIRETto return, but the dynamic storage area (DSA) that isbeing released by the CICS epilog code is not at thefront of the chain. The assembler DSAs are obtained bythe DFHEIENT macro and CICS prolog code, and arechained together, with each one added to the front ofthe chain.


User responseEnsure that all assembler application programs thatare directly called and use DFHEIENT use eitherDFHEIRET or the EXEC CICS RETURN command toreturn to their caller.

Module:DFHEIGA

AEI0

ExplanationPGMIDERR condition not handled.

This is one of a number of abends issued by theEXEC interface program. Because of their similarcharacteristics these abends are described as a group.

See the description of abend AEIA for further details.

System action:

User response:

Module:DFHEIP

AEI1

ExplanationTRANSIDERR condition not handled.




System action:

User response:

Module:DFHEIP

AEI2

ExplanationENDDATA condition not handled.



System action:

User response:

Module:DFHEIP

AEI3

ExplanationINVTSREQ condition not handled.



System action:

User response:

Module:DFHEIP

AEI4

ExplanationEXPIRED condition not handled.



System action:

User response:

Module:DFHEIP

AEI8

ExplanationTSIOERR condition not handled.



System action:

User response:

Module:DFHEIP

AEI9

ExplanationMAPFAIL condition not handled.



System action:

User response:

Module:DFHEIP

AEIA

ExplanationThe EXEC interface program issues an abend when anexceptional condition has occurred but the commanddoes not have the RESP option (or NOHANDLE option),or the application program has not executed anEXEC CICS HANDLE CONDITION command for thatcondition. This will cause DFHEIP to take the systemaction for the condition in question. In most cases, thesystem action will be to abend the transaction.

Because of their similar characteristics, the above-named abend codes for the EXEC interface programare described as a group. The codes and theircorresponding exceptional conditions are as follows:

Code Condition

AEIA ERROR

AEID EOF

AEIE EODS

AEIG INBFMH

AIEH ENDINPT

AEII NONVAL


Code Condition

AEIJ NOSTART

AEIK TERMIDERR

AEIL FILENOTFOUND

AEIM NOTFND

AEIN DUPREC

AEIO DUPKEY

AEIP INVREQ

AEIQ IOERR

AEIR NOSPACE

AEIS NOTOPEN

AEIT ENDFILE

AEIU ILLOGIC

AEIV LENGERR

AEIW QZERO

AEIZ ITEMERR

AEI0 PGMIDERR

AEI1 TRANSIDERR

AEI2 ENDDATA

AEI3 INVTSREQ

AEI4 EXPIRED

AEI8 TSIOERR

AEI9 MAPFAIL

AEXC RESIDERR

AEXF ESCERROR

AEXG UOWLNOTFOUND

AEXI TERMERR

AEXJ ROLLEDBACK

AEXK END

AEXL DISABLED

AEXU NOTPOSS

AEXV VOLIDERR

AEXW TASKIDERR

AEX1 DSNNOTFOUND

AEX2 LOADING

AEX3 MODELIDERR

Code Condition

AEX4 UOWNOTFOUND

AEX5 PARTNERIDERR

AEX6 PROFILEIDERR

AEX7 NETNAMEIDERR

AEX8 LOCKED

AEX9 RECORDBUSY

AEYA INVERRTERM

AEYB INVMPSZ

AEYC IGREQID

AEYE INVLDC

AEYG JIDERR

AEYH QIDERR

AEYJ DSSTAT

AEYK SELNERR

AEYL FUNCERR

AEYM UNEXPIN

AEYN NOPASSBKRD

AEYO NOPASSBKWR

AEYP SEGIDERR

AEYQ SYSIDERR

AEYR ISCINVREQ

AEYT ENVDEFERR

AEYU IGREQCD

AEYV SESSIONERR

AEYX USERIDERR

AEYZ CBIDERR

AEY0 INVEXITREQ

AEY1 INVPARTNSET

AEY2 INVPARTIN

AEY3 PARTNFALL

AEY7 NOTAUTH

AEZE CHANGED

AEZF PROCESSBUSY

AEZG ACTIVITYBUSY

AEZH PROCESSERR


Code Condition

AEZI ACTIVITYERR

AEZJ CONTAINERERR

AEZK EVENTERR

AEZL TOKENERR

AEZM NOTFINISHED

AEZN POOLERR

AEZO TIMERERR

AEXP SYMBOLERR

AEZQ TEMPLATERR

AEZR NOTSUPERUSER

AEZS CSDERR

AEZT DUPRES

AEZU RESUNAVAIL

AEZV CHANNELERR

AEZW CCSIDERR

AEZX TIMEDOUT

AEZY CODEPAGEERR

AEZZ INCOMPLETE

AEZ1 APPNOTFOUND

AEZ2 BUSY


User responseChange the application program either to prevent thecondition recurring, to check it by using the RESPoption, or to handle the condition when it doesoccur (by using the EXEC CICS HANDLE CONDITIONcommand). If necessary, use the contents of theEIBRESP2 field or the EIBRCODE in the EIB to assist indetermining the cause of the exceptional condition.

Problem determinationThe function code of the command that produced theexceptional response and the response code can befound in the EXEC interface block (EIB). The EIB ispart of a larger control block, used by DFHEIP, knownas the EXEC interface storage block (EIS). The EIS isaddressed by the TCAEISA, which is the system part of

the TCA + X'90' The EIB is pointed to from the EIS +X'8'.

The function code may be located at offset X'1B' inthe EIB while the response codes may be one of thefollowing at the given offsets:

EIBRCODE

X'1D'

EIBRESP

X'4C'

EIBRESP2

X'50'

The CICS Application development reference givestranslations of the encoded functions and theirresponses.

Analysis: Because these abend codes are directlyrelated to exceptional conditions that can be specifiedin HANDLE CONDITION commands, the applicationprogrammer should decide whether the condition isone that should be handled by the application (forexample ENDFILE), or one that requires modificationsto the application or CICS tables. :i1.DFHEIP abendcodes

Module:DFHEIP

AEID

ExplanationEOF condition not handled.



System action:

User response:

Module:DFHEIP

AEIE

ExplanationEODS condition not handled.



System action:



User response:

Module:DFHEIP

AEIG

ExplanationINBFMH condition not handled.



System action:

User response:

Module:DFHEIP

AEIH

ExplanationENDINPT condition not handled.



System action:

User response:

Module:DFHEIP

AEII

ExplanationNONVAL condition not handled.



System action:

User response:

Module:DFHEIP

AEIJ

ExplanationNOSTART condition not handled.



System action:

User response:

Module:DFHEIP

AEIK

ExplanationTERMIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEIL

ExplanationFILENOTFOUND condition not handled.



System action:

User response:

Module:DFHEIP

AEIM

ExplanationNOTFND condition not handled.



System action:

User response:

Module:DFHEIP


AEIN

ExplanationDUPREC condition not handled.



System action:

User response:

Module:DFHEIP

AEIO

ExplanationDUPKEY condition not handled.



System action:

User response:

Module:DFHEIP

AEIP

ExplanationINVREQ condition not handled.



System action:

User response:

Module:DFHEIP

AEIQ

ExplanationIOERR condition not handled.



System action:

User response:

Module:DFHEIP

AEIR

ExplanationNOSPACE condition not handled.



System action:

User response:

Module:DFHEIP

AEIS

ExplanationNOTOPEN condition not handled.



System action:

User response:

Module:DFHEIP

AEIT

ExplanationENDFILE condition not handled.



System action:

User response:

Module:DFHEIP

AEIU


ExplanationILLOGIC condition not handled.



System action:

User response:

Module:DFHEIP

AEIV

ExplanationLENGERR condition not handled.



System action:

User response:

Module:DFHEIP

AEIW

ExplanationQZERO condition not handled.



System action:

User response:

Module:DFHEIP

AEIZ

ExplanationITEMERR condition not handled.



System action:

User response:

Module:DFHEIP

AELA

ExplanationThe executing function has been purged before controlcould be returned.

System actionThe transaction is marked to be abnormallyterminated with abend code AELA.

User responseInvestigate the reason the task was purged. It waspurged either by the main terminal operator, or as aresult of a deadlock timeout.


If the task was timed out automatically as a resultof the DTIMOUT value being exceeded, this may bedue to insufficient main storage being available forthe number of tasks in the system. If the amount ofmain storage cannot be increased then the numberof tasks in the system should be reduced to avoidshort-on-storage situations. Another possibility wouldbe to increase the value of the DTIMOUT option for thetransaction.

Module:DFHETL

AELB

ExplanationThe executing function has been purged before controlcould be returned.

System actionThe transaction is marked to be abnormallyterminated with abend code AELB.

User responseInvestigate the reason the task was purged. It waspurged either by the main terminal operator, or as aresult of a deadlock timeout.



If the task was timed out automatically as a resultof the DTIMOUT value being exceeded, this may bedue to insufficient main storage being available forthe number of tasks in the system. If the amount ofmain storage cannot be increased then the numberof tasks in the system should be reduced to avoidshort-on-storage situations. Another possibility wouldbe to increase the value of the DTIMOUT option for thetransaction.

Module:DFHEGL

AEMA

ExplanationAn error (INVALID or DISASTER response) hasoccurred on a call to the application (AP) domain whena request for set user exit active could not be serviced.

System actionThe task is abnormally terminated. The domain thatdetected the original error issues a console messageand might provide an exception trace, and dependingon the options specified in the dump table, a systemdump.

User responseSee the associated console message for furtherguidance.

Module:DFHUEM

AEMB

ExplanationAn error (INVALID or DISASTER response) hasoccurred on a call to the loader (LD) domain. Thedomain that detected the original error will haveprovided an exception trace, a console message, andpossibly a system dump (depending on the options inthe dump table).


User responseSee the related message from the domain thatdetected the original error.

Module:

DFHUEM

AEMP

ExplanationThe task was purged before a set active request tothe application (AP) domain was able to completesuccessfully. The domain that first detected the purgedcondition may provide an exception trace.


User responseInvestigate why the task was purged. This is either asa result of a purge from the main terminal operator viathe CEMT transaction, or by the task being timed outafter waiting for longer than the DTIMOUT (deadlocktimeout) value specified for the transaction.

If the main terminal operator purged the task, this mayhave been in an attempt to clear the system whichappeared to be deadlocked for some reason.

If the task was timed out automatically as a resultof the DTIMOUT value being exceeded, this may bedue to insufficient main storage being available forthe number of tasks in the system. If the amount ofmain storage cannot be increased, reduce the numberof tasks in the system to avoid short-on-storagesituations. Another possibility is to increase the valueof the DTIMOUT option for the transaction.

Module:DFHUEM

AEMQ

ExplanationThe task was purged before an IDENTIFY_PROGRAMrequest to the loader (LD) domain was able tocomplete successfully. The domain that first detectedthe purged condition provides an exception trace.


User responseInvestigate why the task was purged. This is either asa result of a purge from the main terminal operator viathe CEMT transaction, or by the task being timed out


after waiting for longer than the DTIMOUT (deadlocktimeout) value specified for the transaction.



Module:DFHUEM

AEPD

ExplanationAn unexpected error occurred while dispatchingevents.

System actionAn exception trace entry is written. The EP dispatchertask is abnormally terminated with a CICS transactiondump.


Module:DFHEPDS

AEPM

ExplanationAn attempt was made to attach a CICS EP dispatchertask, but the transaction was not attached internally byCICS.

System actionAn exception trace entry is written. The EP dispatchertask is abnormally terminated.

User responseInvestigate why the attempt was made to run a CICSsupplied EP dispatcher task as a user transaction.

Module:DFHEPDS, DFHEPSY

AEPO

ExplanationAn unexpected error occurred in the EP dispatcherevent queue server task.

System actionAn exception trace entry is written. The EP dispatchertask is abnormally terminated with a CICS transactiondump.


Module:DFHEPSY

AETA

ExplanationA CICS transaction has issued a non-CICS commandvia an application "stub" (an expansion of aDFHRMCAL macro). Program DFHERM has determinedthat the exit has been disabled since the previousDFHRMCAL request was issued from the transaction.

System actionThe task is abnormally terminated with a transactiondump

User responseNotify your system programmer.

Module:DFHERM

AETC

ExplanationA CICS transaction has issued a non-CICS commandvia an application "stub" (an expansion of aDFHRMCAL macro). However, the task-related userexit (TRUE) is not known to program manager.

System actionThe task is abnormally terminated with a transactiondump

User responseEnsure that the TRUE as identified to the DFHRMCALmacro has been correctly defined to CICS.

Module:


DFHERM

AETF

ExplanationThe task was purged before a request to thestorage manager (SM) domain was able to completesuccessfully. The domain that first detected the purgedcondition will have provided an exception trace.





Module:DFHERM

AETG




Module:DFHERM

AETH






Module:DFHERM

AETI





Module:DFHERM

AETJ

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anADD_LINK call to the recovery manager (RM) domain.For errors other than EXCEPTION, the RM domainprovides an exception trace, a console message, andpossibly a system dump (depending on the options inthe dump table).

For all errors, DFHERM provides an exception trace,console message DFHAP0002, and possibly a systemdump (depending on the options in the dump table).



Module:DFHERM

AETK

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anSET_LINK call to the recovery manager (RM) domain.For errors other than EXCEPTION, the RM domainprovides an exception trace, a console message, andpossibly a system dump (depending on the options inthe dump table).




Module:DFHERM

AETL

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anSET_UOW call to the recovery manager (RM) domain.For errors other than EXCEPTION, the RM domainprovides an exception trace, a console message, andpossibly a system dump (depending on the options inthe dump table).




Module:DFHERM

AETM

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR, or PURGED) has occurred on anINQUIRE_TRANSACTION call to the transactionmanager (XM) domain. For errors other thanEXCEPTION, the XM domain provides an exceptiontrace, a console message, and possibly a system dump(depending on the options in the dump table).

For all errors, DFHRMSY provides an exception trace,console message DFHAP0002, and possibly a systemdump (depending on the options in the dump table).







Module:DFHRMSY

AETN

ExplanationAn EXCEPTION response with an unexpected reasonoccurred on an INITITIATE_RECOVERY call torecovery manager (RM) domain. DFHRMSY providesan exception trace, console message DFHAP0002, andpossibly a system dump (depending on the options inthe dump table).



Module:DFHRMSY

AETO

ExplanationAn error (DISASTER, INVALID, KERNERROR, orPURGED) has occurred on an INITIATE_RECOVERYcall to the recovery manager (RM) domain. TheRM domain provides an exception trace, a consolemessage, and possibly a system dump (depending onthe options in the dump table).

DFHRMSY also provides an exception trace, consolemessage DFHAP0002, and possibly a system dump(depending on the options in the dump table).



Module:DFHRMSY

AETP

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR, or PURGED) has occurred on anTERMINATE_RECOVERY call to recovery manager(RM) domain. For errors other than EXCEPTION, theRM domain provides an exception trace, a consolemessage, and possibly a system dump (depending onthe options in the dump table).




Module:DFHRMSY

AETQ

ExplanationAn EXCEPTION response with an unexpected reasonoccurred on an INQUIRE_UOW call to the recoverymanager (RM) domain. DFHRMSY provides anexception trace, console message DFHAP0002, andpossibly a system dump (depending on the options inthe dump table).









Module:DFHRMSY

AETR

ExplanationAn error (DISASTER, INVALID, KERNERROR, orPURGED) has occurred on an INQUIRE_UOW call tothe recovery manager (RM) domain. The RM domainprovides an exception trace, a console message, andpossibly a system dump (depending on the options inthe dump table).

DFHRMSY also provides an exception trace, consolemessage DFHAP0002, and possibly a system dump(depending on the options in the dump table).



Module:DFHRMSY

AETS

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR, or PURGED) has occurred on anINQUIRE_STARTUP call to recovery manager (RM)domain. For errors other than EXCEPTION, theRM domain provides an exception trace, a consolemessage, and possibly a system dump (depending onthe options in the dump table).




Module:DFHRMSY

AEX0

ExplanationTCIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEX1

ExplanationDSNNOTFOUND condition not handled.



System action:

User response:

Module:DFHEIP

AEX2

ExplanationLOADING condition not handled.



System action:

User response:

Module:DFHEIP

AEX3

ExplanationMODELIDERR condition not handled.






System action:

User response:

Module:DFHEIP

AEX4

ExplanationUOWNOTFOUND condition not handled.



System action:

User response:

Module:DFHEIP

AEX5

ExplanationPARTNERIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEX6

ExplanationPROFILEIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEX7

ExplanationNETNAMEIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEX8

ExplanationLOCKED condition not handled.



System action:

User response:

Module:DFHEIP

AEX9

ExplanationRECORDBUSY condition not handled.



System action:

User response:

Module:DFHEIP

AEXC

ExplanationRESIDERR condition not handled.



System action:


User response:

Module:DFHEIP

AEXF

ExplanationESCERROR condition not handled.



System action:

User response:

Module:DFHEIP

AEXG

ExplanationUOWLNOTFOUND condition not handled.



System action:

User response:

Module:DFHEIP

AEXI

ExplanationTERMERR condition not handled.



System action:

User response:

Module:DFHEIP

AEXJ

ExplanationROLLEDBACK condition not handled.



System action:

User response:

Module:DFHEIP

AEXK

ExplanationEND condition not handled.



System action:

User response:

Module:DFHEIP

AEXL

ExplanationDISABLED condition not handled.



System action:

User response:

Module:DFHEIP

AEXU

ExplanationDuring execution of an EXEC CICS command, aNOTPOSS condition has been raised on encounteringan invalid parameter. This is probably caused by aprevious storage overlay.



User responseRefer to abend AEIA for an explanation of how todetermine the function code of the CICS commandthat caused the abend.

It is not possible to set an EXEC CICS HANDLECONDITION for NOTPOSS.

The system programmer should investigate the causeof the storage overlay.

Module:DFHEIDTI, DFHEIG, DFHEIP, DFHEIQDS, DFHEIQSA,DFHEIQSC, DFHEIQSM, DFHEIQSP, DFHEIQST,DFHEIQSX

AEXV

ExplanationVOLIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEXW

ExplanationSUPPRESSED condition not handled.



System action:

User response:

Module:DFHEIP

AEXX

ExplanationTASKIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEXY

ExplanationThe executing transaction has been purged beforecontrol could be returned.

This can arise when the transaction is purged while

• A CICS command was being processed• The transaction was waiting to be dispatched


User responseContact your system programmer to determine whythe transaction has been purged.

For module list, see Diagnostics reference.

Module:DFHACP, DFHAPRR, DFHAPRX, DFHBEP, DFHBREX,DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, DFHBSTS,DFHBSTZO, DFHD2CC, DFHD2EX1, DFHD2EX2,DFHD2STR, DFHEDCP, DFHEDFP, DFHEDI, DFHEEI,DFHEGL, DFHEIBAM, DFHEICRE, DFHEIIC, DFHEIG,DFHEIP, DFHEIPA, DFHEIPI, DFHEIPRT, DFHEIPSE,DFHEIPSH, DFHEIQAS, DFHEIQBA, DFHEIQBR,DFHEIQCF, DFHEIQCS, DFHEIQDE, DFHEIQDI,DFHEIQDN, DFHEIQDS, DFHEIQDU, DFHEIQD2,DFHEIQEJ, DFHEIQIR, DFHEIQML, DFHEIQMQ,DFHEIQMS, DFHEIQMT, DFHEIQPF, DFHEIQPI,DFHEIQPN, DFHEIQRL, DFHEIQRQ, DFHEIQSA,DFHEIQSC, DFHEIQSJ, DFHEIQSK, DFHEIQSL,DFHEIQSM, DFHEIQSP, DFHEIQSQ, DFHEIQST,DFHEIQSX, DFHEIQSY, DFHEIQTM, DFHEIQTR,DFHEIQTS, DFHEIQUE, DFHEIQVT, DFHEIQWB,DFHEIQWR, DFHEIQW2, DFHEIUOW, DFHEIWB,DFHEKC, DFHEMS, DFHEOP, DFHEPC, DFHEPS,DFHERM, DFHESC, DFHESE, DFHESN, DFHETC,DFHETL, DFHETRX, DFHTACP, DFHTFP, DFHTIEM,DFHUEM, DFHWBTC, DFHXMBR, DFHXTP, DFHZATS,DFHZNCA, DFHZNCE, DFHZTSP, DFHZXQO, DFHZXST

AEXZ

ExplanationA command has failed due to a serious failure in aCICS component (resource manager).


https://www.ibm.com/support/knowledgecenter//home/reference-diagnostics.html

System actionThe transaction is abnormally terminated with abendcode AEXZ. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.

User responseUse the transaction dump to determine the causeof the failure. For further assistance, or if moduleDFHDUIO is not loaded and no transaction dump isavailable, contact your system programmer.


Module:DFHACP, DFHAPRA, DFHAPRR DFHAPRX, DFHBEP,DFHBREX, DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC,DFHBSTS, DFHBSTZO, DFHCDKRN, DFHEDCP,DFHEDFP, DFHEDI, DFHEEI, DFHEGL, DFHEIACQ,DFHEIBAM, DFHEICRE, DFHEIG, DFHEIIC, DFHEIP,DFHEIPA, DFHEIML, DFHEIPI, DFHEIPRT, DFHEIPSE,DFHEIPSH, DFHEIQBA, DFHEIQBR, DFHEIQCF,DFHEIQCS, DFHEIQDF, DFHEIQDI, DFHEIQDN,DFHEIQDS, DFHEIQDU, DFHEIQD2, DFHEIQEJ,DFHEIQIR, DFHEIQML, DFHEIQMQ, DFHEIQMS,DFHEIQMT, DFHEIQPF, DFHEIQPI, DFHEIQPN,DFHEIQRL, DFHEIQRQ, DFHEIQSA, DFHEIQSC,DFHEIQSJ, DFHEIQSK, DFHEIQSL, DFHEIQSM,DFHEIQSP, DFHEIQSQ, DFHEIQST, DFHEIQSX,DFHEIQSY, DFHEIQTM, DFHEIQTR, DFHEIQTS,DFHEIQUE, DFHEIQVT, DFHEIQWB, DFHEIQWR,DFHEIQW2, DFHEIUOW, DFHEIWB, DFHEKC,DFHEMS, DFHEOP, DFHEPC, DFHEPS, DFHESC,DFHESE, DFHESN, DFHETC, DFHETL, DFHETRX,DFHFCFL, DFHMQTRU, DFHSJIN, DFHTACP, DFHTFP,DFHTIEM, DFHUEH, DFHUEM, DFHWBTC, DFHXMBR,DFHXTP, DFHZATS, DFHZNCA, DFHZNCE, DFHZTSP,DFHZXQO, DFHZXST

AEY0

ExplanationINVEXITREQ condition not handled.



System action:

User response:

Module:DFHEIP

AEY1

ExplanationINVPARTNSET condition not handled.



System action:

User response:

Module:DFHEIP

AEY2

ExplanationINVPARTN condition not handled.



System action:

User response:

Module:DFHEIP

AEY3

ExplanationPARTNFAIL condition not handled.



System action:

User response:

Module:DFHEIP

AEY6

ExplanationInternal logic error in DFHUEM. This arises when usingEXITALL to DISABLE an exit program from all exitpoints for which it has been enabled. The entire userexit table has been scanned and all associations ofthe program have been found. But the activation countfor the program in its exit program block indicatesthere should be more associations (for example, theactivation count has not been reduced to zero). The



user exit table and associated control blocks (EPBsand EPLs) are out of step and have probably beencorrupted.



Module:DFHUEM

AEY7

ExplanationNOTAUTH condition not handled.



System action:

User response:

Module:DFHEIP

AEY8

ExplanationNo DSA was found on the chain while trying to freedynamic storage for an assembler language programusing an EXEC CICS command.


User responseEnsure that the DFHEIENT, DFHEISTG, and DFHEIENDmacro invocations are correctly positioned and retry. Ifthe error persists, you will need further assistance. SeeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHEIP

AEY9

ExplanationOne of the following:

• An EXEC CICS command has been issued that is notsupported by the EXEC interface program DFHEIP.

• A transaction has issued an EXEC CICS commandwhich is supported in principle by the EXEC interfaceprogram DFHEIP, but for which the prerequisitefunction has not been included in the current CICSstart-up.

• A non-CICS command has been issued via anapplication stub (expansion of a DFHRMCAL macro),and the program DFHERM has detected that thenecessary non-CICS support is not available.

• An attempt has been made to use remote resources,but the local SYSID has been specified in an EXECCICS command, or vice versa.

• An attempt has been made to use remote resources,but ISC is not supported.

• An EXEC CICS command contains an invalid AID orCONDITION identifier. This indicates that the EXECCICS command has become corrupted.


User responseCheck that the sysid specified and the resource nameswere correct. If not, notify the system programmer.Either the command (or an application stub) hasbecome corrupted, or the unavailable function needsto be generated (CICS command), ENABLEd (non-CICScommand), or exceptionally the non-CICS support hassuffered damage and is attempting to withdraw itselffrom the CICS system.

Module:DFHEIG, DFHEIP, DFHEEI

AEYA

ExplanationINVERRTERM condition not handled.



System action:

User response:

Module:




DFHEIP

AEYB

ExplanationINVMPSZ condition not handled.



System action:

User response:

Module:DFHEIP

AEYC

ExplanationIGREQID condition not handled.



System action:

User response:

Module:DFHEIP

AEYD

ExplanationA transaction has requested that CICS access astorage area that the transaction itself could notaccess. This occurred when an invalid storage areawas passed to CICS as an output parameter on anEXEC CICS command.


User responseExamine the trace to find the exception trace entrycreated by DFHEISR and then identify the parameterin error. If the abend is handled, EXEC CICS ASSIGNASRASTG, ASRAKEY, and ASRASPC give additionalinformation about the abend. At the time of the abend,register 2 points to the storage area at fault.

Change one or more of the following:

• Correct the code in error in the transaction issuingthe EXEC CICS command in order to supply a validstorage area.

• If storage protection is active, change the EXECKEYon the CEDA definition for the program that issuedthe EXEC CICS command from USER to CICS.

• If storage protection is active, change theTASKDATAKEY attributes on the transactiondefinition from CICS to USER.

• If transaction isolation is active, change the ISOLATEattribute on the transaction definition from YES toNO.

Module:DFHSRP

AEYE

ExplanationINVLDC condition not handled.



System action:

User response:

Module:DFHEIP

AEYF

ExplanationA transaction has requested that CICS access astorage area that the transaction itself could notaccess. This occurred when an invalid storage areawas passed to CICS on a PUT CONTAINER, PUT 64CONTAINER, GET CONTAINER or GET64 CONTAINERcommand. The error can occur when:

• Either the FROM or INTO address is specifiedincorrectly.

• The FLENGTH value specifies a value large enoughto cause the area to include storage which thetransaction can not access.

A common cause of this error is specifying the addressof a halfword area in the FLENGTH parameter, whichexpects a fullword area. This error can arise whena program which previously used commareas, whichhave halfword lengths, has been modified to usecontainers which have fullword lengths.



User responseExamine the trace to find the entry trace entry createdby DFHEISR and then identify the parameter in error.If the abend is handled, EXEC CICS ASSIGN ASRASTG,ASRAKEY, and ASRASPC give additional informationabout the abend. At the time of the abend, register 2points to the storage area at fault.

You will most likely need to do the following:

• Correct the program in error that issued theEXEC CICS PUT CONTAINER or EXEC CICS GETCONTAINER command. Ensure that it supplies theaddress of a valid storage area and that it suppliesan FLENGTH such that no part of the storagearea is inaccessible to the transaction. Ensure thatFLENGTH refers to a fullword length.

You may also need to consider changing one or moreof the following:

• If storage protection is active, change the EXECKEYon the CEDA definition for the program that issuedthe EXEC CICS command from USER to CICS.

• If storage protection is active, change theTASKDATAKEY attributes on the transactiondefinition from CICS to USER.

• If transaction isolation is active, change the ISOLATEattribute on the transaction definition from YES toNO.

Module:DFHSRP

AEYG

ExplanationJIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEYH

ExplanationQIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEYJ

ExplanationDSSTAT condition not handled.



System action:

User response:

Module:DFHEIP

AEYK

ExplanationSELNERR condition not handled.



System action:

User response:

Module:DFHEIP

AEYL

ExplanationFUNCERR condition not handled.



System action:


User response:

Module:DFHEIP

AEYM

ExplanationUNEXPIN condition not handled.



System action:

User response:

Module:DFHEIP

AEYN

ExplanationNOPASSBKRD condition not handled.



System action:

User response:

Module:DFHEIP

AEYO

ExplanationNOPASSBKWR condition not handled.



System action:

User response:

Module:DFHEIP

AEYP

ExplanationSEGIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEYQ

ExplanationSYSIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEYR

ExplanationISCINVREQ condition not handled.



System action:

User response:

Module:DFHEIP

AEYT

ExplanationENVDEFERR condition not handled.



System action:

User response:

Module:DFHEIP


AEYU

ExplanationIGREQCD condition not handled.



System action:

User response:

Module:DFHEIP

AEYV

ExplanationSESSIONERR condition not handled.



System action:

User response:

Module:DFHEIP

AEYX

ExplanationUSERIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEYY

ExplanationNOTALLOC condition not handled.



System action:

User response:

Module:DFHEIP

AEYZ

ExplanationCBIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZA

ExplanationA transaction has been defined with aTASKDATALOC(ANY), but the programs within thetransaction are running amode 24. The exec interfaceprogram is therefore is unable to access the TCA forthe application. Furthermore, any reference to theEIB would cause the transaction to fail with an OC4protection exception.

System actionThe transaction is abnormally terminated.

User responseEither redefine and install a new definition for thetransaction with TASKDATALOC(BELOW), or relink theprograms as amode 31.

Module:DFHEIP

AEZB

ExplanationA transaction has been defined with aTASKDATALOC(ANY), and the application is attemptingto call a task related user exit. However the taskrelated user exit has been linkedited AMODE 24and enabled with the LINKEDITMODE option, therebydirecting CICS to invoke it in AMODE 24. An AMODE24 task related user exit cannot run when the callingapplication is running with TASKDATALOC(ANY), as


this would cause a protection exception, or a storageoverwrite.


User responseEither redefine and install a new definition for thetransaction with TASKDATALOC(BELOW), or modify thetask related user exit so that it is invoked in AMODE31.

Module:DFHERM

AEZC

ExplanationA transaction has been defined with aTASKDATALOC(ANY), but a program within thetransaction is defined to run AMODE 24. CICS cannotinvoke the AMODE 24 program when the transaction isrunning with TASKDATALOC(ANY), as this would causea protection exception, or a storage overwrite.


User responseEither redefine and install a new definition for thetransaction with TASKDATALOC(BELOW), or relink theprogram as AMODE 31.

Module:DFHAPLI

AEZD

ExplanationAn attempt has been made to run a programdefined as EXECKEY(USER) as part of a transactiondefined as TASKDATAKEY(CICS). These attributes areincompatible and the transaction is abended. Thisincompatibility could occur as a result of the programdefinition being autoinstalled. See the Developingsystem programs for CICS and the Defining resourcesfor more information about program autoinstall.

System actionThe transaction is abnormally terminated. MessageDFHAP1226 will show the incompatible program andtransaction.

User responseRedefine and install a new definition either for thetransaction with TASKDATAKEY(USER), or for theprogram with EXECKEY(CICS).

If this abend occurs when running a CICS transaction,a possible cause is that you are not using the CICS-supplied definition for the program. If you are usingyour own copies of CICS-supplied program definitions,they must be defined as EXECKEY(CICS).

Module:DFHAPLI

AEZE

ExplanationCHANGED condition not handled.



System action:

User response:

Module:DFHEIP

AEZF

ExplanationPROCESSBUSY condition not handled.



System action:

User response:

Module:DFHEIP

AEZG

ExplanationACTIVITYBUSY condition not handled.



System action:


https://www.ibm.com/support/knowledgecenter//system-programming/developing_sysprogs.html


https://www.ibm.com/support/knowledgecenter//configuring/resources/dfha22v.html

User response:

Module:DFHEIP

AEZH

ExplanationPROCESSERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZI

ExplanationACTIVITYERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZJ

ExplanationCONTAINERERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZK

ExplanationEVENTERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZL

ExplanationTOKENERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZM

ExplanationNOTFINISHED condition not handled.



System action:

User response:

Module:DFHEIP

AEZN

ExplanationPOOLERR condition not handled.



System action:

User response:

Module:DFHEIP


AEZO

ExplanationTIMERERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZP

ExplanationSYMBOLERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZQ

ExplanationTEMPLATERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZR

ExplanationNOTSUPERUSER condition not handled.



System action:

User response:

Module:DFHEIP

AEZS

ExplanationCSDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZT

ExplanationDUPRES condition not handled.



System action:

User response:

Module:DFHEIP

AEZU

ExplanationRESUNAVAIL condition not handled.



System action:

User response:

Module:DFHEIP

AEZV


ExplanationCHANNELERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZW

ExplanationCCSIDERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZX

ExplanationTIMEDOUT condition not handled.



System action:

User response:

Module:DFHEIP

AEZY

ExplanationCODEPAGEERR condition not handled.



System action:

User response:

Module:DFHEIP

AEZZ

ExplanationINCOMPLETE condition not handled.



System action:

User response:

Module:DFHEIP

AEZ1

ExplanationAPPNOTFOUND condition not handled.



System action:

User response:

Module:DFHEIP

AEZ2

ExplanationBUSY condition not handled.



System action:

User response:

Module:DFHEIP


AFxx abend codesAFC0

ExplanationAn attempt has been made to update a file after filecontrol restart failed.


User responseDetermine the cause of the failure in file controlrestart. Restart CICS.

Module:DFHEIFC, DFHDMPCA

AFC2

ExplanationDFHFCU issued a call to DFHFCFS to open a file. Adisastrous error was returned from DFHFCFS.


At the time the disastrous error is detected, CICSwrites a message to the console, records an exceptiontrace entry and takes a system dump.

CICS processing continues.

User responseThe system programmer should examine the trace,the system dump and any related CICS messages toidentify the cause of the error.

Module:DFHFCU

AFC7

ExplanationThe CICS definition file (CSD) manager (DFHDMPCA)issued a request to DFHFCFS to enable, open or closethe DFHCSD file. A "disastrous error" response wasreturned from DFHFCFS to DFHDMPCA.


At the time the disastrous error is detected, CICSwrites a message to the console, records an exceptiontrace entry and takes a system dump.

CICS processing continues.

User responseThe system programmer should examine the trace,the system dump and any related CICS messages toidentify the cause of the error.

Module:DFHDMPCA

AFCB

ExplanationModule DFHEIFC issued a resource level securitycheck (RSLC) request to module DFHXSRC andreceived a response other than OK or EXCEPTION.


User responseExamine the trace to find the exception trace entrycreated by DFHXSRC at the time of the error. Use thistrace entry to determine the cause of the return codefrom DFHXSRC.

Module:DFHEIFC

AFCC

ExplanationAn internal logic error was detected when callingthe file control request processing module DFHFCFR.Either DFHFCFR returned an INVALID response to itscaller indicating an error in the caller's parameter list,or DFHFCFR passed back a return code that was notrecognized by its caller.





AFCE

ExplanationA GETMAIN for FFLE storage has failed.


User responseRetry the failed transaction.

Module:DFHEIFC

AFCF

ExplanationA deadlock has been detected between two or moretasks issuing file control requests.

System actionThe task that would have entered deadlock is abendedwith a CICS transaction dump.

User responseExamine this transaction and other transactions in thesystem that update the same files to find the cause ofthe deadlock, then correct the error.

When transactions update several files within thesame unit of work, all transactions should updatethese files in the same order. A transactionthat abends AFCF may be retried by specifyingRESTART(YES) in the transaction definition and bycoding a suitable DFHREST program.


AFCG

ExplanationA transaction has issued a sequence of file controlrequests that would cause the file to deadlock itself.

This response arises for different reasons dependingupon the file type.

If the file is being accessed in non-RLS mode,the response is caused by the transaction makingconflicting requests against the same CI. For example,if the file is being accessed using LSR, a self deadlockwill arise when an attempt is made to read a recordthat is in the same CI as a record that is the subjectof a READ UPDATE or WRITE MASSINSERT requestissued by the same transaction.

If the file is accessed in RLS mode there is no CIlocking, but self deadlock responses can still arise.They are caused by sequences of requests thatare either logically meaningless or which cannot beperformed by VSAM RLS.

With VSAM RLS the most likely causes of this abendare as follows:

• Two successive READ UPDATE requests againstthe same record by the same transaction withoutan intervening REWRITE, DELETE or UNLOCKcommand.

This is an incorrect use of file control requests.• A transaction has created a record by WRITE

MASSINSERT and then, without terminating theWRITE MASSINSERT sequence by issuing anUNLOCK request, the same transaction hasattempted to modify the same record by issuing aREAD UPDATE or DELETE request.

This sequence of requests fails if VSAM has notwritten the record out to disk. The only way toguarantee that the record has been written to diskis to issue the UNLOCK request.

• A transaction has updated or deleted a record usinga browse for update sequence and then, withoutterminating the browse for update sequence byissuing an ENDBR request, the same transaction hasattempted to modify the same record by issuinga separate READ UPDATE or DELETE or WRITErequest.

This sequence of requests fails if VSAM has notwritten the record out to disk. The only way toguarantee that the record has been written to diskis to issue the ENDBR request.

If the file is used to access a coupling facilitydata table, then self deadlock responses are causedby sequences of requests that are either logicallymeaningless or which cannot be performed bycoupling facility data tables support.

For coupling facility data tables, the most likely causeof this abend is as follows:

• Two successive READ UPDATE requests havebeen issued against the same record by the



same transaction without an intervening REWRITE,DELETE or UNLOCK command.

This is an incorrect use of file control requests.

System actionThe task that would have entered deadlock is abendedwith a CICS transaction dump.

User responseExamine the previous requests made by thistransaction against this file to identify the causeof the deadlock, then correct the error. In somecases (particularly when the file is being accessed inRLS mode or is using a coupling facility data table)this abend may indicate a programming error in theprogram that issued the file control requests.

When the file is being accessed in RLS mode,if the programming error is a READ UPDATEwith RIDFLD specified followed by a DELETE withRIDFLD specified, consider using the feature togglecom.ibm.cics.rls.delete.ridfld to allow the DELETE withRIDFLD command to succeed. This is intended as amigration aid when you are converting to RLS fromlocal VSAM with CILOCK=NO specified in CICS. Formore information, see VSAM RLS.


AFCH

ExplanationThe transaction has issued a request for a remoteshared data table for which it has an active browse,but in the meantime the table has been disabled orclosed by the owning CICS system, or the owning CICSsystem has failed.



User responseIn the application owning region, take whatever actionnormally follows the issue of a FORCE request in, orthe failure of, the file owning CICS system.

See the Introduction to shared data tables for furtherguidance.

Module:DFHEIFC

AFCI

ExplanationThe transaction issued a file request resulting in a callto the main file control program (DFHFCFR). During theprocessing of the request the transaction was purged.That is, the transaction was the subject of an explicitPURGE or FORCEPURGE request, was timed out, orwas selected by CICS for termination in an attempt toalleviate an SOS condition.

System actionA CICS transaction dump is issued with abend codeAFCI.

A "purged" response is returned from DFHFCFR to itscaller. The transaction issuing the file control requestwill eventually issue an AFCY abend with a furthertransaction dump.

User responseIn some instances, for example if the transaction wasexplicitly purged, no further action is necessary.

Otherwise examine the exception trace and thetransaction dump to identify the point at which thepurge occurred.

Module:DFHFCFR

AFCJ

ExplanationDFHFCU issued a call to DFHFCFS to open a file. Apurged error was returned from DFHFCFS because thetask has been waiting for a resource longer than theDTIMEOUT interval specified for the CSFU transaction.

System actionThe task is abnormally terminated with a CICStransaction dump. CICS processing continues.

User responseExamine the dump to determine the cause of theerror. A system dump can be produced by adding theappropriate dump table entry using the CEMT SETTRDUMPCODE command.

Module:DFHFCU

AFCK


https://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/configuring/parallel-sysplex/vsam_rls.html

https://www.ibm.com/support/knowledgecenter//fundamentals/database/dfhf10w.html

ExplanationThe transaction issued a file update request (READUPDATE, WRITE or DELETE) against an RLS mode dataset for which a DFSMSdss non-BWO backup was inprogress.

System actionThe transaction is abnormally terminated with a CICStransaction dump. CICS processing continues.

User responseAll new file update requests are prohibited when anon-BWO backup is in progress for an RLS mode dataset. This restriction is automatically lifted when thebackup completes. (A non-BWO backup is any typeof backup operation other than a Backup While Openbackup.) When the backup has completed, retry thetransaction.

Module:DFHDMPCA, DFHEIFC

AFCL

ExplanationDuring the loading of a Shared Data Table by the CFTLtransaction, a call to the CICS Transaction Managerhas returned a response (such as DISASTER) afterwhich normal processing could not continue.

System actionMessage DFHFC0949 is issued. Loading of the datatable is terminated and CFTL abends.

User responseRefer to the description of the message for furtherinformation and guidance.

Module:DFHDTLX

AFCM

ExplanationDuring the loading of a data table by the CFTLtransaction, an abend was detected, or a domain callreturned a response (such as DISASTER) after whichnormal processing could not continue.

System actionA message is issued (one of DFHFC0945, DFHFC0946,or DFHFC0947). Loading of the data table isterminated and CFTL abends.

User responseIf this abend is produced as a result of an abend duringloading, message DFHFC0945 is issued. If it is a resultof a domain call failure, depending on which domainthe failure was returned by, one of the messagesDFHFC0946 or DFHFC0947 is issued. Refer to thedescription of the message for further information andguidance.

Module:DFHDTLX

AFCN

ExplanationThe transaction issued a file request that caused filecontrol to attempt to create a journal record butthe record was too large for the journal buffer toaccommodate. This indicates that a journal referencedin the file definition is using an MVS logstream, whichin turn, is using a coupling facility structure which hasbeen defined with a MAXBUFSIZE parameter less thanthe recommended 64000.


User responseRedefine the coupling facility structure that thelogstream is using with a MAXBUFSIZE parameterof 64000. The journal in error can be the forwardrecovery log or the journal used for auto-archiving.If the module that detected the error is DFHDMPCA,the error is associated with a journal referenced in thedefinition of the CSD (DFHCSD).


AFCO

ExplanationAn attempt was made to attach a transactionspecifying DFHDTLX as the program to be givencontrol, but the transaction was not internally attachedby CICS.

DFHDTLX is for use by CICS system transaction CFTL.This loads a Shared Data Table.



User responseEstablish why an attempt was made to attach CFTLillegally, or why a transaction definition specifiedDFHDTLX as the program to be given control.

Module:DFHDTLX

AFCR

ExplanationThe program issued a file control request against afile opened in RLS mode. While executing this request,CICS detected that the SMSVSAM server addressspace had failed.


CICS disables all further RLS accesses and initiateserror recovery.

User responseRetry the transaction when the server is availableagain

If the SMSVSAM server fails, it should normallyautomatically restart itself as quickly as possible.If this does not happen, consult the VSAMdocumentation which provides further guidance ondebugging problems in the SMSVSAM server.


AFCS

ExplanationThe program issued a file control request against a fileopened in RLS mode. VSAM was unable to perform thisrequest because the SMSVSAM server address spacewas inactive.

However, if an offsite restart is being performed(that is, OFFSITE=YES was specified as a systeminitialization override), this transaction abend is alsoissued even if the SMSVSAM server address spaceis active. This is because RLS access is not allowedduring an offsite restart for any RLS file controlrequests other than those issued by transactions

which have been attached by CICS to perform RLSrecovery work.


User responseRetry the transaction when the server is availableagain.

If the SMSVSAM server fails, it should normallyautomatically restart itself as quickly as possible.If this does not happen, consult the VSAMdocumentation which provides further guidance ondebugging problems in the SMSVSAM server.

If an offsite restart is being performed, retry thetransaction after RLS recovery has been completedwhen RLS access by user transactions is allowedagain.


AFCT

ExplanationThe program has made a file control request againsta file opened in RLS mode. The SMSVSAM server hasbeen recycled since an earlier RLS request from thesame unit of work. The same unit of work cannotissue requests against two different instances of theSMSVSAM server. Note that this abend will occur evenif the earlier request was not successful.


User responseResubmit the transaction.


AFCU

ExplanationA program made a file control request against afile that is being accessed in VSAM RLS mode. Theunderlying data set is in lost locks state. File controlrequests are not allowed against a data set that is inlost locks state.



User responseRecovery from lost locks is normally automatic. Seethe Administering recovery and restart for a fullexplanation of lost locks recovery. You will not be ableto issue any file control requests against this data setuntil all systems that owned locks at the time of thelock structure failure have completed their lost locksrecovery.

See the Administering recovery and restart forguidance on how to determine which CICS systemsstill have lost locks recovery pending, for informationon commands that allow you to find the work thatthese systems have outstanding, and on commandsthat allow you to force a system to immediatelycomplete lost locks recovery. The commands thatforce immediate completion of lost locks recoveryshould only be used as a last resort as they may causeloss of data integrity. It is better to allow the automaticrecovery procedures to complete normally.


AFCV

ExplanationA request made against a file opened in RLS mode wasunable to acquire a record lock. It waited for the lock,but the wait time exceeded the maximum wait timeapplicable to that request.


CICS prints message DFHFC0164 and message(s)DFHFC0165 or DFHFC0175 which identify thetransaction(s) or Transactional VSAM unit(s) ofrecovery that were immediately in front of thistransaction in the queue for the lock. Normallythese transaction(s) or Transactional VSAM unit(s) ofrecovery are the owners of the lock, although this isnot the case if a chain of requests for the record hasbuilt up.

User responseRetry the transaction.

If the problem recurs, see messages DFHFC0164and DFHFC0165 or DFHFC0175 to determine thetransaction or Transactional VSAM unit of recovery

that is holding the lock. In most cases the problem lieswith the lock owner rather than the transaction thathas failed.

Examples of reasons why CICS transactions maycause a timeout:

• The transaction that holds the lock has a designerror. For example:

– A conversational transaction updates arecoverable record and then issues a terminalcontrol read. It does not issue syncpoint (andtherefore does not release the lock) until the enduser has responded to the terminal control read.It may therefore hold the lock for a considerableperiod.

– A transaction updates very many records inrecoverable files before issuing syncpoint. You arerecommended to keep the number of updatesmade within a unit of work small and to issuefrequent syncpoints to ensure that locks arereleased regularly.

• The system in which the lock holder is runningis experiencing severe performance degradation.Investigate the reason for the performancedegradation.

• There is a deadlock between RLS and anotherresource manager. For example one transaction maybe holding an RLS lock and waiting for a lock ona transient data queue. The transaction that timesout may hold the lock on the transient data queueand be waiting for the RLS lock. RLS can detectdeadlocks only when all the locks involved in thedeadlock are RLS locks. A deadlock such as thiscan appear to RLS to be a long wait for a lockand is reported as a time out. Examine the designof the transactions to determine whether resourcemanager deadlocks can occur.

• It may be possible for RLS deadlocks to bereported as RLS timeouts if VSAM does notperform deadlock detection until after the timeout value for the request occurred. For example,assume that DEADLOCK_DETECTION is specifiedas (15,4) in SYS1.PARMLIB, member IGDSMSxx.This means that VSAM does not attempt to detectcross-MVS deadlocks until 4 periods of 15 (that is,60) seconds have elapsed. If DTIMOUT was notactive for the transaction and the SIT specifiedFTIMEOUT=30, the RLS request times out after30 seconds, before VSAM has attempted to detectcross-MVS deadlocks. Adjust FTIMEOUT, DTIMOUT,and DEADLOCK_DETECTION to avoid such effects.

DFHFC0175 messages identify Transactional VSAMunits of recovery owning an RLS lock. If a TransactionalVSAM application is the lock owner it should beinvestigated to determine why it is holding the lock.




Some of the above considerations will be similar forTransactional VSAM applications.


AFCW

ExplanationThe program issued a file control request against afile opened in RLS mode. VSAM RLS detected that thisrequest would cause a deadlock. This transaction isabended in order to break the deadlock chain.


CICS prints message DFHFC0166 and message(s)DFHFC0167 or DFHFC0177 which identify the othertransactions or Transactional VSAM units of recoveryin the deadlock chain.

User responseRetry the transaction.

Examine the logic of all the programs involved in thedeadlock chain to determine whether they could beimproved to avoid possible sources of deadlock. Seethe Developing CICS Applications for guidance on howto write programs that avoid deadlocks.


AFCY

ExplanationThe transaction issued a file request resulting in a callto the main file control program (DFHFCFR). Duringthe processing of the request the transaction waspurged (that is, was the subject of an explicit PURGE orFORCEPURGE request, was timed out, or was selectedby CICS for termination in an attempt to alleviate anSOS condition). A "purged" response was returnedfrom DFHFCFR to its caller.


Exception trace entries are made between the pointat which the purge is detected and the issuing of theabend.

If a task times out while waiting for a lock on arecord in a coupling facility data table, CICS will issue

message DFHFC7130 identifying the key of the lockedrecord and the system and unit of work that owns thelock.

A transaction dump with abend code AFCI is takenwhen the purged response is detected by DFHFCFR.

User responseIn some instances, for example if the transaction wasexplicitly purged, no further action is necessary.

If using a coupling facility data table, look for anyrelevant DFHFC7130 messages.

Otherwise examine the exception trace and the AFCI/AFCY transaction dumps to identify the point at whichthe purge occurred.


AFCZ

ExplanationThe transaction issued a file request resulting ina call to the main file control program (DFHFCFR).A "disastrous error" response was returned fromDFHFCFR to its caller.

System actionAt the time the error is detected, CICS writes amessage to the console, records an exception traceentry, and takes a system dump. The trace and dumpidentify the point of error.

Subsequently, the task is abnormally terminated with aCICS transaction dump.

User responseThe system programmer should use the trace anddumps to determine what the error is, and why it hasoccurred.


AFDA

ExplanationAn attempt was made to attach a transactionspecifying DFHFCQT as the program to be givencontrol, but the transaction was not internally attachedby CICS.

DFHFCQT is for use by CICS system transactionsCFQS and CFQR. These provide support for VSAM RLSdata set quiesce and unquiesce operations, DFSMSdss



BWO and non-BWO backups, and certain other dataset related operations.


User responseEstablish why an attempt was made to illegallyattach CFQS or CFQR, or why a transaction definitionspecified DFHFCQT as the program to be given control.

Module:DFHFCQT

AFDB

ExplanationAn attempt was made by CICS to internally attach atransaction specifying DFHFCQT as the program to begiven control, and the transaction id was other thanCFQS or CFQR.

DFHFCQT is for use by CICS system transactionsCFQS and CFQR. These provide support for VSAM RLSdata set quiesce and unquiesce operations, DFSMSdssBWO and non-BWO backups, and certain other dataset related operations.

System actionThe transaction is abnormally terminated with a CICStransaction dump. CICS processing continues but it isprobable that VSAM RLS data set quiesce support hasbeen lost.

User responseRestart CICS. If the problem reoccurs, a moresevere error is indicated. In this case, you will needassistance from IBM. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHFCQT

AFDC

ExplanationCICS system transaction CFQS has failed due to aserious error. An attempt will be made to reattach thetransaction. CICS messages should indicate the causeof the error.

CFQS provides support for the initiation of VSAM RLSdata set quiesce and unquiesce operations.

System actionCFQS is abnormally terminated with a CICStransaction dump. CFQS is reattached and CICSprocessing continues.

User responseCheck Transient Data Queue CSFL for messageDFHFC6028, indicating that the reattach of CFQS wassuccessful. If the reattach fails, VSAM RLS data setquiesce initiation support is lost. If this support isrequired, CICS must be restarted.

If it is not possible to restore VSAM RLS quiesceinitiation support, a more severe error is indicated.In this case, you will need assistance from IBM. SeeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHFCQT

AFDD

ExplanationCICS system transaction CFQR has failed due to aserious error. An attempt will be made to reattach thetransaction. CICS messages should indicate the causeof the error.

CFQR provides support for VSAM RLS data set quiesceand unquiesce operations, DFSMSdss BWO and non-BWO backups, and certain other data set relatedoperations.

System actionCFQR is abnormally terminated with a CICStransaction dump. CFQR is reattached and CICSprocessing continues.

User responseCheck Transient Data Queue CSFL for messageDFHFC6028, indicating that the reattach of CFQR wassuccessful. If the reattach fails, VSAM RLS data setquiesce support is lost. If this happens, CICS must berestarted.

If it is not possible to restore VSAM RLS quiescesupport, a more severe error is indicated. In this case,you will need assistance from IBM. See Working withIBM to solve your problem for guidance on how toproceed.

Module:DFHFCQT

AFDE







ExplanationAn attempt was made to attach a transactionspecifying DFHFCRD as the program to be givencontrol, but the transaction was not internally attachedby CICS.

DFHFCRD is for use by CICS system transaction CSFR.This provides support for error recovery after a failureof the SMSVSAM server.


User responseEstablish why an attempt was made to illegallyattach CSFR, or why a transaction definition specifiedDFHFCRD as the program to be given control.

Module:DFHFCRD

AFDF

ExplanationAn attempt was made to attach a transactionspecifying DFHFCOR as the program to be givencontrol, but the transaction was not internally attachedby CICS.

DFHFCOR is for use by CICS system transaction CFOR.This provides part of the RLS offsite recovery support.


User responseEstablish why an attempt was made to illegallyattach CFOR, or why a transaction definition specifiedDFHFCOR as the program to be given control.

Module:DFHFCOR

AFDG

ExplanationCICS system transaction CFOR has failed due to aserious error. CICS messages should indicate thecause of the error.

DFHFCOR provides part of the RLS offsite recoverysupport.

This abend indicates that this CICS system hascompleted its RLS offsite recovery, but an erroroccurred either in attempting to issue messageDFHFC0575D which reports this fact, or in attemptingto process the reply to message DFHFC0575D.

System actionCFOR is abnormally terminated with a CICStransaction dump. CICS processing continues.

User responseIf you are using an automated procedure to checkfor and reply to message DFHFC0575D, then youshould shut this CICS down and restart it specifyingOFFSITE=YES again. If you are using manualprocedures to check for completion of all RLS offsiterecovery and to reply to message DFHFC0575D thenyou can "tick" this CICS off the list of systems whichhave completed their recovery, but you must ensurethat it is not restarted with OFFSITE=NO until allother CICS systems have completed their RLS offsiterecovery. Also note that until the system is restarted,RLS access will not be allowed by this system.

Module:DFHFCOR

AFDH

ExplanationVSAM has returned a response indicating that the RLSlock structure in the coupling facility is full. VSAM RLSis unable to create any new locks.

This abend code is usually issued from various CICSsystems residing within the same sysplex.

System actionThe transaction which issued the VSAM RLS request isabnormally terminated with a CICS transaction dump.CICS processing continues.

User responseAllocate a larger VSAM RLS lock structure and rebuildthe RLS structure into the new larger structure. Seez/OS MVS Setting up a Sysplex, (GC28-1779) andz/OS DFSMSdfp Storage Administration, (SC26-4920)for further details on creating RLS lock structures andrebuilding lock structures.


AFDI


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaf100/abstract.htm

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idas200/abstract.htm

ExplanationA call to directory domain failed when trying to locatean fct entry.



Module:DFHFCU

AFDJ

ExplanationA call to lock manager failed when trying to locate anfct entry.



Module:DFHFCU

AFDK

ExplanationA file control update request was made against anNSR file whilst transaction isolation was active for thetask. Using NSR files with transaction isolation activeis not supported. The TRANISO SIT parm is YES andthe transaction definition has ISOLATE set to YES.


User responseIf transaction isolation is required, consider convertingthe file to use LSR pools or RLS. However,if transaction isolation is not required, anotheroption is to change the transaction definition tospecify ISOLATE(NO) which will cause that individualtransaction to be run without transaction isolation.Examine the dump to determine the cause of theerror. A system dump can be produced by adding theappropriate dump table entry using the CEMT SETTRDUMPCODE command.


AFDL

ExplanationA file control update request was made but thetask has already updated a file that uses a differentreplication log stream.


User responseUsing multiple replication log streams for onetransaction causes data integrity issues on the mirrorsite. This abend affects only transactions that updatetwo different recoverable files in the same unitof work. Review your replication setup to ensurethat data sets cannot be updated by differentsubscriptions. If the replication setup meets thisrequirement, update the LOGSTREAMID on the dataset definition so that it uses the correct log stream.A system dump can be produced by adding theappropriate dump table entry using the CEMT SETTRDUMPCODE command.

Module:DFHEIFC

AFDN

ExplanationA program has issued a file control request with anunrecognised request type.




Module:DFHEIFC

AFDO

Explanation

An attempt was made to attach a transactionspecifying DFHFCRN as the program to be givencontrol, but the transaction was not internally attachedby CICS.

DFHFCRN is for use by CICS system transaction CFCR.This transaction is used to disable a file defined in aCICS bundle.


User responseEstablish why an attempt was made to inappropriatelyattach CFCR, or why a transaction definition specifiedDFHFCRN as the program to be given control.

Module:DFHFCRN

AFDP

Explanation

CICS failed to disable a file defined in a CICS bundle.


User responseEstablish why the file cannot be disabled, fix the issue,and try to disable the bundle again.

Module:DFHFCRN

AFDQ

Explanation

An attempt has been made to start transaction CFCTmanually which is not supported.


User responseEstablish why an attempt has been made tostart transaction CFCT manually. This transaction isautomatically attached by CICS at startup.

Module:DFHFCLJ1

AGxx abend codeAGMA

ExplanationAn attempt to initiate the good morning message transaction was made without specifying a termid for it to bedisplayed.

System actionThe transaction is abnormally terminated with a CICS transaction dump.



User responseUse the dump to determine how the attempt to start the transaction was made. Ensure that no EXEC CICSSTARTs are made for the good morning message transaction where no termid is specified.

Module:DFHGMM

AIxx abend codesAICA

ExplanationA task has been executing for longer than the runawaytime interval (defined by the ICVR operand on thesystem initialization table macro, DFHSIT) withoutgiving up control. The runaway task condition indicatesa possible loop in the application.

System actionThe task is terminated with an AICA transaction dump.

User responseSee the Troubleshooting and support for guidance ondealing with loops.

Module:DFHSRP

AICB

ExplanationA RETRIEVE WAIT request has been reissued insystem shutdown.


User responseNone

Module:DFHICP

AICC

ExplanationAn incorrect response was returned from a timer (TI)domain request.



Module:DFHTAJP, DFHICP

AICD

ExplanationA incorrect response was returned from a kernel (KE)domain request.



Module:DFHICP

AICE

ExplanationAn incorrect response was returned from a dispatcher(DS) domain request (other than AICG).







Module:DFHICP

AICF

ExplanationAn incorrect response was returned from a transactionmanager (TM) domain request.



Module:DFHICP

AICG

ExplanationA PURGED response was returned from a dispatcherdomain (DS) request, with a reason code ofTASK_CANCEL. TASK_CANCEL was returned as thetransaction had been explicitly cancelled.


User responseNotify your system programmer to determine why thetask has been purged.

Module:DFHICP

AICH






Module:DFHICP, DFHEIIC

AICJ




Module:DFHICP, DFHEIIC

AICK

ExplanationModule DFHEIIC has issued a resource level securitycheck (RSLC) request to module DFHXSRC andreceived a response other than OK or EXCEPTION.





User responseExamine the trace to find the exception trace entrycreated by DFHXSRC at the time of the error. Use thistrace entry to determine the cause of the return codefrom DFHXSRC.

Module:DFHEIIC

AICL

ExplanationDFHEIIC detected an invalid function code in thecommand level parameter list. This is caused eitherby a storage overwrite or a CICS internal logic error.


User responseIf this problem is reproducible, a level 1 trace of the ICand EI components would aid problem determination.Look in the program storage section of the transactiondump and compare argument 0, the exec interfacedescriptor (EID), for the command being processedwith the argument 0 produced by the translatorfor the same command. Any differences mean thatan overwrite of the application program may haveoccurred. If you need further assistance from IBM toresolve this problem, see Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHEIIC

AICN

ExplanationAn incorrect response has been returned from a userdomain (US) request.



Module:DFHICP

AICO

ExplanationAn unexpected EXCEPTION response was receivedfrom a call to the user (US) domain.

The call was issued during initialization of atransaction that was started without a terminal. Thecall was made as part of processing to associate thetransaction with its intended user. The attempt toassociate the intended user with the transaction hasfailed.

The userid for the intended user of the transactionmay not be correctly defined.


User responseDetermine why the intended user of the transaction isnot correctly defined.

Examine messages produced for the CICS job by theexternal security manager (ESM). This may require theassistance of a security administrator.


When the user has been correctly defined, considerrerunning the transaction.

Module:DFHICXM

AICQ

ExplanationModule DFHDFST is executing at a terminal which isnot permitted.






User responseDetermine why this transaction is executing at aterminal.

Module:DFHDFST

AICR

ExplanationA DFHTC write request has failed for IRC. The returncodes within TCATPAPR and TCTEIRET should beexamined to determine the cause of failure.

System actionThe CSNC transaction is abnormally terminated with aCICS transaction dump.


Module:DFHCRR

AICS

ExplanationModule DFHDFST has encountered an error duringRetrieve processing.


User responseUse level 1 trace entries to determine the cause of thefailure.

Module:DFHDFST

AICT

ExplanationModule DFHDFST has encountered an error duringSTART processing.


User responseUse level 1 trace entries to determine the cause of theerror.

Module:DFHDFST

AIEA

ExplanationAn unexpected EXCEPTION response was receivedfrom a call to the user (US) domain.

The call was issued during initialization of atransaction that was started without a terminal. Thecall was made as part of processing to associate thetransaction with its intended user. The attempt toassociate the intended user with the transaction hasfailed.



User responseDetermine why the intended user of the transaction isnot correctly defined.

Examine messages produced for the CICS job by theexternal security manager (ESM). This may require theassistance of a security administrator.


When the user has been correctly defined, considerrerunning the transaction.

Module:DFHIEXM

AIEB

ExplanationThe transaction id (CIEP) of the ECI for TCP/IP listenertask has been initiated invalidly, probably by enteringthe id at a terminal. This transaction must only beinitiated by CICS internal processes.




User responseDo not initiate CIEP directly.

Module:DFHIEP

AINA

ExplanationAn application program has issued an EXEC CICSLINK command to the indoubt testing tool programDFHINDT but has failed to pass a commareacontaining the request to be executed. Valid requestsare: ON, OFF, RESYNC COMMIT or RESYNC BACKOUT.


User responseCorrect the application program so that it passes acommarea to DFHINDT containing a valid request forDFHINDT.

Module:DFHINDT

AINB

ExplanationAn application program has issued an EXEC CICSLINK command to the indoubt testing tool programDFHINDT passing a commarea that did not contain avalid request to be executed, Valid requests are: ON,OFF, RESYNC COMMIT or RESYNC BACKOUT


User responseCorrect the application program so that it passes acommarea to DFHINDT containing a valid request forDFHINDT.

Module:DFHINDT

AINC

ExplanationThe indoubt testing tool issued a EXEC CICS INQUIREEXITPROGRAM command to inquire on the status of

the indoubt testing tool task related user exit programDFHINTRU, and the command failed with a NOTAUTHresponse.


User responseThe indoubt testing tool can be run under transactionCIND , under a user transaction where the programEXEC CICS LINKs to DFHINDT. or under a transactionwhere the program EXEC CICS LINKs to DFHINDAP.If command security checking is active for thetransaction (CMDSEC=YES), check that the userhas read access to resource EXITPROGRAM. Ifresource security checking is active for the transaction(RESSEC=YES), check that the user has read access toresource DFHINTRU.

Module:DFHINDT, DFHINDAP

AIND

ExplanationThe indoubt testing tool issued a EXEC CICS INQUIREEXITPROGRAM command to inquire on the statusof the indoubt testing tool task related user exitprogram DFHINTRU, and the command failed with anunexpected response.




AINE

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anSTART_LINK_BROWSE command issued by theindoubt tool to recovery manager (RM) domain. Forerrors other than EXCEPTION, the RM domain providesan exception trace, a console message, and possibly a



system dump (depending on the options in the dumptable).

For all errors, DFHINDT provides an exception trace,console message DFHAP0002, and possibly a systemdump (depending on the options in the dump table).



Module:DFHINDT

AINF

ExplanationAn EXCEPTION response with an unexpected reasonoccurred on an GET_NEXT_LINK call issued by theindoubt testing tool to recovery manager (RM) domain.DFHINDT provides an exception trace, consolemessage DFHAP0002, and possibly a system dump(depending on the options in the dump table).



Module:DFHINDT

AING

ExplanationAn error (DISASTER, INVALID, KERNERROR, orPURGED) has occurred on an GET_NEXT_LINK callissued by the indoubt testing tool to recovery manager(RM) domain. The RM domain provides an exceptiontrace, a console message, and possibly a system dump(depending on the options in the dump table).

DFHINDT also provides an exception trace, consolemessage DFHAP0002, and possibly a system dump(depending on the options in the dump table).



Module:DFHINDT

AINH

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anEND_LINK_BROWSE command issued by the indoubttool to recovery manager (RM) domain. For errorsother than EXCEPTION, the RM domain provides anexception trace, a console message, and possibly asystem dump (depending on the options in the dumptable).




Module:DFHINDT

AINI

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anINQUIRE_UOW command issued by the indoubttesting tool to recovery manager (RM) domain. Forerrors other than EXCEPTION, the RM domain providesan exception trace, a console message, and possibly asystem dump (depending on the options in the dumptable).









Module:DFHINDT

AINJ

ExplanationAn EXCEPTION response with an unexpected reasonoccurred on an INITIATE_RECOVERY call issuedby the indoubt testing tool to recovery manager(RM) domain. DFHINDT provides an exception trace,console message DFHAP0002, and possibly a systemdump (depending on the options in the dump table).



Module:DFHINDT

AINK

ExplanationAn error (DISASTER, INVALID, KERNERROR, orPURGED) has occurred on an INITIATE_RECOVERYcall issued by the indoubt testing tool to recoverymanager (RM) domain. The RM domain provides anexception trace, a console message, and possibly asystem dump (depending on the options in the dumptable).

DFHINDT also provides an exception trace, consolemessage DFHAP0002, and possibly a system dump(depending on the options in the dump table).



Module:DFHINDT

AINL

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anSET_RECOVERY_STATUS command issued by theindoubt testing tool to recovery manager (RM) domain.For errors other than EXCEPTION, the RM domainprovides an exception trace, a console message, andpossibly a system dump (depending on the options inthe dump table).




Module:DFHINDT

AINM

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anTERMINATE_RECOVERY command issued by theindoubt testing tool to recovery manager (RM) domain.For errors other than EXCEPTION, the RM domainprovides an exception trace, a console message, andpossibly a system dump (depending on the options inthe dump table).









Module:DFHINDT

AINN

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anADD_LINK command issued by the indoubt testingtool to recovery manager (RM) domain. For errorsother than EXCEPTION, the RM domain provides anexception trace, a console message, and possibly asystem dump (depending on the options in the dumptable).

For all errors, DFHINTRU provides an exception trace,console message DFHAP0002, and possibly a systemdump (depending on the options in the dump table).



Module:DFHINTRU

AINO

ExplanationThe indoubt testing tool task related userexit DFHINTRU issued an EXEC CICS INQUIRETRANSACTION command to inquire whether thecurrent transaction was in the indoubt transactionclass DFHTCIND. The command failed with aNOTAUTH response.


User responseWhen the indoubt testing tool is active, the taskrelated user exit DFHINTRU is invoked whenevera CICS transaction is started. For all transactions

for which command security checking is active,ensure that the user has read access to resourceTRANSACTION. If started transaction resourcesecurity checking is specified, for all transactions forwhich resource security checking is active, ensure thatthe user has read access to the transaction name inthe specified RACF resource class.

For more information on command security andresource security see the CICS Security.

Module:DFHINTRU

AINP

ExplanationThe indoubt testing tool task related userexit DFHINTRU issued an EXEC CICS INQUIRETRANSACTION command to inquire whether thecurrent transaction was in the indoubt transactionclass DFHTCIND. The command failed with anunexpected response.



Module:DFHINTRU

AINQ

ExplanationThe indoubt testing tool task related user exitDFHINTRU issued an EXEC CICS INQUIRE TASKcommand to inquire on the current task to obtain theunit of work ID to include in message DFHIN1009. Thecommand failed with a TASKIDERR response.



Module:




https://www.ibm.com/support/knowledgecenter//security/security.html



DFHINTRU

AINR

ExplanationThe indoubt testing tool task related user exitDFHINTRU issued an EXEC CICS INQUIRE TASKcommand to inquire on the current task to obtain theunit of work ID to include in message DFHIN1009. Thecommand failed with a NOTAUTH response.


User responseWhen the indoubt testing tool is active, the taskrelated user exit DFHINTRU is invoked whenevera CICS transaction is started. For all transactionsfor which command security checking is active(CMDSEC=YES), ensure that the user has read accessto resource TASK.

Module:DFHINTRU

AINS

ExplanationThe indoubt testing tool task related user exitDFHINTRU issued an EXEC CICS INQUIRE TASKcommand to inquire on the current task to obtain theunit of work ID to include in message DFHIN1009. Thecommand failed with an unexpected response.



Module:DFHINTRU

AINT

ExplanationThe indoubt testing tool issued a EXEC CICS ENABLEcommand to enable the indoubt testing tool task

related user exit program DFHINTRU, and thecommand failed with a NOTAUTH response.


User responseThe indoubt testing tool can be run under transactionCIND , under a user transaction where the programEXEC CICS LINKs to DFHINDT. or under a transactionwhere the program EXEC CICS LINKs to DFHINDAP.If command security checking is active for thetransaction (CMDSEC=YES), check that the userhas update access to resource EXITPROGRAM. Ifresource security checking is active for the transaction(RESSEC=YES), check that the user has update accessto resource DFHINTRU.


AINU

ExplanationThe indoubt testing tool issued a EXEC CICS ENABLEcommand to enable the indoubt testing tool taskrelated user exit program DFHINTRU, and thecommand failed with an unexpected response.




AIPA

ExplanationIP interconnectivity program DFHISCOP has beeninitiated invalidly, probably by entering a transactionid that refers to it, for example CISC or CISS, at aterminal. This program must only be initiated by CICSinternal processes.





User responseDo not initiate CISC or CISS directly.

Module:DFHISCOP

AIPB

ExplanationIP interconnectivity receiver program DFHISRRP hasbeen initiated invalidly, probably by entering atransaction id that refers to it, for example CISR, at aterminal. This program must only be initiated by CICSinternal processes.


User responseDo not initiate CISR directly.

Module:DFHISRRP

AIPC

ExplanationIP interconnectivity error and message programDFHISEMP has been initiated invalidly, probably byentering a transaction id that refers to it, for exampleCISE, at a terminal. This program must only beinitiated by CICS internal processes.


User responseDo not initiate CISE directly.

Module:DFHISEMP

AIPD

ExplanationIP interconnectivity program DFHISCOP has beeninitiated with invalid attach parameters by CICSinternal processes. This could be the result of aconfiguration error or a storage overwrite.

DFHISCOP should be defined as the initial programfor the IS domain connectivity transactions; these areCISC and the transactions for TCPIPSERVICEs withprotocol IPIC, CISS by default. This error could occur

if DFHISCOP is defined as the initial program for someother CICS internal transaction.


User responseCheck that DFHISCOP is correctly defined.

If necessary, examine the dump and any exceptiontrace entries to determine why the attach parametersare missing or invalid.

Module:DFHISCOP

AIPE

ExplanationIP interconnectivity program DFHISCOP received anINVALID, DISASTER, or EXCEPTION response from acall to the intersystems communication (IS) domain toacquire or release an IPCONN, or from another domainduring IS domain initialization processing.

The domain that detected the original error providesan exception trace, a console message and, possibly, asystem dump.


User responseSee the related message from the domain thatdetected the original error and examine the dump andany exception trace entries for further information ifnecessary.

Module:DFHISCOP

AIPF

ExplanationIP interconnectivity program DFHISCOP received anPURGED response from a call to the intersystemscommunication (IS) domain to acquire or release anIPCONN.







Module:DFHISCOP

AIPG

ExplanationIP interconnectivity long-running request/responsereceiver program received an INVALID, DISASTER, orEXCEPTION response from its PROCESS_INPUT call tothe intersystems communication (IS) domain.




Module:DFHISRRP

AIPH

ExplanationIP interconnectivity long-running error and messageprogram received an INVALID, DISASTER, orEXCEPTION response from its PROCESS_ERROR callto the intersystems communication (IS) domain.




Module:DFHISEMP

AIPI

ExplanationIP interconnectivity program DFHISREU or DFHISREXhas been initiated invalidly, probably by entering thetransaction ID that refers to it, CISU or CISX, at aterminal. This program must only be initiated by CICSinternal processes.


User responseDo not initiate CISU or CISX directly.

Module:DFHISREU, DFHISREX

AIPJ

ExplanationThe IS attach client module DFHISXM receivedan INVALID, DISASTER, or unexpected EXCEPTIONresponse from its INITIALIZE_RECEIVER call tomodule DFHISIS.

The call was issued during initialization of atransaction that was started by a transaction attachmessage received on an IP connection. The callwas made as part of processing to associate thetransaction with its intended user. The attempt to


associate the intended user with the transaction hasfailed.


Security attributes defined for the IPCONN may not beconsistent with the security parameters received in thetransaction attach message.


User responseExamine the dump and any exception trace entries forfurther information if necessary.

Verify the userid for the intended user is correctlydefined to the external security manager. :p Verify theIPCONN security attributes are correctly defined.

Module:DFHISXM

AIPK

ExplanationThe IS attach client module DFHISXM received aPURGED response from its call to another module.

The call was issued during initialization of atransaction that was started by a transaction attachmessage received on an IPIC connection.

The ISSB representing the IPIC receive sessionallocated to this transaction has been flagged forabend following an error on the IPCONN or purgerequest from the initiating system.


User responseLook for related messages reported in the error log.Examine the dump and any exception trace entries forfurther information if necessary.

Module:DFHISXM

AIPL

ExplanationThe IS attach client module DFHISXM receivedan INVALID, DISASTER, or unexpected EXCEPTIONresponse from its call to another module.

The call was issued during initialization of atransaction that was started by a transaction attachmessage received on an IPIC connection. The attemptto initialize the transaction has failed.

The input message received may not be in theexpected format.


User responseExamine the dump and any exception trace entries forfurther information if necessary.

Module:DFHISXM

AIPM

ExplanationThe transaction was connected to another transactionin another CICS system via an IPIC link. This othertransaction has abnormally terminated.


User responseCorrect the cause of the abend in the connectedtransaction.

Module:DFHISIS

AIPN

ExplanationIP interconnectivity program DFHISLQP has beeninitiated invalidly, probably by entering a transactionID that refers to it, CISQ, at a terminal. This programmust be initiated only by CICS internal processes.



User responseDo not initiate CISQ directly.

Module:DFHISLQP

AIPO

ExplanationIP interconnectivity program DFHISLQP has beeninitiated with invalid attach parameters by CICSinternal processes. This could be the result of aconfiguration error or a storage overwrite.

DFHISLQP should be defined as the initial programfor the IS domain connectivity transaction CISQ. Thiserror could occur if DFHISLQP is defined as the initialprogram for some other CICS internal transaction.


User responseCheck that DFHISLQP is correctly defined.

If necessary, examine the dump and any exceptiontrace entries to determine why the attach parametersare missing or invalid.

Module:DFHISLQP

AIPP

ExplanationIP interconnectivity program DFHISLQP received anINVALID, DISASTER, or EXCEPTION response from acall to the intersystems communication (IS) domainto process requests that are locally queued for anIPCONN.




Module:DFHISLQP

AIPR

ExplanationIP interconnectivity program DFHISLQP received anPURGED response from a call to the intersystemscommunication (IS) domain to acquire or release anIPCONN.






Module:DFHISLQP

AIPS

ExplanationIP interconnectivity remote scheduler programDFHISRSP has been started invalidly, probablybecause a transaction id that refers to DFHISRSP,for example CISM, has been entered at a terminal.DFHISRSP must be started by CICS internal processesonly.

System actionThe task is abnormally ended.


User responseDo not start CISM directly.

Module:DFHISRSP

AIPT

ExplanationIP interconnectivity remote scheduler programDFHISRSP received an INVALID, DISASTER, orEXCEPTION response from its PROCESS_SCHEDULERcall to the intersystems communication (IS) domain.


System actionThe task is abnormally ended with a transaction dump.


Module:DFHISRSP

AIPU

ExplanationFor CICS 4.1 and later, IPCONN names that are longerthan four characters are not supported in transactionrouting between CICS regions.

System actionThe task is abnormally ended with a transaction dump.

User responseCorrect the IPCONN names so that they are not longerthan four characters if used in transaction routingbetween CICS regions.

Module:DFHISXM

AIS1

ExplanationAn unexpected return code has been returned after aDFHMROQM FUNC=ENQ command was issued.

This command was issued when enqueueing work forthe IRC control task (CSNC) during IRC initialization.

System actionIf IRC is being initialized during CICS initialization (asa result of IRCSTRT being specified in the DFHSITor override parameters), then CICS is abnormallyterminated.

If IRC is being initialized during the execution ofa CEMT SET IRC OPEN command, then the CEMTtransaction is abnormally terminated.


Module:DFHCRSP

AIS2

ExplanationAn unexpected return code has been returned after aDFHMROQM FUNC=WAIT_Q command was issued.

This command was issued when waiting for more IRCwork to process.

System actionCSNC is abnormally terminated with a system dump.All tasks using MRO links to other systems areabnormally terminated.

All tasks in other CICS regions (includingshared database batch regions) that are currentlycommunicating with this system are also abended.


Module:DFHCRNP

AIS3

ExplanationAn attempt to issue a STCK (Store Clock) instructionfailed.




System actionCSNC is abnormally terminated with a system dump.

All tasks using MRO links to other systems areabnormally terminated.


User responseRepair or enable the system clock.

Module:DFHCRNP

AIS4

ExplanationAn unexpected return code has been returnedafter a DFHMROQM FUNC=ENQUEUE command. Thiscommand was issued when enqueueing work to theIRC 'delayed work' queue.




Module:DFHCRNP

AIS5

ExplanationAn unexpected return code has been returned after aDFHMROQM FUNC=ENQUEUE command was issued.

This command was issued when enqueueing work tothe IRC 'immediate work' queue.




Module:DFHCRNP

AIS6

ExplanationAn INVALID, DISASTER or EXCEPTION condition hasoccurred on a call to the storage manager domain(SM) to GETMAIN or FREEMAIN a file control read setbuffer.




Module:DFHMIRS

AIS7

ExplanationA PURGED condition has occurred on a call to thestorage manager domain (SM) to FREEMAIN a filecontrol read set buffer.



User responseInvestigate the reason why the task was purged. It waspurged either by the main terminal operator , or as aresult of a deadlock timeout.




Module:DFHMIRS

AIS8

ExplanationAn internal logic error has been detected in moduleDFHMIRS.



Module:DFHMIRS

AIS9

ExplanationThe mirror program has detected that a DPL serverprogram has returned in an invalid state followingthe completion of the LINK command. The serverprogram or a program it linked to has initiated asynclevel 2 conversation with another program whichin turn has issued a syncpoint. The server programhas not responded to the syncpoint request which isstill outstanding when control returns to the mirrorprogram.

The mirror program only issues this abend code if theLINK request did not specify SYNCONRETURN.


User responseCorrect the design of the DTP application orapplications initiated by the server program. If theSYNCONRETURN option is not specified on the LINKrequest, only the client program should initiate thesyncpoint. If it is necessary to issue syncpointrequests from the DTP applications, consider usingthe SYNCONRETURN option on the LINK request. Seethe CICS intercommunication for further details of theLINK command and its options.

Module:DFHMIRS

AISA

ExplanationThe mirror transaction (CSMI) has been attachedfrom some facility other than a terminal. This is notpermitted.


User responseUsing the dump, check the field TCAFCAAA to identifythe invalid attach.

Module:DFHMIRS

AISB

ExplanationThe mirror transaction (CSMI) has detected errors inthe data passed to it from the attaching transaction.


User responseThe invalid input will be visible in the transactiondump. This error is likely to be caused by somemismatch between the two systems. A typical examplemight be a DL/I request received on a systemgenerated without DL/I.

Module:DFHMIRS

AISC

ExplanationThe mirror transaction (CSMI) has not received a TIOAfrom the terminal.


User responseUse the trace in the dump and the dumped TCTTE toanalyze the problem further.




Module:DFHMIRS

AISD

ExplanationThe mirror program executed the request and receiveda nonzero return code as a result. The data flowcontrol state of the intersystem link being used wassuch that this information could not be returnednormally.

System actionThe mirror task is abnormally terminated with a CICStransaction dump.

User responseThe transaction dump provided will provideinformation required to analyze the source of thenonzero return code at its point of origin.

Module:DFHMIRS

AISF

ExplanationThe CICS mirror program DFHMIRS has been attachedin an unsupported manner. The principal facility forthe mirror transaction is defined as APPC, however theconversation is unmapped.


User responseThere is a problem with the system that caused themirror transaction to be attached. If you need furtherassistance from IBM to resolve this problem, seeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHMIRS

AISG

ExplanationThe mirror program executed the request andproduced the reply. This would not be sent becausethe data flow control state of the intersystem link wassuch that this could not be done.

System actionThe task (CSMI) is abnormally terminated with a CICStransaction dump.

User responseUse the transaction dump provided to analyze theproblem.

Module:DFHMIRS

AISH

ExplanationThe new connection task, CSNC, has been invoked inan incorrect manner (for example, from a terminal orvia an EXEC CICS START request).


User responseNone.

Module:DFHCRNP

AISI

ExplanationA function shipping request was passed by DFHEIPto DFHISP. This was found to be invalid by thetransformer, DFHXFP.

System actionThe transaction issuing the function shipping requestis abnormally terminated with a CICS transactiondump.

User responseThe transaction dump will provide information tofurther analyze the problem.

Module:DFHISP

AISJ

ExplanationThe IRC control task CSNC has abended because theattempt to LINK to DFHCRR failed.



System actionCSNC is abnormally terminated with a system dump.All tasks using MRO links to other systems areabnormally terminated. All tasks in other CICS regions(including shared database batch regions) that arecurrently communicating with this system are alsoabnormally terminated.

User responseEnsure that program DFHCRR is available.

Module:DFHCRNP

AISK

ExplanationThe user transaction has been abnormally terminatedduring the execution of a function shipping requeston an APPC session. This has happened becausethe mirror transaction on the remote system hasabnormally terminated, and caused a request forsyncpoint rollback to be sent across the session. CICSabends the user transaction in these circumstancesso that function shipping remains transparent to thetransaction.


User responseCheck the log on the mirror system to determine thereason for the original abend of the mirror task.

Module:DFHISP

AISL

ExplanationThe LU services manager transaction has been starteddirectly from a user terminal. This is not permitted.


User responseNone. The LU services manager transaction must bestarted internally by CICS.

Module:

DFHLUP, DFHCLS3, DFHCLS4, DFHZLS1

AISN

ExplanationTask CSNC attempted to acquire a SUSPEND TOKENto enable it to suspend itself until further work arrives.The attempt failed.

System actionCSNC is abnormally terminated with a dump. The IRCfacility is disabled.


Module:DFHCRNP

AISO

ExplanationTask CSNC attempted to suspend itself, awaitingfurther work. The attempt failed.

System actionCSNC is abnormally terminated with a dump. The IRCfacility is disabled.


Module:DFHCRNP

AISP

ExplanationA mirror transaction (transaction identifiers CSHR,CSM1, CSM2, CSM3, CSM5, or CSMI) has been invokedwith an invalid principal facility. The mirror transactionexecutes with an MRO session, an LU6.1 session or anAPPC session as its principal facility.





User responseDo not attempt to invoke the mirror transaction byentering the transaction identifier at a terminal.

Module:DFHMIRS

AISQ

ExplanationAn EXEC CICS command has been issued against aCPI Communications session. A CPI Communicationssession is one that has a CPI-Communications ControlBlock (CPC) associated with it.


User responseDo not mix EXEC commands with CPI Communicationscalls on the same end of a conversation.

Module:DFHMIRS

AISR

ExplanationThe CICS Inter-Region Session Recovery Program(DFHCRR) has been invoked in an incorrect manner,for example, from a terminal.

System actionThe program DFHCRR is abnormally terminated with aCICS transaction dump.

User responseNone.

Module:DFHCRR

AISS

ExplanationA security violation has occurred while CICS wasattempting to start a conversation with a remote APPCsystem. The security access level of the requestor wasinsufficient to access the transaction on the connectedAPPC system. Depending on the nature of the requestand the way security has been set up, the requestorwith an insufficient access level can be the local CICS

system, the requesting transaction, or the terminaluser.

Note:

DTP programs do not abend with code AISS after asecurity failure in the remote region.


User responseFirst, verify that the access was correctly denied. Then,if required, change the access level.

Module:DFHZARM

AIST

ExplanationAn unexpected return code has been returned after aDFHTC TYPE=LOCATE command.

System actionCSNC is abnormally terminated with a system dump.All tasks using MRO links to other systems areabnormally terminated. All tasks in other CICS regions(including shared database batch regions) that arecurrently communicating with this system are alsoabended.

User responseThe trace in the system dump should be used toanalyze the problem further.

Module:DFHCRNP

AISU

ExplanationAn INVALID, DISASTER, or EXCEPTION condition hasoccurred on a call to the storage manager domain (SM)to FREEMAIN a FCENT control block.





Module:DFHMIRS

AISV

ExplanationA PURGED condition has occurred on a call to thestorage manager domain (SM) to FREEMAIN a FCENTcontrol block.



User responseInvestigate why the task was purged. This is either as aresult of a purge from the master terminal operator viathe CEMT transaction, or by the task being timed outafter waiting for longer than the DTIMOUT (deadlocktimeout) value specified for the transaction.

If the master terminal operator purged the task, thismay have been in an attempt to clear the systemwhich appeared to be deadlocked for some reason.


Module:DFHMIRS

AISW

ExplanationAn INVALID, DISASTER, or EXCEPTION condition hasoccurred on a call to the storage manager domain (SM)to GETMAIN or FREEMAIN a CRB control block.




Module:DFHCRSP

AISX

ExplanationA PURGED condition has occurred on a call tothe storage manager domain (SM) to GETMAIN orFREEMAIN a CRB control block.



User responseInvestigate why the task was purged. It was purgedeither as a result of a purge from the main terminaloperator via the CEMT transaction, or by the task beingtimed out after waiting for longer than the DTIMOUT(deadlock timeout) value specified for the transaction.



Module:DFHCRSP

AISY

ExplanationThe LU services manager transaction has been started,but invalid parameters have been detected.



User responseSee message DFHZC4921 for further guidance.

Module:DFHLUP

AISZ

ExplanationDFHMXP has received an unexpected reply whencommitting START PROTECT NOCHECK requests senton a LUTYPE6.2 synclevel 1 conversation.


User responseDetermine what happened to transaction CVMI in thepartner system. If the START PROTECT NOCHECKrequests had been committed, no further action isnecessary. If they had not been committed, user-defined action is required to recover from the error.

Module:DFHMXP

AITA

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe recovery manager (RM) domain to initialize therecovery status of an IRC session. The domainprovides an exit trace, and possibly a console messageand a system dump (depending on the optionsspecified in the dump table).

This failure is either the result of a task purge, or aCICS logic error,

System actionThe CSNC task is abnormally terminated with a CICStransaction dump.

User responseSee the related diagnostic material produced by therecovery manager domain and determine the reasonfor the failure. In the case of a CICS logic error, youneed further assistance from IBM. See Working with

IBM to solve your problem for guidance on how toproceed.

Module:DFHCRNP

AITB

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to therecovery manager (RM) domain. The domain providesan exit trace, and possibly a console message and asystem dump (depending on the options specified inthe dump table).



User responseSee the related diagnostic material produced by therecovery manager domain and determine the reasonfor the failure. In the case of a CICS logic error, youneed further assistance from IBM. See Working withIBM to solve your problem for guidance on how toproceed.

Module:DFHISP DFHMXP

AITC

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to therecovery manager (RM) domain. The domain providesan exit trace, and possibly a console message and asystem dump (depending on the options specified inthe dump table).



User responseSee the related diagnostic material produced by therecovery manager domain and determine the reasonfor the failure. In the case of a CICS logic error, you






need further assistance from IBM. See Working withIBM to solve your problem for guidance on how toproceed.

Module:DFHMIRS

AITD

ExplanationThe mirror program has received an unexpectedresponse from the RX domain.

There are several reasons why this error may occur:

• A request received from an EXCI client isinconsistent with an earlier request in the same Unitof Work

• CICS has received an unexpected response fromthe Recoverable Resource Management Servicescomponent of MVS.

• There has been an internal error in the RX domain.


User responseUse the exception trace provided by the RX domainto determine the reason for the failure. If the error iscaused by an inconsistent request from an EXCI client,there may be an error in the client program.

In the other cases, you might need further assistancefrom IBM. See Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHMIRS

AITE

ExplanationA transaction has executed a transactional EXCIrequest from a batch region, and has been waiting forone of the following events for longer than the intervalspecified in the RTIMOUT or DTIMOUT value for thetransaction.

• A further transactional EXCI request from the batchregion

• A syncpoint initiated by Resource RecoveryManagement Services (RRMS).


User responseDetermine why the expected event has not occurred:

If a further transactional EXCI request is expected:

• The batch program may be suspended

If a syncpoint is expected:

• The batch program may be suspended beforereaching syncpoint

• RRMS may have started syncpoint processing but iswaiting for another Resource Manager to respond tothe syncpoint request.

See Working with IBM to solve your problem forguidance on how to proceed.

Module:DFHMIRS

AITF

ExplanationA transaction has executed a transactional EXCIrequest from a batch region, and has been purgedwhile waiting for one of the following events:




User responseDetermine why the expected event has not occurred:

If a further transactional EXCI request is expected:

• The batch program may be suspended

If a syncpoint is expected:

• The batch program may be suspended beforereaching syncpoint

• RRMS may have started syncpoint processing but iswaiting for another Resource Manager to respond tothe syncpoint request.

See Working with IBM to solve your problem forguidance on how to proceed.







Module:DFHMIRS

AITG

ExplanationA transaction has executed a transactional EXCIrequest from a batch region, and both of the followingevents has occurred:



Normally, only one event should occur, and not both.


User responseDetermine why both events have occurred. Thissituation may arise when an EXCI client times out ona DPL request that CICS is not ready to receive andthen proceeds to take a syncpoint. If this is not thecase, you may need assistance from IBM. See Workingwith IBM to solve your problem for guidance on how toproceed.

Module:DFHMIRS

AITH

ExplanationA mirror transaction processing an ECI request froma TCP/IP connected client has failed while trying toreceive data from, or send data to, a client. This couldbe a read time out, or a more serious error in theflows that prevented CICS from correctly processingthe data.


User responseIf the error was a time out, determine why the clienthas not continued with the extended ECI conversation.Other errors will have associated IE domain messagesto aid in problem determination.

Module:

DFHMIRS

AITI

ExplanationA mirror transaction processing a START CHANNELor LINK CHANNEL request has failed while trying toreceive data from, or send data to, a connected CICSsystem. Because a channel may include a considerableamount of data, it may require many calls to terminalcontrol to transmit channel data. DFHMIRS callsprogram DFHAPCR to perform all the inter-systemtransmission of channel data. Terminal control hasdetected an error in one of these calls. The error couldbe a read time out, or a more serious error in theflows that prevented CICS from correctly processingthe data.


User responseIf the error was a time out, determine why the otherend has not continued with the conversation. Othererrors will have associated terminal control messagesto aid in problem determination. Examine trace entriesfrom DFHAPCR to determine terminal control error andsense information.

Module:

AITJ

ExplanationA mirror transaction processing a request from a clientconnected using IP interconnectivity has failed whiletrying to receive data from, or send data to, a client.This could be a read time out, or a more seriouserror in the flows that prevented CICS from correctlyprocessing the data.


User responseIf the error was a time out, determine why the clienthas not continued with the conversation. Other errorswill have associated IS domain messages to aid inproblem determination.

Module:DFHMIRS




AITK

ExplanationThe ISCINVREQ condition has been raised. This canhappen when the resource proves to be on yet anotherremote system, that is, when daisy-chaining is active.


User responseCheck that daisy-chaining of requests is intended andthat all relevant intersystem links are in service.

Module:DFHMIRS

AITL

ExplanationThe IPIC client sent a CCSID that was not recognized.


User responseCheck that the client system is using one of the clientcode pages supported by CICS TS.

Module:DFHMIRS

AITM

ExplanationA command has been received by the mirror programto call itself.


User responseCorrect the API command in the client system programso that it does not request an EXEC CICS LINKPROGRAM to be executed that specifies the name ofthe mirror program.

Module:

DFHMIRS

AITN

ExplanationAn attempt to change the TCB DFHMIRS was runningon has failed.

System actionThe transaction is terminated.

User responseContact your IBM support center.

Module:DFHMIRS

AITO

ExplanationIP interconnectivity program DFHISPHP andDFHISPRP has been initiated invalidly, probably byentering a transaction ID that refers to it, CISP or CIS1,at a terminal. This program must be initiated only byCICS internal processes.


User responseDo not initiate CISP or CIS1 directly.

Module:DFHISPHP

AITP

ExplanationThe application context handling module, DFHMNAC,has returned an unexpected response from functionMIRROR_ACD.

System actionThe transaction is terminated.


Module:DFHMIRS


AJxx abend codesAJ01

ExplanationThe main method of the Java environment setup class,Wrapper, has been invoked without an argument.Wrapper main expects the class name of the user'smain to be passed as the first argument.

The callUserClass method of Wrapper detects this,sets return code INVALID_ARGUMENTS and invokesnative method SetAbend to abend the task.



Module:DFJCICS

AJ02

ExplanationA CICS AbendError has been caught by the Javaenvironment setup class, Wrapper.

The callUserClass method of Wrapper detects this,sets return code ABEND_RECEIVED and invokes nativemethod SetAbend to abend the task.


User responseSee related messages and JVM error output in stderrto determine the reason for the original abend.

Module:DFJCICS

AJ03

ExplanationA CicsConditionException has been caught by the Javaenvironment setup class, Wrapper.

The callUserClass method of Wrapper detects this,sets return code CONDITION_RECEIVED and invokesnative method SetAbendForCondition to abend thetask. The appropriate default abend code for thecondition should be issued but, if for some reason thisis not possible, an AJ03 abend may be issued.


User responseSee related messages and JVM error output instderr to determine the reason for the originalCicsConditionException.

Module:DFJCICS

AJ04

ExplanationAn unexpected error has been caught by the Javaenvironment setup class, Wrapper, attempting toinvoke the user class or an unhandled exception hasbeen thrown in the Java environment.

In the first case, the callUserClass methodof Wrapper detects this, sets return codeUNEXPECTED_EXCEPTION and invokes native methodSetAbend to abend the task. In the second case, theJNI code invokes the SetAbend method to abend thetask and AJ04 is set as the default abend code.


User responseSee related messages and JVM error output in stderrto determine the reason for the original exception.

Module:DFJCICS

AJ05

ExplanationAn unhandled exception has been caught by theJava environment setup class, Wrapper, as anInvocationTargetException from the user class.



The callUserClass method of Wrapper detects this,sets return code INVOCATION_TARGET_EXCEPTIONand invokes native method setAbend to abend thetask.



Module:DFJCICS

AJ07

ExplanationThe Java environment setup class, Wrapper, has beenunable to invoke the user's main method. The classwhose name was passed as an input parameter to itsCallUserClass method was not found.


User responseCheck that CICS has been granted read permission tothe target class and the entire zFS directory structurein which the class or Jar file is located.

Module:DFJCICS

AJ09

ExplanationThe Java environment setup class, Wrapper, has beenunable to invoke the user's main method. A publicstatic method, taking either a CommAreaHolder ora String array as input, was not found in the classwhose name was passed as an input parameter to theCallUserClass method of Wrapper.


User responseCheck that you have provided a main method, with anappropriate method signature, in the specified class.Also check that the target class explicitly uses the'public' class modifier and that it is stored in a jarfile on the JVM's classpath. CICS must have readpermission for the jar file.

Module:DFJCICS

AJ10

ExplanationThe Java environment setup class, Wrapper, hasdetected that the user's class has used JDBC or SQLJ.It however has been unable to load the DB2 JDBCclasses necessary to call back the JDBC/SQL driver forcleanup processing following completion of the userclass.



Module:DFJCICS

AJ11

ExplanationThe Java environment setup class, Wrapper, hasdetected that the user's class has used JDBC or SQLJ.It however has been unable to find the DB2 JDBCstatic method to call back the JDBC/SQL driver forcleanup processing following completion of the userclass.



Module:DFJCICS




AJ12

ExplanationThe Java environment setup class, Wrapper, hasdetected that the user's class has used JDBC or SQLJ.It however has been unable to invoke the DB2 JDBCstatic method to call back the JDBC/SQL driver forcleanup processing following completion of the userclass.



Module:DFJCICS

AJ13

ExplanationAn exception occurred and CICS was unable toinstantiate an instance of the user's class.


User responseSee related messages and JVM error output in stderrto determine the reason for the exception. Check thatthe class has a no argument constructor as CICSrequires this in order to instantiate the class.

Module:DFJCICS

AJ99

ExplanationThe Java environment setup class, Wrapper, hasdetected an AbendException and issued setAbend.The abend code extracted from the AbendExceptionis too long.

System actionTask abnormal termination continues with the abendcode set to AJ99

User responseCorrect the abend code String used to create theAbendException.

Module:DFJCICS

AJA0

ExplanationThe native method SetAbendForCondition has beenpassed an invalid Resp value by the Wrapper class.



Module:DFJCICS

AJCD

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call tothe storage manager (SM) domain. The domain thatdetected the original error provides an exception trace,a console message, and possibly a system dump(depending on the options in the dump table).



Module:DFHJCP

AJCE









Module:DFHJCP

AJCS

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call to the logmanager (LM) domain. The domain that detected theoriginal error provides an exception trace, a consolemessage, and possibly a system dump (depending onthe options in the dump table).



Module:DFHJCP

AJCT

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call to therecovery manager (RM) domain. The domain thatdetected the original error provides an exception trace,

a console message, and possibly a system dump(depending on the options in the dump table).



Module:DFHJCP

AJCU

ExplanationA purge response has been received from either thelog manager or or the recovery manager. The domainthat detected the original purge condition provides anexception trace.





Module:DFHJCP

AJVM

ExplanationA JVM has thrown an Exception that was caught byCICS. An abend has not been triggered, the AJVM codeexists for use in messages that expect to reference


an abend code. Messages that reference this codeare preceded by other diagnostics that document theexception, typically a DFHSJ1004 message.

System actionProcessing continues.


Module:DFHSJSC

AJST

ExplanationProgram DFHJSON was called using EXEC CICS LINK,but no channel was provided.

System actionCICS terminates the task with a transaction dump.

User responseChange the application program to pass a channel.

Module:DFHJSON

AKxx abend codesAKC0

ExplanationAn attempt has been made to run the CICS internaltask CSSY as a user transaction.


User responseInvestigate why the attempt was made to run CSSY asa user transaction.

Module:DFHAPATT

AKC1

ExplanationA DFHKC WAIT request was issued when the ECB wasalready marked as waiting.

System actionThere is a probable user error. The transaction isabnormally terminated.

User responseCorrect the program that issued the request.

Module:DFHXCP

AKC2

ExplanationA bad response has been received from a dispatcher(DS) domain call.

System actionThe transaction is abnormally terminated with atransaction dump and a trace entry.

User responseExamine the trace entry for further information.

Module:DFHXCP

AKC3

ExplanationThe task has been purged, probably due to operatoraction such as a CEMT TASK PURGE command. Thetask might also have been purged as a result of CICSissuing a purge request.


User responseUse the transaction dump to determine why the taskwas purged. In particular, if the purge was operatorinitiated, the dump should be useful in determiningwhy this task needed to be explicitly purged.

Module:DFHXCP, DFHXMAT, DFHXMCL, DFHXMIQ, DFHXMTA


AKC6

ExplanationDFHKC RESUME should always be preceded byDFHKC SUSPEND. If this protocol is violated then thetransaction is abnormally terminated with abend codeAKC6.

System actionTransaction is abnormally terminated with abend codeAKC6.

User responseExamine the trace entry for further information.

Module:DFHXCP

AKC8

ExplanationA bad response has been received from a call to thekernel (KE) domain during the processing of a taskpurge request.

System actionThe transaction is abended with a transaction dump.

User responseExamine the dump and any exception trace entries forfurther information.

Module:DFHXCP

AKC9

ExplanationAn incorrect response has been received from a call tothe enqueue (NQ) domain during the processing of aDFHKC TYPE=ENQ or a DFHKC TYPE=DEQ request.


User responseExamine the dump and any exception trace entries forfurther information. Since the DFHKC service is onlyused for internal enqueues, this abend indicates anerror in CICS. If you need further assistance from IBM

to resolve this problem, see Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHXCP

AKCB

ExplanationThe CICS transaction manager restart task could notcomplete because a necessary step failed. The taskhas done some essential recovery operations andabnormally terminated itself with code AKCB.

System actionCICS writes a transaction dump for the transactionmanager restart task.

CICS sends three messages to the console, one toidentify the error detected by the transaction managerrestart task, one to say that the task has failed, andone that gives you the option of cancelling CICS orletting it continue. Depending on the nature of theoriginal error, you may see messages from some othersystem component (for example, an access method).

User responseUse the messages and dumps to find out the cause ofthe failure.

Module:DFHKCRP

AKCC

ExplanationThe CICS transaction manager has abended thetransaction because the purge threshold of itsTRANCLASS has been reached. This is specifiedby the PURGETHRESH parameter on CEDA DEFINETRANCLASS. See the Defining resources manual formore details of this parameter.

System actionThe transaction is abended and messages DFHAC2004and DFHAC2036 are issued. The transaction dump issuppressed for this abend code.

User responseResubmit the transaction. The cause of the abend maybe a temporary stress condition in the system.

If the problem persists, determine why theTRANCLASS purge threshold has been reached.Ensure that PURGETHRESH has been specified




https://www.ibm.com/support/knowledgecenter//configuring/resources/dfha22v.html

correctly. Also, ensure that the MAXACTIVE value ofthe TRANCLASS has not been set too low. Transactionsattached after the MAXACTIVE limit has been reachedare immediately queued subject to the PURGETHRESHlimit.

If PURGETHRESH and MAXACTIVE are set correctly,look for a more general problem which has causeda decrease in the capacity of the system to executetransactions in the TRANCLASS. The decrease might,for example, be caused by a connected CICS regionwhich processes requests for transactions in theTRANCLASS, if this connected region has sloweddown.

Examine all resources (files, links, storage, and so on)used by the transactions in the TRANCLASS which isreaching the purge threshold and determine why thecapacity of the system is reduced.

Module:DFHXMAT, DFHXMCL

AKCE

ExplanationWhile CICS transaction manager was recordingchanges to a transaction or profile definition, a writeto the system log failed.

System actionCICS terminates the transaction with a transactiondump.

User responseUse the dumps to find out why the write to the logfailed.

Module:DFHKCQ

AKCF

ExplanationWhile CICS transaction manager was recordingchanges to a profile definition, a write to the catalogfailed.

System actionCICS terminates the transaction with a transactiondump.

User responseUse the dumps to find out why the write to the catalogfailed.

Module:DFHKCQ

AKCR

ExplanationTransaction manager has received an invalid requestcode. The last AP F000 trace entry before the programcontrol program (PCP) ABEND TRACE entry (TRACEID 'F2', request code X'6000') will contain the invalidtransaction manager request code in the fifth byte ofthe first section of the trace.


User responseDetermine the cause of the invalid request code andcorrect the problem.

Module:DFHXCP

AKCS

ExplanationA deadlock timeout condition has been detected.This condition may occur within a transaction thatspecifies DTIMOUT to be nonzero on its installedtransaction definition. Deadlock timeout occurs whena transaction has been waiting or has been suspendedfor longer than the time specified in DTIMOUT.

The abend may be driven by a variety of internal CICSevents, for example:

• A short on storage condition• A temporary storage shortage• ENQUEUE• An ALLOCATE request• A RETRIEVE WAIT request.

The abend can also occur if CICS stops running fora time, for example while an sdump is taken. This isbecause deadlock timeout is based on total elapsedtime, and not just the time CICS is executing.

Analysis: The transaction receiving the AKCS abendmust have been suspended or must be waiting for areason such as a short on storage, enqueued on alock, a short on temporary storage, a suspend afterRETRIEVE WAIT, a suspend after ALLOCATE, or animplicit ALLOCATE within function shipping or terminalsharing support. If none of these apply, the trace


might reveal some event that has caused CICS to stoprunning for a time.

System actionThe transaction is abnormally terminated. A dumpis not provided unless the dump table entry fortransaction dump code AKCS indicates that one shouldbe taken.

User responseThe transaction should be reexecuted, and thesituation causing the SUSPEND to occur may clearitself.

The AKCS abend is to be expected occasionally, unlessDTIMOUT is set to zero. No special action is necessary.

Module:DFHXCP

AKCT

ExplanationA terminal read-time-out condition has been detected.The transaction has been waiting for a terminal inputmessage for an interval longer than specified in theRTIMOUT value for that transaction.

If an EXEC CICS HANDLE ABEND has been issuedfor this task, the read that was timed-out is stilloutstanding. To cancel this read you should issue anEXEC CICS ABEND at the end of the user exit routineso that CICS can clean up the terminal's TCTTE.

System actionThe transaction is abnormally terminated. Atransaction dump is not provided.

User responseThis abend is a normal one. Coding RTIMOUT in thePROFILE entry asks for the task to be abnormallyterminated if the terminal does not send input withinthe specified time.

Module:DFHXCP

AKCV

ExplanationA bad return code was passed as a result of theresume of a task suspended by ICP.

System actionThe transaction is terminated with a dump.

User responseCheck the response from the resume in the trace todetermine the cause of the error.

Module:DFHALP

AKEA

ExplanationA program check has been detected by the kernel (KE)domain.

System actionIf an application is in control, the ASRA abend ispresented to the application. Otherwise, the functionalrecovery routine of the CICS module in control at thetime is given control. This recovery routine producessuitable diagnostics and may terminate CICS.

User responseLook at the kernel domain section of the system dumpto determine where the program check has occurred.

Module:DFHKESTX

AKEB

ExplanationAn operating system abend has been detected by thekernel (KE) domain.

System actionIf an application is in control, the ASRB abend ispresented to the application. Otherwise, the functionalrecovery routine of the CICS module in control at thetime is given control. This recovery routine producessuitable diagnostics and may terminate CICS.

User responseCheck the console for any MVS messages that mayhave caused this abend.

Look at the kernel domain section of the system dumpto determine where the abend has occurred.

Module:DFHKESTX

AKEC


ExplanationThe kernel (KE) domain has detected runaway.

System actionIf an application is in control, the AICA abend ispresented to the application. Otherwise, the functionalrecovery routine of the CICS module in control at thetime is given control. This recovery routine producessuitable diagnostics and may terminate CICS.

User responseLook at the kernel domain section of the system dumpto determine where the runaway has occurred.

Module:DFHKESTX, DFHKERRU

AKED

ExplanationThe kernel (KE) domain has been requested to initiateabend processing as a result of a deferred abendrequest.

System actionAbend processing starts for the task that is subject tothe deferred abend request.

User responseThe task is not abended with AKED but by an abendcode specified by the requestor of the deferred abend.See the description of this abend for further guidance.

Module:DFHKEEDA

AKEF

ExplanationThe kernel (KE) domain has detected an error whileprocessing a domain call. The error may have beencaused by a domain gate that was not yet active duringinitialization

System actionIf an application is in control, the transactionterminates with a system dump. Otherwise, thefunctional recovery routine of the CICS module incontrol at the time is given control. This recoveryroutine produces suitable diagnostics and mayterminate CICS.

User responseSee any related messages from the kernel domain.

Look at the kernel domain section of the system dumpto determine where the error has occurred. Check thata call has not been made to a domain gate that hasnot yet been made active. Check that the caller has notspecified KERNERROR(YES).

If the abend occurs during CICS system initialization,ensure that the utility (DFHCCUTL) used to initializethe local catalog (DFHLCD) is at the correct level. Asample job is provided in SDFHINST(DFHDEFDS).

Module:DFHKERKE

AKEG

ExplanationThe kernel (KE) domain issued an SM GETMAIN forkernel stack storage, but the GETMAIN request failed.

System actionIf an application is in control, the transactionterminates with a system dump. Otherwise, thefunctional recovery routine of the CICS module incontrol at the time is given control. This recoveryroutine produces suitable diagnostics and mayterminate CICS.

User responseLook at the kernel domain section of the system dumpto determine why sufficient storage was not available.

If the short-on-storage condition persists, considerincreasing the size limit of the CICS DSA. You can varythe DSA dynamically using the DSALIM parameter onthe CEMT main terminal command.

Module:DFHKESGM

AKEH

ExplanationThe transaction was purged while running outside thecontrol of CICS.

System actionCICS terminates the transaction abnormally.

The EXEC CICS HANDLE ABEND command can nothandle this abend.


User responseInvestigate the reason why the transaction waspurged.

Possible reasons are

• An operator purged the transaction• The transaction was purged because DTIMEOUT has

been exceeded• Another transaction purged the transaction

Module:DFHKESTX

AKEI

ExplanationThe kernel (KE) domain has detected runaway whilethe transaction is running outside the control of CICS.

System actionIf an application is in control, the AICA abend ispresented to the application. Otherwise, the functionalrecovery routine of the CICS module which waslast in control at the time of runaway detection isgiven control. This recovery routine produces suitablediagnostics and may terminate CICS.

The EXEC CICS HANDLE ABEND command can nothandle this abend.

User responseSee the Troubleshooting and support for guidance ondealing with loops.

Module:DFHKESTX

AKEJ

ExplanationA backlevel XPI call has been detected by the kernel(KE) domain.

System actionAdditional error messages will be produced by CICSthat identify the global user exit or task related userexit that made the backlevel XPI call. If an AP domainglobal user exit or task related user exit issued thebacklevel XPI call the ASRJ abend is presented to theapplication.

User responseReassemble the exit program identified by theadditional error messages using the latest CICSlibraries.

Module:DFHKESTX

AKER

ExplanationA task has been recovered from a JVM server onto theQR TCB following a KILL against the JVM server.


User responseNone

Module:DFHAPLJP

AKEX

ExplanationA program check has been detected by the kernel(KE) domain while executing under a TCB that is notenabled for EXEC CICS commands. This is probablybecause of an attempt to execute a CICS command inan environment where this is not possible.

System actionIf an application is in control, the ASRA abend ispresented to the application. Otherwise, the functionalrecovery routine of the CICS module in control at thetime is given control. This recovery routine producessuitable diagnostics and may terminate CICS.

User responseLook at the kernel domain section of the system dumpto determine where the program check has occurred.

Module:DFHKESTX

AKEZ

ExplanationA user attach has failed because there are insufficientkernel tasks available. This indicates an internal logicerror.



System actionMessage DFHKE0001 is issued and a system dump istaken. The attach of the user transaction fails.


Module:DFHKETA

AKKA

ExplanationA kill request has been actioned when a transactionwas not protected from purge or force purge. Thetransaction is either in a dispatcher suspend, thedeferred abend processor is in control, the applicationis calling CICS, CICS is returning to the application, orthe application is outside of the control of CICS.

System actionIf an application is in control, the abend is presentedto the application. Otherwise, the functional recoverymodule of the CICS module in control at the timeis given control. This recovery routine producesdiagnostics and might terminate CICS. This abendcode cannot be handled by the application.

User responseNotify the system programmer to determine why thetask has been killed.

Module:DFHDSSR, DFHKEEDA, DFHEIP, DFHKEDS

AKKB

ExplanationA kill request has been actioned when a transactionwas not protected from forcepurge but was protectedfrom purge. The transaction is either in a dispatchersuspend, the deferred abend processor is in control,the application is calling CICS, CICS is returning to theapplication, or the application is outside of the controlof CICS.

System actionIf an application is in control, the abend is presentedto the application. Otherwise, the functional recoverymodule of the CICS module in control at the timeis given control. This recovery routine produces

diagnostics and might terminate CICS. This abendcode cannot be handled by the application.



AKKC

ExplanationA kill request has been actioned when a transactionwas protected from force purge. The transaction iseither in a dispatcher suspend, the deferred abendprocessor is in control, the application is calling CICS,CICS is returning to the application, or the applicationis outside of the control of CICS.




AKKD

ExplanationA CEKL purge has been requested. Abend processinghas started for the task that is subject to the deferredabend request.

System actionThe task is abended with abend code AKKD.

User responseNotify the system programmer to determine why thetask has been purged.

Module:DFHKEEDA

AKKE



ExplanationA CEKL force purge has been requested. Abendprocessing has started for the task that is subject tothe deferred abend request.

System actionThe task is abended with abend code AKKE.

User responseNotify the system programmer to determine why thetask has been purged.

Module:DFHKEEDA

AKKG

ExplanationThe kernel (KE) domain has detected a kill requestfrom the runaway exit program. The task was notprotected from runaway when the kill request wasactioned.



Module:DFHKESTX, DFHKERRU, DFHKEKIL

AKKH

ExplanationThe kernel (KE) domain has detected a kill requestfrom the runaway exit program. The task wasprotected from runaway when the request wasactioned.



Module:DFHKESTX, DFHKERRU, DFHKEKIL

AKSE

ExplanationA user has generated an addition to the keyword table,but code has not been added to process this keyword.

System actionThe transaction is abnormally terminated and a dumpis taken.

User responseAdd code to process the keyword.

Module:DFH99KC

ALxx abend codesALGA

ExplanationAn error has occurred obtaining a lock within the logmanager domain.

System actionThe recovery routine of the module in control isinvoked which issues message DFHLG0002 with a

system dump. DFHLG0002 reports the module incontrol at the time of the error.

User responseSee the description of message DFHLG0002 for furtherguidance.

Module:DFHLGGL, DFHLGJN, DFHLGLD, DFHLGST

ALGB


ExplanationAn error has occurred releasing a lock within the logmanager domain.

System actionThe recovery routine of the module in control isinvoked which issues message DFHLG0002 with asystem dump. DFHLG0002 reports the module incontrol at the time of the error.



ALGC

ExplanationA disaster response has been detected whenprocessing the building block code used by the logmanager.




ALGD

ExplanationA disaster response has been detected whenprocessing the building block storage interface codeused by the log manager.



Module:DFHLGCM, DFHLGGL, DFHLGJN, DFHLGLD, DFHLGST

ALGE

ExplanationAn unexpected error has occurred while the logmanager was attempting to find a journal modeldefinition.



Module:DFHLGJN

ALGF

ExplanationAn unexpected error occurred when the log managerwas attempting an enqueue or dequeue operation.



Module:DFHLGGL, DFHLGJN, DFHLGST

ALGG

ExplanationTransaction CSQC has been issued from a terminal.This is not permitted. The transaction can only bestarted internally by CICS.



User responseDo not try to invoke CSQC from a terminal.

Module:DFHLGQC

ALIC

ExplanationCICS has issued a GETMAIN request during theinitialization phase for an application program inorder to obtain run time execution storage forLanguage Environment above the 31-bit line. Howeverinsufficient storage was available to satisfy therequest.

System actionCICS abnormally terminates the task. CICS processingcontinues.

User responseSee the related message from the Storage Managerdomain where the original error was detected.

Module:DFHAPLI

ALID

ExplanationCICS has issued a GETMAIN request during theinitialization phase for an application program inorder to obtain run time execution storage forLanguage Environment below the 31-bit line. Howeverinsufficient storage was available to satisfy therequest.



Module:DFHAPLI

ALIF

ExplanationCICS has issued a GETMAIN request during theinitialization phase for an application program in orderto obtain thread storage for Language Environment.However insufficient storage was available to satisfythe request.



Module:DFHAPLI

ALIG

ExplanationCICS has been unable to determine the language ofthe user application program about to be executed.Either the program was compiled against an old levelof compiler that is no longer supported by CICS, or thelanguage of the program is not supported by CICS.

System actionCICS abnormally terminates the task and disables theprogram. CICS processing continues.

User responseEnsure that the program to be run is written in oneof the languages and compiled against a level ofcompiler supported by CICS. See the Developing CICSApplications for details of the languages and compilerscurrently supported.

Module:DFHAPLI

ALIH

ExplanationCICS has determined the language of a program to beVS COBOL II, but Language Environment has indicatedthat it is unable to execute the program. NormallyLanguage Environment is able to execute VS COBOLII programs in compatibility code.





User responseEnsure that the program to be run is writtenin one of the languages supported by CICS andLanguage Environment, and compiled against a levelof compiler supported by Language Environment. Seethe Language Environment Migration Guide for detailsof the languages and compilers currently supported,and any actions which may be necessary by the usersuch as re-compilation or re-linking.

Module:DFHAPLI

ALII

ExplanationCICS has determined the language of a program tobe OS/PLI, but Language Environment has indicatedthat it is unable to execute the program. NormallyLanguage Environment is able to execute OS/PLIprograms in compatibility code.


User responseEnsure that the program to be run is writtenin one of the languages supported by CICS andLanguage Environment, and compiled against a levelof compiler supported by Language Environment. Seethe Language Environment Migration Guide for detailsof the languages and compilers currently supported,and any actions which may be necessary by the usersuch as re-compilation or re-linking.

Module:DFHAPLI

ALIJ

ExplanationCICS has determined that an C or C++ programcompiled with the XPLINK option is aboutto be executed but the program is definedwith attribute CONCURRENCY(QUASIRENT). XPLINKprograms execute on open TCBs and cannotrely on quasi-reentrancy. They must be coded tothreadsafe standards and defined to CICS withCONCURRENCY(REQUIRED).


User responseEnsure that the program is coded to threadsafestandards and defined as CONCURRENCY(REQUIRED),or recompile the program without the XPLINK option.

A program can be defined as threadsafe byusing standard CICS or CPSM resource definitionfacilities, via program auotinstall, or by usinga Language Environment runtime option. Theruntime option can be specified in the sourceof the program by means of a #pragmarunopts(ENVAR(CICSVAR=REQUIRED)) statement.Alternatively ENVAR=('CICSVAR=REQUIRED') can bespecified in a CEEUOPT CSECT which is then linkeditedwith the program.

Module:DFHAPLI

ALIK

ExplanationCICS has determined that an OS/VS COBOL programis about to be executed. However CICS no longersupports such programs.


User responseEnsure that the program is recompiled against alevel of COBOL compiler supported by CICS. Seethe Developing CICS Applications for details of thelanguages and compilers currently supported.

Module:DFHAPLI

ALIL

ExplanationCICS has attempted to change to an OPEN TCB onwhich to execute the JAVA, XPLINK or OPENAPIprogram, but the change mode was unsuccessful.CICS may be short on storage and have insufficientstorage to allow creation of the new TCB.




User responseCheck other messages from CICS to determinewhether CICS is short on storage. Consider reducingmax tasks (MXT) to reduce the storage requirementsfrom concurrent transactions

Module:DFHAPLI, DFHAPLJ, DFHAPLX

ALX1

ExplanationCICS has issued an initialize request to the LanguageEnvironment preinitialized services system (CEEPIPI).However, CEEPIPI has returned an error condition.This error strongly indicates an internal failure inLanguage Environment.


User responseThe full trace entry will indicate the return codefrom Language Environment. Consult the LanguageEnvironment Programming Guide manual for anexplanation of the return code.

Module:DFHAPLX

ALX2

ExplanationCICS has issued an add_entry request to the LanguageEnvironment preinitialized services system (CEEPIPI).However, CEEPIPI has returned an error condition.This error strongly indicates an internal failure inLanguage Environment.


User responseThe full trace entry will indicate the return codefrom Language Environment. Consult the Language

Environment Programming Guide manual for anexplanation of the return code.

Module:DFHAPLX

ALX3

ExplanationCICS has issued a call_main request to the LanguageEnvironment preinitialized services system (CEEPIPI).However, CEEPIPI has returned an error condition.This error strongly indicates an internal failure inLanguage Environment.



Module:DFHAPLX

ALX4

ExplanationCICS has issued a remove_entry request to theLanguage Environment preinitialized services system(CEEPIPI). However, CEEPIPI has returned an errorcondition. This error strongly indicates an internalfailure in Language Environment.



Module:DFHAPLX

ALX5


ExplanationCICS has issued a terminate request to the LanguageEnvironment preinitialized services system (CEEPIPI).However, CEEPIPI has returned an error condition.This error strongly indicates an internal failure inLanguage Environment.



Module:DFHAPLX

AMxx abend codesAMGB

ExplanationA task has been purged due to lack of storage.


User responseTry the transaction again later. If the short-on-storagecondition persists, increase the size of the dynamicstorage areas.

Module:DFHMGP

AMI1

ExplanationWhen the mirror task is resumed, a bad response otherthan a time out or a cancellation was given by thedispatcher.

System actionThe mirror transaction is abnormally terminated with atransaction dump.

User responseUse the dump and the trace to determine the cause ofthe error.

Module:DFHMIRS

AMNA

ExplanationAn exception response has been received from themonitoring (MN) domain while processing a userevent monitoring point (EMP) request. The exceptionresponse is produced when the 4-byte DATA1 field inthe user parameter contains an invalid address.


User responseUse the transaction dump to determine why the DATA1value passed to the monitoring (MN) domain wasinvalid.

Module:DFHCMP

AMNB

ExplanationAn exception response has been received from themonitoring (MN) domain whilst processing a userevent monitoring point (EMP) request. The exceptionresponse is produced when the 4-byte DATA2 field inthe user parameter contains invalid data.


User responseUse the transaction dump to determine why the DATA2value passed to the monitoring (MN) domain wasinvalid.

Module:DFHCMP


AMNZ

ExplanationAn unexpected error response has been received fromthe monitoring (MN) domain while processing a userevent monitoring point (EMP) request.


User responseThis indicates a possible error in CICS code. An earlierCICS message is issued from the monitoring domain.Follow the user response for that message.

Module:DFHCMP

AMPB

ExplanationA task exceeded a policy threshold and the actiondefined is to abend the task.

System actionA DFHMP3002 message precedes this abend.

User responseSee DFHMP3002 message for diagnostics todetermine the cause of the abend.

Module:DFHMPXM

AMPC

ExplanationAn unexpected error occurred in the deferred ruleevaluation task CMPE.

System actionAn exception trace entry is written. The CMPE task isabnormally terminated with a CICS transaction dump.


Module:DFHMPDE

AMPD

ExplanationAn attempt was made to attach a CICS deferred ruleevaluation task CMPE, but the transaction was notattached internally by CICS.

System actionAn exception trace entry is written. The CMPE task isabnormally terminated.

User responseInvestigate why an attempt was made to run a CICSsupplied deferred rule evaluation task as a usertransaction.

Module:DFHMPDE

AMQA

ExplanationDFHMQCON had enabled DFHMQTRU with a globalwork area smaller than that needed by DFHMQTRU.This could be due to a mismatch of version levelbetween DFHMQCON and DFHMQTRU.


User responseCheck that the versions of DFHMQCON andDFHMQTRU are compatible. If you are unable to solvethe problem, contact your IBM support center.

Module:DFHMQTRU

AMQB

ExplanationDFHMQCON had enabled DFHMQTRU with a task localwork area smaller than that needed by DFHMQTRU.This could be due to a mismatch of version levelbetween DFHMQCON and DFHMQTRU.



User responseCheck that the versions of DFHMQCON andDFHMQTRU are compatible. If you are unable to solvethe problem, contact your IBM support center.

Module:DFHMQTRU

AMQC

ExplanationUnrecognizable WebSphere MQ API call. All supportedAPI calls are documented in the IBM MQ applicationsreference manual.


User responseSee the IBM MQ applications reference manual fordetails of the supported WebSphere MQ API.

Module:DFHMQTRU

AMQD

ExplanationUnrecognizable RMI API call. The CICS-MQ taskrelated user exit (TRUE) was invoked with anunrecognizable request type.



Module:DFHMQTRU

AMQE

ExplanationAn attempt to EXEC CICS LOAD the data conversionservice module CSQAVICM was unsuccessful.


User responseEnsure that the WebSphere MQ SCSQAUTH library hasbeen specified in the CICS DFHRPL concentation andthat CSQAVICM is defined as a program to CICS. Adefinition for CSQAVICM is supplied in the DFHMQ CSDgroup.

Module:DFHMQCON

AMQF

ExplanationAn internal logic error has been detected in the CICSbridge monitor.

System actionMessage DFHMQ0750 is written to the CICS CSMTtransient data queue and the CICS bridge monitor taskis ended abnormally.

User responseSee the description of message DFHMQ0750 for moreinformation.

Module:DFHMQBR0

AMQG

ExplanationThe CICS DPL bridge program has detected an error ina request message for this unit of work.

System actionAll request messages for this unit of work arecopied to the dead-letter queue with an MQFB_CICS_*reason code. Corresponding error messages arewritten to the CICS CSMT transient data queue. AnMQCRC_BRIDGE_ERROR reply is sent to the reply-toqueue if requested. The CICS bridge task is endedabnormally.

User responseSee the description of the accompanying messages formore information.

Module:DFHMQBP0

AMQH


https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.ref.dev.doc/q089580_.htm



ExplanationThe CICS bridge monitor or DPL bridge programabended due to an unexpected return code from anEXEC CICS API call.

System actionMessage DFHMQ0704 is written to the CICS CSMTtransient data queue and the CICS bridge monitor orDPL bridge program is abnormally terminated.


Module:DFHMQBR2

AMQI

ExplanationThe CICS bridge monitor or DPL bridge programabended due to an unexpected return code from anWebSphere MQ API call.

System actionMessage DFHMQ0710 is written to the CICS CSMTtransient data queue and the CICS bridge monitor orDPL bridge program is abnormally terminated.


Module:DFHMQBP2

AMQJ

ExplanationThe CICS DPL bridge program abended beforeprocessing any messages for the unit of work.

System actionAll request messages for this unit of work are left onthe CICS bridge queue to be handled by the CICSbridge monitor.

User responseSee the description of the accompanying messages formore information.

Module:

DFHMQBP2

AMQK

ExplanationThe CICS DPL bridge program abended during errorprocessing.

System actionAn unexpected error occurred during CICS DPL bridgeerror processing.

User responseSee the description of the accompanying messagesfor more information. If the problem reoccurs, contactyour IBM support center.

Module:DFHMQBP2

AMQM

ExplanationDFHMQBP0 attempted to process a Link3270 bridgerequest but received an unspecified error. This abendcode is only ever issued within message DFHMQ0778.

System actionInput messages are backed out to the backout-requeue queue or dead-letter queue.

User responseExamine the CICS log immediately prior to theDFHMQ0778 message for further information on thetype of error encountered. If the problem reoccurs,contact your IBM support center.

Module:DFHMQBP0

AMQN

ExplanationThe Link3270 bridge has returned one or more bridgevectors. DFHMQBP0 has detected that one of thebridge vector lengths is invalid.

System actionThe transaction is abended. Input messages arebacked out to the backout-requeue queue or dead-letter queue.


User responseCheck whether a transaction HANDLE ABEND routinehas recovered from a 3270 Bridge abend andsuppressed the abend. If this is the case the HANDLEABEND routine should be coded to allow the 3270Bridge abend to continue by reissuing the abend. If theproblem reoccurs, contact your IBM support center.

Module:DFHMQBP0

AMQO

ExplanationAn attempt has been made to invoke DFHMQTSK usinga transaction identifier that is not CKTI.

System actionThe transaction is abended.

User responseDo not attempt to invoke program DFHMQTSK as auser transaction.

Module:DFHMQTSK

AMQT

ExplanationTemporary storage queue DFHCKBR is required butthe TSModel definition for it does not exist.

System actionThe transaction is abended.

User responseEnsure the TSModel definition for DFHCKBR is presentin RDO group DFHMQ.

Module:DFHMQBR0

AMSA

ExplanationAn input data stream received from a 3270 begins witha set buffer address (SBA) order but is not followedby two 1-byte address fields. This is probably due to ahardware error.


User responseIt may be possible to bypass the problem by enteringtwo spaces before the data to be entered.

If the problem persists, you need further assistance.See Working with IBM to solve your problem forguidance on how to proceed.

Module:DFHMSP

AMSB

ExplanationAn internal logic error has been detected in moduleDFHMSP.


User responseRetry the CMSG transaction, specifying operands in adifferent order. If this fails, keep the dump and contactyour IBM Support Center.

Module:DFHMSP

AMSC








Module:DFHMSP

AMSD

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call to

the storage manager (SM) domain. The domain thatdetected the original error provides an exception trace,a console message and, possibly, a system dump(depending on the options specified in the dumptable).


User responseSee the related error message produced by thedomain that detected the original error.

Module:DFHMSP

ANxx abend codesANJ1

ExplanationAn attempt has been made to run the CICS internaltask CNJL as a user transaction.


User responseInvestigate why the attempt was made to run CNJL asa user transaction.

Module:DFHSJNS

ANJ2

ExplanationAn unexpected error was encountered in the CNJLtransaction.


User responseInvestigate why the CNJL task failed.

Module:DFHSJNS

ANJ3

ExplanationAn attempt has been made to run the Node.js workertask CNJW as a user transaction.


User responseInvestigate why the attempt was made to run CNJW asa user transaction.

Module:DFHSJNW

ANJ4

ExplanationAn unexpected error was encountered processing alocal Node.js call to CICS


User responseInvestigate why the task failed.

Module:DFHSJNW


ANQA

ExplanationAn error has occurred obtaining a lock within theenqueue domain.

System actionThe recovery routine of the module in control isinvoked which issues message DFHNQ0002 with asystem dump. DFHNQ0002 reports the module incontrol at the time of the error.

User responseSee the description of message DFHNQ0002 forfurther guidance.

Module:DFHNQED, DFHNQIB, DFHNQNQ, DFHNQST

ANQB

ExplanationAn error has occurred releasing a lock within theenqueue domain.

System actionThe recovery routine of the module in control isinvoked. This routine issues message DFHNQ0002with a system dump. DFHNQ0002 reports the modulein control at the time of the error.


Module:DFHNQED, DFHNQIB, DFHNQNQ, DFHNQST

ANQC

ExplanationAn error has occurred obtaining a sysplex enqueue.The limit for the number of concurrent sysplexresource ENQ requests has been reached.

System actionModule DFHNQED issues message DFHNQ0103 andthe task issuing the EXEC ENQ request is abended.


Module:DFHNQED

ANQD

ExplanationAn error has occurred obtaining a sysplex enqueue. Anunexpected environmental error has been detected.

System actionModule DFHNQED issues message DFHNQ0104 andthe task issuing the EXEC ENQ request is abended.


Module:DFHNQED

ANQE

ExplanationAn EXEC ENQ has been issued on a resource for whichthe enqmodel is either disabled or in the waiting state.

System actionModule DFHNQRN issues message DFHNQ0105 andthe task issuing the EXEC ENQ request is abended.


Module:DFHNQRN

ANQF

ExplanationAn EXEC CICS ENQ request has been issued too earlyduring transaction initialization, before a recoverabletransaction environment has been established.



User responseThis error should only occur when an exit such as the3270 Bridge Exit is executing. If the exit program iswritten in a high level language, the ENQ may havebeen issued by Language Environment.

Module:DFHEKC

ANSA

ExplanationAn error has occurred obtaining the numberspace lockwithin the AP domain.

System actionThe recovery routine of the module in control isinvoked which issues message DFHAP0002 with asystem dump. DFHAP0002 reports the module incontrol at the time of the error.

User responseSee the description of message DFHAP0002 forfurther guidance.

Module:DFHBRNS

ANSB

ExplanationAn error has occurred releasing a lock within the APdomain.

System actionThe recovery routine of the module in control isinvoked which issues message DFHAP0002 with asystem dump. DFHAP0002 reports the module incontrol at the time of the error.

User responseSee the description of message DFHAP0002 forfurther guidance.

Module:DFHBRNS

AOxx abend codesAOTA

ExplanationThe OT domain resynchronization transaction CJTRhas been started in an incorrect manner (for example,from a user terminal, or by a start request). This is notpermitted.


User responseNone. The OT domain resynchronization transactionmust be started internally by CICS.

Module:DFHOTR

AOTB

ExplanationAn unexpected error was encountered by the OTdomain resynchronization transaction CJTR. Thedomain that detected the original error will haveprovided an exception trace, a console message and,possibly, a system dump (depending on the optionsspecified in the dump table).



Module:DFHOTR


APxx abend codesAPC0

ExplanationA serious error occurred in a call to the programmanager domain when trying to link a system program.


User responseUse the dump to investigate why the error occurred.Look at the trace records prior to the error forabnormal conditions in processing the PGLK domaincall. This may be due to a problem with directorymanager, loader, or storage manager. Check theprogram size. It may be necessary to increase theoverall size limits of the DSAs or EDSAs.

Module:DFHEICRE, DFHEIG, DFHEIP, DFHEIQCS, DFHPCP,DFHMCY

APC1

ExplanationA request for a TGT exceeding 64KB has beendetected.

System actionCICS abnormally terminates the transaction anddisables the installed program definition.

User responseChange the application program to reduce the workingstorage requirement. Perform CEMT NEWCOPY andENABLE for the program when it has been corrected.

Module:DFHAPLI

APC2

ExplanationAn illegal branch has been attempted by a LanguageEnvironment user program following an abendcondition with an active handle label abend. Usuallyan Out-Of-Block GOTO will have resulted, implyingthat the program tried to branch to, for example, aninactive block.

System actionThe transaction is abnormally terminated and theprogram is disabled.

User responseUse the dump and trace to determine the cause of theerror and amend the GOTO in error.

Module:DFHAPLI

APC3

ExplanationAn attempt to run the program has failed becauseCICS has identified the program as 'LanguageEnvironment enabled' but Language Environmentsupport is not present in the system.


User responseRefer to messages issued during CICS initialization todetermine why Language Environment is not presentin the system.

Module:DFHAPLI

APCF

ExplanationA CICS task has invoked a program which was definedas PL/I, but the program was not compiled with asupported PL/I compiler, or the program may not bewritten in the PL/I language.

System actionCICS terminates the task, and disables the program.

User responseCheck that the program is PL/I. If the program is PL/I,recompile it with a Language Environment conformingcompiler such as Enterprise PL/I for z/OS, in whichcase you might need to change the source program. Ifthe program is not PL/I, redefine it correctly.

Module:DFHAPLI


APCG

ExplanationThe transaction was purged either by main terminalactions or due to deadlock timeout actions as part ofa request to the loader for a usable program copy.Deadlock timeout could be caused by a programwhose size exceeds the available space in the DSAsor EDSAs.


User responseUse the dump to investigate why the transactionwas purged. This may be due to waiting for loaderresources or for program storage. Check the programsize. It may be necessary to increase the overall sizelimits of the DSAs or EDSAs.


Module:DFHACP, DFHCRNP, DFHCRSP, DFHDBCT, DFHDBDSC,DFHEDFP, DFHEIG, DFHEIP, DFHEICRE, DFHEIQCS,DFHEIPSH, DFHEIQIR, DFHEIQSJ, DFHFCRP, DFHFEP,DFHICP, DFHKCQ, DFHMCP, DFHMCPE, DFHMCY,DFHMSP, DFHPCPG, DFHPHP, DFHPSIP, DFHPUP,DFHRDCAL, DFHRTC, DFHSII1, DFHSIJ1, DFHSPP,DFHSTP, DFHTACP, DFHTBSGB, DFHTCRP, DFHTDX,DFHTFP, DFHTSPA, DFHTSRP, DFHUSBP, DFHXRCP,DFHXRE, DFHXRSP, DFHZATA, DFHZATD, DFHZCPLN,DFHZGAI, DFHZQ00, DFHZNCA, DFHZOPA, DFHZXCU

APCH

ExplanationA request for a program which CICS has identifiedas VS COBOL II cannot be executed because eitherLanguage Environment is not active in this addressspace or Language Environment cannot providesupport for the COBOL language.


User responseEnsure that the correct Language Environment supportis present. Refer to messages issued during CICSinitialization to determine why COBOL support is notpresent.

Module:

DFHAPLI

APCI

ExplanationA request for a program which CICS as identifiedas an OS/PLI program cannot be executed becauseeither Language Environment is not active in thisaddress space or Language Environment cannotprovide support for the PL/I language.


User responseEnsure that the correct Language Environment supportis present. Refer to messages issued during CICSinitialization to determine why PL/I support is notpresent.

Module:DFHAPLI

APCJ

ExplanationA request for a C/370 program could not be executedeither because Language Environment was unable torecognize the program as having been compiled underthe C/370 Compiler, or because the program was notlink-edited with the attribute AMODE(31).


User responseEnsure that the program is link-edited with theattribute AMODE(31). If necessary, recompile theprogram with a Language Environment conformingcompiler such as OS/390 C/C++.

Module:DFHAPLI

APCK

ExplanationA request for a C program could not be honoredeither because Language Environment is not active inthis address space or because Language Environmentcannot provide support for the C language.



System actionThe transaction is terminated abnormally and theprogram is disabled.

User responseEnsure that the correct Language Environment supportis present. Refer to messages issued during CICSinitialization to determine why C support is notpresent.

Module:DFHAPLI

APCL

ExplanationA request for a program which CICS has identifiedas 'LE-enabled' has failed because LanguageEnvironment is unable to execute the program.


User responseEnsure that the program has been compiled eitherwith a Language Environment conforming compileror with a compiler which is supported by LanguageEnvironment in compatibility mode. Refer to theLanguage Environment Migration Guide to verify thisconformance.

If the compiler is supported, and the relevantlanguage migration guides do not indicate any specialactions, refer this problem to your installation systemsprogramming facility.

Module:DFHAPLI

APCN

ExplanationAn attempt to release an internal CICS program,a mapset, or a partitionset because the program,mapset or partitionset has not been loaded or hasalready been deleted. This is probably an internal CICSerror.

System actionThe transaction is abnormally terminated with a CICStransaction dump. The name of the program for whichthe RELEASE was attempted can be found in theabend dump at TCAPCPI.

User responseThis is either an internal CICS error or is due to theoverwriting of CICS internal control blocks. If you needfurther assistance from IBM to resolve this problem,see Working with IBM to solve your problem forguidance on how to proceed.


Module:DFHAMPEN, DFHFEP, DFHMCP, DFHMCPE, DFHMCY,DFHPHP, DFHTBSSP, DFHZCPLN

APCO

ExplanationA GETMAIN of storage for LEVEL 2 trace failed duringtransaction initialization.



Module:DFHAPXM

APCS

ExplanationAn attempt to run the program failed becauseCICS was unable to make a successful connectionwith Language Environment to determine the run-time characteristics of the program. This abend isaccompanied by message DFHAP1200 which gives thereason code set by Language Environment indicatingthe nature of the error.


User responseRefer to the Language Environment z/OS LanguageEnvironment Debugging Guide manual for the meaningof the reason code, and take whatever action isnecessary to correct the error.

Module:DFHAPLI

APCT




https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ceea100/abstract.htm

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ceea100/abstract.htm

ExplanationOne of the following has occurred:

1. The program name in the EXEC CICS HANDLEABEND program is not usable at the time an abendoccurs because:

• The program is not on the relocatable programlibrary (RPL).

• The program is disabled.• The program cannot be loaded.

2. An attempt to load a mapset or partitionset failedbecause although the program is defined to CICS

• It is not available on the RPL, or• It is disabled, or• It cannot be autoinstalled.

3. An attempt to link to, load, or release an internalCICS program failed because:

• The program is not on the RPL.• The program is disabled.• The program cannot be loaded.

System actionThe transaction requiring the program is abnormallyterminated with a CICS transaction dump.

User responseIn cases 1 and 2, define the program, mapsetpartitionset to CICS using CEDA and ensure it isenabled.

In case 3, the definition of a CICS-provided moduleis incorrect. Check for associated messages issuedduring CICS start up.


Problem determinationThe trace preceding the abend indicates the program,mapset, or partitionset that could not be loaded,linked to, or released. The name is also in TCAPCEPI.

Module:DFHACP, DFHAMPEN, DFHCRSP, DFHEDFP, DFHEIG,DFHEIP, DFHEICRE, DFHEIPSH, DFHEIQCS,DFHEIQSJ, DFHFEP, DFHICP, DFHMCP, DFHMCPE,DFHMCY, DFHMELDE, DFHPCPG, DFHPHP, DFHPUP,DFHRDCAL, DFHSII1, DFHTBSGB, DFHTFP, DFHTSRP,DFHZCPLN, DFHZQ00, DFHZXCU

APCW

ExplanationThe program language is defined as COBOL but thelevel of the compiler under which it is compiledcannot be determined. Most probably, the programwas compiled under an OS/VS COBOL compiler butthe required level of support for that compiler is notpresent in the system.


User responseThe program source will need to be converted andcompiled with a Language Environment conformingCOBOL compiler such as Enterprise COBOL.

Module:DFHAPLI

APCY

ExplanationIn an MVS/ESA environment, a CICS macro requesthas been issued from a PL/I or COBOL application.Alternatively, it is possible that the applicationprogram has been link edited without the EXECinterface module (for example, DFHECI or DFHELII)which is used by the CICS high-level languageprogramming interface. See the Configuring for detailsof what has to be done to include this module.


User responseRemove the macro request from the applicationprogram.

Module:DFHAPLI

APCZ

ExplanationAn attempt has been made to run an 'old-style'application program (that is, a program with a pre-release 1.6 or a DFHE program stub) that has beenlink-edited with the RENT or REFR attributes. Thesetypes of programs are not reentrant and thereforecannot be loaded into read-only storage.



https://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/configuring/configuring.html


User responseRelink the program without the RENT and REFRattributes.

Module:DFHAPLI

APGA

ExplanationAn error has occurred obtaining a lock within theProgram Manager domain.


User responseContact your local IBM support center for assistance.

Module:DFHPGAI, DFHPGAQ, DFHPGDD, DFHPGDM,DFHPGEX, DFHPGIS, DFHPGLD, DFHPGLE, DFHPGLK,DFHPGLU, DFHPGPG, DFHPGRE, DFHPGRP, DFHPGST,DFHPGUE, DFHPGXE, DFHPGXM

APGB

ExplanationAn error has occurred releasing a lock within theProgram Manager domain.



Module:DFHPGAI, DFHPGAQ, DFHPGDD, DFHPGDM,DFHPGEX, DFHPGIS, DFHPGLD, DFHPGLE, DFHPGLK,DFHPGLU, DFHPGPG, DFHPGRE, DFHPGRP, DFHPGST,DFHPGUE, DFHPGXE, DFHPGXM

APGC

ExplanationA transaction has tried to allocate an excessiveamount of storage for containers. A transaction mustnot allocate more than 5% of the storage available forholding containers above the bar.

System actionCICS issues message DFHPG0400, and abnormallyterminates the task. CICS processing continues.

User responseIf the program is incorrect, correct it to allocate lesscontainer storage. If the program is correct, increaseMEMLIMIT so that the program does not use morethan 5% of the storage available.

Module:DFHPGCR

APGD

ExplanationThe entry point of an assembler application programindicates that it is AMODE(64), but the AMODE(64)CICS stub program, DFHEAG, is not included at thefront of the load module.


User responseFor an AMODE(64) assembler application program,ensure that the binder places the AMODE(64) CICSstub, DFHEAG, at the front of the load module.You can use the CICS-supplied procedure DFHEGTALto translate, assemble and bind the AMODE(64)program. .p:If the assembler application program isnot AMODE(64), change any AMODE 64 statements inthe program or the binder job to the correct AMODE.You can use the CICS-supplied procedure DFHEITALto translate, assemble and bind the AMODE(24) orAMODE(31) program.

Module:DFHAPLI3

APGE

ExplanationThe AMODE(64) CICS stub program, DFHEAG, isincluded at the front of the load module, but the entry


point of the assembler application program indicatesthat it is not AMODE(64).


User responseFor an AMODE(24) or AMODE(31) assemblerapplication program, ensure that the binder places theDFHEAI stub program at the front of the load module.You can use the CICS-supplied procedure DFHEITALto translate, assemble and bind the AMODE(24) orAMODE(31) program.

For an AMODE(64) assembler application program,change any AMODE statements in the program orthe binder job to AMODE 64. If there are no AMODEstatements then include an AMODE 64 statement inthe program, the binder job, or both, you can usethe CICS-supplied procedure DFHEGTAL to translate,assemble and bind the AMODE(64) program.

Module:DFHAPLI3

APIA

ExplanationThe transaction id (CPIH) of the Pipeline InboundHTTP router program has been initiated invalidly,probably by entering the id at a terminal. Thistransaction must only be initiated by CICS internalprocesses.


User responseDo not initiate CPIH directly.

Module:DFHPIDSH

APIB

ExplanationThe Pipeline outbound router program received anerror response from the Pipeline Manager when itstarted the pipeline.

System actionThe outbound router program is abnormallyterminated.

User responseExamine the trace and associated messages todetermine why the Pipeline Manager failed to startsuccessfully.

Module:DFHPIRT

APIC

ExplanationThe Pipeline HTTP outbound router program receivedan error response from its attempt to do an EXECCICS GET CONTAINER call to obtain the pipeline namefrom the DFHWS-PIPELINE container. Both a trace andmessage DFHPI0998 are issued and these will be anindication of what the error was. If the trace pointid is '09DD'x then a CONTAINERERR was returnedto DFHPIRT. A point id of '09DE'x indicates that aLENGERR was returned.

System actionThe outbound router program is abnormallyterminated.

User responseExamine the trace and associated messages todetermine why the Pipeline failed to start successfully.

Module:DFHPIRT

APIG

ExplanationA provider mode Web service invocation has failed.This may be due to a problem whilst processing aSOAP request message or generating a SOAP responsemessage.

System actionCICS abends the transaction and a SOAP Faultmessage is sent to the requester.

User responseExamine the CICS trace for exception traces issuedfrom DFHPITL. These will identify the source of thefailure. If validation is currently disabled for the failing


WEBSERVICE then consider enabling it and reproducethe problem. This causes CICS to call a Java basedprogram to validate the SOAP message against theWSDL for the WEBSERVICE. If the SOAP message ismalformed then a message will be issued to describethe problem in more detail.

Module:DFHPITP

APIH

ExplanationThe transaction id (CPIL) of the Pipeline WebSphereMQ Listener program has been initiated invalidly,probably by entering the id at a terminal. Thistransaction must only be initiated by being triggeredby an inbound WebSphere MQ message.


User responseDo not initiate CPIL directly.

Module:DFHPILSQ

APII

ExplanationAn attempt has been made to use WebSphere MQas the transport for CICS Web Services, but theWebSphere MQ stub CSQCSTUB could not be loadedduring CICS Initialisation. The WebSphere MQ libraryCSQCLOAD needs to be included in the DFHRPLconcatenation to permit use of WebSphere MQ as atransport for CICS Web Services

System actionThe attempt to use WebSphere MQ as a transportfor CICS Web Services has been rejected. Any furthersuch attempts will also be rejected.

Message DFHAP0900 is produced.

The task is abnormally terminated with a CICStransaction dump.

User responseThe WebSphere MQ library CSQCLOAD must beincluded in the DFHRPL concatenation to allow use ofWebSphere MQ as a transport for CICS Web Services.

This is in addition to the other WebSphere MQ librariesneeded for WebSphere MQ support in CICS.

Module:DFHPILSQ

APIJ

ExplanationA WebSphere MQ function call issued by transactionCPIL was unsuccessful and has set a non-zero reasoncode. The transaction CPIL is used to start a PIPELINEfor a message received from WebSphere MQ.

System actionMessage DFHPI0111 is produced, which includes theWebSphere MQ reason code. The task is abnormallyterminated with a CICS transaction dump.

User responseCheck the WebSphere MQ reason code in the IBM MQmessages manual, and examine the trace to determinewhy the WebSphere MQ function call failed. You mayneed help from IBM to resolve this problem.

Module:DFHPILSQ

APIK

ExplanationThe CICS supplied SOAP Handler received anunexpected response from another module.

System actionCICS attempts to run the pipeline in an error mode. Nodump is taken.

User responseExamine the CICS joblog for associated messages.

Module:DFHPISN

APIL

ExplanationThe CICS supplied SOAP Handler has failed with adisaster response.

System actionCICS attempts to run the pipeline in an error mode. Adump is taken.


https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.ref.doc/q050250_.htm

https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.ref.doc/q050250_.htm

User responseKeep the dump and contact your IBM Support Center.

Module:DFHPISN

APIM

ExplanationThe transaction id (CPIQ) of the Pipeline InboundWebSphere MQ router program has been initiatedinvalidly, probably by entering the id at a terminal.This transaction must only be initiated by CICS internalprocesses.


User responseDo not initiate CPIQ directly.

Module:DFHPIDSQ

APIN

ExplanationThe Web Services Atomic Transaction (WS-AT) handlerhas detected a problem. The transaction id (CPIS) ofthe Pipeline WSAT resync program has been initiatedinvalidly, probably by entering the id at a terminal.This transaction must only be initiated by CICS internalprocesses.


User responseDo not initiate CPIS directly.

Module:DFHPIR

APIO

ExplanationThe Web Services Atomic Transaction (WS-AT) handlerhas detected a problem. The WSAT RegistrationServices program has encountered an error, whichhas prevented it from completing the processing of aregistration or 2PC protocol request. The program isabnormally terminated.

System action:

User responseExamine the trace and associated messages todetermine why the Registration Services program hasfailed.

Module:DFHPIRS

APIP

ExplanationThe Web Services Atomic Transaction (WS-AT) handlerhas detected a problem. The WSAT CoordinationContext header handler program has encounteredan unrecoverable error, which has prevented it fromsuccessfully creating or processing a coordinationcontext. The program is abnormally terminated.

System action:

User responseExamine the trace and associated messages todetermine why the Coordination Services program hasfailed.

Module:DFHWSATH

APIQ

ExplanationThe Web Services Atomic Transaction (WS-AT) handlerhas detected a problem. The WSAT application handlerprogram has encountered an unrecoverable error,which has prevented it from creating or processinga registration message or a protocol message. Theprogram is abnormally terminated.

System action:

User responseExamine the trace and associated messages todetermine why the Registration/Protocol Servicesprogram has failed.

Module:DFHWSATX.

APIR

ExplanationThe Web Services Atomic Transaction (WS-AT) handlerhas detected a problem. The WSAT application handlerprogram has encountered an attempt to use one-waymessages in a WS-AT message. This combination is


not permitted in WS-AT. The program is abnormallyterminated.

System action:

User responseExamine the trace and associated messages todetermine which messages are at fault.

Module:DFHWSATH.

APIS

ExplanationCICS encountered a GETMAIN failure duringtransaction initialization.

System actionA severe error message and system dump should havepreceeded this abend.

User responseUse related diagnostics to determine the cause of theproblem.

Module:DFHPIXM.

APIT

ExplanationThe Web Services Atomic Transaction (WS-AT) handlerhas detected a problem. The attempt to resynchronizeoutstanding units of work has failed.


User responseInvestigate why the UOWs cannot be resynchronized.

Module:DFHPIR

APIU

ExplanationThe Pipeline WebSphere MQ Listener program hasencountered an attempt to parse a target URI that islonger than 255 bytes. The maximum length of a targetURI in the RFH2 header is expected to be 255 bytes.

System actionThe program is abnormally terminated.

User responseExamine the trace and associated messages todetermine which messages are at fault.

Module:DFHPILSQ.

APL0

ExplanationAbend codes with 'PL' as the middle two charactersare issued by PL/I, and are described in further detailin the Enterprise PL/I for z/OS Programming Guide.

System action:

User response:

Module:

APL1


System action:

User response:

Module:

APL2


System action:

User response:

Module:

APL3


System action:

User response:

Module:


https://www.ibm.com/support/knowledgecenter/SSY2V3_5.2.0/com.ibm.ent.pl1.zos.doc/pg/preface_plugin.html




APL4


System action:

User response:

Module:

APL5


System action:

User response:

Module:

APL6


System action:

User response:

Module:

APL7


System action:

User response:

Module:

APL8


System action:

User response:

Module:

APL9


System action:

User response:

Module:

APLA


System action:

User response:

Module:

APLB


System action:

User response:

Module:

APLC


System action:

User response:

Module:

APLD


System action:












User response:

Module:

APLE


System action:

User response:

Module:

APLF


System action:

User response:

Module:

APLG


System action:

User response:

Module:

APLH


System action:

User response:

Module:

APLI


System action:

User response:

Module:

APLJ


System action:

User response:

Module:

APLK


System action:

User response:

Module:

APLL


System action:

User response:

Module:

APLM


System action:

User response:

Module:

APLN












System action:

User response:

Module:

APLO


System action:

User response:

Module:

APLP


System action:

User response:

Module:

APLQ


System action:

User response:

Module:

APLR


System action:

User response:

Module:

APLS


System action:

User response:

Module:

APLT


System action:

User response:

Module:

APLU


System action:

User response:

Module:

APLV


System action:

User response:

Module:

APLW


System action:

User response:












Module:

APLY


System action:

User response:

Module:

APLZ


System action:

User response:

Module:

APLX


System action:

User response:

Module:

APP1

ExplanationThe DFHIC TYPE=GET response code was not anormal response.

System actionThe transaction is abnormally terminated with a CICStransaction :i1.DFHP3270 abend codes dump.

User responseAnalyze the dump. The response code is in the low-order byte of register 0.

Module:DFHP3270

APP2

ExplanationThe length of data that has been passed to DFHP3270via temporary storage is less than or equal to 5.


User responseCheck the user DFHTEP. If it is not at fault, submit anAPAR.

If this abend has occurred, the data that DFHP3270obtained from temporary storage was probably putthere with an incorrect length. The user may haverequested indirectly that this data be placed intemporary storage either by an application requestfor printing (for example ISSUE PRINT) or by pressingthe Print Request key. However, CICS should controlthe data length for this request. Under normalcircumstances, the only way the user could haverequested directly that data is to be placed intemporary storage is in the user's TEP. The usershould check any invocations of DFHIC TYPE=PUT inhandling print requests, particularly when dealing withthe "printer unavailable or busy" condition, and ensurethat the length field is set correctly.

Problem determinationRegister 6 points to the data retrieved from temporarystorage via a DFHIC TYPE=GET macro invocation. Thelayout of this data is:

• Terminal data area length (2 bytes)• Write control indicator (1 byte)• Write control or carriage control character (1 byte)• Data (variable length)

Analysis: DFHP3270 has been called to handle aprint request from a 3270 Information Display Systemterminal. It obtains from temporary storage the datato be printed, via a DFHIC TYPE=GET invocation. Itensures that some data to be printed is present. Thearea returned from temporary storage contains thedata to be printed preceded by 4 bytes as describedabove. DFHP3270 has found that, because the lengthof data passed to it is less than or equal to 5, there isno data to be printed.

Module:DFHP3270

APP3





ExplanationAn attempt to request data has been sent to anonprinter or unsupported device type by either:

• A terminal operator entering CSPP as a transactioncode, or

• A transaction issuing a DFHTEP request.

System actionThe transaction is abnormally terminated. A CICStransaction dump is not provided.

User response1. Ensure that the terminal operator ceases to use

CSPP as a transaction code, or2. Correct the user DFHTEP program.

Module:DFHP3270

APR1

ExplanationAn abnormal DFHIC TYPE=PUT response code wasreceived during print key processing.


User responseAnalyze the dump. The response code is in low-orderbyte of register 0.

Module:DFHPRK

APSJ

ExplanationThe abending transaction invoked the system spoolerinitialization program (DFHPSIP) illegally, that is from aprogram other than the CICS module, DFHSIJ1.

System actionCICS terminates the transaction abnormally. The EXECCICS HANDLE ABEND command can not handle thisabend.

User responseRemove any calls or links to DFHPSIP from yourapplication programs. If you can find no invocationof DFHPSIP in your application, you need furtherassistance to resolve this problem. See Working withIBM to solve your problem for guidance on how toproceed.

Module:DFHPSIP

APST

ExplanationA task issued a SPOOL command without themandatory NOHANDLE operand.


User responseCorrect the syntax of the command, specifyingNOHANDLE.

Module:DFHEPS

APSU

ExplanationThe CICS SVC passed an invalid JES interface returncode to the CICS system spooler (an MVS subtask).


User responseThis is an internal error - check any JES failures thatoccurred at the same time.


Module:DFHPSPST

APSV

ExplanationA storage area for VSAM macro return codes containedan invalid value.






User responseCheck the syntax and input data of the spoolcommands issued by the failing transaction. Check anyJES failures that occurred at the same time.

Module:DFHPSPST

APSW

ExplanationAn abend occurred within a CICS system spoolersubtask.


User responseThis is an internal CICS error. If you need furtherassistance from IBM to resolve this problem, seeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHPSPST

APSX

ExplanationA CICS storage area used for notification of invalidparameters contained an invalid value.



Module:DFHPSPST

APSY

ExplanationA CICS storage area for MVS macro return codescontained an invalid value.



Module:DFHPSPST

APSZ

ExplanationA CICS area, used to store a JES interface return code,contained an invalid value.



This is an internal CICS error. If you need furtherassistance from IBM to resolve this problem, seeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHPSPST

APTI

ExplanationThe task was purged before a GETMAIN request to thestorage manager (SM) domain was able to completesuccessfully. The domain that first detected the purgedcondition will have provided an exception trace.








Module:DFHPSPST

APTJ

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call tothe storage manager (SM) domain. The domain thatdetected the original error will have provided anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).



Module:DFHPSPST

APUA

ExplanationAn internal error was detected when module DFHPUPwas invoked. The GETSTG parameter is missing on acall to DFHPUP (PUPF).





Module:DFHPUP

APUB

ExplanationAn internal error was detected when module DFHPUPwas invoked. The GETSTG parameter is missing on acall to DFHPUP (PUPU).





Module:DFHPUP

APUC

ExplanationAn internal error was detected when module DFHPUPwas invoked. An invalid function code was supplied fora domain call to DFHPUP.





Module:DFHPUP

APUD





ExplanationThe RDO language definition table (DFHEITSP) couldnot be located in the library.




User responseEnsure that module DFHEITSP is in the library and isvalid for this release of CICS.

Module:DFHPUP

APUE

ExplanationThe RDO language definition table (DFHEITSP) couldnot be loaded because of a lack of available storage.

System actionProcessing is abnormally terminated with an operatingsystem dump.

User responseAllocate more storage and resubmit the offline COPYor APPEND command(s) that failed.

Module:DFHPUP (Batch environment)

APUF

ExplanationEither the RDO language definition table is invalid or itis missing from the library.




User responseEnsure that module DFHEITSP is in the library and isvalid for this release of CICS.

Module:DFHPUP

APUG

ExplanationAn internal error was detected in module DFHPUP.Storage could not be obtained for the CSD recordbuffer.





Module:DFHPUP

APUH

ExplanationAn internal error was detected in module DFHPUP.Storage could not be obtained for the argument list.





Module:DFHPUP

APUI

ExplanationAn internal error was detected in module DFHPUP.Storage cannot be freed for the argument list.








Module:DFHPUP

APUJ

ExplanationAn internal error was detected in module DFHPUP.Storage cannot be freed for the CSD record buffer.





Module:DFHPUP

APUK

Explanation• In a CICS environment, storage could not be

acquired for a buffer to contain logged RDOcommands in the CEDA transaction.

• In a batch environment, storage could not beacquired for a buffer to contain back-translatedresource definitions from the CSD.





Module:DFHPUP

APUL

ExplanationNote:

The description of this abend also applies to APUM,APUN and APUO.

CICS cannot find a match for a function code in thelanguage definition table, because the parameterizedresource definition contains an unrecognized resourcetype code.

The abend code issued depends on the DFHPUPoperation that was invoked before the error occurred:

AbendDFHPUP operation

APUL

FLATTEN

APUM

TRANCASE

APUN

COMPARE

APUO

BACKTRANS

The cause of the abend is either:

1. A language definition table (DFHEITSP orDFHEITCU) in the library is invalid for the CICSrelease you are running, or

2. A CICS logic error has occurred.




User responseYour response depends on which of the two possiblereasons apply:





1. Ensure that the DFHEITSP and DFHEITCU modulesin the library are valid for this release of CICS.

2. If you need further assistance from IBM to resolvethis problem, see Working with IBM to solve yourproblem for guidance on how to proceed.

Module:DFHPUP

APUM

ExplanationRefer to the description of abend APUL.

System action:

User response:

Module:DFHPUP

APUN


System action:

User response:

Module:DFHPUP

APUO


System action:

User response:

Module:DFHPUP

APUP

ExplanationAn internal error occurred in DFHPUP processing of thelanguage definition table for RDO. There was a stackerror building a keyword list for the syntax tree.





Module:DFHPUP

APUQ

ExplanationAn internal error occurred in DFHPUP processing of thelanguage definition table for RDO. Too many keywordsfound in syntax expansion.





Module:DFHPUP

APUR

ExplanationAn internal error occurred in DFHPUP processing of anargument list or a CSD record buffer. The data type fora keyword field conflicts with the data type specified inthe language definition table.




User responseEnsure that the module DFHEITSP is in the library andis valid for this release of CICS.

Module:DFHPUP

APUS






ExplanationAn internal error occurred in DFHPUP processing ofa CSD record buffer. The integer data length for akeyword field is invalid.





Module:DFHPUP

APUT

ExplanationAn internal error occurred in DFHPUP processing ofan argument list or a CSD record buffer. The keywordexistence bit number, which is the KEP(1) value inlanguage definition table DFHEITSP, is not valid.





Module:DFHPUP

APUZ

ExplanationCICS has found an unrecognized resource type code ina CSD record. The unrecognized code does not matchany of the function codes in the language definitiontable. This abend can occur for one of the followingreasons:

1. You are using a CICS release that does not supporta type of definition that was created on the CSD fileby a later CICS release.

2. The language definition table (DFHEITSP orDFHEITCU) is invalid for this CICS release.

3. The CSD manager (DFHDMP) has passed an invalidCSD record buffer to DFHPUP. This is a CICSinternal logic error.


abnormally terminated with a CICS transactiondump


User responseDetermine which of the possible reasons caused theerror. If you can eliminate reasons 1 and 2, you canassume that reason 3 applies.

Take action corresponding to the reason you haveestablished as follows:

1. Avoid operations on groups containing definition-types that are unsupported by the CICS release youare running.

2. Ensure that the library contains versions ofDFHEITSP and DFHEITCU that are valid for theCICS release you are running.


Module:DFHPUP

APXA

ExplanationThe user transaction's profile could not be found.

System actionThe task is abnormally terminated with a CICStransaction dump. The user transaction is not started.

User responseCheck that the profile name in the user transactiondefinition is correct, and that this profile has beendefined.

Module:DFHAPXM




ARxx abend codesARCB

ExplanationCICS has attempted to enable a task-related user exit,or a global user exit during initialization, but failedbecause the exit program could not be found.

On all types of start, CICS attempts to enable DFHEDP,the EXEC DLI task-related user exit and DFHLETRU,the language environment task-related user exit. On anemergency restart, CICS enables transaction backoutexit programs as specified by the first two TBEXITSsystem initialization parameters.

On all types of start, CICS attempts to enable filecontrol backout programs as specified by the third,fourth, fifth and sixth TBEXITS system initializationparameters.

System actionCICS issues a message to the console indicatingwhich exit program is involved. CICS initialization thenterminates abnormally with a system dump.

User responseIf the associated message indicates that programDFHEDP could not be found, check that IBM-suppliedgroup DFHEDP is included in the group list used atCICS cold or initial start time.

If the associated message indicates that programDFHLETRU could not be found, check that IBM-supplied group DFHMISC is included in the group listused at CICS cold or initial start time.

For transaction backout exit programs, including thefile control backout programs, ensure the program hasbeen defined and is in a library available to CICS.

If necessary, use the dump to find out why the exitprogram could not be enabled.

Module:DFHRCEX

ARHA

ExplanationThe SAA resource recovery interface has been invokedwith an invalid first parameter. The first parametershould be the code of the function to be performed.This is a CICS internal logic error.



Module:DFHCPIR

ARHB

ExplanationThe SAA resource recovery interface has been invokedwith an invalid number of parameters for the call.

System actionthe transaction is abnormally terminated with a CICStransaction dump.

User responseThe exception trace point produced with thisabend contains the SAA resource recovery verbname that was issued incorrectly. Use this todetermine where the application program was inerror and amend application program accordingly.The Systems Application Architecture CommonProgramming Interface Resource Recovery Reference,SC31-6821, provides a detailed description of theSAA resource recovery verbs and how they should becalled.

Module:DFHCPIR

ARHC

ExplanationThe SAA resource recovery interface has detected anunexpected return code from the syncpoint program.This is a CICS internal logic error.





https://www.ibm.com/support/knowledgecenter/SSB27U_6.4.0/com.ibm.zvm.v53.cn2v0/toc.htm

https://www.ibm.com/support/knowledgecenter/SSB27U_6.4.0/com.ibm.zvm.v53.cn2v0/toc.htm


Module:DFHCPIR

ARLA

ExplanationAn error has occurred obtaining a lock within theResource Lifecycle domain.



Module:DFHRLDM

ARLB

ExplanationAn error has occurred releasing a lock within theResource Lifecycle domain.



Module:DFHRLDM

ARLC

ExplanationAn attempt has been made to run the CICS internaltask CRLR as a user transaction.


User responseInvestigate why the attempt was made to run CRLR asa user transaction.

Module:DFHRLRP

ARLD

ExplanationThe Resource Lifecycle resolution transaction, CRLR,experienced a failure.



Module:DFHRLRP

ARM0

ExplanationAn attempt was made to attach a transactionspecifying DFHRMXN3 as the program to be givencontrol, but the transaction was not internally attachedby CICS.

DFHRMXN3 is for use by CICS system transactionCSKP. This provides support for activity keypoints,


User responseEstablish why an attempt was made to attach CSKPincorrectly, or why a transaction definition specifiedDFHRMXN3 as the program to be given control.

Module:DFHRMXN3

ARP2

ExplanationThe server controller detected an internal error duringCICS ONC RPC enable processing.




System actionOne of the following messages is issued: DFHRP0508,DFHRP0509, DFHRP0528, DFHRP0529, DFHRP0590,DFHRP0591.

User responseSee the user response for the message.

Module:DFHRPMS

ARP4

ExplanationThe server controller has performed an exceptiondisable because of an internal error.

System actionOne of the following messages is issued: DFHRP0503,DFHRP0559, DFHRP0697, DFHRP0726, DFHRP0728,DFHRP0730, DFHRP0741.

User responseYou need further assistance from IBM to resolve thisproblem. See External Interfaces Guide and Workingwith IBM to solve your problem for guidance on how toproceed.

Module:DFHRPMS

ARP5

ExplanationAn invalid attempt was made to start the servercontroller.

System actionThe following message is issued: DFHRP0640.


Module:DFHRPMS

ARP9

ExplanationThere was not enough storage for the connectionmanager.

System actionNone.


Module:DFHRPC01

ARPA

ExplanationAn unexpected response from DFHSUSN has occurredwhen trying to sign off a user of the CRTE transactionin the target system when processing a CANCELrequest.

This abend can be caused by incorrect use of theVTAM VARY INACT command. Otherwise it indicatesthat there may be an error in CICS.

System actionThe CSSF transaction (CRTE cancel processortransaction) is terminated with an ARPA abend.

User responseEnsure that the VTAM VARY inact command is usedcorrectly. If this is not the cause of the abend, youneed further assistance from IBM to correct thisproblem. See Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHRTC

ARPF

ExplanationThe alias could not be initialized.

System actionOne of the following messages is issued: DFHRP0103,DFHRP0104, DFHRP0106, DFHRP0108, DFHRP0109.


Module:DFHRPAS

ARPG







ExplanationThe alias was not able to link to the CICS programor the Encode function of the converter one of thefollowing reasons:

• The userid supplied for the alias was not valid.• The CICS program is not defined as a resource to the

external security manager.• The CICS program name is not valid.• The CICS program was on a different system from

CICS ONC RPC, and the specified system name wasnot valid.

• The converter program name was not valid.• The converter program is defined as remote.• The alias is not authorized to use the converter

System actionOne of the following messages is issued: DFHRP0121,DFHRP0131, DFHRP0138, DFHRP0139, DFHRP0141,DFHRP0156, DFHRP0157, DFHRP0159.


Module:DFHRPAS

ARPH

ExplanationThe alias detected a global work area error.



Module:DFHRPAS

ARPI

ExplanationThe alias detected a logic error.

System actionOne of the following messages is issued: DFHRP0107,DFHRP0133, DFHRP0135, DFHRP0137, DFHRP0143,DFHRP0144, DFHRP0148, DFHRP0149, DFHRP0155,DFHRP0164, DFHRP0168, DFHRP0170.


Module:DFHRPAS

ARPJ

ExplanationThe alias ends for one of the following reasons:

• An unexpected response was received from CICSduring transaction initialization.

• The external security manager is no longer available.• The remote CICS region in which the CICS program

was running abended.• The CICS program, which was running in a remote

CICS region, abended.• The reply could not be sent to the client.

System actionOne of the following messages is issued: DFHRP0105,DFHRP0132, DFHRP0136, DFHRP0140, DFHRP0145,DFHRP0146, DFHRP0147, DFHRP0150, DFHRP0165,DFHRP0166, DFHRP0167.


Module:DFHRPAS

ARPK

ExplanationThe alias detected a CICS logic error.

System actionOne of the following messages is issued: DFHRP0102,DFHRP0122, DFHRP0142, DFHRP0160.


Module:DFHRPAS

ARPL

ExplanationThe alias detected an authorization error.




Module:DFHRPAS

ARPM

ExplanationThe alias detected an error in user code.



Module:DFHRPAS

ARPN

ExplanationThe alias detected an error while trying to switch TCBs.



Module:DFHRPAS

ARPO

ExplanationThe alias program detected an abend.

System actionOne of the following messages is issued: DFHRP0181,DFHRP0182, DFHRP0183.


Module:DFHRPAS

ARPU

ExplanationThe connection manager could not access the CICSONC RPC data set, and received an error responsewhen it tried to send message DFHRP1512.

System actionNone.


Module:DFHRPC01

ARPV

ExplanationThe connection manager received an unexpectedresponse from CICS following an EXEC CICScommand.

System actionOne of the following messages is issued: DFHRP1540,DFHRP1651, DFHRP1954.


Module:DFHRPC0E

ARPW

ExplanationThe connection manager received an unexpectedresponse from CICS following an EXEC CICScommand.






Module:DFHRPC0E

ARPX

ExplanationThe connection manager was started against an invalidterminal.



Module:DFHRPC01

ARPZ

ExplanationThe connection manager has insufficient authority.



Module:DFHRPC0B

ARSA

ExplanationAn attempt has been made to invoke the CRSTtransaction from a terminal. CRST is an internal CICStransaction and cannot be invoked in this way.


User responseNone.

Module:DFHRSTK

ARTA

ExplanationThe task does not own a terminal as its principalfacility.


User responseEnsure that DFHRTE has not been specified as theprogram for a task other than CRTE. Ensure that CRTEhas not been initiated by means other than terminalinput.

Module:DFHRTE

ARTB

ExplanationThere is no input TIOA or the data length is zero.


User responseEnsure that DFHRTE has not been specified as theprogram for a task other than CRTE. Ensure that CRTEhas not been initiated by means other than terminalinput.

Module:DFHRTE

ARTC

ExplanationThe link to the required system is not usable for anunknown reason.



Module:DFHRTE



ARTD

ExplanationAn internal logic error has been detected.



Module:DFHRTE

ARTE

ExplanationAn error was encountered when attempting to readfrom or write to temporary storage.


User responseDetermine the cause of the temporary storageproblem and correct it.

Module:DFHRTE

ARTF

ExplanationAn attempt has been made to use the routingtransaction (CRTE) from a terminal that has apermanent transaction code set.


User responseInform the system programmer.

Module:DFHRTE

ARTG

ExplanationCICS could not find the profile specified for atransaction being routed.


User responseCheck your transaction and profile definitions.

Module:DFHRTE

ARTH

ExplanationAn error (INVALID, DISASTER or EXCEPTIONresponse) has occurred on a call to schedule aremote terminal delete by DFHRTE during sign-offfor a surrogate terminal session running CRTE. Thedomain that detected the original error provides anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).



Module:DFHRTE

ARUA

ExplanationAn exception condition was returned on the ADD_LINKduring the BIND phase of ATTACH for the transactioninvoked by the RUN command.

System actionCICS terminates the invoked transaction abnormallywith a dump. The RUN SYNCHRONOUS command thatwas issued by the application returns with an errorresponse of INVREQ (RESP2 28).

User responseMore details can be found in the trace.

Module:



DFHXMRU

ARUB

ExplanationA RUN SYNCHRONOUS command caused anattempt to attach a transaction defined as remote.Only transactions defined as local may be runsynchronously.

System actionCICS terminates the invoked transaction abnormallywith a dump. The RUN SYNCHRONOUS command thatwas issued by the application returns with an errorresponse of ACTIVITYERR or PROCESSERR (RESP227).


Module:DFHXMXM

ARUC

ExplanationA RUN SYNCHRONOUS command caused an attemptto attach a transaction with an invalid USERID.

System actionCICS terminates the invoked transaction abnormallywith a dump. The RUN SYNCHRONOUS command thatwas issued by the application returns with a resp2value of 27.


Module:DFHXMRU

ARUD

ExplanationA RUN SYNCHRONOUS command caused an attemptto attach a child transaction. The parent transactionwhich issued the RUN SYNCHRONOUS command wasthen purged before the child task could be run.

System actionCICS terminates the invoked transaction abnormallywith a dump.

User responseNone

Module:DFHXMXM

ARXA

ExplanationA transactional EXCI request has been received froma batch region. CICS has encountered an error whenattempting to express interest in an RRMS Unit ofRecovery.

DFHRXUW provides an exception trace, consolemessage DFHRX0002, and possibly a system dump(depending on the options in the dump table).

System actionThe transaction is terminated with a CICS transactiondump.

User responseResource Recovery Services (RRS) may have been shutdown after the request was received by CICS. If thisis the case, retry the EXCI request once RRS has beenrestarted.

If this is not the case, use the exception trace providedby the RX domain to determine the reason for thefailure. You might need further assistance from IBMin this situation. See Working with IBM to solve yourproblem for guidance on how to proceed.

Module:DFHRXUW

ARXB

ExplanationAn error (EXCEPTION, DISASTER, INVALID,KERNERROR or PURGED) has occurred on anADD_LINK call to the recovery manager (RM) domain.For errors other than EXCEPTION, the RM domainprovides an exception trace, a console message, andpossibly a system dump (depending on the options inthe dump table).

For all errors, DFHRXUW provides an exception trace,console message DFHRX0002, and possibly a systemdump (depending on the options in the dump table).





User responseSee Working with IBM to solve your problem forguidance on how to proceed.

Module:DFHRXUW

ARXC

ExplanationA transactional EXCI request has been received from abatch region when either:

• CICS did not register as a resource manager withRecoverable Resource Management Services (RRMS)because system initialization parameter RRMS=NOwas specified.

• the RX domain did not succesfully complete itsinitialization.


User responseIf CICS was started with system initializationparameter RRMS=NO, restart CICS specifyingRRMS=YES (or route transactional EXCI requests toanother CICS system).

Otherwise, investigate why the RX domain did notinitialize succesfully. A failure during initialization ofthe domain is accompanied by a console message anda system dump. See Working with IBM to solve yourproblem for guidance on how to proceed.

Module:DFHRXUW

ARZ2

ExplanationAn attempt to service a GIOP request failedduring task attach due to required resources beingunobtainable, or missing information from requestdata.

System actionThe request fails and the task is abnormallyterminated with abend code ARZ2. CICS takes atransaction dump, unless module DFHDUIO is notloaded.


Module:DFHRZXM

ARZ3




Module:DFHRZIX, DFHRZTCX

ARZ4




Module:DFHRZRM, DFHRZSO1





ARZ5

ExplanationThe target request stream task detected that thesource task was no longer active. The target task isunable to process the request it was attached for.


User responseInvestigate why the source task has terminated beforethis target began initialisation. There may be relevantmessages in the CICS log. Otherwise a CICS trace orsystem dump will be required to identify the problem.One possible cause is that the source task was timedout and purged before the target task started.

Module:DFHRZXM

ARZE


System actionThe transaction is abnormally terminated with abendcode ARZE. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.


Module:DFHRZLN, DFHRZRM, DFHRZSO, DFHRZSO1,DFHRZTA, DFHRZXM

ARZF


System actionThe transaction is abnormally terminated with abendcode ARZF. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.



ARZI


System actionThe transaction is abnormally terminated with abendcode ARZI. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.



ARZJ


System actionThe transaction is abnormally terminated with abendcode ARZJ. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.




ARZR

ExplanationA request stream task encountered a failure whiletrying to join with an existing target request streamtask. This may be caused by the existing target tasktaking too long to respond and the new task reachingits DTIMOUT limit.

System actionThe request fails and the task is abnormallyterminated with abend code ARZR. CICS takes a

transaction dump, unless module DFHDUIO is notloaded.


Module:DFHRZJN

ASxx abend codesASCA

ExplanationA DFHSC TYPE=GETMAIN request has resulted in acall to the storage manager (SM) domain which hasreturned an INVALID or DISASTER response.


User responseThere has been an earlier failure which led tothe response from the storage manager domain.Investigate the earlier failure (which is accompaniedby a console message and a system dump).

Module:DFHSMSCP

ASCB

ExplanationA DFHSC TYPE=FREEMAIN request has resulted in acall to the storage manager (SM) domain which hasreturned an INVALID or DISASTER response.


User responseThere has been an earlier failure which led tothe response from the storage manager domain.Investigate the earlier failure (which is accompaniedby a console message and a system dump).

Module:DFHSMSCP

ASCP

ExplanationA task which has issued an unconditional DFHSCTYPE=GETMAIN request has been purged whilewaiting for sufficient contiguous main storage tobecome free.


User responseInvestigate why the task was purged. This will eitherhave been as a result of a purge from the mainterminal operator via the CEMT transaction, or by thetask being timed out after waiting for longer than theDTIMOUT (deadlock timeout) value specified for thetransaction.

If the task was purged by the main terminal operatorthen this may have been in an attempt to clear thesystem which appeared to be deadlocked for somereason.


If the task was timed out automatically as a resultof the DTIMOUT value being exceeded then this maybe due to insufficient main storage being available forthe number of tasks in the system. If the amount ofmain storage cannot be increased then the numberof tasks in the system should be reduced to avoidshort-on-storage situations. Another possibility wouldbe to increase the value of the DTIMOUT option for thetransaction.

Module:DFHSMSCP

ASCR

ExplanationA DFHSC macro request has been issued with aninvalid request type.


Detection of the invalid request by DFHSMSCP causesa console message and a system dump to beproduced.

User responseUse the associated console message and systemdump to investigate the problem.

Module:DFHSMSCP

ASDA

ExplanationThe default shutdown transaction (CESD) has beenstarted directly from a terminal. This is not permitted.This transaction can only be started internally by CICS.


User responseNone.

Module:DFHCESD

ASFA

ExplanationAn internal logic error occurred in DFHSFP because ofan unexpected response from EXEC CICS. This abendcode is usually accompanied by message DFHCE3598which contains the associated return codes.



Module:DFHSFP

ASFB

ExplanationAn attempt was made to execute the CICS signoffprogram without an associated terminal.

System actionCICS terminates the transaction with a dump. Thisabend code is usually accompanied by messageDFHCE3598.

User responseOnly use the signoff program when there is a relatedterminal.

Module:DFHSFP

ASFC

ExplanationAn attempt was made to execute the CICS signoffprogram against an APPC session.


User responseOnly use the signoff program when there is a relatedterminal.

Module:



DFHSFP

ASH2

ExplanationAn attempt to service a Scheduler Services requestfailed due to required resources being unobtainable.This may result in a request being unserviceable oran Activity being marked abended depending on thenature of the failure.

System actionThe transaction is abnormally terminated with abendcode ASH2. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.

User responseCheck that any required links between regions areavailable. Check the Distributed Routing Programname is correct and the program is usable. Usethe transaction dump to determine the cause of thefailure. For further assistance, or if module DFHDUIOis not loaded and no transaction dump is available,contact your system programmer.

Module:DFHSHXM

ASH3

ExplanationA transaction bound to a Scheduler Services requesthas backed out. No other abend code has beenset. The SH abend request uses this abend code bydefault.

System actionThe transaction continues backing out. A subsequenttask will process the SH abend request.

User responseNone.

Module:DFHSHRM

ASH4

ExplanationA Scheduler Services request attempted to attach atransaction that is currently disabled.

System actionThe transaction is abnormally terminated with abendcode ASH4. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.

User responseCheck the status of the transaction. For furtherassistance, or if module DFHDUIO is not loaded andno transaction dump is available, contact your systemprogrammer.

Module:DFHSHXM

ASHA


System actionThe transaction is abnormally terminated with abendcode ASHA. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.


Module:DFHSHDM

ASHB


System actionThe transaction is abnormally terminated with abendcode ASHB. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.


Module:DFHSHDM


ASHR


System actionThe transaction is abnormally terminated with abendcode ASHR. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.


Module:DFHSHRSP

ASHU

ExplanationIn the process of transferring the request from oneregion to another an abend occurred due to a routingfailure. The Request cannot be routed to a suitableregion. The request is unserviceable.

System actionThe transaction is abnormally terminated with abendcode ASHU. CICS takes a transaction dump, unlessmodule DFHDUIO is not loaded.

User responseCheck the links between regions are available. Checkthe Distributed Routing Program name is correct andthe program is usable. Use the transaction dumpto determine the cause of the failure. For furtherassistance, or if module DFHDUIO is not loaded andno transaction dump is available, contact your systemprogrammer.

Module:DFHSHRSP

ASIA

ExplanationAn error has occurred on a call to the storage manager(SM) domain. The domain that detected the originalerror will have provided an exception trace, a consolemessage and, possibly, a system dump (depending onthe options specified in the dump table).

System actionThe task is abnormally terminated with a CICStransaction dump. CICS then terminates abnormally.


Module:DFHSII1

ASIB

ExplanationAn attempt has been made to run the CICS internaltask CPLT as a user transaction.


User responseInvestigate why the attempt was made to run CPLT asa user transaction.

Module:DFHSIPLT

ASJ7

ExplanationAn error has caused the JVM server to receive aSIGABRT signal.

System actionCICS produces a system dump and terminatesimmediately.

User responseContact IBM support.

Module:DFHSJSC

ASJA

ExplanationAn error has occurred obtaining a lock within the Javadomain.




Module:DFHSJST

ASJB

ExplanationAn error has occurred releasing a lock within the Javadomain.



Module:DFHSJST

ASJH

ExplanationA JVM has terminated due to a program check or otherreason.


User responseCheck the JVM's STDOUT and STDERR files, and anyJVM dumps for further information.

Module:DFHSJIN

ASJI

ExplanationProgram DFHSJJI was called using EXEC CICS LINK,but no channel was provided.


User responseChange the application program to pass the correctchannel.

Module:DFHSJJI

ASJL

ExplanationAn error has occurred after linking to an applicationrunning in Liberty.CICS issues this abend in order torelease resources associated with the task that issuedthe LINK.



Module:DFHSJJS

ASJO

ExplanationThe JVMServer resolution transaction CJSR, hasencountered an internal error.

The CICS system transaction CJSR provides supportfor initializing new JVMServers. If this fails it is likelythat there is an underlying error with the CICS system.



Module:DFHSJIT

ASJS

ExplanationA Java application running in a JVMSERVER invokedthe System.exit() method.


System actionCICS produces a system dump and terminatesimmediately.

User responseChange the application to avoid invoking System.exit(),or implement a Java Security Manager to preventSystem.exit() from being invoked.

Module:DFHSJSC

ASJR

ExplanationDFHSJJS was invoked by a caller running within a JVMserver. While the request was being processed, theJVM server terminated. DFHSJJS is not able to returncontrol to the caller in the usual manner.


User responseNone.

Module:DFHSJJS

ASNA

ExplanationAn internal logic error occurred in DFHSNP because ofan unexpected response from EXEC CICS.



Module:DFHSNP

ASNB

ExplanationAn attempt was made execute the CICS sign onprogram without an associated terminal. This abendcode is usually accompanied by message DFHCE3548.

System actionCICS terminates the transaction with a dump.

User responseOnly use the sign on program when there is a relatedterminal.

Module:DFHSNP

ASNC

ExplanationThe signon program attempted to send a request tothe user but failed to do so.



Module:DFHSNP

ASND

ExplanationA request from DFHSNTU to ENQ on the address of theSNEX has failed during signoff terminal user.

System actionA transaction dump is taken and the task which issuedthe signoff is abended.


Module:DFHSNTU





ASOA

ExplanationThe TCP/IP listener task CSOL has been incorrectlystarted from a terminal. It can only be enabled bythe Sockets Domain at CICS system initialization or byusing CEMT SET TCPIP OPEN or the equivalent SPIfunction.


User responseNone.

Module:DFHSOL

ASOB

ExplanationThe Sockets Domain has encountered a locking errorwhile attempting to issue a lock.


User responseThe exception trace prior to this abend gives moreinformation as to why this abend was issued.

Module:DFHSOCK DFHSODM DFHSOIS DFHSOLS DFHSOUEDFHSOS00-23

ASOC

ExplanationThe TCP/IP listener task CSOL has encountered anunlocking error while attempting to issue an unlock.



Module:DFHSOL

ASOD

ExplanationThe TCP/IP transaction attach module DFHSOXMencountered an error during the bind stage oftransaction attach processing for a new task.



Module:DFHSOXM

ASOL

ExplanationThe TCP/IP listener task CSOL has abended.


User responseInvestigate why the transaction was abended. Theexception trace prior to this abend gives moreinformation as to why this abend was issued.

Module:DFHSOL

ASP1

ExplanationIntersystem communication failed while a syncpointwas being taken. Communication with the coordinatorsystem has been interrupted, and the failure occurredduring the critical indoubt period of syncpointprocessing. As a result this CICS system is in doubtabout the outcome of the unit of work for thetransaction.

Alternatively, a transaction may have timed outwhile waiting for Recoverable Resource ManagementServices (RRMS) to provide the outcome of the unitof work, or RRMS may have failed during the criticalindoubt period.


The transaction definition specifies WAIT(YES) as anindoubt attribute. Therefore the unit of work is notcompleted but is shunted and allowed to wait forresynchronization with the coordinator system. If theWAITTIME attribute is specified on the transactiondefinition, the unit of work waits for the specifiedtime. If after that time the coordinator system has notresynchronized, a unilateral decision is made aboutthe unit of work as specified by the ACTION keywordon the transaction definition. A WAITTIME of zero, thedefault, means an indefinite wait. The unit of work canalso be forced to take a unilateral decision by means ofa CEMT SET UOW command.

System actionThe transaction is abnormally terminated. The EXECCICS HANDLE ABEND command cannot handle thisabend.

The associated unit of work is shunted awaitingthe return of the coordinator system. Recoverableresources updated by the unit of work remain locked.The locks are released when the unit of work is backedout or committed at resynchronization time, or when aunilateral decision is made by this system.

Message DFHAC2201 is sent to the terminal enduser if possible, and message DFHAC2231 is sent totransient data destination CSMT.

User responseNone. Any updates performed by the unit of work areresolved automatically when resynchronization withthe coordinator system takes place.

Alternatively, the user can force resolution of theupdates independently of the coordinator system bymaking a CEMT request to commit or back out the unitof work.

Module:DFHAPAC

ASP2

ExplanationA syncpoint has been attempted when an intersystemconversation is in a state in which the EXEC CICSSYNCPOINT command is not allowed. If CICS isconnected to a system which must act as LASTAGENT, such as IMS, then this ABEND will be issuedfrom SYNCPOINT processing if a PREPARE has beenreceived on a link to another system. In order tosupport syncpointing CICS must act as COORDINATORwhen it is directly connected to the LAST AGENT, theCOORDINATOR system may send PREPARE syncpointcommands but never receives them.

System actionThe task is abnormally terminated with a CICStransaction dump which includes terminal controlinformation. In particular, the dump contains stateinformation for the links used by this transaction. TheEXEC CICS HANDLE ABEND command cannot handlethis abend.

User responseEnsure that the application issues an EXEC CICSSYNCPOINT command only when its sync level 2conversations are in the correct state. The EXEC CICSSYNCPOINT command may be issued only when eachconversation is in one of the following states:

SENDPEND-RECEIVE (Not for MRO)PEND-FREESYNC-RECEIVESYNC-SEND (Not for MRO)SYNC-FREE

Module:DFHAPAC

ASP3

ExplanationAn application has requested syncpoint, either viaEXEC CICS SYNCPOINT or implicitly via EXEC CICSRETURN. The coordinator of the syncpoint is not thisCICS system but is remote. During the syncpointprotocol the remote coordinator has decided that theunit of work cannot be committed and must be backedout.

This error can occur with external resource managersconnected to CICS via the resource manager interface(RMI) as well as CICS systems connected via LU 6.2,MRO and IPIC. If an external resource manager suchas DB2 is the only recoverable resource updated inthe transaction, the recovery manager (RM) domaincan optimize the syncpoint protocol. In this instance,the external resource manager becomes the syncpointcoordinator. In this instance if the external resourcemanager returns with a backed out response, an ASP3abend results.

System actionThe transaction is abnormally terminated andrecoverable resources updated by the unit of work arebacked out. The EXEC CICS HANDLE ABEND commandcannot handle this abend.



User responseRefer to the remote coordinator system to determinewhy the unit of work was backed out.

Module:DFHAPAC

ASP7

ExplanationA resource manager involved in syncpoint protocolshas replied 'No' to a request to 'Prepare'. The resourcemanager may be local to this CICS system, or may be aremote resource manager on another CICS system, oran external resource manager communicating throughthe resource manager interface (RMI).

System actionCICS terminates the transaction abnormally.Recoverable resources updated by the unit of work arebacked out. The EXEC CICS HANDLE ABEND commandcannot handle this abend.

If it is a local resource manager that has voted no,message DFHAC2218 is sent to the terminal enduser if possible, and message DFHAC2248 is sent totransient data destination CSMT.

If it is a remote resource manager that has votedno, message DFHAC2219 is sent to the terminal enduser if possible, and message DFHAC2249 is sent totransient data destination CSMT.

User responseThis abend is caused by a prior problem. For example:

• the resource manager cannot flush its buffersbecause of an I/O error

• the resource manager cannot communicate withCICS because of a TP failure.

• Event Processing is unable to emit a synchronousevent

Inspect the CICS message log to determine the causeof the earlier problem and corrrect it. An ASP7 can alsooccur during terminal or connection install if CICS isshort on storage. For instance if message DFHAC2248shows the transaction as CATA then look for earliershort on storage messages.

Module:DFHAPAC

ASP8

ExplanationThe transaction requested syncpoint rollback, but wasusing a type of processing for which syncpoint rollbackis not supported.

System actionCICS terminates the transaction abnormally. The EXECCICS HANDLE ABEND command cannot handle thisabend.


User responseThis error may be an application error or aconfiguration error. Some communication sessions,(for example, LU6.1) do not support syncpointrollback, and if CICS detects such a sessionduring rollback processing, the task is abended.This restriction is described in the CICSintercommunication. To resolve the problem, either:

• Change the application so that it does notissue syncpoint rollback commands while the non-supporting sessions are allocated (e.g. issue an EXECCICS FREE first), or

• Change the configuration so that either APPC or MROsessions are used for communication. These arethe only two session types which support syncpointrollback.

Alternatively, following a session failure during aprevious syncpoint, CICS may have decided to rollbackthis unit-of-work in order to preserve data integrity.Since the unit-of-work contains a session which doesnot support syncpoint rollback, this abend ensues. Inthis case, no action is required in response to thisabend, although action may be required to deal withthe original failure.

Module:DFHAPAC

ASP9

ExplanationThe transaction requested syncpoint via EXEC CICSSYNCPOINT, but this is not allowed in a transactionthat is acting on behalf of an Activity.




System actionCICS terminates the transaction abnormally. EXECCICS HANDLE ABEND command cannot handle thisabend.

User responseThe error indicates an invalid attempt to syncpoint thetransaction.

Module:DFHEISP

ASPA

ExplanationThe task was purged before a request to recoverymanager (RM) domain was able to completesuccessfully. The domain that first detected the purgedcondition provides an exception trace.

System actionThe task is abnormally terminated with a CICStransaction dump. If processing is at a point wheredata integrity might not be maintained, CICS isabnormally terminated.




If CICS is abnormally terminated, it should beemergency restarted to ensure that data integrity ismaintained.

Module:DFHAPAC

ASPB

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call to therecovery manager (RM) domain. The domain thatdetected the original error will have provided anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).

System actionThe task is abnormally terminated with a CICStransaction dump. If processing is at a point wheredata integrity might not be maintained, CICS isabnormally terminated.

User responseSee the related message from the domain thatdetected the original error. If CICS was abnormallyterminated, it should be emergency restarted toensure that data integrity is maintained.

Module:DFHAPAC

ASPC

ExplanationAn error (INVALID or DISASTER) has occurred ona call to the bridge syncpoint routine (DFHBRSP).The domain that detected the original error will haveprovided an exception trace, and, possibly, a systemdump (depending on the options specified in the dumptable).



Module:DFHSPP

ASPD

ExplanationThe transaction requested syncpoint via EXEC CICSSYNCPOINT, or rollback via EXEC CICS SYNCPOINTROLLBACK, but this is not allowed in a transaction thatis associated with an OTS transaction.


System actionCICS terminates the transaction abnormally. EXECCICS HANDLE ABEND command cannot handle thisabend.

User responseThe error indicates an invalid attempt to syncpoint thetransaction.

If DB2 is being accessed in the transaction, check thatthe DB2ENTRY or DB2CONN pool definition used bythe transaction does not specify DROLLBACK(YES).

Module:DFHEISP

ASPF

ExplanationCICS issued an internal syncpoint request resultingin a syncpoint with an intersystem session whichhas returned ROLLEDBACK to recovery manager (RM)domain. As a result, the transaction is abnormallyterminated because the unit of work which was beingsyncpointed has been backed out.

This could result from shutting down IRC or from thefailure of a connected CICS region.

System actionThe transaction is abnormally terminated. Recoverableresources updated by the unit of work are backed outand locks released. The EXEC CICS HANDLE ABENDcommand cannot handle this abend.


User responseDetermine why the remote intersystem sessionreturned a ROLLEDBACK response to the syncpointrequest. Once this has been corrected retry thetransaction.

To avoid ASPF abends in future, ensure that no in-flightunits of work exist before shutting down IRC.

Module:DFHAPAC

ASPI

ExplanationDuring CICS synchronization level 1 (synclevel 1)commit, an unexpected FMH or no data has been

received from the partner system. Local resourcesand synclevel 2 partners have been committed, butsynclevel 1 function-shipped resource updates mayhave been backed out.

System actionThe transaction does not abend. CICS synclevel1 commit processing continues, with the aim ofcommitting as many synclevel 1 resources as possible.

User responseExamine the transaction dump to determine why theFMH was invalid or missing, It is likely that the error isin the remote system.

See the Developing distributed applications for moreinformation about syncpointing.

Module:DFHCR2U

ASPJ

ExplanationDuring CICS synchronization level 1 (synclevel 1)commit, unexpected syncpoint message data has beenreceived from the partner system. Local resourcesand synclevel 2 partners have been committed, butsynclevel 1 function-shipped resource updates mayhave been backed out.

System actionThe transaction does not abend. CICS synclevel1 commit processing continues, with the aim ofcommitting as many synclevel 1 resources as possible.

User responseExamine the transaction dump to determine why themessage data was invalid. It is likely that the error is inthe remote system.

See the Developing distributed applications for moreinformation about syncpointing.

Module:DFHCR2U

ASPN

ExplanationA transaction has issued an EXEC CICS RETURN inbackout required program state. The backout requiredprogram state is set when an application receives orissues an abend, or receives a backout request on aprotected conversation.


https://www.ibm.com/support/knowledgecenter//applications/developing/connections/develop_plex.html

https://www.ibm.com/support/knowledgecenter//applications/developing/connections/develop_plex.html



User responseTo avoid the transaction abend, the application shouldcode an EXEC CICS SYNCPOINT command beforethe EXEC CICS RETURN. A syncpoint issued in'backout required' program state results in a backoutbeing performed, and the ROLLEDBACK conditionreturned on the EXEC CICS SYNCPOINT command.If this condition is then handled, a subsequent EXECCICS RETURN will complete successfully. For LU61conversations the application should issue an EXECCICS FREE followed by an EXEC CICS SYNCPOINTROLLBACK, in order to avoid a subsequent ASP8abend.

Module:DFHAPAC

ASPO

ExplanationAn intersystem session failed while a syncpoint wasbeing taken. The intersystem session that failed wasthe link to the coordinator system. The failure occurredduring the indoubt period of syncpoint processing. As aresult this CICS system is in doubt as to the outcomeof the unit of work for the transaction.

The unit of work is not shunted to await the returnof the coordinator system, but is instead unilaterallycommitted. The unit of work is not shunted for one ofthe following reasons:

• The transaction definition specifies WAIT(NO).• The unit of work includes an MRO session to a

back-level CICS system which does not support theWAIT(YES) option, and the role of the session in theunit of work is such that it cannot await the return ofthe coordinator system.

• The unit of work includes an LU6.1 session, and therole of the session in the unit of work is such that itcannot await the return of the coordinator system.

• The unit of work involves a task related user exitwhich is not enabled with the INDOUBTWAIT option.

• The unit of work has updated a recoverable transientdata destination, which is defined with WAIT(NO).

• The unit of work involves the installation of CICSresource definitions from the CSD (CICS systemdefinition) file.

The unit of work is committed, rather than backedout, because the transaction definition specifiesACTION(COMMIT).

The fact that the unit of work is committed isremembered by the recovery manager (RM) domainuntil the unit of work is resynchronized with thecoordinator system. At this time, according to whetherthe coordinator system committed or backed out, therecovery manager domain issues resynchronizationmessages reporting whether or not the resolutionof the unit of work in the subordinate system wasconsistent with the coordinator system.

System actionThe transaction is abnormally terminated. Recoverableresources updated by the unit of work are committedand locks released. The EXEC CICS HANDLE ABENDcommand cannot handle this abend.


User responseAny updates performed by the unit of work arecommitted. There is a danger that recoverableresources will be inconsistent with the coordinatorsystem if the coordinator system has backed out. If thereason for the failure is the first of those listed aboveand if you wish CICS to ensure that data integrity ismaintained, change the indoubt transaction definitionto specify WAIT(YES) so that CICS automaticallyhandles indoubt failures and resynchronizes the unitof work when the link to the coordinator system isreestablished.

Module:DFHAPAC

ASPP

ExplanationAn intersystem session failed while a syncpoint wasbeing taken. The intersystem session that failed wasthe link to the coordinator system, and the failureoccurred during the critical indoubt period of syncpointprocessing. As a result this CICS system is in doubt asto the outcome of the unit of work for the transaction.

The unit of work is not shunted to await the returnof the coordinator system. Instead it is unilaterallybacked out. The unit of work is not shunted for oneof the following reasons:


• The transaction definition specifies WAIT(NO).• The unit of work includes an MRO session to a

back-level CICS system which does not support theWAIT(YES) option, and the role of the session in theunit of work is such that it cannot await the return ofthe coordinator system.

• The unit of work includes an LU6.1 session, and therole of the session in the unit of work is such that itcannot await the return of the coordinator system.

• The unit of work involves a task related user exitwhich is not enabled with the INDOUBTWAIT option.

• The unit of work has updated a recoverable transientdata destination, which is defined with WAIT(NO).

• The unit of work involves the installation of CICSresource definitions from the CSD (CICS systemdefinition) file.

The unit of work is backed out, rather thancommitted, because the transaction definitionspecifies ACTION(BACKOUT).

The fact that the unit of work is backed out isremembered by recovery manager (RM) domain untilthe unit of work is resynchronized with the coordinatorsystem. At this time, according to whether thecoordinator system backed out or committed, therecovery manager domain issues resynchronizationmessages reporting whether or not the resolutionof the unit of work in the subordinate system wasconsistent with the coordinator system.



User responseAny updates performed by the unit of work are backedout. There is a danger that recoverable resources willbe inconsistent with the coordinator system if thecoordinator system has committed. If the reason forthe failure is the first of those listed above and if youwish CICS to ensure that data integrity is maintained,change the indoubt transaction definition to specifyWAIT(YES) so that CICS automatically handles indoubtfailures and resynchronizes the unit of work when thelink to the coordinator system is reestablished.

Module:DFHAPAC

ASPQ

ExplanationDuring phase 2 of the two phase syncpoint protocolan error occurred while communicating with a remotesystem. The error occurred after the recoverableresources were committed or backed out, so dataintegrity is not in danger.

System actionThe transaction is abnormally terminated. Recoverableresources updated by the unit of work will havebacked out or committed depending on the decisiontaken by the recovery manager (RM) domain, whichwas not influenced by this later problem. The EXECCICS HANDLE ABEND command cannot handle thisabend.


User responseRefer to earlier messages issued by thecommunication or remote resource managementcomponents of CICS to determine the cause of theintersystem communication problem.

Module:DFHAPAC

ASPR

ExplanationIntersystem communication failed while a syncpointwas being taken. Communication with the coordinatorsystem has been interrupted, and the failure occurredduring the critical indoubt period of syncpointprocessing. As a result this CICS system is in doubt asto the outcome of the unit of work for the transaction.

However, this CICS system has not updated anyrecoverable resources in the unit of work and hencedoes not require the unit of work to be shuntedto await resynchronization of its resources later.The coordinator system commits or backs out itsresources. No resources on this system need to bekept in step.

This error can occur with external resource managersconnected to CICS via the resource manager interface(RMI) as well as CICS systems connected via IPIC, LU6.2 and MRO. If an external resource manager suchas DB2 is the only recoverable resource updated inthe transaction, the recovery manager (RM) domaincan optimize the syncpoint protocol. In this instance,


the external resource manager becomes the syncpointcoordinator. If the link to the external resourcemanager is lost during this time, CICS will be indoubtas to whether the external resource manager updateswere committed or backed out.

System actionThe transaction is abnormally terminated. There areno recoverable resources affected in this CICS system.The EXEC CICS HANDLE ABEND command cannothandle this abend.


User responseRefer to messages on the remote system todetermine if the remote resources were backed out orcommitted.

Module:DFHAPAC

ASQA

ExplanationThe CLS2 transaction was processingresynchronization work but the communicationssession which it was using has failed.

System actionThe work is reexecuted on a new session. Ifreexecution has has already been attempted, thetransaction terminates.

User responseThe error may be caused by the failure of severalsessions between communicating systems during theresynchronization process. To confirm this, examinethe CSMT transient data queue for the relevant period.

Another cause could be logic errors within theresynchronization program, either on this system oron the partner system, which caused the sessionto be terminated. In this case, CSMT transient datamessages indicate the nature of the error.

Module:DFHCRRSY

ASQB

ExplanationThe CLS2 transaction was executing exchange lognames or resynchronization with a remote systemwhen a logic error occurred.


Message DFHRS2158 may also be issued.


Module:DFHCRRSY

ASQC

ExplanationThe CLS2 transaction was attached with anunexpected start code. The transaction can beattached due to terminal input (on a communicationssession), or via a system attach. Neither of thesemethods was used.


User responseThe error indicates an invalid attempt to start thetransaction.

Module:DFHCRRSY

ASQD

ExplanationThe CLS2 transaction was attached but could notuse the transaction manager interface to obtain inputparameters.


User responseThe error indicates a failure in the transactionmanager. See the exception trace entries produced by



the transaction managed to determine the reason forthe error.

Module:DFHCRRSY

ASQE

ExplanationThe CLS2 transaction was executing exchange lognames with a remote system and 3 retry attemptshave failed to solicit a warm exchange log names reply,in response to a warm exchange log names requestsent by CICS.


User responseThis abend indicates an error in the remote system. Itshould have saved the log name sent by CICS and, onreceiving a later exchange lognames request, shouldthen respond with a warm reply.

Module:DFHCRRSY

ASQG

ExplanationThe CLS2 transaction was executing resynchronizationwork and has failed during the receipt of data fromremote system via an MRO session. The data waslonger than expected.


User responseThe abend indicates a CICS logic error, possibly inthe remote system. The transaction storage in thedump shows the data received. The transaction traceshows the preceding flows between the systems,which should match those documented in the z/OSCommunications Server: SNA Programmer's LU 6.2Reference manual, SC30-6808.


Module:DFHCRRSY

ASQH

ExplanationThe CLS2 transaction was executing resynchronizationwork and has failed during the receipt of data fromremote system via an MRO session. The data wasshorter than the minimum length expected.

System actionThe transaction is anormally terminated with atransaction dump.

User responseThis indicates a CICS logic error, possibly in the remotesystem. The transaction storage in the dump showsthe data received. If you need further assistance fromIBM to resolve this problem, see Working with IBM tosolve your problem for guidance on how to proceed.

Module:DFHCRRSY

ASQI

ExplanationThe CLS2 transaction was executing the exchangelognames process as part of the initialization sequencefor an APPC connection. An attempt to invoke the CICSrecovery manager to save a logname failed.


Message DFHRS2157 may also be issued.

User responseThis indicates an error in the CICS recovery managerwhich has produced its own exception trace records.Look at the trace records and the CSMT message logfor further information about the error.

Module:DFHCRRSY

ASQK

ExplanationThe CLS2 transaction was processing exchangelognames or resynchronization for a connected partneridentified by a netname. The connection entryassociated with the netname was located and locked,


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istr620/abstract.htm






but could not be unlocked in subsequent processing.This indicates a CICS internal logic error.

System actionThe transaction is abnomally terminated with atransaction dump.

Message DFHRS2156 may also issued.

User responseThis indicates an error either in the CICS tablemanager, (which may have produced its own exceptiontrace records) or in the resynchronization programitself. Look at the trace records and the CSMT messagelog for further information which might have indicatedan error in the table manager program or in thetable entry for the connection. If you need furtherassistance from IBM to resolve this problem, seeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHCRRSY

ASQL

ExplanationThe CLS2 transaction was executing theresynchronization of a unit of work with a connectedpartner, and has locked the associated data managedby the CICS recovery manager. The invocation of theTERMINATE_RECOVERY command to unlock the datafailed.


Message DFHRS2154 is also issued.

User responseThis indicates an error either in the CICS recoverymanager (which may have produced its own exceptiontrace records) or in the resynchronization programitself. Look at the trace records and the CSMTmessage log for further information. If you needfurther assistance from IBM to resolve this problem,see Working with IBM to solve your problem forguidance on how to proceed.

Module:DFHCRRSY

ASQM

ExplanationA CICS internal logic error has occurred inthe management of dynamic storage for theresynchronization program.


User responseThis indicates that the resynchronization program hasexhausted the available space for recording storageareas. The symptoms may indicate that the programwas looping without executing the error recoveryprocess. If you need further assistance from IBM toresolve this problem, see Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHCRRSY

ASRA

ExplanationThe task has terminated abnormally because of aprogram check.

System actionThe task is abnormally terminated and CICS issueseither message DFHAP0001 or DFHSR0001. MessageDFHSR0622 may also be issued.

User responseRefer to the description of the associated message ormessages to determine and correct the cause of theprogram check.

Module:DFHSRP

ASRB

ExplanationAn operating system abend has occurred and CICS hasbeen able to abend the current transaction.

System actionThe task is abnormally terminated and CICS issueseither message DFHAP0001 or DFHSR0001






User responseRefer to the description of the associated message todetermine the cause of the original operating systemabend, and take the necessary corrective action.

Module:DFHSRP

ASRD

ExplanationThe task has been abnormally terminated for one ofthese reasons:

• A program contains an assembler macro call which isno longer supported by CICS.

• An invalid attempt has been made to access the CSAor TCA.

• An attempt to access a TCA via field CSAQRTCA(previously CSACDTA) has been made.

• A non-assembler program has been wrongly definedto CICS as an assembler program.

• An application program has been link-edited withoutan appropriate exec interface stub.

This error appears as a program check.

System actionThe task is abnormally terminated and CICS issuesmessage DFHSR0618, followed by either DFHAP0001or DFHSR0001.

User responseRefer to the description of the associated messages todetermine and correct the error.

It is likely that either R12 which usually addressesthe TCA or R13 which usually addresses the CSA ispointing to an area of storage that you are not allowedto access.

Module:DFHSRP

ASRE

ExplanationThe task has been abnormally terminated because anattempt has been made to access a CICS-DB2 RCTload module.

The RCT nolonger exists as a load module and cannotbe accessed directly.

To access information about CICS DB2 resourcedefinitions, use the CICS SPI commands EXEC CICSINQUIRE/SET DB2CONN, EXEC CICS INQUIRE/SETDB2ENTRY and EXEC CICS INQUIRE/SET DB2TRAN.

This error appears as a program check.

System actionThe task is abnormally terminated and CICS issuesmessage DFHSR0619, followed by either DFHAP0001or DFHSR0001.

User responseChange the application to use the CICS SPI commandsto access information about CICS DB2 resourcedefinitions.

Module:DFHSRP

ASRJ

ExplanationThe task has terminated abnormally because a APdomain global user exit or task related user exitinvoked by the task has made a backlevel XPI call.

System actionThe task is abnormally terminated. CICS will haveissued error message DFHAP0702 or DFHAP0708which will have identified the exit program that madethe backlevel XPI call.

User responseReassemble the exit program using the latest CICSlibraries.

Module:DFHSRP


ATxx abend codesATC1

ExplanationThe CICS terminal control restart task could notcomplete because a necessary step failed. The taskhas done some essential recovery operations andabnormally terminated itself with code ATC1.

System actionCICS writes a transaction dump for the terminalcontrol restart task.

CICS sends two messages to the console, one toidentify the error detected by the terminal controlrestart task, and DFHTC1001 to report that the taskhas failed. A third message follows either to say thatCICS has terminated abnormally with a dump, or toask you to reply GO or CANCEL. Depending on thenature of the original error, you may see messagesfrom some other system component (for example, anaccess method).

User responseFirst, if CICS has requested a response, you mustreply. If you reply 'GO', CICS continues processing, butwithout terminal control. If you reply 'CANCEL', CICSterminates abnormally with a dump.

Use the messages and dumps to find out the cause ofthe failure.

Module:DFHTCRP

ATC2

ExplanationA CICS SET VTAM OPEN command has failed due toVTAM rejecting a CICS request.

System actionMessage DFHZC2302, DFHZC2304 or DFHZC2307is sent to the console, and CICS terminates thetransaction abnormally with a transaction dump.

User responseThe RPL with the VTAM request code and returncode can be found in the RA pool addressed fromTCTVRVRA. Use the z/OS Communications Server:SNA Programming manual, to determine the causeof the error and the actions necessary to correct it.After correcting the error, either retry the request or

terminate CICS and restart the network in your owntime.

Module:DFHZSLS

ATC3

ExplanationA write to a TLX device was issued with a data lengthof 0 causing TIOA data length (TIOATDL) to be zero.


User responseFor an error writing to a TLX device correct the errorin the user program by ensuring that a data length fordata to be placed in the terminal input/output area(TIOA) is provided at write time.

Module:DFHZARL DFHZARQ

ATC4

ExplanationA serious CAVM error has occurred. The XRF TCB hasabended.

System actionCICS abnormally terminates with a system dump.

User responseUse the dump and the guidance in any messagesissued by other system components to diagnose andcorrect the original error.

See the Troubleshooting and support for furtherguidance on using system dumps.

Module:DFHTCRP

ATC5

ExplanationAn internal logic error has been detected duringAPPC mapped processing. The conversation statemaintained by DFHZARL does not match the statewhich is jointly maintained by DFHETL and DFHZARM.


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/abstract.htm

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/abstract.htm


This problem could also arise when CICS is receivingapplication data. CICS may receive and end of chainnotification before receiving all the data expected.



Module:DFHETL

ATC6

ExplanationDFHETL has a SEND DATA request with a data lengthgreater than 65 528 bytes which is the maximum thatit can process.


User responseThis is a CICS internal logic error. If you need furtherassistance from IBM to resolve this problem, seeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHETL

ATC7

ExplanationDFHZSUP has detected a bad response from anINITIAL-CALL request to DFHZARL. This response isreturned to DFHZSUP in the DFHLUC parameter list.


User responseExamine field LUCCDRCD in the DFHLUC parameterlist. This appears in the ENTRY/EXIT trace points forDFHZARL. If trace is switched off, then it can be foundin DFHZSUP's LIFO entry in the transaction dump.

• LUCCDRCD = 'A0000100' - session failure• LUCCDRCD = 'A0010100' - read timeout• LUCCDRCD = 'A0010000' - deadlock timeout.

(The offset for LUCCDRCD can be found in CICS DataAreas).

If LUCCDRCD is X'00000000', the error is the result ofa connection failure. In this case examine the CSMTlog for further diagnostic information.

Module:DFHZSUP

ATC8

ExplanationAn error has occurred during the processing of aninbound function management header (FMH). Eithera length error has been detected, for example,incomplete FMH received, or an invalid field has beendetected within the FMH.


User responseNotify the system programmer of the error. Theproblem is probably in the remote system that hassent the invalid FMH.

Module:DFHETL

ATC9

ExplanationA DFHKC RESUME macro call has been issued for atask without first issuing DFHKC SUSPEND. DFHKCRESUME must be preceded by DFHKC SUSPEND.


User responseExamine the trace entry to locate the error.

Module:DFHZNCE

ATCA




https://www.ibm.com/support/knowledgecenter//reference-data-areas/reference_data-areas.html

https://www.ibm.com/support/knowledgecenter//reference-data-areas/reference_data-areas.html

ExplanationThe system was in a final quiesce mode when the CICSapplication program issued a DFHTC macro.

System actionThe task requesting the I/O is abnormally terminatedwith a CICS transaction dump.

User responseNone.

Module:DFHZARQ

ATCB

ExplanationThe CICS application program issued two consecutiveDFHTC writes or two consecutive DFHTC reads, but ineither case did not issue an intervening wait.


User responseTake corrective action within the program beingexecuted.

This is almost certainly an application program error.Determine the flow of control through the applicationand determine why an intervening wait is not issued.The trace table may be useful to discover where theapplication is issuing the read and write requests. Ifnecessary, start trace or auxiliary trace using the mainterminal command and rerun the transaction to obtaina trace. The output of the auxiliary trace can be printedusing the trace utility program, DFHTU730.

Problem determinationA transaction dump is provided with this abend. Inthe dump, register 12 addresses the current TCA,and register 10 and the field TCAFCAAA address theTCTTE associated with this task. In TCATPOS2, bitTCATPOWR (X'01') indicates that a write is requestedby the DFHTC macro, and bit TCATPORR (X'10')indicates that a read is requested. In TCTTEOS, bitTCTTEOWR (X'01') indicates that a write is in progress,and bit TCTTEORR (X'10') indicates that a read is inprogress.

Analysis:


R10=@TCTTE TCZARQ05 Bit TCATPOWR is on in byteR12=@TCA (TCZAQ1W) TCATPOS2, and bit TCTTEOWR is on in byte TCTTEOS.

R10=@TCTTE TCZARQ05 Bit TCATPOWR is on in byteR12=@TCA (TCZAQ2W) TCATPOS2, and bit TCTTEORR is on in byte TCTTEOS.

R10=@TCTTE TCZARQ12 Bit TCATPORR is on in byteR12=@TCA TCATPOS2, and bit TCTTEORR is on in byte TCTTEOS.

Module:DFHZARQ

ATCC

ExplanationAn application program, using a pipeline session, haseither issued more than one write request or issueda read request.:sysact. The transaction is abnormallyterminated with a CICS transaction dump.

System action:

User responseCorrect the application program so that it will notissue more than one consecutive WRITE to a pipelinesession terminal.

Module:DFHZARQ

ATCD

ExplanationThis abend code is used whenever a CTYPE request ora QUEUE request is issued and VTAM or a ZCP functionhas not been included in the system.

It is also used to abend a task that issues an APPCcommand when the CICS system is not at a level tosupport APPC.


User responseCorrect the transaction so that it does not issue aCTYPE macro instruction if VTAM is not generated intothe system, or include the ZCP function for which theCTYPE or QUEUE request was issued.

Module:


DFHZDSP, DFHZERH

ATCE

ExplanationA CICS application program has issued a DFHTCrequest without specifying the address of a TIOA, butthe request is not an ERASE ALL UNPROTECTED or aREADBUF request for a 3270 data stream terminal.


User responseCorrect the error in the user program by ensuringthat a terminal input/output area (TIOA) is providedat write time.

This is almost certainly an application program error.Determine the flow of control through the applicationand determine why a TIOA has not been specified.

Problem determinationA transaction dump is provided with this abend. Inthe dump, register 12 addresses the current TCA,and register 10 and the field TCAFCAAA addressesthe TCTTE associated with this task. Register 8 andTCTTEDA should contain the address of the TIOA tobe used in the I/O request, but actually they containzero. For a 3270 data stream terminal, byte TCTETDSThas bit TCTETTSI (X'01') set. An erase-all-unprotectedrequest is indicated by the setting of bit TCTTEEUI(X'40') in byte TCTTEEUB, and a read buffer request isindicated by the setting of bit TCTTERBI (X'80') in byteTCTTERBB. Analysis:


R10=@TCTTE TCZARQ41 NIOABAR (register 8) contains zero.R8=0 Register 8 has been loaded field TCTTEDA of the TCTTE associated with this task.

Module:DFHZARQ

ATCF

ExplanationA DFHTC CTYPE macro was issued to a non-VTAMterminal control table terminal entry (TCTTE), or a

DFHTC CTYPE=COMMAND or RESPONSE macro wasissued to a VTAM 3270 TCTTE.


User responseEnsure that the program issues CTYPE macrosto VTAM terminals only, and does not issueCTYPE=COMMAND or RESPONSE to a VTAM 3270.

Module:DFHZCRQ

ATCG

ExplanationA CICS application program has issued a DFHTCrequest for a terminal that it does not own. Theproblem of ownership may be because the taskpreviously issued a WRITE,LAST request (which wouldhave detached the terminal from that task) or becausethe task incorrectly specified the terminal to which therequest is directed.


User responseThis is most probably an application error (unlessstorage has been completely overwritten). Determinethe flow from the trace table and when a request tothe DFHZCP detach routine, DFHZDET, or a DFHTCWRITE,LAST was issued.

Problem determinationRegister 12 addresses the current TCA and register10 contains the address of the TCTTE. The addressof the TCTTE was obtained either from TCAFCAAA inthe case of a non-ISC transaction, or from TCATPTAif bit TCATPTTA (X'40') is on in byte TCATPOC3 (thisindicates that TERM=YES was specified on the DFHTCrequest and that this is an ISC transaction). In theTCTTE thus located, the field TCTTECA does notcontain the address of the TCA, indicating that this TCAis not owned by this task.


Analysis: A DFHTC request has been issued specifyinga TCTTE in which the field TCTTECA does not containthe address of the TCA.


R10=@TCTTE TCZARQ05 TCTTECA is not equal to register 12.

Module:DFHZARQ

ATCH

ExplanationThe task was purged before a domain call was able tocomplete successfully. The task that first detected thepurged condition provides an exception trace.


User responseInvestigate why the task was purged. It was purgedeither as a result of a purge from the main terminaloperator via the CEMT transaction, or by the task beingtimed out after waiting for longer than the DTIMOUT(deadlock timeout) value specified for the transaction,or by CICS issuing a purge request.



When CICS purges a task, it does so to allow anoperation to complete which would be held up by thepresence of active tasks, or to ensure data integrity.For example, CICS will purge a task which has maderecoverable updates to a coupling facility data tableif it determines that the coupling facility data tableserver for the pool in which that table resides hasrecycled, to ensure that all updates in the unit of workwill be backed out.

For module list,see Diagnostics reference.

Module:

DFHBSM62 DFHBSS DFHBSSZ DFHBSTZ DFHBSTZVDFHBSTZ1 DFHBSTZ2 DFHTBSB DFHTBSBP DFHTBSDDFHTBSDP DFHTBSL DFHTBSLP DFHTBSQ DFHTBSRDFHTBSRP DFHTBSSP DFHTCRP DFHTOASEDFHTOATM DFHTOLCR DFHTOLUI DFHTRZCPDFHTRZIP DFHTRZPP DFHTRZXP DFHTRZYPDFHTRZZP DFHZCQCH DFHZCQDL DFHZCQIQDFHZCQIS DFHZCQRS DFHZCQ00 DFHMRXMDFH62XM

ATCI

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call tomodule DFHRTSU. The module that detected theoriginal error provides an exception trace, a consolemessage and, possibly a system dump (depending onthe options specified in the dump table).


User responseSee the related message produced by the module thatdetected the original error.

Module:DFHZSUP DFHMRXM DFH62XM

ATCJ

ExplanationThis abend is issued by DFHZATA in the followingcircumstances:

• Transaction CATA is issued from a terminal• The address of the AWE (TCAFCAAA) is 0• The AWE is invalid (TCTWETYP should be

TCTTEAWE)• An abend is issued early in DFHZATA.

This abend is issued by DFHZATD in the followingcircumstances:

• Transaction CATD is issued from a terminal• The address of the AWE (TCAFCAAA) is 0• TCAFCAAA is an AWE and not a terminal• An abend is issued early in DFHZATD.

This abend is issued by DFHZATR in the followingcircumstances:

• Transaction CATR is issued from a terminal



• An abend is issued early in DFHZATD.

System actionCICS rejects the request.

User responseDetermine the issuing program and the reason for theabend and take the appropriate action as follows:

Do not try to invoke CATA, CATD or CATR from aterminal.

If the address in TCAFCAAA is incorrect, the callingmechanism has failed. This is a CICS logic error.

If an abend has been issued, use the transaction dumpto determine where the abend occurred. This is a CICSlogic error.

Module:DFHZATA DFHZATD DFHZATR

ATCK

ExplanationAn application program has issued a WRITE to aVTAM terminal specifying CCOMPL=NO without beingauthorized to do so.


User responseSpecify CHAINCONTROL in the transaction profile.

Module:DFHZARQ

ATCL

ExplanationAn error has occurred either during automaticjournaling or automatic logging of terminal messagesto or from this transaction. The message being loggedwill be one associated with an explicit READ or WRITEin the application program.


User responseUse the dump to ascertain why the journal or logrecord could not be written correctly. If a journalrecord length error is indicated, TIOATDL may havebeen corrupted.



X'8001' - WRITEX'8003' - PUT




Analysis:



Module:DFHETL, DFHTCPCM, DFHZARQ

ATCN

ExplanationAn error has occurred during the automatic journalingor automatic logging of the initial input message of thistransaction. This input message is the message thatactually caused the transaction to be invoked.


User responseUse the dump to ascertain why the log record couldnot be written correctly.


If a journal record length error is indicated, TIOATDL(X'08') may have been corrupted.



X'8001' - WRITEX'8003' - PUT



Analysis:


R4=@JCA TCZARQJP JCAJCRC is nonzero. TCZSUPJW Journal error.

Module:DFHZSUP DFH62XM DFHTFXM

ATCO

ExplanationAn application program has attempted to perform afunction not supported by a terminal or system.

Possible errors are:

1. SIGNAL not supported.

A DFHTC TYPE=SIGNAL request with theWAIT=YES option was issued to a VTAM logical unitthat CICS does not support for the receipt of theSIGNAL indicator.

2. WRITE STRUCTURED FIELD not supported.

This write may have been attempted as a result ofa SEND command with the STRFIELD keyword to adevice that does not support this function.

3. APPC mapped conversation not supported.

The application has attempted to perform a normalterminal control command on a session that is inuse for an APPC unmapped conversation. (OnlyEXEC CICS GDS commands are permitted.)


User responseCorrect the application program.

Module:DFHZARQ

ATCQ

ExplanationThe application program issued a write operation toa terminal that was in send status. In order to allowthis write to proceed, a signal command was sent,and DFHZCP started to read data from the terminalwaiting for the change direction indication. As eachdata record is received, it is placed on temporarystorage and, for one of these operations, a temporarystorage error has occurred.


User responseCheck that temporary storage has been included in thesystem and that it has sufficient space.

If an invalid request is indicated, check that the lengthof the data being written to temporary storage is notgreater than the VSAM control interval size minus 84.The length of the data is in TIOATDL (which is 8 greaterthan the length of the data that is read in by DFHZCP).

Problem determinationRegister 12 addresses the current TCA. TCACCSV1contains a saved copy of TCATSTR containing thetemporary storage response code. The temporarystorage response code may be one of:

X'04' - IOERROR - I/O errorX'08' - NOSPACE - No temporary storage spaceX'20' - INVREQ - Invalid request.

The temporary storage identification is constructed byconcatenating the character string "DFHQ" with theterminal identification from TCTTETI. The temporarystorage identification is placed in TCATSDI.

Register 8 and field TCTTEDA address the TIOA thatis being written to temporary storage. The addresspassed to temporary storage is that of TIOATDL.


Analysis: After the DFHTS TYPE=PUTQ, the temporarystorage response code was not zero.


R12=@TCA ZRAQ60 TCATSTR is nonzero.

Module:DFHZRAQ

ATCR

ExplanationAn application program has issued a read operation,after a previous write operation has caused DFHZCPto read-ahead data from the terminal in order to avoida lock-out. DFHZCP has now issued a DFHTS GETQ toretrieve the saved data from temporary storage, andan error has occurred.


User responseDetermine the cause of the temporary storage errorand correct it.

If a temporary storage identification error is indicated,examine TCTTETI for a valid terminal identification.

Problem determinationRegister 12 addresses the current TCA. TCACCSV1contains a saved copy of TCATSTR that contains thetemporary storage response code. The temporarystorage response code may be one of:

X'01' - ENERROR - Entry errorX'02' - IDERROR - Identification errorX'04' - IOERROR - I/O errorX'20' - INVREQ - Invalid request

The temporary storage identification is constructed byconcatenating the character string "DFHQ" with theterminal identification from TCTTETI. The temporarystorage identification is placed in TCATSDI.

Analysis: After the DFHTS TYPE=GETQ, the temporarystorage response code was not zero.


R12=@TCA ZRAR90 TCATSTR is not zero.

Module:DFHZRAR

ATCS

ExplanationAn application program attempted to send data to alogical unit after a SIGNAL data flow command withan RCD (request change direction) has been received.This condition arises when the application handles theIGREQCD exceptional condition incorrectly.


User responseHandle the IGREQCD exceptional condition correctly.

Module:DFHZARQ

ATCT

ExplanationAn attempt to build a surrogate TCTTE to represent aremotely-owned terminal failed.




ATCU

ExplanationAn application program attempted to send data to alogical unit, but was in receive mode (EIBRECV is set),and read-ahead queuing was not specified in installedprofile definition (RAQ=NO).




User responseEither change the application program to issuereceives until EIBRECV is not set, or specify RAQ=YESin the installed profile definition (If RAQ=YES isspecified, ensure that all input messages are readbefore the transaction is terminated.)

Module:DFHZARQ

ATCV

ExplanationAn application attempted an operation on a logicalunit, but was not in the correct mode for one of thefollowing reasons:

1. When issued by DFHZARQ, CICS cannot performthe current request because another request isoutstanding (EIBSYNC is set). This holds for APPCor non-APPC systems

2. When issued by DFHETL, the application iscommunicating with an APPC system, and is notin the correct state to perform the attemptedoperation. This holds for APPC systems only

3. When issued by DFHZISP, a TCTTE free wasrequested, and there is an outstanding sync pointrequest. This holds for non-APPC systems only

4. When issued by DFHZISP, a TCTTE free wasrequested, the TCTTE is in receive mode, andRAQ=NO was specified in the installed profiledefinition. This holds for non-APPC systems only.


User responseThe response depends on the reason for the error asfollows:

1. Issue a sync point and then issue the request.2. Issue the free request and reallocate the session.3. Either change the application to issue receives until

EIBRECV is not set, or specify RAQ=YES in theinstalled profile definition. (If you specify RAQ=YESin the installed profile definition, ensure that allinput messages are read before the transaction isterminated.)

4. See the CICS documentation where rules for thecorrect use of commands are given. Then correctthe application.

The application program has attempted an operationon a logical unit that is invalid, because the program'scurrent status on the session with that logical unitdoes not permit it. An investigation of the TCTTE (thatis, Session), status bytes, and TCA type of requestbytes will reveal which of the above problems arerelevant.

When the cause of the problem has been ascertained,the application program should be changed to ensurethat the session-oriented information is acted uponbefore any further requests are sent across thatsession. The session status information is madeavailable to the application program in the execinterface block (EIB) immediately following theexecution of RECEIVE, CONVERSE, or RETRIEVErequests across the session. The relevant bytes mustbe tested, strictly in the order shown, and actedupon, before any further operations are attemptedon the session. In addition, the status informationbytes themselves are necessarily volatile in that theyare reset before the execution of every EXEC CICS...statement. Thus it is good programming practiceto save them into application user storage after aRECEIVE, CONVERSE, or RETRIEVE for later testing.The states are:

1. EIBSYNC

the application must take a syncpoint

2. EIBFREE

the application must free the session (or terminatewhen the session will be freed automatically)

3. EIBRECV

the application must continue receiving data byissuing further RECEIVE commands; by definition,data cannot be sent while in this state.

Some of these status tests can sometimes be omitted(for example, testing of the EIBSYNC status is notessential if it is known that the application programon the remote system never issues sync point requestsitself). However, the tests should always be carriedout, particularly if the remote application might beamended at a future date, in which event the sessionhandling logic may well be altered. Also, it may be thatthe remote transaction itself causes an unsuspectedflow on the session. For example, if the remoteprogram issues EXEC CICS SEND..... LAST across thesession, followed by RETURN, a syncpoint request(RQD2) will be added onto the transmitted data.(The application programmer is referred to the CICSdocumentation for a discussion of this topic). Asa result of this addition, an unsuspected syncpointrequest is received by the local application, whichabend if the session is freed without the sync pointrequest being honored.


Note:

An ATCV abend is also raised by module DFHETL ifa state error occurs during processing of an APPCmapped application (that is, the program attempts toperform an operation while in the wrong state). Thehandling of APPC mapped applications is describedin the CICS Diagnostics reference. Some commandsare processed by DFHZARQ, as above, and othersby various other modules invoked by DFHETL. Rulesfor using commands for APPC are given in the CICSdocumentation. Reference to this guide should revealthe programming error.

Problem determinationRegister 12 addresses the current TCA. Register 10and field TCAFCAAA address TCTTE. The terminal byteTCTTECRE has bit TCTEUCOM (X'02') set if sync pointis required, and TCTEUFRT (X'04') set if Free Sessionis required; TCTESMDI has TCTEUSMD (X'02') set if theapplication is in SEND mode. TCTERCVI has TCTEURCV(X'01') set if the application is in RECEIVE mode. BitTCTESRAQ (X'80') in byte TCTEIRAQ indicates thatread-ahead queuing is coded on the installed profiledefinition for this transaction.

The type-of-request bits in the TCA are set as follows:

• TCATPOS1 TCATPIS (X'01') Signal requested.

– TCATPFRE (X'03') Free TCTTE.• TCATPOS2 TCATPORR (X'10') Receive requested.

– TCATPOWR (X'01') Send requested.

Analysis:

Number Label Description

DFHZARQ1. TCZAQW8 Attempting to receive when sync point or Free Session outstanding.2. TCZAQ2W Attempting to send while in receive mode.3. ZARQNOPG Issuing SIGNAL while in send mode.

DFHZISP4. ZISPVTCK Attempting to free session while sync point request is outstanding.

Module:DFHETL, DFHZARQ, DFHZISP

ATCW

ExplanationThe system has been generated without an installedprofile definition for an LU6.1 or APPC session.


User responseNotify the system programmer of the error.


ATCX

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call tothe storage manager (SM) domain. The domain thatdetected the original error provides an exception trace,a console message and, possibly, a system dump(depending on the options specified in the dumptable).

An application program that issues terminal controlrequests after an ATCX abend may cause furtherproblems.



For module list,see Diagnostics reference.

Module:DFHBSMIR, DFHBSMPP, DFHBSM62, DFHBSS,DFHBSTB, DFHBSTB3, DFHBSTC, DFHBSTZ,DFHBSTZB, DFHBSTZO, DFHBSTZR, DFHBSTZV,DFHBSTZ1, DFHBSTZ2, DFHBSZZS, DFHAPRT,DFHCRP, DFHQRY, DFHZARL, DFHZARQ, DFHZERH,DFHZGET, DFHZFRE, DFHZNAC, DFHZRVS, DFHZSUP,DFHMRXM, DFH62XM DFHZTSP, DFHZXST

ATCY

ExplanationAn error has occurred during the processing of aninbound function management header (FMH). Eithera length error has been detected, for example,incomplete FMH received, or an invalid field has beendetected within the FMH.





User responseNotify the system programmer of the error. Theproblem is probably in the remote system that hassent the invalid FMH.

If the inbound FMH is from a system with anearlier release of CICS then you may need to setUSEDFLTUSER. See 'Attach Time Security and theUSEDFLTUSER option' in chapter 12 of the CICSSecurity.

Module:DFHZARQ, DFHZSUP DFHMRXM DFH62XM

ATCZ

ExplanationAn error (INVALID, DISASTER orEXCEPTION response) has occurred on theSET_NETWORK_IDENTIFIER call to the securitydomain as part of opening the CICS VTAM ACB (forexample, EXEC CICS SET VTAM OPEN or CEMT SETVTAM OPEN). The domain that detected the originalerror provides an exception trace, a console message,and depending on the options specified in the dumptable, a system dump.

System actionThe task is abnormally terminated with a CICStransaction dump. The VTAM ACB is closed.

User responseUse the dump, the trace and the console messageto diagnose and correct the original error. Retry thecommand when the earlier error is resolved.

Module:DFHZSLS

ATD3

ExplanationThe task has been purged, probably due to operatoraction such as a CEMT TASK PURGE command. Thetask might also have been purged as a result of CICSissuing a purge request.


User responseUse the transaction dump to determine why the taskwas purged. In particular, if the purge was operatorinitiated, the dump should be useful in determiningwhy this task needed to be explicitly purged.

Module:DFHTDB

ATD9

ExplanationAn incorrect response has been received from a call tothe enqueue (NQ) domain during the processing of anENQUEUE or a DEQUEUE request.


User responseExamine the dump and any exception trace entries forfurther information. Since this is only used for internalenqueues, this abend indicates an error in CICS. Ifyou need further assistance from IBM to resolve thisproblem, see Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHTDB

ATDC

ExplanationA transaction has issued an EXEC CICS READQ,WRITEQ or DELETEQ command against a transientdata queue. The task was suspended, waiting for aresource. While suspended, the task was purged.


User responseInvestigate why the transaction was purged. It mayhave been purged via CEMT or automatically, byDTIMEOUT for example.

Module:DFHETD

ATDS





ExplanationA deadlock timeout condition has been detected.This condition may occur within a transaction thatspecifies DTIMOUT to be nonzero on its installedtransaction definition. Deadlock timeout occurs whena transaction has been waiting or has been suspendedfor longer than the time specified in DTIMOUT.

The abend is driven by the internal CICS event,ENQUEUE.

Analysis: The transaction receiving the ATDS abendmust have been suspended after issuing an ENQUEUErequest.

System actionThe transaction is abnormally terminated. A dump isnot provided (even if a dump table entry has been setup).

User responseThe transaction should be reexecuted, and thesituation causing the SUSPEND to occur may clearitself.

The ATDS abend is to be expected occasionally, unlessDTIMOUT is set to zero. No special action is necessary.

Module:DFHTDB

ATDY

ExplanationTransient data initialization has failed. A consolemessage, DFH12xx, gives the reason for the failure.

System actionTransient data initialization terminates abnormally.This abend is always followed by an ATDZ abendfor the failing function, and by message DFHSI1521(if CICS abends unconditionally), or messageDFHSI1522, which prompts you to reply GO orCANCEL.

User responseSee the associated console message for informationregarding the cause of the failure. Then respond tomessage DFHSI1522, if it has been issued.

Module:DFHTDRP

ATDZ

ExplanationA CICS function invoked by transient data initializationhas failed. If the failing function is a transient dataroutine, this abend is preceded by a console messageand an ATDY abend.

System actionTransient data initialization terminates abnormally.This abend is always followed by message DFHSI1521(if CICS abends unconditionally), or messageDFHSI1522, which asks you to reply GO or CANCEL.

User responseRefer to the associated console message for furtherinformation regarding the cause of the failure. Thenrespond to message DFHSI1522, if it has been issued.

Module:DFHTDRP DFHTDB

ATFE

ExplanationA FREEMAIN request to the storage manager hasfailed while CICS was executing a CEDA CHECK orCEDA INSTALL command.

System actionCICS abnormally terminates the task with atransaction dump.

User responseUse the dump and any associated messages issuedby the storage manager to investigate the FREEMAINfailure.

Module:DFHTOUT1

ATGE

ExplanationA GETMAIN request to the storage manager has failedwhile CICS was executing a CEDA CHECK or CEDAINSTALL command.

System actionCICS abnormally terminates the task with atransaction dump.


User responseUse the dump and any associated messages issuedby the storage manager to investigate the GETMAINfailure.

Module:DFHTOUT1

ATMA

ExplanationThe task was purged before a GETMAIN request to thestorage manager (SM) domain was able to completesuccessfully. The domain that first detected the purgedcondition will have provided an exception trace.





When CICS purges a task, it does so to allow anoperation to complete which would be held up by thepresence of active tasks.

Module:DFHTMP

ATMB

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe storage manager (SM) domain. The domain thatdetected the original error will have provided anexception trace, a console message and, possibly, a

system dump (depending on the options specified inthe dump table).



Module:DFHTMP

ATNA

ExplanationA terminal operator entered the transactionidentification for NACP.


User responseDo not reenter the NACP transaction identification(CSNE).

Module:DFHZNAC

ATNB

ExplanationThe application program has issued a terminal controlrequest for a terminal for which a previous requestwas terminated with an abend AZCT, because of a readtimeout condition. The terminal control blocks are notin a fit state to allow a new request to be processed.


User responseChange the application program to issue an abendwhen handling an abend AZCT.

Module:DFHZARQ

ATNC


ExplanationThe application program has issued a terminal controlrequest for a terminal for which a previous terminalcontrol request was terminated with an abend ATCH,because the task was purged. The terminal controlblocks are not in a fit state to allow a new request tobe processed.


User responseChange the application program to issue an abendwhen handling an abend ATCH.

Module:DFHZARQ

ATND

ExplanationThe node error program (NEP) or NACP decides that atask should abnormally terminate, but the task is at acritical point of processing and immediate terminationwould put the integrity of the system at risk.

System actionThe task is abnormally terminated with a CICStransaction dump when the task next requests anyaction against the terminal, or issues a sync pointrequest involving the terminal.

User responseCheck destination CSMT for possible furtherinformation. Use the dump to determine why the taskwas abnormally terminated by NEP. Abend ATND isoften associated with delayed response by the taskdue to a problem with a resource. If delayed longenough, a user might cancel their emulator session,triggering an ATND abend. If you suspect this is thecase, investigate possible slow down or hangs in tasks.

Module:DFHZARQ, DFHZARL, DFHZSUP

ATNI

ExplanationThere are two forms of this abend:

VTAM form

The node error program (NEP) or NACP decidesthe task should be abnormally terminated.DFHZNAC informs the request module to abendthe transaction after the TC unit has completed.

Non-VTAM form

The terminal error program (TEP) or terminalabnormal condition program (TACP) decides thetask should be abnormally terminated. DFHTACPinforms DFHZARQ to abend the transaction afterthe TC unit has completed.


User responseThis usually occurs when, due to a hardware failure, anetwork device rejects the data stream sent to it. Thedevice itself may indicate an error code that will givea specific reason for the rejection. Check the CSMT logfor further information.

This abend can also result from an error in a connectedsystem such as a mirror transaction abend.

Abend ATNI can occur if a user application does notcorrectly handle an error return code from an externalresource manager, such as DB2.

For the NEP (VTAM) form, run a VTAM trace type=BUFfor the logical unit and repeat the error.

For the TEP (non-VTAM) form, run a link trace for theline or local channel address for the device.

Examine the data stream and error response todetermine the cause of the error.

This type of error occurs if the definitions in the TCT donot match the attributes of the actual device.

Module:DFHZARL, DFHZARM, DFHZARQ, DFHZRAQ, DFHZSUP

ATOA

ExplanationYou have attempted to invoke the CESC transactionwith a terminal as principal facility. This is not allowed.

System actionCICS terminates the CESC transaction. No dump isproduced.


User responseEnsure that the CESC transaction is not run against aterminal.

Module:DFHCESC

ATOB

ExplanationCICS has received an abnormal response from anEXEC CICS START TRANSACTION(CESC) request. Thisis caused by an internal error.

System actionCICS terminates the CESC transaction with a dump.


Module:DFHCESC

ATOC

ExplanationCICS has received an abnormal response from arequest to DFHZCUT to timeout a local userid table(LUIT). This is caused by an internal error in DFHZCUT.



Module:DFHCESC

ATOD

ExplanationCICS has received an abnormal response from anEXEC CICS CANCEL TRANSACTION(CESC) request.



Module:DFHCESC

ATOE

ExplanationCICS cannot determine the time at which an XRFtakeover began.



Module:DFHCESC

ATOF

ExplanationCICS has received an abnormal response from anEXEC CICS DELAY TRANSACTION(CESC) request.



Module:DFHCESC

ATOG

ExplanationCICS has received an abnormal response from anEXEC CICS START TRANSACTION(CEGN) request. Thisis caused by an internal error.

System actionCICS terminates the CEGN transaction with a dump.








Module:DFHCESC

ATOH

ExplanationAn attempt has been made to invoke the CESCtransaction with an invalid function code. TheCESC transaction should only be invoked by CICS.Valid codes are TERM_TIMEOUT, XRF_TIMEOUT, andENABLE_TIMEOUT.

The most likely cause of this error is an invalid attemptby a user to invoke CESC.

System actionCICS terminates the CESC transaction with atransaction dump.

User responseDetermine how CESC was invoked. If it was invokedby CICS, you will need further assistance from IBM toresolve this problem. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHCESC

ATOT

ExplanationAn error has occurred in the invocation of the CEGNtransaction. CEGN has issued an EXEC CICS RETRIEVEcommand to retrieve the CEGN parameter list. Eitherthe EXEC CICS RETRIEVE command has failed or it hassucceeded but the retrieved data is invalid.

The most likely cause of this error is an invalid attemptby a user to invoke CEGN (for example, from a terminalor via an EXEC CICS START request).

System actionCICS terminates the CEGN transaction with atransaction dump.

User responseDetermine how CEGN was invoked. If it was invokedby CICS, you will need further assistance from IBM to

resolve this problem. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHCEGN

ATOU

ExplanationThe CEGN transaction has attempted to issue an EXECCICS RETURN but the command has failed.



Module:DFHCEGN

ATOV

ExplanationThe CEGN transaction has attempted to issue an EXECCICS GETMAIN, ASSIGN, or SEND but the commandhas failed.



Module:DFHCEGN

ATPA

ExplanationAn error occurred when trying to estimate the length ofa CICS message owned by the message domain.











Module:DFHTPR.

ATPB

ExplanationAn error occurred when trying to retrieve a CICSmessage from the message domain.



Module:DFHTPR.

ATPC

ExplanationAn error occurred when trying to estimate the length ofa CICS message owned by the message domain.



Module:DFHTPQ.

ATPD

ExplanationAn error occurred when trying to retrieve a CICSmessage from the message domain.



Module:DFHTPQ.

ATPE






When CICS purges a task, it does so to allow anoperation to complete which would be held up by thepresence of active tasks.

Module:DFHTPQ, DFHTPR.

ATPF

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call tothe storage manager (SM) domain. The domain thatdetected the original error will have provided anexception trace, a console message and, possibly, a






system dump (depending on the options specified inthe dump table).



Module:DFHTPQ, DFHTPR.

ATRA

ExplanationThe field engineering global trap exit program,DFHTRAP, requested task abnormal termination.However, the currently active task was not a systemtask (for example, task dispatcher) and it was notabout to abend.

System actionCICS disables the trap exit so that it will not bereentered, and terminates the currently active taskabnormally.

User responseThis is a user-requested task abend.

If you want to use the trap again, you must reactivate itas follows:

CSFE DEBUG,TRAP=ON

You should use the global trap exit only inconsultation with an IBM support representative.

Module:DFHTRP

ATSA

ExplanationThe transaction CTSD was attached other than by aninternal request from the TS domain.


User responseInvestigate why the CTSD transaction was started.This transaction is intended for CICS internal use onlyand should not be started by a user or from a terminal.

Module:DFHTSDQ

ATSB

ExplanationThe transaction CTSD was attached with invalidparameters.


User responseYou need further assistance from IBM to resolve thisproblem. See Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHTSDQ

ATSC

ExplanationThe task was canceled during execution of atemporary storage command.


User responseInvestigate the reason the task was canceled. Thetask has been canceled by the main terminaloperator or automatically by either the deadlocktimeout (DTIMEOUT) mechanism or the read timeout(RTIMOUT) mechanism.

Module:DFHEITS, DFHICP, DFHTSP

ATSD

ExplanationAn INVALID or DISASTER response was received froma request to the Temporary Storage (TS) Domain.




User responseThere has been an earlier failure which lead to theresponse from TS. Investigate the earlier failure (whichis accompanied by a console message and a systemdump).

Module:DFHEITS, DFHICP, DFHTSP

ATSP

ExplanationA task has attempted to issue a WRITEQ TS request fora recoverable TS queue that has already been deletedin the same unit of work.


User responseCorrect the application to avoid issuing a WRITEQ TSrequest to a recoverable queue in a unit of work inwhich the queue has already been deleted.

Module:DFHEITS, DFHTSP

ATSQ

ExplanationA move of data to or from temporary storage hasfailed. The probable reason is that the size of the areabeing passed to CICS is inconsistent with the datalength being used.


User responseIdentify the failing temporary storage request in theapplication and verify whether the length supplied onthe request agrees with the data area size. Correct theapplication as appropriate.

Note:

If the error occurs in DFHTSP and not in DFHETS,there is probably an internal logic error in temporarystorage. In this case you will need further assistancefrom IBM. See Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHEITS

ATSU

ExplanationA DISASTER response caused by an IOERR wasreceived from a request to the Temporary Storage (TS)Domain.


User responseThere has been a failure during the creation of atemporary storage record. The likelihood is that anIOERR occurred during the buffer preparation prior tothe new record being added to it. It is recommendedthat the queue be deleted to avoid future references tothe failed record.

Module:DFHEITS, DFHTSP, DFHICP

ATUF

ExplanationInsufficient space exists to build the parameter list forthe DYNALLOC SVC.

System actionThe task is abnormally terminated and a dump istaken.


Module:DFH99KO




AUxx abend codesAUEL

ExplanationInternal logic error in CICS user exit management. Thisarises when an attempt to obtain or release the lock onthe chain of EPB's fails unexpectedly.



Module:DFHUEM, DFHERM.

AUEP

ExplanationThe task has been abnormally terminated becausea return code of UERCPURG has been sent to the

User Exit Handler by a User Exit Program. The valueof UERCPURG is defined by the macro DFHUEXITTYPE=EP, ID=xxxxxxxx, where xxxxxxxx is the exitpoint by which the exit program is enabled. This codedoes not apply to exit points in domains. The exitprogram returns this value when it has made a requestfor CICS services using the exit programming Interface(XPI) and when the XPI call has had a RESPONSE codeof PURGED. Exit programs must not set UERCPURGreturn code under any other circumstance.


User responseRefer to the Developing system programs for CICS forthe use of this return code.

Module:DFHUEH

AWxx abend codesAW2A

ExplanationThe DFHW2A Web2.0 alias program was executed ina transaction that was not attached by CICS WebSupport. This is usually caused by attempting to issuethe CW2A transaction directly from a terminal. This isnot supported.


User responseDo not attempt to execute the CW2A transaction froma terminal.

Module:DFHW2W2

AWB2

ExplanationThe CICS Web Interface has encountered an errorwhile performing a transaction attach call for the aliastask.

System actionMessage DFHWB0727 describing the error is writtento the CWBO transient data destination and a traceentry is made.

User responseSee the associated message for guidance.

Module:DFHWBXN

AWB3

ExplanationCICS Web transaction, CWXN, has been illegallystarted either with data, or by a user at a terminal,with the wrong start code.




System actionThe CICS Web Interface is not started.

User responseCICS Web Transaction Execution should only ever bestarted by Sockets Domain using DFHXMAT ATTACH,not by a user at a terminal or with data.

Module:DFHWBXN

AWB4

ExplanationThe CICS Web Transaction Execution has received abad response from an INQUIRE_TRANSACTION call todetermine the start code for the CWXN transaction.

System actionThe CICS Web Interface is not started.

User responseCICS Web Transaction Execution should only ever bestarted by Sockets Domain using DFHXMAT ATTACH,not by a user at a terminal or with data.

Module:DFHWBXN

AWB5

ExplanationThe CICS Web Interface Server Controller couldnot continue with enable processing because therequested port is not available.

System actionAn exception trace entry 4106 is written, and messageDFHWB0131 is issued.

User responseTerminate the TCP/IP application which is using therequested port, and use CBWB to enable the featureagain, or use CWBC to enable the CICS web Interfaceusing a different port number.

Module:DFHWBM

AWB7

ExplanationThe CICS Web Interface environment variablesprogram was invoked, but the invoking transactiondoes not appear to be executing in a valid Webenvironment.

System actionThe program writes an exception trace point 4623.

User responseDetermine how the environment variables programwas invoked. It is only meaningful to execute theprogram from a transaction that has been initiatedfrom the Web, either through the CICS Web Interfaceor through the Business Logic Interface.

Module:DFHWBENV

AWB8

ExplanationThe CICS Web Interface environment garbagecollection task CWBG has been started directly froma terminal. This is not permitted.


User responseNone.

Module:DFHWBGB

AWB9

ExplanationThe CICS Web Interface connection manager faileddue to lack of storage.

System actionA transaction dump is taken.


Module:DFHWBC01



AWBA

ExplanationCICS Web Receive process has received an exceptionresponse from the Web Send Receive function,DFHWBSR, which could be one of the following errors:

• An error in the Analyzer program• No Analyzer program specified• Unable to link to Analyzer program• An Analyzer data length error• An Analyzer header length error• A codepage conversion error• A storage error occurred• An error that the connection has been closed• A sockets receive error

System actionAn error message is sent to the client and the CWBOtransient data queue.

User responseRefer to any error messages accompanying this abendto determine why the abend has occurred.

Module:DFHWBXN

AWBB

ExplanationThe incoming parameter list to the CICS Web BusinessLogic Interface program is not in the expected format.At present, the structure is assumed to be fixed andonly a single version level is recognized.

System actionThe CICS Web Business Logic Interface program is notexecuted.

User responseEnsure that the program receives a parameter list inthe correct format.

Module:DFHWBBLI

AWBC

ExplanationNo commarea was passed to a CICS Web Interfaceutility program. One of the utility programs suppliedwith the CICS Web Interface was executed, but thecommarea that was passed was absent or was tooshort to contain valid information.

System actionThe CICS Web Interface utility is not executed.

User responseEnsure that the program passes a commarea that islong enough to contain the expected parameters forthe utility you are invoking.

Module:DFHWBENV, DFHWBTL

AWBD

ExplanationCICS detected an error during transaction initializationfor a directly attached user transaction because CICSeither failed to authenticate the user or Web Receiveprocess has received an exception response from theWeb Send Receive function, DFHWBSR, which couldbe one of the following errors:

• A storage error occurred• Method in the request not implemented by the

server• A socket receive error• Request header is invalid• A codepage conversion error• An error that the connection has been closed

System actionAn error message is sent to the client and the CWBOtransient data queue.

User responseRefer to any error messages accompanying this abendto determine why the abend has occurred.

Module:DFHWBXM

AWBE


ExplanationThe CICS Web Interface detected that a Converterprogram attempted to change the address of theresponse buffer when it was not allowed to do so.

System actionThe data in the new response buffer is not returned tothe Web browser. A CICS transaction dump is taken.

User responseThe Converter program is only allowed to replace theresponse buffer if the converter_volatile flag inthe Converter parameter list is set to '1'. Check thatyour Converter program is not trying to return a newresponse buffer when this flag is set to '0'.

Module:DFHWBBLI

AWBF

ExplanationThe CICS Web Interface alias detected an error inits initialization. The alias was not started by EXECCICS START, or there was an error in the EXEC CICSRETRIEVE command for the start data.

System actionIf there is an error in EXEC CICS RETRIEVE, messageDFHWB0103 is written to the CWBO destination. ACICS transaction dump is taken.

User responseIf the alias was not started by EXEC CICS START,check if it is being started from a terminal. This is notallowed. Otherwise, see the associated message forguidance.

Module:DFHWBA

AWBH

ExplanationThe CICS Web Interface alias detected a logic error.

System actionAn exception trace entry 454F is written. MessageDFHWB0106 is written to the CWBO destination. ACICS transaction dump is taken.

User responseUse related diagnostics to determine the userresponse.

Module:DFHWBA

AWBI

ExplanationThe CICS Web Interface alias received an unexpectedresponse from EXEC CICS ASSIGN STARTCODE

System actionAn exception trace entry 4544 is written. MessageDFHWB0102 is written to the CWBO destination.


Module:DFHWBA

AWBJ

ExplanationThe CICS Web Interface alias received an unexpectedresponse when it switched to the RP TCB.

System actionAn exception trace entry 454E is written. MessageDFHWB0105 is written to the CWBO destination. Atransaction dump is taken.


Module:DFHWBA

AWBK

ExplanationThe CICS Web Interface alias detected an abend in theconverter or the CICS program servicing the request.





Module:DFHWBA

AWBL

ExplanationThe CICS Web Interface alias detected an error in anEXEC CICS LINK command for program DFHWBBLI.

System actionAn exception trace entry 4543 is written. MessageDFHWB0101 is written to the CWBO destination. Atransaction dump is taken.


Module:DFHWBA

AWBM

ExplanationThe CICS Web Interface alias detected errorresponse from the Business Logic Interface programDFHWBBLI.

System actionMessage DFHWB0101 is written to the CWBOdestination. A transaction dump is taken.


Module:DFHWBA

AWBN

ExplanationThe CICS Web Interface alias detected an error in anEXEC CICS LINK command for program DFHWBEP.

System actionMessage DFHWB0101 is written to the CWBOdestination. A transaction dump is taken.


Module:DFHWBA

AWBO

ExplanationThe CICS Web Interface alias program has receiveda non-HTTP request for an HTTP service or a SSLrequest has been sent to a non-SSL TCPIPSERVICE.

System actionMessage DFHWB0114 is written to the CWBOtransient data destination and a transaction dump istaken. An exception trace entry, 4567, is also written.


Module:DFHWBA

AWBP

ExplanationThe CICS Web Interface alias has detected that theapplication has started sending a chunked responseover the socket but has not terminated the sequenceof web send chunk commands with a zero lengthchunk.

System actionA transaction dump is taken.

User responseCheck the application to see why the terminatingchunk was not sent.

Module:DFHWBA

AWBQ

ExplanationThe CICS Web Business Logic Interface programdetected an error in its parameter list.

System actionIf the abend was issued from the Business LogicInterface program, DFHWBBLI, an exception trace


entry '4581' is made and message DFHWB0119 iswritten to the CWBO transient data destination. If theabend was issued from the Web Interface program,DFHWBA1, an exception trace entry '4560' is writtenand message DFHWB0124 is sent to the CWBOdestination. A transaction dump is taken.


Module:DFHWBA1, DFHWBBLI

AWBR

ExplanationThe CICS Web Business Logic Interface programdetected a logic error.

System actionIf the abend was issued from the Business LogicInterface program, DFHWBBLI, an exception traceentry '4583' is made and message DFHWB0118 iswritten to the CWBO transient data destination. If theabend was issued from the Web Interface program,DFHWBA1, an exception trace entry '4558' is writtenand message DFHWB0123 is sent to the CWBOdestination.


Module:DFHWBA1, DFHWBBLI

AWBU

ExplanationThe CICS Web Interface connection manager could notget storage to send a message to the terminal.

System actionProcessing continues.


Module:DFHWBC01

AWBV

ExplanationThe CICS Web Interface connection manager detectedan error response on EXEC CICS DEQ.



Module:DFHWBC04

AWBX

ExplanationThe CICS Web Interface connection manager wasstarted against an invalid terminal type.



Module:DFHWBC01

AWBZ

ExplanationThe CICS Web Interface connection manager detecteda NOTAUTH response to EXEC CICS EXTRACT EXIT.

System actionMessage DFHWB1902 is written to the CWBOdestination.


Module:DFHWBC0B

AWC1



ExplanationThe CICS Web Interface 3270 bridge exit DFHWBLTcould not establish a partnership with the Webterminal translation task which started the abendedtransction.

System actionAn exception trace entry 4106 is written, and messageDFHWB0131 is issued.


Module:DFHWBLT

AWC2

ExplanationThe CICS Web Interface 3270 bridge exit DFHWBLTwas passed an invalid state token by attachprocessing.

System actionAn exception trace entry 410C is written, and messageDFHWB0130 is issued.

User responseUse related diagnostics to determine the userresponse. On a busy CICS region, the most likelycause is that the bridged transaction started after thestate data had been discarded by Web 3270 garbagecollection process.

Module:DFHWBLT

AWC3

ExplanationAn application using the CICS Web 3270 functionissued an unsupported combination of BMS andTerminal Control commands.

System actionAn exception trace entry is written.


Module:DFHWBLT

AWC4

ExplanationThe CICS Web Interface 3270 bridge exit DFHWBLThas been reinvoked after returning an earlier error.

System actionAn exception trace entry is written.


Module:DFHWBLT

AWC5

ExplanationThe CICS Web Interface 3270 bridge exit DFHWBLTabended during attach processing because it could notgetmain a brxa user area.

System actionMessage DFHWB0132 is issued, and an exceptiontrace entry 410D is written.

User responseUse related diagnostics to determine the userresponse. The most likely cause of this abend is thatCICS is having storage problems.

Module:DFHWBLT

AWC6

ExplanationThe CICS Web Interface 3270 bridge exit DFHWBLThas detected an inconsistency in its requestparameters or state data.

System actionMessage DFHWB0133 is issued, and an exceptiontrace entry is written.


User responseUse related diagnostics to determine the userresponse. The most likely cause of this abend is astorage overwrite.

Module:DFHWBLT

AWC7

ExplanationCICS detected an error during transaction initializationfor a CICS Web alias transaction.

System actionMessage DFHWB0360 is issued. No transaction dumpis taken for this abend.

User responseUse related diagnostics to determine the userresponse. The most likely cause of this abend isan invalid userid being passed to CICS by the CICSWeb Interface Analyzer user replaceable module. Theuserid is invalid if:

• It is not defined in the external security manager• It is revoked• It is not authorized to access this CICS region

Module:DFHWBXM

AWC8

ExplanationCICS detected an error during transaction initializationfor a CICS Web alias transaction.

System actionA transaction dump is taken for this abend.


Module:DFHWBXM

AWC9

ExplanationCICS detected an error during transaction initializationfor a CICS IPCONN acquire server-side transaction.

System actionA severe error message and system dump should havepreceeded this abend.

User responseUse related diagnostics to determine the cause of theproblem.

Module:DFHWBXM

AWKY

ExplanationA request to PURGE or WRITE a record using theglobal catalog during warm keypointing has failed.


User responseCheck for problems with the global or local catalog.See any DFHCCnnnn messages issued by the CICScatalog domain for further guidance.

Module:DFHWKP

AWSA

ExplanationDFHWSSE1 failed to address the EIB.



Module:DFHWSSE1

AWSC

ExplanationA container which is required by a SOAP Featurepipeline stage was not found.




User responseCheck that user-written programs in earlier pipelinestages use the correct containers.

Module:DFHWSPMI,DFHWSPMO

AWSD

ExplanationDFHWSSE1 failed to read a Container.



Module:DFHWSSE1

AWSH

ExplanationA BTS activity that represents a stage in the SOAPFeature pipeline was found by the pipeline manager tobe in an incorrect state.


User responseCheck that user-written programs in earlier pipelinestages use the correct BTS protocols.

Module:DFHWSPMI,DFHWSPMO

AWSJ

ExplanationDFHWSSE1 failed to get the length of a Container.



Module:DFHWSSE1

AWSL

ExplanationThe SOAP Feature inbound pipeline manager could notlink to the message adapter.


User responseCheck previous CICS messages to determine why themessage adapter could not be linked to.

Module:DFHWSPMI

AWSN

ExplanationAn EXEC CICS DEFINE COUNTER or EXEC CICS GETCOUNTER command has returned a bad response.


User responseCheck the options table DFHNCOPT for possibleerrors. Look in the CICS job log for any AXMSCnnnnmessages.

Module:DFHWSDSH

AWSP

ExplanationAn application making a Web Service request passeda SOAPAction HTTP request header exceeding 256bytes in length to the SOAP Feature pipeline.





User responseCheck that SOAPAction headers exceeding 256 bytesin length are not constructed by applications invokingWeb Services.

Module:DFHWSRT

AWSQ

ExplanationThis is normal behavior when a user stage of thepipeline abends.


User responseCorrect the user abend.

Module:DFHWSPMI

AWSR

ExplanationEither the TARGET-URI or the REQUEST-BODYcontainer was not found when an application invokedthe SOAP Feature pipeline to make a Web Servicerequest.


User responseCheck that the application making the Web Servicerequest supplies the required containers.

Module:DFHWSRT

AWSS

ExplanationThe SOAP Feature service provider pipeline wasrequested to invoke the message adapter under a

different transaction ID or user ID to the pipeline, butwas unable to satisfy the request.


User responseCheck that transaction ID and user ID requested arevalid, and that the user ID with which the pipeline isrunning is a surrogate of the requested user ID.

Module:DFHWSPMI

AWST

ExplanationThe HTTP or WebSphere MQ transport stage of theSOAP Feature pipeline has encountered an input oroutput error.


User responseUse CICS or WebSphere MQ messages to help youdetermine the cause of the problem. The error may betransient, in which case you can retry.

Module:DFHWSTOH

AWSU

ExplanationAn invalid URI was passed to the SOAP Featurerequester pipeline as the location of a Web Serviceprovider.


User responseCheck that applications making Web Servicerequesting specify valid URIs for locations of WebService providers.

Module:DFHWSRT

AWSX


ExplanationDFHWSSE1 received an unexpected response from theWSSE API.



Module:DFHWSSE1

AWSY

ExplanationA problem was encountered in the DFHPIRT outboundrouter program. This usually implies that one of

the containers used by DFHPIRT was not populatedcorrectly.


User responseCheck that applications using DFHPIRT correctlypopulate the control containers required for pipelineprocessing.

Module:DFHPIRT

AXxx abend codesAXF0

ExplanationA task has been purged due to lack of storage in adynamic storage area (DSA).


User responseTry the transaction again later.

If the short-on-storage condition persists, considerincreasing the size limit of the CICS DSAs. You can varythe DSAs dynamically using the DSALIM and EDSALIMparameters on the CEMT main terminal command.

Module:DFHXFP

AXF1

ExplanationThe storage manager module, DFHSMGF, has returneda condition not expected by DFHXFP.


User responseLook for any related CICS messages and abends todetermine if there has been a prior failure in CICSstorage.

Module:DFHXFP

AXF2

ExplanationA task has been purged due to lack of storage in theDSA.


User responseTry the transaction again later.

If the short-on-storage condition persists, increase thesize of the dynamic storage area using the DFHSIT DSAparameter.



Module:DFHXFP

AXF3

ExplanationThe storage manager module DFHSMMC has returneda condition not expected by DFHXFP.


User responseLook for any related CICS messages and abends todetermine if there has been a prior failure in CICSstorage.

Module:DFHXFP

AXF4

ExplanationThe task was purged before a GET_BUFFER requestto the EXEC interface service routines module(DFHEISR), was able to complete successfully. Thedomain that first detected the purged conditionprovides an exception trace.





Module:

DFHXFX

AXF5

ExplanationAn error (INVALID, DISASTER, or unexpectedEXCEPTION response) has occurred on a call to theEXEC interface service routines module(DFHEISR).The domain that detected the original error providesan exception trace, a console message, and possibly, asystem dump (depending on the options specified thedump table).



Module:DFHXFX

AXF8

ExplanationA keyword such as TOKEN, CONSISTENT,REPEATABLE, UNCOMMITTED, or NOSUSPEND hasbeen specified on a file control command for shippingto a system which does not support these functions.


User responseEnsure that CICS in the file-owning region is at thecorrect level.

Module:DFHXFX

AXFA

ExplanationThe key length for a file control request that is to besent to a remote system has to be obtained from thefile control table, and has proved to be zero.



User responseEnsure that the key length has been defined eitherin the remote file definition that is being used, or asa length option from the application program that isusing it.

Module:DFHXFP

AXFB

ExplanationAn unacceptable function management header (FMH)type has been found. It must be type 05, type 06, ortype 43.



Module:DFHXFP

AXFC

ExplanationThe request passed to the data transformationprogram is unknown to CICS. This abend can alsooccur in an MRO/IRC system as a result of an invalidEXEC CICS START request issued from the user's nodeerror program (DFHZNEP).


User responseSee the Developing system programs for CICS forrestrictions on the use of EXEC CICS commands fromwithin an NEP. If this is not the cause of the abend, youwill need further assistance from IBM. See Workingwith IBM to solve your problem for guidance on how toproceed.

Module:DFHXFP

AXFD

ExplanationThe request that is passed to the data transformationprogram cannot be sent to a remote system; forexample, a storage control request.



Module:DFHXFP

AXFE

ExplanationThe transformation requested does not exist; forexample, a DL/I schedule reply is not recognizedby the outbound request processor in the datatransformation program.



Module:DFHXFP

AXFF

ExplanationAn unacceptable queue organization has been found ina queue model function management header (FMH).










Module:DFHXFP

AXFG

ExplanationAn unacceptable argument number has been foundin the data following a function management header(FMH) of type 43.



Module:DFHXFP

AXFH

ExplanationThe argument number in the data following a functionmanagement header (FMH) of type 43 is acceptable,however, the argument itself is not expected.



Module:DFHXFP

AXFI

ExplanationThe data length for a WRITEQ TD or READQ TD is zero.The abend can also occur when determining the lengthfor file control requests.



Module:DFHXFP

AXFJ

ExplanationThe error code held in UIBFCTR and UIBDLTR cannotbe converted to an equivalent SNA error code.



Module:DFHXFP

AXFL

ExplanationTransformers 2 and 4 expect to receive a functionmanagement header (FMH), possibly followed by userdata. A null chain of data has been received.



Module:DFHXFP

AXFM







ExplanationThe ISCINVREQ condition has been raised. This canhappen when the resource proves to be on yet anotherremote system, that is, when daisy-chaining is active.


User responseCheck that daisy-chaining of requests is intended andthat all relevant intersystem links are in service.

Module:DFHXFP

AXFN

ExplanationThe user domain module, DFHUSAD, has returned acondition not expected by DFHXFX.


User responseLook for any related CICS messages, abends orexception traces to determine if there has been a priorfailure in user domain or security domain.

Module:DFHXFX

AXFO

ExplanationThe check on the DS and DBA parameters in anattach function management header (FMH) has failed.This abend represents a user error resulting from amismatch in the system definitions for both ends of anintersystem link.



Module:DFHXFP

AXFP

ExplanationCICS requires a second function management header(FMH) to follow an attach FMH. No second FMH wasreceived.



Module:DFHXFP

AXFQ

ExplanationEither the function management header (FMH) justreceived is too short or too long to be a valid FMH,or an expected FMH is not present.


User responseCheck that the transaction profile parameter, INBFMH,is set to ALL. If communicating across a distributedprogram link, ensure that the requested function issupported on the partner system.

Module:DFHXFP

AXFR

ExplanationThe CICS command level interface imposes amaximum length of 32 767 for data. The length of thedata just received exceeds this limit.




Module:DFHXFP

AXFS

ExplanationA PSB has been scheduled successfully. However, themaximum possible length of an I/O area exceeded65 535. This abend is likely to occur if path calls areused to retrieve large segments, and/or if FLS causesexcessive expansion of segments.



Module:DFHXFP

AXFT

ExplanationAn estimate of the size of the output I/O area has beenmade, and it exceeds the maximum possible size of65 535.

Note:

While the estimated size may exceed the actual size,the difference will only be a few bytes.

This abend is likely to occur if a database calls, inserts,or replaces multiple segments, and many qualifiedsegment search arguments are specified.



Module:DFHXFP

AXFU

ExplanationA two-level cursor is present in a functionmanagement header (FMH) relating to a linear(temporary storage) queue. However, these cursors

are valid only for hierarchical queues that are notsupported by CICS.



Module:DFHXFP

AXFV

ExplanationThe user domain module, DFHUSAD, has returned acondition not expected by DFHXFX.


User responseLook for any related CICS messages, abends orexception traces to determine if there has been a priorfailure in user domain or security domain.

Module:DFHXFX

AXFW

ExplanationAn invalid length specification has been given in a CICScommand-level request corresponding to one of thedata variables.

The CICS-architected FMH is followed by zero or moreself-describing data variables for each parameterspecified.


User responseCheck for an invalid or zero length specified in a CICScommand-level request, or for data truncation in auser-written node error program (NEP).



Module:DFHXFP

AXFX

ExplanationA function shipping request by an APPC link failedbecause

• the remote system does not support full syncpointprotocols, or

• the exchange log name sequence could have failed,resulting in a mismatch, or

• the request has not completed within the allocatedtime (10 seconds).


User responseCheck that the request was directed to the correctremote system, and that the remote system is set upto support full syncpoint protocols (synclevel 2).

Module:DFHXFP

AXFY

ExplanationAn APPC conversation failure has occurred when anattach between CICS systems was issued.



Module:DFHXFP

AXFZ

ExplanationThe monitoring domain module, DFHMNOD, hasreturned a condition not expected by DFHXFX.


User responseLook for any related CICS messages, abends orexception traces to determine if there has been a priorfailure in the monitoring domain.

Module:DFHXFX

AXG1

ExplanationAn unexpected problem occurred in a DPL LINKrequest over MRO with a commarea greater than 24K

The problem occured in transformer 1 sending therequest.

A channel or container command returned anunexpected error.



Module:DFHXFP

AXG2


The problem occured in transformer 2 receiving therequest.




Module:DFHXFP


AXG3


The problem occured in transformer 3 returning theresponse.




Module:DFHXFP

AXG4


The problem occured in transformer 4 receiving theresponse.




Module:DFHXFP

AXGA

ExplanationProgram DFHAPCR has returned an unexpectedresponse. DFHAPCR performs the following functions:-

• Extracts the contents of all containers making up achannel and transmits them to a remote system.

• Recreates the channel and containers from inbounddata received from a remote system.

DFHAPCR has either detected an error in inbounddata or has received an unexpected response whilstextracting or recreating channel data.

One cause of this error is that an EXCIjob using channels and containers has sent aDFHTRANSACTION channel to a CICS release thatdoes not support transaction channels. Transactionchannels are supported in CICS TS 5.2 and higher.


User responseLook for any related CICS messages and abendsto determine if there has been a prior failure inProgram Manager, which manages containers. Lookfor exception trace entries from Program Manager orDFHAPCR to determine the cause of the error.

If an EXCI job is sending a transaction channel to a preCICS TS 5.2 system, change the EXCI job to use a nontransaction channel.

Module:DFHXFX,DFHXFP

AXGB

ExplanationThe application context handling module, DFHMNAC,has returned an unexpected response from functionIS_ACD_SET.



Module:DFHXFP

AXGC

ExplanationThe application context handling module, DFHMNAC,has returned an unexpected response from functionGET_ACD.




Module:DFHXFX, DFHXFP

AXGD

ExplanationThe application context handling module, DFHMNAC,has returned an unexpected response from functionMIRROR_ACD.



Module:DFHXFX, DFHXFP

AXGE

ExplanationA distributed program link (DPL) request, specifyingchannel name DFHTRANSACTION, has also specified aCOMMAREA that is too large for the terminal I/O area(TIOA).


User responseCheck if the request is using the correct length forthe COMMAREA. If a DFHTRANSACTION channel isspecified the COMMAREA size should not exceed 24KB. In this case to accommodate a size greater than24 KB specify a user channel instead of a COMMAREA.

Module:DFHXFP

AXMA

ExplanationAn error has occurred obtaining a lock within thetransaction manager domain.

System actionThe recovery routine of the module in control isinvoked which issues message DFHXM0002 with asystem dump. DFHXM0002 reports the module incontrol at the time of the error.

User responseSee the description of message DFHXM0002 forfurther guidance.


Module:DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD,DFHXMFD, DFHXMLD, DFHXMQD, DFHXMST,DFHXMTA, DFHXMXD, DFHXMXE

AXMB

ExplanationAn error has occurred releasing a lock within thetransaction manager domain.

System actionThe recovery routine of the module in control isinvoked. This routine issues message DFHXM0002with a system dump. DFHXM0002 reports the modulein control at the time of the error.



Module:DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD,DFHXMFD, DFHXMLD, DFHXMQD, DFHXMST,DFHXMTA, DFHXMXD, DFHXMXE

AXMC

ExplanationAn severe error has occurred allocating a uniquetransaction number to a new transaction.

System actionThe recovery routine of the module in control isinvoked. This routine issues message DFHXM0002




with a system dump. DFHXM0002 reports the modulein control at the time of the error.


Module:DFHXMAT, DFHXMXE

AXMD

ExplanationAn attempt has been made to run the CICS internaltask CSXM as a user transaction.


User responseInvestigate why the attempt was made to run CSXM asa user transaction.

Module:DFHXMAB

AXMU

ExplanationDuring transaction attach the userid that had beenassigned to the transaction was found to be invalid.


User responseDetermine how the invalid userid had been assignedto the transaction. It might have been output by auser-replaceable module.

Module:DFHXMAT

AXMY

ExplanationDuring transaction attach an unexpected erroroccurred obtaining transaction class membership.

System actionThe transaction is no longer considered for classmembership. It is then abnormally terminated with aCICS transaction dump.

User responseUse the dump to determine why the transaction failedto obtain membership of its transaction class.

Module:DFHXMAT

AXMZ

ExplanationA serious failure in another component has beendetected by the transaction manager domain.

System actionThe task in control is abnormally terminated with atransaction dump. Further diagnostics should havebeen taken by the failing component.

User responseLook for earlier messages identifying the source of theproblem. Refer to the descriptions of these messagesfor further guidance.

Module:DFHXMTA

AXSA

ExplanationThe CICS security control task could not completebecause a necessary step failed. The task has donesome essential recovery operations and abnormallyterminated itself with code AXSA.

System actionCICS writes a transaction dump for the security controlrestart task.

CICS sends messages to the console, one to identifythe error detected by the security control task, and, ifthe error occurred during initialization, one to say thatsecurity initialization or CEMT PERFORM SECURITYREBUILD has failed. A third message follows either tosay that CICS has terminated abnormally with a dump,or to ask you to reply GO or CANCEL. Depending onthe nature of the original error, you may see messagesfrom some other system component (for example, anaccess method).


User responseFirst, if CICS has requested a response, you mustreply. If you reply 'GO', CICS continues processing,but without support for the external security manager.CICS security still operates. If you reply 'CANCEL',CICS terminates abnormally with a dump.

Use the messages and dumps to find out the cause ofthe failure.

Module:DFHXSMN

AXSB

ExplanationA system transaction has been started from a terminal;this is not permitted. Category 1 transactions can onlybe started internally by CICS.

System actionThe task is abnormally terminated. No transactiondump is taken.

User responseNone.

Module:DFHXMTA

AXSC





If the task was timed out automatically as a resultof the DTIMOUT value being exceeded, this may be

due to insufficient main storage being available forthe number of tasks in the system. If the amount ofmain storage cannot be increased, reduce the numberof tasks in the system to avoid short-on-storagesituations. Another possibility is to increase the valueof the DTIMOUT option for the transaction.

Module:DFHXSMN

AXSD




Module:DFHTCRP

AXSE

ExplanationThe CICS security token service has been calledwithout a channel.


User responseChange the program calling the DFHSAML processor.Ensure that you call it using the interface defined inthe SAML programming interface.

Module:DFHSAML

AXSF


ExplanationThe CICS security token service encountered a severeerror.

System actionA system dump will be taken with an associatedDFHAP0002 message. The task is abnormallyterminated with a CICS transaction dump.


Module:DFHSAML

AXSG

ExplanationThe DFHSAML program is not running in CICS key.


User responseInstall the DFHSAML program definition provided inthe group DFHSAML.

Module:DFHSAML

AXTA

ExplanationThe calculation of the length of data to be shipped hasfailed.



Module:DFHAPRX, DFHXTP

AXTB

ExplanationAn attempt to obtain a buffer to ship data has failed.




AXTC

ExplanationAn attempt to transform data ready for shipment hasfailed.




AXTD

ExplanationNo buffer was received from a remote system.




AXTE







ExplanationIncorrect data was received from a remote system.The data was not long enough.




AXTF

ExplanationNo relay process function management header (FMH)was received from the remote system.




AXTG

ExplanationTransformation of data received from remote systemfailed.


User responseCheck that the reason for failure of the transformationprocess was not incorrect definition of the remoteterminal. In particular check that the user area lengthspecified for the terminal is the same in both local andremote systems. If the terminal definitions are correct,you need further assistance to resolve this problem. If

you need further assistance from IBM to resolve thisproblem, see Working with IBM to solve your problemfor guidance on how to proceed.


AXTH

ExplanationAn attempt to locate terminal identifier failed.




AXTI

ExplanationThe major request byte LUCOPN0 of the DFHLUCparameter list specified to the transaction-routingtransformer is invalid, or corresponds to a request thatis not shipped to a remote system. The parameterlist will be found in the dynamic storage of thetransformer's caller and may be located using theoutput from auxiliary trace.




AXTJ

ExplanationAn unexpected combination of bit settings in the fieldsXTSSTAT and XTSTCOPC in the parameter list of thetransaction-routing transformer was made.










AXTK

ExplanationAn APPC conversation failure occurred when an attachbetween CICS systems was issued.



Module:DFHXTP

AXTL

ExplanationThe processing of APPC mapped data requires thegeneration of an APPC attach FMH with default values.In particular, the sync level requested is defaulted to2. However, the session that is to be used has beenbound with a sync level of 1.




• The remote system is capable of supporting a synclevel of 2.

• Exchange lognames has completed for theconnection. You can use the command CEMTINQUIRE CONNECTION to do this. See the CICS

intercommunication for more details of the exchangelognames process.

• The correct sync level has been requested.

Module:DFHXTP

AXTM

ExplanationAn attempt has been made to route a message-protected transaction over an APPC link bound atsync level 1. The attempt has failed because suchtransactions can be routed only over an APPC link thathas been bound at sync level 2.


User responseIf the transaction is to be routed to CICS OS/2(which is bound at synclevel 1), remove the messageprotection option. If the transaction is to be routedto another host system and message protection isrequired, the link must be redefined so that it can bebound at synclevel 2.

Module:DFHXTP

AXTN

ExplanationThe transaction-routing transformer module detectedthat the application buffer chained off a TCTTE atoffset TCTERCSA has a corrupted header. This iscaused either by a CICS logic error or by a storageoverwrite.




AXTO






ExplanationAn exception response has been returned to thetransaction-routing transformer module from the CICSsecurity manager. Prior to the call to the CICS securitymanager, the transformer module detected that ashipped terminal definition had preset security. Thetransformer then invoked the CICS security manager inorder to perform a preset security signon for the useridsent with the shipped terminal information. It is thispreset security signon attempt which failed.

System actionThe transaction routing request is terminated and amessage is sent to the terminal owning region (TOR)to indicate that the transaction routing request hasfailed. The CICS security manager issues a DFHSNxxxxmessage to the transient data queue, CSCS.

User responseThe most likely cause of this abend is that the terminalbeing shipped to the application owning region (AOR)has preset security with a userid which is not validin the AOR. To confirm this, check the associatedDFHSNxxxx message on the CSCS transient dataqueue in the AOR which gives the precise reason forthe failure of the preset security signon request. Thiscould be the result of an unauthorized transactionrouting request.


AXTP

ExplanationAn exception response has been returned tothe transaction-routing transformer module fromDFHCCNV FUNCTION(CONVERT_DS3270_FOR_SBCS).The module was called for a CICS client virtualterminal which requested conversion from ASCII toEBCDIC for data coming from the client. However, theconversion failed.

System actionThe transaction routing request is terminated and amessage is sent to the terminal owning region (TOR) toindicate that the transaction routing request has failed.The CICS security manager issues a DFHSNnnnnmessage to the transient data queue, CSCS.

User responseExamine the response and reason returned in theDFHCCNV commarea DFHC32. The client and server

codepages will have already been validated so thismay be a CICS error. You may need to contact IBM forfurther assistance. See Working with IBM to solve yourproblem for guidance on how to proceed.


AXTQ

ExplanationAn exception response has been returned tothe transaction-routing transformer module fromDFHCCNV FUNCTION(CONVERT_DS3270_FOR_SBCS).The module was called for a CICS client virtualterminal which requested conversion from EBCDIC toASCII for data to be sent to the client. However theconversion failed.


User responseExamine the response and reason returned in theDFHCCNV commarea DFHC32. The client and servercodepages will have already been validated so thismay be a CICS error. You may need to contact IBM forfurther assistance. See Working with IBM to solve yourproblem for guidance on how to proceed.


AXTR

ExplanationAn exception response has been returned tothe transaction-routing transformer module fromDFHPGLE FUNCTION(LOAD_EXEC) whilst trying to loadEXEC program DFHCCNV.







User responseExamine the response and reason returned fromDFHPGLE to determine why CICS was unable to callDFHCCNV.


AXTS

ExplanationOne of the following conditions has occured.

• A transaction running in an AOR has created achannel. The transaction has terminated by issuingEXEC CICS RETURN TRANSID CHANNEL to namethe next transaction in the pseudo-conversation andpass the channel to it. However the TOR is not at ahigh enough CICS level to support channels.

• A transaction running in an AOR has created achannel. The transaction has terminated by issuingEXEC CICS RETURN TRANSID CHANNEL to namethe next transaction in the pseudo-conversation andpass the channel to it. The channel is transmitted tothe TOR and is held there until the next transactionin the pseudo-conversation starts. However, whenthe next transaction is initiated, it is found to residein an AOR that is not at a high enough CICS level tosupport channels.

System actionThe transaction routing request is terminated and amessage is sent to the terminal owning region (TOR) toindicate that the transaction routing request has failed.

User responseIf channels are passed between transactions in apseudo-conversation, you must ensure that all TOR

and AOR systems involved in passing the channel areat a high enough CICS level to support channels.


AXTU

ExplanationProgram DFHAPCR has returned an unexpectedresponse. DFHAPCR performs the following functions:-

• Extracts the contents of all containers making up achannel and transmits them to a remote system.

• Recreates the channel and containers from inbounddata received from a remote system.

DFHAPCR has either detected an error in inbounddata or has received an unexpected response whilstextracting or recreating channel data.


User responseLook for any related CICS messages and abendsto determine if there has been a prior failure inProgram Manager, which manages containers. Lookfor exception trace entries from Program Manager orDFHAPCR to determine the cause of the error.


AZxx abend codesAZAB

ExplanationDFHZARM has a SEND DATA request with a data lengthgreater than 65 528 bytes which is the maximum thatit can process.



Module:DFHZARM

AZAD



ExplanationDFHZCN1 has been started from an unexpectedsystem. The CCIN transaction can only be issued bya client.

System actionThe transaction is abnormally terminated. Exceptiontrace point AP3008 is written. Data1 holds the XMIQstart type.

User responseIssue the CCIN transaction only from a client.

Module:DFHZCN1

AZAE

ExplanationDFHZCN1 was started from a terminal facility, but notan LU6.2 session. The CCIN transaction may only beissued by a client.


User responseIssue the CCIN transaction only from a client.

Module:DFHZCN1

AZAF

ExplanationDFHZCN1 was started for transaction CCIN. Howevereither the environment is wrong or the clientarchitecture has been violated. This abend is alwaysissued in conjunction with a DFHZC32nn messagewhich explains the problem in more detail.

System actionException trace point AP30xx is written. Thetransaction is abnormally terminated.

User responseLook for a DFHZC32nn message on the console orCSNE and look for exception trace points AP30xx. Usethese to diagnose the problem.

Module:DFHZCN1

AZAG

ExplanationDFHZCT1 has been started from an unexpectedsystem. The CTIN transaction can only be issued bya client.

System actionThe transaction is abnormally terminated with a CICStransaction dump. Exception trace point AP302A iswritten. Data1 holds the XMIQ start type.

User responseIssue the CTIN transaction only from a client.

Module:DFHZCT1

AZAH

ExplanationDFHZCT1 was started from a terminal facility, but notan LU62 session. The CTIN transaction can only beissued by a client.

System actionThe transaction is abnormally terminated with a CICStransaction dump. Exception trace point AP3032 iswritten. Data1 holds the principal facility address.

User responseIssue the CTIN transaction only from a client.

Module:DFHZCT1

AZAI

ExplanationDFHZCT1 was started for transaction CTIN. Howevereither the environment is wrong or the clientarchitecture has been violated. This abend is alwaysissued in conjunction with a DFHZC32nn messagewhich explains the problem in more detail.

System actionException trace point AP30xx is written. Thetransaction is abnormally terminated.


User responseLook for a DFHZC32nn message on the console orCSNE and look for exception trace points AP30xx. Usethese to diagnose the problem.

Module:DFHZCT1

AZAJ

ExplanationDFHZCN1 was started for transaction CCIN. However,the CCIN transaction is being started on a surrogate,which means that it has been defined as a remotetransaction. CCIN must be a local transaction and berun on a CICS region which is directly connected to aclient.

System actionException trace point AP3041 is written. Thetransaction is abnormally terminated.

User responseEither use the default definitions for CCIN or ensurethat it is defined as a local transaction.

Module:DFHZCN1

AZAK

ExplanationDFHZCT1 was started for transaction CTIN. However,the CTIN transaction is being started on a surrogate,which means that it has been defined as a remotetransaction. CTIN must be a local transaction and berun on a CICS region which is directly connected to aclient.

System actionException trace point AP3039 is written. Thetransaction is abnormally terminated.

User responseEither use the default definitions for CTIN or ensurethat it is defined as a local transaction.

Module:DFHZCT1

AZCA

ExplanationAn internal logic error has been detected duringAPPC mapped processing. The conversation statemaintained by DFHZARL does not match thatmaintained jointly by DFHETL and DFHZARM.

The problem may also arise when CICS is assemblingapplication data and receives end of chain beforereceiving all of the data that is expected.



Module:DFHZARM

AZCB

ExplanationCICS has received sense code X'088901xx' duringAPPC mapped processing. This should be followed byan error data GDS (generalized data stream) variable.

CICS has attempted to receive the error data. Howeverthis attempt has failed because no data has beenreceived or because the data received is not for anCICS ISSUE ERROR of the correct length.

CICS expects the error data to indicate that the othersystem does not recognize GDS ID X'12F2' (functionmanagement data).


The erroneous GDS ID is returned to the remotesystem for further analysis there.

User responseCheck for session failure and for abend by thetransaction in the other system.


Module:DFHZARM

AZCC




ExplanationThe failing transaction has sent function managementdata to a transaction running in a system that does notprovide support for application function managementdata.


User responseCheck that the remote system can support applicationfunction management data.

Module:DFHZARM

AZCD

ExplanationA possible intersystem logic error has been detectedduring APPC mapped processing. The length ofapplication data that is to be received (as determinedfrom the LL fields and concatenation flags) does notmatch the length actually received. CICS determinesthe length of application data that is to be receivedfrom the LL fields and concatenation flags. However,CICS has not received all of the data that is expected.

This abend can be caused by a loss of data followingthe failure of a persistent sessions restart in a partnersystem. In this case, no logic error has occurredbecause any updates are backed out.


User responseIf this abend is not caused by the failure of a persistentsessions restart in a partner system, you will needfurther assistance from IBM. See Working with IBM tosolve your problem for guidance on how to proceed.

Module:DFHETL, DFHZARM

AZCE

ExplanationAn intersystem error has been detected during APPCmapped processing. The length of application datathat is to be received (as determined from the LLfields and concatenation flags) exceeds the CICS

implementation limit of 32 767, for receive andconverse commands, or 65 000 for CICS transactionrouting or function shipping requests.


User responseReduce the amount of data that the transaction in theremote system is transmitting to CICS.


AZCF

ExplanationAn internal logic error has been detected duringAPPC mapped processing. An invalid request has beenpassed to DFHZARL.



Module:DFHZARM

AZCG

ExplanationAn internal logic error has been detected during APPCmapped processing. DFHZARM expects the TCTTEpassed to have been defined as APPC, TCTEILUC(TCTELUC) set on, and TCTECVT set to TCTEMAPD (toindicate a mapped conversation).








Module:DFHZARM

AZCH

ExplanationSense code X'0889xxxx' has been receivedunexpectedly during the processing of APPC mappeddata.

This represents a violation of the APPC architecture bythe remote system.




AZCI

ExplanationThe processing of APPC mapped data requiresgeneration of an APPC attach function managementheader (FMH) with default values. In particular, thesync level requested is defaulted to 2. However, thesession that is to be used has been bound with a synclevel of 1.




• The remote system is capable of supporting a synclevel of 2.

• Exchange lognames has completed for theconnection. You can use the CEMT INQUIRECONNECTION to do this. See the CICSintercommunication for details of the exchangelognames process.

Module:DFHETL, DFHZARM, DFHZARQ

AZCJ

ExplanationAn APPC structured field with GDS ID X'12F1' (nulldata) has been sent to a remote system that doesnot support the receipt of these fields. The remotesystem has responded negatively and has terminatedthe conversation.


User responseThe problem is in the remote system. If you needfurther assistance from IBM to resolve this problem,see Working with IBM to solve your problem forguidance on how to proceed.

Module:DFHZARM

AZCK

ExplanationAn internal logic error has been detected duringerror recovery for APPC mapped processing. Theconversation was being switched to RECEIVE state byan internal CICS SEND INVITE, but the conversationhad already been FREEd by the partner.



Module:DFHZARM

AZCL

ExplanationCICS has received sense code X'088901xx' duringAPPC mapped processing. The generalized datastream (GDS) should contain a valid GDS identity in







the error data but CICS does not recognize the value.The values recognized by CICS are:

X'12F1' null dataX'12F2' function management dataX'12FF' application data.


User responseCheck for session failure and for an abend by thetransaction in the other system.

Module:DFHZARM

AZCM




Module:DFHZARM

AZCN

ExplanationThe task has been purged before a GETMAIN requestto the storage manager (SM) domain was able tocomplete successfully. The task that first detected thepurged condition provides an exception trace.





Module:DFHZARM

AZCO

ExplanationThe VTAM persistent sessions initialization transactionCGRP has been started directly from a terminal. Thisis not permitted. This transaction can only be startedinternally by CICS.


User responseNone.

Module:DFHZCGRP

AZCP

ExplanationA logic error has been detected in ZCP. An allocationrequest for a starting task cannot be satisfied.




Module:DFHZSUP DFH62XM

AZCQ

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe recovery manager (RM) domain to change therecovery status of an intercommunication session.The domain provides an exit trace, and possibly aconsole message and a system dump (depending onthe options specified in the dump table).


User responseThis failure is either the result of a task purge, orit represents a CICS logic error and you will needassistance from IBM.

See the related diagnostic material produced by therecovery manager domain.


AZCR

ExplanationA logic or protocol error has been detected duringprocessing of an APPC SYNCPOINT ROLLBACKrequest. An attempt has been made to restore theconversation state to what it was after completion ofthe last successful unit of work. This saved state doesnot match flows received from the partner.

The problem arises during rollback in one of thefollowing situations:

• The saved state is receive, and the partner sentchange direction on the last flow, indicating that thepartner expects CICS to be in send state

• The saved state is send, and the partner did notsend the change-direction indicator on the last flow,indicating that the partner expects CICS to be inreceive state.

System actionThe task is abnormally terminated with a CICStransaction dump. Other processing continues.

User responseThe problem can arise because of a failure in CICS, ora failure in the partner. To determine which is failing,analyze the flows at the last successful syncpoint.Try to determine the states the two LUs were in atthis point. Look at the last syncpoint flow into CICSfrom the partner, before the abend. From this flow,calculate whether the change-direction indicator onthe SPCMOD modifier byte is on. ( See the SystemsNetwork Architecture Formats (GA27-3136) manualfor further information on the SPCMOD modifier byte.)The indicator must only be set when the saved CICSconversation state is send. If the last CICS state wassend, and the indicator is on, CICS is at fault. Similarly,if the last CICS state was receive, and the indicator isoff, CICS is at fault.

If the last CICS state was send and the indicator is off,or the last CICS state was receive, and the indicatoris on, CICS has received a change-direction indicatorwhen it was not expecting one. In this case, examinethe partner for a logic error.

Module:DFHZARL

AZCT

ExplanationA terminal read-time-out condition has been detected.The transaction has been waiting for a terminal inputmessage for an interval longer than specified in theRTIMOUT value for that transaction.

Coding RTIMOUT in the PROFILE entry causes the taskto be abnormally terminated if the terminal does notsend input within the specified time.

System actionThe transaction is abnormally terminated. A dumpis not provided unless the dump table entry fortransaction dump code AZCT indicates that one shouldbe taken.

User responseIf a HANDLE ABEND command has been issued for thistask, the read that was timed-out is still outstanding.In order to cancel this read, issue an ABEND commandat the end of the user exit routine so that CICS canclean up the terminal's TCTTE. No further terminalcontrol commands should be issued.



https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=GA27-3136-20

https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=GA27-3136-20

Module:DFHZARQ

AZCU

ExplanationThe COVR transaction has been started directlyfrom a terminal, or by a START command. This isnot permitted. This transaction can only be startedinternally by CICS.

System actionThe transaction is abnormally terminated. Notransaction dump is taken.

User responseNone.

Module:DFHZCOVR

AZCV

ExplanationA logic error has been detected in the COVRtransaction while trying to connect to VTAM.



Module:DFHZCOVR

AZCW

ExplanationAn attempt has been made to run the CICS internaltask CSTP as a user transaction.


User responseInvestigate why the attempt was made to run CSTP asa user transaction.

Module:DFHZCSTP

AZI1

ExplanationAn IRC data transmission request has been issued,but cannot be completed because the transmissionprotocol has been violated.

If the session is not used for distributed transactionprocessing, that is if it is used for function shipping ortransaction routing, then the problem is caused by aCICS logic error.

If the session is used for distributed transactionprocessing, then the following are possible causes ofthe abend:

• An invalid terminal control command, such as ISSUESIGNAL, was issued

• A send request was issued but the session was notin send state, or a read request was issued but thesession was not in receive state.


User responseDetermine the cause of the abend and if appropriate,correct the application. For further guidance, refer tothe section on the EXEC Interface block (EIB) in theCICS intercommunication. The EIB describes the stateof the session after a request has been issued.

Module:DFHZARQ

AZI2

ExplanationAn IRC data transmission request has been issued butcannot be completed. Possible causes of the probleminclude:

• The transaction running in the connected system hasbeen purged, or

• The transaction running in the connected system hasbeen timed out, or

• The abending transaction has attempted to SENDwhile in RECEIVE state, or

• The abending transaction has attempted to RECEIVEwhile in SEND state.




If the abend was caused by DFHIRP rejecting thetransmission request, the dump will contain DFHIRP'sreturn code in the field TCTEIRET for the TCTTErepresenting the failed IRC session. The address ofthis TCTTE is in field B of the trace entry representingthe DFHTC data transmission request.

The meanings of the DFHIRP return codes are given inthe copybook, DFHIRSDS.


User responseIf the cause of the error was a purge or a time-out, nofurther action is required.

If the error was caused by a condition such as anattempted SEND while in RECEIVE state or vice versa,analyze the dump and correct the protocol violation.

Module:DFHZARQ

AZI3

ExplanationA terminal control request issued by an applicationto a remotely-owned terminal failed because theconversation with the other system failed.



Module:DFHZARQ

AZI4

ExplanationAn IRC data transmission request has been issued, butcannot be completed because the other system hasbecome unavailable for interregion communication.


User responseRerun the transaction when IRC is available.

Module:DFHZARQ

AZI5

ExplanationAn IRC data transmission request has been issued, butthe data sent by the connected system in response tothe request violated IRC protocols.



Module:DFHZARQ

AZI6

ExplanationThe transaction was connected to another transactionin another CICS system via an IRC link. This othertransaction has abnormally terminated.


User responseCorrect the cause of the abend in the connectedtransaction.

Module:DFHZARQ

AZI7

ExplanationThe transaction was processing an MRO request whichinvolved waiting for a response from a connectedsubsystem. The 'wait' request was rejected by theCICS dispatcher.




System actionThe transaction is abnormally terminated with a dump.


Module:DFHZIS2

AZI8

ExplanationThe error log data received with an ISSUE-ABEND flowon an IRC connection was not in the correct format.



Module:DFHZIS1

AZI9

ExplanationThe transaction was processing an MRO request whichinvolved waiting for a response from a connectedsubsystem. During the wait, the failing transaction waspurged. The purge can only have been the result ofoperator action, such as a CEMT SET TASK PURGE.

System actionThe task is abnormally terminated with a dump.

User responseInvestigate the reason the transaction was purged.

Module:DFHZIS2

AZIA

ExplanationThe transaction attempted to acquire or free storageduring MRO processing. The response from the CICS

storage manager (SM) domain indicated that therequest was invalid.



Module:DFHZIS2

AZIB

ExplanationThe transaction was purged whilst waiting for storageto receive MRO data from a connected subsystem. Thepurge may have been the result of operator action,such as CEMT SET TASK PURGE, or as the result ofthe waiting time exceeding the DTIMOUT value for thetransaction.


User responseIf the condition is caused by time-out, examine theDTIMOUT value for the failing transaction and increaseit if it is too low.

Module:DFHZIS2

AZIC

ExplanationAn INVALID, DISASTER, or EXCEPTION condition hasoccurred on a call to the storage manager domain(DFHSMGFM) to FREEMAIN a CRB control block.

The domain that detected the original error providesan exception trace, a console message, and possibly asystem dump.






User responsePlease see the related message from the domain thatdetected the original error.

Module:DFHZIS2

AZID

ExplanationA PURGED condition has occurred on a call to thestorage manager domain (DFHSMGFM) to FREEMAINa CRB control block.

The domain that detected the original error providesan exception trace.





Module:DFHZIS2

AZIE

ExplanationAn interregion communication (IRC) ISSUE-ERROR orISSUE-ABEND flow has been received in violation ofIRC protocols. This can be caused by:

• A CICS logic error. IRC protocols are not available toMRO distributed transaction processing applications.They are for CICS internal use only.

• A transaction abend on a connected system. Thisresults in an FMH 7 flow over an LU6.2 connectionand causes this abend to be issued.


User responseCheck whether a mixture of mapped and unmappedconversations are being used as this can cause thisabend. Check for any other reasons for transactions tobe abending on the attached system.

If a CICS logic error is involved, you will need furtherassistance from IBM. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHZARQ

AZIF

ExplanationAn error (INVALID, DISASTER or unexpectedEXCEPTION response) has occurred on a call tothe recovery manager (RM) domain to change therecovery status of an intercommunication session.The domain provides an exit trace, and possibly aconsole message and a system dump (depending onthe options specified in the dump table).

This is either the result of a task purge, a CICS logicerror, or of the inappropriate use of the indoubt testtransaction, CIND. CIND should be activated only onthe CICS system where the syncpoint processing wasinitiated. In particular, CIND should not be used on anyof the CICS mirror transactions.


User responseDetermine whether CIND has been activated fora transaction that did not initiate the syncpointprocessing. If CIND is not being used see the relateddiagnostic material produced by the recovery managerdomain and determine the reason for the failure.

In the case of a CICS logic error, you need furtherassistance from IBM. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHZARQ

AZIG






ExplanationAn MRO session read-time-out condition has beendetected. The transaction has been waiting for an MROsession for an interval longer than specified in theRTIMOUT value for that transaction.

Coding RTIMOUT in the PROFILE entry causes the taskto be abnormally terminated if the session does notrespond within the specified time.

System actionThe transaction is abnormally terminated. A dumpis not provided unless the dump table entry fortransaction dump code AZIG indicates that one shouldbe taken.

User responseIf a HANDLE ABEND command has been issued for thistask, the read that was timed-out is still outstanding.In order to cancel this read, issue an ABEND commandat the end of the user exit routine so that CICS canclean up the terminal's TCTTE. No further terminalcontrol commands should be issued.

Module:DFHZIS2

AZR2

ExplanationModule DFHZARRA is unable to acquire main memoryfor a new application buffer because the storagemanager GETMAIN failed.


User responseUse the trace to identify the failing return from thestorage manager and analyze the reason for failure.

Module:DFHZARRA

AZR3

ExplanationDuring a GETMAIN request, the storage domaindetected that the task has been purged.


User responseUse the trace to investigate why the task was purged.Check if the main terminal operator was responsible.

Module:DFHZARRA

AZR4

ExplanationAn unexpected response has been received from adispatcher domain call.



Module:DFHZARER

AZR5

ExplanationAn unexpected response has been received from adispatcher domain call.



Module:DFHZARR1

AZR6

ExplanationAn exception condition was raised as the result ofa request from the APPC communications routine




DFHZARL to the CICS recovery manager domain. Thisis either caused by a CICS logic error or by theinappropriate use of the indoubt test transaction,CIND. CIND should be activated only on the CICSsystem where the syncpoint processing was initiated.In particular, CIND should not be used on any of theCICS mirror transactions.


User responseDetermine whether CIND has been activated fora transaction that did not initiate the syncpointprocessing. If CIND is not being used, you will needfurther assistance from IBM to resolve the problem.See Working with IBM to solve your problem forguidance on how to proceed.

Module:DFHZARER

AZRA

ExplanationDFHZARRC detected that the address of an FMH in theAPPC was not in the receive buffer. The cause couldeither be a storage overwrite or a CICS internal logicerror.


User responseIf this problem is reproducible, a level 1 and 2 trace ofthe TC component would aid problem determination.Check the TCTTE in the transaction dump for printablecharacters or other signs of a storage violation error.

Module:DFHZARRC

AZRB

ExplanationModule DFHZARR0 was called with an invalid firstparameter. The first parameter should be the code ofthe function to be performed. This is a CICS logic error.


User responseIf this problem is reproducible, then a level 1 and2 trace of the TC component would aid problemdetermination. If you need further assistance fromIBM to resolve this problem, see Working with IBM tosolve your problem for guidance on how to proceed.

Module:DFHZARR0

AZRD

ExplanationThe logical and physical APPC receive buffers havebecome out of step. This problem is caused either by astorage overwrite or by a CICS internal logic error.


User responseIf this problem is reproducible, then a level 1 and2 trace of the TC component would aid problemdetermination. Check the TCTTE in the transactiondump for printable characters or other signs of astorage violation error.

Module:DFHZARR0

AZRE

ExplanationThe logical APPC receive buffer (addressed byTCTERBLA) starts before or after the physical receivebuffer (addressed by TCTERBLA). This is not valid asthe logical receive buffer is the part of the physicalreceive buffer that is yet to be processed. Thisproblem could be caused either by a storage overwriteor by a CICS internal logic error.






User responseIf this problem is reproducible then a level 1 and2 trace of the TC component would aid problemdetermination. Check the TCTTE in the transactiondump for printable characters or other signs of astorage violation error.

Module:DFHZARR0

AZRF

ExplanationThe DFHZUSR state machine has returned an invalidstate error at a point where it should not be possible.This is a CICS internal logic error.



Module:DFHZARRF

AZRG

ExplanationThe DFHZUSR state machine has returned an invalidstate error at a point where it should not be possible.This is a CICS internal logic error.



Module:DFHZARR

AZRH

ExplanationThe DFHZARR state variable RECEIVE_TYPE, used tocontrol receive processing, has been set to an invalidvalue. The only other module that has access to thisvariable is DFHZARRF. This is a CICS internal logicerror.



Module:DFHZARR

AZRI

ExplanationOne of the parameters passed to DFHZARR1. wasinvalid. This is a CICS internal logic error.



Module:DFHZARR1

AZRJ

ExplanationThe length of a record that DFHZARR0 has beenrequested to remove from the APPC receive buffer,is longer than the buffer itself. This problem couldbe caused either by a storage overwrite or by a CICSinternal logic error.












Module:DFHZARR0

AZRK

ExplanationThe DFHLUC parameter list passed back fromDFHZERH to DFHZARRF contained an invalidcombination of LUCCIERR, LUCCIFRE, and LUCCIRBKfields. This is a CICS internal logic error.


User responseIf this problem is reproducible, a level 1 and 2 trace ofthe TC component would aid problem determination.If you need further assistance from IBM to resolve thisproblem, see Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHZARRF

AZRL

ExplanationModule DFHZARRF was called with an invalid firstparameter. The first parameter should be the code ofthe function to be performed. This is a CICS internallogic error.


User responseIf this problem is reproducible, a level 1 and 2 trace ofthe TC component would aid problem determination.If you need further assistance from IBM to resolve this

problem, see Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHZARRF

AZRM

ExplanationModule DFHZARR called one of its own internalroutines at the wrong time. This is a CICS internal logicerror.



Module:DFHZARR

AZRN

ExplanationThe DFHLUC parameter list passed back fromDFHZERH to DFHZARRF did not have LUCCIERR seton. This is a CICS internal logic error.



Module:DFHZARRF

AZRO

ExplanationModule DFHZARER was called with an invalid firstparameter. The first parameter should be the code of






the function to be performed. This is a CICS internallogic error.



Module:DFHZARER

AZRP

ExplanationModule DFHZARER detected an invalid response fromDFHZNAC. This is a CICS internal logic error.



Module:DFHZARER

AZRQ

ExplanationModule DFHZARRA was called with an invalidparameter. This is a CICS internal logic error.


User responseIf this problem is reproducible, a level 1 and 2 trace ofthe TC component would aid problem determination.If you need further assistance from IBM to resolve this

problem, see Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHZARRA

AZRR

ExplanationModule DFHZARRA detected that the applicationbuffer chained off of a TCTTE at offset TCTERCSA hada corrupted header. This is caused either by a CICSlogic error or by a storage overwrite. The exceptiontrace point that accompanies this abend code givesthe TCTTE address.



Module:DFHZARRA

AZRS

ExplanationModule DFHZARRA is unable to acquire main memoryfor a new application buffer into which it is supposedto copy some data. This is because the DFHLUCreceive request is SUBTYPE=LLID, SET=YES andDFHZARRA does not know the length to acquire onthe GETMAIN. DFHZARRA requires the length of therecord currently being received, but it has been setto 0 in error. This is a CICS logic error. The exceptiontrace point that accompanies this abend code givesthe TCTTE address.








Module:DFHZARRA

AZRT

ExplanationModule DFHZARRA has detected that the applicationbuffer, into which it is supposed to copy some data, isinvalid. This is either because the address of the bufferis zero or because its length is less than that of thedata to be copied into it. This is a CICS logic error.The exception trace point that accompanies this abendcode gives the buffer address and length plus the dataaddress and length.



Module:DFHZARRA

AZRU

ExplanationModule DFHZARRF detected an unexpected responsefrom DFHZARR0. This is a CICS logic error. Theexception trace point that accompanies this abendcode gives the invalid response code.



Module:DFHZARRF

AZRV

ExplanationModule DFHZARR1 detected an unexpected responsefrom DFHZARR0. This is a CICS logic error. Theexception trace point that accompanies this abendcode gives the invalid response code.



Module:One of the parameters passed to DFHZARR1

AZRW

ExplanationModule DFHZARRA detected a negative record lengthin the TCTTE (field TCTELLC). This is caused eitherby a CICS logic error or by a storage overwrite. Theexception trace point that accompanies this abendcode gives the TCTTE address and the value ofTCTELLC.



Module:DFHZARRA

AZRY

ExplanationModule DFHZARR detected an unexpected responsefrom DFHZARRC. This is a CICS logic error. Theexception trace point that accompanies this abendcode gives the invalid response code.








Module:DFHZARR

AZRZ

ExplanationModule DFHZARR detected an unexpected responsefrom an internal subroutine. This is a CICS logic error.The exception trace point that accompanies this abendcode gives the invalid response code.



Module:DFHZARR

AZS0

ExplanationAn invalid request was passed via the DFHZSTAMmacro to the processing DFHZSTAP program. This isa CICS internal logic error.



Module:

DFHZSTAP

AZS1

ExplanationNo TCTTE pointer was passed via the DFHZSTAMmacro to the processing DFHZ program. This is a CICSinternal logic error.



Module:DFHZSTAP

AZS2

ExplanationThe TCTTE passed via the DFHZSTAM macro to theprocessing DFHZSTAP program does not relate to anMRO or an APPC Conversation. This is a CICS internallogic error.



Module:DFHZSTAP

AZS3

ExplanationThe TCTTE passed via the DFHZSTAM macro tothe processing DFHZSTAP program for an APPCConversation, but the LUC Extension Control Block wasnot located. This is a CICS internal logic error.









Module:DFHZSTAP

AZS4

ExplanationWhile processing a DFHZSTAM request in DFHZSTAP,the DFHZUSRM LUC State Machine was found to havean invalid setting. This is a CICS internal logic error.



Module:DFHZSTAP

AZS5

ExplanationWhilst processing a DFHZSTAM request in DFHZSTAP,the Internal State number was found to have an invalidsetting. This is a CICS internal logic error.



Module:DFHZSTAP

AZS6

ExplanationWhilst processing a DFHZSTAM request in DFHZSTAP,the Internal State number was found to have an invalidsetting. This is a CICS internal logic error.



Module:DFHZSTAP

AZT1

ExplanationThe task has been attached improperly in theapplication-owning region when transaction routing.


User responseThe conversation with the routing system should be anMRO session or an LU type 6.2 conversation. Ensurethat the transaction is being attached by the CICSrelay program in the connected system and not by auser program.

If the transaction is being attached by the CICS relayprogram in the connected system, you need furtherassistance to resolve this problem. See Working withIBM to solve your problem for guidance on how toproceed.

Module:DFHZTSP

AZT3

ExplanationThe task is being routed back to the region from whereit came.


User responseCorrect the transaction definition.

Module:DFHZTSP, DFHAPRT, DFHRTE








AZT6

ExplanationThe task in the application-owning region has receiveda ROLLBACK request from the terminal-owning region,but the conversation is continuing. The terminal-owning region has violated the transaction routingprotocol.



Module:DFHZTSP

AZT7

ExplanationA session terminal control table (TCT) entry for aremotely owned APPC terminal or connection couldnot be added to the TCT.



Module:DFHZTSP

AZT8

ExplanationA session terminal control table (TCT) entry for aremotely owned APPC terminal or connection couldnot be deleted from the TCT.



Module:DFHZTSP

AZT9

ExplanationA session terminal control table (TCT) entry for aremotely owned APPC terminal or connection couldnot be deleted from the TCT because it is locked byanother task.


User responseThe other task may be transitory in nature, and if so,another attempt will succeed.

Module:DFHZTSP

AZTA

ExplanationThe task does not own a terminal as its principalfacility.



Module:DFHZTSP, DFHAPRR

AZTB

ExplanationAn attempt to install or delete a remote terminal inthis CICS system has failed. This may be becauseCATA was trying to install a local terminal at the sametime as CITS was installing a remote terminal with thesame termid. In this situation CICS gives priority to






the locally installed terminal (CATA). This abend canoccur if the CITS/CDTS/CMTS/CFTS transactions takean excessively long time to execute, for example dueto the CICS system having reached MAXTASK or theshort on storage (SOS) condition. This abend can alsooccur if the CITS/CDTS/CMTS/CFTS transactions arenot available (that is , if the transactions have not beeninstalled).

System actionThe task which is being initialized for transactionrouting is abnormally terminated with a CICStransaction dump.

User responseIf there was an abend AZI6/AZTS abend in theTOR then retry the request after the locally installedterminal with the same TERMID has logged off. If theCICS system reached MAXTASK or short on storage(SOS) conditions, retry the request when the CICSsystem is processing less work. Alternatively it may benecessary to update the MAXTASK value or the storageallocation for the CICS system. Otherwise, verify thatthe listed transactions exist and have been installed.If the failure persists then you need further assistanceto resolve this problem. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHZTSP, DFHAPRA

AZTC

ExplanationAn attempt to install or delete a remote terminal in thissystem has failed. This is because a short-on-storage(SOS) condition has caused the failure of a GETMAINfor the attach of CITS, CDTS, or CFTS.

This abend can also occur duringshutdown if the transaction definition specifiesSHUTDOWN(DISABLED).


User responseInvestigate the reason for the SOS condition. See theTroubleshooting and support for guidance on dealingwith the SOS condition.

Retry the transaction later.

Module:

DFHZTSP, DFHAPRA

AZTE

ExplanationAn attempt to use EDF and to route a transaction to aremote region has failed.

This is because the CEDF transaction was used to startan EDF session and then there was an attempt to routea transaction to a remote region.

Communication between the local region and theremote region uses an IPIC connection.

However the remote region is an earlier version ofCICS which does not support use of EDF with an IPICconnection.

System actionThe task is abnormally ended with a CICS transactiondump.

User responseYou can do one of the following:

• Enable CEDX for the transaction on the remoteregion.

• Release the IPIC connection and run the transactionwith EDF enabled using another connection type.

Module:DFHAPRT

AZTF

ExplanationDFHZTSP tried to GETMAIN or FREEMAIN a TCTTEwhose length (TCTTETEL) is longer than the largestTCTTE SUBPOOL and is therefore invalid. This impliesa storage violation or a CICS internal logic error.


User responseUse the transaction dump to identify the TCTTE inerror. First, check whether this is a storage overwrite.If so, check in your statistics to see if you are gettinga number of storage violations caused by the sametransaction. If this is the case, then a user-suppliedapplication is probably causing the problem.





If it is not a storage violation problem, or if there isa random storage violation, there might be an errorin CICS. In this case, you need further assistance toresolve the problem. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHZTSP

AZTG

ExplanationAn attempt has been made to attach a task ona remotely-owned terminal without an intersystemTCTTE as its principal facility.



Module:DFHZTSP

AZTH

ExplanationAn error response was received from the remoteterminal control macro.



Module:DFHZTSP

AZTI

ExplanationAn attempt has been made to attach a task ona remotely-owned terminal, but the terminal is notdefined in this system as a remotely-owned terminal.

This may occur after an AZVK abend when CICSattempts to delete the surrogate TCTTE, but there isstill a transaction running against it.

Alternatively, another task holds a lock on thisterminal.


User responseCheck the terminal control table definitions in thesystems involved. If the definitions are correct, checkthat no other tasks have locks held on the terminal(CECI, for example).

Check to see if an AZVK abend occurred earlier for thisterminal and determine if the link session timing outwas the original cause. All should be well once the longrunning transaction finishes.


AZTL

ExplanationAn attempt has been made to attach a task to aremotely-owned terminal that cannot be used to runthis transaction.


User responseInform the system programmer. Check the terminalresource definitions in the systems involved.


AZTM

ExplanationThe data received from the remote system does notcontain an FMH (function management header).








Module:DFHZTSP

AZTN

ExplanationConversation with a remote system has beenunexpectedly terminated.



Module:DFHZTSP

AZTO

ExplanationThe TCTTE ownership chain is in error.



Module:DFHZTSP

AZTP

ExplanationA BMS TYPE=STORE request issued on behalf of aremote transaction failed.

System actionThe task abnormally terminates with a CICStransaction dump.

User responseInform the system programmer. Check that therequired BMS support has been generated.


AZTQ

ExplanationInvalid BMS data received from remote system.




AZTR

ExplanationA BMS TYPE=PAGEOUT request issued on behalf of aremote system failed.


User responseEnsure that the required BMS support has beengenerated.


AZTS

ExplanationThe conversation with the remote system failed.







User responseInvestigate why the conversations with the remotesystem failed. The transaction on the remote systemhas probably been abnormally terminated or thesession has failed.

If message 'DFHZC4930 Session unbound followingread timeout.' occurred just before the AZTS then theAZTS is caused by a timeout occurring on an APPCsession when CICS attempted to converse with theremote system.

Module:DFHZTSP, DFHAPRR, DFHAPRA

AZTT

ExplanationAn attempt was made to attach a task on a remotesystem, but the connection with the remote system isnot an APPC or MRO connection.


User responseRedefine the connection as APPC or MRO, or avoidusing transaction routing on this connection.

Module:DFHZTSP

AZTU

ExplanationThe task does not own the link TCTTE after a syncpoint has been taken.



Module:DFHZTSP

AZTV

ExplanationAn invalid function management header (FMH) hasbeen received from the remote system.



Module:DFHZTSP

AZTW

ExplanationAn attempt was made to attach a task on a remotely-owned terminal that was already running a task.

This may be caused by a read time out occurring in theterminal owning region for the link session being usedby this transaction. The read timeout is specified inprofile DFHCICSS. Although the session has timed outthe transaction may still be running and the surrogateTCTTE is unable to accept any more transactions untilthe first one has finished.


User responseCheck the terminal control table definitions in thesystems involved.

Check to see if a read timeout abend occurred onthe TOR for the same terminal to determine if this isthe cause. Wait until the transaction terminates beforeretrying any further transactions on this terminal.


AZTY

ExplanationA session TCT entry for a remotely owned APPCterminal or connection could not be created becauseto do so would exceed the maximum number of APPCsessions permitted.




The maximum number of sessions depends onwhether the PTF shipped for APAR PQ27823 isinstalled. The basic limit is 46656 and the names arein the range -AAA to -999. The APAR doubles this limitto 93312 giving an additional range of AAA- to 999-.


User responseInform the system programmer. Either wait for thesystem to become less busy, or delete some APPCsessions.

The system programmer should consider increasingthe number of CICS TORs.

Module:DFHZTSP

AZTZ

ExplanationThe CICS relay program DFHCRT has been attached inan unsupported manner.


User responseThe relay transaction executes with an MRO sessionor an LU type 6.2 conversation as its principal facility.Ensure that the transaction is being attached by APPCterminal sharing logic and not directly by a usertransaction.

If the transaction is being attached by APPC terminalsharing logic, you need further assistance to resolvethis problem. See Working with IBM to solve yourproblem for guidance on how to proceed.

Module:DFHZTSP

AZVA

ExplanationDFHZTSP has timed out waiting for service transactionCITS to complete during the creation of a remoteterminal while attaching a task in the application-owning region.

The probable cause of this is that the application-owning region is very busy, so the CITS transactionhas been waiting to be dispatched for longer than thetimeout value allowed by DFHZTSP. Lack of storage onthe target system is one possible reason why CITS hasnot been dispatched, or has been dispatched but hasnot completed.


User responseRetry the transaction when the system becomes lessbusy. For more information on improving transactionthroughput on the target system, see the Improvingperformance.

Module:DFHZATS

AZVB

ExplanationDFHZCQ has failed to create the remote terminaldefinition. A previous message or messages shouldindicate the reason for the failure.


User responseSee the previous message or messages for furtherguidance.

Module:DFHZATS

AZVC

ExplanationAn unexpected error has occurred in DFHZATS. This isprobably caused by DFHZATS being unable to addressthe CSA, EIB or the TCA. It can also occur if DFHZATSis called with an EXEC CICS START command fortransactions CITS, CFTS, CMTS or CDTS. These areinternal CICS transactions and should not be called inthis way.





http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/tuning/improving_performance.html

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/tuning/improving_performance.html


Module:DFHZATS

AZVD

ExplanationAn unexpected error has occurred in the installprocedure of DFHZATS.


User responseThis is a CICS logic error. If you need furtherassistance from IBM to resolve this problem, seeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHZATS

AZVE

ExplanationDFHZATS is trying to install a remote terminal with thesame terminal id as an existing TCT entry.


User responseChange the terminal names to ensure that a duplicatedoes not occur in the same system.

Module:DFHZATS

AZVF

ExplanationOne of the remote install or delete transactions ofDFHZATS (CITS, CFTS, CMTS or CDTS) has beenstarted directly from a terminal. This is not permitted.These transactions can only be started internally byCICS.


User responseNone.

Module:DFHZATS

AZVG

ExplanationAn error has occurred in the remote delete routines.



Module:DFHZATS

AZVH

ExplanationAn error has occurred in the remote delete routineduring the mass deletion of remote terminals.



Module:DFHZATS

AZVI

ExplanationAn error has occurred in the remote delete routinewhile an attempt was being made to delete a singleremote terminal.







User responseCheck the CADL transient data queue for anyassociated messages indicating the reason for theerror. If you cannot resolve the problem, you will needassistance from IBM. See Working with IBM to solveyour problem for guidance on how to proceed.

Module:DFHZATS

AZVJ

ExplanationAn error has occurred during the mass deletion ofremote terminals. This is caused by a CICS logic error.



Module:DFHZATS

AZVK

ExplanationAn unexpected return code has been received from theremote delete routine during the deletion of a singleremote terminal.

This may occur after an AZTW abend when CICSattempts to delete the surrogate TCTTE, but there isstill a transaction running against it. It may also occurwithout an AZTW if the link session timed out leavingthe transaction in the AOR still running but followedby a logoff from the terminal which initiated the longrunning transaction.


User responseLook for an accompanying DFHZC6911 messageindicating the reason for the delete failure, and takeappropriate action.

Check to see if the link session for this terminal timedout and whether the terminal then issued anothertransaction or logged off. All should be well once thelong running transaction finishes.

Module:DFHZATS

AZVL

ExplanationAn error has occurred during the mass flagging ofremote terminals for deletion.



Module:DFHZATS

AZVM

ExplanationAn error has occurred in DFHZATMF. This is probablycaused by DFHZATMF being unable to address theCSA, EIB, or the TCA.



Module:DFHZATMF

AZVN







ExplanationThe remote delete flag transaction of DFHZATMF(CRMF) has been started directly from a terminal. Thisis not permitted. This transaction can only be startedinternally by CICS.


User responseNone.

Module:DFHZATMF

AZVO

ExplanationThe remote delete transaction of DFHZATMD (CRMD)has been started directly from a terminal. This isnot permitted. This transaction can only be startedinternally by CICS.


User responseNone.

Module:DFHZATMD

AZVP

ExplanationAn error has occurred in DFHZATMD. This is probablycaused by DFHZATMD being unable to address theCSA, EIB, or the TCA.



Module:DFHZATMD

AZVQ

ExplanationA request to install a shipped terminal definition hasbeen rejected by the autoinstall user program.


User responseRetry the transaction when the system is less busy.

Module:DFHZATS

AZVR

ExplanationAn attempt to install a shipped terminal definition hasfailed because the autoinstall user program has issuedan unexpected return code.


User responseExamine the autoinstall user program to determinewhy this return code was issued.

Module:DFHZATS

AZVS

ExplanationAn attempt to install a shipped terminal definition hasfailed because an error has occurred in the autoinstalluser program.


User responseExamine the autoinstall user program to determine thereason for the failure.

Module:DFHZATS



AZVU

ExplanationDFHZATS was attempting to autoinstall a shippedterminal, a virtual terminal or a shipped connectionand the autoinstall URM was called. However theautoinstall failed for one of the following reasons:

• The name returned by the URM inSELECTED_SHIPPED_TERMID started with one ofthese characters:

<>-

• The value in the SIT VTPREFIX parameter containedimbedded blanks or a character that is not allowedfor terminal names.



Module:DFHZATS

AZXA

ExplanationAn unexpected error, with reason code 5, has beendetected in the catchup program, DFHZXCU. See thedescription of message DFHXG6492 for further details.

System actionConsole message DFHXG6492 is issued, and CICScontinues after abending the transaction.

User responseRefer to message DFHXG6492.

Module:DFHZXCU

AZXB

ExplanationAn unexpected error, with reason code 4, has beendetected in the catchup program, DFHZXCU. See thedescription of message DFHXG6492 for further details.

System actionConsole message DFHXG6492 is issued, and CICScontinues after abending the transaction.

User responseRefer to message DFHXG6492.

Module:DFHZXCU



Chapter 2. System abend and dump codes

Abend and dump codes are used by the following system components and products:

• The CICS system• IMS• The CICS translator• The CICS system dump program• The CICS utility program, DFHCSDUP• The external CICS interface• The CICS JVM interface• Language Environment®

CICS system dump codesTo help proceed with problem diagnosis, CICS references a system dump code that corresponds to theevent that requested a CICS system dump. In most cases, system dump codes correspond to a DFHmessage with the DFH prefix removed.

For example, system dump code DM0001 corresponds to message DFHDM0001 with the DFH tagremoved. For further information, look up the relevant message where appropriate.

However, there are some exceptions to this format, as shown in the following list.System dump code

Corresponding message or exception conditionABNDU603

This system dump code refers to a USER abend code and is associated with message DFHSR0603.ABNDU605

This system dump code refers to a USER abend code and is associated with message DFHSR0605.APTRAPPC

This system dump code is associated with message DFHTR1001.APTRAPUS

This system dump code is associated with message DFHTR1000.APUSER

This system dump code is issued through the use of the CEBT transaction when performing aPERFORM SNAP command.

APXRFTOThis system dump code has no DFH message associated with it. An error in the currently active CICSsystem has occurred. An alternate CICS system is now taking control and is requesting that the activeCICS system produces a dump of itself.

CCVNOSPThis dump along with the DFHCC0203 message is provided for diagnostic purposes when a "nospace" response is received from VSAM while attempting to write a catalog record.

MT0001This system dump code has no DFH message associated with it. It indicates that a dump wasrequested by a user of CEMT, issuing either a PERFORM SNAP or a PERFORM DUMP.

For more information about using dumps in problem diagnosis, see Using dumps in problemdetermination.


http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/troubleshooting/cics/dfhs148.html

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/troubleshooting/cics/dfhs148.html

DHxx (IMS) abend codesIf the IMS high-level programming interface (HLPI) has found a condition caused by a programming error,or if DL/I has returned a status code to HLPI that indicates an error, IMS returns a status code xx to CICSTransaction Server for z/OS. Some more common abend codes are listed here. For a full list of xx statuscodes that can make up a DHxx abend, see DL/I status codes in IMS product documentation.

DHTA

ExplanationA task has issued a program specification block (PSB)schedule request but the PSB could not be found.

See the description of the DL/I status code TA in theIMS messages and codes manual for guidance.

System action:

User response:

Module:

DHTC

ExplanationA task has issued a program specification block(PSB) schedule request but the PSB has already beenscheduled.

See the description of the DL/I status code TC in theIMS messages and codes manual for guidance.

System action:

User response:

Module:

DHTE

ExplanationA task has issued a program specification block(PSB) schedule request but a PSB initializaton erroroccurred.

See the description of the DL/I status code TE in theIMS messages and codes manual for guidance.

System action:

User response:

Module:

DHTG

ExplanationA task has issued a terminate request but the requestfailed because the program specification block (PSB) isnot scheduled.

See the description of the DL/I status code TG in theIMS messages and codes manual for guidance.

System action:

User response:

Module:

DHTH

ExplanationA task has issued a DL/I request but the request failedbecause the program specification block (PSB) is notscheduled.

See the description of the DL/I status code TH in theIMS messages and codes manual for guidance.

System action:

User response:

Module:

DHTJ

ExplanationA task has issued a program specification block (PSB)schedule request but the request failed because CICSis not connected to DBCTL.

See the description of the DL/I status code TJ in theIMS messages and codes manual for guidance.

System action:

User response:

Module:

01xx (translator) abend codes0100 Explanation

The listing data set has not opened successfully.


https://www.ibm.com/support/knowledgecenter/SSEPH2_14.1.0/com.ibm.ims14.doc.msgs/compcodes/ims_dlistatuscodes.htm

https://www.ibm.com/support/knowledgecenter/en/SSEPH2_14.1.0/com.ibm.ims14.doc.msgs/common/mc.htm






System actionThe CICS command level translator terminatesabnormally. A system dump is produced if aSYSABEND or SYSUDUMP DD statement is provided.

User responseEnsure correct JCL or determine what is causing theopen error.

Module:DFHEAP (for assembler language), DFHECP (forCOBOL), DFHEDP (for C), DFHEPP (for PL/I)

0101

ExplanationThe translator encountered a program check fromwhich it could not recover.

System actionThe CICS command-level translator terminatesabnormally. A system dump is produced if aSYSABEND or SYSUDUMP DD statement is provided.

User response:If you need further assistance from IBM to resolve thisproblem, see Working with IBM to solve your problemfor guidance on how to proceed.

Module:DFHEAP (for assembler language), DFHECP (forCOBOL), DFHEDP (for C), DFHEPP (for PL/I)

02xx (DFHPD730) abend codes0211

ExplanationA program check has occurred while the system dumpformatting program was handling an earlier programcheck.

System actionThe system dump formatting program terminatesabnormally. A system dump is produced if aSYSABEND or SYSUDUMP DD statement is provided.

User response:The program check preceding the abend isaccompanied by message DFHPD0123. See thedescription of this message for more guidance.

Module:DFHPD0680

0212

ExplanationA sixth program check has occurred during executionof the system dump formatting program.

System actionThe system dump formatting program terminatesabnormally. A system dump is produced if aSYSABEND or SYSUDUMP DD statement is provided.

User responseThis abend is preceded by five DFHPD0123 messages,one for each of the five earlier program checks. Seethe description of this message for more guidance.

Module:DFHPD0680

03xx (DFHCSDUP) abend codes0300

ExplanationThe SYSIN data set has not opened successfully.

System actionThe CSD batch update utility terminates abnormally. Ifa SYSABEND or SYSDUMP DD statement is provided, asystem dump is produced.

User responseEnsure that the JCL is correct and that the SYSIN dataset exists in sequential form. If necessary, examine theSYSIN DD statement to determine the cause of theerror.

Module:DFHCSDUP

0301

Chapter 2. System abend and dump codes 313


ExplanationThe RECFM parameter specified in the SYSIN data setis invalid.

System actionThe CSD batch update utility terminates abnormally. Ifa SYSABEND or SYSUDUMP DD statement is provided,a system dump is produced.

User responseEnsure that the RECFM parameter in the SYSIN dataset is either F or V.

Module:DFHCSDUP

0302

ExplanationThe record length specified in the SYSIN data set isinvalid.


User responseEnsure that the record length specified in the SYSINdata set is no greater than 80.

Module:DFHCSDUP

0303

ExplanationThe SYSPRINT data set did not open successfully.


User responseEnsure that the SYSPRINT data set exists. Ifnecessary, examine the SYSPRINT DD statement todetermine the cause of the error.

Module:DFHCSDUP

0304

ExplanationDFHCSDUP has found an unrecognized resource typecode in a CSD record. The unrecognized code doesnot match any of the function codes in the languagedefinition table. This can occur for one of the followingreasons:

1. You are using a CICS release that does not supporta type of definition that was created on the CSD fileby a later CICS release.

2. The language definition table (DFHEITSP orDFHEITCU) is invalid for this CICS release.

3. The CSD manager (DFHDMP) has passed an invalidCSD record buffer to DFHPUP. This is a CICSinternal logic error.


User responseDetermine which of the possible reasons caused theerror. If you can eliminate reasons 1 and 2, you canassume that reason 3 applies.

Take action corresponding to the reason you haveestablished as follows:

1. Ignore the message.2. Ensure that the library contains versions of

DFHEITSP and DFHEITCU that are valid for theCICS release you are running.


Module:DFHCSDUP

0305

ExplanationAn unexpected return code was received either whiletrying to close the alternate SYSIN and SYSPRINTDCBs (CLOSEDCB) or while trying to free the task localstorage (FREETLS).






Module:DFHCSDUP

0307

ExplanationAn attempt to print the input command failed. Sincemessages cannot be issued, the utility must terminate.



Module:DFHCSDUP

0308

ExplanationDuring the migration of a TCT table, a bad commandsequence was found. This can occur for one of thefollowing reasons:

• TYPETERM was not preceded by TERMINAL• TERMINAL was not followed by TYPETERM


User responseCorrect the TCT table to be migrated and rerun the job.

Module:DFHCSDUP

0309

ExplanationDFHCSDUP has found an unrecognized function codein a command. This is a CICS internal logic error.



Module:DFHCSDUP

0321

ExplanationAn internal error has occurred in module DFHCSDUPwhen invoked by a CSD utility command.

System actionMessage DFH5100 is issued and the CSD batchupdate utility terminates abnormally. If a SYSABENDor SYSUDUMP DD statement is provided, a systemdump is produced.


Module:DFHCSDUP

0322

ExplanationWhile processing a MIGRATE command, the specifiedtable to be migrated could not be loaded.



Module:DFHCSDUP







0323

ExplanationWhile processing a command, VSAM detected an error.

System actionMessage DFH5179 is issued preceded by eitherDFH5177 or DFH5178 depending on the error and theCSD batch update utility terminates abnormally. If aSYSABEND or SYSUDUMP DD statement is provided, asystem dump is produced.

User responseSee the description of the issued messages todetermine the cause of the error.

Module:DFHCSDUP

0325

ExplanationWhen the LIST command invoked DFHDMP to scanthe objects on the CSD file, an error occurred duringexecution of the DFHDMP function.



Module:DFHCSDUP

0326

ExplanationThere has been an internal logic error in theDFHCSDUP utility program. The data in the back-translated output buffer is invalid. The length codemay be out of range or the data fields in the wrongsequence. One or more of the data fields may beinvalid.



Module:DFHCSDUP

0327

ExplanationThe language table DFHEITCU could not be loaded.


User responseRefer to the preceding message which should specifythe reason for the failure. If you need furtherassistance from IBM to resolve this problem, seeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHCSDUP

0328

ExplanationThe language table DFHEITCU could not be unloaded.


User responseRefer to the preceding message which should specifythe reason for the failure. If you need furtherassistance from IBM to resolve this problem, seeWorking with IBM to solve your problem for guidanceon how to proceed.

Module:DFHCSDUP






0330

ExplanationThe cross reference table size for the table beingmigrated is too small.

System actionThe CSD batch update utility terminates abnormally. Ifa SYSABEND or SYSUDUMP statement is provided, asystem dump is produced.


Module:DFHCSDUP

0331

ExplanationDFHCSDUP was invoked to perform an EXTRACTcommand using a Language Environment-conformingHLL user exit, but the utility failed to initialize the CEEenvironment successfully.

System actionThe CSD batch update utility terminates abnormally.If a SYSABEND or SYSUDUMP statement is provided,a system dump is produced. Register 15 contains theinitialization return code.


Module:DFHCSDUP

0332

ExplanationDFHCSDUP was invoked to perform an EXTRACTcommand using a Language Environment-conformingHLL user exit, but during execution the utility recived abad return code from the Language Environment.

System actionThe CSD batch update utility terminates abnormally.If a SYSABEND or SYSUDUMP statement is provided,a system dump is produced. Register 15 contains theLanguage Environment return code. code.


Module:DFHCSDUP

04xx (external CICS interface) abend codes0401

ExplanationAn external CICS interface (EXCI) request was issuedusing the CALL API or the EXEC API, and the EXCI stubDFHXCSTB link-edited with the application detectedthat it was running in AMODE 24 or AMODE 64. Theexternal CICS interface only supports calls made inAMODE 31.

System actionThe application terminates abnormally.

User responseChange the application so that EXCI calls are made inAMODE 31, or relink-edit the application AMODE 31.

Module:DFHXCSTB.

0402

ExplanationThe external CICS interface module DFHXCPRHissued an MVS ESTAE macro to establish a recoveryenvironment, but a nonzero return code was returnedfrom MVS.

System actionThe application terminates abnormally with a dump.





User responseExamine the dump and any associated MVS messagesproduced to determine why the MVS ESTAE requestfailed.

If the error occurred while processing anINITIALIZE_USER request on behalf of the application,an attempt to format the dump using the CICS IPCSdump formatter does not produce any formattedoutput. This is because the error occurred too earlyin EXCI initialization for there to be any control blocks.

Module:DFHXCPRH

0403

ExplanationThe external CICS interface module DFHXCPRH issuedan MVS GETMAIN request to obtain storage for itsXCGLOBAL block, but a nonzero return code wasreturned from MVS.

System actionModule DFHXCPRH issues an MVS abendwith abend code 0403 which invokes itsESTAE routine to clear up its environment. ASYSMDUMP is taken before returning control tothe application. An application using the EXCICALL API receives RESPONSE(SYSTEM_ERROR)REASON(XCGLOBAL_GETMAIN_ERROR) in its returnarea. The subreason1 field of the return area containsthe R15 return code from MVS indicating why theGETMAIN failed. An application using the EXCI EXECAPI receives RESP(LINKERR) RESP2(602).

User responseUse the MVS R15 return code obtained from theapplication or from the dump to determine whythe MVS GETMAIN request failed. If the reason isinsufficient storage, increase the region size of thebatch application.

An attempt to format the SYSMDUMP produced withthe CICS IPCS dump formatter does not produceany formatted output for the job because the erroroccurred too early in EXCI initialization for there to beany control blocks.

Module:DFHXCPRH

0404

ExplanationThe external CICS interface module DFHXCPRHneeded to take an MVS SDUMP for an earlier reportedproblem. However the error has occurred too earlyin EXCI initialization for EXCI dump services to beavailable.

System actionModule DFHXCPRH issues an MVS abend with abendcode 0404 which invokes its ESTAE routine from whicha SYSMDUMP is taken instead of an SDUMP to capturethe earlier reported problem.

User responseExamine the SYSMDUMP to determine the cause of theearlier reported problem.


Module:DFHXCPRH

0405

ExplanationThe external CICS interface module DFHXCPRH issuedan IEFSSREQ SSI verify request to MVS to determinethe number of the CICS SVC type 3 SVC to use. The SSIVERIFY request failed.

System actionModule DFHXCPRH issues an MVS abendwith abend code 0405 which invokes itsESTAE routine to clear up its environment. ASYSMDUMP is taken before returning control tothe application. An application using the EXCICALL API receives RESPONSE(SYSTEM_ERROR)REASON(SSI_VERIFY_FAILED) in its return area. Thesubreason1 field of the return area contains theR15 return code from MVS indicating why the SSIverify failed. An application using the EXCI EXEC APIreceives RESP(LINKERR) RESP2(606).

User responseUse the MVS R15 return code obtained from theapplication or from the dump to determine why theSSI VERIFY request failed.

An attempt to format the SYSMDUMP produced withthe CICS IPCS dump formatter does not produce


any formatted output for the job because the erroroccurred too early in EXCI initialization for there to beany control blocks.

Module:DFHXCPRH

0406

ExplanationThe external CICS interface module DFHXCPRH calledthe CICS SVC to initialize the EXCI environment. TheCICS SVC call failed.

System actionModule DFHXCPRH issues an MVS abendwith abend code 0406 which invokes itsESTAE routine to clear up its environment. ASYSMDUMP is taken before returning control tothe application. An application using the EXCICALL API receives RESPONSE(SYSTEM_ERROR)REASON(CICS_SVC_CALL_FAILURE) in its return area.The subreason1 field of the return area contains theR15 return code from the CICS SVC indicating whyit failed. An application using the EXCI EXEC APIreceives RESP(LINKERR) RESP2(607).

User responseUse the MVS R15 return code obtained from theapplication or from the dump to determine why theCICS SVC call failed.


Module:DFHXCPRH

0407

ExplanationThe external CICS interface module DFHXCPRH issueda call to the CICS SVC to check whether the SVC in useis at the correct level to be used with the external CICSinterface. The check failed indicating that the CICSSVC is not at the correct level.

System actionMessage DFHEX0100 is output, and moduleDFHXCPRH issues an MVS abend with abend code0407 which invokes its ESTAE routine to clear up itsenvironment. A SYSMDUMP is taken before returning

control to the application. An application using theEXCI CALL API receives RESPONSE(SYSTEM_ERROR)REASON(INCORRECT_SVC_LEVEL) in its return area.An application using the EXCI EXEC API receivesRESP(LINKERR) RESP2(627).

User responseSee the explanation of message DFHEX0100 forguidance.


Module:DFHXCPRH

0408

ExplanationThe external CICS interface module DFHXCPRH issuedan MVS GETMAIN request for its working storage but anonzero return code was returned from MVS.

System actionModule DFHXCPRH issues an MVS abendwith abend code 0408 which invokes itsESTAE routine to clear up its environment. ASYSMDUMP is taken before returning control tothe application. An application using the EXCICALL API receives RESPONSE(SYSTEM_ERROR)REASON(WS_GETMAIN_ERROR) in its return area.The subreason1 field of the return area containsthe R15 return code from MVS indicating why theGETMAIN failed. An application using the EXCI EXECAPI receives RESP(LINKERR) RESP2(601).



Module:DFHXCPRH

0409


ExplanationThe external CICS interface module DFHXCPRH issuedan MVS GETMAIN request for storage required for itsSSI VERIFY request, but a nonzero return code wasreturned from MVS.

System actionModule DFHXCPRH issues an MVS abendwith abend code 0409 which invokes itsESTAE routine to clear up its environment. ASYSMDUMP is taken before returning control tothe application. An application using the EXCICALL API receives RESPONSE(SYSTEM_ERROR)REASON(VERIFY_BLOCK_GM_ERROR) in its returnarea. The subreason1 field of the return area containsthe R15 return code from MVS indicating why theGETMAIN failed. An application using the EXCI EXECAPI receives RESP(LINKERR) RESP2(605).



Module:DFHXCPRH

0410

ExplanationThe external CICS interface module DFHXCPRH issuedan MVS GETMAIN request for an XCUSER block but anonzero return code was returned from MVS.

System actionModule DFHXCPRH issues an MVS abendwith abend code 0410 which invokes itsESTAE routine to clear up its environment. ASYSMDUMP is taken before returning control tothe application. An application using the EXCICALL API receives RESPONSE(SYSTEM_ERROR)REASON(XCUSER_GETMAIN_ERROR) in its returnarea. The subreason1 field of the return area containsthe R15 return code from MVS indicating why theGETMAIN failed. An application using the EXCI EXECAPI receives RESP(LINKERR) RESP2(603).


Module:DFHXCPRH

0411

ExplanationThe external CICS interface dump module DFHXCDMPwas attempting to call the CICS SVC in order foran MVS SDUMP to be taken to capture an earlierproblem. DFHXCDMP was unable to call the SVC asno SVC number was available. DFHXCDMP issued an0411 abend in order that the callers ESTAE routine isinvoked which takes a SYSMDUMP instead.

System actionA SYSMDUMP is taken instead of an SDUMP for anearlier reported problem.

User responseUse the SYSMDUMP produced to diagnose the earlierreported problem.


Module:DFHXCDMP

0412

ExplanationThe external CICS interface dump module DFHXCEIPwas processing an EXCI EXEC API request anddetected that the EXEC parameter list passed to itcontained a function that is not supported by theexternal CICS interface.

System actionThe application is abnormally terminated with a dump.

User responseThis error indicates the parameter list being passedto the EXCI has not been generated by the CICStranslator. The translator should always be used.


Correct the application to specify the correct EXCIEXEC API command.

An attempt to format the SYSMDUMP produced withthe CICS IPCS dump formatter may not produce anyformatted output for the job if this was the first EXCIrequest for this TCB.

Module:DFHXCEIP

0413

ExplanationThe external CICS interface dump module DFHXCEIPwas processing an EXCI EXEC API request anddetected that the EXEC parameter list passed to itdid not require the mandatory RETCODE parameter inwhich return codes are returned to the application.

An attempt to format the SYSMDUMP produced withthe CICS IPCS dump formatter may not produce anyformatted output for the job if this was the first EXCIrequest for this TCB.

System actionThe application is abnormally terminated with a dump.

User responseThis error indicates the parameter list being passedto the EXCI has not been generated by the CICStranslator. The translator should always be used.Correct the application to specify RETCODE.

Module:DFHXCEIP

0414

ExplanationThe external CICS interface module DFHXCEIP issuedan MVS ESTAE macro to establish a recoveryenvironment but a nonzero return code was returnedfrom MVS.


User responseExamine the dump and any associated MVS messagesto determine why the MVS ESTAE request failed.

An attempt to format the SYSMDUMP produced withthe CICS IPCS dump formatter may not produce any

formatted output for the job if this was the first EXCIrequest for this TCB.

Module:DFHXCEIP

0415

ExplanationThe external CICS interface module DFHXCEIPdetected an error early in EXCI initialization beforeEXCI dump services were available. DFHXCEIP issuesabend 0415 so that its ESTAE routine is invoked fromwhere an SYSMDUMP is taken instead to capture theerror.


User responseExamine the SYSMDUMP to determine the cause of theearlier reported error.


Module:DFHXCEIP

0416

ExplanationThe external CICS interface module DFHXCEIPreceived an unexpected return code from DFHXCBAMwhen processing a channels and containers command.



Module:DFHXCEIP

0417


ExplanationThe External CICS interface has refused to store datain a Container because the total storage allocated forthe Channel will exceed 5% of MEMLIMIT.


User responseReview the storage requirements for the PROGRAM.If the volume of data is correct, either delete anyunnecessary Containers from the Channel, or increaseMEMLIMIT so that the program does not use morethan 5% of the storage available.

Module:DFHXBAM

0418

ExplanationThe external CICS interface module DFHXCBAMreceived a purged response when processing achannels and containers command.



Module:DFHXCBAM

0419

ExplanationThe external CICS interface module DFHXCBAMreceived a disaster response when processing achannels and containers command.



Module:DFHXCBAM

4xxx LE/370 abend codesAbend codes in the range 4000 to 4095 are issued by LE/370 runtime library modules for LE enabledapplications running on CICS.

When LE/370 detects an unrecoverable error, LE/370 terminates the transaction with an EXEC CICSabend with an abend code numbered from 4000-4095. A write-to-operator (WTO) is performed to writea CEE1000S message to the system console. This message contains the abend code and the reason codeassociated with the abend.

Some of these abends can occur when the system is under stress and LE/370 is unable to acquire theresources required to report a previous abend or failure. In this case there will usually be other symptomsthat the system is under stress (for example short on storage messages or other transactions beingpurged with AEXY or AKC3 abends), and inspection of the transaction dump should allow identification ofthe original abend.

LE/370 abend codes and run-time messages are described in Language Environment abend codes in z/OSLanguage Environment Runtime Messages.


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ceea900/abd.htm

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ceea900/abd.htm

CICSPlex SM Abend and dump codesWhen abnormal conditions occur, CICSPlex® SM attempts to recover in an orderly manner and continuewith normal processing. Occasionally conditions arise that prevent or preclude such recovery and a task,component, or system might end. In this situation, an abend or dump code is issued.

CICS abend and dump codesIf you have to contact IBM in response to an abend or dump code, gather as much diagnostic informationas possible.

The following diagnostic information is required by IBM support to help diagnose the problem:

• Job log from the MAS.• EYULOG from the CMAS to which the MAS was connected or was attempting to connect.• CICS TRANDUMP data set from the MAS. Use the CICS DFHDUP utility to format the dump data set.• CICS AUXTRACE data set from the MAS, if available. Use the EYU9XZUT trace format utility to format

the data set, as described in Using trace in CICSPlex SM. Also keep a copy of the unformatted trace dataset.

EYUI

Explanation:A non-recoverable error occurred during initialization.

System action:MAS initialization terminates. The CICS systemcontinues to run normally, but it is not known toCICSPlex SM.

User response:Examine the MAS job log for any messages that mightindicate a problem. If such messages exist, followthe instructions associated with those messages andthen restart the MAS. If no messages exist, or if noappropriate action is indicated, gather the specifieddiagnostic information and contact your IBM supportcenter.

Module:EYU9XLEV

EYUK

Explanation:Either a non-recoverable abend occurred during MASinitialization or a proper environment did not existwhen attempting to recover from an abend.

System action:MAS initialization terminates. The CICS systemcontinues to run normally, but it is not known toCICSPlex SM.

System action:If this abend occurred during initialization, MASinitialization terminates. The CICS system continues torun normally, but it is not known to CICSPlex SM.

User response:Examine the MAS job log for any messages that mightindicate a problem. If such messages exist, follow theinstructions associated with those messages and then

restart the MAS, if necessary. If no messages exist,or if no appropriate action is indicated, gather thespecified diagnostic information and contact your IBMsupport center.

Module:EYU9XLRV

EYUO

Explanation:The environment create routine in a CMAS or MAS wascalled invalidly. The calling process was not a CICSPlexSM service.

System action:CICS system processing continues.

User responseMake sure that:

• No site-written programs are attempting to callCICSPlex SM environment create.

• Users are not attempting to use CICSPlex SMTRANIDS directly, either from a terminal or via anEXEC CICS START.

If neither of these conditions exists, gather thespecified diagnostic information and contact your IBMsupport center.

Module:EYU9XLOP

EYUR

Explanation:An error occurred while attempting to recover from anabend.

System action:


http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/troubleshooting/cpsm/eyus1br.html

The failing task terminates. The CICS systemcontinues to run normally, but it may not be knownto CICSPlex SM.

User response:Examine the MAS job log for any messages that mightindicate a problem. If such messages exist, follow theinstructions associated with those messages and thenrestart the MAS, if necessary. If no messages exist,or if no appropriate action is indicated, gather thespecified diagnostic information and contact your IBMsupport center.

Module:EYU9XLRV

EYUV

Explanation:The Web User Interface environment create routinein a CMAS or MAS was called invalidly. The callingprocess was not a CICSPlex SM service.

System action:The failing task terminates. A transaction dump istaken. CICS system processing continues.

User responseMake sure that:

• No site-written programs are attempting to callCICSPlex SM Web User Interface environmentcreate.

• Users are not attempting to use CICSPlex SMTRANIDS directly, either from a terminal or via anEXEC CICS START.

If neither of these conditions exists, contact your IBMSupport Center.

Module:EYU0VGIN

EYUX

Explanation:An exception condition was detected in a remote MASbut a full CICSPlex SM exception trace could not bewritten at that time. This condition is not necessarilya failure in the application, but the reportingof an exception condition, which is usually the

result of communications problems. Communicationsexceptions cannot be sent to the connected CMAS.

System action:A transaction dump is taken to document theexception. Task execution continues, taking theappropriate action for the exception condition.

User response:Examine the MAS and CMAS job logs for any messagesthat might indicate a problem, especially for thoserelated to the communications network. If suchmessages exist, follow the instructions associatedwith those messages. If no messages exist, or if noappropriate action is indicated, gather the specifieddiagnostic information and contact your IBM supportcenter.

Module:EYU9XLEV, EYU9XLOP

EYUY

Explanation:A CMAS-to-CMAS connection has terminatedabnormally. The receive task component of theconnection has tried to terminate as cleanly aspossible, but it has detected that it is still in anetwork receive state. This makes it impossiblefor it to terminate, without CICS generating anadditional transaction abend describing this apparenttransmission state discrepancy. However, this networkstate cannot be reset because of the reportedconnection failure. This abend is issued to preemptthe normal CICS abend code related to these networkstate errors.

System action:The CPI-C or MRO receive task should now endcompletely with this abend. When all task componentsfor the connection have terminated, the first speakerCMAS of the connection pair should attempt toreestablish the connection.

User response:Check the CMAS job log, EYULOG, and CICS messagelog for previous failures or error conditions and followthe User Response for these messages.

Module:EYU0CLCT, EYU0CLCU, EYU0CLMT, EYU0CLMU

Uxxxx abend codesIn response to any of the Uxxxx abend codes, gather as much diagnostic information as possible andcontact IBM support.

For a list of available diagnostic information, see “CICS abend and dump codes” on page 323.

U100

Explanation:An ISPF interface failure has occurred.

U1600

Explanation:A PC has issued a call to an unavailable service.


U1700 throughU1798

Explanation:Recovery Manager abends.

U1799

Explanation:A should-not-occur condition has occurred.

U1800

Explanation:Indicates that a C housekeeping failure has occurred.

U1801

Explanation:A failure has occurred in GSI housekeeping.

U1802

Explanation:A failure has occurred in GSI router housekeeping.

U1803

Explanation:A transaction manager housekeeping failure hasoccurred.

U1804

Explanation:A failure has occurred in the SAS/C resident module.

U1899

Explanation:System environmental conditions have caused afailure with DYNAEC EPD.

U1900

Explanation:A failure has occurred with the storage manager.

U3000

Explanation:An error has occurred in a built in service functionroutine.

U4000

Explanation:Indicates that a pseudo GSI service failure hasoccurred.

U4080

Explanation:An unrecoverable control task error has occurred.

U4090

Explanation:A server or application initialization error has occurred.

U4095

Explanation:A task has been terminated by PGTERM.

System dump codesIn response to any of these dump codes, gather the following diagnostic information and contact yourIBM Support Center:

• Job log and EYULOG from the CMAS.• Unformatted SVC dump (SDUMP). Have access to IPCS.• CICS AUXTRACE data set from the CMAS. Use the EYU9XZUT trace format utility to format the data set.

Also keep a copy of the unformatted trace data set.

EYUXL001

Explanation:The initialization process failed.

System action:initialization terminates.

Module:EYU9XLEV

EYUXL002

Explanation:The recovery routine was entered during initialization.

System action:

initialization terminates.

Module:EYU9XLRV

EYUXL003

Explanation:The recovery routine was entered, but could notsuccessfully recover from the abend.

System action:processing terminates.

Module:EYU9XLRV



Notices

This information was developed for products and services offered in the U.S.A. This material might beavailable from IBM in other languages. However, you may be required to own a copy of the product orproduct version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program, orservice that does not infringe any IBM intellectual property rights may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You cansend license inquiries, in writing, to:

IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY 10504-1785 United States of America

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS”WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR APARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties incertain transactions, therefore this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Licensees of this program who want to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact

IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY 10504-1785United States of America


Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Programming License Agreement, orany equivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions.Actual results may vary.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to actual people or business enterprises isentirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platformfor which the sample programs are written. These examples have not been thoroughly tested underall conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Programming interface informationCICS supplies some documentation that can be considered to be Programming Interfaces, and somedocumentation that cannot be considered to be a Programming Interface.

Programming Interfaces that allow the customer to write programs to obtain the services of CICSTransaction Server for z/OS, Version 5 Release 6 are included in the following sections of the onlineproduct documentation:

• Developing applications• Developing system programs• CICS TS security• Developing for external interfaces• Application development reference• Reference: system programming• Reference: connectivity

Information that is NOT intended to be used as a Programming Interface of CICS Transaction Server forz/OS, Version 5 Release 6 , but that might be misconstrued as Programming Interfaces, is included in thefollowing sections of the online product documentation:

• Troubleshooting and support• CICS TS diagnostics reference

If you access the CICS documentation in manuals in PDF format, Programming Interfaces that allow thecustomer to write programs to obtain the services of CICS Transaction Server for z/OS, Version 5 Release6 are included in the following manuals:

• Application Programming Guide and Application Programming Reference

328 Notices

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/applications/developing.html

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/system-programming/developing_sysprogs.html

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/security/security.html

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/applications/developing/interfaces/externalInterfaces.html

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/reference-applications/reference-programming.html

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/home/reference-systemprogramming.html

http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/reference-connectivity/reference-connections.html


http://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/home/reference-diagnostics.html

• Business Transaction Services• Customization Guide• C++ OO Class Libraries• Debugging Tools Interfaces Reference• Distributed Transaction Programming Guide• External Interfaces Guide• Front End Programming Interface Guide• IMS Database Control Guide• Installation Guide• Security Guide• Supplied Transactions• CICSPlex SM Managing Workloads• CICSPlex SM Managing Resource Usage• CICSPlex SM Application Programming Guide and Application Programming Reference• Java™ Applications in CICS

If you access the CICS documentation in manuals in PDF format, information that is NOT intended to beused as a Programming Interface of CICS Transaction Server for z/OS, Version 5 Release 6 , but that mightbe misconstrued as Programming Interfaces, is included in the following manuals:

• Data Areas• Diagnosis Reference• Problem Determination Guide• CICSPlex SM Problem Determination Guide

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the Web atCopyright and trademark information at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks ortrademarks of Adobe Systems Incorporated in the United States, and/or other countries.

Apache, Apache Axis2, Apache Maven, Apache Ivy, the Apache Software Foundation (ASF) logo, and theASF feather logo are trademarks of Apache Software Foundation.

Gradle and the Gradlephant logo are registered trademark of Gradle, Inc. and its subsidiaries in the UnitedStates and/or other countries.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon,Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation orits subsidiaries in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

The registered trademark Linux® is used pursuant to a sublicense from the Linux Foundation, the exclusivelicensee of Linus Torvalds, owner of the mark on a worldwide basis.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

Red Hat®, and Hibernate® are trademarks or registered trademarks of Red Hat, Inc. or its subsidiaries inthe United States and other countries.

Notices 329

https://www.ibm.com/legal/copytrade.shtml

Spring Boot is a trademark of Pivotal Software, Inc. in the U.S. and other countries.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Zowe™, the Zowe logo and the Open Mainframe Project™ are trademarks of The Linux Foundation.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the following terms and conditions.Applicability

These terms and conditions are in addition to any terms of use for the IBM website.Personal use

You may reproduce these publications for your personal, noncommercial use provided that allproprietary notices are preserved. You may not distribute, display or make derivative work of thesepublications, or any portion thereof, without the express consent of IBM.

Commercial useYou may reproduce, distribute and display these publications solely within your enterprise providedthat all proprietary notices are preserved. You may not make derivative works of these publications,or reproduce, distribute or display these publications or any portion thereof outside your enterprise,without the express consent of IBM.

RightsExcept as expressly granted in this permission, no other permissions, licenses or rights are granted,either express or implied, to the publications or any information, data, software or other intellectualproperty contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the useof the publications is detrimental to its interest or, as determined by IBM, the above instructions arenot being properly followed.

You may not download, export or re-export this information except in full compliance with allapplicable laws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONSARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED ORIMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM online privacy statementIBM Software products, including software as a service solutions, (Software Offerings) may use cookies orother technologies to collect product usage information, to help improve the end user experience, to tailorinteractions with the end user or for other purposes. In many cases no personally identifiable informationis collected by the Software Offerings. Some of our Software Offerings can help enable you to collectpersonally identifiable information. If this Software Offering uses cookies to collect personally identifiableinformation, specific information about this offering’s use of cookies is set forth below:

For the CICSPlex SM Web User Interface (main interface):Depending upon the configurations deployed, this Software Offering may use session and persistentcookies that collect each user’s user name and other personally identifiable information for purposesof session management, authentication, enhanced user usability, or other usage tracking or functionalpurposes. These cookies cannot be disabled.

For the CICSPlex SM Web User Interface (data interface):Depending upon the configurations deployed, this Software Offering may use session cookies thatcollect each user's user name and other personally identifiable information for purposes of sessionmanagement, authentication, or other usage tracking or functional purposes. These cookies cannot bedisabled.

For the CICSPlex SM Web User Interface ("hello world" page):Depending upon the configurations deployed, this Software Offering may use session cookies thatcollect no personally identifiable information. These cookies cannot be disabled.

330 Notices

For CICS Explorer®:Depending upon the configurations deployed, this Software Offering may use session and persistentpreferences that collect each user’s user name and password, for purposes of session management,authentication, and single sign-on configuration. These preferences cannot be disabled, althoughstoring a user's password on disk in encrypted form can only be enabled by the user's explicit actionto check a check box during sign-on.

If the configurations deployed for this Software Offering provide you, as customer, the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes, seeIBM Privacy Policy and IBM Online Privacy Statement, the section entitled Cookies, Web Beacons andOther Technologies and the IBM Software Products and Software-as-a-Service Privacy Statement.

Notices 331

https://www.ibm.com/privacy

https://www.ibm.com/privacy/details

https://www.ibm.com/software/info/product-privacy


IBM®

CICS TS for z/OS: CICS Codes - IBM

Documents