Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Global options

The global options apply to all archive log data sets processed concurrently by PACLOG.

The following figure shows the syntax diagram for the global options:

Following are descriptions for the global options and their parameters.

OptionDescription
LIMIT

Specifies the limits to be used by PACLOG when searching for original archive log data sets to process.

You can express the limit as a number of hours, a number of logs, or a relative byte address (RBA) range. If you do not specify LIMIT, PACLOG uses the entries in the DB2 bootstrap data set (BSDS) and the BMC archive history file to determine those original archive log data sets that have not yet been processed and then processes those log data sets.

You can also use the LIMIT option when reprocessing archive log data sets that have already been processed, that is, when you use the REDO option (see Archive copy specification). The limit you specify applies to all archive log data sets being processed. For more information about using the LIMIT option, see Recommended archive log processing practices and Deciding which logs to process.

ValueDescription
LIMIT HOURS nLimits the number of original log data sets that have been selected for processing to those covering the last n hours. The number must be in the range 1 through 999 and greater than the interval between successive PACLOG operations. LIMIT HOURS uses the end RBA timestamp in determining which process. The end RBA timestamp is based on Greenwich Mean Time (GMT).
LIMIT LOGS nSpecifies the number of original log data sets to be processed by PACLOG. Log data sets are counted backwards with the most recent archive log data set considered as the first data set. The number must be in the range of 1 through 9999.
LIMIT RBARANGE startRba endRba

Use the LIMIT RBARANGE option with start and end values (in hexadecimal notation) to specify an RBA range to be searched by PACLOG for original log data sets.

If you want to search from a specific start RBA to the current time, specify an end RBA of FFFFFFFFFFFF to ensure that the whole period is searched.

SIMULATE

Specifies the current PACLOG job is a simulation. PACLOG generates processed log data sets, but it performs no action against the original log data sets.

You can specify whether to keep or delete the processed log data sets and whether to update the BMC archive history file. If you do not specify SIMULATE, PACLOG performs processing for normal archive log data sets.

ValueDescription
UPDATEHISTSpecifies that the archive history file is to be updated. Otherwise, the archive history file is not updated.
KEEP

(SIMULATE UPDATEHIST KEEP) Specifies that the processed copies of the log data sets that have been produced by the current job should be retained and cataloged. Copies of all three files are retained: the BSDS file, the archive log file, and the archive history file.

When the copies are cataloged, copies 1 and 2 are named as follows to distinguish them from the original copies:

  • BSDS copy: prefix.Y dataSetNumber

  • Archive log copy: prefix.Z dataSetNumber

  • Archive history file: prefix.H dataSetNumber

NOKEEP

(SIMULATE UPDATEHIST NOKEEP) Specifies that the data sets produced by the current job should be deleted.

Note

If you use SIMULATE UPDATEHIST NOKEEP, the entry in the archive history file is not deleted.

DB2LOGPRODUCTIf you use a DB2 log processing product, such as the BMC Software Log Master product, use the DB2LOGPRODUCT keyword to specify that PACLOG is not to filter log records that may be needed by the log product.
Was this page helpful? Yes No Submitting... Thank you

Comments