I have seen this problem before.  When I saw it, it was because we had tape
drives getting a lot of fibre channel SCSI errors and causing all kinds of
locking apparently.  You may want to check to make sure something like that
is not happening.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Chetan H. Ravnikar [mailto:Chetan.Ravnikar AT SYNOPSYS DOT COM]
Sent: Saturday, September 21, 2002 3:06 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: q act says *No match found*


Ok I bounced the server and things look OK, :)


On Sat, 21 Sep 2002, Bob Booth - UIUC wrote:

> Date: Sat, 21 Sep 2002 13:04:05 -0500
> From: Bob Booth - UIUC <booth AT uiuc DOT edu>
> Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> To: ADSM-L AT vm.marist DOT edu
> Subject: Re: q act says *No match found*
>
> Hard to tell whats going on.  Is this a fresh install of TSM?  What
> version? What platform is it?
>
> Do a 'q stat' and check to see what your activity log retention period
> is.. It is possible to set the ACTLOGRETENTION to 0, thereby turning
> it off.
>
> hope this helps,
>
> bob
>
> On Sat, Sep 21, 2002 at 10:23:34AM -0700, Chetan H. Ravnikar wrote:
> > Any help is appreciated,
> > I am wondering how can this happen, a fully functional server now
> > does not give any activity log
> >
> > please help
> >
> > thanks
> >
> >
> > tsm: server1>q act
> > ANR2034E QUERY ACTLOG: No match found using this criteria. ANS8001I
> > Return code 11.
> >
> > tsm: server1>