After upgrading to r19 of Sysview Performance Management Option for DB2 for z/OS (IDB2), why is my billing program that reads the IDB2 history data encountering S0C4-11 abends?

book

Article ID: 7389

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

A custom program was written to capture the Sysview Performance Management Option for DB2 for z/OS (IDB2) history data in SMF format for IMS billing.  

After IDB2 was upgraded to r19,  the program started encountering S0C4-11 abends.   

Cause

This adhoc program was developed a few years back and was not designed to handle SMF records in compressed format.  

 

Environment

CA DB2 Tools' r19 (including the application of ptf RO91442)

Resolution

With the application of ptf RO91442 in r19, the ability to unload and retain SMF compressed records during the history unload process became available.

This process is controlled with the 'CMP=' parameter on the IDB2 Unload job (CMP=YES is the default if not specified).

To alleviate the S0C4-11 abends when reading the compressed SMF unloaded history records, the parameter CMP=NO needed to be added to the IDB2

Unload job's execution parameters.