Creating z/OS® component versions from JCL

To create IBM® z/OS® component versions from job control language (JCL), create and submit JCL to run the buztool.sh command.

About this task

Note: The JCL to run buztool.sh is changed in HCL DevOps Deploy (Deploy) 6.2.5 to use the BPXBATCH utility. The JCL created before version 6.2.5 needs to be updated to follow the format in the new example.

Procedure

  1. Create a JCL file in a partitioned data set and base the file on the sample in the high_level_qualifier.SBUZSAMP(BUZRJCL) file.
  2. Use the buztool.sh createzosversion command to create the component version or buztool.sh createlinkedversion to create the linked version.
    Table 1. Arguments for the buztool command
    Parameter Required Description
    -c, -component true The component name in Deploy. The component name can contain only letters, numbers, and spaces.
    -v, -version false The name of the version to create. If a version is not specified, a version name is generated from the current time stamp. The version name can contain only letters, numbers, and spaces.
    -s, -shiplist true The location of the ship list file.
    -verb, -verbose false To display a trace log, set this parameter to true. If verbose is specified with no value, it is assumed true. This value should always be set to false in all environments, unless additional logging is needed for a specific need. Setting this to true, can cause out of memory errors, if the log generated is immense.
    -o, -output false The full path name of the file where the output of the version creation is written.
    -t, -type false The type of the version to create. Set to full to create a full version. Default is incremental.
    -to, -token false The token used to authenticate the server. This token can be created by a user who has access to create versions in the corresponding component. If the token is not provided, buztool takes the token from the <agent_home>/conf/installed.properties> server.token value to authenticate.
    -prop, -propertiesFilePath false The full path of the buztool properties file. The buztool property file contains deployType to copyType mappings. Use this parameter to pass details of external repository . See The buztool properties file, for more information.
    -url, -serverUrl false The URL of the server in which the version is to be created.
    -runtime.deploy false When set to false, disables hash calculation of artifacts. Default is true.
    -zpv false To use v2 package format, set this parameter to v2. If the parameter is not provided, it assumes it to be v1.
    -extrepo.url false The URL of external repository.
    -extrepo.repositoryType false The type of external repository. The value can be Nexus, or Artifactory.
    -extrepo.repository false The name of the repository in Artifactory (or Nexus) to which the version is uploaded.
    -extrepo.username false The user name of external repository.
    -extrepo.password false The password of external repository.
    -extrepo.apiKey false The API key of JFrog Artifactory to be used.
    -extrepo.rawDirectory false The raw directory in the Nexus repository to be used.
    -extrepo.httpProxyHost false The proxy host for external repository.
    -extrepo.httpProxyPort false The proxy port for external repository.
    createlinkedversion true The argument to create a linked version
    Note: This argument is applicable to z/OS linked versions.
    -from.hash true Specifies the commit from which a build tool like IBM Dependency Based Build calculates the changed files and performs a build. The system assumes that a previous version already exists for this commit, and Deploy uses that version as the parent for the new version that you create.
    Note: This argument is applies only to z/OS® linked versions.
    -to.hash true Specifies the commit hash in the repository where the build runs, typically the HEAD of the branch. This commit will be mapped to the version that you are creating.
    Note: This argument applies only to z/OS® linked versions.
    -parent.version true Specifies the parent version name for the version that you are creating. This field is required only when multiple versions exist for the commit ID specified in the -from.hash argument.
    Note: This argument applies only to z/OS® linked versions.
    For example, the following command creates a new version in the CICSModules component:
    /opt/install-dir/agent/bin/buztool.sh "createzosversion" "-c" "CICSModules" "-v"
        "fixbug100" "-s" "/u/ucduser/build/shiplist.xml"
    As shown, you must enclose all arguments in double quotation marks.
  3. Modify the sample file to reflect your system configuration.
  4. Submit the JCL.

Results

The content that the ship list file specifies is available in a component in Deploy.