IBM Support

IT39166: IT IS NOT CLEAR THAT THE "RECORD DETECTION" AND DELIMITER FIELDSOF THE FILE INPUT SHOULD BE PROMOTED TOGETHER

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 properties "Record Detection" and "Delimiter" of the File
    Input node are linked. For example it does not make sense to set
    the delimiter for a flow if the record detection is "Whole File"
    or any other non-delimited option. When using the properties on
    the node the toolkit will grey out the Delimter option where
    appropriate, however when the properties are promoted there is
    no physical linkage between the message flow design document and
    the value of the promoted property because different instances
    of the flow could have different value set for the promoted
    properties.
    
    For this reason the Record Detection and Delimiter fields should
    be promoted together to ensure consistent behaviour of the
    toolkit and this advice should be documented in the Knowledge
    Center
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus version 10 or App Connect
    Enterprise version 11 or 12 using the File Nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The properties "Record Detection" and "Delimiter" of the File
    Input node are linked. It does not make sense, for example, to
    set the delimiter for a flow if the record detection is "Whole
    File" or any other non-delimited option.
    
    When using the properties on the node the toolkit will grey out
    the Delimiter option where appropriate. When the properties are
    promoted, however, there is no physical linkage between the
    message flow design document and the value of the promoted
    property because different instances of the flow could have
    different values set for the promoted properties.
    
    For this reason the Record Detection and Delimiter fields should
    be promoted together to ensure consistent behaviour of the
    toolkit and this advice should be documented in the Knowledge
    Center
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT39166

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-11-22

  • Closed date

    2022-10-27

  • Last modified date

    2022-10-27

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

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

Document Information

Modified date:
28 October 2022