Re: [ADSM-L] Problem running a script from TSM client

Hi,

Thanks for the reply. I'm alrady giving the full path to the
powershell.exe and to the script that should be executed. I'm quoting the
path as it does indeed contain spaces.

Here is an example of the command:

'"c:\windows\system32\windowspowershell\v1.0\powershell.exe c:\program
files\tivoli\tsm\ba\bin\powershell.ps1" e saturday'

I believe that's the correct path to the powershell.exe, however I'm not
connected to the box to check it at the moment.

Having had a read of your excellent FAQ, it sounds like my best option is
to add the following to the client dsm.opt:

SCHED             See what's happening in Scheduler work, as in debugging
                  a POSTSchedulecmd command not getting run.

Regards,
Steve


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT vm.marist DOT edu] On Behalf Of 
Richard Sims
Sent: 31 March 2011 13:15
To: ADSM-L AT vm.marist DOT edu
Subject: Re: [ADSM-L] Problem running a script from TSM client

When you run a command from your shell command line, the prevailing PATH
spec allows finding the command.  Background tasks may not have such PATH
information.  It is essential that OS environment commands used in
pre/postschedule commands employ full paths to assure finding the command.
When a command is not found, the common result is return code 1.  And if
that full string contains spaces, quoting is necessary, as specified in
the client manual.

    Richard Sims   http://people.bu.edu/rbs