WebSphere MQ for z/OS V7.0.1 migration and installation--important information including highlights of new function

This document includes the following sections:

Maintenance
Installation
Migration
Configuration
New Function
Highlights of new function


Problems and solutions when migrating to WebSphere MQ for z/OS v7.0.1 contains more details of migration and fallback procedures, limitations, and restrictions plus some symptoms associated with common issues.

Technote 1312983 contains comparable information for WebSphere MQ for z/OS 7.0.0. If you are migrating from WebSphere MQ for z/OS 6.0.0, see the New Function information and subsequent highlights in that item.

Technote 1596103 contains comparable information for WebSphere MQ for z/OS 7.1.0.

See Webcast replay: WebSphere MQ for z/OS V7.0.1 - Installation, Migration, New Functions and Common Problems

View documentation in the Information Center in the WebSphere MQ Library. In the Information Center, see instructions for navigating and searching.

The Portable Document Format (PDF) versions of WebSphere MQ (WMQ) documentation are no longer being maintained, except for the Program Directory. Additional information about creating and printing WMQ PDF material is in technote 1460172. WebSphere MQ manuals are not available in BookManager format.

Maintenance

• Review migration-related maintenance for fallback and coexistence. The list includes fixes for the releases being migrated from and to.
• Plan to apply the current V7.0.1 PTFs. The complete list of V7.0.1 maintenance identifies HIPER (High Impact or Pervasive) and PE (Program Error) fixes along with all other available PTFs.
• Review II14556 if you are using WebSphere Application Server (WAS) and/or RRS applications.
• See Cross Product Dependencies and other information in the PSP bucket.
• Order the WebSphere MQ product and maintenance. See ShopzSeries or Buying Options if you do not already have the product.

Installation

• No matter what kind of product delivery packaging you use, see the WebSphere MQ for z/OS Version 7.0.1 Program Directory (GI13-0529-01) and the WebSphere MQ for z/OS Version 7.0.1 System Setup Guide. Among other things, the Program Directory shows the SMP/E statements that should be used.
• The Program Directory lists a new optional LINK job, CSQ8SLDQ, to enable automatic relinking after service is applied to Language Environment, TCP/IP, or OS/390 callable services (APPC and RRS). Apply the fix from PM06599 for this job or implement the circumvention described in the APAR.
• Always use the highest level of early code, as stated in Configuration Task 3 in the WebSphere MQ for z/OS System Setup Guide.
  
  

Migration

• Explore subtopics of Migrating WebSphere MQ (significantly updated in early 2012) in the WebSphere MQ Version 7.0.1 Information Center, including:
  - Upgrade, migration, and maintenance of WebSphere MQ on z/OS
  - Where to find a topic about a specific migration path
  Take note of special situations such as
  - queue manager clusters
  - queue-sharing groups (QSG)
  - client-connection and server-connection channels
  - JMS exception listeners
  - Compatibility, coexistence, and interoperability
  - List of changes by version, release, and maintenance level -- Changes, depending on whether you are migrating from 6.0.0 and 7.0.0, are listed, for example:
  - Client Changes
  - Data type version changes
  - JMS and Java changes
  - MQI return code changes
  - MQRFH2 migration, message properties, and property folders
  - Publish/Subscribe changes
  - Version 6 functions with preferred version 7.0.1 alternatives
  - z/OS: OPMODE
  - z/OS: Resolving transactions in a queue-sharing group
  - z/OS: Recompile Batch programs that use z/OS language environment
  - z/OS: Sysplex parm scope
  - z/OS: CSQINP1 and CSQINP2 changed
  - z/OS: DB2 plan names
  - z/OS: Client Attachment Feature
  - z/OS: 64-bit storage
  
  
• Review documentation updates, including:
  PK98278 Documentation update for 701 migration
  PM01980 Using Java manual needs correction for JVM support
  PM03381 The OPMODE value displayed under different circumstances is clarified in the documentation

• Backward migration
  See the document Problems and solutions when migrating to WebSphere MQ for z/OS v7.0.1. It contains details of backward migration maintenance, procedures, limitations, and restrictions plus some symptoms associated with common issues.
  
  
  For releases earlier than Version 6.0, no backward migration support from Version 7.0 is provided. Because there is no good fall-back capability other than returning to matching back-ups of page sets, BSDSs and logs, this is not a good practice for production systems. It might be sufficient for a test queue manager.
  
  
  
• MQ Explorer considerations
  If you use the MQ Explorer to administer your z/OS queue manager then after migration between releases, actions must be performed to ensure that the MQ Explorer's cached view of the queue manager attributes, including the command level, are correctly refreshed after the migration.
  
  
• Compatibility of SCSQnnnn libraries
  - See technote 1457146.
  - CICS Transaction Server APARs PM10011 and PM12034 say:
  "If you have WebSphere MQ Version 7 installed and you have applied the PTF for APAR PK66866/PK89844, then it is important that you ensure that your CICS STEPLIB concatenation only includes the WebSphere MQ Version 7 SCSQAUTH.
  All modules in WebSphere MQ Version 7 SCSQAUTH are downwardly compatible."
  
  
• More granular MULC recording, provided by PK73461 as serviceparm bit '00000000 10' is replaced in V7.0.1 by the MULCCAPT=REFINED system parameter.
• XA client users connecting to a Queue Sharing Group (QSG) should review technote 1449050.
  
  

Configuration

• In the System Setup Guide, focus on Customizing your queue managers.
• CSQINP1 and CSQINP2 input data sets changed from V6.0. Some Sample definitions supplied with WebSphere MQ have additional object definitions. You will need to change the order of the CSQINP2 data sets as shown in CSQ4MSTR of SCSQPROC. CSQ4INYS and CSQ4INSG are reordered, and CSQ4INSR is new. This is primarily true if you plan to use publish/subscribe, but it would be advisable to update the order of data sets now so you will not have to remember to do it in the future.
• Set MEMLIMIT as described in Exploiting 64-bit storage. The queue manager must be allowed to access storage above the bar.
  
• Review the PSMODE queue manager attribute, which controls whether WebSphere MQ Version 7.0 publish/subscribe and the queued publish/subscribe interface that enables previous publish/subscribe engines to coexist with WebSphere MQ Version 7.0 is running, and hence enables applications to publish/subscribe using the MQI and the queues being monitored by the queued publish/subscribe interface respectively.
  
  While PSMODE(ENABLED) is the default initial value, PSMODE(COMPAT) is used if the QMGR object is migrated from an earlier version.
• PROVIDERVERSION=6 is not required like it was at V7.0.0. See
  - Information about using WebSphere MQ as the JMS Provider for WebSphere Application Server Version 6.1
  - Information about using the WebSphere MQ messaging provider for WebSphere Application Server Version 7.0
  
  

New Function

• Review new function provided in WebSphere MQ for z/OS 7.0.0.
• Major areas of new function in WebSphere MQ for z/OS 7.0.1 include:
  • Use of 64-bit storage for some objects
  • Log compression
  • The new OPMODE property to control new functionality and backward migration
  • Admin structure recovery
  • Generic Application Structure Backup
  • Transaction recovery within a queue-sharing group
  • The option for batch and USS applications to use the z/OS XPLINK, which is a high performance calling interface
  • The option for automatic client reconnection after a queue manager or network failure
  • Support for IMS applications to use the WebSphere MQ message property APIs so that IMS applications can communicate with JMS applications.
  • Support for message selectors on MQOPEN
  • The CSQUMGMB utility to migrate the publish/subscribe configuration data from WebSphere Event Broker
    
• See the Highlights section below for further details of these and other areas of new function.
  
• For additional information relating to WebSphere MQ V7 changes, see
  • SupportPac MP1G: WebSphere MQ for z/OS V7.0.1 Performance Report
  • WebSphere MQ V7.0.1 announcement letter (209-248)

Highlights of new function

• Use of 64-bit storage for some objects
  In V7.0.0, the new pubsub features started to exploit 64bit storage.
  In V7.0.1, additional control blocks moved above the bar, for example locks and queue indexes.
  Set MEMLIMIT as described in Exploiting 64-bit storage.
• Log compression
  This can be used to reduce the amount of data written to the log for persistent messages on private queues. See benefits, costs, and options in the Log Compression topic. Availability of this function is controlled by the new OPMODE property.
