IBM Content Manager Version 8.5 Fix Pack 3 Readme

This readme document contains information about installation and removal of the fix pack and about known problems, restrictions, and solutions in support of IBM® Content Manager Version 8.5.

Readme file for:
IBM Content Manager
Product or component release:
Version 8.5
Update name:
Fix Pack 3
Fix ID:
  • 8.5.0.300-ECM-CM-WIN-fixpack3
  • 8.5.0.300-ECM-CM-AIX-fixpack3
  • 8.5.0.300-ECM-CM-SOL-fixpack3
  • 8.5.0.300-ECM-CM-LNX-fixpack3
  • 8.5.0.300-ECM-CM-zLNX-fixpack3
Publication date:
12 June 2015
Last modified date:
8 July 2015
Online version of readme file: CM_8.5.0.3_fix_pack_readme.html
Important: The most current version of the readme file can always be found online.

Download location

Download IBM Content Manager Version 8.5 Fix Pack 3 from the following location: Fix Central Download Support site or access the fix pack from the table below.

Table 1. Files associated with readme file
Platform File Name
Windows FP8.5.00.300_installer_win.zip
AIX FP8.5.00.300_installer_aix.tar.Z
Solaris SPARC FP8.5.00.300_installer_sun.tar.Z
Linux FP8.5.00.300_installer_lnx.tar.gz
Linux zSeries FP8.5.00.300_installer_zlnx.tar.gz

Known problems, restrictions, and solutions

Known problems, restrictions, and solutions that affect administration and usage of fix packs are documented as techdocs in the product support knowledge base.

To review all known problems, restrictions, and solutions that affect Version 8.5 fix packs, use the following link to query the product support knowledge base: IBM Content Manager Enterprise Edition Version 8.5.0 or IBM Content Manager for z/OS Version 8.5.0

In addition, the fix pack includes the following known problems:

  • Known issues while you are upgrading to Version 8.5 Fix Pack 3

    If you are upgrading to IBM Content Manager Version 8.5 Fix Pack 3 on Linux®, you might experience DB2® instance down. In this case, you need to apply DB2 APAR IC98362 (for DB2 Version 10.1) or IC98880 (for DB2 Version 10.5) and try the upgrade again.

Prerequisites for Version 8.5 Fix Pack 3

The official statements for hardware and software support for IBM Content Manager are provided as part of the hardware and software requirements for IBM Content Manager Version 8.5.

For complete details about the hardware and software requirements for IBM Content Manager, see Hardware and software requirements for IBM Content Manager Enterprise Edition Version 8.5.0 or Hardware and software requirements for IBM Content Manager for z/OS Version 8.5.0.

The fix pack includes the following new prerequisite:

  • IBM Content Manager for z/OS Toolkit installation requirement

    Before you update an existing Toolkit environment with this fix pack, you must complete the two steps that are described in ++HOLD(ACTION) of the PTF to create new UNIX directories and new DDDEF in your SMP/E environment. Otherwise, the PTF will fail to APPLY.

  • IBM Content Manager for z/OS library server and resource manager have a new requirement: Integrated Cryptographic Service Facility

    As this fix pack contains stronger encryption for passwords, you need to install Integrated Cryptographic Service Facility, ICSF, on the z/OS platform. ICSF is a component of z/OS and it is included in the base product. ICSF provides Cryptographic Support either in its own software routines or through access to the cryptographic hardware available on System z. Refer to http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD103782 for the supported hardware and operating system releases.

The fix pack includes the following optional prerequisite:

  • IBM HTTP Server powered by Apache for z/OS, 31-bit instances of either Version 8.5.5 or the base element of z/OS 2.2

    Resource manager on z/OS now supports running directly under either the IBM HTTP Server Version 5.3 (Domino Go Web), or under the IBM HTTP Server Version 8.5.5 powered by Apache 31-bit instances, or under the IBM HTTP Server powered by Apache base element of z/OS 2.2, 31-bit instances. Refer to the z/OS technote http://www.ibm.com/support/docview.wss?uid=swg21688370 for details about this updated support.

