On 2016-09-05, at 14:01, R.S. wrote: > My €0.02: It would be good idea to enhance ftp protocol, to use something > like GIMFAF.XML file. > It is used by SMP/E Internet Delivery, every file or dataset is accompanied > with XML description stored in GIMFAF.XML file. > > In such scenarion every file transfer from "structured world" (MVS, VM) to > "flat file world" (unix, windows) would give two files: the file itself and > metadata. And of course the metadata would be automatically applied during > transfer the opposite direction. > It's pretty good. Opportunities for improvement:
o There's no all-embracing archive convention. Rather, the GIMPAF file directs downloading individual archive files from a server. (Unless RECEIVE ORDER improves on this). o It's biased toward unloaded PDSes. o In fact, UNIX files are loaded into PDSes, then unloaded by IEBCOPY RECEIVE reloads the PDSes, then APPLY copies members to UNIX directories. Pretty roundabout. Are exended attributes kept in the GIMFAF metadata? No, the metadata describes only the PDS RELFILE; metadata for individual files must be yet elsewhere, perhaps in the SMPMCS. (You can tell I've never worked with a UNIX product packaged for SMP/E) o SMP/E or at least GIMUNZIP is a prerequisite for receiving. How about going the other way: a "pax -z" archive containing simple UNIX files (pax keeps metadata in more files) plus Classic data sets flattened with AMATERSE or TRANSMIT. Timothy's ply plus remarks by Ed J. nicely describe an effect of Conway's Law. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
