Guardian Procedure Calls Reference Manual

Table 17 FILE_CREATELIST_ Item Codes (continued)
DescriptionSize
(Bytes)
Item
Code
Lock-key length. For key-sequenced files, the generic lock-key length. The length must be between
1 and the key length of the file, or can be 0 to automatically use the key length of the file. The
length must be 0 for non-key-sequenced files.
247
Primary extent size. For disk objects other than SQL shorthand views, an unsigned integer specifying
the size of the first extent, in pages (2048-byte units). The maximum extent size is 65,535 pages
250
(134,215,680 bytes). If this item is omitted or is equal to 0, a size of 1 is used. The value might
be rounded up to an even number during file creation. Item 199 is an alternate form for this item.
Secondary extent size. For disk objects other than SQL shorthand views, an unsigned integer
specifying the size of extents after the first one, in pages (2048-byte units). The maximum extent
251
size is 65,535 (134,215,680 bytes). (A file can have up to 15 secondary extents allocated.) If this
item is omitted or equal to 0, the primary extent size is used. The supplied value might be rounded
up to an even number during file creation.
Maximum extents. For disk objects other than SQL shorthand views, the maximum number of extents
allowed for the file. The minimum and default value is 16. See the FILE_CREATE_ procedure
252
Considerations (page 389). (For partitioned files that are not key-sequenced, the only value permitted
is 16.)
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, a value of 1 specifies that I/O transfers are to occur with
the exact counts specified; a value of 0 specifies that transfers are to be rounded up to an even
265
byte boundary. Must be equal to 0 for other file types. The default value is 0. See Considerations
(page 400).
Audited file. A value of 1 specifies that the file is to be audited by the Transaction Management
Facility (TMF) subsystem; 0 otherwise. Must be 0 for systems without the TMF subsystem. The default
value is 0.
266
Audit compression. For audited disk objects other than SQL shorthand views, a value of 1 specifies
that the audit data is to be compressed; 0 specifies otherwise. The default value is 0.
267
Data compression. For key-sequenced disk objects, a value of 1 specifies that the primary keys of
data records are to be compressed; 0 specifies otherwise. Must be 0 for other file types. Can be
1 only if key offset (item 45) is 0. The default is 0. See Considerations (page 400).
268
Index compression. For key-sequenced disk objects, a value of 1 specifies that index block entries
are to be compressed; 0 otherwise. Must be 0 for other file types. The default value is 0. See
Considerations (page 400).
269
Refresh EOF. For disk objects other than SQL shorthand views, a value of 1 specifies that a change
to the end-of-file value is to cause the file label to be written immediately to disk; 0 specifies otherwise.
The default value is 0.
270
Create options. For disk objects, miscellaneous file attributes in the form that FILE_CREATE_ accepts
and is an alternative to using items 65 to 70. To use this item, specify attributes as described under
271
the options parameter of FILE_CREATE_. If you specify any of items 65 to 70, and if you also
specify item 71, the last item to appear takes precedence. The default value is 0. See Considerations
(page 400) for queue files. See Considerations (page 400) for index and data compression with
increased limits.
Write through. For disk objects, a value of 1 specifies write-through caching; a value of 0 specifies
that writes to the file are to be buffered. If omitted, 1 is used for unaudited files and 0 is used for
272
audited files. CAUTION: If writes to an unaudited file are buffered, one or more changes to the file
can be lost if a failure occurs that affects the disk or disk process.
Verify writes. For disk objects other than SQL shorthand views, a value of 1 indicates that the file
label is to specify that writes to the file should be read back and the data verified; 0 indicates
otherwise. If omitted, 0 is used.
273
Serial writes. For disk objects other than SQL shorthand views, a value of 1 indicates that the file
label is to specify that writes are to be made serially to the mirror when a file resides on a mirrored
274
FILE_CREATELIST_ Procedure 395