Re: Program runs once correctly, not again until signoff/signon

On 11 Jun 2013 13:25, John McKee wrote:

A CLLE calls an RPGLE. Works perfectly the first time. The CLLE
takes parameters. Of interest is the second, which determines what
the program does.

The second parameter, presumably "determines what the program does" and thus is deemed "of interest"... Or is it [though I presume not] the second time that program is called that is of interest because the program fails?

The program has two functions. If I run it with one function, trying
to run it with the second function results in MCH3402 "Tried to refer
to all or part of an object that no longer exists"

What are the full details of the MCH3402, the context of the failure, that would be presented in an F6=Print after F1=Help on the message in the active joblog, or a DSPJOBLOG OUTPUT(*PRINT) with LOG(4 0 *SECLVL) in effect [albeit for MCH3402, *MSG is as good as *SECLVL].

Log out and back in, and the function works.

And if the program is instead run with function-two first on the fresh login, followed by being run with function-1?

Program does turn on *INLR immediately before a Return.

I have not seen this error before and do not know how to debug it.

What the failing source statement is, is a good start, to try to identify what is the pointer that is identified as having its object destroyed.