After resetting log RBAs to zero in a non-Data Sharing DB2 environment are there any requirements for CA Log Analyzer for DB2 for z/OS?

Products

• RC Compare for DB2 for z/OS
• 24X7 High-Availability Manager for DB2 for z/OS
• Batch Processor
• Compile QQF
• Data Compressor for DB2 for z/OS
• CA Unicenter NSM
• RC/Update for DB2 for z/OS
• DB2 TOOLS- DATABASE MISC
• Database Analyzer for DB2 for z/OS
• Fast Unload for DB2 for z/OS
• Fast Check for DB2 for z/OS
• Fast Index for DB2 for z/OS
• Rapid Reorg for DB2 for z/OS

Issue/Introduction

Description:

After resetting the log RBAs to zero on a non-Data Sharing DB2 subsystem, are there any requirements to have CA Log Analyzer for DB2 for z/OS (PLA) execute with the reset RBA values?

Solution:

After following IBM's instructions for resetting the log RBAs to zero, create a new ENABLExx member in your highlvl.CDBAPARM (if not already present). Specify the reset RBA timestamp that is recorded in the MASTER log or use the value returned from running a DSNJU004 (use the timestamp of the first ARCHIVE Log after reset) representing when the RBA reset occurred.

Example of entry within ENABLExx member:

PLA-SSID-RBA-RESET-TS (2013-03-24-18.22.00.000000)

If executing PLA under the r15 release please make certain PTF RO37387 is applied. This maintenance is incorporated into higher releases of PLA.

Environment

Release:
Component: PLA