Problems?
If the 'hello' example doesn't work, one of the following problems
may be the cause:
-
You didn't install on a file system that supports long file
names (for example, on OS/2 or Windows NT you should use an
HPFS disk or equivalent). Like most Java applications, NetRexx
uses long file names.
-
You have a down-level Unzip or Tar program. Check that the
file 'Rexx.class', with just the 'R' as a capital letter,
exists in the subdirectory 'classes/netrexx/lang' or
'classes\netrexx\lang' below the Java home directory.
-
You have only the Java runtime installed, and not the toolkit. If
the toolkit is installed, you should have programs called javac,
javac, and jdb on your computer.
-
You have a down-level version of Java installed. The current
version is either 1.0.1 or 1.0.2, or later. You can check the
version you have using the command 'java -version'.
-
Your Java toolkit installation has .class files from an earlier
installation in classes/java/lang or other subdirectories. Try
reinstalling the Java toolkit in a clean subdirectory.
-
Your CLASSPATH variable is set incorrectly (try leaving it
unset, unless your Java installation instructions required that it
be set).
-
(This item applies to NetRexx 0.78, or earlier, only; NetRexx 0.79
has its own class loader.) There's a known problem under the Linux
JDK 1.0.1 and some other toolkits, where the compiler fails with a
missing class Agent, or is missing a method in the class
sun.tools.debug.Agent; it appears that in some toolkits the Agent
class is missing or is down-level (missing the Agent() constructor).
As a workaround, a true 1.0.1 Agent.class is included with the older
NetRexx files as Agent.class.101. To try this, copy that file to
the Java classes/sun/tools/debug directory, giving it the name
Agent.class; this should allow NetRexxC to work, though it may
affect the jdb debugger.
[ previous section | contents | next section ]
From 'nrinst.doc', version 0.81.
Copyright(c) IBM Corporation, 1996. All rights reserved. ©