kc_con_str - LU6.1 connections

The data structure kc_con_str is defined for the object type KC_CON. In the case of KC_GET_OBJECT, UTM returns the properties and the current status of partner applications and connections for distributed processing via LU6.1 in kc_con_str.

Connections for distributed processing and their properties can be created and deleted dynamically (KC_CREATE_OBJECT object type KC_CON, KC_DELETE_OBJECT subopcode1=KC_IMMEDIATE or KC_DELAY, object type KC_CON, see also section "Effects of deletion during the application run" in chapter "KC_DELETE_OBJECT - Delete objects").

Data structure kc_con_str

char co_name[8];

char pronam[8];

char bcamappl[8];

char lpap[8];

char termn[2];

char listener_port[5]; (only on Unix, Linux and Windows systems)

char t_prot; (only on Unix, Linux and Windows systems)

char tsel_format; (only on Unix, Linux and Windows systems)

char state;

char auto_connect;

char connect_mode;

char contime_min[10];

char letters[10];

char conbad[5];

char ip_addr[15];

char co_deleted;

char ip_addr_v6[39];

char ip_v[2];

char pronam_long[64];

The fields in the data structure have the following meanings:

co_name
	Contains the name of the partner application that will be communicated with via the logical connection. The name is up to 8 characters long.
pronam
	Contains the name of the computer on which the partner application co_name is located. If the real computer name is longer than 8 characters: The pronam field contains a symbolic local name assigned for this computer by the transport system. If no connection was established yet, pronam contains blanks. The complete name, up to 64 characters long, can be taken from the pronam_long field. In a UTM application on BS2000 systems it is either the name of a Unix, Linux or Windows system, or the name of a BS2000. In a UTM application on Unix, Linux or Windows systems, pronam contains the name of the partner computer that UTM uses to search for the IP address of the partner in the Name Service.
bcamappl
	Contains the name of the local application via which the connection to the partner application will be established. bcamappl can be the application name defined in the KDCDEF control statement MAX (APPLINAME) or a BCAMAPPL name of the application. The name is a maximum of 8 characters long. In order to be able to establish connections using this name, the local transport system must be known.
lpap	Specifies the partner application to which the logical connection will be established. The name of the LPAP partner via which the partner application connects is specified.
termn	Contains the code for the type of communication partner. The code is entered in the communication area header for the job-receiving services, i.e. for services in the local application that are started by a partner application. The code is defined by the user and serves to arrange the communication partners in groups of certain types. It is not evaluated by UTM. The terminal code is two characters long.
listener_port (only on Unix, Linux and Windows systems)
	Contains the port number of the transport address of the partner application. If listener_port = '0', then no port number was specified when the CON object was created.
t_prot (only on Unix, Linux and Windows systems)
	t_prot contains the address format with which the partner application signs on to the transport system. The address formats are specified as follows:
	'R'	RFC1006, ISO transport protocol class 0 using TCP/IP and the convergence protocol RFC1006.
tsel_format (only on Unix, Linux and Windows systems)
	Contains the format indicator of the T-selectors of the partner address generated by the TNS generation tool.
	'T'	TRANSDATA format
	'E'	EBCDIC character format
	'A'	ASCII character format
	The meanings of the address formats are described in the "PCMX documentation" (openUTM documentation).
state	Specifies the status of the partner application or its LPAP partner:
	'Y'	The partner application is not disabled (ON). The connection to the partner application is or can be established.
	'N'	The partner application is disabled (OFF). No logical connection to the partner application can be created. The lock must be explicitly removed by the administration in order for the application to be able to work with the partner application (see kc_lpap_str.state under point state in chapter "kc_lpap_str - Properties of LU6.1 partner applications").
auto_connect
	Specifies if the connection to the partner application is automatically established at the start of the application:
	'Y'	When the application is started, UTM will attempt to establish the connection automatically, i.e. if the partner application is available when the local application is started, then the connection is established after starting.
	'N'	No automatic connection when starting.
connect_mode
	Specifies the current status of the connection:
	'Y'	The connection is established.
	'W'	UTM is now attempting to establish the connection (waiting for connection)
	'N'	The connection is not established.
contime_min
	Specifies how many minutes the connection to the partner application has existed until now.
letters	Contains the number of input and output messages for the partner application since the last start of the local application.
conbad	Specifies how often the connection has been lost since the last start of the local application.
ip_addr	Returns the IP address used by UTM for this connection from the object table of the application if the address is an IPv4 address. BS2000 systems: openUTM always returns blanks in the ip_addr field. Unix, Linux and Windows systems: An IPv6 address is returned in the ip_addr_v6 field (see below). UTM uses the address to set up connections to partner applications. UTM reads the IP address from the name service when the application is started using the generated processor name (pronam). If the object tables do not contain an IPv4 address for the partner computer, UTM will return blanks in ip_addr.
co_deleted
	Indicates whether the transport connection was deleted from the configuration dynamically:
	'Y'	The transport connection is deleted.
	'N'	The transport connection is not deleted.
ip_addr_v6
	Returns the IP address used by UTM for this connection from the object table of the application if the address is an IPv6 address or an IPv4 address embedded in IPv6 format. BS2000 systems: openUTM always returns blanks in the ip_addr_v6 field. Unix, Linux and Windows systems: An IPv4 address is returned in the ip_addr field (see above). UTM uses the address in order to establish connections to the partner application. UTM reads the IP address from the Name Service using the generated computer name (pronam) when the application is started. If there is no IPv6 address in the object tables for the partner computer, UTM returns blanks in ip_addr_v6.
ip_v	Specifies whether the IP address used by UTM for this connection is an IPv4 or an IPv6 address: Unix, Linux and Windows systems:
	'V4'	IPv4 Address.
	'V6'	IPv6 address or IPv4 address embedded in IPv6 format.
	BS2000 systems: openUTM always returns blanks in the ip_v field.
pronam_long
	Name of the computer on which the partner application co_name is located. In a UTM application on BS2000 systems, this is either the name of a Unix, Linux or Windows system, or of a BS2000 host. pronam_long is always supplied. In a UTM application on Unix, Linux or Windows systems, pronam_long contains the name of the partner computer by means of which UTM searches the IP address of the partner computer in the name service.