IBM Mainframe Forum

Hi all,

In ims V7R1,recentely we have encountered abend 0C4 and after that,ims terminates completely.a part of log at the time
of abend is:
*********************************************************************************************************************
DFS616I OLDS BUFFERS SUCCESSFULLY PURGED BSI7
DFS629I IMS DBT TCB ABEND - SYS 0C4 BSI7
DFS629I PSW AT ERROR = 077C1000 8008B57C BSI7
DFS629I MODID = UNKNOWN EPA = UNKNOWN BSI7
DFS629I R0-3 0F27E678 00000001 0BC008E8 0BC008DC BSI7
DFS629I R4-7 8003FD14 0F224A9C 0A9EDC7B 00000000 BSI7
DFS629I R8-11 0BC00780 0F2248DC 0F27E678 0BE5C060 BSI7
DFS629I R12-15 0008B4CA 0BE5C780 8008A4E2 0008B4CA BSI7
DFS3905W IMS DUMP REQUEST ERROR - P SDUMP PROCESSING ERROR, RC=4-N/A
BSI7
DFS3932I IMS DUMP REQUEST COMPLETED - RETURN CODE = 048 BSI7
IEA043I SVC DUMP REACHED MAXSPACE LIMIT - MAXSPACE=00000500 MEG
DFS0613I DBC RGN U113 DUE TO S0C4 U0000 DURING DL/I CALL IN CCTL CICSBSI
BSI7
IEA794I SVC DUMP HAS CAPTURED: 704
DUMPID=164 REQUESTED BY JOB (CICSBSI )
DUMP TITLE=CICSBSI ABEND SYS 0C4 USER 0000-004, DATE.TIME: 010
.151144, CALLER=DP , TCB=DBT, MODULE=UNKNOWN ,P
*********************************************************************************************************************
The abend occures 1 or 2 times a day!

Could you please help me why the error create or how i can prevent it?

Best regards,
Mehrdad.

I do not know your environment so this is my best guess. Your SYS1.DUMP is missing causing the 0C4. Looking at the dump provided it was the Primary SDUMP from the DFSFDMP0 Dump Assist Module. IMS needs all the 'stuff' in place for it to run.

Contact your Database Administrator. If the DBA does not know how to fix it, I am looking for work. Anyway Here is more info:
DFS3905W


IMS DUMP REQUEST ERROR - t SDUMP PROCESSING ERROR, RC=r-ccc

Explanation


The IMS™ dump assist module (DFSFDMP0) received a nonzero return code from SDUMP while processing an IMS SDUMP request. The meanings of the variables are: t P or S, indicating whether the request was a primary or secondary SDUMP request r SDUMP return code 04=partial memory dump created
08=no dump created
ccc The reason code taken from SDUMP (the value is UNK, if no reason code was available). SDUMP reason codes are explained in z/OS MVS Programming Authorized Assembler Services Reference Vol 3 (SA22-7611). For a partial memory dump (return code=04), the value of ccc is N/A. In this case, obtain the reason code from z/OS message IEA911E or IEA611E.
System action


If this is the primary SDUMP request (t=P), IMS retries with a secondary SDUMP for the following conditions: •A partial memory dump was created (return code 4) which was not due to a QUIESCE=YES request that could not be honored.
•No memory dump was created (return code 8), but the reason code is one of the following: 001, 255, 005 through 009. A retry is not attempted if the internal parameter list passed by the caller of the dump assist routine specifies no secondary memory dump.

If the secondary SDUMP fails, this message is issued with (t=S) when the SDUMP return code is 4; or when the reason code does not indicate that the SVC memory dump was suppressed either because of another SVC dump in progress or because a SYS1.DUMP data set was unavailable.

When both SDUMP requests fail, IMS online memory dump formatting is permitted if the FMTO parameter you specified allows it.
http://pic.dhe.ibm.com/infocenter/dzich ... 3905w.html