Thanks a lot guys for the good info on ODP. I think SEQONLY(*NO) on the OPNQRYF
should solve my problem.

Vini

______________________________ Reply Separator _________________________________
Subject: Re: Re[2]: Problem in OPNQRYF
Author:  "Joep Beckeringh" <joepb@tip.nl> at ARO-INTERNET
Date:    7/30/99 11:27 PM


Vini,
     
>         I feel that IBM should fix up the CPYFRMQRYF to reposition the 
file
> pointer to the first record after it has done it's piece of work.
     
Will you then fix up your RPG program to reposition the file pointer as 
well?  Like F. Kolmann pointed out, using SHARE(*YES) implies that no 
program should make assumptions where the file pointer is.  CPYFRMQRYF does 
not, as your observation shows.  Your program does; it assumes the pointer 
is at the beginning of the file.  However, this is easily fixed with POSDBF 
in the CL.
     
As for the problems with SETLL *LOVAL: this will not try to position to the 
first record, but to the first selected record, but if you want to use 
random access, you'll have to specify SEQONLY(*NO) on the OPNQRYF.
     
Joep Beckeringh
     
     
+---
| 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 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 ...


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].