Consider a BTEQ session with the ASCII client character set.
The data from the cunicode, csjis, and clatin columns are returned to the BTEQ session in ASCII, as illustrated by the following figure.
Note that your application should declare its variables as mixed single-byte strings to store the data from the database.
Because the ASCII repertoire is much smaller than the repertoires of cunicode or csjis columns, some characters might be converted to error characters on input, some might be converted to something else on export, or the transaction might abort.