IIRC, we started with Operlog en Jes2 Checkpoint for the same reason. Operlog is both easy to implement and nice to have. We moved JES Chkpt back to disk later, because of the slightly more complicated procedures and the lack of benefit in a 2-system Sysplex and because we had other exploiters then.
Kees. "Timothy Sipples" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED] om>... > > 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 > > ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************************** ---------------------------------------------------------------------- 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
