How conditions arising in child enclaves are handled
If a Language Environment or CEEBXITA-initiated (generated by setting the CEEAUE_ABND field of CEEBXITA) abend occurs in a child enclave created by SVC LINK or CMSCALL, regardless of the language of its main, the entire process is terminated.
Condition handling in child enclaves created by SVC LINK or CMSCALL varies, depending on the language of the child's main routine, the setting of the TRAP runtime option in the parent and child enclaves, the type of condition, and whether the routine is running under MVS™. Refer to one of the following tables to see what happens when a condition remains unhandled in a child enclave.
| If the child enclave was created by: | See: |
|---|---|
| An SVC LINK under MVS and has a C, C++, or Language Environment-conforming assembler main routine | Table 1 |
| An SVC LINK or CMSCALL under CMS and has a C or Language Environment-conforming assembler main routine | Table 2 |
| An SVC LINK under MVS and has a COBOL main program | Table 1 |
| An SVC LINK under MVS and has a Fortran or PL/I main routine | Table 1 |
You should always run your applications with TRAP(ON) or your results might be unpredictable.