It looks like you had a S0C4 during termination most likely from a storage 
overlay. My observations from the very limited information provided:

On Mon, 16 Jun 2025 17:09:08 -0500, Charles Mills <[email protected]> wrote:

>16.52.50 JOB04842  +IDI0012S Abend 0000C9 occurred in abend exit processing, 

The diagnostic messages may not be completely reliable. Keep in mind that an 
abend in abend recovery means that messages might be for the second (or 
subsequent) abend instead of the initial abend.

Also realize the S0C9 is not for your abend. It's for an abend in abend 
recovery or secondary abend recovery.

>16.52.50 JOB04842  +CEE0374C CONDITION=CEE3204S TOKEN=00030C84 59C3C5C5 
>00000000  816 

We don't see message CEE3204S in the messages provided. I assume the messages 
you provided are from the joblog (syslog might contain additional messages). 
It's possible it's a documentational msgid that never produces an actual 
message.

Message id CEE3204S identifies a S0C4 abend. It's possible the even this S0C4 
is from a secondary abend. In that case, the initial abend can only be 
determined from the system trace.

>   816                       WHILE RUNNING PROGRAM CERTREPT  

Find out the component associated to mod or lmod CERTREPT. GEMINI thinks it 
associated to encryption.  

>   816                       PSW     078D0400 9A804D70                         
>                                         
>   816                       GPR 0-3 00000000 00000000 00000000 00000008       
>                                         
>   816                       GPR 4-7 00791860 1B41BB28 1A804D70 9A81EAA6       
>                                         
>   816                       GPR 8-B 9A81EA6C 1B424800 1B417D70 86087018       
>                                         
>   816                       GPR C-F 1A9181D8 1B17C840 00000002 00000002    
                                           

PSW addr & R6 are the same and the other regs are too far to be used as a base 
reg. I suspect these registers are from a secondary abend in abend recovery. If 
from the initial abend, then they are most likely corrupted.  

>Storage is apparently being exhausted, despite REGION=0M. 
>        VIRT:  7872K  SYS:   768K  EXT:  1649760K  SYS:    12420K    

Unlikely storage is exhausted. You don't see any indication of an S787 abend. 
Below the bar "VIRT:" storage and above the bar "EXT:" storage looks 
reasonable. While 2TB above the bar (EXT:) is large, it's not outrageous.

System exits can override REGION=0M but you don't see an S787 abend.

>In the SYSUDUMP 
>I see allocation after allocation -- 13,000 lines or so -- of x'21000' bytes 
>in subpool 2.

You're chasing a wild goose here. 13,000 lines times x'21000' is 1.6GB more 
than below the bar storage used (VIRT: 7872K). This storage must be above the 
bar.

>and I am seeing that printf() message,

If everything you say is true, then a storage overlay is most likely because 
you are in standard terminations. If CERTREPT is encryption, then you've 
overlayed something that is being committed or rollback. Maybe database, vsam, 
files or ???. 

>16.52.49 JOB04842  IKJ56245I DATA SET xxxxxx.D167.T1652476.xxxxxxCR NOT 
>ALLOCATED, NOT ENOUGH SPACE ON VOLUMES+  
>CHNGDUMP SET,SDUMP,MAX SPACE=12000M

12000M (12GB) is less than 1% of the space needed for the 1.7TB above the bar 
storage. Maybe IBM can give you some advice on creating a dump otherwise you 
may be forced into a standalone dump. 

Maybe changing the dump options can reduce the dump to a manageable size. Check 
with IBM on how they handle these situations. Maybe exclude above the bar 
storage.

As a last resort method, you could set a slip trap with ACTION=WAIT and use 
IPCS to look at active storage of foreign address spaces but this will require 
some setup.

>   821             DUMP TITLE=IDIDA ESTAE exit entered.              JOB04842 
> SDWA                                     
>   821                        =7F510B58                                        
>                                         

You did get a dump that should contain the system trace. Maybe you can find the 
S0C4 abend and see what was happening at that time. Possibly search backwards 
for another abend to see if the S0C4 was a secondary abend or the initial 
abend. 

Good luck.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to