Saving a change command script for offline scheduling

You can save your generated change commands to a script that is compatible for being run directly from a data server. You can run the saved scripts or schedule them to run in batches on the server through the DB2® Command Line Processor (CLP) shell interface.

Before you begin

The change management script must be open in the Change Management Script Editor, and you must have generated the change commands.

Procedure

To save the commands in a script that can be run directly from the data server, complete the following steps:

  1. In the Commands section of the Change Management Script Editor, click Save. The commands that will be saved are displayed in the Save the Commands to a Script window. The commands are modified as needed so that they can be run from the data server.
  2. Optional: Edit the commands, including any comments that have been inserted.
  3. Specify the file name, path, and location for saving the script. You can save the script to the data server file system, which might be remote, or to the local file system.
    Tip: The Secure Shell (SSH) protocol must be set up to browse for and save files to a remote server on a Windows® operating system. If this protocol is not set up, you can save the script to the local server and then manually transfer the file by using a file transfer mechanism, such as FTP.

Results

You can use the same technique to save undo change commands to a script that can be run from a data server. After a change command script has been deployed successfully, click Save Undo in the Messages section of the Change Management Script Editor. The commands are displayed in the Save the Commands to a Script window.

What to do next

The saved scripts are ready to be run or scheduled to run.

Feedback