################################################################################ # IBM EDMSuite OnDemand # # AIX, HP-UX, Solaris, Windows NT # # README # # Release 2.2.1.0 # # June 14, 1999 # # # # 5622-662, 5765-D60, 5765-E20 5639-E12 (C) COPYRIGHT IBM CORPORATION 1999 # # 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. ================================================================================ 1. Contents 2. Server Change History 2.1 AIX Server 2.1.2.2.1.0 Release/PTF (2.2.1.0) 2.2 HP-UX Server 2.2.2.2.1.0 Release/PTF (2.2.1.0) 2.3 Solaris Server 2.3.2.2.1.0 Release (2.2.1.0) 2.4 Windows NT Server 2.4.2.2.1.0 Release/PTF (2.2.1.0) 3. Client Change History 3.1 OS/2 Client 3.1.2.2.1.0 Release/PTF (2.2.1.0) 3.2 Windows 3.1 Client 3.2.2.2.1.0 Release/PTF (2.2.1.0) 3.3 Windows 32-bit Client 3.3.2.2.1.0 Release/PTF (2.2.1.0) 3.4 Windows 32-bit Administrator 3.4.2.2.1.0 Release/PTF (2.2.1.0) 4. Upgrade Instructions for 2.2.1.0 5. Client/Server Backward Compatibility 6. Documentation Corrections ------------------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 --------------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 --------------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 --------------end of Windows NT 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 --------------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) --------------end of OS/2 Client------------------------------------------------ 3.2 Windows 3.1 Client 3.2.2.2.1.0 Release/PTF (2.2.1.0) --------------end of Windows 3.1 Client----------------------------------------- 3.3 Windows 32-bit Client 3.3.2.2.1.0 Release/PTF (2.2.1.0) --------------end of Windows 32-bit Client-------------------------------------- 3.4 Windows 32-bit Administrator 3.4.2.2.1.0 Release/PTF (2.2.1.0) --------------end of Windows 32-bit Administrator------------------------------- ------------------end of Client Change History---------------------------------- 4. Upgrade Instructions for 2.2.1.0 -------------------------------------------------------------------------------- OnDemand Version 2.2.1.0 adds the following enhancements: NOTE: Please see Section 5, Client/Server Backward Compatibility - Support for loading files up to 4GB in size. (Previous limitation was 2GB. PDF Indexer continues to support files up to 2GB.) - Support for 64-bit integers as a datatype. To support the 64-bit integer datatype, 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 datatype: - All clients older than version 2.2.1.0 - Windows 3.1 Client - CICS Client (Service Offering) - Ad-Hoc Data Distribution (16bit and 32bit) (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. OS2, 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. 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-100MB). 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 datatype, both the clients and server must be at version 2.2.1.0 or later. ------------------end of Client/Server Backward compatibility------------------- 6. Documentation Corrections -------------------------------------------------------------------------------- The latest revisions of the US English versions of the OnDemand publications are available in PDF format on the IBM web site: http://www.software.ibm.com/data/ondemand/library.html 6.1 IBM EDMSuite OnDemand: Indexing Reference, S544-5489-05 6.1.1 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. ----------- end of corrections to S544-5489-05 --------------------------------- 6.2 IBM EDMSuite OnDemand: Installation Guide for UNIX Servers, G544-5598-01 6.2.1 Page 28. Configuration Notes. Add the following item to the list: 5. For Solaris servers, create a link to the DB2 shared libraries. Enter the following commands: cd /lib ln -s /opt/IBMdb2/V5.0/lib/libdb2.so.1 . 6.2.2 Pages 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 ADSM 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 ADSM (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. (The OnDemand instance owner is archive, by default.) 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 DSM_CONFIG and DSMI_CONFIG environment variables. These variables contain the full path name of the options file ADSM 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 DSM_CONFIG=/usr/lpp/adsm/bin/dsm.opt.db2 export DSMI_CONFIG=/usr/lpp/adsm/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 ADSM (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 ADSM, remember to run the dsmapipw command to set the new password in DB2. ---------- end of corrections to G544-5598-01 ---------------------------------- 6.3 IBM EDMSuite OnDemand: Installation Guide for Windows NT Servers, G544-5526-05 6.3.1 Page 34. Verify Server and Client Options, second paragraph. Add NOPREEMPT to the server options file. This parameter makes sure that mount requests cannot be preempted by other commands (except for the backup database command). 6.3.2 Page 39. Item 3. In the device class statement, change format=2600 to format=2600MB. 6.3.3 Page 49. Change the first sentence from "You must set the COMPRESS parameter to yes." to "You must set the COMPRESSION parameter to yes." 6.3.4 Page 49. Change the "COMPRESS yes" parameter and value pair in the sample dsm.opt.db2 file to COMPRESSION yes. 6.3.5 Pages 51 - 52. 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 ADSM 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 ADSM (see Registering the DB2 client node on page 51). Use the dsmapipw command to set the client node password in DB2. The dsmapipw command is installed in the \sqllib\adsm directory. To set the client node password: 1. On the library server, log on with the OnDemand system administrator account. 2. Start a command prompt. 3. Set the DSM_CONFIG and DSMI_CONFIG environment variables. These variables contain the full path name of the options file ADSM uses to identify the server that maintains the DB2 files. (You created the options file in Configuring client options on page 48.) For example: set DSM_CONFIG=d:\adsmv3\baclient\dsm.opt.db2 set DSMI_CONFIG=d:\adsmv3\baclient\dsm.opt.db2 4. Run the dsmapipw command. For example: \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 ADSM (see Registering the DB2 client node on page 51). 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. Exit the command prompt. 7. If DB2 is running, you should stop and restart DB2. Important: If you change the client node password in ADSM, remember to run the dsmapipw command to set the new password in DB2. 6.3.6 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.7 Page 111. PDF indexer. The Acrobat software is distributed on the OnDemand product CD-ROM. Use the setup.exe program to install the software. The setup program is located in the \adobe\win\acrobat3 directory. When prompted for the product serial number, use the serial number provided by IBM (listed in the README.TXT file found in the root directory of the product CD-ROM). You may install the Acrobat Distiller software on any OnDemand library or object server for which you hold a license. 6.3.8 Page 112. Item 5 (Configuring Acrobat distilling software). To configure the Distiller to delete input files from the IN directory rather than moving them to the OUT directory after successfully distilling a file, open the Watched Folders dialog box and select "After Distilling, the PostScript file should be: Deleted". ---------- end of corrections to G544-5526-05 ---------------------------------- ----------------- end of Documentation Corrections -----------------------------