DSXchange

There's no End corresponding to the Then in the ReadSeq statement within the scope of the for..next loop. The End seems to occur after the Next statement. But the compiler was expecting to find End when it encountered Next, so it complained about not expecting the Next. Formatting your code would ha...

DataStage processes are background processes and will therefore gobble whatever resources they can. Statistics gathering on the Tracing tab of the Job Run Options dialog can provide useful information about where the hot spots in an active stage are. The PerfMon question is really in the "how long i...

Version 8 of DataStage is quite some time away - not before April 2006 at the very earliest. It's only just gone into beta testing.

Good catch. I've edited the original code.

That is true. But you could schedule it for the 28th then use a routine to edit the AT queue entry appropriately.

It's only relevant for server jobs. Think about what it would actually mean for a parallel job!

You could always interpose a Head stage for testing.

Can you please provide details of how you do this in parallel jobs?

There's no other syntax. The File Set control file has a name that conventionally ends in ".fs". The individual data files reside on the disk resource specified for each processing node in the configuration file. Yes, I get up early - usually about 5:00 (too many years in the military!). 6:45 isn't ...

In the current version there's no magic formula, apart from "don't overload the system". In the next major version (aka Hawk) there come some estimating tools, whether they get down to this level of detail remains to be seen. If you're not paging heavily sure, why not bump the memory some more? The ...

You create a File Set by writing to a File Set stage.

Specify eight-way partitioning in a configuration file.

Run job.

Done.

Before you can call a stored procedure from DataStage you must first import the stored procedure definition (so that arguments may be checked).

Verify the syntax for CALL - sometimes curly braces are required.

That's why I specified "not been re-scheduled". If it has been you can simply read the AT queue.

It's not possible. That's the rule for Integer.

Changing the data type is your only solution. This may require negotiation with the owner of the target table. All Oracle "integers" are stored as NUMBER, so you can increase the size of the number data type.

Look at the code. It returns -1 if the job can not be attached - that is, if the job name can not be found. The routine works as documented. The problem is somewhere with your job name. Job names must not only be correctly spelled they must also be correctly cased.

Do you have any idea what these shared memory segments do? If not, how do you know that they're not doing something vital? For example, there is one which, if removed, will cause DataStage to halt. Every DataStage process has - needs - a shared memory segment (key 0xadebnnnn), plus there are a few o...