About this task
To setup VSAM RLS , two levels of changes are needed: System-level
change and VSAM-level change.
Procedure
- System-level change
- Define Sharing Control Data Set (SHCDS)
- Define CF cache structures
- Define CF lock structures
- SMS definitions
- Modifying the PARMLIB IGDSMSxx Member
- VSAM-level change
- Change LOG parameter. VSAM RLS requires adding LOG
parameter to IDCAMS, so the IA administrator needs to alter/define
data set as:
- LOG(UNDO/ALL) : Indicates file is recoverable
- LOG(NONE) : Indicates file is non-recoverable
- Change storage class parameter. VSAM RLS requires RLS
data sets must be assigned to a storage class with a cache set defined
and must be SMS managed.
Example
The following is an example of how to define a VSAM RLS data
set:
DEFINE CLUSTER (NAME(SIBIN.CCZVSAM.BASE) -
INDEXED -
CYLINDERS(8 100) -
LOG(NONE) -
STORCLAS(NORMALG) -
DATACLAS(NOCACHE) -
KEYS(58 0) -
CISZ(18324) -
SHR(2 3) -
RECORDSIZE(112 112))
What to do next
Some tips on VSAM RLS performance tuning:
- The minimum cache size is 30M, because XCF needs some room for
structures control.
- RLS_Max_Pool_Size should be 20 percent larger than cache size,
because the LRU becomes active after the pool is 80 percent full
and starts aging buffers out.
- False contention is related with lock structure size only. If
false contention is high, lock structure size should be increased.
- For single system, set up a DATACLASS for VSAM RLS and set RLSCFCACHE(NONE)
parameter for this data class. This will improve performance.
- Too large AIX record size will downgrade the VSAM RLS performance.