The Jazz™ Build Engine
is installed when you install the Jazz Team
Server for System z®. Setting
up the build engine is optional.
Before performing the setup steps,
review
Lesson 8: Team Builds in the tutorial
Getting Started with Rational Team Concert™.
Restriction: The 64-bit Java™ Virtual
Machine (JVM) works with the application server, but the JVM that
invokes the Apache Ant tool for performing Antz builds on z/OS®
must be a 31-bit JVM:
either JVM 1.5 or 1.6. Currently, Antz does not support any 64-bit
JVM. For more information about Jazz Build
Engine prerequisites, refer to
Detailed System Requirements for Rational Team Concert for System z Version 2.0 at
http://www-01.ibm.com/support/docview.wss?rs=3641&uid=swg27016662.
Complete the following steps before starting the build engine:
- Register the build engine instance using Rational Team Concert for System z client.
- Create a Jazz user
ID for the build engine. This user ID must have write access to the
directory that you will use to create the build artifacts.
- Optional: Create an encrypted password file for
the build engine to use to prevent casual observation. For
information on creating an encrypted password file, see Creating a password file using the sample BLZBPASS job.
- Edit the BLZBENG member and modify the settings using the
instructions in the JCL.
- Comment out the SYSPRINT DD statement in the JVMPRC50 PROC
provided by JZOS. The Jazz Build
Engine for System z will
allocate SYSPRINT dynamically during the build.
//JVMPRC50 PROC JAVACLS=, < Fully Qfied Java class..RQD
// ARGS=, < Args to Java class
// LIBRARY='JAZZ00.MVS269.JZOS.LOADLIB', < STEPLIB FOR JVMLDM module
// VERSION='50', < JVMLDM version: 50
// LOGLVL='+T', < Debug LVL: +I(info) +T(trc)
// REGSIZE='0M', < EXECUTION REGION SIZE
// LEPARM=''
//JAVAJVM EXEC PGM=JVMLDM&VERSION,REGION=®SIZE,
// PARM='&LEPARM/&LOGLVL &JAVACLS ARGS'
//STEPLIB DD DSN=&LIBRARY,DISP=SHR
//*SYSPRINT DD SYSOUT=* < System stdout (commented out)
- To start the build engine, submit the BLZBENG JCL. The
job must remain active and the following messages must end in the
STDOUT: 2009-02-16 11:00:00 Running build loop... and 2009-02-16
11:00:00 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.
- To end the build engine, stop or purge the job.