CleverView for cTrace Analysis: Frequently Asked Questions

What does CleverView for cTrace Analysis do?
What protocols does this product support for the IP packet trace of the mainframe component trace?
What unique features offered by CleverView for cTrace Analysis are not inherent in other trace decoding tools?
Can CleverView for cTrace Analysis save me a lot of trace analysis time by offering a quick path to highlighting packets with exceptional condition? Does it make this information easily accessible to me?
If I need to go to the detail packet and transaction level, does this product offer an easy way for me to digest the information with a good filtering capability?
Does CleverView for cTrace Analysis offer filtering capabilities that make it easier to find problem packets?
Can I create my own filters?
Who would benefit from this tool in our IT organization?
Does CleverView for cTrace Analysis offer Sniffer® Trace Support?
Is there a simple way to compare traces with CleverView for cTrace Analysis?
Does CleverView for cTrace Analysis offer a real-time option for packet tracing and analysis?
Does CleverView for cTrace Analysis offer tools for component trace generation?
What methods are available for transferring trace files to CleverView for cTrace Analysis?
What is the size limit for trace files analyzed by CleverView for cTrace Analysis?
Is it possible to customize the CleverView for cTrace Analysis GUI for my own purposes?
How does CleverView for cTrace Analysis handle Enterprise Extender?
Does CleverView for cTrace Analysis support OSPF?
Does CleverView for cTrace Analysis handle migrations to the IPv6 environment?
If I generate a component trace manually under z/OS, can I use CleverView for cTrace Analysis to analyze it?
Can I trial the product or see a demonstration before purchasing?