DSXchange

Naaa....just using his quote

See if thishelps if you want to do in oracle.
If you want to do it in datastage you can A) write a c function B)write a Basic routine and do it in Basic transformer.

Einstein says "Your welcome"

Because you made that a key. Make that column key on which you are doing lookup so that it shows up in the "where" predicate.

Left outer join can be accomplished without the constrained. The key words in Ray's reply were "constrained to put only those records for which the lookup succeeded ".

Import meta data rather than defining it yourself.
Oracle and MYSQL are two different database. They will have data type mismatches. Thats where DataStage comes in and does data conformity. Use the rich functions of datastage to get that done.

bcarlson wrote:Thoughts anyone? Anyone? Bueler? Bueler?

Brad, you are one funny guy and I give you an A in sarcasm
Jokes apart, I think thats a great idea. As this is one of the major transitioins from Version x.x to Version 8.0, it would be nice to have all issues regarding the transition in one place.

For the Field function above, is everything taken from the first element of the dynamic array before the field marker? I am assuming that it is as it is a C array which is actually one contiguous string. It is one contigous string and the field sperator is the @FM as described by Ray. So Field(Exec...

What would hold a developer from invoking your routine that makes the job writable again? If developers will stop at the sign that this job is being used by someone, then do as Ray suggested, a big annotation that will tell anyone who opens it that this job is still under constructioin and not to ch...

I dont think there is a limit but you might be running out of space. Hence the limit is directly proportional to the disk space. But it is better to avoid having large number of jobs as it will, then, start taking longer in pulling up jobs and other objects from the repository.

What, they just get in and start modifying your jobs ? DS_AUDIT has all the information on what job was accessed and changed by whom. Catch them and get them nuked. This is insane and very unprofessional. Build another project for yourself, do your development there and ask your adminstrator to only...

When you say lock it, you mean to say to make it read only or keep it open on your desktop and come back and continue working?

They can be if you make the target as varchar.

Try this.

There are around 12 bulk loader jobs which run in parallel but with different tables as targets. Are you providing different TEMP_DIR's for all these jobs in the DB2 Load Stage? They are all trying to create the same set of command files. If their folder is the same then thats your problem right th...