FileID = OSILocalNSAPCnfg.sys

                  NSAP                                Comment

: 39  840F 454E45 00000009  0003 000C       ; possible AFI 39 format NSAP

{End}   THE REMAINDER OF THIS FILE IS DOCUMENTATION.


The above is an example of a syntactically correct NSAP configuration file.  
Entries may be added or replaced as necessary.  It is advisable to read the 
documentation and syntax notes which follow before making any modifications.


Local Network Service Access Point (NSAP).

The configuration utility reads this file as part of the configuration 
process.  The information presented here is used to configure the NSAP(s) 
for this end system.  The NSAP defines a unique network address for this end 
system, therefore, at least one NSAP must be configured.  Although it is 
possible to configure up to four NSAPs, there should generally be no logical 
need for more than a single NSAP per LAN end system.

The format and abstract syntax of an NSAP is implementation dependent, and 
any NSAP format may be used.  Entries in this file may be up to 19 bytes in 
length, and must NOT specify an NSAP selector.  The selector will be appended 
by the LAN software, increasing the NSAP length to a maximum of 20 bytes.


Syntax.

The {End} tag following the data entries must not be deleted.  It terminates 
the reading of the file and nothing beyond this tag is seen by the utility.  
If the end tag is omitted, the final entry will not be processed and an error 
will be given.  Any large comments should follow the End tag.

NSAP data entries are started by a colon.  They are terminated by a comment, 
by the colon of the following NSAP entry, or by the end tag.  The NSAP 
addresses specified in this file must be expressed as strings of hexadecimal 
bytes, with each byte being expressed as a two character pair in the range 
00 to FF.  Data within an NSAP address entry may be presented as a string of 
contiguous characters, or the characters may be separated by any number of 
spaces or tabs.  This allows data to be written in such a way as to separate 
logical fields within the information being presented.

A semicolon is used to indicate the beginning of a comment.  Comments are 
terminated by the colon which begins the next data entry.  Comments cannot 
contain colons or braces, unless they follow the end tag.  This file is 
entered in comment mode, and remains comment until the first data entry
(colon) is encountered.
