Previous Topic: Common CA 1 TMC and Separate OAM TCDBsNext Topic: CA Vtape Virtual Tape System


Separate CA 1 TMCs and Common OAM TCDB

Important! This method is not recommended and should be avoided if at all possible.

CPUA and CPUB have a common OAM TCDB. Any tape can be mounted to satisfy a scratch request on either system. By having different categories defined on each system (this is done by modifying SYS1.PARMLIB members as explained in the OAM PISA guide), the problem of shared scratch pools can be removed. However, it is still possible to request a specific-volume from either system for any volume. CA 1 only knows about its tapes and not about other system tapes. Other system tapes appear as FOREIGN. Using EXPDT=98000 you can read (or update) active tapes from the other system. In this case, you must tightly restrict the use of EXPDT=98000 processing. If you don't, anyone that has access to EXPDT=98000 processing can request tapes from the other system and read, modify or both, the existing data. The full 44-character data set name checking is not available. External security rules are not sufficient.

The entry and eject exits can be used as shipped with CA 1 without modification and the real-time scratch processing performed with the ROBSCR option can be run on both systems.