Path Configuration
An InfoConnect path is a named collection of configuration settings that allows you to connect to a host. Paths are required for connections to ALC, T27 and UTS terminal sessions. From the Workspace, use the Manage Path dialog box to view and/edit paths that have already been configured on your system.
Path configuration information is stored in the InfoConnect database (ic32.cfg), which contains connection settings information for ALC, T27, and UTS terminal sessions. The database contains information about all the InfoConnect packages, path templates and libraries that have been installed, as well the paths that have been created. The InfoConnect packages, path templates and libraries are included based on which product features (emulations and transports) are installed.
You can use any of these tools to update the database.
You can use the Path Wizard to configure new paths for your session documents. The wizard takes you through configuration steps in the correct order to ensure that you specify settings in the correct order. The Wizard is accessible from the InfoConnect Workspace and from the Database Editor.
The Database Editor enables you to view, create, and modify paths. You can start the Database Editor from the InfoConnect Workspace or from the Windows Start menu.
The InfoConnect Manager is an administrative tool that you can use to create and configure paths, as well as to perform additional administrative functions. Start the InfoConnect Manager from the Windows Start menu.
Configuring a path requires that you identify an appropriate path template, the library channels associated with the path template, and path configuration data required by those libraries. Library channels (also referred to as transports) are typically installed with the product by the administrator.
Each InfoConnect library installs several path templates that are relevant to that library. These path templates are available both from the InfoConnect Workspace and from the InfoConnect Manager any time you create a new path.
Terminal IDs
If the path contains configuration data about the PC (such as a terminal ID, station ID, or other similar identifier), you must create a path for each terminal session that you plan to open with a host or host application. For example, to open three terminal emulation sessions simultaneously, you would need three paths. INT1, TCP-A, and HLCNTS paths fall into this category. The benefit of assigning terminal IDs to PCs is that you can monitor compliance.
Paths that do not specify a terminal ID or station ID are reusable. In other words, you can use the same path for several sessions connecting simultaneously. TELNET paths fall into this category.