The system was in a final quiesce mode when the CICS application program issued a DFHTC macro.
The task requesting the I/O is abnormally terminated with a CICS transaction dump.
None.
DFHZARQ
The CICS application program issued two consecutive DFHTC writes or two consecutive DFHTC reads, but in either case did not issue an intervening wait.
A transaction dump is provided with this abend. In the dump, register 12 addresses the current TCA, and register 10 and the field TCAFCAAA address the TCTTE associated with this task. In TCATPOS2, bit TCATPOWR (X'01') indicates that a write is requested by the DFHTC macro, and bit TCATPORR (X'10') indicates that a read is requested. In TCTTEOS, bit TCTTEOWR (X'01') indicates that a write is in progress, and bit TCTTEORR (X'10') indicates that a read is in progress.
Analysis:
Register Label Description
R10=@TCTTE TCZARQ05 Bit TCATPOWR is on in byte
R12=@TCA (TCZAQ1W) TCATPOS2, and bit TCTTEOWR
is on in byte TCTTEOS.
R10=@TCTTE TCZARQ05 Bit TCATPOWR is on in byte
R12=@TCA (TCZAQ2W) TCATPOS2, and bit TCTTEORR
is on in byte TCTTEOS.
R10=@TCTTE TCZARQ12 Bit TCATPORR is on in byte
R12=@TCA TCATPOS2, and bit TCTTEORR
is on in byte TCTTEOS.
The transaction is abnormally terminated with a CICS transaction dump.
Take corrective action within the program being executed.
This is almost certainly an application program error. Determine the flow of control through the application and determine why an intervening wait is not issued. The trace table may be useful to discover where the application is issuing the read and write requests. If necessary, start trace or auxiliary trace using the master terminal command and rerun the transaction to obtain a trace. The output of the auxiliary trace can be printed using the trace utility program, DFHTU640.
DFHZARQ
An application program, using a pipeline session, has either issued more than one write request or issued a read request.
The transaction is abnormally terminated with a CICS transaction dump.
Correct the application program so that it will not issue more than one consecutive WRITE to a pipeline session terminal.
DFHZARQ
This abend code is used whenever a CTYPE request or a QUEUE request is issued and VTAM or a ZCP function has not been included in the system.
It is also used to abend a task that issues an APPC command when the CICS system is not at a level to support APPC.
The transaction is abnormally terminated with a CICS transaction dump.
Correct the transaction so that it does not issue a CTYPE macro instruction if VTAM is not generated into the system, or include the ZCP function for which the CTYPE or QUEUE request was issued.
DFHZDSP, DFHZERH
A CICS application program has issued a DFHTC request without specifying the address of a TIOA, but the request is not an ERASE ALL UNPROTECTED or a READBUF request for a 3270 data stream terminal.
A transaction dump is provided with this abend. In the dump, register 12 addresses the current TCA, and register 10 and the field TCAFCAAA addresses the TCTTE associated with this task. Register 8 and TCTTEDA should contain the address of the TIOA to be used in the I/O request, but actually they contain zero. For a 3270 data stream terminal, byte TCTETDST has bit TCTETTSI (X'01') set. An erase-all-unprotected request is indicated by the setting of bit TCTTEEUI (X'40') in byte TCTTEEUB, and a read buffer request is indicated by the setting of bit TCTTERBI (X'80') in byte TCTTERBB. Analysis:
Register Label Description
R10=@TCTTE TCZARQ41 NIOABAR (register 8)
contains zero.
R8=0 Register 8 has been loaded
field TCTTEDA of the TCTTE
associated with this task.
The transaction is abnormally terminated with a CICS transaction dump.
Correct the error in the user program by ensuring that a terminal input/output area (TIOA) is provided at write time.
This is almost certainly an application program error. Determine the flow of control through the application and determine why a TIOA has not been specified.
DFHZARQ
A DFHTC CTYPE macro was issued to a non-VTAM terminal control table terminal entry (TCTTE), or a DFHTC CTYPE=COMMAND or RESPONSE macro was issued to a VTAM 3270 TCTTE.
The transaction is abnormally terminated with a CICS transaction dump.
Ensure that the program issues CTYPE macros to VTAM terminals only, and does not issue CTYPE=COMMAND or RESPONSE to a VTAM 3270.
DFHZCRQ
A CICS application program has issued a DFHTC request for a terminal that it does not own. The problem of ownership may be because the task previously issued a WRITE,LAST request (which would have detached the terminal from that task) or because the task incorrectly specified the terminal to which the request is directed.
Register 12 addresses the current TCA and register 10 contains the address of the TCTTE. The address of the TCTTE was obtained either from TCAFCAAA in the case of a non-ISC transaction, or from TCATPTA if bit TCATPTTA (X'40') is on in byte TCATPOC3 (this indicates that TERM=YES was specified on the DFHTC request and that this is an ISC transaction). In the TCTTE thus located, the field TCTTECA does not contain the address of the TCA, indicating that this TCA is not owned by this task.
Analysis: A DFHTC request has been issued specifying a TCTTE in which the field TCTTECA does not contain the address of the TCA.
Register Label Description
R10=@TCTTE TCZARQ05 TCTTECA is not equal
to register 12.
The transaction is abnormally terminated with a CICS transaction dump.
This is most probably an application error (unless storage has been completely overwritten). Determine the flow from the trace table and when a request to the DFHZCP detach routine, DFHZDET, or a DFHTC WRITE,LAST was issued.
DFHZARQ
The task was purged before a domain call was able to complete successfully. The task that first detected the purged condition provides an exception trace.
The task is abnormally terminated with a CICS transaction dump.
Investigate why the task was purged. It was 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, or by CICS issuing a purge request.
If the master terminal operator purged the task, 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, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.
When CICS purges a task, it does so to allow an operation to complete which would be held up by the presence of active tasks, or to ensure data integrity. For example, CICS will purge a task which has made recoverable updates to a coupling facility data table if it determines that the coupling facility data table server for the pool in which that table resides has recycled, to ensure that all updates in the unit of work will be backed out.
DFHBSM62 DFHBSS DFHBSSZ DFHBSTZ DFHBSTZV DFHBSTZ1 DFHBSTZ2 DFHTBSB DFHTBSBP DFHTBSD DFHTBSDP DFHTBSL DFHTBSLP DFHTBSQ DFHTBSR DFHTBSRP DFHTBSSP DFHTCRP DFHTOASE DFHTOATM DFHTOLCR DFHTOLUI DFHTRZCP DFHTRZIP DFHTRZPP DFHTRZXP DFHTRZYP DFHTRZZP DFHZCQCH DFHZCQDL DFHZCQIQ DFHZCQIS DFHZCQRS DFHZCQ00 DFHMRXM DFH62XM
An error (INVALID, DISASTER, or unexpected EXCEPTION response) has occurred on a call to module DFHRTSU. The module 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).
The task is abnormally terminated with a CICS transaction dump.
See the related message produced by the module that detected the original error.
DFHZSUP DFHMRXM DFH62XM
This abend is issued by DFHZATA in the following circumstances:
This abend is issued by DFHZATD in the following circumstances:
This abend is issued by DFHZATR in the following circumstances:
CICS rejects the request.
Determine the issuing program and the reason for the abend and take the appropriate action as follows:
Do not try to invoke CATA, CATD or CATR from a terminal.
If the address in TCAFCAAA is incorrect, the calling mechanism has failed. This is a CICS logic error.
If an abend has been issued, use the transaction dump to determine where the abend occurred. This is a CICS logic error.
DFHZATA DFHZATD DFHZATR
An application program has issued a WRITE to a VTAM terminal specifying CCOMPL=NO without being authorized to do so.
The transaction is abnormally terminated with a CICS transaction dump.
Specify CHAINCONTROL in the transaction profile.
DFHZARQ
An error has occurred either during automatic journaling or automatic logging of terminal messages to or from this transaction. The message being logged will be one associated with an explicit READ or WRITE in the application program.
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.
The transaction is abnormally terminated with a CICS transaction dump.
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.
DFHETL, DFHTCPCM, DFHZARQ
An error has occurred during the automatic journaling or automatic logging of the initial input message of this transaction. This input message is the message that actually caused the transaction to be invoked.
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.
Analysis:
Register Label Description
R4=@JCA TCZARQJP JCAJCRC is nonzero.
TCZSUPJW Journal error.
The transaction is abnormally terminated with a CICS transaction dump.
Use the dump to ascertain why the log record could not be written correctly.
If a journal record length error is indicated, TIOATDL (X'08') may have been corrupted.
DFHZSUP DFH62XM DFHTFXM
An application program has attempted to perform a function not supported by a terminal or system.
Possible errors are:
A DFHTC TYPE=SIGNAL request with the WAIT=YES option was issued to a VTAM logical unit that CICS does not support for the receipt of the SIGNAL indicator.
This write may have been attempted as a result of a SEND command with the STRFIELD keyword to a device that does not support this function.
The application has attempted to perform a normal terminal control command on a session that is in use for an APPC unmapped conversation. (Only EXEC CICS GDS commands are permitted.)
The transaction is abnormally terminated with a CICS transaction dump.
Correct the application program.
DFHZARQ
The application program issued a write operation to a terminal that was in send status. In order to allow this write to proceed, a signal command was sent, and DFHZCP started to read data from the terminal waiting for the change direction indication. As each data record is received, it is placed on temporary storage and, for one of these operations, a temporary storage error has occurred.
Register 12 addresses the current TCA. TCACCSV1 contains a saved copy of TCATSTR containing the temporary storage response code. The temporary storage response code may be one of:
X'04' - IOERROR - I/O error
X'08' - NOSPACE - No temporary storage space
X'20' - INVREQ - Invalid request.
The temporary storage identification is constructed by concatenating the character string "DFHQ" with the terminal identification from TCTTETI. The temporary storage identification is placed in TCATSDI.
Register 8 and field TCTTEDA address the TIOA that is being written to temporary storage. The address passed to temporary storage is that of TIOATDL.
Analysis: After the DFHTS TYPE=PUTQ, the temporary storage response code was not zero.
Register Label Description
R12=@TCA ZRAQ60 TCATSTR is nonzero.
The transaction is abnormally terminated with a CICS transaction dump.
Check that temporary storage has been included in the system and that it has sufficient space.
If an invalid request is indicated, check that the length of the data being written to temporary storage is not greater than the VSAM control interval size minus 84. The length of the data is in TIOATDL (which is 8 greater than the length of the data that is read in by DFHZCP).
DFHZRAQ
An application program has issued a read operation, after a previous write operation has caused DFHZCP to read-ahead data from the terminal in order to avoid a lock-out. DFHZCP has now issued a DFHTS GETQ to retrieve the saved data from temporary storage, and an error has occurred.
Register 12 addresses the current TCA. TCACCSV1 contains a saved copy of TCATSTR that contains the temporary storage response code. The temporary storage response code may be one of:
X'01' - ENERROR - Entry error
X'02' - IDERROR - Identification error
X'04' - IOERROR - I/O error
X'20' - INVREQ - Invalid request
The temporary storage identification is constructed by concatenating the character string "DFHQ" with the terminal identification from TCTTETI. The temporary storage identification is placed in TCATSDI.
Analysis: After the DFHTS TYPE=GETQ, the temporary storage response code was not zero.
Register Label Description
R12=@TCA ZRAR90 TCATSTR is not zero.
The transaction is abnormally terminated with a CICS transaction dump.
Determine the cause of the temporary storage error and correct it.
If a temporary storage identification error is indicated, examine TCTTETI for a valid terminal identification.
DFHZRAR
An application program attempted to send data to a logical unit after a SIGNAL data flow command with an RCD (request change direction) has been received. This condition arises when the application handles the IGREQCD exceptional condition incorrectly.
The transaction is abnormally terminated with a CICS transaction dump.
Handle the IGREQCD exceptional condition correctly.
DFHZARQ
An attempt to build a surrogate TCTTE to represent a remotely-owned terminal failed.
The task is abnormally terminated with a CICS transaction dump.
You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.
DFHZSUP DFHMRXM DFH62XM
An application program attempted to send data to a logical unit, but was in receive mode (EIBRECV is set), and read-ahead queuing was not specified in installed profile definition (RAQ=NO).
The transaction is abnormally terminated with a CICS transaction dump.
Either change the application program to issue receives until EIBRECV is not set, or specify RAQ=YES in the installed profile definition (If RAQ=YES is specified, ensure that all input messages are read before the transaction is terminated.)
DFHZARQ
An application attempted an operation on a logical unit, but was not in the correct mode for one of the following reasons:
Register 12 addresses the current TCA. Register 10 and field TCAFCAAA address TCTTE. The terminal byte TCTTECRE has bit TCTEUCOM (X'02') set if sync point is required, and TCTEUFRT (X'04') set if Free Session is required; TCTESMDI has TCTEUSMD (X'02') set if the application is in SEND mode. TCTERCVI has TCTEURCV (X'01') set if the application is in RECEIVE mode. Bit TCTESRAQ (X'80') in byte TCTEIRAQ indicates that read-ahead queuing is coded on the installed profile definition for this transaction.
The type-of-request bits in the TCA are set as follows:
Analysis:
Number Label Description
DFHZARQ
1. TCZAQW8 Attempting to receive
when sync point or Free
Session outstanding.
2. TCZAQ2W Attempting to send while
in receive mode.
3. ZARQNOPG Issuing SIGNAL while in
send mode.
DFHZISP
4. ZISPVTCK Attempting to free session
while sync point request is
outstanding.
The transaction is abnormally terminated with a CICS transaction dump.
The response depends on the reason for the error as follows:
The application program has attempted an operation on a logical unit that is invalid, because the program’s current status on the session with that logical unit does not permit it. An investigation of the TCTTE (that is, Session), status bytes, and TCA type of request bytes will reveal which of the above problems are relevant.
When the cause of the problem has been ascertained, the application program should be changed to ensure that the session-oriented information is acted upon before any further requests are sent across that session. The session status information is made available to the application program in the exec interface block (EIB) immediately following the execution of RECEIVE, CONVERSE, or RETRIEVE requests across the session. The relevant bytes must be tested, strictly in the order shown, and acted upon, before any further operations are attempted on the session. In addition, the status information bytes themselves are necessarily volatile in that they are reset before the execution of every EXEC CICS... statement. Thus it is good programming practice to save them into application user storage after a RECEIVE, CONVERSE, or RETRIEVE for later testing. The states are:
Some of these status tests can sometimes be omitted (for example, testing of the EIBSYNC status is not essential if it is known that the application program on the remote system never issues sync point requests itself). However, the tests should always be carried out, particularly if the remote application might be amended at a future date, in which event the session handling logic may well be altered. Also, it may be that the remote transaction itself causes an unsuspected flow on the session. For example, if the remote program issues EXEC CICS SEND..... LAST across the session, followed by RETURN, a syncpoint request (RQD2) will be added onto the transmitted data. (The application programmer is referred to the CICS Distributed Transaction Programming Guide for a discussion of this topic). As a result of this addition, an unsuspected syncpoint request is received by the local application, which abend if the session is freed without the sync point request being honored.
DFHETL, DFHZARQ, DFHZISP
The system has been generated without an installed profile definition for an LU6.1 or APPC session.
The transaction is abnormally terminated with a CICS transaction dump.
Notify the system programmer of the error.
DFHZSUP DFHMRXM DFH62XM
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).
An application program that issues terminal control requests after an ATCX abend may cause further problems.
The task is abnormally terminated with a CICS transaction dump.
See the related message produced by the domain that detected the original error.
DFHBSMIR, DFHBSMPP, DFHBSM62, DFHBSS, DFHBSTB, DFHBSTB3, DFHBSTC, DFHBSTZ, DFHBSTZB, DFHBSTZO, DFHBSTZR, DFHBSTZV, DFHBSTZ1, DFHBSTZ2, DFHBSZZS, DFHAPRT, DFHCRP, DFHQRY, DFHZARL, DFHZARQ, DFHZERH, DFHZGET, DFHZFRE, DFHZNAC, DFHZRVS, DFHZSUP, DFHMRXM, DFH62XM DFHZTSP, DFHZXST
An error has occurred during the processing of an inbound function management header (FMH). Either a length error has been detected, for example, incomplete FMH received, or an invalid field has been detected within the FMH.
The transaction is abnormally terminated with a CICS transaction dump.
Notify the system programmer of the error. The problem is probably in the remote system that has sent the invalid FMH.
If the inbound FMH is from a system with an earlier release of CICS then you may need to set USEDFLTUSER. See 'Attach Time Security and the USEDFLTUSER option' in chapter 12 of the CICS RACF® Security Guide.
DFHZARQ, DFHZSUP DFHMRXM DFH62XM
An error (INVALID, DISASTER or EXCEPTION response) has occurred on the SET_NETWORK_IDENTIFIER call to the security domain as part of opening the CICS VTAM ACB (for example, EXEC CICS SET VTAM OPEN or CEMT SET VTAM OPEN). The domain that detected the original error provides an exception trace, a console message, and depending on the options specified in the dump table, a system dump.
The task is abnormally terminated with a CICS transaction dump. The VTAM ACB is closed.
Use the dump, the trace and the console message to diagnose and correct the original error. Retry the command when the earlier error is resolved.
DFHZSLS
The CICS terminal control restart task could not complete because a necessary step failed. The task has done some essential recovery operations and abnormally terminated itself with code ATC1.
CICS writes a transaction dump for the terminal control restart task.
CICS sends two messages to the console, one to identify the error detected by the terminal control restart task, and DFHTC1001 to report that the task has failed. A third message follows either to say that CICS has terminated abnormally with a dump, or to ask you to reply GO or CANCEL. Depending on the nature of the original error, you may see messages from some other system component (for example, an access method).
First, if CICS has requested a response, you must reply. If you reply ‘GO’, CICS continues processing, but without terminal control. If you reply ‘CANCEL’, CICS terminates abnormally with a dump.
Use the messages and dumps to find out the cause of the failure.
DFHTCRP
A CICS SET VTAM OPEN command has failed due to VTAM rejecting a CICS request.
Message DFHZC2302, DFHZC2304 or DFHZC2307 is sent to the console, and CICS terminates the transaction abnormally with a transaction dump.
The RPL with the VTAM request code and return code can be found in the RA pool addressed from TCTVRVRA. Use the VTAM Programming manual, to determine the cause of the error and the actions necessary to correct it. After correcting the error, either retry the request or terminate CICS and restart the network in your own time.
DFHZSLS
A write to a TLX device was issued with a data length of 0 causing TIOA data length (TIOATDL) to be zero.
The transaction is abnormally terminated with a CICS transaction dump.
For an error writing to a TLX device correct the error in the user program by ensuring that a data length for data to be placed in the terminal input/output area (TIOA) is provided at write time.
DFHZARL DFHZARQ
A serious CAVM error has occurred. The XRF TCB has abended.
CICS abnormally terminates with a system dump.
Use the dump and the guidance in any messages issued by other system components to diagnose and correct the original error.
See the CICS Problem Determination Guide for further guidance on using system dumps.
DFHTCRP
An internal logic error has been detected during APPC mapped processing. The conversation state maintained by DFHZARL does not match the state which is jointly maintained by DFHETL and DFHZARM.
This problem could also arise when CICS is receiving application data. CICS may receive and end of chain notification before receiving all the data expected.
The task is abnormally terminated with a CICS transaction dump. CICS processing continues.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHETL
DFHETL has a SEND DATA request with a data length greater than 65 528 bytes which is the maximum that it can process.
The transaction is abnormally terminated with a CICS transaction dump.
This is a CICS internal logic error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHETL
DFHZSUP has detected a bad response from an INITIAL-CALL request to DFHZARL. This response is returned to DFHZSUP in the DFHLUC parameter list.
The transaction is abnormally terminated with a CICS transaction dump.
Examine field LUCCDRCD in the DFHLUC parameter list. This appears in the ENTRY/EXIT trace points for DFHZARL. If trace is switched off, then it can be found in DFHZSUP's LIFO entry in the transaction dump.
(The offset for LUCCDRCD can be found in CICS Data Areas).
If LUCCDRCD is X'00000000', the error is the result of a connection failure. In this case examine the CSMT log for further diagnostic information.
DFHZSUP
An error has occurred during the processing of an inbound function management header (FMH). Either a length error has been detected, for example, incomplete FMH received, or an invalid field has been detected within the FMH.
The transaction is abnormally terminated with a CICS transaction dump.
Notify the system programmer of the error. The problem is probably in the remote system that has sent the invalid FMH.
DFHETL
A DFHKC RESUME macro call has been issued for a task without first issuing DFHKC SUSPEND. DFHKC RESUME must be preceded by DFHKC SUSPEND.
The transaction is abnormally terminated with a transaction dump.
Examine the trace entry to locate the error.
DFHZNCE
A transaction has issued an EXEC CICS READQ, WRITEQ or DELETEQ command against a logically recoverable transient data queue. The task was enqueued because another task currently owns the enqueue. While waiting to obtain the enqueue, the task was purged.
The transaction is abnormally terminated with a CICS transaction dump.
Investigate why the transaction was purged. It may have been purged via CEMT or automatically, by DTIMEOUT for example.
DFHETD
A deadlock timeout condition has been detected. This condition may occur within a transaction that specifies DTIMOUT to be nonzero on its installed transaction definition. Deadlock timeout occurs when a transaction has been waiting or has been suspended for longer than the time specified in DTIMOUT.
The abend is driven by the internal CICS event, ENQUEUE.
Analysis: The transaction receiving the ATDS abend must have been suspended after issuing an ENQUEUE request.
The transaction is abnormally terminated. A dump is not provided (even if a dump table entry has been set up).
The transaction should be reexecuted, and the situation causing the SUSPEND to occur may clear itself.
The ATDS abend is to be expected occasionally, unless DTIMOUT is set to zero. No special action is necessary.
DFHTDB
Transient data initialization has failed. A console message, DFH12xx, gives the reason for the failure.
Transient data initialization terminates abnormally. This abend is always followed by an ATDZ abend for the failing function, and by message DFHSI1521 (if CICS abends unconditionally), or message DFHSI1522, which prompts you to reply GO or CANCEL.
See the associated console message for information regarding the cause of the failure. Then respond to message DFHSI1522, if it has been issued.
DFHTDRP
A CICS function invoked by transient data initialization has failed. If the failing function is a transient data routine, this abend is preceded by a console message and an ATDY abend.
Transient data initialization terminates abnormally. This abend is always followed by message DFHSI1521 (if CICS abends unconditionally), or message DFHSI1522, which asks you to reply GO or CANCEL.
Refer to the associated console message for further information regarding the cause of the failure. Then respond to message DFHSI1522, if it has been issued.
DFHTDRP DFHTDB
The task has been purged, probably due to operator action such as a CEMT TASK PURGE command. The task might also have been purged as a result of CICS issuing a purge request.
The transaction is abnormally terminated with a transaction dump.
Use the transaction dump to determine why the task was purged. In particular, if the purge was operator initiated, the dump should be useful in determining why this task needed to be explicitly purged.
DFHTDB
An incorrect response has been received from a call to the enqueue (NQ) domain during the processing of an ENQUEUE or a DEQUEUE request.
The transaction is abnormally terminated with a transaction dump.
Examine the dump and any exception trace entries for further information. Since this is only used for internal enqueues, this abend indicates an error in CICS. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTDB
A FREEMAIN request to the storage manager has failed while CICS was executing a CEDA CHECK or CEDA INSTALL command.
CICS abnormally terminates the task with a transaction dump.
Use the dump and any associated messages issued by the storage manager to investigate the FREEMAIN failure.
DFHTOUT1
A GETMAIN request to the storage manager has failed while CICS was executing a CEDA CHECK or CEDA INSTALL command.
CICS abnormally terminates the task with a transaction dump.
Use the dump and any associated messages issued by the storage manager to investigate the GETMAIN failure.
DFHTOUT1
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 will have provided an exception trace.
The task is abnormally terminated with a CICS transaction dump.
Investigate why the task was purged. It was 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, or by CICS issuing a purge request.
If the master terminal operator purged the task, 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, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.
When CICS purges a task, it does so to allow an operation to complete which would be held up by the presence of active tasks.
DFHTMP
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 will have provided an exception trace, a console message and, possibly, a system dump (depending on the options specified in the dump table).
The task is abnormally terminated with a CICS transaction dump.
See the related message from the domain that detected the original error.
DFHTMP
A terminal operator entered the transaction identification for NACP.
The transaction is abnormally terminated with a CICS transaction dump.
Do not reenter the NACP transaction identification (CSNE).
DFHZNAC
The application program has issued a terminal control request for a terminal for which a previous request was terminated with an abend AZCT, because of a read timeout condition. The terminal control blocks are not in a fit state to allow a new request to be processed.
The task is abnormally terminated with a CICS transaction dump.
Change the application program to issue an abend when handling an abend AZCT.
DFHZARQ
The application program has issued a terminal control request for a terminal for which a previous terminal control request was terminated with an abend ATCH, because the task was purged. The terminal control blocks are not in a fit state to allow a new request to be processed.
The task is abnormally terminated with a CICS transaction dump.
Change the application program to issue an abend when handling an abend ATCH.
DFHZARQ
The node error program (NEP) or NACP decides that a task should abnormally terminate, but the task is at a critical point of processing and immediate termination would put the integrity of the system at risk.
The task is abnormally terminated with a CICS transaction dump when the task next requests any action against the terminal, or issues a sync point request involving the terminal.
Check destination CSMT for possible further information. Use the dump to determine why the task was abnormally terminated by NEP.
DFHZARQ, DFHZARL, DFHZSUP
There are two forms of this abend:
The task is abnormally terminated with a CICS transaction dump.
This usually occurs when, due to a hardware failure, a network device rejects the data stream sent to it. The device itself may indicate an error code that will give a specific reason for the rejection. Check the CSMT log for further information.
This abend can also result from an error in a connected system such as a mirror transaction abend.
Abend ATNI can occur if a user application does not correctly handle an error return code from an external resource manager, such as DB2.
For the NEP (VTAM) form, run a VTAM trace type=BUF for the logical unit and repeat the error.
For the TEP (non-VTAM) form, run a link trace for the line or local channel address for the device.
Examine the data stream and error response to determine the cause of the error.
This type of error occurs if the definitions in the TCT do not match the attributes of the actual device.
DFHZARL, DFHZARM, DFHZARQ, DFHZRAQ, DFHZSUP
You have attempted to invoke the CESC transaction with a terminal as principal facility. This is not allowed.
CICS terminates the CESC transaction. No dump is produced.
Ensure that the CESC transaction is not run against a terminal.
DFHCESC
CICS has received an abnormal response from an EXEC CICS START TRANSACTION(CESC) request. This is caused by an internal error.
CICS terminates the CESC transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCESC
CICS has received an abnormal response from a request to DFHZCUT to timeout a local userid table (LUIT). This is caused by an internal error in DFHZCUT.
CICS terminates the CESC transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCESC
CICS has received an abnormal response from an EXEC CICS CANCEL TRANSACTION(CESC) request.
CICS terminates the CESC transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCESC
CICS cannot determine the time at which an XRF takeover began.
CICS terminates the CESC transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCESC
CICS has received an abnormal response from an EXEC CICS DELAY TRANSACTION(CESC) request.
CICS terminates the CESC transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCESC
CICS has received an abnormal response from an EXEC CICS START TRANSACTION(CEGN) request. This is caused by an internal error.
CICS terminates the CEGN transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCESC
An attempt has been made to invoke the CESC transaction with an invalid function code. The CESC transaction should only be invoked by CICS. Valid codes are TERM_TIMEOUT, XRF_TIMEOUT, and ENABLE_TIMEOUT.
The most likely cause of this error is an invalid attempt by a user to invoke CESC.
CICS terminates the CESC transaction with a transaction dump.
Determine how CESC was invoked. If it was invoked by CICS, you will need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCESC
An error has occurred in the invocation of the CEGN transaction. CEGN has issued an EXEC CICS RETRIEVE command to retrieve the CEGN parameter list. Either the EXEC CICS RETRIEVE command has failed or it has succeeded but the retrieved data is invalid.
The most likely cause of this error is an invalid attempt by a user to invoke CEGN (for example, from a terminal or via an EXEC CICS START request).
CICS terminates the CEGN transaction with a transaction dump.
Determine how CEGN was invoked. If it was invoked by CICS, you will need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCEGN
The CEGN transaction has attempted to issue an EXEC CICS RETURN but the command has failed.
CICS terminates the transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCEGN
The CEGN transaction has attempted to issue an EXEC CICS GETMAIN, ASSIGN, or SEND but the command has failed.
CICS terminates the transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHCEGN
An error occurred when trying to estimate the length of a CICS message owned by the message domain.
CICS terminates the transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTPR.
An error occurred when trying to retrieve a CICS message from the message domain.
CICS terminates the transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTPR.
An error occurred when trying to estimate the length of a CICS message owned by the message domain.
CICS terminates the transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTPQ.
An error occurred when trying to retrieve a CICS message from the message domain.
CICS terminates the transaction with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTPQ.
The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The task that first detected the purged condition will have provided an exception trace.
The task is abnormally terminated with a CICS transaction dump.
Investigate why the task was purged. It was 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, or by CICS issuing a purge request.
If the master terminal operator purged the task, 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, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.
When CICS purges a task, it does so to allow an operation to complete which would be held up by the presence of active tasks.
DFHTPQ, DFHTPR.
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 will have provided an exception trace, a console message and, possibly, a system dump (depending on the options specified in the dump table).
The task is abnormally terminated with a CICS transaction dump.
See the related message produced by the domain that detected the original error.
DFHTPQ, DFHTPR.
The field engineering global trap exit program, DFHTRAP, requested task abnormal termination. However, the currently active task was not a system task (for example, task dispatcher) and it was not about to abend.
CICS disables the trap exit so that it will not be reentered, and terminates the currently active task abnormally.
This is a user-requested task abend.
If you want to use the trap again, you must reactivate it as follows:
CSFE DEBUG,TRAP=ON
You should use the global trap exit only in consultation with an IBM support representative.
DFHTRP
The transaction CTSD was attached other than by an internal request from the TS domain.
The transaction is abnormally terminated with a CICS transaction dump.
Investigate why the CTSD transaction was started. This transaction is intended for CICS internal use only and should not be started by a user or from a terminal.
DFHTSDQ
The transaction CTSD was attached with invalid parameters.
The transaction is abnormally terminated with a CICS transaction dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTSDQ
The task was canceled during execution of a temporary storage command.
The transaction is abnormally terminated with a CICS transaction dump.
Investigate the reason the task was canceled. The task has been canceled by the master terminal operator or automatically by either the deadlock timeout (DTIMEOUT) mechanism or the read timeout (RTIMOUT) mechanism.
DFHEITS, DFHICP, DFHTSP
An INVALID or DISASTER response was received from a request to the Temporary Storage (TS) Domain.
The transaction is terminated with a CICS transaction dump.
There has been an earlier failure which lead to the response from TS. Investigate the earlier failure (which is accompanied by a console message and a system dump).
DFHEITS, DFHICP, DFHTSP
A task has attempted to issue a WRITEQ TS request for a recoverable TS queue that has already been deleted in the same unit of work.
The task is abnormally terminated with a CICS transaction dump.
Correct the application to avoid issuing a WRITEQ TS request to a recoverable queue in a unit of work in which the queue has already been deleted.
DFHEITS, DFHTSP
A move of data to or from temporary storage has failed. The probable reason is that the size of the area being passed to CICS is inconsistent with the data length being used.
The transaction is abnormally terminated with a CICS transaction dump.
Identify the failing temporary storage request in the application and verify whether the length supplied on the request agrees with the data area size. Correct the application as appropriate.
DFHEITS
A DISASTER response caused by an IOERR was received from a request to the temporary storage (TS) domain.
The transaction is terminated with a CICS transaction dump.
There has been a failure during the creation of a temporary storage record. The likelihood is that an IOERR occurred during the buffer preparation prior to the new record being added to it. It is recommended that the queue be deleted to avoid future references to the failed record.
DFHEITS, DFHTSP, DFHICP
Insufficient space exists to build the parameter list for the DYNALLOC SVC.
The task is abnormally terminated and a dump is taken.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFH99KO