As I mentioned before there seems to be two strategies about monitoring
in general and I have had this discussion with many z sys progs. There
is the group that says the fastest resolution is to wait for a failure to
happen and then start working on fixing the problem which is the
best way to use their skills. The latest discussion I had on this
was with a group of customers in Toronto last month. I was talking about
the idea of finding loopers running on the z and some new techniques
with the OMEGAMON XE on z/OS v4.20 release. Some creative use of monitoring
buckets to pick them off as early as possible which by doing
this could save MIPS which is saving money versus using
the cycles for something that is going to be cancelled eventually.
That generated a whole group discussion on what happens if you generate
some false positives meaning that there isn't a looping job and it is
better to let a failure happen then generate these false positives where
the staff would be working on a perceived problem and not the real thing.
Some were for being proactive and had actually seen results with the looper
situation and others were pretty steadfast in only working on failures. In
the discussion a bit about different IT organizations came up as there
are strict department areas of control between say a group focused on
performance versus a group focused on automation. Some have performance
groups only for z and a different performance group for distributed and networks
Other groups have a silo'd approach to their area of control
and things outside their domain are not in their control and hence, not our job.
That discussion also brought up the point that to tie automation
and performance for proactive management would span several departments
which may have other priorities.
In general, the attendees viewed it important to ensure that
the z platform is inclusive of an enterprise wide strategy for achieving
the business goals that are imposed on IT and they need to work
across the silos but there are only so many hours in the week.
I know many customers have established performance automation routines
using OMEGAMON products where if a problem is uncovered with situations
where a proactive recovery routine is started or notification to the IT
staff for them to take a specified action to prevent an outage or degradation
of the system to take place. Although OMEGAMON products can deploy the "eyes"
into the systems by not needing a message to be issued to kick off an event.
The sister products like NetView on z/OS and Systems Automation actually
perform the automated actions, but how in a silo'd group does this
get accomplished for the benefit of all?
Again they all had their different domains and areas of responsibility but
With the discussion it was interesting how people react. I have
already discussed how to integrate the different managing IT staff with
different domain responsibilities by getting them to share the same view
of the problem on a piece of glass at a console. Even then some of the
attendees see no value in this. Some viewed this as a loss of control of
being in charge of their domain. I still think this saves both time and
money and could be leveraged effectively based on defining a business process.
The next step would be to integrate the performance tooling to work as a
business process to be able to sense a problem, isolate the problem,
diagnose and then repair the problem as an integrated process.
Many companies are using business process modelers to streamline actions
and provide for a competitive advantage of how a line of business manager
can generate an exacting control based on business needs.
When you think about your IT business processes, Change, Configuration, Problem,
Performance, Availability, how integrated is the IT staff and the process
to resolve events about these processes whether they are on the z platform
or from distributed platforms.
The group in Toronto all identified areas where this would help
with their jobs, but they all said, how much time in the week can you do
your job and still have time left over to talk about an automated process. There
has got to be an easier way. I guess that will be the next discussion.
Mike E Goodman Ends with z
Mike Goodman 270001BMTD firstname.lastname@example.org Tags:  tivoli performance z/os proactive service omegamon management 466 Visits
Mike Goodman 270001BMTD email@example.com Tags:  z situations ism itm automation tivoli omegamon management smcz 632 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:  cics monitoring omegamon tivoli systems management e3270ui z/os 669 Visits
OMEGAMON v5.1 will be generally available on March 9th. Announced on Feb 7th, this
release is what I would call a customer guided development piece of work. As part
of the effort Tivoli is expanding the Early Access Program. The EAP is a way
for customers and system programmers to follow along and comment and improve how
they want the OMEGAMON tools to function and work. The 5.1 releases will follow
what we call problem solving scenarios. The purpose of the scenarios are to ensure
that we just don't add metrics without the thought of how they relate to problem
solving. A major change required by the customers was to stop just putting data
on a screen and format the data as information that is organized around how they
use the tools to analyze and correlate key performance indicators. In zOS it is
about moving from a plex view, to an lpar view, to an address space and organizing
the flow of information to help keep related kpi's associated with problems as
defined by the system programmers as they tell us what are the common problems or
information they need to quickly get to the root cause from the same green screen.
The new Early Access Program will involve all OMEGAMON products. With the new
integrated architecture, it makes sense for us to have only one customer program
where if you participate you could follow along and comment on Messaging, DB2, IMS,
Storage, Mainframe Networks as well as the next CICS and z/OS development work.
It helps both development and customers focus on how tools are being used today.
For example, a CICS SME told us that one major issue in there environment was that
a user would call and say their session was hung. The normal procedure was to then
get a large amount of data and start whittling it down with sorts, filters trying
to find the users session. The business as usual was for monitors to return 140
thousand rows of data, spiking a cpu, then reduce and reduce. They told us on
average this process took about 2 hours. Innovation rules on opportunities to
provide problem solving scenarios like this. Now, we have instituted a FIND
command. The end user can usually tell you his user id and by typing find and the
user id, the query brings back not only a significant lesser amount of data and
reduces CPU cycles, but also shows where the user is connected in about a minute. It is
so cool, that plans now are to leverage a FIND or locate in all the other
monitors. By using the EAP program, you can follow along with only one monitor
or multiples, there is no need to actually download code, the sessions last about
an hour, all recorded for playback. So, if your a system programmer and want to
have an impact on the next release, think of it as designing the tool you use
to solve problems you need to solve, then join the program. And, last, look
me up at Pulse or SHARE in Atlanta.
Join the EAP..
Steps to participate:
1. A completed nomination form should be completed and submitted.
For Customers and Business Partners, please use the following link
(you will need to login with your IBM Web ID):
Mike Goodman 270001BMTD email@example.com Tags:  management it tivoli systems performance z omegamon ism 680 Visits
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 Goodman 270001BMTD firstname.lastname@example.org Tags:  ism omegamon ibm performance z/os ims tivoli systems 688 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 email@example.com Tags:  green omegamon screen tivoli z portals 1 Comment 1,710 Visits
I was reminded by a recent customer call that only real sysprog's use
green screens. It reminded me of a very brilliant lady who worked with
my sons teachers and to paraphrase her quote, "If you only do what you know,
you only get what you have gotten." This whole discussion was about
leveraging a Portal for system programmers as a way to provide visibility
for operations, etc. I mentioned all the portals and GUIs being deployed
for folks to manage the heterogeneous environments to which I didn't make
much of an impact on the image of portal vs greenscreen. Of course, SHARE
is coming up, Pulse is coming up, System z Tech Universities where I
watch other sysprog's and customers demonstrate and leverage portals for
operations, LOBs, end to end management. Asking the basic question,to leverage and manage end to end solutions. In my case, I discussed
When have you folks been to a conference lately?
How do you know what other folks are doing or available
Integrated Performance Management where workload exists on multiple platforms
including the z. I think when you work so long in an environment and don't
get outside of it to smell the roses or in this case, listen and look at how
others attack problems by leveraging technologies, then you only do what you
only know and the world passes you by. Certainly, I hope sysprog's out there
in the world today can put equal value for management in both the green screen
for deep dive analysis on z platform resources and a portal for putting
non z info like zBX or linux on z or blades, datapower, end to end
transaction tracking and other not typical green screen info in a GUI where
it provides visibility across a plethora of IT resources.
For Tivoli z solutions here is the link to the System z Management
community group on Developerworks.
go get registered and get the latest and greatest tidbits and advice.
Mike Goodman 270001BMTD firstname.lastname@example.org Tags:  pump management omnibus z systems omegamon tivoli event zpump 731 Visits
I was discussing the need to centralize as one process the ability
have a focal point for an event management system. Many customers today
have a group that is managing distributed systems and a different group
that is managing the z platform. This is sometimes a issue that has been
promoted over time and the business ends up with two processes. In Tivoli
for centralized management of events, OMNIbus is the product customers
deploy for integration of both z and distributed event mananagement. In
December, Tivoli released the Event Pump on z/OS v4.2.1. This product
reads the syslog for messages that the IT group has registered
as important and changes them into an event and forwards it to OMNIbus.
This gives customers with Tivoli the ability to centralize all events to a
focal point. The Event Pump on z/OS in its new release has increased the
out of the box capability of handling messages as well as picking up new
message feeds. The Event Pump on z/OS gives customers the capability
of having out of the box value as the product is delivered with a best
practice of important messages already registered to be changed into
events and forwarded to OMNIbus. RMFIII, CICS TDQ, CPSM were recently added
to DB2, IMS, CICS, SA, OPS/MVS, TWS and new feeds are generally added about
every quarter. Many sys progs have perhaps built their own way of integrating
events, but the Event Pump on z/OS has a lot of benefits vs RYO. With
the new release, the zPump has the capability for handling messages with
the same message id by being able to use literals in message text to
distinguish differences. Also, there is the capability of adding
data to the messages as they are changed into events for Operations
management. Another nice item instead the RYO approach is that
in a plex environment, a down message saying something is
offline can be brought online by a message from a different system. The zPump
has awareness of the messages so the sys progs don't have to figure out all
the particulars of what system generates the clearing messages.
The other item here is that the Event Pump for z/OS also has toolkit that is
named a Data Source Customizer which gives the sys progs the ability to
add messages or create new messages that can be registered and monitored. So
a very easy way for sys progs to integrate z messages into a centralized
event management system is with the zPump. Of course, OMNIbus or NetCool
is required, but instead of trying to keep up with new messages, upgrades to
new releases, etc etc. A nice solution.
Mike Goodman 270001BMTD email@example.com Tags:  z management smcz tivoli omegamon systems tco itil 547 Visits
So my last discussion here on my blog was about conferences and which ones as
z focused folks that we attend. I was at zExpo in Berlin last week with about
400-450 other z oriented folks. A lot of interactions and networking going on
most of the week. I thought the conference was great. Many sessions were repeated
and that gave a lot of us who always fear that we will pick the wrong session to
go to when you have options to actually see both. The next big conference I guess
would be back to Boston and SHARE in August. At zExpo I spent time talking about
the concept of moving from systems management which for z folks is old hat, to
moving to service management. Seems simple, but talking with the folks in attendance
it was easy to see that many of us are still very focused on ensuring that the
technology that we are responsible for is still how we manage. So, if you are
responsible for the z/OS operating system, that is your focus. When you talk
Cloud computing, SaaS, other new service oriented focused solutions, the idea
of just managing the system or z applications kinda falls flat. A service being
offered in a Cloud could depend on more than one application, security, storage,
networks and all of those items need to be managed as a coordinated action by IT and
measured all together as the service. As z folks, it is understanding that your
SME skills are just part of the team that enables the business to deliver the
service that the clients are paying for. That is what I believe ITIL 3 is about as
we try to enable IT to move out of the silos and establish the service definition
that makes the business successful. I was surprised at the conference that many
of my conversations with the attendees were along the lines of, "yes, I understand
that but my group or dept have not been involved in any of these discussions." Now
that to me was pretty disturbing that the backend systems are generating all this
business value via transactions but when involving a service delivery organization
that the z folks are somewhat participating. It would be nice to see some presentations
from IT folks on how they get organized for service management and are being successful.
Anyway, this is a short thread on the concept of up lifting systems management to the
next level, service management which is what will deliver Cloud, reduce TCO, improve
ROI and create a leaner IT that works smarter and not harder. That is something
we can all rally around.
Mike Goodman 270001BMTD firstname.lastname@example.org 324 Visits
I wanted to give a shout out to an upcoming conference call for customers and
IBMrs alike. Joe Winterton is giving an update on 'January 28 -
Exploring your z10 and z/OS systems with OMEGAMON XE for z/OS. Joe is one
of the acknowledge experts on z/OS and is a speaker at SHARE as well as the
development manager of the OMEGAMON on z/OS product. The information can
be found at this url.
Hopefully you can make time to listen in on this call. I will be back to
discussing events, z management in the next update as I am getting
ready with presentations for Pulse in February in Las Vegas on February
21-24. If your going to be at Pulse feel free to ring me up. My contact information
is in my widget on this page.
I will be bringing updates from the presentations by the customers on
how they are using the products and leveraging the capabilites of the z platform
in their companies. It should be a diverse group of discussions and technology
discussions. Reading about products is sometimes a big yawn, but listening to
how customers have deployed and leverage the products for their business I think
generates some really good thought provoking discussions. So it should be good.
One other point I wanted to make is that with the release of OMEGAMON XE for
CICS on z/OS v4.20, the OMEGAMON family v4.20s are all generally available.
Big thing in the OMEGAMON for CICS v4.20 is that the OMEGAMON XE for CICS TG
is now part of that product, so customer upgrading to OMEGAMON XE for
CICS v4.20 will get OMEGAMON XE for CICS TG as part of the
OMEGAMON XE for CICS product.
Mike Goodman 270001BMTD email@example.com 434 Visits
Pulse has come to a close. As a z person, I was very pleased to hear discussions and see presentations
where the platform is being used to leverage both IT and business imperatives. Steve Mills did a greatfinish, a lot of good presentations that customers did on how they are being successful. For z folks,
job discussing how the zEnterprise is going to change the landscape. From the start to the
zEnterprise as a footprint and platform that can improve TTV, ROI and reduce infrastructure costs were
pretty cool. Lots of examples as customers are starting to look at how they could leverage the capabilities
in the not to distant future. I shared a presentation slot with Phil Murphy from Forrester where he presented
ideas on organizations and understanding how to reconcile business imperatives versus the basic IT budget
planning to support the business. A couple of other points that came across. The first one was that for
an integrated enterprise, more companies are using a GUI or the Tivoli Enterprise Portal as a bridge to
integrate staff and technology at an awareness level of what is happening event wise on the resources
they are monitoring. Another point here is that from the Tivoli management infrastructure, that z folks
are very aware of automation and how it is implemented and maintained. For automated situations which
are provided with both the Tivoli z products and distributed products, customers are strategically
integrating the automated situations and the automation staff into a single automation dept. They have
a group responsible for creating/maintaining, doing change management, requests for control as part of
the overall automation strategy including the automation tools like systems automation, NetView etc.
The difference is that SMEs for zOS performance, CICS performance etc, are responsible for working out
what thresholds, queues, workload monitoring, but they work with the automation team to have those autonomic
monitoring built, deployed and maintain. This will stop the work around deploying automated situations
where there are false positives happen and after some time, operations just doesn't think it is a valid error. By putting
a staff around just automation, all automation and making them responsible for its success, you take
the care and feeding away from the SME who is not focused on a service or business level success and
put it into the hands of a team who has the end to end responsibility for an automated service.
How are you organized around automation? does a single group own all situations, both distributed and
z? How are you planning to bridge distributed automation with z automation as a strategy before that
zBX shows up on the dock. It is going to show up, it is just a matter of time.
Mike Goodman 270001BMTD firstname.lastname@example.org Tags:  tivoli rfe ism management omegamon systems z 847 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 email@example.com Tags:  hypervisors netview z/vm omegamon management z cloud z/os systems zenterprise 573 Visits
A couple of items for those folks that follow my rambling. There is a conference call presentation
on May 26th on the new release of NetView 6.1. A lot of neat features and work has gone into the new
release including a new logging feature where as a sysprog, you can look and read the many logs from
a single screen. A lot of integration work was done between NetView and OMEGAMON XE for Mainframe Networks such
as launching a trace from MfN using NetView. As your shops move to zEnterprise and your looking for how
the performance is running on your internode or interensemble networks across your environment. There is
also a zSummit roadshow moving around the US. Next in Chicago on May 25th and Columbus on June 8th. A
excellent way to get yourself prepared for the new computing platform. I had a great discussion in
Vienna at the about getting virtualized. In the brave new world, the move up the management stack would
from resource management views of the day to day tasks to a new services or update services management
view. This is how customers are bridging across the current pillars of operation. Now it seems the lessons
of breaking down the pillars is again starting up with the decisions of using different vendors hypervisors.
The view of now using different vendors hypervisors would limit how you could move workload around in
your virtual data center. So reuse, cost of computing goals will be harder to do. A good case for z/VM
in this environment is still security, scale, cost, reduced power, reduced number of servers required, etc.
So in the new frontier or old computing model that we are calling Cloud, are the decisions the IT shop
is making enabling the move of workload across the elasticity of a virtual environment actually ensuring
that this will work or are you using several different vendors hypervisors based on legacy of the
hardware installed or resources and building a new bunch of silos where we again get focus on the technology
versus the services you are trying to provide.
Mike Goodman 270001BMTD firstname.lastname@example.org 305 Visits
The call for abstracts for Pulse for 2012 is about to close. This year I expect to see more z
input and papers. The Automated Operations Technical Conference and those associated
presentations will be part of the Pulse agenda. I know that for some sys prog's the choice is
between SHARE which is the week after and Pulse which is March 4-7. Always good to have choices.
I attended and presented at zSymposium earlier in Oct and have been traveling throughout
Europe discussing customers plans for 2012. It is about lock down period for many of
the companies and no major changes going on till January. There are a couple of beta programs
going on, OMEGAMON XE on z/OS and OMEGAMON XE for CICS on z/OS. If you have a sand box
where you could knoodle with the code and give us some feedback, well feel free to contact
me and we can figure out how to get that done. The other piece of news is that Gartner has
come out with the application performance monitoring review and it puts Tivoli in a
leadership position. APM is really the next step up from the basic monitoring which is
becoming a commodity throughout many customers environments. In particular it discusses
two characteristics of integrating monitoring both from a horizontal tracking of transactions
and a vertical deepdive for faster problem resolution focused on the end users experience.To have the ability when a domain is found to have a impacted response time issue, being
able to deep dive into that domain in context of the transaction to provide failure analysis.
It is how ITCAM for Transactions works with OMEGAMON XE to provide these capabilities. I will
say that all of this is demo'd and there are lots of meet the experts sessions if you choose
to attend Pulse. I know the team is working to make sure there is content that would be suitable
for the z sys programmers to attend and get value out of the session. Think AOTC.experience and use. Hope to see you there.
Sometimes it is hard to justifya technical conference in Vegas, but remember
the zSymposium has been there on and off forseveral years and this STG education
conference is well attended. I am working with several of the customers to discuss
the early adopter programs and theagile transparent development work going on from
Tivoli as a panel with q and a's on whetherit helps them guide development in providing
the correct building of the tools for a better
Mike Goodman 270001BMTD email@example.com Tags:  smc systems omegamon z tivoli pulse availability management performance 779 Visits
Hard to believe it is already October. Hope readers of this got at
least some vacation during the summer. Since my last post I have
been to SHARE, zExpo as well as many customer visits. At this time
the OMEGAMON family v 5.1 release now include Messaging, IMS and
Storage as well as CICS, zOS and DB2. The last of the releases,
Mainframe Networks, is about to come out the door. Many of the
companies are already in production and using the new enhanced
3270 user interface as well as the other features and functions of
the portfolio including zIIP enablement and the use of specialty
processors if they are available. I am amazed that the OEM vendors
claim that they use less MIPS because they leverage specialty processors
and leave out the fact that OMEGAMON does this also. It seems to be
that this is something they are the only vendor to provide when in fact,
that is not the case. Hopefully, when folks understand where you compare
apples to apples versus apples to starfish, OMEGAMON is not the villain
that some vendors make it out to be on MIPS usage. Most of these discussions
are what I would call a marketecture vs reality.
Meantime, on developerworks, I have placed some documentation. An updated
Parmgen reference upgrade guide, some e3270ui workspace reference layouts.
Kind of a cheat sheet to understand the layouts. Also, many of you
have taken advantage of the OMEGAMON open house events that have taken
place around the world.
Pulse is coming, March 3-6 and abstracts are being called for. We continue
to add z content to this event. This year the Automated Operations Technical
Conference will be joint located in the Pulse conference. Just like last year.
Also the Parmgen lab will be repeated.
Well, I will promise to update this a bit more regular than lately.
Here is the link to the System z Management team room on Developerworks.
go get registered and get the latest and greatest tidbits and advice.
Mike Goodman 270001BMTD firstname.lastname@example.org Tags:  green systems ibm omegamon tivoli screen performance management 643 Visits
Well, they say you can't teach an old dog new tricks. Things that have existed for years
and decades will simply continue to exist. Why do something new or change?
So I am a guy who has worked in IBM for 36 years, but has changed jobs and
positions every 5 years or so. I guess I have job hopped within the same business
and been luckier than most to be able to do it. The one thing that has been pretty
constant in all of this is that the z platform was here before I started with IBM and
will be here long after I leave IBM. I guess you can call it a survivor even though
there seems to be articles every year that are touting its impending doom. I think like
my job hopping, you pick up new skills, address new challenges and adapt to
keeping yourself valuable to the business. It would seem to me that the z has done
the same and continues to adapt and change, but keeps the same value proposal
that major business requires as it moves through time.
One of the interesting ideas that changing times is creating is a big stir for the z and all z
users. Is the green screen the only presentation service that is required or that
will ever be required for the z subject matter experts? This has created different
opinions from many of the businesses I talk with as well as operations folks,
tooling support folks and others in IT that are starting to see alternatives show
up on the doorstep, regardless of whether it is needed or not. As far as I have read,
a lot of the details or say the imperative of alternatives to green screens
would be that all the kids (I myself am far from a kid) or people entering the IT world
are from a gaming background or are so trained in web browsers and pop ups that
the only way to keep the business going is to change the old technologies to
adapt or adopt to make IT support and the z platform viable and to have a way to
bring new talent into the IT business.
In particular, the z stands out in this because of the vast green screens being
used today and the idea that with a greying workforce (that could be me), there
is a critical shortage of upcoming people who would find it appealing enough
to work on z systems or subsystems if it were just that plain old green screen.
That to me is pretty interesting as part of a product manager team with
Tivoli and OMEGAMON and and discussing System Management requirements
with customers because I think that down the road, there will be requirements
where both the green screen and the vast arrays of GUIs with web 2.0 and beyond
will have a pretty dramatic impact on the IT folks who support the z and z subsystems.
I think the idea of having a reach and range of information about how IT systems
are working or not working will create what I call a funnel system that works
in several ways.
A basic premise is that if you want to manage the business effectively and with
an eye on the TCO of all the running technologies deployed, you integrate an
end-to-end perspective, and ensure that any bump in the night generates an
event/alert and that gets sent to a focal point where someone or some automation
routine is running. This seems to be a standard operation within a mature systems
management IT shop. This data is filtered, reduced and hopefully has
a meaningful message when it gets to the end of the funnel and someone looks at it.
Since we are talking and end-to-end view and consolidation of this information....
Should it be a green screen? A MCS for the enterprise?
I think that the diverse information being received precludes that from ever becoming
a reality in IT. As companies staff help desks and customer service centers, it would
seem that graphics and Web GUIs are taking the predominant role with all sorts of
capabilies to sort, or display and relate impacts on the business.
In fact, this area keeps changing, it seems, every 6 months with new internet technologies
being introduced all the time. There are different use cases and personas using this
web technology that are the first line of awareness even if the trouble ticket is cut
automatically when something goes bump in the night. The event shows up at this
integrated web/portal based GUI orin some business several portals/GUIs where
the different personas might have a different IT process to work on. So, I think the case
of only having this in a green screen has passed in time.
Now the issue is if the bump in the night happened on the z or a z subsystem...haste
and speed to resolve are a priority because of the potential loss of $$. So if the bump
in the night is shown in a nice graphical web based portal, and we all know that web
response time is not what you call as dynamic as a green screen, it creates the dilemma
that IT people are discussing. Is there only one choice here or multiple?
Is it better to have a wide range of data available to view or is it better that we need a
quick reach into the z system and subsystems with speed?
Next up Funneling out..