Browse Prior Art Database

Validating LAN Server Generic Alert Definition Keywords

IP.com Disclosure Number: IPCOM000105778D
Original Publication Date: 1993-Sep-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 6 page(s) / 189K

Publishing Venue

IBM

Related People

Arkeketa, WW: AUTHOR [+4]

Abstract

Disclosed is a set of rules governing the input of certain keywords and associated parameters used to generate generic alert tables that can be used to build LAN Server* (LS) generic alerts. The content of the generic alert tables file are described at the end of this disclosure.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 23% of the total text.

Validating LAN Server Generic Alert Definition Keywords

      Disclosed is a set of rules governing the input of certain
keywords and associated parameters used to generate generic alert
tables that can be used to build LAN Server* (LS) generic alerts.
The content of the generic alert tables file are described at the end
of this disclosure.

      When a file contains keywords and associated parameters that
are intended to relay information to the system, then that set of
keywords and associated parameters need to be validated to some
extent before utilizing the information.

The following is a set of simple rules regarding different aspects of
the file's syntax.

     o   A comment line begins with ";".   Everything following the
         ";" is ignored.  The ";" can appear anywhere on the line.
         Blank lines are also ignored.

     o   "Blank" is used as a separator character.  The left and
         right parenthesis and comma are also used when defining the
         MSG: keyword parameters (see MSG: keyword below for more
         details).

     o   Each KEYWORD must be on the same line with all of its
         corresponding parameters.  Multiple keywords can be on the
         same line as long as all parameters associated with the
         keywords are also on that line.  Only the MSG: keyword and
         its related message IDs can span more than one line.

     o   Each code point must be expressed as 1-4 hexadecimal digits
         (i.e., 0-9, A-F).

The following is an overview of the keywords used to define generic
alerts and specific rules associated with each one.

     1.  MSG:   msgid (1-n)  or  msgid(subid,index) (1-n)

         a.  The message ID should exist in a message file (i.e.,
             NET.MSG), but this is not enforced, so that it is
             possible to generate generic alerts from a FFST/2
             message control block without a "real" message or
             message file existing.  The generic alert could be
             generated, but the associated message data would be
             rejected by FFST/2.  On the other hand, the
             I_NetLanProbe internal API has a "build alert only"
             interface that could be used with this approach.

         b.  Each message ID must be expressed as 4 decimal digits
             (0-9).  Leading zeroes are required.

         c.  Each subid must be expressed as 1-3 decimal digits.

         d.    Each subid must be preceeded by a left parenthesis and
             followed by a comma.

         e.  The index must be expressed as one decimal digit (0-8).

         f.  Each index must be preceeded by a comma and followed by
             a right...