DFHPDxxxx messages

DFHPD0101
Pointer to xxxxxxxx at offset X'offset' is invalid.
Explanation:

A pointer to a block of type xxxxxxxx, whose address is at offset offset in the block just formatted, is invalid.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

Either the pointer to the required area was corrupted, Start of changethe pointer has not been initialized, or the address was valid but the area was not present in the dump. In the latter case, if the area is essential for diagnosing the problem, a fresh dump which includes the missing area has to be obtained.End of change

Start of changeIt is possible that the storage is present in the dump, and the pointer has been initialized with its address, but the storage has not been referred to by CICS code. You can check this by browsing the storage in the dump at this address.End of change

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

SYSPRINT

Modules:

Start of changeDFHDUFFT, DFHDUFUT, DFHXRDUFEnd of change

DFHPD0102
Pointer to xxxxxxxx at offset X'offset' is zero.
Explanation:

A pointer to a block of type xxxxxxxx, whose address is at offset offset in the block just formatted, is zero.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

The area may have been corrupted or not set up correctly. Start of changeIt is also possible that the zero value is valid. This depends on the circumstances or timing of the dumps collection; for example, a zero value is valid before the block is initialized.End of change

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

SYSPRINT

Modules:

Start of changeDFHDUFFT, DFHDUFUT, DFHXRDUFEnd of change

DFHPD0103
xxxxxxxx address X'address' is invalid.
Explanation:

The address address of a block of type xxxxxxxx is invalid.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

Either the pointer to the required area was corrupted, Start of changethe pointer has not been initialized, or the address was valid but the area was not present in the dump. In the latter case, if the area is essential for diagnosing the problem, a fresh dump which includes the missing area has to be obtained.End of change

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

SYSPRINT

Modules:

Start of changeDFHDUFFT, DFHDUFUT, DFHXRDUFEnd of change

DFHPD0104
Address of xxxxxxxx is zero.
Explanation:

The address of a block of type xxxxxxxx is zero.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

The area may have been corrupted or not set up correctly. Start of changeIt is also possible that the zero value is valid. This depends on the circumstances or timing of the dumps collection; for example, a zero value is valid before the block is initialized.End of change

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

SYSPRINT

Modules:

Start of changeDFHDUFFT, DFHDUFUT, DFHXRDUFEnd of change

DFHPD0105
A loop has been detected. xxxxxxxx at address X'address' already encountered.
Explanation:

The formatting program avoids loops resulting from corrupted control block chains by checking for duplicate addresses. The block xxxxxxxx at address address has already been encountered and may already have been formatted.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

Check the chain fields in control blocks of the same type which have already been processed. Start of changeOtherwise the problem may be caused by the timing of the dumps collection, if for example this occurs before the block is initialized.End of change

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

SYSPRINT

Modules:

Start of changeDFHDUFFT, DFHDUFUTEnd of change

DFHPD0106
An error has occurred while formatting xxxxxxxx.
Explanation:

An error has occurred during the formatting of a block of type xxxxxxxx.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

If no data has been formatted for the block then the block address was probably invalid. In this case see message DFHPD0101.

If part of the block has been successfully formatted then it is possible that the length of the control block is incorrect. The length may have been overwritten which may provide a clue to the problem.

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

SYSPRINT

Modules:

Start of changeDFHDUFUT, DFHDUFFTEnd of change

DFHPD0107
Eyecatcher for xxxxxxxx at X'address' is invalid.
Explanation:

The eyecatcher field of a control block of type xxxxxxxx at address address has an incorrect value.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

Investigate why the eyecatcher has been overwritten or why the control block has not been set up correctly. For more information on how to solve storage overwrite problems, see the CICS® Problem Determination Guide.

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

SYSPRINT

Modules:

Start of changeDFHDUFFT, DFHDUFUTEnd of change

DFHPD0108
Unable to start browse of xxxxxxxx.
Explanation:

An error has occurred when attempting to start browsing a table of type xxxxxxxx.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

This error may be due to the Table Manager Program (TMP) control blocks being invalid. Check the TMP control blocks for the table in question.

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

SYSPRINT

Modules:

Start of changeDFHDUFUTEnd of change

DFHPD0109
Unable to get next entry in xxxxxxxx table.
Explanation:

An error has occurred when attempting to access the next entry in a table of type xxxxxxxx.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

This error may be due to the Table Manager Program (TMP) control blocks being invalid. Check the TMP control blocks for the table in question.

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

SYSPRINT

Modules:

Start of changeDFHDUFUTEnd of change

DFHPD0110
Unable to access data for xxxxxxxx
Explanation:

The Interactive Problem Control System (IPCS) service routine ADPLMEMA was unable to find the requested data for control block xxxxxxxx in the dump.

System action:

Dump formatting continues after skipping any sections impacted by the lack of data.

User response:

Either the pointer to the required area was corrupted, which may in itself be a clue to the problem, or the address was valid but the area was not present in the dump. In the latter case, if the area is essential for diagnosing the problem obtain a fresh dump which includes the missing area.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDX1End of change

