As Andy says, "The command line is your friend." It can be used for comparison testing, starting with basic interactions such as 'dsmc query session', and working upward to B/A operations as needed. You mention the command line hanging, but then also talk about opening a window, so are you really talking about dsmj? If really dsmc, consider client tracing with that more straightforward case.
Which flavor of "GUI" is it? Web type client or dsmj? If the former, check for any problem indications in dsmerror.log and dsmwebcl.log. If the latter, don't overlook all the issues that one can have with Java. Java was supposed to be the universal, runs-anywhere facility, but it suffered a lot of schizophrenia in the history of its development, where any number of problems can prevail - not the least of which is its heavy demand on memory resources, all the more problematic in a computer which already has a good workload. Richard Sims On Feb 12, 2009, at 3:13 PM, Steve Stackwick wrote:
All, I have a W2K3 SP2 32bit server whose brand new TSM 5.5.1 client install is behaving peculiarly. The GUI hangs at Initializing (though it does start after a *LONG* time), the command line hangs at an open window, likewise. The usual suspects: this is not a cluster, and the admin sez he tried to apply the VSS fix and was told it was superseded by what was already on the machine. Any clues?