DFHSRxxxx messages

DFHSR0001
applid An abend (code aaa/bbbb) has occurred at offset X'offset' in program progname.
Explanation:

An abnormal end (abend) or program check has occurred in program progname. Storage protection is active, and CICS was executing in USER key at the time of the abend or program check.

The code aaa is a three digit hexadecimal MVS system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The four digit code bbbb, which follows aaa, is a user abend code, produced either by CICS or by another product on the user’s system. Message DFHME0116 is normally produced containing the symptom string for this problem.

System action:

An exception trace entry is made giving details of the error. System dump SR0001 is taken unless you have specifically suppressed dumps for that dumpcode in the dump table.

CICS continues and abends the transaction, unless you have specified in the dump table that CICS should terminate. The transaction abend code is ASRA, ASRB, ASRD or ASRE.

User response:

As the execution key was USER key, modname is probably a customer application program. Review this program and correct the error.

Note that if the error was an 0C4 program check caused by an attempt to overwrite a CICS DSA, the exception trace entry indicates which DSA the program attempted to overwrite. If this is the case, also refer to the explanation for message DFHSR0622.

For advice on problem determination, refer to the CICS® Problem Determination Guide.

Report the details of the symptom string given in message DFHME0116.

If you want to suppress system dumps that precede ASRA, ASRB, ASRD or ASRE abends when the execution key is USER, you must specify this on an entry in the dump table for system dumpcode SR0001. Use either CEMT or an EXEC CICS command. Further guidance on this can be found in the CICS System Definition Guide.

Destination:

Console

Modules:

DFHSRP

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

DFHSR0601
applid Program interrupt occurred with system task taskid in control
Explanation:

A program check has been detected in a system task. taskid is the system task identifier (for example, TCP, III) as set in field TCAKCTTA.

System action:

CICS abnormally terminates with system dump SR0601 and an exception trace entry which gives the kernel error data for the program check.

User response:

Use the dump to determine the cause of the program check. The most likely causes are either an error in a CICS module, or an error in a user-written PLT program.

For advice on problem determination, refer to the CICS Problem Determination Guide.

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameters: applid, taskid

DFHSR0602
applid Program interrupt routine has been entered while processing program interrupt for same task
Explanation:

A program check occurred. CICS started to abend the task with an abend code of ASRA when another program check occurred. As this is a potentially recursive situation, DFHSRP terminates CICS.

System action:

CICS abnormally terminates with system dump SR0602 and exception trace entries giving the kernel error data for each program check.

User response:

Try to discover where and why the first program check occurred. The most likely cause is an error in the application program. The second program check may be due to a CICS error while terminating the task.

For advice on problem determination, refer to the CICS Problem Determination Guide.

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameter: applid

DFHSR0603
applid Program interrupt has occurred
Explanation:

A program check occurred, and CICS did not attempt to recover, because SRT=NO was specified in the system initialization table or by the operator at start-up time.

System action:

CICS abnormally terminates with system dump SR0603 and an exception trace entry giving the kernel error data for the program check.

User response:

Initially, check that the specification of SRT=NO is correct. If it is incorrect, change it as described in the CICS System Definition Guide.

For advice on problem determination, refer to the CICS Problem Determination Guide.

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameter: applid

DFHSR0605
applid Error from KE Domain - DFHSRP initialization
Explanation:

Module DFHSRP has detected a severe error during the initialization phase of CICS. It is unlikely that any recovery functions can run until the error is found and corrected.

System action:

CICS abnormally terminates with system dump SR0605.

User response:

Use the dump to determine, if possible, the cause of the problem and what must be done to correct it.

For advice on problem determination, refer to the CICS Problem Determination Guide

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameter: applid

DFHSR0606
applid Abend (code aaa/bbbb) has been detected.
Explanation:

DFHSRP has detected an abnormal termination which CICS is not able to handle fully (for example, the abend code cannot be found in the SRT). In this instance it is the CICS system and not merely a transaction, that has abnormally terminated.

The code aaa is a three digit hexadecimal MVS system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The four digit code bbbb, which follows aaa, is a user abend code produced either by CICS or by another product on the user’s system.

System action:

CICS abnormally terminates. A system dump (dumpcode SR0606) can be taken with this message depending on the abend code. An exception trace entry is produced giving the kernel error data for the abend.

User response:

Use the dump to determine the abnormal termination, and to investigate its cause.

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameters: applid, aaa/bbbb

DFHSR0612
applid Abend recovery has been entered by same task
Explanation:

An operating system abnormal termination occurred. CICS started to abend the task with abend code ASRB when another operating system abnormal termination occurred. As this is a potentially recursive situation, DFHSRP terminates CICS.

System action:

CICS abnormally terminates with system dump SR0612 and exception trace entries giving the kernel error data for each operating system abend.

User response:

The most likely cause of the second operating system abend is an error in a global user exit program running at the XSRAB exit. This is the global user exit that can be invoked when an abend code is found in the SRT. If such a program was running, determine the cause of the second abend and take steps to prevent a recurrence.

Note that this message will also be issued if a global user exit program running at the XSRAB exit gets into a loop (runaway), or issues an unknown XPI call (kernerror). The second exception trace entry should help to diagnose this.

For advice on problem determination, see the CICS Problem Determination Guide.

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameter: applid

