DSXchange

I think this is just Pivot and not "Vertical" pivot.

Kryt0n,

Not sure what you are trying to say.
checks for output file present and more than zero bytes size. So that must work (unless you have first line is header turned on).

Do your have ant corporate scheduler?

Alternatively do from windows scheduler.

Can I suggest a simple
in the after-job shell

Some obvious points are left out for you to analyse and refine.

Try this.

Go to
Start -> Control Panel -> Scheduled Tasks

See whether you can add another task with the user you have mapped to.

To put it in simple terms, if you have multiple valued field stored in an column in an hash file seperated with value markers, you can normalise the structure so each value will appear in a row of its own. This method is extremely useful to prepare set of rows from one row with one (or more) additio...

It is no folder permission. It is scheduling permission.

Can you use 'AT' and schedule external to DataStage ?

Can you please explain what you expect to see.

It is the output speed and not row count.

Hope it is not a multi-instance job and you seeing a different instance whose log has been cleared.

Try calling this job from a sequencer and see the 'related log' from the sequencer log.

Log into dssh for the project and attempt to see RT_LOG for the job.

You can treat $ as a delimiter and rest as decimal.

Can you provide one sample record.

What happens in case of negative, zero or null values ?

Check the DataStage machine throughput when 1.) DataStage server down 2.) DataStage server running 3.) DataStage jobs running This will give you an idea. As mentioned before, try running individual jobs rather than 10 in a go. Are you using a transformer in the job? 10 jobs may themselves spawn 20 p...

Is SQLServer, DataStage Server and client all running on the same machine?

Provide some sample values for which the code fails.

What is your machine configuration and capacity ?

Try running the jobs one at a time. That will give you an idea of which one takes significant resouces.

When running the job, try to guage the process and resource consumption.

Btw, DS v8.x by itself consumes significant resource.

Is your source database partitioned ?

How many nodes are you running in ?

Check the performance if you run in less number of nodes.