Re: opnqryf interferes with chain

Buck,

compile listing shows FLDCHAR20 is indeed the key field...

K e y F i e l d I n f o r m a t i o n

File Internal External

Record field name field name Attributes

1 TESTTBL

RTBL

FLDCHAR20 CHAR 20

* * * * * E N D O F K E Y F I E L D I N F O R M A T I O N * *
* *


So I am still wondering what the ovrdbf/opnqryf is doing to cripple the
chain?



On Tue, Mar 20, 2018 at 11:46 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

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.

--
--buck

http://wiki.midrange.com
Your updates make it better!

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD