A basic sysplex will provide z/OS availability, an improvement over single image. This can be done for the cost of a few CTC connections between LPARS. If you have the spare channels to define as CTC's, this is fairly easy to do.
IIRC, (I know someone will correct me if I am wrong) a basic sysplex will also provide PDSE sharing within the sysplex. AFAIK there is no way with IBM vanilla code to share PDSE's across a SYSPLEX boundary (either monoplex or multi-system). Some 3rd party products will support this. <snip> > Unless your two systems are in the same Sysplex (Base or Parallel) I would > highly recommend that you do not share your sysres disk...they contain PDSE > datasets that you shouldn't share outside a sysplex. > > Similarly, any disk you do share should not contain PDSE datasets. We're slowly coming to this realization. We don't have a Sysplex, and sharing PDSE's, while it works somewhat, doesn't work that great. My personal libraries are PDSEs and if I am logged on to both PROD and DEV at the same time I have to make sure I am not trying to edit members in the same PDSE in both environments. Blech. I thought PDSEs were the future? </snip> ---------------------------------------------------------------------- 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
