Administering IMS Connect Extensions definitions with the ISPF dialog

This section describes how to create IMS Connect Extensions repository definitions using the ISPF dialog.

To manage IMS Connect Extensions repository definitions, select option 1 Definitions on the primary menu of the IMS Connect Extensions ISPF dialog.
Figure 1. The Definitions panel in the IMS Connect Extensions ISPF dialog
  File  Menu  Help 
──────────────────────────────────────────────────────────────────────────────
                                 Definitions 
Option ===>                                                                   

1  System Definitions   Specify definitions for IMS Connect systems
2  User Exits           Specify User Message Exits
3  Datastores           Define datastore processing options
4  Datastore Groups     Group datastores for collective control
5  Affinity Lists       Associate datastores for Affinity processing
6  Applications         Group transactions for Application control
7  Transactions         Define transaction processing options
8  System Groups        Group IMS Connect systems for collective control
9  OTMA Routing Rules   Define rules for message routing
10 OTMA Routing Lists   Associate datastores for rules based routing
11 ODBM Targets         Define Open Database target systems
12 ODBM Routing Rules   Define rules for Open Database routing
13 ODBM Routing Lists   Associate Open Database targets for routing
14 PSB Name Lists       Specify a list of PSB names
15 Transaction Lists    Specify a list of transaction names
16 Routing Plans        Define routing plans to enable rules grouping
17 IP Address Rules     Define rules to assign attributes based on IP address
S  Definitions Setup    Tailor and run the definitions setup job

For each definition type there is typically a list panel, which lists existing definitions, and an edit panel, which you can use to specify the attributes of a new or existing definition.

Definitions for OTMA rules-based routing

OTMA rules-based routing in IMS Connect Extensions requires you to create one or more routing rules that depend on several supporting definitions. The structure of this relationship can be seen in the following diagram.
Figure 2. The structure of an OTMA routing rule in IMS Connect Extensions
OTMA routing rules defined in IMS Connect Extensions route messages destined for the IMS data store in the IRM_IMSDestId field in the IRM message to target and fallback destinations in an OTMA routing list containing one or more IMS data stores. OTMA routing rules apply to either an IMS Connect system or a group of systems and can be made conditional on an optional list of transactions. OTMA routing rules may belong to a routing plan.
The following minimum set of definitions are required to create an OTMA routing rule for a single IMS Connect system. Use the following sequence to create your definitions:
  1. IMS Connect system (option 1 System Definitions)
  2. IMS data stores (option 3 Datastores)
  3. OTMA routing list containing your IMS data stores (option 10 OTMA Routing Lists)
  4. OTMA routing rule referencing all of the above (option 9 OTMA Routing Rules)
The following definitions are optional and may be added later as required:
  • IMS Connect system group containing a collection of IMS Connect systems (option 8 System Groups)
  • Transaction list (option 15 Transaction Lists)
  • Routing plan (option 16 Routing Plans)
For more information, see OTMA workload routing in IMS Connect.

Definitions for ODBM rules-based routing

ODBM rules-based routing in IMS Connect Extensions requires you to create one or more routing rules that depend on several supporting definitions. The structure of this relationship can be seen in the following diagram.
Figure 3. The structure of an ODBM routing rule in IMS Connect Extensions
ODBM routing rules defined in IMS Connect Extensions route messages using the input alias name inside a DRDA request message to target and fallback destinations in an ODBM routing list containing one or more ODBM targets. ODBM routing rules apply to either an IMS Connect system or a group of systems and can be made conditional on an optional list of PSB names. ODBM routing rules may belong to a routing plan.
The following minimum set of definitions are required to create an ODBM routing rule for a single IMS Connect system. Use the following sequence to create your definitions:
  1. IMS Connect system (option 1 System Definitions)
  2. ODBM targets (option 11 ODBM Targets)
  3. ODBM routing list containing your ODBM targets (option 13 ODBM Routing Lists)
  4. ODBM routing rule referencing all of the above (option 12 ODBM Routing Rules)
The following definitions are optional and may be added later as required:
  • IMS Connect system group containing a collection of IMS Connect systems (option 8 System Groups)
  • PSB name list (option 14 PSB Name Lists)
  • Routing plan (option 16 Routing Plans)
For more information, see ODBM workload routing in IMS Connect.

Legacy OTMA routing methods

For customers who are using transaction routing and primary datastore routing, the following definitions apply. For more information, see Legacy OTMA routing methods.
Transaction routing
  • IMS Connect system (option 1 System Definitions)
  • IMS Connect system group containing a collection of IMS Connect systems (option 8 System Groups)
  • IMS data stores (option 3 Datastores)
  • IMS data store group (option 4 Datastore Groups)
  • Affinity List (option 5 Affinity Lists)
  • Applications (option 6 Applications)
  • Transactions (option 7 Transactions)
Primary datastore routing
For customers who are using the legacy primary datastore routing method, the following definitions apply.
  • IMS Connect system (option 1 System Definitions)
  • IMS Connect system group containing a collection of IMS Connect systems (option 8 System Groups)
  • IMS data stores (option 3 Datastores)
  • IMS data store group (option 4 Datastore Groups)
  • Affinity List (option 5 Affinity Lists)