Health Check for Your z/OS Systems Should Include Coupling Facility Activity

 

As another New Year begins, most of us are open to some new practices that improve life both at home and at work. Probably the most common challenge we face personally in the new year is our weight. I put on my share, and it’s never easy to get back on track! Reducing calories on the intake side is a good start, however, coupled with a regular regimen of exercise, diet has a multiplying effect. Suddenly, the effects of exercise go far beyond the goal that drove the change in activity, and it pervades other areas.

It’s no different in IT.

(Here’s a reference of the exercise multiplier and an example article showing the many other exercise benefits.)

Whether you have just completed your year-end budgets or not, it won’t be long before cost pressures, time pressures and all the other pressures of new projects squeeze many of us into ‘surviving the next day’ versus moving along a progressive path of improvement. I’ve been there.

Digging Your Way Out of the Holiday Workload Avalanche

Some of us may feel like Ground Hog Day is really the week after the New Year; which typically begins with consecutive day-long ‘war room’ events to sort out incidents from:

  • the avalanche of changes that broke loose after holiday freezes,
  • the normal jump in workload demand as a new year begins,
  • the new demand from the customers that sales signed up on New Year’s Eve to meet their year-end goals.

How can you make progress in that situation? After you dig out from the initial avalanche, my suggestion is to start with something known and something relatively easy to change. The progress of small deliberate steps can become a positive and pervasive ongoing practice.

This may be as simple as evaluating your infrastructure configuration with a health check. For most z/OS environments, this is non-trivial; but starting with something that is easily overlooked and not too difficult to remedy can pave the way for more progress.

Checking your Coupling Facility Activity

With the hundreds of other configuration options to consider on your z/OS systems, a suitable ongoing ‘health check’ gives you a proactive stance and positions you to begin addressing the cost and complexity of your major mainframe applications and changing business demands. One area worth a quick look is checking your Coupling Facility activity for:

  • long synchronous CF requests, and
  • conversion of synchronous requests to asynchronous requests.

What’s too long? Best practices indicate that you should be seriously investigating anything greater than 60 microseconds. Why? Depending on the frequency of those requests, it could be costing you some valuable processing power, not to mention added latency for the affected workloads. I don’t know about you, but cutting down CPU a percentage point or two in the first month sounds like a great way to start the New Year!

Improving the Health of your IT Systems

While this may seem like an old issue that you don’t have to worry about, our technical services have recently reviewed some system data with >200 microsecond latency!

Share presentations (copyrighted W&W material) and other sources (IBM) are readily available to assist you with some minor changes that can be made with new features and options in your z/OS environment that could overcome the items above.

Investing a little time driving a small win will help you start the new year on the right foot, and provides a nice way to win allies and continue improvements to the health of your IT systems. IntelliMagic Vision provides an automated way to conduct daily health checks for your coupling facilities and the rest of your z/OS infrastructure. Check out this white paper on Reporting on Coupling Facility Health and Performance and find out how you can get on the road to true z/OS fitness this year!

 

Reporting on Coupling Facility for Health and Performance

Leave a Reply