{
{    The purpose of this request is to wait until data is available to be
{  received from a peer application over an established CDNA Session
{  connection.
{
{    This request completes as soon as data is available to be received.  If no
{  data is available when this request is made, the request waits a specified
{  interval of time for data to become available.  If no data becomes available
{  within the specified interval, the request will return abnormal status with
{  condition nae$no_data_available.
{
{    The request completes (with normal status) when one of the following
{  conditions occurs:
{
{    - A complete message (or a partial message which completes a message) is
{      available.
{
{    - A partial message whose length equals or exceeds 4096 bytes is
{      available.
{
{    - A partial message contained in 4 or more message blocks is available.
{
{    NOTE: The fact that this request completes normally when 4096 bytes of
{  partial message data are available reflects the limit on the amount of data
{  which may be held within the connection.  A receive data operation will not
{  complete upon delivering a partial message of this size.  In order to insure
{  immediate completion, a request which initiates a receive data operation
{  must specify a buffer of no more than 4096 bytes. If the peer has sent a
{  partial message in blocks smaller than the maximum Transport PDU size, then
{  it is possible for the limit of queued buffers to be reached before the limit
{  on queued data. If this occurs, a receive data operation with a buffer of
{  4096 bytes may not complete immediately, either. The receive buffer size
{  must be established based on the behavior of the peer if immediate completion
{  of a receive request is to occur.
{
{    The osp$await_activity_complete request may also be used to wait for data
{  to be available.  It indicates that data is available under the same
{  conditions.
{
{    At any given time, only one task may be waiting for data to become
{  available on a given connection (no matter which request is used to wait
{  for data).
{
{    A task may not wait for data to become available on a connection if there
{  is already a task waiting for data to become available on the connection or
{  a receive data operation is in progress for the connection.  An attempt to
{  await data availability under either of these conditions results in abnormal
{  status with the condition nae$multiple_waits_attempted.
{
{    WARNING: An application must receive data which has been sent by the peer
{  application within a reasonable amount of time.  If available data
{  accumulates in the connection over an extended period of time, the NAM
{  terminates the connection.
{
{        NAP$AWAIT_DATA_AVAILABLE (FILE_IDENTIFIER, WAIT_TIME,
{          EXPECTED_WAIT_TIME, STATUS)
{
{  FILE_IDENTIFIER: (input) This parameter specifies the file access identifier
{        established when the network file was opened.
{
{  WAIT_TIME: (input) This parameter specifies the maximum number of
{        milliseconds the request is to wait for data to become available.
{
{  EXPECTED_WAIT_TIME: (input) This parameter specifies the expected number of
{        milliseconds the request will have to wait for data to become
{        available.  A value of 0 indicates that no estimate of the actual wait
{        time is being provided.
{
{  STATUS: (output) This parameter specifies the request status.
{        CONDITIONS:
{              ame$improper_device_class
{              ame$improper_file_id
{              ame$ring_validation_error
{              nae$multiple_waits_attempted
{              nae$no_data_available
{              {other BAM conditions}
{
