DSXchange

You need to surround the DSJobInvcationId with hashes(#).

A job before this job. That runs your sql and stores it in USER STATUS. Then the second job is invoked which passes the value of USER STATUS to a job parameter. Bind the two jobs using a sequence job. Alternately, you can also land your value to a flat file and in the sequence job, cat the result of...

chulett wrote:You said your three arguments in the stage were 'separated by spaces , as required by the shell script' and yet this seems to show you actually have commas there.

O yea, that too.

Read the error message. Its not able to find oos_env.sh and /callbase.out. Fully qualify these files within your original script.

Try to get rid of the warnings instead of demoting it. Search on the error message on the "How to". As for message handling, you can only do it from the director. No method, that I know of, can demote the warning message within a job, other than in a modify stage using NOWARN, but thats for modify s...

What is the ORA code that you are getting? Also tell us, what is the length and scale that you are using for this particular field.

Don't worry about the millisecond part. The database will add it. As for the file, specify the default timestamp in the target sequential file stage.

Change the default timestamp of your output stage to
%yyyy-%mm-%dd-hh.nn.ss.6

It will be skipped.

You should have given us the entire error message from the very begining. You main error is "This server does not support transactions". Take this error with your dba and see what he/she has to say.

But with ODBC stage, 32bit or 64bit should not matter as an external third party odbc driver is being used. Anywho, there is something else going on. Just for debugging, load to a flat file. See if the error persists. If it goes away then we have isolated the problem to be in the odbc stage. Then tr...

A stand alone program is a package that can be invoked by any program. Either manually, or via a scheduller. Like a shell script. If you can package your CORBA program as a stand alone entity then it can be called from within DataStage.

You can do it within the before/after job subroutine. Look into DSLogEvent(), DSLogFatal() or DSLogWarn() API calls.

And you would probably use WaitForFile activity to ensure that Corba has written the data to a file on your OS filesystem. You may still face issues if you have to send something back to corba(handshaking), in which case , the wait for file should trigger a job or routine that creates a file that c...

Is this the first job with the ODBC stage thats having a problem? What other stages are you using? SIGBUS usually happens when an attempt is made to access a memory address that is out of reach or may be invalid.
What datatypes are you using? What database is it? 32bit database or 64 bit?