Abend codes AAxx

AACA
Explanation:

An invalid error code has been passed to the DFHTFP or DFHACP programs.

System action:

CICS terminates the task abnormally with a dump.

User response:

Notify the system programmer.

Modules:

DFHTFP,DFHACP

AALM
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the log manager (LM) domain. The domain that detected 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 by the domain that detected the original error.

Modules:

DFHAMLM

AALN
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the TD manager. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMTD

Start of change
AALO
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the CICS/DB2 table manager DFHD2TM. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMD2

End of change
Start of change
AALP
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Program Manager. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMPG

End of change
Start of change
AALQ
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Business Application Manager. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMBA

End of change
Start of change
AALR
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Temporary Storage Manager. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMBA

End of change
Start of change
AALS
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Global Enqueue Manager. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMBA

End of change
Start of change
AALT
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Internet Inter-Orb Protocol Manager. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMOP

End of change
Start of change
AALU
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Sockets Domain Manager. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMSO

End of change
Start of change
AALV
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Enterprise Java Domain. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMEJ

End of change
Start of change
AALW
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Web Domain. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMWB

End of change
Start of change
AALX
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Pipeline Manager. The domain that detected the original error provides a trace entry 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:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMPI

End of change
Start of change
AAL1
Explanation:

DFHALP was processing a request that deadlocked. The most likely reason for the abend is that an ALLOCATE QUEUE request has been suspended because there are no contention-winning links available.

AAL1 is issued for non time-out related deadlocks, for instance 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 enough contention-winning sessions available to satisfy the ALLOCATE QUEUE request.

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

Modules:

DFHALP

End of change
Start of change
AAL2
Explanation:

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

System action:

The transaction is abnormally terminated with a dump.

User response:

Check the return code from the resume or the suspend to determine the cause of the error.

Modules:

DFHALP

End of change
Start of change
AAL3
Explanation:

The task has been purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The task that first detected the purged condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate the reason why the task was purged. It was purged either by the master terminal operator or as a result of a deadlock timeout.

Modules:

DFHALP

End of change
Start of change
AAL4
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the storage manager (SM) domain. The domain that detected 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 by the domain that detected the original error.

Modules:

DFHALP

End of change
Start of change
AAL6
Explanation:

An error (INVALID, DISASTER or EXCEPTION response) has occurred on a call to SIGNOFF_TERMINAL_USER by DFHALP during sign-off for a surrogate terminal session running CRTE. The domain that detected 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 by the domain that detected the original error.

Modules:

DFHALP

End of change
Start of change
AAL7
Explanation:

An error (INVALID, DISASTER or EXCEPTION response) has occurred on a call to schedule a remote terminal delete by DFHALP during sign-off for a surrogate terminal session running CRTE. The domain that detected 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 by the domain that detected the original error.

Modules:

DFHALP

End of change
Start of change
AAL8
Explanation:

DFHALP was processing a request that deadlocked. The most likely reason for the abend is that an ALLOCATE QUEUE request has been suspended because there are no contention-winning links 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 the transaction dump table has been modified for AAL8.

User response:

Ensure that there are enough contention-winning sessions available to satisfy the ALLOCATE QUEUE request.

If you are running with modegroups, ensure that there are 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 this abend from recurring.

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

Modules:

DFHALP

End of change
Start of change
AAMA
Explanation:

There is an internal logic error in DFHAMP.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAMC
Explanation:

The task was purged before a GETMAIN request to the storage manager domain was able to complete successfully.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate the reason the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Modules:

DFHAMP

End of change
Start of change
AAMD
Explanation:

An unexpected return code has been received from DFHDMP. This is due to an internal logic error.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAMF
Explanation:

An unexpected return code has been received following a call to the kernel (KE) domain. This might be due to an internal logic error.

System action:

CICS terminates the task abnormally with a dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAMH
Explanation:

An unexpected return code has been received following a call to DFHFCMT. This might be due to an internal logic error.

System action:

CICS terminates the task abnormally with a dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAMI
Explanation:

An unexpected return code has been received following a call to DFHFCRL. This might be due to an internal logic error.

System action:

CICS terminates the task abnormally with a dump. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

User response:

Modules:

DFHAMP

End of change
Start of change
AAMJ
Explanation:

