3.1.4.24 R_QMGetRTQMServerPort (Opnum 31)
The R_QMGetRTQMServerPort method returns an RPC port number, as specified in [MS-RPCE], for the requested combination of interface and protocol. The returned RPC port number can be used for all qmcomm and qmcomm2 methods.
-
DWORD R_QMGetRTQMServerPort( [in] handle_t hBind, [in] DWORD fIP );
hBind: MUST be set to an RPC binding handle as described in [MS-RPCE] section 2.
fIP: Specifies the interface for which a port value is to be returned. One of the following values MUST be specified; otherwise, this method MUST return 0x00000000 to indicate failure.
Value |
Meaning |
---|---|
IP_HANDSHAKE 0x00000000 |
Requests that the server return the RPC port number for the qmcomm and qmcomm2 interfaces bound to TCP/IP. The default port number is 2103. |
IP_READ 0x00000001 |
Requests that the server return the RPC port number for the qm2qm interface, as specified in [MS-MQQP], bound to TCP/IP. The default port number is 2105. |
IPX_HANDSHAKE 0x00000002 |
Requests that the server return the RPC port number for the qmcomm and qmcomm2 interfaces bound to SPX.<65> The default port number is 2103. |
IPX_READ 0x00000003 |
Requests that the server return the RPC port number for the qm2qm interface, as specified in [MS-MQQP], bound to SPX.<66> The default port number is 2105. |
Return Values: On success, this method returns a non-zero IP port value for the RPC interface specified by the fIP parameter. If an invalid value is specified for fIP, this method MUST return 0x00000000.
Exceptions Thrown: No exceptions are thrown beyond those thrown by the underlying RPC protocol, as specified in [MS-RPCE].
As specified in section 3.1.3, this protocol configures a fixed listening endpoint at an RPC port number. For the interface and protocol specified by the fIP parameter, this method returns the RPC port number determined at server initialization time. If the default port is already in use, the server SHOULD increment the port number by 11 until an unused port is found.
Security consideration: Servers MUST NOT enforce security limitations for this method, since clients can call this method before configuring RPC binding security. See section 5.1 for details.