11.01.2013 Views

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Specify SHAREOPTIONS(3,3) for the ACDS and COMMDS. These data sets must be shared<br />

between systems that are managing a shared DASD configuration in a DFSMS environment.<br />

Define GRS resource names for active SMS control data sets<br />

If you plan to share SMS control data sets between systems, consider the effects <strong>of</strong> multiple<br />

systems sharing these data sets. Access is serialized by the use <strong>of</strong> RESERVE, which locks<br />

out access to the entire device volume from other systems until the RELEASE is issued by the<br />

task using the resource. This is undesirable, especially when there are other data sets on the<br />

volume.<br />

A RESERVE is issued when SMS is updating:<br />

► The COMMDS with space statistics at the expiration time interval specified in the<br />

IGDSMSxx PARMLIB member<br />

► The ACDS due to changes in the SMS configuration<br />

Place the resource name IGDCDSXS in the RESERVE conversion RNL as a generic entry to<br />

convert the RESERVE/RELEASE to an ENQueue/DEQueue. This minimizes delays due to<br />

contention for resources and prevents deadlocks associated with the VARY SMS command.<br />

Important: If there are multiple SMS complexes within a global resource serialization<br />

complex, be sure to use unique COMMDS and ACDS data set names to prevent false<br />

contention.<br />

For information about allocating COMMDS and ACDS data set names, see z/<strong>OS</strong> DFSMS<br />

Implementing <strong>System</strong>-Managed Storage, SC26-7407.<br />

272 <strong>ABCs</strong> <strong>of</strong> z/<strong>OS</strong> <strong>System</strong> <strong>Programming</strong> <strong>Volume</strong> 3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!