Or perhaps... could it have something to do with this flash alert I
received in my inbox today?

http://www-01.ibm.com/support/docview.wss?uid=swg21696086&myns=swgtiv&mynp=OCSSGSG7&mync=E&cm_sp=swgtiv-_-OCSSGSG7-_-E

Abstract

RHEL 6.6 contains a kernel defect, which can cause Tivoli Storage Manager
operations to hang on operating system semop() calls. This issue was
introduced in kernel level 2.6.32-434.

....

Best regards,

Mike, x7942
RMD IT Client Services

On Fri, Feb 6, 2015 at 8:45 AM, Sims, Richard B <rbs AT bu DOT edu> wrote:

> 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
>
>