| Author |
Message
|
| Rahul999 |
 Posted: Sat Jul 17, 2010 2:29 am Post subject: Solved: How to know the exact fix pack level of BROKER V6.1 |
 |
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Hi All,
I would like to know what is the exact level of fix pack has been applied on a Message Broker V6.1 running on AIX. I know of a command which gives me the version of Message broker but I dont think it list down the correct fix pack level. I need to collect this information to see whether i need an upgrade of Message Broker or not.
Below is the output of mqsiservice command on message broker, although it gives a value for "Fixpack capability level" but I dont think this is the correct fix pack level we have installed.
| Quote: |
$ mqsiservice BRKBRK1
BIPv610 en GB
ucnv Console CCSID 819 dft ucnv CCSID 819
ICUW ISO-8859-1 ICUA ISO-8859-1
Install Path = /opt/IBM/mqsi/6.1
Working Path = /var/mqsi
Component UUID = 332aba4e-2601-0000-0080-99e4220f5d4d
process id = 2367668
broker db name = MQSIBKDB
broker db userId = mqsiuser
broker db password =
queue manager = BRKQM
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
Fixpack capability level = (effective level 6.1.0.2)
|
Last edited by Rahul999 on Sun Jul 18, 2010 6:04 am; edited 1 time in total |
|
| Back to top |
|
 |
