Parameter Set Error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
iwin
Premium Member
Premium Member
Posts: 99
Joined: Mon Apr 11, 2005 9:20 pm

Parameter Set Error

Post by iwin »

Hi All,
I have a Master Sequencer running 5 sequencer jobs using a parameter Set until last nite. I had to add 2 new parameters to the parameter set and when i run the master sequencer now i get an error :
CUSTOMER_UNIT_SEQ..JobControl (@Delete_Job_Seq): Controller problem: Error calling DSSetParam(PS.P_EMAIL_ADDR), code=-3
[ParamName does not reference a known parameter of the job]
CUSTOMER_UNIT is the Master sequencer.
Delete_Job_Seq is a Job Sequencer called in the Master Sequencer above.
PS is the parameter set.
P_EMAIL_ADDR is a new parameter in parameter Set PS.

After getting this error, i removed the added parameters and ran the jobs and now i am getting the same error with an existing parameter. This parameter was not changed at all.


Please Advice..[/quote]
Every person you meet knows something you don't, Learn from them.
-- H. Jackson Brown
jhmckeever
Premium Member
Premium Member
Posts: 301
Joined: Thu Jul 14, 2005 10:27 am
Location: Melbourne, Australia
Contact:

Post by jhmckeever »

I had the same issue and resolved it by a combination of re-compiling the jobs which used the modified parameter sets and/or removing and replacing the job activity on the sequence canvas.

J.
<b>John McKeever</b>
Data Migrators
<b><a href="https://www.mettleci.com">MettleCI</a> - DevOps for DataStage</b>
<a href="http://www.datamigrators.com/"><img src="https://www.datamigrators.com/assets/im ... l.png"></a>
devidotcom
Participant
Posts: 247
Joined: Thu Apr 27, 2006 6:38 am
Location: Hyderabad

Post by devidotcom »

I face the same issue.. does any upgrade help resolve the problem.

Also, when we migrate code from one environment to the other (i.e., dev to test) do we need to compile the jobs and sequences?
We received this issue with migrating jobs from one env to the other.
jcthornton
Premium Member
Premium Member
Posts: 79
Joined: Thu Mar 22, 2007 4:58 pm
Location: USA

Post by jcthornton »

It has been my experience that modifying parameter sets is an action which warrants specific foll-up actions to prevent problems.

Upon modifying (or importing the modified parameter set), I will typically do a 'Where Used' for the parameter set and compile all of the found objects.

That step is simply to ensure that everything is in sync and to avoid the types of issues which you are seeing.

I have not seen any patches or upgrades which alter this behavior.
Jack Thornton
----------------
Spectacular achievement is always preceded by spectacular preparation - Robert H. Schuller
Post Reply