On Wed, 29 Oct 2025 at 16:26, Joseph Reichman <
[email protected]> wrote:
> I allocated all there sysudump sysmdump and sysabend file was empty even
> put in a Estae
>
> Made a breakpoint at the recovery exit never hit
>
> Now doing a where points to the first instruction in IEWBIND wonder if that
> is a stm 14,12,12(13)
>
OK... Lots of layers here. Try to simplify. How do you plan to invoke the
program when it's all working? EXEC PGM= or CALL on TSO? If CALL works
(i.e. fails the same as under TEST), then make sure your SYSxDUMP is
allocated, then issue the CALL, wait for the
IKJ56641I <yourprog> ENDED DUE TO ERROR
IKJ56640I SYSTEM ABEND CODE 0C4 REASON CODE 00000004
and then hit Enter. I tried this to be sure. I called my program IEFS0C4,
and it contains just a store of R5 into location 0. I got:
call 'tony.test.load(iefs0c4)'
IKJ56641I IEFS0C4 ENDED DUE TO ERROR+
READY
<I hit ENTER here with no intervening commands>
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=0C4 REASON CODE=00000004
TIME=17.05.14 SEQ=00119 CPU=0000 ASID=004D
PSW AT TIME OF ERROR 078D0000 0002CFFC ILC 4 INTC 04
ACTIVE MODULE ADDRESS=00000000_0002CFF8 OFFSET=00000004
NAME=IEFS0C4
DATA AT PSW 0002CFF6 - 00005050 00000000 00000000
GR 0: 00000004 1: 0000BC60
2: 0000BD6C 3: 0000B6D8
4: 8591602C 5: 008CC940
6: 0000B8E0 7: 0000B698
8: 008CC940 9: 00FD6680
A: 85924030 B: 0592502F
C: 0000E4A8 D: 0000FF68
E: 80FD66D0 F: 0002CFF8
END OF SYMPTOM DUMP
READY
I had SYSUDUMP allocated to SYSOUT, and it has the dump of the S0C4 in it.
Of course this would work just as well in batch. Search for the string
"*RCVY PROG" and then back up a few lines and you should see your program
check 004 in the trace table.
Tony H.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
