Wednesday, March 3, 2010

RLIM enhancements to OMEGAMON XE For CICS V4.20

I've posted earlier on the new features of OMEGAMON XE for CICS V4.20 (now GA by the way). One nice enhancement I didn't mention is you now have the ability to use RLIM (the resource limting facility) to automatically start an application trace. This means that if you have an outlier transaction running in a CICS region, RLIM can invoke the trace and hopefully capture at least a portion of the problem tran. To take advantage of this option you need to set your RLIM options carefully, but it has potential for certain customers. I will do a nother post on RLIM in more detail later this month.

1 comment:

  1. Hello,
    I don't know if this is the place, but I hope you could help me or at least point me to some resources.
    At our facility we use the Resource Limiting feature for CPU and DB2 Calls. I'm trying to find a way to dynamicly change the kill values of the transaction we specified. The way we currently change them, is by changing the kill value inside the GLOBAL BLOCK member and restarting (shutting it down, and starting up) omegamon. Is there a way to change the values without restarting omegamon?

    Igor Basko


Note: Only a member of this blog may post a comment.