What would cause error message LAE0058E DB2/BSDS LEVEL ERROR for a bootstrap dataset related to a member that is no longer active when executing CA Log Analyzer for DB2 for z/OS?

Products

• 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

Issue/Introduction

Question:

What would cause error message LAE0058E DB2/BSDS LEVEL ERROR for a bootstrap dataset related to a member that is no longer active when executing
CA Log Analyzer for DB2 for z/OS (PLA)?

 

Answer:

When executing a DML activity report, PLA falls into logic looking for the BSDS from a DB2 Data Sharing member which has been quiesced or (deactivated) some time ago under an older release of DB2.  A -DISPLAY GROUP will display which member is quiesced.

The following error is returned: LAE0058E DB2/BSDS LEVEL ERROR

IBM recommends deleting the BSDS datasets in order to properly quiesce those deactivated data sharing members. However, if you would like the ability to activate that member in the future, simply renaming the BSDS datasets has the same effect yet allowing the ease of reactivating those members in the future. Either the deletion or rename of the BSDS datasets for permanently quiesced DB2 data sharing members will resolve the problem where PLA fails with error message LAE0058E.

Environment

Release:
Component: PLA