DSXchange

Param1 and Param2 have a different meaning depending on what rule you're choosing. For example, an UNCERT match requires one parameter (the value between 700 and 900 that indicates the level of tolerated uncertainty), which you give as Param1. Other match rules require two parameters.

Can you please post a picture of the License tab from your Administrator client? (Search forum for how to post a link to a picture).

Welcome aboard. :D

There's a check box in the Administrator client Permissions tab for "operator can see full logs". Did you check that?

Algorithm design:
Find current status. If "Finished OK" then do the remainder.
Find start of current run.
Find newest "job finished" message prior to that timestamp.
Get status from that event.

Ah, the ever-hasty grasshopper!

Yeah, right. No doubt "on individual laptops" means they're running Linux.

Maybe some quote characters around the nick in the Subject would be nice.

I read it wrong at first glance!

99 may well be a limit for concurrently connected client users. It is NOT a limit on the number of projects you may create, which is unlimited (disk space permitting) in version 7.5.1A Look carefully at the Licensing tab in the Administrator client. There are two frames. The one on the left is for t...

What version are you running? Current versions are licensed by CPU, and there's no such limit on the number of projects. Earlier versions were licensed by the number of projects, so you'd have to buy more licenses to go past 99. Indeed, I've been working with DataStage since before version 1.0, and ...

And here's me assuming it was a blackness grade in pencils...

Modular?!! Re-usable?!! Keep it a separate function; add a DEFFUN declaration to yours. But it's STILL two passes through the data. Three, if you have to build the list first that you pass as your routine's argument. I'd prefer to use an SQL that offers MEDIAN and RANK right there in the query. Inci...

Only you can do so for sure. If there were database tables involved I'd be suggesting to check for self-locking. But there aren't. With no knowledge of the two job designs it is difficult to suggest anything else, apart from enabling some of the reporting environment variables. Are you noticing more...

So, if we can have 79, is 2B a hex number. And, if so, is 79 a hex number?

In the Aggregator stage, find the Method property on the Stage tab and change it from Hash to Sort. Then, on the Input tab, go to the Partitioning tab and change the partitioning to Hash, choosing the grouping keys for aggregation in the same order. Still on the Partitioning tab, select the Perform ...

Welcome aboard.

The answer to your first question is "No", in general.

Throw lots of money at lots of consultants. I believe IBM is offering (or will offer) such a service, but will use lots of (outsourced?) developers to implement the same.