| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3679.1 | or how about.. | TOOK::MCPHERSON | Life is hard. Play short. | Wed Sep 02 1992 17:49 | 9 |
| If I may continue the litany...
(4) I'm still trying to figure out how to get the *rest* of DECmcc to do
what I want it too...
|
| 3679.2 | YES HERE IS ONE PLAYING ! ! ! ! ! ! | HLRG02::SYSTEM | Incredible but . . . not true . | Thu Sep 10 1992 10:43 | 55 |
| Hi ,
I have just played a little bit with the SCRIPT AM.
I think it is a great tool.
It is very simple in use AFTER you have done it once.
------------------------------------------------------------------------------
First time I had a few problems:
In the text file MCC_SCRIPT_README.TXT there is a description about integrating
new scripts.
In the chapter about moderately-integrated scripts you have to add some text
about that it is necessary FIRST to do the create command and after that you
can work with your script.
I discovered how to do this by reading in MCC_SCRIPT_INSTALL.COM .
------------------------------------------------------------------------------
I discovered also a few bugs:
- When I give the following home-made command it is right:
MCC> show mcc 0 script users allusers all status
BUT when I give the same command but now wiht a wildcard than the returned
out_entity is * and not the entity name.
- When I start up IMPM, double click on the MCC icon all thing is right,
BUT when I double click on the SCRIPT icon than I got :
$ man/e/i=d
%CMA-F-EXCCOP, exception raised; VMS condition code follows
-SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=C9C40128, PC
=000A3B0B, PSL=03C00008
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
0004B8C4 0004B8C4
0007C782 0007C782
000775DC 000775DC
0007AC78 0007AC78
------------------------------------------------------------------------------
I hope you have enjoyed this response. ;-)
Kindest regards,
/-/ Henk.
(sorry for the late answer, but I have more things to do)
|
| 3679.3 | thats what we like -- feedback !! 8) | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Fri Sep 11 1992 11:48 | 27 |
| RE: .2
Henk.
>> It is very simple in use AFTER you have done it once.
I fell off my bike, once, too 8)
>> First time I had a few problems ... In the text file MCC_SCRIPT_README.TXT
The documentation isn't wonderful 8( sorry about that. We have been
assigned a writer and produced a postscript Use manual. It needs a lot
of work still .. its on the list. I'm glad you got your script to work
just the same.
The postscript file is at: molar::script_am:mcc_script_use.ps
>> I hope you have enjoyed this response. ;-)
Yes we do! I have made a few bug fixes since IFT-1 ... some in the
area of wildcarding. Its possible that I've fixed this particular
bug already. This one sounds familiar. I should have another kit
available soon.
Thanks,
/keith
|
| 3679.4 | Comments and questions | MSBCS::DOLAN | | Fri Sep 11 1992 13:42 | 28 |
| hi - I looked into the script_am because I need to execute as directives a lot
of layered product's command files eg. startup procedures, ivp's ... In many
cases there are no error conditions set in the scripts, just messages
written to stdout. I wanted to be able to show the output of the command
procedure in the IMPM window. I found that parsing on spaces in the script_am
made it fairly ineffective for my needs, however here are some comments.
1. Using loosely integrated scripts seems poorly documented. In particular
I went looking for a section called "Integrating a Loosely Integrated Script."
I found the use of Command as a child entity and an argument confusing.
2. Using a loosely integrated script with the FCL PM I received output
associated with arg1, arg2....however, when I ran the same script from
the IMPM there was a lot of screen refreshing but at the end all I had were
args having NOT RETURNED messages associated with it.
3. I couldn't figure out how to create an instance with the IMPM. I didn't
find the create directive in the operations menu.
4. After working with loosely integrated, I moved my script to be a moderately
integrated script. This time when I tried to use the IMPM I could not get
to the children of SCRIPT. When I double clicked on SCRIPT, I kept getting an
ACCESS VIOLATION.
While the Script_am did not meet my current needs I will be interested in
following it's progress, since I can see some other potential uses.
Hope this helps. lynn dolan
|
| 3679.5 | answers | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Fri Sep 11 1992 14:50 | 82 |
| RE: .4
Hi Lynn,
>hi - I looked into the script_am because I need to execute as directives a lot
>of layered product's command files eg. startup procedures, ivp's ... In many
>cases there are no error conditions set in the scripts, just messages
>written to stdout. I wanted to be able to show the output of the command
>procedure in the IMPM window. I found that parsing on spaces in the script_am
>made it fairly ineffective for my needs, however here are some comments.
Correct .. the Script AM processes columns of data, turning them into
DECmcc Attributes. Entire screens/pages of output as you suggest does
not work well with it. But, perhaps application launching is what you
need. This allows you to add a menu item to the IMPM and execute your
script more interactivly.
>1. Using loosely integrated scripts seems poorly documented. In particular
>I went looking for a section called "Integrating a Loosely Integrated Script."
>I found the use of Command as a child entity and an argument confusing.
I feel terrible about the documentation quality 8( This will be reworked
and when available, the location will be posted in this conference.
The "Command" Child entity is the hook to loosly-integrated scripts.
The MS for this entity defines the generic attribute names (arg1, ...)
and datatype (latin1string). Perhaps "Command" is a poor choice. Would
anyone have a better idea?
The "Command" Attribute contains the exact command you want the Script
AM to execute. Again - any other suggestions ?
>2. Using a loosely integrated script with the FCL PM I received output
>associated with arg1, arg2....however, when I ran the same script from
>the IMPM there was a lot of screen refreshing but at the end all I had were
>args having NOT RETURNED messages associated with it.
a) The Script AM converts each line of output from sys$output / sdtout to
a separate entity - so one show directive can return countless entites.
The IMPM does not pause or in any other way (like a scrolled window) let
you view each entities worth of data .. you just see blinking with the
last entity finally displayed.
b) The "Command" child entity defines 32 attributes (arg1 - arg32). If your
script doesn't return this many attributes, the IMPM tells you that
the attribute wasn't returned. This only occurs for loosly-integrated
Scripts.
>3. I couldn't figure out how to create an instance with the IMPM. I didn't
>find the create directive in the operations menu.
There is no "create" menu item .. you must goto the Edit pull-down menu
(or MB2) and select TOOLBOX. Here you will see the child entities
available for the Script AM .. you create the Script Instance as you would
any other entity for DECmcc.
>4. After working with loosely integrated, I moved my script to be a moderately
>integrated script. This time when I tried to use the IMPM I could not get
>to the children of SCRIPT. When I double clicked on SCRIPT, I kept getting an
>ACCESS VIOLATION.
The IMPM expands all available scripts by using the Show <entity *> all Ident
directive. There was a bug in the Script AM wildcard expansion. This is
fixed and will be available with the new IFT-1A kit.
>While the Script_am did not meet my current needs I will be interested in
>following it's progress, since I can see some other potential uses.
Thank you! You are correct that the Script AM will not solve everyones
problem. For v1.3 there are 5 integration techniques:
o IMPM Application Launching
o Script AM
o Data Collector
o Callable DECmcc
o DECmcc Management Modules
Hopefully one of these techniques will be right for your project.
/keith
>Hope this helps. lynn dolan
|
| 3679.6 | a welcome addition | CTHQ::WOODCOCK | | Mon Sep 14 1992 09:49 | 11 |
| Hi there,
If you are out of the office for a month then the "minute" still turns into
the "month". But I've returned to find this gem and was sitting around trying
to figure out what unmanagable thing I was going to manage. It is good to see
this type of integration although I haven't fixed any real life problems with
it yet. I did get thru the docs and got the unmanagable to be managed, see note
3711 for the example :-).
kind regards,
brad...
|
| 3679.7 | | KYOA::KOCH | It never hurts to ask... | Thu Feb 25 1993 00:18 | 7 |
| The Script AM seems interesting. Would I be able to implement a VCS
like capability with it?
I want to issue commands to a port and receive the output. Or am I
simply limited to monitoring a port?
Comments and ideas are welcome...
|
| 3679.8 | Script AM does anything a script can do .. 8) | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Thu Feb 25 1993 10:42 | 14 |
| RE: .7
>> Would I be able to implement a VCS like capability with it?
>> I want to issue commands to a port and receive the output. Or am I
>> simply limited to monitoring a port?
If you can do this via a script (DCL or Ultrix Shell script) than you
can use the Script AM .. The script AM simple executes a script and
propogates the output (STDOUT) from the script back into MCC.
So - you script can send commands to the port, get back tht output,
probably have to filter/format the data, then return it to Script AM.
/keith
|