CRE Programmer's Guide

CRE Services
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
2-2
Comparing the CRE in the OSS and Guardian
Environments
Note that the CRE does not support Event Management Service (EMS) events.
Comparing the CRE in the OSS and Guardian
Environments
Many of the services provided by the CRE in the Guardian environment are not
needed or are not meaningful in the OSS environment. This subsection summarizes
the differences between CRE services in the OSS and Guardian environments for
each of the following topics:
•
Standard Files on page 2-2
•
$RECEIVE on page 2-3
•
Memory Organization on page 2-3
•
Traps and Exceptions on page 2-3
•
Program Initialization on page 2-4
•
Program Termination on page 2-4
•
Error Reporting on page 2-5
•
Standard Functions on page 2-5
•
CRE Services on page 2-5
•
Process Pairs on page 2-6 (fault-tolerant programming)
Standard Files
In the Guardian API or environment, the CRE supports three standard files (standard
input, standard out, and standard log), and supports routines that enable program
Using the Native Heap Managers
on page 2-43
Learn how to use the native heap managers and how to
query or set heap-management attributes
TNS CRE Traps and Exceptions
on page 2-47 and Native CRE
Signals and Exceptions on
page 2-55
Learn how the CRE handles traps, signals, and
exceptions
Reporting CRE Errors in the OSS
Environment on page 2-54
Understand how the CRE determines where it writes
error messages in the OSS environment
Using Standard Functions
on
page 2-56
Call CRE library functions explicitly from your program
Using Process Pairs
on
page 2-59
Learn how the CRE manages process pairs
Using the Inspect, Native Inspect,
and Visual Inspect Symbolic
Debuggers With CRE Programs
on page 2-62
Use the corresponding symbolic debugger product to
locate where a program is overwriting CRE data
Circumventing the CRE
on
page 2-66
Use system procedures to manipulate services
managed by the CRE
Read the Following
Subsection: In order to: (continued)