Your Installation's Goals - Do You Need to Use JES XCF Component Services?

As noted above, as JES2 MAS members or JES3 complex members initialize, each automatically attaches to the default JES XCF group. JES uses the JES XCF component as its member-to-member communication mechanism. Therefore, if you do not need to monitor or modify JES message processing or use the JES XCF services, you do not need to use the JES XCF macros and exits described in this document. If, however, you do need to monitor or modify JES message processing or define your own JES XCF groups, you should become familiar with the JES XCF macros, the services each provides, and the JES XCF exits. Table 1 provides an overview of the tasks you will need to accomplish based on your installation's need to affect JES XCF processing.

Table 1. JES XCF Tasks Based on Your Need to Modify JES XCF Communication
If your installation code:	Do the following:
Does not need to monitor JES messaging Does not need to modify JES messaging Will not use JES XCF to send data	Nothing. Your installation will realize the immediate benefits of JES XCF that are listed in JES benefits from the use of the common coupling services component.
Sends and receives messages within standard JES exits or JES3 DSPs	Obtain the JES XCF group token Use JES XCF macros to send and/or receive messages in standard exits or JES3 DSPs
Monitor or modify JES messages	Code JES XCF exit IXZXIT03 to obtain storage for JES XCF transport exit IXZXIT01 and receive exit IXZXIT02 Use JES XCF exits IXZXIT01 and IXZXIT02 to monitor or modify JES messages

Note: If necessary, your installation can create its own JES XCF group and provide JES2 MAS or JES3 complex member attachments to it. Use this document to provide the information you require to create your own attachments.