IC99093: INDEX RETRY LOGIC CAN ORPHAN GROUP_ID 3 AND 4 RECORDS

5.2.6.0

APAR status

• Closed as program error.

Error description

• When Index runs, it acts on GROUP_ID 1 and 2 records.
  Index should not touch GROUP_ID 3 or 4 records. Those are only
  affected by purge. Index has retry logic. If index fails on a
  set of processes for any reason, it marks the records for those
  WF_IDs to -5 and sets the ARCHIVE_DATE to one
  day in the future. When index runs, it looks for -5 records
  and reprocesses them.
  
  However, there is an issue with the logic that marks the
  records to -5. The mark only looks at WF_ID and does not look at
  the GROUP_ID. If there is a GROUP_ID 3 or 4 record with the
  same WF_ID as one of the records in the retry logic, it is
  marked -5 as well.
  
  Once the GROUP_ID 3 and 4 records are marked -5, they
  are never touched again.
  The index logic is driven by GROUP_ID 1 records, so the index
  retry will never look at those records.
  The purge logic is driven by ARCHIVE_FLAG of 1 or 2.  It will
  never look at any record with a -5 ARCHIVE_FLAG.
  

Local fix

• Circumvention:
  Reflag orphaned records manually.
  

Problem summary

• Users Affected:
  All
  
  Problem Description:
  Index retry logic in indexing BP can orphan GROUP_ID 3 and 4
  records.
  
  Platforms Affected:
  All
  

Problem conclusion

• Resolution Summary:
  A code fix has been provided.
  
  Delivered in:
  5020600
  

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

• Fixed component ID

  5725D0600

Applicable component levels

• R526 PSY

     UP