IBM® ImagePlus® for OS/390® consists of three components:
- ImagePlus Object Distribution
Manager (IODM)
- ImagePlus Folder Application
Facility/Application Programming Interface (IPFAF/API)
- ImagePlus Folder Application
Facility/Folder Workflow Application (IPFAF/FWA)
Content Manager Version
8 provides migration utilities designed for customers who
use all three of these ImagePlus components.
Running these migration utilities:
- Does not migrate your actual object data, because it
is not necessary. ImagePlus stored
your objects using the Object Access Method (OAM), which is a component
of DFSMS. Content Manager
Version 8 continues to use OAM for object storage and retrieval,
so moving the actual objects is not a necessary part of the migration
process. Because the objects stay where they are, you can maintain
your current strategy with respect to the OSMC component of OAM for
backups and the transitioning of objects from DASD to other media
(for example, optical or tape). However, you cannot continue the current
strategy with respect to the OSMC expiration of objects. To synchronize the Content Manager metadata with the objects deleted from OAM, you can create a custom application using the Content Manager application programming interface (API) or use the OAM CBRHADUX exit to automatically delete metadata from the library server after its corresponding resource manager object has been deleted by integrating with the batch delete utility. You can also prevent the deletion of an expired resource manager object if retention management is enabled. Note that resource manager configurations with Tivoli® Storage Manager do not apply. See Configuring the optional Content Manager for z/OS high-volume batch update utility for more information.
Tip: You can avoid
the use of the object expiration functionality of OSMC and instead
use item retention within the item type in conjunction with an application
that deletes objects based on the item retention specification for
the item type. After the item retention is set, the value in the EXPIRATIONDATE
column in the root component table for the item type is set for documents
that are subsequently imported. If you are migrating documents from ImagePlus for OS/390 into a Content
Manager Version 8 release and you plan to use the expiration date
for objects, you must set the value in the EXPIRATIONDATE column properly
as part of the migration. Content
Manager Version 8 releases do not have a utility for expiring documents,
but the expiration date could be used by a custom application. In this case, you need to assign an expiration date to the data after the migration. This can be accomplished by writing a program or contracting with IBM or an IBM Business Partner to write the program for you. The date assigned would most likely be related to the definitions associated with the storage and management classes assigned to each item.
- Does not migrate your IODM data. In ImagePlus, object requests are routed to
IODM, which retrieves the object from OAM and sends it to the ImagePlus Workstation Program
(IWPM). In Content Manager
Version 8 Release 5, the resource manager performs the same function,
retrieving objects from OAM.
Basic document pointer structure is stored in IPFAF/API DB2 tables. Some of the major structural
components are a function of the front-end application that calls
IPFAF/API. The utilities are specifically designed for customers who
use IPFAF/FWA as their front-end application. If you have deployed
a customized front-end application, you might be able to use the utilities
or some portion of them after careful study. You can contract with IBM for assistance.
Tip: Content Manager Version 8 Release 5 for z/OS does not have the same built-in
batch processing capabilities that ImagePlus OS/390 has. If you want to do
batch processing, you might need to use business partner code or write
your own applications.
