################################################################################ # IBM EDMSuite OnDemand # # AIX, HP-UX, WinNT # # README # # Release 2.2.0.14 # # February 3, 1998 # # # # 5622-662, 5765-D60, 5639-E12 (C) COPYRIGHT IBM CORPORATION 1998 # # All Rights Reserved # # Licensed Materials - Property of IBM # # US Government Users Restricted Rights - Use, duplication or # # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # ################################################################################ The information about OnDemand contained in this file was not available at the time the OnDemand documentation was printed. Please make note of these items, which supersede the information contained in the OnDemand product publications. **********************************URGENT**************************************** * PLEASE READ SECTION 6 FOR LATEST ONDEMAND PROBLEMS REQUIRING ACTION * * PLEASE READ SECTION 7 FOR LATEST ONDEMAND PREREQ CHANGES * ******************************************************************************** ================================================================================ 1. Contents 2. Server Change History 2.1 AIX Server 2.1.2.2.0.0 Release (2.2.0.0) 2.1.2.2.0.1 PTF (2.2.0.1) 2.1.2.2.0.2 PTF (2.2.0.2) 2.1.2.2.0.3 PTF (2.2.0.3) 2.1.2.2.0.4 PTF (2.2.0.4) 2.1.2.2.0.5 PTF (2.2.0.5) 2.1.2.2.0.6 PTF (2.2.0.6) 2.1.2.2.0.7 PTF (2.2.0.7) 2.1.2.2.0.8 PTF (2.2.0.8) 2.1.2.2.0.9 PTF (2.2.0.9) 2.1.2.2.0.10 PTF (2.2.0.10) 2.1.2.2.0.11 PTF (2.2.0.11) 2.1.2.2.0.12 PTF (2.2.0.12) 2.1.2.2.0.13 PTF (2.2.0.13) 2.1.2.2.0.14 PTF (2.2.0.14) 2.2 Windows NT Server 2.2.2.2.0.5 Release (2.2.0.5) 2.2.2.2.0.6 PTF (2.2.0.6) 2.2.2.2.0.7 PTF (2.2.0.7) 2.2.2.2.0.8 PTF (2.2.0.8) 2.2.2.2.0.9 PTF (2.2.0.9) 2.2.2.2.0.10 PTF (2.2.0.10) 2.2.2.2.0.11 PTF (2.2.0.11) 2.2.2.2.0.12 PTF (2.2.0.12) 2.2.2.2.0.13 PTF (2.2.0.13) 2.2.2.2.0.14 PTF (2.2.0.14) 2.3 HP-UX Server 2.3.2.2.0.12 Release (2.2.0.12) 2.3.2.2.0.13 PTF (2.2.0.13) 2.3.2.2.0.14 PTF (2.2.0.14) 2.4 ACIF 2.4.2.2.0.0 Release (2.2.0.0) 2.4.2.2.0.1 PTF (2.2.0.1) 2.4.2.2.0.2 PTF (2.2.0.2) 2.4.2.2.0.3 PTF (2.2.0.3) 2.4.2.2.0.4 PTF (2.2.0.4) 2.4.2.2.0.5 PTF (2.2.0.5) 2.4.2.2.0.6 PTF (2.2.0.6) 2.4.2.2.0.7 PTF (2.2.0.7) 2.4.2.2.0.8 PTF (2.2.0.8) 2.4.2.2.0.9 PTF (2.2.0.9) 2.4.2.2.0.10 PTF (2.2.0.10) 2.4.2.2.0.11 PTF (2.2.0.11) 2.4.2.2.0.12 PTF (2.2.0.12) 2.4.2.2.0.13 PTF (2.2.0.13) 2.4.2.2.0.14 PTF (2.2.0.14) 3. Client Change History 3.1 Windows 3.1 Client 3.1.2.2.0.0 Release (2.2.0.0) 3.1.2.2.0.1 PTF (2.2.0.1) 3.1.2.2.0.2 PTF (2.2.0.2) 3.1.2.2.0.3 PTF (2.2.0.3) 3.1.2.2.0.4 PTF (2.2.0.4) 3.1.2.2.0.5 PTF (2.2.0.5) 3.1.2.2.0.6 PTF (2.2.0.6) 3.1.2.2.0.7 PTF (2.2.0.7) 3.1.2.2.0.8 PTF (2.2.0.8) 3.1.2.2.0.9 PTF (2.2.0.9) 3.1.2.2.0.10 PTF (2.2.0.10) 3.1.2.2.0.11 PTF (2.2.0.11) 3.1.2.2.0.12 PTF (2.2.0.12) 3.1.2.2.0.13 PTF (2.2.0.13) 3.1.2.2.0.14 PTF (2.2.0.14) 3.2 OS/2 Client 3.2.2.2.0.0 Release (2.2.0.0) 3.2.2.2.0.1 PTF (2.2.0.1) 3.2.2.2.0.2 PTF (2.2.0.2) 3.2.2.2.0.3 PTF (2.2.0.3) 3.2.2.2.0.4 PTF (2.2.0.4) 3.2.2.2.0.5 PTF (2.2.0.5) 3.2.2.2.0.6 PTF (2.2.0.6) 3.2.2.2.0.7 PTF (2.2.0.7) 3.2.2.2.0.8 PTF (2.2.0.8) 3.2.2.2.0.9 PTF (2.2.0.9) 3.2.2.2.0.10 PTF (2.2.0.10) 3.2.2.2.0.11 PTF (2.2.0.11) 3.2.2.2.0.12 PTF (2.2.0.12) 3.2.2.2.0.13 PTF (2.2.0.13) 3.2.2.2.0.14 PTF (2.2.0.14) 3.3 Windows 32-bit Client 3.3.2.2.0.0 Release (2.2.0.0) 3.3.2.2.0.1 PTF (2.2.0.1) 3.3.2.2.0.2 PTF (2.2.0.2) 3.3.2.2.0.3 PTF (2.2.0.3) 3.3.2.2.0.4 PTF (2.2.0.4) 3.3.2.2.0.5 PTF (2.2.0.5) 3.3.2.2.0.6 PTF (2.2.0.6) 3.3.2.2.0.7 PTF (2.2.0.7) 3.3.2.2.0.8 PTF (2.2.0.8) 3.3.2.2.0.9 PTF (2.2.0.9) 3.3.2.2.0.10 PTF (2.2.0.10) 3.3.2.2.0.11 PTF (2.2.0.11) 3.3.2.2.0.12 PTF (2.2.0.12) 3.3.2.2.0.13 PTF (2.2.0.13) 3.3.2.2.0.14 PTF (2.2.0.14) 3.4 Windows 32-bit Administrator 3.4.2.2.0.0 Release (2.2.0.0) 3.4.2.2.0.1 PTF (2.2.0.1) 3.4.2.2.0.2 PTF (2.2.0.2) 3.4.2.2.0.3 PTF (2.2.0.3) 3.4.2.2.0.4 PTF (2.2.0.4) 3.4.2.2.0.5 PTF (2.2.0.5) 3.4.2.2.0.6 PTF (2.2.0.6) 3.4.2.2.0.7 PTF (2.2.0.7) 3.4.2.2.0.8 PTF (2.2.0.8) 3.4.2.2.0.9 PTF (2.2.0.9) 3.4.2.2.0.10 PTF (2.2.0.10) 3.4.2.2.0.11 PTF (2.2.0.11) 3.4.2.2.0.12 PTF (2.2.0.12) 3.4.2.2.0.13 PTF (2.2.0.13) 3.4.2.2.0.14 PTF (2.2.0.14) 4. Loading On-line Publications 5. Documentation Corrections 6. Urgent Problems 6.1 (October 8, 1998) Unexpected expiration of database indexes 6.2 (February 3, 1999) Unexpected expiration of resources from ADSM 7. Pre-req changes 7.1 (February 3, 1999) ================================================================================ 2. Server Change History -------------------------------------------------------------------------------- 2.1 AIX Server 2.1.2.2.0.0 Release (2.2.0.0) 2.1.2.2.0.1 PTF (2.2.0.1) - Added DB2 Version 5 user exit db2uext2 (disk/adsm) - Fixed a bug which caused the server to get 'unable to communicate to object server' message when deleting an application group - Fixed a bug which caused the server to drop core or fail with 'unable to close file errno = 9' message during server printing 2.1.2.2.0.2 PTF (2.2.0.2) - Fixed a bug which caused the server to store an invalid value for the storage set load type - Fixed a bug which caused ars_load to fail during loading when using the -c option and the ACIF CONVERT=NO option 2.1.2.2.0.3 PTF (2.2.0.3) - Added support for new compression algorithm OD77 NOTE: All OnDemand clients MUST be at 2.2.0.0 or later in order to support OD77 - Changed default arsadmin compression from LZW16 to OD77 - Fixed a bug which caused the server to leave defunct processes after deleting an application group 2.1.2.2.0.4 PTF (2.2.0.4) - Added support for enhanced N-UP - Fixed a bug which caused improper communication between Object and Library Servers 2.1.2.2.0.5 PTF (2.2.0.5) - Added new command arsdoc. This command will phase out the existing arsdocget and arsquery commands. 2.1.2.2.0.6 PTF (2.2.0.6) - Added support to retry cancel requests when DB2 is dealing with a generic and poor performance query - Fixed a bug which caused a performance degradation during document retrieval due to documents being stored using the wrong compressed object size - Fixed a bug which caused loading to fail when multiple hits point to the same large object document 2.1.2.2.0.7 PTF (2.2.0.7) - Added OnDemand instance support - Fixed a bug which caused arsdoc to be unable to write to output file - Fixed a bug which made resources unavailable for retrieval or back caching when using ADSM - Fixed a bug which caused ars_adsm to not work correctly with ADSM Version 3 2.1.2.2.0.8 PTF (2.2.0.8) - Added arsadm command (replaces arsuser). Used for both users/groups - Added arsdoc print command - Fixed a bug which caused arsjesd to not properly calculate filesystem sizes for large filesystems 2.1.2.2.0.9 PTF (2.2.0.9) - Fixed a bug which caused a DBCS index characters to be improperly converted - Fixed a bug which caused arsview to fail when converting a large object segment 2.1.2.2.0.10 PTF (2.2.0.10) - Fixed a bug which could cause arsjesd to core dump during checkpoint - Added support for server-based selective print 2.1.2.2.0.11 PTF (2.2.0.11) - Added support for arsdb command, will replace ars_db - Added support for arsload command, will replace ars_load - Added support for arssyscr command, will replace arssys.create 2.1.2.2.0.12 PTF (2.2.0.12) - Fixed a bug which caused unexpected expiration of database indexes - Fixed a bug which caused processes to remain present - Fixed a bug which caused arsmaint -c (Cache Expiration) to stop after the first filesystem in which to expire data - Fixed a bug which caused db2uexit/db2uext2 to fail when writing to disk (introduced in 2.2.0.11) - Fixed a bug which caused max rows in arsseg table to be exceeded under high volume loading - Fixed a bug which caused an ADSM error when a folder is defined with Find Document Location and document is not viewable - Fixed a bug in ars_adsm to support both V2 and V3 2.1.2.2.0.13 PTF (2.2.0.13) - Fixed a bug in PDF indexer when finding the coordinates - Fixed a bug in PDF indexer so that the subkeyword type=trigger is optional instead of required - Fixed a bug in arsjesd which caused defunct processes to remain - Fixed a bug in arsjesd which caused a core dump during checkpoint restart - Fixed a bug in all clients which caused the server to generate a message indicating the retrieval of data failed because the document requested was larger than the size of the object - Fixed a bug which caused arsdoc to not retrieve all of the data for a document that is a large object - Added support for generating concurrent usage messages to the system log 2.1.2.2.0.14 PTF (2.2.0.14) - Added support for presenting the client an image overlay to use during local printing. - Added support for validating the loadid from the System Log when unloading data - Added additional information during unload process, number of rows deleted and number of objects deleted - Added support for server-based search of annotation text and annotation text color attributes - Added support so that when adding documents individually, string fields use proper case-sensitivity. Previously it was the responsibility of the user to ensure proper case - Added support for doing a single login to ADSM per node during bulk document retrieval (cdrom, server printing). - Added support for arsdoc query to display the loadid for a document's particular load - Added support for arsdoc query to output document handle information - Changed System Log codepage to be UTF-8 instead of 819 - Fixed a bug which caused arssockd to not start without messages when using an instance other than the default ARCHIVE instance - Fixed a bug which caused a field to be processed twice when specifying a postprocess command for an application. If a field was setup to divide by 100, then it would actually be divided by 10000 - Fixed a bug in arspdoci (PDF Indexer) which caused an error with valid parameters - Fixed a bug for reloading resources to ADSM in order to avoid ADSM expiring the resource too soon --------------end of AIX Server------------------------------------------------- 2.2 Windows NT Server 2.2.2.2.0.5 Release (2.2.0.5) - Initial Release 2.2.2.2.0.6 PTF (2.2.0.6) - Added support to retry cancel requests when DB2 is dealing with a generic and poor performance query - Fixed a bug which caused a performance degradation during document retrieval due to documents being stored using the wrong compressed object size - Fixed a bug which caused loading to fail when multiple hits point to the same large object document - Fixed a bug which caused arsload to not accept the -A and -G parameters 2.2.2.2.0.7 PTF (2.2.0.7) - Added OnDemand instance support - Fixed a bug which caused arsdoc to be unable to write to output file - Fixed a bug which made resources unavailable for retrieval or back caching when using ADSM - Fixed a bug which caused the arsload service to not be available after system reboot 2.2.2.2.0.8 PTF (2.2.0.8) - Added support for unified logon for WinNT using NTLM - Added arsadm command (replaces arsuser). Used for both users/groups - Added arsdoc print command - Fixed a bug which caused arsload to fail periodically - Fixed a bug which caused arssockd to GPF during periods of high activity 2.2.2.2.0.9 PTF (2.2.0.9) - Fixed a bug which caused a DBCS index characters to be improperly converted - Fixed a bug which caused arsview to fail when converting a large object segment - Fixed a bug which caused arsdb to fail when creating the database 2.2.2.2.0.10 PTF (2.2.0.10) - Fixed a bug which could cause arsjesd to GPF during checkpoint - Fixed a bug which caused multiple instances to not be supported under MSSQL - Fixed a bug which caused arsadmin to GPF during loading - Added support for server-based selective print 2.2.2.2.0.11 PTF (2.2.0.11) - Fixed a bug which caused Object Servers to GPF when accessed - Fixed a bug which caused OnDemand messages to be unknown to the WinNT event viewer 2.2.2.2.0.12 PTF (2.2.0.12) - Fixed a bug which caused unexpected expiration of database indexes - Fixed a bug which caused max rows in arsseg table to be exceeded under high volume loading - Fixed a bug which caused arsmaint -c (Cache Expiration) to stop after the first filesystem in which to expire data - Fixed a bug which caused db2uext2 to fail when writing to disk (introduced in 2.2.0.11) - Fixed a bug which caused an ADSM error when a folder is defined with Find Document Location and document is not viewable - Added support for Configurator to run arsdb and arssyscr during creating of OnDemand Instance 2.2.2.2.0.13 PTF (2.2.0.13) - Fixed a bug which caused arssockd to GPF when updating system information from the admin client - Fixed a bug in PDF indexer when finding the coordinates - Fixed a bug in PDF indexer so that the subkeyword type=trigger is optional instead of required - Fixed a bug in the configurator where after database creation failed, the configurator continued to the next step - Fixed a bug which caused the server to not start when using net start - Fixed a bug which caused loading to fail when specifying a postprocess command of sort | uniq - Fixed a bug which caused a tablespace to be specified for SQLServer - Fixed a bug which caused arscmd.exe to GPF - Fixed a bug which caused arsload.exe to fail if CONVERT=NO is below INPEXIT - Added support for generating concurrent usage messages to the system log 2.2.2.2.0.14 PTF (2.2.0.14) - Added support for ADSM being thread-safe - Added support for presenting the client an image overlay in which to use during client local printing. - Added support for validating the loadid from the System Log when unloading data - Added additional information during unload process, number of rows deleted and number of objects deleted - Added support for server-based annotation text and color attributes to be a part of a document query - Added support so that when adding documents individually, string fields use proper case-sensitivity. Previously it was the responsibility of the user to ensure proper case - Added support for doing a single login to ADSM per node during bulk document retrieval (cdrom, server printing). - Added support for arsdoc query to display the loadid for a document's particular load - Added support for arsdoc query to output document handle information - Removed ADSM service dependency - Changed System Log codepage to be UTF-8 instead of 819 - Fixed a bug which caused the configurator to not be able to stop arssockd when arsload is running - Fixed a bug which caused arssockd to not start without messages when using an instance other than the default ARCHIVE instance - Fixed a bug which caused a field to be processed twice when specifying a postprocess command for an application. If a field was setup to divide by 100, then it would actually be divided by 10000 - Fixed a bug in arspdoci (PDF Indexer) which caused an error with valid parameters - Fixed a bug for reloading resources to ADSM in order to avoid ADSM expiring the resource too soon --------------end of Windows NT Server------------------------------------------ 2.3 HP-UX Server 2.3.2.2.0.12 Release (2.2.0.12) - Initial Release 2.3.2.2.0.13 PTF (2.2.0.13) - Fixed a bug in PDF indexer when finding the coordinates - Fixed a bug in PDF indexer so that the subkeyword type=trigger is optional instead of required - Added support for generating concurrent usage messages to the system log 2.3.2.2.0.14 PTF (2.2.0.14) - Added support for presenting the client an image overlay in which to use during client local printing. - Added support for validating the loadid from the System Log when unloading data - Added additional information during unload process, number of rows deleted and number of objects deleted - Added support for server-based annotation text and color attributes to be a part of a document query - Added support so that when adding documents individually, string fields use proper case-sensitivity. Previously it was the responsibility of the user to ensure proper case - Added support for doing a single login to ADSM per node during bulk document retrieval (cdrom, server printing). - Added support for arsdoc query to display the loadid for a document's particular load - Added support for arsdoc query to output document handle information - Changed System Log codepage to be UTF-8 instead of 819 - Fixed a bug which caused arssockd to not start without messages when using an instance other than the default ARCHIVE instance - Fixed a bug which caused a field to be processed twice when specifying a postprocess command for an application. If a field was setup to divide by 100, then it would actually be divided by 10000 - Fixed a bug in arspdoci (PDF Indexer) which caused an error with valid parameters - Fixed a bug for reloading resources to ADSM in order to avoid ADSM expiring the resource too soon --------------end of HP-UX Server----------------------------------------------- 2.4 ACIF 2.4.2.2.0.0 Release (2.2.0.0) 2.4.2.2.0.1 PTF (2.2.0.1) - (APAR PQ07492) acif loops when input data contains overprint carriage controls and the pagedef contains bar code descriptors on the LNDs 2.4.2.2.0.2 PTF (2.2.0.2) - (APAR PQ08772) Processing failure for data with multiple bin encoding 2.4.2.2.0.3 PTF (2.2.0.3) 2.4.2.2.0.4 PTF (2.2.0.4) - (APAR PQ09307) Enhanced N-UP support 2.4.2.2.0.5 PTF (2.2.0.5) 2.4.2.2.0.6 PTF (2.2.0.6) 2.4.2.2.0.7 PTF (2.2.0.7) - (APAR PQ10246) Additional Windows NT Support 2.4.2.2.0.8 PTF (2.2.0.8) 2.4.2.2.0.9 PTF (2.2.0.9) - (APAR PQ15334) Negative offsets not working properly 2.4.2.2.0.10 PTF (2.2.0.10) - (APAR PQ16927) PQ16927 acif builds incorrect MCF2 for DBCS code page/set on 2nd page - Fixed a bug which caused arsacif to look for the wrong message file acif.cat instead of arsacif.cat - Added support for shipping compiled user exits 2.4.2.2.0.11 PTF (2.2.0.11) - (APAR PQ18140) acif loops under WinNT 2.4.2.2.0.12 PTF (2.2.0.12) - (APAR PQ19344) Port to HP-UX 2.4.2.2.0.13 PTF (2.2.0.13) - (APAR PQ21767) acif fread error 2.4.2.2.0.14 PTF (2.2.0.14) - (APAR PQ22677) data fails to acif - apkexits.h was modified, therefore any customer defined user exits must be recompiled --------------end of ACIF------------------------------------------------------- ------------------end of Server Change History---------------------------------- 3. Client Change History 3.1 Windows 3.1 Client 3.1.2.2.0.0 Release (2.2.0.0) 3.1.2.2.0.1 PTF (2.2.0.1) - Added new DDE functions - Fixed a bug which caused TIFF viewing to fail with message if data was invalid (missing byte on EOF) - Pixel Translations - Fixed a bug which caused an error -5016 when printing TIFF locally 3.1.2.2.0.2 PTF (2.2.0.2) - Fixed a bug which caused the client to improperly print DBCS line data - Fixed a bug which caused the client to drop pels when displaying line data 3.1.2.2.0.3 PTF (2.2.0.3) - Added support for new/modified command line parameters 3.1.2.2.0.4 PTF (2.2.0.4) - Update AFP Viewer 2.38A, enhanced N-UP support 3.1.2.2.0.5 PTF (2.2.0.5) - Added support for new EDMSuite Splash Screen - Added support for 'Show Search String' which allows for automatic text search when viewing data - Update AFP Viewer 2.39 3.1.2.2.0.6 PTF (2.2.0.6) 3.1.2.2.0.7 PTF (2.2.0.7) - Update AFP Viewer 2.40 3.1.2.2.0.8 PTF (2.2.0.8) - Update AFP Viewer 2.40A 3.1.2.2.0.9 PTF (2.2.0.9) - Update AFP Viewer 2.40B 3.1.2.2.0.10 PTF (2.2.0.10) - Added support for copy bitmap to clipboard for line data 3.1.2.2.0.11 PTF (2.2.0.11) - Update AFP Viewer 2.41 3.1.2.2.0.12 PTF (2.2.0.12) - Update AFP Viewer 2.42 - Update of Core Fonts to support Euro symbol. For those customers using customized fonts, this change updates the alias.fnt and csdef.fnt files. Therefore you must update these files after installation. 3.1.2.2.0.13 PTF (2.2.0.13) - Added support that always forces an AND operation when a field is defined as fixed with a default value. - Update AFP Viewer 2.44 - Update of Pixel Image Viewer 4.2 3.1.2.2.0.14 PTF (2.2.0.14) - Update AFP Viewer 2.45 --------------end of Windows 3.1 Client----------------------------------------- 3.2 OS/2 Client 3.2.2.2.0.0 Release (2.2.0.0) 3.2.2.2.0.1 PTF (2.2.0.1) - Added new DDE functions - Fixed a bug which caused the client to lock up if specifying an empty server name during login 3.2.2.2.0.2 PTF (2.2.0.2) - Fixed a bug which caused the client to stop operation when printing > 256 documents from hit list. - Fixed a bug which caused the client to not properly cleanup temporary files in DATA and RES directories. - Fixed a bug which caused the client to not display image data 3.2.2.2.0.3 PTF (2.2.0.3) - Added support for new/modified command line parameters 3.2.2.2.0.4 PTF (2.2.0.4) - Update AFP Viewer 2.15A, enhanced N-UP support 3.2.2.2.0.5 PTF (2.2.0.5) - Added support for new EDMSuite Splash Screen - Added support for 'Show Search String' which allows for automatic text search when viewing data - Update AFP Viewer 2.16 3.2.2.2.0.6 PTF (2.2.0.6) 3.2.2.2.0.7 PTF (2.2.0.7) - Fixed a bug which caused the client to not properly cleanup temporary files in DATA and RES directories. - Fixed a bug which caused a GPF when viewing N-UP documents - Update AFP Viewer 2.16B 3.2.2.2.0.8 PTF (2.2.0.8) - Update AFP Viewer 2.16C 3.2.2.2.0.9 PTF (2.2.0.9) - Update AFP Viewer 2.16D 3.2.2.2.0.10 PTF (2.2.0.10) - Fixed a bug which caused copying data to clipboard to not work 3.2.2.2.0.11 PTF (2.2.0.11) - Update AFP Viewer 3.2.2.2.0.12 PTF (2.2.0.12) - Added NLS translations for Danish, Finnish, and Swedish - Update AFP Viewer 2.16E 3.2.2.2.0.13 PTF (2.2.0.13) - Added support that always forces an AND operation when a field is defined as fixed with a default value. - Update AFP Viewer 2.18 3.2.2.2.0.14 PTF (2.2.0.14) - Fixed a bug which caused printing to process images when the set image option was set to none - Update AFP Viewer 2.19 --------------end of OS/2 Client------------------------------------------------ 3.3 Windows 32-bit Client 3.3.2.2.0.0 Release (2.2.0.0) 3.3.2.2.0.1 PTF (2.2.0.1) - Added new DDE functions - Added support for viewing LZW TIFF images - Pixel Translations - Fixed a bug which caused TIFF viewing to fail with message if data was invalid (missing byte on EOF) - Pixel Translations - Fixed a bug which caused an error -5016 when printing TIFF locally - Fixed a bug which caused LAN attached printers to not show up in print dialog when running under WinNT 4.0 - Fixed a bug which caused arssck32.dll to not be found using OLE - Fixed a bug which caused OLE to not be able to print to a LAN attached printer 3.3.2.2.0.2 PTF (2.2.0.2) - Added support for multiple instances of the client - Fixed a bug which caused the client to improperly print DBCS line data - Fixed a bug which caused the client to drop pels when displaying line data 3.3.2.2.0.3 PTF (2.2.0.3) - Added support for new/modified command line parameters 3.3.2.2.0.4 PTF (2.2.0.4) - Update AFP Viewer 2.38A, enhanced N-UP support - Fixed a bug which caused the client to utilize full CPU when searching or retrieving documents - Fixed a bug which caused the client to not show the icon for an external application definition 3.3.2.2.0.5 PTF (2.2.0.5) - Added support for new EDMSuite Splash Screen - Added support for 'Show Search String' which allows for automatic text search when viewing data - Fixed a bug which caused the client to GPF when printing to a color printer - Fixed a bug which caused the client to not save print setup changes - Fixed a bug which caused the client to show incorrect values in search criteria screen when switching between equal and between operators on a date field - Update AFP Viewer 2.39 3.3.2.2.0.6 PTF (2.2.0.6) 3.3.2.2.0.7 PTF (2.2.0.7) - Fixed a bug which caused the client to hang when copying text from document - Fixed a bug which caused the client to use the ini file for AFP documents instead of the registry - Update AFP Viewer 2.40 3.3.2.2.0.8 PTF (2.2.0.8) - Added support for unified logon for WinNT using NTLM - Update AFP Viewer 2.40A 3.3.2.2.0.9 PTF (2.2.0.9) - Fixed a bug which caused the client to not properly read the registry for external application definitions - Fixed a bug which caused an OLE scroll problem with certain pages - Update AFP Viewer 2.40B 3.3.2.2.0.10 PTF (2.2.0.10) - Fixed a bug which caused incorrect displaying of DBCS line data - Added MAPI support - Added support for copy bitmap to clipboard for line data 3.3.2.2.0.11 PTF (2.2.0.11) - Update AFP Viewer 1.41 3.3.2.2.0.12 PTF (2.2.0.12) - Fixed a bug under Win95 which causes local printing to print n*n copies of the document - Added NLS translations for Danish, Finnish, and Swedish - Added Adobe ATM 4.0 for Win95 and WinNT. In order for arssetup to properly transfer ATM, arssetup and the server must be at 2.2.0.12 or greater. - Added Shortcuts and Expression Find capabilities - Update AFP Viewer 1.42 (Fixes performance problem introduced in 2.2.0.8) - Update of Core Fonts to support Euro symbol. For those customers using customized fonts, this change updates the alias.fnt and csdef.fnt files. Therefore you must update these files after installation. 3.3.2.2.0.13 PTF (2.2.0.13) - Fixed a bug which caused a GPF during logon and server connection cannot be established - Fixed a bug which caused a GPF while printing to a LAN attached printer - Fixed a bug which caused an infinitely loop to occur while doing a find operation on a document - Fixed a bug which caused a PDF document window to be blank - Fixed a bug which during printing showed the default printer instead of the last printer selected - Fixed a bug which caused only 1/2 of a TIFF image to display - Fixed a bug which caused OLE to not update the scroll bar after calling GetDocCurrentPage - Added OLE functions for annotations - Added support for thumbnails, bookmarks, and group annotations - Added support that always forces an AND operation when a field is defined as fixed with a default value. - Update AFP Viewer 1.44 - Update of Pixel Image Viewer 4.2 3.3.2.2.0.14 PTF (2.2.0.14) - Added support for allowing the thumbnail windows to be docked - Added new OLE method GetAnnotationStatus - Update AFP Viewer 1.45 --------------end of Windows 32-bit Client-------------------------------------- 3.4 Windows 32-bit Administrator 3.4.2.2.0.0 Release (2.2.0.0) 3.4.2.2.0.1 PTF (2.2.0.1) - Miscellaneous focus and message fixes 3.4.2.2.0.2 PTF (2.2.0.2) - Added support for logins to multiple servers 3.4.2.2.0.3 PTF (2.2.0.3) - Fixed a bug which caused the admin to GPF when adding a floating trigger using the graphical indexer 3.4.2.2.0.4 PTF (2.2.0.4) - Fixed a bug which caused the bubble text to not be visible 3.4.2.2.0.5 PTF (2.2.0.5) - Added support for defining 32 fields, instead of 16, for both Folders and Application Groups 3.4.2.2.0.6 PTF (2.2.0.6) - Fixed a bug which caused integer fields to maintain old search operators of like and not like 3.4.2.2.0.7 PTF (2.2.0.7) - Added support for allowing the view info code page to be different from the ACIF CPGID - Fixed a bug which caused a GPF when exporting an Application Group with Applications that have different default printers 3.4.2.2.0.8 PTF (2.2.0.8) - Added support for unified logon for WinNT using NTLM - Added support for refresh list from view menu - Added support for allowing the view info to be different from the ACIF parameters - Fixed a bug which caused message logging values to not be retained during Application Group copy 3.4.2.2.0.9 PTF (2.2.0.9) - Added support for allowing DBCS characters to be entered 3.4.2.2.0.10 PTF (2.2.0.10) - Added support for more user friendly dialogs for system parameters, application group storage management - Added support for using first available uid/gid instead of using the last one used plus one. 3.4.2.2.0.11 PTF (2.2.0.11) - Fixed a bug which caused the NT printer list to not be displayed 3.4.2.2.0.12 PTF (2.2.0.12) - Added additional user-friendly dialogs 3.4.2.2.0.13 PTF (2.2.0.13) - Added support for specifying the number of pages to work with when using the graphical indexer report wizard on a large input file 3.4.2.2.0.14 PTF (2.2.0.14) - Added support for storing user, group, application, application group, folder, printer, storage set information as a system log document when adding or deleting - Added support for displaying the number of documents stored in an application group before deleting the application group - Fixed a bug which caused a GPF when accessing Storage Nodes --------------end of Windows 32-bit Administrator------------------------------- ------------------end of Client Change History---------------------------------- 4. Loading On-line Publications (AIX Only) -------------------------------------------------------------------------------- If you have installed the OnDemand publications, the following steps will guide you through loading them: 1) Create the OnDemand publications folder, application group, and application: /usr/lpp/ars/config/arssys.create -p or /usr/lpp/ars/bin/arssyscr -p 2) Modify the application group storage management parameters with the administrator interface. For example, assign the application group to a cache only storage set or to a storage set that copies files to optical storage. 3) Modify the application group database tablespace type to the appropriate setting (None, SMS, DMS). 4) Load the publications. File Name Form Number Publication ---------------------------------------------------------------- arsb0mst.afp S544-5463-00 Getting Started with the Administrator Interface for Windows NT and Windows 95 arsd0mst.afp S544-5489-00 Indexing Reference arsi1mst.afp G544-5280-01 Installation and Configuration Guide arsn0mst.afp S544-5469-00 Getting Started with the User Interface for Windows NT and Windows 95 arso1mst.afp S544-5278-01 OS/2 Client User's Guide arsp1mst.afp G544-5281-01 Introduction and Planning Guide arsr1mst.afp S544-5293-01 Administrator's Reference arsw1mst.afp S544-5275-01 Windows Client User's Guide Issue the following commands: cd /usr/lpp/ars/pubs/en_US /usr/lpp/ars/bin/ars_load -n -v -g 'OnDemand Publications' \ -u -p or /usr/lpp/ars/bin/arsload -n -v -g 'OnDemand Publications' \ -u -p NOTE: Replace with the name of an OnDemand user that has administrator authority for the application group. Replace with the password for the user. Replace with the name of the publication, for example, arsa0mst.afp. ------------------end of Loading Online Publications---------------------------- 5. Documentation Corrections -------------------------------------------------------------------------------- The latest revisions of the US English versions of the OnDemand manuals are available in PDF format on the IBM web site: http://www.software.ibm.com/data/ondemand/library.html 5.1 IBM EDMSuite OnDemand: Indexing Reference, S544-5489-04 5.1.1 Page 73. FORMDEF parameter. The form definition you ask ACIF to retrieve may be located inline in the file. To use an inline form definition you must do the following: o If you specify the FORMDEF parameter, the name of the inline form definition must match the name of the specified form definition, or you must specify FORMDEF=DUMMY. If the name specified for the FORMDEF parameter does not match the name of an inline form definition, ACIF looks for the form definition in the FDEFLIB search path. If you specify FORMDEF=DUMMY and there is no inline form definition, ACIF searches the FDEFLIB search path for a form definition named DUMMY. ACIF reports an error and stops if unable to locate the form definition. o If a form definition resource is included inline with the data, the file must be identified as containing carriage control characters (CC=YES). o If the length of the records in the form definition is less than or equal to the logical record length defined for the file, you can specify fixed length records for the record format: - In AIX, HP-UX, and Windows NT, specify FILEFORMAT=RECORD,n (where n is the logical record length defined for the file). - In MVS, specify record format FBA (fixed blocked with ANSI carriage control characters) or FBM (fixed blocked with machine carriage control characters). o If the length of the records in the form definition is greater than the logical record length defined for the file, you must specify variable length records: - In AIX, HP-UX, and Windows NT, specify FILEFORMAT=RECORD. The first two bytes of each record determine the record length. - In MVS, specify record format VBA (variable blocked with ANSI carriage control characters) or VBM (variable blocked with machine carriage control characters). 5.1.2 Page 88. PAGEDEF parameter. The page definition you ask ACIF to retrieve may be located inline in the file. To use an inline page definition you must do the following: o If you specify the PAGEDEF parameter, the name of the inline page definition must match the name of the specified page definition, or you must specify PAGEDEF=DUMMY. If the name specified for the PAGEDEF parameter does not match the name of an inline page definition, ACIF looks for the page definition in the PDEFLIB search path. If you specify PAGEDEF=DUMMY and there is no inline page definition, ACIF searches the PDEFLIB search path for a page definition named DUMMY. ACIF reports an error and stops if unable to locate the page definition. o If a page definition resource is included inline with the data, the file must be identified as containing carriage control characters (CC=YES). o If the length of the records in the page definition is less than or equal to the logical record length defined for the file, you can specify fixed length records for the record format: - In AIX, HP-UX, and Windows NT, specify FILEFORMAT=RECORD,n (where n is the logical record length defined for the file). - In MVS, specify record format FBA (fixed blocked with ANSI carriage control characters) or FBM (fixed blocked with machine carriage control characters). o If the length of the records in the page definition is greater than the logical record length defined for the file, you must specify variable length records for the record format: - In AIX, HP-UX, and Windows NT, specify FILEFORMAT=RECORD The first two bytes of each record determine the record length. - In MVS, specify record format VBA (variable blocked with ANSI carriage control characters) or VBM (variable blocked with machine carriage control characters). 5.1.3 Page 97. TRIGGER parameter options and values when running ACIF under Windows NT. When you define a TRIGGER parameter using structured field data, you must change the order of the length bytes in the trigger string value. The length bytes are bytes two and three of a structured field. Some instructions in the x86 architecture use the length bytes in the reverse of the order that they appear in the input data. ACIF automatically changes the order of the length bytes in all input structured fields before indexing the data. For example, in the input data, a structured field may appear as follows: 5A0010D3EEEE00... In the example, the hexadecimal value 0010 represents the length of the structured field (16 bytes following the 5A). To support the x86 architecture, after reading the input data into its storage, ACIF changes the order of the length bytes before indexing the data. The data would appear in ACIF storage as follows: 5A1000D3EEEE00... When defining a TRIGGER parameter using structured field data, the order of the length bytes in the trigger string value must be the same as the data in ACIF storage, not the original input data. For example: TRIGGER1=*,1,X'5A1000D3EEEE00...' Before writing the output data, ACIF restores the length bytes to their original locations. 5.1.4 Page 98. TRIGGER parameter examples when running ACIF under Windows NT. The following TRIGGER parameter shows how to specify structured field data. Because ACIF changes the order of the length bytes in all structured fields before indexing the data, you must make sure that the order of the length bytes in the trigger string value is the same as the data in ACIF storage. This example could be used to index mixed mode data, such as a line data report that contains NOP structured fields, allowing ACIF to logically segment the report into documents. TRIGGER1='*,1,X'5A1000D3EEEE0000000000000000000000',(TYPE=GROUP) 5.1.5 Page 141. Message 0425-463. Change the text of the message to: "The index specified by the GROUPNAME parameter was not defined or was invalid." Change the Explanation to: "The index specified by the groupname parameter was not defined or the index contained a field which was based on either a floating or a recordrange trigger. This is invalid." ----------- end of corrections to S544-5489-04 --------------------------------- 5.2 IBM EDMSuite OnDemand: Installation Guide for UNIX Servers, G544-5598-00 5.2.1 Page 25. Installing DB2 UDB. The minimum swap space for an HP-UX server with DB2 UDB Version 5.2 is 256 MB. Servers with 128 MB or more of physical RAM should set the swap space to two times the size of physical RAM. 5.2.2 Page 25. Installing DB2 UDB. The correct URL for the DB2 UDB service update is: ftp://service.software.ibm.com/ps/products/db2/fixes 5.2.3 Page 27. ADSM Configuration Notes, item 1. Add NOPREEMPT to the server options file. This parameter makes sure that mount requests are not preempted by other commands (except for the backup database command). 5.2.4 Page 45. DB2 and ADSM parameters. Changes the values of the parameters in the ars.cfg file to the values listed on page 45. 5.2.5 Page 46 - 46. ADSM parameters. Changes the values of the parameters in the ars.cfg file to the values listed on pages 45 and 46. 5.2.6 Page 62. OnDemand database backup. If you specify a variable block size you must also specify a buffer size in the backup command that is less than or equal to the maximum block size limit for the backup device being used. For maximum performance, you should set the buffer size to the maximum block size for the backup device. See the DB2 documentation for details. See also DB2 technical note JMER-3PFMYE and PMR 00711,370. 5.2.7 Page 87. Top of page. In the device class statement, change format=2600 to format=2600MB. 5.2.8 Page 103. Define the Device Class. In the device class statement, change format=2600 to format=2600MB. 5.2.9 Page 105. Configuring the client options. You must create the dsm.opt.db2 file. Use the sample client options provided. Store the file in the directory named by the ARS_DB2_ADSM_CONFIG parameter in the ars.cfg file (by default, the /usr/adsm directory). 5.2.10 Page 159. PDF indexer. The Acrobat software is distributed on the OnDemand product CD-ROM. The installation program is located in the \adobe\unix\acrobat3\ directory, where is AIX or HPUX. When prompted for the product serial number, use the serial number provided by IBM (listed in the README.TXT file found in the root directory of the product CD-ROM). You may install the Acrobat Distiller software on any OnDemand library or object server for which you hold a license. 5.2.11 Page 160. Setting up the Distiller daemon. To configure the Distiller daemon to delete input files from the IN directory rather than moving them to the OUT directory after successfully distilling a file, add the following parameter to the command you use to run the Distiller daemon: -srcdisp delete ---------- end of corrections to G544-5598-00 ---------------------------------- 5.3 IBM EDMSuite OnDemand: Administrator's Reference, S544-5293-07 5.3.1 Page 52. The OnDemand database. If you specify a variable block size you must also specify a buffer size in the backup command that is less than or equal to the maximum block size limit for the backup device being used. For maximum performance, you should set the buffer size to the maximum block size for the backup device. See the DB2 documentation for details. See also DB2 technical note JMER-3PFMYE and PMR 00711,370. 5.3.2 Page 96. OnDemand system logging facility. OnDemand servers now generate system log messages to help you track the number of users logged on the server. OnDemand writes message number 201 to the system log every 30 minutes. This message contains the current number of users logged on to the server. OnDemand writes message number 202 to the system log every time the number of concurrent users exceeds the previous maximum number of concurrent users. 5.3.3 Page 151. arsadmin command reference. The unload command function now includes the -Q parameter. The -Q parameter allows you to force the arsadmin command to unload the loadID named with the -L parameter, even if the loadID is not found in the system log. If you do not specify the -Q parameter, the arsadmin command fails if it cannot find the loadID in the system log. 5.3.4 Page 182. The arsdoc query command now includes the -D parameter. Specify the -D parameter to append the document handle information to the end of each output record. The document handle consists of the following ten values, in the order listed: document name offset length compressed object offset compressed object length annotation type compression type resource id primary node id secondary node id The values are separated by a delimiter. The default delimiter is the comma character. You can specify a different delimiter with the -e parameter. You cannot specify the -H, -n, or -N parameters when you specify the -D parameter. 5.3.5 Page 182. The arsdoc query command now includes the -I parameter. Specify the -I parameter to append the load ID to the end of each output record. The load ID is separated from the database field values by a delimiter. The default delimiter is the comma character. You can specify a different delimiter with the -e parameter. You cannot specify the -H, -n, or -N parameters when you specify the -I parameter. NOTE: The load ID for a document is determined by searching the system log. This can be very time consuming, depending on the number of records stored in the system log. The system log is searched for each document that matches the query. To use the -I parameter, the user running the query must have permission to access the system log application group and folder. If the load ID is not found in the system log, the string "Load Id could not be found" is appended to the end of the output record. 5.3.6 Page 199. arsjesd command reference Notes. Depending on the date format you specify to Download, the date portion of the filename can be YYDDD or YYYYDDD. Apply APAR OW36539 to Download and use the DATE_FORMAT=YYYY keyword in the routing file to control the format of the date placed in the filename. 5.3.7 Page 201. arsload command reference. The arsload command now includes the -X parameter. The -X parameter allows you to override the type of indexer defined in the application. Possible values are: -X G specifies to use the OnDemand Generic indexer -X A specifies to use the OnDemand ACIF indexer You must override the default indexer if you create index data in a format other than that supported by the indexer defined in the application. For example, you define an application and specify ACIF as the indexer. Later, you use the arsdocget command to extract documents from an application group. The arsdocget command generates index data in the Generic index format. To load the index data into the application, you must specify: arsload -X G ---------- end of corrections to S544-5293-07 ---------------------------------- 5.4 IBM EDMSuite OnDemand: Installation Guide for Windows NT Servers, G544-5526-05 5.4.1 Page 34. Verify Server and Client Options, second paragraph. Add NOPREEMPT to the server options file. This parameter makes sure that mount requests cannot be preempted by other commands (except for the backup database command). 5.4.2 Page 39. Item 3. In the device class statement, change format=2600 to format=2600MB. 5.4.3 Page 63. Configuring scheduled tasks, OnDemand database backup. If you specify a variable block size you must also specify a buffer size in the backup command that is less than or equal to the maximum block size limit for the backup device being used. For maximum performance, you should set the buffer size to the maximum block size for the backup device. See the DB2 documentation for details. See also DB2 technical note JMER-3PFMYE and PMR 00711,370. 5.4.4 Page 111. PDF indexer. The Acrobat software is distributed on the OnDemand product CD-ROM. Use the setup.exe program to install the software. The setup program is located in the \adobe\win\acrobat3 directory. When prompted for the product serial number, use the serial number provided by IBM (listed in the README.TXT file found in the root directory of the product CD-ROM). You may install the Acrobat Distiller software on any OnDemand library or object server for which you hold a license. 5.4.5 Page 112. Item 5 (Configuring Acrobat distilling software). To configure the Distiller to delete input files from the IN directory rather than moving them to the OUT directory after successfully distilling a file, open the Watched Folders dialog box and select "After Distilling, the PostScript file should be: Deleted". ---------- end of corrections to G544-5526-05 ---------------------------------- ----------------- end of Documentation Corrections ----------------------------- 6. Urgent Problems -------------------------------------------------------------------------------- 6.1 (October 8, 1998) Unexpected expiration of database indexes Problem: When you define an application group, you specify the type of tablespaces used to store application group index data. You can specify DMS, SMS, or NONE. If you specify DMS and SMS tablespaces for some application groups and NONE for other application groups, unexpected expiration of index data may occur for the application groups with no tablespace support (NONE). Versions Effected: OnDemand for AIX Server - Version 2.1.1.2 thru 2.2.0.11 OnDemand for WinNT Server - Version 2.2.0.5 thru 2.2.0.11 Solution: 1) Upgrade to OnDemand AIX/WinNT Version 2.2.0.12 or later. IMPORTANT: If you are unable to upgrade your system, do not expire application group index data (with the arsmaint -d command). You should not expire application group index data until after you upgrade to OnDemand 2.2.0.12 or later. 2) Changes made in OnDemand 2.2.0.12: a) For application groups with no tablespace support (NONE), OnDemand now creates all application group tables in the USERSPACE1 tablespace. b) For application groups that specify DMS or SMS tablespace support, OnDemand now makes sure that before dropping a tablespace, there is only one table in the tablespace. Otherwise, OnDemand drops only the table and not the tablespace, to avoid dropping unrelated tables. Background: In versions prior to OnDemand 2.2.0.12: 1) When creating a table for an application group that used DMS or SMS tablespaces, OnDemand first created a tablespace and then created a table within the tablespace. When expiring database indexes, OnDemand dropped the tablespace, which automatically dropped all tables in the tablespace. 2) When creating a table for an application group that did not use tablespace support (NONE), OnDemand created the table without specifying a tablespace. The table could be created in any tablespace, including DMS and SMS tablespaces. When expiring database indexes in DMS and SMS tablespaces, OnDemand could have dropped tables that belonged to non-DMS and non-SMS application groups. Problem Determination: 1) To determine whether the problem exists on your system, run the following DB2 commands. The commands will list the application groups and tables that could be effected. NOTE: Even if the commands list no application groups or tables, there is no guarantee that your system cannot be effected in the future unless you upgrade to OnDemand 2.2.0.12. db2 CONNECT TO archive db2 "SELECT root.arsag.name, root.arsseg.table_name \ FROM root.arsag, root.arsseg, syscat.tables \ WHERE syscat.tables.tbspace <> CONCAT('ROOT_',syscat.tables.tabname) \ AND syscat.tables.tbspace LIKE 'ROOT%' \ AND root.arsseg.table_name = syscat.tables.tabname \ AND root.arsseg.agid = root.arsag.agid ORDER BY root.arsag.name" db2 TERMINATE 6.2 (February 3, 1999) Unexpected expiration of resources from ADSM Problem: When resources are stored for AFP documents, a check is made to determine whether or not the resource already exists. If it does not exist, the resource is stored into cache and/or ADSM. However if the resource already exists, then the resource is not re-loaded. Since ADSM expires resources based on when they were initially loaded, it is possible for resources to expire before the list of documents that reference them have expired. Versions Effected: OnDemand for AIX Server - Version 2.1.0.0 thru 2.2.0.13 OnDemand for WinNT Server - Version 2.2.0.5 thru 2.2.0.13 OnDemand for HP-UX Server - Version 2.2.0.12 thru 2.2.0.13 Solution: 1) Upgrade to OnDemand Version 2.2.0.14 or later. 2) Changes made in OnDemand 2.2.0.14: If during a load, OnDemand determines that a resource already exists, the resource is automatically reloaded into ADSM. Doing so guarantees that the resource will not expire from ADSM until the last load that references the resource also expires. ------------------end of Urgent Problems---------------------------------------- 7. Pre-req changes -------------------------------------------------------------------------------- 7.1 (February 3, 1999) OnDemand for WinNT (PTF 2.2.0.14 or greater) - Requires ADSM Client API Version 3.1.0.6 OnDemand for HP-UX (PTF 2.2.0.14 or greater) - Requires ADSM Client API Version 3.1.0.6 ------------------end of Pre-req changes----------------------------------------