Configuring a z/OS deployment definition

After you create a deployment definition, you can configure it by modifying or adding deployment definition properties.

Procedure

  1. If the Deployment Definition editor is not already open, expand the Enterprise Extensions node, then the Deployments node. Right-click the deployment definition that you want to configure and select Open Deployment Definition.
  2. In the Deployment Definition editor, go to the Overview tab.
    1. Optional: In the General Information Description field, briefly describe your deployment definition.
    2. Optional: Select Ignore warnings when computing overall status.
    3. In the Supporting Build Engines field, click Create to create a build engine, or select an existing build engine by clicking Add, selecting the build engine, then clicking OK. You must associate a build engine with your package definition. For more information, see Creating build engines.
    4. Optional: In the Pruning Policy field, select Prune build results, then set the number of successful and failed builds to save.
  3. Optional: Go to the Properties tab. From the Properties table, you can highlight an existing property that you want to edit. Click Edit and enter a value in the Value field. You can also click Add or Remove to add or remove properties.
  4. Perform the following steps from the z/OS Deployment tab:
    1. On the Load tab, select a package definition, select a load method (FTP or Copy), and then configure the following properties:
      Copy
      If you select Copy, the package you deploy is transferred by copying it to the load space (for mounted drives).
      Note: When you select Copy, you do not have to specify a Host Name, User ID, or Password File.
      FTP
      Deploy the package to the load space by FTP.
      Note: If you select FTP, you must specify a Host Name, User ID, and Password file for the system that contains your package.
      Host name
      If you select FTP, you must specify the host name of the system that contains your package.
      User ID
      If you select FTP, you must specify your user ID on the system that contains your package.
      Password file
      If you select FTP, you must specify the location of the password file (by using the Jazz™ Build Engine and the -createPasswordFile flag) on the system where your deployment is running. The encrypted password is the password for the user ID on the system that contains your package. For more information about password files, see:
      Deployed package root directory
      Specify the directory where you want your package to be loaded.
      Note: Blanks or $ character are not supported in the Deployed package root directory.
      Original package root directory
      Specify the directory where the package was created. This directory should be the same as the Package Root Directory in the associated package definition.
      Note: Blanks or $ character are not supported in the Package Root Directory.
      Load pre-command
      Specify a command to run on the deployment system before loading.
      Load post-command
      Specify a command to run on the deployment system after loading.
      Note: If you want to call a REXX script from the load pre-command or load post-command fields, see Starting the ISPF gateway from pre-deployment or post-deployment commands in Configuring the ISPF gateway for build, deployment, and promotion support.
    2. On the Deploy tab, specify the PDS you packaged, and where to deploy it.
      HFS target directory
      If the package being deployed contains HFS files, you need to specify the directory so the HFS files within the archive will be unpacked to it.
      Deploy pre-command
      Specify a command to run on the deployment system before you deploy.
      Deploy post-command
      Specify a command to run on the deployment system after you deploy.
      Rollback pre-command
      Specify a command to run on the deployment system before the rollback.
      Rollback post-command
      Specify a command to run on the deployment system after the rollback.
      Temporary working data set prefix

      During deployment, by default, a temporary data set name will be used as the prefix. Either it is created by using the prefix(HLQ) specified in the user's TSO profile if it exists, or it is the userid. If the user does not have data set creation privilege to the prefix, they can specify a prefix here to use during the deployment.

      Note: If you want to call a REXX script from the deployment and rollback pre-command or post-command fields, see Starting the ISPF gateway from pre-deployment or post-deployment commands in Configuring the ISPF gateway for build, deployment, and promotion support.
    3. Optional: Select Allow multiple rollbacks and indicate how many packages that you want saved. Selecting this option allows your team to roll back any saved package that was successfully deployed.
      Notes:
      • This option is available only with version 5.0.1 or later. With earlier versions, you can only roll back the last package that was successfully deployed to its previously deployed state.
      • If the value for Maximum number of rollbacks to keep is set to 0, all rollback archives are saved on the deployment server. To free up space on the server, you must delete obsolete rollback archives manually or by using a scheduled cleanup program.
    4. On the Publish tab, specify the options for publishing the deployment report:
      Publish delta deploy manifest
      Select this option to publish the delta deployment manifest file in the deployment result.
      Publish cumulative deploy manifest
      Select this option to publish the cumulative deployment manifest file in the deployment result.
      Publish rollback manifest
      Select this option to publish the rollback manifest file in the deployment result.
  5. Optional: Go to the Ant tab.
    1. In the Build File and Targets section, specify the Ant build file and targets you want your definition to start. Reference properties by using this format: ${propertyName}.
    2. In the Ant Configuration section, select Include the Jazz build toolkit tasks on the Ant library path if you want to add the -lib Ant argument with the path to the Jazz buildtoolkit directory.
    3. Specify any of the following configuration details:
      • Ant home
      • Ant arguments. The default is -verbose.
      • Working directory
      • Java™ home
      • Java VM arguments. The default is -Xquickstart.
      • Properties file
  6. Click Save to save your deployment definition.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki