********************************************************************************************** IBM ImagePlus VisualInfo 2.4.x Fixpack2 (UR02412) for OS/2 November 3rd, 1999 This is an interim fixpack between Formal Corrective Service Deliverables (CSDs). Table of Contents 1.0 Customer Service and Support Information 2.0 Requirements/Prerequisites for Installation 3.0 Installation 3.1 Installation Instructions 3.2 Installation problems 3.3 Post Installation notes 4.0 Database considerations 5.0 Markup anomalies 6.0 Miscellaneous 7.0 APAR Fixes 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 REQUIREMENTS/PREREQUISITES FOR INSTALLATION ________________________________________________________ This FixPak (syslevel UR02412) is designed to update VisualInfo UR02311, UR02400, and UR02410. It should not be applied to any other versions of VisualInfo. ________________________________________________________ 3.0 Installation ________________________________________________________ 3.1 Installation Instructions 1. Shut down and reboot your workstation to ensure that all file locks are released. 2. Download or copy the file os202412.zip to a temporary directory on your PC. 3. Unzip the file using PKUNZIP2 with the -d option to create the subdirectory structure. IMPORTANT: Do NOT perform this step from your VisualInfo installation directory. c:\temp\pkunzip2 -d os202412.zip 4. To install the Fixpack, type "SERVICE" from the temporary directory to start the installation program. Follow the instructions presented to complete the Fixpack installation process. c:\temp\service 3.2 Installation problems _______________________ 3.2.1 Cannot find frnoinst.ini error This error can occur in two circumstances: 1) A version of VisualInfo is installed that this fixpack does not support. Please review "2.0 REQUIREMENTS/PREREQUISITES FOR INSTALLATION" in this file. 2) A previous version of VisualInfo has been removed but the FRNROOT enviroment variable is still set. From an OS/2 command prompt, type "SET FRNROOT=" to reset the enviroment variable. Then restart the installation program from the same OS/2 command prompt. 3.2.2 EPFIE211 error The error message "EPFIE211: A product name is required to perform the requested action. Specify a product name." is displayed if the FixPak installation program cannot find an existing VisualInfo installation. Make sure you have the proper prerequisites. Please review "2.0 REQUIREMENTS/PREREQUISITES FOR INSTALLATION" in this file. 3.2.3 EPFIE115 error - Restore not working If the restore function fails, you can manually restore the product by copying the files from the backup subdirectory using the OS/2 COPY command. 3.3 Post Installation notes _______________________ 3.3.1 Previously disabled cache will be enabled. If you have previously installed the Library Client in non-cache mode, caching will be enabled. If you still desire non-cache operation, follow the steps in section 3.3.2 after product installation has completed. 3.3.2 Installing non-cache components Follow these steps to install the library client without cache and the client without cache: 1) Follow the instructions in the Planning and Installation Guide to install: a) Library Client with cache b) Client Application with cache 2) After the cache code is installed, open an OS/2 window and change to the \FRNROOT subdirectory (the directory where VisualInfo was installed). 3) Rename the files that enable caching: a) Rename FRNROOT\FRNODAMN.EXE to FRNROOT\FRNODAYL.EXE b) Rename FRNROOT\DLL\FRNODAPI.DLL to FRNROOT\DLL\FRNODAYL.DLL c) Rename FRNROOT\DLL\FRNOLCLI.DLL to FRNROOT\DLL\FRNOLCYL.DLL 4) Rename the files that disable caching: a) Rename FRNROOT\FRNODANL.EXE to FRNROOT\FRNODAMN.EXE b) Rename FRNROOT\DLL\FRNODANL.DLL TO FRNROOT\DLL\FRNODAPI.DLL c) Rename FRNROOT\DLL\FRNOLCNL.DLL TO FRNROOT\DLL\FRNOLCLI.DLL You will now be able to use the library client without cache and the client without cache. Make a note to yourself that you renamed the files and are using the non-cache code; you'll need to remember this if you ever call IBM for service. 3.3.3 Enabling CID installation for non-cache components Follow these steps to enable CID installation of the library client without cache and the client without cache: 1) Follow the instructions in the Planning and Installation Guide to copy the code to your server. 2) Open an OS/2 window and change directories to the location where you copied the files, for example \FRNOS2. 3) Rename the files that enable caching: a) Rename FRNOS2\FRNODAMN.EXE to FRNOS2\FRNODAYL.EXE b) Rename FRNOS2\DLL\FRNODAPI.DLL to FRNOS2\DLL\FRNODAYL.DLL c) Rename FRNOS2\DLL\FRNOLCLI.DLL to FRNOS2\DLL\FRNOLCYL.DLL 4) Rename the files that disable caching: a) Rename FRNOS2\FRNODANL.EXE to FRNOS2\FRNODAMN.EXE b) Rename FRNOS2\DLL\FRNODANL.DLL TO FRNOS2\DLL\FRNODAPI.DLL c) Rename FRNOS2\DLL\FRNOLCNL.DLL TO FRNOS2\DLL\FRNOLCLI.DLL Because you renamed the files, you can now install both the library client without cache and the client without cache by specifying the parameters for the "Library client with cache" and the "Client with cache" during the CID install. Do not use the parameters "Library Client without cache" or "Client without cache." Make a note to yourself that you renamed the files and are using the non-cache code. You'll need to remember this if you ever call IBM for service. 3.3.4 Removing the non-cache components Because you renamed the files during installation, you can use the Installation program to remove the non-cache components: 1) From the Installation and Maintenance window, select the Selectable Components option. Now select Delete from the Actions pull-down menu. 2) Press Enter. The components that you installed are removed. To remove any remaining files, follow the instructions in the documentation to perform a manual removal. 3.3.5 Setting the LC_ALL environment variable in CONFIG.SYS In order for some country- or language-sensitive information (such as dates and times) to be properly displayed, you must set the LC_ALL variable in your CONFIG.SYS file, if it is not already set. For example, SET LC_ALL=en_US. This variable should be set according to the names suggested in IBM's "National Language Support Reference Manual", Volume 2. Some common examples are in the following table. Language Country LC_ALL -------------- -------------- ------- Arabic Egypt ar_EG Chinese (Simplified) China (PRC) zh_CN Chinese (Traditional) Taiwan (ROC) zh_TW Danish Denmark da_DK Dutch Netherlands nl_NL English United States en_US Finnish Finland fi_FI French France fr_FR German Germany de_DE Hebrew Israel iw_IL Italian Italy it_IT Japanese Japan ja_JP Korean South Korea ko_KR Norwegian Norway no_NO Portuguese Brazil pt_BR Spanish Spain es_ES Swedish Sweden sv_SE 3.3.6 Setting the TZ environment variable in CONFIG.SYS To ensure that the timestamps for some functions are properly reported (e.g. the status of execution of scheduled database utilities), set the TZ variable in your CONFIG.SYS file. For example, for the Eastern Standard Time Zone in the U.S.A., specify SET TZ=EST5EDT The syntax for TZ is: SET TZ=SSShDDD where: SSS = Standard-timezone identifier h = The difference in hours between the standard time zone and Greenwich Mean Time (GMT). A positive number denotes time zones west of the Greenwich meridian; a negative number denotes time zones east of the Greenwich meridian. Greenwich Mean Time is also referred to as Coordinated Universal Time (CUT). DDD = Daylight saving time (DST) zone identifier The following table lists some common examples: Territory TZ --------------------------- -------- USA (Eastern Zone) EST5EDT USA (Pacific Zone) PST8PDT Japan JST-9 3.3.7 Specifying SCSI Device Drivers in your CONFIG.SYS file If you use a scanner or printer that connects to your system using an IBM SCSI or other adapter, you must specify the device driver in your CONFIG.SYS file, using BASEDEV= and DEVICE= statements. Verify that the CONFIG.SYS file contains the required BASEDEV= statements: For a PS/2 SCSI adapter and built-in SCSI: BASEDEV=IBM2SCSI.ADD For an IBM 16-bit Fast SCSI adapter: BASEDEV=FD16-700.ADD For any SCSI adapter: BASEDEV=OS2SCSI.DMD Add DEVICE= statements for the device drivers of all devices you want to use from your computer. These statements take the following form: DEVICE=\ where is the drive and path where you installed the device drivers and is the name of the driver. The VisualInfo-installed device drivers are located in the \DLL subdirectory where you installed the Image Services component. ________________________________________________________ 4.0 Database considerations ________________________________________________________ 4.1 DB2 UDB Software Developer's Kit is required by VI The Software developer's Kit component of DB2 UDB contains the sqlprep.exe program which is needed by VI Library Server to compile the Library Server Dll's. Symptom is Library Server build of dll's fails. FRN7634 logged in FFST with RC=1041. 4.2 Databases must be re-bound after VisualInfo Fixpack installation The Library and Object Server databases must be re-bound after this Fixpack. 4.3 SBTEVENTS table cleanup The library includes the SBTEVENTS table for recording application and system events. The majority of events may be those produced as folders and documents move through the workflow. There are situations where event table entries are never deleted, which can cause this table to become quite large. To reduce the size of the events table, use DB2 to remove unnecessary events. Be sure to remove only those events that are of no interest to you. The EventCode field in the SBTEVENTS table identifies the type of event. This field contains the following values: Value Definition ----- ---------- 1-25 Events related to workbaskets, workflows, etc. 1000 History (activity) log transition utility 1001 Expired time check utility 1002 Database reorganization utility 1003 Database "runstats" utility >=4096 Application events For example, to delete all the workbasket and workflow events, use the following commands (assuming your library server is LIBSRVR2): dbm start using database libsrvr2 dbm "delete from sbtevents where eventcode = 25" In addition, to avoid the generation of events by the Folder Manager, use "SET FRNFMEVENTS=0" in the CONFIG.SYS file. If this variable is not specified or is nonzero, normal event logging occurs. 4.4 Restrictions using Oracle databases The following restrictions apply when using Oracle for the server database. These will result in errors if they are attempted: 1) The Library Server Database Bind Utility and the Object Server Database Bind Utility found in the VisualInfo Utilities folder should not be used to bind Oracle databases. 2) When defining a database index on an index class through System Administration, the descending option should not be used for the key fields and order list. Oracle does not support descending sort key fields. ________________________________________________________ 5.0 Markup anomalies ________________________________________________________ 5.1 Highlighting color and grayscale documents When you are highlighting a displayed page within the VisualInfo client, if the document is color or grayscale, the highlight may be difficult to see. If the portion of the image underneath the highlight is dark, you may not be able to see any of the highlight. Because the colors for highlighting were chosen for their transparency, they work best with high-contrast images like black and white. 5.2 Client operating system differences (non-image pages) The displayed and printed presentation of the VisualInfo client for non-image content class documents (for example, word processing and spreadsheet) may differ from one operating system to another. These differences range from line lengths to how columnar, tabular, and embedded data are presented. Because of these differences, line and page breaks may occur at different locations within the same document, depending on the operating system used to create them. Also, the presentation and printing may differ from that performed by the native executable program (for example, a word processor or spreadsheet program) for that content class. A major consequence of this is that annotations made using a VisualInfo client on one operating system may not appear in the same logical position when displayed on a different operating system for these non-image documents. Annotation position is based on the displayed page and the offset from the upper left corner of the displayed image. If the non-image document has differences in the pages or in the information within the page, any annotation (highlight or note) will not appear in the same logical location. Thus, highlighting a paragraph of text in one operating system does not ensure that it will be displayed correctly when viewed using a different operating system client. 5.3 Client restriction in Simplified Chinese version The Simplified Chinese version of the Client for OS/2 does not support the note log or note annotations (also called sticky notes) if OS/2 is using code page 1381 ("GB" code page). ________________________________________________________ 6.0 Miscellaneous ________________________________________________________ 6.1 FFST/2 consideration VisualInfo OS/2 component error logging functions are enabled to work with FFST/2 provided on OS/2 Version 3.0 and earlier. These error logging functions do not work with the version of FFST provided with OS/2 Version 4.0. If you want to enable error logging for VisualInfo components on OS/2 Version 4.0, install FFST/2 included with the VisualInfo product. Note that this version of FFST is provided in English only. 6.2 Limitations for non-image files The VisualInfo Client for OS/2 supports the double-byte character set (DBCS) for the ASCII data format, but you may have to register a language-appropriate font. See the README.IS2 file for details on how to set the FIWTDBCSFONT variable in your CONFIG.SYS file. 6.3 Path and File Name Character Limitations When entering path names or file names, only the following characters may be used, regardless of language: ABCEDFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789()'-_&% 6.4 Command Line Interface for VI Fax Background Processor The VisualInfo Fax Background Processor has a command line interface that may be used for automation or debugging purposes. The syntax is as follows: FRNOFXBP.EXE /U:userid /P:password /L:library [/D:] - a '=' can be used instead of the ':'. - The options can be in upper or lowercase and in any order. - If all 3 options are not present, then the logon panel will be displayed. If the logon fails, the logon panel will be displayed. - The fourth option, /d: or /d=, which causes debugging messages to be logged to the frnofxbp.log file, is optional, but requires the /U /P and /L parameters. ________________________________________________________ 7.0 APAR Fixes with Descriptions ________________________________________________________ APARs contained in Fixpack2 for 2.x.x APAR NUMBER: IR41001 COMPONENT: Object Server PMR NUMBER: 47961 APAR DESCRIPTION: Lan cache file copies not left when migrating files from staging area to remote server. Some perfotmance degradation caused if server must cache a copy on a subsequent retrieve request. Impact will vary depending on cache usage. FIX DESCRIPTION: Internal value incorrectly translated. Should be applied to all Lan Cache systems APAR NUMBER: IR40801 COMPONENT: dltoolkit PMR NUMBER: 99999 APAR DESCRIPTION: The following problems exist with WIN VI 2.4 Folder Manager Trace: . When running folder manager trace by setting environment variable FRNFMTRACE=/P, the trace contains the following erroneous information: . 1. SimLibSearch API . The input parameter ulMemListRequest is reported as having the value TRUE or FALSE in the trace, although the API allows five possible values for this parameter. The trace should be changed to record the actual value passed to the API. . 2. Unknown ftn 82 . The trace contains an API request with the API name 'Unknown ftn 82' The trace should be changed to give the actual API name. This API is called by the standard client application VIC.EXE during logon to VisualInfo. The trace should be changed to recognise this API. . 3. Unknown ftn 164 . When calling the new API SimLibStoreObject, the folder manager trace contains the API name 'Unknown ftn 164'. The trace should be changed to recognise this API. . 4. Ip2GetNextWorkbasketInWorkflow . The trace incorrectly shortens the name of this API to Ip2NextWorkbasketInWorkflow (missing the word 'Get'). . Folder Manager trace is a valuable diagnostic tool for understanding application programming and performance issues and should be kept current as the APIs change. FIX DESCRIPTION: Change foodump.c to add additional information as user requested. APAR NUMBER: IR41099 COMPONENT: System Administration PMR NUMBER: 44391,077,724 APAR DESCRIPTION: OS/2 FRNOSA.EXE does not properly reflect the users logged on after an user is forced off. FIX DESCRIPTION: Add function to refresh the logon user count. APAR NUMBER: IR41275 COMPONENT: VI Client PMR NUMBER: 31688,001,866 APAR DESCRIPTION: NULLs were embedded between entries in the notelog, preventing the entire notelog contents from being copied and pasted into another application. FIX DESCRIPTION: NULLs are now converted to blanks when the text is loaded into the notelog. APAR NUMBER: IR41088 COMPONENT: Client Application PMR NUMBER: 68763 APAR DESCRIPTION: If a user tries to export (in Common Interchange Format) a folder that contains an infinite loop (e.g. Folder A contains Folder B which contains Folder C which contains Folder A), the client hangs. FIX DESCRIPTION: The client will now detect folder nesting beyond 40 levels and reject this, assuming it to be an infinite loop. APAR NUMBER: IR41452 COMPONENT: Client Application PMR NUMBER: 53909,001,866 APAR DESCRIPTION: Library Servers used to require two single quotes, at least for dynamic queries. That is, a search for "O'Brian" would cause an SQL error where a search for "O''Brian" would succeed. Now that the dynamic query syntax matches the static query syntax (only one single quote required), the client must be changed to submit this. FIX DESCRIPTION: The client no longer doubles single quotes when searching. APAR NUMBER: IR41544 COMPONENT: Client Application PMR NUMBER: 79202,071 APAR DESCRIPTION: Searches over "All Classes" that matched more items than either the server would return (as specified in the LS Configuration) or than the client would display (as specified in FRNDISPLAYCOUNT) resulted in misleading warning messages. It appeared that the search was not functioning correctly. FIX DESCRIPTION: The Library Server was returning more rows than requested but this was because the search was over multiple index classes and the limit is per class, not overall. Two changes are being made in the client to clear up the warning message: 1) The client will never request more rows than the server would return. Until now, if FRNDISPLAYCOUNT were 10000 but MaxRows on the server were 5000, the client would pointlessly request 10000 rows, even though it would never get more than 5000 out of a Search Results folder. 2) The warning message will not say how many items were really returned, just that it was at least 1 more than the number that can be shown. APAR NUMBER: IR41078 COMPONENT: Image Services PMR NUMBER: 27316,070,724 & 54956,077,724 & 30024,077,724 & 02706,090,618 APAR DESCRIPTION: After installing VI v2.4.1 the customer receives the following when viewing a document: FRN:6616a can't open sec. window, FFST: FRN6750A image service calls were not successfull, FRN6605A: problem occured in library object window FIX DESCRIPTION: Image Services DLLs were correctly re-built not to link the compiler's run-time DLL. APAR NUMBER: IR41696 COMPONENT: Client Application PMR NUMBER: 91371 APAR DESCRIPTION: If one object matches a Basic Search, it should be opened when the search completes. But if the object was only viewable in a subset (user doesn't have access to base index class), an error was being returned instead. FIX DESCRIPTION: Permissions for the active view/subset, rather than the base index class, are now being checked so that objects will be openable when they should be. APAR NUMBER: IR41432 COMPONENT: Client Application PMR NUMBER: 25605,033,724 APAR DESCRIPTION: The hOrigClass parameter in the USEREXITSTRUCT passed to the ChangeSMS user exit does not contain the correct original class number. FIX DESCRIPTION: The parameter is now correct. APAR NUMBER: IR39330 COMPONENT: IS/2 PMR NUMBER: 26667 B090, C616 APAR DESCRIPTION: Masks should be saved even when storing document only. Documents stored without this fix may be missing their masks. This is not evident until the documents are retrieved! FIX DESCRIPTION: Correct code to save masks even when storing documents only APAR NUMBER: IR40920 COMPONENT: Client Application PMR NUMBER: 60969,180 APAR DESCRIPTION: Importing large (~5MB) CIF documents was running out of memory. FIX DESCRIPTION: Memory usage on file import has been made more efficient. APAR NUMBER: IR41005 COMPONENT: Client Application PMR NUMBER: 00001,Z55 APAR DESCRIPTION: VhlImportDocObj was failing to import documents whose content class was < 8 characters FIX DESCRIPTION: The imports now suceed APAR NUMBER: IR41028 COMPONENT: Client Application PMR NUMBER: 68241,180 APAR DESCRIPTION: Notelogs were corrupted on export / import using common interchange format. CRLF characters (0d0a) are being converted to LFLF (0a0a). FIX DESCRIPTION: CRLF sequences are now handled correctly. APAR NUMBER: IR40502 COMPONENT: Object Server PMR NUMBER: 30281,057,649 APAR DESCRIPTION: When Migrator attempted to migrate objects with size larger than the free space at the target volume, it did not issue the FRN9882A message at the operator console. The destager had the same problem. FIX DESCRIPTION: When the object server detects the object to be moved is larger than the free pace available on the target volume, put FRN9882A message to both FFST log and operator console. APAR NUMBER: IR37875 COMPONENT: Object Server PMR NUMBER: 01008,324 APAR DESCRIPTION: VisualInfo - Digital Library - Object Server - Optical Two scenarios have been detected where the client makes a second request for an object located on an offline optical platter. One is where the client selects RETRY in the FRN4320W popup window at the client. The other is where the client select CANCEL in the FRN4320W popup window and then later requests the same object. The object server posts (apparently a normal sequence of messages) FRN7030A, FRN9924A, FRN9919A rc 9936 with FRN9924 showing up in different places depending on how the problem is encountered. FIX DESCRIPTION: Fixed problem with allocating/deallocating resources to display volume information in the popup window. APARs contained in Fixpack1 for 2.4.x APAR NUMBER: IR37365 COMPONENT: LIBRARY SERVICE PMR NUMBER: 84360,060 APAR DESCRIPTION: In SIMLIBCREATEITEM API, if user provides duplicate item names, the API goes into an infinite loop trying to get a unique item id. user should not input duplicate item names FIX DESCRIPTION: In SIMLIBCREATEITEM API, added loop control to avoid infinite loop when user provided duplicated item names. APAR NUMBER: IR39736 COMPONENT: IMAGE SERVICES PMR NUMBER: 76132,400 APAR DESCRIPTION: There is no feature in VI OS/2 to allow the scanner to pause after x pages have been scanned. This was a feature in IWPM V1 and was not in IWPM V2 OS/2 . FIX DESCRIPTION: FIWSS.DLL was changed to enable this function. FIWSS.DLL was changed to allow one to do non-batch scanning and pause the scanner after x pages have been scanned. By adding an OS/2 environmental: FIW_PAUSEAFTERNPAGES, the user can go to the DTP settings window, and select in the "Begin new Document" group box: After (number) of pages have been scanned. The environmental FIW_PAUSEAFTERNPAGES tells the code to pause the scanner after the number of pages have been scanned as opposed to sending an end-of-document return code to the caller as is the case when the OS/2 environmental is not present. APAR NUMBER: IR38760 COMPONENT: IWPM PMR NUMBER: 27803,004 APAR DESCRIPTION: When displaying or printing a JPEG image that does not contain the JFIF (JPEG File Interchange Format) header, IWPM/NT switches the red and blue color mappings on the image. FIX DESCRIPTION: Code was changed to resolve problem. APAR NUMBER: IR39580 COMPONENT: IWPM PMR NUMBER: 27754,004 APAR DESCRIPTION: PCL Optimized Printer was not recognizing the size of the pages being printed and was unable to switch trays based on page size. FIX DESCRIPTION: Code was changed to resolve problem. APAR NUMBER: IR39271 COMPONENT: VI OS/2 CLIENT PMR NUMBER: 68366,180 APAR DESCRIPTION: The logon on did not work for recieve mail. FIX DESCRIPTION: code fix corrected problem APAR NUMBER:IR38604 COMPONENT: IMAGEPLUS WKST PMR NUMBER: 46788,005 APAR DESCRIPTION: Under IWPM V121 no MIO MODCA tag was placed in documents as they were scanned and stored. In V210 this changed. Logic was added to include the MIO tag and depending on the situation assign it 1 of 3 different values. The values determine how the document will be treated - clip to fit, shrink to fit, etc. If the MIO tag is absent the defaultis shrink to fit. It appeared that for some cases under V210 that the only value being assigned was for clip to fit which caused the loss of some of the document along the edges when printing. FIX DESCRIPTION: An environment variable was added to effectively turn off the MIO tag. It actually sets the value to shrink to fit which is what would be assigned by default if the tag was not there. It requires the inclusion of the environment variable MIOTAGNOT in the config.sys. Its presence automatically turns off the tag. APAR NUMBER: IR38864 COMPONENT: IMAGE SERVICES PMR NUMBER: 95627,010 APAR DESCRIPTION: t: The VisualInfo Client is hanging when closing a document window. The customer is running VI version 2.03.1 CSD level UR02311 on a Dani version 2.11 with CSD level XRD6200. VI client fails when running the following scenario: Documents are selected in a Workbasket and opened in New windows pressing the Enter key. The 5 windows appear with the documents just as expected. The windows are closed again one after another with ALT+ then sometimes the VI client is hanging: I.e. The cursor is a clo the VI client is not responding to PM message. After pressing FIX DESCRIPTION: Fixed by this APAR. APAR NUMBER: IR39281 COMPONENT: VI OS/2 CLIENT PMR NUMBER: 95708,060 APAR DESCRIPTION: Every time a Danish VI client start an information message is logged to the OS/2 message log saying "FRN2900I: A problem occurred in loading a string from the dynamic link library of Presentation Manager resources. The application will use a hard-coded string" The corresponding message from the OS/2 system log is as follow: FIX DESCRIPTION: Fixed by this APAR. APAR NUMBER: IR39438 COMPONENT: IMAGE SERVICES PMR NUMBER: 08820,031 APAR DESCRIPTION: When doing a batch scan, after many documents have been scanned and stored, message FIW2203A will appear and scanning cannot continue FIX DESCRIPTION: During the batch scan overlap mode, the recently scanned document will get moved to the store workingset and then get stored to the host. After the store was done, a delete document command SimWsDeleteObj is called. This process will delete all objects in document including the cache compon- ents. Howver, before the delete request thread can signal that this document can be deleted, another thread that actually deletes the objects has already checked this document flag and saw that it was not ready to be deleted. This will cause PMGPI allocated storage (display memory) to never be freed. APAR NUMBER: IR39387 COMPONENT: IMAGE SERVICES PMR NUMBER: 65092,031 APAR DESCRIPTION: The SVI PTOCA tag was not recognized or processed. FIX DESCRIPTION: Support for SVI tags in a PTOCA document within a MO:DCA document was added. APAR NUMBER: IR39387 COMPONENT: IMAGE SERVICES PMR NUMBER: APAR DESCRIPTION: The SVI PTOCA tag was not recognized or processed. FIX DESCRIPTION: Support for SVI tags in a PTOCA document within a MO:DCA document was added. APAR NUMBER: IR40502 COMPONENT: Object Server PMR NUMBER: 30281,057,649 APAR DESCRIPTION: When Migrator attempted to migrate objects with size larger than the free space at the target volume, it did not issue the FRN9882A message at the operator console. The destager had the same problem. FIX DESCRIPTION: When the object server detects the object to be moved is larger than the free pace available on the target volume, put FRN9882A message to both FFST log and operator console. APAR NUMBER: IR40711 COMPONENT: 5648A0830 PMR NUMBER: 03810,070,724 APAR DESCRIPTION: Store/Retrieve fails if loopback enabled FIX DESCRIPTION: Isolator modified to skip loopback address (127.0.0.1) if another, real address present in list APAR NUMBER: IR37185 COMPONENT: Library Services PMR NUMBER: n/a APAR DESCRIPTION: Ip2ListHistory won't provide variable text in different messages. FIX DESCRIPTION: Fixed DosGetMessage function to handle variable text. Updated frnwutf.txt to add messages 2250 to 2272 in both English and German versions of the message files. APAR NUMBER: IR40820 COMPONENT: Toolkit PMR NUMBER: APAR DESCRIPTION: If a user searches for items in an index class by using either the VI standard client application or the function SimLibSearch with option SIM_SEARCH_MAKE_FOLDER, and if there was at least one item found with an ACL that does not authorize the user to access the item, the complete search aborts with errors 7083 and 6260 instead of just skipping the items with insufficient access rights for this operation. In addition, 6260 = SIM_RC_PRIVILEGE_ERROR should not be returned by SimLibSearch according to latest docs. FIX DESCRIPTION: Modified parameter for LibraryClient API to filter out unauthorized objects if SIM_SEARCH_MAKE_FOLDER is specified. APAR NUMBER: IR39255 COMPONENT: Object Server PMR NUMBER: 25548 APAR DESCRIPTION: The migrator ends its cycle prematurely (stalls) if the last object in a batch cannot be migrated. In a system where many migrator errors occur, this can prevent the migrator ever processing some objects and reduces migrator throughput. If all objects in a batch failed the migration, then the rest of objects will not be migrated not even at the next cycle. This is because the entire failing batch will be reselected again at the next cycle. FIX DESCRIPTION: After issueing a migration failure message (FRN9816) for a single object, the migrator will ignore the failure and continue to process other migration candidates. APAR NUMBER: IR37200 COMPONENT: Object Server PMR NUMBER: 21279,487 APAR DESCRIPTION: Incremental backups fail due to the archive bit is not set during migration from DASD to optical. The problem was triggered by the files on DASD has been backed up previously and have the archive bit turned off before the migration to optical. FIX DESCRIPTION: The migrator will set the archive bit after migration to optical. APAR NUMBER: IR36844 COMPONENT: Object Server PMR NUMBER: 63637,B057,C649 APAR DESCRIPTION: 1. When Migrator attempted to migrate objects to optical and encountered a logically write protected platter, it logged an write error as expected. However, Migrator continued to attempt to migrate the rest of the objects to the same platter rather than skipping to another one that might work. 2. After a volume is marked full by using the system administration tool and VI is re-cycled. the migrator is still tried to write to that volume, even there are other volumes available. FIX DESCRIPTION: 1. Fix has been put in the migrator so that dDuring migration cycle, if the migrator detects that there are more than 10 write errors from a volume, the migrator will mark the volume full and issue a new message FRN9743. After this action, the object server will not migrate any object to that volume. 2. Fix has been put in the Object server so that when a volume has been marked full, it will not be selected as the target volume for store operation. APAR NUMBER: IR38601 COMPONENT: Object Server PMR NUMBER: 11561, B689 APAR DESCRIPTION: VisualInfo - Digital Library - Object Server Message FRN9883E is posted in FFST but there is no entry in the trace making it difficult to identify where in the event sequence the error occurrence. FIX DESCRIPTION: In migrator add a trace msg to match with FFST. APAR NUMBER: IR38605 COMPONENT: Object Server PMR NUMBER: 11561 B689 APAR DESCRIPTION: VisualInfo - Digital LIbrary - Object Server FFST logs FRN9814A during shutdown but the trace has no respective entry. In the case of this PMR, the DosStopSession API could not be used to stop a PID. FIX DESCRIPTION: Add trace msg to match FFST msg. APAR NUMBER: IR38646 COMPONENT: Object Server PMR NUMBER: 11561 APAR DESCRIPTION: FIX DESCRIPTION: Disable hard problem pop up window, and if chmod failed on discard, don't delete object row, update the action date to a new date to prevent this object keep picking up by Migrator. APAR NUMBER: IR37283 COMPONENT: Library Services PMR NUMBER: 84216,010 APAR DESCRIPTION: 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 contents of EventData: "SCANNER1","Demo, testwb","100" FIX DESCRIPTION: Ip2ListHistory has been fixed to handle comma as part of a workbasket name. APAR NUMBER: IR38955 COMPONENT: Object Server PMR NUMBER: APAR DESCRIPTION: Small objects can not be destaged. FIX DESCRIPTION: Modified the code to get the real system error code, and add extra byte check for volume selection. APAR NUMBER: IR40920 COMPONENT: Client Application PMR NUMBER: 60969,180 APAR DESCRIPTION: Importing large (~5MB) CIF documents was running out of memory. FIX DESCRIPTION: Memory usage on file import has been made more efficient. APAR NUMBER: IR41005 COMPONENT: Client Application PMR NUMBER: 00001,Z55 APAR DESCRIPTION: VhlImportDocObj was failing to import documents whose content class was < 8 characters FIX DESCRIPTION: The imports now suceed. APAR NUMBER: IR41028 COMPONENT: Client Application PMR NUMBER: 68241,180 APAR DESCRIPTION: Notelogs were corrupted on export / import using common interchange format. CRLF characters (0d0a) are being converted to LFLF (0a0a). FIX DESCRIPTION: CRLF sequences are now handled correctly. APAR NUMBER: IR40484 COMPONENT: OS/2 Client PMR NUMBER: 03202,023 APAR DESCRIPTION: Date fields in Index windows were allowing 3-digit years, such as "199". FIX DESCRIPTION: The client will now reject dates between 100 and 999 inclusive. Also, 2-digit dates will be immediately converted (as soon as the focus leaves the field) to 4-digit dates in Date-type key fields. As an intended side-effect, the Suspend dialogs will no longer allow 2-digit dates. APAR NUMBER: IR39188 COMPONENT: IS/2 PMR NUMBER: 26637 B090 C616 APAR DESCRIPTION: VI goes away when help not available FIX DESCRIPTION: Catch IBM Open Class exceptions if help not present APAR NUMBER: IR39330 COMPONENT: IS/2 PMR NUMBER: 26667 B090, C616 APAR DESCRIPTION: Masks should be saved even when storing document only. Documents stored without this fix may be missing their masks. This is not evident until the documents are retrieved! FIX DESCRIPTION: Correct code to save masks even when storing documents only APAR NUMBER: IR40140 COMPONENT: VI Client for Windows PMR NUMBER: 99999,999,000 APAR DESCRIPTION: Missing Windows Client sample files and outdated header file. The sample code is documented in the installation/planning guide but can't be found after install. The files were in the install image but the installation program does not copy them to the user's machine. The header(FRNPLW.H) file shipped was not up-to-date. Starting CM V2.4NLV, the sample codes are shipped/installed as requested. The missing files are listed below: frnpexto.cpp frnpexto.mak frnplw.h frnwuecp.c frnwuecp.def frnwuecp.dsp frnwuecp.mak tables.h FIX DESCRIPTION: Created self-extracted zip files for users who needs the files to download. APAR NUMBER: IR40341 COMPONENT: OS/2 Client PMR NUMBER: 87199 APAR DESCRIPTION: System got a SYS3175 at view of documents with VHLPI commands in modul PMMERGE:DLL. Problem: Via VHLPI Functions customer displays docs or folders. The SYS3175 errors occur either when opening or closing folders or docs. The error condition is not reproduceable but in some cases he gets in FFST the following error msg: FRN2900I These errors happen often under C++ but seldom under REXX PAGE FIX DESCRIPTION: With the updated FRNOLW.DLL from this APAR fix, the Vhl APIs will no longer trap when closing windows. APAR NUMBER: IR39311 COMPONENT: Client Application PMR NUMBER: 89432,071 APAR DESCRIPTION: Error messages displayed when attempting to export or view a document with no parts do not give enough information. FIX DESCRIPTION: More explicit error messages have been added.