Overview

The PACLOG for DB2 product is a DB2 log management batch utility that provides substantial storage media savings while preserving the integrity of all archived log data that might be needed for recovery.

The product assists the database administrator (DBA) in determining what data is retained in archive log data sets and in choosing the archive log storage media. It also provides statistics useful in the management of archive log data sets.

For first-time users

This section provides important information that you should be familiar with before using PACLOG for the first time.

The following table outlines the key topics and the topics in this space that provide more details.

Topic

See topic

Prerequisites for using PACLOG:

  • Required operating system and DB2 environment

  • Installation requirements

  • Appropriate authorizations

Preferred settings and practices

  • Setting up the DB2 environment

  • Recommended processing practices for the archive log data set

Using the various PACLOG options for normal processing and for simulated processing

Using PACLOG to accomplish the following tasks:

  • Conserving disk space by using the PACLOG modeling tool

  • Assisting in disaster recovery

  • Providing reports that help you manage archive log data sets

Actions that you may need to take to allow log data sets that have been processed by PACLOG to be used in a recovery by some versions of the NGT Recover utility

PACLOG and NGT Recover compatibility

Information you may need to control the Extended Compression Architecture (XCA) compression subsystems in certain situations

XCA subsystem control

Benefits of PACLOG functionality

The functionality provided by the PACLOG product offers substantial time and resource savings and performance benefits, as shown in the following table.

Functionality and benefits

More information

Time and resource savings

Reduction of up to 95 percent or more in the amount of media that is required to store archive log data

Because you have control over which types of records to retain and compress, you can considerably reduce the media space that is required to store archive logs.

Potential reduction in the size and number of active logs with a corresponding reduction in the amount of DASD that is needed for them:

  • The ability to keep archive logs on DASD eliminates any need to keep large amounts of data in active logs.

  • You can use the interactive PACLOG modeling tool to calculate the optimum size for your active logs.

Increase in the time period that is covered by a given amount of media that is used for log data

More jobs access the logs concurrently when you perform a recovery using the BMC Next Generation Technology Recover for DB2 for z/OS product as the recover utility.

Recommended archive log processing practices

Reduction in the time that is required to perform a recovery when the logs are on DASD instead of tape

None

Elimination of tape mounts for log access when the logs are on DASD instead of tape

None

Reduction in the time that is needed to transmit log data over a communications network

None

Notification when an archived log data set is no longer needed, thus releasing DASD and tape for other purposes

Archive log management reports

Assistance in disaster recovery

You can make and catalog additional copies of processed archive log data sets specifically for recovery site use. You can also use PACLOG to restore these log data sets to disk at the recovery site.

PACLOG in disaster recovery

Trial processing of archive logs before disposing of the original log

You can perform simulation runs without performing any actions on the original log.

Using PACLOG to simulate log processing

Performance benefits

Allows compression of processed archive log data sets:

  • This feature reduces the amount of media required for archived logs and supports effective capacity planning.

  • PACLOG syntax provides separate compression options for disk and tape.

Compressing archive log records

Allows for the removal of unwanted log records, which further reduces the amount of media required

PACLOG provides the option to remove log data that is:

  • Not required for recovery

  • For user-specified DB2 objects

You can specify multiple filter options separately for each copy of a processed log data set.

Removing unwanted records and objects

Searches for original archive log data sets (optionally, according to user-specified limits) and meets users’ needs for scheduling flexibility

PACLOG allows retrieval of original archive logs in different ways:

  • Over a specified number of the most recent hours

  • Over a specified relative byte address (RBA) range

  • For a specified number of the most recent original logs

Deciding which logs to process

  • Concurrently creates and processes up to four copies of the original unprocessed archive log data sets

  • Allows scheduling of log data set processing to match available resources to meets users’ needs for flexibility and efficiency

PACLOG options allow any mix of up to two local site copies and up to two offsite copies.

Deciding which copies to make and when

  • Allows table space pattern matching in table space specifications

  • Provides flexibility in customizing log data set processing to meet users’ needs

PACLOG syntax lets you use wildcards with the FILTERTS option.

Removing unwanted records and objects

Allows different output device types for each copy of the processed archive log data set

PACLOG provides flexibility and efficiency and optimizes media usage by:

  • Writing processed copy 1 to disk

  • Allowing either tape or disk for each of the other copies

  • Allowing copies to be stacked to tape

Choosing the output medium

While processing an archived log data set, gathers and reports information useful for log management

This feature facilitates administrative decision making by providing management reports that:

  • Report which archive log data sets were processed

  • List any archive log data sets that have expired

  • Provide filtered and unfiltered record statistics

Archive log management reports

Allows report output to be used by other tools

This feature facilitates integration with other technology by allowing customization of the interface between PACLOG and your tool.

Archive log management reports

Allows reprocessing of previously processed log data sets

This feature provides maximum media savings over a wide range of environments by allowing (for example) reprocessing to remove previously uncommitted transactions.

Reprocessing a processed local site archive log

Allows simulated processing of original archive log data sets

You can create processed log data sets without taking any action against original log data sets. This enables you to evaluate the PACLOG product without disrupting production work. You have flexibility in simulation because PACLOG allows several levels of process simulation.

Using PACLOG to simulate log processing

Uses dynamic data set allocation for both original and processed log data sets

Increase productivity by simplifying the generation of PACLOG JCL.

Specifying the PACLOG data set DD statements

Compatible with both IBM and BMC Software recovery utilities

You can use the processed logs in a recovery using either the IBM DB2 RECOVER or the NGT Recover utility.

Was this page helpful? Yes No Submitting... Thank you

Comments