Planning to program applications for OAM

The z/OS DFSMS OAM Application Programmer's Reference describes the OSREQ macro, the programming interface provided by OAM. This document contains detailed information about programming applications which use OAM.

As you consider OAM programming applications, keep in mind the following items:

Application design plays a significant role in OAM performance. For example, careful use of buffering can reduce virtual storage requirements.
Application programs are responsible for synchronizing OAM-related DB2 databases (for example, using SYNCPOINT under CICS).
The auto-delete installation exit can be programmed specifically for an application, as described in Auto-delete installation exit (CBRHADUX).
ACS routines must be programmed.
Maintenance of the auto-delete installation exit and ACS routines is generally the responsibility of the storage administration team. However, a particular application might require modification to use the exit and the ACS routines.
When objects are stored directly to the file system sublevel from an application program, the application must perform the DB2 "commit" within 24 hours of storing the object. Failure to do this will ultimately result in loss of object data stored in the file system.