Abend codes ADxx

ADCA
Explanation:

This abend is issued if DBCTL returns a non-zero response code when a DL/I request has been issued from an application program.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Look up accompanying message DFHDB8109 that appears on the CDBC transient data destination.

Modules:

DFHDLIDP

ADCB
Explanation:

This abend occurs when DBCTL has notified CICS that a task has issued a DL/I request, but it did not have a PSB scheduled. If your application does have a PSB scheduled then a possible cause for this abend is that the DBCTL STOP THREAD command may have been used to terminate the DBCTL thread that corresponds to this task.

System action:

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User response:

Check if the DBCTL operator has issued a STOP THREAD command for the task that has abnormally terminated. Look up DBCTL response code 28 in the DBCTL return code section of the IMS™ Messages and Codes manual.

Modules:

DFHDLIDP

ADCC
Explanation:

This abend occurs when DBCTL has notified CICS that a task has issued program specification block (PSB) request, but it has a PSB already scheduled. CICS prevents a task from issuing a PSB schedule request to DBCTL when it has already issued a PSB schedule request by returning a PSBSCH response in UIBDLTR. However, in this case it is DBCTL that has rejected the subsequent PSB schedule request. A possible cause for this abend is a storage over-write.

System action:

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User response:

Check for any messages issued from your CICS system indicating that storage over-writes have taken place. Look up DBCTL response code 32 in the DBCTL return code section of the IMS Messages and Codes manual.

Modules:

DFHDLIDP

Start of change
ADCD
Explanation:

This abend is issued when a deadlock has been detected by IMS and this transaction has been selected for abnormal termination.

This abend can occur when a transaction is accessing IMS resources via DBCTL or via a remote DLI request to a remote CICS region. The remote CICS region can be accessing IMS via DBCTL, or if it is a CICS 4.1 region or earlier, accessing IMS via local DLI.

System action:

Access to IMS resources via DBCTL is withdrawn for this transaction. Further attempts to access IMS will result in an AEY9 abend.

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User response:

If ADCD abends occur infrequently in your system, no action is required although you may like to consider setting your system up in such a way that, after an ADCD abend is issued, the transaction is automatically restarted. See the CICS® Recovery and Restart Guide for further information.

If ADCD abends are occurring frequently in your system, you may need to review the design of your applications. Some general techniques for deadlock avoidance are described in the CICS Recovery and Restart Guide.

Modules:

DFHDLIDP

End of change
ADCE
Explanation:

This abend is issued when the module DFHDBAT returns a nonzero return code in reply to a DL/I request issued from an application program to DBCTL. DFHDBAT is a task related user exit and forms part of the CICS-DBCTL interface. This abend is accompanied by message DFHDB8110.

System action:

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User response:

Look up the accompanying message DFHDB8110 that appears on the CDBC transient data destination.

Modules:

DFHDLIDP

Start of change
ADCF
Explanation:

This abend is issued when the module DFHDLIDP detects that the CICS-DBCTL interface has been configured using a DRA startup table (DFSPZPxx) which specifies option PCBLOC-31, and the application is amode 24.

PCBLOC=31 specifies that the PCB address list and PCBs can be stored above the line. This is incompatible with amode 24 applications.

System action:

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User response:

Linkedit the application amode 31, or change the DRA startup table option to PCBLOC=24.

Modules:

DFHDLIDP

End of change
Start of change
ADCI
Explanation:

This abend is issued when IMS returns a user abend 3303 response for a DL/I request issued from an application program.

System action:

Access to IMS resources via DBCTL is withdrawn for this transaction. Further attempts to access IMS will result in an AEY9 abend.

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User response:

Check the description in the IMS Messages and Codes manual for the meaning of IMS user abend 3303.

Modules:

DFHDLIDP

End of change
ADCJ
Explanation:

This abend is issued when an application has been using DBCTL, and while the application was still scheduled to DBCTL, the CICS-DBCTL interface was terminated.

System action:

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User response:

Check the CDBC transient data destination for messages indicating the reason for termination of the CICS-DBCTL interface. If you do not know where the CDBC transient is, then please check with your system programmer. Check for messages issued from the DBCTL system.

Modules:

DFHDLIDP

ADCP
Explanation:

When checking the DBCTL program specification block (PSB), the external security manager checked the usage of the PSB, and found that:

