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

si_52_build_5020500_interimfix_10
si_52_build_5020500_interimfix_10

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 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