|
|
To use ID management for your design-time sessions, before you can establish a host connection and create tasks, you must first configure your address pools and assign IDs to those pools in MCS. To do this, in the MCS left pane under Services, click ID Management. Under ID Management, click Configure IDs. For more information, click Help in the ID Management tree.
To ensure that IDs are always available for the design-time sessions, create separate address pools for your design-time and run-time sessions.
Services Builder for UTS/T27 does not support ID sets or host name files. In addition, the lease and inactivity timeouts must be set to 0.
Host IP Address Or Domain Name: Type the IP address or domain name of the ClearPath NX, ClearPath LX, or A Series host.
Terminal Type: Click the terminal emulation type to use.
If you click Auto Select, a connection with the host is established using the first terminal emulation type that works. (Each possible terminal emulation type is tried sequentially until a successful connection is established.)
Selecting Auto Select is appropriate in most cases. However, some hosts require that the terminal type be specified. If your host requires this, click the appropriate terminal emulation type.
Use ID Management: Select this option to obtain a terminal ID from ID management.
If you clear this option, you must specify a station ID.
Station ID: Type the station identifier (up to 16 characters) to use with this configuration. You can specify a station ID only if Use ID Management is cleared. Each station ID should be unique within the entire network.
ID Management Pool Name: If you selected Use ID Management, type the name of the address pool from which to obtain an ID.
If you cleared Use ID Management, any entry in this box is ignored.
MCS Address (ID Management): If you selected Use ID Management, type the IP address or domain name of the server where MCS is installed.
If you cleared Use ID Management, any entry in this box is ignored.
Screen Recognition Wait Timeout (In Milliseconds): Type the maximum number of milliseconds (1–2147483647) that the session should wait for a new screen from the host before notifying the screen recognition engine that a new screen has been received. (If a new screen is received in less than this amount of time, the screen recognition engine is notified immediately.) The default value is 1000 milliseconds (one second).
 |
When you are running against an application containing non-forms mode screens, take care choosing the optimum value for the recognition wait timeout. The value you choose should represent the shortest elapsed time before any complete screen (forms or non-forms) is received from the host. Selecting a value that is too large may cause excessive delays in traversing a non-forms mode screen. |
If you experience problems with screen recognition (such as tasks not working properly), try increasing this value.
 |
|
 |
Creating or Editing a T27 Configuration |
 |
Task Builder for Screens Help Links |
 |