Message and command flow in a sysplex

In a sysplex, MVS™ messages and commands can flow from system to system. Because you can direct the message or command to one or more systems, you need to understand how exits, subsystems, and hardcopy log processing occurs in a sysplex.

Consider the following for message and command flow in a sysplex:

Console operations. MCS, SMCS and extended MCS consoles can receive messages from different systems or enter commands to affect the processing of other systems.
Installation exits. Installation exits can perform much of your message and command processing. For processing like message suppression, making messages eligible for automation, or for processing that alters commands, message and command flow in a sysplex become important.
Subsystem processing. Subsystems can process MVS messages and commands. To help control or coordinate subsystem functions in a sysplex, subsystems need to consider from which systems messages and commands originate.
Automation for systems in a sysplex. Automation programs like NetView® use messages and commands to control automation in a system. How different systems control automation in a sysplex depends on how messages and commands can flow from system to system.
Logging of messages and commands in a sysplex. You can use the operations log (OPERLOG) to record messages and commands from all the systems in a sysplex. The operations log centralizes log data in a sysplex.