IBM. Read This First. IBM Content Manager OnDemand for iseries

Transcription

1 IBM Content Manager OnDemand for iseries IBM Read This First Notice This document applies to the IBM Content Manager OnDemand for iseries Version 5 Release 2, Program Number 5722-RD1, for all language feature codes. The information in this document supplements the current level of available product publications for this release. Date last updated: September 9, 2005

2 Copyright International Business Machines Corporation All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Read This First Before you install IBM Content Manager OnDemand for iseries (CM OnDemand) V5R2, you should read this document, which contains additional information that you need to know. Most importantly, read page 4 through page 6. The information on these pages is required for successful installation of this product. Trademarks The following terms are trademarks of the IBM Corporation in the United States or other countries: IBM iseries Page 3 of 22

4 SUMMARY OF CHANGES This document is the most current version of the Read This First document that ships with Content Manager OnDemand for iseries Version 5 Release 2. It contains new and changed information related to the topics listed. September 9, 2005 edition: IMPORTANT NOTICES for All Customers Added statement regarding support for UDF-formatted optical volumes. Corrections to CM OnDemand V5R2 Publications Added information regarding maximum input file size for Common Server (including a statement about PDF Indexer). May 6, 2005 edition: Additional Details on Documented Functions Cache Only - Library Server storage set no longer created for new Common Server instances after PTF SI14169 is applied September 12, 2003 edition: IMPORTANT NOTICES for All Customers IMPORTANT information for CommonStore customers regarding the locale PTFs May 15, 2003 edition: IMPORTANT NOTICES for All Customers New server release (level ) for Common Server now available Important, MANDATORY locale specification process REQUIRED for all Common Server customers Special installation instructions for Japanese Common Server customers Recommendations Choice of job description when starting the output queue monitor from a job scheduler Additional Common Server ARS.CFG entry to consider if using DHCP Additional Details on Documented Functions Additional information on deleting a Common Server instance Page 4 of 22

5 SUMMARY OF CHANGES (continued) January 17, 2003 edition: IMPORTANT NOTICES for All Customers New server release (level ) for Common Server now available Important, MANDATORY index data correction process REQUIRED for all Common Server customers Updated Client software required for Common Server; optional for Spool File Archive users New Product Functions Available After Publications Deadline How to specify multi-key indexes in Common Server How to specify transaction fields for sorted listing reports in Common Server (similar to PAGE reports in Spool File Archive) Report Wizard now supports specification of application identifier database and displayed values Additional Details on Documented Functions Change in default job queue for QOND400 job description How to change your archive media choices after you've archived data in Common Server Mapping AFP fonts for multi-byte languages How to define data with Shift Out/Shift In (SOSI) characters in Common Server Additional information and parameters available for ARSDOC API Additional information and parameters available for ARSLOAD API Customizing the administrative client to handle exporting definitions between local and non-local servers Using the Spool File Archive Combine report occurrences function with Content Manager, VisualInfo, or ImagePlus WAF Integration How to delete a particular set of objects from Object Archive Corrections to CM OnDemand V5R2 Publications Clarification of QRDARSADM and QONDADM group profiles for Common Server administrators Maximum size of Group and Server Queue names increased Correction to RSCF0200 Format for Spool File Archive s Retrieve Archived Resource API Complete List of CM OnDemand V5R2 Publications August 30, 2002 edition: IMPORTANT NOTICES for All Customers Information APAR available for list of current CM OnDemand V5R2 PTFs Importance of getting current on PTFs Check out the most current updates to this document Page 5 of 22

6 IMPORTANT NOTICES for All Customers All customers please read the following topics for important information regarding your CM OnDemand V5R2 software. Information APAR available for list of current CM OnDemand V5R2 PTFs An information APAR is available that contains both a list of current (non-superseded) PTFs as well as a list of ALL V5R2 PTFs for OnDemand. The information APAR number is II You can review this information APAR on the web at Importance of getting current on PTFs It is imperative that you review the information APAR listed above and load and apply all PTFs that relate to the product options you have installed. Some V5R2 PTFs will be created after the cutoff date for the general availability (GA) cumulative PTF package, and therefore there will be critical PTFs that you are missing until you load and apply all current PTFs (above and beyond what is included in the cumulative package). New server release (level ) for Common Server now available A new release of the server code for Common Server is now available via PTFs for your iseries system. PTFs SI08157, SI08158, and SI08159 provide the update. Note: These are the same PTFs as described below for the mandatory locale specifications. The locale code is shipped with the new server code due to their interdependence. These PTFs supersede the PTFs described below for the server update that became available in January, Important, MANDATORY locale specification process REQUIRED for all Common Server customers PTFs SI08157, SI08158, and SI08159 provide an important update to OnDemand Common Server, allowing the specification of locale information, which is now mandatory for all Common Server customers. Full instructions are provided at the following web site: Limited instructions are also included in the Special Instructions section of the SI08159 PTF cover letter, but should be used only if you are unable to obtain the full instructions from the internet. It is important to understand and perform these instructions completely, AND to understand that your CM OnDemand Common Server system will be UNAVAILABLE as soon as you apply these PTFs. The steps outlined in the instructions will need to be completed before you can successfully restart the servers for your Common Server environment. Note: These are the same PTFs as described above for the new server release. The new server software is shipped with the locale specification updates due to their interdependence. This does NOT imply, however, that you can ignore the locale specification instructions if you choose not to upgrade to the new server. ALL Common Server customers must follow the locale specification instructions; the upgraded server is an added benefit of performing the mandatory locale specification steps. Note that these PTFs supersede the PTFs for index data correction that were available in January, 2003, and require that you complete the index data correction steps prior to performing the steps outlined in the locale instructions. Page 6 of 22