DFHPD0111I
Pointer to xxxxxxxx at offset X'offset' is zero.
Explanation:

A pointer to a block of type xxxxxxxx, whose address is at offset offset in the block just formatted, is zero.

System action:

Dump formatting continues after skipping any sections affected by the zero pointer.

User response:

The message is informatory, indicating that the area was zero at the time the dump was taken.

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

SYSPRINT

Modules:

Start of changeDFHDUFFT, DFHDUFUT, DFHXRDUFEnd of change

DFHPD0112I
Address of xxxxxxxx is zero.
Explanation:

The address of a block of type xxxxxxxx is zero.

System action:

Dump formatting continues after skipping any sections affected by the block.

User response:

The message is informatory, indicating that the area did not contain an address at the time the dump was taken.

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

SYSPRINT

Modules:

Start of changeDFHDUFFT, DFHDUFUT, DFHXRDUFEnd of change

DFHPD0113
This block has already been processed.
Explanation:

The block whose heading line has just been printed has already been formatted in this section of the dump.

System action:

The block is formatted again then any sections which may be impacted by the probable control block chain loop are skipped.

User response:

Check the chain fields in the control blocks processed so far. This may provide a clue to the problem.

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

SYSPRINT

Modules:

DFHPD640

DFHPD0114
Invalid keyword keyword
Explanation:

The keyword keyword is not valid for the CICS640 verb.

System action:

The keyword is ignored.

User response:

Correct the keyword and retry.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDKWEnd of change

DFHPD0115
CICS job not found during ASCB scan.
Explanation:

The dump formatting program searched the dump for CICS jobs satisfying the specified JOB criterion (if any), but found none.

System action:

There is only a severe problem when this message is followed by message DFHPD0120.

User response:

If this is a severe error, ensure that the dump is the correct one, that the JOB keyword is correctly specified, and that the dump contains the necessary MVS and CICS data areas.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDX1End of change

DFHPD0116
Cannot access the AFCB.
Explanation:

The formatting program was unable to access data for the AFCB.

System action:

No formatting is performed.

User response:

Ensure that the dump is the correct one, and that the dump contains the necessary MVS data areas.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDX1End of change

DFHPD0117
An error has occurred while formatting xxxxxxxx.
Explanation:

An error has occurred during the formatting of a block of type xxxxxxxx.

Either the user has performed a GETMAIN for the storage, but the storage has not been referenced. Unreferenced storage may not be present in the dump.

Or the block address is invalid,

Or the length of the control block is incorrect.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

If no data has been formatted for the block then either the storage has not been referenced, or the block address was invalid. If the block address was invalid, refer to message DFHPD0101.

If part of the block has been successfully formatted then it is possible that the length of the control block is incorrect. The length may have been overwritten which may provide a clue to the problem.

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

SYSPRINT

Modules:

Start of changeDFHDUFFT, DFHDUFUTEnd of change

DFHPD0118
Invalid argument for JOB=, CURRENT assumed
Explanation:

The argument for the JOB operand of the CICS640 verb is invalid.

System action:

The keyword is ignored.

User response:

Correct the invalid argument and retry.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDKWEnd of change

DFHPD0119
Duplicate keyword keyword found. Value value accepted
Explanation:

The CICS640 keyword keyword has already been encountered.

System action:

The value value specified in the message overrides any value previously specified for keyword keyword. Processing continues with the new value value.

User response:

Remove the duplicate keyword specified on the CICS640 verb.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDKWEnd of change

DFHPD0120
CICS IPCS exit is terminating.
Explanation:

The CICS exit is terminating.

System action:

The exit is returning to the Interactive Problem Control System (IPCS) without performing the requested function. A previous message gives the reason for this.

User response:

To determine what action is necessary, refer to the message immediately preceding this one on the dump.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDX1End of change

DFHPD0121I
Formatting control blocks for job jobname
Explanation:

This shows the job name for the CICS system from which the dump was taken.

System action:

Processing continues.

User response:

None.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDX1End of change

DFHPD0122I
End of dump for job jobname
Explanation:

This marks the end of the output from the CICS print dump exit.

System action:

None. The formatting job has just completed.

User response:

None.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDX1End of change

DFHPD0123
A program check has occurred while processing keyword keyword
Explanation:

A program check has occurred during processing of the keyword identified in the message.

System action:

Dump formatting continues after skipping any sections affected by the error.

Note that the maximum possible number of occurrences of this message is five. If a sixth program check occurs, the dump formatting program terminates abnormally with a DFHPD640 abend code.

User response:

A dump should accompany this message, but if no dump is produced, rerun the job with //DFHSNAP DD SYSOUT=A included in the JCL job stream.

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

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDX1End of change

DFHPD0124
Storage violation detected at X'address'. Leading SAA is invalid.
Explanation:

The Storage Accounting Area (SAA) in the first eight bytes of the user storage element at address X'address' has been found to be invalid. However, the trailing SAA is valid.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

Investigate why the storage has been overwritten or has not been set up correctly. For more information on how to solve storage overwrite problems, refer to the CICS Problem Determination Guide.

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

