Sharing catalogs outside of the sysplex (i.e. with connected LPARs that just "happen" to not be in the sysplex), is perfectly fine as long as you remember that it's impossible for them to share the information stored in the CF's, so if you cache the catalog(s) in the CF you will need to stop doing that. Otherwise there is no real danger involved and in fact it is done all the time.
I can't stress enough though that you can't treat it like all of your plexed systems are able to cache it in the CF and the "other" LPAR will magically get that cache somehow, because it will not. Now, assuming you don't mind having a slight bit more overhead by not caching the catalog(s) in the CF, you should have no problems. Also, it's normally a really good idea if you are going to share your catalogs, that you share them all. Unless you are very regimented (and careful), because you could end up with some issues (data management wise), where some datasets are cataloged and some are not, this can be a real issue with SMS dataset and also when you run your tape management processes, so unless you are careful, sharing just a subset is pretty dreadful. So, either share them all, or don't share any. As long as you aren't caching them (in the CF structures) you will be fine. People do this all the time where they have a sysplex and a test or sandbox system or they have LPARs that they are trying to combine. It's just like running several LPARs on the same BOX that are not SYSPLEXed, it works fine. Just remember that the DASD needs to be shared and there will be reserves, (but they are catalogs so it's minor and not many). It's also a good idea when sharing DASD at all to have GRS involved (or MIM). Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
