difference b/w job parameters and environment variables

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
4friends
Participant
Posts: 71
Joined: Tue May 01, 2007 12:51 pm
Location: Mumbai

difference b/w job parameters and environment variables

Post by 4friends »

anybody can explain the difference b/w job parameters and environment variables?
thanks & regards
kk
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Environment variables are part of the (execution) environment - you can use them in operating system shells even on systems that don't have DataStage installed.

Job parameters are exactly what the name suggests; placeholders whose values are supplied when (before) a job run request is issued.

It is possible to use the value of an environment variable to provide a value to a job parameter.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Pre-empting your next question

Post by ray.wurlod »

Premium membership costs less than 30c (about INR12) per day, and will allow you to read the entire posts made by the five premium posters. This is one of the ways that the hosting and bandwidth costs of DSXchange are funded. No-one posting is paid to do so. The revenue from premium membership is totally devoted to covering costs (and does not totally do so).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Govindarajan
Participant
Posts: 24
Joined: Mon Jul 12, 2004 10:16 am

Re: difference b/w job parameters and environment variables

Post by Govindarajan »

Environment variables are at PROJECT level and can be used any jobs are sequencers developed under the project, Whereas job parameters are at job level. On top of it you can create a environment variable and re-assign the value at job level.
Post Reply