{
{    The purpose of this request is to synchronize data transfer over an
{  established CDNA Session connection.  Synchronizing a connection clears the
{  connection of data which has been sent (in one or both directions) but not
{  received.  Synchronizing a connection sends a limited amount of priority
{  data to the peer application.
{
{    Synchronization is given priority over data transfer on a connection.
{  This means that the peer application may be notified of the synchronization
{  prior to receiving data which was sent before the synchronize operation.
{  (The peer application is always notified of the synchronization prior to
{  receiving any data sent after the synchronize operation.)
{
{    Synchronization is not subject to connection flow control.  That is, there
{  is no regulation of the number of synchronization notifications which may
{  accumulate in a connection (due to failure of the peer application to
{  receive them).  A connection may be synchronized even if the connection is
{  congested such that data may not be transferred to the peer application.
{
{    Since synchronization is not subject to flow control, it should be used
{  judiciously.  If an excessive number of synchronization notifications
{  accumulate in the connection, the network may terminate the connection.
{
{    If send data synchronization is specified and a send data operation is
{  active, the operation completes immediately.  Normal status is returned even
{  though not all data is transferred.  Subsequent send data operations result
{  in normal data transfer.
{
{    If receive data synchronization is specified, the the peer application
{  must confirm the synchronization before the transfer of data from the peer
{  application may resume.  Until a notification of the synchronize confirm
{  operation is received by the application, no data may be received from the
{  peer application.
{
{    If receive data synchronization is specified, notification of a
{  synchronize confirm operation by the peer application must be received
{  before another synchronize request specifying receive data synchronization
{  may be made.
{
{    If only send data synchronization is specified, then no peer confirmation
{  is required.  Transfer of data to the peer application may resume upon
{  completion of the request.
{
{        NAP$SE_SYNCHRONIZE (FILE_IDENTIFIER, DIRECTION, DATA, STATUS)
{
{  FILE_IDENTIFIER: (input) This parameter specifies the file access identifier
{        established when the network file was opened.
{
{  DIRECTION : (input) This parameter specifies the direction(s) in which data
{        transfer is to be synchronized.  Data which has been sent in the
{        specified direction but not received is discarded.  The permitted
{        parameter values and their meanings are:
{
{          nac$se_synchronize_send_data: Synchronize the transfer of data to the
{            peer application.
{
{          nac$se_synchronize_receive_data: Synchronize the transfer of data
{            from the peer application.
{
{          nac$se_synchronize_all_data: Synchronize the transfer of data to and
{            from peer application.
{
{  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_synch_confirm_pending
{              nae$se_synchronize_length_error
{              nae$se_unknown_synch_direction
{              nae$supervisory_traffic_limit
{              {other BAM conditions}
{
