Conference azur::mcc

>	I was wondering if the new feature "Application Launching Capability"
>has anything to do with including our own applications in the
>applications menu. We have written several command procedures and
>would like to know if we can somehow include them in this
>applications menu. Or is this applications menu only for other
>Presentation modules?
>

    Yes. It has *everything* to do with that!   Mind you, right now there's no
    (supported/documented) way to pass entity instance data into an external
    aplication.   I.e. right now you CAN'T simply highlight an icon, go to the
    applications pull-down and, select "Telnet" and havea window created with a
    telnet session to that device.   You *can* select (f'rinstance) "Telnet
    Window" from the "Applications" Pull-down and have it create a decterm with
    Telnet started... then you can say "telnet foo.lkg.dec.com"


    If you want to try adding your own applications, do this:   

    Start the IMPM.

    SAVE the current customized settings.   (this will write the file
    mcc_resource.dat to your current directory, in case it wasn't already
    there.

    CAREFULLY edit mcc_resource.dat to include your applications.  (I have
    included a snippet of my mcc_resource.dat (VMS system, running MCC
    T1.2.4) so you can get an idea of the format.    BE VERY CAREFUL.  I
    seem to remember that screwed up resource files can cause IMPM to
    ACCVIO.

    Also: I STRONGLY urge you to make certain that the command you insert
    in the applications definition works correctly from DCL (or shell)
    before you try to invoke it from the IMPM.  (It can take a few
    iterations to get it right, and you can spend a lot of time waiting for
    the IMPM to start...)

    regards, 
    doug

    mcc_resource.dat Excerpt:

		{look toward the bottom of the file...}
	.
	.
	.
mcc_pml.applications.DECmcc IP Autoconfiguration.vms_command:	CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE ="DECmcc IP Autoconfiguration",ICON_NAME="DECmcc AC IP") @mcc_common:mcc_ip_autoconfig.com
mcc_pml.applications.DECmcc DECnet Phase IV Autoconfiguration.vms_command:	CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE ="DECmcc Phase IV Autoconfiguration ",ICON_NAME="DECmcc AC DNA4") @mcc_common:mcc_wan4_autoconfig.com
mcc_pml.applications.DECmcc Telnet Window.vms_command:	CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE ="DECmcc Telnet Window",ICON_NAME="Telnet") Telnet
mcc_pml.applications.StrataCom Window.vms_command:	submit/remote xxxxxx"username password"::"test_script"
mcc_pml.applications.DECmcc Command Line (FCL).vms_command:	CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE ="DECmcc Command Line",ICON_NAME="DECmcc FCL") MANA/ENTER 
mcc_pml.applications:	DECmcc Command Line (FCL),DECmcc IP Autoconfiguration,DECmcc DECnet Phase IV Autoconfiguration,DECmcc Telnet Window,StrataCom Window

Hi Doug,

	It works!!! I tried it out, and it works! Why isn't this
feature documneted in the Director Use manual. It is exactly what
my customer is looking for, adding their own applications and
the FCL application, and that it is included in the Resource.dat
because then for different users, the Applications menu could be
customized.

	The second question about the Alternate Identifiers
is still open.(just so that it doesn't get lost in all the talk
about the Applications menu)

Thanks and regards,
Julie Ann

   The second question on alternate identifiers is one that I have seen asked
a couple of different places in the notes file, but I have not seen answered.
Is this one of those features that didn't make it into the eft kit?

 Thanks,
 Scott

    alt idents is working in the map, sounds like it just didn't get
    documented (or at least the version we brought to DECUS has it
    working; maybe it didn't get into EFT). I had better check. I will
    let you know.
    

    re:.2
    It isn't documented coz it wasn't supposed to be public. This has
    changed.
    
    re:.3
    
    It isn't in the eft kit.  It will be in the v1.2 ssb kit.
    
    /Jim