DSXchange

Since you have no other way to identify the changes, you will have to do all the comparisons. No way around it. You might like to use the CRC32() function, so that there's only one comparison, but you have to apply it both to your new source data and to the corresponding row in the target, in both c...

No.

Yeah, but DataStage is still a 32-bit application on Linux platforms. That situation will doubtless change one day.

Go to the Administrator client and determine whether this map has been built and loaded. If not, build and load it by dragging it onto the right hand list. You will also need to restart DataStage services to get the newly-built map loaded into memory.

You have to substitute JOBNAME with the actual name of your job. Do an ls listing in the Scripts directory to see the names of the script files.

You need the pathname of the script unless (a) you are in the Scripts directory, and (b) "." is in your PATH. It can be a relative path so, for example, if you are in the Scripts directory, you could specify ./JOBNAME.stp -ipe.env JOBNAME.env -ipe.env /opt/qsadm/Ascential/QualityStage/Projects/DEV/i...

Thanks for that - might mark thread as Resolved.

Except on Itanium, ALL DataStage servers are 32-bit applications (currently, anyway) and therefore must find 32-bit libraries. DataStage can not use 64-bit libraries which, more and more, are the default for database client applications.

Be more precise about your Decimal data type - what precision and scale have you specified? What is the setting of the Decimal Output property in the Aggregator stage for the column(s) in question?

Search DSXchange, IBM, the web.

Nothing with in DataStage allows for indexed array processing of this kind.

You could fabricate a "dynamic array" as a delimited string, but there's still no convenient way to "traverse it multiple times".

Therefore, yes, you are going to need to create some code.

I believe the "boundary" is a length of 4096, to comply with the ODBC 3.5 (and earlier) standard.

What is the value of APT_STRING_PADCHAR environment variable?

The COBOL FD importer should handle it automatically. You probably end up with a tagged subrecord in the schema definition.

Emplace a Sort stage on the input of the Remove Duplicates stage. Even if the Sort stage specifies a sort mode of "don't sort, previously sorted" (because the keys are already correctly sorted) that should be sufficient to prevent the alert from being generated.