Re: SP URGENT HELP: SYSTEM .. to keep a log file
Posted in 1996
In message <199611280856.AA154661395@amsoas.nl.dhl.com>, Scott Hanson <shanson@ams-co.nl.DHL.COM> writes }Operating System: HP-UX B.10.01 A }X-Mailer: Elm [revision: 111.1] } }> }> I am using SP for Client Server application. }> In order to monitor and check the update procedures I need to log the }> progress in a unix text file. e.g.: }> }> SYSTEM "echo "||text||" >> log_file"; }> }> This command takes too long top process, cca. 1sec !!!!!! }> }> Is there a better way of achieving the same goal. }> }> Please HELP }> -- }> george@icc-gcp.demon.co.uk }> } }You could try to use TRACE from withtin the SP, but this does inhibit }performance. } }set debug file to 'log_file'; } }... } }trace on; }trace "text"; } }you will get other information as well, but you could filter it out. } }just a suggestion :-) } }Scott }-- }Scott Hanson Junior Consultant scott@worldaccess.nl }NexTime B.V. Database & O/S Technology work: (31) 10 207 5400 Hi, I have received two suggestions (many thanks for comunicating): 1. use a DB table as a log file: - problem with this solution is, that if database crashes or gets corrupted there is no trace of update history 2. use trace on function: - this works OK, but the log file gets overwritten each time the trace is started. I would have to have a separate log file for each updadte run and each function. I am looking for a similar function to that in 4GL errorlog(...) Many thanks for the efford and hope to hear more ideas. -- George C Parobek