IJ24057: FILE SIZE AND DATA MISMATCHES ON DEPENDENT FILESETS.

APAR status

• Closed as program error.

Error description

• On occasion when performing operations on a
  dependent fileset, it doesn't set the recovery flag and
  due to this, if somehow fileset is gone to
  recovery then recovery will not be triggered.
  Because of this case, pending data changes
  will not replicate to remote (home) and
  data mismatches can be seen.
  

Local fix

• Create one file on an independent fileset
  which will set the recovery flag.
  

Problem summary

• On occasion when performing operations on a
  dependent fileset, it doesn't set the recovery flag and
  due to this, if somehow fileset is gone to
  recovery then recovery will not be triggered.
  Because of this case, pending data changes
  will not replicate to remote (home) and
  data mismatches can be seen.
  

Problem conclusion

• Benefits of the solution: 
  It will set the recovery flag once you
  start performing operations on a dependent fileset.
  So, next recovery will always take care of
  pending data changes to replicate to the
  remote (home) site and data will be kept in
  sync at all times.
  Work around:
  Create one file on an independent fileset
  which will set the recovery flag.
  Problem trigger:
  When recovery happens on a dependent
  fileset and the needRecovery bit is set to 0.
  Symptom: File size and data mismatches.
  Platforms affected: All OS environments
  Functional Area affected: AFM
  Customer Impact: Suggested
  

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