[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

5305.0. "<OSIName> <OSIAddress> in command definition for ologin ?" by KETJE::PACCO (Gallia divisa est in partes tres) Tue Jul 06 1993 15:34

    I tried to set-up an "operations button" for the entity
    	"NODE"
    
    I followed the examples shown in
    /usr/mcc/mcc_system/mcc_appl_mccbase.def
    
    I defined:
    
    #
    Menu:  Operations
        Button:     ologin
            binary:     /usr/bin/ologin
            argument:   <OSIAddress>
            env_type:   TERMINAL
            term_title: OSI login
            icon_label: ologin
            applies_to: node
        Button:     ologinname
            binary:     /usr/bin/ologin
            argument:   <OSIName>
            env_type:   TERMINAL
            term_title: OSI login
            icon_label: ologin
            applies_to: node
    Endmenu:
    #
    
    Trying both entries, It happens that the first entry does not launch
    the application, where as the second one launches the OSI login
    application, but gives the DNA$Towers of the node entity.
    
    It is confusing to get the towers, where you expect a name.
    Is there any elegant way to call "ologin" from a button as it is the
    case for "dlogin" ?
    
    Regards,
    	Dominique.

T.R	Title	User	Personal Name	Date	Lines
5305.1	There is another way ...	TOOK::FLETCHER	Robin G. Fletcher ..	`Wed Jul 14 1993 15:11`	29
	- OSI Name .. is retrieved from DNS as the SECOND identifier in the list DNS returns. - OSI address .. is retrieved from DNS as the THIRD identifier in the list DNS returns. If your DNS set up does not store the "name" and "address" in this order, you should use the following mechanism to get "name" and "address" data passed to your login binary. The argument specification could look like the following: argument: <node.!.name> or argument: <node.!.address> If you do not surround the argument specification with the system's DEL_KEY or your specified DEL_KEY (usually '') then if the argument can not be retrieved, the application will not be launched. EX: DEL_KEY: ...... argument: <OSIAddress> Would launch the application even if it could not get the address argument. Are you getting any error messages, telling you why it cannot launch with the Address associated pushbutton?
5305.2	Are extended submenus wishfull thinking ?	KETJE::PACCO	Gallia divisa est in partes tres	`Tue Jul 20 1993 13:23`	12
	Thanks, the <Node.!.Name> format works. Going further on this I have two more questions: 1). Is it possible to have embedded sub-menus for applications ? 2). Is it possible to have a sub-menu on an "operations" application. Regards, Dominique.
5305.3	yes and maybe.	MCDOUG::doug	Dead or Canadian?	`Wed Jul 21 1993 09:26`	14
	> 1). Is it possible to have embedded sub-menus for applications ? Yes, but you can only go one level deep. I.e. no sub-sub menus.. > 2). Is it possible to have a sub-menu on an "operations" application. I don't know. Never tried that., but I don't see why it wouldn't work as long as you weren't replacing an entry that was already in the menu (i.e. "Set" or "Show"). /doug
5305.4	Submenus ARE possible in Operations applications.	KETJE::PACCO	Gallia divisa est in partes tres	`Tue Jul 27 1993 13:00`	8
	I tried to use submenus in the "Operations" application. YES, IT WORKS. The "Buttons" appear in the operations window at the same level as the partitions for SHOW, SET etc... Dominique.