| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5130.1 | Little different syntax for executing MCC_MEMORY script on remote systems. | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Tue Jun 01 1993 11:24 | 40 |
| RE: .0
> I have copied over the 4 procedures MCC_SCRIPTS:MCC_*.COM to the target
> machine, a VAX (NODE4) entity, and tried using the IMPM. For
> example:
>
> I use the TOOLBOX and create a global entity, MEMORY_TEST.
> double click on MEMORY__TEST, I now see the child entities
> (disk, memeory, etc)
>
> I get the TOOLBOX and click on MEMORY (this provides me with an
> operations type window)
> I click on the COMMAND field and here's where I get stuck...
> I've tried @'remote_system'::MCC_MEMORY,
> @'remote_system::MCC_MEMORY.COM, and several others...
>
> I've also tried using the COMMAND child entity, writing a DCL procedure
> that sets host over to the remote system and executes MCC_MEMORY, but
> I prefer the way the field format looks in MCC_MEMORY.COM. Eventually
> I want to try this on PDPs, does POLYCENTER support this?
To execute the MCC_MEMORY script on a remote system:
1) copy the script to the remote system
2) on the remote system, define a system logical pointing to the script:
def/sys/exe mcc_memory disk:[dir]mcc_memory.com
3) on the remote system, either enable the TASK object or setup
network proxy from the local system.
4) when you create the script on the local system...
command = @mcc_scripts:mcc_memory <remote-system>
where <remote-system> is the name of the remote system to execute
the script on.
/keith
|
| 5130.2 | What about MCC_DISK using the IMPM??? | IOOSRV::GALVIN | Mic, (306) 781-5448 | Tue Jun 01 1993 13:33 | 15 |
| Keith,
Thanks. I got that info from an earlier response you gave someone
else.
Couple more questions; how do I execute MCC_DISK remotely from the
IMPM,
I looked at the .COM and P1 is a different beast...smile.
Also, do we support PDPs with the SCRIPT? Running DECnet IV? Running
LAT? I saw a not from Erik, regarding OSI, is this the same situation?
I've tried the DATA COLLECTOR and I think I can get it to work for the
PDP that's running DECnet, but the LAT has me puzzled...thanks!
/Mic
|
| 5130.3 | The Remote-system name can be any argument | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Tue Jun 01 1993 14:27 | 29 |
| re: .2
> Couple more questions; how do I execute MCC_DISK remotely from the
> IMPM,
> I looked at the .COM and P1 is a different beast...smile.
You should modify the MCC_DISK script to take another argument, and
use it for the remote system name to execute the script on. Ofcourse
this is an optional argument, and if omitted will execute the script
on the current system.
> Also, do we support PDPs with the SCRIPT? Running DECnet IV? Running
> LAT? I saw a not from Erik, regarding OSI, is this the same situation?
If the PDP runs DECnet, then I would imagine that the script can execute
remotely .. however, it can't be the same script. The PDP isn't a VAX,
and therefore doesn't have DCL (does it?). You'd have to have a front
end script (VMS) to execute a remote script (PDP-whatever) .. The results
should be the same. But - I never did this so I can't promise anything.
> I've tried the DATA COLLECTOR and I think I can get it to work for the
> PDP that's running DECnet, but the LAT has me puzzled...thanks!
LAT and DECnet are two totally different things .. I don't know how LAT
could work for you in this situation .. I mean that I don't know how you
can execute a remote script and send the data back to the VMS system via
LAT ..
/keith
|