Hello All,
I am running execute command successfully from qv 12 however the job earlier used to take around 1 minute and now takes around 30 minutes with execute in place.
04:27:31 0195 EXECUTE cmd.exe /C E:\Batchfile\Trigger.bat
2017-07-20 04:27:31 Running an execute command
2017-07-20 04:56:17 0197 exit Script
Any suggestions to fine tune this ? I do not want to block an engine process for so long.
Regards,
Nisha
Check the parameters being passed to QMSEDX. There is a "-timeout" value which indicates how many seconds to wait for the task to complete. The default is 1 minute (your old behavior). Perhaps someone set it to 30 minutes or longer?
-Rob
is there any Loops in the script, Or synthetic keys? Please explain about the data model in detail
Hello Varun,
There is absolutely no such data model issue as its a simple extractor job based on its trigger we are running an hourly application.
Extraction takes 1 min max and now on completion of extraction the bat file triggers the application which is taking 30 minutes.
Earlier it was on successful completion of extraction job but then when if timestamp check was failing we had given dummy load a from b script which is exit condition on failure, however we want to avoid any job failures hence on completion executing script.
Regards,
Nisha
Can you please check the Close when finished check-box is checked? Some time this simple check box end up showing a huge time in the log file.
Thanks,
Varun
We are running through Publisher.
Hello Rob,
It triggers a task in publisher, I am using QMSEDX.exe to trigger it.
Regards,
Nisha
Check the parameters being passed to QMSEDX. There is a "-timeout" value which indicates how many seconds to wait for the task to complete. The default is 1 minute (your old behavior). Perhaps someone set it to 30 minutes or longer?
-Rob
Hello Rob,
Many thanks, I passed a parameter for timeout and it is working as expected now.
Regards,
Nisha