DFS0123E DBD CHANGE UNSUPPORTED BY VERSIONING: DB=dedbname RSN=rc SEG segmname variable text
or
Explanation
An application program attempted to access a version of a Fast Path data entry database (DEDB) other than the current version, but IMS cannot build the internal blocks that are required to access non-current versions of the database, because the current version of the database contains a change in the database definition (DBD) that is not supported by database versioning.
Application programs cannot access any prior version of the database, unless the application programs are changed or the unsupported change is removed from the database.
- dedbname
- The name of the DEDB that contains the changes that are unsupported by database versioning.
- fld_name
- The name of the field that is associated with the unsupported change.
- rc
- The reason code that identifies the DBD change that is not supported by database versioning. Look up the return code in the following table for additional information about the unsupported change.
- segmname
- The name of the segment that is associated with the unsupported change.
- variable_text
- A short description of the change that is not supported by database versioning. Look up the return code in the following table for additional information about the unsupported change.
| RC | Variable text | Meaning |
|---|---|---|
| 01 | SEG segmname EXPECTED, FOUND SEG segmname INSTEAD | The order of the segments in the current version
of the database did not match the order in the requested version of
the database. A segment order mismatch can happen if any of the
following changes were made to the current version of the database:
IMS might also issue this message if the expected segment was skipped due to a previous error in the validation process. IMS issues this message for each segment it finds that is not the expected segment. |
| 02 | SEG segmname NEW | After validating all of the segments in the requested version of the database, the current version of the database contains an additional segment. |
| 03 | SEG segmname NOT FOUND | A segment in the requested version of the database
was not found in the current version. A segment might not be found
for any of the following reasons:
|
| 04 | SEG segmname INSERTION RULE CHANGED | The rule that specifies how data is inserted in this segment was changed. |
| 05 | SEG segmname COMPRESSION EXIT CHANGED | The compression exit routine for a segment was changed. |
| 06 | SEG segmname TYPE CHANGED | The type of the segment (Direct Dependent or Sequential Dependent) was changed. |
| 07 | SEG segmname SUBSET POINTER(S) CHANGED | The subset pointers were changed. |
| 08 | SEG segmname MINIMUM LENGTH CHANGED | The minimum length of the segment was increased or decreased. This message is also issued when a segment is changed from variable length to fixed length or vice versa. |
| 09 | SEG segmname MAXIMUM LENGTH DECREASED | The length of segment was decreased. |
| 10 | SEG segmname DATA CAPTURE EXIT CHANGED | One or more of the data capture exit routines was changed. |
| 11 | FLD fld_name NOT FOUND | A field in the old segment was not found in the current version of the segment. Either the field was deleted or a previous error caused it to be skipped. |
| 12 | FLD fld_name EXPECTED, FOUND FLD fld_name INSTEAD | While looking for a match to a field in the old segment version, a different field was encountered instead. This message is issued for each field that is encountered that is not the expected field. If the expected field was skipped due to a previous error, a message is issued for each of the remaining fields in the segment. |
| 13 | FLD fld_name OFFSET CHANGED | The offset of a field in the requested database was changed in the current version of the database. |
| 14 | FLD fld_name LENGTH CHANGED | The length of a field in the requested database was changed in the current version of the database. |
| 15 | FLD fld_name TYPE CHANGED | The type of padding was changed in the field. |
| 16 | FLD fld_name SEQUENCING CHANGED | The field was changed from sequenced to unsequenced or vice versa. |
| 17 | FLD fld_name OVERLAPS FLD fld_name | The field definitions in the current version of the database are incompatible with the field definitions of the requested database, because the offsets and lengths of two or more new fields in the current version of the database overlap each other. |
| 18 | SEG segmname MAX LENGTH OF VAR LENGTH SEG INCREASED | A variable length segment has increased in length. |
| 19 | SEG segmname SECONDARY INDEX RELATIONSHIP CHANGED | A segment changed from being involved in a secondary index to no longer being involved in a secondary index. |
| 20 | SEG segmname REFERENCED BY SECONDARY INDEX, CHANGED | A segments involved in a secondary index has increased in length or added new fields. |
| 21 | SEG segmname SDEP CHANGED | An SDEP has increased in length or added new fields. |
System action
IMS cannot build the internal blocks that are required to provide access to prior versions of the database. Only the most recent version of the database can be accessed.
IMS continues checking for other unsupported changes.
Programmer response
Determine whether you need to keep the changes in the database or remove them.
If you keep the changes in the database, existing application programs cannot access the database until they are modified to use the new database structure. The prior versions of the database cannot be accessed anymore.
If you need to remove the unsupported changes from the database, you need to recover the database to the prior version. Any updates to the database that were made by application programs that used the current version of the database will be lost.
The version numbers for the current version of the database and the version of the database that the application program was attempting to access are identified in message DFS0006E. Message DFS0006E is issued to the console after the last or only DFS0123E message.