Download as PDF, PPTX
Uploaded byRobert Hain
IMS11 BMC Susbystem Optimizer - subzero
The document discusses BMC Subsystem Optimizer for zEnterprise (Subzero), a product that allows CICS, DB2, and IMS databases to run on separate logical partitions (LPARs), reducing monthly license charges. It provides examples where Subzero lowers costs by 16-30% by optimizing workload placement across LPARs. Technical details are also given on how Subzero intercepts and routes data requests between subsystems on different LPARs without requiring application changes.
More Related Content
Similar to IMS11 BMC Susbystem Optimizer - subzero
IMS11 BMC Susbystem Optimizer - subzero
- 1. Lead Product Manager david_schipper@bmc.com May2015 David Schipper BMC Subsystem Optimizer for zEnterprise® Reducing Monthly License Charges
- 2. Agenda Sub-capacity Pricing andMonthly License Charges (MLC) BMC Subsystem Optimizer for zEnterprize (Subzero) Use cases Technical details Roadmap
- 3. Survey Says… Source: BMCSoftware 2014 Mainframe Survey 3% 16% 26% 27% 34% 34% 44% 47% 48% 52% 70% Other Outsourcing Big Data Mobility Cloud Implementation Data Recovery Business / IT Alignment Data Privacy Application Modernization Application Availibility IT Cost Reduction / Optimization
- 4. Hardware 20% IBM OTC 5% ISV10% MLC Software - z/OS, DB2, IMS, CICS, etc… 30% Other 10% People 25% Peak 4HRA MSUs Peak Processing MIPS What the business wants: •Reduce MLC monthly charges •Reduce MIPS required •Improve performance and availability in the process What Drives Mainframe Costs?
- 5. Sub-capacity pricing IBM MLCsoftware charged at peak MSU usage Not based on full machine capacity Key metric is the 4 Hour Rolling Average (4HRA)
- 6. Sub-capacity pricing –Single LPAR % of Expense % of MSU Peak z/OS @ $85/MSU - 542 MSUs $46,070 24% 29% IMS DB @ $125/MSU - 542 MSUs $67,750 35% 6% DB2 @ $75/MSU - 542 MSUs $40,650 21% 23% CICS @ $72/MSU - 542 MSUs $39,024 20% 26% Other 0% 17% Total $193,494 37 39 30 32 35 30 82 87 92 76 81 84 101 105 123 102 98 101 110 105 142 120 125 127 150 140 155 122 120 132 0 100 200 300 400 500 600 1 2 3 4 5 6 4-Hour Rolling Average IMS DB Other DB2 CICS z/OS 542 ……………………….…………………… 719 720
- 7. 35 32 1830 24 35 45 42 46 37 44 39 115 117 102 110 107 97 105 110 98 101 125 128 135 130 112 141 155 150 0 100 200 300 400 500 1 2 3 4 5 6 4-Hour Rolling Average IMS DB Other DB2 CICS z/OS 37 39 30 32 35 30 82 87 92 76 81 84 101 105 123 102 98 101 110 105 142 120 125 127 150 140 155 122 120 132 0 100 200 300 400 500 600 1 2 3 4 5 6 4-Hour Rolling Average IMS DB Other DB2 CICS z/OS Sub-capacity pricing – LPAR Aggregation ……………..…….….…….……… 719 720 ……………….…….….…….………719 720 480 476 542 452 459 449455 419 376 431435 474 915 907 918 871 914 923 915 907 918 871 914 923 % of MLC Expense % of MSU Peak z/OS @ $85/MSU - 923 MSUs $78,455 24% 31% IMS DB @ $125/MSU - 923 MSUs $115,375 35% 7% DB2 @ $75/MSU - 923 MSUs $69,225 21% 21% CICS @ $72/MSU - 923 MSUs $66,456 20% 28% Other $0 0% 13% Total $329,511
- 8. Survey Says…… Source: BMCSoftware 2014 Mainframe Survey 1% 7% 17% 24% 29% 36% 37% 39% Other None of the above Use 3rd-party software to manage peak 4HRA Monitor 4HRA real-time Use defined capacity to limit 4HRA Configure WLM to automatically manage performance Tune workloads to reduce MSU utilization Move workloads to run outside of 4HRA
- 9. IBM’s Software CostReporting Tool (SCRT) MLC Product Name MLC Product ID Tool MSUs z/OS V1 5694-A01 642 DB2 10 for z/OS 5605-DB2 579 DB2 V9 for z/OS 5635-DB2 642 DB2 UDB for z/OS V8 5625-DB2 579 DB2 UDB for OS/390 V7 5675-DB2 309 DB2 UDB for OS/390 V6 5645-DB2 109 CICS TS for z/OS V4 5655-S97 315 CICS TS for z/OS V3 5655-M15 287 CICS TS for OS/390 V2 5697-E93 212 CICS TS for OS/390 5655-147 140 CICS/ESA V4 5655-018 131 WebSphere MQ for z/OS V7 5655-R36 560 MQSeries for z/OS V6 5655-L82 511 MQSeries for OS/390 V5 5655-F10 89 MQSeries MVS/ESA 5695-137 109 LPAR LPAR LPAR LPAR LPAR Product Name Product ID Highest Date/Time DB2A DB2B ESAJ ESAM IMSA z/OS V1 5694-A01 642 19 Sep 2011 - 22:00 UTC 29 157 103 9 39 DB2 10 for z/OS 5605-DB2 579 19 Sep 2011 - 22:00 UTC 29 157 103 0 39 DB2 V9 for z/OS 5635-DB2 642 19 Sep 2011 - 22:00 UTC 29 157 103 9 39 DB2 UDB for z/OS V8 5625-DB2 579 19 Sep 2011 - 22:00 UTC 29 157 103 0 39 DB2 UDB for OS/390 V7 5675-DB2 309 22 Sep 2011 - 22:00 UTC 0 0 93 0 0 DB2 UDB for OS/390 V6 5645-DB2 109 08 Sep 2011 - 17:00 UTC 0 0 0 0 0 CICS TS for z/OS V4 5655-S97 315 29 Sep 2011 - 23:00 UTC 0 0 46 0 0 CICS TS for z/OS V3 5655-M15 287 06 Sep 2011 - 22:00 UTC 0 0 0 0 0 CICS TS for OS/390 V2 5697-E93 212 26 Sep 2011 - 23:00 UTC 0 0 28 0 0 CICS TS for OS/390 5655-147 140 14 Sep 2011 - 22:00 UTC 0 0 0 0 0 CICS/ESA V4 5655-018 131 08 Sep 2011 - 20:00 UTC 0 0 0 0 0 Difficult to understand…doesn’t provide cost. Just a reporting mechanism for IBM’s billing system… Does not identify opportunities for savings….
- 10. 10 Steps toReducing Mainframe MLC Costs 1. Understand the Cost Base 2. Analyze Peak Workloads 3. Implement Capping 4. Review Workload Placement 5. Leverage Technology – the Benefit of Technical Currency 6. Review the SCRT Process 7. Manage the Entire Software Portfolio 8. Evaluate Possibilities to Qualify for Special-Situation Terms 9. Investigate Alternative Licensing Metrics 10. Plan Procurement Negotiation Strategy Source: White paper by David G. Wilson President and General Manager, SZS Consulting, Ltd Analyze Negotiate Take Action
- 11. Need to thinkdifferently • Taking MLC cost savings to the next level • Overcoming technical limits • Thinking outside the box
- 12. BMC Subsystem Optimizerfor zEnterprize® (Subzero) The Why… – IBM requires that CICS, DB2, and/or IMS DB run on the same LPAR if a CICS transaction access DB2 or IMS DB – Increases MLC since all are billed at the combined peak The How… – Remove this IBM requirement and lower MLC – No application code changes required – Utilizes IBM published facilities The What… – Flexibility on where you can run CICS, IMS, and DB2 – Enhanced system redundancy and recovery options – Further workload balancing options
- 13. LPAR1 CICS DB2 or IMS DB Subzero Subzero LPAR2 1.CICS application SQL or DL/I calls are intercepted by Subzero 2. Subzero routes the data access request to the appropriate DBMS 3. DB2/IMS DB processes the data request and returns the requested data 4. Subzero routes the result set back to the initiating CICS application Subzero BMC Subzero basics
- 14.
- 15. Annual savings $791,280 LPAR1 284 LPAR 2 447 LPAR 3 511 LPAR 4 296 Add 3% for Subzero overhead 46 Aggregate monthly peak R4 1584 z/OS @ $72/MSU - 1584 MSUs $114,022 IMS @ $125/MSU - 958 MSUs $119,738 CICS @ $72/MSU - 1584 MSUs $114,022 Monthly MLC fee $347,782 -16% Subzero use case – CICS/IMS DB data sharing With Subzero CICS 284 MSU CICS 273 MSU IMS 117+121 MSU CICS 296 MSU CICS 224 MSU IMS 96+127 MSU Subzero Subzero Subzero Subzero LPAR 1 LPAR 3 LPAR 4 LPAR 2 Without Subzero LPAR 1 405 LPAR 2 320 LPAR 3 390 LPAR 4 423 Aggregate monthly peak R4 1538 z/OS @ $72/MSU - 1538 MSUs $110,736 IMS @ $125/MSU - 1538 MSUs $192,250 CICS @ $72/MSU - 1538 MSUs $110,736 Monthly MLC fee $413,722 LPAR 1 CICS 284 MSU IMS 121 MSU LPAR 3 CICS 273 MSU IMS 117 MSU LPAR 4 CICS 296 MSU IMS 127 MSU LPAR 2 CICS 224 MSU IMS 96 MSU
- 16. Without Subzero LPAR 1405 LPAR 2 320 LPAR 3 390 LPAR 4 423 Aggregate monthly peak R4 1538 z/OS @ $72/MSU $110,736 IMS @ $125/MSU $192,250 CICS @ $72/MSU $110,736 Monthly MLC fee $413,722 LPAR 1 - CICS 115 LPAR 3 - CICS 203 LPAR 2 - IMS 610 LPAR 4 - IMS 610 Add 3% for Subzero overhead 46 Aggregate monthly peak R4 1584 z/OS @ $72/MSU - 1584 MSUs $114,058 IMS @ $125/MSU - 1220 MSUs $152,500 CICS @ $72/MSU - 318 MSUs $22,896 Monthly MLC fee $289,454 -30% Annual savings $1,491,216 Subzero use case – LPAR isolation LPAR 1 CICS 62 MSU IMS 343 MSU LPAR 3 CICS 140 MSU IMS 250 MSU LPAR 4 CICS 63 MSU IMS 360 MSU LPAR 2 CICS 53 MSU IMS 267 MSU With Subzero CICS 62 MSU Subzero Subzero Subzero LPAR 1 LPAR 3 LPAR 4 LPAR 2 CICS 53 MSU CICS 140 MSU CICS 63 MSU IMS 343 MUS IMS 267 MSU Subzero Subzero Subzero IMS 250 MSU IMS 360 MSU
- 17. With Subzero Without Subzero LPAR1 - CICS/DB2/IMS 405 LPAR 2 - CICS/DB2/IMS 320 LPAR 3 - CICS/DB2 390 LPAR 4 - CICS/DB2 423 Aggregate monthly peak R4 1538 z/OS @ $72/MSU - 1538 MSUs $110,736 DB2 @ $75/MSU - 1538 MSUs $115,350 CICS @ $72/MSU - 1538 MSUs $110,736 IMS @ $125/MSU - 725 MSUs $90,625 Monthly MLC fee $427,447 LPAR 1 - CICS/DB2 324 LPAR 2 - CICS/DB2 256 LPAR 3 - CICS/DB2 390 LPAR 4 - CICS/DB2 423 LPAR 5 - IMS 145 Add 3% for Subzero overhead 46 Aggregate monthly peak R4 1584 z/OS @ $72/MSU - 1584 MSUs $114,058 DB2 @ $75/MSU - 1393 MSUs $104,475 CICS @ $72/MSU - 1393 MSUs $100,296 IMS @ $125/MSU - 145 MSUs $18,125 Monthly MLC fee $336,954 Annual savings $1,085,916 Subzero use case – isolating IMS LPAR 1 CICS 62 MSU DB2 262 MSU LPAR 3 CICS 140 MSU DB2 250 MSU LPAR 4 CICS 63 MSU DB2 360 MSU LPAR 2 IMS 81 MSU CICS 53 MSU DB2 203 MSU IMS 64 MSU LPAR 2 LPAR 2 IMS 81+64 MSU Subzero LPAR 5 Subzero LPAR 1 CICS 62 MSU DB2 262 MSU LPAR 3 CICS 140 MSU DB2 250 MSU LPAR 4 CICS 63 MSU DB2 360 MSU LPAR 2Subzero CICS 53 MSU DB2 203 MSU Subzero
- 18. Without Subzero With Subzero DB2or IMS on LPAR 1 must be restarted before CICS on LPAR 1 can process transactions Subzero can automatically redirect DB2 or IMS calls from CICS on LPAR 1 to DB2 or IMS on LPAR 2 LPAR 3 CICS DB LPAR 4 CICS DB LPAR 1 CICS DB LPAR 2 CICS DB x LPAR 3 CICS DB LPAR 4 CICS DB LPAR 1 CICS DB LPAR 2 CICS DB x SUBZEROSUBZERO SUBZEROSUBZERO Database redundancy example
- 19.
- 20. CICS Architecture and ProcessingFlow LPAR1 LPAR2 Subzero Common Code Subzero Subsystem Server Subzero Subsystem Server DFSPRRC0 (IMS) Subzero Common CodeDSNAPRH (DB2) Subzero Controlling Agent XCF XCF Resume Resume IMS DB2 CCTL DSNAPRH XCF XCF Subzero Controlling Agent When the CICS transaction issues a DB2 or IMS data request: 1. Subzero Common Code intercepts the request 2. Uses XCF to route the request to the Subzero Subsystem Server for that database 3. The Subzero Subsystem Server gets the data from DB2 or IMS DB 4. Uses XCF to send the data to the Subzero Controlling Agent 5. The Subzero Controlling Agent sends the data back to the transaction via the Subzero Common Code
- 21. Subzero transparency andfallback Utilizes IBM published facilities – Standard IBM CICS/DB2/IMS DB interfaces – Subsystems think they are communicating directly – All existing CICS, DB2 and IMS commands will respond as expected – Single-Phase or Two-phase commit protocols are preserved; data integrity is maintained by the requestor WLM classification and accounting – Information is propagated from the client address space to the Subzero Subsystem Server address space – Allows WLM performance monitoring to include these address spaces in its service policy management No application code changes If a local DB2 or IMS instance satisfies the CICS connection request, Subzero steps out of the way and allows processing as normal
- 22. Enabling Subzero Complete installationand product customization Define the Subzero configuration – Uses DBC and LGC to define targets (Remote Subsystem Access) – Subzero will support both Local and Remote Subsystem Access CICS – Add Subzero product libraries in CICS STEPLIB and DFHRPL – PLT Changes • Subzero code runs as first pass PLT program – DBC must be started before CICS – IMS and/or DB2 libraries required to support local connectivity Subzero Requirement – CICS 4.1 and later – DB2 10.1 and later – IMS 12.1 and later – z/OS 1.12 and later
- 23. MainView for DB2,MainView for IMS and MainView for CICS were enhanced to facilitate Subzero control and monitoring – New 3270 and MV Explorer views and hyperlinks – Use Subzero API to collect component data – Enhancements through PTFs Subzero Monitoring
- 24. Roadmap Subzero 2.0 –September 2015 – Installation Verification Program (IVP) • Available now as a 1.0 PTF – IMS TM to DB2 support • Beta May/June – MQ separation from DB2 for MQ shared queues – MQ separation from DB2 for MQ running DB2 stored procedures Subzero future plans – DB2 and IMS DB batch job support – Separation of MQ from CICS
- 25. BMC Subzero Significantly reduceMLC costs Add operational flexibility to critical workloads running on CICS with DB2/IMS DB • Removes the IBM requirement that subsystems must reside on same LPAR • No application changes Speed recovery time for DB2 and IMS subsystem failures Strengthen overall IT mainframe budget
- 26. Lowering IBM MLCCosts The BMC Software Investment • Foundation for understanding MLC • Quickly identify MLC cost components • Simulate options for MLC cost reduction Cost Analyzer for zEnterprise® • Reduce IMS batch CPU consumption up to 50% • Reduce IMS batch elapsed times up to 70% • No IMS application changes Application Accelerator for IMS • Cost optimization with soft capping • Intelligent capping minimizes SLA risks • Simulate mode for gradual implementation Intelligent Capping for zEnterprise® • Reduce CICS, DB2, and IMS MLC costs • Increased operational flexibility • No application changes Subsystem Optimizer for zEnterprise®
- 27. Thank You — Bring ITto Life.™ CAzE iCap AAI Subzero
- 28. © copyright 2015BMC Software, Inc.