I use to be able to cancel my query in Toad before I am now noticing it’s not working like it use. I am not sure if this is a TOAD issue or a Db2 z/OS issue. I know I can’t cancel threads on z/OS, but Toad was always good about canceling my query after the warning of records being pulled back.
If I run a query that takes a long time I get the following message:
I would then say Yes.But now it seems like my query has canceled but i can’t run any other queries unless I force close out of Toad via task manager.
I never had this issue before 6.3, but I am not sure like I said if its related to 6.3 or some change on the RDBMS.
This is an old /new issue. Previous to version 6.2 this happened to me all the time. In version 6.2 this got corrected, and now I’m experiencing it again.
Another issue that came back ( I think), is when I run a script across many schema(s). If one of the files is empty, it hangs. This was corrected in version 6.2 and got messed up in version 6.3.
I am not going to stop using version 6.3 as the compare to excel feature makes life much easier for me, but I would like the big boys to check this out.
That is good to know! Thanks for the information. Hopefully they can fix it quickly. I am enjoying 6.3 and going back to 6.2 is something I want to do.