Re: CallP & CallB in SQLRPGLE ??

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:
> 
> Thanks to everyone for their suggestions. I guess I have a lot to learn
> ;-) -- maybe as much about activation groups as overrides, since I guess I
> thought that unless I told it otherwise an ILE program would run in the
> default activation group.
> 
> I'm still a little confused, though. The following always worked:
> 
>         . . .
>         Call PgmB
>         Override. . . .
>         Call  PgmC
>         Delete Override
> 
> but this didn't:
> 
>         . . .
>         CallB PgmB
>         Override. . . .
>         Call PgmC
>         Delete Override. . .
> 
> I got the second example to work by compiling PgmC to use *CALLER
> activation group, so my new question is: why does replacing Call PgmB with
> CallB PgmB cause PgmC to respond differently to the override?
> 
> (Maybe Gary Guthrie's article will explain this? I'm looking forward to
> it!)
+---
| 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
+---