################################################################################ # IBM Content Manager OnDemand # # AIX, HP-UX, Solaris, Windows NT (server/client) # # OS/400 (clients only) # # README # # Release 2.2.1.8 # # July 28, 2000 # # # # 5622-662, 5765-D60, 5765-E20, 5639-E12 (C) COPYRIGHT IBM CORPORATION 2000 # # 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 publications were printed. Please make note of these items, which supersede the information contained in the OnDemand publications. ================================================================================ The IBM ADSTAR Distributed Storage Manager (ADSM) product and its features are now part of the Tivoli Storage Management product set. ADSM is now known as Tivoli Storage Manager (TSM). The TSM base product includes some functions that were purchased features for ADSM. For the latest information about TSM products, see http://www.tivoli.com/tsm. We recommend that you install TSM V3.7 on your object servers. OnDemand now supports DB2 UDB V6.1. For the latest information about DB2, see http://www.software/ibm/com/data. For the latest DB2 product updates, see ftp://service.software.ibm.com/ps/products/db2. The OnDemand server products are "Tivoli Ready". The ODTIVOLI.TXT file in the server installation directory provides more information. For details about Tivoli Ready enablement, see http://www.ibm.com/software/tivoli-ready. OnDemand now supports Oracle 8i (8.1.5.0). See section 7 for more information. ================================================================================ 1. Contents 2. Server Change History 2.1 AIX Server 2.1.2.2.1.0 Release/PTF (2.2.1.0) 2.1.2.2.1.1 PTF (2.2.1.1) 2.1.2.2.1.2 PTF (2.2.1.2) 2.1.2.2.1.3 PTF (2.2.1.3) 2.1.2.2.1.4 PTF (2.2.1.4) 2.1.2.2.1.5 PTF (2.2.1.5) 2.1.2.2.1.6 PTF (2.2.1.6) 2.1.2.2.1.7 PTF (2.2.1.7) 2.1.2.2.1.8 PTF (2.2.1.8) 2.2 HP-UX Server 2.2.2.2.1.0 Release/PTF (2.2.1.0) 2.2.2.2.1.1 PTF (2.2.1.1) 2.2.2.2.1.2 PTF (2.2.1.2) 2.2.2.2.1.3 PTF (2.2.1.3) 2.2.2.2.1.4 PTF (2.2.1.4) 2.2.2.2.1.5 PTF (2.2.1.5) 2.2.2.2.1.6 PTF (2.2.1.6) 2.2.2.2.1.7 PTF (2.2.1.7) 2.2.2.2.1.8 PTF (2.2.1.8) 2.3 Solaris Server 2.3.2.2.1.0 Release (2.2.1.0) 2.3.2.2.1.1 PTF (2.2.1.1) 2.3.2.2.1.2 PTF (2.2.1.2) 2.3.2.2.1.3 PTF (2.2.1.3) 2.3.2.2.1.4 PTF (2.2.1.4) 2.3.2.2.1.5 PTF (2.2.1.5) 2.3.2.2.1.6 PTF (2.2.1.6) 2.3.2.2.1.7 PTF (2.2.1.7) 2.3.2.2.1.8 PTF (2.2.1.8) 2.4 Windows NT Server 2.4.2.2.1.0 Release/PTF (2.2.1.0) 2.4.2.2.1.1 PTF (2.2.1.1) 2.4.2.2.1.2 PTF (2.2.1.2) 2.4.2.2.1.3 PTF (2.2.1.3) 2.4.2.2.1.4 PTF (2.2.1.4) 2.4.2.2.1.5 PTF (2.2.1.5) 2.4.2.2.1.6 PTF (2.2.1.6) 2.4.2.2.1.7 PTF (2.2.1.7) 2.4.2.2.1.8 PTF (2.2.1.8) 3. Client Change History 3.1 OS/2 Client 3.1.2.2.1.0 Release/PTF (2.2.1.0) 3.1.2.2.1.1 PTF (2.2.1.1) 3.1.2.2.1.2 PTF (2.2.1.2) 3.1.2.2.1.3 PTF (2.2.1.3) 3.1.2.2.1.5 PTF (2.2.1.5) 3.1.2.2.1.6 PTF (2.2.1.6) 3.2 Windows 3.1 Client 3.2.2.2.1.0 Release/PTF (2.2.1.0) 3.2.2.2.1.1 PTF (2.2.1.1) 3.2.2.2.1.2 PTF (2.2.1.2) 3.2.2.2.1.3 PTF (2.2.1.3) 3.3 Windows 32-bit Client 3.3.2.2.1.0 Release/PTF (2.2.1.0) 3.3.2.2.1.1 PTF (2.2.1.1) 3.3.2.2.1.2 PTF (2.2.1.2) 3.3.2.2.1.3 PTF (2.2.1.3) 3.3.2.2.1.4 PTF (2.2.1.4) 3.3.2.2.1.5 PTF (2.2.1.5) 3.3.2.2.1.6 PTF (2.2.1.6) 3.3.2.2.1.7 PTF (2.2.1.7) 3.3.2.2.1.8 PTF (2.2.1.8) 3.4 Windows 32-bit Administrator 3.4.2.2.1.0 Release/PTF (2.2.1.0) 3.4.2.2.1.1 PTF (2.2.1.1) 3.4.2.2.1.2 PTF (2.2.1.2) 3.4.2.2.1.3 PTF (2.2.1.3) 3.4.2.2.1.4 PTF (2.2.1.4) 3.4.2.2.1.5 PTF (2.2.1.5) 3.4.2.2.1.6 PTF (2.2.1.6) 3.4.2.2.1.7 PTF (2.2.1.7) 3.4.2.2.1.8 PTF (2.2.1.8) 4. Upgrade Instructions for 2.2.1.0 5. Client/Server Backward Compatibility 6. Documentation Corrections 7. Oracle Instructions ------------------end of Contents----------------------------------------------- 2. Server Change History -------------------------------------------------------------------------------- 2.1 AIX Server 2.1.2.2.1.0 Release/PTF (2.2.1.0) - Pre-reqs - AIX 4.2.1 or later - DB2 UDB 5.2 or later - ADSM 3.1.0.6 or later 2.1.2.2.1.1 PTF (2.2.1.1) - Added additional generic index file format support (See below for additional details) - Added option to arsview (-x) to not display horizontal/vertical lines - Added option to arsview (-y) to use character space reset algorithm - Added support to arsmaint to ignore the lost+found directory - Fixed a bug which caused arsload to not return a 0 return code - Fixed a bug which caused PDF indexing to fail because of "word search or extraction error" 2.1.2.2.1.2 PTF (2.2.1.2) - Added support to arsdoc which allows the specific of an application group for all functions (-G parameter) - Fixed a bug which caused arsdb to not allow multiple backup devices - Fixed a bug which caused arsdate to fail when displaying values 2.1.2.2.1.3 PTF (2.2.1.3) - Added support to arsload to delete the .ARD file when using the generic index file format - Fixed a bug which caused arsacif to not collect inline resources - Fixed a performance problem with arsacif that was introduced in version 2.2.0.13 - Fixed a bug which caused arsadm user to not delete a user when the user is specified in lower case - Fixed a bug which caused the loading of the generic index file format to not accept CRLF - Fixed a bug which caused arsjesd to not invoke the -x when multiple -d directories are installed 2.1.2.2.1.4 PTF (2.2.1.4) - Added support to arsacif for allowing up to 2 characters when FILEFORMAT=STREAM 2.1.2.2.1.5 PTF (2.2.1.5) - Added support for Tivoli Ready - Added support for FaxPlus/Open for server-based FAX - Fixed a bug which caused arsacif to add a x'00' character to the output file when the record length for a line was zero and CONVERT=NO - Fixed a bug which caused arsload to use the -c option to find the index file instead of -d - Fixed a bug which caused arssockd to exit when receiving the unexpected errno=76 - Fixed a bug which caused arssockd to not properly release memory when doing server based text search on AFP and line data documents - Fixed a bug which caused an incorrect message 32 (Logoff) instead of message 33 (Logoff Timeout) when encountering a logoff which timed out - Fixed a bug which caused arssyscr to return a non-zero return code when successful 2.1.2.2.1.6 PTF (2.2.1.6) - Added support for Oracle database (see section 7) - Added support for logging more field information during document add, update and delete - Fixed a bug which caused table segments to not be dropped when the table segment has no more data - Fixed a bug which caused arsload to return a zero return code when no rows are loaded - Fixed a bug which caused the PDF indexer to add extra space characters when dealing with a rotated document - Fixed a bug which caused group ids to not be removed from folder and application group definitions when the group was deleted - Fixed a bug which caused all applications to be removed from all folders when a folder was deleted. This occurred when the folder being deleted contained only specific applications within the application group. - Fixed a bug which caused server based text search to fail when data resides on object server - Fixed a bug which caused arsacif to dump core with transaction data 2.1.2.2.1.7 PTF (2.2.1.7) - Fixed a bug which caused the unloading process to not generate the message number 84 (Unload of database) - Fixed a bug which caused arsdb to drop core when displaying messages when starting the database 2.1.2.2.1.8 PTF (2.2.1.8) - Added support for Arabic - Added support for Oracle table spaces - Modify code to only get client hostname when logging to System Log --------------end of AIX Server------------------------------------------------- 2.2 HP-UX Server 2.2.2.2.1.0 Release/PTF (2.2.1.0) - Pre-reqs - DB2 UDB 5.2 or later - ADSM 3.1.0.6 or later 2.2.2.2.1.1 PTF (2.2.1.1) - Added additional generic index file format support (See below for additional details) - Added option to arsview (-x) to not display horizontal/vertical lines - Added option to arsview (-y) to use character space reset algorithm - Added support to arsmaint to ignore the lost+found directory - Fixed a bug which caused arsload to not return a 0 return code - Fixed a bug which caused PDF indexing to fail because of "word search or extraction error" 2.2.2.2.1.2 PTF (2.2.1.2) - Added support to arsdoc which allows the specific of an application group for all functions (-G parameter) - Fixed a bug which caused arsdb to not allow multiple backup devices - Fixed a bug which caused arsdate to fail when displaying values - Fixed a bug which caused server based text search to fail 2.2.2.2.1.3 PTF (2.2.1.3) - Added support to arsload to delete the .ARD file when using the generic index file format - Fixed a bug which caused arsacif to not collect inline resources - Fixed a bug which caused arsadm user to not delete a user when the user is specified in lower case - Fixed a bug which caused the loading of the generic index file format to not accept CRLF - Fixed a bug which caused arsjesd to not invoke the -x when multiple -d directories are installed 2.2.2.2.1.4 PTF (2.2.1.4) - Added support to arsacif for allowing up to 2 characters when FILEFORMAT=STREAM 2.2.2.2.1.5 PTF (2.2.1.5) - Pre-reqs - HP-UX 11.0 (we no longer support HP-UX version 10.20) - Added support for Tivoli Ready - Fixed a bug which caused arsacif to add a x'00' character to the output file when the record length for a line was zero and CONVERT=NO - Fixed a bug which caused arsload to use the -c option to find the index file instead of -d - Fixed a bug which caused arssockd to not properly release memory when doing server based text search on AFP and line data documents - Fixed a bug which caused an incorrect message 32 (Logoff) instead of message 33 (Logoff Timeout) when encountering a logoff which timed out - Fixed a bug which caused arssyscr to return a non-zero return code when successful 2.2.2.2.1.6 PTF (2.2.1.6) - Added support for Oracle database (see section 7) - Added support for logging more field information during document add, update and delete - Fixed a bug which caused table segments to not be dropped when the table segment has no more data - Fixed a bug which caused arsload to return a zero return code when no rows are loaded - Fixed a bug which caused the PDF indexer to add extra space characters when dealing with a rotated document - Fixed a bug which caused group ids to not be removed from folder and application group definitions when the group is deleted - Fixed a bug which caused all applications to be removed from all folders when a folder was deleted. This occurred when the folder being deleted contained only specific applications within the application group. - Fixed a bug which caused server based text search to fail when data resides on object server 2.2.2.2.1.7 PTF (2.2.1.7) - Fixed a bug which caused the unloading process to not generate the message number 84 (Unload of database) - Fixed a bug which caused arsdb to drop core when displaying messages when starting the database 2.2.2.2.1.8 PTF (2.2.1.8) - Added support for Arabic - Added support for Oracle table spaces - Modify code to only get client hostname when logging to System Log --------------end of HP-UX Server----------------------------------------------- 2.3 Solaris Server 2.3.2.2.1.0 Release (2.2.1.0) - Pre-reqs - DB2 UDB 5.2 or later - ADSM 3.1.0.6 or later 2.3.2.2.1.1 PTF (2.2.1.1) - Added additional generic index file format support (See below for additional details) - Added option to arsview (-x) to not display horizontal/vertical lines - Added option to arsview (-y) to use character space reset algorithm - Added support to arsmaint to ignore the lost+found directory - Fixed a bug which caused arsload to not return a 0 return code - Fixed a bug which caused PDF indexing to fail because of "word search or extraction error" 2.3.2.2.1.2 PTF (2.2.1.2) - Added support to arsdoc which allows the specific of an application group for all functions (-G parameter) - Fixed a bug which caused arsdb to not allow multiple backup devices - Fixed a bug which caused arsdate to fail when displaying values 2.3.2.2.1.3 PTF (2.2.1.3) - Added support to arsload to delete the .ARD file when using the generic index file format - Fixed a bug which caused arsacif to not collect inline resources - Fixed a bug which caused arsadm user to not delete a user when the user is specified in lower case - Fixed a bug which caused the loading of the generic index file format to not accept CRLF - Fixed a bug which caused arsjesd to not invoke the -x when multiple -d directories are installed 2.3.2.2.1.4 PTF (2.2.1.4) - Added support to arsacif for allowing up to 2 characters when FILEFORMAT=STREAM - Fixed a bug which caused arsacif to drop core 2.3.2.2.1.5 PTF (2.2.1.5) - Added support for Tivoli Ready - Fixed a bug which caused arsacif to add a x'00' character to the output file when the record length for a line was zero and CONVERT=NO - Fixed a bug which caused arsload to use the -c option to find the index file instead of -d - Fixed a bug which caused arsload to fail with invalid structured field when loading large files - Fixed a bug which caused arssockd to not properly release memory when doing server based text search on AFP and line data documents - Fixed a bug which caused an incorrect message 32 (Logoff) instead of message 33 (Logoff Timeout) when encountering a logoff which timed out - Fixed a bug which caused arssyscr to return a non-zero return code when successful 2.3.2.2.1.6 PTF (2.2.1.6) - Added support for Oracle database (see section 7) - Added support for logging more field information during document add, update and delete - Fixed a bug which caused table segments to not be dropped when the table segment has no more data - Fixed a bug which caused arsload to return a zero return code when no rows are loaded - Fixed a bug which caused the PDF indexer to add extra space characters when dealing with a rotated document - Fixed a bug which caused group ids to not be removed from folder and application group definitions when the group is deleted - Fixed a bug which caused all applications to be removed from all folders when a folder is deleted. This occurred when the folder being deleted contained only specific applications within the application group. - Fixed a bug which caused server based text search to fail when data resides on object server 2.3.2.2.1.7 PTF (2.2.1.7) - Fixed a bug which caused the unloading process to not generate the message number 84 (Unload of database) - Fixed a bug which caused arsdb to drop core when displaying messages when starting the database 2.3.2.2.1.8 PTF (2.2.1.8) - Added support for Oracle table spaces - Modify code to only get client hostname when logging to System Log --------------end of Solaris Server-------------------------------------------- 2.4 Windows NT Server 2.4.2.2.1.0 Release/PTF (2.2.1.0) - Pre-reqs - DB2 UDB 5.2 or later - ADSM 3.1.0.6 or later - Due to possible installation problems when installing 2.2.1.0 on top of 2.2.0.5 (the initial release of OD/NT), it is recommended that you install 2.2.0.15 on top of 2.2.0.5, and then install 2.2.1.0 2.4.2.2.1.1 PTF (2.2.1.1) - Added additional generic index file format support (See below for additional details) - Added option to arsview (-x) to not display horizontal/vertical lines - Added option to arsview (-y) to use character space reset algorithm - Fixed a bug which caused arsload to not return a 0 return code - Fixed a bug which caused PDF indexing to fail because of "word search or extraction error" - Fixed a bug which caused the configurator to use wrong name for the load data service 2.4.2.2.1.2 PTF (2.2.1.2) - Added support to arsdoc which allows the specific of an application group for all functions (-G parameter) - Fixed a bug which caused arsview to output multiple CR per LF - Fixed a bug which caused arsdb to not allow multiple backup devices - Fixed a bug which caused arsdate to fail when displaying values 2.4.2.2.1.3 PTF (2.2.1.3) - Added support to arsload to delete the .ARD file when using the generic index file format - Added support for Microsoft SQL Server 7.0 - Fixed a bug which caused arsacif to not collect inline resources - Fixed a bug which caused arsacif to GPF during indexing - Fixed a bug which caused arssockd to hang in a high usage environment - Fixed a bug which caused arsadm user to not delete a user when the user is specified in lower case - Fixed a bug which caused the loading of the generic index file format to not accept CRLF - Fixed a bug which caused arsjesd to not invoke the -x when multiple -d directories are installed - Fixed a bug which caused arsview to incorrectly output extra CRLF characters 2.4.2.2.1.4 PTF (2.2.1.4) - Added support to arsacif for allowing up to 2 characters when FILEFORMAT=STREAM - Fixed a bug which caused arsacif to GPF 2.4.2.2.1.5 PTF (2.2.1.5) - Added support for Tivoli Ready - Fixed a bug which caused arsacif to add a x'00' character to the output file when the record length for a line was zero and CONVERT=NO - Fixed a bug in which viewable messages in the System Log did not get stored - Fixed a bug which caused arsload to use the -c option to find the index file instead of -d - Fixed a bug which caused arsmaint -c to not properly delete empty directories - Fixed a bug which caused arssockd to not properly release memory when doing server based text search on AFP and line data documents - Fixed a bug which caused an incorrect message 32 (Logoff) instead of message 33 (Logoff Timeout) when encountering a logoff which timed out - Fixed a bug which caused arssyscr to return a non-zero return code when successful - Fixed a bug which caused arsdb to fail when creating an MSSQL Server database because of being unable to set the language - Fixed a bug which caused loading to fail with DBCS characters 2.4.2.2.1.6 PTF (2.2.1.6) - Added support for Oracle database (see section 7) - Added support for logging more field information during document add, update and delete - Fixed a bug which caused table segments to not be dropped when the table segment has no more data - Fixed a bug which caused arsload to return a zero return code when no rows are loaded - Fixed a bug which caused the PDF indexer to add extra space characters when dealing with a rotated document - Fixed a bug which caused group ids to not be removed from folder and application group definitions when the group is deleted - Fixed a bug which caused all applications to be removed from all folders when a folder is deleted. This occurred when the folder being deleted contained only specific applications within the application group. - Fixed a bug which caused server based text search to fail when data resides on object server 2.4.2.2.1.7 PTF (2.2.1.7) - Fixed a bug which caused the unloading process to not generate the message number 84 (Unload of database) - Fixed a bug which caused arsdb to GPF when displaying messages when starting the database 2.4.2.2.1.8 PTF (2.2.1.8) - Added support for Arabic - Added support for Oracle table spaces - Modify code to only get client hostname when logging to System Log --------------end of Windows NT Server------------------------------------------ ------------------end of Server Change History---------------------------------- 3. Client Change History 3.1 OS/2 Client 3.1.2.2.1.0 Release/PTF (2.2.1.0) 3.1.2.2.1.1 PTF (2.2.1.1) - Added support for viewing line data utilizing iconv - Update AFP Viewer 2.22 - Fixed a bug which caused client to crash when viewing documents in auto cascade/tile mode 3.1.2.2.1.2 PTF (2.2.1.2) - Update AFP Viewer 2.23 3.1.2.2.1.3 PTF (2.2.1.3) - Update AFP Viewer 2.24 3.1.2.2.1.5 PTF (2.2.1.5) - Update AFP Viewer 2.25 - Fixed a bug which caused the client to GPF when encountering an error converting line data between different code pages in order to view the document 3.1.2.2.1.6 PTF (2.2.1.6) --------------end of OS/2 Client------------------------------------------------ 3.2 Windows 3.1 Client 3.2.2.2.1.0 Release/PTF (2.2.1.0) 3.2.2.2.1.1 PTF (2.2.1.1) - Update AFP Viewer 2.48 3.2.2.2.1.2 PTF (2.2.1.2) - Update AFP Viewer 2.49 3.2.2.2.1.3 PTF (2.2.1.3) - Update AFP Viewer 2.50 --------------end of Windows 3.1 Client----------------------------------------- 3.3 Windows 32-bit Client 3.3.2.2.1.0 Release/PTF (2.2.1.0) 3.3.2.2.1.1 PTF (2.2.1.1) - Added support for PDF thumbnails - Update AFP Viewer 1.48 - Fixed a bug which caused the client to not use unified login after a timeout - Fixed a bug which caused the client hang when the view title string was greater than 200 characters - Fixed a bug which caused the client to not properly display PDF documents using the rotation definition 3.3.2.2.1.2 PTF (2.2.1.2) - Update AFP Viewer 1.49 - Updated all national languages to match function available in US/English client - Fixed a bug which caused the client to not properly store print properties under Win95 - Fixed a bug which caused the client to hang if the last character in a line data document is 0x8B - Fixed a bug which caused images to not rotate properly - Fixed a bug which caused copy document pages to file for line data to omit form feed characters 3.3.2.2.1.3 PTF (2.2.1.3) - Added support for including the Monarch integration with the client installation. (Prior to 2.2.1.3., Monarch integration was a separate installation.) - Update AFP Viewer 1.50 - Fixed a bug which caused the client to not work with UNC names - Fixed a bug which caused the client to not retain orientation during local printing 3.3.2.2.1.4 PTF (2.2.1.4) - Added support for the Print and Go To commands as shortcuts - Added support for highlighting the most recent line in Find All - Fixed a bug which caused the client to fail when doing server-based text search against a local server - Fixed a bug which caused the client to print the number of pages instead of the number of copies specified when printing PDF from the hit list 3.3.2.2.1.5 PTF (2.2.1.5) - Added support for multiple monitor (Win2000) - Added AFP support for BIDI languages (Arabic and Hebrew) - Update AFP Viewer 1.51 - Fixed a bug which caused the OLE store doc command to GPF when dealing with big integers (64bit) - Fixed a bug which caused the client to GPF when viewing AFP data with a certain page segment - Fixed a bug which caused the client to ignore an AFP orientation triplet and therefore display the data improperly - Fixed a bug which caused the client to display the same AFP line twice when the line followed a no-op structured field 3.3.2.2.1.6 PTF (2.2.1.6) - Added support to be able to set image intensity for OLE - Added support to be able to cancel during folder search and document retrieval when using OLE - Fixed a bug which caused the client to improperly display Traditional Chinese characters - Fixed a bug which caused the client to fail doing a server print from the hit list because of unified login - Fixed a bug which caused the copy document pages to file to lose formatting when dealing with large object documents - Fixed a bug which caused the client to fail when invoking an external application because of a space in the file name - Fixed a bug which caused the line data viewer to not properly handle machine carriage controls - Fixed a bug which caused expression find to not work properly with null values in the data - Fixed a bug which caused the install process to not properly assign the execution directory during compact install - Fixed a bug which caused the install process to not properly register the OLE control 3.3.2.2.1.7 PTF (2.2.1.7) - Added support for different ways to handle overstrike carriage controls in line data - Fixed a bug which caused printing of notes to be poor for data types other than line data 3.3.2.2.1.8 PTF (2.2.1.8) - Added support for Arabic - Update AFP Viewer 1.52 - Fixed a bug which caused the Norwegian text 'Send' to be truncated - Fixed a bug which incorrect copy results when scrolling right with logical view - Fixed a bug which caused notes to not print correctly with image data --------------end of Windows 32-bit Client-------------------------------------- 3.4 Windows 32-bit Administrator 3.4.2.2.1.0 Release/PTF (2.2.1.0) 3.4.2.2.1.1 PTF (2.2.1.1) - Fixed a bug which caused the graphical indexer to hang when trigger not found on next page - Fixed a bug which caused the graphical indexer to not allow more than 3 characters for the code page 3.4.2.2.1.2 PTF (2.2.1.2) - Added Japanese translation 3.4.2.2.1.3 PTF (2.2.1.3) - Fixed a bug which caused the administrator to GPF when updating a folder 3.4.2.2.1.4 PTF (2.2.1.4) - Added support for allowing up to 2 characters for ACIF when FILEFORMAT=STREAM 3.4.2.2.1.5 PTF (2.2.1.5) - Fixed a bug which caused the admin client to allow modification of page size for line data instead of forcing a single option 3.4.2.2.1.6 PTF (2.2.1.6) - Fixed a bug which caused the line data viewer to not properly handle machine carriage controls 3.4.2.2.1.7 PTF (2.2.1.7) - Fixed a bug which didn't allow printers to be added - Fixed a bug which caused the administrator to GPF when updating groups 3.4.2.2.1.8 PTF (2.2.1.8) - Added support for Arabic - Added support for defining table spaces when server uses Oracle --------------end of Windows 32-bit Administrator------------------------------- ------------------end of Client Change History---------------------------------- 4. Upgrade Instructions for 2.2.1.0 -------------------------------------------------------------------------------- NOTE: Please see Section 5, Client/Server Backward Compatibility NOTE: OnDemand Version 2.2.1.0 requires DB2 UDB V5.2 or later with the latest FixPak. If you plan to use ADSM to maintain data on archive media, OnDemand V2.2.1.0 requires ADSM V3.1 or later, including the ADSM API V3.1.0.6 or later. OnDemand Version 2.2.1.0 adds the following enhancements: - Support for loading files up to 4 GB in size. (Previous limitation was 2 GB. PDF Indexer continues to support files up to 2 GB.) - Support for 64-bit integers as a data type. To support the 64-bit integer data type, all clients and service offerings must be at version 2.2.1.0 or later. At this time, the following clients and service offerings do not support the 64-bit integer data type: - All clients older than version 2.2.1.0 - Windows 3.1 Client - CICS Client (Service Offering) - Ad-Hoc Data Distribution (16-bit and 32-bit) (Service Offering) - Production Data Distribution (Service Offering) - Distributed User/Group Management - Distributed Server Print Management - New commands (AIX only): - arsdb replaces ars_db - arsload replaces ars_load - arsdocget replaced by arsdoc - arsquery replaced by arsdoc - arsuser replaced by arsadm - arsgroup replaced by arsadm - New packaging of client and server installation. OS/2, Win16, Win32 clients are provided as separate zip files and are no longer shipped as server-based install images. The enhancements require changes to the OnDemand system tables. Therefore, the following instructions must be completed if you are upgrading to version 2.2.1.0 from a previous version of OnDemand. If you have already installed version 2.2.1.0, you do not have to complete these steps. If you are installing OnDemand for the first time (version 2.2.1.0), you do not need to complete these steps. We recommend that you log all of the following steps. For example, in UNIX, use the script command. - (WinNT) Due to possible installation problems when installing 2.2.1.0 on top of 2.2.0.5 (the initial release of OD/NT), it is recommended that you install 2.2.0.15 on top of 2.2.0.5, and then install 2.2.1.0 1) Make sure that your server has the appropriate pre-reqs. 2) Back up your system (ADSM, DB2, OnDemand). For UNIX installs, the ars.cfg, ars.ini, ars.cache, and ars.dbfs files will be replaced. Make sure that you back up these files so that you can merge the information in them into the new versions of the files installed by 2.2.1.0 (see step 4). NOTE: Many customers have their own way of starting and running OnDemand. If you have custom commands or scripts, make sure that you back them up before you continue. 3) Install OnDemand Version 2.2.1.0 NOTE: You should assume that the entire server directory will be removed. Make sure that you back up any custom files you stored in the server directory before you begin. NOTE: The client subdirectory under the server install directory will be removed and is no longer needed. The clients are now shipped as separate zip files. 4) Reconfigure the OnDemand configuration files (UNIX only): - ars.cfg - ars.ini - ars.cache - ars.dbfs - arsload.cfg (userid/password for arsload command) 5) Reconfigure the OnDemand script/batch files: - ars_adsm (UNIX Only) - arslog - arsprt NOTE: You should also reconfigure any custom commands that may be affected by the OnDemand command name changes. For example, you may need to modify the /etc/inittab to use arsdb instead of ars_db and arsload instead of ars_load. 6) Upgrade the OnDemand system tables: - Create a temporary working directory NOTE: Make sure that you specify a directory with plenty of free space (20 - 100 MB). The upgrade does not export the data tables, only the OnDemand system tables. Space needed can vary depending on the number of Folders/ApplGroups defined to the system and the number of annotations stored in the database. mkdir /tmp/OnDemand.2210 or mkdir c:\tmp\OnDemand.2210 - Change to the directory cd /tmp/OnDemand.2210 or cd c:\tmp\OnDemand.2210 - Export the existing tables NOTE: Because new tables are added in 2.2.1.0, you must specify the -f flag to ignore errors. You should expect errors because the arsprtusr and arsusrgrpid tables are new to 2.2.1.0. arsdb -flxv - Drop the old tables NOTE: Because new tables are added in 2.2.1.0, you must specify the -f flag to ignore errors. You should expect errors because the arsprtusr and arsusrgrpid tables are new to 2.2.1.0. arsdb -dfv - Create the new tables/indexes arsdb -rtv - Import the old table information into the new tables NOTE: Because new tables are added in 2.2.1.0, you must specify the -f flag to ignore errors. You should expect errors because the arsprtusr and arsusrgrpid files do not exist prior to 2.2.1.0. arsdb -filv - Run maintenance on the new tables arsdb -mv - You are done! NOTE: All server-based printer definitions will not be accessible to end-users. You must run the administrative client to grant authority to these printers. ------------------end of Upgrade Instructions for 2.2.1.0----------------------- 5. Client/Server Backward Compatibility -------------------------------------------------------------------------------- OnDemand has always provided backward compatibility between clients and servers. However, please note the following: - Library and object servers must always be at the same version - The administrative client should always be at the same version as the server - Versions of the administrative client older than 2.2.1.0 will not work against a version 2.2.1.0 server - Version 2.2.1.0 or later of the administrative client will not work against a server older than version 2.2.1.0 - When new function has been added to a version of the client and server, you should not use the new function unless both the client and server are at the same version. For example, if you plan to use the new 64-bit integer data type, both the clients and server must be at version 2.2.1.0 or later. ------------------end of Client/Server Backward compatibility------------------- 6. Documentation Corrections -------------------------------------------------------------------------------- NOTE: For the latest OnDemand publications, see the OnDemand Web site: http://www.software.ibm.com/data/ondemand 6.1 IBM EDMSuite OnDemand: Introduction and Planning Guide, G544-5281-04 OnDemand now supports Oracle 8i (8.1.5.0). See section 7 for more information. 6.1.1 ADSTAR Distributed Storage Manager (ADSM) is now known as Tivoli Storage Manager (TSM). 6.1.2 Page xvii. Related documentation: o The TSM On-line Library CD-ROM contains all of the TSM publications. o DB2 UDB V6.1 is now supported. The DB2 server CD-ROM contains the latest DB2 publications. 6.1.3 Pages 17 - 21. OnDemand and ADSM. TSM includes the same components and works the same way with OnDemand. You define devices and storage configuration to TSM the same way. You administer and operate TSM the same way. 6.1.4 Page 23. AIX server requirements: o DB2 UDB V6.1 is now supported. o We recommend that you install TSM V3.7 on your object servers. 6.1.5 Page 24. HP-UX server requirements: o HP-UX Version 11.00 is now required (version 10.20 is no longer supported). o DB2 UDB V6.1 is now supported. o We recommend that you install TSM V3.7 on your object servers. 6.1.6 Pages 24 - 25. Solaris server requirements: o DB2 UDB V6.1 is now supported. o We recommend that you install TSM V3.7 on your object servers. 6.1.7 Pages 25 - 26. Windows NT server requirements: o DB2 UDB V6.1 is now supported. o Microsoft SQL Server 7 is now supported (SQL Server 6.5 is no longer supported). o We recommend that you install TSM 3.7 on your object servers. 6.1.8 Page 26. Optical and tape storage. See http://www.tivoli.com/tsm for the latest information about supported devices. 6.1.9 Page 26. Optical and tape storage. OnDemand requires version 3.1.0.6 or later of the TSM API. The TSM API is automatically installed as part of the basic, default TSM server installation (along with the TSM administrative client, which is also required by OnDemand). If you install a version of the TSM server earlier than 3.1.0.6, you must obtain version 3.1.0.6 of the TSM API and install it before you can use TSM with OnDemand. 6.1.10 Page 28. Windows client. Beginning with OnDemand Version 2.2.1.5, IBM no longer distributes the Windows 3.1 client. The Win32 client requires a PC with an Intel Pentium 166 MHz (or faster) processor. 6.1.11 Pages 28 - 29. Administrative clients. The clients require a PC with an Intel Pentium 166 MHz (or faster) processor. 6.1.12 Page 58. Table 3. Database and Folder Field Types. The Field Size listed in the table is for DB2 and SQL Server. For Oracle, use the following values: Field Type Field Size ---------- ---------- Small Integer 22 bytes Integer 22 bytes Bit Int Not Supported Decimal 22 bytes String(Fixed) 1 - 254 declared String(Variable) 1 - 254 used plus 4 byte overhead Date 22 bytes Time 22 bytes Date/Time 22 bytes Date/Time (TZ) 22 bytes Application Group N/A Segment N/A Text Search 1 - 254 Annotation Text Search 1 - 254 Annotation Color Search N/A 6.1.13 Page 58. Table 3. Database and Folder Field Types. The field size for the Date and Time fields should be 4 (four) bytes for DB2 and SQL Server. 6.1.14 Page 58. Table 3. Database and Folder Field Types. OnDemand now supports the following database and folder field types: FIELD TYPE FIELD SIZE DESCRIPTION ---------- ---------- ----------- Big Int Eight (8) bytes Contains whole numbers between -922337036854775807 and 922337036854775807. Big integer fields hold a 64-bit integer representation of a number or character string in the form of an integer constant. NOTE: Only DB2 supports the Big Int field type. Annotation 1-254 Use to search annotations to a Text Search document for the specified string. A match occurs and an item is added to the document list if one or more annotations contain the text specified in the search field. You can define one annotation text search field per folder. Annotation N/A Use to search annotations to a Color Search document by specifying a color. A match occurs and an item is added to the document list if the color of the text in one or more annotations is the same as the color specified in the search field. You can define one annotation color search field per folder. 6.1.15 Pages 61 - 87. Estimating storage requirements. You use TSM the same way. You calculate storage requirements for reports, migrated index data, and DB2 log files and backup image files the same way. 6.1.16 Page 68. Table 4. Index Field Types and Sizes. The Field Size listed in the table is for DB2 and SQL Server. For Oracle, use the following values: Field Type Field Size ---------- ---------- Small Integer 22 bytes Integer 22 bytes Bit Int Not Supported Decimal 22 bytes String(Fixed) 1 - 254 declared String(Variable) 1 - 254 used plus 4 byte overhead Date 22 bytes Time 22 bytes Date/Time 22 bytes Date/Time (TZ) 22 bytes 6.1.17 Page 68. Table 4. Index Field Types and Sizes. The field size for the Date and Time fields should be 4 (four) bytes for DB2 and SQL Server. 6.1.18 Page 68. Table 4. Index Field Types and Sizes. OnDemand now supports the following field type in DB2: FIELD TYPE FIELD SIZE ---------- ---------- Big Int 8 (eight) bytes 6.1.19 Page 68. Calculating the size of the database. NOTE: The following formulas were derived from information provided with the database manager products that are supported by OnDemand. See the database manager product information for detailed information. For DB2, use the following formula to estimate the amount of database space required to hold the index data for a report: tableSize = ( Sum of column lengths ) indexSize = ( Index 1 length + 8 ) + ( Index 2 length + 8 ) + ... databaseSize = ( ( tableSize + 40 ) * 1.5 + ( indexSize * 2 ) * number of indexed items per month * number of months to keep index in database For Oracle, use the following formula to estimate the amount of database space required to hold the index data for a report: tableSize = ( Sum of column lengths ) + 3 + ( Number of columns * 2 ) indexSize = ( Index 1 length + 8 ) + ( Index 2 length + 8 ) + ... databaseSize = ( ( tableSize + 40 ) * 1.2 + ( indexSize * 1.2 ) * number of indexed items per month * number of months to keep index in database For SQL Server, use the following formula to estimate the amount of database space required to hold the index data for a report: tableSize = ( Sum of column lengths ) + 6 + Number of VARCHAR columns indexSize = ( Index 1 length + 11 ) + ( 1 if VARCHAR ) ) + ( Index 2 length + 11 ) + ( 1 if VARCHAR ) ) + ... databaseSize = ( ( tableSize + 40 ) * 1.2 + ( indexSize * 1.2 ) * number of indexed items per month * number of months to keep index in database 6.1.20 Page 71. Database transaction log storage. Change the fourth sentence in the first paragraph, that begins with "If you are using SQL Server" to: If you are using SQL Server, when a log file fills, SQL Server closes the full file and opens a new log file, provided you have configured the transaction log to use multiple log files. The OnDemand database uses the AUTOGROW feature to reduce the potential of running out of transaction log space. The log files are truncated after a successful backup of the transaction log and can be reused. 6.1.21 Page 76. Backup report storage space. OnDemand supports one method of maintaining a backup copy of reports: a copy storage pool in TSM. OnDemand no longer supports secondary storage nodes. If you need to maintain two copies of a report on archive media, you must configure a copy storage pool in TSM. 6.1.22 Page 115. Windows client. Beginning with OnDemand Version 2.2.1.5, IBM no longer distributes the Windows 3.1 client. 6.1.23 Page 116. Adobe software provided with OnDemand. Beginning with OnDemand Version 2.2.1.5,IBM no longer distributes the 16-bit versions of the Adobe software. 6.1.24 Pages 123 - 133. Planning for backup and recovery. You can use TSM to maintain DB2 log files and backup image files the same way. You manage the TSM database, recovery log, and other control files the same way. You use TSM to maintain reports on archive media the same way. 6.1.25 Pages 132 - 133. Reports on archive media. OnDemand supports one method of maintaining a backup copy of reports: a copy storage pool in TSM. OnDemand no longer supports secondary storage nodes. If you need to maintain multiple copies of a report on archive media, you must configure a copy storage pool in TSM. ---------- end of corrections to G544-5281-04 ---------------------------------- 6.2 IBM EDMSuite OnDemand: Installation Guide for UNIX Servers, G544-5598-01 OnDemand now supports Oracle 8i (8.1.5.0). See section 7 for installation and configuration information. 6.2.1 ADSTAR Distributed Storage Manager (ADSM) is now known as Tivoli Storage Manager (TSM). 6.2.2 Page xii. Related documentation: o The TSM On-line Library CD-ROM contains all of the TSM publications. o DB2 UDB V6.1 is now supported. The DB2 server CD-ROM contains the latest DB2 publications. 6.2.3 Page 5. AIX server requirements: o DB2 UDB V6.1 is now supported. o We recommend that you install TSM V3.7 on your object servers. 6.2.4 Page 5. HP-UX server requirements: o HP-UX Version 11.00 is now required (version 10.20 is no longer supported). o DB2 UDB V6.1 is now supported. o We recommend that you install TSM V3.7 on your object servers. 6.2.5 Pages 6 - 7. Solaris server requirements: o DB2 UDB V6.1 is now supported. o We recommend that you install TSM V3.7 on your object servers. 6.2.6 Pages 7 - 8. Optical and tape storage. See http://www.tivoli.com/tsm for the latest information about supported devices. 6.2.7 Page 7. Optical and tape storage. OnDemand requires version 3.1.0.6 or later of the TSM API. The TSM API is automatically installed as part of the basic, default TSM server installation (along with the TSM administrative client, which is also required by OnDemand). If you install a version of the TSM server earlier than 3.1.0.6, you must obtain version 3.1.0.6 of the TSM API and install it before you can use TSM with OnDemand. 6.2.8 Page 9. Windows client. Beginning with OnDemand Version 2.2.1.5, IBM no longer distributes the Windows 3.1 client. The Win32 client requires a PC with an Intel Pentium 166 MHz or faster processor. 6.2.9 Page 10. Administrative clients. The clients require a PC with an Intel Pentium 166 MHz or faster processor. 6.2.10 Page 10. Windows client setup program. Beginning with OnDemand Version 2.2.1.5, IBM no longer distributes the Windows 3.1 client. 6.2.11 Pages 21 - 23. Configuration files. For TSM, the path name of the files is different. See the "TSM Quick Start Guide" for your server operating system for information about where the files are stored. 6.2.12 Pages 27 - 28. Installing DB2. DB2 UDB V6.1 is now supported. Follow the instructions in "DB2 V6 Quick Beginnings" to install DB2 and get the latest product updates. 6.2.13 Page 28. Configuration Notes: o For DB2 UDB V6.1, the path names listed in item 2 have changed. See "DB2 V6 Quick Beginnings" for details. o For Solaris servers, create a link to the DB2 shared libraries. For example: cd /lib ln -s /opt/IBMdb2/V6.1/lib/libdb2.so.1 . 6.2.14 Pages 31 - 34. Installing ADSM. For TSM, see the "TSM Quick Start" publication for your server operating system for the latest information on installing and configuring TSM. 6.2.15 Page 31. Installation notes: o For TSM on a library/object server or object server, install the API, Client, Server, and Licenses packages. For TSM on a cache-only library server, install the API and Client packages. NOTE: For AIX, install the 32-bit API, 32-bit Client, Device Support Runtime, License, Server, and Server Runtime packages o To obtain the latest TSM product updates, see: ftp://ftp.service.software.ibm.com/storage/tivoli-storage-manager o OnDemand requires version 3.1.0.6 or later of the TSM client API files. The API files are automatically installed as part of the basic, default TSM server installation. If you install a version of the TSM server earlier than 3.1.0.6, you must obtain version 3.1.0.6 of the API files and install them before you can use TSM with OnDemand. 6.2.16 Pages 31 - 32. Configuration notes. Item 1. For TSM, the server options file can be found in: AIX /usr/tivoli/tsm/server/bin HP-UX /opt/tivoli/tsm/server/bin Solaris /opt/tivoli/tsm/server/bin For TSM, add the following server options to the list: COMMMETHOD HTTP HTTPPORT 1580 6.2.17 Page 36. Item 13. To obtain the latest service update for OnDemand, see: ftp://service.software.ibm.com/software/ondemand/fixes/v221 Then follow the links to the latest PTF for your server. 6.2.18 Page 37. Item 3. Enter the following command: swinstall -s /cdrom/server/hpux/OD2215 -x mount_all_filesystems=FALSE 6.2.19 Page 37. Item 11. To obtain the latest service update for OnDemand, see: ftp://service.software.ibm.com/software/ondemand/fixes/v221 Then follow the links to the latest PTF for your server. 6.2.20 Page 39. Item 3. Enter the following command: /usr/sbin/pkgadd -d /cdrom/server/sun/OD2215 6.2.21 Page 39. Item 7. To obtain the latest service update for OnDemand, see: ftp://service.software.ibm.com/software/ondemand/fixes/v221 Then follow the links to the latest PTF for your server. 6.2.22 Page 49. DB2 parameters. Change ARS_DB2_DATABASE_DRIVE to ARS_DB2_DATABASE_PATH. 6.2.23 Page 51. DB2 and ADSM parameters. For TSM, verify the path name to the options file: AIX /usr/tivoli/tsm/client/api/bin HP-UX /opt/tivoli/tsm/client/api/bin Solaris /opt/tivoli/tsm/client/api/bin 6.2.24 Pages 51 - 53. ADSM parameters. For TSM, verify all of the path names for all of the parameters. For example, the path name for the DSMSERV_DIR parameter should be: AIX /usr/tivoli/tsm/server/bin HP-UX /opt/tivoli/tsm/server/bin Solaris /opt/tivoli/tsm/server/bin 6.2.25 Page 61. Start ADSM. Removing ADSM Records. o For TSM, before you use the ars_adsm command to start TSM, make sure that you have modified it for your server operating system. See item 6.2.26 for details. o For TSM, remove the "autosrvr" record from inittab (the "adsm" record is not created by TSM). 6.2.26 Page 71. ADSM database backup. For TSM, before you use the ars_adsm command to backup the database, make sure that you have modified it for your server operating system. See item 6.2.26 for details. 6.2.27 Page 85. Configuring ars_adsm. For TSM, before you use the ars_adsm command, make sure that you have modified it for your server operating system: o For AIX, locate the following lines: ADSM_DIR=/usr/lpp/adsmserv/bin ADSM_CLIENT_DIR=/usr/lpp/adsm/bin and change them to: ADSM_DIR=/usr/tivoli/tsm/server/bin ADSM_CLIENT_DIR=/usr/tivoli/tsm/client/api/bin o For HP-UX, locate the following lines: ADSM_DIR=/opt/adsmserv/bin ADSM_CLIENT_DIR=/usr/adsm and change them to: ADSM_DIR=/opt/tivoli/tsm/server/bin ADSM_CLIENT_DIR=/opt/tivoli/tsm/client/api/bin o For Sun Solaris, locate the following lines: ADSM_DIR=/opt/IBMadsm-s/bin ADSM_CLIENT_DIR=/opt/IBMadsm-c and change them to: ADSM_DIR=/opt/tivoli/tsm/server/bin ADSM_CLIENT_DIR=/opt/tivoli/tsm/client/api/bin 6.2.28 Page 88. Starting the server. For TSM, the dsmserv command is in the following directory: AIX /usr/tivoli/tsm/server/bin HP-UX /opt/tivoli/tsm/server/bin Solaris /opt/tivoli/tsm/server/bin 6.2.29 Pages 105 - 107. Configuring device drivers (under Adding an automated tape library for HP-UX). For TSM, for the latest information, see "TSM for HP-UX Quick Start", GC35-0370. 6.2.30 Page 114. Preparing storage pool volumes. The example LABEL LIBVOL command is incorrect: o To label storage volumes and check them into a library that is filled with blank storage volumes, use the following command: label libvol archlib0 search=yes overwrite=yes checkin=scratch labelsource=prompt o To label storage volumes and check them into a library by manually inserting each new storage volume when prompted, use the following command: label libvol archlib0 search=bulk overwrite=yes checkin=scratch labelsource=prompt With both forms of the command, you are prompted to label each storage volume. 6.2.31 Page 116. About storage pools. Third paragraph, fourth item. OnDemand no longer supports secondary storage nodes. If you need to maintain multiple copies of a report on archive media, you must configure a copy storage pool in TSM. 6.2.32 Page 119. In the example define schedule command, change 'startime' to 'starttime'. 6.2.33 Page 123 - 124. Replace the topic titled "Setting the client node password in DB2" with the following: Setting the client node password in DB2 Before DB2 can use TSM to maintain log files and backup image files, you must set the client node password in DB2 on the library server. You established the client node password when you registered the client node in TSM (see "Registering the DB2 client node" on page 123). Use the dsmapipw command to set the client node password in DB2. The dsmapipw command is installed in the INSTHOME/sqllib/adsm directory of the instance owner. (By default, the OnDemand instance owner is "archive".) To set the client node password: 1. On the library server, log in as the root user. 2. Open a terminal window. 3. Set the DSMI_DIR and DSMI_CONFIG environment variables. These variables identify the user-defined directory that contains the API trusted agent file and the full path name of the options file that TSM uses to identify the server that maintains the DB2 files. (You created the options file in Defining client user options on page 120.) For example: export DSMI_DIR=/usr/tivoli/tsm/client/api/bin export DSMI_CONFIG=/usr/tivoli/tsm/client/api/bin/dsm.opt.db2 4. Run the dsmapipw command. For example: /home/archive/sqllib/adsm/dsmapipw 5. The dsmapipw command prompts you for the following information: old password, which is the current password for the client node. This is the password you specified when you registered the client node in TSM (see Registering the DB2 client node on page 123). new password, which is the password that will be stored in DB2. You will be prompted twice for the password. NOTE: Unless you have a good reason for *not* doing so, specify the old password when prompted. 6. Close the terminal window. 7. If DB2 is running, you should stop and restart DB2. Important: If you change the client node password in TSM, remember to run the dsmapipw command to set the new password in DB2. 6.2.34 Page 129. Defining storage sets. Third paragraph. OnDemand supports one method of maintaining a backup copy of reports: a copy storage pool in TSM. OnDemand no longer supports secondary storage nodes. If you need to maintain two copies of a report on archive media, you must configure a copy storage pool in TSM. 6.2.35 Page 136. Storing system migration data in table spaces. In item 7, changes "system log" to "system migration". 6.2.36 Page 158. Table 18. Supported Language Codes, Locales, and Code Sets. Arabic is now supported. Add the following item to the table: Language Code Country Op. System Locale Code Set ------------- ------- ---------- ------ -------- ARA Arabic AIX ar_AA ISO8859-6 HP-UX ar_SA.iso88596 iso88596 6.2.37 Page 161. Mapping AFP fonts. The ARSFONT.PDF file provides details about mapping AFP fonts. You can get a copy from the OnDemand publications CD-ROM or the OnDemand web site. 6.2.38 Page 163. Second paragraph under the first item on the page that begins with "For all other types of data". The ARSFONT.PDF file provides details about mapping AFP fonts. You can get a copy from the OnDemand publications CD-ROM or the OnDemand web site. 6.2.39 Page 171. Overview. In the second sentence, change ARS_DB2_DATABASE_DRIVE to ARS_DB2_DATABASE_PATH. ---------- end of corrections to G544-5598-01 ---------------------------------- 6.3 IBM EDMSuite OnDemand: Installation Guide for Windows NT Servers, G544-5526-05 OnDemand now supports Oracle 8i (8.1.5.0). See section 7 for installation and configuration information. 6.3.1 ADSTAR Distributed Storage Manager (ADSM) is now known as Tivoli Storage Manager (TSM). 6.3.2 Page xiii. OnDemand publications. The following publications have been replaced and obsoleted by the "OnDemand User's Guide," SC26-9810: Installation Guide for OnDemand Clients, G544-5527 Getting Started with the OS/2 Client, S544-5510 Getting Started with the Windows 3.1 Client, S544-5509 Getting Started with the Windows NT and Windows 95/98 Client, S544-5469 6.3.3 Page 3. Installation checklist. Items 7 and 9. To install and configure TSM on your object servers, see "Installing and Configuring Tivoli Storage Manager", which replaces and obsoletes information used to install and configure TSM from the installation and configuration guide. You can get a copy from: http://www.software.ibm.com/data/ondemand 6.3.4 Page 4. Item 3 under "Verify the installation of OnDemand." Use the "User's Guide," SC26-9810. (The "Installation Guide for OnDemand Clients" is obsolete.) 6.3.5 Page 7. Server software requirements: o DB2 UDB V6.1 is now supported. o Microsoft SQL Server 6.5 is no longer supported. If you plan to use SQL Server as the database manager, you must install SQL Server 7. o We recommend that you install TSM V3.7 on your object servers. 6.3.6 Pages 7 - 8. Optical and tape storage. o See http://www.tivoli.com/tsm for the latest information about supported devices. o OnDemand requires version 3.1.0.6 or later of the TSM API. The TSM API is automatically installed as part of the basic, default TSM server installation (along with the TSM administrative client, which is also required by OnDemand). If you install a version of the TSM server earlier than 3.1.0.6, you must obtain version 3.1.0.6 of the TSM API and install it before you can use TSM with OnDemand. 6.3.7 Pages 9 - 10. Windows client. Beginning with OnDemand Version 2.2.1.5, IBM no longer distributes the Windows 3.1 client. The Win32 client requires a PC with an Intel Pentium 166 MHz or faster processor. 6.3.8 Page 10. Administrative clients. The clients require a PC with an Intel Pentium 166 MHz or faster processor. 6.3.9 Page 11. Windows client setup program. Beginning with OnDemand Version 2.2.1.5, IBM no longer distributes the Windows 3.1 client. 6.3.10 Page 19. OnDemand system administrator account. After you install and configure the system, remember to add the ODADMIN user to OnDemand. If you change the password in User Manager, remember to change it in OnDemand. 6.3.11 Page 23. Installing DB2. DB2 UDB V6.1 is now supported. Follow the instructions in "DB2 UDB for Windows NT V6 Quick Beginnings" to install DB2. 6.3.12 Page 24. Installing DB2 FixPak. For DB2 UDB V6.1, the current FixPak is FP2_WR21163 (12/99). Go to the FTP site listed on page 24. Follow the links for your language and DB2 V6.1 operating system. Follow the link to the latest FixPak. Get the ZIP file for the FixPak and the README files. Follow the instructions in the README files to apply the FixPak. 6.3.13 Page 25 - 26. Installing SQL Server. If you plan to use SQL Server as the database manager, you must install SQL Server 7 (SQL Server 6.5 is not supported). See the SQL Server 7 installation information to install SQL Server on the library server. 6.3.14 Pages 27 - 28. Installing ADSM. To install TSM on your object servers, see "Installing and Configuring Tivoli Storage Manager", which replaces and obsoletes information used to install and configure TSM from the installation and configuration guide. You can get a copy from: http://www.software.ibm.com/data/ondemand 6.3.15 Pages 33 - 54. Configuring ADSM. To configure TSM on your object servers, see "Installing and Configuring Tivoli Storage Manager", which replaces and obsoletes information used to install and configure TSM from the installation and configuration guide. You can get a copy from: http://www.software.ibm.com/data/ondemand 6.3.16 Pages 56 - 57. Important things to remember. Make the following changes to the list of items in the third paragraph: 1. Change "Size of the database (SQL Server)" to "Size of Database" 2. Change "Location of primary log files (DB2)" to "Location of log files" 3. Change "Number of primary log files (DB2)" to "Number of log files" 4. Change "First file system named (DBFS and Cache)" to "First cache file system named" 6.3.17 Page 60. Add the following item to SQL Server: o Number of Log Files 6.3.18 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. 6.3.19 Page 78. Storing system migration data in table spaces. Item 6. Change "system log" to "system migration." 6.3.20 Page 86. Table 3. Supported Language Codes, Locales, and Code Sets. Arabic is now supported. Add the following item to the table: Language Code Country Locale Code Set ------------- ------- ------ -------- ARA Arabic AA 1256 6.3.21 Page 87. Mapping AFP fonts. The ARSFONT.PDF file provides details about mapping AFP fonts. You can get a copy from the OnDemand publications CD-ROM or the OnDemand web site. 6.3.22 Page 89. Data type. The ARSFONT.PDF file provides details about mapping AFP fonts. You can get a copy from the OnDemand publications CD-ROM or the OnDemand web site. 6.3.23 Page 108. Working with instances. Change the last sentence on the page to "After locating the instance in the Registry, OnDemand..." 6.3.24 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 (see the README.TXT file on the server CD-ROM). You may install the Acrobat Distiller software on any OnDemand library or object server for which you hold a license. 6.3.25 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 ---------------------------------- 6.4 IBM EDMSuite OnDemand: User's Guide, SC26-9810-00 6.4.1 ADSTAR Distributed Storage Manager (ADSM) is now known as Tivoli Storage Manager (TSM). 6.4.2 Page 3. Change the second paragraph, that begins with "To view PDF documents..." to "For Windows clients, to view PDF documents..." 6.4.3 Page 4. Installing Adobe software. OS/2 software. Change the first sentence in the second paragraph to "You need the Acrobat Reader for OS/2 Warp to view the OnDemand publications provided in PDF format on the CD-ROM." The OS/2 client does not support viewing PDF documents retrieved from OnDemand. 6.4.4 Pages 11 - 14. Installing for Windows 3.1. Beginning with OnDemand Version 2.2.1.5, IBM no longer distributes the Windows 3.1 client with the product. 6.4.5 Page 12. Change items 2 and 3 at the top of page to: 2. Select Run from the File menu. 3. In the Command Line field, type x:\client\windows\win16\setup (where x is the letter of your CD-ROM drive or the network drive). Then press Enter. 6.4.6 Page 12, To install on a user's PC. Change items 2 and 3 to: 2. Select Run from the File menu. 3. In the Command Line field, type x:\client\windows\win16\setup (where x is the letter of your CD-ROM drive or the network drive). Then press Enter. 6.4.7 Page 15. Hardware. The OnDemand client requires a PC with an Intel Pentium 166 MHz (or faster) processor. 6.4.8 Pages 16 - 17. Installing for Windows 95, Windows 98, and Windows NT describes how to install the client from Autorun. However, the client CD-ROM does not contain the Autorun files. Therefore, you cannot install the client from Autorun. 6.4.9 Page 19. To use Uninstall. To remove the OnDemand client software from the PC, use the Add/Remove Programs applet in Control Panel. 6.4.10 Pages 33 - 35. Starting the OnDemand client. The OnDemand program folder/group has been renamed to IBM OnDemand. 6.4.11 Page 58. Changing start up parameters. Item 1. The OnDemand program folder/group has been renamed to IBM OnDemand. Item 3. The default client software installation directory is now: \Program Files\IBM\OnDemand32 6.4.12 The following information can be used to obtain and install the latest version of OnDemand client software from IBM service on the World Wide Web. Note: these instructions assume you use Netscape Navigator to browse the Web. The steps for other browsers may be different. 1. Point your browser to: ftp://service.software.ibm.com/software/ondemand/fixes/v221 Follow the links to the latest PTF for your client. 2. Click the ZIP file for the client you want to install or upgrade. For example: odwin32.zip 3. Select Save it to disk. 4. Click OK. 5. Choose the Save as location. 6. Click Save. After the download is complete, you can expand the ZIP file or store the ZIP file in a shared location, depending on how you plan to distribute the client software: o A user can expand the ZIP file to a temporary directory and then run the Setup program to install or update the client on a PC. After expanding the ZIP file, follow the instructions in the OnDemand User's Guide, SC26-9810, to install the client. See "Install on a user's PC" for details. After installing the client, the user can delete the temporary directory and the ZIP file. o An administrator can store the ZIP file in a shared location so that other users can access it. o An administrator can expand the ZIP file to a shared location so that other users can run the Setup program from the shared location. o If your organization shares a copy of the OnDemand client software from a network server, an administrator can expand the ZIP file and run the Setup program to install or update the client on the server. o If your organization distributes user-defined files with the OnDemand client, an administrator must expand the ZIP file to a shared location and then copy the user-defined files to that location. Users can then run the Setup program from the shared location to install or update the client software and the user-defined files on their PCs. ---------- end of corrections to SC26-9810-00 ---------------------------------- 6.5 IBM EDMSuite OnDemand: Administrator's Reference, S544-5293-08 6.5.1 ADSTAR Distributed Storage Manager (ADSM) is now known as Tivoli Storage Manager (TSM). 6.5.2 Page xv. Related documentation: o ADSM has been replaced by TSM. You can find copies of the TSM publications on the TSM On-line Library CD-ROM. o DB2 UDB V6.1 is now supported. The DB2 server CD-ROM contains copies of the latest DB2 publications. 6.5.3 Pages 14 - 15. Loading storage objects. OnDemand no longer supports secondary storage nodes. Use a TSM copy storage pool if you need to maintain multiple copies of data on archive media. 6.5.4 Page 41. The second paragraph contains a reference to secondary storage node. OnDemand no longer supports secondary storage nodes. 6.5.5 Page 63. Reports on archive media. OnDemand no longer supports secondary storage nodes. Use a TSM copy storage pool to maintain a backup copy of data on archive media. 6.5.6 Page 80. Searching the library. The VOLRANGE parameter works only with libraries that support a bar code reader (IBM 3995 libraries do not). To label all of the volumes in a library that has been filled with blank storage volumes, use the following command: label libvol odlib0 search=yes overwrite=yes checkin=scratch labelsource=prompt The LABEL LIBVOL command prompts you for the label of each storage volume. 6.5.7 Page 89. Starting ADSM. For TSM, make sure that you have modified the ars_adsm command for your server operating system. See item 6.5.18 in this README for details. 6.5.8 Page 105. Monitoring the network. The OnDemand processes no longer provide information that can be displayed with the netstat command. You can obtain information about the number of users on the system from the system log. For example, message numbers 201 and 202 contain information about the maximum number of users and the number of logged on users in 30 minute increments. 6.5.9 Pages 109 - 112. Administrative tools and procedures. ADSM Version 3 has been replaced by TSM V3.7. See your TSM information for help with administering TSM. 6.5.10 Page 109. OnDemand configurator. The "Installation and Configuration Guide for Windows NT Servers", G544-5526 describes how to use the configurator. 6.5.11 Page 109. Administrative client. "Getting Started with the Administrative Client," S544-5293-08 describes how to install the administrative client. The "Installation Guide for OnDemand Clients" publication is obsolete. 6.5.12 Page 110. Administering SQL Server. SQL Server 6.5 is no longer supported. Use SQL Server 7 instead. 6.5.13 Page 113. Install and configure the system. The "User's Guide", SC26-9810 contains information about installing OnDemand clients. 6.5.14 Page 115. Software licensing. ADSM. For TSM, see your TSM information for help with administering TSM. 6.5.15 Page 117. Starting and stopping services. For TSM, the TSM services are: TSM Server and TSM Scheduler. 6.5.16 Page 117. Starting and stopping services. Two services has been added with DB2 UDB V6.1: DB2 JDBC Applet Server and DB2 JDBC Applet Server - Control Center. The services should automatically start when the system is booted. 6.5.17 Page 127. The second paragraph on the page. For TSM, the "DB2 Administration Guide: Design and Implementation" contains information about managing DB2 files in TSM. 6.5.18 Page 139. arsadm command reference. The following changes have been made to the arsadm command: 1) The arsadm user function has been changed to allow users with a User Type of ApplGrp/Folder Administrator or User Administrator to have the following additional Create authorities: o An ApplGrp/Folder Administrator can be given Create Users and Create Groups authority. o A User Administrator can be given Create Groups, Create ApplGrps, and Create Folders authority. The -t flag has been changed so that the c, e, a, f,and b values can be combined with the u, g,and d values where appropriate. User types: u - User g - User Administrator d - ApplGrp/Folder Administrator s - System Administrator Authorities: c - Create Users authority e - Create Groups authority a - Create ApplGrps authority f - Create Folders authority b - Create ApplGrps, Create Folders authority Examples: -t u User -t ceaf User w/Create Users, Groups, ApplGrps, Folders authority -t uceaf User w/Create Users, Groups, ApplGrps, Folders authority -t uceb User w/Create Users, Groups, ApplGrps, Folders authority -t uc User w/Create Users authority -t g User Administrator -t geaf User Administrator w/Create Groups, ApplGrps, Folders authority -t geb User Administrator w/Create Groups, ApplGrps, Folders authority -t ge User Administrator w/Create Groups authority -t d ApplGrp/Folder Administrator -t dce ApplGrp/Folder Administrator w/Create Users, Groups authority -t dc ApplGrp/Folder Administrator w/Create Users authority -t s System Administrator Notes: 1) The -t flag values can be specified in any order (for example, -t ge or -t eg specify the same thing). 2) If u, g, or d is not specified as one of the values and more than one value exists, a user type of User is assumed (that is, -t ce). 3) The only valid values that can be specified with u are c, e, a, f, and b. 4) The only valid values that can be specified with g are e, a, f, and b. 5) The only valid values that can be specified with d are c and e. 6) No other values can be specified with s. 2) The Inactivity Time Out value can now be specified for users when adding or updating a user. The new flag is -s. Valid values for the -s flag are: -1 = Never Time Out 0 = Use System Inactivity Time Out Value >0 = Number of Minutes ( 1 - 1440 minutes ) 3) Inactive userids can now be deleted with the arsadm user function, using two new flags: -e expire_date and -f date_format. The two new flags are valid only when deleting inactive userids. You can use one of following three formats to delete inactive userids: A) Delete one userid: arsadm user -u userid -p passwd -h host -a d -i USER1 -v For example: arsadm user -u wagner -p "" -h everest -a d -i DEBBIE -v B) Delete all userids inactive since a specified date: arsadm user -u userid -p passwd -h host -a d -e expire_date -v For example: arsadm user -u wagner -p "" -h everest -a d -e 11/12/1998 -v C) Delete all userids inactive since a specified date using a date format: arsadm user -u userid -p passwd -h host -a d -e expire_date -f date_format -v For example: arsadm user -u wagner -p "" -h everest -a d -e "November 12, 1998" -f "%B %e, %Y" -v When deleting userids with the date method, arsadm uses the following process to determine if a userid should be deleted: 1) A query is performed for all of the userids that can be maintained by the logged on user. 2) Each userid is examined. If the user's password has not been updated between the specified date and the current system date, the userid is deleted. For example, assume that passwords expire every 180 days. User A logs on to the server on 3/15/1999; User B logs on to the server on 10/20/1998. Both users changed their passwords when they logged on, and have not logged on to the server since that time. You run the arsadm user command on 11/12/1999 to delete inactive userids. You specify an expire date of 11/12/1998. When the arsadm command runs, User A is not deleted because the password was updated within the date range (11/12/1998 - 11/12/1999). However, User B is deleted because the password has not been updated since 10/20/1998. The following example shows how to configure the system to automatically remove inactive userids on a regular schedule. For example, you could use the process to remove users that have not logged on for at least 180 days. 1) On the server, set Minimum Password Age to Expires In 180 Days. 2) Create a shell script that uses arsdate to determine the date for 180 days prior to today's date: arsdate -g -d -180 -f "%m/%d/%Y" 3) Using the date returned by arsdate, run the arsadm user command to delete inactive userids: arsadm user -u wagner -p "" -h everest -a d -e expire_date -v 4) Run the shell script every day from inittab. When the shell script runs, userids that have not logged on to the server in at least 180 days will be deleted. Notes 1) The -f flag is optional. If you do not specify the -f flag, the default date format is "%m/%d/%Y". 2) Userids should *NOT* be deleted with the date method if you do not use password expiration on the server (that is, Minimum Password Age is set to Password Never Expires). 3) When you add a userid to the server, the user must change their password the first time that they log on. If you add a new userid and you run the arsadm user delete function with the -e flag before the user logs on for the first time, the userid will be deleted. 6.5.19 Pages 165 - 167. ars_adsm command reference. For TSM, before you use the ars_adsm command, make sure that you have modified it for your server operating system. See item 6.2.26 for details. 6.5.20 Page 169. arsdate command reference. Purpose The arsdate command can be used to display the database value for a given date and time string or display the date and time string for a given database value. Values whose data types are Date, Time, Date/Time, or Date/Time (TZ) are represented in an internal form that is transparent to the casual user of OnDemand. Casual users enter these values the same way they appear in a report. However, to search the database with an SQL string, a user must enter the internal form of the value. The arsdate command shows you the internal value of a date or time string. Parameters -a Use to display database values and date strings for Date fields. For example, to display the database value for the date 9/1/99, enter: arsdate -a 9/1/99 The arsdate command returns: 9/1/99 -> 10836 To display the date string for the database value 10836 in the default format, enter: arsdate -a 10836 The arsdate command returns: 10836 -> 9/1/99 -i Use to display database values and date and time strings for Date/Time fields. The time part of a Date/Time field is not adjusted for the local time zone. You typically use the -i parameter to find out one of two things: o Given a date and time printed on a report, what value did OnDemand store in a Date/Time database field? You can use the result to search a Date/Time field with an SQL string. o Given a value stored in a Date/Time database field, what would be the date and time printed on a report? -t Use to display database values and time strings for Time fields. The time is not adjusted for the local time zone. For example, to display the database value for the time 04:00:00, enter: arsdate -t 04:00:00 The arsdate command returns: 04:00:00 -> 4800 To display the time string for the database value 4800, enter: arsdate -t 4800 The arsdate command returns: 4800 -> 04:00:00 -z Use to display database values and date and time strings for Date/Time (TZ) fields. The time part of a Date/Time (TZ) field is adjusted for the local time zone. If you run the arsdate command with the -z parameter on systems in different time zones and you specify the same date and time value, the result will be different. For example, suppose you need to determine the value stored in a Date/Time (TZ) field for "09/01/99 04:00:00". The command: arsdate -z "09/01/99 04:00:00" on a system in the Eastern time zone will return: 09/01/99 04:00:00 -> 936187200 If you run the same command on a system in the Mountain time zone, the result will be: 09/01/99 04:00:00 -> 936180000 A typical use of the -z parameter is to determine a database value with which to search the OnDemand system log. You can use the result to search the Date/Time (TZ) field of the system log with an SQL string. For example, suppose a user in New York logs on to a server in Denver. To retrieve the log on message with an SQL string, you must specify the date and time part of the query using the local time of the client that is running the query. If the user logged on to the server at 4 a.m. Eastern time, a query run in Denver must specify 2 a.m. to retrieve the message. Examples 1. The following example shows how to determine the database value for the specified date and time string. The data type of the database field is Date/Time. arsdate -i "09/01/99 04:00:00" 09/01/99 04:00:00 -> 936158400 In this example you could use the database value to search a Date/Time field in the database with an SQL string. For example: arsdoc get -i "WHERE somedate=936158400" ... 2. The following example shows how to determine the date and time string for the specified database value. The data type of the database field is Date/Time. The result is shown using the default display format. arsdate -i 936158400 936158400 -> 09/01/99 04:00:00 3. The following example shows how to determine the database value for the specified date and time string. The data type of the database field is Date/Time (TZ). The arsdate command adjusts the time part of the result for the local time zone. arsdate -z "09/01/99 04:00:00" 09/01/99 04:00:00 -> 936180000 If you were to run the same command on a system in the Eastern time zone, the result would be: arsdate -z "09/01/99 04:00:00" 09/01/99 04:00:00 -> 936187200 Notes 1. When displaying the date string for a given internal value, by default, the arsdate command displays the date string using the mm/dd/yy format. If you want the arsdate command to display the date string using a different format, you must specify the date format with the -f parameter. For example: arsdate 10907 10907 -> 11/11/99 arsdate -f "%m/%d/%Y" 10907 10907 -> 11/11/1999 2. When displaying the internal value for a given date string, by default, the arsdate command expects you to specify the date string using the mm/dd/yy format. If you want to specify the date string using a different format, you must specify the date format with the -f parameter. For example: arsdate 11/11/99 11/11/99 -> 10907 arsdate 11/11/1999 11/11/1999 -> -1 (Error) arsdate -f "%m/%d/%Y" 11/11/1999 11/11/1999 -> 10907 6.5.21 Page 173. arsdb command reference. If you plan to use Oracle with OnDemand, then you will need to use standard Oracle procedures to start, stop, maintain, and optimize the database, to make backup copies of the database, and so forth. In addition, some of the other options for the arsdb command do not apply when using Oracle with OnDemand. See Section 7 of this README for details. 6.5.22 Page 181. arsdoc command reference. All of the arsdoc command functions now support the -G parameter to specify the name of the application group. o ADD. When the database query is run to retrieve the document that contains the data used in the add, the search is limited to the specified application group, even if the folder named with the -f parameter contains more than one application group. This ensures that only documents in the specified application group can be used for the add. o UPDATE. When the database query is run to determine the document(s) to update, the search is limited to the specified application group, even if the folder named with the -f parameter contains more than one application group. This guarantees that only documents in the specified application group can be updated. o DELETE. The -G parameter has been added as an optional parameter. If specified, the database query that is run to determine the document(s) to delete is limited to the specified application group. The addition of the -G parameter allows you to delete documents from a specific application group in folders that contain more than one application group. If you do not specify the -G parameter, the query runs against all of the application groups in the folder. o GET. The -G parameter has been added as an optional parameter. If specified, the database query that is run to retrieve documents is limited to the specified application group, even if the folder named with the -f parameter contains more than one application group. If you do not specify the -G parameter, the query runs against all of the application groups in the folder. o QUERY. The -G parameter has been added as an optional parameter. If specified, the database query is run against the specified application group, even if the folder named with the -f parameter contains more than one application group. If you do not specify the -G parameter, the query runs against all of the application groups in the folder. o PRINT. The -G parameter has been added as an optional parameter. If specified, the database query that is run to determine the document(s) to print is limited to the specified application group, even if the folder named with the -f parameter contains more than one application group. If you do not specify the -G parameter, the query runs against all of the application groups in the folder. NOTES: 1. For the ADD and UPDATE command functions, you can use either the -g or -G parameter to specify the name of the application group. 2. You can use the -G parameter with the -i parameter to query folders that contain more than one application group. For example, a folder contains three application groups. You want to query only one of the application groups. Use the -G parameter to specify the application group that you want to query. Use the -i parameter to specify the application group's database field. You can also use the -G and -i parameters when the application groups have different database field names. The following example shows how to search a folder and three application groups that have different database field names: arsdoc get -f "Student Information" -G loans -i "where number LIKE '123456' and loan_date = 10593" arsdoc get -f "Student Information" -G grades -i "where number LIKE '123456' and grade_date = 10593" arsdoc get -f "Student Information" -G transcripts -i "where number LIKE '123456' and trans_date = 10593" 3. You can use the -G parameter with the -q parameter to query folders that contain more than one application group. When you specify the -G parameter and you specify a public named query with the -q parameter, the arsdoc command queries the application group named with the -G parameter instead of the application group specified in the named query. (If you do not specify the -G parameter, the query runs against the application group specified in the named query. If the named query does not identify an application group, the query runs against all of the application groups in the folder.) 6.5.23 Page 181. arsdoc command reference. The arsdoc ADD function can now be performed without providing an input document from a file or by retrieving an existing document from the system. This means that you can add database field values without adding a document. To add database field values without adding a document, do not specify the -o -i, or -q parameters; specify the database field names and their values using one or more -n parameters. 6.5.24 Page 187. Parameters. The -c parameter should be used only for AFP and line data. 6.5.25 Page 205. arsload command reference. The following change has been made to the arsload command: The arsload command now supports the -j parameter to specify the name of a file that contains additional indexing parameters. For example: arsload ... -j /tmp/extraIndexing.parameters ... When you specify the -j parameter and name a file, the arsload command adds the indexing parameters from the specified file to the indexing parameters that it extracts from the application. (Indexing parameters are typically specified on the Indexing Information page in applications.) If an indexing parameter appears in both the specified file and the application, the arsload command uses the value from the specified file. 6.5.26 Page 223. arsview command reference. The following changes have been made to the arsview command: 1. The arsview command now supports an orientation of 180 degrees. The -o parameter now accepts values of 0, 90, 180, and 270. 2. The arsview command now accepts the -x parameter. If you specify -x, the output will not contain horizontal or vertical lines that were present in the AFP document. 3. The arsview command now accepts the -y parameter. Specify the -y parameter to use the character space reset algorithm to place text in the output. ----------- end of corrections to S544-5293-08 --------------------------------- 6.6 IBM EDMSuite OnDemand: Indexing Reference, S544-5489-05 6.6.1 ADSTAR Distributed Storage Manager (ADSM) is now known as Tivoli Storage Manager (TSM). 6.6.2 Page xvi. Related documentation: o ADSM has been replaced by TSM. You can find copies of the TSM publications on the TSM On-line Library CD-ROM. o DB2 UDB V6.1 is now supported. See the DB2 server CD-ROM for the latest DB2 publications. 6.6.3 Page 62. CCTYPE parameter. It is very important to correctly identify the type of carriage control characters in the input file. ACIF may process an input file even though the CCTYPE parameter incorrectly identifies the type of carriage control characters in the input file. However, the output file may be unusable. If you are not certain which type of carriage control characters are in the input file, contact your system administrator. 6.6.4 Page 67. DEFAULT keyword. The default value can be specified either as character data or hexadecimal data. If the input data is anything other than ASCII, the default value must be specified in hexadecimal. If the input data is ASCII, use the following format: DEFAULT='value' 6.6.5 Page 69. Transaction field syntax. Options and values. Change the second sentence in the second and third paragraphs from "A transaction trigger must specify..." to "A transaction field must specify..." 6.6.6 Page 71 - 72. FILEFORMAT parameter. The NEWLINE keyword now supports a two-character line delimiter, which is common in data from DOS, OS/2, and Windows operating systems. The following shows an example of a FILEFORMAT parameter used to process input data containing two-character line delimiters: FILEFORMAT=STREAM,(NEWLINE=X'0D0A') The NEWLINE keyword must be specified if the line delimiter is two characters. If the NEWLINE keyword is not specified, the default line delimiter is X'0A' for ASCII data and X'25' for EBCDIC data. 6.6.7 Page 75. GROUPNAME parameter. Change the NOTE to "When defining the group name, a FIELD cannot be based on a floating trigger." 6.6.8 Page 85. LINECNT parameter. The default value is 0 (zero). A value of zero means that ACIF will not create any page breaks. The document will be stored as a single page if there are no carriage controls present in the data. 6.6.9 Page 103 - 104, USERMASK parameter. The USERMASK must be specified in hexadecimal when CPGID=500 and the input data is EBCDIC. For example: USERMASK=1,'*',X'C181C282C383' FIELD3=*,*,15,(OFFSET=(10:24),MASK='*@@@@@@@@@@@@@@',ORDER=BYROW) 6.6.10 Page 127. Message number 0425-278. In the explanation, change "The OIB can be contained..." to "The IOB can be contained..." 6.6.11 Page 169. In the second paragraph under Variable-length files, change X'0A0D' to X'0D0A'. 6.6.12 Page 203, "Format of the generic indexer file." OnDemand now supports two formats of the generic indexer file. In addition to the format described in the book, the new generic indexer file format can contain the following lines: COMMENT: A comment line. Comment lines can be placed anywhere in the file. CODEPAGE: Identifies the code page of the index data. You can specify one and only one code page. The CODEPAGE: line must appear before the groups. After the CODEPAGE: line, define the groups. Each group represents one document to be indexed. A group consists of the following: GROUP_FIELD_NAME: Identifies a database field name. You can specify 1 - 32 fields. You must specify one for each application group field. GROUP_FIELD_VALUE: The value of the database field. Specify one VALUE for each FIELD. Note: Specify one or more pairs of GROUP_FIELD_NAME and GROUP_FIELD_VALUE lines -- one pair for each index field. After you've defined all of the GROUP_FIELD_NAME and GROUP_FIELD_VALUE pairs, complete the group by coding the following three lines: GROUP_OFFSET: The byte location of the data to be indexed. Specify 0 (zero) for the first byte in the file. GROUP_LENGTH: The length in bytes of the document. Specify 0 (zero) to process the entire input file. GROUP_FILENAME: The full path name of the input file on the server. If one input file contains multiple documents to be to be indexed, specify the input file name on the GROUP_FILENAME: line in the first group and leave the GROUP_FILENAME: lines in all other groups blank. The following example generic indexer file shows how to index three documents with two fields. There is a different input file for each document: COMMENT: COMMENT: Generic Indexer Example 1 COMMENT: Different input file for each document COMMENT: COMMENT: Specify code page of the index data CODEPAGE:819 COMMENT: Document #1 COMMENT: Index field #1 GROUP_FIELD_NAME:rdate GROUP_FIELD_VALUE:07/13/99 COMMENT: Index field #2 GROUP_FIELD_NAME:studentID GROUP_FIELD_VALUE:0012345678 COMMENT: document data starts at beginning of file GROUP_OFFSET:0 COMMENT: document data goes to end of file GROUP_LENGTH:0 GROUP_FILENAME:/arstmp/statement7.out COMMENT: Document #2 COMMENT: Index field #1 GROUP_FIELD_NAME:rdate GROUP_FIELD_VALUE:08/13/99 COMMENT: Index field #2 GROUP_FIELD_NAME:studentID GROUP_FIELD_VALUE:0012345678 GROUP_OFFSET:0 GROUP_LENGTH:0 GROUP_FILENAME:/arstmp/statement8.out COMMENT: Document #3 COMMENT: Index field #1 GROUP_FIELD_NAME:rdate GROUP_FIELD_VALUE:09/13/99 COMMENT: Index field #2 GROUP_FIELD_NAME:studentID GROUP_FIELD_VALUE:0012345678 GROUP_OFFSET:0 GROUP_LENGTH:0 GROUP_FILENAME:/arstmp/statement9.out COMMENT: COMMENT: End Generic Indexer Example 1 The following example generic indexer file shows how to index three documents with two fields. One input file contains all of the documents: COMMENT: COMMENT: Generic Indexer Example 2 COMMENT: One input file contains all documents COMMENT: COMMENT: Specify code page of the index data CODEPAGE:819 COMMENT: Document #1 GROUP_FIELD_NAME:rdate GROUP_FIELD_VALUE:07/13/99 GROUP_FIELD_NAME:studentID GROUP_FIELD_VALUE:0012345678 COMMENT: first document starts at beginning of file (byte 0) GROUP_OFFSET:0 COMMENT: document length 8124 bytes GROUP_LENGTH:8124 GROUP_FILENAME:/arstmp/accounting.student information.loan.out COMMENT: Document #2 GROUP_FIELD_NAME:rdate GROUP_FIELD_VALUE:08/13/99 GROUP_FIELD_NAME:studentID GROUP_FIELD_VALUE:0012345678 COMMENT: second document starts at byte 8124 GROUP_OFFSET:8124 COMMENT: document length 8124 bytes GROUP_LENGTH:8124 COMMENT: use prior GROUP_FILENAME: GROUP_FILENAME: COMMENT: Document #3 GROUP_FIELD_NAME:rdate GROUP_FIELD_VALUE:09/13/99 GROUP_FIELD_NAME:studentID GROUP_FIELD_VALUE:0012345678 COMMENT: third document starts at byte 16248 GROUP_OFFSET:16248 COMMENT: document length 8124 bytes GROUP_LENGTH:8124 COMMENT: use prior GROUP_FILENAME: GROUP_FILENAME: COMMENT: COMMENT: End Generic Indexer Example 2 6.6.13 Page 226. FIELD parameter. Change the second sentence in the first paragraph. You can define up to 32 (thirty two) index fields. 6.6.14 Page 231 - 232. INDEXSTARTBY parameter. The INDEXSTARTBY parameter determines the page number by which the first group (document within the input file) must be found. The first group is identified when *all* of the triggers and fields are found. For example: TRIGGER1 = ul(4.72,1.28), lr(5.36,1.45), *, 'ACCOUNT' TRIGGER2 = ul(6.11,1.43), lr(6.79,1.59),1,'SUMMARY' INDEX1 = 'Account',FIELD1,FIELD2, FIELD1 = ul(6.11,1.29), lr(6.63,1.45),2 FIELD2 = ul(6.69,1.29), lr(7.04,1.45),2 INDEX2 = 'Total',FIELD3 FIELD3 = ul(6.11,1.43), lr(6.79,1.59),2 INDEXSTARTBY = 3 The word ACCOUNT must be found on a page in the location described by TRIGGER1. The word SUMMARY must be found on the page following the page where ACCOUNT was located, in the location described by TRIGGER2. In addition, there must be one or more words found for fields FIELD1, FIELD2, and FIELD3 in the locations described by FIELD1, FIELD2, and FIELD3 which are located on a page that is two pages after the page where TRIGGER1 was found. In the example, the first group in the file must start on either page 1, page 2, or page 3. If TRIGGER1 is found on page 1, TRIGGER2 must be found on page 2, and FIELD1, FIELD2, FIELD3, must be satisfied on page 3. 6.6.15 Page 235. TEMPDIR parameter. On Windows NT servers, the default drive for the temporary directory is C. If you do not specify the TEMPDIR parameter, the default drive and directory is C:\TEMP. 6.6.16 Page 236. The page variable of the TRIGGER parameter. Replace the description of the page variable with the following: The page number in the input file on which the trigger must be located: o For TRIGGER1, the page value must be * (asterisk), to specify that the trigger can be located on any page in the input file. The PDF Indexer begins searching on the first page in the input file. The PDF Indexer continues searching until the trigger string value is located, the INDEXSTARTBY value is reached, or the last page of the input file is searched, whichever occurs first. (If the PDF Indexer reaches the INDEXSTARTBY value or the last page and the trigger string value is not found, then an error occurs and indexing stops.) o For all other triggers, the page value can be 0 (zero) to 16, relative to TRIGGER1. For example, the page value 0 (zero) means that the trigger is located on the same page that contains TRIGGER1; the value 1 (one) means that the trigger is located on the page after the page that contains TRIGGER1; and so forth. (For TRIGGER2 through TRIGGER16, the trigger string value can be a maximum of 16 pages from TRIGGER1.) 6.6.17 Page 248. -t temp_dir. On Windows NT servers, the default drive for temporary files is C. If you do not specify the -t parameter, the default drive and directory for temporary files is C:\TMP. ----------- end of corrections to S544-5489-05 --------------------------------- 6.7 IBM EDMSuite OnDemand: Getting Started with the Administrative Client, S544-5463-08 NOTE: For the latest technical updates to the administrative client, please see the online Help. 6.7.1 ADSTAR Distributed Storage Manager (ADSM) is now known as Tivoli Storage Manager (TSM). 6.7.2 Page xviii. Related documentation: o ADSM has been replaced by TSM. You can find copies of the TSM publications on the TSM On-line Library CD-ROM. o DB2 UDB V6.1 is now supported. You can find copies of the latest DB2 publications on the DB2 server CD-ROM. 6.7.3 Page 3. Hardware. The administrative client requires a PC with an Intel Pentium 166 MHz (or faster) processor. 6.7.4 Page 5. Installing from Autorun. The client CD-ROM does not contain the Autorun files. Therefore, you cannot install the client from Autorun. 6.7.5 Page 6. To install on a user's PC. Delete the first sentence. You cannot install the client from Autorun. 6.7.6 Page 7. To use Uninstall. To remove the OnDemand client software from the PC, use the Add/Remove Programs applet in Control Panel. 6.7.7 Page 13. Starting the administrative client. The OnDemand program folder/group has been renamed to IBM OnDemand. 6.7.8 Pages 21 - 23. Administrative client startup parameters. The default client software installation directory is now: \Program Files\IBM\OnDemand32 6.7.9 Page 22. Changing start up parameters. The OnDemand program folder/group has been renamed to IBM OnDemand. ---------- end of corrections to S544-5463-08 ---------------------------------- 6.8 IBM EDMSuite OnDemand: Win32 Client Customization Guide, S544-5466-06 6.8.1 Page 22. Parameters. pDateTime. Change the description to: "Points to a BSTR to receive the date and time for the annotation." 6.8.2 Page 23. Change the last "End if" on the page to "Next j". 6.8.3 Page 28. Parameters. pDateTime. Change the description to: "Points to a string to receive the date and time for the annotation." 6.8.4 Pages 32, 36, 40, 50, 63, 66, and 100. Change "var.lVal" to "vari.lVal". 6.8.5 Pages 36, 49, 56, 60, 63, 66, 73, 76, 81, 85, 96, 100, 104, 120, and 132. Change "var.iVal" to "vari.iVal". 6.8.6 Page 53. Change the statement "var.vt = VT_ARRAY ] VT_BSTR" to "var.vt = VT_ARRAY | VT_BSTR". 6.8.10 Page 62. Change the last "End if" on the page to "Next j". 6.8.11 Page 107. Example. The example prints page 5 of the open document. 6.8.12 Page 110. Change both occurrences of "C:\FILES\DATA" + count + ".DOC" to "C:\FILES\DATA.DOC" 6.8.13 Page 126. Example. C/C++ Example. Change SetDocBackgroundColor to SetDocImageColor. 6.8.14 Page 138. Example. C/C++ Example. In the rc statement, change VARIANT to &var. 6.8.15 Page 217. Example. Change the string "25,0,75,100" to "/W 25,0,75,100" ---------- end of corrections to S544-5466-06 ---------------------------------- 6.9 IBM EDMSuite OnDemand: OS/2 Client Customization Guide, S544-5465-03 6.9.1 Page 5. In the example for Product Title, change the value for the /T parameter to "Joe's OS//2 Application". 6.9.2 Page 11. Change the parameter value in the first occurrence of the WinMessageBox call from "MB_OK ] MB_ERROR" to "MB_OK | MB_ERROR". 6.9.3 Page 14. Change the second parameter of the WinMessageBox command from "hwndFrame" to "hwnd". 6.9.4 Pages 21, 22, 24 - 31, 33 - 39, 41 - 50, 52, 56, 59, 60, 62 - 64, 66 - 70, 72, and 73. In the Example, add "hwnd, " as the first parameter of the DoDdeCommand. 6.9.5 Page 24. The parameters for the sprintf command should be: sprintf ( parms, "/N %s /P %s /G 2", "22", "d:\arsdata\annot.txt" ); 6.9.6 Page 24. In the DoDdeCommand, change "PRINT_DOC" to "ANNOTATE_DOC". 6.9.7 Page 37. In the example, change the value of the /C parameter in the sprintf statement to "Fred's OS//2 Application". 6.9.8 Page 41. In the example, change the value of the second parameter in the DoDdeCommand to "/N 8". 6.9.9 Page 45. In the example, remove the period following GET_NUM_DOC_PAGES. 6.9.10 Page 68. In the example, change the value of the second parameter in the DoDdeCommand to "/P C:\DDEAPPL\DDEAPPL.HLP". 6.9.11 Page 70. In the example, change the value of the second parameter in the DoDdeCommand to "/W 25,0,75,100". 6.9.12 Page 72. In the example, change the value of the next to last parameter in the sprintf statement to "05//23//95". ---------- end of corrections to S544-5465-03 ---------------------------------- ----------------- end of Documentation Corrections ----------------------------- 7. Configuring OnDemand to work with Oracle -------------------------------------------------------------------------------- Beginning with OnDemand Version 2.2.1.6, Oracle 8i (8.1.5.0) is supported as a database manager for the OnDemand database. The following information can help you configure OnDemand to work with Oracle. NOTE: You must be an experienced Oracle database administrator to configure OnDemand to work with Oracle. 1) Configure OnDemand (UNIX) A. Set the name of the database in the ars.ini file. For example: [@SRV@_ARCHIVE] SRVR_INSTANCE=ARCHIVE In the example, the name of the OnDemand instance and the name of the database is ARCHIVE. B. Set Oracle as the database manager in the ars.cfg file. The default value is: DB_ENGINE=DB2 Change the value to: DB_ENGINE=ORACLE C. Add the following parameter to the ars.cfg file: ARS_ORACLE_HOME= Replace with the base installation directory for Oracle. For example: ARS_ORACLE_HOME=/oracle (WinNT) Use the OnDemand configurator program to define the OnDemand instance and use Oracle as the database manager. The name of the OnDemand instance and the name of the database must be the same. 2) Configure Oracle and OnDemand database logon processing (UNIX) OnDemand runs as root under UNIX. You must do one of the following to configure OnDemand to work with Oracle: o Add the following variable to the Oracle instance file (for example, init.ora): remote_os_authent = true o Add the following parameters to the ars.cfg file: ARS_ORACLE_USERID=root ARS_ORACLE_PASSWD= ; GRANT dba TO root ; (WinNT) Create the user as follows: CREATE USER IDENTIFIED EXTERNALLY ; GRANT dba TO ; Replace with the userid that you used to create the OnDemand instance (from the OnDemand configurator program). All tables created by OnDemand will be owned by the user that you create. If you wish to have a default Oracle table space for the user, then you should specify the table space when you create the user. 5) Integrate OnDemand with the Oracle shared library. You must configure the following so that the OnDemand commands can run with Oracle: (AIX) /lib/libclntsh.a Either create a link to the shared library in the /usr/lib directory: cd /usr/lib ln -s /lib/libclntsh.a . or set the following variable: LIBPATH=/lib (HPUX) /lib/libclntsh.sl Either create a link to the shared library in the /usr/lib directory: cd /usr/lib ln -s /lib/libclntsh.sl . ln -s /lib/libclntsh.sl.8.0 . or set the following variable: SHLIB_PATH=/lib (SunOS) /lib/libclntsh.so Either create a link to the shared library in the /usr/lib directory: cd /usr/lib ln -s /lib/libclntsh.so . ln -s /lib/libclntsh.so.8.0 . or set the following variable: LD_LIBRARY_PATH=/lib (WinNT) /bin/oci.dll Oracle adds the /bin directory to the PATH during installation. You should not have to add the directory to the PATH. (However, you can verify that the directory is in the PATH.) 6) Create OnDemand system tables. Run the following command: arsdb -I -rtv 7) Initialize the OnDemand System Log and System Migration facilities. Run the following commands: arsssycr -I -l arsssycr -I -m After you successfully create and initialize the database, you will need to use standard Oracle procedures to start, stop, and optimize the database, to make backup copies of the database, and so forth. In addition, some of the other options for the arsdb command do not apply when using Oracle with OnDemand. The following options of the arsdb command are not valid when you use Oracle with OnDemand: arsdb -g (Start the database......use the Oracle procedures instead) arsdb -h (Stop the database.......use the Oracle procedures instead) arsdb -k (Activate the database...does not apply to Oracle) arsdb -l (Import/Export Format....does not apply to Oracle) arsdb -m (Reorg...................does not apply to Oracle) arsdb -y (Backup..................use the Oracle procedures instead) arsdb -z (Backup..................use the Oracle procedures instead) arsdb -Y (Backup..................use the Oracle procedures instead) arsdb -Z (Backup..................use the Oracle procedures instead) ------------------end of Oracle Instructions------------------------------------