Quantum DSC: Troubleshooting
I use a Data Management Script to transfer data to a Quantum file. When I ran the script after upgrading to version 3.0 of the UNICOM Intelligence Data Model, I found that the card and column allocations are not the same as before.
This may occur if the following conditions are all true:
▪You are generating card and column allocations in the OnAfterMetaDataTransformation event section.
▪The InputDataSource section in your Data Management Script contains a SelectQuery statement that refers to columns by name (rather than just “Select * From …”).
▪The order of the columns in the SelectQuery statement is different from the order of the variables in the input metadata.
▪{} (not answered) is used with categorical questions. {} (not answered) is written as NULL (not asked) by the Quantum DSC and as a result, these values are not included in the base when tabulating.
The problem occurs because in versions of the UNICOM Intelligence Data Model prior to version 3.0, the order of variables in the output was determined by the order of the columns in the SelectQuery statement. However, In version 3.0 of the UNICOM Intelligence Data Model, the order of variables in the output is determined by the order of the variables in the input metadata. This may result in card and column allocations that are different from before.
Workaround: Generate card and column definitions in the OnBeforeJobStart event section instead of the OnAfterMetaDataTransformation event section. Alternatively, pre-allocate card and column information using
Metadata Model to Quantum before you run your data transfer. In addition, do not use the data transfer to create new variables. Instead, define them in the input metadata before using Metadata Model to Quantum to allocate card and column information.
See also