Data Model > UNICOM Intelligence Data Model accessories > Metadata Model to Quantum > Getting started > Metadata Model to Quantum error codes
 
Metadata Model to Quantum error codes
The following lists provide details about the Metadata Model to Quantum error codes. Metadata Model to Quantum checks the card, column, and punch definitions when you run the Check Cols and Punches (see Checking the card, column, and punch definitions), Export Quantum Specification, and Export Data Map (see Using the Data Map) commands.
The column error codes are displayed in the Error Flag column in the Metadata Model to Quantum window. The punch code errors are shown in the Error Flag column in the Manual Allocation dialog box (see Allocating card, column, and punch Codes manually).
Notes
When Check Cols and Codes encounters a major column allocation error (such as C5 or C6) in a variable, it does not perform any punch code checks on that variable.
When Check Cols and Codes encounters more than one column allocation error in a variable, it records only the code of the first error found.
When Check Cols and Codes encounters more than one punch code error in an element, it records only the code of the first error found.
Column allocation errors
Code
Description
C0
Program error.
C1
Duplicate card and column number (it overlaps another variable).
C2
The column number overlaps the serial or card field.
C3
The column number is greater than the maximum card length.
C4
The card number that has been calculated contains more digits than can fit in the card number field.
C5
The start column is less than or equal to zero and is not -1, which would indicate a variable to be stored in the .dau file.
C6
The column count is less than zero.
C7
The allocations for a text variable that is to be stored in the .dau file are inconsistent. The CardStart and ColStart custom properties should both be set to -1 and the ColCount custom property should be set to 0.
C8
The column count is less than the number of columns required for this variable.
C9
The variable cannot fit onto the card. If you run Allocate Cols and Punches, the column count shows the number of columns required by the variable. Check the Card and Column preferences dialog box to see that the Number of Spare Columns for Categoricals text box has an appropriate value and that the Explode Multipunched Questions options has not been selected in an unsuitable file.
C10
This variable has punch code errors.
C11
This variable has been set up as an overflow variable which will be written to the .dau file. However, only text variables can be written to the .dau file and this is not a text variable.
C12
The value of Max card length in the Card and Column preferences dialog box has defined that a single card of infinite length is to be used, but the CardStart custom property for this variable has a non-zero value.
C13
The DataFormat custom property is invalid. The numeric and literal values are valid for single response categorical variables. The numeric and bitstring values are valid for multiple response categorical variables. The date and time formats are valid for datetime variables.
C14
The CodeWidth custom property is less than required.
Punch code errors
Code
Description
P1
No column offset has been specified.
P2
The column offset is greater than the column count for the variable.
P3
No punch code has been specified.
P4
The punch code is not in the punch mask used for allocation.
P5
This variable contains a duplicate punch code and column offset combination.
P6
This variable has been defined as a no-data variable, but it has card column allocations. These are not required.
P7
The punch or column offset is not consistent with those set for the first variable in the grid.
P8
The punch code is not 1 and the variable is set to write multiple response questions to multiple, single-coded columns.
P9
The Value custom property, or the value created using the column offset and punch, is not a number. A number is required if the DataFormat custom property is numeric or bitstring.
P10
This variable contains a duplicate Value custom property.
See also
Checking the card, column, and punch definitions
Metadata Model to Quantum window
Getting started