Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Using an API to serialize resources z/OS MVS Planning: Global Resource Serialization SA23-1389-00 |
|||||||||||||||
You can choose from the following macros to serialize access to
global resources:
Guideline: As of z/OS® V1R6, IBM® recommends using the ISGENQ service for unauthorized serialization requests, although the ENQ, DEQ, and RESERVE interfaces will continue to be supported. The following table shows how to serialize access to resources
at three levels:
Note: To serialize access to resources across sysplexes and
between VM and z/OS establish
a reserve through the RESERVE macro or ISGENQ macro with the RESERVEVOLUME=YES
parameter. Because this serialization involves I/O to the entire volume;
you lose much of the granularity of the qname and rname resource abstraction.
As of z/OS V1R6, use the ISGENQ macro to obtain, change, release resources, test an obtain request, and reserve a DASD volume. For detailed information about using the ISGENQ macro:
The RESERVE macro obtains access to a resource and the DEQ macro frees the resource. The RESERVE macro, by default, has a scope of SYSTEMS. The corresponding DEQ macro must specify a scope of SYSTEMS. The ENQ macro with a scope of SYSTEMS obtains access to a resource. The DEQ macro frees the resource when you specify a scope of SYSTEMS. Guideline: Some applications may require specific RNL changes
for ENQs or related products that are installed.
Note:
|
Copyright IBM Corporation 1990, 2014
|