DSXchange

Do you have some examples of 'issues that were not captured' or what kind of warnings you'd want to 'suppress'?

Not positive but you can try changing the value of UVTEMP in the uvconfig file and then stop/regen/restart the engine.

You can't, so don't worry about it. There's a PX version of EReplace posted here which a search should turn up.

Enclosed in hash/pound signs. You can use them in generated sql as well.

As noted, your metadata in the stage only matches those 37 records. Or perhaps your Period in the Viewer is not set to 1. Or your Row Limit is too low. Or all three.

Same issue, an improper dsenv file. Can you post the entire contents of the file, wrapped in code tags, please?

You missed the fact that there are no files whatsoever in the Project that end in that job number. I suspect Ray will have him manually delete the records in those tables.

Metadata issues will cause the stage to 'drop' records. How many records does the actual UNIX file have? Check outside of DataStage.

Your 'transaction size' setting is only applicable to the inserts. Now, whether the deletes will commit automatically or wait for the first insert commit, I can't say. How exactly are you issuing this "pre SQL delete"?

Or the @INROWNUM / @OUTROWNUM system variables. Or sequence objects in your database. Or...

Have you restarted DataStage after this change?

Odd. What exact 8.x version?

Sounds like a bug to me that you'll probably need to report to your official support provider.

You have to type ". ./dsenv" from that directory for them to "show up".

DataStage can easily handle XML up to many megabytes in size, it's CLOBs that are not supported. Change it to a Varchar and CAST or use the dbms_lob package to substring it in your select.

And unmostly that chulett guy ....