z/OS MVS Planning: Global Resource Serialization
z/OS MVS Planning: Global Resource Serialization
Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Temporary data sets z/OS MVS Planning: Global Resource Serialization SA23-1389-00 |
|
If you take no action, global resource serialization treats non-VIO temporary data sets as global resources. One reason for letting temporary data sets be global resources is that your installation can then run scratch functions (such as SCRATCH VTOC,SYS) safely at any time against shared volumes. If your installation wants global resource serialization to treat
temporary data sets as local resources, the data set names must appear
in the SYSTEMS exclusion RNL. However, the format of a temporary data
set name is not compatible with the format of a generic RNL entry.
So a pattern entry that contains wildcard characters is necessary
to extend the matching specification. The format of a temporary data
set name is one of the following:
If you want GRS to treat temporary data sets as local resources,
use the following RNLDEF in the appropriate GRSRNLxx parm member to
create a pattern RNL entry.
For more information on a pattern resource name, see How the RNL is scanned. 
|
 Copyright IBM Corporation 1990, 2014 |
