Today Tivoli announced the OMEGAMON v5.1 CICS and z/OS products. I have been working with
customers and development for over 16 months on concepts, design and a usability. Much like
monitors that have grown up over time, Customers have asked, we need this metric, we need
that metric and the randomness of how subject matter experts perceived where this should be
viewed was almost always up to the individual developer. In deciding to change the course
and structure of the OMEGAMON portfolio, we decided we needed to talk with the system
programmers that used our tools to solve performance problems. Talk about folks that had
a lot of concerns to discuss. It wasn't about being able to view data splashes of huge
rows of data, it was about being innovative and how to organize metrics into information.
In some cases, the discussion was that we need to pull 90 thousand rows of data, then we
filter and sort all the while eating MIPS to find a single user who was hung or a single
transaction. That is the way it was done in the past, so thinking about what problem
they were trying to solve, a new find command. So don't return huge amounts of data,
simply return what I am trying to find. Most users can remember their user id. Even the
help desk folks could use this ability to free sessions and users . It was discussions
in early adopter programs and reviews with outside in design and interviews
with the SMEs that use our tools that generated what is the basis for the 5.1 releases.
The refresh of the portfolio was a little overdue and while some might think that enhancing
a green screen is a thing of the past, when you look at resource monitors across the
different technologies whether open systems or z, updates are always appreciated. There
is up and coming work for more early adopters programs and designs for this brand and
we will continue to enhance and deliver the changes required for SMEs for today's problems.
Here is an opportunity for system programmers responsible for solving today's performance problems on today's systems to
work with development to help design a tool that solves what they need to accomplish. Over
100 pieces of feedback went into these releases. We reviewed every month with the customers
who recommend changes in the design, metrics, use cases. One customers said he needed to
be able to work with web services. Agile means that bubbled to the top on the priority list
and was delivered in this CICS 5.1 release. I encourage others that as we update the
other branded OMEGAMONs and even start work on the next phase of CICS and z/OS that you
participate. Make sure that Tivoli is working to deliver tools that you find effective and
will solve today's performance problems. It is somewhat easy to add metrics, but innovation is using KPI data
and changing it to information to streamline how you solve problems and that is an important
part of the discussion that are ongoing with our agile development work. Most of today's
monitors were built awhile ago. Some are older than the young system programmer using them to
try and solve problems. Leveraging your knowledge and being innovative is a better path. While
looking at the past, we can make effective changes to revise and change the design the tools
you require for the job of the future. SME designed tools for SMEs that Tivoli builds and delivers. Neat.
If your at Pulse or SHARE, there are demos and presentations available and look me up. I will
be at both.
Mike E Goodman Ends with z
with Tags: ism X
Mike Goodman 270001BMTD firstname.lastname@example.org Tags:  management it tivoli performance systems z omegamon ism 816 Visits
Mike Goodman 270001BMTD email@example.com Tags:  omegamon ism ibm performance ims z/os tivoli systems 834 Visits
For our IMS folks.
OMEGAMON XE for IMS v420 IF3 just was made generally availablebased on processing all 10 messages.
and is focused on two areas: Improved granularity for
application metrics and usability enhancements to Application Trace.
OMEGAMON collected application metrics previously based on an application
schedule. That is, if an application was scheduled and processed 10 messages
before terminating the application metrics displayed were cumulative
IF3 has modified this and now displays application metrics based on unit of recovery (UOR).
In this fashion, runaway applications are easier to spot. In addition twenty-five new metrics
have been added to the OMEGAMON 3270 and TEP views. Some of these include new IMS
application calls (ICAL), external subsystem calls, elapsed times for intent conflicts,
pool space, and application scheduling as well as VSAM/OSAM I/O counts.
OMEGAMON XE for IMS v420 greatly enhanced the application trace capabilities. OMEGAMON XE
for IMS v420 IF2 added CPU and elapsted times for DL/I, DB2, and MQSeries calls. We've
enhanced these capabilities in IF3 by making them a bit easier to use. An application trace
repository has been added which retains all application trace requests. These requests,
once activated, will remain active across OMEGAMON starts if so desired. The management of
application traces is easier with an updated management interface.
This updated interface allows more trace filtering options as well as the ability to
add, delete and clone trace requests. In addition, the interface allows viewing by trace
request saving screen switching. The trace filtering interface has also been greatly enhanced.
One can specify multiple transactions, programs, abend codes, scheduling classes, among others.
New to filtering is the ability to filter by region type and elapsed and/or CPU time, either
total or by DL/I, DB2, or MQSeries call type,
The largest enhancement to application trace in IF3 is the exception journal. One can setup
an exception trace specifying service level commitments in total application elapsed time,
abend conditions, elapsed time by call time (DL/I, DB2, and/or MQSeries), and total CPU time
for the application or by call type. This is an especially useful feature for higher volume
shops where 99.9% of the applications run within the defined service level commitment times.
For those problem transaction instances, application trace will capture the trace data and save
this off in a new exception repository. This should make finding mis-behaving transaction
quicker to locate.
The best thing about this IF3 is that it had a beta with several customers, and the input on how
it should work, act and function was part of the agile process of development and reviewed monthly
with the customers requesting these functions which enabled them to retire another vendors
Mike Goodman 270001BMTD firstname.lastname@example.org Tags:  xe tivoli performance z omegamon ism system zenterprise tuning 777 Visits
So for those folks going to zSymposium in Vienna, please look me up as I will be there covering a topic
entitled "the new Virtualized Data Center". It seems as IT organizations move to use virtualization to
save costs, floor space all those benefits, some groups run on their own so instead of having a virtualized
platform, they end up creating even more silo's with in the IT groups. A lot of choices out there for
hypervisors, OS support, etc. A lot of good data on why zVM and linux on z is the most cost effective if
your IT shop has z/VM. Another thing for our OMEGAMON XE users is that we have been working on a
performance tuning document. I always chuckle when I listen to all the hype about a vendors claim
about how they use less MIPS then a Tivoli solution. The concern that I see is that the
depth and breadth of what is monitored is in the eye of the system programmers. When you actually get
down to getting the research or comparable apple to apple monitoring, much of it is the same, one
monitor might be less on z/OS, but use more with monitoring CICS. The approach seems to be to discuss
one monitor where it might be true, but then use that to justify all the monitors. There is a point
where in most cases, a full suite of performance monitors for the zOS systems and subsystems including
z/VM and Linux are not available from most vendors like they are with OMEGAMON. For this reason, systems that were installed
5 years ago or even last year, still need to be tuned as z platforms change. The field technical support
folks who travel and work with customers to help reduce MIPS consumption by doing health checks on
the production level z using the OMEGAMON portfolio and giving tuning recommendations
have help put together a best practices tuning book. The pdf is located on developer works at this url
System Hygiene is important so this document will help as it gives you tips and hints on how to reduce
MIPS usage. A must read for system programmers. I know it will help.
Mike Goodman 270001BMTD email@example.com Tags:  z situations ism itm automation tivoli omegamon management smcz 709 Visits
2011 and if you look back 6 months and you look forward from here 6 months, I think everyone
can see that there is a churn in technology happening that impacts business as usual. The new
CIO Business Priorities are out which were surveyed in 2010 and number one with a bullet for
business priorities is to increase enterprise growth. The number one technology priority is
Cloud computing. Both complement each other. From a staff point, it is indeed the new vision
of delivering managed services that will enable this to happen. There are several customers
I have talked with now that have found from an operations perspective, that combining both
distributed skills with mainframe skills within the same services group is starting to payoff.
A simple example can looked at using the Tivoli Enterprise Portal. Now before you dismiss this
because it is not a green screen and to slow, let me describe how the Portal can be leveraged.
When your looking at workload across different platforms which is the concept of zEnterprise, you
need to take into account, zOS and perhaps CICS,DB2. Since this is a fit for purpose system, you
may have a composite part of an application or database running on Power in a blade or Linux on x.
It could even involve some App servers running on Linux on z. There are certainly different sets
of skills that exist in IT today to provide support and management of those resources. Recently I
have seen some Automation teams now crossing the pillar boundaries by using situations, automated
tasks and the Tivoli Portal. A single team now is responsible via change control requests to
build out automation using situations provided by the Tivoli Monitoring solution. It is a combination
of staff but are responsible for building situations, documentation of them, providing actions that are
automated, ensuring that those actions are secure and support of this work. They have started to
combine CPU% from the different OS's in a single workspace with drill down capability to easily
identify within a managed workload using the system of systems, which one of the operating systems
is struggling with the workload. An at a glance view. They also have provided reflex automation
in a simple form that can take action to resolve some of these struggling CPUs. So they manage the
automation as a discipline but it includes the ITM infrastructure capabilities that provide a lot
of the function to find problems before a system or workload blows up. The technology is in place
and now it needs to be leveraged in that end to end composite view based on combining a bunch
of resources that are being managed into a single focused operation or service that supports the
business. I thought, a bright idea to combine distributed skills and zOS skills within the IT dept
to provide a base automation service to reduce MTTR, improve customer service versus two different
groups each dedicated to the existing pillars. What shape are you in?
Mike Goodman 270001BMTD firstname.lastname@example.org Tags:  cloud omegamon systems tivoli z management ism z/os 855 Visits
As the year winds down, probably the last conference of the year was CMG in Orlando. Even in
December I think the attraction is that it is in a warm place, however for those attending, it was
quite chilly so no warm breezes. I presented and discussed using the z platform as a key for cloud.
Simply put, because of the characteristics of the z platform to jump start cloud projects, it has some basic
principles that help it as an enabler. When introducing or trying to roll out a cloud project there
are some discussion points or obstacles that need to be understood. For example, I discussed what
would be required just to provide a web service which would be a key access for all customers because
of the use of the internet. This would be a basic infrastructure delivery. You would need to ensure
24 hour availability of, IP, HTTP, DDHCP, DDNS, just to put out the shingle. Then there is security,
spinning out some storage, usage and billing, etc. etc. This all needs to be done prior to even
advertizing the services available via the cloud. So why the z? First obstacle would be security and
with the z, you get a multi-tenant design point with EAL 5 certification. Supports Virtualization,
a share all approach to systems resources to create the scalability required to reduce costs and deliver
standardized services. Provides availability measured in years, 24 x 7 x 365 with zero data loss recovery.
It is efficient when you look at the energy and power required, up to 80% reduction in costs versus using
the same computing power in a distributed environment. Finally, it is scale, the ability to handle
massive demand of users and data. When interviewed, CxO's point to the importance of cloud for their
enterprise. It could be a public, private or hybrid, but they all point out it is a way to reduce
costs and deliver services for their consumers. It was interesting that at CMG, the attendees that
sat through this session all thought that their IT departments need to be working on their cloud
strategy and for the infrastructure, the z folks had a better grasp of how to leverage what you have
versus buying more IT technology. More about this and managing a zEnterprise in my next update
Mike Goodman 270001BMTD email@example.com Tags:  tivoli rfe ism management omegamon systems z 1,010 Visits
Several changes for customers of Tivoli and especially the OMEGAMON products have taken place. One
change that took affect on Nov 1 was a change in the way Marketing enhancement requests are going to
take place in the future. In the old process, if an marketing request was required, it would take
the level 2 or 3 person or an IBM rep to open the request and provide customers with the MR number and
perhaps they would get feedback on its progress. Many times it would seem to customers that these
requests went into some DB from which no information ever was returned. In truth, the database being
used had never been "scrubbed" and for me, I had enhancement requests when I took the job of product
manager over 5 years old. The times they are a changing which is good for everyone. The Tivoli portfolio
is moving to a new process for customers.
The Tivoli Request for Enhancement on developerworks is now the way the requests will be handled.
To read more on this, go to http://www-01.ibm.com/support/docview.wss?uid=swg21449404
Customers will be able to enter directly their requests but will require that they use their customer number,
password, etc. The advantage of this for all parties is that you will be able to see other RFE requests so
that if another customer has a requirement that you feel would also benefit your business, you can add
your name to that request and follow along. Most of the RFE information describing what the request is
can be read by everyone. From Tivoli, we will have a better opportunity to ask for more details and not
have to have several email trails trying to fully understand the request. Certain areas of the request
will remain private, such as the business case for the requirement and how it would benefit your company.
So now it will shed more light on the process, the requests outstanding, work going on and it will be
able to provide for you when the requests come available as this is the front end system now of an
agile process where these requirements can be driven right into a release plan. Rational has been using
this for several years so I think all OMEGAMON customers will like this fresh approach. If you have an
old marketing request, there is no reason in the world why you couldn't open up the same request using the
new process. It is pilot and expect perhaps a few glitches along the way, but overall I think it is will
prove out best for the products and customers. It will be easier to prioritize work if 50 customers want
a particular enhancement request and would see benefits vs just 1.
I also just returned from a meeting of the Swiss Tivoli User Group where they had a dedicated z track for the
customers. In fact, I know the NYC TUG has at least a meeting each year where the z is focused on. If
your a member of a TUG and think that your group could benefit from a z track, let the Tivoli Rep know
and we would be glad to support the meeting. They can always contact me directly. So a bit of vacation
for me over the Thanksgiving holiday as I try to use up the days I have acquired. Enjoy yours.
Mike Goodman 270001BMTD firstname.lastname@example.org Tags:  tivoli ism omegamon mfn management systems z netview 696 Visits
Well a bit of vacation and catching up. A couple of things to let you all know
about. The OMEGAMON documentation has come up with some improvements about providing
an easier way to use the all the documentation that is provided. The OMEGAMON XE Integrated
Information Center is a redesigned way to access data. Instead of looking within one book about
something, when searching it covers the many books that are delivered with the product. Hopefully
this will make it easier to find what your looking for. It is worth going and looking
at the quick start section which provides some guidance on how to use the changes that have been
added. It has been vastly improved to help install and configure the products. So, recommend you all
check it out. .
This week is zExpo in Boston where it is a bit grey and rainy, much different then the SHARE week,
however I would say, great attendance with a lot of focus on zEnterprise. In discussions with the
attendees a lot of zOS background folks but not many z Networking folks. For the zEnterprise and
the new network connectivity through the OSAs, I would like to point out that for the customer
network and new connections, that OMEGAMON XE for Mainframe Networks has support for these
connections and performance monitoring and folks that are considering using and attaching the
blade extensions would benefit by understanding or monitoring these networks proactively versus
trying to debug with pings, etc when a performance degradation appears. Is it the network?
a constraint with the lpar or blades gets a bit more crucial when your managing by workload and
fit for purpose Providing the visibility into the OSA CHPID types as an example you can have a
connection from app server to CICS, knowing its on internal network and would set higher
expectations for throughput and faster response time so you might set lower threshold on
those connections with a situation to trigger an event sooner and then notify both the network
management folks as well as the folks in charge of the zHMC admin to debug what is going on
in virtual servers and internal network. A lot of customers today work on just making sure the
connections are available, but in the future, besides the connections, performance will be a key
kpi to monitor.
Mike Goodman 270001BMTD email@example.com Tags:  automation zenterprise ism netview tivoli management systems omegamon z/os 667 Visits
For those of you that are subscribed or those that haven't, the monthly electronic magazine zAdvisor is out.
You can catch up at http://www-01.ibm.com/software/tivoli/systemz-advisor/ If you haven't subscribed, always
good things to review such as Rocky's corner for some performance tips. I was at SHARE earlier this month and
have been digesting information about the new zEnterprise. The good thing for those getting 196 machines is that
from what I can figure out, the Tivoli software your using today, will work just like it does today. Some new
things like the optimizer blades will be managed by OMEGAMON XE for DB2, etc as new functions are being exploited
for the fit for purpose workloads that the machine is designed for. For those folks that have added zOSMF to
the z, the OMEGAMON development team has added a technote and it should be posted shortly on the zOSMF website of
how to add a link for OMEGAMON from the performance links displayed on zOSMF. Some very cool discussions are
now going on as to how organizations will look at managing events, performance, operation views as either
different systems or as a system of systems. I have heard all types of discussions on this. Some are saying
that for the time being, we will manage it as components, yet they are also saying it will help them
step up and start managing based on service delivery. I think that the new frontier will be as service
delivery. Looking at the zEnterprise as something like a local machine, but then as a plex or group
of plexes or as a group of ensembles, managing as individual technologies will have to be coordinated across
a workload view of the fit for purpose workloads and applications. Changing something in a blade and not coordinating with
the rest of the ensemble could have a different impact if you don't understand the services being provided by
that piece of the systems of system technology. I believe it may get IT staff and strategy acting as one
component aligned with the business as it gets adopted. For those that say the z and systems management will
never change, it is what it is, then some new thinking is in line. As I get new info, I will post in my blog
some of the things that I am finding out about approaches and a pragmatic view of what you can expect. This
was just the general announcement #1, GA1 info, GA2 it sounds like is being updated and getting ready to
put on the truck. Next blog will cover some more details on the GA1 and the ISM approach