There are a variety of reasons why HCM might fail to setup a TCP/IP connection with the host running
under z/OS.
Possible causes can be:
- TCP/IP is not up and running.
- The HCM user ID is not authenticated for use by UNIX System Services or does not have a home directory.
- A DD statement for SYSTCPD is not available.
- The HCM agent job is not started as a lack of initiators.
- There are problem with the names server.
The following suggestions may help to pinpoint the cause of the
problem:
- Issue a ping command to check whether you
have a TCP/IP connection from your workstation to the host.
- Observe the console output for CBDGnnnI messages when you start
the HCM dispatcher.
- Try to log in with HCM using a wrong user ID or password: You
get an EEQX401I or EEQX402I message. In addition, you should see the
CBDG985I message on the console.
- When using a correct user ID and password, check on the console,
whether an HCM Agent job has been started, check for CBDGnnnI messages.
If the HCM agent job has terminated, check its job output for possible
reasons, check whether there are any EDCnnnI messages.