iCan Blog Archive

One of the many systems management enhancements in the 7.2 release was the addition of message monitors and system monitors to the IBM Navigator for i GUI. This is the first step in making Management Central functions available in the Web console.

If you are on 7.1 or earlier, you already have these monitors with Management Central in the System i Navigator GUI. This blog highlights the major differences you’ll discover with the monitors on the 7.2 release.

You’ll find monitors as a new set of tasks in the left-frame navigation area:

<br /> <img alt=”” src=”/IBMSystemsMag/media/Grady-Booch-Audio-Files/09302014-DawnMayMonitors_1.JPG” style=”width: 326px; height: 350px;”

The biggest difference with the monitors on 7.2 is there’s no support for system groups; they only can be started on the system on which they are created. While Navigator was enhanced with groups in the 7.2 release, groups are currently used for just Compare and Update of PTFs (which I will write about at some point). Message monitors and system monitors in the 7.2 Navigator cannot (yet) be started on a group of systems.

Message Monitors are very similar to the message monitors in Management Central, with one significant exception – on 7.2 you must have the IBM Universal Manageability Enablement for i (<a href=”http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaq9/rzaq9lpp5770ume.htm” target=”_blank”>5770UME, V1R4</a>) product installed; this licensed program product is shipped with the operating system and should be installed by default on 7.2. If you don’t have this LPP installed, you’ll get an error when you try to start the message monitor. This product provides the underlying support for the message monitor implementation; from a user interface perspective, you should not see many differences.

System Monitors on 7.2 are similar to Management Central System Monitors on prior releases with regards to the kinds of performance metrics you can monitor as well as the user interface on how you create the monitors. However, the underlying implementation of system monitors on 7.2 is different than that of management central system monitors. Both implementations use Collection Services as the data source for the monitor metric data, but on 7.1 and earlier, Management Central obtained the metric data directly from the management collection object; on 7.2 the metric data is obtained from the Collection Services database files. This means that for system monitors on 7.2, you must have the Collection Services data go into the database files at each collection interval. This is the default setting, but it’s something that can be changed.

Another significant difference is how you view the monitor graphs; with 7.2, you use the Performance Data Investigator (PDI) to view the monitor data. You can launch directly to PDI from the monitor itself, as shown in the following image.

<img alt=”” src=”/IBMSystemsMag/media/Grady-Booch-Audio-Files/09302014-DawnMayMonitors_2.JPG” style=”width: 623px; height: 261px;”

In addition, PDI has a new Monitors content package where you can investigate monitor data.

<img alt=”” src=”/IBMSystemsMag/media/Grady-Booch-Audio-Files/09302014-DawnMayMonitors_3.JPG” style=”width: 517px; height: 304px;”

PDI currently does not have the ability to automatically refresh the data in the monitor graph, so you have to manually refresh the graph with the Refresh button that was added. But the really nice thing about using PDI as the interface for viewing monitor data is that you have the same user interface to view monitor data as well as more detailed Collection Services data.

Finally, the system monitors in 7.2 have slightly different metrics to select from; obsolete metrics regarding IOP utilization can no longer be monitored, and there are several new metrics you can chose to monitor, such as temporary storage utilization, spooled file creation rate, and shared processor pool utilization, among others.

I’ll write more about how the 7.2 system monitors work in a future blog, as there are many more interesting aspects to cover.

This blog post was originally published on IBMSystemsMag.com and is reproduced here by permission of IBM Systems Media.