The meaning of the term "user" in the above context depends on the way the transaction was invoked.

Notes.

By the above definitions, a PSB used by a routed transaction has two users, the terminal user and the communicating region. Therefore, for routed transactions, the external security manager makes two checks, on the terminal user (as qualified in 1 above), and on the communicating region (2 or 3 above).

System action:

CICS abnormally terminates the task attempting to schedule the PSB. CICS processing continues.

User response:

Ensure that the PSB is defined to the external security manager, and that all users have the correct level of authorization. If the system setup is correct, note the security violation.

Modules:

DFHDLIDP

ADCQ
Explanation:

This abend occurs when an application has issued an EXEC DLI SCHD request for a PSB that contains no DBPCBs, and the SYSSERVE keyword was not specified. This abend also occurs when an application has issued a PCB request for a PSB that contains no DBPCBs, and the IOPCB option was not specified.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Check that the application program has scheduled the appropriate PSB.

Modules:

DFHDLIDP

ADCR
Explanation:

This abend occurs when an application has issued a DL/I request other than a schedule request, and the DBCTL DRA return code of 40 indicates that there was no active communication with DBCTL.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Check the CDBC transient data destination for messages indicating the reason for termination of the CICS-DBCTL interface. If you do not know where the CDBC transient data destination is, check with your system programmer. Check for messages issued from the DBCTL system.

Modules:

DFHDLIDP

ADCS
Explanation:

CICS issued a single-phase commit request to DBCTL and an unexpected response was returned from DBCTL.

System action:

CICS issues message DFHDB8119 to transient data queue CDBC, then terminates the task abnormally with a CICS transaction dump.

User response:

Message DFHDB8119 shows the unexpected response from DBCTL, along with the recovery token of the LUW involved. The explanation of message DFHDB8119 indicates how the outcome of the LUW can be determined.

Modules:

DFHDBAT

ADCT
Explanation:

A user has attempted to invoke the CICS-DBCTL control transaction from a terminal.

System action:

CICS rejects the request.

User response:

Do not try to invoke CICS internal transactions directly.

Modules:

DFHDBCT

ADCV
Explanation:

The connection to DBCTL was terminated and then re-established. The failing task had issued a schedule request against an earlier run of DBCTL and is therefore no longer scheduled.

System action:

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User response:

No action is required, although you may like to consider setting your system up in such a way that, after an abend ADCV is issued, the transaction is automatically restarted.

Modules:

DFHDLIDP

ADDA
Explanation:

An error (INVALID or DISASTER response) has occurred on a call to the storage manager domain. The domain that detected the original error provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User response:

See related message from the domain that detected the original error.

Modules:

DFHDBME, DFHDLI, DFHDLIDP

ADDB
Explanation:

An error (INVALID or DISASTER response) has occurred on a call to the catalog (CC) domain. The domain that detected the original error provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User response:

See related message from the domain that detected the original error.

Modules:

DFHDBCON, DFHDBDSC

ADDC
Explanation:

An error (INVALID or DISASTER response) has occurred on a call to the loader (LD) domain. The domain that detected the original error will have provided an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User response:

See related message from the domain that detected the original error.

Modules:

DFHDBCON, DFHDBDI

ADDI
Explanation:

CICS has been notified of a DBCTL failure. However, it has been unable to complete the search for a DBCTL alternate. This is possibly due to an unexpected return code from an IEFSSREQ request.

System action:

A CICS transaction dump is produced. CICS continues as if no XRF DBCTL alternate has been found. This abend is accompanied by message DFHDX8323.

User response:

Refer to message DFHDX8323 for further information. It may be necessary to restart DBCTL manually.

Modules:

DFHDBCT

ADDJ
Explanation:

CICS has failed to connect to DBCTL because program DFHDBAT could not be ENABLED.

System action:

A CICS transaction dump is produced. The state of the CICS/DBCTL interface remains not connected.

User response:

Refer to the transaction dump to determine why the ENABLE failed.

Modules:

DFHDBCON

ADEF
Explanation:

A severe error has been encountered when executing transaction CLS3.

System action:

CLS3 is abnormally terminated with a transaction dump. CICS issues message DFHZC4948.

User response:

See message DFHZC4948 for further guidance.

Modules:

DFHCLS3