| zpat |
| Posted: Sat Jul 17, 2010 5:01 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
mqsireportbroker
lslpp -l | grep mqsi |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Sat Jul 17, 2010 7:03 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Thanks zpat,
I tried both the commands, below is the output I got from both of them, the 2nd command tells me that Fix Pack level is 5, hope that is correct.
1. mqsireportbroker BRKBRK1
| Quote: |
BIP8926I: Broker Name 'BRKBRK1'
Install path = '/opt/IBM/mqsi/6.1'
Work path = '/var/mqsi'
Broker UUID = '332aba4e-2601-0000-0080-99e4220f5d4d'
Process id = '2367668'
Service userId = 'mqsiuser'
Service password = '********'
Queue Manager = 'BRKBRK1'
User Name Server Queue Manager = ''
Broker database name = 'MQSIBKDB'
Broker database userId = 'mqsiuser'
Broker database password = '********'
User lil path = ''
User lil path64 = ''
User exit path = ''
User exit path64 = ''
Active user exits = ''
LDAP principal = ''
LDAP credentials = ''
ICU converter path = ''
HTTP listener port = '7080'
Pubsub migration = 'false'
Pubsub access control = 'false'
Trusted (fastpath) Queue Manager application = 'false'
Configuration change timeout = '300' seconds
Internal configuration timeout = '60' seconds
Statistics major interval = '60' minutes
Operation mode = 'enterprise'
Fixpack capability level = '' (effective level '6.1.0.2')
Broker registry format = 'v6.1' |
2. lslpp -l | grep mqsi
| Quote: |
mqsi61 6.1.0.5 COMMITTED IBM WebSphere Message Broker
mqsi61.brokerc 6.1.0.5 COMMITTED Broker Component
mqsi61.brokerf 6.1.0.5 COMMITTED Broker Feature
mqsi61.cfgmgrc 6.1.0.5 COMMITTED Config. Manager Component
mqsi61.cfgmgrf 6.1.0.5 COMMITTED Config. Manager Feature
mqsi61.core 6.1.0.5 COMMITTED Core Component
mqsi61.data 6.1.0.5 COMMITTED Data Component
mqsi61.datadirect 6.1.0.5 COMMITTED DataDirect Component
mqsi61.disthub 6.1.0.5 COMMITTED DistHub Component
mqsi61.is 6.1.0.5 COMMITTED Integration Services Component
mqsi61.itlm 6.1.0.5 COMMITTED ITLM Component
mqsi61.la 6.1.0.5 COMMITTED LA Component
mqsi61.links 6.1.0.5 COMMITTED Links Component
mqsi61.mrm 6.1.0.5 COMMITTED MRM Component
mqsi61.profiles 6.1.0.5 COMMITTED Profiles Component
mqsi61.samples 6.1.0.5 COMMITTED Samples Component
mqsi61.tsamples 6.1.0.5 COMMITTED Transformation Services
mqsi61.tsc 6.1.0.5 COMMITTED Transformation Services
mqsi61.tsf 6.1.0.5 COMMITTED Transformation Services
mqsi61.unsc 6.1.0.5 COMMITTED UNS Component
mqsi61.unsf 6.1.0.5 COMMITTED UNS Feature
|
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Jul 17, 2010 8:03 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
So you have 6.1.0.5 installed but...
What level are you running at?
Hint, it is in the output from report broker.
You need to know BOTH things to fully understand the revision level that broker is running at.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| zpat |
| Posted: Sat Jul 17, 2010 9:15 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
mqsichangebroker BRKBRK1 -f all
Unless you really want to cripple the function to 6.1.02 |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Sat Jul 17, 2010 11:46 pm Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
smdavies wrote:
| Quote: |
So you have 6.1.0.5 installed but...
What level are you running at?
Hint, it is in the output from report broker. |
| Quote: |
BIP8926I: Broker Name 'BRKBRK1'
Install path = '/opt/IBM/mqsi/6.1'
Work path = '/var/mqsi'
Broker UUID = '332aba4e-2601-0000-0080-99e4220f5d4d'
Process id = '2367668'
Service userId = 'mqsiuser'
Service password = '********'
Queue Manager = 'BRKBRK1'
User Name Server Queue Manager = ''
Broker database name = 'MQSIBKDB'
Broker database userId = 'mqsiuser'
Broker database password = '********'
User lil path = ''
User lil path64 = ''
User exit path = ''
User exit path64 = ''
Active user exits = ''
LDAP principal = ''
LDAP credentials = ''
ICU converter path = ''
HTTP listener port = '7080'
Pubsub migration = 'false'
Pubsub access control = 'false'
Trusted (fastpath) Queue Manager application = 'false'
Configuration change timeout = '300' seconds
Internal configuration timeout = '60' seconds
Statistics major interval = '60' minutes
Operation mode = 'enterprise'
Fixpack capability level = '' (effective level '6.1.0.2')
Broker registry format = 'v6.1' |
Does that mean our administrator has installed Fix Pack Level5 but message broker runtime environment is at fix pack level2, is it possible?
I thought that once you installed fix pack5 and re-start the broker it will automatically take into affect the latest installed fix pack.
Thanks. |
|
| Back to top |
|
|
| zpat |
| Posted: Sun Jul 18, 2010 12:30 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Run the command I mentioned above. Otherwise it will remain functionally at 6.1.02. But the maintenance is applied. |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Sun Jul 18, 2010 12:57 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
zpat wrote:
| Quote: |
Run the command I mentioned above. Otherwise it will remain functionally at 6.1.02. But the maintenance is applied.
|
Thanks Zpat for all the help, but my question remains is how come the functionality at 6.1.0.2 whereas we have fix pack 5 installed on that broker? |
|
| Back to top |
|
|
| zpat |
| Posted: Sun Jul 18, 2010 2:22 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Because IBM have made it work like that. You have to opt for the new function to be enabled.
They claim that sites want fixes without new function so they made it possible. |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Sun Jul 18, 2010 2:30 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
zpat wrote:
| Quote: |
Because IBM have made it work like that. You have to opt for the new function to be enabled.
They claim that sites want fixes without new function so they made it possible. |
Ok, does that mean each fix pack have 2 components - 1. Fixes 2. New function? And, if you apply fix pack on a broker only the fixes take into affect but for new function to be enabled you have to run the command which you specified earlier. |
|
| Back to top |
|
|
| zpat |
| Posted: Sun Jul 18, 2010 3:19 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Yes, if you run it with -f all then all function is enabled now and in the future. Otherwise choose the level you want such as -f 6.1.05 |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Sun Jul 18, 2010 5:54 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Thanks zpat, all the information provided by you was really helpful, I am editing the subject of this post to "SOLVED".
Thanks. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Jul 19, 2010 12:48 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
The "Fixpack capability level" setting is only used to limit the introduction of new feature function in later fixpacks. The setting doesn't prevent any fixes being applied.
The reason is, particularly on later fixpacks, many users don't want new features potentially affecting an existing broker, and instead just want to apply fixes. This setting allows IBM to deliver new feature function easily while still allowing the rollup of fixes.
As zpat said, use mqsichangebroker -f all if you don't mind new function always being enabled when you apply fixpacks.
In the past (6.1.0.3), this feature has been used to disable new nodes, such as PHP and IMS. It's not currently used on 7.0.0.1. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jul 19, 2010 4:23 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
If there was a feature to disable Java compute nodes, I would be tempted to turn it on 
There is too much temptation for Java developers to let rip in Java instead of using builtin functions! |
|
| Back to top |
|
|
|
|