While installing a file, using RDO, a call was made to DFHFCFS to enable the file. An irrecoverable error was returned from DFHFCFS.

System action:

The task is abnormally terminated with a CICS transaction dump.

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

User response:

Inform the system programmer. Examine the trace and the dump to identify the point of error.

Modules:

DFHAMP

End of change
Start of change
AAMK
Explanation:

While installing a file, using RDO, a call was made to DFHFCDN. An irrecoverable error was returned from DFHFCDN.

System action:

The task is abnormally terminated with a CICS transaction dump. At the time the error is detected, CICS writes a message to the console, records an exception trace entry, and takes a system dump.

User response:

Inform the system programmer, Examine the trace and dump to identify the point of error.

Modules:

DFHAMP

End of change
Start of change
AAMN
Explanation:

There has been an unexpected return code from a call to DFHPRPT. This might be due to an internal logic error.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAMO
Explanation:

An invalid return code was returned from DFHTOR, the CICS terminal object resolution program.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAMP
Explanation:

An unexpected return code has been received from DFHPUP. This might be due to an internal logic error.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAMQ
Explanation:

An attempt has been made to install a partner using RDO. However, the partner resource manager (PRM) is unavailable having failed to initialize during CICS initialization.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

If you need to use the PRM, correct the problem which prevented the PRM from initializing, and restart CICS.

Modules:

DFHAMP

End of change
Start of change
AAMS
Explanation:

There has been an unexpected return code following a GETMAIN request to the storage manager. This is due to an internal logic error.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAMT
Explanation:

There is an internal logic error in DFHAMP due to an unexpected return code from DFHTMP.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAMZ
Explanation:

An unexpected return code has been received from DFHZCP. This is due to an internal logic error.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMP

End of change
Start of change
AAM1
Explanation:

DFHXMCL has returned an unexpected response during the install of a transaction class. This can be caused by the task being purged during the install.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

If an error has occurred, at the time the error is detected, CICS issues a DFHXMnnnn console message, records an exception trace entry and takes a system dump.

User response:

Determine why the task has failed. If there 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 purged either by the master terminal operator or as a result of deadlock timeout.

Modules:

DFHAMP

End of change
Start of change
AAM2
Explanation:

DFHXMXD has returned an unexpected response during the install of a transaction definition. This can be caused by the task being purged during the install.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

If an error has occurred, at the time the error is detected, CICS issues a DFHXMnnnn console message, records an exception trace entry and takes a system dump.

User response:

Determine why the task has failed. If there 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 purged either by the master terminal operator or as a result of deadlock timeout.

Modules:

DFHAMP

End of change
Start of change
AAOA
Explanation:

An application has issued a CPI verb which CICS does not support. The entry point referenced in the application program was resolved in the link edit stub, but the function requested could not be resolved when control passed to CICS.

There are two possible reasons for this:

System action:

The transaction is abnormally terminated with a CICS transaction dump. An exception trace entry is also written.

User response:

At the time of the error, general register 0 points to an 8-byte character string which should match the name of the issued CPI call. Use the trace or the dump to verify that this character string is the name of a CPI function which is supported.

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

Modules:

DFHCPI

End of change
Start of change
AAOB
Explanation:

An application has issued a CPI verb which specifies more than eight parameters.

System action:

The transaction is abnormally terminated with a CICS transaction dump and an exception trace entry is also written.

User response:

Change your application program so that the correct number of parameters is specified on the CPI call.

Modules:

DFHCPI

End of change
Start of change
AAOC
Explanation:

CPI Communications is invoked with an invalid number of parameters for call

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

The exception trace point produced with this abend contains the incorrectly issued CPI Communications verb name. Use this to determine where the application program was in error and amend it accordingly.

The SAA CPI Communications Reference manual, SC26-4399, provides a detailed description of all the CPI Communications verbs and how they should be called.

Modules:

DFHCPARH

End of change
Start of change
AAOD
Explanation:

The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The domain that first detected the purged condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate the reason the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Modules:

DFHCPCBI

End of change
Start of change
AAOE
Explanation:

The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The domain that first detected the purged condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate the reason the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Modules:

DFHCPCBA

End of change
Start of change
AAOF
Explanation:

The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The domain that first detected the purged condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate the reason the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Modules:

