We recently had a situation where the libv became out of sync and an audit
libv could not be run without errors. The situation that caused this was
after IBM came out to insert another i/o port for J1 drives. What we ended
up doing was deleteing all drives paths and the library. We then redefined
the library, the drives and paths and everything came back after first doing
a checkin for all scratches and then all privates.

The volume list that is kept in the db is all that is required. q vol to
checkin all vols in the library after redefining the library and drives.
Regards
Will

-----Original Message-----
From: Richard Sims [mailto:rbs AT BU DOT EDU]
Sent: Friday, September 24, 2004 1:43 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: storage media inaccessible? - fixed


In the absence of major problems, which would be reflected in the TSM
server Activity Log, and perhaps AIX Error Log, the 3494 Library Manager
database should always be in sync with the TSM server. The combination
is
just that reliable. I would presume that in your elective library
stoppage
that you likewise suspended activities on the TSM server, just in case.
In the rare case when it's necessary, the AUDit LIBRary can be run to
re-synchronize information.  See the IBM doc for the authoritative scoop
on the operation of that command, and ADSM QuickFacts for additional
notes.

    Richard Sims     http://people.bu.edu/

On Sep 24, 2004, at 12:08 PM, William Rosette wrote:

> I just stopped and started my 3494 tape library and received the same
> results.  I was thinking that the PC that controls the DB on the 3494
> was
> not "synced" up with the AIX SP TSM server.  I'd be interested if
> anybody
> else has any ideas.