DSXchange

You came to know it supports it how exactly? And why not answer my first question?

Rick001 wrote:OS in UNIX.

We know that. Which UNIX?

What operating system?

How would you do it if you took DataStage out of the picture? That's probably the same way you'd have to do it with DataStage.

lottokahe wrote:@Craig:
"For AIX, Visual Age C++ 6.0, XL C/C++ v7" (Install and Upgrade Guide)

Just wanted to check as PX is very picky and anything other than supported compilers do not seem to work with the product.

PACK is an acronym? Sheesh, learn something new every day...

RayLade wrote:Maybe this is a version 8 thing?

No.

select pinv.*,pdesc.description from product_description pdesc, product_inventory pinv where pdesc.pcode <=pinv.pcode -- this SQL is forming a cartesian product of the tables used. No, it's not a 'cartesian product' - but I'm sure it's doing exactly what you told it to do and giving you way too man...

That would cause a different error, specifically "Table or View does not exist". Your user/password is wrong for the instance you connected to, period. And DataStage doesn't care if you source from a View or a Table, it all works the same.

Search the forums for your message - it's been discussed here many (many) times.

Call your Support provider, especially if it's "really urgent".

Can we do exception handling in datastage? By this I mean can we catch any datastage error and write it into a file. Say for example if I am creating a file and datastage is not able to create the file due to some reason. In this case instead of datastage job failing I want to capture this error in...

In a word - no. A container is just a collection of stages. It's a 'people thing', using one doesn't do anything for performance.

You've posted this three times, please delete the other two. You won't be able to once someone replies to them. Problems with the Sequence job itself will cause it to abort regardless of the state of any child jobs. Post your error message(s) from the log - cut and paste, don't hand type them here.

Or you are missing the ".*.adm" files in either the DSEngine or Project directories, particularly the .developer.adm file.