Kbase P125471: How to monitor OCX calls using -clientlogging and -logentrytypes.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/06/2009 |
|
Status: Verified
GOAL:
How to monitor OCX calls using -clientlogging and -logentrytypes.
GOAL:
How to record OCX calls using -clientlogging and -logentrytypes.
GOAL:
Can I track OCX or COM object calls made from a 4GL / ABL session?
GOAL:
How to monitor COM calls using -clientlogging and -logentrytypes.
GOAL:
How to record COM calls using -clientlogging and -logentrytypes.
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
FIX:
When using the startup pareameter -logentrytypes ProEvents.Other in conjunction with the -logginglevel parameter of 2 to 4 OpenEdge will record some COM related messages in the client log file.
Setting -logginglevel 2 as a startup parameter for the client turns on logging of COM, Async, and Socket events.
At logging levels 2 and 3 OpenEdge logs COM events only when the application defines a trigger for the event, on the assumption that you are interested only in events for which you havewritten a trigger.
At level 4 (Extended), OpenEdge logs all COM events.