IBM Support

IT30785: IBM MQ Appliance reports Invalid log type parameter for parse and mpgw log categories

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • MQ Appliance reported "Invalid log type" error for log
    categories parse and mpgw and the the default log  likely to
    contain the errors for parse or mpgw or for both parse and mpgw
    log categories.
    
    20191017T011346.570Z [0x80e00062][network][error] logging
    target(trap-collector): tid(1679): Invalid log type parameter in
    'snmp://trap/?Type=parse&Level=error&Time=Wed Oct 16 2019
    11:45:10&TransID=0&Domain=default&EventCode=0x30002'
    20191017T011346.570Z [0x80e00086][network][error] logging
    target(trap-collector): tid(1679): Cannot create connection to
    'snmp://trap/?Type=parse&Level=error&Time=Wed Oct 16 2019
    11:45:10&TransID=0&Domain=default&EventCode=0x30002'
    
    91101T175324.304Z [0x80e00062][network][error] logging
    target(trap-collector): tid(1759): Invalid log type parameter in
    'snmp://trap/?Type=mpgw&Level=error&Time=Fri Nov 01 2019
    10:39:03&TransID=71121&Class=mpgw&Name=rest-mgmt&Domain=default&
    EventCode=0xd30003'
    20191101T175324.304Z [0x80e00086][network][error] logging
    target(trap-collector): tid(1759): Cannot create connection to
    'snmp://trap/?Type=mpgw&Level=error&Time=Fri Nov 01 2019
    10:39:03&TransID=71121&Class=mpgw&Name=rest-mgmt&Domain=default&
    EventCode=0xd30003'
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using the IBM MQ Appliance with SNMP traps enabled
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The parse and mpgw log categories were partially enabled and
    this caused the invalid log type errors for parse and mpgw log
    categories.
    

Problem conclusion

  • IBM MQ Appliance code has been modified to completely enable
    parse and mpgw log categories.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.x CD    9.2.0
    v9.1 LTS   9.1.0.5
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT30785

  • Reported component name

    MQ APPLIANCE M2

  • Reported component ID

    5737H4700

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-31

  • Closed date

    2020-03-27

  • Last modified date

    2020-09-24

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    MQ APPLIANCE M2

  • Fixed component ID

    5737H4700

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
26 September 2020