ADIR
Explanation:

The abend code is issued for either of the following reasons:

System action:

A CICS transaction dump is provided to assist in problem determination.

User response:

Either generate a DFHDIP program into the system or specify INBFMH correctly on the profile definition.

Modules:

DFHDIP

ADLE
Explanation:

A DL/I request was made for a remote database, but the system named in the remote PDIR entry was unknown to CICS, that is, not specified in a DFHTCT TYPE=SYSTEM macro or CEDA DEFINE CONNECTION command.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Either correct the SYSIDNT parameter in the relevant DFHDLPSB entry, or define the remote system to CICS with a DFHTCT TYPE=SYSTEM macro or a CEDA DEFINE CONNECTION command.

Modules:

DFHDLIRP

ADLF
Explanation:

A DL/I request was made for a remote database, but the link to the system on which the database resides was down.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Notify the system programmer. Once the link to the remote system has been reestablished, resubmit the transaction.

Modules:

DFHDLIRP

ADLG
Explanation:

A DL/I request was made for a remote database, but there were errors in the DL/I argument list that was provided by the user.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Ensure that any errors in the DL/I argument are corrected.

Modules:

DFHDLIRP

ADLP
Explanation:

When checking the DLI program specification block (PSB), the external security manager checked the usage of the PSB, and found that:

The meaning of the term "user" in the above context depends on the way the transaction was invoked.

Note:
By the above definitions, a PSB used by a routed transaction has two users, the terminal user and the communicating region. Therefore, for routed transactions, the external security manager makes two checks, on the terminal user (as qualified in 1 above), and on the communicating region (2 or 3 above).
System action:

The task attempting to schedule the PSB abnormally terminates.

User response:

Ensure that the PSB is defined to the external security manager, and that all users have the correct level of authorization. If the system setup is correct, note the security violation.

Modules:

DFHDLIRP

ADMA
Explanation:

The alternate CICS task responsible for tracking the DBCTL connection status of the active CICS has received an error from the CICS Availability Manager (CAVM) message input service.

System action:

The tracking transaction terminates with a CICS transaction dump. No further action is taken in response to DBCTL status changes. The global exits, XXDFB and XXDTO, are never invoked and no attempt at a DBCTL restart is made in the event of a takeover. This abend is accompanied by DFHDX8331.

User response:

Check for any other messages relating the CAVM dataset problems. In the event of a takeover, it may be necessary to restart DBCTL manually.

Modules:

DFHDBCR

ADMB
Explanation:

The CICS/XRF DBCTL tracking task has received an unrecognizable message from the CICS/XRF message manager. This abend is preceded by message DFHDX8333.

System action:

The CICS/XRF DBCTL tracking task abends.

User response:

Refer to the instructions for message DFHDX8333.

Modules:

DFHDBCR.

Start of change
ADMD
Explanation:

The alternate CICS system task responsible for tracking the DBCTL connection status of the active CICS has been unable to complete its search for a DBCTL alternate, possibly due to an unexpected return code from an IEFSSREQ request.

System action:

A CICS transaction dump is produced. The tracking transaction continues as if no DBCTL alternate had been found. This abend is accompanied by message DFHDX8335.

User response:

Refer to message DFHDX8335 for further information. It may be necessary to restart DBCTL manually.

Modules:

DFHDBCR.

End of change
ADPA
Explanation:

The CICS supplied transaction for managing debugging profiles, CADP, has received a exception response from the file manager, with reason file error. The file manager will have issued a message to the CICS joblog containing a code which indicates the precise nature of the error. For example this abend will be issued if the underlying file DFHDPFMB used by CADP is disabled or doesn't exist.

System action:

CICS abends the transaction with a transaction dump.

User response:

Examine the CICS joblog for associated messages, correct the problem and retry the CADP transaction.

Modules:

DFHDPLU

ADPB
Explanation:

The CICS supplied transaction for managing debugging profiles, CADP, has received a disaster response from the file manager, with reason internal error. There is an error in the file manager program.

System action:

CICS abends the transaction with a transaction dump.

User response:

Examine the CICS joblog for associated messages. Contact IBM for assistance with this type of error.

Modules:

DFHDPLU

ADPC
Explanation:

