Richard,

I just removed an ANS1312E problem from my to-do list.  It was caused by
some clients trying to access a new storage pool of DEVC=FILE while the
MAXNUMMP was set to 0.  The only thing odd in the AC was the line number of
files backed up = 0.  The only help was in the client's schedlog.


At 05:47 PM 3/17/2005 -0500, you wrote:

Al -

I should think you'd see *some* server message in your Activity Log
when a client session is rudely terminated, such as ANR0535W, which
usually correlates with the ANS1312E. Beyond that you could pursue
Query Event and/or Select * From Summary. Also see if field 11 of the
accounting record yields an Abnormal condition for those circumstances.
The droll approach is Disk of the Month Club: just routinely add more
disk space every so often, in that backup/archive demands inexorably
increase over time anyway. :-)

  Richard Sims

On Mar 17, 2005, at 2:10 PM, Al Delaney wrote:

We occasionally get "Media Mount" errors on some of our TSM clients
because we force them to disk pools on the server and migrate to tape
pools.  Occasionally the disk pools fill before they can be moved to
tape and we don't permit the clients to allocate a tape unit to
complete
their backups.  Problem is, the "Media Mount" error message only occurs
in the client's log, not the server's, so it's hard to track down when
and by whom they occur so we can tune our pool sizes or backup
schedules
appropriately.  We've adjusted the high migration percentage, but I'd
like a way to see each morning if any of these issues occurred without
having to slurp in over 300 client logs.  Querying the server's
activity
log doesn't show this error (msg ANS1312E).  Any ideas are appreciated.
Al Delaney
Louisiana State University

Fred Johanson
ITSM Administrator
University of Chicago
773-702-8464