Expand Configuration and Management Manual (H06.21+, J06.10+)

Managing the Network
Expand Configuration and Management Manual — 529522-013
18 - 6
Gaining Access to Remote Nodes
Running a Program on a Remote Node
When you want to run a program on the network, the program file must reside on the
node where the program is to run. You can use the explicit and implicit RUN
commands to run a program at a remote node the same way you would use these
commands to run a program on the local node.
For example, to run a program named MYPROG on the remote node \CITY using an
explicit RUN command, you would type this command:
RUN \CITY.MYPROG
To run the same program using an implicit RUN command, you would type this
command:
\CITY.MYPROG
When you run a program on a remote node, the default volume and subvolume names
remain in effect. Unless you use the SYSTEM command to change the default node,
the local node remains the default. If, for example, the default node was the local node
when the RUN \CITY.MYPROG command was executed, MYPROG looks for any files
it needs on the local node unless a remote node is explicitly specified in the MYPROG
program file.
You can omit the remote node name from the RUN command if you first issue a
SYSTEM command to change the default node to the remote node. In this example,
the RUN command runs the editor in system \XYZ. The file YOURFILE is also
assumed to reside on system \XYZ.
SYSTEM \XYZ
TEDIT YOURFILE
This command sequence runs \CITY.$DEFLT.DEFLT.MYPROG in processor 3 of the
system named \CITY. The IN file is a disk file located on system \XYZ; the OUT file is a
process named $SPL running on system \SYS45.
SYSTEM \CITY
RUN MYPROG /IN \XYZ.$CAT.SUB.FNAME, OUT \SYS45.$SPL, CPU 3/
Note. These examples and explanations assume that the proper network access rights are in
effect.