home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!usenet.coe.montana.edu!saimiri.primate.wisc.edu!mimbres.cs.unm.edu!constellation!geohub.gcn.uoknor.edu!dwight
- From: dwight@geohub.gcn.uoknor.edu (Dwight D. Moore)
- Newsgroups: comp.os.vms
- Subject: Re: DCL Help: Starting a remote DCL file & knowing when it's done
- Message-ID: <1992Nov6.154233.24247@constellation.ecn.uoknor.edu>
- Date: 6 Nov 92 15:42:33 GMT
- Article-I.D.: constell.1992Nov6.154233.24247
- References: <a725911.12@bugs.mc.ti.com> <1992Nov5.212240.9749@rtpnc.epa.gov>
- Sender: usenet@constellation.ecn.uoknor.edu (Usenet Administrator)
- Reply-To: dwight@geohub.gcn.uoknor.edu
- Organization: Geosciences Computing Network, Univ. of Oklahoma
- Lines: 75
- Originator: usenet@kittyhawk.ecn.uoknor.edu
-
- In article <1992Nov5.212240.9749@rtpnc.epa.gov>, rbn@ralph.rtpnc.epa.gov (Bob Boyd) writes:
- |>Newsgroups: comp.os.vms
- |>Path:
- |
- constellation!mimbres.cs.unm.edu!ncar!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!concert!
- !epa-rtp!ralph.rtpnc.epa.gov!rbn
- |>From: rbn@ralph.rtpnc.epa.gov (Bob Boyd)
- |>Subject: Re: DCL Help: Starting a remote DCL file & knowing when it's done
- |>Message-ID: <1992Nov5.212240.9749@rtpnc.epa.gov>
- |>Sender: usenet@rtpnc.epa.gov
- |>Nntp-Posting-Host: ralph.rtpnc.epa.gov
- |>Reply-To: rbn@ralph.rtpnc.epa.gov
- |>Organization: Unisys/EPA
- |>References: <a725911.12@bugs.mc.ti.com>
- |>Date: Thu, 5 Nov 1992 21:22:40 GMT
- |>Lines: 41
- |>
- |>It's relatively easy to set up DCL code that uses transparent task-to-task
- |>DECnet to do this. The basics are that there are two command procedures:
- |>
- |>1. The local procedure:
- |>
- |> Opens for read/write a file specification that causes the remote task
- |> command procedure to be invoked.
- |>
- |> This looks something like:
- |>
- |> OPEN_LINK:
- |> open/read/write remote_link
- |>'remote_node'::"0=''remote_task'"/error=open_failed
- |>
- |> Then issue a read against the link.
- |>
- |> WAIT_FOR_REMOTE:
- |> read/end=remote_done/error=remote_died remote_link remote_record
- |>
- |>2. The remote procedure:
- |> Must be defined to NCP by the same name as used in procedure 1, or be a
- |>command
- |> procedure by the same name. It could also be a logical name that points to
- |>the
- |> command procedure.
- |>
- |> opens SYS$NET for read/write to complete the network link:
- |>
- |> open/read/write net_link SYS$NET/error=net_died
- |>
- |> Then it invokes whatever other commands/images that it is supposed to do.
- |>
- |> When it is done, it can simply issue a
- |>
- |> close/nolog net_link
- |>
- |>If you want examples of stuff like that there are several around. I have some if you
- |>want.
- |>Let me know by e-mail if you do.
- |>
- |>--
- |>Bob Boyd
- |>rbn@ralph.rtpnc.epa.gov
- |>Unisys/EPA
- |>
- |>
-
- If you have system priviledges, setting up a DECnet object is another way
- of making a "known" DECnet task so that the DCL file can reside in the SYS$SYSTEM
- directory. This is good for typical remote batch jobs.
- ----------------------------------------------------------------------------
- Dwight D. Moore
- Geosciences Computing Network
- University of Oklahoma
-
- dwight@geohub.gcn.uoknor.edu (129.15.40.10)
- These opinions do not necessarily represent the opinions of OU or the GCN.
- ----------------------------------------------------------------------------
-