A file format conversion of the database enables changes to be made to database files that do not affect record formats. A file format conversion can be used to change such things as the AREASIZE and BLOCKSIZE attributes of a data set, the MODULUS attribute of an Access, or the TABLESIZE attribute of a set or subset.
 |
When using XE features, the following operations affect a file format conversion and require a reorganization:
|
Multiple data sets and their spanning sets and subsets can be modified by performing a DASDL compilation, a BUILDREORG run, a DMALGOL REORGANIZATION compilation, and a run of the Reorganization program that was compiled.
Most of the changes allowed as part of the update process can also be made during a reorganization. The changes can be made to any structure, whether the structure is being reorganized.
If a DASDL UPDATE compilation increases the database update level, the old description file is backed up using a WFL job, and is located under the same usercode and on the same pack as the new description file. This old description file is backed up as
DESCRIPTION/<database name>/<old update level>
The old update level designation is the update level of the old description file.
Examples of when the update level increases include
-
Changing file or record formats
-
Adding or deleting structures
-
Updating to the next major ClearPath MCP release
If DASDL cannot back up the old description file for any reason (such as WFL syntax errors, a discontinued COPY job, a missing file, or a missing pack), DASDL returns an error. The old description file is not backed up if the update level is not increased, or if the DASDL UPDATE compilation checks for syntactical correctness only or has errors.
