|  |         I think what you want is FAL$LOG---define it /SYSTEM.  Defining
        it to a value of "1" will log the files actually opened.
        Defining other bits will increase the logging (you can make
        it dump every record it transfers, I think, plus bookkeeping
        info, although I don't recall the values).  And yes, any
        output will be in NETSERVER.LOG.
        
        	/dave
 | 
|  | The following info is extracted from BULOVA""::SYS$NOTES:DECNETVMS.NOT
Note 21.5
-------------------------------------------------------------------------
     File Access Listener (FAL) logging:
     FAL$LOG logical name with equivalence string of X or X_Y where:
     1.  X is a hexadecimal bit mask as follows:
          Bit 0 set enables logging of file name.
          Bit 1 set enables generation of throughput statistics.
          Bit 2 set enables logging of DAP messages.
          Bit 3 set enables logging of xmit and recv AST completions.
          Bit 4 set enables logging of xmit and recv QIO requests.
          Bit 5 is reserved.
          Bit 6 set disables DAP message blocking.
          Bit 7 set disables DAP CRC error checking.
          Bits 8-31 are reserved.
     2.  Y is a  hexadecimal  number  of  bytes  per  DAP  message  to
         display.
     Example Definitions:
          $ Define FAL$LOG 1
          $ Define FAL$LOG DF
          $ Define FAL$LOG 5_50
     Note that options 2,3, and 4 degrade performance.
				Jim Halpin
 |