Article Title           : decnet_debugging_logicals
Creation Date           : unknown       
Author                  : ERW, NCD Technical Support
Last Update             : November 11, 1992
Last Update By          : ERW, NCD Technical Support
Expiration Rules        : Applies to VMS until further notice.
Location		: NCD-Articles/Host_Systems/VMS
=============================================================================
 
[DECnet-VAX] Network Object Logging Capabilities
Last Technical Review:  9-JUN-1989                            Size: 127 lines


COPYRIGHT (c) 1988, 1989, 1990 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.

COMPONENT: DECNET/VAX     OP/SYS: VMS V4.X, V5.X

LAST TECHNICAL REVIEW: 11-OCT-1988 14:55

SOURCE: Customer Support Center/Colorado Springs USA


SUBJECT:

Logging capabilities of DECnet/VAX Objects


DISCLAIMER:

These features are both unsupported and undocumented development
tools. However, they can be useful in troubleshooting some types of
network object related issues.


DESCRIPTION:

Use:    Logical names FAL$LOG, NML$LOG, EVL$LOG, RTPAD$LOG and
        RTPAD$TRACE when defined cause the network objects FAL, NML,
        EVL, and CTERM/REMACP to output various types of information
        into the logfile. This information can vary from status  or
        control information to a listing and breakdown of every message
        processed by the object.


File Access Listener (FAL) logging:

FAL$LOG logical name with equivalance string of X OR X_Y where:

        1. X is a hexadecimal bit mask when set enables logging in
           NETSERVER.LOG as follows:

           Bit 0 -- Enables file logging
           Bit 1 -- Enables generation of throughput statistics
           Bit 2 -- Enables logging of DAP messages
           Bit 3 -- Enables logging of transmit and receive AST completions
           Bit 4 -- Enables logging of transmit and receive QIO requests
           Bit 5 -- Enables logging of internal counters
           Bit 6 -- Disables DAP message blocking
           Bit 7 -- Disables DAP CRC error checking
           Bits 8-31 -- RESERVED

        2. Y is a hexadecimal number of bytes per DAP message to display
           in the NETSERVER.LOG file.

        Example definitions for FAL$LOG:
          $ DEFINE FAL$LOG 1
          $ DEFINE FAL$LOG DF
          $ DEFINE FAL$LOG 5_50

NOTE: Some options for FAL$LOG will degrade performance.


Network Management Listener (NML) logging to:

NML$LOG logical name with equivalance string of X, where X is a bit mask
that when set enables logging as follows:

        Bit  0 -- Enables all NICE messages
        Bit  1 -- Enables all permanent data base I/O
        Bit  2 -- Enables endparse state transitions
        Bit  3 -- Enables loopback I/O
        Bit  4 -- Enables ACP I/O
        Bit  5 -- Enables MOP I/O
        Bit  6 -- Enables service operations
        Bit  7 -- Enables logging of things related to event processing
        Bits 8-15 -- RESERVED (unimplemented)
        Bit 16 -- Enables dumping of node permanent data base
        Bit 17 -- Enables dumping of line permanent data base
        Bit 18 -- Enables dumping of logging permanent data base
        Bit 19 -- Enables dumping of object permanent data base
        Bit 20 -- Enables dumping of circuit permanent data base
        Bit 21 -- Enables dumping of module permanent data base

        Example definition for NML$LOG:
           $ DEFINE NML$LOG 1F


Event Logger Object (EVL) logging:

EVL$LOG logical name with equivalance string of X, where X is a bit
mask that when set enables logging as follows:

        Bit 0 -- Enables logging of any data base changes

        Bits 1-3  Refer to messages:
           Bit 1 -- Anytime link to sink is open
           Bit 2 -- Anytime link is confimed to a sink node receiver
           Bit 3 -- Anytime link to event monitor process

        Bits 4-6  Refer to events:
           Bit 4 -- All raw events
           Bit 5 -- Events queued to a sink
           Bit 6 -- Events received by a receiver

        Bits 7-31 RESERVED

        Example definition of EVL$LOG:
           $ DEFINE EVL$LOG 3F


CTERM/REMACP Remote Terminal Object (REMACP) logging:

RTPAD$LOG logical name with equivalence string of X, where X a bit mask
and RTPAD$TRACE logical name equivalance string of VMS_file_specification.

        Bit 0 -- Display VMS-to-XXX message
        Bit 1 -- Place trace of CTERM session in file pointed to by
                 RTPAD$TRACE. Note that the logical RTPAD$TRACE must
                 contain a good filespec or RTPAD dies with a RMS$_ISI

        Example definitions of RTPAD$LOG and RTPAD$TRACE:
           $ DEFINE RTPAD$LOG 3
           $ DEFINE RTPAD$TRACE SYS$MANAGER:RTPAD.LOG