Conference csc32::consolemanager

712.0. "ENS Logs multiple events against one scan entry" by WOTVAX::FLACKI ("One Mail Short of a Full Inbox") Fri May 05 1995 13:20

        
        I don't know if I have worded the title correctly, so let me 
        explain...
        
        I have a BT Monarch telephone exchange with a data logger port 
        (output only) running at 1200 baud.
        
        I connected this to VCS (TXA7) as I need to log all of the 
        information sent out by this thing. In particular I need 
        events raised if there is an outgoing call (indicated by an 
        'O' at the start of the line), or a call that failed to get 
        through (indicated by an 'F' at the end of a line).
        
        This was working fine until I upgraded to PCM. I then found 
        that the output of each line in a CONSOLE MONITOR was not 
        terminated with a CR/FF and so, there was a continuous stream 
        of data on only one line of the terminal.
        
        To fix this I found that I needed to set the terminal to 
        NOECHO - Why ????
        
        While I was fixing this, and to date, if an outgoing call is 
        made ENS will continuously flag an outgoing call event. 
        Incoming failed calls are much the same however the 
        notification system works fine for a while (2 for three calls) 
        and then it appears to loop, flagging the event continuously.
        
        PCM V1.5 (MUP).
        
        Can anyone help ? 
        Thanks in advance,
        Ian.
        
        Listings below...
        
$ show term txa7
Terminal: _TXA7:      Device_Type: Unknown       Owner: No Owner
   Input:    1200     LFfill:  0      Width:  80      Parity: None
   Output:   1200     CRfill:  0      Page:   24      
Terminal Characteristics:
   Interactive        No Echo            No Typeahead       No Escape
   Hostsync           TTsync             Lowercase          No Tab
   Wrap               Scope              No Remote          Eightbit
   No Broadcast       No Readsync        No Form            Fulldup
   No Modem           No Local_echo      No Autobaud        No Hangup
   No Brdcstmbx       No DMA             Altypeahd          Set_speed
   No Commsync        Line Editing       Overstrike editing No Fallback
   No Dialup          No Secure server   No Disconnect      Pasthru
   No Syspassword     No SIXEL Graphics  No Soft Characters No Printer Port
   Numeric Keypad     No ANSI_CRT        No Regis           No Block_mode
   No Advanced_video  No Edit_mode       No DEC_CRT         No DEC_CRT2
   No DEC_CRT3        No DEC_CRT4        No DEC_CRT5        Ansi_Color
   VMS Style Input

$console edit /inter=char
POLYCENTER Console Manager
Character Cell Editor Version V1.5-006
Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved

>show system btexch
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT): 
System Name         = BTEXCH
    Information     = BT Monarch Exchange
    Connection      = Direct connection
    Terminal Device = TXA7
    Terminal Speed  = 1200
    Scan Profile    = BTMONARCH    BT Monarch Exchange
    Icon filename   = DEC_EXPANSION.XBM
    Console line    = Disabled
    Logging is enabled, directory = CONSOLE$LOGFILES

>show scan btmonarch
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT): 
Scan Name       = BTMONARCH
    Information = BT Monarch Exchange
    Events (2)
      BT$CALL_FAILED     BT Call Failed - User Hung Up
      BT$OUTGOING_CALL    User Has Made Outgoing Call
    Scans (0)

>show event bt$call_failed
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT): 
Event Name      = BT$CALL_FAILED
    Information = BT Call Failed - User Hung Up
    Class       = BTCF
    Subsystem   = VAXcluster Console System
    Text        = F
    Text string = Literal (exact pattern match)
    Start       = 0
    Count       = 1
    Priority    = Warning

>show event bt$outgoing_call
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT): 
Event Name	= BT$OUTGOING_CALL
    Information = User Has Made Outgoing Call
    Class       = BTOC
    Subsystem   = VAXcluster Console System
    Text        = O
    Text string = Literal (exact pattern match)
    Start       = 0
    Count       = 1
    Priority    = Warning

$ console extract btexch
POLYCENTER Console Manager
Extract facility Version V1.5-006
Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved


Working ... 
 * DDMMYYTimeDuratnPort1Port2 TTA1Trans TTA2Dig  Durat2 or Dig    MeterAccount
 IN01059515280000053498C3300E 0002          3300F      
 ON01059515520000163498C0007T               9842708                    
 IN01059518250000033498C3300E 0001          3300F      
 IN01059518250000043498C3300E 0001          3300F
 done.

Hi,
   we had a known bug in V1.5 where a single character event would continualy 
trigger ENS. this is fixed in V1.6 which is currently in field test. You are
welcome to pull the FT kit and use it ( in fact we hope to ship an updated kit
today).

You may also wish to consider using the regular expression matching facility
to make your searching better.

Example:

To match on start of line: ^O and set event to Regular rather than Literal

To match on end of line:    F^ and set event to Regular rather than Literal

In fact this may also stop your problem of retriggering in V1.5 (but don't quote
me on that).

>    To fix this I found that I needed to set the terminal to 
>    NOECHO - Why ????
 
Why was the terminal set to ECHO anyway??

Cheers Simon...

        Simon,
        
        Many thanks for your quick response. I have been working on 
        this for days !!!
        
        The echo appears to set by default.
        
        Thanks agian,
        Ian.