Your installation's need to create its own JES XCF attachment should be based on either 1) whether JES members will be sending large amounts of data or 2) whether your modifications will adversely affect system performance.

If you expect to use the JES-defined attachment to send large amounts of data, that added load can affect JES' ability to communicate between its members. This is likely to degrade performance and impact members' ability to communicate critical information across the JES XCF group. To maintain JES' high-speed delivery of such information, you cannot allow your installation to over-use the JES-defined attachment for other less critical communication needs.

If however, you do not expect to send large amounts of data or do not expect to use the attachment often, the JES-defined attachment might very well meet your installation's needs. Therefore, before creating another attachment, use the JES-defined attachment and closely monitor system performance. If you determine that you do not need to create a separate attachment to JES XCF, you can still use JES XCF to, for example, modify and reroute messages. To do so, you will need to retrieve the default JES XCF group token using the procedure in Retrieving the JES XCF Group Token.

If you determine that you will be sending large amounts of data, or have experimented with the JES XCF attachment and found performance degradation, then you will need to create an independent attachment to the JES XCF component.