I have been able to graft a TAPE=TAPn function into PIPEDDR. It probabl y isn't the way the original author would have liked it, but it works for n ow.
I have had some luck with contacting other contributors to the Downloads page and would like to continue that. My client's dependency on programs like this really has nothing to do with the legal aspects of any of this. The only considerations are that it doesn't cost them anything and they c an blame me when it doesn't work after I am dead and gone. Having someone to blame is a pretty good midigation for risk. But my basic process is to try to get the current tools to work before throwing them away for something completely different. So I ask about CKDSVRST before switching completely to PIPEDDR. /Tom Kern On Tue, 13 Mar 2007 09:27:06 +0100, Rob van der Heij <[EMAIL PROTECTED]> wrote: >On 3/12/07, Thomas Kern <[EMAIL PROTECTED]> wrote: > >> Like PIPEDDR, which does use "trackread" & "trackwrite" but doesn' t write to >> tape or restore to a larger minidisk. > >I suppose the PIPEDDR adds some additional checks to protect your own >feet. But the basic stages add no such restrictions. You can certainly >write your data to a tape with CMS Pipelines, and if you look at a few >of your CKDVRST tapes you can probably reverse engineer it and have >the pipeline restore those files. >For copying local disks track by track the function is close to DDR >(but probably a bit easier to incorporate in an existing program). >With a FORMAT RECOMP you can have CMS fix up after copying to a larger >disk. > >> It would help if IBM released the source code to these programs when t heir >> internal support retires. Or remove them from the public offering. > >I ensure you many would get in trouble if IBM would withdraw products >once the author retires or leaves the company ;-) If the legal >folks (and programmers) at IBM had any fear about such obligations, we >would never have those download pages in the first place. >But it certainly makes sense to think about your dependency such >things if you can. Frequently I find CMS Pipelines helpful to put >things together again when something breaks. > >Rob >======================== ========================= ========================
