DFHSTxxxx messages

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

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in CICS code.

Alternatively, unexpected data has been input, or storage has been overwritten.

Note:
There is NO applid for DFHSTUP modules.

The code aaa/bbbb is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).

System action:

An exception entry is made in the trace table.

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.

User response:

If CICS is still running, it is necessary to decide whether to terminate CICS.

Look up the MVS code, if there is one, in the 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.

Destination:

Console

Modules:

DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE, DFHSTUx (Modules within DFHSTUP), DFHSTWR, DFHSTRD

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

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

An error has been detected in module modname. The code X'code' is the exception trace point id which uniquely identifies what the error is and where the error was detected.

System action:

An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

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

User response:

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.

Destination:

Console

Modules:

DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE

XMEOUT Parameters: applid, X'code',modname

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

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHSTDM

XMEOUT Parameters: applid, X'code',modname

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

Note that no applid is included for DFHSTUP modules.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE, DFHSTUx (Modules within DFHSTUP), DFHSTWR, DFHSTRD

XMEOUT Parameters: applid, X'offset', modname

DFHST0005
applid A hardware error has occurred (module modname, code X'code'). The Time-of-Day clock is invalid.
Explanation:

Execution of the STCK machine instruction resulted in a non-zero condition code.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHSTST, DFHSTDM

XMEOUT Parameters: applid, modname,X'code'

DFHST0101I
applid The Statistics Domain has set the collection interval to 24 hours.
Explanation:

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.

System action:

Other processing continues.

User response:

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.

Destination:

Console

Modules:

DFHSTST, DFHSTDM, DFHSTTI

XMEOUT Parameter: applid

DFHST0102I
applid The Statistics Domain has cancelled interval collections.
Explanation:

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.

System action:

Other processing continues.

User response:

Start of changeRefer to any associated message for guidance on resolving the original problem.End of change

Start of changeIf no associated message has been issued, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.End of change

Start of change
Destination:

Console

End of change
Start of change
Modules:

DFHSTST, DFHSTDM, DFHSTTI

XMEOUT Parameter: applid

End of change
Start of change
DFHST0103
applid An SMF error has occurred with return code X'rc'.
Explanation:

SMF has returned to the statistics (ST) domain with an error return code X'rc' from the SMFEWTM macro.

System action:

Other CICS processing continues.

User response:

Refer to the OS/390 MVS System Management Facility (SMF) manual for a detailed explanation of the meaning of the return code.

Destination:

Console

Modules:

DFHSTST

XMEOUT Parameters: applid, X'rc'

DFHST0201 S
An attempt to open the statistics data set has failed.
Explanation:

DFHSTUP has tried to open the unloaded SMF data set but has failed.

System action:

A dump is taken and the job step is terminated.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTRD

DFHST0202 S
A read error on the statistics data set has occurred
Explanation:

A read error was encountered on the unloaded SMF data set.

System action:

A dump is taken and the job step is terminated.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTRD

DFHST0203 W
The statistics data set is empty.
Explanation:

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.

System action:

The job step is terminated.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTIN

End of changeStart of change
DFHST0204 S
Invalid record id encountered on the statistics data set.
Explanation:

An invalid record identifier recid has been encountered in the unloaded SMF data set.

System action:

A dump is taken and the job step is terminated.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTUx (modules within DFHSTUP)

End of changeStart of change
DFHST0206 S
An invalid parameter ( ) has been specified for the DFHSTUP utility.
Explanation:

One or more of the parameters specified in the SYSIN data set were incorrect.

System action:

The job step is terminated.

User response:

Correct the erroneous parameter as identified in the message and resubmit the job.

Destination:

SYSPRINT

Modules:

DFHSTUP1

End of changeStart of change
DFHST0207 W
An incomplete data record has been encountered on the statistics data set.
Explanation:

A record input from the unloaded SMF data set specifies that the data it contains is incomplete.

System action:

Processing continues.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTUx (modules within DFHSTUP)

End of changeStart of change
DFHST0208 S
An attempt to open the SYSIN data set has failed.
Explanation:

DFHSTUP has tried to open the SYSIN data set but has failed.

System action:

A dump is taken and the job step is terminated.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTRD

DFHST0209 S
A read error on the SYSIN data set has occurred.
Explanation:

