ibm-information-center/dist/eclipse/plugins/i5OS.ic.apis_5.4.0.1/unix15.htm

90 lines
7.3 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
<title>Resource Reservation Setup Protocol APIs</title>
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<!-- Begin Header Records ========================================= -->
<!-- NETMG2 SCRIPT A converted by B2H R4.1 (346) (CMS) by HOLTJM at -->
<!-- RCHVMW2 on 29 Jan 1999 at 10:01:37 -->
<!-- File Edited December 2001 -->
<!-- 031112 JETAYLOR replaced API and/or Exit listings with -->
<!-- pagegenerator output from javascript array -->
<!-- End Header Records -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<a name="Top_Of_Page"></a>
<!-- Java sync-link -->
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript">
</script>
<h2>Resource Reservation Setup Protocol APIs</h2>
<p>The resource reservation protocol (RSVP), along with the RAPI APIs, perform
your integrated services reservation. This protocol is part of the Quality of
service (QoS) function that allows you to request network priority and
bandwidth for TCP/IP applications. The RSVP protocol is used to load rules to
the TCP/IP stack that controls these requests. These rules are called IntServ
rules. QoS also allows the user to define DiffServ rules that request special
handling in the network for groups of applications or connections. See <a href=
"../rzak8/rzak8kickoff.htm">Quality of service (QoS)</a> for more
information.</p>
<p>The six monitor APIs can be used to retrieve information on both IntServ and
DiffServ rules.</p>
<p><strong>Note:</strong> A thorough understanding of the RSVP protocol and the
contents of Internet RFC 2205 is required to be able to use the RAPI APIs
correctly. These APIs will not function unless the proper sequencing of events
between the client and server is observed.</p>
<p>The Resource Reservation Setup Protocol APIs are:</p>
<!-- ***** NOTE ***** Do not manually update text or links in this section. -->
<!-- Updates made in this section *will* be overlaid by automated tools -->
<!-- Notify User Technologies of needed updates to be made in XML for API finder.-->
<!--***************API BEGIN PASTE***************-->
<ul>
<li><A HREF="QgyOpenListQoSMonitorData_API.htm">QgyOpenListQoSMonitorData</A> (Open List of QoS Monitor Data) allows the user to gathering information related to QoS services.</li>
<li><A HREF="qtoq_accept.htm">qtoq_accept()</A> (Accept QoS Sockets Connection) provides simplified Quality of Service support for connection-oriented sockets communications between RSVP aware applications on a client and server.</li>
<li><A HREF="qtoq_close.htm">qtoq_close()</A> (Close QoS Sockets Connection) is called to close the socket and Qos session that was created using the other qtoq_sockets-type APIs.</li>
<li><A HREF="qtoq_connect.htm">qtoq_connect()</A> (Make QoS Sockets Connection) provides simplified Quality of Service functionality for connection-oriented sockets communications between RSVP aware applications on a client and server.</li>
<li><A HREF="qtoq_ioctl.htm">qtoq_ioctl()</A> (Set QoS Sockets Control Options) provides simplified Quality of Service functionality for connectionless sockets communications between RSVP aware applications on a client and server.</li>
<li><A HREF="QtoqDeleteQoSMonitorData.htm">QtoqDeleteQoSMonitorData</A> (Delete QoS Monitor Data) allows the user to delete one or more sets of collected QoS monitor data.</li>
<li><A HREF="QtoqEndQoSMonitor_API.htm">QtoqEndQoSMonitor</A> (End QoS Monitor) allows the user to stop gathering information related to QoS services.</li>
<li><A HREF="QtoqListSavedQoSMonitorData.htm">QtoqListSavedQoSMonitorData</A> (List Saved QoS Monitor Data) allows the user to return a list of all collected monitor data that was saved previously.</li>
<li><A HREF="QtoqSaveQoSMonitorData.htm">QtoqSaveQoSMonitorData</A> (Save QoS Monitor Data) allows the user to save a copy of the collected QoS monitor data for future use.</li>
<li><A HREF="QtoqStartQoSMonitor_API.htm">QtoqStartQoSMonitor</A> (Start QoS Monitor) allows the user to gathering information related to QoS services.</li>
<li><A HREF="rapi_dispatch.htm">rapi_dispatch()</A> (Dispatch the RAPI message handling routine defined in the rapi_session() call) dispatches the RAPI message-handling routine defined in the rapi_session() call.</li>
<li><A HREF="rapi_fmt_adspec.htm">rapi_fmt_adspec()</A> (Format a RAPI Adspec into a string suitable for printing) formats a RAPI Adspec into a string suitable for printing by converting the RAPI Adspec information that has been passed to the API into a string in the supplied buffer.</li>
<li><A HREF="rapi_fmt_filtspec.htm">rapi_fmt_filtspec()</A> (Format a RAPI Filter spec into a string suitable for printing) formats a RAPI Filter spec into a string suitable for printing by converting the RAPI filtspec information that has been passed to the API into a string in the buffer that has been passed to the API.</li>
<li><A HREF="rapi_fmt_flowspec.htm">rapi_fmt_flowspec()</A> (Format a RAPI Flowspec into a string suitable for printing) formats a RAPI Flowspec into a string suitable for printing by converting the RAPI flowspec information that has been passed to the API into a character string in the buffer that was passed to the API.</li>
<li><A HREF="rapi_fmt_tspec.htm">rapi_fmt_tspec()</A> (Format a RAPI Tspec into a string suitable for printing) formats a RAPI Tspec into a string suitable for printing by converting the RAPI Tspec information that has been passed to the API into a string in the buffer that has been passed to the API.</li>
<li><A HREF="rapi_getfd.htm">rapi_getfd()</A> (Get a descriptor to wait on before dispatching the RAPI message handling routine) returns the file descriptor associated with a successful rapi_session() call.</li>
<li><A HREF="rapi_release.htm">rapi_release()</A> (Release the currently active RAPI reservation and close the open sessions) releases the RAPI reservation that is active currently and closes the open sessions.</li>
<li><A HREF="rapi_reserve.htm">rapi_reserve()</A> (Make, modify, or delete a RAPI reservation) used to make, modify, or delete an RSVP reservation in the network.</li>
<li><A HREF="rapi_sender.htm">rapi_sender()</A> (Identify a RAPI sender) identifies an RSVP sender to potential receivers of the data.</li>
<li><A HREF="rapi_session.htm">rapi_session()</A> (Create a RAPI session) returns an API session ID that is unique to this request.</li>
<li><A HREF="rapi_version.htm">rapi_version()</A> (Retrieve the current RAPI version) returns the RAPI version currently being used by the RSVP agent.</li>
</ul>
<!--***************API END PASTE***************-->
<br>
<hr>
<center>
<table cellpadding="2" cellspacing="2">
<tr align="center">
<td valign="middle" align="center"><a href="#Top_Of_Page">Top</a> | <a href=
"unix.htm">UNIX-Type APIs</a> | <a href="aplist.htm">APIs by category</a></td>
</tr>
</table>
</center>
</body>
</html>