James,

Is the RPG qualifying the library as part of a USROPN? I've done this if I don't find the file the library list. If it isn't in the library list I hardcode the library to the production library it is supposed to reside in.

Gary Monnier

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Thursday, January 12, 2012 10:11 AM
To: RPG programming on the IBM i / System i
Subject: Weird issue with a display file

I've got a program that uses a display file. And I just discovered that it's looking for its display file in a specific library, ignores the *LIBL, and complains if the library where it was looking for the display file doesn't exist.

And doing a DSPPGMREF on another program with a display file, I discovered that it's not the only one that looks for its DSPF in a specific library.

The problem with this specific case is that when installed on the customer box, the program looks for the display file in the wrong library.

I've been writing RPG programs for over 17 years, and I've never noticed this before. I don't recall database files being implicitly qualified to wherever the compiler found them at compile time. This would seem to make it difficult to move programs that use display files.

Can somebody shed some light on this?

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.