Maxl Script will not write to error file for data laod.

Question

Sorry Glenn here is the new thread. I re ran without the semi colon after data 3 and the same error came up without anything being written to the error file.
I purposely removed a member from the orginal outline that is included in the data loaded but yet the error file is not written to. I tried doing the load manually but executing it in the background, error file is to be created on my local HD but it does not write it there. Checked the output and it is written to a directory located on the server. Although i think this is normal.
Could it be that it will not write to a local drive? I am going to try specifying a spot on the server to see if it runs there.
thanks
Original post below.
Hello,
I am also having this issue.
I will include my script below but will state some details before
We are on Essbase 11.1.1.3
I am running Admin Console from my client PC that connects to the server in the script and I read that in this set up the error file will not get written to. This documentation was for v 9.1.3
Here is my script (i changed some of the names)
login 'user' 'password' on server';
create application 'Money1' as 'Money2';
spool stderr on to 'errorfile';
import database 'Money1'.'Main' data
from local text data_file 'Money1_Data.txt'
using server rules_file 'Data3'
on error append to 'dataload.err';
execute calculation 'CALC ALL;' on 'Money1'.'Main';
logout;
spool off;
exit;
here is the error output i get:
code line: on error append to 'dataload.err';
Statement executed with warnings.
(3) Syntax error near ['$']
I don't see a dollar sign anywhere in my code and the error file does not get produced.
Also do error files get written too if the actins are executed in the background?
Thanks!
Alex

Answer 1

This works for me in a MaxL script run through essmsh.exe:
import database appname.dbname data from local text data_file "d:\\datafilename.txt" using server rules_file "rulename"
     on error write to "d:\\errorfilename.err" ;Sometimes EAS (I think you are running it through that) does weird things to MaxL. I eschew MaxL in EAS as much as possible (like 100% of the time).
NB -- the datafilename and errorfilename and their drive letters are local to wherever you're running this process through the MaxL shell. I don't know how that works when you're running EAS -- are drives local to your session, local to the EAS server? Dunno. Leave EAS behind, buy TextPad (no I am not the author of that fine product) and download the MaxL syntax library, and be happy. :)
Regards,
Cameron Lackpour
Edited by: CL on Oct 7, 2010 7:12 AM
Put the MaxL into a code block to get it to display correctly.