Table of Contents
- Altering Database Default Options
- Altering Database Options
- Altering Database Parameters
- Altering Audit Trail Specifications
- Altering Control File Specifications
- Altering Data Set Descriptions
- Describing Data Set Alterations
- Altering Aggregate Items
- Altering Count Items
- Altering Record Type Items
- Altering Data Items
- Altering Filler Items
- Altering Group Items
- Altering Link Items
- Altering Population Items
- Altering the Variable-Format Part
- Altering Global Items
- Altering the Data Set Logical Option
- Altering Data Set Physical Options
- Altering Item Types and Sizes
-
- Allowable Sign Changes
- Effect of Changing an Occurs Clause
- Effect of Changing a Boolean Value in a Field
- Changing Compact, VERIFY Condition, and SELECT Condition Items
- Translating Alpha or Group Items to Number, Real, Field, or Boolean Items
- Translating Number, Real, Field, or Boolean Items to Alpha or Group Items
- Truncation
- Altering Sets, Subsets, and Accesses
- Altering Remaps and Virtual Information
-
- Altering Remaps
- Altering Remap Options
- Altering Remap Aggregate Items
- Altering Remap Count Items
- Altering Remap Record Type Items
- Altering Remap Data Items
- Altering Remap Filler Items
- Altering Remap Group Items
- Altering Remap Link Items
- Altering Remap Population Items
- Altering Remap References
- Altering Remap Sets, Subsets, and Accesses
- Altering the Remap Variable-Format Part
- Altering the Global Data Remap
- Altering Virtual Count Items
- Altering Virtual Data Items
- Altering Virtual Group Items
- Altering Virtual Population Items
- Altering Logical Databases
This section describes the capabilities and limitations of the update, reorganization, and modeling processes.
Summary of the Update, Reorganization, and Modeling Processes summarizes the actions that must be performed for each form of the update, reorganization, and modeling processes. Numbers in parentheses refer to explanatory notes following the table.
Table 18. Summary of the Update, Reorganization, and Modeling Processes
|
Form of Process |
Recompile Database Description |
Compile and Execute Reorganization Program |
Recompile Tailored Data Management Software |
Recompile User Programs |
|---|---|---|---|---|
|
Update |
Yes |
No |
Yes (3) |
No |
|
Model only (2) |
Yes |
No |
Yes |
No |
|
Garbage collection reorganization |
No |
Yes |
No |
No |
|
File format conversion with items not changing |
Yes |
Yes |
Yes |
No |
|
Record format conversion with item or key changes |
Yes |
Yes |
Yes |
Yes (1) |
Explanatory Notes
-
User programs need not be recompiled if they access the reformatted data set by means of remaps. However, when structures are deleted, their structure numbers can be reused. As a result, some combination of deletions and additions can produce a situation in which a new set has the same structure number as a deleted set of the same data set. If this situation occurs, the effect is the same as changing the key, and therefore requires that all programs that explicitly invoke the structure must be recompiled.
-
When the MODEL option is used with the UPDATE option, the actions are the same as using only the MODEL option. A MODEL option cannot be used with reorganization specifications; the required information is taken from the description file for the modeled database, which itself must have just been reorganized.
-
The control file should always be updated. Whenever the update level of the description file in increased, recompilation of tailored data management software is required. If nothing is mentioned about recompilation, then recompilation of tailored data management software is required. Some forms of the update process do not require recompilation of all data management software. Refer to the Update column in XE Feature Summary of the Update, Reorganization, and Modeling Processes through Allowed Changes to the Data Set Logical Option for more details.
Most features of the database can be changed using a form of the update or reorganization processes. XE Feature Summary of the Update, Reorganization, and Modeling Processes through Allowed Changes to the Data Set Logical Option indicate the database changes allowed and the form of the update or reorganization process to be used for each change. Often, more than one form of the update and reorganization processes can be used to make the desired change. The user can then select whichever form is most convenient.
XE Feature Summary of the Update, Reorganization, and Modeling Processes summarizes the actions that must be performed when using XE features for each form of the update, reorganization, and modeling processes.
Table 19. XE Feature Summary of the Update, Reorganization, and Modeling Processes
|
Form of Process |
Recompile Database Description |
Compile and Execute Reorganization Program |
Recompile Tailored Data Management Software |
Recompile User Programs |
|---|---|---|---|---|
|
Set or reset the EXTENDED option for a data set |
Yes |
Yes |
Yes |
Yes |
|
Set, reset, or change the value of the SECTIONS option for a data set (the range is 2 through 63). |
Yes |
Yes |
Yes |
Yes |
|
Set, reset, or change the value of the SECTIONS option for an index sequential set |
Yes |
Yes |
Yes |
No |
