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.
An example of a standard enterprise application topology for the z/OS platform is shown. The z/OS components run on CICS with virtual storage access method (VSAM) for the data source. Some of the web and mobile components also run on z/OS using an application platform such as IBM WebSphere for z/OS. Some components run on distributed platforms.
Additional information for the z/OS platform can be found in https://www.ibm.com/support/knowledgecenter/zosbasics/com.zos.zmainframe/toc.htm
These characteristics require the following considerations, as detailed in these areas of HCL Launch.
- Installing the z/OS agent
Before you deploy to the IBM z/OS® platform, you must install the z/OS® agent and configure the z/OS® server for communication with HCL Launch. If the build process runs on a different logical partition (LPAR), then you must additionally install the agent on the build LPAR. You can install the z/OS® agent and deployment tools by using the IBM System Modification Program Extended (SMP/E) or by extracting archive files to the z/OS® UNIX™ file system.
- Upgrading IBM z/OS agents
You can upgrade IBM z/OS® agents. However, you must upgrade the server before you upgrade the agents.
- Starting z/OS agents from the z/OS UNIX command line
The UCD z/OS agent can be started from ISPF as a started task or from the z/OS UNIX command line. To start an agent from ISPF as a started task refer to Starting agents. To start the z/OS agent from the z/OS UNIX command line, follow this procedure.
- Installing the z/OS agent and deployment tools by using SMP/E
IBM System Modification Program/Extended (SMP/E) is a tool for installing and maintaining software on z/OS® systems. SMP/E controls software changes at the element level. Job Control Language (JCL) is submitted by using 3270 emulation.
- Job Monitor customization
The Job Monitor binary is installed with the IBM z/OS® deployment tools in the hlq.SBUZAUTH data set. You need the assistance of a security administrator and a TCP/IP administrator to complete this customization task.
- Planning storage
You can store the versions in CodeStation or in Artifactory/Nexus. To store versions in Artifactory or Nexus, the artifactory details must be passed to the buztool.sh. Every z/OS agent that is used to deploy projects, stores backups of old artifacts so that a rollback can be done when required. Plan the agent directory to ensure there is sufficient space for backup.
- Customizing and verifying the TSO-ISPF client gateway
HCL Launch uses the IBM z/OS® Time Sharing Option-Interactive System Productivity Facility (TSO-ISPF) gateway when it imports and deploys component versions.
Parent topic: Overview of integrations