DSXchange

That routine cannot be edited anyways. Right ?

Only one of you can post. Both dont have to copy the same reply.
Empty result can also mean that the variable has no value defined. When you run your job, in the second entry of the log file, do you see a value for that particular environment variable?

how are you identifying the phantoms. At the unix prompt?
When you do

how many do you see, do they have PPID other than 1?

Thats not necessary and extra work + unnecessary maintenance. As pointed out @INROWNUM and @OUTROWNUM can accomplish the task.

A Phantom is a background process so nothing to be scared of them. If there are warnings in your log file then post them here.

Craig is right. If your environment varialbe is correctly defined via the administrator then run the following command. It takes Arg1 and the environment variable name, without the '$' sign and returns yout he value. envVar=Arg1 Cmd= "env | grep -w " : envVar : ' | awk -F"\="':&q...

Good question. I am not sure what you are going to put there. Do this In the filter command, get rid of the redirection. Basically your filter command will look something like this cat #path#file_1 #path#_file_2 cat #path#_file_3 ......#path#_file_12 In the File section put #path#file_1. I think it ...

NO. It wont. Thats what i wanted to find out. If it does'nt work from command line, it wont work from DSExecute() either.
Go to your unix prompt, type env. What ever variables you see there, only they can be called.
I wonder how it was working before.

I have a routine call for the first row, this is done with the constratin @INROWNUM=1 after that all the rows will continue the processing normally If the routine does'nt require input from your first row and is called before the processing of the rows then you can run the routine while initializin...

Log onto your unix server and run the same command. Does it spit out the value?

Search on the error message. This has been discussed here before.

It wont do the same thing. The constraint is there to make sure that only the records that are present in the lookup go through the ACCEPT link, other way of saying NOT(DSLink6.NOTFOUND). And the ones that fail the lookup will go down the REJECT link. If you take the constraint out then every record...

Thats time is for extraction only or for extrction + sorting + aggregations? If its just extractioin then there isnt much you can do. Execpt extract in chunks using the Multiple instances, load it to sepererate file, do a cat and sort and then in your second job, do the aggregations and load.

That should be ok. So its just enterprise stage connected to lookup thats creating a problem right. If you remove that stage, does the job work?

Use the cat command in the Filter options in the sequential file stage properties. Funnel Stage can get you what you need too.