Software Announcement 200-075
April 4, 2000

Preview: IBM MQSeries for OS/390, Version 2 Release 2

 ENUS200-075.PDF (16KB)


At a Glance

Improved availability, capacity, productivity, system management, and family consistency

  • High availability and high capacity through non-persistent messages in shared queues
  • Low-cost messaging within a sysplex through non-persistent shared queue messages
  • Easy system management within a sysplex
  • Improved operations:
    • Command to list applications with open handles on a specified queue
    • Faster restart with better handling of long-running units of work
  • Easier performance tuning and user charge back through more accounting and statistics data
  • Application programming productivity through the Application Messaging Interface (AMI) including easier working with MQSeries Integrator and MQSeries publish and subscribe
  • Improved consistency with the rest of the MQSeries family through the AMI, Unicode support, and support for 100 MB non-shared queue messages
  • Improved serviceability through better dump formatting

Overview

IBM intends to introduce MQSeries® for OS/390® V2.2 with new and improved function.

The headline item is shared queues for non-persistent messages of up to 63 KB stored in coupling facility list structures. Applications running on multiple queue managers in the same queue-sharing group anywhere in the Parallel Sysplex® can access the same shared queues for:

  • High availability
  • High capacity
  • Workload balancing.

You can set up different queue sharing groups to access different sets of shared queues.

You get easy system management of MQSeries resources within a queue-sharing group.

Other items in this release simplify MQSeries system management and operation for sysplex and non-sysplex users. The Application Messaging Interface (AMI) simplifies application development for MQSeries Integrator and MQSeries publish and subscribe, and support for 100 MB messages continues our drive for complete MQSeries family consistency across the platforms.

Note: The 100 MB message support in this release is also available via APAR PQ33000 on MQSeries for OS/390 Version 2 Release 1.

An Early Support Program will be open to a limited number of customers in second quarter 2000.

Intended Customers

  • Need to run MQSeries applications within a Parallel Sysplex for high availability or high capacity
  • Want low-cost messaging between applications within a Parallel Sysplex
  • Want improved system management and easier operation
  • Want to use the AMI to communicate with MQSeries Integrator and MQSeries publish and subscribe

Key Prerequisites

The following products or equivalents at the specified minimum levels:

  • OS/390 V2.6
  • Shared queues: OS/390 V2.9, coupling facility level 9 and DB2® 5.1
  • CICS applications: CICS/ESA® 4.1 or any level of CICS® Transaction Server (CTS)
  • IMS™ applications: IMS 5.1
  • DB2 applications: DB2 5.1
  • If you choose to use Interlink SNS/TCPaccess in place of IBM TCP/IP then you need V4.1
  • PL/I applications: AD/Cycle® PL/I for MVS™ and VM 1.1
  • COBOL applications:
    • IBM SAA AD/Cycle COBOL/370™
    • VS COBOL 2 V4
    • IBM COBOL for OS/390 and VM V2.1
    • IBM COBOL for MVS and VM V2.1

OS/390 includes appropriate levels of Language Environment®, TCP/IP, VTAM®, SMP/E, TSO/E, JES, C/C++, DFSMS™ / DFP, Security Server, High Level Assembler, ISPF, and ICSS.

Planned Availability Date

General availability, prices, ordering information, and terms and conditions will be provided when the product is announced.

Previews provide insight into IBM plans and direction.

Description

Availability and Capacity

All the shared queues stored in the same list structure can be accessed by applications running on any queue manager in the same queue-sharing group anywhere in the Parallel Sysplex. Each queue manager can be a member of a single queue-sharing group only.

This provides high availability, high capacity, and pull workload balancing. Work does not stop if an individual application instance or queue manager should fail or be recycled, as other instances of the same application accessing the same shared queues continue to do the work. Throughput is no longer constrained by the capability of a single queue manager, as multiple queue managers can access the same shared queues. Automatic pull workload balancing is achieved as the least constrained application instance will process the most messages.

