Hi Gurus !
I noticed a strange behaviour of our TSM server (v 4.1.3.0, on AIX 4.3.3) : I defined
a client schedule loking like this
Policy Domain Name: SP
Schedule Name: SERVER_MIGRATION
Description: server move 4 og. to 1 ug.
Action: Command
Options:
Objects: /home/tsm/dsmc_archive.sh
Priority: 5
Start Date/Time: 10.03.2002 00:00:00
Duration: 10 Hour(s)
Period: 1 Day(s)
Day of Week: Saturday
Expiration: 18.03.2002 23:59:59
Last Update by (administrator): SAX021
Last Update Date/Time: 11.03.2002 09:43:18
Managing profile:
Querying events this morning showed me this schedule as :
Scheduled Start Actual Start Schedule Name Node Name
Status
-------------------- -------------------- ------------- -------------
---------
10.03.2002 00:00:00 10.03.2002 00:00:07 SERVER_MIGRA- PACRS170
Completed
TION
But I found there was an error in our "/home/tsm/dsmc_archive.sh" shell script, that
caused it to fail.
The script looks like :
dsmc archive -archmc=migartion_archive -subdir=yes -quiet -archsyml=no /sapmnt/T21/
dsmc archive -archmc=migration_archive -subdir=yes -quiet -archsyml=no /usr/sap/put/
In the first line of the script, I made a typo, specifiying an inexistant management
class, therefore the script failed !
How is it possible that TSM returns me "completed", as this script failed ? Is it a
bug ? Is there any way checkin the real status of the schedule, without logging on the
node to verify dsmsched.err ?
Thanks in advance !
Arnaud
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
