Re: Problems with spool files

[Charles Wilt <charles.wilt@xxxxxxxxx>]

James,

In the spirit of teaching a man to fish vs. giving him a fish...

Spool files exist on in output queues.

Which output queue a spool file is created in is determined by the
OUTQ parameter on the printer file.  The default value of OUTQ on a
printer file is OUTQ(*JOB) which means to use the out queue specified
in the job attributes of the job creating the spool file.

The OUTQ attribute of a job can be changed via the CHGJOB command, but
is initially determined for an interactive by the OUTQ parameter on
the job description.  The default value of OUTQ on the job description
is OUTQ(*USRPRF).  The default value of OUTQ on a user profile is
OUTQ(*WRKSTN).  The default value of the OUTQ parameter for a
workstation device is OUT(*DEV) which means use the output queue
associated with the device specified in the PRTDEV parameter of the
workstation description.  The default value of PRTDEV for a
workstation is PRTDEV(*SYSVAL); which means use the printer specified
in the QPRTDEV system value.

Here's a link to the documentation in the info center:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzalu/rzalurouting.htm

If the output queue holding the spool file is attached to a working
printer, the spool file will be printed unless the spool file  is
HELD.

I'd strongly recommend using your own printer file instead of QPRINT;
with HOLD(*YES) and strongly consider using the EXTFILE keyword with a
qualified name in order to prevent your program from using another
printer file of the same name.

Consider using your own OUTQ, but think about clean up.  Does your
process automatically delete the spool file after transforming, or
will your users need to take care of it?

HTH,
Charles




On Tue, Aug 24, 2010 at 1:49 PM, James H. H. Lampert
<jamesl@xxxxxxxxxxxxxxxxx> wrote:
> Actually, the user profile must NOT be changed, and if there is even a
> remote possibility that an override would interfere with other things to
> be printed, then THAT must not happen, either.
>
> The program, on the other hand, can be changed at will, which is why I
> suggested creating my own private print file and output queue, under a
> different name.
>
> --
> JHHL
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.