Subject: Re: 400 printing over a WAN

My goal is to get an AS/400 , model 9406 sitting in city A to print to 400 
printers sitting in city B.  Today, the printers have twinax interfaces.  The 
400 does have an Ethernet card and an IP stack loaded ( V3R2 code).  The two 
offices in which the 400 and these printers sit will need to have LAN-LAN links 
set up anyways for normal client to server communications.  My Goal here is to 
allow the 400 to talk to these printers across the WAN without the need to do 
something like TDM-ing some bandwidth off the circuit to run a dedicated 400 to 
controller link (not that I have a controller - the current 400 support the 
printers thru a built in WSC).  How can I connect a twinax printer to my LAN in 
such a way that I can get the 400 to see it thru its Ethernet interface?

Subject: Re: 400 printing over a WAN

What problem are you trying to solve?  What are your goals?

To be able to print to these printers from PC's and your mainframe?
IF this is your goal, (IF).  Then there are a couple different ways
around this.  Study 'NetServer'.  This will allow PC's (of the Wintel
variety at least) to select these printers just as if they were any
other Windows printer.
There should be some way, if you're already connecting your mainframe
and their 400, to configure remote printers to share between the mainframe
and the 400.

If the goal is to trash the 400 but keep the printers (I'll avoid the
argument as to why you need a drug test) then there are a couple of
things you can do there.  See if the IBM 5494 control unit, (or compatible
marketed by Perle) will configure to the mainframe.  Or, there are many
protocol converters out there that can convert printers from twinax to
3270 or lan (more versatile).


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