CRE Programmer's Guide

Contents
Common Run-Time Environment (CRE) Programmer’s Guide528146-004
viii
10. Run-Time Diagnostic Messages (continued)
10. Run-Time Diagnostic Messages (continued)
Heap-Management Messages 10-12
Function Parameter Message 10-14
Math Function Messages 10-15
Function Parameter Messages 10-17
Input/Output Messages 10-18
COBOL Messages 10-25
FORTRAN Messages 10-25
Native CRE Messages 10-25
Mapping Message Numbers Between Run-Time Environments 10-26
A. Data Type Correspondence
Glossary
Index
Examples
Example 2-1. C Program That Overwrites the MCB Pointer 2-65
Example 2-2. Run of C Program That Overwrites the MCB Pointer 2-65
Example 2-3. Inspect Session for C Program That Overwrites the MCB
Pointer 2-66
Figures
Figure 1-1. Language-Specific Run-Time Environments 1-1
Figure 1-2. The Common Run-Time Environment in the Guardian
Environment 1-2
Figure 1-3.
The Common Run-Time Environment in the OSS Environment 1-3
Figure 2-1.
A C-Series Mixed-Language Process 2-18
Figure 2-2. Using the CRE—Mixed-Language Process—Quiescent State 2-20
Figure 2-3. Using the CRE—The COBOL Routine Defaults Opening Standard
Output 2-21
Figure 2-4. Using the CRE—The TAL Routine Opens Standard Output 2-22
Figure 2-5. Using the CRE—The C Routine Opens Standard Output 2-23
Figure 2-6. Using the CRE—Quiescent State With Standard Output Open 2-24
Figure 2-7. Using the CRE—The COBOL Routine Writes to the File
$VOL.SUBVOL.FILE 2-25
Figure 2-8. Using the CRE—The TAL Routine Writes to the File
$VOL.SUBVOL.FILE 2-26
Figure 2-9. Using the CRE—The C Routine Writes to the File
$VOL.SUBVOL.FILE 2-27