An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in 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).
An exception entry is made in the trace table.
For modules DFHSTST and DFHSTTI, a dump is taken and the collection interval is set to 24 hours. Message DFHST0101 is also issued.
For module DFHSTDM, the action depends on the initialization error action value which is used by the domain (DM) manager. The usual action is to terminate CICS with a dump.
For module DFHSTUE, processing continues.
For modules DFHSTWR, DFHSTRD, and DFHSTUx (modules within DFHSTUP), the job step is terminated with a dump.
For ALL modules, a system dump is taken, unless you have specifically suppressed dumps in the dump table.
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. Then look up the CICS alphanumeric code in this manual. This tells you, for example, whether the error was a program check, an abend, a runaway or a recovery percolation, and may give you some guidance concerning user response.
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.
Console
DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE, DFHSTUx (Modules within DFHSTUP), DFHSTWR, DFHSTRD
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.
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 is 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 will depend on the importance of the function being executed at the time of the error.
For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.
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.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE
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.
This error has occurred above the 16MB line.
An exception entry is made in the trace table (code X'code' in the message). 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.
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 is issued to this effect.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Inform the system programmer. 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 suggested 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. If CICS is not already terminated, you need to bring CICS down to do this. See the CICS System Definition Guide or the CICS Performance Guide for further information on CICS storage.
Console
DFHSTDM
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.
Note that no applid is included for DFHSTUP modules.
An exception entry is made in the trace table.
For modules DFHSTST and DFHSTTI, a system dump is taken and the collection interval is set to 24 hours. Message DFHST0101 will also be issued.
For module DFHSTDM, the action depends on the initialization error action value which is used by the domain (DM) manager. The usual action will be to terminate CICS with a dump.
For module DFHSTUE, processing continues.
For modules DFHSTWR, DFHSTRD, and DFHSTUx (modules within DFHSTUP), the job step is terminated with a dump.
For ALL modules, a system dump is taken, unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Notify the system programmer. 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 here. 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 module modname is terminated and CICS continues.
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 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
DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE, DFHSTUx (Modules within DFHSTUP), DFHSTWR, DFHSTRD
XMEOUT Parameters: applid, X'offset', modname
Execution of the STCK machine instruction resulted in a non-zero condition code.
A system dump is taken and interval collections are cancelled. Message DFHST0102 is also issued.
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
DFHSTST, DFHSTDM
XMEOUT Parameters: applid, modname,X'code'
A problem has been detected by, or has been passed back to, the statistics (ST) domain. As a result, the collection interval has been set to the maximum value. The end-of-day collection time is unchanged.
A message explaining the problem has already been issued by the module in error.
Other processing continues.
Refer to the associated message for guidance on resolving the original problem.
Use CEMT SET STATISTICS to reset the interval when the problem has been resolved.
Console
DFHSTST, DFHSTDM, DFHSTTI
XMEOUT Parameter: applid
A problem has been detected by, or has been passed back to, the statistics (ST) domain. A message explaining the problem may have already been issued by the module in error.
To reduce the occurrence of this problem, the interval collections have been cancelled. The end-of-day collection time is unchanged.
Other processing continues.
Refer to any associated message for guidance on resolving the
original problem.
If no associated message has been issued, you will need further
assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHSTST, DFHSTDM, DFHSTTI
XMEOUT Parameter: applid
SMF has returned to the statistics (ST) domain with an error return code X'rc' from the SMFEWTM macro.
Other CICS processing continues.
Refer to the OS/390 MVS System Management Facility (SMF) manual for a detailed explanation of the meaning of the return code.
Console
DFHSTST
XMEOUT Parameters: applid, X'rc'
DFHSTUP has tried to open the unloaded SMF data set but has failed.
A dump is taken and the job step is terminated.
Ensure that the JCL for the job is correct. A sample set of JCL to execute the DFHSTUP utility is contained in the CICS Operations and Utilities Guide.
If incorrect JCL is not the cause of the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
SYSPRINT
DFHSTRD
A read error was encountered on the unloaded SMF data set.
A dump is taken and the job step is terminated.
Inform the system programmer. First check that the JCL for the job is correct. A sample set of JCL to execute the DFHSTUP utility is contained in the CICS Operations and Utilities Guide. Resubmit the job.
SYSPRINT
DFHSTRD
An end-of-file condition was detected during the first attempt to read the unloaded SMF data set, or the unloaded SMF dataset contained no CICS statistics from any CICS system.
The job step is terminated.
The most likely cause is an error in the JCL which unloads the SMF dataset. First check that the JCL is correct. A sample set of JCL to unload the SMF dataset is contained in the CICS Operations and Utilities Guide. Also check that you have unloaded the correct SMF dataset. Resubmit the job.
SYSPRINT
DFHSTIN
An invalid record identifier recid has been encountered in the unloaded SMF data set.
A dump is taken and the job step is terminated.
Check that the unloaded SMF data set contains statistics records. CICS statistics records are of SMF record type 110, sub-type 2. For further information, see the CICS Data Areas.
If the SMF data set does contain statistics records, the most likely cause of the problem is a corrupted SMF dataset. Unload the SMF dataset again and rerun the DFHSTUP utility. If the problem persists, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
SYSPRINT
DFHSTUx (modules within DFHSTUP)
One or more of the parameters specified in the SYSIN data set were incorrect.
The job step is terminated.
Correct the erroneous parameter as identified in the message and resubmit the job.
SYSPRINT
DFHSTUP1
A record input from the unloaded SMF data set specifies that the data it contains is incomplete.
Processing continues.
For an incomplete data record to have been encountered, there must have been an error in the running of CICS. This should result in an exception trace and perhaps a dump being issued.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
SYSPRINT
DFHSTUx (modules within DFHSTUP)
DFHSTUP has tried to open the SYSIN data set but has failed.
A dump is taken and the job step is terminated.
Ensure that the JCL for the job is correct. A sample set of JCL to execute the DFHSTUP utility is contained in the CICS Operations and Utilities Guide.
If incorrect JCL is not the cause of the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
SYSPRINT
DFHSTRD
A read error was encountered on the SYSIN data set.
A dump is taken and the job step is terminated.
Inform the system programmer.
To resolve the problem, collect the dumps and any relevant messages and determine why the read failed. Resubmit the job.
SYSPRINT
DFHSTRD
No statistics data records exist for applid applid in the unloaded SMF data set. This is because
The job step continues.
Check that you have specified the correct applid. If necessary, respecify
the correct applid.
Check that you have unloaded the correct SMF data set.
If necessary, unload the correct SMF data set.
If you have specified the correct applid and unloaded
the correct SMF data set, then there are no statistics data records for applid applid.
SYSPRINT
DFHSTUP1
The DFHSTUP utility detected an error from a GETMAIN macro while obtaining working storage. This was because DFHSTUP had exhausted the available storage.
A dump is taken and the job step terminates.
Check that you have specified the correct REGION size on the EXEC JCL command used to execute the DFHSTUP utility. A sample set of JCL to execute the DFHSTUP utility is contained in the CICS Operations and Utilities Guide.
If you have specified the correct REGION size, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
SYSPRINT
All DFHSTUP modules
The dataset used by the DFSORT utility to output its messages is missing.
A dump is taken and the job step is terminated.
Check the JCL used to execute the DFHSTUP utility to ensure that the SYSOUT DD was correctly specified. A sample set of JCL to execute the DFHSTUP utility is contained in the CICS Operations and Utilities Guide.
If you have specified the correct SYSOUT DD statement, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
SYSPRINT
DFHSTUP1
An error was detected by the DFSORT utility and the DFHSTUP utility terminated.
A dump is taken and the job step is terminated.
The user must inspect the DFSORT message dataset and search for messages indicating the reason for the failure of the DFSORT utility. A detailed explanation of the messages produced by DFSORT can be found in the DFSORT Application Programming Guide (SC33-4035).
After analyzing the DFSORT error message, take the appropriate corrective actions and resubmit the job.
SYSPRINT
DFHSTUP1
The DFHSTUP utility was unable to obtain the system time and date from the CICS kernel.
A dump is taken and the job step is terminated.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
SYSPRINT
DFHSTUP1
The statistics utility program has detected that a statistics record has a version number which is incompatible with the version number expected by the DFHSTUP utility.
The statistics record containing the invalid version number is ignored. Statistics records immediately following which are of the same type and which also contain an invalid version number are also ignored. Processing continues.
Obtain a dump of the SMF data set. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
SYSPRINT
All DFHSTUP modules.
The statistics utility program has detected an error while attempting to open the DFHSTWRK data set during non-summary statistics processing.
The statistics utility program ends abnormally.
Ensure that the DFHSTWRK data set has been specified on the job, and that the attributes of the data set are correct.
SYSPRINT
DFHSTU17
The statistics utility program has detected an error while attempting to write to the DFHSTWRK data set during non-summary statistics processing.
The statistics utility program ends abnormally.
Ensure that the DFHSTWRK data set has been specified on the job, that the attributes of the data set are correct, and that the data set is large enough.
SYSPRINT
DFHSTU17
The statistics utility program has detected an error while attempting to read from the DFHSTWRK data set during non-summary statistics processing.
The statistics utility program ends abnormally.
Check that the DFHSTWRK data set has been specified on the job, that the attributes of the data set are correct, and that the data set is large enough.
SYSPRINT
DFHSTU17
The statistics utility program has detected an error while attempting to open the DFHSTWRK data set while processing summary statistics.
The statistics utility program ends abnormally.
Check that the DFHSTWRK data set has been specified on the job, and that the attributes of the data set are correct.
SYSPRINT
DFHST17X
The statistics utility program has detected an error while attempting to write to the DFHSTWRK data set during summary statistics processing.
The statistics utility program ends abnormally.
Check that the DFHSTWRK data set has been specified on the job, that the attributes of the data set are correct, and that the data set is large enough.
SYSPRINT
DFHST17X
The statistics utility program has detected an error while attempting to read from the DFHSTWRK data set during summary statistics processing.
The statistics utility program ends abnormally.
Check that the DFHSTWRK data set has been specified on the job, that the attributes of the data set are correct, and that the data set is large enough.
SYSPRINT
DFHST17X
The file subsection of the DFHSTUP report entitled ‘Data Table Requests Information’ only contains formatted information if the data currently being processed contains statistics records for files accessed as data tables. This message is written to the DFHSTUP report, when the utility program detects that there are no data table statistics in this section of the statistics report.
Processing continues normally.
Take no action unless you expect data table statistics in the DFHSTUP report. In this case, ensure that the data tables feature is in use during the time period covered by the statistics being processed.
SYSPRINT
DFHSTU17, DFHST17X
The transient data subsection of the DFHSTUP report entitled ‘Transient Data - Intrapartition’ contains no data.
Processing continues normally.
Take no action unless you expect TD intrapartition statistics in the DFHSTUP report.
SYSPRINT
DFHSTUTQ, DFHSTTQX
The transient data subsection of the DFHSTUP report entitled ‘Transient Data - Extrapartition’ contains no data.
Processing continues normally.
Take no action unless you expect TD extrapartition statistics in the DFHSTUP report.
SYSPRINT
DFHSTUTQ, DFHSTTQX
The transient data subsection of the DFHSTUP report entitled ‘Transient Data - Indirect’ contains no data.
Processing continues normally.
Take no action unless you expect TD indirect statistics in the DFHSTUP report.
SYSPRINT
DFHSTUTQ, DFHSTTQX
The transient data subsection of the DFHSTUP report entitled ‘Transient Data - Remote’ contains no data.
Processing continues normally.
Take no action unless you expect TD remote statistics in the DFHSTUP report.
SYSPRINT
DFHSTUTQ, DFHSTTQX
One or more of the parameters on the extract command specified in the SYSIN data set were incorrect.
The job step is terminated.
Correct the erroneous parameter as identified in the message and resubmit the job.
SYSPRINT
DFHSTUP1
A duplicate EXTRACT USERPROGRAM command has been detected.
The duplicate command is ignored and the extract exit program specified on the first command is used. Processing continues.
Remove the erroneous command.
SYSPRINT
DFHSTUP1
The member is not in the libraries named in the JCL.
The utility terminates processing of the command that required access to library member member.
Ensure that the member is correctly link-edited into the library and resubmit the job.
SYSPRINT
DFHSTUP
DFHSTUP could not load the extract library member member.
The utility terminates processing of the command that required access to the library member.
Ensure that the member is correctly link-edited into the library and resubmit the job.
SYSPRINT
DFHSTUP
During processing of an EXTRACT command, a program check or abend aaa/bbbb has occurred in extract exit program modname.
The code aaa/bbbb is, if applicable, a 3-digit hexadecimal MVS system completion code aaa (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The 4-digit code bbbb, which follows aaa is, if applicable, a user abend code produced by the extract exit program. If the user abend code is not applicable, this field is filled with four hyphens.
The EXTRACT command is terminated.
For a program check, refer to prior messages to resolve the error in the extract exit program. For a user abend code consult the relevant documentation of the user exit program to determine the error.
SYSPRINT
DFHSTUP
No report was produced by DFHSTUP due to the fact that an EXTRACT exit program was specified and no other report options. DFHSTUP invokes the exit program to process the statistics records and suppresses all its reporting
EXTRACT processing continues.
If a DFHSTUP report is required in addition to the report produced from the specified EXTRACT exit, specify the necessary DFHSTUP reporting options.
SYSPRINT
DFHSTUP
A batch job has issued a DFHSTUP utility EXTRACT command. The EXTRACT command has been terminated because of a non-zero value in register 15 on return from an extract user exit program.
Execution of the utility EXTRACT command is terminated.
Determine the cause of the error detected by the user exit program using the return code retcode provided and the relevant documentation of the user exit program.
SYSPRINT
DFHSTUP
During processing of an DFHSTUP command, a program check or abend aaa/bbbb has occurred in module modname.
The code aaa/bbbb is, if applicable, a 3-digit hexadecimal MVS system completion code aaa (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The 4-digit code bbbb, which follows aaa is, if applicable, an Language Environment abend code. If the abend code is not applicable, this field is filled with four hyphens.
The DFHSTUP command is terminated.
Look up the MVS code, if there is one, in the OS/390 MVS System Codes manual. Look up the Language Environment abend code in the Language Environment Debugging and Run-Time Messages manual.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
SYSPRINT
DFHSTUP