DFHTCxxxx messages

DFHTC1001
applid Terminal control initialization failed (modname).
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHSII1, DFHTCRP

XMEOUT Parameters: applid, modname

DFHTC1002
applid Unable to link to program DFHTCRP.
Explanation:

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.

System action:

CICS terminates abnormally with a dump.

User response:

To correct this error, place DFHTCRP in a partitioned data set in the DFHRPL DD statement.

Destination:

Console

Modules:

DFHSII1

XMEOUT Parameter: applid

Start of changeDFHTC1004End of change
Start of changeapplid Program DFHTORP cannot be found. Typeterms cannot be initializedEnd of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS terminates abnormally with a dump.

End of change
Start of change
User response:

To correct this error, place DFHTORP in a partitioned data set in the DFHRPL DD statement.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHTCRPEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

DFHTC1011
applid Unable to load xxxxxx Start of changeDuring a CICS cold or initial start,End of change CICS could not PC LOAD the CICS module, DFHxxxxxx, probably because it is missing from the library.
System action:

CICS initialization continues, but, even if it completes, VTAM resource initialization will be incorrect in some respect, depending on the function of module DFHxxxxxx.

User response:

If CICS completes initialization, processing of VTAM resources will be invalid. You should cancel CICS, make module DFHxxxxxx available and then restart CICS.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, xxxxxx

DFHTC1012
applid Failure in installing VTAM resources
Explanation:

Start of changeDuring a cold or initial start, CICS could not install all the VTAMEnd of change resources defined by TCT macros. CICS has issued other message(s) identifying which resources could not be installed.

System action:

CICS initialization continues.

User response:

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.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameter: applid

DFHTC1013
applid Restore failed for xxxxxx
Explanation:

During a warm or emergency restart, CICS could not restore the resource xxxxxx.

System action:

CICS continues initialization.

User response:

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.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, xxxxxx

Start of changeDFHTC1014End of change
Start of changedate time applid Communication resource definition for (resname) was not restored from the catalog because the resource definition for (highname) was not installed.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

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:

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHTCRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeresname, End of changeStart of changehighnameEnd of change

DFHTC1015
applid TCT load module contains obsolete entries
Explanation:

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.

System action:

The bring-up is abandoned.

User response:

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.

Destination:

Console

Modules:

DFHAPSIP

XMEOUT Parameter: applid

DFHTC1022
applid Error for XRF tracking record - Type: type - Key: key
Explanation:

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:

TCT
CONTENTS
ZCP
SESSIONS

key is the location of an object in the TCTTE hierarchy.

System action:

The associated resource is in an incorrect state, missing, or not deleted at the end of takeover.

User response:

Decide whether the named resource is critical and see if you can resolve the problem.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, type,key

DFHTC1023
applid Logic error in tracking condition
Explanation:

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:

  1. No broadcast message accepted outside tracking. The GETMSG routine in DFHTCRP should only accept broadcast messages and those whose id matches that in field GETMSPEC. This field should only be set during tracking.
  2. Broadcast message with null key. A null-key record indicates that the catch-up stream that it arrives in is complete. This can only happen to the broadcast tracking stream if the active has just done a normal (warm) shut-down.
System action:

The message in question is ignored

User response:

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

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, condition

DFHTC1024I
applid XRF takeover while catching up.
Explanation:

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.

System action:

Takeover continues.

User response:

Watch for further messages.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameter: applid

DFHTC1034I
applid TCT contents incomplete. Will read catalog.
Explanation:

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.

System action:

Takeover continues.

User response:

Look out for any errors while reading the CICS catalog.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameter: applid

DFHTC1035E
applid Session states may be incorrect
Explanation:

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.

System action:

Takeover continues.

User response:

Be prepared for some logical units (LUs) that were ACQUIRED in the old active not to be after the takeover.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameter: applid

DFHTC1036I
applid Unimplemented tracking-type incomplete: xxxx
Explanation:

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.

System action:

Takeover continues.

User response:

Decide whether the implied level incompatibility exists and is expected. DFHTCRP

XMEOUT Parameters: applid, xxxx

DFHTC1040I
applid nnnn Terminal control tracking records received.
Explanation:

An alternate is standing by and has received nnnn terminal control tracking messages from the active.

System action:

Tracking continues.

