Quick Guide On How to Use NetTL for STREAMS/UX

Check if NetTL is running.

nettl -status

NetTL will start running by default after the system boot (see nettl(1M) for more detail).

If NetTL is running, you can check the log file name, STREAMS/UX subsystem ID, STREAMS/UX log classes, etc.

If it is not running, a superuser needs to start NetTL.

nettl -start

NetTL can be stopped by a superuser.

nettl -stop

You can change the set of NetTL log classes you are interested in.

By default, only DISASTER and ERROR messages are logged. A superuser can modify this default by using the nettlconf command (see nettlconf(1M)). Bit masks for turning on log classes are the following:

For example:

You can format and read the logged messages.

netfmt -f /var/adm/nettl.LOG00

The default error log file is /var/adm/nettl.LOG00.

You can format and filter the logged messages.

netfmt -f /var/adm/nettl.LOG00 -c filter_file

The filter_file would look like:

Example 1: To format only STREAMS DISASTER messages:

formatter   filter  subsystem   STREAMS 
formatter   filter  class        DISASTER

Example 2: To filter on time:

formatter   filter  time_from      12:34:56   1/1/94 
formatter   filter  time_through   21:43:56   1/2/94

Example 3: To filter on STREAMS module ID and sub-ID:

STREAMS      1       100 
STREAMS      2       * 
STREAMS      *       101

Example 4: More complex example:

formatter    filter     subsystem     STREAMS 
formatter    filter     class         DISASTER
formatter    filter     class         ERROR
formatter    filter     class         WARNING
formatter    filter     time_from     12:34:56   1/1/94
formatter    filter     time_through  21:43:56   1/2/94 
STREAMS      1          100 
STREAMS      2          * 
STREAMS      *          101