RE: Problem in OPNQRYF

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

>>          Many people have suggested putting a *LOVAL SETLL in the RP
>>  This
>> would only crash the program because the *LOVAL SETLL will try to
>>  position it to
>> the first record. This necessarily could not be the first record in
>>  the
>> selection criterion.

The key sequence and the selection criteria are unrelated.  I can do a
QRYSLT(STATUS='Y') and KEYFLD(CUSTNO).  *LOVAL SETLL will position me to the
first record of the customers having STATUS='Y'.  This will be the record
with the lowest customer number.

>>         I feel that IBM should fix up the CPYFRMQRYF to reposition t
>>  file
>> pointer to the first record after it has done it's piece of work.
>>
>
>Its not a bug in CPYFRMQRYF!   I have about a dozen programs that I
>use that have worked great since V2R2, and would stop working if
>IBM changed this behavior!  This is the way it was designed to work,
>its the way its always worked, and theres no reason to change it.

I have programs doing this from System/38 days, maybe release 6 or 7.  It
always worked like this and it's supposed to work like this.  That's how
shared open files work. 

>The whole IDEA behind OVRDBF SHARE(*YES) and using an OPEN file,
>that you have to CLOF to close is that you can keep reusing it
>without having to close the file!   Thats the whole reason it exists!!

Shared opens exist so that multiple programs can position the file pointer
without having to do a full open.  It is a performance enhancement.  Try it
- you'll like it!

Buck Calabro
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---END