Allowed Changes to Data Set Physical Options details the changes that can be made to the data set physical options. Numbers in parentheses refer to explanatory notes following the table.
Table 37. Allowed Changes to Data Set Physical Options
|
Option |
Model |
Update |
File Format Conversion (No Item Changes) |
|
|---|---|---|---|---|
|
ALLOCATE |
No |
Yes (3) |
Yes |
|
|
AREAS |
Yes |
Yes (1) |
Yes |
|
|
AREASIZE |
No |
No |
Yes |
|
|
AVERAGE RECORD SIZE |
No |
No |
Yes |
Yes |
|
BLOCKSIZE |
No |
No |
Yes |
|
|
BUFFERS |
Yes |
Yes (1) |
Yes |
|
|
CHECKSUM |
No |
No |
Yes |
|
|
DATAENCRYPT |
No |
No |
Yes |
Yes |
|
DATAMASK |
No |
No |
Yes |
Yes |
|
DIGITCHECK |
No |
Yes |
Yes |
|
|
disk/pack |
Yes (6) |
Yes (2,6) |
Yes (6) |
|
|
DUMPSTAMP |
No |
No |
Yes |
|
|
EXTENDED |
No |
No |
No |
|
|
LOCK TO MODIFY DETAILS |
No |
Yes (3) |
Yes |
|
|
OBFUSCATIONLEVEL |
No |
No |
Yes |
Yes |
|
OPEN PARTITIONS |
No |
Yes |
No |
No |
|
PARTITION set name |
No |
No |
No |
|
|
POPULATION |
No |
Yes (1,4) |
Yes |
|
|
POPULATIONINCR |
Yes (5) |
Yes (5) |
Yes (5) |
|
|
POPULATIONWARN |
Yes (5) |
Yes (5) |
Yes (5) |
|
|
REBLOCK |
No |
Yes (3) |
Yes |
|
|
REBLOCKFACTOR |
Yes |
Yes (1) |
Yes |
|
|
RECORDCOUNT |
No |
No |
Yes |
Yes |
|
SECTIONS |
No |
No |
Yes (7) |
|
|
STRENCRYPT |
No |
No |
Yes |
Yes |
|
SUBBLOCKSIZE |
No |
No |
Yes |
|
|
VSS2OPTIMIZE |
No |
No |
Yes |
|
|
VSS2WARN |
Yes |
Yes (1) |
Yes |
|
|
VSS3OPTIMIZE |
No |
No |
Yes |
Yes |
Explanatory Notes
-
Recompilation of tailored data management software is not necessary.
-
When the disk/pack option is changed, the system searches for the data set on the new device. The data set can be copied from the old device to the new device by using library maintenance.
The disk/pack option should not be changed for the LOB tank data set, restart data set, or global data set in conjunction with any updates that cause a reorganization. These files are accessed before the reorganization runs DMCONTROL and are expected to be on the original pack. Once DMCONTROL is run, these files are expected to be on the new pack. This move to the new pack requires manual intervention and, if not handled correctly, could lead to errors.
If the structure is in a permanent directory, the permanent directory must exist on the new device or the directory must be created manually before copying the structures.
-
Recompile the DMSUPPORT library.
-
The DASDL compiler uses the population value to compute values for the AREAS, AREASIZE, and BLOCKSIZE options for data sets; and for the AREAS, AREASIZE, and TABLESIZE options for sets and subsets. Thus, changing the population value can affect these options. Changing the population of a data set can also change the population of sets and subsets which reference the data set, because sets and subsets inherit the population of the data set by default.
Both the update and reorganization processes can be used to change the population value.
When the reorganization process is used, the population value can be increased or decreased as desired. The new population value is used to compute new values for the AREAS, AREASIZE, BLOCKSIZE, and TABLESIZE options; and the reorganization process then reformats the files using these new values. Alternatively, the AREAS, AREASIZE, BLOCKSIZE, and TABLESIZE options can be specified explicitly in DASDL.
When an update process is used, the AREASIZE and BLOCKSIZE options must not change. DASDL computes a new value for the AREAS option based on the new population value.
-
If the attributes associated with these options are changed through the VDBS facility, a SYSTEM/DMCONTROL OVERRIDE operation must be performed before changes specified through DASDL can take effect.
-
If the attributes associated with these options are changed through a DMCONTROL operation, a SYSTEM/DMCONTROL OVERRIDE operation must be performed before changes specified through DASDL can take effect.
-
If you change a nonsectioned data set to a sectioned data set, change a sectioned data set to a nonsectioned data set, or change the value of the SECTIONS option, although items within the data set are not changed, you need to recompile user programs. Refer to XE Feature Summary of the Update, Reorganization, and Modeling Processes for additional information.
