PRODUKTE FALLSTUDIEN LEISTUNGEN JOBS KONTAKT IMPRESSUM MEETINGS
DE  |  ENGLISH       
DB2 - Produkte System / z/OS Anwendungsentwicklung Rechenzentrum

 
TUC
 




Key benefits:
  • Generates utility statements intelligently.
  • Executes utilities only when needed.
  • Decrease resources usage and minimizes costs.
  • Ensures all objects are covered.
  • Removes possibility for human errors.
  • Allows handling exceptions only.
  • Uniforms processing.
  • Provides a single point of control.
  • Balances workload.
  • Improves security.







Profile features:
  • Group objects for processing.
  • Utility statements generated for all objects and are ready for use before execution.
  • Statements refreshed automatically when a new object is created.
  • Utility options defined per profile.
  • Jobs generated for all utilities.
  • Profiles created automatically for any new database.


















Recovery features:
  • Recover to any event.
  • Recover a single table of a multi table tablespace to a point in time.
  • Recover an entire volume.
  • Recover dependent objects.
  • Recover to a unit of recovery based on DSN1LOGP output.
  • Recover dropped objects or copy any source datasets using DSN1COPY.



Unique features:
  • Manage Reorg Discard Conditions.
  • Create exceptions tables for CHECK DELETE automatically.
  • Calculate space based on estimated rows per table.
  • Manage compression.
  • Edit and sort unload datasets.
  • Generate MODIFY statements to retain last image copies.

Policy Features:
  • Define rules to qualify objects using Real Time Statistics and catalog tables.
  • Define Thresholds to specific objects.
  • Exclude objects from policy coverage.
  • Enforce policy rules to trigger the execution of utilities.
  • Build dynamic profile including all candidate objects qualified for utility execution.
  • Order immediate execution of jobs to process selected candidate objects.
  • Display selected candidates to fine tune your rules and thresholds.
 
TUC - Total Utility Control for DB2 z/OS

Overview
Total Utility Control for DB2 z/OS provides features and services that allow you to create a set of maintenance procedures and define the rules needed to follow your maintenance policy. Maintenance tasks might include backing up your data, collecting statistics, REORGing your data or recovering data when needed. Each task might have different requirements and rules.

Customization options allow you to set up your environment options and utility skeletons once and then have your utility statements generated automatically for all your DB2 objects using Profiles. Jobs to run utilities for profiles are tailored automatically using job skeletons. You can balance your workload by splitting profiles and have multiple jobs running at the same time to process all profile objects faster. Policy rules and thresholds define which utility jobs should be triggered for execution.

Real Time Statistics (RTS) is monitored and compared to predefined thresholds to trigger utility execution and provide near real-time utility maintenance on an as needed basis. Total Utility Control saves resources and minimizes costs by assuring that only the utilities that really need to be done are triggered for execution.

Total Utility Control comes with a default set up of rules, skeletons and procedures that allow you to easily make changes and adjust it to your needs. You can also map your existing maintenance jobs and procedures and have the product use these jobs when a utility job is triggered for execution.

Includes support for all IBM DB2 utilities BMC utilities and BMC log master. You can define different utility options for each profile. Support is provided for utilities from other vendors as well. All options are supported. TUC automates the deployment of the 'right tool for each task'.

Generate utility statements
DB2 objects are grouped in profiles to allow the objects to be processed at the same time. Utility statements and jobs are generated for all objects in profile scope. You may use generic notations to include objects in a profile. Utility statements are refreshed automatically whenever an object is dropped or a new object is created. Skeletons are used to control how a statement should look like. Global and local utility options can be assigned for each profile.

Image



Ensure recoverability
Make sure that all your objects are recoverable by letting TUC manage your backups intelligently. Full and incremental image copies are taken only when needed. When using incremental copies, you need to make sure that you have your last full image copy always available. TUC identifies when exactly you need to take a full image copy and helps you save space and resources. To ensure that every syncpoint taken is recoverable, TUC checks for non recoverable events. A new backup is taken automatically if an event such as LOAD REPLACE took place after the last backup. Syncpoints are recorded with a meaningful name, assigned by your application, to allow you to easily identify the log point you wish to recover to. TUC recovery services dialogs allow you to easily generate your recovery statements for any group of objects. You can recover an entire database, specific tablespaces, specific tables or an entire volume. You can also use DSN1COPY to recover data using image copies that are no longer recorded in the DB2 catalog. Internal ids translation tables are automatically generated.




