Following is a brief explanation of the main parts of the Lister Accessory report. Note that the report uses standard DMSII terms such as set, key, data type, offset, etc.
|
|
|
Dataset
|
Each data set is identified by its structure number and its name. In addition, the following information may appear:
|
|
Column
|
Description
|
|
Format level
|
The DMSII update (format) level.
|
|
RecType
|
The record type value for a variable format data set. Note that RecType does not appear for fixed format data sets.
|
|
RecSz
|
The size of the record in words. Words is a common way of expressing size on a ClearPath NX, LX, or A Series host. You can convert words into bytes as follows:
1 word = 6 bytes
|
|
MaxRecs
|
This is an upper bound record count estimate; it is not meant to be an accurate count of the records. Note that the MaxRecs count appears only when you set MAX RECORDS = TRUE.
|
Set
|
Sets are listed underneath their parent data set name and before its data item list, if included. Each set is identified by the set structure number and set name. Lister Accessory also reports if the set allows duplicates.
|
Subset
|
Subsets are listed after any sets and before the data item list, if included. Each subset is identified by the subset structure number and subset name. Lister Accessory also reports if the subset allows duplicates.
|
Key
|
Keys are listed underneath their set or subset. Descending keys will be labeled as “Descending.”
|
DataItems
|
The next several lines list the data items in the data set. The columns are explained in the following table.
|
|
Column Title
|
Description
|
|
Num
|
Data item number.
|
|
Name
|
Data item name. An asterisk (*) in front of the name indicates that it is a required item, i.e., it cannot be null.
|
|
Type
|
Type of data item, which can be one of the following: Number, Alpha, Binary, Boolean, Field, Group, Image, RecType, Link, and Kanji (for WIDE (n)).
|
|
Offset
|
Offset to the data item in digits (half-bytes). Offsets indicate the location of a data item in a record formatted by BINARYFORMAT. If the offset is a relative offset, rather than an absolute offset, a “+” precedes the number. Items within OCCURring groups have relative offsets. If the offset is a raw offset as opposed to a formatted offset, a "@" precedes the number.
|
|
Size
|
The physical size of the data item in 4-bit digits (half-bytes). Compare this to DecSz, which is a user declared size.
|
|
DecSz
|
The user declared size of the item in the length of the field. The units of length vary according to the field type, as follows:
NUMBER type is 4-bit digits (same as half-byte) ALPHA type is bytes GROUP is 0
Compare this to the Size column (explained above). The Size column shows the physical size of the data item in 4-bit digits.
|
|
Decs
|
If the data item is numeric, the Decs column shows the number of digits to the right of the assumed decimal point. If the numeric has no decimals, the Decs field is blank.
If the data item is Boolean, the Decs column shows the number of the bit within the four bit digit that contains the value of the Boolean. If the Decs field is blank, the bit number is zero.
|
|
Sign
|
If the data item is numeric, an S indicates it has a sign; if the numeric has no sign, the field is blank.
|
|
Occurs
|
The data item OCCURS value. For example, a data item called MONTH could occur 12 times.
|
|
Subs
|
The number of subscripts the data item requires for occurring items or groups. For example, an occurring data item within an occurring GROUP would have a SUBS = 2.
|
|
Target
|
The structure number referenced by a link item. The example Lister Accessory report does not show the Target column because Links were not enabled for the database.
|