Conference azur::mcc

4537.0. "What we inherited from PHILLIPS" by FROCKY::KREMPEL (Matias Krempel - Finance DCC D.A.CH.) Fri Feb 12 1993 11:49

    Attached you will find some info on network- and system-management
    products we inherited during the acquisition of PHILLIPS.
    
    The related notes conference is 
    
    	BCFI::FBS_SRM_INFO
    
    Matias
    
             <<< BCFI::A1_BAS:[NOTES$LIBRARY]FBS_SRM_INFO.NOTE;1 >>>
                      -< SRM, System Resource Management >-
================================================================================
Note 4.2                         SRM Information                          2 of 2
BCFI::BACKLUND "Ingemar Backlund @VLB"              456 lines   5-FEB-1993 11:36
                           -< DECbank Sales Update >-
--------------------------------------------------------------------------------

System Resource Management (SRM)

Author

o Ingemar Backlund, DTN: 832-4965, E-Mail: @JAR 


Highlights

o System Resource Management (SRM) is the group of products that provide
System and Network Management in Digital's Financial Business Systems (FBS)

o SRM runs on an IBM host system with UNIX servers and PC workstations

o SRM provides the tools for effective management of complex networks,
answering the customer's need for:  

  o increased cost control 
  o superior system quality 
  o changes implemented quickly and easily 
  o a high level of security 

o SRM's System Control Centre facilities eliminate the need for technical
expertise in the branches

o The SRM products cooperate with such products as IBM NetView 


Product Description

SRM consists of a group of products providing systems management in a 
network of FBS computers.  SRM provides effective management functions from a
centrally located entity called the System Control Center (SCC). Managers 
can plan additions, moves, etc., from the SCC and make changes quickly, 
easily, securely and cost-effectively.  The SRM product group is based on OSI 
System Management and follows OSI Network Management Forum recommendations.

The SRM product group can be used in both IBM and non-IBM host 
environments. In an IBM host environment, SRM cooperates with such products as 
NetView and uses the IBM host facilities to aid the software distribution 
process by utilizing the SNA network more efficiently.  In non-IBM host 
environments, SRM can for example, distribute software directly to network 
nodes from the SCC.


The SRM products can be divided into the following functional groups:


o System Control Center

  o System Control Center/Software Package 

o Base Functions

  o Remote Execute 
  o VTAM Bridge Facility 
  o VTAM Bridge - Store and Forward 
  o PVBF Gateway 

o  Fault Management

  o Event Logging 
  o PC Event Logging 
  o NetView Gateway 
  o NetView Hardware Monitor Panels 
  o Systems Management Application 
  o System Log Analysis 

o Configuration Management (Software Distribution)

  o Software Distribution and Installation 
  o Software Installation in PC Workstations 


System Control Center/Software Package


Overall management at the SCC is provided by a set of software functions
gathered into a package called the System Control Center/Software Package
(SCC/SWP).  This is a menu-based application developed using TFM (Task 
Flow Management), the FBS 4GL development environment.  The result is central
network control via the SRM functions through an interface that is uniform, and 
easy to learn and use. 

Other types of application or function can easily be implemented in the 
SCC/SWP as the SRM products are based on OPEN standards.  At the same time, a
secure environment is provided by the ability to assign access rights to
functions on a user group basis.  The SCC also offers a channel to 
Network Management functions in an IBM host.  The NetView Gateway product in the
branches converts events to IBM format and these events can then be sent 
to the NetView system for presentation at the IBM host.  The 3270 Emulator 
can be used in the SCC to log into the host NetView system.

Each SRM function has a product in the SCC and a corresponding product in 
the branches. Between the SCC and the branches the routing function PVBF is a 
VTAM Bridge located in the IBM host.  PVBF is mainly used for software
distribution, and software can also be stored in the host for more 
efficient distribution.  All configuration data in the SCC is stored in an 
Informix database called the Management Information Database (MID).  The 
Management Information Collector (MIC) is used to collect information from the 
branches.


