OK, I thought you meant an active device and a printer, and I was afraid
of collisions if both send print jobs at the same time. I'll give the
dummy device a try.
I'm not sure why remote outq's are the least preferred method. In my
experience they're much more resilient and nowhere near as "high
maintenance" as devices. I only use devices where I need page# control, or
with printers that don't support LPR.
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Tuesday, January 26, 2016 3:27 PM
To: Java Programming on and around the IBM i <java400-l@xxxxxxxxxxxx>
Subject: Re: Java print to remote outq?
Normally, when you create a printer DEVD, the system creates an OUTQ of
the same name.
If the OUTQ already exists, (IIRC) you'll get a warning message.
See the section, "*Configuring a Dummy Device Description to Use with a
Remote Output Queue"*
Note however, that a remote outq is the least prefered method of printing..
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.