I think the IBM FTP development team, z/OS, and the HFS file system make for an uneasy menage-a-trois.
Like many people who did not "grow up with" MVS's atypical indirect file reference system (i.e., a program opens a DD name that will ultimately "point" to an actual dataset rather than the dataset name itself) I think the FTP team doesn't quite "get it" how z/OS dataset references are supposed to work. Why else would the documentation treat "DD references" as a weird afterthought, and the product designers think DD references were an oddball niche feature that could be left out of the API with no harm done? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin Sent: Thursday, April 27, 2006 12:27 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: FTP PUT of a temporary dataset In a recent note, Charles Mills said: > Date: Thu, 27 Apr 2006 11:40:24 -0700 > > The //DD: option also supports DD * and SYSOUT, and all of those other > wonderful little features of JCL like DEFER and RLSE and so forth. > I know I had a lot of trouble when //DD: referred to an allocation of PATH='/dev/fd/n'. FTP didn't want to respect the attributes I specified on the DD statement. It seems if it can't find them in the DSCB, it doesn't believe they're there, or it really has cognitive difficulty with //DD: referring to an HFS file. Some of this was fixed by APAR, but not quite to my satisfaction. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
