MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2013

RE: OUTQs & printing



fixed

If things are actually printing in strange places, be sure to check WRKWTR device name versus option 8 to the OUTQ name. Sometimes creative users assign a different queue to a writer (using the *BASIC interface). Ending the writer and starting it again will put it back to its default.

If you see them going to the wrong queue, my first guess would be the scope of the override. As we started mixing in ILE, we had to change a lot of overrides to *JOB scope.
--
Sean Porterfield
________________________________________
From: Graves, Chuck
Sent: Thursday, October 24, 2013 13:13

After 20+ years I thought I understood this, but...

I suddenly have printed reports going all over the place and NOT to where they should be going. Something has changed and I fear that chasing it with a shotgun has complicated matters

Is there a chart or something that explains the hierarchy of *JOBD, *USRPRF, outq parameter on external printer files etc. etc. as to where something prints? I'm doing OVRPRTF and CHGJOB commands in CL, which are NOT directing reports to where I want them to go.

I have many if not most *USRPRF which are defined as *SYSVAL on the PRTDEV parameter, others with *WORKSTN, and mixtures of *WORKSTN & *DEV on the OUTQ parameter.

And where does the OUTQ parameter on a device description come into all of this..

This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact