Use of the standard VMS * and % wildcards within Peek/Spy nodename
   specifications is based on the correct configuration of the
   logical name PEEK_WILDCARD_NODES.

   This logical name is used by Peek/Spy to determine which DECnet
   nodes are available to be checked for a wildcard match during a
   wildcarded nodename operation.

   The multi-valued logical PEEK_WILDCARD_NODES should equate to
   the actual nodenames available to be checked, in the order they
   should be accessed, during a wildcarded nodename operation.

   The logical name PEEK_WILDCARD_NODES can be defined by the
   PEEK_DEFAULTS.COM file when starting up PEEK. PEEK_DEFAULTS.COM
   contains an example of the use of this logical name to control
   use of wildcarded nodenames.

   The PEEK_WILDCARD_NODES logical name as defined by PEEK_DEFAULTS.COM
   can also be superceded in any of the logical-name tables specified in
   LNM$PEEK_TABLE_SEARCH_LIST which is defined in PEEK_DEFAULTS.COM.
   This allows customization, for individual users or groups of users,
   of the nodes which are checked during wildcarded nodename operations.

   Example: $ DEFINE PEEK_WILDCARD_NODES NODE_A,NODE_F,NODE_C

   Placing the above command into one's LOGIN.COM would direct PEEK
   to check the nodes NODE_A, NODE_F and NODE_C, in that order,
   during a wildcarded nodename operation, to see if they match the
   wildcarded nodename specified in a PEEK command.

1  –  Forcing 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 occurs
   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 control string requests a
   different username to do the watching, PEEK will use DECnet
   network access to PEEK on the local node.

   One can also force network access 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 in any of the logical-name
   tables specified in LNM$PEEK_TABLE_SEARCH_LIST which is defined
   in PEEK_DEFAULTS.COM.