> Typically a "dataset" is MVS - z/OS, while a "file" is UNIX.
Please do not forget about the z/VM (CMS minidisk, SFS). So, we will use this sentence as Typically a "dataset" is MVS - z/OS, while a "file" is UNIX or z/VM. Anyway, the dataset is a self-organized data on ECKD device with different Count-Key's, meanwhile the file can be allocated on a pre-formatted media. Exactly. And it one reason why z/OS does not work with 9336 devices -- it can't drive by length of every FBA-block, which has fixed 512 bytes length. Yes, it is possible, in theory, but too many z/OS programs require CKD/ECKD arch. Nobody will patch them. With regards, =Maxim 2017-04-26 19:02 GMT+03:00 Gerhard Adam <[email protected]>: > Typically a "dataset" is MVS - z/OS, while a "file" is UNIX. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Porowski, Kenneth > Sent: Wednesday, April 26, 2017 8:39 AM > To: [email protected] > Subject: Terminology - Datasets > > From a z/OS - Mainframe perspective > > You have the UNIX filesystem with various types of files in it. > > You have the "classic" Mainframe datasets (sequential, PDS, VSAM, etc.) > > To differentiate the "classic" datasets from the UNIX filesystem/files what > is the correct/preferred terminology for the "classic" datasets? > > MVS dataset > MVS style dataset > MVS type dataset > z/OS dataset > etc. > something else? > > > > This email message and any accompanying materials may contain proprietary, > privileged and confidential information of CIT Group Inc. or its subsidiaries > or affiliates (collectively, “CIT”), and are intended solely for the > recipient(s) named above. If you are not the intended recipient of this > communication, any use, disclosure, printing, copying or distribution, or > reliance on the contents, of this communication is strictly prohibited. CIT > disclaims any liability for the review, retransmission, dissemination or > other use of, or the taking of any action in reliance upon, this > communication by persons other than the intended recipient(s). If you have > received this communication in error, please reply to the sender advising of > the error in transmission, and immediately delete and destroy the > communication and any accompanying materials. To the extent permitted by > applicable law, CIT and others may inspect, review, monitor, analyze, copy, > record and retain any communications sent from or received at this email > address. > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Regards, =Maxim Bochagov ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
