Re: ile question

I will just add a comment to your original post.

Interface changes (i.e. PI) _never_ impact signatures or really anything else.

I would have to agree with Brad that in the original scenario, a copy of the Service Program was still active. In the far distant past the debugger did some funky stuff with persistent Activation Groups that caused oddball behaviours but that was all pulled out eons ago.


Jon P.

On Mar 31, 2023, at 9:38 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:

Thanks Brad!

After further research, I think the problem is even further down the stack
than this.
So what I provided probably is not diagnosable at all.

I'll try and get more details.

thanks

Jay

On Fri, Mar 31, 2023 at 9:15 AM Brad Stone <bvstone@xxxxxxxxx> wrote:

Activation groups most likely.

If the service program was called previously it is in memory. I'm sure Jon
or someone else can explain it in more detail (QRPLOBJ?) but I always
suggest people start a new job when installing new service programs with my
software.

Compiling the calling program, as you found, also solves this "issue". So
would reclaiming the activation group you're using for the program/svc pgm.

On Fri, Mar 31, 2023 at 8:10 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

I have pgmA that calls srvPgmA.procedureA

srvPgmA.procedureA was modified.
Nothing changed with the PI between pgmA and this procedure.
This procedure was calling a C function but was changed to call
another srvPgm instead (that C function is called here instead).
Again, no changes to the PI between pgmA and srvPgmA.procedure.

When srvPgmA was recreated the same signature was preserved and remained.

Now when we debug pgmA and step into srvPgmA.procedureA, the debugger

gets

lost.

What is going on in this scenario?

if we recompile pgmA, all is good.

Since there were no changes in the srvPgmA.procedureA pi, and no
procedures were were rearranged in the module and binder source for
srvPgmA, I'm not sure why this is happening.

Can someone explain?

tia

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.