DSXchange

ya...unix is always there ......just wanted to check there is a DS option too.

but how can i select 3 times from the time picker combo box?do u mean I have to schedule it 3 times?I don't have much experience in DS.If you could explain a little.

Is it possible to schedule a job multiple times every day?(Server edition).Like each day it should run on 7 AM , 1 PM and 6 PM.

Ok.A custom trigger is probably required then.Another thing is tthat if I am running a sequence with 3 jobs(running concurrently) and one them finishes with Warning and the rest finish OK;in that case what will be the status of the sequence?Will it be finished with Warnings?

I have 2 jobs in a sequence in seires,connected by OK trigger.Warn limit for the jobs is 0 . Now if the first job finishes with say 10 warnings,will the second job run?

sorry folks...after going through the whole thread..I find my question already answered!

I have a related query.....if I migrate a job where I have added an environment variable,will the environment variable also be migrated along with the job? Or I have to create that environment variable separately in the target project?

I have a related query.....if I migrate a job where I have added an environment variable,will the environment variable also be migrated along with the job? Or I have to create that environment variable separately in the target project?

I guess I will have to create an extra field in the reject link (apart from the ones coming from input link),say error_msg and have to decode <linkname>.REJECTCODE to get the specific error message like unique key violation.....is that correct?

oh ok,i see...what is OE stage?..i mean ,full form?

ok...so just keeping an transformer before load stage and using the reject constraint. Is it possible to capture the reject reson too (like duplicate,null value)?any inbuilt help for that?

In server version,is it possible to catch the records which are rejected in DB level(constraints)? Idea is to create a bad file/reject file.

Recently in a datastage best practices document,I read that while loading in oracle ,it is adviseable to use the UPSERT strategy(even if it is only inert mode) always . For the jobs where records are only to be inserted,we need to put a where condition in the update statement "where 1=2 " ...

Is it possible to use a job parameter in the user defined query in OCI stage ?

Is the datastage repository a file based system or rdbms based?Also,I keep hearing about universe.Is it a proprietary database which is shipped along with datstage?