Re: Stored procedures - unpredictable or what ?!

> rt10hp@csl.gov.uk (Richard Thomas) writes: > ..snip.. > What I really hate is an SP that works one day, > crashes out with an error message the next day, and causes the whole > system to core dump the next. (OK, the last one hasn't happened yet, > but it's only a matter of time!). The problems always occur with > system statements, and tend to throw up spurious errors such as -1, > -10, -11, and even a -103 - scary. (I won't waste bandwidth by telling > you what these errors are - they are all totally irrelevant to what > the SP is trying to do, and as I said, they don't seem to happen all > the time. 'finderr' will give you the error message). 103 may be irrelevant, but why are the others that. They are os-error messages and you are making a call to the os via the system statement. Remember that the exact error message you see from using finderr may be wrong. The os may return these numbers due to other errors. According to Informix you should be able to find the true errors in your os documentation from the error numbers. I guess you can if you are a C-programmer (with some Unix experience). If not you may have a hard time. > Questions: > > 1) Is anyone else out there having these problems ? Not yet. > 2) Has anyone found a solution ? > 3) Is it time to go home yet ? Yes, but come back soon. > 4) Why can't my organisation employ a professional Informix type person ? Aren't you about to become that? :-) > Yours in anguish, > Richard. > > NB I'm using Online 7.10.UD1 with dbaccess By now a significant number of defects have been found in the 7.10 releases. It might help you to upgrade to 7.12 or something newer. Nils.Myklebust@ccmail.telemax.no NM Data AS, Postbox 9090, Gronland, 0133 Oslo, Norway My opinions are those of my company