Had a similar problem... we would perform incremental backups under
     the true node name but push SAP archives as a client named as the SAP
     instance name.  A single machine would have (1) its node name and
     possibly (2) CN1 (3) QA1 (4) TR1 ... anyway, more than one "registered
     node name"  I was worried and in discussions with IBM was told the
     same... must have one license per physical box using the adsm server.

     Since then we have altered the way we push archives and have retired
     client boxes were we have a great deal of excessive licenses anyway so
     I don't tend to worry anymore.

     Dwight




______________________________ Reply Separator _________________________________
Subject: how does the client license work
Author:  HiltonT (HiltonT AT TCE DOT COM) at unix,mime
Date:    2/12/99 8:29 AM


Could someone verify how IBM sells client licenses?  Here's the way I've
always thought it worked.  If I buy 10 licenses, I issue the command
'register license file=10client.lic'.  Since I use closed registration,
every time I register a node that drops my available number of licenses by
one.  So, If I want to have 2 nodes registered for each "box" being backed
up (say one for the regular backup/archive client and one for a
SQL-Backtrack client) then I would have to buy more licenses after
registering nodes for 5 "boxes".

Yesterday I was complaining to our IBM sales folks about having to use an
additional license for our DFS backups because the version 3 DFS client and
SQL-Backtrack can't coexist using the same node name.  They told me that the
ADSM client license is one charge for each "box" being backed up.  So, in my
example above, we would only have to pay for 5 licenses (5 boxes) but I
would register 10 client licenses and 10 nodes.

Which version has everyone else been told?

Tina Hilton
Thomson Consumer Electronics
Systems Software
317-587-4292
hiltont AT tce DOT com