Share via

1.7 Versioning and Capability Negotiation

  • Article

Supported transports: This protocol uses the RPC over TCP/IP protocol sequence. However, it supports a mechanism for explicitly negotiating the RPC endpoint to be used. Details are specified in section 3.1.4.1.

Protocol versions: This protocol uses a single version of the RPC interface, but that interface has been extended by adding the following additional methods at the end:

  • R_MoveMessage (Opnum 10) (section 3.1.4.10)

  • R_OpenQueueForMove (Opnum 11) (section 3.1.4.11)

  • R_QMEnlistRemoteTransaction (Opnum 12) (section 3.1.4.12)

  • R_StartTransactionalReceive (Opnum 13) (section 3.1.4.13)

  • R_SetUserAcknowledgementClass (Opnum 14) (section 3.1.4.14)

  • R_EndTransactionalReceive (Opnum 15) (section 3.1.4.15)

Capability Negotiation: This protocol is used for receiving messages from a remote queue manager.<2> The queue manager can implement a capability negotiation mechanism as specified in the processing rules for Opening a Queue (section 3.2.4.1) to determine whether this protocol is supported by the remote queue manager.

Security and authentication methods: This protocol supports the NT LAN Manager (NTLM) Authentication Protocol and Kerberos authentication methods.<3>