• The new OPMODE property
  OPMODE = (Mode, VerificationLevel) is an option in CSQ6SYSP to control new functionality and backward migration. The default is OPMODE=(COMPAT,701).
  COMPAT
  The queue manager runs in compatibility mode. Certain new functions are not available (log compression and group unit of recovery). The queue manager can be migrated back to an earlier release.
  NEWFUNC
  All new functions provided in this level of code are available. The queue manager cannot be migrated back to an earlier release. If you find an issue in the new functions, you can switch off the new functions by using OPMODE=(COMPAT,701) but will not be able to revert to a previous version.
  VerificationLevel
  The format is "vrm" (version, release, modification level) and must match the level of the CSQ6SYSP macro being compiled.
• Admin structure recovery
  At WebSphere MQ Version 7.0.1 and later, the first queue manager started can rebuild the admin structure partitions for other members of the queue sharing group as well as its own, and it is no longer necessary to restart each queue manager in the queue sharing group at this stage. See Recovering a queue-sharing group at the alternative site.
• Generic Application Structure Backup
  The BACKUP CFSTRUCT command will now allow a generic structure name.
• Transaction recovery within a queue-sharing group, or GROUP unit of recovery disposition
  - In previous releases, all Units of Work (UOWs) are owned by an individual queue manager.
  V7.0.1 adds support for a UOW to be owned by the QSG. This capability is required for support of 2-phase commit resolution while connected to the QSG. It therefore enables WebSphere MQ Extended Transactional Clients to connect to other queue managers in a queue sharing group to continue processing their unit of recovery.
  - See:
  - Enabling GROUP units of recovery - this includes
  - defining a recoverable application structure called CSQSYSAPPL,
  - defining a shared queue called SYSTEM.QSG.UR.RESOLUTION.QUEUE
  - setting the GROUPUR queue manager attribute
  - Application support for GROUP units of work
  - All queue managers in the group need to have OPMODE=NEWFUNC for this function to be available. Once NEWFUNC has been used, the queue manager can not be reverted to a prior release.
  - See technote 1449050.
• The option for batch and USS applications to use z/OS XPLINK, which is a high performance calling interface available for C applications. It uses dynamic link libraries (DLLs).
• The option for automatic client reconnection after a queue manager or network failure. It allows the client application to continue processing without having to issue an MQCONN or MQCONNX MQI call to reconnect to the queue manager.
  - See Automatic client reconnection for details of application suitability and how to configure it.
  - See the Automatic Client Reconnection section of the Webcast WebSphere MQ V7.0 Client Enhancements.
• Support for IMS applications to use the WebSphere MQ message property APIs so that IMS applications can communicate with JMS applications.
• Support for message selectors on MQOPEN using the SelectionString field in the MQOD structure. This allows for point-to-point selectors and removes the need to use PROVIDERVERSION=6.
• The migrate publish/subscribe configuration utility (CSQUMGMB)
  The CSQUMGMB utility migrates the publish/subscribe configuration data from WebSphere Event Broker Version 6.0 or WebSphere Message Broker Version 6.0 or 6.1 to WebSphere MQ Version 7.0.1 and later versions. Sample JCL CSQ4MGMB is provided in SCSQPROC.
• JVM: PM01980 contains a documentation update to say that on z/OS, you can use either a 31-bit or 64-bit Java virtual machine (JVM).
• Page Set Usage with Small Messages:
  - As stated in SupportPac MP1G, to allow the scavenger to work more efficiently with small messages, each message is now stored in a separate 4K page. Prior to version 7.0.1, small messages were stored such that multiple messages could co-exist on the same page.
  - The change will have a positive effect in most cases but could increase the size requirements for your page sets and buffer pools, depending on workload patterns. You may see CSQP014E or CSQP020E after migration. You may notice an increase in SMF field QPSTGETN because it represents the number of MQGET requests for a new (or empty) page. Performance for MQPUT and MQGET will degrade if there are more messages on the queue than will now fit in the BUFFPOOL. A tuning attribute, MAXSHORTMSGS, can be used under the direction of IBM Service to use the pre-7.0.1 function if necessary.