Activity log debugging support

There are different ways debugging an activity log. Activity log debugging support is not a replacement for using program language debugger (C++, OSI), but provides some support in combination with those debuggers.

One possibility is setting a step number in the ACTIVITY_LOG section, which allows processing a number of activity log lines. One may also use the pause action

More comfortable is the the break point feature. Break points may be set by editing the log file and replacing ':' between action type and action name (...S:SetText ...) by '#'(...S#SetText ...). Now, replay will stop before executing the activity. In order to continue, the replay application needs the focus. Pressing the enter key will continue replaying until next break point.

The program allows splitting a multiple session activity log file into separate user or session files (by process id). The program is called as

SplitActionLog path oper [name]

• path - is the activity log file path.

• oper - is the requested operation :

• u[ser] - split by user name

• s[ession] - split by session number (process id)

• name- contains the session number or user name for lines to be filtered in the activity log.

When not passing a name, a file is greated foe each user (and session, in case of session operation) in the same directory as path.user[_session].ext (when path.ext was the file name for the original activity log file