IJ32219: DO NOT LOG THE ERROR 124 TO THE GATEWAY NODE LOG

APAR status

• Closed as program error.

Error description

• AFM logs an error 124 (error not supported),
  when the Control file
   is not available at home site (non-GPFS home site).
  

Local fix

Problem summary

• AFM logs an error 124 (error not supported),
  when the Control file
  is not available at home site (non-GPFS home site).
  

Problem conclusion

• Benefits of the solution:
  Gateway node log is not flooded
  with error 124, when the control
  file is not present at the Home site.
  Also the operation that
  gets skipped because of the
  unavailability of the control file
  doesn't set inode bits which causes
  this file to be picked up
  by recovery later.
  
  Work around:
  None.
  
  Problem trigger:
  Try to set EAs on a file when home is a non-GPFS node
   which doesn't contain the afm control file.
  
  Symptom:
  Error message
  
  Platforms affected:
  ALL Linux OS environments
   (serving as AFM Gateway nodes)
  
  Functional Area affected:
  AFM
  
  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