IJ25369: PREFETCH FAILS WHEN LIST FILE WITH SAME NAME PRESENT

APAR status

• Closed as program error.

Error description

• While prefetching files with AFM a file containing a list
  of files to be prefetched is provided to the mmafmctl
  prefetch command. But if the prefetch command is
  initiated
  on a application node and a file with similar name and in
  the same path is present on the gateway node, the file
  list
  on gateway is actually queued instead of file list passed
  to the prefetch command. This file on the gateway may be
  completely unrelated to the prefetch and hence the
  prefetch
  will fail.
  

Local fix

• If an unrelated file list is present on the gateway node
  with same name and path as the one passed to the prefetch
  command then delete that file from the gateway node and
  retry the prefetch command
  

Problem summary

• Prefetch enhancements in 5.0.2
  introduced a minor internal check
  such that if the list file is present
  in an NFS mount common
  across the application and
  Gateway nodes, AFM skips
  copying this list file from app to
  GW and uses the list file
  as is on GW node.
  But sometimes the same path
  and file name can exist and
  have 2 entirely unrelated files.
  

Problem conclusion

• Benefits of the solution:
  Ability for AFM prefetch to be able to decide whether
  or not to copy the list file from app node to gateway
  node, if the same list file is available on the
  gateway node also.
  Work around:
  Rename the list file on the Application
  node to have a unique name
  such that it doesn't match any
  similar file on the Gateway node.
  Or remove/rename similar named list
  files on the gateway node
  so that AFM prefetch doesn't detect
  the same named list file
  from the Application node that its
  present on the gateway node.
  Problem trigger:
  Have same named list file
  on the gateway node and the application
  node. These files should
   have a different list of files.
   Try running prefetch with this list file
   from the application node.
  Symptom:
  Unexpected Results/Behavior
  Platforms affected:
  All Linux Gateway nodes and
   Linux and AIX OS nodes application 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