And test your S-A IPL and your Disaster Recovery plan every so often. Bill Fairchild, Senior Software Engineer ASG Software Solutions 1333 Third Avenue South Naples, FL 34102-6400 USA
----- Original Message ----- From: "Clark Morris" <[email protected]> To: [email protected] Sent: Monday, June 16, 2014 8:08:20 PM Subject: Stand-alone Restore was Re: Dataset in Two master catalog On 16 Jun 2014 10:55:47 -0700, in bit.listserv.ibm-main you wrote: >Well, there's one thing that scared me even more: finding you need >stand-alone restore to get the enterprise system up and finding you >don't have a functional S-A tape to IPL. Didn't happen to us, but I >remember several decades ago hand-carrying our S-A dss and DSF tapes >across town to another data center to help them (successfully) get their >system back. Makes one think about your own procedures: Starting >keeping multiple copies of our most current S-A IPL tapes at that point >with one set off-site. My boss made me put the stand-alone restore program (for FDR in our case) as the first file on every dump. The pain of hitting load 5 times (VOL1, HDR1, HDR2, tape mark, the standalone program) was more than offset by the lack of having to find the correct version of the standalone restore program. Clark Morris > >S-A restore should be a last resort to recover from an IPL failure >(having a functional alternate system from which repairs can be made is >much quicker and more useful), but S-A restore is still an essential >part of last line of defense. Saved our tails on at least several >occasions over the course of 30 years. As John points out, for S-A >restore obviously one must at a minimum also have external documentation >of critical device addresses and volsers. As an extension of that and >part of our nightly DR backup we started producing nightly VTOC listings >of all production drives (saved on workstations, not printed), which >provided some useful tracking of physical location of long-term data sets. > Joel C. Ewing > >On 06/16/2014 10:54 AM, Skip Robinson wrote: >> Blessed are the pessimists, for they shall take backups. ;-) >> >> OTOH nothing scares me more than the prospect of depending on stand-alone >> restore to IPL the enterprise. >> >> . >> . >> J.O.Skip Robinson >> Southern California Edison Company >> Electric Dragon Team Paddler >> SHARE MVS Program Co-Manager >> 626-302-7535 Office >> 323-715-0595 Mobile >> [email protected] >> >> >> >> From: "R.S." <[email protected]> >> To: [email protected], >> Date: 06/14/2014 08:33 AM >> Subject: Re: Dataset in Two master catalog >> Sent by: IBM Mainframe Discussion List <[email protected]> >> >> >> >> W dniu 2014-06-13 19:25, Skip Robinson pisze: >>> Just as matter of recommended practice, putting a shared IODF cluster in >> a >>> user catalog for the entire enterprise creates a huge dependency on that >>> user catalog. The user catalog could go south (unlikely) or--worse--the >>> shared IODF might get deleted by accident, making any IPL more or less >>> wishful thinking. >> That's why we do backups. Especially such important files. >> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
