IBM Support

IT34422: Managed File Transfer schema Monitor.xsd incorrectly states that directory monitors can monitor more than 1 directory

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

  • The schema Monitor.xsd, shipped as part of IBM MQ Managed File
    Transfer, defines the format of XML documents that can be used
    to create and delete resource monitors.
    
    In the schema, the value of the "maxOccurs" attribute for the
    "directory" element indicates that there is no upper limit on
    the number of directories that can be monitored, as shown below:
    
    <xsd:element name="directory" type="monitoredDirectoryType"
             minOccurs="1" maxOccurs="unbounded" />
    
    However, if a user manually builds an XML document containing a
    request to create an resource monitor, where the document
    contains multiple "directory" elements, and then puts a message
    containing that document onto the agent's command queue:
    
      SYSTEM.FTE.COMMAND.<agent_name>
    
    the resource monitor that is created only monitors the directory
    specified in the first "directory" element. The directories
    mentioned in the other "directory" elements are ignored.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - IBM MQ 9.1 Managed File Transfer
    - IBM MQ 9.2 Managed File Transfer
    
    who use the Monitor.xsd XML schema to manually build XML
    messages to create resource monitors that monitor a directory
    resource.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In the Monitor.xsd schema file shipped as part of IBM MQ Managed
    File Transfer, the definition for monitorResourcesType looked
    like this:
    
    <xsd:complexType name="monitorResourcesType">
      <xsd:choice>
        <xsd:sequence>
          <xsd:element name="directory"
    type="monitoredDirectoryType"
                  minOccurs="1"    maxOccurs="unbounded" />
         </xsd:sequence>
         <xsd:element name="queue" type="monitoredQueueType"/>
       </xsd:choice>
    </xsd:complexType>
    
    The "directory" element had the "maxOccurs" attribute set to
    "unbounded", which indicated that there could be multiple
    "directory" entries. However, this was incorrect. When creating
    a resource monitor that monitors a directory, only one directory
    can be specified.
    

Problem conclusion

  • To resolve this issue, the definition of the "directory" element
    within the "monitorResourcesTypes" complex type has been changed
    so that "maxOccurs" is set to 1, as shown below:
    
    <xsd:complexType name="monitorResourcesType">
      <xsd:choice>
        <xsd:sequence>
          <xsd:element name="directory"
    type="monitoredDirectoryType"
                  minOccurs="1"    maxOccurs="1" />
         </xsd:sequence>
         <xsd:element name="queue" type="monitoredQueueType"/>
       </xsd:choice>
    </xsd:complexType>
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.11
    v9.2 LTS   9.2.0.5
    v9.x CD    9.2.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

    IT34422

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-01

  • Closed date

    2021-12-21

  • Last modified date

    2021-12-21

  • 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 BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
22 December 2021