1; How do you know for sure that tempdbs is not used?
Did you try SET EXPLAIN? Did you check with onstat -D?
onmonitor is no longer supported by informix. If you want to create a new dbspace, you should use onspaces. Did you rebounce your instance?
You are not displaying all the logical logs. What log has flag C and flag L? Do you use logged databases?
1. Did you restart the engine? In order to get the DBSPACTEMP variable accepted, you need to restart the engine. Once restarted, you will get a message in the online.log that the variable has changed.
If you restarted the engine, try with "SET EXPLAIN ON;" before executing the qry. You will get the qryplan, and it should include your temp dbspace.
If you display 'onstat -d', does your temporary dbspace contain a T flag?
2. Even with logged databases, IDS 9.30 has dynamic logging. It will create new log files on the fly, but only when needed. You don't know what log contains the oldest open transaction. The C flag will show you in what log it is currently writing. The L flag will show you in what log the latest checkpoint occurred.
I recreated the dbspace WITHOUT mentioning that it is a temporary dbspace but added this in the onconfig as DBSPACETEMP and restarted the server. THEN THE PROCESS BEGAN TO USE THE TEMP DBSPACE for creating temporary tables.
But WHEN IT WAS CREATED AS A TEMPORARY DBSPACE ( and added this as a DBSPACETEMP in ONCONFIG) , the temporary tables did NOT use this dbspace.