|
I'm supporting a recent V6.04 mixed-mode BPCS implementation, and my question is this: what are the implications of removing the *PRTF override command in CL program SYS501C? It is currently wreaking havoc with a variety of in-house programs and queries that have been added to BPCS menus and which use a varied mix of page size parameters. Users don't understand why reports that fit on the page with condensed print last week have suddenly expanded to 10CPI and go off into oblivion. Creating CL programs to provide print file overrides for so many small jobs doesn't seem practical, but I'm leery of pulling out the *PRTF override. Have any of you had to deal with this? What worked? Any ideas or experience are welcome! Dave Thomas Radius Information Systems Ltd. Toronto ON -- Dilbert's Words Of Wisdom: "I love deadlines. I especially like the whooshing sound they make as they go flying by."
begin: vcard fn: David Thomas n: Thomas;David org: Radius Information Systems Ltd. adr: 295 The West Mall;;Suite 320;Toronto;ON;M9C 4Z4;Canada email;internet: davet@radiusinfo.com tel;work: 416-626-9556 tel;fax: 416-626-9565 tel;home: 416-922-3899 x-mozilla-cpt: ;0 x-mozilla-html: TRUE version: 2.1 end: vcard
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.