Defining an LU 6.2 connection on Windows
SNA must be configured so that an LU 6.2 conversation can be established between the two machines.
Once the SNA is configured, proceed as follows.
See the following table for information.
| Remote platform | TPNAME | TPPATH |
|---|---|---|
| z/OS or MVS™/ESA without CICS | The same as in the corresponding side information about the remote queue manager. | - |
| z/OS or MVS/ESA using CICS | CKRC (sender) CKSV (requester) CKRC (server) | - |
| IBM i | The same as the compare value in the routing entry on the IBM i system. | - |
| UNIX and Linux systems | The same as in the corresponding side information about the remote queue manager. | MQ_INSTALLATION_PATH/bin/amqcrs6a |
| Windows | As specified in the Windows Run Listener command, or the invokable Transaction Program that was defined using TpSetup on Windows. | MQ_INSTALLATION_PATH\bin\amqcrs6a |
MQ_INSTALLATION_PATH represents the high-level directory in which IBM MQ is installed.
If we have more than one queue manager on the same machine, ensure that the TPnames in the channel definitions are unique.
For the latest information about configuring AnyNet SNA over TCP/IP, see the following online IBM documentation: AnyNet SNA over TCP/IP and SNA Node Operations.
- Send end on LU 6.2 on Windows
Create a CPI-C side object (symbolic destination) from the administration application of the LU 6.2 product we are using. Enter this name in the Connection name field in the channel definition. Also create an LU 6.2 link to the partner. - Receive on LU 6.2 on Windows
Receiving channel programs are started in response to a startup request from the sending channel.
Parent topic: Set up communication on Windows
Related concepts