Maintenance tasks may include log analysis to audit changes on critical tables. TUC online dialogs allow the user to generate log analysis jobs for specific objects and specific logs.
Processing log analysis requests
The DB2 logs record updates on tables for the entire DB2 subsystem. If you allow users to access the information on the logs, you basically expose the data in all tables. To protect your data you need to prevent read access to the logs but that creates a problem when log analysis is required. TUC has a unique mechanism that allows users to place a request for object processing, including log analysis. The user needs authorization to place a request but does not need direct authorization to process the objects. The user can then place a request to scan the logs for a group of objects without having read access to the DB2 logs. The request is processed automatically by TUC and jobs can be handed over to the scheduler as needed. When the request completes successfully, the user can access the desired outputs. This leaves the responsibility and control of the operation in the hands of the administrators.
Display log inventory
TUC allows you to display the log map inventory for a limited number of days or logs. TUC accesses the BSDS directly to allow you to quickly display only the relevant information. The displayed list of logs allows you to generate jobs to analyze the logs using ULT or DSN1LOGP. You can issue commands to offload the active logs or display the logging status.
Displaying log durations
TUC allows you to display the duration of all of your active logs and archive logs. Since the rate of logging can be sometimes high, it is important to monitor and see how long you keep your updates in the logs, increase the size or number of your active logs if necessary or increase the retention of your archive logs. TUC analyzes the log duration of all members of the data sharing group and allows you to identify the member with the shortest logging duration that may affect the entire group.
Rebuilding the BSDS
Renaming BSDS or active logs might be needed when you implement data sharing or when you wish to bring up your subsystem on disaster recovery site. TUC allows you to rename current active logs, archive logs and BSDS datasets. The new names are reregistered in the new BSDS datasets. You can generate the batch job to reregister logs in batch or online. The generated JCL allows you to take the following steps:
- Take a backup for the current BSDS datasets
- Rename BSDS datasets
- Rename active logs
- Rename archive logs allocated on DASD
- Alter the SHAREOPTIONS of the active logs to enable data sharing
- Remove archive logs that no longer exist using DSNJU003 DELETE
- Remove old names of active and archive logs before rename
- Reregister active and archive logs with new names using DSNJU003 NEWLOG