PROBLEM:  (UVO106363)    (Patch ID: TCR160-002)
********
This patch fixes two problems in the asedirector.  The first is an ASE command
timeout problem encountered by large ASE services. The second is an incorrect
decision made by the asedirector as a result of a failed inquire services
command.

1) The asedirector has static timeout values for some commands to
   aseagent processes.  Certain commands take a much longer time 
   to complete because they involve inquiring about large services.  
   As a result, large ASE services could encounter a premature timeout
   on the following commands, as show in the daemon.log: ASE_STOP_ALL,
   ASE_DELETE_ALL, ASE_ADD_ALL, ASE_DELETE_MEMBER, ASE_REVERT_DB.

   This patch modifies these command timeouts relative to the ASE 
   service size eliminating this premature timeout.

2) When the asedirector inquires about the status of services on a
   member, the command or the service inquiry may fail.  In this rare
   situation the director may incorrectly start a duplicate instance
   of a service on another node.  
   
   This patch fixes this problem such that if the director receives a
   failure, it will assume the service is running on that member.  It 
   will then either stop that service before restarting it, or not start
   it at all until it gets a correct response.

   The most common reason for this problem to occur is due to a timeout
   from the aseagent of a check action script for a service.  A less 
   probable reason to occur is due to an asedirector timeout on the 
   ASE_INQ_SERVICES command.  Both timeouts can be found in the daemon.log 
   file.