M204.2452: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (add <var>'s) |
||
| Line 1: | Line 1: | ||
{{Template:M204.2452 skeleton}} | {{Template:M204.2452 skeleton}} | ||
<P>A Model 204 field is indexed, but this index cannot be used in SQL applications, because the SQL datatype of a column mapped to the field does not match the field datatype.</P> | <P> | ||
<P>This message might be produced during SQL query compilation in the following cases:</P> | A Model 204 field is indexed, but this index cannot be used in SQL applications, because the SQL datatype of a column mapped to the field does not match the field datatype.</P> | ||
<ul><LI>Field is | <P> | ||
This message might be produced during SQL query compilation in the following cases:</P> | |||
<ul> | |||
<LI>Field is <var>ORDERED CHARACTER</var>, but SQL column type is not <var>CHARACTER</var>.</LI> | |||
<LI>Field is <var>ORDERED NUMERIC</var>, but SQL column type is <var>CHARACTER</var>.</LI> | |||
<LI>Field is <var>KEY STRING</var>, but SQL column type is not <var>CHARACTER</var>.</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 <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> | |||
<b>Response:</b> Notify the System Manager.</p> | |||
<p> | |||
<b>System manager response:</b> If possible, redefine the field, or alter or recreate the table to change the column datatype, so that there is no datatype mismatch. | |||
</p> | |||
{{Template:M204.2452 footer}} | {{Template:M204.2452 footer}} | ||
<!-- skeleton as it was in pdf/INDEX FOR indextype FIELD fieldname CANNOT BE USED IN SQL QUERY PROCESSING/--> | <!-- skeleton as it was in pdf/INDEX FOR indextype FIELD fieldname CANNOT BE USED IN SQL QUERY PROCESSING/--> | ||
Latest revision as of 19:41, 19 March 2018
M204.2452 Index for token field token2 cannot be used in SQL query processing
A Model 204 field is indexed, but this index cannot be used in SQL applications, because the SQL datatype of a column mapped to the field does not match the field datatype.
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: Notify the System Manager.
System manager response: If possible, redefine the field, or alter or recreate the table to change the column datatype, so that there is no datatype mismatch.
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 |