Engine connection does not work when connecting to the z/OS connector (versions 8.3.x and 8.5.x)

If one of the following errors occurs when running the test connection, follow the steps described in the cause and solution section:
  1. AWSUI0766E Test connection to myengine: failed. AWSUI0833E The operation did not complete. There was a communication failure. The internal message is: AWSJZC093E The requested engine zserver is not defined.
  2. AWSUI0766E Test connection to myengine : failed. AWSUI0833E The operation did not complete. There was a communication failure. The internal message is: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:ZOS_CONNECTOR_HOSTNAME:31127".
  3. AWSUI0766E Test connection to myengine : failed. AWSUI0833E The operation did complete. There was a communication failure. The internal message is: EQQPH26E TME user ID missing in TME user to RACF userid mapping table: myuser@hostname1.test.com

Cause and solution:

The possible causes for the case above are:
  1. The name of the server startup job on host side must be defined on the z/OS® connector before you perform the test connection from the TDWC.
  2. The WebSphere Bootstrap port is incorrect. Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.
  3. The RACF® user ID has not been defined in the mapping table on host side.
You can solve the problem as follows:
Environment description example
The environment is composed of a z/OS connector installed on the hostname1.test.com, a TDWC installed on either the same or another system, and a z/OS engine installed on the hostname2.test.com(port 445).
Steps on the z/OS connector side
Define a connection from the z/OS connector to the host side by running the following script located in the directory <ZCONN_INST_DIR>/wastools and then restart WebSphere®: 
> createZosEngine -name zserver -hostName hostname2.test.com/portNumber 445
> stopWas
> startWas
where zserver is a logical name and can be changed to any other name.

Check the Bootstrap port by running the script showHostProperties.bat (sh) located in the directory <ZCONN_INST_DIR>/wastools.

Steps on the TDWC side
On the TDWC web interface, define an engine connection from TDWC to the z/OS connector, as follows:
Engine name
Choose any name.
Engine Type
z/OS.
Host Name
Either hostname1.test.com or localhost depending on if TDWC is installed on the same host of Z/CONN or not.
Port Number
The z/OS connector Bootstrap port.
Remote Server Name
zserver (or the name you used in step 2 - createZosEngine).
User ID / Password
For example, the credentials you specified when installing z/OS Connector (that is, the user that owns the z/OS Connector instance). The user can be any user that is authenticated by the User Registry configured on the embedded WebSphere installed with the products.
Note: Bootstrap Port Number in version 8.5.x depends on which product is installed first. If TDWC is installed first, the Bootstrap port is 22809 and subsequent products installed on top of TDWC inherit that. If z/OS Connector is installed first, the Bootstrap port is 31217. If the z/OS connector version is 8.3 FPx, the default Bootstrap port is 31127.
Steps on the z/OS side

Make sure that user myuser@hostname1.test.com is defined in the RACF user ID mapping table on host side (USERMAP parameter in the SERVOPTS initialization statement).