I second Jim's advice. Especially on our servers with large number of files, using the managedservices option saves TONS of memory. We had one server that after a few weeks, DSMC.NLM was using nearly 3/4 of a gig of RAM. Using managedservices and dsmcad.nlm solved the problem.
Matt Zufelt Southern Utah University >>> [EMAIL PROTECTED] 03/05/03 02:31PM >>> Do it! Run managedservices webclient schedule. I'd advise upgrading to the 5.1.5.6 client to avoid an potential problem with the client trying to grap an invalid port, I believe it was an nwipcport error. Other than that it's been good, helped with the memory release issue a lot. Mark Hayden wrote: > I have been reading about a option called " managedservices " that you > put in the dsm.opt file to help resolve memory problems that the TSM > scheduler causes by not releasing the memory back to the NetWare > Server....We have had ongoing problems with this forever. I would just > like to know if anyone is using this option on any NetWare clients???? > Thanks > > I would like to try this with the option" managedservices schedule" to > see if this helps.... What do you think? > > Thanks, Mark Hayden > Informations Systems Analyst > E-Mail: [EMAIL PROTECTED] -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
