Affinity fields


Affinities can be defined for any messages that have unique processing characteristics.

These affinities are used by the Affinity Manager component in selecting the datastores that can process the message. The affinity fields in the following table are used to add/define affinities to Energizer:

Field

Description

Affinity Type

Specifies one of the following resource association types to an affinity:

  • DEST - Datastore (one of the defined datastores)
  • CLIENT - IMS Connect Client
  • TRAN - IMS Transaction Code (specific or generic)
  • USER - RACF (or equivalent) User ID
  • GROUP - RACF (or equivalent) Group name
  • STRING - Message ID String (requires Value Type which Specifies whether Value is a readable 1-8 EBCDIC string, a readable 1-8 ASCII string, or a 2-16 hexadecimal string.)
  • PORT - TCP/IP Port Number (the one assigned to IMS Connect)

Value

Specifies one of the following values that are associated with the affinity type:

  • Datastore - enter the datastore in the message or 1- to 7-characters ending with an asterisk (*), indicating a generic datastore name
  • IMS Connect Client - enter the 1- to 8-byte client name
  • IMS Transaction Code - enter a fully-qualified transaction name or 1- to 7-characters ending with an asterisk (*), indicating a generic transaction name
  • RACF (or equivalent) User ID - enter the 1- to 8-character RACF (or equivalent) User ID
  • RACF (or equivalent) Group Name - enter the 1- to 8-character RACF (or equivalent) group name
  • Message ID - enter the 1- to 8-character message ID
  • TCP/IP Port Number- enter the port number that received the message

Value Type

Applies only to STRING - Message ID transaction types

The field is used to specify whether Value should be interpreted as a readable 1-8 EBCDIC string, a readable 1-8 ASCII string, or a 2-16 hexadecimal string

Active

Specifies whether this affinity is Active or Inactive

The default is Active. The Affinity Manager ignores inactive affinities.

Data Offset 1

(Numeric) Specifies the offset within the message data, which further qualifies an affinity

If this field is specified, the Data Operator 1 and Data Value 1 must also be specified.

Data Operator 1

Specifies which operator to use when comparing the message data (Data Offset 1 data) to the Data Value 1

If the Data Offset 1 field is specified, this field must be specified. Valid operators are as follows:

  • EQ - equal
  • NE - not equal
  • GE - greater than or equal
  • GT - greater than
  • LT - less than
  • LE - less than or equal

Data Value 1

Specifies an actual data value to use for the comparison against the Data Offset 1 message data value

If the Data Offset 1 field is specified, this field must be specified.

Data Value Type 1

Applies only to STRING - Message ID affinity types

Specifies whether Data Value 1 should be interpreted as a readable 1-8 EBCDIC string, a readable 1-8 ASCII string, or a 2-16 hexadecimal string

Data Operator

Specifies which logical operator to use when the two qualifying values are specified

Data Offset 2

(Numeric) Specifies the offset within the message data, which further qualifies an affinity

If this field is specified, the Data Operator 2, and Data Value 2 must be specified.

Data Operator 2

Specifies the operator to use when comparing the message data (Data Offset 2 data) with the Data Value 2

Valid operators are as follows:

  • EQ - equal
  • NE - not equal
  • GE - greater than or equal
  • GT - greater than
  • LT - less than
  • LE - less than or equal

If the Data Offset 2 field is specified, this field must be specified.

Data Value 2

Specifies the actual data value to use for the comparison against the Data Offset 2 message data value

If the Data Offset 2 field is specified, this field must be specified.

Data Value Type 2

Applies only to STRING - Message ID affinity types

Specifies whether Data Value 2 should be interpreted as a readable 1-8 EBCDIC string, a readable 1-8 ASCII string, or a 2-16 hexadecimal string

Destinations

Specifies the assigned affinity destination(s)

The destination must be one or more datastores that are defined to the DataStore Router.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*