| 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 |
I have a customer that I demo'd the MCC Director 1.2 on VMS for
yesterday. My customer wanted to know if he could do the following:
1. Using the TSAM, alarm on the status of a port on a DECserver
300(I think).
2. When the alarm fires, execute a command file that is on
another node - this command file is one they already use manually
to take action when certain things happen on their terminal
servers.
They are using the DS300s to provide connect to some sort of
process control &/or data collection devices. They did not
want to move the command file to the MCC station.
I'm pretty sure this could be done, but am not that familiar
with batch ques and remote submitting, etc. What would anyone
recommend as good scheme to implement this capability?
Thanks in advance!
Richard
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3289.1 | DEC SCHEDULER should do the job | CLARID::PATEL | We'll get it right on the night | Thu Jul 02 1992 03:10 | 17 |
probably a little bit of an over kill -- but why not use DEC schedule
to schedule a job on the remote system ?
there are other "clugey/cheap/nasty" ways but these tend to be
unreliable/insecure etc...
one way could be to use the product called "deliver" from the tool
shed. Deliver will take any mail arriving to a account and based on the
contents of the from, sub fields will do different things such as
execute com files. When rule fires, send mail to account ACTION on
Remotenode:: with subject:Restart TSV1 = call com file restart P1 =
TSV1 etc etc
-- hows that for $0.02
Amrit
| |||||
| 3289.2 | Submit/remote | RACER::dave | Ahh, but fortunately, I have the key to escape reality. | Thu Jul 02 1992 06:25 | 1 |
How about simply doing a submit/remote from the alarm command procedure? | |||||
| 3289.3 | SUBMIT/REMOTE Works & It's Almost Free! | MORO::MAUTZ_RI | Networks>=DECnet | Thu Jul 02 1992 18:59 | 25 |
Thanks for the help in .1 & .2. I'll look up the software
package in case it's something the customer might want to
use, but I tried the submit/remote and it works just dandy.
I guess I sort of knew about submit/remote but somehow thought
it was complicated and I wanted to see if anyone had used it.
What I did is write a command procedure that contained the
single command: SUBMIT/REMOTE NODE"user pass"::TEST_X.COM. and
called it SUBMIT.COM. I then created an MCC alarm the had
SUBMIT.COM as it Alarm Fired Precedure.
On node NODE:: in my "user pass" account I put a command
procedure called TEST_X.COM that deleted a file I didn't want.
When the alarm fired, the file I didn't want disappeared.
WARNING - use of username and password the way I did is not
recommended, because of the obvious security risk. I only did
this as a "quick and dirty" way to run the test. A better way
would be to use a suitable proxy account to do this sort of thing.
The only other thing I can think of is to make sure you do all
the normal things you have to take into account when submitting
jobs to a batch file, ie. file specs, privs, logical name assignments,
etc.
| |||||