Richard,

Thanks for the mail. I indeed started dsmserv in the $DSMSERV_DIR
directory.
The error also show when running the "register license command":

TSM:SERVER1>
register license file=*.lic
ANR2017I Administrator SERVER_CONSOLE issued command: REGISTER LICENSE
file=*.lic
ANR2852I Current license information:
ANR9639W Unable to load Shared License File dsmreg.sl.
ANR2032E REGISTER LICENSE: Command failed - internal server error
detected.
TSM:SERVER1>

I also tried copying all .lic and dsmreg.sl file from the production
server, but no luck.

Geert


Richard Sims <rbs AT bu DOT edu> wrote on 12/12/2005 20:18:39:

> Geert - Two things I would check into...
>
> First, that dsmserv was started while sitting in the server directory;
> two, that dsmreg.sl actually is in the server directory.
> It *might* be the case that there is a dsmreg32.sl there instead: if so,
> try creating a dsmreg.sl symlink to it.
>
>     some hunches,  Richard Sims
>
> On Dec 12, 2005, at 1:59 PM, Geert De Pecker wrote:
>
> > Hi all,
> >
> > We are replacing our old tsm backup server (running 5.1) with new
> > hardware
> > and TSM 5.3.
> > So far, we did all configs on the server working with a single
> > client and
> > are about to start
> > testing with multiple clients.
> >
> > When I tried connecting woth another client (after registering the
> > node),
> > I got messages
> > telling us that the licensing was not ok.
> >
> > When starting the dsmserv, I also noticed the following message:
> >
> > ANR9639W Unable to load Shared License File dsmreg.sl.
> >
> > We are not able to register the licenses with "register license
> > file=*.lic".
> >
> > Platform is suse sles9.
> >
> > I can't find any hints on the net and would appreciate any help.
> >
> > Kind regards,
> >
> > Geert
>