IBM DB2 Document Manager Version 8.3 Fix Pack 12 (Build 704) Readme

Content

This readme has the following parts:

1. Problems fixed in this release
2. Known problems
3. Quality improvements
4. Supplemental installation information
5. Product documentation and support

1. Problems fixed in this release

This section lists problems that were fixed after the release of DB2 Document Manager Version 8.3 Fix Pack 11.

If a link in the following table does not work, the detailed information for that APAR is not yet available from the Support page.

Table 1. Problems that were fixed for Version 8.3 Fix Pack 12 of DB2 Document Manager

APAR	Brief problem description
IO09687	Out-of-memory exception caused the dllhost.exe process to fail in some situations In some configurations that contained a large number of native folders, an out-of-memory exception occurred during a cache refresh and the exception was not handled. This caused the dllhost.exe process to exit abnormally, resulting in loss of connection to the DB2 Document Manager library. DM COM errors were written to the Windows event log. With the fix of this APAR, exceptions of this type are handled with a DB2 Document Manager error message and the dllhost.exe process does not exit abnormally. See 5.2.1.24 for Best Practice information.
IO10026	The Document Add Options dialog box was sometimes displayed after AutoCAD 2008 documents were viewed DB2 Document Manager sometimes displayed the Document Add Options dialog box after you viewed and closed an AutoCAD document without making changes.
IO10189	When starting AutoVue, DB2 Document Manager sometimes ignored command line arguments The Desktop template did not always pass AutoVue -C command line arguments correctly.
IO10217	Plug-in arguments that were configured in Designer were not always parsed correctly To avoid this issue, see 5.2.1.1 Configuring Desktop menu command plug-ins before you configure a Desktop menu command plug-in in Designer.
IO10226	The Item Templates dropdown menu was missing from some windows In some configurations, the Revise and Add From Library Template windows did not display their associated Item Templates dropdown menus.
IO10239	In single sign-on configurations, DB2 Document Manager sometimes requested a second user login When DB2 Document Manager was configured for single sign-on, the Desktop sometimes prompted you to log in a second time after you started an application.
IO10316	MSG files could not be opened for Checkout-Launch or Copy-Launch actions The Desktop locked some MSG files, and this prevented them from being opened by other applications.
IO10320	In some DB2 Document Manager configurations, the dllhost.exe process would hang indefinitely during the cycle This Lifecycle Services problem locked DB2 Document Manager resources and resulted in COM errors. With the fix of this APAR, the DdmWpSrv.ini file is installed with DB2 Document Manager Version 8.3 Fix Pack 12. The file contains the following default setting: [LifeCycleQueue]    Process1000LifeCycleItems=No With the default setting of No, Lifecycle Services processes 20 service requests during a single cycle. If you change the setting to Yes, then Lifecycle Services processes 1000 service requests during a single cycle. Important: Do not change the default value if the dllhost.exe process in your configuration is running normally.
IO10330	Rendition Services truncated commands that were longer than 512 characters With the fix of this APAR, Rendition Services now supports 2048 command-line characters.
IO10337	Item Property CVLs sometimes displayed incomplete data Item Property CVLs that were generated from saved searches of a very large number of items did not display all the data associated with all of the items. Tip: Running a large search (such as searching for all of the items in the system) can be extremely time consuming and processor-intensive, depending on how many items are in the repository.
IO10352	Searches from the Content search tab were not case sensitive Content searches were not case sensitive by default, as they should have been. For example, even if you did not select the Case insensitive search option and you searched for Cyan, DB2 Document Manager returned both cyan and Cyan. With the fix of this APAR, content searches are case sensitive by default, unless you select the Case insensitive search option.
IO10363	In single sign-on configurations, DB2 Document Manager sometimes requested a password before transitioning a document If DB2 Document Manager was configured for single sign-on and the Require user authentication option was enabled for a transition, the Desktop prompted you to enter your password before transitioning a document. With the fix of this APAR, in single sign-on configurations the Desktop passes the first authentication and does not prompt for your password during transitions.
IO10704	Advanced search values were doubled when the keyboard was used to select the property If you selected the property in an advanced search by using the keyboard instead of the mouse, the predefined value list was doubled.
IO10751	Checkout operations sometimes failed after a document was added When you clicked Checkout or Checkout-Launch in the dialog box prompt after adding a document, the checkout operation would fail if a background property modification changed the filename before you clicked the command.

Important: If an APAR does not have a hyperlink. Click this link for the Latest Closed APARs available on the Support and Download page.

For problems that were fixed in previous releases, see the following technote:

IBM DB2 Document Manager Version 8.3 cumulative APAR list

Back to top

2. Known problems

This section describes the known problems in DB2 Document Manager Version 8.3 Fix Pack 12.

2.1 Do not use DB2 Content Manager Status attribute with DB2 Document Manager

The DB2 Content Manager Client for Windows uses an attribute called Status, which is described as Workpackage Status. Do not use this attribute with DB2 Document Manager. If you use it on a dialog window, it can cause an error when you add a document.

2.3 The cursor position cannot be controlled in a Microsoft Outlook item