7 IMPORTANT information for CommonStore customers regarding the locale PTFs Please note that the internal interface between CommonStore and CM OnDemand does not give a warning if you install the locale PTFs described above and then store data without setting the locale information. It is very important that you follow the instructions for the locale PTFs as described above and set the proper locale values after applying the locale PTFs and before storing any data. Special installation instructions for Japanese Common Server customers When installing the Common Server product option (5722-RD1 option 10), the job which is performing the installation must be running in CCSID 5035 or the creation of the QUSROND default instance will fail. To change the CCSID of your job execute the following command: CHGJOB LANGID(JPN) CNTRYID(JP) CCSID(5035) Once the CCSID of the job has been changed to 5035, install the OnDemand Common Server product option following the instructions in the IBM Content Manager OnDemand for iseries Common Server Installation and Planning Guide. New server release (level ) for Common Server available January, 2003 A new release of the server code for Common Server is now available via PTFs for your iseries system. HIPER PTF SI06587 (along with corequisite PTFs SI06287 and SI06581 and prerequisite PTF SI07038), provide the update. Note: These are the same PTFs as described below for the mandatory index data correction. The correction programs are shipped with the new server software due to their interdependence. Important, MANDATORY index data correction process REQUIRED for all Common Server customers; Available January, 2003 HIPER PTF SI06587 (along with corequisite PTFs SI06287 and SI06581 and prerequisite PTF SI07038), provide an important set of index data correction programs that are mandatory for all Common Server customers. Full instructions are provided at the following web site: Limited instructions are also included in the Special Instructions section of the SI06587 PTF cover letter, but should be used only if you are unable to obtain the full instructions from the internet. It is important to understand these instructions fully before running the correction programs. It is also important to understand that your CM OnDemand Common Server system will be UNAVAILABLE as soon as you apply these PTFs. The correction process will need to be completed before you can successfully restart the server for your Common Server environment. Even new installations must complete the process described in the instructions, although the process need only be performed on the default QUSROND instance and will run very quickly due to the absence of any archived data. Note: These are the same PTFs as described above for the new server release. The new server software is shipped with the correction programs due to their interdependence. This does NOT imply, however, that you can ignore the correction programs if you choose not to upgrade to the new server. ALL Common Server customers must run the correction programs; the upgraded server is an added benefit of running the mandatory correction programs. Page 7 of 22

8 Updated Client software required for Common Server; optional for Spool File Archive users Customers installing the new Common Server software need to install the end-user OnDemand Client software on all end-user workstations as well as the OnDemand Administrator Client software on a limited number of workstations for those users who will perform administrative functions for OnDemand. A CD-ROM containing both Clients is shipped with all OnDemand V5R2 Server feature orders. However, the Common Server Administrator Client users must update their Administrator Client software to the level or higher for use with OnDemand for iseries V5R2 Common Server. If the CD-ROM that you receive contains Client software at a level below , you must update the Administrator Client software from the Internet. (The end-user client software does not need to be updated, but can be updated if desired for use with both the new Common Server and the current Client/Server software for Spool File Archive, since enhancements have been added at this new level.) To download the OnDemand Clients, go to the internet FTP web site at ftp://service.software.ibm.com/software/ondemand/fixes/v71/ Both the Administrator and end-user Clients are packaged together in a file named odwin32.zip. Download the file from this FTP site and then unzip it into a temporary directory. Then double click the setup.exe file and follow the instructions on the resulting panels. Note: When you upgrade to the new level of Common Server described elsewhere in this document, it is recommended that you upgrade your administrative and end-user Client levels to or higher, since the level of the Clients provide fixes and additional function that can be used with the new Common Server. Also note: If you upgrade the end-user Client, you may lose font customizations you have made on the workstation. See the CM OnDemand for iseries Common Server Planning and Installation Guide for details regarding the method to backup your customized font files prior to upgrading. UDF-formatted optical volume support CM OnDemand Common Server does support UDF-formatted optical volumes. CM OnDemand Spool File Archive, Object Archive, Record Archive, and AnyStore do not support UDF-formatted optical volumes. Check out the most current updates to this document See the latest version of this document on the CM OnDemand web site at Page 8 of 22

