DSXchange

That's a database question.

DataStage does not support BLOB data type.

Another possibility (which I have encountered in the past) is that the web server itself is overloaded. This is another thing that you should check.

A couple of nice features. To reduce I/O operations for large sorts, the Sort stage converts bounded length fields to variable length before the sort, and converts them back to bounded length after the sort. Sort optimization also improves run time during which implicit sorts are sometimes required,...

Yes and no. Auditing of security events is handled in audit log files (outside of XMETA). Date/time created/modified are recorded in XMETA, and reported via tools such as Information Governance Catalog or Metadata Workbench.

SoundexName is/was NOT a built-in function. In any version. A number of sites created similar routines. For example, I once created a Soundex algorithm for Pacific Island names (in which the rules around vowel handling, leading "NG", etc., are different than in US English). I called this S...

Read the Planning, Installation and Configuration Guide again. The DB2 users must be created before the installation is performed. It's best practice to pre-create the WAS admin user, the IIS admin user and the DataStage admin user too, though this is not always possible (for example where the syste...

There is no change in behaviour. Job logs are purged only if the job finished with a status of DSJS.RUNOK or DSJS.RUNWARN. If the job aborts, the log is not purged.

Actually it's sufficient that the sequences log a warning when any activity finishes with a status other than OK. That propagates the problem up to the master sequence (without the need to force jobs to abort) at which point logs can be inspected to detect what the actual problem is. But to resolve ...

... except DS_AUDIT, which now seems to be less complete than before.

First, you need to realise that "", " " and NULL are not the same thing, and that NULL (whatever that is) never occurs in text files. The NUL byte ('\0') may appear as a string terminator. So you need to be very sure what these "rogue" lines contain, and deal with them....

vmcburney wrote:Edit: renamed Hash file.

On a heavily loaded server, even the Ops Console can consume valuable resources.

And it's hashed files, dammit, not hash files!

Server jobs do run differently post version 7.5 than they did in version 7.5 and earlier, primarily because of the need to interact with the WebSphere Application Server through the Information Server Framework. This adds some overhead which results in, depending on your circumstances, as much as a ...

Run Success triggers from all activities to an "All" sequencer.
Run Otherwise triggers from all activities to an "Any" sequencer.
Create a Notification activity downstream of each.

Have DataStage generate the file name and pass it to a script as a command line argument.