More on -922 error

Application: Informix SE 5.0 Operating System: SCO Openserver 5.0.4 release e. Okay, I have more info on my Informix -922 error that I posted last week: I finally tracked down the problem, but I don't have a fix for it. We used to have an SCO Unix 3.2v4.2 system. This past fall, I tarred the user directories and untarred them on our new server which runs SCO Openserver 5.0.4e. None of the old directories give me the -922 error, but whenever I create a new directory, it does. Everything is identical between the old and new systems: the umasks, the directory permissions, all the user accounts, the whole directory structure, etc... The only difference is the version on the operating system. Here is an example: SCO 5.0.4e system: In the /u/jeff directory (my account). I run isql, no errors. cd ace (a subdirectory that was transferred from the old system via tar), I run isql - no errors. mkdir /u/jeff/test; cd /u/jeff/test; isql (I get the -922 error, dir permissions are 755 just like /u/jeff/ace - yet one works, the other does not). In /tmp, I run isql - no errors. mkdir /tmp/temp; cd /tmp/temp; isql (the -922 error occurs). SCO 3.2v4.2 system: In /u/jeff, I run isql, no errors. mkdir /u/jeff/test; cd /u/jeff/test; isql - still no errors. Now, if I mount the old system, I can cd into my old account, create a subdirectory, and run isql just fine (although I'm logged into SCO/OS 5.0.4e). So, the problem must be with the inode's on SCO/OS 5.0.4 as seen by Informix SE 5.0 right? Any idea where to go from here? BTW: Afterwards, I also created a copy of the 3.2v4.2 mkdir program in SCO/OS 5.0.4 but that didn't make a difference. I still got the -922 when I created a new directory. -- Jeff Jeff Raihanan Info Systems Director Network Behavioral HealthCare, Inc. Portland, Oregon jeff@nbhc.org