I have an EGL-generated program in which a dump (sometimes) occurs in ELAASTRM (U1608 in ELARPRTR).

This is what abend-aid says:

Entry Number....... 1207561
Code............... U1608  
Job Name........... CRDG8U00
                           
Program............ ELARPRTR
Offset............. 0000004E
LE Condition ID.... CEE3250C

When I debug via xpediter I get the following abend info:

*******************************************                            
*             Error Location              *                            
*******************************************                            
                                                                       
The next sequential instruction to be executed in program ELARPRTR was 
at displacement 00000050.                                              
                                                                       
        00000044  0BE0          BSM     R14,R0                         
        00000046  50E0F070      ST      R14,112(,R15)                  
        0000004A  58F0F06C      L       R15,108(,R15)                  
        0000004E  0CEF          BASSM   R14,R15                        
 NSI==> 00000050  58E10000      L       R14,0(R1,R0)                   
        00000054  58EE0070      L       R14,112(R14,R0)                
        00000058  0B0E          BSM     R0,R14                         
        0000005A  C5D3C1D9D7D9  BPRP    13,*+X'0782,*-X'4C504E' EH     
        00000060  E3D9          DATA    X'E3D9'                        

I'm lost here. What could be the problem?

Hey,

This is the EGL COBOL runtime module that is called during termination of the EGL rununit.

So, a couple of questions:

a.) Did this program used to run?

b.) What release of RBD are you using to generate the COBOL?

c.) Did something change recently (fixpacks, host runtime PTF, etc)?

d.) Did you recently regenerate the program?

e.) Is the problem repeatable?

Mark

Thanks for the swift reaction!

a) It is running in a production environment for some years now.

Only now and then it gives this abend.

b) Version is 8.0.1.1

c) Last time it has changed in production is 2012.

d) It is recently under development in test

e) I can repeat the problem in test

Has the EGL runtime been updated recently or has it been the same for a long time?

That abend is caused intentionally when the EGL runtime detects that a memory overlay has occurred. EGL manages some memory allocations at runtime and has a storage accounting area similar to CICS. I believe you are running batch, but EGL still does this check. This memory overlay could be from anywhere, so it could be an error in EGL's runtime, EGL's generated code or a user error that causes a memory overlay.

Can you please open a PMR provide me with the dump?

Thank you.