installing mq 9.1.0.0 lts to coexist with mq 8.0.0.9 in windows ... · note: the particular fix...

of 47

Installing MQ 9.1.0.0 LTS to coexist with MQ 8.0.0.9 in Windows, including applying Fix Packs 8.0.0.14 and 9.1.0.4

https://www.ibm.com/support/pages/node/2800929

Date last updated: 17-Apr-2020

Angel Rivera – [email protected]

IBM MQ Support

+++ Objective This techdoc shows all the steps to install MQ 9.1.0.0 LTS in Windows, while co-existing ("side-by-side") with MQ 8.0.0.9. Furthermore, the steps include the installation of the Fix Packs 8.0.0.14 and 9.1.0.4. Note: The particular fix packs mentioned in this tutorial were the latest ones at the time the tutorial was written – the overall recommendation is to apply the most recent fix pack level. None of the installations are designated as “Primary”. Therefore, you must use “setmqenv” to setup the MQ environment for the desired installation. NOTE regarding MQ 9.0: The principles discussed in this techdoc apply also to MQ 9.0. Keep in mind that the End Of Support (EOS) for MQ 8.0 is 30-Apr-2020 and for MQ 9.0 is 30-Sep-2021. At the time this tutorial was written, the EOS for MQ 9.1 has not been announced yet. An important aspect of this feature of multiple installations of MQ (multi-install) in the same host, is that this type of installation does not require that the MQ 8.0 queue managers and applications need to be stopped when doing activities with MQ 9.1. That is, the installation of MQ 9.1 does not affect the running MQ 8.0 applications. This is helpful when you try to do a staging upgrade of the MQ 8.0 queue managers to MQ 9.1. The equivalent document for Linux is: https://www.ibm.com/support/pages/node/2800923 Installing MQ 9.1.0.3 LTS to coexist with MQ 8.0.0.9 in Linux x86 64-bit, including applying Fix Packs 8.0.0.14 and 9.1.0.4


mailto:[email protected]


of 47

The chapters are: Chapter 1: Installing MQ 9.1 side-by-side to MQ 8.0 Chapter 2: Need to run setmqenv to use MQ 9.1 or MQ 8.0 commands Chapter 3: Creating a queue manager under MQ 9.1 Chapter 4: Remote access to the new MQ 9.1 queue manager Chapter 5: Migrating an MQ 8.0 queue manager to MQ 9.1 Chapter 6: Installing fix pack MQ 8.0.0.14 Chapter 7: Installing Fix Pack 9.1.0.4 Chapter 8: Uninstallation +++ Using MQ 9.1 Long Term Support (LTS) for this tutorial Starting with MQ 9.0, there are 2 branches for delivering the code. Here is a SUMMARY of when to use Long Term Support (LTS) and when to use Continuous Delivery (CD): a) Use LTS if you want STABILITY and you are willing to sacrifice new features that may come with CD. You are not willing to tolerate the bugs that may come with the new features. You will have fix packs that can be applied on top of LTS. In our experience, customers want LTS for the PRODUCTION queue managers. b) Use CD if you want NEW FEATURES and you are willing to tolerate the bugs that may come with the new features. There are NO fix packs that can be applied on top of a CD release (but there might be interim fixes). In a sense, the next CD release, such as MQ 9.1.2, is the fix pack for MQ 9.1.1 and has new features and fixes for bugs. If you are using 9.1.1 CD, you MUST UNINSTALL 9.1.1 in order to install the new 9.1.2 CD (this action does NOT change the data of the queue manager). In our experience, customers want CD for the DEVELOPMENT queue managers. Note: For more details see: http://www-01.ibm.com/support/docview.wss?uid=swg27047919 IBM MQ FAQ for Long Term Support (LTS) and Continuous Delivery (CD) releases

http://www-01.ibm.com/support/docview.wss?uid=swg27047919

of 47

+++ Hardware and software used for this tutorial Windows 10 Hostname: ventanas1.fyre.ibm.com Queue Managers: QM80 => Created with MQ 8.0.0. To remain at 8.0.0 QMMIG => Created with MQ 8.0.0. To be migrated to 9.1.0 QM910 => Created with MQ 9.1.0. To remain at 9.1.0 The MQ 8.0 code was installed as the only installation of MQ in the directory:

C:\Program Files\IBM\WebSphere MQ\ by following the instructions from these tutorials: http://www.ibm.com/support/docview.wss?uid=swg27050058 Installing MQ 9.0 in Windows, using only the defaults http://www.iibm.com/support/docviiew.wss?uiid=swg27050059 Installing MQ 9.0 in Windows, specifying additional components (Telemetry, AMS, MFT) The MQ 8.0 installation is NOT designated as Primary. The MQ 8.0.0.9 rebased code was downloaded from IBM Passport Advantage and it has the cumulation of MQ 8.0.0.0 + 8.0.0.1 + … + 8.0.0.9 https://www.ibm.com/support/pages/downloading-ibm-mq-version-80 Downloading IBM MQ Version 8.0 The Part Number is: CNS92ML IBM MQ V8.0.0.9 for Windows eImage The installation file was downloaded into a temporary directory: C:\downloads\mq8009win>dir 01/15/2020 12:35 PM 554,041,438 IBM_MQ_V8.0.0.9_FOR_WIN_MUL.zip Unzip the zip file. Move to the subdirectory: MQServer As an Administrator, double click to execute the following command:

Setup.exe

http://www.ibm.com/support/docview.wss?uid=swg27050058

http://www.iibm.com/support/docviiew.wss?uiid=swg27050059

https://www.ibm.com/support/pages/downloading-ibm-mq-version-80

of 47

Follow the instructions from the tutorial. The MQ 8.0 code will be installed as Installation1 in: C:\Program Files\IBM\WebSphere MQ\ The data and recovery logs for the queue managers will be located in the default: C:\ProgramData\IBM\MQ\ For this tutorial, the “Windows Client” is a component that needs to be explicitly selected from the Features menu by using the (*) Custom option. Note that the Typical option does not install the MQ Windows Client.