The CICS supplied transaction for managing debugging profiles, CADP, has received a disaster response from the file manager, with reason disaster percolation. There is an error in one of the CICS domains called by the file manager.

System action:

CICS abends the transaction with a transaction dump.

User response:

Examine the CICS joblog for associated messages. Contact IBM for assistance with this type of error.

Modules:

DFHDPLU

ADPD
Explanation:

The CICS supplied transaction for managing debugging profiles, CADP, has received a purged response from the file manager. reason disaster precolation. It is likely that an underlying request to CICS File Control has timed out because the record that CADP is trying to access, is held up by another transaction. For example this would occur if CECI was bing used to access the underlying file, DFHDPFMB, at the same time as using CADP.

System action:

CICS abends the transaction with a transaction dump.

User response:

Investigate if there are other tasks running against the file used by CADP.

Modules:

DFHDPLU

ADPI
Explanation:

The CICS supplied program for inactivating all debugging profiles, DFHDPIN, has received a exception response from the file manager, with reason file error. The file manager will have issued a message to the CICS joblog containing a code which indicates the precise nature of the error. For example this abend will be issued if the underlying file DFHDPFMB used by CADP was disabled or deleted whilst DFHDPIN was running.

System action:

CICS abends the transaction with a transaction dump.

User response:

Examine the CICS joblog for associated messages, correct the problem and retry the CADP transaction.

Modules:

DFHDPIN

ADPL
Explanation:

A server program has issued a command which is restricted in the distributed program link (DPL) environment. Certain API and CPI-RR requests, and the DL/I terminate request are not allowed in the DPL environment. See the CICS Application Programming Guide for a list of these restricted commands.

A server program is a program which has been remotely linked, or a program defined to run with the DPL subset.

System action:

CICS abends the transaction with a transaction dump.

User response:

Remove the restricted commands from the server program, or run the server program locally.

Modules:

DFHEIP, DFHCPIR, DFHDLI

ADXA
Explanation:

The XRF DBCTL state catch-up transaction, DXCU, has failed.

System action:

DXCU is abnormally terminated with a CICS transaction dump. This abend is accompanied by DFHDX8319.

User response:

Diagnose the error from the CICS transaction dump. Refer to DFHDX8319 for further information.

Modules:

DFHDXCU

ADXB
Explanation:

The XRF DBCTL state catch-up transaction, DXCU, has failed.

System action:

DXCU is abnormally terminated with a CICS transaction dump. This abend is accompanied by DFHDX8318.

User response:

Use the dump to help diagnose the problem. Refer to DFHDX8318 for further information. Check for any other messages relating to CICS availability manager (CAVM) data set problems.

Modules:

DFHDXCU

AD2A
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a LOCK call to the lock manager (LM) domain. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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:

DFHD2EX1

AD2B
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an UNLOCK call to the lock manager (LM) domain. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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:

DFHD2EX1

AD2C
Explanation:

An unexpected EXCEPTION response has occurred on a locate call to directory manager (DD) domain to locate a DB2TRAN control block. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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:

DFHD2EX1

AD2D
Explanation:

An error (INVALID or DISASTER response ) has occurred on a locate call to directory manager (DD) domain to locate a DB2TRAN control block. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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:

DFHD2EX1

AD2E
Explanation:

An unexpected EXCEPTION response has occurred on a locate call to directory manager (DD) domain to locate a DB2ENTRY control block. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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:

DFHD2EX1

AD2F
Explanation:

An error (INVALID or DISASTER response ) has occurred on a locate call to directory manager (DD) domain to locate a DB2ENTRY control block A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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:

DFHD2EX1

AD2G
Explanation:

A transaction attempted to use a DB2ENTRY that is DISABLED or is DISABLING. The DISABLEDACT attribute of the DB2ENTRY specified ABEND meaning that new transactions that attempt to use the DB2ENTRY should be abended.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use CEMT INQ DB2TRAN TRANSID(tttt) where tttt is the transid, to determine the name of the DB2ENTRY involved. Re-enable the DB2ENTRY or discard the DB2ENTRY so that the transid will use a pool thread.

Modules:

DFHD2EX1

AD2H
Explanation:

The CICS-DB2 attachment facility detected that a dynamic plan exit program abended.

System action:

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

User response:

See the associated DFHDB2050 transient data message to determine the abend code with which the dynamic plan exit program abended. Determine why the exit program abended.

