Hi Everyone,
A team member ran into an issue where they had a Sequence defined that called 20 or so parallel jobs. One of the job activities in the sequence accidentall had an incorrect database connetion parameter defined and subsquently caused the underlying parallel job to fail. I was reading up on the validating a job functionality here and was curious if running the Validate option on the job sequence would in fact validate each of the parallel jobs inside of that sequence to make sure the passed down parameters and database connections etc... would work.
Our test case turned up negative in that the Validate button only validated that the Sequence job would run successfully. I was wondering if anyone knows of any best practices that we could adopt to test all of the passed down parameter settings for large job sequences such as this one. I know that it is really each developers responsibility to ensure that they are passing down the proper variables in their job activities, but I was curious if there was any automation that we could use.
Thanks so much,
Josh
Validating jobs
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 40
- Joined: Thu Apr 17, 2008 1:52 pm
- Location: Huntsville, AL
Re: Validating jobs
I wish someone should say YES. But my answer is NO.
DS User
DS User
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 40
- Joined: Thu Apr 17, 2008 1:52 pm
- Location: Huntsville, AL