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

This document includes the following sections:

Documentation
Maintenance
Installation
Migration
Configuration
New Function
Highlights of new function


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

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

See Webcast replay: WebSphere MQ for z/OS V7.1.0.

Documentation

View documentation in the Information Center in the WebSphere MQ Library. In the Information Center, see instructions for navigating and searching. There is a new icon in the left-hand frame that will allow you to "search selected topic" or "search selected topic and all subtopics".

The Information Center has been reorganized with task-oriented topics of.

Product overview
Planning
Migrating and upgrading
Installing
Security
Configuring
Administering
Developing applications
Monitoring and performance
Troubleshooting and support
Reference

The Portable Document Format (PDF) versions of WebSphere MQ (WMQ) documentation are no longer being maintained, except for the Program Directory. 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.1.0 PTFs. The complete list of V7.1.0 maintenance identifies HIPER (High Impact or Pervasive) and PE (Program Error) fixes along with all other available PTFs.
• 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

• Review Installing the WebSphere MQ for z/OS product including System Requirements.
• No matter what kind of product delivery packaging you use, see the WebSphere MQ for z/OS Version 7.1.0 Program Directory (GI13-0572-00) and the Configuring z/OS topic. Among other things, the Program Directory shows the SMP/E statements that should be used.
• Always use the highest level of early code, as stated in Configuration Task 3.
  
  

Migration

• Migration instructions
  Explore subtopics of Migrating and Upgrading WebSphere MQ in the WebSphere MQ Version 7.1,0 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)
  - Compatibility, coexistence, and interoperability
  - List of changes by version, release, and maintenance level

• Object sizes
  Starting at WMQ V7.1.0, the queue manager will automatically resize objects definitions in PSID(0) the first time the queue manager starts at a new release. Previously, the resizing was done when the object was altered. Depending on how many objects need to be migrated, there may a slight delay during the first start-up.
  
  SupportPac MP1H documents the increase in object sizes and the effect on PSID(0) and extended private storage.

• Backward migration
  See the document Problems and solutions when migrating to WebSphere MQ for z/OS v7.1.0. It contains details of backward migration maintenance, procedures, limitations, and restrictions plus some symptoms associated with common issues.
  
  Because service has been discontinued for WebSphere MQ for z/OS version 7.0.0, no backward migration PTF is available.
  
  For releases earlier than Version 6.0, no backward migration support from Version 7.1 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.
  
  
• Compatibility of SCSQnnnn libraries
  - See technote 1457146.
  - CICS Transaction Server APARs PM10011 (CICS TS 3.2) and PM12034 (CICS TS 4.1) point out that if you have WebSphere MQ Version 7 installed, 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."
  
  
• CONNSWAP parameter for CSQ6SYSP
  PK97354 for V7.0 (or PK91707 for V6) provided a service parameter to prevent a job from being swapped out while it is in the middle of an MQI call and therefore possibly holding latches. This functionality is now provided by the CONNSWAP parameter in CSQ6SYSP; the service parameter is no longer in use. To continue use of this function, you will need to set CONNSWAP=NO. The service parameter setting can still be left set in case of fallback to the prior release.
  
  A value of YES means that the jobs are swappable. A value of NO means that they are not swappable. The default behavior is that they are swappable, which is the same as with previous releases, except the case where the service parameter has been set.
  
  Users of the service parameter or CONNSWAP=NO need to be aware of
  PM66389: With 7.1.0 early code and the service parm for PK91707/PK97354 or CONNSWAP=NO, a job remains non-swappable.
  
  
• XA client users connecting to a Queue Sharing Group (QSG)
  Review technote 1449050.
  
  

Configuration

• Review the topic Customizing your queue managers.
• Some Sample definitions supplied with WebSphere MQ have additional object definitions. CSQINP1 and CSQINP2 input data sets changed from V6.0. 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 was new at V7.0.1. 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.
• If migrating from V6, 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 the publish/subscribe engine and the queued publish/subscribe interface are running. It can enable applications to publish/subscribe using the MQI and the queues to be monitored by the queued publish/subscribe interface.
  
  While PSMODE(ENABLED) is the default initial value, PSMODE(COMPAT) is used if the QMGR object is migrated from an earlier version.
  
  

New Function

