Product: IBM CallPath Reporter Version: 6.3.0 Level: J2032 Platform: OS/2 Date: 20 June 2001 Service File: ecros2.exe History: ecros2.hst Size: 1192313 (1.1Mb) Installation Instructions: -------------------------- Download the self-extracting file, ecros2.exe, into a temporary directory. Execute it from the command line and follow the prompts. If you answered "Yes" to the backup query and wish to undo the service update, issue the following commands: : cd \ -Qdr where is the drive letter on which product is installed and is the full path name of the backup self-extracting file. Fixes contained in this Service Package: ---------------------------------------- Name: APAR IC27268 Date: 29 September 2000 Library: 8936 Symptom: Telephony Reporter periodically stops logging to DB and enters SUSPEND MODE. Problem: Telephony Reporter periodically stops logging to DB and enters SUSPEND mode. Solution: Modified source to ignore AGENTSTATS and APPLSTATS errors and support two new config variables. The variables must be added to "Report.cfg" and spelled exactly as specified below. HighWaterMark=50 LowWaterMark=25 Name: APAR IC27268 Date: 22 Mar 2001 Library: 8997 Symptom: The database connection goes into suspend mode, and after resuming the connection, it eventually goes back down. Problem: When inserting a call segment or call summary record that has the same primary key as a row already in the database, the insert fails, the database connection is suspended, and the duplicate record is written to the cr.dat file. After resuming the connection, the duplicate record is read from the cr.dat file, and the insert once again fails for the same reason, thus putting the database connection in an unrecoverable suspend state. Solution: When the insert of a call segment or call summary record fails due to a duplicate primary key, the database connection is no longer suspended. Instead, information about the failing record is put in the callseg.err or callsum.err file, located in the working directory. Name: APAR IC30643 Date: 13 Jun 2001 Library: 9423 Symptom: After certain database failures, as Reporter receives records, the "Items waiting to be processed" continually grows and records are not being written to the archive file. Problem: In several cases, when the database connection goes down and Reporter tries to insert a record into the database, it throws a NullPointerException while processing the SQLException, and the thread that processes the records from the queue dies. Reporter will then never enter suspend mode and the "Items waiting to be processed" will keep growing. Solution: Fixed the code to correctly handle all SQLExceptions. Files contained in this Service Package: ---------------------------------------- cfgframe.jar readme.txt cpeecr.jar