DSXchange

I am getting the following error when trying use the orchadmin command line utility.
I am working on the Windows server 2003 o/s.

"The environment variable APT_ORCHHOME can not be empty.
Please assign it to the proper directory in the DataStage PX install area."

Could you pls tell me what might be the problem?

You need to define the proper path for $APT_ORCHHOME. I'm not sure what it would be for Windows but here's my UNIX;

dev:echo $APT_ORCHHOME
/etl/dev/DataStage/PXEngine
dev:/ADM/oracle/home/z901464:

You need to find where your PXEngine folder resides on your DS Server and map the environment variable $APT_ORCHHOME to it.

I am aware of the process for Unix.
But the similar process is not working in Windows. I am not so sure if I am missing anything.
I have tried setting the $APT_ORCHHOME using the SET command and also in different ways by includig them in Windows Env Variable list (I don't have much experience in working on Windows server) etc.
But none of them seems to be working.
And also I am not able to find the dsenv file also.

So can anybody advise how to setup this?

There's no dsenv file on a Windows server, so everything is via environment variables. Not sure, but I think you need to reboot the server after adding new ones.

if any inone still facing the issue,

can add below two environement without pre-fixing $ to variable in user defined enviorment variable

APT_CONFIG_FILE=C:/Ascential/DataStage/Configurations/2Node.apt
APT_ORCHHOME=C:/Ascential/DataStage/PXEngine

steps 1- goto control pannel ->system propertise -> advance - environment variables - user defined variable -> now set above two environment variables-

Note- path name could be differe

singhald wrote:if any inone still facing the issue,

can add below two environement without pre-fixing $ to variable in user defined enviorment variable

APT_CONFIG_FILE=C:/Ascential/DataStage/Configurations/2Node.apt
APT_ORCHHOME=C:/Ascential/DataStage/PXEngine

steps 1- goto control pannel ->system propertise -> advance - environment variables - user defined variable -> now set above two environment variables-

Note- path name could be differe

Which one do you think will be used when a job runs - the one set via this method or the one set in the Administrator client?

It might be a better approach to set them in the user's startup script.