DFHMExxxx messages

DFHME0001
applid An abend (code xxx/yyyy) has occurred at offset X'offset' in module modname.
Explanation:

An abnormal end or program check has occurred in module modname.

The code xxx/yyyy 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 (for example AKEA) or a number referring to a CICS message (for example 1310 refers to CICS message DFHTS1310).

System action:

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this error may not be critical, CICS is not terminated, even if you have specified terminate in the dump table.

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

User response:

Since the abend affects the national language modules in the message (ME) domain, CICS is not automatically terminated. However, you may decide that your system should not be allowed to run without these modules, in which case you need to bring CICS down.

Look up the MVS code, if there is one, in the relevant MVS codes manual which is detailed in the book list in this manual. Look up the CICS alphanumeric code in this manual. This code tells you, for example, whether the error was a program check, an abend, a runaway, or a recovery percolation.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEDM, DFHMEME, DFHMESR

DFHME0002
applid An 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 the place where the error was detected.

System action:

A bad return code is sent to the caller of the message (ME) domain. If the call is made by the domain manager, DFHDMDM, CICS is terminated by the domain manager, and a message is issued to this effect. However, if the message is issued by a message domain module, CICS is allowed to continue.

An exception entry is made in the trace table. For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.

A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this error may not be critical, CICS is not terminated immediately, even if you have specified terminate in the dump table.

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

User response:

Inform the system programmer as this message indicates a severe error in CICS code. Its impact may or may not be severe, depending on the circumstances. For example, if it only occurs once and CICS has not been terminated by the domain manager, you may decide to continue to run and bring CICS down at a convenient time. But if the message recurs or if you cannot run without the full use of all CICS messages, 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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEDM, DFHMEME, DFHMESR, DFHMEWT

DFHME0004
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 was executing at the time the error was detected.

System action:

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. This situation may not be an error, or if it is an error it may not be critical, so CICS is not terminated immediately, even if you have specified terminate in the dump table. CICS will purge the runaway task if you have specified this in the SIT.

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

User response:

This error affects message generation, and the message (ME) domain does not automatically terminate CICS. You should decide whether the problem is serious enough to bring CICS down.

Since some transactions can use a lot of CPU time, this message may have been caused by a long-running transaction. Usually, CICS terminates a task which it considers to be a runaway task. It does this termination when the task exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR which is measured in milliseconds).

If you have declared ICVR=0, you have to terminate the task yourself if you consider that it has gone into a loop. Purge the task using the CEMT transaction.

If CICS has purged the task and you consider that it was not a runaway, you should increase the ICVR time interval in the SIT. You will have to bring CICS down at a suitable time in order to do this.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEDM, DFHMESR, DFHMEME

DFHME0006
applid Insufficient storage to satisfy GETMAIN (code X'code') in module modname. MVS code mvscode.
Explanation:

An MVS GETMAIN was issued by module modname, but there was insufficient storage available to satisfy the request. The code X'code' is the exception trace point ID which uniquely identifies the place in the code where the error occurred. The code mvscode is the MVS GETMAIN return code.

System action:

An exception entry is made in the trace table with code X'code'. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this may not be a critical error, CICS is not terminated immediately, even if you have specified terminate in the dump table. However, if this error indicates a general problem with storage, CICS could be abnormally terminated by the CICS storage manager. A message will be issued to this effect.

If the GETMAIN fails for DFHMEDM, a return code is sent to the domain manager, DFHDMDM, and CICS is terminated by the domain manager. A message is issued to this effect.

If the GETMAIN fails for the message domain DFHMEME, it could occur in one of four places. The code X'code' indicates which GETMAIN has failed as follows:

Code
Meaning
X'0340' -
During formatting of TD message

The message is not issued.

X'0341' -
During build of message

The message is not issued.

X'0342' -
While building user exit parameters

The message is issued to original destination.

X'0343' -
During rebuild of message in English

The rebuilt English message is not issued.

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

User response:

If CICS is terminated, look out for the relevant termination messages from the storage manager or the domain manager and the user response suggested.

Try decreasing the size limits of the DSAs or EDSAs. Or, try increasing the size of the whole region, if it is not already at maximum size. You will need to bring CICS down to do this, if it has not already been terminated.

The problem may be a temporary one which rights itself if more storage becomes available. If CICS is still running, and you can manage without the full set of CICS messages, you may decide to continue and bring CICS down at a convenient time.

You can get diagnostic information about the MVS return code by consulting the relevant MVS codes manual.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEDM, DFHMEME

DFHME0101
applid An error (code X'code') occurred while writing message msgno to transient data destination dest
Explanation:

CICS has tried to write message msgno to the transient data destination dest. This has failed for one of the following reasons:

  1. Destination dest has not been defined in the DCT.
  2. Destination dest is currently disabled.
  3. The transient data queue for destination dest is full.
  4. An I/O error has occurred writing to destination dest.

The code X'code' is the exception trace point ID which uniquely identifies the place where the error was detected.

System action:

An exception entry is made in the trace table and CICS continues.

User response:

Check that dest is defined in your DCT.

If (1), add a new entry to the DCT for destination dest. Alternatively, if msgno is a DFHDB2xxx message, refer to the installed DB2CONN object. Change any of the msgqueue1, msgqueue2 and msgqueue3 parameters of the DB2CONN that specify destination dest so that they name a valid destination defined in the DCT.

If (2), use CEMT to reset the status of the queue to ‘enabled’.

If (3), allocate more space for the queue, or reset the trigger level (if messages are being issued to a terminal or printer).

If (4), investigate and fix the cause of the I/O error.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0102
applid An error (code X'code') has occurred in module modname while producing message msgno.
Explanation:

A severe error has been detected and the message (ME) domain has been unable to produce message msgno. The code X'code' is the exception trace point ID which uniquely identifies the place where the error was detected.

System action:

A return code is sent to the caller of the message (ME) domain, but since the call was made by a message domain module, CICS is allowed to continue.

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this may not be a critical error, CICS is not terminated immediately, even if you have specified terminate in the dump table.

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

User response:

Inform the system programmer as this indicates a severe error in CICS code. However, its impact may not be serious. For example, if the error only occurs once and you can run without message msgno, you may continue to run and bring CICS down at a convenient time.

However, if the message recurs (and on each recurrence there is a different message number msgno), or if you cannot run without the full use of all CICS messages, 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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEBU, DFHMEIN, DFHMEWT, DFHMEME

DFHME0105
applid Insufficient storage to load module modname.
Explanation:

An MVS load has failed. The message language module modname could not be loaded as there was insufficient storage available. The language module is defined in the SIT for messages in a particular language, or is the default language module.

The default language is always used for messages sent to transient data queues and to consoles (providing that it is not a double-byte language in which case the message is sent to the console in English). If the default language module cannot be loaded, no messages can be delivered. Terminals can have messages in the default language or in another chosen language. If the chosen language module cannot be loaded, terminal messages use the default language instead.

System action:

An exception entry is made in the trace table and a dump is taken, unless you have specifically suppressed dumps in the dump table. As this may not be a critical problem, CICS is not terminated unless the default language module cannot be loaded, (even if you have specified terminate in the dump table).

If the missing module is not the default language module, CICS uses the default language for messages to terminals. If the default language module cannot be loaded, a return code is sent to the domain manager and CICS is terminated by the domain manager.

User response:

If the default language is in operation and this is acceptable, you need not bring CICS down. (Or you may bring CICS down at a more convenient time.)

If the default language is in operation and this is not acceptable, or if the default language module itself is missing, try decreasing the size limits of the DSAs or EDSAs. Or you could try increasing the size of the whole region, if it is not already at maximum size.

Alternatively, you may be able to get more storage space by removing unwanted language modules from storage. To do this, bring CICS down, remove the language codes you do not need from the SIT or respecify the list of language modules as an override parameter, and restart CICS.

Note:
You should not remove the default language module from the SIT.
Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEDM

DFHME0106
applid Module modname could not be loaded. REGISTER 1 = X'nnnnnnnn' and REGISTER 15 = X'nnnnnnnn'
Explanation:

The message language module modname could not be loaded. The reason that it could not be loaded is given by the contents of registers 1 and 15, which are returned by MVS.

System action:

If the missing module is not the default language module, CICS uses the default language for messages.

If the default language module is missing, a return code is sent to the domain manager and CICS is terminated.

An exception entry is made in the trace table and a dump is taken, unless you have specifically suppressed dumps in the dump table. As this may not be a critical problem, CICS is not terminated unless the default language module cannot be loaded (even if you have specified terminate in the dump table).

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

User response:

If the default language is in operation and this is acceptable, you need not bring CICS down, or you may do so at some convenient time.

If the default language is in operation and this is not acceptable, or if the default language module itself is missing, consult the MVS messages and codes manual to check the return codes displayed in the message. The return codes indicate why the module could not be loaded.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEDM

DFHME0107
applid Module modname cannot be found in the library.
Explanation:

The message load module modname was not found in the library defined in the JCL for the CICS job. This load module is a language module for messages. It is either a module which has been defined in the SIT for messages in a particular language, or it is the default language module.

The default language is always used for messages sent to transient data queues and to consoles (providing that it is not a double-byte language, in which case the message is sent to the console in English). If the default language module is missing no messages can be delivered.

Terminals can have messages in the default language or in another chosen language. If the chosen language module is missing, terminal messages use the default language instead.

System action:

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. But since this may not be a critical error, CICS is not terminated immediately, even if you have specified this in the dump table, unless the default language module is missing, (even if you have specified terminate in the dump table).

If the missing module is not the default language module, CICS uses the default language for messages. If the default language module is missing, a return code is sent to the domain manager and CICS is terminated.

User response:

This error could have occurred because of a problem in a library or in the SIT. If the default language is in operation and this is acceptable, you need not bring CICS down, or you may do so at some convenient time.

The missing module may have been placed in the wrong library, or the wrong or misspelled module name may have been used in the right library.

If the default language is in operation and this is NOT acceptable, link the missing module into the library defined in the JCL for your CICS job by correcting whichever of the problems has occurred. You have to bring CICS down to do this.

It is also possible that an incorrect or misspelled language code has been used in the SIT. In this case, you have to bring CICS down, reinstall your chosen language code as a system initialization parameter, and restart CICS.

If you no longer need this language module, you should remove it from the SIT at the next convenient opportunity.

If the default language module is missing, CICS is terminated by the domain manager. You need to discover whether the fault is in the library or the SIT and follow the appropriate procedure above.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEDM

DFHME0108
applid Message msgno cannot be found in module modname.
Explanation:

Message msgno should have been delivered, but was not found in message language module modname.

This module is the national language module specified in the SIT by the user which gives messages in a chosen language.

System action:

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this may not be a critical error, CICS is not terminated, even if you have specified terminate in the dump table.

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

User response:

This indicates an error in CICS code. However, its impact may not be severe. For example, the error may only occur once, or you may decide to continue to run without message number msgno.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

Note that this message will appear after maintenance has been applied to the CICS message domain if there are older, pre-maintenance, versions of the DFHMETxl message modules elsewhere in the STEPLIB concatenation.

If you have just applied maintenance and are encountering this message, check for, and remove, older versions of the message modules in the STEPLIB concatenation.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEIN

DFHME0109
applid Message set setname could not be found in module modname while producing message msgno.
Explanation:

Message set setname was not found in the message language module modname.

The setname is the first two characters after the DFH in CICS messages (for example, LD or 21), which is followed by the message number.

System action:

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this may not be a critical error, CICS is not terminated, even if you have specified terminate in the dump table.

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

User response:

This indicates an error in CICS code. However, its impact may not be severe. For example, the error may only occur once, or you may decide to continue without message number msgno.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEIN

DFHME0110
applid Optional value nn is missing from insert ii for message msgno.
Explanation:

Start of changeOptional insert value nn was requested for insert ii on a call to the message domain but could not be found in the definition template for message msgno.End of change

System action:

CICS delivers the message with ??? in place of the insert ii as it cannot resolve which optional value has been requested for the insert.

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this may not be a critical error, CICS is not terminated, even if you have specified terminate in the dump table.

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

User response:

This message indicates an error in CICS code. However, its impact may not be severe. For example, the error may only occur once, or you may decide to continue without message msgno.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEBU

DFHME0111
applid Insert ii is missing for message msgno.
Explanation:

Insert ii is required for message msgno. The insert was not found.

System action:

CICS delivers the message with ??? in place of the missing insert ii.

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. But since this may not be a critical error, CICS is not terminated, even if you have specified terminate in the dump table.

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

User response:

Ensure that you have loaded the correct message language module. That is, ensure that you have the correct language specified in the NATLANG system initialization parameter and that the library concatenation accessed by your CICS job contains the correct message language module.

This message indicates a severe error in CICS code. However, its impact may not be serious. For example, the error may only occur once, or you may decide to continue without message msgno.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEBU

DFHME0112
applid Insert number ii is invalid for message msgno (code X'code').
Explanation:

Insert ii, supplied on the call to the message (ME) domain, was invalid. For example, it may have been a decimal insert with a length greater than 4 bytes.

The code X'code' uniquely identifies the occurrence of the invalid insert.

System action:

CICS delivers the message with ??? in place of the invalid insert ii.

An exception entry with code X'code' is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this may not be a critical error, CICS is not terminated, even if you have specified terminate in the dump table.

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

User response:

Ensure that you have loaded the correct message language module. That is, ensure that you have the correct language specified in the NATLANG system initialization parameter and that the library concatenation accessed by your CICS job contains the correct message language module.

This message indicates an error in CICS code. However, its impact may not be serious. For example, the error may only occur once, or you may decide to continue without message msgno being produced.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEBU

DFHME0113
applid Incorrect parameters used in call to DFHMEME for message msgno.
Explanation:

A call to the message (ME) domain for message msgno was made with an invalid combination of parameters.

