As many of you know, to qualify for Parallel Sysplex software pricing aggregation there are a few requirements. One requirement is that you have to run at least one qualifying service from a list of about 20.
I'm working with a couple customers who are new to Parallel Sysplex and aggregation, and I wanted to get some feedback from more experienced IBM-MAINers about your "favorite" service(s) for beginning customers. Bear in mind that these are customers who are extremely focused on service quality, and they're used to having physically separate systems (or at least non-aggregated LPARs). They'd like to qualify for aggregation, but they want to make sure that separate LPARs are kept as separate as possible, with the lowest possible risk that "bad things" happening in one LPAR could affect the others. In other words, they're slowly gaining confidence. (Even though it's not, think of this situation as if there were two separate companies sharing two mainframes, each company with one LPAR on each mainframe. The goal is to bring all four LPARs into one Parallel Sysplex using one of the qualifying services while making sure that Company X can't affect Company Y and vice versa.) So what are your favorites in this role? System Logger LOGREC? RACF database caching? JES2 checkpoint in the coupling facility? MQ shared queue? Thanks for any advice. - - - - - Timothy Sipples IBM Consulting Enterprise Software Architect Specializing in Software Architectures Related to System z Based in Tokyo, Serving IBM Japan and IBM Asia-Pacific E-Mail: [EMAIL PROTECTED] ---------------------------------------------------------------------- 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
