Hi,

Cowen is probably right. The problem might be "At what rate do you
create/delete these during the night?" 

TSM (5.3.4.2) have a timing issue regarding a fast update rate of
volhist.out. And will get a 
lock for about an hour until it continue its processing. 
In my case I was deleting old copypool volumes with a macro, del vol
discadd=y wait=y'.

05-03-2007 13:02:37      ANR2017I Administrator issued command: DELETE
VOLUME 
                         001535 discardd=y wait=y  (SESSION: 1) 
05-03-2007 13:02:37      ANR0984I Process 204 for DELETE VOLUME (DISCARD
DATA)     
                         started in the FOREGROUND at 13:02:37.
(SESSION: 1,      
                         PROCESS: 204)

05-03-2007 14:03:02      ANR0538I A resource waiter has been aborted.

05-03-2007 14:03:02      ANR0538I A resource waiter has been aborted.

05-03-2007 14:03:02      ANR4513E A database lock conflict was
encountered in      
                         processing sequential volume history
information.        
05-03-2007 14:03:02      ANR9999D icvolhst.c(4060): ThreadId<37> Lock
Conflict     
                         encountered in updating volume history
list.(SESSION: 1, 
                         PROCESS: 204)

05-03-2007 14:03:03      ANR9999D ThreadId<37> issued message 9999 from:

                         (SESSION: 1, PROCESS: 204)

05-03-2007 14:03:03      ANR4510E Server could not write sequential
volume history 
                         information to volhist.out.

L2 support confirmed the timing issue and kindly asked me to restart TSM
server without volhist option so I could finsh my job.
... answers like that is why I like to spend $$$ on support...


//Henrik
(I might still not know what I am talking about..) ;)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Cowen
Sent: den 20 mars 2007 21:49
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Error writing volume history file

Some time ago (years), that error message would appear when a deadlock
of some kind prevented the volume history table from being accessed
during the write attempt.

One GB scratch volumes?  At what rate do you create/delete these during
the night?  A high rate would increase the chance of a timing window
being "illuminated".

Just curious, why such a small volume?  Would larger volumes result in a
lower rate of creation/deletion?


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Thomas Denier
Sent: Tuesday, March 20, 2007 1:57 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Error writing volume history file

We are seeing the following pair of messages occasionally:

ANR9999D icvolhst.c(5267): ThreadId <47> Error Writing to output File.
ANR4510E Server could not write sequential volume history information to
/var/tsm_automation/volumehistory.

Successive occurances of this pair of messages are typically a week to
two weeks apart. We have a 5.3.4.0 server running under mainframe Linux.
There is plenty of disk space available in the /var file system. The
Linux error logs do not report any I/O errors when these TSM messages
occur. The path at the end of the second message is the one specified
for the sequential volume history file in our server options file.

I have already contacted IBM, but I am not optimistic about getting a
resolution; the last e-mail I got from IBM requested 'ls' command output
needed to check the possibility of root not having write access to the
volume history file.
Has anyone else seen this and found a way to stop it?


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.