IBM Support

IT31832: fteCreateMonitor ignores any monitor metadata when recreating amonitor from an input file using the -ix parameter

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

  • When running the fteCreateMonitor command, specifying the -ix
    parameter to create a resource monitor from an input file, any
    monitor metadata contained within the monitor definition is
    ignored,
    
    For example:
    
    - A resource monitor definition is exported to an XML file using
    the fteListMonitors command:
    
    fteListMonitors -ma IBMagent -mn Monitor -ox
    Monitor1Definition.xml
    ——
    The Monitor1Definition.xml file contains the monitor metadata
    associated with the monitor:
    
    <metaDataSet>
      <metaData key=“fileLock”>FileExtension:.lck</metaData>
    </metaDataSet>
     ——
    - The XML file is then used to create a new monitor, using the
    fteCreateMonitor command:
    
    fteCreateMonitor -ma newIBMAgent -ix /tmp/Monitor1Definition.xml
    ——
    However, the newly created monitor does not contain any monitor
    metadata.
    

Local fix

  •  Use -mmd option while creating the resource monitor using
    fteCreateMonintor command.
    
    
     fteCreateMonitor -ix Monitor1Definition.xml  -mmd
    “fileLock=FileExtension:.lck” -f
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of IBM MQ Managed File Transfer who
    have resource monitors defined that contain monitor metadata.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When creating a resource monitor using the fteCreateMonitor
    command, it is possible to specify some user-defined metadata
    (also known as monitor metadata) which will be passed to any
    user exits that the monitor has been configured to invoke. The
    monitor metadata is specified by using the -mmd parameter on the
    fteCreateMonitor command.
    
    If a resource monitor containing monitor metadata is exported to
    an XML file, by specifying the -ox parameter on either the
    fteCreateMonitor or fteListMonitors command, then the resultant
    XML file would contain the monitor metadata as expected, as
    shown in the example below:
    
    <metaDataSet>
        <metaData key="MyKey">MyValue</metaData>
    </metaDataSet>
    
    However, when the resource monitor definition was imported from
    the same XML file, by passing in the -ix parameter on the
    fteCreateMonitor command, the command would ignore the metadata.
    As a result, the monitor would be recreated without its
    associated metadata.
    

Problem conclusion

  • To resolve this issue, the fteCreateMonitor command has been
    updated to process any monitor metadata contained within the
    input file when the -ix parameter is specified. This ensures
    that the resource monitor is recreated with its associated
    metadata.
    
    If the fteCreateMonitor command is unable to process the monitor
    metadata contained witn the input file, it will generate an
    exception similar to the one shown below:
    
    BFGCL0395E: An error occurred attempting to parse the given
    monitor definition file XML. The error was: Open quote is
    expected for attribute "key" associated with an  element type
    "metaData".
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.15
    v9.0 LTS   9.0.0.11
    v9.1 CD    TBC.
    v9.1 LTS   9.1.0.6
    
    The latest available MQ 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

    IT31832

  • Reported component name

    IBM MQ MFT V9.1

  • Reported component ID

    5724H7272

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-11

  • Closed date

    2020-04-15

  • Last modified date

    2020-04-15

  • 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

    IBM MQ MFT V9.1

  • Fixed component ID

    5724H7272

Applicable component levels

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

Document Information

Modified date:
16 April 2020