New DB2 Universal Database for OS/390 functions have been incorporated into the Control Center.
The Generate DDL function allows the user to selectively generate the DDL statements used to create database objects and optionally, dependent objects. As an example, a user can request that the DDL be generated for a table, including all its indexes and all views based on the table. The generated statements can then be saved either on OS/390 as a data set or in a local workstation file. When running Control Center as an applet, the workstation file resides on the Web server. See the Control Center Online Help for more information.
The Control Center gives you the ability to restart OS/390 utilities that have stopped. Any utilities whose status is active or stopped can be displayed using the display utility command. Utilities whose status is stopped can be restarted. There are two ways to restart utilities: from the last committed point (Current) or the last committed phase (Phase). Stopped utilities that were not started from Command Center cannot be restarted.
Each time a utility is run, a Utility ID is generated. In Version 7, you can modify the ID generated by the Control Center, and replace it with a default Utility ID that the user can specify on the Tools Settings window.
After a utility has been run, you may need to delete or rename the data sets that remain. You can use the Command Center's new OS/390 DATASET object to manage these data sets.
You can use wildcards and dynamic allocation to develop DB2 for OS/390 utility control statements to manage a large number of database objects. Utilities have the ability to dynamically build lists of database objects and dynamically allocate the data sets that they use or produce. LIST, TEMPLATE, and JOB STEP objects have been added to the Control Center in support of DB2 for OS/390.
See the Control Center Online Help for more information on OS/390 utility support.