DSXchange

Only if you can report a problem.

Unless you can use ODBC you're screwed. It's the only way you can access worksheets in an Excel workbook. And even then they're system tables. Get someone to create the DSN for you.

Why a routine? It's easier with a command. Convert the ";" characters to line terminator characters, then append to the existing file. In a command you can use tr to effect the conversion and echo (with the >> redirection operator) to write to the file. In a routine you can use Ereplace() to effect ...

You lost control. Every named pipe must have a reading process consuming whatever the writing process is putting into the pipe. A broken pipe occurs whenever either of these processes stops. You need to send coordination messages so that the reading process can shut down gracefully.

Take a look at the demonstration routine DSSendMailTesterAttachment. Try it with your values. If it works, diagnose the differences. If it doesn't work, read the error messages (double click the Result cell in the test grid) carefully. Carefully.

My car won't start. Tell me what's wrong. We cannot diagnose problems reported as "there is an error". We need to know the precise error message. Copy/paste it from the log detail view - do not summarize, do not paraphrase. Why are you using the ODBC stage for your import? Why not use the Oracle plu...

Only via a scripted approach, unless you have an OCI stage that is documented as working with Oracle 9i - this will connect successfully to Oracle 10g.

Otherwise upgrade to version 7.5.

Should not INVENTORY_TIMESTAMP be qualified with the input link name? Try it a piece at a time. Does TimestampToDate() work? Then does applying WeekdayFromDate() work applied to that result? Only then apply the Field() function. Put the results into stage variables; put them on separate output colum...

Try the job log for the job sequence that contains the Execute Command activity - there should be an entry there showing the command that was sent.

I am failing to see six 05-level items to receive the flattened OCCURS item ABC-CLIENT-INFORMATION in your target record. 05 SPLTC-CLIENT-INFORMATION-01. 10 SPLTC-CLIENT-INFORMATION-01-CLIENT-TYPE PIC X. 10 SPLTC-CLIENT-INFORMATION-01-CLIENT-ROLE PIC X(2). etc. 05 SPLTC-CLIENT-INFORMATION-02. 10 SPL...

What kumar_s has in mind, I believe, is not a before/after subroutine (because Call, in the SQL sense, does not work there unless you wrap it in BCI function calls), but probably the Open/Close commands in the OCI stage.

Every stage in a parallel job works only with the virtual Data Sets associated with its links*. What's on the other end of that link is totally irrelevant, provided that the rows match the record schema. Look at the generated osh and the score to see this happening. * (With the single exception, nat...

... only if the total number of rows is a whole multiple of the number of partitions.

You may be surprised to hear that you specify port numbers through APT... environment variables. If you did not know that, chances are that you are not using non-default port numbers. DataStage is probably still trying to use rsh to start the section leader processes on the other nodes. Check the st...

Shouldn't it (the second -ipe.env argument) be followed by a pathname? Could this be why your report file isn't getting written, because it doesn't understand the project environment? (Please note that I have no experience running QS jobs from the command line, so if I'm on the wrong track, feel fre...