This form of reorganization allows changes to be made to the format of existing data set and global data records. Using record format conversion, new items can be added and existing items can be deleted from the database description.
* UPDATE; R RANDOM DATA SET ( F FIELD(10); G GROUP ( M REAL; N NUMBER(S5,2); ); ); A ACCESS TO R KEY IS G DUPLICATES * MODULUS = 1000;
![]() |
When using XE features, adding or removing the EXTENDED option for a data set causes a record format conversion and requires a reorganization. |
Multiple data sets and their spanning sets and subsets can be modified by compiling the DASDL description, running the BUILDREORG program, performing a DMALGOL REORGANIZATION compilation, and running the Reorganization program.
Most of the changes allowed as part of an update process can be made during a reorganization. These changes can be made to any structure, whether the structure is being reorganized. In addition, all the changes allowed during a file format conversion are allowed for the structure 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.