Parameter Set Changes - Deploy

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
synsog
Premium Member
Premium Member
Posts: 232
Joined: Sun Aug 01, 2010 11:01 pm
Location: Pune

Parameter Set Changes - Deploy

Post by synsog »

Hi All,
We currently have 3 Parameter Sets and they have been deployed to UAT as part of the first release. Now as part of second release we have added a couple of New Parameters to one parameter set, say PARAM1

Value Files
DEV - DEV_PARAM1_VAULE
UAT - UAT_PARAM1_VALUE

Now when we deploy jobs to UAT, if we also deploy the changed parameter set (PARAM1) it copies over the corresponding value file from DEV to UAT and over writes the values in UAT.

My question is how to do promote changes in Parameter Sets between ENV, does this have to be done Manually in UAT (add the 2 New Params and the corresponding Values) or is there better approach?

Thanks
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

I handle that manually myself, and would also be interested to learn if there's a better way.
Choose a job you love, and you will never have to work a day in your life. - Confucius
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Manually for me too, after performing a Usage Analysis so that I can recompile any jobs that use the Parameter Set once changed. (This is one of the few times we compile in production, and it requires an extra step in the approvals processes.)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply