SELECTING AHEAD (EXPERT USER MODE):
----------------------------------

If  you are a novice user, you will  want to walk through the menus and
enter one menu selection at a time.

If  you are  an expert  user, you  can skip  menus by  selecting ahead.
Example:  to display the datalink objects, you can EITHER select 0 from
the main  menu, then 0 from the objects menu,  OR you can type 0 0 from
the main menu.

SETTING AND CLEARING OBJECTS.
-----------------------------

To SET or READ-AND-CLEAR an object, step through the NMF object screens
until the relevant  object is in view.   A prompt at  the bottom of the
screen then allows you to set or clear any one of the objects in view.

$
SELECTING ANOTHER HOST NIA (IN MULTIPLE-NIA SYSTEMS).
------------------------------------------------

NIA selection is a main-menu option for systems that support multiple
host-NIAs.  This allows you to selectively monitor any active host NIA
in your system.  INAMON begins with the default NIA selected.

$
LOOP MODE.
----------

One of the options  that you  find at  the bottom  of each  NMF objects
screen is 'A' for again (repeat current screen).  If you just type 'A',
the screen  is repeated once.   If you type 'A  <count>', the screen is
repeated <count> times.  If  <count>  is  0,  the  screen  is  repeated
indefinitely.  You can hit escape to exit from loop mode.

Using the  'A' response in  conjunction with the  'REPEAT' command, you
can set up endless cycles of  several  screens,  e.g.    the  following
command, entered  from the main  menu would cycle  through the datalink
objects (5 times), then the internet objects (5 times), then repeat the
cycle:

0 0 a 4 e 0 1 a 4 repeat

$
ATTACHING REMOTE AGENT
----------------------

The  transport or CASE address  buffer to attach a  remote agent can be
defined in  a NETADDR  file residing  in the  directory from  which the
program was loaded.  The address can also be typed from the console.

When  an address is typed from the console, only the NSAP address is to
be  entered.  Other addressing info is defaulted (local and remote TSAP
selector = 03 00, local nsap selector = null).

When an address is taken from the NETADDR file, a complete TSAP address
must be specified in the NETADDR file, i.e.  local nsap selector, local
tsap selector, remote nsap, remote tsap.

$
Sample NETADDR file (using 'local' NSAP formats):

;                l.   local                                 remote
;                n.   tsap s.         remote NSAP           tsap s.
;                --  <-----> <---------------------------> <----->
NODE1:address=0x 00  02 0300 0b 49 0003 00aa000209C6 fe 00 02 0300;
NODE2:address=0x 00  02 0300 0b 49 0003 00aa000223EC fe 00 02 0300;

On selecting ATTACH AGENT from the main menu, the following message is
displayed:

 Type N to use NETADDR file
      T to TYPE NSAP

The following are two equivalent ways to attach to a remote agent:
 (1) Type 'N', then type address alias (e.g. NODE1)
 (2) Type 'T', then type NSAP (e.g. '49 0003 00AA00000209C6 FE00')

Note that spaces in the NETADDR file, or in an NSAP typed from the
keyboard, are not significant.

$
BATCH MODE.
----------

If you set objects from a submit file, use the batch option to get rid
of all prompts.  Example:

inamon batch
set 4008 5
set 4009 77
clear 2003
exit

$
TERMINAL INDEPENDENCE
---------------------

INAMON    requires   terminal    dependent   information    in   either
:CONFIG:TERMCAP,  or :LANG:AEDIT.MAC.   At  least the  following escape
sequences  are required: AFMH (cursor home), AFES or AFER (erase screen
or erase  rest of screen),  AFEL (erase to  end of line).   If defined,
reverse video  sequences (AFRV, AFNV) will be  used in loop mode (again
0) when the interval is non-zero.

INAMON will first look at :CONFIG:TERMCAP.  If the file does not exist,
or  does not contain  an AFMH entry,  it will try  :LANG:AEDIT.MAC.  If
neither  file exists or if  some of the entries  required by INAMON are
missing, a warning message is displayed.

Under RMX II.3,  the  default  termcap  file  is  not  appropriate  and
aedit.mac will be used instead.    The  use  of  aedit.mac  presents  a
problem if several terminal types are in use at the same time.  If this
is  a problem, the  user can enrich  the termcap file  with the entries
required  by INAMON.   Remember to use  the SET TERM  command to define
your terminal type.

$

It is  expected that RMX I.8 and RMX  II.4 will provide a more complete
termcap file,  sufficient for use by INAMON.   RMX 86 R7 has no concept
of a terminal type; therefore, :lang:aedit.mac is always required.