Troubleshooting on IBM z/OS Container Extensions (zCX)

Investigate and resolve errors on IBM® z/OS® Container Extensions (zCX).

About this task

You can use various techniques to diagnose and fix errors that occur when you run IBM App Connect Enterprise on IBM z/OS Container Extensions (zCX).

Procedure

Environment variables

  • Check the STDOUT and STDERR in the job log for errors that report missing or incorrect environment variables.
    Edit the ENVFILE to address these errors. For more information, see Environment variables in STDENV and BIPENVS.

Space

  • Check the STDOUT and STDERR in the job log for error messages about lack of disk space.
    Customize and run the JCL job BIPXDSP. The job BIPXDSP removes all unused containers, unused networks, and used images (both dangling and unreferenced). For more information, see Customizing the JCL.

BIPXBLD

BIPXBLD fails to unzip or untar the IBM App Connect Enterprise or MQClient packages.

  • Check the STDOUT and STDERR in the job log for error messages that are related to unzipping or untarring the IBM App Connect Enterprise or MQClient packages.

    Do not to use Secure Copy Protocol (SCP) to transfer the package. SCP assumes that files are text, so binary files that are copied between EBCDIC and ASCII operating systems are corrupted during the copying process.

BIPXBLD fails to install the IBM App Connect Enterprise or the MQClient packages.

  • Check the STDOUT and STDERR in the job log for error messages that are related to installing the IBM App Connect Enterprise or MQClient packages.

    Ensure that the tar file is for the Client deb install packages for IBM MQ on Ubuntu on z Systems, and not the Client rpm install packages for IBM MQ on Linux for z Systems.

Docker container issues

  • Submit the JCL job BIPXDBG to obtain more information on the docker container in which the integration server is expected to run.

Console listener issues

The console listener task does not work.

  • Check whether the integration server is running, by submitting the JCL job BIPXDBG, and checking the output.
    • If the integration server is stopped, cancel the console listener task.
    • If the integration is running, submit the JCL job BIPXSTP to stop it, or delete it.

The console listener fails with RC=3584.

  • Check whether the user ID under which the console listener runs has execute access to the supplied scripts specified in the ACE_SCRIPTS_DIR environment variable.
    For more information, see Environment variables in STDENV and BIPENVS.