Starting and Stopping Sybase Control Center in UNIX

You can start Sybase Control Center or the SCC agent manually, which is useful for testing and troubleshooting, or you can set up a service to start automatically and to restart in case of failure.

This topic applies to both Sybase Control Center (the server, which includes the management UI) and the Sybase Control Center agent that runs on each product server managed by SCC.. When you install SCC and the SCC agent in the same directory by selecting both options in the installer, you start and stop them together—by executing a single command or controlling a single service. This topic applies to both singleton installations (which do not use a shared disk) and instances of SCC agents and servers running from a shared disk.

If you start Sybase Control Center or the SCC agent manually, you must issue a command every time you start or shut down. If you run as a service (which is recommended), you can configure the service to start and restart automatically. These are the options:

Use the scc.sh script to start Sybase Control Center or the SCC agent manually. You can either:
- Run scc.sh in the foreground to get access to the Sybase Control Center console, which you can use to shut down and to display information about services, ports, system properties, and environment variables.
- Run scc.sh in the background to suppress the console.
You can use scc.sh to run Sybase Control Center at a nondefault logging level for troubleshooting. When you start manually with scc.sh, you cannot take advantage of the automatic start and restart features available to services.
Use the sccd script to configure a service that starts Sybase Control Center or the SCC agent automatically.

Here are the steps for each starting and stopping option:

Before you start Sybase Control Center or the SCC agent for the first time, set environment variables. Do this only once.
1. Change to the Sybase directory (the parent of the Sybase Control Center installation directory).
2. Execute one of the following to set environment variables.
  Bourne shell:
```
. SYBASE.sh
```
  C shell:
```
source SYBASE.csh
```
Run Sybase Control Center or the SCC agent (or both, when they are installed together) in the foreground.
Running in the foreground is a method of manually starting; you must issue commands to stop and restart Sybase Control Center or the SCC agent.
1. To start Sybase Control Center or the SCC agent and drop into the console when the start-up sequence is finished, enter the scc command.
  For a singleton installation:
```
$SYBASE/SCC-3_2/bin/scc.sh
```
  For an instance:
```
$SYBASE/SCC-3_2/bin/scc.sh -instance <instance-name>
```
  You can omit the -instance option if the instance’s name is the same as its host name (the default).
Run Sybase Control Center or the SCC agent (or both, when they are installed together) in the background.
You can use nohup, &, and > to run Sybase Control Center or the SCC agent in the background, redirect output and system error to a file, and suppress the SCC console. Running in the background is a method of manually starting; you must issue commands to stop and restart Sybase Control Center or the SCC agent.
1. Execute a command similar to the sample below that matches your shell. Both sample commands direct output to the file scc-console.out. If the output file already exists, you might need to use additional shell operators to append to or truncate the file.
  Bourne shell (sh) or Bash
  For a singleton installation:
```
nohup ./scc.sh 2>&1 > scc-console.out &
```
  For an instance:
```
nohup ./scc.sh -instance <instance-name> 2>&1 > scc-console-your-instance.out &
```
  You can omit the -instance option if the instance’s name is the same as its host name (the default).
  C shell
  For a singleton installation:
```
nohup ./scc.sh >& scc-console.out &
```
  For an instance:
```
nohup ./scc.sh -instance <instance-name> >& scc-console.out &
```
  You can omit the -instance option if the instance’s name is the same as its host name (the default).
Shut down Sybase Control Center or the SCC agent (or both, when they are installed together) .
1. To shut down from the scc-console> prompt, enter:
```
shutdown
```
  Warning! Do not enter shutdown at a UNIX prompt; it shuts down the operating system.
  To shut down from the UNIX command line, enter the scc --stop command.
  For a singleton installation:
```
$SYBASE/SCC-3_2/bin/scc.sh --stop
```
  For an instance:
```
$SYBASE/SCC-3_2/bin/scc.sh --stop -instance <instance-name>
```
  You can omit the -instance option if the instance’s name is the same as its host name (the default).
Configure Sybase Control Center or the SCC agent to run as a service.
A UNIX service is a daemon process that starts automatically after the machine is started and runs in the background. UNIX installations of Sybase Control Center include a shell script, sccd, which you can use to configure the Sybase Control Center service. (Some UNIX platforms supply tools that make service configuration easier; Linux chkconfig is an example.)
Note: Sybase recommends that if you are not familiar with setting up services in UNIX, you delegate this task to a system administrator or consult the system administration documentation for your UNIX platform.
1. Copy $SYBASE/SCC-3_2/bin/sccd into this directory:
  - AIX (SCC agent only): /etc/rc.d/init.d
  - HP-UX (SCC agent only): /sbin/init.d
  - All other platforms: /etc/init.d
2. Open sccd and make these changes:
  - Change the line that sets the SYBASE variable to the location of your Sybase installation (that is, the parent of SCC-3_2, the Sybase Control Center installation directory). By default, this directory is called Sybase.
  - If you are not using shared-disk mode, or you are using shared-disk mode to run a single instance whose name is the same as the host name, skip to step 3 or step 4.
  - If you are using shared-disk mode to run a single instance whose name is not the host name, or to run multiple instances on the same host, add the instance name to the script name. Change:
```
SCRIPT_NAME=scc.sh
```
    to:
```
SCRIPT_NAME="scc.sh -instance <instance-name>"
```
  - If you are using shared-disk mode to run multiple instances on the same host, append the instance name to the name of the ouput log file. Change:
```
./${SCRIPT_NAME} --start 2>&1 >> ${SCC_HOME}/log/scc-service.out &
```
    to:
```
./${SCRIPT_NAME} --start 2>&1 >> ${SCC_HOME}/log/scc-service_<instance-name>.out &
```
  - If you are using shared-disk mode to run multiple instances on the same host, save a copy of the sccd script for each instance, giving each copy a unique name. In each copy, add the instance name to the script name and append the instance name to the output log file name as described above. Perform the remaining steps in this procedure for each copy of sccd.
3. In Linux, configure the service to run in run levels 2, 3, 4, and 5:
```
/usr/sbin/chkconfig --add sccd
/usr/sbin/chkconfig --level 2345 sccd
```
  You can test the sccd script with /usr/sbin/service sccd status. (The service command accepts these options: start | stop | status | restart.)
4. On non-Linux platforms, locate this directory:
  - AIX (SCC agent only): /etc/rc.d/rc<X>.d
  - HP-UX (SCC agent only): /sbin/rc<X>.d
  - Solaris: /etc/rc<X>.d
  where <X> is the run level (for example, 3). Make two soft links in the directory for your platform and set the links to point to:
  - AIX (SCC agent only):
    /etc/rc.d/init.d/sccd: S90sccd and
    
    /etc/rc.d/init.d/sccd: K10sccd
  - HP-UX (SCC agent only):
    /sbin/init.d/sccd: S90sccd and
    
    /sbin/init.d/sccd: K10sccd
  - Solaris:
    /etc/init.d/sccd: S90sccd and
    
    /etc/init.d/sccd: K10sccd
  The S90sccd link starts the service and the K10sccd link stops the service. The two-digit numbers in the links indicate the start and stop priorities of the service.
5. Use the S90sccd and K10sccd links to test starting and stopping the service. The links are called automatically when the machine is started or shut down.