DSXchange

This error is being generated by the driver. You should contact Data Direct (the supplier of the driver).

The second person personal pronoun in English is spelled "you". We have a participant whose name is U (which is a fairly common Burmese name). The present tense plural form of the verb "to be" is spelled "are". Here in DSXchange we expect professional standards of English, primarily to assist those...

There is no certification presently available for Server Edition.

Nor is there any planned, last we heard, though never say never.

Not sure what you're doing. The mkproj utility is, as far as I'm aware, used for creating a project. Apparently (from your error message) it also gets involved when you deploy job designs, rule sets or match specifications. A lot of the times when there's "unable to..." errors, it's worth checking p...

The big hurdle is the installation and different security implementation. Existing DataStage jobs should work fine (assuming 8.0.1 with all fix packs applied). To protect yourself, take two exports and an operating system backup (verified) before beginning the upgrade. Read through the installation/...

There's no limit in DataStage. There IS a limit in DB2.

XMETA - shared metadata for ALL Information Server products (including IA and BG). IADB - as the name suggests, Information Analyzer (analysis) database. It is functionally independent of XMETA. Metadata Server is actually the WebSphere Application Server delivering services such as Metadata Deliver...

Given that the messages are being generated by the DSSetParam() function itself I think you're right that there's a bug, so you need to involve your support provider to ascertain whether it's a known bug and, if so, whether there's a quick fix available.

Are the rows in the target table identified with "last updated" or similar? In any case, you are up for comparing new (source) with old (target) to determine whether anything's changed - essentially a Slowly Changing Dimension scenario.

Welcome aboard. Each of the 81xxx error codes is related to the RPC mechanism. 81002 is the rather generic "No connection." This may mean that your connection has become broken, or was never established in the first place. There's not a whole lot more that 81002 can reveal. What are you trying to do...

Obvious question: what changed between yesterday and today? (Note: "nothing" is not the correct answer.)

"On the same box" as the DataStage server ? Because this is what you need. User name and password can be left blank, or can be your Windows user name and password. Note that worksheets are presented as "system tables" so, when importing table definitions, you need to check the "include system tables...

Source file --> Transformer --> XML output --> Target file

might be a better design.

Source file --> Transformer --> XML output --> Target file

might be a better design.