Setting up the planning team

To most effectively implement OAM, your planning team should include individuals with significant technical expertise in the following areas:

DFSMS-Related Products. OAM is a component of DFSMS and interacts closely with other members of the DFSMSdfp family of products. Knowledge of system-managed storage (SMS) and the interactive storage management facility (ISMF) is essential for successful planning and implementation. Additionally, familiarity with DFSMShsm and the other DFSMS components provides a meaningful context for understanding OAM.
DB2. OAM uses DB2 databases to store objects and internal information (such as object indexes). Implementing OAM for objects is likely to have a significant impact on your installation’s DB2 space requirements. If OAM is to be set up in a Parallel Sysplex, DB2 data sharing installation and knowledge is also required.
Catalogs. OAM uses collections to subdivide object data within Object storage groups. Collections must be cataloged.
File systems. If OAM is to use a file system, the planning team must evaluate the file systems provided by Network File System (NFS) and zFS.
Customer Information Control System (CICS). If OAM is invoked by CICS transactions, the planning team must evaluate the effect of their interaction.
Hardware Configuration Definition (HCD). HCD is used to define devices to the hardware configuration.
Information Management System (IMS). If OAM is invoked by IMS transactions, the planning team must evaluate the effect of their interaction.
Time Sharing Option/Extended (TSO/E). If OAM is invoked by TSO/E transactions, the planning team must evaluate the effect of their interaction.
Cross-system Coupling Facility (XCF). If OAM is to be established in a Parallel Sysplex, the planning team must evaluate the impact to the coupling facility requirements and resources.

As with any major installation, the OAM planning effort should also involve people with project management experience and representatives of the end-user areas that are affected by the implementation.