Conference csc32::consolemanager

Roberto,

  The 2 steps you have should work. Why does this not solve your
  problem? Can you give an example of where it doesnt work i.e.
  what is your event definition, what does the line of console
  output look like.

Cheers,
Phil

Hi Phil,
thanks for your cooperation.
This is the situation:
if my customer has scanning on the screen this sentence:

   SECURITY: Penetrazione intruder su SYSMAN.

This is the event definition:

Event name:  Security
Class:       Sect
Subsystem:   VAX Cluster console system
Information: Alarm intrusion

When occurs the event Security, his display has truncated after SECURITY:
Regards,
       Roberto.

Hi,
   plase post ALL the event attributes.

I.e. 
Text to Scan for:
Regular: Y/N
Start:
Count:

Cheers Simon....

Hi Simon,
here are other attributes of that event (excuse me if they were incomplete):

 Context start  = 1
 Context count  = 1
 Event priority = warning
 both Literal than Regular Extension show the error.

Regards,
       Roberto.

  Yes, but, What is the "Event Text" attribute set to????

Cheers,
Phil

Hi Phil,
my customer affirms the "Event Text" attribute has setted to 'Literal String',      
but also setted in 'Regular Expression' shows the same failure.
Regards,
       Roberto.

Roberto,
        I think we are still at Crossed Purposes. 

The event text is the actual string you wish to scan for. Not whether
it is literal or not.

An example of an event below:

Event Name:  CNXMAN
Info:        OpenVMS Connection manager Message
Text:        %CNXMAN,
Class:       Cluster
SubSystem:   Op sys
Regular exp: N
Start:       0
Count:       1
Priority:    Minor

The Text field here is the straight Literal string %CNXMAN, as soon
as that is seen on the console the event is triggered.

Just changing to a regular will make no difference as it string in 
the Text field does not contain Meta Characters.

If the text was changed to:

Text:        %CNXMAN,*^
Regular exp: Y

Here the event will be triggered by the %CNXMAN, followed by any 
characters terminated by a Line feed. I.e not until the full line
of text has been received.

The "*" is a multicharacter wildcard
The "^" is Line feed.

Hope that clarify things for you.

Cheers Simon...

Hi Simon,
these are all attributes:

Event Name: SECURITY
Info      : Alarm intrusion
Text      : SECURITY:
Class     : Sect
Subsystem : VAX Cluster console system
Start     : 1
Count     : 1
Priority  : warning
  
Regards,
       Roberto.

Roberto,
        now I understand what you see.

As the scan text is just SECURITY: as soon as the ":" is
seen the event is triggered. The ENS process will probably 
process this before the rest of the line of text has appeared
on the console.

By changing the event so that the text is:

Text     : SECURITY:*^
and changing the event type to Regular Exp the event will not trigger 
until the end of the line.

Hope this helps.

Cheers Simon....

Hi Simon,
thanks for your suggestion, but unfortunately also this last doesn't
solve the problem, that isn't systematic but random.
Also other events, without ':' character termination show the same
problem.
An opinion of my customer (he has worked for 5 years with VCS SW product
and now he is testing PCM to substitute VCS) is that PCM is maybe slower
compared to high speed of his Alpha system, an Alphastation 200 model
4/233.  
Regards,
       Roberto.

Roberto,

  Lets start again...

  1) Have you read the user guide, in particular the part about
     regular expressions?

  2) Does changing your event so that when you use the following
     commands in the character cell editor you get the output
     shown below...

PCM Edit> show event SECURITY
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
Event Name      = security
    Information = Alarm intrusion
    Class       = Sect
    Subsystem   = VAX Cluster console system
    Text        = SECURITY:*^
    Text match  = Regular Expression (token match)
    Start       = 1
    Count       = 1
    Priority    = Warning
PCM Edit>


    PLEASE NOTE THE *^ characters on the end of the Text string
    and the Text match set to regular expression!!!

  3) Have you made the same change to the other events causing
     you a problem (added the *^ to the text field and changed
     the event to a regular expression).


  4) It is IMPORTANT that you read the manual regarding regular
     expressions because if your original text string contains one
     of the regular expression meta-characters YOU WILL NOT get
     your event detected.

  Finally, get your customer to install V1.6, we believe it performs
  better than V1.5, in any case, your customer should see MUCH better
  performance from his Alpha running PCM than a VAX running VCS.

Cheers,
Phil

Hi Phil,
following your suggestion, my customer will install PCM 1.6.
Thanks a lot for you hints.
Regards,
       Roberto.