9 New Product Functions Available After Publications Deadline The following information on new product functions became available after the OnDemand publications deadline. How to specify multi-key indexes in Common Server Multi-key indexes can be used when an index value occurs multiple times within a single document. For example, invoices might have invoice number, customer number, and customer name defined as the first three index fields, each occurring once within a given invoice. Then you might also want to define item number as a multi-key index, since there might be multiple item numbers within one invoice. With multi-key, an end-user could search by item number to find any invoice for a given item number, no matter where that item number appeared in the list of invoiced items. Without the multi-key capability, only the first item number on the page would be indexed. To enable multi-key indexing, the keyword ALLOWMULTIPLEVALUES=YES must be added to each INDEX statement that is to have multiple values captured per document. For example: INDEX2=X' ',FIELD2,(TYPE=GROUP,BREAK=NO,ALLOWMULTIPLEVALUES=YES) The ALLOWMULTIPLEVALUES=YES specification would be added to the OnDemand Application definition. Go to the Indexer Information tab, then click on Keyboard and then Modify to edit the Application's Indexer Parameters. Note that this new keyword ALLOWMULTIPLEVALUES is only valid when BREAK=NO. A more detailed explanation with examples, including screen shots, is part of a PDF version of the OnDemand for iseries and AS/400 Bulletin # 17 and will be included in the next release publications. If you are not on the distribution list for this bulletin and would like to be, please contact your OnDemand support representative or visit the OnDemand support web page and search for the bulletin at How to specify transaction fields for sorted listing reports in Common Server (similar to PAGE reports in Spool File Archive) A transaction report contains pages of records with one or more columns of sorted data. For example, each page of a general ledger report might contain up to 80 transaction detail lines. Each line contains a unique value, such as a transaction number. The lines of the report are sorted on the transaction number. Rather than storing every transaction number in the database using a multi-key index (perhaps hundreds of thousands of rows), you can break the report into groups of pages (say, 100 pages in a group), extract the beginning and ending transaction number for each group of pages, and store the values in the index database. Then, to retrieve the group of the report that contains a specific transaction number, a user enters a transaction number. OnDemand compares the transaction number with the beginning and ending values stored in the database and retrieves the group that matches the query. To define a transaction report that contains one or more columns of sorted data as described in the example, a transaction field is used. A transaction field allows OnDemand to index a group of pages using the first index value on the first page and the last index value on the last page. The easiest method of specifying a transaction field is to use the report wizard and graphical indexer. The indexer parameter for the transaction field will look similar to the following: Page 9 of 22

10 FIELD1=*,*,10,(OFFSET=(3:12),MASK='##########',ORDER=BYCOL) The indexer parameter for the index created from the transaction field will look similar to the following. INDEX1=X'D ',FIELD1,(TYPE=GROUPRANGE,BREAK=NO) These indexer parameters would be added by the report wizard to the OnDemand Application definition. To see them, go to the Indexer Information tab, then click on Keyboard and then Modify to view the Application's Indexer Parameters. A more detailed explanation with examples, including screen shots, is part of a PDF version of the OnDemand for iseries and AS/400 Bulletins for 2002 and will be included in the next release publications. If you are not on the distribution list for this bulletin and would like to be, please contact your OnDemand support representative or visit the OnDemand support web page and search for the bulletins at Report Wizard now supports specification of application identifier database and displayed values With the level or higher of the OnDemand Administrator Client, fields for Displayed Value and Database Value have been added to the Application Identifier page of the Report Wizard. On the Report Wizard page that asks Do you want to be able to add other applications to the application group?, you can now specify the actual displayed value and database value of the application that you are defining. These values will be added to the application group in the Name Mapping section and the Database Value will be used as the Identifier for the application that is being created. Page 10 of 22

