Error 32504

I'm working on a site with 4 servers running identical Informix versions (OWS 7.20, AIX 4.2) and identical software. The sites are mostly standalone except for one suite of tables which is shared. We went through using one set of physical tables and synonyms for the rest of the sites (on the shared tables), but these are heavily used and performance over the WAN precluded continuing with this setup. So, now the tables are phsically present at all sites and the software (RDS 6.05) inserts/updates/ deletes at all 4 as required. As there are several hundred users total at these sites, and each site's local administrator has autonomy to add and delete users as required, it has become a complete pain to continually keep the sites' password files in sync with each other so that Informix can do its remote thang. Unfortunately, an option like NIS is not possible. Recently I began fiddling with SET SESSION AUTHORIZATION and discovered that although an indivual user could not use it to change usernames, a DBA priviledged SPL with public execute permission could. Thinking I had found the answer, I created a 'psuedo'user at each site, and created an SPL to SET SESSION AUTHORIZATION to this user. The 'pseudo'user was given Informix permissions to do only what needed to be done at the remote sites. Alas, when a session that has run SET SESSION AUTHORIZATION attempts to remotely update a table, I get the error number I put in the Subject of this post. The error describes how I can't do remote work on a table if I have changed my "sensitivity level". Now, I'm a 1990's guy and am well aware of society's prevelance for men to be more in tune with their feminine sides, but I did not know that RDBMS's had got in on the act. So, what's a "sensitivity level" and how do I change it to something I can use? I suspect it's just trying to tell me I can't change users and do remote work on tables, but it doesn't actually say that in the error message. Maybe there's a way out? Failing that, anyone got any bright ideas as to how to work around this awful requirement for entries in hosts.equiv and local passwd files for each remote user? TIA -- Bryan Tonnet batonnet@phase4.com.au