BMC Software, Inc., Confidential and Proprietary Information
7-4 Administrative Products for DB2 Installation Guide
Overview
The dialog for two of the Scripts helps you create SQL-like data
manipulation language (DML) statements to change (update and delete
capabilities) and to migrate data structures. You can also modify the DML
statements in an ISPF edit session provided by CM/P. Using DML gives you
functions similar to the CHANGE MANAGER Specification component,
except you can change or migrate multiple data structures in a single DML
statement.
Three of the Scripts use triggers, which are conditions that result in the
remaining Script steps being executed if the trigger condition is true. For the
Compare trigger, you specify the trigger in the form of a comparison. For the
DML triggers, you specify the triggers in the
WHERE clause of the DML
statement.
The information that you provide through the CM/PILOT dialog is stored in
a Task ID, which is a unit of work with a unique identifier. CM/PILOT
provides the dialog for the creation and maintenance tasks that are associated
with Task IDs. You can also reuse Task IDs for change management jobs that
you run repeatedly.
CM/PILOT Applications
You can associate a group of CHANGE MANAGER profiles that will be
used repeatedly for the change management tasks of a specific DB2
application. This feature is called a CM/PILOT Application. You can also
define a Work ID name template in a CM/PILOT Application, which lets you
standardize naming conventions for CHANGE MANAGER Work IDs that
CM/PILOT creates. There is no limit to the number of Task IDs that can use
a CM/PILOT Application.
CM/PILOT Worklists
A CM/PILOT worklist, which contains commands for CHANGE
MANAGER components, is created when you execute a Task ID. The
worklist passes the information that you provide through the CM/PILOT
dialog. The JCL for processing the CM/PILOT worklist can also be created
for you at the same time.
The successful processing of a CM/PILOT worklist results in the creation of
a CHANGE MANAGER worklist, along with the associated CHANGE
MANAGER Execution JCL to process it. You can then submit the Execution
JCL for CHANGE MANAGER worklist processing whenever you like,
thereby allowing you to schedule the jobs that actually perform the data
structure changes and migrations. Actual data structure changes and
migrations occur only when the CHANGE MANAGER worklist is
processed.
