Terminal Server

The aXes Terminal Server will create DBCS-capable devices when it is running on a DBCS-enabled version of IBM i. The QIGC system value indicates whether IBM i is DBCS enabled. If set to 1 the operating system is DBCS, if set to 0 the operating system is SBCS.

Note that IBM i V5R4 and above is always DBCS-capable thus aXes will always create DBCS devices by default.

The aXes Terminal Server will create a 5555-C01 device on DBCS-capable systems. You can specify the required workstation type globally using the DefaultWorkstationType= directive, or for a specific user on the user entry in the configuration file. See Section 1. Terminal Server Configuration for more information about these directives.

When a DBCS device is created the DBCS feature attributes are set automatically by IBM i based on the device keyboard type. However they are not changed when an existing device is reused even if they keyboard type is changed.
The following table shows the default DBCS features set for specific keyboard types:

 

Language

Keyboard Type

Keyboard Description

CS

CP

DBCS Feature

Japanese

JEB

Japan English

697

281

2424J4

 

JEI

Japan English Multinational

697

500

2424J4

 

JKB

Japan Kanji and Katakana

1172

290

2424J4

 

JPB

Japan Latin Extended

1172

1027

2424J4

 

JUB

Japan Kanji and

United States English

697

37

2424J4

 

KAB

Japan Katakana

332

290

2424J4

Korean

KOB

Korea

1173

833

2424K0

Chinese

RCB

Simplified Chinese

1174

836

2424S0

 

TAB

Traditional Chinese

1175

37

2424C0

If specific DBCS features are required for your application then specify the correct keyboard type and let aXes create new devices, or manually create the devices with the required DBCS feature and let aXes reuse the devices.

You can specify the required keyboard type globally using the DefaultKeyboardType= directive in the aXes-TS configuration file, or for a specific user on the user entry in the configuration file. See Section 1. Terminal Server Configuration for more information about these directives.

Input Method Editors

Dynamic HTML does not allow full control over the Input Method Editor (IME). aXes Terminal Server will activate the IME for the current language when the cursor enters a DBCS-capable or Katakana-shift field. Although aXes Terminal Server will activate the IME for Katakana-shift fields it cannot switch to Half-width Katakana input mode. The user must do that using the mouse or a keyboard shortcut.  Normally the IME is in Direct Input mode. For DBCS-Open and DBCS-Either fields, the IME will retain its previous setting. For DBCS-Only and DBCS-Graphic fields, the IME is switched to DBCS input for Chinese and Korean. If the current language is Japanese the IME is switched to Hiragana input.

Spool File Server

The aXes Spool File Server supports DBCS data if the CCSID of the spooled file can be determined. See Data Conversion for information on how Web Spooler performs data conversion.

PDF documents that contain DBCS data may require the Adobe Asian Fonts to be downloaded. Acrobat Reader will determine if these fonts are required when a PDF containing DBCS data is opened. A “Missing Components Found” message

box will be displayed asking if you want to download one of the Asian Fonts.

There are four categories of Asian Fonts supplied by Adobe:

Japanese    6.95 MB

Traditional Chinese    7.08 MB

Simplified Chinese    10.73 MB

Korean    4.11 MB

If you choose to not install the appropriate Asian fonts you will not be able to correctly view PDF documents that contain DBCS data.

If you have AFPDS or IPDS spooled files that contain DBCS data you will also need to install the IBM AFP DBCS Fonts/400 collection.

Data Explorer Server

The aXes Data Explorer Server supports DBCS data if the CCSID of the aXes-DE job is a DBCS CCSID. The CCSID is set by default to the value specified in the QCCSID system value. See Data Conversion for information on how Data Explorer performs data conversion.

 

Administrators

Legal Mentions

aXes is brought to you by:

LANSA

Serving the IBM i community for 30 years.