Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (F)
Guardian Procedure Calls Reference Manual—522629-013
5-53
FILE_CREATELIST_ Procedure
198 4 Key offset (32-bit). For key-sequenced disk files, the byte offset
from the beginning of the record to the primary key field. This
an alternate form for item 45; one of the two items is required
for key-sequenced files.
199 4 Primary extent size (32-bit). The size in pages (2048-byte
units) of the first extent. If omitted or 0, a size of 1 is used. The
value can be rounded during creation to a multiple of the block
size. For Format 1 files, the size must be less than 65,536.
This is an alternate form for item 50.
200 4 Secondary extent size (32-bit). The size in pages (2048-byte
units) of extents after the first extent. If 0 or omitted, the size of
the primary extent is used. The value can be rounded during
creation to a multiple of the block size. For Format 1 files, the
size must be less than 65,536. This is an alternate form for
item 51.
212 2 Block checksumming option. For Format 2 structured files,
specifies whether data protection needs to be used through
checksum calculation and comparison (1 specified if needed
and 0 if not needed). If omitted or -1 is specified, the default
value 1 is used. This item is ignored for files that do not support
a checksum option.
221 * Partition maximum extents array. This item is an array of INT
values that specify the maximum extents for each secondary
partition. This item is optional and can only be specified for key-
sequenced files. If present, it must be supplied at some point
after item 90 (number of partitions) and item 41 (file type). If this
item is not present, FILE_CREATELIST_ will use the maximum
extents value for the file (item 52) and apply it to each
secondary partition. The length of the item is 2 times the
number of partitions (item 90).
Table 5-3. FILE_CREATELIST_ Item Codes (page 12 of 12)
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.
Item
Code
Size
(Bytes) Description