Product: IBM CallPath Reporter Version: 6.3.1 Level: J2109 Platform: AIX Date: 18 September 2001 Service File: ecraix.tar History: ecraix.hst Fileset: cpecr.obj Size: 778240 (0.7Mb) Checksum: 4237954943 Installation Instructions: -------------------------- This Service File is a tar of an installp update fileset. It includes both the fileset, cpecr.obj, and its related .toc file. You must have root authority to install this fileset. - Download ecraix.tar into a directory. - Extract the fileset using the command "tar -xvf ecraix.tar". - Start "smit install_update". - Select "Install/Update From All Available Software". - Enter the directory name to which the fileset was extracted. - Enter the fileset name, cpecr.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 Reporter 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 IC30821 Date: 02 Jul 2001 Library: 9509 Symptom: Reporter should automatically attempt to restart after a database connection failure. Problem: When Reporter encounters a problem inserting a record into the database, it suspends the database connection but never tries to reestablish the connection. Instead, the customer must manually resume the connection. Solution: Added code so that Reporter will automatically attempt to resume a failed database connection. Name: APAR IC31659 Date: 17 Sep 2001 Library: 9730 Symptom: Reporter should be able to be automatically started when the GUI comes up. Problem: When the Reporter GUI is brought up, the user must manually click on Actions-->Reporter-->Start in order for Reporter to be started. Solution: The user can now specify AutoStart=YES in Report.cfg in order to specify that Reporter will be automatically started when the GUI is brought up. In order for Reporter to successfully start, the user must have previously configured the server and database information correctly. Setting AutoStart=NO or removing this parameter from Report.cfg will disable this feature. Name: APAR IC31660 Date: 17 Sep 2001 Library: 9823 Symptom: Timestamps are incorrect in the Reporter database when using certain timezones. Problem: When using certain system timezones, the timestamps that Reporter generates in the database, as well as in Report.out and on the "Last database insert" field of the Reporter GUI, are incorrect. The timezones that were addressed with this fix are GMT0BST and NZST-12. Solution: Java does not always correctly map the timezone of the system that Reporter is running on to a Java timezone; in these cases, the timezone that Java uses usually defaults to GMT, which then throws off the times that Reporter writes to the database and to its logs. Code has been added to correct this problem for the GMT0BST and NZST-12 timezones. The user can now add CustomTimeZone=GMT0BST to Report.cfg to correctly handle British Summer Time or CustomTimeZone=NZST-12 to correctly handle New Zealand time. Files contained in this Service Package: ---------------------------------------- cpecr/cfgframe.jar cpecr/cpeecr.jar cpecr/cpecr.copyright cpecr/cpecr.txt