Alternate character sets

Overriding Codepage

Alternate codepages may be loaded by XCICS using the load directive.

Specified codepage must be an absolute path name to a table file.

This table file must be a 512 bytes length sequential file, containing on the first 256 bytes the ASCII to EBCDIC translation values and on the second 256 bytes the EBCDIC to ASCII values. I.e. the file at offset 0x20 (ASCII blank) contains 0x40 (EBCDIC blank), while at offset 0xFF+0x40 contains 0x20.

Codepages may be loaded for whole CICS (load codepage) or only for BMS routines (load bms_codepage).

Syntax

load codepage=<table>
load bms_codepage=<table>

Example

load codepage=$XFRAMEHOME/etc/IBM930.tbl;

Example XFRAME codepage tables are deployed with XFRAME and may be found in $XFRAMEHOME/etc with ".tbl" extention.

The human readable sources for the codepage tables deployed with XFRAME may be found in $XFRAMEHOME/tools with .cpg extention.

If the need for a new codepage arise, user may create its own codepage source starting from one of those provided, editing it and the converting it to an XFRAME codepage table using the script $XFRAMEHOME/tools/cpg2tbl.ksh.

Specifying DBCS conversion table

If application requires a DBCS conversion table, it may be loaded using load dbcs_table directive

Specified DBCS table must be an absolute path name to a table file.

Syntax

load dbcs_table=<table>

Example

load dbcs_table=$XFRAMEHOME/etc/IBM-Kanji.tbl;

Example XFRAME DBCS tables are deployed with XFRAME and may be found in $XFRAMEHOME/etc with ".tbl" extention.

The human readable sources for the codepage tables deployed with XFRAME may be found in $XFRAMEHOME/tools with .dbcs extention.

If the need for a new DBCS conversion table arise, user may create its own codepage source starting from one of those provided, editing it and the converting it to an XFRAME DBCS table using the script $XFRAMEHOME/tools/dbcs2tbl.ksh.