JR58698: ENHANCEMENT TO SUPPORT DTS IN MQ CLIENT MODE IN NON-XA ENVIRONMENT FOR ORACLE AND MQ CONNECTOR TARGETS

IBM InfoSphere Information Server, Version 11.7.1.1 (Fix Pack 1)
IBM InfoSphere Information Server, Version 11.7.1.1 for AIX
IBM InfoSphere Information Server, Version 11.7.1.1 for Windows
IBM InfoSphere Information Server, Version 11.7.1.1 for Linux
Download IBM InfoSphere Information Server, Version 11.7.1.3
IBM InfoSphere Information Server, Version 11.7.1.3 for AIX
IBM InfoSphere Information Server, Version 11.7.1.3 for Windows
IBM InfoSphere Information Server, Version 11.7.1.3 for Linux
Download the mod pack for IBM InfoSphere Information Server 11.7.1.0 In-Place Upgrade

APAR status

• Closed as new function.

Error description

• Enhance DTS stage to support MQ Client mode in addition to
  server mode.
  The MQ Server and Client mode cannot be mixed and matched for
  the links.
  Use case:
  Not all customer applications using InfoSphere DataStage have
  local Queue Manager available on their server. This limits usage
  of DTS. DTS enhancement will allow access to the remote Queue
  Manager which significantly can reduce application design
  complexity.
  Only the Oracle Connector and the MQ Connector flavors of the
  DTS target will support Client mode.
  

Local fix

• Use Server mode.
  

Problem summary

• This APAR is an enhancement to the Distributed Transaction Stage
  (DTS) which adds support for the MQSeries Client mode in a
  non-XA environment for Oracle Connector and MQ Connector
  targets. Changes include, but are not limited to the following:
  > The DTS Stage Properties tab
  - When "Global transaction" is disabled, a new property called
  "Mode" is enabled in the Connection properties section. Either
  Client or Server mode may be selected.
  - When Server mode is selected, the DTS performs the same as
  before.
  - When Client mode is selected, additional properties are
  enabled. The job designer must now specify the "Client channel
  definition". The Client channel definition comprises the
  "Channel name", the "Transport type" and the "Connection name".
  Only the TCP Transport type is supported.
  > The DTS Input link Properties
  The DTS supports multiple input links where the link types
  (e.g., Oracle Connector and MQ Connector) can be mixed types.
  >> Input link Properties tab for MQ Connector
  Similar to the Stage properties tab, when "Global transaction"
  is disabled, a new property called "Mode" is enabled in the
  Connection properties section. Either Client or Server mode may
  be selected. The Mode selected on the MQ Connector page must
  match the mode selected on the Stage properties page. Otherwise,
  a runtime error with occur. Each MQ Connector link may have
  different specifications for the Client channel definition. In
  fact, MQ Connector DTS targets each need their own connection to
  be specified, independent of the stage.
  >> Input link Properties tab for Oracle Connector, ODBC
  Connector and Teradata Connector.
  There are no changes to the stage editor for these types of
  input links. Oracle Connector links can participate in Client
  mode of a non-XA environment. No changes for ODBC Connector and
  Teradata Connector types were implemented.
  

Problem conclusion

• MQSeries Client Connection mode is now supported for the
  Distributed Transaction Stage, with additional functionality for
  Oracle Connector and MQ Connector.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• RB50 PSY

     UP

• RB70 PSY

     UP