RE: Job separators with Remote Outq

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Leland, David
>
> The remote outq can be used on the same machine and that's how
> I'm doing it.
> There is no printer associated with it.  You simply assign an IP
> address to
> it and change a few other parameters.

Ugh.

As you can tell, I don't use IP-based printers.  Still, the remote outq
approach seems like an inadequate way to do things.  Wouldn't it make more
sense to create a device description that automatically sends data to an IP
address?  Please, if this is a stupid question, bear with me - I'm
absolutley useless on these things.  But it would seem to me that the
correct implementation of this setup would be to have a normal output queue
and change the device description to dump data to a TCP/IP port.  Then you
could do all kinds of cool things with the device description to define the
printer (including defining a SEPPGM).

The remote outq directly to a TCP/IP address seems like a "quick and dirty"
solution that only handles a very limited set of circumstances.  Or am I
completely nuts here?

Joe