obj_type=KC_CON

In order to create a new LU6.1 transport connection to a remote application, you must place the data structure kc_con_str in the data area.

The following table shows how the fields in the data structure are to be supplied with data.

	Field name 1	Meaning
m	co_name[8]	Name of the partner application with which there is to be communication via the logical connection. For the format of the name see the section "Format and uniqueness of object names".
		BS2000 systems: co_name 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).
		Unix, Linux and Windows systems: You must specify the T-selector which the partner application uses to sign on to the transport system for co_name. The first character must be a letter.
m2 o3	pronam_long[64]	Name of the partner system.
		For pronam_long you specify the name of the processor on which the partner application co_name runs. This is the name of a Unix, Linux, Windows or BS2000 system. The complete host name (FQDN) under which the host is known in the DNS has to be specified. The name can be up to 64 characters long. Instead of a 64 character FQDN name, a short local name (on BS2000 systems: BCAM name) of the partner computer may be used (max. 8 characters). In this case, it must be possible for the transport system to map the local name to an FQDN name or an IP address using external additional information (in BS2000 systems: FQDN file, in Unix, Linux or Windows systems: hosts file).
o	bcamappl[8]	Specifies a name of the local application, as defined at generation in the control statement MAX or BCAMAPPL. A BCAMAPPL name for which T-PROT=SOCKET is generated must not be specified.
		Default: If nothing is specified, the primary application name in MAX ...,APPLINAME= applies.
m	lpap[8]	Name of the LPAP partner of the partner application to which the connection is to be set up. The name of the LPAP partner by means of which the partner application obtains a connection must have been defined by means of the LPAP statement at generation.
		By creating a number of CON objects with the same LPAP name, parallel connections to the partner application are configured. You must ensure that the parallel connections lead to the same partner application (co_name and pronam).
o	termn[2]	Identifier for the type of the communication partner with a maximum length of 2 characters. termn is not queried by UTM; it is set by the user for evaluation purposes in order, for example, to query or group terminal types. The identifier termn is entered in the KB header for job-receiving services (i.e. for services started in the local application by a partner application).
o3	listener_port[5]	Port number of the partner application.
		BS2000 systems: A port number not equal 0 may only be specified, if the local application specified in the bcamappl parameter was not generated with T-PROT=NEA.
o3	t_prot	Only on Unix, Linux and Windows systems: Contains the address format with which the partner application signs on to the transport system. The address format is specified as follows:
		'R'	RFC1006, ISO transport protocol class 0 via TCP/IP and RFC1006 convergence protocol.
o3	tsel_format	Only on Unix, Linux and Windows systems: Contains the format indicator of the T-selector of the partner address:
		'T'	TRANSDATA format
		'E'	EBCDIC character format
		'A'	ASCII character format
		The significance of the address formats is described in the "PCMX documentation" (openUTM documentation).

1	All fields of the kc_con_str data structure that are not listed and all the fields that are not relevant to the operating system used are to be set to binary zero. The data structure is described in full in chapter "kc_con_str - LU6.1 connections".
2	Mandatory on BS2000 systems
3	Optional on Unix, Linux and Windows systems