System action:

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS is not terminated, even if you have specified terminate in the dump table.

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

User response:

Ensure that you have loaded the correct message language module. That is, ensure that you have the correct language specified in the NATLANG system initialization parameter and that the library concatenation accessed by your CICS job contains the correct message language module.

This message indicates a severe error in CICS code. However, its impact may not be serious. For example, the error may only occur once, or you may decide to continue without message msgno.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0114
applid There are no destinations specified for message msgno
Explanation:

There was no destination destid specified in the message language module for message msgno. This error could occur if the message language module has been corrupted or is not at the correct release level.

System action:

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this error may not be critical, CICS is not terminated even if you have specified terminate in the dump table.

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

User response:

Ensure that you have loaded the correct message language module. That is, ensure that you have the correct language specified in the NATLANG system initialization parameter and that the library concatenation accessed by your CICS job contains the correct message language module.

This message indicates a severe error in CICS code. However, its impact may not be serious. For example, the error may only occur once, or you may decide to continue without message msgno being produced. If you feel it is not critical, you can continue to run your system without message msgno until a convenient time comes to resolve the problem.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEIN

DFHME0115
applid modname Message module for language language not found. The default module modnameb is used.
Explanation:

The message language module modname for the national language language could not be found in the list of available modules. It is not found if a CICS program calls for a message in a particular language from the message domain, but the message domain cannot locate the message in that language.

The message language module may be unavailable because the LOAD for the appropriate message language module failed at initialization. In this case, there will have been an earlier message about the failed LOAD. Alternatively, the module may not be available because the language specified on the terminal definition, or userid definition, was not specified in the SIT or was specified incorrectly.

System action:

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this may not be a critical error, CICS is not terminated, even if you have specified terminate in the dump table.

All messages which should appear in language language in module modname appear in the system default language modnameb instead.

User response:

Your action depends on whether the use of the default language for messages is acceptable or not. If it is acceptable, you can delay taking any action until a convenient time. This may entail changing a terminal or userid definition if that is the cause of the problem.

If the use of the default language is not acceptable, and if module modname failed to load at initialization, take the action described for the appropriate message about a failed LOAD issued during start-up.

Otherwise, bring CICS down and specify module modname in the SIT or respecify the list of language modules as an override parameter, and restart CICS.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEIN

DFHME0116
applid (Module:modname) CICS symptom string for message msgno is symstring
Explanation:

Message msgno has been issued as the result of a possible CICS error.

Symptom string symstring has been produced to provide additional diagnostic information for IBM support.

System action:

This message accompanies message msgno and has no effect on the system action. The system action is that stated in message msgno.

User response:

Refer to the user response of message msgno which provides the necessary information to determine if the error is serious enough to be reported to IBM Support.

Destination:

Console

Modules:

DFHMEME

XMEOUT Parameters: applid, msgno,symstring, modname

DFHME0117
applid The Message User Exit point XMEOUT is unavailable for message msgno
Explanation:

The message (ME) domain was unable to use the message user exit point 'XMEOUT' when it was processing message msgno. This is probably because it was invoked too early in CICS initialization. A response of KERNERROR has been returned to the message (ME) domain from the program which invokes the user exit, DFHAPEX.

System action:

The message (ME) domain continues processing as this error is not severe. The message msgno which the message (ME) domain was trying to produce is not suppressed or rerouted by the message user exit. Instead, it is issued to the original destination defined for message msgno.

User response:

None. You cannot suppress message msgno because the error has occurred too early in initialization.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0118
applid An error has occurred when calling the Message User Exit for message msgno
Explanation:

The message (ME) domain has received an incorrect response from DFHAPEX, the program which invoked the message user exit.

System action:

The message (ME) domain will continues processing as this error is not severe. The message msgno which the message (ME) domain was trying to produce is not suppressed or rerouted but is issued to its original destination.

User response:

This message indicates a probable error in the message user exit. Ensure that your message user exit program is working properly.

However, it is possible that the user exit invoking program DFHAPEX interface has been corrupted. DFHAPEX issues an exception trace entry to indicate that there is an error, but is not able to issue its own error message via the message (ME) domain as doing so would cause CICS to loop. In this case, you will need further assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0119
applid Message msgno has an invalid {Destination | User Exit | Message Identification} component
Explanation:

The message (ME) domain has encountered an invalid component in the definition of message msgno in the message language module. The message language module may have been corrupted or be at the wrong release level.

System action:

The ME domain produces an exception trace entry and continues processing. No dump is taken.

User response:

Ensure that you are using the correct level of the message language module. That is, ensure that you have the correct language specified in the NATLANG system initialization parameter and that the library concatenation accessed by your CICS job contains the correct message language module.

