BMC Subsystem Optimizer for zenterprise Reducing Monthly License Charges

Transcription

1 BMC Subsystem Optimizer for zenterprise Reducing Monthly License Charges David Schipper Lead Product Manager 11 March 2015

2 Agenda Sub-capacity Pricing and Monthly License Charges (MLC) BMC Subsystem Optimizer for zenterprize () Use cases Technical details Roadmap

3 Survey Says IT Cost Reduction / Optimization 70% Application Availibility Application Modernization Data Privacy Business / IT Alignment 52% 48% 47% 44% Data Recovery Cloud Implementation Mobility Big Data 27% 26% 34% 34% Outsourcing 16% Other 3% Source: BMC Software 2014 Mainframe Survey

4 What Drives Mainframe Costs? Peak Processing MIPS People 25% Hardware 20% IBM OTC 5% Other 10% MLC Software - z/os,, IMS,, etc 30% ISV 10% What the business wants: Reduce MLC monthly charges Reduce MIPS required Improve performance and availability in the process Peak 4HRA MSUs

5 Sub-capacity pricing IBM MLC software 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 4-Hour Rolling Average IMS DB Other z/os % of Expense % of MSU Peak $85/MSU MSUs $46,070 24% 29% IMS $125/MSU MSUs $67,750 35% $75/MSU MSUs $40,650 21% $72/MSU MSUs $39,024 20% 26% Other 0% 17% Total $193,494

7 Sub-capacity pricing LPAR Aggregation Hour Rolling Average Hour Rolling Average IMS DB Other z/os IMS DB Other z/os % of MLC Expense % of MSU Peak $85/MSU MSUs $78,455 24% 31% IMS $125/MSU MSUs $115,375 35% $75/MSU MSUs $69,225 21% $72/MSU MSUs $66,456 20% 28% Other $0 0% 13% Total $329,511

8 Need to think differently

9 BMC Subsystem Optimizer for zenterprize () The Why IBM requires that,, and/or IMS DB run on the same LPAR if a transaction access 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, IMS, and Enhanced system redundancy and recovery options Further workload balancing options

10 BMC basics LPAR1 LPAR2 or IMS DB 1. application SQL or DL/I calls are intercepted by 2. routes the data access request to the appropriate DBMS 3. /IMS DB processes the data request and returns the requested data 4. routes the result set back to the initiating application

11 Sample Use Cases

12 use case / data sharing LPAR 1 LPAR 2 Without 284 MSU LPAR MSU 121 MSU 117 MSU 224 MSU LPAR MSU 96 MSU 127 MSU LPAR LPAR LPAR LPAR Aggregate monthly peak R $72/MSU MSUs $75/MSU MSUs $72/MSU MSUs $110,736 Monthly MLC fee $336,822 LPAR MSU LPAR MSU LPAR 3 LPAR MSU With LPAR LPAR LPAR LPAR Add 3% for overhead 46 Aggregate monthly peak R MSU MSU Annual savings $443, MSU $72/MSU MSUs $75/MSU MSUs $72/MSU MSUs $114,022 Monthly MLC fee $299,887-11%

13 use case LPAR isolation LPAR 1 62 MSU LPAR MSU 343 MSU 250 MSU LPAR 2 53 MSU LPAR 4 63 MSU 267 MSU 360 MSU Without LPAR LPAR LPAR LPAR Aggregate monthly peak R $72/MSU $75/MSU $72/MSU $110,736 Monthly MLC fee $336,822 LPAR 1 62 MSU 53 MSU Annual savings $1,300,416 LPAR 3 LPAR MSU 63 MSU LPAR MUS 267 MSU 250 MSU 360 MSU With LPAR LPAR LPAR LPAR Add 3% for overhead 46 Aggregate monthly peak R $72/MSU MSUs $75/MSU MSUs $72/MSU MSUs $22,896 Monthly MLC fee $228,454-32%

