× 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 3/20/2018 10:40 AM, Jay Vaughn wrote:
Can anybody tell me why my chain won't work in my pgm when the below two
commands are issued first before the pgm runs?


OVRDBF FILE(TESTTBL) TOFILE(*FILE) OVRSCOPE(*JOB) SHARE(*YES) SEQONLY(*NO)
OPNSCOPE(*JOB)

OPNQRYF FILE((*LIBL/TESTTBL *FIRST *ONLY)) OPTION(*INP) KEYFLD((FLDCHAR20
*ASCEND)) SEQONLY(*NO) OPNSCOPE(*JOB)

program is compiled with...

H DftActGrp(*No) ActGrp(*Caller)

ftesttbl if e k disk

d g_fldchar20 s like(fldchar20) inz('0000001')

chain g_fldchar20 testtbl;
if %found(testtbl);
dsply (fldchar20);
else;
dsply ('not found');
endif;

Look at the compiler listing for the program.
What key is listed for TESTTBL?

Assuming that key is not FLDCHAR20, the program should be compiled in
such a way that the key matches between the RPG and the access path used
at runtime.

One way is to run the OPNQRYF, execute the OVRDBF, and compile the RPG.
In this way, the compiler will use the exact same file/access path that
the runtime does.

Another way is to create a PF with no records in it, which is an exact
copy of TESTTBL, but keyed by FLDCHAR20 instead. Change your F-spec to
point to this empty PF, change the OVRDBF to override the empty PF to
the OPNQRYF access path.

Another solution is to toss OPNQRYF altogether and use embedded SQL.


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.