The term I remember was 'delta tapes'. You could only get them by hand from your SE. It was a chaotic time.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Edward Gould Sent: Tuesday, April 11, 2017 10:39 AM To: [email protected] Subject: (External):Re: DF/EF and DFP was Re: z/OS PL/I 5.1 with "continuous delivery announced". > On Apr 11, 2017, at 11:59 AM, Clark Morris <[email protected]> wrote: > > [Default] On 11 Apr 2017 06:12:34 -0700, in bit.listserv.ibm-main > [email protected] (John McKown) wrote: > >> On Tue, Apr 11, 2017 at 8:10 AM, David Crayford <[email protected]> wrote: >> ———————SNIP------------------------------------------------------ >> ?Why am I shuddering? and thinking "shades of JES2 level set PTFs"? >> Of course, nothing will heal the scars from DF/EF. > > > I remember Jamie Yates then with IBM getting up in front of a SHARE > session and among other things saying IBM had customers calling in > with SEV 1 DF/EF catalog problems before they experienced one because > they would have one by the time they got a call back. He had other > horror stories. > > I got very familiar with PE chains on DFP and nearly canceled going to > SHARE because of potential problems. I called it Darned Fragile > Product. > > Clark Morris > At the time we were doing an upgrade from VS1 to MVS. I can attest the the LONG pe chains, it was causing me nightmares at home and at work. On one day I received 3 round real tapes (6250 BPI) with fixes on. My memory is sketchy but it seemed like it took several days of receiving and applying to get the fixes on. We were getting to the point we had to freeze maintenance as we were going live in a week. I guess we lucked out as there were very few PTFS that needed to be fixed. Astonishingly we went live the next week and nothing broke. We then had to migrate the MVS to a remote site. Somewhere along the lines another mega ptf tape showed up. We bit the bullet and didn’t receive the maintenance, Somehow it all worked. The next big was converting to NJE and surprisingly it went off without a issue (2 small jcl issues non NJE/JES2) . During this whole mess we were getting calls in the 0 dark thirty hours that jobs were running too fast and there had to be something wrong. I talked the people into checking the outputs and the totals etc and they were agreeing with the numbers they were expecting, but something HAD to be wrong. I got to work at 230 AM and the entire nights workload was complete (instead of 7 AM). I double checked the numbers and said what is the problem? Again they insisted that jobs were running way to fast, I called up the VP and spoke to him and explained the situation. He asked me for my opinion and I told him that this was to be expected as MVS buffered I/O a lot better than VS1 and had a lot better performance. He then asked should we “publish” (this means sending data to the options exchange and I said go for it. I gave the phone to the supervisor and they talked for a few minutes and they hung up and said lets publish. We broke all records and all the data was good. On the negative side a few months later we had to upgrade our memory as paging was going wild. That put “us” in the bad boy column because it cost us money to upgrade. Ed ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
