Kbase P147482: How to debug problem with loading osmetrics.dll?
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  03/05/2010 |
|
Status: Verified
GOAL:
How to debug problem with loading osmetrics.dll?
GOAL:
Are there any debug programs for osmetrics.dll?
GOAL:
How to run debug programs for osmetrics.dll?
GOAL:
What is TestOSMetrics?
GOAL:
How to run TestOSMetrics
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.2x
OpenEdge 10.1C
OpenEdge Management
FIX:
On Unix:
1.start a proenv window
<OpenEdge install path>/bin/proenv
2. set the CLASSPATH
proenv> CLASSPATH=$DLC/java/progress.jar:$DLC/java/osmetrics.jar:$DLC/java/messages.jar; export CLASSPATH
3. set the shared library path:
proenv> SHLIB_PATH=$DLC/bin:$DLC/lib:$SHLIB_PATH; export SHLIB_PATH
SHLIB_PATH is for HPUX
LIBPATH for AIX
LD_LIBRARY_PATH for Solaris, Unixware, Linux
4. set appropriate variables:
proenv> AMS_DEBUG_FILE_ENV=[your directory]/osmetrics.log; export AMS_DEBUG_FILE_ENV
5. run the program
proenv> java -DInstall.Dir=$DLC com.progress.osmetrics.TestOSMetrics -all
On Windows:
1.Launch proenv from the Openedge Program group (Start>>Programs)
2. set appropriate variables:
proenv>set AMS_DEBUG_FILE_ENV=[your directory]\osmetrics.log
proenv>set CLASSPATH=%DLC%/java/progress.jar;%DLC%/java/messages.jar;%DLC%/java/osmetrics.jar
3.run the program:
proenv>java -DInstall.Dir=%DLC% com.progress.osmetrics.TestOSMetrics -all
The program will attempt to load all memory, cpu, filesystem, and disk hardware on the system and will attempt to poll them 3 times.
Output is written to stdout but a detailed log will be created in osmetrics.log in the directory you specified above.