monitor temp dbspace

Our environment: 7.2.UC5, Sun 5.2.1 solaris, probably about 400-600 connections - occasionally a user will create a really wild outer join on (possibly) unindexed filter, creating a REALLY LARGE usage of temp dbspace for the sort (order by) or some other (scan..) I have developed a method for monitoring the temp dbspace - when the user has actually built a temp table for his/her use - but what if the engine has to create an object for temporary use ( for the order by ) - it may show up in the onstat -g sql as v_sort or multi scans as well...(?) what i really would like is to see some SMI ( syssession?, sessionprofile?) linking the offending user to his ownership of the space ( via informix engine) how about max_disksorts? is their a correlation there? any ideas welcomed... erosenth@ix.netcom.com or edward_rosenthal@providian.com thanks ....