Expand Configuration and Management Manual (G06.24+)

Managing the Network
Expand Configuration and Management Manual—523347-008
19-6
Setting Up Network Security
For example, to run a program named MYPROG on the remote node \CITY using an
explicit RUN command, you would type the following command:
RUN \CITY.MYPROG
To run the same program using an implicit RUN command, you would type the
following 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 the following
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
The following 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/
Setting Up Network Security
One of the first tasks you must perform after completing the network configuration is to
set up access to remote resources for network users. To access a process, device, or
file on a remote system, a user must have the appropriate access. Topics explained in
this section include the following:
•
Remote File Security
•
Remote Process Security
•
Remote TACL Processes
•
Global Remote Passwords
•
Subnetwork Security
•
Remote Super ID User
•
Additional Security Techniques