TUC – TOTAL UTILITY CONTROL FOR DB2 Z/OS
Release Dependent Features
Version 2 Release 2
Table of Content
1
Release Dependent Features.........................................................................................................2
1.1 Deployment ............................................................................................................................................2
1.2 Real Time Statistics................................................................................................................................2
1.3 New Object Types, New Data Types......................................................................................................2
1.4 Implicit databases...................................................................................................................................3
1.5 Online REORG .......................................................................................................................................3
1.6 Clone Tables ..........................................................................................................................................3
1.7 Suppressing logging ...............................................................................................................................3
1.8 More flexibility with partitions..................................................................................................................4
1.9 Distribution statistics and histograms .....................................................................................................4
1.10 Backing up and restoring the system ...................................................................................................4
1.11 COPY and RECOVER tape parallelism ...............................................................................................4
1.12 RESTART.............................................................................................................................................5
1.13 Long names..........................................................................................................................................5
1.14 Unicode Catalog ...................................................................................................................................5
1.15 Reordered Row Format ........................................................................................................................5
1.16 ACCESS command ..............................................................................................................................5
1.17 Online CHECK DATA DELETE YES....................................................................................................5
1.18 DB2 Administrative Scheduler..............................................................................................................5
2
Notices.............................................................................................................................................6
1|6
© UBS Hainer GmbH
TUC – TOTAL UTILITY CONTROL FOR DB2 Z/OS
1
Release Dependent Features
Total Utility Control for DB2 allows you to easily exploit and deploy the many new features introduced
with each DB2 release to improve availability, recoverability, performance and resources utilization.
The new migration process, introduced in version 8, allows you to migrate to compatibility mode
before enabling new functionality. Total Utility Control automatically identifies the DB2 version and
mode and allows you to immediately start exploiting release dependent features. This document
describes how you can exploit and deploy these features.
1.1 Deployment
Total Utility Control tailors utility statements using ISPF skeletons. These skeletons are exposed to the
users and users may make changes to these skeletons using a friendly user interface. The interface
allows you to add new skeletons for any kind of DB2 object processing that may be required.
Skeletons are using a pre-defined list of symbols to set the different utility options for each object and
the user may add new symbols as required. This infrastructure provides a powerful tool in deploying
new functionality when you can enable or disable utility options from a single point of control. The
default setup includes definition of most of the available utility options depending on the DB2 version.
The sample skeletons include conditional statements that allow you to tailor different utility statements
for each DB2 version while using the same skeleton.
1.2 Real Time Statistics
DB2 collects information at real time that allows you to identify the volume of data in your DB2 objects
and the rate of changes since the last COPY, REORG or statistics collection. This information can be
externalized in an interval to DB2 tables called Real Time Statistics tables. Total Utility Control allows
you to exploit this information and make intelligent decisions on utility execution using dynamic rules.
The Real Time Statistics feature was first introduced in DB2 version 7 and has become more and
more the standard tool for database administrators in selecting candidates for utility execution. In DB2
version 9 the Real Time Statistics tables have been migrated into the DB2 catalog tablespace
DSNDB06.SYSRTSTS and additional columns have been added to support instances of cloned
tables. Total Utility Control automatically identifies the correct Real Time Statistics tables to be
examined and tolerates the changes that have been made to these tables.
1.3 New Object Types, New Data Types
DB2 version 8 introduced Materialized Query Tables and DB2 version 9 introduced XML objects. Total
Utility Control provides full support in processing these objects by utilities. Support is also provided for
new data types, such as BIGINT, BINARY, VARBINARY and DECFLOAT.
2|6
© UBS Hainer GmbH
TUC – TOTAL UTILITY CONTROL FOR DB2 Z/OS
1.4 Implicit databases
Total Utility Control automatically identifies any new object created on your subsystem. That includes
implicit databases, introduced in DB2 version 9. An automatic profile is created for any new database.
These profiles are also refreshed automatically whenever a new object is created or an old object is
dropped. This way, utility statements and jobs always stay in sync with the DB2 catalog.
1.5 Online REORG
DB2 version 9 eliminates the relatively lengthy BUILD2 phase to improve availability. Total Utility
Control allows you to avoid the BUILD2 phase even prior to version 9, by automatically identifying if
the request for a reorg includes all the partitions in a partitioned tablespace and switch to object level
instead of partition level. This way the NPIs are built only once and there is no need for a BUILD2
phase.
1.6 Clone Tables
DB2 version 9 introduced clone tables that allow you to create a copy of a current table, in the same
table space, that has the same attributes, structure, and data as the original table. After you create a
clone table, you can insert or load data into the clone table and exchange the clone table name with
the current table name. Utilities have been enhanced to allow you to control the way clone tables are
processed. Total Utility Control allows you to easily deploy these options. The linear VSAM dataset
naming convention has also changed to allow representing the number of the table instance in the
tablespace.
Clone tables are fully supported in TUC version 2.2. The SYSCOPY extract includes the instance of
each image copy. Datasets mapping and relating datasets to objects record the instance. OBIDS
information is collected for all instances. EXCHANGE between base and clone table is automatically
identified. Matching datasets to objects allows matching datasets to the current base instance. The
DISDB command displays the status of base and clone tables and allows stopping and starting each.
The CLONE keyword is automatically added to STOP and START commands.
1.7 Suppressing logging
Total Utility Control automatically identifies a non-recoverable event that may cause an attempt to
recover to fail when no log information is available. An image copy is automatically triggered to ensure
recoverability. In version 9, new non-recoverable events were introduced, including suppressing
logging on a tablespace or an index. These events may trigger an image copy when attempting to
create a recoverable syncpoint using Total Utility Control services.
3|6
© UBS Hainer GmbH
TUC – TOTAL UTILITY CONTROL FOR DB2 Z/OS
1.8 More flexibility with partitions
Total Utility Control for DB2 may help you take full advantage of the partitioning benefits and exploits
the partitioning independence and parallel processing when running utilities and by that save time and
resources and provide longer availability. Prior to rebalancing your partitions, adding more partitions or
rotating your partitions you can use Total Utility Control Space Estimation feature to allocate the
projected space for each one of your partitions. Total Utility Control can balance the workload when
running utilities on your partitioned tablespace by automatically split the work into multiple jobs running
at the same time and by that speeding up your backups, reorgs and other utilities. Total Utility Control
exploits real time statistics to determine which partitions are candidates for backup, reorg or statistics
collection and save resources by running only the work that you really need to run.
1.9 Distribution statistics and histograms
Total Utility Control allows you to take advantage of the new statistics collection options. You can
easily enable the distribution statistics feature as well as collecting statistics history. Total Utility
Control also exploits real time statistics to determine which objects are candidates for statistics
collection and helps you save resources by collecting statistics only for the objects that you need to.
1.10 Backing up and restoring the system
Total Utility Control helps you assure that you have all the backups to restore your system at any time.
Services are provided to ensure recoverability of all objects. Applications may take consistency
syncpoints and name these syncpoints for use in recovery when needed. When a syncpoint is taken,
all objects are checked for non recoverable events such as LOAD REPLACE LOG NO. If a non
recoverable event was found, an image copy is taken automatically to ensure that you can always
recover your data. Total Utility Control exploits real time statistics to determine which objects you need
to backup. You can save resources by taking incremental copies. Total Utility Control helps you
manage your incremental copies by automatically identifying when the last full copy was taken and if it
is still available. Similarly the active and archive logs are also monitored to identify if updates made
since the last copy are still available in the logs and by that you can ensure that you can always
recover your data. It will also help you to identify if you need to add more active logs to your
subsystem.
1.11 COPY and RECOVER tape parallelism
Total Utility Control allows you to take advantage of the parallel processing when taking image copies
on tape or DASD. Templates management allows you to easily set your parallel processing stacking
options for all your dynamically allocated image copies. The total size of all objects is evaluated to
determine the desired set of options and allows you to conditionally backup on DASD or on tapes
depending on object size.
4|6
© UBS Hainer GmbH
TUC – TOTAL UTILITY CONTROL FOR DB2 Z/OS
1.12 RESTART
Total Utility Control takes advantage of the new RESTART feature, introduced in DB2 version 7 PTF
and version 8, by providing services that allow you to easily rerun your utility procedures.
1.13 Long names
Total Utility Control supports the new version 8 objects long names. The user interface may truncate
some of the object names. However, you can always use the REPORT primary command to generate
a report from the displayed list. Reports always show object names in full length.
1.14 Unicode Catalog
Total Utility Control supports the new version 8 UNICODE catalog tables.
1.15 Reordered Row Format
TUC version 2.2 OBIDS information records the row format of each tablespace. Different format is
identified when comparing the attributes of source datasets and target objects.
1.16 ACCESS command
TUC version 2.2 supports the new version 9 –ACCESS command that allow you to remove the group
bufferpool dependency for objects and to pre-open datasets. From the DISDB list panel you can use
the E line command to –ACCESS MODE(OPEN) an object and the N line command to Access Mode
Non-group Bufferpool Dependent.
1.17 Online CHECK DATA DELETE YES
In DB2 version 9 you can run the CHECK DATA DELETE utility in SHRLEVEL CHANGE and allow the
tables to be accessible while the CHECK is running. Then you can run the REPAIR utility in
SHRLEVEL CHANGE to DELETE all the rows that violate constraints. TUC version 2.2 provides a
utility procedure that automates the process.
1.18 DB2 Administrative Scheduler
DB2 version 9 and also DB2 version 8 (By PTF) allows you to use a built-in scheduler to schedule jobs
and stored procedures. TUC allows you to define tasks to schedule jobs and procedures and to
process pending orders by handing over jobs to the administrative scheduler. You can use the online
dialogs TASKS option to display add and remove tasks. You can also display related task from the
orders list panel to see the status of the task processing the order.
5|6
© UBS Hainer GmbH
TUC – TOTAL UTILITY CONTROL FOR DB2 Z/OS
2
Notices
Copyright 2005
All rights reserved.
IBM is a registered trademark of International Business Machines Corporation.
DB2 is a registered trademark of International Business Machines Corporation.
All other trademarks belong to their respective companies.
Information included in this documentation is considered to be proprietary and confidential. Your use
of this information is subject to the terms and conditions of the applicable license agreement for the
product and the proprietary and restricted rights notices included in this documentation.
6|6
© UBS Hainer GmbH