IBM Support

IT34494: ROUTING CHANNELS CREATED WITH REST API CAN CREATE MAILBOX PATHS WITH EMBEDDED SPACES

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 creating Routing Channels with the REST API,
    if the Routing Channel Template creates Producer or Consumer
    Mailboxes with text appended to either the ProducerCode or
    ConsumerCode, spaces may appear between the Code and text. For
    example if the Template's Producer Mailbox Path is
    ${ProducerCode}_in, the resulting mailbox could include spaces
    between the value of the Producer's Code and "_in". (e.g. Code
    _in)
    

Local fix

  • B2BISFG-54190
    

Problem summary

  • Users Affected:
    
    Customers creating Routing Channels with the REST API, which
    use Routing Templates that set Producer or Consumer Mailboxes
    to a Partner Code, followed by text. The issue seen with Oracle
    and DB2 Databases.
    
    
    
    Problem Description:
    
    When creating Routing Channels with the REST API, if the Routing
    Channel Template creates Producer or Consumer Mailboxes with
    text appended to either the ProducerCode or ConsumerCode,
    spacesmay appear between the Code and text. For example if the
    Template's Producer Mailbox Path is ${ProducerCode}_in, the
    resulting mailbox could include spaces between the value of the
    Producer's Code and "_in". (e.g. Code _in)
    
    
    
    Platforms Affected:
    
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix is provided.
    Trim the Partner's Code before assigning to the Routing Channel
    Fact Map, which removes the spaces before the Code is used in
    the Routing Rule creation.
    
    
    
    Delivered in:
    
    5020603_16
    5020605_4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT34494

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    526

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-09

  • Closed date

    2021-04-08

  • Last modified date

    2021-05-24

  • 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

[{"Line of Business":{"code":"LOB02","label":"AI Applications"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.6"}]

Document Information

Modified date:
25 May 2021