Hardware Configuration Manager
Workstation - Host Communication
TCP/IP via AnyNet
25 Feb 1997
This update applies to the User's Guide of IBM Hardware Configuration Manager for MVS, SC33-6469-00, Version 1 Release 1 (first edition, October 1995).
Chapter 1. TCP/IP Communication for HCM via AnyNet
The IBM AnyNet product family enables application programs to communicate without change over different transport networks and across interconnected networks. Originally introduced as the VTAM Multiprotocol Transport Feature (MPTF) in VTAM V3R4.2 for MVS/ESA, it has been renamed to the VTAM AnyNet Feature for V4R2 and is available now on several platforms including OS/390, OS/2 and Windows 3.x.
HCM/HCD communication is implemented as an APPC application. By installing and activating AnyNet on the host (MVS) as well as on the workstation (OS/2 or Windows), you can run HCM over TCP/IP networks.
For the platform operating systems on both sides, HCM/HCD still appears to be an APPC application. Therefore most of the SNA related definitions as described under " Setting up APPC definitions" in the HCM User's Guide are still required. The only exception is the definition of the local SNA major node for the communication controller. This is not needed anymore.
Instead you must enable TCP/IP connectivity between the host and the workstation, and establish an AnyNet link between SNA and TCP/IP:
- Host definitions
The IP network is represented to VTAM in a TCP/IP major node. This is defined via a VBUILD TYPE=TCP.
IPSA7ANY VBUILD TYPE=TCP, C
PORT=397, WELLKNOWN PRT FOR ANYNET C
TCB=50, NUMBER MVS SUBTASKS C
TCPIPJOB=TCPIP TCP/IP JOBNAME
IPSA7GIP GROUP ISTATZZ=ACTIVE GROUPNAME
IPSA7LIP LINE ISTATZZ=ACTIVE LINENAME
IPSA7PIP PU ISTATZZ=ACTIVE
Since the communication between HCM and HCD is always initiated from the workstation, you may let VTAM define the workstation LU dynamically. In this case the DYNLU=YES start option must be specified. Otherwise, you must define the workstation LU as cross-domain resource as shown in the following example:
where X7316C00 is the independent LU name of the workstation, and IPSA7PIP is the name of the PU statement in the TCP/IP major node definition.
- Workstation definitions (OS/2)
It is assumed here that you have AnyNet/2 SNA over TCP/IP installed on your system, for example as part of the "Personal Communications AS/400 and 3270 Version 4.1" product. To use the TCP/IP network when starting HCM the following steps are required:
- Configure CPI communications over AnyNet
In the Communication Manager Configuration Definition panel select
- Definition selection = Additional definitions
- Workstation Connection Type = Anynet
- Feature or Application = CPI Communications
Select AnyNet base parameters in the Communication Manager Profile List panel and set non-native-only as default routing preference in the AnyNet Parameters panel.
Also set non-native-only as partner LU routing preference in the Partner LU panel for the HCD LU.
- Map HCD LU name to IP address
A link is needed to tell AnyNet which IP address to use when the HCM establishes the LU-LU session with the HCD part. This is done by adding an entry into the HOSTS file. The HCD LU name is reformatted by AnyNet into an IP domain name in the form
where the SNASUFFIX is the domain name suffix from the AnyNet Parameters panel.
For example, if HCD has the fully qualified LU name DEIBMIPS.IPSA7APC and the SNASUFFIX is SNA.IBM.COM, AnyNet generates the domain name
You can resolve this domain name either through an entry in the local HOSTS file, eg.
188.8.131.52 IPSA7APC.DEIBMIPS.SNA.IBM.COM HCD
or by defining the name in a domain name server.
- Workstation definitions (Windows 3.1)
**** to be done ****
Back to the HCD / HCM home page