Weird schedule name generated from defining a client action - Help deleting schedule

dig1tal

ADSM.ORG Member
Joined
Dec 14, 2007
Messages
48
Reaction score
0
Points
0
Location
alderan
Hello,

I was attempting to create a script on the TSMSERVER that defined a client action.
Here are script contents:
define clientaction tsmserver action=command objects='/tsm/scripts/q_courier.ksh' wait=no

Running the script generated a schedule with a strange name:
DOMAIN @29 CMD 05/10/12 09:32:04 5 D Once Any

The client action also associated the TSMSERVER to the schedule:
Policy Domain Name: DOMAIN
Schedule Name: @29
Associated Nodes: TSMSERVER

My issue is that I can't delete the schedule and it is holding up administrative schedules/scripts:

dsmadmc -id=admin -password=password "delete assoc domain @29 tsmserver"
IBM Tivoli Storage Manager
Command Line Administrative Interface - Version 5, Release 5, Level 0.0
(c) Copyright by IBM Corporation and other(s) 1990, 2007. All Rights Reserved.

Session established with server TSMSERVER: AIX-RS/6000
Server Version 5, Release 5, Level 3.0
Server date/time: 05/11/12 10:14:59 Last access: 05/11/12 10:07:20

ANS8000I Server command: 'delete assoc domain @29 tsmserver'
ANR2600E DELETE ASSOCIATION: Invalid schedule name - @29.
ANS8001I Return code 3.

ANS8002I Highest return code was 3.

I suspect the '@' is preventing me from deleting the association and schedule. I've tried escaping the quotes as well as running the command from the console with no luck.

05/11/12 08:44:17 Next operation scheduled:
05/11/12 08:44:17 ------------------------------------------------------------
05/11/12 08:44:17 Schedule Name: @29
05/11/12 08:44:17 Action: Command
05/11/12 08:44:17 Objects: /tsm/scripts/q_courier.ksh
05/11/12 08:44:17 Options:
05/11/12 08:44:17 Server Window Start: 09:32:04 on 05/10/12
05/11/12 08:44:17 ------------------------------------------------------------
05/11/12 08:44:17 Scheduler has been stopped.

05/11/12 09:36:50 Scheduler has been started by Dsmcad.

Any input/feedback would be greatly appreciated.
 
Issue resolved, I was not using type=client in the delete schedule command :x
 
Back
Top