DSXchange

Yes. Inside the transformer. Call your routine inside the transformer.

set the final delimiter to end.

Post your routine. You can call DSSetUserStatus() function within that job to set the user status. And then retrieve it in a sequence job as i explained in my previous post.

I am sorry, i meant the delimiter. And i just double checked that you specifically have tab as an option so you dont need to put the ascii value of tab which is 009.

In JobActivity 2, when double click the expression window open, right click on it you will find 'Activity Variables'. Choose that, you will see 3 options. One of them will be $UserStatus. Use that.

what have you specified as the quote character, i mean what ascii value? Its suppose to be 009. Could you please confirm.

kashif007 wrote:Sequential_File_1,0: Delimiter for field "column1" not found; input: <empty>, at offset: 0

Pay close attention to that. What does that mean ???

Read my previous post.

Ok, i missed the part where you said "treat them as a single record". We still need two stage variables. counter | If cond then counter+1 else counter cond | If LEFT(In.Col1,3) = 250 then @TRUE else @FALSE Counter is initialized to 1 and cond intialized to @FALSE. No constraints. Again, orde...

Ok now i am confused. Do you want all the records in the output with a counter in the begining or you just want all the records between 100 and 250 as a single record with a prefixed counter

Heres what you can do Edward. Read the entire row as one record. That means specify the quote and delimiter as 000 and define one column say Col1. You need two stage variables. Say 'StgVar' and 'cond'. The initial value for StgVar is "" and for cond is @FALSE. Their derivations are as follows StgVar...

The in parameters, i believe they are being fed to the STP stage via a sequential file, right ? Make sure there are no leading or trailing spaces.

Compile or Reset. Both. Thanks Craig. You are officially my mentor. I think, this is the second time i made you my mentor, officially.

Well atleast there is a workaround. Yea, i know, sometimes i presumme and over assume....