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.

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.

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.