The Microsoft Outlook API that DB2 Document Manager uses to implement Outlook integration does not support control of the cursor position for placement of attachments in an Outlook item.

2.4 Invalid class attribute causes DB2 Document Manager operation to fail

If you specify a value that is not valid for a document's class attribute in the Power Modify window, any DB2 Document Manager operation that must read the class configuration will fail. The document might become unusable. If this problem happens, use the Power Modify window to reset the class value.

2.5 Long file names truncated

When you add a document to the repository, DB2 Document Manager removes a portion of the document file name that is longer than a certain number of characters. The maximum number of characters varies from 166 to 214, depending on the operating system of the DB2 Document Manager server and the connection protocol between the DB2 Document Manager client and server.

2.6 Complex search queries with a large number of CVL values can result in an error

When it performs complex search queries, DB2 Document Manager sometimes returns a General Internal Error. This error occurs only in some circumstances when a single query contains a particularly large number of conditions. For example, if you combine many OR conditions and LIKE operators in a single search query, the action can result in low search performance or error.

For recommendations on how to perform effective search queries and avoid the error, see the following technote:

IBM DB2 Content Manager Query Performance Guide


2.7 Rendition service sometimes fails for certain applications

Some applications can be started by using the system account. However, some applications require a Windows user account to start the application. To ensure that the rendition service works properly, the application that processes the rendition must be able to run the print command by using the system account if the rendition service is set up to run by using the system account or by using the Windows user account if the rendition service is set up to run by using the Windows user account.

2.7 Equals (=) operator does not work for multi-value searches
Use the contains operator instead of the equals (=) operator when you configure multi-valued searches.

Back to top

3. Quality improvements

This section contains information about quality improvements in this release.

3.1 Application integration: Support for newer versions of integrated applications

Depending on your existing DB2 Document Manager Version 8.3 Fix Pack installation, the installation of DB2 Document Manager Version 8.3 Fix Pack 12 might enable the Desktop to integrate with newer versions of the following applications:

• Lotus Notes
• Autodesk AutoCAD
• Adobe Acrobat (Distiller)
• Lotus Sametime Connect

See System requirements for IBM DB2 Document Manager Version 8.3 Fix Pack 12 for details about supported applications.

3.2 Federal Desktop Core Configuration (FDCC) Compliance

DB2 Document Manager complies with the Federal Desktop Core Configuration (FDCC) for Microsoft Windows XP SP2 and Windows Vista Enterprise.

Important: To use the integration between DB2 Document Manager Desktop and Microsoft Office applications under FDCC, you must undertake specific installation procedures, which are included in the following technote:

How to install IBM DB2 Document Manager Desktop on an FDCC-compliant Microsoft Vista or Windows XP system

3.3 States: An option controls whether security actions are applied after potential attribute value changes

In previous releases, Lifecycle Services applied a state's security actions in the following situations:

• When a document transitioned to the state
• When it processed a Modify properties trigger if any of the security action definitions were based on a library attribute
• When it processed a Checkin trigger if any of the security action definitions were based on a library attribute
  

However, in some situations you might not want security actions to be applied in the latter two cases even if you defined property-based security actions. You might want Lifecycle Services to apply security actions only when a document enters a new state, and/or want Desktop users to be able to set a document's security without Lifecycle Services subsequently resetting the security when it processes Checkin and Modify properties triggers.

Beginning with DB2 Document Manager Version 8.3 Fix Pack 8, you can control whether Lifecycle Services applies security actions when it processes Modify properties and Checkin triggers. Select the New option on the Security page of the New or Modify State Configuration window. If property-based security actions exist, apply all state security actions when you process Checkin or Modify properties triggers.

• Do not select this option if you want Lifecycle Services to apply all security actions only when a document transitions to the state.
  
• Select this option if you want Lifecycle Services to apply all security actions after a user checks in a document or modifies the properties of a document.
  
  Important: Lifecycle Services applies the security actions only if one or more of the security action definitions are based on a library attribute. If none of the security action definitions are based on a library attribute, Lifecycle Services does not apply the security actions when it processes Checkin or Modify properties triggers.

Action required for existing users: If you want the state security behavior of your system to continue to operate as it has in past releases, select the New option on the Security page of the New or Modify State Configuration window.

3.4 Custom dialog box controls: Data exchange file format

When DB2 Document Manager writes item property values to the INI file, it modifies the values in the
following ways:

• Each UNIX or DOS-style line return is replaced with "\n" to prevent the property value from splitting across multiple lines.

For example, if the item property value is an address with multiple lines such as:

350 5th Ave.
New York, NY 10118

The value that is written to the INI file is:

PropertyValue_Y=350 5th St.\NewYork, NY 10118

• Each backslash ("\") character in the item property value is escaped with an additional backslash character to prevent it from being mistaken for part of a line return ("\n") character.

For example, if the item property value is a path such as:

C:\projects\new\designs\

The value that is written to the INI file is:

PropertyValue_Y=C:\\projects\\new\\designs\\

Desktop action plug-ins must undo these modifications before they display item property values to users. When plug-ins save user-modified values to the INI file, they must convert the values back to the expected INI format: each line return is replaced with ''\n'' and each backslash character is replaced with "\\."

After the plug-in finishes, and after the property values are read from the INI file, DB2 Document Manager reverses the INI modifications in memory. As a result of the line return modifications and subsequent reversal, UNIX-style line returns are converted to DOS-style line returns.

3.5 Recommendation: Limit ACLs to 40 pairs of user/group and privilege sets

To take advantage of folder caching and avoid performance delays caused by unnecessary library retrievals, administrators should configure Access Control Lists (ACLs) to include no more than 40 pairs of user/group and privilege sets. Do so by using the built-in DB2 Content Manager group ICMPUBLC or by creating supergroups that contain other groups.

3.6 DB2 Document Manager viewer determines printing access through user privileges

The DB2 Document Manager viewer determines whether a user can print a document by examining the user privileges, not through an ACL, as DB2 Content Manager does. Also, users who do not have printing privileges might still be able to print by opening a document in another application.

Back to top

4. Supplemental installation information

Read this section before you install or upgrade DB2 Document Manager.

4.1 Upgrading to DB2 Document Manager Version 8.3 Fix Pack 12

DB2 Document Manager Version 8.3 Fix Pack 12 requires that a publicly available version of one of the following releases or a custom test fix for one of these releases is installed before you upgrade to Version 8.3 Fix Pack 12:

• DB2 Document Manager Version 8.3 Fix Pack 11
• DB2 Document Manager Version 8.3 Fix Pack 10
• DB2 Document Manager Version 8.3 Fix Pack 9
• DB2 Document Manager Version 8.3 Fix Pack 8
• DB2 Document Manager Version 8.3 Fix Pack 7
• DB2 Document Manager Version 8.3 Fix Pack 6
• DB2 Document Manager Version 8.3 Fix Pack 5
• DB2 Document Manager Version 8.3 Fix Pack 4
• DB2 Document Manager Version 8.3 Fix Pack 3
• DB2 Document Manager Version 8.3 Fix Pack 2
• DB2 Document Manager Version 8.3 Fix Pack 1
• DB2 Document Manager Version 8.3
• DB2 Document Manager Version 8.2

4.2 Hardware and software requirements

This section provides hardware and software requirements for DB2 Document Manager that supersede the information in Chapter 1 of Planning and Installing DB2 Document Manager.

System requirements for IBM DB2 Document Manager Version 8.3 Fix Pack 12 contains a complete list of software requirements for this fix pack.

4.2.1 Repository prerequisites

This section provides repository prerequisites for DB2 Document Manager that supersede the information in Chapter 1 of Planning and Installing DB2 Document Manager.

4.2.1.1 DB2 Content Manager

DB2 Content Manager systems only

DB2 Document Manager Version 8.3 Fix Pack 12 requires DB2 Content Manager Version 8.3 Fix Pack 3A or later.

If you want to take advantage of the support for 32-character item type, attribute, and view names in the DB2 Content Manager system administration client, be sure to install and configure DB2 Content Manager Version 8.3 Fix Pack 4 or later.

DB2 Document Manager Version 8.3 Fix Pack 12 is also compatible with DB2 Content Manager Versions 8.4 and 8.4.2. However, to access DB2 Content Manager Versions 8.4 or 8.4.2, DB2 Document Manager Version 8.3 Fix Pack 12 must use DB2 Information Integrator for Content Version 8.3 Fix Pack 11 or 12.

DB2 Document Manager Version 8.3 Fix Pack 12 cannot access DB2 Content Manager Versions 8.4 or 8.4.1 by using Version 8.4 of DB2 Information Integrator for Content.

In summary, the following are the only configurations that involve DB2 Document Manager Version 8.3 Fix Pack 12 and DB2 Content Manager Version 8.4 that are currently supported:

• DB2 Document Manager V8.3 Fix Pack 12 --> DB2 Information Integrator for Content V8.3 Fix Pack 11 --> DB2 Content Manager V8.4 or V8.4.2 server
• DB2 Document Manager V8.3 Fix Pack 12 --> DB2 Information Integrator for Content V8.3 Fix Pack 12 --> DB2 Content Manager V8.4 or V8.4.2 server

4.3 Microsoft Windows Server 2003 and Windows XP update for Windows Communication Foundation

Microsoft Support provides an update that adds support for the WS-AtomicTransaction protocol to MSDTC and support for the Windows Communication Foundation (WCF) COM+ Integration feature.

The update is free and available from the Microsoft Support Web site. For more information about this update, please review the Microsoft Downloads Web site.

Important: This Windows update is a prerequisite for DB2 Document Manager Version 8.3 Fix Pack 5 and later releases and is a prerequisite for the fix to APAR IO06225a.

Microsoft Windows Server 2003 SP2 systems: This update is not needed on Microsoft Windows Server 2003 SP2 systems.

4.4 Microsoft Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 33

Microsoft Support provides a hotfix that fixes a problem that causes DB2 Document Manager to stop responding. When this problem occurs, an event is not logged in Event Viewer. The cause is an access violation that occurs in the Comsvcs.dll file when it runs a COM+ application on a Microsoft Windows 2000-based computer.

A hotfix for this problem is free and available from Microsoft Support. For more information about this problem, see the Microsoft Web site at:

http://support.microsoft.com/kb/892349/

The hotfix is also included in Microsoft Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Package 33. You should install this hotfix package. For more information about this hotfix rollup package, see the Microsoft Web site at:

http://support.microsoft.com/kb/896720/

The Hotfix Rollup Package 33 contains all of the fixes that were released in the previous Windows 2000 COM+ 1.0 hotfix rollup packages.

Important: This hotfix is a prerequisite for DB2 Document Manager Version 8.3 Fix Pack 5 and later releases, and a prerequisite for the fix to APAR IO06225a.

4.5 IProcessInitializer Interface does not register with Microsoft COM+ Rollups

For Microsoft Windows 2000 systems only: IProcessInitializer Interface does not register with Microsoft COM+ rollups.

To read about this problem and its resolution, which must be performed on servers that already have Rollup Package 33, see the Microsoft Web site at:

http://support.microsoft.com/kb/319776

4.6 Microsoft SOAP Toolkit 3.0 Hotfix

Microsoft Support provides a hotfix that fixes a problem when you use DB2 Document Manager to add or check in files over SOAP to a Windows Server 2003 system. The hotfix is free and available from Microsoft Support, but you cannot download the hotfix from Microsoft's public Web site. You must call Microsoft Support, and they will provide you with a download URL through e-mail. Be sure to mention KB article 894550.

Important: The hotfix is a patch to Microsoft SOAP Toolkit 3.0, so you must install the full toolkit before you apply the hotfix. For more information about this update, please review the Microsoft Downloads Web site.

Install DB2 Document Manager, the Microsoft SOAP Toolkit, and the hotfix for the toolkit in the following order:

1. DB2 Document Manager.
2. The Microsoft SOAP Toolkit 3.0.
3. The Microsoft Windows 2003 hotfix on Windows Server 2003 systems that are hosting the DB2 Document Manager SOAP server support.

4.7 Autodesk AutoCAD 2007 Service Pack 2

Autodesk provides an AutoCAD 2007 service pack that includes a hotfix for failures that can occur when closing, saving, or plotting drawings. For complete information and to download the service pack, see the following AutoCAD Services and Support Web pages:

AutoCAD 2007 Service Pack 2:

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=9444984&linkID=9240618

AutoCAD 2007 Hotfix:

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=8185238&linkID=9240618

Back to top

5. Product documentation and support

This section provides information about the product documentation and support.

5.1 Accessing the documentation

You can access the DB2 Document Manager product documentation at this Web page:
http://www.ibm.com/software/data/cm/docmgr/support.html


5.2 Documentation corrections and clarifications for all DB2 Document Manager Version 8.3 Fix Packs

5.2.1 System Administration Guide

5.2.1.1 Configuring Desktop menu command plug-ins

Source:

Chapter 6: Configuring library elements
Configuring plug-ins
How to configure a plug-in

Clarification:
The following information should be included.
When you configure a plug-in of type Desktop menu command and radio button Command:

• Put the plug-in arguments in the Arguments field. Do not include the arguments with the command in the Command field. This ensures
  that the command string can be clearly distinguished from the command arguments.
• If the command string contains embedded white space, wrap the entire string in double quotation marks ("). Similarly, if a command argument
  contains embedded white space, wrap the argument in double quotation marks.
  

Important: In addition to the command line arguments that you configure, DB2 Document Manager appends a plug-in control settings file to the command line.
The plug-in control settings file is a temporary INI file that DB2 Document Manager creates and writes to the user's profile-based temp folder.

5.2.1.2 DB2 Document Manager service log files reside on the server on which the service is enabled
Source
Appendix A. DB2 Document Manager logging
Enabling service logging

Error
The last sentence in the section does not sufficiently describe the location of the service log file or its naming convention.

Correction
The sentence should read:

The log file for each enabled service is stored in the DB2 Document Manager installation root directory on the DB2 Document Manager server on which the service is enabled.

Default installation directory:
C:\Program Files\IBM\DB2 Document Manager

Log file naming convention:
DMService_LibraryName_ProcessHandleNumber.log

Example log file name:
IBMDMRenditionManager_corporateCM83fp3_1.log

5.2.1.3 DB2 Document Manager does not support items that have more than one base part
Source:
Chapter 5: Configuring item types and classes
Item Types Overview

Clarification:
The following limitation should be included:
DB2 Document Manager does not support items that have more than one base part. For example, an item that contains both the ICMBASE and ICMBASETEXT base parts is not supported.

5.2.1.4 MAPI Notification limitations with Microsoft Outlook
Source:
Chapter 2: Getting Started
Configuring DB2 Document Manager to send notifications to your e-mail account

Chapter 6: Configuring Library Elements
Adding a notification configuration for Microsoft e-mail

Clarification:
The following limitations should be included:

• MAPI Notification only works with Outlook Express and Outlook 2000 SR-1a. Outlook 2000 SP2 and SP3 include additional security features that prevent the DB2 Document Manager Notification Services from connecting to Outlook.

• MAPI Notification only works when Outlook 2000 is configured for Internet Mail Only mode. If it is configured for either Corporate or Workgroup mode, then the DB2 Document Manager Notification Services will not be able to log into MAPI.

5.2.1.5 Group name not applicable to Desktop login
Source
Appendix G: End-user quick reference guide
Starting and logging in to the Desktop
How to start and log in to the Desktop

Error
Step 4 incorrectly mentions the group name as potentially applicable when logging in.

Correction
Step 4 should read:
4. Type your user name and password, then click Log in.

5.2.1.6 Configuring a view
Source
Chapter 3. Designing the Desktop
Views overview
Configuring a view

Error
Steps 7 and 8 contain inaccurate information about your ability to specify 0 (zero) if you do not want to limit the number of items that are returned. 0 (zero) is not a valid value for the lists Maximum # of items returned and Return documents in increments of.

Correction
Steps 7 and 8 should read:

7. From the Maximum # of items returned list, select the number of documents to return from DB2 Document Manager searches. (You can select a number up to 10,000 or type in a number up to 99,999.) If the search results exceed the number you specified, the search returns the last set of items.

8. From the Return documents in increments of list, select the number of documents to return. If the search result exceeds the number of documents you specified, the return increment control allows the user to specify a higher number of documents to display.

5.2.1.7 Determining a sequence of revisions
Source
Chapter 7. Configuring a life cycle
Revisioning

Clarification
Revision numbers are unique but not necessarily sequential because the application reuses the revision numbers of deleted revisions. To identify the most recent revision, find the latest modified date and time. Do not use revision numbers to determine the sequence.

5.2.1.8 Rendition Services overview
Source
Chapter 10. Configuring Rendition Services
Rendition Services overview

Clarification
This section is missing the following important information about a Microsoft Outlook limitation.

Microsoft Outlook limitation: Microsoft Outlook does not support automated printing of e-mail messages that are in HTML format. This means that an attempt by a user to create a rendition of an HTML-formatted e-mail message will fail.

Recommendation: If your users need to print HTML-formatted e-mail messages, they can use an Outlook MSG file viewer that supports HTML e-mail messages. One example is the Priasoft MSG File Viewer and Assessor. To launch the MSG viewer when Rendition Services attempts to create a rendition of an HTML-formatted e-mail message, the viewer must either register a print handler in the Windows registry or support command line arguments and you must add the required registry settings manually.


5.2.1.9 Creating a PDF rendition configuration
Source
Chapter 10. Configuring Rendition Services
Creating rendition configurations
How to create a rendition configuration (step 11 a 5 b)

Clarification
Step 11 a 5 b should read:

Select the If possible, print using associated application option to enable Rendition Services to attempt to convert the rendition source file to PostScript with its native application. If the native application is not present on the server where Rendition Services is running, the default specified application is used.

Requirement: Whenever a Windows application is opened for the first time by a Windows user ID, certain windows open and prompt for user input. These windows must be suppressed from opening each time that the application is launched. Any other automatic windows must also be disabled. For any Windows service, Rendition Services must be able to run unattended. If a window is presented that requires a user to acknowledge the window, Rendition Services cannot run.

Recommendation: When you are first setting up the configurations for Rendition Services, configure Rendition Services to run with the system account and interact with the Desktop. This action provides a certain measure of visual feedback in setting up and troubleshooting the configuration. After you complete your testing, assign a Windows user ID to Rendition Services. Microsoft Outlook is an exception to this recommendation.

• For Microsoft Outlook 2000 and Microsoft Outlook 2002 sites, start and run an instance of Outlook on the server where Rendition Services is running. Configure Rendition Services to run with the system account and interact with the Desktop.

• For Microsoft Outlook 2003 sites, do not start and run an instance of Outlook on the server where Rendition Services is running. Rendition Services starts Microsoft Outlook when it needs it. Configure Rendition Services to run with a Windows user account (not the system account).

5.2.1.10 [ItemData_X] section
Source
Appendix E. Custom dialog controls
Data exchange file
[ItemData_X] section

Clarification
This section is missing information about the PropertyMaxBufferSize_Y entry. The description for this entry should read:

Entry

Description

PropertyMaxBufferSize_Y

Maximum buffer size that is allowed for the library property that is specified by PropertyLabel_Y (where both PropertyLabel_Y and PropertyMaxBufferSize_Y have the same value for Y). The maximum buffer size includes space for an end-of-line character (\n). This means that the real buffer size is PropertyMaxBufferSize - 1. For example, if a property of type character has a PropertyMaxBufferSize of 25, you can store up to 24 characters in that property. This is true for all property types that DB2 Document Manager supports. DB2 Document Manager retrieves this value from the repository. The plug-in should not set this value.

This section is also missing information about the possible data types and the expected format of the data when you are setting a value from a plug-in (by using the entry PropertyUpdateValue_Y).

Data formats

BLOB
DB2 Document Manager does not support properties of data type BLOB.

Character
For properties of data type Character, the type and length are defined in the General section of the Modify Library Property Configuration window.

Example: If the maximum length for properties of data type Character is 254 and a plug-in provides a value that is longer than 254 characters, the value is truncated.

CLOB
DB2 Document Manager does not support properties of data type CLOB.

Date
For properties of data type Date, the value must be in the following format: yyyy-mm-dd-hh.mm.ss.nnnnnn

where:

• yyyy is a 4-digit year value (0000 to 9999)
• mm is a 2-digit month value (01 to 12)
• dd is a 2-digit day value (01 to 31)
• hh is a 2-digit hour value, in 24-hour format (00 to 23); ignored by DB2 Document Manager
• mm is a 2-digit minute value (00 to 59); ignored by DB2 Document Manager
• ss is a 2-digit second value (00 to 59); ignored by DB2 Document Manager
• nnnnnn is a 6-digit microsecond value (000000 to 999999); ignored by DB2 Document Manager

Example:

2008-03-03-08.26.33.000000

If a plug-in provides a value that is not in the above format, DB2 Document Manager ignores the value that is provided and uses the default value of 1970-01-01-00.00.00.000000 (January 1, 1970).

Decimal
For properties of data type Decimal, the length and number of fixed digits is defined in the Decimal length section of the Modify Library Property Configuration window.

Example: If a property of data type Decimal is defined to have a total length of 5 and to have 2 fixed digits, DB2 Document Manager supports values between -999.99 and 999.99.

Double
For properties of data type Double, DB2 Document Manager supports decimal values with a maximum length of 31 digits, including the sign (positive or negative) and the decimal point. Values can have up to 6 digits after the decimal point. Scientific notation (such as 1.234e+02) is not supported.

Long
For properties of data type Long, the minimum and maximum length is defined in the Integer length section of the Modify Library Property Configuration window. Commas, such as the thousandth separator, are not supported.

Short
For properties of data type Short, the minimum and maximum length is defined in the Integer length section of the Modify Library Property Configuration window. Commas, such as the thousandth separator, are not supported.

Time
For properties of data type Time, the value must be in the following format: yyyy-mm-dd-hh.mm.ss.nnnnnn

where:

• yyyy is a 4-digit year value (0000 to 9999); replaced with 1970 by DB2 Document Manager
• mm is a 2-digit month value (01 to 12); replaced with 01 by DB2 Document Manager
• dd is a 2-digit day value (01 to 31); replaced with 01 by DB2 Document Manager
• hh is a 2-digit hour value, in 24-hour format (00 to 23)
• mm is a 2-digit minute value (00 to 59)
• ss is a 2-digit second value (00 to 59)
• nnnnnn is a 6-digit microsecond value (000000 to 999999)

Example:

2008-03-03-08.26.33.000000

Plug-ins must provide the date portion (yyyy-mm-dd) of the Time value, but DB2 Document Manager replaces it with 1970-01-01.

Time stamp
For properties of data type Time stamp, the value must be in the following format: yyyy-mm-dd-hh.mm.ss.nnnnnn

where:

• yyyy is a 4-digit year value (0000 to 9999)
• mm is a 2-digit month value (01 to 12)
• dd is a 2-digit day value (01 to 31)
• hh is a 2-digit hour value, in 24-hour format (00 to 23)
• mm is a 2-digit minute value (00 to 59)
• ss is a 2-digit second value (00 to 59)
• nnnnnn is a 6-digit microsecond value (000000 to 999999)

Example:

2008-03-03-08.26.33.000000

Time stamp values in the data exchange file are in Greenwich Mean Time (GMT). Plug-ins must convert time stamp values to GMT when writing them to the data exchange file.

Variable character
For properties of data type Variable character, the supported character set is defined by the character type that is selected from the Character type list on the Modify Library Property Configuration window. The minimum and maximum length is defined in the Character length section of this same window and does not include the end-of-line character (\n).

Example: If the minimum and maximum lengths that are specified are 0 and 2048, respectively, the property can store a string with up to 2048 characters. DB2 Document Manager allocates a buffer of size 2049 bytes for this value. The last byte is used to hold the end-of-line character.

5.2.1.11 DB2 Document Manager viewer uses the Stellent INSO Engine
Source
Appendix H. DB2 Document Manager viewer
Supported formats

Error
DB2 Document Manager viewer uses the Stellent INSO Engine, not the MS-Tech INSO Engine.

Correction
The DB2 Document Manager viewer uses two engines for rendering viewable documents and images: Bedrock Engine and Stellent INSO Engine.

5.2.1.12 How to specify advanced view configuration settings
Source
Chapter 3. Designing the Desktop
Views overview
Configuring a view
How to specify advanced view configuration settings

Clarification
Because of the fix for APAR IO06566, step 3 differs depending on your content repository type. It should read as follows:

3. To define Desktop expanded view settings, select the Display expanded view indicator [+] option.

Optional for DB2 Content Manager systems.
Required for Domino.Doc and Panagon systems.
Select one or more of the following options:

Display life cycle history object
Allows the user to select and view the life cycle.

Display children cpdoc folder
Allows the user to select the expanded view indicator [+] and view the related files of a document.

Display markup folder
Allows the user to open the folder and view the markups that are associated with the parent file.

Display XML folder
Displays the XML-related objects.


5.2.1.13 How to assign data lists to a Desktop template
Source
Chapter 3. Designing the Desktop
Desktop templates overview
Configuring a Desktop template
How to assign data lists to a Desktop template

Clarification
A note is needed in the Users option section of step 2, which should read:

Users
From cache data
Retrieve the users list from the cache.

From library data
Retrieve the users list from the library.

Tip for DB2 Content Manager systems only: Make sure that Desktop users have the appropriate privilege (SystemQueryUserPrivs) to be able to retrieve the users list from the library. DB2 Content Manager checks the privilege sets of users who attempt to retrieve this list from the library.

DB2 Content Manager systems only: If user lists are configured to display LDAP entries, Desktop users must have the appropriate privilege (SystemQueryUserPrivs) to be able to see the users list. (You configure the display of LDAP entries in user lists by selecting the Distinguished Name option on the New or Modify CVL Configuration window or by selecting the Distinguished Name option on the Role Checks page of the Library Configuration Wizard or the Library Configuration window.)


5.2.1.14 Configuring a CVL
Source
Chapter 4. Configuring shared items
Controlled vocabulary list overview
Configuring a CVL

Clarification
Information about privileges is needed in the Distinguished Name portion of step 6, which should read:

Distinguished Name
Display LDAP (Lightweight Directory Access Protocol) entries that identify and describe authorized users to an LDAP server. This value is relevant only for the User List type.

DB2 Content Manager systems only: Make sure that Desktop users have the appropriate privilege (SystemQueryUserPrivs) to be able to see the users list.


5.2.1.15 Configuring Desktop library objects
Source
Chapter 6. Configuring library elements
Configuring Desktop library objects

Clarification
Information about privileges is needed in the Distinguished Name portion of step 5, which should read:

Distinguished Name
An LDAP (Lightweight Directory Access Protocol) entry that identifies and describes an authorized user to an LDAP server

DB2 Content Manager systems only. Make sure that Desktop users have the appropriate privilege (SystemQueryUserPrivs) to be able to see the users list.

Performance impact: Selecting the Distinguished Name option as opposed to selecting the Name option impacts performance. This performance impact is because the Distinguished Name option must retrieve additional information about the users.


5.2.1.16 Adding a notification configuration for Microsoft e-mail
Source
Chapter 6. Configuring library elements
Configuring a notification for Microsoft e-mail client
Adding a notification configuration for Microsoft e-mail

Error
Step 11b incorrectly identifies the DB2 Document Manager file DdmSmtp.exe as the mail application's executable file, which it is not.

b. In the E-mail application field, type DdmSmtp.exe, the mail application's executable file.

Correction
Step 11b should read:

b. In the E-mail application field, type DdmSmtp.exe.


5.2.1.17 Adding a notification configuration for Lotus Notes e-mail
Source
Chapter 6. Configuring library elements
Configuring a notification for Lotus Notes e-mail client
Adding a notification configuration for Lotus Notes e-mail

Error
Step 11b incorrectly identifies the DB2 Document Manager file DdmSmtp.exe as the mail application's executable file, which it is not.

b. In the E-mail application field, type DdmSmtp.exe, the mail application's executable file.

Correction
Step 11b should read:

b. In the E-mail application field, type DdmSmtp.exe.

5.2.1.18 Adding a Sametime notification using Designer
Source
Chapter 6. Configuring library elements
Configuring a notification for Sametime instant messaging
Adding a Sametime notification using Designer

Error
Step 11b incorrectly identifies the DB2 Document Manager file DdmMsgTo.exe as the instant messaging application's executable file, which it is not.

b. In the E-mail application field, type DdmMsgTo.exe, the instant messaging application's executable file.

Correction
Step 11b should read:

b. In the E-mail application field, type DdmMsgTo.exe.


5.2.1.19 Searching: Filters
Source
Appendix G: End-user quick reference guide
Searching
Filters

Error

The information in this section is out of date. It contains documentation for operators (Starts with and Ends with) that are no longer in the interface.

Correction

This section should read:

Filters are used to compare the property values that you provide in the Search window to the property values that are associated with documents in the library. All documents that meet the search criteria that are specified by the property-filter-value combination are returned in the search results.

Example:

To create a search for all documents with "proposal" in the title:

Property: Title

Filter: Contains

Value: proposal

You can also enter a partial value as part of your search criteria.

• To find a partial value anywhere in a document's property value, specify that partial value.
  
  For example, specify ocume or *ocume* to find both "document" and "dmdocuments."
• To find a partial value at the start of a document's property value, use an asterisk (*) wildcard at the end of the value.
  
  For example, specify docu* to find "document" but not "dmdocuments."
• To find a partial value at the end of a document's property value, use an asterisk (*) wildcard at the beginning of the value.
  
  For example, specify *ments to find "dmdocuments" but not "document."

5.2.1.20 How to add application integration commands
Source
Chapter: 3, Designing the Desktop
Section: Application integration overview
Subsection: Configuring an application integration profile
Subsection: How to add application integration commands

Error
The first MicroStation application command in step 2 contains several typographical errors.
DdmCel - Do not allow use of DdmCel for cel placement (off - allowed)
If this option is not selected, allows use of cell replacement.

Correction
The command description should read:
DdmCell - Do not allow use of DdmCell for cell placement (off - allowed)
If this option is not selected, allows use of cell placement.


5.2.1.21 Adding a Sametime notification using Designer
Source
Chapter: 6, Configuring library elements
Section: Configuring a notification for Sametime instant messaging
Subsection: Adding a Sametime notification using Designer

Error
Step 9d contains information for an invalid option (Copy of Document):
Copy of Document
Attaches a copy of the item to the message.

Correction
Step 9d should read:
d. From the Attachment list, select one of the following options:

• Document Pointer: Attaches a document link to the message. If you select this option, the recipient must have access to the DB2 Document Manager Desktop and library from which the document pointer is stored.
• None: No item is attached.

5.2.1.22 How to configure rules
Source
Chapter: 12, Configuring Automation Services
Section: Configuring Automation Services
Subsection: How to configure rules

Error
The important note at the end of step 7 contains a typographical error.

Correction
The note should read:
Important: The instructions that you provide in the Instructions field can have a maximum of 254 characters.

5.2.1.23 How to define a route and start a document on the route
Source
Appendix G, End-user Quick Reference Guide
Section: Managing processes
Subsection: How to define a route and start a document on the route

Error
Step 18 contains a typographical error.

Correction
The step should read:
18. In the Provide instructions for the item recipients field, type in any instructions for the recipients. You can type up to 254 characters in this field.
5.2.1.24 Optimal number of folders in the root directory

Appendix D, Performance Tuning Guidelines

Section: DB2 Document Manager Services
Subsection: Cache Manager

Appendix G, End-user Quick Reference Guide
Section: Managing Folders

Addition
Best Practice: For optimal memory management, it is best practice to maintain 5000 or fewer folders in the root directory. However, you do not need to restrict the number of folders that are nested inside each root-level folder.

5.2.1.25
Chapter 12, Configuring Automation Services
Section: Configuring automation services
Subsection: How to configure an action

Error
Step 9 incorrectly instructs you to "...type the state to which to transition."
Instead, it should instruct you to "...type the object name of the state, not the display name, to which to transition."

Correction
The step should read:
9. If you are configuring a Transition action type, click the Action tab and in the New State field, type the object name of the state, not the display name, to which to transition.

5.3.2 Planning and Installation Guide

This section describes documentation corrections and clarifications for information in the DB2 Document Manager Planning and Installation Guide.

5.3.2.1 DB2 Document Manager service log files are created in the DB2 Document Manager installation root directory
Source
Chapter 6. Installing or upgrading DB2 Document Manager
Library information
Configuring Cache Manager and other services

Error
In step 3d, the location of the service log file is incorrectly identified as "the DM directory."

Correction
Step 3d should read:

On the Logging page, select Generate Logfiles to create a log that tracks information when the service is logged in.

The log file is created in the DB2 Document Manager installation root directory and is called DM_Service_LibraryName_ProcessHandleNumber.log. If you select this option, you can configure two additional options:

• To log all of the services activities, select the Log Detailed Messages option.
  This option causes the service to run slower. Select the Log Detailed Messages option only if requested to do so by your IBM Support representative.
• Specify the maximum log file size in the Max File Size field.
  

5.3.2.2 Desktop and Designer installable on a single system or multiple systems
Source
Chapter 1: Planning for DB2 Document Manager
System components overview
Configuration examples
Suggested configuration scenarios

Error
The first bullet mistakenly implies that you cannot run both the Desktop and the Designer on the same client system. It currently reads:
“Clients, running either the DB2 Document Manager Desktop end-user application or the DB2 Document Manager Designer system administration application ...”

Correction
The first bullet should read:
"Clients, running the DB2 Document Manager Desktop end-user application, the DB2 Document Manager Designer system administration application, or both the Desktop and Designer applications ..."

5.3.2.3 Notification Services not a base component
Source
Chapter 1: Planning for DB2 Document Manager
System components overview
Configuration examples
Suggested configuration scenarios

Error
Notification Services is incorrectly identified as a base component of the server.

Correction
The second bullet should read:

• DB2 Document Manager server, which includes the following base components:
• Cache Manager
• Lifecycle Services

5.3.2.4 User ID required to manage revision numbers
Source
Chapter 2. Preparing DB2 Content Manager
Creating an administrative account

Error
The first paragraph incorrectly states that the application requires a user ID to manage version numbers. It requires a user ID to manage revision numbers, not version numbers.

Correction
Paragraph 1 should begin:

DB2 Document Manager requires a user ID to manage life cycle processes and history, uniqueness checking, and revision numbers.


5.3.3 Message Reference

This section describes documentation corrections and clarifications for information in the DB2 Document Manager Message Reference.

5.3.3.1 DDM20744E
Source
Chapter 2. Messages for DB2 Document Manager

Error
The message DDM20744E is not included in the Message Reference.

Correction
The message should read:
DDM20744E: ERROR: The maximum number of object lock interaction was exceeded.

Back to top

5.5 Support Web page

For any questions, concerns, or problems related to DB2 Document Manager or to access the product documentation, visit this Web site:
http://www.ibm.com/software/data/cm/docmgr/support.html

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
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 states 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.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Trademarks

See http://www.ibm.com/legal/copytrade.shtml for information about IBM trademarks.

Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

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

Back to top