Essmsh executes maxl script, but does not end

Question

Hi, I could really need some help with a Maxl script I've built for a customer.
The script builds the account dimension several times in a row. Each time for a different Alias Table.
I choose this method, instead of the Load Alias_Table method, because I don't want to load Aliases for all members in all dimensions. Just only for the account dimension.
When running the script from a batch file manually, nothing seems wrong, however when running the batch file from HAL essmsh never finishes.
This is what happens in HAL:
a batch file is executed containing the following command:
call Essmsh D:\JDE2GL\Bin\Maxl_UpdateOutline.txt
The Maxl_UpdateOutline.txt contains the following Maxl script:
login {user} {password} on {server};
spool stdout on to 'output.txt';
spool stderr on to 'errors.txt';
alter database {application}.{database} unlock all objects;
alter system unload application {application};
import database {appliaction}.{database} dimensions
connect as '{SQLuser}' identified by '{SQLpassword}' using server rules_file 'DmAc_Def'
preserve all data on error append to 'D:\\JDE2GL\\Outbox\\MaxL_UpdateOutlineAc_Def.err';
import database {application}.{database} dimensions
connect as '{SQLuser}' identified by '{SQLpassword}' using server rules_file 'DmAc_BEL'
preserve all data on error append to 'D:\\JDE2GL\\Outbox\\MaxL_UpdateOutlineAc_BEL.err';
import database {application}.{database} dimensions
connect as '{SQLuser}' identified by '{SQLpassword}' using server rules_file 'DmAc_FRA'
preserve all data on error append to 'D:\\JDE2GL\\Outbox\\MaxL_UpdateOutlineAc_FRA.err';
import database {application}.{database} dimensions
connect as '{SQLuser}' identified by '{SQLpassword}' using server rules_file 'DmAc_USA'
preserve all data on error append to 'D:\\JDE2GL\\Outbox\\MaxL_UpdateOutlineAc_USA.err';
import database {application}.{database} dimensions
connect as '{SQLuser}' identified by '{SQLpassword}' using server rules_file 'DmAc_SPA'
preserve all data on error append to 'D:\\JDE2GL\\Outbox\\MaxL_UpdateOutlineAc_SPA.err';
import database {application}.{database} dimensions
connect as '{SQLuser}' identified by '{SQLpassword}' using server rules_file 'DmAc_ARG'
preserve all data on error append to 'D:\\JDE2GL\\Outbox\\MaxL_UpdateOutlineAc_ARG.err';
spool off;
logout;
exit;
In the "Outbox" directory I can see the error log files, with some warnings on duplicate member names appear.
In the Essbase Application Log file, I can see that all dimension builds were executed succesfully.
The spool file output.txt nor the errors.txt are created when running from HAL.
I've used this HAL procedure thousands of times with one dimension build without any problems, even with more dimension builds it didn't give any errors until recently.
Does somebody have any ideas..? Would be much appreciated!
Thanks,
Rudy

Answer 1

Hi,
we work with the exit label as follows:
alter database ...
iferror getmeout;
alter database ...
iferror getmeout...
define label "getmeout";
spool off;
logout;
EXIT;
the spool off and logout command should be part of the defined lable (in your case, too), otherwise you wouldnt logout your session if an error occurs.
Kind regards
André