And, if the GAMS IDE is used, a double-click at an error message in the LOG will navigate directly to the problematic code in the source file.Ĭonsider the following simple example: Set c 'crops' / barley, wheat, soy, wheat, rice / Note Compilation error messages also appear in the LOG file. lst), hence it is easy to detect lines where compilation errors occured by inspection. More often than not, many subsequent compilation errors will have vanished.īefore we will turn to an overview of the most common errors, examples that illustrate them and advice how to resolve them, we will provide some basic information on compilation errors and error messages.Ĭompilation errors are marked with four asterisks ( ****) in the compilation output of the GAMS listing file (also called output file or lst file, since it has the extension. Therefore we recommend to start with fixing the first few errors and to run the program again. Note Frequently, many compilation errors in the latter part of the code are actually consequential errors that will disappear as soon as the compilation errors in the beginning have been resolved. Rosenthal offers some detailed material on this topic. In addition, the tutorial A GAMS Tutorial by Richard E. For an introduction to compilation errors, see section Compilation Errors. In this tutorial we will explain the causes of the most common compilation errors and offer some advice on how to fix them. This can be very frustrating, especially for new users. Often when a program is run for the first time, it cannot be solved successfully because of compilation errors. As detailed in chapter GAMS Output, the execution of a GAMS program passes through several stages, where the compilation is the first stage.

Gams error 149