Customer pain point:
A number of users of CICS Configuration Manager for z/OS (CICS CM) prepare and condition CICS resource definitions (on their development LPAR) into change packages for delivery. They then transfer these for deployment onto other LPARs. However, the remote LPARs do not have CICS CM deployed. Therefore, instead of exporting the changes using CICS CM’s internal format, their implementation uses the CICS CM export function to build export files in DFHCSDUP format for transfer and subsequent use.
This implementation works very well except that: Commands to DELETE unwanted definitions and to ADD (or REMOVE) a Group in a List are not supported. This is because the command data is stored along with change package control information in export files in CICS CM format, whereas DFHCSDUP files have no provision for change packages.
What the enhancement provides
The enhancement addresses the requirement to support commands to DELETE unwanted definitions and to ADD (or REMOVE) a Group in a List. Therefore, when CICS CM migrates a change package to a DFHCSDUP export file, package commands to perform DELETEs and ADD (or REMOVE) Groups in a List are converted into their DFHCSDUP command equivalents. The export file now contains both the resource definitions and commands required for the target system.
How does this enhancement help CICS Configuration Manager users
This enhancement provides more flexibility with CICS CM implementations. If the deployment LPARs do not require CICS CM services for definition editing, security, life cycle migration, auditing and so forth, and only require deployment, then the DFHCSDUP format file can be used to export the definitions and commands prepared on a development LPAR using CICS CM. This simplifies CICS CM set up and implementation.