This message indicates a severe error in CICS code. However, its impact may not be severe. For example, the error may only occur once, or you may decide to continue without message number msgno. If you feel it is not important, you can continue to run your system without this message until a convenient time comes to resolve the problem.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEIN

DFHME0120I
applid Message msgno has been rerouted to its original destination.
Explanation:

The message domain user exit point XMEOUT has attempted to route message msgno to a transient data (TD) queue while CICS is quiescing or terminating. After CICS shutdown has started, a message can only be rerouted to a TD queue if its original destination has a TD queue.

System action:

The message is rerouted to its original destination.

User response:

None. For programming information about the XMEOUT user exit, see the CICS Customization Guide.

Destination:

Console

Modules:

DFHMEME

XMEOUT Parameters: applid, msgno

DFHME0121
applid The {first | second} attempt at formatting message msgno, TD queue queuename has failed - {Invalid DBCS format |Unknown error}
Explanation:

The message (ME) domain was trying to produce message msgno (destined for transient data queue queuename). However, an invalid response has been returned from the message formatting routine, DFHMEFO. This error is probably due to invalid DBCS characters being found in either the message inserts or the message text. The message text is checked at definition time for mismatched shift-out and shift-in characters. However, adjacent shift-in and shift-out characters could appear in a message, for instance, if a double byte message insert has not been supplied correctly.

Start of changeThe message (ME) domain first tries to format the message into 128-byte segments. However, if the transient data queue has been defined with a different queue length, formatting is performed a second time using the new queue length. (Hence the reason for first or second attempts at formatting the message.)End of change

System action:

A dump is taken. The message domain does not issue the message being formatted. An exception trace entry is made by the formatting routine DFHMEFO.

User response:

This message indicates an error in CICS code. However, its impact may not be severe. For example, the error may only occur once, or you may decide to continue without the message msgno. If you feel it is not critical, you can continue to run your system without message msgno until a convenient time comes to resolve the problem.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0122
applid The Message User Exit has returned invalid route code information for message number msgno
Explanation:

The message user exit program has set an invalid route code as the destination of message msgno. Valid route codes are numbers 1 to 28 inclusive.

System action:

The message (ME) domain ignores the invalid route code and defaults to the original destination defined for message msgno in the message language module.

User response:

Check that your message user exit program sets valid route code information for message msgno.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0123
applid The Message User Exit has returned invalid TD queue information for message number msgno
Explanation:

The message user exit program has set an invalid queue name as the destination of the message msgno. Valid queue names consist of 4 alphanumeric characters.

System action:

The message (ME) domain ignores the invalid queue name and defaults to the original destination defined for message msgno in the message language module.

User response:

Check that your message user exit program sets valid queue name information for message msgno.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0124
applid TD is unavailable for writing message msgno to TD queue queuename
Explanation:

The message (ME) domain has tried to output message msgno to transient data queue queuename. However, transient data (TD) is not yet available. This situation may occur early in CICS initialization.

System action:

If the message destination is CDBC, the message is rerouted to the console instead. If the message destination is any other TD queue, it is lost.

User response:

The impact of this error may not be severe. For example, the error may only occur once, or you may decide to continue without message msgno. If you feel it is not critical, you can continue to run your system without message msgno until a convenient time comes to resolve the problem.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0125
applid The Message User Exit has returned an invalid return code rc for message msgno
Explanation:

The message user exit has returned a return code rc. which is neither 0 or 4 when it was processing message msgno. (A return code of 4 indicates that the message is to be suppressed.)

System action:

The message (ME) domain continues processing as normal and does not suppress or reroute the message. Instead, it issues the message as it was originally defined in the message language module.

User response:

Check that your message user exit program is working properly, and that it is passing the correct return code back to the message (ME) domain.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0126
applid Error in SYMREC invocation. Return code in R15 = X'mmmm', Reason code in R0 = X'nnnn'.
Explanation:

While handling an error, CICS tried to write a symptom record to SYS1.LOGREC.

However, a further problem was detected while attempting to invoke the SYMREC service.

Return code X'mmmm' in register 15 and reason code X'nnnn' in register 0 indicate the reason for the error. This may be one of the following.

System action:

Processing continues and a system dump may be produced.

An exception trace entry (pointid=X'0806') is made in the trace table which contains the symptom record which CICS attempted to write.

User response:

Determine whether the error was caused by a problem in the format of the symptom record produced by CICS, or by a problem in the SYMREC service.

The meanings of the return and reason codes, together with additional information about the SYMREC service can be found in the OS/390 MVS Programming: Assembler Services Reference manual.

Return codes 0010 or 0014 indicate a problem in the SYMREC service which must be reported to the MVS System Administrator.

