Pre-SVS IEBCOPY didn't have the PDS unload feature that is probably what most of us think of as the raison d'etre of IEBCOPY these days. IEHMOVE was the unload tool. And as Joe M. says, it was riddled with bugs, several of them of the "copy dataset, delete old version, oops - the new version wasn't created - too bad" form. I remember playing the "prefix-TURKEY" game, and no-one ever had much trouble guessing which program was being discussed:
IEHTURKEY - IEHMOVE IEDTURKEY - TCAM IHKTURKEY - CRJE etc. IIRC, SVS IEBCOPY had to run APF authorized so that it could use EXCPVR; neither of which concept existed in MVT. Perhaps the tweak changed EXCPVR to EXCP, and remove a TESTAUTH or MODESET or two. Tony H. > -----Original Message----- > From: VM/ESA and z/VM Discussions > [mailto:[EMAIL PROTECTED] On Behalf Of Joe Morris > Sent: Sat 22 October, 2005 11:47 > To: VMESA-L@LISTSERV.UARK.EDU > Subject: Re: IEH/IEB/... names? > > Jay Maynard <[EMAIL PROTECTED]> writes: > >On 2005-10-21, Joe Morris <[EMAIL PROTECTED]> wrote: > > >>>IEBCOPY - is a data-set utility used to copy one or more (PDSes) > >>> or merge (PDSes) > >> As distributed it wouldn't work under OS/360. I made a > small tweak > >> to it (details of which I don't recall but IIRC it involved an > >> appendage) and it ran quite happily for several years on OS/360. > > >I'll have to look at the Hercules OS/360 package, which > includes a copy > >of IEBCOPY for OS/360...wonder if it's your work. > > My tweak was to retrofit the SVS version of IEBCOPY back to > OS/360. There always was an IEBCOPY in OS/360, but it > required a DD card for every data set involved. The SVS > version of the utility gave you most of the file-copy > features of IEHMOVE without the infestation of bugs. > > My notes from the tweak stayed with my PPOE. I don't recall > if I ever put it on the Michmods (SHARE) tape, but I'm > getting a vague recollection that the SVS version had an SIO > appendage...and the tweak was disabling it (the appendage > probably was required to control page presence in SVS, an > issue that OS/360 didn't have to worry about). Or maybe it > was something else; it *has* been a few years. > > > >>>IEHIOSUP - is a system utility used to update TTR entries in the > >>> transfer control tables of the supervisor call library > (SVC lib). > >>> IEHSISUP must be used after: the SVC lib is moved. The > OPEN, CLOSE, > >>> TCLOSE, EOV,... & other modules are changed or replaced in the > >>> SVC lib. > >> Worse than that: you had to remember to rerun it whenever you > >> replaced > >> *any* SVC load. > > >The initial starter MFT system build for Hercules ran into a > >chicken-and-egg > >problem: How do you run IEHIOSUP to set up the TTRs if you > don't have a > >system to run it on? Roger Bowler wound up writing a utility > that does > >the update, by finding SYS1.SVCLIB and processing the PDS > directory - > >and parsing the AWSCKD image to get there. > > Back in ye olde days a new installation was bootstrapped > using the dump/restore starter system you ordered from PID. > Once the installation got a locally-configured build it in > turn could be used to initialize the next system build's SVCLIB. > > Joe Morris >