Base Function Products

These functions must be present when SRM is used, and are used by most of 
the SRM products.  Certain Base Functions are used only in an SNA network.

o The Remote Execute functions are:

  o Log-in on a remote node and act as a remote operator

  o Execute commands in a remote node from a local application, running in
    foreground or background, and have the output and exit status immediately 
    sent to the local node. 

o VTAM Bridge Facility (PVBF).  This is a VTAM application running on an 
IBM host with the MVS operating system.  PVBF has two main facilities:

  o Routing. PVBF/Routing realizes a network relay in the IBM mainframe,
    allowing an OSI transport connection between any two Digital nodes via 
    SNA. It is used, for example, in the SRM Remote Execute product.

  o Store and Forward. PVBF/SAF is the host component of a file transfer
    facility between an FBS node and an IBM host.

o VTAM Bridge - Store and Forward.  This combines the VTAM Bridge 
facilities described above with the Configuration Management Store and Forward 
facilities described later. The Store and Forward product is located in the IBM 
host.

o PVBF Gateway. This is a UNIX package located in the UNIX branch server. 
The PVBF Gateway cooperates with the VTAM Bridge facility in an IBM host and
supports communication over an SNA network. 


Fault Management

Fault Management is the detection, diagnosis and correction of faults 
that cause abnormal system operation.  If an error occurs in the branch,
information about this event is sent to the SCC.  The SCC operator can 
further inspect the SRM Event Log using a remote log-in, and take appropriate 
action.

o Event Logging.  This is the base for other SRM products and user
applications that want to read information from the Event Log.   Event 
Logging functions are:  

  o Collecting event messages submitted from other components 
  o Event reporting from user programs 
  o Logging of event messages 
  o Administering the event log 
  o Reading and interpreting the event log 
  o Log listing 
  o Reading and setting the event reporting mask maintained by a selected 
    set of device drivers 
  o An interface that allows user defined filtering of event messages 
    before logging. 

o PC Event Logging. This enables events to be reported via a C/TFM 
application interface in the PC workstation and sent to the Event Log in the 
server. Events can be sent further to NetView (if present).  The customer 
organisation can decide the events to be sent and specify the format of events.

o NetView Gateway.  The NetView Gateway product is inserted as an event 
filter in the SRM event logging system and interprets each event.  Important 
events are converted to IBM format and transferred to NetView in the IBM host.  
The types of event sent and the frequency with which they are sent are
customizable.  A Conversion Table Editor is used for further customization of 
the NetView Gateway.  The customer organization can also link in its own exit 
routines to perform any special interpretation and conversion of events. This 
type of customization is normally only carried out at the central site, with the
result distributed to the relevant nodes.

o NetView Hardware Monitor Panels.  These panels are located at the IBM 
host.They contain recommended actions and alert descriptions to be shown to 
the NetView operator.

o Systems Management Application (SMA).  Using SMA, standard systems 
management operations, such as get value, set value and action, can be 
performed on attributes of the managed DC projects (such as X.21 or SDLC running
on a DC control unit).  Events (such as a threshold exceeded for an error 
counter) are also received from DC managed objects and logged into the Event 
Logging system. Typical SMA operations are:  

  o reading statistical counters 
  o setting thresholds, for example on error counters 
  o receiving events when thresholds are exceeded 
  o changing configuration information 

o System Log Analysis (SLA).  SLA is a tool used to analyse the contents 
of the Event Log.  It provides the service engineer or system administrator 
with a comprehensive set of functions, such as:  

  o produce summary or detailed reports 
  o analyze the Event Log, comparing results with predefined threshold values. 
    If a threshold is exceeded, a local or remote operator can be notified. 
  o generate service event records on the System Event Log. 


Configuration Management (Software Distribution)

The main task of configuration management is to ensure system 
consistency. The distribution and installation of new software versions and 
network supervision requires considerable investment. SRM protects this 
investment by providing efficient tools for centralized control of software 
distribution and installation.