Installing IBM Content Manager Fix Pack 3

To install an IBM Content Manager Version 8.5 fix pack, you determine where the fix pack should be installed, prepare the environment for the fix pack installation, complete the installation worksheet for the fix pack programs, install the fix pack, and verify the fix pack installation.

A single installation program installs the fix pack. All of the components installed by the original installation program are updated by this fix pack installation program. You install the fix pack to the repository installation directory (IBMCMREPO) first, and then use the repository installation's updated version of Configuration Manager to update the target installation (IBMCMROOT) with the fix pack.
Restriction: If you install the fix pack on a reference machine without IBM Content Manager Version 8.5 installed to the repository directory, the updated Configuration Manager from the fix pack can only apply the fix pack on a target machine with previously installed and configured IBM Content Manager Version 8.5 components. It cannot install and configure new components. To install and configure new components at this fix pack level, both the fix pack and IBM Content Manager Version 8.5 must be installed to the repository installation directory on the reference machine. For IBM Content Manager for z/OS components, you must install IBM Content Manager for z/OS Version 8.5 using SMP/E first before the fix pack.
For information about supported component and product compatibility combinations, see IBM Content Manager V8.5 for EE Component and Product Compatibility or IBM Content Manager V8.5 for z/OS Component and Product Compatibility.

Before you install the fix pack on Windows

Before you run the fix pack installation program on Windows®, you must prepare the environment.

  1. Perform these steps to prepare your Windows environment for fix pack installation:
    Table 2. Steps to prepare the Windows environment
    If the following statement is true Perform this step
    If you have the library server monitor running on Oracle: Stop the monitor. Enter the following SQL statement:
    set serveroutput on
execute icmlsmon.stopmonitor
    If you have the library server monitor running on DB2: Stop the monitor.

    Stop the service ICM LS Monitor DBNAME.
    If you are using DB2: Stop the DB2 instance where the IBM Content Manager databases are installed.

    Enter the following command to exit all DB2 applications: db2stop
    If you are using DB2 and DB2 Net Search Extender: Enter the following command: db2text stop
    If you are using DB2 and DB2 Text Search: Enter the following command: db2ts "STOP FOR TEXT"
    If you are using DB2: Start the DB2 instance:
    1. Enter db2start at a command prompt.
    2. If you use DB2 Net Search Extender, enter db2text start at a command prompt.
    If you installed IBM Content Manager Services for Lotus® Quickr® Version 1.0: Delete win32serv.dll and WinFileService.dll from your WINDIR\system32 directory if these two files exist.
  2. Optional: Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation and replication performance:
    Option Description
    DB2 Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION (PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC)

    RUNSTATS ON TABLE schema_name.RMREPLICATION WITH DISTRIBUTION AND DETAILED INDEXES ALL
    Oracle Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION(PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC);

    COMPUTE STATISTICS TABLESPACE REPLICAS;
    If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time.
  3. Optional: Recommendation: Create an index on the RMOBJECTS table to improve the background performance:
    Option Description
    DB2 Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID)

    RUNSTATS ON TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES ALL
    Oracle Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID);

    COMPUTE STATISTICS TABLESPACE OBJECTS;
    If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time.
  4. Important: Stop all resource manager services (purger/migrator/stager/replicator) by using the system administration client or the resource manager administration console.
  5. If you are using Oracle and have it installed: Ensure that all of the connections to the IBM Content Manager servers are stopped but the listener and your Oracle instance are started. You or your Oracle DBA should quiesce all user activity or terminate all user sessions on the IBM Content Manager library server database (whether or not Oracle indicates that they are active). Additionally, extproc processes might still be alive even after user sessions are terminated. Make sure to stop them before installing the Fix Pack by completing the following steps:
    1. Open the Windows Task Manager.
    2. Click Processes.
    3. Click each process with the name extproc.exe and click End Process.
  6. If you have multiple active Oracle homes installed on the same Oracle server, then make sure that the IBM Content Manager runtime environments can correctly access the IBM Content Manager databases. Verify that the DB2 Content Manager processes are started with correct values for the intended Oracle home in such environment variables as ORACLE_HOME, PATH, and CLASSPATH.
  7. Configure debug logging.

    Follow the instructions in Enabling debug installation logging on Windows.

Before you install the fix pack on AIX, Linux, and Solaris

Before you run the fix pack installation program on AIX®, Linux, or Solaris, you must prepare the environment.

Restriction: After you install IBM Content Manager on AIX, Linux, or Solaris, the IBM Content Manager file sets do not reflect the current version of the product. To retrieve the correct product level and determine whether the target installation should be updated with the fix pack, enter this command on target machine:
/opt/IBM/db2cmv8/bin/cmlevel -l
  1. Perform these steps to prepare your AIX, Linux, or Solaris environment for fix pack installation:
    Table 3. Steps to prepare the AIX, Linux, or Solaris environment
    If the following statement is true Perform this step
    If you have the library server monitor running on Oracle : Stop the monitor. Enter the following SQL statement:
    set serveroutput on
execute icmlsmon.stopmonitor
    If you have the library server monitor running on DB2 : Stop the monitor. Enter the following command : /etc/rc.cmlsproc - shutdown
    If you are using DB2: Stop the DB2 instance where the IBM Content Manager databases are installed.
    Enter the following command, where the user ID of the DB2 instance is db2inst1 by default:
    su - userID of the DB2 instance
db2stop
    For AIX only: As root, enter the /usr/sbin/slibclean command to unload unused shared libraries from memory.
    If you are using DB2 and DB2 Net Search Extender: Enter the following command: db2text stop
    If you are using DB2 and DB2 Text Search: Enter the following command: db2ts "STOP FOR TEXT"
    If you are using DB2: Start the DB2 instance.
    1. As the root user, enter the following command: 
      su - userID of the DB2 instance
    2. Enter the following command: 
      db2start
    3. If you have DB2 Net Search Extender installed, enter the following command:
      db2text start
    4. Enter the following command:
      exit
  2. Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation and replication performance:
    Option Description
    DB2 Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION (PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC)

    RUNSTATS ON TABLE schema_name.RMREPLICATION WITH DISTRIBUTION AND DETAILED INDEXES ALL
    Oracle Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION(PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC);

    COMPUTE STATISTICS TABLESPACE REPLICAS;
    If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time.
  3. Recommendation: Create an index on the RMOBJECTS table to improve the background performance:
    Option Description
    DB2 Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID)

    RUNSTATS ON TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES ALL
    Oracle Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID);

    COMPUTE STATISTICS TABLESPACE OBJECTS;
    If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time.
  4. Important: Stop all resource manager services (purger/migrator/stager/replicator) by using the system administration client or the resource manager administration console.
  5. If you are using Oracle and have it installed: Ensure that all of the connections to the IBM Content Manager servers are stopped but the listener and your Oracle instance are started. Terminate all outstanding extproc processes unless other applications other than IBM Content Manager require them. Oracle occasionally continues to run extproc processes to save time when reloading them. If Oracle reuses an old extproc process that did not pick up the changes to your tnsnames and listener configuration, then a TNS error can result.
    On AIX:
    1. From a command prompt, enter the following command: 
      /usr/bin/ps -ef | grep -i oracleSID
      where SID is associated with your IBM Content Manager library server database. The process ID number is displayed in the second column.
    2. For each process ID number, enter the following command:
      /usr/bin/kill -9 processID
      where processID is the process ID number. Ensure that you already stopped active database sessions against the library server (in the previous step) before you run the kill -9 command.
    3. Log in as root and enter the /usr/sbin/slibclean command to unload unused shared libraries from memory.
    On Solaris and Linux:
    1. From a command prompt, enter the following command: 
      /usr/ucb/ps -auxww | grep -i oracleSID
      where SID is associated with your IBM Content Manager library server database. The process ID number is displayed in the second column.
    2. For each process ID number, enter the following command:
      /usr/bin/kill -9 processID
      where processID is the process ID number. Ensure that you already stopped active database sessions against the library server (in the previous step) before you run the kill -9 command.
  6. If you have multiple active Oracle homes installed on the same Oracle server, then make sure that the IBM Content Manager runtime environments can correctly access the IBM Content Manager databases. Verify that the IBM Content Manager processes are started with correct values for the intended Oracle home in such environment variables as ORACLE_HOME, PATH, CLASSPATH, and LIBPATH (AIX) or LD_LIBRARY_PATH (Solaris).
  7. Set up for debug logging.

    Follow the instructions in Enabling debug installation logging on AIX, Linux, or Solaris.

