Is it possible to call a CMD or VBS within MAXL? Need script help

Question

Hello,
I have a CMD script that uses MAXL to execute Essbase backups, the details of which are located in a txt file. That works fine, and I have the logs being sent to a folder.
What I am trying to accomplish is AFTER it is finished running the backup, it calls a CMD script to parse the log file for errors, then either send a successful or failure notification through SMTP.
I have all the scripts to perform the operations and they all function properly, but when I run it, the email is sent before the Essbase backup has completed.
Is there a better way to do this like possibly calling the other CMD/VBS directly from within the MAXL shell? This is my current CMD file:
Echo Calls Maxl shell with reference to EssbaseBackup.txt for variables
call \\<server>\HyperionPlanning\App\Backups\MaxlBackup.cmd
Echo Search Essbase Backup Logs for Errors
findstr /c:"ERROR" \\<server>\HyperionPlanning\App\Backups\Logs\HyperionSetEssbaseForBackuplog.txt
if %ERRORLEVEL% NEQ 0 goto NO_ERROR
goto ERROR
Echo Sends backup success mail
:NO_ERROR
\\<server>\HyperionPlanning\App\Backups\mail_send_success.vbs
EXIT 0
Echo Sends backup failure notification
:ERROR
\\<server>\HyperionPlanning\App\Backups\backup_failed.vbs
EXIT 1MaxlBackup.cmd
"C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\EssbaseClient-32\bin\startmaxl.cmd" "\\<server>\HyperionPlanning\App\Backups\EssbaseBackup.txt"EssbaseBackup.txt
spool on to '\\<server>\HyperionPlanning\App\Backups\logs\HyperionSetEssbaseForBackuplog.txt';
set timestamp on;set timestamp off;
login admin identified by <password> on <server>;
alter system logout session on application App force;
alter application App disable connects;
alter database App.main force archive to file 'F:\Backups\App\Appmain.arc';
alter database App.cap force archive to file 'F:\Backups\App\Appcap.arc';
alter application App enable connects;
set timestamp on;set timestamp off;
logout;
spool off;Edited by: Metatron on Mar 30, 2012 8:10 AM

Answer 1

Try taking the code that is in the MaxLBackup.cmd and stick it into the root script just to remove that area of complexity. If that works, you might also try removing CALL from the line. Although I thought the point of CALL was to run another script and then return control to originating script.
Here's some old (System 9.3.1) code that does what you're doing -- the pathing is wrong for 11x:
REM Write filters to disc
%hyperion_home%\products\Essbase\EssbaseClient\bin\essmsh.exe -D write_filters_to_disc.mshs %7,%8
REM If error, go to end, else write
IF ERRORLEVEL == 1 (SET errormsg=Error! - Read of filters from Essbase failed &     GOTO ERROR)The -D and .mshs are to handle an encrypted MaxL script.
Regards,
Cameron Lackpour