On the member jobs.
And it would be Job time out on member job right. Not job part time out as I want member job should time out after a certain period.
You probably want both. The job part time out to govern how long the job can run against a particular server, and a job timeout to define how long the job will run in total. Then you should be able to set a job timeout on the batch job to determine how long the batch job should run for.
One question though – is there a reason the job is running longer than it should? Typically you should not need to set job timeouts.
Thanks for your reply Bill.
I guess Job part time out for member jobs would do well as it will ensure auto cancel once the server will reach the maximum time limit decided.
Member Jobs are for taking UFS Dumps etc. for Solaris which might take time.
Once more question, Will Batch Job will automatically detect once I set property on the member jobs individually ? Or I need to recreate batch job once I set the property for job part time out on member jobs ?
The batch job will pickup the changes. No need to re-create