On Thu, Sep 21, 2017 at 5:42 PM, Jesse 1 Robinson <[email protected]> wrote:
> 'Override' libraries give me the willies. War story. Shortly after I > started here, VTAM would not come up one Sunday after a maintenance IPL. > Turned out that some modified VTAM module(s) had been placed 'temporarily' > into an override library for testing and promptly forgotten about. The perp > had a note *in plain sight* on his wall to remind him of this maneuver. It > had been there so long that he no longer saw it (!). Willies, I tell you. > I can see that. But, then again, how is that any different from forcing this person to put the module into the "regular" library "for testing"? I don't put "for testing" modules into my system specific "override" libraries. If I had some sort of "for testing" library, I would manage it like we do our "quick fix" libraries. These are "production" load libraries to which the programmers have WRITE access. If a production problem occurs over night and they need to put in a "patch", they do it by linking into one of these libraries. And at noon every day (even weekends), we clean out _everything_ from these libraries. This may result in another outage next cycle if the programmer doesn't get a fix into production in time. But that is the cost that we & they just need to pay. Nothing will stay in a "quick fix" library longer than 24 hours. > > . > . > 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] > -- *L'Shanah Tovah Tikatevu* Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
