Product:       CallPath Enterprise Client for AIX
Version:       2.02.0001
Package Name:  csebclnt1978.tar
        Size:  880640 (860Kb)
        Level: 1978

Results of 'sum csebclnt1978.tar ' is '16734'

How to install:
This is a tar of an installp update fileset.  It includes both the fileset and
its related .toc file.
 
You must have root authority to install this fileset.
o Download csebclnt1978.tar into a directory.
o Extract the fileset using the command 'tar -xvf csebclnt1978.tar'
  and remember the extracted fileset name, csebclnt.obj, for a later step.
o Start 'smit install_update' (for AIX < 4.2 use install_selectable)
o Select 'Install/Update From All Available Software'
o Enter the directory in which the fileset was extracted.
o Enter the fileset name, csebclnt.obj, into the field 'SOFTWARE to install'

Fixes:

APAR  IC29587
    Symptom:  Over an extended period of time the number of
              abandoned event monitors increase resulting in
              a continued degradation in system performance.
              Another symptom is that if an application monitoring
              routed-trigger events exits without releasing the
              monitor, then this monitor continues to be active
              and since only one application can monitor
              routed-trigger events, no other monitor for this
              event is allowed.
 
    Problem:  If an application holding event monitors dies or
              attempts to close the connection (and discards the
              connection handle) while the CPE client could not
              communicate with the CPE server, then the event
              monitors held by this application are not cleaned up.
   Solution:  If the CPE client or server receives an event that
              is no longer deliverable, then the connection associated
              with this event is closed and the associated
              event monitors are stopped.
 

PMR  47625
 
    Problem: When an application is monitoring but is not receiving from its
             event queue the event queue gets full and the CallPath Enterprise
             client's event thread hangs in sending the next event to this
             application.

    Workaround: If an application is monitoring, ensure that the application
                is reading from its event queue in a timely manner.

    Solution: To limit the effect of an unresponsive application a code change
              was made to time out (after 6 seconds) the delivery of an event.
              This allows all applications, other than the unresponsive one,
              to continue receiving events.
 

PMR  70892
(Def 7651)
    Symptom: In a multithreaded application, a Tads* call that immediately follows
             a TadsConnectToServer call may return TADS_HANDLE_DISCONNECTED.

 
    Problem: The problem occurs when one thread has issued a TadsDisconnectFromServer
             while another thread, at the same time, issues a TadsConnectToServer
             and gets the same connection handle.  Then when the second thread
             does a subsequent Tads call, it occasionally returns right away with
             a return code of TADS_HANDLE_DISCONNECTED.

    Workaround: None.

    Solution: Processing within TadsDisconnectFromServer was prematurely marking
              its connection handle as available.  In rare cases, this resulted
              in data associated with the new connection being overwritten.  The
              disconnect logic was changed to kept its connection handle until all
              processing has completed.
 

PMR  74506
(Def 7042)
    Symptom: CEO applications in AIX that were set up to handle a SIGTERM signal were
             not seeing the SIGTERM signal until the second time the signal was sent.
 
    Problem: The build process that created the AIX API library (libcseb.a) was
             bringing in some incorrect libraries in the step where the shared library
             is created.  This altered the SIGTERM behavior.

    Workaround: None.

    Solution: libcseb.a now built with correct libraries.
 

PMR  09162
(Def 6960)
    Symptom: The TCP connection between the CallPath Enterprise Server and an
             associated daemon breaks for no apparent reason.  Shortly
             thereafter the server traps in AZAOM30.DLL.
 
    Problem: The daemon receives a 0 length message from its server connection.
             In response the daemon assumes the connection has gone away and
             closes the connection.  Once the server discovers that the
             connection to the daemon is broken he attempts to cleanup and
             ends up overwriting memory.
    Workaround: None

    Solution: Changed code to not treat a "no data" condition on a TCP socket
              receive call as an error.  Corrected the memory overwite problem.
 

PMR  42104
(Def 7020)
    Symptom: In NT, occasionally the CallPath Enterprise Client traps after
             restarting an associated CallPath Enterprise Server. This
             problem can also occur in the server if associated daemons
             are stopped and started multiple times.
 
    Problem: The extents of an array holding connection information is
             exceeded.  This results in memory being corrupted and the
             trap.
    Workaround: None

    Solution: Changed code to not use the socket handle as an index into
              the connection information array.  Instead, hashing is used to
              locate array entries.
 

PMR  09206
(Def 6912)
    Symptom: An occasional performance problem on CallPath Enterprise Server
             when a client goes away.
 
    Problem: CallPath Enterprise Clients are sending (in error)
             TADS_SYSTEM_EVENTS to the server. The server is fooled into
             treating these clients as daemons, and when one of these clients
             goes away, the server sends a TADS_SYSTEM_EVENT to all clients
             monitoring for system events.  This causes a big performance
             problem when hundreds of clients are attached.

    Workaround: None

    Solution: Modified the server code to not be fooled into treating regular
              clients as daemons.  Modified the client code to not send
              TADS_SYSTEM_EVENTS to the server.
 

PMR  32718
(Def 6748)
    Symptom: Enterprise Client, Server, or a Daemon could abend during some
             shutdown scenarios. Usually this would occur during a user-invoked
             shutdown. Occsasionally, it would happen during an attempt at orderly
             shutdown due to a terminating error.
 
    Problem: 1) Attempting to shutdown a client, server, or daemon that was
                started with the nodisplay option in certain AIX environments
                by using the SIGTERM signal.
             2) Timing problem between shutdown of NetLayer and shutdown of
                DispatcherLayer.
             3) Attempts to shutdown a daemon using the daemon stop() method.

    Workaround: None.

    Solution: Several timing and cleanup problems in shutdown logic were removed.
 

Files in service:
usr/lpp/cseb/bin/csebclnt
usr/lpp/cseb/rc/Csebclnt
usr/lpp/cseb/text/csebclnt.copyright
usr/lpp/cseb/text/csebclnt.txt