DSXchange

It's quite possible - likely even - that the difference is not in DataStage at all - it might be in the target database, or in the way that LD_LIBRARY_PATH is set up, or all kinds of things. More detective work is required.

My bad Answered late at night. Craig is right, you need to work out where the license file IVVM.LIC is, and make sure that is visible to DataStage applications.

You can execute ANALYZE.FILE (from within a DataStage environment) in any project. You can use it from the Administrator client's Command window. You may need to use SETFILE to create a VOC pointer to a pathed hashed file.

EXACTNUMERIC counts digits. It does not count decimal placeholder or sign designator.

Au contraire, mon ami!

Every Build stage that you create in a parallel job is customization, and may (depending on your selection) create a new library. So the capacity to do so easily is built into the product.

Yes it's possible. The Designer carries the same title whether you run DataStage only, QualityStage only, or both. Licensing affects which stages you can use.

The problem is with your assumption that the FTP stage unzips anything. It does not. The FTP stage is intended to transfer a file a row at a time, and feed those rows into your job. Since that's not what you want, either unzip the file at source (perhaps using a "before transfer" command in the FTP ...

Read the manual about the Transformer stage function. You can specify the format in the function; if you do not it follows the ISO 8601 standard (YYYY-MM-DD) rather than the job default.

Have you imported the "table definition" of the stored procedure into your Repository?

The first does not require DELETE privilege, while the second does not require UPDATE privilege. Otherwise it depends on how the "delete first" is implemented. If it's for each row, then the result would be the same if entire rows were being passed. If the "delete first" truncates the target table, ...

DSP.Close is an internal DataStage function. If there's a COMMON mismatch either you've got your own routine(s) that have happened upon one of the names used for named COMMON area in DSP.Close or, more likely, there's a bug which you need to report to IBM through your support provider.

Be more modular. Create a separate job to clear each file. Each job sets "clear before writing" then sends 0 rows. Use job sequences to tie it all together with your downstream requirements.

EXACTNUMERIC is total significant digits, not just the ones to the right of the decimal place. That's why Craig originally reacted to "the 16th position". In your second, successful, example, the total significant digits is less than or equal to 15, the value of EXACTNUMERIC.

Since there is no version 7.2x I will assume you are using version 7.5x2.

This is an error in the DataStage client. The only solution is to re-install the client software.

Is there any more information in the error message, such as which query parameter lacks a descriptor?