Thin Client technology may make some functions expensive in terms of system performance. Adjustments have been to minimize the amount of message traffic between the client and the server. For example, if a program resizes a window to be larger than the available screen space, the operation succeeds, because checking for failure is an expensive operation.
Frequent message traffic as a result of communications between screen controls on the display host and an application on the server can negatively affect thin client performance. To identify operations that may be causing performance issues for the thin client, you can establish a screen trace to monitor network message traffic on a slow screen. You can start with a trace of a frequently used screen if it is not clear which screen is causing your performance issue.
One way to improve system performance is to recompile your programs to the Version 5.2 or later object format. In older object files that use MODIFY to set control properties frequently, the thin client must return status to the runtime after each MODIFY statement that sets a property value. When you recompile, thin client sends status back to your program only if the program uses that status value.