Interpreting runtime messages

The first step in debugging your routine is to look up any runtime messages. runtime messages are written to the C stderr stream. runtime messages provide users with additional information about a condition, and possible solutions for any errors that occurred. They can be issued by Language Environment common routines or language-specific runtime routines and contain a message prefix, message number, severity code, and descriptive text.

In the following example Language Environment message:
CEE3206S The system detected a specification exception (System Completion Code=0C6).

Language Environment messages can appear even though you made no explicit calls to Language Environment services. C/C++ runtime library routines commonly use the Language Environment services. This is why you can see Language Environment messages even when the application routine does not directly call common runtime services.