Using VSAM local shared resources (LSR)

Effects

CICS® always builds a control block for LSR pool 1. CICS builds control blocks for other pools if either a LSR pool definition is installed, or a file definition at CICS initialization time has LSRPOOL= defined with the number of the pool.

Where useful

VSAM local shared resources can be used in CICS systems that use VSAM.

Recommendations

See VSAM tuning: general objectives.

How implemented

CICS uses the parameters provided in the LSR pool definition to build the LSR pool.

How monitored

VSAM LSR can be monitored by means of response times, paging rates, and CICS LSRPOOL statistics. The CICS LSRPOOL statistics show string usage, data set activity, and buffer lookasides (see LSRpool statistics).

Related tasks
VSAM and file control: improving performance
VSAM tuning: general objectives
Defining VSAM buffer allocations for NSR (INDEXBUFFERS and DATABUFFERS)
Defining VSAM buffer allocations for LSR
Defining VSAM string settings for NSR (STRINGS)
Defining VSAM string settings for LSR (STRINGS)
Specifying maximum keylength for LSR (KEYLENGTH and MAXKEYLENGTH)
Specifying resource percentile for LSR (SHARELIMIT)
Using Hiperspace buffers
Permitting VSAM subtasking (SUBTSKS=1)
Using data tables to improve performance
Using coupling facility data tables to gain performance benefits
Performance aspects of VSAM record-level sharing (RLS)
[[ Contents Previous Page | Next Page Index ]]