REORG is best used with large areas that contain large amounts of data. We do not recommend using REORG to process small areas. For small areas, use the normal BACKUP and LOAD functions of the CA Datacom/DB Utility (DBUTLTY). Areas of medium size can best be reorganized by using the BACKUPONLY option of REORG to perform a fast parallel backup, followed by the resulting 1-25 files used as concatenated into a single LOAD function.
Note: If you are partitioning by some portion of Native Key, running a REORG DDNAME=*,INNUM=n (where n is the number of partitions) gives the current way to break up the data set.
Three sets of subtasks are associated with the REORG function:
Note: The REORG function updates a current index to reflect the moving of data into Native Key sequence order, but REORG does not reorganize an index, that is to say, REORG does not build a new index. REORG therefore cannot be successfully executed after the INIT of an index.
Instead of performing all three sets of subtasks with REORG, you can use the function to perform a parallel backup only, if desired, or you can use REORG to perform only a parallel loading of the data with index update. A reporting only option is also available, if you use REORG OPTION2=BACKUPONLY and either DDNAME=* or DDNAME**. For information about DDNAME=, see the list of Required Keywords.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|