Re: ADRDSSU VTOC -- also IEBCOPY

2014-06-08 Thread Ed Jaffe
On 6/8/2014 3:15 PM, Paul Gilmartin wrote: I suspect that the advent of PDSE partly impelled conversion to more conventional access methods rather than duplicating in IEBCOPY facilities available in PDSE and Binder. Not only that, but the channel programs it used - which were once considered "b

Re: ADRDSSU VTOC -- also IEBCOPY

2014-06-08 Thread Tony Harminc
On 8 June 2014 18:15, Paul Gilmartin wrote: > Another contributor to this thread told me long ago that IEBCOPY did > not (then) rely on customary access methods. Rather, with the goal of > best performance it used specialized channel programs and facilities > such as EXCP V=R and I/O appendages.

Re: ADRDSSU VTOC -- also IEBCOPY

2014-06-08 Thread Paul Gilmartin
On 2014-06-07, at 14:46, John Gilmore wrote: > > I certainly concede the possibility of front-ending BSAM or QSAM. > Nevertheless, the data-management facility for multiple-member > operations is BPAM; and in most circumstances it is the one that > should be used. With my back to the wall I could

Re: ADRDSSU VTOC -- also IEBCOPY

2014-06-08 Thread retired mainframer
:>: -Original Message- :>: From: IBM Mainframe Assembler List [mailto:ASSEMBLER- :>: l...@listserv.uga.edu] On Behalf Of Paul Gilmartin :>: Sent: Sunday, June 08, 2014 6:25 AM :>: To: ASSEMBLER-LIST@LISTSERV.UGA.EDU :>: Subject: Re: ADRDSSU VTOC -- also IEBCOPY :>: :>: On 2014-06-07, at 23:

Re: ADRDSSU VTOC -- also IEBCOPY

2014-06-08 Thread Paul Gilmartin
On 2014-06-07, at 23:19, retired mainframer wrote: > :>: -Original Message- > :>: From: IBM Mainframe Assembler List [mailto:ASSEMBLER- > :>: l...@listserv.uga.edu] On Behalf Of Paul Gilmartin > :>: Sent: Saturday, June 07, 2014 11:46 AM > :>: To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > :>: Subj