Conference csc32::consolemanager

Ollie,

  Exactly which text triggered the false alarms?

  I just tried this with my version of your regular expression and it
  worked OK for me.

  My version is...

#31[0-9,A-F][0-9,A-F]#[P,S,T]*#[0-9]*^

  I simplified this by not doing the extra character checks on "Permanent,
  Temporary and Statistics" although I think what you were doing is
  entirely legal.

  Note the use of the # character for whitespaceand yes [0-9,A-F] is
  legal, in fact it is necessary to achieve what you want, that is
  detect hex values. Also, I havnt tried it in your case, but the ^
  character can be used for match on start of line, doing this would
  convert my form of the regular expression to...

^#31[0-9,A-F][0-9,A-F]#[P,S,T]*#[0-9]*^

  Using my form of expression I could get this to generate an event on your
  " FSAS01    31.10.94 05:03:58" line although I didnt try with your
  expression.

Cheers,
Phil

    
    Phil,
    
    Thanks alot again. I'll try with your expressions. 
    
    -Olli
    

    
    Well,
    
    When I used character cell interface lot of strange things happend.
    For example terminal server names changed to uppercase, some system
    names which were included in filters changed to upper case.
    Actually I had to restore my PORT file.
    
    But now PCM is working and here is some results for regular expression
    First there is 3 events and then there is output of action routine
    which echoed event name and text. As you see there is strings which
    should be there.
    
    For example for expression  #31[0-9,A-F][0-9,A-F]#Permanent#[0-9]*^
    
    when i send message "  31.F  Permanent    2"
    action was launched.
    but when message    "  311. Permanent   2"
    didn't launched action.
    
    As you seen the last match for numbers 0-9 didn't work either.
    
    I am running PCM V1.5 ECO 1 on ULTRIX V4.3A.
    
---
DELETE_EVENT:
    NAME: as400_diskerr1
END:

ADD_EVENT:
    NAME: as400_diskerr1
    INFO: as400 disk error
    TEXT: #31[0-9,A-F][0-9,A-F]#Permanent#[0-9]*^
    CLASS: as400_critical
    SUB_SYSTEM: as400
    REGULAR_EXPRESSION: Y
    START: 0
    COUNT: 1
    PRIORITY: CRITICAL
END:

DELETE_EVENT:
    NAME: as400_diskerr2
END:

ADD_EVENT:
    NAME: as400_diskerr2
    INFO: as400 disk error
    TEXT: #31[0-9,A-F][0-9,A-F]#Temporary#[0-9]*^
    CLASS: as400_critical
    SUB_SYSTEM: as400
    REGULAR_EXPRESSION: Y
    START: 2
    COUNT: 4
    PRIORITY: CRITICAL
END:

DELETE_EVENT:
    NAME: as400_diskerr3
END:

ADD_EVENT:
    NAME: as400_diskerr3
    INFO: as400 disk error
    TEXT: #31[0-9,A-F][0-9,A-F]#Statistics#[0-9]*^
    CLASS: as400_critical
    SUB_SYSTEM: as400
    REGULAR_EXPRESSION: Y
    START: 2
    COUNT: 4
    PRIORITY: CRITICAL
END:

Tue Nov  1 07:50:03 EET 1994 as400_diskerr1 310A   Permanent   9
Tue Nov  1 07:50:16 EET 1994 as400_diskerr1 31.A   Permanent   9
Tue Nov  1 07:51:28 EET 1994 as400_diskerr1 31.1   Permanent   9
Tue Nov  1 07:53:03 EET 1994 as400_diskerr1 31.1   Permanent   9
Tue Nov  1 07:53:15 EET 1994 as400_diskerr1 31.1   Permanent   9
Tue Nov  1 08:03:52 EET 1994 as400_diskerr1 3111   Permanent   9
Tue Nov  1 08:03:58 EET 1994 as400_diskerr1 3111   Permanent   9
Tue Nov  1 10:45:43 EET 1994 as400_diskerr1 31Z1 Permanent 1
Tue Nov  1 10:46:08 EET 1994 as400_diskerr1 3122    Permanent 1
Tue Nov  1 10:46:46 EET 1994 as400_diskerr2 3122   Temporary     sgsg 1
Tue Nov  1 10:50:15 EET 1994 as400_diskerr1 3122     Permanent  3     ss
Tue Nov  1 10:50:46 EET 1994 as400_diskerr1 31.2     Permanent  3
Tue Nov  1 10:51:13 EET 1994 as400_diskerr1 3112     Permanent  k
Tue Nov  1 10:51:17 EET 1994 as400_diskerr1 3112     Permanent  .
Tue Nov  1 10:52:42 EET 1994 as400_diskerr3 3112     Statistics 2
Tue Nov  1 10:56:51 EET 1994 as400_diskerr3 s  3112     Statistics 2
    
    
     

Ollie,

  Yes, the character cell editor is full of problems, we would
  prefer that people use the DECwindows editor whenever possible.

  Anyway, back to your problem, I will take another look at what
  you are doing, but it will have to wait until next week I am
  afraid.

Cheers,
Phil

    
    Phil,
    
    	Have you had time to check this problem?
    
    	-Olli
    

Ollie,

  I am real sorry, no I havnt, there is only me on the team
  at the moment, (Dave doesnt have the resource to look at
  this) the rest of the team (Simon) is on holiday, so,
  dealing with development for the next release, putting
  patches together and answering IPMT cases doesnt leave
  me a lot of time! Fortunately Simon returns at the end
  of the month, so we can get moving on this again.

  I havnt forgotten, it is on my to-do list.

Cheers,
Phil

Olli,
       Im back from leave and I shall have a look at this one today.

Cheers Simon..........

To the World,
             yes what Olli found was a bug. We have a fix he is going to check
for us. It was a bit of an obscure one that one.

The fix will be in the next ECO kit.

Cheers Simon......

    
    To the PCM engineering,
    
    New image works as it should with reg exp. Now we and one customer gets
    correctly AS400 disk error events. 
    
    thanks,
	-Olli
    

Olli,

  Thanks for your patience while we resolved this for you.

  This fix will be in everyones Christmas stocking (it will be part of the 
  MUP kit).

Cheers,
Phil