• Subject: RE: Problem in OPNQRYF
  • From: Chris Bipes <ChrisB@xxxxxxxxxxxxxxx>
  • Date: Wed, 28 Jul 1999 13:11:28 -0700

Does the qtemp file have the same name as the QPNQRYF?  If so, you have
opened the qryf, not the qtemp file.  Get rid of the ovrdbf share(*yes), not
needed to cpyfrmqryf.  Add an ovrdbf file to qtemp/file.  That should force
the rpgle to open the work file in qtemp and not the queried file.

-----Original Message-----
From: Vini.Kolathur@msasaro.com [mailto:Vini.Kolathur@msasaro.com]
Sent: Wednesday, July 28, 1999 11:38 AM
To: RPG400-L@midrange.com
Subject: Problem in OPNQRYF


     Hi,
        I am working on a V4R1 and i faced this queer problem.
     These are following sequence of steps that i follow in a CLP:
     1.Override the file with Share(*yes).
     2.Do a OPNQRYF with a Query select expression.
     3.Do a CPYFRMQRYF to a file in QTEMP which is not used anywhere.
     4.Call a RPGILE program which reads the file used in OPNQRYF.
     
     The problem is that when the RPG is called the file is already at EOF.
     When the same thing is done with step 3 left out then the program 
     works fine. Is that a bug somewhere or am i missing something.
     
     Vini
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.