gpg;e seupdate does work for inactive accounts

This query shows search engine update jobs downloading structure reports for enabled seusers but disabled accounts.

select accounts.description, accounts.isActive, tasks.name, tasks.accountID, jobID, jobHistory.name, jobHistory.node, jobHistory.endTime, jobHistory.cpuTime, jobHistory.wallTime, jobHistory.maxMemory, jobHistory.maxResidentMemory, jobHistory.maxVirtualMemory, minute, hour, dayOfMonth, dayOfWeek, uncompress(stderrCompressed) from tasks join jobHistory on taskID=tasks.id join tsacommon.accounts on accountID=accounts.id where endTime < '2010-10-21 07:00:00' and endTime > '2010-10-20 07:00:00' and wallTime > '00:10:00' and accounts.isActive='false' order by wallTime\G

This uses unnecessary quota and CPU time on the cluster work nodes and database servers.

If an account ID passed in is inactive, seupdate should not do anything for that account. This is happening because the code that downloads the structure reports is ignoring the isActive flag for the account it's finding seUsers for.