Jeanne,
It's just an as I haven't tested it before but I know that command routing can
be used with two different syntaxes :
- one is : server_name:command"
- another is : (server_name) command
And only the second on is valid in TSM scripts.
>From Admin guide :
"Note: When you are writing scripts, you must use the parentheses for server
routing information."
--
Best regards / Cordialement / مع تحياتي
Erwann SIMON
----- Mail original -----
De: "Jeanne Bruno" <JBruno AT CENHUD DOT COM>
À: ADSM-L AT VM.MARIST DOT EDU
Envoyé: Jeudi 7 Mai 2015 17:45:50
Objet: Re: [ADSM-L] AW: EXPIRE INVENTORY problem
Hello. We do use node groups. But what rule would I use if I want to cancel
one of the replications that may be running and I don't know the process number
and if it's still running by 6am, then cancel it? Can I use a 'duration' on a
replication??
This select statement works if I run from the console:
select "TSM_NNNNN:cancel process", cast((PROCESS_NUM)as num(5)) as PROCESSID
from Processes where PROCESS="Replicate Node" and STATUS LIKE "Replicating
node(s) EXCHANGE_BA1%"
(where TSM_NNNNN is your server name on the console prompt)
But trying to use the processid (or PROCESS_NUM variable) in a script wasn't
working for me to cancel it.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Erwann SIMON
Sent: Thursday, May 07, 2015 10:23 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] AW: EXPIRE INVENTORY problem
Hi Jeanne,
No, CANCEL REPLICATION does not support any option and so only allows to cancel
all running replication processes.
If you want to have have more control over you replication processes, you can
replicate by node groups and/or use replication rules.
--
Best regards / Cordialement / مع تحياتي
Erwann SIMON
----- Mail original -----
De: "Jeanne Bruno" <JBruno AT CENHUD DOT COM>
À: ADSM-L AT VM.MARIST DOT EDU
Envoyé: Jeudi 7 Mai 2015 16:09:53
Objet: Re: [ADSM-L] AW: EXPIRE INVENTORY problem
Hello. This is good info.
Does anyone know; if there are multiple Replications happening, would the
'CANCEL REPLICATION' cancel all of them? Can I associate the name of the
replication with it if I wanted to cancel only one of them? (In this case I
know the 'name' of the replication, but not the process number....for scripting
purposes and it's the middle of the night)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Vandeventer, Harold [OITS]
Sent: Thursday, May 07, 2015 8:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] AW: EXPIRE INVENTORY problem
The EXPIRE process finally finished about 6 hours after starting. It reported
as successful but was qualified with "finished before completion" due to being
cancelled.
I got some info from IBM via the PMR.
1: CAN PRO <number> and CANCEL EXPIRATION accomplish the same thing. CAN PRO
requires the process number, but CANCEL EXPIRATION cancels any currently
running EXPIRE process. CANCEL EXPIRATION was created so it could be used in
scripting where the process number would be unknown. Similar to the CANCEL
REPLICATION command.
2: the EXPIRE process works on a filespace-by-filespace basis for a node.
It processes ALL of given filespace, then checks for duration limit. If below
the duration limit, it moves on to the next filespace. If beyond duration, the
process stops.
It's unknown why it took 6 hours to process a single filespace, the typical
time on this server is about 1 hour.
So, something odd, hopefully won't see that again. It really messed up my
maintenance processing with significant that delay.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Michael malitz
Sent: Wednesday, May 06, 2015 10:17 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] AW: EXPIRE INVENTORY problem
Hallo Harold,
you should use the command "cancel expiration" instead of "cancel process".
With cancel expiration you have "checkpointing" at transaction boundaries.
Rgds Michael Malitz
-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag
von Rick Harderwijk
Gesendet: Mittwoch, 6. Mai 2015 16:44
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: EXPIRE INVENTORY problem
If you cancel an expiration, does it not log every transaction, so that when
you cancel, it effectively does a rollback on all the entries in the database?
That might take some time as well...
On Wed, May 6, 2015 at 4:31 PM, Vandeventer, Harold [OITS] < Harold.Vandeventer
AT ks DOT gov> wrote:
> I'm running TSM 6.3.4.300 on Windows.
>
> I have a script that issues EXPIRE INVENTORY DURATION=90 RESOURCE=40
> WAIT=YES.
>
> It was still running over 2 hours after start.
>
> I issued a CANCEL PRO and it's been in "cancel in progress" for over
> 30 minutes.
>
> During all this time, Q PRO is reporting a constant number of nodes
> processed, objects examined and objects deleted.
>
> Database and log space look fine, Health Monitor via the AdminCenter
> GUI looks fine.
>
> What's happening in that process that would cause this behavior?
>
> ------------------------------------------------------------
> Harold Vandeventer
> Systems Programmer
> State of Kansas - Office of Information Technology Services STE 751-S
> 910 SW Jackson
> (785) 296-0631
>
>
> [Confidentiality notice:]
> **********************************************************************
> * This e-mail message, including attachments, if any, is intended for
> the person or entity to which it is addressed and may contain
> confidential or privileged information. Any unauthorized review, use,
> or disclosure is prohibited. If you are not the intended recipient,
> please contact the sender and destroy the original message, including
> all copies, Thank you.
> **********************************************************************
> *
>
|
