× 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.



On 12-Jan-2012 10:11 , James Lampert wrote:
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?


No idea, but per no mention if the problem was circumvented...

Pending resolution to the above, the request to "OVRDSPF TheFile TOFILE(*LIBL/TheFile) OVRSCOPE(as_required)" should allow the program to run without error. And FWiW, a similar override in effect for the particular named FILE() and a library qualified file named TOFILE() could also cause the described problem, irrespective of what DSPPGMREF shows and what the RPG run-time effects with regard to the value shown.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.