Your directions sound very clear and I’ll try it on my Intel Mac when I get home tonight!
The problem here is that you are typing “name=servoy_repository” in the options box. Please leave the box empty, and follow the same procedure you described above. By default, Sybase Central will connect to servoy_repository. You will also see the other dbs, but this time the connection should be successful.
I don’t quite get it since on that tab it says to enter the name of each database but the whole difference between connecting to the database server and connecting to the database itself has always been somewhat nebulous for me…let alone when I get into Oracle and messing around with Schemas, logins and their differences… Anyway this sounds like a very thorough description. I’ll check it out tonight and report back either way so that even the clueless like me have a full, successful description of how to connect Sybase Central 9 on a MacIntel machine!
First of all I did get Sybase Central running on my MacIntel machine per your directions as I explain below and that was the main thing. However, I couldn’t get the dblocate to work even after following the directions. For the most part I don’t think that is very important as I’ll always know the IP address of any SQL anywhere database I want to access and whether it is running or not. And your directions are very good for getting Sybase Central to work with a known SQLAnywhere database. But in case anyone else needs dblocate to work this is what happened for me in following your directions:
When you open the command prompt, source the file /Applications/SQLAnywhere9/System/bin32/asa_config.sh. After this, you can run dblocate. BTW, you can also run Sybase Central right from there. The binary name is “scjview”.
To be honest I’m not quite sure what it means when you say ‘source the file’. But since the file in question is clearly a shell script I presume that means to run/execute it. Therefor I first had to make the file (asa_config.sh) executable (with chmod +x asa_config.sh). Then it ran fine. However I was still not able to run ‘dblocate’, getting the exact same messages as before. I was though able to launch Sybase Central from Applications/SQLAnywhere9/System/shared/sybcentral43/scjview.
As for hooking up to all the databases running under the servoy_repository server, your directions worked perfectly: leaving the box for the connection parameters empty and everything else as I had it.
john.allen:
To be honest I’m not quite sure what it means when you say ‘source the file’. But since the file in question is clearly a shell script I presume that means to run/execute it. Therefor I first had to make the file (asa_config.sh) executable (with chmod +x asa_config.sh). Then it ran fine. However I was still not able to run ‘dblocate’, getting the exact same messages as before. I was though able to launch Sybase Central from Applications/SQLAnywhere9/System/shared/sybcentral43/scjview.
Hi John,
Happy July 4th from your neighbour up here in Canada
Glad you got Sybase Central to work properly now.
The shell script correctly sets your PATH and library environment variables. You don’t need to change the file attributes, all you need to do is run the following at a Terminal: