As has already been noted, use CPYFRMQRYF.  If the open scope of the 
query Open Data Path is to the activation group [OPNSCOPE(*ACTGRPDFN)], 
I presume the request would have to be from within an ILE CL compiled in 
that activation group or perhaps *CALLER would work [but being in debug 
at a request level out of the debugger, probably not?].  Given OPNQRYF 
OPNID(MYQRY), then use CPYFRMQRYF FROMOPNID(MYQRY) with TOFILE of either 
*PRINT for a somewhat formatted output [numbered rows], or QSYSPRT for 
an unformatted output, or to a database file OUTFILE(QTEMP/qryf) 
CRTFILE(*YES).  For the output to a database file, you can then RUNQRY 
*NONE QTEMP/QRYF to view in a report form.  For either of the print 
options, OUTFMT(*HEX) is sometimes desirable.
  Note however, so the program can continue as though nothing happened, 
use POSDBF OPNID(MYQRY) POSITION(*START) after the CPYFRMQRYF.  The copy 
from the open query file request will leave the ODP position at *END, so 
when returning to the program, the request by the program to read from 
the ODP would encounter the 'end of file' condition.
Regards, Chuck
-- All comments provided "as is" with no warranties of any kind whatsoever.
Bob O. wrote:
Is there a way to view the contents of a file that is overriden and has 
records selected via OPNQRYFL during a STRISDB session?  If you do F21 
during the debugging session and do an UPDDTA command, you get the full 
file.  I'd like to see the contents after the records are selected.  
Thanks!
_________________________________________________________________
Make every IM count. Download Messenger and join the i’m Initiative now. 
It’s free. http://im.live.com/messenger/im/home/?source=TAGHM_MAY07
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.