Ted MacNEIL wrote:
I obviously can't comment on traces I haven't seen. I can say that TCP
provides guaranteed delivery ... if you (and your software) are willing to cope
with some very ugly timings.
We have no guaranteed delivery! Period!
And, the only change was SNA to TCP/IP.
If TCP/IP is so robust, why has it NEVER happened in 7 years under SNA (how
long we've had the TN3270 client we use), and it always happens under TCP/IP.
I don't understand that statement. If you've been using Tn3270 for 7 years you've
been using TCP/IP. >By definition, Tn3270 is 3270 over TCP/IP.
Not being a network person, I may be tripping over terminology.
It's been the same desktop client for 7 years.
First, in my VERY unhumble opinion, anybody using screen scraping gets what he or she deserves. (BOOM!) That was as true under pure SNA as
under TCP/IP.
All well and good!
It doesn't fly with the business or my mangement.
If I could get away with that, we would be TCP/IP on the mainframe, tomorrow.
And, we would have a whole lot of scrap 3745's and 3174's.
(If you went for 7 years without screen reformatting you lived in a very static
world, indeed.
Never said that we did.
We have people who re-do the MACROS when the screens change.
(Just did it for Germany)
That sounds like a problem with the Tn3270 client, or some kind of
incompatability between the Tn3270 client and server, or some such.
I can reproduce the problem manually (with 5 minutes of effort).
It has to do with the lack of think time.
Just pound a PFKey until the host barfs.
It happens with:
RUMBA
ATTACHMATE
Hummingbird,
and at least three different web-clients:
2 in JAVA
and on in ACTIVEx.
I could imagine this is a problem with the PC OS (presumably Windows).
Did you try to :
change OS on PC,
change OS on host (yes, there are errors in z/OS!)
change *whole* network connectivity, i.e. connect PC directly to the
subnetwork, where OSA is connected, change networking cards, drivers,
switches, firewalls, routers, rules on those devices, etc.
Next question:
"What was the result"?
Answer:
"No matter what client I used, if I typed 'too fast', my session got forcibly
disconnected".
This indicates that script has nothing to do with the problem. The
reason is rather speed of 'typing'. It was *never* an issue in
environments I worked. Including some scripting on PC, even huge "batch
script, which issued millions of CICS transaction using 3270 emulator.
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
