Figure 1 shows the hardware and software in a typical OAM object environment and illustrates the possible interactions. The OAM object environment is closely tied to SMS and DB2. OAM also interacts with the OAM thread isolation support (OTIS). OTIS is an OAM subsystem that provides OAM-to-DB2 functions that use a different thread to DB2 than the application program thread. Applications can use OSREQ, the application programming interface, to interact with OAM. Applications can also communicate directly with DB2. Each application is responsible for synchronizing its DB2 databases, whether the operation is generated by the application or by OAM.

Figure 1. OAM Interactions with Software and Hardware