Do you hear that thunder? It’s the rolling tsunami of data requests coming to hit your mainframe this holiday shopping season. So, what will you do about it?
More business activity is always a good thing. But is your mainframe environment prepared for the wave of transactions that come into IBM® DB2®, IMS®, CICS®, MQ®, and other software? After all, availability is the key. But since the mainframe is so solid in this regard, you really need to be concerned about the spikes that yield a higher 4-hour rolling average (4HRA); that’s what drives your monthly license charge (MLC) costs.
Are you ready to manage your MLC costs for the big bang this holiday season? If you’re not sure, then take a look at ways to report, model, and proactively change your MLC software peaks. If you see an average 10% spike in activity as a result of holiday shopping, you might need a cost analyzer solution to know what workloads are driving MLC costs the most. After all, the only way to dodge a big spike in your MLC bill in January is to manage it in December.
Analyzing and modeling changes to your environment this month can lead to a much more manageable bill next month. For example, you might find that your workload capping efforts need to change as a result of the large volume of retail transactions. Maybe you can lower the caps for development or test environment workloads to provide more LPAR capacity in production? Or, maybe you can move a CICS or DB2 subsystem to another LPAR to better handle the increased workload? Subsystem optimization is the new “low-hanging fruit” for many mainframe shops these days. If you haven’t taken a look at it yet, you should.
Bottom line? Be prepared. Be tough. And be thoughtful about your holiday shopping customers. They don’t intend to create havoc in your mainframe environment—all they want is that new scarf or tablet.
All of us at BMC wish you the very best this holiday season! Onward and upward in 2016.
These postings are my own and do not necessarily represent BMC's position, strategies, or opinion.
See an error or have a suggestion? Please let us know by emailing email@example.com.