DSXchange

Almost certainly. The DataStage server is the client for the database. It is the DataStage server that must establish the ODBC connection, and therefore you must set up your DSNs on the server. This involves two files on UNIX machines: .odbc.ini in the DataStage engine directory (usually DSEngine), ...

Ask the DBA why the SP is taking longer to respond than it formerly did. There may be a solution at that end.

Ask the UNIX sys admin whether the overall load has increased since when it was working.

Welcome aboard. :D

You should also be able to do it in a DataStage server job with an XML Input stage, a Transformer stage (if needed) and a Sequential File stage.

81016 decodes as "The (TCP) connection was refused or the dsrpcd daemon is not running". Check the server to see whether the dsrpcd daemon is, in fact running. If it is, check that your firewall is open to port number 31538, which is the port number on which dsrpcd listens (unless you've changed it).

You design so that there is a link running into the BAPI stage. When you open the BAPI stage, there will be an Inputs tab on which you can enter the properties relevant to this link.

This is because Data Direct do not provide an ODBC driver, based on UNIX, for connection to MS Access.

Database rejects will NOT go down the reject link of a Transformer stage. The rejects link (which is NOT the same thing as the Otherwise/Log link) handles input rows that cause an exception in the stage, for example an attempt to divide by zero or to take the square root of a negative number. Databa...

Import error at record 0 is almost always an incorrect setting of "First Line Is Column Names" property. This is not supported for fixed width format files in DataStage. However, if your file does have column headings on the first line, then it's unlikely that this row will match the record schema, ...

You should be able to report these directly using Analyis Server.

Unsafe. Job status values can be negative if internal errors occur.

What's happening in between reading and writing? Parallel processing may assist if some heavy duty transformation is occurring. You can allocate multiple readers to the file - particularly effective if the file has fixed width records - and achieve parallelism in reading. Unfortunately the operating...

Do you happen to have an ODBC driver for Excel that runs on UNIX? That would be the first requirement. None such ships with DataStage.

What does it do? Do you want to call it row by row, or only once per run? Can you invoke it from an operating system shell (or shell script) that invokes BTEQ? If so, why not encapsulate it that way and invoke the shell script from DataStage?

Each row in a Data Set (or File Set) carries an additional four columns of management information totalling 80 bits; the partition number, the partition count, the ordinal number of the record within the partition and the record ID. The data in a Data Set are stored in one or more files on each node...

The Oconv() and Iconv() functions used in that routine might make life tricky, however.

You could, I guess, use the ICI functions ic_iconv() and ic_oconv(). You will find these documented in the Intercall Reference Guide on the IBM UniVerse web site.