IJ28607: QUEUE GETTING DROPPED IN A SW FILESET WITH AFMFASTCREATE CAUSING A RECOVERY AND RESYNC TO GET TRIGGERED

APAR status

• Closed as program error.

Error description

• afmFastCreate when set doesn't filter create messages
  already in the queue when remove comes in. As a
  result both a create and a remove on same
  file can exist on the queue at the same time.
  If a Link gets sandwiched between the create and the
  remove then the Link fails to find the remote file and
  sees it as a conflict and drops the queue.
  Causing resync + recovery later to complete the sync.
  

Local fix

Problem summary

• afmFastCreate when set doesn't filter create messages
  already in the queue when remove comes in. As a
  result both a create and a remove on same
  file can exist on the queue at the same time.
  If a Link gets sandwiched between the create and the
  remove then the Link fails to find the remote file and
  sees it as a conflict and drops the queue.
  Causing resync + recovery later to complete the sync.
  

Problem conclusion

• Benefits of the solution:
  Queue doesn't get dropped and this unwanted recovery +
  resync is not triggered for the fileset. Ability to replicate
  the
  captured queue as is for AFM.
  
  Work Around:
  None today.
  
  Problem trigger:
  Run a lot of temporary file generating workloads on a SW/DR
  Primary fileset with afmFastCreate on. During the temporary
  files getting generated and removed, a link should
  be created as well.
  
  Symptom:
  Unexpected Behavior.
  
  Platforms affected:
  ALL Linux OS environments.
  
  Functional Area affected:
  AFM and AFM ADR
  
  Customer Impact:
  High Importance
  

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

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels