There is no bug, you simply need to understand how SHARE(*YES) works. 
Effectively
the file cursor is shared across many programs and each program must make NO
assumptions as to where the cursor is pointing and EXPLICTLY position to the 
data it
needs.

Vini Kolathur wrote:

>      Yes i agree that the CPYFRMQRYF is not necessary there. I had just put
>      that there to make sure that the record selection is working fine. So
>      does that mean that IBM has to fix up the CPYFRMQRYF to clsoe the file
>      after finishing it's work.
>
>      Vini
>
> ______________________________ Reply Separator 
>_________________________________
> Subject: Re: Problem in OPNQRYF
> Author:  Rob Berendt <rob@dekko.com> at ARO-INTERNET
> Date:    7/28/99 4:39 PM
>
> I agree, if the CPYFRMQRYF is not used, then delete the step.
>
> Of course my favorite solution is to replace the OPNQRYF with
> imbedded SQL in the RPG program.
>
>
>
>
> joepb@tip.nl on 07/28/99 04:22:27 PM
> Please respond to RPG400-L@midrange.com@Internet
> To:     RPG400-L@midrange.com@Internet
> cc:
> Fax to:
> Subject:        Re: Problem in OPNQRYF
>
> Vini,
>
> >      1.Override the file with Share(*yes).
> Causes an ODP (open data path) for this file to be shared by different
> programs.
>
> >      2.Do a OPNQRYF with a Query select expression.
> Creates an ODP with the record pointer pointing at the first selected
> record.
>
> >      3.Do a CPYFRMQRYF to a file in QTEMP which is not used anywhere.
> Uses the ODP, leaving the pointer after the last selected record.
>
> >      4.Call a RPGILE program which reads the file used in OPNQRYF.
> Uses the same ODP with the pointer still at EOF, so when it tries to read,
> it gets EOF.
>
> You could either reposition the pointer (POSDBF POSITION(*START)) or leave
> out the CPYFRMQRYF (pretty useless, if the file in QTEMP is not used
> anywhere).
>
> Joep Beckeringh
>
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This is the RPG/400 Discussion Mailing List!  To submit a new         *
> * message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
> * from this list send email to MAJORDOMO@midrange.com and specify       *
> * 'unsubscribe RPG400-L' in the body of your message.  Questions should *
> * be directed to the list owner / operator: david@midrange.com          *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This is the RPG/400 Discussion Mailing List!  To submit a new         *
> * message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
> * from this list send email to MAJORDOMO@midrange.com and specify       *
> * 'unsubscribe RPG400-L' in the body of your message.  Questions should *
> * be directed to the list owner / operator: david@midrange.com          *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This is the RPG/400 Discussion Mailing List!  To submit a new         *
> * message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
> * from this list send email to MAJORDOMO@midrange.com and specify       *
> * 'unsubscribe RPG400-L' in the body of your message.  Questions should *
> * be directed to the list owner / operator: david@midrange.com          *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *



+---
| 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



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].