Printer Pass-thru (TCP/IP vs. SNA)

We currently have an environment where we move print from a corporate
AS/400 to ours via a high speed multi-protocol connection.  We use the
process lightly and have always configured the remote OUTQ's as SNA.
However, recently we have had numerous issues with SNA traffic on our
network.  So far the network gods have admitted to no problems but we now
routinely have SNA outages that are in the hours range.  It's not really
mine to solve so I've stayed out of it and this is not the intent of my
question.

Shortly, hourly plant payroll checks will be coming across this connection.
And I can smell the disaster coming.  I have no true vested interest in the
SNA connection.  We used it starting years ago because it was what we used
locally and everyone was comfortable with it.  I've not pushed migration of
certain applications towards TCP/IP since our network supports both
(normally quite well) and the telcom people haven't pushed the issue.
Therefore, I only want to take the task on if it is necessary.

My question is that I'd like to know what issues exist if any between
sending print from AS/400 to AS/400 via TCP/IP vs. SNA?  The print being
transferred from them is plain vanilla (standard SCS).  I'm sure that there
are a few people that have changed their method from SNA to TCP/IP and
would like to get their perspective on performance, functionality,
ownership, attributes, etc.



Michael Crump
Saint-Gobain Containers
1509 S. Macedonia Ave.
Muncie, IN  47302
(765)741-7696
(765)741-7012 f
(800)428-8642

mailto:mike.crump@saint-gobain.com