Allowed Actions details the actions that can be performed during an update, reorganization, or modeling process. Numbers in parentheses refer to explanatory notes following the table.
Table 25. Allowed Actions
|
Option |
Model |
Update |
File Format Conversion (No Item Changes) |
|
|---|---|---|---|---|
|
Add new disjoint data set. |
No |
Yes |
Yes |
|
|
Add new embedded data set. |
No |
Yes (2) |
Yes (2) |
|
|
Delete existing disjoint data set. |
No |
Yes (1,5) |
Yes (1, 5) |
|
|
Delete existing embedded data set. |
No |
No |
Yes (1,4) |
|
|
Change data set name. |
No |
No |
No |
|
|
Change data set type. |
No |
No |
No |
|
|
Change order in which items are declared. |
No |
No |
No |
|
|
Add, change, or delete verify condition. |
No |
No |
Yes (3) |
Yes (3) |
Explanatory Notes
-
When an embedded data set is deleted, it must also be eliminated from all remaps which include it.
Any program that attempts to use a deleted data set receives a VERSIONERROR #2 error. Note that you cannot delete the restart data set.
-
Embedded data sets can be added if the master data set is added at the same time.
-
When a new VERIFY condition is specified or the existing VERIFY condition is changed, the user must ensure that all existing records satisfy the new VERIFY condition. If the Reorganization program encounters a record that does not satisfy the new VERIFY condition, it terminates with an exception.
-
Embedded data sets can be deleted, regardless of whether the master data set is deleted at the same time.
-
When the structure with the highest number has been deleted from the database schema (DASDL), the application programs that have not been recompiled might receive an OPEN ERROR 17. The error results from invoking the deleted structure and occurs regardless of whether the application actually uses the structure. OPEN ERROR 17 messages continue to occur as long as the number of the highest structures invoked by the program is greater than the number declared in DASDL.
An error can also occur when the application does not specify the deleted structure for some operation. If a subsequent DASDL update process adds a new structure and reuses the number from the previously deleted structure, the application receives a VERSION ERROR 2.
You can avoid these errors by recompiling the program.
