"h" is short for "halt", however I would advise against using "halt" and stick to "h".

The reason?

Glad you asked...

...a nameless soul some years ago used to type in all COS command in full. Unfortunately, one day, he happened to be logged into the IBM he was working on - as root - and typed in "halt", thinking he was in Caché (actually MSM at the time) ...but he wasn't - he was at the # (root user) prompt in AIX and the halt command proceeded to stop the whole IBM immediately. Were this Caché it may have recovered easier but it wasn't and the databases ended up like swiss cheese - just a warning folks

Assumedly, you also may only want to see "new" additions to the log file. My thoughts on this would be as follows;

Method 1 - Using COS code throughout

1. Take a snapshot of the existing ens.log/cconsole.log, loading it into Cache as an Object/Global
2. Every "n" seconds, rescan the existing log file.
3. If new lines have appeared report them, write to text file, email, text etc. them
4. Goto step 1

Method 2 - Using OS tools

1. Take a snapshot of the existing log file into a copy text file
2. Every "n" seconds, use an OS tool to compare this file with the current log file (e.g. diff in Unix etc.)
3. If different, report the differences, write to text file, email, text etc. them
4. Goto step 1

If you really only want "...to write the event log to the text file..." then you can either use COS or a simple copy command at the OS level to copy the log file to another text file