DSXchange

datastage1 wrote:Is there any way to give points for the correct n helpful answers in these forums as i am new here.

That's coming... currently being tested by a small group of people.

Did the stage generate that SQL or did you? I would think your parameter marker would look more like :1 or ? rather than being bound using a column name.

What Ken is talking about can be done but isn't simple. To get an idea of what would be involved, first create a 'skeleton' job that would be your base job with no metadata in it and export it to a .dsx. Then add in the metadata for one table and export it to another .dsx. Look at the differences be...

Keep in mind the fact that you can only delete a post that doesn't have any replies made to it. You can always edit your own posts, however.

You might want to try clicking on the Help button inside the stage itself.

Why not just do something with a Lookup? Build a table with the subsitution values and use that. When values change or are added, no change to the job itself would be needed.

OP is looking for deletion of category and not job. How do you know this? The OP didn't explicitly state that. My first thought was that they wanted to delete a category - and all jobs in it - from the command line and that's where my money is. Regardless, please be careful about handing out advice...

Exactly. So use a Sequence job to do the check after the job completes and to conditionally send the email.

You don't need a DataStage job to 'combine' or merge two flat files, if the two files have the same metadata and merge means concatenate the two together. Take our Guru friend's cat command and add the missing redirection: cat SRCFILEA SRCFILEB > SCRFILEC A script can do this. Or the Merge stage if ...

You could create an 'empty' hashed file that anything like this could leverage. To clear the source hashed file would be as simple as copying the DATA.30 and OVER.30 from the empty hashed file into the current hashed file's directory. You could also clear it in the GUI. Another link to an Aggregator...

Yes - you specifically need the 7.5x2 version in order to run PX jobs on Windows. With other versions you can only develop PX jobs.

One way would be to search the forum for KeyMgtGetNextValue and you'd find posts like this one.

This is a duplicate post. If you'd like to respond to it, please do so in this one instead.

Writing to a DB with an Update action of Update/Insert or Insert/Update is always going to be slow..in fact very very slow. Always split your Updates and Inserts. Load them through two seperate links and then it will very much faster. I totally agree. Not just slow but typically the slowest way you...

Or: