Requests That Should Not Be Propagated

You may not want to propagate requests for the following data set-type resources:

System data sets that are replicated on different systems. Because each system has a unique copy of these data sets, you may not want to issue global ENQ requests for them.
Shared data sets that need to be accessed concurrently from different systems and are serialized across systems by the tasks that use them. If you are in doubt, check with the product vendor.
ISPF LIST, LOG, and PROFILE data sets that are associated with a TSO session for a specific user. You may not want to propagate requests for these resources because TSO users usually log on to one system at a time.
Resources for which you want controlled integrity exposures. For example, the CICS or IMS products can keep data sets open indefinitely if you run these products around the clock. Some sites then run reports or other read-only jobs on other systems because this is the only alternative to stopping the product, running the job, and then restarting the product. If you are controlling integrity exposures manually and you do not want to change the procedures of your site, then you need to tell GDIF not to propagate requests for those resources.
Resources that are serialized through RESERVE by both z/OS and z/VM. You should not convert reserves issued by a z/OS system that protect a resource that is shared with a z/VM system. CA ACF2 and CA Top Secret are examples of products that can run on both z/OS and z/VM.