<div class="content"><p> </p><p>During the process of creating a remote <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_aa5e9c2d-16c1-4301-8bfe-18a0913ed275" data-linktype="relative-path">cursor</a></span>,
a <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_60e0e1fa-66fe-41e1-b5e3-ceab97e53506" data-linktype="relative-path">client</a></span>
calls the R_QMGetRemoteQueueName method to retrieve the name of the <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_91d29587-3e24-439b-8f2c-c2a43be99afc" data-linktype="relative-path">remote
queue</a></span> associated with a <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_c1a6400d-703b-4f9a-a74c-40f1487978d9" data-linktype="relative-path">queue</a></span> handle. This
method is obsolete and the <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_434b0234-e970-4e8c-bdfa-e16a30d96703" data-linktype="relative-path">server</a></span> SHOULD take
no action and immediately raise the exception MQ_ERROR_ILLEGAL_OPERATION
(0xc00e0064).<a id="Appendix_A_Target_11"></a><a aria-label="Product behavior note 11" href="3d105257-668f-4768-83fe-344c8405a5a5#Appendix_A_11" data-linktype="relative-path">&lt;11&gt;</a></p><dl>
<dd>
<div><pre> HRESULT R_QMGetRemoteQueueName(
   [in] handle_t hBind,
   [in] DWORD pQueue,
   [in, out, ptr, string] WCHAR** lplpRemoteQueueName
 );
</pre></div>
</dd></dl><p><b>hBind: </b> MUST be set to an <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_8a7f6700-8311-45bc-af10-82e10accd331" data-linktype="relative-path">RPC</a></span>
binding handle as described in <span><a href="../ms-rpce/290c38b1-92fe-4229-91e6-4fc376610c15" data-linktype="relative-path">[MS-RPCE]</a></span>
section <span><a href="../ms-rpce/a01f5886-c485-4bcf-bb23-e0d755510ab7" data-linktype="relative-path">2</a></span>.</p><p><b>pQueue: </b> MUST be a <b>DWORD</b> that contains
a queue context value obtained from the <b>cli_pQMQueue</b> member of the
structure returned by the <span><a href="e8d526c6-a119-4d27-8fac-bf59bab72f30" data-linktype="relative-path">rpc_ACCreateCursorEx</a></span>
method of the qmcomm2 interface. See section <span><a href="aa04190e-9582-43f4-8288-26aa6ec631a1" data-linktype="relative-path">4.4</a></span> for an example
illustrating this value being obtained.</p><p><b>lplpRemoteQueueName: </b> A pointer to a buffer to
receive the null-terminated name of the remote queue associated with <i>pQueue</i>.
On input, this value MUST be NULL.</p><p><b>Return Values: </b> On success, this method MUST return
MQ_OK (0x00000000); otherwise, the server MUST return a failure HRESULT, and
the client MUST treat all failure HRESULTs identically. Additionally, if a
failure HRESULT is returned, the client MUST disregard all out-parameter
values.</p><p>Exceptions Thrown: This method SHOULD take no action and
SHOULD immediately raise the exception MQ_ERROR_ILLEGAL_OPERATION (0xc00e0064).<a id="Appendix_A_Target_12"></a><a aria-label="Product behavior note 12" href="3d105257-668f-4768-83fe-344c8405a5a5#Appendix_A_12" data-linktype="relative-path">&lt;12&gt;</a></p><p>During the remote cursor creation sequence, the <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_2739ef12-a749-4540-9ac3-715968ef4df4" data-linktype="relative-path">supporting
server</a></span> MAY indicate that the client MUST contact a remote <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_476f10ed-08f0-4887-b583-59d5cf909979" data-linktype="relative-path">queue
manager</a></span> to proceed.<a id="Appendix_A_Target_13"></a><a aria-label="Product behavior note 13" href="3d105257-668f-4768-83fe-344c8405a5a5#Appendix_A_13" data-linktype="relative-path">&lt;13&gt;</a> In
response, this method is called by the client to determine where to find the
remote queue manager. <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_7bc5d175-2fa4-481e-893c-6f3eb2862fa4" data-linktype="relative-path">Supporting servers</a></span>
SHOULD contact the remote queue manager on behalf of the client, thus
eliminating the purpose of this method.<a id="Appendix_A_Target_14"></a><a aria-label="Product behavior note 14" href="3d105257-668f-4768-83fe-344c8405a5a5#Appendix_A_14" data-linktype="relative-path">&lt;14&gt;</a></p><p>This method is invoked at the dynamically assigned <span><a href="102555d1-0dbf-4b2e-b78c-e388823d252c#gt_b91c1e27-e8e0-499b-8c65-738006af72ee" data-linktype="relative-path">endpoint</a></span>
returned by the <span><a href="a8c96155-a7e6-41cb-95c7-6ab7e4f8214d" data-linktype="relative-path">R_QMGetRTQMServerPort</a></span>
method when IP_HANDSHAKE (0x00000000) or IPX_HANDSHAKE (0x00000002) is the
interface specified by the <i>fIP</i> parameter.</p><p> When processing this call, the server MUST do the
following: </p><ul><li><p><span><span> 
</span></span>Locate the <span><a href="01412cba-2803-4644-be30-76cdb8560cec" data-linktype="relative-path">RemoteQueueProxyHandle (section 3.1.1.5)</a></span>
ADM element instance in the server&#39;s <i>iRemoteQueueProxyHandleTable</i> where
the <b>Context</b> attribute value of the <b>RemoteQueueProxyHandle</b> ADM
element instance equals <i>pQueue</i>.</p>
</li><li><p><span><span> 
</span></span>If no such <b>RemoteQueueProxyHandle</b> ADM element instance
exists, take no further action and return a failure <span><a href="../ms-dtyp/a9046ed2-bfb2-4d56-a719-2824afce59ac" data-linktype="relative-path">HRESULT</a></span>.</p>
</li><li><p><span><span> 
</span></span>Set <i>lplpRemoteQueueName</i> to the <b>PathName</b> attribute
of the located <b>RemoteQueueProxyHandle</b> ADM element instance.</p>
</li><li><p><span><span> 
</span></span>Return MQ_OK (0x00000000).</p>
</li></ul></div>