IBM Support

ITCAM Agents for WebSphere Messaging Version 7.3.0 Fix Pack 03 (7.3.0-TIV-XEforMsg-FP0003) Readme

Fix Readme


Abstract

This is the third fix pack after ITCAM Agents for WebSphere Messaging Version 7.3.0 GA. This fix pack provides support for IBM MQ 9.2 (KMQ agent and KMC agent) and support for IBM App Connect Enterprise 11.0.0 (KQI agent). It also fixes APARs of previous product versions.

Content

1. List of fixes
  The following APARs and critical defects are addressed in this fix pack.
 
  ITCAM agent for WebSphere MQ
    IV75485 - MQ CHANNEL TRANSMIT SPEED SHOWS A HUGE VALUE AT THE TEP
    IV86027 - UNKNOWN OBJECT NAME EVENT IS GENERATED DUE TO KMQ.IRA.AGENT.QUEUE
    IV92780 - SITUATION BASED ON MESSAGE STATISTICS DOES NOT FIRE AND AGENT TERMINATES
    IV93208 - MQ AGENT COULD TERMINATE WITH MQRC_SELECTOR_NOT_FOR_TYP - avoid abort with MQRC_SELECTOR_NOT_FOR_TYPE
    IV93221 - ERROR LOG WORKSPACE DOES NOT SHOW DATA WITH MQ ERROR LOG FILES IN GERMAN
    IV95376 - PRE-REQUISITE CHECKER FAILED WHEN THERE IS ONLY WMQ 9 INSTALLED
    IV96266 - MQ AGENT BECOMES OFFLINE IF THERE ARE MANY ALIAS QUEUES  - queueStatQueue find() call performance issue
    IV97255 - SOME ATTRIBUTES ARE MISSING IN GROUP 'QUEUE LONG TERM HISTORY' IN ONLINE HELP
    IV97799 - ATTRIBUTE ""MAX CHANNELS"" AND ""MAX ACTIVE CHANNELS"" should be ""n/a""  IN CASE OF MONITORING OF REMOTE QMGR
    IV98677 - KMQ agent can not start without compat-libstdc++ library
    IJ00969 - KMQ agent can not correctly parse error log of MQ 9.0.3
    IJ02775 - INCORRECT LOG DATE & TIME IN ERROR LOG WORKSPACE dayFirst format of Error Log Timestamp
    IJ03581 - MQSeries_Events situation returns incorrect Resource Name for Put Inhibited event
    IJ07077 - ERROR LOG WORKSPACE SHOWS NO DATA WITH MESSAGES IN JAPANESE UTF8
    IJ08491 - PRE-REQUISITE CHECK FAILS FOR MQ AGENT ON OS WINDOWS 2016
    IJ11010 - Agent can't get event user id for authority events
    IJ14114 - Maximum Active Channels is showing Incorrect Value in current qmgr status workspace
    IJ18521 - MQ agent get unresponsive when collecting data from large number of queues with queue statistics enabled
    IJ18753 - SUPPORT MONITORING OPTION TO TURN ON/OFF PUBSUB DATA COLLECTION
 
  ITCAM agent for WebSphere Message Broker
    IV91032 - The core dump occurs on Linux when connecting to MQTT server
    IV97262 - REST API is supported to display the message flows under REST API
    IJ06079 - The wrong broker status is reported in TEP                                                         
    IJ10125 - Add parameter KQI_MEM_SIZE in qi.ini to set the java process max memory size
    IJ10142 - kqi agent can't be stopped smoothly
    IJ14670 - THE MULTI-INSTANCE BROKER STATUS CAN'T BE GOT RIGHTLY FOR ACE V11
    IJ17592 - The multi-instance broker status isn't right if the user name includes '_'
    IJ12087 - APM IIB AGENT SHOWS INTEGRATION BROKER "STOPPED" WHEN /BIN/AWK IS MISSING
 
  ITCAM configuration agent for WebSphere MQ
    IV85232 - CONFIGURATION MANAGER MISSING ATTRIBUTES FOR EXISTING OBJECTS.
    IV91719 - ABILITY TO SORT SYMBOLIC VARIABLES IN TEPS.
    IV92834 - TEMS CRASHING WHEN DELETING QUEUE-SHARING GROUP OBJECTS FROM TEMS CONFIGURATOR(KCF).
    IJ00190 - THERE IS AN INCORRECT VALIDATION FOR ATTRIBUTE SSLCIPH FOR CHANNELS ON Z/OS AND OS/400.
    IJ07734 - TEMS CRASHES WHEN IMPORT A XML FILE VIA TEMS CONFIGURATOR GUI IF THE XML FILE CONTAINS A PARTICULAR FORMAT '<xxxx />'.
    IJ11460 - 'WebSphere MQ Version' shows as 'Unknown' in Configuration view of TEP and cases Validate Error: KMC0612E
    IJ13020 - Need to support more Cipher Spec values for MQ 7.5.0 and higher.
    IJ17803 - TEMS crashing when running MCRunSchedule.sh