Completing the installation worksheet for IBM Content Manager

You can use an installation worksheet to gather the information needed to install the fix pack for IBM Content Manager.

This worksheet is valid only when configuring a library server and resource manager database. For the component or components that you are updating, gather the information listed in the following table. When the installation wizard runs, it automatically prompts you to enter data for any setting that it cannot detect. The table is provided with blank spaces so that you can print it and enter your information.
Supply values for the following table:
Table 4. Installation worksheet for IBM Content Manager
Product component to update Data required Your values
Library server Library server database name  
Library server schema name (DB2 only)  
Library server JDBC connection string (Oracle only)  
Library server database administration ID  
Library server database administration password  
Library server database connection port  
Resource manager database Resource manager database name  
Resource manager schema name (DB2 only)  
Resource manager JDBC connection string (Oracle only)  
Resource manager database administration ID  
Resource manager database administration password  
Resource manager database connection port  
Resource manager application (for each application) Application server home directory  
Application server profile home directory  
Resource manager Web application name  
Application server administration ID *  
Application server administration password *  
Application server node name **  
Resource manager Web server name **  
Application server cluster name ***  

* Only needed if application server security is enabled.

** Only needed if the deployment target is an application server.

*** Only needed if the deployment target is a cluster.

Installing the fix pack for IBM Content Manager

To install the fix pack for IBM Content Manager, run the installUpdate fix pack installation wizard.

You must first install the fix pack to the IBM Content Manager repository on the reference machine, and then use the updated Configuration Manager on this reference machine to update each target machine with the fix pack. The target machines are any computer where one of these system components is installed. Note that a target machine can also be the same as the reference machine. The Configuration Manager will launch the fix pack configuration wizard for a target machine after you select a target machine and click Configuration > Update configuration on the menu bar. The fix pack configuration wizard updates only those system components and components that are local to the computer on which it runs. For example, if your IBM Content Manager library server and resource manager components are installed on different computers, then you need to run the fix pack configuration wizard for both computers.
Complete the following steps to install IBM Content Manager.
Important: The more component views that exist in the library server, the longer that the fix pack installation can take to run because of the need to regenerate the access statements for those component views. Although the generation of an individual access statement for a component view can take only subseconds, the actual time that the installation takes can vary according to your environment, your content management setup, and the number of component views that you have configured.

