Product: IBM CallPath Enterprise Client Version: 6.3.0 Level: E2033 Platform: AIX Date: 25 June 2001 Service File: eclaix.tar History: eclaix.hst Fileset: csebclnt.obj Size: 880640 (0.8Mb) Checksum: 2716618771 Installation Instructions: -------------------------- This Service File is a tar of an installp update fileset. It includes both the fileset, csebclnt.obj, and its related .toc file. You must have root authority to install this fileset. - Download eclaix.tar into a directory. - Extract the fileset using the command "tar -xvf eclaix.tar". - Start "smit install_update" (for AIX < 4.2 use install_selectable). - Select "Install/Update From All Available Software". - Enter the directory name to which the fileset was extracted. - Enter the fileset name, csebclnt.obj, into the field "SOFTWARE to install". Service files are installed with root ownership and root access permissions. If you want users WITHOUT root authority to be able to start or access the IBM CallPath Enterprise Client product files, the following changes are required: - Change the group with the chgrp command for all of the directories and files within the installation path. For example, to permit the Admin group, issue: "chgrp -R Admin /usr/lpp/cseb" - Change the file permissions with the chmod command. For example, "chmod -R g+x+r /usr/lpp/cseb" Fixes contained in this Service Package: ---------------------------------------- Name: APAR IC30160 Date: 20 April 2001 Library: 9359 Symptom: csebclnt may trap/core dump if an associated CEO server is stopped and started several times. This problem may also occur if TCP/IP communcations with a CEO server is broken and re-established several times over a 10 to 20 minute period. Problem: If the heartbeat option is configured and a TCP/IP connection to a CEO server is expired by the heartbeat logic, then an exception may occur in removing the broken connection. The exception occurs when the broken connection is already being removed by another thread. Solution: Once a connection is marked internally as "close-pending" the heartbeat logic will no longer reference the connection. Name: APAR IC29587 Date: 13 February 2001 Library: 9188 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 that holds 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 will be closed and the associated event monitors are stopped. Also, if a CPE client is unable to open its IPC queue on startup, it will log an error message and exit. Name: APAR IC28809 Date: 11 November 2000 Library: 9013 Symptom: TadsDisconnectFromServer does not return. Problem: In AIX, while a signal handler is executing other threads in the process are suspended (assuming a Draft 10 version of the thread library). For this problem, the main thread has a TadsGetEvent request pending at the time the application's SIGTERM signal handler begins. Within the signal handler a call to TadsDisconnectFromServer is made. This disconnect request attempts to lock a semaphore that's held by the suspended TadsGetEvent request and remains hung on the lock request. Solution: The best solution is to not make Callpath requests from within a signal handler. By definition, processing within a signal handler should be kept to a minimum. In this particular situation, the application did not have a problem when using an older version of Callpath. The problem was introduced when Callpath switched to the draft 10 version of the AIX thread library. To have Callpath behave the same as in previous releases, changes were made to TadsDisconnectFromServer and TadGetEvent processing to remove the semaphore dependency that resulted in the hang. Name: APAR IY12501 Date: 17 August 2000 Library: 8882 Symptom: A CallPath Enterprise client has multiple TCP connections to its server. Problem: If the case of the server host name in the client INI file is different than the case of the server host name used by the application on the TadsConnectToServer API call, then two or more TCP socket connections are established between the Callpath Enterprise client and the associated server. Solution: Ensure only one connection is established between a Callpath Enterprise client and any associated Callpath Enterprise server. Name: APAR IC28839 Date: 15 Nov 2000 Library: 9021 Symptom: When installing an Enterprise product the following error occurs; "Could not add dll path to autoexec.bat". If this error was ignored on the installation then there will be an incomplete install of the product. Now when service is applied to the product the following error will be displayed; "Not Enough disk space on target drive while attempting to copy files. To continue, first free disk space on the target drive and then click OK." Whether OK or Cancel is chosen the program will result in an endless loop. One must use Task Manager to end the Callpath Service application. Problem: The problem is that some Windows 2000 machines have a hidden AUTOEXEC.BAT file which prevents install from updating the path. This results in a corrupted registry entry. This also causes the service executables to fail which gives the "out of disk space" error above. Solution: The solution is to turn off the hidden attribute from the AUTOEXEC.BAT file, uninstall, and then reinstall. The following steps will assist in the process. 1) Stop all components 2) Turn off the hidden attribute on the AUTOEXEC.BAT file. This can be done by opening a command prompt and from the root directory, usually c:\, type "attrib -H AUTOEXEC.BAT". 3) Copy all of the .INI and/or .DEF files from the conf directory to a temporaray directory. 4) Uninstall the product. 5) Reinstall the product. This time there should be no error messages displayed from the install program. 6) Copy the .INI and/or .DEF file from the temporary directory back to conf. Files contained in this Service Package: ---------------------------------------- cseb/bin/csebclnt cseb/bin/eclrun cseb/bin/eclpost cseb/rc/Csebclnt cseb/text/csebclnt.copyright cseb/text/csebclnt.txt cseb/bin/ecs.config