.
There's an easier way to get the node number. It's explained very well
at http://www.lascon.co.uk/d005303.htm so I won't repeat it here. Just
beware that the result of this process of starting at NODE 38 will be a
number in hex. You must convert it to decimal for use on the
undocumented args to the EXPIRE INVENTORY command.

I do this all the time, if I know there's some client node that has a
bunch of tapes tied up that could be freed for reclamation by starting
expiration with that node. Works great, especially if you're digging out
of one of those awful expiration mudpits where you run out of scratch
tapes and your database is bloated. (Why does this happen when I go on
vacation?)

OTOH, to skip a node, you could control expiration with a TSM Script
that contains two EXPIRE INVENTORY commands. For instance, if you figure
out that you want to skip node 42 (decimal) you could put these in your
script:

  expire inventory beginnode=1 endnode=41
  commit                    (not sure it's needed but it can't hurt)
  expire inventory beginnode=43 endnode=999999

One caveat I discovered the hard way is, you cannot start this script
manually from a dsmadmc session. You must start it via an admin
schedule. The reason is just like the unix nohup command. If you do run
it manually, then you must keep that dsmadmc session logged in until the
script finishes, or else it will stop when you do. What will happen is
that the first EXPIRE INVENTORY command will run to completion, but the
second one will not start. RUNning it via a 1-time admin schedule solves
that problem. (To make an admin schedule run only once, add the
EXPIRE=TODAY option.)

Just beware that as somebody else pointed out, skipping expiration
probably will not accomplish what you want. Instead you need to assign
that node to a different policy domain where things are kept forever.
I keep one of those handy for cases of e-discovery.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
There are only 10 types of people in the world: Those who understand
binary, and those who don't ...


On Fri, 15 Aug 2008, Schneider, Jim wrote:

>
>To run expiration for one node use the following undocumented
>parameters:
>expire inventory beginnode=<number> endnode=<number>
>
>To get the node numbers, use the following case-sensitive commands from
>a dsmadmc session:
>create sqltable Nodes Mynodes
>select c0,c1 from Mynodes order by c1
>drop sqltable Mynodes
>
>To bypass expiration on one node use a pair of commands.  I wrote a
>script to issue the first command, wait for it to end, then issue the
>second command.
>For example,
>expire inventory beginnode=<first node in list> endnode=103
>expire inventory beginnode=105 endnode=<last node in list>
>
>The nodes are numbered in the order in which they were registered.
>There will be gaps if any nodes were deleted.
>
>Hope this helps,
>Jim Schneider
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
>Zoltan Forray/AC/VCU
>Sent: Friday, August 15, 2008 10:59 AM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: [ADSM-L] Expiration
>
>I would like the reverse.......to run expiration AGAINST one specific
>node.   I hope V6 adds this.
>
>
>
>"Lepre, James" <jlepre AT SOLIXINC DOT COM>
>Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>08/15/2008 11:50 AM
>Please respond to
>"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>To
>ADSM-L AT VM.MARIST DOT EDU
>cc
>
>Subject
>Re: [ADSM-L] Expiration
>
>
>
>
>
>
>Hello Everyone,
>
> Is there a way to stop expiration from happening on a certain Node?
>
>Thank you
>
>James Lepre
>
>
>
>
>---------------------------------------------------------------
>Confidentiality Notice: The information in this e-mail and any
>attachments
>thereto is intended for the named recipient(s) only.  This e-mail,
>including any attachments, may contain information that is privileged
>and
>confidential  and subject to legal restrictions and penalties regarding
>its unauthorized disclosure or other use.  If you are not the intended
>recipient, you are hereby notified that any disclosure, copying,
>distribution, or the taking of any action or inaction in reliance on the
>contents of this e-mail and any of its attachments is STRICTLY
>PROHIBITED.
> If you have received this e-mail in error, please immediately notify
>the
>sender via return e-mail; delete this e-mail and all attachments from
>your
>e-mail  system and your computer system and network; and destroy any
>paper
>copies you may have in your possession. Thank you for your cooperation.
>