tbcheck core dumping

We have two AS400 386 machines, using Interactive unix. On one box, where the database was originally built, we were running 4.0 Online. Unfortunately, we had a problem and overflowed the dreaded lock table. I ran tbcheck -cd, and it core dumped. Since 4.0 was not the most stable release, I saw no real cause for alarm. I also ran a tbcheck -cI, which died with a memory allocation error, and message about "bad columns list for sysindexes". From the output of the tbcheck -cI, I had an idea about which table I thought was damaged, and there were no rows in it, so I didnt worry too much. I was able to do a update statistics and get a dbschema with no problem. This database is now due to be moved to the production 386 machine. As a dry run, I tbunloaded the database and moved it to the new machine, expecting problems. The production box is running 4.1 Online. The database tbload'ed with no problems. Just for grins, we ran the tbchecks again. The tbcheck -cI had no problems. The tbcheck -cd is core dumping. Now what? From my past experience, tbcheck was much improved under 4.1. Has anyone seen this and have any comments/suggestions? thanks, Naomi -- Naomi Walker (aka N7FSA) Anasazi Inc. Phoenix, Arizona 602-395-1731 {uunet!pyramid},{sun!sunburn!gtx!},{asuvax} !anasaz!qip!naomi