Problem

How is managed the CFT's resources protection

GRS multi-system protection

Resolution

Transfer CFT uses QNAME CFTSHARE to protect various resources.

QNAME CFTSHARE must be propagated in all members of a GRS configuration.
This is the only QNAME to be propagated.

Transfer CFT uses the following other QNAMEs:
· CFTFILES to protect transferred files
· CFTSUBM to serialize JOBS submitted on the Internal Reader
· CFTPUTS for general internal serialization
· CFTCATSH to share the catalog dataspace

The CFTFILES ENQs do not need to be broadcasted to all systems in the GRS RING.

Note:
major ENQ are CFTSHARE, CFTCATSH, CFTPARM and CFTFILES

The display command below will list all current ENQs
D GRS,RES=(CFT*,*)

Note about license keys:
Since CFTV3, license keys can also be locked to force one separate key per monitor.
(it does not apply to beeper and label license keys)

Note: The only case you can share the same license key based on the CPU_ID in between several CFTs is when they are all installed on different physically or logically isolated LPARs (CFTSHARE QNAME not propagated).