Executing a task ID

Use the following procedure to execute a task ID. Executing a task ID consists of creating a CM/PILOT worklist and the JCL for processing the worklist, and then processing the CM/PILOT worklist. The results of a successful execution are an Analysis worklist and the Execution JCL to process the worklist.

If the worklist fails to process successfully, you must correct the error and specify either to restart the processing from the last sync point before the failure or to start the worklist processing over from the beginning. For more information, see Restarting-a-CM-PILOT-worklist and Starting-a-CM-PILOT-worklist-over.

In addition to the information that you specified for the task ID before selecting to execute it, you need to provide CM/PILOT with data set names and other processing options.

To execute a task ID

  1. On the BMC AMI Change Manager for Db2 Main Menu, select CM/PILOT, and press Enter.
  2. On the CM/PILOT Main Menu, select TASKIDs and press Enter.
  3. On the TASKID Action Menu, type the name of a TASKID or a specify a wildcard pattern and select Execute a TASKID. Then, press Enter.
  4. On the TASKID Interface panel, type the name of a WORKID, if it is not already specified.
  5. Specify the data set names to be used to process the CM/PILOT worklist.
    1. Type the name of the data set that will contain the CM/PILOT worklist. The data set can be partitioned or sequential, and you can use symbolic variables in the name.
      • If you specify a partitioned data set (PDS), you can either provide a member name or leave it blank to create a list of existing members from which to select. The data set must be fixed block (FB) and have a logical record length (LRECL) of 80.
      • If you specify a sequential data set that does not exist, it is created when the CM/PILOT worklist is created. If you specify a sequential data set that does exist, the disposition of the data set is set to shared and any existing data in the data set is overwritten.
    2. Type the name of the data set that will contain the JCL to process the CM/PILOT worklist. The data set can be partitioned or sequential, and you can use symbolic variables in the name.
      • If you specify a PDS, you can either provide a member name or leave it blank to create a list of existing members from which to select.
      • If you specify a sequential data set that does not exist, it is created when the JCL is created. If you specify a sequential data set that does exist, the disposition of the data set is set to shared and any existing data in the data set is overwritten.

    3. Type the name of the data set for Diagnostics. You can specify either a sequential data set or SYSOUT for the diagnostic output from CM/PILOT worklist processing. You can also use symbolic variables to specify a sequential data set.If you specify a sequential data set that does not exist, it is created when the CM/PILOT worklist is processed. If you specify a sequential data set that does exist, its disposition is set to SHR and any existing data in the data set is overwritten.

      For more information about the diagnostic output, see To review the diagnostic output.

  6. Select the method of executing the worklist. For more information about worklists, see Viewing-the-execution-status-of-a-task-ID.
    • Initial indicates that this is the initial processing job for the CM/PILOT worklist.
    • Restart indicates that this is a restart of the processing job for the CM/PILOT worklist. The initial job had previously failed and is being restarted from a sync point.
    • Start Over indicates that this CM/PILOT worklist processing job is being started over from the beginning. The job either previously failed and you have determined that it cannot be restarted from a sync point, or you want to reuse the Task ID.

  7. To override the options that are set in Change Manager to process the CM/PILOT worklist, type S to select Override 

    Change Manager

     options and then press Enter.

  8. On the Override Change Manager Options panel, select Override 

    Change Manager

     Options.

  9. Type S to select the options that you want to override, and press Enter.For more information about overriding the options, see Getting-started.

    Warning

    We do not recommend that you select the Autosubmit override option. This powerful option automatically submits the JCL, which is created from the CM/PILOT generated worklist to Execution. When you use the Autosubmit override option, use caution because any error in your specifications might cause significant damage to your schemas and a loss of data.

  10. Press END until the TASKID Interface panel is displayed.
  11. On the TASKID Interface panel, type S to select Create Worklist. Then, press Enter.

  12. On the Step Settings panel, type S to select the steps in the script that you want to modify, and press Enter.The subsequent Step Settings panels that are displayed vary depending on the script used for the task ID.

    Important

    A maximum of two settings are shown for each step on the Step Settings panel. Additional settings that you can modify on subsequent panels for each step might exist.

    The panels that might be displayed enable you to specify

    • The scope for a catalog to catalog comparison
    • Outbound and inbound migrate profiles
    • Baseline profiles
    • Baseline names for new baselines that will be created
    • Baseline names for existing baselines that will be used
    • Work ID to use in a work ID comparison
    • Data set sizing

    If a script requires profiles, and the profiles are defined in the application that the task ID is using, the profile names appear on the appropriate panels. You can change the profile names if necessary.

    After the Step Settings panels are displayed, the Change Manager Datasets panel is displayed.

  13. Specify the data set names to contain items such as the Analysis worklist, the Execution JCL for processing the Analysis worklist, and the CDL file.

    Important

    The data sets that are shown vary, depending on the script that is used for the task ID.

  14. Press END.
  15. On the TASKID Interface panel, select your options for processing the worklist.

    1. To edit the worklist, type S to select Edit Worklist.

      Important

      In columns 73 through 80 of the last line of each command in the CM/PILOT worklist, a hash verification number exists. CM/PILOT uses the number for diagnostics to detect changed commands and inserted commands. Do not modify this number.

    2. To create the JCL for processing the CM/PILOT worklist, type S to select Create JCL.
    3. To review or modify the JCL, type S to select Edit JCL.
    4. To submit the JCL to process the CM/PILOT worklist, type S to select Submit JCL.
    5. Press Enter.

  16. Execute the Analysis worklist. For more information about executing Analysis worklists, see Restarting-a-worklist or Executing-an-alter-type-worklist.

    Important

    The JCL that you use to execute the Analysis worklist is contained in the data set that you specified for JCL Dataset Name in the Change Manager Datasets panel.

    Tip

    Consider the following items when you execute a task ID:

    • You can view the execution status of a task ID by issuing the VIEW command-line command from the TASKID Interface panel.
    • If you directed the diagnostic output to a sequential data set, you can browse it from the TASKID Interface panel by issuing the BROWSE command-line command.

To create a multi-step job

You can create additional job steps in the Execution JCL that is created to process the Analysis worklist. Such steps include creating a baseline and performing a comparison before or after Analysis worklist processing. For example, updates, establishing recovery points, and generating change records can be combined into one job.

  1. On the Step Settings panel, specify additional job steps by selecting to modify the step settings for the Execution step.
  2. Select Specify additional steps to include in job.

  3. On the Execution Pre- and Post-Processing Interface panel, specify the additional steps, which is shown in the following figure. You are prompted for additional information on subsequent panels, depending on the job steps that you choose.For more information, see Generating-a-multi-step-job.

    ACMFEXC1 ---------- Execution Pre- and Post-Processing Interface --------------
    Command ===>                                                                   
                                                                                  
    WORKID . . . . . : RDACRJ.ALT04                                                
    Specify additional steps to be included in this job.  Then press Enter.        
    Pre-Execution Compare                                                          
    1 1. Do not do a compare before execution                                      
      2. Compare two previous baselines                                            
      3. Compare a previous baseline to the current catalog                        
    Pre-Execution Baseline                                                         
    1 1. Do not build a baseline before execution                                  
      2. Build a baseline before execution                                         
                                                                                  
    Post-Execution Compare                                                         
    1 1. Do not do a compare after execution                                       
      2. Compare a previous baseline to the new catalog structures                 
      3. Compare the baseline built during a previous job step to the new          
            catalog structures                                                     
      4. Create CDL to fall back to a previous baseline
    Post-Execution Baseline                                                        
    1 1. Do not build a baseline after execution                                   
      2. Build a baseline after execution
    Commands: HELP PREVIOUS END

To reuse a task ID

If you use a script to perform a change management task repeatedly, you can reuse the same task ID each time.

When you execute the task ID, use one of the following options:

  • Create a new work ID by changing the work ID name on the TASKID Interface panel.
  • Reuse the existing work ID by leaving the work ID name as it is displayed.

Important

When you reuse a work ID, the change definition (CD) table entries for the existing work ID are deleted before the new work ID is created.

You can only reuse a work ID with those scripts that create a new work ID. You cannot reuse a work ID with the following scripts:

  • Change Data Structures Using an Existing Work ID (WKID_STRUCTURE_CHG)
  • Migrate Data Structures Using an Existing Work ID (WKID_MIGRATE)

To review the diagnostic output

The CM/PILOT component provides diagnostic output in the AEXPRINT file. The diagnostic output contains information about the processing of a CM/PILOT worklist. If the Task ID contains DML, the diagnostic output includes a DML report.

On the TASKID Interface panel, you can specify your choice to direct the diagnostic output to SYSOUT or to a sequential data set.Diagnostic output from the Change Manager Execution job that processes the Change Manager worklist is also placed in the AEXPRINT file. For more information about the Change Manager diagnostics that the Execution component provides, see Review-of-Analysis-results or Outputs-of-change-results.

Viewing the DML Report

The DML report that is included as part of the CM/PILOT diagnostic output contains information about the data structures that are affected by the DML statements. You can view this report and evaluate the changes before you execute the changes. You can also determine which data structures are affected by accessing the Change Manager Worklist Specification, which marks the affected objects as Changed.

If you want to produce a DML report without creating an Analysis worklist, you can create a trial DML report.

  1. To create a trial DML report, select to change the Analysis step options when you create the CM/PILOT worklist.

  2. Select the option to produce a trial DML report.CM/PILOT worklist will contain only the necessary commands to produce the report. If the results of the report are not what you intended, edit the WHERE clause in the DML statement to narrow the scope. If you want to execute the task ID after creating a trial DML report, you must re-create the CM/PILOT worklist.

    Important

    Although the Analysis worklist is not created when you create a trial report, Change Manager updates the CD tables for the work ID.

    The DML report contains the following sections: summary, DML, and detail.

    Section

    Description

    Summary section

    The summary section of the report provides the data structures that are affected by each type of DML statement in the Task ID. For example, this section shows how many table spaces and other data structures would be affected by an UPDATE TABLESPACES statement.

    DML section

    The DML section of the report provides the actual DML statements, with statement numbers, for a Task ID. The statement numbers are referenced by any problems that are listed in the WARNING, ERRORS and CONFLICTS DETECTED subsections. The following list describes warning conditions, error conditions, and conflicts:

    • A warning condition occurs when the results of DML statement actions might be different than the anticipated results. A Change Manager worklist is created.
    • An error condition denotes a problem that you must correct before a Change Manager worklist is created.
    • A conflict occurs when two or more statements assign conflicting values to an object.

    Detail section

    The detail section of the DML report provides a detailed listing of the UPDATE, DELETE, and MIGRATE statements for a Task ID. This information provides the old and new values of the attributes that are being updated.

    Important

    If no changes are made to the LABEL attribute of tables, views, columns, and aliases, the LABEL attribute is not shown in the report. This omission enhances the readability of the report.

Related topic

Using-task-IDs

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*