JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2.1

Localized-Message String Format
A localized message file contains strings in the following form:
message=message_text
For example:
driver_err_error_from_server_msg=An error was returned from the server.
Error: {0} Error detail: {1}
where the message is driver_err_error_from_server_msg. The message_text is: An
error was returned from the server. Error: {0} Errordetail: {1}
The pattern {n} in message_text, where n equals 1, 2, 3, and so forth, is a placeholder that
is filled in at run time by the Type 4 driver. Any translation must include these placeholders.
Creating a Localized-Message File
1. Extract the SQLMXMesseges_en.properties file, which is in the t4sqlmx.jar file. For
example from a UNIX prompt, use the jar Java tool:
jar -x SQLMXMessages_en.properties < t4sqlmx.jar
2. Copy the file.
3. Edit the file and replace the English text with the text for your locale.
4. Save the file, giving it a file name that meets the naming requirements described under
File-Name Format for Localized Messages.
5. Put the file in a directory anywhere in the class path for running the JDBC application.
The new messages file can be anywhere in the class path for running the user application.
At run time, if driver cannot read the messages property file, the driver uses the message portion
of the property as the text of the message. For a description of the message portion, see the
Localized-Message String Format.
At run time, if the Type 4 driver cannot read the messages property file, it sets the locale to English
locale, thereby loading the default properties file that is shipped with the Type 4 Driver. The default
properties file, SQLMXMessages_en.properties, fetches the error messages and status
messages.
32 Accessing SQL Databases with SQL/MX