IMS 0C4 DURING DL/I CALL IN CCTL

[mehi1353]

Hi all,
Could anyone please help me to find the cause of this problem:

DFS0613I DBC RGN U113 DUE TO S0C4 U0000 DURING DL/I CALL IN CCTL
CICSPSA2 IMSA
DUMPID=162 REQUESTED BY JOB (CICSPSA2)
DUMP TITLE=CICSPSA2 ABEND SYS 0C4 USER 0000-004, DATE.TIME: 064
.103949, CALLER=DP , TCB=DBT, MODULE=UNKNOWN ,P
DFS629I IMS CTL TCB ABEND - IMS 0113 IMSA


after the abend ,IMS terminates completely!

we use IMS V7R1.

[dick scherrer]

Hello,

To get help you will probably need to provide much more info. . .

How often does this happen? Did this ever work correctly? If yes, what was changed?

Do other similar processes work correctly? If yes, see what is different between the ones that work and this one.

Do you know at what place in the code the problem happened? If not, you may want to add some diagnostic code to help identify where in the code the problem occurs.

[BillyBoyo]

How did you get on with this? You have two "DFS" messages to look up, google can find them in a flash.

Something has abended (helpful, aren't I ). Module "unknown" and an S0C4. Look at the dump(s) produced. My wild guess would be something has overwritten some program code. With the dump, you can do better than my wild guess. From the PSW see what was supposed to be being executed. Find the module it was within (if it is all Cobol (and not crashed in an IMS routine), just look backwards from the failing address until you find a Cobol program). If at the failing address it is all space (or low-values, or high-values, or a repeating pattern, or something that is obviously data not program code, which is what there should be where you are looking) then my wild guess came in. If not, you have the dump and the program listings. We'd need more information for more advice.

In this sort of error, the whole of IMS goes down and has to get restarted. Work on the dump, it is a bit of a pain bringing down an IMS region just to see some displays.

[DFSHDC40]

IMS hasnt abended S0C4 - CICS has
The application had issued a DL/I call that hadnt completed
IMS recognises a dependednt region (CICS) has gone while in DL/I so abends U0113 to force BO on ERE
Why did CICS abend?

[sys2462019]

We have an IMS DBCTL connecting to 4 CICS regions. Every time recycling CICS regions would crash the IMS control region with U0113.
Then the automation would re-start the IMS back up. So we could live with that.
Please advise, as an IMS Systems Programmer, what should be done with this situation? or just leave it alone? Thanks!

DFS4445I CMD FROM MCS/E-MCS CONSOLE USERID=AUTAO1SB: DIS CCTL
DFS000I MESSAGE(S) FROM ID=IMSC 675
CCTL STATUS
CIGNDEVT ATTACHED
CIGNCLOM ATTACHED
LTCCLOT1 ATTACHED
CIGNCLOT ATTACHED
*2019042/145945*
DFS3896I ATTEMPTING TO PURGE OLDS BUFFERS IMSC
DFS616I OLDS BUFFERS SUCCESSFULLY PURGED IMSC
DFS629I IMS CTL TCB ABEND - IMS 0113 IMSC
IEA794I SVC DUMP HAS CAPTURED: 924
DUMPID=071 REQUESTED BY JOB (IMSTEST )
DFS3932I IMS DUMP REQUEST COMPLETED - RETURN CODE = 000 IMSC
DUMP TITLE=IMSTEST ABEND SYS 000 USER 0113 , DATE.TIME: 0
.151017, CALLER=CTL , TCB=CTL, MODULE=UNKNOWN ,P
DFS629I IMS CTX TCB ABEND - IMS 4095 IMSC
DFS629I IMS STC TCB ABEND - IMS 4095 IMSC
DFS629I IMS DLG TCB ABEND - IMS 4095 IMSC
DFS629I IMS RDS TCB ABEND - IMS 4095 IMSC

[NicC]

Do not tailgate othber ele's topics. Start your own. Topic locked.