Example: Using ALLOCATE and OCOPY

Using the ALLOCATE command to associate the PDSE member with the ddname specified in the DDNAME keyword, user TURBO could enter:
```
ALLOCATE DDNAME(MVSWORK) DSNAME('TURBO.WORKLOAD.TOTALS(OCT17)')
```
Tip: For an ALLOCATE that begins with your TSO/E prefix as the high-level qualifier, you can enter the data set name more simply as DSNAME(WORKLOAD.TOTALS(OCT17))— without the user ID. (The TSO/E prefix defaults to your user ID, but it can be set with the PREFIX command.) If you do not enclose the data set name in quotes, TSO/E automatically prefixes the name with your TSO/E prefix. For JCL, you need the user ID.
Using the ALLOCATE command to create a new z/OS UNIX file and associate it with the ddname specified in the DDNAME keyword, TURBO could enter:
```
ALLOCATE DDNAME(OPNWORK) PATH('/u/turbo/wkld/totals/oct17')
         PATHDISP(KEEP,DELETE) PATHOPTS(ORDWR,OCREAT)
         PATHMODE(SIRUSR,SIWUSR)
```
In this example:
- PATHDISP(KEEP,DELETE) indicates that the file should be saved if the session ends normally, but that it should be deleted if the session ends abnormally.
- The PATHOPTS operand is required only when you are creating a new file. PATHOPTS(ORDWR,OCREAT) indicates that the owner has read/write access and this is a new file being created.
- Specifying PATHMODE is required only when you are creating a new file (OCREAT). PATHMODE(SIRUSR,SIWUSR) indicates that the owner has read and write permission. If you do not specify a PATHMODE, the default permissions set when the file is allocated are:
  - owner=---
  - group=---
  - other=---
After the data set and file have been allocated, TURBO would enter the OCOPY command, using the ddnames, to copy the MVS™ partitioned data set member to a z/OS UNIX file using the default conversion table:
```
OCOPY INDD(MVSWORK) OUTDD(OPNWORK) TEXT CONVERT(YES) PATHOPTS(USE)
```
PATHOPTS(USE) indicates that TURBO wants to use the PATHOPTS specified on the ALLOCATE command.