Starting Your Product › Configuring Runtime: IMS and CICS › Establish Client/Server Support › Customize Middleware › Customize for TCP/IP › IMS

IMS

The TCP/IP Direct Connect option of CA Gen for IMS runtime is included in the Pax file as option IMS TCP/IP DC.

Each User Message Exit consists of Assembler Language modules that are installed, using MSM or SAMPJCL, into the CEG9PLD1 dataset.

Gen provides a different User Message Exit for each version of IMS Connect supported, namely v10, v11, v12 and v13. These user message exits are delivered with name TIR##TCP, where ## is the IMS Connect version number.

Each TIR##TCP exit can be customized using one of three exits. The user message exits are supplied as object code only while the customizable exits are supplied as source code and object load modules with default behavior. Refer to the comments in the exits themselves for information about the default behavior and how to modify them. If the exits are modified, the relevant user message exit must be relinked to include the modifications. Once relinked the user message exit must be renamed from TIR##TCP to CAGRITCP as this is the name specified by Gen clients when connecting to IMS Connect.

Making a change to the three exits requires:

• Re-assembling and re-linking the TIR##XXX exit(s), where ## is the required version and XXX is the specific exit name
• Relinking the TIR##TCP user message exit
• Renaming the TIR##TCP exit to CAGRITCP
• Copying relinked CAGRITCP user message exit to the SDFSRESL library
• Stopping and restarting IMS Connect

For more information, see the instructions in the exits source code.

The IMS Connect user message exit can use IPv4 or IPv6 sockets protocol.

To use the IMS Connect user message exit TIR##TCP/CAGRITCP, configure IMS Connect to include the exit name. For information about setting up and customizing IMS Connect, see the IMS Connect User's Guide in the IBM documentation set. Add the user message exit name CAGRITCP to the TCPIP statement's IMS Connect EXIT parameter.

IPv4 Example

HWS (ID=……)
TCPIP (HOSTENAME=<IPV4 TCP/IP Stack name>
   EXIT=(HWSSMPL0,CAGRITCP))
DATASTORE  (ID=....,GROUP=IMSXCF,MEMBER=....,
TMEMBER=IMSA,DRU=...)

IPv6 configuration Example

HWS (ID=……)
TCPIP (HOSTENAME=<IPV6 TCP/IP Stack name>,…
  EXIT=(HWSSMPL0,CAGRITCP),IPV6=Y)
DATASTORE  (ID=....,GROUP=IMSXCF,MEMBER=....,
TMEMBER=IMSA,DRU=...)

Configure the IMS control region to use OTMA.

Note: For more information, see the IMS documentation, especially the Install Volume 2: System Definition and Tailoring.

For example:

…..
OTMA=Y,
GRNAME=IMSXCF,
OTMAMN=IMSA,
….

Where:

• GRNAME-Matches the name specified in the GROUP parameter of the IMS Connect DATASTORE statement.
• OTMANM-Matches the name specified in the TMEMBER parameter of the IMS Connect DATASTORE statement.