Defining an LU6.2 connection for z/OS using APPC/MVS
To define an LU6.2 connection there are a number of settings to configure.
APPC/MVS setup
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 following table for information:
Remote platform | TPNAME |
---|---|
z/OS® or MVS | The same as TPNAME in the corresponding side information about the remote queue manager. |
IBM® i | The same as the compare value in the routing entry on the IBM i system. |
UNIX and Linux® systems | The same as TPNAME in the corresponding side information about 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 might be required.
In an environment where the queue manager is communicating using 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.
ALTER QMGR LUNAME(luname)
and restart the channel initiator.See LUNAME for further information.