Allowed Changes to Control File Specifications details the changes that can be made to the control file specifications. Numbers in parentheses refer to explanatory notes following the table.
Table 24. Allowed Changes to Control File Specifications
|
Option |
Model |
Update |
File Format Conversion (No Item Changes) |
|
|---|---|---|---|---|
|
DBPATH |
No |
Yes (7,8) |
No |
No |
|
Disk/pack |
Yes |
Yes (1,5) |
Yes (3) |
|
|
DOCADMIN |
No |
Yes |
No |
No |
|
RUNTIMEUC |
No |
Yes |
No |
No |
|
SECURITYGUARD |
Yes |
Yes |
Yes |
Yes |
|
USERCODE |
Yes |
Yes (2,5) |
Yes (4) |
Yes (4) |
|
VSS3OPTIMIZE |
Yes |
Yes |
Yes |
Yes |
Explanatory Notes
-
On a DASDL update, the DASDL compiler runs the DMCONTROL program and assumes that the old control file is on the old device. The DMCONTROL program then writes the new control file to the new device.
When the DMCONTROL option is set (the default value) in the DASDL description, SYSTEM/DMCONTROL is initiated during the DASDL compilation and the DASDL compiler provides a label-equation for the control file on the old device. In this way, SYSTEM/DMCONTROL can locate the control file on the old device, update it, and write it back to the new device. However, when the DMCONTROL option is reset in the DASDL description, the user must run SYSTEM/DMCONTROL following the DASDL compilation to update the control file. However, before doing so, the control file must be copied from the old device to the new device. This can be done using a library maintenance procedure. By default, SYSTEM/DMCONTROL looks on the new device for the control file.
When both the MODEL and UPDATE options are designated, the DASDL compiler runs SYSTEM/DMCONTROL with the assumption that the old control file is on the new device. The control file can be copied to the new device using a library maintenance procedure.
-
On a DASDL update, the DASDL compiler runs SYSTEM/DMCONTROL with the assumption that the old control file has the old usercode. SYSTEM/DMCONTROL then produces the new control file with the new usercode.
When both the MODEL and UPDATE options are designated, the DASDL compiler runs SYSTEM/DMCONTROL with the assumption that the old control file has the new usercode. The old control file can be given the new usercode by using the WFL CHANGE command or a library maintenance procedure.
-
The Reorganization program assumes the old control file is on the new device. The control file can be copied to the new device using a library maintenance procedure.
-
The Reorganization program assumes the old control file and the database files have the new usercode. The old control file and the database files can be given the new usercode by using the WFL CHANGE command or a library maintenance procedure.
-
Recompile the user programs and tailored data management software. Recompilation of the DMSUPPORT library is not necessary.
-
The pack name can be added if it was not previously specified in the DASDL description. The Reorganization program assumes the old control file is on the new device. The control file can be copied to the new device using a library maintenance procedure.
-
On a DASDL update, the DASDL compiler runs the DMCONTROL program and assumes that the old control file is in the location specified by the previous value of the DBPATH command. The DMCONTROL program then writes the new control file in the location specified by the current data path specification.
-
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.
