Adding active logs

You can use OPERTUNE to add one of the following types of log data sets:

• Single copy 1 log data set
• Single copy 2 log data set
• Copy 1–copy 2 pair

OPERTUNE provides a utility to copy archive log data into a predefined VSAM data set that can be used as the active log to be added. The JCL to execute the utility is found in the DDTKLOGU member of the OPERTUNE CNTL data set. For more information about the Copy Log utility, see Adding an archive log to the active list.

Consider the following before adding active logs:

• You must add a log to a member subsystem in the Db2 data sharing group, not a Db2 data sharing group.
• You must create the log data sets with the proper attributes before you add the data set, or dynamic allocation errors will result. You can use the MODIFY parameter to already-created log data sets (see Step 5 in Add-active-logs), or you can create them separately (see Creating-active-logs).
• If you are adding active logs after receiving a DSNJ111E OUT OF SPACE IN ACTIVE LOG DATA SETS message from the Db2 subsystem, you must reply to any outstanding DSNJ008E messages for the Db2 subsystem to use the new active logs.
• If the subsystem is running in dual logging mode, the copy 2 log data set (if specified) is allocated and ready for logging; otherwise, the copy 2 log data set is added to the bootstrap data set (BSDS) with no allocation attempt. Data sets added by OPERTUNE are marked new and reusable unless the LIKE parameter is used.
• The copy 1 BSDS data set is updated to reflect the addition of the new logs. The copy 2 BSDS data set is updated only if the subsystem is running in dual BSDS mode.
• If you use OPERTUNE to add logs into positions other than first or last, ensure that the subsystem is not cycled before the newly added logs have been used. During initialization, Db2 re-chains the logs in RBA sequence, placing new, unused logs into the chain immediately following the currently used log. This re-chaining does not cause an operational problem but causes the logs to be logically chained and, therefore, written in an order other than the physical order of the logs in the BSDS.
• Print Log Map DSNJU004 always prints logs in RBA sequence. OPERTUNE displays active logs in the physical sequence in which they reside in the BSDS.

This section contains the following topics: