IBM Support

IT02065: IBM STERLING B2B INTEGRATOR VERSION 5020402_2. THE CAUSE IS A PREVIOUS FIX. IT IS RESOLVED BY BACKING OUT THAT FIX.

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.

Direct link to fix

APAR status

  • Closed as program error.

Error description

  • ERROR DESCRIPTION:
    All attempts to do an SFTP GET to pull a file from a separate
    IBM Sterling B2B Integrator (SI below) instance fail with an
    error saying that the message was not extractable. The file can
    be retrieved using other clients. This only occurs when the
    extractability of the file on the SI instance that is acting as
    the server is set to 1. There is no issue if the extractability
    is greater than 1, the extractability is set to "yes" or the
    extractability is set to "extractable until" with a setting
    that is a future date. The Advanced Status column of SFTP
    Client GET Service and the sftpclient.log file both show
    "NoSuch file.: The message [<mailbox name>/<file name>] is not
    extractable!" when this happens. Process Data shows "No such
    file.: The message [/<mailbox name>/<file name>] is not
    extractable" in the <Prev_NotSuccess_Adv_Status> tag. The
    extractability remains at 1 after the failure.
    

Local fix

  • LOCAL FIX:
    STRRTC - 424680
    NM / NM
    Circumvention: If the owner of the SI instance that is acting
    as the server is willing to change the extraction type or value
    of the messages in the target mailbox, that is the workaround.
    If not, there is no workaround.
    

Problem summary

  • All attempts to do SFTP GET to pull a file from another SI
    instance fail with an error saying that the message was not
    extractable. The customer can retrieve the same document using
    FileZilla SFTP Client.
    This only occurs when the extractability of the file on the SI
    instance that is acting as the server is set to 1. There is no
    issue if the extractability is greater than 1, the
    extractability is set to "yes" or the extractability is set to
    "extractable until" with a setting that is a future date.
    When this happens, the Advanced Status column of SFTP Client GET
    Service shows ""NoSuch file.: The message [Inbox/EDIData.txt] is
    not extractable!".
    

Problem conclusion

  • Made the required fix. After making the changes, the SFTP GET on
    an SI instance from another SI SFTP server with a mailbox
    message
    having the extractability count works fine. This works fine even
    when the extractability is set to 1.
    DELIVERED IN:
    5020500
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT02065

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    524

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-27

  • Closed date

    2014-12-05

  • Last modified date

    2014-12-11

  • 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

  • R525 PSY

       UP



Document information

More support for: Sterling B2B Integrator

Software version: 5.2.4

Reference #: IT02065

Modified date: 11 December 2014