Conference azur::mcc

4975.0. "The very easy doubleclick Launch..." by VNASWS::HONISCH (Guenter Honisch ACT Austria) Thu Apr 29 1993 12:36

Thats the way I customize our MCC Systems with Procedures launched by
a doubeclick on a reference Icon

I abuse the Remarks Parameter for launching the real function 
( name of .COM file)
I start for any doubleclick the Com file : REMARKS_ATTR_LAUNCH.COM;

This procedure gives all parameters defined in the MCC_APPL_REFERENCE_DC.DEF
to the called procedure which does the real work...
You can also put several Parameters in "Textfile" Attribute 
(seperate with spaces)

i.e.:
set reference .ref.ss_auinb0 remarks = MCC_SHO_STAT_BRIDGE.COM, -
        text file = .br.auinb0

causes at Doubleclick at .ref.ss_auinb0 ICON the MCC_SHO_STAT_BRIDGE.COM to run
and gives ".br.auinb0" as P2 to it

The main advantage is the extremely Easiness of changes without restarting MCC

					have Fun 

							Guenter

********************************************************************************

Setup Logical i.e.

"MCC_APPL_USER_LOCATION" = "mcc_user:[MCC.CMD.LAUNCH]"
"MCC_LAUNCHDIR" = "mcc_user:[MCC.CMD.LAUNCH]"

********************************************************************************
MCC_APPL_REFERENCE_DC.DEF;1 => Menufile to make "REFERENCE Class"
                                Doubleclick sensitive (in MCC_LAUNCHDIR:)
********************************************************************************

LAUNCH: DOUBLECLICK
        ARGUMENT: <Reference.!.Remarks>
        ARGUMENT: <Reference.!.Text File>
        ARGUMENT: <Domain>
        ARGUMENT: <datafile>
        SHELL: @MCC_LAUNCHDIR:REMARKS_ATTR_LAUNCH.COM
        ENV_TYPE: terminal
        APPLIES_TO: REFERENCE

********************************************************************************
ARGUMENT: <datafile> is most likely unnecessary, 
	  but its in for historic reasons...

********************************************************************************
REMARKS_ATTR_LAUNCH.COM; => intermediate Launchfile in MCC_LAUNCHDIR:
********************************************************************************

$set noon
$sho time
$@MCC_LAUNCHDIR:'p1 'p1 'p2 'p3 'p4 'p5 'p6 'p7 'p8
$Exit

********************************************************************************
 EDIT_TEXT.COM => calls editor and edits file in "Textfile" Attribute
			   in MCC_LAUNCHDIR:
********************************************************************************
$set noon
$def/user sys$input Sys$command
$edit/nojou mcc_maps:'p2
$!wait 00:00:15
$Exit

********************************************************************************
OR...
********************************************************************************
LAUNCH_PAR.COM; just show all Parameters for a launch (Debug use)
********************************************************************************
$set noon
$sho time
$write sys$output "P1 : ",P1
$write sys$output "P2 : ",P2
$write sys$output "P3 : ",P3
$write sys$output "P4 : ",P4
$write sys$output "P5 : ",P5
$write sys$output "P6 : ",P6
$write sys$output "P7 : ",P7
$write sys$output "P8 : ",P8
$wait 00:00:30
$
********************************************************************************
SET_H_DTE.COM;1 set host/dte to port name in "Textfile" Attribute i.e. TTA2:
********************************************************************************

$set noon
$def/user sys$input Sys$command
$set host/dte 'p2
$Exit
$
********************************************************************************
OR...
********************************************************************************
MCC_SHO_STAT_BRIDGE.COM; sho overview status 
				of a FDDI bridge with one Doubleclick
********************************************************************************
$! call  MCC
$!
$open/write x sys$scratch:mcc_shostat.tmp
$ write x "mana/enter"
$ write x "sho bridge "+''p2'+" all attributes, to file sys$scratch:brstat.tmp"
$ write x "sho bridge "+''p2'+" all counters, to file sys$scratch:brcou.tmp"
$open/write x sys$scratch:mcc_sho
$ close x
$ @sys$scratch:mcc_shostat.tmp
$ delete sys$scratch:mcc_shostat.tmp;
$sea /win=(0,2) sys$scratch:brstat.tmp; "fru type"
$sea  sys$scratch:brcou.tmp; "="
$sea  sys$scratch:brstat.tmp; "Spanning Tree Mode"
$sea  sys$scratch:brstat.tmp; "Best Root"
$sea  sys$scratch:brstat.tmp; "Device State"
$sea  sys$scratch:brstat.tmp; "Device Broken Reason"
$sea  sys$scratch:brstat.tmp; "NVRAM Failed Flag"
$delete sys$scratch:br*.tmp;*
$inquire ex "Return to exit"
$exit
********************************************************************************
    

    Some more info to .0
    I use a separate Domain for each FDDI device which has all important
    Childentities and SNMP, RBMS, SNMP grouped together
    Also i do have several Doubleclick Buttons predefined for Docu, reset,
    Status...
    Therefore the examles I used in .0
    
    
    How about a Ultrix Version of this ???
    					Guenter