11 Recommendations Please follow the recommendations in this section when using OnDemand. Choice of job description when starting the output queue monitor from a job scheduler When starting an OnDemand output queue monitor (STRMONRDAR command for Spool File Archive or STRMONOND command for Common Server) from a job scheduler, you may be unsure of which job description to use. In most cases, STRMONRDAR will work best using the QRDARS400 job description and STRMONOND will work best using the QOND400 job description. Note that you may have special system needs that require the use of your own job description, but these two IBM-supplied job descriptions will work successfully for many customers. Additional Common Server ARS.CFG entry to consider if using DHCP Some OnDemand Client users may experience longer than normal logon times when using DHCP to assign the TCP/IP addresses for their workstations. In these cases, making the change described below to the ARS.CFG file may correct the problem. The ARS.CFG file is located down the /QIBM/UserData/OnDemand/<instance> path in IFS on your iseries server. For the default OnDemand instance named QUSROND, the file would be located at /QIBM/UserData/OnDemand/QUSROND/ars.cfg If you create a new instance called TEST, the ARS.CFG file for it would be located at /QIBM/UserData/OnDemand/TEST/ars.cfg If you are experiencing longer than normal logon response times in a DHCP environment: 1) ENDTCPSVR *ONDMD to end the server jobs. 2) Enter WRKLNK '/qibm/userdata/ondemand/qusrond/ars.cfg' and select option 2 - edit on ARS.CFG --> do this for all your instances by replacing qusrond with your instance name. 3) Add the following statement as the last statement in ARS.CFG: ARSSOCK_RESOLVE_CLIENT_NAME=0 4) STRTCPSVR *ONDMD to restart the server jobs. Page 11 of 22

12 Additional Details on Documented Functions The following detail supplements information already found in the V5R2 publications. Cache Only - Library Server storage set no longer created for new Common Server instances after PTF SI14169 is applied After you apply OnDemand PTF SI14169, creating a new Common Server instance will not create the "Cache Only - Library Server" storage set as had been done previously. The "Cache Only - Library Server" storage set has some limitations that development hopes to avoid by no longer making it available for new instances. Existing instances that are already using the "Cache Only - Library Server" storage set can continue to do so even after applying this PTF. If you wish to set up your archive media as "cache only," you should consider using disk pool media rather than setting up a "cache only" environment, since defining a disk pool storage level will allow you to add optical or tape storage level(s) later. Additional information on deleting a Common Server instance In addition to the information provided in the Common Server Planning and Installation Guide regarding the process for deleting an instance, please note the following two points: If the server for the instance is already started, you must end the server before deleting the instance. You can end a specific server by issuing the following command (noting no space between *ENDTCPSVR and instance_name): CALL QRDARS/QRLMCTL *ENDTCPSVRinstance_name You can consider deleting the instance user profile (which has a name that matches the instance name), but be careful to verify that the user profile does not own objects that will still be required after the instance is deleted. Change in default job queue for QOND400 job description (CM OnDemand for iseries Common Server Administration Guide) In the base code for V5R2 (and in a PTF for V5R1), the QOND400 job description in library QRDARS was changed to use job queue QSYSNOMAX instead of QBATCH. This may affect all commands (as well as the Common Server jobs) because they all default to using QOND400 job description. This change was made to help customers who have QBATCH job queue set up as single-threaded, which means that only one job can be processed at a time. How to change your archive media choices after you've archived data in Common Server (CM OnDemand for iseries Common Server Administration Guide) If you set up your Common Server application group to only use the default Storage Set Name of "Cache Only - Library Server" with no other storage sets selected, then archived some data, and now desire to have your data move from cache (disk) to another archive media after a specified period of time, consider these important points: 1. You can not simply change the storage set in an application group. However, you can rename the application group and the associated application, then copy the application group back to its original name and change the storage group during the copy process. Then copy the application back to its original name, specifying that it belongs to the changed application group (which has already been copied back to its original name). Change the folder so that it also points back to the original application group. (When you renamed the application group above, the associated applications and folders were automatically updated to use the new name. But now you want the folder to point to both application groups.) Page 12 of 22

13 Note that if you are using the output queue monitor to automate the archiving of spooled files, it is especially important that you follow these instructions to preserve the original application group name to match it with a value on the STRMONOND command. The process just described will cause any FUTURE archives to use the modified storage set, but will not change anything for data that has already been archived. 2. If you need to move all the EXISTING archived reports to optical or other media (in addition to changing the way your FUTURE archives are processed), you will need to re-spool, delete, and re-archive them. The easiest way to do this is: 1. Use the System Log to determine the load id of each report you need to re-spool. 2. Use the Administrator Client to add a server printer. 3. Issue the PRTRPTOND command to recreate the spooled files and place them in the output queue of the server printer. 4. Follow the steps outlined above to change the storage set defined in the application group. 5. Re-archive the spooled files. 6. Delete the application group with the "temporary" name that you used during the rename step (which also deletes the application AND the actual archived data) -- just make sure you have re-spooled and re-archived everything first! You may prefer to use the OnDemand end-user Client to print all the documents to a server printer, instead of determining the load id and using the PRTRPTOND command. An example of the second process (which moves EXISTING archived reports) may help to explain the steps: Re-spool all the ABC reports to an output queue. Then rename the application group from ABC to ABC1. Then rename the application to ABC1. Then copy the ABC1 application group back to ABC, changing the Storage Set information during the copy. Then copy the ABC1 application back to ABC. Archive everything as ABC. Then, at the end, delete the ABC1 application group. That will delete the ABC1 application group and application and ALSO all the data, which cleans up the old data that you just re-spooled and re-archived. Mapping AFP fonts for multi-byte languages (CM OnDemand Common Server Planning and Installation Guide) IBM provides font definition files for the following multi-byte languages: Japanese CODED.JPN and CSDEF.JPN Korean CODED.KOR and CSDEF.KOR Simplified Chinese CODED.CHS and CSDEF.CHS Traditional Chinese CODED.CHT and CSDEF.CHT For example, for Japanese, if a font is listed in the CSDEF.JPN file, it will be supported in the AFP viewer. The actual font mapping from AFP font to Windows font happens in the [FGID] section of the CSDEF.JPN file. (The [FGID] section is at the end of the file.) If a font is not listed in the CSDEF.JPN file, you can add the font by editing the CSDEF.JPN file with a standard text editor. See the Windows Client Customization Guide for details about how to map AFP Fonts. How to define data with Shift Out/Shift In (SOSI) characters in Common Server (CM OnDemand for iseries Common Server Planning and Installation Guide) Appendix B of the CM OnDemand Common Server Planning and Installation Guide addresses numerous considerations for National Language Support (NLS), including a discussion of Shift Out/Shift In (SOSI) characters. Page 13 of 22

