|
You won't get what you want, in all likelihood, because the print text will change the line counting that would happened in the program that generated the spooled files . Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com |---------+-----------------------------> | | John Ross | | | <jross-ml@netshare| | | 400.com> | | | Sent by: | | | midrange-l-admin@m| | | idrange.com | | | | | | | | | 11/23/2002 01:29 | | | PM | | | Please respond to | | | midrange-l | | | | |---------+-----------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: midrange-l@midrange.com | | cc: | | Subject: RE: Changing PRTTXT on a spool file | >------------------------------------------------------------------------------------------------------------------------------| How about? /* Copy the report to a database file */ CRTPF FILE(QTEMP/SPOOLFILE) RCDLEN(133) MONMSG MSGID(CPF7302) CPYSPLF FILE(QSYSPRT) TOFILE(QTEMP/SPOOLFILE) + SPLNBR(*LAST) MBROPT(*REPLACE) CTLCHAR(*FCFC) /* Rebuild the spooled file */ OVRPRTF FILE(QSYSPRT) CTLCHAR(*FCFC) PRTTXT('Some text you want added') CPYF FROMFILE(QTEMP/SPOOLFILE) TOFILE(QSYSPRT) DLTOVR FILE(QSYSPRT) any cleanup you want/need to do. I have not tested this, but I am pretty sure it will be the new job and user information on the new report. What I mean is if user A runs the initial report and then user B runs the program to add the PRTTXT you would have to do a WRKSPLF SELECT(B) not sure if the API's would get around that problem or not. If you do write it with the API's how about making them open source programs? John Ross At 09:33 AM 11/22/2002 -0800, you wrote: >Thanks Vern. > >Unfortunately, I have no control of the job which creates the print file. In >fact, the file could come from anywhere. I only have access to it after the >fact. > >I'm not opposed to using an API. Does anyone have an example? > >Thanks. > >Albert _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.