DSXchange

It is a generic feature of all wire protocol drivers that they do not require client software.

Of course dsjob will authenticate each time you invoke it, which is (I daresay) what your script is doing. I'm not sure that using the API would be that much faster; authentication is a tiny part of what you're doing. As to your standards, are you able to determine the reason (if any) behind that de...

Chances are that the other 30% are null, and/or that your analysis settings have limited the number of rows analyzed. Likewise your display options may limit display of results to 1000 rows in frequency reports. A quick way would be to sort by frequency - if you see values that weren't in the report...

You need commas in the format specification for the Oconv() function, and then you need to remove the default delimiters. That is, you probably should use something like Oconv(Date(), "DYMD[4,2,2]" : @VM : "MCN") : "_" : Oconv(Time(), "MT" : @VM : "MCN&qu...

If you clear the entries for a particular invocation from the RT_STATUSnnn table, then the log entries for that invocation will also cease to be visible, and will be removed at the next auto-purge (or, perhaps, sooner, depending on how the logging agent is operating).

That's 250 jobs per minute which, given the number of internal tables that need to be opened and interrogated, strikes me as reasonable. If you don't want to code it in C++ you could always create a routine in DataStage BASIC, which uses the same API. Depending on your skill set this may be a more e...

The easiest way is to ask whomever designed the hierarchy of sequences for a copy of their documentation.

Otherwise you can traverse the design information (to get the dependencies at design time) or the job logs (to get the dependencies for a particular run).

Does the Shared Container have its own parameters? Are you mapping to these from the job?

The elapsed time is the simple difference between start time and end time. Look at the timestamps on your job - they're six months apart!

Try not redirecting errors, to determine whether any errors are generated during execution of the dsjob command.

My favourite is the "Related Log" capability in Director client (Log View). One can traverse the logs from sequence to sub-sequence to job and back again without needing to switch back to status view and figure out which folder the other job is in. Saves a LOT of time when troubleshooting.

Give a man a fish...

I've always had success by specifying that the four tables are in a different database than that in which the target table exists.

Convert the inbound string to a time using StringToTime() with an appropriate format specification (such as "%hh.%nn.%ss").

Wrap that result in a TimeToString() function with a format string that specifies your desired output format.

We were pondering this question at the end of a training class I've just given. What do YOU think is the coolest feature of DataStage?

(Please indicate also the version that you are using.)

Concatenate the first four fields then pivot.