Hi,
When you set these things up, remember that the command is being passed
to a shell for execution, since most Unix shells do not like a space
between a redirection operator and a filename, the command is probably
failing. You should find the failure logged on the client in tsm home
area.

Regards

Pete

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
John Monahan
Sent: 19 January 2006 22:21
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Gene - syntax/punctuation for an object in a
schedule


The entire command should be surrounded in single quotes.  I believe it
will also help if you remove the space before backset.out like so:
>backset.out

What interface are you using to create the sched - Admin Center, older
web admin, or command line?


______________________________
John Monahan
Senior Consultant Enterprise Solutions
Computech Resources, Inc.
Office: 952-833-0930 ext 109
Cell: 952-221-6938
http://www.computechresources.com




Gene Shaffer <gene.shaffer AT AURORA DOT ORG>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> 01/19/2006
02:50 PM Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Gene - syntax/punctuation for an object in a schedule






Hi;
I am creating a schedule that invokes a script which generates
backupsets. The Action field is set to COMMAND and in the Object field I
am trying to pass the string to execute the script. It is: nohup
./backupset/gen_backupset2.sh  > backset.out

I believe it needs single or double quotes or something around either
the whole line or part of the line. I have tried numerous permutations,
but when I update it with TODAY and NOW to get it to run and test it out
it just sits there. Any ideas?

Gene Shaffer
Software Systems Engineer
Aurora Health Care

" Experience is something you don't get until just after you need it"