Known Problems

The following is a list of problems which are known but which have not been resolved permanently at the time of writing of this manual.  This document will be updated as these issues are resolved, or as new problems are discovered.  In the former case, resolved problems will be moved to the Resolved Problems section of this manual.
 
Number
Symptom
Root Cause
Status
Resolution/Workaround
1 Any SES driver may create intermittent file access problems with applications in Virtual DOS Machines (VDMs) which access shared files using file locking to serialize access.  This has been seen with one particular WINOS2 application called TeleCenter System or TCS.  This is an application created with FoxPro and the problem only manifests itself when the same application on multiple machines tries to access the same file simultaneously.  The problem appears as a file locking or file access problem. In this case, the application may receive unexpected results. This problem is not specifically a KTRACE problem, but will occur with even a "NULL" SES driver.  In other words, the precence of ANY SES driver is sufficient to cause this problem.  Further research to isolate the specific tracepoint and/or specific fixpak is continuing.  The problem has been seen at Warp v4 with Fixpak 9 applied. Problem is open awaiting feedback from IBM on possible SES defect. There is currently no known workaround for this issue.  KTRACE should be disabled by removing KTRACE.SYS from CONFIG.SYS and rebooting.


© 2001 Golden Code Development Corporation.  ALL RIGHTS RESERVED