Ok, thank you for the model input files. I tested running the model instance you provided, and immediately saw that there were problems:
1) When running with the old TIMES v4.2.7, I can see two GAMS compile errors in the equation EQL_COMCES (which was introduced in v4.2.3). These errors appear only when using TIMESED with STAGES (i.e. a stochastic run with elastic demands), and the errors were caused by not having made that new equation fully stochastic-aware. This small bug in the code was subsequently fixed in TIMES v4.3.1 (in February 2019).
2) However, your listing file shows a lot of more errors, which I cannot reproduce with TIMES v4.2.7 (which is the version number your listing file indicates you are using)! Therefore, I suspect that you, or someone else, has modified your TIMES code in such a way that you get many more GAMS errors.
Consequently, if you are willing to use the ETSAP TIMES code, the solution to the problem is simple: Just upgrade to the latest version, v4.4.1. However, if you want to continue using some modified version of TIMES, I am afraid I am not able to suggest any solution; ETSAP cannot really provide support for any modified versions of the code. But in that case I would also strongly encourage you to share the modified code with the ETSAP community, such that if you have implemented any useful new features or improvements, those can be integrated into the common code.
1) When running with the old TIMES v4.2.7, I can see two GAMS compile errors in the equation EQL_COMCES (which was introduced in v4.2.3). These errors appear only when using TIMESED with STAGES (i.e. a stochastic run with elastic demands), and the errors were caused by not having made that new equation fully stochastic-aware. This small bug in the code was subsequently fixed in TIMES v4.3.1 (in February 2019).
2) However, your listing file shows a lot of more errors, which I cannot reproduce with TIMES v4.2.7 (which is the version number your listing file indicates you are using)! Therefore, I suspect that you, or someone else, has modified your TIMES code in such a way that you get many more GAMS errors.
Consequently, if you are willing to use the ETSAP TIMES code, the solution to the problem is simple: Just upgrade to the latest version, v4.4.1. However, if you want to continue using some modified version of TIMES, I am afraid I am not able to suggest any solution; ETSAP cannot really provide support for any modified versions of the code. But in that case I would also strongly encourage you to share the modified code with the ETSAP community, such that if you have implemented any useful new features or improvements, those can be integrated into the common code.