When PRO IV cannot communicate with SQL Server, or there is a datatype mismatch or any other SQL error, PRO IV halts the session and requires user intervention. I need to run a batch job that uses SQL tables, but do not want it to halt my overnight processing if there is an error. Is there any way to trap the SQL 366 error so that it doesn't halt the session? Has anyone had any luck with this?
Click the link below to see the new game I'm developing!
2 replies to this topic
#2
Mike Schoen
-
- Members
-
- 198 posts
Expert
- Gender:Male
- Location:Guelph, Canada
Posted 13 January 2003 - 04:33 PM
You can override the rollback function @RFUNCT at start of your batch process, and then log errors and continue processing. The only thing to watch out for is to make sure that your rollback function doesn't use any oracle files itself, or it will rollback while trying to log the rollback 
#3
Thomas Haight
-
- Members
-
- 14 posts
Member
- Gender:Male
- Location:Freeport, United States
Posted 14 January 2003 - 02:36 PM
Thanks for the reply Mike... But that still does not stop the message that comes up requiring user input. Also, this is a SQL Server app, not Oracle. I don't know if that makes a difference.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