It is recommended that you create a batch file that will invoke the MQ utility “setmqenv” for the desired Installation. This batch file needs to be located in a directory in your PATH, such as: C:\WinTools Example, using Batch file: set-mq-80.bat Note that “SET PATH” must be in a single long line. +begin (do not include this line) REM Setup the environment to run MQ 8.0

CALL " C:\Program Files\IBM\WebSphere MQ\bin\setmqenv" -n Installation1

REM Adding Samples to the path

SET

PATH=%PATH%;%MQ_FILE_PATH%\Tools\c\Samples\Bin;%MQ_FILE_PATH%\Tools\c\Sampl

es\Bin64;%MQ_FILE_PATH%\Tools\jms\samples;%MQ_JAVA_INSTALL_PATH%\bin\

dspmqver -f 2

+end (do not include this line)

of 47

Before you invoke setmqenv via set-mq-80 notice the default environment variables that are set by the MQ installer: C:\> set MQ MQ_FILE_PATH=C:\Program Files\IBM\WebSphere MQ MQ_JAVA_DATA_PATH=C:\ProgramData\IBM\MQ MQ_JAVA_INSTALL_PATH=C:\Program Files\IBM\WebSphere MQ\java MQ_JAVA_LIB_PATH=C:\Program Files\IBM\WebSphere MQ\java\lib64;C:\Program Files\IBM\WebSphere MQ\java\lib MQ_JRE_PATH=C:\Program Files\IBM\WebSphere MQ\java\jre Then issue: C:\> set-mq-80 Version: 8.0.0.9 Notice more environment variables (in bold): C:\> set MQ MQ_DATA_PATH=C:\ProgramData\IBM\MQ MQ_ENV_MODE=64 MQ_FILE_PATH=C:\Program Files\IBM\WebSphere MQ MQ_INSTALLATION_NAME=Installation1 MQ_INSTALLATION_PATH=C:\Program Files\IBM\WebSphere MQ MQ_JAVA_DATA_PATH=C:\ProgramData\IBM\MQ MQ_JAVA_INSTALL_PATH=C:\Program Files\IBM\WebSphere MQ\java MQ_JAVA_LIB_PATH=C:\Program Files\IBM\WebSphere MQ\java\lib64 MQ_JRE_PATH=C:\Program Files\IBM\WebSphere MQ\java\jre Now display the version-fixpack level: C:\> dspmqver Name: WebSphere MQ Version: 8.0.0.9 Level: p800-009-180321.1 BuildType: IKAP - (Production) Platform: WebSphere MQ for Windows (x64 platform) Mode: 64-bit O/S: Windows 10 Professional x64 Edition, Build 18363 InstName: Installation1 InstDesc: Primary: Yes InstPath: C:\Program Files\IBM\WebSphere MQ DataPath: C:\ProgramData\IBM\MQ MaxCmdLevel: 802 LicenseType: Production

of 47

Display the MQ installations: C:\> dspmqinst InstName: Installation1 InstDesc: Identifier: 1 InstPath: C:\Program Files\IBM\WebSphere MQ Version: 8.0.0.9 Primary: Yes State: Available MSIProdCode: {74F6B169-7CE6-4EFB-8A03-2AA7B2DBB57C} MSIMedia: 8.0 Server MSIInstanceId: 1set-mq-80 Version: 8.0.0.9 Display the queue manager together with the installation, version and status: C:\> dspmq -o installation -s QMNAME(QM80) STATUS(Running) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.9) + UnxUtils package The UNIX "which" command is not native to Windows, but it is used in this tutorial to show the directory where an executable file is located. Note: The Windows “where” command is a close relative to Unix “which”. The UnxUtils.zip and UnxUpdates.zip packages contain the "which" utility. These zip files can be downloaded from: http://sourceforge.net/projects/unxutils/files/ Download file: UnxUtils.zip http://unxutils.sourceforge.net/UnxUpdates.zip Download file: UnxUpdates.zip For details on the utilities that are provided in these packages, see: http://unxutils.sourceforge.net/ GNU utilities for Win32

http://sourceforge.net/projects/unxutils/files/

http://unxutils.sourceforge.net/UnxUpdates.zip

http://unxutils.sourceforge.net/

of 47

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 1: Installing MQ 9.1 side-by-side to MQ 8.0 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The MQ 9.1 installation will NOT be designated as Primary. ++ All queue manager data is stored in a common directory structure Even though the executable code for each version of MQ is stored in a different directory structure, the data for all the queue managers, regardless of the version, is stored in: MQ_DATA_PATH=C:\ProgramData\IBM\MQ ++ Downloading the MQ 9.1 code Download the code from IBM Passport Advantage. Consult the following technote for the Part Numbers that you can use to quickly identify the MQ 9.1 downloadable components for installation: https://www.ibm.com/support/pages/downloading-ibm-mq-version-910 Downloading IBM MQ Version 9.1.0 For this tutorial, the following file was downloaded: CNRE9ML IBM MQ V9.1 for Windows 64-bit eImage The file was downloaded into the directory: C:\downloads\mq9100 The downloaded file has the following name: IBM_MQ_9.1_WINDOWS.zip ++ Current setup of MQ 8.0 MQ 8.0 is already installed in the default location (MQ_INSTALLATION_PATH): C:\Program Files\IBM\WebSphere MQ For completeness, here is the default location for the "data" for the queue managers is (MQ_DATA_PATH): C:\ProgramData\IBM\MQ ++ Installing MQ 9.1 Login as an Administrator. MQ 9.1 will be installed in its default location: C:\Program Files\IBM\MQ


of 47

