Creating z/OS® component versions from z/OS® UNIX™ System Services

To create IBM® z/OS® component versions from z/OS® UNIX™ System Services, submit the buztool.sh command from a z/OS® UNIX™ shell.

Procedure

  1. Open a z/OS® UNIX™ shell.
  2. Use the buztool.sh createzosversion command to create the component version.
    Table 1. Arguments for the buztool createzosversion.sh createzosversion command
    Parameter Required Description
    -c, -component true The component name in HCL Launch. 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.
    For example, the following command creates a new version in the CICSModules component:
    buztool.sh createzosversion -c CICSModules -v fixbug100 -s /u/ucduser/build/shiplist.xml
    If an argument contains spaces, enclose the argument in double quotation marks, as shown in the following example:
    buztool.sh createzosversion -c "CICS Modules" -v "fixbug 100" -s /u/ucduser/build/shiplist.xml

Results

The content that the ship list file specifies is available in a component in HCL Launch.
Note: If the agent is upgraded from V7.0.5, the postfix "/artifactory/" is not automatically added to the Artifactory URL from agent V7.1.0. This may result in HTTP response error code 404 while creating version using the buztool. Add postfix "/artifactory" manually to the url property in the artifactory properties file to avoid the 404 HTTP error.