Comparing a baseline to a baseline

To compare a baseline to a baseline

1. On the BMC AMI Change Manager for Db2 Main Menu, select Compare (CDL Build), and press Enter.
2. On the Compare Type Selection panel, select Baseline for both the Compare1 Type and the Compare2 Type. Press Enter.
3. On the Compare Baseline to Baseline panel, specify the values for the inputs to the comparison.
   1. Type the name of the location of a catalog for Compare1. The local Db2 catalog is the default.
   2. Type the name of the baseline for Compare1 or type a wildcard pattern to display a list of baselines.
   3. Type the name of the location of a catalog for Compare2. The local Db2 catalog is the default.
   4. Type the name of the baseline for Compare2 or type a wildcard pattern to display a list of baselines.
   5. (Optional) Specify the name of an outbound migrate profile for Compare2. The outbound migrate profile must contain change rules to resolve the names of the objects and creators. Change Managerapplies the change rules to the objects in Compare2 before the comparison.
   6. Press Enter.
4. On the Compare CDL Options panel, type Y or N for each object type that you want to include in or exclude from the comparison.
5. Type S to display a list of the object attributes to include in or exclude from the comparison.
6. On the Compare Object Attributes panel, if you selected to display a list of the object attributes, specify the object attributes.
   1. To include an object attribute in the comparison, type Y adjacent to the attribute.
   2. If you specified to include the partition attributes, you can exclude one or more of the partition attributes. Type N adjacent to the attributes that you want to exclude.
   3. Press END.
7. On the Compare CDL Options panel, type S to generate comparison report information as comments in the CDL file.
8. (Optional) Specify the name of an outbound migrate profile. The outbound migrate profile can contain change rules and locations. Change Managerapplies the rules after it performs the comparison (when it generates the CDL).
9. Select a Run Type and press Enter. Be aware that specifying foreground for large comparisons might make your TSO session unavailable for a lengthy period of time.
10. On the Compare JCL Processing Interface panel, specify the data set names to be used in the comparison.
    1. (Batch run type) Type the data set name for the JCL that is generated by this process.
    2. Type the data set name for the CDL that is generated by this process.
    3. Type one of the following options for Diagnostics:
       • (foreground run type) To display the diagnostics on the terminal, type TERM.
       • To write the diagnostics to a sequential file, type the name of the data set.
       • To write the diagnostics to a print data set, type SYSOUT.
    4. (Foreground run type) If you specified SYSOUT, specify the SysoutClass.
11. Type S to select Override Compare defaults to change data set allocation parameters or to control the content of the CDL that is generated by the comparison process. Press Enter.
12. On the Compare Override Options panel, if you selected to override the defaults, specify the data set and CDL options.
    1. To specify the data set allocation parameters for new data sets, type a value for the Unitname, Volume, Priqty, or Secqty.
    2. To include CDL statements for created, altered, or dropped objects, type S to select the statements.
    3. To display, in the CDL, the change rules from an outbound migrate profile or the automatic change rules, type S for Display change rules applied to Compare2 BEFORE the Compare.
    4. Press END.
13. On the Compare JCL Processing Interface panel, select your options for the comparison.
    1. To create the input for the comparison, select one of the following options:
       • (Foreground run type) Type S to select Create Input.
       • (Batch run type) Type S to select Create JCL.

    2. To review or modify input to the comparison process, select one of the following options:

       • (Foreground run type) Type S to select Edit Input.
       • (Batch run type) Type S to select Edit JCL.

       The following figure shows an example of the ALUIN input stream.

       Press END to return to the Compare JCL Processing Interface panel.

       SSID DEBA
       CMPTYPE1 BASELINE
       CMPIN1 RDACRJ.BLUNLD200704240001
       LOCATION1 DEBA
       CMPTYPE2 BASELINE
       CMPIN2 RDACRJ.BLUNLD200704240002
       LOCATION2 DEAH
       INCLUDE (ALTER CREATE DROP )
       NODEFINE

    3. To run the comparison, select one of the following options:

       • (Foreground run type) Type S to select Run Compare.
       • (Batch run type) Type S to select Submit JCL.

       Change Managergenerates a CDL file and a diagnostic output file.

    4. To edit the CDL file that is generated by the comparison, type S to select Edit CDL File.

       Warning

       Do not attempt to edit the CDL file while the comparison is in progress, or the file will be locked, and the Compare component will not be able to access it.

    5. Press Enter.

Where to go from here

After you have compared your data structures and have generated a CDL file, you can import the CDL file to an alter-type work ID and process it as a set of change requests for a subsystem.