DFHXMxxxx messages

DFHXM0001
applid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.
Explanation:

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in the CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.

The code aaa/bbbb is a 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; 1310 refers to message DFHTS1310).

System action:

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. In some circumstances CICS is terminated directly if the error occurred in a crucial XM domain module.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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 relevant MVS codes manual which is detailed in the book list in the front of this manual.

Next, look up the CICS alphanumeric code in this manual. for further guidance.

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.

Destination:

Console

Modules:

DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD, DFHXMDM, DFHXMER, DFHXMFD, DFHXMIQ, DFHXMLD, DFHXMQD, DFHXMQC, DFHXMRP, DFHXMSR, DFHXMTA, DFHXMXD, DFHXMXE

XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname

DFHXM0002
applid A severe error (code X'code') has occurred in module modname.
Explanation:

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.

System action:

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. In some circumstances CICS is terminated directly if the error is critical.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

This indicates a possible error in CICS code. The severity of its impact 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.

If the severe error code is X'1112', there are no free transaction numbers to allocate to new transactions as all available transaction numbers are in use. If you are using transaction classes to limit the number of CICS tasks in your system, specify a transaction class purge threshold (PURGETHRESH) for any transaction class that has a heavy transaction load. See the CICS Resource Definition Guide and the CICS Performance Guide for more information.

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

Destination:

Console

Modules:

DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD, DFHXMDM, DFHXMER, DFHXMFD, DFHXMIQ, DFHXMLD, DFHXMQD, DFHXMQC, DFHXMRP, DFHXMSR, DFHXMTA, DFHXMXD, DFHXMXE

XMEOUT Parameters: applid, X'code',modname

DFHXM0004
applid A possible loop has been detected at offset X'offset' in module modname.
Explanation:

A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at offset X'offset'. This is the offset of the instruction which happened to be executing at the time when the error was detected.

System action:

An exception entry is made in the trace table.

A system dump is taken unless you have specifically suppressed the dump (by a user exit program at the XDUREQ exit, in the dump table or by global system dump suppression). CICS processing 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.

User response:

If CICS has not been terminated, it is necessary to decide whether the problem is serious enough to bring CICS down.

Since some CICS functions can use a lot of CPU time, this message may have been caused by a long-running function. So there may not be an error. Usually, CICS purges a CICS function which exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR which is measured in milliseconds). This means that execution of module modname is terminated and CICS continues.

If you have specifies ICVR=0 in the SIT and you consider that module modname has gone into a loop, you have to terminate CICS in order to terminate the runaway function.

If CICS has terminated module modname, and you consider that it was not a runaway, you should increase the ICVR time interval in the SIT. You have to bring CICS down at a suitable time to do this permanently. But you can change the ICVR time interval temporarily online using the CEMT transaction.

If raising the ICVR time does not solve the problem, you may need further assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD, DFHXMDM, DFHXMER, DFHXMFD, DFHXMIQ, DFHXMLD, DFHXMQD, DFHXMQC, DFHXMRP, DFHXMSR, DFHXMTA, DFHXMXD, DFHXMXE

XMEOUT Parameters: applid, X'offset', modname

DFHXM0101
date time applid terminal userid tranid TRANSACTION definition entry for transname has been added.
Explanation:

This is an audit log message indicating that transaction definition entry transname has been added to the system using the INSTALL command.

System action:

The system continues normally.

User response:

None.

Destination:

CSKL

Modules:

DFHXMXD

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, transname

DFHXM0103
date time applid terminal userid tranid TRANSACTION definition entry for transname has been deleted.
Explanation:

This is an audit log message indicating that transaction definition entry transname has been deleted from the system using the DISCARD command.

System action:

The system continues normally.

User response:

None.

Destination:

CSKL

Modules:

DFHXMDD

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, transname

DFHXM0105
date time applid terminal userid tranid TRANSACTION definition entry for transname has been replaced.
Explanation:

This is an audit log message indicating that transaction definition entry transname has been replaced in the system using the INSTALL command.

System action:

The system continues normally.

User response:

None.

Destination:

CSKL

Modules:

DFHXMXD

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, transname

DFHXM0110
date time applid Transaction definition transid1 has been installed with the same REMOTENAME and REMOTESYSTEM as existing definition transid2.
Explanation:

Transaction definition transid1 has been installed with the same REMOTENAME and REMOTESYSTEM as transaction definition transid2.

If this CICS system routes a transaction to the CICS system named as the REMOTESYSTEM of both the definitions and that transaction issues an EXEC CICS START request for the transaction-id named as the REMOTENAME of transid1 and transid2, CICS can either attach transid1 or transid2 on the local system to satisfy the START request.

System action:

The install of transaction definition transid1 continues normally.

If an EXEC CICS START request is issued on a remote system as described in the message explanation, CICS attaches transid1 and not transid2 on the local system.

CICS does not always resolve this ambiguity in the same way after a warm or emergency restart, however.

User response:

This situation usually causes no problems because the correct transaction is attached in the remote system. However, the correct transaction in the local system may not have been attached and this can manifest itself in the following ways:

Although these are not necessarily problems, you may want to check the definitions of the remote transactions in this system in case they have been defined incorrectly.

If remote START requests are issued as described, and it does matter which transaction CICS attaches in the local system, you should modify and reinstall the transaction definition that should not be attached. This removes any ambiguity.

Destination:

CSMT

Modules:

DFHXMXD

XMEOUT Parameters: date, time,applid, transid1, transid2

DFHXM0111
date time applid Catalog failure while processing {INSTALL | SET | DISCARD} request for transaction definition transid.
Explanation:

An error has occurred while altering the catalog during the processing of an install, set, or discard request for transaction definition transid.

System action:

The request continues as normal.

Depending upon the error that has occurred with the catalog, there may be severe problems if a warm or emergency restart of CICS is attempted. The catalog domain will have issued a message outlining the problem in this case.

Alternatively the problem may only be local to the catalog record containing the image of transaction definition transid and the following problems may occur only on a warm or emergency restart.

INSTALL
If it is a reinstall, the old version of the transaction definition is recovered. If it is an install, the transaction definition is not recovered.
SET
The change requested by the SET is not recovered. Instead the transaction definition is recovered to the state prior to the SET request being issued.
DISCARD
The transaction definition is recovered on the restart even though it is currently discarded.
User response:

No immediate action is required. Consider performing a cold or initial start the next time CICS is restarted to remedy the problem. If a cold or initial start is not appropriate and the problem is only localized to transaction definition transid, remedy the effects outlined for each case previously.

For example,

INSTALL
Reinstall the tranclass definition after the restart.
SET
Reissue the SET command after CICS has been restarted.
DISCARD
Reissue the DISCARD command after CICS has been restarted.

If the catalog problem persists after the restart, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHXMDD, DFHXMXD

XMEOUT Parameters: date, time,applid, {1=INSTALL, 2=SET,3=DISCARD}, transid

DFHXM0112
date time applid The install of transaction definition transid1 has removed ALIAS alias of transid2.
Explanation:

Transaction definition transid1 has been installed with an ALIAS of alias. However, ALIAS alias currently invokes transaction definition transid2.

System action:

The install of transid1 continues as normal.

The ALIAS alias now invokes transaction definition transid1 and not transid2 as previously.

User response:

If removal of transaction definition transid2's ALIAS was expected, no action is required. However, transaction definition transid2 should be modified on the CSD so that it no longer specifies the ALIAS.

If the ALIAS has been removed in error, reinstall transaction definition transid2 to reinstate its ALIAS. Transaction definition transid1 should be modified on the CSD so that it no longer specifies the ALIAS.

Destination:

CSMT

Modules:

DFHXMXD

XMEOUT Parameters: date, time,applid, transid1, alias, transid2

DFHXM0113
date time applid The install of transaction definition transid1 has removed TASKREQ taskreq of transid2.
Explanation:

Transaction definition transid1 has been installed with a TASKREQ of taskreq. However, TASKREQ taskreq currently invokes transaction definition transid2.

System action:

The install of transid1 continues as normal.

The TASKREQ taskreq now invokes transaction definition transid1 and not transid2 as previously.

User response:

If removal of transaction definition transid2's TASKREQ was expected, no action is required. However, transaction definition transid2 should be modified on the CSD so that it no longer specifies the TASKREQ.

If the TASKREQ has been removed in error, reinstall transaction definition transid2 to reinstate its TASKREQ. Transaction definition transid1 should be modified on the CSD so that it no longer specifies the TASKREQ.

Destination:

CSMT

Modules:

DFHXMXD

XMEOUT Parameters: date, time,applid, transid1, taskreq, transid2

DFHXM0114
date time applid The install of transaction definition transid1 has removed XTRANID X'xtranid' of transid2.
Explanation:

Transaction definition transid1 has been installed with a XTRANID of xtranid. However, XTRANID xtranid currently invokes transaction definition transid2.

System action:

The install of transid1 continues as normal.

The XTRANID xtranid now invokes transaction definition transid1 and not transid2 as previously.

User response:

If removal of transaction definition transid2's XTRANID was expected, no action is required. However, transaction definition transid2 should be modified on the CSD so that it no longer specifies the XTRANID.

If the XTRANID has been removed in error, reinstall transaction definition transid2 to reinstate its XTRANID. Transaction definition transid1 should be modified on the CSD so that it no longer specifies the XTRANID.

Destination:

CSMT

Modules:

DFHXMXD

XMEOUT Parameters: date, time,applid, transid1, X'xtranid',transid2

DFHXM0115
date time applid The install of transaction definition transid1 has removed TPNAME tpname of transid2.
Explanation:

Transaction definition transid1 has been installed with a TPNAME of tpname. However, TPNAME tpname currently invokes transaction definition transid2.

System action:

The install of transid1 continues as normal.

The TPNAME tpname now invokes transaction definition transid1 and not transid2 as previously.

User response:

If removal of transaction definition transid2's TPNAME was expected, no action is required. However, transaction definition transid2 should be modified on the CSD so that it no longer specifies the TPNAME.

If the TPNAME has been removed in error, reinstall transaction definition transid2 to reinstate its TPNAME. Transaction definition transid1 should be modified on the CSD so that it no longer specifies the TPNAME.

Destination:

CSMT

Modules:

DFHXMXD

XMEOUT Parameters: date, time,applid, transid1, tpname, transid2

DFHXM0116
date time applid PROGRAM parameter missing from transaction definition transid. PROGRAM is required because REMOTESYSTEM is the same as the local system.
Explanation:

Transaction definition transid has been installed without a PROGRAM parameter. Since it has been defined with a REMOTESYSTEM equal to the local system, a program is required if the transaction is executed on this system.

System action:

The install of transid continues as normal. Any attempt to run the transaction transid will fail because there is no program to link to.

User response:

This message is issued for information only. There is no problem if transaction transid is not executed on this system. If it is to be executed, the definition of transid needs to be modified and then reinstalled.

If the transaction is not executed, you may wish to investigate why the transaction definition has been installed. It could be that the transaction is defined in an RDO group that is shared between a number of different CICS systems. For example transid may be TTT1 in the following pair of definitions used to implement transaction routing to this local system CICB.

  Transaction  Remotesystem   Remotename   Program
  TTT1         CICB           TTT2         -
  TTT2         -              -            PROGA

In this example, a single definition would suffice if the transaction was made to have the same name on this system.

  Transaction  Remotesystem   Remotename   Program
  TTT1         CICB           TTT1         PROGA
Destination:

CSMT

Modules:

DFHXMXD

XMEOUT Parameters: date, time,applid, transid

DFHXM0201
date time applid terminal userid tranid TRANCLASS definition entry for tranclassname has been added.
Explanation:

This is an audit log message indicating that tranclass definition entry tranclassname has been added to the system using the INSTALL command.

System action:

The system continues normally.

User response:

None.

Destination:

CSKL

Modules:

DFHXMCL

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, tranclassname

DFHXM0203
date time applid terminal userid tranid TRANCLASS definition entry for tranclassname has been deleted.
Explanation:

This is an audit log message indicating that tranclass definition entry tranclasssname has been deleted from the system using the DISCARD command.

System action:

The system continues normally.

User response:

None.

Destination:

CSKL

Modules:

DFHXMCL

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, tranclassname

DFHXM0205
date time applid terminal userid tranid TRANCLASS definition entry for tranclassname has been replaced.
Explanation:

This is an audit log message indicating that tranclass definition entry transname has been replaced in the system using the INSTALL command.

System action:

The system continues normally.

User response:

None.

Destination:

CSKL

Modules:

DFHXMCL

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, tranclassname

DFHXM0211
date time applid Catalog failure while processing {INSTALL | SET | DISCARD} request for tranclass definition tranclassname.
Explanation:

An error has occurred while altering the catalog during the processing of an install, set, or discard request for tranclass definition tranclassname.

System action:

The request continues normally.

Depending upon the error that has occurred with the catalog, there may be severe problems if a warm or emergency restart of CICS is attempted. The catalog domain will have issued a message outlining the problem in this case.

Alternatively the problem may only be local to the catalog record containing the image of tranclass definition tranclassname and the following problems may occur only on a warm or emergency restart.

INSTALL
If it is a reinstall, the old version of the tranclass definition is recovered. If it is an install, the tranclass definition was not recovered.
SET
The change requested by the SET is not recovered. Instead the tranclass definition is recovered to the state it was in before the SET request was issued.
DISCARD
The tranclass definition is recovered on the restart even though it is currently discarded.
User response:

No immediate action is required. To fully resolve the problem, consider performing a cold or initial start the next time CICS is restarted. If a cold or initial start is not appropriate and the problem is only localized, to tranclass definition tranclassname, you can resolve each of the symptoms separately.

For example:

INSTALL
Reinstall the tranclass definition after CICS has been restarted.
SET
Reissue the SET command after CICS has been restarted.
DISCARD
Reissue the DISCARD command after CICS has been restarted.

If the catalog problem persists after the restart, you may need further assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHXMCL

XMEOUT Parameters: date, time,applid, {1=INSTALL, 2=SET,3=DISCARD}, tranclassname

DFHXM0212
applid Transaction transid has been attached with unknown tranclass tranclassname.
Explanation:

Transaction transid has just been attached. It is defined as belonging to tranclass tranclassname but tranclassname does not exist.

This message is only issued the first time transaction transid is attached with the unknown tranclass.

System action:

The attach of transaction transid proceeds as normal but without being subject to any tranclass scheduling constraints.

User response:

If transaction transid should belong to tranclass tranclassname, install that tranclass. If not, modify the transaction definition for transid as appropriate, and reinstall.

The CEDA CHECK command can be used to ensure that each of the tranclasses referenced by transaction definitions are defined within the same startup GRPLIST.

Note:
Do not attempt to reroute this message to a transient data queue.
Destination:

Console

Modules:

DFHXMQC

XMEOUT Parameters: applid, transid,tranclassname

DFHXM0213
applid Insufficient storage for system attach of transaction transid.
Explanation:

There is insufficient storage for a new task to be created for the attach of transaction transid.

Since the majority of the storage required for the new task is obtained from DSA storage, CICS is probably short on storage in one of the DSAs.

System action:

The attach request is queued. It is retried later when more storage should have become available. If the retried attach fails, it is queued and retried repeatedly until it succeeds.

User response:

If CICS is short on storage, message DFHSM0133 is also issued. Refer to that message for advice on how to resolve the condition.

If message DFHSM0133 has not been issued, the problem has been caused by insufficient MVS storage. In this case consider lowering the EDSALIM of the system to increase the amount of available MVS storage.

Note:
Do not attempt to reroute this message to a transient data queue.
Destination:

Console

Modules:

DFHXMAT

XMEOUT Parameters: applid, transid

DFHXM0301
date time applid An attempt to link to the user-replaceable transaction restart program (DFHREST) has failed for task number tasknum. Transaction restart is not performed for transaction tranid.
Explanation:

A restartable transaction abended and the transaction manager attempted to link to the user-replaceable transaction restart program (DFHREST) but the link has failed. Likely reasons are:

System action:

The transaction is not restarted.

User response:

If the problem is not rectified, a message is issued each time the link to DFHREST fails. To avoid this, ensure that DFHREST is properly defined and present in a library specified in the DFHRPL concatenation.

See the CICS Customization Guide for more information about user-replaceable programs.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHXMTA.

XMEOUT Parameters: date, time,applid, tasknum, tranid

DFHXM0302
applid An abend abcode occurred in the user-replaceable transaction restart program (DFHREST) under task number tasknum. Transaction restart is not performed for transaction tranid.
Explanation:

A restartable transaction abended and the transaction manager linked to the user-replaceable transaction restart program (DFHREST). DFHREST abended.

System action:

The transaction is not restarted.

User response:

If the problem is not rectified, a message is issued each time DFHREST abends. To avoid this, fix the problem in DFHREST and ensure that it is properly defined and present in a library specified in the DFHRPL concatenation.

See the CICS Customization Guide for more information about user-replaceable programs.

Destination:

Console

Modules:

DFHXMTA.

XMEOUT Parameters: applid, abcode,tasknum, tranid

DFHXM0303
applid A severe error (code X'code') has occurred while initializing task number tasknum with transaction identifier tranid. Terminal termid has not been released. The task is suspended indefinitely.
Explanation:

An internal error has prevented the initialization of task number tasknum with identifier tranid.

The task cannot run and cannot be abended. The principal facility of the task is a terminal. No message may be sent to the terminal and it is unusable by CICS. Rather than terminate CICS, the transaction manager keeps CICS running and preserves its integrity by suspending the task.

The suspended task will hold its MXT slot until CICS is terminated.

Note that the task may hold resources (for example, locks and enqueues) so you should cancel CICS at your earliest convenience. Otherwise you may risk other tasks being prevented from running because they also need access to the same resources. You may wish to add a dump table entry to always terminate CICS on this message.

System action:

The task is suspended indefinitely. First failure diagnostics should be produced by the component which first detects the error. The transaction manager also takes a dump. Message DFHME0116 is normally produced containing the symptom string for this problem.

The terminal principal facility of the task is unusable by CICS until CICS is canceled.

The task is suspended with a resource type of FOREVER and a resource name of DFHXMTA.

User response:

You must cancel CICS if you need to release the terminal associated with the task. You cannot quiesce CICS since this task will not terminate. You cannot purge or force-purge the task.

Note the error code X'code'. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHXMTA.

XMEOUT Parameters: applid, X'code',tasknum, tranid, termid

DFHXM0304
applid A severe error (code X'code') has occurred while initializing task number tasknum with transaction identifier tranid. Transient data queue tdqueue has not been released. The task is suspended indefinitely.
Explanation:

An internal error has prevented the initialization of task number tasknum with identifier tranid.

The task cannot run and cannot be abended. The principal facility of the task is a transient data queue. The TD queue will not trigger another task until CICS is terminated. Rather than terminate CICS, the transaction manager keeps CICS running and preserves its integrity by suspending the task.

The suspended task will hold its MXT slot until CICS is terminated.

Note that the task may hold resources ( for example, locks and enqueues) so you should cancel CICS at your earliest convenience. Otherwise you risk other tasks being prevented from running because they also need access to the same resources. You may wish to add a dump table entry always to terminate CICS on this message.

System action:

The task is suspended indefinitely. First failure diagnostics should be produced by the component which first detects the error. The transaction manager also takes a dump. Message DFHME0116 is normally produced containing the symptom string for this problem.

The task is suspended with a resource type of FOREVER and a resource name of DFHXMTA.

User response:

You must cancel CICS if you need to release the TD queue associated with the task. You cannot quiesce CICS since this task will not terminate. You cannot purge or force-purge the task.

Note the error code X'code'. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
Do not attempt to reroute this message to a transient data queue.
Destination:

Console

Modules:

DFHXMTA.

XMEOUT Parameters: applid, X'code',tasknum, tranid, tdqueue

DFHXM0305
applid A severe error (code X'code') has occurred while initializing task number tasknum with transaction identifier tranid. The interval control element has not been released. The task is suspended indefinitely.
Explanation:

