Hello Lucas, In practical terms you could share a sysres volume set across multiple environments, so long as you guarantee that they never get updated.
In our environment we did that once. Now we have separate sets for Production / Test / Sysmaint. (due to inadvertant changes happening to production when someone updated the test sysres.) Now what did I say about "never get updated". :-) In practice, the active sysres datasets do get updated for various reasons. (especially since many of our systems stay up for > 6 months between IPLs) Consider having multiple cycles of sysres sets. (not just 2 flip flop sets). We use a minimum of 3. Since, after some IPLs, we could have cycle B active on prod sysplex member #1, cycle C ative on prod sysplex member #2, with cycle A being the backout set for sysplex member #1 and cycle B being the backout set for sysplex member #2. There is at least 1 PDSE dataset on the sysres set (TCPIP - SEZALOAD) that must not be updated across sysplexes without major problems occurring. Regards Bruce Hewson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
