Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Register for and Process Alarms to Alerts

IP.com Disclosure Number: IPCOM000113640D
Original Publication Date: 1994-Sep-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 6 page(s) / 173K

Publishing Venue

IBM

Related People

Baier, KJ: AUTHOR [+2]

Abstract

This invention provides a way for a customer to initialize their network from a host system to detect alarm information, establish additional alarm filters in a network and convert the alarms selected into SNA alerts. It also provides a way to control the product from a host using runcmds (runcmds are Remote Operation commands) via Remote Operations (another product).

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

Register for and Process Alarms to Alerts

      This invention provides a way for a customer to initialize
their network from a host system to detect alarm information,
establish additional alarm filters in a network and convert the
alarms selected into SNA alerts.  It also provides a way to control
the product from a host using runcmds (runcmds are Remote Operation
commands) via Remote Operations (another product).

      This invention interacts with the Remote Operations (ROPS)
product to support the registration of filters on a network that is
attached to the host via a workstation that is also attached to the
Local Area Network.

      An interface is supported at both the host and at the local
workstation.  The commands covered below are sent to the workstation
from the host with the ROPS runcmd.  The commands are also supported
at the command line interface.  The local workstation interface is
referred to as a command line interface.  Command line commands are
entered locally at the workstation.  At the command line, each
command is preceded with "tiecli".  At the host, the commands are
preceded with the runcmd.

Example starting LAN NetView Tie* from OS/2*:

  start tie <parameters>

Example issuing a Tie command from OS/2:

  tiecli <commands & keywords>

Example starting Tie from the host:

  runcmd sp=puname appl=remoteop op=<operator id>; start tie
<parameters>

Example issuing a Tie command from the host:

  runcmd sp=puname appl=tie op=<operator id>; <tie commands>

This invention parses, syntax checks the command and issues the
command to the LAN NetView Manage* product XMP interface.  It also
maintains a history of sieves registered for use in reconfiguration
after a stop and restart.

Commands supported:

  REGISTER, DEREG, STOP_NORMAL, STOP_IMMEDIATE, START TIE

The commands syntax:
  1.  REGISTER dnnetid=netid dnsysid=sysid classoi=object_identifier
      typeoi=object_identifier instnetid=netid instsysid=sysid
      instoi=object_identifier instid=product_id time=begin&end
      freqnum=frequency_threshold freqperiod=seconds
  2.  DEREG this the same as the REGISTER command.
  3.  STOP_NORMAL
  4.  STOP_IMMEDIATE
  5.  START TIE <op:operator_id> <tiebase>

Keyword Reference

The following keywords are supported in the REGISTER and DEREG
commands:
   DNNETID
   DNSYSID
   TIME
   INSTNETID
   INSTSYSID
   INSTID
   INSTOI
   FREQNUM
   FREQPERIOD

The program displays an error message for unrecognized keywords and
ignores the command.

  DNNETID & DNSYSID Keywords

      Use the DNNETID and DNSYSID keywords to specify the workstation
network address for the event sieve you are registering, for example:
     DNNETID = NETID
     DNSYSID = SYS06

      The address identifies the node where the program is to create
the event sieve.  Supported values are network_id and system_id for
the remote node, or nothing indicating the sieve is to be created on
the loc...