DSXchange

Too corny.

There must have been an earthquake while I was typing - moved the keyboard.

Is the cron daemon running?

If that's not possible include a Nested Condition activity within the loop to test whether $Counter > ""

I'm currenly successfully using a twelve character password over Citrix (DataStage 7.5.1).

That's a good point. Yes, the "library path" is the pathname of the library object itself, in which the function is exposed. But it's an unfortunate choice of terminology because, as we both did, it can be so readily confused with the name of the environment variable that specifies the shared librar...

What partitioning algorithm is being used on the reference link? What stage type supplies records to the reference link?

It might be worth re-installing the DB2 UDB API stage in this project.

Reject link with maximum rows = 1.

Export/import is the only way. Any other "easy" way will involve you having to make repairs which will take even longer. You can use the format.conv command to export and import, but this is messier and slower than the DataStage command. Have you looked at other ways of recovering disk space, such a...

You can't stop it without terminating the process (usually a database process) that is generating the errors. And note too that these are buffered, so a few thousand will still arrive after that.

DataStage does not have a schedule. It uses AT on Windows. So the only way to "query the DataStage schedule" is to use the AT command.

The way to start a "no hangup" background process is to use nohup in combination with the terminating ampersand.

You can still use redirection operators, for example to capture stdout/stderr into a log file.

Is the cron daemon running?

Please purchase premium membership, then my reply will be in "visible format" without me having to do anything at all! Premium membership is one of the ways that the hosting and bandwidth costs incurred by DSXchange are defrayed. I do not intend to prejudice that funding by establishing a precedent ...

Yes. All you have to do is to record where you left off, and add that to a key generated from 0 or 1 in the next run.

1. U has not logged in for some time, and probably doesn't know.

2. With operator combination enabled you can't know either. Disable operator combination to find out which stage is throwing the error.