Welcome to the System z Management Blog, where you can read the perspectives from System z experts. This Blog provides insights into the System z solution, as well as technical details about specific IBM products.
Thanks for your attendance of our on-going open Q&A calls (focus topics covered to-date: PARMGEN and OMEGAMON enhanced 3270UI).
For our next call, Michael Crump (OMEGAMON enhanced 3270UI Architect) , will conduct an informal webcast on OMEGAMON enhanced 3270UI/Tivoli OMEGAMON Manager and answer your questions live on:
Session#1 * : 7/24/2013 (Wednesday) @ 11 a.m. PT / 1 p.m. CT / 2... [More]
What’s New in OMEGAMON XE for IMS v510 IBM® Tivoli® OMEGAMON® XE for IMS® v5.10 provides the following key enhancements and benefits: Self-Describing Agents (SDA) reduces the total cost of ownership and improves time to value by eliminating manual installation of application data on ITM servers (TEMS and TEPS) as well as eliminating monitoring outages due to recycling these servers when agents are updated by maintenance. With SDA, the proper level of application data is automatically propagated and installed on all ITM server components... [More]
Hi all TDSz users, If you have not already done so, be sure to check out the new Tivoli Decision Support for z/OS wiki at the following address: http://www.ibm.com/developerworks/wikis/display/tivoli/Tivoli+Decision+Support+for+zOS On here the TDSz developers will be keeping you up to date with any changes to the product, such as performance fixes, enhancements, new product tolerations and our integration with TCR (Tivoli Common Reporting). You can also find links to all our TDSz product documentation. If there is any specific... [More]
The IBM support people do a great job updating the Tivoli APAR notification page, which contains a list of some open or recently closed APARs that might impact you. Review the APAR record to determine if there is an interim fix or fix pack you need to apply. The Tivoli APAR notification page was last updated on January 3, 2012. Here are some APARs for OMEGAMON XE for IMS on z/OS: OA37615 LOOP AND HIGH CPU IN XE AGENT AFTER ACCESSING FAST PATH DATA Status: CLOSED 11 Oct 2011 Reported release: V420 ... [More]
The previously published Part 1 of this series in April was on the evolution of the CICS transaction server’s serviceability process and enhancements by Bill Bulfin and Ed Addison.
See Part 1 , titled CICS
Serviceability: An Ever-Evolving Process.
second part of the two-part series on the evolution of the CICS transaction
server’s serviceability process and enhancements is available here: Part 2: CICS Serviceability: Past, Present and Future
Hi Community please have a look to the following documents where the benefits of this feature are illustrated ! Do you need to condition the start of a job to a specific return code of a predecessor job? Would you like to shorten your workload execution time by conditioning the start of a job to a specific step return code without waiting the whole job execution? Conditional logic feature is what can help you to realize these scenarios. The feature is well described in the TWS for z/OS Managing the Workload manual (there is a dedicated... [More]
When you are making global entry changes (KC2GLBxx) and you want these changes to be picked up, a simple OMEG RECYCLE will suffice. You do not have to recycle your CICS region or recyle the classic started task or even perform a OMEG SHUT, OMEG REMOVE or OMEG INIT for that matter. The only time you need to do anything other than a OMEG RECYCLE is if the name of your GLOBAL (KC2GLBxx) has changed. Then you need to update the DD card in the CICS region. In this case, however, you do need to recycle the CICS region. Note: It is very important... [More]
Check out this first part, of a two part series, on the evolution of the CICS transaction server’s serviceability process and enhancements by Bill Bulfin and Ed Addison. Bill Bulfin has provided Level 2 worldwide remote technical support for CICS and the CICS tools portfolio of products, while Ed Addison has had a Level 2 career supporting VSAM and CICS. Through the years, serviceability, as it relates to CICS, has been primarily concerned with reducing the time and effort required to identify and solve a problem by CICS customers and IBM... [More]
For all of you IBM Tivoli OMEGAMON XE for IMS z/OS v.4.2.0 users, please consider applying Interim Feature 3 (IF3), which is now available. IF3 received great reviews from our early customer feedback. It includes a number of enhancements, especially for the Application Trace Facility (ATF). With IF3, we've improved the usability of ATF making it easier to identify and analyze poor performing transactions that can impact CPU utilization and service level agreements; traces are automatically activated at OMEGAMON startup saving you time; trace... [More]
Hi, all, on April 9th the new product IBM Automation Control for z/OS was announced. This product has enhanced the Tivoli System Automation family with a product focused on helping smaller zEnterprise customers. The IBM Automation Control for z/OS (IACz) product is targeted at single System z customers looking to move from manual scripting to policy based automation. IBM Automation Control for z/OS provides: Goal-oriented and policy-based design reduces the need for user scripts Start, stop, monitor and recover z/OS applications and... [More]
Mainframe computers play a central role in the daily operations of many of the
world's largest corporations, and batch processing is a fundamental part of the
workloads that run on the mainframe. Do you want a book that specifically addresses batch processing in detail? Click the following link: Batch Modernization on z/OS
Hello, on the link below there is a list of important APARs for Tivoli System Automation for z/OS with a short description/explanation. https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=5e65990a-9690-42e2-93b1-c2267be7620c#fullpageWidgetId=Waa62f018a05a_4ca4_b612_49ffee80398e&file=f51f0841-5031-4197-8da4-34b20cdcdeee
Just a reminder that OMEGAMON XE for zOS (4.2.0 and 5.1.0) will use RMF to collect metrics like Coupling Facility, XCF and Locking. This is a way to lower the OMEGAMON collection cpu used for customers already collecting this information with RMF. We plan to continue to use RMF more over time for OMEGAMON collection.