> On Nov 21, 2017, at 10:24 AM, Jesse 1 Robinson <jesse1.robin...@sce.com> > wrote: > > In addition to IEBUPDTE-like utilities, StarTool (and I would hope its CBT > predecessor) has a REPLACE function that can scan an entire PDS(E) and > replace one string with another as long the result does not exceed line > length. It allows such filters as WORD, PREFIX, and SUFFIX. You can make a > trial run to examine the results without actually updating anything before > doing it for real. Several other options are included as well. Something to > keep in mind. > > . > .
Skip: I never had the free tool, I always used the $$ version. I also will freely admit it has saved my ass many a time. Little story: Way back in the XA days, we had just put an enormous number of JES2 fixes on and I *DID* look at each hold on the 30-40 fixes. None of them mentioned the fact that JES2 would no longer accept a specific JECL parameter. About 0500 I had just let the production system go, so they started to run jobs. About 5 minutes later I get a call saying something is wrong and the JECL parameter is flagged as an error. I started to look at it and to me it seemed valid, so I headed for the manual and it agreed with what I was saying it was valid. I was sweating as I didn’t want to back out all the maintenance. I looked at other option and found one. I had no idea how many of these were in production. I did a quick scan of the library where production came out of and found 10 jobs. I said to myself go for it, so I did a scan/replace and it found the 10 jobs. I called back to production control and asked them too resubmit. Just about the time he submitted it, The VP walked into the office of the supervisor where I was at and asked if we should back out as we had until 6 AM of the stock markets would not open. I said wait one minute and I called back to production control and the job ran successfully. I turned around to the VP and said, no everything is fine. He looked at me and said he had been told there was a major issue and I said no sir, it was a minor issue which has been fixed. After that morning I went back through every JES2 fix that went on and there was NOT a single hold. I then went back and read the cover letters and found the blasted fix. I called in to the support center and bitched at the level 1 people and asked to be connected to level 2. I let level 2 know in no uncertain terms that a HOLD was mandatory for something like this. I didn’t get a lot of oops we are sorry, so at the next SHARE, I buttonholed one of the JES2 IBMers and raged on him. From then on JES2 was good at putting out holds on PTFS. Ed ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
