> On Jun 14, 2017, at 8:47 AM, Turner Cheryl L <[email protected]> wrote: > > was hoping you'd chime in John (and I appreciate the responses from Skip, > Lizette and EdG, as well). Since I am the person that does the maintenance > and OS upgrades now, I was taking it upon myself to be a bit proactive (or > creating busy work?) and looking at the EREP reports for potential problems > where there may be PTFs available but maybe we just didn't have them on at > the time due to our maintenance windows. We are still in the process of fine > tuning which reports to generate and we are unloading the reports to GDGs . > > So I will summarize the advice as this: Look at them, as you have time. > Decide if any of them are a true problem or something worth investigating > further, check out IBMLINK and/or look for a way to fix it. Open a PMR to > IBM/vendor if really unsure. > > But I still can't get my head around, why cut 100's of symptom/software > records a day at all for a particular problem, if we're just going to ignore > them - abend or not. But I'll try to let that not keep me awake at night. > > Thanks everyone.
I don’t know about others but I like a clean ship. Its a few minutes a day routine. If you spot anything that looks unusual then its worth a look. Unusual is different for each person. If I saw more than 2 that was unusual to me. The research was done with the daily look at any hyper APARS. The number of hypers was small (usually). I hated to call IBM for a problem that was already addressed. Generally talking with IBM was not an issue except for thing like CBPDO and other system distributions. The CBPDO calls turned to longish calls and were on average the least productive. Other places at IBM were superb and it was 5 minute at most, unless we forget the PSF people who were thorough and understood traces better than I. When it came to level 3 the phone calls were longish but except for a couple of instances relatively painless. When I got into a disagreement with level 2, I just called the duty manager and explained the issue and he seemed to always come out on my side. This clean ship as I called it, showed in the fact we almost always never had an outage due to software. We were on the bleeding edge with DASD and always had to keep DFDSS up to date. That was the other reason I kept the system up to date. Ed ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
