RE: Order Entry GUI - Timing out

Rick/Wade, are these messages you are getting strictly "time outs" or  have you also received "connection reset by peer".

We have been dealing with this issue for about 5 months but our problems mostly centers around the "connection reset by peer"

messages. We have done substantial work on our network, we have put  2 10/100 auto-sensing switches  and moved our GUI users onto these switches. We have replaced workstations from 166/64meg memory to 400/128meg of memory.  This problem only exist at Our Inman South Carolina  location, which happens to have the most GUI users. Our other locations have at some point experienced this problem but never to the extreme of our Inman location.. We are unable to refresh or enter orders without difficulties. We are currently using  dialup connections to allow us to enter orders. By the way green screen on these same workstations is  working great. We have played with the "time out" setting from blank to 999, and are also clearing the order files as suggested. We have and continue to have AT&T, Nortel, and SSA working on first the problem and then the solution.

Any additional information or suggestion which may help us resolve this problem  will be greatly appreciated.

Thank You.
Willie Gonzalez
PDHPC  Inman,S.C.

-----Original Message-----
From:   Ata510@aol.com [SMTP:Ata510@aol.com]
Sent:   Tuesday, November 09, 1999 10:53 PM
To:     BPCS-L@midrange.com
Subject:        Re: Order Entry GUI - Timing out

Many times "time out" problems are caused by work files which are full in
Order Entry. Table scans over those files exceed the time out value. Logicals
are not delivered in abundance over these work files, as there are not meant
to be many records in them. But when programs end abnormally in Order Entry,
records can be left in the files, over time causing a build up of records. If
you ever have a bug where Order Entry looped or some other thing regularly
caused crashes during Order Entry, chances are these files have lots of
useless records left in them. 

Check out the ZEF, ECHW, ECLW and PDW files for any records. In an ideal
world there would be no records in these files when users are out of BPCS and
batch processing is completed. Clear them when no job is using BPCS (CLRPFM).
If the files are very large, chances are they are contributing to the problem
you are having.

If that doesn't have any effect, also try running DBMON on the server job
(SSATCP) to see if there are logicals being built over non-work files while
running Order Entry. Also check network round-trip times with large packets
of data if you are using TCP/IP and make sure your network performance is OK.

If the time-out value in the workstation settings is left blank, then there
is effectively no time out (indefinite). If you are still having 'time out'
problems, then the cause is not related to that parameter in the workstation
settings.




+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---