User response:

None.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, nnnn

DFHTC1041I
applid Terminal control tracking started.
Explanation:

An alternate is initializing, and is now about to start accepting messages from the active. Message DFHTC1044 should appear shortly.

System action:

Initialization continues.

User response:

None.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameter: applid

DFHTC1042I
applid Waiting for terminal control tracking to drain.
Explanation:

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.

User response:

Look for message DFHTC1046.

Destination:

Console

Modules:

DFHZXQO

XMEOUT Parameter: applid

DFHTC1043I
applid Terminal control tracking ended - nnn records received.
Explanation:

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.

System action:

Takeover continues.

User response:

None.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, nnn

DFHTC1044I
applid Terminal control catch-up started.
Explanation:

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.

System action:

Initialization continues.

User response:

None.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameter: applid

DFHTC1045I
applid Terminal control catch-up complete.
Explanation:

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.

System action:

Normal tracking continues.

User response:

None.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameter: applid

DFHTC1046I
applid Flushing terminal control tracking.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZXQO

XMEOUT Parameter: applid

DFHTC1047I
applid Higher node missing. Record dropped for key
Explanation:

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.

System action:

The tracking message is discarded and so the associated action (an INSTALL or LOGON) is not performed.

User response:

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.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, key

DFHTC1060
applid Insufficient storage - code(X'code') in module DFHTCRP.
Explanation:

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.

System action:

Terminal control initialization is terminated with a system dump and message DFHTC1001 is issued.

User response:

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.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, X'code'

DFHTC1575
applid No TCT entry for termid
Explanation:

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.

System action:

The record is ignored.

User response:

If TCT termid is required, system initialization should be canceled. Ensure that a matching TCT entry for terminal termid exists and retry.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, termid

Start of change
DFHTC1600
applid The value for SYSIDNT, sysid1, does not match the one specified in the last cold or initial start, sysid2. CICS normal operation may be affected.
Explanation:

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 action:

System initialization continues.

User response:

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.

Destination:

Console

Modules:

DFHTCRP

XMEOUT Parameters: applid, sysid1, sysid2

End of change
DFHTC2500
date time applid {Line | CU | Terminal }out of service {Term |W/Term }termid
Explanation:

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.

System action:

Other processing continues.

User response:

None.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, {1=Line , 2=CU ,3=Terminal }, {1=Term , 2=W/Term }, termid

DFHTC2501
Msg too long, please resubmit
Explanation:

The terminal operator has keyed in more data than was expected for this READ.

System action:

The transaction in progress is terminated.

User response:

Reset the terminal and restart the transaction after the message TRANSACTION HAS BEEN ABENDED has been received.

Destination:

Terminal End User

Modules:

DFHTACP

DFHTC2502
date time applid TCT search error {on line w/term | at term }termid{, trans | , dest }tranid|destid{, rel line=}rr,time
Explanation:

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.

System action:

The control unit is placed out of service or, if it is not a general polled device, the line is placed out of service.

User response:

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.

Destination:

CSMT

Modules:

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

DFHTC2506
date time applid Output event rejected return code zz {on line w/term | at term }termid{, trans }tranid{, rel line=}rrtime
Explanation:

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.

System action:

The line is placed out of service.

