Thanks :-)

Looks like your LE has about 10 levels of "depth". The handler is getting 
invoked, and then itself abending/raising a condition, so it gets invoked 
again, and does the same thing - until LE runs out of patience that was defined 
for it.

The IGZMSG is the module which informs of a run-time problem. You earlier 
mentioned a COBOL message about recursion? IGZMSG would cause the message to be 
output, and I was wondering if it was a 15S or a 64S IGZ message.

Basically, the handler has been entered twice. The first time presumably the 
intended one - and then again. Then it hits the "invalid recursion" problem, 
and just keeps triggering the handler.

I can't see that the initial use of the handler could trigger the "recursive" 
problem, because it should be an entirely separate executable from the "main" 
program. 

With RECURSIVE on the PROGRAM-ID, the handler will be entered twice still (I'm 
assuming) but since there is no code to deal with the second condition, it will 
be ignored by the handler. 

To confirm that the ENTRY is not actually being used recursively, that it is in 
a separate executable (only worth checking because if it isn't, this problem 
would be caused) I'd REDEFINES the PROCEDURE-POINTER as PIC X(9) and DISPLAY it 
after the SET. Before that SET I'd put another SET ... ENTRY ... to the "main" 
program-name, and again DISPLAY that.  The two addresses DISPLAYed should not 
be close together (address of the ENTRY should be further away than the address 
of the PROGRAM-ID, by at least the length of the program in its entirety).

Given that that checks out, I'd DISPLAY the information in the handler, and see 
how much appears. If two conditions are being presented, knowledge of the 
second condition will be useful.

Does your program on Git work, or exhibit the problem? If it doesn't exhibit 
the problem, what needs to be done to it to do so?

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

Reply via email to