DSXchange

Why not post a request on the Enhancements Wish List forum? Here or DeveloperNet or both.

Link Partitioner splits a single stream into up to 64 separate streams with identical metadata.
Link Collector gathers them back into one stream.
Each creates a process of its own, so you must enable inter-process row buffering.

Should be in the bin folder wherever you've installed the Engine, for example C:\Ascential\DataStage\Engine\bin, along with all the other server-side executables.

If you have NLS installed and enabled you set your default date format in the TIME locale category. If you do not have NLS installed, or if it is installed but not enabled, then the default date format is set at field LOC0020 in a file called msg.text in the Engine (or DSEngine) directory. Alternate...

Validating a job means doing everything the job does except processing rows. It even creates missing hashed files, if there is a Hashed File stage with an input link.

Without access to DataStage I can't say. It's not ALL in my head, you know!

1. Install on a different platform to prevent the warning from occurring.

2. Create a message handler to demote the warning to an informational message.

These are alternatives.

kumar_s wrote:Iam still thinking a way to capture the file size (alone) from dos prompt.

You have MKS Toolkit installed, so you have the test command. This can also be used in an if construct in a shell script using square brackets.

That's right, by default. That's why it's not x4. But you can override the Execution Mode, provided the data are partitioned on the pivot keys.

There are quite a few errors in this Chapter. For example it gives the Transformer stage function for null handling rather than the Modify stage function. There are also errors of omission, such as the fix_zero option for decimal numbers. Be very, very careful. Check anything you propose to do with ...

Welcome aboard. :D In the Manager client select the table definition then click on the Usage Analysis tool (it looks like a chemist's beaker). Provided you've been professional about metadata management - never changing table definitions in jobs after you've loaded them - this should show all the jo...

Welcome aboard. :D

The most usual reason for this error is that you lack write permission on the client machine, where the XML file needs to be generated as part of compiling a job sequence.

It's still an easy change with SQL, even though you need a pair of UPDATE statements per job. You could use inline prompting to create a stored procedure (paragraph, that is) to effect the change for one job, and another that looped through all jobs. PA * <<I2,Old Name>> UPDATE DSJOBS SET NAME = 'pr...

I too have been programming in this language since the early 1980's and have always used READSEQ in this fashion. It is not used as a function. One is using the "Boolean context" of READSEQ - the same context that drives the THEN/ELSE decision can also be used to drive the WHILE decision. It is perf...

Yes, but prefer to issue a warning (UtilityWarningToLog routine) and exit (Terminator activity) rather than to abort. Create a small job that selects COUNT(*) from source into a text file, then read this text file (Execute Command activity) then, depending on the result, either continue with regular...