Guardian Procedure Calls Reference Manual

Item Codes
Table 15 lists the item codes for the file attributes that may be specified in item-list.
NOTE: 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.
Table 15 FILE_ALTERLIST_ Item Codes
DescriptionSize (Bytes)Code
File code. For disk objects other than SQL shorthand views, an application-defined value
associated with the file. File codes 100 to 999 are reserved for use by HP.
242
Expiration time. For disk objects other than SQL shorthand views, the Julian GMT timestamp
giving the time before which the file cannot be purged.
857
Odd unstructured. For unstructured files, causes the file to allow odd-byte positioning and
transfers. The supplied value must be 1. Once this attribute is set for a file, it cannot be reset.
265
Audited file. A value of 1 if the file is to be a TMF-audited object; 0 otherwise. Must be 0 for
systems without the TMF subsystem. Unless partonly is 1, all alternate-key files and all
partitions are changed.
266
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.
270
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.
278
Secondary partition. For disk objects, a value of 0 indicates a primary partition and a value
of 1 indicates a secondary partition.
280
Items 90 through 99 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.
• For enhanced key-sequenced files, you cannot change the extent size of the primary partition of the file.
These 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.
Number of partitions. For disk objects, the number of extra (secondary) partitions for the file.
The maximum value is 15 for legacy key-sequenced files, 63 for enhanced key-sequenced files
290
in RVUs between H06.22/J06.11 and H06.28/J06.17, and 127 for enhanced key-sequenced
files with increased limits in H06.28/J06.17 RVUs with specific SPRs and later RVUs. (For a
list of the required H06.28/J06.17 SPRs, see SPR Requirements for Increased Enscribe Limits
for the H06.28/J06.17 Release (page 31).)
Partition descriptors. An array of four-byte values, one for each secondary partition: Each entry
has this structure:
INT primary-extent-size;
INT secondary-extent-size;
*91
These values give the primary and secondary extent sizes in pages (2048-byte units). For a
format 1 legacy key-sequenced file, the maximum extent size is 65,535 pages; for a format
2 legacy key-sequenced file, the maximum extent size is 536,870,912 pages. For an enhanced
key-sequenced file, the maximum extent size is 536,870,912 pages, and the primary partition
must have a primary extent size of at least 140 pages. The length of this item in bytes is four
times the value of item 90. Item 97 is an alternate form for this item.
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. Item 98 is an alternate form for this
item.
*92
348 Guardian Procedure Calls (F)