• Review new function provided in WebSphere MQ for z/OS 7.0.0.
• Review new function provided in WebSphere MQ for z/OS 7.0.1
• Major areas of new function in WebSphere MQ for z/OS 7.1.0 include:
  • Channel access control (CHLAUTH)
  • CFLEVEL(5) support for Coupling Facility structures
  • Shared message data set (SMDS) function and statistics
  • Resilience to a coupling facility connectivity failure
  • Group unit of recovery support for CICS® Transaction Server for z/OS (CICS TS)
  • Federal Information Processing Standards (FIPS) 140-2 compliance for z/OS
  • More information about the subject and issuer distinguished name
  • IMS OTMA Resource Monitoring
  • Bind On Group
  • Dead Letter Queue usage on channels and topics
  • Other new channel definition and status options
  • SLOAD option for CSQUTIL
  • CSQINPT initialization data set for Publish/Subscribe commands
• 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
  • WebSphere MQ V7.1.0 announcement letter (211-394)
  • SupportPac MP1H: WebSphere MQ for z/OS V7.1.0 Performance Report
    
    

Highlights of new function

• Channel access control (CHLAUTH)
  Provides more precise control over the access granted to connecting systems at a channel level. For example, you will not have to use a channel security exit to block access to clients with blank MCAUSER or to map a channel's user ID to a valid user ID on the server.
  - Channel Authentication includes
  Blocking IP addresses
  Blocking user IDs
  Blocking queue manager names
  Blocking SSL or TLS DNs
  Mapping IP addresses to user IDs to be used
  Mapping queue manager names to user IDs to be used
  Mapping user IDs asserted by a client to user IDs to be used
  Mapping SSL or TLS DNs to user IDs to be used
  Mapping queue managers, clients, or SSL or TLS DNs according to IP address
  - Disabled by default for migrated queue managers. Enable it with ALTER QMGR CHLAUTH(ENABLED)
  - Enabled for new WebSphere MQ version 7.1 queue managers
  - Defined with SET CHLAUTH commands, displayed with DISPLAY CHLAUTH, and removed with SET CHLAUTH(*) ACTION(REMOVE).
  - Uses SYSTEM.CHLAUTH.DATA.QUEUE. CSQ4INSA has the queue definition and some default rules.
• OPMODE=NEWFUNC
  OPMODE=NEWFUNC controls functions to:
  - allow connection to a CF structure at CFLevel (5)
  - enable resilience to a coupling facility connectivity failure (CFCONLOS)
  - enable OTMA Resource Monitoring
• CFLEVEL(5) support for Coupling Facility structures
  CFLEVEL(5) enables:
  - Shared Message Data Set (SMDS) support
  - Toleration of a loss of connectivity to the CF structure (CFCONLOS and RECAUTO)
  - Additional PROPCTL(V6COMPAT) function for shared queues. Below CFLEVEL(5), behavior is like V7.0.1 with PM25890. CFLEVEL(5) supports using the queue for pub-sub or with MsgHandle.
  You can only increase the value of CFLEVEL to 5 if all the queue managers in the queue-sharing group are at command level 710 or greater and have OPMODE set to NEWFUNC.
• Shared Message Data Set (SMDS)
  Choose to offload large message data (63 KB or more) for shared queues to a WebSphere MQ managed data set rather than to DB2. See Planning your coupling facility and offload storage environment.
  - Can provide significant performance improvements and cheaper storage for large messages. Reference SupportPac MP1H.
  - Requires the CFSTRUCT to use CFLEVEL(5) or greater
  - Uses VSAM linear data sets. Reference sample CSQ4SMDS in SCSQPROC.
  - Controlled with the OFFLOAD(SMDS|DB2) option on the CFSTRUCT definition.
  - New commands:
  ALTER SMDS
  DISPLAY SMDS
  DISPLAY SMDSCONN
  RESET SMDS
  START SMDSCONN
  STOP SMDSCONN
  - New options for DEFINEor ALTER or DISPLAY CFSTRUCT:
  DSBUFS
  DSDBLOCK
  DSEXPAND
  DSGROUPs
  OFFLD1TH(percentage) OFFLD1SZ(size)
  OFFLD2TH(percentage) OFFLD2SZ(size)
  OFFLD3TH(percentage) OFFLD3SZ(size)
  OFFLOAD
  - New TYPE(SMDS) option for DISPLAY USAGE
  - Can be administered with the V7.1 MQ Explorer
• SMDS statistics
  The QESD DD statement has been added to thlqual.SCSQPROC(CSQ4SMFJ). to provide a data definition for printing SMDS statistics.
