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
- Open a z/OS® UNIX™ shell.
- Use the buztool.sh createzosversion command
to create the component version.
Table 1. Arguments for the buztool.sh createzosversion command Parameter Required Description -c true The component name in HCL Launch. The component name can contain only letters, numbers, and spaces. -v 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 true The location of the ship list file. -verb 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 false The full path name of the file where the output of the version creation is written. -t false The type of the version to create. Set to full to create a full version. Default is incremental. -ar false The full path of the external artifact repository property file. Use this parameter if the artifacts have to be stored in an external artifactory other than Codestation. -to 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. -zpv false To use v2 package format, set this parameter to v2. If the parameter is not provided, it assumes it to be v1. -prop false The full path of the buztool properties file. The buztool property file contains deployType
tocopyType
mappings. Use only for v2 package format. See The buztool properties file, for more information.Example format for the external artifactory repository properties file is below:#Mon Apr 06 02:29:53 EDT 2020 #Repository_type valid values are NEXUS or ARTIFACTORY Repository_type=ARTIFACTORY #url - External Repository URL url=http\://10.134.119.249\:8081/artifactory #username to connect username= #password to use. This password will be encrypted after first use password= #apiKey - In case of ARTIFACTORY, it can be either password or apikey. This element will be encrypted after first use apiKey= #repository - repository name in ARTIFACTORY or NEXUS to which artifacts are uploaded. repository=my-maven-repo #httpProxyHost - if a proxy must be used to connect ARTIFACTORY httpProxyHost= #httpProxyPort - if proxy must be used to connect ARTIFACTORY httpProxyPort= #rawdirectory - Name of the directory to push version to under Nexus repository rawdirectory=
For example, the following command creates a new version in the CICSModules component:
If an argument contains spaces, enclose the argument in double quotation marks, as shown in the following example:buztool.sh createzosversion -c CICSModules -v fixbug100 -s /u/ucduser/build/shiplist.xml
buztool.sh createzosversion -c "CICS Modules" -v "fixbug 100" -s /u/ucduser/build/shiplist.xml
Results
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.