Connection tab

Communications Library

Rocket TE displays the available host connection options. Select the appropriate link for additional configuration information:

Note: Rocket TE defaults to the connection type that was chosen during installation.

Connection Type

Microsoft Host Integration Server: Select to connect to the host system to a Windows server running the Microsoft Host Integration software.
Note: The Microsoft SNA Client or Host Integration Client must be installed on the PC on which Rocket TE is running before the connection can be made.

Refer to Microsoft SNA Server for more information.
TN3270E/TN3270E: Select to connect to the host system via TCP/IP using the TN3270/TN3270E protocol.

Refer to TN3270E Properties for more information.

Use Custom LUA-RUI Compliant Dynamic Link Library

Selects a custom connection type for Rocket TE to use when connecting to the host system. The Dynamic Link Library (DLL) specified must be LUA (Logical Unit Addressing)-RUI (Request Unit Interface) compliant.

Browse: Allows you to enter the path and file name of the Dynamic Link Library DLL
LU Name: Type the LU /Pool Name to use when using the Custom Library Link above.

Properties

Click to configure the highlighted connection.

Options

After selecting the connection type, select from the following options:

Auto-Connect Session: If enabled, Rocket TE auto-connects the session after the communications library has initialized.
Auto-Reconnect if LU is Deactivated by Host: If enabled, Rocket TE auto-connects the session if the LU being used is varied off on the host system while a Rocket TE session is active.
Note: The LU obtained by the reconnect is not the same as with the prior session.
Auto-Close Session on Disconnect: If selected, the Rocket TE application auto-closes after disconnecting from the host system.
Connect Retry: If enabled, Rocket TE tries to connect to the host the number of times selected in the Retry up to list box and use the interval selected in the times, retrying every list box.
Note: The LU obtained by the reconnect might not be the same as with the prior session.