If you have a large number of component views, such as thousands of views, and if the fix pack upgrade is slow, then you might want to inspect the installation log file during the installation. By inspecting this log file, you can find out if the delay is due to the generation of these access statements. The update configuration log including the generation of the access statements is IBMCMREPO/version/cmcfgmgr/log/hostname/version/cmfpconfig.log, where IBMCMREPO is the installation location on the reference machine as defined by the IBMCMREPO environment variable and version is the fix pack version.

  1. Run the installUpdate program to start the installation.
    Option Description
    AIX, Linux, and Solaris installUpdate
    Windows installUpdate.bat
    The installation wizard detects which IBM Content Manager system components and components are installed on the computer on which it is running and displays the components that will be updated with this fix pack installation.
    Attention: If you close the Configuration Manager before installing the fix pack, you can reopen it by launching the Configuration Manager shortcut or by running the cmcfgmgr_CM script at IBMCMREPO\VERSION\bin\. Then click Configuration > Update configuration on the menu bar.
  2. Continue with the wizard as instructed by the interface panels.
    Enter the data that you gathered in Completing the installation worksheet for IBM Content Manager.
  3. After you enter all configuration information, click Next to begin the fix pack installation.

The fix pack installation and configuration data is retained in log files that are created by the fix pack installation wizard during installation. You can find log files for the installation and configuration in the following locations. In the path for the log file location, IBMCMREPO is the installation directory, version is the fix pack version, and hostname is the name of the host for which the fix pack is being installed.

Table 5. Locations of log files
Log file type Log file location
Installation IBMCMREPO/version/cmcfgmgr/log/hostname/version/fpinstall.log
Removal IBMCMREPO/version/cmcfgmgr/log/hostname/version/fpuninstall.log
Configuration IBMCMREPO/version/cmcfgmgr/log/hostname/version/cmfpconfig.log
Removal of configuration IBMCMREPO/version/cmcfgmgr/log/hostname/version/cmfpunconfig.log
Validation log IBMCMREPO/version/cmcfgmgr/log/hostname/cfgactions.log
Tip: For more information about the log file locations for Version 8.5, see Log file locations.

Installing the fix pack in silent mode

To run a silent installation, enter the following command:
install -i silent -f path/install.rsp
where path/install.rsp represents the complete path and file name for the installation response file. If no path is specified, the default location is the local directory.
To run a silent configuration, enter the following command:
IBMCMREPO/VERSION/bin/cmcfgmgr_CM -f path/config.rsp
where path/config.rsp represents the complete path and file name for the configuration response file. If no path is specified, the default location is the local directory.
For remote configuration, you must specify the login user's password for the target machines too:
IBMCMREPO/VERSION/bin/cmcfgmgr_CM -f path/config.rsp -p password

When the configuration manager runs in silent mode, no windows display and the configuration progresses as if you had entered the response file values into each window.

If you run a silent installation or configuration that stops immediately, you might not see any error messages. Some error messages are hidden when there are no installation windows.

Removing the fix pack

To remove IBM Content Manager fix pack 3:

  1. Open the Configuration Manager on the reference machine by running the cmcfgmgr_CM script at IBMCMREPO\VERSION\bin\, or by double-clicking the Configuration Manager shortcut.
  2. Expand the profile and right-click the host from which you will be removing the fix pack, and select Connect and Validate. Enter your user id and password to start the validation process.
    When the validation process completes, click Finish.
  3. In the Configuration Manager menu bar, click Configuration > Remove Operations. The fix pack update wizard opens.
  4. Select Remove the fix pack configuration and click Next. Follow the instructions in the wizard to complete the removal of the fix pack.

Additional updates

