DSXchange

Welcome. That setting already *is* 'global' and will apply to all jobs. What kind of problem are you having?

You can't quote a field name, it will end up as a literal as you found. And you need to qualify the field name with the stage name, StageName.A would be more appropriate if you've got the field name correct.

How much help do you need? You use a colon to concatenate so simply mention the two field names separated by a ":".

You mean 185, yes?

You'd need to provide the decimal value for the character, much like you need to use '009' for a TAB. Oh... and welcome. :D

Best approach would have been to have parameterized anything that could change - including schema. And no, I don't believe you can 'fix' imported table definitions that way but have never tried, never having had the need.

You need to find out who is in the log and ask them to get out. It could also be a failed / zombie process that you'll need to find and kill. The first way to try would be using the 'Cleanup Resources' option in the Director on that Server and in that Project... unless there is a more better way in ...

You still need to try and reset the aborted job and see if anything shows up from the previous run. Also missed this in the first go-round: Also, reg. the usage of NOTFOUND, I am using that for Hash file references only. There are two Hash files out of which I am looking up values and I have used NO...

Right, which is what Ray suggested you look for if I recall correctly. Or it could be another process entirely - for example, on Windows servers we've seen Anti-Virus software do crap like this.

The project directory of the job in question.

So you meant "does not appear as link ordering issue", yes? Do as Ray suggested and check the actual source code around line 185 in the code it mentioned in the error, it will help figure out what is causing the problem.

From what I recall, the Filter has a tendancy to strip quotes or stop when it hits the first one. You can try escaping them or maybe try doubles? Might help, might not.

Please repost this question in the appropriate forum - the PX forum. This is for a different product, with a (granted) very similar name.

You'd need to expand on your "does not work" statement in the other post or the "encountering problems" one here. How about some examples of what you are putting in the Filter and what the end result is?

prasson_ibm wrote:Even u convert MEM_ID to numeric data type it wont match the ref. data set,u have to remove leading zeros......

Numeric data types don't have "leading zeroes".