DSXchange

You still have to call it Key in DataStage - that's what gets its value to replace the parameter marker in the WHERE clause.

chulett wrote:ps. PITA is an acronym, it's short for Pain In The Ass.

All these years I thought pita was a kind of flat bread!

"Roll your own" transpose functionality as a Build stage.

This is non-trivial. You need to change the device width in the same dssh shell as the one in which you execute the query. Therefore your query needs to contain \xFE characters (in lieu of line feeds between commands). Ignoring that for the moment, if your job names and category names are short enou...

Log warnings, so that the problem is propagated upwards to the master controlling sequence. Deal with warnings appropriately there.

How do you expect to manipulate character sets if the tool for doing so is disabled?

The answer is no.

You can try using NVarChar as a data type but no guarantees are made. It may or may not work, when NLS is disabled.

For starters, stop thinking like a server developer.

You will have to create your own function. Test each character and, if its value falls between 48 and 57 inclusive append that character to the initially empty result variable.

Any of the C functions that can execute a system call.

Take an Economics 101 class - particular where they talk about supply and demand. You must monitor your jobs under normal (baseline) conditions and perhaps running in isolation under full data load then, from these measures, calculate the maximum demand you can place on the system, and schedule acco...

"do not work" does not work in DSXchange. Post the actual error message.

So you're actually after something like 00001010 for the result rather than 26? In server this would be easy, either via the DTB (decimal to binary) command or using Oconv() with an "MB" conversion. I think there's no convenient expression in the parallel environment; you could concatenate eight bin...

U did not ask the question. Maybe it will help ketanshah123.

Please mark the thread as Resolved.

The solution appears to have been understanding how to perform grouping in conjunction with the COUNT set function in SQL - that is,

It is only available as a services offering from IBM.

Ask your support provider if you are wishing to buy their service to convert from server to parallel jobs.

How rigorous has your metadata management been?

Get a time machine, redo from start and document as you go.

There is never time to retrofit documentation, in spite of myriad protestations of the "oh, we'll do it later" kind.