DSXchange

My bad. My awk WAS slightly different then yours. I changed mine and added double quotes. Here's the error when it works correctly; Sequential_File_0,0: Filter status 256; filter process failed: 1; import error at record 0. Here is my awk; awk -F'\t' '{if( FILENAME != " #PATH#/ " ) {print...

It worked for me both within DS and from the command line. Perhaps FILENAME = #FileDirectory#/ will never equal #FileDirectory# (without the slash). I would suspect a snytax problem if the awk with the condition worked before. Perhaps you need to enclose the && (condition) in parens to ensu...

awk -F'\t' '{if(<condition>) {print $0}}' #FileDirectory#/#Filename# Try awk -F'\t' '{if(<condition> && FILENAME != #FileDirectory#) {print $0} else {exit 1}}' thanks for taking the time off to reply robinson... I tried the above. But the following two issues arise: 1) The condition (which ...

Thanks for replying kumar,

Okay that makes sense... But , is there a way to make the job abort in this case? .. I'm trying my best to avoid using the Filter stage..

Anyway to make the job abort even with the awk script in place..

My job contains two parameters for the File directory - #FileDirectory# FileName- #Filename# The Sequential File stage contains a filter with some awk code in it to filter out some records with the two parameters at the end of the awk code line... Filter looks like this: awk -F'\t' '{if(<condition>)...

Can someone provide some inputs on this ? Disadvantages or otherwise with regard to this approach?

Hi, I thought i'd post this. I think I found a solution/workaround to the problem mentioned. Thought we can use a user-defined insert SQL in the Oracle Stage by leveraging the LEVEL pseudocolumn in the Oracle d/b. Its pretty handy.. syntax can be found here: http://www.psoug.org/reference/connectby....

Query in Sparse lookup will be executed every time when each row enters the stage. And hence you get the new sequence number generated. Increment of the sequence number is the job of Database not Datastage. Yeah, i got that ... but... on what are they doing the column matches? There is no key expre...

In the DataStage Parallel Job Developer's Guide, they mention that when we have a user generated SQL query, we have to use sparse lookups. Is there a reason why they suggest this ? On what basis does the lookup happen when the mode is Sparse Lookup. In my job, there are no key column matches in my L...

Create a dummy column along with the Nextval, say with the constant value '1' and lookup on that. If you MINVALUE starts with negative, there is a possibility to get 0's, else no. ... Thanks ArndW and Kumar, this approach works. :) I get your point about the performance overhead but right now there...

...Using a reference lookup to a unique Oracle sequence is another option, but it will severely impact performance... Havoc - this is a solution Hey Arnd, Just tried out the above method. But got a question..On what key can we join the input data with the Oracle sequence to get the nextval? Tried t...

ray.wurlod wrote:Will these jobs be running consecutively or simultaneously? ...

Hi ray,

these jobs will be running simultaneously, still havent found a solution as to how we can go about implementing this. The unique identifer should be a sequence too

I think using job name is better - since the JOBNO for a job may change (re-import to another project, saving of a copy, etc.). Are you looking at something like an Oracle Sequence, but driven from DataStage? Well that is the point but we have to load this same sequence number for three other jobs....

Why not use JOBNO? This is stored in DS_JOBS. You can easily look it up based on the job name. How can we leverage the JOBNO to create a unique identifier? One more query is this JOBNO dynamic or static? Basically there are multiple jobs and we have to avoid clashes when generating this unique iden...

Hi , I have a scenario in which a unique identifier or a sequence number must be generated across jobs i.e. there are multiple jobs inserting on the same table and should insert the next sequence number/unique identifier per job. This unique identifier should then be passed and be inserted in TWO ot...