CA Dynam for VSE User Guide

CA Dynam for VSE User Guide CA Dynam for VSE User Guide

supportcontent.ca.com
from supportcontent.ca.com More from this publisher
03.03.2015 Views

Processing Unchained Multifile Tapes The first DSN in the unchained multifile set dictates all volume criteria, density, tape length, and so on, for that tape and subsequent files, regardless of what is specified on the TLBL or the Catalog. All output $TEST multifile data sets (unchained or predefined) are created as single file data sets with a file sequence of one on separate volumes. Unchained multifile versions are scratched when they become eligible regardless of the location of the file on the tape. After a volume contains no active files (all unchained files are in scratch status), the volume is returned to scratch status. File sequence numbers for unchained multifile versions are relative to the start of the volume on which the file exists. File sequence numbers for predefined multifiles are relative to the volume that starts the whole multifile set. In effect, the file sequence for unchained versions start over with each new tape volume, where predefined versions continue incrementing from the first file on the first volume of the set. The following illustrates this point: DSN VOLSER FILESEQ FILESEQ PREDEFINED UNCHAINED dsn1 tape01 1 1 dsn2 tape01 2 2 tape02 2 1 dsn3 tape02 3 2 dsn4 tape02 4 3 tape03 4 1 The following JCL examples show how to create multifile data sets using the STACK= option. Examples: Adding a file to an active tape Note: REF must be used as the DTFNAME and filea must be the last active file on that VOLSER. // TLBL REF,'filea',STACK=A // TLBL NEWFILE,'fileb',STACK=A // EXEC pgm Create a new multifile set on a scratch volume: // TLBL OUT1,'filea',STACK=B // TLBL OUT2,'fileb',STACK=B // TLBL OUT3,'filec',STACK=B 2–68 User Guide

Using Automatic Multifile (AMF) Data Sets Creating a new multifile set in multiple steps: // TLBL OUT,'filea',STACK=* // EXEC pgm // TLBL REF,'filea',STACK=* // TLBL OUT,'fileb',STACK=* // EXEC pgm // TLBL REF,'fileb',STACK=* // TLBL OUT,'filec',STACK=* // EXEC pgm Using Automatic Multifile (AMF) Data Sets CA Dynam/T incorporates a special feature to automatically generate multifile data set names at output open time. The system adds another data set to the multifile set if both the following conditions are satisfied: • The first data set on the multifile set was cataloged with this option. • The special data set for the file is in the TLBL. Generating AMF File Numbers Three asterisks (***) in the TLBL's DSN indicate to CA Dynam/T that this could be an automatic multifile (AMF) data set. CA Dynam/T replaces the three asterisks with a three-digit number if the following conditions are satisfied: • If you are opening the file as output, CA Dynam/T generates this number by adding one to the number of the previous file in the AMF set. • If the file is opened as input, CA Dynam/T retrieves this number from the Catalog. The number is determined by any one of the following, in the same order of priority shown here: 1. File sequence number from the TLBL 2. Version number from the TLBL or the relative generation 3. Three numbers of the last-created AMF data set Creating an Automatic Multifile Data Set Create automatic multifile data sets with the DYNCAT DEFINE command. The parameter MF=AUTO in the DEFINE statement indicates this is an AMF data set. The PREVFILE parameter is not permitted. The DSN must contain three asterisks (***), or it will be rejected. This defines the base data set name for the AMF set. This name should permanently reside in the Catalog. Chapter 2: Maintaining Tape Files 2–69

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

Creating a new multifile set in multiple steps:<br />

// TLBL OUT,'filea',STACK=*<br />

// EXEC pgm<br />

// TLBL REF,'filea',STACK=*<br />

// TLBL OUT,'fileb',STACK=*<br />

// EXEC pgm<br />

// TLBL REF,'fileb',STACK=*<br />

// TLBL OUT,'filec',STACK=*<br />

// EXEC pgm<br />

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

<strong>CA</strong> <strong>Dynam</strong>/T incorporates a special feature to automatically generate multifile<br />

data set names at output open time. The system adds another data set to the<br />

multifile set if both the following conditions are satisfied:<br />

• The first data set on the multifile set was cataloged with this option.<br />

• The special data set <strong>for</strong> the file is in the TLBL.<br />

Generating AMF File Numbers<br />

Three asterisks (***) in the TLBL's DSN indicate to <strong>CA</strong> <strong>Dynam</strong>/T that this<br />

could be an automatic multifile (AMF) data set. <strong>CA</strong> <strong>Dynam</strong>/T replaces the three<br />

asterisks with a three-digit number if the following conditions are satisfied:<br />

• If you are opening the file as output, <strong>CA</strong> <strong>Dynam</strong>/T generates this number<br />

by adding one to the number of the previous file in the AMF set.<br />

• If the file is opened as input, <strong>CA</strong> <strong>Dynam</strong>/T retrieves this number from the<br />

Catalog. The number is determined by any one of the following, in the<br />

same order of priority shown here:<br />

1. File sequence number from the TLBL<br />

2. Version number from the TLBL or the relative generation<br />

3. Three numbers of the last-created AMF data set<br />

Creating an Automatic Multifile Data Set<br />

Create automatic multifile data sets with the DYN<strong>CA</strong>T DEFINE command. The<br />

parameter MF=AUTO in the DEFINE statement indicates this is an AMF data<br />

set. The PREVFILE parameter is not permitted. The DSN must contain three<br />

asterisks (***), or it will be rejected. This defines the base data set name <strong>for</strong><br />

the AMF set. This name should permanently reside in the Catalog.<br />

Chapter 2: Maintaining Tape Files 2–69

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

Saved successfully!

Ooh no, something went wrong!