14 If your data contains SOSI characters, you may need to update your OnDemand application definition. To do this, you will need to use the Update function after the application has been created. (The Report Wizard does not provide options for SOSI characters.) 1) After you create the application group, application, and folder using the Report Wizard or by creating each one individually, use the Update function on the particular application. Go to the View Information tab, and select PR Mode (default is None; or choose SOSI1, SOSI2, SOSI3). You will need to upgrade your OnDemand Administrator Client software to the level or above in order to work with these parameters. (See the previous entry in this document for instructions on updating your client software.) 2) As is stated in Appendix B under Indexing, you may need to modify the starting and ending columns and column width values generated by the graphical indexer. To do this, go to Indexer Information tab within the application definition. Under Parameters Source, click on Keyboard and then press the Modify button so that you can edit your Indexer parameters. Additional information and parameters available for ARSDOC API (CM OnDemand for iseries Common Server Administration Guide) If the folder that is specified with the -f parameter contains only one application group, then you can omit the -g or -G parameter. In other words, you no longer have to specify the name of the application group. When using the ADD and UPDATE functions and specifying field values with the -n parameter: Specify a null (blank) field value by using single quotes within double quotes. For example: -n middle="''" Specify a string field value that contains a null (blank) or other special character by enclosing the field value in single quotes within double quotes. For example: -n name="'sally Smith'" The GET and QUERY functions can now sort the data that is retrieved from the server. The data is sorted by using the Sort field from the Field Information page for the folder. Note: For the GET function, you must specify the n parameter, so that the documents will be returned in the sorted order. A date format string can now be specified with the -S parameter. For example: -S " , ,%m%d%Y" If you do not specify a date format, then the date values must be specified using the Display Format that is set on the Field Information page in the folder. The ARSDOC program now supports the -xloadid parameter. For the GET function, use the -x parameter to limit the documents that can be retrieved to the set of documents that were loaded into the system under the specified loadid. For the QUERY function, use the -x parameter to limit the query to the set of documents that were loaded into the system under the specified loadid. When you specify the -x parameter, use the -f and -G parameters as follows: Specify the -f parameter to search all application groups. You can specify the search using the -i parameter or the -q parameter. Specify the -G parameter to search a specific application group. You must specify the search using the -i parameter. Specify both the -f parameter and the -G parameter. The ARSDOC program will verify that the application group can be searched from the folder. When you specify the -x parameter, you cannot specify the -X parameter. Page 14 of 22

