Specifies to perform a cleanup to delete work files and unlock target areas. You can use this option to complete a successful unload/reload operation if cleanup was not performed automatically. It can also be used to delete work files created by an incomplete unload/reload operation that is not being continued.
Note: For more information, see Considerations for running REORG on VSE.
Specifies to not delete work files during the cleanup phase.
Directs an explicit cleanup job to delete all work files associated with the current control file, including those that were not dynamically allocated by the current REORG operation. This option does not apply to DBKEYS files.
By default, only files dynamically allocated by the current REORG operation are deleted.
Specifies to not unlock the reloaded database areas during the cleanup phase.
Specifies to produce a status report by reading the reorganization control file. This can be run while other REORG jobs are executing to obtain a current status of the entire REORG process.
Directs REORG to estimate the size of work files by gathering statistics in a separate pass of the database. This option generates estimates for both UNLOAD and RELOAD work files.
By default, statistics are collected during the unload phase that can be used for sizing RELOAD work files only. UNLOAD work files must be sized manually.
If specified together with setup-options, statistics gathering starts as soon as the setup phase is complete and processing stops after the statistics have been gathered. Additional jobs are automatically submitted to help gather statistics and process the database by UNLOAD slice and index.
If specified independently of setup-options, it must be specified in a separate execution of the REORG utility that occurs between the setup and UNLOAD phases. Multiple jobs are submitted to gather statistics only if the SUBMIT option is specified. Processing stops when file estimation is complete.
When file estimation is complete, processing must be restarted by specifying a new STOP AFTER point.
File size estimates are automatically used when dynamically allocating work files if no primary space value is specified for the file's DSMODEL.
Specifies the database name the source subschema with be bound to. All bound areas will be unloaded, unless restricted with the area-name option. The source subschema name must be specified with this option.
Specifies the segment of the database whose areas are to be unloaded. The segment is referred to as the source segment, and the database is referred to as the source database.
Specifies the subschema that describes the source database.
By default, if the source-subschema-name is not specified, it indicates that an SQL-defined segment is to be unloaded. In this case, the REORG utility extracts the description of the database from the dictionary to which the session is connected.
Specifies an area in the source segment to unload. Records in this area may target different areas in the target database.
By default, if no areas are specified for a non-SQL defined database, all areas in the source segment that are also defined in the source subschema are unloaded. If no areas are specified for an SQL-defined database, all areas in the segment are unloaded.
Specifies the name of the database into which data is reloaded. This is referred to as the target database.
If an SQL-defined database is being reorganized, the target-database-name must be the same as the source-segment-name specified in the SEGMENT clause.
If a non-SQL-defined database is being reorganized, target-database-name must be the name of either a segment or a DBNAME identifying the database into which data is to be reloaded.
Specifies the subschema that describes the database into which the data is reloaded.
Do not specify a target subschema if reorganizing an SQL-defined database.
By default, if reorganizing a non-SQL-defined database and target-subschema-name is not specified, the source subschema is also the target subschema.
Specifies the DMCL that defines the database into which the data is reloaded.
By default, if a target-dmcl-name is not specified, the DMCL that describes the source database is used during the reload phase and therefore must also describe the target database.
See the source/target DMCLs in Initiating a REORG Operation for additional information.
Specifies the degree to which parallel processing is to be used to reduce elapsed time. The default is 1, which means that one job processes data and another processes system indexes.
Use of this option exponentially increases the number of work files needed. For more information, see Work files and the n WAYS parameter in Work Files.
Specifies to reuse work files as much as possible. Use of this option reduces the number of work files that are needed.
Specifies that each task that stores a record into the new database generates a DBKEYS file that maps the old db-key of the record with the new db-key of the record.
For more information, see Generating db-key cross-reference information in Using the REORG Utility.
Specifies to process sorted output data directly from the SORT, instead of writing it to an intermediate work file. Use of this option reduces the number of files and the amount of disk space needed.
Specifies to not lock source areas to prevent concurrent update. By default, source areas are locked at the start of unload processing.
When source areas are locked, they remain locked even after the REORG has completed. This prevents updates to the source area under the assumption that the target database is now the current database.
Specifies a time-interval in minutes. Each time this interval expires, a message is written indicating the current task being processed and the percentage of records processed to that point. This message is not produced while data is being sorted.
Directs REORG setup to delete work files that may be left from a previous run. All existing work files that match the name of a new work file are deleted, including DBKEYS files. For more information see, Considerations for running REORG on VSE.
By default, old work files are reused.
Specifies the percentage used to estimate the size of SYSOF2 and SYSOF8 work files and all output work files for the two overflow tasks: RELOAD2 and RELOAD5. The size of these files cannot be predicted, so they are estimated to be a percentage of related work files.
By default, 10% is used.
Specifies a limit on the size of the overflow cache used to temporarily hold records that do not fit on their target page.
nnn is the maximum size of the overflow cache specified in bytes, Kilobytes (2**10), Megabytes (2**20), or Gigabytes (2**30), depending on whether it is followed by no qualifier or by KB, MB, or GB respectively.
A value larger than 2**31-1 is limited to 2**31-1 bytes.
By default, 32 KB is used.
Specifies the processing phase after which execution halts. The options are:
Continues processing until the entire reorganization operation is complete. CLEANUP is the default if setup-options are specified.
Terminates processing after setup is complete and before unload is initiated. This option is valid only if setup-options are specified.
Terminates processing after the unload phase is complete and before reload is initiated.
Terminates processing after the reload phase is complete and before cleanup is initiated.
If neither setup-options nor STOP AFTER is specified on a REORG statement, the processing stop point remains unchanged from that previously established.
If STOP AFTER is specified, and the reorganization control file indicates that processing has already been initiated for a phase beyond that specified as a stop point, a warning is issued and processing is terminated.
Specifies to submit JCL for additional REORG jobs to the internal reader when a REORG operation is restarted.
This option is not valid during the initial setup phase, because by default, if processing continues beyond the initial setup phase, JCL is automatically submitted before starting the unload phase.
The JCL to be submitted is retrieved from the RORGJCL file. If no RORGJCL is present in the execution JCL, the SUBMIT option is ignored.
Specifies whether to create work files and for which phases. The options are:
Does not dynamically create work files. This is the default.
Creates only the files used during unload processing.
Creates only the files used during reload processing.
Creates both unload and reload work files.
Note: For information about REORG's work files and using data set models to create them, see Work Files.
|
Copyright © 2014 CA.
All rights reserved.
|
|