Environment Variable Import

bobyon · Post by **bobyon** » Tue Jul 07, 2015 3:17 pm

I'm working on developing a routine (script) for setting environment variables. I know there are the dsadmin commands of envadd, envset and envdelete. I also find now that export and import are available via the DS Administrator GUI.

Has anyone found a way to initiate the import from a command line?

The dsadmin commands also don't seem to provide the ability to add/update the variable description. Is there an option for setting the description?

Thanks,
Bob

ArndW · Post by **ArndW** » Wed Jul 08, 2015 7:59 am

I haven't looked around for a command line method, but if you are moving ALL of the environment settings from one project (or machine) to another, you could copy the "DSParams" file in its entirety.

qt_ky · Post by **qt_ky** » Wed Jul 08, 2015 10:10 am

We do some scripted "sed" find/replace commands on the DSParams file for certain settings that cannot be changed via the dsadmin command. The same could be done for inserting env vars rather than importing via dsadmin.

bobyon · Post by **bobyon** » Wed Jul 08, 2015 1:13 pm

Mostly this will be used to add new environment variables.

FranklinE · Post by **FranklinE** » Wed Jul 08, 2015 1:48 pm

You need a good Unix script writer. We have a ksh script to import environment variables. The command line is documented, so mostly you need to set your Unix environment.

We use a ssi file to keep all environment variables. Updating them or adding new ones is as simple as editing the ssi file and running the script.

rkashyap · Post by **rkashyap** » Tue Jul 14, 2015 8:59 am

Note that IBM InfoSphere Information Server, Version 11.3.1.1 (Fix Pack 1) has a patch for a setenv issue. This issue can (once in a while) corrupt dsParams file.

chulett · Post by **chulett** » Tue Jul 14, 2015 10:05 am

FranklinE wrote:We use a ssi file to keep all environment variables.

Forgot that this was something I wanted to ask about - "ssi file"? All my searches turn up is a flood of Social Security Income references. Guessing that's not what you meant.

FranklinE · Post by **FranklinE** » Wed Jul 15, 2015 10:36 am

I forget what the acronym is supposed to represent. What I know is there's a standard path that ends with etc/ssi/ in which these files with extension .ssi are kept. They are text files with bunches of variables relevant to the process being run. They are sourced in at runtime.

Our DS ssi files contain all project-specific environment settings, such as default paths (/data, /cm, etc.) and settings for sys-level (dev, sat, etc.) that are determined at runtime as well. We parameterize just about everything, and the ssi file keeps us sane.

Edit: search on "unix ssi". It stands for "server side includes".

chulett · Post by **chulett** » Wed Jul 15, 2015 12:41 pm

Awesome, thanks Franklin.

ray.wurlod · Post by **ray.wurlod** » Wed Jul 15, 2015 3:57 pm

So CSI means "client side includes". I wonder if the makers of the TV series are aware of that?

FranklinE · Post by **FranklinE** » Thu Jul 16, 2015 8:34 am

I always ask my server if the sides are included.

ray.wurlod · Post by **ray.wurlod** » Thu Jul 16, 2015 3:49 pm

Do you want fries with that? :D