{
{    The purpose of this request is to interrupt an established CDNA Session
{  connection.  A connection interrupt sends a limited amount of priority
{  information to the peer application.
{
{    An interrupt is given priority over data on a connection.  This means that
{  the peer application may receive an interrupt prior to receiving data sent
{  before the interrupt.  (The peer application always receives an interrupt
{  prior to receiving any data sent after the interrupt).
{
{    An interrupt is not subject to connection flow control.  That is, there is
{  no regulation of the number of interrupts which may be held within a
{  connection.  A connection may be interrupted even if the connection is
{  congested such that data may not be transferred to the peer application.
{
{    Since interrupts are not subject to flow control, they should be used
{  judiciously.  If an excessive number of interrupts accumulate in the
{  connection (due to failure of the peer application to receive them), the
{  network may terminate the connection.
{
{        NAP$SE_INTERRUPT (FILE_IDENTIFIER, DATA, STATUS)
{
{  FILE_IDENTIFIER: (input) This parameter specifies the file access identifier
{        established when the network file was opened.
{
{  DATA: (input) This parameter specifies the data to be sent to the peer
{        application.  The length of the data may range from 1 to 14 bytes.
{
{  STATUS: (output) This parameter specifies the request status.
{        CONDITIONS:
{              ame$improper_device_class
{              ame$improper_file_id
{              ame$ring_validation_error
{              nae$connection_terminated
{              nae$improper_protocol
{              nae$se_interrupt_length_error
{              nae$supervisory_traffic_limit
{              {other BAM conditions}
{
