Start of change

Convert BSDS records to the extended 10-byte format: DSNTIJCB

You must convert the BSDS to a new format that supports 10-byte RBA and LRSN fields before you start Db2 in Db2 12. By default, the BSDS of a Db2 11 subsystem is initialized in the 6-byte, pre-Db2 11 format.

Before you begin

Start of changeBefore you can convert the BSDS, the Db2 subsystem or data sharing member must be started in Db2 11 new-function mode. End of change

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 migrating to Db2 12.
Attention: After the BSDS is converted to the 10-byte format, Db2 stops issuing messages to warn you about the risk of reaching the 6-byte RBA or LRSN limits. The increased size of all log records also accelerates progress toward the 6-byte RBA logging limit.

Start of changeIn 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.End of change

Start of changeIn 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.End of change

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.

Procedure

To convert the BSDS to use the extended 10-byte RBA and LRSN format, complete the following steps:

  1. Stop Db2.
    Tip: Start of change If you complete the BSDS conversion as part of the Db2 12 migration process, you can avoid an extra stop and start of Db2. To do so, complete the BSDS conversion sometime between Migration step 9: Stop Db2 11 activity and Migration step 18: Start Db2 12.End of change
  2. Run job DSNTIJCB and make sure that it allocates the Db2 11 SDSNLOAD module.
    The DSNTIJCB job for each Db2 subsystem or data sharing member is located in the prefix.NEW.SDSNSAMP sample library that is generated when you run the installation CLIST in MIGRATE mode.
    Db2 runs the DSNJCNVT conversion utility to convert the bootstrap data set records to support 10-byte RBA and LRSN fields. For more information, see DSNJCNVT.
  3. Start Db2.

What to do next

Start of changeIf you have not already done so, complete the following tasks:End of change

  1. Convert all page sets for the Db2 catalog and directory as described in Convert the BSDS, Db2 catalog, and directory to 10-byte RBA and LRSN format .
  2. Convert all user objects to support the 10-byte RBA and LRSN, as described in Converting page sets to the 10-byte RBA or LRSN format. After Db2 reaches the hard logging limit, you might not be able to convert the catalog and directory page sets, as described in Converting page sets to the 10-byte RBA or LRSN format.

  3. Continuously monitor the RBA and LRSN values until all catalog, directory, and user objects are converted to the 10-byte RBA or LRSN format. Failure to convert page sets before the 6-byte soft logging limit is reached results in failed updates with reason code 00C2026D, and any objects still in the 6-byte format become read-only. RBA or LRSN values greater than x'F00000000000' indicate that your system is at risk of reaching the 6-byte logging limit. For more information about the RBA and LRSN logging limits, see What to do before RBA or LRSN limits are reached.

End of change