Defining an LU 6.2 connection

SNA must be configured so that an LU 6.2 conversation can be established between the two machines. Then proceed as follows.

See the Multiplatform APPC Configuration Guide for OS/2 examples, and the following table for information.

Table 13. Settings on the local OS/2 or Windows system for a remote queue manager platform

If you have more than one queue manager on the same machine, ensure that the TPnames in the channel definitions are unique.

Sending end for OS/2

Establish a valid session between the two machines. The local LU that WebSphere MQ uses is decided in the following order:

1. Specify the LU that will be used. In the queue manager configuration file (qm.ini), under the LU 6.2 section add the line:

   LOCALLU = Your_LU_Name
   

   For more information about the values you set using qm.ini, see Appendix C, Configuration file stanzas for distributed queuing.

2. Specify the environment variable:

   APPNLLU = Your_LU_Name
   

3. If this has not been specified, your default LU will be used.

When you define a WebSphere MQ channel that will use the LU 6.2 connection, the Connection name (CONNAME) channel attribute specifies the fully-qualified name of the partner LU. as defined in the local Communications Manager/2 profile.

SECURITY PROGRAM is always used when WebSphere MQ attempts to establish an SNA session.

Sending end for Windows

Create a CPI-C side object (symbolic destination) from the administration application of the LU 6.2 product you are using, and enter this name in the Connection name field in the channel definition. Also create an LU 6.2 link to the partner.

In the CPI-C side object enter the partner LU Name at the receiving machine, the TP Name and the Mode Name. For example:

Partner LU Name              OS2ROG2
Partner TP Name              recv
Mode Name                    #INTER

Receiving on LU 6.2

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 start this listener program with the RUNMQLSR command, giving the TpName to listen on. Alternatively, you can use Attach Manager in Communications Manager/2 for OS/2, or TpStart under SNA Server for Windows.

Using the RUNMQLSR command

Example of the command to start the listener:

RUNMQLSR -t LU62 -n RECV [-m QMNAME]

where RECV is the TpName that is specified at the other (sending) end as the "TpName to start on the remote side". The last part in square brackets is optional and is not required for the default queue manager.

It is possible to have more than one queue manager running on one machine. You must assign a different TpName to each queue manager, and then start a listener program for each one. For example:

RUNMQLSR -t LU62 -m QM1 -n TpName1
RUNMQLSR -t LU62 -m QM2 -n TpName2

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.

Using Communications Manager/2 on OS/2

If you are going to use Attach Manager in Communications Manager/2 to start the listener program, you must specify the Program parameter string or parm_string in addition to the TPNAME and TPPATH.

You can do this using the panel configuration in Communications Manager/2 or, alternatively, you can edit your NDF file directly (see the heading "Define Transaction Programs" in the Multiplatform APPC Configuration Guide).

Panel configuration

These are the entries required on the TP definition panel:

Transaction Program (TP) name  :  AMQCRS6A
OS/2 program path and file name:  c:\mqm\bin\amqcrs6a.exe
Program parameter string       :  -n AMQCRS6A

NDF file configuration

Your node definitions file (.ndf) must contain a define_tp command. The following example shows what must be included:

define_tp
  tp_name(AMQCRS6A)
  filespec(c:\mqm\bin\amqcrs6a.exe)
  parm_string(-n AMQCRS6A -m QM1)

Using Microsoft SNA Server on Windows

You can use TpSetup (from the SNA Server SDK) to define an invokable TP that then drives amqcrs6a.exe, or you can set various registry values manually. The parameters that should be passed to amqcrs6a.exe are:

  -m QM -n TpName

where QM is the Queue Manager name and TpName is the TP Name. See the Microsoft SNA Server APPC Programmers Guide or the Microsoft SNA Server CPI-C Programmers Guide for more information.