Previous Topic: Common CA TLMS VMF and Separate OAM TCDBsNext Topic: CA Vtape


Separate CA TLMS VMFs and Common OAM TCDB

This is not a recommended method to use and should be avoided. Since CPUA and CPUB have a common OAM TCDB, then any tape could 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 manual), the problem of shared scratch pool could be removed. However, it would still be possible to request a specific volume from either system for any volume. Since each CA TLMS would only know about its tapes and not about the other system's tapes, they would appear as FOREIGN. So using EXPDT=98000 you could read (or update) active tapes from the other system. So in this case, you would have to tightly restrict the use of EXPDT=98000 processing. If not, then anyone that has access to EXPDT=98000 processing could request tapes from the other system and read and/or modify the existing data. Since full 44-character dataset name checking would NOT be available, external security rules would not be sufficient.

The entry and eject exits could be used as shipped with CA TLMS without modification. The TLMU003 usermod to implement immediate scratch processing could be implemented on both systems.