3.6.3 Configure Advanced Connection Settings Dialog Box (5250)

From this dialog box, you can define advanced TN5250 features.

Advanced 5250

Sign-on Options

Do Not Sign On Automatically

Select if you do not want to log on to the host as soon as you establish a connection. This is the default.

Automatically Sign On Using Windows Credentials

Select to log on to the host using your Windows username and password. This option works in conjunction with IBM Enterprise Identity Mapping (EIM), which must be configured on your host computer.

Automatically Sign On Using Specified User ID and Password

Select to log on to the host using the specified user ID and password.

Connection Action

You can configure a session to run a macro, start an application, open a Web page, send an e-mail message, or perform a variety of other actions before or after it connects to the host.

Run a macro or other action before the initial connection

Select to run the connection action after the session file is opened but before the session initially connects to a host. (This action is performed even if the session is not configured to connect automatically.)

Select Action

Click to select an action to perform or a macro to run before you connect to the host. By default, the Select Action window opens at the screen for selecting a macro. If you prefer to perform a different action when your session connects, you can select other actions from the task pane.

Run a macro or other action after the initial connection

Select to run the connection action when the session initially connects to a host.

Select Action

Click to select an action to perform or a macro to run when you connect to the host.

Run when reconnecting

Select to run the connection action when the session initially connects to a host, and every time it reconnects to the host.


Security Settings

Secure data communications with SOCKS or SSL/TLS.


Keep Alive

Send Keep Alive packets

Select to provide a constant check between your session and the host so that you become aware of connection problems as they occur.

Choose one of the three types of keep-alive packets:



To cause



The TCP/IP stack to keep track of the host connection. This method requires less system resources than Send NOP Packets or Send Timing Mark Packets. However, most TCP/IP stacks send Keep Alive packets infrequently.


Send NOP Packets

InfoConnect to periodically send a No Operation (NOP) command to the host. The host is not required to respond to these commands, but the TCP/IP stack can detect if there was a problem delivering the packet.


Send Timing Mark Packets

InfoConnect to periodically send a Timing Mark Command to the host to determine if the connection is still active. The host should respond to these commands. If InfoConnect does not receive a response or there is an error sending the packet, it shuts down the connection.

Keep Alive timeout in seconds

Select the interval between the keep-alive requests. The range of values is 1 to 9999 seconds; the default value is 600 seconds.

Telnet Location

Telnet location

(Optional) Type up to 41 characters of descriptive text to provide information about your session. For example, you might include your system location, computer name, or IP address.

This features uses the SEND-LOCATION option supported under Telnet connections (RFC779).

InfoConnect does not initiate a WILL SEND command unless you activate theTelnet location option by typing information in this box.



Short name

By default, InfoConnect assigns the first available letter (A if no other sessions are running) and saves that short name value when you save your session document. If you open multiple sessions that have the same HLLAPI short name value, InfoConnect automatically reassigns the HLLAPI short name of each newly opened session using the next available letter.

Select a HLLAPI short name to associate with this session. This value is used by a HLLAPI application to identify a host session. Any single capital letter (A-Z) can be used as a short name.

If your HLLAPI application requires a specific short name value, specify this value, then save your session document. If you run multiple sessions, you must ensure that sessions running at the same time do not require the same HLLAPI short name.

If you want InfoConnect to generate new, arbitrary short name values for each new session, save all session documents with the HLLAPI short name set to A. InfoConnect will always set the HLLAPI short name to A for the first session, and will reset the short name to the next available letter for each subsequent session.

Long name

Enter a HLLAPI long name to associate with this session. A HLLAPI long name identifies the host session for the convenience of the user. It is not used by the HLLAPI application. The long name can be up to eight characters long and can include letters, numbers, and other characters.


If you are migrating from an Extra! or legacy Reflection product, and your application uses the default HLLAPI compatibility settings, simply select Reflection or Extra! from the Compatibility drop-down list. This configures the HLLAPI support in InfoConnect to match the default settings found in those applications.

If your application requires custom HLLAPI compatibility settings, select Custom from the Compatibility drop-down list. Once Custom is selected, you can enter a custom compatibility mask.

NOTE:Because of variations in the implementation of HLLAPI in previous products, when HLLAPI applications from Extra! and from previous versions of Reflection are run against InfoConnect, they may not behave exactly as they did when run against the product for which they were originally written. Even when you have selected the correct compatibility setting, minor differences may be seen in the status or return code reported by a handful of functions.

Custom compatibility mask

The possible numeric values for the custom compatibility mask styles are "bit masks" that contain separate bits of information about InfoConnect's HLLAPI configuration. Each style is equated to a decimal and hexadecimal value. A list of the styles and values is shown in the table below.

To create a compatibility mask, add the decimal or hexadecimal values of each style and enter the sum into the Custom Compatibility Mask field. Values can be entered in either decimal or hexadecimal format; however, when using hexadecimal values, replace the 0x at the front of the value with &H. For example, to use hexadecimal value 0x5380, enter &H5380 in the Custom Compatibility Mask field.

For example, to turn on the Propagate EAB (decimal value = 1), Input Inhibited Position (decimal value = 8), and Don't Wrap at PS End (decimal value = 512), add these three numbers (1 + 8 + 512 = 521) and enter the total into the Compatibility Mask field.

For details, see Custom Compatibility Masks.