A read error was encountered on the SYSIN data set.

System action:

A dump is taken and the job step is terminated.

User response:

Inform the system programmer.

To resolve the problem, collect the dumps and any relevant messages and determine why the read failed. Resubmit the job.

Destination:

SYSPRINT

Modules:

DFHSTRD

DFHST0210 I
No statistics are available for applid applid.
Explanation:

No statistics data records exist for applid applid in the unloaded SMF data set. This is because

System action:

The job step continues.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTUP1

DFHST0211 S
Processing terminated. Getmain failed with a short on storage condition.
Explanation:

The DFHSTUP utility detected an error from a GETMAIN macro while obtaining working storage. This was because DFHSTUP had exhausted the available storage.

System action:

A dump is taken and the job step terminates.

User response:

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.

Destination:

SYSPRINT

Modules:

Start of changeAll DFHSTUP modulesEnd of change

DFHST0212 S
Processing terminated. DFSORT message dataset (DD=SYSOUT) is missing.
Explanation:

The dataset used by the DFSORT utility to output its messages is missing.

System action:

A dump is taken and the job step is terminated.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTUP1

DFHST0213 S
Processing terminated. Error detected by DFSORT. Check DFSORT messages.
Explanation:

An error was detected by the DFSORT utility and the DFHSTUP utility terminated.

System action:

A dump is taken and the job step is terminated.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTUP1

DFHST0214 S
Processing terminated. Failure to obtain system time and date.
Explanation:

The DFHSTUP utility was unable to obtain the system time and date from the CICS kernel.

System action:

A dump is taken and the job step is terminated.

User response:

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

Destination:

SYSPRINT

Modules:

DFHSTUP1

DFHST0216 W
An incompatible statistics record version number , was detected by module .
Explanation:

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.

System action:

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.

User response:

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.

Destination:

SYSPRINT

Modules:

All DFHSTUP modules.

Start of changeEnd of change

Start of change
DFHST0217 S
An attempt to open the DFHSTWRK data set has failed.
Explanation:

The statistics utility program has detected an error while attempting to open the DFHSTWRK data set during non-summary statistics processing.

System action:

The statistics utility program ends abnormally.

User response:

Ensure that the DFHSTWRK data set has been specified on the job, and that the attributes of the data set are correct.

Destination:

SYSPRINT

Modules:

DFHSTU17

End of change
Start of change
DFHST0218 S
A write error has occurred on the DFHSTWRK data set.
Explanation:

The statistics utility program has detected an error while attempting to write to the DFHSTWRK data set during non-summary statistics processing.

System action:

The statistics utility program ends abnormally.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTU17

End of change
Start of change
DFHST0219 S
A read error has occurred on the DFHSTWRK data set.
Explanation:

The statistics utility program has detected an error while attempting to read from the DFHSTWRK data set during non-summary statistics processing.

System action:

The statistics utility program ends abnormally.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHSTU17

End of change
Start of change
DFHST0220 S
An attempt to open the DFHSTWRK data set has failed.
Explanation:

The statistics utility program has detected an error while attempting to open the DFHSTWRK data set while processing summary statistics.

System action:

The statistics utility program ends abnormally.

User response:

Check that the DFHSTWRK data set has been specified on the job, and that the attributes of the data set are correct.

Destination:

SYSPRINT

Modules:

DFHST17X

End of change
Start of change
DFHST0221 S
A write error has occurred on the DFHSTWRK data set.
Explanation:

The statistics utility program has detected an error while attempting to write to the DFHSTWRK data set during summary statistics processing.

System action:

The statistics utility program ends abnormally.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHST17X

End of change
Start of change
DFHST0222 S
A read error has occurred on the DFHSTWRK data set.
Explanation:

The statistics utility program has detected an error while attempting to read from the DFHSTWRK data set during summary statistics processing.

System action:

The statistics utility program ends abnormally.

User response:

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.

Destination:

SYSPRINT

Modules:

DFHST17X

End of changeEnd of change
Start of changeDFHST0223 IEnd of change
Start of changeThere are no data table statistics to report.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

Processing continues normally.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTU17, DFHST17XEnd of change

Start of change
DFHST0224 I
There are no intrapartition queues to report.
Explanation:

