Re: FTP serialization when writing PDS/PDSE members

2016-12-12 Thread Paul Gilmartin
On Tue, 6 Dec 2016 17:11:37 -0600, Kirk Wolf wrote: > >What you are seeing leads me to believe that the data set I/O is *not* >occurring while it is being transferred. Otherwise, you should also see >an ENQ on SPFEDIT/DSN (no member), right? > Blocking conceals a lot of sins. If I allocate my

Re: FTP serialization when writing PDS/PDSE members

2016-12-10 Thread Jesse 1 Robinson
, December 10, 2016 8:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: FTP serialization when writing PDS/PDSE members On Sat, 10 Dec 2016 19:46:00 -0800, Charles Mills wrote: >I think it is well known and probably documented (perhaps not with stunning >clarity) that you cannot

Re: FTP serialization when writing PDS/PDSE members

2016-12-10 Thread Paul Gilmartin
On Sat, 10 Dec 2016 19:46:00 -0800, Charles Mills wrote: >I think it is well known and probably documented (perhaps not with stunning >clarity) that you cannot write to two members of a PDS (non-E) at once. > Understood; perhaps better than NFS understands. It puts out two ENQ EXC SPFEDIT

Re: FTP serialization when writing PDS/PDSE members

2016-12-10 Thread Charles Mills
: Saturday, December 10, 2016 12:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP serialization when writing PDS/PDSE members On Tue, 6 Dec 2016 18:27:58 -0600, Kirk Wolf wrote: >There are two SPFEDIT enqs required to follow the protocol. The data set >one (without member) is used to serialize

Re: FTP serialization when writing PDS/PDSE members

2016-12-10 Thread Paul Gilmartin
On Tue, 6 Dec 2016 18:27:58 -0600, Kirk Wolf wrote: >There are two SPFEDIT enqs required to follow the protocol. The data set >one (without member) is used to serialize during actual I/O.You aren't >seeing that while transferring with FTP, which is why I believe that the >actual I/O is

Re: FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Paul Gilmartin
On Tue, 6 Dec 2016 18:27:58 -0600, Kirk Wolf wrote: >There are two SPFEDIT enqs required to follow the protocol. The data set >one (without member) is used to serialize during actual I/O.You aren't >seeing that while transferring with FTP, which is why I believe that the >actual I/O is

Re: FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Graham Harris
Might employing the GRS enqueue monitor help understand what is going on behind the scenes, and in what order? On 7 December 2016 at 00:27, Kirk Wolf wrote: > There are two SPFEDIT enqs required to follow the protocol. The data set > one (without member) is used to

Re: FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Paul Gilmartin
On Tue, 6 Dec 2016 17:11:37 -0600, Kirk Wolf wrote: > >What you are seeing leads me to believe that the data set I/O is *not* >occurring while it is being transferred. Otherwise, you should also see >an ENQ on SPFEDIT/DSN (no member), right? > In: z/OS 2.1.0 ISPF z/OS ISPF Planning

Re: FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Kirk Wolf
There are two SPFEDIT enqs required to follow the protocol. The data set one (without member) is used to serialize during actual I/O.You aren't seeing that while transferring with FTP, which is why I believe that the actual I/O is being deferred. Kirk Wolf Dovetailed Technologies

Re: FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Paul Gilmartin
On Tue, 6 Dec 2016 17:11:37 -0600, Kirk Wolf wrote: > >What you are seeing leads me to believe that the data set I/O is *not* >occurring while it is being transferred. Otherwise, you should also see >an ENQ on SPFEDIT/DSN (no member), right? > Can't tell. While creating a member with Edit and

Re: FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Kirk Wolf
Thanks Gil, What you are seeing leads me to believe that the data set I/O is *not* occurring while it is being transferred. Otherwise, you should also see an ENQ on SPFEDIT/DSN (no member), right? Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Dec 6, 2016 at 5:02 PM, Paul

Re: FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Paul Gilmartin
On Tue, 6 Dec 2016 16:46:04 -0600, Paul Gilmartin wrote: >On Tue, 6 Dec 2016 15:15:54 -0600, Kirk Wolf wrote: > >>As many are aware, z/OS Comm Svr FTP uses DISP=SHR + ISPF compatible ENQs >>when writing PDS members. >> >Anyone for an RFE for /bin/cp to do likewise? >... >LM services LMPUT

Re: FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Paul Gilmartin
On Tue, 6 Dec 2016 15:15:54 -0600, Kirk Wolf wrote: >As many are aware, z/OS Comm Svr FTP uses DISP=SHR + ISPF compatible ENQs >when writing PDS members. > (Curiously, last I looked, the ISPF doc is in the install/config guide.) NFS does likewise. And NFS (I'm guessing FTP) creates ISPF

Re: FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Charles Mills
ist [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Kirk Wolf Sent: Tuesday, December 06, 2016 1:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: FTP serialization when writing PDS/PDSE members As many are aware, z/OS Comm Svr FTP uses DISP=SHR + ISPF compatible ENQs when writing PDS members. See for example this

FTP serialization when writing PDS/PDSE members

2016-12-06 Thread Kirk Wolf
As many are aware, z/OS Comm Svr FTP uses DISP=SHR + ISPF compatible ENQs when writing PDS members. See for example this message for evidence: === EZA2563W Data set dsname used exclusively by someone else. Explanation: A data transfer (get, put or append) of a partitioned