o Software Distribution and Installation (SWDI). Using SWDI software can 
be distributed from the SCC to the WAN nodes and further to nodes on 
connected LANs. Once software has been distributed in this way, it can be 
installed later. Installation can include operations such as creation, removal 
and replacement of files and directories, editing files, linking, and other
actions. Files to be changed can be saved and reinstalled later if
installation was unsuccessful. Distribution and installation are 
controlled by commands and lists in the SCC. The status of the distribution and 
installation can be requested and reported.

o Software Installation in PC Workstations. The SWDI component in the PC
workstation, connected to a UNIX server via a LAN, has access to software 
in the UNIX server via a file-sharing mechanism (for example, the SMB 
Server). When distributing software to a DOS workstation, the SCC first 
distributes and then installs the software at the UNIX server on the LAN. As 
part of the installation process, the software is queued for each PC workstation
affected. Each PC workstations examines, for example at startup, to see if any 
software is queued for it. If so, the PC retrieves and installs the software 
onto its disk then reports the result back to the SCC.   Distribution and 
installation are handled as distribution to a UNIX server for a diskless PC 
workstation in which all files reside on the UNIX server.

o Store and Forward (SAF). The SAF function is a file transfer facility
between FBS nodes and an IBM host. Files (datasets) are stored as 
sequential files on the host and the VTAM Bridge Facility is used to 
store/retrieve the files. The SAF commands in the FBS node enable files to be 
stored, retrieved, deleted or listed. The SAF facility can be used together 
with SWDI for more efficient parallel distribution. SAF can be used to store 
Digital software in the IBM (or MVS compatible) host. The FBS nodes in the WAN 
will later retrieve the stored software under the control of the SCC. 




Main Features


o Excellent application distribution to the complete FBS network.

o Global supervision and monitoring of local systems, transparently to 
the network users.

o Efficient central control via the System Control Center menu-based 
application. 


Operating System Platforms

SRM Release 3.4 runs under AT&T UNIX and SCO UNIX. The following SRM Release 
3.3 products have not been ported to the SCO environment.

o Response Time Package 
o Preventive Maintenance Reminder Tool (PMRT) 
o System Control Center/Software Package (SSC/SWP) 

RTP and PMRT will be ported to SCO UNIX on request. SCC/SWP has not been 
ported as it is based on TFM Release 2.5 which is not available on the SCO UNIX
platform. SRM products in a Control Center must be configured to run on
AT&T UNIX while those in the branches can run under SCO UNIX. SRM products
configured in this way can communicate freely with each other.


Hardware/Software Requirements

Hardware requirements:

DOS PC                             IBM PC (or 100% compatible) 
                                   Ethernet network TCP/IP or OSI                                   




UNIX branch server                 Intel-based hardware
                                   LAN Ethernet
                                   WAN X.25, X.21, V.24, SNA

System Control Center              P9000i series with WAN/LAN support
                                   
IBM host                           Hardware supporting IBM 370 assembler
                                   instruction set

Software requirements:                                                   

DOS PC                             MS-DOS Release 3.3 or later
                                   MS-Windows Release 3.0 or later
                                   SMB Server or compatible (PATHWORKS)
                                   TFM Start
                                   
UNIX branch server                 AT&T or SCO UNIX
                                   SMB Server or compatible

System Control Center              AT&T UNIX
                                   
IBM host                           VTAM Release 2 or later
                                   MVS/SP Release 1.3 or later


Software Licensing

SRM is available under traditional licensing.


Ordering Information

All prices are in USD.

o SRM System Resource Management  Version 3.4

Software licenses:

  Order number		Description			Price
  QL-0DGAW-AA		SRM Remote Execute SCO		  350
  QL-0DHAW-AA		SRM PVBF Gateway SCO		  150
  QL-0DJAW-AA		SRM Event Log SCO		  500
  QL-0DKAW-AA		SRM NetView Gateway SCO		  500
  QL-0DLAW-AA		SRM Systems Management SCO	  175
  QL-0DMAW-AA		SRM System Log SCO		  175
  QL-0DNAW-AA		SRM Software Distribution and
	  		Installation SCO		  500
  QL-0DPAW-AA		SRM Store and Forward SCO	  325
  QL-0DSAW-AA		SRM PC Event Logging SCO	  500
  QL-0DQAW-AA		SRM Software Installation in 
			  the PC Windows		  100
  QL-0DRAW-AA		SRM Event Logging Windows	  100

