×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
All,
Looking to provide users with our own performance metrics.
I've found the following APIs:
* End Transaction (QYPEENDT, qypeEndTransaction) indicates the end
of a user-defined transaction.
* Start Transaction (QYPESTRT, qypeStartTransaction) is called at
the start of a user-defined transaction.
Along with the Collection Services Data Collection Exit Program.
I also found an excellent presentation by Bruce Vining
http://www.brucevining.com/Presentations/PPT_Presentations/Summit2007_Reducing_Support_Costs.pdf
Which I think will be a big part of the solution, but not all of it.
For instance, one thing that we're really interested in is how many
jobs are waiting in the job queues. So I'm curious if there's anybody
out there with experience writing programs to capture and report your
own metrics outside of the above APIs.
If so any tips/tricks/thoughts/comments you'd like to share would be
appreciated.
For example, assuming a metric is collected frequently enough, writing
the data directly to a DB file may not be a good idea due to the
overhead of the DBMS. Which is why IBM uses *MGTCOL objects. I
assume I'd have to make due with *USRSPC objects or IFS stream
files....
Thanks!
Charles Wilt
midrange.com
