Author: Gene Shaffer <gene.shaffer AT AURORA DOT ORG>
Date: Thu, 19 Jan 2006 14:50:30 -0600
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:
Author: John Monahan <JMonahan AT COMPURES DOT COM>
Date: Thu, 19 Jan 2006 16:20:43 -0600
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: What interface are you using to create the sched - Admin Cent
Author: Peter Hitchman <Peter.Hitchman AT THOMSON DOT COM>
Date: Fri, 20 Jan 2006 03:35:53 -0500
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 com
Author: Gene Shaffer <gene.shaffer AT AURORA DOT ORG>
Date: Fri, 20 Jan 2006 13:24:56 -0600
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
... 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 a
Author: Gene Shaffer <gene.shaffer AT AURORA DOT ORG>
Date: Fri, 20 Jan 2006 16:08:37 -0600
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 m
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_b