DSXchange

There's no debugger for routines, only for the jobs themselves. Best way I've found is to build the routine one logical 'segment' at a time and pass out the intermediate results as the Answer. Keep testing the routine and make sure each bit of logic works as desired before adding another. Lather, ri...

We are using transaction size of 5000 but thats for commit rt? Yes, but with a great big CAVEAT. Make sure you are not using the 'Transaction Size' box on the General tab on the Input of the OCI stage, that's just there for 'backwards compatability' and to confuse people. It is ignored. Check the v...

And?

Thanks!

ak77 wrote:Use the meta-data definition and just follow it through out unless if you are doing any comparison or date manipulation

And even then, most of the time. Dates in that ISO format are directly comparable without conversion to internal format.

Sounds like familiar advice.

Interesting find. By the way - 'complete PCL'?

Which is exactly what I meant when mentioning that the 'outer' side was held in the hashed file. So, as noted, swap it around to switch from one to the other.

Another option is to leverage your Enterprise Scheduler... if you have one. For example, we use Control-M to run jobs or series of jobs under our custom job control. Besides the boundries we've defined within our job control, we also have a fall back - Control-M. It is simple for it to monitor the r...

No. A little tip, however. Something like DSJobStartDate which doesn't change over the course of the job only needs to be 'derived' once - not over and over for each row. So what I do is still use it in a Stage Variable but don't put the call in the Derivation, put the call in the Initial Value fiel...

Hmmm... works fine for me. You could always try hovering over the link, then take the Topic number and plug it straight into the address bar yourself. See if that works more better.

No shouting please.

Do you mean a left or a right outer join? As noted, with a hashed file holding the 'outer' side. Any hashed lookup miss will return nulls for all looked up columns. Turn it into an inner join by using a contraint to filter out the rows where the join returns nulls.

Are you using an OCI stage? Have you read the .pdf document that comes with the plug-in on how it handles dates? There's no need for User Defined SQL just to do this. You should be declaring the target field as a Date or Timestamp datatype. You should be using the 'conv' brothers to get the date int...

For goodness' sake!

That should be because you'be enable to option to 'automatically handle things that fail' or some such. A routine that returns a non-zero answer is considered to have failed in that regard. Either turn that option off or I believe it will only auto-check if you don't have a failure trigger - add one...

See if this post helps. There were several more - you need to search on UserStatus (one word) rather than two.