Automatic DSOP update for Datacom areas did not always work

Products

• Datacom
• Datacom/AD
• Datacom/DB

Issue/Introduction

According to the Datacom white paper, "Planning & Preparing for a Conversion to VSAM LDS Datasets Document (Version 3)":

At release 15.0 and above, whenever a database definition with a data area defined as DSOP 0, 1 or 2 is catalogued to the CXX, the DSOP option is automatically updated in the CXX to DSOP 4 or DSOP5.  DSOP options 4 (replaces DSOP 0 and 1) and DSOP 5 (replaces DSOP 2) provide more modern data area space management and these options are required for most data area 24x7 functionality.

This appears to work on some but not all areas. After running the catalog of my database (even twice!), the CXX report still shows the old DSOP.

Environment

z/OS

Cause

The CXX report showed the unchanged table was in "history" status, and was therefore not changed.

Resolution

A review of the CXX report showed that the area was in History status:

 AREA NAME  - xxx                                *HISTORY*

As noted in the documentation for the CXX report,

AREA NAME: DATACOM-NAME of the area.

If multiple tables exist in this area, this information is duplicated for each table. If *HISTORY* follows the name, this entry has been logically deleted but still exists to provide the ability to back up the area.

Consequently, since the tables for this area are not found in the current catalogued version of the Datadictionary entities, there is nothing here that would have its DSOP converted. The Datadictionary update run previously shows other tables and areas, and these were converted as expected. However this *HISTORY* Area and table are not available in the current cataloged version, and subsequently were not converted.

Additional Information

As always, please contact Broadcom support for Datacom if you have further questions.