Screen Handling
The Screen Handling tab allows you to determine how a blank screen is handled at connection startup and how screen settling is handled. These settings only apply if your connection is used as the default connection.
When the connect application event processes the obtain default connection action, ZIETrans attempts to open a connection to the host. If this connection attempt is not completed successfully, the application will end with an error page. If the connection attempt does complete successfully, the host screen is allowed to settle according to the screen timers specified on this page. These timers are also used to settle the host screen at the completion of a custom screen recognition event, the blank screen application event (if configured), and the unmatched screen event. For a detailed description of screen-settling algorithms and settings, refer to ZIETrans screen-settling reference.
- Wait until connect timeout before termination with an error
- This option causes ZIETrans to terminate the application with an error page if the host screen remains blank after successfully connecting to the host.
- Show blank screen
- This option causes ZIETrans to proceed with screen recognition
processing even if the host screen remains blank
after successfully connecting to the host.
If you wish to ensure that a blank screen is not shown to your users, you may specify a screen recognition event in the Event Priority list for processing a blank screen, or you may add actions to the Blank screen Application Event to handle a blank screen. By default, the Unmatched screen application event will present the user with the blank host screen. For more information about screen recognition events, refer to Screen event priority. For more information about application events, refer to Application events.
- Send the host key
- This option will send a host function key to the host if the connection remains blank after successfully connecting to the host. This key will be sent once, the screen will be allowed to settle, and then ZIETrans will proceed with screen recognition processing. You can select which key to send from the drop-down list. This option is useful if your host always draws a blank initial screen, and users must submit a particular function key (SysReq, for example) before the host will present a new screen.
- Minimum time to wait for initial host screen:
- The default is 2000 milliseconds. This is the minimum amount of time that the application waits for the arrival of initial screen updates after the host connection becomes ready. Increase this amount if the host is slow to send the first screen, even if the connection has been in the ready state for some time.
- Maximum time to wait for the screen to settle:
- The default is 1200 milliseconds. This is the maximum amount that the application waits for the arrival of screen updates after the initial screen update. Increase this value if the host is slow to send the contents and you receive frequent partial screens.
- Maximum time to wait for screen to settle (session using asynchronous update):
- This value is only used if your application
is using the asynchronous update applet (for Web applications). For
more information see Using the server push (applet) method.
The initial default value is 400 milliseconds. You should increase this amount if the host is slow to send the screen and you receive frequent partial screens. This value can also be lower than the Maximum time to wait for the screen to settle if the browser specific settings in the com.ibm.common.AppletSettings class in the application.hap file are set to refresh.