MQSeries applications running on these queue managers can MQPUT and MQGET non-persistent messages of up to 63 KB to the same shared queues. Shared queue support for trigger first or trigger depth is based on committed messages only, and can start an application to run on any or every queue manager in the queue-sharing group for each trigger event. Shared queue support for trigger every is also based on committed messages only and can start an application to run on any queue manager in the queue-sharing group for each trigger event. If a queue manager fails, all queue managers in the same queue-sharing group will cooperate to recover its shared queue-related work.

Applications that work with local queues will generally work unchanged with shared queues, provided they use non-persistent messages of 63 KB or less. You may need to modify some applications to accommodate new shared queue-specific reason codes, and to change MQGET by MsgId or CorrelId to match the way the queue is indexed.

The MQSeries mover can exploit shared transmission queues and shared channel synchronization queues to enable a different mover to take over inbound and outbound channels from a failed mover. The MQSeries mover also supports a generic input port to provide session balancing for inbound channels.

Shared queue definitions and other control data reside in a DB2 data sharing database. Other MQSeries object definitions can also reside in that database to provide a single system image across a queue-sharing group. MQSeries resource names in security profiles can be qualified by a queue-sharing group name to provide a single system image for security.

Shared queues require list structure enhancements in coupling facility level 9 and OS/390 V2.9.

Easier Operation

You can use a new command to determine which applications have an open handle of a specified type on a specified generic queue name. The returned information identifies:

  • Queue name and handle TYPE
  • Queue manager name
  • Batch job or CICS region or IMS region
  • CICS or IMS transaction
  • Mover channel and connection

You can use this information to purge the offending application. You can also list all the address spaces connected to a queue manager together with a count of the user tasks currently using MQSeries from that address space.

Improved Operations and Faster Restart

This integrates support already delivered for the current release through the service channel. New messages warn you of incomplete units of work as log data sets are archived. Restart improvements let you immediately commit units of work that would otherwise require you to mount possibly lost archived log data sets and delay restart while MQSeries reads these data sets. Other restart improvements tell you how far restart has gone, and how much work remains.

Easier Performance Tuning and User Charge Back

Extra accounting data is cut at the end of each transaction and for long-running transactions at each statistics collection interval. This includes comprehensive data on a per queue and MQSeries request type basis. New shared queue statistics are also cut at each statistics collection interval.

Application Programming Productivity

You can use the new Application Messaging Interface (AMI). This high-level API for the MQSeries family includes verbs for the send and forget, request and response, and publish and subscribe communication styles. It removes complicated options from your applications, replacing them with references to new policy and service objects. These objects can also enforce standards and add value through functions like built in error handling. The AMI can communicate with other members of the MQSeries family, including MQSeries Integrator and MQSeries publish and subscribe.

Improved Consistency

In addition to the Application Messaging Interface this release includes data conversion support for Unicode UCS-2 and UTF-8 code pages and support for non-shared queue messages of up to 100 MB.

Improved Serviceability

This formats the key data for specified internal components in an easily understood way.

Early Support Program

An Early Support Program will be open to a limited number of customers in second quarter 2000. Contact your IBM representative and use the following URL to submit an application:

Year 2000

This product is Year 2000 ready. When used in accordance with its associated documentation, it is capable of correctly processing, providing, and/or receiving date data within and between the twentieth and twenty-first centuries, provided that all products (for example, hardware, software, and firmware) used with the product properly exchange accurate date data with it.

Customer Financing

IBM Global Financing offers attractive financing to credit-qualified commercial and government customers and Business Partners in more than 40 countries around the world. IBM Global Financing is provided by the IBM Credit Corporation in the United States. Offerings, rates, terms, and availability may vary by country. Contact your local IBM Global Financing organization. Country organizations are listed on the Web at:

Trademarks

 
IMS, MVS, COBOL/370, and DFSMS are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
MQSeries, OS/390, Parallel Sysplex, DB2, CICS, CICS/ESA, AD/Cycle, Language Environment, and VTAM are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Other company, product, and service names may be trademarks or service marks of others.