John Lemkelde wrote:
>
> We are getting the following message:
>    ANS4089E File not found during Backup, Archive or Migrate processing
> on a node that is running Oracle.  We cannot find any processes that are
> removing files during the backup.  Oracle is brought down during 'pre'
> processing
> and backup at 'post' processing.
>   How can we find out which file it was trying to backup, to further
> track down what is occurring.

The above message touches on one of my pet peeves: a lot of ADSM messages
leave out critical information. The message announcing that an EXPORT was
unable to read a file from a storage pool tape also omits the name of the
file involved. The message announcing that a session from an unregistered
node was rejected omits the offending node name. I opened an incident for
the EXPORT message. As I recall, it took IBM about two months to decide to
add the file name to the message (not two months to actually fix the code
two months just to decide that it should be fixed). As far as I can
tell, IBM has yet to realize that the uninformative error messages are
part of a widespread pattern rather than a handful of abberations that
can appropriately be dealt with by the APAR process.