Rose,
As Richard suggested, please take a look at the IBM technote (1163079).
Most of the time that this message appears, it is because you
need to specify the:
/EXCSERVER=exchange-server-name
option on the command-line invocation.
Where "exchange-server-name" is your Exchange Server na
As David has suggested, I have also had success with disconnecting and
reconnecting 3584 library network cable.
Scott
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David Longo
Sent: Thursday, October 23, 2008 11:04 AM
To: ADSM-L@VM.MARIST.EDU
S
Hello Everyone,
Has anyone written a script to stop reclamation at a certain point or
know of a way to stop it instantly without canceling the process
manually from the command line. I know you can use the duration
parameter; however this stops the reclamation after it is done with the
curr
A better process might be to put the Reclamation last on the list of
things to run. In other words instead of stopping reclamation to do
other things, do all other things first and then run reclamation.
Or you could create a script to get the process number for reclamation
processes and then canc
It was counter intuitive for me when I first heard it, but the newer
3584 has two network ports on the base frame. Several of our libraries
have both ports configured with IP addresses, and in the event the first
is unreachable, you can use the second.
I always associated this second port with the
James,
This may not address your specific need, but here is how we handle reclaims.
We are running reclamations about 12 to 20 hours a day.
We check every 15 minutes to see if a any other job is accessing a each
storage pool, then check if an admin schedule called "STOP_PROCESSING"
(which does
