DSXchange

You need to purchase a 3rd party product that supplies ODBC connectivity to Windows from UNIX. DirectConnect (or whatever they are called now) is one such supplier.

Could it be fixed length fields? Sometimes loader files use fixed lengths so that they can more easily stream data.

The background processes get started when you start the server. What messages do you get while you start DataStage? Also, have you checked the other posts in this forum regarding reasons why the rpcd won't start (hint - open connections)

I've done this sort of thing before with UNIX db2 connectivity without any problems. The nice thing about DB2 sessions is that they are persistent, so you only need to issue your connect once per session. I'm not sure how you can issue 'db2cmd' before the connect, though. What is the output of 'Resu...

Katz, I've often implemented a small loop instead of the non-interruptable DSWaitForJob() call. It will issue a call to DSGetJobInfo() to get the status, and if it is still running it will wait a couple of seconds and then try again. That way I can issue a call to DSLogFatal() if I end up waiting to...

The message would seem to indicate you had a job called 'Category_Name' or did you replace that text?

Let me understand. You have EXACTNUMERIC set to 38 in your uvconfig, the database table definition for a column is (30,6), you define the column as (30,6) in your database read stage (which stage, which database?) and when you output this column to a sequential file keeping the same (30,6) definitio...

I know this is a silly question - but did you read my post? It does answer your question.

If you mean a EE Configuration file, then there is no problem at all to have the files shared across projects.

Ensure your commit size is 1

Remove the Delete from the 2nd link. Doesn't that satisfy your logic?

Those numbers are internal format for date and time; but the contents of that file (it is a sequential file) might contain the job name or number which you can lookup in the DS_JOBS table.

Link 1 has your before-sql "delete" in the DB2 stage, Link 2 doesn't. That is why you need to separate your stages as well.

I suggest using 2 links and 2 distinct stages for exactly that reason.

I should have read the original in more detail. I hate how the modify stage only allows one action to be performed per column....