Media and distribution:

  Order number		Description			Price
  QA-0DGAA-HC		SRM RX23 Kit			  265

Distribution package:

  Order number		Description			Price
  QB-0DTAA-AA		SRM SCO Distribution Package	3,640

The distribution package contains one SRM RX23 Kit and one each of the 
following licenses:

  o SRM Remote Execute SCO
  o SRM PVBF Gateway SCO
  o SRM Event Log SCO
  o SRM NetView Gateway SCO
  o SRM Systems Management SCO
  o SRM System Log SCO
  o SRM Software Distribution and Installation SCO
  o SRM Store and Forward SCO
  o SRM Installation in the PC Windows
  o SRM Event Logging Windows
  o SRM PC Event Logging SCO

For large volumes, license packages (QP-00CAA-**) are available. These packages 
contain one server license for every five workstation licenses and are defined
for projects of up to 10,000 workstations. Prices range from 39,663USD (for 50 
workstations) to 1,887,500USD (10,000 workstations). Please refer to the price 
list for further details of package sizes and prices.

o SRM System Control Center  Version 3.4

Software licenses:

  Order number		Description			Price
  QL-0DUAW-AA		SRM System Control Center
			  Testsite			 4,000
  QL-0DVAW-AA		SRM System Control Center
			  1-40 nodes			13,000	
  QL-0DWAW-AA		SRM System Control Center
			  1-100	nodes			26,000
  QL-0DXAW-AA		SRM System Control Center
			  1-200	nodes			40,000
  QL-0DYAW-AA		SRM System Control Center
			  1-400	nodes			65,000
  QL-0DZAW-AA		SRM System Control Center
			  1-1000 nodes			85,000

Media and distribution:

  Order number		Description			Price
  QA-0DUAA-HC		SRM System Control Center 
			  Testsite AT&T UNIX		  350

o SRM PVBF Version 1.2:

Software licenses:

  Order number		Description			Price
  QL-0E0AX-AA		SRM PVBF MVS			22,000

Media and distribution:

  Order number		Description			Price
  QA-0E0AA-HP		SRM PVBF MVS 6250 PBI		  215

o SRM PVBF Store and Forward  Version 1.2:

Software licenses:

  Order number		Description			Price
  QL-0E1AX-AA		SRM PVBF SA MVS			35,000

Media and distribution:

  Order number		Description			Price
  QA-0E1AA-HP		SRM PVBF SA 6250 BPI		  215

o SRM NetView Panels Support  Version 1.0

Software licenses:

  Order number		Description			Price
  QL-0E2AX-AA		SRM NetView Panels MVS		4,500

Media and distribution:

  Order number		Description			Price
  QA-0E2AA-HP		SRM NetView Panels MVS 6250 BPI	  160


Availability

SRM Release 3.3 and SRM Release 3.4 are available now. 


Resources and Further Information

o  SRM, 			SPD 44.21.00
   SRM System Control Center, 	SPD 45.17.00
   SRM PVBF, 			SPD 45.18.00
   SRM PVBF SA			SPD 45.19.00
   SRM NETV PN			SPD 45.20.00


o  SRM data sheets, presentation material and scripts are available through 
Digital Equipment AB BCFI, DTN: 832-4600, or directly through the author.

o  The notes conference STAKI1::FBS_COMPETITION contains current information 
about the competition in the Retail Banking market.


Services

Professional services are available worldwide. These include project 
management, writing functional specificiations, software customization, and 
sales support.

Contact: Gunnar Wikman, DTN: 832-4786, E-Mail Gunnar Wikman @JAR