RE: two qprint outq's

Are you saying that you can't delete QUSRSYS/QPRINT because now you need it,
or because you are unable to delete it?  If you want to get rid of
QUSRSYS/QPRINT you can move all it's spool files from QUSRSYS/QPRINT to
QGPL/QPRINT then delete it.

How does QPRINT get started on your system?  Depending on how you start your
writers the QPRINT writer may get started to the QUSRSYS output queue the
next time you end it.  If you do a:

STRPRTWTR QPRINT
STRPRTWTR DEV(QPRINT)
STRPRTWTR DEV(QPRINT) OUTQ(*DEV)
 or
STRPRTWTR DEV(QPRINT) OUTQ(QPRINT)

...I believe you'll end up with the QPRINT writer started to the
QUSRSYS/QPRINT output queue, if you have a standard system and user library
list as Jim Franz outlined.  You might be even more confused tomorrow.

It seems to me that getting rid of the QUSRSYS/QPRINT queue is your best
bet.  QPRINT is a legacy.  I don't use QPRINT or much of anything from QGPL
on my systems.  Since yours is alread in use dismantling that might be too
much trouble.

-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.com>


-----Original Message-----
From: midrange [mailto:midrange.mail@sfmco.com]
Sent: Tuesday, October 16, 2001 12:30 PM
To: midrange-l@midrange.com
Subject: two qprint outq's


This might be a dumb question, but....

Somehow or another our system has two QPRINT outq's.  One in QGPL and one in
QUSRSYS.  Now for some reason all spoolfiles sent to QPRINT go to the one in
the QUSRSYS lib.  Our writer is started on the one in QGPL.  We cannot
delete the QPRINT outq in QUSRSYS.  The problem did not start occuring until
today.  Anyone have a suggestion on how to fix?


_______________________________________________
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.