Sorry about the re-post, but I forgot to turn on the notifications the first time.


OK, I've got my Iway channel built and running. It's great. My only problem left is that it quits after running for 1 hour. I'm dropping a text file into a folder, and my process flow takes that and loads the records into an old mainframe DB2 database. After insering the records for an hour, it quits with a 'timeout' error. I've verified that when publishing the process flow I have zero in the timeout value, and in my file listener my execution time limit is 7200 (2 hours). Still quitting after 1 hour. Is there another parameter somewhere that I've missed? Thanks for a great forum.

Mike

This message has been edited. Last edited by: Mike in DeLand,

If you're using the SQL agent, it has a timeout parameter too.

Thanks for your response. In my SQL object in the designer, I do have timeout = 0 on there. I looked at the ODBC that is being used and did not see anywhere that a 1 hour timeout would be set.

Hi Mike,
Are you using a persistent database connection?
What is the actual error message you're getting in the iWay log?
I've seen this happen where the firewall chops the connection to the MF after a period, may be worth checking with your firewall guys.

Thanks for the tip. I ran my procedure yesterday and it ran all the way through. I'm thinking maybe I didn't compile something right.