Hello, Ashish.

I've seen this before in library manager environments.  Usually I
recommend people bring down all their TSM servers, then on each TSM
server's host, delete their device files (rmt* and smc*), run cfgmgr to
redetect, restart TSM, and update their paths.  It's the surest fix.

If you want to spend the time to troubleshoot and find out what broke,
try this, then send us the output of the lsdev command again.  This will
set each device to "defined" and then back to "available".  If they stay
defined, then those device files have a problem.  This shouldn't affect
devices already in use - it should just say "device busy" or something
like that.  Note:  You will probably have to do this on all your TSM
servers' hosts.

lsdev -Cc tape | grep IBM | awk '{print $1}' | while read DEV; do
   echo "testing $DEV"
   rmdev -l $DEV
   mkdev -l $DEV
done

________________________________
Alex Paschal
Storage Solutions Engineer
MSI Systems Integrators
________________________________

Your Business.  Better.




-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
ashish sharma
Sent: Wednesday, February 11, 2009 8:02 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] cannot run command

Hello,

The o/p of command is as below:


# /usr/sbin/lsdev  -C  -c tape  -H
name  status    location     description

rmt0  Available 1Z-08-00-0,0 Differential SCSI 4mm Tape Drive
rmt1  Available 31-08-01     IBM 3580 Ultrium Tape Drive (FCP)
smc0  Available 31-08-01     IBM 3584 Library Medium Changer (FCP)
rmt2  Available 31-08-01     IBM 3580 Ultrium Tape Drive (FCP)
rmt3  Available 2U-08-01     IBM 3580 Ultrium Tape Drive (FCP)
rmt6  Available 2d-08-01     IBM 3580 Ultrium Tape Drive (FCP)
rmt4  Available 2U-08-01     IBM 3580 Ultrium Tape Drive (FCP)
rmt5  Available 2U-08-01     IBM 3580 Ultrium Tape Drive (FCP)
rmt7  Available 2d-08-01     IBM 3580 Ultrium Tape Drive (FCP)
smc1  Available 2d-08-01     IBM 3584 Library Medium Changer (FCP)
rmt8  Available 2d-08-01     IBM 3580 Ultrium Tape Drive (FCP)
rmt9  Available 2d-08-01     IBM 3580 Ultrium Tape Drive (FCP)
rmt10 Available 2d-08-01     IBM 3580 Ultrium Tape Drive (FCP)





while o/p of "q proc" does not show anything.



Regards

Ashish



On 2/11/09, Kamran Rao <kamran.rao AT grhosp.on DOT ca> wrote:
>
> As root - run "lsdev -Cc tape" and see if your drives and medium
changer
> are showing up as "available" - if shows up as "defined" then you
might
> have a device problem. You have not mentioned what kind of library and
> also if it is a direct connect as "scsi" or via FC adapter etc etc?
>
>
> Regards,
>
> Kamran Rao
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of
> ashish sharma
> Sent: February 11, 2009 10:08 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] cannot run command
>
> Hello all,
>
> My TSM server version is
>
> Storage Management Server for AIX-RS/6000 - Version 5, Release 3,
Level
> 5.0 on AIX.
>
> The issue i am facing is that when i try to give command  like "q
path"
> or "q mount" the command hangs as shown below
>
> *************************
> tsm: TSMLM>q mount
>
> *************************
>
> and does not give any o/p but when i give command like q session, it
> works but again i am unable to cancel any session.Does anybody has any
> idea why is it happening?I think restaring the server might solve the
> problem but at present i am not in favour of it.
>
>
>
>
> --
> Best Regards
> Ashish Sharma
> ST Microelectronics Ltd.
> 919717003853
>



--
Best Regards
Ashish Sharma
ST Microelectronics Ltd.
919717003853

This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.

Thank you.