Re: Spool File to Remote Outq "Stuck"

["Jim Franz" <franz400@xxxxxxxxxxxx>]

> *SPLCTL special authority will do it, but it has global implications
*splctl is like the qsecofr of spool. This will let you look/control any
spool file in the entire system, even if not authorized to the outq! I
prefer to give users a pgm run from menu that adopts authority & can only
control/reset specific printers.
I have found that by using IBM's recommended settings for remote outqs, and
getting the ptfs for lan & remote printing, our users rarely if ever have to
reset (except printing thru a windoze print server, which gets "stuck" and
re-booted more often). I have never had to bring down tcp to fix a print
problem.
The main ibm knowledge base doc for remote outq, which has internal links to
settings and ptfs
is Configuring a Remote Output Queue (RMTOUTQ)

http://www-912.ibm.com/s_dir/slkbase.NSF/1ac66549a21402188625680b0002037e/9f
4b1d4d23c582f1862565c2007d4471?OpenDocument&ExpandSection=4,3&Highlight=0,re
mote,outq,timers#_Section4

and the biggest resaon I've seen for losing connection is timeout values on
HP Jet Direct or HP Network printers. See
http://www-912.ibm.com/s_dir/slkbase.NSF/1ac66549a21402188625680b0002037e/1e
61e34f2505754f862566e20051c3de?OpenDocument&ExpandSection=2&Highlight=0,jet,
direct,timer#_Section2

hth
jim franz
----- Original Message -----
From: "Vernon Hamberg" <vhamberg@attbi.com>
To: <midrange-l@midrange.com>
Sent: Friday, September 13, 2002 10:50 PM
Subject: RE: Spool File to Remote Outq "Stuck"


> John
>
> *SPLCTL special authority will do it, but it has global implications, if
> you want to control spooled output more. Check the Tips and Tools security
> book for more info. I don't remember all the details.
>
> Luck
>
> Vern
>
> At 06:36 AM 9/13/02 -0400, you wrote:
> >Steve Ryan's solution worked like a charm.
> >
> >Now, what authority does a user need to enable him/her to end and start
the
> >writer.  What do I change in the user profile?
>
> _______________________________________________
> 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.
>
>