Analyzing a change

After a change is registered, you must analyze it before you can run it. During this analyze step, Db2 Admin Tool analyzes how the change modifies existing objects and creates a work statement list (WSL) that can be used to run the change.

To analyze a change:

1. Navigate to the Changes (ADB2C11) panel by completing the following steps:
   1. On the DB2 Administration Menu (ADB2) panel, specify option CM, and press Enter.
   2. On the Change Management (CM) (ADB2C) panel, specify option 1, and press Enter.
   3. Optional: At the bottom of the Manage Changes (ADB2C1) panel, specify any search criteria to filter or limit the changes that are displayed.
   4. On the Manage Changes (ADB2C1) panel, specify option 1, and press Enter.
2. On the Changes (ADB2C11) panel, issue the AN line command for the change that you want to analyze.
3. On the Generate Analyze Job (ADB2C11A) panel, complete the following fields:

   ADB2C11A  ----------------- Generate Analyze Job  ----------------------- 21:45
   Command ===> 
    
   Specify the following for Analyze:                                            
                                                                     More:     + 
   Base version method . . . . .          (Auto, User, or Existing)
   
   Change reporting options  . . NO       (Yes/No)
   
   Required data set information:
     PDS for WSL . . . . . . . . DSNA.RUN.WSL
     PDS for analyze job   . . . DSNA.ANALYZE.JCL
     Prefix for data sets  . . . JOHNSON
     Existing data set action  . CONDITIONAL (Conditional, Prompt, Replace)
     Change tag type . . . . . . ID          (ID, Name, Owner)   
   
   Options: 
     Run SQLID . . . . . . . . .          (Blank, a SQLID, or <NONE>
     Object Grantor  . . . . .            (Blank or a SQLID) 
     Validate WSL  . . . . . . : NO       (Yes/No)
     Use utility options . . . . NO       (Yes/No)
     Generate templates  . . . . NO       (Yes/No)
     Build JCL to run WSL  . . . NO       (Yes/No)
     Generate a recover change . YES      (Yes/No)
       Data to recover . . . . . B        (Original, Existing, Both or None)
       Recover with DDL only . . NO       (Yes/No)
       PDS for recover WSL . . . DSNA.RECOVER.WSL
       PDS for recover job . . . DSNA.RECOVER.JCL
     Authorization Switch ID . .          (SQLID to connect, <SQLID>, or blank)
     SECADM Authorization ID . .          (SQLID to connect or blank)  
     Stop on conversion error. .          (Yes/No)   
     Content of apply job(s) . . ALL      (All, DDL) 
     Unload method . . . . . . . P        (Unload, Parallel unload, HPU)
     Use DEFER YES . . . . . . . YES      (Yes/No)
     Allow rotate parts  . . . . NO       (Yes/No)
     Retain GENERATED ALWAYS:
       For ROWID . . . . . . . . NO       (Yes/No)
       For ROW CHANGE TIMESTAMP. NO       (Yes/No)
     IDENTITY START value  . . . C        (Original, Computed)
     SEQUENCE RESTART value  . . C        (Original, Computed)
     Disable REORG optimization  YES      (Yes/No)
   
     Optional jobs after Reload or Alter:
       Run CHECK DATA  . . . . . NO       (Yes/No)
       Take an image copy  . . . N        (after: Reload/Alter/Both/None)
       Run REORG/REBUILD . . . . N        (Mandatory, All relevant, None)
       Run RUNSTATS  . . . . . . N        (after: Reload/Alter/Both/Min/None)
       Run REBIND  . . . . . . . A        (Mandatory, All relevant, None)    
                    
   BP - Change batch job parameters
   TU - Specify TEMPLATE usage
   UO - Change utility options
   CO - Change options common to change functions

   Base version method

   Specify the base version method that Db2 Admin Tool is to use for the comparison to generate the changes. If you specify U (User-defined), you are prompted to specify the version scope to use. If you specify E (Existing), you are prompted to specify the base version to use. For more information about how to chose this value, see Base version method for change analysis.

   Change reporting options

   Specify whether to change reporting options before submitting the analyze job. If you specify YES, you are prompted to specify the reporting options to use.

   Required data set information

   Specify information about the data sets for the generated WSL and the generated jobs.

   The value of the Change tag type option determines the PDS member names.

   Tips:

   • Keep the WSLs for Change Management changes separate from other WSLs. Do not mix them in the same data set.
   • Choose a unique naming convention for the WSL and JCL data sets such that members for other Change Management databases are not put in the same data set.

   Options

   Specify job options. The following options are some of the preferences that you can specify:

   Generate templates

   Specify whether to use active templates. If you specify Yes, templates are generated for non-utility data sets with the template definitions that are defined for Object Comparison Tool. If you specify No, the value of the Prefix for data sets option is used to name the data sets. If the Take an image copy or Run REORG options are Yes, the utility templates are used.

   Generate a recover change

   Specify whether Db2 Admin Tool is to automatically generate a change that will recover the current change. If you specify Yes, you will be prompted to register the recover change.

   Data to recover

   If Generate a recover change = Yes, specify whether you want to recover the original data, the existing data, or both. Original data is the data that exists just before the original change is run. Original data can be recovered for objects that were unloaded during the original change. Existing data is the data that exists in the table just before the original change is recovered. If you specify that you want both, you can choose which data to recover at the time of recovery. You can also choose to recover only the DDL and not the data.

   Optional jobs after Reload or Alter

   Specify any optional utility job steps.

   Recommendations:

   • If the change affects tables that are part of an RI relationship, run the CHECK DATA utility.
   • If the change is a pending ALTER operation, run the REORG utility.

   Depending on the values that you specify, you might be prompted for additional information before the analysis jobs are generated and an ISPF Edit session is displayed.

4. If the change that you are analyzing was already analyzed (the change is in ANALYZED status), specify whether to continue or cancel the analyze request when you are prompted. If you continue, the change is placed back in DEFINED status before the new analyze job is created.
5. Edit and submit the generated analyze job.
   This job performs the analysis and generates a WSL for running the change.

   When the job completes successfully, the change is placed in ANALYZED status. If the job does not complete successfully, check the error messages in the job output. Correct any errors and then reanalyze the change by issuing the AN command.

   If you requested that a recover change be generated, the recover change is created and is also placed in ANALYZED status. A delta version for the recover change is also created.

6. Press PF3 to return to the Changes (ADB2C11) panel to verify that the status of the change is ANALYZED.
   If you requested that a recover change be generated, you can verify that it is also included in the list of changes.

   Tip: If you return to the Changes (ADB2C11) panel before the submitted job completes, you can click the REFRESH command after the job completes to see the refreshed status of the change.