Re: startlog() messages
Posted in 1994
> : The problem is that sometimes the info in the logfile is not comprehensive > : enough. It does not tell which executable it came from. > > Our convention is to use a different errlog file for each executable; this > elimates any confusion. For instance, you could use the following code in > each program: > > LET log_file = arg_val(0) clipped, ".log" > CALL startlog(log_file) And we append the user's $LOGNAME too, so we know who to ask if we need to know what they were doing to make the the program died. BTW: You might want to massage arg_val(0) if it could be a long pathname. --------------------------------------,------------------------------------- Kerry Sainsbury, kerry@kcbbs.gen.nz | THE INFORMIX FAQ Quanta Systems, Auckland, New Zealand | kcbbs.gen.nz:/informix/* | mathcs.emory.edu:/pub/informix/faq/* +64 9 377-4473 (work) 276-5546 (home) | quasar.ucar.edu:/?