| 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 |
Hi,
Testing DECmcc/ULTRIX V1.3.0 & SCRIPT_AM, I've got the following
unexpected results using Wildcarding option :
#manage
1) GETTING characteristics for ALL mcc_df instances...
MCC> show script * mcc_df * all char
Script LOCAL_NS:.script.chipcom_procedures mcc_df test1
AT 1993-04-08-13:49:48.367 Characteristics
Examination of attributes show:
Command =
"/usr/mcc/mcc_system/mcc_scripts/mcc_df /dev/rz0a"
Script LOCAL_NS:.script.chipcom_procedures mcc_df test2
AT 1993-04-08-13:49:48.863 Characteristics
Examination of attributes show:
Command =
"/usr/mcc/mcc_system/mcc_scripts/mcc_df /dev/rz1a"
2) GETTING identifiers for ALL mcc_df instances...
MCC> show script * mcc_df * all id
Script LOCAL_NS:.script.chipcom_procedures mcc_df test1
AT 1993-04-08-13:51:00.430 Identifiers
Examination of attributes show:
File System = test1
Script LOCAL_NS:.script.chipcom_procedures mcc_df test2
AT 1993-04-08-13:51:00.566 Identifiers
Examination of attributes show:
File System = test2
3) TRYING to get status for ALL instances... Please note that ONLY
status of FIRST instance are returned !!
MCC> show script * mcc_df * all status
Script LOCAL_NS:.script.chipcom_procedures mcc_df *
AT 1993-04-08-13:51:08.797 Status
Examination of attributes show:
Command Executed =
"/usr/mcc/mcc_system/mcc_scripts/mcc_df /dev/rz0a"
Total kbytes = 210359
kbytes used = 179604
kbytes free = 9720
percent kbytes used = 95 %
inodes used = 1270
inodes free = 105226
percent inodes used = 1 %
Mounted on = "/usr/mcc1"
4) GETTING attributes for ALL instances... (please note that it works!)
MCC> show script * mcc_df * all attr
Script LOCAL_NS:.script.chipcom_procedures mcc_df test1
AT 1993-04-08-13:51:13.559 All Attributes
File System = test1
Command Executed =
"/usr/mcc/mcc_system/mcc_scripts/mcc_df /dev/rz0a"
Total kbytes = 210359
kbytes used = 179604
kbytes free = 9720
percent kbytes used = 95 %
inodes used = 1270
inodes free = 105226
percent inodes used = 1 %
Mounted on = "/usr/mcc1"
Command =
"/usr/mcc/mcc_system/mcc_scripts/mcc_df /dev/rz0a"
Script LOCAL_NS:.script.chipcom_procedures mcc_df test2
AT 1993-04-08-13:51:14.637 All Attributes
File System = test2
Command Executed =
"/usr/mcc/mcc_system/mcc_scripts/mcc_df /dev/rz1a"
Total kbytes = 210359
kbytes used = 185245
kbytes free = 4079
percent kbytes used = 98 %
inodes used = 1122
inodes free = 105374
percent inodes used = 1 %
Mounted on = "/usr/mcc"
Command =
"/usr/mcc/mcc_system/mcc_scripts/mcc_df /dev/rz1a"
5) TRYING to get 'percent kbytes used' for ALL instances... Please note
that ONLY first instance is returned !!!
MCC> show script * mcc_df * percent kbytes used
Script LOCAL_NS:.script.chipcom_procedures mcc_df *
AT 1993-04-08-13:51:25.164 Status
percent kbytes used = 95 %
Is this a known problem of SCRIPT AM ?
Thank you for your replies.
Renato
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4844.1 | Weird things happening with the Script AM | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Thu Apr 08 1993 14:01 | 29 |
Renato,
Yes these are know problems, more or less. The entity model which
we used for the Script AM doesn't follow all of the guidelines. We
put the Script as a global entity so that it worked easily on the
Iconic Map. The Script AM is *not* a global entity ... I would like
to see Relationship in the Map.
The Script AM really has two interfaces:
o One for managing script 'instances'; create, delete, show, set.
o One for executing scripts.
We bundled both interfaces together for simplicity and are now getting
bitten by this decision. This is something that needs work. I hope that
at the same time we correct the entity model so that things make more
sense based on the dual interfaces, that we also implement Tight
Integration (also known as High-Integration).
Relationship: With Relationships you could select and Entity, press the
MB3 button and see the word 'scripts' on the pop-up menu. Selecting
'scripts' would display all the scripts which operate on the entity you
have selected. I want to see Relationships applied to the Alarms User
Interface too.
/keith
| |||||
| 4844.2 | V1.3 MUP for FCL ? V1.4 for new functionalities ? | ZTOIS1::VISTA | Renato VISTA, SIS Strasbourg, France | Tue Apr 13 1993 04:45 | 18 |
Keith,
Thank you for your reply.
Will be there any patch (v1.3 MUP ?) available to obtain a complete
usage of FCL interface applied on SCRIPT global entity ?
About the "relationship" occurrance on Map, will this new
functionaly implemented in next version (V1.4...) ?
Regards,
Renato
Regards,
Renato
| |||||
| 4844.3 | No Script AM changes in the v1.3 MUP | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Tue Apr 13 1993 10:38 | 19 |
RE: .2
Renato,
> Will be there any patch (v1.3 MUP ?) available to obtain a complete
> usage of FCL interface applied on SCRIPT global entity ?
No 8( There will be no changes to the Script AM in the v1.3 MUP
(least that I know about).
> About the "relationship" occurrance on Map, will this new
> functionaly implemented in next version (V1.4...) ?
I'd sure be happy if it were - but v1.4 is a limited release. As
such, something like Relationships is not on the list. You can
send your 'vote' for Relationships to Dan (MOLAR::) Carr ... Dan
is the supervisor over the Visualization Services (The Iconic Map)
/keith
| |||||
| 4844.4 | Product management | TOOK::MINTZ | Erik Pavlik Mintz | Tue Apr 13 1993 14:20 | 13 |
I'm probably starting to sound like a broken record, but... V1.4 is NOT a Polycenter framework release. It is a network management release, and as such, will contain very few framework enhancements (only those required directly by the developers in the Network Managment Applications group). As for the Script AM, as far as I know, there is currently nobody assigned to maintain that module. If you have requirements, please make sure that product management is aware of them (e.g. NOTED::EMF_REQ). -- epm | |||||