Errors for x12 with user provided spec file since Eviews 9
Posted: Tue Jun 16, 2015 5:43 am
Since Eviews 9 several jobs that use the x12 method with a user provided specification file fail with errors. With earlier versions of Eviews these jobs worked correctly. I used the 64 bit version and the build of June 8.
A simple example job that produces error messages is attached (test.prg, with spec file test.txt). The job gives the following error messages:
Line 11: force=both
^
ERROR: Argument name "force" not found
Line 14: automdl {method=best file="x12a.mdl"}
^
ERROR: Argument name "method" not found
Line 14: automdl {method=best file="x12a.mdl"}
^
ERROR: Argument name "file" not found
Is this a bug or have some arguments of x12 been cancelled?
A simple example job that produces error messages is attached (test.prg, with spec file test.txt). The job gives the following error messages:
Line 11: force=both
^
ERROR: Argument name "force" not found
Line 14: automdl {method=best file="x12a.mdl"}
^
ERROR: Argument name "method" not found
Line 14: automdl {method=best file="x12a.mdl"}
^
ERROR: Argument name "file" not found
Is this a bug or have some arguments of x12 been cancelled?