kc_bcamappl_str - Names and addresses of the local application

The data structure kc_bcamappl_str is defined for the object type KC_BCAMAPPL. In the case of KC_GET_OBJECT, UTM returns the names and properties of the local application in kc_bcamappl_str.

UTM informs about the properties of the local application that are assigned tithe application name as defined in MAX APPLI or to the BCAMAPPL names of the application. BCAMAPPL names are also the application names that are used for distributed processing with LU6.1 and for connecting to clients; they are generated with the KDCDEF statement BCAMAPPL. The names assigned to the application are used to establish connections between the communication partners and the application. Each name of the application is assigned its own address for establishing a connection.

Data structure kc_bcamappl_str

char bc_name[8];

char t_prot[6];

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

char listener_port[5];

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

char signon_tac[8];

char secure_soc; 

char user_auth; 

The fields in the data structure have the following meanings:

bc_name
	Contains the name of the local application whose properties UTM returns.
t_prot	The meaning of the data returned in t_prot depends on the operating system under which the UTM application is running. BS2000 systems: t_prot contains the transport protocol used for connections to partner applications established using this application name. Only the first field element of t_prot contains data. The rest contain blanks. The transport protocol is specified as follows:
	'N'	NEA transport protocol
	'I'	ISO transport protocol
	'R'	ISO Transport protocol and RFC1006 convergence protocol via TCP/IP connections
	'TA'	TCP/IP protocol using HTTP or USP protocol
	'TH'	TCP/IP protocol using HTTP protocol
	'TU'	TCP/IP protocol using USP protocol
	Unix, Linux and Windows systems: t_prot contains the address format assigned to the BCAMAPPL names during KDCDEF generation. The address formats are specified as follows:
	'R'	ISO Transport protocol and RFC1006 convergence protocol via TCP/IP connections
	'TA'	TCP/IP protocol using HTTP or USP protocol
	'TH'	TCP/IP protocol using HTTP protocol
	'TU'	TCP/IP protocol using USP protocol
listener_id (only on Unix, Linux and Windows systems)
	Contains the listener ID of the BCAMAPPL names. The listener ID is a positive integer between 0 and 32767. The listener ID determines which connections are to be administered together by the same net process. All connections established via access points and BCAMAPPL names with the same listener ID will be administered by a single net process. BCAMAPPL names with t_prot='T' (SOCKET) form a separate set of numbers, i.e. no BCAMAPPL names for communication via socket interface are bundled with BCAMAPPL names/access points for other transport protocols in a single net process, even if the listener ID is the same.
listener_port
	Only applies if t_prot='T' or 'R' ('R' only on Unix, Linux and Windows systems). listener_port contains the port number at which openUTM waits for connection requests from outside. The port number specified at KDCDEF generation is passed. See also the openUTM manual “Generating Applications”. In UTM applications on BS2000 systems, listener_port is only used if t_prot='T' is generated. In all other cases listener_port='0'. In UTM applications on Unix, Linux and Windows systems, listener_port = '0' means that no listener port number was generated.
tsel_format (only on Unix, Linux and Windows systems)
	Contains the format indicator of the T-selector in the address.
	'T'	TRANSDATA format
	'E'	EBCDIC character format
	'A'	ASCII character format
	If tsel_format contains a blank, then no format indicator was defined in the KDCDEF generation. The meanings of the address formats are described in the "PCMX documentation" (openUTM documentation).
signon_tac
	signon_tac either contains the name of the transaction code of the sign-on service assigned to this transport system access point or is empty (no sign-on service).
secure_soc
	'N'	The secure socket layer is not used for communication over this application.
	'Y'	The secure socket layer is used for communication over this application.
user_auth
	'N'	*NONE is generated as the authentication mechanism for HTTP clients.
	'B'	*BASIC is generated as the authentication mechanism for HTTP clients.