Re: RCLRSC - Round 2

CRTBNDCL creates a *PGM object.
I did not try it, but *CALLER for procedure in this case could be a PEP and
not the program which has CALL statement for PGMA.
If this is a reason, try to change CALL PGMA to a bound/procedure call to
PGMA (in this case PGMA should not be a *PGM, of course).

    Alexei Pytel





                    Paul Tuohy
                    <tuohyp@attglobal.n       To:     midrange-l@midrange.com
                    et>                       cc:
                    Sent by:                  Subject:     RCLRSC - Round 2
                    midrange-l-admin@mi
                    drange.com


                    10/26/2001 02:03 PM
                    Please respond to
                    midrange-l





Hi all - now to my next problem with RCLRSC.

It now involves an ILE RPG program. Yes, I know that I should be running
ILE programs in their own activation group and not in the default
activation group - but no choice here.

OK. Same as before. I have a program called TEST. It is an RPG IV
program compiled as DFTACTGRP(*NO), ACTGRP(*CALLER) and it is running in
the default activation group. The program simply loops until F3 is
pressed and does calls to:-

                     Call PGMA
                     Call PGMB

PGMB is an RPG IV  program compiled as DFTACTGRP(*NO), ACTGRP(*CALLER).

PGMA is a CL program that simply issues a RCLRCS LVL(*CALLER).

1. When PGMA is a CLP, everything works fine.
2. When PGMA is a CLLE compiled with CRTBNDCL DFTACTGRP(*YES), it does
NOT work (which really surprises me, as I thought that this should
emulate OPM).
3. When PGMA is a CLLE compiled with CRTBNDCL DFTACTGRP(*NO)
ACTGRP(*CALLER), it does NOT work.

Surely option 2 should work?

Any suggestions or comments please

TIA

Paul Tuohy
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.