Brings to mind a near catastrophe in a previous shop where SYS1.PARMLIB was kept on sysres. 'For compatibility' of course. Our VTAM guy made a change on one system single-box that involved APF list. Shortly thereafter we switched sysres for maintenance. The load library change was off of sysres, so it remained, but the APF list change got replaced with the copy on the already-copied new sysres. After IPL, VTAM would not come up. Logon impossible. Remote data center in the Bay Area; we were in LA. We were about to jump in a car and make the trip north when we figured out a fix, which involved running a job that an operator *literally* punched onto cards.
Self-inflicted wound. Survived through a mechanism that has long ceased to exist. No one needs that level of anxiety. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Eells Sent: Tuesday, November 29, 2016 9:33 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Catalogs in a SYSPLEX Jesse 1 Robinson wrote: > I have to admit that locating MCAT on sysres avoids one step that we need to > take. We run seven 'sysplexes' (some monoplex) that do not share any > resources including MCAT. When we install a new release, there are often new > sysres data sets that need to be cataloged on any plex by the time the new > release gets migrated there. We have a Rexx that ferrets out any new data > sets in the SMP/E 'master catalog' and creates a batch job with DEF NVSAM > commands. That job gets sent to all sysplexes as soon as SMP/E install is > complete. New catalog entries cause no problem. Old catalog entries that > really ought to be deleted don't cause problems either except for OCD types. Of course, it introduces other steps, such as IMPORTing the usercats for each plex, and either freezing or keeping current and master-catalogs-to-be in sync. <snip> -- John Eells IBM Poughkeepsie ee...@us.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
