Home

 

Connection name (CONNAME)

 

This is the communications connection identifier. It specifies the particular communications link to be used by this channel.

It is optional for server channels, unless the server channel is triggered, in which case it MUST specify a connection name.

The name is up to 48 characters for z/OS, 264 characters for other platforms, and:

If the transport type is TCP

This is either the hostname or the network address of the remote machine (or the local machine for cluster-receiver channels). For example, (MACH1.ABC.COM), (fe80:43e4:0204:acff:fe97:2c34:fde0:3485) or (19.22.11.162). It may include the port number, for example (MACHINE(123)). It can include the IP_name of a z/OS dynamic DNS group or a network dispatcher input port.

If you use an IPV6 address in a network that only supports IPV4, the connection name will not be resolved. In a network which uses both IPV4 and IPV6, Connection name interacts with Local Address to determine which IP stack is used. See Local Address (LOCLADDR) for further information.

If the transport type is LU 6.2

For WebSphere MQ for iSeries, Windows systems, and UNIX systems, give the fully-qualified name of the partner LU if the TPNAME and MODENAME are specified. For other versions or if the TPNAME and MODENAME are blank, give the CPI-C side information object name as described in the section in this book about setting up communication for your platform.

On z/OS there are two forms in which to specify the value:

  • Logical unit name

    The logical unit information for the queue manager, comprising the logical unit name, TP name, and optional mode name. This can be specified in one of 3 forms:

    luname, for example IGY12355

    luname/TPname, for example IGY12345/APING

    luname/TPname/modename, for example IGY12345/APINGD/#INTER

    For the first form, the TP name and mode name must be specified for the TPNAME and MODENAME attributes ; otherwise these attributes must be blank.

    For client-connection channels, only the first form is allowed.

  • Symbolic name

    The symbolic destination name for the logical unit information for the queue manager, as defined in the side information data set. The TPNAME and MODENAME attributes must be blank.

    For cluster-receiver channels, the side information is on the other queue managers in the cluster. Alternatively, in this case it can be a name that a channel auto-definition exit can resolve into the appropriate logical unit information for the local queue manager.

The specified or implied LU name can be that of a VTAM generic resources group.

If the transmission protocol is NetBIOS

This is the NetBIOS name defined on the remote machine.

If the transmission protocol is SPX

This is an SPX-style address consisting of a 4-byte network address, a 6-byte node address and a 2-byte socket number. Enter these in hexadecimal, with the network and node addresses separated by a fullstop and the socket number in brackets. For example: 
CONNAME('0a0b0c0d.804abcde23a1(5e86)')

If the socket number is omitted, the default WebSphere MQ SPX socket number is used. The default is X'5E86'.

This attribute is valid for channel types of:

It is optional for server channels, unless the server channel is triggered, in which case it MUST specify a connection name.

The definition of transmission protocol is contained in Transport type (TRPTYPE).

 

Parent topic:

Channel attributes in alphabetical order


ic11650_


 

Home