You are currently on IBM Systems Media’s archival website. Click here to view our new website.

MAINFRAME > Administrator > IMS

Extending the Power of IMS Connect


Earlier this year, IBM released a tool that allows users to increase the performance, availability and security of the connections between their e-business applications and IMS* databases. The tool-IMS Connect Extensions for z/OS*-is, as its name implies, a companion tool for IMS Connect for z/OS, IBM's high-performance TCP/IP server that connects TCP/IP clients and local z/OS applications to IMS, IBM's transaction and hierarchical database-management system.

IMS Connect Extensions provides a new level of control, enabling users to more easily monitor, manage, tune and secure IMS Connect for z/OS as it opens and closes TCP/IP sockets and routes transactions. Figure 1 shows an example configuration using IMS Connect Extensions.

The functions and services that IMS Connect Extensions makes available to IMS Connect users include (see Figure 2):

  • Event collection and reporting
  • Transaction routing
  • Workload balancing
  • Transaction pacing
  • Enhanced security management
  • Online command interface
  • Status Monitor

Event Collection and Reporting

IMS Connect Extensions monitors and records four categories of events related to TCP/IP-connections management, transactions processing and IMS Connect trace functions. For each event of a given type, IMS Connect Extensions creates an event record and stores that record in an active journal data set. Each event record contains an event number and details about the event. IMS Connect Extensions records the following types of events:

  • Connect status
  • Message related
  • Recorder trace
  • IMS Connect trace

A Connect-status event record identifies a change in the status of the IMS Connect system, such as the initialization and termination of the z/OS region in which Connect runs, the beginning and ending of accept-socket actions, changes in IMS datastore availability, and the opening and pre-closing of recorder-trace data control blocks (DCBs) on the OS.

A message-status event record identifies events related to processing incoming message requests, such as the beginning and ending of the close-socket action, the beginning and ending of a z/OS System Authorization Facility (SAF) request, the sending and receiving of messages to IMS Open Transaction Manager Access (OTMA), the entry and return from user message exits, the reading from and writing to sockets, and the timing out of OTMA. Both a recorder-trace event record and an IMS Connect-trace event record identify and capture selected events recorded by traces initiated from IMS Connect.

Ben Johnson is an IBM information developer. He has been writing about IMS since 2003, focusing on both IMS database administration and IMS communications and connections, with a particular interest in OTMA and IMS Connect. He can be contacted at bpj@us.ibm.com.

Jack Yuan is a senior software engineer for IMS development. He can be contacted at jackyuan@us.ibm.com



Advertisement

Advertisement

2019 Solutions Edition

A Comprehensive Online Buyer's Guide to Solutions, Services and Education.

Bringing IMS and SOA Together With IMS Connect

New requirements for IMS Connect functionality could make implementing an SOA environment with IMS easier and more flexible.

Celebrating 40 Successful Years

IMS version 10 supports synchronous and asynchronous callout

IBM Systems Magazine Subscribe Box Read Now Link Subscribe Now Link iPad App Google Play Store
Mainframe News Sign Up Today! Past News Letters