Error during running server routine for setting the path

ag_ram · Post by **ag_ram** » Wed Jan 09, 2008 3:19 pm

In the routine I am check the record counts in dataset. If there is no record i am returning 1 else I am returning 2.

After running my routine I am getting this error.

Message to be logged is...
> dsrecords /appl/infoserver/Server/Projects/ILOS_Online_Shopping/datasets/OS_vanavailability_001_ex_TMS.DS_rejstores.ds:exec(): 0509-036 Cannot load program /appl/infoserver/Server/PXEngine/bin/dsrecords because of the following errors:
> 0509-150 Dependent module liborchaix3.a(libtemp.o) could not be loaded.
> 0509-022 Cannot load module liborchaix3.a(libtemp.o).
> 0509-026 System error: A file or directory in the path name does not exist.
>

I feel I need to set some environment variable in the routine before I call dsrecords in DSEecuete inside the routine.

Please suggest me how to set these environment variable. I have tried as we generally do in shell script. But that is not working.

currently my routine code carries as below.

APT_CONFIG_FILE = '/appl/infoserver/Server/Configurations/2node.apt'
APT_ORCHHOME = '/appl/infoserver/Server/PXEngine'
PATH = '%PATH%' : '/appl/infoserver/Server/PXEngine/bin'
ORCHBIN = APT_ORCHHOME : '/bin'
LIBPATH = '/appl/infoserver/Server/PXEngine/lib'

I assume this is not working as expected. Please anyone post how to set these variables in the routine.

regards

ray.wurlod · Post by **ray.wurlod** » Wed Jan 09, 2008 4:41 pm

I guess you posted here because it's a server routine, even though you are in a parallel job. The correct syntax for setting environment variables requires no space either side of the "=" character.

In any case you are not setting environment variables, you are setting DataStage BASIC variables. To set environment variables you need to be in the (operating system) environment, and to use a mechanism that can successfully export the environment variables for use by subsequent and child processes.

By the time you run a before-job subroutine, job parameter values have already been set so that, even if your routine successfully changes the values of the environment variables, the job parameters still retain the values that they had when the job was initiated.

One of the absolute rules in DataStage is that there is no legal mechanism for changing the value of a job parameter once the job is running.

So it appears that you need to find a different approach.

ag_ram · Post by **ag_ram** » Wed Jan 09, 2008 7:11 pm

Thanks.

Just an info...this routine is one of the job activity in seqeucner.

No need of setting environment variables. You are right.

But when I open the routine in designer and tried to run that error was thrown.

But when i ran the sequencer, routine was succesdful. Anyway problem is resolved but just need to know Cant we test the routine in designer?

thanks Ray once again.

ray.wurlod · Post by **ray.wurlod** » Wed Jan 09, 2008 11:15 pm

Alas, no. The Test bed you get in Designer* does not have the fully-featured "wrapper" that a job sequence (= job control routine) has.

* For those on versions earlier than 8.0, read Manager here. In version 8 all Manager functionality has been subsumed into Designer and there is no more Manager client.