Try OpenEdge Now
skip to main content
New and Revised Features
Preface : OpenEdge messages
 

OpenEdge messages

OpenEdge displays several types of messages to inform you of routine and unusual occurrences:
*Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value.
*Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database.
*Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.
After displaying a message, OpenEdge proceeds in one of several ways:
*Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages.
*Returns to the Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages.
*Halts processing of a procedure and returns immediately to the Procedure Editor. This does not happen often.
*Terminates the current session.
OpenEdge messages end with a message number in parentheses. In this example, the message number is 200:
** Unknown table name table. (200)
If you encounter an error that terminates OpenEdge, note the message number before restarting.
* Obtaining more information about OpenEdge messages