RE: configuring remote printer queue

[MARK_WELTE@xxxxxxxxxxxxxx]

Phani,

That is very strange. We are using the exact same setup with no problems.
We have dummy user profiles set on sysA that have "live" outqs in their
user profile. One difference between our setup and the one that you
described is that our outqs are actual printers and not remote output
queues. But, I can't see why that would make a difference.

Sorry that I can't be more help,
Mark Welte





PhaniHR <PhaniHR@inf.com> on 10/09/98 04:57:46 AM

Please respond to MIDRANGE-L@midrange.com

To:   "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
cc:    (bcc: MARK WELTE/DMTN)
Subject:  RE: configuring remote printer queue




Hi Mark,

I've tried this. I created a dummy id on sysA with the default queue as the
remote queue. Any spool file created by this id goes to the remote queue
and
gets printed. when I send a spool file from sysB to this id on sysA, the
outq is always qprint and not the default remote queue. is there any way of
making the default queue to the remote queue or is there something that I'm
missing.

Regards,
Phani - AS/400 System Group

> If that is the case, then setup a dummy user profile on system A that has
> the output queue as the remote output queue. Then use SNDNETSPLF to send
> the spool file via SNADS from system B to the dummy user profile on
system
> A. I think this will then send the print to that user's output queue
which
> should actually send it to the printer.




+---
| 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
+---