| 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
|
| 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.
|