DSXchange

chandra.shekhar@tcs.com wrote:See the Maximizing concurrency section of this article.

What article would that be?

After all, apparently you would not be permitted to install it.

How come you can install your own code?

Download ETLstats to your own machine then pretend you wrote the code for your client. But do include source attribution in your code - that's only common courtesy.

... and make sure there's a space between the -x option and the pathname of the Data Set descriptor file.

All the important information is in the part you can see. But do renew - it helps keep DSXchange going.

If the number of invoices is never going to be too large it should be straightforward to create a routine and invoke it from a Routine activity in the controlling sequence. That same routine could invoke DSSendMail or you may prefer to keep the two tasks separate.

I'm running bi2bg successfully at my current site (finishing there today) so let's catch up at IOD. We've scripted it to run out of a third party scheduler, but the script itself is very straightforward. You'll notice we're running on Windows, so it's a BAT file, but there's hardly any logic to it. ...

I presume you mean Transformer stages. Transforms are not available in parallel jobs.

They don't.

You can, however, hire DataStage time on the Amazon cloud (search DSXchange for details).

(Actually there is a built-in - but undocumented - utility for archiving and restoring hashed files - it's the "UniVerse" uvbackup and uvrestore commands.) There is also a "UniVerse" bulk loader called loadfile, but you would need to save the log in loadfile format. There is a BA...

All the RT_* entries are necessary. With the exception of RT_LOG* they should not grow very large. Keep RT_LOG* small by autopurging at as short an interval as you can tolerate. As Paul noted indirectly, projects can be created anywhere on the file system, other than the root directory. So you could...

You don't even need user-defined SQL for this. Simply use DataStage to filter the rows needing deleting) and pass them to a straightforward DELETE in the target stage.

Other than what Arnd said, a shared container created in 8.1 should be able to be used without problems in 8.7 jobs.

If the shared container includes Enterprise stage types, you should consider updating these to Connectors.

There is probably a property you can set in the stage called something like "treat warnings as fatal". This would force the job to abort.

Did you follow the steps for setting up the ODB in exacting detail? It's absolutely vital that this be done correctly. During beta testing I needed three attempts to get it right. Once it is set up properly it's a great tool. I think they need to simplify its setup but, if you think about what it's ...