I don't know. I don't know UNIX (z or otherwise) well enough to have a "feeling" for what is going on.
LCD '' fixes it, so my *guess* is that it just somehow has "UNIX paths on the brain" and //DD: looks wrong to it. That's my mental model. No real idea. If it is not documented behavior I would say it feels like a bug to me, too. Too bad I'm a red-headed stepchild (otherwise known as a Dallas customer) rather than a z/OS licensee, and therefore cannot open PMRs. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Friday, August 7, 2020 3:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Why EZA1685W Invalid local file identifier ? On Fri, 7 Aug 2020 14:34:03 -0700, Charles Mills wrote: >Solved. Is this documented FTP behavior? Looks like a bug to me. z/OS V2R2 >for what it's worth. > >Given //MYOUTPUT DD SYSOUT=* >GET 'my.pds(member)' //DD:MYOUTPUT >Succeeds as it should, but not if it is preceded by > >LCD /u/usr > >In which case you get the error message of the subject. Is that what people >would expect? Is that documented? > >You can "fix" it by adding LCD '' between the two commands. In other words, >GET to a DD fails if the current local directory is a UNIX path. > Is it possible that when LCD is a UNIX path, GET forks a new address space to facilitate resolution of relative paths, but this loses DDNAMEs? Feels like a bug. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
