Resource classes processed by GDIF and ECMF are known as managed resources. The names of these classes are specified in the QNAME list (see Creating a QNAME List in this chapter). You can tell GDIF to add classes to the list by running in PROCESS=ALLSYSTEMS mode. When GDIF adds a class while running in PROCESS=ALLSYSTEMS mode, it specifies ECMF=NO for the newly added class: ECMF gives no contention warnings for the newly added class. If you want to receive a contention warning for the newly added class, then you should include the class in the MIMQNAME member, instead of adding the class while running in PROCESS=ALLSYSTEMS mode.
When GDIF serializes a resource class, it propagates requests for that resource to other CA MII systems. The GDIF keyword of the QNAME statement controls this. The exempt list lets you specify that some resource names of the class be propagated, while other names of the class are not.
When GDIF serializes a resource class, it can optionally suppress hardware RESERVEs; the RESERVES keyword of the QNAME statement controls this. When the hardware RESERVE is suppressed, the RESERVE macro is considered to be converted. When you convert a RESERVE, you rely on GDIF to provide the serialization: other systems can continue to access the device. Other systems can read or update data sets that reside on that device, but GDIF ensures that other systems cannot gain ownership of the resource whose name was specified on the RESERVE macro. By converting the RESERVE, GDIF lets the RESERVE macro serialize individual data sets instead of “locking up” every data set on the device. Note that the exempt list, described later in this chapter, lets you specify that some resource names of the class should convert the RESERVE, while other names of the class should use hardware RESERVE serialization.
|
Copyright © 2014 CA.
All rights reserved.
|
|