Debugging Your NetView Automation Table
LarryGreen 0600009UYQ Visits (5775)
The Automation Table is one of a number of capabilities in the NetView® for z/OS® program that allow for automated handling of many of the information-system and network operations that usually require human intervention. Automation can improve the availability of systems and networks by quickly and accurately responding to unexpected events. And when outages do occur, whether planned or unplanned, automation can dramatically reduce recovery time. Automation can reduce the chances for operator errors by either eliminating the need for operator response entirely, or if operator intervention is required, by simplifying the task, and ensuring consistent responses to similar events. As customer environments grow larger and more complex, automation can increase operator productivity, ensure consistent operating procedures, allow for centralized control, slow the growth of staffing requirements, and remove other constraints that could hinder smooth growth.
The Automation Table allows customers to identify conditions they want automation to handle and to specify actions to be taken in response to those conditions. The Automation Table can be structured as a single table defined in one data set member, or as multiple, concatenated tables; it also allows for one table to include another one. Within a table, related statements can be further organized into blocks. This flexibility allows the customer to structure the table efficiently to minimize condition checking and therefore CPU usage, and if desired, in a way to reflect organizational, geographic, or other considerations of their company.
Regardless of how simple or complex your automation table is, there will undoubtedly be times when automation is not doing what you expected – there’s a bug somewhere. How do you find it?
NetView provides a number of tools and techniques to help identify and correct bugs or other undesired actions in your automation table. These range from simple syntax checking, to tests of the automation logic, to tools to help you analyze the structure of your table and understand its efficiency, and more. To learn more, take a look at "Deb