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

I was curious about the order of the functions as well. Firts
function starts subsystems and application tasks. Second function
ends the tasks and then the subsystems. Doesn't matter which function
is called second. Log in, use first function, then second and it
fails. Logout and back in and second function works but first won't.

Message id CPA0702

From program QCLXERR
From Library QSYS

Instruction 00C6

To program *EXT

ILE Control language (CL) procedure SSYZCOCL in module SSYZCOCL in
program SSYZCOCL in library BSYOBJ1 detected an error at statement
number 0000006500.

That CL statement is: CALL PGM(SSYZCO) PARM(&ENV &FUNC &RETCD)

The first error returned is in the RPGLE program - RNQ0202. The call
to ONLINEUP ended in error (C D G F).

RPG procedure SSYZCO in program BSYOBJ1/SSYZCO at statement 008400
called program or procedure ONLINEUP, which ended in error.

The procedure ONLINEUP was prepared by the vendor. Doesn't mean it
has no issues. Just wasn't written here. It appears to be used to
check whether the selected environment is active or not.

John McKee

On Tue, Jun 11, 2013 at 4:20 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

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.

--
Regards, Chuck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.