03.03.2015 Views

CA Dynam for VSE User Guide

CA Dynam for VSE User Guide

CA Dynam for VSE User Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Changing File Characteristics<br />

Storage Requirements<br />

Carefully consider storage requirements when using <strong>CA</strong> <strong>Dynam</strong>/FI to increase<br />

the block size or buffers of a file -- single buffering to double buffering (DB). If<br />

additional storage is needed <strong>for</strong> the blocks or buffers, it is taken from partition<br />

GETVIS. This storage can be considerable depending on the new block size<br />

and/or buffer size.<br />

Also be aware that it is not always an efficient use of storage to specify<br />

BLKSZ=OPTIMIZE <strong>for</strong> a file that originally wrote small records in small blocks.<br />

This is true, <strong>for</strong> example, if the device type is a 3380 disk drive.<br />

Block Sizes and Logical Record Lengths<br />

The logical record length (LRECL) and the physical block size (BLKSZ) can<br />

affect each other, depending on the record <strong>for</strong>mat specified. <strong>CA</strong> <strong>Dynam</strong>/FI will,<br />

if necessary, alter either or both the LRECL and BLKSZ, depending on both the<br />

old and new record <strong>for</strong>mat. The exact conditions and actions taken are<br />

described below.<br />

Note that if the user specifies an LRECL or BLKSZ value through Job Control or<br />

the Catalog, then <strong>CA</strong> <strong>Dynam</strong>/FI uses these values just as they are. However, if<br />

either the LRECL or BLKSZ value is not specified through Job Control or the<br />

Catalog, then one or more of the following can occur:<br />

• If control characters <strong>for</strong>:<br />

−<br />

−<br />

DTFPR (printer)files are added to records, then record length is<br />

increased one byte.<br />

DTFCD (punch) files are deleted from records, then record length is<br />

decreased one byte.<br />

• If changing from:<br />

−<br />

−<br />

Fixed- or undefined- to variable-length records, then record length is<br />

increased four bytes to include record descriptor word (RDW).<br />

Variable- to fixed- or undefined-length records, then record length is<br />

decreased four bytes and RDWs are eliminated.<br />

• If record <strong>for</strong>mat is to be fixed-unblocked or undefined, then block size<br />

equals record length.<br />

• If record <strong>for</strong>mat is to be fixed blocked and:<br />

−<br />

Old <strong>for</strong>mat was fixed (blocked or unblocked), then block size equals<br />

old blocking factor (old block size divided by old LRECL) multiplied by<br />

record (current LRECL).<br />

For example, if you specify RECFM=FB and LRECL=50 when:<br />

old logical record length = 80<br />

6–22 <strong>User</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!