Custom character codes

HULFT handles codes other than the default supported double byte codes as custom character codes.

For details on the double byte codes that HULFT supports by default, refer to Double byte codes supported by HULFT.

 

HULFT converts custom character codes by using a custom character table.

The user needs to register pairs of one input code and one output code each in a custom character table in advance.

HULFT refers to the custom character table, and if the target codes are registered as input codes in the custom character table, converts target codes into the corresponding output codes.

 

In HULFT, when you want to convert double byte codes including custom characters, you must specify a setting for Use Custom Character Table in the System Environment Settings.

The setting of Use Custom Character Table in the System Environment Settings varies depending on host type, as shown below.

HULFT for Mainframe

You can select one of the following options:

0:

Convert custom character codes to relevant codes by referring to the custom character table

1:

Convert to relevant codes by referring to the custom character table first

If you select '1' above, HULFT refers to the custom character table first even when converting double byte codes that HULFT supports by default.

When you want to convert custom characters, make sure to use the DD statement for XREXTLIB to specify HULFT load module library that stores the custom character table.

If you do not specify XREXTLIB, HULFT does not convert custom characters.

HULFT for IBMi, HULFT for UNIX/Linux, HULFT for NSK, and HULFT for Windows

You can select one of the following options:

0:

Convert all the custom character codes to default codes ('') without using the custom character table

1:

Convert custom character codes to relevant codes by referring to the custom character table

2:

Convert to relevant codes by referring to the custom character table first

If you select '2' above, HULFT refers to the custom character table first even when converting double byte codes that HULFT supports by default.

 

To allow HULFT to return an error if the input codes to be converted are not registered in the custom character table, specify the appropriate field in the System Environment Settings, as shown below:

Product Name	System Environment Settings
	Field Name	Tag Name
HULFT for Mainframe	Handling of Unregistered Custom Characters	GAIJIERR
HULFT for IBMi	Handling of Unregistered Custom Characters	GAIJIERR
HULFT for UNIX/Linux	Handling of Unregistered Custom Characters	gaijierr
HULFT for NSK	Handling of Unregistered Custom Characters	gaijierr
HULFT for Windows	Handling of Unregistered Custom Characters	gaijierr

 

When you create a custom character table, you can use one of the Custom Character Conversion Template files that HULFT provides.

For certain characters, HULFT provides sample pairs of input codes and corresponding output codes that you can add to a custom character table for Code-set Conversion for Japanese. These samples are provided in Custom Character Conversion Template files. The relevant characters are the following:

• NEC special characters

• Certain characters in the JIS2004 standard

On some host types, HULFT does not provide the Custom Character Conversion Template files that you can use for the above characters.

Table 1.12 Custom Character Conversion Template

Conversion Type	Type	Host Type
		Mainframe	IBMi	UNIX/Linux	NSK	Windows
Code-set Conversion for Japanese	NEC special characters	✓	✓	✓	✓	✓
	Certain characters in the JIS2004 standard	-	✓	✓	✓	✓
Code-set Conversion for Chinese	Not provided	-	-	-	-	-

✓	:	Provided
-	:	Not provided