APAR IC33641:
Problem Summary:
****************************************************************
* USERS AFFECTED: All TSM Server users and platforms. *
****************************************************************
* PROBLEM DESCRIPTION: The message ANR0197E is issued *
* periodically during volume operations *
* once it is available. *
****************************************************************
The volume processing for TSM may issue ANR0197E in cases
where a given volume did not need to be checked for
orphan segments. The processing does not make any
changes to the server database or take any inappropriate
actions, it simply tries to check a volume when the
volume is in use and should not be checked.
Temporary Fix:
Comments:
MODULES/MACROS: NONE
Problem Conclusion:
The TSM volume processing that checks for orphan segment
entries has been modified to prevent inappropriately
attempting to check a volume.
-----Original Message-----
From: Jolliff, Dale
Sent: Tuesday, September 17, 2002 11:18 AM
To: 'ADSM: Dist Stor Manager'
Subject: ANR9999D - ANR0197E
This is from a 4.2.1.15 server that is the library manager for 4 other TSM
servers..
Anybody seen this before?
09/17/2002 09:07:53 ANR1181E astxn.c412: Data storage transaction
0:12456483
was aborted.
09/17/2002 09:07:53 ANR9999D asalloc.c(663): ThreadId<94> Volume E01710
being
accessed remotely - ending repair attempt.
09/17/2002 09:07:53 ANR0197E Removal of extraneous database entries for
volume
E01710 failed due to contention with other server
processes or activities.
A move data from a volume referenced like this will finish successfully,
however as the data is moved the "unreadable bytes:" counter increments in
query process.
The volumes referenced from the bitfile in the first line move OK also - and
the error seems to pop up somewhere else the next day.
