Interfaces to the Operating System
To implement system automation, begin by giving the NetView® program access to information
that describes the state of the operating system, subsystems, and
applications. Also set up the NetView program
to send commands to the system and receive command responses. You
can enter commands and receive responses using the subsystem interface
or extended multiple console support (EMCS) consoles. Other interfaces
that you can use for system automation include:
- System Automation for OS/390® Processor Operations can intercept traffic on system consoles.
- The NetView program terminal access facility (TAF) can intercept messages from other applications, including system applications, to their own consoles.
- Local devices of MVS™ can pass certain types of system problem notifications to the NetView program for processing.
- The MS transport and the high-performance option of the MS transport allow LU 6.2 communication between two applications. One use of the transports is to pass information between a system application and the NetView program.
- The program-to-program interface accepts MSUs from system applications running with the NetView program on the same system and can pass them to the NetView program hardware monitor or to the automation table.
If you intend to automate your system, ensure that the messages and other information you want to automate come to the NetView program.
See Overview of Automation Products for an overview of the relationship between the operating system and the NetView program in system automation.
For step-by-step information about how to set up system communication, see Establishing Communication between the NetView System and the Operating System.
If you need system flow information in more detail, see MVS Message and Command Processing.