Collect IBM MQ MustGather data to solve install and uninstall problems on Linux, UNIX, Windows, IBM i and HP Integrity NonStop Server

Resolving The Problem

Please answer these questions about the problem and then follow the steps below:

• What are you trying to install or uninstall?
• What account are you using to perform the installation or uninstallation?

Step 1: Generate Data

It is helpful to gather information from the system when the install or uninstall problem is happening in order to identify the cause:

1. Run the install or uninstall with debug logging enabled in order to gather more detailed information about the failure:
   
   

   Generating debug install and uninstall data on AIX

   
   
   1. Export the environment variable INST_DEBUG=YES, which will direct AIX to log extra debugging information. Then run the install or uninstall, whether you do so through SMIT or by running the installp command directly. For example:
      
      

      Enable debugging on AIX

      
      sh> export INST_DEBUG=YES
      sh> installp...
      
   
   
   
   2. Unset the INST_DEBUG variable when done:
      
      

      Disable debugging on AIX

      
      sh> unset INST_DEBUG
      
   
   
   
   3. The smit.log file, located in the root directory of the system, will contain the debugging information from the install or uninstall attempt.
   
   

   Generating debug install and uninstall data on HP-UX

   
   
   1. Create two files to enable MQ debugging, with the second file specifying a debug level of 2. Then run the install normally, whether you use the System Management Homepage (SMH), System Administration Manager (SAM, used on HP-UX 11.23 and earlier), or the swinstall and swremove commands:
      
      

      Enable debugging on HP-UX

      
      sh> touch /tmp/AMQ_DEBUG_SW_SCRIPTS
      sh> echo 2 > /tmp/wmq_debug_install.
      sh> swinstall...
      
   
   
   

   2. Take note of the install or uninstall job ID. The job ID consists of the system host name followed by a hyphen and a unique number, like myhost.example.com-12345. Use this job ID to retrieve the install debug log into a file. For example:
      
      

      Retrieving the install or uninstall log on HP-UX

      
      sh> swjob -a log myhost.example.com-12345 @ myhost.example.com:/ > /tmp/mqinstall.log
      
   
   
   
   3. Remove the two debugging files when done:
      
      

      Disable debugging on HP-UX

      
      sh> rm /tmp/AMQ_DEBUG_SW_SCRIPTS /tmp/wmq_debug_install
      
   
   

   Generating debug install and uninstall data on Linux

   
   
   1. Add the "-vv" option to the rpm command and capture all output (stdout and stderr) to a file. For example:
      
      

      Generating debug output on Linux

      
      sh> rpm -vv ... 2>&1 | tee mqinstall.log
      
   
   

   Generating debug install and uninstall data on Solaris

   
   
   1. Use the script command to start logging output to a file. For example:
      
      

      Logging screen output to a file

      
      sh> script mqinstall.log
      
   
   
   
   2. Add the "-v" option to the Solaris pkgadd or pkgrm command. For example:
      
      

      Generating debug output on Solaris

      
      sh> pkgadd -v ...
      
   
   
   
   3. Exit the script command to stop logging output. For example:
      
      

      Stop loggin screen output

      
      sh> exit
      
   
   

   Generating debug install and uninstall data on Windows

   
   
   1. Use the msiexec command with the option "/l*vx" to log debugging output to a file. Use the MQ Knowledge Center documentation on Advanced installation using msiexec to determine what addition parameters to use to install or uninstall MQ. For example:
      
      

      Logging Microsoft Installer output to a file

      
      C:\> msiexec /l*vx "C:\mqinstall.log" ...
      
   
   

   Generating debug install and uninstall data on IBM i

   
   
   1. Specify the OUTPUT(*PRINT) option on the RSTLICPGM or DLTLICPGM commands to ensure that a job log is spooled. For example:
      
      

      Logging install and install information to a job log

      
      ===> RSTLICPGM ... OUTPUT(*PRINT)
      
      Then use WRKSPLF option 5 to display the joblog
      
   
   

   Generating debug install and uninstall data on HP Integrity NonStop Server

   
   
   1. Use the script command to start logging output to a file. For example:
      
      

      Logging screen output to a file

      
      osh> script mqinstall.log
      
   
   
   
   2. Run the install or unstall command. For example:
      
      

      Installing on HP Integrity NonStop Server

      
      osh> mqc8_8.0.0.0_hpns-ia64.run ...
      
   
   
   
   3. Exit the script command to stop logging output. For example:
      
      

      Stop loggin screen output

      
      osh> exit
      
   
   



2. Save the output of any errors reported by the install or uninstall process. Take a screen shot of the error, or use a camera phone to capture an image of the problem.

Step 2: Collect Data

1. Record the MQ version and maintenance level currently on the system or identify the version you are attempting to install.



2. Record the operating system version and maintenance level.



3. If your system has more than one MQ installation, record your MQ installation details:



Linux and UNIX


sh> dspmqinst > /tmp/dspmqinst.txt



Windows


C:\> dspmqinst > %TEMP%/dspmqinst.txt




4. On Linux and UNIX systems, include the /etc/opt/mqm/mqinst.ini file, if it exists.



5. On Windows systems, save a copy of the MQ information from the Windows registry information using the amquregn program, if you have an MQ installation available to run it.



6. Record the precise commands you used to start the install or uninstall process. On Linux and Solaris systems, include the crtmqpkg command you used to repackage MQ, if you are working with multiple installations.



7. On AIX systems, collect the smit.log and smit.script files found in the root directory of the system.



8. On Windows systems, collect the MSI installer log file. If you used msiexec, then you will have selected the file name on the command line. Otherwise, include all files named MSI*.*, MQ*.*, and amq*.* located in the %TEMP% directory of the user who attempted the install or uninstall. Include the files amqmsccw.txt and amqmjpse.txt from the IBM MQ data directory, if they exist.



9. On all systems, include the mqpatch.dat and mqpatch.log files from the MQ installation directory, if they exist.



10. On all systems, list the contents (if any) of the directory where you were trying to install, update, or remove MQ. For example:



Linux and UNIX


sh> ls -alR /path/to/mq > mqfiles.txt



Windows


C:\> DIR /S "C:\Program Files\IBM\MQ" > %TEMP%/mqfile.txt



IBM i Qshell


===> ls -alR /QIBM/UserData/mqm /QIBM/ProdData/mqm /QSYS.LIB/QMQM.LIB > /tmp/mqfile.txt



HP Integrity NonStop Server


osh> ls -alR /path/to/mq > mqfiles.txt




11. If you were trying to install WebSphere MQ File Transfer Edition V7.0, collect its install logs as well:



WebSphere MQ File Transfer Edition V7.0 install logs on Linux and UNIX


/opt/IBM/WMQFTE/IBM_WebSphere_MQ_File_Transfer_Edition_*_InstallLog.log



WebSphere MQ File Transfer Edition V7.0 install logs on Windows (may vary)


C:\Program Files\IBM\WMQFTE\IBM_WebSphere_MQ_File_Transfer_Edition_*_InstallLog.log



WebSphere MQ File Transfer Edition V7.0 install logs on IBM i


/QIBM/ProdData/WMQFTE/V7/IBM_WebSphere_MQ_File_Transfer_Edition_*_InstallLog.log




12. Manually package your files for IBM, including files containing the output from the commands listed in Steps 1 and 2. For new installations, skip over any directories or files which do not yet exist on the system.

Step 3: Send Data to IBM

1. Send your data to the IBM ECuRep repository by email to websphere_support@ecurep.ibm.com, by standard or secure HTTP or FTP, or by using the IBM Secure Diagnostic Data Upload Utility (SDDUU) Java application.



2. While the data is transferring, send an email or use the IBM Service Request tool to update your PMR with your description of the problem and of the data you are sending.




A good description of the problem and the data is the most important information you can provide to IBM. Please do not send data without providing a description!



3. Contact your country representative if you need to speak to an IBM technical support representative, or in the US call 1-800-IBM-SERV. Refer to the IBM Software Support Handbook for more information on working with IBM.

Back to top