text: **OAM DB**
  
  **Shared Data**
  
  *Figure 12-6 Scalability: Parallel Sysplex/multiple LPARs (z/OS)*
  
  Figure 12-6 illustrates an example of a two-system Content Manager OnDemand Parallel 
  Sysplex implementation. z/OS system A contains a library server and an object server. The 
  library server and object server can be either combined in a single executable file (most 
  common z/OS implementation) or separated into two executable files, in which case they are 
  installed in separate LPARs. z/OS system B shows a multiple LPAR system with a combined 
  library/object server that is installed in each of the LPARs. 
  
  Both of these systems (all LPARs and all instances of the Content Manager OnDemand 
  server) access a single set of Content Manager OnDemand database tables through DB2 
  data sharing. They also access a single OAM archive system through an OAMplex. Not 
  shown in the figure is the access to a single Job Entry Subsystem (JES) spool and a shared 
  file system (which consists of a set of hierarchical file systems (HFS) or z/OS file systems 
  (zFS). The term “single” is used to imply that the same set of data is available to all systems 
  concurrently. Each of these single systems consists of highly redundant components and 
  therefore do not represent a SPOF. 