Using commands that have sysplex scope

Commands that have sysplex scope have the following characteristics:

They affect resources that are shared throughout the sysplex. Examples of such resources include the Sysplex Timer, the coupling facility, couple data sets, and certain DASD volumes.
You can issue them from any system in the sysplex; the results are identical.
The results of issuing them are sysplex wide without the need to use ROUTE *ALL. You should not use any form of the ROUTE command to issue a command with sysplex scope because doing so is redundant. Here's why:
- You use ROUTE to have a command issued on a particular system, group of systems, or all systems in the sysplex. Using the ROUTE command is the logical equivalent of walking up to a console attached to each system you route to, and issuing the command from that console.
- You do not need to issue a command with sysplex scope on a particular system, group of systems, or all systems in the sysplex. You issue the command once from any system.

Note that a command can have sysplex scope when you use particular parameters, and not have sysplex scope when you use other parameters.

Commands that have sysplex scope are so noted in the documentation for that command, and include those in the following table. If a command has All under “Conditions”, then the command has sysplex scope under all circumstances and for all variations.

Table 1. MVS™ System Commands With Sysplex Scope
Command	Conditions
CHNGDUMP	Has sysplex scope only when all systems are connected to the same coupling facilities, and you specify ,SDUMP,SYSFAIL,STRLIST=.
CONTROL C,A	All
CONTROL C,D	Has sysplex scope only when you specify L=.
CONTROL M	Has sysplex scope only when you do not specify MLIM, UEXIT, LOGLIM, or APPLID.
CONTROL other	Other parameters of CONTROL have sysplex scope only when you specify L=.
DISPLAY CF	Has sysplex scope only when displaying information about the coupling facility and only for those systems connected to the coupling facility. Does not have sysplex scope when displaying an individual system's coupling facility configuration information (coupling facility channels and paths).
DISPLAY CNGRP	All
DISPLAY CONSOLES	Has sysplex scope unless you specify DISPLAY C,B or DISPLAY C,U.
DISPLAY DUMP	Has sysplex scope only when you issue the OPTIONS parameter to display the results of a CHNGDUMP ...SDUMP,SYSFAIL,STRLIST= command.
DISPLAY EMCS	Has sysplex scope, except when you specify STATUS=B or STATUS=ERR. When you specify STATUS=FULL, consoles from all systems will be displayed (for consoles that are not active on the system where this command is processed, some information will not be displayed).
DISPLAY GRS	Has sysplex scope unless you specify SUSPEND. Also, note the following about DISPLAY GRS,C and DISPLAY GRS,RES: the output generated by these commands includes both system-specific information (S=SYSTEM) and sysplex information (S=SYSTEMS). The S=SYSTEM information is valid only for the system on which you issue the command. The S=SYSTEMS information is identical regardless of the system on which you issue the command.
DISPLAY GRS,ANALYZE	Has sysplex scope for Enqs, but can be limited to a system. Note that D GRS,ANALYZE,LATCH only returns latch analyze information for the system the command is running in.
DISPLAY LOGGER	Has sysplex scope when you use either L or C,SYSPLEX options.
DISPLAY OPDATA	Has sysplex scope for the PREFIX operand, the MODE operand, and the MONITOR operand (except for SPACE and DSNAME, and all MONITOR operands issued from a TSO user).
DISPLAY PFK	Has sysplex scope only when you specify CN=.
DISPLAY R	Has sysplex scope, but the output might be different on different consoles, because the output of DISPLAY R is dependent on the routing criteria for the console specified by CN=. If you do not specify CN=, the routing criteria of the console issuing the command is used. If you issue the command in a program (by using the MGCRE macro) the console you specify in the macro is used. If you specify a console ID of 0, all retained messages are included in the command response.
DISPLAY WLM	All
DISPLAY XCF,ARMSTATUS	Has sysplex scope provided all systems are using the same ARM couple data set.
DISPLAY XCF,CF	Has sysplex scope provided all systems in the sysplex are connected to the same coupling facilities.
DISPLAY XCF,COUPLE	Has sysplex scope as long as all systems are using the same types of couple data sets, as specified on the TYPE parameter (SYSPLEX, ARM, CFRM, SFM, LOGR, and WLM.) If you do not specify the TYPE parameter, only system-specific data is displayed.
DISPLAY XCF,GROUP	All
DISPLAY XCF,POLICY	Has sysplex scope as long as all systems are using the same types of couple data sets, as specified on the TYPE parameter (ARM, CFRM, SFM, and LOGR.)
DISPLAY XCF,STRUCTURE	Has sysplex scope provided all systems in the sysplex are connected to the same coupling facilities.
DISPLAY XCF,SYSPLEX	All
MONITOR	Has sysplex scope only when you specify L=.
MOUNT	Has sysplex scope only when you issue the command against an automatically switchable tape device.
REPLY	All
RESET CN	Issue the command from the system where the console was active to avoid inconsistent sysplex results.
SEND	Has sysplex scope only when sending to consoles; does not have sysplex scope when sending to TSO users.
SET CNGRP	Has sysplex scope provided all systems are sharing the same parmlib data set.
SET CON	Has sysplex scope when adding a sysplex accessible console (SMCS, subsystem), or when changing the value that is associated with a sysplex scope CONSOLxx keyword.
SET DAE	Has sysplex scope only when all systems are sharing the same DAE data set and the same parmlib data set.
SET GRSRNL	Has sysplex scope only when all systems are sharing the same parmlib data set.
SET SMS	Has sysplex scope when you are issuing the command to change the name of the ACDS or COMMDS. All systems in the sysplex must be in the same SMS complex, and using the same parmlib data set. If you are issuing the command to start or restart SMS on a system, only the system on which you issue the command is affected.
SETCON DELETE	All
SETCON MODE	All
SETLOGR FORCE	Has sysplex scope when you use DELETE,LSName options.
SETSMS	Has sysplex scope only if you are changing the SCDS, ACDS, or COMMDS, and only if all systems in the sysplex are in the same SMS complex.
SETXCF FORCE	Has sysplex scope only when all systems are connected to the same coupling facility.
SETXCF COUPLE	Has sysplex scope only when you specify PSWITCH, ACOUPLE, or PCOUPLE, and all systems have access to the specified couple data set.
SETXCF START\|STOP	Have sysplex scope only when you specify POLICY or REBUILD.
STOPMN	Has sysplex scope only when you specify L=.
UNLOAD	Has sysplex scope only when you issue the command against an automatically switchable tape device.
VARY CN	Has sysplex scope unless all of the following are true: You issue VARY CN(conspec),ONLINE without specifying SYSTEM=. You do not specify SYSTEM= in the CONSOLxx parmlib member that defines this console. The console has never been active in the sysplex.
VARY SMS, STORGRP\|VOLUME	Has sysplex scope under these conditions only: You specify (storgrp\|volume,ALL) and all systems in the sysplex are in the same SMS complex. You specify (storgrp\|volume system) where system is a system group, and the system group exactly matches the sysplex (that is, none of the systems in the sysplex is explicitly defined to SMS).
VARY SWITCH	Logical partition cluster scope -- see the "Intelligent Resource Director" chapter in z/OS MVS Planning: Workload Management for more information.
VARY XCF	All
VARY WLM	All