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
+---