Customizing the JCL

Customize the JCL, as part of creating an integration server on IBM® z/OS® Container Extensions (zCX).

About this task

All JCL has a standard header, which includes the following items:
  • A brief description of its function.
  • A description where further information can be found.
  • Instructions about how to customize the JCL.
  • A section that lists the JCL itself.
The following sample JCL is supplied by the IBM z/OS Management Facility installation process:
  • BIPXBLD - Sample job to build a Docker image to run an integration server.
  • BIPXCLIS - Sample job to run the console listener program.
  • BIPXDBG - Sample job to debug the integration server Docker container.
  • BIPXDLI - Sample job to load a Docker image from a .tar archive on z/OS UNIX System Services.
  • BIPXDSP - Sample job to run a Docker system purge to clear space on the zCX instance.
  • BIPXGET - Sample job to copy or move a file from a running integration server Docker container to UNIX System Services.
  • BIPXIS - Sample job to run an integration server in zCX and display its logs.
  • BIPXISCM - Sample job to run an integration server runtime command.
  • BIPXISTP - Sample job to stop the integration server or to stop and remove its container, or to remove the container that is already stopped.
  • BIPXPUT - Sample job to copy a file from UNIX System Services to a running integration server Docker container.

Procedure

  1. Customize the JCL files by following the instructions in the files. You can customize the files by using an ISPF edit macro that you must tailor, or you can edit each of the PDSE members manually. Most of the customizations are standard for all of the JCL files.
  2. Create environment files and set the environment variables that you need for each task.
    You need a different set of environment variables for each task such as building an image, starting an integration server, or running commands. Therefore, you can choose to create a different environment file for each task and or integration server. For each task, you might need more than one environment file if different users have different levels of access. You can specify multiple environment files in the STDENV concatenation. For more information, see Environment variables in STDENV and BIPENVS.

What to do next

Create an IBM App Connect Enterprise Integration Server Docker image on IBM z/OS Container Extensions (zCX), as described in Creating an IBM App Connect Enterprise Integration Server Docker image on IBM z/OS Container Extensions (zCX) by using the supplied JCL.