Hi All,
Can anyone tell me the difference between $ENV and $PROJDEF values specifying for the environmental variables.
Difference between $ENV and $PROJDEF
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
When a UNIX process runs it runs in a shell in which there are some shell variables and environment variables defined. Exported environment variables are available to any sub-shells invoked from that shell.
When you run a DataStage job, your shell starts a number of sub-shells. Some of these run uv, uvsh, dssh or osh. Any of these has access to the exported environment variables. The special default value $ENV is an instruction to obtain the actual default value from the exported environment variables available to the shell.
Each DataStage project can have a list of other environment variables defined. These are configured in the Administrator client and stored in the DSParams file for that project. These environment variable values are the ones that are accessed via the special default value $PROJDEF for a job parameter environment variable.
To complete the picture there is a third special value $UNSET which instructs the job to unset the environment variable unless a non-default replacement value is supplied. This is useful for those environment variables that switch on diagnostics/tracing if they are set.
When you run a DataStage job, your shell starts a number of sub-shells. Some of these run uv, uvsh, dssh or osh. Any of these has access to the exported environment variables. The special default value $ENV is an instruction to obtain the actual default value from the exported environment variables available to the shell.
Each DataStage project can have a list of other environment variables defined. These are configured in the Administrator client and stored in the DSParams file for that project. These environment variable values are the ones that are accessed via the special default value $PROJDEF for a job parameter environment variable.
To complete the picture there is a third special value $UNSET which instructs the job to unset the environment variable unless a non-default replacement value is supplied. This is useful for those environment variables that switch on diagnostics/tracing if they are set.
Last edited by ray.wurlod on Sat Apr 10, 2010 3:17 pm, edited 1 time in total.
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.