Fast/Unload with the Sir2000 Field Migration Facility: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
(Automatically generated page update) |
||
| Line 15: | Line 15: | ||
of a RELATED pair of fields are always unloaded. | of a RELATED pair of fields are always unloaded. | ||
<li>If <b><i>UAI SORT field_R</i></b> or <b><i>HASH field_R</i></b> | <li>If <b><i>UAI SORT field_R</i></b> or <b><i>HASH field_R</i></b> | ||
causes <b><i>field_R</i></b> to be implicitly unloaded (see [[#uaif1|UAI SORT or HASH and field unload order]]), | causes <b><i>field_R</i></b> to be implicitly unloaded (see [[Fast/Unload Extraction Language (FUEL)#uaif1|UAI SORT or HASH and field unload order]]), | ||
and <b><i>field_R</i></b> is a RELATED field, then any UNLOAD field statement | and <b><i>field_R</i></b> is a RELATED field, then any UNLOAD field statement | ||
causes the other field of the RELATED | causes the other field of the RELATED | ||
Revision as of 19:40, 15 January 2015
For the most part, the presence of a file which has been modified with the Sir2000 Field Migration Facility has no effect on Fast/Unload processing. The exceptions are as follows:
- The ADD, CHANGE, and DELETE statements may not be issued for a RELATED field.
- When doing an unload with UAI, the Fast/Unload output contains all of the Sir2000 Field Migration Facility definitions, which can be used to recreate them during the Fast/Reload LAI operation.
- The UNLOAD field statement, if it references a RELATED field, will cause the other of the pair of RELATED fields to be unloaded. This ensures that if a partial record is unloaded, both occurrences of a RELATED pair of fields are always unloaded.
- If UAI SORT field_R or HASH field_R causes field_R to be implicitly unloaded (see UAI SORT or HASH and field unload order), and field_R is a RELATED field, then any UNLOAD field statement causes the other field of the RELATED pair to also be implicitly unloaded, after field_R.