On 18 December 2014 at 19:56, Paul Gilmartin <[email protected]> wrote:
> I take as the authority: > http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idad400/dsam.htm%23dsam?lang=en z/OS DFSMS Using Data Sets SC23-6855-00 > http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idad400/dsam.htm%23dsam?lang=en > You can store all types of data sets on DASD but only sequential data sets > on magnetic tape. Mountable tape volumes can reside in an automated tape > library. For information about magnetic tape volumes, see z/OS DFSMS Using > Magnetic Tapesz/OS DFSMS Using Magnetic Tapes. You can also direct a > sequential data set to or from spool, a UNIX file, a TSO/E terminal, a > unit record device, virtual I/O (VIO), or a dummy data set. > > OK. So what might a "File Object" be mapped to that isn't subsumed by that > description. OK; I guess a socket. PL/I supported QTAM and later TCAM message queues as what a C or Java person might call "first class objects". Looked at another way, such a teleprocessing (sounds quaint now, doesn't it) file is a part of the PL/I language, but is not mapped to any sort of dataset or even DD statement. It is a TRANSIENT (as opposed to SEQUENTIAL or DIRECT) PL/I file. I imagine this support disappeared along with QTAM and TCAM. > But on occasion, I've cited it to IBM > support when they say, "WAD; we don't support that; as the Manual says it > must be a data set." Invariably, they Humpty-Dumpty me, and I lose. Your case would be better supported if they had said " You can store all types of files on DASD but only sequential files on magnetic tape." That would closely match what you might find in the PL/I manuals. But then that wouldn't be what a "Using Datasets" book would say, would it... Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
