How to use zEC12 self-sensing system (Zaware) to expand the system management of Zos

IBM mainframe system from its birth to now has more than more than 40 years of history, its powerful handling capabilities and its safe, reliable and continuous service offerings make it a core system for finance, aviation, insurance, and government, but with the continuous updating of the ZOS system and the expanding function, how to ensure the healthy operation of the system, Discovering potential system risks in a timely manner poses a huge challenge to the IT department of the Enterprise.

· How to keep up with the changing technology

· How to keep up with the changes in the product

· How to ensure that all products are properly configured

· How to discover the anomalies in the system in the daily system maintenance

August 28, 2012, IBM ZEC12 officially released, ZEC12 provides Zaware (System z Advanced Workload analysis Reporter) self-awareness to determine whether the system is having problems by analyzing its internal information in real time , the problem of timely warning and classification, and through a graphical view of the display, so as to further diagnose the cause of system anomalies.

IBM's zaware is able to analyze a large number of log message data, Zaware use Zos operlog message to build a zos system normal operation of the model, the Zaware analysis engine by observing the current behavior of the system and the system's previous behavior model to compare, Using pattern recognition techniques to identify system anomalies, IBM Zaware is able to tell the system administrator that the current behavior has changed to alert the system of possible risks before a real problem occurs.

Zaware provides system administrators with a new view of system behavior that can help us answer similar questions as follows:

· Are there any exception messages on the system?

· When did these exception messages start?

· Are these exception message activities repeated?

· Have these exception messages never been present before?

· Do these exception messages appear along with problems with the system?

· Are the messages of these exceptions confined to one system or on multiple systems?

Compared with the existing management system, Zaware does not need to specify which system events need to be monitored, but to determine the possible problems of the system through its own analysis. For example, IBM TIVOLI NET view for ZOS is often used to monitor system-known exceptions, which are often based on specific messages related to a particular problem, and the actions required are clear. If new messages are not defined to an automated processing system, they are ignored, causing potentially important information to be not monitored. Since these messages have never been seen in the system before, they are well suited to be processed by Zaware systems as exception messages.

1. IBM Zaware Architecture

The zaware consists of two parts, the zaware application and the monitored client system (called "monitored clients" in the zaware term).

As shown in figure: 1-01

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/OS/other/