3.10.2 Notes on the Japanese-language environment

(1) About unsupported characters

Performance Management does not support the following double-byte characters:

If unsupported characters are used, alarms and reports will not execute normally. Also, unsupported characters might be displayed as question marks (?) or as garbled characters.

To Page Top

(2) About searching for character strings

Use wildcard characters, such as the asterisk (*) and question mark (?), to search for character strings.

If inequality signs, such as < and >, are used, the search might not be performed correctly because interpretation of these signs depends on the character encoding used by the host on which the target database is running. Therefore, do not use inequality signs, such as < and >, in search conditions.

To Page Top

(3) Notes on creating files

Be careful of the following if you include Japanese when you edit the initial settings file (config.xml) or when you create the command parameter file (XML file):

Note:

The following commands specify an XML file for the input file:

• jpcrdef create

• jpcrdef delete

• jpcrdef output

• jpcasrec update

• jpcasrec output

• jpcaspsv update

• jpcaspsv output

• jpcrpt

• If you edit the initial settings file (config.xml) or create a parameter file (XML file), specify "UTF-8", "shift_jis", or "euc-jp" for the encoding of the XML declaration described in the first line of the file.

• In files (XML files) that are output by the definition commands of jpcrdef output, jpcasrec output, or jpcaspsv output, the XML declaration is output with the encoding set to "UTF-8".

• When you edit the initial settings file (config.xml) with Notepad or create a command parameter file (XML file) with Notepad, if you save the encoding of the XML declaration in "UTF-8", BOM is added to the head of the file. This might cause the startup of the service of PFM - Web Console to fail or might cause an error when the command is executed. If you are using Notepad to create a file, follow the procedure below:

  1. Specify "shift_jis" for the encoding of the XML declaration of the parameter file (XML file).

  2. Specify "ANSI" character encoding when saving the file. If you are using a text editor other than Notepad, create the file so that the BOM is not added.

• If you use Notepad to edit a file (XML file) that is output by the definition commands of jpcrdef output, jpcasrec output, or jpcaspsv output, and then set it as a parameter file (XML file), follow the procedure above for creating files in Notepad.

• In XML documents and their file names, do not use the prohibited characters. For details about the prohibited characters, see 3.10.2(1) About unsupported characters.

To Page Top