On Tue, 21 Dec 2021 07:41:08 -0600, Bill Schoen wrote: >Yes, this implies open() and all other file related APIs. > Hmmm... I imagine: o mkdir within a PDS(E) directory?
o Hard link to a PDSE member version? o open( , O_TRUNC) a PDSE member seek() to the middle of it write() data with a short length? There will be a list of restrictions, ever-growing as users encounter new limitations. A wonderful thing about UNIX filesystems is that I can keep program objects and data objects in the same directory. (How did the PDSE designers fail to think of that?!) I thought about that after I suggested in a thread (already too long) in ASSEMBLER-LIST that it would be useful to keep a snapshot of a program object and all associated ASMADATA files. keeping them in a single directory, "chmod -R a-w" would be a boon. >On Tue, 21 Dec 2021 09:57:54 +0800, David Crayford wrote: >> ... >>*New file system support to access z/OS data sets* >> >>IBM plans to provide a new file system type that will render traditional >>z/OS data sets accessible by the z/OS UNIX name space. This will enable >>z/OS UNIX applications, tools, and utilities transparent access to data >>in these data sets in a secure and consistent manner. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
