Stored Proc problems

We are experiencing some problems with the use of stored procedures and I am interested to see if anyone else has encountered these problems and what they have done or what suggestions you might have for me. Our situation: We are running OnLine 5.02.UC6 on SUN 2000 (Solaris). We are using stored procedures quite heavily. These stored procedures are called from within 4GL code. Upon running the 4GL reports we receive the following errors: SQL statement error number -211 Cannot read system catalog (sysprocauth) SYSTEM error number -107 ISAM error: record is locked SQL statement error number -312 Cannot update system catalog (sysprocplan) SYSTEM error number -100 ISAM error: duplicate value for a record with unique key. SQL statement error number -397 System catalog (sysprocplan) corrupted. These errors don't occur *every* time we run the reports that use stored procs, but it does seem to occur consistently with the same report, but only when run with certain options. These stored procs select data. The options will make the proc select different data. The manuals say to run the tbchecks. I have run tbcheck -cc which is supposed to check the system catalogs. However, since tbcheck -cc doesn't print any information about the stored procedure system tables, I would say tbcheck isn't checking these tables. I have also called tech support. They asked me to drop and re-create the stored procedures followed with update statistics. I have done this and it doesn't make a difference. They have identified a bug, #33292. This bug is associated with the 312, 100 error and is fixed in 6.0. This doesn't help me much since we aren't moving to 7.x until mid next year. I am concerned about these errors and any damage it is causing to the database. This is a production system and I don't want to see it crash on me. Any info or assistance would be greatly appreciated. Thanks, Debbie Shelton DBA McCaw Cellular Communications, Inc. debbie.shelton@mccaw.com