DSXchange

HAVING COUNT(*) = 1 gives you the 90 records and HAVING COUNT(*) > 1 gives you the other 10. Isn't that what you wanted? You can do this within DataStage, effectively emulating the HAVING clause. Use a "fork join" with an Aggregator stage to get the count for each group, then run one copy of these r...

Probably not. An eight-way join is probably implemented as seven nested pairwise joins, so that at best you could not get any result row until the seventh was under way. This is possibly using sorting (to make efficient use of B-tree indexes) which would mean that the result set is not available unt...

If you are looking up against the target make sure you insert a sequential file stage (write all records to a sequential file so that whole process of lookup and update breaks into two seperate processes) before you update the target. This is to avoid deadlocks. "a copy of it" - for example into a ...

You can prevent the sub-sequence from aborting by explicitly handling failure of its activities. You can set the compile options automatically to log a warning if an activity fails to finish successfully. You can create a routine that writes an informational or warning entry into the controller's lo...

Umm... a script using dsjob -ljobs to get the jobs and dscc to compile them? That would also, of course, be slow.

When DataStage decides an event as info or warning, any clue? From 7.5.2 (maybe even from 7.5.1) any "unusual" event - one that would not be expected to occur every run - will be posted as an alert (that is, with "warning" severity). This should have been the case in earlier versions, but was not s...

Most of the information changed by the Administrator client is stored in the DSParams file. Tighten the permissions on that file.

My friend, that answer is only simple in fewer than four dimensions!

The dsrecords executable, properly executed, returns the number of records in the Data Set followed by the word "records". dsrecords MyProject/Controls/Engagements.ds 277381 records You can use a -n option to suppress display of the word "records". dsrecords -n MyProject/Controls/Engagements.ds 2773...

All in one column is tough. For a single domain such as US you could use a USPREP rule set. Not sure how you go about pre-parsing for MNS. Is there any pattern at all to the data, maybe that you could pre-parse with DataStage? Could you, perhaps, try running your data through the COUNTRY rule set, t...

That would depend on what kind of database you elected to use for IADB. If you made it another DB2 instance alongside XMETA (the common repository), then it would look very much like the entries for XMETA.

DateFromDaysSince() in Transformer stage or date_from_days_since() in Modify stage.

abhay10 wrote:COUNT DOESNT WORK IN DATASTAGE...

Yes it does, when it's done right.

By default the Row Generator stage operates in sequential mode. You would have to set it to execute in parallel mode for these values to make any sense. PART is the number of the partition on which a particular process is executing (starting from zero), while PARTCOUNT is the number of partitions pr...

Did you move the environment variable definitions to the new project? They are not automatically moved by the export/import process - though the job parameters that refer to them are. You need to copy the relevant lines from the DSParams file in the old project and paste them into the DSParams file ...