There are a variety of reasons why HCM might fail to setup a TCP/IP connection with the host running under z/VM.
Possible causes can be:
- TCP/IP is not up and running on the host and/or on the workstation.
- The z/VM HCD TCP/IP dispatcher for HCM is not up and running on the host.
- The external security manager (ESM) is not properly configured
on the host.
The following suggestions may help to pinpoint the cause of the problem:
- Issue a ping command to check whether your
host is reachable from your workstation.
- Check the output from the z/VM HCD TCP/IP dispatcher for HCM on the host.
- Try to login with HCM and check for messages from HCM on the workstation
and from the z/VM HCD TCP/IP dispatcher for HCM on the host.
- Use the TCP REPORT ON command in the z/VM HCD TCP/IP dispatcher for HCM on
the host to get information about TCP/IP traffic (refer to Reusable Server Kernel Programmer''s Guide and
Reference for details).
- Use the TCP LIST and TCP
QUERY subtaskid commands in the z/VM HCD TCP/IP dispatcher for HCM on the host to get information
about TCP/IP sessions (refer to Reusable Server
Kernel Programmer's Guide and Reference for details).