CON - define a connection for distributed processing based on LU6.1

The CON statement allows you to define a transport connection between the local UTM application and a partner application. It also assigns an LPAP partner to the real partner application, i.e. the logical access point of the partner application in the local application. You must define the LPAP partner in an LPAP statement (see "LPAP - define an LPAP partner for distributed processing based on LU6.1").
By issuing several CON statement for the same partner application, you can also define parallel transport connections.

Generation when standalone UTM applications are to be linked to UTM cluster applications

For more information on generating LU6.1 connections see "Distributed processing via the LU6.1 protocol"

When generating the CON, PTERM and MUX statements, please note that the name triplet (appliname or ptermname, processorname, local_appliname) must be unique within the generation run.

Example

If a PTERM statement has already been generated with
    PTERM partner_name1,PRONAM= processorname1,

you cannot generate a CON statement with
    CON partner_name1 PRONAM= processorname1,

but you can enter
    CON partner_name1 ,PRONAM= processorname1 ,BCAMAPPL= local_appliname1,

provided local_appliname1 is not identical to the primary UTM application name.

The statements MUX partner_name1 ... and CON partner_name1 are also mutually exclusive.

CON	remote_appliname [ ,BCAMAPPL=local_appliname ] [ ,LISTENER-PORT=number ] ,LPAP=lpapname ,PRONAM={ processorname | C’processorname’ } [ ,TERMN=termn_id ] Unix, Linux and Windows system specific operands [ ,T-PROT=RFC1006 ] [ ,TSEL-FORMAT={ T | E | A } ]

remote_appliname	Name of the partner application with which you wish to communicate via the logical connection. remote_appliname can be up to eight characters in length. Permitted characters are capital letters, numbers and the characters $, # and @. Hyphens are not allowed in names. The first letter must be a capital letter. If lowercase letters are used in a name, you must enter it in single quotes ('...') . remote_appliname is a mandatory specification. BS2000 systems: remote_appliname can be either the BCAM name of a UTM partner application (in the case of a homogeneous link) or the name of a TRANSIT application (in the case of a heterogeneous link). The first letter must be uppercase. Unix, Linux and Windows systems: You must specify the T-selector that the partner application uses to sign on to the transport system for remote_appliname. The first character must be a letter.
BCAMAPPL=	local_appliname A name for the local application, as defined in the MAX or BCAMAPPL control statement. A BCAMAPPL name may not be specified for which T-PROT=SOCKET is generated. On Unix, Linux and Windows systems this name must not begin with a ’$’. The BCAMAPPL name specified in the CLUSTER statement is not permitted here. Default: If nothing is specified, then the primary application name defined in MAX ...,APPLINAME= is used.
LISTENER-PORT=	number Port number of the partner application. All port numbers between 1 and 65535 are allowed. Default: 0 (i.e. no port number) BS2000 systems: A port number different from 0 may only be specified if the local application specified in the parameter BCAMAPPL is not generated with T-PROT=NEA. If 0 is specified, the transport system uses the standard port 102. Unix, Linux and Windows systems If OPTION CHECK-RFC1006=YES, then a port number must be entered for LISTENER-PORT.
LPAP=	lpapname Name of the LPAP partner of the partner application with which the connection is to be established. The name of the LPAP partner via which the partner application signs on must be defined using the statement LPAP lpapname. By issuing several CON statements with the same lpapname, you can establish parallel connections to the partner application. Please note, however, that these parallel connections lead to the same partner application (remote_appliname and processorname). Mandatory parameter
PRONAM=	{ processorname | C’processorname’ } Name of the partner host. The complete name (FQDN) by which the computer is known in the DNS must be specified. The name can be up to 64 characters long. If the processorname contains special characters it must be entered as a character string using C’...’. Mandatory operand No distinction is made between uppercase and lowercase notation; KDCDEF always converts the name of the partner computer into uppercase.
TERMN=	termn_id Identifier up to two characters in length, which indicates the type of communication partner. termn_id is not queried by openUTM, but is used by the user when querying or grouping terminal types, for example. termn_id is entered in the KB header for job-receiving services, i.e. for services started by a partner application in the local application. Default: A4
T-PROT=	This operand is only supported on Unix, Linux and Windows systems. Address format with which the partner application signs on to the transport system. The following address formats are explained in the "PCMX documentation" (openUTM documentation).
RFC1006	Address format RFC1006 Default: RFC1006
TSEL-FORMAT=	This operand is only supported on Unix, Linux and Windows systems. Format identifier of the T-selector. The format indicator specifies the encoding of the T-selectors in the transport protocol. You will find more information in the "PCMX documentation" (openUTM documentation).
T	TRANSDATA format (encoded in EBCDIC)
E	EBCDIC character format
A	ASCII character format Default:     T   if the character set of the T-selector corresponds to the TRANSDATA format.     E   in all other cases It is recommended to specify a value explicitly for TSEL-FORMAT for operation via RFC1006.

The address of a partner application of a UTM application on Unix, Linux and Windows systems

In order to be able to establish a connection to a partner application, the UTM application must know the address of the partner application. You can enter the address using the following operands:

• remote_appliname (address of the partner application in the partner processor)

• PRONAM (real host name or UTM host name of the partner processor)

• LISTENER-PORT (port number for RFC1006)

• T-PROT (the transport protocol used)

• TSEL-FORMAT (format indicator of the T-selector)

See "Providing address information for the CMX transport system (Unix, Linux and Windows systems)".