By Sharon Roeder and Ariana Bibiano
Starting in function level 508 of Db2 13 for z/OS, system administrators can increase the maximum number of active and archive logs in the bootstrap data set (BSDS). The maximum number of active log data sets is increased to 1,000 per log copy and the maximum number of archive log data sets is increased to 14,500 per log copy.
Before the availability of this new capability, the maximum number of active log data sets was 93 per log copy and the maximum number of archive log data sets was 10,000 per log copy. With Db2 13 function level 508, this enhancement improves the scalability of log data by increasing the maximum amount of active log data sets to allow for 24–48 hours of active log data. This capability is especially useful in replication or backup and recovery scenarios to avoid the need to access archive log data sets.
The new DSNJCNVU stand-alone conversion utility converts the BSDS by formatting additional records so that it can support the new maximum values of active and archive log data sets. The DSNJCNVU utility only needs to be run for a Db2 subsystem or data sharing member that was installed in version 11 or later. Any Db2 subsystem or data sharing member that was migrated to Db2 13 from version 10 or earlier already has a BSDS that is large enough to accommodate the new maximum active and archive log data sets.
You can run the DSNJU004 (print log map) utility against the BSDS to determine if the DSNJCNVU conversion utility needs to be run. If the DSNJU004 utility indicates that the DSNJCNVU conversion utility was not run, this means that the BSDS is not large enough and DSNJCNVU needs to be run to support the new maximum values.
For more information about this new capability, see:
#Db2forz/OS