Operational Flow and Considerations

There are some important operational factors to consider before and during the execution of CA IDMS/DB Reorg.

Each step of CA IDMS/DB Reorg must be executed in sequence. You can repeat steps, but you cannot skip a step.
While the database is being reorganized, you must ensure that no other jobs are run against any area that is being reorganized.
The new database for all areas specified in COPY statements must be formatted by running IDMSBCF prior to the STORE Step.
In a VSE/ESA environment, you must assign the symbolic units for work files to a device type, even if you have a file manager, because of CA IDMS/DB Reorg's own device-independent support.
Execution time is directly related to the size of the area or areas being reorganized, the number of records in those areas, and the number of set linkages for each of those records. As the database reorganization executes, you can monitor the progress of the utility from the operator console.
CA IDMS/DB Reorg runs with an outstanding operator reply unless DSPLYINT=NO is specified. Be sure that your system console operator is aware of valid reply choices. See DSPLYINT Parameter.
CA IDMS/DB Reorg automatically bypasses the IIXSDBK step, if it is not needed. IIXSDBK is executed only if you are updating an area containing integrated index sets sorted by db-key.