Before you start the subsystem

Before you can start BSA XCF capable subsystem, you have to initialize it (see "Initializing subsystems in the sysplex").

Joining the sysplex

When a subsystem that is BSA XCF capable is activated, message 9170I appears, and then it is joined to XCF. As a rule, the join is made in the XCF group BETAGRP. When the join is executed, a unique member name is established for each joined user (started task, batch job or TSO online user), identifying this user to XCF.

Note: The XCF group must have an assignment to an XCF transport class. For further information, see "XCF optimization".

XCF member name

The member names created when a join is set up to XCF group BETAGRP have the following structure:

Bnn$sctssidasidn

where:

Character...	Meaning...
nn	Beta product number that was specified by parameter XCF_PROD when the subsystem ID was initialized
$	Separator
sc	Sysclone name of the system from which the join was executed
t	Type of address space:
ssid	Subsystem ID the join was executed for
asidn	ASID number (decimal) of the address space

Searching for subsystem IDs

When a request is made to a subsystem ID, XCF searches for it in the following order of sequence (the subsystem concerned must be active):

1. The search for the subsystem ID is first made on the local LPAR (i.e. the LPAR the user or the batch job is currently working on).
2. If the subsystem ID cannot be found on the local LPAR, the search is continued within the BSA XCF complex.
3. If the subsystem ID cannot be found in the BSA XCF complex, the next and final search is made on the active OCF complex. If this search also fails, the request made to the subsystem ID terminates with an error.