| Title: | "ASK THE WIZARDS" |
| Moderator: | QUARK::LIONEL |
| Created: | Mon Oct 30 1995 |
| Last Modified: | Mon May 12 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1857 |
| Total number of notes: | 3728 |
Return-Path: "VMS001::WWW"@vms001.das-x.dec.com Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX); Tue, 25 Mar 1997 20:59:22 -0500 Received: from vms001 by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV) id UAA24281; Tue, 25 Mar 1997 20:52:13 -0500 (EST) Date: Tue, 25 Mar 1997 20:54:46 -0500 Message-Id: <[email protected]> From: "VMS001::WWW"@vms001.das-x.dec.com (25-Mar-1997 2055) To: [email protected], [email protected], [email protected] Subject: Ask the Wizard: '[email protected]' X-VMS-To: [email protected] Remote Host: (null) Browser Type: Mozilla/3.0 (Win16; I) Remote Info: <null> Name: Kevin Phillips Email Address: [email protected] CPU Architecture: VAX and Alpha Version: v 6.2 Questions: Dear Wizard.. Hi, its me again and this time I have a query regarding DCL scripting and our Cluster of 2 Alpha's. I have a script that calls some other scripts for system monitoring. The problem is, though I have the master script running on one Alpha it still needs to be able to invoke a script on the other one. I've tried numerous methods like: $! Run Script on the other Alpha $! $ @NCLAA"user password"::S$FAX1:[USERS.MONITOR]NCLAA_MON.COM and $! $ SET HOST 0 USER PASSWORD @s$FAX1:[USERS.MONITOR]NCLAA_MON.COM $! $! Finished Running on NCLAA Both don't seem to work - The data that is created with NCLAA_MON.COM is specific to processes running on that host. My last resort would be to just make the NCLAA_MON.COM submit itself and just hope that the master one will Synch up with the data... How DO I activate a script on another Machine in DCL? Is it possible? Thanks again Kevin Phillips
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1702.1 | DECnet task-to-task, SUBMIT, SYSMAN> DO, etc... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Wed Mar 26 1997 09:43 | 12 |
Activating a DCL procedure on another node is fairly simple -- one can use DECnet task-to-task (OPEN, READ, WRITE and CLOSE commands over a DECnet task-to-task connection), or one can use the DECnet task object via `TYPE host"user pass"::"task=taskname"', or one can use node-specific VMScluster batch queues and SUBMIT commands. (The DECnet techniques are covered in the DECnet management manual.) Your command procedure will operate within the context of the node it is invoked on -- in your specific example shown, you have invoked a remote procedure for execution on the local node. | |||||
| 1702.2 | EPS::VANDENHEUVEL | Hein | Thu Mar 27 1997 13:33 | 26 | |
> $! Run Script on the other Alpha
> $!
> $ @NCLAA"user password"::S$FAX1:[USERS.MONITOR]NCLAA_MON.COM
This will use RMS (DECnet/FAL) to open the file on the other node,
read it, and execute it on the local node. Much like: $TYPE NCLAA::...
> My last resort would be to just make the NCLAA_MON.COM submit itself and just
>hope that the master one will Synch up with the data...
That is not a bad solution at all. Check out the SYNC command to ensure
proper ordering. Additional hints in this space: - Use f$envi("procedure")
to figure out what file to submit and to figure out the work directory.
- Submit the procedure with /PARAM=some_step. Use the P1 (or other param
of course) to understand whether this is master, slave, first start, or
partly done. For example. Absence might indicate a fresh start, do the
local stuff, submit on remote node with param "slave" and exit.
Upon finding "slave" jump to a specific label and to the appropriate
stuff. ($if p1.nes."" then goto 'p1 !?). When done, resubmit on
original node with param "slave_done" or some such to allow the
procedure to re-start at the right place.
hth,
Hein van den Heuvel
| |||||