Language Environment and HLL condition handling interactions

This section discusses the condition handling discussion. It would be helpful for you to read Introduction to Language Environment condition handling before reading this topic. Introduction to Language Environment condition handling introduces you to terminology and concepts that are discussed in the present topic, and offers a brief overview of pre-Language Environment HLL condition handling. It discusses in detail the Language Environment condition handling model and the many services that you can use to tailor how conditions are handled in your application. In addition, it introduces the three steps of condition handling in Language Environment.

If you are running a single-language application written in C or PL/I, which have extensive built-in error handling functions, and you are relying entirely upon the semantics of these languages to handle errors, you will not notice much difference in how errors are handled under Language Environment.

However, if you are running a single-language application written in COBOL or assembler that has little built-in error handling, you might notice a change in how errors are handled under Language Environment. For example, in an application that relies on abend codes to handle errors, you might need to alter the assembler user exit to get the same behavior under Language Environment as under the previous runtime environment. See Using runtime user exits for information about modifying the assembler user exit.

For information about condition handling in ILC applications, see z/OS V2R1.0 Language Environment Writing Interlanguage Communication Applications.