× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

Here's our situation:

PGM1 is a ILE RPG Program in LIB1. Was compiled with ACTGRP(*DFT).
SRV1 is a service program in LIB1
PRC1 is a procedure of SRV1.

PGM1 is using PRC1 in an Eval operation.

Now let's complicate the thing a little.

We have another SRV1 in LIB2 that is using different operations but
still has the PRC1.

The first situation is:

LIBL has LIB1 as first Library.
PGM1 calls PRC1 from SRV1 of LIB1.
PGM1 exits with INLR set *ON and then a RCLRSC is done in the caller CL
program.

Then,
We put LIB2 on top of LIB1 in LIBL.
PGM1 calls PRC1 from SRV1 on LIB1.
PGM1 exits with INLR set *ON and then a RCLRSC is done in the caller CL
program.

Why does PGM1 still points at SRV1 from LIB1?


Then we found out that if we compile PGM1 with ACTGRP(TEST), PGM!
change it'S pointer on the second call to PRC1.
(the activation group's name does make any difference as long it is not
*DFT or *CALLER)

Is this behavior normal or should we apply a PTF? Or are we missing
something?

Thanks,



Pascal Bellerose
pascal_bellerose@xxxxxxxxxxxx
Cascades Canada inc.
Programmeur-analyste au support
Telephone: 819-363-6114 (2114)
Télécopie/Fax: 819-363-6155 (6155)

Tenez-vous vraiment à imprimer ce courriel?
Changez d'environnementalité!

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.