The CICS terminal control restart task could not complete because a necessary step failed. The task has done some essential recovery operations and has 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 one, DFHTC1001, to say 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).
Message DFHME0116 is normally produced containing the symptom string for this problem.
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. You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.
Console
DFHSII1, DFHTCRP
XMEOUT Parameters: applid, modname
The CICS terminal control recovery program, DFHTCRP, is unavailable. CICS cannot find DFHTCRP in any data set concatenated in the DFHRPL DD statement in the CICS startup job stream.
CICS terminates abnormally with a dump.
To correct this error, place DFHTCRP in a partitioned data set in the DFHRPL DD statement.
Console
DFHSII1
XMEOUT Parameter: applid
The CICS terminal object resolution program, DFHTORP, is not available. CICS cannot find DFHTORP in any data set concatenated in the DFHRPL DD statement in the CICS startup job stream.
CICS terminates abnormally with a dump.
To correct this error, place DFHTORP in a partitioned data set in the DFHRPL DD statement.
Console
DFHTCRP
XMEOUT Parameter:
applid
CICS initialization continues, but, even if it completes, VTAM resource initialization will be incorrect in some respect, depending on the function of module DFHxxxxxx.
If CICS completes initialization, processing of VTAM resources will be invalid. You should cancel CICS, make module DFHxxxxxx available and then restart CICS.
Console
DFHTCRP
XMEOUT Parameters: applid, xxxxxx
During a cold or initial start, CICS could not install all
the VTAM
resources defined by TCT macros. CICS has issued other message(s)
identifying which resources could not be installed.
CICS initialization continues.
If any of the uninstalled resources is essential, use RDO to make it available, or cancel CICS. The most likely reasons for this message are:
If you suspect an error in CICS, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTCRP
XMEOUT Parameter: applid
During a warm or emergency restart, CICS could not restore the resource xxxxxx.
CICS continues initialization.
If resource xxxxxx is essential to your system, cancel CICS. This problem is probably caused by a CICS logic error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTCRP
XMEOUT Parameters: applid, xxxxxx
During an emergency restart, CICS could not restore the resource resname from the catalog, because the definition for another resource highname that it depends on is not present. Usually resname is a session or modegroup and highname is a connection.
CICS continues restart, and deletes this resource from the CICS catalog. If the definition referred to was being installed when the previous CICS failed, both definitions are restored from the system log later in the restart.
If resource resname is essential to your system and is not restored later in initialization you can reinstall the resource having first installed the resource that it depends on. This message can be caused by:
CSMT
DFHTCRP
XMEOUT Parameters:
date,
time,
applid,
resname,
highname
During CICS initialization, the TCT load module DFHTCTxx (xx being the suffix) was found to contain entries not generated by the assembly macros for this release of CICS. This table cannot be used.
The bring-up is abandoned.
Either the incorrect TCT suffix was specified or implied, or the TCT has been assembled against the wrong level of CICS macros. Retry the bring-up, specifying a different suffix, or using a TCT assembled against the correct macros, as appropriate.
Console
DFHAPSIP
XMEOUT Parameter: applid
An error during XRF tracking prevented a change to a resource from being tracked. The resource is of type type and is associated with key key.
type is the tracking record type. This is one of the following:
key is the location of an object in the TCTTE hierarchy.
The associated resource is in an incorrect state, missing, or not deleted at the end of takeover.
Decide whether the named resource is critical and see if you can resolve the problem.
Console
DFHTCRP
XMEOUT Parameters: applid, type,key
During XRF tracking, a condition was detected which is not possible within the intended design. The insert indicates which of the checked conditions has been detected:
The message in question is ignored
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTCRP
XMEOUT Parameters: applid, condition
The alternate CICS that issued this message has only just started. Apparently the active CICS failed before the alternate could obtain all the information about TCT resources in the active. Please refer to messages DFHTC1034-DFHTC1036 for details of the types of information which may be missing or may be incomplete.
Takeover continues.
Watch for further messages.
Console
DFHTCRP
XMEOUT Parameter: applid
DFHTC1024 provides background information for this message. Apparently, the active CICS failed before the alternate CICS could obtain the definitions for all the trackable resources in the active’s TCT. Definitions may be missing at this point. However, the CICS catalog in the active may contain a more complete set of definitions in the restart data set. These will now be read as for a warm or emergency restart.
Takeover continues.
Look out for any errors while reading the CICS catalog.
Console
DFHTCRP
XMEOUT Parameter: applid
DFHTC1024 provides background information for this message. Apparently, the active CICS failed before the alternate CICS could obtain the session-state for all the trackable resources in the active’s TCT. States may be incorrect at this point.
Takeover continues.
Be prepared for some logical units (LUs) that were ACQUIRED in the old active not to be after the takeover.
Console
DFHTCRP
XMEOUT Parameter: applid
DFHTC1024 provides background information for this message. Apparently, the active CICS failed before the alternate CICS had been sent all the information regarding a type of resource which has not been implemented. This does not have any serious consequences as the information would have been thrown away. However, it does indicate a level of incompatibility between the old active system and this system.
Takeover continues.
Decide whether the implied level incompatibility exists and is expected. DFHTCRP
XMEOUT Parameters: applid, xxxx
An alternate is standing by and has received nnnn terminal control tracking messages from the active.
Tracking continues.
None.
Console
DFHTCRP
XMEOUT Parameters: applid, nnnn
An alternate is initializing, and is now about to start accepting messages from the active. Message DFHTC1044 should appear shortly.
Initialization continues.
None.
Console
DFHTCRP
XMEOUT Parameter: applid
An alternate is taking over and is processing the remaining few tracking records from the active. This message is issued every 15 seconds while the takeover is held up for processing to complete. This is potentially an error, especially if it is repeated an unusual number of times. The likely causes include a delay in STANDBY BIND or UNBIND processing in VTAM, or a CICS logic error. The system issues this message twice and then flushes the outstanding tracking activity as described in message DFHTC1046.
Look for message DFHTC1046.
Console
DFHZXQO
XMEOUT Parameter: applid
An XRF alternate system is taking over. The last of the terminal control tracking records from the failing active system has been received and is being processed.
Takeover continues.
None.
Console
DFHTCRP
XMEOUT Parameters: applid, nnn
An XRF alternate system is preparing to standby and has received the first message from the active containing information about terminal control resources installed and/or bound before this alternate was started.
Initialization continues.
None.
Console
DFHTCRP
XMEOUT Parameter: applid
An XRF alternate system is standing by, and has now received all the terminal control information it needs about terminal control resources installed and/or bound in the active before this alternate was started.
Normal tracking continues.
None.
Console
DFHTCRP
XMEOUT Parameter: applid
An alternate is taking over and is processing the remaining few tracking records from the active. Message DFHTC1042 has been issued twice. DFHZXQO is now doing a controlled flush of the outstanding activity.
CICS posts one outstanding action every 2 seconds in an attempt to free the hold-up. A system dump is taken for the first action only.
This processing only occurs when an error or unforeseen circumstance arises. If the problem can be reproduced, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHZXQO
XMEOUT Parameter: applid
An XRF alternate has received a tracking message from the active CICS, but either the associated system entry for this terminal is not present, or the ordering of terminal catalog records on the restart data set is incorrect (in that the terminal in error comes before the associated system entry).
key is the location of an object in the TCTTE hierarchy. This situation occurs if the active CICS was unable to send all of its tracking messages. This sometimes results in the system entry not being sent.
The tracking message is discarded and so the associated action (an INSTALL or LOGON) is not performed.
Ensure the CAVM message data set is large enough and restart the alternate. Check that the active CICS job is referring to the correct restart data set.
Console
DFHTCRP
XMEOUT Parameters: applid, key
A request for storage could not be satisfied in module DFHTCRP. The specific error is identified by the X'code' in the message. This implies that the dynamic storage area (DSA) size is too small. The X'code' identifies an exception trace record.
Terminal control initialization is terminated with a system dump and message DFHTC1001 is issued.
Since sufficient storage should be obtainable from within the minimum size DSA, this may imply a logic error within CICS. Try to increase the CDSASZE parameter in the system initialization table (SIT). You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTCRP
XMEOUT Parameters: applid, X'code'
This message is issued when system initialization reads a warm start record for which there is no matching terminal control table (TCT) entry. termid is the TCT name that is missing.
The record is ignored.
If TCT termid is required, system initialization should be canceled. Ensure that a matching TCT entry for terminal termid exists and retry.
Console
DFHTCRP
XMEOUT Parameters: applid, termid
SYSIDNT has been specified in the SIT or as a system initialization parameter override on a warm or emergency start of CICS. The value of SYSIDNT does not match that specified on the last cold or initial start. SYSIDNT should be updated only on a cold or initial start.
System initialization continues.
For an emergency or warm start of CICS, ensure that SYSIDNT has the same value as in the last cold or initial start. It is recommended that CICS is re-initialized with the appropriate value specified for the SYSIDNT parameter for the correct operation of CICS.
Console
DFHTCRP
XMEOUT Parameters: applid, sysid1, sysid2
This message indicates the OUT-OF-SERVICE conditions on completion of error processing in DFHTACP. It is possible that some of these conditions were true before the error was detected.
Other processing continues.
None.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, {1=Line , 2=CU ,3=Terminal }, {1=Term , 2=W/Term }, termid
The terminal operator has keyed in more data than was expected for this READ.
The transaction in progress is terminated.
Reset the terminal and restart the transaction after the message TRANSACTION HAS BEEN ABENDED has been received.
Terminal End User
DFHTACP
An invalid terminal address was received on the line identified by terminal termid. This error can normally occur only on control unit devices such
as a 2980 or a 3270. This is because CICS uses general polling and not all
terminals on the control unit may be defined to CICS. All other conditions
are undefined.
The optional part of the message "destdestid" applies only to TCAM. The destination destid is given when it does not match any of the network names (netnames)
specified on the TCTTE generation.
The control unit is placed out of service or, if it is not a general polled device, the line is placed out of service.
Ensure that all terminals on the failing control unit are defined in the terminal control table (TCT).
Where applicable, ensure that the TCAM MCP terminal generation names match the CICS DFHTCT TYPE=TERMINAL NETNAME parameter.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans ,2=, dest }, tranid|destid, {1=, rel line=}, rr, time
An output operation was attempted but was halted by the I/O routines and resulted in the SAM return code zz. If an abnormal condition is detected after a READ or WRITE macro, the operation is not started, and control is returned to the user program at the instruction following the READ or WRITE macro.
The line is placed out of service.
Ensure that the system is dumped at shutdown time in order to document the failure. For an explanation of the SAM return codes, zz, refer to the OS/VS SAM manual, (GC27-6980).
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, zz, {1=on line w/term , 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time
An input operation was attempted but was halted by the I/O routines, and resulted in the SAM return code zz. If an abnormal condition is detected after a READ or WRITE macro instruction, the operation is not started, and control is returned to your program at the instruction following the READ or WRITE macro instruction.
The line is placed out of service.
Ensure the system is dumped at shutdown time in order to document the failure.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, zz, {1=on line w/term , 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time
This message is issued when one of the following has occurred.
The write request is not executed, and the transaction terminates abnormally. CICS processing continues.
The user response depends on the condition that has occurred. For condition
CSTL
DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
The data length in TIOATDL was not positive for a write operation.
The transaction is abnormally terminated.
Correct the zero or negative data length specification in the application program.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
A write was requested on terminal termid by transaction tranid. However, the TCTTEDA field was not initialized.
The write request is not executed, and the transaction terminates abnormally. CICS processing continues.
Ensure that transaction tranid obtains the required storage and initializes the TCTTEDA field.
CSTL
DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
One of the following has occurred:
The write request is not executed, the terminal write storage is freed (if possible), and the transaction terminates abnormally. CICS processing continues.
Ensure that application programs do not set the value of TIOATDL greater than the TIOA GETMAIN size, and that the TIOA data length is not greater than the TCAM blocksize. Also ensure that the application program does not require a TIOA larger than 32767 bytes.
CSTL
DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
A unit check error has occurred on the line defined by terminal termid. The sense (SNS=ss) is provided.
D/T 3275 dialed gives an automatic two-minute time out
if there is no activity on the line.
The line is placed out of service on SAM lines.
Intervention on a switched line causes the task to be abnormally terminated and the line to be logically disconnected. Intervention on a non-switched line with a dummy (unidentified) terminal causes the line to be placed out of service. With a real terminal, intervention causes the terminal to be placed out of service and the transaction to be abnormally terminated.
A data check with a dummy terminal causes the line to be placed out of service. With a real terminal, it causes the terminal to be placed out of service and the transaction to be abnormally terminated.
Lost data on a READ,TEXT command causes a MESSAGE TOO LONG response to be sent to the terminal. The transaction is abnormally terminated.
Time-out on a READ,TEXT command causes a MESSAGE TOO LONG response to be sent to the terminal. Time-out with a dummy terminal causes the line to be placed out of service. With a real terminal, it causes the terminal to be placed out of service and the transaction to be abnormally terminated.
Examine the system console log message generated by SAM for this error and have the unit error corrected.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, ss, {1=on line w/term , 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time
A unit check error has occurred on the line defined by terminal termid. SAM indicates this error as undefined - S.N.O (should not occur). The sense (SNS=ss) is provided.
The line is placed out of service on SAM lines.
Intervention on a switched line causes the task to be abnormally terminated and the line to be logically disconnected. Intervention on a nonswitched line with a dummy (unidentified) terminal causes the terminal to be placed out of service and the transaction (task) to be abnormally terminated. With a real terminal, intervention causes the terminal to be placed out of service and the transaction to be abnormally terminated.
A data check with a dummy terminal causes the line to be placed out of service. With a real terminal, it causes the terminal to be placed out of service and the transaction to be abnormally terminated.
A time-out on a READ,TEXT command causes a MESSAGE TOO LONG response to be sent to the terminal. Time-out with a dummy terminal causes the line to be placed out of service. With a real terminal, it causes the terminal to be placed out of service and the transaction to be abnormally terminated.
Examine the system console log message generated by SAM for this error and have the unit error corrected.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, ss, {1=on line w/term , 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time
A unit exception error occurred on the line defined by terminal termid.
With a:
Examine the system console log message generated by SAM for this error and have the unit error corrected.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
A unit exception error has occurred on the line defined by terminal termid. SAM indicates this error as undefined - S.N.O (should not occur).
With a:
Examine the system console log message generated by SAM for this error. Have the unit error corrected.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
An I/O error (that was not a unit check, a unit exception, or a negative response) occurred on the line defined by terminal termid.
The line associated with terminal termid is placed out of service.
Examine the system console log message generated by SAM for this error. Have the unit error corrected.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
The task associated with terminal termid and transaction tranid was to have been abnormally terminated, but TPURGE(NO) was specified in the CSD definition for this task.
The terminal is placed out of service.
Use the master terminal facility to intercept or terminate the task.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, termid, {1= transaction },tranid, time
Input has occurred on a control unit (general poll) for which terminal termid is out of service or has a task that has not issued a DFHTC TYPE=READ macro.
No action is performed by CICS. Control is given to a user-written terminal error program, DFHTEP.
Code DFHTEP as dictated by environmental needs.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
An invalid destination was passed to TCAM from terminal termid.
The write is halted and the task is abnormally terminated with a dump.
Ensure that the destination is defined in the TCAM message control program (MCP).
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, termid, {1=, trans }, tranid, time
While processing an error for a non-VTAM terminal, CICS attempted to link to user replaceable module DFHTEP. The link failed. One or more of the default actions described in message DFHTC2538 have been taken.
The default action(s) set by DFHTACP are taken.
Refer to message DFHTC2538 for an explanation of the default action(s) that have been taken.
Possible solutions are:
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, {1=module DFHTEP is not AMODE 31, 2=module DFHTEP could not be loaded, 3=there is no PPT entry for program DFHTEP}
While processing an error for a non-VTAM terminal, user replaceable module DFHTEP was linked to and the program has abended with abend code abcode. One or more of the default actions described in message DFHTC2538 have been taken.
Control is passed back to the calling module DFHTACP. DFHTACP reinstates the default action(s) set before DFHTEP was called. The action(s) are then taken.
Refer to message DFHTC2538 for an explanation of the default action(s)
that have been taken.
Refer to abend code abcode for details of the
original error. Follow the user response given in abend code abcode to
solve the problem.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, abcode
A problem has arisen during the processing of an error for a non-VTAM terminal and message msgno has been issued. The explanations for all possible default actions are as follows:
The system action is stated in message related message.
Follow the guidance given in the user response section of message related message.
CSMT
DFHTACP
XMEOUT Parameters: date, time,applid, actions, relatedmessage
CICS has detected a violation of SNA protocols in a query response from device termid.
DFHQRY runs without effect.
Find out why an invalid query response is being sent to CICS.
CSMT
DFHQRY
XMEOUT Parameters: date, time,applid, termid