DSXchange

How about adding an additional layer. Call the CORBA interface, land your data in a staging file. And read that file from DataStage. If you can create a stand alone program to invoke CORBA which can be called from command line interface, then you can invoke it from within datastage.

...which was advised in the very first place. And if you do that, then even your DB2 stage will work. No need for a routine.

If its DB2UDB and the table is empty only then, you can do a Load from /dev/null . This also gets rid of any table locks on UDB's. Get the exact syntax from google by searching for "How to truncate a UDB table?" Only try this if its UDB. If its DB2, then all the tables in that particular table space...

What is your job design? Sometimes it helps by recreating the job. Try that.

Never done it, never saw it done. Get in touch with your support provider.

You need to roll your own custom code for that. Look at the code of DSJobReport and DSSendMail(). I am sure you can merge the functionality of both into a single routine.

Is that particular column nullable in the table?
Also look at the .bad file for oracle error message.

How exactly do you intend to merge the two technologies?In other words, what exactly is your question again ?

Then I will be seeing micro-organisms within the internal dates.
Why I said its the same thing is because both @Date and Date() return internal formats. Same is the case with @Time and Time().

A shared container is merely a reusable ground. As Craig already pointed out, no performance gain can be experienced with the use of one.

Can you use the the same username and password and access the table from your favourite sql tool?

Why do you have to do a lookup again? Can't you get the seq.nextval in your source itself?
Something like


Possible ???

In a server job There is only a delimiter to be specified in a server sequential file stage, which is, the field delimiter. There is no record delimiter. The record delimiter will be specified by either Unix Style or DOS Style line termination. There is no property called Record Delimiter in server ...

Half glass empty, half glass full.

Please delete your other post in the Site Forum.
As for your query, you can search on it. There are zillions of posts on it, some of which outline the entire step by step process. Make sure you use the id with which the jobs were locked in the first place.