To enable client communication with a host, you must create at least one InfoConnect path.
You can create a single connection path for each host connection that you want to establish between the clients and the host, or you can create a pooled connection path and specify multiple terminal IDs for that path.
Each INT1 path includes the following information:
The network address (terminal ID) for the PC
The type of terminal or device that the PC will emulate when a session is established (such as a UTS60 terminal)
Any initial transaction associated with the host application you want to run, if it is not already included in the environment (for example, to run MAPPER, you transmit the ^ symbol)
Which environment to use
Whether to connect to the host automatically
To find the Path tab in Connection Manager
Run the Connection Manager.
From the path tree, click an INT1 path.
Click the Path tab.
To find the Path tab in Database Editor
Run the Database Editor.
From the Connection Type list box, click INT1.
Click the Path tab.
From the Paths And Their Descriptions list box, click the name of the path that you want to modify.
Options |
Description |
---|---|
Terminal ID |
Type the terminal identifier (typically up to 8 alphanumeric characters) to use for the communication session associated with this path. Each Terminal ID should be unique within the entire network. The Terminal ID is also known as a TID or PID. If you're using Connection Manager and data appears in this text box, the path is a single connection path. This text box is dimmed if data appears in the Pooled Terminal IDs list box. |
Pooled Terminal IDs |
In the text box, type a terminal identifier (typically up to 8 alphanumeric characters) for a communication session that uses this path. Each Terminal ID should be unique within the entire network. The Terminal ID is also known as a TID or PID. When you click Add, the Terminal ID is added to the list box. You can also remove a Terminal ID from this list box by clicking the desired Terminal ID from the list box and clicking Delete. If data appears in this list box, the path is a pooled connection path. |
Device Type |
Click the type of terminal or device that the PC will emulate when a session with the host is established. To use this path with :
NOTE:Clicking TERMINAL is the same as clicking UTS40. Clicking MAPPER is the same as clicking UTS40, and in addition the initial transaction ^ is sent automatically. When you click SERVER, no message boxes appear. |
Initial Transaction |
Type the word or phrase (up to 15 characters) that the PC should send to the host when a session with the host is first established. This parameter is optional, and is primarily used in TIP mode. For example, you might type ^ to run MAPPER. You can also use this parameter to transmit passwords. If an Initial Transaction is already associated with the specified Environment, the PC transmits that initial transaction unless you change it here. If you do not specify an environment, the PC transmits the Initial Transaction associated with the DEFAULT environment, unless you change it here. |
Channel |
Click the channel to use for this path. The channel determines certain configuration settings that apply to all paths that use this channel (such as the string to use to establish and end host connections). However, all channels contain the same list of environments. |
Environment |
Click the default environment to use with this path. If you created an environment named DEFAULT, you can type an environment name here that is not on the list of configured environments (up to 12 characters), or you can leave this text box blank. If you type an environment name that is not on the list of configured environments, INT1 uses that name as the host application name and uses the connection associated with the DEFAULT environment when you connect to the host. If you do not type an environment name, INT1 uses both the application name and connection associated with the DEFAULT environment when you connect to the host. |
Auto-Connect |
Select this option to automatically establish communication with the host when a terminal emulation or file transfer session that uses this path is first opened. If you clear this option, you must press the transmit key or issue a $$OPEN command to establish a session with the host application. |
Path Options |
Select or clear the desired options:
|
Traced |
Select this option to enable the creation of a log file containing diagnostic information about the data flow in the session that uses this path. (Selecting this option does not create the log file. To do that, you must initiate the trace using the InfoConnect Manager. Selecting this option simply lets you control which paths are traced and which are not.) If you clear this option, diagnostic information about this path will not be gathered. |
Hidden |
Select this option to mark the path as hidden (it does not appear in the InfoConnect Manager application window unless you’re logged in as an administrator). If you clear this option, this path appears in the InfoConnect Manager application window. |
System |
Select this option to mark the path for internal use by other transports (it does not appear in the InfoConnect Manager application window unless you’re logged in as an administrator). If you clear this option, this path can be used by accessories and will appear in the InfoConnect Manager application window. |
To specify the terminal ID for a single connection path
Go to the Path tab.
Do one of the following:
If you’re using |
Do this |
---|---|
Connection Manager |
If any Terminal IDs appear in the Pooled Terminal IDs text box, delete all of them by clicking each one and then clicking Delete. For more information on pooled connection paths, click Related Topics below. In the Terminal ID text box, type a unique terminal identifier (typically up to 8 alphanumeric characters) to be used for the communication session associated with this path. |
Database Editor |
In the Terminal ID text box, type a unique terminal identifier (typically up to 8 alphanumeric characters) to be used for the communication session associated with this path. |
Each Terminal ID should be unique within the entire network. The Terminal ID is also known as a TID or PID.
Save.
To add a terminal ID to a pooled connection path
Go to the Path tab.
In the Pooled Terminal IDs text box, type a terminal identifier (typically up to 8 alphanumeric characters).
Each Terminal ID should be unique within the entire network. The Terminal ID is also known as a TID or PID.
Click Add.
Save.
To delete a terminal ID from a pooled connection path
Go to the Path tab.
From the Pooled Terminal IDs list box, click the terminal ID that you want to delete.
Click Delete.
Save.
To specify the device type
Go to the Path tab.
From the Device Type list box, click the type of terminal or device that the PC will emulate when a session with the host is established.
To use this path with this |
Click this |
---|---|
Designer Workbench |
DW |
UniMail |
OFIS |
A printer (INT1 automatically prints each buffer it receives from the host) |
PRINTER |
ATB Printer Access |
ATBHost |
Badge codes |
UTS70 |
MAPPER (UTS40 only) |
MAPPER |
A Windows server (as a Windows service) |
SERVER |
Clicking TERMINAL is the same as clicking UTS40. Clicking MAPPER is the same as clicking UTS40, and in addition the initial transaction ^ is sent automatically. When you click SERVICE, no message boxes appear.
Save.
To specify an initial transaction in an INT1 path
Go to the Path tab.
In the Initial Transaction text box, type the word or phrase (up to 15 characters) that the PC should send to the host when a session with the host is first established.
This parameter is optional, and is primarily used in TIP mode. For example, you might type ^ to run MAPPER. You can also use this parameter to transmit passwords.
If an Initial Transaction is already associated with the specified Environment, the PC transmits that initial transaction unless you change it here.
Save.
To enable or disable automatic host connections
Go to the Path tab.
Do one of the following:
To do this |
Do this |
---|---|
Automatically establish communication with the host when a terminal emulation session that uses this path is first opened |
Select Auto-Connect. |
Require that you press the transmit key or issue a $$OPEN command to establish a session with the host application |
Clear Auto-Connect. |
Save.
To save
Do one of the following:
To do this |
Do this |
---|---|
Save in Connection Manager |
From the Path menu, click Save. |
Save in Database Editor |
From the Record menu, click Save Record. |
To delete
To do this |
Do this |
---|---|
Delete in Connection Manager |
From the Path menu, click Delete. |
Delete in Database Editor |
From the Record menu, click Delete Record. |