|
I just setup a remote out queue this morning. Here is the command I used to set it up using IP. CRTOUTQ OUTQ(QBARRETT/BEBTEST) RMTSYS(SFO400P4) RMTPRTQ(SFO400P4) AUTOSTRWTR(1) MSGQ(QBARRETT) CNNTYPE(*IP) TRANSFORM(*NO) I created the out queue on both systems just changing the system name. And thanks to your email, I'm on an LPAR 740, I'm going to try to use OptiConnect for another test. >>> Mike.Crump@saint-gobain.com 08/13/02 10:09AM >>> 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 _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.