A return code of 000C and a reason code of 0F1C indicates that the ASREXIT installation exit has prevented CICS from writing the symptom record. This could be caused by an installation error. Report the problem to your MVS system administrator.

Any other return code indicates that the symptom record is invalid to the SYMREC service.

The impact of this error need not be severe, if for example, the problem occurs only as an isolated incident or on the production of a particular message. In these cases, this message can be ignored.

However, if the problem is persistent, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEWS

DFHME0127
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 the place where the error was detected.

System action:

An exception entry is made in the trace table. For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.

A dump is taken, unless you have specifically suppressed dumps in the dump table. But since this error may not be critical, CICS is not terminated immediately, even if you have specified terminate in the dump table.

No symptom string is produced for this message because the error has occurred in a module concerned with symptom strings.

User response:

Inform the system programmer. This message indicates a severe error in CICS code. However, the impact of this error should not be severe because the module DFHMEWS is not crucial to CICS functioning.

If the problem recurs, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEWS

DFHME0128
applid Message msgno has an invalid route code.
Explanation:

The routine which issues the console message was unable to do so as it encountered an invalid route code associated with message msgno. Valid route codes are numbers from 1 through 28.

This error could only happen if the route codes have become corrupted as they are being passed to the routine which issues the console message, DFHSUWT.

System action:

The message (ME) domain issues an exception trace entry. Message msgno is not issued.

User response:

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0129
applid Unable to format console message msgno as it contains invalid DBCS characters.
Explanation:

The routine which attempted to format console message msgno was unable to do so as it was found to contain invalid double byte (DBCS) characters. For example, adjacent or unmatched pairs of shift-in and shift-out characters are invalid in a string of DBCS text.

This situation could occur if there are inserts in the message which contain, for example, a shift-out and a shift-in character with no double byte characters entered in between.

System action:

The message (ME) domain continues processing but message msgno is not issued as it cannot be formatted. The message formatting routine, DFHMEFO, issues an exception trace entry. The routine which issues console messages, DFHSUWT, also issues an exception trace entry.

User response:

Ensure that any double-byte information entered from a terminal which may be used as a message insert is entered correctly.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0130
applid Message msgno has an invalid descriptor code.
Explanation:

The routine which issues the console message was unable to do so as it encountered an invalid descriptor code associated with message msgno. Valid descriptor codes are numbers 1 through 16.

This error could only happen if the descriptor codes have become corrupted as they are being passed to the routine which issues the console message, DFHSUWT.

System action:

The message (ME) domain issues an exception trace entry. Message msgno is not issued.

User response:

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0131
applid Unable to calculate length of message msgno due to message table corruption, code(code)
Explanation:

The message (ME) domain could not calculate the length of the message msgno due to possible corruption of the message language module.

System action:

A return code is sent to the caller of the message (ME) domain. The message msgno is not issued.

User response:

Ensure that you are using the correct level of the message data module. That is, ensure that you have the correct language specified in the NATLANG system initialization parameter and that the library concatenation accessed by your CICS job contains the correct message language module.

This message indicates an error in CICS code. However, its impact may not be severe. For example, the error may only occur once, or you may decide to continue without message number msgno. If you feel it is not critical, you can continue to run your system without message msgno until a convenient time comes to resolve the problem.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0132
applid The User's Message Exit program has failed while processing message msgno
Explanation:

The user’s message exit program is either looping or has failed with a program check.

System action:

The message (ME) domain continues processing and issues message msgno to its original destination. The user exit invoking program DFHAPEX issues an exception trace entry to indicate that the user’s message exit program has failed, but it cannot issue its own error message via the message (ME) domain as doing so would cause CICS to loop.

User response:

Disable your message exit program and ensure it is working properly.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0133
applid Message msgno could not be found in module DFHMEMGT
Explanation:

The message domain was trying to issue one of its own error messages to indicate that an error had occurred in the message domain. However, the message domain was unable to find the message it was attempting to issue in its own internal message table DFHMEMGT.

System action:

An exception entry is made in the trace table by the message domain. A dump is taken, unless you have specifically suppressed dumps in the dump table. Since this may not be a critical error, CICS is not terminated, even if you have specified terminate in the dump table.

User response:

This message indicates an error in CICS code. However, its impact may not be severe.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHSUME

DFHME0134
applid Message msgno has been truncated because it was too long.
Explanation:

The message (ME) domain was trying to output message msgno, but truncated the message because it was too long. Message msgno is a conversational message to an operator which has exceeded the maximum size of 119 characters.

System action:

The ME domain truncates the message to 119 bytes before issuing it. An exception trace entry is made and a dump taken, but processing continues.

User response:

