DSXchange

info_ds wrote:DsGuru2B, I didnt know that your name was Brian

Yea, I didnt know either.

While doing a join, select TableB's key a well. All new records will have null key from TableB. Filter that in the transformer by putting a contraint. Or you can also filter in the sql select.

I have no experience with ADAM. The message that I wanted to convey with my previous post was, that as long as you can write a stand alone piece of code that executes and provides the right result, you can invoke it from within datastage.

Craig is right. Use the dsjob command to redirect your log to a file. Utilize the power of unix to parse your own custom log.

What exactly do you want fromt he repository tables? Kim is the leader in querying repository tables. You can search for code by his id "kduke". There are others as well. Search will help.

Time to mark your post as "Resolved".

Post here some sample data, a few values, for that particular column.

Do you mean UNIX New Line?
If yes, then you can set it in the format tab under Record Level property Record Delimiter.

This is not a datastage issue but rather the type of database. I have, in the past, inserted space in not null columns in a SqlServer table.

Do as it says. Let it be decimal, go to extended properties for that column and set either the width or max width which should be 19 for you I believe (1 for decimal point, 1 for sign, 17 length). Try it out.

Where is your lookup coming from? Is it a database or a flat file? If database, then write sql to select max date and status grouping on S.No. Load the result to a hashed file keyed on S.No. Now your hased file contains the latest status for a S.No. From here on do the normal lookup against the hash...

The control really depends upon how you design. If you need restartability you need to make the sequence jobs restartable. If you have a few jobs then putting them in a single line is ok but if you have many jobs, then build sequences and child sequences. Or simple write a batch job, in which you ha...

In what order do you want to run them? Ray's solution will work for you if the answer to his question is, "It does'nt matter", which is rarely the case. Build a file which has all the job names in the order in which they need to be run. Cat the file, read it one by one and pass it to the dsjob -run...

You can only execute stored procedures form native api stages. Any return values will be either ignored and or the stored procedure wont run. Its better to create a small script that fires off your stored procedure and gets the return code. This way you can fire off the script in the before/after jo...

Something is off. What is your source. Regardless, check the row counts of your source and then do a comparison with target. Something fishy going on with what you see on the designer as rows. You sure no other process going on? Like an after job subroutine that doubles the file or soemthing. Someth...