User response:

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).

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, zz, {1=on line w/term , 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time

DFHTC2507
date time applid Input event rejected return code zz {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

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.

System action:

The line is placed out of service.

User response:

Ensure the system is dumped at shutdown time in order to document the failure.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, zz, {1=on line w/term , 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time

DFHTC2511
date time applid Invalid write request {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

This message is issued when one of the following has occurred.

  1. A transaction has issued a write to its terminal facility that currently has a terminal status of input.
  2. A transaction has issued a write to a 3735 during batch transmission prior to receipt of the end-of-file (EOF) condition.
System action:

The write request is not executed, and the transaction terminates abnormally. CICS processing continues.

User response:

The user response depends on the condition that has occurred. For condition

  1. ensure that transactions do not issue write requests to terminals in input status.
  2. ensure that the 3735 batch transaction does not issue its first write request before it has received the EOF condition.
Destination:

CSTL

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time

DFHTC2513
date time applid Output length zero {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

The data length in TIOATDL was not positive for a write operation.

System action:

The transaction is abnormally terminated.

User response:

Correct the zero or negative data length specification in the application program.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time

DFHTC2514
date time applid No output area provided {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

A write was requested on terminal termid by transaction tranid. However, the TCTTEDA field was not initialized.

System action:

The write request is not executed, and the transaction terminates abnormally. CICS processing continues.

User response:

Ensure that transaction tranid obtains the required storage and initializes the TCTTEDA field.

Destination:

CSTL

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time

DFHTC2515
date time applid Output area exceeded {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

One of the following has occurred:

System action:

The write request is not executed, the terminal write storage is freed (if possible), and the transaction terminates abnormally. CICS processing continues.

User response:

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.

Destination:

CSTL

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time

DFHTC2516
date time applid Unit check SNS=ss {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

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.

System action:

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.

User response:

Examine the system console log message generated by SAM for this error and have the unit error corrected.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, ss, {1=on line w/term , 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time

DFHTC2517
date time applid Unit check SNS=ss, S.N.O. {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

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.

System action:

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.

User response:

Examine the system console log message generated by SAM for this error and have the unit error corrected.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, ss, {1=on line w/term , 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time

DFHTC2518
date time applid Unit exception on {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

A unit exception error occurred on the line defined by terminal termid.

System action:

With a:

User response:

Examine the system console log message generated by SAM for this error and have the unit error corrected.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time

DFHTC2519
date time applid Unit exception S.N.O. {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

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).

System action:

With a:

User response:

Examine the system console log message generated by SAM for this error. Have the unit error corrected.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time

DFHTC2521
date time applid Undetermined unit error {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

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.

System action:

The line associated with terminal termid is placed out of service.

User response:

Examine the system console log message generated by SAM for this error. Have the unit error corrected.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time

DFHTC2522
date time applid Intercept Required for terminal termid{ transaction }tranid,time
Explanation:

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.

System action:

The terminal is placed out of service.

User response:

Use the master terminal facility to intercept or terminate the task.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, termid, {1= transaction },tranid, time

DFHTC2529
date time applid Unsolicited input {on line w/term | at term }termid{, trans }tranid{, rel line=}rr,time
Explanation:

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.

System action:

No action is performed by CICS. Control is given to a user-written terminal error program, DFHTEP.

User response:

Code DFHTEP as dictated by environmental needs.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, {1=on line w/term , 2=at term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time

DFHTC2534
date time applid Invalid destination at term termid{, trans }tranid,time
Explanation:

An invalid destination was passed to TCAM from terminal termid.

System action:

The write is halted and the task is abnormally terminated with a dump.

User response:

Ensure that the destination is defined in the TCAM message control program (MCP).

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, termid, {1=, trans }, tranid, time

DFHTC2536
date time applid Link to DFHTEP from DFHTACP failed because {module DFHTEP is not AMODE 31 | module DFHTEP could not be loaded | there is no PPT entry for program DFHTEP}.
Explanation:

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.

System action:

The default action(s) set by DFHTACP are taken.

User response:

Refer to message DFHTC2538 for an explanation of the default action(s) that have been taken.

Possible solutions are:

Destination:

CSMT

Modules:

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}

DFHTC2537
date time applid Abend abcode has occurred in module DFHTEP.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, abcode

DFHTC2538
date time applid Default actions actionshave been taken for message number relatedmessage.
Explanation:

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:

Action
Meaning
LINEOS
Place line out of service
NONPRGT
Non purgeable task
TERMOS
Place terminal out of service
ABENDT
Abend task on terminal
ABORTWR
Abort write and free terminal storage
RELTIOA
Release TCAM incoming message
SIGNOFF
Call the signoff program for terminal in error
System action:

The system action is stated in message related message.

User response:

Follow the guidance given in the user response section of message related message.

Destination:

CSMT

Modules:

DFHTACP

XMEOUT Parameters: date, time,applid, actions, relatedmessage

DFHTC8510
date time applid SNA protocol violation detected in query response at termid termid
Explanation:

CICS has detected a violation of SNA protocols in a query response from device termid.

System action:

DFHQRY runs without effect.

User response:

Find out why an invalid query response is being sent to CICS.

Destination:

CSMT

Modules:

DFHQRY

XMEOUT Parameters: date, time,applid, termid

[[ Contents Previous Page | Next Page Index ]]