******************************************************************* ** VISUAL INFO GENERAL CSD INFORMATION ** ** ** ** (For Corrective Service Delivery UR02410) ** ** ** ** Corrective Service Delivery (CSD) UR02410 is for AIX and ** ** Windows 95/98/NT systems. This file contains general CSD ** ** information that is not currently contained in the formal** ** documentation for VisualInfo. Please read the contents ** ** of this file before applying the CSD. ** ** ** ** In addition to the APAR fixes, this CSD contains ** ** preventive maintenance items that are related to the ** ** Client and Server Application. Maintenance items and ** ** APAR fixes are summarized in this README. ** ** ** ** This README file applies to all languages. This CSD is ** ** not for Windows 3.1 and cannot be installed on ** ** Windows 3.1 Systems. ** ** ** ******************************************************************* ** ** ** CSD241.ENU Table of Contents: ** ** ** ** 1.0 Customer Service and Support Information ** ** ** ** 2.0 Product Documents Available from Product WEB Site ** ** ** ** 3.0 Requirements/Prerequites for Installation ** ** ** ** 4.0 Installation Instructions / Issues ** ** 4.1 Windows 95/98/NT Installation ** ** 4.2 AIX Installation ** ** 5.0 Misc. Information ** ** 5.1 Inaccurate info displayed if attempting ** ** to start another instance of Library ** ** or Object Server ** ** 5.2 Maintaining FRNDIAG.LOG - IR37710 ** ** 5.3 Purger dies - IR39026 ** ** (Object Server - AIX & Windows) ** ** 5.4 Large Object Support (AIX & Windows NT) ** ** 5.5 Java SysAdmin - resource usage (Windows NT) ** ** 5.6 Library or Object Servers - SQL errors ** ** 5.7 NLV Related Remarks ** ** 5.8 VisualInfo ** ** 5.8.1 Deleted FRNOUT.MSG during uninstall of ** ** VI Fax Background Processor or Client ** ** Application - potential runtime error ** ** 5.8.2 AIX HACMP ** ** 6.0 APAR Fixes Rollup with Descriptions ** ** ** ******************************************************************* 1.0 CUSTOMER SERVICE AND SUPPORT INFORMATION ________________________________________________________________________ The following customer service and support guidelines apply to the U.S., Canada, and Puerto Rico only. Outside these countries, contact your local IBM representative or Authorized IBM Supplier for information on warranty and software support. In addition to program services described in the License Information, possible sources of help are available: - Through the Internet (http://www.ibm.com/products/support.html) * Search tips and techniques database * Download fixes, device drivers - By telephone (1-800-237-5511) If you are a licensed customer with a support contract and you need support, have the following information available when you call 1-800-237-5511. (In Canada, call 1-800-465-2222.) - The product name and version number - The kind of hardware and software you are using - What happened and what you were doing when the problem occurred - Whether you tried to solve the problem and how - The exact wording of any messages displayed If you are a licensed customer but do not have a support contract and you need support, call one of the following numbers to purchase a support contract: If you have an IBM Corporate Customer Number, - In the U.S. and Puerto Rico, call 1-800-799-7765, - In Canada, call 1-800-426-2255. All other customers with a valid license should call 1-800-237-5511. These service phones are staffed Monday through Friday, 8:00 a.m. to 5:00 p.m. Eastern time. ________________________________________________________________________ 2.0 PRODUCT DOCUMENTS AVAILABLE FROM PRODUCT WEB SITE ________________________________________________________________________ VisualInfo publications are available from the IBM ImagePlus web site: http://www.software.ibm.com/data/imageplus/ Select the LIBRARY tab and select the ImagePlus product in which you are interested. You will need an ID and password to access the publications. The ID is imageplus and the password is sulpegami (The password is imageplus written backwords) The publications are in HTML form. You can view the publications from your web browser. Publications consist of: * Planning and Installation (updated for this CSD) * System Administration (updated for this CSD) * Application Programming Guides * Application Programming Reference * Client for Windows User's Guide * Client for OS/2 User's Guide * Messages and Codes ________________________________________________________________________ 3.0 REQUIREMENTS/PREREQUISITES FOR INSTALLATION ________________________________________________________________________ This CSD is for AIX and Windows 95/98/NT. In order to install this CSD, you must have the following product base level releases installed: a) VisualInfo 2.4 Customers using UDB for their database and experiencing problems viewing Index Class attributes should install the UDB fixpack for APAR JR12067. Note: For DB2 only - Part of the functionality of this CSD is an automatic bind of the Library and Object Server databases. For the object server users will see FRN9981A message in the frndiag.log file that is the SQL failure mechanism for the bind to take place. The FRN9981A message before a BIND message should be ignored. Special notes: The most current list of scanners that are compatible with VisualInfo are listed at the ImagePlus web page: http://www.software.ibm.com/data/imageplus Select the list of scanners that you would like to view. ******************************************************************* 4.0 Installation Instructions -------------------------------------------------------------------- 4.1 Windows 95/98/NT Installation ----------------------------------------------------------------- 1. Download the UR51031.EXE file in binary mode to a temporary subdirectory on your workstation. 2. Shut down and reboot your workstation to ensure that all file locks are released. 3. UR51031.EXE is a self-extracting WINZIP file that can be extracted by simply entering UR51031. 4. After extracting the ZIP file, run setup. 4.2 AIX Installation --------------------------------------------------------------- 1. Download the UR51031.tar file in binary mode to a temporary subdirectory on your workstation. 2. Unpack the UR51031.tar file into your temporary subdirectory using the AIX tar utility. For example: # tar -xvf UR51031.tar 3. Log in as root. 4. Start the Installation wizard by entering ./frnxupdate.sh -------------------------------------------------------------------- ******************************************************************* 5.0 Misc. Information -------------------------------------------------------------------- 5.1 Inaccurate info displayed if attempting to start another instance of Library or Object Server On the Windows NT platform, if the Library Server or the Object Server is running and an attempt is made to start another instance of the same server, another GUI will be brought up that will display inaccurate information. Any attempts to shutdown that server results in problems. To avoid this situation, before starting either the Library or Object Server, ensure that no other instance of the same server is currently running. --------------------------------------------------------------- 5.2 Maintaining FRNDIAG.LOG - IR37710, IR39299 The frndiag.log file grows infinitely. The administrator should manually prune the log after reviewing the contents. This change allows limitation of log space used. Two new environment variables have been defined: FRNLOGSIZE and FRNLOGNUM. FRNLOGSIZE specifies the number of kilobytes to use for each log, the minimum value is 1 and the maximum value is 2097151. FRNLOGNUM sets the number of log copies to keep. This is only used if FRNLOGSIZE is set. FRNLOGNUM has a minimum value of 1 and a maximum value of 999. If FRNLOGNUM is not set, the default is 1. When using wrapped logs the behavior is: When the frndiag.log has exceeded the size of (FRNLOGSIZE*1024), the oldest log is deleted. Frndiag.log is then renamed to frndiag.001 and frndiag.001 becomes frndiag.002 and so on... for as many copies as FRNLOGNUM specifies. The following is used to calculate the approximate maximum storage used: Maximum Storage Used = (FRNLOGSIZE + 1) * 1024 * (FRNLOGNUM + 1) Each log file when full will just exceed the requested size threshold. --------------------------------------------------------------- 5.3 Purger dies - IR39026 (Object Server - AIX & Windows) The Purger incorrectly handled messages from processors requesting space. Behavior of the system is now changed. 1. Purger and Destager will honor disabled state at all times except when enabled or started by an administration client or during start up of server when the destager and purger will enable approximately 1 minute after startup. It is the administrator's responsibility to enable the processes if he has disabled them. 2. A Store operation will check the staging area purge start limit. If found to be over the start limit, the store will attempt to notify the destager to start the destage operation. Destager will then notify Purger at the end of the destage cycle. 3. Messages requesting destage or purge operations received when the operation is in progress will be discarded or answered with an error code as appropriate. 4. Only the first process requesting space when the purger is enabled and not running will be posted when the space is available. All others will be returned with a 9930 error indicating that there is currently insufficient space. Destager and Purger will run and rectify space constraint if possible. Practical Implications. *. The staging area should be on its own file system (AIX) or disk partition (Windows). 1. Destage operation will occur at either purge start limit or by time idle setting. Small values for time idle causing Destager to run very frequently should be avoided because it slows the overall system performance. Destage frequency/time idle on systems where stores are occuring throughout the day may find a very large value to be the most satisfactory, as the Destager will run as needed. 2. Purger time idle on systems read mostly should be set for a frequency such that the staging area never reaches 100% full but does not cycle too frequently. Small values for frequency/time idle will degrade system performance. For most systems, a value of less than 30 may indicate that the staging area size should be reviewed. 3. Most systems should find the staging area maintained closely within the percent start/stop bounds of the Purger regardless of large values set for frequency/idle time for the Destager and Purger. --------------------------------------------------------------- 5.4 Large Object Support (AIX and Windows NT) Improvements have been made to lessen the system memory requirements and increase transport speed of large objects. However, as objects grow in size there are still some tunable factors which must be configured properly. The proper settings for a given environment will be documented in a performance newsletter. These tunable factors are described below with the exception of object transmission rates and transmit buffer settings. For more details, see the newsletters at: http://www.software.ibm.com/data/edmsuite/newsletter --------------------------------------------------------------- The following are some parameters which need to be configured. On the Object Server: 1) Ensure that the staging and destaging volumes can support large objects. 2) Via System Administration SMS Configuration, ensure the Client Response timeout in seconds is large enough to allow for the object transmission time. On the Library Server: 1) Via System Administration Library Server Configuration, ensure the Client and Object Server response timeouts in seconds is large enough to allow for the object transmission time. On the Client: 1) Set the FRNFMTIMEOUT environment variable to the minutes value to allow for the object transmission. 2) If using the Toolkit Object APIs accessing as SIM_OPEN_DISK and the filename is to be generated automatically, ensure that there is enough disk space in the WORK disk directory to accommodate the object. If the filename is specified in the Object API, then ensure that there is enough disk space to accommodate the object in the specified filename path. In these cases, the toolkit memory specified by FRNHEAPSIZE is not required except for request/response data from Library Server queries. The default heapsize can actually be lowered. 3) If using the Toolkit Object APIs accessing as SIM_OPEN_MEMORY, ensure that there is enough virtual memory and toolkit memory. The toolkit memory is set by the FRNHEAPSIZE environment variable which is in 4K units. The virtual memory is set within the operating system. The goal of this release is to keep the required memory usage down such that only one copy of the object need fit in the virtual memory heap and one object need fit into the toolkit memory. This was not necessarily achieved for all object APIs. --------------------------------------------------------------- 5.5 Java SysAdmin - resource usage (Windows NT) To save system resources, do not start multiple help panels at the same time. --------------------------------------------------------------- 5.6 Library or Object Servers - SQL errors - Rebind During initialization of either the Library Server or the Object Server or during the logon to the Library Server, if you get a SQL error -818, -1224, or -900, the server databases need to be rebound. --------------------------------------------------------------- 5.7 NLV Related Remarks 1) ESP a) During installation of DL on NT, be sure to only enable the Media Support Feature if the hardware for it is available. b) In Java System Administration input panels, the character, \, cannot be entered from the keyboard. It has to be cut and pasted. c) For all utilities, the timestamp is 8 hours ahead. This is a Java bug, and a fix will be provided as an APAR. 2) DAN a) In Java System Administration input panels, the character, \, cannot be entered from the keyboard. It has to be cut and pasted. 3) FRA a) Due to an error in the viewer program for HTML files, some help files might appear with what looks like typos. A fix will be provided via an APAR. 4) ITA a) Due to an error in the viewer program for HTML files, some help files might appear with what looks like typos. A fix will be provided via an APAR. 5) PBT a) Due to an error in the viewer program for HTML files, some help files might appear with what looks like typos. A fix will be provided via an APAR. 6) CHS a) (AIX) To run the Internet Application Toolkit, make sure the small Chinese font is installed and the display resolution is set to high resolution. Otherwise, lower parts of some panels might not become visible. However, the functionality of this component is not effected by insufficient settings. 7) CHT a) (AIX) Currently, Java does not support locale Zh_TW. The message "Missing charsets in String to FontSet conversion" might appear. Please ignore this problem. b) (NT) Some special characters in Help Files might cause the help window to disappear. This does not cause any impact on the running system. Reopen the help file, and proceed. -------------------------------------------------------------------- 5.8 VisualInfo 5.8.1 Deleted FRNOUT.MSG during uninstall of the VI Fax Background Processor or Client Application - potential runtime error When uninstalling the VI Fax Background Processor, the frnoutf.msg, which is shared by the Client Application component may be deleted, creating a potential runtime error within the Client Application. The same situation applies if the Client Application is uninstalled. The Fax Background Processor may lose access to the frnoutf.msg, thus creating a potential runtime error. For this reason, if you installed both the VI Fax Background Processor and the Client Application and you later choose to uninstall either: 1) backup the frnoutf.msg file 2) restore frnoutf.msg file after uninstalling the component 5.8.2 AIX HACMP Library server and object server can tolerate in a properly established HACMP environment. We make this statement based on field experience. Seamless takeover is not supported. Library server and object server must be restarted with appropriate recovery steps. The client must be logged off and logged back on. ******************************************************************* 6.0 APAR Fixes Rollup with Descriptions Following is a list of NEW APARs closed since the last release. These APAR fixes are included in this release of the product. -------------------------------------------------------------------- New Release 2.4.1 APARS Service Level: UR02410 Date: 3/1/99 Following is a list of previous APARs closed since the last release. These APAR fixes are included in this release of the product. APAR Description of APAR Number ------------------------------------------------------------------- IR37283 The Ip2ListHistory API is failing on items which have been stored in a workbasket that contains a comma (',') in its name. The internal parsing of the EventData row in the SBTEVENTS table fails, because the comma is used as separator between the strings. The API can't parse the following ------------------------------------------------------------------- IR38604 Scanned documents converted to AFP data stream clipped when printed ------------------------------------------------------------------- IR38739 Displaying bad message if object server has a problem ------------------------------------------------------------------- IR38740 OLE Automation crash ------------------------------------------------------------------- IR38760 JPEG blue and red switch if there is no JFIF header ------------------------------------------------------------------- IR38781 Auto-foldered items don't get removed from wrong folder when re-indexed ------------------------------------------------------------------- IR38836 Static queries not created ------------------------------------------------------------------- IR38864 VI Client is hanging when closing a document window ------------------------------------------------------------------- IR39019 Object Server posts a vague msg in the application event viewer associated with an error msg icon. This msg in the app event viewer corresponds to a msg in the frndiag.log file, which is unclear to customer what it means. contents of EventData: "SCANNER1","Demo, testwb","100" ------------------------------------------------------------------- IR39268 Alternate Search user exit does not return empty fields ------------------------------------------------------------------- IR39271 Cannot log on to Lotus Notes to receive mail ------------------------------------------------------------------- IR39281 "Missing string" error logged to FFST ------------------------------------------------------------------- IR39292 OS/2 notelog doesn't display correctly under Windows ------------------------------------------------------------------- IR39293 Index class tabs should be sorted ------------------------------------------------------------------- IR39387 SVI PTOCA tag is not processed ------------------------------------------------------------------- IR39391 Object server is unresponsive or is hung. Shared memory is not being released eventually causing an out of memory condition. ------------------------------------------------------------------- IR39434 The page number dissapears if the client loses focus ------------------------------------------------------------------- IR39438 Memory leak problem generates FIW2203A ------------------------------------------------------------------- IR39487 OLE Suspend not handling attributes correctly ------------------------------------------------------------------- IR39506 Note log text should automatically word wrap ------------------------------------------------------------------- IR39512 Adding Euro Support. ------------------------------------------------------------------- IR39552 Occasionally, the wrong annotations appear for documents ------------------------------------------------------------------- IR39580 PCL not automatically selecting paper size ------------------------------------------------------------------- IR39736 Pause scanner after X pages have been scanned ------------------------------------------------------------------- IR39787 Y2K: Two-digit date fields were being saved incorrectly -------------------------------------------------------------------