Example 9. DBY exists, DBZ is to be added

DBY must be reorganized. DBZ must be loaded using an initial load program. DBIL must be specified in the control statement for DBY. Do not specify DBR in the control statement for DBY.

Example 9 is shown in the following figure.

Figure 1. DBY exists, DBZ is to be added
DBY has SEG A and child SEG B. DBZ has SEG C. SEG B is to be logical child of SEG C.

Procedure

  1. Determine whether the change you are making affects the code in any application programs. If the code is affected, make sure it gets changed.
  2. Unload DBY, using the existing DBD and HD Unload utility.
  3. Code a new DBD for DBY and DBZ.
  4. If the change you are making affected the code in application programs, make any necessary changes to the PSBs for these application programs. If you have the DB/DC Data Dictionary, it can help you determine which application programs and PCBs are affected by the DBD changes you have made.
  5. Rebuild the ACB if you have ACBs prebuilt rather than built dynamically.
  6. Recalculate database space for DBY and calculate space for DBZ.
  7. For non-VSAM data sets, delete the old database space and define new database space. For VSAM data sets, delete the space allocated for the old clusters and define space for the new clusters.
  8. Run the Prereorganization utility, specifying DBIL in the control statements for DBY and DBZ.
  9. Reload DBY, using the new DBDs and the HD Reload utility.
  10. Load DBZ, using an initial load program.
  11. Run the Prefix Resolution utility, using the DFSURWF1 work files that are output from Steps 9 and 10 as input.
  12. Run the Prefix Update utility, using the DFSURWF3 work file that is output from Step 11 as input.
  13. Remember to make an image copy of both databases as soon as they are loaded.