Our parmlib members (including IEASYMxx) are the same for home and DR. This reduces the level of surprise when we test/declare. The first DR IPL is done with an Operator prompt. This first IPL the sysplex specific settings are updated, before we re-IPL the full environment.
Part of the reason we do it this way is because the DR supplier can't guarantee the hardware we'll run on (model/serial#), so the CFRM policy will need to be updated at the time of the test/declare. Bart -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of mf db Sent: Monday, February 17, 2014 6:30 AM To: [email protected] Subject: IEASYMxx in DR Hello All, Just looking for a general idea of sharing IEASYMxx in DR site. How many of you intend to keep a different IEASYMxx member in production site and another for DR(Disaster recovery) site or else keeping One IEASYMxx across production and DR would be a good choice ? Just looking for some idea. Any pointers ? Peter ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