An internal error has prevented the initialization of task number tasknum with identifier tranid.

The task cannot run and cannot be abended. The principal facility of the task is an interval control element. Any start data associated with the ICE will not be retrieved. Rather than terminate CICS, the transaction manager keeps CICS running and preserves its integrity by suspending the task.

The suspended task will hold its MXT slot until CICS is terminated.

Note that the task may hold resources (for example, locks and enqueues) so you should cancel CICS at your earliest convenience. Otherwise you may risk other tasks being prevented from running because they also need access to the same resources. You may wish to add a dump table entry always to terminate CICS on this message.

System action:

The task is suspended indefinitely. First failure diagnostics should be produced by the component which first detects the error. The transaction manager also takes a dump. Message DFHME0116 is normally produced containing the symptom string for this problem.

The task is suspended with a resource type of FOREVER and a resource name of DFHXMTA.

User response:

You must cancel CICS if you need to destroy the ICE. Any start data will remain in temporary storage until it is deleted unless it is nonrecoverable in which case it will disappear on the next cold, initial or emergency restart of CICS. You cannot quiesce CICS since this task will not terminate. You cannot purge or force-purge the task.

Note the error code X'code'. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHXMTA.

XMEOUT Parameters: applid, X'code',tasknum, tranid

DFHXM0306
applid A severe error (code X'code') has occurred while initializing task number tasknum with transaction identifier tranid. The task is suspended indefinitely.
Explanation:

An internal error has prevented the initialization of task number tasknum with identifier tranid.

The task cannot run and cannot be abended. The task has no principal facility bound to it. Rather than terminate CICS, the transaction manager keeps CICS running and preserves its integrity by suspending the task.

The suspended task will hold its MXT slot until CICS is terminated.

Note that the task may hold resources (for example, locks and enqueues) so you should cancel CICS at your earliest convenience. Otherwise you may risk other tasks being prevented from running because they also need access to the same resources. You may wish to add a dump table entry to always terminate CICS on this message.

System action:

The task is suspended indefinitely. First failure diagnostics should be produced by the component which first detects the error. The transaction manager also takes a dump. Message DFHME0116 is normally produced containing the symptom string for this problem.

The task is suspended with a resource type of FOREVER and a resource name of DFHXMTA.

User response:

You must cancel CICS if you need to destroy the task. You cannot quiesce CICS since this task will not terminate. You cannot purge or force purge the task.

Note the error code X'code'. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHXMTA.

XMEOUT Parameters: applid, X'code',tasknum, tranid

DFHXM0307
applid A severe error (code X'code') has occurred while terminating task number tasknum with transaction identifier tranid. The terminal termid has not been released. The task is suspended indefinitely.
Explanation:

An internal error has prevented the termination of task number tasknum with identifier tranid. It is not possible to abend the task or send a message to its terminal principal facility. Rather than terminate CICS, the transaction manager keeps CICS running and preserves its integrity by suspending the task.

The suspended task will hold its MXT slot until CICS is terminated.

Note that the task may hold resources (for example, locks and enqueues) so you should cancel CICS at your earliest convenience. Otherwise you may risk other tasks being prevented from running because they also need access to the same resources. You may wish to add a dump table entry to always terminate CICS on this message.

System action:

The task is suspended indefinitely. First failure diagnostics should be produced by the component which detected the error. The transaction manager also takes a dump. Message DFHME0116 is normally produced containing the symptom string for this problem.

The terminal principal facility of the task is unusable until CICS is canceled.

The task is suspended with a resource type of FOREVER and a resource name of DFHXMTA.

User response:

You must cancel CICS if you need to free up the terminal associated with the task. You cannot quiesce CICS since this task will not terminate. You cannot purge or force purge the task.

Note the error code X'code'. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHXMTA.

XMEOUT Parameters: applid, X'code',tasknum, tranid, termid

DFHXM0308
applid A severe error (code X'code') has occurred while terminating task number tasknum with transaction identifier tranid. The transient data queue tdqueue has not been released. The task is suspended indefinitely.
Explanation:

An internal error has prevented the termination of task number tasknum with identifier tranid. It is not possible to abend the task. The principal facility of the task is a transient data queue. The TD queue will not trigger another task until CICS is terminated. Rather than terminate CICS, the transaction manager keeps CICS running and preserves its integrity by suspending the task.

The suspended task will hold its MXT slot until CICS is terminated.

Note that the task may hold resources (for example, locks and enqueues) so you should cancel CICS at your earliest convenience. Otherwise you may risk other tasks being prevented from running because they also need access to the same resources. You may wish to add a dump table entry always to terminate CICS on this message.

System action:

The task is suspended indefinitely. First failure diagnostics should be produced by the component which detected the error. The transaction manager also takes a dump. Message DFHME0116 is normally produced containing the symptom string for this problem.

The task is suspended with a resource type of FOREVER and a resource name of DFHXMTA.

User response:

You must cancel CICS if you need to free up the transient data queue associated with the task. You cannot quiesce CICS since this task will not terminate. You cannot purge or force purge the task.

Note the error code X'code'. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
Do not attempt to reroute this message to a transient data queue.
Destination:

Console

Modules:

DFHXMTA.

XMEOUT Parameters: applid, X'code',tasknum, tranid, tdqueue

DFHXM0309
applid A severe error (code X'code') has occurred while terminating task number tasknum with transaction identifier tranid. The interval control element has not been released. The task is suspended indefinitely.
Explanation:

An internal error has prevented the termination of task number tasknum with identifier tranid. It is not possible to abend the task. The principal facility of the task is an interval control element. Rather than terminate CICS, the transaction manager keeps CICS running and preserves its integrity by suspending the task.

The suspended task will hold its MXT slot until CICS is terminated.

Note that the task may hold resources (for example, locks and enqueues) so you should cancel CICS at your earliest convenience. Otherwise you may risk other tasks being prevented from running because they also need access to the same resources. You may wish to add a dump table entry to always terminate CICS on this message.

System action:

The task is suspended indefinitely. First failure diagnostics should be produced by the component which detected the error. The transaction manager also takes a dump. Message DFHME0116 is normally produced containing the symptom string for this problem.

The task is suspended with a resource type of FOREVER and a resource name of DFHXMTA.

User response:

You must cancel CICS if you need to destroy the ICE associated with the task. Any start data remains in temporary storage until it is deleted unless it is nonrecoverable, in which case it disappears on the next cold, initial or emergency restart of CICS. You cannot quiesce CICS since this task does not terminate. You cannot purge or force purge the task.

Note the error code X'code'. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHXMTA.

XMEOUT Parameters: applid, X'code',tasknum, tranid

DFHXM0310
applid A severe error (code X'code') has occurred while terminating task number tasknum with transaction identifier tranid. If the task had a principal facility, it has been released. The task is suspended indefinitely.
Explanation:

An internal error has prevented the termination of task number tasknum with identifier tranid. It is not possible to abend the task. Rather than terminate CICS, the transaction manager keeps CICS running and preserves its integrity by suspending the task.

The suspended task will hold its MXT slot until CICS is terminated.

Note that the task may hold resources (for example, locks and enqueues) so you should cancel CICS at your earliest convenience. Otherwise you risk other tasks being prevented from running because they also need access to the same resources. You may wish to add a dump table entry always to terminate CICS on this message.

System action:

If the task had a principal facility, it has been released. If this was a terminal, the terminal should be usable by CICS.

The task is suspended indefinitely. First failure diagnostics should be produced by the component which detects the error. The transaction manager also takes a dump. Message DFHME0116 is normally produced containing the symptom string for this problem.

The task is suspended with a resource type of FOREVER and a resource name of DFHXMTA.

User response:

You cannot quiesce CICS since this task will not terminate. You cannot purge or force-purge the task.

Note the error code X'code'.

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

Destination:

Console

Modules:

DFHXMTA.

XMEOUT Parameters: applid, X'code',tasknum, tranid

Start of changeDFHXM0311End of change
Start of changeapplid A severe error (code X'code') has occurred while initializing task number tasknum with transaction identifier tranid. Scheduler resources associated with the task have not been released. The task is suspended indefinitely.End of change
Start of change
Explanation:

An internal error has prevented the initialization of task number tasknum with identifier tranid.

The task cannot run and cannot be abended. The principal facility of the task is the scheduler. The scheduler will not initiate another task until CICS is terminated. Rather than terminate CICS, the transaction manager keeps CICS running and preserves its integrity by suspending the task.

The suspended task will hold its MXT slot until CICS is terminated.

Note that the task may hold resources (for example, locks and enqueues), so you should cancel CICS at your earliest convenience. Otherwise, you risk other tasks being prevented from running because they also need access to the same resources. You may wish to add a dump table entry to always terminate CICS on production of this message.

End of change
Start of change
System action:

The task is suspended indefinitely. First failure diagnostics should be produced by the component which first detects the error. The transaction manager also takes a dump. Message DFHME0116 is normally produced containing the symptom string for this problem.

The task is suspended with a resource type of FOREVER and a resource name of DFHXMTA.

End of change
Start of change
User response:

You must cancel CICS if you need to release the resources associated with the task. You cannot quiesce CICS since this task will not terminate. You cannot purge or force-purge the task.

Note the error code X'code'. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
Do not attempt to reroute this message to a transient data queue.
End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHXMTA.End of change

Start of changeXMEOUT Parameters:End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecode',End of changeStart of changetasknum, End of changeStart of changetranidEnd of change

DFHXM0501
applid CICS cannot satisfy request for MXT. Value mxtvalue has been used instead.
Explanation:

The value entered for MXT cannot be handled by the system. mxtvalue is the largest value for which CICS has been able to acquire task storage.

The majority of the task storage required is now acquired from CICS DSAs.

System action:

The system continues to run with a MXT value of mxtvalue.

User response:

Check that the original value entered for MXT was correctly typed. If the value is mistyped, use CEMT to amend the MXT value (you are unlikely to be able to force the value higher). Remember that MXT now only includes user tasks and so it should not need to be set to a value as high as in previous releases.

If the value mxtvalue is acceptable, no action is necessary.

If the value mxtvalue is too small, check to see which programs, apart from CICS, are running in this region. To relieve the storage constraint, either increase the DSALIM or EDSALIM of the system to give CICS more storage for its own use. For further details about storage allocation at initialization, see the CICS Transaction Server for z/OS® Installation Guide.

Destination:

Console

Modules:

DFHXMSR

XMEOUT Parameters: applid, mxtvalue

DFHXM0502
applid A catalog failure has occurred while saving the MXT setting.
Explanation:

An error has occurred while saving the requested MXT setting on the catalog.

System action:

The requested MXT change request continues as normal.

Depending upon the error that has occurred with the catalog, there may be severe problems if a warm or emergency restart of CICS is attempted. The catalog domain will have issued a message outlining the problem in this case.

Alternatively the problem may only be local to the catalog record containing the MXT value and only it may not be recovered on a warm or emergency restart.

User response:

No immediate action is required. Consider performing a cold or initial start, with the required MXT value specified in the SIT the next time CICS is restarted. If a cold start is not appropriate, add MXT as a SIT override specifying the required MXT value.

Destination:

Console

Modules:

DFHXMSR

XMEOUT Parameter: applid

DFHXM0503
applid CICS cannot support minimum MXT value of minmxt. CICS is terminated.
Explanation:

A severe lack of storage has resulted in CICS not being able to acquire enough task storage to satisfy even the minimum MXT value of minmxt.

CICS cannot perform any useful work without minmxt number of user tasks.

System action:

CICS is terminated.

User response:

Investigate why there is insufficient storage for CICS to support such a low number of user tasks.

To relieve the storage constraint, either increase the DSALIM or EDSALIM of the system to give CICS more storage for its own use. For further details about storage allocation at initialization, see the CICS Transaction Server for z/OS Installation Guide.

Destination:

Console

Modules:

DFHXMSR

XMEOUT Parameters: applid, minmxt

[[ Contents Previous Page | Next Page Index ]]