Why there need to set environment variable while running CLT from inline command ?

vaibhav2288

Hi All,
In last I came at some situations where when I run the CLT from CMD, it works fine, but when I get the result of the CLT by running that in script which is called in inline command I dont get any result.

For example - iwuseradm display-name user;

In this when I run this command from the CMD then get the proper user display name.

But In Custom_instantiation.cfg, I have called the script in which I am getting the reviewers list and according to user ID I am getting the
display-name of user. But when I run this command I dont get any result.

After lot of environment variable printing with or without CMD. I came to know when I set the

$ENV{'Path'} = 'c:\Programs Files\Common Files\Interwoven\lib';

I am able to get the display name. This directory path contains various .dll files.

Any resolution for this......Similarly with iwgroup.exe. for iwgroup we need to set SYSTEMROOT variable to 'C:\Windows'....

Any Cause for this ...........

Please anyone related with this thread....post on this....

ISCBorisB

For whatever reasons (portability perhaps) TS strictly controls forked execution environments.
Almost always they have certain set of TS-provided Environment variables and nothing else.
The set may differ for different execution threads (like inline or callServer) and different OS.

There is absolutely nothing you can do about this. If you need additional Environment variables
your code has to set them.