Each instance of the channel initiator must have the name of the LU that it is to use defined to APPC/MVS, in the APPCPMxx member of SYS1.PARMLIB, as in the following example:
LUADD ACBNAME(luname) NOSCHED TPDATA(CSQ.APPCTP)
luname is the name of the logical unit to be used. NOSCHED is required; TPDATA is not used. No additions are necessary to the ASCHPMxx member, or to the APPC/MVS TP profile data set.
The side information data set must be extended to define the connections
used by DQM. See the supplied sample CSQ4SIDE for details of how to do
this using the APPC utility program ATBSDFMU. For details of the TPNAME
values to use, see the Multiplatform APPC Configuration Guide
("Red Book") and the following table for information:
Table 32. Settings on the local z/OS system for a remote queue manager platform
| Remote platform | TPNAME |
|---|---|
| z/OS, OS/390, or MVS/ESA | The same as TPNAME in the corresponding side information on the remote queue manager. |
| z/OS, OS/390, or MVS/ESA using CICS | CKRC (sender)
CKSV (requester) CKRC (server) |
| OS/400 | The same as the compare value in the routing entry on the OS/400 system. |
| OS/2 | As specified in the OS/2 Run Listener command, or defaulted from the OS/2 queue manager configuration file. |
| Compaq OpenVMS Alpha | As specified in the Digital OVMS Run Listener command. |
| Compaq NonStop Kernel | The same as the TPNAME specified in the receiver-channel definition. |
| Other UNIX systems | The same as TPNAME in the corresponding side information on the remote queue manager. |
| Windows | As specified in the Windows Run Listener command, or the invokable Transaction Program that was defined using TpSetup on Windows. |
If you have more than one queue manager on the same machine, ensure that the TPnames in the channel definitions are unique.
See the Multiplatform APPC Configuration Guide also for information about the VTAM definitions that may be required.
In an environment where the queue manager is communicating via APPC with a queue manager on the same or another z/OS system, ensure that either the VTAM definition for the communicating LU specifies SECACPT(ALREADYV), or that there is a RACF(R) APPCLU profile for the connection between LUs, which specifies CONVSEC(ALREADYV).
The z/OS command VARY ACTIVE must be issued against both base and listener LUs before attempting to start either inbound or outbound communications.
The connection name (CONNAME) field in the channel definition should be set to the symbolic destination name, as specified in the side information data set for APPC/MVS.
The LU name to use (defined to APPC/MVS as described above) must also be specified in the channel initiator parameters. It must be set to the same LU that will be used for receiving by the listener.
The channel initiator uses the "SECURITY(SAME)" APPC/MVS option, so it is the user ID of the channel initiator address space that is used for outbound transmissions, and will be presented to the receiver.
Receiving MCAs 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. The listener program is an APPC/MVS server. You start it with the START LISTENER command, or using the operations and control panels. You must specify the LU name to use by means of a symbolic destination name defined in the side information data set. The local LU so identified must be the same as that used for outbound transmissions, as set in the channel initiator parameters.