IBM Content Manager, Version 8.5 Fix Pack 3 includes the following additional updates.

  • System administration web client

    You can now deploy a plug-in into IBM Content Navigator that allows you to administer IBM Content Manager users over a secure Web connection. In this first release of system administration web client, the following tasks are supported.
    • Authentication and authorization of users.
    • Searching and filtering tasks for data modeling.
    • Importing LDAP users.
    Restriction: The following administration tasks are not supported:
    • Library server and resource manager configuration.
    • Document routing and workflow.
    • Data modeling tasks such as create, edit, copy, and delete.
    • Business Process Management and LDAP integration.
    Learn more...

  • Encrypt data at rest in the resource manager

    The Content Manager EE resource manager can now encrypt all object content when at rest (with the exception of cataloged content). As a result, administrative users or other personnel with access to the file system or its backups can no longer view the encrypted data. You can enable this encryption (of all incoming data) from the Privacy tab in the system administration client.
    Restriction: The resource manager for z/OS is not included.
    Important:
    • Data at rest encryption impacts performance and requires significant additional CPU load.
    • You must have valid, tested database backups of the resource manager database. Otherwise, loss of the database information will result in the loss of the encrypted content.
    By default, encrypt data at rest is disabled. Learn more...

  • Content Manager EE support for Oracle 12.1.0.1

    Content Manager Enterprise Edition Version 8.5 Fix Pack 3 supports Oracle 12.1.0.1 on AIX, Linux, and Solaris.

    The following Oracle 12c patches are required:

    For AIX, Linux, and Solaris: Patches 18169693, 19920266, and 20051833.

    Restriction: Windows is not supported.

    For more information, see the technote Upgrading to Content Manager 8.5 fix pack 2 or later with Oracle 12c.

  • IBM Content Manager for z/OS Toolkit security enhancement

    A number of Toolkit utilities now enhance security for password input. Each time a utility is run, it now encrypts the password (if it was not encrypted already). For utilities where the input is from the console, the user-entered password no longer displays. For those utilities that are run from batch or from the command line (where the passwords are entered either in-stream in the JCL or directly on the command line), those passwords are now encrypted and input from a file. For existing utilities that already specify the passwords in a file, those passwords are now encrypted.

    The enhanced security affects the following utilities. They are listed according to the name of the batch version of the command (for example JCLs) and the UNIX System Services scripts. The JCLs can be found in the hlq.SICMSAMP dataset that is created by SMP/E jobs when you install the IBM Content Manager for z/OS Toolkit. The scripts can be found in the config directory of the installed Toolkit under UNIX System Services, for example, /usr/lpp/icm/V8R5M0/config.
    • ICMCFGLB, cmcfglsi – Utility for building component table views and default item types. For those users that have an existing parameter file with a clear password, this utility must be run at least once in order to encrypt the password in the parameter file.
    • ICMCONFG, icmconfig – Utility for configuring the Toolkit connector environment.
    • ICMCRYPT, encrypt – Utility for generating shared connection ID information.
    • ICMVERFY, icmverify – Utility for verifying successful configuration of the Toolkit connector environment.
    • ICMVALTL, icmrmlsval390 – Utility for finding data discrepancies between the library server and the resource manager.
    Further usage details can be found in each of those JCLs and scripts.

    In addition, the z/OS validation utility (ICMVALTL or icmrmlsval390) now provides an option to enable a secure connection to the library server and resource manager database. Details of this option can be found in the ICMRM.properties390 file. The ICMRM.properties390 file is in the home directory where the z/OS validation utility is installed, for example, zOSValidator/ICMRM.properties390.

  • Enhanced audit filtering for documents

    As an audit event improvement, a new IBM Content Manager API (listContentViewEvents) can retrieve the IDs of all documents that have been viewed by a specific user or list of users within a specific date range. The API also has a for-record-only flag that limits results to documents that are declared as records, and returns the record ID generated by IBM Enterprise Records when present. For more information, see http://www.ibm.com/support/docview.wss?uid=swg27045642

  • Library server provides an option to gracefully shut down the usage statistics service on AIX, Linux, and Solaris

    Manually modify the entry for the library server usage statistics service in /etc/inittab file and replace the word 'respawn' with 'once'.

    After you modify the /etc/inittab file, enter the following command:

    init q

    To shut down the library server usage statistics service, enter the following command:

    /etc/rc.cmusproc -shutdown
    Note: When the usage statistics service is not running, the library server continues to gather the access data in ICMSTUSSTATGING table. When the service is brought up, the data is processed.

  • Improved performance for use with IBM Enterprise Records Version 5.2 Fix Pack 1

    IBM Content Manager Enterprise Edition Version 8.5 Fix Pack 2 or later provides a much improved performance for use with the new IBM Enterprise Records Version 5.2 Fix Pack 1. The new integration of IBM Enterprise Records with Content Manager Version 8 removes the requirement for Content Federation Services and provides a highly scalable records management implementation to meet the demands of the largest Content Manager Version 8 systems. For more information, see IBM Enterprise Records V5.2 Announcement.

  • New check box in system administration client to indicate IBM Enterprise Records enablement

    System administration client now has a new "IBM Enterprise Records" check box to indicate that IBM Enterprise Records is enabled. The new check box is located under the "Enable Record Management" section when you select the "Feature" tab in library server configuration window. Select this check box when Content Manager Version 8.5 is integrated with Enterprise Records Version 5.2 FP1 or later and Enterprise Records is configured for direct access to Content Manager.

  • On-hold enhancement

    Holds are used to ensure that items cannot be updated or deleted until the hold is removed. Starting from Version 8.5 Fix Pack 2, an internal checkout operation is done before a hold is added to an item. After the add hold operation is finished, the item is checked in. If the item is already checked out, even from the same user ID that adds the hold, an ICM7960 error is returned. You can avoid this error by first checking in the item before a hold is added.

  • Windows service support for Event Monitor and BPM Event Handler

    You can start Event Monitor or BPM Event Handler as a service on Windows operating system. For more information about event monitor and BPM event handler enhancements, see http://www.ibm.com/support/docview.wss?uid=swg21666540.

  • Windows domain administration user support for server and client components

    A Windows domain administration user is now supported to run Version 8.5 Fix Pack 2 or later installation and configuration with the following considerations:

    • The domain group of the Windows domain administration user must be added to the local Windows administrator group.
    • You can use the domain administration user to log on to the reference machine and launch the installation and configuration wizard. The library server administration ID, library server connection ID, and resource manager administration ID don't support the domain administration user.
    • You must choose the ‘Run as administrator’ option when you run the IBM Content Manager installation program or the updated configuration manager.
    • If you are using DB2 and a Windows domain administration user to configure Content Manager server components, perform the following steps before you run the fix pack configuration wizard to prevent SQL1092N error during the configuration:
      1. Change the logon user ID for the DB2 server instance to the domain user.
      2. If Windows Extended Security is enabled, you must add the domain user to the DB2ADMNS group or its equivalent.
      3. Add the domain user to the local Windows administrator group.
      4. From a DB2 command prompt, enter the following command: 
        db2set DB2_GRP_LOOKUP=LOCAL,LOCALTOKEN
      5. From a DB2 command prompt, enter the following command: 
        db2 UPDATE DBM CFG USING CATALOG_NOAUTH YES
      6. Restart DB2.

        For more information about SQL1092N error, see SQL1092N.

  • Resource manager validation utility recovery tools enhancements

    The resource manager validation utility recovery tools ICMFILENOTFOUNDCleanup and ICMNOTINRMCleanup are enhanced with additional control options. For more information, see http://www.ibm.com/support/docview.wss?uid=swg27043867.

  • Resource manager option for file system synchronous write operation

    Resource manager provides an option for file system write operations to synchronize with the underlying storage devices to help prevent potential data loss when storage devices are not configured properly and run out of disk space. For more information, see http://www.ibm.com/support/docview.wss?uid=swg27043996.

  • Web services support for the EXPIRATIONDATE system attribute

    Content Manager Web services now support the EXPIRATIONDATE system attribute. This enhancement enables Web services to return the EXPIRATIONDATE system attribute when you run a RunQueryRequest or a RetrieveItemRequest.

  • New error message codes for IBM Content Manager library server and API

    Content Manager Version 8.5 Fix Pack 2 introduced new error message codes for library server and API when integrated with IBM Enterprise Records product. See the techdoc http://www-01.ibm.com/support/docview.wss?uid=swg21688872 for details about these error codes.

  • Content Manager support for storing and retrieving objects greater than 2 gigabytes in size

    Content Manager now supports storing and retrieving objects that are greater than 2 gigabytes in size. You can use this feature when you use Content Manager Version 8.5 Fix Pack 2 or later Java APIs that use streaming. Loading these large objects into memory during the add, update, or retrieve operation is not allowed and produces an error. This change allows large objects to be stored and retrieved on Content Manager servers that are version 8.5 and above. This feature is not supported for z/OS resource managers. LAN cache and Tivoli Storage Manager retrieve cache features currently do not support caching of objects greater than 2 gigabytes in size. Synchronous replication with large objects requires the resource manager to be at version 8.5 Fix Pack 2 or above. Partial retrieve is not supported for objects larger than 2 gigabytes in size.

    Content Manager APIs that use streaming for the document model use the following method to set the content for a part: 

    base.setAddLocation(location);

    Where the location passed in is a stream or a file name. See the sample SDocModelItemICM.java for complete details.

    For resource items, use one of the following methods: 

    - DKLobICM.add(filename)
