There is potentially an IBM Software Pricing issue with splitting a sysplex.
IBM pricing, since parallel sysplex was introduced, has allowed machines to be aggregated together for pricing. There are some complicated rules and a red paper which describes the rules is available at <https://www.redbooks.ibm.com/abstracts/redp3967.html>. It is more than 10 years old, but still applicable (unless you are using IBM's Country Multiplex Pricing in which case it doesn't matter). In brief, you need a "primary" sysplex using more than 50% of the CPU time on each machine during a user/site determined "prime shift". So if you have two machines aggregated today and after this split one is primarily PRODUCTION and the other is primarily DEVELOPMENT you won't be able to aggregate them. So you'll want to spread the larger of the sysplex across both machines. The same applies if you have more than two machines; spread your primary/larger sysplex across all the machines. Loosing aggregation is very expensive. However, you could start using IBM's Country Multiplex Pricing (CMP) to avoid this problem. Again, in general, if your workload is growing overtime you should be OK. IF your workload is shrinking then CMP may not save you money, and could cost you money. Again, the rules are complicated. Al Al Sherkow, I/S Management Strategies, Ltd. Consulting Expertise on IBM Workload License Charges (WLC) and LCS Software Seminars on IBM Mainframe Software Pricing +1 414 332-3062 www.sherkow.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
