DSXchange

The job log is a database table in the Repository. It is viewed using the Director client. New rows (log events) are added to the table. The table may be purged (of old events) automatically or manually.

Moderator: please move to QualityStage forum

Accumulate cumulative total in the Transformer stage (using stage variables) downstream of the Aggregator stage.

Did you check while the job was starting, or at some other time?

Timeouts can be caused by lots of other things, like failure to connect to a database.

The original purpose for the Folder stage was to be able to grab a number of (small) XML documents out of a directory. Both this original specification and the size of XML documents seems to have gotten well out of hand. Try an alternative approach using a job sequence loop and a sequential file sta...

Blame Microsoft.

If you are using MS Access, check to see whether there is a leftover "ldb" file corresponding with the "mdb" file - if there is, and no-one is using AuditStage, delete the "ldb" (lock) file.

Decimals have decimal placeholders. End of story. If you want an integer, specify an integer data type.

Search DSXchange for this error code/message. Many others have encountered it in the past.

If you still have questions after your search, please post them here.

You might also consider disabusing yourself of the notion that a DataStage server can deliver an unlimited amount of resources.

keshav0307 wrote:sorting of the data will take most of the time. So if the partition and join key are same for all files then there should be major difference in total time.

I think you left out "not".

The total time should not be an issue using cascaded Join stages, because pipeline parallelism keeps the data flowing. Join stages are fairly good at throughput, because they rely on the fact that both left and right inputs are identically partitioned and sorted so, for example, need only one row at...

If that's the case (which I can't verify at the moment), then you have to push back on the requirement. It's a silly requirement anyway - what are "they" trying to achieve? Late binding can be accomplished in other, more rigorous, ways.

No. Like with other languages, routines lack a "main" module and therefore there is no command line interface, either from TCL or from the operating system. You could construct a "main", or test bed, module, the same as the Test facility does on the fly, but there is no DataStage documentation on ho...

Why not just create a job parameter by adding the LD_LIBRARY_PATH environment variable as a job parameter?

Have you properly compiled and linked the routine? Have you properly created a parallel routine definition in your DataStage repository?

But it could be. The job sequence itself could have a parent sequence. However, encrypted parameters are still an issue - can you use $ENV to pick these up?

What about trying your IS Admin user ID (probably isadmin)?