Re: Sanity check: RTVOBJD *LIBL/ABCMONRG RTNLIB(&LIBNAM), then CALL &LIBNAM/ABCMONRG???

Jim,
How would that code sample find an object which is not in your library
list? The RTVOBJD, as coded, would not.

On Wed, Feb 5, 2025 at 8:16 AM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

—Or— is it assuming the library may not be in the library list and the
original developer used this technique to find it?

I’ll do something like this for utility programs where the library is
often not in any lib list.


Jim Oberholtzer
Agile Technology Architects

On Feb 4, 2025, at 11:14 PM, Don Brown via MIDRANGE-L <

midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

 It is using the library list to find the program object.

So no, the call could be unqualified and call the same program.

Cheers
Don



Don Brown

Senior Consultant

[1]OneTeam IT Pty Ltd
P: 1300 088 400

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of

Dan

Bale
Sent: Wednesday, 5 February 2025 2:27 PM
To: Midrange Systems Technical Discussion <

midrange-l@xxxxxxxxxxxxxxxxxx>

Subject: Sanity check: RTVOBJD *LIBL/ABCMONRG RTNLIB(&LIBNAM), then

CALL

&LIBNAM/ABCMONRG???

Code snippet of a production CLP program I am currently modifying:

DCL VAR(&LIBNAM) TYPE(*CHAR) LEN(10)
RTVOBJD OBJ(ABCMONRG) OBJTYPE(*PGM) RTNLIB(&LIBNAM)
CALL PGM(&LIBNAM/ABCMONRG)

Is there *any* scenario where "CALL ABCMONRG" without the first two
statements doesn't always call the program from the same library?

&LIBNAM is not used anywhere else in the program.
There are no intervening statements between the RTVOBJD and CALL

commands.

There is enough complexity in other parts of the program that tells me

the

original programmer was no dummy. Am I the dummy?
*** CONFIDENTIALITY NOTICE: The information contained in this
communication may be confidential, and is intended only for the use of

the

recipients named above. If the reader of this message is not the

intended

recipient, you are hereby notified that any dissemination,

distribution,

or copying of this communication, or any of its contents, is strictly
prohibited. If you have received this communication in error, please
return it to the sender immediately and delete the original message and
any copy of it from your computer system. If you have any questions
concerning this message, please contact the sender. ***
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To

subscribe,

unsubscribe, or change list options,
visit: [2]https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[3]https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
Message protected by MailGuard: e-mail anti-virus, anti-spam and

content

filtering.
[4]https://www.mailguard.com.au

References

Visible links
1. https://www.oneteamit.com.au/
2. https://lists.midrange.com/mailman/listinfo/midrange-l
3. https://archive.midrange.com/midrange-l.
4. https://www.mailguard.com.au/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.