Updated: 11 December 1998 |
OpenVMS Record Management Utilities Reference
Manual
Previous | Contents | Index |
This attribute corresponds to the DAT_NCMPR option in the XAB$B_FLG field and should be set for DECnet for OpenVMS operations.
Duplicate alternate keys can be useful. For example, sorting a customer file on an alternate key of a postal code is a common application and one that requires duplicate keys.
When duplicate keys are not allowed, any attempt to write a record where the key would be a duplicate results in an error.
This attribute corresponds to the DUP option in the XAB$B_FLG field.
The INDEX_AREA, DATA_AREA, and LEVEL1_INDEX_AREA values are used when the data level and the index levels are placed in separate areas or when each key is placed in its own area.
This attribute corresponds to the XAB$B_IAN field.
This attribute corresponds to the IDX_NCMPR option in the XAB$B_FLG field and should be set for DECnet for OpenVMS operations.
The /FILL_BUCKETS qualifier to the CONVERT command overrides this attribute.
This attribute corresponds to the XAB$W_IFL field except that the XAB$W_IFL field contains a byte count, not a percentage.
This attribute corresponds to the XAB$B_SIZ0 field. Its value must be specified because there is no default.
When the data level and the index levels are placed in separate areas, or when each key is placed in its own area, use the LEVEL1_INDEX_AREA, DATA_AREA, and INDEX_AREA values.
This attribute corresponds to the XAB$B_LAN field.
This attribute corresponds to the XAB$L_KNM field.
In some databases, such entries are not desirable; some records will not contain a value for a particular alternate key. By allowing null keys, by declaring a null field, and by writing the null field as the alternate key for a record, you can include the record in the database.
A null key value is specified with the KEY NULL_VALUE secondary attribute. If a record has the specified null value in its alternate key field, a pathway to that record will not be made in the alternate index structure.
This attribute corresponds to the NUL option in the XAB$B_FLG field.
If the alternate key is a string data-type key, you can specify the null value either by enclosing the character in apostrophes or by specifying an unsigned decimal number denoting the character's ASCII value without enclosing characters.
The string data-type keys include STRING, DSTRING, COLLATED, and DCOLLATED. |
This attribute corresponds to the XAB$B_NUL field.
This attribute corresponds to the XAB$W_POS0 field.
Prolog 3 files accept multiple keys (or alternate keys) and all data types. They also give you the option of compressing your data, indexes, and keys. PROLOG 3 is the default.
On the other hand, Prolog 1 and 2 files do not allow these options. You should not specify Prolog 3 if the primary key is segmented and the segments overlap. If you want to use a Prolog 3 file in this case, consider defining the overlapping segmented key as an alternate key and then choosing a different key to be the primary key.
To specify a Prolog 3 file, assign the value 3 to this attribute. To specify a Prolog 1 or 2 file, assign the value 2. There is no perceivable difference between PROLOG 1 and PROLOG 2.
If you do not specify a value for this attribute, the utility that creates a data file from the FDL file uses the system or process default. To see these default values, enter the DCL command SHOW RMS_DEFAULT.
This attribute is not supported for DECnet for OpenVMS operations; the default prolog in effect at the remote node is used.
This attribute corresponds to the XAB$B_PROLOG field.
For Prolog 3 files, segments cannot overlap.
This attribute corresponds to the key size fields, XAB$B_SIZ0 to XAB$B_SIZ7.
This attribute corresponds to the positioning fields, XAB$W_POS0 to XAB$W_POS7.
The default key data type is STRING.
This attribute corresponds to the XAB$B_DTP field.
4.1.9 NETWORK Section
The NETWORK section sets run-time network access parameters. The following table lists the NETWORK secondary attributes and their default values. Note that all NETWORK secondary attributes are run-time attributes.
Secondary Attribute | Default Value |
---|---|
BLOCK_COUNT | Varies |
LINK_CACHE_ENABLE | YES |
LINK_TIMEOUT | 30 |
NETWORK_DATA_CHECKING | YES |
BLOCK_COUNT
A local node uses this numeric attribute to establish the size, in blocks, of a message buffer for messages between itself and a remote node. The value can be 0 to 127. By default, the local node uses the NETWORK BLOCK COUNT value for the process. If that value is 0, then the NETWORK BLOCK COUNT value for the system is used. Use the SHOW RMS command to see what the process and system values are for NETWORK BLOCK COUNT.The BLOCK_COUNT attribute corresponds to the XABITM item code XAB$_NET_BLOCK_COUNT, the requested block count.
LINK_CACHE_ENABLE
This switch enables logical link caching. It corresponds to the XABITM item code XAB$_NET_LINK_CACHE_ENABLE.LINK_TIMEOUT
This numeric attribute specifies the logical link timeout in seconds, from 0 to 65,535. It corresponds to the XABITM item code XAB$_NET_LINK_TIMEOUT.NETWORK_DATA_CHECKING
This switch enables data access protocol (DAP) level cyclic redundancy check (CRC). It corresponds to the XABITM item code XAB$_NET_DATA_CRC_ENABLE.
The RECORD section contains secondary attributes that define various controls for records. The RECORD keyword itself takes no value; it serves only to begin this section. The following table lists the RECORD secondary attributes and their default values. Note that all RECORD secondary attributes are create-time attributes.
Secondary Attribute | Default Value |
---|---|
BLOCK_SPAN | YES |
CARRIAGE_CONTROL | CARRIAGE_RETURN |
CONTROL_FIELD | 2 |
FORMAT | VARIABLE |
SIZE | No default |
BLOCK_SPAN
This switch determines whether records can span block boundaries in a sequential file. It corresponds to the BLK option in the FAB$B_RAT field.When the switch is set to NO, records cannot be larger than 512 bytes. When the space remaining in a block is insufficient to store the next record, RMS stores the next record in a new block.
CARRIAGE_CONTROL
This attribute corresponds to the FAB$B_RAT parameter and must be one of the following keywords:CONTROL_FIELD
This attribute specifies the size, in bytes, of the fixed-length control portion of VFC records. Its value must be a number in the range 1 to 255. The default value is 2.This attribute corresponds to the FAB$B_FSZ field.
FORMAT
This keyword attribute establishes the record format for the data file. Its value must be one of the following keywords:
FIXED Specifies fixed-length records. STREAM Specifies that the records are STREAM records; the record is viewed as a continuous stream of bytes, delimited by a special character. This format is compatible with RMS--11 stream files. This is valid for sequential files only. STREAM_CR Specifies that the records are STREAM records; the record is viewed as a continuous stream of bytes, delimited by a CR character. This is valid for sequential files only. STREAM_LF Specifies that the records are STREAM records; the record is viewed as a continuous stream of bytes, delimited by an LF character. This is valid for sequential files only. UNDEFINED Specifies undefined record format, which means that the record is a continuous stream of bytes with no specific terminator. This keyword is valid for sequential files only. VARIABLE Specifies variable-length records. This is the default setting. VFC Specifies variable-length records with fixed-length control fields (VFC). This is valid for sequential and relative files. This attribute corresponds to the FAB$B_RFM field.
SIZE
Sets the maximum record size in bytes.When used with fixed-length records, this value is the length of every record in the file.
When used with variable-length records, this value is the longest record that can be placed in the file. With sequential or indexed files, you can specify 0 and the system will not impose a maximum record length. (Note, however, that records in an indexed or relative file cannot cross bucket boundaries.)
When used with relative files, the SIZE attribute is used with the BUCKET_SIZE attribute to set the size of the fixed-length cells.
With VFC records, do not include the fixed control portion of the record in the SIZE calculation; only the data portion is set by this attribute. The RECORD CONTROL_FIELD attribute sets the size of the fixed control portion.
The fixed area is the size, in bytes, of the fixed-control portion of VFC records. Regular VFC records have a control field size of 0.
This attribute corresponds to the FAB$W_MRS field.
Table 4-1 gives the maximum record sizes, in bytes, for the various file organizations and record formats.
File Organization | Record Format | Maximum Record Size |
---|---|---|
Sequential | Fixed-length | 32,767 |
Sequential (disk) | Variable-length | 32,767 |
Sequential (disk) | VFC | 32,767 1 |
Sequential (disk) | Stream | 32,767 |
Sequential (disk) | Stream CR | 32,767 |
Sequential (disk) | Stream LF | 32,767 |
Sequential (ANSI Tape) | Variable-length | 9,995 |
Sequential (ANSI Tape) | VFC | 9,995 1 |
Relative | Fixed-length | 32,255 |
Relative | Variable-length | 32,253 |
Relative | VFC | 32,253-FSZ 1 |
Indexed, Prolog 1 or 2 | Fixed-length | 32,234 |
Indexed, Prolog 1 or 2 | Variable-length | 32,232 |
Indexed, Prolog 3 | Fixed-length | 32,224 |
Indexed, Prolog 3 | Variable-length | 32,224 |
Previous | Next | Contents | Index |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6027PRO_008.HTML
|