DSXchange

First check your install log to see whether the installation was successful or not. You might also look in the History section of Version.xml (for Information Server) to see what's been installed and whether successful. One possibility is that you have not yet installed the engine tier.

The table name becomes the FROM clause and the column names become the SELECT clause. The generated SQL is probably reported in the job log.

Backslash on UNIX escapes the next character. So \bis_data\msg\mfr\offshore\log\ becomes "bis_datamsgmfroffshorelog" - you end up with a file of this name in your current working directory. NT-based Windows doesn't care most of the time - you can use forward slashes or backslashes in pathn...

I cannot discern any generalizable logic that would produce the desired output. Can you please provide a written rule (or set of rules)? In particular I don't understand how the final two rows in your example, especially the penultimate one, are obtained.

chulett wrote:So... this is how you take a break, eh?

You orta see how he navigates his boat!!!

Looks like the job is being run in Reset mode, not in Normal mode. Status code 21 means "has been reset". Check in the Director's status view.

I'm afraid this is just "how it works" - the designed-in defaults are in the compiled job too. This is where values files come in handy - you can choose the appropriate values file (for example the one for dev or the one for test) at run time.

The sequential file is not on your conductor node, the problem is in establishing communication between the conductor node and the node on which the sequential file resides.

The actual delimiter in the file is irrelevant, provided it matches the metadata used in the record schema.

The only limit you might strike is if the operating system has a limit on the number of bytes in a line in a file. There is no limit within DataStage per se. Check with your UNIX administrator.

What happens when you invoke on-line help from within the stage?

Please publish the user variable's derivation expression. This should assign the return value from the function to the user variable. There is no scope for using routines in a UV stage, so I'm not clear what you're doing here. In server jobs transform function routines may only be called from a Tran...

Just login to the database and drop the index!

What happens when you invoke on-line help from within the stage?

How about a DROP INDEX statement (perhaps embedded in a stored procedure) executed from the "Before SQL" or "Open Command"?