Those "Failed" instances might reflect initial read or write problems
which were surmounted upon retry.  There have been APARs on such
counts involving migration, where the same sort of thing might be
happening in backup stgpool.  Development realized that such instances
should not be regarded as failures, given that they ultimately
succeeded.  Seems like the table needs a middle-ground count for
Retries.

   Richard Sims

Reply via email to