On Mon, 24 Sep 2012 09:24:11 -0400, Kurt Quackenbush wrote: >> I get the same error if I run pax(1) from the keyboard with the same >> input and output. > >So this is not something unique to how SMP/E uses pax, right? Or is >there still a question? > Not for you. I need to investigate whether extended attributes can be suppressed in the archive.
>> The GIMZIP archive was not directly output from GIMZIP; I did some >> post-processing to redact local data set names. This ought to be a >> feature in GIMZIP. > >Can you be more specific? What ought to be a feature of GIMZIP? > I've long wished that: o GIMZIP could build its product from non-catalogued data sets, perhaps unloaded RELFILEs on tape, passed temporary DSNs, or MCS/JCLIN in PDS members or UNIX files. I'd like to be able to transform an SMP/E installation tape to a GIMZIP archive without copying the parts to transitory catalogued data sets. o The producer's local data set names could be redacted from the GIMPAF file in order not to expose data set prefixes (which may be TSO user IDs) to customers. Both these desiderata could be addressed if GIMZIP supported using DDNAMEs to identify its source data and used the data set names from its control file in the generated GIMPAF. Thanks, gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