Modules:

DFHD2EX1

AD2I
Explanation:

The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because it was not link edited AMODE 31.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the associated DFHDB2051 transient data message to determine the name of the dynamic plan exit program involved. Re-linkedit the dynamic plan exit program AMODE 31.

Modules:

DFHD2EX1

AD2J
Explanation:

The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because it is disabled.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the associated DFHDB2053 transient data message to determine the name of the dynamic plan exit program involved. Enable the dynamic plan exit program.

Modules:

DFHD2EX1

AD2K
Explanation:

The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because no program definition was found.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the associated DFHDB2057 transient data message to determine the name of the dynamic plan exit program involved. Ensure that the dynamic plan exit program has been correctly defined to CICS.

Modules:

DFHD2EX1

AD2L
Explanation:

The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because the program could not be loaded.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the associated DFHDB2058 transient data message to determine the name of the dynamic plan exit program involved. Ensure that the dynamic plan exit program has been correctly defined and is in a load library accessible to CICS.

Modules:

DFHD2EX1

AD2M
Explanation:

The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because the program is defined as remote.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the associated DFHDB2066 transient data message to determine the name of the dynamic plan exit program involved. Correct the program definition for the dynamic plan exit program so that it is defined as local.

Modules:

DFHD2EX1

AD2N
Explanation:

The CICS-DB2 attachment facility failed to link to a dynamic plan exit program.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the associated DFHDB2054 transient data message to determine the name of the dynamic plan exit program involved. Examine the transaction dump to determine why the link failed.

Modules:

DFHD2EX1

AD2O
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an WAIT_MVS call to the dispatcher (DS) domain. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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:

DFHD2EX1

AD2P
Explanation:

The transaction was unable to obtain a DB2 thread from a DB2ENTRY or the pool. See the associated transient data message DFHDB2011 to determine which DB2ENTRY was involved or whether it was the pool. The transaction was abended because the DB2ENTRY or the pool specified threadwait(no) meaning do not wait for a thread if all threads are currently in use. Note if message DFHDB2011 indicates that the pool was being used, it means the transaction was using the pool directly rather than overflowing to the pool. (An abend AD3T is produced when a transaction overflows to the pool and no pool threads are available.)

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Determine whether more threads should be allocated to the DB2ENTRY or the pool, or whether the number of instances of this transaction should be limited using TRANCLASS.

Modules:

DFHD2EX1

AD2Q
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an getmain call to the storage manager (SM) domain. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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:

DFHD2EX1

Start of change
AD2R
Explanation:

The CICS-DB2 thread TCB processing the DB2 request for this transaction has abended. An exception trace (AP 319D) is written containing the MVS abend code and reason code as well as the relevant CICS-DB2 control blocks used by the CICS task and the CICS-DB2 thread TCB. In particular the CSUB control block contains data from the MVS SDWA at the time of the abend, for example fields CSB_SDWA_REGS (regs 0 -15) and CSB_SDWA_PSW.

The thread TCB is terminated if a CICS transaction is forcepurged from CICS and the thread is still active in DB2.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the trace in the CICS transaction dump to determine why the CICS-DB2 thread TCB abended.

Modules:

DFHD2EX1

End of change
Start of change
AD2S
Explanation:

The thread TCB servicing the DB2 request for the transaction issued a sign-on request to DB2 which failed. The installed DB2CONN specifies THREADERROR(N906D) or THREADERROR(ABEND).

System action:

If THREADERROR(N906D) is specified in the DB2CONN, processing continues. A -906 sqlcode is returned to the application, and a transaction dump is taken with abend code AD2S.

If THREADERROR(ABEND) is specified in the DB2CONN, the task is abnormally terminated with a CICS transaction dump.

User response:

Examine the AUTHID or AUTHTYPE parameter of the DB2ENTRY or pool used for the transaction. Ensure the id is authorised to access the plan in DB2.

Modules:

DFHD2EX1

End of change
Start of change
AD2T
Explanation:

An attempt to create a DB2 thread by the TCB servicing the DB2 request for the transaction failed with DB2 reason code 00F30040. The installed DB2CONN specifies THREADERROR(N906D) or THREADERROR(ABEND).

System action:

