house and other monitoring solutions for TWS for z/OS and End to End have a negative resource impact and the response time is very slow. How does TWSemon address this?
Most (maybe all) available monitoring solutions for TWS for z/OS actually request status information from TWS for z/OS via PIF (Programming Interfaces) or J2EE API. This leads to significant resource consumption and in times with high production load, these PIF requests cannot be handled in time by TWS. Unfortunately the result is when you need the monitor the most, it may not be giving you the answers in time. TWSemon does not normally poll /request information from TWS for z/OS. TWS for z/OS is delivering status information automatically to TWSemon through its exit 7 (EQQUX007). This architecture does not put additional resource requirements on TWS for z/OS and works even in large production environments.
Related Questions
- house and other monitoring solutions for TWS for z/OS and End to End have a negative resource impact and the response time is very slow. How does TWSemon address this?
- What are the important parameters to measure during the wind resource monitoring program?
- How does negative behavior impact academic achievement?
