I found the answer.
The QMSEDX.exe when passed with the task name waits for the status after it triggers the reload.
It waits for a minute and then thinks that something has gone wrong and tries to terminate itself. in the process sends a signal to CTRL M saying that the job failed.
This can be traced back by setting the verbosity to 5 if some one see the same problem. some thing like the below
QMSEDX.exe -task="FILENAME.QVW" -password="XXXX" -verbosity=5
The soution to this problem would be to upgrade your QMSEDX.exe to 2.0.3 where the developers have fixed this problem by retrying to check after few minutes and the job is now expectedly not sending any signal to external triggers like control M.
Hope this helps.
i do not have a perfect document to help you with the steps. i think with a bit of patience , this should work with the scratch pad notes below.
control m should trigger a batch script on your qlikview server.
on the qlikview side,
download th QMSEDX ( check if the EDX is supported now )
setup a folder and call the batch or command script with like this
E:\Qlikview_EDX_JOBS\QMSEDX_CommandLine\new\QMSEDX.exe -task="EDX Global Extract Run/Global_Extract_QVD_Generator.qvw" -password="1234"
make sure , you are setting up this reload as a EDX (External event) in QMC and set your password 1234
set up your folders accessible (not browsable though) in QMC.
also if the QV server doesn't have controlm agent, install that too.
check permissions of your folders too
once you setup all steps above, you should be able to trigger the script from controlm
give us a shout if this is not working.
note - try this trigger with a quickly reloable document
all the best