RE: Text on report

["Stone, Joel" <StoneJ@xxxxxxxxxxxxxxxx>]

Title: RE: Text on report

I think we are both correct.  A SRC-PF can be read by RPG, but it cannot be read using a key.  I was suggesting setting up a multi-purpose comment file using a group key prefix.  Then he can use the comment file in many pgms and systems, instead of creating a new comment file for each app!

Also, SQL, OPNQRYF and such need to read the file by key if one wants to join the comments to various records in various reports.

-----Original Message-----
From: Jeff Crosby [mailto:jlcrosby@fwi.com]
Sent: Friday, June 23, 2000 3:26 PM
To: RPG400-L@midrange.com
Subject: Re: Text on report

"Stone, Joel" wrote:

> On the other hand, source files are limited use files.  They cannot be used
> with Query/400, nor with OPNQRYF, nor with lots of other products.
>    <snip>
> With source files, you always have to convert the file to a PF prior to
> using it.  If there are lots of msgs in a source file, it could take awhile
> to convert to a PF, especially in an interactive job.

What I am understanding you to say is that is you are going to put the
text in a PF, it must be a PF-DTA, not a PF-SRC, because you can't read
a PF-SRC in an RPG program.  I get this from your statement that you
need to convert the source file to a PF.  If this is what you are
saying, you are incorrect.  A PF-SRC is still a PF.  You only need an F
spec with QTXTSRC as the file name, and it works like any other
externally described file.  No special incantations needed.  I know
because I've done it.  You can use Query/400 on a source file as well.

If I misunderstood you, sorry.

--
-Jeff
The opinions expressed are my own and not necessarily
the opinion of my company.  Unless I say so.
+---
| 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
+---