PROBLEM:        (CLD MCPM11PV8) (Patch ID: ASE130-016)
*******
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: ASE130-025)
********
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)     (Patch ID: ASE130-005)
*******
The procedure for removing a volume from an AdvFS domain that is under the
control of an ASE service should be, first run rmvol, then run asemgr to modify
the service.  The relevant asemgr menu selection is "Modify the AdvFS domain
information."  If this procedure is followed, DECsafe will be unable to start
the service following the modification.
Asemgr will emit the message, "Start failed - Unable to start service."
Examination of the daemon log will show that when DECsafe attempted to start
the service, it passed the deleted volume to the advfs_dmn_action script.
Do not attempt to reproduce the problem.  There is no way to recover from it
except to (1) install this patch or (2) delete the affected service.

PROBLEM:  		    (Patch ID: ASE130-028)
********
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.