Timothy Hughes wrote:

Is this just specific to 5.3.2.x? I am planning on upgrading
some Novell clients from 5.2.2 to 5.3.012 next week.

I have seen the problem on both 5.3.0.0 and 5.3.012 as well. Problem is
the server has to be rebooted for the problem to show up. And any
changes you make for testing require a reboot which is why I setup a
test server for the job. :-)

TSM 5.3.2.1
TSM novell client 5.2.2
NW 6.5 SP2

Not sure if the problem shows up in SP2 or not. Definitely on SP5.

Thanks in advance!




Patrick Boutilier wrote:

Richard Sims wrote:

I'm Netware-ignorant, but this sounds like an install problem: see if
you can review what transpired in the install, and check the Readme
file for any gotchas.

Not an install problem since dsmcad loads fine from command prompt, just
not autoexec.ncf

To employ a Unix analogy, it might work as a circumvention if it
could be started by doing a 'cd' to the client directory first, then
launch, which may allow it to find its resources...if that kind of
thing works in a Netware environment.

I believe the problem is that when dsmcad looks for the default dsm.opt
file it is looking in the wrong place (
\SYS:TIVOLI/TSM/CLIENT/BA/dsm.opt instead of
<SERVERNAME>\SYS:TIVOLI/TSM/CLIENT/BA/dsm.opt )

The 5.2.x client does not have this problem, just the 5.3.x client. I
will open up a bug report with IBM since I can duplicate this at will.
Just installed a basic Netware 6.5 server and applied sp5. This bug
shows up right away which is why I am very surprised that nobody else
has run across it.

   Richard Sims