On 8 June 2014 18:15, Paul Gilmartin <[email protected]> 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. In consequence, it needed to > operate with APF priviliges and could not deal with VIO. > > 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.
Indeed, these days IEBCOPY is as likely to produce IEW or IGW messages as its own IEB ones. It seems to have become merely a front end for underlying callable system services. AMBLIST has taken much the same path. Tony H.