Go to the directory where the downloaded file is located: C:\downloads\mq9100 Unzip the downloaded file. The files will be extracted into a new subdirectory called: MQServer Go inside the new subdirectory and start the installer: setup.exe Click on "Software Requirements", in this case the requirements were met. Click on "Network Configuration" In this case, the machine is not part of a Domain; thus, there is no need to indicate a domain user and the answer to the question is "No" Click on "IBM MQ Installation". Click on "Launch IBM MQ Installer” The installer detects that there are other installations in the box:

For this tutorial, we want to leave the other installations intact. Thus, select the first entry: Install leaving the existing installation(s) untouched Click Next. Accept the license.

of 47

For this tutorial select the “Custom” installation.

Click Next. In the Installation Details you will see: Installation Name: Installation2 Installation folder for program files: C:\Program Files\IBM\MQ

of 47

The list of features to be installed will be shown. Notice that some items are NOT selected by default: Telemetry, Managed File Transfer, Advanced Message Security. However, notice that the “MQI Client” is not selected. It is highly recommended that you install it. Therefore, for this tutorial, the “MQI Client” is explicitly selected:

Click Next. In the screen titled "Ready to Install IBM MQ" you will see the summary of the Installation Name, location, components to install, etc. Click Install to proceed. The copying of the files into the installation directory structure will begin. After the copying the files, a dialog will appear that says: The IBM MQ Installation Wizard has successfully installed IBM MQ. Click Finish After the installation, you will see the following dialog: Welcome to the Prepare IBM MQ Wizard Because this scenario is not using a Windows Domain, accept the default of "No".

of 47

Accept to launch the MQ Explorer 9.1 and unless you have a very specific reason, you can accept the default setting: (*) Start MQ Explorer with a new workspace

of 47

++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 2: Need to run setmqenv to use MQ 9.1 or MQ 8.0 commands ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Now that we finished with the installation activities, let's verify that there are several directories with the MQ executables:

Open the Windows Explorer for the Drive where you installed the MQ code, such as: Note that there are 2 locations: C:\Program Files\IBM\MQ => MQ 9.1 C:\Program Files\IBM\WebSphere MQ => MQ 8.0 Start a Windows command prompt, such as in Windows 10: Start > Windows System > Command prompt

There is a new MQ command, dspmqinst, that will display the different versions installed in the system without the need to take a look at the directories. In Unix/Linux, the information on the installations is stored in the file: /etc/opt/mqm/mqinst.ini But in Windows, there is no file mqinst.ini and instead, the information is kept in the registry. The installation configuration information is held in the following key on Windows systems: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere MQ\Installation

of 47

This key must not be edited or referenced directly since its format is not fixed, and could change. Let's display the entries: InstName: Installation1 InstDesc: Identifier: 1 InstPath: C:\Program Files\IBM\WebSphere MQ Version: 8.0.0.9 Primary: Yes State: Available MSIProdCode: {74F6B169-7CE6-4EFB-8A03-2AA7B2DBB57C} MSIMedia: 8.0 Server MSIInstanceId: 1 InstName: Installation2 InstDesc: Identifier: 2 InstPath: C:\Program Files\IBM\MQ Version: 9.1.0.0 Primary: No State: Available MSIProdCode: {5D3ECA81-BF8D-4E80-B36C-CBB1D69BC110} MSIMedia: 9.1 Server MSIInstanceId: 1 Notice that the values for InstName are very important! "Installation1" refers to MQ 8.0 "Installation2" refers to MQ 9.1 + Now, let's display the version of MQ using the default (or primary) installation: C:\> dspmqver Name: WebSphere MQ Version: 8.0.0.9 Level: p800-009-180321.1 BuildType: IKAP - (Production) Platform: WebSphere MQ for Windows (x64 platform) Mode: 64-bit O/S: Windows 10 Professional x64 Edition, Build 18363 InstName: Installation1 InstDesc: Primary: Yes InstPath: C:\Program Files\IBM\WebSphere MQ DataPath: C:\ProgramData\IBM\MQ

of 47

MaxCmdLevel: 802 LicenseType: Production Note there are a number (1) of other installations, use the '-i' parameter to display them. C:\> where dspmqver C:\Program Files\IBM\WebSphere MQ\bin64\dspmqver.exe C:\Program Files\IBM\WebSphere MQ\bin\dspmqver.exe ++ Question: How can we display the version of the newly installed MQ? Answer: You need to run the new MQ 9.1 "setmqenv" command and specify the proper installation. In this case it is Installation2. C:\> setmqenv -n Installation2 Now let's try again to display the version: C:\> where dspmqver C:\Program Files\IBM\MQ\bin64\dspmqver.exe C:\Program Files\IBM\MQ\bin\dspmqver.exe C:\> dspmqver Name: IBM MQ Version: 9.1.0.0 Level: p910-L180705 BuildType: IKAP - (Production) Platform: IBM MQ for Windows (x64 platform) Mode: 64-bit O/S: Windows 10 Professional x64 Edition, Build 18363 InstName: Installation2 InstDesc: Primary: No InstPath: C:\Program Files\IBM\MQ DataPath: C:\ProgramData\IBM\MQ MaxCmdLevel: 910 LicenseType: Production After setmqenv the MQ related variables point to the MQ 9.1 installation: C:\> set MQ MQ_DATA_PATH=C:\ProgramData\IBM\MQ MQ_ENV_MODE=64 MQ_FILE_PATH=C:\Program Files\IBM\MQ MQ_INSTALLATION_NAME=Installation2 MQ_INSTALLATION_PATH=C:\Program Files\IBM\MQ MQ_JAVA_DATA_PATH=C:\ProgramData\IBM\MQ

of 47

