DSXchange

Yes, I second Craig's opinion that you will have to test everything (job execution, data etc) There have been changes to functions such as field() which we found to be "Fixed" in 8.5.3 which altered the functionality and was loading incorrect data in target and our jobs needed to be fixed....

Yes its not an supported operating system. However installation problem is most likely caused by Microsoft .net framework 1.1. Which is known for its problem with windows 7. Try installing .net framework 1.1 using slip stream manually and then try to install Data Stage using this link . Just in case...

and yes, don't forget to partition your data correctly.

I think its related to broken pipe, do you have any other warning or error messages or do you get any thing in the log when you reset the failed job?

I would be more worried about the execution of the program ZETL_PROVA_DEV_FTP as I do not see the stage waiting for even a second before initiating transfer of the file. Check SAP logs for execution of this program.

There can be many reasons for getting all records for update. But since you are seeing every record as update here are my wild guesses. 1. You are writing to oracle database with APT_ORACLE_PRESERVE_BLANKS flag set to false and while loading those blanks are ommited. 2. You are unsupported character...

Did you try WinRS?

Can you get the CPU usage during time of abort? Although there can be high CPU utilization there are few things which you may already know, are known to increase such incidents like &PH&, big log files etc.. But I have seen the number of occurrences go down without operator combination. But ...

Do you see any other error there? and as Mike asked, are you able to login to WAS console?

What is the error? Are you using same user to connect to database and is it the same database you are connecting from both environments?

How do you expect the file to be present in there. Did you write any logic to get that file created? Like running any ABAP Program?

make sure the entry in .odbc.ini is correct?

I prefer having multiple sequence levels for better maintenance after wards depending on number of jobs to be sequenced.

There are things you can do before even sending the record to DB2 Connector. You can restrict that record in your job itself. I think if you sort on key and start and take the last record. Pass it through the lookup to get start of the record already there in the data base and if new record has star...

did you verify the parameters being passed during runtime and during view data?