MSX File with Undefined Constant Running without Error

[henryricca]

When an undefined variable was referred to in the [TERMS] section of a .msx file due to a typo, MSX ran without outputting an error message. Not sure if MSX just assumes a default value for undefined constants in cases like this, but an error message would have helped us quickly realize that a typo was responsible for the odd results we were getting. The following 3 files are in the attached .zip folder, which highlight the issue.

chloramine.inp - EPANET input file for the simple example network provided with the manual

chloramine_undefined_constant.msx - MSX input file with the undefined constant due to a typo. In line 97, 'DCO1' was typed instead of 'DOC1'

chloramine_undefined_constant.rpt - report file generated from running 'chloramine.inp' with 'chloramine_undefined_constant.msx'. The results are odd due to the typo, but no error message was output

Undefined_Constant_Issue.zip