ON-EXIT not being fired?

My understanding is that ON-EXIT should always be fired.

But I have what appears to be a case where it wasn't fired.

More specifically, my ON-EXIT calls a procedure in a *SRVPGM to log the
status at the end of the program..

Usually I see something like so
ON-EXIT B2D35006-D918-1A5D-9C32-0004AC1C3FB4
CurrentState: Successful completion
INPUT PARAMETERS B2D35006-D918-1A5D-9C32-0004AC1C3FB4
CurrentState: Begin MainLine Code
ON-EXIT A7A81006-D914-1A5D-9C32-0004AC1C3FB4
CurrentState: Successful completion
INPUT PARAMETERS A7A81006-D914-1A5D-9C32-0004AC1C3FB4
CurrentState: Begin MainLine Code

But today we had an issue and I saw the following
INPUT PARAMETERS 4CE3F006-D8A4-1A5D-9C32-0004AC1C3FB4
CurrentState: Begin MainLine Code
INPUT PARAMETERS 66905006-D60D-1A5D-9C32-0004AC1C3FB4
CurrentState: Begin MainLine Code
INPUT PARAMETERS F32AA006-D5F9-1A5D-9C32-0004AC1C3FB4
CurrentState: Begin MainLine Code

Anybody see or know of an instance where the ON-EXIT doesn't run?

One possible explanation, the problem today was due to mismatching
parameters between the SQL external stored procedure definition and the RPG
program being used. And since the SP was defined as "PARAMETER STYLE SQL"
, there's a bunch of implicit parms that the DB normally passes after the
explicit parms.

SO is this just another case of "memory corruption is like a box of
chocolates...you never know what you're going to get."

Charles