Previous Topic: Separate CA 1 TMCs and Separate OAM TCDBsNext Topic: Separate CA 1 TMCs and Common OAM TCDB


Common CA 1 TMC and Separate OAM TCDBs

This method is not recommended, however it can be done. This provides the user with the ability to logically partition the Tape Library (with separate TCDBs) but still have a common CA 1 TMC. This creates a problem because the entry exit (CTSUXENT in hlq.CTAPSAMP library) needs to be modified on both systems, and the ROBSCR scratch option should NOT be enabled (ROBSCR=NO). The entry exit on CPUA needs to have all the CPUB cartridges defined to it, and not take ownership of them (even though they are defined to the TMC.) This additional code is best to be performed prior to the "ASKCA" label because all of the cartridges are known to both systems (because they share a common TMC). So, on CPUA before the ASKCA label, you must compare the volser and see if it is owned by CPUB. If it is, branch to label RC16 (leave it in insert status for CPUB to take ownership). This also applies to CPUB, the exit must look for CPUA cartridges and branch to label RC16 for them (so CPUA takes ownership of its cartridges.) If you want to share a common exit on both systems, the exit needs to be modified to look at the SMFID or SYSTEM-NAME and determine if the volser should be owned or not based on the combination of which system it is running on, and which tape is being inserted.

It is best to disable the real-time scratch interface by setting ROBSCR=NO in the TMOOPTxx member. Instead, break the scratch list created by TMSCLEAN and into two separate lists. One list consists of CPUA owned scratch tapes and the other is a list of CPUB owned scratch tapes. Then, on each system run CTSSYNC taking in the correct list of scratch tapes (CTSSYNC can be run with PARM=SYNC and the sysin is simply a list of cartridges.)