DSXchange

Assuming you have QualityStage licensed and have developed your QualityStage jobs, nothing.

You cannot fastload into an already populated table. it Multi loads data into the table. this is one of the reasons that a temporary table is created when we use the enterprise stage. What you say is true, but DataStage hides that from the developer by describing the operation as "Fast Load in Appe...

Teradata Enterprise Stage supports Fast Load in Append mode. Read the pertinent chapter in the Parallel Job Developer's Guide

Of course it can.

But I did just advise you not to.

Anything in &PH& directory would be a good start. Clear the &PH& directory in all projects. Any file in &SAVEDLISTS& directory that has a name beginning with "&&S." is also not required. Are there any temporary files (or temporary hashed files) that have been created ...

So? File size is not a debit against free space. However if, for example, the program were allocating large chunks of disk space (maybe doubling the size at each step) then this would be an issue. That said, you only have 418056KB free on /tmp, so maybe something else was eating /tmp space at the sa...

Please post the exact message.

Check also that your project directory's file system is not full, and that you have write permission to it.

Re-indexing is unlikely to help, as the log tables are not indexed.

When you renew your license the vendor will send you a new XML file.

OK, with QualityStage essentially embedded in DataStage, you can use the RTI Input and RTI Output stages (or whatever they are called in version 8 - something with WISD/WISL in the name, no doubt) and expose your job as a web service by this means. Take a browse around the SOA forum for some ideas, ...

Still awaiting response from kumar_s...

Is yours precisely the same error, with precisely the same number in the name of the file?

If not, are the numbers in your file names corresponding to process IDs or, perhaps, invocation IDs of multi-instance jobs?

It's an old SDK routine that provides a technique for comparing a field's value with its value in the preceding row. You can inspect the source code and documentation within the SDK routine itself to see how it works and how to use it. This routine pre-dates stage variables. These days we recommend ...

Can you be more precise about your question?

Do you want DataStage/QualityStage to be able to access web services, or to be able to BE web services?

No. YOU need to investigate where the fractional seconds are disappearing. Put a Peek stage on every link. Or compile in trace mode, which is effectively the same thing. Only run a few rows in the latter case. You must also be honest about anything you are doing with this field as it passes through ...

There's also Ray Perry as a possibility.

(Do you sense a conspiracRay afoot?)

Which Ray is that?