This fix pack has several enhancements that add to the ways you can display transaction data, separate specialty-processor from general-purpose CPU usage, and diagnose application performance problems by examining data for outbound API requester applications.
Displaying transactions per second or per minute
A new OPTIONS command lets you display the Transaction Rate as transactions per second, instead of per minute. This applies wherever Transaction Rate shows up; for example, at the All Active CICSplexes panel, the CICS Region Overview, the CICSplex Regions Performance Summary, or the CICSplex Service Level Summary and Service Class Detail panels. For details on how to change the setting, see Viewing transaction rate per second or per minute. All of the CICS regions being monitored must be at Fixpack 3 or above in order to set the rate to transactions per second.
New resource types for Resource Limiting
Resource Limiting has been enhanced with three new Resource Types: CPUGP (general processor CPU), CPUQR (QR TCB), and RUNTIME. This lets you specify resource limits for general processors, excluding time spent on specialty processors, as well as for tasks held due to MXT or Class maximum (RUNTIME).
If you have programs that run on specialty engines, these are most likely less of a concern than programs running on the general processor, because they have less impact on the system and the overall cost of running the environment. So you may not want to include the time on specialty engines in the CPU Time calculation for Resource Limiting.
Programs that run on the general processor, and especially the QR TCB, may be of more concern. Because there is only one QR TCB, it’s important to limit the amount of time a task is using it. With this enhancement, you can specify Resource Limiting thresholds for time spent on the QR TCB, by using the CPUQR Resource Type, as well as time spent on a general processor, by using the CPUGP Resource Type, without limiting the time spent on a specialty processor or an Open TCB.
With the new Resource Types, the Task History Detail and Active Task Detail panels now displays the CPU time on specialty processors, the CPU eligible for specialty processors, and the CPU time on general purpose processor(s).
The upcoming CICS Performance Analyzer for z/OS (CICS PA) APAR PH58649 will provide users the ability to report on transactions which have exceeded the warn limits for all the resources supported by RLIM.
Monitoring Outbound API requester applications via z/OS Connect
IBM Z OMEGAMON for CICS can now monitor outbound API requests being made by CICS applications. If you use outbound APIs, you need to be able to keep track of which ones are in use and how they're performing. This fix pack provides an enhancement that shows you which outbound APIs are being used by CICS applications, along with their response time. If you have applications experiencing timeouts, resulting in delays to CICS requests, this enhancement can show you which API is most at fault. Outbound API monitoring allows you to identify tasks that are holding resources and delaying other work in the CICS region. IBM Z OMEGAMON for CICS displays the request rate per minute and the average response time, in seconds, for each API currently in use, as well as other information from the URIMAP, including the total number of faults and timeouts since transaction manager statistics were last reset. You can also see historical information for a previous time period, in the Historical Summary.
FIND command for Temporary Storage models
The FIND command can now be used to find Temporary Storage models based on the queue prefix. As with other resource types, the asterisk (*) and question mark (?) wildcards are supported.
New Task values
IBM Z OMEGAMON for CICS now provides TCP/IP Service and TCP/IP Port information on the Transaction Statistics panel; they are displayed in a new subpanel at the bottom of the panel.
These and other previous enhancements are listed in IBM Documentation, under What’s New in IBM Z OMEGAMON for CICS.
#OMEGAMON #IBMZ #IBMz/OS #CICS #monitoring #AIOps