//NEWPDSE  DD  DSNAME=FILEA.ABC(REC1),DISP=(NEW,KEEP)

In the example, the NEWPDSE DD statement defines member REC1 in the new PDSE named FILEA.ABC. Note that installation-written ACS routines select the data class (which specifies LIBRARY for DSNTYPE), management class, and storage class for the data set.

//NEWA   DD  DSNAME=REPORT.ONE(WEEK1),DISP=(NEW,KEEP),
//       DATACLAS=DCLAS09,DSNTYPE=LIBRARY

In the example, the NEWA DD statement defines member WEEK1 in the new PDSE named REPORT.ONE. DSNTYPE=LIBRARY overrides the DSNTYPE attribute in data class DCLAS09 but uses other data set attributes in DCLAS09. A version 1 or version 2 PDSE will be created based on the PDSE_VERSION specification or omission in the IGDSMSxx parmlib member. Note that installation-written ACS routines select the management class and storage class for the data set.

//NEWB   DD  DSNAME=REPORT.ONE(WEEK2),DISP=SHR,
//       DATACLAS=DCLAS09,DSNTYPE=LIBRARY

In the example, the NEWB DD statement adds a new member named WEEK2 to the existing PDSE named REPORT.ONE. DSNTYPE=LIBRARY overrides the DSNTYPE attribute in data class DCLAS09 but uses other data set attributes in DCLAS09. Other jobs can be concurrently processing existing members of PDSE named REPORT. Note that installation-written ACS routines select the management class and storage class for the data set.

//NEWC   DD  DSNAME=REPORT.THREE(WEEK3),DISP=(NEW,KEEP),
//       DATACLAS=DCLAS09,DSNTYPE=(LIBRARY,2)

In the example, the NEWC DD statement defines member WEEK3 in the new PDSE named REPORT.THREE. DSNTYPE=(LIBRARY,2) overrides the DSNTYPE attribute in data class DCLAS09 but uses other data set attributes in DCLAS09. The "2" as the second DSNTYPE value causes the new PDSE to be in the version 2 format, which can produce performance benefits in some environments. Note that installation-written ACS routines select the management class and storage class for the data set.

//FILESYS DD DSNAME=OPENDS.USRJOE,DATACLAS=DCLAS05,DISP=(NEW,KEEP),
//        DSNTYPE=HFS,SPACE=(CYL,(100,100,1))

The FILESYS DD statement creates an HFS data set to contain an HFS file system. The DCLAS05 in DATACLAS specifies allocation characteristics. The number of directory blocks must be specified to indicate that this is an HFS data set but the value has no effect on allocation.

//PIPE  DD PATH='/u/payroll/buffer',DSNTYPE=PIPE,
//     PATHOPTS=(OWRONLY,OEXCL,OCREAT),PATHMODE=(SIWUSR,SIRGRP),
//     PATHDISP=(KEEP,DELETE)

The PIPE DD statement creates a file named /u/payroll/buffer for use as a FIFO special file. The PATHOPTS parameter specifies that the user intends that the program open the FIFO special file for writing. The PATHMODE parameter specifies that the file owner can write in the FIFO special file and that users in the file group class can read from the FIFO special file. The PATHDISP parameter requests that the file be kept when the program ends normally and deleted when it ends abnormally.

Pathnames are case-sensitive. If you are specifying a pathname containing a special character, including a lowercase character, enclose it in apostrophes. For more information, refer to PATH parameter.

//SYSUT2  DD UNIT=SYSDA,DSNAME=BIGPROJ.BIGDATA,DSNTYPE=LARGE,
//           SPACE=(TRK,(80000,40000))

The SYSUT2 DD statement creates a single-volume data set that contains more than 65535 tracks. Space units such as cylinders, megabytes, or average record size can be used instead of counting tracks. A data class (DATACLAS) with a DSNTYPE value of LARGE can be coded instead of DSNTYPE=LARGE. While SMS is running, you can use a data class for a new data set that will not be SMS-managed.