MSIR.0254 Invalid COLUMN numbers for TABLE (tabname): Difference between revisions
mNo edit summary |
(Automatically generated page update) |
||
| Line 5: | Line 5: | ||
<p class="note"><b>Note:</b> The column numbers don't have to appear in sequential order in the file, since the <var class="product">Janus Specialty Data Store</var> sorts the records by COL_NUM before processing them. It is only essential that, once sorted, the COL_NUM values go from 1 to the number of columns. </p> | <p class="note"><b>Note:</b> The column numbers don't have to appear in sequential order in the file, since the <var class="product">Janus Specialty Data Store</var> sorts the records by COL_NUM before processing them. It is only essential that, once sorted, the COL_NUM values go from 1 to the number of columns. </p> | ||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] [[Category:MSIR.0200 - MSIR.0399]] | ||
Revision as of 15:49, 13 August 2015
This message indicates that a table was defined in the JANCAT file for a Janus Specialty Data Store port, but the column number field (COL_NUM) in the column descriptor records (RECTYPE=C) for that table did not go from 1 to the number of columns in the table. While the port is started (or reloaded) in spite of the error, the indicated table is marked as invalid and is not usable after this error.
This error is indicative of an error in an ad hoc or user application run against the JANCAT file or a bug in the JANCAT application. In the former case (and maybe even the latter) correct the data in the JANCAT file with another ad hoc or restore the JANCAT file to the state it was in before the bad data was added to the file. In the latter case, call Technical Support.
Note: The column numbers don't have to appear in sequential order in the file, since the Janus Specialty Data Store sorts the records by COL_NUM before processing them. It is only essential that, once sorted, the COL_NUM values go from 1 to the number of columns.