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.

4.44 VSAM: Buffering modes<br />

User<br />

ACB<br />

MACRF=<br />

(LSR,NUB)<br />

INDEX<br />

Data<br />

INDEX<br />

User ACB<br />

MACRF=<br />

(LSR,NUB)<br />

Data<br />

User ACB INDEX<br />

MACRF=<br />

(LSR,NUB)<br />

Buffers and I/O related control blocks<br />

associated with a pool (BLDVRP)<br />

Multiple data sets share pooled resources<br />

Figure 4-54 VSAM LSR buffering mode<br />

Data<br />

VSAM buffering modes<br />

The VSAM buffering modes that you can use are:<br />

► NSR, LSR, GSR, and RLS<br />

Buffers and I/O related<br />

control blocks<br />

Non-shared resource (NSR)<br />

Non-shared resource (NSR) is the default VSAM buffering technique. It has the following<br />

characteristics:<br />

► The resource pool is implicitly constructed at data set open time.<br />

► The buffers are not shared among VSAM data sets; only one cluster has CIs in this<br />

resource pool.<br />

► Buffers are located in the private area.<br />

► For sequential reads, VSAM uses the read-ahead function: when the application finishes<br />

processing half the buffers, VSAM schedules an I/O operation for that half <strong>of</strong> the buffers.<br />

This continues until a CA boundary is encountered; the application must wait until the last<br />

I/O to the CA is done before proceeding to the next CA. The I/O operations are always<br />

scheduled within CA boundaries.<br />

► For sequential writes, VSAM postpones the writes to DASD until half the buffers are filled<br />

by the application. Then VSAM schedules an I/O operation to write that half <strong>of</strong> the buffers<br />

to DASD. The I/O operations are always scheduled within CA boundaries.<br />

Chapter 4. Storage management s<strong>of</strong>tware 177

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

Saved successfully!

Ooh no, something went wrong!