IBM DB2 support determined the 'hang' problem was caused by a DB2 application program. Without getting into details, DB2 does a 'suspend for commit' that can take 7+ CPU minutes to complete.
DB2 support suggests we fix our application (which I agree we should). However, it seems like the DB2 code should not be able to cause a 7+ minute MVS 'outage'. Am I wrong to think the DB2 code should be fixed too? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
