|
I/O operations allows operators to make operational changes to z/OS-based I/O configurations—ESCON and FICON—in a safe, system-integrated way. To help operators make those changes or perform I/O problem determination, it also provides displays with accurate, up-to-date information that is extracted directly from the active I/O configuration of an enterprise. From these displays, not only can an operator view information but also control I/O resources. Establishments without ESCON or FICON Directors can still benefit from those functions.
I/O operations performs its control operations across multiple systems in a centralized and system-integrated manner. A change can be input on one system, and the I/O operations running on that system will automatically communicate that change to copies of I/O operations on other systems that are potentially affected. Each I/O operations that is participating in the operation then uses system interfaces to coordinate the I/O configuration change with its own operating system image. If the coordination is not successful (for example, if one z/OS image rejects a request because it would remove connectivity to an allocated or reserved device), then the operation will fail. This change processing is performed using the two-phase commit model of database systems, so that I/O operations can attempt backout of a failed operation. If, for example, a director's connectivity is changed using I/O operations, it identifies the affected paths and VARYs them appropriately, across multiple system images as one operation (and attempts backout if the entire operation is not successful).
Using I/O operations gives an operator the ability to configure channels on and off, remap the internal connectivity of ESCON/FICON Directors (port-by-port or as an entire configuration), and vary devices on and off. The operator can also control I/O operations itself—for example, fence off a system that cannot respond in order to avoid unnecessary delays, or establish communications with instances of I/O operations running on images that do not share ESCON/FICON Directors.
I/O operations itself collects the information it displays—no separate configuration data file is necessary—and updates it dynamically as the configuration changes. The resources it reports on range from system images to channels, ESCON/FICON Directors and their internal connectivity configuration, control units, devices, converters, and coupling facilities. It reports on resources regardless whether they are ESCON/FICON or not, though information is most complete for ESCON/FICON resources.
I/O operations provides a programming interface that allows you to build scripts for NetView operators or to write automation applications, including full multisystem function. It also provides an ISPF dialog and a command set for the z/OS operator's console, which are intended for local usage on a single system.
In System Automation for z/OS, I/O operations covers the I/O configuration function. You may have questions about its relation to other IBM configuration management tools: the Hardware Configuration Definition (HCD) facility in z/OS, and the Hardware Configuration Management (HCM) product.
HCM is the recommended Graphical User Interface (GUI) for use with I/O operations. You can use HCM as your main tool to create I/O configuration definition data, HCD as your main tool to activate those definitions, and I/O operations as your main tool to manage the configurations, once activated. None of the three replaces any other, but they are integrated to exploit each other's function.
|