14 use case isolating IMS LPAR 1 LPAR 3 62 MSU 262 MSU 140 MSU IMS 81 MSU 250 MSU LPAR 2 LPAR 4 LPAR 2 63 MSU IMS 64 MSU 53 MSU 203 MSU 360 MSU Without LPAR 1 - //IMS 405 LPAR 2 - //IMS 320 LPAR 3 - / 390 LPAR 4 - / 423 Aggregate monthly peak R $72/MSU MSUs $75/MSU MSUs $72/MSU MSUs $110,736 $132/MSU MSUs $95,700 Monthly MLC fee $432,522 LPAR 1 LPAR 3 62 MSU 262 MSU LPAR 5 IMS MSU LPAR 4 LPAR 2 LPAR 2 53 MSU 203 MSU With LPAR 1 - / 324 LPAR 2 - / 256 LPAR 3 - / 390 LPAR 4 - / 423 LPAR 5 - IMS 145 Add 3% for overhead 46 Aggregate monthly peak R MSU 250 MSU Annual savings $1,134, MSU 360 MSU $72/MSU MSUs $75/MSU MSUs $72/MSU MSUs $100,296 $132/MSU MSUs $19,140 Monthly MLC fee $337,969-22%

15 Database redundancy example SUBZERO SUBZERO SUBZERO SUBZERO LPAR 1 LPAR 3 xdb DB LPAR 2 LPAR 4 DB DB Without or IMS on LPAR 1 must be restarted before on LPAR 1 can process transactions LPAR 1 xdb LPAR 2 DB With LPAR 3 DB LPAR 4 DB can automatically redirect or IMS calls from on LPAR 1 to or IMS on LPAR 2

16 Technical Details

17 Architecture and Processing Flow LPAR1 LPAR2 XCF Controlling Agent DFSPRRC0 (IMS) Common Code Resume XCF Subsystem Server CCTL IMS Controlling Agent DSNAPRH () Common Code Resume XCF XCF Subsystem Server DSNAPRH When the transaction issues a or IMS data request: 1. Common Code intercepts the request 2. Uses XCF to route the request to the Subsystem Server for that database 3. The Subsystem Server gets the data from or IMS DB 4. Uses XCF to send the data to the Controlling Agent 5. The Controlling Agent sends the data back to the transaction via the Common Code

18 transparency and fallback Utilizes IBM published facilities Standard IBM //IMS DB interfaces Subsystems think they are communicating directly All existing, 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 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 or IMS instance satisfies the connection request, steps out of the way and allows processing as normal

19 Enabling Complete installation and product customization Define the configuration Uses DBC and LGC to define targets (Remote Subsystem Access) will support both Local and Remote Subsystem Access Add product libraries in STEPLIB and DFHRPL PLT Changes code runs as first pass PLT program DBC must be started before IMS and/or libraries required to support local connectivity Requirement 4.1 and later 10.1 and later IMS 12.1 and later z/os 1.12 and later

20 Monitoring MainView for, MainView for IMS and MainView for were enhanced to facilitate control and monitoring New 3270 and MV Explorer views and hyperlinks Use API to collect component data Enhancements through PTFs

21 Roadmap 2.0 September 2015 Installation Verification Program (IVP) Available now as a 1.0 PTF IMS TM to support Beta May/June MQ separation from for MQ shared queues MQ separation from for MQ running stored procedures future plans and IMS DB batch job support Separation of MQ from

22 BMC Significantly reduce MLC costs Add operational flexibility to critical workloads running on with /IMS DB Removes the IBM requirement that subsystems must reside on same LPAR No application changes Speed recovery time for and IMS subsystem failures Strengthen overall IT mainframe budget

23 Lowering IBM MLC Costs The BMC Software Investment Cost Analyzer for zenterprise Foundation for understanding MLC Quickly identify MLC cost components Simulate options for MLC cost reduction Application Accelerator for IMS Reduce IMS batch CPU consumption up to 50% Reduce IMS batch elapsed times up to 70% No IMS application changes Intelligent Capping for zenterprise Cost optimization with soft capping Intelligent capping minimizes SLA risks Simulate mode for gradual implementation Subsystem Optimizer for zenterprise Reduce,, and IMS MLC costs Increased operational flexibility No application changes

24 CAzE AAI icap Thank You Bring IT to Life.

25 copyright 2014 BMC Software, Inc.