In a perfect world, perfect programs would always behave the way they were intended to. All the data would be consistent, the users would always act properly, and there would be no unexpected conditions. Unfortunately, the perfect world does not exist and even the most elaborate programs may sometimes fail. To minimize losses and prevent damage from spreading any further, developers, users, and system administrators should react to any unexpected circumstances.
This chapter will also describe the classic exception. The information pertaining to the classic exception for the program is important because, in older implementations, they can come across this solution.
This philosophy was also incorporated in the Systems Applications and Products in Data Processing (SAP) system, through the use of several tools, concepts, and syntax statements. This chapter will describe how to handle improper runtime behavior, both at the programming level and error root...