M204.2451: Difference between revisions
(Automatically generated page update) |
m (add <var>'s) |
||
| Line 7: | Line 7: | ||
This message might be produced during SQL query compilation in the following cases:</P> | This message might be produced during SQL query compilation in the following cases:</P> | ||
<ul> | <ul> | ||
<LI>Field is ORDERED CHARACTER, but SQL column type is not CHARACTER.</LI> | <LI>Field is <var>ORDERED CHARACTER</var>, but SQL column type is not <var>CHARACTER</var>.</LI> | ||
<LI>Field is ORDERED NUMERIC, but SQL column type is CHARACTER.</LI> | <LI>Field is <var>ORDERED NUMERIC</var>, but SQL column type is <var>CHARACTER</var>.</LI> | ||
<LI>Field is KEY STRING, but SQL column type is not CHARACTER.</LI> | <LI>Field is <var>KEY STRING</var>, but SQL column type is not <var>CHARACTER</var>.</LI> | ||
<LI>Field is KEY or HASH, its datatype is BINARY or FLOAT, but SQL column type is CHARACTER.</LI> | <LI>Field is <var>KEY</var> or <var>HASH</var>, its datatype is <var>BINARY</var> or <var>FLOAT</var>, but SQL column type is <var>CHARACTER</var>.</LI> | ||
<LI>Field is KEY or HASH, its datatype is STRING, but SQL column type is not CHARACTER.</LI></ul> | <LI>Field is <var>KEY</var> or <var>HASH</var>, its datatype is <var>STRING</var>, but SQL column type is not <var>CHARACTER</var>.</LI> | ||
</ul> | |||
<p> | <p> | ||
<b>Response:</b> Avoid using such columns anywhere in query specifications except select column lists.</p> | <b>Response:</b> Avoid using such columns anywhere in query specifications except select column lists.</p> | ||
<p> | <p> | ||
<b>System manager response:</b> If possible, alter or recreate the table to change the column datatype, so that there are no datatype mismatches.</p> | <b>System manager response:</b> If possible, alter or recreate the table to change the column datatype, so that there are no datatype mismatches. | ||
</p> | |||
{{Template:M204.2451 footer}} | {{Template:M204.2451 footer}} | ||
<!-- skeleton as it was in pdf/BAD MAPPING OF SQL COLUMN tablename.columnname TO M204FIELD fieldname (DATATYPE MISMATCH)/--> | <!-- skeleton as it was in pdf/BAD MAPPING OF SQL COLUMN tablename.columnname TO M204FIELD fieldname (DATATYPE MISMATCH)/--> | ||
Latest revision as of 19:37, 19 March 2018
M204.2451 Bad mapping of SQL column token.token2 to M204 field token3 (datatype mismatch)
An SQL column is mapped to an indexed Model 204 field, but its SQL datatype is not consistent with the Model 204 datatype of the field. If such a column is used in a retrieval condition of an SQL request, the whole file resource is locked at evaluation time, and Table B is searched instead of indexed. If the file is large, substantial performance degradation results.
This message might be produced during SQL query compilation in the following cases:
- Field is ORDERED CHARACTER, but SQL column type is not CHARACTER.
- Field is ORDERED NUMERIC, but SQL column type is CHARACTER.
- Field is KEY STRING, but SQL column type is not CHARACTER.
- Field is KEY or HASH, its datatype is BINARY or FLOAT, but SQL column type is CHARACTER.
- Field is KEY or HASH, its datatype is STRING, but SQL column type is not CHARACTER.
Response: Avoid using such columns anywhere in query specifications except select column lists.
System manager response: If possible, alter or recreate the table to change the column datatype, so that there are no datatype mismatches.
Message attributes:
| RETCODEO=0 | Sets online return code |
|---|---|
| RETCODEB=0 | Sets batch (single user) return code |
| CLASS=I | Information class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter |
| AUDITAD | Writes the message with line type AD to the audit trail |
| NOCOUNT | Does not increment the error count (ERCNT) parameter |