If THREADERROR(N906D) is specified in the DB2CONN, processing continues. A -906 sqlcode is returned to the application and a transaction dump is taken with abend code AD2T.

If THREADERROR(ABEND) is specified in the DB2CONN, the task is abnormally terminated with a CICS transaction dump.

User response:

Either the plan is unavailable or is not known to DB2.

Modules:

DFHD2EX1

End of change
Start of change
AD2U
Explanation:

An attempt to create a DB2 thread by the TCB servicing the DB2 request failed. The installed DB2CONN specifies THREADERROR(N906D) or THREADERROR(ABEND).

System action:

If THREADERROR(N906D) is specified in the DB2CONN, processing continues. A -906 sqlcode is returned to the application and a transaction dump is taken with abend code AD2U.

If THREADERROR(ABEND) is specified in the DB2CONN, the task is abnormally terminated with a CICS transaction dump.

User response:

Examine the dump to determine why the create thread failed.

Modules:

DFHD2EX1

End of change
AD2V
Explanation:

Start of changeThe CICS-DB2 attachment facility issued a commit or abort request to DB2 but received a reason code 00F30805 indicating that connection toEnd of change DB2 has been lost. This is due to DB2 terminating abnormally or being in the process of terminating abnormally. Start of changeIf the commit or abort request was preceded by a prepare request, DB2 may well still be indoubt. In this case, the CICS-DB2 attachment facility instructs CICS to remember the outcome of the UOW pending resynchronisation, which will happen when CICS and DB2 are reconnected. For an abort request not preceded by a prepare, i.e. a transaction abend or syncpoint rollback, DB2 will not be indoubt as the UOW was still inflight. DB2 will backout updates made by the UOW when restarted so there is no need for CICS to remember the outcome of the UOW.End of change

System action:

The transaction completes normally but a transaction dump is taken with abend code AD2V. If DB2 is indoubt about the outcome of the UOW it will be resolved when CICS and DB2 are reconnected.

User response:

Contact your system programmer to restart the DB2 subsystem.

Modules:

DFHD2EX1

AD2W
Explanation:

The CICS-DB2 attachment facility issued a single-phase commit call to DB2 but received an unexpected response. Transient data message DFHDB2055 details the DB2 reason code received. The commit request may have been processed or it may have been ended. There is no resynchronisation needed, as no CICS recoverable resources were updated.

System action:

The CICS-DB2 attachment facility abnormally terminates the transaction with abend code AD2W. The CICS recovery manager will supersede the AD2W abend code with abend code ASPR. A transaction dump is taken.

User response:

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

Modules:

DFHD2EX1

Start of change
AD2X
Explanation:

The CICS-DB2 attachment facility detected that the CICS task and the thread TCB were in an invalid state. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The task is abnormally terminated with a 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:

DFHD2EX1

End of change
Start of change
AD2Y
Explanation:

The transaction was unable to obtain a DB2 thread from a DB2ENTRY or the pool because there were no TCBs available on which to create the thread. The number of thread TCBs currently running is at the TCBLIMIT defined in the DB2CONN. Message DFHDB2010 is output to transient data. The transaction was abended because either:

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Determine whether TCBLIMIT should be increased or whether the number of transactions using DB2 at any one instance should be limited using transaction classes.

Modules:

DFHD2EX1

End of change
AD2Z
Explanation:

DB2 detected a deadlock and the CICS-DB2 attachment facility attempted a syncpoint rollback command for the transaction as DROLLBACK(YES) was specified for the DB2ENTRY or POOL. The syncpoint rollback command failed. Message DFHDB2070 is output to transient data detailing the transid involved and the EIBRESP2 from the failed syncpoint rollback command.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Examine the eibresp2 value to determine why the syncpoint rollback request failed. One possible reason could be that the transaction running is a DPL server transaction which was DPLed to by a client transaction without specifying the SYNCONRETURN parameter. In this case syncpoints, or syncpoint rollbacks, cannot be taken by the server transaction, so DROLLBACK(YES) is invalid in this case.

Modules:

DFHD2EX1

AD21
Explanation:

The CICS-DB2 attachment facility received a request for a resource manager with the incorrect name. Message DFHDB2045 is output to transient data detailing the invalid name.

System action:

The transaction is abnormally terminated with a 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:

DFHD2EX1

AD22
Explanation:

