| Author |
Message
|
| chanduy9 |
 Posted: Tue Jul 28, 2009 7:40 am Post subject: Fixpack capability level = '' (effective level '6.1.0.2') |
 |
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi.
When I run mqsireportbroker BRKDEV, the below output is coming,
[wbrkadm@MTDAPPLX01 ~]$ mqsireportbroker BRKDEV
BIP8926I: Broker Name 'BRKDEV'
Install path = '/opt/ibm/mqsi/6.1'
Work path = '/var/mqsi'
Broker UUID = '59f64467-2001-0000-0080-baab0166e2e2'
Process id = '21223'
Service userId = 'wbrkadm'
Service password = '********'
Queue Manager = 'BRKDEV_QM'
User Name Server Queue Manager = ''
Broker database name = 'BRKDEV'
Broker database userId = 'wbrkadm'
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 = '7082'
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'
But, I have applied fix pack 6.1.04, then why it is showing Fixpack capability level = '' (effective level '6.1.0.2'). I have changed mqsiprofile to 6.1.0.4.
login as: wbrkadm
wbrkadm@xx.xx.xx.xxx's password:
Last login: Tue Jul 21 16:42:43 2009 from 10.2.32.49
-bash: [wbrkadm: command not found
MQSI 6.1.0.4
/opt/ibm/mqsi/6.1
The fix pack level showing as 6.1.0.2 for Broker and Config Mgr:
[wbrkadm@MTDAPPLX01 ~]$ mqsiservice BRKDEV
BIPv610 en US
ucnv Console CCSID 1208 dft ucnv CCSID 1208
ICUW UTF-8 ICUA UTF-8
Install Path = /opt/ibm/mqsi/6.1
Working Path = /var/mqsi
Component UUID = 59f64467-2001-0000-0080-baab0166e2e2
process id = 21223
broker db name = BRKDEV
broker db userId = wbrkadm
broker db password =
queue manager = BRKDEV_QM
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)
BIP8071I: Successful command completion.
[wbrkadm@MTDAPPLX01 ~]$ mqsiservice CMGRDEV
BIPv610 en US
ucnv Console CCSID 1208 dft ucnv CCSID 1208
ICUW UTF-8 ICUA UTF-8
Install Path = /opt/ibm/mqsi/6.1
Working Path = /var/mqsi
process id = 9271
ConfigMgr db userId = wbrkadm
ConfigMgr db password =
jdbc driver name = com.ibm.db2.jcc.DB2Driver
jdbc connection name = db2
queue manager = CMGRDEV_QM
ComponentType = ConfigMgr
Fixpack capability level = (effective level 6.1.0.2)
Do I need to run any commands on Broker and config mgr after appling the fix pack? Please advise.
Thanks,
Chandra.
_________________
Chandra,
IBM WebSphere MQ Certified. |
|
| Back to top |
|
 |
