An abend or program check has occurred in module modname. This implies an error in CICS code. Alternatively, it is possible that 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).
An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table. CICS continues unless you have specified in the dump table that CICS should terminate.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If CICS is still running, it is necessary to decide whether to terminate CICS.
Look up the MVS code, if there is one, in the OS/390 MVS System Codes manual.
Next, look up the CICS alphanumeric code in this manual. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some guidance concerning a user response.
If module modname is not crucial to the running of your CICS system, you have the option to continue to run and to bring CICS down at a convenient time to resolve the problem.
If you cannot run without the full use of module modname you should bring CICS down in a controlled shutdown.
You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.
Console
DFHMNDM, DFHMNMN, DFHMNNT, DFHMNSR, DFHMNST, DFHMNSU, DFHMNTI, DFHMNUE, DFHMNXM
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
An error has been detected in module modname.
The code X'code' is the exception trace point id
which uniquely identifies what the error is and
where the error was detected.
For further information about CICS exception trace entries,
refer to the CICS Problem Determination Guide.
An exception entry (code 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 will continue unless you have specified in the dump table that CICS should terminate.
If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message will be issued to this effect.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Inform the system programmer. 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 module you should bring CICS down in a controlled shutdown.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHMNDM, DFHMNMN, DFHMNNT, DFHMNSR, DFHMNST, DFHMNSU, DFHMNTI, DFHMNUE, DFHMNXM
XMEOUT Parameters: applid, X'code',modname
A CICS 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 where the error was detected.
An exception entry is made in the trace table (code code in the message). A system dump is taken, unless you have specifically suppressed dumps in the dump table. This is a critical error.
If DFHMNDM issues this message, CICS terminates, even if you have specified in the dump table that CICS should not terminate.
If DFHMNMN, DFHMNST or DFHMNXM issues this message, an exception trace and a system dump is taken and CICS continues.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If CICS has been terminated by another module, look out for the relevant termination messages (from, for example, the domain manager), and look up the user response for these messages.
If CICS is still running, the problem may be a temporary one which will right itself if more storage becomes available. If you can manage without module modname, you may decide to continue 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 all CICS modules, you should bring CICS down in a controlled shutdown.
Try increasing the size limits of the DSAs or EDSAs. See the CICS System Definition Guide or the CICS Performance Guide for further information on CICS storage.
Console
DFHMNDM, DFHMNMN, DFHMNST, DFHMNXM
XMEOUT Parameters: applid, X'code',modname
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.
An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table. This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Notify the system programmer. If CICS has not been terminated, it will be 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 here. Usually, CICS will purge 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 module modname will be terminated and CICS will continue.
But if you have declared ICVR=0 in the SIT and you consider that module modname has gone into a loop, you will 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 will 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 will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHMNDM, DFHMNMN, DFHMNSR, DFHMNST, DFHMNSU, DFHMNTI, DFHMNUE, DFHMNXM
XMEOUT Parameters: applid, X'offset', modname
A hardware error has occurred during the running of
module modname.
The MVS Store Clock facility is the timing mechanism for
the operating system.
The code X'code' is the exception trace point ID
which uniquely identifies the place where the error was detected.
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 will continue unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message will be issued to this effect.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Notify the system programmer. This is in all probability a hardware error and you should in the first instance investigate the MVS Store Clock and find out whether it is working properly. If this is the cause, you should take the appropriate action to have it repaired or replaced.
In the unlikely event that this is not a hardware problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHMNDM, DFHMNMN, DFHMNST, DFHMNUE, DFHMNXM
XMEOUT Parameters: applid, modname,X'code'
The monitoring domain authorized services routine issued a SMFEWTM macro to write a record to the MVS system management facilities (SMF) data set and encountered a non-zero return code.
The request is ignored and the SMF record is lost. An exception entry is made in the trace table. CICS operation continues.
If the same error condition occurs continuously, the error messages are suppressed but tracing continues. The message is reissued if a different error condition occurs or if a zero return code has been received since the message was last issued.
Consult the OS/390 MVS System Programming Library: System Management Facilities (SMF) manual for a detailed explanation of the return codes.
Console
DFHMNSU
XMEOUT Parameters: applid, X'rc'
The monitoring control table for suffix xx could not be found in the library described by the DFHRPL DD statement. This suffix is specified as a system initialization parameter.
Control is returned to the parameter manager for interaction with the operator. Further action depends upon which PARMERR= parameter is specified. The operator may enter another suffix or continue with system initialization.
If initialization continues without an override, monitoring domain uses the default monitoring control table.
There are three likely causes of this error:
Ensure that the suffix specified is correct and that a library described in the DFHRPL DD statement contains a copy of the named monitoring control table.
If the suffix is incorrect and PARMERR=INTERACT is specified, the operator is prompted to enter an alternative suffix.
If the suffix is incorrect and PARMERR=IGNORE is specified, the monitoring domain uses the default monitoring control table.
If the monitoring control table is missing or misspelled and you want to reinstall it, CICS has to be terminated. Reassemble the monitoring control table into the relevant library.
Console
DFHMNSR
XMEOUT Parameters: applid, xx
The monitoring domain has determined the monitoring control table suffix xx from the last CICS execution, but was unable to locate the monitoring control table in the library described by the DFHRPL DD statement and no override suffix has been specified.
Subsequent executions of CICS will continue to use the suffix specified in the message until it is changed in the SIT.
Initialization continues with the monitoring domain using the default monitoring control table.
Ensure that a library described in the DFHRPL DD statement contains a copy of the named monitoring control table. If the monitoring control table is missing, it must have been deleted. If you want to reinstall the table, CICS must be terminated. Reassemble the monitoring control table into the relevant library.
Console
DFHMNDM
XMEOUT Parameters: applid, xx
The monitoring domain is initializing with default monitoring control table settings. This occurs:
System initialization continues.
None.
Console
DFHMNDM
XMEOUT Parameter: applid
The monitoring domain has attempted to re-establish the status of the monitoring classes and the monitoring control table suffix under which it was running during the last execution of CICS. But it was unable to successfully read the record from the global catalog.
An exception entry is made in the trace table.
System initialization continues with the supplied system initialization parameters.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Investigate the cause of the error using any dump or other diagnostic messages which have been issued (for example, from VSAM or MVS).
If the problem has been caused by an I/O error, there will be an earlier CICS message from the catalog. Follow the user response for this message.
If the problem has been caused by an invalid data length, there will be an exception trace entry in the trace table.
Console
DFHMNDM
XMEOUT Parameter: applid
The monitoring domain has attempted to update either the status of the monitoring classes or the monitoring control table suffix in the CICS global catalog, but was unable to successfully complete the request.
An exception entry is made in the trace table, and CICS operation continues with the updated values. Since the updates are not saved across a restart, the subsequent execution of CICS will restart with values recorded before the updates were applied.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Investigate the cause of the error using any dump or other diagnostic messages which have been issued (for example, from VSAM or MVS).
If the problem has been caused by an I/O error, there will be an earlier CICS message from the catalog. Follow the user response for this message.
If the problem has been caused by an invalid data length, there is an exception trace entry in the trace table.
Console
DFHMNSU
XMEOUT Parameter: applid
The monitoring control table with the suffix xx is used for this CICS run.
Processing continues.
None. You can suppress this message with the system initialization parameter, MSGLVL=0.
Console
DFHMNDM
XMEOUT Parameters: applid, xx
The CICS monitoring facility is currently active for this run of CICS.
Processing continues.
None. You can suppress this message with the system initialization parameter, MSGLVL=0.
Console
DFHMNDM
XMEOUT Parameter: applid
The CICS monitoring facility is currently inactive for this run of CICS.
Processing continues.
None. You can suppress this message with the system initialization parameter, MSGLVL=0.
Console
DFHMNDM
XMEOUT Parameter: applid
A SYSIN parameter has been encountered that does not contain an equals sign. Equals signs are mandatory for every keyword supported by the monitoring dictionary utility.
The job step is terminated with a return code of 12.
Correct the SYSIN keyword that does not have an equals sign and resubmit the job. For further guidance on the syntax of DFHMNDUP keywords, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
Following the equals sign of the MCT= keyword there must be a 2-character operand or a delimiter. Neither has been found. The 2-character operand is treated as the suffix for an MCT to load.
The job step is terminated with a return code of 12.
Correct the MCT= keyword with a valid operand or delimiter.
If you do not wish to have a dictionary record constructed from a particular MCT, you can use a default MCT image by specifying a blank or a comma after the equals sign, or by specifying MCT=NO. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
A SYSID of greater than 4 characters, or a SYSID keyword without an operand has been specified.
The job step is terminated with a return code of 12.
Specify a valid SYSID of up to 4 characters. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
A generic APPLID (GAPPLID) of greater than 8 characters, or a GAPPLID keyword without an operand has been specified.
The job step is terminated with a return code of 12.
Specify a valid GAPPLID of up to 8 characters. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
A specific APPLID (SAPPLID) of greater than 8 characters has been specified.
The job step is terminated with a return code of 12.
Specify a valid SAPPLID of up to 8 characters or allow the SAPPLID to default to the GAPPLID by not specifying SAPPLID. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
The date has been specified incorrectly. There are three possible reasons for this:
The job step is terminated with a return code of 12.
Ensure that the date is in the format ‘yyddd’ or ‘yyyyddd’ and that the values are valid.
If you want DATE to default to the current date, do not specify this parameter. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
The time has been specified incorrectly. There are three possible reasons for this:
The job step is terminated with a return code of 12.
Ensure that the time specified is in the format ‘hhmmss’ and that the values are valid.
If you want TIME to default to the current time, do not specify this parameter. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
A SYSIN parameter has been processed and found to contain an unrecognized keyword.
The job step is terminated with a return code of 12.
Rename the unrecognized keyword. See the CICS Operations and Utilities Guide. for a complete list of supported keywords. Also, ensure that there are no blanks preceding any of the keywords in the SYSIN data set.
SYSPRINT
DFHMNDUP
There are no SYSIN parameters specified in the JCL.
The job step is terminated with a return code of 12.
Check the JCL for the existence of SYSIN parameters. If SYSIN does not exist or has no parameters, see the CICS Operations and Utilities Guide for guidance on coding DFHMNDUP parameters.
SYSPRINT
DFHMNDUP
DFHMNDUP attempted to load ‘DFHMCTxx’ from STEPLIB, where ‘xx’ is the suffix provided via the MCT= keyword. This MCT was not found in the STEPLIB concatenation.
The job step is abended with a dump.
Ensure that the MCT suffix is correct and that the library that contains it is in the STEPLIB concatenation for the job step.
Console
DFHMNDUP
An MVS GETMAIN for the utilities global storage has failed. There is not enough MVS storage below the line available in the region.
The job step is terminated with a return code of 12.
Increase the REGION= parameter of your JCL and try again. If this fails, consult your MVS system programmer.
SYSPRINT
DFHMNDUP
An MVS GETMAIN for the 32KB record buffer storage has failed. There is not enough MVS storage below the line available in the region.
The job step is terminated with a return code of 12.
Increase the REGION= parameter of your JCL and try again. If this fails, consult your MVS system programmer.
SYSPRINT
DFHMNDUP
Because DATE and/or TIME have not been specified, DFHMNDUP has attempted to retrieve the current DATE and/or TIME from MVS using the TIME macro. The TIME macro has reported that the MVS clocks are damaged.
The job step is terminated with a return code of 12.
Inform your MVS system programmer of the failure.
SYSPRINT
DFHMNDUP
DFHMNDUP parameter syntax requires keyword/operand pairs to be separated by a delimiter in the form of a comma or a blank space. A delimiter has been found missing from a keyword/operand.
The job step is terminated with a return code of 12.
If the SYSIN data set has been coded such that there are multiple parameters on one line, then ensure that there is one blank or one comma between each parameter. If the SYSIN data set has been coded such that there is only one parameter on a line, ensure that it is terminated with a blank or a comma. For further guidance on the syntax of DFHMNDUP parameters, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
The two mandatory parameters are for the generic APPLID (GAPPLID) and the MVS system identifier (SYSID). These two parameters have not been specified and there are no defaults.
The job step is terminated with a return code of 12.
Specify the following:
For further guidance on the syntax of DFHMNDUP parameters, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
A JOBNAME has been specified with more than eight characters.
The job step is terminated with a return code of 12.
Specify a valid JOBNAME of up to eight characters. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
The JOBDATE parameter has been specified incorrectly. There are three possible reasons for this:
The job step is terminated with a return code of 12.
Ensure that JOBDATE consists of valid characters in the format ‘yyddd’ or ‘yyyyddd’.
If you want JOBDATE to default to the current date, do not specify this parameter. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
The JOBTIME parameter has been specified incorrectly. There are three possible reasons for this:
The job step is terminated with a return code of 12.
Ensure that JOBTIME consists of valid characters in the format ‘hhmmss’.
If you want JOBTIME to default to the current time, do not specify this parameter. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
A USERID has been specified with more than eight characters.
The job step is terminated with a return code of 12.
Specify a valid USERID of up to eight characters. For further guidance, see the CICS Operations and Utilities Guide.
SYSPRINT
DFHMNDUP
The SYSPRINT file cannot be opened because the SYSPRINT DD statement is missing or incorrectly defined.
The job step is terminated with a return code of 12.
Ensure that the SYSPRINT DD statement has been correctly defined. For further guidance, see the CICS Operations and Utilities Guide.
Console
DFHMNDUP
The SYSIN file cannot be opened because the SYSIN DD statement is missing or incorrectly defined.
The job step is terminated with a return code of 12.
Ensure that the SYSIN DD statement has been correctly defined. For further guidance, see the CICS Operations and Utilities Guide.
Console
DFHMNDUP