MQ_JAVA_INSTALL_PATH=C:\Program Files\IBM\MQ\java MQ_JAVA_LIB_PATH=C:\Program Files\IBM\MQ\java\lib64 MQ_JRE_PATH=C:\Program Files\IBM\MQ\java\jre +++ Hint: You can create a batch file that will run the setmqenv command with the specified syntax. Ensure to have this batch file in a directory in your PATH (such as C:\WinTools) For example, the batch file set-mq-910.bat can be created with the contents: ============= begin batch file (do NOT include this line!) REM Setup the environment to run MQ 9.1 CALL "C:\Program Files\IBM\MQ\bin\setmqenv" -n Installation2 REM Adding Samples to the path SET PATH=%PATH%;%MQ_FILE_PATH%\Tools\c\Samples\Bin;%MQ_FILE_PATH%\Tools\c\Samples\Bin64;%MQ_FILE_PATH%\Tools\jms\samples;%MQ_JAVA_INSTALL_PATH%\bin\ dspmqver -f 2 ============= end batch file (do NOT include this line!) Notice a couple of points: 1) Need to use the "CALL" argument when invoking setmqenv. Without this argument, the execution of setmqenv will terminate the batch and will not allow following statements to execute. That is, with the CALL, you allow other statements in the batch file to be executed. 2) If you add an MQ directory into your PATH, such as the location for the C-samples: PATH=…;C:\Program Files\IBM\MQ\tools\c\Samples\Bin;… Then this directory will be REMOVED by setmqenv the next time is run. If you want to be able to run the C-samples from MQ 9.1, then the last line in the above batch file is needed, in order to place back into the PATH the directory for the samples. Notice also that MQ_FILE_PATH is used in order to use the proper directory structure for MQ 9.1: SET PATH=%PATH%;%MQ_FILE_PATH%\tools\c\Samples\Bin

of 47

++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 3: Creating a queue manager under MQ 9.1 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Before we create a queue manager under MQ 9.1, let's show the current queue managers created under MQ 8.0. C:\> set-mq-91 Display the status of the queue managers: C:\> dspmq QMNAME(QM80) STATUS(Running) QMNAME(QMMIG) STATUS(Running) There is an additional parameter to dspmq -o installation which will show the queue managers with the following information: - the installation name: INSTNAME(Installaton1) - the path of the MQ code: INSTPATH(C:\Program Files\IBM\WebSphere MQ) - and the version: INSTVER(8.0.0.9) Also, parameter -s will show the status. C:\> dspmq -o installation -s QMNAME(QM80) STATUS(Running) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.9) QMNAME(QMMIG) STATUS(Running) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.9) + Let's create a new queue manager under MQ 9.1: You could use also the MQ Explorer 9.1 to create the queue manager. The crtmqm is used here to illustrate the new informational text that is displayed to indicate that Installation2 is used. C:\> crtmqm -u SYSTEM.DEAD.LETTER.QUEUE QM910 AMQ7077: You are not authorized to perform the requested operation. Wait a second! I am an Administrator and I should have the proper authority to create a new MQ queue manager! What is going on?

of 47

The answer is that you need to open a Windows Command Prompt as an Administrator. Start > Windows System > Command Prompt > More > Run as administrator

Notice that the title for the window will say: Administrator: Command Prompt

Notice that the version of MQ in the Command Prompt will be MQ 8.0: C:\Users\Administrator> dspmqver -f2 Version: 8.0.0.9 You will need to run setmqenv or the batch file set-mq-910: C:\> set-mq-910 Version: 9.1.0.0

of 47

C:\> crtmqm -u SYSTEM.DEAD.LETTER.QUEUE QM910 IBM MQ queue manager created. Directory 'C:\ProgramData\IBM\MQ\qmgrs\QM910' created. The queue manager is associated with installation 'Installation2'. Creating or replacing default objects for queue manager 'QM910'. Default objects statistics : 87 created. 0 replaced. 0 failed. Completing setup. Setup completed. Then start the queue manager. Notice the lines that indicate the installation and the version under which the queue manager is running: C:\> strmqm QM910 IBM MQ queue manager 'QM910' starting. The queue manager is associated with installation 'Installation2'. 5 log records accessed on queue manager 'QM910' during the log replay phase. Log replay for queue manager 'QM910' complete. Transaction manager state recovered for queue manager 'QM910'. IBM MQ queue manager 'QM910' started using V9.1.0.0. Let's display again the installed queue managers and showing the installation, code path and version. Notice the values for the new queue manager, which reflect the association with the MQ 9.1 installation. C:\> dspmq -o installation -s QMNAME(QM80) STATUS(Running) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.9) QMNAME(QMMIG) STATUS(Running) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.9) QMNAME(QM910) STATUS(Running) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.0) ++ Cannot use MQ 9.1.0 administrative commands to run an MQ 8.0 queue manager You cannot use MQ 9.1.0 administrative commands to run an MQ 8.0 queue manager Corollary: And vice versa, you cannot use MQ 8.0 administrative commands to run an MQ 9.1.0 queue manager. Just for the sake of illustrating that each queue manager needs to be run with the proper level of the code, the following shows the error message when trying to use the MQ 9.1.0 endmqm command on a queue manager that was started with MQ 8.0: Right now, the environment has been set to use MQ 9.1.0 commands.

of 47

C:\> set-mq-910 Version: 9.1.0.0 C:\> endmqm -i QM80 AMQ5691E: Queue manager 'QM80' is associated with a different installation ('Installation1'). Similarly, if we enable now the MQ 8.0 commands … C:\> set-mq-80 Version: 8.0.0.9 C:\> endmqm -i QM910 AMQ5691: Queue manager 'QM910' is associated with a different installation ('Installation2').

of 47

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 4: Remote access to the new MQ 9.1 queue manager ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Let's customize the queue manager to allow it to be monitored remotely by the MQ Explorer and to create a local queue Q1 for initial testing: The following tutorial provides more details. https://www.ibm.com/support/pages/node/1135522 Configuring MQ to use a dedicated Listener, Channel and Queue in Linux Here is an excerpt of the commands. C:\> runmqsc QM910 ## Define a listener for all users. The default is port 1416. define listener(LISTENER) trptype(tcp) control(qmgr) port(1416) start listener(LISTENER) ## Define a channel to be used by a remote MQ Explorer define channel(SYSTEM.ADMIN.SVRCONN) chltype(SVRCONN) ## Define test queue: define qlocal(Q1) ## Security note: the following ALTER is not suitable for PRODUCTION but might be suitable for TEST queue managers. ## For testing queue managers: disable userid/password for remote users ALTER AUTHINFO(SYSTEM.DEFAULT.AUTHINFO.IDPWOS) + AUTHTYPE(IDPWOS) CHCKCLNT(OPTIONAL) REFRESH SECURITY TYPE(CONNAUTH) ## Security note: the following CHLAUTH records may not be suitable for PRODUCTION but might be suitable for TEST queue managers. ## For testing queue managers: allow MQ Administrator to remotely access the queue manager SET CHLAUTH(*) TYPE(BLOCKUSER) USERLIST('nobody','*MQADMIN') SET CHLAUTH(SYSTEM.ADMIN.*) TYPE(BLOCKUSER) USERLIST('nobody') SET CHLAUTH(SYSTEM.DEF.SVRCONN) TYPE(ADDRESSMAP) ADDRESS(*) + USERSRC(CHANNEL) SET CHLAUTH(SYSTEM.DEF.*) TYPE(BLOCKUSER) USERLIST('nobody') end


of 47

Now you start the MQ Explorer 9.1 from a remote host, using a userid that is an MQ Administrator in the host that has the newly created queue manager.

of 47

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 5: Migrating an MQ 8.0 queue manager to MQ 9.1 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ After installing MQ 9.1, you now want to migrate/upgrade an MQ 8.0 queue manager to be used with MQ 9.1. It is necessary to perform 2 steps: 1: Use “setmqm” to associate the queue manager with the desired installation (MQ version). 2: Use “strmqm” under the desired version, which will update the data of the queue manager for the new version. For this tutorial, the queue manager QMMIG which was created with MQ 8.0 is going to be used as illustration of the upgrade procedure. + Take a backup of the queue manager: Once a queue manager has been migrated to MQ 9.1, it is no longer possible to use it with the previous version of MQ. The migration process changes a number of files and object definitions, and it is not possible to go back. If you are running MQ 8.0 and you want to upgrade to MQ 9.1, then you must do a backup before upgrading. When you use the first strmqm to start the queue manager at version 9.1, the strmqm program will change the formats of certain MQ object files and this cannot be reversed. For more information on the backup and restore activities, please see: https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.con.doc/q018580_.htm IBM MQ 9.1.x / IBM MQ / Configuring / Configuring high availability, recovery and re-start / Backing up and restoring IBM® MQ queue manager data + For MQ 7.0: Use the “saveqmgr” utility from the SupportPac MS03 Use the saveqmgr command to capture the object definitions and authorities. This utility is provided with the following supportpac:

http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24000673 MS03: WebSphere MQ - Save Queue Manager object definitions using PCFs Example: The following saves both the objects and the authority records (each in one single line): UNIX: saveqmgr -m QMgr -f /tmp/mq/qm_data.mqs -z /tmp/mq/qm_auth.sh

https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.con.doc/q018580_.htm


http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24000673

of 47

Windows: saveqmgr.exe -m QMgr -f C:\temp\mq\qm_data.mqs -z C:\temp\mq\qm_auth.bat + For MQ 7.1 or later: Use new feature dmpmqcfg The dmpmqcfg tool is new in MQ 7.1 and it is an alternative to the SupportPac MS03. Here are the main references from the MQ 7.1 Information Center. https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.ref.adm.doc/q083160_.htm IBM MQ 9.1.x / IBM MQ / Reference / Administration reference / IBM MQ control commands reference / dmpmqcfg (dump queue manager configuration) https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.con.doc/q018650_.htm IBM MQ 9.1.x / IBM MQ / Configuring / Configuring high availability, recovery and re-start / Backing up and restoring IBM MQ queue manager data Backing up queue manager configuration Summary: Default - only attributes that are different than the default (except setmqaut, which are not included in the output) dmpmqcfg -m QMgr > QMgr.dmpmqcfg.out.mqsc Specify all attributes, including default ones (except setmqaut, which are not includ-ed in the output) dmpmqcfg -m QMgr -a > QMgr.dmpmqcfg.out.all.mqsc Capture the authentication records in setmqaut format Windows: dmpmqcfg -m QMgr -o setmqaut > QMgr.dmpmqcfg.setmqaut.bat Unix: dmpmqcfg -m QMgr -o setmqaut > QMgr.dmpmqcfg.setmqaut.sh Note: The output file that has the setmqaut commands, includes the name of the queue manager in each command. Thus, if you want to restore the commands into a different queue manager, you will need to edit the file and specify the desired queue manager name. To restore - play back the commands for runmqsc: runmqsc Qmgr < QMgr.dmpmqcfg.out.mqsc or runmqsc Qmgr < QMgr.dmpmqcfg.out.all.mqsc To restore the setmqaut commands: Windows: QMgr.dmpmqcfg.setmqaut.bat

https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.ref.adm.doc/q083160_.htm

https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.ref.adm.doc/q083160_.htm



of 47

Unix: chmod 755 QMgr.dmpmqcfg.setmqaut.sh ./ QMgr.dmpmqcfg.setmqaut.sh Because the queue manager to be migrated is at MQ 8.0, you need to run the script that sets the running environment to MQ 8.0: C:\> set-mq-80 C:\> dspmqver Name: WebSphere MQ Version: 8.0.0.9 Ensure that the queue manager is running: C:\> where dspmq C:\Program Files\IBM\WebSphere MQ\bin64\dspmq.exe C:\Program Files\IBM\WebSphere MQ\bin\dspmq.exe C:\> dspmq -m QMMIG -o installation -s QMNAME(QMMIG) STATUS(Running) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.9) Notice that the value for the attribute CMDLEVEL for the queue manager is 800: C:\> runmqsc QMMIG display qmgr cmdlevel version 1 : display qmgr cmdlevel AMQ8408: Display Queue Manager details. QMNAME(QMMIG) CMDLEVEL(800) VERSION(08000009) end Stop the queue manager C:\> endmqm -i QMMIG WebSphere MQ queue manager 'QMMIG' ending. WebSphere MQ queue manager 'QMMIG' ended. Change the environment to run the MQ 9.1 commands C:\> set-mq-910 Version: 9.1.0.0 C:\> dspmqver Name: IBM MQ Version: 9.1.0.0

