IBM United States
Software Announcement 200-347
October 3, 2000
IBM MQSeries for OS/390 V5R2 Increases Your Messaging Availability and Bandwidth
At a Glance
Improved availability, capacity, productivity, system management and family consistency
For ordering, contact:
Your IBM representative, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL (Reference: LE001).
This new version of MQSeries® for OS/390® delivers new and improved function. As part of an ongoing harmonization process the Version and Release number have been aligned with the new MQSeries V5.2 distributed products announced today.
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 a Parallel Sysplex® can access the same shared queues for:
You can set-up different queue-sharing groups to access different sets of shared queues, for example, to separate test and production work.
You get easy system management of MQSeries resources within a queue-sharing group.
MQSeries system management and operation for sysplex and non-sysplex users is now easier.
The Application Messaging Interface (AMI) simplifies development of applications, especially those interfacing with MQSeries Integrator or MQSeries publish and subscribe.
Support for 100 MB messages and a rules-driven, dead-letter queue handler continues the drive toward MQSeries family consistency across the major platforms.
Note: 100 MB message support is also available via APAR PQ33000 on MQSeries for OS/390, V2R1.
MQSeries for OS/390, V5R2 is Advanced ClusterProven for S/390® and for the new zSeries 900 (z900).
For shared queues: OS/390, V2.9, coupling facility level 9 and DB2® 5.1
For a comprehensive list of prerequisites, refer to the Specified Operating Environment section.
Availability and Capacity
Multiple queue managers in the same queue-sharing group running anywhere in the same parallel sysplex can MQPUT and MQGET non-persistent messages of 63 KB or less to the same set of shared queues. Each queue manager can only be a member of a single queue-sharing group.
Work does not stop if an application or queue manager should fail or be recycled. 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. Multiple application instances on multiple queue managers can access the same shared queues and can thus do the same work. Pull workload balancing ensures that the most capable application instance processes the most messages.
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 peer recover its shared-queue-related work. Uncommitted messages will be quickly resolved and made available to other queue managers.
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.
You can use a new 128-byte application generated connection token to ensure that a single instance of an application is executing within a queue-sharing group or that all instances are executing within the same queue manager. This serialization is only released when the application finishes normally, or when recovery is completed if the application or queue manager fails.
The MQSeries mover exploits shared transmission queues and a shared channel synchronization queue. This enables a different mover to take over channels from a failed mover. The MQSeries mover also supports a generic input port to provide session balancing for inbound channels. These mover enhancements enable unchanged remote queue managers to work with a queue-sharing group as a whole, rather than with individual queue managers within that queue-sharing group.
You can use a new intra-group queuing mechanism to send non-persistent messages of 63 KB or less to another queue manager in the same queue-sharing group. This exploits a shared queue to avoid the system management and execution time costs of 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 and/or a queue manager name to provide flexible security control.
You can now determine which applications have an open handle of a specified type on a specified generic queue name.
You can identify:
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.
You can use a new rules-driven, dead-letter queue handler to automate
processing messages that could not be delivered to their target queues.
This periodically scans the dead-letter queue, matching data in each
message's headers against a user-defined rules table. When a match is
found, the associated action is taken. You can use this, for example, to
retry messages automatically when the mover fails to MQPUT to a target
queue that was temporarily disabled or full.
Improved Operations and Faster Restart
This integrates support already delivered 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 progressed, 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. Statistics for the new coupling facility and DB2 resource
managers are also cut at each statistics collection interval. This can
either be the current MQSeries specific interval or the system-wide SMF
Application Programming Productivity
The new AMI, a high-level API for the MQSeries family, includes verbs for
send and forget, request and response, and publish and subscribe
messaging styles. It removes complicated options from your applications,
replacing them with references to new policy and service objects. The
policy objects can enforce standards and also add value through functions
like built-in error handling. The AMI can be used in conjunction with
MQSeries publish and subscribe and with other family members including
In addition to the AMI, this release includes:
This product is Year 2000 ready.
The family of products based on IBM's industry-leading MQSeries software helps companies:
The MQSeries family allows companies to maximize e-business opportunities by:
The MQSeries family consists of five key components:
Hardware and Software Support Services
SmoothStart Service for MQSeries provides customers with planning
and installation services for MQSeries Solutions to ensure that their
MQSeries Commercial Messaging environment is quickly up and running.
Depending on customer requirements, an IBM specialist works with the
customer's technical and programming staff to increase productivity and
accelerate implementation of MQSeries licensed software.
Planning Services for MQSeries Solutions
IBM Planning Services for MQSeries Solutions is a customizable service
designed to help customers with a plan to implement an MQSeries Solution
within an organization. With this service, IBM can create the plan by
collecting the necessary business requirements and infrastructure
information, or can work with customer staff to customize and create the
MQSeries plan. In addition, IBM Planning Services MQSeries Solutions
assists in designing system network architecture, developing deployment
and application migration plans, and recovery planning of MQSeries
objects and data.
Design Services for MQSeries Applications
IBM Design Services for MQSeries Applications helps customers produce high- and low-level designs for your MQSeries applications including assistance in modifying or writing applications to take full advantage of your MQSeries environment. This offering is customizable and may include assistance in evaluating your test plans and making sure your applications perform effectively.
For further information visit:
For additional information related to new enhanced Support Line and associated services, refer to Services Announcement 699-026 , dated June 15, 1999.
For MQSeries® courses, visit:
Call IBM Education and Training at 800-IBM-TEACH (426-8322) for catalogs, schedules and enrollments.
MQSeries is a member of the International Middleware Association (IMWA) and the Electronic Messaging Association (EMA).
Specified Operating Environment
Any System/390® or IBM zSeries 900 (z900) processor capable of
running the required level of operating system and that has enough
storage to meet the combined requirements of the programming
prerequisites, MQSeries for OS/390®, the access methods, and the
Note that for software requirements, the Program Directory shipped with the product will normally contain the latest level of information, particularly concerning APAR/PTF levels of supported products.
The following products or equivalents at the specified minimum levels:
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.
The z900 requires the IBM License Use Management (LUM) tool for the Workload License Charge. A PTF will be made available to implement the LUM tool.
Compatibility: MQSeries for OS/390, V5R2 is upwardly compatible with programs written for MQSeries for MVS/ESA V1R2 and MQSeries for OS/390, V2R1. Regression testing is performed to ensure compatibility.
User Group Requirements:
This announcement satisfies or partially satisfies requirements from
one or more of the worldwide user group communities. Groups include
Australasian SHARE/GUIDE (ASG), COMMON, COMMON Europe, GUIDE
International, G.U.I.D.E. Europe, Japan GUIDE/SHARE (JGS), Guide Latin
American (LAG), SHARE EUROPE, and SHARE Incorporated.
MQSeries for OS/390, V5R2 on 9-track magnetic tape, 6250 bits per inch (bpi), 3480 1/2-inch tape cartridge or 4-mm DAT cartridge dependent on which feature number is selected.
One printed copy of each of the following books:
Order Title Number MQSeries for OS/390 License Program GC34-5893 Specification MQSeries for OS/390 Problem GC34-5892 Determination Guide MQSeries for OS/390 Messages and GC34-5891 Codes Order Title Number MQSeries Application Programming SC33-1673 Reference MQSeries Concepts and Planning Guide GC34-5650 MQSeries Application Programming Guide SC33-0807 MQSeries Programming Interfaces SX33-6095 Summary MQSeries Intercommunication SC33-1872 MQSeries MQSC Command Reference SC33-1369 MQSeries Clients GC33-1632 MQSeries Using C++ SC33-1877 MQSeries Queue Manager Clusters SC34-5349 Program Directory GI10-2532 MQSeries Application Messaging SC34-5604 Interface MQSeries Events Monitoring SC34-5760 MQSeries System Administration Guide SC34-5652 MQSeries System Setup Guide SC34-5651
A CD-ROM containing the above publications in Adobe Acrobat Portable Document Format (PDF) and HTML is separately orderable.
Optionally, if ordered, the Client Attachment feature on 9-track magnetic tape, 6250 bit per inch (bpi), 3480 1/2-inch tape cartridge or 4mm DAT cartridge dependent upon which feature number is selected.
One copy of the MQSeries Clients V5.1 CD-ROM is supplied with the Client Attachment feature.
Security, Auditability, and Control
The announced program uses the security and auditability features of the operating system software. The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.
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:
The following advance publication is available now from the MQSeries Web site:
Order Title Number MQSeries Concepts and Planning Guide GC34-5650
Orders for new licenses can be placed now.
Shipment will not occur before availability date.
New users of MQSeries for OS/390 should specify machine type/model 5655-F10.
MQSeries for OS/390, V5R2
ESL: To order an ESL license, specify the program number, feature number 9001 for asset registration, and the applicable ESL OTC feature number. Also specify the feature number of the desired distribution medium.
ESL OTC Feature Description Number MQSeries for OS/390, V5R2 (5655-F10) 0024 Client Attach Feature 0065
ESL machines can be determined by referring to the IBM Entry End User/390 Attachment (Z125-4379).
Parallel Sysplex® License Charge (PSLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the PSLC Base feature. If applicable, specify the PSLC Level A and PSLC Level B, and PSLC Level C, PSLC Level D features and quantity.
If there is more than one program copy in a Parallel Sysplex, the charge for all copies is associated to one license by specifying the applicable PSLC feature numbers and quantity represented by the sum of the Service Units in Millions (MSUs) in your Parallel Sysplex. For all other program copies, specify the PSLC No-Charge (NC) Identifier feature on the licenses.
Also, specify the feature number of the desired distribution medium.
PSLC PSLC Basic License Machine Feature MLC Feature MSU Capacity Number Description 1 0001 PSLC Base, 1 MSU 2 0002 PSLC Base, 2 MSUs 3 0003 PSLC Base, 3 MSUs 4 to 45 0004 PSLC Level A, 1 MSU 0005(1) PSLC Level A, 42 MSUs 46 to 175 0006 PSLC Level B, 1 MSU 0007(1) PSLC Level B, 10 MSUs 0008(1) PSLC Level B, 50 MSUs PSLC PSLC Basic License Machine Feature MLC Feature MSU Capacity Number Description 176 to 315 0009 PSLC Level C, 1 MSU 0010(1) PSLC Level C, 10 MSUs 0011(1) PSLC Level C, 50 MSUs 316 or more 0012 PSLC Level D, 1 MSU 0013 PSLC Level D, 50 MSUs NA 0014 PSLC NC IDENTIFIER
Variable Workload License Charge (WLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the WLC Base feature. If applicable, specify the WLC Level 1, WLC Level 2, WLC Level 3 and WLC Level 4 features with the appropriate quantity.
Also, specify the feature number of the desired distribution medium.
The Variable WLC requires the use of the IBM License Use Management (LUM) tool. A PTF will be made available to implement the LUM tool on MQSeries for OS/390, V5R2.
Variable WLC Aggregation: When z/OS is installed on two or more System/390 or z900 machines comprising a sysplex, Variable WLC aggregation applies to z/OS and the S/390® software programs which have Variable WLC.
Whether there is only one or more than one license of the program in the sysplex, the charge for all licenses is associated to the "aggregation license" by specifying the applicable WLC feature numbers and quantity represented by the sum of the MSUs (millions of service units) in the sysplex. The "aggregation license" is an additional program license which is ordered and serialized, although there is no shipment associated with it.
For the actual licenses, the charge is reflected as $0.00 by specifying the applicable "registration" Variable WLC feature numbers and the quantity equal to the MSUs of that license running on the designated machine.
For MQSeries for OS/390, V5R2 (5655-F10), the Variable WLC feature numbers are as follows:
WLC Feature WLC Basic License MLC MSU Capacity Number Feature Description 0 to 45 0028 WLC Base, 45 MSU 46 to 175 0029 WLC L1, 1 MSU 176 to 315 0032 WLC L2, 1 MSU 316 to 575 0034 WLC L3, 1 MSU 0036 WLC L3, 50 MSU 576 or more 0038 WLC L4, 1 MSU 0040 WLC L4, 50 MSU
WLC Reg WLC Basic License Feature No-Charge Registration MSU Capacity Number Feature Description 0 to 1 0030 WLC Base, 1 MSU Reg 2 to 175 0031 WLC L1, 1 MSU Reg 176 to 315 0033 WLC L2, 1 MSU Reg 316 to 575 0035 WLC L3, 1 MSU Reg 0037 WLC L3, 50 MSU Reg 576 or more 0039 WLC L4, 1 MSU Reg 0041 WLC L4, 50 MSU Reg
Example 2: If there are 2 machines in a sysplex, and a program is running on machine #1 at 190 MSUs and on machine #2 at 140 MSUs, the Variable WLC feature numbers and quantities to be ordered would be:
S/390 Usage Pricing (Usage License Charge) Basic License: To order a basic license, specify the appropriate program and feature number, if required, for asset registration. Specify the applicable S390 Usage Pricing feature. Also, specify the feature number of the desired distribution medium.
Charges will be based upon the Peak MSUs. Usage reported between thresholds of features 1, 2, or 3, will be rounded up to the next MSU level. Above 1.0 MSU, usage will be rounded to the nearest whole MSU. For example, 2.4 MSUs would round to 2.0 MSUs for pricing, and 2.5 MSUs would round to 3.0 MSUs for pricing.
Pricing will be determined by selecting either:
Usage Pricing Feature Description Number 0 to 0.25 MSU Base 0015 0.26 to 0.5 MSU Base 0016 0.51 to 1.0 MSU Base 0017 Level A Chg/MSU (2 to 11 MSUs) 0018 Level B Chg/MSU (12 to 44 MSUs) 0019 Level C Chg/MSU (45 to 78 MSUs) 0020 Level D Chg/MSU (Above 78 MSUs) 0021 Level D Chg/MSU Per 50 MSUs for 0022 machine capacity of 79 or more MSUs N/C ID Feature 0023
Examples for ordering:
Client Attachment Feature
Usage Pricing Feature Description Number 0 to 0.25 MSU Base 0056 0.26 to 0.5 MSU Base 0057 0.51 to 1.0 MSU Base 0058 Level A Chg/MSU (2 to 11 MSUs) 0059 Level B Chg/MSU (12 to 44 MSUs) 0060 Level C Chg/MSU (45 to 78 MSUs) 0061 Level D Chg/MSU (Above 78 MSUs) 0062 Level D Chg/MSU Per 50 MSUs for 0063 machine capacity of 79 or more MSUs N/C ID Feature 0064
PSLC PSLC Basic License Machine Feature MLC Feature MSU Capacity Number Description 1 0042 PSLC Base, 1 MSU 2 0043 PSLC Base, 2 MSUs 3 0044 PSLC Base, 3 MSUs 4 to 45 0045 PSLC Level A, 1 MSU 0046(1) PSLC Level A, 42 MSUs 46 to 175 0047 PSLC Level B, 1 MSU 0048(1) PSLC Level B, 10 MSUs 0049(1) PSLC Level B, 50 MSUs 176 to 315 0050 PSLC Level C, 1 MSU 0051(1) PSLC Level C, 10 MSUs 0052(1) PSLC Level C, 50 MSUs 316 or more 0053 PSLC Level D, 1 MSU 0054 PSLC Level D, 50 MSUs NA 0055 PSLC NC IDENTIFIER
WLC Feature WLC Basic License MLC MSU Capacity Number Feature Description 0 to 45 0069 WLC Base, 45 MSU 46 to 175 0070 WLC L1, 1 MSU 176 to 315 0073 WLC L2, 1 MSU 316 to 575 0075 WLC L3, 1 MSU 0077 WLC L3, 50 MSU 576 or more 0079 WLC L4, 1 MSU 0081 WLC L4, 50 MSU
WLC Reg WLC Basic License Feature No-Charge Registration MSU Capacity Number Feature Description 0 to 1 0071 WLC Base, 1 MSU Reg 2 to 175 0072 WLC L1, 1 MSU Reg 176 to 315 0074 WLC L2, 1 MSU Reg 316 to 575 0076 WLC L3, 1 MSU Reg 0078 WLC L3, 50 MSU Reg 576 or more 0080 WLC L4, 1 MSU Reg 0082 WLC L4, 50 MSU Reg
Growth Opportunity License Charge (GOLC): To order a GOLC software, specify the program number, feature number 9001 for asset registration, and the GOLC monthly charge feature number from the table below. Also, specify the feature number for the desired distribution medium.
GOLC GOLC Feature Category Number H30 0025 H50 0026 H70 0027
Client Attach Feature
GOLC GOLC Feature Category Number H30 0066 H50 0067 H70 0068
Single-Version Charging: To elect single-version charging, the customer must notify and identify to IBM the prior program and replacement program and the designated machine the programs are operating on.
The machine-readable material shipped on the distribution media is common to all languages shipped, and includes messages translated to Japanese and Simplified Chinese. Different distribution medium feature numbers are provided by language, but this is only because they cause the appropriate translated hardcopy publications to be shipped with the product tape.
Feature Distribution Medium Number OS/390 Magnetic Tape 9-track 6250-bpi 5811 3480 1/2-inch Tape Cartridge 5812 4-mm DAT Cartridge 6147
Basic Machine-Readable Material with Translated Publications: For an order with hard-copy publications in Japanese (Kanji), select the feature number of the desired distribution medium below, instead of the base feature number:
Feature Distribution Medium Number OS/390 Magnetic Tape 9-track 6250-bpi, with 5801 Japanese publications 3480 1/2-inch Tape Cartridge, with 5802 Japanese publications 4-mm DAT Cartridge, with Japanese 6148 publications
No translated publications in Simplified Chinese are provided for MQSeries for OS/390, V5R2 so there are no Simplified Chinese distribution media feature numbers.
Example: If publications are not desired for the initial order, specify feature number 3470 to ship media only. For future updates, specify feature number 3480 to ship media updates only. If, in the future, publication updates are required, order an MES to remove feature number 3480; then, the publications will ship with the next release of the program.
Feature Description Number Initial Shipments Serial number only (suppresses shipment 3444 of media and documentation) Ship media only (suppresses initial 3470 shipment of documentation) Ship documentation only (suppresses 3471 initial shipment of media) Single Pallet delivery 3483 Update Shipments Ship Media updates only (suppresses 3480 update shipment of documentation) Ship documentation only (suppresses 3481 update shipment of media) Suppress updates (suppresses update 3482 shipment of media and documentation) Expedite Shipments Local IBM office expedite 3445 (for IBM use only) Customer expedite process charge 3446 ($30 charge for each product)
Expedite shipments will be processed to receive 72-hour delivery from the time IBM Software Delivery and Fulfillment (SDF) receives the order. SDF will then ship the order via overnight air transportation.
Feature Description Number OS/390 Magnetic Tape 9-track 6250-bpi 5821 3480 1/2-inch Tape Cartridge 5822 4-mm DAT Cartridge 6149
Order Title Number MQSeries for OS/390 License Program GC34-5893 Specification MQSeries for OS/390 Problem GC34-5892 Determination Guide MQSeries for OS/390 Messages and Codes GC34-5891 MQSeries Application Programming SC33-1673 Reference MQSeries Concepts and Planning Guide GC34-5650 MQSeries Application Programming Guide SC33-0807 MQSeries Programming Interfaces SX33-6095 Reference Summary MQSeries Intercommunication SC33-1872 MQSeries MQSC Command Reference SC33-1369 MQSeries Clients GC33-1632 MQSeries Using C++ SC33-1877 MQSeries Queue Manager Clusters SC34-5349 Program Directory GI10-2532 MQSeries Application Messaging SC34-5604 Interface MQSeries Events Monitoring SC34-5760 MQSeries System Administration Guide SC34-5652 MQSeries System Setup Guide SC34-5651
Unlicensed Publications in Softcopy
Product Kit: One copy of the MQSeries for OS/390 specific publications Product Kit on CD-ROM (SK3T-6897) will be shipped free of charge with this product if feature number 7099 is specified in the order.
Collection Kit for Transaction Processing and Data products: One copy of the Collection Kit for Transaction Processing and Data products CD-ROM (SK2T-0730) will be shipped free of charge with this product if feature number 7132 is specified in the order.
Subsequent updates (technical newsletters or revisions between releases) to the publications shipped with the product will be distributed to the user of record for as long as a license for this software remains in effect. A separate publication order or subscription is not needed.
The following publications are translated:
Order Title Number Language: English MQSeries for OS/390 License Program GC34-5893 Specification Language: Japanese MQSeries for OS/390 Problem GC88-8846 Determination Guide MQSeries for OS/390 Messages and Codes GC88-8845 MQSeries Application Programming SC88-7354 Reference MQSeries Concepts and Planning Guide GC88-8615 MQSeries Application Programming Guide SC88-7253 Language: English MQSeries Programming Interfaces SX33-6095 Reference Summary Order Title Number Language: Japanese MQSeries Intercommunication SC88-7775 MQSeries MQSC Command Reference SC88-7315 MQSeries Clients GC88-7495 MQSeries Using C++ SC88-7778 MQSeries Queue Manager Clusters SD88-7165 Language: English Program Directory GI10-2532 MQSeries Application Messaging SC88-8704 Interface MQSeries Events Monitoring SC88-8705 MQSeries System Administration Guide SC88-8617 MQSeries System Setup Guide GC88-8616
Terms and Conditions
Single Version Replacement Charging Replaced Programs Programs Applies MQSeries MQSeries Yes for OS/390, for OS/390, V2R1 (5655-A95) V5R2 (5655-F10) MQSeries To a follow-on, N/A for OS/390, if any V5R2 (5655-F10)
Use Priority/Reference Code: LE001 Phone: 800-IBM-CALL Fax: 800-2IBM-FAX Internet: firstname.lastname@example.org Mail: IBM Atlanta Sales Center Dept. LE001 P.O. Box 2690 Atlanta, GA 30301-2690
You can also contact your local IBM Business Partner or IBM representative. To identify them, call 800-IBM-4YOU.
Note: Shipments will begin after the planned availability date.