1 SHIP
  This SHIP command makes 'shipping' files to other nodes easier
  and quicker than entering individual COPY commands. Use of the
  SHIP command assumes that accounts on multiple systems are
  PROXYed together. 

  Command format:

    $ SHIP source [destination] [nodes] [user] [password]

2 SOURCE
  The file specification of the file(s) to be copied. This
  parameter is required and is simply given to the COPY command.
  A null will cause this and all other parameters to be quieried
  in prompt mode. 

2 DESTINATION
  The file specification of the destination of the file(s) to be
  copied. This parameter is given to the COPY command. If not
  provided then the file specification "*.*;*" is used as the
  default. 

2 NODES
  A list of DECNET nodes to which the specified files are to be
  shipped. If this parameter is null then then logical name
  SHIP$NODES is evaluated. If SHIP$NODES is not defined or
  defined as blank also, then all nodes that are current in the
  current DECNET area are used. If specified as "*" (either
  explicitly or as the value for SHIP$NODES), then all nodes that
  are current in the ENTIRE DECNET network are used. 

  Alternatively, this parameter may be the name of a logical name
  whose value is a list of one or more nodes.  Refer to EXAMPLES
  for more information.
2 USER
  If the desired distination account is different than the
  default account on the destination systems (which is typically
  your procy account) then the destination account is specified
  here. This parameter is given to the COPY command for alternate
  DECNET login. 

2 PASSWORD
  The password that matches the account specified in the USER
  parameter. If the USER parameter is not specified, this
  parameter is not prompted for. If the USER parameter is
  specified, this parameter is required. This parameter is given
  to COPY command for alternate DECNET login. 

2 Examples

  $ SHIP FOO.BAR [.TEST]  vax1,vax2
    (SHIP Version 2.3  6-Jun-1985)
     Copying: FOO.BAR to [.test]
     Copying: FOO.BAR to VAX1::[.test]
     %SHIP-W-NSNR: Node "VAX2" skipped - not reachable

  In this example, it is not clear how many nodes are defined in
  the DECnet network. However, the user wanted to ship file only
  to VAX1 and VAX2. Currently, in this example, VAX2 is not
  available. Also, since the destination directory is NOT null,
  then SHIP will also copy the specified files to the destination
  directory on the source node. 

  $ define ship$node "VAX1,VAX2"
  $ SHIP FOO.BAR
    (SHIP Version 2.1  9-Apr-1985)
     Copying: FOO.BAR to VAX1::*.*;*
     %SHIP-W-NSNR: Node "VAX2" skipped - not reachable


  In this example the destination nodes were not specified so the
  logical name "SHIP$NODES" was evaluated. Currently, in this
  example, VAX2 is not available. The file FOO.BAR will be copied
  to the default directory of the account used on VAX1 (typically
  the root directory of the proxy account on VAX1). 

  $ define some_nodes VAX1,VAX2,VAX4
  $ SHIP FOO.BAR sys$login: some_nodes
    (SHIP Version 2.3  6-Jun-1985)
     Copying: FOO.BAR to sys$login:
     Copying: FOO.BAR to VAX1::sys$login:
     %SHIP-W-NSNR: Node "VAX2" skipped - not reachable
     Copying: FOO.BAR to VAX4::sys$login:


  In this example the destination nodes were specified in the
  logical name "SOME_NODES". Currently, in this example, VAX2 is
  not available. The file FOO.BAR will be copied to the default
  directory (as specified by "SYS$LOGIN") of the account used on
  VAX1 and VAX4.

