Managing Transfer CFT to Sentinel communication parameters

This topic describes the configuration files and parameters you set to enable interoperability between Transfer CFT and Sentinel.

• Viewing parameter values
• Setting parameter values
• TCP exchange parameters - all platforms
• Transfer CFT parameters for Sentinel interoperability - all platforms
• Communication with the Event Router - z /OS only
• Overflow file definition - z /OS only

Viewing parameter values

To view the values of all Transfer CFT exchange parameters:

1. Open a command console.
2. Enter an absolute path to the cftuconf user file (cftuconf.dat).
3. Enter the command:
4. CFTUTIL listuconf id=sentinel.*

To view the value of a specific Transfer CFT Sentinel exchange parameter:

1. Open a command console.
2. Enter an absolute path to the cftuconf user file (cftuconf.dat).
3. Enter the command:
4. CFTUTIL listuconf id=sentinel.[parameter_name]
5. Example (returning the TRKTYPE value):
6. CFTUTIL listuconf id=sentinel.TRKTYPE

Setting parameter values

To set the value of a Transfer CFT exchange parameter:

1. Open a command console.
2. Enter an absolute path to the cftuconf user file (cftuconf.dat).
3. Enter the command:
4. CFTUTIL uconfset id=sentinel.[parameter_name]
5. Example (setting the TRKTYPE value):
6. CFTUTIL uconfset id=sentinel.TRKTYPE,value=TCP

TCP exchange parameters

The following table lists the principal parameters that you define to enable Transfer CFT to generate and send event-related messages to Sentinel via TCP.

UCONF parameters for Sentinel interoperability

All platforms

The following table lists the UCONF values that are currently used in Transfer CFT to define Sentinel interoperability. You can set these UCONF values either in the GUI or by using a command line.

Communication with the Event Router

Z/OS environment

The following table describes the definition of communication with the Event Router via XCF. In this configuration:

• The XCF definition (queue=xxxx) is the XCF member name representing the ER server.
• The XCF group is PELISCOP by default. You can modify this default by setting queue = "member group"

Overflow file definition

Z/OS environment

The following table describes the overflow file definition for the Logger file. In this configuration:

• TRKSHAREDFILE=YES is MANDATORY when the logger file is shared between the ER and applications. Set this to NO if the applications are sending messages directly to the Sentinel server without going through an Event Router
• The log structure is ONLY used to define a logger file shared between the partitions of the SYSPLEX, and is NOT referenced in any parameters