An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.
The code aaa/bbbb is a three 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; TS1310 refers to message DFHTS1310).
An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.
CICS continues unless you have specified in the dump table that CICS should terminate.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If CICS is still running, it is necessary to decide whether to terminate CICS.
Look up the MVS code, if there is one, in the OS/390 MVS System Codes manual. Then look up the CICS alphanumeric code. This tells you, for example, whether the error is a program check, an abend, or a runaway, and may give you some guidance concerning user response.
If module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.
If you cannot run without the full use of module modname, you should bring CICS down in a controlled shutdown.
You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.
Console
DFHTDA, DFHTDB, DFHTDRM, DFHTDOC
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
An error has been detected in module modname. The code X'code' is the exception trace point id which uniquely identifies what the error is and where the error was detected. For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.
An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.
CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.
Message DFHME0116 is normally produced containing the symptom string for this problem.
The severity of this error depends on the importance of the function being executed at the time of the error.
CICS may not have been terminated.
If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.
If the message recurs or if you cannot run without the full use of module modname, you should bring CICS down in a controlled shutdown.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTDA, DFHTDB, DFHTDRM, DFHTDOC
XMEOUT Parameters: applid, X'code',modname
This is an informational message indicating that transient data initialization has started.
System initialization continues.
None. The message can be suppressed with the system initialization parameter MSGLVL=0.
Console
DFHTDRP
XMEOUT Parameter: applid
This is an informational message indicating that transient data initialization has completed successfully.
System initialization continues.
None. The message can be suppressed with the system initialization parameter MSGLVL=0.
Console
DFHTDRP, DFHTDRM
XMEOUT Parameter: applid
Transient data initialization has failed.
The SETXIT routine in DFHTDRP has been entered following abnormal termination of the transient data initialization task.
Alternatively an attempt to open the intrapartition data set failed.
Provided there are no subsequent serious errors which prevent further initialization of CICS, CICS issues one of two messages depending on what other errors, if any, have occurred during initialization.
If DFHSI1521 is issued, CICS initialization is terminated. If DFHSI1522 is issued, decide if CICS initialization is to be continued in degraded mode or to be terminated.
If, as part of a restart of CICS rather than during an initial start or a cold start, the intrapartition data set fails to open successfully when it was successfully opened on the previous CICS run, message DFHSI1521 is issued and CICS is terminated.
Check previous console messages, one of which should explain why transient data initialization has failed.
Console
DFHTDRP
XMEOUT Parameter: applid
This is an informational message indicating that transient data initialization
has been suspended pending takeover.
Some transient data initialization can be performed while
CICS is operating in standby mode. However the remaining initialization can
not be performed until takeover is complete because transient data sets, with
the exception of the DFHCXRF data set, are assumed to be passively shared.
System initialization continues.
None. The message can be suppressed with the SIT parameter MSGLVL=0.
Console
DFHTDRP
XMEOUT Parameter: applid
This is an informational message indicating that transient data initialization has been resumed following takeover.
System initialization continues.
None. This message can be suppressed with the system initialization
parameter MSGLVL=0.
Console
DFHTDRP
XMEOUT Parameter: applid
This is an informational message indicating that transient data is being initialized with TDINTRA=EMPTY specified on the SIT. This has the effect of initializing all intrapartition TD queues in an empty state. The TDINTRA SIT parameter is ignored during a cold or initial start.
System initialization continues.
None. The message can be suppressed with the system initialization parameter MSGLVL=0.
Console
DFHTDRP
XMEOUT Parameter: applid
During a warm or emergency restart, CICS has found that the contents of the intrapartition data set are not consistent with that in the DCTEs. The intrapartition data set could have been corrupted.
CICS terminates after producing a dump and writing an exception trace.
A system dump with dumpcode TD0170 is taken unless you have specifically suppressed dumps in the dump table.
Reinitialize the intrapartition data set.
Perform a cold start or an initial start of CICS.
Console
DFHTDRM
XMEOUT Parameter: applid
A transient data module cannot continue processing following the failure of a dfhxxyym call to domain xx.
The response (code X'response') and reason (code X'reason') are those returned from the domain call (that is, xxyy_response and xxyy_reason).
This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
A system dump with dumpcode TD0180 is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTDA, DFHTDB, DFHTDOC, DFHTDRM
XMEOUT Parameters: applid, X'response', X'reason', dfhxxyym
Module DFHTDRP cannot continue processing following the failure of a dfhxxyym call to domain xx.
The response (code X'response') and reason (code X'reason') are those returned from the domain call (that is, xxyy_response and xxyy_reason).
This is a critical error.
CICS writes a dump and terminates abnormally.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTDRP
XMEOUT Parameters: applid, X'response', X'reason', dfhxxyym
The trigger level has been reached for intrapartition transient data queue queue.
Module DFHTDB or DFHTDRM could not initiate the associated transaction following the response of a dfhxxyym call to domain xx.
The response (code X'response') and reason (code X'reason') are those returned from the domain call (that is, xxyy_response and xxyy_reason).
Initiation of the associated transaction has failed.
This is probably a CICS logic error.
Each subsequent write to the transient data queue causes another attempt to initiate the transaction, which will fail. However, this message is only issued the first time the error is detected.
CICS writes a dump and continues processing. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, X'response', X'reason', dfhxxyym, queue
No more data can be written to extrapartition queue queue.
A system abend, MVS code X'37', has occurred during processing on the data set with ddname ddname.
If the system abend occurs during processing of an EXEC CICS WRITEQ TD command, the NOSPACE condition is returned.
If the system abend occurs during processing of an EXEC CICS SET TDQUEUE CLOSED command, the data set is not closed and the IOERR condition is returned.
Note that a second attempt to close the data set succeeds.
Consider allocating more space to the data set before you bring CICS up again.
Console
DFHTDA, DFHTDOC
XMEOUT Parameters: applid, queue,ddname
A system abend, MVS code abcode, has occurred during processing on the extrapartition queue queue (that is, the data set with ddname ddname).
A system dump with dumpcode TD0242 is taken unless you have specifically suppressed dumps in the dump table.
Since this may not be a critical error, CICS is not terminated, and the IOERROR condition is returned.
Examine the CICS job log. QSAM issues a message explaining the reason for the system abend. See OS/390 MVS System Messages for a description of this message.
Console
DFHTDA, DFHTDOC
XMEOUT Parameters: applid, abcode,queue, ddname
An I/O error has occurred during the processing of an output operation to the extrapartition data set ddname on queue queue.
An IOERR condition is returned. Subsequent put requests are returned IOERR.
Close data set ddname via CEMT. If the I/O errors persist after a subsequent open, you probably need to reallocate this data set on a different volume.
Console
DFHTDA, DFHTDOC
XMEOUT Parameters: applid, queue,ddname
An attempt to write to intrapartition transient data set with ddname ddname has failed due to a NOSPACE condition. CICS did attempt to extend the data set but the relative byte address (RBA) of the next control interval (CI), if it were added, would have exceeded 2 gigabytes (x'7FFFFFFF').
The system continues normally.
Delete unwanted transient data queues from the intrapartition data set.
Console
DFHTDB
XMEOUT Parameters:
applid,
ddname
An I/O error has occurred during the processing of an input operation to the extrapartition data set ddname on queue queue.
An IOERR condition is returned. Subsequent put requests are returned IOERR.
Close data set ddname via CEMT. If the I/O errors persist after a subsequent open, you probably need to reallocate this data set on a different volume.
Check the definition of the extrapartition transient data queue. The specification of an invalid blocksize or recordsize may have caused the I/O error.
Console
DFHTDA, DFHTDOC
XMEOUT Parameters: applid, queue,ddname
An attempt to write to intrapartition transient data set with ddname ddname has failed due to a NOSPACE condition. CICS did attempt to extend the data set but no secondary space was defined or available.
The system continues normally.
Delete unwanted transient data queues from the intrapartition data set, or consider redefining the intrapartition data set with additional secondary storage allocation.
Console
DFHTDB
XMEOUT Parameters: applid, ddname
While dynamically allocating queue queue, CICS transient data issued an MVS DYNALLOC macro. The DYNALLOC failed with return code cccc. rrrr is the additional return code in register 15.
CICS continues with queue queue closed.
For the meaning of the DYNALLOC return codes, see the OS/390 MVS Programming: Authorized Assembler Services Guide.
Console
DFHTDOC
XMEOUT Parameters: applid, queue,X'rrrr', X'cccc', module
While closing queue queue, CICS transient data issued the MVS macro, DYNALLOC, to dynamically deallocate the queue. Deallocation failed with the MVS return code, cccc. rrrr is the return code in register 15.
CICS continues with the queue closed, but still allocated.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If you change the DSNAME in the DCTE, and then reopen the queue in the same CICS run, CICS may open the original data set. For an explanation of the MVS return code, see the OS/390 MVS Programming: Authorized Assembler Services Guide.
Console
DFHTDOC
XMEOUT Parameters: applid, queue,X'rrrr', X'cccc', module
An attempt by CICS to open queue queue failed because neither the JCL nor the DCTE specified the data set name.
CICS transient data has not opened queue queue, for the following reasons:
CICS continues processing with queue queue closed.
Before resubmitting the transaction, supply the data set name in the JCL or the DCTE. You can set the name in the DCTE while CICS is running by using CEDA to correct and reinstall the DCT entry.
Console
DFHTDOC
XMEOUT Parameters: applid, queue,module
The trigger level has been reached for the transient data queue queue. The transaction associated with the queue is remote, which is invalid for trigger transactions. The initiation of the transaction has, therefore, failed.
Until the error is corrected, each subsequent write to the transient data queue causes another attempt to initiate the transaction, which fails. However, in order to avoid filling the log with messages, this message is only issued the first time the error is detected.
Perform one of the following, as appropriate:
Console
DFHTDXM
XMEOUT Parameters: applid, tranid,queue
The trigger level has been reached for transient data queue queue. Initiation of the associated transaction has failed due to an error in system set up.
Until the error is corrected, each subsequent write to the transient data queue causes another unsuccessful attempt to initiate the transaction. However, in order to avoid filling the log with messages, this message is only issued the first time the error is detected.
Check the definition for the queue in the DCT. The queue must have a transaction associated with it that exists, is defined as local, and is installed.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, tranid,queue
The trigger level has been reached for the transient data queue queue. The schedule of the associated transaction has failed due to an error in system set up.
Until the error is corrected, each subsequent write to the transient data queue causes another attempt to schedule the transaction, which fails. However, in order to avoid filling the log with messages, this message is only issued the first time the error is detected.
Check the following and amend if necessary:
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, tranid,queue
A transaction that was attached when a TD trigger level was reached is ending abnormally and automatic transaction restart was requested for this transaction via the user replaceable module DFHREST. A severe error occurred when CICS attempted to restart the transaction.
Message DFHAP0002 is issued with a dump for the severe error that caused the restart to fail. Abnormal termination of the transaction for which restart was requested continues. The transaction is not automatically restarted.
The system attempts to reattach the trigger level transaction when the next TD request is received for this TD queue and the trigger level has been reached or exceeded.
Investigate the reason for the earlier severe error. See message DFHAP0002 for further guidance.
Console
DFHTDXM
XMEOUT Parameters: date, time,applid, tranid, queue-name
An attempt to read a control interval from the intrapartition data set with ddname ddname has failed due to a logical I/O error. retcode is the return code in register 15 and fdbkcode is the value of the feedback field in the request parameter list (RPL).
This is a critical error and CICS is terminated, even if you have specified
in the dump table that CICS should not terminate.
A system dump with dumpcode TD0360 is taken unless you
have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem. For the meaning of the codes in the message, refer to the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, ddname,X'retcode', X'fdbkcode'
An attempt to write or rewrite a control interval to the intrapartition data set with ddname ddname has failed due to a logical I/O error. retcode is the return code in register 15 and fdbkcode is the value of the feedback field in the request parameter list (RPL).
This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
A system dump with dumpcode TD0361 is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
For the meaning of the codes in the message, refer to the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, ddname,X'retcode', X'fdbkcode'
An attempt to read a control interval from the intrapartition data set with ddname ddname has failed due to a physical I/O error. retcode is the return code in register 15 and fdbkcode is the value of the feedback field in the request parameter list (RPL).
A system dump with dumpcode TD0362 is taken unless you have specifically suppressed dumps in the dump table.
This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
For the meaning of the codes in the message, refer to the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.
A copy of the physical error message produced by VSAM appears in (one of) the transient data VSAM error message area(s) in the system dump.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, ddname,X'retcode', X'fdbkcode'
An attempt to write or rewrite a control interval to the intrapartition data set with ddname ddname has failed due to a physical I/O error. retcode is the return code in register 15 and fdbkcode is the value of the feedback field in the request parameter list (RPL).
A system dump with dumpcode TD0363 is taken unless you have specifically suppressed dumps in the dump table.
This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
For the meaning of the codes in the message, refer to the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.
A copy of the physical error message produced by VSAM will appear in (one of) the transient data VSAM error message area(s) in the system dump.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, ddname,X'retcode', X'fdbkcode'
Control interval 0 in the intrapartition data set is reserved for transient data control information. The remaining control intervals are allocated to hold data for queues as determined by transient data processing on behalf of application program requests.
An invalid attempt has been made to read control interval 0 for the intrapartition data set with ddname ddname.
This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
A system dump with dumpcode TD0380 is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Each intrapartition DCTE contains pointers which, if the queue is not empty, are relative byte addresses (RBAs) associated with the intrapartition data set with ddname.
Furthermore each allocated control interval, apart from the first, contains one or more user records as well as a queue control record. This latter record, the first in the control interval, contains the forward chain pointer or RBA for the next control interval containing data for the queue.
In each case, transient data assumes that RBAs address record boundaries within the intrapartition data set.
The assumption can be violated in several ways. The type of violation may be determined from:
Violations include:
CICS may be restarted. An emergency restart for transient data will result in the RBAs being reconstructed from the system log and the intrapartition data set.
If an activity keypoint was taken between the occurrence of the error and its detection, it may prove necessary for a cold start or an initial start of CICS to be carried out.
CICS may be restarted. An emergency restart for transient data results in the RBAs being reconstructed from the system log and the intrapartition data set.
Note: If the contents of the I/O buffer were written to the intrapartition data set between the occurrence of the error and its detection, it may prove necessary to perform a cold start or an initial start of CICS.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, ddname
Control interval 0 in the intrapartition data set is reserved for transient data control information; the remaining control intervals are allocated to hold data for queues as determined by transient data processing on behalf of application program requests.
An invalid attempt has been made to (re)write control interval 0 for the intrapartition data set with ddname ddname.
This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
A system dump with dumpcode TD0381 is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Refer to message DFHTD0380.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, ddname
The output pointer for queue qqqq does not address a record boundary within the intrapartition data set with ddname ddname.
This is a critical error and CICS is terminated, even if you have specified
in the dump table that CICS should not terminate.
A system dump with dumpcode TD0382 is taken unless you
have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Refer to message DFHTD0380.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, qqqq,ddname
The input pointer for queue qqqq does not address a record boundary within the intrapartition data set with ddname ddname.
This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
A system dump with dumpcode TD0383 is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Refer to message DFHTD0380.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, qqqq,ddname
A forward chain pointer for queue qqqq is invalid with respect to the intrapartition data set with ddname ddname.
This is a critical error and CICS is terminated, even if you have specified
in the dump table that CICS should not terminate.
A system dump with dumpcode TD0384 is taken unless you
have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Refer to message DFHTD0380.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, qqqq,ddname
Control interval (CI) 0 in the intrapartition data set, ddname, is reserved for transient data control information. The remaining control intervals are allocated to hold data for queues as determined by transient data processing on behalf of application program requests.
System dump TD0385 is taken unless you have specifically suppressed dumps in the dump table.
This is a critical error. CICS is terminated even if you have specified in the dump table that CICS should not terminate.
Refer to the User Response of message DFHTD0380.
Console
DFHTDB, DFHTDRM
XMEOUT Parameters: applid, ddname
This is an audit log message indicating that transient data queue entry tdqueuename has been deleted from the DCT using the DISCARD command. Where:
The system continues normally.
None.
CSQL
DFHTDTM
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, queuename
This is an audit log message indicating that transient data queue entry tdqueuename has been added to the DCT using the INSTALL command Where:
The system continues normally.
None.
CSQL
DFHTDTM
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, tdqueuename
This is an audit log message indicating that transient data queue entry tdqueuename has been replaced in the DCT using the INSTALL command. Where:
The system continues normally.
None.
CSQL
DFHTDTM
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, tdqueuename
While carrying out operation xxxx (INSTALL) CICS found an error
in the destination control table (DCT) index. This message is
issued on warm or emergency restarts when transient data is installing entries
from the global catalog. The most likely reasons for this error are:
An application program has overwritten the index,
or
The CICS Directory Domain created the index incorrectly. or
The global catalog has been corrupted.
CICS writes a dump. The transaction abnormally terminates with abend code ATDY and message DFHSI1522 is issued.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Respond GO or CANCEL to message DFHSI1522.
Look at the contents of the global catalog, to determine if the catalog entry has been corrupted for the DCTE that is failing to install.
Assuming that the error is a storage violation, and that you have activated the trace facility, find in the trace the unsuccessful attempt to access the DCT by DFHTDP. Then find the last preceding successful access. You have now narrowed the search to programs that were running between these two accesses. Examine these programs for an error that could cause a storage violation.
If you have not activated trace, but you can recreate the error, activate trace, recreate the error, and proceed as in the previous paragraph.
Console
DFHTDRP
XMEOUT Parameters: applid, xxxx
During a warm or emergency restart, CICS was unable to add
a particular entry to the destination control table (DCT) for destination xxxx.
CICS ignores the definition and continues initialization.
The cause of this install failure may be indicated in earlier messages issued from the transient data (TD) component. It may be the result of a failure to open the DFHINTRA data set, or a security error associated with any userid included in the definition. In the latter case, it is possible to create an RDO definition for the entry, with the correct userid, once CICS has initialized, and then to install it using the CEDA transaction.
Console
DFHTDRP
XMEOUT Parameters: applid, xxxx
During a warm start, while carrying out operation xxxx (STARTBROWSE, GETNEXT or ENDBROWSE), the transient data recovery program (DFHTDRP) found an error in the destination control table (DCT) catalog.
The most likely reasons for this error are I/O errors in the catalog data set, or a logic error in the CICS module, DFHCCCC.
CICS writes a dump. The transaction abnormally terminates with abend code ATDY and message DFHSI1522 is issued.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Respond GO or CANCEL to message DFHSI1522.
Determine and correct the I/O errors on the catalog data set. If you cannot restore the catalog data set, or suspect that there might be a CICS logic error in DFHCCCC, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTDRP
XMEOUT Parameters: applid, xxxx
CICS is unable to open the intrapartition data set ddname because no DD statement has been provided.
During a cold or initial start, TD initialization continues until any DCT macro entries have been processed. Any intrapartition entries found are not installed and message DFHTD1217 is issued for each install failure encountered. At the end of TD initialization, message DFHTD0102 is issued. If no other initialization errors occur, message DFHSI1522 is issued.
For all other starts, TD checks the catalog to see if DFHINTRA had opened successfully on the previous CICS run. If it did, initialization is terminated. If it did not, TD initialization continues normally.
During a cold or initial start, respond GO or CANCEL to message DFHSI1522.
Modify the CICS JCL to add a DD statement defining the intrapartition data set (DFHINTRA).
Console
DFHTDRP
XMEOUT Parameters: applid, ddname
CICS is unable to open the intrapartition data set ddname because it is not defined as VSAM ESDS.
During a cold or initial start, TD initialization continues until any DCT macro entries have been processed. Any intrapartition entries found are not installed and message DFHTD1217 is issued for each install failure encountered. At the end of TD initialization, message DFHTD0102 is issued. If no other initialization errors occur, message DFHSI1522 is issued.
For all other starts, TD checks the catalog to see if DFHINTRA had opened successfully on the previous CICS run. If it did, initialization is terminated. If it did not, TD initialization continues normally.
On a cold or initial start, respond GO or CANCEL to message DFHSI1522.
Recreate the intrapartition data set as a VSAM ESDS and restart CICS.
Console
DFHTDRP
XMEOUT Parameters: applid, ddname
The intrapartition data set ddname is not formatted (it is empty). Initial formatting is done (if necessary) when CICS is cold or initial started.
CICS continue to initialize until the destination control table has been completed. Any intrapartition definitions being read from the global catalogue will fail to install because of the original failure. When DFHTDRP completes its processing, CICS writes a dump. The transaction abnormally terminates with abend code ATDY and message DFHSI1522 is issued.
Respond GO or CANCEL to message DFHSI1522.
Perform a cold or initial start when CICS is next brought up.
Console
DFHTDRP
XMEOUT Parameters: applid, ddname
The intrapartition data set ddname was not initialized for intrapartition transient data. The most likely reason for this is data corruption by:
CICS writes a dump. The transaction abnormally terminates with abend code ATDY and message DFHSI1522 is issued.
Respond GO or CANCEL to message DFHSI1522.
Reinitialize the intrapartition data set.
Console
DFHTDRP
XMEOUT Parameters: applid, ddname
VSAM has detected an error during SHOWCB processing for the intrapartition data set ddname with VSAM return code retcode.
CICS writes a dump. The transaction abnormally terminates with abend code ATDY and message DFHSI1522 is issued.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Respond GO or CANCEL to message DFHSI1522.
Check the return code in the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.
Console
DFHTDRP
XMEOUT Parameters: applid, ddname,retcode
VSAM has detected an error during OPEN processing for the intrapartition data set ddname. retcode is the VSAM return code and errorcode is the VSAM error code.
CICS writes a dump, then attempts to continue with initialization. If a cold or initial start is taking place, any entries found in a DCT load module are installed, except for any intrapartition entries. If any of these are found, message DFHTD1217 is issued for each install failure. When TDRP completes its processing message DFHTD0102 is issued followed by message DFHSI1522.
For all other types of start, if DFHINTRA had failed during the previous run of CICS, processing continues as normal. If DFHINTRA was open on the previous run, CICS terminates.
Message DFHME0116 is normally produced containing the symptom string for this problem.
On a cold or initial start, respond GO or CANCEL to message DFHSI1522.
Check the return code and error code in the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.
Console
DFHTDRP
XMEOUT Parameters: applid, ddname,retcode, errorcode
VSAM has detected an error during CLOSE processing for the intrapartition data set ddname. retcode is the VSAM return code.
CICS writes a dump, then attempts to continue with initialization. If a cold or initial start is taking place, any entries found in a DCT load module are installed, except for any intrapartition entries. If any of these are found, message DFHTD1217 is issued for each install failure. When TDRP completes its processing message DFHTD0102 is issued followed by message DFHSI1522.
For all other types of start, if DFHINTRA had failed during the previous run of CICS, processing continues as normal. If DFHINTRA was open on the previous run, CICS terminates.
Message DFHME0116 is normally produced containing the symptom string for this problem.
For a cold or initial start, respond GO or CANCEL to message DFHSI1522.
Check the return code in the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.
Console
DFHTDRP
XMEOUT Parameters: applid, ddname,retcode
VSAM has detected an error during PUT processing for the intrapartition data set ddname. retcode is the VSAM return code and errorcode is the VSAM error code.
CICS writes a dump. The transaction abnormally terminates with abend code ATDY and message DFHSI1522 is issued.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Respond GO or CANCEL to message DFHSI1522.
Check the return code and error code in the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.
Console
DFHTDRP
XMEOUT Parameters: applid, ddname,retcode, errorcode
VSAM has detected an error during GET processing for the intrapartition data set ddname. retcode is the VSAM return code and errorcode is the VSAM error code.
CICS writes a dump. The transaction abnormally terminates with abend code ATDY and message DFHSI1522 is issued.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Respond GO or CANCEL to message DFHSI1522.
Check the return code and error code in the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.
Console
DFHTDRP
XMEOUT Parameters: applid, ddname,retcode, errorcode
Transient data initialization detected an error with userid userid during installation of the intrapartition queue for automatic transaction initiation.
The specified userid is not valid for use by this CICS job for non-terminal transactions initiated by the transient data trigger.
There may be a previous message which gives the cause of this error.
Transient data initialization continues.
The intrapartition queue definition is not added to the destination control table.
Notify the system programmer.
If the userid is invalid, correct the userid specified in the resource definition for the intrapartition queue.
If the userid is valid, ensure that it can be used by non-terminal transactions that are initiated by trigger for the intrapartition queue. See the CICS RACF® Security Guide for guidance.
Console
DFHTDTM
XMEOUT Parameters: applid, queuename, userid
Module DFHTDTM detected the failure of a dfhxxyym call to domain xx while attempting to install an intrapartition entry containing a USERID.
The response (code X'response') and reason (code X'reason') are those returned from the domain call (that is, xxyy_response and xxyy_reason).
This can be due to a CICS logic error.
If the error occurred during transient data initialization, this process will continue if possible. If processing cannot continue then a dump will be taken and an abend ATDY is issued.
Refer to earlier messages and the dump produced by domain xx.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTDTM
XMEOUT Parameters: applid, X'response', X'reason', dfhxxyym
An attempt was made to establish security for userid userid. The attempt was rejected by the external security manager (ESM).
Security has not been established for the userid.
The response and reason codes (safresp and safreas) returned by the system authorization facility (SAF), and the response and reason codes (esmresp and esmreas) returned by the external security manager (ESM) are those issued by the RACROUTE REQUEST=VERIFY or RACROUTE REQUEST=EXTRACT macros. These return codes are described in the OS/390 MVS Programming: Authorized Assembler Services Guide and in External Security Interface (RACROUTE) Macro Reference for MVS and VM (SC28-1366). See these manuals for an explanation of the codes.
There may be further messages produced by CICS or the external security manager (ESM) which provide more information.
Console
DFHTDTM
XMEOUT Parameters: applid, userid,X'safresp', X'safreas', X'esmresp',X'esmreas'