DFHCPCBS

End of change
Start of change
AAOG
Explanation:

During the processing of CMACCP (accept conversation), CPI Communications detected that the application was attached with an unsupported sync level.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

This condition is caused by a back-end CPI Communications transaction being attached with a sync level that is not CM_NONE (0) or CM_CONFIRM (1).

Change the front-end transaction, (that is, the initiator of the conversation in the other system) so that it defines the sync level correctly.

Modules:

DFHCPCBA

End of change
Start of change
AAOH
Explanation:

Journaling of data sent on a CPI communications mapped conversation has failed. This condition is caused by a nonzero response from the CICS log manager.

Problem determination:

Register 12 addresses the current TCA and field TCAJCAAD and register 4 address the JCA. The log manager request is contained in JCATR2 and the response code is in JCAJCRC.

Possible request codes are:

X'8001' - WRITE
X'8003' - PUT

Possible response codes are:

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

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

Analysis:

Register  Label     Description
 
R4=@JCA   TCZARQPJ  JCAJCRC is nonzero.
System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Use the dump to ascertain why the journal or log record could not be written correctly. If a journal record length error is indicated, TIOATDL may have been corrupted.

Modules:

DFHCPCOJ

End of changeStart of change
AAOI
Explanation:

The journaling of data received on a CPI Communications mapped conversation has failed.

Problem determination:

Register 12 addresses the current TCA and field TCAJCAAD and register 4 address the JCA. The CICS log manager request is contained in JCATR2 and the response code is in JCAJCRC.

Possible request codes are:

X'8001' - WRITE
X'8003' - PUT

Possible response codes are:

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

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

Analysis:

Register  Label     Description
 
R4=@JCA   TCZARQPJ  JCAJCRC is nonzero.
System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

This condition is caused by an invalid response from the log manager. Use the dump to ascertain why the journal or log record could not be written correctly. If a journal record length error is indicated, TIOATDL may have been corrupted.

Modules:

DFHCPCRI, DFHCPCRW

End of changeStart of change
AAOJ
Explanation:

CPI Communications has detected an unexpected response from one of its internal routines.

System action:

The transaction is abnormally 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 the course of events prior to this error. For example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPIC

AAOK
Explanation:

CPI Communications has detected an unexpected call to one of its internal routines.

System action:

The transaction is abnormally 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 the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPIC

AAOL
Explanation:

CPI Communications has made an invalid call to DFHLUC.

System action:

The transaction is abnormally 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 the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCLR

End of changeStart of change
AAOM
Explanation:

The CPI Communications and the DFHZUSR state machines are out of synchronization.

System action:

The transaction is abnormally 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 the course of events prior to this error. For example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCLR, DFHCPSRH

AAON
Explanation:

CPI Communications has detected an unexpected response from DFHLUC.

System action:

The transaction is abnormally 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 the course of events prior to this error. For example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCLR, DFHCPCLC

End of changeStart of change
AAOO
Explanation:

CPI Communications has been invoked with an invalid first parameter. The first parameter should be the code of the function to be performed. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

A level 2 trace for ‘CP’ of the transaction shows the course of events before this error occurred (such as the modules called and their parameters) plus details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPARH

AAOP
Explanation:

The CPI Communications state machine has been requested to perform a state transition request that 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:

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

A level 2 trace for ‘CP’ of the transaction shows the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

The transaction dump shows the CPC. You may need further assistance from IBM to fully resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCFS

AAOQ
Explanation:

The return code generated by CPI Communications does not have an entry in the state table against the current CPI Communications verb. This error is detected by the CPI Communications state machine.

System action:

The transaction is abnormally 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 the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCFS

AAOR
Explanation:

CPI Communications has detected an invalid value in the CPC (conversation control block).

There are 2 possible causes of this error:

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

A level 2 trace for ‘CP’ of the transaction shows the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

Modules:

DFHCPIC

AAOS
Explanation:

CPI Communications has detected that the conversation state is RESET for a situation where this should not occur. That is, the conversation control block (CPC) is about to be deleted.

There are two possible causes of this error:

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

A level 2 trace for ‘CP’ of the transaction shows the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself. You may need further assistance from IBM to fully resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPIC

AAOT
Explanation:

While chaining through the CPCs (conversation control blocks) for a given conversation, CPI Communications detected that the chain was broken.

There are two possible causes of this error.

  1. The CPC chain has been overwritten, or
  2. There is an error in the CPI Communications chaining mechanism.
System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Determine which of the above caused the error.

A level 2 trace for ‘CP’ of the transaction shows the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You may need further assistance from IBM to fully resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCBI

AAOU
Explanation:

CPI Communications has detected an error in the TP_name or partner_LU_name while processing an initialize conversation request. The TP_name or partner_LU_name is obtained by lookup of the 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, or
  2. There is an error in the mechanism that returns the data from the PRT and interprets it.
System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

A level 2 trace for ‘CP’ of the transaction shows the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCBI

AAOV
Explanation:

CPI Communications has detected that its internal state table is corrupted.

This error is detected by the CPI Communications state machine.

System action:

The transaction is abnormally 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 the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCFS

AAOW
Explanation:

CPI Communications has detected an internal logic error in DFHCPCLC.

System action:

The transaction is abnormally 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 the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCLC

AAOX
Explanation:

CPI Communications has detected a bad syncpoint return code which has been set on a synclevel 0 or 1 conversation. The bad return code is only expected on a synclevel 2 conversation.

System action:

The transaction is abnormally 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 the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPIC

AAOY
Explanation:

CPI Communications detected an invalid LL field in the GDS records from which it was receiving on a mapped conversation.

Although it is possible that the remote system is sending invalid records, it is more likely to be an error in the receive logic because DFHZARRC (a lower level receive module) also checks the LLs before passing them to CPI Communications.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Use CICS traces and, possibly a VTAM trace, to determine the data that was sent between both systems.

A level 2 CICS trace for ‘CP’ of the transaction documents 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 error itself.

You may need further assistance from IBM to fully resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCRB

AAOZ
Explanation:

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

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Use CICS traces and, possibly, a VTAM trace to determine the data that was sent between both systems.

A level 2 CICS trace for ‘CP’ of the transaction documents 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 error itself.

You may need further assistance from IBM to fully resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCRB

AAO2
Explanation:

CPI Communications has detected an unexpected response from DFHLUC.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

This is a CICS internal logic error.

A level 2 CICS trace for ‘CP’ of the transaction documents 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 error itself.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCBA

AAO3
Explanation:

The CPI interface detected that a call was made to a CPI Communications function without CPI Communications being initialized. This implies that CPI Communications initialization failed while CICS was initializing.

System action:

The transaction is abnormally terminated with a CICS transaction dump. An exception trace entry is also written when this event occurs.

User response:

Check the console listing to determine the reason why CPI Communications failed to initialize during CICS initialization. Correct the problem and restart CICS.

If the console listing indicates that CPI Communications initialized successfully, you need further assistance to resolve the problem. Collect the console listing, the traces and the transaction dump. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPI

AAO4
Explanation:

DFHZARL, or a module called by DFHZARL, has detected a logic error. This error is almost certainly caused by the module receiving invalid data or indicators from VTAM.

System action:

Before returning to the CPI Communications layer, DFHZARL calls DFHZNAC to clean up the session and put out messages on the CSNE log. CPI Communications abnormally terminates the transaction with a CICS transaction dump, and produces an exception trace entry.

User response:

Check the CSNE log to determine the type of error. You may need further assistance from IBM to fully resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPCLR

End of changeStart of change
AAO5
Explanation:

The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The domain that first detected the purged condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate the reason why the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Modules:

DFHCPCBA, DFHCPCBI, DFHCPCBS

End of changeStart of change
AAO7
Explanation:

The CPI Communications syncpoint request handler has been passed an invalid DFHLUC parameter list. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

A level 2 trace for ‘CP’ of the transaction shows the course of events before this error occurred (such as the modules called and their parameters) plus details of the error itself. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPSRH

AAO8
Explanation:

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

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

A level 2 trace for ‘CP’ of the transaction shows the course of events before this error occurred (such as the modules called and their parameters) plus details of the error itself. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPSRH

AAO9
Explanation:

A task has been purged either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) 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 system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, the number of tasks in the system should be reduced to avoid short-on-storage situations. Another possibility would be to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHCPCLR

End of change [[ Contents Previous Page | Next Page Index ]]