- DKLobICM.add(stream)

    See the sample SResourceItemCreationICM.java for details.

Cumulative fix list (APARs)

The cumulative fix list contains all APARs that are fixed in Version 8.5 of IBM Content Manager.

Important: For some APARs, such as security-related APARs, information about that APAR is not made available to customers to avoid compromising customer and product security.
Table 6. Fix list for IBM Content Manager Version 8.5 Fix Pack 3
APAR Description
Beans
IO23557 Semicolon in a new password is causing the password to be cut before the semicolon.
IO23092 CMBITEM returns empty strings for NULL values.
Connector
IO22380 Java DKAuthorizationMgmtICM.isAuthorized method can cause slow performance.
IO22672 C++ DKUserMgmtICM.listUserDefs() on Oracle encounters ORA-01406.
IO22739 Option is added for DDO properties CREATETS, LASTCHANGEDTS, and CHKOUTTIMESTAMP to be returned as java.sql.Timestamp in Java.
IO22755 DKContentOperationsICM.setStringProperty API does not allow <<null>> to represent a null string value.
IO22910 C++ API throws an exception with a DGL3854A: Internal error message when the response exceeds 512 bytes.
Library Server
IO22777 IBM Content Manager fails to save a document after enabling retention policy during the update to an existing item type.
IO22788 A search in IBM Content Manager may not return a result if the search string contains certain Slovak characters.
IO22906 Adding not nullable attribute to an existing item type when providing empty string as default value fails with ICM7015 error.
IO23002 IBM Content Manager library server log reports allocation failed error in some stored procedure.
PI31843 Unable to retrieve a workflow for an itemid with special character symbols causing double byte usage in UNICODE.
PI33452 $ symbol in the attributes ICM$RETENTIONDATE and ICM$AUTODELETEDATE is not consistent in SQL generation.
PI36588 IBM Content Manager slowing down during IER bulk declare/undeclare processing.
PI37724 Unable to create new user ID with a special symbol @ in the first position.
Resource Manager
IO22894 Storage subsystem error condition can lead to miscalculation of volume capacity and subsequent suspension of volume.
IO22931 The IBM Content Manager Validation utility could incorrectly report file size mismatch errors when device manager is disabled.
System Administration Client
IO22448 LDAP user import scheduler cannot add a scheduled job to an operating system when the operating system is Windows Server 2012 or later.
XMLSDK
IO22517 A java.lang.IllegalArgumentException error is thrown when retrieving a document with a '0x1a' character in filename.
IO23018 A Webservices query on an item type with an auto-delete retention policy fails with an org.w3c.dom.DOMException error.
Viewer
IO22995 Pages of a TIFF document are printed incorrectly as inverted.

Copyright and trademark information

IBM, the IBM logo, and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml

Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Other company, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:
  • the Excluded Components are provided on an "AS IS" basis
  • IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  • IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
  • IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.