Re: 1 remote outq...for users across the usa?

If you can assign static IP addresses to the remote users, you _might_
be able to write a Telnet exit program to trap the IP address and assign
a device name.  I know you can do that with display devices, not sure
about printers.

Or, if you can use iSeries Access you can just assign a printer name and
direct their printouts to that device.  I would still have a Telnet exit
program in place to ensure that only validated IP addresses are allowed
to connect.

Tom

On Fri, 2003-11-14 at 05:57, Rick Rayburn wrote:
> Mission: to have multiple remote users from each of their homes...working on 
> their own pC's...take a menu option that prints a report...to their home 
> printer.
> 
> Access to our 400 is currently through the internet with standard java - 
> tcp/ip entrance.
> 
> There IS a virtual printer function within the software but it assigns an 
> outq name dynamically and none of these users are going to be able to 
> execute change job commands...nor do we want them to have to. There is no 
> way, I believe, to extract the name of the virtual device/outq that each job 
> creates so that wouldn't work. In addition, the least amount of windows that 
> open up remotely on each PC, the less questions and phone calls will be made 
> to our customer service ot IT departments.
> 
> Best scenario would be to establish a "remote" outq of some sort...hopefully 
> attached to the printer file of the report that is printed...and when 
> spooled, would automatically print on each persons home printer...is any of 
> this feasable?
> 
> Thanks much.
> 
> Rick Rayburn
> 
> _________________________________________________________________
> MSN Messenger with backgrounds, emoticons and more. 
> http://www.msnmessenger-download.com/tracking/cdp_customize
> 
> _______________________________________________
> 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.
>