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.

Cool Classic interface tricks

I've done quite a few posts over the past few weeks on the Tivoli Portal, and its unique capabilities. But, I don't want to keep the sole focus on the Tivoli Portal. Classic 3270 interface has some nice capabilities that you may not know about.

Classic interface is very customizable, built around the notions of major and minor commands, menus, etc. You can make custom screen spaces to target specific technical requirements, or to focus on a specific user or audience.

It's easy to customize Classic screen spaces, and you can do some very nice things with Classic. But, there are other interesting things you can do, as well. For example, did you know you can have the Classic interface execute a screen space based on such things as time of day, or if a specific Classic exception has been hit? Did you know that you can have one screen space execute, and then call and execute another screen space? Did you know about the ability of the Classic interface to execute screens, and then log the output?

I will do a series of posts that go into examples of how to use features, such as Timed Screen Facility (TSF), Automated Screen Facility (ASF), Auto-update, Exception Logging Facility, and other cool Classic techniques.

Availability alerts using situations

When creating an availability alert or creating a workspace focused on z/OS availability, it may be useful to create some alerts focused on the availability of key tasks. I showed and example earlier of how you can use the integration of System Automation (SA) with the TEP to create an intelligent task/resource availability alert based upon the logic encoded within SA.

What if you do not have SA? What are ways to create some task availability alerts? One easy starting point is to use OMEGAMON z/OS, and to create address space alerts using the situation support for the 'Missing' function. In the example I show, if any of the tasks in the list are detected by the situation to be missing, an alert will fire.

This is an offshoot of the Key Task light from the OMEGAMON MVS CUA interface. The advantage of using the TEP and situations are two-fold. First, you can add additional logic in a situation that you cannot have in the basic Key Task light in CUA. The second thing is that you can make situations time of day sensitive a couple ways. One is to add time sensitivity into the situation logic. Another way is to manage the situations using policies to start/stop them.

Using policies to start and stop situations based upon the needs of the installation is a powerful, and easy to use technique. You can manage the alert, make it time sensitive, and not have to code all the logic into the situation. Just let the policy manage it.

Using custom queries to analyze situation distributions

If you want an easy way to understand what situations are distributed and where they are distributed (without having to get into the situation editor for each one), this technique may prove useful.
You can create 2 custom queries that go against the TEMS. The first is:

SELECT DELTASTAT, UNIQUE(SITNAME) FROM O4SRV.ISITSTSH WHERE DELTASTAT = 'S';

This will show a list of what situations are distributed.

The second queries is:

SELECT NODEL, OBJNAME FROM O4SRV.TOBJACCL WHERE OBJNAME = $SITNAME$;

This will work to show where a situation is distributed (passing a variable SITNAME).

You can go from the first query on the first workspace to the second using a link and passing SITNAME as the variable for the drill down. Above is an example of what you would get.

This is a good exercise in custom queries and using workspace links. Here is a URL that describes the set up in more detail:

http://www-01.ibm.com/support/docview.wss?uid=swg21454974&myns=swgtiv&mynp=OCSSZ8F3&mync=R

Online ITM problem solving tools

Here's a web page that consolidates a list of useful support links, and some online assist and help functions for support and documentation for IBM Tivoli Monitoring (ITM).

Here's the link:

http://www-01.ibm.com/support/docview.wss?uid=swg21303361&myns=swgtiv&mynp=OCSSZ8F3&mynp=OCSSLSFT&mynp=OCSSLSDR&mync=R

For the "well dressed" mainframe fan

If you are a System z mainframe fan, here's a chance to let the whole world know about it. An amusing array of mainframe t-shirts. Here's a link for more info:

http://www.mainframezone.com/store

Information on IBM Support

Here is a link to an interesting web page that provides a lot of information on using IBM Support and items like the Support Portal and My Notification. There are links on this page for instructional videos and a software support handbook. This is a good starting point for navigating the various facilities of IBM support.

http://www-01.ibm.com/support/docview.wss?uid=swg21439079&myns=swgtiv&mynp=OCSSBNJ7&mynp=OCSSNFET&mynp=OCSSLKT6&mynp=OCSSSHRK&mynp=OCSSPLFC&mynp=OCSSZ8F3&mynp=OCSSRM2X&mynp=OCSS2GNX&mynp=OCSSVJJU&mynp=OCSSGSPN&mynp=OCSSGSG7&mynp=OCSSTFWV&mynp=OCSSPREK&mync=R