From IBM MQ Version
9.0 there are two types of
release; a Long Term Support Release (LTSR) and Continuous Delivery Release (CDR). The aim of the
two release types is to meet the requirement for delivery of new and enhanced IBM MQ functions as rapidly as possible in the next CDR, while at
the same time maintaining a stable long term support release for systems that need a long term
deployment of IBM MQ, and for customers who prefer this
traditional option.
The release model
Externally, for IBM MQ, the two release types are
distinguishable by the modification number in the version.release.modification
(v.r.m) release identifier.
IBM MQ Version
9.0.0 has a zero modification number and is
designated as LTSR.
Continuous Delivery releases will have a non-zero modification number, for example, 9.0.1, 9.0.2,
and so on.
LTS Releases are updated by fixpacks or PTFs, which provide defect fixes and security updates in
a predictable fashion. This process matches the way service has been provided on prior versions of
IBM MQ.
Fixpacks are numbered according to a v.r.m.f scheme so, for example, the first
fixpack for the IBM MQ Version
9.0.0 LTSR will be numbered
9.0.0.1.
CD Releases are made available on a regular basis, and contain functional enhancements as
well as the latest set of defect fixes and security updates.
Each CD Release replaces the prior ones for that version of IBM MQ, so it is possible for you to skip CD releases, if a
specific CD Release does not contain any function that is relevant for your enterprise.
The next sections describe the specific detail of the process for obtaining, installing, and
using IBM MQ code in the new release model. IBM MQ for z/OS® and IBM MQ
on distributed platforms are considered separately.
Considerations for IBM MQ for z/OS
Ordering
When ordering IBM MQ for z/OS
Version 9.0, two separate features are offered on ShopZ. The
features correspond to the Long Term Support Release and the Continuous Delivery Release.
Both features are applicable to the same product id (PID). It is the product id that is
licensed, so where one feature is licensed, there is entitlement to use the alternative feature if
required.
When ordering the following IBM MQ for z/OS
products, select the feature corresponding with either the LTS Release or CD Release:
- IBM MQ for z/OS Version 9.0
- IBM MQ for z/OS Version 9.0 Managed File Transfer
If you are selecting products for inclusion in a ServerPac, it is not possible to choose
both the LTSR and CDR in the same ServerPac order, because the products cannot be installed by SMP/E
in the same target zone.
IBM MQ for z/OS
Version 9.0 Advanced Message Security (AMS) provides both
the LTS and CD release options.
The release options are selected by choosing the equivalent
release for the base product, IBM MQ for z/OS
Version 9.0, and enabling with the product 5655-AM9.
Attention: You cannot choose CD Release enhancements for AMS functions on an LTSR
IBM MQ base.
If your enterprise uses IBM MQ for z/OS
Version 9.0 Value Unit Edition (VUE), the same product
5655-VU9 enables VUE licensing in either the LTS or CD Release of IBM MQ for z/OS
Version 9.0.
Installation
The LTS and CD releases are provided in separate sets of
FMIDs. Note that these FMIDs cannot be installed in the same SMP/E target zone.
Where you
require both the LTS and CD releases, you should:
- Install the LTS release and CD release in separate target zones
- Maintain separate target and distribution libraries for the two releases
As the releases use different FMIDs, it is not possible to update a CD Release with
maintenance for an LTS Release or the other way round. Similarly, there is no way to switch a
version of the product code from LTS to CD or the other way round.
However it is possible to
switch a queue manager between the release models, for further information see Migration
Maintenance
The LTS Release is serviced by the application of PTFs which
provide defect fixes. Note that the PTFs resolve specific issues, and are not cumulative.
IBM provides groups of fixes in RSU levels
for an LTS Release.
The CD Release is serviced by the application of PTFs which deliver both
defect fixes and functional enhancements.
Each set of PTFs is cumulative and increases the
modification level of the CD release. That is, a set of PTFs will update the product and change the
reported v.r.m from V9.0.1 to V9.0.2. The subsequent set of PTFs supersedes the
first set, and updates the installed product to V9.0.3.
Migration between LTSR and CDR
There are constraints and
limitations, but generally a single queue manager can be migrated from using LTS Release code to CD
Release code or from using CD Release code to LTS Release code provided that the target release is
higher than that in use prior to the migration.
IBM MQ for z/OS has traditionally provided a fallback capability
(backward migration) so that after a period of running following a migration, it is possible to
fallback to the prior release without loss of data provided that new release operation is restricted
to compatible operations through the OPMODE(COMPAT) control.
This capability is retained for
LTS Releases, but is not possible when the source or target of a migration is a CD Release.The
following are valid migration scenarios and illustrate this principle:
Once a queue manager starts running a CD release of code, the queue manager sets the OPMODE
to NEWFUNC at the new release level. The queue manager command level will also be updated to
indicate the new release level.
| Source release | Destination release | Notes |
|---|---|---|
| V8.0.0 | V9.0.0 LTSR | backward migration supported while V9.0.0 in OPMODE(COMPAT) |
| V8.0.0 | V9.0.1 CDR | No backward migration, target release is CD |
| V9.0.0 LTSR | V9.0.2 CDR | No backward migration, target release is CD |
Considerations for IBM MQ on distributed platforms
Ordering
Within Passport Advantage there are two separate eAssemblies for
IBM MQ Version
9.0. One contains installation images for
IBM MQ Version
9.0.0 Long Term Support Release, and the other
contains installation images for IBM MQ Version
9.0.x Continuous
Delivery Release.
Download installation images from the eAssembly according to your choice of
release.
Alternatively, for the LTS Release only, a media pack is available, containing
product installation DVDs.
All IBM MQ versions,
and for IBM MQ Version
9.0 both the LTS and CD releases, belong
to the same Product Id.
Entitlement to use IBM MQ
extends across the entire product (PID) subject to the constraints of licensed components and
pricing metrics. This means that you can freely choose between LTSR and CDR installation images for
IBM MQ Version
9.0.
Installation
Once an installation image has been downloaded from Passport
Advantage, you should only select for installation the components for which you have purchased
entitlement. See IBM MQ license information for further information about
which installable components are included for each chargeable component.
It is possible to
install components from IBM MQ Version
9.0 LTSR and components
from IBM MQ Version
9.0 CDR on the same operating system image.
If you do this, the components appear as separate installations, as supported by IBM MQ multi-version support. Each version has distinct sets of
queue managers associated with that version.
Each new CD Release is provided as an
installation image. The new CD Release can be installed along side an existing release, or, an
earlier CD Release can be updated in place by the installer to the new release.
Maintenance
The LTS Release is serviced by the application of fixpacks,
which provide defect fixes. The fixpacks are made available periodically and are
cumulative.
The only maintenance provided for a CD Release will be in the form of an iFix
delivered to resolve a specific customer issue, if required, on a CD Release for which service is
available.
Migration between LTSR and CDR
There are constraints and limitations but,
generally, a single queue manager can be migrated from using LTS Release code to CD Release code, or
from using CD Release code to LTS Release code, provided that the target release is higher than that
in use prior to the migration.
Two approaches are possible:
- Install the new release of code in place so that an existing installation of IBM MQ is updated. Any queue managers associated with the installation use the new release of code when started.
- Install the new release of code as a new installation, then move individual queue manager instances to the new installation using the setmqm command.
Once a queue manager starts running a CD release of code, the queue manager command
level is updated to indicate the new release level. This means any new functions provided in the
release are enabled, and it will no longer be possible to restart the queue manager using a code
release with a lower
Comments
Post a Comment