/[NO]FORCE_NETWORK_ACCESS

   When using wildcards in nodenames, PEEK will skip accessing
   the network to watch processes on the current node.

   (An exception to skipping network access for the local node is when
   there is an access control string in the wildcarded nodename
   specification which does not match the current username. In this
   case, because the access requests a different username to do the
   watching, PEEK will use network access to PEEK on the local node.)

   One can force access across the network for the local node
   during a wildcarded nodename operation by specifying
   /FORCE_NETWORK_ACCESS on the command line or by specifying the
   logical name WATCHER$FORCE_NETWORK_ACCESS as TRUE. This logical
   may be defined system-wide by PEEK_DEFAULTS.COM, or may be locally
   defined in any of the logical-name tables specified by
   LNM$PEEK_TABLE_SEARCH_LIST, which is defined in PEEK_DEFAULTS.COM.
   See the top-level PEEK Subtopic: Defaults.

   Example:  $ PEEK/FORCE_NETWORK_ACCESS *::*