Question & Answer
Question
Why did my CICS Transaction Server for z/OS (CICS TS) region terminate with messages DFHDS0002 code X'0056' in DFHDSKE and BPXP018I code 0033E000 after the KILL and FORCEPURGE commands were entered to purge a task?
A CEMT SET TASK(value) KILL command was entered against a task:
DFHCQ0259I CEKL SET: KILL request issued for task number 12345
The tasks did not go away so a CEMT SET TASK(value) FORCEPURGE command was then entered against the same task:
DFHCQ0256I CEKL SET: FORCEPURGE request issued for task number 12345
This was followed by a sever error in CICS:
DFHDS0002 A severe error (code X'0056') has occurred in module DFHDSKE
Then the region shut down without any further messages from CICS. Only a series of the following messages were issued:
BPXP018I THREAD xxx IN PROCESS yyy ENDED WITHOUT BEING UNDUBBED WITH COMPLETION CODE 0033E000
IEF450I ABEND=S000 U1800 REASON=00000000
Answer
Dispatcher trace entry DS 0056 lends its number to the error code of message DFHDS0002.
DS 0056 DSKE *EXC - DSKE_TASK_SUSP_TOK_IN_USE
DSKE_TASK_SUSP_TOK_IN_USE is the reason the region came done. Module DFHDSKE issues that exception trace entry when it detects an inconsistent state that it can't recover from.
The following behavior is documented under the CEMT SET TASK command in CICS documentation for KILL and FORCEPURGE:
FORCEPURGE
Terminate the task as soon as it is consistent with system integrity, and without regard to data integrity. CICS® cannot always determine whether a forced purge is safe; it is possible to abend the system when you specify this option. For example, if a task is forcepurged during backout processing, CICS terminates abnormally. If you want to terminate a task, but do not want to terminate CICS, use the PURGE option instead.
KILL
Terminate the task. System and data integrity is not guaranteed. The KILL option extends the PURGE and FORCEPURGE options. Use this option only after first attempting a purge or forced purge. The KILL option does not guarantee integrity of any kind, but in some situations you can use it to free up a stalled region, thus enabling the region to continue processing. In some cases, for example, if a task is killed during backout processing, CICS terminates abnormally.
One of the main objectives of CICS is to maintain data integrity. Since CICS can not maintain integrity in these circumstances, the act of entering a KILL or FORCEPURGE command against a task that is already in backout processing is just another way to telling the CICS region to shutdown without further processing.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
06 December 2016
UID
dwa1325381