We have a situation similar to Art's.  Instead of using the same outq, each
remote location is assigned its own outq.  As someone else mentioned, DO
NOT WRKOUTQ on this machine!

When a user dials in, our users start the printer to their outq.  In our
case, we don't automatically start the printer to the Q, although that
would be a logical extension of our procedures.

Because we have no control over which of our multiple lines a user reaches
when they dial in, which controls the terminal and printer devices that
conversation will use, we have a table that matches the line to the printer
device to be used for that line.  When the user starts the printer, the
printer device is automatically filled in; the user just enters the outq
name they wish to use.

--Paul E Musselman

>We had a similar situation where we had multiple customers dialing into us
>through an ASYNC protocol converter (Andrew DataLynx YUK)
>If a customer spooled a report, then hung up the connection before it
>printed, the report was left in the spool file.
>If another customer dialed in, the spool file would still be there and they
>could print it.   The reports showed prices, which of course were different
>for each customer.
>Art Tostaine, Jr.

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].