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.

BSAM support<br />

For BSAM in z/<strong>OS</strong> V1R9, if you code a nonzero MULTACC value, OPEN calculates a default<br />

number <strong>of</strong> READ or WRITE requests that you are suggesting the system queue more<br />

efficiently. OPEN calculates the number <strong>of</strong> BLKSIZE-length blocks that can fit within 64 KB,<br />

then multiplies that value by the MULTACC value. If the block size exceeds 32 KB, then OPEN<br />

uses the MULTACC value without modification (this can happen only if you are using LBI, the<br />

large block interface). The system then tries to defer starting I/O requests until you have<br />

issued this number <strong>of</strong> READ or WRITE requests for the DCB. BSAM will never queue (defer)<br />

more READ or WRITE requests than the NCP value set in OPEN.<br />

For BSAM, it will work as documented for DASD:<br />

► If you code a nonzero MULTACC value, OPEN will calculate a default number <strong>of</strong> read or<br />

write requests that you are suggesting the system queue more efficiently.<br />

► The system will try to defer starting I/O requests until you have issued this many read or<br />

write requests for the DCB.<br />

Note: BSAM will never queue or defer more read or write requests than the number <strong>of</strong><br />

channel programs (NCP) value set in OPEN.<br />

QSAM support<br />

For QSAM in z/<strong>OS</strong> V1R9, if you code a nonzero MULTACC value, OPEN calculates a default<br />

number <strong>of</strong> buffers that you are suggesting the system queue more efficiently. OPEN<br />

calculates the number <strong>of</strong> BLKSIZE-length blocks that can fit within 64 KB, then multiplies that<br />

value by the MULTACC value. If the block size exceeds 32 KB, then OPEN uses the<br />

MULTACC value without modification (this can happen only if you are using LBI, the large<br />

block interface). The system then tries to defer starting I/O requests until that number <strong>of</strong><br />

buffers has been accumulated for the DCB. QSAM will never queue (defer) more buffers than<br />

the BUFNO value that is in effect.<br />

Note: If you code a nonzero MULTACC value, OPEN will calculate a default number <strong>of</strong><br />

buffers that you are suggesting the system queue more efficiently.<br />

QSAM support for MULTSDN parameter<br />

You can use the MULTSDN parameter <strong>of</strong> the DCBE macro with QSAM. In previous releases,<br />

QSAM ignored the MULTSDN parameter. This new support for MULTSDN allows the system<br />

to calculate a more efficient default value for DCB's BUFNO parameter, and reduces the<br />

situations where you need to specify a BUFNO value. The user can use MULTSDN to give a<br />

hint to OPEN so it can calculate a better default value for QSAM BUFNO instead <strong>of</strong> 1, 2, or 5.<br />

The user will not have to be dependent on device information such as blocks per track or<br />

number <strong>of</strong> stripes. QSAM accepts a MULTSDN value for the following data sets:<br />

► Tape data sets<br />

► DASD data sets <strong>of</strong> the following types:<br />

– Basic format<br />

– Large format<br />

– Extended format (non-compressed)<br />

– PDS<br />

For these supported data set types, the system uses MULTSDN to calculate a more efficient<br />

value for BUFNO when the following conditions are true:<br />

► The MULTSDN value is not zero.<br />

► DCBBUFNO has a value <strong>of</strong> zero after completion <strong>of</strong> the DCB OPEN exit routine.<br />

► The data set block size is available.<br />

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

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

Saved successfully!

Ooh no, something went wrong!