Running the Jazz Build Engine on z/OS

Follow these steps to process your build request on z/OS® using the Jazz® Build Engine.

Before you begin

The Jazz Build Engine is installed when you install the Build System Toolkit on z/OS. Setting up the build engine is optional. Some build templates for z/OS require the Rational® Build Agent, not the Jazz Build Engine. You need the Jazz Build Engine only for builds that you define using a Jazz Build Engine template, such as the Command Line - Jazz Build Engine template. For more information, see Build templates available for z/OS.

Before performing the setup steps, review the Manage builds with the IBM® Engineering Workflow Management Build lesson in the Get started with Engineering Workflow Management tutorial.

About this task

Complete the following steps before starting the build engine:


  1. Use the Eclipse client to create a build engine definition on the Engineering Workflow Management server. This "registers" the build engine with the server, which needs to know such build engine characteristics as the build engine ID, supported build definitions, and so forth. These characteristics are saved in the build engine definition.
  2. Two user IDs (which might not be the same) are required to run the Jazz Build Engine on z/OS: First, the build engine JCL specifies a user ID and password that are used to connect and authenticate to the server to perform build and SCM operations. Second, the user ID the BLZBENG JCL requires on z/OS determines what z/OS data set and file system authority should be used on the z/OS build system.
    1. Confirm that the user ID specified in the BLZBENG JCL is a valid user for your server, and that it has the required credentials to extract the artifacts to build.
    2. Confirm that the user ID assigned to the BLZBENG job has the authority to create the necessary artifacts on z/OS.
  3. Optional: Create an encrypted password file for the build engine to use to prevent casual observation.
    For information about creating an encrypted password file, see Creating a password file using the sample BLZBPASS job.
    Note: (Optional) You can now use application password with OpenID Connect. For more information, see Obtaining an application password.
  4. Edit the BLZBENG member and modify the settings using the instructions in the JCL.
  5. To start the build engine, submit the BLZBENG JCL. The job must remain active and the following messages must end in the STDOUT: <Time and date> Running build loop... and <Time and date> Waiting for request. If these messages are not shown in the STDOUT, check the SYSOUT to identify the issues that occurred when you initialized the build engine.
  6. To end the build engine, stop or purge the job.