Re: Duplicate Queues

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Not to mention there are other applications out there that also only
deal with *DEVD's and not *OUTQs.

Charles

On Fri, Jan 29, 2010 at 12:43 PM,  <rob@xxxxxxxxx> wrote:
> 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
> --
> 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 10:26 AM
> Subject:        RE: Duplicate Queues
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
>
> Just delete the MONTHEND in QUSRSYS created when you created the
> MONTHEND device description. The only thing that really cares about the
> relationship between the outq and the device is the print writer. If you
> never start the writer, there's no issue. Writers can be started in
> QSTRUP (autostart) but needn't be.
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Burns, Bryan
> Sent: Friday, January 29, 2010 8:30 AM
> To: MIDRANGE-L@xxxxxxxxxxxx
> Subject: Duplicate Queues
>
> We've had an outqueue called QGPL/MONTHEND for many years and when I
> recently created a dummy printer called MONTHEND, the system created
> another MONTHEND queue in QUSRSYS.  Now, our month-end job stream is
> sending reports to both queues as a result of printer overrides for
> printer MONTHEND.
>
> Can I just blow away the QUSRSYS/MONTHEND queue?  And can anyone offer
> guidelines for the creation of outqueues with respect to libraries?
>
> Thanks in advance.
>
> Bryan Burns
> ECHO Outdoor Power Equipment
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
> moment to review the archives at http://archive.midrange.com/midrange-l.
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.