Richard,
Thank you very much indeed for taking the trouble to respond.
The information you've provided is spot on. By omitting the space between
the > symbol and the filename all my troubles are gone. And only one set of
double quotes.
Joy!
Cheers,
Eric Winters
Sydney Australia
|---------+---------------------------->
| | Richard Sims |
| | <rbs AT BU DOT EDU> |
| | Sent by: "ADSM: |
| | Dist Stor |
| | Manager" |
| | <[email protected]|
| | .EDU> |
| | |
| | |
| | 01/07/2003 10:39 |
| | PM |
| | Please respond to|
| | "ADSM: Dist Stor |
| | Manager" |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: ADSM-L AT VM.MARIST DOT EDU
|
| cc:
|
| Subject: Re: Correct syntax for defining objects in command schedule
|
|
|
|
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
>I need to use the administrative command line interface to define a client
>schedule which will run the following command;
>
>/dir/script > /dir/log 2>&1
>
>Looks simple enough. After all, I just need to define a schedule with an
>action of command and objects with the command in it. But I'm having
>difficulty in establishing the correct syntax for quoting those objects.
>The reference guide advises that multiple objects should be double quoted
>with single quotes around the whole lot. In this case it doesn't work.
Eric - The Ref Manual, in talking of "multiple objects", is talking about
encoding multiple file names which may contain blanks, which thus
need to be stored in the server as double-quoted constructs.
That's different from what you seek to do: you have just the command
string.
You want to enter:
def sched domain schedule_name action=command starttime=18:00
objects="/dir/script >/dir/log 2>&1"
Note the removal of a space from around the redirect, which prevents TSM
from recognizing it as a redirect for it, but allowing it to be a Unix
redirect.
(I tested this via DEFine CLIENTAction before replying, to be sure.)
Richard Sims, BU
|
