DSXchange

See new thread on capturing output of "UniVerse" commands.

Welcome aboard DataStage does not use SQL internally, so the wildcard technique is different. DataStage uses a technique called pattern matching. The patterns against which you match can be specified as containing alphabetic, numeric or "any" character types. So your expression should look something...

Editing the DSX file is a valid approach. Make sure, however, that you export components' default properties (this is done on the Options tab of the Export dialog).

What kind (brand) of database server? What version?
I haven't encountered it either, but it sounds like a candidate for a list of "gotchas". See what else you can discover by asking "them" (the application owners/support staff) and post same here.

No job, whether server, parallel or mainframe, has the ability to restart itself.
Restart capability must be implemented in a job control routine of some kind (whether build from scratch, from a Batch or from a job sequence, or using an external scripting language).

You have two choices. One is to use a "BASIC Transformer" stage, in which you can re-use the same expressions that you used in server jobs. The other is to use a regular (parallel) Transformer stage. This uses a completely different expression language. There are no conversion tools (at least none o...

Welcome aboard! :D The best way to think of Version Control is as the "fifth DataStage client". Version Control actually uses a dedicated project on the DataStage server for storing versioned DataStage objects; they are not stored on the client machine where the Version Control client is installed. ...

The same can be done with SQL Server. Use a Sequential File stage (or even an FTP stage) to produce the data file, then (remotely?) trigger a BAT file to perform the BCP command on the Windows machine.

Each is as easy as the other. A Routine (probably a before-after subroutine) has the advantage of being portable. Not sure what you mean by neat formatting. I use the Enter key (sometimes twice) to end paragraphs in text. The code is isolated by selecting the code then clicking on the Code button. S...

It can be done, but not with DataStage GUI facilities. You need to create the routine separately from DataStage, then use the BASIC compiler with its -I option to prevent reverse engineering before cataloging it. From DataStage you refer to the routine as an external UniVerse routine. Then hide the ...

Imagine you were trying to do this in a database other than UniVerse. The answer is the same; you can not do it with a single command. It's easy to build a paragraph, however. Execute both commands - whether successfully or not - from the Administrator client, then select both from the command histo...

Everything you need to know is in the manual for the stage type (oraoci8.pdf or oraoci9.pdf).

This is one where server side tracing may aid diagnosis. Enable server side tracing (from Administrator or DS.TOOLS menu) then open Director. Switch to Schedule view. Then close Director and disable server side tracing. Inspect the trace file (DSR_TRACE...) to see how the server was being queried. C...

No, the address is actually the offset in the compiled code.

You can view this compiled code in an "assembler" format using
The associated source statement should be nearby in the output.

DSRMessage is the subroutine invoked by DataStage itself to log events in job logs. It is eventually called by DSLogInfo and related functions. The all-upper-case tokens such as DSTAGE_TRX_E_0011 are keys to a "resource file". All DataStage messages are tokenized in this way so that it is easily loc...