Program CALL audit trail (AREV Specific)
At 31 JUL 2000 11:15:05AM Nick Stevenson wrote:
Have a system with around 4,000 programs. There are about 5 versions of this system. I want to implement some sort of run-time audit trail where as each program is called, it will log to a file date,time,parameter values, etc and as it exits it logs the same sort of stuff. This will be used for debugging and working out the logic flow through a suite of programs.
With so many programs, I don't want to have modify & compile each of them.
Has anyone any idea of how this could be achieved within AREV 3.12?
At 31 JUL 2000 11:36AM Mike Balchin wrote:
I had asimilar problem,my solution was to write a general callng routine through which all menus, subroutines etc are processed.
Not only can it keep a history of activity but it can also manage messages, security etc.
At 31 JUL 2000 11:54AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
Pat McN developed a routine which tracked not only what was called but how long it executed so you could identify bottlenecks. I'm sure Aaron will know where it is!
World Leaders in all things RevSoft
At 01 AUG 2000 07:10AM Steve Smith wrote:
I think it was a "profiler" or somesuch. Released c. 1990 under the Advantage Program for AREV c. version 2.x
If I recall (memory fails) it slip-trapped $RTP2 (program loader)
At 01 AUG 2000 08:46AM Nick Stevenson wrote:
This term 'slip-trapped' - sounds good, haven't a clue what you mean. I like the idea of it - don't want to alter all the programs in the system! I'll do some searching, but if you have a memory-recall let me know.
Thanks all.
At 01 AUG 2000 09:38AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
It was part of the Developers Utility Series Disk 5, which is available for download at http://www.revelation.com/WEBSITE/SOFTWARE.NSF/76c3ba2a4214609785256421006d5324/f4747aeb1047084a852563fb006949eb?OpenDocument
World leaders in all things RevSoft
At 01 AUG 2000 04:20PM Steve Smith wrote:
Sorry for the jargon,
"Slip trapping" (also known as "shelling" or adding a "wrapper" routine) means you rename native AREV routines and then write your own routine handler in its place, which then calls the renamed native AREV routine.
Beware that you can lock yourself out of the system at any stage, so always do this on a copy of your application, and keep backups.
An MFS on your VOC file or program libraries can also offer similar diagnoses.