On 2018-01-29, at 12:27:59, Charles Mills wrote: > DTFCP supported some subset of disk and tape I/O capabilities. > The design integrity of OS/360's I/O architecture has been much compromised with the advent of utilities which gratuitously (sometimes with a goal of performance) enforce device dependence. Such utilities should at least support, if possible, a fallback to device-independent I/O.
As an irritating example, AMATERSE refuses to UNPACK an archive from a UNIX file. It certainly has the capability -- the rule can be circumvented by pre-concatenating an empty temp Classic data set to deceive whatever check the designers imagined necessary. (Apparently they test only the first catenand.) -- gil
