RE: Duplicate Queues

I don't see any reason for having a printer device description you're
never going to use. That is, a dummy printer device.

The query doesn't reference a printer, it references a print file. The
printer file names an outq. The outq is attached to the printer device
description by the print writer.

Goes like this:

Program names a print file.
Print file may be overridden.
Print file names an outq.
Outq is attached to a printer device description by a print writer.

The only reason to have a reference to an outq in a printer device
description is autostart. QSTRUP goes through the list of printer device
descriptions looking for ones with autostart. It does a STRPRTWTR for
each of those using the defaults, which is outq(*devd).

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Burns, Bryan
Sent: Friday, January 29, 2010 9:53 AM
To: Midrange Systems Technical Discussion
Subject: RE: Duplicate Queues

Yes, that is correct - dummy device is for queries.

I'm going to go with your suggestion Rob and keep the QUSRSYS/MONTHEND
queue. That said, I just found 13 printer overrides in our MAPICS app
that overrides printer files to QGPL/MONTHEND. Now I've got to go
change those...

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, January 29, 2010 9:40 AM
To: Midrange Systems Technical Discussion
Subject: RE: Duplicate Queues

However, if they created the dummy device to receive printouts from
query, where will the spool files go? Let alone the fact that what you
suggest

can't be done.
crtoutq qgpl/robone
CRTDEVPRT DEVD(ROBONE) DEVCLS(*VRT) TYPE(3812) MODEL(1) ONLINE(*NO)
dltoutq qusrsys/robone
CPF3469 - Operation not allowed for output queue. ...because it is used
to spool output files for device ROBONE.


Rob Berendt