|
Use of save and restarts and their effect |
Top Previous Next |
|
Saves and restarts allow one to run GAMS code up to a point and save the job status in a set of work files, then start another job which has all the results of the first job. Thus, for example, we could divide a big job into pieces running the data component (trandata.gms) then using save to preserve the run status in work files called S1. Then we could run the model component tranmodl.gms restarting from the S1 work files and save the resultant status in work files called S2. Finally we could run the report writing part tranrept.gms restarting from the work files in S2. The net effect of this is the same as if the continuous undivided file was run composed of the three parts in the individual files. Each component would start from the previous component just if it was one continuous file.
|