is this true for tsm running on z/os


----- Original Message -----
From: "David Smith" <davidsm AT BSR.COM DOT AU>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, March 31, 2004 7:33 PM
Subject: Re: tsm and old nodes


> Given that TSM is licensed by processor now and not node (the internal
licensing does not seem to have cought up with the new model) you should be
able to have as many node definitions as you want.  Retired nodes have 0
processors and therefore require 0 licenses.  The TSM 'managed system for
LAN' license field should be updated to 'managed system for LAN CPU' to be
in line with the actual license model.  This is my take on the issue anyway.
>
> If the above holds true, I would not worry about moving any of the old
node data.  Just leave it as it is.
>
> David Smith
> Technical Specialist
> Business Services and Resources
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager on behalf of Tim Brown
> Sent: Thu 4/1/2004 6:56 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Cc:
> Subject: tsm and old nodes
>
>
>
> i have a number of tsm clients that no longer exist physically, either the
server was replaced
> and node name is different on new server or the server was merged with
another server
>
> i want to keep the data but i have noticed that these clients still occupy
a license.
>
> i have in a few cases, exported the node, deleted the file space, deleted
the node
> and marked the tape in the event i ever have to get data of it via the
inport function
>
> is this the best way to handle this kind of situation how do others handle
this
>
> i tried once to reallocate the old filespace so that the new server had
references
> to the old filespace and the current filespace. that process is too
cumbersome
>
> i have some more nodes that dont exist any more and i was going to
> export them like i did the others
>
> Tim Brown
> Systems Specialist
> Central Hudson Gas & Electric
> 284 South Ave
> Poughkeepsie, NY 12601
> Email: tbrown AT cenhud DOT com
> Phone: 845-486-5643
> Fax: 845-486-5921
>
>
>