Certain partial upgrades of DB2 Content Manager for z/OS V8.3 or V8.4 components might cause unintended document replacement
A condition has been identified where under very specific circumstances (specified in the following information), an update to an object previously stored in the DB2 Content Manager z/OS resource manager might be unintentionally replaced when a new version of the object was intended to be created. In such cases, the version that was updated will be deleted.
The problem might or might not be evident when it occurs. It becomes evident if an object with an external object name is updated or modified and then subsequently there is an attempt to display the object. In such cases, the user will receive an OAM error: return code 8, reason code 2C040100. If there is no attempt to display the updated or modified object, there will be no immediate symptom evident, but the condition will still exist.
This condition was first identified in DB2 Content Manager V8.3. A fix in the DB2 Content Manager z/OS resource manager (APAR PK53986) was delivered in DB2 Content Manager V8.3 FP7 (PTFs UK32427 and UK32428). An equivalent fix was included in the DB2 Content Manager z/OS V8.4 product at general availability. In DB2 Content Manager V8.3 FP9 a replacement solution was delivered with APAR PK64318 to resolve the problem by using the Java and C++ APIs. Subsequently, the DB2 Content Manager z/OS resource manager fix in FP7 was removed in FP9 with PTF UK39841. Equivalent fixes with the APIs were also delivered for DB2 Content Manager Enterprise Edition (EE) V8.4.1 or later and DB2 Content Manager z/OS V8.4.1 or later at their general availability. Such resolutions of the problem, however, require use of the APIs with the replacement solution, and the APIs with the solution exist only in the DB2 Content Manager API V8.3 FP9 or later, or DB2 Content Manager API V8.4.1 or later. The DB2 Content Manager APIs at V8.4 do not contain the fix.
Who is affected:
All DB2 Content Manager z/OS resource manager customers that have not upgraded to DB2 Content Manager V8.4.1 or later for all components, (library server, resource manager, toolkit, APIs and clients), both Enterprise Edition (all supported operating systems) and DB2 Content Manager for z/OS, are potentially affected. Any DB2 Content Manager z/OS environments earlier than DB2 Content Manager V8.3 FP7 are also affected when the specific circumstances (specified in the Specific circumstances under which the problem occurs section) exist.
The error condition does not arise in any of the following environments (each of which have a fix in either the resource manager itself (with DB2 Content Manager 8.3 FP7) or in the API/client solution introduced in DB2 Content Manager 8.3 FP9 or later):
- DB2 Content Manager for z/OS resource manager V8.3 FP7 or FP8, and DB2 Content Manager APIs/clients any version and fix pack
- DB2 Content Manager for z/OS resource manager V8.3 FP9 and later, and DB2 Content Manager APIs/clients V8.3 FP9 and later
- DB2 Content Manager for z/OS resource manager V8.4, and DB2 Content Manager APIs/clients any version and fix pack
- DB2 Content Manager for z/OS resource manager V8.4.1 or later, and DB2 Content Manager APIs/clients V8.3 FP9 and later
- DB2 Content Manager z/OS resource manager V8.4.1 or later, and DB2 Content Manager APIs/clients V8.4.1 or later
In any other DB2 Content Manager for z/OS resource manager environment, the problem will occur under the specific circumstances specified as follows.
Note: In addition, if any of the following upgrade paths are taken from any of the unaffected environments listed in this section, the error condition might be reintroduced to the new environment:
- DB2 Content Manager z/OS resource manager remains at V8.3 with FP9 or later, and the DB2 Content Manager APIs/clients are upgraded from V8.3 FP9 or later to V8.4. (Note: Upgrading the DB2 Content Manager APIs/clients to V8.4.1 or later will not result in reintroduction of the condition.)
- DB2 Content Manager APIs/clients remain at V8.3 FP8 or earlier, and the DB2 Content Manager z/OS resource manager is upgraded to V8.4.1 or later.
Specific circumstances under which the problem occurs:
The error condition might occur only when all of the following conditions exist:
- Part level versioning is being used.
- External object names are being used for new object stores, or were used at some previous point. (Note: The DB2 Content Manager V2.3 and ImagePlus migration utilities migrate the object name to the external object name attribute in DB2 Content Manager V8.x. Therefore, if your environment was a migration from DB2 Content Manager V2.3 or ImagePlus, this condition still exists, even if the DB2 Content Manager V8.x implementation is not using external object names.)
- An object stored with an external object name is updated or modified.
If you have or had an affected environment as explained in the Who is affected section, the entire DB2 Content Manager environment (that is, all components) needs to be updated to DB2 Content Manager V8.4.1 or later in parallel. This action must be taken on all DB2 Information Integrator for Content or Information Integrator Content Edition servers, all DB2 Content Manager Windows client workstations, and for the DB2 Content Manager z/OS resource manager.
This condition is resolved if you are using all components of DB2 Content Manager V8.4.1 or later. If you use all DB2 Content Manager 8.4.1 or later components (library server, resource manager, toolkit, APIs and clients), then this problem does not occur.
If you have any questions or concerns, contact IBM Software Support.
More support for:
Content Manager for z/OS
Software version: 8.3, 8.4, 18.104.22.168, 8.4.1, 22.214.171.124, 8.4.2
Operating system(s): z/OS
Reference #: 1397419
Modified date: 17 December 2009
Translate this page: