|
|||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||
 | ||||||||||
| ||||||||||
 | ||||||||||
| ||||||||||
 | ||||||||||
| ||||||||||
 | ||||||||||
| ||||||||||
 | ||||||||||
|
||||||||||
| ||||||||||
 | ||||||||||
| ||||||||||
 | ||||||||||
| ||||||||||
 | ||||||||||
| ||||||||||
 | ||||||||||
| ||||||||||
 | ||||||||||
|
|
|
| ||
| ||
| ||
|
Does TWSemon support TWS for z/OS and End to End?
Yes. TWSemon supports TWS for z/OS and the TWS End to End environments. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
Does TWSemon support TWS distributed (formerly Maestro)?
No, TWSemon currently does not support TWS distributed, whereas TWS End to End is fully supported. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
Can I monitor multiple TWS for z/OS Controllers from one single point?
TWSemon allows monitoring of multiple controllers from one consolidated view. There is no requirement to use “split screen” functionality. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
Is it possible to monitor multiple TWS for z/OS controllers, in a consolidated view, if they are installed on different LPARs, CPUs, Sysplexes or data centers?
Yes, as long as there is a network connection (TCP/IP) to the different environments, TWSemon fully supports these complex environments. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
What is the difference between the TWSemon Supervisor Screen and the TWSemon Working Screen?
The TWSemon Working Screen allows users to monitor “out of line situations” with the added ability to analyze and resolve those events (operating). The Supervisor Screen allows monitoring only. The TWSemon Working Screen and Supervisor Screen are both part of the TWSemon license. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
How can I avoid getting hundreds of “long duration” messages, as most of them are not important?
Normally TWS for z/OS produces an exorbitant amount of non-critical “long duration” messages. With TWSemon it is possible to filter the long duration messages based on absolute and relative values (e.g. job runs 10 Minutes and 30% longer). This allows the user to focus on only on real long duration jobs, rather than responding to “false alarms”. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
I currently need to check manually if certain jobs are completed at a certain time. This is an error prone manual process. Is there a way TWSemon can assist?
Within the TWSemon administration, you can define milestones to jobs. In case the job is not completed by the defined time (late/milestone), TWSemon will display a warning. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
How can I proactively monitor service levels in the TWS for z/OS and End to End environments, and be made aware of a problem as soon as possible?
TWSemon SLA Realtime Forecast, which is an optional component of TWSemon, fulfills this requirement. TWSemon SLA Realtime Forecast sits on the TWSemon monitoring architecture and is especially designed to forecast in real-time if future service levels are under risk or will be met. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
Can I display a graphical view of the Current Plan, for example to visualize the predecessor dependencies of a job in error?
The ISPF interface of TWSemon provides a lot of advantages for monitoring and operating in a TWS for z/OS and End to End environment; however, for visualizing a flowchart of the current plan it has its limits. TWSemon Web, an optional component of TWSemon fulfills this requirement. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
In-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. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
How long does it take to install TWSemon?
The length of installation depends on your environment. There is a checklist available to make sure that all required authority settings are in place prior to installation. The base installation then takes about 2-3 hours and each additional TWS for z/OS Controller will add proximally another 30 minutes. |
||
|
Need More Info
Back to Top
|
||
| ||
| ||
| ||
|
How long does it take to train operators on TWSemon?
We suggest an initial 2-3 hour training session and another 2 hours “deep dive” session after two weeks working with TWSemon. |
||
|
Need More Info
Back to Top
|
||
| ||
| Contact us for a free 30 day trial or a live presentation of our solutions | ||
| ||
|
| Legal Notice | Imprint | Site Map |
|
|
Copyright © 2008 APS|ENTERprise software consulting gmbh (Germany). All rights reserved. |
