RE: Text on report

Jim,
Here is an idea, but it may not be applicable to your situation.
It is based on the following steps that can be used to create a copy of an
existing spool file.

1.      The spool file is copied to disk via CPYSPLF CTLCHAR(*FCFC).
        At this point the disk file could in fact be altered in any way
(especially if it was a         cheque run, if you catch my drift).
2.      Then execute the OVRPRTF QSYSPRT CTLCHAR(*FCFC).
        You can include any other parameters of the OVRPRTF cmd if you
desire that change the  attributes of the new spool file.
3.      Then execute the CPYF cmd to copy the disk file to QSYSPRT.
        This produces a new spool file which will differ only if you have
changed the content or  overridden the attributes.

In your situation step 1 above could be replaced as follows.
1(a)    Using SEU, type the text you require into a source member.
        In the first column of each text line you must enter the appropriate
*FCFC line formatting
        character. These are very simple.
1(b)    Then copy the source member to the disk file using CPYF
FMTOPT(*CVTSRC).

Then perform steps 2 and 3 above to generate the report.
If you create a simple CL pgm that takes a source member name as a parameter
and code steps 1(b) then steps 2 and 3 then you have yourself a report
utility and you hardly had to write any code at all.

You can demonstrate how easy it is if, instead typing a sample document into
SEU, just copy an existing spool file to disk, then into a source member,
then perform the new steps as above.

Hope this helps
Cheers, Peter Connell   
  

-----Original Message-----
From: End of the Trail [mailto:endofthetrail@skyenet.net]
Sent: Wednesday, June 21, 2000 3:24 PM
To: RPG400-L@midrange.com
Subject: Re: Text on report


Since you are asking the worst of two evils, I vote for the file routine.
If you load a 80 or 132 variable from a file and print it, it allows you to
change the wording or paragragh on the fly.  No recompiling or maintaining
the program.

That is my 2 cents.

Eurrat Saylor    www.skyenet.net/~endofthetrail/elsresum.htm
9562 East  750 North
Walkerton (Koontz Lake), IN  46574
219-586-7970  tel
219-586-2677  fax

-----Original Message-----
From: Jim Langston <jlangston@conexfreight.com>
To: RPG400-L@midrange.com <RPG400-L@midrange.com>
Date: Tuesday, June 20, 2000 2:51 PM
Subject: Text on report


>I have a report to generate that has quite a bit of text on it.  A whole
paragraph, basically.
>
>I'm not using the reports, but O specs in my RPG program.  I know some
would say, and probably rightfully so, to use a report program for this, but
I want to do this in O specs.
>
>My question is, how do you feel would be the best way to get this long text
data into my program to print on the page?  There are a number of ways I
could do it, including puting it in a file, then opening it and reading it a
line at a time into a variable and printing it out.  Or I could do a Compile
time array and stick it on the bottom of my program.
>
>I could type out the text in the O specs and just space it accordingly, but
the rather short length of the input fields for the O specs for constants
kinda limits me on this.
>
>There is another type of array, I think, where I could create the file and
then load the array with the information at run time from the file, though
I've never done that before.
>
>Does anyone have any other, maybe even better, suggestions?
>
>Regards,
>
>Jim Langston
>
>+---
>| 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
>+---
>

+---
| 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
+---
 
**********************************************************************************************************
Privileged / Confidential Information may be contained in this message. If you 
are not the addressee indicated in this message (or responsible for delivery of 
the message to such person), you may not copy or deliver this message to 
anyone. In such case, you should destroy this message, and please notify us 
immediately. 

Please advise immediately if you or your employer does not consent to Internet 
e-mail for messages of this kind. Opinions and other information expressed in 
this message are not given or endorsed by my firm or employer unless otherwise 
indicated by an authorised representative independent of this message.
+---
| 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
+---