XCFOPTS
Purpose
The XCFOPTS statement defines run-time options for HCL Workload Automation for Z systems that use services of the cross-system coupling facility (XCF). Specify this statement for a tracker, controller, or standby controller that uses XCF for communication.
XCFOPTS is defined in the member of the EQQPARM library as specified by the PARM parameter on the JCL EXEC statement.
Format
Parameters
- GROUP(XCF group name)
- The name of the XCF group that the HCL Workload Automation for Z system
should join. This is an alphanumeric name consisting of 1 to 8 characters
where the first character is alphabetic.
The name of this XCF group must be different from the one defined in the DSTOPS and FLOPTS groups.
- MEMBER(XCF member name)
- The XCF member name that identifies
the HCL Workload Automation for Z system.
This is an alphanumeric name consisting of 1 to 8 characters where
the first character is alphabetic.
The member name must be unique within the group. If an HCL Workload Automation for Z system tries to join a group with the same name as an existing member, an error message is issued, and HCL Workload Automation for Z ends.
- TAKEOVER(HOSTFAIL,SYSFAIL)
- The TAKEOVER keyword applies to an HCL Workload Automation for Z system
where you specify OPCHOST(STANDBY) on the OPCOPTS statement. It defines
the situations when the standby system automatically takes over from
the host HCL Workload Automation for Z system
if the host fails. If you have not specified TAKEOVER, HCL Workload Automation for Z sends
a WTO message to the operator console asking the operator to manually
start takeover actions. You can specify either one or both of the
takeover conditions.
- HOSTFAIL
- Automatic takeover occurs when the controller fails.
- SYSFAIL
- Automatic takeover occurs when the system that the HCL Workload Automation for Z controller is running on fails.
In this example of an XCFOPTS statement:
- 1
- A standby controller has a member name of GRP1STBY.
- 2
- GRP1STBY is a member of the XCF group XCFGRP1.
- 3
- The standby controller automatically attempts to take over the functions of the controller if the controller fails, or if the z/OS system that the controller is running on fails.