Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (F)
Guardian Procedure Calls Reference Manual—522629-013
5-6
FILE_ALTERLIST_ Procedure
70 2 Refresh EOF. For disk objects other than SQL shorthand
views, a value of 1 if a change to the end-of-file value is to
cause the file label to be written immediately to disk; 0
otherwise.
78 2
Reset broken flag. Must be 0, indicating that the file is no
longer to be marked “broken”. For a partitioned file,
partonly
must be 1 when changing this attribute.
80 2 Secondary partition. For disk objects, a value of 0 indicates a
primary partition and a value of 1 indicates a secondary
partition.
The following four items are used for altering the partition description. You can alter
the partition description in these ways:
•
You can change the volume names of existing partitions.
•
For non-key-sequenced files, you can add new partitions.
•
For key-sequenced files, you can change the extent sizes of partitions.
The following items alter only the partition description in the primary file; no
secondary partitions are moved, updated, or created. The
partonly parameter
must be 0 to use these items. You must specify the items in this order: item 90, then
item 91 or 97, then item 92 or 98, and finally item 93 or 99.
90 2 Number of partitions. For disk objects, specifies the number
of extra (secondary) partitions the file is to have. The maximum
value is 15.
91 * Partition descriptors. An array of 4-byte values, one for each
secondary partition: Each entry has the following structure:
INT primary-extent-size;
INT secondary-extent-size;
These values give the primary and secondary extent sizes in
pages (2048-byte units). The length of this item in bytes is four
times the value of item 90.
92 * Partition-volume name-length array. An array of byte counts,
each of type INT, giving the length of each partition volume
name supplied in item 93.
Table 5-2. FILE_ALTERLIST_ Item Codes (page2of9)
Items in this table with a size of 2 bytes are of data type INT. The term “disk file”
applies only to Enscribe files. The term “disk object” applies to Enscribe files and
SQL objects.
Code
Size
(bytes) Description