| zpat |
| Posted: Tue Jul 28, 2009 7:44 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
run mqsichangebroker -f 6.1.0.4 to enable the features, or you can enable all the features for current version with -f all
IBM have decided to make the functions selectable, so you can apply maintenance without getting any new features.
Strange but true! |
|
| Back to top |
|
|
| issis |
| Posted: Wed Aug 12, 2009 11:42 pm Post subject: |
|
|
Novice
Joined: 20 Aug 2004
Posts: 17
Location: Finland
|
| zpat wrote: |
| run mqsichangebroker -f 6.1.0.4 to enable the features, or you can enable all the features for current version with -f all |
This is ok with the broker but the configuration manager still reports the initial fixpack level while brokers have 6.1.0.4.
| mqsiservice wrote: |
| Fixpack capability level = (effective level 6.1.0.2) |
The mqsichangeconfigmgr does not offer the "-f" option but it appears to update automatically. When I start the cfgmgr, it reports following:
| syslog wrote: |
| WebSphere Broker v6104[438304]: (DEVCM1)[1]BIP1003I: The Configuration Manager is available for use. |
Interesting.
Mikko |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Aug 13, 2009 8:51 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
What version of WMB 6.1 the broker is running on and what version it's using for features are 2 seperate things. 6.1.0.3 and 6.1.0.4 have new features that are not automatically available. By default the FixPack compatability version is "stuck" at 6.1.0.2, even if you are running at 6.1.0.4. You can change this and enable those features if you like with a command to bump up the compatibility version to match the actual installed version.
This does not apply at all to the config manager, which has only 1 version for both the software level and the compatability level.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fschofer |
| Posted: Fri Aug 14, 2009 12:17 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
mqsiservice is an undocumented command so i would not rely on it.
Use the new fixpack4 commands mqsireportbroker and mqsireportconfigmgr instead.
Greetings
Frank |
|
| Back to top |
|
|
| emileke |
| Posted: Wed Nov 11, 2009 4:49 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2001
Posts: 110
Location: South Africa
|
Hi all,
Very interesting but does it mean the Broker and Configuration Manager is running at the "effective level " or the "CMVC Level: S610-FP04AIX DH610-FP04" ?
Clearly mqsiservice and mqsireportbroker/mqsireportconfigmgr are not in sync or does not produce the same result.
I guess what I am asking is, what is the level that the components are running at?
_________________
Emile M Kearns |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Nov 11, 2009 5:27 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Your software is running at the version displayed when you issue mqsiprofile.
On a Broker, the features you can use are determined by what "Fixpack capability level" is set to.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| emileke |
| Posted: Wed Nov 11, 2009 7:24 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2001
Posts: 110
Location: South Africa
|
Thanks, that clears it
_________________
Emile M Kearns |
|
| Back to top |
|
|
| deecee |
| Posted: Mon Aug 08, 2016 5:03 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2014
Posts: 51
|
Hello,
I am getting a similar error in IIB 9 now.
I have just upgraded the fixpack from 9.0.0.1 to 9.0.0.5.
mqsireportbroker properties says it's running at 9.0.0.1 and the fixpack capability level is 9.0.0.5
I have run the changebroker command too. What else do I have to do to update the version displayed? Or can I assume my broker is running at 9.0.0.5? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 08, 2016 5:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| deecee wrote: |
| I have run the changebroker command too. |
What exactly did you run?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| deecee |
| Posted: Mon Aug 08, 2016 5:54 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2014
Posts: 51
|
mqsistop broker
mqsichangebroker BDPBRKDLX01 -f 9.0.0.5
mqsistart broker |
|
| Back to top |
|
|
| Craig B |
| Posted: Tue Sep 20, 2016 5:32 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
So if you want to see what version of the code you are running on in a command console then you can use "mqsiversion -v". This shows the version of the product and for 9.0.0.5 it would show:
BIP8996I: Version: 9005
BIP8997I: Product: IBM Integration Bus
BIP8998I: CMVC Level: S900-FP05
BIP8999I: Build Type: Development, 64 bit, amd64_nt_4
Fixpackcapability will default to blank until you choose to set it to a value.
While it is blank it will tell you the base level. So the version it reports as the base level just prior to when Fixpackcapability was needed.
So in IIB when functionality is shipped in a fixpack that needs this flag to protect it then Fixpackcapability will be switched on in that fixpack and the default effective level will be the last fixpack that didn't have it enabled.
After that you can then set it to a specific fixpack level if you want to pick up new functionality. This is only for new functionality. You will still get all of the fixes in 9.0.0.5 irrespective of what the fixpackcapability field is set to.
As far as I know the only piece of functionality that is affected by fixpack capability in V9 is whether Maps are compiled on first use or at deploy time. So if this is of no concern to you then I really wouldn't worry about what fixpack capability is set to.
_________________
Regards
Craig |
|
| Back to top |
|
|
| deecee |
| Posted: Tue Sep 20, 2016 5:38 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2014
Posts: 51
|
Thank You Craig.
I needed the new version for the DFDL fixes that were included.
The new fix pack was installed in a different path to the original installation and hence I was facing this issue. Now it's resolved. Thanks! |
|
| Back to top |
|
|
|
|
