z/OS DFSMSdfp Storage Administration
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Defining secondary lock tables

z/OS DFSMSdfp Storage Administration
SC23-6860-01

You can define multiple secondary VSAM RLS lock structures to be associated with a single SMS storage class. A secondary lock structure is identified by an SMS storage class attribute called a lock set. You can define up to 256 lock sets per sysplex. Each lock set can contain a single lock structure name. When an application opens a VSAM data set, RLS processing checks the storage class defined for the data set to determine which lock structure to use. If the storage class specifies a secondary lock structure, RLS processing uses the secondary lock structure to serialize access to records in the data set.

If you do not define secondary lock structures, VSAM RLS uses the primary DFSMS CF lock structure, the IGWLOCK00 lock table, to hold the record locks. However, using a single lock structure forces DFSMS to combine all locking information for all instances of the SMSVSAM address space in the same lock structure. That might cause differing workloads to interfere with each other and affect system and application availability. You can use secondary lock structures to help prevent locking constraints and allow isolation of workloads.

Follow these steps to implement VSAM RLS multiple lock table:

  1. Define the names, sizes and preference locations of the new lock tables in the CFRM policy using the IXM utility.

    _______________________________________________________________

  2. Activate the new CFRM policy.

    _______________________________________________________________

  3. Define the names of the new lock tables in the SMS control data set (CDS) using the ISMF Control Data Set function or Naviquest. Specify the name of a lock set and one lock structure per lock set (you can use the same lock structure for multiple lock sets). If you do not specify the names of the new lock sets, RLS processing uses the primary lock structure, IGWLOCK00, for all record locking.

    _______________________________________________________________

  4. Use ISMF or Naviquest to add the lock set name to each storage class for which you requested multiple lock table. Otherwise RLS processing uses IGWLOCK00 for all record locking.

    _______________________________________________________________

  5. Validate and activate the SMS configuration to allow the new definitions in the Source Control Data Set (SCDS) to take effect.

    _______________________________________________________________

  6. Allocate VSAM data sets using the storage classes that contain the new lock set names.

    _______________________________________________________________

  7. Update ACS routines.
Note:
  1. Secondary lock structures are used for record locks only. When secondary lock structures are used, IGWLOCK00 is still required for other types of locks. IGWLOCK00 is required for the initialization of the SMSVSAM address space.
  2. The number of lock structures that are concurrently connected varies and depends on the value of MAXCAD specified in the IEASYxx member that is used for system initialization. There might be 10-14 lock structures, including IGWLOCK00, connected at the same time.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014