• Resilience to a coupling facility connectivity failure
  Resilience to a coupling facility connectivity failure
  - Requires CFLEVEL(5).
  - CFCONLOS attribute
  The QMGR CFCONLOS attribute controls whether loss of connectivity to the administration structure is tolerated.
  The CFSTRUCT CFCONLOS attribute controls whether loss of connectivity is tolerated by each application coupling facility structure.
  Values:
  - TERMINATE - The queue manager will terminate when connectivity to the structure is lost.
  - TOLERATE - The queue manager will tolerate loss of connectivity to the structure without terminating.
  - ASQMGR - The action taken for the CFSTRUCT is based on the setting of the CFCONLOS queue manager attribute.
  - RECAUTO - YES or NO for the CFSTRUCT definition
  Controls whether coupling facility structures should be automatically recovered using logged data following total loss of connectivity.
  - RESET CFSTRUCT ACTION (FAIL)
  Simulates a structure failure and set the status of the application structure to FAILED.
• Group unit of recovery support for CICS® Transaction Server for z/OS (CICS TS) 4.2
  Exploit group unit of recovery (GROUPUR=ENABLED, which requires OPMODE=NEWFUNC) by way of the CICS RESYNCMEMBER(GROUPRESYNC) configuration in the MQCONN resource definition. A CICS configured with this option can connect to any suitable queue manager in a queue sharing group (QSG) which is running on the same LPAR as that CICS region.
• Federal Information Processing Standards (FIPS) 140-2 compliance for z/OS
  FIPS support:
  - SSLFIPS attribute for the QMGR
  - New Cipher Specs (SSLCIPH channel attribute)
  TLS_RSA_WITH_DES_CBC_SHA (new)
  TLS_RSA_WITH_3DES_EDE_CBC_SHA (new and FIPS certified)
  TLS_RSA_WITH_AES_128_CBC_SHA (existing - FIPS certified)
  TLS_RSA_WITH_AES_256_CBC_SHA (existing - FIPS certified)
• More information about the subject and issuer distinguished name
  Support is added for a range of new security attributes. In order to access these attributes WebSphere MQ Version 7.1 obtains the Distinguished Encoding Rules (DER) encoding of a certificate and uses it to determine the subject and issuer distinguished names.
  The subject and issuer distinguished names appear in the SSLPEER and SSLCERTI fields. A SERIALNUMBER attribute is also included in the subject distinguished name and contains the serial number for the certificate of the remote partner.
  The attributes are passed to channel security exit programs.
• OTMA Resource Monitoring for the IMS bridge
  x'3C' OTMA protocol messages are available in IMS v10 or higher to report IMS health status, WMQ OTMA Resource Monitoring will slow down the rate at which requests are sent over the bridge if a flood warning is received. Processing will gradually get faster in response to a flood relieved notification.
  This function requires OPMODE=NEWFUNC.
• MQOO_BIND_ON_GROUP and DEFBIND(GROUP)
  Allow an application to request that a group of messages are all allocated to the same destination instance of a cluster queue. Use the MQOO_BIND_ON_GROUP option for MQOPEN or use MQOO_BIND_AS_Q_DEF for MQOPEN with DEFBIND(GROUP) on the DEFINE command for the queue. For z/OS, use INDXTYPE(GROUPID) when messages are retrieved using message grouping selection criteria.
• Dead Letter Queue usage on channels and topics
  The Use Dead-Letter Queue (USEDLQ) attribute can be used to provide increased granular control over which channels and topics use the Dead-Letter queue when a message cannot be delivered.
• BATCHLIM on the channel definition
  BATCHLIM is the limit, in kilobytes, of the amount of data that can be sent through a channel before taking a sync point.
• RPRODUCT and RVERSION on DISPLAY CHSTATUS
  RPRODUCT and RVERSION return the remote partner product identifier and version. See the Product Identifier Values. If blank, the remote partner is V6 or earlier.
• SLOAD option for CSQUTIL
  Selective LOAD (SLOAD) processes a single queue even if multiple queues were offloaded by COPY or SCOPY.
• CSQINPT DD statement
  The MQSC commands contained in the CSQINPT data set, for example to define subscriptions, are executed at the end of publish/subscribe initialization, and output is written to the data set specified by the CSQOUTT DD statement.
  - DEFINE SUB for SYSTEM.DEFAULT.SUB is no longer permitted in the CSQINP2 input data set but can be issued from CSQINPT. CSQ4INST in thlqual.SCSQPROC provides the sample definition.
  - CSQ4INYT in thlqual.SCSQPROC provides sample commands.
• PSCLUS
  This QMGR attribute, with options of ENABLED or DISABLED, controls whether the queue manager participates in publish subscribe activity across any clusters in which it is a member. This function was available with WMQ for z/OS V7.0.1 via a Service parameter via APAR PM56310. It matters most in large clustering environments.
• MQ Explorer caching
  In the past, if you used the MQ Explorer to administer your z/OS queue manager, then after migration between releases, actions were needed to refresh the Explorer's cached view of the queue manager attributes, including the command level. New message AMQ4616 indicates the connection to the queue manager will be automatically replaced.