Archives of the TeradataForum
Message Posted: Wed, 28 Mar 2001 @ 20:09:44 GMT
You can't directly abort a session through SQL. The best you can do is set the user's spool down to zero. This would eliminate the user's work area. This works as long as the user's request needs work space (spool) after you have set the spool limit to zero. This works in the vast majority of cases, but it's not perfect.
From MVS, there are TDP commands which can be used to abort sessions, however this would require some programming. Specifically, you would need to identify the sessions to be aborted, perhaps through SQL, and then exeecute the appropriate TDP command (KILL I think) for each session. This would require RACF authorization to perform the TDP commands.
Another alternative is to develop a program that takes advantage of the Teradata PM/API. This is the API used by PMON. The API is pretty straightforward and there is a lot of flexibility to develop a monitoring program. At the customer I am working with now, we designed and developed a fairly robust C application using PM/API that we use for monitoring the system and aborting queries or sessions based speecific rules that we set up. Again, this required a significant development effort, but the benefits have been significant as well.
Thomas F. Stanek
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|