Service Management on System z Blog
barbara kennedy 2700025GG7 email@example.com Tags:  ibmservicemanagementsyste... mainframe ztiv tivz 472 Visits
Welcome to the
barbara kennedy 2700025GG7 firstname.lastname@example.org Tags:  tivz omegamon service-mgmt ztiv zos ibmtivoli mainframe 1 Comment 1,038 Visits
Top 10 Ways to Participate in Pulse 2010
Pulse 2010 will be held February 21-24 in always exciting Las Vegas and feature the best of the best in Service Management. There will be announcements, presentations, demonstrations and receptions. Analysts and experts will address specialized topics for business leaders, technicians, and executives. Get smart, get certified and get connected. Plan to participate now. Call for papers and session contributors ends November 2.
barbara kennedy 2700025GG7 email@example.com Tags:  ibmtivoli mainframe tivz ibmservicemanagementsyste... omegamon ztiv zos 573 Visits
Do you have a topic to present? A best practice to share? A perspective for a panel?
Benefits of Speaking at Pulse 2010:
Ready to share your experience?
Important dates for submitting papers/proposals for Pulse 2010:
barbara kennedy 2700025GG7 firstname.lastname@example.org Tags:  mainframe service-mgmt ztiv tivz zos 1 Comment 882 Visits
Good news for all is that the “Call for Papers” for Pulse 2010 has been extended by popular demand. November 20th is the revised deadline so there is more time to finalize creative input. I spoke with Marcus Boone, product manager for Tivoli’s system z portfolio, regarding suggestions for Pulse participation. He is anxious to hear from those customers who can share real-world experiences on how an integrated approach to service management on System z is creating real benefits. Virtualization projects with savings, new Linux workload projects or best practices in the very complex world of ‘always available’ are good examples. Marcus believes Pulse 2010’s emphasis on alternative forms of customer participation, such as roundtables, panels and open discussions to support a topic will be both more interesting and more meaningful to all.
Please plan to join the conversation. Submit your proposal online at http://www.ibm.com/software/tivoli/pulse/.
Wayne Bucek 120000989Y email@example.com Tags:  mainframe servicemgmt ztiv 2 Comments 1,181 Visits
Hi. I am Wayne Bucek a 20-year veteran in the systems management arena. When I have to come off the bike trails, I am a Consulting IT Specialist for zTivoli solutions. My favorite part of the job is to assist customers with the selection, design, and implementation of IBM zTivoli products. I am IBM-certified in WebSphere MQ.
Prior to joining vendor community, I had a real job - 10 years' experience across the disciplines of z/OS systems programming, application programming, and performance management.
I hope to make this blog a place z techies can come to link their real world business problems to zTivoli solutions.
Many customers manage the performance of their MQ environments based on requirements from the application development community. These requirements are often as simple as monitoring the current depth of the queues used by the application. When the current queue depth of a queue exceeds the threshold specified for the application, an alert must be raised. This relatively straight forward process can become an administrative nightmare in an environment where thousands of queues need to be monitored with this level of granularity. In this case, an OMEGAMON XE for Messaging situation would be required to monitor each queue. This design results in a high cost of collection, along with a high cost of ownership, as the administrative burden of implementing this scheme is prohibitive.
A better way to approach the problem is to group queues into queue depth threshold brackets. For example, queues A, B, C; are all evaluated against a current depth threshold of 10 of more. Queues D, E, F are evaluated against the next higher threshold bracket, perhaps current depth greater than 50. Bracket thresholds are determined based on the current depth requirements specified by the application owners. As many brackets as needed can be defined.
The key to the solution lies in the assignment of a queue to a threshold bracket. Customers will seldom have a queue naming standard based on their queue depth monitoring needs. However, OMEGAMON XE for Messaging provides a creative solution to the problem. OMEGAMON is sensitive to the queue definitions description field. The description field, typically a comment, can be modified to indicate which queue depth threshold bracket the queue should be evaluated against. Then, a single OMEGAMON XE situation can be constructed, reflective of multiple (perhaps all) queue depth threshold brackets. This situation would use an 'OR' construct, essentially checking for combination of Current Depth < threshold AND description field == queue bracket threshold limit, across the multiple specified brackets.
Wayne Bucek 120000989Y firstname.lastname@example.org Tags:  mainframe servicemanagement ztiv 2 Comments 917 Visits
OMEGAMON XE for Messaging is a complete WMQ management solution. Many customers focus exclusively on the performance monitoring aspect of the product, which is the ability to monitor WebSphere Broker and WebSphere MQ, and disregard the WMQ configuration agent.
The configuration agent is a robust, feature rich, component of the solution. However, the features and associated benefits of the configuration component are distinctly different from those of the monitoring components. When discussing the WMQ Configuration agent, I like to begin by covering the business benefits it offers. The following items (IMHO) represent the business benefits of the WMQ Configuration agent.
* Centralized administration of WebSphere MQ objects
* Single GUI across platforms
* Eliminates configuration errors
* Assists in dealing with large numbers of objects
* Disaster recovery tool
The list of features offered by the WMQ Configuration agent are too lengthy to list here, but a full accounting can be found in the product documentation at:
Future blog entries will cover this material in more detail.
barbara kennedy 2700025GG7 email@example.com Tags:  servicemgmt cloud tivz mainframe 1,015 Visits
Recently I interviewed Joe Clabby of Clabby Analytics regarding the role of the mainframe for cloud computing. We invite your comments -
Q - Joe, cloud computing has been characterized in many ways, but is basically a new service consumption and delivery model inspired by consumer Internet services. Key components include on-demand self service, ubiquitous network access, location independent resource pooling and rapid elasticity. In recent weeks you have been advocating the mainframe for management of the cloud. Why?
A - Simple ─ a mainframe is a cloud-in-a-box.
Q- In your experience, have customers who have adopted service management from system z realized measurable ROI? Can you share any examples?
Q - Not every customer has a mainframe. At what point(s) should a business consider adopting the platform for service management?
IBM is a client of Clabby Analytics and has provided compensation to Clabby Analytics for participation in this interview.
Wayne Bucek 120000989Y firstname.lastname@example.org 429 Visits
OMEGAMON XE for Messaging on Z/OS provides comprehensive statistical information on application workloads using the MQI. When transaction response time degrades, it is helpful to isolate the delay to the offending subsystem. The Application Statistics feature facilitates problem identification, providing clocks and counts by MQI request type, for all monitored applications.
Details on the operation of this feature are found in the WebSphere MQ Monitoring Agent User's Guide. A white paper discussing Application Statistics best practices is available on the Tivoli Wiki.
Raymond Sun 060000ASTK email@example.com Tags:  ztiv service-management tivz ibmtivoli mainframe linux 2 Comments 1,058 Visits
As you consider moving workloads to Linux on System z, you will want to evaluate which workloads are the best fit. Ideally, data intensive or mixed workloads are best suited for System z whereas CPU intensive workloads may be better run on other platforms. On a recent webcast where I was co-presenting with Bill Reeder (IBM Linux Enterprise Servers), we discussed best workloads for Linux on System z which leverages the strengths of System z like WebSphere MQ, Domino, SAP. We also talked about good workloads for Linux on System z which run well on Linux on System z but can also run on other platforms. So, there are other factors (e.g. organizational politics) which must be evaluated in deciding the ideal platform for workloads.