Start of change

DSNJCNVT

The DSNJCNVT stand-alone conversion utility converts the bootstrap data set (BSDS) records that are necessary to support 10-byte RBA and LRSN fields.

At migration to Db2® 12, you cannot start Db2 12 until the BSDS is converted to use the 10-byte RBA and LRSN formats. You can convert the BSDS before or during the Db2 12 migration process.

Running DSNJCNVT is optional and can be done any time after migrating to Db2 11 new-function mode. Conversion is required during installation if the RBA or LRSN is approaching the end of the range. For a data-sharing installation, if the LRSN is approaching the end of the range, the BSDS of each member can be converted one at a time.

In data sharing, you must convert the BSDS for each Db2 member separately.

Attention: In Db2 subsystems that are not data sharing members, if Db2 is already at risk of reaching the 6-byte RBA limit, it is strongly recommended that you first convert all catalog and directory objects, then convert all user objects to the 10-byte RBA format, before you convert the BSDS.

In Db2 subsystems that are not data sharing members, always convert all Db2 catalog, directory, and user objects to use the extended 10-byte RBA format before you convert the BSDS, especially if Db2 is close to reaching the logging limit for the 6-byte RBA. Failure to convert page sets to the 10-byte RBA format before Db2 reaches the 6-byte logging limit results in failed updates with reason code 00C2026D. No updates are allowed for any object that is still in the 6-byte format.

In data sharing, if any Db2 member is approaching the logging limit for the 6-byte RBA but the LRSN is not approaching the limit of the 6-byte range, converting the BSDS of just that member sufficient to resolve the immediate problem and prevent outages. However, if the LRSN is also approaching the end of the 6-byte range, you must continue and convert page sets to use the 10-byte format before the limit is reached.

For instructions, see Converting the BSDS to the 10-byte RBA and LRSN (Db2 Administration Guide).

Environment

Run the DSNJCNVT utility as a batch job only when Db2 is not running.

Your Db2 subsystem must be in new-function mode to convert the BSDS.

Authorization required

The authorization ID of the DSNJCNVT job must have the required RACF® authorization and read/write access to the new BSDSs and read access to the old BSDSs.

Required and optional data sets

DSNJCNVT recognizes DD statements with the following DD names:

SYSUT1
Specifies the old BSDS that is to be converted. This statement is required.
SYSUT2
Specifies the second copy of the old BSDS that is to be converted. This statement is optional.
SYSUT3
Specifies the new, converted BSDS. This statement is required.
SYSUT4
Specifies the second copy of the converted BSDS. This statement is required if the installation uses dual BSDSs; otherwise, it is optional.
SYSPRINT
Contains the output messages from the conversion utility. This statement is required.

Running DSNJCNVT

Use the following EXEC statement to run this utility:

//EXEC   PGM=DSNJCNVT

Considerations for running DSNJCNVT

  • The Db2 subsystem that owns the BSDSs that are to be converted must be stopped. DSNJCNVT is a stand-alone utility.
  • In a data-sharing environment, allow Db2 utilities that read the logs of peer members to finish before converting the BSDSs.
  • In a data-sharing environment, stop data replication products before the conversion to ensure that the old BSDSs can be successfully renamed and replaced by the converted BSDSs. The recommended procedure is to stop the replication product first and then stop the Db2 system that is to have its BSDSs converted. This procedure allows sharing systems to deallocate the BSDSs when the state of the member changes to inactive.
  • The RACF user ID that is running DSNJCNVT must have read/write access to the new BSDSs and read access to the old BSDSs.
  • The Db2 subsystem that owns the BSDS that is to be converted must start after the data sharing group was migrated to Db2 11 new-function mode.
  • Conversion to the new BSDS format is required to write new format log records and remove the 6-byte RBA and LRSN limits.

Sample DSNJCNVT control statement

The following statements specify that DSNJCNVT is to convert the BSDS that is needed to support 10-byte RBA and LRSN fields.

//CONVERT EXEC PGM=DSNJCNVT,REGION=64M
//SYSUT1   DD  DSN=DB2A.OLD.BSDS01,DISP=SHR
//SYSUT2   DD  DSN=DB2A.OLD.BSDS02,DISP=SHR
//SYSUT3   DD  DSN=DB2A.BSDS01,DISP=OLD
//SYSUT4   DD  DSN=DB2A.BSDS02,DISP=OLD
//SYSPRINT DD  SYSOUT=*     
You can view another example of using DSNJCNVT in job DSNTIJCB in prefix.SDSNSAMP.

DSNJCNVT output

The following example shows sample DSNJCNVT output:

CRCR convert started 
DSNJ200I DSNJCNVT CONVERT UTILITY PROCESSING COMPLETED SUCCESSFULLY
FOR MEMBER 'xxxxxxxx' 
End of change