IBM Support

IT11800: INCOMPLETE PGP FILE RECEIVED - PGP UNPACKAGE BP HALTS WITH ERROR

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

  • An incomplete PGP file is uploaded by the producer. When that
    happens, the FileGatewayRoutePGPUnpackageDocument BP halts
    with a status of "Error" at the PGP Unpackage Service
    step. The parent BP, FileGatewayMailboxRouteArrivedFile, waits
    in State "Active" with Status "Sucess" until a timeout is
    reached. Prior to the timeout, the SFG Arrived File tab on the
    Activity screen shows the file as "Determining" or "Routing,"
    depending on the version, with Deliver Status "Not
    Available."
    
    After the timeout, the parent shows as ending with status
    "Success," but on the SFG Arrived File tab, the route shows as
    "Failed" with Delivery Status "Not Available."
    
    The Arrived File Events screen shows the following errors:
    FG_0250 error "ERROR: Failed BP
    'FileGatewayRoutePGPUnpackageDocument' to extract PGP layer
    with workflow [<WFID>].
    FG_0650 with "Extract PGP layer failed for file <file name>
    with error Execution of bp
    [FileGatewayRoutePGPUnpackageDocument] failed, wfid:<WFID>.
    FG_0455 Arrived File is now failed while Routing with error
    message: Execution of bp [FileGatewayRoutePGPUnpackageDocument]
    failed, wfid:<WFID>.
    

Local fix

  • STRRTC - 473509
    NM / NM
    Circumvention:
    
    Insert the below BPML into the existing version of the
    FileGatewayRoutePGPUnpackageDocument BP between the line that
    reads:
    <assign name="Assign" to="PrimaryDocument"
    from="PGP/Document/@SCIObjectID"/>
    
    and the line that reads:
    
    </sequence>
    
    After that, change the new version to be the default. This will
    not prevent the BP from failing, but will get it to report back
    to the parent BP so that the final failure does not have to
    wait until a timeout occurs.
    
    
          <onFault>
            <sequence>
              <assign to="Error">True</assign>
            </sequence>
          </onFault>
    

Problem summary

  • Users Affected:
    Sterling File Gateway users receiving PGP files
    
    Problem Description:
    If a corrupt PGP file is received from a trading partner, it
    can cause Sterling File Gateway to not signal that there was an
    error processing this file for the length of time it waits
    on a business process to complete.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix has been provided.
    
    Delivered In:
    5020500_10
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT11800

  • Reported component name

    STR FILE GATEWA

  • Reported component ID

    5725D0700

  • Reported release

    225

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-10-15

  • Closed date

    2015-10-30

  • Last modified date

    2015-11-23

  • 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 FILE GATEWA

  • Fixed component ID

    5725D0700

Applicable component levels

  • R225 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4TGX","label":"IBM Sterling File Gateway"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
23 November 2015