{
{    The purpose of this request is to initiate the establishment of a CDNA
{  connection to a CDNA server application.  In general, the server may be any
{  application which is active on some CDNA system and provides its services via
{  a CDNA connection.
{
{    Establishing a connection is a cooperative process which requires the
{  active participation of both the client application and the server
{  application.  This request is used by the client to request that a connection
{  to a server be established.
{
{    The server application may either accept or reject the requested
{  connection.  If the server accepts the requested connection, the connection
{  becomes established and may be accessed.  If the server rejects the requested
{  connection, the attempt to establish the connection fails and attempts to
{  access the connection result in an abnormal status indicating that the
{  connection has been terminated by the peer application.
{
{    The specified network file is created at the beginning of the connection
{  establishment activity and may be used during this activity to manage the
{  connection.  In particular, the request to establish the connection may be
{  cancelled by detaching (returning) the network file.  However, attempts to
{  access the connection before establishment is complete result in abnormal
{  status.
{
{    The calling task specifies whether it is to wait for the server to respond
{  to the connection request or execute concurrently with the connection
{  establishment activity.  If the task waits for the server to respond, then
{  the network file is detached (returned) if the server does not respond within
{  the specified wait time.  Furthermore, if the server rejects the connection
{  while the task is waiting, the network file is detached (returned). The
{  request returns abnormal status under either of these conditions.
{
{    If the calling task executes concurrently with the connection establishment
{  activity, the nap$await_server_response (or osp$await_activity_complete)
{  request may be used to determine whether the server has responded to the
{  connection request.  A task which executes concurrently with the connection
{  establishment activity is responsible for detaching (returning) the network
{  file if the server rejects the connection or does not respond to the
{  connection request within a reasonable amount of time.
{
{        NAP$REQUEST_CONNECTION (SERVER, CLIENT, FILE, PROTOCOL, ATTRIBUTES,
{          WAIT_TIME, STATUS)
{
{  SERVER: (input) This parameter specifies the network address of the server
{        application to which a connection is to be established.
{
{  CLIENT: (input) This parameter specifies the name of the client application
{        on whose behalf the connection is requested.
{
{        The specified name must be the name of a defined client application --
{        refer to the MANAGE_NETWORK_APPLICATIONS utility.  The caller must
{        be authorized to perform the functions of the specified client
{        application.  The criteria used to validate this privilege is
{        determined by the client_ring, client_system_privilege and
{        client_capability attributes of the specified client application.
{
{  FILE: (input) This parameter specifies the name of the network file which is
{        to be created to identify the local end point of the requested
{        connection.
{
{        The network file is created in the $LOCAL catalog.
{
{  PROTOCOL: (input) This parameter specifies the protocol to be used to provide
{        the connection to be established.
{
{  ATTRIBUTES: (input) This parameter specifies the connection attribute values
{        which are to be used for the requested connection.  A value of NIL for
{        this parameter indicates that default values are to be used for all
{        attributes.
{
{  WAIT_TIME: (input) This parameter specifies the number of milliseconds that
{        the request is to wait for the server to respond to the connection
{        request.  A value of 0 indicates that the calling task is to execute
{        concurrently with the connection establishment activity.
{
{  STATUS: (output) This parameter specifies the request status.
{        CONDITIONS:
{              ame$file_known
{              nae$address_protocol_mismatch
{              nae$application_inactive
{              nae$application_max_conn_limit
{              nae$client_protocol_mismatch
{              nae$connection_terminated
{              nae$insufficient_resources
{              nae$invalid_eoi_message_size
{              nae$max_data_length_exceeded
{              nae$network_inactive
{              nae$server_response_timeout
{              nae$unknown_address_kind
{              nae$unknown_application
{              nae$unknown_attribute
{              nae$unknown_protocol
{              {other BAM conditions}
{
