Troubleshooting
Solutions to the following common problems are provided in this page:
Description: JET 3270 does not work correctly running
under Internet Explorer 3.0 or Communicator 4.04.
Cause: JET 3270 does not support these browsers, it supports
Internet Explorer 5 and 4.01 SP 1 and Netscape Communicator 4.7,
4.6, 4.5,
4.07 and 4.06.
Corrective Action: Run JET 3270 under Microsoft Internet Explorer
5 or 4.01 SP1 or Netscape Communicator 4.7, 4.6, 4.5, 4.07 or 4.06.
Description: After installing earlier versions of JET 1.0 or JET Any
Host then installing JET 3270, it does not work correctly.
Cause: The JET 3270 installation process does not remove old files
from the installation directory. These files can interfere with the
proper operation of the new version of JET 3270.
Corrective Action: Delete the installation
directory ("C:\jet3270" by
default) and reinstall JET 3270.
Description: Even though a new version of JET 3270 has been
successfully installed, JET 3270 is still behaving exactly as it did
for the previous version
Cause: Browsers store loaded applets in their memory, and continue to
use this code even if the Reload button is clicked, or the memory
and/or disk cache is cleared.
Corrective Action:
Restart your browser, and reload the web page or page on the local
hard drive that contains the reference to the JET 3270 applet.
Delete all old versions of JET software.
Description: Microsoft Internet Explorer was unable to load the JET
3270 applet.
Cause:
The browser has been configured to disable its Java support
The browser could not find the JET 3270 applet files on
the web
server or the local hard drive
A network communication error occurred while the browser was
loading the applet files
Corrective Action:
Enable Java support. To do this, from the "View" menu select
"Options...", select the "Security" tab. Click the "Enable Java
Programs" box (in the "Active content" area) so that a tick is placed
there.
Ensure that the <APPLET> tag within the web page that was
loaded correctly refers to
JET3270.class and
JET32704.cab. Refer to Configuration for more information.
Ensure that all of the JET 3270 class files are
correctly installed
on the web server or local hard drive
Ensure that there is a stable connection between the browser and
the web server
Description: The JET 3270 applet starts, and displays a screen
containing the text "Connecting...", but does not get any further.
Cause:
The Domain Name Server used by the browser may be down or unable to
resolve the name of the IBM host system.
There may be no TN3270 Server program listening
on the specified port
on the IBM host system.
A network Firewall may be preventing access to the IBM host
system.
Corrective Action:
Ensure that the Domain Name Server used by the browser is active and
able to resolve the name of the IBM host system.
Ensure that there is a Telnet Server program listening
on the port to
which the JET 3270 applet is trying to connect. The default port
number is 23. The <APPLET> tag that refers to the JET 3270
applet may
override this value by containing a <PARAM NAME="port" ....>
tag. Refer to
Configuration
for more information.
Ensure that there is no firewall preventing the system on which the
browser is running from reaching the IBM host system.
Description: The JET 3270 applet starts and
successfully connects to
the IBM host system, then displays a screen containing the text
"Negotiating Options...", but does not get any further.
Cause: The program listening on the port to which the
JET 3270 applet
has connected is probably not a compatible Telnet Server program.
Corrective Action: Ensure that a TN3270 server
program is listening.
Description: A dialog box with a message like "Could not execute
print command: [Ljava.lang.String;@805202f" appears after clicking
Print on the print dialog box when running JET 3270 under
Communicator on Linux. Clicking OK dismisses the dialog box but
the terminal screen is not printed.
Cause: Communicator for Linux does not support printing from Java
applets properly.
Corrective Action:
Login as root on the Linux machine. Create a /usr/bin/lp file with the
following contents: