On Tue, 9 Oct 2007 11:01:28 +0200, R.S. wrote: >Jan MOEYERSONS wrote: >>> >>> STOR 'NULLFILE' >>> 125 Storing data set NULLFILE >>> >>> ... I wonder where it went? >> >> Would that not be the equivalent of a dummy file? I seem to remember that >> >> //NONO DD DSN=NULLFILE >> >> is the same as >> >> //NONO DD DUMMY >> True, unless John G. is lurking to dispute what it says in the RM.
>It is the same. However NULLFILE can be used in FTP (as file name), >while DD DUMMY would require special syntax. >What's funny, NULLFILE requires RACF authorization. At least in ftp. > My puzzlement arose when I discovered that some UNIX-like utilities such as ftp and cp fail when //'NULLFILE' is supplied as a source file, but (ftp at least) can use it as a target file. RACF seems not to be the answer because I don't believe RACF supports allowing write access to a data set while prohibiting read access. My conjecture now is that such utilities will supply default DCB attributes for an output data set, but not for an input data set: it makes little sense to try to guess characteristics of an input data set which has never been opened, while a reasonable guess can be made for creating a new data set. It's disappointing that such utilities don't follow through with their support of Classic data sets by displaying Classic messages such as IEC141I 013-nn which are well described in M&C. (I'm guessing at the code; LOOKAT seems broken just now.) -- gil ---------------------------------------------------------------------- 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
