Fix Pack capability level in WebSphere Message Broker

Technote (FAQ)


Question

Why does the output of WebSphere Message Broker (WMB) command "mqsiservice -v" show a previous Fix Pack capability level after upgrading?

This is true for any version of WMB, but the following example shows output after upgrading WebSphere Message Broker V6.1 to FP03. The command "mqsiservice -v" shows "effective level 6.1.0.2".

>mqsiservice <Broker name> -v
Install Path = C:\Program Files\IBM\MQSI\6.1
Working Path = C:\Documents and Settings\All Users\Application Data\IBM\MQSI
...
...
...
ComponentType = Broker
Fix Pack capability level = (effective level 6.1.0.2) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

BIP8996I: Version: 6103
BIP8997I: Product: WebSphere Message Brokers
BIP8998I: CMVC Level: S610-FP03 DH610-L81015
BIP8999I: Build Type: Production
BIP8071I: Successful command completion.

Cause

While the broker benefits from the fixes included in the Fix Pack level installed, it is effectively running at a functional level of 6.1.0.2. It would not be able to use the new functions introduced in Fix Pack 3 unless they are 'enabled'.

Many customers with working solutions wish to apply important fixes, but they do not wish to add new functionality due to the potential of introducing new issues.

Answer

Run the following commands to enable the level of functionality to Fix Pack 3:

1. Stop the broker

2. mqsichangebroker <broker name> -f 6.1.0.3

3. Start the broker

This only needs to be enabled for the broker.

This information is also documented in the topic mqsichangebroker command in the online documentation. See the references to the parameter: -f


Product Alias/Synonym

WMB MB Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Message Broker
Installation

Software version:

6.1, 7.0, 8.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

All Editions

Reference #:

1376622

Modified date:

2013-02-15

Translate my page

Machine Translation

Content navigation