Conference azur::mcc

DECmcc V1.2 has the ability to launch loosely coupled applications from
it's iconic map interface.  These applications appear as pushbutton
entries in the "Applications" pulldown menu.  The DECmcc Iconic
Map can pass information to the launched application via a
datafile.  The datafile, produced in the user's current directory,
contains the following DECmcc map window context information:  domain,
map file name, and all selected entities.  Once the application is 
launched, it is independent of DECmcc V1.2. 

To launch the HUBwatch application, the user MUST define the environment
variable NMS_DIR in the window from which the DECmcc Iconic Map is
invoked to point to the top_level directory in which the HUBwatch
software has been defined.  In further example, I will assume the 
HUBwatch top_level directory is /usr/mcc/hubwatch. 

The user can add the DEC HUBwatch application to their DECmcc map 
window by modifying their private mcc_resource.dat file as follows.

(1)  First, "mcc_pml.applications:" is a list of application names,
     separated by comma, that shall be added to the Applications
     pulldown menu.  Add "DEC HUBwatch" to the list. 

	(ex.) mcc_pml.applications:  DECmcc FCL, DEC HUBwatch

(2)  Add the following line, verbatum, to the mcc_resource.dat file.

     mcc_pml.applications.DEC HUBwatch:/usr/mcc/hubwatch/mcc_hubwatch.csh <DF> 


More information regarding launching applications through DECmcc V1.2
can be obtained in the DECmcc V1.2 Use Manual. 

The C-Shell script, mcc_hubwatch.csh, receives the launched application
datafile and extracts the list of selected SNMP entities.  From this
list, the script determines the read and write community strings and
then invokes the HUBwatch application. 

The script creates and appends to a community string file 
	NMS_DIR/uid/DH90_comm_table.txt
The format of the file is:

	ip read_community_string write_community_string

If this file is not writtable to the user invoking the application, the
launch shall fail.  The user must have write authority on the file.

The following script file has been tested and shown to work.  We supply 
it for your convenience, but it is unsupported.


#!/bin/csh 
#
#	mcc_hubwatch.csh
#
# Digital Equipment Corporation, 1992.
#
# Software Product Group
# Open Network Systems Engineering 
# Network Management Systems
#
# Description:
#
#  This is C-Shell script to invoke the DEC Hub Watch90 Application for all
#  selected entities on a DECmcc Iconical Map.
#
# Parameters:
#
#   $1 is the name of the Launch Application Datafile
#
# Dependencies:
#   DEC Hub Watch90 Environment variable LNMSHOME points to toplevel directory
#    in which HUBWatch software resides. 
#
#
# Set up some variables.
#
set HUBWATCH_DIR = `printenv NMS_DIR`
if ($HUBWATCH_DIR == "") then
   echo "DEC Hub Watch 90 Application invokation requires"
   echo " LNMSHOME to point to top_level directory."
   exit 1
endif
#
# File containing IP community strings.
#  Format:  IP_address read_community write_community
#
set COMMUNITY_FILE = $HUBWATCH_DIR/uid/DH90_comm_table.txt
#
# Get application launch datafile from DECmcc
#
set DATAFILE = $1
if ($DATAFILE == "") then
   echo "No datafile passed.  Exiting"
   exit 1