Improve Performance
To better manage your allocated space, you can estimate the maximum number of expected rows for each table. Statistics is collected to determine the actual high water mark number of rows. TUC calculates space using the provided estimations and alters space allocation prior to reorg. The reorg preparation steps also include automatic creation of online reorg mapping tables. TUC manages the purging of old data from your DB2 tables to allow you to improve performance by keeping only the data you need in your tables. You can define the discard conditions for each table and have the appropriate reorg discard statements generated for each tablespace. CHECK DELETE can also be used to remove dependent rows from discarded tables. Exceptions tables for all dependent tables are created automatically in a special exceptions database. Exception tables can also be dropped automatically when empty or when expired. You can rebind all dependent packages following reorg to allow the DB2 optimizer to select the best access path for your applications.




Trigger execution
DB2 collects Real Time Statistics that can be used to identify the rate of changes since the last COPY or REORG. TUC allows you to define policy rules to qualify objects for utility execution based on Real Time Statistics and catalog tables. Utility jobs can be automatically triggered and handed over to a scheduler for immediate execution. The jobs process only the objects that were selected by policy rules. Objects can be excluded from policy coverage.

Image


Recovery
There could be many different recovery scenarios and you can never know which objects and to which event you would need to recover to. That is why it is important to have a friendly interface that allows you to select the objects and the events for recovery. TUC provides many options to tailor your recovery processing for every possible scenario.

DSN1LOGP and PIT Backout for Application Testing
The DSN1LOGP utility allows you to format log pages and search for recovery events and changes made by the application. The volume of the output is huge and it becomes difficult to identify what you are looking for. TUC analyzes the output and provides an interface that allows the user to easily group objects related to a single unit of recovery, identify the sync points taken before or after the event and allow you to recover the entire group of objects to the desired point in time. This way if an application program completed successfully, committing changes that corrupted the data, and you wish to backout these changes, you can easily identify the recovery log point.

Check lost IC
Image copy datasets can be deleted by mistake or expire. The recording in the DB2 catalog not always reflect your current datasets inventory. You do not want to find out that you have a missing image copy dataset when you attempt to recover. TUC verifies that the last image copy for every object is available and the object is recoverable. Objects with missing image copy datasets are automatically copied.

Avoiding RUNSTATS
Statistics collected with RUNSTATS is used by the DB2 optimizer but has been traditionally used also to determine which objects require REORG. Since Real Time Statistics was introduced in DB2 version 7 it may no longer be necessary to use the catalog statistics to base these decisions. Collecting statistics with RUNSTATS is expensive and many resources can be saved by avoiding running RUNSTATS. TUC is using real time statistics to trigger REORG execution. In addition, only the objects that require processing are processed.

Operational Advantage
DB2 places objects in a restrictive status to prevent users from accessing inconsistent data or make changes to unrecoverable data. Any application attempting to do so fails. It is important to resolve restricted statuses and make data available as soon as possible. TUC allows you to respond quickly by allowing you to trigger execution or manually tailor jobs to COPY objects in COPY pending, remove exceptions from tables in CHECK pending or recover objects in recovery pending status.

Workload balancing with up to 35 parallel jobs
A DB2 database can include thousands of tablespaces and a single tablespace could have thousands of partitions. With so many objects, it makes sense to exploit parallelism and split the work to multiple jobs running at the same time each processing a subgroup of the objects. TUC features allow you to easily name your jobs to support parallel execution and automatically balance the objects so that each job will process a subgroup of the objects that are at about the same total size.

Security
Running DB2 utilities requires skill and knowledge. The user must be familiar with the different utility options and how they affect the execution, allocate sufficient work space for processing of large objects, use the correct naming conventions, how to restart in case of a failure and how to avoid data corruption and loss. In many cases, administrators simply avoid granting users from using utilities. Instead developers end up with writing programs to INSERT or DELETE data instead of using LOAD or REORG DISCARD. TUC provides a mechanism that allows users to place a request for utility processing and receive a signal when the processing has completed successfully. This way the responsibility and the control stays in the hands of the administrator but the users can exploit the power of utilities. Requests are recorded for auditing and workload balancing.

Performance
It is important to run the DB2 maintenance regularly and periodically as appose to doing that only when you have a performance problem. Collect statistics when the volume of data has dramatically increased or decreased to allow the optimized to choose the best access path for your application. REORG your data when the rate of changes since the last reorg is high to avoid scanning of data because of poor clustering or lack of free space. Purge old data from your tables to keep your tables small and easy to maintain. TUC provides all the services you need to set up maintenance procedures automatically and avoid ending up with poor performance.

 
 
 
 
 
Go to Top