Hello Tim,

Any dsmc command is openning a connexion with the server (dsmc q se, dsmc q 
fi...), but dsmc help doesn't. You may give it a try.

Also, TSM 6.1.0 is worth an update to a fixed version, don't you think ?

-- 
Best regards / Cordialement / مع تحياتي
Erwann SIMON

----- Mail original -----
De: "Tim Brown" <TBrown AT CENHUD DOT COM>
À: ADSM-L AT VM.MARIST DOT EDU
Envoyé: Vendredi 6 Février 2015 20:30:31
Objet: Re: [ADSM-L] TSM issue with RedHat

This just happed, had been working for months. If I use ./dsmc q fi 
I get nada, hangs! Will guarantee a reboot of linux will fix it.
Also no other locations is there another tsm log file


Tim

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Sims, Richard B
Sent: Friday, 06 February, 2015 8:45 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM issue with RedHat

>From my experience, this likely has nothing to do with the TSM server, but 
>rather either configuration issues with the client or permissions on the 
>dsmerror.log, or its location.
Start with a simple command like ‘dsmc q fi’, as an ordinary user and then 
root, to see if there are issues with dsmerror.log access, and expand from 
there. ‘dsmc q inclexcl’ will in particular exercise your client configuration 
files, as well as attempt to query the server.
We don’t know if your client system ever had viable sessions with the TSM 
server or if this is a new system attempting its first interactions.

  Richard Sims, Boston University