Package name considerations in mixed code page environments

Package names are determined when you invoke the PRECOMPILE PROGRAM command or API. By default, they are generated based on the first 8 bytes of the application program source file (without the file extension) and are folded to uppercase. Optionally, a name can be explicitly defined. Regardless of the origin of a package name, if you are running in an unequal code page environment, the characters for your package names should be in the invariant character set. Otherwise you might experience problems related to the modification of your package name. The database manager cannot find the package for the application or a client-side tool cannot display the correct name for your package.

A package name modification due to character conversion occurs if any of the characters in the package name are not directly mapped to a valid character in the database code page. In such cases, a substitution character replaces the character that is not converted. After such a modification, the package name, when converted back to the application code page, might not match the original package name.

To avoid conversion problems with package names, use only characters which are valid under both the application and database code pages.