Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!mordor!lll-tis!ames!ucbcad!ucbvax!RED.RUTGERS.EDU!AWalker
From: AWalker@RED.RUTGERS.EDU (*Hobbit*)
Newsgroups: comp.os.vms
Subject: decnet tasks
Message-ID: <12313359517.35.AWALKER@RED.RUTGERS.EDU>
Date: Thu, 25-Jun-87 13:43:59 EDT
Article-I.D.: RED.12313359517.35.AWALKER
Posted: Thu Jun 25 13:43:59 1987
Date-Received: Sat, 27-Jun-87 07:43:40 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 18

I think the "right thing" to do is have the task open sys$net: and read any
additional info it needs.  It would also be nice to be able to specify an
actual .com file path on the remote node -- the "task=foo" construct locks you
into having FOO.COM in the default decnet directory.  The workaround, I suppose,
is to have FOO.COM grab whatever other cmd file you wanted to execute -- or 
use the "task=sys$net" construct [which I think is really cute!!  Never thought
of doing that before...].

I've seen some sites that protect the default decnet-access home directory
against writing by the default account, presumably so you can't drop little
task files there and fire them up.  The "task=sys$net" hack, for these guys,
could be thought of as a security hole, I suppose...

Anyway, if you want to pass parameters, you can always open channels and fire
them back and forth till the cows log out...

_H*
-------