In a Sysplex environment, only one Datacom MUF is required. CA-11 on all other systems access the MUF via an XCF connection. Each system in the Sysplex must have access to module DBSIDPR. Each system must also have the Datacom SVC loaded by CAIRIM.
There are 3 parameters in Datacom that should be taken into consideration for the XCF connection. These parameters are MUF, XCFFROM and TASKS.
MUF AD10MUF,99,NO This statements gives the MUF a name.
XCFFROM *,SYSPROD Defines remote system that may access mu
- '*' is specified as the wild-card task names that will access muf via XCF.
This is required after CA-Datacom/AD SP03.
- SYSPROD represents the value of group name on the TOGROUP parameter
TASKS 35,33K,0,0,29 # of TASKS, SIZE,0,0,XCFTASKS
- the # of TASKS first parameter is the maximum number of tasks that accesses the MUF (this includes both local and XCF) . This value should be larger then the number of XCFTASKS
- the XCFTASKS is the maximum number of XCF accesses. The following should be taken into consideration when calculating the number of XCFTASKS needed
- 5 for EACH Unicenter CA-11 started task region. Assuming DBAS Configuration file contains a parameter of DBTASKS=5 One additional task is needed in the MUF definition for the Automatic Resume/Heartbeat function added by PTF QO81922. See NOTE below.
- 1 additional task for the Unicenter CA-11 maintenance process that runs on the Unicenter CA-11 region running on the same machine as the MUF
- 1 for EACH concurrent user (TSO, CICS, Roscoe) of Unicenter CA-11
EXAMPLE: A SYSPLEX ENVIRONMENT WITH 3 LPARS AND MUF RESIDING LPAR3.
LPAR 1: 2 TSO USERS AND 1 CICS USER
LPAR 2: 2 TSO USERS
XCFTASKS= LPAR1 + LPAR2
XCFTASKS= (6 + 3) + (6 + 2) = 17
Note: With PTF QO81922 for the Automatic Resume/Heartbeat functions, add 1 to DBTASK value to get the total number per system for the XCF task number. Also for the best performance, MUF must reside at the LPAR which has the most workload of batch processing.