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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Using Automatic Multifile (AMF) Data Sets<br />

This statement creates the next AMF data set name in sequence. For instance,<br />

if the last DSN on the current set was AMF008, <strong>CA</strong> <strong>Dynam</strong>/T would create DSN<br />

AMF009 and place it in the Catalog as file one of a new AMF set. The next time<br />

the job creating the AMF DSN is run, AMF009 is used. You can then delete<br />

DSNs AMF002 through AMF008. This frees space in the Catalog. The base<br />

DSN, AMF***, must remain in the Catalog; it contains pointers to the data set<br />

names currently in use.<br />

Scratching More Than the Last AMF DSN<br />

If you manually scratch a tape other than the last DSN of an AMF set, you<br />

must tell <strong>CA</strong> <strong>Dynam</strong>/T which DSN to use next <strong>for</strong> output.<br />

For instance, suppose data sets AMF001 through AMF008 had been created,<br />

but data sets AMF005 through AMF008 contained bad data and had to be<br />

recreated, then do the following:<br />

1. Scratch DSN AMF005 using DYN<strong>CA</strong>T DELETE. This would scratch AMF005<br />

through AMF008 because <strong>CA</strong> <strong>Dynam</strong>/T always scratches <strong>for</strong>ward on<br />

chained multifile data sets:<br />

DELETE 'AMF005' ALL<br />

2. Issue the following DYN<strong>CA</strong>T update statement:<br />

ALTER 'AMF***' MF=005<br />

This update statement tells <strong>CA</strong> <strong>Dynam</strong>/T to use DSN AMF005 <strong>for</strong> outputting<br />

the next file of this AMF set. The same procedure must be followed when<br />

members of the current AMF set are deleted.<br />

Inputting AMF Data Sets<br />

Several methods are available to call <strong>for</strong> the desired input AMF data set. The<br />

following examples assume that AMF001 through AMF014 have all been<br />

created on the same tape. AMF014 is the latest (last) file. Each of the<br />

following will result in DSN AMF007 being the data set requested (provided the<br />

file is being opened <strong>for</strong> input):<br />

// TLBL INFILE,'AMF***',,,,,8 (version number field)<br />

// TLBL INFILE,'AMF***',,,,7 (file sequence number field)<br />

// TLBL INFILE,'AMF***.(-7)' (relative generation)<br />

// TLBL INFILE,'AMF007' (real DSN)<br />

// TLBL INFILE,'AMF***',,,,7,2 (file sequence overriding version)<br />

Subsequent files of AMF sets are also subsequent generations; thus, cyclic<br />

control of these data sets does not apply. You can set retention dates and use<br />

the MF=NEW option to divide the AMF data sets into easily manageable groups<br />

of tapes.<br />

Chapter 2: Maintaining Tape Files 2–71

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

Saved successfully!

Ooh no, something went wrong!