DSXchange

Uninstall the patch. Report the problem back to IBM.

We've had various conversations here on the topic and it really depends on what you mean by 'anonymise', probably 'masking' as Ray notes. For example, one such conversation is here.

It means the first 7 characters from the output of the DSJobStartTimestamp macro, which is a constant that is the date/time that the job started.

"dsjob -jobinfo" is (basically) the command. In a loop, call it for each of the jobs that you pulled from the project using "-ljobs". The output of the jobinfo call will include the last run date and status, from what I recall.

Two ODBC links, one for the delete and one for the inserts. Make sure only the first row goes to the delete link before it goes to the insert link.

Not that I'm aware of, they (like all scheduled items) are only shown to the user that actually scheduled them.

Does that work from the command line, i.e. outside of DataStage?

horserider wrote:$APT_DECIMAL_INTERM_ROUND_MODE = Round toward negative infinity

That doesn't look like any kind of valid APT value... perhaps "round_neg_inf"???

Yes , I think restartability will work only if a sequence aborts not in other cases Correct. A Sequence job must have checkpoints enabled and have aborted to be in an Aborted/Restartable status which then means it can pick up from where it left off when you run it next. This regardless of it being ...

Could you take another shot at explaining what it is you are trying to do, please? I'm a little lost. Don't worry anything about "routines" or even any job / DataStage specific language, just lay out your requirements for us in words, much like they must have been given to you.

... which means there are no 'extra' pipes in your file and thus my suggestion should have worked just fine as well.

First you'll need some flavor of command line zip, which is not something that comes with Windows. MKS Toolkit, perhaps, but not Windows.

Those "dbf" files are the database.

There's more to it than that, your compay would have to be paying maintenance to be entitled to support. Check with whomever would know about that in your organization.

I'd still get support involved. The last 7.5.x version was 7.5.3, perhaps somewhere in those releases your issue is addressed.