15 The following example shows how to limit a query to the documents that were loaded into the system under a specific load ID. For example, assume that the specified folder could be used to search several application groups; each application group contains more than one application; there are 500,000 documents in the application groups. By using the -x parameter, the query will be limited to the set of documents that was loaded into the system under the specified load ID. Without the -x parameter, the query is run against all 500,000 documents. arsdoc query -h rockies -x FAA f load-scanned-images -q query -o output -v The ARSDOC program now supports the -XloadId parameter. For the GET function, use the -X parameter to retrieve documents by using the index file that was generated for the specified loadid. For the QUERY function, use the -X parameter to build a hit list from the index file that was generated for the specified loadid. When you specify the -X parameter, you must specify the -G parameter and name the application group. When you specify the -X parameter, you cannot specify the -x parameter, or the -i, -q, -S, and -f parameters. The following example shows how to use an index file to retrieve documents from the system. The index file was generated for the set of documents that was loaded into the system under the specified load ID. When using the -X parameter, the database is not queried; rather, documents are retrieved based on the information in the index file. arsdoc get -h rockies -X FAA G load-scanned-images-jpeg -o jpeg -v Additional information and parameters available for ARSLOAD API (CM OnDemand for iseries Common Server Administration Guide) The ARSLOAD program supports the I parameter. Use the I parameter to identify the instance of OnDemand that you want to process. You must use the I parameter to identify the instance if: The name of the default instance is not QUSROND. You are running more than one instance on the same server and you want to process an instance other than the default instance. The syntax diagram in the current V5R2 publication shows the -X parameter as a required parameter. The -X parameter is optional and is used only to specify an Indexer that is different than the Indexer that is specified on the Indexing Information page. Customizing the administrative client to handle exporting definitions between local and non-local servers (CM OnDemand Common Server Administration Guide) OnDemand supports two types of servers. The first type of server uses TCP/IP to communicate between the client programs and the server programs. The server programs can run on operating systems, such as AIX, HP-UX, OS/400, Sun Solaris, Windows, z/os and OS/390. Depending on the server operating system, the databases supported by the server can be DB2, Oracle (AIX, HP-UX, Sun Solaris, Windows platforms only), and Microsoft SQL server (Windows platform only). Definitions of users, groups, applications, for example, are stored in the database as well as the index values for the report data that is loaded into the system. The second type of server is a local server. The local server is self-contained (no TCP/IP communication) and is defined using files contained in a directory located on a PC rather than in a server database. The files represent the system tables that define the various objects such as users, groups, and applications. One of the uses of a local server is to provide the ability to export definitions from a non-local server to a local server so the definitions can then be imported to a different non-local server. This is especially beneficial when a Page 15 of 22

16 TCP/IP connection does not exist between two non-local servers. One of the limitations of exporting definitions from a non-local server to a local server is that the local server does not support any of the operating system-specific or database-specific parameters that are defined when using the administrative client. When a user logs on to a server, the administrative client determines whether the user has logged on to a local server or a non-local server. If the server is a non-local server, the operating system and the database types are determined. Based on the type of server, the operating system, and the database, default settings are established, entry fields are hidden or displayed, and values are added to or removed from selection lists. For definitions that have been exported from a non-local server to a local server, updating or viewing the definitions may not have the desired results because of the operating system differences between local and non-local servers. For example, when an application group and application are exported from an OS/400 server to a local server, the OS/400 indexer that is specified in the application is not supported on a local server. When the application is viewed on the local server, the Indexer field on the Indexer Information page will not have a value and the OS/400 Indexer will not be listed as a choice of indexers. To correctly display the operating system- and database-specific parameters on a local server from parameters that have been exported from a non-local server, two string values can be added to the local server definition in the Windows Registry on the local server workstation. (Note that the prerequisite for this support is a CM OnDemand Administrator Client at the level or higher.) The string values identify the operating system and the database. Then, when a user logs on to the local server from the administrative client, the server definitions will resemble and operate like a non-local server for the specified operating system and database. In the case of the application group and application that were exported from the OS/400 server, the OS/400 Indexer will now be selected when the application is updated or viewed from the local server. Because the OS/400 Indexer is dependent upon the operating system and not the database type, only the operating system string value is necessary in the Registry. As another example, an AIX server uses Oracle as the database. An application group and application are exported from the AIX server to a local server. To correctly display the database-specific parameters in the application group, the database string value of Oracle is added to the local server definition in the Registry. Note: Although a local server can resemble a non-local server, the following are system limitations for a local server: The userid of a user that is defined on a local server cannot be updated. User and group permissions for users are not supported from the User Permissions page on Users dialog box. The Find function is not supported. Server Printers are not supported. Data Distribution Files and Groups are not supported. Note: For a local server, the default administrative userid is admin. There is no initial password set for the admin userid on a local server. There are two ways to set these Registry entries. If you are using the CM OnDemand Administrator Client at the level or higher, these selections can easily be made when you create a Local server. Pulldowns for Operating System and Database appear on the Add a Server dialog box when you create a server with the Protocol parameter set to Local. The Registry is updated for you automatically. If you are using the CM OnDemand Administrator Client at the level (or higher, although you would likely prefer the graphical method described above for any client above ), these Registry entries can be made directly, using the Registry Editor as described below. Important: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. IBM cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use the Registry Editor at your own risk. Page 16 of 22

