PATH is not only under-specified in the JCL reference, it is also over-specified.
- Is case-sensitive. Thus, /u/joe and /u/JOE and /u/Joe define three different files. Is not an aspect of the PATH= parameter, it is an aspect of the HFS. Logically they could change HFS tomorrow to be non-case-sensitive (granted, it ain't gonna happen -- I'm just talking logic here) without touching the PATH= code and the above sentence would no longer be true. Or I could write a product that mounted a remote Windows volume as an HFS volume and the above sentence would not be true. /u/Joe and /u/Fred are also different files, but that's an aspect of HFS, not of PATH=. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Wednesday, March 07, 2012 11:19 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Tips for continuing DD statement with only one parameter field On Wed, 7 Mar 2012 19:04:40 -0800, Charles Mills <charl...@mcn.org> wrote: >Well, who's counting indeed, but my JCL reference says > >The pathname: ... >- Has a length of 1 through 255 characters. ... > I stand corrected; I misread earlier in the same section: Each directory or filename: Is preceded by a slash (/). The system treats any consecutive slashes as a single slash. ... Has a length of 1 through 254 characters, not including the slash. But now I've read it more carefully and submitted the RCF: Hello, MHVRCFS In: Title: z/OS V1R13.0 MVS JCL Reference Document Number: SA22-7597-15 12.48.2 Subparameter Definition pathname Is incomplete, perhaps misleading. The description appears to prohibit the following which are in fact allowed: ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
