On Mar 20, 2007, at 1:56 PM, Thomas Denier wrote:

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.

Hi, Thomas -

Yet another exasperating instance of lazy programming, failing to at
least report the errno which the process thread encountered.  Would
the Development managers who may be following ADSM-L drive home to
the developers that fully useful error messages be emitted when there
is a problem?  The lack of information is wasting the time of
customers and, in this case, product support personnel.

One possible, but less likely cause could be a volume history set of
such size that it exceeds the "filesize" Unix Resource Limit under
which the TSM server was started: if yours is a large set, try
pruning and see if the problem goes away.  Another possible cause is
the TSM server running out of file descriptors as it attempts to open
that external file: if low, boost that number for server start.

   Richard Sims