Re(2): CallP & CallB in SQLRPGLE ??

["Mike Naughton" <mnaughton@xxxxxxxxxxxx>]

Okay -- I think I found the answer (in an answer by Bryan Meyers in
August, 1998, News/400):
 
"If the program that executes the override is an ILE program running in an
ILE activation group, activation group level scoping
(OVRSCOPE(*ACTGRPDFN)) is the default. If the program (ILE or OPM) is
running within the default activation group, call stack level scoping is
in effect. "

When I compiled PgmA without a CallB, it compiled to the default
activation group, so call stack level scoping was in effect and PgmC
picked up the override. Once I added the CallB, as Jim pointed out, I
couldn't use the default activation group anymore, and then the fact that
PgmC was compiled with *NEW became HUGELY significant.

Wow! and thanks again to everyone who helped!


RPG400-L@midrange.com writes:
>As Mike Naughton said, it's not specifically the CallB that did it,
>but the way you compiled it.  And since you used CallB you didn't use
>the default activation group, right?
>
>To bind to a service program (maybe even a module, haven't looked into
>that yet) you can not use the default activation group, as you will
>get the error:  Parameter BNDDIR not allowed with DFTACTGRP(*YES).
>Which basically means you just left OPM land into Activation Group
>world.
>
>Regards,
>
>Jim Langston
>
>Me transmitte sursum, Caledoni!
>
>
>Mike Naughton wrote:


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---