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.

5.36 Creating a VSAM cluster<br />

//VSAM DD DSN=NEW.VSAM,<br />

// DISP=(,CATLG),<br />

// SPACE=(1,(2,2)),AVGREC=M,<br />

// RECORG=KS,KEYLEN=17,KEYOFF=6,<br />

// LRECL=80<br />

Figure 5-36 Creating a VSAM data class<br />

NEW.VSAM<br />

NEW.VSAM.DATA<br />

NEW.VSAM.INDEX<br />

Creating a VSAM data set using JCL<br />

In the DFSMS environment, you can create temporary and permanent VSAM data sets using<br />

JCL by using either <strong>of</strong> the following:<br />

► The RECORG parameter <strong>of</strong> the JCL DD statement<br />

► A data class<br />

You can use JCL DD statement parameters to override various data class attributes; see<br />

Table 5-2 on page 298 for those related to VSAM data sets.<br />

Important: Regarding DISP=(OLD,DELETE), in an SMS environment, the VSAM data set<br />

is deleted at unallocation. In a non-SMS environment, the VSAM data set is kept.<br />

A data set with a disposition <strong>of</strong> MOD is treated as a NEW allocation if it does not already<br />

exist; otherwise, it is treated as an OLD allocation.<br />

For a non-SMS environment, a VSAM cluster creation is only done through IDCAMS. In<br />

Figure 5-36, NEW.VSAM refers to a KSDS VSAM cluster.<br />

Chapter 5. <strong>System</strong>-managed storage 299

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

Saved successfully!

Ooh no, something went wrong!