deployexpert created the topic: Troubleshooting in installanywhere
When running the installer against a 1.1.x VM, the Show Password Panel action will
not echo keyboard input as asterisks. A bug in certain Java 1.1.x implementations may
cause an installer to crash if the text field has the echo character set. If the Unix
installer is run against a 1.1.x VM, this panel will show the entered password as clear
The Show Choose Java VM Console action traces symbolic links for any data entered
as a path to a VM. This can lead it to display an unfamiliar path.
InstallAnywhere does not support pre-Java 2 Virtual Machines on RedHat 9. This is
due to a known problem caused by RedHat switching to a new threading model in this
z/OS and OS/390
z/OS and OS/390 use EBCDIC, instead of ASCII. InstallAnywhere installers work fine
on these platforms, but certain actions behave differently than developers may expect.
When files are installed, they are installed using a binary copy mechanism. Text files
are installed the same way. When building the installer on a Windows system to be
installed on z/OS, the text files will be installed in ASCII format. To have text files
installed in EBCDIC, first convert them using a tool like “native2ascii” (part of the
J2SE SDK), then add them separately to the installer. Use Check Platform rules on
both the ASCII text files and EBCDIC text files to indicate what platform the files
should be installed on.
Actions, such as Modify Text File, perform changes in the destination system’s
encoding. To have Modify Text File to make changes in ASCII, use a utility like
“native2ascii” to convert the file to ASCII after the Modify Text File action has