Re: startlog() messages

In article <Cxxs8G.64z@cix.compulink.co.uk>, akent@cix.compulink.co.uk ("Andy Kent") writes: |> > We have a set of programmes that call startlog(filename) at the start. |> > This is to track Informix errors, that users are not bothered to less us |> > know. |> > > The problem is that sometimes the info in the logfile is not |> > comprehensive |> > enough. It does not tell which executable it came from. |> > > eg : |> > > Date: 14-10-94 Time: 17:03:41 |> > Program error at "nextnum.4gl", line number 43. |> > SQL statement error number -244. |> > Could not do a physical-order read to fetch next row. |> > SYSTEM error number -107. |> > ISAM error: record is locked. |> > > Unfortunately "nextnum.4gl: is a function called by various |> executables. For logging, have each executable reference a unique filename. For example, the executable "prog1" uses: STARTLOG(prog1.log) and executable "prog2" uses: STARTLOG(prog2.log) You will be able to tell which executable bombed by the log that contains the error message. -- ################################################################################ | Dwan Norwood | Denver, Colorado | Voice: (303) 488-7696 | | The Alert Centre | The Mile High City | Email: dnorwood@alert.com | ################################################################################ # "You can get a lot more done with a kind # # word and a gun than with a kind word alone." # # - Al Capone - # ################################################################################