Peek/Spy accepts nodenames in the targets of its PEEK, SPY, WATCH and SHOW USERS commands. Use a standard VMS DECnet node specification ending with a double colon. This may contain an accesss control string per standard VMS DECnet rules. Peek/Spy must be running on the target node, and the PEEK and SPY objects/applications must be defined for DECnet on the target nodes. See the PEEK Node_Names Subtopic: Set-up. Examples: $ PEEK NODEA::J_DOE ! Watch process J_DOE on NODEA. $ SPY NODEA"SYSTEM SYSPASS"::J_DOE ! SPY via SYSTEM account on NODEA. $ SPY/TERM=(NODEA::LTA*,NODEB::LTA*) ! Watch LTAs on NODEA and NODEB. $ PEEK/SHOW USERS NODEA::J_DOE,P_SMITH ! Show these two users on NODEA. Standard VMS * and % wildcards are allowed in the nodename portion of a target specification (providing PEEK has been configured for use of wildcards in nodenames). See the PEEK Node_Names Subtopic: Wildcards.
1 – Watching
In a list of target specifications on a PEEK, SPY or WATCH command,
different nodenames can be prepended to each target in the list. A
nodename, if present, applies only to the single target specification
to which it is prepended.
Examples:
$ PEEK/TERMINAL=(TTA1:,NODEA::TTA1:,TTA2:)
In this example, first TTA1 on the current network node will be
watched. Then TTA1 on NODEA will be watched. Then TTA2 on the
current node will be watched.
$ PEEK/USERNAME=(NODEA::*,P_SMITH)
In this example, first users on NODEA will be watched. Then user
P_SMITH on the current node will be watched.
For more information, see the top-level PEEK Subtopic:
Watching Node_Names.
2 – Showing Users
For PEEK/SHOW USERS, only a single leading nodename may be used. This single leading nodename applies to all of the following user specifications on the SHOW USERS command line. Example: $ PEEK/SHOW USERS NODEA::J_DOE,P_SMITH In this example, Peek will show users J_DOE and P_SMITH on NODEA. Wildcards may still be used in the single leading nodename in a SHOW USERS command. See the top-level PEEK Subtopic: Commands SHOW USERS.
3 – Security
All of the standard DECnet security features are supported, including
access-control strings within node specifications, incoming and
outgoing proxy login access, etc.
Example of an access-control string in a node specificiation:
$ PEEK NODEA"USERB PASSWORDB"::J_DOE
Peek will be run from the account USERB on NODEA and will watch
process J_DOE on NODEA.
4 – Set-up
Peek/Spy must have been started on the target DECnet node, and PEEK and/or SPY must have been added to the DECnet network database on the target node as a known network objects/applications. The commands to define Peek/Spy as network objects/applications are different for DECnet Phase IV and DECnet Phase V.
4.1 – IV-Phase-DECnet-Setup
PEEK can be added as a known object via NCP on a target node either
permanently or temporarily using the NCP DEFINE or SET command.
The basic NCP commands to add the PEEK object on a target node
permanently are:
$ RUN SYS$SYSTEM:NCP
NCP> DEFINE OBJECT PEEK NUMBER 0 FILE PEEK$LOCATION:PEEKNET_Vx.EXE
For SPY use:
NCP> DEFINE OBJECT SPY NUMBER 0 FILE PEEK$LOCATION:SPYNET_Vx.EXE
To permanently enable both incoming and outgoing proxy access to PEEK
and SPY on a target node use:
NCP> DEFINE OBJECT PEEK NUMBER 0 -
FILE PEEK$LOCATION:PEEKNET_Vx.EXE PROXY BOTH
NCP> DEF OBJECT SPY NUMBER 0 -
FILE PEEK$LOCATION:SPYNET_Vx.EXE PROXY BOTH
Note that the correct VMS version number for your system (_V5 _V6 _V7)
must replace the _Vx in the file specifications above. Also note that
the .EXE suffix is required syntax on the file specification.
Use SET instead of DEFINE in the above NCP commands if you only want
the PEEK/SPY objects added to the network datebase temporarily, not
permanently.
See the appropriate VMS Networking manual for more information about
granting access to PEEK as a network object, and for the appropriate
NCP commands for doing this, based on the security considerations of
your site.
4.2 – V-Phase-DECnet-Setup
The following is a typical DECnet Phase V application setup for
PEEK and SPY. These commands were generated by the conversion of
the Phase IV NCP commands listed in the PEEK Node_Names Set-up
Subtopic: IV-Phase-DECnet-Setup.
$ RUN SYS$SYSTEM:NCL.EXE
CREATE NODE 0 SESSION CONTROL APPLICATION PEEK
SET NODE 0 SESSION CONTROL APPLICATION PEEK NODE SYNONYM TRUE
SET NODE 0 SESSION CONTROL APPLICATION PEEK INCOMING PROXY TRUE , -
OUTGOING PROXY TRUE
SET NODE 0 SESSION CONTROL APPLICATION PEEK IMAGE NAME -
PEEK$LOCATION:PEEKNET_V7.EXE
SET NODE 0 SESSION CONTROL APPLICATION PEEK ADDRESSES { NAME = PEEK }
CREATE NODE 0 SESSION CONTROL APPLICATION SPY
SET NODE 0 SESSION CONTROL APPLICATION SPY NODE SYNONYM TRUE
SET NODE 0 SESSION CONTROL APPLICATION SPY INCOMING PROXY TRUE , -
OUTGOING PROXY TRUE
SET NODE 0 SESSION CONTROL APPLICATION SPY IMAGE NAME -
PEEK$LOCATION:SPYNET_V7.EXE
SET NODE 0 SESSION CONTROL APPLICATION SPY ADDRESSES { NAME = SPY }
$ EXIT
These commands are in the file PEEK_SPY_NET$NCP_APPLICATIONS.COM
which is included with your Peek/Spy distribution.
You can enable this typical application setup for DECnet Phase V
by executing this command file. You may also add this to your
SYSTARTUP_VMS.COM if you always want to have the PEEK/SPY
applications defined for DECnet Phase V. NET$CONFIGURE.COM may
also be used to add the PEEK/SPY applications to DECnet.
See the appropriate VMS Networking manual for more information about
granting access to PEEK as a network application, and for the
appropriate commands for doing this, based on the security
considerations of your site.
5 – Wildcards
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.
5.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.