Modern mainframe workloads are becoming more complex, as digital priorities drive new requirements for mainframe applications. To address and prevent issues, mainframe operators must have the information they need in a format that the rest of the war room team can understand and act upon.
Given the complexity of modern enterprise IT environments, serious problems inevitably crop up from time to time—problems with no clear fix, likely because it is difficult to determine where the problem is occurring and what its root cause may be.
When such problems arise, it’s time for a situation room – commonly known as the “war room.”
The war room is a crisis management technique that brings together representatives from across the IT landscape to hash out everything they know about the problem at hand. Working together, the theory goes, will lead to a better understanding of the cause of the problem and thus the necessary fix.
The participants in this exercise come from all corners of the IT organization, and in many cases, are people who don’t work together on a day-to-day basis. Each individual brings their own strengths and insights to the table—ideally for better resolution of the problem at hand.
Furthermore, if an issue gets to the war room stage, the problem likely has the attention of executives who will be on the call as well looking over the shoulder of the war room team, increasing the urgency and pressure to solve the problem quickly.
Sometimes, however, communication issues get in the way, as war room participants often speak different jargon. After all, this ad hoc team might consist of network operations, front-end leadership, security operations, cloud management, systems and virtualization operations, mainframe operations, and more.
Of all these various professionals, one stands out as being the one most likely to have communication challenges in a war room environment: the mainframe professional.
Click here to read the entire article.
