DSXchange

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!

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!

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.

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....

just to be on the safe side, i changed the sequencer parameters (hard coded) and put $PROJDEF at job level...
it still picks up the job level parameters
can anyone plz tell me where I'm going wrong here?

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?

yes, i do expect an automatic override...

my understanding is this: if the job sequence has parameters defined, and so does the jobs run by the sequence, then the sequence parameters should override the job level parameters.

isn't that how it should work?

No, not automagically. Simply having 'the same parameters' defined in both doesn't mean squat - they must be passed from parent to child to 'override' the default values in the child.

not same...i have different values in both..
i need to know whose parameters will work

not same...i have different values in both..
i need to know whose parameters will work

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).

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.

Thanks! was pretty confused earlier.