| Author |
Message
|
| j.f.sorge |
 Posted: Wed Nov 24, 2010 11:45 pm Post subject: [solved] how to migrate WMB 6.1 32 bit exe group to 64 bit |
 |
|
Master
Joined: 27 Feb 2008
Posts: 218
|
There is one APAR IC66021 which has been introduced in WMB 6.1.0.8. This fix should enable migrating any existing 32 bit execution group into 64 bit one, but I did not find the command which does it.
Does anyone know this command?
Thanks in advance!
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Last edited by j.f.sorge on Fri Nov 26, 2010 2:19 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Nov 25, 2010 4:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
That APAR text should ideally mention what the command is.
The only thing I can think that could do this, maybe, is mqsicreatexecutiongroup. It at least has flags for 32bit or 64bit operation.
Best bet all around is to open a PMR and a) point out the documentation is bad, b) ask the command. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 25, 2010 5:26 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
At a guess check the documentation for mqsimigratecomponents 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Thu Nov 25, 2010 5:42 am Post subject: |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
| fjb_saper wrote: |
| At a guess check the documentation for mqsimigratecomponents |
Infocenter does not mention anything about changing the processor architecture in migration process.
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Thu Nov 25, 2010 8:04 am Post subject: |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
| mqmatt wrote: |
| In V6.1 processor architecture can only be set at execution group creation time. |
If I read the information about the APAR mentioned above it says that message broker 6.1.0.8 has been changed in order to allow that change.
| mqmatt wrote: |
| Check out mqsicreateexecutiongroup -l. |
When I create new execution groups I always create them with the -l option, but there are old ones (on test environment) which I wanted to convert into 64 bit ones.
In order to clarify I have opened PMR 87901,031,724.
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Nov 25, 2010 8:11 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Thu Nov 25, 2010 11:40 pm Post subject: |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
IBM Support sent the following answer.
| Quote: |
APAR IC66021 provides a new environment variable that can be set if a user wishes to migrate their 32 bit execution groups to 64 bit, without having to manually re-create the EG at 64 bit.
The environment variable, MQSI_FORCE_64BIT_EGS, can be set with two different values:
* MQSI_FORCE_64BIT_EGS=TEMP, which starts the EGs as 64 bit.
* MQSI_FORCE_64BIT_EGS=PERM, which starts the EGs as 64 bit and permanently updates the EG's processor architecture.
Instructions
1. Apply the fix for APAR IC66021.
2. Export the environment variable with the appropriate value, e.g., export MQSI_FORCE_64BIT_EGS=TEMP or export MQSI_FORCE_64BIT_EGS=PERM Note that values are case-sensitive, so "TEMP" is not the same as "temp", for example.
3. If the value TEMP has been used, then the EG will start as 64 bit, but the change will not be permanent. If the value PERM has been used, then the EG's process architecture will be updated. This can be checked by issuing the following command: mqsibrowse <Broker> -t BROKERAAEG The ProcArchitecture column of the BROKERAAEG table should contain 64 for each of the migrated EGs if the PERM value was used.
Warning: The Processor Architecture value under the Properties tab of the execution group in the Toolkit, is not updated to reflect the change. |
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Nov 26, 2010 1:56 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Thanks for sharing
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
