DSXchange

If the target table has two keys specified and you are updating it using just one, then that means, your updating the second key as well. In which case there is a high possiblity of duplicates. Thats why you have to specify the same or more number of keys in your update where condition as the keys i...

How many keys does the target table have specified, and how many keys are you providing for the update?

Whats the status on your problem, any progress or stuck somewhere.
Follow Craigs guideline. Its pretty straight forward.

Ok, i think i am giving solution for aborting the Main Control Job. If your controlling the process sequence using DS Basic coding, then you make an explicit call to DSLogFatal(). If you are controlling the process via sequence job, then you need to handle it within the sequence. I do not remember i...

You mean DSLogFatal
Heres the syntax

Within the job control, you need to use the "DSLogFatal subroutine". Look into it in DataStage Help.

That is due to the fact that you are handling it appropriately within your code. In your present code, you are checking the status and if it fails, you are sending out an email. According to the "Main Job", its executing all the statements properly and hence will not abort. I think thats a good prac...

-Load your second table in a hashed file keyed on 'UNIQUE_KEY'. -Specify the following stage variables FirstNameChk: If ISNULL(in.FIRST_NAME)=1 then UtilityHashLookup(myHashedFileName,1,2) else in.FIRST_NAME GenKey: If ISNULL(in.FIRST_NAME)=1 then GenKey+1 else UtilityHashLoo...

That was a smart solution that Kumar came up with. It can work for both server and px.

Welcome aboard Do you have the logic in your mind. If you do, you can put down the psuedocode here and someone can help you build a routine. You can get the Year and month both by using ICONV/OCONV functions. Look into help. Need more info on what do you mean by "convert the remote server time to lo...

Way to go Kumar. Keep up the good work. Dsxians are getting to learn a lot from you. Keep it coming buddy

on the key.
If it exists it will update, if not then it will insert.
It will try for the entire table.

You can update it if you know the primary key value. In such situations where a surrogate key is to be generated, the updates are done with natural keys and not its primary key, due to the same fact that pk is not known.

Remove all the file and just keep one file in that folder that starts with 'File'. Then do view data.
If that works, that means that the stage is able to find the files, but doesnt know which one to open.

We dont, but googledoes