Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!seismo!mcvax!ukc!eagle!icdoc!iwm
From: iwm@icdoc.UUCP
Newsgroups: comp.os.vms
Subject: Parameters to network tasks
Message-ID: <462@ivax.doc.ic.ac.uk>
Date: Thu, 18-Jun-87 11:11:31 EDT
Article-I.D.: ivax.462
Posted: Thu Jun 18 11:11:31 1987
Date-Received: Sat, 20-Jun-87 09:27:17 EDT
Sender: iwm@doc.ic.ac.uk
Reply-To: iwm@doc.ic.ac.uk (Ian Moor)
Distribution: comp
Organization: Dept. of Computing, Imperial College, London, UK.
Lines: 14


I would like to be able to pass parameters to a DECNET task, looking at
examples in the manuals, the recommended way seem to be to write them on 
the DECNET link and have the task read them from SYS$NET, this seems too
complex for simple uses and requires producing special sending software.
For example we have TCP/IP on machine AVAX, on another node I should like to 
be able to type   COPY prog.pas avax::"task=ftp asun2 prog.p" and have
the ftp task read SYS$NET and ftp it to machine asun2 as prog.p. 
Some experimentation shows that one extra argument is passed as P1 to the
task (a command file) IF it is only alphanumeric, putting more arguments causes
an error 'incorrect device type', giving a fileid with a dot in it causes a
network protocol error and quoting the arguments  seems to prevent them being
transmitted. Does anybody know whats going on here ? Does DECNET make use of
the arguments (e.g for the FAL task) ?