Hi Thomas!
This puts me on the right track, thanks!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: Rupp Thomas (Illwerke) [mailto:thomas.rupp AT ILLWERKE DOT AT]
Sent: Friday, August 02, 2002 16:03
To: ADSM-L AT VM.MARIST DOT EDU
Subject: AW: Housekeeping through a TSM script
Hi Eric,
we do a reschedule of the Job if processes are still running.
/* Still Processes running? */
/* If YES reschedule Job */
select * from processes
if (rc_ok) goto reschedule
/* Start Backup of Storagepools etc.*/
ba stg ARCHIVE COPY_BREGENZ wait=yes
....
ba db dev=3590E type=full
delete schedule r_copy_backup type=a
exit
/* Restart Schedule */
reschedule:
delete schedule r_copy_backup type=a
def sch r_copy_backup type=admin -
cmd="run Ill_Copy_Backup" active=yes -
startt=NOW+0:20 duration=5 durunits=minutes -
perunits=onetime expiration=today+1
Hope this helps
Thomas Rupp
Vorarlberger Illwerke AG
MAIL: thomas.rupp AT illwerke DOT at
TEL: ++43/5574/4991-251
FAX: ++43/5574/4991-820-8251
> -----Ursprüngliche Nachricht-----
> Von: Loon, E.J. van - SPLXM [SMTP:Eric-van.Loon AT KLM DOT COM]
> Gesendet am: Freitag, 02. August 2002 13:00
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: Housekeeping through a TSM script
>
> Hi TSM-ers!
> At this moment al my maintenance processing is scheduled at specific
> hours.
> I'm thinking about creating a script which starts all maintenance, one
> after
> the other. The only problem I have is that I cannot find a way to see if
> reclamation has finished. Most of the administrative task have the
> wait=yes
> parameter, so the script waits until the task is finished, but since you
> schedule reclamation through the update stgpool command one can't use that
> trick here.
> I thought about issuing a q proc command every 10 minutes and capturing
> the
> return code 11 (no processes found) but a sleep 600 or something like that
> is not supported in a TSM script.
> Does anybody else have an idea how to do this? AIX scripts are not an
> option
> due to security reasons (userid and passwords in the script).
> Thanks in advance!
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
>
> **********************************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and
> may be unlawful. If you have received this e-mail by error, please notify
> the sender immediately by return e-mail, and delete this message.
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in
> receipt.
> **********************************************************************
----------------------------------------------------------------------------
--------------
Dieses eMail wurde auf Viren geprueft.
Vorarlberger Illwerke AG
----------------------------------------------------------------------------
--------------
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM),
its subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible for
any delay in receipt.
**********************************************************************
|
