By "filename" I was referring to a UNIX filename, not a legacy dataset name. That was the topic I was responding to, the minimum and maximum lengths of UNIS filename specifications in JCL, DYNALLOC and TSO ALLOC. I would guess that A would be a valid dataset name. IIRC I had a bug in software I was developing and created a dataset with what I had intended would be a PDS member name, TEST or FOO or something like that, and it worked with no issues. In some cases there might be a catalog access violation enforced by RACF, but that would not mean the dataset name itself was invalid.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jeremy Nicoll Sent: Saturday, December 5, 2020 2:43 AM To: [email protected] Subject: Re: TSO ALLOCATE Pathname Length? On Sat, 5 Dec 2020, at 00:12, Charles Mills wrote: > I guess '/' is the only valid 1-byte filename in JCL, right? I recall reading tapes (on MVS) produced on VAXes or some other 'foreign' computer system. They had 17 character ANSI file datasetname values (17 chars being all the HDR1 label has space for). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
