8.2.2 Maximum number of characters that can be defined for items when converting the character encoding to a UTF-8 environment
In a UTF-8 environment, multi-byte characters such as Japanese are represented by using more bytes than are used in Japanese locales that are not UTF-8. By default, the maximum number of bytes that can be specified for each item of a unit does not depend on the character encoding. Therefore, the maximum number of characters that can be used for definitions in the UTF-8 environment is less than the information defined in Japanese locales that are not UTF-8.
You can set up the embedded database to permit the same number of characters used in a Shift-JIS environment to be used in the UTF-8 environment for the specification of definition items such as a unit name. This setting is available for the following combinations of OSs and JP1/AJS3 - Manager versions:
-
Linux and JP1/AJS3 - Manager 09-50-01 or later
-
OS Solaris 11 and JP1/AJS3 - Manager 10-00-03 or later
-
AIX or HP-UX, and JP1/AJS3 - Manager 10-50-01 or later
For details, see 15.1.10 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- Cautionary notes
-
-
If you set up the embedded database to use the same number of characters that are used in a Shift-JIS environment to specify definition items such as unit names, the maximum number of nesting levels is 10. Therefore, a unit consisting of ten or more levels cannot be migrated to a UTF-8 environment. If you want to migrate such units, you need to change the unit configuration beforehand.
-
Migration to a UTF-8 encoding environment must be performed in the standard configuration. For an environment upgraded from JP1/AJS2 - Manager, perform the migration after changing the configuration to the standard configuration.
For details about how to change the configuration to the standard configuration, see 8.5 Upgrading JP1/AJS2 - Manager to JP1/AJS3 - Manager.
-