Description

The z/OS File Source Config plugin automates uploading data sets, UNIX files, and generic artifacts from a z/OS system into a component version. The z/OS File Source Config plugin provides a Web UI to run the version import commands from z/OS deployment tools.

Quick Info

Product
HCL Launch
Type
plugin
Compatibility
HCL Launch version 7.0 or later
Created by
HCL Software
Website
Updated Date
May 31, 2021
Version Name Modified date Action

4.1100666

launch-zosfilesourceconfig-4.1100666.zip 16-Mar-2021 07:44

5.1109122

launch-zosfilesourceconfig-5.1109122.zip 11-Jun-2021 07:55

launch-zosfilesourceconfig-4.1100666.zip

4.1100666


launch-zosfilesourceconfig-5.1109122.zip

5.1109122


Summary

The z/OS File Source Config plugin automates uploading data sets, UNIX files, and generic artifacts from a z/OS system into a component version. New component versions are created based on ship list files.

This plugin includes one or more steps, click Steps for step details and properties.

Compatibility

This plugin requires HCL Launch version 7.0 or later.

This plugin is supported to run on z/OS.

Installation

See Installing plugins in HCL Launch for installing and removing plugins.

History

The following table describes the changes made in each plugin version.

Plugin history details
Version Description
5 Minor enhancements
4 Fixing CVE:CVE-2019-4233

Usage

The HCL Launch z/OS deployment tools must be installed to the version import agent to use the z/OS File Source Config plugin.

To use this plugin, create a component to define the z/OS artifacts to be used. The component contains the information for importing the artifacts and any processes to perform on the artifacts.

Create a component

To create a component, complete the following steps. For more information, see Creating components
topic in the product documentation.

  1. In the HCL user interface, click Components and then click Create Component.
  2. In the Create Component window, specify a name and description for the component.
  3. In the Teams fields, specify the access information for the new component.
  4. To use a template for the new component, select a template from the Template list. In this case, the component inherits source configuration, properties, and processes from the template.
  5. In the Source Config Type list, select zOS File.

  6. Specify the properties for the component. See the Setting tab for descriptions.
  7. Click Save.

Import a version

When the artifacts are imported, a component version is created using the version of the package. You can specify to import a specific package version or import all versions. If importing all versions, a component version is created for each version.

  1. Click the Versions tab for the component.
  2. Click Import New Versions.
  3. Specify a specific version of the package to import, or leave blank to import the latest version of the package available in the repository. Additionally, enable Import All Versions to import all versions of a package.
  4. Click Save.

Step palette

To access this plugin in the palette, click Source and Repositories > zOS File.

Steps

The following process steps are available in the zOS File plugin.

Import Version

This step has no input properties.

Roles

Roles in the zOS File plugin

The plugin adds these roles automatically to resources. You cannot add these roles manually.

zOSFileComponentProperties

Properties for the zOSFileComponentProperties role
Name Type Description Reference
Default Shiplist String Input the content of a shiplist. When both shiplist content and shiplist file are specified, the shiplist content is used. ${p:component/zOSFileComponentProperties/defaultShiplistContent}
Default Shiplist File String Specify the path to a default shiplist file on the host. ${p:component/zOSFileComponentProperties/defaultShiplitFilePath}
Version Name Prefix String Specify a version name prefix ${p:component/zOSFileComponentProperties/versionNamePrefix}

zOSFileImportProperties

Properties for the zOSFileImportProperties role
Name Type Description
Shiplist String Input the content of a shiplist. If left blank the default shiplist content is used. When both shiplist content and shiplist file are specified, the shiplist content is used.
Shiplist File String Specify the path to a shiplist file on the host. If left blank the default shiplist file is used.
Since Time Stamp String Specify a time stamp to include artifacts modified arfter this timestamp. Specify LASTVERSION to use the time stamp of the last version. If left blank, all artifacts in shiplist are included.
Version Name String Specify the version name. If left blank, a version name is generated based on the prefix and current time stamp.