You're not crazy. I'm seeing it too. I only had one SP5 server and I've just upped the client on it from 5.2.3 to 5.3.2 and it will not load on boot.
Version 5.03.02 Sunday, September 18, 2005 Module DSMCAD.NLM load status OK ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs or a related file: \SYS:/TIVOLI/TSM/CLIENT/BA/dsmerror.log. errno = 6, Perm ission denied Module DSMCAD is NOT loaded. Initialization failure. Check TSM error log for more information. ANS1520E Failure writing to the Tivoli Storage Manager error log: errno = 6, Per mission denied That's the last thing autoexec.ncf with a delay of 5 right before it. The install went fine and the client, API, and books show up as installed in nwconfig. The CAD will load after the server is fully booted. It could possibly be a Novell bug as they may have changed some of the end-stage loading sequences. My purely subjective sense is that Tomcat is loading later for example. Going back to 5.2.3 means things work just fine Good luck with IBM and could you let us know if they find the bug? Andrew Ferris Network Support Analyst iCAPTURE Research Centre University of British Columbia >>> [EMAIL PROTECTED] 2/27/2006 5:21:22 am >>> 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