17 For information about how to edit the registry, view the Changing Keys and Values Help topic in Registry Editor (Regedit.exe) or the Add and Delete Information in the Registry and Edit Registry Data Help topics in Regedt32.exe. You should back up the registry before you proceed. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD). To add an operating system value and a corresponding database value to the Registry, move to the \HKEY_CURRENT_USER\Software\IBM\OnDemand32\Common key. Under the Common key, move to the local server subkey that you want to modify. All server subkeys begin with the To specify an operating system for the local server, add a new value under the selected local server subkey. The name of the new value is OS_TYPE and the data type is String (REG_SZ). To specify a database for the local server, add a new value under the selected local server subkey. The name of the value is DB_TYPE and the data type is String (REG_SZ). The actual string values for the operating system and database are case insensitive and can be entered in lower, upper, or mixed case. The table below contains a list of the string values that can be specified for the operating system value (OS_TYPE) and the corresponding database value (DB_TYPE). If a database is specified and the operating system does not support the database, the database value will be ignored and DB2 will be used. For example, if the OS_TYPE is OS400 and Oracle is specified for the DB_TYPE, the specified DB_TYPE (Oracle) will be ignored and DB2 will be used instead. If a database value is not specified, the default for the local server is DB2. If an operating system value is not specified, the default for the local server is AIX. Operating System and Database values OS_TYPE AIX HPUX OS390 OS400 SUN WIN32 DB_TYPE DB2, Oracle DB2, Oracle DB2 DB2 DB2, Oracle DB2, Oracle, MSSQL The figure below shows an example of the Registry after an operating system value and a database value have been added to a local server that is identified by subkey (where localservername is the name you have given to the local server when you defined it). Page 17 of 22

18 Using the Spool File Archive Combine report occurrences function with Content Manager, VisualInfo, or ImagePlus WAF Integration (CM OnDemand for iseries Administration Guide) You may have chosen to have OnDemand automatically combine multiple report occurrences in order to avoid the 999 sequence number maximum in Spool File Archive. (To activate this function, you use the OnDemand administrative tool accessed through iseries Navigator. On the report definition s Archive tab, you can specify whether to combine occurrences.) If you also integrate that report with Content Manager, VisualInfo, or ImagePlus WAF imaging systems (known as CM/400 Integration), you may need to change the way you perform the integration. First, a brief review of the Report Combine function: OnDemand normally stores each archived spooled file separately, and identifies it by the date and a 3-digit sequence number (known as the object name). This forces a limit of 999 archives per day for a specific report definition. The Report Combine function was created to provide a mechanism which allows OnDemand to append an archived spooled file to the end of one already archived that day, thereby using the same sequence number. Report combining occurs after all user exit processing is completed and the report is successfully archived. By combining multiple report occurrences and running the CM/400 Integration functions, CM/400 Client users may lose the ability to retrieve the integrated reports from the CM/400 Client. The linkage from OnDemand to CM/400 is added with the original date and 3-digit sequence number. When the Report Combine function occurs after the linkage records are created, the CM/400 control file ends up with the wrong object name. Any attempt to retrieve these documents results in the CM/400 Client issuing an FRN6556A message. You can still use the report combine function, but without specifying one of the CM/400 Integration Index exits (QRLWEXITV or QRLWEXITM) in the Spool File Archive report definition. You need to remove the linkages to any combined reports that were already integrated into CM/400 by using the remove function (RMVVIRDAR command) and then integrate them back into CM/400 either manually or programmatically using the initialize function (ADDVIRDAR command). The suggested approach to automate CM/400 integration with report combining is to add an entry, or entries, to the OS/400 job scheduler which execute the ADDVIRDAR command to load the indexes into the imaging system. The ADDVIRDAR command will ONLY add indexes for reports that have not already been integrated, so the command can be run over and over again without risk of duplication. Therefore, many job schedule entries can be created that Page 18 of 22

19 execute the ADDVIRDAR command each day, perhaps hourly; the number and frequency can be managed by you to coincide with how soon you need to be able to retrieve the reports using the imaging system client. A sample command to create a job schedule entry is shown below. See the command help text for the ADDVIRDAR command for additional details and other options for parameter values, as the sample shown below may need to be altered to meet your requirements. Note that the value of *HIGHEST for the VERSION parameter is new for V5R2. ADDJOBSCDE JOB(ODTOCM) CMD(ADDVIRDAR REPORT(INVOICETST) VERSION(*HIGHEST) + RPTDATE(*CURRENT *CURRENT) CALLVI(*YES) SBMJOB(*NO)) FRQ(*WEEKLY) + SCDDAY(*MON *TUE *WED *THU *FRI) SCDTIME('08:00:00') + JOBD(QRDARS/QRDARS400) USER(QRDARS400) TEXT('Integrate OnDemand rpts into CM') How to delete a particular set of objects from Object Archive (CM OnDemand for iseries Administration Guide) If you need to delete a set of objects from Object Archive, the following information can be used to do so. Note that this is similar to the Delete Report (DLTRPTRDAR) command for Spool File Archive, but for use with Object Archive instead. In the following commands, the lowercase words represent the following: library - The name of the library that contains the objects that were archived. object - The object name, which is equivalent to the date of the archive in YYYYMMDD format. seq - The sequence number of the archive (3 digits). Enter the following SIX commands: 1. ADDLIBLE QRDARS 2. CALL PGM(QRLCOVR) PARM(*ADD 'RLCRLO' ' *') Note: Be sure the third parameter has a space before the *. 3. STRCMTCTL LCKLVL(*CHG) 4. CALL PGM(QRLODLT) PARM('library' 'object' 'seq' '*' *YES) If you display the joblog (be sure to show the detailed messages by pressing F10), you should see some messages that indicate what was done. The last parameter in step 4 causes OnDemand to do a cleanup even if all the objects can't be found (which is equivalent to DLTRPTRDAR CLEANUP(*YES) ). For example, if the archive was for library TBROWN and it was the first one done on May 5, 1997, you would enter the following for step 4: CALL PGM(QRLODLT) PARM('TBROWN' ' ' '001' '*' *YES) 5. COMMIT 6. ENDCMTCTL To create a CL program to delete Object Archive objects from disk/optical storage, create the sample CL program shown below called DLTOBJRDAR Page 19 of 22

20 PGM PARM(&LIBRARY &OBJECTNAME &SEQUENCENO &CLEANUP) DCL VAR(&LIBRARY) TYPE(*CHAR) LEN(10) DCL VAR(&OBJECTNAME) TYPE(*CHAR) LEN(8) DCL VAR(&SEQUENCENO) TYPE(*CHAR) LEN(3) DCL VAR(&RETURNCODE) TYPE(*CHAR) LEN(8) DCL VAR(&CLEANUP) TYPE(*CHAR) LEN(4) ADDLIBLE LIB(QUSRRDARS) MONMSG MSGID(CPF2103) ADDLIBLE LIB(QRDARS) POSITION(*AFTER QUSRRDARS) MONMSG MSGID(CPF2103) STRCMTCTL LCKLVL(*CHG) MONMSG MSGID(CPF8351) EXEC(RCVMSG MSGTYPE(*LAST)) + /* ALREADY STARTED */ ROLLBACK CALL PGM(QRDARS/QRLODLT) PARM(&LIBRARY + &OBJECTNAME &SEQUENCENO &RETURNCODE &CLEANUP) MONMSG MSGID(CPF0000 CPF9999) EXEC(ROLLBACK) COMMIT ENDCMTCTL ENDPGM The program has 4 parameters: OS/400 Library Name (10 Char) OnDemand Object Name (YYYYMMDD) Sequence number ( ) Cleanup (*YES or *NO) To execute the program, call the program as shown below, substituting the correct information for the parameters: CALL PGM(DLTOBJRDAR) PARM('EWAITMAN' ' ' '001' '*YES') By specifying cleanup *YES, OnDemand will remove all its database entries even if it cannot physically delete the object from optical. Page 20 of 22

21 Corrections to CM OnDemand V5R2 Publications Please note the following corrections to the OnDemand V5R2 publications. Clarification of QRDARSADM and QONDADM group profiles for Common Server administrators (CM OnDemand for iseries Common Server Administration Guide) To ensure that all administrative actions function properly for your Common Server administrators, add both the QRDARSADM and QONDADM user profiles as either Group Profile or Supplemental Groups parameter values in the user profiles of your OnDemand administrators. Maximum size of Group and Server Queue names increased (CM OnDemand Common Server Administration Guide) The maximum field length available for Group (of users) Name has been increased to 128 characters. The maximum field length available for Server Queue Name (in a Printer definition) has been increased to 60 characters. Correction to RSCF0200 Format for Spool File Archive s Retrieve Archived Resource API (CM OnDemand for iseries Administration Guide) There is an incorrect table for the Retrieve Archived Resource API in Appendix A of the CM OnDemand for iseries Administration Guide. The table for the RSCF0200 Format is incorrect and should look as follows: RSCF0200 Format Offset DEC Hex Type Field CHAR(*) Buffer to hold the resource group The field description, below the table, for the Total length of all resources should be deleted. The word group should be added to the field name Buffer to hold the resource, so that it matches the field name shown above in the RSCF0200 Format table. Maximum input file size for Common Server Currently, the maximum input file size for CM OnDemand Common Server is 2GB. This is stated incorrectly in the OnDemand Common Server Administration Guide under the description of the ARSLOAD API. (Note that the maximum input file capacity for the PDF Indexer is approximately 3,000 pages, regardless of file size.) Page 21 of 22

22 Complete List of CM OnDemand V5R2 Publications The table below lists the OnDemand V5R2 publications. The publications are available through the iseries InfoCenter at CM OnDemand V5R2 publications Title English Order Number IBM Content Manager OnDemand for iseries Common Server Planning and Installation Guide SC Common Server Administration Guide SC Common Server Indexing Reference SC Common Server Web Enablement Kit Installation and Configuration Guide SC IBM Content Manager OnDemand for iseries Installation Guide Administration Guide IBM Content Manager OnDemand User's Guide Windows Client Customization Guide SC SC SC SC Note: Translated publications are also available. Page 22 of 22