Archive copy option descriptions
The following table describes the ARCHIVE copy option and its parameters:
Option | Description |
---|---|
ARCHIVE n | When you do not specify the REDO option, ARCHIVE n (where n = 1, 2, 3, or 4) specifies one of up to four processed copies of original log data sets. The original log data sets must be within the range specified by the LIMIT option or be indicated as unprocessed by the archive history file. The original log data sets are deleted unless this is a simulation (see Global-option-descriptions). When you specify the REDO option, PACLOG processes copies 1 and 2 of log data sets that have already been processed and found within the same range. Use ARCHIVE1 and ARCHIVE2 to create processed copies for local site use and ARCHIVE3 and ARCHIVE4 to create processed copies for recovery site use. |
PREFIX prefix | Use this option to tell PACLOG to use prefix as the high-level qualifier in the data set names for the third or fourth processed log data sets (ARCHIVE3 and ARCHIVE4). PREFIX is only valid for the third and fourth processed log data sets and provides a means of identifying these log data sets as offsite logs. PREFIX is a required option for ARCHIVE3 and ARCHIVE4. If the installation option TSTAMP is set to YES, then the prefix cannot be more than 17 characters. If TSTAMP is set to NO, then the prefix can be up to 35 characters. For information about installation options, see Installing. |
REDO | When you specify the REDO option with either ARCHIVE1 or ARCHIVE2, PACLOG processes (or reprocesses) all log data sets (original or already processed) that are found within the range that is specified by the LIMIT option. If a log data set within the range specified has already been processed and the current syntax specifies less filtering than the previous processing, PACLOG still processes the log data set, but you receive a warning message. PACLOG updates the archive history file when reprocessing is completed. For more information, see Reprocessing a processed local site archive log. Also, for a discussion of the archive history file, see the BMC-archive-history-file. |