The COUPLE statement

The COUPLE statement includes the following keywords:

SYSPLEX — contains the name of the sysplex. The sysplex name allows a system to become part of the named sysplex.
Specify the same sysplex-name for each MVS™ system in the sysplex. Sysplex-name must match the sysplex name specified on the couple data sets when they were formatted.

If you plan to define two or more sysplexes, IBM® recommends that their names be unique. Some applications cannot handle duplicate sysplex names. Also, consider using meaningful names. For example, if you plan to set up three sysplexes in a New York installation, two in San Francisco, and another in Dallas, the sysplex names could be defined as: NYPLEX00, NYPLEX01, NYPLEX02, SFPLEX00, SFPLEX01, and DAPLEX00.

The sysplex name is also the substitution text for the &SYSPLEX system symbol. As of MVS/ESA SP 5.2, if you specify the sysplex name in both the COUPLExx and LOADxx parmlib members, all parmlib members can use the defined substitution text for &SYSPLEX.
PCOUPLE, ACOUPLE — contain the names of the primary and alternate sysplex couple data sets and are described in Planning the couple data sets.
INTERVAL, OPNOTIFY, CLEANUP — can contain values that reflect recovery-related decisions for the sysplex. They are described in the topic, Controlling availability and recovery through COUPLExx.
CTRACE — can name an XES or XCF component trace parmlib member that contains initialization parameters for its component trace.
In the CTRACE keyword, you can specify a CTnXCFxx, a CTnXESxx parmlib member, or both (by specifying the CTRACE keyword twice). For information about component traces, see z/OS MVS Diagnosis: Tools and Service Aids.
MAXMSG, RETRY, CLASSLEN — can contain values related to signaling services and are discussed in Planning for optimum signaling performance. A value you specify for one of these keywords on the COUPLE statement becomes the default value if you do not specify that keyword on the CLASSDEF, PATHIN, PATHOUT, or LOCALMSG statement.
CFRMPOL — can contain the name of a CFRM policy that is to be automatically started at IPL time, if there is no other previously-activated CFRM policy in effect. See Starting a CFRM policy.
CFRMOWNEDCFPROMPT — allows the installation to request operator prompting to control usage of coupling facilities previously owned by the same sysplex at IPL time.
VMCPUIDTOLERATION — controls the verification of CPU identification information.