KANJI1 support is deprecated. KANJI1 is not allowed as a default character set; the system changes the KANJI1 default character set to the UNICODE character set. Creation of new KANJI1 objects is highly restricted. Although many KANJI1 queries and applications may continue to operate, sites using KANJI1 must convert to another character set.
When the server character set is KANJI1 and the client character set is KanjiEBCDIC, the offset count includes Shift-Out/Shift-In characters, which are not matched, but treated as an indication of a transition from a single byte character and an multibyte character.
The nonzero position of the result is reported as follows:
| Character Set | Result |
|---|---|
| KanjiEBCDIC | Position of the first byte of the logical character offset (including Shift-Out/Shift-In in the offset count) within string_expression_1. |
| Other | Logical character offset within string_expression_1. |