DSXchange

Clearly it's not rare. Floating point exceptions ought not to occur with hashed files, though it is possible with corrupted hashed files (where the modulus calculation performs an improper division). Have you checked the structural integrity of the hashed file(s) that your job accesses? Otherwise, w...

Yes, have fewer, smaller XML files. These stages were intended to process short messages when exposed as a web service - they are not intended to perform "grunt work". Investigate DataStage TX as an alternative.

There is no such thing as NULL in a text file - there is only text.

You use the Null Field Value property to specify how you want NULL to be represented when writing to the file. This can be any string you like in a delimited file, but must be of the correct width in a fixed-width format file.

Sometimes - no promises - clicking Cancel then saying "No" to "OK to exit install?" issues a "wake up call" to the installation process and allows it to keep going.

You do not set $PROJDEF in the Administrator. In the Administrator you set an explicit default value that is used to replace $PROJDEF if that is found as the default value for a job parameter.

That's just not good enough, is it?
What do you do when you have to use one "for real"?

ProfileStage does not use Microsoft Access internally as far as I am aware. Officially ProfileStage supports only Oracle, DB2/UDB or Microsoft SQL Server for the ProfileStage database (PSDB). The problem is not with using Oracle as the PSDB, it's with the install utility that creates the PSDB. There...

Using a User Variables activity upstream of these other activities is an erudite manner in which to expose the values to those other activities in a consistent and easily-maintained way.

Unless you have set an explicit default value for the environment variable using the Administrator client, $PROJDEF can not be properly decoded. This might lead to the error that you have reported.

Decimal data types are deliberately preceded and trailled with zeroes so that you can verify visually that precision and scale are set correctly.

In that case also check your locale setting, since comma may be the legitimate decimal placeholder in your locale (for example much of Europe) but you haven't told the computer (DB2) that this is the case.

He means APT_DISABLE_COMBINATION of course.

This will allow you to narrow down the problem to the specific operator in which it is occurring, rather than be bewildered by operators combining to execute in the same process.

I have severe doubts about your claim. @INROWNUM is always assigned 1 for the first row input.

Of course, due to output constraints this row may not be output, but what I say is, and remains, true.

Perhaps you want @OUTROWNUM ?

If you really want to be pedantic, it's probably the DataStage resource service (which has the memory key daec7511 for version 7.5.1.1). in this shared memory segment are lock tables among other things; you have reserved space for them (using uvconfig) but it is not consumed until required. Neverthe...