Page 1 of 1

DSParam file values not reflected in ADMINistrator

Posted: Sat Jun 21, 2008 3:02 am
by ArndW
I've just encountered a very odd scenario that I am at a loss to explain. I've installed a fresh V8 AIX system, created a project and then added the "[EnvVarValues]" section information (about 30 values) to the DSParams file in that project. This was done when no clients were active. When I go into the ADMINistrator tool to look at the environment values these additions are not visible. I then added a dummy variable, "aaa" to the user defined variables and saved it. The DSParams is updated with this value and all the other ones I entered are gone. I replaced these values, removed the "aaa" entry and saved the file in VI. Closed down the clients and restarted DataStage. Checked the DSParams file to ensure that the changes I made are still there. Rebooted my PC. Went into the ADMINistrator and see that the "aaa" entry is still there and none of my changes are visible.

I am now one confused DS'er. What could be happening?

Posted: Sat Jun 21, 2008 4:47 am
by ray.wurlod
The obvious thing that might have changed is the version of DataStage. Have you ever had this technique work with an 8.x installation? We know it's OK in version 7.x, but that doesn't have a common metadata repository (XMETA). My guess would be that the common repository is now the single source of truth for DataStage project-defined environment variables and that, yes, this represents a change in functionality. I can't test this during the weekend.

Posted: Sat Jun 21, 2008 4:54 am
by ArndW
I am fairly sure, but not certain, we did this on some of the other 8.0.1 installations here - although they were on Solaris and this is AIX.

There must be information stored elsewhere - in the ADMIN tool one must type in a prompt for each user defined setting. The DSParams file doesn't contain the text for this prompt. Right now I am assuming that DS now sources this information from the bowels of the IIS server instead of from the DSParams file.

Posted: Sat Jun 21, 2008 4:17 pm
by ray.wurlod
This "loss of functionality" has serious implications for transfer of environment variables from project to project, and probably should be reported to IBM as a grizzle.
Or, if it's a bug in AIX implementation only, again IBM needs to know about it.