This message indicates that msgno has been incorrectly defined in the message table, or that the inserts supplied to the message have caused it to exceed the size limit imposed on conversational messages. If enough information can be obtained from the truncated message, the impact of this error may not be severe. If necessary, you can continue to run your system without this message until a convenient time comes to resolve the problem.

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

DFHME0135
applid The default language language specified in the SIT NATLANG parameter is invalid. It has been defaulted to E.
Explanation:

The default language is the first character in the NATLANG system initialization parameter. The default language language is not in the list of valid CICS language suffixes.

System action:

CICS continues with a default language of E (US English).

User response:

If you do not want a default language of E, change the first character in the NATLANG system initialization parameter to another valid CICS language suffix. See the CICS System Definition Guide for a list of valid CICS language suffixes.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMESR

DFHME0136
applid Message msgno is missing from national language module modname. Searching the English message table for the message text.
Explanation:

Message msgno cannot be issued in the specified language because the message was not found in the national language module modname.

This could be the result of a PTF containing message msgno not being applied to the module modname. In this case, the text of the missing message could be present in the English language message table DFHMET1E.

System action:

An exception entry is made in the trace table. The message domain tries to find the message in the English language message table. If the message is not found in the English table either, message DFHME0108 is issued followed by a system dump.

User response:

Run the MEU PTF update process to ensure that any new messages have been applied to your language table modname, and rebuild this table. See the CICS Operations and Utilities Guide for guidance on this.

If message DFHME0108 follows this message, there is an error in CICS code and you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEIN

DFHME0137
applid Message msgno cannot be rerouted to a transient data destination by the message user exit XMEOUT.
Explanation:

The message msgno cannot be rerouted to a transient data destination via XMEOUT because by doing so, CICS could get into a loop.

System action:

An exception entry is made in the trace table. The message (ME) domain ignores the queue destination returned by the message exit and defaults to the original destination defined for message msgno in the message language module.

User response:

Alter your message user exit program to avoid rerouting the message msgno to a transient data destination. The noreroute indicator is passed by the message domain to the exit so that the exit program can check whether or not it is valid to reroute a particular message.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHMEME

Start of changeDFHME0138End of change
Start of change Message msgno not issued by module because MVS WTO is short on storageEnd of change
Start of change
Explanation:

The message msgno cannot be written to the console because MVS is short on storage and the MVS WTO has abended with either abend code 878, 80A or 804 while trying to issue the message. The message domain module which was attempting to issue the message is module.

End of change
Start of change
System action:

An exception trace entry is written by the message domain and a dump is taken for dumpcode ME0138. Message DFHME0138 is written out in message text part of the dump summary instead of being sent to the console in order to avoid causing another abend.

End of change
Start of change
User response:

Ensure you have enough storage for MVS or reduce the storage requirements of your CICS system below 16MB. Try decreasing the limits of the CICS dynamic storage areas (DSAs), or increasing the MVS region size. To increase the MVS region size you must terminate CICS and change the MVS JCL REGION parameter. For more information about how to do this, see the CICS Performance Guide.

Note:
This message cannot be changed with the message editing utility.
End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHMEME, DFHSUMEEnd of change

Start of changeDFHME0139End of change
Start of changeapplid (Module:modname) Message msgno has been suppressed by KILL processing.End of change
Start of change
Explanation:

Message msgno has been suppressed for a task that is being killed.

The message and system dump request have been suppressed because the error has been caused by the attempt to kill the task.

End of change
Start of change
System action:

The attempt to kill the task continues.

End of change
Start of change
User response:

None

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHMEMEEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changemodname,End of changeStart of changemsgnoEnd of change

Start of change
DFHME0140
applid CICSPlex SM messages cannot be issued because the English message table mmmmmm cannot be found.
Explanation:

The message load module mmmmmm was not found in STEPLIB for the CICS job. This load module is required for CICSPlex SM messages.

System action:

An exception entry is made in the CICS trace table. Message domain stops processing this message and returns a disaster response to CICSPlex SM which in turn cannot continue to issue messages because its message module has not been loaded.

User response:

This error could have occurred because the CICSPlex SM authorized library, which contains the default message load module is not in the JCL for the CICS job. Ensure that the correct library is included in the STEPLIB concatenation of the CICS JCL and restart your CICS.

Destination:

Console

Modules:

DFHMEME

End of change
DFHME0500
PLEASE ENTER A MESSAGE NUMBER.
Explanation:

No search of the messages and codes file has been made because both the component ID and message number fields were blank when you pressed the ENTER key.

System action:

The transaction redisplays the main menu with this message.

User response:

Enter a valid message number or abend code.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHCMAC

DFHME0501
AN INVALID OPTION HAS BEEN ENTERED.
Explanation:

A key other than F3 or ENTER has been pressed.

System action:

The transaction redisplays the main menu with this message.

User response:

Enter a valid message number or abend code and press ENTER, or press a valid function key.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHCMAC

DFHME0502
THE CMAC FILE IS DISABLED.
Explanation:

The CMAC file is disabled for one of these reasons:

System action:

The transaction redisplays the main menu with this message.

User response:

If the CMAC file was defined as disabled, use the CEMT transaction to enable the file.

If the CMAC file has been disabled, determine the reason. It might have been disabled for maintenance or update.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHCMAC

DFHME0503
THE CMAC FILE CANNOT BE FOUND IN THE FCT.
Explanation:

The CMAC file cannot be found in the file control table (FCT).

System action:

The transaction redisplays the main menu with this message.

User response:

Check that the CMAC file has been defined and installed. See the CICS Transaction Server for z/OS® Installation Guide for guidance.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHCMAC

DFHME0504
RESOURCE SECURITY CHECK FAILED ON CMAC FILE.
Explanation:

The resource security check has failed.

System action:

The transaction redisplays the main menu with this message.

User response:

Ensure that the resource security class is correct.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHCMAC

DFHME0505
THE CMAC FILE IS CLOSED OR UNENABLED.
Explanation:

One of the following has occurred:

System action:

The transaction redisplays the main menu with this message.

User response:

Use the CEMT transaction to ensure that the CMAC file is in the OPEN ENABLED state.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHCMAC

DFHME0506
REQUESTED MESSAGE NUMBER/ABEND CODE NOT FOUND
Explanation:

The attempt to retrieve the specified message number or abend code has been unsuccessful.

System action:

The transaction redisplays the main menu with this message.

User response:

Ensure that the correct message number or abend code has been entered.

If no message numbers or abend codes appear to be valid, check that the correct DSName has been specified on the CMAC file definition.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHCMAC

DFHME0507
CHECK THAT THE CORRECT DSNAME IS BEING USED.
Explanation:

An attempt to retrieve a record from the CMAC data set has been unsuccessful because the CMAC DSName is incorrectly specified.

System action:

The transaction redisplays the main menu with this message.

User response:

Ensure that the correct DSName has been specified on the CMAC file definition.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHCMAC

DFHME0508
THE CMAC TRANSACTION IS INVALID FOR THE CONSOLE.
Explanation:

You have tried to invoke the CMAC transaction from a CONSOLE. This is not permitted.

System action:

The CMAC transaction ends with this message.

User response:

Ensure that CMAC is invoked from a terminal that is not being used as a CONSOLE.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHCMAC

DFHME9993I
UNABLE TO DETERMINE LENGTH OF MESSAGE msgno - response reason
Explanation:

The message DFHmsgno could not be found by the message (ME) domain in the message tables.

System action:

CICS continues.

User response:

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHMGPME

DFHME9994I
UNABLE TO RETRIEVE MESSAGE msgno - response reason
Explanation:

The message DFHmsgno could not be retrieved by the message (ME) domain from the message tables.

System action:

CICS continues.

User response:

If you are using a message table which has been created using the message editing utility, ensure that all relevant PTFs have been correctly applied.

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

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHMGPME

DFHME9996I
MESSAGE PARAMETER LIST ERROR - CHECK PLIST
Explanation:

The parameter list for the message generation process is not valid.

System action:

CICS continues but the message in error cannot be issued.

User response:

Ensure that the DFHMGT entry for the message has been built correctly.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHMGP00

DFHME9997I
MESSAGE FIND ERROR - CHECK THE MESSAGE MODULE
Explanation:

The message being issued could not be found by the message generation process in the DFHMGT table entry for this message set.

System action:

CICS continues but the message in error cannot be issued.

User response:

Ensure that an entry exists for the message number in the appropriate DFHMGT tables.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHMGP00

DFHME9998I
MESSAGE NUMBERS GREATER THAN 9999 ARE INVALID
Explanation:

The message being issued has a message number greater than 9999. Message numbers should be in the range 1 through 9999.

System action:

CICS continues but the message in error cannot be issued.

User response:

Redefine the message number.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHMGP00

DFHME9999I
THE MESSAGE INDEX MODULE 'DFHMGT' IS MISSING
Explanation:

The message generation process cannot find an index module in the DFHMGT table for the message it is trying to issue. This can occur where a message defined as being destined for either a console or a TDQ is being issued as a terminal end user message.

System action:

CICS continues but the message in error cannot be issued.

User response:

Ensure that the destination is correct for the message being issued.

Note:
This message cannot be changed with the message editing utility.
Destination:

Terminal End User

Modules:

DFHMGP00

[[ Contents Previous Page | Next Page Index ]]