This is not a recommended method to use, however it can be done. This gives the user the ability to logically partition the 3494 (with separate TCDBs) but have a common CA TLMS VMF. The problem is that the entry exit (CTSUXENT in CAI.CTAPSAMP) would need to be modified on both systems AND there would need to be additional modification to the TLMU003 usermod (the SCRATCH exit TLMSRACF). The entry exit on CPUA would need to have all the CPUB cartridges defined to it, and not take ownership of them (even though they are defined to the VMF). This additional code would best be done PRIOR to the "ASKCA" label, since you know that all the cartridges are known to both systems (since they share a common VMF). So, on CPUA before the ASKCA label you would have to compare the volser and see if it is owned by CPUB. If so, then branch to label RC16 (leave it in insert status for CPUB to take ownership). Likewise on CPUB, the exit would have to look for CPUA cartridges and branch to label RC16 for them (so that CPUA could take ownership of its cartridges). If there is a desire to share a common exit on both systems, then the exit will need to be modified to look at the SMFID or SYSTEM-NAME and make the determination if the volser should be owned or not based on a combination of which system it is running on and which tape is being inserted.
In this environment it would be best to not use the TLMSRACF scratch exit and to instead use multiple CTSSYNC jobs; one to process all scratch tapes owned by CPUA and the second to process all scratch tapes owned by CPUB. A CA Earl report would have to be written to select scratch tapes based on creating system SMFID (CPUA and CPUB) writing the output to separate transaction files. Then, on each system CTSSYNC would be run taking in the correct list of scratch tapes (CTSSYNC can be run with PARM=SYNC and the SYSIN would simply be a list of cartridges).
|
Copyright © 2014 CA.
All rights reserved.
|
|