endif
#
# Get list of selected SNMP entities from launch application datafile.
#
set IPs = `cat $DATAFILE | awk '$1 == "SENTITY:" && $2 == "SNMP" {print $6}'`
set Hosts = `cat $DATAFILE | awk '$1 == "SENTITY:" && $2 == "SNMP" {print $8}'`
#
# If there are NO selected SNMP entities, exit.
#
if ($#IPs == 0) then
   echo "NO SNMP Entities were selected.  Exiting."
   exit 0
endif
#
@ i = 0
#
# Start up DEC HUB Watch for each selected SNMP entity.
#
foreach ip ($IPs)
#
   set host = ($Hosts)
   @ i++
#
#  Get community string for read and write for each IP.
#   If community file does NOT exist, prompt user for
#    information and write it to new file.
  set read_comm = `grep $ip $COMMUNITY_FILE | awk '{print $3}'`
  set write_comm = `grep $ip $COMMUNITY_FILE | awk '{print $4}'`
#
# Invokation depending on availability of write community string.
#  Inform user that when write_community is found in $COMMUNITY_FILE, application
#  will be invoked with write permissions.
#
  if ($write_comm == "") then
     echo "DEC HUB Watch 90 invoked for SNMP entity $ip read-only."
     echo "  If read-write required, edit $COMMUNITY_FILE and ensure entry states "
     echo "    ip_address read_community write_community."
     echo ""
     $HUBWATCH_DIR/bin/DH90_main -x $ip -a $host -to 5 -rt 3 &
  else 
    $HUBWATCH_DIR/bin/DH90_main -x $ip -c $write_comm -a $host -to 5 -rt 3 &
  endif
end

sleep 20

exit





 

DECmcc V1.2 has the ability to launch loosely coupled applications from
it's iconic map interface.  These applications appear as pushbutton
entries in the "Applications" pulldown menu.  The DECmcc Iconic
Map can pass information to the launched application via a
datafile.  The datafile, produced in the user's current directory,
contains the following DECmcc map window context information:  domain,
map file name, and all selected entities.  Once the application is 
launched, it is independent of DECmcc V1.2. 

In the window from which the V1.2 DECmcc Iconic Map is invoked, the user
MUST define the logical name NMS_DIR.  NMS_DIR must point to the
top_level directory in which the HUBwatch software has been defined.  In
further example, we will assume the HUBwatch top_level directory to be
MCC_SYSTEM. 

The user can add the DEC HUBwatch application to their V1.2 DECmcc map 
window by modifying their private mcc_resource.dat file as follows:

(1)  First, "mcc_pml.applications:" is a list of application names,
     separated by comma, that shall be added to the Applications
     pulldown menu.  Add "DEC HUBwatch" to the list. 

	(ex.) mcc_pml.applications:  DECmcc FCL, DEC HUBwatch

(2)  Add the following line, verbatum, to the mcc_resource.dat file.

     mcc_pml.applications.DEC HUBwatch: @mcc_system:mcc_hubwatch.com <DF> 


More information regarding launching applications through DECmcc can be
obtained in the V1.2 DECmcc Use Manual. 

The DCL command procedure, mcc_hubwatch.com, receives the launched
application datafile and extracts the selected SNMP entity information. 
From this list, the command procedure  determines the read and write
community strings and then invokes the HUBwatch application. 

The command procedure will get the read and write community strings for
selected entity(ies) from the community file NMS_DIR:DH90_agents.txt. 
If the community file does NOT exist, launch HUBWatch without arguments.

The format of the community file is:

	ip read_community_string write_community_string

The following script file has been tested and shown to work.  We supply 
it for your convenience, but it is unsupported.



---------------------------mcc_hubwatch.com------------------------------
$ !-----------------------------------------------------------------------------
$ !
$ !	mcc_hubwatch.com
$ !
$ !-----------------------------------------------------------------------------
$ !
$ ! Digital Equipment Corporation, 1992.
$ !
$ ! Software Product Group
$ ! Open Network Systems Engineering 
$ ! Network Management Systems
$ !
$ ! Description:
$ !
$ !  This is DCL Command Procedure to invoke the DEC Hub Watch90 Application for a
$ !  selected entity on a DECmcc Iconical Map.
$ !
$ ! Parameters:
$ !
$ !   $1 is the name of the Launch Application Datafile
$ !
$ ! Dependencies:
$ !   DEC Hub Watch90 Environment variable NMS_DIR points to toplevel directory
$ !    in which HUBWatch software resides. 
$ !
$ ! 	Some convenience function definitions
$ ! 
$ !-----------------------------------------------------------------------------
$
$  	echo = "write sys$output"
$  	ask  = "inquire/nopunctuation"
$
$ !-----------------------------------------------------------------------------
$ !
$ !	Find out where HUBwatch software was loaded.  Logical NMS_DIR should
$ !     contain directory location of HUBwatch software.
$ !
$ !-----------------------------------------------------------------------------
$
$ 	HUBWATCH_DIR = f$trnlnm("NMS_DIR")
$	if HUBWATCH_DIR .eqs. ""
$	then
$	   echo "Exiting.  Define NMS_DIR to location of HUBwatch software."
$	   exit
$	endif
$	dh90_main :== "$ ''HUBWATCH_DIR'dh90_main"
$
$ !-----------------------------------------------------------------------------
$ !
$ ! 	File containing IP community strings.
$ !  	Format:  IP_address read_community write_community
$ !
$ !-----------------------------------------------------------------------------
$
$  	COMMUNITY_FILE = "''HUBWATCH_DIR'DH90_agents.txt"
$
$ !-----------------------------------------------------------------------------
$ !
$ ! 	Get application launch datafile from DECmcc
$ !
$ !-----------------------------------------------------------------------------
$  	DATAFILE = P1
$  	if ((DATAFILE .eqs. "").OR.(f$search(DATAFILE) .eqs. "")) 
$	then 
$   	  echo "No datafile passed or not found.  Exiting"
$   	  exit 
$ 	 endif
$ !-----------------------------------------------------------------------------
$ !
$ ! 	Get selected SNMP entity from launch application datafile.
$ !
$ !-----------------------------------------------------------------------------
$  	open/read/err=readerr_data_file   in_file 	'DATAFILE'
$ !------------
$  read_a_line:
$ !------------
$   	read/end=end_of_data in_file _line
$!
$  	if (f$locate ("SENTITY:", _line) .eq. 0)
$	then
	  IPaddress = f$element(5," ",_line)
	  HostName  = f$element(7," ",_line)
	  goto end_of_data
$	endif
$!
$    	goto  read_a_line
$ !------------
$  end_of_data:
$ !------------
$ 	close in_file
$
$ !--------------------------------------------------------------------------------------
$ !
$ ! 	If there are NO selected SNMP entities, start application without any arguments.
$ !
$ !--------------------------------------------------------------------------------------
$
$  	if (IPaddress .eqs. "") 
$	then
$   	  dh90_main 
$         exit
$ 	endif
$
$ !----------------------------------------------------------------
$ !
$ !  Get read and write community string for selected entity.
$ !   If community file does NOT exist, launch without arguments.
$ !
$ !----------------------------------------------------------------
$
$   	if f$search(COMMUNITY_FILE) .eqs. ""
$	then
$   	  dh90_main 
$         exit
$ 	else
$  	  open/read/err=readerr_data_file   in_file 	'COMMUNITY_FILE'
$ !------------
$  read_b_line:
$ !------------
$   	  read/end=end_data in_file _line
$!
$  	  if (f$locate(IPaddress, _line) .eq. 0)
$	  then
$	    WriteCommunity  = f$element(2," ",_line)
$	    goto end_data
$	  endif
$!
$    	  goto  read_b_line
$ !------------
$  end_data:
$ !------------
$ 	  close in_file
$  	  if WriteCommunity .eqs. ""
$	  then
$   	    dh90_main 
$ 	  else
$	    dh90_main -a 'Hostname -x 'IPaddress -c 'WriteCommunity -to 5 -rt 3
$	  endif
$ 	endif
$
$ 	exit
$ !------------
$  readerr_data_file:
$ !------------
$  	echo "Error reading ''COMMUNITY_FILE'."  
$ 	exit




 

The DECmcc T1.3/V1.3 Application Launch facility enables a user to easily 
integrate applications into the Iconic Map window.  Using the launch 
mechanism, the user can specify that the application be associated with 
a single user, a group of users, or with an entire system.

At start up, DECmcc T1.3/V1.3 checks both a user and a system directory 
to identify any Application Interface Definition files to be 
incorporated into the Map window.  The Application Interface Definition 
file names must have the following format:

	mcc_appl_<appl_name>.def  

where <appl_name> is unique.

Place the Application Interface Definition File in one of the default 
directories or in a directory specified by the user.  The default 
system directories are

	MCC_SYSTEM		<---   VMS
	/usr/mcc/mcc_system     <---   ULTRIX

The user may specify a different system directory for the Application 
Interface Definition Files by using the MCC_APPL_SYS_LOCATION
environmental variable or logical name. 

To make the application local to a user or group of users, the default 
directies are

	SYS$LOGIN:              <---   VMS
	~/                      <---   ULTRIX

The user may specify a different local directory for the Application 
Interface Definition Files by using the MCC_APPL_USER_LOCATION 
environmental variable or logical name.

A user can launch HUBwatch from DECMcc V1.3 by placing the definition
file supplied here in the correct directory.  The following definition
file has been tested and shown to work.  We supply it for your
convenience, but it is unsupported. 


#
# 	DEChub 90 Front Panel Management Launch Application Interface Definition
#		File for Digital's Network Management Platforms.
#
#   mcc_appl_hubwatch.def
#
#   Date:  13-October-1992
#
#
DEL_KEY:  *
Menu:  Applications
  Button:  DEC HUBwatch
    binary:  $NMS_DIR/bin/DH90_main
    argument:  -x <InternetAddress> -a <InternetName> 
    argument:  *-c <SNMPwrCommunity>* -to 5 -rt 3
    env_type:  WINDOW
Endmenu:
		 

The following DECmcc V1.3 launch definition file has been provided for 
your convenience.  It has been tested and shown to work, but is 
unsupported.  

This note is also cross-posted in EMDS::HUB_MGNT and has been sent to 
KOKO::NET_PARTNERS.

...kjn


#
# 	DEChub 90 Front Panel Management Launch Application Interface Definition
#		File for Digital's Network Management Platforms.
#
#   mcc_appl_hubwatch.def
#
#   Date:  27-JAN-1993
#
#
DEL_KEY:  *
Menu:  Applications
  Button:  DEC HUBwatch VMS
    binary:  mcr hubwatch
    argument:  -x <InternetAddress> -a <InternetName> 
    argument:  *-c <SNMPwrCommunity>* -to 5 -rt 3
    env_type:  WINDOW
Endmenu:
		 

Hi,

The SPD does not mention support for Ultrix 4.3. We have a customer interested
in using MCC but is in the process of upgrading to 4.3. As Ingres does not come
with 4.3 does this mean the customer has to buy Ingres?

thanks. 

DECmcc is supported on ULRTRIX V4.3
There is an earlier note on Ingres support for those who will be using
the exporter FM (otherwise you don't need it).

-- Erik

The command to invoke HUBwatch has changed.  You need to change your 
mcc_appl_hubwatch.def files to reflect new command.


              <<< EMDS::$1$DUA24:[NOTES$LIBRARY]HUB_MGNT.NOTE;1 >>>
                         -< Hub Management Conference >-
================================================================================
Note 161.3                     VMS Documentation?                         3 of 3
MAIL::CLAYTON "Merlin Clayton DTN 445-7217"          21 lines  18-FEB-1993 10:08
                                -< Now Working >-
--------------------------------------------------------------------------------
The problem with launching HUBwatch T1.1.8 was related to the method of
envoking HUBwatch from VMS.  

The old way was "mcr hubwatch ....."

The new way is "WATCH /AGENT <agent_name>"

I made the necessary changes to the MCC_APPL_HUBWATCH.def procedure and the 
launch from mcc now works.

The only problem I had was that I had to hard code the community name because
when I tried passing the variable it could not be found in the agent table.
This is most likely a problem with case sensitivity.  Hubwatch also did not
like the format of the IP address, so I just eliminated it from the argument
string.

Maybe someone can shed some light on these issues.

Thanks.

Merlin