[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

4572.0. "Argument ID for Reference Entity?" by MAIL::CLAYTON (Merlin Clayton DTN 445-7217) Thu Feb 18 1993 16:51

Using the new lauched application mechinism in V1.3, is there a way to 
register Reference Data entities and pass the name of the Reference Data 
entity to an application/procedure via an argument in the mcc_appl_....def
procedure?

I would like to register 3rd party devices that only have an RS232 console
port for management as Reference entities.  I want to connect the RS232 
console port to a LAT port on a terminal server and define the device as a
reverse LAT service.  Then when I select the reference entity, I double click
on it, and it opens up a terminal window into the device.  The registered 
reference entity name would have to be the LAT service name, which can be
done.  However, in reading the documentation on launched appls, I do not see
an obvious "well known agument identifier" for a reference entity name.

Is there a relatively easy way to do the above?

Thanks.

Merlin

T.RTitleUserPersonal
Name
DateLines
4572.1user-defined argument.TOOK::MCPHERSONpre-retinal integrationThu Feb 18 1993 17:0429
>done.  However, in reading the documentation on launched appls, I do not see
>an obvious "well known agument identifier" for a reference entity name.
>
>Is there a relatively easy way to do the above?


Try:

MENU: Applications
  Button: Console Connect
  SHELL: sys$login:connect.com
    Argument: <REFERENCE.!.Remarks>
ENDMENU

This should pass in the value of the "Remarks" attribute for the selected
reference entity.   If you had the LAT service name as the "Remarks" attribute,
then that'd get passed to sys$login:connect.com in P1.  Of course, you *could*
augment the reference entity to include an attribute called "Service Name", if
you wanted.  (You know how to do that, right Merlin?   ;^)


/doug