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 |
DECmcc V1.3, ULTRIX V4.2A I am trying to add an option to the Operations menu and to get it to pass some info about the (single) selected entity. I have managed to get the option to appear in the menu when the entity is selected (although if I used TABs to seperate the APPLIES_TO: and the entity name, the option would not appear! Is this a qared bug?) When the option is selected, the debug script called does not get the command line options! The only successful ones sent to the script so far are: Domain, Application_id, and Window_id. The entity class is: DAP> show class unix_system -> Class (1) : UNIX_SYSTEM Definition (3) : PRESENTATION_NAME Definition (3) : INSTANCE_REQUIRED Definition (3) : DYNAMIC Definition (3) : INSTANCE_DATATYPE Subclass (2) : CPU 1 Subclass (2) : FILESYSTEM 2 Subclass (2) : PRINTER 3 Subclass (2) : TAPE 4 Subclass (2) : DISK 5 Subclass (2) : APPLICATION 6 Attribute (5) : SYSTEMID 1 Attribute (5) : NODEALIAS 2 Attribute (5) : SYSTEMNAME 3 Attribute (5) : CPUTYPE 4 Attribute (5) : TRANSPORT 5 Attribute (5) : EVENTPROCESSING 6 Attribute (5) : EVENTSINK 7 Attribute (5) : EVENTTRANSPORT 8 Attribute (5) : USERSTHRESHOLD 9 Attribute (5) : PROCESSTHRESHOLD 10 Attribute (5) : OPERATINGSYSTEM 11 Attribute (5) : TOTALMEMORY 12 Attribute (5) : FREEMEMORY 13 Attribute (5) : TOTALSWAP 14 Attribute (5) : FREESWAP 15 Attribute (5) : MAXIMUMPROCESSES 16 Attribute (5) : CURRENTPROCESSES 17 Attribute (5) : MAXIMUMUSERS 18 Attribute (5) : CURRENTUSERS 19 Attribute (5) : PAGEFAULTS 20 Attribute (5) : PAGEIN 21 Attribute (5) : PAGEOUT 22 Attribute (5) : PAGESFREED 23 Attribute (5) : PAGESRECLAIMED 24 Attribute (5) : SWAPIN 25 Attribute (5) : SWAPOUT 26 Attribute (5) : SWAPFRAGMENT 27 Attribute (5) : TOTALVIRTUALMEMORY 28 Attribute (5) : ACTIVEVIRTUALMEMORY 29 Attribute (5) : TOTALREALMEMORY 30 Attribute (5) : ACTIVEREALMEMORY 31 Attribute (5) : TOTALVIRTUALTEXT 32 Attribute (5) : ACTIVEVIRTUALTEXT 33 Attribute (5) : TOTALREALTEXT 34 Attribute (5) : ACTIVEREALTEXT 35 Attribute (5) : CACHEHITS 36 Attribute (5) : CACHEMISS 37 Attribute (5) : TOTALSEMAPHORES 38 Attribute (5) : USEDSEMAPHORES 39 Directive (6) : SHOW 1 Directive (6) : SET 2 Directive (6) : DIRECTORY 26 Directive (6) : SELECT 28 Directive (6) : REGISTER 29 Directive (6) : DEREGISTER 30 Directive (6) : ERASE 33 Directive (6) : RENAME 34 Directive (6) : GETEVENT 65 Event (10) : SYSTEM_BOOTED 1 Event (10) : SWAP_SPACE_EXHAUSTED 2 Event (10) : USERS_THRESHOLD_EXCEEDED 3 Event (10) : PROCESS_THRESHOLD_EXCEEDED 4 Event (10) : EVENT_PROCESSING_OFF 5 Attribute_Partition (11) : IDENTIFIERS 1 Attribute_Partition (11) : STATUS 2 Attribute_Partition (11) : CHARACTERISTICS 4 Event_Partition (13) : CONFIGURATION_EVENTS 15 My ddc file contains: DEL_KEY: * MENU: Operations Button: UDM Show Users SHELL: /usr/udm/mike ARGUMENT: AUTO UNIX_SYSTEM ARGUMENT: *<UNIX_SYSTEM.!.systemid>* APPLIES_TO: UNIX_SYSTEM ENV_TYPE: TERMINAL ICON_LABEL: UDM Remote Login Endmenu: If anyone can spot what I am doing wrong, please tell me as soon as possible. Thanks. Mike Wheeler
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
5082.1 | USE SPACES IN ATTRIBUTE NAMES | WOTVAX::WHEELERM | Wed May 19 1993 08:18 | 18 | |
Ahah! (or ha ha ha ha) I have the answer. The following works: ARGUMENT: <UNIX_SYSTEM.!.SYSTEM ID> but ARGUMENT: <UNIX_SYSTEM.!.SYSTEMID> would not. The documentation talks about attributes but does not mention that if you have an attribute with name "systemid" and with presentation name (? not sure of terminology) "System ID", then in the .def file you must use the presentation name. Is this a bug? Will it change shortly? (P.S. Another reason why I had assumed the attribute name should be used is because it said so in 4842.1) | |||||
5082.2 | The name in the dictionary may not be the attribute name | RACER::dave | Ahh, but fortunately, I have the key to escape reality. | Wed May 19 1993 08:36 | 30 |
4842.1 is not the right note number (at least in the virtual reality that I use to read this conference, your mileage may vary).... ** Warning ** Abstract diatribe about to follow.... The name of the Attribute IS the presentation name. It just happens that the MCC dictionary cant use usefull attribute names as tags to store the attribute definition, and uses something that is usually very close, i.e. has the spaces and other funny chars removed, for the tag that is used to store the info. Users should never see that name, only the presentation name. So, if an attribute is stored under the tag of SYSTEMID, and the presentation name field in the dictionary is "System ID", then the name of the attribute is "System ID". It just so happens that for single word attributes names the mapping is "one to one". Another way to think about it is kind of like File ID's and file names on VMS. The ***Real*** tag used to store your file is the File ID, and the "Presentation Name" of the file is the name stored in the directory. Its not usefull to refer to files as "DKB0:[1423,7,0]", but to use the presentation name, e.g. "DKB0:MAIL.MAI". You can translate back to the FID if you want to, but it is not usefull in many cases. If you want to play wizard, have a good time... I'm positive that someone else in MCC is going to have a different view on this, and will flame me at lunch today.... PS: Any guess what would happen if I had two attributes, "SYSTEM ID" and "SYS TEMID"? |