DSXchange

There's no risk (if it's done right). Might be more interesting to establish "why" - both why your standards are as they are and why this developer does things that way. (My guess for the latter is that they've always done it that way.) The only gotcha I can think of is troubleshooting - o...

Lose the dollar sign. Use #ParamSet.Param1# rather than #ParamSet.$Param1# unless $Param1 exists as an environment variable parameter within the parameter set ParamSet.

You don't. Use dsrecords to determine whether the Data Set contains any records at all.

A request from our side. Please GET a premium membership. It is worth it to you (as any premium member will attest), it's not expensive (at less than US$0.30, or Rs12, per day), and the benefits are worth having. Premium membership is the model by which DSXchange is funded. Did you notice the lack o...

Lookup will succeed only if the two values are EXACTLY the same. Yours are not, as proved by them being sent to the reject link. Time for some detective work. If you post the values from both inputs, we can probably spot the problem (assuming it's not non-printing characters!). Another remote possib...

The full syntax of orchadmin command may be found here Records are dumped to stdout so you will need a redirection operator to catch the dumped records into a file. It might also be worth running orchadmin check first to verify the structural integrity of the Data Set, and possibly also dsrecords to...

My practice is always to use fully-qualified table/view names, with each component in the name being a parameter (typically from a Parameter Set). The value of using Parameter Set is that one may have a different values file (containing its own set of "default" values) for each environment...

In fact there's no such thing as "Parallel Edition" in version 9.1.

Check the user name used to connect to Oracle from your DataStage job. Maybe THIS user can't "see" the table or view.

I meant that you should show us the exact syntax of your orchadmin command. Also, can you list the Data Set using the Data Set Management tool in the Designer client?

vijayasarathi7 wrote:I have a job, to capitolizing 1st and last letters.

Why?

Why "without using Aggregator"?

This can be done simply using key change detection techniques and stage variables, as has been discussed many times on DSXchange.

Then it sounds like you need to base your changes on this - maybe a separate job with smaller arrays that is run at busy times (unless, of course, the array size can be a parameter - this will depend on which stage type you are using).

This can be done by using either CAPITALS transform or OConv(InLink.TheString,"MCT") in a "BASIC Transformer" stage. In a parallel Transformer stage you could loop through the words in the string and capitalize them individually using Upcase(lvTheWord[1,1]):lvTheWord[2,Len(lvTheW...

Is there a way to predict these spikes?