Home

 

APPC/MVS setup

 

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:

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.
i5/OS The same as the compare value in the routing entry on the i5/OS system.
HP OpenVMS As specified in the OVMS Run Listener command.
Compaq NonStop Kernel The same as the TPNAME specified in the receiver-channel definition.
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 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.

 

Parent topic:

Defining an LU6.2 connection


ic14990_


 

Home