The CICS-DB2 attachment facility EDF processor was unable to interpret the SQL request.

System action:

The command is not interpreted by EDF. A CICS transaction dump is taken with abend code AD22.

User response:

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

Modules:

DFHD2EDF

AD23
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a LOCK call to the lock manager (LM) domain made by the CICS-DB2 attachment facility service transaction CEX2. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The CICS-DB2 service task initiates a force shutdown of the CICS-DB2 interface.

User response:

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

Modules:

DFHD2EX2

AD24
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an UNLOCK call to the lock manager (LM) domain made by the CICS-DB2 attachment facility service transaction CEX2. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The CICS-DB2 Service task initiates a force shutdown of the CICS-DB2 interface.

User response:

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

Modules:

DFHD2EX2

AD25
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a LOCK call to the lock manager (LM) domain made by the CICS-DB2 attachment facility while processing a DSNC command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DSNC command fails and the transaction is abnormally terminated with a 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:

DFHD2CC

AD26
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an UNLOCK call to the lock manager (LM) domain made by the CICS-DB2 attachment facility while processing a DSNC command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DSNC command fails and the transaction is abnormally terminated with a 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:

DFHD2CC

Start of change
AD27
Explanation:

The CICS-DB2 attachment facility attempted to attach a TCB on which a DB2 thread was to be created to service the SQL request from the application. The attach of the TCB failed due to lack of storage.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Increase the size of the CICS region or lower the TCBLIMIT value specified in the DB2CONN.

Modules:

DFHD2EX1

End of change
Start of change
AD28
Explanation:

The CICS-DB2 attachment facility attempted to attach a TCB on which a DB2 thread was to be created to service the SQL request from the application. The attach of the TCB failed.

System action:

The transaction is abnormally terminated with a 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:

DFHD2EX1

End of change
AD29
Explanation:

The CICS-DB2 attachment facility was unable to link to its EDF processor DFHD2EDF.

System action:

The command is not interpreted by EDF. Message DFHDB2048 is output to transient data and a transaction dump is taken with abend code AD29.

User response:

Examine the trace in the CICS transaction dump to determine why the link to module DFHD2EDF failed.

Modules:

DFHD2EDF

AD3A
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a LOCK call to the lock manager (LM) domain made by the CICS-DB2 attachment facility startup program. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

Startup of the CICS-DB2 interface is terminated, and the interface is closed. 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:

DFHD2STR

AD3B
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an UNLOCK call to the lock manager (LM) domain made by the CICS-DB2 Attachment facility startup program. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

Startup of the CICS-DB2 interface is terminated, and the interface is closed. 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:

DFHD2STR

Start of change
AD3C
Explanation:

An error (INVALID, DISASTER response) has occurred on a CONNECT_TO_DB2 function call to the CICS-DB2 Coordinator program DFHD2CO made by the CICS-DB2 Attachment facility startup program. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

Startup of the CICS-DB2 interface is terminated, and the interface is closed. 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:

DFHD2STR

End of change
AD3D
Explanation:

An unexpected response was received while attempting to delete a record from a temporary storage queue during processing of a DSNC STRT command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DSNC STRT command fails. 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:

DFHD2CM1

Start of change
AD3E
Explanation:

During processing of a DB2 request for the transaction, an identify request was made to identify the calling TCB to DB2. The identify request failed. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DB2 request fails. The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the exception trace in the dump to determine why the identify request failed. The CSUB control block is output as part of the exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The identify request contains eyecatcher "IDEN" and is followed by the DB2 FRB response and reason codes.

Modules:

DFHD2D2

End of change
Start of change
AD3F
Explanation:

During processing of a DB2 request for the transaction, a terminate thread request was made to DB2 which failed. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DB2 request fails. The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the exception trace in the dump to determine why the terminate thread request failed. The CSUB control block is output as part of the exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The terminate thread request contains eyecatcher "TERM" and is followed by the DB2 FRB response and reason codes.

Modules:

DFHD2D2

End of change
AD3G
Explanation:

An unexpected response was received from an EXEC CICS GETMAIN issued during processing of a CICS-DB2 DSNC command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DSNC command fails. 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:

DFHD2CM1

AD3H call.
Explanation:

The issuing of an EXEC SQL command or IFI call from a Dynamic Plan Exit is not allowed.

System action:

The task is abnormally terminated.

User response:

Remove any EXEC SQL commands or IFI calls from the Dynamic Plan Exit.

Modules:

DFHD2EX1

AD3I
Explanation:

An unexpected response was received from an EXEC CICS INQUIRE DB2CONN command issued during startup of the CICS-DB2 interface. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

Startup of the CICS-DB2 interface is terminated, and the interface is closed. 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:

DFHD2CM1

Start of change
AD3J
Explanation:

A commit request to DB2, issued during the second phase of syncpoint, failed. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump. CICS maintains a record that the UOW committed pending a future resynchronization request with DB2.

User response:

Examine the exception trace in the dump to determine why the commit request failed. The CSUB control block is output as part of the exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The commit request contains eyecatcher "COMM" and is followed by the DB2 FRB response and reason codes.

Modules:

DFHD2D2

End of change
Start of change
AD3K
Explanation:

An abort request to DB2, issued during the second phase of syncpoint, failed. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump. CICS maintains a record that the UOW backed out pending a future resynchronization request with DB2.

User response:

Examine the exception trace in the dump to determine why the abort request failed. The CSUB control block is output as part of the exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The abort request contains eyecatcher "ABRT" and is followed by the DB2 FRB response and reason codes.

Modules:

DFHD2D2

End of change
Start of change
AD3L
Explanation:

During processing of a DB2 request for the transaction, an associate request was made to associate the DB2 connection with the calling TCB. The associate request failed. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DB2 request fails. The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the exception trace in the dump to determine why the associate request failed. The CSUB control block is output as part of the exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The associate request contains eyecatcher "ASSO" and is followed by the DB2 FRB response and reason codes.

Modules:

DFHD2D2

End of change
AD3M
Explanation:

An unexpected error occurred during processing of a DSNC MODIFY command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DSNC MODIFY command fails. 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:

DFHD2CM1

AD3P
Explanation:

An unexpected error occurred during processing of a DSNC STOP command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DSNC STOP command fails. 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:

DFHD2CM1

AD3Q
Explanation:

An unexpected response was received while attempting to read a record from a temporary storage queue during processing of a DSNC STRT command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DSNC STRT command fails. 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:

DFHD2CM1

AD3R
Explanation:

An unexpected response was received while attempting to read a record from a temporary storage queue during startup of the CICS-DB2 interface. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

Startup of the CICS-DB2 interface is terminated, the interface is closed. 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:

DFHD2STR

AD3S
Explanation:

An unexpected response was received from an EXEC CICS SET DB2CONN command issued during startup of the CICS-DB2 interface. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

Startup of the CICS-DB2 interface is terminated, and the interface is closed. 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:

DFHD2CM1

AD3T
Explanation:

The transaction was unable to obtain a DB2 thread from the pool. Message DFHDB2011 is output to transient data. The transaction was abended because the transaction tried using a DB2ENTRY but all threads were in use on the DB2ENTRY, and despite threadwait(pool) being specified, all threads in the pool were also in use. The pool definition within the DB2CONN specifies threadwait(no).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Determine whether more threads should be allocated to the DB2ENTRY or the pool, or whether the number of instances of this transaction should be limited using TRANCLASS.

Modules:

DFHD2EX1

Start of change
AD3U
Explanation:

An error (INVALID or DISASTER response ) has occurred on a locate call to transaction manager (XM) domain to locate a transaction definition. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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:

DFHD2EX1

End of change
AD3W
Explanation:

An unexpected response was received while attempting to write a record to a temporary storage queue during startup of the CICS-DB2 interface. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

Startup of the CICS-DB2 interface is terminated, and the interface is closed. 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:

DFHD2STR

AD3X
Explanation:

An unexpected response was received while attempting to write a record to a temporary storage queue during processing of a DSNC STRT command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System action:

The DSNC STRT command fails. 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:

DFHD2CM1

Start of change
AD3Z
Explanation:

The CICS-DB2 thread TCB processing the DB2 request for this transaction has abended because the DB2 adapter is being shutdown.

System action:

The task is abnormally terminated.

User response:

If this abend should occur at CICS or DB2 shutdown then it can be ignored, because the DB2 adapter is abending the task as part of shutdown processing, otherwise you will need assistance from IBM.

Modules:

DFHD2EX1

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