Rolling back implemented schema changes in UrbanCode Deploy/HCL Launch

To use two different component processes to generate the rollback artifacts

This topic describes how to use two different component processes to generate the rollback CDL file and the other rollback artifacts respectively.

This topic describes how:

• To generate the rollback CDL file
• To generate the other rollback artifacts

To generate the rollback CDL file

Use the following procedure to generate the rollback CDL file for your component process.

1. Create a component process or open an existing component process for configuration. For more information, see the following topics:
   • Creating-a-component-process
   • To configure a component process

2. Add the following process steps sequentially and configure them:

   Serial number	Process step
   1	BMC AMI DevOps Common - Authentication
   2	Select one or a combination of the following Schema Migration steps: BMC AMI DevOps Schema Migration - Schema Mig: Cat to Cat Baseline Profile as Scope BMC AMI DevOps Schema Migration - Schema Mig: Cat to Cat Migrate Profile as Scope BMC AMI DevOps Schema Migration - Schema Mig: Cat to Cat Objects as Scope BMC AMI DevOps Schema Migration - Schema Mig: Cat to DDL-WL-BL BMC AMI DevOps Schema Migration - Schema Mig: Use Existing CDL File
   3	BMC AMI DevOps Schema Migration - Output Transmission
   4	BMC AMI DevOps Common - JCL Execution
   5	BMC AMI DevOps Common -  Clean Up

   When configuring the BMC AMI DevOps Schema Migration process step, do the following:

   1. In the Select Baseline Type Before Execution field, select one of the following baseline types:
      1. 
         
         • Pre-Execution Baseline
         • Full-Recovery Baseline
   2. Enter the baseline profile name in the Baseline Profile Name (before execution) field.
   3. Enter the baseline name in the Baseline Name (before execution) field.
   4. Select the Generate CDL to Rollback Schema Changes check box.
   5. Enter a partitioned data set (PDS) and member name in the Rollback PDS and Member Name (CDL) field.    
   6. Click OK to save your BMC AMI DevOps Schema Migration process step configuration.
3. Execute the component process. For more information, see To execute a component process.

This implements the defined schema changes and also generates the rollback CDL file.

To generate the other rollback artifacts

After generating a rollback CDL file for your component process, you can use the following procedure to generate the other rollback artifacts, which can be used to roll back the implemented schema changes.

1. Create a component process or open an existing component process for configuration.

2. Add the following process steps sequentially and configure them:

   Serial number	Process step
   1	BMC AMI DevOps Common - Authentication
   2	BMC AMI DevOpsSchema Migration - Schema Mig: Use Existing CDL File
   3	BMC AMI DevOpsSchema Migration - Output Transmission
   4	BMC AMI DevOps Common -  Clean Up

   When configuring the BMC AMI DevOps Schema Migration - Schema Mig: Use Existing CDL File process step, do the following:

   1. In the Work ID Name field, enter a different work ID from the one you entered when configuring the component process that generated the rollback CDL file.

      Tip

      BMC recommends adding a _RB suffix to the work ID you entered when configuring the component process that generated the rollback CDL file.

      Example

      In the Work ID Name field, if you entered ${p:Job_ID} when configuring the component process that generated the rollback CDL file, you can enter ${p:Job_ID}_RB when configuring the component process that generates the other rollback artifacts.

   2. In the CDL PDS and Member Name field, enter the PDS and member name of the rollback CDL file.
   3. In the Worklist PDS and Member Name field, enter the PDS and member name of the rollback worklist.
   4. In the Impact Report PDS and Member Name field, enter the PDS and member name of the rollback impact report.
   5. In the Execution JCL PDS and Member Name field, enter the PDS and member name of the rollback execution JCL.

   6. (optional) In the Additional Analysis Input Keywords field, add the following lines if you are rolling back schema changes using a full-recovery baseline that you created using the work ID of the component process that generated the rollback CDL file:

      BLNAME baselineName
      BLRECOVER

      The baselineName variable represents the baseline name of the full-recovery baseline.

   7. Click OK to save your BMC AMI DevOpsSchema Migration - Schema Mig: Use Existing CDL File process step configuration.

   When configuring the BMC AMI DevOps Schema Migration- Output Transmission process step, do the following:

   Important

   The BMC AMI DevOps Schema Migration - Output Transmission process step lets you download any or all of the rollback artifacts to the destination directory. To download a rollback artifact, enter its respective source PDS name.

   You must enter the source PDS name for at least one rollback artifact.

   1. In the Source PDS Name (CDL) field, enter the PDS of the rollback CDL file.
   2. In the Source PDS Name (WORKLIST) field, enter the PDS of the rollback worklist.
   3. In the Source PDS Name (EXEC_JCL) field, enter the PDS of the rollback execution JCL.
   4. In the Source PDS Name (IMPACT REPORT) field, enter the PDS of the rollback impact report.
   5. In the Source Member Name field, enter the file name of the rollback member on the mainframe.
   6. In the Destination Directory Name field, enter the directory into which you want to download all the rollback artifacts.
   7. In the Destination File Name field, enter a value that can be used to generate the file names for all the rollback artifacts.
   8. Click OK to save your BMC AMI DevOps Schema Migration - Output Transmission process step configuration.
3. Execute the component process. For more information, see To execute a component process.

This generates the rollback execution JCL.

To use the same component process to create the rollback artifacts

The following procedure describes how you can use the same component process to create all the rollback artifacts.

1. Create a component process or open an existing component process for configuration. For more information, see the following topics:
   • Creating-a-component-process
   • To configure a component process

2. Add the following process steps sequentially and configure them:

   Serial number	Process step	Comments
   1	BMC AMI DevOps Common - Authentication
   2	Select one of the following Schema Migration process steps: BMC AMI DevOpsSchema Migration - Schema Mig: Cat to Cat Baseline Profile as Scope BMC AMI DevOps Schema Migration - Schema Mig: Cat to Cat Migrate Profile as Scope BMC AMI DevOps Schema Migration - Schema Mig: Cat to Cat Objects as Scope BMC AMI DevOps Schema Migration - Schema Mig: Cat to DDL-WL-BL BMC AMI DevOps Schema Migration - Schema Mig: Use Existing CDL File	Generates the rollback CDL file
   3	BMC AMI DevOps Schema Migration - Output Transmission 1	Downloads the CDL file, worklist, impact report, and execution JCL, which implement the schema changes, to the specified directory
   4	BMC AMI DevOps Common - JCL Execution	Implements the schema changes
   5	BMC AMI DevOps Schema Migration - Schema Mig: Use Existing CDL File	Generates the other rollback artifacts
   6	BMC AMI DevOps Schema Migration - Output Transmission 2	Downloads all the rollback artifacts to the specified directory
   7	BMC AMI DevOps Common -  Clean Up

   When configuring the BMC AMI DevOps Schema Migration process step, do the following:

   1. In the Select Baseline Type Before Execution field, select one of the following baseline types:
      1. 
         
         • Pre-Execution Baseline
         • Full-Recovery Baseline
   2. Enter the baseline profile name in the Baseline Profile Name (before execution) field.
   3. Enter the baseline name in the Baseline Name (before execution) field.
   4. Select the Generate CDL to Rollback Schema Changes check box.
   5. Enter a partitioned data set (PDS) and member name in the Rollback PDS and Member Name (CDL) field.
   6. Click OK to save your BMC AMI DevOps Schema Migration process step configuration.

   When configuring the  BMC AMI DevOps Schema Migration - Schema Mig: Use Existing CDL File process step, do the following:

   1. Enter a different work ID in the Work ID Name field from the one you entered when configuring the first BMC AMI DevOps Schema Migration process step.

      Tip

      BMC recommends adding a _RB suffix to the work ID you entered when configuring the BMC AMI DevOps Schema Migration process step.

      Example

      In the Work ID Name field, if you entered ${p:Job_ID} when configuring the BMC AMI DevOps Schema Migration process step, you can enter ${p:Job_ID}_RB when configuring the BMC AMI DevOps Schema Migration - Schema Mig: Use Existing CDL File process step.

   2. In the CDL PDS and Member Name field, enter the PDS and member name of the rollback CDL file.
   3. In the Worklist PDS and Member Name field, enter the PDS and member name of the rollback worklist.
   4. In the Impact Report PDS and Member Name field, enter the PDS and member name of the rollback impact report.
   5. In the Execution JCL PDS and Member Name field, enter the PDS and member name of the rollback execution JCL.

   6. (optional) In the Additional Analysis Input Keywords field, add the following lines if you are rolling back schema changes using a full-recovery baseline that you created using the work ID of the first BMC AMI DevOps Schema Migration process step:

      BLNAME baselineName
      BLRECOVER

      The baselineName variable represents the baseline name of the full-recovery baseline.

   When configuring the  BMC AMI DevOps Schema Migration - Output Transmission 2 process step, do the following:

   Important

   The BMC AMI DevOps Schema Migration - Output Transmission process step lets you download any or all of the rollback artifacts to the destination directory. To download a rollback artifact, enter its respective source PDS name.

   You must enter the source PDS name for at least one rollback artifact.

   1. In the Source PDS Name (CDL) field, enter the PDS of the rollback CDL file.
   2. In the Source PDS Name (WORKLIST) field, enter the PDS of the rollback worklist.
   3. In the Source PDS Name (EXEC_JCL) field, enter the PDS of the rollback execution JCL.
   4. In the Source PDS Name (IMPACT REPORT) field, enter the PDS of the rollback impact report.
   5. In the Source Member Name field, enter the file name of the rollback member on the mainframe.
   6. In the Destination Directory Name field, enter the directory into which you want to download all the rollback artifacts.
   7. In the Destination File Name field, enter a value that can be used to generate the file names for all the rollback artifacts.
   8. Click OK to save your BMC AMI DevOps Schema Migration - Output Transmission 2 process step configuration.
3. Execute the component process. For more information, see To execute a component process.