IBM Time Zone Update Utility (JTZU): known problems and diagnostic information

• JTZU failed to update a single JVM on Windows
• JTZU cannot find JTZU.jar
• JTZU exits with the message 'TimeZone info not found'
• JTZU fails to load a library, either <something>.lib or <something>.a
• JTZU fails to patch a VM, the log reports failure to copy 'TimeZone.class'
• After running JTZU under superuser permissions, a lower-privileged user can not use the SDK or JRE

• Collecting information required for further assistance

JTZU patches one of the Java binaries. On Windows systems, binaries that are in use are locked and cannot be updated. If you attempt to use JTZU to patch the SDK or JRE that you are using to run JTZU, JTZU will fail.
To work around this problem, run JTZU with a different SDK or JRE. If you do not have another SDK or JRE available, duplicate the JRE you are using to run JTZU.

JTZU uses relative path names to find installation files. Try running JTZU from the directory it was installed into.

There are two possible reasons for this problem:
1. JTZU is not installed correctly. There should be a TimeZoneInfo sub-directory within the JTZU installation directory. If the TimeZoneInfo sub-directory is missing, re-install JTZU. Check that your extract tool is set to extract sub-directories.
2. You are not running JTZU using runjtzu.bat (Microsoft® Windows®) or runjtzu.sh (other platforms). This script sets up the correct environment for JTZU to find the data it needs. Run JTZU using the supplied script.

You are not running JTZU using runjtzu.bat (Microsoft® Windows®) or runjtzu.sh (other platforms). This script sets up the correct environment for JTZU to find the data it needs. Run JTZU using the supplied script.

You are not running JTZU using runjtzu.bat (Microsoft® Windows®) or runjtzu.sh (other platforms). This script sets up the correct environment for JTZU to find the data it needs. Run JTZU using the supplied script.

Where JTZU patches SDKs or JREs using the superuser or 'root' account, the updated files are created with the umask of the privileged account. If the umask is secured, the updated files will be inaccessible when using a lower-privileged account. This can stop lower-privileged users from using the Java system.

To restore the correct ownership, group access, and permissions to the newly patched content, change the permissions to match the parts of the SDK or JRE that were unchanged.

Alternatively, when performing the patching of JREs, use the user account that owns that JRE instead of patching under the identity of the superuser profile. Where possible, run JTZU under the superuser account to discover all the SDKs and JREs on the system, then partition the SDKList.txt to patch JREs and SDKs using account of the SDK or JRE owner.

Collecting information required for further assistance

To diagnose JTZU problems, obtain the following files from the JTZU directory and email this information to jtzu@uk.ibm.com.

1. The JTZU log file Logfile.log.
2. The directory search file DirectorySearch.txt.
3. The SDKList.txt file, if present.
4. The JTZU settings file, runjtzuenv.bat (Microsoft® Windows®) or runjtzuenv.sh (other platforms). Copy and paste the contents of this file into the email because batch and script files are often stripped from emails.
5. The output of java -version, run from the JTZU directory.