Tuesday, July 29, 2014

What to look for with V5.30

When you are looking at V5.30 there are several things in general that you will find as a common theme in the new release. 

The first is to look at many enhancements in the area of enhanced 3270 user interface (e3270ui).  e3270ui is getting more robust and is finally becoming industrial strength.  Some of the things you will find in the new e3270ui include:
     Improved diagnostics and deployment flexibility
     Expanded history and near term history capability
     Additional trace/analysis support
     More robust cross tool navigation using what is called embedded data

History is going to be a big area of enhancement in V5.30.  Look for quite a few new capabilities in the area of history. 

Wednesday, July 23, 2014

New OMEGAMON Versions announced - V5.30!

A new version of OMEGAMON is always a festive occasion for this blogger, and the announcement of OMEGAMON V5.30 is an important event.  V5.30 includes a lot of new functionality and capability.  It includes major enhancements to e3270 user interface, and to the core OMEGAMON monitoring capabilities.  I plan to be blogging extensively about what's new in V5.30 in the coming months. 

The planned GA date for V5.30 is September 5th.  The following are the new OMEGAMON releases:
Note that Messaging is V7.3.  That is because Messaging version numbers will correlate to the corresponding MQseries versions.

There are also bundling options for OMEGAMON.  There is the  OMEGAMON Performance Management Suite for z/OS V5.3.  This suite consists of the following:

There is also a  OMEGAMON for z/OS Management Suite that includes the following:

If you want more information on the announcement, here is a link to the announcement letter:

Tuesday, July 1, 2014

How to use OMEGAMON IMS to monitor the response time of an individual transaction

I recently had a customer ask me about how to use OMEGAMON IMS to monitor the response time of an individual transaction.  The RTA function of OMEGAMON IMS is based upon the notion of RTA groups.  These groups are typically defined using the KOIGBLxx macro that specifies the group and startup options for RTA and for Bottlneck Analysis.  The groups may be transaction based, scheduling class based, program based, or based on combinations of trans/classes/programs.  Since you have a limited number of RTA groups, most groups represent multiple  trans/classes/programs.

But, if you want to isolate just one specific transaction there are three ways to do it.

1-  Add the transaction to its own RTA group in KOIGBLxx.

2-  Use the OMEGAMON Application Trace Facility.  This will provide very detailed response time data.

3-  You can add the transaction dynamically to its own RTA group.  This is easy enough to do, but keep in mind the transaction will only be there until OMEGAMON is recycled.

To add the transaction dynamically, do the following:
      Logon to the classic interface
      Go to the RTA menu
      Select E for controls and stop RTA
      Select F for options
      Use the SETG command to alter the group
      As in the example below     aSETG01 tran=addpart          will add the addpart tran to group 1