The channel definition at the sending end specifies the address of the target. A listener program must be run at the receiving end.
If the target machine is remote, specify the SPX address of the target machine in the Connection name field of the channel definition.
The SPX address is specified in the following form:
network.node(socket)
where:
If the local and remote machines are on the same network then the network address need not be specified. If the remote end is listening on the default socket (5E86) then the socket need not be specified.
An example of a fully specified SPX address specified in the CONNAME parameter of an MQSC command is:
CONNAME('00000001.08005A7161E5(5E87)')
In the default case, where the machines are both on the same network, this becomes:
CONNAME(08005A7161E5)
The default socket number may be changed by specifying it in the queue manager configuration file (qm.ini) or the Windows registry:
SPX: Socket=5E87
For more information about the values you set using qm.ini or the Windows registry, see Appendix C, Configuration file stanzas for distributed queuing.
If you want to use the KEEPALIVE option (as discussed in Checking that the other end of the channel is still available) you need to add the following entry to your queue manager configuration file (qm.ini):
SPX: KeepAlive=yes
You can use the timeouts described in IPX/SPX parameters to adjust the behavior of KEEPALIVE.
Receiving channel programs are started in response to a startup request from the sending channel. To do this, a listener program has to be started to detect incoming network requests and start the associated channel.
You should use the WebSphere MQ listener.
When receiving on SPX, a maximum number of outstanding connection requests
is set. This can be considered a backlog of requests waiting
on the SPX port for the listener to accept the request. The default
listener backlog values are shown in Table 14.
Table 14. Default outstanding connection requests on OS/2 and Windows If the backlog reaches the values in Table 14, the reason code, MQRC_Q_MGR_NOT_AVAILABLE is
received when trying to connect to the queue manager using MQCONN or
MQCONNX. If this happens, it is possible to try to connect
again.
However, to avoid this error, you can add an entry in the qm.ini
file or in the registry for Windows:
This overrides the default maximum number of outstanding requests (see Table 14) for the SPX listener.
To run the listener with the backlog option switched on, use the
RUNMQLSR -B command. For information about the
RUNMQLSR command, see the WebSphere MQ System
Administration Guide book.Using the SPX listener backlog option
Platform
Default listener backlog value
OS/2 Warp
5
Windows Server
5
Windows Workstation
5
SPX:
ListenerBacklog = n
To run the Listener supplied with WebSphere MQ, that starts new channels as threads, use the RUNMQLSR command. For example:
RUNMQLSR -t spx [-m QMNAME] [-x 5E87]
The square brackets indicate optional parameters; QMNAME is not required for the default queue manager, and the socket number is not required if you are using the default (5E86).
For the best performance, run the WebSphere MQ listener as a trusted application as described in Running channels and listeners as trusted applications. See the WebSphere MQ Application Programming Guide for information about trusted applications.
You can stop all WebSphere MQ listeners running on a queue manager that is inactive, using the command:
ENDMQLSR [-m QMNAME]
If you do not specify a queue manager name, the default queue manager is assumed.
In most cases the default settings for the IPX/SPX parameters will suit your needs. However, you may need to modify some of them in your environment to tune its use for WebSphere MQ. The actual parameters and the method of changing them varies according to the platform and provider of SPX communications support. The following sections describe some of these parameters, particularly those that may influence the operation of WebSphere MQ channels and client connections.
Please refer to the Novell Client for OS/2 documentation for full details of the use and setting of NET.CFG parameters.
The following IPX/SPX parameters can be added to the Novell NET.CFG file, and can affect WebSphere MQ SPX channels and client connections.
Please refer to the Novell Client for DOS and MS Windows documentation for full details of the use and setting of NET.CFG parameters.
The following IPX/SPX parameters can be added to the Novell NET.CFG file, and can affect WebSphere MQ SPX channels and client connections.
Please refer to the Microsoft documentation for full details of the use and setting of the NWLink IPX and SPX parameters. The IPX/SPX parameters are in the following paths in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service\NWLinkSPX\Parameters HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service\NWLinkIPX\Parameters
Please refer to the Microsoft documentation for full details of the use and setting of the IPX and SPX parameters. You access them by selecting Network option in the control panel, then double-clicking on IPX/SPX Compatible Transport.