|
John: On Wed, 05 September 2001, "John Taylor" wrote: > I don't think a standard comm trace on the ethernet line would be > effective --too much data coming through-- but TRCTCPAPP may be an option. I believe a comm trace will be much more help than TRCTCPAPP simply because I don't believe the info you need to see will ever reach the TCP app trace; it's hard to believe this gets up to the TCP application level (though I'm stretching my knowledge when I start in that area). Now, it's true you're going to get much more than you need in a comm trace. Fortunately, you'll have multiple tries. If you can't catch it the first time, then keep the trace running and try again. But beyond that, how about some info on your physical setup? How many adapters are you interfacing with? And how many TCP/IP interfaces do you have defined? (You mentioned multiple subnets.) How many routes? (I've seen troubles related to these questions.) And I've lost track of your OS/400 release. Tom Liotta -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
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.