Re: Retrieving key field info from OPNQRYF command

Well, you got me, Allen.

I have a couple of programs that I was able to combine in an effort to
prove/disprove that capability.  As yet, I am unable to retrieve anything
other than the DEFINED keys for the file, not as actually presented from
OPNQRYF.  Methinks OPNQRYF doesn't populate the feedback information as we
would hope.  I cannot guess why that choice would have been made.  But if
it isn't in the feedback area (and I can't find a way to force it into
there), then we're not going to be able to pull it out.

Perhaps there is some other way?  What is it that you're trying to
accomplish, big-picture wise?

Dennis






Allen Hartley <hartley@prodatacomputer.com>@midrange.com on 01/22/2002
12:18:47 PM

Please respond to mi400@midrange.com

Sent by:  mi400-admin@midrange.com


To:   mi400@midrange.com
cc:
Subject:  Re: [MI400] Retrieving key field info from OPNQRYF command


Dennis,

Yes I specified to allow override processing '1' and I tried both *INT &
*EXT
for the format type (field 9).

Thanks
Allen

Dennis Lovelady wrote:

> Hmmm... that doesn't sound right, though I must admit not playing with
> OPNQRYF's effects on the API.
>
> I'll toy with it, but in the meantime, are you certain you've specified
to
> allow override processing in the API  ('1' in API parm field 7)?
>
> Dennis
>
> Allen Hartley <hartley@prodatacomputer.com>@midrange.com on 01/22/2002
> 12:03:45 PM
>
> Please respond to mi400@midrange.com
>
> Sent by:  mi400-admin@midrange.com
>
> To:   mi400@midrange.com
> cc:
> Subject:  Re: [MI400] Retrieving key field info from OPNQRYF command
>
> Dennis,
>
> I use the QDBRTVFD API to get the file information FILD0100 and from that
I
> get the key information based on the key offset, but this is only for the
> file which has no keys and not for the currently used access path
> (OPNQRYF).  I tried to use FILD0300 to retrieve the key field information
> but it comes back with an error stating that the file is not a keyed
file.
>
> Allen
>
> Dennis Lovelady wrote:
>
> > Hi, Allen:
> >
> > Have a look at the QDBRTVFD API.