of 47

Display the status of the queue managers. C:\> where dspmq C:\Program Files\IBM\MQ\bin64\dspmq.exe C:\Program Files\IBM\MQ\bin\dspmq.exe C:\> dspmq -o installation -s QMNAME(QM80) STATUS(Running) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.9) QMNAME(QMMIG) STATUS(Ended immediately) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.9) QMNAME(QM910) STATUS(Running) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.0) Use strmqm to start the queue manager. Because the queue manager was last used with MQ 8.0, then the strmqm at MQ 9.1 will proceed to upgrade the queue manager. C:\> strmqm QMMIG AMQ5691E: Queue manager 'QMMIG' is associated with a different installation ('Installation1'). Hum, what happened! Why did the strmqm program from MQ 9.1 did not handle the request as expected? Because the queue manager QMMIG is still associated with MQ 8.0. It is necessary to reassign QMMIG from MQ 8.0 to MQ 9.1 via the command setmqm. + The following MQ command: dspmqinf QMMIG … shows the stanza for the desired queue manager that exists in the file that has the index of the queue managers… C:\ProgramData\IBM\MQ\mqs.ini In this case, the output is: C:\> dspmqinf QMMIG QueueManager: Name=QMMIG Directory=QMMIG Prefix=C:\ProgramData\IBM\MQ InstallationName=Installation1

of 47

Notice that this queue manager is associated with Installation1 To find out the MQ version for Installation1, use: C:\> dspmqinst -n Installation1 InstName: Installation1 InstDesc: Identifier: 1 InstPath: C:\Program Files\IBM\WebSphere MQ Version: 8.0.0.9 Primary: Yes State: Available MSIProdCode: {74F6B169-7CE6-4EFB-8A03-2AA7B2DBB57C} MSIMedia: 8.0 Server MSIInstanceId: 1 OK, the previous 2 commands indicate that the queue manager QMMIG is associated with Installation1, which is the installation for MQ 8.0.0.9. To see all the MQ installations, you can use the following command: C:\> dspmqinst InstName: Installation1 InstDesc: Identifier: 1 InstPath: C:\Program Files\IBM\WebSphere MQ Version: 8.0.0.9 Primary: Yes State: Available MSIProdCode: {74F6B169-7CE6-4EFB-8A03-2AA7B2DBB57C} MSIMedia: 8.0 Server MSIInstanceId: 1 InstName: Installation2 InstDesc: Identifier: 2 InstPath: C:\Program Files\IBM\MQ Version: 9.1.0.0 Primary: No State: Available MSIProdCode: {5D3ECA81-BF8D-4E80-B36C-CBB1D69BC110} MSIMedia: 9.1 Server MSIInstanceId: 1 Notice that Installation2 is for MQ 9.1.

of 47

Therefore, we need to: - disassociate the queue manager QMMIG from Installation1 (MQ 8.0) and - associate it with Installation2 (MQ 9.1). + Question: What action needs to be done to associate the desired queue manager to the installation for MQ 9.1? Answer: Need to specify the MQ command: setmqm The following command associates the desired queue manager with Installation2 (MQ 9.1): C:\> setmqm -m QMMIG -n Installation2 The setmqm command completed successfully. Now the queue manager is associated with Installation2. C:\> dspmqinf QMMIG QueueManager: Name=QMMIG Directory=QMMIG Prefix=C:\ProgramData\IBM\MQ InstallationName=Installation2 Proceed to start the queue manager. Because this is the first time that the MQ strmqm 9.1 command is being issued on a queue manager that a prior use with an older release (8.0), then it will do a migration: C:\> strmqm QMMIG IBM MQ queue manager 'QMMIG' starting. The queue manager is associated with installation 'Installation2'. 5 log records accessed on queue manager 'QMMIG' during the log replay phase. Log replay for queue manager 'QMMIG' complete. Transaction manager state recovered for queue manager 'QMMIG'. Migrating objects for queue manager 'QMMIG'. Default objects statistics : 5 created. 0 replaced. 0 failed. IBM MQ queue manager 'QMMIG' started using V9.1.0.0. Now display the attributes for the queue manager using runmqsc. Notice the CMDLEVEL and the new VERSION fields:

of 47

C:\> runmqsc QMMIG display qmgr cmdlevel version 1 : display qmgr cmdlevel version AMQ8408I: Display Queue Manager details. QMNAME(QMMIG) CMDLEVEL(910) VERSION(09010000) end + For more information on the new attributes and queues that were added in MQ 9.0 and MQ 9.1, see the following technotes: http://www.ibm.com/support/docview.wss?uid=swg21578742 New WebSphere MQ 7.1, 7.5, 8.0, 9.0 and 9.1 attributes in DISPLAY QMGR for new or migrated queue managers http://www.ibm.com/support/docview.wss?uid=swg21608033 New SYSTEM queues added in WebSphere MQ 7.1, 7.5, 8.0, 9.0, 9.0.1 and 9.1 http://www-01.ibm.com/support/docview.wss?uid=swg21620936 New objects and new attributes for objects in WebSphere MQ 7.1, 7.5, 8.0, 9.0, 9.0.1 and 9.1



http://www-01.ibm.com/support/docview.wss?uid=swg21620936

of 47

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 6: Installing fix pack MQ 8.0.0.14 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This chapter describes the steps to install the fix pack 8.0.0.14 on top of the installed 8.0.0.9 on a system that has multi-version installations of MQ. The InstallAnywhere tool will ask you eventually which is the Installation Name that you want to upgrade. Depending on how the upgrade goes, you very likely will need to reboot the Windows server. For this scenario, there is another installed version (9.1) and the queue managers running under that other version will NOT be stopped in order to demonstrate that you can continue using those other versions while performing maintenance activities for 8.0.x.x. Log in as an Administrator. If you created the batch file "set-mq-80" mentioned earlier in this document, then issue it: C:\> set-mq-80 Version: 8.0.0.9 In this case, QMMIG and QM910 are running under MQ 9.1, while QM80 is running under MQ 8.0: C:\> dspmq -o installation -s QMNAME(QM80) STATUS(Running) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.9) QMNAME(QMMIG) STATUS(Running) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.0) QMNAME(QM910) STATUS(Running) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.0) ++ Need to stop the MQ 8.0 processes before installing the fix pack The following section of the MQ 8.0 online documentation describes the steps to stop the MQ processes prior to performing maintenance to the MQ code (such as applying a fix pack). https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q007691_.htm IBM MQ 8.0.0 / IBM MQ / Migrating and upgrading IBM MQ / IBM MQ maintenance tasks (On platforms other than z/OS ) / Applying and removing maintenance level up-dates (On platforms other than z/OS ) /

https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q007691_.htm


of 47

Applying and removing maintenance on Windows Here is a summary and excerpt of the main steps. Stop all applications using the MQ installation for 8.0. In this case we know that the queue manager QM80 is running under MQ 8.0 C:\> endmqm -i QM80 Stop the IBM MQ service for the installation. Right-click the WebSphere MQ icon in the taskbar > click Stop WebSphere MQ.

++ Downloading the fix pack The following technote announces the fix pack 8.0.0.14 and provides links to the IBM Fix Central to download the appropriate filesets: https://www.ibm.com/support/pages/node/712857 Recommended Fixes for IBM MQ In particular for MQ 8.0.0.14, the link is: https://www.ibm.com/support/pages/node/1282120 Fix Pack 8.0.0.14 for WebSphere MQ v8 The following technote has links to different technotes that list the fixes addressed in a given fix pack. http://www.ibm.com/support/docview.wss?rs=171&uid=swg21254675 Fixes by version for WebSphere MQ



http://www.ibm.com/support/docview.wss?rs=171&uid=swg21254675

of 47

In particular for MQ 8.0: https://www.ibm.com/support/pages/node/713099 Fix list for IBM MQ Version 8.0 In this scenario, the file set for 8.0.0.14 for Windows was downloaded into the following directory:

C:\downloads\mq80014\ The file name is: 8.0.0-WS-MQ-Windows-FP0014.zip Extract the files from the zip file.


of 47

Execute the following file: WS-MQ-8.0.0-FP0014.exe

You will see a dialog:

Title: InstallAnywhere Contents: InstallAnywhere is preparing to install ...

You need to wait until the preparation is over, which may take several minutes. Then you will see another window: IBM WebSphere MQ (fix pack 8.0.0.14 files) Click OK to continue.

of 47

You will see the information for the section “Introduction”. Click Next.

You will see the section “Installation Type”. Most people do not choose the default, which is the top option: Load files only Instead, they choose this one that is more practical:

(*) Load files and apply fix pack Click Next.

You will see the section “Information” Click Next.

of 47

You will see the section “Destination Folder” Accept the default location to save the files. In this case: C:\Program Files\IBM\source\WebSphere MQ 8.0.0.14 Click Next.

You will see the section “Advanced Options”. Click Next.

You will see the section “Pre-installation summary” Click Install.

of 47

You will see the section “Loading…” which has a progress indicator.

You have to wait for the Loading process to finish. After the Loading process is completed, then you will see the section “Apply Fix Pack”. Click Done.

You will see another dialog where you can select which is the Installation that you want to upgrade. In this case it is: Installation1 (8.0.0.9) Click OK

of 47

Accept the default for the Backup Folder. Click “Apply”.

There will be more dialogs with progress indicators. NOTE: Depending on how the upgrade goes, you very likely will need to reboot the Windows server. After the reboot, open a Windows command prompt and execute the following commands. Notice the new fix pack level of 8.0.0.14. C:\> set-mq-80 Version: 8.0.0.14 C:\> dspmq -o installation -s QMNAME(QM80) STATUS(Ended immediately) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.14) QMNAME(QMMIG) STATUS(Ended unexpectedly) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.0) QMNAME(QM910) STATUS(Ended immediately) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.0) Start the desired MQ 8.0 queue manager. C:\> strmqm QM80 WebSphere MQ queue manager 'QM80' starting. The queue manager is associated with installation 'Installation1'. 5 log records accessed on queue manager 'QM80' during the log replay phase. Log replay for queue manager 'QM80' complete. Transaction manager state recovered for queue manager 'QM80'. WebSphere MQ queue manager 'QM80' started using V8.0.0.14.

of 47

C:\> runmqsc QM80 display qmgr cmdlevel version 1 : display qmgr cmdlevel version AMQ8408: Display Queue Manager details. QMNAME(QM80) CMDLEVEL(800) VERSION(08000014) end Notice that the value in the attribute VERSION needs to be interpreted as with dots separating every 2nd digit: 08.00.00.14

of 47

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 7: Installing Fix Pack 9.1.0.4 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This chapter describes the steps to install the fix pack 9.1.0.4 on top of the installed 9.1.0.0 on a system that has multi-version installations of MQ. The InstallAnywhere tool will ask you eventually which is the Installation Name that you want to upgrade. Depending on how the upgrade goes, you very likely will need to reboot the Windows server. For this scenario, there is another installed version (8.0) and the queue managers running under that other version will NOT be stopped in order to demonstrate that you can continue using those other versions while performing maintenance activities for 9.1.x.x. Log in as an Administrator. If you created the batch file "set-mq-910" mentioned earlier in this document, then issue it: C:\> set-mq-910 Version: 9.1.0.0 In this case, QMMIG and QM910 are running under MQ 9.1, while QM80 is running under MQ 8.0: C:\> dspmq -o installation -s QMNAME(QM80) STATUS(Running) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.14) QMNAME(QMMIG) STATUS(Ended unexpectedly) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.0) QMNAME(QM910) STATUS(Ended immediately) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.0) ++ Need to stop the MQ 9.1.0 processes before installing the fix pack The following section of the MQ 9.1.0 online documentation describes the steps to stop the MQ processes prior to performing maintenance to the MQ code (such as applying a fix pack). https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.ibm.mq.mig.doc/q007691_.htm IBM MQ 9.1.x / IBM MQ / Maintaining and migrating / Applying maintenance to IBM MQ / Applying and removing maintenance on Windows



of 47

Here is a summary and excerpt of the main steps. Stop all applications using the MQ installation for 9.1.0. In this case we know that the queue managers QMMIG and QM910 are running under MQ 9.1.0 C:\> endmqm -i QMMIG C:\> endmqm -i QM910 Stop the IBM MQ service for the installation. Right-click the WebSphere MQ icon in the taskbar > click Stop WebSphere MQ.

++ Downloading the fix pack The following technote announces the fix pack 8.0.0.14 and provides links to the IBM Fix Central to download the appropriate filesets: https://www.ibm.com/support/pages/node/712857 Recommended Fixes for IBM MQ In particular for MQ 9.1.0.4, the link is: https://www.ibm.com/support/pages/downloading-ibm-mq-version-9104 Downloading IBM MQ Version 9.1.0.4 The following technote has links to different technotes that list the fixes addressed in a given fix pack. http://www.ibm.com/support/docview.wss?rs=171&uid=swg21254675 Fixes by version for WebSphere MQ



http://www.ibm.com/support/docview.wss?rs=171&uid=swg21254675

of 47

In particular for MQ 9.1.0. LTS: https://www.ibm.com/support/pages/node/740167 Fix list for IBM MQ Version 9.1 LTS In this scenario, the file set for 9.1.0.4 for Windows was downloaded into the following directory: C:\downloads\mq9104 The file name is: 9.1.0-IBM-MQ-Win64-FP0004.zip Extract the files from the zip file.


of 47

Execute the following file: IBM-MQ-9.1.0-FP0004.exe

You will see a dialog:

Title: InstallAnywhere Contents: InstallAnywhere is preparing to install ...

You need to wait until the preparation is over, which may take several minutes. Then you will see another window: IBM MQ (fix pack 9.1.0.4 files)

Click OK to continue.

of 47

You will see the information for the section “Introduction”. Click Next.

You will see the section “Installation Type”. Most people do not choose the default, which is the top option: Load files only Instead, they choose this one that is more practical:

(*) Load files and apply fix pack Click Next.

of 47

You will see the section “Information” Click Next.

You will see the section “Destination Folder” Accept the default location to save the files. In this case: C:\Program Files\IBM\source\WebSphere MQ 8.0.0.14 Click Next.

You will see the section “Advanced Options”. Click Next.

of 47

You will see the section “Pre-installation summary” Click Install.

You will see the section “Loading…” which has a progress indicator.

You have to wait for the Loading process to finish. After the Loading process is completed, then you will see the section “Apply Fix Pack”. Click Done.

of 47

You will see another dialog where you can select which is the Installation that you want to upgrade. In this case it is: Installation2 (9.1.0.0) Click OK

Accept the default for the Backup Folder. Click “Apply”.

There will be more dialogs with progress indicators. The last dialog looks like this. Click “Finish”.

of 47

NOTE: Depending on how the upgrade goes, you very likely will need to reboot the Windows server. After the reboot, open a Windows command prompt and execute the following commands. Notice the new fix pack level of 9.1.0.4. C:\> set-mq-910 Version: 9.1.0.4 C:\> dspmq -o installation -s C:\ProgramData\IBM\MQ>dspmq -o installation -s QMNAME(QM80) STATUS(Ended unexpectedly) INSTNAME(Installation1) INSTPATH(C:\Program Files\IBM\WebSphere MQ) INSTVER(8.0.0.14) QMNAME(QMMIG) STATUS(Ended unexpectedly) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.4) QMNAME(QM910) STATUS(Ended immediately) INSTNAME(Installation2) INSTPATH(C:\Program Files\IBM\MQ) INSTVER(9.1.0.4) Start the desired MQ 9.1.0 queue manager. C:\> strmqm QM910 IBM MQ queue manager 'QM910' starting. The queue manager is associated with installation 'Installation2'. 5 log records accessed on queue manager 'QM910' during the log replay phase. Log replay for queue manager 'QM910' complete. Transaction manager state recovered for queue manager 'QM910'. IBM MQ queue manager 'QM910' started using V9.1.0.4. C:\> runmqsc QM910 display qmgr cmdlevel version 1 : display qmgr cmdlevel version AMQ8408I: Display Queue Manager details. QMNAME(QM910) CMDLEVEL(910) VERSION(09010004) end Notice that the value in the attribute VERSION needs to be interpreted as with dots separating every 2nd digit: 09.01.00.04

of 47

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 8: Uninstallation ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The following tutorial applies to MQ 8.0 and MQ 9.1, and includes all the steps that are needed to uninstall MQ in Windows. http://www.ibm.com/support/docview.wss?uid=swg27050128 Uninstalling MQ 9.0 components in Windows (example Telemetry) The objective of this techdoc is to show all the steps to uninstall one component for MQ 9.0 on Windows. In order to provide concrete steps, the following component will be uninstalled:

MQ Telemetry Service The techdoc has the following chapters: Chapter 1: Stopping the queue manager Chapter 2: Invoking the MQ installer (setup.exe) +++ end


installing mq 9.1.0.0 lts to coexist with mq 8.0.0.9 in windows ... · note: the particular fix...

Documents