Exception occurs in Fortran

This scenario describes the behavior of an application that contains a Fortran and a COBOL routine. Refer to Figure 1 throughout the following discussion. In this scenario, a COBOL main routine invokes a Fortran subroutine. An exception occurs in the Fortran subroutine.

The actions taken follow the three Language Environment condition handling steps: enablement, condition, and termination imminent.

1. If an I/O error is detected on a Fortran I/O statement that contains an ERR or IOSTAT specifier, Fortran semantics take precedence. The exception is not signaled to the Language Environment condition handler.
2. In the enablement step, Fortran treats all exceptions as conditions. Processing continues with the condition handling step, described below.
3. There is no user-written condition handler on the Fortran stack frame (because CEEHDLR cannot be called from a Fortran routine), and the condition is percolated.
4. If a user-written condition handler registered using CEEHDLR is present on the COBOL stack frame, it is given control. (User-written condition handlers written in COBOL must be compiled with COBOL/370 or COBOL for MVS & VM.) If it successfully issues a resume, with or without moving the resume cursor, the condition handling step ends. Processing continues in the routine to which the resume cursor points. Note that you must be careful when moving the resume cursor in an application that contains a COBOL program. See GOTO out-of-block and move resume cursor for details.

   In this example, there is not a user-written condition handler registered for the condition, so the condition is percolated.

5. If the condition is of severity 0 or 1, Language Environment default actions take place, as described in Table 1.
6. If the condition is of severity 2 or above, Language Environment default action is to promote the condition to T_I_U (Termination Imminent due to an Unhandled condition) and redrive the stack. Condition handling now enters the termination imminent step.
7. If on the second pass of the stack no condition handler moves the resume cursor and issues a resume, Language Environment terminates the thread.