IBM Support

IC59697: WMQFTE WILD CARD BEHAVIOR IS NOT CORRECT, AS STATED IN THE MANUAL.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • In the manual it is stated when wild card '*' symbol is used the
    symbolic links are ignored. But on linux, MQFTE doesn't ignore.
    When a destination file is created from a source that is a
    symbolic link, the destination file becomes a hard link (that is
    a regular file). You cannot successfully transfer symbolic links
    to directories.
    If symboliclink is directory and file is saved under the
    symbolic linkdir, file is not sent. But if symbolic link is a
    file, file is sent though set upper dir in fteCreateTransfer.
    
    PROBLEM CONCLUSION:
    The Infocentre at Boulder has been updated with teh correct
    words. A new disk will be produced and translated for the first
    fixpack.
    
    
    Here are the relevant words from
    
    http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/topic/com.i
    bm.wmqfte.admin.doc/wildcards.htm
    
    Before:
    Symbolic links
    Symbolic links are a type of file that contain a pointer to
    another file or directory and are known as shortcuts on Windows.
    Wildcard source specifications ignore symbolic links, but you
    can use symbolic links in a file transfer if you exactly specify
    the symbolic link as a source. However, when a destination file
    is created from a source that is a symbolic link, the
    destination file becomes a hard link (that is, a regular file).
    You cannot successfully transfer symbolic links to directories.
    
    After:
    Symbolic links
    Symbolic links are a type of file that contain a pointer to
    another file or directory and are known as shortcuts on Windows.
    You can match symbolic link files with wildcard characters.
    However, when a destination file is created from a source that
    is a symbolic link, the destination file becomes a hard link
    (that is, a regular file). You cannot successfully transfer
    symbolic links to directories because this could potentially
    create a recursive path.
    

Local fix

Problem summary

  • WMQFTE manual incorrectly described wild card behaviour when
    compared to the product.
    Manual needs correcting
    

Problem conclusion

  • Here are the relevant words from
    http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/topic/com.i
    bm.wmqfte.admin.doc/wildcards.htm
    
    Before:
    Symbolic links
    Symbolic links are a type of file that contain a pointer to
    another file or directory and are known as shortcuts on Windows.
    Wildcard source specifications ignore symbolic links, but you
    can use symbolic links in a file transfer if you exactly specify
    the symbolic link as a source. However, when a destination file
    is created from a source that is a symbolic link, the
    destination file becomes a hard link (that is, a regular file).
    You cannot successfully transfer symbolic links to directories.
    
    After:
    Symbolic links
    Symbolic links are a type of file that contain a pointer to
    another file or directory and are known as shortcuts on Windows.
    You can match symbolic link files with wildcard characters.
    However, when a destination file is created from a source that
    is a symbolic link, the destination file becomes a hard link
    (that is, a regular file). You cannot successfully transfer
    symbolic links to directories because this could potentially
    create a recursive path.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC59697

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    700

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-27

  • Closed date

    2009-02-05

  • Last modified date

    2009-02-05

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
05 February 2009