NCPHELP.HLB  —  SET  LOGGING
 Use the SET LOGGING command to create or modify logging parameters in
 the volatile database on the executor node. Use the DEFINE LOGGING
 command to create or modify logging parameters in the permanent
 database on the executor node. The STATE and NAME parameters are valid
 only for the executor node (i.e., the SINK parameter should specify or
 default to the executor).

 SET     KNOWN LOGGING     (parameters ...)
         LOGGING CONSOLE
         LOGGING FILE
         LOGGING MONITOR

 All underscores found in parameters must be replaced with spaces
 when parameters are used in NCP commands.

1  –  ALL 

 Use the SET LOGGING ALL command to update the  volatile  copy  of  the
 database on the executor node with all the logging parameters stored
 for the logging component in the permanent database on  the  executor
 node.

2  –  EVENTS event-list 

 Specifies those events to be logged.

 See HELP EVENTS for a list of valid events.

3  –  KNOWN 

 Introduces a plural parameter or component.

3.1  –  EVENTS 

 Indicates that all events are to be logged.

3.2  –  LOGGING 

 Indicates that the specified parameters for all known logging are to be
 created or modified in the database.

4  –  CIRCUIT circuit-id 

 Identifies the circuit for which events are to be logged.

5  –  LINE line-id 

 Identifies the line for which events are to be logged.

6  –  CONSOLE 

 Indicates that the specified parameters for the logging console are to
 be created or modified in the database.

7  –  FILE 

 Indicates that the specified parameters for the logging file are to be
 created or modified in the database.

8  –  MODULE 

 Introduces a MODULE parameter.  Possible module names are:

         X25-PROTOCOL
         X25-SERVER
         X29-SERVER
         X25-ACCESS

8.1  –  X25-ACCESS 

 Indicates that the logging parameters for the specified source are to
 be created or modified in the data base.

8.2  –  X25-PROTOCOL 

 Indicates that the logging parameters for the specified source are to
 be created or modified in the data base.

8.3  –  X25-SERVER 

 Indicates that the logging parameters for the specified source are to
 be created or modified in the data base.

8.4  –  X29-SERVER 

 Indicates that the logging parameters for the specified source are to
 be created or modified in the data base.

9  –  MONITOR 

 Indicates that the specified parameters for the logging monitor are to
 be created or modified in the database.  If no NAME parameter, the
 default monitor is OPCOM.

10  –  NAME file-name 

 Identifies the name of a console, file, or monitor program to which
 events will be logged.

 If no NAME parameter is specified for the monitor sink, events
 will be sent to the default monitor, OPCOM.  If no NAME parameter
 is specified for the console sink, events will be sent to OPA0:.

11  –  NODE node-id 

 Identifies the node for which events are to be logged.

12  –  SINK 

 Identifies the node that is to receive events. There are two
 possibilities:

         EXECUTOR        identifies the local node
                         (default).

         NODE node-id    identifies a node in the
                         network.

13  –  STATE 

 Specifies the operational state of the sink. There are three possible
 states:

         HOLD    The sink is temporarily unavailable
                 and events should be queued.

         OFF     The sink is unavailable for receiving
                 events.

         ON      The sink is available for receiving
                 events.

14  –  Examples 

      NCP>SET LOGGING MONITOR KNOWN EVENTS
      NCP>SET LOGGING MONITOR STATE ON

          These two commands enable normal event logging using OPCOM.
          To receive the formatted events at a terminal, use the DCL
          command, REPLY/ENABLE=NETWORK.

      NCP>SET LOGGING CONSOLE KNOWN EVENTS
      NCP>SET LOGGING CONSOLE NAME [SYSMGR]EVENTS.DAT
      NCP>CLEAR LOGGING CONSOLE EVENT 4.14
      NCP>SET LOGGING CONSOLE STATE ON

           These commands enable formatted logging of all events but
           the node reachability change event to file EVENTS.DAT.

      NCP>SET LOGGING MONITOR STATE OFF

          This command sets the operational state  of  logging  to
          OPCOM on the executor node to OFF.
Close Help