SYSPRINT

Modules:

Start of changeDFHDUFUTEnd of change

DFHPD0125
Storage violation detected at X'address'. Trailing SAA is invalid.
Explanation:

The Storage Accounting Area (SAA) in the first eight bytes of the user storage element at address X'address' has been found to be invalid. However, the leading SAA is valid.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

Investigate why the storage has been overwritten or has not been set up correctly. For more information on how to solve storage overwrite problems, refer to the CICS Problem Determination Guide.

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

SYSPRINT

Modules:

Start of changeDFHDUFUTEnd of change

DFHPD0126
Storage violation detected at X'address'. Leading and trailing SAAs are invalid.
Explanation:

The Storage Accounting Areas (SAAs) in the first and last eight bytes of the user storage element at address X'address' are invalid.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

Investigate why the storage has been overwritten or has not been set up correctly. For more information on how to solve storage overwrite problems, refer to the CICS Problem Determination Guide.

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

SYSPRINT

Modules:

Start of changeDFHDUFUTEnd of change

DFHPD0127
Storage violation detected at X'address'. Leading and trailing SAAs differ.
Explanation:

Although the Storage Accounting Areas (SAAs) in the first and last eight bytes of the user storage element at address X'address' are valid, they do not match.

System action:

Dump formatting continues after skipping any sections affected by the error.

User response:

Investigate why the storage has been overwritten or has not been set up correctly. For more information on how to solve storage overwrite problems, refer to the CICS Problem Determination Guide.

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

SYSPRINT

Modules:

Start of changeDFHDUFUTEnd of change

DFHPD0128
Invalid data length X'length' specified for address X'address'.
Explanation:

The offline utility DFHPD640 has detected a request for a block of data of invalid length X'length' while formatting a system dump.

System action:

Dump formatting usually continues after skipping any sections affected by this error.

User response:

This message indicates a probable error in CICS code. 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:

SYSPRINT

Modules:

Start of changeDFHDUFUT, DFHDUFFTEnd of change

DFHPD0129
CICS Domain Anchor Blocks not found for AFCB. Scan will continue.
Explanation:

The dump formatter has attempted to find a CICS dump in a TCB chain but has failed. The scan will continue. This is because DFHPD640 could not find the addresses of the CICS domain anchor blocks in the kernel global storage. Possible causes for this are:

System action:

There is only a severe problem when this message is followed by message DFHPD0120.

User response:

If this is a severe error. Try to recreate the original error and produce a valid system dump against which the dump formatter can be rerun.

If the problem recurs, you will need further assistance from IBM. Collect the sysprint output from the dump formatter and note any relevant messages. See CICS Problem Determination Guide for guidance on how to proceed.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDX1End of change

DFHPD0130
Keyword keyword1 is no longer valid. Replace with keyword keyword2
Explanation:

In CICS Transaction Server for z/OS®, Version 3 Release 1 the keyword keyword1 has been replaced by keyword2 for the CICS640 verb.

For example, the keyword PCP has been replaced by PG.

System action:

The keyword keyword1 is ignored.

User response:

Correct the keyword and retry.

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

SYSPRINT

End of change
Modules:

Start of changeDFHPDKWEnd of change

DFHPD0131
CICS job jobname is for CICS version version1. CICS IPCS exit is for CICS version version2.
Explanation:

The CICS job jobname being processed by the dump formatting program was executing under CICS version version1, but the dump formatting program was the one distributed with CICS version version2.

System action:

Start of changeDump formatting continues for the CICS job.End of change

Start of change
User response:

Unless formatting MRO control blocks, retry dump formatting for the CICS job using the dump formatting program for CICS version version1.

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 changeDFHPDX1End of change

Start of changeDFHPD0133End of change
Start of changeSpecified task not found.End of change
Start of change
Explanation:

No transaction could be found for the task identifier specified in the taskid keyword parameter.

End of change
Start of change
System action:

Dump formatting continues after skipping any sections affected by the error.

End of change
Start of change
User response:

Correct the invalid taskid and retry.

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 changeDFHPD640End of change

Start of changeDFHPD0134End of change
Start of changeLink to module CEEERRIP has failed.End of change
Start of change
Explanation:

While formatting dump data an attempt was made to link to the Language Environment IPCS Verbexit program CEEERRIP. The link failed.

End of change
Start of change
System action:

Dump formatting continues after skipping any sections affected by the error.

End of change
Start of change
User response:

CEEERRIP is supplied on SYS1.MIGLIB. Ensure that SYS1.MIGLIB is in the concatenation for the MVS linklist or LPA.

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 changeDFHPD640End of change

Start of changeDFHPD0135End of change
Start of changeProgram check occurred with CEEERRIP in control.End of change
Start of change
Explanation:

While formatting dump data a program check occurred in the Language Environment IPCS verbexit module CEEERRIP.

End of change
Start of change
System action:

Dump formatting continues after skipping any sections affected by the error.

End of change
Start of change
User response:

A dump should accompany this message. 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.
End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHPD640End of change

[[ Contents Previous Page | Next Page Index ]]