DSXchange

Parallel jobs can ONLY be run in Information Server. To run parallel jobs you must have DataStage Enterprise Edition licensed. To run server jobs you must have the server engine licensed.

Welcome aboard. Where is user dsadm defined (in operating system registry, in Active Directory, in custom internal registry in Information Server)?

Start by configuring connectivity to the remote instance using DB2 client software. Then establish a Data Connection object to record connection parameters you need for that. Use an associated Parameter Set if you like. Then, when using the Connector import wizard, specify that Data Connection. And,...

You don't necessarily need to set a pointer; the pathname of the hashed file will suffice, depending on the option chosen in the Hashed File stage. The error, by the way, is not in UniVerse, it's in your design - you have not properly specified the location of the hashed file. If you believe you nee...

As far as DataStage is concerned, MPP = cluster, which has a fixed number of machines. A grid has a dynamically variable number of machines, with available resources being managed by some form of grid management software.

It's not a difficult routine to write, provided that your script is in some standard form such as ANSI-compliant SQL.

The concierge program is to help you with a new migration tool which picks up other things like DSParams values, Information Server and product roles, scripts, and so on.

They (IBM) are possibly releasing this tool to general availability late in 1Q2011.

Ah. My Sys Admin always uses smit (or smitty, usually). Useful to know.

A "pin" is the junction between a link and a stage (the analogy is from the way that integrated circuit components plug in to a printed circuit board). Each link, therefore, has two pins. Input pin 0 is the first pin attached to the stage, input pin 1 the second, and so on. Ditto for outpu...

ExecCmd_Split returned an exit status of 255. You have "automatically handle failures" selected. The non-zero exit status from the Execute Command activity has caused the sequence to fail, returning the captured exit status. Investigate why the command has returned 255.

Welcome aboard.

So what's suddenly changed in your environment? Hint: "nothing" is clearly not the correct answer.

I have just learned of one customer having QualityStage issues after a do-it-yourself upgrade, in particular with the Match Designer test utility, but this customer happily admits that the problem could be between the keyboard and the chair. Will be reviewing their system some time this month.

The only thing that is possible with the Notification activity is a hard-coded body. To do anything else create a routine that ends up invoking DSSendMail().