IBM Content Manager Version 8.5 Fix Pack 6 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 6
Fix ID:
  • 8.5.0.600-ECM-CM-WIN-fixpack6
  • 8.5.0.600-ECM-CM-AIX-fixpack6
  • 8.5.0.600-ECM-CM-SOL-fixpack6
  • 8.5.0.600-ECM-CM-LNX-fixpack6
  • 8.5.0.600-ECM-CM-zLNX-fixpack6
Publication date:
9 December 2016
Last modified date:
9 December 2016
Online version of readme file: CM_8.5.0.6_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 6 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.600_installer_win.zip
AIX FP8.5.00.600_installer_aix.tar.Z
Solaris SPARC FP8.5.00.600_installer_sun.tar.Z
Linux FP8.5.00.600_installer_lnx.tar.gz
Linux zSeries FP8.5.00.600_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. For Content Manager for z/OS, also read the cover letter that is shipped with the PTF.

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

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

    If you are upgrading to IBM Content Manager Version 8.5 Fix Pack 6 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.

  • Error com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-1131, SQLSTATE=38503, during creating or retrieving a document

    This error indicates that the library server was terminated abnormally.

    This problem happens because the library server might not return data for the requested operation. The CLOB/BLOB output parameters of one of the library server stored procedures are not large enough to contain the data to be returned. The default value is 320 K.

    In this fix pack, instead of terminating abnormally, the library server now has a new error code 7964 with the following error message:

    ICM0001: This is an unexpected internal error or an unrecognized error code. Run the application again with server trace set to Detail and Data. Save the server log and see your IBM service representative. : 7964 (STATE) : [LS RC = 7964]

    When a stored procedure needs to return data that is bigger than its LOB parameters maximum size, it returns this error code. You can redefine the stored procedure's LOB parameters to be bigger and try again the operation that caused the error.

    When this error occurs, the library server trace log will contain the detailed information about this error. Open the library server log to find the error code and determine which stored procedure returned this error and contact IBM support for assistance to redefine such stored procedure.

Prerequisites for Version 8.5 Fix Pack 6

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 prerequisites:

  • 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 6

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 z/OS

The fix packs on z/OS are installed by using SMP/E. During the SMP/E RECEIVE process, installation instructions are in the ++HOLD sections, which can be found in the SMPRPT DD name in the RECEIVE job. The ++HOLD sections must be reviewed before the start of the SMP/E APPLY process.

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 Enterprise Edition

To install the fix pack for IBM Content Manager Enterprise Edition, 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 6:

  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 6 includes the following additional updates.

  • Included software updates

    Content Manager Enterprise Edition Version 8.5 Fix Pack 6 includes the following updated software.

    • IBM Runtime Environment Java Technology Edition 8.0.3.20 (SR3FP20) (AIX, Windows, Linux, Linux zSeries)
    • Oracle Outside In Technology 8.5.2 with patch 23148557 and patch 23558243
    • Snowbound RasterMaster version 14.4.3
    • IBM Global Security Toolkit version 8.0.50.57
  • Supported software and operating systems

    With this fix pack, Content Manager EE supports the following operating systems and software.

    Operating systems:
    • Red Hat Enterprise Linux (RHEL) Server 7.2
    • AIX 7.2
    Software:
    • WebSphere Application Server Version 9.0 and WebSphere Application Server Network Deployment Version 9.0
    • 64-bit IBM Security Directory Server Client version 6.4.0.10 or later, or version 6.3.1.19 or later, for the library server component
    • DB2 Enterprise Server Edition version 11.0 and later fix packs
    • Oracle Enterprise Edition version 12.1.0.2 on Linux for zSeries
  • Language support for system administration web client plugin

    IBM Content Manager system administration web client plugin supports languages other than English. For the list of supported languages, see http://www.ibm.com/support/docview.wss?uid=swg27048909.

  • WebSphere Liberty database connection pooling with Java API

    The Content Manager Java API now supports WebSphere Liberty database connection pooling. For more information about using the WebSphere Liberty database connection pooling with Java API, see http://www.ibm.com/support/docview.wss?uid=swg27048913.

  • Resource manager encryption utility (Encryptor) for existing data at rest

    The Content Manager EE resource manager Version 8.5 Fix Pack 6 introduces a new encryption utility named Encryptor. You can use the encryptor to encrypt the existing data at rest. The encrypt data at rest feature was introduced in resource manager Version 8.5 Fix Pack 3. When the data at rest encryption feature is enabled, the resource manager encrypts newly stored data. However, the existing data in the resource manager is not encrypted unless this feature is enabled and the content is updated. You can now use the encryptor to encrypt the existing data at rest in resource manager. For more information, see http://www.ibm.com/support/docview.wss?uid=swg27048930.

  • System administration client and LDAP import utility enhancements

    The System administration client and LDAP import utility provide the following enhancements:

    • An administrator can set an option that allows local IBM Content Manager users to be created and maintained in an LDAP group. Before Fix Pack 6, when you used "LDAP user import scheduler" to import and synchronize LDAP users/groups between Content Manager and LDAP server, LDAP groups were only allowed to contain imported LDAP users. In this fix pack, administrator can set a flag CMLDAPGROUPMIXEDUSERALLOWED=TRUE in [IBMCMWorkingDirectory]/cmgmt/sa/cmadmin.properties, then use the system administration client to add Content Manager local users to an LDAP group. The LDAP import scheduler does NOT remove Content Manager local users during the synchronization process when this flag is set. With this enhancement, administrator can use a local user to test all property settings for an LDAP user without creating an LDAP user in LDAP server itself.
    • Content Manager LDAP user import utility can overcome multi-value attribute 5000 limit for Microsoft Active Directory(AD). Before Fix Pack 6, LDAP user import utility did not retrieve more than 5000 users from one LDAP group. AD has a 5000 hard limit for "MaxValRange" in LDAP setting since Windows Server 2008, which limits the number of return results for a multi-valued attribute. In this fix pack, LDAP import utility uses a client-side search to overcome this limit. This enhancement is transparent to the user and no additional configuration is needed.

Behavior changes

IBM Content Manager, Version 8.5 Fix Pack 6 includes the following behavior changes.

  • With the fix of APAR IO24850, a new version of item or part will have different values for Create timestamp (CREATETS) and Create User (CREATEUSERID) attributes of the root component (DDO property DK_ICM_PROPERTY_CREATETS DK_ICM_PROPERTY_CREATEUSERID) than before. CREATETS and CREATEUSERID values will be set to the current timestamp and user of the current update operation instead of copying from previous versions. If your application needs to retain the old behavior, turn on bit 3 (starting from bit 0) of the column SYSTEMFLAG3 of the ICMSTSYSCONTROL table in the Library Server database.

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 6
APAR Description
Connector
IO24496 Error sometimes happened when searching a string with non-single byte UTF8 characters.
IO24544 Active item type view cache is not cleared when datastore cache is cleared.
IO24611 Query returns unexpected search results when the search string contains a single quote.
IO24827 Null pointer error when setting C++ DKLobICM with invalid MIME type.
Install and Upgrade
IO24783 Library server configuration fails if the user password contains the character $ on UNIX or % on Windows.
Library Server
IO24651 Auto-link/foldering is creating a new folder instead of linking document to an existing folder
IO24850 New versions have incorrect CREATETS and CREATEUSERID values
Library Server for z/OS
PI60151 Library server monitor heart beat incorrectly marks resource manager as unavailable.
PI64680 High volume batch utility is not processing all input when stopcount is used.
PI67963 Importing itemtype definitions to create itemtypes is getting unexpected error with SQL error -519.
Resource Manager
IO24832 Resource manager threads hang during migration to Tivoli Storage Manager.
Resource Manager for z/OS
PI61614 Resource manager not recovering from abend correctly and getting OAM 34010200 and this continues for a while.
PI64425 Apache HTTP Server not handling German and other codepages for translation of orders from client code.
Viewer
IO24434 Selecting a Zoom Option in German locale does not change the scale.
IO24764 Thumbnails that are generated for TIFF documents are slow to generate.
IO24780 OutOfMemoryError during page manipulation of a document.
Web Administration Client
IO24645 Group assignment list for a user is incorrect in the Content Manager system administration web client plugin.

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.