Aloha

Usually I try to post at least a couple items a week, even when I'm out on vacation. However, last week I was on vacation on the Big Island of Hawaii (near Kona), and what can I say? Here's a picture of where I held office hours last week.

I will be at the Share conference in Anaheim this week. I will be doing a series of presentations on monitoring and performance management, and attending sessions. I'm sure I will come up with quite a few nuggets of relevant information for the blog, so please stay tuned.

OMEGAMON XE For DB2 PE And Extended Insight

I've posted several times on new features in OMEGAMON XE for DB2 V5.10. But, I think that's for good reason, there is quite a bit of new feature/function contained within this new release.

Probably one of the most interesting new features added to OMEGAMON XE For DB2 PE (important note - this is relevant for PE only, it's not in PM) is a feature called Extended Insight. Extended Insight provides something that many users ask for often; getting an analysis of DB2 distributed queries that will break out the host time versus the network time. Extended Insight helps to answer a key question: is the problem on the host and the SQL query, or is the problem in the network?

The nice thing about Extended Insight is it can be referenced interactively within the Tivoli Enterprise Portal. When you are in a thread view you can drill down and get the relevant Extended Insight performance stats. In the screen shot I show here, you can see an example of the navigation. Another interesting thing about Extended Insight is it allows OMEGAMON DB2 to provide information that integrates nicely with ITCAM displays, and provides drill down detail of SQL level activity within ITCAM.

Again, please note that Extended Insight is only available with OMEGAMON XE For DB2 Performance Expert (PE), and is not in OMEGAMON For DB2 PM. So if you are a PM customer and want the feature, you may need to upgrade to PE. If in doubt, contact your IBM rep. I'm sure they will be happy to help you out.

Some recent and upcoming events of interest

Here are a few Tivoli z webcast events you might find of interest.

Tivoli for zEnterprise – Why integrated service management matters

Join us for this complimentary webcast and learn how Tivoli products can help you prepare for a better way of integrating service management under the new IBM zEnterprise “system of systems” and manage your data center as one. The speaker is Fillmore Bowen.

Here's a link to register:

http://www-01.ibm.com/software/sw-events/webcast/U074717Q21914I24.html

zSecure V1.12 helps consolidate security management

Learn about the new capabilities in Security zSecure suite V1.12 that enhance mainframe security on the consolidated zEnterprise platform.

Here's a link to register:

http://www-01.ibm.com/software/os/systemz/webcast/jan20/index.html?S_TACT=110GU00M&S_CMP=twr

Better manage IT costs with Tivoli Asset and Financial Management for zEnterprise

Learn how Tivoli Asset and Financial Management for zEnterprise can help IT organizations more responsibly manage their entire asset lifecycles, optimize software spending and improve audit-readiness. The speaker is Sig Puchaz.

Here's the link:

http://www-01.ibm.com/software/sw-events/webcast/G509526H80465Q34.html

All these events are free, and you can download them after the fact even though the live event may have already occurred.

More on OMEGAMON DB2 V5.10

There's a lot of new stuff in OMEGAMON XE For DB2 V5.10. Another interesting nugget is Near Term History support for zIIP processors. This can be useful because collecting Near Term History data is one of the more costly functions of OMEGAMON DB2.

The cost of Near Term History collection in OMEGAMON can vary. It has the potential to be costly primarily because it has the potential to collect and store a considerable amount of data. In some shops it may be as much as millions of records of information per day.

What V5.10 provides is support for zIIP processor utilization by the tasks that write Near term History. The OMEGAMON DB2 zIIP support requires no special configuration options for the zIIP processor, and requires no special configuration or setup in WLM. Essentially what happens is, if a zIIP is available, OMEGAMON DB2 has the option of using, if appropriate.

zIIP support is a good way to offload some of the cost of DB2 historical data collection.

New capabilities in OMEGAMON DB2 V510

–OMEGAMON DB2 V5.10 is a robust new release. You should be interested in V5.10, especially if you are looking at going to DB2 for z/OS Version 10.

DB2 Version 10 offers quite a few new monitoring and metric capabilities. DB2 10 improves the support for monitoring and managing both static and dynamic SQL. A unique statement execution identifier (that I mentioned in a prior post) is introduced. Statement type and statement execution identifier are externalized that can be used to correlate statement execution on the server with the client application.

ØDB2 V10 provides updated IFCIDs related to SQL execution, and new Static SQL Statement Cache trace information (flag IFCID 400, comparable to IFCID 318 for dynamic SQL).

Here is an example of the kind of information you can now get in OMEGAMOn DB2 V5.10. Note that the information looks similar to what you could get before for dynamic SQL, but now we can get similar information for Static SQL. Look closely at the example, and you will see what I mean.

New stuff in OMEGAMON XE For DB2 V5.10

A new version of OMEGAMON is always an exciting event (for me anyways). The newest release of OMEGAMON DB2, V5.10, is no different. OMEGAMON DB2 V5.10 was made generally available last year to coincide with the release of DB2 Version 10. One of the things that V5.10 does well is exploit many of the new instrumentation features of Version 10 of DB2 on z/OS.

DB2 Version 10, like most new DB2 versions, provides more traces, more trace granularity and detail, and more collection/analysis options. This includes new trace IFCIDs, and more information added to existing IFCIDs. Some of the most interesting stuff revolves the notion of a statement ID. Statement ID is a unique counter used to identify a statement, and its usage, across a DB2 system. It allows for more granularity of performance information at the statement level.

OMEGAMON DB2 V5.10 provides support for statement ID information in several ways, including both the Tivoli Portal and Classic 3270 interface. This information can be shown for both dynamic as well as for static SQL calls. It looks like very useful information, and I plan to do some additional posts on this, and in general on OMEGAMON DB2 V5.10.

New video on creating Dashboards using the Tivoli Portal

I've made my first foray into the world of Youtube. I created a video that discusses and then shows an interactive example of how you can build an integrated management and monitoring Dashboard using OMEGAMON and the Tivoli Enterprise Portal. What I did was I created an example that shows how you can pull together information from multiple monitoring agents (z/OS, CICS, DB2), and place that information on a single display.

I have plans to create other relevant videos as we go along. I think that videos can be a great way to show customization and usage scenarios.

I've added an area for links on the right for my videos. There is also a link to the Dashboard video below:

http://www.youtube.com/watch?v=Vs6Yhv1p4zg

IBM's mainframe-blade hybrid to do Windows

Here's a link to an interesting article in the UK press that talks about what is happening with the z196 zEnterprise mainframe. The focus of the article is on the zBX technology, and what IBM is doing to support AIX, Linux, and Windows in this environment. It's an interesting read from a 3rd party. Here's the link:

http://www.theregister.co.uk/2011/01/12/ibm_zenterprise_zbx_update/

An even cooler SOAP example

So far I've shown examples of how you can use the SOAP client to issue SOAP requests into the ITM infrastructure and the results of those requests. But, there is quite a bit more you can do with the SOAP interface. For example, you can issue a SOAP request from the 'Action' tab in the situation editor. In other words, when a situation is true, OMEGAMON can automatically execute a SOAP request.

Here I show an example of how this is done. When my EW_DB2_Test situation is true it will issue the following command (note - the XML file needs to be in the -hilev-\CMS\html directory):

soap:CT_Execute,filename=test.xml

In the example I show that when EW_DB2_Test is true it will execute an XML file, and within that XML file it will issue the CT_Activate method, and it will work similar to the example on my earlier CT_Activate post.

Once you know how to set this up, it's easy and works quite well.

Another SOAP example - CT_Activate

Here's another interesting example of what you can do with the SOAP interface to ITM. The CT_Activate method allows you to activate a situation. In the example I show how you can activate a situation called EW_Demo_Sit.

In the SOAP IE client I select the CT_Activate method. In the payload field I enter the XML detail for the method (the hub, the name of the situation, etc.). Once I click 'Make SOAP Request' I then see EW_Demo_Sit being activated in the Tivoli Portal (see the example).

The CT_Activate method is a potentially useful way to start situations, when required. There is a corresponding CT_Deactivate method to use for stopping situations. Potential uses for this technique could include starting/stopping situations to manage alerts that are only required for certain time of day/day of week scenarios. This would be an alternative to using policies to manage the start up and shut down of situations. It works well, and it's convenient and easy.

SOAP example - The CT_GET method

IBM provides some useful SOAP methods with ITM monitoring Web services. The provided methods allow you to dynamically query information and control the ITM monitoring environment.

Let's start with a straightforward example where we are going to query some monitoring information using the CT_GET method. The CT_GET method enables you to receive a group of XML objects or individual XML objects from any ITM monitoring agent. You can use this to obtain real time data from the ITM infrastructure.

ITM also provides a SOAP client to issue the SOAP requests. The client can be either a command line utility (not supported on z/OS though) or executed through Internet Explorer. To start the client in IE you would type in a URL, such as in the following example:

http://localhost:1920///cms/soap/kshhsoap.htm

Once you get the client screen back (as I show in the example), you can select a method (such as CT_GET), and pass the additional needed parameters (such as the hub, and the information you want to get).

In the example, we are requesting information from the NT_System table from the Windows OS monitoring agent. On the right of the screen we see the information fields coming back from the agent.

Once you understand it, the SOAP interface is straight forward, and has some useful capabilities. Note that this same SOAP interface is being exploited by such IBM tools as System Automation to interface with ITM monitoring.

I will show some additional examples in subsequent posts.

New link for SOAP

On the right under Useful Links I added a link to a nice document "Using IBM Tivoli Monitoring V6.1 SOAP Services". This document is a nice tutorial on XML and using SOAP in IBM Tivoli Monitoring.

Getting Started using Tivoli Monitoring Web Services

To get started using Tivoli Monitoring Web Services you first need to configure the Tivoli Monitoring infrastructure to enable Web Services (SOAP) support. Don't assume that this option has been enabled by default.

In the example I have shown, here we see how to enable the ITM infrastructure for SOAP in a Windows environment. From the Manage Tivoli Services window, right click on the Tivoli Enterprise Monitoring Server (TEMS) entry, and then select the 'Advanced' option followed by the 'Configure Soap Server Hub' option from the pop up menus in Windows. You will then get a pop up window where you can enter the information on the SOAP configuration. Here you will enter information such as the Hub name, location, and IP port number. Note such things as the Alias name, you will need that for the IBM provided methods that I will demonstrate on later posts.

Once you enter the required information, be aware that Manage Tivoli Services will want to re-cycle the TEMS, so do this at a time where that is acceptable.

Using Tivoli Monitoring Web Services

The Web Services support that is included as part of the IBM Tivoli Monitoring (ITM) infrastructure, is a useful, but commonly overlooked component of the tool. Certain add on components, such as ITMSUPER, that I've talked about earlier use Web Services support. But, there is quite a bit more you can do with the Web Services capability.

IBM provides out of the box quite a few SOAP methods with IBM Tivoli Monitoring Web services. These methods allow you to dynamically query and control IBM Tivoli Monitoring
environments. Using IBM’s SOAP methods, you can:
- Stop or start policies and situations
- Forward trapped messages to Universal Message console
- Retrieve attribute data that you can display in charts or reports
- Open and close events
- Make real-time requests for monitoring agent data

The SOAP support can be employed as part of situation and policy support. You can also retrieve data and store it in the Tivoli Data Warehouse (TDW).

There are some supplied commands and tools you can use to test web services calls, and to get a better understading of what you can do with ITM monitoring and Web Services. I will next do a series of posts that cover Web Services, and how to set up and use them.

Upcoming System z Technology Summits

Want to learn more about System z and zEnterprise? IBM is putting on a series of System z Technology summits. There will be in-depth sessions on zEnterprise, DB2, CICS, application development, and data center operations/management. Learn more about what's happening with z/OS V1.12, the new zEnterprise, DB2 V10, CICS and much more.

The event will happen at multiple locations:
Toronto, ON -- January 27, 2011
Dallas, TX -- February 8, 2011
San Francisco, CA -- February 10, 2011
Washington, DC -- February 15, 2011
Atlanta, GA -- February 17 2011
New York City -- March 8, 2011
Costa Mesa, CA -- March 15, 2011

It's looks like a very nice in-depth event, and to sign up for event here's the URL:

ibm.com/software/systemz/summit

Interested in Cloud computing and System z?

If you are interested in Cloud computing and System z, here is a webcast you may find interesting.

You can attend this complimentary webcast to learn the value of automating your service environment on System z. Analyst Joe Clabby, of Clabby Analytics, will discuss the importance of service management automation, and why it is a key requirement for virtualization and Cloud computing. You’ll come away with a good understanding of what an integrated service management strategy should be, and the requirements to be able to integrate business processes across the enterprise and consolidate complex workloads into highly available automated solutions using IBM’s Tivoli System Automation products on System z.

The event is January 13th, 2011 at 11 AM Eastern time. Here is a link to sign up:

http://www.ibm.com/software/os/systemz/webcast/jan13/index.html?S_TACT=110GU00M&S_CMP=5x5

Learn about zSecure in a free webcast

The Security zSecure suite provides cost-effective security administration, improves service by detecting threats, and reduces risk with automated audit and compliance reporting. On January 20th, 2011 IBM Tivoli will offer a free webcast to talk about the benefits of zSecure.

The webcast will focus on the new capabilities in Security zSecure suite V1.12 that enhance mainframe security on the consolidated zEnterprise platform. With simplified user administration, consistent security policy enforcement, improved security management, and automated audit event analysis and compliance reporting, zSecure can help you establish your mainframe as an enterprise security hub from which to manage distributed and consolidated security.

Register now for this webcast by logging onto ibm.com/software/systemz/webcast/jan20

Timed screen facility (TSF)

Timed screen facility (TSF) is a useful tool that's part of the Classic interface. TSF allows you to have the Classic interface execute a screen space at a specified time.

There are certain commands you need to know in order to use TSF. First, you can issue .TSF00 to list what timers (if any) are currently specified (see the example). You need to enble TSF via the .TSFON command. Next you need to enable Automatic update mode (using the .AUPON command). It's important to remember that for the timers to work, you need to have an active OMEGAMON session running in auto update mode.

To set the timer, you need to enter a timer and command in the time slot, such as .TSF01 for timer number 1. You enter a time and the screen space name, as I show in the example. Once this is done, you let the session run in auto-update, and then when the timer is hit, the screen space will execute (as I show at the bottom of the example).

TSF is handy because you can execute any Classic screen space based on time of day or day of week. You can have OMEGAMON execute a screen, or set of screens at off hours, and have the screen execute a LOG command to log and spool out the output of the commands. This is very handy and very convenient.

More useful Classic interface commands

We've covered the notions of major and minor commands, and I've shown you some short cuts on how to figure out what commands are available. The next step is to learn a few of the edit commands. You will want to know how to edit and save screen spaces because in many scenarios, if you are using the automated screen functions I've mentioned earlier, you will do this with screens you've crafted and built to suit your own technical needs.

To edit screens without having the commands execute you can use what is called definition mode. To get into definition mode it's /DEF ON (as I show in the example). To get out of definition mode it's /DEF OFF. You can enter your major and minor commands, as we've discussed before.

Once you have the commands you need in the screen space, you can save the screen space by using the command /SAVE screen. This will save the screen. If you are updating a screen that's already created, then use /REP screen to replace the screen (as I show in the example). To invoke the screen manually you can type the screen name in the command line (again as I show in the example).

Some other useful edit commands:

.. - type .. and then hit enter to clear out whatever is after .. on the panel

.d - to delete a line

.d 2 - to delete 2 lines

.i - to insert a line

.i 2 - to insert 2 lines

> - use this in column 1 to indicate a comment line

.rc - repeat command - this will wrap around the commands if needed

Try them out and try making some of your own Classic screen spaces.

Now that we've covered the basiscs, I will nest go in to how to invoke and automate using Classic screen spaces (including ones you've customized).

Useful Classic interface commands

When looking at using the Classic interface, it's useful to know the essentials of the Classic interface command structure. That starts with the notion of Major and minor commands.

All Classic product provided screen spaces are composed of these Major and minor commands. In the example, on the top portion of the screen shot, we see the Major command, ALLJ (for all jobs), and three minor commands, cpu, dprt, and ecsa. Think of it as the minor commands provide detail for the corresponding Major command. Also, notice that the Major commands are in ALL CAPS. The minor commands are all in lower case.

Not familiar with all the commands? You can break down and read the manuals. But, you can also use some classic commands to list the Major commands. For example, you can do H.MJC to list the Major commands, and provide a one line help for each. I show an example of this in the screen shot.

Don't know all the minor commands for a Major? No problem, just execute .EXM underneath a given Major command, and it will execute the minor commands for a given Major (as I show in the example).

Knowing how to get the commands is a great starting point for what we will be discussing next.