Home
Integrating
HCL Launch supports integrations with other products, products from others, and certain cloud systems.
Deploying components to the z/OS® platform
Use the toolkit to deploy to the IBM® z/OS® platform.
Security requirements on IBM® z/OS® computers
Specific security definitions are used to secure HCL Launch functions for the IBM® z/OS® environment. To deploy applications to an IBM z/OS environment, the user accounts on the agent computer must have adequate access permissions. You must also identify specific directories and data sets to the authorized program facility.
IBM® z/OS® component versions
Component versions forIBM® z/OS® are imported from the build LPAR by using the buztool.sh command.

Integrating
HCL Launch supports integrations with other products, products from others, and certain cloud systems.
- Integrating with IBM® Rational® Asset Manager
  You can use IBM® Rational® Asset Manager to store and catalog build outputs, test results, and related packages as part of component processes in HCL Launch.
- Integrating with IBM® Rational® Test Workbench
  You can use IBM® Rational® Test Workbench to virtualize services and to run integration tests as part of component processes in HCL Launch.
- z/OS considerations for HCL Launch
  HCL Launch includes support for the z/OS platform. Although the articles in this Knowledge Center for using HCL Launch to deploy applications, certain platform-specific configuration factors must be considered when using a z/OS model.
- Deploying components to the z/OS® platform
  Use the toolkit to deploy to the IBM® z/OS® platform.
  - Ship list files
    The ship list file describes the files from the build to include in the new component version to deploy. Ship list files can also use generic artifacts to describe changes that are not physical files, such as configuration changes.
  - Searching the z/OS environment inventory
    The z/OS search feature is available for any application that contains a z/OS type component. Search is performed for a specific file in the artifacts belonging to the z/OS components deployed to that environment.
  - 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.
  - Security requirements on IBM® z/OS® computers
    Specific security definitions are used to secure HCL Launch functions for the IBM® z/OS® environment. To deploy applications to an IBM z/OS environment, the user accounts on the agent computer must have adequate access permissions. You must also identify specific directories and data sets to the authorized program facility.
    - IBM® z/OS® agent user accounts
      If you run the agent from a UNIX™ command line, the agent user account is the account that you use to log in to the UNIX shell. If you run the agent as a started task, the agent user account is assigned by the Resource Access Control Facility (RACF®) using the started procedures table (ICHRIN03) or the STARTED class. To learn more about RACF, see the z/OS® Security Server RACF System Programmer's Guide, SA23-2287-00.
    - IBM® z/OS® authorized program facility
      To deploy applications to an IBM® z/OS® environment, you must identify specific directories and data sets to the authorized program facility (APF).
    - IBM® z/OS® directories and data sets
      To deploy applications to an IBM® z/OS® environment, the user accounts on the agent computer must have adequate access permissions. You must also identify specific directories and data sets to the authorized program facility.
    - IBM® z/OS® tokens
      Tokens are used to authenticate with the HCL Launch server when z/OS® component versions are imported.
    - IBM® z/OS® component versions
      Component versions forIBM® z/OS® are imported from the build LPAR by using the buztool.sh command.
    - Security configuration related to z/OS
      Information for the HCL Launch server’s security model and the security configurations related to server agent communication for IBM® z/OS® are referenced in this topic.
  - Troubleshooting problems on z/OS®
    To troubleshoot problems on agent computers that are running IBM® z/OS®, examine the agent log files.

IBM® z/OS® component versions

Component versions forIBM® z/OS® are imported from the build LPAR by using the buztool.sh command.

Note: The user account that runs buztool.sh must have access to the UNIX™ directories and files and MVS™ data sets. Refer to IBM z/OS directories and data sets.

The user account used to import versions must have the following:

Access to the Time Sharing Option (TSO) and Interactive System Productivity Facility (ISPF) environments
Sufficient virtual memory to run Java™ in the OMVS address space. A minimum of 200 MB of virtual memory is required. The following list includes typical values for RACF® configuration parameters that specify virtual memory:
- ASSIZEMAX= 2147483647
- FILEPROCMAX= 00524287
- PROCUSERMAX= 00032767
- THREADSMAX= 00100000