Thanks, but just knowing a job is enabled isn't quite enough.
A little more detail:
I run two tape jobs to a tape server that also runs BAckup exec (until I'm confident enough to switch to Veeam)
To run a veeam tape job I need to stop BExec services so have written a PRE-JOB script to check if there are any active BExec jobs and, if not, stop the services, otherwise check again in 5 mins, up to an hour)
I also have a POST-JOB script that starts the BExec services again after the Veeam tape job.
All of this works fine, but because I have 2 tape jobs and they must be run in serial (because only 1 tape drive available) I run the second job right after the first job.
So, it would save me a little time, plus be a bit more efficient, if I could know that the second job was chained to the first so I could build logic into the POST-JOB script to say "if there are no other jobs chained to this one, start the services again, otherwise leave them stopped. (Note: my PRE-JOB script only stops running services anyway)
I want to build in this intelligence in case I later run the second job under its own schedule rather than chained, in which case the first job will automatically restart the services when completed.
Hopefully this makes sense?
(It has also been a learning exercise with Powershell which I just don't do much of these days so want to keep my hand in...)
[New Sig: PLEASE get GFS tape support for incrementals!!!]