TM1 Tops

[Eric]

I have referred to the limited TM1 Tops documentation.
http://www.applix.com/doc_lib/ENG/wwhel ... wwhelp.htm

I am trying to cancel a thread; however, I have tried the C & V command and nothing happens any clues?

Version 9.0 SP3

Could it be the security setting
SecurityPackageName=Kerberos
IntegratedSecurityMode=3

Think it is being finicky with IntegratedSecurityMode=3 setting?

[Alan Kirk]

I am trying to cancel a thread; however, I have tried the C & V command and nothing happens any clues?

I don't think that cancelling a thread has a 100% success rate; I'm sure that I read of instances in the old Forum where it just didn't work, and indeed I've had one or two myself on 9.1SP3. As Mike C explained it at the time TM1 Top was released:

The Tm1Top utility will not "kill" a thread. It is designed to cancel thread processing when a thread is involved in doing a lengthy calculation. (The prompt for the thread ID reads "Cancel processing of a thread".) The Tm1Top functionality merely sets a "please exit" bit in the thread header which is periodically checked by the thread. If the bit is set the threads exits through the normal channels. It is not "killed" which would not release locks, private objects, and other resources.

The implication as I read it is that if you have a thread which never checks the said header, or does so only very, very infrequently, it's entirely possible that you'll be waiting an awfully long time for the thread to end.

If I were to choose an analogy, the cancel thread command in TM1 top is like putting up a "Stop" sign in front of a speeding driver. If the driver is well behaved / programmed, they'll stop.

A TRUE thread killing tool would be like pumping a few 9mm slugs into the car's tyres, but alas a metaphorical 92FS Beretta isn't part of the TM1 Top arsenal.

[ScottW]

As far as I am aware the tm1top "C" command to kill a thread works for the following scenarios only
- cancels a TI process (by inserting ProcessQuit command)
- cancels construction of a view

For anything else (such as saving a bad rule that has gone haywire ... ) the "C" command will not work.

[Eric]

I apologize, my post must be unclear.

I literally go to the Cmd can entered C.....waited..... nothing happened. Read documentation where it states upon hitting C you should be prompted to input the thread ID to cancel. That did not happen. Upon further review I saw comments regarding entering V in the cmd to validate the user. I type v and hit enter....wait....nothing happened again!

Thought that the security level setup was causing the issue, but maybe not. If no one has any ideas I will submit a ticket to insight, YEA!

[Martin Ryan]

Are you typing in capitals? I think it has to be capital V and capital C.

Martin

[Steve Vincent]

yep, must be SHIFT+C or SHIFT+V to get it to work...

[Eric]

GRRRRRR!!!!!

Well that is one way to make a guy feel like a jack@@@. It works now.

[ScottW]

Traps for young players eh.
I did mention the "C" command not the "c" command didn't I

[Eric]

grumble.... grumble...grumble. Yes you and all of the documentation said "C" not "c". Stupid case sensitivity!

Man, I just got my He-Man Sword of Power in the mail.... Please don't make me return it.