2. Prerequisites
  Make sure that the following software installed in your environment is compatible with this fix pack.
 
    Supported WebSphere MQ
      * WebSphere MQ 7.1
      * WebSphere MQ 7.5
      * IBM MQ 8.0
      * IBM MQ 9.0
      * IBM MQ 9.1
      * IBM MQ 9.2
    
    Supported IBM broker products:
      * WebSphere Message Broker 8.0
      * IBM Integration Bus 9.0
      * IBM Integration Bus 10.0
      * IBM App Connect Enterprise 11.0
    
    Supported IBM Tivoli Monitoring
      * IBM Tivoli Monitoring 6.3.0 fix pack 7 or later
3. Known problems and workarounds
  • TEMS Configurator (KCF) returns false result when validates Queue Manager v9.1 since there is un-supported attribute in IBM MQ 9.1. Workaround: uncheck 'Validate individual property fields' in Queue Manager Validation section.
  • Red Hat 8 on x86-64 is supported but it may need to install some additional 32 bit libraries.  Refer to the following link for details:  https://www.ibm.com/support/pages/node/1282876
    
4. Known limitations
   Some of OS platforms that were supported in Fix Pack 02 are not included in Fix Pack 03.
   This fix pack is available for following platforms:
  • Linux x86-64 (Red Hat and SUSE) 
  • Windows
  • AIX
  • Solaris sparc
  • Solaris 10 on x86-64
  • Linux (Red Hat and SUSE) on Power little endian (for kmq agent only)
  • Linux on z/OS
5. Download location
   You can download this fix pack from Passport Advantage.
   The part number of installation image is CC3X5EN.
   You can also download the fix pack from Fix Central in following link.
   Note:
    zLinux image is added to Fix Central only. It can not be downloaded from Passport Advantage.
  
6. Installation information
   The installation instructions for this fix pack are the same as those for the GA
   Version 7.3. Refer to the Installation and Setup Guide on the following
   Knowledge Centre to install, configure, and uninstall (if necessary)
   the WebSphere Message Broker monitoring agent, WebSphere MQ monitoring agent, and
   WebSphere MQ configuration agent.
 
   Welcome page on the Knowledge Center of ITCAM Agents for WebSphere Messaging:

7. Post installation
 
  7.1 WebSphere Message Broker monitoring agent
 
    7.1.1 Additional configuration required if the WebSphere Message Broker agent is upgrade from V7.3 GA to V7.3 FP3
 
    If you already installed the WebSphere Message Broker agent of V7.3 GA and have enabled historical data for Message flow status,
    complete the following steps after the agent is upgrade to V7.3 FP3.
    (1) Ensure you have upgraded application support files on Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server.
    (2) Stop the WebSphere Message Broker monitoring agent if it is running.
    (3) Remove the following local historical data files:
      Linux or UNIX:
        <agent_install_path>/<arch_code>/qi/hist/<AgentId>/KQITMFLS*
      Windows:
        32-bit agent: <ITM_HOME>\TMAITM6\logs\History\KQI\<instance ID>\KQITMFLS*
        64-bit agent: <ITM_HOME>\TMAITM6_x64\logs\History\KQI\<instance ID>\KQITMFLS*    
    (4) If you upgraded the agent from V7.3 GA to V7.3 FP2 and historical data collection is enabled for the Message
    Flow Status table, check the Message_Flow_Status table and any other related summarization tables
    (Message_Flow_Status with suffix such as _H, _D, _Y, _Q, _M, _W) in your warehouse database.
    If the length value of the DFMF_SAOF and DFMF_SSOF columns is 24,  change it to 12 by doing one of the following steps:
      -- Drop the table and allow WPA to rebuild it with correct column definitions.
      -- Manually perform ALTER COLUMN for DFMF_SAOF and DFMF_SSOF to specify a length of 12.
8. Document change history
   Oct. 01 2019          Original version
   Dec. 16 2020          Include 64 bit agents for Linux on z/OS

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Component":"5724K13MB;5724K350F;5724K3500","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF043","label":"Red Hat"},{"code":"PF027","label":"Solaris"},{"code":"PF048","label":"SUSE"},{"code":"PF033","label":"Windows"}],"Version":"7.3.0 Fix Pack 03","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 December 2020

UID

ibm11077315