Google
 

Trailing-Edge - PDP-10 Archives - BB-H348C-RM_1982 - swskit-v21/documentation/fallog.doc
There are no other files named fallog.doc in the archive.
FAL LOGGING CAPABILITY					Jim Krycka
							02-FEB-1981

FAL has a built-in logging capability that is useful for gathering throughput
statistics and otner information, for enabling/disabling access options,
and for diagnosing DAP related problems. This diagnostic tool was developed
to aid Development and Software Specialists; there are no plans to document
it for coustomer use.

On startup, FAL attempts to translate the logical name 'FAL$LOG'. If the
translation succeeds and the equivalence string is of the proper form,
the FAL will log results to 'SYS$OUTPUT' (which is FAL.LOG by default).
If the translation fails or the equivalence string is invalid, logging
will not occur.

For logging to work, the equivalence string for 'FAL$LOG' must be of the
form 'x' or 'x_y', where x is a hexadecimal bit mask and y is a hexadecimal
number. For FAL distributed with DECnet-VAX V2.0, the bit mask is defined
as follows:

    .	Bit 0 set enables logging of the name of the file being accessed
		and DAP error codes that are returned by FAL.
    .	Bit 1 set enables logging of throughput statistics and other DAP
		related performance information.
    .	Bit 2 set enables logging of individual DAP messages as they are
		encoded (built) or decoded (received and processed). By default
		the first 20 (14 hex) bytes of each DAP message are displayed.
		If the 'x_y' form of the logical name is specified, then y
		represents the number of bytes per message to display.
		Note that the bytes of a message are displayed in
		hexidecimal and are read from right to left!
    .	Bit 3 set enables logging of transmit and receive AST completions,
		including the number of bytes transferred. Since DAP messages
		may be blocked into packets, there is only one AST per message
		packet transferred.
    .	Bit 4 set enables logging of posting of QIO requests for the logical
		link and the associated mailbox.
    .	Bit 5 is undefined.
    .	Bit 6 set disables DAP message blocking.
    .	Bit 7 set disables file level CRC checksum generation and comparison.
    .	Bit 8 through 31 are undefined.

NOTE: The above definitions are subject to change.

'FAL$LOG' may be defined as a system-wide logical name:

	$ DEFINE/SYSTEM FAL$LOG 80	! Disable CRC checking

(or as a local name in FAL.COM (or LOGIN.COM):

   	$ DEFINE FAL$LOG 1		! Display filename
	$ RUN SYS$SYSTEM:FAL.EXE
	$ PURGE/KEEP=6 SYS$LOGIN:FAL.LOG
	$ LOGOUT/BRIEF

   	$ DEFINE FAL$LOG 3		! Display filename and statistics
	$ RUN SYS$SYSTEM:FAL.EXE
	$ PURGE/KEEP=6 SYS$LOGIN:FAL.LOG
	$ LOGOUT/BRIEF

   	$ DEFINE FAL$LOG 5_14		! Display filename and first 20 bytes
	$ RUN SYS$SYSTEM:FAL.EXE	!  of each DAP message
	$ PURGE/KEEP=6 SYS$LOGIN:FAL.LOG
	$ LOGOUT/BRIEF

   	$ DEFINE FAL$LOG 1F_50		! Display everything including first 80
	$ RUN SYS$SYSTEM:FAL.EXE	!  bytes of each DAP message
	$ PURGE/KEEP=6 SYS$LOGIN:FAL.LOG
	$ LOGOUT/BRIEF