Updating XCF initialization options

This section is useful if you use XCF for communication.

XCF initialization options are specified in the COUPLEnn member of SYS1.PARMLIB. If you have not specified your own COUPLEnn member, the system uses the default member, COUPLE00. The IBM-supplied COUPLE00 member causes the system to be IPLed in XCF-LOCAL mode. This mode is not supported by Tivoli Workload Scheduler for z/OS. So ensure that your system uses a COUPLEnn member that does not IPL the system in XCF-LOCAL mode. The COUPLEnn member must include the PCOUPLE keyword of the COUPLE statement. If this is omitted, XCF is initialized in XCF-LOCAL mode. For Tivoli Workload Scheduler for z/OS purposes, you can use the default values for the remaining XCF options.

|COUPLEnn example
|COUPLE   SYSPLEX(PLEX1)                 /* SYSPLEX name             */
|         PCOUPLE(PLEX1.COUPLE1)         /* Primary couple data set  */
|         ACOUPLE(PLEX2.COUPLE2)         /* Alternate couple data set*/
|         MAXMSG(2000)                   /* No of 1k message buffers */
|CLASSDEF CLASS(DEFAULT)                 /* Default transport class  */
|         CLASSLEN(956)                  /* Message length           */
|         GROUP(OPCGRP,OPCDS)            /* OPC Group names          */
|PATHIN   DEVICE(cccc,dddd)              
|PATHOUT  DEVICE(aaaa,bbbb)
|PATHIN   STRNAME(str1,str2) CLASS(DEFAULT)
|PATHOUT  STRNAME(str1,str2) CLASS(DEFAULT)

Issue the console command "D XCF,CLASSDEF,CLASS=ALL" to see if you already have a DEFAULT class (the name of this class might be something other than DEFAULT) having CLASSLEN(956), which is the default value. If there is such a class, you just need to add the TWS specific GROUP names (OPCGRP,OPCDS) to the CLASSDEF statement for that CLASS, as shown in the example above.

Note:

| |

By specifying MAXMSG(2000) on the COUPLE statement, as shown |above, all transport classes will use this value unless a different |value is specified at the CLASSDEF level. MAXMSG(2000) is the default |value.

If XCF is used to connect the Data Store to the controller, a specific XCF group must be defined, and it must be different from the one used to connect the controller to the z/OS® tracker. These two separate XCF groups can use the same XCF transport class.

Note:

You can change XCF options while the system is active by using the SETXCF operator command.

For more information about XCF, see z/OS MVS™ Setting up a Sysplex.