|
Another way to change the OUTQ for a spooled file is change it while it’s still open, e.g. by putting in your AS/SET program: C CHGSPLFA INV210O SPLNBR(*LAST) OUTQ(PRT02) This overcomes the problem of not being able to open and close the printer file for an OVRPRTF command to work. Of course if you need a variable outq, you’ll still have the put the above statement into a QCMDEXC call. Bernard Burchell. > <<snip>> >As usual, "it depends". If program "A" performs the OVRPRTF for print program >"B" which is called from "A", it will work fine. It all has to do with the >scope of overrides on the AS/400. When you perform an override, it is valid >for both the current call stack level and all subsequent levels (valid for "A" >which calls "B" and maintains the override, and if "B" calls "C" the override >will be valid for "C" as well). The problem is, unless you perform a manual >"OPEN" with a user-controlled file, RPG program "A" (under ye olde RPG logic >cycle) has already opened all of the files before the OVR gets performed. I >know of know way to make a print file "UC" under AS/Set, but would love to >hear if it could be done. > >Your specific example could be due to the OUTQ placed under "printer >characteristics" (option 7, I _think_) on the report layout. Even so, it will >still only work for one OUTQ, rather than the several suggested by the >original question. > >Clear as mud ;-)? > >Dean Asmussen >Enterprise Systems Consulting, Inc. >Fuquay-Varina, NC USA >E-Mail: DAsmussen@aol.com > +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.