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.
I am creating the schedule using the Admin GUI. I tried putting a single
quote around the
string and it just sat there. When I looked at the schedule again it had
stripped the single
quotes out, so I tried a single quote on each end and a double quote
outside of those.
It sat there, but did not
On Jan 19, 2006, at 3:50 PM, Gene Shaffer wrote:
...
nohup ./backupset/gen_backupset2.sh backset.out
...
but when I update it
with TODAY and NOW to get it to run and test it out it just sits
there.
Gene - I seriously doubt that the problem has anything to do with
quotes or spaces.
Sadly enough, on the AIX system that this lives on, /backupset IS the full
path to gen_backupset2.sh.
I'm beginning to lose heart and start considering alternatives like
throwing this in crontab or maybe
some administrative immediate action schedule. I have tried a simple test
script that merely
On Jan 20, 2006, at 5:08 PM, Gene Shaffer wrote:
Sadly enough, on the AIX system that this lives on, /backupset IS the
full
path to gen_backupset2.sh.
Then by all means have that in your specification. Your original
posting
said ./backupset/gen_backupset2.sh which is a relative, rather
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
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
