Computers: Universe: Other VOC RecordsComputers: Universe: Other VOC RecordsIn addition to the types of VOC record we have discussed, you will come across a number of others, which I will list briefly here chiefly for the sake of completeness.
VOC records with M as the first character of their first fields are menu pointers, used to invoke UniVerse menus. To see them explained, turn to Menus of Commands.
As has been briefly mentioned, records in the dictionary of a UniVerse file are used to describe the contents or layout of the main or data records. Their main use is to name and describe the fields available via the Retrieve query language. For instance, the record CUSTOMER.NUMBER in the dictionary of an INVOICES file allows the term CUSTOMER.NUMBER to appear in Retrieve enquiries based on that file. Some dictionary records, though, could apply to many files: for instance, a dictionary item called RECORD.LENGTH reporting the length of a record in bytes could be useful, and no matter what fields are stored in a record, every record has a particular length. To avoid having to set up dictionary items such as RECORD.LENGTH in every dictionary, you can save them instead in the VOC file, where Retrieve will be able to use them regardless of the file you are enquiring about. For more information about dictionary records, turn to Dictionaries.
A few VOC records exist simply to store information or configuration details, rather than to support the UniVerse command language. These have an X at their beginning of their first field. One example, which you will find in every UniVerse account, is:
>ED VOC RELLEVEL
4 lines long.
----: P
0001: X
0002: 9.4.1.1
0003: INFORMATION
0004: INFORMATION.FORMAT
Bottom at line 4.
----: Q
>
Field 2 stores the release of UniVerse, and fields 3 and 4 define the 'flavour' of the UniVerse account (see UniVerse and PICK above),
X type VOC records should be used sparingly, or (preferably) not at all. The VOC file is central to the function and performance of the UniVerse account. Every additional X type makes the file larger and possibly slower to access, and removes a 'word' which would otherwise have been available to the UniVerse command language. If you find yourself planning many X type records, consider setting up a separate UniVerse file to store them, rather than littering the VOC with them.