Searching powerterm history ...

[ChaimBu]

Good morning !!

Perhaps I should have appended this thread to a former thread I had opened last week regarding using powerterm as a console, but I felt that it was better to open a new thread.

The managers here are becoming more and more interested in the possibility of connecting PCs and using powerterm as a console. They have asked me to research the following:

1. Is it possible to search the history? I do not see such an option, but that doesn't mean it isn't there!

2. If it isn't possible to search the history, is it possible to save the entire history as it is at any given moment to a text file on the PC, and this can of course be searched.

Thanks,

Chaim

[Wim Van den Wyngaert · Accepted solution]

In the User Guide :

Option menu.

Start/Stop Trace

Stores the session in a log file. Raw data is stored in the Capture.log file, while formatted data with readable escape sequences is stored in the Trace.log file. This option changes to Stop Trace once the Start Trace option has been activated.


This is without timestamps, no archiving cleanup, etc as console manager would do.

And probably overwrites the previous version on restart. So you have to handle all that yourself

Wim (never used powerterm)

[Ian Miller.]

Chaim, you probably want to look at console manager products as trying to implement this on the cheap using powerterm history will cost you more in people time and inefficiency.

[Dean McGorrill]

hi Chaim,
First I'm glad your system manager is
thinking of moving away from the paper! The
powerterm capture.log, trace.log are not
very pretty. if your looking for the logs
some of it gets written into c:\ptw525 on
the pc, at least thats where mine does.
PuTTY has logging to. I havn't tried it.
I'm with Ian, finding some console management software might be easier.

Dean

[Dean McGorrill]

Chaim,
I just tried PuTTY, and its logging
is very good. click session logging, then
click printable output, then click back
to session and connect. the default output is putty.log. there are options to always
append or over write. Hope this helps

Dean

[Andy Bustamante]

For what it's worth, Procomm also has logging and includes a scripting language. You should be able to start logging and have scripted aging of log files.

Epsilon, http://www.lugaru.com, is an editor that includes the ability to create sessions to a comm port and telent sessions. Using control sequences is a bit odd, but very useful for capuring terminal sessions.

Andy

[Hoff]

TDI ConsoleWorks or one of the various other available console management packages is to be recommended and encouraged here, particularly over approaches based on PowerTerm or PuTTY. These options are nice *terminal* packages, not *console* packages.

From the OpenVMS Frequently Asked Questions ( http://64.223.189.234/node/1 ), here are some of the available options:

14.3.8 Console Management Options

Options to collect multiple consoles into a single
server are available, with both hardware options and
software packages that can provide advanced features
and capabilities.

Some of the available console management options for
OpenVMS:

o Heroix: http://www.robomon.com/

o KI Products: http://www.ki.com/products/clim/

o Global Maintech: http://www.globalmt.com/

o TECsys: http://www.tditx.com/

o CA: http://www.cai.com/products/commandit.htm

Computer Associates is the owner of what was once
known as the VAXcluster Console System (VCS) console
management package, and has integrated this capability
into the CA management product suite.


--