It's May 24, and today we're very pleased to announce NetView for z/OS V6.1, a release that was designed, developed and tested with customers to deliver the value and capabilities that customers have asked for and need. And it's not just a new release, but a new version -- Version 6, continuing NetView's long tradition of delivering rock-solid value to customers through powerful network and system management capabilities. Here are just a few of the highlights of this new release.
Expanded logging and log browsing
There's a wealth of information available in the log files on a z/OS system. For example, the syslog generally contains information about system activity, the netlog about network activity, and various joblogs hold information about specific jobs. For some problems, you can find all the diagnostic information you need in just one of those logs. But for other types of problems, debugging is not so simple; you might have to browse the syslog for some of the information, then to go to ISPF for a joblog, and finally to the NetView console to review the netlog. You locate and piece together the various bits of information, and finally arrive at a diagnosis. NetView V6.1 dramatically simplifies this process with the introduction of the Consolidated Audit, NetView and z/OS Log -- the CANZLOG. This log consolidates in one place all of the system's message traffic, including JES and subsystem messages. And at your option, can also include foreign messages -- messages forwarded by z/OS across the sysplex. Rich filtering capability allows you to browse only the records you care about. Need to know what was happening on a certain console at 2:00 last Sunday morning when that job abended? No problem. Need to see all the messages with a certain descriptor code from a particular address space? Easy. Need to see the messages that match a particular DOM? Simple. Filters can be organized using logical combinations of attributes to include or exclude the desired messages. CANZLOG also archives log records and then recalls them seamlessly as needed, so the user need not distinguish between active and archived records. All messages in the CANZLOG are subject to automation, and a REXX API provides program access to all data. For an in-depth discussion of the CANZLOG function, see the whitepaper on that topic in the NetView for z/OS section of the IBM Tivoli Media Gallery (http://www.ibm.com/developerworks/wikis/display/tivolimediagallery/Tivoli%20NetView%20for%20zOS).
We've also added a default operator logon profile, so that users who are defined in a SAF product, such as RACF, no longer have to be defined in the NetView operator definition member. This allows you to quickly and easily add and define authority for users who might need to be able to log in to NetView in order to use the CANZLOG, but should not have access to other NetView functions.
Smart Packet Collection
As reliable as IP transport has become over the last few years, network problems do still occur. You've just deployed a new application; the server and client can connect, but the server keeps terminating the connection. Why? Is the client sending something incorrect that causes the server to end the connection? Or is the problem on the server side? You need to know what's being sent over the connection. For several releases now, NetView has offered real-time collection of IP packets. You could start and stop packet traces, collect the traced packets, and view them in real-time. NetView V6.1 adds intelligence to packet collection. Rather than having to analyze all the data yourself to locate a problem, NetView can do the analysis for you. For example, connections can be analyzed to identify those with errors of a certain type, such as retransmits. See which packets belong to those connections, and drill down into packet content for specifics. Examine statistical information about the connection, such as data segment statistics, data quantity and throughput, window statistics, etc. Drop a connection, or save the traced packets for later recall. NetView's smart packet collection greatly simplifies the task of debugging network problems.
"Wait a minute," you say. "You're talking about NetView. Doesn't it just manage SNA?" Take another look. Yeah, you can still use NetView to manage your SNA environments, but there's a LOT more capability there. Did you know NetView has been managing IP networks for 15 years? Smart packet collection joins the robust set of IP management capabilities already available in NetView, including traps, connection
management, automated response to intrusions, SNA over IP, dealing with hung listeners, and much, much more.
Demos of CANZLOG and smart packet collection are available in the Tivoli NetView for z/OS section of the IBM Tivoli Media Gallery (http://www.ibm.com/developerworks/wikis/display/tivolimediagallery/Tivoli%20NetView%20for%20zOS)
GDPS Active/Active support
Also announced today is IBM's GDPS Active/Active continuous availability solution. This solution provides for two or more sites, separated by unlimited distances, running the same applications and having the same data to provide cross-site workload balancing and near continuous availability. This solution represents a paradigm shift from a failover model to a near continuous availability model. It significantly increases workload, system, and site resiliency, and provides granularity down to the workload level. NetView provides monitoring of workload status, workload servers, replication, load balancers and other managed elements that are part of the solution, and the associations among them.
This new version of NetView will be generally available on May 27. Check it out. The full announcement letter is at http://www-01.ibm.com/common/ssi/rep_ca/6/897/ENUS211-186/ENUS211-186.PDF