Job Parameters override
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 73
- Joined: Thu Mar 08, 2007 9:50 pm
- Location: Bangalore
Job Parameters override
Hi,
I have a query.
The server jobs have job properties.
Also, sequences (schedulers) have job properties.
Can you tell me who has greater prominence? As in, can server job parameters override scheduler job properties? or is it the other way around?
Thanks!
I have a query.
The server jobs have job properties.
Also, sequences (schedulers) have job properties.
Can you tell me who has greater prominence? As in, can server job parameters override scheduler job properties? or is it the other way around?
Thanks!
Re: Job Parameters override
What ever parameters given through Sequencer or scheduler is taken finally. As we call sequencer first and then sequencer in turn calls jobs,we pass sequencer parameters to jobs.so sequencer have greater prominence I think.Rea_Antony wrote:Hi,
I have a query.
The server jobs have job properties.
Also, sequences (schedulers) have job properties.
Can you tell me who has greater prominence? As in, can server job parameters override scheduler job properties? or is it the other way around?
Thanks!
Thanks, BK
-
- Participant
- Posts: 73
- Joined: Thu Mar 08, 2007 9:50 pm
- Location: Bangalore
yes, that is what I thought too.. but that isn't what happened when I tried to test it
see, i have a sequence. I have given $PROJDEF values
I have one job as part of this sequence. In the job parameters, i have hard coded the source,target etc..
As per my understanding, the sequence level parameters should ALWAYS override the job level. But when i run teh sequence, the job parameters only work and teh sequence parameters are ignored....![Confused :?](./images/smilies/icon_confused.gif)
![Sad :(](./images/smilies/icon_sad.gif)
see, i have a sequence. I have given $PROJDEF values
I have one job as part of this sequence. In the job parameters, i have hard coded the source,target etc..
As per my understanding, the sequence level parameters should ALWAYS override the job level. But when i run teh sequence, the job parameters only work and teh sequence parameters are ignored....
![Confused :?](./images/smilies/icon_confused.gif)
-
- Participant
- Posts: 73
- Joined: Thu Mar 08, 2007 9:50 pm
- Location: Bangalore
There's no 'automatic' override at work here, which it sounds to me like you are expecting - you either pass the Sequence parameters to any called job via the Job Activity stage or... you don't. How are you handling things in your Sequence job?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 73
- Joined: Thu Mar 08, 2007 9:50 pm
- Location: Bangalore
-
- Participant
- Posts: 73
- Joined: Thu Mar 08, 2007 9:50 pm
- Location: Bangalore
-
- Participant
- Posts: 73
- Joined: Thu Mar 08, 2007 9:50 pm
- Location: Bangalore
Not sure how many times or different ways you want me to say it.
The child's job parameters will always be in effect unless you specifically pass (or 'override' if you prefer) them in the Sequence job. To be pedantic, that means on the Job tab of Job Activity stage, putting the Sequence job's parameter name(s) in the Value Expression of the corresponding child job's parameter name(s).
![Confused :?](./images/smilies/icon_confused.gif)
The child's job parameters will always be in effect unless you specifically pass (or 'override' if you prefer) them in the Sequence job. To be pedantic, that means on the Job tab of Job Activity stage, putting the Sequence job's parameter name(s) in the Value Expression of the corresponding child job's parameter name(s).
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Turning the logic around, if the Job activity sets the job parameter value using the value of the sequence's parameter, then it is the sequence's parameter value that ends up being used. If the Job activity sets the job parameter value using some other expression then the sequence parameter value is ignored.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 73
- Joined: Thu Mar 08, 2007 9:50 pm
- Location: Bangalore