|
On 24/08/2004, at 5:18 AM, rob@xxxxxxxxx wrote:
No thanks, I've had enough of the SDLC errors and obscure error codes for
SNA that I used to get with STRPASTHR. Codes that IBM seemed to hold near
and dear to their hearts and hide from the rest of us. Codes that meant
doing odd things like varying off and deleting device descriptions and
letting them recreate again when a connection attempt was made. And if
the planets were in just the right alignment - maybe everything would work
that time. I'll take TCP/IP instead.
Oh, sure, SNA did have the 'fire and forget' mentality that you could send
something off, and if the remote system was down, it would wait, and retry
when that system reconnected. That was nice. But finding out why
something stayed stuck in WRKDSTQ and the like could be a shuddering
experience.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists
http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.