Configuring Hosts for HCON

3270 Host Connection Program 2.1 and 1.3.3 for AIX: Guide and Reference

Configuring Hosts for HCON

Before users on the system can use the Host Connection Program (HCON) to communicate with a System/370 mainframe host, the host must meet certain configuration requirements. Different systems have differing requirements, depending on the hardware and operating system installed. However, the Virtual Telecommunications Access Method (VTAM) configuration necessary for HCON is the same for all system types. To set up HCON-related VTAM Network Control Program (VTAM/NCP) information on the mainframe host, you need to:

See "VTAM/NCP Node Definition Examples" for descriptions of node tables for specific connection types.

Host Requirements

VTAM release 3.2 or later is recommended when using HCON. Because the host definitions needed to support different links and protocols vary, consult the VTAM publications for details of VTAM and NCP generation descriptions.

After you have configured the host for use with HCON, provide each HCON user with an appropriate logon ID on the host computer. Before writing programs with the HCON Application Programming Interface (API) to communicate with a host system, you must install the host API on that system.

The host definitions for HCON can be classified into these categories:

Channel attachment:
- DFT using a 3174/3274 or equivalent
Remote attachment:
- DFT using a 3174/3274 or equivalent
Standalone:
- Using a Node T2.1 device
- Using SDLC (switched or leased line)
- Using a Token-Ring network
- Using an X.25 wide area network.

These macros are used in VTAM and NCP connection definitions for connecting to local systems:

GROUP	Defines a group of communication lines attached to the NCP or VTAM. All of the lines in each physical line group have common physical attributes. Many parameters from the LINE, PU and LU macros may be specified in the GROUP macro for ease of coding and readability. This grouping eliminates the need to include common parameters in each subsequent macro and allows overrides when appropriate.
LINE	Supplies specific characteristics of the communication link. Proper values should be determined by checking with the common carrier and modem supplier.
PU	Defines the characteristics of the node's physical unit.
LU	Defines the characteristics of a logical unit (LU). A physical unit type 2.1 node, such as HCON, can support multiple LUs. An LU provides the interface to an SNA network for terminals and printer support to a host application. An LU's session is established between the two LUs by the SNA BIND command. The BIND parameters determine the protocol for the session. The BIND image is an entry in a logon mode (LOGMODE) table, which is created by the MODETAB, MODEENT, and MODEEND macros. The LOGMODE parameters define session parameters that make up the BIND image.

HCON supports the following host control units. Each control unit has different configuration requirements.

3274/3174 Control Unit

Following are the 3274 controller customization requirements (for 3274 Configuration Support D) for a local system running the HCON 3278/79 emulator, the 3270 file transfer program, or the application programming interface (API):

Customize the 3274 to include Distributed Function Terminal (DFT) support.
Customize the controller for Extended Data Stream processing.
If a local system is to support multiple sessions, customize the controller for Multiple Interactive Screens.

5088/6098 Graphics Control Unit

The 5088 controller address is normally set up during the installation process. Refer to the 5088 Models 1, 2, and 1R Graphics Controller Maintenance Information manual for details.

The setup parameter of the HIA adapter on the local system and the 5088 control unit must match. Use SMIT 5085 from the command line to view or change the HIA setup parameters. For host channel and terminal type definition, refer to the System Planning and Installation Guide for 6098 Graphics System.

[ Previous | Next | Contents | Search ]