Home
Integrating
HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
z/OS considerations for DevOps Deploy
HCL DevOps Deploy (Deploy) includes support for the z/OS platform. Although the articles in this Knowledge Center for using Deploy to deploy applications, certain platform-specific configuration factors must be considered when using a z/OS model.
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.

Integrating
HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
- Integrating with DevOps Test Performance
  When you use HCL DevOps Test Performance (Test Performance), you can create tests and run those tests in HCL DevOps Deploy (Deploy) by using the Test Performance Deploy plug-in.
- z/OS considerations for DevOps Deploy
  HCL DevOps Deploy (Deploy) includes support for the z/OS platform. Although the articles in this Knowledge Center for using Deploy to deploy applications, certain platform-specific configuration factors must be considered when using a z/OS model.
  - 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 DevOps Deploy (Deploy). 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 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 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 install/topics/run_agent.html. 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 DevOps Deploy (Deploy) uses the IBM® z/OS® Time Sharing Option-Interactive System Productivity Facility (TSO-ISPF) gateway when it imports and deploys component versions.
- Deploying components to the z/OS® platform
  Use the toolkit to deploy to the IBM® z/OS® platform.

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.

Before you begin

Procedure

Create a JCL file in a partitioned data set and base the file on the sample in the high_level_qualifier.SBUZSAMP(BUZRJCL) file.

Use the buztool createzosversion command to create the component version.

Table 1. Arguments for the buztool createzosversion command
Parameter	Required	Description
-c	true	The name of the component in HCL DevOps Deploy (Deploy). 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. Note: The version name must not end in a space.
-s	true	The location of the ship list file.
-verb	false	To display a trace log, set this parameter to `true`.

For example, the following command creates a new version in the CICSModules component:

buztool "createzosversion" "-c" "CICSModules" "-v" "fixbug100" "-s" "/u/ucduser/build/shiplist.xml"

As shown, you must enclose all arguments in double quotation marks.

Modify the sample file to reflect your system configuration.
Submit the JCL.

Results

The content that the ship list file specifies is available in a component in Deploy.