On Fri, 2 Sep 2005 12:04:19 -0500, Tom Schmidt wrote: >On Fri, 2 Sep 2005 17:38:21 +0200, Lucas Morton wrote: > >>I'm in the process of redesign out z/OS infrastructure: In 1 year we >>increased our z/OS system images from 2 (1 production and 1 testing) >>to 6 (2 in production sysplex, 2 dev. and 2 test). So I think that a >>shared SYSRES might simplify the thing. >> >>Should I share SYSRES between sysplexes? I now that I can't share >>PDSE's outside a plex, so I will clone volumes with PDES, but.. what >>about the other O.S. and Software datasets?. > >Lucas, > >You don't mention whether you have MIM available to span ENQs across your >plexes, so I'll presume that you don't. If that is correct, then you >should NOT share a sysres across plexes since you will not have data set >integrity from one plex to the next. > >Clone the sysres to make things easier for you for sure, but don't share >without dataset integrity. (Bad things(tm) happen if you lose integrity.) > >-- >Tom Schmidt >Madison, WI
Sorry for answering my prior post, but you ought not share sysres from test to development to production anyway: You should roll your sysres maintenance up through those levels (for quality control) just as your applications should roll up through those levels. So whether you have MIM or not, you ought to maintain an offline (not-in- use) SMP/E 'target' sysres, then one* IPL sysres for each level (test / dev / prod) with the prod sysres being the top of your hierarchy. You could, if you have the DASD, also have 2 IPL sysres at each level (say, A and B) with one being used currently and the other as the former/next value for clone purposes. Several shops that I know of do essentially that. -- Tom Schmidt Madison, WI ---------------------------------------------------------------------- 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
