Cancelled SCRI remains Generating status while running :WAIT command

[Michael A. Lowry]

I tried to cancel a script moments ago. The script was running a :WAIT command. I noticed that the script remained running (in Generating status) until the wait time had fully elapsed. Is this normal? Is there a way to cancel such a task immediately?

[Anon Anon]

Hi Michael,

yeah this is normal behavior - if a script is in state "Generating" you can cancel it but there will be noch change in its state until the time elapsed.

Interestingly the "cancel" command is recognized but delayed.
I did a short test with a WAIT 120 script command, after almost 2 Minutes its being cancelled but this time period does not show up in statistics.
after a while I got the popup window user aborted ...

https://us.v-cdn.net/5019921/uploads/editor/cx/oydzjxsepbld.jpg" width="1229">

For my sandbox ENV I usually choose "change status manually" in activity Window - but for our PROD env. I want to be safe and wait until time elapses and the popup from my cancel command appears :-)

cheers, Wolfgang

[Legacy User]

Hi,

I support Wolfgang’s approach. The "change status manually" should really be the very last thing to do.

In this example it might leave back some entries in MQMEM. It’s no problem for the system having a few obsolete ones there. However if this is done on a wide base, it can end up in Thousands of them, still no issue for the system, but can cause some irritation.

 KR, Josef

[Michael A. Lowry]

In my Automation Engine tracing workflow, I opted to break the longer waits up into smaller ones, for a couple of reasons:

• so that other important changes (like a filling file system) would be detected earlier; and
• so that cancel commands would be caught and acted upon sooner.

It would be nice if there were a variant of the :WAIT command that did not block other actions.