|
Short Description
|
TEFIND failures
|
|
Entered
|
By:
intek
When: 1998-08-26 21:47:34 Build: 1.03.20d
|
|
Categories
|
Type:
Question
Department: Product
Category:
Troubleshooting
|
Description
|
Shortly after adding 10 additional users to the box (up to 20 concurrent right now), we are starting to get failures in TEFIND commands (one of which I copied below). It is not consistent so to me that rules out the mainframe screens changing or bad code -- sometimes it goes through sometimes not.
The surfer machine is a Compaq with 256M and dual pentium 300's. SS is running as a service with no logging (as suggested from a previous ticket).
I have bumped up the TIMEOUTs from 10000 to 20000, but no luck. Can anything else be added to the command to help out in explaining what's failing? Timeout? Not finding the "magic" word?
The heat is now on full blast here as out system is getting blamed for slower-than-normal sales. *ANY* advice is most welcome.
<TEACTION ENTER "[ENTER]" SKIPSCAN>
<TEFIND VARROOT=FOUND TEXT="TELEPHONE"
STARTROW=16 ENDROW=16 TIMEOUT=20000>
<TEIF FOUND.OFFSET == -1>
<TESET
|
|
|
|
Append
|
By: WindSurfer When: 1998-08-26 22:11:27 New Status:
Pending Customer
|
|
Comment
|
Can you please check CPU utilization on the Screensurfer server during peak periods? It should not be even close to maxed out with only 20 users. However, there could be something that is particular to your system that could be causing an issue. The TEFIND code has a 100 millisecond wait between checks, so it shouldn't be causing CPU racing.
What do the users see in the display when the error occurs? Is "TELEPHONE" on line 16 or not?
20 seconds is a very long time for a host response time, but there could be something else about this particular transaction causing a problem-- is the TN3270 or SNA gateway in good shape?
Will give you a call in the morning.
|
|
|
|
Append
|
By: WindSurfer When: 1998-08-26 22:26:10 New Status:
Pending Customer
|
|
Comment
|
Just noticed one of your questions wasn't answered fully-- when a timeout is included, ONLY when the timeout occurs is the -1 returned, since Screensurfer keeps looking up until the timeout.
|
|
|
|
Append
|
By: intek When: 1998-09-01 15:00:23 New Status:
Pending IE
|
|
Comment
|
Increasing the timeout seems to have little effect on the number of "green screens" our reps are receiving. Do you think it would be beneficial to tweak any of the other settings, for instance Screen.SettleTime or Screen.TimeOut to try and avoid missing the text?
|
|
|
|
Append
|
By: WindSurfer When: 1998-09-01 15:48:41 New Status:
Pending Customer
|
|
Comment
|
Maybe it isn't after the timeout that they are seeing the greenscreen? Is the missing text present on the screen when the error occurs? Have you seen delays in your representitive session during the time of day when these are occurring? Are the reps also maybe just seeing screens that you haven't recognized yet?
The best way for us to provide some answers to you is if you can do a log of a specific session performing typical work. Then, send us the log along with an e-mail which identifies which screen transition(s) experience this problem. The log doesn't need to contain a timeout or a problem, just a representitive 3270 datastream conversation.
|