The transient data subsection of the DFHSTUP report entitled ‘Transient Data - Intrapartition’ contains no data.

System action:

Processing continues normally.

User response:

Take no action unless you expect TD intrapartition statistics in the DFHSTUP report.

Destination:

SYSPRINT

Modules:

DFHSTUTQ, DFHSTTQX

End of change
Start of change
DFHST0225 I
There are no extrapartition queues to report.
Explanation:

The transient data subsection of the DFHSTUP report entitled ‘Transient Data - Extrapartition’ contains no data.

System action:

Processing continues normally.

User response:

Take no action unless you expect TD extrapartition statistics in the DFHSTUP report.

Destination:

SYSPRINT

Modules:

DFHSTUTQ, DFHSTTQX

End of change
Start of change
DFHST0226 I
There are no indirect queues to report.
Explanation:

The transient data subsection of the DFHSTUP report entitled ‘Transient Data - Indirect’ contains no data.

System action:

Processing continues normally.

User response:

Take no action unless you expect TD indirect statistics in the DFHSTUP report.

Destination:

SYSPRINT

Modules:

DFHSTUTQ, DFHSTTQX

End of change
Start of changeDFHST0227 IEnd of change
Start of changeThere are no remote queues to report.End of change
Start of change
Explanation:

The transient data subsection of the DFHSTUP report entitled ‘Transient Data - Remote’ contains no data.

End of change
Start of change
System action:

Processing continues normally.

End of change
Start of change
User response:

Take no action unless you expect TD remote statistics in the DFHSTUP report.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTUTQ, DFHSTTQXEnd of change

Start of changeDFHST0228 SEnd of change
Start of changeAn invalid extract parameter ( ) has been specified for the DFHSTUP utility.End of change
Start of change
Explanation:

One or more of the parameters on the extract command specified in the SYSIN data set were incorrect.

End of change
Start of change
System action:

The job step is terminated.

End of change
Start of change
User response:

Correct the erroneous parameter as identified in the message and resubmit the job.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTUP1End of change

Start of changeDFHST0229 WEnd of change
Start of changeA duplicate extract command has been detected. Command ignored.End of change
Start of change
Explanation:

A duplicate EXTRACT USERPROGRAM command has been detected.

End of change
Start of change
System action:

The duplicate command is ignored and the extract exit program specified on the first command is used. Processing continues.

End of change
Start of change
User response:

Remove the erroneous command.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTUP1End of change

Start of changeDFHST0230 EEnd of change
Start of changeUnable to locate the extract library member member.End of change
Start of change
Explanation:

The member is not in the libraries named in the JCL.

End of change
Start of change
System action:

The utility terminates processing of the command that required access to library member member.

End of change
Start of change
User response:

Ensure that the member is correctly link-edited into the library and resubmit the job.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTUPEnd of change

Start of changeDFHST0231 EEnd of change
Start of changeUnable to load the extract library member member.End of change
Start of change
Explanation:

DFHSTUP could not load the extract library member member.

End of change
Start of change
System action:

The utility terminates processing of the command that required access to the library member.

End of change
Start of change
User response:

Ensure that the member is correctly link-edited into the library and resubmit the job.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTUPEnd of change

Start of changeDFHST0232 SEnd of change
Start of change An abend (code aaa/bbbb) has occurred in extract exit program modname. Extract exit processing has been terminated.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

The EXTRACT command is terminated.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTUPEnd of change

Start of changeDFHST0233 IEnd of change
Start of changeDFHSTUP report suppressed. Report options requested only an EXTRACT userprogram to be invoked.End of change
Start of change
Explanation:

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

End of change
Start of change
System action:

EXTRACT processing continues.

End of change
Start of change
User response:

If a DFHSTUP report is required in addition to the report produced from the specified EXTRACT exit, specify the necessary DFHSTUP reporting options.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTUPEnd of change

Start of changeDFHST0234 SEnd of change
Start of changeEXTRACT terminated at user's request RC=retcode.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

Execution of the utility EXTRACT command is terminated.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTUPEnd of change

Start of changeDFHST0235 SEnd of change
Start of change An abend (code aaa/bbbb) has occurred in program modname.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

The DFHSTUP command is terminated.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHSTUPEnd of change

[[ Contents Previous Page | Next Page Index ]]