URGENT - CICS Region abnormal termination
Posted: Wed Feb 16, 2011 2:28 pm
Hi,
In my environment there are around 22 CICS regions are running with TS2,.3 and 4 regions (name as CICSE*) running with CICS TS2.2. Recently, as part of LPAR consolidation, we have moved the CICSE* regions to another LPAR.
Later we found that the region is not poining to correct DB2 system. So we have modified the RCT and made it point to correct DB2 system and we have done the COLD start for the regions.
Since then, regions are comming down abnormally with the below messages.
STC16350 ---- TUESDAY, 15 FEB 2011 ----
STC16350 +DFHIC0801 ECEHCICS CICS time altered from 24.00.000 to
00.00.006 - d
STC16350 +DFHSR0606 ECEHCICS Abend (code 01D/AKEB) has been detected.
STC16350 +DFHME0116 ECEHCICS 117
(Module:DFHMEME) CICS symptom string for message DFHSR0606 is
PIDS/5697E9300 LVLS/620 MS/DFHSR0606 RIDS/DFHSRP PTFS/UK05569
AB/S001D AB/UAKEB
STC16350 +DFHDU0201 ECEHCICS ABOUT TO TAKE SDUMP. DUMPCODE: SR0606 ,
DUMPID:
STC16350 IEA794I SVC DUMP HAS CAPTURED: 119
DUMPID=015 REQUESTED BY JOB (CICSEH )
DUMP TITLE=CICS DUMP: SYSTEM=ECEHCICS CODE=SR0606 ID=5/0001
STC16350 +DFHDU0202 ECEHCICS SDUMPX COMPLETE. SDUMPX RETURN CODE X'00'
STC16350 BPXP018I THREAD 24A5322000000001, IN PROCESS 50331813, ENDED
127
WITHOUT BEING UNDUBBED WITH COMPLETION CODE 0033E000, AND REASON CODE
00000000.
STC16350 +ACFAE071 LONG WAIT SUBTASK ABENDED; LONG WAIT SUBTASK DISABLED
STC16350 +ACFAE070 SHORT WAIT SUBTASK ABENDED; SHORT WAIT SUBTASK
DISABLED
STC16350 +DFHDU0303I ECEHCICS Transaction Dump Data set DFHDMPA closed.
STC16350 +DFHKE1800 ECEHCICS ABNORMAL TERMINATION OF CICS IS COMPLETE.
STC16350 IEF450I CICSEH CICS STARTING - ABEND=S000 U1800 REASON=00000000
148
TIME=04.08.18
STC16350 IEF404I CICSEH - ENDED - TIME=04.08.39
This region abnormal termination is happening when any user logged into the system and execute any application transaction. CICS suplied transactions are working fine. We cound not find the issue and we are doing the restart on the system every time.
Could you please let us know what can be done to fix this issue?
Thanks,
Sridhar A
In my environment there are around 22 CICS regions are running with TS2,.3 and 4 regions (name as CICSE*) running with CICS TS2.2. Recently, as part of LPAR consolidation, we have moved the CICSE* regions to another LPAR.
Later we found that the region is not poining to correct DB2 system. So we have modified the RCT and made it point to correct DB2 system and we have done the COLD start for the regions.
Since then, regions are comming down abnormally with the below messages.
STC16350 ---- TUESDAY, 15 FEB 2011 ----
STC16350 +DFHIC0801 ECEHCICS CICS time altered from 24.00.000 to
00.00.006 - d
STC16350 +DFHSR0606 ECEHCICS Abend (code 01D/AKEB) has been detected.
STC16350 +DFHME0116 ECEHCICS 117
(Module:DFHMEME) CICS symptom string for message DFHSR0606 is
PIDS/5697E9300 LVLS/620 MS/DFHSR0606 RIDS/DFHSRP PTFS/UK05569
AB/S001D AB/UAKEB
STC16350 +DFHDU0201 ECEHCICS ABOUT TO TAKE SDUMP. DUMPCODE: SR0606 ,
DUMPID:
STC16350 IEA794I SVC DUMP HAS CAPTURED: 119
DUMPID=015 REQUESTED BY JOB (CICSEH )
DUMP TITLE=CICS DUMP: SYSTEM=ECEHCICS CODE=SR0606 ID=5/0001
STC16350 +DFHDU0202 ECEHCICS SDUMPX COMPLETE. SDUMPX RETURN CODE X'00'
STC16350 BPXP018I THREAD 24A5322000000001, IN PROCESS 50331813, ENDED
127
WITHOUT BEING UNDUBBED WITH COMPLETION CODE 0033E000, AND REASON CODE
00000000.
STC16350 +ACFAE071 LONG WAIT SUBTASK ABENDED; LONG WAIT SUBTASK DISABLED
STC16350 +ACFAE070 SHORT WAIT SUBTASK ABENDED; SHORT WAIT SUBTASK
DISABLED
STC16350 +DFHDU0303I ECEHCICS Transaction Dump Data set DFHDMPA closed.
STC16350 +DFHKE1800 ECEHCICS ABNORMAL TERMINATION OF CICS IS COMPLETE.
STC16350 IEF450I CICSEH CICS STARTING - ABEND=S000 U1800 REASON=00000000
148
TIME=04.08.18
STC16350 IEF404I CICSEH - ENDED - TIME=04.08.39
This region abnormal termination is happening when any user logged into the system and execute any application transaction. CICS suplied transactions are working fine. We cound not find the issue and we are doing the restart on the system every time.
Could you please let us know what can be done to fix this issue?
Thanks,
Sridhar A