oh Gil, You know very well that the Command Reference documents only that pax supports MVS data set names and does not mention that DD:XXX names are supported. You have said this many times before, and I agree that IBM should formally support this. Have you opened a requirement?
Surely they are just using whatever name you give it as an argument to fopen(), so one would assume that extra work would be required *not* to support DD:XXXX. But of course you are technically right, as usual :-) I have no reservations using cp and pax with DD names, but this wouldn't be acceptable to pedants. Perhaps it isn't supported and document because IBM can't figure out how to get DD's visible to BPXBATCH to test it :-) Seriously... if IBM were to document in the Command Ref that DD:NAME is supported in several shell utilities, they would get sucked into describing why it is hard to use DD names in the context of forked address spaces. Then they might have to document exactly when the shell forks vs spawns, which they have already declined to do. Kirk Wolf Dovetailed Technologies http://dovetail.com On Fri, Jan 17, 2014 at 1:16 PM, Paul Gilmartin <paulgboul...@aim.com>wrote: > On Fri, 17 Jan 2014 13:12:09 +0000, van der Grijn, Bart (B) wrote: > > >I'm trying to use pax to write to a ddname. > >The following code: > >... > >wCMD = "pax -w -X -z -x pax -f //DD:PAX" aDir > > > I don't believe any such construct is supported. Have you seen > any documentation that states that it is. > > Submit a requirement. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
