Using ODBR

Before using online database reorganization (ODBR), you must first perform an initial setup.

About this task

The following lists ODBR processing considerations:
  • You cannot run an ODBR move session when database reorganization (DBR), the online DASD formatter, module copy, capture, or restore is running.
  • You cannot run DBR, the online DASD formatter, capture, restore, or the alternate FCTB loader when an ODBR move session is running.
  • For the best results when you run an ODBR move session, avoid running DASD-intensive operations such as recoup, pool reallocation, or nightly file maintenance. Pause or complete the ODBR move session before DASD-intensive operations are run.
  • For the best results, avoid running ODBR move sessions on different multiple database function (MDBF) subsystems at the same time.
  • If the capture function was run before the ODBR session, run the capture function again after the ODBR session completes. You cannot restore the data captured before the ODBR session.
  • Set up a fallback image that includes all physical copies of the core image restart area (CIMR) components. The fallback image must not have any logical references to other images for the CIMR components.
  • If the device type in your MDBF subsystem is defined in the system initialization process (SIP) as selectively duplicated, you must ensure realtime DASD modules are online during an ODBR session if you attempt to move simplex fixed or pool records.

Procedure

To set up and use ODBR, complete the following steps:

  1. In a loosely coupled complex, enter the following commands to add the ODBR utility to the utility processor resource ownership table (PROT) and assign ownership of the utility to a subsystem:
    1. ZPROT ADD UT ODBR BSS
    2. ZPROT ASN UT ODBR BSS.
    Note: The ODBR utility must be assigned to one of the first eight processors in a loosely coupled complex.
  2. Enter the following commands to initialize the z/TPFDF database that is used to hold the ODBR control information:
    1. ZUDFM INIT FCBE
    2. ZUDFM INIT FCBE.
    Note: This command is entered twice to complete the initialization.
  3. Build the FACE table (FCTB). To do this step:
    1. Modify RAMFIL statements in SIP input deck.
      Note: The area that you want to move any records to in the alternate FCTB must be defined as IFORMAT or SPARE in the base FCTB and have a formatted record size that is the same as the records that are being moved to that area.
    2. Enter the bldtpf command to generate an alternate FCTB.
  4. Enter fctbval -m to check your changes to the alternate FCTB.
  5. Use the offline loader (TPFLDR) to create the input medium that contains the alternate FCTB. Be sure that only the alternate FCTB is in the load.
  6. Enter ZODBR LOAD to load the alternate FCTB for ODBR.
    Note:
    • Load processing performs a compatibility check for the alternate FCTB and the existing database, and validates the DASD format.
    • You can customize compatibility checking for the alternate FCTB and the existing database by using the ufct.c user exit.
    • If there is a problem, the load is prevented.
    • A maximum of one ODBR alternate FCTB can be loaded at a time for all z/TPF system images in this subsystem.
    • To prevent interference with the general file loader, ODBR is not supported from image 1.
  7. Enter ZODBR DISPLAY PROFILE to display the current profile options for ODBR.
  8. Enter ZODBR PROFILE to change your profile options, if necessary.
  9. Enter ZIMAG DISPLAY PROCESSOR to display the image that each processor is running on. All processors in the z/TPF complex must be running on the same image to run the ODBR move session. To obtain the image name for the ODBR move session, enter ZODBR DISPLAY STATUS.
  10. Enter ZODBR DISPLAY OMST ALL to verify that the correct data records are being relocated. This verification must be consistent with step 4.
  11. Enter ZODBR START to start an ODBR move session.
    During the move session, use the ZODBR DISPLAY commands to display the status of the session. If there is a problem, do one of the following actions:
    • Do the following steps:
      1. Enter ZODBR CANCEL to stop ODBR processing.
      2. Enter ZODBR START to start processing again or enter ZODBR DELETE to permanently end this ODBR move session.
    • Do the following steps:
      1. Enter ZODBR PAUSE to pause the move session.
      2. Enter the ZODBR RESTART start processing again.
      Note: If a system outage occurs, enter the ZODBR RESTART command to restart ODBR.
  12. If specified in your profile options, the data move is verified automatically. Otherwise, enter ZODBR VALIDATE to verify the records manually. ZODBR VALIDATE validation errors are placed in the odbrRecordValidationError.log file in the directory that is specified by the PATH parameter of the ZODBR PROFILE command.
  13. If necessary, enter ZODBR LEVEL to change the allowed number of entry control blocks (ECBs) that can be active simultaneously to move or validate data in a processor during ODBR move session processing.
  14. Accept the alternate FCTB and complete ODBR.
    1. If manual validation is running, allow it to complete or you can stop it by entering ZODBR VALIDATE STOP.
    2. Complete or stop the processing of any restricted non-ODBR utility that is running on the z/TPF system.
    3. Enter ZODBR ACCEPT to start end-of-session processing.
      Notes:
      • Virtual File Access (VFA) is flushed during the end-of-session processing.
      • If pool record types are moved, all the pool sections that are associated with the moved pool record types will be reordered when get file storage (GFS) is active on the processor.
      • If an error occurs during the end-of-session processing, a destructive IPL of the ODBR owning processor might be necessary.
      • During end-of-session processing, it is recommended that commands that might affect the external lock facility (XLF) cache (such as the ZBUFC commands) are not entered during end-of-session processing or active when the ZODBR ACCEPT command is entered.
    4. Enter ZIMAG DISPLAY IMAGE and specify the name of the current image to verify that the accepted FCTB is the current FCTB.

What to do next