DevOps Automation

DevOps Automation

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#DevOps
 View Only

From Multiple JSON input to Unified YAML Configurations - A new way to generate artifact information for z/OS Deployments

By Shabaz Kowthalam posted Mon August 04, 2025 09:48 AM

  

The Challenge: Navigating Multiple Inputs to Understand Context

During z/OS deployments in DevOps Deploy, the Generate Multiple Artifact Information step is used to create custom information based on artifacts. This custom information includes items such as database BIND commands, CICS new copy lists, and SYSIN commands. The generated artifact information is subsequently used in post-processing steps of the deployment process.

The Generate Multiple Artifact Information step uses multiple JSON inputs to define filters and a template, which then generates text output. For example, it generates BIND commands and CICS new copy member lists using the property names bind-commands and cics-new-copy-members.

 

The challenge with this approach is that it is difficult to get a clear view of a single property's defined template and filters at a glance. Navigating multiple JSON inputs to check a property's value is not user-friendly, and users must remember to manually add a comma for each key-value pair.

The Solution: A new ‘Generate Multiple Artifact Information YAML’ step

This new step uses a single YAML input file where property templates and filters are defined in one place. This allows for the sequential addition of multiple properties. As the example demonstrates, using a single YAML input significantly improves the readability and maintenance of the property filters and templates used for generating artifact information. 

JSON - YAML inputs mapping

Below is a mapping of the old JSON inputs to their equivalent YAML attributes in the new step.

  • Container Name Filter JSON => sourceContainer

  • Target Data Set Name Filter JSON => targetContainer

  • Resource Name Filter JSON => resource

  • Deploy Type Filter JSON => deployType

  • Custom Properties Filter JSON => customProperties

  • Template JSON => template [Mandatory input]

  • Deployment action Filter JSON => deployAction

Benefits of YAML step 

The new Generate Multiple Artifact Information YAML step offers the following advantages over the older Generate Multiple Artifact Information step:

  • Improved readability, as all settings are in a single location 

  • The ability to include comments 

  • Familiarity with YAML syntax, which is commonly used in CI/CD applications 

  • Easier management of multi-line template outputs

How to Get the Plugin?

To use the new Generate Multiple Artifact Information YAML step, download the latest version of the z/OS Multi Generate Artifact Information plugin from the following page:

https://urbancode.github.io/IBM-UCx-PLUGIN-DOCS/UCD/zos-multi-generate-artifact-info/downloads.html

0 comments
21 views

Permalink