z/OS UNIX file path specification - Key = '8017'

DALPATH specifies the pathname of the z/OS® UNIX file to be allocated.

You can code DALPATH only with the DALDUMMY, DALTERM, DALDDNAM, DALPOPT, DALPMDE, DALPNDS, DALPCDS, DALBLKSZ, DALBUFNO, DALLRECL, DALNCP, DALRECFM, DALLRECK, DALFDAT and DALDSNT keys. DALPATH is mutually exclusive with all other keys. In JCL, the information conveyed by this key is specified using the PATH keyword.

Dynamic allocation does not support backward or forward references. See Table 1.

When you code this key, # must be 1, LEN is the length of the pathname, and PARM contains the pathname. The maximum length of the pathname is 255 characters. Refer to Table 1 for values.

You specify either:
- The hex integers representing OCREAT alone
  or
- The hex integers representing both OCREAT and OEXCL
on the DALPOPT key,
And if
The file does not exist,

Then MVS™ performs an open() function. The options from DALPOPT, the pathname from the DALPATH key, and the options DALPMDE (if specified) are used in the open(). MVS uses the close() function to close the file before the application program receives control.

For status group options other than OCREAT and OEXCL, the description in this information assumes that the application passes the values to the open() function without modification. That is, this application uses dynamic allocation information retrieval (the DYNALLOC macro) to retrieve the values specified for DALPOPT and passes the values to the open() function. The application program can ignore or modify the information specified in the JCL.

Example: To specify the z/OS UNIX file pathname /u/myuid/myapp/scr.dat:, code

KEY    #     LEN   PARM
8017   0001  0016  61 A4 61 94 A8 A4 89 84 61 94 A8 81 97 97 61 A2 83 99 4B 84 81 A3

Example: To specify a dummy z/OS UNIX file, /dev/null:, code

KEY    #     LEN   PARM
8017   0001  0009  61 84 85 A5 61 95 A4 93 93

Note: Specifying the DALDUMMY key with any pathname achieves the same result.