I haven't used Query/400 in a really, really long time. Probably close
to 10 years.
Makes me wonder why it was done this way. It seems to validate to a
device description list. Internally, it must be using the device
description to come up with an outq name that it uses to override its
own print file. Why couldn't they validate to an outq list? The
interface does allow SPOOL(*NO) which would require a device
description, but that could be handled conditionally.
If you say PRTDEV(*PRINT), it uses the OUTQ of your job (the help text
says something entirely misleading). I have DKIMMEL specified as the job
OUTQ and query puts the output there even though there is no DKIMMEL
device description on my system. So if you have your jobd set up right,
there's no need to have a dummy device description. You can also do a
CHGJOB OUTQ(SOMEOUTQ) and the output will go to SOMEOUTQ if the query is
set up with PRTDEV(*PRINT).
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, January 29, 2010 11:44 AM
To: Midrange Systems Technical Discussion
Subject: RE: Duplicate Queues
Dan,
Have you ever used Query/400? So, unless they want to wrap every query
they use with a program they have to specify a device.
Screen is pretty basic:
Printer . . . . . . . . . *PRINT
Form size:
Length . . . . . . . . .
Width . . . . . . . . . 132
Start line . . . . . . . .
End line . . . . . . . . .
Line spacing . . . . . . . 1
Print definition . . . . . N
There is no way to specify output queue unless
- You use wrapper programs
- You use a device associated with that output queue.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Dan Kimmel" <dkimmel@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
Date: 01/29/2010 12:19 PM
Subject: RE: Duplicate Queues
Sent by: midrange-l-bounces@xxxxxxxxxxxx
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
midrange.com
