DSXchange

Premium membership will, among other benefits, let you see the entire posts of the five premium posters. Premium membership is inexpensive - less than 30c per day. All revenue from premium membership is allocated to defraying hosting and bandwidth costs incurred by DSXchange. So, by taking premium ...

Warnings are not necessarily for bad things, they are also alerts for unusual things. In the ordinary course of events DataStage does not expect to process zero rows, so it alerts the operator when a query returns zero rows.

This is the underlying philosophy behind the "Warning" severity.

The structure of the repository is deliberately not published by the vendor, who reserves the right to change it at any time, and has done so in the past. Further, the repository makes use of capabilities such as tables having variant and nested structures, so it is a rather esoteric art to figure o...

Take a look at the job control code generated by compiling the job sequence. Managing the checkpoints is a single function call. It ought to take hardly any time at all. I suggest that there is something else at fault here.

The GUI (sequencer icon) will tell you.
Three lights on = "All".
One light on = "Any".

Welcome aboard. Presumably you use the command line interface ( dsjob ) from CA Unicenter to start your DataStage jobs. Use the -jobstatus option to have it report the job status when the job finishes, or later use the -jobinfo option to interrogate the job's status from the DataStage repository.

I don't believe that the Transfer stage still exists in version 8. But you could do the same thing with a Transformer stage.

Of course they are stored, but in a number of places. Job parameters have design-time default values, run-time default values (set in Director), indirect default values (for environment variable job parameters), and, of course, the values with which the job was last run. All of these things are stor...

Pivot stage goes from rows to columns (horizontal pivot), not columns to rows (vertical pivot). Search the forum for "vertical pivot" to learn various techniques.

It has been suggested (at IOD 2007) that vertical pivot will be possible in the Pivot stage in version 8.1 (later this year).

Rank - and any derivative of it - is a display function, not a calculated function.

DataStage only takes one pass through the data, unless you explicitly design it to take two. Without two passes you can not calculate percent, rank or any other value that depends on the total count or value.

How would you do it if DataStage were not involved? I see no parameter markers in your SQL - how do you provide values from DataStage to the table? The columns can be called anything within DataStage - just choose a different name for the second incarnation of the column. The columns in your job des...

Take a look at the setting of the UVTEMP value in your uvconfig file. This points to /tmp by default. Point it to some other location, then stop DataStage, regenerate and re-start DataStage.

I do not know what the sqloInit.log is - what stage types are you using?

's right. It's Phil's thread. Obviously he's firing at the vendor with all available ammunition.

StringToTimestamp() function in Transformer stage. Concatenate your strings as the first argument, and provide an appropriate timestamp format string - depending on what you've done with the strings (for example inserted delimiter characters.

Where you have an "All" Sequencer, and the job sequence stops before all that Sequencer's inputs have fired, then you get this message. It is more informative than anything else, but suggests that you may need to investigate what halted the sequence.