DFHSR0613
applid Abend has occurred with system task taskid in control
Explanation:

An operating system abnormal termination has been detected in a system task. taskid is the system task identifier (for example, TCP, III) as set in field TCAKCTTA.

System action:

CICS abnormally terminates with system dump SR0613 and an exception trace entry giving the kernel error data for the operating system abend.

User response:

Use the dump to determine the cause of the abend, and take action to correct it.

For advice on problem determination, see the CICS Problem Determination Guide.

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameters: applid, taskid

DFHSR0615
applid Program interrupt has occurred in recovery task
Explanation:

An operating system abnormal termination occurred. CICS started to abend the task with an abend code of ASRB when a program check occurred. DFHSRP terminates CICS.

System action:

CICS abnormally terminates with system dump SR0615 and exception trace entries giving the kernel error data for the operating system abend and the program check.

User response:

The most likely cause of the program check is an error in a global user exit program running at the XSRAB exit. This is the global user exit that can be invoked when an abend code is found in the SRT. If such a program was running, determine the cause of the program check and correct it.

For advice on problem determination, refer to the CICS Problem Determination Guide.

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameter: applid

DFHSR0618
applid An illegal macro call or reference to the CSA or TCA has caused the abend which follows
Explanation:

A user program was executing which either contains an assembler macro which is no longer supported, or refers illegally to the CICS TCA or CSA. This error appears as an 0C4 program check.

System action:

Either The transaction abends with abend code ASRD. This message is followed by message DFHAP0001 or DFHSR0001 which gives the name of the program in error and the offset into that program at which the error occurred.

Or This is a critical error and CICS is terminated. This message is followed by a DFHSR06xx message giving the reason for the termination.

User response:

Review the program and correct the error.

If the error is in the module DFHUEHC, ensure that UEPCSA and UEPTCA are not being used because these reference fetch-protected storage.

For advice on problem determination, refer to the CICS Problem Determination Guide.

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameter: applid

Start of changeDFHSR0619End of change
Start of changedate time applid An illegal reference to the RCT has caused the abend which follows.End of change
Start of change
Explanation:

A user program was executing and referred illegally to the RCT. This error appears as an 0C4 program check.

End of change
Start of change
System action:

The transaction abends with abend code ASRE. This message is followed by message DFHAP0001 or DFHSR0001 which gives the name of the program in error and the offset into that program at which the error occurred.

End of change
Start of change
User response:

Review the program and correct the error by using the CICS supplied SPI commands to retrieve data from the RCT.

For advice on problem determination, refer to the CICS Problem Determination Guide.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2

End of change
Modules:

Start of changeDFHSRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

DFHSR0622
applid An attempt to {overwrite |access} the dsaname has caused the abend which follows
Explanation:

An 0C4 program interrupt (protection exception) has occurred. CICS has diagnosed the cause of the 0C4 as an attempt to either access or overwrite storage in DSA dsaname. The DSA is one of CDSA, RDSA, UDSA, ECDSA, ERDSA or EUDSA for overwrite, or either UDSA or EUDSA for access.

If dsaname is CDSA or ECDSA:
CICS is running with storage protection active. Both the CDSA and the ECDSA therefore contain CICS key storage. They are write protected from user programs executing in User key. The most likely causes of the 0C4 are:
  • A program executing in CICS key passed the address of CICS key storage in the CDSA or ECDSA to a user program executing in User key and this user program attempted to write to this storage.
  • A user program executing in User key contains an error and accidentally attempted to write to CICS key storage in the CDSA or ECDSA.
  • A user program executing in User key deliberately attempted to write to CICS key storage in the CDSA or ECDSA.
If dsaname is ERDSA or RDSA:
CICS may be running with or without storage protection active. The ERDSA or RDSA contains only reentrant CICS and user programs. If RENTPGM=PROTECT was specified as a system initialization parameter, the ERDSA or RDSA is write protected from programs executing in both CICS key and User key. If RENTPGM=NOPROTECT, the ERDSA or RDSA is only protected from user programs executing in User key. The most likely causes of the 0C4 are:
  • A user program residing in the ERDSA or RDSA has attempted to modify its own storage, (that is, the program is not reentrant).
  • A user program contains an error and accidentally attempted to overwrite program storage in the ERDSA or RDSA.
If dsaname is EUDSA or UDSA:
CICS is running with both storage protection and transaction isolation active. The EUDSA and UDSA contain only USER key non-shared storage. The most likely causes of the 0C4 are:
  • If the action is overwrite, a program has attempted to modify the non-shared storage belonging to another transaction.
  • If the action is access, a program has attempted to either read storage or execute an instruction within another transaction's non-shared storage.
System action:

Either, the transaction abends with abend code ASRA. This message is followed by message DFHAP0001 or DFHSR0001 which gives the name of the program in error and the offset into that program at which the error occurred. Additionally, an exception trace entry is taken which gives program, offset, execution key and the DSA in question.

Or, this is a critical error and CICS is terminated. This message is followed by a DFHSR06xx message giving the reason for the termination.

User response:

Depending on the cause and dsaname, do one of the following:

Destination:

Console

Modules:

DFHSRP

XMEOUT Parameters: applid, {1=overwrite, 2=access}, dsaname

[[ Contents Previous Page | Next Page Index ]]