Creating z/OS component versions#
You can create z/OS component version by running the buztool.sh command from job control language (JCL) or from the z/OS® UNIX™ System Services command line. You can also create z/OS component version by using the z/OS File Source Config plug-in.
In an automated system, typically, you write a script that runs the buztool.sh command after a build is created by your build system. The buztool.sh command then creates a component version which can be deployed using a deploy process.
You can work with the component that contains z/OS files as you would work with any other component in HCL™ Launch. Use the z/OS Utility plug-in to create processes that deploy components that contain z/OS files. See the HCL Launch website for information about the z/OS Utility plug-in: Plugins.
Note: IMS.TFORMAT members (member name containing non-readable characters) are not supported. PDS members name can have ONLY [0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ@#$] characters.
- 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.
- 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.
- Creating z/OS component version using the v2 package format
Starting with HCL Launch version 7.0.5, you can create IBM z/OS component versions from a new package version called version 2 or v2. You can create v2 component versions using the buztool.sh command.
- Merging z/OS component versions
Two or more z/OS component versions can be merged from a snapshot into one component version to simplify the deployment to the next environment. Merging component versions in this way avoids deploying intermediate programs into production.
Parent topic: Deploying components to the z/OS platform