Hi,
When I create a new project, where can I found the default file for the global variable like $PATH, $TMPDIR and the User Defined ?
Thanks
Pey
Parameter File
Moderators: chulett, rschirm, roy
Re: Parameter File
Pey,Peytot wrote:Hi,
When I create a new project, where can I found the default file for the global variable like $PATH, $TMPDIR and the User Defined ?
Thanks
Pey
$PATH, $TMPDIR (syncsort?), and other environment specifications are usually in the dsenv file in $dshome. The UNIX id that administers DataStage (dsadm) should source the dsenv in its .profile, then when the DSEngine is brought up, it inherits all of these.
Hope this helps.
-Howard
Pey,
Also, make sure that your id's source the dsenv file as well....that way, when you open up a shell session through telnet or ssh, you pick up the environment the same way that DataStage does...invaluable for troubleshooting, and nice to maintain that stuff in one place (dsenv) rather than a bunch of individual's .profiles.
-Howard
Also, make sure that your id's source the dsenv file as well....that way, when you open up a shell session through telnet or ssh, you pick up the environment the same way that DataStage does...invaluable for troubleshooting, and nice to maintain that stuff in one place (dsenv) rather than a bunch of individual's .profiles.
-Howard
Re: Parameter File
Hi,Peytot wrote:Hi,
When I create a new project, where can I found the default file for the global variable like $PATH, $TMPDIR and the User Defined ?
Thanks
Pey
you can view these datastage variable through administrator. If you choose project properties General tab you can find a button Environment... when you click that you cansee the variable and the default values and at the same time you can also add some user defined variables aslo
Hope this will help you.
------------------
Neena
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
I really like this feature in version 7.0. Much safer viewing and setting DataStage specific environment variables in the Administrator rather than poking around in the dsenv file directly. I also like the log message whenever a job runs showing all environment variable settings.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn