PROBLEM:        (CLD MCPM11PV8) (Patch ID: TCR100-006)
********
After removing all of the LSM objects for a physical disk from the diskgroup,
a subsequent delete of the volume from the ASE service did not properly update
the ASE database.  ASE still contained information for the deleted disk which
made it impossible to use the disk in another service, and caused error
messages to be logged when starting the old service.

This problem was fixed by adding calls to functions that check for changes
in the LSM configuration, and then make changes to the ASE database after
confirming them with the user.

PROBLEM:  (GOZ100879 & MCSM31QBP)    (Patch ID: TCR100-024)
********
This patch increases the timeout values for the LSM action scripts that
are part of the TruCluster Production Server, Available Server and DECsafe
Available Server products.  The timeouts were too small for large LSM
configurations and, under certain conditions, would cause the start of
the services to fail, leaving them unassigned.

PROBLEM:        (QAR 43216, QAR 48875)  (Patch ID: TCR100-017)
********
This patch fixes a problem in ASE where removing a volume from an AdvFS
domain mounted by an ASE service causes the service to fail to restart,
and the daemon.log says "I/O error".

PROBLEM:  				(Patch ID: TCR100-027)
********
An ASE environment in which a service modification is performed while,
and the same time, another process is attempting to obtain service
status using asemgr could potentially corrupt the ASE Configuration Data
base for that service. The results of the data base corruption is a loss
of LSM and physical disk information in the data base for that service.
This will be seen as problems with relocating the service and "grep:
can't open" messages when checking status of the service.