Chapter 34. Catalog Manipulation Utilities

< Day Day Up >

Chapter 34. Catalog Manipulation Utilities

IN THIS CHAPTER

The CATENFM Utility
The CATMAINT Utility
The DSNJCNVB Utility
The MODIFY Utility
The RUNSTATS Utility
The STOSPACE Utility

The DB2 Catalog and the DB2 Directory are essential to the continuing performance of your DB2 subsystem. This chapter discusses several utilities that can help you keep these system databases and structures in an optimal state.

< Day Day Up >

The `CATENFM` Utility

The CATENFM utility is used to change the mode of a DB2 V8 subsystem. It can be used to enter enabling-new-function mode and new-function mode. Refer to Appendix G, "DB2 Version 8 Overview," for more details about the modes of DB2 Version 8.

NOTE

All new V8 functionality is unavailable until the DB2 subsystem enters new-function mode.

This utility should only be used by a DBA or system programmer who understands the ramifications of moving from one DB2 V8 mode to another.

< Day Day Up >

The `CATMAINT` Utility

The CATMAINT utility is used when migrating from one version or release of DB2 to another. It changes the structure of the DB2 Catalog by altering and creating DB2 tables and indexes using the special links and hashes in the DB2 Catalog database. The CATMAINT utility modifies the DB2 Catalog objects in place.

An execution of CATMAINT cannot be partially successful; all the catalog changes are made when the job is successful, or none are made when the job fails.

Only an INSTALL SYSADM as specified in the DSNZPARM s can execute the CATMAINT utility.

`CATMAINT` Guidelines

The guideline presented next should be followed when you are considering CATMAINT usage.

Use `CATMAINT` Only As Directed

The CATMAINT utility should be used only when migrating to a new release of DB2, and then only as directed by IBM in the DB2 release migration procedures.

< Day Day Up >

The `DSNJCNVB` Utility

The DSNJCNVB utility is used to convert the bootstrap data set (BSDS) so that it can support up to 10,000 archive log volumes and 93 active log data sets per log copy.

If you do not convert the BSDS, only 1,000 archive log volumes and 31 active log data sets per log copy can be managed.

The DSNJCNVB utility should be executed as a batch job only when DB2 is not operational. Furthermore, DSNJCNVB can only be run on a DB2 V8 subsystem in new-function mode. Although converting the BSDS is optional, it is highly recommended for large or highly-active DB2 shops .

Expand the Size of the BSDS Before Converting

If you have migrated to V8 from aprevious version of DB2, you will need to create a larger BSDS before converting it with DSNJCNVB .

After you have migrated to V8 new-function mode, execute the following steps to prepare to run the DSNJCNVB utility:

Rename your existing BSDS copy 1 data set. Be sure to retain your original copy of the BSDS so you can restore it in case of a failure during conversion.
Allocate a larger BSDS data set using the VSAM DEFINE statement in installation job DSNTIJIN , using the original BSDS name .
Use VSAM REPRO to copy the original data set to the new, larger data set.
Repeat steps 1 through 3 for copy 2 of the BSDS (if you are using dual BSDSs).

Finally, after expanding the size of your BSDSs, you can invoke the conversion utility, DSNJCNVB , using the JCL snippet shown in Listing 34.1. The SYSUT1 and SYSUT2 DDNAME s specify the data sets for copy 1 and copy 2 of the BSDS.

Listing 34.1. `DSNJCNVB` JCL

//DSNJCNVB EXEC PGM=DSNJCNVB

//STEPLIB  DD   DISP=SHR,DSN=DB2P.SDSNEXIT

//         DD   DISP=SHR,DSN=DB2P.SDSNLOAD

//SYSUT1   DD   DISP=OLD,DSN=DB2P.BSDS01

//SYSUT2   DD   DISP=OLD,DSN=DB2P.BSDS02

//SYSPRINT DD   SYSOUT=*

< Day Day Up >