Change Manager components

Most components that BMC AMI Change Manager for Db2 uses to perform its tasks can run in the foreground or as batch jobs.

Change Manager uses the following components:

  • Front End

  • Specification

  • Baseline

  • Compare

  • Import

  • Analysis

  • JCL Generation

  • Execution

  • CM/PILOT

The Specification and Analysis components provide the same functionality as they do in ALTER. For a description of these components, see ALTER components.

Change Manager Front End

In Change Manager, the Front End component can also maintain migrate and baseline profiles, and interact with the Baseline, Compare, and Import components.

Baseline component

The Baseline component captures a set of Db2 structure definitions from either the Db2 catalog, a DDL file, or a migrate worklist at a specific point in time.

The captured set of data structure definitions is called a baseline. If the structures are defined in the Db2 catalog, a baseline can also capture the data and authorizations that are associated with those structures. A baseline of both data structures and data is called a full-recovery baseline.

Baselines act as control points during data structure management. Baselines establish a static set of data structures for an application version. If you make a change with unwanted results, you can restore the data structures. If you establish a full-recovery baseline, you can also restore the data. You can also restore the data structure back to a prior baseline and convert the current data to those structures.

You can also use baselines for version comparison. For example, when you first install an application, create a baseline. At a later time, perform a comparison between the baseline and the Db2 catalog. This comparison creates a CDL file that shows any modifications that have been made to the application’s data structures since the initial installation.

Note

A baseline is also a Change Manager object.

Compare

The Compare component determines the differences between two sets of data structures and then generates a CDL file.

The generated CDL file contains all of the changes that the comparison found between the two sets of data structures. You can compare data structures that are stored in a DDL file, work ID, baseline, worklist, or Db2 catalog. The inputs to the Compare component are called the primary and secondary input sources. The CDL file contains the changes that, if applied to the primary input source, would produce the data structures of the secondary input source.

You can use the generated CDL file in any of the following ways:

  • Process the file as a set of change requests for the current subsystem

  • Save the file as a record of the changes made

  • Import the file to a different subsystem in order to update a separate version of the data structures

CDL has advantages over DDL in automating the process of updating data structures. CDL allows more types of modifications to data structures and, unlike DDL, can retain local modifications to those structures.

Change Manager Import

You can import data structures that are stored in a CDL, DDL, or DML file.

The Import component converts the data structures in the files into change requests in a work ID. Change Manager stores these change requests in the CD tables. The Import component provides a batch function similar to that provided by the Specification component with limited validation checking.

Change Manager JCL Generation

In Change Manager, the JCL Generation component also generates JCL for the Compare, Baseline, Baseline Report, and CM/PILOT components.

Change Manager Execution

When Change Manager is used in the BMC Database Administration for DB2 or BMC AMI Database Administration for Db2 solution, the Execution component can enable a worklist to execute in parallel.

That is, the component executes portions of the worklist concurrently.

For information about Database Administration or BMC AMI Database Administration, see Solution integration.

CM/PILOT

The CM/PILOT component automates Db2 change management tasks. With CM/PILOT , you do not need to decide which Change Manager processes are required for a task or the sequence in which you need to complete them—CM/PILOT provides scripts to guide you through the process.

The CM/PILOT component enables you to choose from several predefined scripts or to create your own scripts. You can copy scripts, including those that CM/PILOT provides, and modify them to meet your needs. You can also edit, browse, delete, and perform other maintenance tasks on scripts.

CM/PILOT enables you to quickly and easily use the vast change management power of Change Manager. By following the dialog panels that are provided in the CM/PILOT scripts or in the scripts that you create, you can specify, analyze, and execute an Analysis worklist to perform the following tasks:

  • Change data structures

  • Migrate data structures

  • Migrate only data

  • Receive data structure changes

  • Receive DDL to create data structures

  • Create full-recovery baselines

  • Recover data structures with current or old data

  • Select a user-defined script

  • Replicate work IDs

When you want to perform a change management task, CM/PILOT determines the components that Change Manager will use and ensures that they are run in the correct sequence. CM/PILOT enables you to create tasks that can be done later by someone else or through job scheduling. By reusing these tasks, you can ensure that the change management task is done the same way every time.

The CM/PILOT component enables you to easily prepare for various Change Manager tasks that can be processed on demand. CM/PILOT dialog panels are task oriented and easy to use. The panels guide you through the Change Manager components that are necessary to accomplish the specific tasks and prompt you for the information that is needed to build worklists that can be processed at any time.

CM/PILOT simplifies the decision-making process and enables you to prepare change management tasks that are performed repeatedly. It also lets you create change management tasks that can be performed by less-experienced DBAs. And with its unique script-locking feature, CM/PILOT lets you create script steps that cannot be modified and can only be run as you have specified.

You can also use two CM/PILOT scripts to help you create SQL-like Data Manipulation Language (DML) statements to update, delete, and migrate data structures. You can also import DML statements into an alter-type work ID. After the statements are imported, Change Manager creates entries in the CD tables as if they had been requested in the Specification component.



Was this page helpful? Yes No Submitting... Thank you

Comments