Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX README: Release B.06.00

cluster and packages so that unauthorized users are restricted
from
viewing sensitive package attribute values like the Sybase
administrator
password. See section G in this README file for more details
on
configuring Role Based Access (RBA).
A. Overview
The Sybase ASE Toolkit for Serviceguard consists of a shell script
that
is used to start, stop, and monitor a single instance of Sybase ASE.
Please note that this toolkit supports only modular packages.
NOTE: This toolkit does NOT support the Sybase ASE HA Failover
feature.
To use this toolkit, the toolkit script must be integrated with
the
Serviceguard master control script. Subsequent sections (D,E,F
sections)
of this document provide guidelines for integration of this
toolkit
with Serviceguard master control script.
NOTE: This README assumes that the user has already installed
Serviceguard, Sybase ASE and the Sybase ASE Toolkit on all the
nodes in the cluster.
B. Sybase Information
Sybase ASE should be accessible from the same location on all nodes
in
the cluster that will run the package.
The ASE instance can be configured in different ways:
* Shared Config - where all Sybase ASE installed binaries and
the
database files are on a shared file system on LVM.
* Local Config -where the Sybase ASE instance is installed and
configured
on single node and the files are replicated on all the other nodes in
the
cluster.The application datafiles should be on shared file system on
LVM.
Local Configuration
If the choice is to store the configuration files on a local disk,
the
configuration MUST be replicated to local disks on all nodes
configured