Monitor Client can't retrieve performance data

Hi all,

I post it for the second time. Does anybody have an idea.

I have followed the guidance to set classpath and path, here is all of my 
settings.

set CLASSPATH=c:\jdk1.1.8\lib.classes.zip;
c:\sybase\ASEP\monclass.zip;c:\sybase\ASEP\3pclass.zip;%CLASSPATH%

set 
PATH=c:\jdk1.1.8\bin;c:\sybase\ASEP;c:\sybase\dll;c:\sybase\OCS-12_0\dll;%PATH%
set PATH=%PATH%;c:\sybase\SYSDLL
set PATH=%PATH%;c:\sybase\Sybase Central 3.2\win32
set PATH=%PATH%;c:\sybase\sqlremote\dll
set PATH=%PATH%;c:\sybase\OCS-12_0\bin
set PATH=%PATH%;c:\sybase\SQLRemote\bin

Do I need to include some more path and classpath
For your information:
Server - Solaris, SYBASE ASE 12.0
Client - NT PC Client for ASE 12.0



Regards

Wandi Djoewarto

0
djoewarto
12/22/2000 6:18:41 AM
sybase.sqlserver.admin 2338 articles. 0 followers. Follow

1 Replies
259 Views

Similar Articles

[PageSpeed] 9

djoewarto@asiamail.com wrote:

> I post it for the second time. Does anybody have an idea.
> 
> I have followed the guidance to set classpath and path, here is all of my
> settings.
> 
> set CLASSPATH=c:\jdk1.1.8\lib.classes.zip;
> c:\sybase\ASEP\monclass.zip;c:\sybase\ASEP\3pclass.zip;%CLASSPATH%
> 
> set
> PATH=c:\jdk1.1.8\bin;c:\sybase\ASEP;c:\sybase\dll;c:\sybase\OCS-12_0\dll;%PATH%
> set PATH=%PATH%;c:\sybase\SYSDLL
> set PATH=%PATH%;c:\sybase\Sybase Central 3.2\win32
> set PATH=%PATH%;c:\sybase\sqlremote\dll
> set PATH=%PATH%;c:\sybase\OCS-12_0\bin
> set PATH=%PATH%;c:\sybase\SQLRemote\bin
> 
> Do I need to include some more path and classpath
> For your information:
> Server - Solaris, SYBASE ASE 12.0
> Client - NT PC Client for ASE 12.0

	There was a post made on the 4th of December about this. However, your
	path looks to be correct based on what was said in that post. You don't
	need to set anything else I believe. I'm not familiar with a 12 client
	on NT, so I'm not sure how much help I can be. You could try asking in
	the NT newsgroup here. The other thing I would suggest is that you test
	one of the other Java based tools to see if it works (e.g. jisql). If
	that works, then its not the Java setup that's the cause of the problem.
	You might also want to report what error message you're getting or what
	isn't happening.

-am
0
Anthony
12/23/2000 9:40:15 AM
Reply: