IBM Support

IC96192: XPATH ERRORS POST TO SYSTEM LOG WHEN BUSINESS PROCESS RUNS AND RECEIVES FILENAMES BEGINING WITH A NUMBER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • XPath errors post to System log when BP runs and receives
    filenames begining with a number. The Business Process
    contained a combination of FSA service followed by the
    ForEachDocument Service. This issue was originally reported at
    V5006_1, but this issue has also been recreated in
    V5.2.4.1.
    
    In the BP with a File System Adapter (FSA) is collecting files
    and the received filenames begin with a number and each file is
    processed with the ForEachDocument Service and this is when SI
    throws errors per each file in the System logs. If the received
    filenames begin with an alpha character instead of a number,no
    errors are generated to the System log. The remote TP has a
    requirement specifying that their filenames must begin with a
    number, not with an alpha character.
    
    Note: Even though errors are generated to the System log, the
    BP runs successfully and processes all received files.
    
    Example of errors put to the SI System log when received file
    beginning with a number in above scenario:
    
    [2013-05-08 15:01:17.167] ERROR XPathCacheLoader.load() key =
    425_ACFILE_DFA_201304150830_90200560.pdf/@ContractWorkFlowName
    TransformerException cause = 'null', message =
    '425_ACFILE_DFA_201304150830_90200560.pdf could not be formatted
     to a number!'
    
    
    [2013-05-08 15:01:17.168] ERROR XMLUtil.getXObject() newXPath =
    425_ACFILE_DFA_201304150830_90200560.pdf/@ContractWorkFlowName
    TransformerException null
    

Local fix

  • RTC ID: 562959
    LRB / LRB
    Circumvention: None
    

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    Errors are thrown when filenames begin with numbers.
    
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix is provided.
    
    Delivered In:
    5020600
    5020500_11
    5020601_2
    5020603_7
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC96192

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-09-24

  • Closed date

    2015-10-21

  • Last modified date

    2018-10-17

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS3JSW","label":"Sterling B2B Integrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.0","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
11 September 2024