CICS ABENDS

7/31/2019 CICS ABENDS

1/28

Just for reference , posting CICS abend codes on this thread.

Code:

AACA

Explanation: An invalid error code has been passed tothe DFHTFP or DFHACP programs.System Action: CICS terminates the task abnormallywith a dump.User Response: Notify the system programmer.Module: DFHTFP,DFHACP

AALM Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the log manager (LM) 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 dump table).System Action: The task is abnormally terminated

with a CICS transaction dump.User Response: See the related message produced bythe domain that detected the original error.Module: DFHAMLM

AALNExplanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the TD manager. The domain that detected theoriginal error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Inform the system programmer.

Examine the trace and the dump to identify the pointof error.Module: DFHAMTD

AALOExplanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the CICS/DB2 table manager DFHD2TM. Thedomain that detected the original error provides a traceentry and possibly a system dump (depending on theoptions specified in the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Inform the system programmer.

Examine the trace and the dump to identify the pointof error.Module: DFHAMD2

AALPExplanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Program Manager. The domain that detectedthe original error provides a trace entry and possibly asystem dump (depending on the options specified in


2/28

the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Inform the system programmer.Examine the trace and the dump to identify the pointof error.Module: DFHAMPG

AALQExplanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Business Application Manager. The domainthat detected the original error provides a trace entryand possibly a system dump (depending on the optionsspecified in the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Inform the system programmer.Examine the trace and the dump to identify the pointof error.Module: DFHAMBA

AALRExplanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Temporary Storage Manager. The domainthat detected the original error provides a trace entryand possibly a system dump (depending on the optionsspecified in the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Inform the system programmer.Examine the trace and the dump to identify the pointof error.Module: DFHAMBA

AALSExplanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Global Enqueue Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Inform the system programmer.Examine the trace and the dump to identify the pointof error.Module: DFHAMBA

AALTExplanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Internet Inter-Orb Protocol Manager. Thedomain that detected the original error provides a traceentry and possibly a system dump (depending on theoptions specified in the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Inform the system programmer.


3/28

Examine the trace and the dump to identify the pointof error.Module: DFHAMOP

AALUExplanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Sockets Domain Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Inform the system programmer.Examine the trace and the dump to identify the pointof error.Module: DFHAMSO

AALVExplanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on a

call to the Enterprise Java Domain. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Inform the system programmer.Examine the trace and the dump to identify the pointof error.Module: DFHAMEJ

AAL1Explanation: DFHALP was processing a request thatdeadlocked. The most likely reason for the abend isthat an ALLOCATE QUEUE request has been

suspended because there are no contention-winninglinks available.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 Action: CICS terminates the task abnormally.A dump is taken.User Response: Ensure that there are enoughcontention-winning sessions available to satisfy the

ALLOCATE QUEUE request.If you are running with modegroups, ensure that thereare contention-winning sessions available to satisfy the

ALLOCATE request in that modegroup.Module: DFHALP

AAL2Explanation: Either an incorrect response (other thanPURGED) was returned from the suspend of theallocated task, or an incorrect response was returnedfrom the resume.System Action: The transaction is abnormally


4/28

terminated with a dump.User Response: Check the return code from theresume or the suspend to determine the cause of theerror.Module: DFHALP

AAL3Explanation: The task has been purged before aGETMAIN request to the storage manager (SM)domain was able to complete successfully. The task thatfirst detected the purged condition provides anexception trace.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Investigate the reason why the taskwas purged. It was purged either by the masterterminal operator or as a result of a deadlock timeout.Module: DFHALP

AAL4Explanation: An error (INVALID, DISASTER or

unexpected EXCEPTION response) has occurred on acall to the storage manager (SM) domain. The domainthat detected the original error provides an exceptiontrace, a console message, and possibly a system dump(depending on the options specified in the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: See the related message produced bythe domain that detected the original error.Module: DFHALP

AAL6Explanation: An error (INVALID, DISASTER orEXCEPTION response) has occurred on a call to

SIGNOFF_TERMINAL_USER by DFHALP duringsign-off for a surrogate terminal session running CRTE.The domain that detected the original error provides anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: See the related message produced bythe domain that detected the original error.Module: DFHALP

AAL7Explanation: An error (INVALID, DISASTER orEXCEPTION response) has occurred on a call to

schedule a remote terminal delete by DFHALP duringsign-off for a surrogate terminal session running CRTE.The domain that detected the original error provides anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: See the related message produced bythe domain that detected the original error.Module: DFHALP


5/28

AAL8Explanation: DFHALP was processing a request thatdeadlocked. The most likely reason for the abend isthat an ALLOCATE QUEUE request has beensuspended because there are no contention-winninglinks available.AAL1 is issued for non time-out related deadlocks.AAL8 is issued for stall purges and deadlock time-outs.System Action: CICS terminates the task abnormally.A transaction or system dump is not taken unless thetransaction dump table has been modified for AAL8.User Response: Ensure that there are enoughcontention-winning sessions available to satisfy the

ALLOCATE QUEUE request.If you are running with modegroups, ensure that thereare contention-winning sessions available to satisfy the

ALLOCATE request in that modegroup.It might be necessary to increase the deadlock timeout(DTIMEOUT) value for the transaction to prevent thisabend from recurring.If you require a transaction or system dump for thisabend then add AAL8 to the transaction dump table.Module: DFHALP

AAMAExplanation: There is an internal logic error inDFHAMP.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: You need further assistance from IBM

to resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.Module: DFHAMP

AAMCExplanation: The task was purged before a GETMAINrequest to the storage manager domain was able tocomplete successfully.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Investigate the reason the task waspurged. It was purged either by the master terminaloperator or as a result of deadlock timeout.Module: DFHAMP

AAMDExplanation: An unexpected return code has beenreceived from DFHDMP. This is due to an internal logicerror.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.Module: DFHAMP


6/28

AAMFExplanation: An unexpected return code has beenreceived following a call to the kernel (KE) domain.This might be due to an internal logic error.System Action: CICS terminates the task abnormallywith a dump.User Response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.Module: DFHAMP

AAMHExplanation: An unexpected return code has beenreceived following a call to DFHFCMT. This might bedue to an internal logic error.System Action: CICS terminates the task abnormallywith a dump.User Response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS Problem

Determination Guide for guidance on how to proceed.Module: DFHAMP

AAMIExplanation: An unexpected return code has beenreceived following a call to DFHFCRL. This might bedue to an internal logic error.System Action: CICS terminates the task abnormallywith a dump. You need further assistance from IBM toresolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.User Response:Module: DFHAMP

AAMJExplanation: While installing a file, using RDO, a callwas made to DFHFCFS to enable the file. Anirrecoverable error was returned from DFHFCFS.System Action: The task is abnormally terminatedwith a CICS transaction dump.At the time the error is detected, CICS writes amessage to the console, records an exception trace entryand takes a system dump.User Response: Inform the system programmer.Examine the trace and the dump to identify the pointof error.Module: DFHAMP

AAMKExplanation: While installing a file, using RDO, a callwas made to DFHFCDN. An irrecoverable error wasreturned from DFHFCDN.System Action: The task is abnormally terminatedwith a CICS transaction dump. At the time the error isdetected, CICS writes a message to the console, recordsan exception trace entry, and takes a system dump.User Response: Inform the system programmer,Examine the trace and dump to identify the point oferror.


7/28

Module: DFHAMP

AAMNExplanation: There has been an unexpected returncode from a call to DFHPRPT. This might be due to aninternal logic error.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.Module: DFHAMP

AAMOExplanation: An invalid return code was returnedfrom DFHTOR, the CICS terminal object resolutionprogram.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: You need further assistance from IBM

to resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.Module: DFHAMP

AAMPExplanation: An unexpected return code has beenreceived from DFHPUP. This might be due to aninternal logic error.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.Module: DFHAMP

AAMQExplanation: An attempt has been made to install apartner using RDO. However, the partner resourcemanager (PRM) is unavailable having failed to initializeduring CICS initialization.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: If you need to use the PRM, correctthe problem which prevented the PRM frominitializing, and restart CICS.Module: DFHAMP

AAMS

Explanation: There has been an unexpected returncode following a GETMAIN request to the storagemanager. This is due to an internal logic error.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.Module: DFHAMP


8/28

AAMTExplanation: There is an internal logic error inDFHAMP due to an unexpected return code fromDFHTMP.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.Module: DFHAMP

AAMZExplanation: An unexpected return code has beenreceived from DFHZCP. This is due to an internal logicerror.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.

Module: DFHAMP

AAM1Explanation: DFHXMCL has returned an unexpectedresponse during the install of a transaction class. Thiscan be caused by the task being purged during theinstall.System Action: The transaction is abnormallyterminated with a CICS transaction dump.If an error has occurred, at the time the error isdetected, CICS issues a DFHXMnnnn console message,records an exception trace entry and takes a systemdump.User Response: Determine why the task has failed. Ifthere is a system dump, use it together with the trace

entry and the console message to resolve the problem.If there is no system dump, the task has been purgedeither by the master terminal operator or as a result ofdeadlock timeout.Module: DFHAMP

AAM2Explanation: DFHXMXD has returned an unexpectedresponse during the install of a transaction definition.This can be caused by the task being purged during theinstall.System Action: The transaction is abnormallyterminated with a CICS transaction dump.If an error has occurred, at the time the error isdetected, CICS issues a DFHXMnnnn console message,

records an exception trace entry and takes a systemdump.User Response: Determine why the task has failed. Ifthere is a system dump, use it together with the traceentry and the console message to resolve the problem.If there is no system dump, the task has been purgedeither by the master terminal operator or as a result ofdeadlock timeout.Module: DFHAMP


9/28

AAOAExplanation: An application has issued a CPI verbwhich CICS does not support. The entry pointreferenced in the application program was resolved inthe link edit stub, but the function requested could notbe resolved when control passed to CICS.There are two possible reasons for this:v You have linkedited your application program with aCPI stub which supports more function than thisrelease of CICS.v The linkedit stub has been corrupted.System Action: The transaction is abnormallyterminated with a CICS transaction dump. Anexception trace entry is also written.User Response: At the time of the error, generalregister 0 points to an 8-byte character string whichshould match the name of the issued CPI call. Use thetrace or the dump to verify that this character string isthe name of a CPI function which is supported.If the character string is not an intelligible characterstring, the stub has probably been corrupted.Module: DFHCPI

AAOBExplanation: An application has issued a CPI verbwhich specifies more than eight parameters.System Action: The transaction is abnormallyterminated with a CICS transaction dump and anexception trace entry is also written.User Response: Change your application program sothat the correct number of parameters is specified onthe CPI call.Module: DFHCPI

AAOCExplanation: CPI Communications is invoked with aninvalid number of parameters for callSystem Action: The transaction is abnormally

terminated with a CICS transaction dump.User Response: The exception trace point producedwith this abend contains the incorrectly issued CPICommunications verb name. Use this to determinewhere the application program was in error and amendit accordingly.The SAA CPI Communications Reference manual,SC26-4399, provides a detailed description of all theCPI Communications verbs and how they should becalled.Module: DFHCPARH

AAODExplanation: The task was purged before a GETMAINrequest to the storage manager (SM) domain was able

to complete successfully. The domain that first detectedthe purged condition provides an exception trace.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Investigate the reason the task waspurged. It was purged either by the master terminaloperator or as a result of deadlock timeout.Module: DFHCPCBI

AAOE


10/28

Explanation: The task was purged before a GETMAINrequest to the storage manager (SM) domain was ableto complete successfully. The domain that first detectedthe purged condition provides an exception trace.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Investigate the reason the task waspurged. It was purged either by the master terminaloperator or as a result of deadlock timeout.Module: DFHCPCBA

AAOFExplanation: The task was purged before a GETMAINrequest to the storage manager (SM) domain was ableto complete successfully. The domain that first detectedthe purged condition provides an exception trace.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Investigate the reason the task waspurged. It was purged either by the master terminaloperator or as a result of deadlock timeout.Module: DFHCPCBS

AAOGExplanation: During the processing of CMACCP(accept conversation), CPI Communications detectedthat the application was attached with an unsupportedsync level.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This condition is caused by aback-end CPI Communications transaction beingattached with a sync level that is not CM_NONE (0) orCM_CONFIRM (1).Change the front-end transaction, (that is, the initiatorof the conversation in the other system) so that itdefines the sync level correctly.

Module: DFHCPCBA

AAOHExplanation: Journaling of data sent on a CPIcommunications mapped conversation has failed. Thiscondition is caused by a nonzero response from theCICS log manager.Problem Determination: Register 12 addresses thecurrent TCA and field TCAJCAAD and register 4address the JCA. The log manager request is containedin JCATR2 and the response code is in JCAJCRC.Possible request codes are:X8001 - WRITEX8003 - PUTPossible response codes are:

X01 - IDERROR - Journal identification errorX02 - INVREQ - Invalid requestX03 - STATERR - Status errorX05 - NOTOPEN - Journal not openX06 - LERROR - Journal record length errorX07 - IOERROR - I/O error.The address of the TIOA is contained in register 8 andits data length is in TIOATDL.Analysis:Register Label DescriptionR4=@JCA TCZARQPJ JCAJCRC is nonzero.


11/28

System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Use the dump to ascertain why thejournal or log record could not be written correctly. If ajournal record length error is indicated, TIOATDL mayhave been corrupted.Module: DFHCPCOJ

AAOIExplanation: The journaling of data received on a CPICommunications mapped conversation has failed.Problem Determination: Register 12 addresses thecurrent TCA and field TCAJCAAD and register 4address the JCA. The CICS log manager request iscontained in JCATR2 and the response code is inJCAJCRC.Possible request codes are:X8001 WRITEX8003 PUTPossible response codes are:X'01' IDERROR Journal identification error

X'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 DescriptionR4=@JCA TCZARQPJ JCAJCRC is nonzero.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This condition is caused by an invalidresponse from the log manager. Use the dump toascertain why the journal or log record could not bewritten correctly. If a journal record length error is

indicated, TIOATDL may have been corrupted.Modules: DFHCPCRI, DFHCPCRW

AAOJExplanation: CPI Communications has detected anunexpected response from one of its internal routines.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This is a CICS internal logic error.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.

You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Module: DFHCPIC

AAOKExplanation: CPI Communications has detected anunexpected call to one of its internal routines.System Action: The transaction is abnormally


12/28

terminated with a CICS transaction dump.User Response: This is a CICS internal logic error.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.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Module: DFHCPIC

AAOLExplanation: CPI Communications has made aninvalid call to DFHLUC.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This is a CICS internal logic error.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.

You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Module: DFHCPCLR

AAOMExplanation: The CPI Communications and theDFHZUSR state machines are out of synchronization.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This is a CICS internal logic error.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.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Modules: DFHCPCLR, DFHCPSRH

AAONExplanation: CPI Communications has detected anunexpected response from DFHLUC.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This is a CICS internal logic error.

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.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Modules: DFHCPCLR, DFHCPCLC


13/28

AAOOExplanation: CPI Communications 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.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: A level 2 trace for CP of thetransaction shows the course of events before this erroroccurred (such as the modules called and theirparameters) plus details of the error itself.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Module: DFHCPARH

AAOPExplanation: The CPI Communications state machinehas been requested to perform a state transition requestthat is considered to be an impossible situation. (The

SAA CPI Communications Reference manual, (SC26-4399)documents all these situations.)There are two possible causes of this error:v The CPC (conversation control block) has beenoverwritten in such a way that the conversation statehas been altered, orv There is an error in the CPI Communications statemachine.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: A level 2 trace for CP of thetransaction shows the course of events prior to thiserror, for example, the modules called and theirparameters. The level 2 trace also provides details ofthe error itself.The transaction dump shows the CPC. You may need

further assistance from IBM to fully resolve thisproblem. You need further assistance from IBM toresolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.Module: DFHCPCFS

AAOQExplanation: The return code generated by CPICommunications does not have an entry in the statetable against the current CPI Communications verb.This error is detected by the CPI Communications statemachine.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This is a CICS internal logic error.

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.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Module: DFHCPCFS


14/28

AAORExplanation: CPI Communications has detected aninvalid value in the CPC (conversation control block).There are 2 possible causes of this error:v The CPC (conversation control block) has beenoverwritten, orThere is an error in CPI Communications whichcauses it to reject valid values.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: A level 2 trace for CP of thetransaction shows the course of events prior to thiserror, for example, the modules called and theirparameters. The level 2 trace also provides details ofthe error itself.Module: DFHCPIC

AAOSExplanation: CPI Communications has detected thatthe conversation state is RESET for a situation wherethis should not occur. That is, the conversation controlblock (CPC) is about to be deleted.

There are two possible causes of this error:v The CPC has been overwritten, orv There is an error in CPI communications.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: A level 2 trace for CP of thetransaction shows the course of events prior to thiserror, for example, the modules called and theirparameters. The level 2 trace also provides details ofthe error itself. You may need further assistance fromIBM to fully resolve this problem. You need furtherassistance from IBM to resolve this problem. See Part 4of the CICS Problem Determination Guide for guidanceon how to proceed.Module: DFHCPIC

AAOTExplanation: While chaining through the CPCs(conversation control blocks) for a given conversation,CPI Communications detected that the chain wasbroken.There are two possible causes of this error.1. The CPC chain has been overwritten, or2. There is an error in the CPI Communicationschaining mechanism.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Determine which of the above causedthe error.A level 2 trace for CP of the transaction shows the

course of events prior to this error, for example, themodules called and their parameters. The level 2 tracealso provides details of the error itself.You may need further assistance from IBM to fullyresolve this problem. You need further assistance fromIBM to resolve this problem. See Part 4 of the CICSProblem Determination Guide for guidance on how toproceed.Module: DFHCPCBI


15/28

AAOUExplanation: CPI Communications has detected anerror in the TP_name or partner_LU_name whileprocessing an initialize conversation request. TheTP_name or partner_LU_name is obtained by lookup ofthe sym_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 thedata from the PRT and interprets it.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: A level 2 trace for CP of thetransaction shows the course of events prior to thiserror, for example, the modules called and theirparameters. The level 2 trace also provides details ofthe error itself.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Module: DFHCPCBI

AAOVExplanation: CPI Communications has detected thatits internal state table is corrupted.This error is detected by the CPI Communications statemachine.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This is a CICS internal logic error.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.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem Determination

Guide for guidance on how to proceed.Module: DFHCPCFS

AAOWExplanation: CPI Communications has detected aninternal logic error in DFHCPCLC.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This is a CICS internal logic error.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.You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Module: DFHCPCLC

AAOXExplanation: CPI Communications has detected a badsyncpoint return code which has been set on asynclevel 0 or 1 conversation. The bad return code isonly expected on a synclevel 2 conversation.


16/28

System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This is a CICS internal logic error.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.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Module: DFHCPIC

AAOYExplanation: CPI Communications detected an invalidLL field in the GDS records from which it wasreceiving on a mapped conversation.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.

System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Use CICS traces and, possibly aVTAM trace, to determine the data that was sentbetween both systems.A level 2 CICS trace for CP of the transactiondocuments the course of events prior to this error (suchas the modules called and their parameters). The level2 trace also provides details of the error itself.You may need further assistance from IBM to fullyresolve this problem. You need further assistance fromIBM to resolve this problem. See Part 4 of the CICSProblem Determination Guide for guidance on how toproceed.Module: DFHCPCRB

AAOZExplanation: CPI Communications has detected aninvalid ID field in the GDS records it was receiving ona mapped conversation. The exception trace point thataccompanies this abend gives the ID field in data 3.The valid IDs are 12FFX for application data and12F1X for null data.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Use CICS traces and, possibly, aVTAM trace to determine the data that was sentbetween both systems.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 level2 trace also provides details of the error itself.You may need further assistance from IBM to fullyresolve this problem. You need further assistance fromIBM to resolve this problem. See Part 4 of the CICSProblem Determination Guide for guidance on how toproceed.Module: DFHCPCRB


17/28

AAO2Explanation: CPI Communications has detected anunexpected response from DFHLUC.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: This is a CICS internal logic error.A level 2 CICS trace for CP of the transactiondocuments the course of events prior to this error (suchas the modules called and their parameters). The level2 trace also provides details of the error itself.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.Module: DFHCPCBA

AAO3Explanation: The CPI interface detected that a call wasmade to a CPI Communications function without CPICommunications being initialized. This implies that CPICommunications initialization failed while CICS was

initializing.System Action: The transaction is abnormallyterminated with a CICS transaction dump. Anexception trace entry is also written when this eventoccurs.User Response: Check the console listing to determinethe reason why CPI Communications failed to initializeduring CICS initialization. Correct the problem andrestart 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.You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.

Module: DFHCPI

AAO4

Explanation: DFHZARL, or a module called byDFHZARL, has detected a logic error. This error isalmost certainly caused by the module receiving invaliddata or indicators from VTAM.System Action: Before returning to the CPICommunications layer, DFHZARL calls DFHZNAC toclean up the session and put out messages on theCSNE log. CPI Communications abnormally terminatesthe transaction with a CICS transaction dump, andproduces an exception trace entry.

User Response: Check the CSNE log to determine thetype of error. You may need further assistance fromIBM to fully resolve this problem. You need furtherassistance from IBM to resolve this problem. See Part 4of the CICS Problem Determination Guide for guidanceon how to proceed.Module: DFHCPCLR

AAO5


18/28

Explanation: The task was purged before a GETMAINrequest to the storage manager (SM) domain was ableto complete successfully. The domain that first detectedthe purged condition provides an exception trace.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Investigate the reason why the taskwas purged. It was purged either by the masterterminal operator or as a result of deadlock timeout.Modules: DFHCPCBA, DFHCPCBI, DFHCPCBS

AAO7Explanation: The CPI Communications syncpointrequest handler has been passed an invalid DFHLUCparameter list. This is a CICS internal logic error.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: A level 2 trace for CP of thetransaction shows the course of events before this erroroccurred (such as the modules called and theirparameters) plus details of the error itself. You need

further assistance from IBM to resolve this problem. SeePart 4 of the CICS Problem Determination Guide forguidance on how to proceed.Module: DFHCPSRH

AAO8Explanation: The CPI Communications syncpointrequest handler has been passed an invalidconversation control block (CPC). This is a CICSinternal logic error.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: A level 2 trace for CP of thetransaction shows the course of events before this error

occurred (such as the modules called and theirparameters) plus details of the error itself. You needfurther assistance from IBM to resolve this problem. SeePart 4 of the CICS Problem Determination Guide forguidance on how to proceed.Module: DFHCPSRH

AAO9Explanation: A task has been purged either as a resultof a purge from the master terminal operator via theCEMT transaction, or by the task being timed out afterwaiting for longer than the DTIMOUT (deadlocktimeout) value specified for the transaction.System Action: The task is abnormally terminated

with a CICS transaction dump.User Response: Investigate why the task was purged.If the task was purged by the master 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 result ofthe DTIMOUT value being exceeded, this may be dueto insufficient main storage being available for thenumber of tasks in the system. If the amount of mainstorage cannot be increased, the number of tasks in thesystem should be reduced to avoid short-on-storage


19/28

situations. Another possibility would be to increase thevalue of the DTIMOUT option for the transaction.Module: DFHCPCLRAbend codes ABxx

ABACExplanation: An activity issued EXEC CICS RETURN(without the ENDACTIVITY option) but no eventswere processed during the activation. The activity wasexecuted with a RUN command.System Action: The task is abnormally terminatedwith a CICS transaction dump. The EXEC CICSHANDLE ABEND command cannot handle this abend.User Response: Investigate why the activity did notprocess any events.Module(s): DFHBASP

ABADExplanation: An activity issued EXEC CICS RETURNENDACTIVITY while there were activity completionevents pending. The activity was executed with a RUNcommand.System Action: The task is abnormally terminatedwith a CICS transaction dump. The EXEC CICSHANDLE ABEND command cannot handle this abend.User Response: Investigate why the activity hadpending activity completion events.Module(s): DFHBASP

ABAEExplanation: An activity issued EXEC CICS RETURN(without the ENDACTIVITY option) but no eventswere processed during the activation. The activity wasexecuted with a LINK command.System Action: The task which issued the LINK isabnormally terminated with a CICS transaction dump.The EXEC CICS HANDLE ABEND command cannothandle this abend.User Response: Investigate why the activity did notprocess any events.Module(s): DFHEIBAM

ABAFExplanation: An activity issued EXEC CICS RETURNENDACTIVITY while there were activity completionevents pending. The activity was executed with a LINKcommand.System Action: The task which issued the LINK isabnormally terminated with a CICS transaction dump.The EXEC CICS HANDLE ABEND command cannothandle this abend.User Response: Investigate why the activity had


20/28

pending activity completion events.Module(s): DFHEIBAM

ABLAExplanation: The task was purged before a GETMAINrequest to the storage manager (SM) domain was ableto complete successfully. The domain that first detectedthe purged condition provides an exception trace.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Investigate why the task was purged.It was purged either by the master terminal operator oras a result of deadlock timeout.If the task was purged by the master 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 result ofthe DTIMOUT value being exceeded, this may be dueto insufficient main storage being available for the

number of tasks in the system. If the amount of mainstorage cannot be increased, the number of tasks in thesystem should be reduced to avoid short-on-storagesituations. Another possibility would be to increase thevalue of the DTIMOUT option for the transaction.Modules: DFHMCP, DFHMCPE, DFHM32, DFHPBP,DFHRLR

ABLBExplanation: An error (INVALID, DISASTER, orunexpected EXCEPTION response) has occurred on acall to the storage manager (SM) domain. The domain

that detected the original error provides an exceptiontrace, a console message and, possibly, a system dump(depending on the options in the dump table).System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Please see the related messageproduced by the domain that originally detected theerror.Modules: DFHMCP, DFHMCPE, DFHM32, DFHPBP,DFHRLR

ABMA

Explanation: The user has supplied a terminal I/Oarea (TIOA) with an invalid data length that was eitherequal to zero or greater than the storage accountinglength minus 12.Alternatively, the length field of a header or trailer areaprovided by the application program is invalid (that is,not positive).Problem Determination: The output services workarea (OSPWA) is in user storage and will be printed ina transaction dump. It is addressed by register 2 at thetime of the abend. Relevant fields are:


21/28

v OSPTR7Chapter 3. Transaction abend codes 1143v OSPHDRAv OSPTRLARegister 4 or OSPTIOA points to the TIOA. In theTIOA, the following fields are relevant:v TIOATDLv TIOASALAnalysis:Register Label DescriptionR4=@TIOA PBCKTDL TIOATDL is zero or greaterthan TIOASAL-12.R2=@OSPWA PBD20080 R0 (= first halfword ofR0=length trailer) is zero.of trailer R8=OSPTRLA.R8=@trailer OSPTR7 has X20 bit set.R2=@OSPWA PBDTXHDR R0 (= first halfword ofR8=@header header) is zero.R0=length R8=OSPHDRA.of header. OSPTR7 has X40 bit set.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Correct the program that supplied the

erroneous data length.Check the TIOA. If either of the conditions described ispresent, check the application program. For programsusing command-level interface, the TIOA is obtained byCICS using the length of the data item passed in theFROM option on an EXEC CICS SEND MAP or EXECCICS SEND TEXT command, or in the TRAILER orHEADER option on an EXEC CICS SEND TEXT or anEXEC CICS SEND PAGE command. Check the dataitem for zero length.Header and trailer records have a special formatdescribed in the CICS Application Programming Reference.An ABMA abend occurs if the first halfword (thelength) is not positive. Check the remainder of theheader/trailer record for validity when the length ischecked.

Modules: DFHPBP, DFHMCP

ABMBExplanation: The user has specified a cursor positionin the BMS output request. It is larger than the currentscreen size for the 3270 for which output is being built.Problem Determination: If the abend occurs inDFHPBP:At the time of the abend, register 2 points to theOSPWA and register 1 to the TTP. Relevant fields are:v OSPTR3 has X10 bit set to indicate a user-specifiedcursor position

v OSPCP contains a halfword cursor position specifiedby userv TTPSCSZ contains the halfword value of the screensize to compare against.If the abend occurs in DFHMCP or DFHMCX:v Register 6 points to the OSPWA (in LIFO storage)v OSPCP contains a halfword cursor position specifiedby userv OSPTR3 has X10 bit set to indicate a user-specifiedcursor positionv OSPSCSZ contains the halfword value of the screen


22/28

size to compare against.Analysis:Register Label DescriptionIn DFHPBP:R2=@OSPWA PBDBADC OSPTR3 X10 bit setindicates the user-R1=@TTP specified cursorposition.TTPSCSZ halfword screensize.OSPCP halfword cursorposition.In DFHKCP or DFHMCX:R6=@OSPWA MCENEAU2 OSPTR3 X10 bit setindicates the userspecifiedcursorposition.OSPSCSZ halfword screensize.OSPCP halfword cursorposition.System Action: The transaction is abnormallyterminated with a CICS transaction dump.

User Response: Correct the program that specified theincorrect cursor location.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 theprogram 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 size ofthe smallest screen.Modules: DFHPBP, DFHMCP (for minimum-functionBMS), DFHMCX

ABMCExplanation: The CMSG transaction is attempting tosend a message to a greater number of terminals thanis possible. There is no fixed maximum because thevalue depends on the other operands specified on therouting command.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Redefine the route list.Module: DFHMCP

ABMDExplanation: DFHTPR or DFHTPP has issued aDFHDI TYPE=SEND and has received a return codeother than FUNCERR-REQUEST FOR CHANGEDIRECTION SIGNALED or NORESPSystem Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Inform your system programmer.Modules: DFHTPP, DFHTPR


23/28

ABMEExplanation: DFHTPR or DFHTPP has detected aninvalid datastream or DFHWBBMS detected invalidforms data while processing a basic mapping support(BMS) request.System Action: The transaction is abnormallyterminated with a CICS transaction dump. If the

ABEND was issued from DFHTPR or DFHTPP thenregister 7 indicates the location at which the ABENDwas detected.User Response: If DFHTPR or DFHTPP issued the

ABEND then examine the transaction dump for baddata in the TIOA. If the origin of the bad data is anapplication program, correct the program. If

DFHWBBMS issued the ABEND then check the validityof the incoming forms data in the CICS trace.Modules: DFHTPP, DFHTPR, DFHWBBMS

ABMFExplanation: The value specified for the length optionof the basic mapping support (BMS) send map isgreater than the length of the from area.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Redefine the value for the lengthoption.

Module: DFHPBP

ABMGExplanation: The user has requested a basic mappingsupport (BMS) service that was not specified at systemgeneration, or at initialization.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Correlate services requested againstoptions specified in the system generation of BMS.Follow this procedure:1. Scan the trace table for the transaction ID that

issued the abend. If this is CSPQ (page cleanup),module DFHTPQ abnormally terminated because amessage purge delay of zero has been specified andCSPQ has been entered via a terminal. The messagepurge delay is specified in the PRGDLAY of theDFHSIT macro, and its value can be found inSITPRGD.2. Scan the trace table for the last BMS request (codeFA). Use the option bytes at the start of the failingmodule to see if the requested functions have beengenerated. For example, paging may have been


24/28

requested, 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:DFHMCPDFHRLRDFHPBPDFHTPPModules: DFHMCP, DFHTPQ

ABMIExplanation: The map specified for a BMS inputmapping request was not an input map.

System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Either define another input map orredefine the existing map.Modules: DFHMCP, DFHMCX, DFHMCY

ABMLExplanation: The terminal control locate routinereceived invalid data from DFHRLR and returns withan error return code. DFHRLR is attempting to scan theTCT for a BMS ROUTE request with LIST=ALL oroperator class or operator ID specified in the route list.

The terminal control table may have been corrupted.Problem Determination: Register 11 points to thecurrent 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 TCTTEto the next.Chapter 3. Transaction abend codes 1145Analysis: The current TCTTE address is either not on afull-word boundary or is not within the limits of theTCT, or the address of the next TCTTE, obtained byadding TCTTETEL to the current address, is invalid.This check is made by locate code (DFHZLOC) inDFHZCX.

Register Label DescriptionR11=@TCTTE RLRLOCN Issue DFHTC CTYPE=LOCATESystem Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.The terminal control table has probably been corruptedduring execution. Attempt to scan through the TCT in adump. (Because the system dump uses the sametechnique for printing all TCTTEs, the system dump


25/28

fails at the same point.)Determine which entry is incorrect. It may be that theTCTTE 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 by someearlier transaction. If this is so, it is probably oneassociated with the terminal whose TCTTE isoverwritten.Modules: DFHRLR for full-function BMS

ABMMExplanation: An invalid map was specified.System Action: The transaction is abnormallyterminated with a CICS transaction dump.

User Response: Use the supplied dump to diagnosethe problem. Register 6 contains the address of the BMSinstruction being executed when the error wasrecognized.Module: DFHPBP

ABMOExplanation: The map specified for a BMS outputmapping request was not an output map.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Either define another output map or

redefine the existing map.Modules: DFHMCP, DFHMCX, DFHMCY

ABMQExplanation: The query transaction (CQRY) has beeninitiated and either the task is not terminal-oriented, orthe associated 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 ofa keyboard/printer device. The CQRY transaction doesnot have an operator interface, and under normal

conditions 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 TCTTE forthe associated terminal. If register 8 contains zero, thisindicates that the task is not terminal-oriented.System Action: The task is abnormally terminatedwith a CICS dump.User Response: Ensure that the terminal associatedwith CQRY is of the 3270 or SCSPRINT family of


26/28

devices.Module: DFHQRY

ABMRExplanation: The Page Retrieval transaction (CSPG)has been initiated but the task is not terminal-oriented.System Action: The task is abnormally terminatedwith a CICS dump.User Response: Ensure that a terminal is associatedwith the CSPG transaction.Module: DFHTPR

ABMUExplanation: The application program supplied anaddress that is not within region boundaries. Thelow-order 3 bytes of general register 1 in thetransaction dump contain the erroneous address. Thehigh-order byte of register 1 indicates 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)System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Correct the application program thatis supplying the erroneous address.Modules: DFHMCP, DFHEMS

ABMVExplanation: DFHRLR has detected an invalid routelist entry.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Check that the route list is correctlybuilt with reserved field in the entry containing blankand a stopper of halfword XFFFF to terminate the list.Module: DFHRLR

ABMXExplanation: A text string passed to BMS contained aset attribute order that was invalid for one of thefollowing reasons:1. The set attribute sequence was less than three

characters.2. The attribute type was invalid.System Action: The task is abnormally terminatedwith a CICS transaction dump.User Response: Correct the application program.Module: DFHPBP

ABMYExplanation: BMS is building a TTP (Terminal TypeParameter) control block but the pagesize selected for a


27/28


28/28

@TCTTETE The device dependent suffixand the map set suffix haveloaded into the lower twobytes of register 3 by thesubroutine RLRSUFXS.System Action: The transaction is abnormallyterminated with a CICS transaction dump.User Response: Do not use terminals not supportedby BMS for applications using BMS services.Check the terminal type and model number. Confirmthat it is a terminal that is not supported by BMS. A listof terminals supported by BMS is given in the CICSApplication Programming Guide. Check that the TCTChapter 3. Transaction abend codes 1147macro for the terminal accurately describes the physicalterminal.Module: DFHRLR

ABM2Explanation: No user data was supplied for this BMSrequest. That is, the address of a user data area was notfound in either TCTTEDA or TCAMSIOA.

When a BMS macro level output request is issued, theuser must have placed the address of the data to bepassed to BMS in TCTTEDA or TCAMSIOA beforeissuing the macro.Module: DFHMCP

ABM3Explanation: A BMS input or output request has beenissued from a task that is not terminal-oriented.System Action: The task is abnormally terminatedwith a CICS dump.User Response: The task issuing a BMS input oroutput request must be attached to a terminal.Module: DFHMCP

ABM4Explanation: An invalid request response has beenreceived to a temporary storage PUT or PUTQ requestissued by BMS. The data passed to the temporarystorage program has an invalid length.Problem Determination: Abend in DFHMCP (seeAnalysis)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 register 8at the time of the abend. The first 8 bytes containstorage accounting information. MCRLLBB contains thelength of the MCR (halfword) abend in DFHTPP.

CICS ABENDS

Documents

Transcript of CICS ABENDS