Network Entry Type

When multiple z/OS systems are interconnected and require consolidated operations at one focal point system, you can use focal point services to monitor and control the systems.

These services allow an operator to view the status of multiple systems from a single system acting as a focal point and to send messages, commands, and responses from a focal point system to other systems. The Network entry type allows you to:

• Define paths for sending messages, commands, or responses from one system to another.
• Define primary and backup focal point systems.
• Define user Terminal Access Facility (TAF) fullscreen sessions and specify whether each of these should be initiated automatically when the operator logs on to the SA z/OS NetView Interface. If a TAF session is not defined to start automatically, you can initialize it using the OPER dialog.
• Define gateway sessions connecting systems.

  A gateway session uses autotasks both inbound to and outbound from a system to send data between systems.

  Communication with the focal point system is performed using the NetView RMTCMD command or XCF. XCF is used when commands are sent to systems within the same sysplex (that is, with the same XCF group ID or PLEX ID). Otherwise, RMTCMD is used. In both cases, you can see the responses on your operator task.

• Define OMEGAMON sessions.

  OMEGAMON sessions can be used to retrieve exception information or general performance and availability data for health monitoring and proactive automation.

• Manage access keys to the NetView password data set, where passwords can be stored that are needed when OMEGAMON sessions have to be established.
• Define Simple Object Access Protocol (SOAP) servers and their attributes to be able to communicate with IBM Tivoli Monitoring (ITM).

The chapter Automating Networks in IBM Z® System Automation Customizing and Programming provides more information on the defining automation networks.