Exceptions handler question
-
Hi, I have a question about information provided by the exception handler My Background is on the MainFrame there Z/OS MVS via RTM (Recovery Termination Manager) provides information about the abend in a COntrol block SWDA (System Diagnotic Area) The Recovery Routine (ESTAE,ARR,FRR) provides the abilty to do a retry of the Aborted Task Does the FRameWork (AFX) provide anything besides a catch routine for the code that is problematic Thanks
-
Hi, I have a question about information provided by the exception handler My Background is on the MainFrame there Z/OS MVS via RTM (Recovery Termination Manager) provides information about the abend in a COntrol block SWDA (System Diagnotic Area) The Recovery Routine (ESTAE,ARR,FRR) provides the abilty to do a retry of the Aborted Task Does the FRameWork (AFX) provide anything besides a catch routine for the code that is problematic Thanks
-
Hi, I have a question about information provided by the exception handler My Background is on the MainFrame there Z/OS MVS via RTM (Recovery Termination Manager) provides information about the abend in a COntrol block SWDA (System Diagnotic Area) The Recovery Routine (ESTAE,ARR,FRR) provides the abilty to do a retry of the Aborted Task Does the FRameWork (AFX) provide anything besides a catch routine for the code that is problematic Thanks
To my knowledge, MFC does not contain tools for managing task transactions. There is no common framework for managing undos, redos, etc... The try / catch mechanism is a simplistic implementation of such a system, built into C++ that allows a program to gracefully unwind from an aborted task. the Afx classes that support exception handling, simply build upon this framework. I have seen articles that discuss transaction processing for the windows file system and other kernel elements, coming up in future releases, but at this time, I don't know much about it. You'll likely find that you'll need to roll your own Transactional Tasks manager for your application.
-
What exactly is your issue in terms of C/C++/MFC? What frame work are you talking about?
One of these days I'm going to think of a really clever signature.
-
you code a Catch pargraph and an excpetion happens somewhere in your THREAD the catch block is executed but you really don't know where in your code it happened Thanks
I know how to code a catch block, I was just wondering whether you had posted in the correct forum. When you catch the exception it should contain sufficient information for you to discover what went wrong in your code.
One of these days I'm going to think of a really clever signature.
-
you code a Catch pargraph and an excpetion happens somewhere in your THREAD the catch block is executed but you really don't know where in your code it happened Thanks
// don't know where in your code it happened Let your debugger stop at any exception (IDE::Ctrl+Alt+E in a loaded solution) :)
They sought it with thimbles, they sought it with care; They pursued it with forks and hope; They threatened its life with a railway-share; They charmed it with smiles and soap. :)