Yes, this implies open() and all other file related APIs.
It will use the ISPF ENQ model as documented in the ISPF Customization book,
however, ENQs may be held for a short period of time after last close of a file.
Bill Schoen
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.
>
Does this imply support for open() and thereby shell redirection?
How does this interact with SYSDSN ENQ?
How does this interact with ENQ SPFEDIT,rname,E,52,SYSTEMS?
How does this interact with ENQ SPFEDIT,rname,E,12,SYSTEMS?
What about the converse? I've long wished for support for UNIX
directoriies in STEPLIB, SYSEXEC, ...
It has long been an irritant that "cp source //pds(member) issues ENQ EXC
on the entire target data set. Will this be mitigated? (I suspect this is a
limitation of the C/C++ RTL.)
A problem was reported here a few weeks ago that:
//STEP1 EXEC PGM=BPXBATCH,PARM='pax -wf "//''dat.set'"''
//STEP3 EXEC PGM=AMATERSE
//SYSUT1 DD DISP=SHR,DSN=data.set
failed on an ENQ on "data.set". Will this be mitigated?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
